LISI/ENSMAÉcole Nationale Supérieure de Mécanique et

d’Aérotechnique1, avenue Clément Ader - BP 40109 - 86961 Futuroscope cedex - France

PLib ontologies(ISO 13584 / IEC 61360):

Where are we ?

Guy Pierrapierra@ensma.fr

20602_09g

Content

• Standardization

• Tools availability

• Who use PLIB?

• Conclusion: Vision for the future

30602_09g

What is PLib?

I - A model for dictionnary / product ontology:Characterization of an object = 1 class

+ a set of property values

Multilingual : Class and properties = 1 language independent identifier+ a set of translatable attributes

II - A Model for librairies / catalogues:Objects are:

- gathered into classes,- described by properties values, and possibly - associated with representations (e. g., geometry)

III - Domain ontologiesFor each particular technical domain (e. g., electronic components, fasteners,...), PLib ontologies need to be defined.

40602_09g

• Defining multilingual Product semantics:1 - Parts are structured as a specialization hierarchy:washer / lock washer / lock washer internal teeths

• Catalogues may be queried at various levels of details

2 - Properties may be shared across ontologies

• decentralized view of ontology development with parallel work and shared responsabilities

• Defining corporate component database3 - Each company may choose its own hierarchy, select standard properties, and add its own properties

• Independence of database with automatic information exchange and integration

• Electronic commerce4 - Standard ontologies provide multilingual product semantics

• automatic processing of electronic commerce and B2B transactions

5 - The library model contains all catalogue information

• automatic generation of active and multilingual electronic catalogues

Advantages of the PLib model

50602_09g

PLib Status?

• All the standard documents are now International standards – Model of ontology jointly published ISO and IEC from 1998 to

2004– A total of 12 international standards

• Product ontologies developped as International standards– electronic components IEC 61360-4 – process instruments IEC 61360-4 – Fasteners ISO 13584-511– measuring instruments ISO 13584-501– machining tools ISO 13399– bearings ISO 23768– mechanics ISO/TC 10 NWI– optics and photonics ISO/TC 172 NWI

60602_09g

New developments

• ISO / IEC– A guide is under ballot for using PLib in all ISO and IEC TC

• ISO TC184/SC4/WG2– XML schemas for PLIB exchange (OntoML) have been distributed for

review– An improved version of the ontology model has been balloted

• Cooperation is initiated with UN/CEFACT for ebXML EDI (CEN/ISSS cCAT)

• An international consortium has been set up :OIDDI: Open and Interoperable Domain Dictionary Initiative

• to promote the emergence of compatible and complementary ontologies

• to ensure orthogonality between dictionaries and business processes

– Participants: RosettaNet,ECALS/JEITA, UNSPSC, eCl@ss, IEC SC3D, ISO PLIB

• Status: Pending a proposal for a CEN/ISSS Workshop has been submitted

• National Standards: Japan, France, Germany...

70602_09g

Content

• Standardization

• Tools availability– free suite for standard ontology development (LISI/ENSMA, Fr)

– Mediator system for ontology mapping (Semaino, De)

– Online dictionary / catalogue server(Paradine, At)

+ Large size component DBMS (Toshiba Corp., Jap)

+ free browser/publisher (CNIS, CN), eCommerce server (Komerko,Fr)...

• Who use PLIB?

• Vision for the future

80602_09g

1/3 PLIB Tool setLISI/ENSMA + CRCFA0

• An API reading / writing PLIB files

• An editor for creating / updating PLIB compliant ontologies

• A browser for publishing dictionary data

• PLIB full checking

• Transient data

• Available on the Web!

PLIB API(Java)

PLIB Editor User interface

APIs

API Ecco(Java)

ECCO Toolkit

Data

P21PLIB

physical file

P21PLIB

physical file

Global architecture

90602_09g

2/3 PLIB Editor

Ontology Editor

Instance (product data) management

Class selectionfor exportation

100602_09g

3/3 PLIB Browser

PLIB Browser Generator

PLIB Browser

P21PLIB

physical file

110602_09g

Some other research projects:Ontology-based database

(OBDB)

