emix — archive

[David Webber]

David / Toby,

Beware of ocean boiling!!!

In my experience building intelligent expert systems - there are a slew of potential inputs and sources of control information and rules.

Within OASIS though - all we can do is focus on core concepts and build that.  I'm sure implementers will find all kinds of value-add features for their products to differentiate themselves in the marketplace.  We don't need wire XML formats to support those!

As an example look at the OASIS emergency work with the CAP spec'.  That is incredibly simple XML constructs - many argue too simple.  Nevertheless - time to market was key for them - so they went with simplest path - and as a result - there is an array of vendors offering all kinds of products - and devices that use CAP messages.

I believe that KISS here for V1.0 is also vital.

DW

<snip>Is the question of “plane of control” the same as “where is the human interface?”, unless (as in the case of the refrigerator) there is no human interface? And in the case of a campus or microgrid there are effectively multiple human inputs that impact a single system. There is the building operator and the human resources office and the Energy management director’s office and the “how green we want to be” CEO office. Each of these impacts decisions about conditions on energy use, and how and when and why. Hopefully they all work together to have a consistent policy for response to price signals and other priorities.
It’s the “other priorities” that Toby brought up on the call. Price is not all that matters. Maybe source matters. Maybe local matters—that might be factored in as a price adder on external power. Other priorities might be reflected as exceptions in the policy for a particular system, like “the bowling alley will never go into reduced-power mode when the director has bowling league”.</snip>


Thanks, DW