Products Domain

The Products domain encompasses tangible and intangible offerings created by an organization to address customer needs and deliver value. This domain integrates products into business architecture, connecting them with capabilities, value streams, policies, and stakeholders across the enterprise ecosystem.

Schema: product.schema.json
Specification: JSON Schema Draft-07

Overview

What is a Product?

A product represents any tangible or intangible offering that an organization creates, develops, or provides to deliver value to customers, stakeholders, or markets. Products can range from:

• Physical goods — Hardware, equipment, manufactured items
• Software applications — Desktop apps, mobile apps, web platforms
• Services — Consulting, maintenance, support offerings
• Reports and data — Analytics dashboards, datasets, business reports
• Intellectual property — Patents, licenses, proprietary technologies

In the context of enterprise architecture, products serve as key value delivery mechanisms that connect organizational capabilities with customer needs.

Purpose and Value

The Products domain enables architects and planners to:

• Track product portfolio by documenting all offerings in a structured format
• Manage lifecycle from concept through retirement
• Connect to capabilities by linking products to enabling capabilities
• Measure performance through embedded metrics and KPIs
• Support governance by linking products to compliance requirements

For Data Engineers

The Products domain maps directly to data product concepts:

• Product → Data Product in your catalog
• Product Features → Data product capabilities
• Target Market → Data consumers and use cases
• Quality Metrics → Data quality dimensions
• Lifecycle Stage → Data product maturity

Domain Attributes

Core Attributes

Attribute	Type	Description	Required
productID	String	Unique identifier for the Product, e.g. PROD-001	✓
title	String	Name or title of the Product	✓
description	String	Detailed explanation of what the Product entails	✓
purpose	String	Intended purpose or function within the Organization	✓
owner	String	Individual or team responsible for the Product	✓
orgUnitTitle	String	Organization unit(s) to which the Product is linked
orgUnitID	String	ID of the organization unit (see orgUnitTitle)
productCategory	Enum	Broad categorization of product type
productType	Enum	Specific type of product
targetMarket	Enum	Primary market or customer segment
businessModel	Enum	Revenue or value delivery model
lifecycleStage	Enum	Current stage in product lifecycle
lifecycleManagement	String	Strategies for managing from inception to retirement
marketCompetitiveness	String	Analysis of how the Product compares with competitors
customerFeedback	String	Data on customer satisfaction and Product performance
userBase	String	Description of current user base
usage	String	How the product is typically used
dependencies	String	Other products, processes, or systems required
relatedProducts	String	Products that are related or linked
relatedProductIDs	Array[String]	IDs of related Products (unique)
integrations	String	Systems or platforms the product integrates with
technologyStack	String	Underlying technologies used
performanceIndicators	String	Metrics used to measure success and performance
qualityMetrics	String	Quality assessment measures
adoptionMetrics	String	Usage and adoption measurements
revenueModel	String	How the product generates revenue or value
costs	String	Development, maintenance, and operational costs
pricingStrategy	Enum	Pricing approach
channels	Array[Enum]	Distribution and delivery channels
customerSegments	Array[Enum]	Types of customer the product targets
customerSegmentIDs	Array[String]	IDs of the specific customer segments the product targets (records in the Customer domain; unique)
valueProposition	String	Core value delivered to customers
competitiveAdvantage	String	What differentiates from competitors
risks	String	Potential risks associated with the Product
riskCategories	Array[Enum]	Categories of risks
complianceRequirements	Array[Enum]	Regulatory and compliance needs
securityRequirements	String	Security and privacy requirements
improvementOpportunities	String	Areas for enhancement or improvement
roadmap	String	Future development plans
strategicAlignment	String	Alignment with organizational goals
sustainability	String	Environmental and sustainability considerations
accessibility	String	Accessibility features and compliance
localization	String	Multi-language and regional adaptations
productFeatures	Array[Object]	Specific features of the product (see Product Feature)

Strategic Empathy Attributes

These optional flags record whether a product's design accounts for the people who use it and are affected by it.

Attribute	Type	Description	Required
userEmpathyMappingIntegrated	Boolean	Whether empathy maps and user personas are used consistently in product development
ethicalAIByDesign	Boolean	For AI-driven products, whether ethical considerations and potential empathetic impacts are designed in
accessibilityFeatures	Boolean	Whether the product includes features addressing diverse user needs and challenges

A product record must have productID, title, description, purpose and owner, and may not carry fields other than those listed above. Name-only links (orgUnitTitle, relatedProducts) can be paired with their ID fields (orgUnitID, relatedProductIDs).

Enumeration Values

Product Category (productCategory)

