We will be carrying out essential maintenance activity on this website on Sat 20 June between 0800 and 1800 UK time. You might experience some brief interruption or loss of some functionality. We apologise for any inconvenience this may cause.
Standards Development
This standard will:
- provide guidance to help organisations develop their drainage (surface water, not sewerage) maintenance plans (e.g. checklists to assist when prioritising interventions to get best results out of limited maintenance budgets to minimise flooding and maximise other benefits of good drainage)
- signpost organisations to relevant industry specific guidance
- include good practice case studies to inspire and provide confidence
- include a section on things to consider in contingency plans, where budget falls short
- include tips on partnership working internally and externally (or signpost to useful documents).
Asset management organisations struggle with developing effective maintenance plans with limited operational (OPEX) budgets. This guide will help organisations think how to best prioritise their operational investment to align with their organisation’s objectives. It will do this by signposting to existing documentation, providing case studies and providing prompts for what they should consider (via checklist, or decision trees for example).
It will not:
- provide a standard solution, as each organisation has different needs; this would not be appropriate.
- repeat good practice that is written elsewhere, rather it will signpost people to relevant documents (eg CIRIA/ Sewers for adoption etc., EN752, BSEN 14654 series)
- cover renewals/ capital expenditure
- cover sewerage assets
New Proposal
You are now following this standard. Weekly digest emails will be sent to update you on the following activities:
You can manage your follow preferences from your Account. Please check your mailbox junk folder if you don't receive the weekly email.
You have successfully unsubscribed from weekly updates for this standard.
Comment on proposal
Required form fields are indicated by an asterisk (*) character.