05 Measurement BO

5
Measurement
Review From The Fundamentals Course
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
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-3
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-4
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-5
Final Measurements Can Be Updated

(Via A New IMD)
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-6
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
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-7
Notice how this MC's final

measurements have 2 derived values
Measurement Tables and MOs
Defines the head-end for smart meters.

If not defined on the device, the fallback
from the device type is assumed.
Device
Device
Config.
UOM
X
MC Type
CH, X
TOU
X
Measurement
UOM/TOU/SQI
SQI
X
MC
Algorithm
A MC has final
measurements
Recall that a measurement can have multiple

derived values and each value is held in a
separate column on a measurement. A MC's
MC type defines the UOM/TOU/SQI of each of
the derived values and the algorithm that
calculates each.
An extendable
lookup contains
the valid
condition codes
5-9
Device Type
Service Provider
CH, X
Override
Processing
Method
CH, X
Fallback
Processing Role
Valid
Service
Provider
A service provider has different processing methods for each

role they play a part in. A processing method defines the type
of BO the system should create when the service provider
sends a given type of information (where the type of
information is defined by the processing role). Note, there are
other types of processing methods described later that control
how the system sends information to a service provider.
Initial Meas.
Data (IMD)
ST, CH, X
The measured quantities reside in XML lists in the CLOB

Final measurements refer to their
originating IMD (as an audit).
Measurement
ST, CH, X
Foreshadowing: the data model allows

a measurement to exist that does not
reference an IMD. These types of
measurements are typically not linked
to physical MCs. Rather, they are
used to hold aggregation totals.
Legend
Trans. Data
Admin Data
Master Data
Condition
Measurement
Log
CH, X
A measurement log is not created

when a measurement is first
inserted, only if it is subsequently
updated. The log contains the
before and after image of the
measurement.
FW Data
MO Boundary
Described
elsewhere
ST - Status
CH - Characteristics
X - CLOB
BO Definition
BO Definition
The MC type defines the BO
of its measurement instances
Measurement
Business
Object
MC
Option
IMD
MC Type
The source of an IMD's BO depends on the source of the IMD:

- If the IMD is created by a user manually, the BO is defined in an MC BO option.
- If the IMD is created because the system determines it is time to estimate
consumption, the BO is defined in a different MC BO option.
- If the IMD is sent from a head-end system, the type of BO to create is defined
on one of the service provider's "processing methods".
5 - 11
Business
Object
Legend
Tran. Data
Admin Data
Master Data
FW Data
SGG Preview: The Seeder Creates Initial Load

of IMDs
SGG Initial Load IMD

Architecture
Record Type~Record Version~Time
Stamp~PremiseID~ESIID~Provisioned
~ MeterID~Purpose~Commodity~
Units~CalculationConstant~Interval~
Count~Date~FirstIntervalDateTime~
Data
Record Type~Record Version~Time
Stamp~PremiseID~ESIID~Provisioned
~ MeterID~Purpose~Commodity~
Units~CalculationConstant~Interval~
Count~Date~FirstIntervalDateTime~
Data
JMS Queue(s)
OSB
The L+G SGG includes the OSB

configuration that polls for, parses, and
transforms the L+G payloads into SGG
service format and places each atomic
service call into a JMS queue
<measurement>
<measurement>
<initialMeasurement>
</measurement>
</measurement>
</initialMeasurement>
<measurement>
<measurement>
<deviceActivity>
</measurement>
</measurement>
</deviceActivity>
F1
JMS
Client
The OUAF consumes the

entries in the JMS queues
and invokes the
respective BO services in
parallel
<action>add</action>
<bo>D1-IMDSeeder</bo>
<initialMeasurement>
<channel>29101</channel>
<measurements>
<start>2010-03-14
12:15PM</start>
<mL>
<q>12.1</q>
<status>OK</status>
</mL>
<mL>
<q>36.5</q>
<status>OK</status>
</mL>
</measurements>
</initialMeasurement>
D1 - MD Foundation
D1-IMDSeeder BO
The D1-IMDSeeder BO has pre-processing

algorithms that:
- Derive the service provider (head-end) and MC
- Derive the start and end date / times
- Adjusts interval date / times to match the SPI and
performs under and over count checks (if allowed)
- Populates obviously missing intervals (if allowed)
- Determines the "real" BO that should be created as
the seeder is just a dummy BO for initial validation
If fatal problems are detected during the D1-IMDSeeder's preprocessing algorithms (can't find MC, no interval date/times,
), a seeder BO is instantiated in the Error state. Users can
reprocess these or discard as appropriate.
5 - 13
The JMS queue entries are

configured to invoke the add
D1-IMDSeeder BO
(regardless of the head-end)
D3 - SGG L+G
D3-L&GInitLoadIMD BO
A Demo Script Invokes The Seeder

A BPA script exists in demo that allows a user to paste an IMD XML document and
then pass it to the IMD seeder. You will use this in the next practice. But before
we start the practice, we need to explain in a little more detail how some of the
pre-processing algorithms on the seeder use information in this XML document
<deviceIdentifierNumber>1232112</>
<initialMeasurementData>
<serviceProviderExternalId>L+G</>
<preVEE>
<mcIdN>122</>
<stDt>2010-03-14-12.00.00/stDt>
<enDt>2010-03-15-12.00.00/enDt>
<msrs>
<mL>
<s>1</s>
<q>12.12</q>
</mL>
<mL>
<s>2</s>
<q>6.3</q>
</mL>
</msrs>
</preVEE>
</initialMeasurementData>
D1 - MD Foundation
D1-IMDSeeder BO
D3 - SGG L+G
D3-L&GInitLoadIMD BO
5 - 14
How The Seeder's Derive Head-End / MC Algorithm Works

1
The system finds a service provider with

an external ID equal to the one provided.
<preVEE>
<mcIdN>122</>
<stDt>2010-03-14-12.00..00/stDt>
<enDt>2010-03-15-12.00..00/enDt>
<msrs>
<mL>
<s>1</s>
<q>12.12</q>
</mL>
<mL>
<s>2</s>
<q>6.3</q>
</mL>
</msrs>
</preVEE>
5 - 15
Service Provider
Device Identifier
Type
Device
2
Device Identifier
The service provider defines the device

identifier type that is used to identify
devices when it sends measurements.
The algorithm uses this plus the supplied
deviceIdentiferNumber to find the device.
Note, if the unique ID of the device was
supplied this is used instead.
Device Config.
MC Identifier
Type
MC
MC Identifier
3
The service provider defines the MC
identifier type that is used to identify
channels when it sends measurements. The
algorithm uses this plus the supplied mcIdN
value to find the MC. Note, if the unique ID
of the MC is supplied, this is used instead.
How The Determine "Real" IMD BO Algorithm Works
Processing Role
Initial measurement creation
Service Provider
Processing
Method
BO
XML
The meter's head-end

