1. Jean Alain MOREAU, Marie PAJOT, Florian FABRE, Yves GIRAUD
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

5. 2 different Tools, 1 single Database to meet regulatory compliance
VIGIE
OGIC
Geographic Information System
Analyse and Display PODS data
Threat Analyse
Mitigation and Inspection Planning
Technical Data Base
Recording & georeferencing data
PODS
Work Order
Maximo
Dalle
Inspection, CP
Geographic features, Structure
Environment
Diameter
Pressure
Thickness
Join, Coating
Construction
On the field

6. PODS, the heart of VIGIE and OGIC :
Built on V 4.0.2
Experience of many pipeline network operators, mainly oil and gas
Independent of the GIS publishers
Exhaustive description of pipeline networks
3D imaging of events that form or describe the pipeline
Complex work
To collect and indentify all available data
Mainly manual tasks
In few numbers, it’s about :
70 types of various documents used
documents collected from the Archives
A4 format scanned
3 years, hours (until 20 persons)
Cost : 2 MEUR for the actual Database
Without the pipeline environment (1 MEUR)
Without the survey, inspection, repairs and CP data (for 2011)

7. Geometry

8. Data reprocessing

9. Document Management Data Base
Old data reprocessing methodology
Preparation of a technical electronic document management
Step1
CMMS
Scanning and Compilation
Document Management Data Base
Technical data
Query/ report edition
Step 2
Data analysis
Detailed Pipe-segment Files (FIT)
Data check
Step 3:
3D Drawing
Step 4 : Feeding
BDT Oracle
On PODS model
O2GB2D
Drawing : .dgb and 3D
Add complementary data (concrete slab, casing, crossing…)
Environment DB

10. Document Management Data Base Detailed Pipe-segment Files (FIT)
Step by step data reprocessing
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 3D
Add complementary data (concrete slab, casing crossing…)
Step 4 : Feeding
O2GB2D
BDT Oracle
On PODS model

11. Step 1 : Scanning and Compilation
1992 : Construction
2006 : Modification
2006: Pressure test

12. Step 2 : Data analysis 2006 : Modification 1992 : Construction FIT
2006: Pressure Test

13. Step 3 : 3D Drawing
FIT 3D 2D

14. Step 4 : Database feeding (PODS)

15. 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
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 SERIE
When 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.
Nomenclature globale
AAAAAAXXX S3333P4444
Identification de l’évènement
Identification complémentaire (du sous-type s’il existe)
Identification des points crées (*)
AAAAAA
XXX
-2222
S3333
P4444
code ouvrage
code correspondant 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
21-juin-10
4390,41 16
417
432
07A02C
22-oct-09
8728,57 5
785
790
07A03C
28-juil-09
22604 17
1999
2016 16 16 16

17. TIGF PODS Interpretation : PODS 4.0.2
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, ….
FEATURE_ID
TYPE_CL
CATEGORY_CL
DESCRIPTION
TABLE_NAME
HISTORY_TABLE_NAME
CLOSURE
MULTIPOINT
PIPELINE01
Fermeture, Embout
Closure
STRUCTURE
ELBOW
Coude
Elbow
FLANGE
Bride
Flange
LAUNCHER_RECEIVER
Gare de racleur
Launcher_Receiver
PIPE_JOIN
POINT
PIPELINE02
Soudure
Pipe_Join
PIPE_LENGTH
LINESTRING
Longueur de tube
Pipe_Length
REDUCER
Réduction
Reducer
TEE Te
Tee
VALVE
Vanne
Valve 17 17

18. Modification of PODS 4.0.2 : Try to be faithful to PODS spirit
Modification of existing field
Table
Description
Structure
New_Structure
Motif
CASING
NOMINAL_WALL_THICKNESS_GCL
NUMBER(6,4)
NUMBER(6,2)
Diminution du nombre de décimales
COORDINATE
X_COORD
FLOAT(15)
FLOAT(32)
Augmentation de la taille du champ
Y_COORD
Z_COORD
EVENT_RANGE
FEATURE_ID
VARCHAR2(16)
VARCHAR2(38)
FEATURE_TABLE
LINE
LINE_GUID
CHAR(38)
Changement du type de champ
LINE_HIERARCHY
PARENT_LINE_GUID
LINE_HIERARCHY_GUID
PIPE_BEND
VERT_ANGLE
NUMBER(5,3)
NUMBER(6,3)
HORIZ_ANGLE
ROUTE
STATION_POINT
Add New fields
Table
Description
Structure
ALIGNMENT_SHEET
PLAN_NUMBER
VARCHAR2(10)
CODE_PLAN
VARCHAR2(12)
CASING
TYPE_CL
VARCHAR2(16)
LINE
PROPRIETAIRE_CL
OPERATING_STATUS_GCL
CONCESSION_CL
VARCHAR2(2)
CODE_OUVRAGE_JURIDIQUE
PIPE_SEGMENT
NUMBER_OF_AFFAIR
VARCHAR2(15)
MINIMAL_WALL_THICKNESS_GCL
NUMBER(6,4)
EXTERNAL_DIAMETER_GCL
NUMBER(8,4)
REDUCER
CHAMFER_WALL_THICKNESS_IN_GCL
CHAMFER_WALL_THICK_OUT_GCL
STRUCTURE
VISITOR_COUNT
NUMBER(6)
EMPLOYER_COUNT
VENT_PIPE 18 18 18 18

19. PODS data organization:
Schema based on ORACLE10g
Etape 1 : Saisie et interprétation de la donnée
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
Importation par dump
Vers un schéma Oracle PODSI
PODSI
GEOMETRY
VIGIE
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
CARTO
Génération des géométries
Via l’outil SIG (GEOMEDIA)
Localisation : Sous-traitant
Action : Actavision
Localisation : TIGF
Action : TIGF
Localisation : TIGF
Action : ATOS/INTERGRAPH 19 19 19 19

20. Data sharing with GIS

21. An architecture, from database to end users
Data available for all
An architecture, from database to end users
Etc.
Aerial Photography
Structure
Viewer
Treatment
Pipelines
Land register
County
Topographic map
Database
Software
Users

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

24. A decision support tool to plan inspection and surveys
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

25. Integrity Model : Threat definition
Safety
involves loss of integrity consequences to Human and to Natural Environment
Integrity
involves Threats to pipelines
Risk
(Decrease)
Mitigation Measures
Surveys and Inspection

26. INTEGRITY Integrity Model : Concept Integrity Cycle Identify threats
Record
Evaluate probability
Carry out mitigations
INTEGRITY
Calculate loss consequences
Plan
Classify pipeline segments
Identify Mitigations
Calculate level of threat

27. Integrity Model : the Threat tree
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

28. Threat identification and positioning
Integrity Model :
Threat identification and positioning m
1.2
Depth of cover
Soil resistivity 10 50
Ω.m
-0.85 V
Pipe CP
DCVG results
Defect OK
Feature
Remaining cycles (PIG)
Threat level

29. 2. The ‘‘what-if’’ function
Mitigations and “What If” studies
Mitigation proposals
2. The ‘‘what-if’’ function
To assess the effect of the various proposed measures to lower the level of threat.

30. Inspection and survey plan (PIMS approach)
Validation of the model in a global process management
Integrity Tasks
Operators D Do
Level of threat
Inspection and survey rules Do
Follow progress
Maximo/VIGIE C
Check
Analyse of pipelines and Integrity Tasks Schedule
OGIC P
Plan
Plan
Check
Refine Integrity Model
TAME/OGIC A
Act
Act
Plan

31. To conclude

32. VIGIE (GIS) and OGIC (PIMS) projects :
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