Metamodel

YouDesign Command (UPMX) extends the ServiceNow Common Services Data Model (CSDM) into a full enterprise portfolio model covering strategy, organisation, value, capability, application, data, technology, AI, work, and architecture. One consistent shape that any ServiceNow admin can manage and extend.

YouDesign Command (UPMX) is 100% aligned with ServiceNow CSDM. Every record lives in the CMDB. Every relationship is a CI relationship. There is nothing to learn beyond ServiceNow itself.

YouDesign Command Extensions on the ServiceNow CSDM

YouDesign Command's metamodel is the ServiceNow CSDM, extended with the concepts an enterprise portfolio practice needs. The extensions sit inside the ServiceNow scope x_inpgh_upmx (UPMX) and inherit from the same Configuration Item base class as CSDM, so they share permissions, audit, discovery, CMDB Health, and Service Graph.

YouDesign Command extensions on the ServiceNow CSDM

Vocabulary used on this page

Term	Also called	What it means
Class	Table · Object type · Component type	A category of thing in the model. Every class is backed by a ServiceNow table.
Reference	One-to-many relationship	A single-target pointer field. The "many" side stores the foreign key.
Relationship	Many-to-many · CI relationship	A two-way link between two records, stored in cmdb_rel_ci. The relationship type carries both forward and reverse verbs.
Hierarchy	Self-reference · Parent/child	A reference from a class to itself, used for tree structures (e.g., capability sub-capabilities).
Field	Property · Attribute · Column	A piece of data on a record. Fields added to x_inpgh_upmx_portfolio_element are inherited by every sub-class.

YouDesign Command Metamodel

The diagram below shows the relationships that provide a full line of sight across the enterprise. Not every class needs to be used in every architecture practice. The model is broad enough to fit different maturity levels and portfolio scopes.

YouDesign Command metamodel

Green shapes are ServiceNow CSDM tables; all other shapes are YouDesign Command extensions. Because the extensions inherit from cmdb_ci, the platform treats them as ordinary Configuration Items.

YouDesign Command BIZBOK Extensions

YouDesign Command adopts BIZBOK-aligned concepts where they add value for enterprise portfolio planning. A small number of BIZBOK concepts are intentionally not implemented because they are redundant with stronger YouDesign Command concepts or with the platform's existing target-state architecture techniques.

YouDesign Command BIZBOK extensions

Concepts intentionally not implemented

BIZBOK concept	Rationale for not implementing
Change	Redundant with Strategy, Initiative, and Project. Superseded by the YouDesign Command target-state architecture techniques (Layer, Segment, and Solution Architecture).
Course of Action	Redundant with the Strategy concept.
Capability Behavior	Implementable on a per-customer basis when demand emerges.
Process Outcome	Redundant with the business-process modelling techniques already supported by YouDesign Command; implementable per-customer when needed.
Product Entitlement	Implementable on a per-customer basis when demand emerges.

---

How to read the catalog

The sections below list every documented type as its own card. Each card shows the user-facing label, the technical table name in code, a short definition, and the relationships that the relationship picker offers from or to that type.

Verb notation. Each relationship is shown as Forward :: Reverse. The forward verb reads from this type to the other; the reverse is what the other type says back. For example, Uses :: Used by → Software Product reads as "this type Uses Software Product; Software Product is Used by this type."

Inbound vs. outbound. Inbound lists the types that point at this one. Outbound lists the types this one points to. When both lists hold the same edges, the card collapses them into a single bidirectional block, shown with an ↔ arrow.

All relationships are many-to-many CI relationships stored in cmdb_rel_ci. None of the listed relationships are one-to-one or one-to-many. References (one-to-many fields) live on the table dictionary and are covered on the Properties page, not here.

Click any type name in a relationship line to jump to that type's card.

New to the model? Read Portfolio Element first (the superclass that every YouDesign Command-specific type extends), then the three CSDM cards (Business Application, Business Capability, Information Object), then the Strategy & Direction and Capabilities & Processes domains under Portfolio Element extensions. Everything else builds on those.

---

ServiceNow CSDM tables used by YouDesign Command

YouDesign Command reuses these ServiceNow CSDM tables for the core business and data concepts so the enterprise model stays aligned with CSDM rather than duplicating it.

Business Application

cmdb_ci_business_app

A Business Application is a logical representation of one or more deployed software product instances that together support a specific business process or capability, regardless of where they physically run.

Inbound relationships (47)

• Actor → has interest :: has relevance

• AI Model → Depends on :: Used by

• AI Model → Integrates :: Integrated by

• AI Model → Uses :: Used by

• Building Block → consists of :: is part of

• Business Application → Exchanges data with :: Exchanges data with

• Business Application → has target :: is target

• Business Capability → Provided By :: Provides

• Business Function → Uses :: Used by

• Capability Instance → Provided By :: Provides

• Control → impacts :: impacted by

• Demand → impacts :: impacted by

• Idea → impacts :: impacted by

• Information Object → Creates :: Created by

• Information Object → Deletes :: Deleted by

• Information Object → Reads :: Read by

• Information Object → Updates :: Updated by

• Information Object → Uses :: Used by

• Layer Architecture → impacts :: impacted by

• Logical Application → Uses :: Used by

• Logical Data Object → requires :: required by

• Logical Data Object → Updates :: Updated by

• Logical Interface → Sends Data to :: Receives Data from

• Mapped Application Service → has Instance :: is Instance of

• Organizational Unit → Uses :: Used by

• Pattern → consists of :: is part of

• Pattern → Deploys :: Deployed by

• Portfolio → Contains :: Contained by

• Principle → Compliant :: Compliant with

• Principle → Conformant :: Conformant with

• Principle → Fully Conformant :: Fully Conformant with

• Principle → Non-Compliant :: Non-Compliant with

• Principle → Non-Conformant :: Non-Conformant with

• Process → Uses :: Used by

• Project → Creates :: Created by

• Project → Deletes :: Deleted by

• Project → Introduces :: Introduced by

• Project → Migrates :: Migrated by

• Project → Removes :: Removed by

• Project → Updates :: Updated by

• Risk → impacts :: impacted by

• Segment Architecture → impacts :: impacted by

• Service → Consumes :: Consumed by

• Service → Contains :: Contained by

• Solution Architecture → impacts :: impacted by

• Technical Capability → Enables :: Enabled by

• Value Stream Stage → requires :: required by

Outbound relationships (52)

• has interest :: has relevance → Actor

• Depends on :: Used by → AI Model

• Integrates :: Integrated by → AI Model

• Uses :: Used by → AI Model

• consists of :: is part of → Building Block

• Exchanges data with :: Exchanges data with → Business Application

• has target :: is target → Business Application

• Uses :: Used by → Business Function

• Provided By :: Provides → Capability Instance

• Uses :: Used by → Component

• impacts :: impacted by → Control

• impacts :: impacted by → Demand

• Uses :: Used by → Domain

• Uses :: Used by → Hardware Product

• impacts :: impacted by → Idea

• Creates :: Created by → Information Object

• Deletes :: Deleted by → Information Object

• Reads :: Read by → Information Object

• Updates :: Updated by → Information Object

• Uses :: Used by → Information Object

• impacts :: impacted by → Layer Architecture

• requires :: required by → Logical Data Object

• Updates :: Updated by → Logical Data Object

• Provides :: Provided by → Logical Interface

• Sends Data to :: Receives Data from → Logical Interface

• has Instance :: is Instance of → Mapped Application Service

• Uses :: Used by → Microservice

• Uses :: Used by → Mobile Application

• Uses :: Used by → Organizational Unit

• consists of :: is part of → Pattern

• Deploys :: Deployed by → Pattern

• Contains :: Contained by → Portfolio

• Compliant :: Compliant with → Principle

• Conformant :: Conformant with → Principle

• Fully Conformant :: Fully Conformant with → Principle

• Non-Compliant :: Non-Compliant with → Principle

• Non-Conformant :: Non-Conformant with → Principle

• Creates :: Created by → Project

• Deletes :: Deleted by → Project

• Introduces :: Introduced by → Project

• Migrates :: Migrated by → Project

• Removes :: Removed by → Project

• Updates :: Updated by → Project

• impacts :: impacted by → Risk

• impacts :: impacted by → Segment Architecture

• Consumes :: Consumed by → Service

• Uses :: Used by → Social Media

• Uses :: Used by → Software Product

• impacts :: impacted by → Solution Architecture

• Enables :: Enabled by → Technical Capability

• requires :: required by → Value Stream Stage

• Uses :: Used by → Website

Business Capability

cmdb_ci_business_capability

A Business Capability describes what an organisation requires to execute its business model or fulfil its mission. Capabilities are organisational-level skills embedded in people, processes, and technology, independent of the systems that realise them.

Inbound relationships (45)

• Actor → has interest :: has relevance

• AI Model → Provided By :: Provides

• Building Block → consists of :: is part of

• Business Capability → Conformant :: Conformant with

• Business Capability → Fully Conformant :: Fully Conformant with

• Business Capability → Non-Compliant :: Non-Compliant with

• Business Capability → Non-Conformant :: Non-Conformant with

• Business Event → impacts :: impacted by

• Business Function → delivered by :: delivers

• Business Product → delivered by :: delivers

• Capability Instance → realized by :: realizes

• Control → impacts :: impacted by

• Demand → impacts :: impacted by

• Idea → impacts :: impacted by

• Information Object → Creates :: Created by

• Information Object → Reads :: Read by

• Information Object → Updates :: Updated by

• Initiative → impacts :: impacted by

• Layer Architecture → impacts :: impacted by

• Objective → has target :: is target

• Organizational Unit → delivered by :: delivers

• Organizational Unit → Uses :: Used by

• Outcome → Achieves :: Achieved by

• Outcome → requires :: required by

• Policy → influences :: is influenced by

• Portfolio → Contains :: Contained by

• Principle → Compliant :: Compliant with

• Principle → Conformant :: Conformant with

• Principle → Fully Conformant :: Fully Conformant with

• Principle → Non-Compliant :: Non-Compliant with

• Principle → Non-Conformant :: Non-Conformant with

• Process → is executed by :: executes

• Process Activity → is executed by :: executes

• Project → Creates :: Created by

• Project → Introduces :: Introduced by

• Project → Removes :: Removed by

• Project → Updates :: Updated by

• Risk → impacts :: impacted by

• Segment Architecture → impacts :: impacted by

• Service → Provides :: Provided by

• Solution Architecture → impacts :: impacted by

• Strategy → influences :: is influenced by

• Technical Capability → requires :: required by

• Value Chain → delivered by :: delivers

• Value Stream Stage → Enables :: Enabled by

Outbound relationships (49)

• has interest :: has relevance → Actor

• Provided By :: Provides → AI Model

• consists of :: is part of → Building Block

• Provided By :: Provides → Business Application

• Conformant :: Conformant with → Business Capability

• Fully Conformant :: Fully Conformant with → Business Capability

• Non-Compliant :: Non-Compliant with → Business Capability

• Non-Conformant :: Non-Conformant with → Business Capability

• impacts :: impacted by → Business Event

• delivered by :: delivers → Business Function

• delivered by :: delivers → Business Product

• realized by :: realizes → Capability Instance

• impacts :: impacted by → Control

• impacts :: impacted by → Demand

• impacts :: impacted by → Idea

• Creates :: Created by → Information Object

• Reads :: Read by → Information Object

• Updates :: Updated by → Information Object

• Uses :: Used by → Information Object

• impacts :: impacted by → Initiative

• impacts :: impacted by → Layer Architecture

• Provided By :: Provides → Logical Application

• has target :: is target → Objective

• delivered by :: delivers → Organizational Unit

• Uses :: Used by → Organizational Unit

• Achieves :: Achieved by → Outcome

• requires :: required by → Outcome

• influences :: is influenced by → Policy

• Contains :: Contained by → Portfolio

• Compliant :: Compliant with → Principle

• Conformant :: Conformant with → Principle

• Fully Conformant :: Fully Conformant with → Principle

• Non-Compliant :: Non-Compliant with → Principle

• Non-Conformant :: Non-Conformant with → Principle

• is executed by :: executes → Process

• is executed by :: executes → Process Activity

• Creates :: Created by → Project

• Introduces :: Introduced by → Project

• Removes :: Removed by → Project

• Updates :: Updated by → Project

• impacts :: impacted by → Risk

• impacts :: impacted by → Segment Architecture

• Provides :: Provided by → Service

• Uses :: Used by → Service

• impacts :: impacted by → Solution Architecture

• influences :: is influenced by → Strategy

• requires :: required by → Technical Capability

• delivered by :: delivers → Value Chain

• Enables :: Enabled by → Value Stream Stage

Information Object

cmdb_ci_information_object

An Information Object is a logical or conceptual representation of a real-world data object, e.g. a Person, Account, Asset, Contract, Order, independent of the systems where it is stored.

Inbound relationships (48)

• Actor → has interest :: has relevance

• AI Model → Uses :: Used by

• Building Block → consists of :: is part of

• Business Application → Creates :: Created by

• Business Application → Deletes :: Deleted by

• Business Application → Reads :: Read by

• Business Application → Updates :: Updated by

• Business Application → Uses :: Used by

• Business Capability → Creates :: Created by

• Business Capability → Reads :: Read by

• Business Capability → Updates :: Updated by

• Business Capability → Uses :: Used by

• Capability Instance → Creates :: Created by

• Capability Instance → Reads :: Read by

• Capability Instance → Updates :: Updated by

• Capability Instance → Uses :: Used by

• Configuration file → Depends on :: Used by

