Plant Engineering Life Cycle Conference 2005; 11 April

Dalip Sud

The Application of ISO 15926 Part 4

2

PELC 2005The HagueAGENDA

What is the business problem?

What is ISO-15926 – Part 4?

How is it used in a Company?

How can it be used across Industry?

3

PELC 2005The HagueThe territory

Plant Owner

EPC

EquipVendor

D A (specifications)

A D (information)

B (specifications)C

BC (information)

Emanufacturers

Number ofparticipants

1

1 to 6

~100 to 1000+

StartEnd

Project supply chain: information input-output model

In practice the flows are two-way

4

PELC 2005The HagueBarriers to supply chain integration

Increasing paper volume – physical and electronic

150k pages/US$100m Capex

Increasing need for information as data for applications

High cost of “as built” delivery of documents and data

0.1 to 0.5% of CAPEX for EPCs

Poor specification by supply chain participants

Not early enough, changeable, inconsistent

Concurrent engineering

Causes increasing approval cycles – more paper!

Equipment becoming software rich

More information delivered – in some equipment ~50% of cost is information

USPI-NL Industry workshop highlighted barriers:

5

PELC 2005The HagueWhat is Part 4?

Consistent and logical set of “Text Book References” Common definitions of activities, equipment and properties

Common classification structure, allowing informationsharing and integration within the Process industry supply chain.

The Register is structured according to simple “grammar” rules: “Is classified as”, “Is specialisation of”

“has property of”, “Has a role of”, etc

The content of Register is organized by: Disciplines e.g. rotating, piping, instrumentation and activities

Currently some 12,000 core definitions (class specialisations)

Unique and Internationally agreed!

6

PELC 2005The HagueHigh Level View of the reference data

library

CORE LIBRARY (ISO 15926 Part 4) Terms Definitions Classification and specialisation

PRODUCT MODEL LIBRARY Product models e.g. connecting equipment and

properties Templates e.g.Part 7, other examples presented at Ft

Lauderdale

COMPANY APPLICATIONS LIBRARY Handover, SAP, MESC, Piping, DEP’s

STEPlib

ISO 15926Part-4

SHELLlib

Data about DEP’s

MESCcatalogue

Piping classdata

DEP’s

Information Hand OverDocs & data

SAP Application

AB

C

7

PELC 2005The HagueISO15926-4 Coverage 5-11-2004

0

2000

4000

6000

8000

10000

12000

14000

16000

18000

20000

Physical objects Properties Documents Activities Other

Epistle RDL estimate15926-4 5-11-2004

Final estimate

8

PELC 2005The HagueISO 15926 Part 4 Estimated size

Subject AreaEstimated final nr of class specialisations

Subject Area contd.Estimated final nr of class specialisations

Data Model 1063 Roles / functional objects 600Activities / Occurrences 3000 Aspects 50 - Activities - composites 1500 - Construction materials - non steel 2000 - Activities - Control functions 600 - Construction materials - steel 2000Physical objects - Encoded Information, incl. text, numbers 500 - Chemical elements, elem. particles 126 - Fluids, signals & radiation 5000 - Civil & structural items 2000 - Information 500 - Connection material 300 - Mathematical objects 300 - Document types (carriers) 1000 - Properties 2000 - Electric machines 400 - Qualities & States 1000 - Electrical items 2000 - Units of measure / Dimension 800 - Geographical objects 500 - Association types 40 - Geographical objects - Individuals 800 Class of class 50 - Heat generation & transfer 600 Physical laws 100 - Instrumentation & control &IT 2000 Total 39549 - Lifeforms 500 - Piping 700 - Plants & Process units 500 - Protection material 200 - Rotating equipment 2000 - Solids handling 500 - Static equipment 1500 - Symbols (annotation) 800 - Systems 1000 - Transport material 500 - Valves 400 - Other Physical objects 120Total Physical objects 18326

9

PELC 2005The HagueExample of Part 4 – Heat_Transfer

Microsoft Excel Worksheet

10

PELC 2005The Hague

Shell Example on how Part 4 is used in Projects

ComputerizedMaintenanceManagementSAP PM, MM

DocumentManagement

System

IntsrumentationInTools

CorrosionManagement

System

HandoverDEP

SpecificationDatabase

ProjectHandoverdefinitiondatabase

(e.g. doc-types,classes..)

EPCsystems

ISO 15926Part 4 TS

Doc Matrix

SAP Blueprint(EP or GAME)

MAP EPCmodels to Shell

