Capabilities Inventory and Attributes on International Foundation for Information Technology (IF4IT)

Capabilities Inventory and Attributes

Mon, 01 Jan 0001 00:00:00 +0000

About This Inventory

The Capabilities Inventory governs the enterprise capability map — the structured, hierarchical taxonomy of every distinct area of organizational ability that the enterprise performs, intends to perform, or has decided to exit. A Capability is not a process, not an application, and not a technology: it is an outcome-oriented description of what the enterprise does or must do, independent of who currently does it, which system supports it, or how it is organized today. The inventory records each Capability as a governed Noun Instance with a unique Semantic ID, a full hierarchical path from root to leaf, a description precise enough to distinguish it from adjacent Capabilities, and the full set of governance attributes needed to assess its maturity, prioritize investment, identify who performs the work, and connect the Capability to the rest of the Enterprise Model.

Capabilities Inventory and Attributes

Mon, 01 Jan 0001 00:00:00 +0000

The following terms are used throughout this document with specific meanings. Terms defined in the IF4IT Enterprise Inventory Management Best Practices document or in discipline-specific Best Practices documents (APM, TPM, etc.) are not duplicated here — refer to those documents for broader inventory governance and discipline-specific vocabulary.

Term	Definition
Capability	A discrete, outcome-oriented area of organizational ability — what the enterprise does or must do, independent of how it is currently organized, which process performs it, or which technology supports it. Stable across organizational changes; processes and technologies are not.
Capability Hierarchy	The structured tree of Capabilities organized from a root (Level 0, the enterprise) through Level 1 branches and downward into successively more specific sub-capabilities. Every Capability except the root has exactly one parent Capability.
Capability Map	The complete, governed representation of the enterprise Capability Hierarchy in a visual or structured format. The Capabilities Inventory is the data foundation of the Capability Map.
Function	A specific organized activity the enterprise performs. In some frameworks Function is distinguished from Capability; in the IF4IT model both are treated as Capabilities, with function-level nodes appearing as deeper-level entries in the hierarchy.
Latent Capability	A Capability that the enterprise possesses but has not yet exercised — abilities that exist in potential because the people, systems, and authority are in place, but no organized activity is currently performed.
Aspirational Capability	A target-state Capability the enterprise is building toward as part of a strategy or transformation. The Capability is planned but not yet active.
Decayed Capability	A Capability the enterprise formally retains but where competence has eroded — the activity continues but at degraded performance, often because of staff loss, deprecated technology, or process drift.
Semantic ID	The structured, human-readable, AI-friendly unique identifier assigned to every Capability following the enterprise naming convention. For Capabilities, the path-based form (e.g., /Enterprise/Core Business Capabilities/Human Capital Management/Resource Training and Education) is recommended; the tokenized form (e.g., CAP-FIN-AP-INV-PROC) remains acceptable. Permanent and never reused once assigned.
Hierarchy Identifier	A dotted-notation positional identifier (e.g., 1.1.2.3) reflecting a Capability’s current position in the hierarchy. Used for sorting, compact display, and conversational reference. Positional and changes with reorganization — must not be used as a durable cross-reference identifier.
Leaf Capability Name	The terminal segment of a Capability’s hierarchical path — the name of the Capability considered in isolation from its ancestors. Derived from the final segment of the Semantic ID when the path-based form is used.
Parent Capability Path	The full path from the root of the Capability Hierarchy to the immediate parent of a given Capability, expressed as a forward-slash-delimited string ending with a trailing slash (e.g., /Enterprise/Core Business Capabilities/Human Capital Management/). The root has a Parent Capability Path of “Not Applicable”.
Business Classification	The broad business domain to which a Capability belongs, drawn from the IF4IT recommended top-level decomposition: Industry-Specific, Core Business, or Information Technology (IT). Corresponds directly to the three Level 1 branches of the recommended Capability Hierarchy.
Owning Organization	The organizational unit that has administrative ownership of a Capability and is fully accountable for it — typically the unit where the Business Owner sits. Distinct from Service Organization.
Service Organization	The organizational unit that actually performs the day-to-day work related to a Capability. May be the same as the Owning Organization or different (when work is delegated, outsourced, or run by a shared-services unit). May be internal, external, or hybrid.
Investment Priority	The enterprise’s stated direction for capability investment: Invest (actively develop and strengthen), Sustain (maintain at current level), or Disinvest (reduce investment and plan for exit).
Assessed Maturity	A practitioner evaluation of how well the enterprise performs a Capability relative to peers and industry standards: Exceeds Industry, On-Par w/ Industry, Lags Industry, or Non-Existing.

Capabilities Inventory and Attributes

Mon, 01 Jan 0001 00:00:00 +0000

The Capabilities Inventory governs every Capability the enterprise performs, intends to perform, or has explicitly decided to exit. A Capability qualifies for an entry when it represents a distinct, named, outcome-oriented area of organizational ability that can be assessed, owned, and invested in independently of adjacent Capabilities. Every entry is a Noun Instance of the Capability Noun Type — a unique Capability with its own Semantic ID, its own position in the hierarchy, its own owner, its own service organization, and its own maturity and investment profile.

Capabilities Inventory and Attributes

Mon, 01 Jan 0001 00:00:00 +0000

Enterprise Architecture depends on this inventory as the primary lens through which it describes the current and target state of the enterprise. The Capability Map — derived from this inventory — is the stable, agreed-upon vocabulary for describing what the enterprise does. Without it, architectural assessments, target state designs, and roadmaps are built on informal and inconsistent terminology. Enterprise Architecture uses this inventory to identify capability gaps, define the target capability state, and build roadmaps that connect technology change to business capability improvement. Every inventory contributes to the Enterprise Model; the Capabilities Inventory contributes the business lens through which all other Enterprise Model nodes are interpreted.

Capabilities Inventory and Attributes

Mon, 01 Jan 0001 00:00:00 +0000

The Capabilities Inventory has a direct seeding relationship with the Applications Inventory and Attributes. Applications support Capabilities — every Application record references one or more Capabilities it enables. The Capabilities Inventory is authoritative for Capability definitions; the Applications Inventory is authoritative for Application records and for the specific mapping of Applications to Capabilities. The connecting attribute is the Capability Semantic ID, carried in the Applications Inventory’s Supported Capabilities attribute.

The Capabilities Inventory feeds the Value Streams Inventory (not yet published — refer to the IF4IT Enterprise Inventory Management Best Practices document for its current definition in the Noun Type taxonomy). Value Streams are composed of Capabilities. A Value Stream record will reference the Capabilities it orchestrates to deliver value to a customer or stakeholder.

