Capabilities Domain

The Capabilities domain represents core functions and competencies an organization must develop and maintain to deliver value and achieve strategic objectives. It provides a structured view of what an organization can do, independent of processes, systems, or people.

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

Overview

What is a Capability?

A capability represents the capacity of an organization to perform a particular kind of work or deliver specific outcomes. It encompasses the combination of:

• People — Skills and competencies required
• Processes — Workflows and procedures that enable execution
• Technology — Systems and tools that support delivery
• Information — Data and knowledge needed

Capabilities are expressed in business terms and remain relatively stable over time, while the underlying resources that enable them may change.

Purpose and Value

The Capabilities domain enables architects and planners to:

• Bridge strategy and execution by linking strategic objectives to organizational abilities
• Assess maturity by tracking current vs. target capability levels
• Identify investment needs by highlighting capability gaps
• Enable reuse by describing capabilities independent of implementation
• Support governance by assigning clear ownership and accountability

For Data Engineers

The Capabilities domain maps directly to data platform concepts:

• Capability → Service or Function in your architecture
• Capability Components → Infrastructure components (compute, storage, tools)
• Maturity Level → Service maturity or SLA tier
• Inputs/Outputs → Data flows and dependencies

Core Components

The Capabilities domain includes three essential elements that work together:

1. Capability Function: Represents the overarching purpose and role of a capability within the organization
2. Capability Components: Key structural elements including people, processes, technology, and information
3. Capability Process: Essential workflows, activities, and tasks that drive the capability's operation

Domain Attributes

Core Attributes

Attribute	Type	Description	Required
capabilityID	String	Unique identifier for the Capability, e.g. CAP-001	✓
title	String	The name or title of the Capability	✓
description	String	A detailed explanation of what the Capability entails	✓
purpose	String	The intended purpose or function within the Organization	✓
owner	String	The individual or team responsible for the Capability	✓
orgUnitTitle	String	The organization unit(s) to which the Capability is linked
orgUnitID	String	ID of the organization unit (see orgUnitTitle)
capabilityCategory	Enum	Broad categorization of capability type
capabilityType	Enum	Specific type of capability
businessDomain	Enum	Business domain area
inputs	String	Required resources/information/materials
outputs	String	Deliverables or results produced
performanceIndicators	String	Effectiveness and efficiency metrics
dependencies	String	Other capabilities, processes, or systems required
relatedCapabilities	String	Capabilities that are related or linked
relatedCapabilityIDs	Array[String]	IDs of related Capabilities
maturityLevel	Enum	Current maturity level of the Capability
targetMaturityLevel	Enum	Desired future maturity level
toolsAndTechnologies	String	Tools and technologies used to support the Capability
cost	String	Financial cost for implementation and maintenance
investmentCategory	Enum	Type of investment required
risks	String	Potential risks associated with the Capability
riskCategories	Array[Enum]	Categories of risks
improvementOpportunities	String	Areas for enhancement or improvement
strategicAlignment	String	Alignment with strategic goals and objectives
criticality	Enum	Business criticality level
availability	Enum	Availability requirement
scalability	Enum	Scalability characteristics
parent	String	High-level Capability that encompasses this capability
parentCapabilityID	String	ID of the higher-level Capability that encompasses this one
child	String	Specific Capability that falls under this capability
childCapabilityIDs	Array[String]	IDs of the Capabilities that fall under this one
capabilityFunctions	Array[Object]	Functions that define capability purpose
capabilityComponents	Array[Object]	Structural elements of the capability
capabilityProcesses	Array[Object]	Processes that drive capability operation

A capability record may not carry fields other than those listed above. Name links (orgUnitTitle, relatedCapabilities, parent, child) can be paired with their ID fields.

Enumeration Values

Capability Category (capabilityCategory)

Value	Description	Example
coreBusiness	Central to organization's primary value proposition	Customer service, product development
supporting	Supports core business capabilities	Human resources, finance, procurement
enabling	Enables other capabilities to function	IT infrastructure, data management
strategic	Drives competitive advantage and differentiation	Innovation, strategic planning
foundational	Basic capabilities required for operation	Governance, compliance, risk management
distinctive	Unique capabilities that differentiate from competitors	Proprietary technology, specialized expertise

