6

Time-of-Use Map

Review From The Fundamentals Course

Copyright 2010, Oracle. All rights reserved.

A TOU Map Has TOU Data

A TOU map defines the TOU code for each interval
A time-of-use map's TOU data

An interval MC's final measurements

TOU Map: 6593920101

MC ID: 12391010192

Date/Time

TOU
Code

Date/Time

Final
Consump.

1-Jan-10 3:00pm

PEAK

1-Jan-10 3:00pm

14.678

1-Jan-10 4:00pm

PEAK

1-Jan-10 4:00pm

29.12

1-Jan-10 5:00pm

PEAK

1-Jan-10 5:00pm

12.12

1-Jan-10 6:00pm

PEAK

1-Jan-10 6:00pm

17.16

Technical note: Because TOU data is structured the same as final

measurement data (a separate row exists for each interval), creating the
sum / max quantity for each TOU code becomes a high-speed SQL
statement.

6-2

Copyright 2010, Oracle. All rights reserved.

Logical Groups of TOU Codes

Some implementations have many TOU codes
Consider a rate that has different prices depending on:

The season of the year (winter, spring, summer, fall)

The time of day (peak, off-peak, shoulder)

The actual temperature as compared to the historic

average (normal, hotter, colder)
This rate would require 36 TOU codes (4 seasons * 3 time of
days * 3 temperature bands)
Contrast this to a rate with prices that differ depending on the
time of day (peak, off peak, shoulder); this rate requires just 3
TOU codes
A TOU group defines the TOU codes that can be used on a TOU
map; they exist to prevent errors when setting up a TOU map

When TOU data is created, only TOU codes defined on a

given TOU group can be specified, for example:

6-3

The winter-peak-normal TOU code could not be used

used on a simple TOU map

Copyright 2010, Oracle. All rights reserved.

TOU Group: Multi-season /

Multi-period / Weather
normalized
TOU Code
Winter-Peak-Normal
Winter-Peak-Hot
Winter-Peak-Cold
Winter-Offpeak-Normal
Winter-Offpeak-Hot

TOU Group: Multi-period

TOU Code
Peak
Offpeak
Shoulder

A TOU Map Template Defines TOU Data Generation Rules

Every TOU map references a TOU map template
The system periodically generates TOU data for a TOU map by interpreting
the rules on the map's template
This TOU map template is used to generate the TOU data
for the adjacent rate (notice the TOU Group that holds the
valid TOU codes that can be referenced on the template)

TOU Map Template

6-4

Shoulder

Peak

Shoulder

Off-Peak

Peak

Shoulder

Peak

Off-Peak

Copyright 2010, Oracle. All rights reserved.

The Default TOU code

is used for periods not
explicitly defined
(hence no periods are
needed for off-peak)

Calendars and Holidays

Many rates categorize consumption on holidays differently
For example, holiday consumption might be categorized as Off-Peak
regardless of the day it falls on
TOU Map Template
If special holiday TOU categorization is required by the rate,
the TOU Map Template must reference:
The Work Calendar that defines when holidays start and end
Either of the following:
- the Holiday TOU code for consumption on the holidays
- the Holiday TOU Map Template that defines the TOU codes
to use for different times in the year

6-5

Copyright 2010, Oracle. All rights reserved.

TOU Template Interval Size

A TOU template's interval size (SPI)
controls the values allowed in the
Start and End Times
A template can be used to generate
TOU data for TOU maps whose SPI
is divisible by the template's SPI
For example:
A 60 minute template can be
used to generate TOU data for
60 minute, 15 minute, 5
minute, TOU maps
This means separate templates are
not needed for every SPI

6-6

TOU Map Template

Copyright 2010, Oracle. All rights reserved.

These times
must be in units
of the interval
size (e.g., 10:00,
10:15, 10:30, )

TOU Map Type SPI (Seconds Per Interval)

Recall that a MC's MC type defines its interval size (SPI)

The SPI controls the times on the MC's measurements

Similarly, every TOU map references a TOU map type that defines its interval size

The SPI controls the times on the TOU map's TOU data
The SPI of a TOU map must divide evenly into the SPI of any MC that uses the map
(because the system joins the date/time of the measurement to the date/time of the TOU
data)
This means that it is OK to use a 15 minute TOU map with a 60 minute MC

However, it is not OK to have a 60 minute TOU map used with a 15 minute MC

because the join will miss 3 out of 4 measurements

6-7

TOU Map: 6593920101

MC ID: 12391010192

Date/Time

TOU
Code

Date/Time

Final
Consum.

1-Jan-10 3:00pm

PEAK

1-Jan-10 3:00pm

14.678

1-Jan-10 3:15pm

PEAK

1-Jan-10 4:00pm

29.12

1-Jan-10 3:30pm

PEAK

1-Jan-10 5:00pm

12.12

1-Jan-10 3:45pm

PEAK

1-Jan-10 6:00pm

17.16

1-Jan-10 4:00pm

PEAK

