Presentation is loading. Please wait.

Presentation is loading. Please wait.

 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.

Similar presentations


Presentation on theme: " 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."— Presentation transcript:

1  MEDI 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 FUTUROSCOPE cedex     Eric Sardet – Technical manager Development and use of ontologies in the engineering domain Téléport avenue René Cassin FUTUROSCOPE Cedex FRANCE  +33 (0)  +33 (0)

2 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 LIAS/ENSMA - Futuroscope - 5 Octobre / 49

3 Exchange of technical information: PAST and PRESENT situation : paper document Design Purchase Sales R&D Process control Plant Maintenance DB Equipment manag t Paper Catalogues requirements request FAX Product data Catalogue choice offer FAX Product data documentation MEDI LIAS/ENSMA - Futuroscope - 5 Octobre / 49

4 Sales R&D Plant Web (Internet) Maintenance DB Equipment manag t Product database Process control CAE n manufacturers Purchase Contractual framework Order CLIENTSUPPLIER Exchange of technical information: the FUTURE … Request (Require t ) Request (Require t ) documentation Offer (Product data) New products Consultation / criteria Objective of ontologies: Computerizing an existing technical know-how MEDI LIAS/ENSMA - Futuroscope - 5 Octobre / 49

5 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 MEDI LIAS/ENSMA - Futuroscope - 5 Octobre / 49

6 Ontologies in technical domains: specific needs Needs Language Process Integration Experiences MEDI LIAS/ENSMA - Futuroscope - 5 Octobre / 49

7 Industrial problematic  To have at one’s disposal:  The right data  In the right place  At the right moment  In the right format... Needs Language Process Integration Experiences Strong user requirement: Getting pertinent information on components  Whereas everything aims at:  information system heterogeneity,  data model incompatibilities,  data obsolescence risk. MEDI LIAS/ENSMA - Futuroscope - 5 Octobre / 49

8 Needs Language Process Integration Experiences Units of measure  D, B, d: expressed in millimetre ? millimeter ? mm ?  Needs to explicitly define units of measure  More generally: make explicit technical information MEDI LIAS/ENSMA - Futuroscope - 5 Octobre / 49

9 Needs Language Process Integration Experiences Nature of properties Characteristics d: internal diameter D: external diameter B: width N min : … N max : … Conditions of use n: rotation speed F rad : radial load F ax : axial load Behavior L 10h : life length Depends on MEDI LIAS/ENSMA - Futuroscope - 5 Octobre / 49

10 Different point of views on the same product Needs Language Process Integration Experiences Ball bearing 2D – Representation Schematic representation Calculus Simplified 3D representation... MEDI LIAS/ENSMA - Futuroscope - 5 Octobre / 49

11 Derivation functions Needs Language Process Integration Experiences dDBC dyn C 0 n kin n therm weight mm mm mm kN kN 1/s 1/s kg Characteristics F rad F ax n kN kN 1/s Conditions of use L 10h 10 6 n Behavior e = 0.22 If F ax /F rad <= e Then P = F rad If F ax /F rad > e Then X = 0.56 and Y = 2 and P = X*F rad + Y*F ax L 10h = / (60 * n) * (C dyn / P)^3 Derivation functions 856 MEDI LIAS/ENSMA - Futuroscope - 5 Octobre / 49

12 Heterogeneity, incomplete descriptions Needs Language Process Integration Experiences Manufacturer Supplier Distributor Re-capture  Problems:  Data capture errors  Multilingualism ?  Maintenance: initial requirements representation ?  Bill of material based data: database queries ?  Integration: exchange automation ?  … Re-capture User CodeDesignation AAA BBB … Timer Bearing … Product MEDI LIAS/ENSMA - Futuroscope - 5 Octobre / 49

13 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, …) identification o For information structuration o For object characterization  An interoperable framework allowing data exchanges between business partners Needs Language Process Integration Experiences MEDI LIAS/ENSMA - Futuroscope - 5 Octobre / 49

14 An ontology formalization language Needs Language Process Integration Experiences MEDI LIAS/ENSMA - Futuroscope - 5 Octobre / 49

15 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 Needs Language Process Integration Experiences MEDI LIAS/ENSMA - Futuroscope - 5 Octobre / 49

16 ISO – Parts Library (PLIB) Needs Language Process Integration Experiences Supplier Properties Classes diameter, height,... Information responsible Parts suppliers, standards,... definescharacterized by Ontology / dictionary Documents resources Value domains Value domains valuées dans A set of instances BDD / Catalogue Data exchange System ASystem B Supplier Side User Side 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 of representations MEDI LIAS/ENSMA - Futuroscope - 5 Octobre / 49

17 Property typology Needs Language Process Integration Experiences  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, … MEDI LIAS/ENSMA - Futuroscope - 5 Octobre / 49

