Presentation is loading. Please wait.

Presentation is loading. Please wait.

2005 Indiana GIS Conference March 9-10 - Indianapolis, Indiana City of Columbus, Ohio CMOM and Sewer System Digital Mapping Presented by: Derek Mair, GIS.

Similar presentations


Presentation on theme: "2005 Indiana GIS Conference March 9-10 - Indianapolis, Indiana City of Columbus, Ohio CMOM and Sewer System Digital Mapping Presented by: Derek Mair, GIS."— Presentation transcript:

1 2005 Indiana GIS Conference March Indianapolis, Indiana City of Columbus, Ohio CMOM and Sewer System Digital Mapping Presented by: Derek Mair, GIS Section Manager Date/Time: March 10, 2005 – 10:15AM

2 Introduction CMOM – Capacity Maintenance Operations and Management –Program administered by EPA to ensure that Utilities are eliminating known Sanitary Sewer Overflows (SSO) and properly maintaining their systems Consent Order (July 2002) –Legal agreement between City of Columbus and Ohio EPA to outline CMOM program implementation. Includes points and deadlines.

3 Introduction Project Team Selected –EMH&T is part of a team led by Brown and Caldwell, LLC EMH&T Tasks –System Evaluation and Capacity Assurance Plan (SECAP) (paragraph 13) Stop and mitigate impact of SSO’s –Mapping (paragraph 8) 8.f – Maintain a map 8.g – Proper Management of Information

4 Comprehensive Mapping Project –Scope Definition –Project Management Plan –Schedule and Prioritization –Application Definition and Development –Data Development Approach –Quality Control Standards and Procedures –Deliverable Format Results and Findings Introduction

5 Scope Definition Digital Mapping – Digital Atlas Creation Some things to consider in scoping –Platform for access (MetaMAP) –Format of data (MetaMAP) –Study Area (Entire collection system) –Data Development Approach (Heads-up) –Source Material (Engineering drawings) –Level of Detail

6 Scope Definition Three options for level of detail –Level 1. Atlas Attributes –Level 2. Core Attributes –Level 3. Extended Attributes Selected a combination of 1 and 3 –Level 3 for 6 specific SECAP Study Areas –Level 1 for everything else Would have liked level 3 for everything, but budget would not allow – CMOM is a big initiative and many $$ already obligated

7 Scope Definition Examples of Detail Levels for Mains Level 1Level 2Level 3 “Atlas Attributes”“Core Attributes”“Extended Attributes” Identifier[Level 1, plus][Level 2, plus] Map referenceMaterialInvert Elevations ShapeYear BuiltDatum DiameterGiven SlopePlan Length

8 Scope Definition PROS –Graphical quality is equivalent between all three options –Less time and less money –As-builts already scanned, so research of detail information is simplified CONS –Sometimes working with profiles can show additional nodes such as change in material or change in slope –Lose some information useful in advanced applications –Deal with mix and match data Everyone is informed and OK – Move Forward

9 Scope Definition Tasks Organization Task 1 – Project Setup Task 2 – Data Import Task 3 – Sewer Atlas Update and Numbering Task 4 – Digital Sewer Atlas Creation Task 5 – Delivery Task 6 – Configuration Management Task 7 – SECAP Model Data Support Task 8 – Project Management and Administration

10 Project Management Plan Guiding principle –Accept the present situation and plan for the future Accept Present = Focus on deliverables –Atlas Maps –MetaMap –Model

11 Project Management Plan Project Team –Columbus Division of Sewerage and Drainage (DOSD) –Brown and Caldwell, LLC –Prime Engineering & Architecture, Inc. Plan for the Future Coordinating meeting ESRI Columbus Office –Geodatabase – Reporting Tool –Existing Data

12 Project Management Plan Task 1 – Project Setup 1.1 Document Project Specifications SECAP Model MetaMAP graphics/attributes Atlas Layout 1.4 Develop Work Plan

13 Schedule and Prioritization Work Plan Development –Only 18 months of data development –543 Atlases to complete Some had work done previously – “Reformats” Others had nothing – “New” –Target Model = Detailed attributes Others = Simple attributes

14 Schedule and Prioritization 17 Submittals were arranged One submittal per month –Months 2 through 18 –March 2003 through August 2004 –Average of 32 Atlases per month –Actually higher (61 max) because we wanted to start slowly and confirm quality and procedure Submittal #1 – Total of 6 atlases

