1

From Pipeline Data to Inspection Planning 

Jean Alain MOREAU, Marie PAJOT, Florian FABRE, Yves GIRAUD Integrity Management

2

TIGF at a glance

In 2005, the Gas & Power business line of TOTAL creates TIGF

TIGF operates :

5 000 km of natural gas transmission pipelines (13% national network),

6 recompression units (100 MW)

5.4 Gm3 underground storage facilities (22% national capacity).

TIGF does not own any gas, but transports and stores it for others gas market actors.

3

The “AMF” decree dated August 4th, 2006 :

Own a Geographical Information System (GIS) for 2009 with a Technical Data Base for 2011

VIGIE – Visualisation et Information Géographique des Installations Enterrées (Geographical Visualization and Information of Underground Installations)

Plan inspections, surveys and mitigations

OGIC - Outil de Gestion de l’Intégrité des Canalisations

PIMS - Pipeline Integrity Management System

For TIGF, these are 2 federating projects which shall :

Allow to share data and informations with all users,

Help with decision making

4

The Technical Database

2 different Tools, 1 single Database to meet regulatory compliance

Technical Data BaseRecording & georeferencing data

POD

S

Work Order

Maximo

On the field

VIGIE VIGIE

Geographic Information SystemAnalyse and Display PODS data

Threat AnalyseMitigation and Inspection Planning

OGICOGIC

Dalle

Inspection, CP

Geographic features, Structure

Environment

DiameterPressure

Thickness Join, Coating

Construction

6

PODS, the heart of VIGIE and OGIC :

Built on V 4.0.2Experience of many pipeline network operators, mainly oil and gas Independent of the GIS publishersExhaustive description of pipeline networks3D imaging of events that form or describe the pipeline

Complex workTo collect and indentify all available dataMainly manual tasksIn few numbers, it’s about :

70 types of various documents used10 000 documents collected from the Archives 40 000 A4 format scanned3 years, 65 000 hours (until 20 persons)

Cost : 2 MEUR for the actual DatabaseWithout the pipeline environment (1 MEUR) Without the survey, inspection, repairs and CP data (for 2011)

7

Geometry

8

Data reprocessing

9

Step 2

Step 3: 3D Drawing

Step1

Data analysis

Detailed Pipe-segment Files (FIT)

Old data reprocessing methodology

Step 4 : Feeding

Drawing : .dgb and 3DAdd complementary data (concrete

slab, casing, crossing…)

O2GB2D

Query/ report edition

Data check

BDT OracleOn PODS model

Preparation of a technical electronic document management

Preparation of a technical electronic document management

CMMS

Technical data

Scanning and

Compilation

Document Management

Data Base

Environment DB

10

Step1 CMMS

Technical data

Scanning and

Compilation

Document Management

Data Base

Step 2 Data analysis

Detailed Pipe-segment Files (FIT)

Step 3: 3D Drawing

Drawing : .dgb et 3DAdd complementary data (concrete

slab, casing crossing…)

Step 4 : Feeding

O2GB2D BDT OracleOn PODS model

Step by step data reprocessing

11

Step 1 : Scanning and Compilation

1992 : Construction

2006 : Modification

2006: Pressure test

12

Step 2 : Data analysis

FIT

1992 : Construction

2006 : Modification

2006: Pressure Test

13

Step 3 : 3D Drawing

3D

2D

FIT

14

Step 4 : Database feeding (PODS)

What Kind of data in PODS :

Network :

LINES : Pipelines

SITES : Compression station, Valve and Delivery station, Security valve, CP

Data :

Pipe length, weld join, tee, elbow, closure...

Nominal diameter, Wall thickness, Steal grade, coating, MAOP

Dot Class

Crossing (river, road, railroad,...)

Protection (casing, Concrete slab, river weight),

Marker

Building and housing (HI, IGH, ERP, ICPE)

In the future :

Nominal Depth of cover, temperature

Defects, Repairs, Regulatory compliance effects

16

TIGF PODS Interpretation : PODS 4.0.2

Nomenclature globale

AAAAAAXXX111111111-2222S3333P4444

Identification de l’évènement

Identification complémentaire

(du sous-type s’il existe)

Identification des points crées (*)

AAAAAA

XXX 111111111 -2222 S3333 P4444

code ouvrage

code correspondan

t au type d’événement

incrément global pour

les évènements

ordre dans lequel

l’élément apparaît dans

l’ouvrage

sous-type (Pipe_Length est un sous type de Pipe_Segment)

incrément pour chaque coordonnée

créée

