Capabilities Inventory and Attributes - Understand where the Capabilities Inventory sits in the IF4IT Enterprise Inventory Management Noun Type Taxonomy
Capabilities Inventory and Attributes
Understand where the Capabilities Inventory sits in the IF4IT Enterprise Inventory Management Noun Type Taxonomy
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.
The Capability Noun Type is not the same as a Process, a Function, or a Value Stream. A Process describes how work is done — the sequenced activities that realize a Capability’s outcomes. A Function, in the strict sense found in some frameworks, describes an organized activity grouping; in the IF4IT model, the Capability/Function distinction is collapsed into a single concept treated as Capability throughout. A Value Stream describes end-to-end value delivery composed of multiple Capabilities. A Capability describes what the enterprise must be able to do, stable across process redesigns and organizational restructuring.
Copyright for the International Foundation for Information Technology (IF4IT): 2008 - Present
Legal Disclaimers