Technology Portfolio Management (TPM) Best Practices

Overview

Technology licenses are not uniform. The rights, obligations, restrictions, and financial models associated with different license types vary substantially, and the governance disciplines appropriate to each type differ in important ways. A perpetual license grants the right to use a specific version of the software indefinitely but typically requires a separate maintenance agreement for access to updates and support. A subscription license provides access to the current version and updates for a defined period and expires if not renewed. A SaaS license provides access to a hosted service rather than to software installed on the organization’s infrastructure. An open source license grants rights to use, modify, and distribute the software subject to the conditions of the specific license type. A usage-based license charges based on actual consumption rather than a fixed fee. An embedded license governs software that is embedded in hardware or other products rather than installed independently. Each model requires governance disciplines calibrated to its specific characteristics.

Best Practice

Classify every license agreement in the license inventory by the primary license model type it represents, using the classification as the basis for applying the appropriate governance disciplines to each agreement. For perpetual licenses: track the version covered by the perpetual right, the separate maintenance agreement and its renewal terms, and the technology’s version currency status relative to the perpetually licensed version. When a perpetual-licensed technology reaches end-of-support, the organization must either renew maintenance to access a supported version, migrate to an alternative, or accept the security and compliance risk of operating on an unsupported version without vendor patch support. For subscription licenses: track the renewal date, the subscription scope, and the utilization rate, and manage renewals proactively rather than reactively. For SaaS licenses: apply the SaaS utilization management discipline described in the FinOps subsection. For open source licenses: apply the Open Source Governance disciplines described in the dedicated subsection. For usage-based licenses: implement continuous usage monitoring and forecast usage growth to anticipate cost changes before they appear in billing statements. For embedded licenses: track the product versions in which each embedded software component appears and connect the embedded software’s lifecycle to the product lifecycle in the Hardware Technologies Inventory.

Benefit(s)

License type classification ensures that each license agreement is governed with disciplines appropriate to its specific model rather than with a one-size-fits-all approach that works adequately for no license type. Perpetual licenses are governed for version currency and maintenance agreement management. Subscription licenses are governed for renewal timing and utilization. Open source licenses are governed for compliance and supply chain risk. The classification also makes license portfolio analysis possible: the organization can see the distribution of its license portfolio by type, identify over-concentration in license models that carry specific risks, and make informed decisions about license model preferences in future procurement.