OUVRAGE VALIDE EXPORT SUPPRESSION AJOUT MAJ DATE_DATA LONGUEUR NBPIECEFORME NBTUBE NBSOUDURE

07A01C -1 -1 0 0 -1 21-juin-10 4390,41 16 417 432

07A02C -1 0 0 0 0 22-oct-09 8728,57 5 785 790

07A03C -1 0 0 0 0 28-juil-09 22604 17 1999 2016

TIGF used the field “X_Guid” in order to know quickly the link between event and line

TIGF collect data by LINE (ouvrage lineaire) (pipeline between 2 valves station) and doesn’t used the SERIES table

=> 1 ROUTE = 1 SERIEWhen a modification appears on a pipeline, TIGF delete the former pipeline and regenerate the new one (due to the quantity of link between data)A table allows to manage the pipeline creation, delete and re generation.

171717

TIGF PODS Interpretation : PODS 4.0.2

FEATURE_ID TYPE_CL CATEGORY_CL DESCRIPTION TABLE_NAME HISTORY_TABLE_NAMECLOSURE MULTIPOINT PIPELINE01 Fermeture, Embout Closure STRUCTUREELBOW MULTIPOINT PIPELINE01 Coude Elbow STRUCTUREFLANGE MULTIPOINT PIPELINE01 Bride Flange STRUCTURELAUNCHER_RECEIVER MULTIPOINT PIPELINE01 Gare de racleur Launcher_Receiver STRUCTUREPIPE_JOIN POINT PIPELINE02 Soudure Pipe_Join STRUCTUREPIPE_LENGTH LINESTRING PIPELINE02 Longueur de tube Pipe_Length STRUCTUREREDUCER MULTIPOINT PIPELINE01 Réduction Reducer STRUCTURETEE MULTIPOINT PIPELINE01 Te Tee STRUCTUREVALVE MULTIPOINT PIPELINE01 Vanne Valve STRUCTURE

TIGF created a layer named STRUCTURE : Association of all the events in FEATURE_TABLE wich create the complete pipeline

Field FEATURE_TABLE.HYSTORY_TABLE_NAME = ‘STRUCTURE

The accuracy of the drawing of a pipeline in the database could be check trough different ways:

LINE

ROUTE

SERIES

PIPE_SEGMENT

STRUCTURE LAYER : PIPE LENGTH, PIPE JOIN, ELBOW, TEE, ….

1818

18

Modification of PODS 4.0.2 :Try to be faithful to PODS spirit

Table Description Structure New_Structure MotifCASING NOMINAL_WALL_THICKNESS_GCL NUMBER(6,4) NUMBER(6,2) Diminution du nombre de décimalesCOORDINATE X_COORD FLOAT(15) FLOAT(32) Augmentation de la taille du champCOORDINATE Y_COORD FLOAT(15) FLOAT(32) Augmentation de la taille du champCOORDINATE Z_COORD FLOAT(15) FLOAT(32) Augmentation de la taille du champEVENT_RANGE FEATURE_ID VARCHAR2(16) VARCHAR2(38) Augmentation de la taille du champFEATURE_TABLE FEATURE_ID VARCHAR2(16) VARCHAR2(38) Augmentation de la taille du champLINE LINE_GUID CHAR(38) VARCHAR2(38) Changement du type de champLINE_HIERARCHY PARENT_LINE_GUID CHAR(38) VARCHAR2(38) Changement du type de champLINE_HIERARCHY LINE_HIERARCHY_GUID CHAR(38) VARCHAR2(38) Changement du type de champPIPE_BEND VERT_ANGLE NUMBER(5,3) NUMBER(6,3) Augmentation de la taille du champPIPE_BEND HORIZ_ANGLE NUMBER(5,3) NUMBER(6,3) Augmentation de la taille du champROUTE LINE_GUID CHAR(38) VARCHAR2(38) Changement du type de champSTATION_POINT LINE_GUID CHAR(38) VARCHAR2(38) Changement du type de champ

Modification of existing field

Add New fieldsTable Description Structure

ALIGNMENT_SHEET PLAN_NUMBER VARCHAR2(10)ALIGNMENT_SHEET CODE_PLAN VARCHAR2(12)CASING TYPE_CL VARCHAR2(16)LINE PROPRIETAIRE_CL VARCHAR2(10)LINE OPERATING_STATUS_GCL VARCHAR2(16)LINE CONCESSION_CL VARCHAR2(2)LINE CODE_OUVRAGE_JURIDIQUE VARCHAR2(10)PIPE_SEGMENT NUMBER_OF_AFFAIR VARCHAR2(15)PIPE_SEGMENT MINIMAL_WALL_THICKNESS_GCL NUMBER(6,4)PIPE_SEGMENT EXTERNAL_DIAMETER_GCL NUMBER(8,4)REDUCER CHAMFER_WALL_THICKNESS_IN_GCL NUMBER(6,4)REDUCER CHAMFER_WALL_THICK_OUT_GCL NUMBER(6,4)STRUCTURE VISITOR_COUNT NUMBER(6)STRUCTURE EMPLOYER_COUNT NUMBER(6)VENT_PIPE TYPE_CL VARCHAR2(16)

