Semantic relation modelling version: 1.1 02-03-2005 - 1 Croon Elektrotechniek B.V. A practical...

Semantic relation modellingversion: 1.1 02-03-2005 - 1

Croon Elektrotechniek B.V.

A practical information management framework based on ISO 10303 STEPlib

Leo van Ruijven

Senior consultant

Knowledge and Procesmanagement


Background Croon TBI techniek:

• TBI Holdings consists of approx. 110 companies

• Turnover of TBI Holdings in 2003 is €1,73 billion

• TBI Holdings employes more than 10.000 people

Croon is a modern systemintegrator

Marketsegments industry, marine and buildings

Turnover 2003 is €197 million

Croon employes 1500 people

Croon is part of TBI holdings, division TBI techniek


Subjects:

Some principles of the information management framework

The use of a generic engineering language

The dictionary structure

The resulting framework

The use of templates


Background: success factors of effective cooperation in the process industry

1) Alliance-formula:Open relationships and trust between partners

Acceptance of behavior code by all partners

Integrated design and execution

Shared risk and reward

2) Information management:

Explicit , consistent information (from requirements to maintenance information)

Generic language which can be interpreted by human and computers as well

Common understanding and standardization of terms

Generic information exchange format

This is the subject for this presentation!


The frame work is based on the principles of a system

Task 3

Task 2

Task 1

Element 1 Element 2 Element n

Approach valid for:• Organizations• Chemical processes• Products• Constructions• Etc.Elements fulfil tasks within the system;

Fulfils

Fulfils

Fulfils

Principle / technology

•Content (elements), •Structure (relations),•Behaviour (functions).Functional decomposition

One of more tasks form a process function;

Structure subsystem

Elements react on each other by relations;

Processfunction 1

Processfunction n

Process function structure

The whole of the process functions forms the objective of the system.

Material, energy, information

Material, energy, information


The frame work supports the System Engineering design methodology

Analysis of objectives, requirements and environment Design process management:

Requirement managementInterface management

Risk managementDefining an integrated functional architecture (including functional interfaces)

Analyse loop

Customer needs

According to IEEE 1220 and ISO 10303 AP233

synthese loop

Product design

Verification Transforming the functional architecture to a physical architecture (including physical interfaces)


Checking: One of the basics of System Engineering

Verification consists of proof of compliance with specifications, and may be determined by a objective test, analysis, demonstration, inspection, etc.

“Have we made the product correctly?”

Productdesign

Productrequirements

verification verification

Product realization

validation

validation

Validation consists of proof that the system accomplishes its purpose. It is usually much more difficult (and much more important) to validate a system than to verify it. “Have we made the correct product?”


The frame work supports the “whole – part” lifecycle concept(essential for configuration management and maintenance)

Functional object :pump with tag 13P01

Time

Pump of manufacturer ASerial nr 34562

Whole life cycle of functional object “pump with tag 13P01”

1e Part of whole life cycle

Part of whole ”realizing functional object pump 13P01”

Begin of life end of life

Pump of manufacturer B Serial nr 3A_4562


Pump of manufacturer A Serial nr 104562



Why a new framework for information management?

Research learned that:

• Existing PDM /PLM systems don’t cope enough with the

complex information needs of SE

• Relational databases becomes very complex to manage all the different

information needs

Reasons can be found in:

• Meta-information models of PDM/PLM systems are restricted

• The focus is basically centered on product- or work-breakdown or documents


What is basically needed for information management that cope with SE ?

Generic grammar:Generic rules for combining terms to facts, such that these facts can be interpreted by computers and human as well (generic engineering language)

Technical dictionary:A standard set of terms with definition for all system or plant-items. (physical objects, properties, functions, substances, activities, geometry etc.)

Semantic relationterm A term B

Using both leads to facts

Terms are: a dictionary term, project specific term or a project specific value


UID Lefthand object UID Righthand objectRelation UID

name Name name

contextcontext

Fact-ID

language

• Validity• Status• Source• Remark

“main fact”

description

Defining explicit relationships with facts in the Gellish Tabel Format

Object classes defined in the framework dictionary

Life cycle management:• successor fact ID• author latest change• start date• date latest change

Unique Identifier


Principle of Generic Engineering Language (grammar):

Function q Is realized by Thing aThing a is specialization of Dictionary term bThing a is part of Thing cThing a is of manufacturer Organisation dThing a has function Function eThing a has property Property fThing a has property Property gProperty f is qualified as <quality>Property g Is quantified as <value>Thing a has to be compliant with Information xThing a is located in Geometry element yThing a Is described by Presentation of information z

Semantic relationterm term

