Interface Specification Document

Transcription

1 Title: AMI Interface Specification Principal Investigator: Author: Reviewed by: Interface Specification Constituent Interface: AMI System Interface Interfaces described: AMI to CIS AMI to MDMS Version History Rev. Date Author Change description A 03/28/2011 Pre-release document B Initial Release C 4/22/2011 Incorporated revisions after review D 4/25/2011 Review feedback E 5/11/2011 Additional modifications based on comments Copyright

2 Title: AMI Interface Specification TABLE OF CONTENTS 1 Scope Significant Actors Interface Diagram CIS Functions to be performed MDMS Functions to be performed Functional Naratives Remote Connect / Disconnect Interface Infrastructure Network Layer Application Layer Specific Use Cases Messaging Contents of CIM Messages for Each Interfacing System Testing Matrix MDMS Tested Behaviors MDMS and AMI References: Issues: Miscellaneous Notes: Page 2 of 16 Copyright Rev. 2

3 Title: AMI Interface Specification 1 SCOPE This document describes the interfaces between the Advanced Metering Infrastructure (AMI) and the systems that it interacts with. The Advanced Metering Infrastructure is a two-way communication system that can reach every device in the distribution space (* Footnote: This does not preclude the use of parallel technology alongside the AMI system). Its purpose is to provide control and/or monitoring and recording of distribution devices. AMI systems consist of the hardware, software and associated system and data management applications that create a communications network between end systems at customer premises (including meters, gateways, and other equipment) and diverse business and operational systems of utilities and third parties. The AMI system provides the technology to enable the exchange of information between customer end systems and those other utility and third party systems. In order to protect this critical infrastructure, end-to-end security must be provided across the AMI systems, encompassing the customer end systems as well as the utility and third party systems that are interfaced to the AMI systems. Meter reading services provide the basic meter reading capabilities for generating customer bills. Different types of metering services are usually provided, depending upon the type of customer (residential, smaller commercial, larger commercial, smaller industrial, larger industrial) and upon the applicable customer tariff. The capabilities of the AMI system include: Periodic Meter Reading On-Demand Meter Reading Net Metering for Distributed Energy Resource (DER) and Plug-in Electric Vehicles(PEV) Feed-In Tariff Metering for DER and PEV Interface with Premise Area Network (PAN) devices Remote Connects and Disconnects Meter Event processing (Power Outage, Power Restoration, Voltage) Customers have access to a web portal to view usage information. This portal has its own database that is updated via an extract from the, providing a persistent storage mechanism to integrate data from disparate systems for the purpose of reporting and analysis. Page 3 of 16 Copyright Rev. 2

4 Title: AMI Interface Specification 2 SIGNIFICANT ACTORS This table contains the systems or people that are defined in this specification. Actor Nickname Description Notes MS (Metering System) Meter Data Management System Customer Information System AMI MDMS CIS The Metering Infrastructure responsible for automated energy monitoring and control, configuration of advanced meters, distribution automation, Meter Readings, Meter Events and Alarms 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. The Customer Information System acts as the system of record for Customer, Account, premise and rate information. Table 1 Actors 3 INTERFACE DIAGRAM This section contains either the block diagram to describe the interface between the system and the target systems. Page 4 of 16 Copyright Rev. 2

5 Title: AMI Interface Specification Figure 3-1 System Interface diagram Page 5 of 16 Copyright Rev. 2

6 Title: AMI Interface Specification Information Exchange 3.1 CIS Functions to be performed The Customer Information System (CIS) is the system of record for all customer, account, premise, and rate information. Interactions between the Automated Metering Interface (AMI) system and the CIS system will occur within the following functions: - The CIS system will dispatch requests for meter connects and disconnects and will receive and parse the data from the resulting reply transactions as reported by the AMI Head-End system. - The CIS system will be able to dispatch On-Demand read requests to the AMI Head-End server and parse the read data from the resulting CIM reply message. Exchange Definition This section describes the request reply and any other initiated events that are a part of this exchange between the AMI Head-End system and the CIS system. Remote Connect / Disconnect The CIS system will dispatch requests for meter connects and disconnects using the Create(EndDeviceControl) message. The AMI Head-End will translate this message into a proprietary command and dispatch this to the appropriate meter using the AMI Network infrastructure. Upon receipt of the message, the meter will either open the internal relay to shut off the power upon a disconnect or close the internal relay on a connect message. Upon completion or failure of the task, the meter will respond over the AMI network with a proprietary message and the AMI Head-End system will process the message and reply to the CIS with a Reply(EndDeviceControl) transaction. Page 6 of 16 Copyright Rev. 2

7 Title: AMI Interface Specification Figure 3-2 Connect / Disconnect Sequence Diagram 3.2 MDMS Functions to be performed The Meter Data Management System (MDMS) is system of record for meter reads and events. The MDMS will process all meter reads, apply validation and estimation strategies, and export billing determinants to the appropriate systems. Interactions between the Automated Metering Interface (AMI) system and the MDMS system will occur within the following functions: - The MDMS system will extract the meter read and event information from the files sent from the AMI Head-End system for bulk meter readings. - The MDMS system will be able to request on-demand reads from the AMI Head-End system and parse the meter read and event information returned from the AMI Head-End system. Page 7 of 16 Copyright Rev. 2

