Contract Commitment Model

Contract Commitment Model represents the operational behavior and consumption flexibility of a contract commitment. This field distinguishes between rigid, "use-it-or-lose-it" obligations (typically hourly) and flexible, aggregate-based agreements that accommodate variable usage patterns.

Contract Commitment Model has two possible values: Continuous and Discontinuous. Continuous models (e.g., reserved instances, savings plans) represent a flat, constant "floor" of commitment where any dip in usage results in immediate, unrecoverable waste. Discontinuous models (e.g., enterprise agreements, SaaS minimum spend agreements) represent a broader, more flexible bucket where the commitment is "spikier": the usage can fluctuate wildly, but as long as the aggregate hits the target (or the true-up handles the variance), the commitment is satisfied. In either case, the interval of the commitment is represented by the Contract Commitment Fulfillment Interval.

ContractCommitmentModel MUST adhere to the following requirements:

• ContractCommitmentModel MUST be of type String.
• ContractCommitmentModel MUST NOT be null.
• ContractCommitmentModel MUST be one of the allowed values.
• ContractCommitmentModel MUST be "Discontinuous" when ContractCommitmentFulfillmentInterval is "Full Period".

Reporting and Analysis

• For continuous models: report on Utilization % to identify immediate waste.
• For discontinuous models: report on Burn Rate and Remaining Balance to ensure the "spikes" are not trending toward an early exhaustion of the fund or a massive year-end true-up bill.

Relationship with Fulfillment Interval

Because a Continuous model dictates a recurring, "use-it-or-lose-it" evaluation window, it cannot logically span an entire, cumulative contract term without a reset. Therefore, if the associated Contract Commitment Fulfillment Interval is Full Period, the Contract Commitment Model must be categorized as Discontinuous.