1. Service Definition Technical Guide AMI-Enterprise

2. Getting Started Understand the framework Finding the artifacts Using the artifacts

3. Smartgridipedia.org Site map Note - multiple paths to artifacts Service inventory spreadsheet can be used to filter services specific to the user need Either path can be used to get artifacts specific to information object or business process

4. Example MDMS to Gas Outage integration Event processing

5. AMI Enterprise Interface Reference Model

6. Service Providers & Service Consumers Service Provider / Data Consumer –Meter Data Management System (MDMS) –Third Party Vendor –AMI Management System –Customer Information System (CIS) –Dispatch Center –Gas Outage Management System –Methane Alarm Application –Outage Management System (OMS) –Power Quality Event Controller Service Consumer / Data Provider –Head End –Third Party Vendor –MDMS

7. Find the Information Object from the Logical System Customer Information System –Information objects owned by CIS listed here Enterprise Asset Management –Information objects owned by EAM listed here Work Management System –Information objects owned by WMS listed here Outage Management System –Information objects owned by OMS listed here Meter Data Management System –Information objects owned by MDMS listed here Head End System –Information objects owned by Head End listed here

8. MDMS Information Objects ActivityRecord EndDeviceEvent EndDeviceFirmware LoadControlCommand MeterAssetConfig MeterReading MeterStatus MeterSystemEvent

9. Find the Service and Download the Artifacts Services –MeterSystemEventRequest –MeterSystemEvent WSDL/Design Artifacts –For the WSDL and XSD documents associated with these services please click here: Download MessageHeader.xsd MeterSystemEvent.wsdl MeterSystemEvent.xsd MeterSystemRequest.wsdl OutputData.xsd

10. Interaction Patterns Match interaction to your organization’s implementation

11. Send-Receive Services Interaction Pattern (ESB & Asynchronous) MDMSESB A Native API or Service T S/C OMS B Native API or Service T S/P S/C SendMeterSys temEvent CreateMeterSy stemEvent CreatedMeter SystemEvent ChangeMeterS ystemEvent ChangedMeter SystemEvent ShowMeterSy stemEvent ReceiveMeter SystemEvent CreateMeterSy stemEvent CreatedMeter SystemEvent ChangeMeterS ystemEvent ChangedMeter SystemEvent ShowMeterSy stemEvent Orchestration Service Operations Other interested parties…… Guaranteed delivery within ESB, plus internal routing…… S/C: Service Consumer S/P: Service Provider

12. Send-Receive Services Interaction Pattern (Transparent ESB & Asynchronous) MDMSTransparent ESB A Native API or Service T S/C OMS B Native API or Service T S/P S/C MeterSystemE vent CreateMeterSy stemEvent CreatedMeter SystemEvent ChangeMeterS ystemEvent ChangedMeter SystemEvent ShowMeterSy stemEvent MeterSystemE vent CreateMeterSy stemEvent CreatedMeter SystemEvent ChangeMeterS ystemEvent ChangedMeter SystemEvent ShowMeterSy stemEvent Orchestration Service Operations Other interested parties…… Guaranteed delivery within ESB, plus internal routing…… The transparent ESB can do transformation, but it's not recommended. One would use the transparent ESB to leverage middleware services such as connection management, persistence and error handling, but would not be doing Business Orchestration. Interaction patterns are not shown on the transparent ESB is because it will not be doing Business Orchestration (BPM).

13. MDMS A Native API or Service T S/C OMS B Native API or Service T S/P MeterSystemE vent CreateMeterSy stemEvent CreatedMeter SystemEvent ChangeMeterS ystemEvent ChangedMeter SystemEvent ShowMeterSy stemEventService Operations Send-Receive Services Interaction Pattern (Direct & Asynchronous) This is for the organization with no ESB, that uses a point-to-point implementation