Rate Period Definitions File

Many pricing plans have periods associated with different prices. For example, in a TOU plan, afternoon hours may be “on peak.” The purpose of the rate period definitions file is to provide rate period configuration information to Oracle Utilities for these types of plans. This file should be provided on a periodic basis at the same frequency at which rate periods change. Note that when defining TOU periods, off-peak periods should not be explicitly defined. On-peak and part-peak periods should be defined, and the system will default any other times that are not covered by on-peak and part-peak as off-peak. The data must be provided in a single file that follows a specific naming convention. See File Name Conventions for more information.

Note: This data is only required if you have a time of use (TOU) plan or another pricing plan that requires rate periods. Your Delivery Team will create the file and work with you to gather the necessary inputs.

Column Name	Description
rate_plan_identifier	The unique rate plan for which the event is applicable. This may be a wildcard () if the event is applicable to all rate plans. Type: VARCHAR Can Be Empty?*: No.
rate_component	The unique identifier of the rate component for which the event is applicable (for example, ‘TOU’). This may be a wildcard () if the event is applicable to all rate components in the specified rate plan. Type: VARCHAR Can Be Empty?*: No.
season	The season for which the period is being defined. Type: ENUM Allowed Values: WINTER SPRING SUMMER FALL Can Be Empty?: Yes.
day_type	The type of day for which the period is being defined. Type: ENUM Allowed Values: WEEKEND WEEKDAY HOLIDAY Can Be Empty?: Yes.
period	The period being defined. Type: ENUM Allowed Values: ON_PEAK PART_PEAK OFF_PEAK CRITICAL_PEAK NON_CRITICAL_PEAK Can Be Empty?: No.
ordinal	Allows for distinguishing events with same season, day_type, and period. Type: INTEGER (1-10) Can Be Empty?: Yes.
resolution	Used in combination with duration to indicate the length of time covered by the event. Type: ENUM Allowed Values: QUARTER_HOUR HALF_HOUR HOUR DAY BILLING MONTH YEAR Can Be Empty?: No.
duration	Used in combination with resolution to indicate the length of time covered by the event. Type: INTEGER Can Be Empty?: No.
start_date	Not applicable for rate periods. Type: DATE (MMDD) Can Be Empty?: Yes.
start_time	Start time of the event in military time. Do not specify a timezone. The local timezone of the utility is assumed. Type: TIME (HHMM) Can Be Empty?: No.
event_date	Not applicable for rate periods. Type: DATE (YYYYMMDD) Can Be Empty?: Yes.
effective_start_date	The date on which this event configuration becomes effective. Type: DATE (YYYYMMDD) Can Be Empty?: No.
effective_end_date	Date on which the configuration is no longer effective, if known. This day is not part of the event period. Type: DATE (YYYYMMDD) Can Be Empty?: Yes.