Provides the overview of the UPM-X application architecture and metamodel documentation.
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.
NO OTHER SERVICENOW PLUGINS REQUIRED!
UPM-X does not require any other ServiceNow modules and plugins e.g. HR, PPM, APM, GRC etc. but can provide additional value with further modules activated in ServiceNow.
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.
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!
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 executing its business model or fulfill its mission. Think of Business Capabilities as organizational level skills imbedded in people, process, 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. Person.
⌛ LEGACY TABLES
The legacy tables are technically equivalent to the CSDM tables above and are still supported for existing customers.
Core Object Types extending ServiceNow CSDM
The following object types (tables) are extending the core ServiceNow CSDM. As visualized in the architecture, the cmdb_ci base class is extended with the super class 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 super class.
Any additional fields added on the Portfolio Element will be instantly available and inherited to the sub-tables.
Portfolio Element x_inpgh_upmx_portfolio_element
Portfolio Element is the super-class containing all sub-classes e. g. Value Chain in UPM-X.
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 the way 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.
Conduit for delivering goods, services, or information.
A Chatbot is a computer program designed to simulate conversation with human users, especially over the internet.
A Component encapsulation of technology infrastructure or application functionality that is 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.
Controls are engineering mechanisms that uses 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.
A Domain name is the address where users can access the website or application via browser.
A driver represents an external or internal influence that motivates an organization to define its goals and implement the changes necessary to achieve them.
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 X.
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.
A Journey represents a series of touch points and interactions with organizations or stakeholders, providing/consuming services and products.
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.
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.
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.
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.
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.
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.
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.
A Microservice is an application component communicating with other Microservices across common interfaces e.g. APIs, REST.
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.
Mobile Application x_inpgh_upmx_mobile_application
A Mobile Application is an end-user application consumed on a mobile device.
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.
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.
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.
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.
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.
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.
A Process is an activity or set of activities that provides a specific business capability. Typically, a process produce 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 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. Process Categories can be replaced by top-level Business Capabilities.
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.
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 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.
A Program is a collection of Projects.
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.
A Risk highlights competitive, economic, operational, legal, compliance, strategic, program, project, quality, process, technology etc. risks, which causes 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 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.
A Strategy describes how the company will achieve its goals and objectives by deploying its scarce resources to gain a sustainable competitive advantage.
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.
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.
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 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.
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.
An internal or external website used by the organizational users.
Feature tables are used to define and store feature related data in UPM-X.
Portfolio Feature x_inpgh_upmx_portfolio_feature
Superior table for all portfolio features e.g. cost, KPI etc. Do not use for reporting!
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
Data Quality x_inpgh_upmx_data_quality
UPM-X Data Quality
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.
A glossary of terms & definitions.
UPM-X table to join hosting related information with Portfolio Elements.
UPM-X table containing KPI definitions.
KPI Breakdown x_inpgh_upmx_pf_kpi_breakdown
UPM-X table containing KPI information over time.
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.
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.
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.
UPM-X table containing Scenario information.
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/white listing and relationship fields.
Suggested Relationship Group x_inpgh_upmx_rel_type_suggest_group
Used to store for UPM-X Relationship Picker.
The Usage specifies an element use within a specific company, or department, or location.
Reporting tables provide a quick way for impact analysis and visualizing complex data interdependencies.
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.