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

33<br />

34<br />

35<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 />

114.0 Reference: Project Environment<br />

Response:<br />

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

Exhibit B-1, Tab 8.0, Section 8.2.3, pp. 128-129<br />

Use <strong>of</strong> BC Hydro’s MDMS (Meter Data Management System)<br />

“Lowest Possible Cost<br />

Submission Date:<br />

October 5, 2012<br />

Page 279<br />

All three utilities recognized that there were potential cost benefits attributable to<br />

collaboration. Potential cost benefits can be generally categorized in two ways:<br />

Shared Infrastructure: Cost savings and reduced infrastructure requirements may be<br />

achieved when two or more utilities share all or part <strong>of</strong> the advanced metering<br />

infrastructure. Any shared infrastructure may also result in some increased cost related<br />

to the need to separate the customer data required by each utility and to customize the<br />

shared infrastructure to each utility’s requirements.<br />

S<strong>of</strong>tware systems, particularly the MDMS, could potentially be shared. However, an<br />

initial cost analysis showed that any savings that might be achieved with a joint s<strong>of</strong>tware<br />

license would be <strong>of</strong>fset by complexities related to 1) integrating the MDMS with two<br />

different HESs and two different Customer In<strong>for</strong>mation Systems (which is where the bulk<br />

<strong>of</strong> s<strong>of</strong>tware costs will be spent) and 2) segregating customer data in a manner that would<br />

ensure customer privacy.”<br />

HES: means Head End System and is the AMI System component that manages the<br />

customer meters and other endpoint devices.<br />

MDMS: means Meter Data Management System and is the component with the AMI<br />

System that manages data transmitted from the meter.<br />

114.1 Please explain further the integration <strong>of</strong> the MDMS and the HES. Specifically,<br />

explain how the proposed <strong>FortisBC</strong> HES differs from the existing BC Hydro HES,<br />

including the supplier <strong>of</strong> the two HES systems and the costs to integrate it with a<br />

MDMS.<br />

<strong>FortisBC</strong> utilizes enterprise application integration s<strong>of</strong>tware as the integration plat<strong>for</strong>m <strong>for</strong><br />

integrating and exchanging service-oriented and message-oriented data between IT systems,<br />

including the HES , MDMS and billing system. <strong>FortisBC</strong> is not familiar with BC Hydro’s<br />

enterprise service bus, enterprise application integration s<strong>of</strong>tware, infrastructure and s<strong>of</strong>tware<br />

configurations and versions. This makes it very difficult to estimate the difference in integration<br />

costs between the <strong>FortisBC</strong> and BC Hydro IT environments.<br />

As stated in Exhibit B-1, Tab 8.0, Section 8.2.3, “… an initial cost analysis showed that any<br />

savings that might be achieved with a joint s<strong>of</strong>tware license would be <strong>of</strong>fset by complexities<br />

related to 1) integrating the MDMS with two different HESs and two different Customer

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

Saved successfully!

Ooh no, something went wrong!