9th International Forum on Meta Registry
Corporate R&D Center
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
Copyright © 2006 Toshiba Corporation. All rights reserved.
Presentation outline
• ISO TC184/SC4 standards
• PLIB Standard status
• PLIB Global ontology
• PLIB Database structure
• TOSHIBA’s involvement in PLIB
2
/
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
3
/
Most of the Parts have already become IS
Part No
Title of Part of ISO13584
stage
1
Overview and fundamental principles
IS
10
Conceptual model of parts library
differed
20
Logical model of expressions
IS
24
Logical model of supplier library
IS
25
Supplier library with aggregate values and explicit content
IS
26
Supplier Identification
IS
31
Geometric Programming Interface
IS
42
Methodology for structuring part families
IS
101
Geometrical view exchange protocol by parametric program
IS
102
View exchange protocol by ISO 10303 conforming specification
IS
4
/
IS: International Std.
DIS : Draft ISO Std.
Overview of the structure of PLIB --- Parts
Part composition of ISO13584 and IEC61360 standards
General Principle for
IEC dictionary
IEC61360
Mathematical
Expression
General
Principle
Part1
Dictionary Data-model
Geometry I/F
Parametric
Part1
Part20
Part10
Part24
Part42 ＝ Part2
Part26
Part3
ISO13584
Library Data
Model
Part4
Model I/F
Part101
Part25 ＝ Part5
Supplier
code
Introduction
(deferred)
Part31
Part102
Part501
I/F to STEP
Part511
IEC reference collection
IEC Dictionary Maintenance
Method (now superseded by
database procedure)
5
/
Dictionaries and
Maintenance
Std. Dictionary
IEC61360-4
Title
IEC reference collection of
Domain
Electro-electronic
Stage
IS
TC/Proponent
IEC SC3D
standard data element types and
Registration Authority for
environment & laboratory measuring
Cutting tool data representation
Cuttinginstruments
tools
ISO-TS
component classes
ISO13399-2,-3,-4
ISO TC29
and exchange
ISO13584-501
Reference dictionary for
Measuring instruments
(pre)IS
measuring instrument---
ISO TC184/SC4
TOSHIBA-JEMIMA
Registration procedure
ISO13584-511
Reference dictionary for
mechanical fasteners
ISO 23584
Optics and photonics --
Mechanical fasteners
(Pre) IS
(bolts and nuts)
ISO TC184/SC4
ISO TC2
Optics
CD
TC172 / DIN
Roller bearing
?
TC4
Specification of reference
dictionary
ISO/AWI
Rolling bearings -- Parts library - Reference dictionary
23768
6
/
Std.
Title
Domain
Stage
Proposer
Dictionary
Equipment Catalogues Part 2: Measuring
equipment properties for
electronic data
exchange
IEC61957 －2
7
/
Process
equipment
NWI/W
D
IEC SC65B
NAMUR/DIN
Publicly available consortium dictionaries
Promoter
JEMA @
Dictionary
JEMA dictionary
Domain
Electric
data
Country
yes
Japan
No
Japan
Yes
Japan
Machinery
JEMIMA @
Extended JEMIMA dictionary for
measuring
measuring instruments
instruments
(P501+Process measuring instrument)
JEITA @
ECALS dictionary
Electroelectronic
GALIA @
GALIA PFI dictionary
Automobile
Yes
Related.
(test)
France
8
/
ISO/IEC Guide 77 to Support dictionary development
Committee
Title
Proponent
ISO/IEC JWG1
ISO/IEC guide 77 :Guide for specification
of product properties and families
DIN
9
/
PLIB new parts under development
Std. Dictionary
ISO13584-42
Ed2
Title
function
Methodology for
Dictinary model
structuring part
update
Stage
TC/Proponent
CD
TC184/SC4
WD
TC184/SC4
PWI
TC184/SC4
(NWI/
TOSHIBA-
CD in
Paradine
families
ISO13584-32
Xml exchange format
Collaboration with
OTD group
ISO13584-35
Common spreadsheet
Spreadsheet I/F
TS
Interface for parts
such as for MS-
library
EXCEL both
dictionary & Library
ISO 13584-500
Dictionary for basic
Properties such as
product description
Manufacturer, part
June)
PWI
TC184/SC4
TOSHIBA
No, which are used
in many dictionaries
ISO13584-26
Information supplier
Information supplier
NWI/AMD
identification
identification based
on ICD
10
/
WD
TC184/SC4
(TOSHIBA)
• PLIB ontology model
11
/
Basic concept of class and property in PLIB
class
super
Visible Properties
name scope
property
property
property
class
Class BSU
name;
definition;
etc.
as inverse
described by
Applicable Properties
property BSU
name;
definition;
data
type;
unit;
etc.
Note: this figure shows a conceptual reference framework,
and does not depict actual connection between the entities.
12
/
Concept of a property; three sub types exist
(ABS) property
Non dependent
property
dependent
property
condition
Depend_on
Condition is a property that serves as a condition for another property
13
/
PLIB modeling layers; dictionary and instances (content)
META MODEL
DICTIONARY (meta data)
Library
Model (DB schema)
for Domain Ontology
INSTANCES (data)
(catalogue)
within standard
Transaction
Model
Messaging ,Transaction, & Query
TOSHIBA is developing CQL language
14
/
CQL (Class Query Language)
Sample Tree for Vehicle
SELECT * FROM Ecological* ;
Product
Ecological
Vehicle
(Ecological)
(pid, name, maker, price)
Vehicle
(weight, max_speed)
Electric
Vehicle
（Electric）
Compressed
Natural Gas
Vehicle
(LNG)
15
/
Hybrid
Vehicle
(Hybrid)
Sedan
(displacement,
engine_type)
(motor_max_power,
motor_type)
Ontology as a cascade of reference dictionaries
Standard reference dictionary
IEC 61360-4
Linguistic taxonomy, e.g. UNSPSC
Electric
component
Electric Parts
Electric motor
Sensor
DC motor
AC motor
3phase AC motor
ECALS dict.
Electric
MOTOR
Consortium
dictionary
DC motor AC MOTOR
Proprietary dictionary
Proprietary
dictionary
3-Phase AC
motor
TSB
Part NO
/
Import of properties
Explosion Rated Input
Proof
Voltage
TOSHIBA
AC motor
16
Motor
power
Consortium dictionary
….
Linear
motor
Electric
motor
Import of properties
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
17
/
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 !
18
/
Basic Semantic Unit (BSU), meaning and being
Class and property identification structure in PLIB
Class identification by absolute ID
Supplier_BSU “-” ver.
“.”
Class BSU “-” ver.
up to14characters
up to70 characters
Property identification by absolute ID
Supplier_BSU “-” ver.
up to70 characters
“.”
Class BSU “-” ver.
up to14characters
“.”
Property BSU“-” ver.
up to14characters
Be aware, supplier_BSU is the identifier of information supplier.
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
19
/
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.
• 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”
NOTE: Currently OPI is not usable in PLIB
20
/
BSU identification mechanism, for dictionary supplier
Structure of ICD ( International Code Designator)
Defined in ISO6523
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
21
/
Class borrowing properties from others --- case of
Automobile dictionary
Defined as
visible
Engine
capacity
Electric component dictionary
Electric
component
Automobile
Defined as
visible
class Y
No. of
passengersPassenger
car
Electric
motor
Motor
power
CASE _OF
class
Engine
capacity
Gasolinepowered
vehicle
Formula-1
Engine
capacity
No. of
passengers
Engine
capacity
Applicable property
Visible property
22
/
No. of
passengers
Hybrid car
Engine
No. of
capacity passengers
You need
Motor
Imported from
power
some motor
motor power
power here.
Class having components or composite properties
Electronic parts dictionary
---- class instance type
Electronic
parts
Automobile dictionary
Defined as
visible
Engine
capacity
Automobile
Defined as
visible
No. of
passengersPassenger
car
CPU
Equipped
with
Navigation
system
Cls_BSU1
Clock
cycle
CPU type
Manufacturer
P_BSU 1
P_BSU 2
P_BSU 3
Engine
capacity
Bus
Formula-1
Engine
capacity
No. of
passengers
Engine
capacity
No. of
passengers
sedan
Engine
No. of
Ref. to
capacity passengers Cls_BSU1
P_BSU 1:= 2 Ghz
Applicable property
Visible property
23
/
P_BSU 2:= Pentium
P_BSU 3:= Intel
Referencing a
CPU class as a
whole
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
24
/
Principal class attributes --- Definition
• 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 !
NOTE: ISO10241 “International terminology standard- Preparation and layout”
25
/
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
26
/
Principal class attributes --- some other attributes
• 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
27
/
Property and principal property attributes
Visible properties and Applicable properties
• 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
Applicable
properties
28
/
Property and principal property attributes
• Visible/Applicable structure allows a subclass which is especially
immune from the effect of inherited property
• When imported visible properties become applicable
Defined as
Dictionary 1
Dictionary 2
visible
Property 1
class 1
Inherited and
changed to
applicable
Defined as
visible
Property 2
class X
class Y
class Z Property 3
class 2
Property 1
class 4
class 3
Property 1 Property 2
Property 1 Property 2
Inherited and
kept as visible
class 5
class
CASE _OF
Property 1 Property2 Property 3
Inherited and
changed to
applicable
Inherited and
changed to
applicable
Made applicable
as a result of
importation
NOTE: property in red circle means one in applicable state
29
/
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
30
/
Principal property attributes --- Definition
• 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...
31
/
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
32
/
Available data types --- introduction
• 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
33
/
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
34
/
Available data types--- Aggregate type
• 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
35
/
Available data types--- Enumeration type
• 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
36
/
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.
37
/
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
38
/
Toshiba’s involvement in PLIB
39
/
Parceling format has been tested through the use in TOSHIBA applications
and ISO13584-501 RA tools
Parcels
Automated RA system originally designed
for ISO13584-501
Enterprise PLIB server
PLIB-editor
(LISI/ENSMA)
40
/
Part21
Departmental PLIB server
with web service
Omletto & PLIBBuilder for search, register, and update
PLIB Editor
PLIB Builder plug-in
MS-EXCEL
PLIB Dictionary
Use
EXCEL to
make
data/metad
a
SOAP
Use WebBrowser to
get data
Part21
Web Service
Parceling in CSV
Domain
Engineer
CQL Query
Web Browser
CQLResutSet
CQL Engine
PLIB Builder processes
both data & metadata
DB
41
/
CQL: Class Query Language, developed by TOSHIBA
Some PLIB tools are in business use
OmniPhase TM by TOSHIBA
42
/
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
43
/
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
Dic
Sup
DataType (named_type)
Clas Prop
44
/
Structure of a Parcel
Dict Sup
Instruction column
Cell columns
Clas Prop
parcel_sheet.encoding
parcel_sheet
Each parcel has a self-similar structure
parcel_sheet.source_language
.cmment_lines[0]
・・・・・・・・
.cmment_lines[4]
#ENCODING:UTF8
#SOURCE_LANGUAGE:EN
parcel_sheet.preferred_name
parcel_sheet.code
#CLASSBSU:C001
#CLASSNAME.<lang>:cname
parcel_sheet.definition
#CLASSDEFINITION.<lang>:cdef
#CONTENTID:con001
#CONTENTNAME:conname
#DISCLOSURE:PUBLIC
parcel_sheet.cell_coumlns[5]
parcel_sheet.cell_coumlns[0]
・・・・・・・・・・
#PRIVILEGE:ORDINARY
#GROUP:G001
P004
P003.JA
P003.EN
P002.MAX
P002.MIN
P003
#PROPERTYBSU
DX006
DX005
DX004
DX003
DX002
DX001
#ALTERNATIVEID
name004
name003
name003
name002
name002
name003
#PREFNAME.<lang>
def004
def003
def003
def002
def002
def003
#DEFINITION.<lang>
#DATATYPE
.cmment_lines[5]
・・
.cmment_lines[7]
#VALUEFORMAT
#UNIT
#KEYS
#LEVEL
#AGGREGATE
#LANG
parcel_sheet.cell_values
parcel_sheet.cell_values[2]
STRING_TY
PE
REAL_MEAS
URE_TYPE
REAL_MEAS
URE_TYPE
M..100
NR2..3
kg
NR2..3
kg
KEY
MIN
STRING
STRING
SET(0,10) OF
INT_TYPE
M..100
M..100
NR1..4
KEY
KEY
EN
xxxxx
xxxxx
xxxxx
xxxxx
xxxxx
JA
xxxxx
xxxxx
xxxxx
xxxxx
xxxxx
xxxxx
xxxxx
xxxxx
xxxxx
xxxxx
MAX
xxxxx
xxxxx
xxxxx
xxxxx
xxxxx
parcel_sheet.cell_values[2][1]\cell.cell_value
45
/
parcel_sheet.cell_coumlns[5]\cell_column.
parcel_sheet.cell_coumlns[5]\cell_column.
parcel_sheet.cell_coumlns[5]\cell_column.
parcel_sheet.cell_coumlns[5]\cell_column.
parcel_sheet.cell_coumlns[5]\cell_column.
parcel_sheet.cell_coumlns[5]\cell_column.
parcel_sheet.cell_coumlns[5]\cell_column.
SET(0,10)
xxxxx
xxxxx
xxxxx
xxxxx
xxxxx
parcel_sheet.cell_coumlns[5]\cell_column.
xxxxx
xxxxx
xxxxx
xxxxx
xxxxx
PLIB dictionary build-up; capturing, sharing, & structuring of information
using spreadsheets and part21 file
Domain experts
-> capture domain knowledge in well defined spreadsheet
-> share domain semantics through collective review
Dictionary making tools
(excel macro etc.)
Converter from
Parceling Format
to P21
Parceling
format
(CSV)
p21
EXPRESS
compiler to R / W,
check constraints
Dictionary editor / PLIB experts
-> structure spreadsheet dictionary into well-formed PLIB
-> review dictionary content from data modeling point of view
46
/
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
47
/
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.
48
/
Structure of a Parcel
Dict Sup
Each parcel has a self-similar structure
Instruction column
#ENCODING:UTF8
#SOURCE_LANGUAGE:EN
#CLASSBSU:C001
#CLASSNAME.<lang>:cname
#CLASSDEFINITION.<lang>:cdef
#CONTENTID:con001
#CONTENTNAME:conname
#DISCLOSURE:PUBLIC
#PRIVILEGE:ORDINARY
#GROUP:G001
#PROPERTYBSU
#ALTERNATIVEID
#PREFNAME.<lang>
#DEFINITION.<lang>
Header
section
#DATATYPE
#VALUEFORMAT
#UNIT
#KEYS
#LEVEL
#AGGREGATE
#LANG
P003
DX001
name003
def003
P002.MIN
DX002
name002
def002
P002.MAX
DX003
name002
def002
P003.EN
DX004
name003
def003
P003.JA
DX005
name003
def003
P004
DX006
name004
def004
STRING_TY
PE
REAL_MEAS
URE_TYPE
REAL_MEAS
URE_TYPE
STRING
STRING
SET(0,10) OF
INT_TYPE
M..100
NR2..3
kg
NR2..3
kg
M..100
M..100
NR1..4
KEY
KEY
MIN
MAX
KEY
SET(0,10)
xxxxx
xxxxx
xxxxx
xxxxx
xxxxx
Data
section
49
/
Clas Prop
Cell column
xxxxx
xxxxx
xxxxx
xxxxx
xxxxx
xxxxx
xxxxx
xxxxx
xxxxx
xxxxx
EN
xxxxx
xxxxx
xxxxx
xxxxx
xxxxx
JA
xxxxx
xxxxx
xxxxx
xxxxx
xxxxx
xxxxx
xxxxx
xxxxx
xxxxx
xxxxx
Dictionary as content for Meta dictionary
50
/
NOTE: Parceling prototype uses old code
Dictionary(property) as content, read into a parcel database
(OmniPhase)
51
/
Dictionary(class) as content read into a database (OmniPhase)
52
/
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.
53
/
Class
<PLIB attributes with parceling code>
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.<lang>
P35_P004_1.<lang>
Synonymous Name
P35_P004_2
Short Name.<lang>
P35_P004_3.<lang>
Name Icon
P35_P004_4
Definition.<lang>
P35_P005.<lang>
Source Document of Definition
P35_P006_1
Note.<lang>
P35_P007_1.<lang>
Remark.<lang>
P35_P007_2.<lang>
Simplified Drawing
P35_P008
Superclass
P35_P010
Class Type
P35_P011
Supplier
P35_P012
<System attributes with parceling code>
Author
P35_PS01
54
/
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
Link to excel file (metadic_clas.xls)
Property
<PLIB attributes with parceling code>
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.<lang>
P35_P004_1.<lang>
Synonymous Name
P35_P004_2
Short Name.<lang>
P35_P004_3.<lang>
Name Icon
P35_P004_4
Definition.<lang>
P35_P005.<lang>
Source Document of Definition
P35_P006_1
Note.<lang>
P35_P007_1.<lang>
Remark.<lang>
P35_P007_2.<lang>
<System attributes with parceling code>
Author
P35_PS01
NOT NULL Constraint
P35_PS02
Classification label for class
P35_PS03
55
/
Graphics
P35_P008
Property Data Element Type
P35_P020
Definition Class
P35_P021
Data Type
P35_P022
Unit Structure
P35_P023
Unit in Text RepresentationP35_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
Link to excel file (metadic_prop.xls)
Thank you for listening !
Now PLIB is ready for use,
in your business,
and true issues are found,
only after practice.
56
/