Cloud Cruiser became HPE Consumption Analytics on Nov. 1, 2018. You'll still see the old name in places while we update this site.

 

 

Consumption Analytics Documentation

Home > Documentation for older versions > Cloud Cruiser 4 for HPE GreenLake Flex Capacity > Working in Cloud Cruiser > Onboarding FC customers > Creating rate plans

Creating rate plans

Rate plans enable you to specify rates for individual services for one or more customers. For HPE FC, each customer will have one or more rate plans. There will always be one rate plan defined at the customer level of the account structure.  In addition, if reporting by location, there will be a rate plan for each location. The rate plans should provide rates for each service for the customer.

Services that are not tied to a specific location should be added to the customer level rate plan. For example, if service 00021-SAN is not tied to a location, it should be added to the customer level rate plan for AceRun (00021-AceRun).

Services that are tied to a specific location should be added to a location level rate plan for that location. For example, if service 00021-3PAR-10.10.10.33-FC is tied to location 10.10.10.33, it should be added to a location level rate plan for AceRun (00021-AceRun|10.10.10.33).

All services in the Default rate plan should be set to zero for FC customers.

Begin by setting all prices for all FC services in the Default rate plan to zero, and then create customer-specific rate plans.

Setting the default rate plan

To set prices in the Default rate plan

  1. Click Financial > Rate Plans.
  2. In the list of rate plans, click Default.
    The detail pane refreshes with a list of services in the Default rate plan. Services in red lack a price.

    If you attempt charge for a service that lacks a price, the charge step of Cloud Cruiser's workflow produces a warning and cannot publish billing values.


    defaultRatePlan1.jpg
  3. For any service lacking a price, click the Unit Price field, and enter 0.
    defaultRatePlan2.jpg
  4. Click Save.

Creating customer-specific rate plans

