Cross-domain relationships

1 Introduction
2 Relationship types
3 Examples
4 Enumeration values
5 JSON schema structure
6 Implementation guidelines

This is an experimental schema, not yet tested in Orthogramic.

Introduction

In the Orthogramic Metamodel, cross-domain relationships articulate the comprehensive interactions between elements across distinct business architecture domains. These relationships are pivotal for understanding how components such as strategies, capabilities, value streams, policies, initiatives, and performance metrics interconnect, thereby enabling a cohesive and comprehensive view of the enterprise.

By delineating these interdependencies, cross-domain relationships facilitate:

Strategic alignment across all organizational domains
Operational efficiency through clear dependency mapping
Informed decision-making with complete impact understanding
Risk management through comprehensive relationship visibility
Innovation enablement by identifying cross-domain opportunities
Compliance assurance through governance relationship tracking

Cross-domain relationships serve as the connective tissue that binds various domains, ensuring that changes or developments in one area are appropriately reflected, managed, and leveraged across others. This framework supports practitioners in mapping and analyzing the complex web of interactions that underpin organizational performance, strategic execution, and sustainable competitive advantage.

Relationship types

Each cross-domain relationship type defines a specific way in which two business architecture domains interact. The framework provides comprehensive coverage of domain interdependencies to ensure consistency and clarity across modeling activities.

Financial relationships

Relationship Type	Description

Relationship Type	Description
`funds`	Finance provides financial resources to another domain entity to enable its development, operation, or enhancement
`measures`	Finance expresses the activities, outputs, or outcomes of another domain entity in measurable financial terms
`reports`	Finance produces formal reports capturing the financial performance, costs, or returns associated with another domain entity
`forecasts`	Finance projects future financial needs, costs, or revenues associated with another domain entity

Operational relationships

Relationship Type	Description

Relationship Type	Description
`depends`	One domain entity receives necessary resources, services, or capabilities from another domain entity to deliver its intended outputs or outcomes
`constrains`	One domain entity imposes limitations, standards, or compliance requirements on another domain entity's design, operation, or evolution
`enables`	One domain entity is essential for the successful implementation, operationalization, or fulfillment of another domain entity
`mitigates`	One domain entity actively reduces the risks or vulnerabilities associated with another domain entity
`consumes`	One domain entity uses, relies upon, or draws from the resources, outputs, or services of another domain entity
`delivers`	One domain entity provides specific value or outcomes to another domain entity
`optimizes`	One domain entity improves the performance or efficiency of another domain entity
`maintains`	One domain entity ensures ongoing operation of another domain entity

Governance relationships

Relationship Type	Description

Relationship Type	Description
`monitors`	One domain entity oversees, measures, or evaluates the performance or effectiveness of another domain entity
`governs`	One domain entity defines policies, standards, or decision rights that control the operation of another domain entity
`audits`	One domain entity formally examines and evaluates another domain entity for compliance, performance, or quality
`certifies`	One domain entity provides formal approval or certification to another domain entity
`escalates`	One domain entity receives escalated issues or exceptions from another domain entity
`accountableFor`	For systematic traceability of oversight responsibilities
`responsibleFor`	For a clear line of responsibility between entities

Information and knowledge relationships

Relationship Type	Description

Relationship Type	Description
`informs`	One domain entity provides information or data that shapes decisions in another domain entity
`validates`	One domain entity confirms or verifies outputs, decisions, or processes from another domain entity
`enriches`	One domain entity enhances the data quality, completeness, or value of another domain entity
`learns`	One domain entity gains knowledge or insights from another domain entity
`teaches`	One domain entity transfers knowledge or capabilities to another domain entity
`benchmarks`	One domain entity uses another domain entity as a performance standard or reference point

Innovation and transformation relationships

Relations	Relations

Relations	Relations
`innovates`	One domain entity drives innovation or new developments in another domain entity
`evolves`	One domain entity causes evolutionary changes in another domain entity
`transforms`	One domain entity drives transformational change in another domain entity
`designs`	One domain entity shapes the structure, approach, or architecture of another domain entity
`implements`	One domain entity executes or realizes the vision, strategy, or design of another domain entity

Coordination and integration relationships

Relations	Relations

