Pipeline Information Management

8/11/2019 Pipeline Information Management

http://slidepdf.com/reader/full/pipeline-information-management 1/32

OMV Group

Vienna, 2013-06-04

Achim Kamelger, CIO ITStrategy & Architecture

The Value of an

IntegratedPipeline InformationManagement Systemfor OMV Group

PODS EMEA,

4th June 2013

Vienna, Austria

!"#$% '(%)*+), !"#$%&%'($ *%+,'#$+#

-./ 01- -2+$3 14 5#%6#$78 9 *%+,'#$+#:%$



2 | OMV Group, CIO Strategy & Architecture, June 4, 2013

Agenda

OMV at a Glance !

Current Pipeline Management !

Vision: Integrated Pipeline Management !

RBI/PIM Initiative at OMV Petrom !

Design of an Integrated Solution !

Benefit & Summary !




OMV Business Segments




OMV at a Glance




OMV Key Figures




Agenda

OMV at a Glance !




Design of an integrated Solution !

Benefit & Summary !




Selection:

!

Trans Austria Gas (TAG) ! 3x380 km

! West Austria GAS (WAG) ! ~ 350 km

!

PVS (~Distribution Network) ! ~ 400 km

! Produktenleitung West (PLW) ! ~ 170 km

!

Adria Wien Pipeline (AWP) ! 435 km

!

Planned: Bratislava Schwechat Pipeline (BSP)!

~ 60 km

! Planned: Nabucco!

Major Pipelines in Austria




! Currently several different Pipeline

Management Systems are in

place:

! Example:

! Autocad based (AT)

!

Valis (AT proprietary system)!

Smallworld GIS

(DE proprietary system)

Managing:

Gas pipelines: ~1.700 km

Oil pipelines: ~750 km

Power cables: ~980 km

Water pipelines: ~300 km

Current Pipeline Management Approaches AS IS Situation




! Currently several different Pipeline

Management Systems are in

place:

! Example:

! Esri ArcGIS based in OMV

Petrom and Austria!

Petrom started (digital) data

gathering for

Fixed Assets: ~160.000

Oil/Gas pipelines:~ 24.000km

Current Pipeline Management Approaches AS IS Situation




Current Pipeline Management ApproachesExample: ArcGIS Austria




Analysis Analysis

Current Pipeline ManagementExample: GAS CONNECT AUSTRIA GmbH

Data Entry Analysis Reporting

(Manfred Breit)

06#,;<'+ =%;#$+>;"




Current Pipeline ManagementExample: GAS CONNECT AUSTRIA GmbH (Manfred Breit)

Analysis AnalysisData Entry Analysis Reporting

Classification of readings

Select the campaign

06#,;<'+ =%;#$+>;"




Current Pipeline ManagementExample: GAS CONNECT AUSTRIA GmbH

Dialog for creating CP diagrams for the areaand campaign of interest. Directly from the

PODS tables.

(Manfred Breit)


06#,;<'+ =%;#$+>;"




Current Pipeline ManagementExample: GAS CONNECT AUSTRIA GmbH (Manfred Breit)


06#,;<'+ =%;#$+>;"




!

Data gathering might be

different in each system

and performed differently

from contractors

!

!

with slightly differentinformation (+ formats)

! !different interfaces to

other systems (i.e. ERP)

! ! difficult to link withother systems

ERP (A)

ERP (B)

ERP (C)

CP 1

CP 2

CP 3

PIMSII.

Consequences of the differentPipeline Management Systems

PIMSIII.

Contractordata collection

MultiplePIMS

PIMSI.




Agenda

OMV at a Glance !





Benefit & Summary !




Integrated Pipeline Management SystemConceptual Architecture

GIS Client Desktop Web

Databasespatial enabled

ArcSDE

ArcGIS for Server

0101010101010101010101010101

010101010101010101010101010101010101010101010101010101010101010

Reporting

Integration

Spatial Integration

Data collection,QC and provision

Mobile




!

Location, Geographic Features

! Pipeline Facilities (ROW)

!

Intelligent In-line Inspections

! Physical Inspections

!

Maintenance

! Operation Measures

!

Cathodic Protection

!

Risk, Damage Offline Events

