MEDI 2012 - LIAS/ENSMA - Futuroscope - 5 Octobre 2012 1 / 51 15/01/2015 INTERCRITTs 1 ENSMA, BP 40109, Téléport 2, 1 avenue Clément Ader 86 961 FUTUROSCOPE

MEDI 2012 - LIAS/ENSMA - Futuroscope - 5 Octobre 2012 1 / 51 11/04/23 INTERCRITTs 1

ENSMA , BP 40109, Téléport 2,1 avenue Clément Ader

86 961 FUTUROSCOPE cedex

05 49 49 80 78 - 05 49 49 80 64 [email protected]

http://www.ensma.fr/crcfao

Eric Sardet – Technical [email protected]

Development and use of ontologies in the engineering

domain

Téléport 2 - 15 avenue René Cassin86 961 FUTUROSCOPE Cedex

FRANCE

+33 (0)5 35 54 23 91- +33 (0)5 35 54 24 33

CRITT Informatique ?

Status: Set up in 1986 by LIAS/ENSMA CRT (Technical Resource Center) supported by the French Ministry

of Science and Research. Activities :

Information systems (CAD, PLM, PDM, …), Data modeling, exchange of technical data, Mobile computing Internet Technologies, Database management, …

Personnel: 5 doctors / engineers (mechanics, robotics, …) 2 software engineers Numerous consultants and trainees

Missions : promoting innovation and technology transfer SMEs LABORATORIES approach LABORATORIES SMEs approach

MEDI 2012 - LIAS/ENSMA - Futuroscope - 5 Octobre 2012 2 / 49

Exchange of technical information:PAST and PRESENT situation

: paper document Design

PurchaseSales

R&D Processcontrol

Plant

Maintenance DB

Equipment managt

PaperCatalogues

requirementsrequest

FAX

Product data

Cataloguechoice

offer

FAX

Productdata

documentation


Sales

R&D

Plant

Web(Internet)

Maintenance DB

Equipment managt

Productdatabase

Processcontrol

CAE

n manufacturers

Purchase

Contractual framework

Order

CLIENTSUPPLIER

Exchange of technical information:the FUTURE …

Request(Requiret)

Request(Requiret)

documentation

Offer(Product

data)

New products

Consultation/ criteria

Objective of ontologies: Computerizing an existing

technical know-how


Content

Ontologies in technical domains: specific needs

An ontology formalization language: PLIB (Parts Library, ISO)

Development process of ontologies in the engineering domain

Domain ontologies for database integration

Industrial experiences

Conclusion


Ontologies in technical domains: specific needs

NeedsLanguageProcessIntegrationExperiences


Industrial problematic

To have at one’s disposal: The right data In the right place At the right moment In the right format ...


Strong user requirement: Getting pertinent information on components

Ball bearing NF E 22_300

Screw 10-5-A NF E 25-111

Whereas everything aims at: information system heterogeneity, data model incompatibilities, data obsolescence risk.



Units of measure

D, B, d: expressed in millimetre ? millimeter ? mm ?

Needs to explicitly define units of measure

More generally: make explicit technical information



Nature of properties

Characteristics

• d: internal diameter• D: external diameter• B: width• Nmin: …• Nmax: …

Conditions of use • n: rotation speed• Frad : radial load• Fax : axial load

Behavior• L 10h : life length

Depends on


Different point of views on the same product


Ball bearing

2D – Representation

Schematic representationCalculus

Simplified 3D representation

. . .MEDI 2012 - LIAS/ENSMA - Futuroscope - 5 Octobre 2012 10 / 49

Derivation functionsNeedsLanguageProcessIntegrationExperiences

d D B Cdyn C0 nkin ntherm weight

mm mm mm kN kN 1/s 1/s kg

180 200 31 140 145 5600 2800 6.64

Characteristics

Frad Fax n

kN kN 1/s

50 2.5 980

Conditions of use

L10h

106 n

Behavior

e = 0.22If Fax/Frad <= e

Then P = Frad

If Fax/Frad > e

Then X = 0.56 and Y = 2 and P = X*Frad + Y*Fax

L10h = 100 000 / (60 * n) * (Cdyn / P)^3

Derivation functions

856


Heterogeneity,incomplete descriptions


ManufacturerSupplier

04702

Distributor

04702 387-0442

Re-capture

Problems: Data capture errors Multilingualism ? Maintenance: initial requirements representation ? Bill of material based data: database queries ? Integration: exchange automation ? …

Re-capture

Re-capture

User

Code Designation

AAABBB…

TimerBearing…

Ball bearing NF E 22_300

Screw 10-5-A NF E 25-111

Product


Summary …

Needs: Accurate characterisation of objects Structuration of objects in classes Identification of concepts for referencing purposes Identification of objects Multi-representation of objects Harmonization / automation of exchanges …

