Sie sind auf Seite 1von 81

4

Service Point

Review From The Fundamentals Course

Copyright 2010, Oracle. All rights reserved.

Devices Are Installed At Service Points


A service point (SP) is a physical location where a device may be installed
At any instant in time,
A SP may have a single device installed (or no device may be
installed)
A device may be installed at a single SP (or it may not be installed at a
SP)
Over time:
Different devices may be installed at a SP
A device may be installed at different SPs
12393921

Electric SP

KWH

Installed on 15-Jan-2010 at 12:15


pm

GE
Model: 12-A

Electric Meter (Device)

4-2

Copyright 2010, Oracle. All rights reserved.

Service Points Have Installation Events


An installation event is created when a device
is installed at a SP
Installation events are the history of the
devices that have been installed at a SP
so usage at a SP can be calculated
throughout time
While a device is installed at a SP, it may be
turned off (and back on again)
The installation event that records the
original installation date and time also
records the dates and times when the
device has been turned on and off
When a device is removed, the original
installation event is updated with the removal
date and time
4-3

Installation Event
Installed:
14-Jan-2010 11:30am
Turned on:
14-Jan-2010 11:30am
Removed:
29-May-2010 1:15pm

12393921
KWH
GE
Model: 12-A

15 Ocean Ave

Installation Event
Installed:
1-Jun-2010 9:30am
Turned on:
3-Jun-2010 1:45pm
Turned off:
21-Sep-2010 3:00pm
Turned on:
07-Nov-2010 9:00am

Copyright 2010, Oracle. All rights reserved.

AS93911
KWH
L+G
Model: Z1

Installation Events Reference Device Configurations


Device
Device Id: 918411457633
Serial Number: A1-192-102121
Installation Event 1
Installed:
14-Jan-2010 11:30am
Turned on:
14-Jan-2010 11:30am
Removed:
15-Sep-2010 1:15pm

To be precise, a device configuration is installed at


a service point. This means that if a device is
reconfigured, the original configuration's installation
event must be updated with the "removal"
(reconfiguration) date and a new installation event
created with the "install" (reconfiguration) date

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

Device Configuration
Electric SP
15 Ocean Ave
Installation Event 2
Installed:
15-Sep-2010 1:15pm
Turned on:
15-Sep-2010 1:15pm

4-4

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

Residential electric
generation

65534319873456

Interval kWh 15 minute consumed

002

Residential electric
consumption

Copyright 2010, Oracle. All rights reserved.

If a device is replaced at a SP,


its installation event is expired
and a new installation event is
created. Notice how each
installation event references
the device configuration that's
installed.

Device Exchanges
Device
Device Id: 918411457633
Serial Number: A1-192-102121

Installation Event 1
Installed:
14-Jan-2010 11:30am
Turned on:
14-Jan-2010 11:30am
Removed:
15-Sep-2010 1:15pm

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

Device
Device Id: 145763391841

Electric SP
15 Ocean Ave

Serial Number: ZZ-QW129192

Device Configuration
Installation Event 2
Installed:
15-Sep-2010 1:15pm
Turned on:
15-Sep-2010 1:15pm

4-5

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


Measuring
Component Id

MC Type

Channel
Identifier

Channel Multiplier

VEE Group

98734561215431

Interval kWh 15 minute

001

1.012

Residential electric
simple interval

Copyright 2010, Oracle. All rights reserved.

SP Hierarchies
Using a SP hierarchy makes sense if the parent SPs have many
attributes
Without parent SPs, these attributes must be redundantly
maintained on every child SPs
Bottom line - the method to use is subjective

Electric SP - Gener.
Address:15 Ocean Ave
NMI: 1920101291

Electric SP - Cons.
Address:15 Ocean Ave
NMI: 1920101291

vs

Parent SP: 15 Ocean Ave


NMI: 1920101291

Electric SP - Gener.
Address:15 Ocean Ave

4-6

Copyright 2010, Oracle. All rights reserved.

Electric SP - Cons.
Address:15 Ocean Ave

Different Relationship Types In Different Market


Each market has different relationship types between its service
providers
This market has two relationship types and there is a
single service provider for each relationship:
1) there is a single energy supply company
2) there is a single meter service provider

This "market" is not deregulated


(the distribution company is the
de facto energy supplier and
meter service provider)

A single instance of the meter data


products may have SPs in different
markets where each market has
different relationship types and service
providers

4-7

This market has two relationship types (energy supply and meter service).
In this market, there are multiple service providers for each relationship
type. Each SP can choose any of the relationship type's service providers.
If a SP does not declare a specific service provider for a given relationship
type, the relationship type's "fallback" service provider is assumed.

Copyright 2010, Oracle. All rights reserved.

A Measurement Cycle Has Routes And A Schedule


