The use of ISO13584 Parts Library (PLIB) standard in industrial applications: Hiroshi MURAYAMA Hiroshi.murayama@toshiba.co.jp Corporate R&D Center TOSHIBA Corporation, Japan The use of ISO13584 Parts Library (PLIB) standard in industrial applications 9th International Forum on Meta Registry


Presentation outline: Presentation outline ISO TC184/SC4 standards PLIB Standard status PLIB Global ontology PLIB Database structure TOSHIBA’s involvement in PLIB


ISO TC184/SC4 Industrial Data: ISO TC184/SC4 Industrial Data Standards under ISO TC184/SC4 ISO 10303 STEP (Standards for the Exchange of Product data) ISO 13584 PLIB ( Parts Library ) ISO 15926 RDL (Process Plants including Oil and Gas facilities life-cycle data ) ISO 22745 OTD ( Open Technical Dictionary ) ---------------------------------------------------------------------- ISO 15531 MANDATE(MANDATE - Industrial manufacturing management data )   ISO18629 PSL(- Process specification language) --------------------------------------------------------------------- ISO 8000 Industrial Data Quality standards


Slide4: Most of the Parts have already become IS IS: International Std. DIS : Draft ISO Std.


Overview of the structure of PLIB --- Parts: Overview of the structure of PLIB --- Parts Part1 IEC61360 ISO13584 Part24 Part10 Part501 Part20 Part1 Part26 Part42 Part2 Part3 Part4 Part25 Part31 Part101 Part102 Part511 Part5 ＝ ＝ Dictionaries and Maintenance Dictionary Data-model IEC Dictionary Maintenance Method (now superseded by database procedure) Part composition of ISO13584 and IEC61360 standards


Slide6: Registration Authority for environment & laboratory measuring instruments


Slide8: France


ISO/IEC Guide 77 to Support dictionary development: ISO/IEC Guide 77 to Support dictionary development


PLIB new parts under development: PLIB new parts under development


Slide11: PLIB ontology model


Basic concept of class and property in PLIB: Basic concept of class and property in PLIB class class super property property property described by Class BSU property BSU Note: this figure shows a conceptual reference framework, and does not depict actual connection between the entities. name scope Applicable Properties Visible Properties as inverse name; definition; etc. name; definition; data type; unit; etc.


Concept of a property; three sub types exist: Concept of a property; three sub types exist (ABS) property dependent property Non dependent property condition Condition is a property that serves as a condition for another property Depend_on


PLIB modeling layers; dictionary and instances (content): PLIB modeling layers; dictionary and instances (content) DICTIONARY (meta data) INSTANCES (data) Library META MODEL Model (DB schema) for Domain Ontology Transaction Model Messaging ,Transaction, & Query within standard TOSHIBA is developing CQL language (catalogue)


Sample Tree for Vehicle: Sample Tree for Vehicle SELECT * FROM Ecological* ; CQL (Class Query Language)


Ontology as a cascade of reference dictionaries: Ontology as a cascade of reference dictionaries Sensor Electric component Electric motor Motor power Standard reference dictionary DC motor Electric MOTOR AC MOTOR Explosion Proof Consortium dictionary Rated Input Voltage Linear motor TOSHIBA AC motor 3-Phase AC motor TSB Part NO Proprietary dictionary Consortium dictionary Proprietary dictionary Electric Parts Electric motor AC motor DC motor 3phase AC motor …. Linguistic taxonomy, e.g. UNSPSC Import of properties Import of properties IEC 61360-4 ECALS dict.


Over view of the structure of PLIB --- dictionary: Over view of the structure of PLIB --- dictionary Reference dictionary, Consortium dictionary, and Proprietary dictionary have their own strength and weakness Reference dictionary as International Standard Universal agreement on definition (is it really possible?) Speed to effect a change, and to reach a consensus Consortium dictionary Compromise between speed to effect a change and consensuality on definition Proprietary (User) dictionary Quickness to effect a change Desired specificity of definition for particular use


