All Pipes Production Mapping

29
1 All Pipes Production Mapping Steve Grisé Solution Architect, Vertex3 October, 2012

description

All Pipes Production Mapping. Steve Grisé Solution Architect, Vertex3 October, 2012. Topics. Production Mapping Project Overview Data Model Review and Discussion Process Review and Discussion. Production Mapping In York Region. Planning. Design. Construction. Operations. GIS. GIS. - PowerPoint PPT Presentation

Transcript of All Pipes Production Mapping

Page 1: All Pipes Production Mapping

1

All PipesProduction Mapping

Steve GriséSolution Architect, Vertex3October, 2012

Page 2: All Pipes Production Mapping

2

Topics

1. Production Mapping Project Overview2. Data Model Review and Discussion3. Process Review and Discussion

Page 3: All Pipes Production Mapping

3

Production Mapping In York Region

Planning Design Construction Operations

GIS GISGIS

GIS Processes

Job/Edit Session PostingEditing

StepsJob

QA/QC

Page 4: All Pipes Production Mapping

4

Regional Data Sharing

KingWhitchurc

h-Stouffville…

regionalAll Pipes

York Region

Hydraulic Modeling

Analysis and

Reporting

GIS Processes

Job/Edit Session

Editing Steps

Job QA/QC Posting QA/QC Extract

Other Region

s

Page 5: All Pipes Production Mapping

5

Production Mapping

Data ReviewerQA/QC

Define WorkflowsJobWorkflow steps and tools

Raise the bar for data quality and consistencyDistributed editing based on agreements

Page 6: All Pipes Production Mapping

6

DriversLocal Participation

Meet local business needsDaily OperationsSummary – Reporting and ComplianceAsset Planning and Management

Regional needs met as a by-product of meeting local needs

Incentives and agreements will have some impact on data model/processes over timeWhat are your drivers?

Page 7: All Pipes Production Mapping

7

Best Practices for W/WWGIS updated from Drawings/As-BuiltsRepresents the asset in the organizationOften integrated

Asset Management – ReportingAsset Management – Operations and EngineeringNetwork Analysis

Maturity1. Data Model2. Tools/Applications3. Integration4. Processes and Data Quality

Page 8: All Pipes Production Mapping

8

What is a Data Model?

A representation of the real world in a computer systemSupports business applications and business functions

Defines the set of information products/information we can accessDefines the work that needs to be done to manage the information

An agreement with choices and decisions

Page 9: All Pipes Production Mapping

9

Application-Driven DesignDefine the information products requiredBreak down into layers, reports, othersDesign datasets to support the layersBest Practices are iterative

2 3

4 51

FeatureClassName RoadSegmentDatasetType FeatureClassDescription Road Segments represent centerlines of roadways/carriageways.FeatureDataset ManagedDataDataTheme Transportation; Addresses and NamesShapeType PolylineFeatureType SimpleAliasName Road SegmentsHasM trueHasZ falseSubtypeFieldName nullDefaultSubtype null

FieldsFieldName Type Length Description AliasName DomainName DefaultValue IsNullable Precision Scale RequiredROADSEGID Integer 4 Road Segment ID Road Segment Identifiernull null true 0 0 nullROADCLASS Integer 4 Road_Class Road Classification RoadClass Domain null true 0 0 nullONEWAYDIR String 10 OneWay Direction - either with or against direction of vertices, or None for two-way trafficOneWay Direction ONEWAYDIR Domain null true 0 0 nullFROMLEFT String 12 Left From Address Number along Street Left From Address ADDRNUM Domain null true 0 0 nullTOLEFT String 12 Left To Address Number along Street Left To Address ADDRNUM Domain null true 0 0 nullFROMRIGHT String 12 Right From Address Number along Street Right From Address ADDRNUM Domain null true 0 0 nullTORIGHT String 12 Right To Address Number along Street Right To Address ADDRNUM Domain null true 0 0 nullSTPREDIR String 4 Prefix Direction for Street Name Name Pref ix Direction ROADDIR Domain null true 0 0 nullSTPRETYPE String 12 Prefix Type of street or road Name Pref ix Type ROADTYPE Domain null true 0 0 nullSTNAME String 60 Road or Street Name Street Name ROADNAME Domain null true 0 0 nullSTTYPE String 12 Type of street or road Street Type ROADTYPE Domain null true 0 0 nullSTDIR String 4 Street Name Direction Name Direction ROADPOSTDIR Domain null true 0 0 nullCITY String 60 Name of City street is located in City Name CITYNAME Domain null true 0 0 nullALTNAME1 String 120 Alternate Name 1 Alternate Name1 null null true 0 0 nullALTNAME2 String 120 Alternate Name 2 Alternate Name2 null null true 0 0 nullZIPLEFT String 10 Zipcode on left hand side of line Zip Left ZIP Domain null true 0 0 nullZIPRIGHT String 10 Zipcode on right hand side of l ine Zip Right ZIP Domain null true 0 0 nullJURISDICT String 12 Road Jurisdiction for maintenance and other responsibil ities Jurisdiction ROADJURISDICTION Domainnull true 0 0 nullCFCC_CODE String 4 Census Feature Classification Code for road Census CFCC null null true 0 0 nullLASTUPDATE Date 8 Date of Last Update in Maintenance Database Last Update Date null null true 0 0 nullLASTEDITOR String 50 User that last updated the data Last Editor LASTEDITOR Domain null true 0 0 null