Measurement Cycle: Day 6
Scheduled Selection Date: 7-Sep-2010
A measurement cycle defines its
routes

Measurement Cycle: Day 6


Electric SP
15 Ocean Ave
Cycle: Day 6
Route: 003
Sequence: 121
A manually read SP
references a measurement
cycle, route and sequence
within the route

Routes
001
002

Route

Measurement
Cycle: Day
6
001
Download
(manual
read)
002
Download
(manual
read)
Scheduled
Selection
Date:
6-Oct-2010
003
Download (manual read)
Route
Schedule Type
004
Download (manual read)
Measurement
Cycle: Day
6
001
Download
(manual
read)
002
Download
(manual
read)
Scheduled
Selection
Date:
8-Nov-2010

003

003
Route

Download (manual read)


Schedule Type

004

004
001

Download (manual read)


Download (manual read)

002

Download (manual read)

003

Download (manual read)

004

Download (manual read)

This cycle has a monthly schedule


(any frequency is possible)

4-8

Schedule Type

Copyright 2010, Oracle. All rights reserved.

Service Point Tables and MOs

Copyright 2010, Oracle. All rights reserved.

Defines
when each
of a cycle's
routes is
processed

Service
Type
Measurement
Cycle
CH, X

Schedule Status

Valid Device
Type

Defines the
recipient of the
route's cyclical
information

Measurement
Route
CH, X

Measurement
Cycle Schedule
CH, X
Meas Cycle
Schedule Route
X

SP Type
CH, X

Service
Provider

Used in deregulated markets


when "child" SPs reference a
"master" SP that holds
common attributes

Controls the types


of devices that can
be installed
Time Zone

Service Point
ST, CH, X

Schedule Type

Useful when
routes are
estimated
every other
month

Address

Device

The device
configuration is
referenced on an
installation event
Device
Config.

Install Event ST,


CH, X
Install Date/Time
Removal Date/Time

Related Service
Point

Service Point
Identifier

Service Point
Relationship
Type

Service Point
Identifier Type

A SP may have
many forms of
identification

Service Point
Contact

SP Contact
Relationship
Type

SP / Market
Participant

ON/ OFF
History
X

Defines when the


device is turned on
and off while
installed at the SP
Market
CH, X

Market
Relationship
Type

Contact

Override
Fallback

Used when non-customer


relationships are defined on a SP
(customer relationships are
defined on the usage
subscription(s) linked to the SP)

4 - 10

Device Type

Service
Provider
CH, X

Trans. Data
Market /
Relationship
Type

Valid Service
Providers

The SP's service providers are


defined on the market unless
overridden on a specific SP

Copyright 2010, Oracle. All rights reserved.

Legend

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

BO Definition

Copyright 2010, Oracle. All rights reserved.

BO Definition - Part 1
SP follows the classic
pattern described for the
device-oriented admin
objects

SP Type

Service
Point

Market

Business
Object

Installation
Event

Device

Business
Object

Business
Object

Unusual practice: an installation event's BO is defined in


a device BO option. The reason for this is because the
installation event's lifecycle differs depending on the
type of device BO (e.g., the lifecycle of a smart meter's
installation event involves commissioning and
connecting whereas the installation event for a manual
meter does not have these states)

Option

Legend
Tran. Data
Admin Data
Master Data
FW Data

4 - 12

Copyright 2010, Oracle. All rights reserved.

BO Definition - Part 2

Measurement cycles follows


the classic pattern
described for the deviceoriented admin objects

Business
Object

Measurement Cycle

Business
Object

Measurement Cycle
Schedule

Legend
Tran. Data
Admin Data
Master Data
FW Data

4 - 13

Copyright 2010, Oracle. All rights reserved.

Practice 4-1 (15 Minutes)


In this practice, you will design and set up the suite of admin data necessary to
support the following service points:

A commercial water SP that can only have the 6cm / 2cm type of devices
installed (because it has a 6cm pipe)

A commercial water SP that can only have the 8cm / 2cm type of devices
installed (because it has a 8cm pipe)

A residential water SP that can have either a smart water meter or a


scalar water meter installed (note, you don't have to set up the device
type for the scalar water meter, but pretend that it exists when you design
the SP type)
The next slide provides a summary of the data that should be designed
Please break up into teams and design the admin data necessary to add these
devices
After the admin data is in place, please create SPs and install your devices for
the residential water SP and the commercial 6cm/2cm SP

4 - 14

Copyright 2010, Oracle. All rights reserved.

4-1 Data Overview


1
Service
Type

SP Type
CH, X
Valid Device
Type

Device Type

Device

Time Zone

2
Service Point
ST, CH, X

Address

4
Install Event ST,
CH, X

Related Service
Point

Service Point
Identifier

Service Point
Contact

SP / Market
Participant

ON/ OFF
History
X