Capabilities Inventory and Attributes

Mon, 01 Jan 0001 00:00:00 +0000

The Capabilities Inventory is one of the recognized Noun Types in the IF4IT Enterprise Inventory Management taxonomy — the master catalog of all enterprise inventory types. The full taxonomy, its governance principles, and the Inventory of Inventories are documented in the IF4IT Enterprise Inventory Management Best Practices document. Practitioners should read that document to understand how the Capabilities Inventory fits within the broader enterprise governance framework.

Within the Noun Type taxonomy, Capability is one of the most highly connected Noun Types. The most directly related Noun Types, each with its named relationship, are: (1) Application — an Application supports one or more Capabilities; refer to the Applications Inventory and Attributes for the published Applications Inventory. (2) Value Stream — a Value Stream is composed of one or more Capabilities. The Value Streams Inventory is not yet published — refer to the IF4IT Enterprise Inventory Management Best Practices document. (3) Organizational Unit — an Organizational Unit owns and performs one or more Capabilities; this relationship is the primary accountability and operational-delivery mapping in the Enterprise Model. The Organizational Units Inventory is not yet published — refer to the IF4IT Enterprise Inventory Management Best Practices document. (4) Data and Information Type — a Capability consumes Key Input Data types and produces Key Output Data types; refer to the Data and Information Inventory and Attributes for the published Data and Information Inventory. (5) IT Portfolio — an IT Portfolio is governed and prioritized by the Capabilities it serves. The IT Portfolios Inventory is not yet published — refer to the IF4IT Enterprise Inventory Management Best Practices document. (6) Process — a Process operationalizes a Capability through sequenced activities. The Processes Inventory is not yet published — refer to the IF4IT Enterprise Inventory Management Best Practices document. (7) Vendor — a Vendor materially supports delivery of a Capability through products, services, or outsourced work; refer to the Vendors Inventory and Attributes for the published Vendors Inventory. (8) Regulatory Obligation — a Regulatory Obligation binds a Capability when an enterprise obligation is materially performed within that Capability. The Regulatory Obligations Inventory is not yet published — refer to the IF4IT Enterprise Inventory Management Best Practices document.

Capabilities Inventory and Attributes

Mon, 01 Jan 0001 00:00:00 +0000

Section A — Sourcing and Harvesting

Before building the Capabilities Inventory from scratch, assess whether capability definitions already exist in any form in the enterprise. Common sources include Enterprise Architecture tools and repositories — Archimate-based platforms, LeanIX, Bizzdesign, Sparx EA, and similar EA tools often contain partial or full capability maps; strategic planning documents and business architecture deliverables; and industry-standard capability frameworks that can be adapted as a starting point — BIZBOK (Business Architecture Guild) for general business capabilities, eTOM for telecommunications, BIAN for banking, HL7 FHIR for healthcare, and similar domain-specific frameworks. Harvesting from any of these sources reduces the initial definition effort and surfaces capability thinking that already exists in the organization but may not be formally governed.

Capabilities Inventory and Attributes

Mon, 01 Jan 0001 00:00:00 +0000

Descriptive attributes capture the core identity of each Capability Noun Instance — what it is called, what it means, where it sits in the hierarchy, and the alternate names by which it is known across the enterprise.

Attribute Name	Maturity	Description and Notes
UID	Crawl	Description — A machine-readable system identifier generated by any source system that created or imported this Capability record. Optional — populated only when the Capability is sourced from an external system that assigns its own identifiers. Benefit(s) — Enables automated reconciliation between the Capabilities Inventory and source systems without relying solely on name matching. Source — Manual Examples — CAP-00147, BCE-2041, LX-CAP-009832 Notes — Complements the Semantic ID. Leave empty when no source system generates an ID. Never reused after retirement.
Semantic ID	Crawl	Description — A unique, human-readable, self-documenting identifier assigned to every Capability following the enterprise naming convention. Permanent and never reused once assigned. The connective tissue of the Enterprise Model — enables cross-inventory traversal without ambiguity. Benefit(s) — Eliminates ambiguity when the same Capability is referenced across APM, TPM, Enterprise Architecture deliverables, and the Enterprise Model. Enables AI-assisted cross-inventory traversal without ETL transformation. Source — Manual Examples — /Enterprise/Core Business Capabilities/Human Capital Management/Resource Training and Education (path-based form); CAP-FIN-AP-INV-PROC (tokenized form) Notes — For hierarchical Noun Types like Capabilities, the path-based form is recommended — the full path from root to node provides a natural, unambiguous, self-describing identifier that encodes the Capability’s position in the hierarchy. The tokenized form (CAP-{L1Domain}-{L2Domain}-{ShortName}) remains an acceptable alternative for enterprises that prefer compact identifiers. Unlike the Hierarchy Identifier, which is positional and changes with reorganization, the Semantic ID identifies the Capability for the life of the inventory regardless of subsequent structural changes.
Hierarchy Identifier	Crawl	Description — A dotted-notation positional identifier reflecting the Capability’s current position in the hierarchy. Useful for compact display, natural-order sorting, and conversational reference. Benefit(s) — Provides a short, sortable handle for every Capability that fits in tight display contexts where the full Semantic ID is too long. Source — Manual Examples — 1.0, 1.3, 1.3.2 Notes — CAVEAT — this value is not a unique identifier and must not be used as one. It is positional and changes whenever the hierarchy is reorganized — when Capabilities are reordered, inserted, moved, or removed. A given Hierarchy Identifier does not durably refer to the same Capability over time. For durable cross-references, use the Semantic ID. The Hierarchy Identifier is a display convenience; the Semantic ID is the identity.
Display Name	Crawl	Description — The plain-English name of the Capability as it appears in capability maps, reports, dashboards, and practitioner communications. Benefit(s) — Produces a capability map immediately readable by business stakeholders. Separates permanent identity (Semantic ID) from current preferred label. Source — Manual Examples — Invoice Processing, Sales Opportunity Management, Vulnerability Management
Leaf Capability Name	Walk	Description — The terminal segment of the Capability’s hierarchical path — the name of the Capability considered in isolation from its ancestors. Derived from the final path segment of the Semantic ID when the path-based form is used. Benefit(s) — Provides a queryable column for the terminal name that distinguishes label drift from identity change. Source — Derived Examples — Resource Training and Education, Invoice Processing, Vulnerability Management Notes — For most Capabilities, this value is identical to the Display Name. The two attributes serve different roles. Display Name is the label used in human-facing contexts and may be updated for clarity without changing the Capability’s identity. Leaf Capability Name reflects the path-encoded position and changes only when the Capability’s Semantic ID changes. When the two values differ, it signals that the Capability’s display label has been updated since its position in the hierarchy was last reset.
Description	Crawl	Description — A comprehensive description of the Capability — what the enterprise does or must be able to do in this capability area, the outcomes it produces, and how it differs from adjacent Capabilities. Benefit(s) — The quality of the Description is the most important predictor of whether the Capabilities Inventory remains usable over time. Source — Manual Notes — Write in terms of outcomes and abilities, not activities or tools. Good: “The ability to receive, validate, and process supplier invoices.” Poor: “AP team uses SAP to process vendor bills.”
Parent Capability Path [Hierarchical]	Crawl	Description — The full path from the root of the Capability Hierarchy to the immediate parent of this Capability, expressed as a forward-slash-delimited string ending with a trailing slash. A root-level Capability has a Parent Capability Path of “Not Applicable”. Benefit(s) — Provides complete hierarchical positioning in a single attribute. Enables path-based queries. Source — Manual Examples — /Enterprise/Core Business Capabilities/Human Capital Management/ (Level 4 parent); /Enterprise/ (Level 2 parent); Not Applicable (root) Notes — Use Display Names, not Semantic IDs, in the path. Update on all descendants when a parent’s Display Name changes. The path always ends in a trailing slash to distinguish it from terminal node references.
Aliases / Alternate Names [Multi-Value]	Walk	Description — Other names by which this Capability is known across the enterprise — synonyms, predecessor names from prior taxonomies, team-specific vocabulary, or external framework names that map to this Capability. Benefit(s) — Eliminates cross-document reconciliation failures when the same Capability is referenced by different names in different artifacts. Supports AI-assisted name resolution during inventory harvesting. Source — Manual Examples — AP Processing; Vendor Invoice Management; Supplier Bill Handling Notes — Separate multiple aliases with semicolons. Use Not Applicable when no aliases exist.