Capability Type (capabilityType)

Value	Description	Example
operational	Day-to-day operational capabilities	Manufacturing, logistics, customer support
technical	Technology and engineering capabilities	Software development, system integration
business	Business management and strategy capabilities	Strategic planning, business analysis
governance	Oversight and control capabilities	Risk management, compliance, audit
innovation	Research and development capabilities	R&D, product innovation, process improvement
analytical	Data analysis and intelligence capabilities	Business intelligence, predictive analytics
digital	Digital transformation capabilities	Digital platforms, automation, AI/ML
customer	Customer-facing capabilities	Sales, marketing, customer experience

Business Domain (businessDomain)

Value	Description	Example
operations	Operational business functions	Manufacturing, supply chain, logistics
finance	Financial management functions	Accounting, budgeting, financial planning
technology	Technology and IT functions	Software development, infrastructure, cybersecurity
humanResources	People management functions	Recruitment, training, performance management
salesMarketing	Revenue generation functions	Sales, marketing, customer acquisition
customerService	Customer support functions	Help desk, customer support, service delivery
legalCompliance	Legal and regulatory functions	Legal affairs, compliance, risk management
researchDevelopment	Innovation functions	Product development, research, innovation
qualityAssurance	Quality management functions	Quality control, testing, process improvement
strategyPlanning	Strategic management functions	Strategic planning, business development
procurement	Purchasing and vendor management	Supplier management, procurement, contracts
facilities	Physical infrastructure management	Building management, maintenance

Maturity Level (maturityLevel, targetMaturityLevel)

Both fields use the shared maturity list from common.schema.json.

Value	Description	Characteristics
initial	Ad-hoc, unpredictable processes	Reactive, heroic efforts, inconsistent results
repeatable	Basic project management	Some processes defined, can repeat past successes
defined	Standardized organizational processes	Documented, consistent, proactive management
managed	Quantitatively measured and controlled	Metrics-driven, predictable performance
optimizing	Continuous improvement focus	Innovation-driven, industry-leading practices

Investment Category (investmentCategory)

Value	Description	Example
capex	Capital expenditure	Hardware, facilities, major systems
opex	Operational expenditure	Licensing, maintenance, services
mixed	Combination of CAPEX and OPEX	Hybrid cloud, managed services
people	Human resource investment	Training, hiring, contractors
technology	Technology investment	Software, platforms, tools
process	Process improvement investment	Consulting, re-engineering

Criticality (criticality)

criticality uses the shared four-point rating.

Value	Description	Example
critical	Essential for core operations	Mission-critical systems, safety systems
high	Important for key business functions	Core business applications, reporting systems
medium	Supports important functions	Analytical tools, administrative systems
low	Supporting functions	Nice-to-have features, convenience tools

Availability (availability)

Value	Description	Example
24x7	Continuous availability required	Critical production systems, emergency services
businessHours	Available during business hours	Office applications, administrative systems
onDemand	Available when needed	Analytical tools, reporting systems
seasonal	Available during specific periods	Holiday processing, seasonal operations
scheduled	Available during scheduled windows	Batch processing, maintenance windows

Scalability (scalability)

Value	Description	Example
highlyScalable	Can scale easily with demand	Cloud-based services, automated systems
moderatelyScalable	Can scale with some effort	Traditional applications, manual processes
limitedScalability	Difficult to scale	Legacy systems, resource-constrained processes
notScalable	Cannot scale beyond current capacity	Fixed-capacity systems, manual operations

Sub-Elements

Capability Function (capabilityFunction)

Attribute	Type	Description	Required
title	String	Name/title of the function	✓
description	String	Detailed explanation of the function	✓
purpose	String	Intended purpose of the function	✓
owner	String	Individual/team responsible for the function
orgUnitTitle	String	Organization unit(s) where function resides
orgUnitID	String	ID of the organization unit (see orgUnitTitle)
functionType	Enum	Type of function: primary, secondary, supporting, enabling
inputs	String	Required inputs to perform the function
outputs	String	Outputs or deliverables produced
processes	String	Processes involved in the function
performanceMetrics	String	Metrics for measuring function effectiveness
frequency	Enum	How often the function is performed (shared frequency list)

Capability Component (capabilityComponent)

