05 Measurement

5
Measurements
Copyright 2010, Oracle. All rights reserved.
Initial versus Final Measurements versus Usage

MCs have initial measurements that
record how much was consumed.
MDM
1
Load Initial
Measurements
Each initial measurement is subject to

validation, editing (if they are obviously
wrong), and estimation (if they are missing).
The VEE logic can override the initial
measurements.
Initial measurements are normalized into
final measurements where each final
measurement is for a specific date and time.
The final measurements are periodically

transformed into more concise and palatable
usage (also known as bill determinants) for
the subscribing systems. In this example, a
time-of-use map is applied to the final
measurements for an entire month.
5-2
Date/Time
Initial
Consumption
1-Jan-10 3:00pm
15.1
1-Jan-10 3:15pm
missing
1-Jan-10 3:30pm
14.3
Date/Time
Final
Consumption
1-Jan-10 3:00pm
15.1 kWh
1-Jan-10 3:15pm
12.3 kWh
1-Jan-10 3:30pm
14.3 kWh
UOM / TOU
Usage
kWh / On peak
1200.1 kWh
kWh / Off peak
401.2 kWh
kWh / Shoulder
654.8 kWh
Validate Edit Estimate

Initial Measurements
3
Create Final
Measurements
4
Calculate Usage
VEE Is Discussed Later

MDM
Load Initial
Measurements
For the purposes of this chapter, assume

that the VEE process can change initial
measurements and create exceptions when
the initial measurements are wrong.
The VEE process is described in the next
chapter.
Initial
Consumption
1-Jan-10 3:00pm
15.1
1-Jan-10 3:15pm
missing
1-Jan-10 3:30pm
14.3
Date/Time
Final
Consumption
1-Jan-10 3:00pm
15.1 kWh
1-Jan-10 3:15pm
12.3 kWh
1-Jan-10 3:30pm
14.3 kWh
UOM / TOU
Usage
kWh / On peak
1200.1 kWh
kWh / Off peak
401.2 kWh
kWh / Shoulder
654.8 kWh

Create Final
Measurements
Calculate Usage
5-3
Date/Time
One Initial Measurement Can Create Many

Final Measurements
A single initial measurement may
contain many "readings"
MC ID: 1239101
MDM
IMD ID: 12391011912

Date/Time
Consumption
1-Jan-10 3:00pm
15
1-Jan-10 4:00pm
20
1
Load Initial
Measurements
2

MC ID: 1239101
3
Create Final
Measurements
Date/Time: 1-Jan-10 3:00pm

Consumption: 15 kWh
4
Calculate Usage
MC ID: 1239101
Consumption: 20 kWh
5-4
Terminology: The acronym IMD (initial

measurement data) refers to an initial
measurement for a MC
A separate final measurement is

created for each interval on an IMD
(e.g., if an IMD contains 24 hours of
15 minute readings, 96
measurements will be created)
Terminology: The terms
measurement, final measurement, and
final consumption are synonyms.
Pre and Post VEE Quantities

IMDs contain the original and final versions of how much was
consumed
Terminology: Pre VEE quantities are the
consumption derived from the
measurements recorded by the head-end
system / meter reader
MC ID: 1239101
IMD ID: 12391011912
VEE estimated
missing interval
VEE smoothed a
spike
5-5
Date/Time
Pre VEE
Consumption
Post VEE
Consumption
1-Jan-10 3:00pm
14.678
14.678
1-Jan-10 4:00pm
missing
20
1-Jan-10 5:00pm
13.12
13.12
1-Jan-10 6:00pm
150.12
14.12
Terminology: Post VEE quantities can

differ from their Pre VEE counterparts
when:
1) VEE rules have changed the quantities
because they are missing or obviously
wrong
2) A user has made manual changes including applying mathematical functions
Final measurements are created using the
post VEE quantities
Measurements Have Conditions

A measurement's condition flag indicates its source and quality
MC ID: 1239101
IMD ID: 12391011912
Date/Time
1-Jan-10 3:00pm
Pre VEE
Consumption
Pre VEE
Condition
14.678
1-Jan-10 4:00pm
Post VEE
Consumption
Post VEE
Condition
regular
15.1
regular
missing
20
estimated
1-Jan-10 5:00pm
13.12
regular
13.41
regular
1-Jan-10 6:00pm
150.12
regular
14.12
estimated
Notice it's the pre VEE condition that

indicates the interval is missing and that
the post VEE condition highlights that it
was estimated
Notice that the head-end indicated the
spike was fine (pre VEE is regular), but the
VEE process smoothed it
MC ID: 1239101
A final measurement's condition is copied
from the post VEE condition
Consumption: 14.12 kWh

Condition: estimated
5-6
Final Measurements Can Be Updated

MC ID: 1239101
MDM
IMD ID: 12391012818