Capabilities Inventory and Attributes

Mon, 01 Jan 0001 00:00:00 +0000

Classification attributes position each Capability within the enterprise taxonomy — its level in the hierarchy, its broad business classification, and any regulatory characteristics that govern its handling.

Attribute Name	Maturity	Description and Notes
Capability Level	Crawl	Description — The depth level of this Capability in the Capability Hierarchy, expressed as an integer. Root-level Capabilities are Level 0; their direct children are Level 1; and so on. Benefit(s) — Enables filtering the capability map at different levels of granularity. Source — Manual Examples — 0, 1, 2, 3, 4 Notes — At Run maturity, derived from the Parent Capability Path — level equals path segments plus one. The IF4IT recommended baseline is Levels 0 through 4, with Level 4 typically being leaves. The framework imposes no hard depth limit — enterprises that require deeper decomposition into function-level or sub-function-level detail are free to extend the hierarchy as deep as their analytical needs require. Conversely, enterprises with a smaller operational footprint may stop at Level 2 or Level 3 if deeper decomposition adds no governance value.
Business Classification	Crawl	Description — The broad business domain to which this Capability belongs, drawn from the IF4IT recommended top-level decomposition. Benefit(s) — Enables portfolio-level analysis by capability type. Aligns the inventory with the recommended three-branch top-level structure of the Capability Hierarchy. Source — Manual Examples — Industry-Specific, Core Business, Information Technology (IT) Notes — Valid values: Industry-Specific │ Core Business │ Information Technology (IT). This attribute corresponds directly to the three Level 1 branches of the recommended Capability Hierarchy. Industry-Specific Capabilities are abilities that define what kind of enterprise the organization is. Core Business Capabilities are abilities every enterprise needs to function regardless of industry. Information Technology (IT) Capabilities are abilities required to acquire, deliver, operate, and govern the technology that supports the enterprise.
Regulatory Sensitivity	Walk	Description — The degree to which this Capability touches regulated data, processes, or activities subject to external compliance oversight. Benefit(s) — Surfaces Capabilities whose governance must accommodate regulatory considerations alongside business considerations. Drives selective application of compliance controls. Source — Manual Examples — None, Standard, Elevated, Highly Regulated Notes — Valid values: None │ Standard │ Elevated │ Highly Regulated. Distinguishes Capabilities that incidentally handle some regulated data from Capabilities that exist substantially to satisfy regulatory requirements.

Capabilities Inventory and Attributes

Mon, 01 Jan 0001 00:00:00 +0000

Ownership and Stakeholder attributes identify who is accountable for each Capability, who performs the work, who has executive sponsorship of its development, and who fills the IT accountability role that complements the business owner.

Attribute Name	Maturity	Description and Notes
Business Owner	Crawl	Description — The named individual or role in the business accountable for the performance, maturity, and strategic direction of this Capability. Benefit(s) — Establishes clear accountability for capability performance and maturity improvement. Source — Manual Examples — VP of Finance (Finance capabilities), Chief Marketing Officer (Customer Engagement capabilities)
Executive Sponsor	Walk	Description — The executive-level leader who sponsors the strategic development of this Capability — typically one level above the Business Owner. Benefit(s) — Enables escalation paths for capability maturity improvement efforts requiring cross-functional authority. Source — Manual Examples — CFO (Finance domains), Chief Revenue Officer (Sales capabilities), CIO (IT capabilities)
Capability Steward	Walk	Description — The named individual or role responsible for the day-to-day governance of this Capability’s inventory record — its definition, attribute currency, hierarchy position, and ongoing maintenance. Benefit(s) — Separates accountability for outcomes (Business Owner) from responsibility for the inventory record (Capability Steward). Inventories where these two roles are conflated experience governance decay as Business Owners delegate without delegating responsibility. Source — Manual Examples — Senior Enterprise Architect, Business Architecture Lead, Capability Management Analyst
Owning Organization	Walk	Description — The organizational unit that has administrative ownership of the Capability and is fully accountable for it. Typically the unit where the Business Owner sits. Benefit(s) — Places the Capability in the enterprise organizational hierarchy. Supports organizational design analysis and ownership-gap detection. Source — Manual Examples — Finance Operations, Marketing, IT Infrastructure Notes — Distinct from Service Organization, which identifies who actually performs the work. For Capabilities performed in-house by the owning team, the two values are the same.
Service Organization	Walk	Description — The organizational unit that actually performs the day-to-day work related to the Capability. May be the same as the Owning Organization or different. May be internal, external (vendor), or hybrid. Benefit(s) — Distinguishes administrative ownership from operational execution — a distinction that becomes critical when Capabilities are delegated, outsourced, or run by shared-services units. Surfaces the unit whose tools, processes, and contracts must be inspected to fully understand the Capability’s operational realities. Source — Manual Examples — Shared Services Center, Offshore Captive — Bangalore, Accenture (outsourced) Notes — When the Service Organization is external, the Vendor and Supplier Attributes category captures additional commercial context. When it differs from the Owning Organization, both values should be populated explicitly.
IT Capability Owner	Walk	Description — The named individual or role in IT accountable for the technology and systems supporting this Capability. Benefit(s) — Creates a named IT accountability point for each business Capability — preventing capability gaps from falling between business and IT. Source — Manual Examples — Director of Enterprise Applications, VP of Data and Analytics, Head of Infrastructure

