Reference Data for Dummies

Reference Data in action

An overview of ISO 15926 representation and (possible) operation

Tore R. Christiansen Vestforsk, Sogndal, Friday 12 September 2008 This presentation has five parts

Motivation for Information Standards and Reference Data

Structure of the ISO 15926 standard

Operation and Maintenance of Reference Data Libraries

Reference Data in Offshore Field Development and Operation

Reference Data in Concurrent Space Engineering

This presentation is an informal and enjoyable (?) tour There will be more formal tours (?) in subsequent presentations Please ask and give feedback underways

Complex installations with long life-times

Large cost of production and operation

Large volume and cost of documentation

Many interdependent players Cost effective cooperation requires correct information Great demands for and coordination and collaboration

Demand for effective information exchange

Demand for accurate description

Great need for common languages

The ambiguity of learning

The uncertainty of knowledge

The complexity of information

The volume of data

How can we be sure that we Analyse send and receive correct data and understand it in the way it was intended?

Transform

Bergen

External experts External experts Vendor’s onshore operation centre Process

Stavanger Receive n o ti a ic n u Analyse m Control room Transmitm Aberdeen o c e m Re ti al t l ime a Store data Collect e R Operator’s onshore operation centre

• Better and faster decisions • Streamlined delivery Collaboration chains rooms

Owner Designer

Send XML-message specifying ”pipeline”

I need a ”pipeline” What does he actually mean with these functional by the word ”pipeline”? characteristics

Philosophy

axiomatic concepts, such as thing, class, individual. and property ISO 15926-2 Data model generic engineering concepts, such as physical object, (200 entity types) activity, composition, connection

text book concepts, such as pump, centrifugal pump, reducer, heat exchanger ISO 15926-4 Core set (10000 classes) classes defined by international standards,

and industry associations

s company commodity classes r

e a

y e t

v g

i t

User defined 35000 t classesc defined byc various projects

o a a i

p r

classes t

u m a

o n catalogues from suppliers and

t i

r e a

u l

e O

E manufacturers A Shipping M A

Real world instance data

User system (proprietory format) and Users S Per User Instances in Facades t a Proprietary Objects and Document Classes Per User n d ISO 15926-7 Object Information Models a r ISO 15926-7 Templates d i ISO 15926-4 Reference Data z a t ISO 15926-2 Data Model i o ISO 10303 Implementation model n Express

© Det Norske Veritas AS. All rights reserved 27 October 2008 Slide 8 © Det Norske Veritas AS. All rights reserved 27 October 2008 Slide 9 © Det Norske Veritas AS. All rights reserved 27 October 2008 Slide 10 © Det Norske Veritas AS. All rights reserved 27 October 2008 Slide 11 © Det Norske Veritas AS. All rights reserved 27 October 2008 Slide 12 The structure of product information models

Specific products Instance models A p Applications Reference-models p Ontologies Constraints and behavior p I Properties and relationships Thesaurus c Part hierachies Taxonomies a t i Reference classes Vocabularies o n Names and numbers Signs

Class meta-data

Classes matching search criteria

”Superclass relationships” ”Subclass relationships”

Custom search and display

Format for exporting and importing classes and relationships

Directory of classes

SWRL, SPARQL Rules and conditions

OWL Relationships and constraints S RDF Schema Classes and instances e c u Resources and relationships RDF (O-A-V triples) r i XSD, Xpath, XMLns Data and document models t y XML, XSL, XSLT Syntax and structure

Unicode, URL/URN, XMLns Tokens and references

P21 Master storage Dump SOAP/WSDL/XML Indexing P28 Export Conversion Web Services Express Reporting Extract

Convert RDS Import SQL Data exchange

Transform RD Browser XML Visualization Convert Info exchange

XSLT RDF Transform Reasoning Transform HTML Improvement Manage Information Quality based on Protégé OWL - Stable storage Transform Swoop - Standardized exchange Racer - Intelligent application Pellet

Reference data

RDS Internet

Query Information

WS Extranet WS

Question Solution

Intranet App Rep

People and computers

© Det Norske Veritas AS. All rights reserved 27 October 2008 Slide 19 © Det Norske Veritas AS. All rights reserved 27 October 2008 Slide 20 © Det Norske Veritas AS. All rights reserved 27 October 2008 Slide 21 Reference Data in the lifecycle of a pipeline

The objective of this example is to illustrate how …

… definition of Reference Data allows representation of product information with enough detail and breadth of scope for accurate description of real world technical artifacts and installations

… extension of Reference Data with relations and properties allows construction of product models that can serve as a mechanism for information exchange between application programs used throughout the product lifecycle

