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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

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 189<br />

The assumption that the number <strong>of</strong> marijuana production sites at <strong>FortisBC</strong> is proportional to the<br />

provincial number <strong>of</strong> residential electric customers is based on the following:<br />

• The majority <strong>of</strong> confirmed paying and non-paying marijuana sites are located in privately<br />

owned residences or out buildings versus commercial establishments.<br />

• The rationale is endorsed in Pr<strong>of</strong>essor Neil Boyd’s Opinion (Please BCUC IR1 Q86.1).<br />

• The 2004 <strong>Public</strong> Policy Paper by Stephen T Easton calculates an implied number <strong>of</strong><br />

grow houses by region from the number <strong>of</strong> RCMP busts. Based on Table 5 in the<br />

paper, the proportionate share <strong>of</strong> the provincial estimate in the <strong>FortisBC</strong> service territory<br />

ranges from 5-8% when allowances are made <strong>for</strong> municipal utilities and geographical<br />

overlap with BC Hydro. Please see BCUC IR1 Q74.1.<br />

The research article, “The Marihuana Indoor Production Calculator” filed by Commission staff as<br />

Exhibit A2-2 estimates 10,000 marijuana grow sites existed in BC in 2003. The 2011 Plecas<br />

report filed as Exhibit A2-1 calculates the number <strong>of</strong> sites at 13,206 in 2010. The growth in the<br />

estimated number <strong>of</strong> sites from 2003 to 2010 does not seem to indicate downward pressure<br />

from the 2006 Amendment on the number <strong>of</strong> marijuana grow operations in BC. This is not<br />

surprising given the lucrative nature <strong>of</strong> this illegal business.<br />

Response:<br />

83.3 Is it <strong>FortisBC</strong>’s experience that the marijuana grow operations involving electricity<br />

theft are generally the same size as marijuana grow operations that do not<br />

involve electricity theft? Please explain why or why not.<br />

<strong>FortisBC</strong> does not have in<strong>for</strong>mation that would allow it to compare the size <strong>of</strong> paying and<br />

stealing marijuana grow operations.<br />

<strong>FortisBC</strong> has limited experience with paying marijuana grow operations since it is interested<br />

primarily in detecting and deterring theft. <strong>FortisBC</strong> does not request in<strong>for</strong>mation from the RCMP<br />

<strong>for</strong> marijuana sites that have been busted and are paying <strong>for</strong> electricity.<br />

<strong>FortisBC</strong> does ask the RCMP <strong>for</strong> the number, size and timer settings <strong>of</strong> the lights at busted<br />

grow operations stealing electricity in order to invoice <strong>for</strong> losses.

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

Saved successfully!

Ooh no, something went wrong!