Ontology Instances

DBMSDictionary

Ontology Meta Schema

EXPRESS to SQL

Mapping

PLIBEXPRESS

data model

EXPRESSmodel ofEXPRESS

EXPRESS to Java

Mapping

Ontology to SQL

Mapping

PLIB Editor

PLIB API(Java)

Data API(Java)

DataExchange

P21PLIB

physical file

OntoML

User interface

APIs

Database

• An ontology-based database management system

• Persistent data (PostGRES)

• Importation / exportation

• ...

120602_09g

OntoDB 2/2

PLIB Editor-likefront end

Extraction tools

Ontology management

130602_09g

Query language for PLIB and OBDB OntoQL

SELECT Reference, Configuration,

Weight, Color, Length

FROM "Beach Paddles"

WHERE Color = ‘vert’ or Reference like ‘%3’ or Color = ‘jaune’

SELECT #code, # version, #preferred_name, …

FROM #CLASS

WHERE #name[en]=‘Beach Paddles’

SELECT #name[en]

FROM #CLASS

• A language for creating / updating / querying ontology and ontology based data

140602_09g

OntoWeb 1/2

• Generic Web interface for accessing ontology-based databases

• Global architecture:

HTTP Server(Apache)

Application Server(Tomcat)

DBMS Server(PostGRES)

DBMS Server(SQL Server)

OntoDB FlatLIB

HTTP Request HTTP Response

Controller (Servlets)

View (JSPs)

Application Layer(Java Beans, Action classes)

Business Objects - OntoAPI(Java API)

Mapping Layer(Hibernate)

Query Layer

(OntoQL)

150602_09g

OntoWeb 2/2

Ontology Editor

Class extension management(creation, extraction, …)

Query interface

160602_09g

Software Tool Mediator

• Mapping of catalogue data of companies to– Standard dictionaries– Dictionaries of other companies /

marketplaces

EXCEL

BMEcat

eClass

ETIM

ProfiClass

SAP

PDM

Mediator

170602_09g

Basic functionality of the Mediator

Supplier Customer

Dictionary mapping

Customer Cat.

Catalogue Transformation

Supplier Cat.

180602_09g

Class mappings

• Class mappings specify in which class of the target dictionary products will be put

• 1:1

• N:1 1:N mappings

190602_09g

Property Mappings

• Property mappings determine the value which is given to a property in generated e-catalogue

• 1:1 and 1:n mappings– The value of the target property is taken from

the related source property– One source property may be mapped to several

target properties

• Transformation functions– Predefined functions– User defined functions (Syntax taken from SQL)

200602_09g

Application Scenario

viaMEDICI EPIM

ExportMEDIATOR

Marketing data / Prices

Technical information

Data merge

Semaino Technologies GmbH Dipl.-Inf. Jens Bröking

http://www.semaino.de Dr. Wolfgang Wilkes

210602_09g

eptos™ – Paradine Online Dictionary

• Online Dictionary to develop and maintain Classification Systems and Property Dictionaries

• Offered as Product or ASP Service• Data model according to ISO 13584 /

IEC 61360• Online workflow for standardization of

properties and classes• Some customers: ISO, DIN, eCl@ss,...

220602_09g

Cross Industry Online Dictionary

for product describing properties

(www.DINsml.net)

Standardization process

according to DIN 820

more then 6500 properties and classes

in standardization process

Example: DIN Online Dictionary

Register online forread only access !

(free of charge)

230602_09g

capra™ – Paradine Corporate Dictionary

• Online Dictionary to take over and adapt Classification Systems / Property Dictionariesas well as developing own Dictionaries

• Offered as Product or ASP Service• Data model according to ISO 13584 / IEC

61360• Valuation and Exchange of Products

(Import/Export)• Some customers: PROLIST, Zeiss, ...

240602_09g

Target customers/users

• Target Customers– Companies and

Corporate Groups– Catalog developers– Industry organizations

• Target Users– Standardization department – to take over and adapt

classification systems and properties– Catalog and Classification developer – to search,

download and use content

www.paradine.at

250602_09g

Content

• Standardization