Relations	Relations
`orchestrates`	One domain entity coordinates the activities of multiple other domain entities
`integrates`	One domain entity brings together outputs or processes from another domain entity
`synchronizes`	One domain entity ensures timing alignment with another domain entity
`aligns`	One domain entity is intentionally coordinated or harmonized with another domain entity in purpose, direction, or design without establishing a direct dependency
`prioritizes`	One domain entity influences the priority or sequencing of another domain entity

Market and demand relationships

Relationship Type	Description

Relationship Type	Description
`drives`	One domain entity generates, influences, or amplifies the demand for another domain entity's outputs, services, or capabilities
`responds`	One domain entity is triggered, adapted, or activated in response to changes in another domain entity or external event

Examples

Financial domain relationships example

This demonstrates how Finance interacts with multiple domains through various relationship types:

{
  "crossDomainRelationships": [
    {
      "sourceDomain": "Finance",
      "targetDomain": "Capability",
      "relationshipType": "funds",
      "description": "Finance provides funding to capabilities to enable development and enhancement of organizational competencies aligned with strategic objectives",
      "metadata": {
        "priority": "critical",
        "impact": "strategic",
        "frequency": "quarterly",
        "strength": 5
      }
    },
    {
      "sourceDomain": "Finance",
      "targetDomain": "Initiative",
      "relationshipType": "measures",
      "description": "Finance establishes ROI and financial performance metrics for strategic initiatives",
      "metadata": {
        "priority": "high",
        "impact": "financial",
        "frequency": "monthly",
        "strength": 4
      }
    },
    {
      "sourceDomain": "Finance",
      "targetDomain": "Value Stream",
      "relationshipType": "reports",
      "description": "Finance produces cost and profitability reports for customer value streams",
      "metadata": {
        "priority": "medium",
        "impact": "operational",
        "frequency": "monthly",
        "strength": 3
      }
    }
  ]
}

Innovation ecosystem example

This shows how innovation flows across domains:

{
  "crossDomainRelationships": [
    {
      "sourceDomain": "Strategy",
      "targetDomain": "Capability",
      "relationshipType": "designs",
      "description": "Strategic vision shapes required future capability architecture",
      "metadata": {
        "priority": "strategic",
        "impact": "innovation",
        "strength": 5
      }
    },
    {
      "sourceDomain": "Capability",
      "targetDomain": "Initiative",
      "relationshipType": "innovates",
      "description": "Capability development drives innovation initiatives",
      "metadata": {
        "priority": "high",
        "impact": "innovation", 
        "strength": 4
      }
    },
    {
      "sourceDomain": "Initiative",
      "targetDomain": "Value Stream",
      "relationshipType": "transforms",
      "description": "Digital transformation initiative fundamentally changes customer experience value streams",
      "metadata": {
        "priority": "critical",
        "impact": "customer",
        "strength": 5
      }
    }
  ]
}

Compliance and governance example

This illustrates comprehensive governance relationships:

{
  "crossDomainRelationships": [
    {
      "sourceDomain": "Policy",
      "targetDomain": "Capability",
      "relationshipType": "constrains",
      "description": "Data governance policies constrain information management capabilities",
      "metadata": {
        "priority": "high",
        "impact": "regulatory",
        "strength": 4
      }
    },
    {
      "sourceDomain": "Compliance",
      "targetDomain": "Value Stream",
      "relationshipType": "audits",
      "description": "Compliance function audits customer onboarding value stream for regulatory adherence",
      "metadata": {
        "priority": "critical",
        "impact": "regulatory",
        "frequency": "quarterly",
        "strength": 5
      }
    },
    {
      "sourceDomain": "Risk",
      "targetDomain": "Initiative",
      "relationshipType": "escalates",
      "description": "Risk management escalates high-risk initiative issues to executive committee",
      "metadata": {
        "priority": "critical",
        "impact": "risk",
        "strength": 5
      }
    }
  ]
}

Enumeration values

Priority levels

Property	Allowed Values	Description

Property	Allowed Values	Description
`priority`	`critical`	The relationship is business-critical and requires immediate attention and action
	`strategic`	The relationship has long-term strategic importance and should be prioritized for strategic planning
	`high`	The relationship is important and should be prioritized for attention, action, or analysis
	`medium`	The relationship is important but not critical; it should be monitored and addressed as needed
	`low`	The relationship has limited immediate significance and can be considered lower priority

Impact classifications

Property	Allowed Values	Description

