[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [emix] Differences between Past, Present, and Future
|
On the issue of pricing
power during system spikes let me add the following thoughts. We can price on
intervals at the resolution of the meter.
Perhaps a smart meter, its back haul communication and back office data
processing is programmed for 15 min intervals even though the physical meter
has the capability to sense the rate of delivery nearly instantaneously. If this is sufficient to price and manage
power spikes then that is all we need. If we need 5 min resolution,
or 4 second resolution, we can pass all that data back to the back office. Or, more sensibly we can process the date at the meter or gateway and
send back the sum of the product of price and energy for every 4 sec interval
in the 15 min interval, for example.
The back end communication and data processing won't need to be modified
significantly and the customer will have the incentive to respond to price
spikes. Additionally, I understand
that at least some smart meters can respond with special readings. So if an emergency occurs and a price
spike for a defined subinterval of say 10 seconds in a 5 minute interval is
sent then the meter can respond with a special reading for that subinterval,
without having to measure and price power on fine grained regular intervals. Edward G. Cazalet, Ph.D. 101 First Street, Suite 552 Los Altos, CA 94022 650-949-5274 cell: 408-621-2772 From: Toby Considine [mailto:tobyconsidine@gmail.com] On
Behalf Of Toby Considine This morning, I am thinking of the difference in product
description between an offer, an execution, and a call/delivery. Flow rates: Looking forward, I may be seeking, or offering, a power
source able to offer kW, At the end, I need to have bought kWh. Looking forward, I may be specifying that my call option
requires a response of 12 seconds or less. At the end, I may report that I ramped up in 4.5 seconds. If I am buying a blended product, I may specify at least 70%
renewable and 50% wind. At the end, I may report back, perhaps in [hourly]
intervals, that I was 83% renewable, including 54% wind. At the end, I may report back, perhaps in [hourly]
intervals, that I was 64% renewable, including 54% wind. If the latter, a discount/rebate/penalty may be
applied for any hour with renewables less than 70% Note: I know that the discount/rebate is out of scope, I am
thinking only of the information exchanges necessary to support it. Power spikes and maximum loads need to be priced. Many
markets today have a ratchet price, that if the consumer uses more
than a [3x base load] for more than [5 minutes][ever], the price charged
for the next year [doubles]. Future markets may see me contracting for fixed
load, with a different price for the instantaneous excess. There is no problem
if all customers are on committed energy purchases, and the excess is on the
spot market. Congestion may make the spot market infinitely expensive. How do
we report actual purchase of power peaks? My goals are clean slate. I am not interested in how it was
packed into last year’s meters, nor in expressing the complexity of a
tariff. I am assuming that EMIX delivered over the internet is all, and that no
special or historical knowledge is required of the system behind the ESI. tc "Energy
and persistence conquer all things." -- Benjamin Franklin
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]