Why ISO 15926 - THTH ry · PDF file• 1999– First deployed for PDS to CADDS5 • 2003- First AVEVA VNET deployment ... • Schema defines Dictionary compliance of ISO 15926 –

1

Noumenon Consulting LimitedNoumenon Consulting Limited

ISO 15926 and ISO 15926 and interoperabilityinteroperability

Proteus andProteus andXMpLant technologyXMpLant technology

Adrian Laud Noumenon Consulting Ltd – May 2010


Why ISO 15926 ?

Years Months Days

To date to create the standard

2


ISO 15926 in use today

• 80 major commercial projects are using XMpLant successfully today

• Operations use of Engineering information

• Exchange of designs between systems

• Proving the model for commercial projects

• XMpLant technology is a Deployment tool


XMpLant usage

• Tens of thousands of P&IDs

• Tens of thousands of ISOs

• Tens of thousands of 3D models

Access to intelligent Engineering information in Operations

3


• 30 Areas• 46,000 Isometrics • 1,200 Equipment items • 270,000 steel sections

Shell – Pearl GTL$26 billion project11 main contractors

CCC - C3D – test pack identification

ApplicationsPDMS – 3D modelC3D - Construction

Management


Shell – Pearl GTL

CCC - C3D test pack summary for a line

4


Reference Data Library

Template Modeling and Methodology

Semantic Web / Ontology

Technology (SOA, security, ….)

Gain

Vendor implem

entations

Rule-based EngineeringKnowledge Mgt

High value, high cost resource, available today

Semantic Web XML file transport

Can be expressed implicitly in XML Schema

OWL / RDF XML enables validation online

Essential for non-proprietary data exchange

ISO 15926 Stack

Noumenon Consulting LimitedNoumenon Consulting LimitedR e a l i z i n g O p e n I n f o r m a t i o n I n t e r o p e r a b i l i t y

Proteus and iRING Projects

Business Axis

Com

plia

nce

Axis

iRING

cv

Proteus

iRINGTechnology

Business Requirements

Information Model

ISO 15926Information

Model

5


ISO 15926 implentation• Vendors committing to ISO 15926

• XMpLant Schema 3.3.3 defines DC XML model

• Products demonstrated – FIATECH Apr 2009– Matrix 123 – Dictionary compliance – full engineering scope

– iRING – information sharing – closely limited scope

• XMpLant technology used in interfaces

• Major FIATECH / PCA projects underway– Proteus – follow on from Matrix 123

– JORD – Establishing commercial Reference Data system

• iRING User Group – tools for information sharing


Proteus Business cases• Facilitate movement of P&IDs – simple scope

• P&ID – 3D comparison

• Extraction of attribute lists P&ID and 3D

• Graphical Navigation for P&ID

• P&ID to 3D exchange

• Intelligent P&ID exchange – full scope

• Engineering reports - BOM, Line Lists, Datasheets

6


Proteus ScopeIn scope: • Exchange of intelligent P&ID’s and 3D models.

– Tag numbers, equipment numbers, line numbers etc. – Connectivity– Schematic information (symbology, diagrams)– 3D Geometry (equipment models and pipe routes)

Not in scope:– Design data and process data Data propagation rules – Meta data, e.g. status, ownership, revision, engineer etc.– Design change management


Proteus Project: Results

3D to 3D:Matrix 2

P&ID to P&ID:Matrix 1

P&ID to 3D: Matrix 3

Achieved Achieved

Achieved

• On specification• On time

• On (the vendors’ own) budget

7


P&ID (SVG) from XML


Vendors and ISO 15926• AceCAD• Aspentech• Autodesk• AVEVA• Bentley• Cadmatics• CCC• COADE• Comos

• Dassault Systemes• IBM• Intergraph• INOVx• Invensys• Noumenon• Octaga• VRContext

Companies in maroon demonstrated product at FIATECH conference Apr 2009

8


ISO 15926 P&ID interfaces• AutoPLANT• AVEVA P&ID• Aspen basic (ZyQAD)• Cadworx P&ID• CATIA P&ID• Comos P&ID• SmartPlant P&ID• PDS P&ID• VPE P&ID

Most are export to XML only – green are 2 way


ISO 15926 3D interfaces• AutoPLANT• C3D – import• Cadmatics• Cadworx 3D• CADLinx• PDMS • PDS 3D• PlantView• SmartPlant 3D – import

Most are export to XML only – green are 2 way

9


ISO 15926 visual Navigation• AVEVA NET• Bentley Navigator• C3D• CADLinx• Octaga Enterprise• VR Context


XMpLant technology• Tool for interoperability

• Powerful Rule based mapping subsystem

• XMpDE – core development environment –data driven (Schema and mapping files)

• Enables new applications to be written working on the ISO 15926 model

10

Noumenon Consulting LimitedNoumenon Consulting LimitedOther standards

OperateDesign ConstructFEED

XMpLant

Proprietary systems

ISO 15926 Applications

XMpDE - ISO 15926 Flexible Data Model

Interoperability with XMpLantInteroperability with XMpLant


XMpLant OverviewXMpLant Overview

XMpLantmodel

XML

Schema ReportsBOM, Line lists etc

Map files

Nat

ive

Appl

icat

ions

E

D

Inte

rfac

eIn

terf

ace

Nat

ive

App

licat

ions

A

B

C

Inte

rfac

eIn

terf

ace

Inte

rfac

e ISO 15926-3ISO 15926-4M

appi

ng s

ubsy

stem

Map

ping