18 Needs Language Process Integration Experiences Property description example 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 MEDI LIAS/ENSMA - Futuroscope - 5 Octobre / 49

19 Class typology Needs Language Process Integration Experiences  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 MEDI LIAS/ENSMA - Futuroscope - 5 Octobre / 49

20 Needs Language Process Integration Experiences Class description example 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 MEDI LIAS/ENSMA - Futuroscope - 5 Octobre / 49

21 Semantic relationships between classes Needs Language Process Integration Experiences Standard bearing Bearing is_case_of(d) d D Communautary ontology Private ontology  is_case_of relationship  subsumption relationship between characterization classes without inheritance, with explicit importation of properties Geometric Model is_view_of Ball Bearing D Geometric view view_spec  is_view_of relationship  Relationship between a characterization class and a class representing a business model Bearing Ball Bearing is_a P  is_a relationship  subsumption relationship between characterization classes MEDI LIAS/ENSMA - Futuroscope - 5 Octobre / 49

22 Concept identification IRDI Needs Language Process Integration Experiences MEDI LIAS/ENSMA - Futuroscope - 5 Octobre / 49

23 Domain ontology example: electronic domain Needs Language Process Integration Experiences MEDI LIAS/ENSMA - Futuroscope - 5 Octobre / 49

24 Needs Language Process Integration Experiences Domain ontology example: measuring instruments MEDI LIAS/ENSMA - Futuroscope - 5 Octobre / 49

25  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 Needs Language Process Integration Experiences MEDI LIAS/ENSMA - Futuroscope - 5 Octobre / 49

26 PLIB Exchange format ISO IS : OntoML  XML format (XML Schema) for the exchange of all or part of ontologies (identification: based on ISO )  XML format (XML Schema) for the exchange of all or part of product catalogues (includes ISO )  Recommendations:  Using this format in any engineering project for exchanging ontologies and/or ontological data  Will provide for: o data consistency o compatibility of developed applications Needs Language Process Integration Experiences MEDI LIAS/ENSMA - Futuroscope - 5 Octobre / 49

27 Development process of ontologies in the engineering domain Needs Language Process Integration Experiences MEDI LIAS/ENSMA - Futuroscope - 5 Octobre / 49

28 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 Needs Language Process Integration Experiences MEDI LIAS/ENSMA - Futuroscope - 5 Octobre / 49

29 Class / properties relationships  Fundamental hypothesis  The class hierarchy and the properties shall be defined all together o applicable properties underline the class meaning o property application domain underlines the meaning of each property parts SKF_parts CLASSES PROPERTIES 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 » modeling A class shall be added iff it is a new domain for a property Needs Language Process Integration Experiences MEDI LIAS/ENSMA - Futuroscope - 5 Octobre / 49

30 Local ontologies Vs 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 Local properties part number life cycle... Needs Language Process Integration Experiences MEDI LIAS/ENSMA - Futuroscope - 5 Octobre / 49

31 Domain ontologies: Some metrics  Mechanical fastener ontology (ISO , 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  classification, multi-sector, Germany (www.eclass-online.com)  Multilingual (  15)   classes  More and more properties … Needs Language Process Integration Experiences MEDI LIAS/ENSMA - Futuroscope - 5 Octobre / 49

32  ElectronicsIEC  Process instruments IEC  Mechanical fastenersISO  Measure instrumentsISO  Cutting toolsISO  BearingsISO  Technical product documentationISO/TC 10 NWI  Optics and photonicsISO  … Standardized domain ontologies Needs Language Process Integration Experiences MEDI LIAS/ENSMA - Futuroscope - 5 Octobre / 49

33 Domain ontologies for database integration in an engineering context Needs Language Process Integration Experiences MEDI LIAS/ENSMA - Futuroscope - 5 Octobre / 49

34 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 ) Needs Language Process Integration Experiences MEDI LIAS/ENSMA - Futuroscope - 5 Octobre / 49

35 Seller scenario Parts supplier Ontology delivery + eCatalogue (OntoML) Ontology delivery + eCatalogue Users Local ontology Global ontology or standard Subscription Reference Response Request mappings repository extractions Needs Language Process Integration Experiences MEDI LIAS/ENSMA - Futuroscope - 5 Octobre / 49

36 Buyer scenario Buyer Supplier Local ontology Local ontology Local ontology mappings Global ontology or standard Subscription Standard exchanges Response Request Needs Language Process Integration Experiences MEDI LIAS/ENSMA - Futuroscope - 5 Octobre / 49

37  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 Needs Language Process Integration Experiences MEDI LIAS/ENSMA - Futuroscope - 5 Octobre / 49

