esri user’s conference 2003

Using GIS as a Helping Tool in Gas Pipeline DesignUsing GIS as a Helping Tool in Gas Pipeline Design

Sidney Pereira dos SantosBusiness Consultant

Petrobras Gas Business Unit

Gilberto Luis Sanches HernandesGIS Specialist


Alessandro de Souza DinizGIS Analyst

Imagem

Renato CabralGIS Analyst

Imagem

ESRI User’s Conference 2003


Ø ScenarioØ ChallengesØ GIS Solution AdoptedØ InterfaceØ Data ManagementØ Data Sharing - WEBØ Final Considerations

ObjectiveTo Present GIS Implementation at Petrobras/GBU


ScenarioBR Gas Market & Pipeline Network Expansion

0.0

5.0

10.0

15.0

20.0

25.0

30.0

35.0

40.0

199019911992 1993199419951996 199719981999 20002001

(MMm3/d)

2002

45.0

Internal Production

42.1

20.1

Sales

Gasbol Importation = 2.15 5.74

10.07 23.310.55

9.0 Reinjection9.2

4.1

Growth of ~ 10% per year


Existing SystemDN 12 a 22” 1400 km

(870 miles)

Gasbol –Southern SectionDN 16 a 24” 1100 km

(684 miles)

Gasbol – Northern SectionDN 32” 1813 km (1127 miles)

Gasup (TSB)DN 24” 615 km(382 miles)

CW, S and SE Gas Pipeline Network

30 ~ 34

30 ~ 34

9 ~ 12

14 ~ 20

1.2 ~ 1.7

Total Supply ~ 100 MMm3/d (2.8 MMCFD)


US$ 1.3 billion in ExpansionNew Gas Pipelines: 3000 km (1865 miles)

New Comp. Stations: over 10New city-gates: over 30

Investment in Expansion Projects

Existing PipelinesGas pipelines: 7962 km (4948 miles) Oil/Products: 6300 km (3915 miles)


Why implementing a GIS?

• Management of existing and new gas pipeline projects

• Cover a wide geographic area (~3000 km (1865 miles) new ppl.)

• Assure information integrity and security (ArcSDE + workflow)

• Capability to manage and share spatial info.


• Addressed the following points:

•Overall status of existing data •Data Workflow definition•Data Standardization (in-out)•Data Management & Publishing•Reliability of System Architecture•Scalability (stand alone to enterprise)

Implementation Guideline


APDMCatalog

Files

ArcSDE

DisconnectedEdit

Plug-InPlug-In Plug-InPlug-In

GPCGPC WEB ArcGIS ArcGIS

Browser

TCP/IP ArcIMS

ArcPad

GIS Architecture

Notification of any data editing from

GPC to be inserted into APDM

Gas Pipeline CatalogUser Interface

APDM


• UML approach (Unified Modeling Language)• Easy communication among team members • Implements the best of ISAT and PODS• Customizable – Allows user to incorporate their specific needs.• Spatially enabled

Why APDM?


GeobasePPL

Inspection

APDM

Operation

Encroachment

PPL Facilities

CathodicProtection

SCADA

Facilities Operation Encroachments Geobase InspectionCathodic

ProtectionSCADA

x x x x x x xx x x x x x xx x x x x x xx x x x x x xx x xx x x

DesignProject ManagementOperationMaintenanceGas BusinessFinancing & AccountingEnvironmental x x

Data Structure


• Raw APDM UML (diagram)

• XMI Export – XMI file

• Physical implementation (RDBMS)

• Adapting and expanding model

• Data converting and loading

APDM Implementation


•Linear Reference•Abs. X and Y position from DGPS or Row Orthophotos

x, yvalve

157+588157+574

L1 L2

pipe section replacement

Control Points Definition

x, yvalve

Key definition - design & field survey


Gasduc I Overview

Atlantic Ocean


Gas Pipeline Viewer


Sidney Pereira dos SantosBusiness Consultant


Gilberto Luis Sanches HernandesGIS Specialist


Alessandro de Souza DinizGIS Analyst

Imagem

Renato CabralGIS Analyst

Imagem

ESRI User’s Conference 2003

esri user’s conference 2003

Documents