Basic Semantic Unit (BSU), meaning and being: Basic Semantic Unit (BSU), meaning and being --- Why not use name for ID ? Name in a natural language contains unavoidable ambiguity, i.e. depending on the context; life style, history & culture, the signifié ( signified) may be different. Car ? I want a car… I need it, too! I enjoyed it in Kyoto !


Basic Semantic Unit (BSU), meaning and being: Basic Semantic Unit (BSU), meaning and being Class and property identification structure in PLIB Class identification by absolute ID up to70 characters up to14characters Property BSU up to14characters “.” ver. “-” Class BSU “.” ver. “-” Supplier_BSU ver. “-” up to70 characters up to14characters Class BSU “.” ver. “-” Supplier_BSU ver. “-” Property identification by absolute ID NOTE 1: Length shall not include version and separator code length NOTE 2: Version of each code is an integral part of identification NOTE 3: Revision of each code is not an integral part of identification Be aware, supplier_BSU is the identifier of information supplier.


Basic Semantic Unit (BSU), meaning and being: Supplier code consists of ICD + “/” +OI +“///” + Standard_number ICD + “/” +OI “/” (+ OPI ) + “//” + Standard_number Standard_number is constructed as follows (Standard number)_(Part number)_(Edition number) Supplier BSU examples used for dictionary standards IEC 61360-4 is "112/2///61360_4_1“ ISO 13584-501 is “112/1///13584_501_1” Basic Semantic Unit (BSU), meaning and being Supplier identification structure in PLIB For identification of standards, ISO, IEC and ISO/IEC shall be identified according to the organization identification scheme: "ISO Register for Standards Producing Organizations" whose ICD is 112. NOTE: Currently OPI is not usable in PLIB


BSU identification mechanism, for dictionary supplier : BSU identification mechanism, for dictionary supplier Structure of ICD ( International Code Designator) Defined in ISO6523


Class borrowing properties from others --- case of: You need some motor power here. Class borrowing properties from others --- case of Gasoline- powered vehicle Passenger car Automobile Engine capacity No. of passengers class Y Electric component Electric motor Formula-1 Hybrid car Motor power Engine capacity Defined as visible Defined as visible Motor power Imported from motor power Electric component dictionary Automobile dictionary CASE _OF class Engine capacity No. of passengers No. of passengers Engine capacity Engine capacity No. of passengers Applicable property Visible property


Class having components or composite properties: Class having components or composite properties Bus Passenger car Automobile Engine capacity No. of passengers CPU Formula-1 sedan Clock cycle Engine capacity Defined as visible Defined as visible Ref. to Cls_BSU1 Referencing a CPU class as a whole Automobile dictionary Engine capacity No. of passengers No. of passengers Engine capacity Engine capacity No. of passengers Applicable property Visible property CPU type Manu- facturer Electronic parts Cls_BSU1 P_BSU 1 P_BSU 2 P_BSU 3 P_BSU 1:= 2 Ghz P_BSU 2:= Pentium P_BSU 3:= Intel Equipped with Navigation system Electronic parts dictionary ---- class instance type


Principal class attributes --- preferred name: Preferred name If possible, preferred name shall be selected from International Standards in the relevant domain If there are several names for the same product, names other than the one for preferred name may be recorded as synonymous names Up to 70 characters in any language according to ISO10646 In each language, a preferred name may be given for a product ( multi-lingual ), however, set one language as the source lang. Non roman characters such as Japanese, Chinese, Korean letter sets are usable Update is possible with revision up Recommendation Avoid giving the same preferred name to different products in one dictionary Principal class attributes --- preferred name


Slide25: Definition If possible, definition must be found from International Standards in the relevant domain Required to observe ISO10241, if it is for International Standard Start with lower case letters Shall not start with an article, unless there’s a specific reason Shall consist of a single phrase, describing the concept denoted by the preferred name Avoid definition given by a specific school of thought No maximum length on the definition is set in PLIB Length depends on implementation; tools, step-file (ISO10303 -21) parser, pre-processor such as MS-EXCEL®, etc. Update of the definition in source language usually requires version up Observation In many dictionaries, ISO10241 is not observed ! Principal class attributes --- Definition NOTE: ISO10241 “International terminology standard- Preparation and layout”


