03 Device BO

3
Devices
Review From The Fundamentals Course
Copyright 2010, Oracle. All rights reserved.
A Device Has Measuring Components
UOM: kWh
TOU: Peak
42293921
This device has two measuring components (MCs);

the first measures the number of kWh used during
peak periods; the other measures the number of kWh
used during off-peak periods
Terminology: The terms register and channel
are synonyms for measuring component (MC)
kWh Peak Hours

UOM: kWh
TOU: Off-peak
kWh Off-peak Hours

General Electric
Model: 12-A
3-2
Terminology: while most devices are meters, an

implementation sets up devices for every asset
that measures or monitors resource usage. For
example, a device could be set up to record
average daily temperature (if temperature plays
a part in usage calculations).
Terminology: both of the adjacent MCs
measure the same unit of measure (kWh);
however each MC measures consumption in a
different time-of-use period (peak and off-peak).
All MCs must reference a UOM; TOU is optional.
Device versus MC Attributes

A device has attributes that are the same
regardless of the number of MCs. For
example:
Manufacturer and model

Serial number
Badge number
For smart meters, the head-end system
42293921
kWh Peak Hours
A MC has attributes that may differ for

each MC on a device, for example:
The type of MC
Note, the MC's MC type defines:
Channel ID
Channel multiplier
3-3
Its UOM / TOU / SQI

Whether it is scalar or interval
If interval, its SPI
A value other than 1 means the

system will multiply the measured
consumption by this value to derive
usage
kWh Off-peak Hours

General Electric
Model: 12-A
The Combination of UOM, TOU and SQI Define What A

MC Measures
42293921
UOM: kWh
SQI: Generated
kWh Generated
UOM: kWh
SQI: Consumed
kWh Consumed
General Electric
Model: 12-A
3-4
In addition to UOM and TOU,

there is a 3rd component that is
used to identify what a MC
measures service quantity
identifier (SQI)
An SQI is only used when
multiple MCs measure the same
thing, but in different ways
For example, a meter that

measures both generation
and consumption
Like TOU, SQI is optional
The only required

component is UOM
Scalar versus Interval MCs

The prior slides illustrated a device with 2
scalar measuring components:
Scalar MCs produce a single
measurement over a period of time
Many scalar MCs are read manually,
resulting in measurements at
unpredictable intervals (e.g., "once-amonth" is not a predictable interval as
the number of seconds between
reads will vary)
Interval MCs are measured at predictable
intervals (e.g., every 15 minutes)
A device may have any combination of
interval and/or scalar measuring
components
3-5
The above is an example of a device

with an interval MC
Terminology: The acronym SPI
(seconds per interval) is used to
define the duration of the intervals
between a MC's measurements
A Device Can Be Reconfigured Over Time

Device
Device Id: 918411457633
This device has been reconfigured on 15-Sep2010. The original configuration had a single
MC; after the reconfiguration, it has two MCs
(one measures how much is generated, the
other measures how much was consumed)
Serial Number: A1-192-102121

Badge Number: EC101291012
Device Configuration
Effective Date / Time: 1-Jan-10 12:00am
Measuring
Component Id
MC Type
Channel
Identifier
Channel Multiplier
VEE Group
12154319873456
Interval kWh 15 minute
001
1.012
Residential electric
simple interval
Notice how each device configuration encapsulates

its MCs (the group of MCs are effective on the
device configuration's effective date / time)
Notice how each MC
has a unique,
system-assigned MC
ID (this is the true
identifier of the MC in
the system, all other
forms of ID are
aliases)
3-6
Effective Date / Time: 15-Sep-10 1:15pm

Measuring
Component Id
MC Type
Channel
Identifier
Channel Multiplier
VEE Group
94554319873434
Interval kWh 15 minute generated
001
1.012
generation
65534319873456
Interval kWh 15 minute consumed
002
consumption
Device-Oriented Tables and MOs
The device's head-end (a service

provider) is defined on the device type
unless overridden on a specific device
A device references a
manufacturer and
model
Manufacturer
X
Model
X
Device
ST, CH, X
Defines the head-end

