Separate descriptive attributes from relationship and financial attributes - Technology Portfolio Management (TPM) Best Practices
Separate descriptive attributes from relationship and financial attributes
(Chapter 40 of Technology Portfolio Management (TPM) Best Practices)
Executive Summary: Chapter Overview
IF4ITThe Bottom Line
Core Concepts
| Concept | Definition & Strategic Role |
|---|---|
| Descriptive Attributes | The attributes that identify and describe the technology itself — name, semantic identifier, category, description, lifecycle stage — that change relatively slowly and belong with the primary technology record. |
| Relationship Attributes | Attributes that connect the technology to other entities — dependent applications, vendors, licenses — typically maintained collaboratively by the TPM Practice Owner, the Technology Owner, and the teams that own the connected inventories. |
| Financial Attributes | Attributes that capture what a technology costs — license fees, infrastructure, support — typically maintained by the Finance Partner and TPM Practice Owner in collaboration with procurement and vendor management. |
Quick Q&A
Question: Why does mixing attribute classes in one record cause problems?
Question: How should the separation be implemented in practice?
Read More Below
Overview
Technologies Inventory records contain three fundamentally different types of information that serve different purposes and require different maintenance disciplines. Descriptive attributes describe what a technology is. Relationship attributes describe how it connects to other entities in the Enterprise Model — the applications that depend on it, its vendor, its licenses. Financial attributes describe what it costs. Mixing these three without distinction produces records that are difficult to maintain, difficult to analyze, and difficult to hand off between the roles best positioned to maintain each type.
Best Practice
Structure Technologies Inventory records with an explicit organizational distinction between descriptive, relationship, and financial attributes. Descriptive attributes are best maintained by the Technology Owner, who knows the technology itself. Relationship attributes are best maintained collaboratively by the TPM Practice Owner, the Technology Owner, and the teams that own the connected inventories. Financial attributes are best maintained by the Finance Partner and TPM Practice Owner in collaboration with procurement and vendor management. Document this structural distinction in the TPM data strategy so every contributor understands which attributes they are responsible for.
Benefit(s)
Separating attribute types produces cleaner, more maintainable technology records with higher data quality in each category. Maintenance responsibilities are clear and assigned to the people with the best knowledge of each attribute type. Financial analysis can be performed without touching descriptive or relationship data, and vice versa. AI analysis of Technologies Inventory data is more reliable because the distinction between attribute types is visible in the data structure rather than requiring inference.
How to cite this page
When referencing this page in academic work, internal standards, or external publications, include the page title, IF4IT as author and publisher (The International Foundation for Information Technology (IF4IT), LLC), the URL, and your access date.
Example (informal web citation):
The International Foundation for Information Technology (IF4IT), LLC. Separate descriptive attributes from relationship and financial attributes | Technology Portfolio Management (TPM) Best Practices. https://if4it.org/best-practices/technology-portfolio-management-tpm/separate-descriptive-attributes-from-relationship-and-financial-attributes/ (accessed 2026-09-08).
See About Us for content governance and site-wide citation guidance.
Copyright for The International Foundation for Information Technology (IF4IT), LLC: 2008 - Present
Legal Disclaimers