Skip to content

Commit

Permalink
Size flexibility Appendix
Browse files Browse the repository at this point in the history
  • Loading branch information
@cnharris10
cnharris10 committed Sep 1, 2024
1 parent 93199b7 commit f43ee82
Show file tree
Hide file tree
Showing 3 changed files with 202 additions and 1 deletion.
3 changes: 2 additions & 1 deletion specification/appendix/appendix.mdpp
View file
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,7 @@

*This section is non-normative.*

!INCLUDE "commitment_discounts.md",1
!INCLUDE "commitment_discounts/commitment_discounts.md",1
!INCLUDE "commitment_discounts/size_flexibility.md",1
!INCLUDE "grouping_constructs_for_resources_and_or_services.md",1
!INCLUDE "origination_of_cost_data.md",1
0 ...fication/appendix/commitment_discounts.md → ...mitment_discounts/commitment_discounts.md
View file
File renamed without changes.
200 changes: 200 additions & 0 deletions specification/appendix/commitment_discounts/size_flexibility.md
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,200 @@
# Size Flexibility

A usage-based commitment discount obligates a customer to a usage amount for one or more related SKUs in return for reduced rates. For example, when a customer purchases a usage-based commitment discount to cover a specific database SKU, this commitment will cover every hour over the term where at least one instance of this SKU is running. It can also cover eligible resources wholly, where 1 hour is covered by 1 resource, or partially, where 1 committed hour can be split across multiple resources or 1 resource can be fully covered with unused commitment discount costs. These latter two examples are commonly known as *size-flexibility*.

Since providers have different rules for when size-flexibility is or is not enabled, the following, made-up SKU pricing attributes will be used in each example below, and each example will be categorized under size-flexibility enabled or disabled sections.

## SKUs & Rates

| ProviderName | Service | SkuId | ListUnitPrice | CommittedUnitPrice | NormalizationFactor |
| ------------ | ------- | --------- | -------------- | -------------------| ------------------- |
| TinyCloud | Compute | VM_Small | $0.50 | $0.25 | 1 |
| TinyCloud | Compute | VM_Medium | $1.00 | $0.50 | 2 |
| TinyCloud | Compute | VM_Large | $2.00 | $1.00 | 4 |
| TinyCloud | Compute | VM_XLarge | $4.00 | $2.00 | 8 |

The above, made-up SKU pricing attributes show that this provider, *TinyCloud*, only has 1 service that offers 4 virtual machine SKUs with various list rates, committed rates, and normalization factors. Each SKU's normalization factor classifies its relative size to its committed rate. Usage-based commitment discounts with size-flexibility can fully cover any combination of 1 or more SKUs where the sum of their normalization factor equals the normalization factor of the commitment discount.

### Scenarios *without* size-flexibility

#### Scenario #1: 100% utilization with matching resources

Purchase: 1 commitment discount purchased for 1 year (2023) for 1 VM_Large.
Usage: 1 VM_Large resource runs from 2023-01-01 00:00:00 to 2023-01-01 01:00:00.

The commitment discount covers the first charge period for 1 VM_Large resource (i.e. <my-vm-id>) resulting in a $1 amortized cost.

```json
[
{
"BillingPeriodStartDate": "2023-01-01 00:00:00Z",
"BillingPeriodEndDate": "2023-02-01 00:00:00Z",
"ChargePeriodStartDate": "2023-01-01 00:00:00Z",
"ChargePeriodEndDate": "2023-01-01 01:00:00Z",
"ChargeCategory": "Usage",
"ChargeFrequency": "Usage-Based",
"PricingCategory": "Committed",
"ResourceId": "<my-large-vm-id>",
"PricingQuantity": 1,
"BilledCost": 0.00,
"EffectiveCost": 1.00,
"ConsumedUnit": 1,
"ConsumedUnit": "Hour",
"SkuId": "VM_Large",
"CommitmentDiscountId": "<commitment-discount-id>",
"CommitmentDiscountStatus": "Used",
"CommitmentDiscountQuantity": 1,
"CommitmentDiscountUnit": "Hour"
}
]
```

#### Scenario #2: 0% utilization with a non-matching resource

Purchase: 1 commitment discount purchased for 1 year (2023) for 1 VM_Large.
Usage: 1 VM_Medium resource runs from 2023-01-01 00:00:00 to 2023-01-01 01:00:00.

The VM_Large commitment discount is unused because no VM_Large resources are running. Additionally, 1 hour of on-demand usage was incurred by the running VM_Medium resource. These charges result in a $2 amortized cost.

```json
[
{
"BillingPeriodStartDate": "2023-01-01 00:00:00Z",
"BillingPeriodEndDate": "2023-02-01 00:00:00Z",
"ChargePeriodStartDate": "2023-01-01 00:00:00Z",
"ChargePeriodEndDate": "2023-01-01 01:00:00Z",
"ChargeCategory": "Usage",
"ChargeFrequency": "Usage-Based",
"PricingCategory": "Committed",
"ResourceId": "<my-large-vm-id>",
"PricingQuantity": 1,
"BilledCost": 0.00,
"EffectiveCost": 1.00,
"ConsumedUnit": 1,
"ConsumedUnit": "Hour",
"SkuId": "VM_Large",
"CommitmentDiscountId": "<commitment-discount-id>",
"CommitmentDiscountStatus": "Unused",
"CommitmentDiscountQuantity": 1,
"CommitmentDiscountUnit": "Hour"
},
{
"BillingPeriodStartDate": "2023-01-01 00:00:00Z",
"BillingPeriodEndDate": "2023-02-01 00:00:00Z",
"ChargePeriodStartDate": "2023-01-01 00:00:00Z",
"ChargePeriodEndDate": "2023-01-01 01:00:00Z",
"ChargeCategory": "Usage",
"ChargeFrequency": "Usage-Based",
"PricingCategory": "Standard",
"ResourceId": "<my-medium-vm-id>",
"PricingQuantity": 1,
"BilledCost": 1.00,
"EffectiveCost": 0.00,
"ConsumedUnit": 1,
"ConsumedUnit": "Hour",
"SkuId": "VM_Medium"
}
]
```

