Contents
Introduction
This metamodel facilitates the management of AI Systems across an enterprise. It leverages the Technical Capability model to identify “AI Systems” (i.e. all systems that realize at least one AI technical capability) recording the type or types of AI capability realized by each AI System. The Solution caters for realization by the different component types that represent deployed software instances (Applications, Application Modules, Technology Services). It enables organizations to explore and plan the business impact of AI across their enterprise, viewing AI from the perspectives of business capabilities, organizational units, and all existing applications that interact with, or have become, AI Systems.
A sister Solution is also available that extends the scope of the Enterprise AI Management solution to include the governance of AI Systems. It is part of the Governance, Risk and Compliance Suite Module, and includes the ability to conduct Solution Health Checks of AI Systems against AI principles, policies or regulatory frameworks, and the proactive management and tracking of AI System compliance.
Both these Solutions can be extended to apply the classification of AI Systems to the contents of a technology catalog where this has been deployed using the Technology Portfolio Management Solution. See their respective configuration guide articles for details.
Enterprise AI Management Metamodel
This Solution makes use of a range of workspaces, component and reference types from Ardoq Foundation and the Ardoq Business & IT Optimization Suite. It does not involve any new component or reference types, but it does introduce two new fields.
New Fields
Field | Field Type | Description | Definition |
AI System | Calculated Checkbox | Indicates whether the component is classified as an AI System | True if the component realizes an AI Technical Capability (directly, or via a Technology Product it Deploys), if it is the parent of at least one Application Module that does so or if it is the child of a Technology Product that does so. |
AI Capability | Calculated Checkbox | Indicates whether the component represents an AI technical capability | True if the component has the name Artificial Intelligence or is a descendent of one with that name. |
The AI System field is added to the following component types:
Application - Applications can be directly referenced as realizing Technical Capabilities.
Technology Service - Technology Services can be directly referenced as realizing Technical Capabilities.
Application Module - If the detailed implementation of an application is being modeled (breaking down an Application into its constituent Modules), it may be useful to indicate that some, but not all, Application Modules realize AI capabilities. An application module can directly realize a Technical Capability, and so that Application Module’s AI System field will be set to true if it realizes at least one AI Technical Capability. Note that an Application Module that is an AI System will cause its parent Application to also be an AI System.
If a Technology Catalog has been deployed using the Technology Portfolio Management Solution, the AI System field should also be added to the Technology Product component type in the Technology Product Catalog Workspace. See Configuring the Technology Catalog in the Getting Started guide for more details.
The AI Capability field is added to the Technical Capability component type. It is used to distinguish between technical capabilities that represent a type of AI capability, and those that don’t. For this Solution to identify AI Systems, the technical capability model must contain a technical capability component with the name “Artificial Intelligence”. That component, and all components that sit within the tree descending from it, will have an AI Capability value of true.
Calculated Fields - Gremlin
AI System
(field in Application, Application Module, Technology Service and, where appropriate, Technology Product)
g.V() |
AI Capability
(field in Technical Capability)
g.V() |
Document Version
Version | Date | Responsible | Rationale |
1.0 | 10/14/25 | Simon Field | Published |