Professional Documents
Culture Documents
Bulk Meter Readings - Ph2add
Bulk Meter Readings - Ph2add
"Acknowledgment: This material is based upon work supported by the Department of Energy
under Award Number DE-OE0000193."
Disclaimer: "This report was prepared as an account of work sponsored by an agency of the
United States Government. Neither the United States Government nor any agency thereof,
nor any of their employees, makes any warranty, express or implied, or assumes any legal
liability or responsibility for the accuracy, completeness, or usefulness of any information,
apparatus, product, or process disclosed, or represents that its use would not infringe
privately owned rights. Reference herein to any specific commercial product, process, or
service by trade name, trademark, manufacturer, or otherwise does not necessarily constitute
or imply its endorsement, recommendation, or favoring by the United States Government or
any agency thereof. The views and opinions of authors expressed herein do not necessarily
state or reflect those of the United States Government or any agency thereof."
Version History
Rev. Date Author Change description
A 02/25/2011 Bill Schleicher Initial Release
Modified to fit new format and incorporate
B 03/02/2011 Bill Schleicher
changes from document review
C 03/18/2011 Bill Schleicher Modifications from AEP review
D 05/03/2011 Bill Schleicher Modified after additional document review
E 08/08/2011 AEP workshop Various updates
F 08/25/2011 Tim Simmons Implement various recommended updates
Add Narrative, Interface Diagram, Notes section
G 10/12/2011 Brian D. Green
and update Actors and steps
H 10/31/2011 Ron Cunningham Final team review
Summary:
This use case addresses the four hour Bulk Meter Readings message collected by the AMI Head-End
system and the Scheduled Bulk Meter Readings that are exported to meter data management system
(MDM) every twenty-four hours. This also covers the distribution of those reads from the MDM and AMI
Head-End systems to the operational data store (ODS) and customer information system (CIS) systems.
Narrative:
The Meter Metrology Board (in the Smart Meter) continuously records the meter’s electical usage data
including 15 minute interval data blocks. Every four hours the Meter Metrology Board sends the Bulk
Meter Read Data (meter readings and 15 minute interval data for that four hour time block) to the NIC (in
the Smart Meter). The NIC sends the meter data through the AMI Network to the AMI Head-End. The
AMI Head-End sends batches of Bulk Meter Read Data to MDM where validation, estimation and editing
are completed. The MDM will also perform estimation for any missing meters. The MDM will then send
the bulk meter reads (typically for a 24 hour period) to CIS and ODS. The ODS will then send the bulk
reads to the Customer Web Portal.
Interface Diagram:
Operations
31
32
AMI Network
3 Smart Meter
Customer
Note(s):
The NIC and the Meter Metrology Board are part of the Smart Meter.
Actor(s):
The list of the actors and the roles that are participating in this use case described in the table
below.
AMI Head-End The AMI Head-End is the back office system than controls the
Advanced Metering Infrastructure.
CIS Customer Information System that is the system of record for customer
data and billing.
Customer Web Portal Interactive Web-site that is accessible via the Internet that enables the
exchange and display of information for the customer
MDM Consolidated information from Metering System, performs data
aggregation, validation, estimating and editing (VEE), and serves as a
message broker between CIS and AMI Head-End in this use case
Meter Metrology Board The board, internal to the Smart Meter, on which the functions of the
Smart Meter are configured and performed.
NIC AMI network interface component with Meter Metrology Board within
the Smart Meter.
ODS Operational Data Store is a sub-system of AEP’s data warehouse,
which stores operational data i.e. all metering events and messages.
The participating business function, its acronym and what they provide in this use case are
detailed in the table below.
MDM This is the Meter Data Management The Meter Data Management system
System which provides meter is responsible for collecting the
readings and billing determinants to reads from the AMI Head-End,
CIS. performing VEE services and
presenting the billing determinants
to CIS.
CIS Customer Information System is the Publishes changes to customer
system in place for customer data accounts, customer agreements,
and billing pricing, service location to Metering
System (MS). CIS also issues End
Device Control messages such as
the On Demand Request.
Customer Customer account information and Presentment and Exchange of
Web Portal energy usage data Customers’ account and energy
usage information
• Standard International Electrotechnical Commission (IEC) 61968 Message Definition format must
be followed to provide the Header, Request, Reply, and Payload should be used when defining
the messages for the design specifications. For the purpose of the use cases identified in this
document these have been omited as they are to be provided in the design specification for the
Bulk Meter Reading use cases.
• For the purposes of this use case the gridSMART integration layer and its adapters are not
included.
• When Bulk Reads are mentioned it refers to both interval and register reads.
Normal Sequence:
The sequences of events, showing the order in which they ocurr during the typical progression of this use
case are provided in the table below. The Sequence Diagram that graphically depicts the events is
presented immediately following the tables.
The following table provides a numbered sequence of steps describing the 4 Hour Bulk Meter Reading
process, showing the order in which they occur during the typical progression of this use case.
Integration Scenarios
Adapters will use the Common Information Model (CIM) in Extensible Markup Language (XML) to
send and receive messages and events.
The following are the points of integration that must be tested for this use case. Other non-CIM
message interfaces may be testable in this use case.
• NIC
AMI Head-End
• MDM
• CIS
MDM
• ODS
ODS • Consumer Web Portal
Pre-conditions:
Following are the list of events that must occur prior to processing Bulk Reads.
Post-conditions:
The following events or actions that may happen after or be caused by the completion of the
normal use case events, as well as the exceptions or alternative sequences are:
The following systems must be updated once the Bulk Meter Readings have been processed by
the MDM system.
• Bulk Meter reading are delivered to CIS
There are no exceptions, unusual events or alternate sequences defined for this use case.
The following XML Schema Definition (XSD) diagram shows the normative and informative parts
of the message. Not all of the International Electrotechnical Commission’s (IEC) – CIM message
optional elements must or will be used in the use of IEC – CIM for this specific use case.
References:
• 20100625 AEP Ohio Interoperability Plan V1.docx: Section 4.5.4 (Four Hour Bulk Feed
from AMI Head-End)
• 20100625 Use Cases EPRI Report_V2.4.doc: Section 5.3 (Scheduled Bulk Meter Read from
AMI Head End )
Issues: None
ID Description Status