Device
Config.

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

4 - 15

Copyright 2010, Oracle. All rights reserved.

4-1 Solution
SP Types
1

SP Type

Description

Identifying BO

RW-W-RES

RW - Water Residential

Service Point Type

RW-W-COM-6CM

RW - Water Commercial 6cm

Service Point Type

RW-W-COM-8CM

RW - Water Commercial 8cm

Service Point Type

After setting up the residential


SP type, use the Duplicate
feature to create the 6cm
commercial SP type. Make
sure to select the appropriate
device type. You don't have to
create the 8cm SP type.

Reference your service type


An instance of this BO will be created when a
service point of this type is created

If a scalar device could be installed at this SP, you'd reference its


device type in the list

4 - 16

Copyright 2010, Oracle. All rights reserved.

4-1 Solution
Service Point
2

Navigate to Main / Device Installation / + Service Point to


add a new water residential service point. Please select
your RW - Water Residential SP type when prompted.

Defines if the SP is connected


to the water main

Enter an address that you


can remember

The remaining attributes are optional


and can be left blank (for now).

4 - 17

Copyright 2010, Oracle. All rights reserved.

4-1 Solution
Activate The Device Configuration
3

Before a device configuration can be installed at a SP, it must be


Active (the system validates that all required MC types are linked to
the device config when it is activated). To do this, display your water
60 minute device configuration on the Device Configuration Portal
and then activate it (note, you can click the device configuration link
in the various zones to navigate to this portal).

Defines if the SP is connected


to the water main

Click Activate to change the device


configuration's state to Active (only
Active
Enter an address thatdevice
you configurations can be
installed at a SP)
can remember

4 - 18

Copyright 2010, Oracle. All rights reserved.

4-1 Solution
Installation Event - Add
Use the SP context menu to add an installation event to the
service point

4.1

Find your residential water


device configuration

Search by Serial Number (using your


initials) should show the devices that
you've set up

4 - 19

Copyright 2010, Oracle. All rights reserved.

4-1 Solution
Installation Event - Add Continued
After clicking Save, enter the remaining information

4.2

Enter this date as future exercises


will add measurements starting here

4 - 20

Copyright 2010, Oracle. All rights reserved.

4-1 Solution
Installation Event - Commission
Because this is a smart meter being installed, it must be
commissioned before it can record consumption

4.3

Click Commission to change the


installation event's state to
Commissioned

4 - 21

Copyright 2010, Oracle. All rights reserved.

4-1 Solution
Installation Event - Connect
Because this is a smart meter being installed, it must be
connected before it can record consumption

4.4

Click Connect to change the


installation event's state to
Connected

After it is connected, noticed the


On/Off History is now populated with
an entry

4 - 22

Copyright 2010, Oracle. All rights reserved.

4-1 Solution
Residential Water SP Summary

If you've set everything up appropriately, the 360 search results


should look similar to the following when you search using your
SP's address

4 - 23

Copyright 2010, Oracle. All rights reserved.

Add SP and Installation Event For A 6CM SP


Repeat steps 2, 3 and 4 to add the master data for one instance of a
6cm water SP and install your 6cm/2cm device configuration at it (use
another address you can remember)
Because this is not a smart meter, you won't have to commission
or connect the installation event

If you've set everything up appropriately, the 360 search results


should look similar to the following when you search using your
SP's address

4 - 24

Copyright 2010, Oracle. All rights reserved.

D1-ServicePoint BO Overview

Copyright 2010, Oracle. All rights reserved.

The SP BO Is Simple
Active SPs are capable of having a
device installed

The business rules are equally


simple

4 - 26

Copyright 2010, Oracle. All rights reserved.

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.

SP Schema - Part 1

Intuitive / standard elements

Notice how the parent SP, external ID


and main contact are all flattened into
one of the SP's child tables

4 - 27

Copyright 2010, Oracle. All rights reserved.

SP Schema - Part 2

The standard address constituents


Note: the Admin - Country page is used
to define which of these elements are
used in a country and what their labels
are for the country (e.g., number1 may
not be used in France, and the label for
State may be changed to Province in
Canada)

4 - 28

Copyright 2010, Oracle. All rights reserved.

SP Schema - Part 3
Notice the use of lookup and
extendable lookup (extendable lookups
are used when the valid values could
be longer than 4 characters)
So the SP can be
shown on a map
Information from
CCB; notice how
these are stored in
the CLOB rather
than as real
columns

Standard elements

4 - 29

Copyright 2010, Oracle. All rights reserved.

Installation Event BO Overview

Copyright 2010, Oracle. All rights reserved.

Smart Meter Installation Events Are Interesting


The complex lifecycle reflects the
different states a smart meter can be
in at a SP (you saw this in the prior
exercise when you commissioned and
connected the device config before it
was turned on)

