Business Capabilities
The enterprise's ability to achieve a defined class of outcomes independently of the current structure and means of implementation.
Bundle → Layer → Finding → Questions Filled
2 bundles · 3 layers · 4 findings · 9 questions
Capability definition What the enterprise is able to achieve, independent of who does it.
Capability and boundary
A capability defined by its outcome class, not by a unit or process.
Capability boundary
The class of outcomes a capability covers, apart from process, function and product.
- Which class of outcomes does this capability deliver?
- How does it differ from the process, function or product with a similar name?
Capability level
The level of detail of a capability in the map.
- At which level of the map does this capability sit, and under which parent?
- Is the hierarchy built without using the organisation chart as the taxonomy?
Assessment and realisation How mature a capability is and what realises it.
Maturity assessment
An assessment bound to a named methodology and date.
Assessment method
The methodology, scale and evidence behind a maturity rating.
- Which methodology and scale were used for the maturity rating?
- Which evidence supports the rating, and when was it taken?
Realisation
Units, processes and systems that realise a capability, each as a separate link.
Realisation links
Links from people, processes and systems to the capability they support.
- Which units, processes and systems realise this capability today?
- Does a supporting system realise the capability fully or only partly?
- After a reorganisation, did the capability keep its identifier?
Classifiers Filled
- Family
- Enterprise profiles
- Category
- Enterprise subject
- Entry kind
- subject
- Domain
- EnterpriseSTR
- Industry
- Cross-industry
- Tags
- EM-STR-03W2subjectBusinessCapabilityCapabilityLevelCapabilityAssessmentCapabilityRealization
What it is Filled
The enterprise's ability to achieve a defined class of outcomes independently of the current structure and means of implementation.
Why it exists Filled
The enterprise's ability to achieve a defined class of outcomes independently of the current structure and means of implementation.
Distinguishing features Filled
- A capability survives reorganisation; only its realisations change.
- A capability is defined by its outcomes, not by a department name.
- A maturity rating is meaningful only with the methodology that produced it.
- Distinct from processes and applications, which realise capabilities rather than define them.
What robots and AI may and may not do Filled
Must not
- Use a department name as the sole definition of a capability.
- Renumber or recreate capabilities after a reorganisation.
- State a maturity level without naming the methodology.
- Treat a supporting system as realising a capability in full without evidence.
- Derive headcount or layoff decisions from capability gaps.
Only with a human decision
- Approving changes to the capability map structure.
- Approving maturity ratings used for investment decisions.
May
- Map units, processes and systems to the capabilities they realise.
- Flag capabilities defined only by a department name.
- Show gaps where a capability has no realisation or only partial support.
- Keep capability identifiers stable when realisations move between units.
Moral aspects Filled
- Capability maps used in restructuring can affect jobs and teams.
- Unfounded maturity ratings misdirect investment and blame.
Who is affected
- Business unit leaders
- Staff in the units that realise capabilities
- Enterprise architects
Owners Filled
Steward
The head of strategy or the founder who owns strategic decisions.
Master systems
- Strategic decision log
- OKR tracking system
- Metrics registry
Links to other meta-models Filled
neighbor
- EM-OPS-01
- EM-STR-01
references
- WM-ACT-001 - conceptual-candidate
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- Identified by a stable capability identifier in the capability map, independent of unit or system names.
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition optional Filled
- A record names a capability with an outcome class and a level in a hierarchy.
- Often confused with a department, a process or an application.
Capabilities and actions required Filled
- Capability maps support impact analysis of reorganisations and system changes.
- Realisation links show where several systems support the same capability.
Hazards and failure modes required Filled
- Map decay when the org chart is copied into the capability taxonomy.
- Duplicate capabilities under different unit names.
- Maturity theatre with ratings that lack evidence.
Standards and interfaces required Filled
- The Open Group ArchiMate capability element and realisation relationship.
- APQC Process Classification Framework for coverage of processes.
- ISO/IEC 33001 concepts for process assessment.
Context of use required Filled
- Used in enterprise architecture, portfolio planning and post-merger integration.
- Applies across industries and organisation sizes.
Sources Filled
- ArchiMate: motivation, capability and realization relationships
- APQC: coverage of functions and processes
- PMI: benefit/business case; compare with a chosen OKR school and value-stream management
- The Open Group ArchiMate - Checked live (HTTP 200) on 2026-10-07.
- ESCO skills pillar - Carried over from the published world model wm-act-001-function-capability; checked live (HTTP 200) on 2026-10-09.
- O*NET Content Model - Carried over from the published world model wm-act-001-function-capability; checked live (HTTP 200) on 2026-10-09.
- Semantic Sensor Network Ontology - Carried over from the published world model wm-act-001-function-capability; checked live (HTTP 200) on 2026-10-09.
Open questions
- Where is the boundary of a capability relative to a process, a function and a product?
- How are levels of detail formed without the org structure acting as the taxonomy?
- Which methodology confirms maturity and coverage?
- Установить границу и решение reuse/extend/new по действующим спецификациям.
- Подтвердить semantic crosswalk, права и source mastership.
- Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.
Machine files
Provenance
enterprise research programme · published-partial
Built from: enterprise/models/em-str-03/brief.json, ver-cy/world-models/card-supplements/em-str-03.json
Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.