Override
Method
Device
Device Config.
MC
MC Type
The system retrieves the processing method for the

service provider whose Processing Role is Initial
Measurement Creation.
It then checks if the channel's MC type has an
override processing method:
- If so, it uses the BO on the Override Method
- If not, it uses the default BO on the Processing
Method
Bottom line each head-end / MC type
combination can create a different IMD BO
5 - 16
Practice 5-1 (30 Minutes)

In this practice, you will update your devices / device types so you can add IMDs
and produce final measurements
The specific tasks include:
Create a service provider for the electric smart meter's head-end
Create a service provider for the water smart meter's head-end
A processing method that defines the type of IMD BO to create for the channels
will also be set up
A processing method that defines the type of IMD BO to create for the channels
will also be set up
Create "empty" VEE groups for your MCs
These are created as an IMD cannot be processed without a valid VEE group
The next slide provides a summary of the data that will be set up
Please break up into teams and follow the instructions on the upcoming slides
(there is no need to design anything at this point)
After the admin data is in place, continue following the instructions to create
IMDs for your electric MCs
5 - 17
5-1 Data Overview

3
Device Type
Fallback
Service Provider
Device
2
Device Config.
MC Type
5
Fallback
Fallback Vee
Group
4
VEE Group
Processing
Method
MC
This practice assumes

that all MCs of a given
type have the same VEE
group (an MC's fallback
VEE group is defined, per
VEE role, on its MC type)
6
Initial Meas.
Data (IMD)
Measurement
5 - 18
Processing Role
This practice assumes that all

devices of a given type have the
same service provider
Final measurements are created by

the "normalization" algorithm that's
executed in the IMD's final state. This
algorithm is only executed after the
IMD passes VEE rules. In this
example, our VEE group won't have
rules yet so the measurements on the
IMD will become the final
measurements.
Legend
Trans. Data
Admin Data
Master Data
FW Data
MO Boundary
Described
elsewhere
ST - Status
X - CLOB
5-1 Solution
Add Service Providers
Navigate to Admin / S / + Service Provider to add these
service provider (prefixing each with your initials)
Service Provider
Description
External Id
Identifying BO
RW-E
RW - Electric Service Provider
RWE
Head-End System
RW-W
RW - Water Service Provider
RWW
Head-End System
These are only used if

information is sent to this
service provider (leave
blank for now)
This value will be defined in the XML

document provided to the IMD seeder
These are the ID types that will be used

to find the device and MC for information
sent from the service provider
5 - 19
5-1 Solution
Add Processing Methods
2
Service Provider
Processing Role
Identifying Business Object
RW-W
Initial Measurement
Creation
How To Create MC Related

Information
RW-E
Initial Measurement
Creation
How To Create MC Related

Information
Use the Add link in the

Processing Methods zones
on the Service Provider
portal to add a new
processing method for each
of your service providers
Repeat for your electric
service provider
This is the IMD BO that will be created by

the seeder when this service provider
sends IMDs
Different types of IMD BOs can be created for different
types of MCs. For example, IMDs for scalar MC types would
require a different BO because the schema elements on
IMDs for interval and scalar MCs are very different.
5 - 20
SGG Preview: The future SGG products

