Lessons Learned In Developing an Inventory of Storm Sewer Systems

Transcription

1 Lessons Learned In Developing an Inventory of Storm Sewer Systems June 21, 2012 OWEA 2012 Annual Conference Michael Ellerbrock, PE, LEED-AP BD+C Group Manager, Engineering & Design Infrastructure Management

2 Let s begin with an assumption WE WANT TO DO A STORM WATER INVENTORY!

3 Outline + Misconceptions + Lesson #1 Project Plan + Lesson #2 Estimating Features + Lesson #3 Be Prepared + Lesson #4 Make the Most of Your Data + Summary

4 Recipe for disaster: We need to get crews in the field collecting data now

5 Recipe for disaster: We don t have the time or the budget to change the process

6 Recipe for disaster: We know what data you need!

7 Recipe for disaster: Full speed ahead!

8 LESSON #1 PROJECT PLAN Begin with the end in mind

9 Project Plan Determine the Purpose + What you want to collect + Why you want to collect it + What you are going to do with it after it is collected + How are you going to maintain it?

10 Project Plan Determine the Limits + Defined by NPDES Permit / SWMP + May or May Not be Specific + OEPA MS4 Permit + Private Property Boundaries?

11 Trotwood PWD Program Manager (Woolpert) Data Collection (GSP/Dynotec Team) Project Plan Define Project Team & Responsibilities + Client Included + Communication Protocol TASK DESCRIPTION Program Management QA / QC Plan Accept plan Develop and implement plan Minimal Coordination The QA/QC Plan will document the data collection criteria and consistency requirements for the project. This will be standard for which the data collection efforts will be considered accepted or rejected. The QA/QC plan will include the following: critical field procedures; data dictionary; domain pick lists; verifying values in the database (domain checking); connectivity; logical checks (including checking in/out invert and diameter relationships, slopes, direction of flow, etc.); data accuracies and tolerances for acceptance; etc. The plan will also address the following: project goals; responsible personnel from each firm; process for addressing process changes; and weekly notification process. The Program Manager will develop the QA/QC Plan with minimal coordination with the Data Collection firm.

12 Project Plan Establish Definitions & Detail + Define Structure Parts to inventory + How much detail for each part? + Define Survey Point Location + Basis for feature definition in database.

13 Project Plan Establish Definitions & Detail 22 pipes or a bridge?

14 Project Plan Data Dictionary + Define necessary attributes + Review with users

15 Project Plan Data Dictionary

16 Project Plan Data Dictionary

17 Project Plan Accuracy & Quality + Determine Accuracy of Data Required + Consider Objective / Subjective data + Quality Control + Quality Assurance on 2 levels + Consider End Use of Inventory + Accuracy costs money, Quality should not

18 Project Plan Documentation + Organize Project FIRST! + Data Dictionary + Project Management Plan + QA/QC Plan + Database Work Plan + Field Procedures Manual + Project Communications Plan + Update after pilot study is complete + other significant project changes

19 Project Plan Documentation Field Manual + Data collection methodology + Include procedures for dealing with public + Photos/Details of structure types

20 Project Plan Do a Pilot Study + Test of the Project Plan + What didn t work? + UPDATE PROJECT PLAN DOCUMENTS

21 Project Plan Good Preparation Pays Off + Upfront work saves time and money! + Results in less field time spent searching + Reduces collection of unnecessary points + Reduces processing of unnecessary points + Reduces rework

22 LESSON #2 ESTIMATING FEATURES How many features are there?

23 Estimating Features + Fulton County, Georgia + County Estimated 16,000 based on existing data + Revised After Pilot Study to 33,000 + Finished near 20,000 + City of Trotwood, Ohio + RFP for 4,500 Structures + Revised Estimate of 6,000 during inventory + Finished near 6,300

24 Estimating Features Fulton County timeline

25 Estimating Features + Keep monitoring the number + Unit cost for structures can help

26 LESSON #3 BE PREPARED What Can Go Wrong?

27 Be Prepared Record Documents + Gather background information pertinent to your inventory limits. + Historic documents reveal what is not currently visible

28 Be Prepared Right-of-Way Limits

29 Be Prepared Inaccessible Structures + Entire team is involved in inaccessible structures + Review Discrepancies as a team + Revisits Cost Money!

30 LESSON #4 POST INVENTORY Make the Most of your Data

31 Post Inventory Immediate Use / Application + Documented procedures will provide clarification later. + Document Decisions/Changes. Even non-changes. + Next Step: IDDE + MCM 6 + MCM 2

32 Post Inventory Make the most of the data + Transportation + GIS + Fire + Maintenance + Emergency Repairs + Create Work Orders + Map Updates + HAZMAT + Planning + Future Construction

33 Lessons Learned summary + Lesson #1 Begin with the End in Mind + Lesson #2 How Many Features? + Lesson #3 What Can Go Wrong? + Lesson #4 Make the Most of Your Data

34 QUESTIONS?

35 Contact: Michael Ellerbrock, PE, LEED-AP BD+C Group Manager, Engineering & Design Infrastructure Management Woolpert