[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [emix] Tiered Pricing
When defining the problem think of Time of
Use Intervals as tiers that encapsulate consumption blocks (which are defined
in emix as blockPowerFullRequirements). This is the Zigbee slide in the link I
provided. I do not understand enough about what you
are proposing to say if it will work. It needs to be reflected in EiQuote somehow.
The SE2 Price message I provided does not attempt to get slick with recurrences.
They just publish a schedule that looks like above but with dates and times. Bruce
Bartell Xtensible Solutions From: Toby Considine
[mailto:tobyconsidine@gmail.com] On Behalf Of
Toby Considine The
solution I believe is to use power:blockPowerFullRequirements (which has tiers)
inside each interval through the day. In this way we can state what the tiers
are for each hour of the day and have the size (of the tiers) and or prices
(for each tier) vary within that interval. If
we are communicating day-ahead communication of tiers, that is all we need. As
a further issue, there may be a desire to template the communications, i.e., to
state weekdays vs weekends (assuming they had different price tiers). This we
could accomplish by: 1)
Building two unscheduled
sequences, as above. 2)
Sending 5 gluons (for M-F) starts
referencing one sequence, and two gluons (for Sa-Su) starts. Alternately,
one could want to announce that a particular tiered pricing in in place during
the summer months. This could be done by a Gluon with two vavailabilitys
(weekdays and weekends), and having each vavaialbility reference the appropriate
sequence. Do
we need more than that? tc “The
single biggest problem in communication is the illusion that it has taken
place.”
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]