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

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Enterprise Architecture

ft:clusterId :

    - appportman

bundleId :

    - appportman

workflow :

    - Technology


---

# TRM technical debt form

# TRM technical debt form {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 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 TRM technical debt form

The TRM technical debt form enables ServiceNow customers to create and manage records of technical debt for Technology Reference Model (TRM) products that do not align with defined TRM phases and standards.
This helps organizations track and remediate technology misalignments within their enterprise architecture, ensuring better governance and lifecycle management of software products.
Show full answer Show less  

## Key Features

* **Unique Identification:** Each technical debt record has a unique Number to facilitate easy referencing and management. Records created before upgrading to Enterprise Architecture Workspace 10.1.3 may display as (empty), but can still be accessed.
* **Reason and Business Application:** Document the cause of the technical debt and associate it with a relevant business application for context.
* **State Management:** Technical debt records have states (Active, Resolved, Archived) that reflect their current status and progression. This supports lifecycle tracking and remediation efforts.
* **TRM Product and Phase:** Specify the software product and its TRM phase, such as Approved, Approved with Constraints, Divest, Evaluation, or Unapproved. These phases help classify the technology's lifecycle status and usage permissions.
* **Software and Version Details:** Capture details about the software product, including version, edition, model, and operating system (if applicable), ensuring precise identification of the technology involved.
* **Server and TRM Level:** For relevant products, record the associated server and indicate whether the debt is at the Product or Product Lifecycle level.
* **Automated Updates:** The form includes a Last run timestamp indicating when the scheduled job last updated the technical debt records, maintaining data currency.
* **Related Lists:** The Discovered Technology related list links technical debt records to TLM discovered technology entries, providing a starting point for investigation and remediation. These related records enable navigation to detailed technology lifecycle information.

## Practical Use for ServiceNow Customers

By using the TRM technical debt form, customers can systematically identify and document technology assets that fall outside approved TRM standards. This visibility helps prioritize remediation activities, align technology portfolios with governance policies, and track progress through defined debt states. Integration with TLM discovered technology records supports deeper analysis and informed decision-making regarding technology lifecycle management.  
Create Technology Reference Model (TRM) technical debts for products that aren't aligned with TRM phases and standards.
{#eaw-trm-technical-debt-form__table_ak2_5fg_tyb__entry__2}

| Field | Description |
|-|-|
| Number | Unique identifier of the technical debt record. Select this value to open the technical debt record. Note: If you upgraded to Enterprise Architecture Workspace version 10.1.3, technical debt records created before the upgrade display (empty) in this field. Select (empty) to open these records. Records created after the upgrade have a number. |
| Reason | Reason why the technical debt was created. |
| Business Application | Business application associated with the TRM product. |
| State | State of the technical debt record: Active, Resolved, or Archived. For details on how the record moves between states, see [TRM technical debt states and transitions](https://www.servicenow.com/docs/8DAgcqx6EgFMJXAGk_mH2A "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."). |
| TRM product | Software product that has version-specific life cycles. |
| TRM phase | Phase of the TRM product. The following TRM phases are available: * Approved: The technology is approved for use. * Approved with Constraints: The technology can be used within the constraints specified in the comments. * Divest: A decision was taken to divest from the use of the technology. * Evaluation: This technology is being evaluated and can't be used for production purposes. * Unapproved: The technology is not permitted to be used. {#eaw-trm-technical-debt-form__eaw-create-trm-phase_define-trm-phases_ul_ghz_pcg_d5b} Note: You can modify these phases by navigating to EA WorkspaceSetupTRM Phases. |
| Software product | Software product related to the TRM product. |
| Version | Version of the software product. The software product model name usually contains this version. |
| Edition | Edition of the software product. Populated only when the technical debt is created from a TRM product lifecycle that matches on version and edition. |
| Software product model | Software product model related to the TRM product. |
| Operating system | Operating system on which the TRM product can be deployed. This field appears only when Software is selected in the Type field. |
| Last run | Timestamp when the Populate TRM technical debts in the EA Workspace scheduled job last ran to update the table with technical debt. |
| Server | Server related to the TRM product. Note: This field is available starting with Technology Lifecycle Management (TLM) plugin version 1.7.1. |
| TRM level | Level (Product or Product Lifecycle) at which the technical debt is created. |
[Table 1. Technical Debt form fields]

{#eaw-trm-technical-debt-form__table_ak2_5fg_tyb}

## Related lists {#eaw-trm-technical-debt-form__section_related_lists}

The Discovered Technology related list shows the TLM discovered technology records that this technical debt was created from.

Use this related list as your starting point to investigate and remediate the technical debt. Open a discovered technology record from the list. Use its Number field to open the full TPM Discovered Technology
record, or its TLM technology lifecycle field to open the associated technology lifecycle record. From there, you can identify and update the underlying TRM product or TRM product lifecycle that's causing the debt.
**Related concepts**   

* [TRM technical debt](https://www.servicenow.com/docs/9HeJ7gsI3hwIrMTcfucN0g "Manage the TRM technical debts that are created for the products that aren’t approved for the usage.")  
**Related tasks**   

* [View Technology Reference Model technical debts](https://www.servicenow.com/docs/ZEAG7RWWybK735k~FRbgXQ "View Technology Reference Model (TRM) technical debts created for products that aren't aligned with TRM phases and standards.")  
**Related reference**   

* [TRM technical debt states and transitions](https://www.servicenow.com/docs/8DAgcqx6EgFMJXAGk_mH2A "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.")
* [Governing TRM product fields](https://www.servicenow.com/docs/NUfg4dobcARAGL0istGFKg "The TLM Technology Lifecycle [sn_apm_tpm_technology_lifecycle] table includes fields that link a discovered technology to the TRM product and product lifecycle that govern its obsolescence status.")

*[\>]: and then


