Hon Robin Chapple questions the Minister for Energy regarding billing errors in the Karratha Pilbara Underground Power Project (PUPP), specifically addressing the cause of the errors, the extent of incorrect accounts, review of billing procedures, and lack of apology. The Minister acknowledges the errors and outlines steps taken to rectify the situation.

AnsweredQoN 912Legislative Council
Asked
10 September 2014
Portfolio
Energy

QuestionView source ↗

PILBARA UNDERGROUND POWER PROJECT
912. Hon ROBIN CHAPPLE to the
Leader of the House representing the Minister for Energy:
I refer to the
Pilbara underground power project in Karratha and the adjusted connection
accounts in a revised letter of assessment in Karratha.
(1) Why was this
mistake made?
(2) How many other
accounts have been established to be incorrectly apportioned to date?
(3) Is Horizon Power conducting an internal
review of its billing procedures with the City of Karratha to ensure that all
accounts are correct?
(4) If no to (3),
why not?
(5) Why has Horizon Power not apologised for
the mishandling of the rollout of the PUPP in Karratha to the residents and the
City of Karratha?

AnswerView source ↗

I thank the honourable member for some notice of this
question and provide the following response on behalf of the Leader of the House

(1) The City
of Karratha based its billing on a kilovolt ampere unit model. Although the
model accurately identified the capacity at the supply as 58 kilovolt ampere
units, it did not recognise the nature of the supply address being residential.
(2) Four per
cent of accounts levied were incorrect, largely due to misalignment between the
City of Karratha's billing model and Horizon Power's customer
information system.
(3) Yes.
(4) Not applicable.
(5) Horizon
Power has communicated with residents in the City of Karratha from the
commencement of the project in 2011 to the completion of phase 1 of the project
at the end of 2013.

Explore WA Government Data

Search the full archive in the free dashboard, or query programmatically via API.

Explore more