• Data Store → has source-of-record :: is source-of-record

• Data Store → is stored in :: stores

• Database Catalog → Depends on :: Used by

• Exchange MailBox → Depends on :: Used by

• File System → Depends on :: Used by

• Logical Data Object → has Instance :: is Instance of

• Logical Interface → Transports :: Transported by

• Mapped Application Service → Creates :: Created by

• Mapped Application Service → Deletes :: Deleted by

• Mapped Application Service → Reads :: Read by

• Mapped Application Service → Updates :: Updated by

• Physical Interface → Transports :: Transported by

• Portfolio → Contains :: Contained by

• Process → Creates :: Created by

• Process → Deletes :: Deleted by

• Process → Reads :: Read by

• Process → Updates :: Updated by

• Process → Uses :: Used by

• Process Activity → Creates :: Created by

• Process Activity → Deletes :: Deleted by

• Process Activity → Reads :: Read by

• Process Activity → Updates :: Updated by

• Process Operations → Creates :: Created by

• Process Operations → Deletes :: Deleted by

• Process Operations → Reads :: Read by

• Process Operations → Updates :: Updated by

• Project → Creates :: Created by

• Project → Introduces :: Introduced by

• Project → Removes :: Removed by

• Project → Updates :: Updated by

• Stakeholder → defines :: defined by

Outbound relationships (47)

• has interest :: has relevance → Actor

• Uses :: Used by → AI Model

• consists of :: is part of → Building Block

• Creates :: Created by → Business Application

• Deletes :: Deleted by → Business Application

• Reads :: Read by → Business Application

• Updates :: Updated by → Business Application

• Uses :: Used by → Business Application

• Creates :: Created by → Business Capability

• Reads :: Read by → Business Capability

• Updates :: Updated by → Business Capability

• Creates :: Created by → Capability Instance

• Reads :: Read by → Capability Instance

• Updates :: Updated by → Capability Instance

• Uses :: Used by → Capability Instance

• Depends on :: Used by → Configuration file

• has source-of-record :: is source-of-record → Data Store

• is stored in :: stores → Data Store

• Depends on :: Used by → Database Catalog

• Depends on :: Used by → Exchange MailBox

• Depends on :: Used by → File System

• has Instance :: is Instance of → Logical Data Object

• Transports :: Transported by → Logical Interface

• Creates :: Created by → Mapped Application Service

• Deletes :: Deleted by → Mapped Application Service

• Reads :: Read by → Mapped Application Service

• Updates :: Updated by → Mapped Application Service

• Transports :: Transported by → Physical Interface

• Contains :: Contained by → Portfolio

• Creates :: Created by → Process

• Deletes :: Deleted by → Process

• Reads :: Read by → Process

• Updates :: Updated by → Process

• Uses :: Used by → Process

• Creates :: Created by → Process Activity

• Deletes :: Deleted by → Process Activity

• Reads :: Read by → Process Activity

• Updates :: Updated by → Process Activity

• Creates :: Created by → Process Operations

• Deletes :: Deleted by → Process Operations

• Reads :: Read by → Process Operations

• Updates :: Updated by → Process Operations

• Creates :: Created by → Project

• Introduces :: Introduced by → Project

• Removes :: Removed by → Project

• Updates :: Updated by → Project

• defines :: defined by → Stakeholder

Any ServiceNow table can be connected to YouDesign Command tables via CI relationships. Anything that already lives in the CMDB is one relationship away.

Legacy tables. x_inpgh_upmx_business_application, x_inpgh_upmx_business_capability, and x_inpgh_upmx_information_object are technically equivalent to the CSDM tables above and remain supported for existing customers. New implementations should use the CSDM tables.

---

Portfolio Element, the YouDesign Command architectural superclass

Every YouDesign Command-specific object type inherits from x_inpgh_upmx_portfolio_element, giving the model a single ownership, lifecycle, scoring, relationship, and reporting foundation.

Portfolio Element

x_inpgh_upmx_portfolio_element

Portfolio Element is the super-class containing all sub-classes e. g. Business Application in UPMX.

Connected types (7) · bidirectional

• impacts :: impacted by ↔ Business Event

• Uses :: Used by ↔ Organizational Unit

• Creates :: Created by ↔ Project

• Introduces :: Introduced by ↔ Project

• Migrates :: Migrated by ↔ Project

• Removes :: Removed by ↔ Project

• Updates :: Updated by ↔ Project

Why a superclass. Any field added to Portfolio Element is instantly inherited by every sub-table, so ownership, lifecycle, scoring, relationships, and reporting are managed centrally. Once, not per object type.

---

Portfolio Element extensions

These are the primary architectural object types. They are grouped by domain (strategy, organisation, value, capability, performance, application, data, AI, and architecture) so the model can be navigated by concern, not just by table.

Strategy & Direction

Why the organization changes and how intent becomes measurable direction.

Driver

x_inpgh_upmx_driver

A driver represents an external or internal influence that motivates an organization to define its goals and implement the changes necessary to achieve them.

Connected types (4) · bidirectional

• has interest :: has relevance ↔ Actor

• influences :: is influenced by ↔ Goal

• generates :: generated by ↔ Market

• impacts :: impacted by ↔ Risk

Goal

x_inpgh_upmx_goal

A Goal is something directional your business aims to be, as described in words. The organizational goals of a company typically focus on its long-range intentions for operating and its overall business philosophy. E.g. “Be the most customer-centric service supplier in Northern Europe.”

Connected types (7) · bidirectional

• has interest :: has relevance ↔ Actor

• influences :: is influenced by ↔ Driver

• leads to :: led from ↔ Goal

• leads to :: led from ↔ Mission

• leads to :: led from ↔ Objective

• impacts :: impacted by ↔ Risk

• leads to :: led from ↔ Strategy

Mission

x_inpgh_upmx_mission

A Mission is a written declaration of an organization's core purpose and focus that normally remains unchanged over time. Properly crafted mission statements serve as filters to separate what is important from what is not, clearly state which markets will be served and how, and communicate a sense of intended direction to the entire organization.

Connected types (3) · bidirectional

• has interest :: has relevance ↔ Actor

• leads to :: led from ↔ Goal

• leads to :: led from ↔ Vision

Objective

x_inpgh_upmx_objective

An Objective is a specific target that helps to measure a goal achievement and typically set out in numbers. Objectives need to be Specific, Measurable, Attainable, Relevant and Time-limited (SMART). E.g. Reduce OPEX by 20% by end of 2018.

Connected types (16) · bidirectional

• has interest :: has relevance ↔ Actor

• has target :: is target ↔ Business Capability

• fulfills :: fulfilled by ↔ Business Requirement

• has target :: is target ↔ Capability Instance

• leads to :: led from ↔ Goal

• leads to :: led from ↔ Initiative

• measures :: measured by ↔ Metric

• delivered by :: delivers ↔ Organizational Unit

• Owns :: Owned by ↔ Organizational Unit

• influences :: is influenced by ↔ Policy

• Implements :: Implemented by ↔ Project

• is implemented by :: implements ↔ Project

• impacts :: impacted by ↔ Risk

• Achieves :: Achieved by ↔ Strategy

• Enables :: Enabled by ↔ Strategy

• has target :: is target ↔ Value Stream

Policy

x_inpgh_upmx_policy

A statement of direction for an organization. A rule that prohibits or prescribes specific actions for given conditions ...

Connected types (8) · bidirectional

• influences :: is influenced by ↔ Business Capability

• influences :: is influenced by ↔ Capability Instance

• Supports :: is Supported by ↔ Layer Architecture

• influences :: is influenced by ↔ Objective

• influences :: is influenced by ↔ Organizational Unit

• Supports :: is Supported by ↔ Segment Architecture

• Supports :: is Supported by ↔ Solution Architecture

• defines :: defined by ↔ Stakeholder

Principle

x_inpgh_upmx_principle

A Principle is a guiding sense of requirements and obligations the organization has conducted. Architecture Principles, Formats and other Guiding Principles can be managed in a hierarchal order.

Connected types (71) · bidirectional

• consists of :: is part of ↔ Building Block

• Compliant :: Compliant with ↔ Business Application

• Conformant :: Conformant with ↔ Business Application

• Fully Conformant :: Fully Conformant with ↔ Business Application

• Non-Compliant :: Non-Compliant with ↔ Business Application

• Non-Conformant :: Non-Conformant with ↔ Business Application

• Compliant :: Compliant with ↔ Business Capability

• Conformant :: Conformant with ↔ Business Capability

• Fully Conformant :: Fully Conformant with ↔ Business Capability

• Non-Compliant :: Non-Compliant with ↔ Business Capability

• Non-Conformant :: Non-Conformant with ↔ Business Capability

• Compliant :: Compliant with ↔ Business Product

• Conformant :: Conformant with ↔ Business Product

• Fully Conformant :: Fully Conformant with ↔ Business Product

• Non-Compliant :: Non-Compliant with ↔ Business Product

• Non-Conformant :: Non-Conformant with ↔ Business Product

• Compliant :: Compliant with ↔ Capability Instance

• Conformant :: Conformant with ↔ Capability Instance

• Fully Conformant :: Fully Conformant with ↔ Capability Instance

• Non-Compliant :: Non-Compliant with ↔ Capability Instance

• Non-Conformant :: Non-Conformant with ↔ Capability Instance

• Compliant :: Compliant with ↔ Hardware Product

• Conformant :: Conformant with ↔ Hardware Product

• Fully Conformant :: Fully Conformant with ↔ Hardware Product

• Non-Compliant :: Non-Compliant with ↔ Hardware Product

• Non-Conformant :: Non-Conformant with ↔ Hardware Product

• Compliant :: Compliant with ↔ Layer Architecture

• Conformant :: Conformant with ↔ Layer Architecture

• Fully Conformant :: Fully Conformant with ↔ Layer Architecture

• Non-Compliant :: Non-Compliant with ↔ Layer Architecture

• Non-Conformant :: Non-Conformant with ↔ Layer Architecture

• Compliant :: Compliant with ↔ Logical Application

• Conformant :: Conformant with ↔ Logical Application

• Fully Conformant :: Fully Conformant with ↔ Logical Application

• Non-Compliant :: Non-Compliant with ↔ Logical Application

• Non-Conformant :: Non-Conformant with ↔ Logical Application

• Compliant :: Compliant with ↔ Pattern

• Conformant :: Conformant with ↔ Pattern

• Fully Conformant :: Fully Conformant with ↔ Pattern

• Non-Compliant :: Non-Compliant with ↔ Pattern

• Non-Conformant :: Non-Conformant with ↔ Pattern

• Compliant :: Compliant with ↔ Process

• Conformant :: Conformant with ↔ Process

• Fully Conformant :: Fully Conformant with ↔ Process

• Non-Compliant :: Non-Compliant with ↔ Process

• Non-Conformant :: Non-Conformant with ↔ Process

• Compliant :: Compliant with ↔ Project

• Conformant :: Conformant with ↔ Project

• Fully Conformant :: Fully Conformant with ↔ Project

• Non-Compliant :: Non-Compliant with ↔ Project

• Non-Conformant :: Non-Conformant with ↔ Project

• Compliant :: Compliant with ↔ Segment Architecture

• Conformant :: Conformant with ↔ Segment Architecture

• Fully Conformant :: Fully Conformant with ↔ Segment Architecture

• Non-Compliant :: Non-Compliant with ↔ Segment Architecture

• Non-Conformant :: Non-Conformant with ↔ Segment Architecture

• Compliant :: Compliant with ↔ Service

• Conformant :: Conformant with ↔ Service

• Fully Conformant :: Fully Conformant with ↔ Service

• Non-Compliant :: Non-Compliant with ↔ Service

• Non-Conformant :: Non-Conformant with ↔ Service

• Compliant :: Compliant with ↔ Software Product

• Conformant :: Conformant with ↔ Software Product

• Fully Conformant :: Fully Conformant with ↔ Software Product

• Non-Compliant :: Non-Compliant with ↔ Software Product

• Non-Conformant :: Non-Conformant with ↔ Software Product

• Compliant :: Compliant with ↔ Solution Architecture

• Conformant :: Conformant with ↔ Solution Architecture

• Fully Conformant :: Fully Conformant with ↔ Solution Architecture

• Non-Compliant :: Non-Compliant with ↔ Solution Architecture

• Non-Conformant :: Non-Conformant with ↔ Solution Architecture

Strategy

x_inpgh_upmx_strategy

A Strategy describes how the company will achieve its goals and objectives by deploying its scarce resources to gain a sustainable competitive advantage.

Connected types (22) · bidirectional

• has interest :: has relevance ↔ Actor

• consists of :: is part of ↔ Building Block

• influences :: is influenced by ↔ Business Capability

• impacts :: impacted by ↔ Business Product

• influences :: is influenced by ↔ Capability Instance

• Supports :: is Supported by ↔ Demand

• leads to :: led from ↔ Goal

• impacts :: impacted by ↔ Idea

• is implemented by :: implements ↔ Initiative

• influences :: is influenced by ↔ Journey

• Supports :: is Supported by ↔ Layer Architecture

• Achieves :: Achieved by ↔ Objective

• Enables :: Enabled by ↔ Objective

• is implemented by :: implements ↔ Program

• is implemented by :: implements ↔ Project

• impacts :: impacted by ↔ Risk

• Supports :: is Supported by ↔ Segment Architecture

• Supports :: is Supported by ↔ Solution Architecture

• defines :: defined by ↔ Stakeholder

• Owns :: Owned by ↔ Stakeholder

• leads to :: led from ↔ Strategy

