The Route to Pipeline Management

Nirvana?!

Michael Harris and Ted Tomes

Anadarko Petroleum Corporation

Estes Park, CO

8 June 2009

Today’s Route

• Some Philosophy & A Survey

• What or where is Nirvana?

• Our Vision of the Future 

• Initial Solution

• Revised Solution 

• Challenges

• Lessons Learned

• Recommendations 

Philosophy

• “Insanity – Doing the same things over and over again and expecting different results.” – Albert Einstein

• “Vision without action is a daydream; action without vision is a nightmare.” – Japanese Proverb

• “If fifty million people say a foolish thing, it is still a foolish thing.” – Anatole France

Audience Survey

• How many attendees:• work in transmission, gathering, distribution?• are currently using a corporate PL data model?

– Use PODS? APDM? Internal? Other?

• are implementing a model?• are considering or evaluating a model?• have shutdown or switched models?• have decided to go a different direction?

Today’s Route

• Some Philosophy & A Survey

• What or where is Nirvana?

• Our Vision of the Future 

• Initial Solution

• Revised Solution 

• Challenges

• Lessons Learned

• Recommendations 

Nirvana Defined

• “Emancipation from ignorance…”

• “A goal hoped for but apparently unattainable”

• Complete, online, easily retrieved information about horizontal infrastructure

• Seamless integration with all data sources

• Powerful and enlightening visual representations, accessible from any location.

• Holistic data lifecycle

Nirvana

Our Nirvana

Today’s Route

• Some Philosophy & A Survey

• What or where is Nirvana?

• Our Vision of the Future 

• Initial Solution

• Revised Solution 

• Challenges

• Lessons Learned

• Recommendations 

Am

ps &

vol

ts

Time

Specs

Our Vision of the FutureE

leva

tion,

ft

Distance, miles

• Hydraulic Modeling• Flow Performance• Debottlenecking• Pigging Planning

North

Launcher

Block Valve

River Crossing

Block Valve

Rectifier

20” Pipeline

Our Vision of the Future

PopulatedStructures

20” Pipeline

Name, Address, Phone NumbersBuilding Type, Floors, UnitsMobility Restrictions, Parking, Etc.

Our Vision of the Future

Block K

Leased Acreage

Block C

Block J

Well A-1Well B-1

Well B-2

Well C-2

Well D-2

Well K-1

Well J-1

Well I-1

Well H-1

20” Pipeline

Our Vision of the Future

Block K

Leased Acreage

Block C

Block J

20” PipelineWell A-1

Well B-1Well B-2

Well C-2

Well D-2

Well K-1

Well J-1

Well I-1

Well H-1

System Surveillance• Performance Metrics:

• revenues and expenses• capital requirements• maintenance activity• equipment availability• headcount utilization

• Financial and Operating Data by:• region or area• line, point, or event• contract and lease

Our Vision of the Future

Block K

Leased Acreage

Block C

Block J

20” Pipeline

Data Sources….for the Future

• Pipe, Features, and Attributes – PODS & SDE• TOPO & Satellite – Raster Depot & I‐Cubed• Land, Leases – Tobin Land Suite (TLS)• Land, ROW – Landworks (LPM)• Wells – Well Information System (WINS)• Hydraulics – Flow Desk (Gregg Engineering)• Buildings – Imagery & Ground Survey• Financial – SAP Financial / Control (FICO)• Maintenance – SAP Plant Maintenance (PM)• Documents – Documentum, FileNet, LiveLink

Success!....and…..

We freed our “Stuck” data!

Progress!....but…..

Consuming our data!

….but.…”Gulp!”

Be careful what you wish for!

Champ or Chump?Field Collection

Process

EnhancedWorkflows

Viewing &Access Tools

SystemIntegration

PODSDatabase

Our Goal“Nirvana”

A Prince or A Pig?

Today’s Route

• Some Philosophy & A Survey

• What or where is Nirvana?

• Our Vision of the Future 

• Initial Solution

• Revised Solution 

• Challenges

• Lessons Learned

• Recommendations 

Toomany

databasesAt field

locations.

Desktop Based Solution

Data hard to get at; tough to fully integrate

Highdemand

fortraining

andsupport.

Onedefinitivesource for

pipeline datawith

empowereduser

interface

Desktop Issues

• Desktop Issues– Complex solution; too many moving parts (DB’s, Imports/Exports)

– Reliance on ArcMap requires fairly sophisticated users/cost (licenses).

– Data captured in one area is not visible by other areas until fully validated and posted.

– Accessibility limited to a tethered (coporate network) solution

– Challenges leveraging contractors

Today’s Route

• Some Philosophy & A Survey• What or where is Nirvana?• Our Vision of the Future • Initial Solution• Revised Solution • Architecture and IT Challenges• PODS Challenges• Lessons Learned• Recommendations 

Server Based Solution

Server Issues

• Benefits• Easier tools & simpler workflow for Field Office staff• No databases hosted at field locations.• One central database and workflow.• Users can see data at all stages of the workflow.• Issues• Integration to internal systems still challenging

– Accounting, Land, GIS initiatives, SAP Facility Maintenance

• Manual intervention still required in “round‐trip”• APC cannot directly manage or update PODS.

Today’s Route

• Some Philosophy & A Survey

• What or where is Nirvana?

• Our Vision of the Future 

• Initial Solution

• Revised Solution 

• Challenges

