130 likes | 170 Views
AMI-Enterprise. Service Definition Technical Guide. Getting Started. Understand the framework Finding the artifacts Using the artifacts. Smartgridipedia.org. Site map Note - multiple paths to artifacts Service inventory spreadsheet can be used to filter services specific to the user need
E N D
AMI-Enterprise Service Definition Technical Guide
Getting Started • Understand the framework • Finding the artifacts • Using the artifacts
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
Example MDMS to Gas Outage integration Event processing
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
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
MDMS Information Objects • ActivityRecord • EndDeviceEvent • EndDeviceFirmware • LoadControlCommand • MeterAssetConfig • MeterReading • MeterStatus • MeterSystemEvent
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
Interaction Patterns Match interaction to your organization’s implementation
Orchestration Send-Receive Services Interaction Pattern (ESB & Asynchronous) Service Operations MDMS ESB OMS A B Native API or Service Native API or Service S/C S/P S/C S/P T T Guaranteed delivery within ESB, plus internal routing…… Other interested parties…… S/C: Service Consumer S/P: Service Provider
Orchestration Send-Receive Services Interaction Pattern (Transparent ESB & Asynchronous) Service Operations Interaction patterns are not shown on the transparent ESB is because it will not be doing Business Orchestration (BPM). MDMS Transparent ESB OMS A B Native API or Service Native API or Service S/C S/P S/C S/P T T Guaranteed delivery within ESB, plus internal routing…… Other interested parties…… 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.
Send-Receive Services Interaction Pattern (Direct & Asynchronous) Service Operations This is for the organization with no ESB, that uses a point-to-point implementation MDMS OMS A B Native API or Service Native API or Service S/C S/P T T