Source Collector Classification and Definitions

Understanding Source Collector Terminology

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

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

These attributes are independent of each other, meaning a collector can combine multiple behaviours depending on its purpose and the data source.

Collector Classification Attributes

The primary attributes used to describe Source Collectors are:

• Rating Model
• Collection Behaviour
• Temporal Scope (where applicable)

Rating Model

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

Rated

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

Examples:

• Billing records from external vendors
• Usage data with pricing applied
• Financial transactions

In rated collectors, Varibill typically validates or reconciles values rather than calculating pricing.

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 applies pricing rules to calculate billing values.

Hybrid

Hybrid data includes a combination of rated and unrated elements.

Examples:

• Records containing both quantities and partial pricing
• Data where pricing exists but may require adjustment or enrichment in Varibill

Collection Behaviour

The Collection Behaviour describes how data is retrieved over time.

Discrete

Discrete collectors retrieve a snapshot of the current state at a specific point in time.

Each run replaces or refreshes the previous dataset rather than adding historical records.

Examples:

• Current active users
• Licence assignments
• Configuration states

Discrete collectors are commonly used for validation, allocation, or reconciliation scenarios.

Cumulative

Cumulative collectors retrieve data that accumulates over time.

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

Examples:

• Usage transactions
• Call detail records
• Metered consumption data
• Event logs

Cumulative collectors are commonly used for billing, usage tracking, and historical analysis.

Incremental (Optional Behavior)

Some collectors retrieve only data that has changed since the previous run.

This behaviour is sometimes referred to as incremental collection and may be used together with cumulative or discrete models.

Point-in-Time

Represents the state of data at a specific moment.

Typically associated with discrete collectors.

Period-Based

Represents activity occurring over a defined time period.

Typically associated with cumulative collectors.

Historical

Includes past records covering multiple periods or time ranges.

Related Articles

• Source Collectors: Setup and Configuration Guide