Source Collector Classification and Definitions

Modified on Wed, 18 Mar at 9:53 AM

Understanding Source Collector Terminology

This article explains the terminology used to describe Varibill Source Collectors.

Source Collectors can differ in how they retrieve data, the type of data retrieved, and how that data is processed within Varibill. To help users understand these differences, collectors are described using a set of classification attributes.

These attributes describe different aspects of how a collector retrieves and classifies data. A single collector may retrieve multiple data types, and the billing behaviour of the data is determined at the product level, not by the collector alone.

Collector Classification Attributes

The primary attributes used to describe Source Collectors are:

Rating Model
Collection Behaviour

Rating Model

The Rating Model describes whether the data retrieved by the collector includes monetary values.

Rated

Rated data already contains monetary values such as costs, prices, or charges.

Examples: - Usage data with pricing applied
- Financial transactions

In rated collectors, Varibill typically ingests data that already includes pre-assigned monetary values. This enables the direct application of markup percentages, eliminating the need to reference price lists for billing calculations.

Unrated

Unrated data contains quantities or allocations without monetary values.

Examples: - User licence allocations
- Asset counts
- Subscription quantities
- Consumption units without pricing

In unrated collectors, Varibill typically ingests only quantity (usage) data without any pre-assigned monetary values. Users must then apply pricing rules or rate plans to calculate the billable amounts.

Hybrid

Hybrid data includes a combination of rated and unrated elements within the same dataset. Hybrid refers to the structure of the incoming data only. It does not determine how the product is billed.

Data Capability

Some collectors are limited by the capabilities of the source system.

Point-in-time only: The collector can retrieve only the current state. Historical back-collection is not possible if the source does not retain prior states.
Historically capable: The collector can retrieve records covering previous time periods if the source system supports historical queries.

Example:
A directory system may not allow retrieval of users that were deleted prior to the collector’s first execution. In this case, the collector can only capture users from the time it first runs onward.

This distinction relates to the source platform’s capabilities and not the billing model.

Collection Behaviour

Collection Behaviour describes how the collector retrieves and structures source data during execution. It does not define how products are billed — billing behaviour is configured separately at product level.

Discrete

Discrete collectors retrieve a snapshot of the current state at the time of execution.

Each run captures the current state of the data. Over time, repeated executions build a historical picture, but the collector itself retrieves only the present state.

Examples: - Active users
- Licence assignments
- Configuration states

IMPORTANT: Discrete collection does not mean historical back-collection is possible. If the source system does not retain historical state, past data cannot be retrieved retroactively.

Cumulative

Cumulative collectors retrieve transactional or event-based data that naturally accumulates over time.

Each run typically adds new records to the dataset rather than replacing existing data.

Examples: - Call detail records
- Usage transactions
- Metered consumption
- Event logs

Cumulative collectors are commonly used where each record represents a distinct event, transaction, or measurable unit of consumption.

Billing Principles (Product Level Configuration)

Billing behaviour is determined at product configuration level — not by the collector itself.

Common billing principles include:

Discrete – billed per unit or per instance
Cumulative – billed based on total consumption
Delta – billed on change between measurements
Maximum – billed based on highest measured value
Average – billed based on calculated average
End-of-Cycle – billed at a defined cycle point

A single collector may retrieve data that supports multiple billing principles depending on how products are configured.

Example:
A backup collector may retrieve: - User licences (billed as discrete)
- Storage usage (billed as maximum)

Source Collectors: Setup and Configuration Guide