Pipeline Construction Data Management - Establishing Foundations ...
Pipeline Construction Data Management Establishing Foundations for an Asset Database
Scot Twining Product Manager [email protected]
2
- Make sure data collection serves a purpose
Consider your output goals
- Features can be manipulated during post-processing - Format attribute fields in data dictionary to mimic target DB
Attributes are what is important
- This is secondary to the need for a quick survey - Use ArcGIS models to process the data
Minimize data post-processing
- Quicker surveys save money and time - One time down the right-of-way
Make data collection easy for surveyors
Pipeline Construction Data Management
3
Preliminary centerline Civil Environmental Archaeological
As-built survey In-line Inspection surveys (ILI) Close Interval Surveys (CIS) Physical Inspections (PI) Etc.
-
GPS surveys of existing facilities Pre-construction surveys
Survey Data Collection
4
Plan the survey Create an intelligent survey data dictionary Write survey procedures Train survey crews Collect only what you need Survey data processing using standard procedures and ArcGIS models Load the data
Survey Data Collection To-Do List
5
Good spatial core No specific pipeline attributes Versioned geodatabase
Industry accepted attributes Relational NOT spatial PODS ESRI Geodatabase (in planning)
Survey data dictionary should consider both
- PODS: Pipeline Open Database Standard
- APDM: ArcGIS Pipeline Data Model
Industry-standard pipeline database models Take advantage of linear referencing Pipeline database models
Building a Survey Data Dictionary
6
- Station numbers
Format numeric fields like the target database
- Use for comments, serial numbers, names, and descriptions only
Format text fields with length Limit the number of text fields
- Use for Pipeline Identification - Use for Type codes
Collect PODS attributes Require field entry whenever possible Set defaults Use coded menu items
Building a Survey Data Dictionary
7
8
9
-
Pipelines – on-line feature to on-line feature or control points Foreign line crossings – 2 or 3 points establish the line Anything that goes along the right-of-way Collecting points avoids meandering
Collect lines as a series of points
- Eliminate inefficiencies - Make job easy for surveyors
Document all survey procedures Consult survey managers and crews when writing procedures Conduct training for survey crews Get buy-in from survey managers and crews Go to the field and verify procedures
Survey Procedures
10
11
Survey Data Processing – ArcGIS Models
12
Enterprise GIS database Construction GIS database Construction alignment sheets Environmental permit applications ROW acquisition
Output
13
Output - Enterprise GIS Database
14
Output – Construction Sheets
15
Focus on surveyor (make it easy) Encourage intelligent data capture Minimize data post-processing
Lessons Learned
Product Manager [email protected]
Scot Twining
Pipeline Construction Data Management
Q&A
Scot Twining Product Manager [email protected]
2
- Make sure data collection serves a purpose
Consider your output goals
- Features can be manipulated during post-processing - Format attribute fields in data dictionary to mimic target DB
Attributes are what is important
- This is secondary to the need for a quick survey - Use ArcGIS models to process the data
Minimize data post-processing
- Quicker surveys save money and time - One time down the right-of-way
Make data collection easy for surveyors
Pipeline Construction Data Management
3
Preliminary centerline Civil Environmental Archaeological
As-built survey In-line Inspection surveys (ILI) Close Interval Surveys (CIS) Physical Inspections (PI) Etc.
-
GPS surveys of existing facilities Pre-construction surveys
Survey Data Collection
4
Plan the survey Create an intelligent survey data dictionary Write survey procedures Train survey crews Collect only what you need Survey data processing using standard procedures and ArcGIS models Load the data
Survey Data Collection To-Do List
5
Good spatial core No specific pipeline attributes Versioned geodatabase
Industry accepted attributes Relational NOT spatial PODS ESRI Geodatabase (in planning)
Survey data dictionary should consider both
- PODS: Pipeline Open Database Standard
- APDM: ArcGIS Pipeline Data Model
Industry-standard pipeline database models Take advantage of linear referencing Pipeline database models
Building a Survey Data Dictionary
6
- Station numbers
Format numeric fields like the target database
- Use for comments, serial numbers, names, and descriptions only
Format text fields with length Limit the number of text fields
- Use for Pipeline Identification - Use for Type codes
Collect PODS attributes Require field entry whenever possible Set defaults Use coded menu items
Building a Survey Data Dictionary
7
8
9
-
Pipelines – on-line feature to on-line feature or control points Foreign line crossings – 2 or 3 points establish the line Anything that goes along the right-of-way Collecting points avoids meandering
Collect lines as a series of points
- Eliminate inefficiencies - Make job easy for surveyors
Document all survey procedures Consult survey managers and crews when writing procedures Conduct training for survey crews Get buy-in from survey managers and crews Go to the field and verify procedures
Survey Procedures
10
11
Survey Data Processing – ArcGIS Models
12
Enterprise GIS database Construction GIS database Construction alignment sheets Environmental permit applications ROW acquisition
Output
13
Output - Enterprise GIS Database
14
Output – Construction Sheets
15
Focus on surveyor (make it easy) Encourage intelligent data capture Minimize data post-processing
Lessons Learned
Product Manager [email protected]
Scot Twining
Pipeline Construction Data Management
Q&A
