Baselines File

The baselines file contains any usage baselines that should be used to determine the pricing for tiered and peak time rebate rate plans. Baselines should be provided for each customer as new customers are introduced for the rate plan, or as baselines for customers change. The data must be provided in a single file that follows a specific naming convention. See File Name Conventions for more information.

Baseline Data File Assumptions

Any baseline listed in the file should be unique over a given period of time. For example, a customer cannot have more than one baseline for the same season.
A baseline value should always be provided in the same unit of measure as the reads for the service point associated with the account. For example, if the service point is electric and reads are in kWh, the baseline values should be in kWhs.

Note: This data file is only required if you have tiered and Peak Time Rebate rate plans. Your Delivery Team will work with you to determine if it is required in your situation.

Column Name	Description
account_id	Account identifier. Type: VARCHAR Can Be Empty?: No.
season	Season for which the baseline is applicable. This may be NULL if the baseline is not season-specific. Type: ENUM Allowed Values: WINTER SPRING SUMMER FALL Can Be Empty?: Yes.
usage_baseline	Baseline value. Type: DECIMAL (12,6). See Supported Decimal Formats for details. Can Be Empty?: No.
resolution	Resolution at which the baseline value applies. Type: ENUM Allowed Values: QUARTER_HOUR HALF_HOUR HOUR DAY BILLING MONTH YEAR Can Be Empty?: No.
rate_plan_identifier	The rate plan for which the baseline is applicable. This may be a wildcard () if the baseline applies to all rate plans for which the Service Agreement (SA) is eligible. Type: VARCHAR Can Be Empty?*: No.
rate_component	The unique identifier of the rate component to which the baseline applies. Type: VARCHAR Can Be Empty?: No.
start_date	Effective start date of the specified baseline value. Type: DATETIME. See Date and Time Handling for details. Can Be Empty?: Yes.
end_date	Date on which the specified baseline value is no longer effective. (This day is not part of the period covered by the specified baseline value.) This field may be NULL if the value is effective indefinitely. Type: DATETIME.See Date and Time Handling for details. Can Be Empty?: Yes.