Solution: Domain ontologies

o For concept (classes, properties, …) identificationo For information structurationo For object characterization

An interoperable framework allowing data exchanges between business partners



An ontology formalization language



Domain ontologies in ingeneering

A domain ontology is a representation of concepts belonging to a domain in terms of a data dictionary : classes properties relationships between them

A domain ontology has 5 main characteristics : formal consensual multilingual properties are essential concepts may be referenced

Domain ontologies describe concepts of a given domain



ISO 13584 – Parts Library(PLIB)


SupplierSupplierPropertiesPropertiesClassesClasses

diameter,height,...

Information responsibleParts suppliers, standards, ...

defines characterized by

Ontology / dictionary

DocumentsDocumentsresources

Valuedomains

Valuedomains

valuées dans

A set of instancesBDD / Catalogue

Data exchange

System A System BSupplier

SideUserSide

XML(or EXPRESS)

PLIB is a data model for the definition / exchange of (canonical) domain ontologies and of catalogue of products

Géométrie 2D

A set ofrepresentations


Property typologyNeedsLanguageProcessIntegrationExperiences

Intrinsic properties Any descriptive property for which, if the value is changed, it changes

also the product Properties specifying the context

Any property characterizing the context in which other properties are evaluated

Properties depending on the context Any property depending on the context of use of a given product

Representation properties Any property required for representing a point of view on a product

Property descriptors: terminological (translatable):

o Preferred name, short name, synonymous, symbols, images, ... For typing purposes:

o Class, integer, real measure, code, …



Property descriptionexample

Document view

DC: Definition class PLS: symbol VF: Value format DT: Data type SDD: Source document of definition DOD: Date original definition DCR: Date of current revision DCV: Date of current version

Acronyms


Class typologyNeedsLanguageProcessIntegrationExperiences

Characterization classes Classes describing (properties) product families

Representation classes Classes for the representation of a model specified according

to a point of view

Point of view classes Accurate description of a point of view

Class descriptors: terminological (translatable):

o Preferred name, short name, synonymous, symbols, images, ... Descriptive properties relationships between classes



Class descriptionexample

Document

AP: Applicable properties SD: simplified drawing SDD: Source document of definition DOD: Date original definition DCR: Date of current revision DCV: Date of current version

Acronyms


Semantic relationshipsbetween classes


Standardbearing

Bearing

is_case_of(d)

d

D

Communautary ontology

Privateontology

is_case_of relationship subsumption relationship between characterization

classes without inheritance,with explicit importation of properties

GeometricModel

is_view_of

BallBearing

D

Geometricview view_spec

is_view_of relationship Relationship between a characterization class and

a class representing a business model

Bearing

BallBearing

is_a

P is_a relationship subsumption relationship between characterization classes


Concept identificationIRDI



Domain ontology example: electronic domain




Domain ontology example: measuring instruments


Two approaches: Implicit representation (intentional)

o Based on property roles (selectable, computed, contextual), value domains, calculation functions, filters, …

Expression of the selection process Description factorization Complex description Complex implementation

Instance representation

Class IRDI

Property IRDI

Property value

…………………………..

Instances

Property IRDI

Property value

Explicit representation (extensional)o Describing components by the enumeration

property / value couples Simple description of components Any property becomes selectable Simple implementation No selection according to a given context



PLIB Exchange formatISO IS 13584-32: OntoML

XML format (XML Schema) for the exchange of all or part of ontologies (identification:based on ISO 29002-5)

XML format (XML Schema)for the exchange of all or partof product catalogues(includes ISO 29002-10)

Recommendations: Using this format in any engineering project for exchanging

ontologies and/or ontological data Will provide for:

o data consistencyo compatibility of developed applications



Development process of ontologies in the engineering domain



Initial status

Domain ontologies are consensual. They are defined by: Experts of the target domain Modeling experts

For a given business domain, numerous standards of product descriptions are available:

Domain ontologies definition starts from these standards Additionally, integration of the experts know-how

« Bottom-up » approach: Ontology leaves correspond to the standard descriptions Generic classes allow to factorize common properties



Class / propertiesrelationships

Fundamental hypothesis The class hierarchy and the properties shall be defined all together

o applicable properties underline the class meaningo property application domain underlines the meaning of each property

•parts

•SKF_parts

CLASSESPROPERTIES

•inner_diameter

•....

•Mass

•SKF_ref

•SKF_single_ •ball_bearings

•SKF_double_ •ball_bearings

Simple inheritance

Properties status: visible (has a meaning) applicable (necessary condition) provided (depends on the

use)

A « property-based » modelingA class shall be added iff it is a new domain for a property



Local ontologiesVs communautary (global)

ontologies

Particular articulation relationship: is-case-of Semantic of subsumption without inheritance The local ontology explicitly import required properties

