--- sourceDocument: Yokohama Enterprise Architecture (formerly Application Portfolio Management) sourceDocumentLink: https://www.servicenow.com/docs/r/yokohama/application-portfolio-management Release : - yokohama ft:locale : - en-US ft:publication_title : - Yokohama Enterprise Architecture (formerly Application Portfolio Management) ft:clusterId : - appportman bundleId : - appportman workflow : - Technology --- # Technology Portfolio Management # Technology Portfolio Management {#ariaid-title1} * Release version: Yokohama * * Updated January 30, 2025 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) 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 Technology Portfolio Management (TPM) helps ServiceNow customers actively manage the lifecycle of the underlying technologies (software models) that support business applications. These technologies include operating systems, database systems, middleware, and development tools, each with distinct versions and lifecycle stages. TPM enables tracking of software versions, vendor support dates, and internal lifecycle phases to mitigate risks associated with unsupported or outdated technology. Show full answer Show less Starting with the Xanadu release, the legacy Technology Lifecycle Management module has moved to the Enterprise Architecture Workspace, reflecting enhanced lifecycle management capabilities. ## Key Features * **Lifecycle Tracking:** TPM tracks both internal lifecycle phases (e.g., Early Adopter, Mainstream, Declining, Retired) and vendor lifecycle stages (e.g., Pre-release, General Availability, End of Life, Obsolete) for software products. * **Technology Inventory:** Create and maintain an inventory of all technology models used in the enterprise, supporting risk assessments and upgrade or retirement planning. * **Integration with Application Portfolio:** Business applications link to application services, which run on technology models, allowing lifecycle management at the application service level. * **Integration with Service Mapping:** Use the Mapped Application Service \[cmdbciservicediscovered\] table to associate application instances with business applications. Note that the older apmappinstance table is deprecated and requires migration. * **Dependency on Software Asset Management (SAM):** TPM requires either the SAM Foundation or SAM Professional plugin for full functionality. SAM Premium plugin enhances TPM by enabling product classification views in the TPM timeline. * **Manual or Imported Data:** TPM users without SAM can still manage software models manually or via import into the Software Product Model table. ## Practical Use and Outcomes * **Risk Mitigation:** By tracking technology lifecycle stages, organizations can avoid risks related to unsupported software and plan timely upgrades or retirements. * **Upgrade and Retirement Planning:** TPM's timeline views provide clear visibility into lifecycle dates, enabling informed decisions to initiate demands or projects for technology upgrades or retirements. * **Enhanced Reporting:** With SAM Premium, customers can analyze technology portfolios by product classification, improving governance and portfolio management insights. * **Data Consistency:** Migration guidance ensures alignment of application service data with current ServiceNow tables, supporting smooth upgrades and integration. ## Next Steps for ServiceNow Customers * Ensure installation of SAM Foundation or SAM Professional plugins to enable full TPM capabilities. * If upgrading from older releases, plan data migration from deprecated application instance tables to the Mapped Application Service table. * Populate software product lifecycle data in the Software Product Lifecycle and Software Product Model tables to leverage TPM timeline views. * Use TPM to create inventories, track lifecycle stages, assess risks, and plan lifecycle-driven actions such as upgrades and retirements. * Consider subscribing to SAM Premium for enhanced product classification and reporting features within TPM. 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 [Managing the Technology Lifecycle Management (TLM) in Enterprise Architecture Workspace](https://www.servicenow.com/docs/udaB7kbGeAWr5r4c9CLyeg "Technology Lifecycle Management helps Enterprise Architects to manage technology life-cycle risks and technology life-cycle exceptions. Enterprise Architects can evaluate all their business applications and application services by accessing the discovered technologies and auditing information in the 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. {#technology-portfolio-management__ul_fvt_dx2_jbb} ## Internal and external lifecycle stages of the software product {#technology-portfolio-management__section_s33_lx2_jbb} 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](https://www.servicenow.com/docs/access?context=record-terms-software-licenses&version=yokohama&pubname=yokohama-it-asset-management&ft:locale=en-US) 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 {#technology-portfolio-management__section_q5r_shm_jbb} 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 ## TPM depends on Software Asset Management (SAM) to retrieve the technology information of the software product {#technology-portfolio-management__section_yrc_fkm_jbb} 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](https://www.servicenow.com/docs/access?context=c_SAMMigrationSAMF&version=yokohama&pubname=yokohama-it-service-management&ft:locale=en-US) 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. Figure 2. Connecting software product life cycles to business application 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. Figure 3. TPM timeline showing By Product Classification view 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. **Related concepts** * [Technology risk calculation](https://www.servicenow.com/docs/h~g0g6spo3loYXlc8mSQjQ "Assess the technology risks of your business applications by calculating their risks at the software product (considering the model and full version) level and then at the business application level.") **Related tasks** * [View technology risks in timeline](https://www.servicenow.com/docs/1r4cpRR86v~HaPtyi4x7yA "View the internal and external life-cycle phases of all technologies or the product models that are used in your organization in the Technology Portfolio Management timeline. You can identify the stages at which the technology is, in terms of the risk factor by their color code.") * [Relate a business application to an application service](https://www.servicenow.com/docs/Ybs5V0FnSjWrUBASpaev3Q "Business applications can have multiple instances. Application instances are nothing but application services. Relate business applications to instances by relating business applications to application services. Business application and application service are two different configuration items which must be related through a CI relationship.") * [Associate an application service to hardware model](https://www.servicenow.com/docs/7VmbTa8ckJVGB8r0Y8HmEg "Track your equipment assets such as computers and servers using hardware models.") * [Associate an application service to a software model](https://www.servicenow.com/docs/3iarQpxsYoRt00_sLJF3zA "Business applications have multiple instances such as development, QA, and production. Instances are nothing but application services. Application services must be associated with software models (to the respective full versions) to know the risk of the application service.") * [Create a risk parameter](https://www.servicenow.com/docs/rH95jmwAtdAi7kmqIEgStg "The risk on a software model is calculated based on four preconfigured parameters such as external aging risk, internal aging risk, external stage risk, and internal stage risk.") * [Run scheduled job to generate risk values](https://www.servicenow.com/docs/l_EloaUKoOqqqegAxeNIlg "The risks on the product model and business application is time dependent. Based on the external and internal lifecycles the risk changes every day, hence the risk must be calculated daily. A scheduled job is created that runs daily and calculates the risks of the software model and the business application.")