… representation of Reference Data and relations in formal logic-based knowledge bases allows information integration between sources with different coverage and consistency

… grounding of Reference Data in a standardized upper ontology (meta-model) allows development of formal processes and procedures for lifecycle management of change in structure and behaviour engineering artifacts

Offshore oil field development east of Sakhalin island

Requirement from Russian owner for pipeline transport to loading facility on the Siberian mainland

Process design of pipeline by Japan oil company in Tokyo

Detailed engineering by engineering contractor in Mumbai, India

Procurement of pumps from manufacturer near Kiev, Ukraine

Procurement of pipe from manufacturer near Delhi, India

Transportation from manufacturer to site

Installation on site by local project team from Russian owner

Inspection of pipe wall thickness on site by surveyor from DNV Vladivostok office

Procurement and replacement of corroded pipe section

The scenario uses terms and definitions from the Reference Data Library to

Identify design objects

Represent design alternatives

Exchange data between a set of (mock-up) engineering applications

Manage all real-world artifacts

Ensure information quality across all life-cycle phases

Rules for matching requirements to functions (optimal choice between matching classes) Rules for checking network consistency (continuity of flow from source to sink) Sem- talk CAD OWL Rules for selecting pipe diameter Require- Conceptual drawing (contant flow rate of incompressible fluid) ments design OWL ERP Rules for selecting pump type and size system (contant pressure across pumps) Sem- talk CAD drawing RDS SemTalk Process design OWL Rules for selecting manufacturers Rosneft Russia ERP system (features, performance, location, and price) Sem- talk Required CAD Detailed drawing solution RDS Racer engineering OWL Oil reservoir ERP Rules for procuring and completing construction Fluid transport device Japex Japan system (actual individuals with zero GregorianDateAndUtcTime) Sem- Storage facility talk CAD Proposed drawing Procurement solution RDS Internet OWL and installation ERP Rules for representing inspection and maintenance Oil producing well Larsen & India system (events with non-zero GregorianDateAndUtcTime) Pipeline Thoubro Sem- talk Storage tank CAD drawing Evaluated Inspection RDS Access And maintenance OWL solution ERP Surya Pipeline manifold Russia Global system Pipe section Energo Ukraina Centrifugal pump Sojuz Tank Specified RDS Access

solution DNV Russia Specific pipe section Specific centrifugal pump type Rosneft Russia

Realized solution Pipe individuals Pumps individuals (all at t=0) Supported solution Pipe individuals Pumps individuals (at t>0)

Information Quality Management

installation and operation

Pipeline Field

Terminal

Pump manufacturer

Inspection by local office Concept design finds corroded pipe

Replacement pipes

Pipe manufacturer

Detailed engineering

Given need to transport oil from reservoir to loading facility

Given that offshore loading is not practical

Specify use of a pipeline as fluid transport device (pumping oil through pipelines to loading and storage facilities)

RDS SemTalk

Rosneft Russia Required Proposed solution solution Oil reservoir Oil producing well Fluid transport device Pipeline Storage facility Storage tank

Functional Objects

RDS

Conceptual

Designer Link to RDL definition Find RDL definition Process of ”pipeline” of ”pipeline” Designer

Send XML-message specifying ”pipeline”

You need to use a ”pipeline” Ah, so this is what he means with these particulars when he says ”pipeline”

Given required flow rate

Dimension pipe diameters

Given allowable pressure range

Determine pump capacity and pipe dimensions

1 small manifold 2 thin pipes require require 1 thin pipe 1 medium pump 1 medium pump require 2 medium pipes 1 medium pipe 1 large pump require require 1 large pump 1 thick pipe

RDS

Process Link to RDL definition Find RDL definition Designer of” Pipe section 12 NPS ID” of ”Pipe Section 12 NPS ID” Engineer

Send XML-message specifying ” Pipe section 12 NPS ID”

Use ”Pipe section 12 NPS ID” Ok I see, for this part of the pipeline ”Pipe section 12 NPS ID”

Given pump capacity

Select specific pump products according to performance (and price)

Given pipe diameters

Select specific pipe products according to price (and performance)

Sem- talk CAD drawing

OWL ERP Rules for selecting manufacturers system (features, performance, location, and price) Sem- talk CAD Detailed drawing engineering OWL ERP system

RDS Internet

Larsen & India Thoubro

Semtalk.lnk

RDS PDS

Get Product Data Library Get Product Data Library definition of ”NM 125.500” definition of ”NM 125.500” Engineer Supplier

Send XML-message specifying 4 specimens of ” NM 125.500” Owner I need to order - 4 ”NM 125.500” - 2 ”NM 250.475” He wants four of my ”NM 125.500” pumps - 1 ”NM 500.300”