• Tools availability

• Who use PLIB?– Japan, China, Germany,

Austria,

– The French case...

• Conclusion: Vision for the future

Description ofNon Production Materials

A joint project

Application to:gerard.chaumond@renault.com

jacques.bardot@mpsa.com

bernard.jeanneau@tixis.arcelor.com

WhoWho useuse PLib:ThePLib:The FrenchFrench casecase

What are NPM? all materials that do not enter in company products

Functioning-equipments of individual protection- office consumables- computer consumables - products of cleaning-...

Specific goods from the suppliers of capital goods - chucks- reducers- welding tools- robots , …

Specific goods for the group- gripper devices- part holders-part locators tightenings,..- control toolings

Structure and maintenance- articles of nomenclature -structure body,…- spare parts : - components (detectors, distribut.,..) - subsets (controler, variator,...)

Process- electrodes- cutting tools- tips of screwing- buzzards of painting - brushes, abrasives,..

Commercial goods from catalogs-detectors, actuators, electrical motors,..- electronic command cards- data processing components- cutting tools, …

280602_09g

Référentiel RenaultR 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

Supplier

classification catalogue : Composants d’automatisme et de process -> section 42 : horloges et minuteries,…

04702 387-0442

Market place

387-0442 04702

Manufacturer

04702

classification catalogue :Tableau de distribution onglet protection commande

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

Référentiel PSA Peugeot Citroën

Every party enter again and again all or part of the same information: costs of reentering and risks of errors.

Current situation : example for a timer

290602_09g

Prescriptions

• Codification– Need : To have a unique international interoperable standardised code. Will replace corporate

reference in all exchanges– Decided solution : All suppliers must provide a ISO/IEC 15459-3 code (e. g., EAN,

ODETTE, EDIFICE, …) codifications are compliant (Currently only 45% of the 100 first manufacturers)

• Characterization– Need : To have an homogeneous description of all items in the same class.– Decided solution : All supplier must provide data and catalogues in files conforming with

ISO 13584 PLib, and according to the NPM shared ontology

• Classification– Need : To group similar products in the same group– Decided solution : All supplier must reference an existing recognised international

classification: eCl@ss

300602_09g

Estimated savings

• For PSA and RENAULT :– Information capture and updating of data :

• suppression of internal keying-in in each Group – reliability, richness, transparency, consistent information :

• reduction of the number of administrative claims, e.g. procurement, accountancy, warehouse, …

• reduction of the maintenance costs or of production loss, e.g. stops, breakdowns, …

Globally : over 3 Million Euros of yearly savings each Group– 35% from information capture/update, – 20% from claims, – 45%st from production losses

• For all other actors : no figures, but : – Reduction of claims

– Cost of transcodification/translation of catalogues (formats and contents)

310602_09g

Three level structure of the project

• The NPM consortium activity (Michelin, Alcan, Galia, Saint Gobain, Schneider, Air liquide…)

• Continue development of a shared NPM ontology• Develop a French standard on the previous prescriptions

• PSA and Renault’s common project• Adoption of the 3 concepts• replace each Company’s tools (as old as 25 years) and migrate to a PLIB -

based storage structure

• The LMPR Renault pre-project LMPR = List of Renault prescribed parts– Size of the project:

– 4000 articles, 145 manufacturers, 211 classes– Documention package linked to each family, sometimes to each article

– Time schedule of the project– PLIBEditor deployed in the 145 manufacturers June 2005– Integrated catalogue circulated to integrator by December 2005

320602_09g

Renault’s LMPR project result

330602_09g

Conclusion:Vision for the next 5 years

• Over the next 5 years, all global players will have changed– their current item databases (with same attributes for all products) – for PLib-like databases (Structured classes with specific properties).

• Over the next 5 years, all global players will have changed their requirements about product information:– product = product + characterization data – full electronic exchange not only for e-commerce (commercial data) but

also for engineering (technical data)• integration of engineering and procurement

• PLIB is just in time:– the technology is mature– the technology is good– New competitors emerge– just to hurry up to promoting it and establishing it in Europa, in

Asia…and elsewhere