Count (Active Quantity) Usage

Count Data represents usage that is active over multiple periods until there is a change. For example, Count Data may represent the number of active users for a SaaS product. As soon as a user is added or removed the Count Data changes.

The ZAB Count Data record may be used to capture and bill count-based usage activity. At a minimum, Count Data records must supply a Quantity and Effective Date to the Rate Plan Search Map. The Quantity is evaluated for each charge period until the End Date (on either the Subscription Item or on the Count Data record) has been reached.

For example, a music streaming service charges $10/month per membership. A member can add more listeners to their account for an additional $8/listener a month. When another listener is added to the account, the member is charged $18/month until they decide to drop the additional listener- then their monthly charge goes back to $10/month.

In this example, the customer is charged for the membership regardless if they listen to the service that month or not. The charge is recurring and the amount is consistent until a change is made to the membership- e.g. adding another listener or canceling the membership.

Characteristics

• Count Data records must have an “Effective Date”
  
  • An Effective Date must be populated on the Count Data record and depending on the use case, an End Date may be added.
• Count Data is evaluated for each charge period in which it is effective during the Rating Process.
  
  • For example, if the Count Data record has an Effective Date of 01/01/2021 and an End Date of 04/01/2021, Count Data will be evaluated for each Charge Period through 04/01/2021.
• There are two options available if Count Data quantities need adjustment:
  
  • Add an End Date to the existing Count Data record, then create a new Count Data record for the new total Quantity.
  • Leave the existing Count Data record unchanged (with no End Date), and create a new Count Data record to represent the Quantity increase or decrease with no End Date.

Count Data is rated when:

• Charge periods fall on or after the Effective Date and on or before the End Date, if one is present.
  
  • The End Date is not required for this record type. Count Data with an End Date will become inactive after the stated End Date (no longer produce Charges).
• Charge periods fall on or after the Effective Date and no End Date is present. In this scenario, the Count will stop being charged on the Subscription Item End Date.

Use Case Examples

• A SaaS company charges a monthly fee for each user license. Licenses can be added or removed throughout the life of the contract.
• A company leases a gym for its employees and is charged a monthly membership fee for each employee. Most charges are consistent until an employee leaves or a new employee is hired.

Configuring a Rate Plan Search Map for Count Data

To create the Rate Plan Search Map for Consumption usage:

1. Go to Setup > Zone Advanced Billing Maps/Definitions > Rate Plan Search Map > New
2. Name the Rate Plan Search Map.
3. Select the Search that will be providing Count data.
   
   1. When building the Search, the Search Type should be ‘ZAB Count Data’ or any other record representing Count usage.
4. Select Quantity Search as the Available For Search Type
5. Under Field Mapping, select the Search Map Type ‘Count (Activity Quantity)’
6. Select the Effective/Start Date AND End Date fields on the Count record that align with the Charge Period.
7. Under Search Mapping ‘Quantity Column In Search Results’, specify which column in Search results represents Quantity (e.g. column 8 in search results provides these values).
8. Under Search Mapping ‘Start Date Column In Search Results’, specify which column in Search results represents the Start Date.
9. Under Search Mapping ‘End Date Column In Search Results’, specify which column in Search results represents the End Date.
10. Optionally define any additional fields that should map to the Charge records.
11. Define the Filter Mapping to determine how the Search results should be “matched” to the Subscription Item.
12. Save

Example of a Rate Plan Search Map configured for count-based usage activity. Search data and record types will determine how values and filters are set. Be mindful that configuration is unique to the use case and environment. In this example, quantity values are supplied by the 6th column in the linked Search and Count data is filtered by Subscription Item to ensure activity is only applied to the Subscription Item that matches the one stamped on the Count Data record.