Given order for specific pipes and pumps

Produce and deliver pipes and pumps

Given delivery of acquired product

Install pipes and pumps

2 medium pumps 1 large pump

Thin pipe Medium pipe

Thick pipe

RDS PDS PDW

Link Link

Get Product Data Library Link to Product Data Library definition of ”NPS 16 OD 16 SCH 60” definition of ” NPS 16 OD 16 SCH 60” Write pipe data into Project Data Warehouse Supplier for locations ”position 0” to ”position 1500” Operator

Send XML-message specifying 30.000 pieces of ”NPS 16 OD 16 SCH 60” pipe from ”position 0” to ”position 1500”

I need to document the pipeline in the PDW We have delivered 30.000 pieces of with 30.000 pieces of ”NPS 16 OD 16 SCH ”NPS 16 OD 16 SCH 60” pipe. 60” pipe from ”position 0” to ”position 1500” Installed from ”position 0” to ”position 1500”

Given installed pipelines in operation

Perform DNV inspection of pipe to verify wall thickness

Replace corroded pipe

RDS PDS PDW

Link Link

Access Project Data Warehouse Link to Project Data Warehouse get product data for location ”position 125” definition of ” NPS 16 OD 16 SCH 60” Link to Product Data Library Update Project Data Warehouse Inspector definition of ”NPS 16 OD 16 SCH 60” for location ”position 125” Operator

Send XML-message specifying 200 meters of ”NPS 16 OD 16 SCH 60” pipe at ”position 125”

The inspection shows a need to replace I need to place an order for 200 meters of 200 meters of ”NPS 16 OD 16 SCH 60” ”NPS 16 OD 16 SCH 60” with the supplier and pipe at ”position 125” prepare my team for installation at ”position 125”

The European Space Agency studies many potential space missions

Early phase engineering Space Mission involves feasibility and functionality

More than twenty disciplines are mutually dependent

Need to develop and use advanced collaboration tools

ESTEC hosts the ESA Concurrent Design Facility

Currently based on linked set of Excel workbooks

Currently requires simultaneous on-site presence

ESA wants to distribute design and work with national partners

An Open Concurrent Design Server (OCDS) based on Web Services

Common Space Engineering Information Model (SEIM)

Shared Space Engineering Reference Data Library (SERDL)

X = Video Camera X X Positions Web Broadcast Station MULTIMEDIA WALL

Presenters Desk Team Technical Leader Author

Systems Cost Customer and Ad-Hoc Experts . Config Risks

Structure Progr .’s

Mechanisms Simulation

Instruments

AOCS Thermal Propulsion Power StorageStorage Cabinets Cabinets DHS Mission GS & Ops Comms ESTEC Dh015

CDF intermediate layer Presentation worksheet Input worksheet Reference Data represented Calculation Output according to Calculation worksheet worksheet ISO 12006-3 worksheet Input Input worksheet worksheet Web Service clients Output Output worksheet worksheet

Central data store Data exchange for project data via standard Data parking EDM Document instances web services Document templates protocol Domain Domain XML file XML file specific tool specific tool Standard reference data Syntax and based on common semantics information model defined by RDS ISO 10303-239 Peripheral data store

XML file Peripheral CDF core IDM data store Web Service client

SEIM Main Information Objects and Relationships

Space Engineering Space Engineering Space Engineering Involves Involves Organization Process Product

C s re fie s a si ssifie te as Cla s Cl

Concurrent Design Facility Concurrent Design Facility Is Part Of Parameters Infrastructure

ECSS ISO 10303-239 ISO 12006 OCDS SEDM SERDL SERDL Standards Standard Standard Web Services Documentation Documentation Iteration 3

Engineering Disciplines and Organization System Engineering Process Levels of Decomposition

CDF CDF Involves Role Involves Option Option Role Activity

d Involves me IsR for ela System ipant er g ted tic IsP rin To ar Du P ves ol Inv Equipment CDF Space Instrument CDF Consist s Study Activity Engineering Session Of Subsystem Is Phase Phase Discipline Represented Participant Element By IsSavedIn

System Snapshot

r IsStoredIn Fo ion pt El O em Is s e Ha lve se nt s ha P /E r nvo P r qu r Fo I n op ip Iteration Fo nt io e m Organization e me iss rty e s uip M nt ha beq gP Su Is in nt/ Is C er me U r e uip s e in Eq e a ng nt/ r to E me O r e tru f O ac /Ins f Sp em s yst I ubs Mission Phase Mode Property nt/S me /Ele em yst Is S or ase F ionPh or Miss mMode F For Is /Subsyste entProperty entMode perty/Equipm ode/Elem ElementPro s SystemM Is Concurrent Design Parameters, Units and Dimensions I Concurrent Design Facility Infrastructure and Documentation