8 Title: AMI Interface Specification Exchange Definition This section describes the request reply and any other initiated events that are a part of this exchange between the AMI Head-End system and the MDMS system. On-Demand Readings The CIS system will be able to dispatch On-Demand read requests to the AMI Head- End server using the Get(MeterReadings) message. The message will be received by the AMI Head-End system which will send a proprietary request to the meter over the AMI Network. The results will be returned to the AMI Head-End which will translate the results and send them as a Reply(MeterReadings) message to MDMS so that it can extract the meter read information. Figure 3-3 On-Demand Read Sequence Diagram 4 FUNCTIONAL NARATIVES This section defines in detail how the AMI system will interface to the other systems. Reference diagrams are provided for each of the functions required for this interface. The AMI Head-End will communicate to the AMI network components using a proprietary messaging protocol. Communications to the legacy systems such as Page 8 of 16 Copyright Rev. 2

9 Title: AMI Interface Specification CIS and the OMS will utilize XML documents (transported via TCP-IP) that confirm to the CIM schema as defined in the MeterReadingAndControl- FDIS final.docx document. The detailed message content for each CIM message is provided in section six. The following diagrams detail the reference architecture for each of the functional interfaces between the AMI Head-End and the external system: 4.1 Remote Connect / Disconnect A remote disconnect is issued by the Customer Information System (CIS). The message is sent to the AMI Head-End and routed to the appropriate smart meter. When the message is received at the NIC ESP, it is converted and sent on to the Meter Metrology Board where the board causes the internal meter disconnect relay and sends a confirmation back to the NIC ESP to the AMI Head-End. The AMI Head-End sends the confirmation to the CIS to confirm it for the Customer Service Representative (CSR). Page 9 of 16 Copyright Rev. 2

10 Title: AMI Interface Specification Figure 4-1 Context Diagram for Remote Connect/Disconnect from CIS Page 10 of 16 Copyright Rev. 2

11 Title: AMI Interface Specification 4.2 Interface Infrastructure Network Layer The network layer for interconnection between the AMI Head-end and other legacy systems will be TCP/IP over Ethernet. Networking from the AMI Head- End system out over the AMI network to the endpoint devices is via a proprietary RF protocol over the AMI network Application Layer The AMI Head-End will communicate with the CIS system at the application layer using the Common Information Model (CIM) objects, expressed in XML, as defined in the MeterReadingAndControl-FDIS final document. 4.3 Specific Use Cases The following use cases apply to the interactions between the AMI Head-End system and the CIS system. o On-Demand Reads o Bulk Meter Readings o Remote Connect / Disconnect Page 11 of 16 Copyright Rev. 2

12 Title: AMI Interface Specification 5 MESSAGING 5.1 Contents of CIM Messages for Each Interfacing System To / From Systems CIS -> AMI AMI -> MDMS Message Type (Verb/Noun) Create/ EndDeviceControls Created/ MeterReadings Message Type Content (Class.Attribute) IdentifiedObject.mRID IdentifiedObject.Description EndDeviceControl.drProgramLevel EndDeviceControl.drProgramMandatory EndDeviceControl.priceSignal EndDeviceControl.scheduledInterval EndDeviceControl.type DemandResponseProgram.type DemandResponseProgram.validityInterval EndDeviceAsset.mRID EndDeviceGroup.groupAddress EndDeviceAsset.IdentifiedObject.mRID EndDeviceAsset.IdentifiedObject.name EndDeviceAsset.IndentifiedObject.Name.n ame EndDeviceAsset.IdentifiedObject.Name.Na metype.description EndDeviceAsset.IdentifiedObject.Name.Na metype.name EndDeviceAsset.IdentifiedObject.Name.Na metype.nametypeauthority.description EndDeviceAsset.IndentifiedObject.Name.N ametype.nametypeauthority.name EndDeviceGroup.IdentifiedObject.mRID EndDeviceGroup.IdentifiedObject.name EndDeviceGroup.IdentifiedObject.Name.na me EndDeviceGroup.IdentifiedObject.Name.N ametype.description EndDeviceGroup.IdentifiedObject.Name.N ametype.name EndDeviceGroup.IdentifiedObject.Name.N ametype.nametypeauthority.description EndDeviceGroup.IndentifiedObject.Name. NameType.NameTypeAuthority.name Reading.reason ReadingType.IdentifiedObject.mRID ReadingType.IdentifiedObject.name ReadingType.IdentifiedObject.Name.name ReadingType.IdentifiedObject.Name.Name Type.description ReadingType.IdentifiedObject.Name.Name Type.name ReadingType.IdentifiedObject.Name.Name Type.NameTypeAuthority.description ReadingType.IdentifiedObject.Name.Name Type.NameTypeAuthority.name ServiceDeliveryPoint.IdentifiedObject.mRI D ServiceDeliveryPoint.IdentifiedObject.nam e ServiceDeliveryPoint.IdentifiedObject.Nam e.name Use Case Referenced Connect / Disconnect Bulk Meter Reading Page 12 of 16 Copyright Rev. 2