Capabilities Inventory and Attributes

Mon, 01 Jan 0001 00:00:00 +0000

Lifecycle and Status attributes track the current state of each Capability and the key dates associated with lifecycle transitions.

Attribute Name	Maturity	Description and Notes
Lifecycle Status	Crawl	Description — The current state of the Capability in its governed lifecycle. Benefit(s) — Enables the capability map to distinguish actively governed capabilities from those in transition or exited. Source — Manual Examples — Proposed, Active, Under Review, Deprecated, Retired Notes — Valid values: Proposed, Active, Under Review, Deprecated, Retired. Status changes require inventory owner approval.
Effective Date	Walk	Description — The date on which this Capability became Active. Benefit(s) — Enables longitudinal analysis of how the enterprise capability portfolio has evolved. Source — Manual Examples — 2024-01-01, 2022-07-15
Planned Retirement Date	Walk	Description — The date on which this Capability is planned to reach Retired status. Populated only for Capabilities in Deprecated status. Benefit(s) — Enables transition planning for capabilities scheduled for retirement. Source — Manual Examples — 2026-12-31, 2025-06-30 Notes — Use Not Applicable for Active and Proposed Capabilities.

Capabilities Inventory and Attributes

Mon, 01 Jan 0001 00:00:00 +0000

Governance attributes document the frameworks, bodies, and review processes that govern each Capability — and the dates that anchor the governance cycle.

Attribute Name	Maturity	Description and Notes
Governing Framework	Walk	Description — The capability framework or standard that informed the definition and classification of this Capability. Benefit(s) — Enables traceability between the enterprise capability map and external standards. Source — Manual Examples — BIZBOK (Business Architecture Guild), eTOM (Telecommunications), BIAN (Banking), HL7 (Healthcare), TOGAF, Enterprise-Defined Notes — If no external framework was used, enter Enterprise-Defined.
Governing Body	Walk	Description — The organizational body or function responsible for approving changes to this Capability’s definition, hierarchy position, and governance attributes. Benefit(s) — Ensures changes to the capability map are governed rather than informal. Source — Manual Examples — Enterprise Architecture Review Board, Business Architecture Committee, Portfolio Governance Board
Review Cadence	Walk	Description — How often this Capability record is formally reviewed for accuracy, completeness, and currency. Benefit(s) — Ensures governance attention is proportional to strategic importance. Source — Manual Examples — Quarterly, Semi-Annual, Annual Notes — Minimum: Annual for all Active Capabilities. Quarterly recommended for Investment Priority = Invest or Business Importance = Very High.
Last Reviewed Date	Walk	Description — The date on which this Capability record was most recently reviewed under its governance cadence. Benefit(s) — Surfaces Capabilities whose review is overdue against the established cadence. Anchors the audit trail of inventory governance activity. Source — Manual Examples — 2026-03-15, 2025-12-01
Next Review Date	Walk	Description — The next scheduled review date for this Capability, computed from the Last Reviewed Date and the Review Cadence. Benefit(s) — Drives the inventory’s governance work queue. Makes upcoming review obligations visible without requiring computation. Source — Derived Examples — 2026-09-15, 2026-12-01 Notes — At Crawl maturity, populated manually. At Walk and Run maturity, derived automatically from Last Reviewed Date plus Review Cadence.

Capabilities Inventory and Attributes

Mon, 01 Jan 0001 00:00:00 +0000

Strategic attributes capture the enterprise’s stated direction for each Capability — how important it is, what the investment intention is, how it aligns to strategic goals, and how investment in it is currently classified.

Attribute Name	Maturity	Description and Notes
Investment Priority	Crawl	Description — The enterprise’s stated intention for investment in this Capability: whether to actively grow and strengthen it, maintain it at current levels, or reduce investment and plan for exit. Benefit(s) — Drives portfolio investment decisions in APM and TPM by connecting technology investment to explicit capability-level intentions. Source — Manual Examples — Invest, Sustain, Disinvest Notes — Valid values: Invest, Sustain, Disinvest. Must be set by the Business Owner with Executive Sponsor approval. The single most consequential governance attribute in this inventory.
Business Importance	Walk	Description — The Business Owner’s assessment of how critical this Capability is to the enterprise’s ability to operate and compete. Benefit(s) — Enables risk-weighted portfolio analysis — identifying high-importance capabilities underpowered by their supporting technology. Source — Manual Examples — Very High, High, Medium, Low, Very Low Notes — Valid values: Very High │ High │ Medium │ Low │ Very Low. Assessed annually.
Strategic Goals Alignment [Multi-Value]	Walk	Description — The enterprise strategic goals or objectives that this Capability directly enables or supports. Benefit(s) — Creates a traceable link from the capability portfolio to executive-level strategic intent. Source — Manual Examples — Customer Experience Transformation; Revenue Growth; Operational Efficiency; Regulatory Compliance; Digital Innovation Notes — Use official strategic goal names. Separate multiple values with semicolons.
Investment Tier	Walk	Description — The portfolio tier into which investment in this Capability is currently classified — distinct from the investment direction expressed by Investment Priority. Benefit(s) — Aligns capability investment with the standard IT investment portfolio model. Enables portfolio-level analysis of investment concentration across run, grow, and transform tiers. Source — Manual Examples — Run, Grow, Transform Notes — Valid values: Run │ Grow │ Transform. Run investments sustain current operational performance; Grow investments expand capacity or extend current capabilities; Transform investments fundamentally reshape what the Capability does.

Capabilities Inventory and Attributes

Mon, 01 Jan 0001 00:00:00 +0000

Assessment and Health attributes capture the evaluated state of each Capability — how mature it is, where the gaps are, and how its overall health scores when measured against assessed dimensions.