Study Study CDF IsPartOf Parameter IsPartOf IsPartO CDF Discipline f IDM IsBasedOn Parameter Group Group WorkSpace IDM Template IDM Template Workspace (workspace)

H s n a H H a io V s as Has D as H ns al C s ocu e ue ode port men im Re tatio D n

CDF Parameter Has Parameter Parameter Parameter Study OCDS Documentation Unit Unit Dimension Value Code Report Server and Tools

Note that the SEDM has included Organization Classes Legend Specialization relationship four additional relationships in order to implement the model in OCDS - (superclass/subclass) Process Classes included in Iteration 3 Relationship names in red connect Reference Data (RD) classes defined in different model dimensions Is Participant For Option between Option and Participant Specialization relationship Object Classes Relationship names in black are between RD classes defined within same model dimension Is Discipline For Option between Option and Discipline not included in Iteration 3 Is Mission Phase For Option between Option and Mission Phase Data Classes Miscellanous relationships Is Participant In Session between Participant and Session Relationship SEIM Top name (classification: membership) Equipment Classes (composition: part of)

HasSystem

System Option System Involves Involves Mode (OPT) System (SYS) System Mode (SYM) Element

olves Has Inv se n Pha Missio

Element Mission Phase Element Involves Mode (MIP) (ELE) Element Mode (ELM)

S u H b a s s ys y te as ert m H op Pr nt me Ele nt s e a H um SubSystem r Element t Subsystem Involves s n Mode t I Subsystem Mode Property n (SS) e (SSM) m (ELP) s ip a u H q tE n e m le E The product hierarchy is: Option + System + Mission Phase + System Mode + Element + Element Mode + Element Property + Subsystem + Subsystem Mode + Instrument + Equipment + Equipment Property + Subequipment

Instrument The Space Engineering Reference Data (SERD) values are created from CDF Reference Parameter Types (RTP) Set by combining Information Object Counters (IOC - e.g., ELE# with value ELE1, etc.) and RTP Names (e.g., mass) (INT) to give instantiated values (e.g., OPT1_mass). The legal ordering and combinations - Has ent OPT#_SYS#_RTPname ntEquipm Instrume OPT#_SYS#_MIP#_RTPname OPT#_SYS#_MIP#_SYM#_RTPname OPT#_SYS#_MIP#_SYM#_ELE#_RTPname Equipment OPT#_SYS#_MIP#_SYM#_ELE#_ELM#_RTPname Module Software Product OPT#_SYS#_MIP#_SYM#_ELE#_ELP#_RTPname (EQT) OPT#_SYS#_MIP#_SYM#_ELE#_ss_RTPname OPT#_SYS#_MIP#_SYM#_ELE#_ss_SSM#_RTPname OPT#_SYS#_MIP#_SYM#_ELE#_INT#_RTPname Has OPT#_SYS#_MIP#_SYM#_ELE#_INT#_EQT#_RTPname S OPT#_SYS#_MIP#_SYM#_ELE#_EQT#_RTPname rty ubequip s pe ment OPT#_SYS#_MIP#_SYM#_ELE#_EQT#_EQP#_RTPname Ha ro ntP OPT#_SYS#_MIP#_SYM#_ELE#_EQT#_SEQ#_RTPname me Equipment uip Eq Subequipment All abbreviations for the above IOC’s are listed in the SERDL Documentation (which is linked from the SEIM top page) Property Assembly For instantiated values the # sign in IOC’s are replaced by the relevant number for the Information Object (SEQ) (EQP) For Parameter Values that apply to all instances the IOC is dropped (most often for OPT# and SYS#) Note that The ”ss_” is not replaced by the relevant Discipline (instead the SERD instance has Discipline as its Creator) All Equipment (EQT#) can be part of Elements (ELE#) as well as Instruments (INT#) Eigenfrequencies are treated as subtypes of Element Property (ELP#) Ground Station, Solar Array, Battery and Antenna are treated as subtypes of Equipment (EQT#) Coverglass Thickness and Dose Depth are treated as subtypes of Equipment Property (EQP#) Part Software Module Legend Specialization relationship Included in (superclass/subclass) SERDL iteration 3 included in Iteration 3 Specialization relationship not included in Iteration 3 Not included in Miscellanous relationships SEIM Relationship SERDL iteration 3 name (classification: membership) Relationships Note that only parts of the Product break-down structure is in scope for Concurrent Design in the CDF IDM (composition: part of) (and thus not all parts of the break-down structure has been included in SERDL Iteration 3)

S o t u H m s n b a a e s s p y o H m s e t s l e i m t E i o