[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [energyinterop] Scope questions for discussion
Hi Sila, I would like to add: A.
In the Grid to Building direction: a. I think
there should be separate Emergency/Reliability signals, not just price. The
signal should be clear and not blurred by mapping to a price. b. Especially
with DER becoming more prevalent, upcoming maintenance/outage management events
need to be announced. Buildings would like to know when to turn on the
backup generators. And the construction crews would appreciate the
building make the circuits safe for them. c. A
unique Program Identifier is required because the building/meter/feeder might
be involved in a number of programs with a number of different service
providers. d. Other,
program specific information is required. As usual, Ed homes in to the
heart of it in the Curtailment program example, the baseline. B.
In the Building to Grid direction: a. To
whom does the custodian allow access to the data, for how long, which items,
and when each item was effective? And where should the custodian send the
report of who accessed what and when of my data. I don’t want
to be promiscuous with my data—I wouldn’t want burglars to identify
when my facility will be closed for Founder’s Day. b. Since
I may want to sell curtailment to more than one CSP, I will have to permit both
to access the same data. I leave it up to them to figure out a way to
make sure I’m not selling the same curtailment to two CSPs. Though
if someone can come up with a clear mechanism, I would love to hear it. C.
Trusted custodian of the data: a. Electricity
Distribution Entity – the one who has the data, now. Is always
affected by the load on the distribution infrastructure. Is the natural
monopoly the will likely always be regulated by politicians. b. Root
Certificate Authority-like entities. Used to authenticating.
Verisign doesn’t give me warm fuzzies, though. c. Others
you suggest. D.
And while I was blathering away here, I see Toby’s assessment
of customer forecasts. I like it. What’s it worth to
ya? Perhaps it’s a clause in the Program. So much for fun, back to work, B.O. February 3, 2010 Robert Old Siemens Industry, Inc. Building Technologies 1000 Deerfield Pkwy. Buffalo Grove, IL 60089-4513 Tel.: +1 (847) 941-5623 Skype: bobold2 bob.old@siemens.com www.siemens.com From: Larry Lackey [mailto:llackey@tibco.com] Great start, Sila. To the list
I’d suggest adding the building or facility’s bid/ask price for
consumption/DER over the relevant time period(s). This could, and probably should,
be iterative with the “Grid”, which might be multiple institutions,
providing forward costs for different intervals and buildings responding. Larry From: Sila Kiliccote [mailto:skiliccote@lbl.gov] If the grid has the historical data
from each facility plus weather data from each location, it can generate
forecasts for each building as well as the aggragate. The building's prediction
is an fyi for the grid This happens in the grod between utilities and
ISOs all the time sort of like a check/balance but may not be
necessary if not trusted. Sila
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]