Copyright 2010, Oracle. All rights reserved.

Any Final Measurement Value Can Be TOU

Mapped
Recall that a final measurement for an interval can contain
many derived quantities

TOU Map: 6593920101

MDM
1
Load Initial
Measurements
2

A TOU map can be applied

to aggregate any quantity
on a final measurement

Date/Time

TOU
Code

1-Jan-10 3:00pm

PEAK

1-Jan-10 4:00pm

PEAK

1-Jan-10 5:00pm

PEAK

Validate Edit Estimate

Initial Measurements
Date/Time

As
Measured

Loss
Adjusted

Thermal
Unit

Normal
CCF

% of
Normal

UOM: CCF
SQI: nil

UOM: CCF
SQI: Loss
Adjusted

UOM: BTU
SQI: nil

UOM: CCF
SQI: Normal

UOM: %
of Normal
SQI: nil

1-Jan-10 3:00pm

10

10.1

10.11

10

100%

1-Jan-10 4:00pm

15

15.15

15.165

10

150%

1-Jan-10 5:00pm

10

10.1

10.11

10

100%

3
Create Final
Measurements
4
Calculate Usage

6-8

Copyright 2010, Oracle. All rights reserved.

Not Just For Bill Determinants

While the requirement to aggregate interval consumption into TOU periods is
the principal reason behind TOU maps, the system has many zones that
display interval consumption using TOU periods

These visual metaphors make it easier to understand the vast amounts

of interval data
This chapter exposes you to these zones and the objects behind them

Foreshadowing: TOU maps can be used to

perform certain types of VEE rules as
grouping consumption into time-of-use
periods is a good way to determine average
consumption. A future chapter describes this
in more detail.
6-9

Foreshadowing: All of the TOU concepts

described in this chapter are used when
bill determinants are aggregated into TOU
periods. A future chapter describes how
bill determinants are calculated.

Copyright 2010, Oracle. All rights reserved.

Time-of-Use Tables and MOs

Copyright 2010, Oracle. All rights reserved.

Defines the TOU codes that can

be referenced on a template
and on a map's TOU data
TOU Group
CH, X

Defines the rules used by

the system to periodically
generate a map's TOU
data

The standard Fallback /

Override pattern is used
Discussed later in this course.
For now, understand a TOU map
can have its TOU codes
dynamically changed when
special events occur (like a
critical peak period)

TOU Map
Template
CH, X

TOU
Group /
TOU
Fallback
Override

TOU Map Type

CH, X

TOU Map
ST, CH, X
Time Zone

Valid TOU
Template

Defines the override TOU map

templates that can be specified
on individual TOU maps

TOU Data
CH, X

Controls the seasonal time shifts in the

TOU data (note well - a TOU map can
be used across time zones that have
the same seasonal time shifts)

6 - 11

TOU Map /
Dynamic Option

TOU

Defines its color on

the various graphs

Copyright 2010, Oracle. All rights reserved.

Dynamic
Option

Legend

??? This is an index

organized table (IOT)
as is final
measurement; this
allows VERY FAST
summarization of
final measurements
into TOU periods

Trans. Data
Admin Data
Master Data
FW Data
MO Boundary
Described
elsewhere
ST - Status
CH - Characteristics
X - CLOB

BO Definition

Copyright 2010, Oracle. All rights reserved.

BO Definition
Standard pattern where the "type"
references its BO and the BO of
the related master data BO

Business
Object

TOU Map

Option

TOU Data

TOU Map
Type

Business
Object

TOU Group

Business
Object

TOU Map
Template

Business
Object

The TOU Data BO is defined

in a TOU Map BO option

Legend
Tran. Data
Admin Data
Master Data
FW Data

6 - 13

Copyright 2010, Oracle. All rights reserved.

Practice (30 Minutes)

In this practice, you will create a TOU map template, a TOU map type, and a
TOU map for the requirement shown below

Note - you can use the TOU group in demo called On / Off / Shoulder,
Summer / Winter rather than set up TOU codes
The next slides provide a summary of the tasks

FYI - this is a map used for customers

with electric cars to encourage them to
plug their cars in after midnight

6 - 14

Copyright 2010, Oracle. All rights reserved.

6-1 Data Overview

5

MC Type
TOU Map
Template

XML

Fallback
Override

2
TOU Map
ST, CH, X

TOU Map Type

An MC type has a FK to the

default TOU map used on the
360 zones that show TOU data

4
TOU Data
CH, X

Legend
Trans. Data
Admin Data
Master Data
FW Data
MO Boundary
Described
elsewhere
ST - Status
CH - Characteristics
X - CLOB

6 - 15

Copyright 2010, Oracle. All rights reserved.

6-1 Solution
Add A TOU Map Template

1.1

TOU Map Template

Description

Identifying BO

RW-ECAR

RW - Electric Car

Time of Use Map Template

6 - 16

Copyright 2010, Oracle. All rights reserved.

Navigate to Admin / T / + TOU Map

