Designing, Building, and Maintaining Comprehensive and Usable Enterprise Capability Models - Glossary of Terms and Phrases
Designing, Building, and Maintaining Comprehensive and Usable Enterprise Capability Models
Chapter 2. Glossary of Terms and Phrases
The following terms provide a shared vocabulary for the document. They are included early because the same terms recur throughout the best practices.
| Term | Definition |
|---|---|
| AI Agent | A software-based agent that can use governed enterprise data, documents, knowledge pages, relationships, prompts, and reasoning patterns to search, summarize, explain, recommend, or act on behalf of users or enterprise workflows. |
| AI Runtime | The execution environment in which AI agents, prompts, retrieval logic, tools, models, policies, and governed enterprise context are used to produce AI-assisted answers, recommendations, summaries, or actions. |
| AI-Assisted Capability Modeling | Use of AI to generate, enrich, assess, maintain, publish, or improve ECM content. |
| AI/RAG Retrieval | The use of AI and Retrieval-Augmented Generation to retrieve relevant governed content, such as capability records, knowledge pages, documents, metadata, relationships, and source evidence, before generating an answer or recommendation. |
| Answerable Enterprise Question | A practical enterprise question that can be answered through governed model data, capability attributes, semantic identifiers, relationships, relationship attributes, knowledge pages, heatmaps, documents, or related Noun Type records. |
| Application Portfolio Management (APM) | The discipline of managing applications as a portfolio, including application ownership, lifecycle, cost, value, risk, duplication, modernization, rationalization, and alignment to enterprise capabilities. |
| Automatic Capability Tagging | The use of capability names, Semantic IDs, hierarchy paths, related applications, owners, SMEs, risks, controls, and other capability metadata to suggest or apply document tags automatically. |
| Branch Capability | A capability that has one or more child capabilities. A branch capability can still have its own inventory record, owner, attributes, assessment values, and relationships. |
| Capabilities Inventory | The governed inventory of capability records and attributes. It is the data foundation for the ECM. |
| Capability | An outcome-oriented enterprise ability: what the enterprise does or must be able to do, independent of the current process, application, technology, or organization that performs or supports it. |
| Capability Assessment | An evaluation of a capability using dimensions such as maturity, health, gap severity, risk, strategic importance, readiness, application support, or performance. |
| Capability Health Check | A structured review of capability condition, often combining maturity, gaps, risks, technology support, data readiness, ownership, and investment needs. |
| Capability Heatmap | A visual representation of capability assessment values, such as maturity, health, risk, investment priority, application support, or strategic importance. |
| Capability Hierarchy | The parent-child tree structure that organizes capabilities from broad enterprise areas to more specific capability nodes. |
| Capability Inventory Record | A governed data record that represents one capability in the Capabilities Inventory. It may include Semantic ID, hierarchy, name, description, owner, steward, status, maturity, health, relationships, provenance, governance metadata, assessments, and publication data. |
| Capability Knowledge Page | A wiki or intranet page generated from a capability inventory record and related Enterprise Model relationships. |
| Capability Map | A visual or structured view of the capability hierarchy. A capability map is a view of the model, not the entire model. |
| Capability Page Template | A reusable page structure used to publish a capability record as an intranet, wiki, or knowledge-management page, including attributes, relationships, navigation links, SMEs, documents, assessments, and related Enterprise Model context. |
| Capability Taxonomy | The hierarchical classification structure formed by organizing capabilities into parent-child relationships. A Capability Taxonomy can be used to classify enterprise knowledge, content, documents, systems, processes, and related records by the enterprise abilities they support or describe. |
| Capability-Based Document Classification | The practice of classifying documents by the capabilities they support, govern, evidence, describe, improve, or depend on. |
| Capability-Based Learning | A learning approach that uses the ECM to help employees, consultants, and other stakeholders understand enterprise areas, related knowledge, owners, SMEs, enabling systems, processes, documents, and improvement work. |
| Capability-Based Metadata | Metadata assigned to documents, pages, applications, processes, reports, dashboards, or other records to identify the capabilities they support, affect, govern, enable, or depend on. |
| Capability-Based Navigation | A navigation pattern that allows users to move through enterprise knowledge using capability hierarchy, parent-child links, and related Enterprise Model relationships. |
| Capability-Based Planning | Planning that uses capabilities as the anchor for strategy, investment, roadmap, modernization, rationalization, transformation, and improvement decisions. |
| EDMS Classification Node | A capability-based folder, virtual folder, managed term, metadata value, search facet, or classification point used to organize documents in an Enterprise Document Management System. |
| End-to-End Knowledge Scenario | A practical scenario that tests whether the Enterprise Capability Model can connect capabilities, applications, people, documents, risks, controls, dashboards, and improvement actions to answer real enterprise questions. |
| Enterprise Capability Management Dashboard | An executive-facing dashboard, also known as an Executive Capability Dashboard, that consolidates capability health, maturity, investment priority, strategic alignment, risk, ownership, transformation progress, and knowledge readiness into a leadership view. |
| Enterprise Capability Model (ECM) | A governed, attribute-rich, relationship-aware representation of enterprise capabilities, including hierarchy, identity, ownership, assessments, relationships, governance, and publication views. |
| Enterprise Document Management System (EDMS) | A system used to store, classify, manage, retrieve, govern, and retain enterprise documents. A Capability Taxonomy can provide EDMS metadata, categories, navigation structures, and search facets. |
| Enterprise Inventory Management | The discipline of managing governed inventories of enterprise Noun Type records, including ownership, attributes, identifiers, lifecycle status, relationships, stewardship, quality, validation, and refresh processes. |
| Enterprise Knowledge Management (EKM) | The enterprise-level discipline of capturing, organizing, governing, sharing, finding, reusing, and improving knowledge across business, technology, governance, operational, and decision-making contexts. |
| Enterprise Knowledge Taxonomy | A governed classification structure used to organize enterprise pages, documents, knowledge articles, policies, procedures, standards, training, search results, and AI-retrievable knowledge assets. |
| Enterprise Model | A governed semantic model of the enterprise that connects Noun Types such as Capabilities, Applications, Data, Processes, Value Streams, People, Organizations, Risks, Controls, Technologies, Vendors, Initiatives, Documents, and Knowledge Assets. |
| Expertise Discovery | The ability to find owners, stewards, support contacts, Subject Matter Experts, and other people or roles associated with a capability or related enterprise area. |
| Hierarchy Identifier | A positional identifier, such as 1.0 or 1.1.1, used for display, sorting, navigation, and conversation. It should not be used as durable identity. |
| Human-in-the-Loop Governance | Human review, correction, validation, approval, routing, or rejection of AI-generated or AI-suggested model content. |
| Knowledge Freshness | The degree to which capability pages, attributes, relationships, linked documents, and related knowledge assets are current, reviewed, and trusted. |
| Knowledge Graph Edge | A governed relationship between two Noun Type instances, often described by a semantic predicate and relationship attributes that explain how and why the instances are related. |
| Knowledge Management (KM) | The discipline of capturing, organizing, governing, sharing, finding, reusing, and improving enterprise knowledge so that people and systems can make better decisions and perform work more effectively. |
| Knowledge Management Measure | A measure used to determine whether the Enterprise Capability Model helps users find, reuse, trust, and maintain enterprise knowledge. Examples include page completeness, SME coverage, EDMS tagging coverage, search usage, content reuse, learning linkage, knowledge freshness, and AI retrieval quality. |
| Knowledge Management Touch-Point | A model element, attribute, relationship, page, document, heatmap, identifier, metadata field, view, or workflow that helps capture, organize, publish, retrieve, share, or reuse enterprise knowledge. |
| Leaf Capability | A capability that has no child capabilities within the current model depth. Leaf capabilities are often the most detailed governed capability records in the model. |
| Managed Term | A governed taxonomy value, often managed in a term store or metadata catalog, used to classify content consistently across repositories and search experiences. |
| Question-Driven Model Design | A modeling approach that identifies the questions stakeholders need to answer and then captures the attributes, relationships, identifiers, views, and governance data required to answer those questions. |
| Relationship Attribute | A data element that describes or qualifies a relationship between two Noun Type instances, such as relationship type, confidence, source, owner, status, effective date, review date, evidence, or criticality. |
| Semantic ID | A durable, unique, human-readable identifier for a capability. It should remain stable even when the capability moves within the hierarchy, unless the meaning of the capability materially changes. |
| Semantic Predicate | A descriptive relationship phrase that explains how one Noun Type relates to another, such as is enabled by, is owned by, is realized by, contributes to, consumes, produces, or is governed by. |
| Semantic Relationship | A meaningful governed relationship between two Enterprise Model Noun Type instances, usually expressed through a semantic predicate and supported by relationship attributes. |
| Semantically Linked Knowledge Page | An intranet, wiki, or knowledge-management page that links to related enterprise knowledge using meaningful relationship types, relationship attributes, and contextual explanations rather than generic hyperlinks only. |
| Subject Matter Expert (SME) | A person recognized as having deep practical, operational, technical, regulatory, or domain-specific knowledge about a capability or related enterprise area. |
| Taxonomy Backbone | A durable organizing spine used by systems such as intranets, wikis, EDMS platforms, enterprise search, and AI systems to classify, navigate, retrieve, and explain enterprise knowledge. |
| Technology Portfolio Management (TPM) | The discipline of managing technologies, platforms, infrastructure, tools, and technical assets as a portfolio, including lifecycle, risk, cost, standards alignment, modernization, and capability enablement. |
| Vertical Capability Page View | A published page layout that presents one capability and its attributes in a vertical field-value format so users can read the capability as a complete knowledge page rather than as a row in a wide inventory table. |
| Virtual Folder | A dynamic document grouping created from metadata or search criteria rather than a fixed physical folder path. |
How to cite this page
When referencing this page in academic work, internal standards, or external publications, include the page title, IF4IT as publisher, the URL, and your access date.
Example (informal web citation):
International Foundation for Information Technology (IF4IT). Glossary of Terms and Phrases | Designing, Building, and Maintaining Comprehensive and Usable Enterprise Capability Models. https://if4it.org/best-practices/designing-building-and-maintaining-comprehensive-and-usable-enterprise-capability-models/glossary-of-terms-and-phrases/ (accessed 2026-06-23).
See About Us for content governance and site-wide citation guidance.
Copyright for the International Foundation for Information Technology (IF4IT): 2008 - Present
Legal Disclaimers