Model Concepts (OWL Ontology)
Extension ontology for financial aspects of enterprise architecture.
Provides vocabulary for Total Cost of Ownership (TCO) models, cost allocation to
business capabilities and value streams, investment case tracking (Run/Grow/Transform),
cost-benefit analysis for architecture decision options, and FinOps cloud cost management.
Not intended to replace financial planning tools — the goal is to make cost a queryable
dimension of the architecture knowledge graph, enabling questions like "What is the
annual run cost of all applications supporting this capability?" or "Which decision
option has the best NPV?"
Motivated by Gartner 2025 Leadership Vision identifying lack of financial acumen as
one of the five mistakes EA teams make.
https://meta.linked.archi/financial-architecture/onto#
Formal Rules (SHACL Shapes)
SHACL shapes for validating financial architecture models.
Enforces governance rules: every cost model must have a currency and at least
one cost item, every investment case must have a type and projected ROI,
and every cost-benefit analysis must have cost, benefit, and NPV.
https://meta.linked.archi/financial-architecture/shapes#
Concept Classification (SKOS)
Classification of financial architecture concepts by cost type, investment type, and analysis type.
https://meta.linked.archi/financial-architecture/tax#FinancialArchitectureConceptScheme
Reference Data
Reference data for financial architecture — cost categories,
investment types, and cost periods.
https://meta.linked.archi/financial-architecture/reference-data#
| Type | Resource | Description | URI |
| Model Concepts (OWL Ontology) |
onto |
Extension ontology for financial aspects of enterprise architecture.
Provides vocabulary for Total Cost of Ownership (TCO) models, cost allocation to
business capabilities and value streams, investment case tracking (Run/Grow/Transform),
cost-benefit analysis for architecture decision options, and FinOps cloud cost management.
Not intended to replace financial planning tools — the goal is to make cost a queryable
dimension of the architecture knowledge graph, enabling questions like "What is the
annual run cost of all applications supporting this capability?" or "Which decision
option has the best NPV?"
Motivated by Gartner 2025 Leadership Vision identifying lack of financial acumen as
one of the five mistakes EA teams make. |
https://meta.linked.archi/financial-architecture/onto# |
| Formal Rules (SHACL Shapes) |
shapes |
SHACL shapes for validating financial architecture models.
Enforces governance rules: every cost model must have a currency and at least
one cost item, every investment case must have a type and projected ROI,
and every cost-benefit analysis must have cost, benefit, and NPV. |
https://meta.linked.archi/financial-architecture/shapes# |
| Concept Classification (SKOS) |
Financial Architecture Concept Scheme |
Classification of financial architecture concepts by cost type, investment type, and analysis type. |
https://meta.linked.archi/financial-architecture/tax#FinancialArchitectureConceptScheme |
| Reference Data |
reference-data |
Reference data for financial architecture — cost categories,
investment types, and cost periods. |
https://meta.linked.archi/financial-architecture/reference-data# |