1 / 27

Refining our SGUI definition

Refining our SGUI definition. U.S . experts IEC PC118 Paris meeting Nov 8-9, 2012. Presentation Goals. Review the architecture and definition of the SGUI. Review submitted country use cases [separate presentation]

elia
Télécharger la présentation

Refining our SGUI definition

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. Refining our SGUI definition U.S. experts IEC PC118 Paris meeting Nov 8-9, 2012

  2. Presentation Goals • Review the architecture and definition of the SGUI. • Review submitted country use cases [separate presentation] • Present a simple framework (taxonomy) that organizes the use cases and will help us to evaluate standards ability to meet use case requirements. [separate presentation]

  3. Smart Grid Domains and existing standards NAESB ESPI/ Green Button, AS/NZS4755 WMO WXXM Weather Exchange Model OpenADR OASIS EMIX,OASIS WS-Calendar IEC Common Information Model OASIS Energy Interoperation ASHRAE Facility Smart Grid Information Model SPC201P IEC 61850, ICCP, … SGUI • ASHRAE BACnet, LONtalk • ECHONET, SEP 2.0 • Modbus, Profibus • OPC-UA, ISA standards • CEA 2045 • …

  4. Actors and Information

  5. Virtual Top and End Nodes Energy Interoperation/EPRI terminology A VEN has exactly one VTN in a given relationship A VTN has one or more VENs in a given relationship VTN VEN VEN VEN VEN

  6. DR Signal Distribution Overview A • A: Source of DR signal (price, event, etc.) • Blue Lines—SGUI • B—Communication • C: Recipient of DR Signal (e.g. Device/Facility EMS) VTN B VTN=Virtual Top Node VEN= Virtual End Node C VEN

  7. Same Services, Same Patterns In each example the service request and response flow across the lines Some actors have multiple roles The following examples are for DR event management Energy Interoperation also supports Transactive Control/Transactive Operation

  8. The SGUI is not a single interface between “the grid” and “the facility” The SGUI may be a series of interfaces along the path from source to sink. Each only knows its direct connections.

  9. More Than Utility-CustomerFor Example: A is a wholesale market operator issuing a DR signal B, C, D, E are first level aggregators F, G, H are second level aggregators and B’s customers I, J, L are stores and are G’s customers L is also E’s customer

  10. Example: Price Distribution A is a market operator distributing prices to B, C, D, and E B is a building price server that distributes prices to controllers F, G, H that manage floors in its building I, J, K are HVAC units on floor G L is a thermal storage unit that can run on alternate fuel supply with price from E.

  11. Boundaries Depend on DeploymentSGUI can be used in facility domain G is a Facility ESI I, J, K, L are components of the facility and produce or consume energy Service Requests go to G, which adjusts them and then distributes them to I, J, K, L Information is at ESI, can distribute with BACnet, LON, SEP, …. Facility

  12. Boundaries Depend on DeploymentSGUI outside of facility domain G is a Facility ESI Information is at ESI, can distribute with BACnet, LON, SEP, …. Facility

  13. Cloud DeploymentRemote Energy Management in the Cloud A is wholesale market sending DR signal B is retail utility G is a remote Building EMS in the cloud Facility energy management is performed by G talking to facility components Facility devices

  14. An Actor and Its Interfaces Your Application Code Actor Not to scale VEN Interface VTN Interface

  15. Decouple at the Red Boundary • Application code evolves on its own timeline • The VEN/VTN interfaces and information model is stable • Define a clear mapping between your application code and the SGUI interface Your Application Code Actor VEN VTN

  16. Selected Standards and Developing Specs • There is great diversity of Virtual End Nodes (facilities, etc) • Industrial • Commercial/Institutional • Residential • And hybrids • Large investments across the world • Integration with existing management systems is critical to success of SGUI

  17. Standards for Actors—VENs (1) A A A • ISO/IEC 14543 • ISO 16484-5 (BACnet) • ISO/IEC 14543-3 (KNX) VTN VTN VTN B B B C C C VEN VEN VEN

  18. Standards for Actors—VENs (2) A A A • ISO/IEC 14543-4 (Echonet) • ISO/IEC DIS 14908 (LONtalk) • ISO/IEC 15045 (Residential Gateway) VTN VTN VTN B B B C C C VEN VEN VEN

  19. Standards for Actors—VENs (3) A A A • ISO/IEC TR 15067 (Energy management HES) • ISO 18012 (Product interoperability guidelines) • IEC 62056-61/62 (Metering, tariff) • ISO 20022 (Financial systems) VTN VTN VTN B B B C C C VEN VEN VEN

  20. Standards for Actors—VENs (4) A A A • oBIX (Building automation and integration) • ISA 100, etc (Industrial) • OPC UA (Industrial) VTN VTN VTN B B B C C C VEN VEN VEN

  21. Developing Standards—VENs (5) A A A • Smart Energy Profile • ISO CD/ASHRAE SPC201P (Facility Smart Grid Info Model) VTN VTN VTN B B B C C C VEN VEN VEN

  22. PC118 Focus on the Interface Power Engineering Facility Management and control

  23. PC118 Focus on the Interface We’re doing the interface that ties them all together—service-oriented, minimal information, maximum flexibility TC57 CIM, markets, Grid operations IEC TC57 Standards ISO TC205 FSGIM and many facility automation standards FSGIM, BACnet, KNX, LON, ECHONET, ISO/IEC JTC1 standards, previous slides, and many more

  24. Integration Across Many Standards • Must work for all “reasonable” models and the actors presenting the VEN and VTN interface • Cannot extend each actors’ interfaces and models • They don’t work with each other at details • Viz. “Internet Terminal” problem and solution • Extract key information to communicate • See Grid-Interop 2011 paper on DR event core semantics • The world as it is, not as we would have it.

  25. Summary • We’ve defined our view of the SGUI • Many things on the two sides of the SGUI • Not everyone will accept “speak the same language” • Therefore must do integration approach • Some standards-based environments will be on both sides of the SGUI • Build what we need from a simple pattern • Build an environment where parties collaborate

  26. Supplementary Slides

  27. Aside: The Internet Terminal Problem • In the early days ARPANET was defined to “share resources” • Large computers (supercomputers of the day) • Many manufacturers • But the many manufacturers each had their own special ways to connect to their mainframes • You could have an expensive unique terminal for each kind of computer in your office • OR define an abstract, simplified terminal that could communicate what’s needed • The “internet terminal” let to the telnet definition • Simple communication of core information

More Related