A CLIENT ORIENTED STRATEGY FOR PIPELINE GIS DATA SHARING

Americo Gamarra Senior GIS Analyst Hunt Oil Company

Introduction • A successful GIS implementation requires developing a

strategy for Pipeline Data sharing.

• Previous experience implementing GIS for PERU LNG pipeline project proved that it is important to focus on internal and external clients’ requirements about GIS data.

• Strategy: Client oriented, try to make GIS products part of key departments’ workflows.

About PERU LNG

• PERU LNG 34” PIPELINE has total length of 407,315 meters – 18 Above ground facilities – 296 Crossings:

• 11 Major Rivers, 30 Major Ravines (Quebradas) • 4 Pipelines

• 4 Major Roads, 179 Minor Roads • 238 Minor Ravines (Quebradas) • 29 Wetlands, 33 Canals, etc.

407,315 meters

About PERU LNG

Construction Commisioning & Certification Operation

Jan 2008 – Dec 2009 2010 Jan – June June 2010 - Now

GIS Implementation

Organizationally the GIS team is part of IT department.

About PERU LNG GIS

5 5 5

GIS – Pipeline APDM Pipes – Welds – Wall Thickness – Class Location - Valves – Facilities – Crossings - Ditch Breakers – Appurtenances - Coating – Elbow – Elevation – Operating Pressure – MAOP - HCA – Hydrotest - Right of Way – Cathodic Protection – CP Anode Beds - Risk Analysis – Anomaly – Pig Readings – Inspections – Events – etc.

GIS DB

Pipeline

Environmental

Easement

Archaeology

Geotech

Permits H & S Plant

Welds Layer (PipeJoinMethod)

40+ Layers

Pipeline GIS links to about 125,000+ Field Records (construction field reports, NDTs, Hydrostatic Tests, Caliper Pig, AsBuilt Drawings, easement negotiation files, etc)

ArcReader / Intranet GIS

PIPELINE GIS DATA SHARING

• Success of a GIS implementation in a Pipeline organization will be measured by its capability to support the users’ requirements for geographic information.

APROACH: CLIENT ORIENTED

• The client oriented approach means that the geographic data delivery has to be customized by each client.

A CLIENT ORIENTED STRATEGY FOR PIPELINE GIS DATA SHARING

• This approach requires the GIS department to “know” very well to the audience and their expectations. – “Who is my prospective client? – “What is the role of the client in the current pipeline project stage?” – “What information is required by the client?” – “When is the information/product required?” – “Why is the client asking for this data/product?” – “Which is the recurrence for this requirement?” – “How is the client going to consume the data/product?” – “What is the audience of the data/product?”

• Based on these questions classify requirements and assign priorities (relevance) prior any implementation.

• Methodology

A CLIENT ORIENTED STRATEGY FOR PIPELINE GIS DATA SHARING

Case Study 1: Requirement

• Client: PERU LNG General Management • Stage: Construction • Requirement: Daily Progress Map Report • Audience: Initially Management only (*) (*) After deploying audience was internal and external, map report was used to keep track of progress, control, planning, etc.

Case Study 1: Solution

Case Study 2: Requirement

• Client: Engineering Department • Stage: Commissioning • Requirement: Daily Report Commissioning • Audience:

Internal (Engineering and Operations departments) External (Government, Regulator, International Auditors)

Case Study 2: Solution

Case Study 3: Requirement

• Client: Engineering Department • Stage: Construction / Commissioning • Requirement: As-Builts Delivery • Audience:

Internal (Engineering and Operations departments) External (Government, Regulator, International Auditors)

Case Study 3: Solution

Case Study 3: Solution Auditors accessed AsBuilt data and related records through GIS viewers (Arc Reader and GIS Website)

Case Study 4: Requirement

• Client: Pipeline Operations Department • Stage: Operations • Requirement: Monthly Operations Report • Audience:

Internal (Engineering and Operations departments) External (Regulator)

Case Study 4: Solution

Case Study 5: Requirement

• Client: Pipeline Operations Department • Stage: Operations • Requirement: Support Pipeline Integrity Management by determining threats, HCA, etc. (yearly basis)

• Audience: Internal (Engineering and Operations departments) External (Regulator)

Case Study 5: Solution

Case Study 5: Solution “HCA Gas Analysis and Calculation” software tool based on ArcGIS Desktop, which follows industry standard rules to determine High Consequence Areas

Lessons Learned • It is important to have a strategy for GIS data sharing. As per

experience it’s recommended that data sharing should be client oriented.

• Data sharing requirements should be considered and managed as projects.

• Clients should be engaged from the beginning to ensure final product (map, data, application) meets user’s requirements.

• Users will always require and consume geographic data whether it comes from GIS department or not.