1 / 23

OASIS Standards for smart grids

OASIS Standards for smart grids. Light, loose integration for inter-domain communications Toby Considine TC9, Inc. Smart grids are meant to save resources through improved awareness and control. Inappropriate focus on process can actually waste resources.

mirari
Download Presentation

OASIS Standards for smart grids

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. OASIS Standards for smart grids Light, loose integration for inter-domain communicationsToby Considine TC9, Inc

  2. Smart grids are meant to save resources through improved awareness and control

  3. Inappropriate focus on process can actually waste resources • "If something is not worth doing, it`s not worth doing well" - Peter Drucker

  4. Simple Interfaces let us optimize interoperable services without committing to fixed processes

  5. Perspectives • Infrastructure Analyst, UNC • OASIS Technical Advisory Board • NIST Smart Grid Business & Policy WG • NIST Smart Grid Roadmap team • Chair, OASIS oBIX TC • Editor, OASIS Energy Interaction TC • Editor, OASIS EMIX TC • Convener, WS-Calendar

  6. Interacting with complex objects is hard Simplified schematic of flatworm nervous system

  7. Process integrations value effort over performance

  8. Process compliance merely defines poor performance

  9. Details are a barrier to interoperation

  10. Interfaces should hide details to enable interoperation

  11. Define business needs, not technical processes.

  12. We use composite protocols and security when we want them to scale. HTML IMAP / POP3 SMTP TELNET URIs ASCII / Unicode TCP IP

  13. Coordinate systems using result-oriented semantics

  14. Only coordination that is simple and secure will scale

  15. Building systems are becoming interoperating services

  16. Building-based agents will act as personal day traders in new energy markets • System agents defend mission • Enterprise (or home) defines value • Power Grid offers clearing market • Building agents choreograph response

  17. Zero net energy buildings will require ever more integration

  18. Power Load Management (TC57) Financial Instruments (ISO20022) Enterprise Scheduling (CalConnect) Three CIMs for inter-domain interaction

  19. Energy Interoperation TC • Interactions for DR and DER • Distinguishes between Managed and Collaborative energy • Direct load management by the utility or service provider • Economic messages to align interests. • Contributions • OpenADR from Lawrence Berkeley Labs • Business cases from NAESB

  20. Energy Market Information Exchange TC (EMIX) • Price and Product communication • Price is neither tariffs nor pricing • Energy characteristics of interest to consumer • Volatile products are time dependent

  21. Schedules for the internet of things (WS-Calendar) • Calendaring & Scheduling Consortium • IETF RFC 2445, 2446, 2447 – now RFC 5545… • Standard XML serialization • Common semantics for interactions in • Enterprise • Energy • Buildings • Finance • (PIMs and Vehicles)

  22. There are many standards, select the right one for the job

  23. Discussion Toby.Considine @ gmail.comwww.newDaedalus.com

More Related