• Lessons Learned

• Recommendations 

Architecture Challenges

• How do we centralize the solution?• Can data validation be improved?• How can we work disconnected?• Where can data be accessed?  By what tools?• How do we leverage our contractors?• Can we blend internal and external access?• How we avoid duplication of effort?• Can we leverage industry effort and goals?

IT Challenges

• Decades of data stored in every imaginable format.• Multiple simultaneous modes of data capture.• Timely “round trip” of data from capture to display.• Process automation to eliminate “touching” data.• Managing proliferation of partial solutions.• Cutting edge of technology. • Sophistication of available tools.• New hardware & software adoption.• Ongoing data quality maintenance.• New support obligations.

Challenges of PODS

• PODS has many admirable strengths, but:

• PODS NOT “ready to deploy”; requires buildout.– Not a mature gathering model.

– Ambiguous data definitions, often unclear.

– No standard domain values provided

• Avoid customization of PODS

• PODS not a native GIS solution; don’t expect it.

• Not a geometric network model.

PODS, with only one ”D” 

0 mi

0.8 mi

1.4 mi

1.7 mi

2.2 mi

3-D: Routing and Capture

Cartesian Coordinates; X, Y, Z

PODS Coordinates: Measure

Measure 1-D

PODS, in 3‐D!

Foreign Line Orientation?

Issues EmpoweringPolygons & PODS ?!• Meter Station• Booster Site• Gas Plant• Ground Bed• DOT Structure

Simultaneously UsePolygons & Points?• Either• Both• Related• Automate Creation(e.g., DOT Structure)

Today’s Route

• Some Philosophy & A Survey

• What or where is Nirvana?

• Our Vision of the Future 

• Initial Solution

• Revised Solution 

• Challenges

• Lessons Learned

• Recommendations 

Lessons Learned 1

• Avoid “grass roots” development; compartmentalized – Align SME’s before deployment

• Users demand good and immediate pipeline data.– “Run, don’t walk.” Be prepared.

• Develop a series of “quick wins” that show value. – Harder to “sell” value in an E&P company vs. Midstream

• “If you don’t build it, they might come anyway!”– Users WILL find a solution; right or wrong.   

– At least deploy standard tool sets.

– Don’t under estimate the depth and breadth of need.

Lessons Learned 2

• Manual intervention ongoing & a severe roadblock.

• Develop safety cases and specific examples

• Stewardship of mechanical integrity issues

• Use a mature, well documented and disciplined model – Perform a micro pilot test.

• Approach as a major full‐time integrated project– Resource appropriately.

– Aggressively manage stakeholder expectations.

– You can never over communicate.

Lessons Learned 3

• Strive to be hardware agnostic.

• Maintain a holistic view.

• Develop, document, & leverage domain lists.

• Participate to improve the model selected.

• User focus wasn’t “stop the bleeding”.

• Define internal integration strategy upfront.

• Users need 24/7 remote access.

• Centralized data coordination.

Today’s Route

• Some Philosophy & A Survey

• What or where is Nirvana?

• Our Vision of the Future 

• Initial Solution

• Revised Solution 

• Challenges

• Lessons Learned

• Recommendations 

Value Add Opportunities

• Safety Improvement

• Situational & Spatial Awareness

• Asset Inventory

• Personnel Routing

• Cathodic Protection

• Crossings (road, pipeline, railroad, water)

• One‐Call Management

• Spill and Risk Analysis

• DOT Class Evaluation

Wins!

• Single tool for field data collection.

• Single definitive pipeline database.

• Accurate mileage reporting.

• Better system classification.

• Improved feature attribution.

• Improved centerline accuracy & representation.

• Safer operations.

• Enhanced business decisions.

• Increased receptiveness to the POWER of PODS.

Recommendations 1

• Learn from others.

• Create a “Data Czar”.

• Understand data model.– What it is & isn’t

– Fully informed selection 

– Detailed pilot test

• Participate to improve the selected model.

• Stop the problem from growing.– Freeze the “old”, address the “new”.

Recommendations 2

• Enlist a corporate sponsor and champion.

• Communicate early and often.

• Focus on one “area” for detailed pilot test.

• Leverage and enforce a standard tool set.

• Remain flexible and adaptable.

Acknowledgement

If we have seen a little further it is by standing on shoulders of giants.”

Bernard Chartres (and Isaac Newton)

Questions?

• Clear as mud?  

• Ask Questions!

Backup Slides

• Supporting materials of various business benefits as needed.– Included slides have already been approved as part of a past external presentation.

• Slides will not be shown unless led by questions.

Network Analyst Example

CONDITIONS• 90 Locations• 1 employee• 5 minutes per location• Speed Limit

• 65 mph highways• 55 mph major roads• 45 mph minor roads

RESULTSDistance: 200 milesDuration: 13 hrs*** Not Practical ***

MODIFICATION OPTIONS1. Reduce time on site2. Add an employee / truck3. Prioritize locations (daily)

PRIORITIESRed: UrgentYellow: CautionGreen: “OK”

RESULTSDistance: 166 milesDuration: 10 hrs

“Manageable”

OBSERVATIONS• Visit 26% fewer locations• Time reduced by 23% • Mileage reduced by 17%• Not a “good” solution• Demonstrates impacts ($$)

• People• Time• Safety

• ArcGIS 9.3 “many-to-many” Analysis byParesh Patel

Handheld Collection