From the Field to the Office Integrating As-Builts · From the Field to the Office Integrating...

19
From the Field to the Office Integrating As-Builts Presenter – Nathan Marx Chevron Pipe Line Company (CPL) Co-Presenter – Terry Strahan Morris P. Hebert, Inc. (MPH)

Transcript of From the Field to the Office Integrating As-Builts · From the Field to the Office Integrating...

From the Field to the Office

Integrating As-Builts

Presenter – Nathan Marx Chevron Pipe Line Company (CPL) Co-Presenter – Terry Strahan Morris P. Hebert, Inc. (MPH)

• Introduction • Current As-Built Integration Process • Problem With Current Process • Proposed Solution • Pilot Project & Results • Conclusions • Questions & Answers

Presentation Overview

Introduction

• CPL transforming how it manages/stores pipeline information/records

• From hardcopy as-builts stored in file cabinets

• From electronic as-builts stored in FileNet

• To tabular as-built records stored in PODS and used to generate alignment sheets

• Integrating as-built drawings into a tabular database has challenges

Current Process

• CPL PM initiates Management of Change (MOC) for pipeline new construction or reroute

• CPL PM contracts survey company, but does not always provide enough specifications/standards for data collection/As-Built Drawings – Each contractor uses their own format

• Not all data is collected in a format conducive to being loaded to PODS – CPL’s PODS Domain values not used – Variety of data entries possible, causing errors in data loading – Missing data / Too many “Unknowns” – Data for “Required” fields missing / Incorrect values

Current Process

• Field data entered into AutoCAD – Line work created to depict data collected – Text used to display attributes of features – Tally Sheets generated for materials used to

build pipeline – Paper Alignment Sheets generated

for delivery • Surveyor sends As-Built Drawings to CPL

as final deliverable • Pipeline is put into service, project is completed, and

MOC is closed out by Operations.

Problems With Current Process

• New pipeline has been in service months before GIS is contacted

– No advanced notice provided to GIS of New Construction

– “Issued for Construction” route not loaded into PODS

– GIS not involved in format of data collected for data integrity with PODS

• Paper Alignment Sheets and Tally sheets sent to GIS for “data mining”

– Manual entry for each individual piece of data into PODS

– Data entry slow and costly – High probably for error during data entry as

part of data conversion – Alignment Sheets missing important

information needed in GIS – Data not collected in correct format for entry

into PODS

Proposed Solution

• Developed New As-Built Drawing/Alignment Sheet Preparation and Management Process (DC&T 501) – Specifies roles, responsibilities,

and standards – Specifies MOC information flow

• Developed Pipeline Data Interchange System (PDIS) – consists of As-Built Drawing

template and MS Access Database template based on CPL PODS tables / Domain codes

Proposed Solution

• New Initiative put into place to involve GIS from the beginning – GIS brought into Design Phase of Route

Selection Process – Development of MS Access Database

with PODS tables and domain values pre-populated to be used to load Survey data back to for delivery to Chevron

– PODS data used to develop GPS Data Dictionary for use with Survey data collection process

– Loading of Preliminary Route into PODS as “placeholder” for As-Built

• Survey data accessed by both AutoCAD and GIS for concurrent development

Pilot Project

Current PODS

Cathodic Protection Flange

Foreign Line Crossing Marker

Meter Monument

Pipe Bend PIG Pipeline Vent Reducer

Road Right of Way

Railroad Riser Station Point Tap

Valve Water body

Weld Weight

Current tables in PODS to support Survey Data:

Pilot Project

No Tables currently in PODS to support Survey Data:

Topographic

Culvert Ditch

Driveway Fence

Levee/Canal Power Pole

Structure Tree Line Light Pole Guy Wire

Natural Ground Well

MPH Chevron As-Built GIS Workflow

Data Dictionary

Field Collections

Chevron Database

MPH Internal Use

CASING ELBOW FLANGE RAILROAD

FOREIGN LINE CROSSING LAND USE REDUCER

MARKER METER PIPE_BEND SLEEVE PiPE_JOIN

VALVE VESSEL WATERWAY ROAD RECTIFIER

TOPO

RT-Centerline

TALLY CODES GPS CONTROL

BORE

PIPELINE

Loose End String

TALLY LOOSE END BEND TELLY

TALLY OTHER TALLY WELD

PUP

CHECK SHOT

CONTROL POINT

MONUMENT

CULVERT DITCH DRIVEWAY

FENCE LEVEE POWERPOLE

STRUCTURE TREE LINE LIGHT POLE

TOPO OFF PIPELINE

TOPO ON PIPELINE

PODS New Construction Initiative

• Design • Survey • Construction • Operations

Pilot Project

• Survey Data loaded to PGDB provided by Chevron to match existing PODS tables and current domain values

• Updated Domain values not currently in PODS passed back to Chevron prior to data loading for review and addition to PODS tables as necessary

• PODS Data Loader used to enter data for centerline necessary for event loading of features.

No Tables currently in PODS to support Survey Data:

Pilot Project – SM03 Survey

Pilot Project – SM03 Survey

Conclusion

• CPL’s new DC&T 501 process and PDIS templates improve pipeline information management – Improves data quality – Reduces time required to

load to As-Built info to CPL’s PODS

– Supports CPL’s direction to have PODS be the pipeline system of record

• MPH Survey/GIS AS-Built – Change in philosophy

Question & Answer