systems and device
configuration types
Device Type
CH, X
Override
Fallback
Device Identifier
Type
Device Identifier
A device may have many

forms of identification (e.g.
serial, badge, etc.)
Valid Device
Configuration
A service type must exist

for each service (e.g.,
electric, gas, water)
Defines the MC types that can

be linked to device configs
Device Config
Type
CH, X
Device Config
ST, CH, X
Time Zone
Holds the effective date of

the MCs and defines the
time zone of the MCs'
measurements
What the MC measures

(foreshadowing - an MC can
measure multiple UOMs)
Defines how a MC's

measurements are VEE'ed
Legend
Trans. Data
Measuring
Component
ST, CH, X
Related
Measuring
Component
Measuring
Component
Identifier
MC Relationship
Type
Measuring
Component
Identifier Type
UOM
X
MC Type
CH, X
Fallback VEE
Group Per Role
VEE Group Per

Role
Valid VEE
Groups
Measurement
UOM/TOU/SQI
TOU
X
Value Type
SQI
X
Fallback
VEE Group
Admin Data
Master Data
Override
A MC may have
many forms of ID
3-8
Service Type
CH, X
Valid MC Type
Foreshadowing: for
standalone MCs
Used when 2 MC's
on a device
configuration
interact (e.g., a
scalar check
register and its
interval equivalent)
Valid Service
Provider
Service
Provider
FW Data
MO Boundary
Described
elsewhere
ST - Status
CH - Characteristics
X - CLOB
Legend
All Types Of MCs Can Be Measured,

Only Physical MCs Reference A Device Configuration
The MC class flag on the MC
type controls the type
Device
Config
MC
3-9
Master Data
All types of MCs are measured
Measurement
Only physical MCs reference

a device configuration
Interval channels and scalar

registers are examples of physical
MCs because:
1) they physically exist (you can
touch them)
2) they are linked to a device that
can be configured differently over
time
Admin Data
FW Data
MC Type
Physical
Tran. Data
Standalone
A standalone MC is used
to record measurements
for something that does
not have a physical
presence (for example, to
record the average daily
temperature supplied by a
weather feed).
Scratchpad
A user creates a scratchpad
MC to experiment with
measurement manipulation
functions before applying the
measurements to a physical
or standalone MC (e.g.,
experiment with the impact of
executing the "spike smooth"
function)
Aggregator
An aggregator MC holds
summarized usage from
other MCs (for example,
aggregator MCs holding
total consumption could
exist for each postal code)
BO Definition
Base-Package BOs Are Delivered Pre-Configured

The base-package supplies at least one BO for every MO
For a list of the base-package BOs linked to an MO, use the
Maintenance Object or Business Object transaction
A dashboard zone on these transactions shows all BOs
related to the MO being displayed
Note, this dashboard zone is bundled in demo
This zone has links to the Business Object - Summary tab

where a concise view of the BO's business rules is
presented
The upcoming slides will expose you to the most interesting
patterns and idiosyncratic features of the base-package deviceoriented BOs
3 - 11
Source Of Business Object

As described in the Config Tools class, every instance of an MO must
reference a BO as the BO defines how an instance looks and behave
The following diagram illustrates the source of these BOs
Defines the look and behavior of a
specific "type" instance; after a
device type is created, its
identifying BO cannot be changed
Business
Object
Device Type
Defines how master data
instances that reference a
specific "type" instance
look and behave
Device
If the admin object's master BO is changed, the

new BO definition applies to new devices.
Devices created before the change will
reference the master BO that existed at the
time they were created.
Legend
Tran. Data
Admin Data
The system snapshots the device type's

master BO when a device is created
Master Data
FW Data
3 - 12
This Pattern Is Everywhere

Most "type" and "master data" pairs follow this pattern
Device
Device Type
Device
Config
Device
Config Type
MC
MC Type
Business
Object
Business
Object
Measurement
MC type is an exception as it also

