Croon Elektrotechniek B'V' Leo van Ruijven

1
Croon Elektrotechniek B.V.
Leo van Ruijven
Practical use of Gellish and the relation with
ISO 15296 (semantic relation modelling)
2
Subjects of this presentation

• Needs of technical information management (within
  the context of EM )
• A framework for a practical technical information
  management system, based on system engineering
• The use of the Generic Engineering Language
  (Gellish) and a Reference Data Library (RDL)
  within the framework
• Relation and analogy with ISO 15296
• Practical roadmap for implementing ISO 15296
  standard

3
Objective of technical information management
(within the context of EM )
The main objective A better prise quality ratio
Derived objective Technical information
management must cope with the information needs
as can derived from System Engineering (SE).
( System Engineering as defined by INCOSE and
subject of ISO 10303 AP
4
SE enables us to cope with the complexity of
todays products
Customer needs
Analysis of objectives, requirements and
environment
SE According to IEEE 1220
5
Analysis of product requirements (responsible for
gt 50 of failure costs)
subject
Viewpoints
Experiences
specification
Terms ...
Objectives.
Solutions
Requirement
Implicit Information
client
6
A framework for a practical technical information
management system
Product Objective
These are fundamental views on a product (the
view model level of the framework)
Supporting views Information representation
view, collection view
7
Example of a product view
process view model

• Design process
• conceptual design process
• Requirement analyses process
• Analysis of objectives and environment
• Identify functional requirement
• Define performance requirements and prior
  design conditions
• Functional analyses process
• Decompose sub-functions
• Define performance requirements and
  conditions for sub-systems
• Define functional interfaces (intern and
  extern)
• Define an integrated functional architecture
• Define maintenance and operations strategy

8
Principle of relating elements of different views
to each other
Objective view model
Main objective
Supply energy
9
Making relations explicit, using a Generic
Engineering Language (gellish)
Objective
10
Defining explicit relationships using
main-facts in Gellish Tabel Format
Object classes defined in the framework library
name
Name
name
Relation UID
Fact-ID
UID Lefthand object
UID Righthand object
main fact
context
description
context

• Configuration management
• successor ID
• author latest change
• Start date
• date latest change

• Support for templates
• plural fact ID
• template text

• Units of measurement
• UOM UID
• UOM name

11
Library of the framework starts with the
business object level (can be business specific)
12
Problem with using the Epistel or STEP
libraryNo connection with the world of
engineering
?
?
?
13
Replacing the top of the ISO library with the
view model and business object level
Hierarchy ISO library
top-object (anything)
14
The framework is fully based upon object oriented
templates
Any object in a view model can be characterised
by a set relationships with other objects
(resulting in a collection of facts, together
forming a gellish template)
A gellish template can be seen as
machine-language code, using local variables
(only valid within a specific template) and
global variables (defined in the library) either
can be invariant or variant (parameter)
15
IO module example to show the use of gellish in
combination with templates
16
Template structure of the IO module example
Generic description of IO modules
concept template IO module
concept template IO port
17
concept template IO module and IO module port
generic knowledge
18
Class template 4 DI module and module input port
a specific kind of IO module
19
Instantiated class template 4 DI module and
module input port
20
Example of 15296 part 7 template
21
Conclusion gellish can be a analyses language,
as preparation for part 7
gellish
Part 7
mapping
Gellish offers a way to learn to analyse the
needs and structure of templates, serving a
specific business ( leading to an essential
business model)
By mapping the gellish template structure on part
7 templates, the essential business model
becomes ISO 15296 compliant
22
Template in the context of ISO 15926-7 and
translation to gellish
23
Reasons for starting with Gellish first
Technical engineering communities has already
developed engineering database (EDB) for several
purposes and areas of interest (not integrated)
Translation of legacy EDBs to 15296 standard in
one time will be very complex
Technical engineering communities dont adopt
easily a overruling technology, even if it is
better (not invented here syndrome)
Technical engineering communities must have the
opportunity to discover the advantage of
semantic relation modelling by them self
(culture change !)
(Advantages in this context are Defines ones,
use many Integration of disciplines, areas of
interest of legacy EDB Possibility to exchange
information, based on a RDL)
Gellish offers a way to learn to think in
fundamental and explicit expressions about
products, and shows the power of semantic
relation modelling (creating awareness)
24
When can a company work with ISO 15296 ?

• If the business is analysed and structured in
  (gellish) templates

If the templates and object information models
are stable
If there is a explicit need for exchange of
product information
If tools are available for working with ISO 15296
If the organisation is ready for thinking in, and
working with ISO 15296
25
Implementation process of the ISO 15296 in
relation to CMM level
development company
Using Gellish
1st phase Control (awareness and understanding)
efficient
1
2
3
4
5
optimising
chaotic
Capability Maturity Model Level
26
Actual example in the area of shipbuilding (HVAC)
Branch Reference data library
Exchange of product information, based on XML or
excel sheets
Object templates based on gellish
system definition, requirements, etc. Yard
Sub-sub-system definition, requirements etc.
electrical-contractor
Sub-system definition, requirements etc. HVAC
contractor
27
Snapshot data management tool of EM installation
traffic tunnel (6Km), based on semantic
relations (as required as designed- as build)
28
Snapshot protoype framework tool
29
Thanks !