CliQr is now part of Cisco Learn More About Cisco

Financial Overview

Plans

A plan is an agreement determined by the admin and assigned to a user to determine the capacity or allowed usage for that user.

Icon

Users must accept plans assigned to them by their admins to start using CloudCenter.

Bundles

A bundle is like a prepaid phone card that allows users to run applications based on the capacity specified in the bundle.

Contracts

Every CloudCenter plan requires a contract. CloudCenter administrators can enforce the user to accept a Terms of Contract agreement that dictates how long this agreement should last. A CloudCenter contract does not automatically renew when the contract ends. Once a contract ends, users have the option to switch to another contract.

A contract and a plan work together – when you assign a plan you must assign a contract.

  • If you change a user's plan and also check the Renew Contract check box, it resets the contract period (see Usage Plan for additional context).

  • If you assign a plan to a user, the user signs a contract for a period of time.

  • If the user cancels the contract before the contract period ends, the user might be subject to a One-Time Fee.

You can change your plan at any time. However, when you change your plan, you renew your contract period, and will be back to being on the new plan for the entire span of your contract. For example:

  1. You sign a contract for 2 years.

  2. You change your plan a year after the contract period starts (and you still have a year of your contract remaining).
  3. As you changed your plan before your contract period ended (2 years), your contract period restarts and you will be on the new plan for 2 more years (NOT one year).

Who Creates Contract, Bundles, or Plans?

The root or tenant admin can create contract, bundles, and plans. The tenant admin can belong to an enterprise or to Cisco depending on the deployment. The CloudCenter documentation generally refers to both as the administrator (or admin). See People for additional context.

If the admin does not set up a contract plan or bundle for a user, then that user can deploy any application.

If the admin sets stipulates that the user requires a payment profile to be setup, then when the user logs into the CCM and accepts the terms of agreement, this user must manually set up a Payment Profile.

Admins have the following flexibility when creating contract dependencies:

  • Restrict certain contracts, bundles, and plans to just admins so it is not available to all users.
  • Edit or delete contract, bundles, and plans if no users have signed up. If users have signed up, the admin must create a new contract, bundle, or plan and revise the required settings.
  • Reset the contract start date for an active user.
  • Delete a bundle if that bundle is not assigned to any user.

CloudCenter Subscription Types

The financial controls for each deployment in available in the form of plans and bundles that provide budget and capacity details, charges for each VM, cloud time cost and so forth.

Icon

See Finance for related terminology and definition.

Terms

Contract?

Payment

Subscription Types

 
Plan

Yes

Billed

VM Hour Subscription (Default)

  • Specifies a limit for the number of VM hours per month 
  • Enable Rollover:  If checked, any unused VM hour balance will rollover to the next month. 
 

VM Subscription

  • Allows a specified number of concurrent VMs across all supported clouds
  • Overage Limit and Overage Rate
  • Base Price
  • Maximum Running VMs
  • One-Time Fee 
  • The VM count begins as soon as the VM is deployed
 

Unlimited Subscription

  • Does not have any limitations on usage
  • Users in this plan are not limited to VM hours, number of VMs,  a budget limit, or a time limit
  • Users pay for what they use and do not have to deal with any overage fees
  • Base Price
 

Bundle

No

Prepaid

Prepaid VM-Hour Bundle

  • Prepaid cost limit. No management fee or overage rate fee. Cloud cost is additional.
  • Typically, new users try out this bundle before their admin assigns them to a plan or before the user converts to a subscription plan
  • Seed Credits
  • Usage Increment Units: If checked, units above the limit are rounded up to the next level (for example, 11 minutes of actual usage with a 10-minute increment unit will be metered as 20 minutes).
  • Overage Limit and Overage Rate
  • One-Time Fee
  • Annual Fee: An optional fee charged on a per VM-hour basis.
 

Prepaid Budget Bundle

  • Prepaid time limit. You can run applications until this dollar amount is consumed. No management fee or overage rate fee
  • If your admin sets up a management fee (for example, $0.10 per hour), then this amount is deducted from the dollar limit.
  • Any additional cloud cost is also deducted from the dollar limit
  • Seed Credits
  • One-Time Fee
 

 

Common Options for All Subscription Types

The following parameters and check box selections are available to all subscription types:

Parameter/Check BoxDescription
Usage Details
Only Visible to Tenant Admin
  • If checked, this plan is only visible to the tenant admin.
  • Default = unchecked.
  • See Configure Cloud(s) for additional context.
Plan Fees

Bill me for my users cloud usage

  • If checked, the user's cloud cost is included in the Monthly Balance (SUBSCRIPTION_MONTHLY_FEE), Job Cloud Cost (JOB_CLOUD_COST), or Overage fee (JOB or VM OVERAGE_FEE). See billType for additional context.
  • Default = unchecked. All cloud costs are passed to the parent tenant (Pass Cloud Cost to Parent Organization)
Payment profile is required
  • If checked, users in this plan cannot perform any operation until they setup the payment profile.
  • Default = unchecked.

 

Chargeback Control

The granular chargeback control provided by CloudCenter compliment its management infrastructure:

  • The CloudCenter platform provides policy-driven runtime management (auto-scaling) and a granular level of usage for departmental chargeback. See Policies for additional context.
  • The User Activity Report provides reports and enforces usage at the application level, aggregated across multiple clouds with governance around licensing chargeback. As reports provide a granular level of usage for each tenant, you can enforce departmental chargebacks for the applicable tenants. See Usage Details Report for additional context.
  • You can create plans on a per-customer basis and make these plans visible to particular customers or to all customers for self-service scenarios. The administrator can set up billing cycles and contract lengths, as well as manage chargebacks for these customers. See Plan Configuration for additional context.
  • Tenants get complete independence with respect to enforcing chargebacks and generating billing. Admins/tenant admins can use the CCM UI to allow businesses to modify the user interface such as show/hide chargeback to each tenant/departments. See Tenant Billing for additional context.

Payment Options

A payment profile specifies how the user pays for supported services. The cost of the services includes one-time fees, annual fees, monthly subscription, overage fee, storage cost, and other charges agreed to in the CloudCenter contract.

A user can pay for cost of services using the following methods:

PaymentDependency
Credit cardRequires a valid credit card number, expiration date, and billing address (Visa, MasterCard, American Express, and Discover).
Purchase Order (PO)Requires a valid billing address for the monthly invoices and allows 30 days for the payment.

Meter Applications

Integrated metering, reporting, and billing ensure that users are always aware of their consumption and are charged appropriately for what they use.

  • The CCO monitors and meters deployed applications through the Management Agent. Monitoring and metering data is sent to the CCM for reporting purposes. The CCO continues to enforce deployment policies created by the user. For example, a user may have associated a deployment with an auto-scaling policy. The CCO continues to monitor the deployed application and orchestrates scaling as specified by the user in the policy.
  • IT can meter usage and issue departmental chargebacks, so that the users get the immediacy they need but IT controls and enforces the required mechanisms.
  • CloudCenter meters end user activity, enforces custom plans, and optionally bills the end user's credit card.
  • You can create plans on a universal basis or on a per-application basis for published Marketplace applications. Tenants can create the following types of pricing plans:
    • Pre-paid bundles metered by the consumption of compute-hours on the cloud. For example, a vendor can create a 3,000 compute hours/month bundle for application A and a 10,000 compute hours/month bundle for application B.
    • Pre-paid bundles metered by the number of application jobs or instances.

 

 

  • No labels