Value Stream Domain

The Value Stream domain represents end-to-end activities that create value for customers or internal stakeholders. It provides a dynamic, interconnected view of how value flows through the organization, with links to capabilities, information, and stakeholder expectations.

Schema: value-stream.schema.json
Specification: JSON Schema Draft-07

Overview

What is a Value Stream?

A value stream represents the complete sequence of activities required to deliver a product, service, or outcome that provides value to a customer or stakeholder. Value streams:

Span organizational boundaries — Cross functions and departments
Focus on customer value — Measure success by value delivered
Enable optimization — Identify waste and improvement opportunities
Connect capabilities — Link organizational capabilities to outcomes

The domain integrates performance metrics at each stage, creating a continuous feedback loop for measurement and optimization.

Purpose and Value

The Value Stream domain enables architects and planners to:

Map end-to-end flows from trigger to value delivery
Identify bottlenecks and optimization opportunities
Connect capabilities to value by linking what we do to why it matters
Measure value delivery through stage-level metrics
Align stakeholder expectations with delivery activities

For Data Engineers

The Value Stream domain maps directly to data pipeline concepts:

Value Stream → Data Pipeline /ETL Flow
Value Stream Stage → Pipeline Stage /Transform Step
Inputs/Outputs → Source /Target data
Performance Indicators → Pipeline metrics (latency, throughput)
Enabling Capability → Processing capability

Core Components

The Value Stream domain uses a hierarchical structure:

Value Stream: End-to-end flow delivering value
Value Stream Stages: Sequential steps transforming inputs to outputs
Value Items: Specific outputs or benefits generated
Enabling Capabilities: Capabilities that enable each stage

Domain Attributes

Value Stream Attributes

Attribute	Type	Description	Required
`valueStreamID`	String	Unique identifier for the Value Stream, e.g. `VS-001`	✓
`title`	String	Name or title of the Value Stream
`description`	String	Detailed explanation of the Value Stream, including what triggers it and the end state that delivers value
`purpose`	String	Intended purpose or function within the Organization, including the value delivered and to whom
`owner`	String	Individual or team responsible
`orgUnitTitle`	String	Organization unit(s) linked
`orgUnitID`	String	ID of the organization unit named in `orgUnitTitle`
`performanceIndicators`	String	Metrics for effectiveness and efficiency, including end-to-end cycle time
`dependencies`	String	Capabilities, processes, or systems depended on
`relatedValueStreams`	String	Related or linked value streams
`relatedValueStreamIDs`	Array[String]	IDs of related value streams
`maturityLevel`	Enum	Current maturity level (shared maturity list, see below)
`toolsAndTechnologies`	String	Tools and technologies used
`complianceAndStandards`	String	Regulatory requirements and standards the Value Stream must adhere to
`cost`	String	Financial cost for implementing and maintaining
`risks`	String	Potential risks associated with the Value Stream
`improvementOpportunities`	String	Areas for enhancement
`strategicAlignment`	String	Alignment with strategic goals

Value Stream Stage (`valueStreamStage`)

Attribute	Type	Description	Required
`stageID`	String	Unique identifier for the stage, e.g. `VS-001-S1`	✓
`stageTitle`	String	Name/title of the stage
`parentValueStream`	String	Value Stream it belongs to
`parentValueStreamID`	String	ID of the Value Stream it belongs to
`description`	String	What the stage entails
`valueItems`	String	Specific outputs or benefits generated
`purpose`	String	Intended function within the Value Stream
`owner`	String	Responsible individual/team
`orgUnitTitle`	String	Associated Organization unit(s)
`orgUnitID`	String	ID of the organization unit named in `orgUnitTitle`
`inputs`	String	Required resources/information, including information assets used
`outputs`	String	Deliverables/results produced, including information assets produced
`performanceIndicators`	String	Metrics for effectiveness/efficiency, including stage cycle time and wait time
`dependencies`	String	Other stages/systems it depends on, including the preceding stage
`relatedValueStreamStages`	String	Connected stages
`relatedStageIDs`	Array[String]	IDs of connected stages
`risks`	String	Potential risks
`improvementOpportunities`	String	Areas for enhancement
`strategicAlignment`	String	Alignment with Organization goals
`enablingCapability`	String	Capability that enables this stage
`enablingCapabilityID`	String	ID of the Capability that enables this stage