Vérification des données

Génération des Géométries

Gestion de projet

Etape 2 : Vérification et génération des géométries

Etape 3 : Paramétrage du SIG

Gestion des droits Gestion de paramètres

pour le SIG Gestion des fonctionnalités

spécifiques

Etape 1 : Saisie et interprétation de la donnée

1919

19

PODS data organization:

Récolte des données Saisie et ordonnancement de la

documentation + Numérisation Saisie des carnets de soudures Interprétation des données Intégration des données recoltées

dans un espace géoréférencé Alimentation des caractéristiques des

Event-range

Localisation : Sous-traitantAction : Actavision

Importation par dumpVers un schéma Oracle PODSI

PODSI

Génération des géométriesVia l’outil SIG (GEOMEDIA)

VIGIE

Localisation : TIGFAction : TIGF

Localisation : TIGFAction :ATOS/INTERGRAPH

GEOMETRY

CARTO

Schema based on ORACLE10g

20

Data sharing with GIS

21

Tre

atm

ent

Vie

wer

County

Structure

Pipelines

Aerial Photography

Software

Land register

Database Users

Etc.

Topographic map

An architecture, from database to end users

Data available for all

22

The GIS software

INTERGRAPH software

Geomedia Pro + Transportation for administrators (7)

Geomedia WebMap Pro for users (300)

Business functions :

Data Migration to create Geometry

Dynamic Segmentation, 3D modelling

Emergency management, network optimisation

User functions :

Geographic map position,

Looking for a pipeline

Place a pipeline in its environment

Cost :1,3 MEUR

23

Inspection Planning with PIMS 

PIMS is named OGIC

Based on

A Threat Model (Threat Tree) and a methodology – TAME (BV + ATP)

A Structured database - PODS

Supported by Continuous improvement cycles common to other management systems

Seeking to

Protect the assets

Identify and prioritize pipelines by threat level

Capitalize knowledge

Plan integrity actions (inspection / surveys / mitigations)

Optimize both capital and operating expenditures

A decision support tool to plan inspection and surveys

25

Integrity

involves Threats to pipelines

Safety

involves loss of integrity consequences to Human and to Natural Environment

Risk(Decrease)

Mitigation Measures Surveys and Inspection

Integrity Model : Threat definition

26

INTEGRITY

Identify th

reats

Identify Mitig

ations

Evaluate probability

Calculate loss consequences

Classify pipeline segments

Plan

Carry out mitigations

Integrity Cycle

Record

Calculate level of threat

Integrity Model : Concept

Out of 100 threats in the complete model

45 are already resident in PODS 18 require specific analysis by GIS 37 are borrowed from external database

Integrity Model : the Threat tree

28

Soil resistivity 10

50Ω.m

-0.85

V

0Pipe CP

Remaining cycles (PIG)

DCVG results DefectOK OKFeatureOK

Threat level

m

1.2

Depth of cover

0

Integrity Model : Threat

identification and

positioning

29

1. Mitigation proposals 2. The ‘‘what-if’’ functionTo assess the effect of the various proposed measures to lower the level of threat.

Mitigations and “What If” studies

30

Analyse of pipelines

and Integrity Tasks

ScheduleOGIC

Plan

Integrity Tasks

Operators

Do

Refine Integrity Model

TAME/OGIC

Act

VIGIE : GIS View

Alignement Sheet

Follow progress

Maximo/VIGIE

CheckPlan

Do

Check

Act

Level of threat

Inspection and survey rules

Plan

Inspection and survey plan (PIMS approach)

Validation of the model in a global process management

31

To conclude

32

To conclude

VIGIE (GIS) and OGIC (PIMS) projects :

structure and share the information,

make TIGF regulatory compliant,

highlight true threats incurred by the pipelines,

outlay an inspection program based on true threats,

optimize actions means and resources

Nevertheless,Survey (foot, car, plane ..) is, and remains the main guaranty of

the underground networks safety, for civil work carried out by third parties that will never be completely controlled.

33

Thank you for your kind attention