Designing Your Classic TOU Map Types

Now that you have your TOU map relationship types and your TOU groups defined, you can begin defining classic TOU map types. Recall that the classic TOU map type defines the physical attributes of the classic TOU map.

The essential attributes of any profile type are the TOU Group and the minutes per interval and the associated TOU map data creation algorithms.

The easiest way to start defining your classic TOU map types is to start with the classic TOU map relationship type and determine what type of classic TOU map each customer may have for the same TOU map relationship type.

Let's start with our TOU map relationship types and make some assumptions regarding the physical attributes of the data that a customer may have for each of these roles:

For Active demand, the quantities may be recorded in 15-minute or 30-minute intervals. To facilitate efficiency in processing the data, we recommend that the TOU map data is stored in the same minutes per interval as the interval data being mapped. We'll assume that this is a common TOU map type.
For Reactive demand, the quantities are recorded in 60-minute intervals. This is linked directly to the rate and is therefore a common TOU map type.
For curtailment, we will assume that the override map will be in 15-minute, 30-minute or 60-minute intervals, based on the interval size of the actual demand data. In addition, we require a TOU map creation algorithm. This algorithm will produce a data for the curtailment TOU map based on the existence of a contract option event. It will generate the time of use data based on a classic TOU map template. Refer to Contract Option Background Topics for more information. This will be an SA owned classic TOU map type.

Note:

We said above that we don't need a classic TOU map relationship type for Reactive Demand for our rate example. However, classic TOU map types must be defined. The table below includes the TOU map relationship type because we said we would add it just in case.

We will assume that all of our TOU data will not follow any seasonal time shifting. It will always be displayed in standard time. Refer to Time Zone and Time Changes and Designing Your Time Options for more information.


TOU Map Rel. Type	TOU Map Type, Classic	Common/ SA Owned	TOU Group	Min/ Interval	Seasonal Time Shift	Creation Algorithm
ACTVDMD	4PART15	Common	4PART	15	NoShift	N/a
ACTVDMD	4PART30	Common	4PART	30	NoShift	N/a
RACTVDMD	2PART60	Common	2PART	60	NoShift	N/a
CURTAIL	CURT15	SA Owned	CURTAIL	15	NoShift	Create based on events for 'curtail' contract option type.
	CURT30	SA Owned	CURTAIL	30	NoShift	Create based on events for 'curtail' contract option type.
	CURT60	SA Owned	CURTAIL	60	NoShift	Create based on events for 'curtail' contract option type.

Now, you're ready to set up your interval billing options.

Note:

The above table accomplishes two steps: defining TOU map types and defining the valid classic TOU map types for a TOU map relationship type. When setting up this data, you will need to define your classic TOU map types first and then link them to the appropriate classic TOU map relationship type.