Date/Time
Consumption
1-Jan-10 3:00pm
22
1-Jan-10 4:00pm
12
1
Load Initial
Measurements
2

MC ID: 1239101
3
Create Final
Measurements

Consumption: 22 kWh
4
Calculate Usage
MC ID: 1239101
Consumption: 12 kWh
5-7
If final measurements are wrong (for

whatever reason), a new IMD is
created to correct them. This new IMD
contains the corrected consumption.
After the IMD is VEE'ed, the existing
final measurements are updated with
the newly calculated consumption.
Foreshadowing: the unique identifier

(prime key) of the final measurement
table is MC ID + Date/Time; this means
that it is impossible for more than one
final measurement to exist for a MC for
a given date/time
Note well: for most MCs, an IMD must
be created and completed to add or
update measurements as there is no UI
that allows users to directly edit final
measurements
Practice 5-1
(15 Minutes)
In this practice, you will examine initial measurement data and
final measurements for an interval measuring component.
5-8
Final Measurements May Have Derived Values
Deriving Other Values

Final measurements can record up to 10 derived values in
addition to the "as measured" value
MDM
Date/Time
Consumption
1-Jan-10 3:00pm
10
1-Jan-10 4:00pm
15
1-Jan-10 5:00pm
10
Date/Time
As
Measured
Loss
Adjusted
Thermal
Unit
UOM: CCF
SQI: nil
UOM: CCF
SQI: Loss
Adjusted
UOM: BTU
SQI: nil
1-Jan-10 3:00pm
10
10.1
10.11
1-Jan-10 4:00pm
15
15.15
15.165
1-Jan-10 5:00pm
10
10.1
10.11
1
Load Initial
Measurements
2

3
Create Final
Measurements
4
Calculate Usage
5 - 10
Notice how this MC's final

measurements have 2
derived values
The Derived Values Can Be More Interesting

The derivation formula for each value on a final measurement is
held in an algorithm and therefore can derive anything
MDM
Date/Time
Consumption
1-Jan-10 3:00pm
10
1-Jan-10 4:00pm
15
1-Jan-10 5:00pm
10
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%
1
Load Initial
Measurements
2

3
Create Final
Measurements
4
Calculate Usage
5 - 11
More than consumption

quantities can be derived
Practice 5-2
(10 Minutes)
In this practice, you will examine a measuring component whose
final measurements have derived values.
5 - 12
Scalar Measurements Have IMDs and Measurements

Too
Review: Interval versus Scalar MCs

An interval MC is measured at predictable
boundaries as defined by the MC type's SPI
(seconds per interval)
Measurements are only allowed on

these time boundaries
An example of a consumptive interval MC
that is read every 15 minutes (SPI = 900)
Measurements for a scalar MC are allowed

at any point in time
In practice, scalar MCs are read

monthly / bimonthly / quarterly /
An example a subtractive, scalar MC
5 - 14
Date
Time
kWh
1/1/2010
10:00 AM
1/1/2010
10:15 AM
10
1/1/2010
10:30 AM
1/1/2010
10:45 AM
...
...
...
Date
Time
kWh
1-Jan-10
7:00 AM
31-Jan-10
10:23 AM
1000
2-Mar-10
6:41 PM
1789
1-Apr-10
10:45 AM
2700
...
...
...
Scalar MCs Have Initial and Final Measurements

Too
MDM
Scalar MCs have initial
measurements too. It's just that
the volumes are lower.
Scalar MCs are VEE'ed too. It's

just that the rules are simpler.
Load Initial
Measurements
2
Scalar MCs have final

measurements too
5 - 15
Initial
Consumption
2-Jan-2010
900
31-Jan-2010
1500
Date/Time
Final
Consumption
31-Jan-2010
600 kWh
Date/Time
Usage
31-Jan-2010
600 kWh

Usage for subtractive, scalar

measurements typically contains
that start reading, the end
reading, and the resultant
consumption (which can have a
derived values too)
Date/Time
Create Final
Measurements
4
Calculate Usage
IMDs For Subtractive MCs Have Even More

Quantities
IMDs for subtractive MCs contain the start and stop readings
and the pre and post VEE consumption
MC ID: 1239101
IMD ID: 12391011912
Date/Time
Start
Reading
Stop
Reading
Pre VEE
Consumption
Pre VEE
Condition
Post VEE
Consumption
Post VEE
Condition
1-Jan-10 3:00pm
1500
1500
regular
1515
regular
2-Feb-10 4:11pm
1500
2100
600
regular
606
regular
3-Mar-10 5:22pm
2100
2900
800
regular
808
regular
1-Apr-10 1:00pm
2900
3500
600
regular
606
regular
5 - 16
Practice 5-3
(20 Minutes)
In this practice, you will examine initial measurement data and
final measurements for a scalar, subtractive measuring
component.
5 - 17
The Source Of IMDs
IMDs Can Be Interfaced From Head-End Systems