Attribute	Type	Description	Required
title	String	Name/title of the component	✓
description	String	Detailed explanation of the component	✓
purpose	String	Intended purpose/benefit of the component	✓
owner	String	Individual/team responsible for the component
orgUnitTitle	String	Organization unit(s) utilizing the component
orgUnitID	String	ID of the organization unit (see orgUnitTitle)
componentType	Enum	Type: people, process, technology, information, infrastructure
technologies	String	Technologies and tools used
processes	String	Processes involved in the component
skills	String	Skills and competencies required
vendor	String	External vendor or supplier
lifecycle	Enum	Lifecycle stage, from the shared lifecycle list: ideation, planning, design, development, implementation, launch, operational, enhancement, optimization, retirement
cost	String	Cost associated with the component

Capability Process (capabilityProcess)

Attribute	Type	Description	Required
title	String	Name/title of the process	✓
description	String	Detailed explanation of the process	✓
purpose	String	Intended purpose of the process	✓
owner	String	Individual/team responsible for the process	✓
orgUnitTitle	String	Organization unit(s) executing the process
orgUnitID	String	ID of the organization unit (see orgUnitTitle)
parentCapability	String	The Capability this process supports
parentCapabilityID	String	ID of the Capability this process supports
processType	Enum	Type of process: core, support, management, governance
processCategory	Enum	Process category: operational, strategic, tactical, administrative
inputs	String	Required inputs to the process
outputs	String	Outputs produced by the process
steps	String	Key steps or activities in the process
performanceMetrics	String	Metrics for measuring process effectiveness
complianceRequirements	String	Regulatory requirements governing the process
toolsRequired	String	Tools, equipment and systems needed for the process
duration	String	Typical time to complete the process
frequency	Enum	How often the process is executed (shared frequency list)
automation	Enum	Level of automation, from the shared list: manual, semiAutomated, highlyAutomated, fullyAutomated, aiEnabled
complexity	Enum	Process complexity, from the shared list: simple, moderate, complex, highlyComplex

Sub-elements may not carry fields other than those listed in their tables.

Domain Relationships

The Capabilities domain integrates with other metamodel domains:

Target Domain	Relationship Type	Description
Organization	Ownership	Organization units own capabilities
Strategy	Alignment	Capabilities align with strategic objectives
Initiatives	Enhancement	Initiatives improve or create capabilities
Services	Enablement	Capabilities enable service delivery
Technology	Implementation	Technology implements capabilities
People	Staffing	People staff and operate capabilities
Information	Consumption	Capabilities consume and produce information
Performance	Measurement	Performance metrics measure capability effectiveness
Value Stream	Contribution	Capabilities contribute to value streams

Examples

Example: Automated Track Inspection System