• influences :: is influenced by ↔ Value Stream

Vision

x_inpgh_upmx_vision

A Vision is an aspirational description of what an organization would like to achieve or accomplish if they successfully fulfill their organizational purpose or mission.

Connected types (2) · bidirectional

• has interest :: has relevance ↔ Actor

• leads to :: led from ↔ Mission

Organization & Accountability

Who owns, governs, sponsors, performs, or is affected by the portfolio.

Actor

x_inpgh_upmx_actor

Actors are abstract representations of people, teams, departments, roles and groups.

Connected types (46) · bidirectional

• has interest :: has relevance ↔ Business Application

• has interest :: has relevance ↔ Business Capability

• Performs :: Performed by ↔ Business Function

• has interest :: has relevance ↔ Business Process

• has interest :: has relevance ↔ Business Product

• has interest :: has relevance ↔ Capability Instance

• has interest :: has relevance ↔ Channel

• has interest :: has relevance ↔ Component

• has interest :: has relevance ↔ Data Store

• has interest :: has relevance ↔ Domain

• has interest :: has relevance ↔ Driver

• has interest :: has relevance ↔ Goal

• has interest :: has relevance ↔ Hardware Product

• has interest :: has relevance ↔ Information Object

• has interest :: has relevance ↔ Initiative

• has interest :: has relevance ↔ Journey

• has interest :: has relevance ↔ Logical Interface

• has interest :: has relevance ↔ Mapped Application Service

• has interest :: has relevance ↔ Market

• has interest :: has relevance ↔ Microservice

• has interest :: has relevance ↔ Mission

• has interest :: has relevance ↔ Mobile Application

• has interest :: has relevance ↔ Objective

• has interest :: has relevance ↔ Pattern

• has interest :: has relevance ↔ Physical Interface

• has interest :: has relevance ↔ Process

• has interest :: has relevance ↔ Process Activity

• has interest :: has relevance ↔ Process Category

• has interest :: has relevance ↔ Process Group

• has interest :: has relevance ↔ Process Operations

• has interest :: has relevance ↔ Process Task

• has interest :: has relevance ↔ Process Workflow

• has interest :: has relevance ↔ Program

• has interest :: has relevance ↔ Project

• impacts :: impacted by ↔ Risk

• has interest :: has relevance ↔ Server

• has interest :: has relevance ↔ Service

• has interest :: has relevance ↔ Social Media

• has interest :: has relevance ↔ Software Product

• has interest :: has relevance ↔ Solution Use Case

• has interest :: has relevance ↔ Strategy

• has interest :: has relevance ↔ Technical Capability

• has interest :: has relevance ↔ Value Chain

• has interest :: has relevance ↔ Value Stream

• has interest :: has relevance ↔ Vision

• has interest :: has relevance ↔ Website

Governance Body

x_inpgh_upmx_governance_body

A Governance Body is a committee or group responsible for oversight, decision-making, and policy enforcement.

Organizational Unit

x_inpgh_upmx_organizational_units

An organizational unit is one of several functions within a company typically structured as a multi-level hierarchy.

Inbound relationships (23)

• AI Model → Owns :: Owned by

• AI Model → Used by :: Uses

• Business Application → Uses :: Used by

• Business Capability → delivered by :: delivers

• Business Capability → Uses :: Used by

• Business Function → Performs :: Performed by

• Business Product → delivered by :: delivers

• Business Product → Owns :: Owned by

• Business Product → Uses :: Used by

• Capability Instance → delivered by :: delivers

• Capability Instance → Depends on :: Used by

• Hardware Product → Uses :: Used by

• Idea → impacts :: impacted by

• Initiative → Owns :: Owned by

• Initiative → Performs :: Performed by

• Objective → delivered by :: delivers

• Objective → Owns :: Owned by

• Policy → influences :: is influenced by

• Portfolio Element → Uses :: Used by

• Process → Depends on :: Used by

• Risk → impacts :: impacted by

• Software Product → Uses :: Used by

• Stakeholder → consists of :: is part of

Outbound relationships (31)

• Owns :: Owned by → AI Model

• Used by :: Uses → AI Model

• Uses :: Used by → Business Application

• delivered by :: delivers → Business Capability

• Uses :: Used by → Business Capability

• Performs :: Performed by → Business Function

• delivered by :: delivers → Business Product

• Owns :: Owned by → Business Product

• Uses :: Used by → Business Product

• delivered by :: delivers → Capability Instance

• Depends on :: Used by → Capability Instance

• Uses :: Used by → Hardware Product

• impacts :: impacted by → Idea

• Owns :: Owned by → Initiative

• Performs :: Performed by → Initiative

• delivered by :: delivers → Objective

• Owns :: Owned by → Objective

• influences :: is influenced by → Policy

• Uses :: Used by → Portfolio Element

• Uses :: Used by → Process

• Uses :: Used by → Process Activity

• Uses :: Used by → Process Category

• Uses :: Used by → Process Group

• Uses :: Used by → Process Operations

• Uses :: Used by → Process Workflow

• impacts :: impacted by → Risk

• Uses :: Used by → Software Product

• Uses :: Used by → Solution Use Case

• consists of :: is part of → Stakeholder

• Uses :: Used by → Value Chain

• Uses :: Used by → Value Stream

Stakeholder

x_inpgh_upmx_stakeholder

An internal or external individual or organization with a vested interest in achieving value through a particular outcom...

Connected types (12) · bidirectional

• has target :: is target ↔ Business Requirement

• defines :: defined by ↔ Information Object

• consists of :: is part of ↔ Journey

• consists of :: is part of ↔ Organizational Unit

• contributes :: contributed by ↔ Outcome

• defines :: defined by ↔ Policy

• defines :: defined by ↔ Strategy

• Owns :: Owned by ↔ Strategy

• participates in :: has participant ↔ Touchpoint

• desires :: desired by ↔ Value Proposition

• triggers :: triggered by ↔ Value Stream

• participates in :: has participant ↔ Value Stream Stage

Market, Product & Value

What value is offered, to whom, and through which market-facing structures.

Business Product

x_inpgh_upmx_business_product

A Business Product is a good produced by the company for external customers. A Business Product is typically an outcome of a Business Capability or Business Process.

Connected types (28) · bidirectional

• has interest :: has relevance ↔ Actor

• Contains :: Contained by ↔ AI Model

• consists of :: is part of ↔ Building Block

• delivered by :: delivers ↔ Business Capability

• delivered by :: delivers ↔ Capability Instance

• distributes :: distributed by ↔ Channel

• impacts :: impacted by ↔ Control

• impacts :: impacted by ↔ Idea

• impacts :: impacted by ↔ Initiative

• has target :: is target ↔ Market

• delivered by :: delivers ↔ Organizational Unit

• Owns :: Owned by ↔ Organizational Unit

• Uses :: Used by ↔ Organizational Unit

• Contains :: Contained by ↔ Portfolio

• Compliant :: Compliant with ↔ Principle

• Conformant :: Conformant with ↔ Principle

• Fully Conformant :: Fully Conformant with ↔ Principle

• Non-Compliant :: Non-Compliant with ↔ Principle

• Non-Conformant :: Non-Conformant with ↔ Principle

• delivered by :: delivers ↔ Process

• Contains :: Contained by ↔ Product Line

• Creates :: Created by ↔ Project

• Introduces :: Introduced by ↔ Project

• Removes :: Removed by ↔ Project

• Updates :: Updated by ↔ Project

• impacts :: impacted by ↔ Risk

• impacts :: impacted by ↔ Strategy

• delivered by :: delivers ↔ Value Proposition

Channel

x_inpgh_upmx_channel

Conduit for delivering goods, services, or information.

Connected types (6) · bidirectional

• has interest :: has relevance ↔ Actor

• distributes :: distributed by ↔ Business Product

• impacts :: impacted by ↔ Demand

• impacts :: impacted by ↔ Idea

• served by :: is serving ↔ Market

• impacts :: impacted by ↔ Risk

Journey

x_inpgh_upmx_journey

A Journey represents a series of touch points and interactions with organizations or stakeholders, providing/consuming services and products.

Connected types (14) · bidirectional

• has interest :: has relevance ↔ Actor

• consists of :: is part of ↔ Building Block

• impacts :: impacted by ↔ Control

• has successor :: has predecessor ↔ Journey

• Contains :: Contained by ↔ Journey Stage

• Creates :: Created by ↔ Project

• Introduces :: Introduced by ↔ Project

• Migrates :: Migrated by ↔ Project

• Removes :: Removed by ↔ Project

• Updates :: Updated by ↔ Project

• impacts :: impacted by ↔ Risk

• consists of :: is part of ↔ Stakeholder

• influences :: is influenced by ↔ Strategy

• Implements :: Implemented by ↔ Value Stream

Journey Stage

x_inpgh_upmx_journey_stage

A defined step within an overall customer journey, capturing the customer experience at that particular stage of the jou...

Connected types (3) · bidirectional

• Contains :: Contained by ↔ Journey

• consists of :: is part of ↔ Touchpoint

• Enables :: Enabled by ↔ Value Stream Stage

Market

x_inpgh_upmx_market

A Market is an actual or nominal place where forces of demand and supply operate, and where buyers and sellers interact (directly or through intermediaries) to trade goods, services, or contracts or instruments, for money or barter.

Connected types (8) · bidirectional

• has interest :: has relevance ↔ Actor

• has target :: is target ↔ Business Product

• served by :: is serving ↔ Channel

• impacts :: impacted by ↔ Demand

• generates :: generated by ↔ Driver

• impacts :: impacted by ↔ Idea

• segments :: segmented by ↔ Market

• impacts :: impacted by ↔ Risk

Outcome

x_inpgh_upmx_outcome

The result that is produced by a business capability, and associated with the delivery of a value item by a value stream...

Connected types (7) · bidirectional

• Achieves :: Achieved by ↔ Business Capability

• requires :: required by ↔ Business Capability

• Achieves :: Achieved by ↔ Capability Instance

• requires :: required by ↔ Capability Instance

• consists of :: is part of ↔ Initiative

• contributes :: contributed by ↔ Stakeholder

• consists of :: is part of ↔ Value Item

Product Line

x_inpgh_upmx_product_line

An organizing structure used for product management and marketing of a group of related products.

Connected types (1) · bidirectional

• Contains :: Contained by ↔ Business Product

Touchpoint

x_inpgh_upmx_touchpoint

The means via which a stakeholder or customer experiences their participation in a customer journey stage.

Connected types (3) · bidirectional

• consists of :: is part of ↔ Journey Stage

• participates in :: has participant ↔ Stakeholder

• delivered by :: delivers ↔ Value Item

Value Chain

x_inpgh_upmx_value_chain

A Value Chain is the whole series of activities that create and build value at every step.

Inbound relationships (9)

• Actor → has interest :: has relevance

• Business Capability → delivered by :: delivers

• Capability Instance → delivered by :: delivers

• Control → impacts :: impacted by

• Organizational Unit → Uses :: Used by

• Process → is part of :: consists of

• Risk → impacts :: impacted by

• Value Chain → has successor :: has predecessor

• Value Stream → consists of :: is part of

Outbound relationships (8)

• has interest :: has relevance → Actor

• delivered by :: delivers → Business Capability

• delivered by :: delivers → Capability Instance

• impacts :: impacted by → Control

• is part of :: consists of → Process

• impacts :: impacted by → Risk

• has successor :: has predecessor → Value Chain

• consists of :: is part of → Value Stream

Value Item

x_inpgh_upmx_value_item

The defined value delivered by a value stream stage. Value items are the entrance and exit criterion for value stream st...

Connected types (4) · bidirectional

• consists of :: is part of ↔ Outcome

• delivered by :: delivers ↔ Touchpoint

• consists of :: is part of ↔ Value Proposition

• produces :: produced by ↔ Value Stream Stage

Value Proposition

x_inpgh_upmx_value_proposition

The potential benefits, tangible or intangible, exchanged between provider and consumer. Typically the exchange of money...

Connected types (4) · bidirectional

• delivered by :: delivers ↔ Business Product

• desires :: desired by ↔ Stakeholder

• consists of :: is part of ↔ Value Item

• delivered by :: delivers ↔ Value Stream

Value Stream

x_inpgh_upmx_value_stream

Value Stream Value streams are artifacts within business architecture that allow a business to specify the value proposition derived by an external (e.g., customer) or internal stakeholder from an organization. A value stream depicts the stakeholders initiating and involved in the value stream, the stages that create specific value items, and the value proposition derived from the value stream. The value stream is depicted as an end-to-end collection of value-adding activities that create an overall result for a customer, stakeholder, or end-user.

Inbound relationships (22)

• Actor → has interest :: has relevance

• Building Block → consists of :: is part of

• Control → impacts :: impacted by

• Initiative → impacts :: impacted by

• Journey → Implements :: Implemented by

• KPI → requires :: required by

• KRI → requires :: required by

• Objective → has target :: is target

• Organizational Unit → Uses :: Used by

• PPI → requires :: required by

• Process Activity → consists of :: is part of

• Project → Creates :: Created by

• Project → Introduces :: Introduced by

• Project → Migrates :: Migrated by

• Project → Removes :: Removed by

• Project → Updates :: Updated by

• Risk → impacts :: impacted by

• Stakeholder → triggers :: triggered by

• Strategy → influences :: is influenced by

• Value Chain → consists of :: is part of

• Value Proposition → delivered by :: delivers

• Value Stream Stage → Contains :: Contained by

Outbound relationships (21)

• has interest :: has relevance → Actor

• consists of :: is part of → Building Block

• impacts :: impacted by → Control

