Metamodel
The classes, references and relationships with which YouDesign Command extends the ServiceNow CSDM into a full enterprise portfolio model.
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.
Vocabulary used on this page
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.
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.
Concepts intentionally not implemented
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.
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.
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.
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.
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.
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.
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.”
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.
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.
Policy
x_inpgh_upmx_policy
A statement of direction for an organization. A rule that prohibits or prescribes specific actions for given conditions ...
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.
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.
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.
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.
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.