sub

syst

em

Map files

11


XMpLant and conformanceXMpLant and conformanceXML Schema

XMpLantmodel

Map files

Nat

ive

Appl

icat

ions A

B

C

Inte

rfac

eIn

terf

ace

Inte

rfac

e ISO 15926-3ISO 15926-4M

appi

ng s

ubsy

stem

RDS/WIP online

DictionaryCompliant

XML files

Map filesM

appi

ng s

ubsy

stem

iRING

Map


•Core requirement for ISO 15926 deployment•Rule based with powerful facilities•XMpLant mapping fulfils these requirements

MappingMapping

•Name and Value mapping•Substring processing, evaluations•Format conversion, splitting, concatenation•Nested Mapping, Associations•Pattern matching, Class changing

12


XMpLant Projects• 1999 – First deployed for PDS to CADDS5• 2003 - First AVEVA VNET deployment• 2004 – Catalogue and Specification conversion

• Today– 10 vendors using XMpLant technology or Schema

• Schema defines Dictionary compliance of ISO 15926

– 240 + subscribing to the Schema– 20 successful conversion projects and several pilots– 60+ installations in Operations and many pilots


•20 read interfaces - Import to XMpLant•12 write interfaces – Export from XMpLant

•New ones in development for native systems

•ISO 15926 Dictionary compliant XML files•ISO 15926 iRING adapter – in development

•Read interface for IFC’s (buildings)•Interfaces for other standards - planned

XMpLant interfacesXMpLant interfaces

13


XMpLant AnalysisXMpLant AnalysisSpreadsheet report from P&ID model (same for 3D)


XMpLant AnalysisXMpLant AnalysisPipeline report from P&ID model (same for 3D)

14


•XMpDE enables applications to be developed

that work on the model of ISO 15926

XMpLant Applications

•Dumb to intelligent drawings

•Dumb to intelligent Datasheets

•Neutral Cats and Specs

•Generic Comparator


•Operates on the neutral model•Any input DGN, DWG, SS

•Graphical pre-process to create structure

Dumb to IntelligentDumb to Intelligent

•Pattern matching to recognise Tags•Reclassifies Components based on Tag structure

•Tag manifest and BOM is then possible

•Used by INOVX, AVEVA, Bentley, Octaga and

VRContext for intelligent Navigation

15


Dumb to IntelligentDumb to Intelligent


Dumb to IntelligentDumb to IntelligentSymbol Graphics are Components

Tags from multiple text strings

SVG from enhanced model

16


Pattern matchingPattern matching• Matching of the text string

– Text belonging to a Symbol– An attribute of a Symbol– Free standing Text

• Pattern defined in a “ClassMap”• Parent object reclassified• New Parent created


<Entity Class=“Text”><Attribute Name=“String” Patternmap=“Tagmap”/>

</Entity><Entity Class="TagMap" MapType="PatternMap">

<Attribute Pattern="A-NNNN" NewClass="Equipment"/><Attribute Pattern="n-*-NNNNN-NNNNNA"

NewClass="PipingNetworkSegment"/></Entity>

Pattern MatchingPattern Matching

This will match a text string and reclassify the Component that contains the string. In the first case as Equipment and the second as a PipingNetworkSegment. Wildcards can be used.

17


Datasheets• Mostly Excel spreadsheets• Use generic Excel interface to read/write• Use Mapping to define the Structure

• Intelligent Datasheet using ISO 15926 classes


ExampleExample sheetsheet

DocumentPart

DocumentCell

18


XML DatasheetXML Datasheet<Document Type=“Datasheet” Name=“28-1A-KOG-154-27500-0012”>

<DocumentPart Name=“Sheet1”><DocumentCell Name=“Title” Type=“string”

Value=“PRESSURE INSTRUMENTELECTRICAL DATASHEET”/><DocumentPart Name=“Header”>

<DocumentCell Name=“PackageNumber”Type=“string” Value=“28-1A-KOG-154-27500”/>

..</DocumentPart><DocumentPart Name=“CalibrationValues”>

<DocumentCell Name=“HighSetting” Type=“Number” Value=“71”Units=“barG”/>

</DocumentPart</DocumentPart>

</Document>


•Operates on the neutral model

•Independent of any P&ID or 3D system

Generic ComparatorGeneric Comparator

•Will enable model updates•P&ID to 3D model comparison

•P&ID comparison, 3D model comparison

•GUI for

•assisted matching

•Results display

19



XMpLantComparator

XMpLantXML

XMpLantXML

Topology, P&ID or 3D model

Map

Topology, P&ID or 3D modelMaps remove objects not relevant to

comparison

Comparereport

Result 1

ZGL3D SVG

2D

Result 2

Results are merged into both original XML files and the ZGL file



Colour coding facilitates identification of differences. Compare results are attributes in the comparison model for ease of review.

20


ConclusionsISO 15926 Dictionary Compliant XML

In use today - proven on large projectsInterfaces for many design systems

Exchange XML files for ISO 15926Visual Navigation P&ID and 3DArchive models as ISO 15926 files

Many use XMpLant technologyPowerful analysis and mapping facilitiesDumb to intelligent processing

iRING connectivity tools being developed


ISO 15926 DeploymentISO 15926 Deploymentusing XMpLant technologyusing XMpLant technology

Operational today

Documents

Why ISO 15926 - THTH ry · PDF file• 1999– First deployed for PDS to CADDS5 • 2003- First AVEVA VNET deployment ... • Schema defines Dictionary compliance of ISO 15926 –