Key Concepts

This topic sets out and explains the key concepts of the m3ter platform. Links for more details on these key concepts are provided.

​

Organization

An Organization represents either:

• Your company as a direct customer of m3ter.
• Your company as an indirect customer of m3ter via one of our partners who integrate with m3ter.

​

Products

A Product in m3ter represents a product or service that you offer to your end customers. Each Product can act as a container the following items:

• Plan Templates and Plans
• Meters
• Aggregations
• Pricing

Plans and Plan Templates always belong to a specific Product. You can create Meters and Aggregations which belong to a specific Product, as shown above.

​

Plan Templates and Plans

You can use PlanTemplates to define default values for the pricing Plans you want to apply to your Products. This allows you to avoid unnecessary repetition when setting up your pricing Plans, while retaining some flexibility to adjust individual pricing Plans to suit individual customer accounts. Each Plan is a child of a PlanTemplate and represents a specific pricing plan for one of your products or services. A Plan inherits key attributes for billing purposes from a PlanTemplate, such as the pricing structure, billing currency, billing frequency, billing interval, and any standing charge to apply to each bill. In a particular Plan, only some of these inherited attributes, such as pricing structure and standing charge, can be overridden to meet individual account billing needs. You can create Plan Groups for cases where you want to apply a minimum spend amount at billing across several of your products or features that are each priced separately. When you create the Plan Group, you can define an overall minimum spend and then add the priced Plans you want to include in the Group.

​

Meters

A Meter is used to collect usage data. You can set up Data Fields for a Meter to collect usage data measurements for your products or services. If required, you can use these raw data fields to set up more complex usage data collectors as Derived Fields, whose values are the result of calculations made on Data Fields.

​

Aggregations

When you have configured a Meter for usage data collection, you can create an Aggregation using the Data Fields or Derived Fields on the Meter. This allows you to define how the data collected by Data Fields will be aggregated to create a metric to suit the pricing model you want to apply to one of your products or services. For example:

• You might want a Data Field’s data to be summed to yield a pricing metric.
• Or for another Data Field’s data, you might want the maximum value reached to be used as a pricing metric.

As key aspects for usage-based pricing, there are further ways you can use Aggregations to achieve the precise units of usage you require for pricing your products:

• You can use your Aggregations to create Compound Aggregations. These allow you to derive numerical measures from usage data by applying a calculation to one or more simple Aggregations. This capability greatly extends the range of unit measure you can set up for the pricing you want to apply to usage.
• If the Meter your Aggregation targets contains the appropriate Data Fields, you can also configure Segmented Aggregations, which allow you to segment the usage data collected by a single Meter and go on to apply separate pricing to the resultant segmented values. This capability can prove extremely useful for implementing some pricing and billing use cases.

​

Counters

Many providers of SaaS products and services want to charge their end-customers for product consumption using a subscription or recurring charge pricing model, one where end-customers are charged based on the numbers of product units, seats, or user licenses subscribed to within a given billing period. Counters in m3ter enable you to quickly implement a wide-range of unit-based pricing models for your products:

• Set up recurring subscription charges for your products with a quantity or number of units as the pricing metric.
• Offer your end-customers a flexible subscription model to help them optimize their subscription costs and easily manage their billing as their level of product consumption changes.
• Implement hybrid pricing models for products or services that you want to charge your end-customer for in a mixed way - partly on this kind of subscription basis and partly based on metered product usage.

​

Pricing

​

Usage-Based Pricing

For usage-based pricing, you can link an Aggregation to a Plan or a PlanTemplate to produce usage-based pricing plans. You can then complete the pricing configuration by selecting the type of pricing structure you want for your pricing plans, such as tiered pricing, pricing by volume, or stairstep pricing.

​

Unit-Based Pricing

For unit-based pricing, you can quickly price Product Plans in the Pricing Editor using Counters.

​

Hybrid Pricing

If you want to apply a hybrid pricing model for a product or service, you can set up a combined pricing for a Product Plan to charge end-customers who consume the product or service using:

• An Aggregation as the pricing metric for usage-based charges you want to apply.
• A Counter as the pricing metric for any recurring subscription charges you want to apply.

At billing, all charge amounts due on the Account are combined in a single Bill.

​

Accounts

An Account represents your end customer - a person or company that pays your Organization for one of your products or services. For setting up your end customer Accounts, you can:

• Attach a Plan to an Account, which determines the pricing that will be applied to that Account for billing purposes. When you attach a Plan to an Account, you can select for the start and end dates to define the period the pricing Plan is active and will be applied to the Account for billing purposes.
• Apply a Prepayment/Commitment to an Account for cases where your customer has agreed to pay a fixed amount over the duration of their contract with you to consume one or more of your products or services. The amount is understood as payable regardless of the actual usage they become liable to pay for during the contract period. You can include a surcharge rate to be applied for any overage on the Prepayment/Commitment amount that occurs during the contract period.
• Create Contracts for end-customer Accounts. If you expect to have end customers who consume several different service or product packages you offer, for accounting purposes you can then report on the total Contract values for these end customer Accounts.
• Create Child Accounts for a main or Parent Account. You might want to do this if your Organization has customers with multiple Accounts and instead of issuing multiple bills to these customers, you want to provide them with single Bill for a Parent Account that covers data usage across their multiple Child Accounts.
• Define Custom Plans for an Account. A Custom Plan can only be attached to that specific Account.

In your production environment, operationally you can:

• Open an Account Overview summarizing the Account setup and showing latest Bills for the Account with charts tracking billed usage and any recurring charges.
• Review and manage a detailed listing of Account Bills.

​

Account Plan

When you attach a priced Plan to an Account, this defines a link between them to create an Account Plan. Attaching priced Plans to an Account determines the charges incurred by customers who are put on the Plan when they consume one of your Products.

​

Account Plan Group

When you attach a Plan Group to an end customer Account, this defines a link between them to create an Account Plan Group. The Account Plan Group for an Account determines the charges incurred by the Account.

​

Billing

A Bill is generated for an Account based on the usage-based pricing Plan that has been attached to the Account.