Market Domain
The Market domain represents the external business environment, market dynamics, competitive positioning, and industry trends that influence an organization's strategic decisions and operational performance. It provides a structured approach for modeling market segments, competitive positions, industry forces, and emerging trends.
Schema: market.schema.json
Specification: JSON Schema Draft-07
Overview
What is the Market Domain?
The Market domain captures the external context in which an organization operates, enabling market-centric analysis that drives strategic planning and competitive advantage. The domain covers:
- Market Segments — Distinct portions of markets with unique dynamics
- Competitive Positions — Assessment of competitive standing and rivalry
- Market Trends — Emerging patterns and directional shifts
- Industry Analysis — Evaluation of industry forces and evolution
This domain extends the strategic context of the Triodian Metamodel by providing deeper insights into market conditions, competitive landscapes, and industry evolution.
Purpose and Value
The Market domain enables architects and planners to:
- Analyze market dynamics — Understand competitive forces influencing strategy
- Map competitive positions — Identify threats and opportunities
- Monitor industry trends — Detect potential disruptions to business models
- Support market decisions — Enable data-driven market entry and positioning
- Drive innovation — Identify market gaps and competitive white space
The Market domain maps directly to business intelligence concepts:
- Market Segment → Market dimension /segment hierarchy
- Competitive Position → Competitor data entity
- Market Trend → Time-series trend analysis
- Market Size → Revenue /volume metrics
- Market Share → Calculated market share KPIs
Core Components
The Market domain uses interconnected analytical elements:
- Market Segments: Distinct market portions with unique characteristics
- Competitive Positions: Standing relative to competitors
- Market Trends: Emerging patterns and shifts
- Industry Analysis: Porter's forces and industry evolution
Domain Attributes
Core Attributes
| Attribute | Type | Description | Required |
|---|---|---|---|
marketID | String | Unique identifier for the market element | ✓ |
title | String | Name or title of the market | ✓ |
description | String | Detailed explanation of the market | ✓ |
marketDefinition | String | Definition of market boundaries | |
orgUnitTitle | String | Organization unit responsible for market intelligence | ✓ |
orgUnitID | String | ID of the organization unit named in orgUnitTitle | |
orgUnitRoles | Array[String] | Roles that manage market analysis | |
marketSize | Object | Current and projected market dimensions | |
marketGrowthRate | Object | Rate of market expansion or contraction | |
marketSegmentation | Array[Object] | How the overall market is divided | |
marketTrends | Array[String] | Emerging patterns and directional shifts (detailed trends are marketTrend elements) | |
marketBarriers | Array[String] | Obstacles to market entry or expansion | |
competitiveIntensity | Object | Level of competition in the market | |
regulatoryFactors | Array[String] | Regulatory influences on the market | |
technologicalFactors | Array[String] | Technology impacts on the market | |
economicFactors | Array[String] | Economic influences on the market | |
socialFactors | Array[String] | Social trends affecting the market | |
environmentalFactors | Array[String] | Environmental considerations | |
strategicOpportunities | Array[String] | Market-based opportunities identified | |
strategicThreats | Array[String] | Market-based threats identified | |
strategicAlignment | String | How market understanding supports strategy | |
performanceIndicators | Array[Object] | Metrics for market performance (shared performanceIndicator: metricName, metricDescription, currentValue, targetValue, unit, trend) | |
dependencies | Array[Object] | Dependencies on other domains (shared dependency: dependencyType, domainType, entityID, description) | |
relatedMarkets | Array[Object] | Related markets | |
improvementOpportunities | Array[String] | Areas for enhancement |
Competitive positions, market trends and industry analyses are separate element records, each of which references its market by marketID. They are described below.
Market Size (marketSize)
| Attribute | Type | Description | Required |
|---|---|---|---|
currentSize | String | Current market size | |
currency | String | ISO 4217 three-letter currency code | |
year | String | Year of the current size | |
projectedSize | String | Projected market size | |
projectionYear | String | Year of the projection | |
calculationMethod | String | How the size was calculated |
Market Growth Rate (marketGrowthRate)
| Attribute | Type | Description | Required |
|---|---|---|---|
currentRate | Number | Current growth rate, as a percentage | |
projectedRate | Number | Projected growth rate, as a percentage | |
timespan | String | Period the rate applies to |
Market Segmentation (marketSegmentation)
| Attribute | Type | Description | Required |
|---|---|---|---|
segmentName | String | Name of the segment | ✓ |
segmentDescription | String | Description of the segment | |
segmentSize | String | Size of the segment | |
segmentGrowth | String | Growth of the segment |
Competitive Intensity (competitiveIntensity)
| Attribute | Type | Description | Required |
|---|---|---|---|
level | Enum | Level of competition (shared four-point rating) | ✓ |
description | String | Description of the competitive landscape |
Related Markets (relatedMarkets)
| Attribute | Type | Description | Required |
|---|---|---|---|
marketID | String | ID of the related market | ✓ |
relationshipType | Enum | Nature of the relationship: overlapping, adjacent, parent, subMarket, substitute or complementary | ✓ |
relationshipStrength | Integer | Strength of the relationship (1 = lowest, 5 = highest) |
Enumeration Values
Competitive Intensity Level (competitiveIntensity → level)
The level uses the shared four-point rating from common.schema.json.
| Value | Description | Example |
|---|---|---|
low | Few competitors, limited rivalry | Niche markets |
medium | Some competition, stable dynamics | Mature markets |
high | Many competitors, intense rivalry | Commoditized markets |
critical | Extreme competition, rapid change | Tech markets |
Interpreting Market Growth Rate
marketGrowthRate.currentRate and projectedRate are numbers (percentages), not enumerated values. These bands are a reading guide only:
| Growth band | Description | Example |
|---|---|---|
| Declining | Negative growth | <0% CAGR |
| Flat | No growth | 0-2% CAGR |
| Growing | Moderate growth | 2-10% CAGR |
| High growth | Rapid expansion | 10-20% CAGR |
| Hypergrowth | Explosive growth | >20% CAGR |
Competitor Type (competitorType)
| Value | Description | Example |
|---|---|---|
direct | Same products, same market | Core competitors |
indirect | Different products, same need | Alternative providers |
substitute | Different offering that replaces the need for ours | Substitute products or services |
emerging | New market entrants | Startups, disruptors |
potential | Could enter market | Adjacent players |
Competitive Position Elements
Competitive Position (competitivePosition)
| Attribute | Type | Description | Required |
|---|---|---|---|
positionID | String | Unique identifier for the competitive position | ✓ |
competitorName | String | Name of the competitor | ✓ |
description | String | Competitive position description | ✓ |
orgUnitTitle | String | Organization unit responsible for monitoring this competitor | |
orgUnitID | String | ID of the organization unit named in orgUnitTitle | |
marketID | String | ID of the market this competitor operates in | ✓ |
competitorType | Enum | Classification of competitor | |
competitorStrength | Integer | Overall strength (1-5) | |
marketShare | Object | Market share data: value (percentage), year, trend (increasing, stable, decreasing, fluctuating) | |
valueProposition | String | Competitor's value proposition | |
targetCustomers | Array[String] | Primary customer segments | |
competitiveAdvantages | Array[Object] | Areas of strength: advantage (required), impactLevel (1-5), domain | |
competitiveDisadvantages | Array[Object] | Areas of weakness: disadvantage (required), exploitability (1-5), domain | |
strategicDirection | String | Observed strategic direction | |
recentActions | Array[Object] | Notable competitor movements: date and description (both required), significance (1-5) | |
responseStrategies | Array[String] | Our response approaches | |
benchmarkMetrics | Array[Object] | Comparative metrics: metricName (required), competitorValue, organizationValue | |
monitoringFrequency | Enum | Assessment frequency (shared frequency list, e.g. monthly, quarterly) | |
informationSources | Array[String] | Intelligence sources | |
lastUpdated | Date | Date of last competitive assessment |
Market Trend Elements
Market Trend (marketTrend)
| Attribute | Type | Description | Required |
|---|---|---|---|
trendID | String | Unique identifier for the market trend | ✓ |
trendTitle | String | Name of the trend | ✓ |
description | String | Detailed explanation | ✓ |
orgUnitTitle | String | Organization unit responsible for monitoring this trend | |
orgUnitID | String | ID of the organization unit named in orgUnitTitle | |
marketID | String | ID of the market this trend affects | ✓ |
trendTimeframe | Object | Expected duration and timeline: emergenceDate, maturityEstimate, duration (shared time horizon) | |
trendImpact | Object | Potential impact on organization: impactLevel (minimal … disruptive), opportunityScore and threatScore (1-5) | |
trendEvidence | Array[Object] | Supporting data and observations: evidenceType and source (both required), date | |
trendUncertainty | Object | Level of certainty about the trend: uncertaintyLevel (low, medium, high), uncertaintyFactors | |
affectedDomains | Array[Object] | Business domains impacted: domainType (required), impactDescription, impactSeverity (1-5) | |
responseStrategies | Array[Object] | Approaches to addressing the trend: strategyName (required), implementationStatus | |
trendMonitoring | Object | How the trend is tracked: monitoringMethod, frequency | |
triggerPoints | Array[Object] | Events that would accelerate response: triggerDescription (required), likelihood | |
relatedTrends | Array[Object] | Connected trends: trendID and relationshipType (both required; reinforcing, counteracting, enabling, dependent), relationshipStrength (1-5) | |
lastUpdated | Date | Date of last trend assessment |
Industry Analysis Elements
Industry Analysis (industryAnalysis)
| Attribute | Type | Description | Required |
|---|---|---|---|
industryID | String | Unique identifier for the industry analysis | ✓ |
industryName | String | Name of the industry | ✓ |
description | String | Detailed description of the industry | ✓ |
orgUnitTitle | String | Organization unit responsible for industry analysis | |
orgUnitID | String | ID of the organization unit named in orgUnitTitle | |
marketID | String | ID of the related market | |
industryMaturity | Enum | Current lifecycle stage (shared adoption stage: emerging, growth, mature, declining, legacy, sunset) | |
industryStructure | Object | Key structural characteristics: concentration, majorPlayers | |
powerBalance | Object | Balance of power in the value chain: dominantParty, powerDynamics | |
profitabilityDrivers | Array[Object] | Factors driving industry profitability: driver (required), effectDirection (veryNegative … veryPositive), trend | |
disruptionPotential | Object | Likelihood of industry disruption: disruptionLevel, disruptionSources | |
entryBarriers | Array[Object] | Obstacles to new market entrants: barrier (required), strength, trend | |
substitutionThreats | Array[Object] | Threat of substitute products or services: substitute (required), threatLevel, switchingCosts | |
supplierLeverage | Object | Power of suppliers in the industry: overallLeverage, concentration | |
customerLeverage | Object | Power of customers in the industry: overallLeverage, switchingCosts | |
regulatoryLandscape | Object | Regulatory factors affecting the industry: regulatoryBurden, keyRegulations | |
innovationDynamics | Object | Innovation patterns in the industry: innovationRate (slow, moderate, rapid), innovationFocus | |
industryOutlook | Object | Future outlook for the industry: shortTermOutlook, mediumTermOutlook, longTermOutlook | |
opportunitiesAndThreats | Object | Industry-specific opportunities and threats | |
strategicImplications | String | Strategic implications of this industry analysis | |
lastUpdated | Date | Date of last industry analysis update |
A profitability driver's direction of effect is effectDirection (not impact), because its values describe a direction from veryNegative to veryPositive rather than a magnitude.
Domain Relationships
The Market domain integrates with other metamodel domains:
| Target Domain | Relationship Type | Description |
|---|---|---|
| Strategy | Input | Market analysis informs strategy |
| Customer | Context | Markets contain customer segments |
| Products | Positioning | Products positioned in markets |
| Services | Positioning | Services positioned in markets |
| Capabilities | Alignment | Capabilities aligned to market needs |
| Performance | Measurement | Market KPIs tracked |
| Organization | Responsibility | Org units manage market intelligence |
| Information | Intelligence | Market data as information asset |
| Initiatives | Response | Initiatives respond to market changes |
| Risk | Exposure | Market risks identified |
Examples
Example 1: Enterprise Cloud Software Market
{
"marketID": "MKT-ENTSW-001",
"title": "Enterprise Cloud Software Market",
"description": "The market for cloud-based enterprise software solutions, including SaaS, PaaS, and IaaS offerings targeting medium to large organizations.",
"marketDefinition": "Cloud-based software solutions designed for organizations with 500+ employees, providing business functionality through subscription models with minimal onpremises infrastructure.",
"orgUnitTitle": "Market Intelligence Division",
"orgUnitRoles": [
"Market Research Manager",
"Competitive Analyst",
"Industry Specialist"
],
"marketSize": {
"currentSize": "$457 billion",
"currency": "USD",
"year": "2024",
"projectedSize": "$892 billion",
"projectionYear": "2028",
"calculationMethod": "Revenue-based analysis of public and private cloud software providers"
},
"marketGrowthRate": {
"currentRate": 18.2,
"projectedRate": 16.7,
"timespan": "Annual"
},
"marketSegmentation": [
{
"segmentName": "Enterprise Resource Planning",
"segmentDescription": "Finance, HR, and operational management solutions",
"segmentSize": "$125 billion",
"segmentGrowth": "12.5%"
},
{
"segmentName": "Customer Relationship Management",
"segmentDescription": "Sales, marketing, and service management solutions",
"segmentSize": "$96 billion",
"segmentGrowth": "15.8%"
},
{
"segmentName": "Business Intelligence & Analytics",
"segmentDescription": "Data analysis and visualization tools",
"segmentSize": "$84 billion",
"segmentGrowth": "22.3%"
}
],
"marketTrends": [
"Rapid adoption of AI capabilities across all enterprise software categories",
"Increased focus on vertical-specific solutions and industry clouds",
"Growing importance of API-first architecture and integration capabilities",
"Shift toward composable business applications and microservices"
],
"marketBarriers": [
"High switching costs for core enterprise systems",
"Data security and sovereignty requirements",
"Integration complexity with legacy systems",
"Procurement processes favoring incumbent providers"
],
"competitiveIntensity": {
"level": "high",
"description": "Mature incumbents face pressure from nimble cloud-native providers and platform expansion from tech giants"
},
"regulatoryFactors": [
"Data privacy regulations (GDPR, CCPA, etc.) influencing architectural decisions",
"Industry-specific compliance requirements creating market niches",
"Antitrust scrutiny of platform providers affecting integration strategies"
],
"technologicalFactors": [
"AI/ML capabilities becoming table stakes across all categories",
"Container-based architectures enabling multi-cloud deployments",
"Low-code/no-code capabilities expanding addressable market",
"Edge computing changing deployment models for certain use cases"
],
"economicFactors": [
"Subscription models creating predictable revenue streams",
"Economic uncertainty driving focus on provable ROI",
"Digital transformation investments remaining priority despite budget constraints",
"Consolidation of vendors through mergers and acquisitions"
],
"socialFactors": [
"Remote and hybrid work driving demand for collaborative capabilities",
"Employee experience becoming key purchase criterion",
"Growing emphasis on sustainability tracking and reporting",
"Changing demographics of decision-makers favoring digital-native solutions"
],
"environmentalFactors": [
"Cloud migration reducing on-premises data center footprints",
"Growing demand for carbon footprint tracking capabilities",
"Supplier sustainability becoming procurement criterion"
],
"strategicOpportunities": [
"Industry-specific AI capabilities to drive differentiation",
"Composable enterprise applications addressing flexibility requirements",
"Mid-market expansion with simplified implementation approaches",
"Integration platforms connecting best-of-breed solutions"
],
"strategicThreats": [
"Platform consolidation reducing independent software vendor opportunities",
"Commoditization of core functionality through standard APIs",
"Pricing pressure from open-source alternatives",
"Talent shortages limiting implementation capacity"
],
"strategicAlignment": "This market analysis supports our strategic pivot to industryfocused cloud solutions and expansion of our AI capabilities across the product portfolio.",
"performanceIndicators": [
{
"metricName": "Market Share",
"metricDescription": "Percentage of total market revenue",
"currentValue": "3.8%",
"targetValue": "5.2%",
"unit": "Percentage"
},
{
"metricName": "Competitive Win Rate",
"metricDescription": "Percentage of competitive deals won",
"currentValue": "42%",
"targetValue": "55%",
"unit": "Percentage"
}
],
"dependencies": [
{
"dependencyType": "critical",
"domainType": "capability",
"entityID": "CAP-AI-001",
"description": "AI/ML Development and Implementation capability"
},
{
"dependencyType": "important",
"domainType": "information",
"entityID": "INFO-MARKET-003",
"description": "Competitive Intelligence Database"
}
],
"relatedMarkets": [
{
"marketID": "MKT-CLOUD-002",
"relationshipType": "overlapping",
"relationshipStrength": 4
}
],
"improvementOpportunities": [
"Enhanced tracking of emerging competitors",
"More granular segment-specific growth analysis",
"Better integration of customer feedback into market intelligence"
]
}
Competitive position in this market
A competitor is recorded as a separate competitivePosition element that references the market by marketID.
{
"positionID": "CP-SFCRM-001",
"competitorName": "Salesforce",
"description": "Market leader in cloud CRM with expanding platform capabilities",
"marketID": "MKT-ENTSW-001",
"competitorType": "direct",
"competitorStrength": 5,
"marketShare": {
"value": 19.5,
"year": "2024",
"trend": "increasing"
},
"valueProposition": "Integrated customer 360 platform with industry-specific solutions",
"competitiveAdvantages": [
{
"advantage": "Platform ecosystem",
"impactLevel": 5,
"domain": "Technology"
},
{
"advantage": "Brand recognition",
"impactLevel": 4,
"domain": "Marketing"
}
],
"competitiveDisadvantages": [
{
"disadvantage": "Pricing complexity",
"exploitability": 3,
"domain": "Price"
}
],
"strategicDirection": "Expanding into adjacent markets through acquisitions and platform extensions",
"monitoringFrequency": "monthly"
}
Example 2: Rail Transportation Services Market
{
"marketID": "MKT-RAIL-001",
"title": "North American Rail Transportation Market",
"description": "Freight and passenger rail transportation services in North America",
"marketDefinition": "Rail transportation services including freight hauling, intermodal, and passenger rail",
"orgUnitTitle": "Strategic Planning Division",
"marketSize": {
"currentSize": "$82 billion",
"projectedSize": "$95 billion",
"projectionYear": "2028"
},
"marketGrowthRate": {
"currentRate": 3.2,
"projectedRate": 3.8
},
"marketTrends": [
"Shift from truck to rail for environmental sustainability",
"Precision scheduled railroading optimization",
"Technology-enabled predictive maintenance",
"Intermodal growth driven by e-commerce"
],
"regulatoryFactors": [
"Federal Railroad Administration safety requirements",
"Environmental regulations on emissions",
"Surface Transportation Board rate oversight"
],
"strategicAlignment": "Supports infrastructure modernization and safety excellence goals"
}
Implementation Guidelines
Market Analysis Best Practices
- Define boundaries clearly — Establish unambiguous market definitions
- Monitor continuously — Track market changes in real-time
- Validate with data — Base insights on quantitative evidence
- Connect to strategy — Link market intelligence to strategic decisions
- Update regularly — Refresh analysis on defined schedules
Porter's Five Forces Analysis
PESTLE Analysis Framework
| Factor | Description | Example Indicators |
|---|---|---|
| Political | Government policies, stability | Regulatory changes, trade policy |
| Economic | Economic conditions | GDP growth, interest rates |
| Social | Social trends, demographics | Consumer behavior, workforce |
| Technological | Technology changes | Innovation, digital disruption |
| Legal | Legal requirements | Compliance, litigation |
| Environmental | Environmental factors | Sustainability, climate |
OpenMetadata Integration
When integrating with OpenMetadata, map Market entities as follows:
| Triodian Element | OpenMetadata Entity | Notes |
|---|---|---|
| Market Segment | Glossary Term | Market vocabulary |
| Competitor | Custom Entity | Competitor records |
| Market Metrics | Dashboard | Market KPI dashboards |
| Trend Data | Table | Time-series market data |
| Market Size | Metric | Market size calculations |
# Example: Map Market to OpenMetadata Glossary
def create_market_glossary(market):
"""
Map Triodian Market to OpenMetadata Glossary
"""
terms = []
# Create main market term
market_term = {
"name": market["marketID"].lower(),
"displayName": market["title"],
"description": market["description"],
"glossary": "markets",
"tags": [
{"tagFQN": f"CompetitiveIntensity.{market.get('competitiveIntensity', {}).get('level', 'unknown')}"}
],
"owner": {"name": market.get("orgUnitTitle", ""), "type": "team"}
}
terms.append(market_term)
# Create segment terms
for segment in market.get("marketSegmentation", []):
segment_term = {
"name": segment["segmentName"].lower().replace(" ", "_"),
"displayName": segment["segmentName"],
"description": segment.get("segmentDescription", ""),
"glossary": "markets",
"parent": market["marketID"].lower()
}
terms.append(segment_term)
return terms
Schema Reference
- Repository:
Triodian/Triodian_Metamodel - Schema: market.schema.json
- Specification: JSON Schema Draft-07
- License: Apache License 2.0
Previous: Customer Domain | Next: Finance Domain