### Scenarios *with* size-flexibility

#### Scenario #1: 100% utilization with 2 VM_medium resources

Purchase: 1 commitment discount purchased for 1 year (2023) for 1 VM_XLarge with a normalization factor of 8.
Usage: 2 VM_Medium resources run from 2023-01-01 00:00:00 to 2023-01-01 01:00:00 with a normalization factor of 4 for each resource.

1 commitment discount for a VM_XLarge has a normalization factor of 8, and 2 VM_Medium resources have a normalization factor of 4, each. Therefore, with size flexibility, 1 VM_XLarge commitment discount can fully cover 2 VM_Medium resources resulting in a $2 amortized cost.

```json
[
{
"BillingPeriodStartDate": "2023-01-01 00:00:00Z",
"BillingPeriodEndDate": "2023-02-01 00:00:00Z",
"ChargePeriodStartDate": "2023-01-01 00:00:00Z",
"ChargePeriodEndDate": "2023-01-01 01:00:00Z",
"ChargeCategory": "Usage",
"ChargeFrequency": "Usage-Based",
"PricingCategory": "Committed",
"ResourceId": "<my-medium-vm-id>",
"PricingQuantity": 1,
"BilledCost": 0.00,
"EffectiveCost": 1.00,
"ConsumedUnit": 1,
"ConsumedUnit": "Hour",
"SkuId": "VM_Medium",
"CommitmentDiscountId": "<commitment-discount-id>",
"CommitmentDiscountStatus": "Used",
"CommitmentDiscountQuantity": 1,
"CommitmentDiscountUnit": "Normalized Hour"
},
{
"BillingPeriodStartDate": "2023-01-01 00:00:00Z",
"BillingPeriodEndDate": "2023-02-01 00:00:00Z",
"ChargePeriodStartDate": "2023-01-01 00:00:00Z",
"ChargePeriodEndDate": "2023-01-01 01:00:00Z",
"ChargeCategory": "Usage",
"ChargeFrequency": "Usage-Based",
"PricingCategory": "Committed",
"ResourceId": "<my-medium-vm-id>",
"PricingQuantity": 1,
"BilledCost": 0.00,
"EffectiveCost": 1.00,
"ConsumedUnit": 1,
"ConsumedUnit": "Hour",
"SkuId": "VM_Medium",
"CommitmentDiscountId": "<commitment-discount-id>",
"CommitmentDiscountStatus": "Used",
"CommitmentDiscountQuantity": 1,
"CommitmentDiscountUnit": "Normalized Hour"
}
]
```

#### Scenario #2: 100% utilization with 1 VM_Large resource

Purchase: 1 commitment discount purchased for 1 year (2023) for 1 VM_Small with a normalization factor of 1.
Usage: 1 VM_Large resource runs from 2023-01-01 00:00:00 to 2023-01-01 01:00:00 with a normalization factor of 4.

The VM_Small commitment discount was fully utilized but still only covered 25% of the VM_Large resource, so the rest of the VM incurred an on-demand cost of $1.50, and the amortized cost for this resource is $1.75.

```json
[
{
"BillingPeriodStartDate": "2023-01-01 00:00:00Z",
"BillingPeriodEndDate": "2023-02-01 00:00:00Z",
"ChargePeriodStartDate": "2023-01-01 00:00:00Z",
"ChargePeriodEndDate": "2023-01-01 01:00:00Z",
"ChargeCategory": "Usage",
"ChargeFrequency": "Usage-Based",
"PricingCategory": "Committed",
"ResourceId": "<my-large-vm-id>",
"PricingQuantity": 0.25,
"BilledCost": 0.00,
"EffectiveCost": 0.25,
"ConsumedUnit": 1,
"ConsumedUnit": "Hour",
"SkuId": "VM_Large",
"CommitmentDiscountId": "<commitment-discount-id>",
"CommitmentDiscountStatus": "Used",
"CommitmentDiscountQuantity": 1,
"CommitmentDiscountUnit": "Normalized Hour"
},
{
"BillingPeriodStartDate": "2023-01-01 00:00:00Z",
"BillingPeriodEndDate": "2023-02-01 00:00:00Z",
"ChargePeriodStartDate": "2023-01-01 00:00:00Z",
"ChargePeriodEndDate": "2023-01-01 01:00:00Z",
"ChargeCategory": "Usage",
"ChargeFrequency": "Usage-Based",
"PricingCategory": "Standard",
"ResourceId": "<my-large-vm-id>",
"PricingQuantity": 0.75,
"BilledCost": 1.50,
"EffectiveCost": 0.00,
"ConsumedUnit": 1,
"ConsumedUnit": "Hour",
"SkuId": "VM_Large"
}
]
```

0 comments on commit f43ee82

Please sign in to comment.