Answers embedded below.
Bruce Bartell
Xtensible Solutions
Mobile: +1.321.258.6500
| www.xtensible.net
From: William Cox
[mailto:]
Sent: Thursday, July 28, 2011 3:26
PM
To: Bartell, Bruce
Cc: ;
Subject: Re: [emix] Tiered Pricing
Bruce and all --
Some management-style3 questions...
Much of this is structured for the California
block and tier tariffs, is it not?
>This is not just
for California.
BC Hydro used the same structure along with other utilities in different
states.
How much is SEP2 information model to reflect that?
>It is fully modeled in the SEP2.
How fluid is that information model? Is it a moving target? Is it
anchored (at least for 2.00) by the block and tier tariffs above?
>The SEP 2.0 pricing model is
based on IEC61968 which is a stable model although its 2nd release is still in
circulation for comments. In the current SEP 2.0 model, block tiers are
contained by TOU but the original CIM model can deal with the other way around
(i.e., block to contain tou tiers)
Thanks!
bill
--
William Cox
Email:
Web: http://www.CoxSoftwareArchitects.com
+1 862 485 3696 mobile
+1 908 277 3460 fax
On 7/28/11 12:30 PM, Bartell, Bruce wrote:
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
Mobile:
+1.321.258.6500
| www.xtensible.net
From: Toby Considine
[mailto:] On Behalf Of Toby Considine
Sent: Thursday, July 28, 2011
12:13 PM
To:
Subject: [emix] 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?
tc
“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:
Phone: (919)619-2104
http://www.tcnine.com/
blog: www.NewDaedalus.com