will deliver head-end specific IMD
business objects
5-1 Solution
Update Your Device Types
3
Device Type
RW-E-CONGEN
RW-W-SMART-60
IMDs will only be added for these device types so these are
the only ones that need fallback Head-End Systems (recall
that the fallback head-end on a device's device type is used
if the device doesn't reference a head-end)
Specify your electric service provider on

your electric device type and your water
service provider on your water device type
5 - 21
5-1 Solution
Add VEE Groups
Navigate to Admin / V / + VEE Group to add these VEE
Groups (prefixing each with your initials)
VEE Group
Description
Identifying BO
RW-E-INIT
RW - Electric Init Load VEE
VEE Group
RW-W-INIT
RW - Water Init Load VEE
VEE Group
In a later chapter, VEE rules will be

added to these groups
5 - 22
5-1 Solution
Update Your MC Types
5
MC Type
RW-E-KWH-CON-60
RW-E-KWH-GEN-60
RW-W-LTR-60
IMDs will only be added for these MC types so these are the
only ones that need fallback VEE groups (recall that the
fallback VEE group on a MC's MC type is used if the MC
doesn't reference a VEE group)
Specify the your electric VEE group on

the electric MC types and the water VEE
group on the water MC type
Specify the number of hours to display on
the various 360 graphs (if this is left
blank, the graphs will show nothing)
5 - 23
5-1 Solution
Add IMDs For Your Electric Meter's Channels
Invoke this BPA script and then open the
embedded help to see the format of the XML
that should be supplied to the seeder
6.1
INSTRUCTOR: the next slide contains a

sample of the XML that can be distributed to
the students to save time
<preVEE>
<mcIdN>122</>
<stDt>2010-03-14-12.00..00/stDt>
<enDt>2010-03-15-12.00..00/enDt>
<msrs>
<mL>
<s>1</s>
<q>12.12</q>
<fc>501000</fc>
</mL>
<mL>
<s>2</s>
<q>6.3</q>
<fc>501000</fc>
</mL>
</msrs>
</preVEE>
D1 - MD Foundation
D1-IMDSeeder BO
D1 - MD Foundation
D1-InitialLoadIMDInterval
5 - 24
5-1 Solution
Paste The XML From Your Instructor
6.2
Your electric device's serial number
<devices>
<deviceIdentifierNumber>RW-E-CONGEN</deviceIdentifierNumber>
Your electric head-end's external ID
<serviceProviderExternalId>RWE</serviceProviderExternalId>
<preVEE>
Your consumed MC's channel ID
<mcIdN>RWA</>
<stDt>2010-01-01-00.00.00</stDt>
<enDt>2010-01-02-00.00.00</enDt>
<msrs>
<mL>
<s>1</s>
<q>12.12</q>
<fc>501000</fc>
</mL>
INSTRUCTOR: give this to the students, it's the XML
<mL>
for a day's worth of measurements for both the
<s>2</s>
consumption and generation MCs. The students
<q>6.3</q>
must change it to define their device identifier
<fc>501000</fc>
number and service provider external id. If they
</mL>
followed the instructions in the device practice, they
will not have to change the MC ids.

</msrs>
</preVEE>
<preVEE>
Your generated MC's channel ID
<mcIdN>RWB</>
</preVEE>
</devices>
5 - 25
<devices>
<preVEE>
<mcIdN>RWA</mcIdN>
<stDt>2010-01-01-00.00.00</stDt>
<enDt>2010-01-02-00.00.00</enDt>
<msrs>
<mL>
<s>1</s>
<q>1.2</q>
<fc>501000</fc>
</mL>
<mL>
<s>2</s>
<q>1.6</q>
<fc>501000</fc>
</mL>
<mL>
<s>3</s>
<q>1.4</q>
<fc>501000</fc>
</mL>
<mL>
<s>4</s>
<q>1.7</q>
<fc>501000</fc>
</mL>
<mL>
<s>5</s>
<q>1.5</q>
<fc>501000</fc>
</mL>
<mL>
<s>6</s>
<q>1.7</q>
<fc>501000</fc>
</mL>
<mL>
<s>7</s>
<q>2.1</q>
<fc>501000</fc>
</mL>
<mL>
<s>8</s>
<q>2.4</q>
<fc>501000</fc>
</mL>
<mL>
<s>9</s>
<q>1.9</q>
<fc>501000</fc>
</mL>
<mL>
<s>10</s>
<q>1.8</q>
<fc>501000</fc>
</mL>
<mL>
<s>11</s>
<q>1.7</q>
<fc>501000</fc>
</mL>
<mL>
<s>12</s>
<q>1.6</q>
<fc>501000</fc>
</mL>
<mL>
<s>13</s>
<q>1.8</q>
<fc>501000</fc>
</mL>
<mL>
<s>14</s>
<q>2.2</q>
<fc>501000</fc>
</mL>
<mL>
<s>15</s>
<q>2.5</q>
<fc>501000</fc>
</mL>
<mL>
<s>16</s>
<q>2.3</q>
<fc>501000</fc>
</mL>
<mL>
<s>17</s>
<q>2.8</q>
<fc>501000</fc>
</mL>
<mL>
<s>18</s>
<q>2.9</q>
<fc>501000</fc>
</mL>
<mL>
<s>19</s>
<q>3.2</q>
<fc>501000</fc>
</mL>
<mL>
<s>20</s>
<q>3.1</q>
<fc>501000</fc>
</mL>
<mL>
<s>21</s>
<q>1.9</q>
<fc>501000</fc>
</mL>
<mL>
<s>22</s>
<q>1.8</q>
<fc>501000</fc>
</mL>
<mL>
<s>23</s>
<q>1.7</q>
<fc>501000</fc>
</mL>
<mL>
<s>24</s>
<q>1.6</q>
<fc>501000</fc>
</mL>
</msrs>
</preVEE>
<preVEE>
<mcIdN>RWB</mcIdN>
<stDt>2010-01-01-00.00.00</stDt>
<enDt>2010-01-02-00.00.00</enDt>
<msrs>
<mL>
<s>1</s>
<q>0</q>
<fc>501000</fc>
</mL>
<mL>
<s>2</s>
<q>0</q>
<fc>501000</fc>
</mL>
<mL>
<s>3</s>
<q>0</q>
<fc>501000</fc>
</mL>
<mL>
<s>4</s>
<q>0</q>
<fc>501000</fc>
</mL>
<mL>
<s>5</s>
<q>0</q>
<fc>501000</fc>
</mL>
<mL>
<s>6</s>
<q>0</q>
<fc>501000</fc>
</mL>
<mL>
<s>7</s>
<q>.5</q>
<fc>501000</fc>
</mL>
<mL>
<s>8</s>
<q>.7</q>
<fc>501000</fc>
</mL>
<mL>
<s>9</s>
<q>1</q>
<fc>501000</fc>
</mL>
<mL>
<s>10</s>
<q>1.1</q>
<fc>501000</fc>
</mL>
<mL>
<s>11</s>
<q>1.5</q>
<fc>501000</fc>
</mL>
<mL>
<s>12</s>
<q>2</q>
<fc>501000</fc>
</mL>
<mL>
<s>13</s>
<q>1.8</q>
<fc>501000</fc>
</mL>
<mL>
<s>14</s>
<q>2.7</q>
<fc>501000</fc>
</mL>
<mL>
<s>15</s>
<q>2</q>
<fc>501000</fc>
</mL>
<mL>
<s>16</s>
<q>.5</q>
<fc>501000</fc>
</mL>
<mL>
<s>17</s>
<q>.3</q>
<fc>501000</fc>
</mL>
<mL>
<s>18</s>
<q>0</q>
<fc>501000</fc>
</mL>
<mL>
<s>19</s>
<q>0</q>
<fc>501000</fc>
</mL>
<mL>
<s>20</s>
<q>0</q>
<fc>501000</fc>
</mL>
<mL>
<s>21</s>
<q>0</q>
<fc>501000</fc>
</mL>
<mL>
<s>22</s>
<q>0</q>
<fc>501000</fc>
</mL>
<mL>
<s>23</s>
<q>0</q>
<fc>501000</fc>
</mL>
<mL>
<s>24</s>
<q>0</q>
<fc>501000</fc>
</mL>
</msrs>
</preVEE>
</devices>
5-1 Solution
Examine The IMDs
6.3
The BPA script will show a summary of what it did after you submit the XML
to the seeder (you should see that it created 2 "real" IMDs). Click Cancel as
you're finished if it looks like the above. If you see that the state of the IMDs
is Error, please consult your instructor as it means something in you XML
was not good.
5 - 26
5-1 Solution
Examine The IMDs
6.4
Navigate to 360 - MC and open the IMD Overlay zone for the consumed
channel and click Reload Initial Measurements Using Pre-VEE, you
should see this.
Click the IMD's info string to transfer to the IMD

portal where the IMD can be finalized
5 - 27
5-1 Solution
Create Final Measurements For The IMDs
6.5
Click Perform Additional Mapping to transition the

IMD through its lifecycle (including the final state
where the IMD's measurements are normalized into
final measurements)
There are many ways to see the final measurements:

- The IMD Lens zone will show final measurements if you toggle the Area Content
- The Measurements zone will show them
- Return to 360 - Measuring Component and check out the various zones
Repeat the above for the other channel's IMD
The upcoming slides will describe what happened when you clicked
Perform Additional Mapping
5 - 28
D1-IMDSeeder
The IMD Seeder BO

Lifecycle and Rules
Important: do not rely on the

lifecycle, rules or schemas on
the upcoming slides as they
may be out-of-date. Rather,
open the BO - Summary tab
for up-to-date information.
Recall that an IMD Seeder BO should only be

instantiated if critical validation errors occur; this means
this lifecycle only applies to IMDs with critical errors
(and notice that the initial state is Error meaning that
if such a BO is instantiated, it will be in the Error state).
Errors can be discarded or reprocessed.
Important: use the algorithm descriptions
for more information about what each of
these algorithms actually does
Notice that the IMD seeder has several

pre-processing rules that perform the
critical validation (and implementations
can add more if desired)
Date/time manipulation is described in
the next section
The next slide describes how this
algorithm determines the type of IMD BO
to create. For now, just understand that
it CHANGES the BO that's instantiated
to be whatever it finds.
This algorithm will try to create a new seeder; if it's not
successful, the attempt is rolled back and the initial
seeder remains in the error state; if it is successful, the
original seeder IMD will persist in the Reprocessed
state and a "new" real IMD will be created
5 - 30
Non Obvious Plug-in Spot

The pre-processing algorithm that
determines the "real" IMD BO to create does
this by invoking the determine processing
method(s) algorithms plugged in on the
processing method BO. This is done
because the data structure of the processing
methods differs depending on the role (some
roles allow different processes per MC type,
other per US type, others per) and only the
processing method's BO knows how to
interpret the structure of the information.
Service Provider
Business Object
Processing
Method
Device
Device Config
System Event
BO / Algorithm
MC
Determine Processing Method

Algorithm
IMD
5 - 31
Date / Time Manipulations
Standard versus Local Time

A device supplies IMDs with date / times in one of the following categories:
a) In local time
For example, during the shift from daylight savings to standard, there will be two 1 AMs
b) In standard time
For example, during daylight savings periods, an interval that ends at 3 PM local time will be sent
with a time of 2 PM
How do we know whether a device falls into category a) or b)?
Every device type defines its category (using Incoming Data Shift) and this can be overridden on a
specific device
Where do we care whether a device falls into category a) or b)?
A pre-processing algorithm (Perform Date/Time Adjustments and Undercount/Overcount Check) on