Principal class attributes --- class BSU: Principal class attributes --- class BSU Class BSU code Code must be unique within one dictionary An identifier without any linguistic meaning suggestive of the name of the product, e.g., P501_C0000001 (ISO13584-501) Encoding of administrative information is allowed enables the global identification of the product concept in combination with the supplier BSU, Some characters are prohibited within the code; “. (period) ”, “- (hyphen) ”, and “ (space) ” are not allowed


Slide27: Note Essential information for the understanding of that definition ( unlimited in length ) e.g. Meaning of a term used in the definition. Remark Any explanatory text for clarification, which does not affect the definition ( unlimited in length ). Short name meaningful abbreviation of the preferred name. Standardized abbreviations are preferred ( Up to 30 characters ). Simplified drawing A drawing including at least the reference coordinate system of the part (that is to be used for all the representations of this part), and the letter symbols of the main applicable properties. Attention You have to decide superclass for the class You have to decide applicable properties for the class Principal class attributes --- some other attributes


Property and principal property attributes: Property and principal property attributes All applicable properties are once defined as visible properties in a class. i.e. it is not a different type, but a status of visible property. Applicable properties in a class are either defined in the class( native ), inherited, or imported from other class Applicable properties only characterize a class Visible properties and Applicable properties Applicable properties Visible properties


Slide29: Visible/Applicable structure allows a subclass which is especially immune from the effect of inherited property When imported visible properties become applicable Property and principal property attributes class 4 class 2 class 1 Property 1 Property 1 Property2 Property 2 class Y class X class Z class 3 class 5 Property 2 Property 1 Property 2 Property 1 Property 3 Property 1 Inherited and changed to applicable Defined as visible Defined as visible Inherited and changed to applicable Inherited and changed to applicable Inherited and kept as visible Property 3 Made applicable as a result of importation Dictionary 2 Dictionary 1 class CASE _OF NOTE: property in red circle means one in applicable state


Slide30: Principal property attributes --- Preferred name Preferred Name If possible, preferred name shall be selected from International Standards in the relevant domain If there are several appellations, names other than the one selected for the preferred name can be recorded as synonymous names Up to 70 characters in any language according to ISO10646 In each language, a preferred name may be given for a product ( multi-lingual ), however, set one language as the source lang. Non-roman characters such as Japanese, Chinese, Korean letter sets are usable Update is possible with revision up


Slide31: Definition (similar to class) Prefer definition available from International Standards in the relevant domain Required to observe ISO10241, if it is for International Standard Unlimited text Update of the definition in source language usually requires version up Note Essential information on any part of the definition, for the understanding of that definition ( unlimited in length ), such as description of measuring method, evaluation method, name of the measuring method, etc. Preferred Letter Symbol often used in place of the short name, in tables, formula, drawings etc... Principal property attributes --- Definition


Slide32: Principal Property attributes --- property BSU Property BSU code Code must be unique within one dictionary An identifier without any linguistic meaning suggestive of the name of the product, e.g., P501_P0000001 (ISO13584-501) Encoding of administrative information is allowed enables the global identification of the product concept in combination with the supplier BSU, Some characters are prohibited within the code; “. (period) ”, “- (hyphen) ”, and “ (space) ” are not allowed


Slide33: Simple type ( Base type ) Boolean type --- True or False String type Number type INTEGER INT_MEASURE --- with unit of measurement REAL REAL MEASURE --- with unit of measurement Complex type Level type Aggregate type LIST type SET type BAG type Array type Class instance type --- reference to other class as a composite property Named type Available data types --- introduction


Available data types --- Level type: Available data types --- Level type Level type (real or integer) 4 values fields, i.e., Minimum(min), Maximum(max), Typical(typ), Nominal(nom) are bundled, Necessarily to select active-value fields for the property Typical is a representative value of the property between min. and max. Nominal is the nominal representation value of the property, often mentioned in catalogues


Slide35: Aggregate type ( of any base type) LIST, SET, BAG, and ARRAY types are available LIST has an order among member elements SET has no order among member elements BAG may have the same member twice, or more. Nesting upto 2 levels or less recommended, for practical compatibility among tools Available data types--- Aggregate type