Property	Allowed Values	Description
`impact`	`strategic`	The relationship affects the organization's strategic objectives, positioning, or long-term outcomes
	`operational`	The relationship influences day-to-day business operations, efficiency, or delivery of services
	`tactical`	The relationship impacts specific initiatives, projects, or time-bound goals within the organization
	`financial`	The relationship has direct financial implications for the organization
	`regulatory`	The relationship affects compliance with laws, regulations, or industry standards
	`customer`	The relationship impacts customer experience, satisfaction, or value delivery
	`innovation`	The relationship affects innovation capabilities and competitive advantage
	`risk`	The relationship impacts organizational risk profile or risk management effectiveness

Frequency indicators

Property	Allowed Values	Description

Property	Allowed Values	Description
`frequency`	`continuous`	The relationship involves ongoing, continuous interaction
	`daily`	The relationship involves daily interactions or dependencies
	`weekly`	The relationship involves weekly interactions or reporting cycles
	`monthly`	The relationship involves monthly interactions, reviews, or reporting
	`quarterly`	The relationship involves quarterly interactions or formal reviews
	`annually`	The relationship involves annual interactions or strategic reviews
	`event-driven`	The relationship is activated by specific events or triggers

Relationship strength

Property	Allowed Values	Description

Property	Allowed Values	Description
`strength`	`1`	Very weak relationship with minimal impact or dependency
	`2`	Weak relationship with limited impact or occasional dependency
	`3`	Moderate relationship with regular interaction and mutual dependency
	`4`	Strong relationship with frequent interaction and significant dependency
	`5`	Very strong relationship with continuous interaction and critical dependency

JSON schema structure

Core relationship properties

{
  "sourceDomain": {
    "type": "string",
    "description": "The domain entity that initiates or provides in the relationship"
  },
  "targetDomain": {
    "type": "string", 
    "description": "The domain entity that receives or depends in the relationship"
  },
  "relationshipType": {
    "type": "string",
    "enum": ["funds", "measures", "reports", "forecasts", "depends", "constrains", "enables", "mitigates", "consumes", "delivers", "optimizes", "maintains", "monitors", "governs", "audits", "certifies", "escalates", "accountableFor", "responsibleFor", "informs", "validates", "enriches", "learns", "teaches", "benchmarks", "innovates", "evolves", "transforms", "designs", "implements", "orchestrates", "integrates", "synchronizes", "aligns", "prioritizes", "drives", "responds"]
  },
  "description": {
    "type": "string",
    "description": "Detailed description of how the domains interact"
  },
  "metadata": {
    "type": "object",
    "properties": {
      "priority": {
        "type": "string",
        "enum": ["critical", "strategic", "high", "medium", "low"]
      },
      "impact": {
        "type": "string", 
        "enum": ["strategic", "operational", "tactical", "financial", "regulatory", "customer", "innovation", "risk"]
      },
      "frequency": {
        "type": "string",
        "enum": ["continuous", "daily", "weekly", "monthly", "quarterly", "annually", "event-driven"]
      },
      "strength": {
        "type": "integer",
        "minimum": 1,
        "maximum": 5
      },
      "conditions": {
        "type": "string",
        "description": "Conditions under which this relationship exists"
      },
      "effectiveDate": {
        "type": "string",
        "format": "date",
        "description": "Date when this relationship becomes effective"
      },
      "reviewDate": {
        "type": "string",
        "format": "date", 
        "description": "Date when this relationship should be reviewed"
      }
    }
  }
}

Implementation guidelines

Relationship modeling best practices

Start with high-impact relationships - Focus on critical and strategic priority relationships first
Use bidirectional modeling - Consider if relationships should be modeled in both directions
Validate with stakeholders - Ensure relationship descriptions accurately reflect organizational reality
Regular review cycles - Establish review schedules based on relationship criticality
Impact assessment - Analyze the downstream effects of relationship changes

Domain coverage recommendations

Financial domain - Model all funding, measurement, and reporting relationships
Governance domains - Ensure comprehensive coverage of policy, risk, and compliance relationships
Innovation domains - Capture transformation and development relationships
Operational domains - Model service delivery and capability relationships
Information domains - Include data flow and knowledge transfer relationships

Quality assurance

Avoid relationship redundancy - Ensure each relationship provides unique analytical value
Maintain semantic clarity - Keep relationship types distinct and non-overlapping
Validate completeness - Test relationship models against real organizational scenarios
Monitor relationship evolution - Track how relationships change over time