Attribute Name	Maturity	Description and Notes
Assessed Maturity	Crawl	Description — A practitioner assessment of how well the enterprise performs this Capability relative to industry peers and best practices. Benefit(s) — The single most valuable attribute for connecting the capability map to investment decisions. Source — Manual Examples — Exceeds Industry, On-Par w/ Industry, Lags Industry, Non-Existing Notes — Valid values: Exceeds Industry, On-Par w/ Industry, Lags Industry, Non-Existing. Assessed annually.
Gap Status	Walk	Description — The assessed severity of the gap between the current state of this Capability and the enterprise’s target state. Benefit(s) — Produces a prioritized capability gap register without complex analysis. Source — Manual Examples — No Gap, Minor Gap, Significant Gap, Critical Gap Notes — Valid values: No Gap, Minor Gap, Significant Gap, Critical Gap.
Capability Health Score	Run	Description — A calculated 0–100 composite score representing overall health across assessed dimensions: maturity, gap severity, investment alignment, and performance against KPIs. Benefit(s) — Enables portfolio-level capability health dashboards without manual synthesis. Source — Calculated Notes — Calculation methodology is enterprise-defined. Starting approach: weight Assessed Maturity (40%), investment alignment (30%), Gap Status (30%).

Capabilities Inventory and Attributes

Mon, 01 Jan 0001 00:00:00 +0000

Technical attributes capture the architectural and technology characteristics that define how this Capability is enabled by IT systems, architectural patterns, and realization models.

Attribute Name	Maturity	Description and Notes
Key Enabling Technologies [Multi-Value]	Walk	Description — The primary technology types, platforms, or architectural categories that currently enable delivery of this Capability. Benefit(s) — Enables technology-to-capability alignment analysis. Identifies capabilities that are technology-constrained. Source — Manual Examples — ERP (SAP S/4HANA); RPA; AI/ML; Cloud SaaS; Data Warehouse; API Integration Platform Notes — Use technology category names, not product names. Separate multiple values with semicolons.
Architecture Patterns [Multi-Value]	Run	Description — The architectural patterns governing technical design of systems supporting this Capability. Benefit(s) — Enables architectural coherence analysis: are high-priority capabilities supported by modern, scalable architectures? Source — Manual Examples — Microservices; Event-Driven; API-First; Data Mesh; Monolithic (Legacy) Notes — Separate multiple values with semicolons.
Capability Realization Pattern	Walk	Description — The pattern by which the work of this Capability is realized in practice. Benefit(s) — Captures the realization model at a higher level of abstraction than Architecture Patterns. Distinguishes Capabilities delivered by fully automated systems from those delivered manually, by external providers, or by hybrid arrangements. Source — Manual Examples — Internal Automated, Internal Manual, Outsourced, Hybrid, Shared Service Notes — Valid values: Internal Automated │ Internal Manual │ Outsourced │ Hybrid │ Shared Service.

Capabilities Inventory and Attributes

Mon, 01 Jan 0001 00:00:00 +0000

Operational attributes capture how Capability performance is measured, what the target performance levels are, and when the Capability is operationally active.

Attribute Name	Maturity	Description and Notes
Key Performance Indicators [Multi-Value]	Walk	Description — The KPIs used to measure the operational performance of this Capability. Benefit(s) — Connects the capability map to measurable business outcomes. Source — Manual Examples — Invoice Processing Cycle Time (days); First-Pass Approval Rate (%); Customer Satisfaction Score Notes — Separate multiple KPIs with semicolons. Focus on outcome KPIs.
Target Performance Level	Walk	Description — The defined target for the Capability’s primary KPI. Benefit(s) — Creates a measurable target against which Assessed Maturity can be calibrated. Source — Manual Examples — ≤5 days invoice processing cycle time; ≥92% first-pass approval rate
Operational Hours	Walk	Description — When the Capability is operationally active — the time pattern across which the work is performed and consumers can rely on it. Benefit(s) — Distinguishes 24×7 mission-critical Capabilities from business-hours Capabilities and from batch or scheduled Capabilities. Drives support and continuity planning. Source — Manual Examples — 24×7, Business Hours (Mon–Fri 8am–6pm), Batch (Nightly), Scheduled (Monthly Close)

Capabilities Inventory and Attributes

Mon, 01 Jan 0001 00:00:00 +0000

Security attributes capture the security classification and access considerations associated with this Capability and its governing data.

Attribute Name	Maturity	Description and Notes
Security Classification	Walk	Description — The sensitivity classification of the information associated with this Capability. Benefit(s) — Enables capability-level security architecture. Surfaces capabilities where data sensitivity drives technology selection constraints. Source — Manual Examples — Public, Internal, Confidential, Restricted, Regulated Notes — Reflects the highest sensitivity of any data touched by the capability.
Access Restrictions	Walk	Description — Specific access limitations that apply to who can view or modify records about this Capability beyond the default inventory access controls. Benefit(s) — Enables selective confidentiality for capabilities whose strategic attributes are competitively sensitive. Source — Manual Examples — Executive Leadership only, EA Team and Business Owner only, No additional restrictions Notes — Most Capabilities will have No additional restrictions.

Capabilities Inventory and Attributes

Mon, 01 Jan 0001 00:00:00 +0000

Data and Information attributes capture the data that flows into and out of each Capability — connecting the capability map to the enterprise data architecture.

Attribute Name	Maturity	Description and Notes
Key Input Data and Information [Multi-Value]	Walk	Description — The primary Data and Information Types that this Capability consumes as inputs. Benefit(s) — Creates capability-level data lineage. Enables impact analysis when a data source changes. Source — Manual Examples — Supplier Invoice Data; Purchase Order Data; Goods Receipt Data; Vendor Master Data Notes — Separate multiple values with semicolons. When the Data and Information Types Inventory is published, update to reference its Semantic IDs.
Key Output Data and Information [Multi-Value]	Walk	Description — The primary Data and Information Types that this Capability produces as outputs. Benefit(s) — Identifies which capabilities are authoritative sources for which data types. Source — Manual Examples — Approved Payment Instructions; Vendor Payment Records; Accounts Payable Aging Reports Notes — Separate multiple values with semicolons.
Data Sensitivity	Walk	Description — The overall data sensitivity level for this Capability — the highest sensitivity classification of any data type it produces or consumes. Benefit(s) — Provides a single-attribute summary of the data risk profile. Source — Manual Examples — Public, Internal, Confidential, Restricted, Regulated

Capabilities Inventory and Attributes

Mon, 01 Jan 0001 00:00:00 +0000

Geographic and Jurisdictional attributes capture where this Capability is performed and which regulatory jurisdictions govern its execution.