defines the BO of the measurements
linked to its MCs (this is explained later
in this class)
Legend
Tran. Data
Admin Data
Master Data
FW Data
3 - 13
Lite BOs
The device MO has "lite" BOs
"Lite" BO schemas contain a subset of the elements stored on the
instantiable BOs
"Lite" BOs are not instantiable
"Lite" BOs are "invoked for read and update" when a small subset of
information from the BO is required
The OUAF only retrieves the element in the invoked schema;
and this saves a great deal of processing time
An implementation should retrieve (and update) "lite" BOs rather
than the true instantiated BO if their logic only accesses a subset of
the information
During the next practice, please take the time to navigate to deviceoriented BOs and compare the schemas of the LITE BOs as compared to
the instantiable BOs.
3 - 14
Practice 3-1 (60 Minutes)

In this practice, you will design and set up the suite of admin data necessary to support the following
meters at a water utility:
A water meter that measures liters in 60 minute intervals
A scalar water meter used for large customers that measures liters using two registers:
One register measures water from a 6 cm diameter pipe
The other register measures water from 2 cm diameter pipe
This is a subtractive register
Notes
This type of meter is designed to route low volumes through the smaller pipe's reigster to more accurately measure
the lower consumption
This type of meter can only be installed at SPs with a 6 cm pipe
A scalar meter used for large customers that measures liters from two registers:
One register measures water from a 8 cm diameter pipe
The other register measures water from 2 cm diameter pipe

Notes
This type of meter can only be installed at SPs with a 8 cm pipe
The next slide provides a summary of the data that should be designed
After the admin data is in place, please create devices / device configs / MCs for 60 minute interval
water meter and for the 6cm / 2cm scalar meter
3 - 15
The Code and Description of the

