Commitment Discount Appendix

specification/appendix/appendix.mdpp

@@ -2,6 +2,7 @@
 
 *This section is non-normative.*
 
+!INCLUDE "commitment_discounts.md",1
 !INCLUDE "grouping_constructs_for_resources_and_or_services.md",1
 !INCLUDE "origination_of_cost_data.md",1
 !INCLUDE "examples/examples.mdpp",1

specification/appendix/commitment_discounts.md

@@ -0,0 +1,278 @@
+# Commitment Discounts
+
+A [*commitment discount*](glossary:commitment-discount) is a billing discount model that offers reduced rates on preselected [SKUs](#glossary:sku) in exchange for an obligated usage or spend amount over a predefined [*term*](glossary:term). *Commitment discounts* typically consist of purchase and usage records within cost and usage datasets.
+
+Usage-based *commitment discounts* obligate a customer to a predetermined amount of usage over a preselected *term*. In some cases, usage-based *commitment discounts* also feature [*commitment flexibility*](glossary:commitment-flexibility) which may expand the types of *resources* that a *commitment discount* can cover. It is important to note when mixing *commitment discounts* with and without *commitment flexibility*, the `CommitmentDiscountUnit` should reflect this difference.
+
+Spend-based commitment discounts obligate a customer to a predetermined amount of spend over a preselected *term*. In the usage examples below, each [*row*](glossary:row) measures the monetary amount of the hourly commit consumed by the *commitment discount*, so the `CommitmentDiscountUnit` chosen is "USD", or the [*billing currency*](glossary:billing-currency).
+
+## Purchasing
+
+While customers are bound to the *term* of a *commitment discounts*, providers offer some or all of the following payment options before and/or during the *term*:
+
+* *All Upfront* - The *commitment discounts* is paid in full before the *term* begins.
+* *No Upfront* - The *commitment discounts* is paid on a repeated basis, typically over each [*billing period*](glossary:billing-period) of the *term*.
+* *Partial Upfront* - Some of the *commitment discounts* is paid before the *term* begins, and the rest is paid repeatedly over the *term*.
+
+For example, if a customer buys a 1-year, spend-based *commitment discount* with a $1.00 hourly commit and pays with the partial option, the *commitment discount's* payment consists of a one-time purchase in the beginning of the *term* *and* monthly recurring purchases with the following totals:
+
+1. *One-Time* - $4,380 (`24 hours * 365 days * $1.00 * 0.5`)
+2. *Recurring* - $182.50 (`24 hours * 365 days * $1.00 / 12 months`)
+
+## Usage
+
+Commitment discounts follow a "use-it-or-lose-it" model where the [*amortization*](glossary:amortization) of a *commitment discount's* purchase applies evenly to eligible *resources* over each [*charge period*](glossary:charge-period) of the *term*.
+
+For example, if a customer buys a spend-based *commitment discount* with a $1.00 hourly commit in January (31 days), only $1.00 is eligible for consumption for each hourly *charge period*. If a customer has eligible *resources* running during this *charge period*, an amount of up to $1.00 will be allocated to these *resources*. Conversely, if a customer does have eligible *resources* running that fully take advantage of this $1.00 during this *charge period*, then some or all of this amount will go to waste.
+
+## Commitment Discounts in FOCUS
+
+Within the FOCUS specification, the following examples demonstrate how a *commitment discount* appears across various payment and usage scenarios.
+
+### Purchase *Rows*
+
+All *commitment discount* purchases appear with a positive `BilledCost`, `PricingCategory` as "Committed", and with the *commitment discount's* id populating both the `ResourceId` and `CommitmentDiscountId` value. One-time purchases appear as a single record with `ChargeCategory` as "Purchase", `ChargeFrequency` as "One-Time", and the total quantity and units for *commitment discount's* *term* reflected as `CommitmentDiscountQuantity` and `CommitmentDiscountUnit`, respectively.
+
+Recurring purchases are allocated across all corresponding *charge periods* of the *term* when `ChargeCategory` is "Purchase", `ChargeFrequency` is "Recurring", and `CommitmentDiscountQuantity` and `CommitmentDiscountUnit` are reflected only for that *charge period*.
+
+Using the same *commitment discount* example as above with a one-year, spend-based *commitment discount* with a $1.00 hourly commit purchased on Jan 1, 2023, various purchase options are available:
+
+#### Scenario #1: All Upfront
+
+The entire *commitment discount* is billed _once_ during the first *charge period* of the *term* for $8,670 (derived as `24 hours * 365 days * $1.00`).
+
+```json
+[
+    {   
+        "BillingPeriodStartDate": "2023-01-01T00:00:00Z",
+        "BillingPeriodEndDate": "2023-02-01T00:00:00Z",
+        "ChargePeriodStartDate": "2023-01-01T00:00:00Z",
+        "ChargePeriodEndDate": "2024-01-01T00:00:00Z",
+        "ChargeCategory": "Purchase",
+        "ChargeFrequency": "One-Time",
+        "PricingCategory": "Committed",
+        "ResourceId": "<commitment-discount-id>",
+        "BilledCost": 8760.00,
+        "EffectiveCost": 0.00,
+        "CommitmentDiscountId": "<commitment-discount-id>",
+        "CommitmentDiscountQuantity": 8760.00,
+        "CommitmentDiscountUnit": "USD"
+    }
+]
+```
+
+#### Scenario #2: No Upfront
+
+The *commitment discount* is billed across all 8,760 (`24 hours * 365 days`) *charge periods* of the *term* with $1.00 allocated to each *charge period* over the *term*.
+
+```json
+[
+    {
+        "BillingPeriodStartDate": "2023-01-01T00:00:00Z",
+        "BillingPeriodEndDate": "2023-02-01T00:00:00Z",
+        "ChargePeriodStartDate": "2023-01-01T00:00:00Z",
+        "ChargePeriodEndDate": "2023-01-01T01:00:00Z",
+        "ChargeCategory": "Purchase",
+        "ChargeFrequency": "Recurring",
+        "PricingCategory": "Committed",
+        "ResourceId": "<commitment-discount-id>",
+        "BilledCost": 1.00,
+        "EffectiveCost": 0.00,
+        "CommitmentDiscountId": "<commitment-discount-id>",
+        "CommitmentDiscountQuantity": 1.00,
+        "CommitmentDiscountUnit": "USD"
+    },
+
+    /* ... 8,759 more recurring purchase records for the *term* ... */
+]
+```
+
+#### Scenario #3: Partial Upfront
+
+With a 50/50 split, half of the commitment is billed _once_ during the first *charge period* of the *term* for $4,380 (derived as `24 hours * 182.5 days * $1.00`), and the other half is billed across each *charge period* over the term, derived as (`$1.00 * 8,760 hours * 0.5`). Amortized costs incur half of the amount (i.e. $0.50) from the one-time purchase and the other half from the recurring purchase.
+
+```json
+[
+    {
+        "BillingPeriodStartDate": "2023-01-01T00:00:00Z",
+        "BillingPeriodEndDate": "2023-02-01T00:00:00Z",
+        "ChargePeriodStartDate": "2023-01-01T00:00:00Z",
+        "ChargePeriodEndDate": "2024-01-01T00:00:00Z",
+        "ChargeCategory": "Purchase",
+        "ChargeFrequency": "One-Time",
+        "PricingCategory": "Committed",
+        "ResourceId": "<commitment-discount-id>",
+        "BilledCost": 4380.00,
+        "EffectiveCost": 0.00,
+        "CommitmentDiscountId": "<commitment-discount-id>",
+        "CommitmentDiscountQuantity": 4380.00,
+        "CommitmentDiscountUnit": "USD"
+    },
+    {
+        "BillingPeriodStartDate": "2023-01-01T00:00:00Z",
+        "BillingPeriodEndDate": "2023-02-01T00:00:00Z",
+        "ChargePeriodStartDate": "2023-01-01T00:00:00Z",
+        "ChargePeriodEndDate": "2023-01-01T01:00:00Z",
+        "ChargeCategory": "Purchase",
+        "ChargeFrequency": "Recurring",
+        "PricingCategory": "Committed",
+        "ResourceId": "<commitment-discount-id>",
+        "BilledCost": 0.50,
+        "EffectiveCost": 0.00,
+        "CommitmentDiscountId": "<commitment-discount-id>",
+        "CommitmentDiscountQuantity": 0.50,
+        "CommitmentDiscountUnit": "USD"
+    },
+
+    /* ... 8,759 more recurring purchase records for the *term* ... */
+]
+```
+
+### Usage *Rows*
+
+*Amortization* of *commitment discounts* occur similarly regardless of how *commitment discount* purchases are made.  The same usage-based or spend-based amount is applied evenly across all *charge periods* and potentially allocated to eligible *resources*.  Continuing with the same *commitment discount* example, a one-year, spend-based *commitment discount* with a $1.00 hourly commit and 1 *resource* (for simplicity) yields 4 types of scenarios that can occur during a *charge period*:
+
+* Scenario #1: An eligible *resource* fully consumes the allocated amount (100% utilization)
+* Scenario #2: No eligible *resource* consumes the allocated amount (0% utilization)
+* Scenario #3: An eligible *resource* partially consumes the allocated amount (75% utilization)
+* Scenario #4: An eligible *resource* fully consumes the $1.00 hourly commit with an overage (100% utilization + overage)
+
+#### Scenario #1: An eligible *resource* fully consumes the allocated amount (100% utilization)
+
+In this scenario, one eligible *resource* runs for the full hour and consumes $1.00, so one *row* allocated to the *resource* is produced.
+
+```json
+[
+    {
+        "BillingPeriodStartDate": "2023-01-01T00:00:00Z",
+        "BillingPeriodEndDate": "2023-02-01T00:00:00Z",
+        "ChargePeriodStartDate": "2023-01-01T00:00:00Z",
+        "ChargePeriodEndDate": "2023-01-01T01:00:00Z",
+        "ChargeCategory": "Usage",
+        "ChargeFrequency": "Usage-Based",
+        "PricingCategory": "Committed",
+        "ResourceId": "<resource-id>",
+        "ConsumedQuantity": 1,
+        "ConsumedUnit": "Hour",
+        "BilledCost": 0.00,
+        "EffectiveCost": 1.00,
+        "CommitmentDiscountId": "<commitment-discount-id>",
+        "CommitmentDiscountQuantity": 1.00,
+        "CommitmentDiscountStatus": "Used",
+        "CommitmentDiscountUnit": "USD"
+    }
+]
+```
+
+#### Scenario #2: No eligible *resource* consumes the allocated amount (0% utilization)
+
+In this situation, the full eligible, $1.00 amount remained unutilized and results in 1 unused *row*. In this scenario, it is important to note that while `CommitmentDiscountQuantity` is not because $1 was still drawn down by the *commitment discount* even though, no *resource* was allocated, so `ConsumedQuantity` and `ConsumedUnit` are null.
+
+```json
+[
+    {
+        "BillingPeriodStartDate": "2023-01-01T00:00:00Z",
+        "BillingPeriodEndDate": "2023-02-01T00:00:00Z",
+        "ChargePeriodStartDate": "2023-01-01T00:00:00Z",
+        "ChargePeriodEndDate": "2023-01-01T01:00:00Z",
+        "ChargeCategory": "Usage",
+        "ChargeFrequency": "Usage-Based",
+        "PricingCategory": "Committed",
+        "ResourceId": "<commitment-discount-id>",
+        "ConsumedQuantity": null,
+        "ConsumedUnit": null,
+        "BilledCost": 0.00,
+        "EffectiveCost": 1.00,
+        "CommitmentDiscountId": "<commitment-discount-id>",
+        "CommitmentDiscountQuantity": 1.00,
+        "CommitmentDiscountStatus": "Unused",
+        "CommitmentDiscountUnit": "USD"
+    }
+]
+```
+
+#### Scenario #3: An eligible *resource* partially consumes the allocated amount (75% utilization)
+
+In this scenario, one eligible *resource* runs for the full hour and consumes $0.75 of the $1.00 allocation. One *row* shows $0.75 to a *resource*, and the other *row* shows that $0.25 was unused.
+
+```json
+[
+    {
+        "BillingPeriodStartDate": "2023-01-01T00:00:00Z",
+        "BillingPeriodEndDate": "2023-02-01T00:00:00Z",
+        "ChargePeriodStartDate": "2023-01-01T00:00:00Z",
+        "ChargePeriodEndDate": "2023-01-01T01:00:00Z",
+        "ChargeCategory": "Usage",
+        "ChargeFrequency": "Usage-Based",
+        "PricingCategory": "Committed",
+        "ResourceId": "<resource-id>",
+        "ConsumedQuantity": 1,
+        "ConsumedUnit": "Hour",
+        "BilledCost": 0.00,
+        "EffectiveCost": 0.75,
+        "CommitmentDiscountId": "<commitment-discount-id>",
+        "CommitmentDiscountQuantity": 0.75,
+        "CommitmentDiscountStatus": "Used",
+        "CommitmentDiscountUnit": "USD"
+    },
+    {
+        "BillingPeriodStartDate": "2023-01-01T00:00:00Z",
+        "BillingPeriodEndDate": "2023-02-01T00:00:00Z",
+        "ChargePeriodStartDate": "2023-01-01T00:00:00Z",
+        "ChargePeriodEndDate": "2023-01-01T01:00:00Z",
+        "ChargeCategory": "Usage",
+        "ChargeFrequency": "Usage-Based",
+        "PricingCategory": "Committed",
+        "ResourceId": "<commitment-discount-id>",
+        "ConsumedQuantity": null,
+        "ConsumedUnit": null,
+        "BilledCost": 0.00,
+        "EffectiveCost": 0.25,
+        "CommitmentDiscountId": "<commitment-discount-id>",
+        "CommitmentDiscountQuantity": 0.25,
+        "CommitmentDiscountStatus": "Unused",
+        "CommitmentDiscountUnit": "USD"
+    }
+]
+```
+
+#### Scenario #4: An eligible *resource* fully consumes the $1.00 hourly commit with an overage (100% utilization + overage)
+
+In this scenario, one eligible *resource* runs for the full hour and is charged $1.50. One *row* shows that $1.00 was *amortized* from the *commitment discount*, and the other shows that $0.50 was charged as standard, on-demand spend.
+
+```json
+[
+    {
+        "BillingPeriodStartDate": "2023-01-01T00:00:00Z",
+        "BillingPeriodEndDate": "2023-02-01T00:00:00Z",
+        "ChargePeriodStartDate": "2023-01-01T00:00:00Z",
+        "ChargePeriodEndDate": "2023-01-01T01:00:00Z",
+        "ChargeCategory": "Usage",
+        "ChargeFrequency": "Usage-Based",
+        "PricingCategory": "Committed",
+        "ResourceId": "<resource-id>",
+        "ConsumedQuantity": 1,
+        "ConsumedUnit": "Hour",
+        "BilledCost": 0.00,
+        "EffectiveCost": 1.00,
+        "CommitmentDiscountId": "<commitment-discount-id>",
+        "CommitmentDiscountQuantity": 1.00,
+        "CommitmentDiscountStatus": "Used",
+        "CommitmentDiscountUnit": "USD"
+    },
+    {
+        "BillingPeriodStartDate": "2023-01-01T00:00:00Z",
+        "BillingPeriodEndDate": "2023-02-01T00:00:00Z",
+        "ChargePeriodStartDate": "2023-01-01T00:00:00Z",
+        "ChargePeriodEndDate": "2023-01-01T01:00:00Z",
+        "ChargeCategory": "Usage",
+        "ChargeFrequency": "Usage-Based",
+        "PricingCategory": "Standard",
+        "ResourceId": "<resource-id>",
+        "ConsumedQuantity": 1,
+        "ConsumedUnit": "Hour",
+        "BilledCost": 0.50,
+        "EffectiveCost": 0.00
+    }
+]
+```

specification/glossary.md

@@ -54,7 +54,7 @@ A billing discount model that offers reduced rates on preselected SKUs in exchan
 
 <a name="glossary:commitment-flexibility"><b>Commitment Flexibility</b></a>
 
-A feature of [*commitment discounts*](#glossary:commitment-discount) that may further transform the predetermind amount of usage purchased or consumed based on additional, provider-specific requirements.
+A feature of [*commitment discounts*](#glossary:commitment-discount) that may further transform the predetermined amount of usage purchased or consumed based on additional, provider-specific requirements.
 
 <a name="glossary:cloud-service-provider"><b>Cloud Service Provider (CSP)</b></a>
 

specification/markdownlnt.cfg

@@ -2,6 +2,7 @@
   "plugins" : {
     "MD033" : { "enabled" : false },
     "MD013" : { "enabled" : false },
+    "MD031" : { "enabled" : false },
     "MD041" : { "enabled" : false },
     "additional_paths": "../custom_linter_rules/rule_md_990.py"
   }