Attribute Name	Maturity	Description and Notes
Geographic Scope	Walk	Description — The geographic extent across which this Capability is performed. Benefit(s) — Enables identification of capabilities requiring multi-jurisdictional compliance management. Source — Manual Examples — Global, North America, EMEA, APAC, United States, United Kingdom Notes — For capabilities performed in multiple but not all regions, list regions separated by semicolons.
Operating Jurisdiction [Multi-Value]	Walk	Description — The legal and regulatory jurisdictions within which this Capability operates. Benefit(s) — Surfaces the compliance and regulatory obligations that apply to each Capability area. Source — Manual Examples — United States (SOX, CCPA); European Union (GDPR); United Kingdom (FCA); Canada (PIPEDA) Notes — Separate multiple jurisdictions with semicolons.

Capabilities Inventory and Attributes

Mon, 01 Jan 0001 00:00:00 +0000

Temporal and Effective Date attributes capture the validity windows for Capabilities that are time-bounded.

Attribute Name	Maturity	Description and Notes
Effective From	Walk	Description — The date from which this Capability is recognized as part of the governed enterprise capability portfolio. Benefit(s) — Supports longitudinal capability portfolio analysis. Source — Manual Examples — 2024-01-01, 2023-07-01

Capabilities Inventory and Attributes

Mon, 01 Jan 0001 00:00:00 +0000

Contractual and Legal attributes capture any legal instruments that govern the performance or delivery of this Capability.

The IF4IT has not yet identified standard attributes in this category for the Capabilities Inventory. This does not mean no such attributes exist — organizations building this inventory are encouraged to identify and define attributes in this category that are relevant to their specific context and governance needs.

Capabilities Inventory and Attributes

Mon, 01 Jan 0001 00:00:00 +0000

Vendor and Supplier attributes capture external parties that provide capability delivery when this Capability is outsourced or substantially supported by third-party services.

Attribute Name	Maturity	Description and Notes
Outsourcing Provider	Walk	Description — The name of the vendor or service provider that performs this Capability on behalf of the enterprise when substantially outsourced. Use Not Applicable for internally performed Capabilities. Benefit(s) — Surfaces the enterprise’s outsourcing dependency at the capability level. Source — Manual Examples — Accenture (Payroll Processing), IBM (Infrastructure Management), Cognizant (Application Development) Notes — For partially outsourced Capabilities, note the scope in parentheses.
Outsourcing Model	Walk	Description — The type of outsourcing arrangement governing delivery of this Capability when outsourced. Benefit(s) — Enables portfolio-level analysis of outsourcing model diversity and concentration. Source — Manual Examples — Full Outsourcing, Managed Service, Staff Augmentation, Co-Sourcing, BPO (Business Process Outsourcing) Notes — Use Not Applicable for internally performed Capabilities.

Capabilities Inventory and Attributes

Mon, 01 Jan 0001 00:00:00 +0000

IT Environment attributes capture the IT Operating Environments within which systems supporting this Capability are deployed.

Capabilities Inventory and Attributes

Mon, 01 Jan 0001 00:00:00 +0000

Skills and Competencies attributes capture the human capabilities required to perform this Capability and assess where skill gaps exist.

Attribute Name	Maturity	Description and Notes
Required Skills [Multi-Value]	Walk	Description — The primary skills and competencies practitioners must possess to perform this Capability effectively. Benefit(s) — Connects the capability map to workforce planning. Source — Manual Examples — Financial Analysis; SAP FICO Configuration; Process Automation Design; Data Visualization; Regulatory Compliance (SOX) Notes — Separate multiple skills with semicolons.
Key Roles [Multi-Value]	Walk	Description — The organizational roles or job titles primarily responsible for performing this Capability day-to-day. Benefit(s) — Supports workforce planning and organizational design. Source — Manual Examples — Accounts Payable Specialist; Finance Controller; Data Analyst; Solution Architect; DevOps Engineer Notes — Separate multiple roles with semicolons.
Skill Gap Severity	Run	Description — The assessed severity of the gap between the skills the enterprise currently has and the skills required to perform the Capability at target maturity level. Benefit(s) — Enables capability-level workforce gap analysis. Source — Manual Examples — No Gap, Minor Gap, Significant Gap, Critical Gap

Capabilities Inventory and Attributes

Mon, 01 Jan 0001 00:00:00 +0000

Provenance and Audit attributes capture metadata about the inventory record itself — how it was created, when it was last updated, and the reliability of its content.

Attribute Name	Maturity	Description and Notes
Record Created Date	Walk	Description — The date on which this Capability record was first created in the inventory. Benefit(s) — Supports audit and compliance reporting. Source — Manual Examples — 2024-03-15, 2023-11-01
Record Created By	Walk	Description — The name or role of the individual who created this Capability record. Benefit(s) — Provides accountability for record creation. Source — Manual Examples — Jane Smith (EA Lead), AI Agent (Claude, 2026-05-15)
Last Updated Date	Walk	Description — The date on which any attribute of this Capability record was last modified. Benefit(s) — Enables identification of stale records not reviewed within the expected reconciliation cadence. Source — Manual Examples — 2026-05-15, 2025-09-30
Data Source	Walk	Description — The origin of the data in this Capability record. Benefit(s) — Enables data quality assessment and reconciliation. Source — Manual Examples — LeanIX Export, BIZBOK Framework Adaptation, EA Workshop (2024-Q1) Notes — When AI-generated, document: “AI Agent (Claude, 2026-05-15) — validated by [name].”
AI-Generated	Walk	Description — Indicates whether this record was initially generated by an AI agent. AI-generated records require human validation before being considered authoritative. Benefit(s) — Maintains transparency about record provenance. Enables targeted validation. Source — Manual Examples — Yes (validated), Yes (pending validation), No Notes — Once validated, update to “Yes (validated)” and record the validator’s name in Record Created By.

Capabilities Inventory and Attributes

Mon, 01 Jan 0001 00:00:00 +0000

Risk attributes capture the known risk profile of each Capability — the likelihood and impact of capability failure or underperformance.

Attribute Name	Maturity	Description and Notes
Assessed Risk	Crawl	Description — The practitioner’s overall assessment of the risk associated with this Capability. Benefit(s) — Surfaces high-risk capabilities for priority attention in governance reviews and investment decisions. Source — Manual Examples — Very High, High, Medium, Low, Very Low Notes — Valid values: Very High │ High │ Medium │ Low │ Very Low. Assessed annually.
Key Risk Factors [Multi-Value]	Walk	Description — The specific factors driving the Assessed Risk rating. Benefit(s) — Translates the overall risk rating into actionable intelligence for mitigation planning. Source — Manual Examples — Single vendor dependency; Key person dependency; Legacy technology with no vendor support; Regulatory change exposure Notes — Separate multiple risk factors with semicolons.
Risk Trend	Run	Description — The direction of travel of the risk profile of this Capability over the past review period. Benefit(s) — Enables early warning of deteriorating capability risk. Source — Manual Examples — Improving, Stable, Deteriorating