{
  "capabilityID": "CAP-001",
  "title": "Automated Track Inspection System",
  "description": "AI-enabled system for continuous track geometry measurement and defect detection across the rail network",
  "purpose": "Enhance track inspection efficiency and accuracy through automated monitoring",
  "owner": "Chief of Track Inspection Technology",
  "orgUnitTitle": "Track and Rail Infrastructure Division",
  "capabilityCategory": "coreBusiness",
  "capabilityType": "operational",
  "businessDomain": "operations",
  "inputs": "Track geometry data, rail wear measurements, historical inspection records",
  "outputs": "Daily inspection reports, defect predictions, maintenance recommendations",
  "maturityLevel": "defined",
  "targetMaturityLevel": "managed",
  "toolsAndTechnologies": "LIDAR sensors, machine learning models, cloud analytics platform",
  "cost": "Annual operating cost: $12.8M",
  "investmentCategory": "technology",
  "risks": "Equipment failure, data accuracy issues, sensor calibration drift",
  "riskCategories": [
    "technology",
    "operational",
    "financial"
  ],
  "improvementOpportunities": "Integrate thermal imaging, expand predictive capabilities",
  "strategicAlignment": "Supports accident reduction and efficiency goals",
  "criticality": "critical",
  "availability": "24x7",
  "scalability": "highlyScalable",
  "capabilityFunctions": [
    {
      "title": "Track Geometry Measurement",
      "description": "Automated measurement of track geometry parameters including gauge, alignment, and surface",
      "purpose": "Ensure compliance with FRA track geometry standards",
      "owner": "Track Geometry Program Manager",
      "orgUnitTitle": "Track Inspection Division",
      "functionType": "primary",
      "inputs": "Raw sensor data, track class information",
      "outputs": "Geometry exception reports, maintenance alerts",
      "processes": "Data collection, analysis, reporting, validation",
      "performanceMetrics": "Data processing speed, accuracy rates",
      "frequency": "continuous"
    }
  ],
  "capabilityComponents": [
    {
      "title": "Rail Wear Detection System",
      "description": "Automated measurement of rail head wear and profile degradation",
      "purpose": "Monitor rail degradation and predict maintenance needs",
      "owner": "Rail Integrity Program Lead",
      "orgUnitTitle": "Track Maintenance Division",
      "componentType": "technology",
      "technologies": "Laser profilers, ultrasonic sensors, analysis software",
      "processes": "Data collection, wear analysis, reporting",
      "skills": "Rail inspection certification, data analysis expertise",
      "vendor": "Technology Solutions Inc.",
      "lifecycle": "operational",
      "cost": "Annual licensing: $150K, Maintenance: $50K"
    }
  ],
  "capabilityProcesses": [
    {
      "title": "Defect Detection Workflow",
      "description": "End-to-end process for identifying and reporting track defects",
      "purpose": "Ensure timely detection and resolution of safety-critical defects",
      "owner": "Defect Detection Coordinator",
      "orgUnitTitle": "Safety Compliance Unit",
      "parentCapability": "Automated Track Inspection System",
      "parentCapabilityID": "CAP-001",
      "processType": "core",
      "processCategory": "operational",
      "inputs": "Sensor data, inspection images, historical defect database",
      "outputs": "Defect reports, priority rankings, work orders",
      "steps": "Data ingestion, ML analysis (about 80% of cases), human verification (about 20%), report generation",
      "frequency": "daily",
      "performanceMetrics": "Detection accuracy, false positive rate, time to report",
      "toolsRequired": "Track geometry system, work order management system",
      "automation": "highlyAutomated"
    }
  ]
}

Implementation Guidelines

Capability Modeling Best Practices

1. Start with business outcomes — Define capabilities in terms of what the organization needs to do, not how
2. Keep capabilities stable — Capabilities should not change frequently; implementations do
3. Avoid overlapping capabilities — Each capability should have a clear, distinct purpose
4. Use hierarchies thoughtfully — Parent-child relationships should represent logical decomposition
5. Link to strategy — Every capability should trace to strategic objectives

Maturity Assessment Approach

1. Assess Current State: Document current maturity level with evidence
2. Define Target State: Set realistic target maturity based on strategy
3. Identify Gaps: Analyze gaps between current and target
4. Plan Improvements: Create initiatives to close gaps
5. Execute & Measure: Implement and track progress

OpenMetadata Integration

For Data Platform Teams

When integrating with OpenMetadata, map Capability entities as follows:

Triodian Element	OpenMetadata Entity	Notes
Capability	Custom Entity or Tag	Create custom entity type or use tags
Capability Owner	User/Team	Link to ownership
Inputs/Outputs	Lineage	Map data flows
Maturity Level	Custom Property	Track on services/pipelines
Components (Technology)	Service	Link to actual services

# Example: Link capability to data assets in OpenMetadata
def link_capability_to_assets(capability, data_assets):
    """
    Create custom properties on data assets linking to business capabilities
    """
    capability_tag = {
        "tagFQN": f"BusinessCapability.{capability['title'].replace(' ', '')}",
        "description": capability["description"],
        "source": "Triodian"
    }
    
    for asset in data_assets:
        asset["tags"].append(capability_tag)
        asset["extension"] = {
            "capabilityID": capability["capabilityID"],
            "capabilityOwner": capability["owner"],
            "maturityLevel": capability.get("maturityLevel")
        }
    
    return data_assets

Value Stream Integration

Capabilities are key contributors to value streams. When modeling:

1. Map capabilities to value stream stages — Which capabilities support each stage?
2. Identify capability dependencies — What capabilities must work together?
3. Track capability performance — How do capabilities impact value stream KPIs?

Schema Reference

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

---

Previous: Stakeholder Domain | Next: Strategy Domain