Hierarchies of communautary ontologies may be unadapted according to the user requirements

Required properties may not exist Needs to “customize" ontologies: 1 global ontology / N local ontologies

case-of

case-of

case-of

case-of

case-of

case-of

Local propertiespart numberlife cycle...

capacitors conductors

electronics

bearings gears

basic

mechanics

thermometer thermowell

process control

local ontology



Domain ontologies:Some metrics

Mechanical fastener ontology (ISO 13584-511, 2006) PLIB based, French / English 250 classes 410 properties Several man-years

Cutting tools ontology (ISO 13399, 2005) PLIB based, French / English 500 classes 360 properties Several man-years

eCl@ass classification, multi-sector, Germany (www.eclass-online.com) Multilingual ( 15) 33 000 classes More and more properties …



Electronics IEC 61360-4 Process instruments IEC 61360-4 Mechanical fasteners ISO 13584-511 Measure instruments ISO 13584-501 Cutting tools ISO 13399 Bearings ISO 23768 Technical product documentation ISO/TC 10 NWI Optics and photonics ISO 23584…

Standardizeddomain ontologies



Domain ontologies for database integration in an engineering context



Ontologies and data integration

Local (proprietary) domain ontologies : Immediately usable, standard formats, standard tools Integration by « mappings » (a posteriori mapping )

Global (communautary) domain ontologies : Full and automatic integration, multi-supplier search Completeness / needs, evolution

Local domain ontologies + reference (case-of) to a global domain ontology

The local ontology imports required classes and properties Hierarchy may be simplified, class and property set may be

extended Partial and automatic integration (a priori mapping )



Seller scenario

Parts supplier

Ontology delivery + eCatalogue (OntoML)

Ontology delivery + eCatalogue

Users

Local ontology

Local ontology

Global ontologyor standard

Subscription

Reference

Response

Request

mappings

mappings

repository

extractions



Buyer scenario

Buyer SupplierLocal

ontology

Local ontology

Local ontology

mappings

mappings

mappings


Subscription

Standardexchanges

Response

Request



Objective: product or product catalogue exchange, independently of any producer or consumer system

Requirements: Defining a common description language : the domain ontologies

Defining a common exchange syntax of products and catalogues

Providing a framework making possible the data exchanges

o For ontology information retrieving

o For catalogue information retrieving

o For all or part ontology / catalogue exchanges

Contributing to the interoperability of systems



Product descriptioninteroperability

Processcontrol

CAE

Bearing- ID = 0001-1234#01-ROUL#1

d: float, in mm ID = 0001-1234#02-DIN#1D: float, in mm ID = 0001-1234#02-DOUT#1B: float, in mm ID = 0001-1234#02-WIDTH#1

Classlevel

Independence according to the ontology description model Needs to resolve instance references

ISO TS 29002 – 10: product descriptions

Mapping

Sales

Local ontology

Global ontology

class_ref = 0001-1234#01-ROUL#1

0001-1234#02-DIN#1 = 13.00001-1234#02-DOUT#1 = 24.00001-1234#02-WIDTH#1 = 7.0

Instance of

Instancelevel



Ontology modelsinteroperability

class_ref = 0001-1234#01-BEARL#1

0001-1234#02-DIN#1 = 13.00001-1234#02-DOUT#1 = 24.00001-1234#02-WIDTH#1 = 7.0….

Product catalogue

TerminologicalServer

Bearing- ID = 0001-1234#01-BEAR#1

d: float, in mm ID = 0001-1234#02-DIN#1D: float, in mm ID = 0001-1234#02-DOUT#1B: float, in mm ID = 0001-1234#02-WIDTH#1