Value	Description	Example
physicalProduct	Tangible manufactured goods	Railway equipment, sensors, hardware devices
digitalProduct	Software and digital offerings	Mobile apps, web platforms, digital tools
serviceProduct	Service-based offerings	Consulting services, maintenance services
informationProduct	Data and knowledge products	Reports, datasets, analytics dashboards
platformProduct	Technology platforms	APIs, development platforms, marketplaces
hybridProduct	Combination of physical and digital	IoT devices with software, smart systems

Product Type (productType)

Value	Description	Example
hardware	Physical devices and equipment	Sensors, computers, machinery
software	Applications and programs	Desktop apps, mobile apps, web applications
platform	Technology platforms and frameworks	Development platforms, APIs, operating systems
saas	Software as a Service	Cloud-based applications, subscription software
report	Information and analysis reports	Business reports, compliance reports, dashboards
dataset	Structured data products	Databases, data feeds, analytics datasets
api	Application programming interfaces	REST APIs, GraphQL APIs, integration services
component	Reusable components	Software libraries, hardware components
system	Complete integrated systems	Enterprise systems, integrated solutions
tool	Specialized tools and utilities	Development tools, analysis tools
content	Digital content products	Documentation, training materials, multimedia
intellectualProperty	Patents, licenses, and IP	Patents, trademarks, licensed technologies

Target Market (targetMarket)

Value	Description	Example
internal	Internal organizational use	Employee tools, internal systems
external	External customer market	Customer-facing products
b2b	Business-to-business	Enterprise software, corporate services
b2c	Business-to-consumer	Consumer applications, retail products
b2g	Business-to-government	Government solutions, public sector
b2e	Business-to-employee	Employee benefit platforms, workforce apps
partner	Partner and channel market	Partner platforms, reseller tools
developer	Software developers	SDKs, developer APIs

Business Model (businessModel)

Value	Description	Example
oneTimePurchase	Single transaction purchase	Hardware, perpetual licenses
subscription	Recurring subscription model	SaaS, membership services
freemium	Free with premium options	Free tier with paid upgrades
usageBased	Pay-per-use pricing	API calls, storage usage
advertising	Ad-supported model	Free products with advertising
marketplace	Revenue from transactions between third parties	Commission on marketplace sales
licensing	Licensing model	Software licenses, IP licensing
openSource	Open source with optional services	Community edition with enterprise support
enterprise	Negotiated enterprise agreements	Site licences, enterprise contracts
channel	Sold through intermediaries	Reseller and distributor agreements
internalService	Provided to internal users as a funded service	Internal reports, shared platforms
internalTool	Tool built for internal use	Employee tools, operational utilities

Lifecycle Stage (lifecycleStage)

lifecycleStage accepts the shared delivery lifecycle list from common.schema.json (the first ten values) or one of the product-specific market lifecycle values (the last five).

Value	Description	Example
ideation	Idea being explored	Opportunity assessment
planning	Scope and approach being planned	Business case, roadmap
design	Being designed	Prototypes, specifications
development	Active development	Building and testing
implementation	Being implemented or rolled out	Pilot deployment
launch	Market introduction	Go-to-market, initial release
operational	In normal operation	Live product in steady use
enhancement	Being extended with new features	Major feature release
optimization	Being tuned for performance or cost	Cost reduction, performance work
retirement	End of life	Decommissioning, migration
concept	Initial ideation phase	New product ideas, market research
growth	Market adoption and scaling	User acquisition, feature expansion
maturity	Stable market position	Maintenance, optimization
decline	Decreasing market relevance	Reduced investment, sunset planning
maintenance	Kept running with minimal change	Bug fixes, security patches

Pricing Strategy (pricingStrategy)

Value	Description	Example
costPlus	Cost plus margin pricing	Manufacturing + markup
valueBased	Pricing based on perceived value	Premium positioning
competitive	Pricing based on competition	Market rate matching
penetration	Low price for market entry	Initial discount pricing
skimming	High initial price, later reduced	Premium launch, later discounts
freemium	Free basic tier, paid premium tier	Free plan with paid upgrades
dynamic	Price varies with demand or conditions	Time-of-day or demand-based pricing
bundle	Sold as part of a package	Product suites
usageBased	Price follows consumption	Per API call, per gigabyte

Distribution Channels (channels)

Value	Description
directSales	Direct sales team
onlinePlatform	E-commerce and web sales
partnerChannel	Resellers and partners
retail	Physical retail locations
mobileApp	Mobile apps and app stores
api	APIs, API platforms and developer portals
subscriptionService	Delivered as part of a subscription
marketplace	Third-party marketplaces, including API marketplaces
internalDistribution	Distributed within the organization

Customer Segments (customerSegments)

customerSegments lists the types of customer a product targets. Named segments, such as "Railway Operators", are records in the Customer domain; reference them by ID in customerSegmentIDs.

