© chevrontexaco 2005 standards & information management adrian goulding im/it manager of-lcim...

© ChevronTexaco 2005

Standards & Information Management

Adrian Goulding

IM/IT Manager

OF-LCIM (Europe)

“How a Standard approach to Information Mangement promotes Standards in

Information”


Fifth Largest integrated energy company in the world and second largest in the US1

Capital & exploratory budget in 2004 of $8.5 billion

1 Based on market capitalization


Southern Africa Strategic Business Unit

CABGOC (39.2%), Sonangol (41%), TotalFinaElf (10%)Agip (9.8%).


Sanha Condensate Project - Statistics

• Three bridge-connected platforms; a remote flare; a lone oil-producing platform; a newly built floating production, storage and offloading vessel (FPSO); a trio of large compressors; and more than 62 miles (100 km) of pipeline

• $1.9 billion Capital Spend

• 100,000 barrels a day of oil, condensate and liquefied petroleum gas (LPG) by 2007.

• LPG FPSO is both the largest and first purpose-built vessel of its kind

• 500 million cubic feet per day of dry gas re-injected into the reservoir

• Project duration - 5 years


Sanha Condensate Project - Scope


Sanha Condensate Project - Reach

13 countries on five continents


So on to Information Management . . .


Adopting a Standard – Some wins and losses

Corporate Business Unit guidance in the areas of

Document and Drawing Numbering/Classification

Drawing layout standards

Tagging and Engineering specification

Deficiencies in

× Adherence to guidelines

× Supporting Processes

× Technologies that support/impose standards

× Invited late to the Project


Adopting a Standard - Lessons

• By Contract Specification

Not always specific

Seen as a cost not a saving

• By Procedures

Not always aligned

• By Business Unit Specification

Dated

Not Comprehensive


Adopting a Standard - Technologies

• Shared Drives

• People’s PCs/CDs/Email

• Contractor solution

But a different Contractor for

– Each Phase

– Different Scopes

• Funding an issue

No funding in FEED

No Central Systems


Construction Starts

Issues

Remote Locations

Japan

South Korea

Spain

No IT plan in place No IM plan in place

Built Infrastructure using private and VPN circuits

Servers in Korea & Japan


Collaboration Space was essential

internet

internet

eRoom Server

Suppliers


Effects of a Collaboration Technology

• A tool to use

Web based sharing across the Intra & internet

• Improved work process

Rudimentary workflows

Basis for using Standards

• Better adherence to rules

Especially when additional tools were introduced

Transmittals

Change Order Tracking


Document Capture – What?

Classifications – and I will only focus on handover

• Studies

• Reports

• Drawings

• Data Sheets

• Calibration Settings

• Spare parts

• Design & Construction Manuals

• Operating & Maintenance Manuals


Target Systems for Handover

Drawings & Documents

Recently installed Documentum System

Existing FileNet system in Houston

Maintenance Mangement System

JDE World to be upgraded to Enterprise One

Plethora of local Systems


Documents – Reports & Studies

These are extremely important to understand the fundamentals of the facility

• Flow Assurance Basis for PFDs & P&IDs

• Safety Studies Included in Basis of Design for capacity and layouts

• Hazardous Operation Studies Safe Charts, Sim Ops plans and others

• Design Basis Bringing it all together

Early deliverables which were not included in the Document Numbering regime and so we now have large catch up.

We can now quantify the results of not having standards


Documents - Drawings

Best known deliverable, which in turn has been best managed

• Standard Layouts and Title Block

• Autocad the Standard

• Master Drawing Register

But . . .

• 2D deliverables becoming harder to deliver in a 3D world

• 3D model not brought to As Built and not used beyond Start Up


Documents – Data Sheets

Key deliverable from our EPC and a key document within the operations – about 3rd on the list of wants

• Higher percentage in Excel or Word format

• Captured as unstructured data

But . . .

• Common classification is missing

• Common layout is missing

• Common units are missing

Should ChevronTexaco drive a standard?


Documents – Calibration Settings for example

An example of a commissioning activity

Sanha did not have an Owner Operator Commissioning Tracking System – in the authors view a mistake.

It should have tracked by tag, line, cable, end device

Mechanical completion

Calibration

Commissioning activity

Startup

What we have now is a high amount of unstructured handwritten information in commissioning dossiers


Documents – O&M, D&C & Vendor Manuals

An extra 320 feet of shelving is going to be required to house one copy of the manuals at our shore base in Angola

• Steps towards structured information

Classification of content

Nomenclature in document numbering

Use of Document Management System, Web Delivery & CD Snapshots

• Barriers

Variety of content

Getting into other’s business processes

Format


Bringing Structure to Vendor Documentation

•Classification of content•Dividing into files by classification•Adding meaningful meta data •Restructure Hierarchy

350MB PDF file on a CD

Delivered

Restructure by :-


Documents – Spare Parts

Two elements Sparing Philosophy & Spare Part Catalogues

Again unstructured data but key to the three elements

Asset Register CMMS1

Document Management

Common codes can bring it together

Where we define the Asset

Where we know how to maintain it

Where we maintain knowledge

1 Computer Maintenance Management System


Commissioning Tracking what could have been

AssetRegister

Data Required

Data Captured

TrackingSystem

Commissioning Task


Data Capture - Use of Data Warehouse

Rapid deployment because technology already adopted - eWarehouse

Used as a vehicle for capture and handover• Equipment

• Instruments & end devices

• Lines

Populated our CMMS – JDE Edwards

Advantages• Classification

• Normalisation

• Structure

• “Best set of information in the Concession”


Data Warehouse – beyond Handover

• Wants to be included as a key information repository in Operations

• Hold a higher granularity of data

• Hold relationships

• Step towards Common Asset Codes


Tying the information together

Remember this?

Asset Register

CMMS Document Management

Common codes can bring it together

Where we define the Asset

Where we know how to maintain it

Where we maintain knowledge

Portal – Roles based

Data Warehouse


Thank you for your attention

Questions

© chevrontexaco 2005 standards & information management adrian goulding im/it manager of-lcim...

Documents

project slide

information slide

comprehensive slide

order tracking slide

market capitalization

information mangement

business unit specification

standard technologies