getType(0001-1234#01-ROUL#1)

getName(0001-1234#01-ROUL#1)

…

ISO TS 29002 – 6: terminology

loading

CAE

0001-1234#01-ROUL#1

0001-1234#02-DIN#1 0001-1234#02-DOUT#1

13.0 24.0

<type>CLASS</type><name lg="e">

Bearing</name> …

CAE

Rolling Bearingd (mm) D(mm) B(mm)13.0 24.0 7.0



Reference interpretationsfrom ontologies

Processcontrol

Local ontology

Mapping

getOntology(0001-1234#01-BEAR#1,

ONTOML)…

class_ref = 0001-1234#01-BEAR#1

0001-1234#02-DIN#1 = 13.00001-1234#02-DOUT#1 = 24.00001-1234#02-WIDTH#1 = 7.0

Product catalogue

loadingCAE

Rolling bearingd (mm) D(mm) B(mm)13.0 24.0 7.0

Ontologicalserver

All or partOf the global ontology

or standard

<ontoml>…

</ontoml>

ISO 13584 – 32OntoML



An interoperability frameworkfor technical data integration

Clients

Localizationservice

Terminologicalservices

(http://194.55.163.1)

Ontologicalservices

(http://194.55.163.2)

01

12

-1--

-13

58

4_5

11

_1#

01

-P5

11

AA

A1

59

#0

01

Terminological server=http://194.55.163.1

Ontological server=http:// 194.55.163.2

21

getSourceIdentification("0112-1---13584_511_1#01-P511AAA159#001")

lookupConcept("0112-1---13584_511_1#01-P511AAA159#001")

3

getConcept(name=« square head screw"; Definition="…. ", ..) 4

5

getConceptModel ("0112-1---13584_511_1#01-

P511AAA159#001",

representation="OntoML", super=false, sub=false, depth=1,

langue="fr")

6 OntoMLfile

(ISO TS 29002-5 identifier)

ISO 29002-20: Web Services



Catalogues interrogation

SupplierLocal ontology

mappings

SupplierLocal ontology

mappings

ISO 29002-31: Queries on product data

Clients

I need a bearing: D > 45 B < 12


<request> <select>*</select> <from class="0001-1234#01-BEAR#1"/> <where> <and> <sup prop="0001-1234#02-DOUT#1">45</sup> <inf prop="0001-1234#02-WIDTH#1">12</sup> </and></request>

Generation

ProjectionQuery

Query

class_ref = 0001-1234#01-BEAR#1

0001-1234#02-DIN#1 = 13.00001-1234#02-DOUT#1 = 24.00001-1234#02-WIDTH#1 = 7.0

Response

Response



Some industrial experiences



Renault, Peugeot - CitroënPHF (1/2)

PHF = Non production material Identified problems:

1 product => n identifications Flat product description => designation No structuration Re-capture => errors

ManufacturerManufacturer

04702

Re-capture

DistributeurRetailer

04702 387-0442

Re-capture

Re-capture

Renault repository

Z 000 296 170 : 3752 CONTACTEUR & CONTACTEUR INVERSEUR I > 10A

NOM !INT !TENS BOB. !CONTACTS ! MINUTERIE ! 16, A! 230VAC !1 "F" !04702 LEGRAND

CODE AUTORISATION : AUTORISATION GENERALE DANS LE GROUP E PSA CODE CLASSEMENT : 37521815/ FAMILLE DA : T80 SECT. ACHAT : 88

UNITE GESTION : UN

PSA Peugeot Citroën repository

R 100 125 808

808

NO MABEC :

DAT CREAT NO : 23/05/1997 DAT MODIF NO : 15/11/2000 DAT CLAS NO : 23/05/1997

DESIGNATION : MINUTERIE 16A 220V 50HZ REGLAGE 30S...10MN SOURCE : C LARG.17,5MM NORME : N

ID DDEUR : VER3 ID PT RVI : SEGMENT : EIB6 ID CODIF : BOUC UNITE DIS : U NOM FAB: LEGRAND REF.FAB: 047 02

CODE CLASSEMENT : X75 218 14



Renault: PHF (2/2)

Codification Chosen solution : ISO/IEC 15459-3 code (e. g., EAN, ODETTE, EDIFICE, …)

Characterization Chosen solution : PLIB based data (OntoML), describing according to a global

(communautary) ontology

Classification Chosen solution : reference to an international classification : eCl@ss

Results: Cost reduction: 3 Millions Euros / year for each group

35 % capture/ data update 20 % claiming 45 % maintenance



CETIM

Technical Center for the Mechanic Industry Title: Product description rationalization Objective: to improve electronic commerce for SMEs/SMIs

Which ontologies ? The existing ones New ones if not already defined

How do we make sure that these ontologies are exploitable by part suppliers, integrators, users ?

By using a standard: PLIB (ISO 13584) By contributing to the emergence of free / commercial tools

How do suppliers to master their own product data and to put them at disposal ?

By developing new mapping tools, new storage solutions, … How organizing information circulation between exchange partners ?

Portals, pear to pear exchanges



Other successful stories …

Toshiba Corporation Philips Siemens DIN: property server (DINsml.net) eCl@ss: multi-sector classification

(www.eclass-online.com)

Zeiss (metrology, medical optic)

Sandvick (cutting tools) ...



Conclusion

Engineering is a domain in which ontologies play and will play a fundamental role

Different ontology models are available, objective are different Information characterization => exchange, integration,

management Information reasoning =>indexation



What’s about tomorrow?

Industry leaders intend to change: Their current product database By a « PLIB-like » data base (structuration, characterization,

identification)

Industry leaders intend to change their requirements about products they are using:

Product => product + characterization data Electronic Exchanges : e-engineering, e-commerce Integration in procurement management systems, …

The technology is ready and fits to the requirements

BesoinsLangageProcessusIntégrationExpériences

Everything is ready to make interoperable product data exchanges in the engineering domain