The business rules are equally


interesting

4 - 31

Copyright 2010, Oracle. All rights reserved.

Manual Meter Installation Events Are Simple


The simple lifecycle reflects the different states a
manual meter can be in at a SP (you saw this when
you installed the 6cm/2cm in the last exercise as you
didn't have to commission or connect - the meter was
turned on by default when it was added)

The business rules are more


interesting than the lifecycle

4 - 32

Copyright 2010, Oracle. All rights reserved.

Refresher - Adding Elements To BOs

Copyright 2010, Oracle. All rights reserved.

Child BOs in Demo


Child BOs exist in the demonstration system to illustrate how different
types of SPs can have different elements and business rules
These are defined as child BOs because they inherit the basepackage SP BO's behavior

For example, additional gas-oriented elements


exist on the demo gas service point
Standard pattern: because each of these child
BOs has idiosyncratic elements, they require
their own display and maintenance UI maps

4 - 34

Copyright 2010, Oracle. All rights reserved.

Refresher - When New Elements Are Added To A


Child BO
When elements are added to a child BO that is displayed and/or
maintained by users, the following items must be created and
referenced on the child BO's options:
The Display UI Map (a copy of the base BO's
display map with the new elements positioned
appropriately). This is the UI map used to display
the BO on the portal.
The Display Map Service Script (a
copy of the base BO's service script
with the new display map referenced in
its schema). This is the service script
that retrieves the information displayed
on the Display UI Map.
The Maintenance UI Map (a copy of the base
BO's maintenance map with the new elements
positioned appropriately). This is the UI map
presented during maintenance of the BO.

4 - 35

Copyright 2010, Oracle. All rights reserved.

Advanced Technique - Adding Elements To A


Common Data Area
The schema of many base-package BOs includes a "common data area"
If the element(s) to be added are applicable to all BO's that include the common data
area, a child BO does not have to be created
Rather:

Create a data area and indicate that it extends the base-package common data
area. In this data area, reference the new element(s)

Create new UI maps (if the elements are displayed and/or maintained by users)

Update the base-package BO options to reference the new UI maps (with higher
sequence numbers than the base package UI map options)

This BO includes a common data area. You can add


elements to the BO by creating a data area that extends
the common data area.

4 - 36

Copyright 2010, Oracle. All rights reserved.

Refresher - Revision Control

In the next practice, you will add an element to a


BO to support implementation-specific functionality.
Before starting this practice, your instructor will
turn on Revision Control to help you manage what
you're doing.

Copyright 2010, Oracle. All rights reserved.

Revision Control Overview


A MO can be configured to be subject to revision control
When a MO is under revision control, you must:
Check out an object in order to change it (and while its
checked out, no one else can change it)
Check in an object when youre finished making changes
Alternatively, revert all changes made since the initial check
out
In addition, after revision history exists, you can:
Reinstate an older version of an object
Recover a deleted object
With proper access rights, "take over" someone else's
checked-out work

4 - 38

Copyright 2010, Oracle. All rights reserved.