• impacts :: impacted by → Initiative

• Implements :: Implemented by → Journey

• requires :: required by → KPI

• requires :: required by → KRI

• has target :: is target → Objective

• requires :: required by → PPI

• consists of :: is part of → Process Activity

• Creates :: Created by → Project

• Introduces :: Introduced by → Project

• Migrates :: Migrated by → Project

• Removes :: Removed by → Project

• Updates :: Updated by → Project

• impacts :: impacted by → Risk

• triggers :: triggered by → Stakeholder

• influences :: is influenced by → Strategy

• consists of :: is part of → Value Chain

• delivered by :: delivers → Value Proposition

• Contains :: Contained by → Value Stream Stage

Value Stream Stage

x_inpgh_upmx_value_stream_stage

A defined step within a value stream that delivers a value item, which accrues toward the overall value proposition desi...

Connected types (10) · bidirectional

• requires :: required by ↔ Business Application

• Enables :: Enabled by ↔ Business Capability

• defines :: defined by ↔ Business Requirement

• Enables :: Enabled by ↔ Capability Instance

• impacts :: impacted by ↔ Initiative

• Enables :: Enabled by ↔ Journey Stage

• is executed by :: executes ↔ Process

• participates in :: has participant ↔ Stakeholder

• produces :: produced by ↔ Value Item

• Contains :: Contained by ↔ Value Stream

Capabilities & Processes

What the business must be able to do and how that work is operationalized.

Business Event

x_inpgh_upmx_business_event

A business event is a threat, opportunity, or significant change trigger that requires the organisation to respond, adapt operations, or make an architecture decision.

Connected types (3) · bidirectional

• impacts :: impacted by ↔ Business Capability

• impacts :: impacted by ↔ Capability Instance

• impacts :: impacted by ↔ Portfolio Element

Business Function

x_inpgh_upmx_business_function

Business Functions are a set of activities performed by roles or organizational units in the business, producing a defined output and typically grouped based on required skills or resources.

Connected types (8) · bidirectional

• Performs :: Performed by ↔ Actor

• Provided By :: Provides ↔ AI Model

• Uses :: Used by ↔ Business Application

• delivered by :: delivers ↔ Business Capability

• delivered by :: delivers ↔ Capability Instance

• impacts :: impacted by ↔ Demand

• impacts :: impacted by ↔ Idea

• Performs :: Performed by ↔ Organizational Unit

Business Requirement

x_inpgh_upmx_requirement

A need that an organization must have satisfied in order to solve a problem or meet an objective of a stakeholder or ful...

Connected types (6) · bidirectional

• requires :: required by ↔ AI Model

• impacts :: impacted by ↔ Demand

• consists of :: is part of ↔ Initiative

• fulfills :: fulfilled by ↔ Objective

• has target :: is target ↔ Stakeholder

• defines :: defined by ↔ Value Stream Stage

Capability Instance

x_inpgh_upmx_capability_instance

A Capability Instance is a specific instantiation of a business capability within an organizational context.

Connected types (49) · bidirectional

• has interest :: has relevance ↔ Actor

• Provided By :: Provides ↔ AI Model

• consists of :: is part of ↔ Building Block

• Provided By :: Provides ↔ Business Application

• realized by :: realizes ↔ Business Capability

• impacts :: impacted by ↔ Business Event

• delivered by :: delivers ↔ Business Function

• delivered by :: delivers ↔ Business Product

• Conformant :: Conformant with ↔ Capability Instance

• Fully Conformant :: Fully Conformant with ↔ Capability Instance

• Non-Compliant :: Non-Compliant with ↔ Capability Instance

• Non-Conformant :: Non-Conformant with ↔ Capability Instance

• impacts :: impacted by ↔ Control

• impacts :: impacted by ↔ Demand

• impacts :: impacted by ↔ Idea

• Creates :: Created by ↔ Information Object

• Reads :: Read by ↔ Information Object

• Updates :: Updated by ↔ Information Object

• Uses :: Used by ↔ Information Object

• impacts :: impacted by ↔ Initiative

• impacts :: impacted by ↔ Layer Architecture

• Provided By :: Provides ↔ Logical Application

• has target :: is target ↔ Objective

• delivered by :: delivers ↔ Organizational Unit

• Depends on :: Used by ↔ Organizational Unit

• Achieves :: Achieved by ↔ Outcome

• requires :: required by ↔ Outcome

• influences :: is influenced by ↔ Policy

• Contains :: Contained by ↔ Portfolio

• Compliant :: Compliant with ↔ Principle

• Conformant :: Conformant with ↔ Principle

• Fully Conformant :: Fully Conformant with ↔ Principle

• Non-Compliant :: Non-Compliant with ↔ Principle

• Non-Conformant :: Non-Conformant with ↔ Principle

• is executed by :: executes ↔ Process

• is executed by :: executes ↔ Process Activity

• Creates :: Created by ↔ Project

• Introduces :: Introduced by ↔ Project

• Removes :: Removed by ↔ Project

• Updates :: Updated by ↔ Project

• impacts :: impacted by ↔ Risk

• impacts :: impacted by ↔ Segment Architecture

• Provides :: Provided by ↔ Service

• Uses :: Used by ↔ Service

• impacts :: impacted by ↔ Solution Architecture

• influences :: is influenced by ↔ Strategy

• requires :: required by ↔ Technical Capability

• delivered by :: delivers ↔ Value Chain

• Enables :: Enabled by ↔ Value Stream Stage

Control

x_inpgh_upmx_control

Controls are engineering mechanisms that uses continuous monitoring of operational variables e.g. pressure, temperature etc. to reach product output specifications and objectives.

Connected types (16) · bidirectional

• impacts :: impacted by ↔ Business Application

• impacts :: impacted by ↔ Business Capability

• impacts :: impacted by ↔ Business Process

• impacts :: impacted by ↔ Business Product

• impacts :: impacted by ↔ Capability Instance

• impacts :: impacted by ↔ Journey

• impacts :: impacted by ↔ Process

• impacts :: impacted by ↔ Process Activity

• impacts :: impacted by ↔ Process Category

• impacts :: impacted by ↔ Process Group

• impacts :: impacted by ↔ Process Operations

• impacts :: impacted by ↔ Process Task

• impacts :: impacted by ↔ Process Workflow

• impacts :: impacted by ↔ Solution Use Case

• impacts :: impacted by ↔ Value Chain

• impacts :: impacted by ↔ Value Stream

Process

x_inpgh_upmx_process

A Process is an activity or set of activities that provides a specific business capability. Typically, a process produce a specific service or product.

Inbound relationships (31)

• Actor → has interest :: has relevance

• Building Block → consists of :: is part of

• Business Capability → is executed by :: executes

• Business Product → delivered by :: delivers

• Capability Instance → is executed by :: executes

• Control → impacts :: impacted by

• Information Object → Creates :: Created by

• Information Object → Deletes :: Deleted by

• Information Object → Reads :: Read by

• Information Object → Updates :: Updated by

• Information Object → Uses :: Used by

• Layer Architecture → impacts :: impacted by

• Organizational Unit → Uses :: Used by

• Portfolio → Contains :: Contained by

• Principle → Compliant :: Compliant with

• Principle → Conformant :: Conformant with

• Principle → Fully Conformant :: Fully Conformant with

• Principle → Non-Compliant :: Non-Compliant with

• Principle → Non-Conformant :: Non-Conformant with

• Process → has successor :: has predecessor

• Process Activity → consists of :: is part of

• Process Group → consists of :: is part of

• Project → Creates :: Created by

• Project → Introduces :: Introduced by

• Project → Removes :: Removed by

• Project → Updates :: Updated by

• Risk → impacts :: impacted by

• Segment Architecture → impacts :: impacted by

• Solution Architecture → impacts :: impacted by

• Value Chain → is part of :: consists of

• Value Stream Stage → is executed by :: executes

Outbound relationships (34)

• has interest :: has relevance → Actor

• consists of :: is part of → Building Block

• Uses :: Used by → Business Application

• is executed by :: executes → Business Capability

• delivered by :: delivers → Business Product

• is executed by :: executes → Capability Instance

• impacts :: impacted by → Control

• Creates :: Created by → Information Object

• Deletes :: Deleted by → Information Object

• Reads :: Read by → Information Object

• Updates :: Updated by → Information Object

• Uses :: Used by → Information Object

• impacts :: impacted by → Layer Architecture

• Depends on :: Used by → Organizational Unit

• Contains :: Contained by → Portfolio

• Compliant :: Compliant with → Principle

• Conformant :: Conformant with → Principle

• Fully Conformant :: Fully Conformant with → Principle

• Non-Compliant :: Non-Compliant with → Principle

• Non-Conformant :: Non-Conformant with → Principle

• has successor :: has predecessor → Process

• consists of :: is part of → Process Activity

• consists of :: is part of → Process Group

• Creates :: Created by → Project

• Introduces :: Introduced by → Project

• Removes :: Removed by → Project

• Updates :: Updated by → Project

• impacts :: impacted by → Risk

• impacts :: impacted by → Segment Architecture

• Provides :: Provided by → Service

• Uses :: Used by → Service

• impacts :: impacted by → Solution Architecture

• is part of :: consists of → Value Chain

• is executed by :: executes → Value Stream Stage

Process Activity

x_inpgh_upmx_process_activity

A Process Activity is also referred to as sub-processes with execution on divisional, business line, local or regional levels.

Inbound relationships (20)

• Actor → has interest :: has relevance

• AI Model → Uses :: Used by

• Business Capability → is executed by :: executes

• Capability Instance → is executed by :: executes

• Control → impacts :: impacted by

• Information Object → Creates :: Created by

• Information Object → Deletes :: Deleted by

• Information Object → Reads :: Read by

• Information Object → Updates :: Updated by

• Organizational Unit → Uses :: Used by

• Process → consists of :: is part of

• Process Task → consists of :: is part of

• Process Workflow → Implements :: Implemented by

• Project → Creates :: Created by

• Project → Introduces :: Introduced by

• Project → Migrates :: Migrated by

• Project → Removes :: Removed by

• Project → Updates :: Updated by

• Risk → impacts :: impacted by

• Value Stream → consists of :: is part of

Outbound relationships (19)

• has interest :: has relevance → Actor

• Uses :: Used by → AI Model

• is executed by :: executes → Business Capability

• is executed by :: executes → Capability Instance

• impacts :: impacted by → Control

• Creates :: Created by → Information Object

• Deletes :: Deleted by → Information Object

• Reads :: Read by → Information Object

• Updates :: Updated by → Information Object

• consists of :: is part of → Process

• consists of :: is part of → Process Task

• Implements :: Implemented by → Process Workflow

• Creates :: Created by → Project

• Introduces :: Introduced by → Project

• Migrates :: Migrated by → Project

• Removes :: Removed by → Project

• Updates :: Updated by → Project

• impacts :: impacted by → Risk

• consists of :: is part of → Value Stream

Process Category

x_inpgh_upmx_process_category

Process Categories are used by industry frameworks to classify processes by area. Process Categories can be replaced by top-level Business Capabilities.

Inbound relationships (10)

• Actor → has interest :: has relevance

• Control → impacts :: impacted by

• Organizational Unit → Uses :: Used by

• Process Group → consists of :: is part of

• Project → Creates :: Created by

• Project → Introduces :: Introduced by

• Project → Migrates :: Migrated by

• Project → Removes :: Removed by

• Project → Updates :: Updated by

• Risk → impacts :: impacted by

Outbound relationships (9)

• has interest :: has relevance → Actor

• impacts :: impacted by → Control

• consists of :: is part of → Process Group

• Creates :: Created by → Project

• Introduces :: Introduced by → Project

• Migrates :: Migrated by → Project

• Removes :: Removed by → Project

• Updates :: Updated by → Project

• impacts :: impacted by → Risk

Process Group

x_inpgh_upmx_process_group

Process Groups are groupings of related processes that are applicable across operational hierarchies and silos. Process Groups can be replaced by top-level Business Capabilities.

Inbound relationships (11)

• Actor → has interest :: has relevance

• Control → impacts :: impacted by

• Organizational Unit → Uses :: Used by

• Process → consists of :: is part of

• Process Category → consists of :: is part of

• Project → Creates :: Created by

• Project → Introduces :: Introduced by

• Project → Migrates :: Migrated by

• Project → Removes :: Removed by

• Project → Updates :: Updated by

• Risk → impacts :: impacted by

Outbound relationships (10)

• has interest :: has relevance → Actor

• impacts :: impacted by → Control

• consists of :: is part of → Process

• consists of :: is part of → Process Category

• Creates :: Created by → Project

• Introduces :: Introduced by → Project

• Migrates :: Migrated by → Project

• Removes :: Removed by → Project

• Updates :: Updated by → Project

• impacts :: impacted by → Risk

Process Operations

x_inpgh_upmx_process_operations

Process Operations are technical calls to technology components, or non-technical work performed manually by a person.

Inbound relationships (16)

• Actor → has interest :: has relevance

• Control → impacts :: impacted by

• Information Object → Creates :: Created by

• Information Object → Deletes :: Deleted by

• Information Object → Reads :: Read by

• Information Object → Updates :: Updated by

• Measure → measures :: measured by

• Organizational Unit → Uses :: Used by

• Process Task → consists of :: is part of

• Project → Creates :: Created by

• Project → Introduces :: Introduced by

• Project → Migrates :: Migrated by

• Project → Removes :: Removed by

• Project → Updates :: Updated by

• Risk → impacts :: impacted by

• Solution Use Case → consists of :: is part of

Outbound relationships (15)

