1 / 49

26/09/2014

Téléport 2 - 15 avenue René Cassin 86 961 FUTUROSCOPE Cedex FRANCE ( +33 (0)5 35 54 23 91 - 2 +33 (0)5 35 54 24 33. ENSMA , BP 40109, Téléport 2, 1 avenue Clément Ader 86 961 FUTUROSCOPE cedex ( 05 49 49 80 78 - 2 05 49 49 80 64 . crcfao@ensma.fr : http://www.ensma.fr/crcfao.

stesha
Download Presentation

26/09/2014

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Téléport 2 - 15 avenue René Cassin 86 961 FUTUROSCOPE Cedex FRANCE (+33 (0)5 35 54 23 91- 2+33 (0)5 35 54 24 33 ENSMA , BP 40109, Téléport 2, 1 avenue Clément Ader 86 961 FUTUROSCOPE cedex (05 49 49 80 78 - 205 49 49 80 64 . crcfao@ensma.fr :http://www.ensma.fr/crcfao Development and use of ontologies in the engineering domain Eric Sardet – Technical manager sardet@critt-informatique.fr 26/09/2014 INTERCRITTs 1 MEDI 2012 - LIAS/ENSMA - Futuroscope - 5 Octobre 2012

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

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

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

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

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

  7. 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 Industrial problematic • Whereas everything aims at: • information system heterogeneity, • data model incompatibilities, • data obsolescence risk. Strong user requirement: Getting pertinent information on components MEDI 2012 - LIAS/ENSMA - Futuroscope - 5 Octobre 2012

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

  9. Conditions of use • n: rotation speed • Frad : radial load • Fax : axial load Characteristics • d: internal diameter • D: external diameter • B: width • Nmin: … • Nmax: … Depends on Behavior • L 10h : life length Needs Language Process Integration Experiences Nature of properties MEDI 2012 - LIAS/ENSMA - Futuroscope - 5 Octobre 2012

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

  11. Characteristics 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 Conditions of use Frad Fax n Derivation functions kN kN 1/s 50 2.5 980 e = 0.22 If 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 Behavior L10h 106 n 856 Needs Language Process Integration Experiences Derivation functions MEDI 2012 - LIAS/ENSMA - Futuroscope - 5 Octobre 2012

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

  13. Needs: Accurate characterisation of objects Structuration of objects in classes Identification of concepts for referencing purposes Identificationof objects Multi-representation of objects Harmonization / automation of exchanges … Solution: Domain ontologies For concept (classes, properties, …) identification For information structuration For object characterization An interoperable framework allowing data exchanges between business partners Needs Language Process Integration Experiences Summary … MEDI 2012 - LIAS/ENSMA - Futuroscope - 5 Octobre 2012

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

  15. 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 Needs Language Process Integration Experiences Domain ontologies in ingeneering  Domain ontologies describe concepts of a given domain MEDI 2012 - LIAS/ENSMA - Futuroscope - 5 Octobre 2012

  16. Value domains Ontology / dictionary diameter, height,... Information responsible Parts suppliers, standards, ... valuées dans Supplier Classes Properties defines characterized by Documents resources A set of instances Géométrie 2D BDD / Catalogue A set of representations System A System B Supplier Side User Side Data exchange XML (or EXPRESS) Needs Language Process Integration Experiences ISO 13584 – Parts Library(PLIB) • PLIB is a data model for the definition / exchange of (canonical) domain ontologies and of catalogue of products MEDI 2012 - LIAS/ENSMA - Futuroscope - 5 Octobre 2012

  17. 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): • Preferred name, short name, synonymous, symbols, images, ... • For typing purposes: • Class, integer, real measure, code, … Needs Language Process Integration Experiences Property typology MEDI 2012 - LIAS/ENSMA - Futuroscope - 5 Octobre 2012

  18. Needs Language Process Integration Experiences Property descriptionexample Document view Acronyms • 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 MEDI 2012 - LIAS/ENSMA - Futuroscope - 5 Octobre 2012

  19. 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): • Preferred name, short name, synonymous, symbols, images, ... • Descriptive properties • relationships between classes Needs Language Process Integration Experiences Class typology MEDI 2012 - LIAS/ENSMA - Futuroscope - 5 Octobre 2012

  20. Needs Language Process Integration Experiences Class descriptionexample Document Acronyms • 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 MEDI 2012 - LIAS/ENSMA - Futuroscope - 5 Octobre 2012

  21. P • is_arelationship • subsumptionrelationshipbetween characterization classes Bearing is_a Ball Bearing d • is_case_ofrelationship • subsumptionrelationship between characterization classes without inheritance,with explicit importation of properties Standard bearing Communautary ontology D is_case_of(d) Private ontology Bearing • is_view_ofrelationship • Relationship between a characterization class and a class representing a business model D Ball Bearing is_view_of Geometric Model Geometric view view_spec Needs Language Process Integration Experiences Semantic relationshipsbetween classes MEDI 2012 - LIAS/ENSMA - Futuroscope - 5 Octobre 2012

  22. Needs Language Process Integration Experiences Concept identificationIRDI MEDI 2012 - LIAS/ENSMA - Futuroscope - 5 Octobre 2012

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

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

  25. Two approaches: Implicit representation (intentional) Based on property roles (selectable, computed, contextual), value domains, calculation functions, filters, … Expression of the selection process Description factorization Complex description Complex implementation Instances Class IRDI • Explicit representation (extensional) • 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 Property IRDI Propertyvalue Property IRDI Propertyvalue ………………………….. Needs Language Process Integration Experiences Instance representation MEDI 2012 - LIAS/ENSMA - Futuroscope - 5 Octobre 2012

  26. 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) Needs Language Process Integration Experiences PLIB Exchange formatISO IS 13584-32: OntoML • Recommendations: • Using this format in any engineering project for exchangingontologies and/or ontological data • Will provide for: • dataconsistency • compatibilityof developed applications MEDI 2012 - LIAS/ENSMA - Futuroscope - 5 Octobre 2012

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

  28. 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 Initial status MEDI 2012 - LIAS/ENSMA - Futuroscope - 5 Octobre 2012

  29. Fundamental hypothesis The class hierarchy and the properties shall be defined all together applicable properties underline the class meaning property application domain underlines the meaning of each property CLASSES PROPERTIES • parts • Mass • SKF_ref • SKF_parts • inner_diameter • SKF_double_ • SKF_single_ • ball_bearings • ball_bearings • .... Needs Language Process Integration Experiences Class / propertiesrelationships • 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 MEDI 2012 - LIAS/ENSMA - Futuroscope - 5 Octobre 2012

  30. Particular articulation relationship: is-case-of Semantic of subsumption without inheritance The local ontology explicitly import required properties Local properties part number life cycle ... case-of case-of case-of case-of case-of case-of Needs Language Process Integration Experiences Local ontologiesVscommunautary (global) ontologies • Hierarchies of communautaryontologies may be unadapted according to the user requirements • Required properties may not exist • Needs to “customize" ontologies: 1 global ontology / N local ontologies MEDI 2012 - LIAS/ENSMA - Futuroscope - 5 Octobre 2012

  31. 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 … Needs Language Process Integration Experiences Domain ontologies:Some metrics MEDI 2012 - LIAS/ENSMA - Futuroscope - 5 Octobre 2012

  32. Needs Language Process Integration Experiences Standardizeddomain ontologies • 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 • … MEDI 2012 - LIAS/ENSMA - Futuroscope - 5 Octobre 2012

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

  34. Local (proprietary) domain ontologies : Immediately usable, standard formats, standardtools Integration by « mappings » (a posteriori mapping ) Global (communautary) domain ontologies : Full and automatic integration, multi-supplier search Completeness / needs, evolution Needs Language Process Integration Experiences Ontologies and data integration • 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 ) MEDI 2012 - LIAS/ENSMA - Futuroscope - 5 Octobre 2012

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

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

  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 For ontology information retrieving For catalogue information retrieving For all or part ontology / catalogue exchanges Needs Language Process Integration Experiences Contributing to the interoperability of systems MEDI 2012 - LIAS/ENSMA - Futuroscope - 5 Octobre 2012

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

  39. Product catalogue Rolling Bearing d (mm) D(mm) B(mm) 13.0 24.0 7.0 class_ref = 0001-1234#01-BEARL#1 loading CAE 0001-1234#02-DIN#1 = 13.0 0001-1234#02-DOUT#1 = 24.0 0001-1234#02-WIDTH#1 = 7.0 …. getType(0001-1234#01-ROUL#1) getName(0001-1234#01-ROUL#1) … Terminological Server <type>CLASS</type> <name lg="e"> Bearing </name> … Bearing- ID = 0001-1234#01-BEAR#1 d: float, in mm ID = 0001-1234#02-DIN#1 D: float, in mm ID = 0001-1234#02-DOUT#1 B: float, in mm ID = 0001-1234#02-WIDTH#1 0001-1234#01-ROUL#1 0001-1234#02-DIN#1 0001-1234#02-DOUT#1 13.0 24.0 CAE Needs Language Process Integration Experiences Ontology modelsinteroperability ISO TS 29002 – 6: terminology MEDI 2012 - LIAS/ENSMA - Futuroscope - 5 Octobre 2012

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

  41. Localization service getSourceIdentification("0112-1---13584_511_1#01-P511AAA159#001") Terminological server=http://194.55.163.1 Ontological server=http:// 194.55.163.2 3 lookupConcept("0112-1---13584_511_1#01-P511AAA159#001") Terminological services (http://194.55.163.1) 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") 1 2 OntoML file 6 Ontological services (http://194.55.163.2) Needs Language Process Integration Experiences An interoperability frameworkfor technical data integration (ISO TS 29002-5 identifier) Clients 0112-1---13584_511_1#01-P511AAA159#001 ISO 29002-20: Web Services MEDI 2012 - LIAS/ENSMA - Futuroscope - 5 Octobre 2012

  42. Clients class_ref = 0001-1234#01-BEAR#1 Supplier Global ontology or standard 0001-1234#02-DIN#1 = 13.0 0001-1234#02-DOUT#1 = 24.0 0001-1234#02-WIDTH#1 = 7.0 Local ontology mappings I need a bearing: • D > 45 • B < 12 Response Response Projection Query Generation <request> <select>*</select> <from class="0001-1234#01-BEAR#1"/> <where> <and> <sup prop="0001-1234#02-DOUT#1">45</sup> <infprop="0001-1234#02-WIDTH#1">12</sup> </and> </request> Supplier Local ontology Query mappings Needs Language Process Integration Experiences Catalogues interrogation ISO 29002-31: Queries on product data MEDI 2012 - LIAS/ENSMA - Futuroscope - 5 Octobre 2012

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

  44. PHF = Non production material Identified problems: 1 product => n identifications Flat product description => designation No structuration Re-capture => errors Retailer Distributeur Manufacturer Manufacturer Re-capture PSA Peugeot Citroën repository 04702 Z 000 296 170 : 3752 CONTACTEUR & CONTACTEUR INVERSEUR I > 10A NOM !INT !TENS BOB. ! CONTACTS ! MINUTERIE ! 16, A! 230VAC !1 "F" !04702 LEGRAND Re-capture CODE AUTORISATION : AUTORISATION GENERALE DANS LE GROUP E PSA : 37521815/ CODE CLASSEMENT FAMILLE DA : T80 SECT. ACHAT : 88 UNITE GESTION : UN Re-capture 04702 387-0442 Renault repository Needs Language Process Integration Experiences Renault, Peugeot - CitroënPHF (1/2) MEDI 2012 - LIAS/ENSMA - Futuroscope - 5 Octobre 2012

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

  46. 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 informationcirculation between exchange partners ? Portals, pear to pear exchanges Needs Language Process Integration Experiences CETIM MEDI 2012 - LIAS/ENSMA - Futuroscope - 5 Octobre 2012

  47. 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) ... Needs Language Process Integration Experiences Other successful stories … MEDI 2012 - LIAS/ENSMA - Futuroscope - 5 Octobre 2012

  48. 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 Conclusion MEDI 2012 - LIAS/ENSMA - Futuroscope - 5 Octobre 2012

  49. 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 What’s about tomorrow? Everything is ready to make interoperable product data exchanges in the engineering domain MEDI 2012 - LIAS/ENSMA - Futuroscope - 5 Octobre 2012

More Related