Business Architecture Management

BC-170 Level 1 Cross-Industry 0 providers 0 API surfaces

Design, documentation, and governance of the structural relationships between strategy, capabilities, value streams, operating model, and business information assets. Provides the architectural artefacts that translate enterprise strategy into a coherent, navigable view of how the business is organised to deliver value.

Business Architecture Management (BC-170) is a level-1 business capability in the Cross-Industry model. The catalog holds 0 API surface(s) from 0 provider(s) that can perform some part of it. Reach is the vendor surface that lands on this capability — it is not a claim about what any particular organisation has deployed.

Where this capability definition comes from. This capability is part of a published business-architecture model that API Evangelist did not author. It is redistributed here under CC-BY-4.0. Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0 Changes: Consolidated from 333 per-L1 YAML files into one JSON; English only (upstream i18n/ omitted); descriptions whitespace-normalised. No capability was added, removed, renamed or re-parented. Source repository · NOTICE and third-party framework attributions

Authorities this capability cites

Cited by the capability model itself. These frameworks are referenced, never redistributed, and citing one does not imply its owner endorses this listing.

Sub-capabilities

Business Architecture Governance BC-170.10

Architecture principles, framework adoption, review, and exception handling for the business architecture practice.

no catalog coverage

Business Capability Modeling BC-170.20

Identification, decomposition, assessment, and sourcing analysis of business capabilities used as the primary architectural anchor.

no catalog coverage

Value Stream Modeling BC-170.30

Identification and modelling of end-to-end value streams and their linkage to enabling capabilities.

no catalog coverage

Operating Model Design BC-170.40

Architectural design of the operating model including service delivery model, sourcing footprint, and transition planning.

no catalog coverage

Business Information Modeling BC-170.50

Business-lens modelling of information assets, glossary, and information lifecycle. Conceptual and logical view; physical data architecture sits in IT.

no catalog coverage

Business Architecture Repository Management BC-170.60

Cataloguing, versioning, and tooling for business architecture artefacts.

no catalog coverage

Business Architecture Roadmap and Transition Planning BC-170.70

Current-state, target-state, and transition architecture planning to guide portfolio and investment decisions.

no catalog coverage

Providers that reach this capability

No provider in the catalog currently publishes an API surface that reaches this capability. That is a real answer, not a gap in the page: much of what an enterprise does runs on internal systems that publish no API at all.

This page carries no rating. Capabilities are not rated. A capability is a description of what a business does, not a thing a company publishes, so a Kin Score would have nothing to measure.
The edge table is a Pro feature. This page shows which providers and tags reach Business Architecture Management. The underlying tag → capability edges — each with the quoted fragment of the provider's own OpenAPI that evidences it, a calibrated confidence score, and the contract-provenance gate it passed — are available through the API, along with company-level capability maps. Only edges at confidence ≥ 0.7 with evidence found verbatim in the source contract are published at all.

See plans →  ·  How the edges are graded →