23.03.2013 Views

FortisBC Inc. (FortisBC) Application for a Certificate of Public ...

FortisBC Inc. (FortisBC) Application for a Certificate of Public ...

FortisBC Inc. (FortisBC) Application for a Certificate of Public ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

1<br />

2<br />

3<br />

4<br />

5<br />

6<br />

7<br />

8<br />

9<br />

10<br />

11<br />

12<br />

13<br />

14<br />

15<br />

16<br />

17<br />

18<br />

19<br />

20<br />

21<br />

22<br />

23<br />

24<br />

25<br />

26<br />

27<br />

28<br />

29<br />

30<br />

31<br />

32<br />

Response:<br />

<strong>FortisBC</strong> <strong>Inc</strong>. (<strong>FortisBC</strong> or the Company)<br />

<strong>Application</strong> <strong>for</strong> a <strong>Certificate</strong> <strong>of</strong> <strong>Public</strong> Convenience and Necessity<br />

<strong>for</strong> the Advanced Metering Infrastructure Project<br />

Response to British Columbia Utilities Commission (BCUC or the Commission)<br />

In<strong>for</strong>mation Request (IR) No. 1<br />

Submission Date:<br />

October 5, 2012<br />

Page 252<br />

107.2.1 Are these time periods reasonably similar to that used in the<br />

Future Program Study by Navigant to estimate participant<br />

response to TOU rates? Please explain why or why not.<br />

At page 38 <strong>of</strong> the Navigant report, the authors note,<br />

We recommend using the BC Hydro CRI results as the impact from participating customers. BC<br />

Hydro is most similar to <strong>FortisBC</strong> in terms <strong>of</strong> climate, prices and demographics. As discussed<br />

below, these need to be adjusted <strong>for</strong> number <strong>of</strong> participation rates. We recommend assuming<br />

that 20% to 30% response rate is consistent with analyses that show that 20% to 30% provide<br />

most <strong>of</strong> the response to mandatory TOU programs, and make the voluntary programs (e.g. BC<br />

Hydro, Hydro One) consistent with the mandatory programs (Newmarket Hydro).<br />

The recommendation is based not on a specific set <strong>of</strong> time periods as an input to the analysis,<br />

but rather on the outcomes produced in the referenced studies. The BC Hydro CRI used peak<br />

time periods reflective <strong>of</strong> actual high use periods on its system rather than the long HLH time<br />

frames <strong>of</strong> the Mid-C index.<br />

The BC Hydro CRI used a single peak period defined <strong>for</strong> non-holiday weekdays from 4pm to<br />

9pm <strong>for</strong> the Lower Mainland and Fort St. John, November through February and a two peak<br />

period defined <strong>for</strong> non-holiday weekdays from 7am to 11am and from 4pm to 9pm <strong>for</strong> Campbell<br />

River on Vancouver Island, November through February. 5<br />

Response:<br />

107.2.2 Are these differences between the Mid-C based HLH prices and<br />

LLH prices similar to the peak/<strong>of</strong>f-peak generation prices typically<br />

seen in other jurisdictions with residential TOU rates? Please<br />

explain why or why not.<br />

A comparison <strong>of</strong> prices is not possible because neither the <strong>FortisBC</strong> AMI <strong>Application</strong> not the<br />

Navigant report use a set <strong>of</strong> TOU prices as a basis <strong>for</strong> estimating the customer participation rate<br />

or capacity and energy savings attributable to the introduction <strong>of</strong> the conservation rate. Rather<br />

than developing a set <strong>of</strong> rates and then determining an estimated customer response to those<br />

rates, recommendations were provided by Navigant based upon the experience in other<br />

jurisdictions.<br />

5 Conservation Research Initiative Residential Time <strong>of</strong> Use Rate <strong>Application</strong> August, 2006

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!