20 - Zones and MOs

20
Zones and MOs
Copyright 2010, Oracle. All rights reserved.
Zones and The MOs They Access

This chapter is a "checkpoint"
It reviews the major MOs and the zones on which they are
displayed
20 - 2
Portals Have Many Navigation Paths

Recall that there are many navigation paths to portals, for example:
The 360 View - Measuring Component Portal can be accessed from:
The IMD Portal can be accessed from:
20 - 3
360 Search (by clicking the MC info string on one of the search results)
Everywhere an MC info string appears (by clicking an MC context menu item)
Clicking a 360 button in the Device Configuration Overview zone
BPA scripts that may navigate to this portal to review MC-oriented information
A Favorite Link
Selecting a To Do entry that highlights something unusual about a MC
Bottom line - while called "360 View - Measuring Component", this portal can
be accessed from many other places without going through 360 Search
Everywhere an IMD info string appears (by clicking the respective info string)
BPA scripts that navigate to this portal to review IMD-oriented information
A To Do entry that's been created to highlight something unusual about an IMD
Implementations Can Change Portals

The upcoming slides describe numerous portals and zones
Each zone is described in respect of a specific portal
Recall that any zone can be placed on any portal by changing
the portal's configuration
This is pointed out as implementations do not have to live with
the portal configurations shipped with the base package
because:
New zones can be created and added to any portal
Existing zones can be reused on other portals
Note well: a zone can only be placed on a portal that has its
context (e.g., it doesn't make sense to put a US-oriented
zone on a device-oriented portal)
20 - 4
Looks Can Be Deceiving

A zone may have a visibility script
A visibility script contains the logic that controls if a zone is shown on a

portal
This means the zones that are visible when a portal opens are not necessarily
all of the zones that can appear
The only way to know all possible zones on a portal it to display the portal on
Admin - Portal
For example, the following shows the zones on 360 View - Measuring
Component when an interval MC is displayed
These zones appear if an MC is in context. This
means these zones will not appear if a user
navigates to this portal and had not selected a MC
first (e.g., by clicking a Favorite Link)
These zones appear if an MC is in context
AND the MC's MC type indicates it is interval
There are other zones that appear if the

MC's type indicates it is scalar
20 - 5
Looks Can Be Deceiving (continued)

Broadcasting can cause other zones to appear
This zone only appears if a MC
type is in context (and one gets
in context by broadcasting an
MC type)
This zone exists to remind the

user to broadcast a MC type to
see the history of consumption
for this type of MC at the SP (it
has a visibility script that only
causes it to appear if no MC type
has been broadcast)
20 - 6
20
360 View - Measuring Component

The upcoming slides describe the base-package zones on this
portal
Device
Usage
Subscription
Contact
US/Contact
Service Point
US/SP
Information from many MOs

appears on the upcoming
zones. However, their
primary focus is the
highlighted area.
20 - 8
Device Config.
Install Event
Initial Meas.
Data (IMD)
Measurement
Measurement
Log
MC
Measuring Component Overview
This zone contains much of the information that appears in the Current Context zone
with a few differences:
- If the MC in context references a scalar MC, a link to the scalar MC is shown
- If the MC is a scratchpad, a link to the original MC is shown
- If the MC's device config is installed at a SP, it shows the SP and Installation links
- If the MC's device config is not currently installed at a SP, a message indicates such
- If the MC's device config is installed at a SP, it shows the usage subscriptions that
are linked to the SP (it's possible for multiple USs to be linked to the SP and all USs
are displayed in this zone). If no USs are linked to the current SP, a message
indicates such.
20 - 9
Device Configuration Overview

This zone provides an overview of the MC's device. It shows all the
device's historic configurations and where each has been installed.
The Type column contains a description of the BO

(notice how the above example shows Smart
Meter and Interval Channel rather than just Device
and Measuring Component)
The user can reload 360 View with a different MC or

SP by clicking the respective 360 button (if the device
configuration has a single MC and has been installed
at a single SP, these buttons are not useful)
The MC and SP in context are highlighted by stars after

