Tiered Pricing

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?

“The single biggest problem in communication is the illusion that it has taken place.”
– George Bernard Shaw.

Toby Considine
TC9, Inc

TC Chair: oBIX & WS-Calendar

TC Editor: EMIX, EnergyInterop

U.S. National Inst. of Standards and Tech. Smart Grid Architecture Committee

Email: Toby.Considine@gmail.com
Phone: (919)619-2104

http://www.tcnine.com/
blog: www.NewDaedalus.com

emix message