18.11.2014 Views

Long Term Community Plan 2012-2022 - Hurunui District Council

Long Term Community Plan 2012-2022 - Hurunui District Council

Long Term Community Plan 2012-2022 - Hurunui District Council

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.

<strong>Hurunui</strong> <strong>Community</strong> <strong>Long</strong> <strong>Term</strong> <strong>Plan</strong> <strong>2012</strong> - <strong>2022</strong><br />

Development contributions are being collected to offset the<br />

negative economic effects on ratepayers for future upgrades of<br />

infrastructure in the <strong>District</strong> that are necessary to cater for<br />

growth. Such upgrades will help to ensure that the present level<br />

of provision of water supply services is kept sustainable.<br />

Shared Services<br />

We have an agreement with Waimakariri <strong>District</strong> <strong>Council</strong> to<br />

supply water to the Ashley and Sefton parts of their district. As<br />

such, approximately 1,650 Waimakariri ratepayers = many more<br />

residents pay the water proportion of rates directly to us.<br />

<strong>Community</strong> Outcomes<br />

1. A desirable and safe place to live<br />

2. A place with essential infrastructure<br />

Goals<br />

Supply water<br />

to meet<br />

consumer<br />

needs<br />

How we will<br />

achieve our Goals<br />

Provide a<br />

continuous ‘ondemand’<br />

supply of<br />

potable water to<br />

urban areas and a<br />

‘restricted’ supply<br />

of water to rural<br />

areas<br />

Undertake<br />

a residents<br />

satisfaction survey<br />

Maintain and<br />

improve water<br />

schemes to comply<br />

with DWSNZ<br />

Water tested for<br />

quality<br />

Goals and Performance Measures<br />

Performance Measures Current Situation 11/12 12/13 13/14 14/15 15+<br />

Major faults to water<br />

supply pipelines<br />

greater than 250mm<br />

diameter that affect<br />

customers are<br />

repaired within 24<br />

hours<br />

Resident satisfaction<br />

will continue to<br />

improve over the<br />

coming years<br />

Install 9 mixed oxidant<br />

treatment plants and<br />

eliminate the need for<br />

permanent boil water<br />

notices<br />

The safety standard<br />

of potable water<br />

improves each year**<br />

No such faults were reported<br />

during the year, but we have a better<br />

system in place now to capture this<br />

information and track the completion<br />

of work via our service request<br />

programme<br />

Resident satisfaction levels have<br />

improved since 2007 and in 2011<br />

it reached 82.5%* satisfaction with<br />

water quality. Satisfaction with<br />

quantity of rural water was 81%.<br />

We have 8 permanent boil water<br />

notices in place.<br />

Water standards are measured weekly<br />

or monthly depending on the number<br />

of consumers for each scheme.***<br />

Our potable water met safety<br />

standards in 85% of the district.<br />

√ √ √ √<br />

*Average score over three questions relating to pressure and flow of water (86%), appearance and taste (79%).<br />

**We have been working to improve the safety standard of potable water in the district each year and last year we reached 85%.<br />

***Each scheme, dependent on its risks at intake (shallow through river gallery would be high risk), has a monitoring regime associated with<br />

its need for sampling and testing for e-coli and total coliforms. The higher the risk, the more tests required for the scheme. High risk - once per<br />

week, low risk (deep intake) - once per month. A failure is an e-coli reading >1, which requires retesting until it achieves three clear results.<br />

√<br />

√<br />

√<br />

√<br />

√<br />

Financial Summary<br />

A financial summary for this activity is shown on the next page.<br />

77

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

Saved successfully!

Ooh no, something went wrong!