the IMD Seeder has the job of converting any date/times on the IMD into standard time. This
conversion is only done if the device falls into category a).
Final measurements are stored with two date/times: standard and local.
We use the standard date/time as part of the prime key of the measurement table (meaning there
cannot be more than 1 final measurement for a given date/time)
The presence of the local date/time field simplifies querying measurement data using local time:
5 - 33
Note - if a utility operates in multiple time zones, the measurements are stored in the standard time of
the time zone on the SP at which the device is installed
The zones on 360 View are in local time
The zones on the IMD Portal displays data in local time (???Except the Raw Data zone - this is
shown in standard time)
The Measurement zone on the Measurement portal shows both the local and standard date/time
Time Zone Definition

The system supports the configuration of an Olson DB time zone
name on the time zone admin data
The Olson DB contains the shift date/times for every time zone (and
then some) across the globe. The system uses this information to
shift times (e.g., convert from local to standard) when required.
It should be noted that there are no examples in the base-package of
converting information from one time zone into another
Note - these are NOT used by MDM (these

fields are only used by products that were
developed before the Olson time zone
code)
Users typically enter information in local time and do not have to
define the time-zone label when entering times. However, to refer to
the 1 hour each year where there are redundant times, the user must
suffix the time with the default (i.e., standard) time zone label
5 - 34
An example of
Olson codes from
the US - notice that
even the various
areas of Indiana are
covered
Date Time Manipulation Occurs During Seeder

Pre-Processing
One of the functions performed by this algorithm

is to shift measurements to standard time during
daylight saving periods.
Another function is performed if the IMD is supplied with

individual date/times on the measurements. This algorithm
will remove the individual date/times as these values can be
derived using the IMD's start date/time, the MC's SPI and the
sequence number of the measurement. This removal is done
to save space in the IMD.
5 - 35
Initial Load IMD BOs
Initial Load IMD BOs

Initial load IMD BOs are instantiated for IMDs sent from
external systems (these are the BOs that are determined by
the D1-IMDSeeder BO)
The following IMD BOs exist in the base:
Interval
Scalar
The various SGG products introduce child BOs of the above
that contain head-end specific business rules
In other words, the BOs that follow contain the schema
and core business rules that exist regardless of headend system
5 - 37
Scalar and Interval Initial Load IMD BOs Have The Same Schema
Intuitive / standard elements
The head-end / meter reading system

This raw group contains the data "as sent" from the
head-end / meter reading system (purely for audit)
Explained on the next slide
The trace group is populated by the VEE engine if
isTraceOn is true. It contains information to help "debug"
and performance tune the VEE rules. We recommend
disabling the trace when in production.
5 - 38
preVEE and postVEE Groups Are Identical

Note: notice how the
measurements are stored
in a CLOB (as XML)
These values can be supplied by the head-end /
meter reading system or defaulted by the
system if empty. Most are fairly intuitive.
These values are supplied by the head-end and

define the status codes for the entire set of
measurements (if any)
The measurement list <mL> contains an entry

for every measurement. The node names are
intentionally brief to save space. Note, the
date/time node <dt> is stripped out to save
space after the seeder completes it critical
validations.
5 - 39
Scalar and Interval Initial Load IMD BOs Have The Same
Lifecycle
A deferred monitor exists to prevent initial load IMDs from transitioning
through their lifecycle when they are created (as this would slow down
the load processes)
SGG child BOs may have head-end specific logic to populate the pre
VEE list as per the head-end's status codes (more about this later)
This state applies channel and installation multipliers to the pre VEE
quantities and copies pre VEE to post VEE. This invokes an algorithm
plugged in on the MC Type BO to do the multiplication (it can also
apply one or more factors to apply line loss adjustments (or other
types of pre VEE consumption changes)).
The enter invokes the VEE engine. After the VEE rule complete, the
IMD is transitioned to either Exception or Finalized. VEE is discussed
in the next chapter.
Creates a To Do entry (more about this later)
An "exceptioned" IMD can be forcibly completed (meaning the IMD will
be transitioned to the Finalized state without VEE)
The enter algorithms: 1) creates / updates final measurements using
the post VEE quantities (this algorithm invokes the Derive Other Value
algorithm(s) plugged in on the MC type instance), 2) transition UTs to
the subsequent changes state if UTs exist in the measurement period
5 - 40
Non Obvious Plug-in Spots
The enter algorithm that applies

channel and installation multipliers to
the pre VEE quantities invokes
another algorithm to do this work
based on whether the MC type is
interval or scalar. These algorithms
can also apply one or more factors to
adjust consumption prior to VEE.
Business Object
MC Type
MC
Measurement
UOM/TOU/SQI
IMD
BO / Algorithm
System Event
Algorithm
a. Calculate Interval Consumption

b. Calculate Scalar Consumption
The enter algorithm on an IMD's Finalized state
that creates / updates final measurements using
the post VEE quantities also invokes any derive
other value algorithms plugged in on the MC's MC
type. Recall this is done to derive values like CCF
to Therm or apply line loss or to calculate amount
conserved compared to normal or just about
anything else that can be derived.
5 - 41
Scalar and Interval IMDs Have Very Subtle

Differences
The schema and lifecycle of scalar and interval IMDs are
identical
The main differences between these BOs are the business
rules related to how consumption is calculated
5 - 42
SGGs Have IMD Child BOs

The various SGG products introduce child BOs of the initial load IMDs that
contain head-end specific business rules
In other words, the D1-owned BOs contain the schema and core business
rules that exist regardless of head-end system; the SGGs introduce child
BOs that extend these BOs with head-end specific logic
Parent BO: D1-InitialLoadIMDInterval
Pending
Additional
Mapping
BO: D3-InitialLoadIMDIntervalL+G
<includeBO
name="D1-InitialLoadIMD Interval"/>
<lgElement ... />
...
Status: Additional Mapping