38 Product description interoperability Process control CAE Bearing- ID = #01-ROUL#1 d: float, in mm ID = #02-DIN#1 D: float, in mm ID = #02-DOUT#1 B: float, in mm ID = #02-WIDTH#1 Class level  Independence according to the ontology description model  Needs to resolve instance references ISO TS – 10: product descriptions Mapping Sales Local ontology Global ontology class_ref = #01-ROUL# #02-DIN#1 = #02-DOUT#1 = #02-WIDTH#1 = 7.0 Instance of Instance level Needs Language Process Integration Experiences MEDI LIAS/ENSMA - Futuroscope - 5 Octobre / 49

39 Ontology models interoperability class_ref = #01-BEARL# #02-DIN#1 = #02-DOUT#1 = #02-WIDTH#1 = 7.0 …. Product catalogue Terminological Server Bearing- ID = #01-BEAR#1 d: float, in mm ID = #02-DIN#1 D: float, in mm ID = #02-DOUT#1 B: float, in mm ID = #02-WIDTH#1 getType( #01-ROUL#1) getName( #01-ROUL#1) … ISO TS – 6: terminology loading CAE #01-ROUL# #02-DIN# #02-DOUT# CLASS Bearing … CAE Rolling Bearing d (mm)D(mm)B(mm) Needs Language Process Integration Experiences MEDI LIAS/ENSMA - Futuroscope - 5 Octobre / 49

40 Reference interpretations from ontologies Process control Local ontology Mapping getOntology( #01-BEAR#1, ONTOML)… class_ref = #01-BEAR# #02-DIN#1 = #02-DOUT#1 = #02-WIDTH#1 = 7.0 Product catalogue loading CAE Rolling bearing d (mm)D(mm)B(mm) Ontological server All or part Of the global ontology or standard … ISO – 32 OntoML Needs Language Process Integration Experiences MEDI LIAS/ENSMA - Futuroscope - 5 Octobre / 49

41 An interoperability framework for technical data integration Clients Localization service Terminological services (http:// ) Ontological services (http:// ) _511_1#01-P511AAA159#001 Terminological server=http:// Ontological server=http:// getSourceIdentification(" _511_1#01-P511AAA159#001") lookupConcept(" _511_1#01-P511AAA159#001") 3 getConcept(name=« square head screw"; Definition="…. ",..) 4 5 getConceptModel (" _511_1#01-P511AAA159#001", representation="OntoML", super=false, sub=false, depth=1, langue="fr " ) 6 OntoML file (ISO TS identifier) ISO : Web Services Needs Language Process Integration Experiences MEDI LIAS/ENSMA - Futuroscope - 5 Octobre / 49

42 Catalogues interrogation Supplier Local ontology mappings Supplier Local ontology mappings ISO : Queries on product data Clients I need a bearing:  D > 45  B < 12 Global ontology or standard * Generation Projection Query class_ref = #01-BEAR# #02-DIN#1 = #02-DOUT#1 = #02-WIDTH#1 = 7.0 Response Needs Language Process Integration Experiences MEDI LIAS/ENSMA - Futuroscope - 5 Octobre / 49

43 Some industrial experiences Needs Language Process Integration Experiences MEDI LIAS/ENSMA - Futuroscope - 5 Octobre / 49

44 Renault, Peugeot - Citroën PHF (1/2)  PHF = Non production material  Identified problems:  1 product => n identifications  Flat product description => designation  No structuration  Re-capture => errors Manufacturer Re-capture Distributeur Retailer Re-capture Renault repository Z : 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 : / FAMILLE DA : T80 SECT.ACHAT : 88 UNITE GESTION : UN PSA Peugeot Citroën repository Needs Language Process Integration Experiences MEDI LIAS/ENSMA - Futuroscope - 5 Octobre / 49

45 Renault: PHF (2/2)  Codification  Chosen solution : ISO/IEC 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 :  Results:  Cost reduction: 3 Millions Euros / year for each group  35 % capture/ data update  20 % claiming  45 % maintenance Needs Language Process Integration Experiences MEDI LIAS/ENSMA - Futuroscope - 5 Octobre / 49

46 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 Needs Language Process Integration Experiences MEDI LIAS/ENSMA - Futuroscope - 5 Octobre / 49

47 Other successful stories …  Toshiba Corporation  Philips  Siemens  DIN: property server (DINsml.net)  multi-sector classification (www.eclass-online.com)www.eclass-online.com  Zeiss (metrology, medical optic)  Sandvick (cutting tools) ... Needs Language Process Integration Experiences MEDI LIAS/ENSMA - Futuroscope - 5 Octobre / 49

48 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 Needs Language Process Integration Experiences MEDI LIAS/ENSMA - Futuroscope - 5 Octobre / 49

49 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 Besoins Langage Processus Intégration Expériences Everything is ready to make interoperable product data exchanges in the engineering domain MEDI LIAS/ENSMA - Futuroscope - 5 Octobre / 49


Download ppt " 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."

Similar presentations


Ads by Google