• has interest :: has relevance → Actor

• impacts :: impacted by → Control

• Creates :: Created by → Information Object

• Deletes :: Deleted by → Information Object

• Reads :: Read by → Information Object

• Updates :: Updated by → Information Object

• measures :: measured by → Measure

• consists of :: is part of → Process Task

• Creates :: Created by → Project

• Introduces :: Introduced by → Project

• Migrates :: Migrated by → Project

• Removes :: Removed by → Project

• Updates :: Updated by → Project

• impacts :: impacted by → Risk

• consists of :: is part of → Solution Use Case

Process Task

x_inpgh_upmx_process_task

Process Tasks are technical tasks executed on application level, or non-technical tasks performed by people.

Connected types (15) · bidirectional

• has interest :: has relevance ↔ Actor

• Uses :: Used by ↔ AI Model

• impacts :: impacted by ↔ Control

• measures :: measured by ↔ Measure

• measures :: measured by ↔ Metric

• consists of :: is part of ↔ Process Activity

• consists of :: is part of ↔ Process Operations

• consists of :: is part of ↔ Process Workflow

• Creates :: Created by ↔ Project

• Introduces :: Introduced by ↔ Project

• Migrates :: Migrated by ↔ Project

• Removes :: Removed by ↔ Project

• Updates :: Updated by ↔ Project

• impacts :: impacted by ↔ Risk

• Implements :: Implemented by ↔ Solution Use Case

Process Workflow

x_inpgh_upmx_process_workflow

A Process Workflow consists of multiple Process Tasks in order to implement a Process Activity.

Inbound relationships (11)

• Actor → has interest :: has relevance

• Control → impacts :: impacted by

• Organizational Unit → Uses :: Used by

• Process Activity → Implements :: Implemented by

• Process Task → consists of :: is part of

• Project → Creates :: Created by

• Project → Introduces :: Introduced by

• Project → Migrates :: Migrated by

• Project → Removes :: Removed by

• Project → Updates :: Updated by

• Risk → impacts :: impacted by

Outbound relationships (10)

• has interest :: has relevance → Actor

• impacts :: impacted by → Control

• Implements :: Implemented by → Process Activity

• consists of :: is part of → Process Task

• Creates :: Created by → Project

• Introduces :: Introduced by → Project

• Migrates :: Migrated by → Project

• Removes :: Removed by → Project

• Updates :: Updated by → Project

• impacts :: impacted by → Risk

Performance, Risk & Investment

How value, risk, delivery, and portfolio movement are measured and governed.

Demand

x_inpgh_upmx_demand

A Demand represents a request or need for resources, services, or capabilities from the organization.

Connected types (17) · bidirectional

• impacts :: impacted by ↔ Business Application

• impacts :: impacted by ↔ Business Capability

• impacts :: impacted by ↔ Business Function

• impacts :: impacted by ↔ Business Process

• impacts :: impacted by ↔ Business Requirement

• impacts :: impacted by ↔ Business Service

• impacts :: impacted by ↔ Capability Instance

• impacts :: impacted by ↔ Channel

• generates :: generated by ↔ Idea

• impacts :: impacted by ↔ Layer Architecture

• impacts :: impacted by ↔ Market

• contributes :: contributed by ↔ Program

• leads to :: led from ↔ Project

• leads to :: led from ↔ Project Task

• impacts :: impacted by ↔ Segment Architecture

• impacts :: impacted by ↔ Solution Architecture

• Supports :: is Supported by ↔ Strategy

Idea

x_inpgh_upmx_idea

An Idea captures a concept, innovation, or proposal for evaluation and potential implementation.

Connected types (18) · bidirectional

• impacts :: impacted by ↔ Business Application

• impacts :: impacted by ↔ Business Capability

• impacts :: impacted by ↔ Business Function

• impacts :: impacted by ↔ Business Process

• impacts :: impacted by ↔ Business Product

• impacts :: impacted by ↔ Business Service

• impacts :: impacted by ↔ Capability Instance

• impacts :: impacted by ↔ Channel

• generates :: generated by ↔ Demand

• Supports :: is Supported by ↔ Initiative

• contributes :: contributed by ↔ Layer Architecture

• impacts :: impacted by ↔ Market

• impacts :: impacted by ↔ Organizational Unit

• contributes :: contributed by ↔ Program

• leads to :: led from ↔ Project

• contributes :: contributed by ↔ Segment Architecture

• contributes :: contributed by ↔ Solution Architecture

• impacts :: impacted by ↔ Strategy

Initiative

x_inpgh_upmx_initiative

Initiatives are collections of finite-duration discretionary projects and programs, outside of the organization's day-to-day operational activities, that are designed to help the organization achieve its targeted performance.

Connected types (20) · bidirectional

• has interest :: has relevance ↔ Actor

• consists of :: is part of ↔ Building Block

• impacts :: impacted by ↔ Business Capability

• impacts :: impacted by ↔ Business Product

• consists of :: is part of ↔ Business Requirement

• impacts :: impacted by ↔ Capability Instance

• Supports :: is Supported by ↔ Idea

• Supports :: is Supported by ↔ Layer Architecture

• leads to :: led from ↔ Objective

• Owns :: Owned by ↔ Organizational Unit

• Performs :: Performed by ↔ Organizational Unit

• consists of :: is part of ↔ Outcome

• Contains :: Contained by ↔ Portfolio

• is implemented by :: implements ↔ Project

• impacts :: impacted by ↔ Risk

• Supports :: is Supported by ↔ Segment Architecture

• Supports :: is Supported by ↔ Solution Architecture

• is implemented by :: implements ↔ Strategy

• impacts :: impacted by ↔ Value Stream

• impacts :: impacted by ↔ Value Stream Stage

KPI

x_inpgh_upmx_kpi

A Key Performance Indicator (KPI) is used to measure and evaluate the success of an organization or of a particular activity (such as projects, programs, products and other initiatives) in which it engages.

Connected types (2) · bidirectional

• consists of :: is part of ↔ Metric

• requires :: required by ↔ Value Stream

KRI

x_inpgh_upmx_kri

A Key Risk Indicator (KRI) is a measure used in management to indicate how risky an activity is. Key risk indicators are metrics used by organizations to provide an early signal of increasing risk exposures in various areas of the enterprise. It differs from a key performance indicator (KPI) in that the latter is meant as a measure of how well something is being done while the former is an indicator of the possibility of future adverse impact. KRI give an early warning to identify potential event that may harm continuity of the activity/project.

Connected types (2) · bidirectional

• consists of :: is part of ↔ Metric

• requires :: required by ↔ Value Stream

Measure

x_inpgh_upmx_measure

A Measure is used to specify the measurement type to track key performance indicators and metrics by e.g. percentage, number, currency, activity, process etc. usually on an ongoing basis, to determine success or alignment with objectives and goals.

Connected types (3) · bidirectional

• consists of :: is part of ↔ Metric

• measures :: measured by ↔ Process Operations

• measures :: measured by ↔ Process Task

Metric

x_inpgh_upmx_metric

Metrics track and provide data on your organization's processes and procedures but are not the most important metrics your organization needs to measure, monitor, and perform against to make progress against your strategic plan. E.g. organic inbound website traffic. It's important to track this metric as it helps feed your strategy outcome, but it's not a clearly defined KPI related to an outcome. It's just a valuable metric.

Connected types (8) · bidirectional

• consists of :: is part of ↔ KPI

• consists of :: is part of ↔ KRI

• consists of :: is part of ↔ Measure

• consists of :: is part of ↔ Metric

• measures :: measured by ↔ Objective

• consists of :: is part of ↔ PPI

• measures :: measured by ↔ Process Task

• measures :: measured by ↔ Risk

PPI

x_inpgh_upmx_ppi

Process Performance Indicators (PPI) represent a measurement of the achievement of strategic and operational goals that a company wants to achieve on a process level.

Connected types (2) · bidirectional

• consists of :: is part of ↔ Metric

• requires :: required by ↔ Value Stream

Program

x_inpgh_upmx_program

A Program is a collection of Projects.

Connected types (7) · bidirectional

• has interest :: has relevance ↔ Actor

• contributes :: contributed by ↔ Demand

• contributes :: contributed by ↔ Idea

• Contains :: Contained by ↔ Portfolio

• Governs :: Governed by ↔ Project

• impacts :: impacted by ↔ Risk

• is implemented by :: implements ↔ Strategy

Project

x_inpgh_upmx_project

Projects are planned set of interrelated tasks to be executed over a fixed period and within certain cost and other limitations. It is a major undertaking, especially one involving considerable money, personnel, and equipment.

Connected types (165) · bidirectional

• has interest :: has relevance ↔ Actor

• Creates :: Created by ↔ Business Application

• Deletes :: Deleted by ↔ Business Application

• Introduces :: Introduced by ↔ Business Application

• Migrates :: Migrated by ↔ Business Application

• Removes :: Removed by ↔ Business Application

• Updates :: Updated by ↔ Business Application

• Creates :: Created by ↔ Business Capability

• Introduces :: Introduced by ↔ Business Capability

• Removes :: Removed by ↔ Business Capability

• Updates :: Updated by ↔ Business Capability

• Creates :: Created by ↔ Business Process

• Introduces :: Introduced by ↔ Business Process

• Removes :: Removed by ↔ Business Process

• Updates :: Updated by ↔ Business Process

• Creates :: Created by ↔ Business Product

• Introduces :: Introduced by ↔ Business Product

• Removes :: Removed by ↔ Business Product

• Updates :: Updated by ↔ Business Product

• Creates :: Created by ↔ Capability Instance

• Introduces :: Introduced by ↔ Capability Instance

• Removes :: Removed by ↔ Capability Instance

• Updates :: Updated by ↔ Capability Instance

• Creates :: Created by ↔ Data Store

• Introduces :: Introduced by ↔ Data Store

• Removes :: Removed by ↔ Data Store

• Updates :: Updated by ↔ Data Store

• Creates :: Created by ↔ Database

• Introduces :: Introduced by ↔ Database

• Migrates :: Migrated by ↔ Database

• Updates :: Updated by ↔ Database

• leads to :: led from ↔ Demand

• Creates :: Created by ↔ Domain

• Introduces :: Introduced by ↔ Domain

• Migrates :: Migrated by ↔ Domain

• Removes :: Removed by ↔ Domain

• Updates :: Updated by ↔ Domain

• Introduces :: Introduced by ↔ Hardware Product

• Migrates :: Migrated by ↔ Hardware Product

• Removes :: Removed by ↔ Hardware Product

• Updates :: Updated by ↔ Hardware Product

• leads to :: led from ↔ Idea

• Creates :: Created by ↔ Information Object

• Introduces :: Introduced by ↔ Information Object

• Removes :: Removed by ↔ Information Object

• Updates :: Updated by ↔ Information Object

• is implemented by :: implements ↔ Initiative

• Creates :: Created by ↔ Journey

• Introduces :: Introduced by ↔ Journey

• Migrates :: Migrated by ↔ Journey

• Removes :: Removed by ↔ Journey

• Updates :: Updated by ↔ Journey

• Supports :: is Supported by ↔ Layer Architecture

• Creates :: Created by ↔ Logical Interface

• Introduces :: Introduced by ↔ Logical Interface

• Removes :: Removed by ↔ Logical Interface

• Updates :: Updated by ↔ Logical Interface

• Creates :: Created by ↔ Mapped Application Service

• Introduces :: Introduced by ↔ Mapped Application Service

• Migrates :: Migrated by ↔ Mapped Application Service

• Removes :: Removed by ↔ Mapped Application Service

• Updates :: Updated by ↔ Mapped Application Service

• Creates :: Created by ↔ Microservice

• Introduces :: Introduced by ↔ Microservice

• Migrates :: Migrated by ↔ Microservice

• Removes :: Removed by ↔ Microservice

• Updates :: Updated by ↔ Microservice

• Creates :: Created by ↔ Mobile Application

• Introduces :: Introduced by ↔ Mobile Application

• Migrates :: Migrated by ↔ Mobile Application

• Removes :: Removed by ↔ Mobile Application

• Updates :: Updated by ↔ Mobile Application

• Implements :: Implemented by ↔ Objective

• is implemented by :: implements ↔ Objective

• Creates :: Created by ↔ Pattern

• Introduces :: Introduced by ↔ Pattern

• Updates :: Updated by ↔ Pattern

• Creates :: Created by ↔ Physical Interface

• Introduces :: Introduced by ↔ Physical Interface

• Migrates :: Migrated by ↔ Physical Interface

• Removes :: Removed by ↔ Physical Interface

• Updates :: Updated by ↔ Physical Interface

• Creates :: Created by ↔ Portfolio Element

• Introduces :: Introduced by ↔ Portfolio Element

• Migrates :: Migrated by ↔ Portfolio Element

• Removes :: Removed by ↔ Portfolio Element

• Updates :: Updated by ↔ Portfolio Element

• Compliant :: Compliant with ↔ Principle

• Conformant :: Conformant with ↔ Principle

• Fully Conformant :: Fully Conformant with ↔ Principle

• Non-Compliant :: Non-Compliant with ↔ Principle

• Non-Conformant :: Non-Conformant with ↔ Principle

• Creates :: Created by ↔ Process

• Introduces :: Introduced by ↔ Process

• Removes :: Removed by ↔ Process

• Updates :: Updated by ↔ Process

• Creates :: Created by ↔ Process Activity

• Introduces :: Introduced by ↔ Process Activity

• Migrates :: Migrated by ↔ Process Activity

• Removes :: Removed by ↔ Process Activity

