Source Collector Classification and Definitions

Understanding Source Collector Terminology

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

Source Collectors determine how data is retrieved or received, while billing behavior is determined at the product level.

Collector Classification Attributes

Source Collectors are described using the following classification attributes:

• Rating Model
• Collection Behavior
  • Point-in-Time
  • Period-Based
  • Historically Capable

These attributes describe how data is retrieved and structured. They do not determine how data is billed.

Rating Model

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

Rated

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

Examples:

• Usage data with pricing applied
• Financial transactions

In rated data, billing values are already present. Varibill can apply markups without referencing price lists.

Unrated

Unrated data contains quantities or allocations without monetary values.

Examples:

• User license allocations
• Asset counts
• Subscription quantities
• Consumption units without pricing

In unrated data, pricing and billing rules are applied within Varibill.

These distinctions determine which API endpoint must be used when submitting data.

Hybrid

Hybrid data includes both rated and unrated elements within the same dataset.

Hybrid refers only to the structure of incoming data. It does not determine billing behavior.

Collection Behavior

Collection Behavior describes how data is retrieved from the source system during execution.

It defines how data is collected, not how it is billed.

Point-in-Time

Point-in-Time collectors retrieve the current state of the source system at the time of execution.

Each run reflects the present state only. Historical views are built over time through repeated executions.

Examples:

• Active users
• License assignments
• Configuration states

Period-Based

Period-Based collectors retrieve data for a specific, predefined period such as a billing cycle or invoice month.

Each run targets a particular period rather than capturing the current state. The period is typically controlled by a configuration parameter (for example, a billing period identifier or a month offset).

Examples:

• Invoice line items for a specific billing month
• Unbilled consumption data for a current or previous billing period

Historically Capable

Historically Capable collectors can retrieve past or date-range-based data directly from the source system.

Examples:

• Usage transaction records
• API usage logs
• Metered consumption data

Billing Behavior Context

Billing behavior is determined at the product configuration level, not by the Source Collector.

This means:

1. The Source Collector retrieves data
2. The product configuration determines how that data is billed