Enumeration Values

Maturity Level (`maturityLevel`)

Value	Description	Example
`initial`	Ad-hoc, inconsistent	No standard process
`repeatable`	Basic processes emerging	Some documentation
`defined`	Standardized processes	Documented procedures
`managed`	Quantitatively controlled	Metrics-driven
`optimizing`	Continuous improvement	Predictive optimization

Domain Relationships

The Value Stream domain integrates with other metamodel domains:

Target Domain	Relationship Type	Description
Organization	Ownership	Organization units own and execute value streams
Capabilities	Enablement	Capabilities enable value stream stages
Information	Flow	Information flows through value streams
Products	Delivery	Value streams deliver products
Services	Delivery	Value streams deliver services
Customer	Value	Value streams create value for customers
Performance	Measurement	Performance metrics track value stream effectiveness
Stakeholder	Benefit	Stakeholders benefit from value stream outputs
Policy	Compliance	Value streams comply with policies
Initiatives	Improvement	Initiatives improve value streams

Examples

A value stream and its stages are separate records. Each stage names its value stream in parentValueStream and parentValueStreamID; the order of the stages is carried by each stage's dependencies on the one before it. Cycle and wait times are recorded in performanceIndicators.

Example 1: Track Inspection and Maintenance Value Stream

Value stream

{
  "valueStreamID": "VS-001",
  "title": "Track Inspection and Maintenance",
  "description": "End-to-end process for track inspection and maintenance activities ensuring rail safety and operational reliability. Triggered by: scheduled inspection cycle or reported track condition. Ends when: track certified safe for operation at designated speed.",
  "purpose": "Ensure track safety through efficient inspection and maintenance, giving rail operations, passengers and freight customers safe, reliable track that supports on-time operations",
  "owner": "Track Maintenance Program Director",
  "orgUnitTitle": "Track and Rail Infrastructure Division",
  "orgUnitID": "OU-001",
  "performanceIndicators": "Track quality index: 96.8%, Maintenance completion rate: 94.5%, On-time delivery: 97.2%, Cycle time: average 14 days from inspection to maintenance completion",
  "dependencies": "Track measurement systems, maintenance crews, equipment availability, weather conditions",
  "relatedValueStreams": "Signal system maintenance, bridge inspection process, equipment maintenance",
  "relatedValueStreamIDs": [
    "VS-010",
    "VS-011",
    "VS-012"
  ],
  "maturityLevel": "managed",
  "toolsAndTechnologies": "Track geometry cars, ultrasonic testing equipment, maintenance management software",
  "complianceAndStandards": "49 CFR Part 213 (FRA Track Safety Standards), internal safety standards",
  "cost": "Annual budget: $178M for inspection and maintenance activities",
  "risks": "Weather delays, equipment failures, workforce availability",
  "improvementOpportunities": "Implement predictive analytics, automate reporting processes, enhance mobile capabilities",
  "strategicAlignment": "Directly supports safety and infrastructure reliability strategic goals"
}

Stages

{
  "stageID": "VS-001-S1",
  "stageTitle": "Track Geometry Inspection",
  "parentValueStream": "Track Inspection and Maintenance",
  "parentValueStreamID": "VS-001",
  "description": "Automated measurement of track geometry parameters using track geometry vehicles",
  "valueItems": "Inspection reports, defect identification, safety certifications",
  "purpose": "Identify track geometry defects requiring maintenance",
  "owner": "Track Geometry Program Manager",
  "orgUnitTitle": "Track Inspection Division",
  "orgUnitID": "OU-004",
  "inputs": "Track class data, previous inspection results, maintenance history",
  "outputs": "Track geometry exception reports, maintenance recommendations",
  "performanceIndicators": "Inspection coverage: 98.2%, Defect identification accuracy: 96.5%, Cycle time: 2-3 days per territory",
  "dependencies": "Track geometry vehicle availability, weather conditions, track access windows",
  "relatedValueStreamStages": "Rail wear measurement, maintenance planning",
  "relatedStageIDs": [
    "VS-011-S2",
    "VS-012-S1"
  ],
  "risks": "Equipment malfunction, data transmission failures",
  "improvementOpportunities": "Real-time data analysis, automated work order generation",
  "strategicAlignment": "Supports track safety and maintenance efficiency objectives",
  "enablingCapability": "Automated Track Geometry Measurement",
  "enablingCapabilityID": "CAP-101"
}