Vision of one Data Model forPipeline Management




!

Re-use of technical

solution and data model

!

One single source of data(MDM) leads to faster

availability of information

!

Reduced complexity

! Introduce efficient process

and operational workflows

! Assign roles and

responsibilities (ownership)

!

Contractors provide data inone (or two) formats

Benefits from one IntegratedPipeline Management System

PIMSI.

ERP (A)

ERP (B)

ERP (C)

CP 1

CP 2

CP 3

PIMSII.

PIMSIII.

Contractordata collection

MultiplePIMS

ERP (A)

CP 3

PIMS

DefineStandard for

data gathering

Establish onePIMS utilizing

best of practice




Agenda

OMV at a Glance !





Benefit & Summary !




! Introduce a risk-based management

system, for planning optimum cost

maintenance over the lifetime of an

asset (of pipeline system and static

equipment)

Petrom: Risk based InspectionPipeline Integrity Management

! Unreliable safety and operation

condition which conduct to unplanned

shutdowns and subsequently to loss of

production and maintenance high

costs.!

High frequency failures of pipeline

network due to the, corrosive producedfluids, poor quality of previous repairs

Current situation (As Is)

~160000 fix assets & 24.000km pipelineScope




POSITIVE•

Piloting data acquisition by

business initiative in selected

assets

Negative

•

Isolated data gathering withoutany system integration nor simple

connection to other repository

•

Missing functionality

Negative•

SAP PM contains mostly outdated

information (DQ)

• No data quality assurance process in

place

•

Very limited attributes – inadequate forany RBI calculation are available

•

No process and workflows are in place

•

Roles and responsibilities are not clearly

defined

No connection

Data Gathering Maintenance

!

Business Challenge: Looking for an integrated solution

Risk based InspectionPipeline Integrity Management

?




Agenda

OMV at a Glance !





Benefit & Summary !




Defining the High Level Workflows foran RBI/PIM System

Agreement on" Business Processes & Roles

" Information Flow (ILM) and Information Governance #

Business Architecture &IT Architecture

BusinessProcesses &

Workflow

InformationSystem

Informationflow &

Integration




Defining the High Level Concept Architecture foran RBI/PIM System

#

#

" Agreement on Information flow" Reuse if existing technology #


BusinessProcesses &

Workflow

InformationSystem

Informationflow &

Integration




Designing System Dependencies and Integration foran RBI/PIM System


BusinessProcesses &

Workflow

InformationSystem

Informationflow &

Integration




Designing Information Model/Flow and Interfaces foran RBI/PIM System


BusinessProcesses &

Workflow

InformationSystem

Informationflow &

Integration




Preparation for the RFI/RFP Process

BusinessRequirements

TechnologyRequirements


BusinessProcesses &

Workflow

InformationSystem

Informationflow &

Integration




Agenda

OMV at a Glance !





Benefit & Summary !




! Increased availability, sharing and re-usability of pipeline related data

within the enterprise

!

Increased data quality

! Efficient information workflows that are accessible for different asset

teams

!

Support of technical- and business workflows

! Supporting pipeline risk & -integrity tasks

!

Optimized decision support

!

Supporting maintenance and inspection workflows

! The data model is spatially-enabled and allows a seamless

integration in OMV´s existing systems such as WebGIS, SAP, eDMS,collaboration platform.

!

Reduction of paper archives

Benefits of implementing PODS based on anEnterprise GIS




!

Since April OMV is PODS Member and can benefit from their bestpractices, standards and state-of-the-art data model for pipeline data

management

! All members of OMV Group have access to OMV´s GIS standard based

on Esri Technology (Enterprise License Agreement (ELA))

! Re-use of infrastructure (2 Existing Systems – Vienna, Petrom)

ArcGIS Server based WebGIS/WebOffice Technology (SynerGIS)

!

Full Spatial Enabled PODS

! Capability for PIMS

! Ready for adapting emerging technologies, such as smart devices for

on/offline data gathering and data monitoring

!

OMV Group would clearly benefit from one single, integrated PipelineInformation Management System

! Meeting with OMV´s Pipeline Stakeholder will be scheduled

Summary




Thank you

([email protected])

Pipeline Information Management

Documents

Transcript of Pipeline Information Management