What It Is (And What It's Not)


This functionality's purpose is to:

Prevent multiple developers from working on the same object at the same time
Allow developers to take "check points" so they can revert inadvertent changes
Allow older versions of objects to be reinstated
Allow deleted objects to be reinstated
Allow developers to see how older versions looked
Allow anyone to see when an object was added, changed or deleted
Allow developers to easily navigate to the objects they are currently configuring
(this might be the most useful function during the class)

This functionality does NOT allow a developer to work in a stand-alone


mode because the configuration tools meta-data resides on the central
database

4 - 39

This means that any changes to a checked out object may impact other
developers (for better or for worse)

Copyright 2010, Oracle. All rights reserved.

The Revision Control Zone


The Revision Control dashboard zone is used to perform all
revision-oriented functions

If a MO is subject to revision control, the Revision


Control zone appears in the dashboard
Different actions are available based on the
revision state of the object and the current user.
Well discuss these next.
Shows when the object was last revised and by whom.
Navigates to the Revision History portal where you can
see all the revisions to this object over time.

4 - 40

Copyright 2010, Oracle. All rights reserved.

Checked Out Objects Zone


You can configure the dashboard to show the Checked Out zone
This zone lists all objects that you have checked out
This zone is hidden if you have no objects checked out

Clicking a line navigates to


the object

4 - 41

Copyright 2010, Oracle. All rights reserved.

Instructor - Turn On Revision Control


A script exists to facilitate enabling and disabling revision control for selected MOs
To execute it:

Change your portal preference to show the Favorite Scripts zone in the Dashboard

Click the Search link to pop-up the script search window

Enter "%enable" to find this script and then execute it

Turn on revision control on the following objects:

Business Object
Field
Lookup
Script
UI Map

After revision control is turned on, all students should change their portal preference to show
the Checked Out zone in the Dashboard

4 - 42

Copyright 2010, Oracle. All rights reserved.

Practice 4-2 (45 Minutes)


The electric residential SP needs a new element to indicate if solar is
installed
The element's valid values will reside in a lookup field:
Unknown
Not installed
Less than 5KW System
>= 5KW System
This element will reside in the SP's CLOB
The next slide provides a summary of the data that should be
designed
Please break up into teams and design the admin data necessary to
add these devices
After the admin data is in place, please create an electric SP and
install your electric device at it
4 - 43

Copyright 2010, Oracle. All rights reserved.

4-2 Data Overview


1
Lookup

7
SP Type
CH, X

Valid Device
Type

Field

Device Type

3
BO
Device

BO Schema

BO Option

6
8

4
UI Map

Service Point
ST, CH, X

Script

The Display UI Map


and the Maintenance
UI Map

Address

10
Install Event ST,
CH, X

Related Service
Point

Service Point
Identifier

Service Point
Contact

SP / Market
Participant

ON/ OFF
History
X

Device Config.

Legend
Trans. Data

The Display Map


Service Script

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

4 - 44

Copyright 2010, Oracle. All rights reserved.

4-2 Solution
Lookup
1

Navigate to Admin / L / + Lookup to add a new lookup that contains the valid
value for an electric SP's solar installation flag. Please prefix your Lookup Field
Name with your initials (in real life - this would be prefixed with CM).

4 - 45

Copyright 2010, Oracle. All rights reserved.

4-2 Solution
Field
2

Navigate to Admin / F / + Field to add a new field that references the solar
lookup flag and that contains the label to be used whenever this field is
referenced. The same Field Name used for the lookup must be defined.

4 - 46

Copyright 2010, Oracle. All rights reserved.

4-2 Solution
Business Object - Define Parent BO
3.1

Navigate to Admin / B / Business Object and find DM_StandardServicePoint (the BO you are extending).
Click Duplicate to duplicate this BO. When prompted, please prefix your new BO with your initials (in real life - this
would be prefixed with CM).

Change the description to include your initials Electric Service Point

Change the parent to the BO you are


extending (which is a demo version of the
base-package service point BO). Bottom
line - you are creating a grandchild BO.

4 - 47

Copyright 2010, Oracle. All rights reserved.

4-2 Solution
Business Object - Define BO Schema
3.2

Navigate to Business Object - Schema tab and define the schema

Your BO's schema should include the BO youre


extending plus your additional element
Feel free to defined the required= and default= values
so the FW defaults a blank value to "unknown"
After saving your BO, click View Schema to
ensure you BO's schema contains the original
elements plus the new element

4 - 48

Copyright 2010, Oracle. All rights reserved.

4-2 Solution
UI Map - Display Map
4.1

Return to the Business Object - Main tab and click on the info string of the Display UI Map
option (this will navigate to the UI Map page with the demo service point's UI map displayed).
Click Duplicate to duplicate this UI map. When prompted, please prefix your new map with your
initials (in real life - this would be prefixed with CM).

Change the description to include your initials Electric Service Point - Display

4 - 49

Copyright 2010, Oracle. All rights reserved.

4-2 Solution
UI Map - Define HTML and Schema Of Display Map
Navigate to UI Map - Schema tab and define the HTML and the
schema of your new map

4.2

Add this HTML immediately after


the Consumption Profile HTML

Change the name to be your BO's


code

The Solar Installed field will go at


the bottom of the first section

4 - 50

Test your UI map - you should see


your new element

Copyright 2010, Oracle. All rights reserved.

4-2 Solution
UI Map - Maintenance Map
4.3

Return to the Business Object - Main tab and click on the info string of the Maintenance UI
Map option (this will navigate to the UI Map page with the demo service point's UI map displayed).
Click Duplicate to duplicate this UI map. When prompted, please prefix your new map with your
initials (in real life - this would be prefixed with CM).

Change the description to include your initials Electric Service Point - Maintenance

4 - 51

Copyright 2010, Oracle. All rights reserved.

4-2 Solution
UI Map - Define HTML and Schema Of The Maintenance
Map
Navigate to UI Map - Schema tab and define the HTML and the
schema of your new map

4.4

Add this HTML immediately BEFORE


the Consumption Profile HTML

Change the name to be your BO's


code

Test your UI map - you should see


your new element

The Solar Installed field will go


above Consumption Profile
4 - 52

Copyright 2010, Oracle. All rights reserved.

4-2 Solution
Script - Retrieve Information For Display Map
5.1

Return to the Business Object - Main tab and click on the info string of the Display Map Service Script
option (this will navigate to the Script page with the demo service point's display script displayed).
Click Duplicate to duplicate this script. When prompted, please prefix your new script with your initials (in
real life - this would be prefixed with CM).

Change the description to include your initials Electric SP - Retrieve Details for Display

4 - 53

Copyright 2010, Oracle. All rights reserved.

4-2 Solution
Script - Define Schema
5.2

Navigate to Script - Schema tab and define the schema

Change to reference your display map's code

4 - 54

Copyright 2010, Oracle. All rights reserved.

4-2 Solution
Update The BO Options
6

Return to the Business Object - Main tab and update the options to reference your UI maps and script

4 - 55

Copyright 2010, Oracle. All rights reserved.

4-2 Solution
SP Type
7

SP Type

Description

Identifying BO

RW-E-RES

RW - Electric Residential

Service Point Type

Reference your service type


Reference your BO. An instance of this BO will
be created when a service point of this type is
created

Reference your Electric ConGen device type

4 - 56

Copyright 2010, Oracle. All rights reserved.

4-2 Solution
Service Point
8

Navigate to Main / Device Installation / + Service Point to


add a new electric residential service point. Please select
your RW - Electric Residential SP type when prompted.

Notice your new attribute

Enter an address that you


can remember

4 - 57

Copyright 2010, Oracle. All rights reserved.

4-2 Solution
Activate The Device Configuration
9

Before a device configuration can be installed at a SP, it must be


Active (the system validates that all required MC types are linked to
the device config when it is activated). To do this, display your
electric solar device configuration on the Device Configuration Portal
and then activate it (note, you can click the device configuration link
in the various zones to navigate to this portal).

Defines if the SP is connected


to the water main

Click Activate to change the device


configuration's state to Active (only
Active
Enter an address thatdevice
you configurations can be
installed at a SP)
can remember

4 - 58

Copyright 2010, Oracle. All rights reserved.

4-2 Solution
Installation Event - Add
Use the SP context menu to add an installation event to the
service point

10.1

Find your electric ConGen


device configuration

Search by Serial Number (using your


initials) should show the devices that
you've set up

4 - 59

Copyright 2010, Oracle. All rights reserved.

4-2 Solution
Installation Event - Add Continued
After clicking Save, enter the remaining information

10.2

Enter this date as future exercises


will add measurements starting here

4 - 60

Copyright 2010, Oracle. All rights reserved.

4-2 Solution
Installation Event - Commission
Because this is a smart meter being installed, it must be
commissioned before it can record consumption

10.3

Click Commission to change the


installation event's state to
Commissioned

4 - 61

Copyright 2010, Oracle. All rights reserved.

4-2 Solution
Installation Event - Connect
Because this is a smart meter being installed, it must be
connected before it can record consumption

10.4

Click Connect to change the


installation event's state to
Connected

After it is connected, noticed the


On/Off History is now populated with
an entry

4 - 62

Copyright 2010, Oracle. All rights reserved.

4-2 Solution
Residential Electric SP Summary

If you've set everything up appropriately, the 360 search results


should look similar to the following when you search using your
SP's address

4 - 63

Copyright 2010, Oracle. All rights reserved.

Practice 4-3 (15 Minutes)


The installation event for smart meters requires a validation rule that works as
follows:

If the SP's Solar Installed flag indicates that solar is installed at the SP,
the device's device type must be RW-E-COGEN
Please break up into teams and perform the following:

Define the system event that will be used for this business rule

Define the BO on which the algorithm will be plugged in

Define the pseudo code of the algorithm's script


Note - please do not plug this in as each student does not have their own copy
of the target BO. Rather, your instructor will plug in a sample after all students
design the script that will implement this rule
The next slide provides a summary of the data that will be created by your
instructor
Please break up into teams and design the items listed above.

4 - 64

Copyright 2010, Oracle. All rights reserved.

4-3 Data Overview

Device Type

BO
Device

BO Algorithm

4
3
Algorithm

Service
Point
Install Event

Algorithm
Type

Device
Config.

Legend
Trans. Data

Admin Data

Script

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

4 - 65

Copyright 2010, Oracle. All rights reserved.

Config Tools Refresher: Validation Rules

Ad
BO d

A validation algorithm can be plugged in on a BO if more sophisticated


validation than can be defined using the schema attributes is required
Notice how validation algorithms are executed after the MO processing (e.g.,
core validation rules)

Individual Taxpayer

Ad
M d
O

Enter

2. MO Processing

4 - 66

Exit

Person MO
(Service)

Copyright 2010, Oracle. All rights reserved.

3. Validation algorithms

4-3 Solution
Pseudo Code Of New Validation Rule
This is a validation algorithm plugged in on the installation event BO
Recall that validation algorithms are supplied with the pre and post
images of the BO being added / updated / deleted
The installation event BO has FK's to SP and device configuration and
these must be retrieved to perform the following logic:
Retrieve SP
If solar is not installed, exit
Retrieve Device Configuration
Retrieve Device

If device's device type is not "RW-E-CONGEN", terminate with an


error
Hard coding a device type is not the most elegant logic. In real life,
there would probably be an attribute on the device or device type to
indicate if it could be installed at a SP with solar power. We are doing
this practice like this to save time.

4 - 67

Copyright 2010, Oracle. All rights reserved.

Instructor Only: 4-3 Solution


Use The BO Wizard To Set Up A Validation Algorithm
1

Navigate to Admin / B / + Business Object and select the D1-SmartMeterInstallEvent business


object. When this BO is displayed, use the Create a BO Algorithm Dashboard Zone to create the
suite of admin objects necessary to plug-in a Validation algorithm on this BO.

Click the Create Algorithm button to


initiate the wizard that sets up a new
algorithm type, algorithm, script, and
then plugs the algorithm into a
designated plug-in spot. The next slide
shows how this works

4 - 68

Copyright 2010, Oracle. All rights reserved.

Instructor Only: 4-3 Solution


Supply The Wizard's Parameters

Select BO Algorithm
Define the Name and
Description of the algorithm,
algorithm type and script
Define the BO System Event and
Sequence into which the
algorithm will be plugged

Click Save to set up these objects and


be transferred to the Script page
where the logic can be defined.

4 - 69

Copyright 2010, Oracle. All rights reserved.

Instructor Only: 4-3 Solution


Script - Set Up The Plug-In Script's Data Areas
The script needs to retrieve the SP, Device Config, and
Device BO's in order to implement its logic and therefore
each BO's data area must be defined
Notice how the Data Area Name has been
changed to be easier to read. This is
purely subjective and optional.

Notice how the LITE version of some BOs is used. If your


logic just needs to retrieve elements from a BO that are
defined in a LITE BO's schema, it should be used rather
than the "real" BO as the FW only performs the physical IO
to retrieve elements defined in the schema being retrieved.
Because we have not created a LITE version of the electric service point BO, we are
forced to use the "real" version. This validation is pretty light-weight and won't be
performed by high-volume processing so it's not worth the effort to create a LITE
version. If you were planning to retireve the solarInstalled element in a VEE rule, you
should consider creating a LITE version of the electric SP BO that includes this
element.
4 - 70

Copyright 2010, Oracle. All rights reserved.

Instructor Only: 4-3 Solution


Script - Steps

The FW supplies validation algorithms with every element of


the BO being validated (in its parms). In this case, the
validation is performed against the installation event BO and
this BO has FKs to SP and device configuration

INSTRUCTOR. Create a single Edit Data step


and paste in the following contents. Make sure
to add the error message cat/number
referenced in the script:
move "parm/hard/newBusinessObject/spId" to "ServicePoint/spId";
invokeBO 'RW-ElectricServicePoint' using "ServicePoint" for read;
// Escape if solar is not installed at the SP
if ("string(ServicePoint/solarInstalled) <= '20' ")
terminate;
end-if;
move "parm/hard/newBusinessObject/deviceConfigurationId" to "DeviceConfiguration/deviceConfigurationId";
invokeBO 'D1-DeviceConfigurationLite' using "DeviceConfiguration" for read;
move "DeviceConfiguration/deviceId" to "Device/meterId";
invokeBO 'D1-DeviceLite' using "Device" for read;
// Escape if a solar device type is referenced
if ("string(Device/deviceType) = 'RW-E-CONGEN' ")
terminate;
end-if;
terminate with error (90000, 12345);

4 - 71

Copyright 2010, Oracle. All rights reserved.

4-3 Solution
Create A New Solar Installed SP
Now that the D1-SmartMeterInstallEvent BO has this validation plug-in,
each student should test it by doing the following:
Create a new SP using your SP type and indicate that solar is
installed at the SP
Use the Device Replicator script to create a copy of the electric
ConGen meter
Try to install the new meter configuration at the new SP
The attempt should fail as your device type will not be RW-E-CONGEN

4 - 72

Copyright 2010, Oracle. All rights reserved.

D1-MeasurementCycle

Preview of 2.0.1

Copyright 2010, Oracle. All rights reserved.

Refresher
Recall that a SP will reference a measurement cycle and
route if any of the following functionality is required by an
implementation:
If the system should periodically push usage (bill
determinants) to subscribing systems
Because the CIS's billing process does not request bill
determinants; rather, it bills what the MDM pushes

If the system should download meter read information to


handheld devices
Because the utility has handheld devices and they have
made MDM responsible for the download (in addition to
the upload)

4 - 74

Copyright 2010, Oracle. All rights reserved.

A Measurement Cycle Has Routes And A Schedule


Measurement Cycle: Day 6
Scheduled Selection Date: 7-Sep-2010
A measurement cycle defines its
routes

Measurement Cycle: Day 6


Electric SP
15 Ocean Ave
Cycle: Day 6
Route: 003
Sequence: 121
A manually read SP
references a measurement
cycle, route and sequence
within the route

Routes
001
002

Route

Measurement
Cycle: Day
6
001
Download
(manual
read)
002
Download
(manual
read)
Scheduled
Selection
Date:
6-Oct-2010
003
Download (manual read)
Route
Schedule Type
004
Download (manual read)
Measurement
Cycle: Day
6
001
Download
(manual
read)
002
Download
(manual
read)
Scheduled
Selection
Date:
8-Nov-2010

003

003
Route

Download (manual read)


Schedule Type

004

004
001

Download (manual read)


Download (manual read)

002

Download (manual read)

003

Download (manual read)

004

Download (manual read)

This cycle has a monthly schedule


(any frequency is possible)

4 - 75

Schedule Type

Copyright 2010, Oracle. All rights reserved.

Measurement Cycle Has At Least 1 Route


The system requires every measurement cycle to have at
least one route
This is because the logic to periodically process the SPs
in a measurement cycle is handled route-by-route
Having routes is natural if the implementation requires MDM
to download meter reads to handheld devices
If the implementation only requires measurement cycles
because it must push information to the CIS, these cycles
must still have at least 1 route

4 - 76

Copyright 2010, Oracle. All rights reserved.

Preview - Measurement Cycle Batch Processes


(Being Released In 2.0.1)
3 batch processes manage the measurement cycle schedule
processing
Process: D1-CMCS
Create Pending Measurement Cycle
Schedule Routes

Process: D1-CSPSR
SP /
Measurement
Cycle Schedule /
Route

Create Pending SP / Measurement


Cycle Schedule / Routes

Handheld Activity

Process: D1-PSPSR
Process Pending SP / Measurement
Cycle Schedule / Routes

These processes are described on the upcoming slides

4 - 77

Measurement
Cycle Schedule
Routes

Copyright 2010, Oracle. All rights reserved.

Usage
Transaction

Process D1-CMCS: Create Pending Measurement Cycle


Schedule Routes
This process is only used if routes have the same schedule each month /
quarter /
This process simply copies the routes from the measurement cycle to the
measurement cycle schedule on/after the scheduled selection date (thus
saving the user the burden of defining the routes on every measurement cycle
If a user manually
schedule)
populates a cycle
Measurement Cycle: Day 6
Measurement Cycle: Day 6
Scheduled Selection Date: 6-Oct-2010
Route

Schedule Type

001

Download (manual read)

002

Download (manual read)

003

Download (manual read)

004

4 - 78

Route

Schedule Type

001

Download (manual read)

002

Download (manual read)

003

Download (manual read)

004

Download (manual read)

Download (manual read)

Copyright 2010, Oracle. All rights reserved.

schedule's routes (e.g.,


due to every other
month estimation), this
process will not touch
any of the cycle
schedule's routes

Process D1-CSPSR: Create Pending SP / Measurement


Cycle Schedule / Routes
This process creates an instance of SP / measurement cycle schedule route
for every service point in measurement cycle schedule / routes that are ready
for processing

The BO to create is defined in the batch control's parameters


Measurement Cycle: Day 6
Measurement Cycle: Day 6

Scheduled Selection Date: 6-Oct-2010

Scheduled Selection Date: 6-Oct-2010


Route

Schedule Type

001

Download (manual read)

002

Download (manual read)

003

Download (manual read)

004

Download (manual read)

Route: 001
Service Point: 938329818219
Business Object: D1-SP-MeasCycleSch
Measurement Cycle: Day 6
Status:
Pending Selection Date: 6-Oct-2010
Scheduled
Route: 001
Service Point: 818219938329
Business Object: D1-SP-MeasCycleSch

This process creates


these objects

4 - 79

Status: Pending

Copyright 2010, Oracle. All rights reserved.

Process D1-PSPSR: Process Pending SP / Measurement


Cycle Schedule / Routes
This process transitions the Pending SP / measurement cycle
schedule route BOs to their Complete state
Activity: 494948398398
Activity Type: Handheld download
Service Point: 938329818219
Installation Event: 818219938329
Business Object: D1-Handheld-Download
An implementation plug-ins the appropriate algorithms on the SP /
measurement cycle schedule route business object (as Enter
algorithms on the Complete state) to do the necessary work.

Status: Pending

Base-package algorithms are supplied, ready to be plugged in, that


can:
Create an activity to drive the handheld download interface
Create a usage transaction to drive the bill determinant push
Implementations can obviously develop additional algorithms and
plug them in to do other cyclical-based processing

4 - 80

Copyright 2010, Oracle. All rights reserved.

Review Questions

4 - 81

Copyright 2010, Oracle. All rights reserved.