• Updates :: Updated by ↔ Process Activity

• Creates :: Created by ↔ Process Category

• Introduces :: Introduced by ↔ Process Category

• Migrates :: Migrated by ↔ Process Category

• Removes :: Removed by ↔ Process Category

• Updates :: Updated by ↔ Process Category

• Creates :: Created by ↔ Process Group

• Introduces :: Introduced by ↔ Process Group

• Migrates :: Migrated by ↔ Process Group

• Removes :: Removed by ↔ Process Group

• Updates :: Updated by ↔ Process Group

• Creates :: Created by ↔ Process Operations

• Introduces :: Introduced by ↔ Process Operations

• Migrates :: Migrated by ↔ Process Operations

• Removes :: Removed by ↔ Process Operations

• Updates :: Updated by ↔ Process Operations

• Creates :: Created by ↔ Process Task

• Introduces :: Introduced by ↔ Process Task

• Migrates :: Migrated by ↔ Process Task

• Removes :: Removed by ↔ Process Task

• Updates :: Updated by ↔ Process Task

• Creates :: Created by ↔ Process Workflow

• Introduces :: Introduced by ↔ Process Workflow

• Migrates :: Migrated by ↔ Process Workflow

• Removes :: Removed by ↔ Process Workflow

• Updates :: Updated by ↔ Process Workflow

• Governs :: Governed by ↔ Program

• Depends on :: Used by ↔ Project

• consists of :: is part of ↔ Project Task

• impacts :: impacted by ↔ Risk

• Supports :: is Supported by ↔ Segment Architecture

• Creates :: Created by ↔ Server

• Introduces :: Introduced by ↔ Server

• Updates :: Updated by ↔ Server

• Creates :: Created by ↔ Service

• Introduces :: Introduced by ↔ Service

• Removes :: Removed by ↔ Service

• Updates :: Updated by ↔ Service

• Creates :: Created by ↔ Social Media

• Introduces :: Introduced by ↔ Social Media

• Migrates :: Migrated by ↔ Social Media

• Removes :: Removed by ↔ Social Media

• Updates :: Updated by ↔ Social Media

• Creates :: Created by ↔ Software Product

• Introduces :: Introduced by ↔ Software Product

• Migrates :: Migrated by ↔ Software Product

• Removes :: Removed by ↔ Software Product

• Updates :: Updated by ↔ Software Product

• Supports :: is Supported by ↔ Solution Architecture

• Creates :: Created by ↔ Solution Use Case

• Introduces :: Introduced by ↔ Solution Use Case

• Migrates :: Migrated by ↔ Solution Use Case

• Removes :: Removed by ↔ Solution Use Case

• Updates :: Updated by ↔ Solution Use Case

• is implemented by :: implements ↔ Strategy

• Creates :: Created by ↔ Value Stream

• Introduces :: Introduced by ↔ Value Stream

• Migrates :: Migrated by ↔ Value Stream

• Removes :: Removed by ↔ Value Stream

• Updates :: Updated by ↔ Value Stream

• Creates :: Created by ↔ Website

• Introduces :: Introduced by ↔ Website

• Migrates :: Migrated by ↔ Website

• Removes :: Removed by ↔ Website

• Updates :: Updated by ↔ Website

Project Task

x_inpgh_upmx_task

A Task is a project related activity that needs to be accomplished within a defined period of time or by a deadline.

Connected types (3) · bidirectional

• leads to :: led from ↔ Demand

• consists of :: is part of ↔ Project

• impacts :: impacted by ↔ Risk

Risk

x_inpgh_upmx_risk

A Risk highlights competitive, economic, operational, legal, compliance, strategic, program, project, quality, process, technology etc. risks, which causes business to fail.

Connected types (46) · bidirectional

• impacts :: impacted by ↔ Actor

• impacts :: impacted by ↔ AI Model

• impacts :: impacted by ↔ Building Block

• impacts :: impacted by ↔ Business Application

• impacts :: impacted by ↔ Business Capability

• impacts :: impacted by ↔ Business Process

• impacts :: impacted by ↔ Business Product

• impacts :: impacted by ↔ Capability Instance

• impacts :: impacted by ↔ Channel

• impacts :: impacted by ↔ Data Store

• impacts :: impacted by ↔ Domain

• impacts :: impacted by ↔ Driver

• impacts :: impacted by ↔ Goal

• impacts :: impacted by ↔ Hardware Product

• impacts :: impacted by ↔ Initiative

• impacts :: impacted by ↔ Journey

• impacts :: impacted by ↔ Logical Interface

• impacts :: impacted by ↔ Mapped Application Service

• impacts :: impacted by ↔ Market

• measures :: measured by ↔ Metric

• impacts :: impacted by ↔ Microservice

• impacts :: impacted by ↔ Mobile Application

• impacts :: impacted by ↔ Objective

• impacts :: impacted by ↔ Organizational Unit

• impacts :: impacted by ↔ Pattern

• impacts :: impacted by ↔ Physical Interface

• Contains :: Contained by ↔ Portfolio

• impacts :: impacted by ↔ Process

• impacts :: impacted by ↔ Process Activity

• impacts :: impacted by ↔ Process Category

• impacts :: impacted by ↔ Process Group

• impacts :: impacted by ↔ Process Operations

• impacts :: impacted by ↔ Process Task

• impacts :: impacted by ↔ Process Workflow

• impacts :: impacted by ↔ Program

• impacts :: impacted by ↔ Project

• impacts :: impacted by ↔ Project Task

• impacts :: impacted by ↔ Service

• impacts :: impacted by ↔ Social Media

• impacts :: impacted by ↔ Software Product

• impacts :: impacted by ↔ Solution Use Case

• impacts :: impacted by ↔ Strategy

• impacts :: impacted by ↔ Technical Capability

• impacts :: impacted by ↔ Value Chain

• impacts :: impacted by ↔ Value Stream

• impacts :: impacted by ↔ Website

Applications & Technology

The logical and physical technology landscape that realizes business capabilities.

Chatbot

x_inpgh_upmx_chatbot

A Chatbot is a computer program designed to simulate conversation with human users, especially over the internet.

Component

x_inpgh_upmx_component

A Component encapsulation of technology infrastructure or application functionality that is aligned to implementation structuring.

Inbound relationships (7)

• Actor → has interest :: has relevance

• Business Application → Uses :: Used by

• Hardware Product → consists of :: is part of

• Pattern → consists of :: is part of

• Software Product → consists of :: is part of

• Solution Use Case → consists of :: is part of

• Technical Capability → Provided By :: Provides

Outbound relationships (5)

• has interest :: has relevance → Actor

• consists of :: is part of → Hardware Product

• consists of :: is part of → Pattern

• consists of :: is part of → Software Product

• consists of :: is part of → Solution Use Case

Domain

x_inpgh_upmx_domain

A Domain name is the address where users can access the website or application via browser.

Inbound relationships (11)

• Actor → has interest :: has relevance

• Business Application → Uses :: Used by

• Pattern → consists of :: is part of

• Project → Creates :: Created by

• Project → Introduces :: Introduced by

• Project → Migrates :: Migrated by

• Project → Removes :: Removed by

• Project → Updates :: Updated by

• Risk → impacts :: impacted by

• Solution Use Case → consists of :: is part of

• Technical Capability → Provided By :: Provides

Outbound relationships (9)

• has interest :: has relevance → Actor

• consists of :: is part of → Pattern

• Creates :: Created by → Project

• Introduces :: Introduced by → Project

• Migrates :: Migrated by → Project

• Removes :: Removed by → Project

• Updates :: Updated by → Project

• impacts :: impacted by → Risk

• consists of :: is part of → Solution Use Case

Hardware Product

x_inpgh_upmx_hardware_product

A Hardware Product is a logical representation of a particular kind of commercially built or custom developed hardware e.g. Apple iPhone X.

Inbound relationships (23)

• Actor → has interest :: has relevance

• Business Application → Uses :: Used by

• Component → consists of :: is part of

• Hardware Product → has target :: is target

• Layer Architecture → Uses :: Used by

• Organizational Unit → Uses :: Used by

• Pattern → consists of :: is part of

• Principle → Compliant :: Compliant with

• Principle → Conformant :: Conformant with

• Principle → Fully Conformant :: Fully Conformant with

• Principle → Non-Compliant :: Non-Compliant with

• Principle → Non-Conformant :: Non-Conformant with

• Project → Introduces :: Introduced by

• Project → Migrates :: Migrated by

• Project → Removes :: Removed by

• Project → Updates :: Updated by

• Risk → impacts :: impacted by

• Segment Architecture → Uses :: Used by

• Server → Deploys :: Deployed by

• Server → has Instance :: is Instance of

• Solution Architecture → Uses :: Used by

• Solution Use Case → consists of :: is part of

• Technical Capability → Provided By :: Provides

Outbound relationships (23)

• has interest :: has relevance → Actor

• consists of :: is part of → Component

• has Instance :: is Instance of → Hardware

• has target :: is target → Hardware Product

• Uses :: Used by → Layer Architecture

• Uses :: Used by → Organizational Unit

• consists of :: is part of → Pattern

• Compliant :: Compliant with → Principle

• Conformant :: Conformant with → Principle

• Fully Conformant :: Fully Conformant with → Principle

• Non-Compliant :: Non-Compliant with → Principle

• Non-Conformant :: Non-Conformant with → Principle

• Introduces :: Introduced by → Project

• Migrates :: Migrated by → Project

• Removes :: Removed by → Project

• Updates :: Updated by → Project

• impacts :: impacted by → Risk

• Uses :: Used by → Segment Architecture

• Deploys :: Deployed by → Server

• has Instance :: is Instance of → Server

• Uses :: Used by → Solution Architecture

• consists of :: is part of → Solution Use Case

• Provided By :: Provides → Technical Capability

Logical Application

x_inpgh_upmx_logical_application

A Logical Application is a higher level aggregation of a Business Application to respond to Business requirements on a conceptional/logical level.

Inbound relationships (8)

• Business Capability → Provided By :: Provides

• Capability Instance → Provided By :: Provides

• Logical Interface → Sends Data to :: Receives Data from

• Principle → Compliant :: Compliant with

• Principle → Conformant :: Conformant with

• Principle → Fully Conformant :: Fully Conformant with

• Principle → Non-Compliant :: Non-Compliant with

• Principle → Non-Conformant :: Non-Conformant with

Outbound relationships (8)

• Uses :: Used by → Business Application

• Provided By :: Provides → Capability Instance

• Sends Data to :: Receives Data from → Logical Interface

• Compliant :: Compliant with → Principle

• Conformant :: Conformant with → Principle

• Fully Conformant :: Fully Conformant with → Principle

• Non-Compliant :: Non-Compliant with → Principle

• Non-Conformant :: Non-Conformant with → Principle

Microservice

x_inpgh_upmx_microservice

A Microservice is an application component communicating with other Microservices across common interfaces e.g. APIs, REST.

Inbound relationships (12)

• Actor → has interest :: has relevance

• Business Application → Uses :: Used by

• Microservice → Sends Data to :: Receives Data from

• Pattern → consists of :: is part of

• Project → Creates :: Created by

• Project → Introduces :: Introduced by

• Project → Migrates :: Migrated by

• Project → Removes :: Removed by

• Project → Updates :: Updated by

• Risk → impacts :: impacted by

• Solution Use Case → consists of :: is part of

• Technical Capability → Provided By :: Provides

Outbound relationships (11)

• has interest :: has relevance → Actor

• Sends Data to :: Receives Data from → Microservice

• consists of :: is part of → Pattern

• Creates :: Created by → Project

• Introduces :: Introduced by → Project

• Migrates :: Migrated by → Project

• Removes :: Removed by → Project

• Updates :: Updated by → Project

• impacts :: impacted by → Risk

• Uses :: Used by → Software Product

• consists of :: is part of → Solution Use Case

Mobile Application

x_inpgh_upmx_mobile_application

A Mobile Application is an end-user application consumed on a mobile device.

Inbound relationships (11)

• Actor → has interest :: has relevance

• Business Application → Uses :: Used by

• Pattern → consists of :: is part of

• Project → Creates :: Created by

• Project → Introduces :: Introduced by

• Project → Migrates :: Migrated by

• Project → Removes :: Removed by

• Project → Updates :: Updated by

• Risk → impacts :: impacted by

• Solution Use Case → consists of :: is part of

• Technical Capability → Provided By :: Provides

Outbound relationships (9)

• has interest :: has relevance → Actor

• consists of :: is part of → Pattern

• Creates :: Created by → Project

• Introduces :: Introduced by → Project

• Migrates :: Migrated by → Project

• Removes :: Removed by → Project

• Updates :: Updated by → Project

• impacts :: impacted by → Risk

• consists of :: is part of → Solution Use Case

Social Media

x_inpgh_upmx_social_media

Social Media is an internet-based technology facilitating the sharing of ideas, thoughts, and information through building of virtual networks and communities.

Inbound relationships (11)

• Actor → has interest :: has relevance

• Business Application → Uses :: Used by

• Pattern → consists of :: is part of

• Project → Creates :: Created by

• Project → Introduces :: Introduced by

• Project → Migrates :: Migrated by

• Project → Removes :: Removed by

• Project → Updates :: Updated by

• Risk → impacts :: impacted by

• Solution Use Case → consists of :: is part of

• Technical Capability → Provided By :: Provides

Outbound relationships (9)

• has interest :: has relevance → Actor

• consists of :: is part of → Pattern

• Creates :: Created by → Project

• Introduces :: Introduced by → Project

• Migrates :: Migrated by → Project

