A resource whose actual workload draws meaningfully less from provisioned capacity than the design assumption supporting that capacity. Under-utilization is the engineering counterpart to overprovisioning. The federation distinguishes the two by intent: overprovisioning describes the configuration choice, under-utilization describes the workload outcome. Federation reporting under UFMS-001:2.4 requires utilization to be expressed against the dominant resource constraint, whether CPU, memory, network, or licence-bound metric, rather than a generic average. Under-utilized resources require either rightsizing or documented retention rationale.
A compound of the Latin prefix under and the verb utilise; the term entered cloud cost vocabulary as part of the rightsizing literature.
Federation members publish under-utilization by dominant constraint per service. Sustained under-utilization across multiple constraints triggers a rightsizing or decommissioning ticket under MEV-Annex:3.2. Exemptions for performance headroom are tracked in the exemption register.
@misc{ifo4_glossary_under_utilized,
title = {{Under-Utilized}},
author = {{IFO4 Federation Editorial Board}},
howpublished = {{IFO4 Federation Glossary, slug \texttt{under-utilized}}},
year = {2026},
url = {https://ifo4.org/glossary/under-utilized},
note = {Category: Waste; key: UnderUtilized}
}Federation members and accredited practitioners may challenge any entry under TGS-002:1.7. Filed challenges are routed to the editorial board, triaged into the revision register, and resolved in writing on the public docket. The slug remains stable through any revision.