Slide36: Enumeration types( non-quantitative Int / Code type ) Selectable from predefined list of values, thus convenient to user for definition of value, and querying for a value Meaning may be explained in multiple languages Available data types--- Enumeration type


Unit of measurement : Unit of measurement Both SI units and non SI units(International System of Units) are usable SI Units are selectable or constructible from the predefined list The unit is represented as specified in ISO 10303-41 using, if required, the extensions specified in the common dictionary schema. A mathematical string may be provided in a text representation or it may also be accompanied with a SGML representation.


Some practical rules for PLIB classification: Some practical rules for PLIB classification Avoid creating a class without a property. When create a new class, there must be at least one property by which the class is distinguished from other classes. Set definition of property, data type, (and unit) as early as possible. For similar properties will come up soon, and get confused without proper definition, data type (and unit) ( may be modified later ) Avoid too many string type properties in a class Factorize property to the upper most class Make best use of existing dictionaries and their properties Make best use of language dictionary & encyclopedia in a book form and on the web Keep level of classification shallow as possible


Toshiba’s involvement in PLIB: Toshiba’s involvement in PLIB


Parceling format has been tested through the use in TOSHIBA applications and ISO13584-501 RA tools: Parceling format has been tested through the use in TOSHIBA applications and ISO13584-501 RA tools Part21 Parcels PLIB-editor Enterprise PLIB server Departmental PLIB server with web service Automated RA system originally designed for ISO13584-501 (LISI/ENSMA)


Omletto & PLIBBuilder for search, register, and update: DB Web Browser CQL Engine CQL Query CQLResutSet PLIB Dictionary PLIB Editor Omletto & PLIBBuilder for search, register, and update PLIB Builder plug-in Use EXCEL to make data/metada Web Service MS-EXCEL SOAP Parceling in CSV Part21 Domain Engineer CQL: Class Query Language, developed by TOSHIBA Use Web- Browser to get data PLIB Builder processes both data & metadata


Some PLIB tools are in business use: Some PLIB tools are in business use OmniPhase TM by TOSHIBA


Parceling Format; spreadsheet (CSV ) embedded PLIB format for definition and exchange of dictionary or library: Parceling Format; spreadsheet (CSV ) embedded PLIB format for definition and exchange of dictionary or library TOSHIBA initiated the development of PLIB spreadsheet format called “Parceling format” for the definition and exchange of PLIB dictionary and library. Now PARADINE joins TOSHIBA in the effort to develop the common spreadsheet format for an ISO-TS Parceling format in CSV may be converted into ISO10303-21 physical file for dictionary or for instance. --- The original parceling format was developed for OIDDI Poitiers Meeting, November, 2003. Since then, it has been tested in real business applications


Parcel sheet structure: Parcel sheet structure The parceling format consists of 8 spreadsheets called “Parcels” Parcels: (sheets with * are mandatory) *Dictionary *Supplier *Class *Property Enumeration Document (Reference) Table DataType (named_type)


Structure of a Parcel: Structure of a Parcel Each parcel has a self-similar structure Instruction column Cell columns


PLIB dictionary build-up; capturing, sharing, & structuring of information using spreadsheets and part21 file: PLIB dictionary build-up; capturing, sharing, & structuring of information using spreadsheets and part21 file Converter from Parceling Format to P21 Domain experts Dictionary editor / PLIB experts -> capture domain knowledge in well defined spreadsheet -> share domain semantics through collective review -> structure spreadsheet dictionary into well-formed PLIB -> review dictionary content from data modeling point of view Parceling format (CSV)


Advantage of Parceling format: Advantage of Parceling format Spreadsheets are part of established practice in engineering and management for data capture & transfer Good extensibility by domain experts & dictionary developers for their own use and applications Good interface with existing digital publishing software tools, such as MS-WORD Low cost tool for everyone, everywhere Assured convertibility to EXPRESS definitions