15 Schedule and Prioritization Submittal #1 – “Unofficial” Prototype What were we trying to learn/confirm? –Format suitable for modeling –Quality assurance procedure and levels –Production capacity for City and EMH&T –Deliverable format: Digital –Deliverable format: Hardcopy

16 Schedule and Prioritization First priority was the SECAP data –92 Atlases were required –32 “New” and 60 “Reformats” –Accomplished in first 6 submittals –“Reformats” were in 4 of those submittals Next three (3) submittals designed to finish off core area of city and remaining detailed reformats

17 Schedule and Prioritization

18

19 Project Management Plan

20 Highlights Tasks 1, 4, 5, 7 and 8 went very well –Cooperation from City –Latitude from Brown & Caldwell –Experience of EMH&T Challenges Task 2 – Data Import –Allowed plenty of time to request and receive, but apparently not enough

21 Project Management Plan Challenges (Continued) Task 3 – Sewer Atlas Update and Numbering –Designed to be turned over to City upon completion, but did not happen that way Task 6 – Configuration Management –Quarterly updates ended up being monthly due to volume/quantity To be determined Task 6 – Transfer/Training beginning now

22 Application Definition and Development Two relevant application categories –Production Support –End-user Applications Production Support –Atlas Tracking – SQL Server/Access front-end –Node Numbering – Web-based SQL Server –Task Management – Microsoft Outlook®

23 Application Definition and Development Atlas Tracking – SQL Server/Access front-end

24 Application Definition and Development Node Numbering – Web-based SQL Server

25 Application Definition and Development Task Management – Microsoft Outlook®

