---
sourceDocument: Brazil Enterprise Architecture
sourceDocumentLink: https://www.servicenow.com/docs/r/application-portfolio-management

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Enterprise Architecture

ft:clusterId :

    - appportman

bundleId :

    - appportman

workflow :

    - Technology


---

# Technology Reference Model in Enterprise Architecture Workspace

# Technology Reference Model in Enterprise Architecture Workspace {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read  
The Technology Reference Model (TRM) feature in Enterprise Architecture Workspace helps define the standards for your software and hardware products and manage unapproved products in your organization.

## Overview and benefits of a TRM {#eaw-managing-the-technology-portfolio__section_lwg_dnr_dcc}

In your business enterprise, using unapproved software can create a risk to the organization. The risks can include the following:

* Security risks: The software might be exposed to security issues.
* Delivery risks: There might not be sufficient knowledge on how to support the software.
* Legal risks: A business application might use the software in illegal ways.
{#eaw-managing-the-technology-portfolio__ul_ovt_2nr_dcc}

You must define the standards for the software that is to be used and the software versions that are permitted for use in your organization. Use this module to identify non-permitted software in use across the organization
and the business applications that use it.  
You can use the TRM module in the Enterprise Architecture Workspace to perform the following:

* View a list of all available TRM products. You can also view the list of TRM products grouped by product category
* Request a TRM product
* Request a TRM product lifecycle
* Create a TRM product
* Create a TRM product lifecycle
* Approve or reject TRM product and product lifecycle requests
{#eaw-managing-the-technology-portfolio__ul_jcm_3nr_dcc}

When you request or create a TRM product, you can optionally add one or more lifecycle records as part of the same action. This eliminates the need to submit a separate lifecycle request afterward. Similarly,
approving or rejecting a standalone TRM product lifecycle request applies to all child lifecycle records included in that request.

Using the TRM module, you can manage the standards of the technology and set the right guardrail for technology usage. Setting the standards can improve the technical debt, security posture
and save costs for the organization.

You can also assign an owner to a TRM category, to facilitate clear accountability and improved governance standards. The owner is responsible for maintaining consistent technology compliance standards for that TRM category.

## TRM product lifecycle {#eaw-managing-the-technology-portfolio__section_okg_rxq_dcc}

Each product in the TRM library is associated with a set of lifecycle phases with a start and end date. The lifecycle phases could be approved, unapproved, approved with constraints, divest, and
evaluation.

The TLM home page fetches all the business applications that are used in your organization. It helps to review the status of the software that is being used. You can understand if any
business application is using the software that is not part of the TRM or a software version that is not approved for production. For more information, see [TRM lifecycle timelines on Gantt chart](https://www.servicenow.com/docs/kzLm3YGvPQo0QiE8kIXATw "For Technology Reference Model (TRM), the application services (hardware models and software products) are displayed in a hierarchical structure, similar to the TLM view. The corresponding lifecycle timelines of the application services are displayed as bars on the Gantt chart. It also displays the data for lifecycles with wild card versions. The TRM wildcard version ends with a ‘*’.").

The TRM module uses a similar module to TLM to search in the TRM library. You can view the software that is part of the TRM library, and initiate a request to add the software or software version to the TRM library.

You can also use the TRM with the Software Asset Management (SAM) plugin. This plugin helps you to fetch or select the products and versions for the TRM library. You can also define your own software products when the Software Asset Management integration module isn't available for your instance.

You can add lifecycle records to a TRM product as part of a product request or a standalone TRM product lifecycle request. The following limits apply to the number of lifecycle groups and phases you can include:  
Note:  
* For software products: You can add up to 5 version and edition combinations, with a maximum of 10 phases per combination.
* For hardware products: You can add up to 5 hardware models, with a maximum of 10 phases per hardware model.
* You can zoom on this page to 200% or 400% through your browser settings without the loss of content or functionality. Page layouts are transformed into a vertical, stacked view automatically.
{#eaw-managing-the-technology-portfolio__ul_lifecycle_limits_concept}
* **[TRM technical debt](https://www.servicenow.com/docs/HEkoFsVUp0qKsWmSFMbFGw)**   
  Manage the TRM technical debts that are created for the products that aren't approved for the usage.
* **[Technical debt calculation](https://www.servicenow.com/docs/Dn9Fxcic2TBTXHQvvJrIxQ)**   
  Technical debt records identify products used in business applications that aren't approved in the TRM or that use unapproved versions. View technical debt records to understand conformance gaps and plan remediation.
* **[Work with TRM lifecycle with wildcard](https://www.servicenow.com/docs/p87iTgx4gZ74a7HxiOGxeQ)**   
  Use Technology Reference Model (TRM) lifecycles with wildcards to update multiple software product lifecycles simultaneously without specifying exact minor version details.

**Related concepts**   

* [Working with Technology Reference Model (TRM) in EA Workspace](https://www.servicenow.com/docs/13O_khp~9nspQq~IuQ_n1w "The Technology Reference Model provides a structured, centralized view of all technology products; hardware, software, and platforms used across the enterprise.")
* [Gantt view of TLM and TRM lifecycle timelines](https://www.servicenow.com/docs/11Yl5k72nk0HYGNya6fFCA "A Gantt chart in the Enterprise Architecture Workspace displays TLM and TRM timelines for business applications and their associated application services.")
* [TRM lifecycle timelines on Gantt chart](https://www.servicenow.com/docs/kzLm3YGvPQo0QiE8kIXATw "For Technology Reference Model (TRM), the application services (hardware models and software products) are displayed in a hierarchical structure, similar to the TLM view. The corresponding lifecycle timelines of the application services are displayed as bars on the Gantt chart. It also displays the data for lifecycles with wild card versions. The TRM wildcard version ends with a ‘*’.")
* [Configure TRM phases](https://www.servicenow.com/docs/ujf1lEMN9sCmRjeQOepBSg "A Technology Reference Model (TRM) phase represents the status of the application, that is whether the application is approved for use, being evaluated or being scheduled for divestment.")
* [Configure TRM categories](https://www.servicenow.com/docs/qxsDgPGkKmPzlSodKOR1Dg "A Technology Reference Model (TRM) category refers to a grouping of TRM software products by their purpose and function.")  
**Related tasks**   

* [Approve or reject TRM requests](https://www.servicenow.com/docs/V0PMVYvqGVyyz1wp8w_fkg "As an Enterprise Architect, approve or reject a TRM product or product lifecycle requests submitted by other users.")
* [View TPM and TRM lifecycle timelines on the Gantt chart](https://www.servicenow.com/docs/E_A4LHOchFvp9VsCPFNs1A "Use the Gantt chart to view and track Technology Lifecycle Management (TLM) and Technology Reference Model (TRM) lifecycle timelines.")  
**Related reference**   

* [TRM technical debt states and transitions](https://www.servicenow.com/docs/gagEVaUCPyGscjporpJodA "A TRM technical debt record persists across scheduled job runs and moves between Active, Resolved, and Archived states instead of being deleted and re-created.")