admin data that you create should
be prefixed with your initials so you
can easily identify your data (e.g.,
your water service type should
have a code of RW-W and a
description of RW - Water (given
the author's initials are RW))
3-1 Data Overview

6
Manufacturer
X
7
Model
X
Device Type
CH, X
Device
ST, CH, X
Device Identifier
Valid Service
Provider
Valid Device
Configuration
8
Device Config
Type
CH, X
Device Config
ST, CH, X
The numbers represent the

design and setup sequence of
the objects required to
complete this practice
4
Service Type
CH, X
Valid MC Type
Measuring
Component
ST, CH, X
Related
Measuring
Component
Measuring
Component
Identifier
3
MC Type
CH, X
UOM
X
Legend
Trans. Data
Admin Data
Master Data
VEE Group Per

Role
Fallback VEE
Group Per Role
Valid VEE
Groups
The next slide(s) contain the solution, don't look until you've tried to design
your own instances of the admin data. But please look before you add
instances as future exercises depend on this configuration.
3 - 16
Measurement
UOM/TOU/SQI
TOU
X
FW Data
MO Boundary
SQI
X
Described
elsewhere
ST - Status
X - CLOB
3-1 Solution
Service Type, UOM
1
Service Type
Description
Identifying BO
RW-W
RW - Water
Service Type
UOM
Description
Identifying BO
RW-LTR
RW - Liter
Unit Of Measure
SQIs. SQIs are NOT needed to differentiate between the 2, 6 and 8 centimeter
registers as they all measure liters, the water just flows through different size pipes.
The only time SQIs would be required would be if bill determinant calculations
need to treat the consumption from one register differently from others. If we
assume the bill determinant calculations for this device just calculate the total
number of liters regardless of the size of the pipe; then no SQIs are needed.
If separate SQIs were set up for the 2, 6 and 8 MC types, the bill determinant
calculation logic would need to be configured to retrieve each of these SQI's
consumption independently. The resultant pipe-size segregate consumption would
then have to be summarized to determine the total number of liters.
3 - 17
3-1 Solution
MC Type - Interval
3.1
MC Type
Description
Identifying BO
RW-W-LTR-60
RW - Water Liter 60min
Interval Channel Type - Physical

There are different MC type BOs in the base as there are
different rules for interval versus scalar MC types
An instance of this BO will be created when a

measuring component of this type is created
An instance of this BO will be created when a measurement is
recorded for a measuring component of this type
The measurements
do not have to be
subtracted to
determine the
amount consumed
Reference your service type

Blank means this channel
cannot roll backwards
1 hour = 3600 SPI
Appears on many graphs and
dropdowns
3 - 18
Reference your UOM
3-1 Solution
MC Types - Subtractive Scalar MC Types
3.2
MC Type
Description
Identifying BO
RW-W-LTR-MAN-2CM
RW - Water Liter Manual 2cm
Register Type
RW-W-LTR-MAN-6CM
Register Type
RW-W-LTR-MAN-8CM
Register Type
After setting up the 2

centimeter MC type, use the
Duplicate feature to create the
6 and 8 centimeter MC types
The Description is important as it will be what a user will see to

differentiate between the different registers on a device
An instance of this BO will be created when a
measuring component of this type is created
Used on 360 zones
when scalar
consumption is shown
on graphs
3 - 19
An instance of this BO will be created when a measurement is

recorded for a measuring component of this type
The dial reading must be subtracted from
the prior reading to calculate consumption
If a subtractive scalar measurement exceeds this % of the dial
capacity, the measurement will be discarded prior to VEE starting
Notice this is the same UOM as on the

interval MC type
3-1 Solution
Device Configuration Type - Interval Water
4.1
Device Configuration Type
Description
Identifying BO
RW-W-SMART-60
RW - Water Smart 60 min
Reference your 60 minute

water MC
3 - 20
3-1 Solution
Device Configuration Type - Scalar Compound Device
Configurations
4.2
Description
Identifying BO
RW-W-SCALAR-6CM-2CM
RW - Water Scalar 6cm/2cm Compound
RW-W-SCALAR-8CM-2CM

After setting up the 6/2 device type, use the
Duplicate feature to create the 8/2 device type
Reference your 6cm and 2cm MC types

and set each to be Required (meaning that
a device must have both MCs)
3 - 21
3-1 Solution
Device Type - Interval Water
5.1
Device Type
Description
Identifying BO
RW-W-SMART-60
RW - Water Smart 60 min
Smart Meter Type
If the physical device could be reconfigured to measure a different

UOM or SPI, do not include the SPI or UOM in the device type
description; we've assumed this device is only capable of recording
in 60 minute intervals
Defines if the head-end system

shifts the date/times on the initial
measurements during daylight
savings time periods (not shifted
means that that initial
measurements are always
recorded in standard time)
There are different device type BOs in the base

as there are different rules for smart versus scalar
device types

Used by the SGG products (not applicable
for the time being)
Reference your interval 60 minute device

configuration type
3 - 22
3-1 Solution
Device Type - Scalar Compound
5.2
Device Type
Description
Identifying BO
RW-W-SCALAR-6CM-2CM
Manual Meter Type
RW-W-SCALAR-8CM-2CM
Manual Meter Type

After setting up the 6/2 device type, use the
Duplicate feature to create the 8/2 device type

Reference your appropriate device
configuration type
Some might feel that it is more appropriate to create a single water scalar device type and list both the 8/2 and 6/2
device configurations under it. In some situations, this might be appropriate. However, in the upcoming use-case, we
assume that different SP type have different sized pipes servicing them and that the device that's installed at the SP
should be consistent with the SP type's pipe-size. The easiest way to implement this is using the SP Type / Device
Type relationship and this is only possible if there are separate device types for the 6/2 and 8/2.
3 - 23
3-1 Solution
Manufacture / Model
6
Manufacturer
Description
Identifying BO
RW-ABC CO
RW - ABC Company
Manufacturer
Define a different model for each type of

meter
3 - 24
3-1 Solution
Water Interval Device
7
Navigate to Main - Device + to add a new device that will have

an interval 60 minute water channel. Please select your version
of the RW-W-SMART-60 device type when prompted.
Enter memorable Serial and Internal Meter

Numbers (to make it easier to find your
device later)
Reference your
manufacturer and model
3 - 25
3-1 Solution
Water Interval Device Configuration
8
Use the device context menu to add a new device configuration

to your device.
Enter this date as future

exercises will add older
measurements
3 - 26
3-1 Solution
Water Interval Measuring Component
9
Use the device configuration context menu to add a new MC to

your device configuration. Alternatively, use the Add link in the
Measure Components zone's header bar.
Configure as shown
Enter a Channel ID similar to this but

substitute RW with your initials (this is
important for a future exercise)
3 - 27
3-1 Solution
Water Interval Meter Summary
If you've set everything up appropriately, the Device

Configuration Overview zone should look like this
3 - 28
Add Device / Device Config / MCs For The Scalar

Devices
Repeat steps 7, 8 and 9 to add the master data for one instance
of a 6cm / 2cm compound meter
Make sure that there are 2 MCs linked to the device
configuration (one references the 6cm register, the other
references the 2cm register)

3 - 29
If You Need More Devices

Now that these devices exist, recall from the Fundamentals
class that you can use the Device Replicator to create copies of
them
3 - 30
Practice 3-2 (30 Minutes)

In this practice, you will design and set up the suite of admin data
necessary to support an electric meter that is installed at customers
with solar panels:
Channel 1: measures the kWh that was generated; this is an

interval channel that measures in 60 minute intervals
Channel 2: measures the kWh that was consumed; this is an interval

channel that measures in 60 minute intervals
Please break up into teams and design the admin data necessary to
add this type of device
After the admin data is in place, please create a device
Hint - it's the same as the last exercise except the MC types for the
two channels will need distinct SQIs to differentiate between the
generated and consumed kWh
3 - 31
3-2 Data Overview

7
Manufacturer
X
8
Model
X
Device Type
CH, X
Device
ST, CH, X
Device Identifier
Valid Service
Provider
Valid Device
Configuration
9
Device Config
Type
CH, X
Device Config
ST, CH, X
5
Service Type
CH, X
Valid MC Type
Measuring
Component
ST, CH, X
10
4
MC Type
CH, X
2
UOM
X
Legend
Trans. Data
Admin Data
Related
Measuring
Component
Measuring
Component
Identifier
VEE Group Per

Role
Fallback VEE
Group Per Role
Valid VEE
Groups
Measurement
UOM/TOU/SQI
The next slide(s) contain the solution, don't look until you've tried to design
your own instances of the admin data. But please look before you add
instances as future exercises depend on this configuration.
3 - 32
TOU
X
SQI
X
Master Data
FW Data
MO Boundary
Described
elsewhere
ST - Status
X - CLOB
3-2 Solution
Service Type, UOM, SQI
1
Service Type
Description
Identifying BO
RW-E
RW - Electric
Service Type
UOM
Description
Identifying BO
RW-KWH
RW - kWh
Unit Of Measure
SQI
Description
Identifying BO
RW-GENERATED
RW - Generated
Service Quantity Identifier
RW-CONSUMED
RW - Consumed
Service Quantity Identifier
SQIs. SQIs can be used to differentiate between the kWh that is generated and consumed on the two channels. In this
scenario, both channels would reference the same UOM (kWh) and each would reference one of the SQIs. Doing this allows
the bill determinant calculations to differentiate between the two channels using a combination of UOM and SQI.
UOMs. An alternative to setting up SQIs is to create distinct UOMs: 1) KWH-CONSUMED and 2) KWH-GENERATED. Each
channel would just reference its UOM (no SQIs would be needed). Both of these UOMs would reference the same "base
UOM" so they would be scaled in the same manner when shown on graphs. The bill determinant calculations would then
reference these distinct UOMs rather than each UOM / SQI combinations.
It's really a question of taste and whether an implementation feels these channel are really the same UOM.
3 - 33
3-2 Solution
MC Type
4
MC Type
Description
Identifying BO
RW-E-KWH-CON-60
RW - Electric kWh Consumed

