Familiar with BIZBOK
If you're experienced with BIZBOK, you'll recognise the importance of a structured business architecture approach. The Orthogramic Metamodel builds on this foundation—while significantly extending it—to meet the practical demands of dynamic, federated, and digital-first organisations.
Where BIZBOK provides a strong conceptual grounding, the Orthogramic Metamodel operationalises these concepts within a schema-first, digitally actionable structure. Each domain in the metamodel is defined with consistent JSON schemas, enabling traceability, integration, and automated governance across platforms.
Expanded Domain Coverage
The Orthogramic Metamodel includes all core BIZBOK domains such as Strategy, Capabilities, Initiatives, Stakeholders, Information, and Value Streams. It then extends this foundation with additional domains essential for modern organisations:
| Extended Domain | Purpose |
|---|---|
| Performance | Integrated KPIs and evaluative models for continuous strategic alignment |
| Policy | Formalised guidance embedded within process and capability flows |
| Customer | Customer segments, journeys, and experience |
| Channel | Distribution and delivery pathways |
| Market | Competitive landscape and positioning |
| Risk | Risk identification, assessment, and mitigation |
| Finance | Financial planning and value tracking |
| Supply Chain | Upstream and downstream partners |
| Sustainability | ESG and environmental considerations |
| Technology | Digital platforms and infrastructure |
| People | Workforce design and culture |
This broader scope reflects the real complexity of today's operating environments, where architecture must bridge strategy, delivery, and external accountability.
From Documentation to Continuous Alignment
Unlike traditional frameworks which often focus on documenting static views, Orthogramic is designed for continuous alignment. Strategic shifts, performance data, and external triggers flow directly into the Strategic Response Model, enabling rapid responses that are structurally sound and traceable to their origin.
With machine-readable domain models, automated impact analysis, and integrated validation, the Orthogramic Metamodel turns business architecture from a planning artefact into a real-time strategic asset.
Core Similarities and Differences
| Feature | BIZBOK | Orthogramic Metamodel |
|---|---|---|
| Domain coverage | Broad but informal | Broad, plus adds Performance and Policy as structured domains |
| Data structure | Primarily narrative | Fully structured JSON Schemas |
| Interrelationships | Implicit, often described narratively | Explicit artefacts (e.g., Inter-unit domain relationships) |
| Scenarios | Use-case driven | Strategic Response Model with formalised triggers and responses |
| Implementation focus | Often abstract | Designed for live, API-enabled systems |
| Tooling | Tool-agnostic | Tool-agnostic, but natively supports digital platform integration |
Orthogramic preserves BIZBOK's strengths—such as clear domain thinking and alignment focus—while addressing limitations around reusability, automation, and analytic depth.
Key Concepts to Explore First
Domains as Structured Artefacts
All core business architecture domains (e.g., Capabilities, Value Streams, Information, Stakeholders) are expressed as structured artefacts in Orthogramic. Each has a JSON Schema defining its attributes, sub-elements, and relationships. This enables consistent use across platforms and teams.
Start by familiarising yourself with:
Inter-unit Domain Relationships
BIZBOK often refers to capability ownership and use abstractly. Orthogramic formalises this with a distinct artefact: Inter-unit domain relationships.
You can:
- Define who owns, uses, supports, or depends on a capability, service, or value stream
- Specify relationship strength (1–5 scale)
- Link to organisation units and domain entities with traceable IDs
This enables dynamic governance modelling and improved alignment tracking.
→ See Inter-unit Domain Relationships
Strategic Response Model (SRM)
Orthogramic introduces the SRM to formalise how an organisation responds to internal and external triggers (e.g., policy changes, customer demand shifts, regulatory pressure).
An SRM includes:
- Triggers — Identifiable events or pressures
- Rationales — Business justification for response
- Target outcomes — Desired business objectives
- Business response — Capabilities, initiatives, and value streams activated
This fills a gap in BIZBOK around structured scenario modelling and strategic planning execution.
→ See Strategic Response Model
Applying Your BIZBOK Knowledge
| BIZBOK Concept | Orthogramic Equivalent or Enhancement |
|---|---|
| Capability map | Capability artefacts with inter-unit relationships |
| Stakeholder map | Stakeholders artefact, plus traceable stakeholder requirements |
| Value stream stage maps | Value Stream artefact + Trigger integration via SRM |
| Information concept model | Information artefact with data custodianship and access roles |
| Governance structure | Embedded via custodian roles, ownership models, and policy artefacts |
| Business scenarios | Formalised through the SRM and response modelling tools |
You can start by converting your existing capability and value stream maps into structured artefacts and layering inter-unit relationships to visualise ownership and dependency.
The schema-first approach means your business architecture can directly inform your data catalog:
- Capability ownership → Data asset ownership in OpenMetadata
- Value streams → Data pipeline lineage
- Stakeholders → Data stewards and owners
- Policies → Governance rules and tags
See OpenMetadata Integration for patterns.
Next Steps
1. Review the Metamodel Schemas
Start with the Capabilities, Information, and Stakeholders domains.
2. Use Inter-unit Relationships to Map Governance
Apply the Inter-unit Relationships schema to your existing capability maps.
3. Model a Strategic Response
Use the Strategic Response Model to simulate a business event and the intended architectural response.
4. Embed Automation
With JSON schema conformance, the model can be consumed by APIs, validation engines, and workflow tools. Start with Organization.
5. Contribute to the Open Source Model
The Orthogramic Metamodel is available under Creative Commons BY-SA 4.0 for use and contribution. See the Contribution Guidelines.
Ready to compare in detail? See the Framework Comparison section.