🔋Metamodel
Provides the overview of the UPM-X application metamodel.
UPM-X Extensions on the ServiceNow CSDM
UPM-X’s metamodel is based on ServiceNow’s out-of-the-box Common Services Data Model enhanced with UPM-X specific extensions to enable UPM-X customers to manage and plan their enterprise portfolios.
All to know about the Information Model is that it comprises:
Classes = Table = Object type = Component type
References = 1-to-many Relationships
Relationships = many-to-many (m2m) Relationships
Hierarchies = parent/child relationships referring to itself
Fields = Properties = Attributes = Column
UPM-X Metamodel
The following metamodel represents the common relationships used to provide a full line-of-sight of the enterprise. In an architecture practice, not all classes are used necessarily.
The green shapes are ServiceNow tables used to provide the full enterprise view. Please note that there are “alternative” tables introduced years ago by UPM-X, which are recently part of the CSDM data model of ServiceNow. As UPM-X is natively extending the CMDB, there is technically no difference between the tables. To avoid confusion, we have included those in our metamodel and renamed the original UPM-X tables to avoid confusion by users.
UPM-X BIZBOK Extensions
The following model shows the BIZBOK extensions additionally to the model of the metamodel above.
There are a few BIZBOK concepts we have decided not to implement in the UPM-X metamodel:
| Object Type | Rationale |
|---|---|
| Change | Redundant with more concrete change concepts: Strategy, Initiative, and Project, as well as superseded by more robust techniques for defining target states in architectures. |
| Course of Action | Redundant with Strategy Concept. |
| Capability Behavior | No current demand from our customers. Can easily implement on a per-customer basis if there is a need. |
| Capability Instance | No current demand from our customers. Can easily implement on a per-customer basis if there is a need. |
| Process Outcome | Redundant with other more robust business process architecture and modeling techniques we already support. And no current demand from our customers. Can easily implement on a per-customer basis if there is a need. |
| Product Entitlement | No current demand from our customers. Can easily implement on a per-customer basis if there is a need. |
UPM-X Metamodel is 100% aligned with ServiceNow CSDM
The model can be managed and extended by any ServiceNow admin.
UPM-X Tables
The following lists include all tables which are part of the UPM-X scope, grouped by core object types, features, and reporting tables:
Core Object Types leveraged from ServiceNow CSDM
The following object types (tables) are used in the context of the UPM-X use-cases with enhanced features and relationships.
💡GOOD TO KNOW
Any ServiceNow table can be leveraged and connected to the UPM-X tables via CI relationships!
| Object Type | Table Name | Description |
|---|---|---|
| Business Application | cmdb_ci_business_app | A Business Application is a logical representation of a unique or multiple instance(s) of one or more deployed software products, physically running in or outside of the enterprise environment, which supports a specific business process/capability. |
| Business Capability | cmdb_ci_business_capability | A Business Capability describes what an organization requires to execute its business model or fulfill its mission. Think of Business Capabilities as organizational-level skills embedded in people, processes, and/or technology. |
| 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. |
⌛ LEGACY TABLES
The legacy tables are technically equivalent to the CSDM tables above and are still supported for existing customers.
- x_inpgh_upmx_business_application
- x_inpgh_upmx_business_capability
- x_inpgh_upmx_information_object
Core Object Types extending ServiceNow CSDM
The following object types (tables) extend the core ServiceNow CSDM. As visualized in the architecture, the cmdb_ci base class is extended with the superclass Portfolio Element x_inpgh_upmx_portfolio_element, where all other core tables are extended from.
🚀 INNOVATIVE MODELING APPROACH
The benefit of the modeling approach ins-pi has chosen for UPM-X is the quick extensibility and central management of all fields on the Portfolio Element superclass.
Any additional fields added to the Portfolio Element will be instantly available and inherited by the sub-tables.
| Object Type | Table Name | Description |
|---|---|---|
| Portfolio Element | x_inpgh_upmx_portfolio_element | Portfolio Element is the super-class containing all sub-classes e. g., Value Chain in UPM-X. |
| Actor | x_inpgh_upmx_actor | Actors are abstract representations of people, teams, departments, roles, and groups. |
| 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. |
| Business Event | x_inpgh_upmx_business_event | A business event is a Thread or opportunity to the business requiring a significant change in how the organization operates. |
| 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. |
| 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. |
| 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 fulfill value desired by a customer. |
| Channel | x_inpgh_upmx_channel | Conduit for delivering goods, services, or information. |
| 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 aligned to implementation structuring. |
| Conceptional Data Object | x_inpgh_upmx_conceptional_data_object | A Conceptional Data Object specifies the high-level information flow and data lineage on a conceptional level. |
| Control | x_inpgh_upmx_control | Controls are engineering mechanisms that use continuous monitoring of operational variables e.g. pressure, temperature, etc., to reach product output specifications and objectives. |
| 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. |
| Domain | x_inpgh_upmx_domain | A Domain name is the address where users can access the website or application via a browser. |
| 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.” |
| 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 14 Pro. |
| 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. |
| Journey | x_inpgh_upmx_journey | A Journey represents a series of touch points and interactions with organizations or stakeholders, providing/consuming services and products. |
| 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 journey. |
| 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. |
| 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 gives an early warning to identify a potential event that may harm the continuity of the activity/project. |
| 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 conceptual/logical level. |
| 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. |
| 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. |
| 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, contracts, or instruments for money or barter. |
| Measure | x_inpgh_upmx_measure | A Measure is used to specify the measurement type to track key performance indicators and metrics, e.g., percentage, number, currency, activity, process, etc., usually on an ongoing basis, to determine success or alignment with objectives and goals. |
| 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 essential 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. |
| Microservice | x_inpgh_upmx_microservice | A Microservice is an application component communicating with other Microservices across common interfaces, e.g., APIs and REST. |
| Mission | x_inpgh_upmx_mission | A Mission is a written declaration of an organization’s core purpose and focuses that usually remains unchanged over time. Appropriately crafted mission statements serve as filters to separate what is essential from what is not, clearly state which markets will be served and how, and communicate a sense of intended direction to the entire organization. |
| Mobile Application | x_inpgh_upmx_mobile_application | A Mobile Application is an end-user application consumed on a mobile device. |
| Objective | x_inpgh_upmx_objective | An Objective is a specific target that helps to measure goal achievement and is typically set out in numbers. Objectives need to be Specific, Measurable, Attainable, Relevant, and Time-limited (SMART). E.g., Reduce OPEX by 20% by the end of 2018. |
| 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 stage. |
| 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. |
| 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 for the Business and IT. |
| 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 technically 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. |
| Policy | x_inpgh_upmx_policy | A statement of direction for an organization. A rule that prohibits or prescribes specific actions for given conditions or defined criteria for certain decisions. A policy often derives from legal, contractual, or regulatory requirements, as well as internal organization governance practices. |
| 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. |
| 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. |
| Process | x_inpgh_upmx_process | A Process is an activity or set of activities that provide a specific business capability. Typically, a process produces a specific service or product. |
| Process Activity | x_inpgh_upmx_process_activity | A Process Activity is also referred to as sub-processes with execution on the divisional, business line, local or regional levels. |
| Process Category | x_inpgh_upmx_process_category | Process Categories are used by industry frameworks to classify processes by area. Top-level Business Capabilities can replace Process Categories. |
| Process Group | x_inpgh_upmx_process_group | Process Groups are groupings of related processes that are applicable across operational hierarchies and silos. Top-level Business Capabilities can replace Process Groups. |
| Process Operations | x_inpgh_upmx_process_operations | Process Operations are technical calls to technology components or non-technical work performed manually by a person. |
| Process Task | x_inpgh_upmx_process_task | Process Tasks are technical tasks executed on the application level or non-technical tasks performed by people. |
| Process Workflow | x_inpgh_upmx_process_workflow | A Process Workflow consists of multiple Process Tasks in order to implement a Process Activity. |
| Product Line | x_inpgh_upmx_product_line | An organizing structure used for product management and marketing of a group of related products. |
| Program | x_inpgh_upmx_program | A Program is a collection of Projects. |
| Project | x_inpgh_upmx_project | Projects are planned sets of interrelated tasks to be executed over a fixed period and within certain costs and other limitations. It is a major undertaking, especially one involving considerable money, personnel, and equipment. |
| Project Task | x_inpgh_upmx_task | A Task is a project-related activity that needs to be accomplished within a defined period or by a deadline. |
| Risk | x_inpgh_upmx_risk | A Risk highlights competitive, economic, operational, legal, compliance, strategic, program, project, quality, process, technology, etc., risks which cause the business to fail. |
| Social Media | x_inpgh_upmx_social_media | Social Media is an internet-based technology facilitating the sharing of ideas, thoughts, and information through the building of virtual networks and communities. |
| 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. |
| 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. |
| Stakeholder | x_inpgh_upmx_stakeholder | An internal or external individual or organization with a vested interest in achieving value through a particular outcome. |
| 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. |
| 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. |
| Touchpoint | x_inpgh_upmx_touchpoint | The means via which a stakeholder or customer experiences their participation in a customer journey stage. |
| Value Chain | x_inpgh_upmx_value_chain | A Value Chain is the whole series of activities that create and build value at every step. |
| 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 stages in the value delivery process. |
| Value Proposition | x_inpgh_upmx_value_proposition | The potential benefits, tangible or intangible, exchanged between provider and consumer. Typically the exchange of money for goods or services, delivering value to a customer segment. A result of a value stream delivered to a stakeholder. |
| 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 being 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. |
| Value Stream Stage | x_inpgh_value_stream_stage | A defined step within a value stream that delivers a value item, which accrues toward the overall value proposition desired by the value stream stakeholder. |
| 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. |
| Website | x_inpgh_upmx_website | An internal or external website used by the organizational users. |
Feature Tables
Feature tables are used to define and store feature-related data in UPM-X.
| Table Label | Table Name | Description |
|---|---|---|
| Portfolio Feature | x_inpgh_upmx_portfolio_feature | Superior table for all portfolio features, e.g., cost, KPI, etc. Do not use it for reporting! |
| Cost | x_inpgh_upmx_pf_cost | UPM-X table containing Cost information. |
| Cost Breakdown | x_inpgh_upmx_pf_cost_breakdown | UPM-X table containing Cost Breakdown information over time. |
| Data Definition Scope | x_inpgh_upmx_data_definition_scope | UPM-X Data Quality Scope definition |
| Data Quality | x_inpgh_upmx_data_quality | UPM-X Data Quality – Records of Completeness and Correctness for all DQ Scopes |
| Scoped Fields | x_inpgh_upmx_data_definition | UPM-X Data Quality |
| Global Settings | x_inpgh_upmx_global_settings | Table to store UPM-X Global Settings. |
| Glossary | x_inpgh_upmx_glossary | A glossary of terms & definitions. |
| Hosting | x_inpgh_upmx_hosting | UPM-X table to join hosting-related information with Portfolio Elements. |
| KPI | x_inpgh_upmx_pf_kpi | UPM-X table containing KPI definitions. |
| KPI Breakdown | x_inpgh_upmx_pf_kpi_breakdown | UPM-X table containing KPI information over time. |
| Lifecycle | x_inpgh_upmx_pf_lifecycle | UPM-X table containing Lifecycle definitions. |
| Lifecycle Breakdown | x_inpgh_upmx_pf_lifecycle_breakdown | UPM-X table containing Lifecycle information. |
| Realtime Indicators | x_inpgh_upmx_pf_indicators | UPM-X table containing Indicator definitions. |
| Indicator Breakdown | x_inpgh_upmx_pf_indicator_breakdown | UPM-X table containing Indicator Breakdown definitions. |
| Recommendation | x_inpgh_upmx_pf_recommendation | Defines what needs to 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. |
| Risk & Compliance | x_inpgh_upmx_risk_compliance | UPM-X table to join risk & compliance-related information with Portfolio Elements. |
| Rollup Setting | x_inpgh_upmx_calculation_rollup_rel | Table containing rollup settings for UPM-X. |
| Scenario | x_inpgh_upmx_pf_scenario | UPM-X table containing Scenario information. |
| Stakeholder | x_inpgh_upmx_pf_stakeholder | UPM-X table containing Stakeholder information. |
| Suggested Relationship | x_inpgh_upmx_rel_type_suggest | Used to store for UPM-X Relationship Picker. |
| Suggested Relationship Field | x_inpgh_upmx_rel_type_suggest_field | Used by Relationship Picker to store settings for the suggested relationships for black/whitelisting and relationship fields. |
| Suggested Relationship Group | x_inpgh_upmx_rel_type_suggest_group | Used to store for UPM-X Relationship Picker. |
| Usage | x_inpgh_upmx_usage | The Usage specifies an element used within a specific company, or department, or location. |
Reporting table
Reporting tables provide a quick way for impact analysis and visualizing complex data interdependencies.
| Table Label | Table Name | Description |
|---|---|---|
| Application Risk caused by SW Products | x_inpgh_upmx_dbv_app2swp | Reporting Table: Application Risk caused by SW Products |
| 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 | UPM-X table to store Dashboard filter settings for UPM-X reports. |
| 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. |
| Portfolio Element to Stakeholder | x_inpgh_upmx_portfolio_element_to_stakeholder_view | Database View joining Portfolio Elements and Stakeholders table. |
| Portfolio Element to Project | x_inpgh_upmx_dbv_pe2project | Database view for Portfolio Elements2Projects. |
| 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 | UPM-X table required for roadmap visualization. |
| Roadmap Request | x_inpgh_upmx_roadmap_request | UPM-X table required for roadmap visualization. |
Updated over 1 year ago
What’s Next