Value	Description
enterprise	Large enterprise customers
smb	Small and medium businesses
government	Government and public sector
consumer	Individual consumers
developer	Software developers
partner	Channel partners
startup	Early-stage companies
education	Schools, universities and training providers
healthcare	Healthcare providers and organizations
financial	Banks, insurers and other financial institutions
internal	Users within the organization (internal products)

Product Feature Elements

Each entry in productFeatures is a product feature: a specific capability, function or characteristic of the product that delivers value.

Product Feature (productFeature)

Attribute	Type	Description	Required
title	String	Name or title of the feature	✓
description	String	Detailed explanation of the feature	✓
purpose	String	Intended purpose or benefit of the feature	✓
owner	String	Individual or team responsible for the feature
orgUnitTitle	String	Organization unit(s) involved in the feature
orgUnitID	String	ID of the organization unit (see orgUnitTitle)
featureType	Enum	Type of feature (see below)
priority	Enum	Development and business priority: shared priority list (low, medium, high, critical)
complexity	Enum	Technical complexity: shared complexity list (simple, moderate, complex, highlyComplex)
userStories	String	User stories or use cases related to the feature
acceptanceCriteria	String	Criteria for accepting the feature
technicalSpecifications	String	Technical details and requirements of the feature
dependencies	String	Technical or business dependencies
integrationRequirements	String	Integration needs with other systems
performanceRequirements	String	Performance benchmarks and standards
securityRequirements	String	Security specifications
usabilityRequirements	String	User experience and usability needs
testingRequirements	String	Testing and quality assurance needs
releasePlan	String	Plan for releasing the feature, including target versions
rolloutStrategy	Enum	Feature rollout approach (see below)
targetAudience	String	Specific users or groups for the feature
businessValue	String	Business value and impact
successMetrics	String	Metrics to measure feature success
feedback	String	User feedback and feature reception
maintenanceRequirements	String	Ongoing maintenance and support needs
documentationRequirements	String	Documentation and training needs

A product feature must have title, description and purpose, and may not carry other fields.

Feature Type (featureType)

Value	Description
coreFeature	Essential functionality of the product
premiumFeature	Functionality offered at a higher tier
addOn	Optional extension sold or enabled separately
integration	Connection to another system or platform
customization	Configuration or tailoring for a customer
enhancement	Improvement to existing functionality

Rollout Strategy (rolloutStrategy)

Value	Description
bigBang	Released to all users at once
phased	Released in planned stages
canary	Released to a small group first to detect problems
beta	Released to volunteer or selected testers
geographic	Released region by region
segment	Released to one customer segment at a time

Domain Relationships

The Products domain integrates with other metamodel domains:

Target Domain	Relationship Type	Description
Capabilities	Enablement	Capabilities enable product delivery
Services	Realization	Services may realize products
Customer	Consumption	Customers consume products
Value Stream	Delivery	Products delivered through value streams
Information	Content	Products contain or produce information
Technology	Implementation	Technology implements products
Channel	Distribution	Channels distribute products
Market	Positioning	Market position drives product strategy
Performance	Measurement	Performance metrics measure product success
Policy	Compliance	Products comply with policies

Examples

Example 1: Information Product

