Technology Portfolio Management - Legacy

  • Release version: Zurich
  • Updated July 31, 2025
  • 4 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Technology Portfolio Management - Legacy

    Technology Portfolio Management (TPM) - Legacy enables ServiceNow customers to actively monitor and manage the life cycles of underlying technologies (software models) supporting their business applications. These technologies include operating systems, databases, development tools, and middleware, each with defined life-cycle phases that impact vendor support and risk exposure. TPM helps track the versions, vendor support dates, and internal life-cycle guidance to mitigate risks associated with obsolete technologies and plan for timely upgrades or retirements.

    Show full answer Show less

    Starting with the Xanadu release, the legacy Technology Lifecycle Management module has moved to the Enterprise Architecture Workspace, reflecting an evolution in managing technology life cycles.

    Key Features

    • Technology Life-Cycle Tracking: Track both internal life-cycle phases (Early Adopter, Mainstream, Declining Use, Retired) and vendor life-cycle phases (Pre-release, General Availability, End of Life, Obsolete) to understand technology support status.
    • Technology Inventory Management: Maintain an inventory of all software models used across business applications to assess risks and support upgrade or retirement planning.
    • Integration with Application Portfolio Management: Link business applications to application services and their underlying technologies to ensure comprehensive portfolio visibility.
    • Integration with Service Mapping: Use the Mapped Application Service [cmdbciservicediscovered] table to relate business applications to application services, replacing the deprecated application instances table, with guidance provided for data migration during upgrades.
    • Dependency on Software Asset Management (SAM): TPM requires either SAM Foundation or SAM Professional plugins for full functionality, including retrieving technology information from software product models and enabling product classification views. Customers without SAM can still use TPM but with limited classification capabilities.
    • Risk Management Support: TPM supports technology risk calculation and visualization on a timeline, assisting in proactive risk mitigation.

    Practical Implications for ServiceNow Customers

    • By implementing TPM, customers can systematically track technology versions and support phases, reducing the risk of unsupported technologies disrupting business applications.
    • TPM facilitates informed decision-making on technology upgrades or retirements by providing clear timelines and risk assessments.
    • Upgrading customers should ensure data migration from deprecated tables to current standards (e.g., from apmappinstance to cmdbciservicediscovered) to maintain integration with Service Mapping.
    • Installation of SAM plugins is essential for leveraging full TPM capabilities, including technology classification and detailed product lifecycle data.
    • Customers can manually populate software product models if SAM is not installed, allowing baseline TPM usage.

    The underlying technologies of the business applications used in your business enterprise have a shelf life that must be actively managed and diligently monitored to track their versions and life cycle. Use the timeline view of the Technology Portfolio Management to track their dates, and then create a demand or a project to upgrade or retire them.

    Important:

    Starting with the Xanadu release, the legacy Technology Lifecycle Management module is moved to the Enterprise Architecture Workspace. To learn more, see Manage the Technology Lifecycle Management (TLM) in Enterprise Architecture Workspace.

    The technology of a business application is also known as a software model. A software model is a specific version or configuration of software.

    The software models used in your business applications can be operating systems, database management systems, development tools, and middleware, each of which has a life cycle. If these life-cycle stages are not tracked, there are risks where the vendor may not support them any longer and the business applications that run on these technologies are at stake.

    Creating an inventory of all technologies used in the enterprise helps to:

    • Track the versions of the software and manufacturer support dates for the software.
    • Set an internal life-cycle guidance for the software.
    • Assess the risks in using outdated software.
    • Plan to retire them just like the applications they support, at a definite date.
    • Support upgrade processes.

    Internal and external lifecycle stages of the software product

    The business applications used in your organization are all linked to one or more application services. Each of the application services runs on one or more technologies or software models.

    Note:
    In the context of Application Portfolio Management, an application instance is an application service.

    The software product (each model and full version) has a sequence of life cycle stages/phases from its installation to retirement. Internally, business organizations set a date based on the life-cycle phase of the software products. These phases can be Early Adopter, Mainstream, Declining use, and Retired.

    The vendor also sets a date for the software based on the vendor life-cycle phases such as Pre-release, General Availability, End of Life, and Obsolete. The support from the vendor may vary depending on the phase of the technology. When the software model reaches the stage of obsolescence, the vendor may stop supporting the technology.
    Note:
    The Publisher choice type of the Lifecycle type field in the Software Product Lifecycle form is the same as the External Lifecycle that is being used in Enterprise Architecture.

    As a software asset management user or a software model manager, you can add the software product life-cycle details to the software model for each full version. To use a TPM screen with data on the timeline, ensure that the software life-cycle data is populated in the software product life-cycle table. Similarly, ensure that the hardware life-cycle data is populated in the hardware model table after the technology model suggestion engine runs.

    Integration with Service Mapping to use Technology Portfolio Management

    Create application instances in the Mapped Application Service [cmdb_ci_service_discovered] table and relate business applications to corresponding application services.

    Enterprise Architecture no longer integrates with Service Mapping through the Instances tab. The application Instances tab has been removed and the apm_app_instance table has been deprecated, which is replaced by the Mapped Application Service [cmdb_ci_service_discovered] table. Any data existing in the application instances table must be migrated to the application service table. If you are upgrading to the Madrid release, then contact the ServiceNow personnel for migrating the data.

    Note:
    If you are using the Mapped Application Service [cmdb_ci_service_discovered] table for application instances, then you can proceed to upgrade from Kingston. However, if you are using the deprecated apm_app_instance table to store application instances, then migrate the data in the apm_app_instance table to the Mapped Application Service [cmdb_ci_service_discovered] table.
    Figure 1. Connecting software product life cycles to business application
    APM or TPM dependencies in mature ServiceNow implementation

    TPM depends on Software Asset Management (SAM) to retrieve the technology information of the software product

    Warning:
    TPM and TRM require installation of either SAM Foundation or SAM Professional. Before installing the SAM Foundation plugin, carefully review the Software Asset Management Foundation plugin migration documentation. Contact ServiceNow Support if you do not have either SAM Foundation or SAM Professional installed on your instance.

    You can use Technology Portfolio Management even if you do not have Software Asset Management (SAM) installed. A preconfigured Software Product Model table is available to all TPM users. You can create a list of all software models that your organization uses either manually or import from an existing database or source.

    Using TPM depends on SAM plugins. The dependency is as follows:

    With SAM Premium plugin

    To access the Product Classification [samp_sw_product] table, you need the Software Asset Management Premium plugin. Reference to samp_sw_product_classification is in samp_sw_product table. This content table is referenced in the Software Product Model [cmdb_software_product_model] table to retrieve the technology information. Subscribing to the SAM Premium plugin enables you to view the applications by Business Applications as well as by Product Classification in the TPM timeline.

    Without SAM plugin
    Product classification is not available without this plugin. Viewing by Product Classification is not available in the TPM timeline view. Software model information is retrieved from the SW Product Model [cmdb_software_product_model] table. Populate this table manually or export the content from an excel sheet.