OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

obix message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: oBIX 2.0 and EMIX

We have long discussed support of EMIX and oBIX 2.0, but never discussed what it might mean.


EMIX (Energy Market Information Exchange) is a definition of the Information Model about energy that is needed to Smart Grids / Smart Energy. EMIX is incorporated into the OASIS Energy Interoperation specification (EnergyInterop). Some of you are aware of the work being done by the OpenADR Alliance to profile EnergyInterop for use in specific utility markets. Others may be tracking the Transactive Energy Association (TEA), another profile of EnergyInterop,  and its work to enable widespread use of distributed energy sources and renewables.


EMIX does *not* define a particular Schema. It defines an Information Model that happens to be described using an XSD.  Anything that allows the complete information model to be assembled, and expressed in a manner that is transformable into the EMIX model, is conformant with EMIX.


In oBIX, the bulk reporting format appears to be compatible with the Report Services as defined in EnergyInterop. That format is being accepted by the OASIS WS-Calendar TC as the Streams format, now in second public review. EnergyInterop Report Services are largely a way to convey EMIX information as it varies over time. The initial work on EnergyInterop Report Services was influenced by the pre-existing work in oBIX 1.0


While the first impulse is to think that EMIX describes Power, it is also used for many other attributes. EMIX can describe Volt-Var, of critical importance to Ancillary Services on smart grids, for example. Discussions are underway to describe other energy forms such as Steam, Warm Water, Chilled Water, and Natural Gas in ways that are conformant with EMIX


Well, enough background.


In cartoon form, EMIX and oBIX intersect in Metering. The general function of a meter can be described by EMIX, and the actual measurements on that meter submitted as telemetry. In Report Services, the Meter is described in the header, and the readings in the telemetry. There are several classes of readings: Actual or Estimated, episodic or monotonic (Think Trip Odometer vs car Odometer), actual or projected, etc.


As I listened to Craig discussing the metadata capabilities of oBIX 1.1 in the recent weeks, I think that we can claim conformance with EMIX by defining the standard use of EMIX-based tags on a point that happens to be a metrology point. This brings a conforming application into conformance with this suite of smart energy standards.


One of the functions of OpenADR is to request Reports against particular metrology points. One of the queries supported is the question “What would you [the end node] be willing to measure for me. Each of these then becomes trivial extensions to oBIX 1.x.








"You can cut all the flowers but you cannot keep spring from coming."

-Pablo Neruda

Toby Considine


Editor, OASIS EMIX, Energy Interoperation
Finance & Administration IT
University of North Carolina
Chapel Hill, NC


Email: Toby.Considine@ unc.edu
Phone: (919)962-9073




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]