Base structure of a Parcel: Base structure of a Parcel A Parcel (spreadsheet) is composed of one instruction column for parcel attributes and multiple cell columns for meta-properties Each cell column for one meta property consists of the attributes specified in the instruction column Each parcel sheet has identical list of attributes Instruction column includes mandatory instructive attributes, optional instructive attributes, and optional informative attributes, and comment flag attributes, all of which start with “#” marks Each line corresponding to the attribute in the instruction column records the set of attribute values for the meta-properties in the parcel. The header parts of one package of Parcels constitutes a PLIB compatible dictionary. Each line in Data section records instances (of values) for the set of meta-properties If the meta properties define the PLIB data model, instances collectively correspond to the content of a dictionary, decomposed in the units of parcels. If the meta properties define PLIB dictionary properties, instances forms a population of parts for a class. Giving a different set of meta-properties, any other standard in SC4 may be possibly represented.


Structure of a Parcel: Structure of a Parcel Each parcel has a self-similar structure


Dictionary as content for Meta dictionary: Dictionary as content for Meta dictionary NOTE: Parceling prototype uses old code


Dictionary(property) as content, read into a parcel database (OmniPhase): Dictionary(property) as content, read into a parcel database (OmniPhase)


Dictionary(class) as content read into a database (OmniPhase): Dictionary(class) as content read into a database (OmniPhase)


Policy of coding properties: Policy of coding properties P35_Pxxx[_y] x and y is an alpha numeric number. Pxxx shows categories. _yy is used in local categories. Ex ) P35_P001_1 : dictionary id P35_P001_2 : supplier bsu P35_P001_3 : class/property/table/datatype/document bsu P35_P001_4 : non quantitative value code All of them describe the code to specify the coded objects, but they have different value format in PLIB, so we give them second code to distinguish.


Class: Class Code P35_P001_3 Version Number P35_P002_1 Revision Number P35_P002_2 Date of Original Definition P35_P003_1 Date of Current Version P35_P003_2 Date of Current Revision P35_P003_3 Preferred Name. P35_P004_1. Synonymous Name P35_P004_2 Short Name. P35_P004_3. Name Icon P35_P004_4 Definition. P35_P005. Source Document of Definition P35_P006_1 Note. P35_P007_1. Remark. P35_P007_2. Simplified Drawing P35_P008 Superclass P35_P010 Class Type P35_P011 Supplier P35_P012 Is Case Of P35_P013 Applicable Properties P35_P014 Applicable Types P35_P015 Applicable Documents P35_P094 Applicable Tables P35_P095 Visible Properties (it’s defined in other sheet) Visible Types (it’s defined in other sheet) Sub-class Selection Properties P35_P016 Class Value Assignment P35_P017 Imported Properties P35_P090 Imported Types P35_P091 Imported Tables P35_P092 Imported Documents P35_P093 Coded name P35_P018 Author P35_PS01 Link to excel file (metadic_clas.xls)


Property: Property Code P35_P001_3 Version Number P35_P002_1 Revision Number P35_P002_2 Date of Original Definition P35_P003_1 Date of Current Version P35_P003_2 Date of Current Revision P35_P003_3 Preferred Name. P35_P004_1. Synonymous Name P35_P004_2 Short Name. P35_P004_3. Name Icon P35_P004_4 Definition. P35_P005. Source Document of Definition P35_P006_1 Note. P35_P007_1. Remark. P35_P007_2. Author P35_PS01 NOT NULL Constraint P35_PS02 Classification label for class P35_PS03 Link to excel file (metadic_prop.xls) Graphics P35_P008 Property Data Element Type P35_P020 Definition Class P35_P021 Data Type P35_P022 Unit Structure P35_P023 Unit in Text Representation P35_P023_1 Unit in SGML Representation P35_P023_2 Value Format P35_P024 Preferred Letter Symbol in Text P35_P025_1 Preferred Letter Symbol in SGML P35_P025_2 Synonymous Letter Symbol　　　　　 P35_P025_3 Property Type Classification　　　　 P35_P026 Formula in Text P35_P027_1 Formula in SGML P35_P027_2 Condition P35_P028 DET classification P35_P040


Thank you for listening !Now PLIB is ready for use,in your business, and true issues are found, only after practice.: Thank you for listening ! Now PLIB is ready for use, in your business, and true issues are found, only after practice.