[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [obix] Energy Priorities
To my mind, the SG stops at the ESI, the Energy Services
Interface. I can certainly imagine that some oBIX devices, say iLONs and some
Green JACEs, opt to have an ESI interface. If so, that is probably another
service, but not necessarily in oBIX. I think both sides share an interface. I think that inside an
ESI, there may be a campus-size microgrid – and the grid standards on the
outside are used on the inside, and there may be more ESI’s downstream.
Inside the ESI, there may be a single BAS, or a dozen. They may be only BAS[s]
or there may be appliances and stereos. "If something is not worth doing, it`s not worth doing
well" - Peter Drucker
From: Ron Bernstein
[mailto:ron@lonmark.org] Here here! I completely agree with you Brian. The big concern I
have is that there is a strong division line at the meter which will create two
separate and non-interoperable elements of what could and should be a single
unified system architecture. The big question – “Will the smartgrid
roadmap stop at the meter?” If the answer is no, the oBIX is vital in the
process. If yes, the issue is moot. From: Brian Frank
[mailto:brian.tridium@gmail.com] I personally have an issue with the philosophy that the BAS
needs to understand pricing and associated financial products. That seems
incredibly complex to push that sort of sophistication all the way out to the
edge. What I think BAS should provide: - real-time and historical data from electrical
meters - real-time and historical data on the major electrical
load equipment - ability to immediately or schedule load
reduction to respond to an ISO (or other) event The BAS should understand KW (or MW) reductions. It
shouldn't need to understand how demand reductions map to pricing or rate
structures. I believe oBIX is ideal for these functions. On Thu, Nov 5, 2009 at 11:35 AM, Toby Considine <Toby.Considine@gmail.com> wrote: [no
normative non-committee] oBIX
members are probably as dissatisfied with the OpenADE solutions for sharing
Energy Usage information as am I. But why? If
you were to have a one page description of the Energy Usage Priorities for
Buildings and the Smart Grid, what would it look like? Examples
to get the thought processes running: -
Direct live read-only access to the revenue meter entering the building
(x1) -
Direct live read-only access to the price stream for energy entering the
building (x2) -
Discovery of any other “smart systems” in the building (x3,
X4) -
Direct live read-only access to the current energy use of any other
“smart systems” in the building (x1) -
Discovery of any sub-meters in the building (x3) -
Direct live read-only access to the sub meters in the building (x1) -
Notification of DR event / price applying to building (x5) -
Verification of performance under event (x5) to building ESI (x6) -
Verification of aggregate performance under event from Building ESI to
supplier (x6 or x7) Assuming
we have these items, can we put together the building system energy wish list?
If we had this list, could we get it to be a SG priority? If
we did, would it come back to oBIX as X1
– potential standard oBIX contract X2
– EMIX, as part of EnergyInterop X3
– WS-DD is the natural choice (to me) for discovery. X4
- Once we do discovery, there is the profile for energy use and interaction
(which may be different than, say, the device profile for Printing…what
is the relationship between oBIX systems and Energy Profiles…. X5
– Energy Interop: what do oBIX systems know of Energy Interop
Requests… X6
– Tail end of standard energy contract? X7
– Back to Energy Interoperation. May be part of an oBIX system, but
likely another service…. So,
that was stream of consciousness, not a proposal. What would you write… tc "Energy and persistence conquer all things."
-- Benjamin Franklin
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]