System Event: Enter
Algorithm: L+G additional mapping
5 - 43
BO: D4-InitialLoadIMDIntervalEchelon
A child BO can introduce

elements to the schema
A child BO can introduce
algorithms to any state
Exceptions
Automated Retry
An IMD with a VEE exception typically causes a To Do entry to be
created:
Users are assigned To Do entries and work them one-by-one
But what if the exception is caused by a bad configuration or incorrect
master data, for example:
A factor used by high/low processing has not been configured
properly
The master data sync between the CIS and MDM had a bug and
channel identifiers were not populated correctly
In these scenarios, thousands of IMDs will have VEE exceptions (and
thousands of To Do entries will be created)
To deal with these types of scenarios, IMDs can be configured to retry
VEE every X minutes:
For example, if the factor is corrected when the IMD is next VEE'ed,
the To Do entries will be automatically completed and no one is the
wiser
5 - 45
Exceptions May Be Discarded, Retried or

Manually Resolved
An enter algorithm attempts to create a To Do entry highlighting the
VEE exception.
- If the implementation indicates the specific VEE exception is not
fixable (using the To Do Type / Message configuration), the To Do entry
is not created and the IMD is transitioned to the discard state.
- If a To Do entry is created, the IMD's Next Retry Date/Time is set to a
time X minutes in the future where X is on an algorithm soft parm.
A monitor algorithm transitions the IMD back to VEE when:
- The IMD has Automated Retry set to true (this is populated on the
IMD when it is first created)
- AND the IMD's Next Retry Date/Time is in the past
- AND the IMD's Retry Until Date/Time is in the future (this is
populated on the IMD when it is first created to prevent retry going on
forever)
- AND the To Do entry associated with the IMD is not in the Being
Worked state (if a user is working on the IMD, the system assumes it
should not retry)
An exit algorithm completes To Do entries

that were created (this will happen on
retries and discards)
5 - 46
Manual IMD BOs
Manual IMD BOs

The system does not allow users to change final
measurements directly
To change final measurements, users create a manual IMD
whose quantities reflect the desired final measurements
Note: functions initiated on the 360 - MC zones and on
the IMD lens zone create manual IMDs (e.g., Save as,
Create/Override, )
The following manual IMD BOs exist in the base:
Interval
Scalar
Recall that if an IMD is created by a user manually, the type
of BO is defined in an MC BO option
5 - 48
Manual IMD BOs Are Very Similar To Initial Load

IMD BOs
The schema for manual IMD BOs is identical
to initial load IMDs
The lifecycle is almost identical:
The Additional Mapping and Mapping

Error states do not exist for manual
IMDs (for obvious reasons)
There is no deferred monitor on the

initial state so it transitions immediately
into VEE Ready
The VEE ready state has a monitor

algorithm that will create a To Do entry
if the IMD is in this state for too long
While it doesn't impact the lifecycle or plugins, recall that a different VEE group can be
applied to a manual IMD than to an initial
IMD
Final measurements are created when the IMD is
finalized (just like initial load and manual IMDs)
5 - 49
Estimated IMD BOs
Estimated IMD BOs

If the system determines it's time to estimate consumption
for an MC, it does not create final measurements directly
Rather, the system creates an estimated IMD
When the IMD is finalized, final measurements are
created
The following estimated IMD BOs exist in the base:
Interval
Scalar
Recall that if an IMD is created by the system to estimate
consumption, the type of BO is defined in a BO option on the
related MC's BO
5 - 51
Estimated IMD BOs Are Almost Identical To

Manual IMD BOs
The schema for estimated IMD BOs is
identical to initial load IMDs
The lifecycle is very similar, the main
difference is that there is no Additional
Mapping state (this state is used on
initial load IMDs to perform additional
head-end specific mapping)
Notice that Estimated IMDs are subject to VEE
(this will be described in more detail in a few
slides)
Final measurements are created when the IMD is

finalized (just like initial load and manual IMDs)
5 - 52
Estimating Manually Read MCs versus Other MCs

The base-package assumes the following:
Manually read MCs are estimated when

usage (bill determinants) is calculated
5 - 53
When a real read cannot be found for the

usage period (this is described in the usage
chapter)
All other MCs are monitored by a batch

process that results in the creation of
estimated IMDs when missing intervals are
detected
An MC Type that is subject to

the periodic estimation process
The amount of time that must pass before an

interval is considered missing and the
number of hours of consumption that will be
estimated are defined on the MC type
The upcoming slides describe the periodic

estimation processing
These attributes do not exist for

manually read MC types
Periodic Estimation - Non Obvious Plug-in Spots
Business Object
Device
Device
Configuration
Devices whose MCs are subject to periodic estimation have a Monitor

algorithm plugged in on their Active state. This monitoring algorithm
retrieves the device's MC and invokes the Periodic Estimation algorithm
plugged in on their BO. Note - the device monitoring algorithm can be
configured to look at device configurations from the past X days (where
X is defined in an algorithm parameter).
Business Object
MC
BO / Algorithm
IMD
System Event
Algorithm
Periodic Estimation
The base-package Periodic Estimation

algorithm is described on the next slide
5 - 54
The Base Package Periodic Estimation Algorithm

Take the time to read the algorithm type's
description to understand when and how
estimation is performed for a MC
The base-package algorithm has been configured to create IMDs for each measurement gap in the
historic period. If you'd rather create To Do entries for some types of MCs, your implementation should set
up a new algorithm and plug it in on the relevant MC BOs (remember to inactivate the base-package
algorithm).
5 - 55
Estimated IMDs May Have Different VEE Rules

Foreshadowing - an MC type can have different VEE rules
applied to estimated IMDs, initial load IMDs, and manual IMDs
The rules that are applied are controlled by the VEE group
defined for each of these roles
MC
MC Type
Fallback VEE
Group
VEE Role
VEE Group
Override VEE
Group
VEE Group
Initial Load
Estimated
Manual
5 - 56
IMD
Measurement BO
The Measurement BO Is Simple

Recall that measurements are created when an IMD is
finalized
The base-package BO is very simple; it has no lifecycle and
its schema is very straightforward
5 - 58
Measurement BOs
When Other Values Are Derived
Refresher: 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 - 60
Notice how this MC's final

measurements have 2 derived values
Deriving Other Values Requires Configuration

The MC's MC type must have an entry in its Measurement Value list for each
derived value; this entry defines:
The UOM / TOU / SQI of the derived value
The shorthand notation for the value; this appears throughout the system
The algorithm used to derive the value
UOM
MC Type
Has columns for up to

10 derived values
MC
Measurement
TOU
Measurement
Value
SQI
Recall that a measurement can have multiple derived values and

