Enterprise Architecture (formerly Application Portfolio Management) use case
Summarize
Summary of Enterprise Architecture (formerly Application Portfolio Management) use case
Enterprise Architecture (EA), previously known as Application Portfolio Management (APM), enables ServiceNow customers to define a unified, version-agnostic representation of business applications encompassing all instances, technologies, and data. This is essential for effective planning, governance, and reporting activities such as funding decisions, roadmapping, risk analysis, and technology transformations. Starting with the Xanadu release, most EA capabilities are accessed via the Enterprise Architecture Workspace, which centralizes features like data certification, application assessments, and total cost of ownership (TCO) management.
Show less
Key Features
- Application Life Cycle Management: Register, update, and decommission business applications using the CMDB aligned with the Common Service Data Model (CSDM) framework. Application services are managed as logical configuration items with defined life cycle states.
- Business Application Portfolio Assessments: Evaluate applications based on metrics and impact analysis to support rationalization and strategic planning.
- Roadmap Planning: Facilitate creation of new ideas, demands, and projects to align business applications with organizational goals.
- Data Certification Process: Ensure data quality and governance for better decision-making.
- Total Cost of Ownership (TCO) Calculations: Use Financial Management capabilities to calculate and manage application costs.
- Management of Related Entities: Handle information objects and business capabilities via dedicated CMDB tables.
Key Outcomes
By adopting EA with CSDM, customers gain a consistent and structured approach to modeling business applications and their related assets. This supports automated calculation of technology risk scores, cost analysis, and comprehensive reporting, enabling better governance and informed decision-making.
Technology Portfolio Management (TPM) Use Case
Overview
TPM provides insight into risks associated with software and hardware products reaching their end-of-life (EOL). Leveraging CSDM data, TPM calculates risk scores at various levels—from individual product models to application services and overall business applications—helping customers proactively manage technology lifecycle risks.
Key Features
- Consistent Data Structure: CSDM framework supports lifecycle management and risk analysis across IT Operations Management (ITOM), Service Management, and IT Asset Management (ITAM).
- Risk Calculation Hierarchy: Risks are aggregated from hardware and software product models through application services up to the business application portfolio level.
- Flexible Data Input: Lifecycle data for products can be entered manually, imported, or sourced via Software Asset Management or Hardware Asset Management licenses.
- Optional SDLC Component Configuration: Enables detailed risk mapping, though direct connections between business applications and application services are supported without it.
Key Outcomes
TPM helps customers understand and mitigate risks from obsolete or unsupported technologies by providing a clear risk assessment framework based on product lifecycle stages. This enables proactive technology refresh planning and reduces operational risks.
Enterprise Architecture lets you define a single, version-agnostic entity that represents all instances, technologies, and data used for planning and reporting.
Starting with the Xanadu release, most Enterprise Architecture (formerly Application Portfolio Management) capabilities are available through the Enterprise Architecture Workspace.
Features such as data certification, application assessments, and total cost of ownership (TCO) are now accessed and managed from the Enterprise Architecture Workspace, not from the legacy APM pages. To learn more about Enterprise Architecture Workspace, see Enterprise Architecture Workspace.
Enterprise Architecture use case
You can use a business application for planning and governance activities, such as funding, road mapping, and risk reporting. Rationalizing business applications is a continuous process, and is critically important to reducing costs and planning technology transformations. Rationalizing business applications is also critical for completing mergers, divestitures, or other broad-impact business-led changes.
Key features of the Enterprise Architecture use case
The CMDB, when used by the CSDM framework, provides value to Enterprise Architecture in the following ways:
- Application life cycle management. This includes:
- Registering a new business application (included in the base system).
- Updating a business application
- Decommissioning a business application, including all the related application services and infrastructure. Because application services are logical in nature, they should use the Logical life cycle states. Application services follow the same life cycle guidance as any other logical CI.
- Business application portfolio assessments based on metrics or related impacts.
- Roadmap planning and creating new ideas, demands and projects.
- Data certification process
- Total cost of ownership (TCO) calculations (using the Financial Management module)
- Manage the following related entities:
- Information objects table [cmdb_ci_information_object]
- Business capabilities table [cmdb_ci_business_capability]
Results of the Enterprise Architecture use case
With this use case, CSDM provides Enterprise Architecture a consistent way to model business applications and relate critical data. The use case ensures that the application services (instances) are defined as required for automating the technology risk scores, costs, and other metrics used for analysis.
TPM use case
TPM gives you a better understanding of the risks associated with using software and hardware that is at the end-of-life (EOL) date. You can use the details provided by the CSDM framework to determine the risk of using software and hardware that is at EOL. Each product life cycle EOL date is calculated, then combined following the CSDM framework to provide a score at the Business Application level.
Results of the TPM use case
The CSDM framework provides a consistent data structure. This consistent data structure makes it easier for you to manage the life cycles of your technology and analyze the combined technology risks.
Because of the way the CSDM framework is structured, you can leverage many products from ITOM, Service Management (Service Portfolio Management), and IT Application Management (ITAM).
The risks of using EOL technologies are calculated based on the life cycle of each software and hardware product model identified in the CMDB, and matched with a software and hardware product model.
You can enter the life-cycle data manually, import it from an external source, or use the data provided with your Software Asset Management Professional or Hardware Asset Management license.
- Hardware and software product model — Displays the current life-cycle phases, sources, and indicates the specific models at-risk
- Application Service level — Displays the combined risk status of all underlying hardware and software product models used in the Application Service (Instance).
- SDLC Component — Displays the SDLC components along with the associated application services and business applications
- Business application level — Combines all the underlying Application Service (Instances) to determine the overall risk rating at a portfolio level.
- The business applications used in your organization are all linked to one or more application services. Each of the application services run on one or more technologies or software models.
The name of the Application Service Software model table is [sn_apm_tpm_service_software_model].
- The software model has a sequence of life-cycle stages. The life-cycle stages range from the installation date to the retirement date.
Some business organizations set an internal date based on the life-cycle phase of the software models. These software model phases can be Early Adopter, Mainstream, Declining use, and Retired.
Similarly, the software vendors might also set a date for the software based on the vendor life-cycle phases, such as Pre-release, General Availability, End of Life, and Obsolete. Vendor support might vary depending on the phase of the technology. For example, when the software model reaches the Obsolete phase, the vendor might stop supporting the technology.
The Software Model Life cycle table is named [sam_sw_model_lifecycle].