Applications Inventory and Attributes - Vendor and Licensing attributes for the Applications Inventory

Applications Inventory and Attributes

Chapter 15. Vendor and Licensing attributes for the Applications Inventory

Vendor and Licensing attributes capture the commercial and contractual context governing each application — the governance foundation for avoiding auto-renewal failures, over-provisioning waste, and vendor lock-in.

Attribute Name	Maturity	Description and Notes
Primary Vendor or Supplier	Crawl	Description — The organization that supplies the application — the vendor from whom the software is licensed, the SaaS provider through whom the service is delivered, or the development organization that built and maintains a custom application. Benefit(s) — The foundational commercial governance attribute. Without a named primary vendor for every application, the organization cannot perform vendor concentration analysis, systematically manage vendor relationships, or identify the commercial dependencies that create supply chain risk. Source — Manually Entered. Examples — Salesforce, Inc. (Salesforce CRM), SAP SE (SAP S/4HANA), Microsoft Corporation (Microsoft Teams), Internal Engineering Team (custom-built order management system)
Vendor Support Status	Walk	Description — The current status of the vendor's support commitment for this application: Active Support, Limited Support (reduced scope or tier), or End-of-Life (vendor support has ceased or is announced to cease). Benefit(s) — Applications on Limited Support or End-of-Life vendor status carry security patch gaps, regulatory compliance risks, and operational resilience risks that escalate continuously. Tracking Vendor Support Status enables proactive modernization or replacement planning before the support expiry creates a crisis. Source — Manually Entered. Notes — Valid values: Active Support, Limited Support, End-of-Life.
License Type	Crawl	Description — The type of license under which the organization is authorized to use the application: Perpetual, Subscription, Open Source, or Custom. Benefit(s) — Determines the financial model, renewal obligations, compliance requirements, and exit terms that apply to the organization's use of the application. Mixing perpetual and subscription economics without explicit tracking produces budget forecasting errors and financial planning inconsistencies. Source — Manually Entered. Examples — Subscription (Salesforce CRM), Perpetual (SAP S/4HANA legacy license), Open Source (Apache Kafka — Apache License 2.0), Custom (negotiated multi-year enterprise agreement) Notes — Valid values: Perpetual, Subscription, Open Source, Custom, Not Applicable (for Custom-Built applications).
License Count or Seats Licensed	Walk	Description — The number of licenses or user seats the organization has purchased or provisioned for this application — the maximum authorized usage capacity under the current license agreement. Benefit(s) — The denominator in Utilization Rate calculation and a critical input to license compliance assessment. Organizations consistently over-provision licenses as teams grow and then fail to reduce provisioning when usage declines. Source — Manually Entered.
Licenses in Active Use	Walk	Description — The number of licenses or user seats actively used within the most recent measurement period. Benefit(s) — Enables immediate identification of over-provisioning where licenses purchased substantially exceed licenses used. The difference between License Count and Licenses in Active Use is recoverable cost in subscription environments and negotiating leverage in renewal conversations. Source — Manually Entered or derived from vendor license portal data where available.
License Expiration Date	Crawl	Description — The date on which the current license or subscription agreement expires — after which continued use without renewal would constitute unauthorized use. Benefit(s) — Prevents the most common commercial governance failure: continued use of software after license expiration, which creates legal liability, audit exposure, and emergency renewal negotiations from a position of weakness. Source — Manually Entered. Examples — 2027-06-30 (Salesforce CRM annual subscription), 2028-12-31 (SAP perpetual license support contract), 2026-03-31 — URGENT (legacy reporting tool, auto-renewal in 60 days)
Contract Reference ID	Walk	Description — The identifier of the contract or agreement governing the organization's use of the application in the enterprise contract management system. Benefit(s) — Creates the link between the application inventory and the contract management system of record, enabling APM to surface contract obligations, renewal dates, and exit terms without requiring separate manual research. Source — Manually Entered.
Contract Expiration or Renewal Date	Crawl	Description — The date on which the governing contract expires or auto-renews — which may differ from the License Expiration Date. Benefit(s) — The most operationally critical commercial governance attribute. Auto-renewal clauses in enterprise software contracts are among the most costly and most preventable sources of unwanted financial commitment in large application portfolios. Source — Manually Entered. Examples — 2027-06-30 (Salesforce CRM — 3-year contract with auto-renewal clause, 90-day cancellation notice required), 2026-09-01 (ServiceNow — annual renewal, currently under renegotiation) Notes — Alert thresholds: notify Vendor Relationship Manager 180 days before renewal, escalate to Executive Sponsor 90 days before renewal.
Vendor SLA	Walk	Description — The service level commitments the vendor has made in the governing contract — including availability commitments, support response times, incident resolution targets, and financial remedies when commitments are not met. Benefit(s) — Enables systematic tracking of vendor SLA compliance against actual service delivery and provides the contractual basis for pursuing service credits when vendors fail to meet their commitments. Source — Manually Entered.
Vendor Health Rating	Run	Description — An assessment of the vendor's organizational health and viability as a long-term supplier: Healthy, Stable, Concerns, or At Risk. Benefit(s) — Provides advance warning of vendor instability that may affect the organization's ability to rely on the vendor's product and support over the planning horizon. Applications supplied by vendors rated At Risk require exit planning regardless of current product satisfaction. Source — Manually Entered — assessed periodically by the Vendor Relationship Manager using market intelligence, analyst reports, and direct vendor engagement. Notes — Valid values: Healthy, Stable, Concerns, At Risk.
Sole-Source / Single-Vendor Dependency Indicator	Walk	Description — An indicator of whether the application function it delivers is available only from this vendor in the organization's current configuration. Benefit(s) — Identifies the commercial leverage asymmetry points in the portfolio where the organization's negotiating position is weakest and its operational exposure to vendor pricing changes or business failure is highest. Source — Manually Entered. Notes — Valid values: Yes, No.
Exit Rights and Portability Assessment	Run	Description — An assessment of the organization's practical ability to exit the vendor relationship and transition the application function to an alternative supplier or insourced solution — reflecting contractual exit rights, data portability provisions, integration complexity, and transition cost estimates. Benefit(s) — Without understanding exit rights and portability, organizations discover at the worst possible moment that they have no practical path to exit. Proactive assessment enables informed commercial negotiation and contingency planning before the need to exit becomes urgent. Source — Manually Entered — assessed by the Vendor Relationship Manager and Legal function in conjunction with contract review.

Legal Disclaimers