Business architecture mode coverage

Introduction

The Orthogramic Metamodel has been designed as a comprehensive foundation for modelling an organisation's business architecture. It already supports core domains and structured relationships enabling strategic alignment, performance monitoring, and stakeholder engagement. This document evaluates whether the current metamodel requires extension to support the full spectrum of business architecture modes of operation, as practised by experienced business architects.

Mode comparison

Mode	Support Level	Current Implementation	Recommendations & Additional Details
Creating an organisational perspective	✅ Fully Supported	Organisation domain, Organisation Units, and inter-unit relationships	None needed
Driving a strategic intention	✅ Fully Supported	Strategy, Initiatives (Programs and Projects), and their traceability to Capabilities, Stakeholders, and Performance	None needed
Creating strategic response models	✅ Fully Supported	Strategic Response Model, including Triggers, Rationales, and Responses	None needed
Providing an oversight perspective	✅ Fully Supported	Stakeholder extensions (oversight roles), `accountable_to` and `oversight_of` relationships, and links to Policy and Performance domains	None needed
Capability maturity and gap analysis	⚠️ Partially Supported	Capabilities domain includes `maturityLevel`, but lacks structured representation of current vs. target state comparisons	Add fields for `targetMaturityLevel` and `deltaAnalysis` to Capability schema
Portfolio rationalisation and alignment	⚠️ Partially Supported	Initiatives and their links to Capabilities and Strategy are modelled, but no explicit domain for portfolios or value scoring	Add Portfolio as a new domain or sub-element of Initiatives, including scoring and prioritisation attributes. Use the Finance and Performance domains for cost-benefit inputs
Reference model tailoring and governance setup	Limited Support	Policy and Organisation domains can capture governance rules, but no structured way to define architectural standards, compliance frameworks, or principle hierarchies	Extend Policy domain with sub-elements for `architecturePrinciples`, `complianceFrameworks`, and `governanceStructures`. Link with Risk Management and Sustainability where applicable
Transformation roadmap development	⚠️ Partially Supported	Initiatives and Programs imply time-based change, but no native timeline, milestone, or sequencing model	Add `timeSequence`, `milestone`, and dependencies to Initiatives and Capabilities for roadmap creation. Use the Technology and Innovation domains for transformation-enabling factors
Stakeholder influence and communication enablement	✅ Fully Supported	Stakeholder domain includes `engagementStrategies`, `interestLevels`, and `performanceIndicators`, which allow modelling of influence and communication	Additional enrichment: Incorporate the Customer, Channel, and Market domains where external stakeholder expectations shape decisions
Design and validation of operating models	⚠️ Partially Supported	Organisation, Capability, and Value Stream domains offer some structure, but no consolidated Operating Model entity	Introduce `OperatingModel` as a composite view or virtual entity, linking Organisation, Capabilities, Value Streams, People, Technology, and Performance domains