3.3.2 Contract Commitment Applicability

Contract Commitment Applicability is a structured definition of the specific entities eligible for coverage under a contract commitment. This column details inclusionary and exclusionary logic, as well as the specific portion of eligible cost or usage that is applicable.

3.3.2.1.1 Column Requirements

ContractCommitmentApplicability MUST adhere to the following requirements:

• ContractCommitmentApplicability MUST be of type JSON Object (serialized as a String where necessary).
• ContractCommitmentApplicability MUST conform to StringHandling requirements.
• ContractCommitmentApplicability MUST conform to JsonObjectFormat requirements.
• ContractCommitmentApplicability MUST conform to ContractCommitmentApplicabilityObject requirements.
• ContractCommitmentApplicability MUST NOT be null.

Contract Commitment Applicability consists of a valid JSON object which contains a set of top-level property keys. These keys define entity-based inclusionary and exclusionary logic, as well as the portion of relevant cost and/or usage that is applicable to the contract commitment.

The following section details the normative requirements for the ContractCommitmentApplicabilityObject and its nested properties. For a logical overview of the expected content, see the Schema Structure and Object Example sections.

3.3.2.2.1 Object Requirements

ContractCommitmentApplicabilityObject MUST adhere to the following requirements:

• ContractCommitmentApplicabilityObject MUST conform to the ContractCommitmentApplicabilityObjectSchema JSON Schema.
• ContractCommitmentApplicabilityObject.IsGlobalScope MUST be true when the contract commitment applies to all entities.
• ContractCommitmentApplicabilityObject.IsComplexScope MUST be true when the contract commitment's applicability logic exceeds schema capabilities.
• ContractCommitmentApplicabilityObject.Applicability.Cost MUST represent the fraction of an eligible charge's cost that is applicable to the commitment (0.0 to 1.0).
• ContractCommitmentApplicabilityObject.Applicability.Usage MUST represent the fraction of an eligible charge's usage that is applicable to the commitment (0.0 to 1.0).
• ContractCommitmentApplicabilityObject.Inclusions[*].Applicability.Cost MUST represent the fraction of an eligible charge's cost that is applicable to the commitment (0.0 to 1.0).
• ContractCommitmentApplicabilityObject.Inclusions[*].Applicability.Usage MUST represent the fraction of an eligible charge's usage that is applicable to the commitment (0.0 to 1.0).
• ContractCommitmentApplicabilityObject.Inclusions[*].Dimension SHOULD represent a column in Cost and Usage.
• ContractCommitmentApplicabilityObject.Exclusions[*].Dimension SHOULD represent a column in Cost and Usage.
• ContractCommitmentApplicabilityObject.Inclusions[*].Values MUST contain only the single string "*" when the wildcard is present.
• ContractCommitmentApplicabilityObject.Exclusions[*].Values MUST contain only the single string "*" when the wildcard is present.

3.3.2.2.2 Object Schema Structure

ContractCommitmentApplicability contains a structured JSON object defining the logical boundaries and the applicability percentage of a commitment.

ContractCommitmentApplicability uses a reserved string to represent global or unrestricted boundaries within a specific Dimension.

1. Inclusion Logic: When ["*"] is used in an Inclusion rule, the rule evaluates to True for every entity, effectively making the commitment "Organization-wide" for that specific Dimension.
2. Exclusion Logic: When ["*"] is used in an Exclusion rule, the rule evaluates to True for every entity, effectively excluding all entities (this is typically used only in combination with ExclusionOperator: "And" for surgical filtering).
3. Implicit Wildcards: If a Dimension (e.g., RegionId) is omitted entirely from the Inclusions array, it is treated as an implicit wildcard (unrestricted).

3.3.2.2.3 Object Implementation Guidance

The evaluation of an entity against a commitment applicability must follow a strict linear progression:

1. Normalization: Convert the entity attribute and the Scope Values to a consistent case (default: lowercase) for comparison.
2. Inclusion Evaluation: Iterate through Inclusions. If a match is found, record the rule-level Applicability if present. Apply InclusionOperator. If result is False, terminate.
3. Exclusion Evaluation: Iterate through Exclusions. If True, terminate evaluation.
4. Applicability Resolution:
   • Inheritance: A matching rule's Applicability object takes precedence over the top-level object.
   • Defaulting: If a metric key (Cost or Usage) is missing within a provided Applicability object, the engine must default that specific value to 1.0.
   • Rule-level Priority: Use the Applicability from the matching inclusion rule. If multiple rules match under Or, the engine must use the highest percentage for each respective metric.
   • Fallback: Use the top-level Applicability if no rule-level value is provided.

The evaluation of Applicability percentages must be contextually aligned with the Contract Commitment Model and Contract Commitment Fulfillment Interval:

• Continuous Models: Applicability percentages must be applied to each discrete unit of activity (e.g., every hour) within the Fulfillment Interval. If the commitment is not fully utilized by eligible entities within that hour, the remaining capacity expires.
• Discontinuous Models: Applicability percentages determine the portion of aggregate activity that counts toward fulfillment over the entire Interval (e.g., a full year).

1. Consistency: Engines should expect a JSON Object and should not support scalar (Decimal/Float) values for this field to ensure compatibility with typed database schemas.
2. Conflict Resolution: If IsGlobalScope or IsComplexScope is true, the Inclusions array must be empty or omitted. Additionally, IsGlobalScope and IsComplexScope must both not be true at the same time. Engines should validate these structural constraints before processing.

3.3.2.2.4 Object Example

Here is a basic example of the object format, describing organization-wide coverage except for Database services running in BillingAccountId 123456789012.

• For more detailed examples, please see this column's entry in the JSON Object Examples appendix entry here.
• For the JSON schema, please see Contract Commitment Applicability Object Schema.

{
  "IsGlobalScope": true,
  "ExclusionOperator": "And",
  "Exclusions": [
    {
      "Dimension": "BillingAccountId",
      "Operator": "In",
      "Values": ["123456789012"]
    },
    {
      "Dimension": "ServiceCategory",
      "Operator": "In",
      "Values": ["Database"]
    }
  ]
}

3.3.2.2.5 Object ID

ContractCommitmentApplicabilityObject

3.3.2.2.6 Object Display Name

Contract Commitment Applicability Object

A structured definition of the specific entities to which a contract commitment applies, including inclusion/exclusion logic and applicability percentages.