13 Title: AMI Interface Specification ServiceDeliveryPoint.IdentifiedObject.Nam e.nametype.description ServiceDeliveryPoint.IdentifiedObject.Nam e.nametype.name ServiceDeliveryPoint.IdentifiedObject.Nam e.nametype.nametypeauthority.descripti on ServiceDeliveryPoint.IdentifiedObject.Nam e.nametype.nametypeauthority.name ServiceDeliveryPointGroup.IdentifiedObjec t.mrid ServiceDeliveryPointGroup.IdentifiedObjec t.name ServiceDeliveryPointGroup.IdentifiedObjec t.name.name ServiceDeliveryPointGroup.IdentifiedObjec t.name.nametype.description ServiceDeliveryPointGroup.IdentifiedObjec t.name.nametype.name ServiceDeliveryPointGroup.IdentifiedObjec t.name.nametype.nametypeauthority.de scription ServiceDeliveryPointGroup.IdentifiedObjec t.name.nametype.nametypeauthority.na me TimeSchedule.scheduleInterval.DateTimeI nterval.start TimeSchedule.scheduleInterval.DateTimeI nterval.end UsagePoint.IdentifiedObject.mRID UsagePoint.IdentifiedObject.name UsagePoint.IdentifiedObject.Name.name UsagePoint.IdentifiedObject.Name.NameT ype.description UsagePoint.IdentifiedObject.Name.NameT ype.name UsagePoint.IdentifiedObject.Name.NameT ype.nametypeauthority.description UsagePoint.IdentifiedObject.Name.NameT ype.nametypeauthority.name UsagePointGroup.IdentifiedObject.mRID UsagePointGroup.IdentifiedObject.name UsagePointGroup.IdentifiedObject.Name.n ame UsagePointGroup.IdentifiedObject.Name.N ametype.description UsagePointGroup.IdentifiedObject.Name.N ametype.name UsagePointGroup.IdentifiedObject.Name.N ametype.nametypeauthority.description UsagePointGroup.IdentifiedObject.Name.N ametype.nametypeauthority.name Page 13 of 16 Copyright Rev. 2

14 Basic Connectivity Network Interoperability Syntactic Interoperability Semantic Understanding Response to Failure Title: AMI Interface Specification 6 TESTING MATRIX GWAC Layers Device Pair AMI Head- End AMI Head- End AMI Network CIS YES YES YES YES YES MDMS YES YES YES YES YES AMI Head- End Legend: YES Testable Layers NO Proprietary / Inaccessible Layer N/A Not Applicable NO NO NO NO NO Table 2 Testing matrix including GWAC Stack Layers 6.1 MDMS Tested Behaviors MDMS and AMI The following behaviors should be tested between the MDMS and AMI systems: - The MDMS system processes meter read and event information sent from the AMI Head-End system for bulk meter readings. - The MDMS system is able to request on-demand reads from the AMI Head-End system and process meter read and event information returned from the AMI Head-End system. Page 14 of 16 Copyright Rev. 2

15 Title: AMI Interface Specification Basic Connectivity Basic connectivity over the AMI Network will be validated through the successful response requests processed by the system. Visibility to the AMI network connectivity will only be visible to testing through logs or database entries on the AMI Head-End system. Connectivity between the AMI Head-End and the MDMS will be validated by verifying the appropriate web service transactions are sent between the two systems. Syntactic Interoperability The following test for Syntactic Interoperability should be performed: - Validate that the AMI System has collected the bulk meter readings for all appropriate meters. - Validate that Scheduled Bulk Reads are sent from the AMI Head-End system to the MDMS via the Created/MeterReadings message. - Validate that the MDMS system properly processes and loads the bulk read data received from the Created/MeterReadings message into the MDMS database. - Validate that the MDMS can create an On-Demand read request and send a Get/MeterReadings message to the AMI Head-End. - Validate that the AMI Head end correctly receives the Get/MeterReadings message and processes the On-Demand read request. - Validate that the AMI Head-End creates a Reply/MeterReadings message in response to the On-Demand read request and returns the result to the MDMS. - Validate that the MDMS receives and processes the Reply/MeterReadings message from the AMI Head-End. 7 REFERENCES: The following documents were used as references in preparing this document. Page 15 of 16 Copyright Rev. 2

16 Title: AMI Interface Specification Use Cases EPRI Report_V _9_MeterReadingAndControl_FDIS final document 8 ISSUES: NONE ID Description Status 9 MISCELLANEOUS NOTES: NONE Page 16 of 16 Copyright Rev. 2