each value is held in a separate column on a measurement. A
MC's MC type defines the UOM/TOU/SQI of each of the derived
values and the algorithm that calculates each.
Legend
Trans. Data
Admin Data
Master Data
Algorithm Type
Algorithm
Unusual practice: an algorithm must be set up and plugged in to

derive measurement values. The algorithm's parameters control
how the value is calculated
MO Boundary
Described
elsewhere
ST - Status
X - CLOB
Algorithm
Parameter
5 - 61
FW Data
The Base-Package Derivation Algorithm Can Calculate Many

Things
Take the time to read the algorithm

type's description to understand what
this algorithm can do as it can support
sophisticated derivations
In addition, a value on the IMD can be

used as a variable in the formula
(initialMeasurementElement=h)
5 - 62
If Configuration or Master Data Was Wrong When

The Values Were Derived
Consider what would happen if the factor used to derive a
value on a measurement was incorrect and many
measurements now exist
A batch process can be executed that re-derives these
values for a given measurement BO for a selected date
range
Users can also re-derive these values on a specific MC
using a function on the various 360 - MC zones
The function prompts for the date range to rederive and
simply transitions each measurement to the Rederive
state
5 - 63
A Different Measurement BO Is Used For MCs

With Derived Values
The derived value(s) measurement BO has a lifecycle that allows a
user to re-derive measurements (in case their original derivation was
incorrect due to faulty configuration data). Note - a Function is
available on many of the 360 zones that allows a user to to re-derive
values for a MC for a given date range.
This algorithm re-derives the values
The schema of such a measurement

has elements mapped to the derived
value columns
5 - 64
Recall That Your Electric MC Types Were

Configured With This Measurement BO
MC types with derived values should reference
this BO rather than Measurement (this BO
supports up to 10 derived values,
Measurement does not). This is described in
detail in the Measurement chapter.
In the upcoming practice,

you will add additional
measurement values
5 - 65
Re-deriving In Batch
If large numbers of MCs were derived with incorrect values due
to faulty configuration, a batch process exists that has
parameters defining the date range and measurement BO to rederive
Process: D1-MSRMT
Re-derive Values
5 - 66
Measurement
Cycle Schedule
Routes
An Aside - What Happens If An IMD's

Measurements Are The Same As Previously
Normalized Values
Completion Algorithms
When an IMD is transitioned into its Finalized state, several
Enter algorithms execute (this is true for all types of IMDs)
This algorithm does a lot of work:

1. It invokes the Derive Value Algorithms
plugged in on the MC's MC type
2. It inserts / updates the final measurements
The next slide describes how this
algorithm is configured differently
for the different IMD BOs
Final Measurement
Date/Time
5 - 68
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
An Algorithm Parameters Controls If An Interval Is

Updated
The Overwrite Identical Existing Measurements

parameter is configure to be 20 (No) for Manual
IMDs and 10 (Yes) for Initial Load and Estimated
IMDs
The rationale for this is that if a user doesn't change the measured quantity on a manual IMD,
the measurement shouldn't be updated (the audit history would reflect an update when the
measurement wasn't changed). However, if a head-end sends a replacement IMD, all
intervals in the cut should be updated (including their condition codes). Note - the value of this
parameter for Estimated IMDs is not relevant as its measurements will never exist!
5 - 69
Refresher From Fundamentals Using Factors For Variables
This chapter's final practice has you calculate line loss for each
final measurement on the Consumed MC. Before starting this
practice, numeric-oriented factors will be reviewed
Variable Values That Differ Based On Some

Characteristic
Assume:
A derived value on a measurement is calculated by:
Multiplying each final measured quantity by a line loss
conversion factor whose value varies based on some
characteristic on the SP at which the device is installed
5 - 71
A Factor That Holds Numbers

A factor is used to implement the line loss conversion factor
A factor is configured by the implementation to
hold different line loss conversion factors based
on the characteristic value held on a US's SP
Characteristic Value: Large Consumption

Effective Date
Factor: Loss Factor For Electricity

Type of Characteristic: SP Loss Factor Class
Valid Characteristic Values For This Factor
Value
1-Jan-2010
1.0145
1-Feb-2010
1.0132
1-Mar-2010
1.0143
Large Consumption
Characteristic Value: Regular Consumption
Regular Consumption
Effective Date
Notice how the conversion factor can

change over time for each class of SP
5 - 72
Value
1-Jan-2010
1.0147
1-Feb-2010
1.0151
1-Mar-2010
1.0141
When The Factor's Value Is Retrieved

Factor: Loss Factor For Electricity
Algorithm: Apply Electric Line Loss
Type of Characteristic: SP Loss Factor Class
Algorithm Parameters
Valid Characteristic Values For This Factor
Multiply measured quantity times the

loss factor for electricity
Large Consumption
At run time, the system finds the

conversion factor value using the loss
factor classification on the SP linked to the
MC's device configuration
Regular Consumption
Characteristic Value: Regular Consumption

If the SP is classified as Regular
Consumption, the system retrieves class's
line loss value effective on the start date of
the IMD
In this example, the characteristic value is retrieved from
the SP linked to the MC, but it could be derived /
retrieved from anything related to the MC
5 - 73
Effective Date
Value
1-Jan-2010
1.0147
1-Feb-2010
1.0151
1-Mar-2010
1.0141
Factors Can Be Related To Any Real or Dynamic

Attribute
Factor: Conservation Discount
Derived
Conservation %
Type of Characteristic:
Amount Conserved
Characteristic
Factor Value
Value
<5%
0%
5-10%
10%
10-20%
20%
>20%
30%
This factor's values are dynamically calculated at

execution time by deriving the amount the customer
conserved as compared to the same period in the
prior year. The derivation results in one of the
characteristic values being generated. If the count
is < 5%, no discount percent is returned.
Discount %
Factor: Territory-based KJ conversion

Type of Characteristic: SP Territory Code
This factor's values is retrieved from the SP

linked to the US.
This slide is a simplification as the factor

values are effective-dated (that is, the factor
value can change over time)
5 - 74
Characteristic
Value
Factor Value
North
1.2391
South
1.21919
East
1.32
Practice 5-2 (30 Minutes)

In this practice, you will derive the lossadjusted quantity for each measurement
on your kWh consumed MC:
The derivation is performed by

multiplying the measured quantity
by a loss adjustment factor whose
value differs by whether the SP is
classified as "large" or "regular"
The next slide provides a summary of the
data that will be set up
Please break up into teams and follow the
instructions on the upcoming slides (there
is no need to design anything at this point)
After the admin data is in place, continue
following the instructions to create another
IMD for your electric MCs
5 - 75
Date/Time
As Measured
Loss Adjusted
UOM: kWh
SQI: Consumed
UOM: kWh
SQI: Loss Adjusted
1-Jan-10 3:00pm
1.0
1.01
1-Jan-10 4:00pm
1.5
1.515
1-Jan-10 5:00pm
1.0
1.001
Alternative. Rather than deriving the loss adjusted value for

