Some References and Links
I know it is hard to keep up with the specifications and changes; I can barely keep up and I am putting the smart grids specifications out there. What follows is a brief summary of the road to OpenADR 2.0.
OpenADR 1.0 is out of date.
OpenADR 2.0 is almost here. It relies on the joint work of xcal/ws-calendar for its time/schedule communications. This work was done in joint effort by an IETF-centered group (CalConnect) and by OASIS
In the IETF:
- RFC5545 B. Desruisseaux Internet Calendaring and Scheduling Core Object Specification (iCalendar), http://www.ietf.org/rfc/rfc5545.txt, IETF RFC5545, proposed standard, September 2009
- CalendarResource C. Joy, C. Daboo, M Douglass, Schema for representing resources for calendaring and scheduling services, http://tools.ietf.org/html/draft-cal-resource-schema-03, (Internet-Draft), November 2010.
- FreeBusy E York. Freebusy read URL, http://www.calconnect.org/pubdocs/CD0903%20Freebusy%20Read%20URL%20V1.0.pdf, April 2009
- RFC5546 C. Daboo iCalendar Transport-Independent Interoperability Protocol (iTIP), http://www.ietf.org/rfc/rfc5546.txt, IETF RFC5546, proposed standard, December 2009.
- Vavailability C. Daboo, B. Desruisseaux, Calendar Availability, http://tools.ietf.org/html/draft-daboo-calendar-availability-02, IETF Internet Draft, April 2011
- xCal C. Daboo, M Douglass, S Lees xCal: The XML format for iCalendar, http://tools.ietf.org/html/draft-daboo-et-al-icalendar-in-xml-08, IETF Internet-Draft, April 2011.
Standard schemas for the above can be found in the namespace document of the current Public Review of WS-Calendar (ends on the 14th)
There are open-source implementations using these specs. VAVAILABILITY is only a draft in the IETF, but we rely heavily on it in EMIX and Energy Interoperation. If you are using communications tied to smart energy or to facility use, I reccommend that you read that specification.
For describing product, price, and market terms, Energy Market Information Exchange is used. As so much of EMIX is communication of schedule, it relies heavily on WS-Calendar conformance. This specification is also out for public review, until the 26th.
OpenADR 2.0 is a profile of Energy Interoperation. That specification is soon out for Public Review. You can find “pre-review” versions at:
- http://www.oasis-open.org/committees/download.php/42869/energyinterop-1-0-spec-wd26.pdf
- http://www.oasis-open.org/committees/download.php/42870/energyinterop-1-0-schemas-wd26.zip
One thing that the work lacks is discovery. EnergyInterop is designed to be recursive, so a utility or aggregator might expose a VEN interface up to the wholesale market, while exposing a VTN surface down to the home, office, industrial site, or microgrid. Each of those exposes a VEN on the outside; each may, in turn, choose to use EI internally, with a VTN communicating with numerous VENs.
Some interesting work is attempting to extend the model of OpenADR/Energy interoperation down to appliances and devices. This will place a greater premium on Discovery.
http://datatracker.ietf.org/doc/draft-jennings-energy-pricing/?include_text=1
In Committee, we have talked some about WS-DD as a possible mode, but have not gone beyond the simplest discussion.