Copyright © 2006 Toshiba Corporation. All rights reserved.

Corporate R&D Center

Hiroshi MURAYAMACorporate R&D Center

TOSHIBA Corporation, Japan

PLIB Modeling: Part 3Principles of classification using ISO 13584-IEC61360 data model

A recipe for technical data dictionary

ISO TC184/SC4 Vice Equines Meeting in Italy

2 /

Overview of the structure of PLIB --- Parts

Part1

IEC61360

ISO13584

Part24

General Principle forIEC dictionary

IEC reference collection

Library Data Model

Supplier code

I/F to STEP

Part10

Geometry I/F

Introduction (deferred) Part501

Parametric

Model I/FPart20Part1

Part26

Part42 Part2

Part3

Part4

Part25

Part31

Part101

Part102

Part511

Part5

General Principle

Mathematical Expression

＝＝

Dictionaries and Maintenance

Dictionary Data-model

IEC Dictionary Maintenance Method (now superseded by

database procedure)

Part composition of ISO13584 and IEC61360 standards

3 /

Over view of the structure of PLIB --- dictionary

• Reference data dictionary/Consortium data dictionary

vs. Proprietary user dictionary• Used as an assortment of properties for building a user

dictionary• Sharing a concept of product with global/regional

community• Advantage of Reference dictionary

• Standardized & stable definition• Advantage of consortium dictionary

• Ready-to-use & up-to-date specification

• Role of user dictionary• Tailored compact specification for your own purpose

4 /

How to use PLIB dictionary and library

• Examples of reference data dictionary–ISO13584-501, ISO13584-511, IEC61360-4

• Examples of consortium data dictionaries–JEITA/ECALS dictionary, JEMA dictionary, GALIA dictionary

• Examples of proprietary user dictionary–Car demo dictionary of TOSHIBA

Now you are invited to browse http://www.toplib.com

5 /

Some PLIB tools are in business use

OmniPhase TM by TOSHIBA

6 /

Relation between a class and properties in PLIB

class

class

super

propertypropertyproperty

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.

7 /

What are visible & applicable properties?

• The class where the property is defined visible is called the definition class.

• Under the definition class the property makes sense.– So the name scope class is a modifier for the property

– E.g. The height of a man, and the height of a book, and the height of laptop PC are measured differently. The “height” only make sense if it is qualified by each domain of application, “man”, “laptop”, and ”book”,

• Applicable property of a class means, the class is characterized by the property.

– Usually visibility and applicability of property are the same

– There are exceptional cases where some subclasses of the definition class of a property does not contain the property.

8 /

Visible property---specification of domain

Does this make sense to add these heights?

Even calculation is wrong by definition.

Height of a book

Thickness of a book (not the depth!)

H1

H2

H3

H3

9 /

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 !

10 /

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 lengthNOTE 2: Version of each code is an integral part of identificationNOTE 3: Revision of each code is not an integral part of identification

Be aware, supplier_BSU is the identifier of information supplier.

11 /

• Supplier code consists ofICD + “/” +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 standardsIEC 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

12 /

BSU identification mechanism, for dictionary supplier

Data element name Description Mandatory or optional Data type Maximum length

International Code Designator (ICD)

the identification of an organization identification scheme

Mandatory integer 4

organization identification (OI)

the identification of an organization within an identification scheme

Mandatory string 35

organization part identification (OPI)

the identification of an organization part

Optional string 35

OPI source indicator (OPIS)

the specification of the source of the OPI

Optional character 1

Structure of ICD ( International Code Designator)Defined in ISO6523

13 /

You need some motor power here.

Class borrowing properties from others --- case of

Gasoline-powered vehicle

Passenger car

Automobile

Enginecapacity

No. ofpassengers

class Y

Electric component

Electric motor

Formula-1 Hybrid car

Motor power

Enginecapacity

Defined as visible

Defined as visible

Motorpower Imported from

motor power

Electric component dictionaryAutomobile dictionary

CASE _OF class

Enginecapacity

No. ofpassengers

No. ofpassengers

Enginecapacity

Enginecapacity

No. ofpassengers

Applicable property

Visible property

14 /

Class having component parts ---- class instance

Bus

Passenger car

Automobile

Enginecapacity

No. ofpassengers

CPU

Formula-1 sedan

Clock cycle

Enginecapacity

Defined as visible

Defined as visible

Ref. to Cls_BSU1

Referencing a CPU class as a

whole

Automobile dictionary

Enginecapacity

No. ofpassengers

No. ofpassengers

Enginecapacity

Enginecapacity

No. ofpassengers

Applicable property

Visible property

CPU typeManu-

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

15 /

• 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

16 /

• 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”

17 /

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

18 /

• 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

19 /

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

20 /

• 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 2Property 1Property 2Property 1

Property 3

Property 1Inherited 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 2Dictionary 1

class CASE _OF

NOTE: property in red circle means one in applicable state

21 /

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

22 /

• 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

23 /

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

24 /

• 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

• Name type

Available data types --- introduction

25 /

Available data types --- Level type

• Level type (real or integer)• 4 values fields, i.e., Minimum(min), Maximum(max), Typical(typ), No

minal(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

26 /

• 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

27 /

• 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

28 /

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 requi

red, 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.

29 /

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

30 /

Thank you for listening !Now you are ready to build your own

data dictionary.