MDM
Load Initial
Measurements
The various Smart Grid Gateway products
supply the integration layer to create IMDs
from the "payloads" supplied by their
respective head-end systems. This is the
most common way IMDs are added to the
system.
The MDM-Advanced class describes how
this is implemented
Initial
Consumption
1-Jan-10 3:00pm
15.1
1-Jan-10 3:15pm
missing
1-Jan-10 3:30pm
14.3
Date/Time
Final
Consumption
1-Jan-10 3:00pm
15.1 kWh
1-Jan-10 3:15pm
12.3 kWh
1-Jan-10 3:30pm
14.3 kWh
UOM / TOU
Usage
kWh / On peak
1200.1 kWh
kWh / Off peak
401.2 kWh
kWh / Shoulder
654.8 kWh

Create Final
Measurements
Calculate Usage
5 - 19
Date/Time
IMDs Can Be Loaded Real-Time By Supplying An XML Document

A BPA script exists in MDM demo that
allows a user to paste an IMD XML
document to add IMD(s)
MDM
The embedded help provides a sample
of the XML format to be used
Date/Time
Initial
Consumption
1-Jan-10 3:00pm
15.1
1-Jan-10 3:15pm
missing
1-Jan-10 3:30pm
14.3
As always, the IMD(s) must be VEEed

before final measurements are created
5 - 20
IMDs Can Be Created Via Functions

MDM
The MDM-Advanced class describes how
an implementation can created additional
functions.
Many of the 360 View zones allow

users to Select Functions
When the user clicks OK, an IMD is

created (and it must be VEEed before
final measurements are created)
Executing a function
starts a business process
that prompts for
additional information
5 - 21
Date/Time
Initial
Consumption
1-Jan-10 3:00pm
15.1
1-Jan-10 3:15pm
missing
1-Jan-10 3:30pm
14.3
IMDs Are Created To Estimate Consumption

When the system detects that an MC is missing final measurements, it creates
an IMD
This type of IMD is referred to as an estimated IMD

VEE is discussed in a future chapter. For now, understand that a VEE rule
estimates the IMD's consumption
In other words, the processes that detect missing measurements do

NOT themselves estimate consumption. Rather, these detection
processes simply create an IMD and let the estimation logic embodied in
a VEE rule estimate the consumption for the IMD's time-period
The detection of missing measurements occurs at different points in time for
interval and scalar MCs:
For interval MCs, a dedicated batch process exists (described on the

next slides) as most implementations prefer to create the estimated
IMDs within a few days of the measurement date
For manually read scalar MCs, a usage calculation rule (described in a

later chapter) creates the IMD if it cannot find a measurement and it has
been given permission to estimate
5 - 22
Interval MC Types
The batch process that detects missing consumption for
interval MCs is described in the MDM Advanced class
For now, understand that it uses two elements on interval
MC types:
If an MC has contiguous final measurements

on/after (current date/time - Hours Before Estimate)
the MC is not estimated
If the MC is subject to estimation, measurements

will be estimated through the current date/time (Hours Before Estimation - Number of Hours to
Estimate)
The upcoming slides provide examples
5 - 23
Estimation Horizon Examples

January
Today
1
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
Legend
Hours Before Estimation: 72
Final measurement exists
Contiguous consumption exists through 7-Jan

therefore estimation will not occur because
contiguous consumption exists after 6-Jan.
IMD will be created that

contains estimated
consumption
January
Today
1
No final measurement exists
10
11
12
13
14
15
16
17
18
19
20
21

Contiguous consumption exists through 2-Jan
therefore estimation will occur because contiguous
consumption does not exist through 6-Jan
Consumption will be estimated for missing intervals from
2-Jan through the current time - 48 hours (i.e., Hours
Before Estimation - Number of Hours to Estimate)
Note, the only way this example could happen (where 5 days are being
estimated at a go) is if the implementation did not run the periodic estimation
process after 5-Jan (if this batch job had been run on schedule, the
consumption would have been estimated each day)
5 - 24
22
23
24
25
26
27
28
29
30
31
IMDs Are Created For Each Missing Period

January
Today
1
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31

There is consumption on the 5-Jan, but
contiguous consumption only exists through 2-Jan
In this scenario, two IMDs will be created:
- one for the intervals in the period between 3-Jan to 4-Jan
- another for the intervals in the period between 6-Jan to 7-Jan
In other words, separate IMDs are created for each contiguous
period with missing final measurements
Legend
Final measurement exists
No final measurement exists
IMDs will be created that
contain estimated
consumption
5 - 25
Practice 5-4
(25 Minutes)
In this practice, you will create initial measurement data for your
measuring component, and "complete" the initial measurement
data, in turn creating final measurements.
5 - 26
Interval Profiles
5 - 27
When Many Rules Have The Same Eligibility