Template to add a TOU map
template that holds the line loss
adjustment amount (prefixed with
your initials)

6-1 Solution
Add A TOU Map
Template

1.2

Here's how the template should look

??? Bug note - this should require just

2 periods 05-01 to 10-31 and 11-01 to
04-30 and this doesn't work so we
had to start the template on 01-01
and end on 12-31

6 - 17

Copyright 2010, Oracle. All rights reserved.

6-1 Solution
Add A TOU Map Type
2

TOU Map Type

Description

Identifying BO

RW-ECAR

RW - Electric Car

Time of Use Map Type

6 - 18

Copyright 2010, Oracle. All rights reserved.

Navigate to Admin / T / + TOU Map

Type to add a TOU map type
(prefixed with your initials)

6-1 Solution
Add A TOU Map
3

Navigate to Usage - TOU Map + to add a TOU map. When

prompted, select your TOU Map Type and enter a description
(prefixed with your initials)

6 - 19

Copyright 2010, Oracle. All rights reserved.

6-1 Solution
Generate TOU Data
4.1

After adding the TOU map, you will be transferred to the TOU map
portal. Click the Generate button to generate TOU data for your
map.

Click the Generate

TOU Map Data button

Enter the Start Date/Time and End

Date/Time, use 01-01-2010 12AM
and 02-01-2010 12AM. Then click
Generate.

6 - 20

Copyright 2010, Oracle. All rights reserved.

6-1 Solution
Examine The TOU Data
4.2

After generating the TOU data, you will be returned to the TOU
map portal

??? Bug note - 12am on each day is

being populated with the template's
default TOU code

6 - 21

Copyright 2010, Oracle. All rights reserved.

6-1 Solution
Update Your MC Types
6

MC Type
RW-E-KWH-CON-60

This class only applies a the TOU map to this MC type (so
it's the only one that needs to be updated)

Specify the TOU map that should default on the various 360
graphs (if this is left blank, the graphs will show nothing and
users will have to select a TOU map in the zone)

6 - 22

Copyright 2010, Oracle. All rights reserved.

6-1 Solution
Use TOU-Oriented 360 Zones
7

Open the 360 View - Measuring Component and open the Time of Use
Overlay (we can skip the TOU by day until we have more measurements)

Note, this data defaults as per the

number of hours on the MC type.
Make sure the Start Date/Time is
1/1/10 or later as there is no TOU
data before this date.

6 - 23

Copyright 2010, Oracle. All rights reserved.

A Performance Note

Copyright 2010, Oracle. All rights reserved.

Refresher
Earlier, we said the following:
TOU Map: 6593920101

MDM
1
Load Initial
Measurements
2

A TOU map can be applied

to aggregate any quantity
on a final measurement

Date/Time

TOU
Code

1-Jan-10 3:00pm

PEAK

1-Jan-10 4:00pm

PEAK

1-Jan-10 5:00pm

PEAK

Validate Edit Estimate

Initial Measurements
Date/Time

As
Measured

Loss
Adjusted

Thermal
Unit

Normal
CCF

% of
Normal

UOM: CCF
SQI: nil

UOM: CCF
SQI: Loss
Adjusted

UOM: BTU
SQI: nil

UOM: CCF
SQI: Normal

UOM: %
of Normal
SQI: nil

1-Jan-10 3:00pm

10

10.1

10.11

10

100%

1-Jan-10 4:00pm

15

15.15

15.165

10

150%

1-Jan-10 5:00pm

10

10.1

10.11

10

100%

3
Create Final
Measurements
4
Calculate Usage

6 - 25

Copyright 2010, Oracle. All rights reserved.

The Base-Package Has A "Covering Index"

To speed the retrieval of measurements, the base-package has a covering index that
contains the As Measured value and the first 2 derived values
You can still TOU map the remaining 8 derived values, but the database will not be able
to use the covering index for these and will therefore retrieve the derived value from the
"heap" (and this is not as fast as retrieving the values from the covering index)
If this TOU mapping will be done for a limited number of usage subscriptions, you don't
have to do anything (i.e., it's OK to go to the heap for idiosyncratic TOU mapping)
If this TOU mapping will be done for large volumes of usage subscriptions, you should
change the covering index to include the additional derived values
The covering index includes
the As Measured and the
first 2 derived values

6 - 26

Date/Time

As
Measured

Loss
Adjusted

Thermal
Unit

Normal
CCF

% of
Normal

UOM: CCF
SQI: nil

UOM: CCF
SQI: Loss
Adjusted

UOM: BTU
SQI: nil

UOM: CCF
SQI: Normal

UOM: %
of Normal
SQI: nil

1-Jan-10 3:00pm

10

10.1

10.11

10

100%

1-Jan-10 4:00pm

15

15.15

15.165

10

150%

1-Jan-10 5:00pm

10

10.1

10.11

10

100%

Copyright 2010, Oracle. All rights reserved.

Review Questions

6 - 27

Copyright 2010, Oracle. All rights reserved.