60min
RW-E-KWH-GEN-60
RW - Electric kWh Generated

60min
After setting up the

consumed MC type,
use the Duplicate
feature to create the
generated MC type
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.
1 hour = 3600 SPI
Reference your UOM
3 - 34
Reference your
consumed SQI
3-2 Solution
5
Device Config Type
Description
Identifying BO
RW-E-CONGEN-60
RW - Electric Smart ConGen 60 min
Reference your generated and consumed MC

types and set each to be Required (meaning
that a device must have both MCs)
3 - 35
3-2 Solution
Device Type
6
Device Type
Description
Identifying BO
RW-E-CONGEN
RW - Electric Smart ConGen
Smart Meter Type
Defines if the head-end system shifts

the date/times on the initial
measurements during daylight savings
time periods (Not Shifted means that
that initial measurements are always
recorded in standard time)

Used by the SGG products (not applicable
for the time being)
Reference your interval 60 minute device

configuration type
3 - 36
3-2 Solution
Manufacture / Model
7
Manufacturer
Description
Identifying BO
RW-ABC CO
RW - ABC Company
Manufacturer
Add another model to your manufacturer

for the electric con / gen interval meter
3 - 37
3-2 Solution
Device
8
Navigate to Main / Device / + Device to add a new device. Please

select your RW-E-CONGEN device type when prompted.
Enter memorable Serial and Internal Meter

