Re: [obix] RE: oBIX 2.0 and EMIX (UNCLASSIFIED)

[Markus Jung <mjung@auto.tuwien.ac.at>]

The alignment of oBIX with EnergyInterop including EMIX and OpenADR 
sounds really interesting in terms of ICT research on smart grids.

But at this point I am not sure how the different information models can 
be combined in a meaningful way.

Currently, I think the use case for these standards is for example some 
kind of gateway that can be used for energy management either in 
residential homes or commercial buildings. Such a gateway would use an 
oBIX integration layer to cope with the heterogeneity found in nowadays 
home and building automation systems. Based on oBIX object model as 
semantic integration layer one can provide for example an OpenADR 
interface to the smart grid.

So I think the standards have different scopes but it is quite meanigful 
to use them in one piece of software.

From my point of view it would make sense to see how the oBIX object 
model can be extended to support use cases like demand side management. 
This might include some contracts or facets that allow to express the 
power demand of appliances or to express some tasks and schedules that 
have a certain energy consumption and potential for load management.

Am 17.07.2013 05:26, schrieb Bogen, Chris ERDC-RDE-ITL-MS:
> Classification: UNCLASSIFIED
> Caveats: FOUO
>
> Are you thinking that the "trivial extensions to oBIX 1.x" come in the way of concise artifacts like the encodings and bindings specs?
>
> On the surface it sounds straightforward and interesting.  What is the market penetration of EMIX?
>
>
> Chris Bogen, Ph.D.
> Computer Scientist
> US Army Corps of Engineers
> Engineer Research Development Center
> Vicksburg, MS
>
> -----Original Message-----
> From: obix@lists.oasis-open.org [mailto:obix@lists.oasis-open.org] On Behalf Of Considine, Toby
> Sent: Sunday, July 14, 2013 10:52 AM
> To: obix@lists.oasis-open.org
> Subject: [obix] 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.
>
>   
>
> Comments?
>
>   
>
> tc
>
>   
>
>   
>
>   
>
> ________________________________
>
> "You can cut all the flowers but you cannot keep spring from coming."
>
> -Pablo Neruda
>
> ________________________________
>
> Toby Considine
>
> Chair, OASIS oBIX TC
>
> Editor, OASIS EMIX, Energy Interoperation Finance & Administration IT University of North Carolina Chapel Hill, NC
>
>    
>
> Email: Toby.Considine@ unc.edu <mailto:Toby.Considine@fac.unc.edu>
> Phone: (919)962-9073
>
> http://www.oasis-open.org
> http://www.NewDaedalus.com
>
>   
>
>   
>
>
> Classification: UNCLASSIFIED
> Caveats: FOUO
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php


--
Dipl.-Ing. Markus Jung
Research Assistant
mjung@auto.tuwien.ac.at
Tel. +43 1 58801-18322
Fax +43 1 58801-18391
Institute of Computer Aided Automation
Treitlstr. 1-3/4. Stock/E183-1
Vienna University of Technology