Capabilities Inventory and Attributes

Mon, 01 Jan 0001 00:00:00 +0000

Compliance and Regulatory attributes capture the regulatory obligations that apply to this Capability, the current compliance status, and audit history.

Attribute Name	Maturity	Description and Notes
Regulatory Obligations [Multi-Value]	Walk	Description — The specific regulatory requirements, laws, or compliance frameworks that apply to the performance of this Capability. Benefit(s) — Connects the capability map to the regulatory compliance landscape. Source — Manual Examples — SOX Section 404; GDPR Article 17; PCI-DSS Requirement 6; HIPAA Security Rule Notes — Separate multiple obligations with semicolons.
Compliance Status	Walk	Description — The current compliance status of this Capability with respect to its applicable regulatory obligations. Benefit(s) — Enables a compliance dashboard at the capability level. Source — Manual Examples — Compliant, Partially Compliant, Non-Compliant, Under Assessment Notes — Valid values: Compliant, Partially Compliant, Non-Compliant, Under Assessment.
Last Compliance Audit Date	Walk	Description — The date on which this Capability’s compliance posture was most recently audited under its applicable regulatory framework. Benefit(s) — Supports the compliance dashboard with an audit trail. Surfaces Capabilities whose audit is overdue. Source — Manual Examples — 2026-02-10, 2025-08-22 Notes — Use Not Applicable when no compliance audit has occurred or the Capability is not subject to formal audit.

Capabilities Inventory and Attributes

Mon, 01 Jan 0001 00:00:00 +0000

Financial attributes capture the cost and value profile of each Capability — what it costs to deliver and what value it produces.

Attribute Name	Maturity	Description and Notes
Annual Delivery Cost	Walk	Description — The total annual cost to deliver this Capability, including people costs, technology costs, and any outsourcing costs. Benefit(s) — Enables capability-level financial analysis. Identifies high-cost, low-importance capabilities as rationalization candidates. Source — Manual Notes — Typically an estimated allocation at Walk maturity. A rough order of magnitude is more useful than no value.
Cost Allocation Model	Run	Description — The method by which the cost of this Capability is allocated across the business units or legal entities that consume it. Benefit(s) — Enables showback and chargeback for capability delivery costs. Source — Manual Examples — Activity-Based Costing, Usage-Based Allocation, Headcount-Based Allocation, Fixed Allocation
Value Delivered	Run	Description — The assessed business value delivered by this Capability — the quantified or qualified contribution to revenue, cost reduction, risk mitigation, or strategic differentiation. Benefit(s) — Enables ROI analysis at the capability level. Source — Manual Examples — $5M annual revenue attribution; $2M annual cost avoidance; Regulatory compliance (existential); Competitive differentiation

Capabilities Inventory and Attributes

Mon, 01 Jan 0001 00:00:00 +0000

Relationship attributes connect each Capability to related Noun Instances in other inventories, forming the edges of the Enterprise Model graph for the Capability Noun Type.

Every attribute in this category is Calculated or Derived from records in other inventories. No manual data entry is required for any attribute in this category. Do not create data entry fields for any attribute listed here.

Attribute Name	Maturity	Description and Notes
Supporting Applications [Multi-Value]	Run	Description — The Applications that support or enable this Capability, referenced by Semantic ID from the Applications Inventory. Benefit(s) — The primary cross-inventory relationship for capability-driven portfolio governance. Source — Derived Notes — Derived from the Applications Inventory: when an Application record references this Capability, that Application’s Semantic ID is reflected here.
Parent Value Streams [Multi-Value]	Run	Description — The Value Streams that this Capability composes or contributes to, referenced by Semantic ID from the Value Streams Inventory. Benefit(s) — Connects the capability map to the enterprise value delivery model. Source — Derived Notes — Derived from the Value Streams Inventory when published. Refer to the IF4IT Enterprise Inventory Management Best Practices document.
Owning Organizational Units [Multi-Value]	Run	Description — The Organizational Units that own and perform this Capability, referenced by Semantic ID from the Organizational Units Inventory. Benefit(s) — Maps organizational accountability to the capability map. Source — Derived Notes — Derived from the Organizational Units Inventory when published. Refer to the IF4IT Enterprise Inventory Management Best Practices document.
Related IT Portfolios [Multi-Value]	Run	Description — The IT Portfolios that govern investments in this Capability area, referenced by Semantic ID from the IT Portfolios Inventory. Benefit(s) — Connects capability governance to portfolio governance. Source — Derived Notes — Derived from the IT Portfolios Inventory when published. Refer to the IF4IT Enterprise Inventory Management Best Practices document.
Related Processes [Multi-Value]	Run	Description — The Processes that operationalize this Capability — the sequenced activities that realize the Capability’s outcomes in practice. Referenced by Semantic ID from the Processes Inventory. Benefit(s) — Connects the stable Capability layer to the volatile Process layer. Surfaces which Capabilities are realized by which sequenced workflows. Source — Derived Notes — Derived from the Processes Inventory when published. Refer to the IF4IT Enterprise Inventory Management Best Practices document.
Related Vendors [Multi-Value]	Run	Description — The Vendors whose products or services materially support delivery of this Capability, referenced by Semantic ID from the Vendors Inventory. Benefit(s) — Surfaces vendor dependencies at the capability level — beyond what the Outsourcing Provider attribute captures for fully outsourced delivery. Source — Derived Notes — Derived from the Vendors Inventory when published. Refer to the IF4IT Enterprise Inventory Management Best Practices document.
Related Regulatory Obligations [Multi-Value]	Run	Description — The Regulatory Obligations to which this Capability is subject, referenced by Semantic ID from the Regulatory Obligations Inventory. Benefit(s) — Connects the capability map to the structured regulatory obligation register, complementing the descriptive Regulatory Obligations attribute in the Compliance and Regulatory Attributes category. Source — Derived Notes — Derived from the Regulatory Obligations Inventory when published. Refer to the IF4IT Enterprise Inventory Management Best Practices document.
Child Capabilities [Multi-Value]	Run	Description — All direct child Capabilities of this Capability in the hierarchy. Benefit(s) — Enables hierarchical navigation of the capability map from any node without traversing the full hierarchy. Source — Calculated Notes — Calculated from within the Capabilities Inventory itself. Self-referential relationship.

