1 / 14

Consumers Energy

Consumers Energy. Mark Ortiz March 9, 2011 . Interoperability – Why the Utility Cares. Rapid and evolving technology of the Smart Grid Need solutions that could evolve over time without costly rip and replacement or costly upgrades Requires Integration – LOTS of integration

gittel
Download Presentation

Consumers Energy

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Consumers Energy Mark Ortiz March 9, 2011

  2. Interoperability – Why the Utility Cares • Rapid and evolving technology of the Smart Grid • Need solutions that could evolve over time without costly rip and replacement or costly upgrades • Requires Integration – LOTS of integration • Onslaught of new applications and technologies • AMI, MDMS, HAN, DR, ADE, etc. • Challenges in a complex IT environment • Many custom systems, legacy system and technologies • Typically departmentally controlled – within “silos” • Need ability to govern, manage, and share resources • Both Intra-Enterprise and Inter-Enterprise systems/applications © 2008 Consumers Energy Company

  3. Main Goals • Common business processes • Common architecture principles and patterns • Common information model • Common integration services (functional & informational) • Tested interoperability between systems

  4. Service Definition Process • Step 1 – Business Process Analysis • Step 2 – Integration Requirements Detailed in Sequence Diagrams • Step 3 – Service and Operation Pattern Applied • Step 4 – Service and Information Object Identification and Harmonization • Step 5 – Service Definition (Artifacts Generation & Testing)

  5. Service Definition Process

  6. Key Architecture Considerations • Decoupling of end-point connections and business semantics • Guaranteed delivery • Managed integration • End point compliance to common business semantics and syntax for information exchange to the public (enterprise) • End point compliance to service patterns (interaction patterns, naming and structure patterns, and message exchange patterns) • Minimal business logic and transformation within the integration layer • Leverage IEC TC57 WG14 Interfaces

  7. Step 1) Business Process Analysis CreatedMeterReading (Receive) CreatedMeterReading (Send)

  8. Step 2) Integration Requirements Detailed in Sequence Diagrams 2) Integration with ESB WS WS

  9. Step 3) Service & Operation Pattern Applied • Service name: • Follows <Service pattern name>+<Information Object> (such as “SendMeterReading”/”ReceiveMeterReading” ) • Operation name: • <Operation pattern name>+<Information Object> (such as CreatedMeterReading)

  10. Existing Terminology and Metadata Model Driven Process- Based on an Enterprise Semantic Model Controlled Vocabulary (i.e. wiki, data dictionary, etc.) UML XML Schema

  11. Web Service Definition • Services defined in Web Service Description Language (WSDL). • WSDL documents generated based on a standard template • XSD decoupled from WSDL document (imported) for better maintenance and version control

  12. Standards Development • Industry Working Groups • OpenSG • Chair OpenAMI-Ent,Ent-Conformance • SGIP Testing and Certification Committee • Recent standards development and feedback • IEC TC57 WG14 • Meter Reading & Control Part 9 - 2.0 • IEC 61968 Part 1 and 1-2 • ZigBee Smart Energy Profile 2.0 • NAESB • Smart Services Learning Center • Virtual Smart Grid for End-to-End assessment and validation • Industry Working Groups SSLC Vision Center Standards Development Organizations © 2008 Consumers Energy Company 11 Proprietary and Confidential

  13. Interoperability - The IEC CIM is the Basis for a Common Systems Language for the Smart Grid Enterprise Applications Work & Asset Management MDM/MDUS • Billing • Customer • Information • Outage • Management • The same dictionary is used for multiple forms of system communication: • OpenAMI-Ent • OpenADE • OpenADR • SEP2.0 • Etc. CIM Enterprise Applications Automated Data Exchange One Dictionary Supports Many Forms of Communication OpenHAN, SEP2.0, Demand Response © 2008 Consumers Energy Company 12

  14. Questions & Comments

More Related