their BO description. This is helpful when there are many
MCs under a device configuration or when the device
configuration has been installed at different SPs over time.
Context menus and hyperlinks to the various objects are everywhere
20 - 10
This zone provides an

overview of the MC's final
measurements
Final Values Overlay - Part 1

Recall that an MC type can be configured to
derive values other than the base measurement.
Use this dropdown to change the primary value
that appears in the graph below.
The number of hours

shown by default is
defined on the MC type
Beneath the graph are up to 5 event

bars that highlight if/when events have
occurred that can impact the
measurements (e.g., the meter is off,
tampers, ). The configuration of this
functionality is described after the next
slide.
Described on
next slide
A brief summary of the primary

value's measurements
A 2nd y axis appears if the UOMs of the

MCs do not share the same Base UOM
Detailed hover-text appears when

hovering over the graph
A legend of the information in the graph

20 - 11
Final Values Overlay - Part 2

The Values to Graph section can
be expanded to overlay different
MCs, derived values, and / or time
periods (e.g., same value last year).
The MC type can be configured to

overlay measurements from other
MCs on the graph. The
configuration of this functionality is
described next.
If a scalar MC is selected, its consumption is
intervalized before it is shown on the graph (the
scalar MC type controls if the conversion is
straight-line or performed using an interval
profile)
Numerous functions can be executed against the final
measurements (Override, Export to Excel, ). An
implementation can introduce a new function by creating a
BPA script and defining it in the Measurement Consumption
Function BO Option.
Notice how the x-axis rescales because

the amount of time to be displayed has
changed)
20 - 12
20
360 View Configuration
Before explaining the other zones on 360 MC,

the various configuration options that impact how
these zones look and behave will be explained
Final Value
Overlay Profiles
The Final Values Overlay graph can overlay for
up to 4 MCs in addition to the primary MC
The consumption from these MCs is

intended to help contrast the primary MC's
consumption to things like temperature,
other customers, amount conserved,
An implementation can define combinations of
these contrasting MCs by creating instances of
the Final Values Overlay Profile extendable
lookup
Each instance references up to 4 Factors (MC)
along with the color to use for each
An MC type can reference any number of these
profiles and one can be defined as the default
(the one that appears when the zone is first built)
20 - 14
MC Type
XML
Measuring
Component
MC Type / Final
Values Overlay
Profile
Default
Factor
(MC)
Ext
Factor
(MC)
Final Values
Overlay Profile
Factor
(MC)
Factor
(MC)
Recall that an MC Profile Factor can return a

different MC based a characteristic (e.g., the MC
returned for the temperature factor could differ
based on a geographic-oriented characteristic on
the SP where the MC is installed)
Final Values Graph

Disparate UOMs / SPIs / Magnitudes
Different SPIs may be commingled on the same Y-axis.
For example,
KW 15 minutes and KW 60 minute curves can be

scaled into a common SPI and shown on the
same Y-axis
Different UOMs may be commingled on the same Y-axis.
For example,
KW 15 minutes and kWh 60 minute curves can be

scaled into a common UOM / SPI
Different magnitudes may be commingled on the same Yaxis. For example,
MW and GW can be scaled into a common UOM

This means a KWH 15 minute curve can be converted
into a MW 60 minute curve
The Final Values Graph does this if it encounters MC /
Values with the same Base UOM
Converting a UOM / SPI into a different UOM / SPI is
performed by an algorithm plugged in on the target
UOM's BO (this is delivered pre-configured and
implementations should only need to change it if they
disagree with the base-package axis conversion logic)
20 - 15
MC Type
Measuring
Component
BO
MC Type / Value
UOM
Recall that a UOM can reference a