Capabilities Inventory and Attributes

Mon, 01 Jan 0001 00:00:00 +0000

The relationship between Capabilities and Applications is the most operationally significant cross-inventory relationship in the Enterprise Model. Applications support Capabilities — every Application in the Applications Inventory and Attributes can be mapped to one or more Capabilities it enables. The Capabilities Inventory is the authoritative source for Capability definitions; the Applications Inventory is authoritative for Application records and for the specific mapping of Applications to Capabilities.

The connecting attributes are the Semantic IDs of both Noun Types: the Applications Inventory contains a Supported Capabilities attribute listing the Capability Semantic IDs each Application enables; the Capabilities Inventory reflects those mappings in its Supporting Applications relationship attribute, which is Derived from the Applications Inventory. The relationship is many-to-many: one Application can support multiple Capabilities, and one Capability can be supported by multiple Applications.

Capabilities Inventory and Attributes

Mon, 01 Jan 0001 00:00:00 +0000

Value Streams are composed of Capabilities — a Value Stream orchestrates one or more Capabilities in sequence or in parallel to deliver value to a customer or stakeholder. The Capabilities Inventory is the source of the Capability building blocks. The Value Streams Inventory is not yet published — refer to the IF4IT Enterprise Inventory Management Best Practices document for its current definition in the Noun Type taxonomy.

When the Value Streams Inventory is published, the connecting attributes will be Capability Semantic IDs referenced by Value Stream records; the Capabilities Inventory will reflect those references in its Parent Value Streams relationship attribute. The relationship enables analysis of which Capabilities contribute to the most important value delivery flows.

Capabilities Inventory and Attributes

Mon, 01 Jan 0001 00:00:00 +0000

Organizational Units own and perform Capabilities — the mapping between an Organizational Unit and the Capabilities it is accountable for is the primary accountability structure in the Enterprise Model. The Organizational Units Inventory is not yet published — refer to the IF4IT Enterprise Inventory Management Best Practices document for its current definition in the Noun Type taxonomy.

Within this inventory, two attributes capture organizational accountability at the unit level: Owning Organization (the unit administratively accountable) and Service Organization (the unit that actually performs the work). These two values are often the same — Capabilities performed in-house by the team that owns them — but diverge in important cases: outsourced delivery, shared-services arrangements, captive offshore operations, and similar patterns where ownership and execution are separated. The Owning Organizational Units relationship attribute in the Relationship Attributes category will capture the formal organizational accountability mapping by Semantic ID when the Organizational Units Inventory is published.

Capabilities Inventory and Attributes

Mon, 01 Jan 0001 00:00:00 +0000

Capabilities consume input data and produce output data — the Capability is the processing context that gives data types their business meaning and determines their flow through the enterprise. The Data and Information Inventory and Attributes governs the Data and Information Types of the enterprise, and is the published companion inventory to which the data-flow attributes of the Capabilities Inventory link.

The Key Input Data and Information and Key Output Data and Information attributes in this inventory carry Data and Information Type Semantic IDs from the Data and Information Inventory for precise cross-inventory linkage. The relationship is many-to-many: one Capability can consume and produce multiple data types, and one data type can flow through multiple Capabilities.

Capabilities Inventory and Attributes

Mon, 01 Jan 0001 00:00:00 +0000

IT portfolios are governed and prioritized by the Capabilities they serve — a portfolio investment decision is most defensible when grounded in the importance and maturity of the Capabilities the portfolio enables. The IT Portfolios Inventory is not yet published — refer to the IF4IT Enterprise Inventory Management Best Practices document for its current definition in the Noun Type taxonomy.

When the IT Portfolios Inventory is published, the connecting attribute will be Capability Semantic IDs referenced by IT Portfolio records; the Capabilities Inventory will reflect those references in its Related IT Portfolios relationship attribute. This bidirectional connection enables: what Capabilities does this portfolio serve, and what portfolios serve this Capability?

Capabilities Inventory and Attributes

Mon, 01 Jan 0001 00:00:00 +0000

Processes operationalize Capabilities — a Process describes the sequenced activities that realize a Capability’s outcomes in practice. The Capability is the stable answer to “what does the enterprise do”; the Process is the volatile answer to “how does the enterprise do it.” Both are valuable, but they serve different governance purposes. The Processes Inventory is not yet published — refer to the IF4IT Enterprise Inventory Management Best Practices document for its current definition in the Noun Type taxonomy.

Capabilities Inventory and Attributes

Mon, 01 Jan 0001 00:00:00 +0000

Vendors materially support delivery of Capabilities through products, services, or outsourced work. The relationship complements the Outsourcing Provider attribute in the Vendor and Supplier Attributes category — the Outsourcing Provider attribute names a single principal vendor for fully outsourced Capabilities, while the Related Vendors relationship captures the broader set of vendor dependencies including software vendors, infrastructure providers, and specialized service providers whose products materially enable the Capability. The Vendors Inventory and Attributes is the published companion inventory to which these vendor relationships link.

Capabilities Inventory and Attributes

Mon, 01 Jan 0001 00:00:00 +0000

Regulatory Obligations bind Capabilities — when a regulation creates an enterprise obligation, that obligation is materially performed within one or more Capabilities. The relationship complements the Regulatory Obligations descriptive attribute in the Compliance and Regulatory Attributes category, which lists applicable regulations as free-text values. The structured Related Regulatory Obligations relationship attribute provides Semantic ID-based linkage to the governed obligation register. The Regulatory Obligations Inventory is not yet published — refer to the IF4IT Enterprise Inventory Management Best Practices document for its current definition in the Noun Type taxonomy.

Capabilities Inventory and Attributes

Mon, 01 Jan 0001 00:00:00 +0000

The Capabilities Inventory and Attributes document is one of many Noun Type inventories in the IF4IT Enterprise Inventory Management taxonomy. Each inventory in the taxonomy governs a distinct class of enterprise asset, relationship, or organizational construct — and each contributes its records and relationships to the Enterprise Model that connects them all. The full catalog of recognized Noun Types, the principles that govern inventory design and federation, the Inventory of Inventories, and guidance for building, connecting, and maturing a complete enterprise inventory program are documented in the IF4IT Enterprise Inventory Management Best Practices document. Practitioners who find value in the Capabilities Inventory are encouraged to explore the broader taxonomy — each additional inventory that is built and governed strengthens the Enterprise Model and expands the range of questions that AI-assisted enterprise analysis can answer. The IF4IT welcomes contributions from practitioners who develop attribute categories, attribute definitions, or governance approaches not covered in this document — your real-world experience is how this framework matures.