Presentation is loading. Please wait.

Presentation is loading. Please wait.

Service Definitions A Framework For Standard Interface Development.

Similar presentations


Presentation on theme: "Service Definitions A Framework For Standard Interface Development."— Presentation transcript:

1 Service Definitions A Framework For Standard Interface Development

2 Abstract to Detail Standards Bodies Business Case Conceptual Architecture Use Cases Integration Requirements Sequence Diagram Patterns Services WSDL

3 Leveraging the Overlap CIMug UtilityAMI AMI Enterprise WG Standard Services

4 Key Collaboration Concept Standard building blocks are defined by CIMug –i.e., IEC working groups and other relevant industry groups such as Open Architecture Group (OAG), MultiSpeak Common industry practices are defined by the user community; the AMI Enterprise TF –by specifying how standard building blocks are used for popular scenarios with the resulting artifacts: Use cases specify required services Service definitions (WSDLs) contain the building blocks Artifacts are placed on smartgridipedia.org –Anyone may use a common industry practice or artifact.

5 Moving to a Standard

6 Requirements Traceability Business Benefits Business Processes Functional Requirements Integration Requirements Services Portfolio Interface Reference Model Application Portfolio Resulting from an activity in a Use Case Scenario Resulting from an flow in a Use Case Scenario Includes application services and common services.

7 Services Gap Analysis Map system actors to IEC 61968 systems/IRM Identify integration requirements Create common services per integration requirements Model service sequence diagram that includes vendor and legacy services Create services mapping and gap analysis! Review CIM and MultiSpeak services/schemas Identify Application services/schemas Gap analysis Documents

8 Scope

9 Conceptual Architecture

10 The Process Use Cases Business Processes Integration Requirements Services WSDLs XSDs

11 Business Process B1.3

12 Integration Requirements

13 Service Naming Based on IEC CIM Information Objects Examples: EndDeviceEvent MeterAsset MeteringReading MeterSystemEvent e.g. MeterReading

14 Operation Naming Patterns Utilizing IEC 61968-9 verb : e.g. CreatedMeterReading CREATE CREATED CHANGE CHANGED CANCEL CLOSE DELETE GET CLOSED CANCELED DELETED SHOW REPLY SUBSCRIBE UNSUBSCRIBE

15 Sequence Diagram

16 Recommended Services From AMI-ENT Service Inventory smartgridipedia.org

17 Utility Benefits As utilities pull in the same direction, de facto standards are created; economies of scale should yield: –Improved vendor response & support –Reduced product procurement costs –Reduced effort for requirements analysis and design –Reduced risk of overlooking requirements That are expensive to retrofit later –Reduced life-cycle costs

18 Artifacts - Resources Smartgridipedia.org - wiki –Business processes –WSDLs/XSDs –Information Objects AMI-ENT Task Force - Sharepoint –Issue Tracking –Discussion –Calendar

19 Future Service Definitions Work Sources of information for future service definitions work –PHEV use cases –OpenADR –OpenADE Business process map Integration requirements identification Rationalization/Harmonization New services documented


Download ppt "Service Definitions A Framework For Standard Interface Development."

Similar presentations


Ads by Google