{
  "productID": "PROD-001",
  "title": "Track Quality Index Report",
  "description": "Monthly analysis of track geometry and maintenance metrics across the rail network",
  "purpose": "Track maintenance planning and quality assurance decision support",
  "owner": "Track Quality Analysis Team",
  "orgUnitTitle": "Track Maintenance Division",
  "productCategory": "informationProduct",
  "productType": "report",
  "targetMarket": "internal",
  "businessModel": "internalService",
  "lifecycleStage": "maturity",
  "lifecycleManagement": "Monthly updates, annual review process",
  "marketCompetitiveness": "Industry-leading accuracy of 98.5%",
  "customerFeedback": "User satisfaction: 4.2/5.0",
  "userBase": "500 active users across 12 departments",
  "usage": "Daily reporting, weekly analysis, monthly planning",
  "dependencies": "Track measurement systems, analysis software",
  "relatedProducts": "Rail Wear Report, Bridge Condition Index",
  "integrations": "ERP system, mobile apps, third-party analytics",
  "technologyStack": "Python, PostgreSQL, React, AWS cloud infrastructure",
  "performanceIndicators": "Accuracy: 98.5%, Timeliness: 99%",
  "qualityMetrics": "Defect rate: 0.1%, Customer satisfaction: 4.2/5",
  "adoptionMetrics": "Monthly active users: 450, Feature adoption: 78%",
  "revenueModel": "Internal cost center allocation",
  "costs": "Development: $200K, Annual maintenance: $50K",
  "valueProposition": "Reduce maintenance costs by 30% through predictive analytics",
  "competitiveAdvantage": "Real-time processing with 99.9% accuracy",
  "risks": "Data quality issues, reporting delays",
  "riskCategories": [
    "technology",
    "operational"
  ],
  "complianceRequirements": [
    "industryStandards"
  ],
  "securityRequirements": "Data encryption, access controls, audit trails",
  "improvementOpportunities": "Add predictive analytics, mobile access",
  "roadmap": "Q2: Mobile app, Q4: AI-powered insights",
  "strategicAlignment": "Supports track safety and efficiency goals",
  "sustainability": "Cloud-hosted to reduce energy consumption",
  "accessibility": "WCAG 2.1 compliant, screen reader support",
  "localization": "Available in English, Spanish, French",
  "productFeatures": [
    {
      "title": "Interactive Dashboard",
      "description": "Real-time visualization of track quality metrics",
      "purpose": "Enable quick identification of problem areas",
      "owner": "Dashboard Development Team",
      "featureType": "coreFeature",
      "priority": "critical",
      "releasePlan": "Released in version 2.0"
    },
    {
      "title": "Predictive Maintenance Alerts",
      "description": "AI-powered predictions for maintenance needs",
      "purpose": "Proactive maintenance scheduling",
      "owner": "AI Analytics Team",
      "featureType": "enhancement",
      "priority": "high",
      "complexity": "complex",
      "releasePlan": "In development for version 3.0",
      "rolloutStrategy": "phased"
    }
  ]
}

Example 2: Digital Platform Product

{
  "productID": "PROD-005",
  "title": "Customer Analytics Platform",
  "description": "Self-service analytics platform for customer behavior analysis and segmentation",
  "purpose": "Enable data-driven customer insights across the organization",
  "owner": "Chief Data Officer",
  "orgUnitTitle": "Data and Analytics Division",
  "productCategory": "digitalProduct",
  "productType": "platform",
  "targetMarket": "internal",
  "businessModel": "subscription",
  "lifecycleStage": "growth",
  "customerSegments": [
    "internal"
  ],
  "channels": [
    "onlinePlatform",
    "api"
  ],
  "valueProposition": "Democratize customer insights with self-service analytics",
  "competitiveAdvantage": "Pre-built customer analytics models with 2-minute insights",
  "pricingStrategy": "valueBased",
  "performanceIndicators": "User adoption rate, query response time, insight generation",
  "qualityMetrics": "Data freshness: <1 hour, Uptime: 99.9%",
  "userEmpathyMappingIntegrated": true,
  "accessibilityFeatures": true
}

Implementation Guidelines

Product Modeling Best Practices

1. Start with value proposition — Define customer value before features
2. Track lifecycle stage — Update regularly as product matures
3. Connect to capabilities — Link products to enabling capabilities
4. Measure what matters — Include relevant performance metrics
5. Plan for retirement — Include sunset criteria from the start

Product Portfolio View

OpenMetadata Integration

For Data Platform Teams

When integrating with OpenMetadata, map Product entities as follows:

Triodian Element	OpenMetadata Entity	Notes
Information Product	Data Product	Direct mapping for data products
Product	Dashboard /Pipeline	For analytics products
Product Features	Data Product Properties	Capabilities of data product
Target Market	Consumers	Who uses the product
Quality Metrics	Data Quality Tests	Product quality measures
Lifecycle Stage	Custom Property	Track product maturity

# Example: Create OpenMetadata Data Product from Triodian Product
def create_om_data_product(product):
    """
    Map Triodian Product to OpenMetadata Data Product
    """
    return {
        "name": product["title"].lower().replace(" ", "_"),
        "displayName": product["title"],
        "description": product["description"],
        "fullyQualifiedName": f"dataproduct.{product['title'].lower().replace(' ', '_')}",
        "owner": {
            "name": product["owner"],
            "type": "user"
        },
        "domain": product.get("orgUnitTitle", ""),
        "assets": [],  # Link to tables, dashboards, pipelines
        "experts": [],
        "tags": [
            {"tagFQN": f"ProductCategory.{product['productCategory'].replace(' ', '')}"},
            {"tagFQN": f"Lifecycle.{product['lifecycleStage']}"}
        ],
        "extension": {
            "valueProposition": product.get("valueProposition"),
            "targetMarket": product.get("targetMarket"),
            "businessModel": product.get("businessModel")
        }
    }

Schema Reference

• Repository: Triodian/Triodian_Metamodel
• Schema: product.schema.json
• Specification: JSON Schema Draft-07
• License: Apache License 2.0

---

Previous: Strategy Domain | Next: Services Domain