The framework use dictionary terms and a generic engineering language

to let you build object information models on the fly


objective

function

activity

processSystem

behavour

geometry

relation

System structure

Col

lect

ion

Property

Info

rmat

ion

pres

enta

tion

Information

physical objectlife form System content

The frame work structure is developed from a System Engineering point of view

Defines:• The project• The product• The processes Trough the whole life cycle

“A project is a complex integration of several systems”


Dictionary structure of the framework

view model level: business object level: dictionary object level

Physical object system electrical systemmaterial medium support item mastconnection electrical cable connectionequipment item mechanical equipment item

Occurrence event tripprocess business processactivity to verify

Information object procedure algorithmsignal analogue signal

software control softwareDocument design document functional design documentLife form organisation supplierGeometry shape cylindrical form

space roomFunction system function limiting shortcurrent

process function separatingObjective business objective making profit

project objective delivering in timeCollection collection of property value collection of coloursProperty property absolute property

principle measurement principlequality attitude

Property value status value as-required


Use of the ISO 15926-4 library within the frame work dictionary

Hierarchy

ISO library

top-object(anything)

business object levelISO dictionary level

Hierarchy framework dictionary

view model level


Principle of relating elements of different view models to each other

Supply energy

Main objective

Objective view model

Section 3.1

specification

Chapter 1 : supplying energy

Chapter 2: limiting short currents

Chapter 3

Requirements Fuses

Information presentation view model

Function 1

Limit shortcurrent

Principle I2t

Main function

Function view model

Subsysteem 1

Energy system

switchboard

Fusecharacteristic

Property

Total System

Physical object view model


Specification of a chilled water unit (“object information model” or “template”)

chilled water unit is the whole for <1 .. 3> compressor

compressor is of type semi-hermeticcompressor is of manufacturer Carrierchilled water unit is the whole for <2> condenser condenser has property cooling medium cooling medium is qualified as LT waterLT water is supplied by clientchilled water unit is the whole for <1> liquid coolerliquid cooler is the whole for <2> circuitscircuit is the whole for <1> pumppump has function circulating the chilled waterpump has property pump capacity pump capacity is qualified as 50% of the unit capacity

liquid cooler is the whole for <1> starter panel

Chiller will have a number of semi-hermetic Carrier compressors, two LT water-cooled condensors, one liquid cooler with two circuits and starter panel. Two chilled water pumps will be installed for circulating the chilled water, each capable for 50% of the capacity.

object grammar cardinality Dictionary object

Project specific object

Project specific value


Exchange of information between project-partners based on templates

Sub-system definition, requirements etc.

HVAC contractor

system definition, requirements, etc.

Client

Sub-sub-system definition, requirements etc.

Electrical contractor

Reference data library (standard template’s

and objects)

Exchange of product information, based

on object information models (templates), exchanged by XML

or excel sheets

chilled water unit is the whole for <1 .. n> compressor

compressor is of type semi-hermeticcompressor is of manufacturer Carrierchilled water unit is the whole for <2> condensercondenser has property cooling medium cooling medium is qualified as LT waterLT water is supplied by clientchilled water unit is the whole for <1> liquid coolerliquid cooler is the whole for <2> circuitscircuit is the whole for <1> pumppump has function circulating the chilled waterpump has property pump capacitypump capacity is qualified as 50% of the unit capacity

liquid cooler is the whole for <1> starter panel

“chilled water unit” object information model (template):


Relation viewer of the framework


Realized pilot project with the framework:

Electrical &Mechanical installations of the Westerscheldetunnel (6 km road traffic tunnel)

design and construct including 10 years maintenance:

Designperiode: 5 years Buildingperiode: 3 years (strong overlap with design) 10 main- and 70 sub-systems 20.000 items of E, M and softwaremodules 4000 documents 850 locations

data-sharing with partners by a intranet-application (configuration, change- interface- en documentmanagement)


As-built test-activity related with required function


Final:

Gellish enables to define explicit information in an easy way, without defining a information model first;

Gellish can be seen as semantic relation modeling;

Gellish is useable for relating contract-, design-, build- and maintenance information through the life cycle of a plant;

Gellish is represents the grammar part of ISO 10303 STEPlib; Gellish can be mapped to ISO 15926-7 templates

Gellish is in developing by the gellish forum and is open source;

For more information about gellish: www.sourceforge.com


Thanks for your attention

Date post:	01-Jan-2016
Category:	Documents
Upload:	neil-ball
View:	216 times
Download:	0 times

Semantic relation modelling version: 1.1 02-03-2005 - 1 Croon Elektrotechniek B.V. A practical...

Documents