{
  "stageID": "VS-001-S2",
  "stageTitle": "Defect Analysis and Prioritization",
  "parentValueStream": "Track Inspection and Maintenance",
  "parentValueStreamID": "VS-001",
  "description": "Analysis of inspection data to identify, classify, and prioritize maintenance needs",
  "purpose": "Determine maintenance priorities based on safety risk and operational impact",
  "owner": "Track Analysis Manager",
  "inputs": "Inspection reports, defect data, historical trends",
  "outputs": "Prioritized maintenance work orders, resource allocation plans",
  "performanceIndicators": "Analysis turnaround: 24 hours, Priority accuracy: 98%, Cycle time: 1-2 days",
  "dependencies": "Completion of stage 1 (Track Geometry Inspection)",
  "enablingCapability": "Track Condition Analysis",
  "enablingCapabilityID": "CAP-102"
}

{
  "stageID": "VS-001-S3",
  "stageTitle": "Maintenance Execution",
  "parentValueStream": "Track Inspection and Maintenance",
  "parentValueStreamID": "VS-001",
  "description": "Physical repair and maintenance of identified track defects",
  "purpose": "Restore track to safe operating condition",
  "owner": "Maintenance Operations Manager",
  "inputs": "Work orders, materials, equipment, crew schedules",
  "outputs": "Completed repairs, updated track records",
  "performanceIndicators": "First-time fix rate: 94%, SLA compliance: 97%, Cycle time: 3-7 days depending on defect severity",
  "dependencies": "Completion of stage 2 (Defect Analysis and Prioritization)",
  "enablingCapability": "Track Repair and Maintenance",
  "enablingCapabilityID": "CAP-103"
}

{
  "stageID": "VS-001-S4",
  "stageTitle": "Quality Verification",
  "parentValueStream": "Track Inspection and Maintenance",
  "parentValueStreamID": "VS-001",
  "description": "Post-maintenance inspection to verify repair quality and track safety",
  "purpose": "Certify track safe for operations at designated speed",
  "owner": "Quality Assurance Manager",
  "inputs": "Completed work records, verification inspection data",
  "outputs": "Safety certifications, track release authorization",
  "performanceIndicators": "Verification pass rate: 99.2%, Re-work rate: 0.8%, Cycle time: 1 day",
  "dependencies": "Completion of stage 3 (Maintenance Execution)",
  "enablingCapability": "Quality Verification and Certification",
  "enablingCapabilityID": "CAP-104"
}

Example 2: Customer Onboarding Value Stream

Value stream

{
  "valueStreamID": "VS-002",
  "title": "Customer Onboarding",
  "description": "End-to-end process for onboarding new customers from initial contact through active usage. Triggered by: customer signs contract or places first order. Ends when: customer actively using products/services and achieving value.",
  "purpose": "Successfully activate new customers so they realize value from products and services quickly, through a seamless onboarding experience",
  "owner": "Customer Success Director",
  "orgUnitTitle": "Customer Success Division",
  "orgUnitID": "OU-002",
  "performanceIndicators": "Onboarding completion rate: 94%, Time to first value: 14 days, Customer satisfaction: 4.5/5, Cycle time: average 21 days from contract to full activation",
  "maturityLevel": "defined"
}

Stages

{
  "stageID": "VS-002-S1",
  "stageTitle": "Welcome and Setup",
  "parentValueStream": "Customer Onboarding",
  "parentValueStreamID": "VS-002",
  "description": "Initial customer welcome, account setup, and access provisioning",
  "inputs": "Contract details, customer information",
  "outputs": "Active account, access credentials, welcome materials",
  "performanceIndicators": "Cycle time: 1-2 days"
}

