Subject Matter Expert: Author: Reviewed by: Margaret Goodrich Bill Schleicher Tim Simmons / Margaret Goodrich. Bulk Meter Readings

Transcription

1 Bill Schleicher Tim Simmons / Bulk Meter Readings "Acknowledgment: This material is based upon work supported by the Department of Energy under Award Number DE-OE " 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 B 03/02/2011 Bill Schleicher Modified to fit new format and incorporate 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 G 10/12/2011 Brian D. Green H 10/31/2011 Ron Cunningham Final team review Add Narrative, Interface Diagram, Notes section and update Actors and steps Copyright 2011 American Electric Power Company

2 Bill Schleicher Tim Simmons / 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 () every twenty-four hours. This also covers the distribution of those reads from the 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 where validation, estimation and editing are completed. The will also perform estimation for any missing meters. The 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. Page 2 of 12 Copyright 2011 American Electric Power Company Rev. 8

3 Bill Schleicher Tim Simmons / Interface Diagram: Operations Customer Web Portal 47 ODS CIS AMI-Head End 20 2 AMI Network 3 Smart Meter Customer Note(s): The NIC and the Meter Metrology Board are part of the Smart Meter. Page 3 of 12 Copyright 2011 American Electric Power Company Rev. 8

4 Bill Schleicher Tim Simmons / Actor(s): The list of the actors and the roles that are participating in this use case described in the table below. Name AMI Head-End CIS Customer Web Portal Meter Metrology Board NIC ODS Role description The AMI Head-End is the back office system than controls the Advanced Metering. Customer Information System that is the system of record for customer data and billing. Interactive Web-site that is accessible via the Internet that enables the exchange and display of information for the customer 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 The board, internal to the Smart Meter, on which the functions of the Smart Meter are configured and performed. AMI network interface component with Meter Metrology Board within the Smart Meter. Operational Data Store is a sub-system of AEP s data warehouse, which stores operational data i.e. all metering events and messages. Participating Business Functions: The participating business function, its acronym and what they provide in this use case are detailed in the table below. Acronym Business Function/Abstract Component Services or Information Provided AMI ODS Advanced Metering for energy monitoring and recording, load control capability, tariff/rate data collection. Operational Data Store for metering events and messages. Energy monitoring and control, configuration of advanced meters, offers new rate programs, distribution automation, Meter Readings, Meter Events and Alarms. Operational Data Store is a subsystem of the data warehouse, which stores operational data i.e. all metering events and messages. Page 4 of 12 Copyright 2011 American Electric Power Company Rev. 8

5 Bill Schleicher Tim Simmons / Acronym Business Function/Abstract Component Services or Information Provided CIS Customer Web Portal This is the Meter Data Management System which provides meter readings and billing determinants to CIS. Customer Information System is the system in place for customer data and billing Customer account information and energy usage data The Meter Data Management system is responsible for collecting the reads from the AMI Head-End, performing VEE services and presenting the billing determinants to CIS. Publishes changes to customer accounts, customer agreements, pricing, service location to Metering System (MS). CIS also issues End Device Control messages such as the On Demand Request. Presentment and Exchange of Customers account and energy usage information Assumptions / Design Considerations: Standard International Electrotechnical Commission (IEC) 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. Page 5 of 12 Copyright 2011 American Electric Power Company Rev. 8

6 Bill Schleicher Tim Simmons / 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. Use Case Step Triggering Event Description Of Process Information To Be Exchanged Producer Receiver Message Type 1 A predefined poll from the AMI Head- End Meter Metrology Board collects meter reading data ANSI C12.19 Table Data Meter Metrolog y Board Internal 2 Meter Metrology Board sends Bulk Meter Read Data to NIC ANSI C12.19 Table Data Meter Metrolog y Board NIC write ANSI C12.19 Table Data 3 NIC relays Bulk Meter Read Data to the AMI Network Bulk Meter Read Data NIC AMI Network Proprietary 4 AMI Network relays Bulk Meter Read Data to the AMI Head-End Bulk Meter Read Data AMI Network AMI Head- End Proprietary 5 A predefined push from the AMI Head-End AMI Head-End system sends the Bulk Meter Read Data to (Typically y batches for a 24 hour period) Bulk Meter Read Data Batch AMI Head- End Create/MeterR eadings 6 performs Validation, Estimation, and Editing (VEE) of the Bulk Meter Read Data Bulk Meter Read Data Internal 7 performs 24 hour Estimated Meter Reads Data for any missing meters Estimated Meter Reads Data Internal Page 6 of 12 Copyright 2011 American Electric Power Company Rev. 8

7 Bill Schleicher Tim Simmons / Use Case Step Triggering Event 8 A predefined push from the 9 A predefined push from the Description Of Process sends Bulk and Estimated Meter Read Data to CIS system (typically z batches for a 24 hour period) sends Bulk and Estimated Meter Read Data to ODS (typically z batches for a 24 hour period) 10 ODS sends Bulk and Estimated Meter Read Data to the Customer Web Portal (Consumer Interaction) Information To Be Exchanged Bulk and Estimated Meter Read Data Bulk and Estimated Meter Read Data Bulk and Estimated Meter Read Data Producer Receiver Message Type CIS Create/MeterR eadings ODS Create/MeterR eadings ODS Custome r Web Portal Create/MeterR eadings Page 7 of 12 Copyright 2011 American Electric Power Company Rev. 8

8 Bill Schleicher Tim Simmons / Page 8 of 12 Copyright 2011 American Electric Power Company Rev. 8

9 Bill Schleicher Tim Simmons / 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. Actor Interface Points AMI Head-End NIC CIS ODS ODS Consumer Web Portal Pre-conditions: Following are the list of events that must occur prior to processing Bulk Reads. The must be synchronized with CIS for metering data All meters must be registered with the AMI Head-End System 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 system. Bulk Meter reading are delivered to CIS Page 9 of 12 Copyright 2011 American Electric Power Company Rev. 8

10 Bill Schleicher Tim Simmons / Exceptions / Alternate Sequences: There are no exceptions, unusual events or alternate sequences defined for this use case. Use Case Step Triggering Event Description Of Process Information To Be Exchanged Producer Receiver Message Type Page 10 of 12 Copyright 2011 American Electric Power Company Rev. 8

11 Bill Schleicher Tim Simmons / Message Type(s) Diagram: 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. Page 11 of 12 Copyright 2011 American Electric Power Company Rev. 8

12 Bill Schleicher Tim Simmons / References: Use Cases or other documentation referenced by this use case include: AEP Ohio Interoperability Plan V1.docx: Section (Four Hour Bulk Feed from AMI Head-End) Use Cases EPRI Report_V2.4.doc: Section (Scheduled Bulk Meter Read from AMI Head End ) 61968_9_MeterReadingAndControl_FDIS final.docx: Section 5.4 (Meter Reading Messages); Annex H.6 (XML Schemas for MeterReadings) Section J.2 (GetMeterReadings) Issues: None ID Description Status Miscellaneous Notes: None Page 12 of 12 Copyright 2011 American Electric Power Company Rev. 8