each measurement, it is possible to apply a loss factor when
usage (bill determinants) are calculated.
The pros of deriving values on measurements are:
The derived values are visible on the various 360 MC zones
The derived values can be quickly time-of-use mapped
The derived values can be reported on as they persist in the
database in an easily accessible table
The cons are:
A very small amount of disk space
A very small amount of calculation time
If the factors used to derive the information were incorrect at
the time of derivation, the derived information must be
rederived after any fix
5-2 Data Overview

Recall that a measurement can have multiple derived values and
each value is held in a separate column on a measurement. A
MC's MC type defines the UOM/TOU/SQI of each of the derived
values and the algorithm that calculates each.
MC Type
MC
UOM
TOU
Measurement
UOM/TOU/SQI
Initial Meas.
Data (IMD)
4
SQI
3
Algorithm Type
Algorithm
This factor holds the loss

adjustment factor whose
value may differ based on
the SP's classification
Unusual practice: an algorithm

must be set up and plugged in
to derive measurement values.
The algorithm's parms define
how the value is calculated.
5 - 76
Legend
Trans. Data
1
Algorithm
Parameter
Measurement
6
Char Type
Factor
Admin Data
SP
Master Data
Factor / Char
Value
Char Value
SP Char Value
FW Data
MO Boundary
2
Factor Value
An SP's BO schema can flatten elements to the SP

/ Char table. Your SP BO already has such an
element for the char type in the exercise.
Described
elsewhere
ST - Status
X - CLOB
5-2 Solution
Add A Factor
Navigate to Admin / F / + Factor to add a Factor that holds
the line loss adjustment amount (prefixed with your initials)
Factor
Description
Identifying BO
RW-LOSSFAC
RW - Loss Factor
Factor Number
5 - 77
5-2 Solution
Add Factor Values For Each Char Value
Click the Add icon to define the value for this
characteristic
Repeat for the Regular char value
5 - 78
5-2 Solution
Add A Derive Value Algorithm
3
Algorithm
Description
RW-LOSSELE
RW - Apply Loss Adjustment Electric
Navigate to Admin / A / Algorithm and find