model

AddendumProjectspecific

Project specific

Project specific

Project specific

Project specific

Project specific

ESPIRSpare parts

Project specific

Smart PFS,PEFS, P&ID

Project specific

OTTER

Project specific

Legalrequirements

MAPHandover

model to sitespecific

structure

SAP is a product supplied by SAP AG

INTools is product supplied by Intergraph inc.

If EPC’s map to Part 4Mapping to Shell can reduce to minimal levels!

11

PELC 2005The HagueSo how does Industry move forward?

Each company aligns internally Cross industry teams agree minimum common handover standards

e.g. USPI-NL and FIATECH handover guide

Companies map internal standards to ISO 15926 Part 4 TS

some can be done now (e.g. equipment classes and a limited set of attributes,

plus document classes and meta data

Cross Industry teams come together to standardise Vendor data on the WEB Industry teams agree minimum Common Spare parts specifications

e.g. E-Spir

A series of small, practical steps …

Industry can now start exchanging data without having to map each time

12

PELC 2005The HagueUSPI-NL Data Readiness Framework

ONE TO ONE E-HANDOVER

INTERCOMMUNITY EXCHANGE EMERGING

MATURING INTERCOMMUNITY EXCHANGETime

EXTERNAL PROCESS INTEGRATION

INTERNAL PROCESS INTEGRATION

SUB PROCESS OPTIMIZATION

WORK PROCESS STANDARDIZATION

Today 2-3 Year 5 Year

SMALL CLOSED COMMUNITIESExternalData ReadinessPhases

InternalData ReadinessPhases

2-3 Y ears markInternal Company Standards International S tandards

ONE TO ONE E-HANDOVER

INTERCOMMUNITY EXCHANGE EMERGING

MATURING INTERCOMMUNITY EXCHANGETime

EXTERNAL PROCESS INTEGRATION

INTERNAL PROCESS INTEGRATION

SUB PROCESS OPTIMIZATION

WORK PROCESS STANDARDIZATION

Today 2-3 Year 5 Year

SMALL CLOSED COMMUNITIESSMALL CLOSED COMMUNITIESExternalData ReadinessPhases

InternalData ReadinessPhases

2-3 Y ears mark2-3 Y ears markInternal Company Standards International S tandardsInternal Company Standards International S tandards

13

PELC 2005The HagueBenefits and Desirability of Industry

Agreements

Dovetailed information - Reduce replication and reduce inconsistency

Better quality of decisions – based on maximum latest information

Faster decisions making in a project

Universal access – enable remote working and distributed teams

Enables cost efficiency – move work to lowest cost area

Without industry agreements, will continue to have islands and inconsistent local solutions

14

PELC 2005The HagueAdditional Slides

15

PELC 2005The Hague

STEPlib

ISO15926Part 4

SHELLlib

Data about DEP’s

MESCcatalogue

Piping classdata

DEP’s

Information Hand OverDocs & data

SAP ApplicationCMT

CAPS

SAPGAME

Projectsystems

DEPdocs

DEPstandard

forms

Companytailored

ConsortiaConsortiadevelopmentdevelopment

InternationalInternationalStandard (Part 4)Standard (Part 4)

How Part-4 relates to a company e.g. Shell?

16

PELC 2005The HagueHighlights from Industry Workshop

Volume of paper is growing, upwards of 150k pages per US$100m of Capex; increasing amounts electronically also;

Increasing requirements of information as data for loading into applications.

Cost of documents and data are 0.1 to 0.5% of CAPEX for EPC’s

Clients do not specify information requirements early enough, change them, and are inconsistent.

Concurrent engineering causes increasing approval cycles – more paper!

As equipment becomes software rich – more information is delivered

Common naming of documents, mata-data, and content would help. Specially vendor documents.

Make vendor documents available on the web.

Early definition of data requirements; differentiate between content and layout.

Reference: USPINL Information Handover Workshop April 2003Reference: USPINL Information Handover Workshop April 2003

17

PELC 2005The HagueDoes this work?

Technical data

Equipment classes, Attributes mapped externally to ISO 15926 part 4, internally to SAP-PM

Document classes and meta-data

Extended beyond Epistle handover guide and mapped to ISO 15926 Part 4

Document content Mapped to Shell DEPs (some 25% of document classes covered)

Spare parts According to E-SPIR

Instrumentation – using Shell standard template for INTools (Intergraph) Tools and utilities

Check compliance to guide by EPC’s and vendors

Shell’s common project information handover guide covers: