Constraints

Column type
Dimension
Feature level
Mandatory
Allows nulls
No
Data type
String
Value format
Allowed values
Dataset
Contract Commitment

Description

Contract Commitment Benefit Category defines the primary value or advantage received for a contract commitment. It identifies whether the benefit is realized as a price reduction, a feature entitlement, a guarantee of service availability, or some other commercial outcome.

Requirements

ContractCommitmentBenefitCategory MUST adhere to the following requirements:

  • ContractCommitmentBenefitCategory MUST be of type String.
  • ContractCommitmentBenefitCategory MUST NOT be null.
  • ContractCommitmentBenefitCategory MUST be one of the allowed values.

Implementation guidance

Distinguishing Outcomes from Mechanisms

When categorizing a commitment, the value reflects the actual commercial benefit received, rather than the funding or consumption mechanism used to acquire it. For example, a prepaid "monetary pool" or a drawdown fund is a mechanism; the benefit of that pool is typically the right to use the feature (Entitlement) or the reduced rate unlocked by the commitment (Discount).

Distinguishing from Technical IDs

Availability represents the contractual right to access resources. It must not be confused with technical fields like CapacityReservationId. A single Availability within a contract may encompass multiple technical reservations across various regions or accounts.

Primary Benefit Logic

In cases where a commitment provides multiple benefits (e.g., an Entitlement that also includes a Discount), the value should reflect the primary commercial driver of the agreement as defined by the procurement or FinOps team.

Read the source on focus.finops.org ↗