Criteria
Assume:
Different types of service points have different consumption
profiles, for example:
A single-family home located in a temperate climate consumes
differently than one located in a cold climate
A bakery consumes differently than a school
A MC exists for each consumption profile of interest to an

implementation; the shape of each MC's measurements is the
consumption profile
Users can override consumption for a customer by supplying a
total consumption amount for a time-period and have it
"intervalized" using the customer's profile (e.g., the total
consumption for a temperate-based residential customer would
be used in different time periods than that for a bakery)
In the next practice, you will add consumption for your MC using a
profile (rather than straight lining it). After this practice is complete,
consumption profiles will be explained in more detail
5 - 28
Practice 5-5
(15 Minutes)
In this practice, you will create initial measurement data for your
measuring component based on a consumption profile.
5 - 29
Set Up A Factor
A factor is used to implement interval profiles (the term factor is
intentionally generic as factors can be used for many other
purposes as will be described in future chapters)
MC ID: 182829182192
Factor: kWh Interval Profile
Type of Characteristic: Consumption Profile
Source of Characteristic Value: Service Point
Characteristic
Value
Small
Commercial
Residential
Profile Measuring Component ID

182829182192
MC ID: 393938293929
393938293929
This MC's final measurements are used as the shape

of the consumption profile if SP is defined as using a
consumption profile of Small Commercial
5 - 30
When The Factor Is Used

When this factor is used, the system
retrieves the designated characteristic
type's value using the Source of
Characteristic Value
Factor: kWh Interval Profile

Type of Characteristic: Consumption Profile
Source of Characteristic Value: Service Point
Electric SP
Address: 15 Ocean Ave
Consumption Profile: Residential
Characteristic
Value
Small
Commercial
Residential
For example, if the MC is installed at

this SP, the Residential characteristic
value is retrieved
The system then finds the MC ID
associated with the Residential
characteristic value
Profile Measuring Component ID

182829182192
393938293929
MC ID: 393938293929
This MC's final measurements are then used as the

shape of the curve for this SP
5 - 31
Practice 5-6
(10 Minutes)
In this practice, you will look at the interval profile that was used to
form the shape of the interval consumption created in the prior
exercise.
5 - 32
Review Questions
5 - 33

05 Measurement

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

05 Measurement

Hochgeladen von

Copyright:

Verfügbare Formate

5

Copyright 2010, Oracle. All rights reserved.

Initial versus Final Measurements versus Usage

Each initial measurement is subject to

The final measurements are periodically

kWh / Off peak

Validate Edit Estimate

Copyright 2010, Oracle. All rights reserved.

VEE Is Discussed Later

For the purposes of this chapter, assume

kWh / Off peak

Validate Edit Estimate

Copyright 2010, Oracle. All rights reserved.

One Initial Measurement Can Create Many

IMD ID: 12391011912

Validate Edit Estimate

Date/Time: 1-Jan-10 3:00pm

Copyright 2010, Oracle. All rights reserved.

Terminology: The acronym IMD (initial

A separate final measurement is

Pre and Post VEE Quantities

Terminology: Post VEE quantities can

Copyright 2010, Oracle. All rights reserved.

Measurements Have Conditions

Notice it's the pre VEE condition that

Consumption: 14.12 kWh

Copyright 2010, Oracle. All rights reserved.

Final Measurements Can Be Updated

IMD ID: 12391012818

Validate Edit Estimate

Date/Time: 1-Jan-10 3:00pm

Copyright 2010, Oracle. All rights reserved.

If final measurements are wrong (for

Foreshadowing: the unique identifier

Copyright 2010, Oracle. All rights reserved.

Final Measurements May Have Derived Values

Copyright 2010, Oracle. All rights reserved.

Deriving Other Values

Validate Edit Estimate

Copyright 2010, Oracle. All rights reserved.

Notice how this MC's final

The Derived Values Can Be More Interesting

Validate Edit Estimate

More than consumption

Copyright 2010, Oracle. All rights reserved.

Copyright 2010, Oracle. All rights reserved.

Scalar Measurements Have IMDs and Measurements

Copyright 2010, Oracle. All rights reserved.

Review: Interval versus Scalar MCs

Measurements are only allowed on

Measurements for a scalar MC are allowed

In practice, scalar MCs are read

Copyright 2010, Oracle. All rights reserved.

Scalar MCs Have Initial and Final Measurements

Scalar MCs are VEE'ed too. It's

Scalar MCs have final

Validate Edit Estimate

Usage for subtractive, scalar

Copyright 2010, Oracle. All rights reserved.

IMDs For Subtractive MCs Have Even More

Copyright 2010, Oracle. All rights reserved.

Copyright 2010, Oracle. All rights reserved.

The Source Of IMDs

Copyright 2010, Oracle. All rights reserved.