DM_LOSSGAS (this is a sample algorithm in demo that is
used to derive several values for gas-oriented MCs).
Click Duplicate to duplicate this BO. When prompted,
please prefix your new algorithm with your initials (in real
life - this would be prefixed with CM).
This base-package algorithm type derives other
measurement values. You configure it by setting up the
algorithm's parms as desired. Please take the time to
read the algorithm type description to understand what
this algorithm can calculate (it's very powerful).
The element name of the

derived value on your
measurement BO
This formula multiplies the
variables defined below to
derive the value
When the IMD is normalized, the

system invokes this algorithm for
the collection of measurements
in the postVEE list and calculates
the lossAdjusted element by
applying the formula (and this will
retrieve the effective-dated value
of the factor for whatever SP the
MC is installed at)
V1 is the measured value

V2 is the value of the factor
5 - 79
5-2 Solution
Add An SQI
4
SQI
Description
Identifying BO
RW-LOSSADJ
RW - Loss Adjusted
Service Quantity
Identifier
5 - 80
Navigate to Admin / S / +
Service Quantity Identifier to
add an SQI to identify the loss
adjusted kWh amount
(prefixed with your initials)
5-2 Solution
Update Your MC Type
5
Service Provider
RW-E-KWH-CON-60
Update your consumed MC type to indicate that a value is derived
Add this row, make sure to reference your new SQI and
Value Derivation Algorithm
5 - 81
5-2 Solution
Update Your SP
6
Specify one of the loss factor char values
5 - 82
5-2 Solution
Add Another Day's IMDs
Your electric device's serial number
7.1
<devices>
Your electric head-end's external ID
<preVEE>
Your consumed MC's channel ID
<mcIdN>RWA</>
<stDt>2010-01-02-00.00.00</stDt>
<enDt>2010-01-03-00.00.00</enDt>
<msrs>
<mL>
<s>1</s>
<q>12.12</q>
<fc>501000</fc>
</mL>
INSTRUCTOR: give this to the students, it's the XML for
<mL>
the next day's worth of measurements for both the
<s>2</s>
consumption and generation MCs. The students must
<q>6.3</q>
change it to define their device identifier number and
<fc>501000</fc>
service provider external id. If they followed the
</mL>
instructions in the device practice, they will not have to
change the MC ids.

</msrs>
</preVEE>
<preVEE>
Your generated MC's channel ID
<mcIdN>RWB</>
</preVEE>
</devices>
5 - 83
<devices>
<preVEE>
<mcIdN>RWA</mcIdN>
<stDt>2010-01-02-00.00.00</stDt>
<enDt>2010-01-03-00.00.00</enDt>
<msrs>
<mL>
<s>1</s>
<q>1.2</q>
<fc>501000</fc>
</mL>
<mL>
<s>2</s>
<q>1.6</q>
<fc>501000</fc>
</mL>
<mL>
<s>3</s>
<q>1.4</q>
<fc>501000</fc>
</mL>
<mL>
<s>4</s>
<q>1.7</q>
<fc>501000</fc>
</mL>
<mL>
<s>5</s>
<q>1.5</q>
<fc>501000</fc>
</mL>
<mL>
<s>6</s>
<q>1.7</q>
<fc>501000</fc>
</mL>
<mL>
<s>7</s>
<q>2.1</q>
<fc>501000</fc>
</mL>
<mL>
<s>8</s>
<q>2.4</q>
<fc>501000</fc>
</mL>
<mL>
<s>9</s>
<q>1.9</q>
<fc>501000</fc>
</mL>
<mL>
<s>10</s>
<q>1.8</q>
<fc>501000</fc>
</mL>
<mL>
<s>11</s>
<q>1.7</q>
<fc>501000</fc>
</mL>
<mL>
<s>12</s>
<q>1.6</q>
<fc>501000</fc>
</mL>
<mL>
<s>13</s>
<q>1.8</q>
<fc>501000</fc>
</mL>
<mL>
<s>14</s>
<q>2.2</q>
<fc>501000</fc>
</mL>
<mL>
<s>15</s>
<q>2.5</q>
<fc>501000</fc>
</mL>
<mL>
<s>16</s>
<q>2.3</q>
<fc>501000</fc>
</mL>
<mL>
<s>17</s>
<q>2.8</q>
<fc>501000</fc>
</mL>
<mL>
<s>18</s>
<q>2.9</q>
<fc>501000</fc>
</mL>
<mL>
<s>19</s>
<q>3.2</q>
<fc>501000</fc>
</mL>
<mL>
<s>20</s>
<q>3.1</q>
<fc>501000</fc>
</mL>
<mL>
<s>21</s>
<q>1.9</q>
<fc>501000</fc>
</mL>
<mL>
<s>22</s>
<q>1.8</q>
<fc>501000</fc>
</mL>
<mL>
<s>23</s>
<q>1.7</q>
<fc>501000</fc>
</mL>
<mL>
<s>24</s>
<q>1.6</q>
<fc>501000</fc>
</mL>
</msrs>
</preVEE>
<preVEE>
<mcIdN>RWB</mcIdN>
<stDt>2010-01-02-00.00.00</stDt>
<enDt>2010-01-03-00.00.00</enDt>
<msrs>
<mL>
<s>1</s>
<q>0</q>
<fc>501000</fc>
</mL>
<mL>
<s>2</s>
<q>0</q>
<fc>501000</fc>
</mL>
<mL>
<s>3</s>
<q>0</q>
<fc>501000</fc>
</mL>
<mL>
<s>4</s>
<q>0</q>
<fc>501000</fc>
</mL>
<mL>
<s>5</s>
<q>0</q>
<fc>501000</fc>
</mL>
<mL>
<s>6</s>
<q>0</q>
<fc>501000</fc>
</mL>
<mL>
<s>7</s>
<q>.5</q>
<fc>501000</fc>
</mL>
<mL>
<s>8</s>
<q>.7</q>
<fc>501000</fc>
</mL>
<mL>
<s>9</s>
<q>1</q>
<fc>501000</fc>
</mL>
<mL>
<s>10</s>
<q>1.1</q>
<fc>501000</fc>
</mL>
<mL>
<s>11</s>
<q>1.5</q>
<fc>501000</fc>
</mL>
<mL>
<s>12</s>
<q>2</q>
<fc>501000</fc>
</mL>
<mL>
<s>13</s>
<q>1.8</q>
<fc>501000</fc>
</mL>
<mL>
<s>14</s>
<q>2.7</q>
<fc>501000</fc>
</mL>
<mL>
<s>15</s>
<q>2</q>
<fc>501000</fc>
</mL>
<mL>
<s>16</s>
<q>.5</q>
<fc>501000</fc>
</mL>
<mL>
<s>17</s>
<q>.3</q>
<fc>501000</fc>
</mL>
<mL>
<s>18</s>
<q>0</q>
<fc>501000</fc>
</mL>
<mL>
<s>19</s>
<q>0</q>
<fc>501000</fc>
</mL>
<mL>
<s>20</s>
<q>0</q>
<fc>501000</fc>
</mL>
<mL>
<s>21</s>
<q>0</q>
<fc>501000</fc>
</mL>
<mL>
<s>22</s>
<q>0</q>
<fc>501000</fc>
</mL>
<mL>
<s>23</s>
<q>0</q>
<fc>501000</fc>
</mL>
<mL>
<s>24</s>
<q>0</q>
<fc>501000</fc>
</mL>
</msrs>
</preVEE>
</devices>
5-2 Solution
Finalize The IMDs
7.2
Navigate to 360 - MC and open the IMD Overlay zone for the consumed
channel and click Reload Initial Measurements Using Pre-VEE, the graph
will look like this (notice the various color codes)
Click the IMD's info string to transfer to the IMD

portal where the IMD can be finalized. Finalize
the IMDs for both MCs.
5 - 84
5-2 Solution
Examine The Loss Adjusted Values
7.3
Click the 360 View - Measuring Component favorite link. Make sure your "consumed"
MC is displayed. Open the Final Values Overlay zone.
This dropdown contains the various values on the MC

type's measurements. Select the value for the loss
adjusted amount and click Load.
Notice how the loss adjusted amounts are

only calculated starting on 1/2/2010
5 - 85
5-2 Solution
Examine The Loss Adjusted Values
7.4
Open the Measurements zone
Notice how the loss adjusted amounts are

calculated starting on 1/2/2010
Click on one of the measurements.

Notice the Lost Adjusted quantity.
5 - 86
An Aside - Colors On Graphical Zones
An Aside Colors
Area colors for each IMD status can be configured
using a BO status option on IMD BOs
If no BO status option for Area Color is defined, the
color pallet hierarchy (defined on the next slide)
takes over
If the color pallet hierarchy takes over, Manual Finalized might not always be assigned the color
light green
For this reason, the base package IMD BOs are
delivered with default area colors for their states
The base-package colors can be overridden

by adding a new option with a higher priority
(i.e., the standard way to override a basepackage option value)
Business
Object
BO / Status
Option
IMD
A BO Status Option (Area

Color) can be configured
with the color to use for
an IMD in a given state
This color is used for the Finalized state of

manual IMDs because this BO / state has
an option with this color defined. If it hadn't,
one of the colors above the red line would
have been used.
5 - 88
Color Pallet Hierarchy

1
Foreshadowing: the
TOU graphs also make
use of this hierarchy
The colors above the red line are used to

color the areas when specific colors have not
been defined in the meta-data. Colors are
used from left to right, top to bottom.
The colors below the line are used to

color the lines. Colors are used from
right to left, bottom to top.
3
If the Manual IMD BO's Final state did not have

a specific color defined in its BO option, the
system would have selected a color for this
area using the colors above the line
5 - 89
Review Questions
5 - 90

05 Measurement BO

Cargado por

Información del documento

Derechos de autor

Formatos disponibles

Compartir este documento

Compartir o incrustar documentos

Opciones para compartir

¿Le pareció útil este documento?

¿Este contenido es inapropiado?

Copyright:

Formatos disponibles

05 Measurement BO

Cargado por

Copyright:

Formatos disponibles

5

Review From The Fundamentals Course

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.

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

Deriving Other Values

Validate Edit Estimate

Copyright 2010, Oracle. All rights reserved.

Notice how this MC's final

Measurement Tables and MOs

Copyright 2010, Oracle. All rights reserved.

Defines the head-end for smart meters.

Recall that a measurement can have multiple

A service provider has different processing methods for each

The measured quantities reside in XML lists in the CLOB

Foreshadowing: the data model allows

A measurement log is not created

Copyright 2010, Oracle. All rights reserved.

Copyright 2010, Oracle. All rights reserved.

The source of an IMD's BO depends on the source of the IMD:

Copyright 2010, Oracle. All rights reserved.

SGG Preview: The Seeder Creates Initial Load

Copyright 2010, Oracle. All rights reserved.

SGG Initial Load IMD

The L+G SGG includes the OSB

The OUAF consumes the

The D1-IMDSeeder BO has pre-processing

The JMS queue entries are

Copyright 2010, Oracle. All rights reserved.

A Demo Script Invokes The Seeder

Copyright 2010, Oracle. All rights reserved.

How The Seeder's Derive Head-End / MC Algorithm Works

The system finds a service provider with

The service provider defines the device

Copyright 2010, Oracle. All rights reserved.

How The Determine "Real" IMD BO Algorithm Works

Initial measurement creation

The meter's head-end

The system retrieves the processing method for the