Provides the overview of the UPM-X application architecture and metamodel documentation.
Architecture
UPM-X is 100% natively running in ServiceNow. It requires no integration and ongoing customization to use the application. It requires the minimum ServiceNow platform installation and extends the CMDB CI table with the Portfolio Element super class table.
The benefit of this innovative modeling approach is, that all fields and portfolio features are inherited from the superior table.
The ServiceNow admin can adapt and configure the architecture like any other ServiceNow application.
Metamodel
UPM-X’s metamodel is based on ServiceNow’s out-of-the-box Common Services Data Model enhancing 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
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.
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, reporting, and supporting tables:
Core Object Types
| Table | Label | Description |
| x_inpgh_upmx_portfolio_element | Portfolio Element | Portfolio Element is the super-class containing all sub-classes e. g. Business Application in UPM-X. |
| x_inpgh_upmx_actor | Actor | Actors are abstract representations of people, teams, departments, roles and groups. |
| x_inpgh_upmx_building_block | 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. |
| cmdb_ci_business_app | Business Application | 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. |
| cmdb_ci_business_capability | Business Capability | A Business Capability describes what an organization requires executing its business model or fulfill its mission. Think of Business Capabilities as organizational level skills imbedded in people, process, and/or technology. |
| x_inpgh_upmx_business_process | Business Process UPM-X | Legacy table. Do not use! A Business Process is an activity or set of activities that provides a specific business capability. Typically, a process produce a specific service or product. |
| x_inpgh_upmx_business_product | 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. |
| x_inpgh_upmx_channel | Channel | Conduit for delivering goods, services, or information. |
| x_inpgh_upmx_chatbot | Chatbot | A Chatbot is a computer program designed to simulate conversation with human users, especially over the internet. |
| x_inpgh_upmx_component | Component | A Component encapsulation of technology infrastructure or application functionality that is aligned to implementation structuring. |
| x_inpgh_upmx_conceptional_data_object | Conceptional Data Object | A Conceptional Data Object specifies the high-level information flow and data lineage on a conceptional level. |
| x_inpgh_upmx_control | Control | Controls are engineering mechanisms that uses continuous monitoring of operational variables e.g. pressure, temperature etc. to reach product output specifications and objectives. |
| x_inpgh_upmx_data_store | Data Store | A Data Store is a logical representation of a physical database or file which contains data used by applications or software. |
| x_inpgh_upmx_domain | Domain | A Domain name is the address where users can access the website or application via browser. |
| x_inpgh_upmx_driver | 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. |
| x_inpgh_upmx_glossary | Glossary | A glossary of terms & definitions. |
| x_inpgh_upmx_goal | 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.” |
| x_inpgh_upmx_hardware_product | 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. |
| cmdb_ci_information_object | Information Object | An Information Object is a logical, or conceptual representation of a real-world data object e.g. Person. |
| x_inpgh_upmx_information_object_attribute | Information Object Attribute | An Information Object Attribute is a logical, or conceptual representation of a real-world data object e.g. Name referring to an Information Object. |
| x_inpgh_upmx_journey | Journey | A Journey represents a series of touch points and interactions with organizations or stakeholders, providing/consuming services and products. |
| x_inpgh_upmx_kpi | 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. |
| x_inpgh_upmx_kri | 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. |
| x_inpgh_upmx_logical_application | Logical Application | A Logical Application is a higher level aggregation of a Business Application to respond to Business requirements on a conceptional/logical level. |
| x_inpgh_upmx_logical_data_object | Logical Data Object | A Logical Data Object specifies the high-level information flow and data lineage on a logical level. |
| x_inpgh_upmx_logical_interface | 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. |
| x_inpgh_upmx_market | 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. |
| x_inpgh_upmx_measure | 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. |
| x_inpgh_upmx_metric | 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. |
| x_inpgh_upmx_microservice | Microservice | A Microservice is an application component communicating with other Microservices across common interfaces e.g. APIs, REST. |
| x_inpgh_upmx_mission | 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. |
| x_inpgh_upmx_mobile_application | Mobile Application | A Mobile Application is an end-user application consumed on a mobile device. |
| x_inpgh_upmx_objective | 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. |
| x_inpgh_upmx_organizational_units | Organizational Unit | An organizational unit is one of several functions within a company typically structured as a multi-level hierarchy. |
| x_inpgh_upmx_pattern | 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. |
| x_inpgh_upmx_physical_data_object | Physical Data Object | A Physical Data Object specifies the high-level information flow and data lineage on a physical level. |
| x_inpgh_upmx_physical_interface | 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. |
| x_inpgh_upmx_ppi | 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. |
| x_inpgh_upmx_principle | 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. |
| x_inpgh_upmx_process | 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. |
| x_inpgh_upmx_process_activity | Process Activity | A Process Activity is also referred to as sub-processes with execution on divisional, business line, local or regional levels. |
| x_inpgh_upmx_process_category | Process Category | Process Categories are used by industry frameworks to classify processes by area. Process Categories can be replaced by top-level Business Capabilities. |
| x_inpgh_upmx_process_category | Process Category | Portfolio Element is the super-class containing all sub-classes e. g. Business Application in UPM-X. |
| x_inpgh_upmx_process_group | 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. |
| x_inpgh_upmx_process_operations | Process Operations | Process Operations are technical calls to technology components, or non-technical work performed manually by a person. |
| x_inpgh_upmx_process_task | Process Task | Process Tasks are technical tasks executed on application level, or non-technical tasks performed by people. |
| x_inpgh_upmx_process_workflow | Process Workflow | A Process Workflow consists of multiple Process Tasks in order to implement a Process Activity. |
| x_inpgh_upmx_program | Program | A Program is a collection of Projects. |
| x_inpgh_upmx_project | 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. |
| x_inpgh_upmx_task | Project Task | A Task is a project related activity that needs to be accomplished within a defined period of time or by a deadline. |
| x_inpgh_upmx_risk | Risk | A Risk highlights competitive, economic, operational, legal, compliance, strategic, program, project, quality, process, technology etc. risks, which causes business to fail. |
| x_inpgh_upmx_social_media | Social Media | Social Media is an internet-based technology facilitating the sharing of ideas, thoughts, and information through building of virtual networks and communities. |
| x_inpgh_upmx_software_product | 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. |
| x_inpgh_upmx_solution_use_case | Solution Use Case | A Solution Use Case consists of Process Operations and a set of technologies to implement Process Tasks. |
| x_inpgh_upmx_strategy | Strategy | A Strategy describes how the company will achieve its goals and objectives by deploying its scarce resources to gain a sustainable competitive advantage. |
| x_inpgh_upmx_technical_capability | 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. |
| x_inpgh_upmx_usage | Usage | The Usage specifies an element use within a specific company, or department, or location. |
| x_inpgh_upmx_value_chain | Value Chain | A Value Chain is the whole series of activities that create and build value at every step. |
| 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. |
| x_inpgh_upmx_vision | 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. |
| x_inpgh_upmx_website | 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 | Description |
| x_inpgh_upmx_pf_recommendation | Recommendation | Defines, what needs to be happen to mitigate risk, reduce cost and improve efficiency. |
| x_inpgh_upmx_pf_lifecycle_breakdown | Lifecycle Breakdown | UPM-X table containing Lifecycle information. |
| x_inpgh_upmx_pf_lifecycle | Lifecycle | UPM-X table containing Lifecycle definitions. |
| x_inpgh_upmx_pf_kpi_breakdown | KPI Breakdown | UPM-X table containing KPI information over time. |
| x_inpgh_upmx_pf_kpi | KPI | UPM-X table containing KPI definitions. |
| x_inpgh_upmx_pf_indicator_breakdown | Indicator Breakdown | UPM-X table containing Indicator Breakdown definitions. |
| x_inpgh_upmx_pf_indicators | Realtime Indicators | UPM-X table containing Indicator definitions. |
| x_inpgh_upmx_pf_cost_breakdown | Cost Breakdown | UPM-X table containing Cost Breakdown information over time. |
| x_inpgh_upmx_pf_cost | Cost | UPM-X table containing Cost information. |
| x_inpgh_upmx_hosting | Hosting | UPM-X table to join hosting related information with Portfolio Elements. |
| x_inpgh_upmx_calculation_rollup_rel | Rollup Setting | Table containing rollup settings for UPM-X. |
| x_inpgh_upmx_data_definition | Scoped Fields | UPM-X Data Quality |
| x_inpgh_upmx_global_settings | Global Settings | Table to store UPM-X Global Settings. |
| x_inpgh_upmx_data_quality | Data Quality | UPM-X Data Quality |
| x_inpgh_upmx_data_definition_scope | Data Definition Scope | UPM-X Data Quality |
| x_inpgh_upmx_risk_compliance | Risk & Compliance | UPM-X table to join risk & compliance related information with Portfolio Elements. |
| x_inpgh_upmx_portfolio_feature | Portfolio Feature | Superior table for all portfolio features e.g. cost, KPI etc. Do not use for reporting! |
| x_inpgh_upmx_pf_stakeholder | Stakeholder | UPM-X table containing Stakeholder information. |
| x_inpgh_upmx_pf_scenario | Scenario | UPM-X table containing Scenario information. |
| x_inpgh_upmx_rel_type_suggest_group | Suggested Relationship Group | Used to store for UPM-X Relationship Picker. |
| x_inpgh_upmx_rel_type_suggest | Suggested Relationship | Used to store for UPM-X Relationship Picker. |
| x_inpgh_upmx_pf_reference_model | Reference Model | A reference model is an abstract framework or domain-specific ontology consisting of an interlinked set of clearly defined concepts. |
Reporting table
Reporting tables provide a quick way for impact analysis and visualizing complex data interdependencies.
| Table | Label | Description |
| x_inpgh_upmx_cmdb_cap2cmdb_app2swp | Business Capability > Business Application > Software Product | Reporting Table: Business Capability > Business Application > Software Product |
| x_inpgh_upmx_dbv_scenario_reporting | Scenario Reporting | Reporting table for Scenarios. |
| x_inpgh_upmx_dbv_pe2project | Portfolio Element to Project | Database view for Portfolio Elements2Projects. |
| x_inpgh_upmx_dbv_app2swp | Application Risk caused by SW Products | Reporting Table: Application Risk caused by SW Products |
| x_inpgh_upmx_report_proc2cmdb_app2sftprd | Process > Business Application > Software Product | Reporting Table: Process > Business Application > Software Product |
| x_inpgh_upmx_report_proc2app2sftprd | Business Process UPM-X > App UPM-X > Software Product | Legacy table. Do not use! |
| x_inpgh_upmx_report_cmdb_app2swp | Business Application > Software Product | Reporting Table: Business Application > Software Product |
| x_inpgh_upmx_report_cap2app2swp | Business Capability UPM-X > App UPM-X > Software Product | Legacy table. Do not use! |
| x_inpgh_upmx_report_cap2app2dbs | Business Capability UPM-X > App UPM-X > Database | Legacy table. Do not use! |
| x_inpgh_upmx_report_app2swp | Business Application UPM-X > Software Product | Legacy table. Do not use! |
| x_inpgh_upmx_report_app2infobj2infobjattr | Business Application UPM-X > Information Object UPM-X > Info Object Attribute | Legacy table. Do not use! |
Supporting Tables
Supporting tables are required by UPM-X for additional features.
| Table | Label | Description |
| x_inpgh_upmx_m2m_stakeholders_portfolio_el | Portfolio Element to Stakeholder | The many-to-many Relationship between Portfolio Elements and Stakeholder. |
| x_inpgh_upmx_m2m_scenarios_portfolio_el | Portfolio Element to Scenario | The many-to-many Relationship between Portfolio Elements and Scenario. |
| x_inpgh_upmx_m2m_pe2reference_model | Portfolio Element to Reference Model | The many-to-many Relationship between Portfolio Elements and Reference Model. |
| x_inpgh_upmx_m2m_data_definit_data_definit | UPM-X m2m Data Definit Data Definit | UPM-X Data Quality |
| x_inpgh_upmx_pe_productive | Portfolio Element Productive | |
| x_inpgh_upmx_pe_initialization | Portfolio Element Initializations | |
| x_inpgh_upmx_pe_expiration | Portfolio Element Expiration | |
| x_inpgh_upmx_custom_hierarchy_definition | UPM-X Portal Custom Hierarchy Definition | Table required for UPM-X Portal. |
| x_inpgh_upmx_custom_hierarchy | UPM-X Portal Custom Hierarchy | Table required for UPM-X Portal. |
| x_inpgh_upmx_dashboard_filter_store | Dashboard Filter Store for UPMX Reports | |
| x_inpgh_upmx_roadmap_request | Roadmap Request | |
| x_inpgh_upmx_roadmap_elements | Roadmap Elements | |
| x_inpgh_upmx_report_request | Report Request | |
| x_inpgh_upmx_report_elements | Report Elements | |
| x_inpgh_upmx_portfolio_element_to_stakeholder_view | Portfolio Element to Stakeholder | Database View joining Portfolio Elements and Stakeholders table. |
| x_inpgh_upmx_portfolio_definition | UPM-X Portal Definitions | Table required for UPM-X Portal. |
| x_inpgh_upmx_portfolio_attributes | UPM-X Portal Portfolio Attributes | Table required for UPM-X Portal. |
| x_inpgh_upmx_rating_data | Rating Data |