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 Version: 2.2
Schema Location: /schemas/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
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 |
|---|---|---|---|
title | String | Name or title of the Value Stream | ✓ |
description | String | Detailed explanation of the Value Stream | ✓ |
purpose | String | Intended purpose or function within the Organization | ✓ |
owner | String | Individual or team responsible | ✓ |
orgUnitTitle | String | Organization unit(s) linked | |
valueStreamCategory | Enum | Category of value stream | |
valueStreamType | Enum | Type of value stream | |
triggeringEvent | String | What initiates the value stream | |
endingState | String | Final state when value is delivered | |
customer | String | Primary customer or beneficiary | |
valueProposition | String | Value delivered to customer | |
performanceIndicators | String | Metrics for effectiveness and efficiency | |
dependencies | String | Capabilities, processes, or systems depended on | |
relatedValueStreams | String | Related or linked value streams | |
maturityLevel | Enum | Current maturity level | |
toolsAndTechnologies | String | Tools and technologies used | |
complianceAndStandards | Array[Enum] | Regulatory requirements and standards | |
cost | String | Financial cost for implementing and maintaining | |
cycleTime | String | Total time from trigger to value delivery | |
risks | String | Potential risks associated with the Value Stream | |
riskCategories | Array[Enum] | Categories of risks | |
improvementOpportunities | String | Areas for enhancement | |
strategicAlignment | String | Alignment with strategic goals | |
valueStreamStages | Array[Object] | Stages within the value stream |
Value Stream Stage Attributes
| Attribute | Type | Description |
|---|---|---|
stageTitle | String | Name/title of the stage |
parentValueStream | String | Value Stream it belongs to |
description | String | What the stage entails |
purpose | String | Intended function within the Value Stream |
owner | String | Responsible individual/team |
orgUnitTitle | String | Associated Organization unit(s) |
stageSequence | Integer | Order in the value stream |
inputs | String | Required resources/information |
outputs | String | Deliverables/results produced |
valueItems | String | Specific outputs or benefits generated |
performanceIndicators | String | Metrics for effectiveness/efficiency |
cycleTime | String | Time to complete this stage |
waitTime | String | Wait time before this stage |
dependencies | String | Other stages/systems it depends on |
relatedValueStreamStages | String | Connected stages |
risks | String | Potential risks |
improvementOpportunities | String | Areas for enhancement |
strategicAlignment | String | Alignment with Organization goals |
enablingCapability | String | Capability that enables this stage |
informationUsed | String | Information assets used |
informationProduced | String | Information assets produced |
Enumeration Values
Value Stream Category (valueStreamCategory)
| Value | Description | Example |
|---|---|---|
Operational | Core operational activities | Production, delivery |
Supporting | Internal support activities | HR, Finance, IT |
Development | Product/service development | R&D, Innovation |
Customer | Customer-facing activities | Sales, Service |
Strategic | Strategic planning activities | Planning, M&A |
Value Stream Type (valueStreamType)
| Value | Description | Example |
|---|---|---|
Product Delivery | Delivering products | Manufacturing, fulfillment |
Service Delivery | Delivering services | Customer service, consulting |
Information Processing | Processing information | Analytics, reporting |
Decision Support | Supporting decisions | Planning, analysis |
Maintenance | Maintaining assets | Infrastructure maintenance |
Development | Developing new capabilities | Product development |
Maturity Level (maturityLevel)
| Value | Description | Example |
|---|---|---|
Level 1 - Initial | Ad-hoc, inconsistent | No standard process |
Level 2 - Developing | Basic processes emerging | Some documentation |
Level 3 - Defined | Standardized processes | Documented procedures |
Level 4 - Managed | Quantitatively controlled | Metrics-driven |
Level 5 - 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
Example 1: Track Inspection and Maintenance Value Stream
{
"title": "Track Inspection and Maintenance",
"description": "End-to-end process for track inspection and maintenance activities ensuring rail safety and operational reliability",
"purpose": "Ensure track safety through efficient inspection and maintenance to support safe rail operations",
"owner": "Track Maintenance Program Director",
"orgUnitTitle": "Track and Rail Infrastructure Division",
"valueStreamCategory": "Operational",
"valueStreamType": "Maintenance",
"triggeringEvent": "Scheduled inspection cycle or reported track condition",
"endingState": "Track certified safe for operation at designated speed",
"customer": "Rail Operations Division, Passengers, Freight Customers",
"valueProposition": "Safe, reliable track infrastructure enabling on-time operations",
"performanceIndicators": "Track quality index: 96.8%, Maintenance completion rate: 94.5%, On-time delivery: 97.2%",
"dependencies": "Track measurement systems, maintenance crews, equipment availability, weather conditions",
"relatedValueStreams": "Signal system maintenance, bridge inspection process, equipment maintenance",
"maturityLevel": "Level 4 - Managed",
"toolsAndTechnologies": "Track geometry cars, ultrasonic testing equipment, maintenance management software",
"complianceAndStandards": ["Federal Regulations", "Safety Standards"],
"cost": "Annual budget: $178M for inspection and maintenance activities",
"cycleTime": "Average 14 days from inspection to maintenance completion",
"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",
"valueStreamStages": [
{
"stageTitle": "Track Geometry Inspection",
"stageSequence": 1,
"description": "Automated measurement of track geometry parameters using track geometry vehicles",
"purpose": "Identify track geometry defects requiring maintenance",
"owner": "Track Geometry Program Manager",
"orgUnitTitle": "Track Inspection Division",
"inputs": "Track class data, previous inspection results, maintenance history",
"outputs": "Track geometry exception reports, maintenance recommendations",
"valueItems": "Inspection reports, defect identification, safety certifications",
"performanceIndicators": "Inspection coverage: 98.2%, Defect identification accuracy: 96.5%",
"cycleTime": "2-3 days per territory",
"dependencies": "Track geometry vehicle availability, weather conditions, track access windows",
"relatedValueStreamStages": "Rail wear measurement, maintenance planning",
"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"
},
{
"stageTitle": "Defect Analysis and Prioritization",
"stageSequence": 2,
"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%",
"cycleTime": "1-2 days",
"enablingCapability": "Track Condition Analysis"
},
{
"stageTitle": "Maintenance Execution",
"stageSequence": 3,
"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%",
"cycleTime": "3-7 days depending on defect severity",
"enablingCapability": "Track Repair and Maintenance"
},
{
"stageTitle": "Quality Verification",
"stageSequence": 4,
"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%",
"cycleTime": "1 day",
"enablingCapability": "Quality Verification and Certification"
}
]
}
Example 2: Customer Onboarding Value Stream
{
"title": "Customer Onboarding",
"description": "End-to-end process for onboarding new customers from initial contact through active usage",
"purpose": "Successfully activate new customers to realize value from products and services",
"owner": "Customer Success Director",
"orgUnitTitle": "Customer Success Division",
"valueStreamCategory": "Customer",
"valueStreamType": "Service Delivery",
"triggeringEvent": "Customer signs contract or places first order",
"endingState": "Customer actively using products/services and achieving value",
"customer": "New customers",
"valueProposition": "Fast time-to-value with seamless onboarding experience",
"performanceIndicators": "Onboarding completion rate: 94%, Time to first value: 14 days, Customer satisfaction: 4.5/5",
"cycleTime": "Average 21 days from contract to full activation",
"maturityLevel": "Level 3 - Defined",
"valueStreamStages": [
{
"stageTitle": "Welcome and Setup",
"stageSequence": 1,
"description": "Initial customer welcome, account setup, and access provisioning",
"inputs": "Contract details, customer information",
"outputs": "Active account, access credentials, welcome materials",
"cycleTime": "1-2 days"
},
{
"stageTitle": "Configuration",
"stageSequence": 2,
"description": "Configure products/services to customer requirements",
"inputs": "Customer requirements, configuration templates",
"outputs": "Configured environment, custom settings",
"cycleTime": "3-5 days"
},
{
"stageTitle": "Training",
"stageSequence": 3,
"description": "Train customer users on product usage",
"inputs": "Training materials, user list",
"outputs": "Trained users, certification records",
"cycleTime": "5-7 days"
},
{
"stageTitle": "Go-Live Support",
"stageSequence": 4,
"description": "Support customer through initial production usage",
"inputs": "Go-live checklist, support resources",
"outputs": "Active production usage, resolved issues",
"cycleTime": "7-10 days"
}
]
}
Example 3: Data Analytics Value Stream
{
"title": "Data Analytics Pipeline",
"description": "End-to-end flow for transforming raw data into actionable business insights",
"purpose": "Deliver timely, accurate analytics to support business decision-making",
"owner": "Chief Data Officer",
"orgUnitTitle": "Data and Analytics Division",
"valueStreamCategory": "Supporting",
"valueStreamType": "Information Processing",
"triggeringEvent": "Data refresh schedule or ad-hoc analysis request",
"endingState": "Insights delivered and consumed by business stakeholders",
"customer": "Business stakeholders, executives, analysts",
"valueProposition": "Data-driven insights enabling better business decisions",
"performanceIndicators": "Data freshness: <4 hours, Report accuracy: 99.9%, User satisfaction: 4.3/5",
"cycleTime": "4 hours for standard reports, 2 days for ad-hoc analysis",
"maturityLevel": "Level 4 - Managed",
"toolsAndTechnologies": "Spark, Airflow, Snowflake, Tableau, dbt",
"valueStreamStages": [
{
"stageTitle": "Data Ingestion",
"stageSequence": 1,
"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"
},
{
"stageTitle": "Data Transformation",
"stageSequence": 2,
"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%",
"enablingCapability": "Data Transformation Engine"
},
{
"stageTitle": "Analytics Generation",
"stageSequence": 3,
"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%",
"enablingCapability": "Business Intelligence Platform"
},
{
"stageTitle": "Insight Delivery",
"stageSequence": 4,
"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%",
"enablingCapability": "Report Distribution System"
}
]
}
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
When integrating with OpenMetadata, map Value Stream entities as follows:
| Orthogramic 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):
"""
Map Orthogramic Value Stream to OpenMetadata Pipeline
"""
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"ValueStreamCategory.{value_stream.get('valueStreamCategory', 'Operational')}"},
{"tagFQN": f"MaturityLevel.{value_stream.get('maturityLevel', 'Defined')}"}
],
"tasks": [],
"extension": {
"triggeringEvent": value_stream.get("triggeringEvent"),
"cycleTime": value_stream.get("cycleTime"),
"customer": value_stream.get("customer")
}
}
# Add stages as tasks
for stage in value_stream.get("valueStreamStages", []):
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:
Orthogramic/Orthogramic_Metamodel - Schema Location:
/schemas/value-stream.schema.json - Version: 2.2
- Specification: JSON Schema Draft-07
- License: Creative Commons Attribution-ShareAlike 4.0 (CC BY-SA 4.0)
Previous: Policy Domain | Next: Technology Domain