To create a customer level rate plan

  1. In the list of rate plans, right-click and select Create new rate plan.
    createNewRatePlan.jpg
    The Create new rate plan dialog box appears.
  2. In the Plan Name field, enter a name for the rate plan, using the convention <customerID>-<customerName>.
    For example, for AceRun enter 00021-AceRun.
  3. Enter a Description for the rate plan.
    This description appears directly on the Capacity Usage By Period report. Examples of descriptions include contract numbers, physical locations, and other terminology that might help an FC customer understand the invoice.
  4. Click OK.
    The new rate plan opens in the display pane, with all services from the Default rate plan.
  5. Click Edit Services.
    The Add/Remove Services dialog box appears.
  6. Click the checkbox next to the Group column header.
    This unchecks all of the services.
  7. Select all services starting with the customer ID for this rate plan that are NOT associated with a specific location.
    For example, for AceRun select all services that begin with 00021 and are not location specific.
  8. Click OK.
    The rate plan is updated to include only the customer level services associated with this customer.
  9. Click Save.
  10. Click Edit Customers.
    The Add/Remove Customers dialog box appears.
  11. Click the plus signs (+) on the explorer tree to expand the account structure and check the customer record that should be associated with this rate plan, and then click OK.
  12. Toggle the Show Advanced Options field to Yes.
    Additional columns are added to the table.
  13. Provide details for each service in the plan:
    1. In the Rate Type field, select a rate type:
      • Basic: ONLY USED FOR FIXED CHARGES, all other services will use Sticky Tiers - Metered or Final Tier - Metered, even if the service does not have stepped pricing.  For fixed charges, the monthly charge will be entered in the Fixed Price field.  If there are multiple instances of the same fixed price service, the total of ALL instances should be entered in this field.  For example, if there is a fixed charge of 500.00 for a service and there are 3 instances of that service, 1500.00 should be entered in the Fixed Price field.
      • Sticky Tiers - Metered (Marginal Pricing on the amendment form): Usage in each tier is charged the Unit Price for that tier. For example, with a tier for 0 to <5GB, and a tier for 5GB and up, actual usage of 7GB results in 4GB being charged at the price for the first tier and 3GB being charged at the price for the second tier.
      • Final Tier - Metered (Absolute Pricing on the amendment form): All usage for a date is charged the Unit Price for the final tier reached on that date. For example, with a tier for 0 to <5GB, and a tier for 5GB and up, actual usage of 7GB results in all 7GB being charged at the price for the second tier.
      • Sticky Tiers - Allocated and Final Tier - Allocated are NOT used in the HPE FC implementation

    2. For tiered services, in the Account Level field, enter the level of account structure at which tiered usage will be grouped for charging. This is usually the Customer or Location level of the account structure.
      For example, if all storage used by the FC customer is charged under a single rate plan, set a value of Customer. Alternatively, if an FC customer has multiple sites, and each site has its own rate plan, set a value of Location.
    3. For services with stepped pricing, define the ranges for each step (called Tier in the portal).
      To add multiple steps, right-click a step and select Add New Tier.
    4. Enter a value in either or both the Unit Price or Fixed Price fields.
      The Unit Price is the amount charged for a defined amount of the service used, such as 4 compute hours per day. The Fixed Price is the amount charged for merely using the service, regardless of how much of the service was used. You can define a Unit Price, a Fixed Price, or both. Using both allows you to use the Fixed Price as the setup charge, and the Unit Price as an additional charge based on usage.

      If you attempt charge for a service that lacks a price, the charge step of Cloud Cruiser's workflow produces a warning and cannot publish billing values

    5. In the Requested field, enter the requested capacity (committed capacity plus buffer capacity) for this service.
    6. In the Account Level field, enter a level of your account structure to charge for tiered usage.
      When reporting by Tier, this field should be set to Customer.  When reporting by Location or by Tier and Location, this field should be set to Location.
    7. In the Min Commit field, enter the initial committed capacity for this service.
      This value will be updated automatically month-to-month as usage changes, depending on the FC customer's plan.
    8. In the Commit % field, enter a percentage used to calculate committed capacity from the requested capacity. Enter 100 for a Basic deal.
    9. In the Max Shrink field, enter a percentage that is used to calculate the maximum reduction in committed capacity according to the FC customer's billing plan. For more information, see Billing model overview.
      • A value of 0 is a Basic deal, in which committed capacity can only grow.
      • A value from 1 to 99 is a Premium deal, in which committed capacity can grow and shrink, and the shrink will be gradual based on Max Shrink value (generally 10).
      • A value of 100 is a Premium deal, in which committed capacity can grow and shrink, and the shrink will be immediate.
    10. Optionally, click the Custom Description field, and enter a description of the service.
      advancedOptions.png
  14. Click Save to save the rate plan.

To create a location level rate plan

  1. Repeat the steps used to create a customer level rate plan with the following exceptions:
  2. In step 2, when entering the Plan Name field, enter a name for the rate plan using the convention <customerID>-<customerName>|<Location>.
    For example, for AceRun at location 10.10.10.33 enter 00021-AceRun|10.10.10.33.
  3. In step 7, when selecting services for this rate plan, select any services for this customer that are for the specific location.
    For example, for AceRun select all services that begin with 00021 and include 10.10.10.33 in the service name.
  4. In step 10, when selecting a customer record for this rate plan, continue expanding the explorer tree until you get to the LOCATION customer record that should be associated with this rate plan.
  5. In step 13f, set Account Level to Lcation.
  6. This section should be repeated for each customer location.

Configuring special end-of-month processing

At the end of each month, Cloud Cruiser calculates new minimum commitments and creates new revisions for all rate plans. Most of these are calculated based on the actual usage for the month, the current minimum commitment, the commitment percentage, and the Max Shrink values in the current revision of the rate plan.

However, some customers require the new minimum commitments to be calculated differently. Additionally, there might be cases in which a new minimum commitment needs to be entered manually, and the end-of-month calculations should not override that value. To handle these cases, use the following flags in the 00000_EndOfMonthFlags global lookup table:

  • cb: When set to true, indicates the minimum commitment will always be charged.
  • model: When set to Swedish, resets the minimum commitment to 80% of the actual usage if that value is greater than the current minimum commitment.
  • baselinerounding: When set to true, rounds the minimum commitment to the nearest integer.
  • capacityrounding: When set to true, rounds the actual usage to the nearest integer
  • noupdate_date: When set to the last day of a month (in YYYYMMDD format), no new minimum commitment will be calculated for the month following that date. This allows a new minimum commitment to be manually entered for the next month without being overwritten by end-of-month calculations.