{
  "stageID": "VS-002-S2",
  "stageTitle": "Configuration",
  "parentValueStream": "Customer Onboarding",
  "parentValueStreamID": "VS-002",
  "description": "Configure products/services to customer requirements",
  "inputs": "Customer requirements, configuration templates",
  "outputs": "Configured environment, custom settings",
  "performanceIndicators": "Cycle time: 3-5 days",
  "dependencies": "Completion of stage 1 (Welcome and Setup)"
}

{
  "stageID": "VS-002-S3",
  "stageTitle": "Training",
  "parentValueStream": "Customer Onboarding",
  "parentValueStreamID": "VS-002",
  "description": "Train customer users on product usage",
  "inputs": "Training materials, user list",
  "outputs": "Trained users, certification records",
  "performanceIndicators": "Cycle time: 5-7 days",
  "dependencies": "Completion of stage 2 (Configuration)"
}

{
  "stageID": "VS-002-S4",
  "stageTitle": "Go-Live Support",
  "parentValueStream": "Customer Onboarding",
  "parentValueStreamID": "VS-002",
  "description": "Support customer through initial production usage",
  "inputs": "Go-live checklist, support resources",
  "outputs": "Active production usage, resolved issues",
  "performanceIndicators": "Cycle time: 7-10 days",
  "dependencies": "Completion of stage 3 (Training)"
}

Example 3: Data Analytics Value Stream

Value stream

{
  "valueStreamID": "VS-003",
  "title": "Data Analytics Pipeline",
  "description": "End-to-end flow for transforming raw data into actionable business insights. Triggered by: data refresh schedule or ad-hoc analysis request. Ends when: insights delivered and consumed by business stakeholders.",
  "purpose": "Deliver timely, accurate analytics that give business stakeholders, executives and analysts data-driven insights for better decisions",
  "owner": "Chief Data Officer",
  "orgUnitTitle": "Data and Analytics Division",
  "orgUnitID": "OU-003",
  "performanceIndicators": "Data freshness: <4 hours, Report accuracy: 99.9%, User satisfaction: 4.3/5, Cycle time: 4 hours for standard reports, 2 days for ad-hoc analysis",
  "maturityLevel": "managed",
  "toolsAndTechnologies": "Spark, Airflow, Snowflake, Tableau, dbt"
}

Stages

{
  "stageID": "VS-003-S1",
  "stageTitle": "Data Ingestion",
  "parentValueStream": "Data Analytics Pipeline",
  "parentValueStreamID": "VS-003",
  "description": "Extract data from source systems into data lake",
  "inputs": "Source system connections, ingestion schedules",
  "outputs": "Raw data in data lake",
  "performanceIndicators": "Ingestion success rate: 99.8%, Latency: <30 minutes",
  "enablingCapability": "Data Ingestion Platform",
  "enablingCapabilityID": "CAP-105"
}

{
  "stageID": "VS-003-S2",
  "stageTitle": "Data Transformation",
  "parentValueStream": "Data Analytics Pipeline",
  "parentValueStreamID": "VS-003",
  "description": "Clean, transform, and model data for analysis",
  "inputs": "Raw data, transformation logic, business rules",
  "outputs": "Curated datasets, data models",
  "performanceIndicators": "Transform success rate: 99.5%, Data quality score: 98%",
  "dependencies": "Completion of stage 1 (Data Ingestion)",
  "enablingCapability": "Data Transformation Engine",
  "enablingCapabilityID": "CAP-106"
}

{
  "stageID": "VS-003-S3",
  "stageTitle": "Analytics Generation",
  "parentValueStream": "Data Analytics Pipeline",
  "parentValueStreamID": "VS-003",
  "description": "Generate reports, dashboards, and analytical outputs",
  "inputs": "Curated data, report definitions",
  "outputs": "Reports, dashboards, alerts",
  "performanceIndicators": "Report generation time: <5 minutes, Accuracy: 99.9%",
  "dependencies": "Completion of stage 2 (Data Transformation)",
  "enablingCapability": "Business Intelligence Platform",
  "enablingCapabilityID": "CAP-107"
}

