27.10.2013 Views

FEI-FEVI 2010 EEC Report filed March 31, 2011 - FortisBC

FEI-FEVI 2010 EEC Report filed March 31, 2011 - FortisBC

FEI-FEVI 2010 EEC Report filed March 31, 2011 - FortisBC

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.

FORTISBC ENERGY INC. AND FORTISBC ENERGY (VANCOUVER ISLAND) INC.<br />

<strong>2010</strong> ENERGY EFFICIENCY AND CONSERVATION ANNUAL REPORT<br />

Technologies Program Area are expected to produce between 20 - 30% fewer GHG emissions<br />

than their diesel counterparts. 63 At this time, <strong>FEI</strong> estimates that the vehicles under the <strong>2010</strong><br />

program expenditures represent annual GHG savings of approximately 4,100 tonnes of CO2e<br />

per year, which is the equivalent to taking 800 passenger vehicles off the road. 64 As these<br />

NGVs enter regular operations <strong>FEI</strong> will track and monitor fuel consumption and distance<br />

traveled, which is used to calculate GHG emissions.<br />

10.2.3.3.2.1 Broad Support from <strong>EEC</strong> Stakeholder<br />

Group Consultation<br />

As stated above, one of the key principles developed through the <strong>EEC</strong> Decisions and the<br />

subsequent approved NSAs is the accountability mechanism that allows for oversight by the<br />

stakeholder groups. In accordance with this principle, an <strong>EEC</strong> Stakeholder Group was formed<br />

in December of 2009 (Please see Section 12: <strong>EEC</strong> Stakeholder Group Activities). The members<br />

of the <strong>EEC</strong> Stakeholder Group were solicited through regulatory stakeholders (those that have<br />

historically intervened in the Companies’ regulatory proceedings), from industry groups with<br />

whom the Companies interact, and from key contacts from the Companies’ Energy Solution and<br />

Community Relations departments. Additionally, the Companies have also done the following:<br />

• On <strong>March</strong> 11, <strong>2010</strong>, the proposed Innovative Technologies portfolio was presented to<br />

the <strong>EEC</strong> Stakeholders meeting (Please see Appendix H for a copy of this presentation<br />

and a copy of the attendees list). In particular, at the meeting, the Companies provided<br />

estimates of funds to be applied to various Innovative Technologies Program Area,<br />

including NGVs (see slides 5 and 6). The meeting also achieved several important<br />

goals, such as: 65<br />

a) Providing an opportunity to discuss details of how the weighted average TRC is<br />

applied to the Innovative Technologies portfolio.<br />

b) Allowing the <strong>EEC</strong> stakeholder group to discuss proposed Innovative Technologies<br />

program portfolio and program costs.<br />

c) Introducing the group to the feedback mechanism that affords them an opportunity to<br />

voice any concerns on the approach to Innovative Technologies, and to provide<br />

ongoing dialogue.<br />

• Following the <strong>March</strong> 11, <strong>2010</strong> meeting, all members of the Stakeholder Group were<br />

contacted to provide <strong>FEI</strong> and <strong>FEVI</strong> with feedback. The goal was to ensure any concerns<br />

they may have with the practical application of the weighted average TRC or with the<br />

portfolio of proposed activity for Innovative Technologies have been brought forward and<br />

noted. The Companies did not receive any opposition from the Stakeholder Group<br />

through its request for feedback.<br />

63<br />

Based on BC emissions factors from Natural Resources Canada’s GHGenius model 3.18 available at<br />

www.ghgenius.com<br />

64<br />

Calculation based on US EPA Greenhouse Gas Equivalencies Calculator<br />

65<br />

See page 114 of the <strong>EEC</strong> 2009 Annual <strong>Report</strong><br />

SECTION 10: INNOVATIVE TECHNOLOGIES PROGRAM AREA Page 216

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

Saved successfully!

Ooh no, something went wrong!