To configure special end of month processing

  1. Click Data> Setup > Lookup Tables.
  2. Select the 00000_EndOfMonthFlags table.
  3. Click the plus sign (+) next to the Effective Dates field.
    The New Effective Date dialog box appears.
  4. Enter a new starting date, and then click OK. This date should match the revision date of the rate plan, which is the first day of the month.
  5. Click the Add Row button.
  6. In the Low ID field, enter the name of the service. For example, 00002-3PAR-SSD.
  7. In the Target ID field, enter the special end of month processing flags for that service.  For example, baselinerounding=true. Multiple flags can be set for the same service, separated by a comma.
  8. When done entering the flags, click Save.EndOfMonthFlags.png

Configuring multiple rates over time

Cloud Cruiser supports changing rates over time. For example, if a specific set of rates is available starting January 1, 2015, and will change on April 1, 2015, Cloud Cruiser supports both sets of rates.

To create a new date range for service rates

  1. On the Rate Plan page, click the plus sign (+) next to the Effective Dates field.
    The New Effective Date dialog box appears.
  2. Enter a new starting date, and then click OK.
    The new range is available in the Effective Dates drop-down field.
  3. Select the new range, and then enter rate types and pricing information for your services in the new range.
  4. If you want to remove a range of dates, select the range in the Effective Dates field, click the minus icon, and then click OK in the verification box.

    Ranges cannot overlap. When you add a new range, the end dates of existing ranges are adjusted to accommodate the new range. This ensures that all of the ranges defined for the rate plan combine to cover every day from January 1, 2000 through December 31, 2999. This also effectively prevents the rate plan from expiring.

    If you want a rate plan to expire before December 31, 2999, add a range with the end date you need, and then delete the existing range that ends December 31, 2999 by selecting that range and clicking the minus button. When a rate plan expires, customers assigned to that rate plan are charged according to the rates defined in the Default rate plan.

  5. Click Save.

Configuring step payments

Step payments are a specific example of configuring multiple rates over time. Step payments are based on a contract start date and a set of steps at which the minimum commitment or pricing increases. For example, consider a contract start date of 4/1/2015 with the following increasing minimum commitments:

  • Months 1-3: 25%
  • Months 4-6: 50%
  • Months 7-12: 70%
  • Months 13-48: 80%

In this example, rate plans for the customer are set up with 4 revisions:

Revision date range Minimum commitment
4/1/2015 - 6/30/2015 25%
7/1/2015 - 9/30/2015 50%
10/1/2015 - 3/31/2016 70%
4/1/2016 - 3/31/2019 80%

To create step payment revisions

  1. On the Rate Plan page, click the plus sign (+) next to the Effective Dates field.
    The New Effective Date dialog box appears.
  2. Enter the contract start date (such as 4/1/2015, as in the example above), and then click OK.
    The new range is available in the Effective Dates drop-down field.
  3. Open the Effective Dates drop-down field and select the first revision range (such as 01/01/2000 - 03/31/2015), click the minus icon, and then click OK in the verification box to delete that revision.
    The only revision remaining should be the one starting on on the contract start date.
  4. Enter the minimum commitment percentage for the first step (such as 25%) in the Commit % column, and then click Save.
  5. Click the plus sign (+) next to the Effective Dates field.
  6. Enter the first date of the next step (such as 7/1/2015), and then click OK.
  7. Select the new range, enter the minimum commitment percentage for the second step (such as 50%) in the Commit % column, and then click Save.
  8. Repeat for each step payment.

When these steps are completed, the Commit % values will be used to compute the actual Min Commit values for each month. For example, if the Requested value is 1000 and the Commit % is 25% for the first three months, the Min Commit value will be 250 for the first 3 months. If the Requested value remains 1000 for the next three months and the Commit % increases to 50%, the Min Commit value would be 500 for the next three months. The Min Commit values continue to be calculated in this manner through all rate plan revisions.

Last modified

Tags

This page has no custom tags.

Classifications

This page has no classifications.

 (c) Copyright 2017-2020 Hewlett Packard Enterprise Development LP