• Removes :: Removed by → Project

• Updates :: Updated by → Project

• impacts :: impacted by → Risk

• consists of :: is part of → Solution Use Case

Software Product

x_inpgh_upmx_software_product

A Software Product is a logical representation of a particular kind of commercially built or custom developed software e.g. Adobe Acrobat Reader V11.x.

Inbound relationships (27)

• Actor → has interest :: has relevance

• AI Model → Uses :: Used by

• Business Application → Uses :: Used by

• Component → consists of :: is part of

• Layer Architecture → Uses :: Used by

• Logical Interface → Uses :: Used by

• Microservice → Uses :: Used by

• Organizational Unit → Uses :: Used by

• Pattern → consists of :: is part of

• Principle → Compliant :: Compliant with

• Principle → Conformant :: Conformant with

• Principle → Fully Conformant :: Fully Conformant with

• Principle → Non-Compliant :: Non-Compliant with

• Principle → Non-Conformant :: Non-Conformant with

• Project → Creates :: Created by

• Project → Introduces :: Introduced by

• Project → Migrates :: Migrated by

• Project → Removes :: Removed by

• Project → Updates :: Updated by

• Risk → impacts :: impacted by

• Segment Architecture → Uses :: Used by

• Software → has Instance :: is Instance of

• Software Product → has target :: is target

• Software Product → requires :: required by

• Solution Architecture → Uses :: Used by

• Solution Use Case → consists of :: is part of

• Technical Capability → Provided By :: Provides

Outbound relationships (24)

• has interest :: has relevance → Actor

• Uses :: Used by → AI Model

• consists of :: is part of → Component

• Uses :: Used by → Layer Architecture

• Uses :: Used by → Organizational Unit

• consists of :: is part of → Pattern

• Compliant :: Compliant with → Principle

• Conformant :: Conformant with → Principle

• Fully Conformant :: Fully Conformant with → Principle

• Non-Compliant :: Non-Compliant with → Principle

• Non-Conformant :: Non-Conformant with → Principle

• Creates :: Created by → Project

• Introduces :: Introduced by → Project

• Migrates :: Migrated by → Project

• Removes :: Removed by → Project

• Updates :: Updated by → Project

• impacts :: impacted by → Risk

• Uses :: Used by → Segment Architecture

• has Instance :: is Instance of → Software

• has target :: is target → Software Product

• requires :: required by → Software Product

• Uses :: Used by → Solution Architecture

• consists of :: is part of → Solution Use Case

• Provided By :: Provides → Technical Capability

Technical Capability

x_inpgh_upmx_technical_capability

The Technical Capability helps to establish a business language in requirements specification without focusing on specific technologies and vendor solutions. A Technical Capability specifies functional requirements of Business Capabilities provided by Software and Hardware Products e.g. Business Metrics. Business Applications can use a sub-set of Technical Capabilities to provide Business Capabilities.

Inbound relationships (8)

• Actor → has interest :: has relevance

• Business Application → Enables :: Enabled by

• Business Capability → requires :: required by

• Capability Instance → requires :: required by

• Hardware Product → Provided By :: Provides

• Portfolio → Contains :: Contained by

• Risk → impacts :: impacted by

• Software Product → Provided By :: Provides

Outbound relationships (15)

• has interest :: has relevance → Actor

• Enables :: Enabled by → Business Application

• requires :: required by → Business Capability

• requires :: required by → Capability Instance

• Provided By :: Provides → Component

• Provided By :: Provides → Domain

• Provided By :: Provides → Hardware Product

• Provided By :: Provides → Microservice

• Provided By :: Provides → Mobile Application

• Provided By :: Provides → Pattern

• Contains :: Contained by → Portfolio

• impacts :: impacted by → Risk

• Provided By :: Provides → Social Media

• Provided By :: Provides → Software Product

• Provided By :: Provides → Website

Website

x_inpgh_upmx_website

An internal or external website used by the organizational users.

Inbound relationships (11)

• Actor → has interest :: has relevance

• Business Application → Uses :: Used by

• Pattern → consists of :: is part of

• Project → Creates :: Created by

• Project → Introduces :: Introduced by

• Project → Migrates :: Migrated by

• Project → Removes :: Removed by

• Project → Updates :: Updated by

• Risk → impacts :: impacted by

• Solution Use Case → consists of :: is part of

• Technical Capability → Provided By :: Provides

Outbound relationships (9)

• has interest :: has relevance → Actor

• consists of :: is part of → Pattern

• Creates :: Created by → Project

• Introduces :: Introduced by → Project

• Migrates :: Migrated by → Project

• Removes :: Removed by → Project

• Updates :: Updated by → Project

• impacts :: impacted by → Risk

• consists of :: is part of → Solution Use Case

Data & Integration

How information is represented, stored, exchanged, and traced across the landscape.

Conceptual Data Object

x_inpgh_upmx_conceptional_data_object

A conceptual data object is a high-level representation of business information used to describe meaning, ownership, lineage, and information flow before logical or physical implementation details are introduced.

Connected types (2) · bidirectional

• is associated with :: is associated with ↔ Conceptual Data Object

• is composed of :: is part of ↔ Conceptual Data Object

Data Store

x_inpgh_upmx_data_store

A Data Store is a logical representation of a physical database or file which contains data used by applications or software.

Connected types (11) · bidirectional

• has interest :: has relevance ↔ Actor

• Uses :: Used by ↔ AI Model

• has Instance :: is Instance of ↔ Database

• has Instance :: is Instance of ↔ Database Instance

• has source-of-record :: is source-of-record ↔ Information Object

• is stored in :: stores ↔ Information Object

• Creates :: Created by ↔ Project

• Introduces :: Introduced by ↔ Project

• Removes :: Removed by ↔ Project

• Updates :: Updated by ↔ Project

• impacts :: impacted by ↔ Risk

Logical Data Object

x_inpgh_upmx_logical_data_object

A Logical Data Object specifies the high-level information flow and data lineage on a logical level.

Connected types (7) · bidirectional

• requires :: required by ↔ Business Application

• Updates :: Updated by ↔ Business Application

• has Instance :: is Instance of ↔ Information Object

• Creates :: Created by ↔ Mapped Application Service

• Reads :: Read by ↔ Mapped Application Service

• requires :: required by ↔ Mapped Application Service

• Updates :: Updated by ↔ Mapped Application Service

Logical Interface

x_inpgh_upmx_logical_interface

A Logical Interface is an abstract representation of one or more physical interfaces provided by an Application instance. It helps to understand the integration of Business Applications, and the realization of the data flow i.e. data-lineage.

Inbound relationships (14)

• Actor → has interest :: has relevance

• Business Application → Provides :: Provided by

• Business Application → Sends Data to :: Receives Data from

• Information Object → Transports :: Transported by

• Layer Architecture → impacts :: impacted by

• Logical Application → Sends Data to :: Receives Data from

• Physical Interface → has Instance :: is Instance of

• Project → Creates :: Created by

• Project → Introduces :: Introduced by

• Project → Removes :: Removed by

• Project → Updates :: Updated by

• Risk → impacts :: impacted by

• Segment Architecture → impacts :: impacted by

• Solution Architecture → impacts :: impacted by

Outbound relationships (14)

• has interest :: has relevance → Actor

• Sends Data to :: Receives Data from → Business Application

• Transports :: Transported by → Information Object

• impacts :: impacted by → Layer Architecture

• Sends Data to :: Receives Data from → Logical Application

• has Instance :: is Instance of → Physical Interface

• Creates :: Created by → Project

• Introduces :: Introduced by → Project

• Removes :: Removed by → Project

• Updates :: Updated by → Project

• impacts :: impacted by → Risk

• impacts :: impacted by → Segment Architecture

• Uses :: Used by → Software Product

• impacts :: impacted by → Solution Architecture

Physical Data Object

x_inpgh_upmx_physical_data_object

A Physical Data Object specifies the high-level information flow and data lineage on a physical level.

Physical Interface

x_inpgh_upmx_physical_interface

A Physical Interface is a technical implemented interface provided or consumed by an Application Service. It helps to understand the integration of Application instances, and the realization of the data flow i.e. data-lineage.

Connected types (10) · bidirectional

• has interest :: has relevance ↔ Actor

• Transports :: Transported by ↔ Information Object

• has Instance :: is Instance of ↔ Logical Interface

• Sends Data to :: Receives Data from ↔ Mapped Application Service

• Creates :: Created by ↔ Project

• Introduces :: Introduced by ↔ Project

• Migrates :: Migrated by ↔ Project

• Removes :: Removed by ↔ Project

• Updates :: Updated by ↔ Project

• impacts :: impacted by ↔ Risk

Architecture Assets

Reusable architecture content, debt, decisions, and solution patterns.

Book of Debt

x_inpgh_upmx_book_of_debt

A Book of Debt records and tracks technical and organizational debt items for prioritized resolution.

Building Block

x_inpgh_upmx_building_block

A Building Block is a reusable compilation of various Portfolio Elements e.g. Business Products, Strategies to provide higher level concept solutions, designs and templates to the Business.

Connected types (15) · bidirectional

• consists of :: is part of ↔ Business Application

• consists of :: is part of ↔ Business Capability

• consists of :: is part of ↔ Business Product

• consists of :: is part of ↔ Capability Instance

• consists of :: is part of ↔ Information Object

• consists of :: is part of ↔ Initiative

• consists of :: is part of ↔ Journey

• consists of :: is part of ↔ Pattern

• Contains :: Contained by ↔ Portfolio

• consists of :: is part of ↔ Principle

• consists of :: is part of ↔ Process

• impacts :: impacted by ↔ Risk

• consists of :: is part of ↔ Service

• consists of :: is part of ↔ Strategy

• consists of :: is part of ↔ Value Stream

Decision Log

x_inpgh_upmx_decision_log

A Decision Log records key architectural and strategic decisions with rationale and context.

Layer Architecture

x_inpgh_upmx_layer_architecture

A Layer Architecture organizes components into horizontal layers with defined responsibilities and dependencies.

Connected types (19) · bidirectional

• impacts :: impacted by ↔ Business Application

• impacts :: impacted by ↔ Business Capability

• impacts :: impacted by ↔ Capability Instance

• impacts :: impacted by ↔ Demand

• Uses :: Used by ↔ Hardware Product

• contributes :: contributed by ↔ Idea

• Supports :: is Supported by ↔ Initiative

• impacts :: impacted by ↔ Logical Interface

• Uses :: Used by ↔ Pattern

• Supports :: is Supported by ↔ Policy

• Compliant :: Compliant with ↔ Principle

• Conformant :: Conformant with ↔ Principle

• Fully Conformant :: Fully Conformant with ↔ Principle

• Non-Compliant :: Non-Compliant with ↔ Principle

• Non-Conformant :: Non-Conformant with ↔ Principle

• impacts :: impacted by ↔ Process

• Supports :: is Supported by ↔ Project

• Uses :: Used by ↔ Software Product

• Supports :: is Supported by ↔ Strategy

Pattern

x_inpgh_upmx_pattern

A Pattern is a reusable compilation of various Portfolio Elements e.g. Business Applications, Software Products to provide pre-defined solutions, designs and templates to the Business and IT.

Inbound relationships (28)

• Actor → has interest :: has relevance

• Building Block → consists of :: is part of

• Business Application → consists of :: is part of

• Business Application → Deploys :: Deployed by

• Component → consists of :: is part of

• Domain → consists of :: is part of

• Hardware Product → consists of :: is part of

• Layer Architecture → Uses :: Used by

• Microservice → consists of :: is part of

• Mobile Application → consists of :: is part of

• Pattern → consists of :: is part of

• Portfolio → Contains :: Contained by

• Principle → Compliant :: Compliant with

• Principle → Conformant :: Conformant with

• Principle → Fully Conformant :: Fully Conformant with

• Principle → Non-Compliant :: Non-Compliant with

• Principle → Non-Conformant :: Non-Conformant with

• Project → Creates :: Created by

• Project → Introduces :: Introduced by

• Project → Updates :: Updated by

• Risk → impacts :: impacted by

• Segment Architecture → Uses :: Used by

• Social Media → consists of :: is part of

• Software Product → consists of :: is part of

• Solution Architecture → Uses :: Used by

• Solution Use Case → consists of :: is part of

• Technical Capability → Provided By :: Provides

• Website → consists of :: is part of

Outbound relationships (27)

• has interest :: has relevance → Actor

• consists of :: is part of → Building Block

• consists of :: is part of → Business Application

• Deploys :: Deployed by → Business Application

• consists of :: is part of → Component

• consists of :: is part of → Domain

• consists of :: is part of → Hardware Product

• Uses :: Used by → Layer Architecture

• consists of :: is part of → Microservice

• consists of :: is part of → Mobile Application

• consists of :: is part of → Pattern

• Contains :: Contained by → Portfolio

• Compliant :: Compliant with → Principle

• Conformant :: Conformant with → Principle

• Fully Conformant :: Fully Conformant with → Principle

• Non-Compliant :: Non-Compliant with → Principle

• Non-Conformant :: Non-Conformant with → Principle

• Creates :: Created by → Project

• Introduces :: Introduced by → Project

• Updates :: Updated by → Project

• impacts :: impacted by → Risk

• Uses :: Used by → Segment Architecture

• consists of :: is part of → Social Media

• consists of :: is part of → Software Product

• Uses :: Used by → Solution Architecture

• consists of :: is part of → Solution Use Case

• consists of :: is part of → Website

Portfolio

x_inpgh_upmx_portfolio

A Portfolio is a managed collection of programs, projects, and portfolio elements aligned to strategic objectives.