{
  "stageID": "VS-003-S4",
  "stageTitle": "Insight Delivery",
  "parentValueStream": "Data Analytics Pipeline",
  "parentValueStreamID": "VS-003",
  "description": "Deliver insights to consumers through appropriate channels",
  "inputs": "Generated reports, distribution lists",
  "outputs": "Delivered insights, consumption metrics",
  "performanceIndicators": "Delivery success: 100%, User engagement: 78%",
  "dependencies": "Completion of stage 3 (Analytics Generation)",
  "enablingCapability": "Report Distribution System",
  "enablingCapabilityID": "CAP-108"
}

Implementation Guidelines

Value Stream Mapping Best Practices

Start with the customer — Define value from the customer perspective
Map end-to-end — Include all stages from trigger to value delivery
Identify waste — Look for delays, rework, and non-value activities
Measure flow — Track cycle time, wait time, and throughput
Link to capabilities — Connect stages to enabling capabilities

Value Stream Visualization

Lean Metrics

Track these key metrics for each value stream:

Metric	Description	Target
Lead Time	Total time from trigger to delivery	Minimize
Cycle Time	Active processing time	Minimize
Wait Time	Time waiting between stages	Eliminate
Throughput	Units processed per time period	Optimize
First-Pass Yield	Percentage completed without rework	Maximize

OpenMetadata Integration

For Data Platform Teams

When integrating with OpenMetadata, map Value Stream entities as follows:

Triodian Element	OpenMetadata Entity	Notes
Value Stream	Pipeline	Data processing pipeline
Value Stream Stage	Pipeline Task	Individual transform step
Inputs	Lineage Source	Input data assets
Outputs	Lineage Target	Output data assets
Performance Indicators	Pipeline Status	Execution metrics

# Example: Map value stream to OpenMetadata pipeline
def create_pipeline(value_stream, stages):
    """
    Map Triodian Value Stream to OpenMetadata Pipeline.
    stages are the Value Stream Stage records whose parentValueStreamID is this value stream, in order.
    """
    pipeline = {
        "name": value_stream["title"].lower().replace(" ", "_"),
        "displayName": value_stream["title"],
        "description": value_stream["description"],
        "pipelineType": "batch",
        "owner": {"name": value_stream["owner"], "type": "user"},
        "tags": [
            {"tagFQN": f"MaturityLevel.{value_stream.get('maturityLevel', 'defined')}"}
        ],
        "tasks": [],
        "extension": {
            "valueStreamID": value_stream["valueStreamID"],
            "orgUnitID": value_stream.get("orgUnitID"),
            "performanceIndicators": value_stream.get("performanceIndicators")
        }
    }
    
    # Add stages as tasks
    for stage in stages:
        task = {
            "name": stage["stageTitle"].lower().replace(" ", "_"),
            "displayName": stage["stageTitle"],
            "description": stage.get("description", ""),
            "taskType": "transformation",
            "downstreamTasks": [],
            "tags": []
        }
        pipeline["tasks"].append(task)
    
    # Link tasks sequentially
    for i, task in enumerate(pipeline["tasks"][:-1]):
        task["downstreamTasks"].append(pipeline["tasks"][i+1]["name"])
    
    return pipeline

Schema Reference

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

Previous: Policy Domain | Next: Technology Domain

Overview​

What is a Value Stream?​

Purpose and Value​

Core Components​

Domain Attributes​

Value Stream Attributes​

Value Stream Stage (valueStreamStage)​

Enumeration Values​

Maturity Level (maturityLevel)​

Domain Relationships​

Examples​

Example 1: Track Inspection and Maintenance Value Stream​

Example 2: Customer Onboarding Value Stream​

Example 3: Data Analytics Value Stream​

Implementation Guidelines​

Value Stream Mapping Best Practices​

Value Stream Visualization​

Lean Metrics​

OpenMetadata Integration​

Schema Reference​

Overview

What is a Value Stream?

Purpose and Value

Core Components

Domain Attributes

Value Stream Attributes

Value Stream Stage (`valueStreamStage`)

Enumeration Values

Maturity Level (`maturityLevel`)

Domain Relationships

Examples

Example 1: Track Inspection and Maintenance Value Stream

Example 2: Customer Onboarding Value Stream

Example 3: Data Analytics Value Stream

Implementation Guidelines

Value Stream Mapping Best Practices

Value Stream Visualization

Lean Metrics

OpenMetadata Integration

Schema Reference