Page 10: All Pipes Production Mapping

10

Purpose of the Data Model

Primary goal is to produce a regional GIS database

Region-wideCurrentSupports IntegrationManaged in partnership with Local Area Municipalities (LAMs)Enterprise Data Warehouse

What are your needs?

Page 11: All Pipes Production Mapping

11

Initial Data Model (examples)w_Valve Points that represent water network valves

Asset IdentifierSCADA IdentifierValve TypeDiameter (mm)SettingInstall DateRehab DateValve Elevation(m)York Pressure DistrictLocal Pressure DistrictManufacturerRemotely ControllableOwned ByManaged By

Unique Asset IdentifierUnique SCADA IdentifierType of ValveNominal Diameter for the valveSetting for the valve (type specific)Install Date for the AssetDate of Last RehabilitationValve Elevation (for pressurized systems)York Pressure District/ZoneLocal Sub Pressure District/ZoneName of the ManufacturerIndicates if the valve is remotely controllableOwner of the AssetManager of the Asset

w_Main Lines that represent active water mains in York Region

Asset IdentifierMaterialDiameter (mm)Install DateDepth of Cover(m)Start Pipe Elevation(m)End Pipe Elevation(m)RoughnessYork Pressure DistrictLocal Pressure DistrictRetirement DateDrawing ReferencesPipe Type (Trans/Dist)Owned ByManaged By

Unique Asset IdentifierMaterial type for the assetNominal Diameter for the mainInstall Date for the AssetDepth of Cover in metresElevation at first vertex of pipeElevation at last vertex of pipeRoughness coefficient - a model calculationYork Pressure District/ZoneLocal Sub Pressure District/ZoneProposed Date the Asset will be retired/abandonedList of drawings separated by commasIndicates if Transmission or Distribution MainOwner of the AssetManager of the Asset

Page 12: All Pipes Production Mapping

12

Content Review

Starting PointModeling Task Force at York RegionExisting GIS data/modelsExisting Network Analysis data/models

Page 13: All Pipes Production Mapping

13

Next StepsRefine based on information products/needsDriving forces

Asset Management at York RegionAsset Management for LAMsReporting requirements – MOE and othersOperationsMulti-jurisdictional issues like Inflow and Infiltration

All Pipes Model will be the core data structure that groups will extend for their purposes

… and possibly share at some point…

Page 14: All Pipes Production Mapping

14

Regional Data SharingABC

ABD

ABE

Export

Export

Export

A

B

QA/QC

QA/QC

QA/QC

Load

F

Page 15: All Pipes Production Mapping

15

Regional Data Sharing

A

B

F

Access By Partners

Page 16: All Pipes Production Mapping

16

Challenges

Closest-to-source QAOne-touch editingQuality, currencySustainmentSkill SetsResources

Page 17: All Pipes Production Mapping

17

Processes

Start New Data Received

Water Process

Wastewater Process

Posting Process End

Create Session

Yes

More Changes? No Batch QA/QC

Extract and Load to Regional Database

Multiple sessions

Page 18: All Pipes Production Mapping

18

Next Steps

Review with stakeholders in different areasCollaboration

Maximo-GIS integrationAll Pipes Implementation pilot(s)

Data Model RefinementProcess and rules definitionOthers based on your feedback

What do you want to see?

Page 19: All Pipes Production Mapping

19

OutcomesCentralize data, provide easy access to partner organizations, reduce requests/efforts/redundancy

Optimize Development activities in the Region so that new customers are located close to water/wastewater capacity

Locate assets quickly and identify ownership/maintenance responsibilities

Improve visibility into volume and billing data

Page 20: All Pipes Production Mapping

20

Measuring Success – One example

Page 21: All Pipes Production Mapping

21

Design ProcessWhat map layers can I see and interact with?Where does the Data come from?What Impact is there on All Pipes sharing and Production Mapping work?

Assets

Landbase

Operations

Analysis and Planning

Page 22: All Pipes Production Mapping

22

Possible Impacts

Need Customer Counts for Mains Annual Consumption/Available capacityLocal Official Plans Building PermitsLocal self-reporting on G/Y/R Identifying Properties with Development Potential/Priority ranking

Page 23: All Pipes Production Mapping

23

Your Outcomes

What do you want to see?What layers/data do you need?Is there an impact on

Data warehouseData sharingProcess for you and partners

What information can you provide?

Page 24: All Pipes Production Mapping

24

Page 25: All Pipes Production Mapping

25

Current Situation in York Region

Data StatusCompletenessCurrencyContent

Many good people have worked hard to get to this pointThe Region and partners are spending significant $ on dataLots of work to be done

Page 26: All Pipes Production Mapping

26

Current Situation - Water

Page 27: All Pipes Production Mapping

27

Current Situation - Wastewater

Page 28: All Pipes Production Mapping

28

Current Situation – Data Models

Page 29: All Pipes Production Mapping

29

Current Situation – Data Models