Numbers (to make it easier to find your
device later)
Reference your
manufacturer and model
3 - 38
3-2 Solution
9
Use the device context menu to add a new device configuration

to your device.
Enter this date as future

exercises will add
measurements starting here
3 - 39
3-2 Solution
Measuring Components
10
Use the device configuration context menu to add consumed

and generated MCs for your device configuration. Alternatively,
use the Add link in the Measure Components zone's header bar.
Configure as shown
Enter a Channel Id of ..A for the
Consumed MC and a Channel Id of ..B for
the Generated MC and substitute .. with
your initials (this is important for future
exercises when IMDs are uploaded)
3 - 40
3-2 Solution
Electric Consumed / Generated Meter Summary

3 - 41
Review Questions
3 - 42

03 Device BO

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

03 Device BO

Hochgeladen von

Copyright:

Verfügbare Formate

3

Review From The Fundamentals Course

Copyright 2010, Oracle. All rights reserved.

A Device Has Measuring Components

This device has two measuring components (MCs);

kWh Peak Hours

kWh Off-peak Hours

Terminology: while most devices are meters, an

Copyright 2010, Oracle. All rights reserved.

Device versus MC Attributes

Manufacturer and model

kWh Peak Hours

A MC has attributes that may differ for

Note, the MC's MC type defines:

Its UOM / TOU / SQI

A value other than 1 means the

kWh Off-peak Hours

Copyright 2010, Oracle. All rights reserved.

The Combination of UOM, TOU and SQI Define What A

In addition to UOM and TOU,

For example, a meter that

The only required

Copyright 2010, Oracle. All rights reserved.

Scalar versus Interval MCs

Copyright 2010, Oracle. All rights reserved.

The above is an example of a device

A Device Can Be Reconfigured Over Time

Serial Number: A1-192-102121

Interval kWh 15 minute

Notice how each device configuration encapsulates

Effective Date / Time: 15-Sep-10 1:15pm

Interval kWh 15 minute generated

Interval kWh 15 minute consumed

Copyright 2010, Oracle. All rights reserved.

Device-Oriented Tables and MOs

Copyright 2010, Oracle. All rights reserved.

The device's head-end (a service

Defines the head-end

A device may have many

A service type must exist

Defines the MC types that can

Holds the effective date of

What the MC measures

Defines how a MC's

VEE Group Per

Copyright 2010, Oracle. All rights reserved.

All Types Of MCs Can Be Measured,

All types of MCs are measured

Only physical MCs reference

Interval channels and scalar

Copyright 2010, Oracle. All rights reserved.

Copyright 2010, Oracle. All rights reserved.

Base-Package BOs Are Delivered Pre-Configured

This zone has links to the Business Object - Summary tab

Copyright 2010, Oracle. All rights reserved.

Source Of Business Object

If the admin object's master BO is changed, the

The system snapshots the device type's

Copyright 2010, Oracle. All rights reserved.

This Pattern Is Everywhere

MC type is an exception as it also

Copyright 2010, Oracle. All rights reserved.

Copyright 2010, Oracle. All rights reserved.

Practice 3-1 (60 Minutes)