Connected types (14) · bidirectional

• Contains :: Contained by ↔ Building Block

• Contains :: Contained by ↔ Business Application

• Contains :: Contained by ↔ Business Capability

• Contains :: Contained by ↔ Business Process

• Contains :: Contained by ↔ Business Product

• Contains :: Contained by ↔ Business Service

• Contains :: Contained by ↔ Capability Instance

• Contains :: Contained by ↔ Information Object

• Contains :: Contained by ↔ Initiative

• Contains :: Contained by ↔ Pattern

• Contains :: Contained by ↔ Process

• Contains :: Contained by ↔ Program

• Contains :: Contained by ↔ Risk

• Contains :: Contained by ↔ Technical Capability

Segment Architecture

x_inpgh_upmx_segment_architecture

A Segment Architecture defines vertical segments of the enterprise architecture for specific business domains.

Connected types (19) · bidirectional

• impacts :: impacted by ↔ Business Application

• impacts :: impacted by ↔ Business Capability

• impacts :: impacted by ↔ Capability Instance

• impacts :: impacted by ↔ Demand

• Uses :: Used by ↔ Hardware Product

• contributes :: contributed by ↔ Idea

• Supports :: is Supported by ↔ Initiative

• impacts :: impacted by ↔ Logical Interface

• Uses :: Used by ↔ Pattern

• Supports :: is Supported by ↔ Policy

• Compliant :: Compliant with ↔ Principle

• Conformant :: Conformant with ↔ Principle

• Fully Conformant :: Fully Conformant with ↔ Principle

• Non-Compliant :: Non-Compliant with ↔ Principle

• Non-Conformant :: Non-Conformant with ↔ Principle

• impacts :: impacted by ↔ Process

• Supports :: is Supported by ↔ Project

• Uses :: Used by ↔ Software Product

• Supports :: is Supported by ↔ Strategy

Solution Architecture

x_inpgh_upmx_solution_architecture

A Solution Architecture describes the structure and behavior of a specific solution addressing business needs.

Connected types (19) · bidirectional

• impacts :: impacted by ↔ Business Application

• impacts :: impacted by ↔ Business Capability

• impacts :: impacted by ↔ Capability Instance

• impacts :: impacted by ↔ Demand

• Uses :: Used by ↔ Hardware Product

• contributes :: contributed by ↔ Idea

• Supports :: is Supported by ↔ Initiative

• impacts :: impacted by ↔ Logical Interface

• Uses :: Used by ↔ Pattern

• Supports :: is Supported by ↔ Policy

• Compliant :: Compliant with ↔ Principle

• Conformant :: Conformant with ↔ Principle

• Fully Conformant :: Fully Conformant with ↔ Principle

• Non-Compliant :: Non-Compliant with ↔ Principle

• Non-Conformant :: Non-Conformant with ↔ Principle

• impacts :: impacted by ↔ Process

• Supports :: is Supported by ↔ Project

• Uses :: Used by ↔ Software Product

• Supports :: is Supported by ↔ Strategy

Solution Use Case

x_inpgh_upmx_solution_use_case

A Solution Use Case consists of Process Operations and a set of technologies to implement Process Tasks.

Inbound relationships (20)

• Actor → has interest :: has relevance

• Component → consists of :: is part of

• Control → impacts :: impacted by

• Domain → consists of :: is part of

• Hardware Product → consists of :: is part of

• Microservice → consists of :: is part of

• Mobile Application → consists of :: is part of

• Organizational Unit → Uses :: Used by

• Pattern → consists of :: is part of

• Process Operations → consists of :: is part of

• Process Task → Implements :: Implemented by

• Project → Creates :: Created by

• Project → Introduces :: Introduced by

• Project → Migrates :: Migrated by

• Project → Removes :: Removed by

• Project → Updates :: Updated by

• Risk → impacts :: impacted by

• Social Media → consists of :: is part of

• Software Product → consists of :: is part of

• Website → consists of :: is part of

Outbound relationships (19)

• has interest :: has relevance → Actor

• consists of :: is part of → Component

• impacts :: impacted by → Control

• consists of :: is part of → Domain

• consists of :: is part of → Hardware Product

• consists of :: is part of → Microservice

• consists of :: is part of → Mobile Application

• consists of :: is part of → Pattern

• consists of :: is part of → Process Operations

• Implements :: Implemented by → Process Task

• Creates :: Created by → Project

• Introduces :: Introduced by → Project

• Migrates :: Migrated by → Project

• Removes :: Removed by → Project

• Updates :: Updated by → Project

• impacts :: impacted by → Risk

• consists of :: is part of → Social Media

• consists of :: is part of → Software Product

• consists of :: is part of → Website

---

AI Runtime Core (introducing with V26)

New tables that extend the runtime architecture of AI-enabled systems. They cover agents, models, datasets, prompt templates, and executable skills, all inheriting from Portfolio Element.

AI Agent

x_inpgh_upmx_ai_agent

An AI Agent is an autonomous software entity that can perceive, reason, and act to accomplish tasks on behalf of users.

AI Model

x_inpgh_upmx_ai_model

An AI Model is a trained machine learning model that processes inputs and generates predictions or decisions.

Connected types (23) · bidirectional

• has successor :: has predecessor ↔ AI Model

• Depends on :: Used by ↔ Business Application

• Integrates :: Integrated by ↔ Business Application

• Uses :: Used by ↔ Business Application

• Provided By :: Provides ↔ Business Capability

• Provided By :: Provides ↔ Business Function

• Uses :: Used by ↔ Business Process

• Contains :: Contained by ↔ Business Product

• requires :: required by ↔ Business Requirement

• Provided By :: Provides ↔ Capability Instance

• Uses :: Used by ↔ Data Store

• Uses :: Used by ↔ Database

• Uses :: Used by ↔ Information Object

• Depends on :: Used by ↔ Mapped Application Service

• Owns :: Owned by ↔ Organizational Unit

• Used by :: Uses ↔ Organizational Unit

• Uses :: Used by ↔ Process Activity

• Uses :: Used by ↔ Process Task

• impacts :: impacted by ↔ Risk

• Runs on :: Runs ↔ Server

• Uses :: Used by ↔ Service

• Uses :: Used by ↔ Software

• Uses :: Used by ↔ Software Product

Dataset

x_inpgh_upmx_dataset

A Dataset is a structured collection of data used for training, evaluating, or operating AI models.

Prompt Template

x_inpgh_upmx_prompt_template

A Prompt Template is a structured text pattern used to instruct AI models with consistent formatting and context.

Skill

x_inpgh_upmx_skill

A Skill is a learned AI capability that can be composed and reused across different AI agents and applications.

---

Portfolio Feature and scoring support tables

These tables extend the model with feature-level views: cost, KPI, lifecycle, indicators, recommendations, scenarios, reference models, stakeholders, hosting, usage, and capability mappings.

Business Capability Mapping

x_inpgh_upmx_business_capability_mapping

Stores business capability mapping records used to map portfolio concepts for analysis and reporting.

Cost

x_inpgh_upmx_pf_cost

YouDesign Command table containing Cost information.

Cost Breakdown

x_inpgh_upmx_pf_cost_breakdown

YouDesign Command table containing Cost Breakdown information over time.

Indicator Breakdown

x_inpgh_upmx_pf_indicator_breakdown

YouDesign Command table containing Indicator Breakdown definitions.

KPI

x_inpgh_upmx_pf_kpi

YouDesign Command table containing KPI definitions.

KPI Breakdown

x_inpgh_upmx_pf_kpi_breakdown

YouDesign Command table containing KPI information over time.

Lifecycle

x_inpgh_upmx_pf_lifecycle

YouDesign Command table containing Lifecycle definitions.

Lifecycle Breakdown

x_inpgh_upmx_pf_lifecycle_breakdown

YouDesign Command table containing Lifecycle information.

Portfolio Feature

x_inpgh_upmx_portfolio_feature

Superior table for all portfolio features e.g. cost, KPI etc. Do not use for reporting!

Realtime Indicators

x_inpgh_upmx_pf_indicators

YouDesign Command table containing Indicator definitions.

Recommendation

x_inpgh_upmx_pf_recommendation

Defines, what needs to be happen to mitigate risk, reduce cost and improve efficiency.

Reference Model

x_inpgh_upmx_pf_reference_model

A reference model is an abstract framework or domain-specific ontology consisting of an interlinked set of clearly defined concepts.

Scenario

x_inpgh_upmx_pf_scenario

YouDesign Command table containing Scenario information.

Stakeholder

x_inpgh_upmx_pf_stakeholder

A stakeholder is a person, group, role, or organisation with an interest in, influence over, or dependency on a portfolio element or outcome.

Technical Capability Mapping

x_inpgh_upmx_technical_capability_mapping

Stores technical capability mapping records used to map portfolio concepts for analysis and reporting.

---

Reporting, dashboard, and license tables

These tables support dashboards, reports, database views, roadmap visualisations, and license tracking. They turn the metamodel into usable reporting structures.

Business Application > Software Product

x_inpgh_upmx_report_cmdb_app2swp

Reporting Table: Business Application > Software Product

Business Capability > Business Application > Software Product

x_inpgh_upmx_cmdb_cap2cmdb_app2swp

Reporting Table: Business Capability > Business Application > Software Product

Dashboard Filter Store for UPMX Reports

x_inpgh_upmx_dashboard_filter_store

YouDesign Command table to store Dashboard filter settings for YouDesign Command reports.

License Users

x_inpgh_upmx_license_reporting

Stores YouDesign Command license usage and assignment records.

Process > Business Application > Software Product

x_inpgh_upmx_report_proc2cmdb_app2sftprd

Reporting Table: Process > Business Application > Software Product

Roadmap Elements

x_inpgh_upmx_roadmap_elements

YouDesign Command table required for roadmap visualization.

Roadmap Request

x_inpgh_upmx_roadmap_request

YouDesign Command table required for roadmap visualization.

---

Metamodel, relationship suggestion, and rollup tables

These tables configure the metamodel itself and the relationship-picker rules used across YouDesign Command today. The entire section is on the deprecation path and will be removed with V26 once the relationship-picker logic moves to the platform-native CMDB relationship rules.

Deprecation path. These tables will be removed with V26. The relationship suggestions, metamodel definitions, and rollup configuration listed here are being replaced by platform-native CMDB relationship rules and CSDM-aligned configuration. Do not build new integrations against them.

Metamodel

x_inpgh_upmx_metamodel

Stores YouDesign Command metamodel configuration records.

Metamodel Domain

x_inpgh_upmx_metamodel_domain

Stores domains used to group and organise YouDesign Command metamodel concepts.

Metamodel Property

x_inpgh_upmx_metamodel_property

Stores configurable properties used by YouDesign Command metamodel definitions.

Metamodel Relationship

x_inpgh_upmx_metamodel_relationship

Stores configured metamodel relationship definitions used to describe allowed connections between YouDesign Command object types.

Rollup Setting

x_inpgh_upmx_calculation_rollup_rel

Table containing rollup settings for YouDesign Command.

Suggested Relationship

x_inpgh_upmx_rel_type_suggest

Used to store for YouDesign Command Relationship Picker.

Suggested Relationship Field

x_inpgh_upmx_rel_type_suggest_field

Stores field-level configuration used by the YouDesign Command relationship picker.

Suggested Relationship Group

x_inpgh_upmx_rel_type_suggest_group

Used to store for YouDesign Command Relationship Picker.

---

Many-to-many and association tables

These tables connect portfolio elements to stakeholders, scenarios, reference models, and other supporting structures.

Data Definition to Data Definition (m2m)

x_inpgh_upmx_m2m_data_definit_data_definit

YouDesign Command Data Quality

Portfolio Element to Reference Model

x_inpgh_upmx_m2m_pe2reference_model

The many-to-many Relationship between Portfolio Elements and Reference Model.

Portfolio Element to Scenario

x_inpgh_upmx_m2m_scenarios_portfolio_el

The many-to-many Relationship between Portfolio Elements and Scenario.

Portfolio Element to Stakeholder

x_inpgh_upmx_m2m_stakeholders_portfolio_el

The many-to-many Relationship between Portfolio Elements and Stakeholder.

---

Operational, data quality, settings, and support tables

Additional scoped tables that are not object types, feature tables, or reporting tables but are part of the YouDesign Command application.

Attribute Config

x_inpgh_upmx_attribute_config

Stores attribute configuration that controls how YouDesign Command table fields are presented or interpreted.

Attribute Config Breakdown

x_inpgh_upmx_attribute_config_breakdown

Stores attribute configuration breakdown records used by YouDesign Command reporting.

Data Definition Scope

x_inpgh_upmx_data_definition_scope

YouDesign Command Data Quality

Data Quality

x_inpgh_upmx_data_quality

YouDesign Command Data Quality

Global Settings

x_inpgh_upmx_global_settings

Table to store YouDesign Command Global Settings.

Glossary

x_inpgh_upmx_glossary

A glossary of terms & definitions.

Hosting

x_inpgh_upmx_hosting

YouDesign Command table to join hosting related information with Portfolio Elements.

Risk & Compliance

x_inpgh_upmx_risk_compliance

YouDesign Command table to join risk & compliance related information with Portfolio Elements.

Scoped Fields

x_inpgh_upmx_data_definition

YouDesign Command Data Quality

Score Calculation Detail

x_inpgh_upmx_score_calculation_detail

Stores score calculation details used by YouDesign Command scoring and rollup logic.

Usage

x_inpgh_upmx_usage

The Usage specifies an element use within a specific company, or department, or location.