Peak Pricing Event File
In order to support rate plans with event day pricing attributes, the Rate Engine must receive notification that an event will occur. This peak pricing event file should be transmitted on the day prior to an event date, unless otherwise specified by the Delivery Team. The file must follow a specific naming convention. See File Name Conventions for more information.
Note: This data is only if applicable if your utility needs to provide peak pricing data in support of certain products. Your Delivery Team will work with you to determine if it is required in your situation.
| 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. Type: VARCHAR Can Be Empty?: No. |
|
season |
The applicable season. Not applicable for peak event records. Type: ENUM Allowed Values:
Can Be Empty?: Yes. |
|
day_type |
The type of day. Not applicable for peak event records. Type: ENUM Allowed Values:
Can Be Empty?: No. |
|
period |
The period being defined. ‘PEAK_EVENT’ is applicable for peak event records. Type: ENUM Allowed Values: PEAK_EVENT Can Be Empty?: No. |
|
ordinal |
Allows for distinguishing events with same season, day_type, and period. This is not applicable for peak event records. Type: INTEGER (1-10) Can Be Empty?: Yes. |
|
resolution |
Used in combination with the duration to indicate the length of time covered by the event. The value is typically ‘HOUR’ for peak event records. Type: ENUM Allowed Values:
Can Be Empty?: No. |
|
duration |
Used in combination with resolution to indicate the length of time covered by the event. The value is typically ‘1’ for peak event records. Type: INTEGER Can Be Empty?: No. |
|
start_date |
The start date. This is not applicable for peak event records. 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?: Yes. |
|
event_date |
Date of the critical peak day. Type: DATE (YYYYMMDD) Can Be Empty?: No. |
|
effective_start_date |
Not applicable for peak event records. Type: DATE (YYYYMMDD) Can Be Empty?: Yes. |
|
effective_end_date |
Not applicable for peak event records. Type: DATE (YYYYMMDD) Can Be Empty?: Yes. |