base UOM and a magnitude (the
magnitude is used to scale UOMs that
have the same base UOM but different
magnitudes into the same magnitude
(e.g., KW to MW or vice versa)
BO / Algorithm
System Event
Axis
conversion
Event Bar Profiles
Many of the 360 graphs can have up to 5

event bars under the graph that highlight when
specific events have transpired
The bars are intended to help the user

understand gaps, spikes, or other
consumption anomalies
Different groups of bars can be defined by
creating instances of the Event Bar Profile
extendable lookup
Each instance references up to 5 bar
definitions and the color to use for each bar
If a bar highlights when activities exist, the
relevant activity types are also defined
20 - 16
MC Type
- On/Off
- Activities
Bar Type
XML
Measuring
Component
MC Type / Event
Bar Profile
Default
Ext
Event Bar
Profile
XML
Event Bar 1 /
Activity Type
Every profile can

define up to 5 bars
where each bar has
a bar type that
defines the type of
info in the bar
Activity Type
If the a bar type shows activities, the pertinent

activity types must be defined. The bar under the
graph highlights if there are any activities of these
types in the consumption period
Functions
Many of the 360 graphs allow users to execute
functions
Functions can do virtually anything you can think of
(from creating a scratchpad MC, to copying the
measurements to another MC, to downloading to
Excel, )
The base-package is supplied with many functions
Each is a BPA script that captures information

and executes a service call to perform the
activity (meaning functions can do anything you
can do in a service)
The list of functions is defined in an MC BO option
Implementations can introduce additional functions by
creating new BPA scripts / services (and adding a new
BO option that references the BPA script)
Implementations can deactivate base-package
functions by superseding the base-package option
type with their own (this is done using an MO option)
Doing this means that only functions referenced

on the implementation's option type will appear
on the graph zones
20 - 17
BO
Measuring
Component
BO / Option
Option Type
Measuring
component
consumption
function
20
We will now return to the explanation of the other zones
Interval - IMD Overlay - Part 1
This zone contrasts an

MC's final measurements
to the IMDs from whence
they were derived
Take care showing too much time as

the grid beneath the graph will show
EVERY IMD in this period
Same as on Final Values Overlay
Notice that the final measurement line is

aligned with the shape of the manual IMD's
post VEE quantities (rather than the original
head-end IMD post VEE quantities)
20 - 19
The "line" represents the final

measurements. The "area" represents
EITHER the pre or post VEE
measurements (defaults to post). The two
will align when the final measurements are
the same as the pre / post values
(meaning that VEE didn't change anything
and a user didn't override anything).
The color of the area is based on
1. The state of the respective IMD (e.g.,
areas whose IMD is in the exception state
are colored differently from finalized IMDs)
2. The source of the IMD (manual IMDs
are colored differently from IMDs from
head-ends).
Reload the area under the graph with

either the pre or post VEE
Interval - IMD Overlay - Part 2
Turn off to remove this

IMD's measurements from
the graph's area
The number of final measurements that

reference the IMD (this will be less than the
number on the IMD when it is overridden by
a subsequent IMD or the IMD is not final)
Drill to the IMD portal

(described later)
20 - 20
This area highlights when the VEE process (or

a manual override) changes an IMD's
measurements as the post VEE will differ from
the pre VEE (differences are highlighted in red)
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. These can be overridden.
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.
20 - 21
An Aside 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
20 - 22
This zone highlights if an MC's

measurements have been
changed since they were first
added
Interval - Audit View
Same as on Final
Values Overlay
The measurement details from the area in
the lens are shown below both graphically
and in columnar format. Drag the lens to
see different time periods.
If there are changes, you can use the Snapshot as of

dropdown to see the distinct points in time when
changes occurred (and when measurements were
added). You can select a value from the dropdown to
see how the measurements looked at the selected
point in time (the graph contrasts how it looked then vs
how it looks now)
The vertical bars in the graph highlight the

number of times the interval has been
changed since it was first added (the scale is
on this Y axis). If there are no bars, no
changes have occurred.
Drill to a portal that shows

every change for a given
interval in a grid
How many times

this interval has
been changed
20 - 23
The current quantity and

condition for the interval are
shown (gray means they are
the same)
This zone applies a TOU map to

an MC's final measurements and
summarize the totals by day
Time of Use By Day

Defines which of the final
measurement values to TOU map
Any amount of time can be

used (and the graph scales
appropriately)
Defaults from the MC and

may be overridden
The color of each TOU code is defined on

the TOU admin object (i.e., the colors are
configurable by the implementation)
Every TOU codes in the period will appear

in the legend; however, only the first four
will have distinct colors in the graph (all
others will share the "all others" color). To
see one of the "all others" as a distinct
color, select it and Reload the graph.
20 - 24
The MC type can be configured to

display the final measurements from a
MC derived from a MC-oriented factor
(e.g., in this case, temperature is
shown and the temperature could
differ by geographic area). This line
and the extra y axis appear when an
MC has been so configured.

shows the results for every
interval
Time of Use Overlay
The only difference is that each interval in

the period is colored accordingly
20 - 25
Time of Use By Day

shows the results summarized by
year or by month (based on the
selected Group By option)
Up to 12 TOU codes will

appear
20 - 26
This zone is the scalar equivalent

of the interval IMD overlay
20 - 27
Scalar - IMD Overlay
This zone is the scalar equivalent

of the interval audit overlay
20 - 28
Scalar - Audit View
Practice (15 Minutes)

In this practice, you will use each of the zones described in this section
20 - 29
20
360 View - Device
360 View - Device

portal
Information from many MOs appears
on the upcoming zones. However, their
primary focus is the highlighted area.
Usage
Subscription
Contact
US/Contact
Service Point
US/SP
Device Config.
Install Event
Initial Meas.
Data (IMD)
Measurement
The Device Configuration

Overview zone is not described
in this section as it's the same
zone described earlier
20 - 31
Device
Measurement
Log
MC
Device Overview
This zone contains much of the information that appears in the Current Context zone with a few
differences:
- If the device's current device config is installed at a SP, it show the SP and Installation links
- If the device's current device config is not currently installed at a SP, a message indicates such
- If the device's current device config is installed at a SP, it shows the usage subscriptions that
are linked to the SP (it's possible for multiple USs to be linked to the SP and all USs are
displayed in this zone). If no USs are linked to the current SP, a message indicates such.
20 - 32
20
360 View - Service Point
360 View - Service Point

portal
Device
Usage
Subscription
Contact
US/Contact
Service Point
US/SP

zones. However, their
primary focus is the
highlighted area.
Device Config.
Install Event
Initial Meas.
Data (IMD)
Measurement
Measurement
Log
20 - 34
MC
Service Point Overview
This zone contains much of the information that appears in the Current Context zone with a few
differences:
- If the SP has a device installed, the Device, Device Configuration and Installation links are shown
- If the SP does not currently have a device installed, a message indicates such
- Every US linked to the SP is shown
- If no USs are linked to the current SP, a message indicates such
20 - 35
Measuring Component Types
This zone lists the distinct MC types that have been installed at the SP.
Clicking the adjacent broadcast icon causes other zones to appear that
show information about all MC's of this type that have been installed at the
SP (useful when meter exchanges have occurred and you want to see
consumption across the meter exchange boundaries)
20 - 36
This zone provides an

overview of the final
measurements for MCs of
the broadcast MC type
Interval Consumption History
Notice many of the same features

as on the MC-oriented zones
A list of the MCs along with their

installation info is shown
20 - 37
This zone is the scalar

equivalent of the interval
audit overlay
20 - 38
Scalar Consumption History
Timeline
This zone highlights when different
events have occurred for the SP,
US, contact, device and MC in
context
Hover to see information about the event.

Click to see the details of the event (these details
appear in the area beneath all of the timelines).
The number of timelines and what they show is controlled by

the algorithms defined on the zone's configuration. The base
package algorithms show:
- When usage transactions exist for the US in context
- When activities exist for the contact, usage subscription,
service point, device or measuring component in context.
- When IMDs with VEE exceptions exist for the measuring
component, device or service point in context.
Implementations can add additional timelines by creating a
new algorithm and defining it on the timeline zone's
parameters
20 - 39
The color of the event has meaning (e.g., a

complete usage transaction looks different from an
in progress usage transaction)
20
360 View - Usage Subscription
360 View - Usage Subscription

portal
Device
Usage
Subscription
Contact
US/Contact
Service Point
US/SP
Usage
Transaction
Device Config.
Install Event
Initial Meas.
Data (IMD)
Measurement
The Timeline zone is not

described in this section as it's
the same zone described earlier
20 - 41

zones. However, their primary
focus is the highlighted area.
Measurement
Log
MC
360 Usage Subscription Zones
This zone contains much of the information that appears in the Current Context
zone with a few differences:
- Every SP linked to the US is shown
This zone contains the last X usage transactions for the usage subscription
20 - 42
20
360 View - Contact
360 View - Contact

portal
Device
SP/Contact
Usage
Subscription
Contact
US/Contact
Service Point
US/SP
Usage
Transaction
Device Config.
Install Event
Initial Meas.
Data (IMD)
Measurement

20 - 44
Measurement
Log
MC
360 Contact Zones
This zone contains summary

information about the contact
This zone lists the contacts

usage subscriptions
???
20 - 45
This zone lists the service

points on which the contact is
referenced (these are not the
SPs linked to the USs)
360 View Is Complete

Remember, an implementation can add zones to any of
these portals
We'll now move on to other interesting portals
20 - 46
20
Initial Measurement Data (IMD) Portal
IMD Portal
portal
Device
Usage
Subscription
Service Point
US/SP
Device Config.
Install Event
Initial Meas.
Data (IMD)
VEE Exception
Measurement

20 - 48
Measurement
Log
MC
This zone shows the open

exceptions linked to the IMD;
it is suppressed when there
are none
20 - 49
Open Exception Detail
Numerous functions can be executed

against the IMD (Save as, Smooth
Spikes, Adjust Intervals Using Math,
). An implementation can introduce
a new function by creating a BPA
script and defining it in the Interval
Initial Measurement Function BO
Option.
Interval IMD Lens
This zone provides an overview of an

IMD's pre and post VEE measurement
values and the final measurements that
were created (if any)
Controls if the "area" in the graph is
the post VEE measurements or the
final measurements
The measurement details from the area in

the lens are shown below both graphically
and in columnar format. Drag the lens to
see different time periods below.
The line is the post VEE

measurements. The "area"
represents EITHER the pre or final
measurements.
If a user manually edited a quantity, it
is highlighted accordingly.
Click the line and drag it to change

the Quantities in the grid (you can
also change the quantities in the grid
and this will change the line)
Apply Changes is only enabled if the IMD is in an

editable state (the reason changes are allowed to
non-editable states is to cater for "save as" of an
edited, but final curve). After applying changes, use
the next zone to VEE / force complete the IMD.
20 - 50
Use these dropdowns to highlight

intervals with a given condition code
This zone is the scalar

equivalent of the interval IMD
lens
20 - 51
Scalar Initial Measurement
Initial Measurement
This zone provides an overview of an
IMD. It also contains the actions that
can be executed against the IMD based
on its current state
20 - 52
Raw Data, Pre-VEE and Post-VEE XML Dagta

This zone shows the XML of:
- Raw measurements (what was sent from the head-end)
- Pre VEE measurements
- Post VEE measurements
<mL> is a list node and there will be one for every measurement
<s> is a unique system-generated sequence for each measurement in the IMD
<q> is the quantity (amount consumed)
<fc> is the condition code (estimated, regular, missing, )
<sts> is a list containing status codes sent from the head-end
(the status codes are used to derive the condition code)
This information probably has no use in

production (but that's up to an implementation)
20 - 53
Measurements of Initial Measurement

This zone lists the first 50 final measurements that
currently reference this IMD (if there are more than
50, the zone's Excel download functionality can be
used to see all of the measurements)
20 - 54
20
IMD Log Portal
IMD Log Portal

portal
Device
Usage
Subscription
Service Point
US/SP
Install Event
VEE Exception

20 - 56
Device Config.
Initial Meas.
Data (IMD)
Measurement
Measurement
Log
MC
This zone shows a summary

of the IMD's lifecycle (from
created to finalized).
Initial Measurement Log
If the IMD creates other objects in its

lifecycle (e.g., a To Do entry), a record of
such also appears in this list with a
hyperlink to the related object
20 - 57
This zone shows a summary

of the exceptions (open and
closed) linked to the IMD; it
is suppressed when there
are none
20 - 58
Exception Summary
This zone shows the details

of a broadcast exception
linked to the IMD; it is
suppressed when nothing
has been broadcast
20 - 59
Exception Detail
This zone shows the details

of the trace that is
maintained be the VEE
engine if the IMD is marked
with trace = true (this
information is for
performance and debugging
purposes)
20 - 60
IMD Trace Log
20
Usage Transaction Portal
Usage Transaction Portal

portal
Device
Usage
Subscription
Service Point
US/SP
Usage
Transaction
Device Config.
Install Event
Initial Meas.
Data (IMD)
Measurement

20 - 62
Measurement
Log
MC
Usage Transaction
This zone provides an overview of a usage
transaction and shows the service quantities in its
usage periods. It also contains the actions that can
be executed against the UT based on its current
state.
20 - 63
Usage Transaction Scalar Details

This zone lists the scalar reads on the
usage transaction (if any)
20 - 64
Service Quantity Overlay

This zone ???
20 - 65
Time of Use Overlay

This zone ???
20 - 66
Review Questions
20 - 67

20 - Zones and MOs

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

20 - Zones and MOs

Caricato da

Copyright:

Formati disponibili

20

Zones and MOs

Copyright 2010, Oracle. All rights reserved.

Zones and The MOs They Access

Copyright 2010, Oracle. All rights reserved.

Portals Have Many Navigation Paths

The 360 View - Measuring Component Portal can be accessed from:

The IMD Portal can be accessed from:

Copyright 2010, Oracle. All rights reserved.

Implementations Can Change Portals

Copyright 2010, Oracle. All rights reserved.

Looks Can Be Deceiving

A visibility script contains the logic that controls if a zone is shown on a

There are other zones that appear if the

Copyright 2010, Oracle. All rights reserved.

Looks Can Be Deceiving (continued)

This zone exists to remind the

Copyright 2010, Oracle. All rights reserved.

360 View - Measuring Component

Copyright 2010, Oracle. All rights reserved.

360 View - Measuring Component

Information from many MOs

Copyright 2010, Oracle. All rights reserved.

Measuring Component Overview

Copyright 2010, Oracle. All rights reserved.

Device Configuration Overview

The Type column contains a description of the BO

The user can reload 360 View with a different MC or

The MC and SP in context are highlighted by stars after

Copyright 2010, Oracle. All rights reserved.

This zone provides an

Final Values Overlay - Part 1

The number of hours

Beneath the graph are up to 5 event

A brief summary of the primary

A 2nd y axis appears if the UOMs of the

Detailed hover-text appears when

A legend of the information in the graph

Copyright 2010, Oracle. All rights reserved.

Final Values Overlay - Part 2

The MC type can be configured to

Notice how the x-axis rescales because

Copyright 2010, Oracle. All rights reserved.

360 View Configuration

Before explaining the other zones on 360 MC,

Copyright 2010, Oracle. All rights reserved.

The consumption from these MCs is

Recall that an MC Profile Factor can return a

Copyright 2010, Oracle. All rights reserved.

Final Values Graph

KW 15 minutes and KW 60 minute curves can be

KW 15 minutes and kWh 60 minute curves can be

MW and GW can be scaled into a common UOM

Recall that a UOM can reference a

Copyright 2010, Oracle. All rights reserved.

Event Bar Profiles

Many of the 360 graphs can have up to 5

The bars are intended to help the user

Every profile can

If the a bar type shows activities, the pertinent

Copyright 2010, Oracle. All rights reserved.

Each is a BPA script that captures information

Doing this means that only functions referenced