Transcript Document

The Application of ISO 15926 Part 4
Plant Engineering Life Cycle Conference 2005; 11 April
Dalip Sud
AGENDA

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?
PELC 2005
The Hague
2
PELC 2005
The Hague
The territory
Project supply chain: information input-output model
D
End
Plant
Owner
A
C
B
E
Start
A (specifications)
D (information)
EPC
Equip
Vendor
Number of
participants
1
1 to 6
B (specifications)
C (information)
~100 to 1000+
manufacturers
In practice the flows are two-way
3
Barriers to supply chain integration
PELC 2005
The Hague
USPI-NL Industry workshop highlighted barriers:

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
4
PELC 2005
The Hague
What is Part 4?



Consistent and logical set of “Text Book References”

Common definitions of activities, equipment and properties

Common classification structure, allowing information
sharing 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!
5
PELC 2005
The Hague
High Level View of the reference data library
SHELLlib
 CORE LIBRARY (ISO 15926 Part 4)
 Terms
 Definitions
 Classification and specialisation
 PRODUCT MODEL LIBRARY
STEPlib
MESC
catalogue
Piping class
data
ISO 15926
Part-4
B
A
SAP
Application
Data
about DEP’s
C
DEP’s
Information
Hand Over
Docs & data
 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
6
PELC 2005
The Hague
ISO15926-4 Coverage 5-11-2004
20000
Epistle RDL estimate
15926-4
5-11-2004
Final estimate
18000
16000
14000
12000
10000
8000
6000
4000
2000
0
Physical objects
Properties
Documents
Activities
Other
7
PELC 2005
The Hague
ISO 15926 Part 4 Estimated size
Subject Area
Data Model
Activities / Occurrences
- Activities - composites
- Activities - Control functions
Physical objects
- Chemical elements, elem. particles
- Civil & structural items
- Connection material
- Document types (carriers)
- Electric machines
- Electrical items
- Geographical objects
- Geographical objects - Individuals
- Heat generation & transfer
- Instrumentation & control &IT
- Lifeforms
- Piping
- Plants & Process units
- Protection material
- Rotating equipment
- Solids handling
- Static equipment
- Symbols (annotation)
- Systems
- Transport material
- Valves
- Other Physical objects
Total Physical objects
Estimated final nr of
class specialisations
1063
3000
1500
600
126
2000
300
1000
400
2000
500
800
600
2000
500
700
500
200
2000
500
1500
800
1000
500
400
120
18326
Subject Area contd.
Roles / functional objects
Aspects
- Construction materials - non steel
- Construction materials - steel
- Encoded Information, incl. text, numbers
- Fluids, signals & radiation
- Information
- Mathematical objects
- Properties
- Qualities & States
- Units of measure / Dimension
- Association types
Class of class
Physical laws
Total
Estimated final nr of
class specialisations
600
50
2000
2000
500
5000
500
300
2000
1000
800
40
50
100
39549
8
Example of Part 4 – Heat_Transfer
PELC 2005
The Hague
9
Shell Example on how Part 4 is used in Projects
Legal
requirements
Handover
DEP
Specification
Database
ISO 15926
Part 4 TS
Addendum
Project
specific
Doc Matrix
SAP Blueprint
(EP or GAME)
EPC
systems
MAP EPC
models to Shell
model
Project
Handover
definition
database
(e.g. doc-types,
classes..)
Project specific
If EPC’s map to Part 4
Mapping to Shell can reduce to minimal levels!
PELC 2005
The Hague
MAP
Handover
model to site
specific
structure
Computerized
Maintenance
Management
SAP PM, MM
Project specific
Document
Management
System
Project specific
Intsrumentation
InTools
Project specific
Corrosion
Management
System
Project specific
ESPIR
Spare parts
Project specific
Smart PFS,
PEFS, P&ID
Project specific
SAP is a product supplied by SAP AG
INTools is product supplied by Intergraph inc.
OTTER
10
Project specific
So how does Industry move forward?
PELC 2005
The Hague
A series of small, practical steps …

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
Industry can now start exchanging data without having to map each time

Cross Industry teams come together to standardise Vendor data on the WEB

Industry teams agree minimum Common Spare parts specifications
e.g. E-Spir
11
PELC 2005
The Hague
USPI-NL Data Readiness Framework
ONE TO ONE E-HANDOVER
External
Data
Readiness
Phases
SMALL CLOSED COMMUNITIES
INTERCOMMUNITY EXCHANGE EMERGING
MATURING INTERCOMMUNITY EXCHANGE
Today
2-3 Year
5 Year
Time
EXTERNAL PROCESS INTEGRATION
Internal
INTERNAL PROCESS INTEGRATION
Data
SUB PROCESS OPTIMIZATION
Readiness
Phases WORK PROCESS STANDARDIZATION
2-3 Years mark
Internal Company Standards
International Standards
12
Benefits and Desirability of Industry
Agreements
PELC 2005
The Hague

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
13
Additional Slides
PELC 2005
The Hague
14
PELC 2005
The Hague
How Part-4 relates to a company e.g. Shell?
Consortia
development
Company
tailored
SHELLlib
STEPlib
CMT
SAP
Application
MESC
catalogue
ISO15926
Part 4
Data
about DEP’s
Piping class
data
DEP
docs
CAPS
DEP’s
DEP
standard
forms
SAP
GAME
Information
Hand Over
Docs & data
Project
systems
International
Standard (Part 4)
15
Highlights from Industry Workshop
PELC 2005
The Hague

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.
16
Reference: USPINL Information Handover Workshop April 2003
Does this work?
PELC 2005
The Hague
Shell’s common project information handover guide covers:

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
17