26 Application Definition and Development End-User Applications –MetaMAP® - just wanted more information –CMOM GIS Application CMOM GIS Application - SSO Reporting –“Live” now on Internet –(http://www.gis.columbus.gov /sso/)http://www.gis.columbus.gov /sso/ –(http://gis.emht.com)http://gis.emht.com –Developed by EMH&T using ORACLE®, ArcIMS®, ArcSDE®

27 Data Development Approach Source Material –Base Map (various GIS) [Task 1] –Orthophotos (image files) [Task 1] –Imported Data (ESRI) [Task 2] –Atlas Maps (scan) [Task 3] –Structure Number Atlas (scan) [Task 3] –As-built drawings (scan) Preparatory Tasks Task 1 - Project Setup Task 2 - Data Import Task 3 - Sewer Atlas Update and Numbering

28 Data Development Approach Task 1 - Project Setup 1.2 Prepare Source Material Base Map – Collect and import to MetaMAP® Orthophotography – 2000, 6 inch pixel TIFF = 60GB JPEG = 7GB As-Built drawings copied 1.3 Setup Customized Production Environment AutoCAD® in multi-user environment –Wide Area Network (WAN) connection

29 Data Development Approach Task 2 - Data Import –Information available from various projects Special engineering studies Previous mapping projects –City provided information –EMH&T assessed for import –If suitable, then data was imported –Data attribute (SOURCE) tagged

30 Data Development Approach Task 3 - Sewer Atlas Update and Numbering –Sewer Map Room had the up-to-date atlas without structure numbers –EMH&T had an atlas set with structure numbers –Maintenance Section had other information they wanted reflected Update and improve structure number atlases and provide to City

31 Data Development Approach Task 4 - Digital Sewer Atlas Creation Steps #1 Markup Review #2 Digitizing #3 Entry QA/QC #4 Atlas Preparation Final Checks

32 Data Development Approach Step #1: Markup EMH&T uses redline notes to record calculations and assumptions that are performed as part of the attribute extraction process These digital redline files are a valuable record of decisions made during data conversion that will be available for future reference in cases of discrepancy

33 Data Development Approach

34 Step #2: Digitizing Scanned image registered to base features Orthophotos used, when possible, to assist in determining the proper placement of visible sewer features Each feature is captured as a CAD graphic element with a linkage to an associated record in the database Unique database identifier and the construction drawing reference are tagged to each graphical feature to assist in overall production checking and final quality control

35 Data Development Approach

36 Step #3: Entry EMH&T enters attribute information for each utility feature into the production database Data entry forms will be used to standardize data entry Drop down lists are used to restrict entry to predefined values Attributes are taken from the construction drawings When information is not available from construction drawings, appropriate placeholder values will be used

37 Data Development Approach Step #4: Atlas Preparation Sewer main and node features are annotated to support operations in MetaMap® and the production of the standard 200-scale atlas product Pipes includes diameter, flow direction and construction drawing reference Node features includes a nine-digit identifier Prepare a consistent cartographic product across the DOSD service area

38 Quality Control – Standards and Process Everybody was checking this data –EMH&T checked at three different times –DOSD checked it –B&C checked it Two different types of checking –Production Testing –Acceptance Testing

39 Quality Control – Standards and Process Acceptance Testing –No contracted specification for error % rate –That was not a priority –City had 20 working days –Visual checks primarily –Completeness and correctness of the atlas product –EMH&T had 20 days to correct

40 Quality Control – Standards and Process Independent check by Brown & Caldwell –Concurrent checks of first six submittals SECAP Study area –25 Atlas Sheets (5% of overall) Visual comparison – complete –10% random sample Spatial positioning Attribute completeness Confidence building and procedure development

41 Quality Control – Standards and Process Production Testing –No contract specification for % error rate –EMH&T committed to fix every error found while continuing to move forward – no rejection –The detailed checking of the first six submittals was the compromise to build confidence in the deliverable BUT – EMH&T had the BEST incentive to find and fix every error as soon as we could possibly detect and repair them

42 Quality Control – Standards and Process Per item (Atlas) fee structure Cascading errors –The more you find and the later you find them, the more time is required to fix them – the more $$ you chew up –We certainly did not want them to get through to the client and have us fix them in numerous places and products City liked it –Invoices are simple –City only pays for what they receive and accept

43 Quality Control – Standards and Process What we did to avoid and remove errors StepQC Solution #1 – MarkupFull review - Manual #2 – DigitizingEntry constraints: Menus Automated Checks - Self #3 – Data EntryEntry constraints: Forms, fields Automated checks – vs. Graphics #4 – Atlas PrepAutomatically generated Check plots - Manual

44 Quality Control – Standards and Process

45 Results of QA/QC program –The product is exceptional – only 400 total errors in more than 300,000 features converted –Brown & Caldwell indicated that this is the best data they have seen. They said they expected many more errors given the detailed nature of the work –Client has confidence in the data

46 Deliverable Format Tasks 5 and 6 Scope calls for following: –Digital Product MetaMAP Digital Atlas (PDF) –Hardcopy Product –Routine Updates –Maintenance Tools –Maintenance Training –Support of System

47 Deliverable Format However… The “future” is here… Project team is weighing our options…

48 Results and Findings Don’t be afraid to start simple – you can always enhance it later –City has elected to prepare Level 3 attributes for all features Consider early priorities and work them in appropriately Communicate openly and frequently –Be up-front about problems and search for solutions –Resolution is more “painful” the longer you wait Develop a system of penalties and incentives to guide progress Get “expert” input and opinions whenever possible –Even if you are doing the work in-house, there are simple opportunities to get help

49 Results and Findings Outline expectations and obligations of all parties and stick to them Interim deliverables for checking only, not for interim release Focus on confirming quality at every step Independent quality checks are beneficial Always perform some level of prototype or pilot project –Even if it’s and “unofficial” one Document specifications and get them accepted/approved by all parties Consider limitations of scope decisions and make all parties aware of them

50 Comprehensive Mapping Project –Scope Definition –Project Management Plan –Schedule and Prioritization –Application Definition and Development –Data Development Approach –Quality Control Standards and Procedures –Deliverable Format Summary of Project Considerations

51 Summary of Tasks Tasks Organization Task 1 – Project Setup Task 2 – Data Import Task 3 – Sewer Atlas Update and Numbering Task 4 – Digital Sewer Atlas Creation Task 5 – Delivery Task 6 – Configuration Management Task 7 – SECAP Model Data Support Task 8 – Project Management and Administration

52 Questions Derek Mair EMH&T, Inc


Download ppt "2005 Indiana GIS Conference March 9-10 - Indianapolis, Indiana City of Columbus, Ohio CMOM and Sewer System Digital Mapping Presented by: Derek Mair, GIS."

Similar presentations


Ads by Google