MM Harmonization Document

PiLog India Private Limited
Doc NoPIPL-5-04-001
MATERIAL MASTER HARMONIZATION

GUIDELINES FOR JSL
COPYRIGHT © 2018 PILOG
Rights to the contents of this document

This document contains proprietary information belonging to PiLog Inc. It may not be reproduced without
written permission. Disclosure of the contents of this document to third parties is strictly prohibited. The
information in this document is correct at the time of producing it.
TITLE PAGE
Document Title Material Master Harmonization Guidelines
Document Number PI-IND-5-04-001
Document Issue Version 1
Compiled By Koti Azmira
Effective Date 02 February 2019
Issue Date 02 February 2019
Controlled By Content Management Office
Electronic Media Media Media Identifier

Di s k i dentifier PIPL-5-04-001
Fi l e Identifier Generic MM Ca talogue Specifications to a client
Di s k controlled by Content Ma nagement OFFICE
Approval Position Name Signature Date

CIO – Chi ef Informa ti on Ima d A Syed 5 th April, 2018
Offi cer Pi Log India
AMENDMENT HISTORY
Doc. Issue Date Changed Chapter / No of Checked by

Pages
Topic / Page Name Initial
Version 1.00 05-04-18 First Issue 78
DISTRIBUTION LIST
Distribution This document will be under distribution control to the following persons:
Control
Copy Person Organisation Distr. E-Mail

Control
1. Mr. Ima d A Syed Pi Log Ima d.Syed@PiLog.in
3. Koti Azmi ra Pi Log Koti .a zmira@PiLog.in
Contents
1 Introduction ...................................................................................................................................... 1
1.1 Objective ................................................................................................................................... 1
1.2 Levels of cataloguing .................................................................................................................. 1
1.2.1 Level 1: Reference Data Extraction ....................................................................................... 1
1.2.2 Level 2: Allocation of a PPO -OTD Class ................................................................................ 1
1.2.3 Level 3: Value Extraction ...................................................................................................... 1
1.2.4 Level 4: Dat a Enrichment ..................................................................................................... 1
1.3 CATALOGUING RULES.............................................................................................................. 2
1.4 DICTIONARY ............................................................................................................................. 2
2 Levels ofDat a Harmonization ............................................................................................................. 3
2.1 Level 1: Reference Data Extraction .............................................................................................. 3
2.1.1 General Extraction Rules...................................................................................................... 4
2.1.2 Manufacturer/Supplier Part number Extraction Rules ............................................................. 4
2.1.3 Other Reference Data Extraction Rules ................................................................................. 6
2.2 Level 2: class allocation procedure .............................................................................................. 6
2.3 Level 3: Value Extraction............................................................................................................. 6
2.3.1 Population of Characteristic/Property Values ......................................................................... 7
2.3.2 Clean up of FFT after Level 2 & 3 processing ........................................................................ 7
2.3.3 Technical Value Standardization (TVS) of Property Values ...................................................... 8
2.4 Level 4 Data Enrichment ............................................................................................................. 8
3. Description Generation or Rendering .................................................................................................. 9
3.1 Description Generation of Rendering Algorithm ................................................................................. 9
3.1.1 Short Text (SFD) Generation – Length: 40 Characters ................................................................. 9
3.1.2 Purchase order Description (POD) Generation ..........................................................................11
3 Standardization............................................................................................................................... 13
3.1 Standardization Methodlogy ...................................................................................................... 13
3.1.1 Fractions ........................................................................................................................... 14
3.1.2 Decimals ........................................................................................................................... 14
3.1.3 Tolerance for Units of Measure ........................................................................................... 14
4 Approved Standardization Principles and Guidelines ......................................................................... 14
4.1.1 Sizes/Dimensions .............................................................................................................. 14
4.1.2 Electrical Ratings ............................................................................................................... 16
4.1.3 Material Values .................................................................................................................. 20
4.1.4 Pressure Ratings ............................................................................................................... 21
4.1.5 Threads and Connections .................................................................................................. 22
4.1.6 Pipe and Tube Fittings: (Adaptors, Elbows, Tees, Etc.) ......................................................... 24
4.1.7 Attribute,- Connection Type: ............................................................................................... 25
4.2 Object Specific Rules ................................................................................................................ 26
4.2.1 Hose assemblies ............................................................................................................... 26
4.2.2 Nipple: Pipe....................................................................................................................... 26
4.2.3 Elbow: Tube ...................................................................................................................... 26
4.2.4 Hose Assemblies: Connection 1.......................................................................................... 27
4.2.5 Bearings ........................................................................................................................... 27
4.2.6 Clothingand Footwear ........................................................................................................ 29
4.2.7 Batteries ........................................................................................................................... 30
4.2.8 Drills ................................................................................................................................. 31
4.2.9 Gaskets ............................................................................................................................ 31
4.2.10 Gas, Mixtures .................................................................................................................... 33
4.2.11 Motors (Electrical) .............................................................................................................. 33
4.2.12 Nuts .................................................................................................................................. 34
4.2.13 O-Rings ............................................................................................................................ 34
4.2.14 Seals ................................................................................................................................ 35
4.2.15 Shafts ............................................................................................................................... 35
4.2.16 Switch ............................................................................................................................... 36
4.2.17 Transformer, Distribution .................................................................................................... 36
4.2.18 Valves ............................................................................................................................... 36
4.3 Additional Rules ....................................................................................................................... 37
4.3.1 Free Format Text - (FFT) .................................................................................................... 37
4.3.2 The Attribute, TYPE- .......................................................................................................... 37
4.3.3 The Attributes, SPECIAL FEATURES - V - FURNISHE D ITEMS ........................................... 38
4.3.4 The attribute, COMP RISING............................................................................................... 39
4.3.5 Measurements................................................................................................................... 39
4.3.6 Mass/Weight ..................................................................................................................... 42
4.3.7 Meters/Gages .................................................................................................................... 43
4.3.8 Specifications and Standards ............................................................................................. 43
4.4 Symbols................................................................................................................................... 44
4.5 Units of Measurements and Abbreviations .................................................................................. 44
4.6 Conversion Table (Fractions/Decimals/Millimeters) ..................................................................... 45
4.7 STA NDA RD THREA D PITCH TABLE ......................................................................................... 49
4.7.1 Unit of Measures (UOM) .................................................................................................... 51
5 MDPM WORK FLOW ...................................................................................................................... 52
About This Document
In printed form, this document serves as a working guideline, in that you can make note of
issues and value-structuring methods that may arise. Keep it handy for reference, so that
you can use it effectively to its purpose: enhancing consistency and value standardization.
MATERIAL MASTER HARMONIZATION GUIDELINES
VERSION 1.00
1 INTRODUCTION
1.1 OBJECTIVE
The primary objective of this Material Master Data Standardization specification document
is to guide the user through the complete process of cataloguing and standardization. This
document explains in detail the various steps and procedures to be followed during the
cataloguing and data structuring process in reference to the PiLog Preferred Ontology (PPO).
By following the steps and procedures explained in this document, users significantly
increase favourable project outcome by generating seamless, structured and we l l-de fi ne d
descriptions for all items catalogued.
1.2 LEVELS OF CATALOGUING

Cataloguing data is broadly classified into 4 major levels, which are briefly explained be l ow.
The levels are discussed in detail in Section 3.
1.2.1 LEVEL 1: REFERENCE DATA EXTRACTION
This is the process of identifying and capturing all the reference values of the ite ms such as
Manufacturer name and part number. Drawing numbers, Supplier references and any othe r
reference values of the item, this will be used to describe the item during purchasing.
1.2.2 LEVEL 2: ALLOCATION OF A PPO-OTD CLASS
In this level, each item will be assigned with a suitable PPO. The assignment of cl ass al l ows
all items to be grouped, as defined by the dictionary (i.e. PPO), and to have a correspondi ng
template assigned to the items.
1.2.3 LEVEL 3: VALUE EXTRACTION
In this level all values are populated against corresponding properties and all “junk” data
available will be cleansed. At this level, users can see homogeneous descriptions generated.
1.2.4 LEVEL 4: DATA ENRICHMENT
Level 4 is further classified into two more levels as explained below.
1.2.4.1 LEVEL 4E: ENRICHMENT VIA RESEARCH
Level 4E data enrichment is performed through external research to generate additional

data from technical sources such as manufacturer's catalogues (PDF Library) or the Inte rne t
(Manufacturer's website, Catalogue cuts etc.) as well as cross-verification and cross-
validation of internal information. Further cleansing occurs from validation and
standardization through validation, cross-reference and harmonization.
1 Issue Date 5 December 2016

VERSION 1.00
1.2.4.2 LEVEL 4M: ENRICHMENT VIA PHYSICAL WALKDOWNEXCERCISE
Level 4M data enrichment is sourced through physical walk-down & verification in the
warehouse to enrich the items.
1.3 CATALOGUING RULES

PiLog follows two basic rules during the entire process of cataloguing:
Rule 1:
Do not remove or delete any data provided by the client unless the data is duplicated.
Duplicated in this context refers to the scenario where a word, concept, value, attribute, etc.
Is duplicated within the/a single description or text provided for the item.
Records are NEVER deleted by PiLog, but will be flagged as Potential Duplicates. It will
always be the Client’s responsibility to verify and confirm whether items flagged as Potential
Duplicates are indeed duplicates or not before being removed from the Item Master Set.
Rule 2:
No extra values will be added to client’s data unless researched from a source with integri ty
and authority. If PiLog adds values to a Client’s master data item, PiLog will provide the
source and authenticity for the data added.
1.4 DICTIONARY
The PPO, which is a sub set of the Open Technical Dictionary (OTD), will be used as
Dictionary of choice for the Material Master Standardization process for JSL.
The PPO-OTD dictionary consists of pre-defined templates. The template consists of a l i st of
Classes (Object Qualifier combination) with a set of Properties (Attributes). PiLog wil l make
available the PPO-OTD dictionary (Class/Properties/Abbreviations) for general reference.
PiLog will create Client Preferred Ontology (CPO) by copying over general templates
common to most companies and known and expected templates for the specific Client. The
JSL team will then confirm their CPO templates by confirming or giving approval to:
• The template Class & Property combination for a particular class, including linkage
of respective UNSPSC version 19.
• The properties listed on the template as being complete and property identified as
mandatory and optional.
• Ordering of Properties for description generation.
(Note, for ease of discussion PPO and CPO are interchangeable in following
sections.)
This review and feedback is only done in the MDPM software not in any other editable or
data exchange formats.

VERSION 1.00
PiLog will have the right to make the following changes in the dictionary:
• Change existing Classes and or Attributes of the PPO where necessary.
• Register new Classes and or Attributes in the OTD, and add it to the PPO.
If PPO dictionary changes are made, PiLog will only update the changes/additions in the
MDPM software tool; no additional approval is required from JSL to incorporate the changes
as PiLog manages the PPO dictionary as per industry standards.
PPO is the intellectual property of PiLog. Once the confidentiality document is signed
between both the parties PiLog will provide the JSL related intellectual property in any
format required by Client.
PiLog will provide the templates in spread sheet format. JSL will review and add their
comments and will be return back the file to PiLog. PiLog will review the changes and
implement the proposed changes.
2 LEVELS OF DATA HARMONIZATION

2.1 LEVEL 1: REFERENCE DATA EXTRACTION
The main Objective of this exercise is to capture all the reference data of the items provide d
in the original short and original long.
Reference Data is defined as the supporting information that will assist in procuring an item.
It is the key data which the OEM, OCM manufacturer or supplier of the item uses to refer the
item such as part number, Catalogue number, Article number etc. Reference data may al so
refer to the linkage of the item to higher assembly such as linkage to parent equipment,
model numbers, serial numbers, drawing numbers, catalogue numbers, Equipment tag
numbers, and documentation references of the parent equipment.
Important Note: Reference Data does not include the specific technical properties of the
material item, but rather supporting information that will assist in the purchasing of an item.
Reference data is the data provided by the vendors, Manufacturers or Suppliers who provide
the item/spare to the client. This data serves as a means of identification of the item.
Some of the common reference data types that will be captured include but not l i mi te d to
the following
1. Manufacturer Name(s)
2. Manufacturer Part number(s)
3. Supplier Name(s)
4. Supplier Part number(s)
5. Drawing number(s)
6. Model/Serial number(s)
7. Equipment/Tag number(s)
8. Catalogue/documentation number(s)
Reference Data Extraction is the process of extracting clearly indicated or universally known
reference data from the original short and original long provided by JSL. At this Level of
harmonization, action will be taken by PiLog to Identify and extract al l the reference data
from original short and original long descriptions.

VERSION 1.00
Major exercise done at this level includes but not limited to

• Extract Vendor name(s) and their corresponding Part number(s) from the original short
and original long and populate the data into appropriate segment or table in the system
(data structure).
• Validate Part number(s) Vendor name(s) to determine the part type and populate i nto
Part number segment. Flag part type as OEM, OCM, Manufacturer or Supplier based on
the information available in the original short and original long.
• Extract all other Reference number(s) with Vendor name(s) available in the original
short and original long and populate in the appropriate Reference data segment with
appropriate labels such as model number, serial number, drawing number, equi pment
tag number, equipment model number etc.
• Extract documentation data available in the original short and original long and
populate into documentation segment(Data relate to catalogue number and drawing
number).
• Determine the document type & revision available in the original short and original long
and populate into the documentation segment.
• End equipment details such as Tag no’s, machine Model no’s, will be added in the
reference tab.
The above reference data extracted will be stored in appropriate fields and this will be use d
to identify part number duplicate resolution easier and assist in the standardizing of
manufacturer/supplier and drawing numbers.
2.1.1 GENERAL EXTRACTION RULES
• All Original component Manufacturer (OCM)/ Original Equipment Manufacturer data

extracted from the original short and original long will be populated into the
appropriate Fields/tables.
• All drawing numbers along with its relevant information will be captured under the tab
– Documentation.
• All the other reference data available in the original short and original long will be
captured into appropriate fields; suitable reference labels will be selected.
• All extracted drawings numbers will be included in the Purchase Order Description
(POD).
2.1.2 MANUFACTURER/SUPPLIER PART NUMBER EXTRACTION RULES
• If a clearly indicated part number and a name of a known manufacturer/supplier

appears directly after or before the part number in the original description, the
assumption will be made that the name after or before a part number is the
manufacturer name of the item and will therefore be extracted to the manufacturers
table as a manufacturer pair.

VERSION 1.00
• Clearly indicated manufacturers will be extracted and marked as being a manufacture r.

Clearly indicated suppliers or vendors will be extracted and marked as being suppl i ers.
Where the descriptions don’t clearly distinguish between a manufacturer and a supplier
the data will be extracted and marked as being a Manufacturer.
• If a clearly indicated part number appears in the original short and original long text
with no indication of a manufacturer/supplier, the part number will be extracted to the
manufacturer tab. If no prefixes are found, the data will be extracted only in cases
where cataloguers with the necessary technical knowledge can identify the numbe r as
a part number. However if no prefixes are found, or a number cannot be identified with
the necessary technical knowledge, the data will not be extracted in reference tab.
• If a clearly indicated manufacturer/supplier appears in the original short and original
long text with no indication of a part number prefixing the manufacturer/supplier
name, the manufacturer/supplier will be extracted as a manufacturer and the part
number field populated with “UNKNOWN” as the part number in the manufacturer tab.
• If a clearly indicated part number or any other reference number is provided in the
description without indicating any MFR/VENDOR/SUPPLIER name, in such cases the
numbers will be captured in the appropriate fields, with the appropriate reference
labels, however manufacturer name will be captured as “UNKNOWN” and the name
will automatically be flagged as manufacturer. However PiLog will refer to the three
year PO data and try to acquire the data or PiLog will contact JSL facilitate the
information.
• In the case where a new and old part number appears in the original description, both
numbers will be captured. The old part number will have a prefix as “OLD” and new
part will have prefix “NEW”.
• All part /reference numbers like new & old part numbers, supplier part numbe rs, e tc.
will be included in PO description.
The following table clearly explains all the above scenarios:

Source description Part number field Manufacturer/Supplier field
Bearing P/N 6206 Manuf SKF 6206 SKF
Bearing P/N 6206 6206 UNKNOWN
Bearing Manuf SKF UNKNOWN SKF
Bearing Old P/N 6206 New P/N 6206 OLD 6206 SKF
C3 Manuf SKF
NEW 6206 C3 SKF
*Note: Level 4 processing may enhance and correct missing data elements identified in Level
1.

VERSION 1.00
2.1.3 OTHER REFERENCE DATA EXTRACTION RULES
Drawing Numbers:
Drawing numbers will be captured under the Documentation tab along with its re l ate d data
as mentioned below
• Drawing Item number (Position Numbers)
• Drawing Revisions
If a DRAWING number appears along with Manufacturer/Supplier in the original short and
original long description, the number will be extracted into the document table and DOC
TYPE will be flagged as Mfr Drawing.
2.2 LEVEL 2: CLASS ALLOCATION PROCEDURE

• Read and review JSL data provided in the original short and original long thoroughly
before making a decision.
• Review PPO dictionary options.
• Read and understand class (descriptor) definition.
• Assign the best-suited class based on the original short and original long description.
• In case the provided description is not sufficient to assign a suitable detailed class, then
a generic class would be assigned to the item.
Example: If PiLog is not able to identify a specific Valve i.e. Vale, Gate or Valve, Ball e tc.
for that specific item Class Valve will be assigned and it will have all the Properties
related to Valve like size, Material etc.
In cases where even a generic class could not be assigned, the item will remain on level 1,
Items identified as such, will be submitted to JSL for a decision or for additional information
in order to assign a proper PPO-OTD Class.
Note: During level 2, Data left in the Free Format Text (FFT) will be cleaned to certain extent
by removing the class value if present in the description.
2.3 LEVEL 3: VALUE EXTRACTION

Once the item is assigned a PPO-OTD class, a set of specific required properties or
characteristics that describe the item in detail will be linked to the item from Pi Log’s PPO -
OTD dictionary.
At this level, PiLog takes action to Identify and extract the characteristic data from the
original short and original long description and fill against the properties. An item is
considered Level 3, if one or more Properties can be populated from the client source
description.
The main exercises performed in the level include.

VERSION 1.00
• Extract the property value(s) and UOM(s) value for each property by studying the
property definition from the dictionary and populate property value segments.
• Validate all property values and UOM data provided in the original short and original
long description.
• Determine the UOM for each property value from original short and original long form
(Wherever applicable)
• Standardize the values according to agreed standards.
• Universally accepted industry standard terminology & annotation will be used
wherever applicable.
2.3.1 POPULATION OF CHARACTERISTIC/PROPERTY VALUES
The following extraction guidelines are used during data Extraction into templates:
• Only clearly recognizable values will be captured into properties.
• The values will be captured as provided in the original short and original long
description. No research will be done to check the correctness of the given value
(except in special cases, where the value appears to be incorrect). There are no QC
tools to check the wrong data.
• In case of contradictory values provided in the original short and original long
description, JSL will be notified and PiLog will wait for JSL’s decision for further action.
• On items where original short and original long data contains values, which does not fi t
into any of the property templates, then such values will be transferred to Free Format
Text (FFT).
2.3.2 CLEAN UP OF FFT AFTER LEVEL 2 & 3 PROCESSING
The term FreeFormat Text or FFT, is an area used to capture any information left in the
original description after the reference data and Property values have been extracted to
their respective fields.
FFT will consist of any technical information supporting the material item itself, which has no
Property in the template to populate. Each set of values in FFT will be separated by a comma
(,) from the next set of values.
Data remaining in FFT, will be cleaned according to the following guidelines:
• Removal of foreign/special characters from the FFT. Example: two commas (,,) ne xt to
each other; string of “*”’s, special characters, additional spaces etc.
• Removal of information that has already been populated in the reference data
extraction process as well as the Level 2 allocated PPO-OTD Class.This will only apply to
the item/spare itself and not to any subset, higher assembly, parts, etc.
• Removal of Property values from the FFT that have been extracted and populated to
the Property value fields in the Template.

VERSION 1.00
2.3.3 TECHNICAL VALUE STANDARDIZATION (TVS) OF PROPERTY VALUES
PiLog will standardize the values entered in templates according to ISO 8000 complaint
guidelines. The standard values to be used during cataloguing will be presented to JSL for
approval. Should there be any changes from JSL it will become JSL specific TVS rules and
values will be standardized strictly according to the approved values received from JSL. The
Value standardization process is discussed in detail in this document.
2.4 LEVEL 4 DATA ENRICHMENT

The main objective of this level is to enhance the client provided original short and ori gi nal
long text information by sourcing additional data from various resources. The characteristics
of the item are enriched in accordance with the data requirement (template) by means of
using various resources such as drawings, catalogues, and Datasheets and data repositori es
in order to supplement the missing mandatory property or characteristics data.
Additionally research is conducted on the manufacturer/Vendors website or other web
resources based on the reference data such as part numbers, model numbers, drawing
numbers provided in the original short and original long to enrich the description.
The main exercise performed at this level includes but not limited to
• Performance of research on reference numbers provided in original short and ori gi nal
long to collect additional data.
• Cross verification of data to ensure that an item meets the needs of the client through
comparison with external reference documentation, repository and or list of values.
• Cross validation of data to determine whether an item complies with an internal
regulation, requirement, specification, or imposed condition, such as data format or
source correctness.
• Provide reference URL to designate the source of data extracted and populated.
• Provide reporting on data added through enrichment process.
Notes:
1. Not all the items can be enriched using the research of data mart/repositories, Internet,
vendor portals, drawings, data sheets etc.
2. Only the items that have genuine part number, model number, drawing or re fe re nce s
can be enriched through Level-4 research. If such data or doc’s are not available e i ther
JSL on site personal will provide the information.
3. Supplement data is extracted to populate properties only from the reputed sources
such as Manufacturer or Vendor website/portal, data sheets, drawings and PiLog
repository.
4. Level 4 cataloging generates further enhancement to short and long descriptions.

VERSION 1.00
5. An item will be taken to Level-4 in an attempt to, populate as many mandatory class
properties as available and to improve the data quality.
3. DESCRIPTION GENERATION OR RENDERING

For each item/spare two different descriptions will be generated after cataloguing process is
completed, be it up to Level 3 or Level 4
These descriptions are
• Short Format Description (SFD) – 40 Characters Max (For later use in SAP)
• Purchase Order Description (POD)
These descriptions are generated by the system according to some predefined
logic/algorithm configured in the system which is known as Description Generation
Algorithm. The Users have the flexibility to modify the descriptions generated to sui t the i r
business needs. However the final Algorithm to be used should be mutually agreed by Pi Log
and JSL.
3.1 DESCRIPTION GENERATION OF RENDERING ALGORITHM

Description generation Algorithm is the logic based on which the description generator
works in the system. The logic explains how the descriptions should be generated with
specific sequences for PPO-OTD Class, each property value or reference data or FFT. SFD and
POD work on Separate Algorithms which is discussed in detail in the next section. JSL team is
expected to review the Algorithm and agree on the logic. Once agreed, the algorithm will be
applied to the description generation process in the MDPM system.
3.1.1 SHORT TEXT (SFD) GENERATION – LENGTH: 40 CHARACTERS
SFD Algorithm
SFD will be generated in the following sequence:
CLASS ABBREVIATION: OEM PART NUMBER WITH PREFIX “OEM” WITHOUT
MANUFACTURER, MANUFACTURER PART NUMBER WITH PREFIX “PN” WITHOUT
MANUFACTURER, MODEL NUMBER WITH PREFIX “M” WITHOUT MANUFACTURER,
PROPERTY VALUES WITH UOM WITHOUT PROPERTY NAME, FFT, SUPPLIER PART NUMBER
WITH PREFIX “SUPPL PN” WITHOUT SUPPLIER NAME, REFERENCE NUMBERS WITH
APPROPRIATE SUFFIXES, DRAWING NUMBER WITH PREFIX “DWG”, POSITION NUMBER WITH
PREFIX “POS”,END EQUIPMENT DETAILS WITH PREFIX “F/”
Typical SFD:
VLV GATE:PN 23675,2IN,150LB,FLANGED RF

VERSION 1.00
Notes:
• After class abbreviation colon symbol (:) will be used.
• Each value will be separated by comma symbol (,)
• After each prefix, a single space will be given to differentiate the suffix from the
value.
• No space will be given before or after comma in order to make the best use of the
available space.
• SFD will be generated in order to give a meaningful sentence. The Values entered will
not be truncated in case if the available space is not sufficient for the complete value
to appear. Either complete value will appear or the value will not appear at all.
Incomplete values will not appear.
Rules followed in SFD generation

Class:
Approved Abbreviation of the class will appear in SFD
Note: JSL should approve abbreviation for all the classes available in the dictionary.
Part Number:
OEM PN and MFR PN captured for an item will appear in the SFD. Below is the order of
sequence.
1. OEM PN with Prefix: ’OEM PN’
2. MFR PN with Prefix: ’PN’
Note: 1) OEM Name/MFR Name will not appear in SFD.
2)Multiple Part Numbers will be add if available.
Model Number:
Item Model No captured will appear in SFD with prefix ‘M:’.Manufacture name will not
appear in SFD
Property values:
All Captured Mandatory Property Value (s) +UOM will appear in SFD. Property name wi l l
not appear in SFD.
Notes: JSL to approve the mandatory properties marked as well as the sequencing of the
properties available in PPO-OTD for each class if there are any concerns
Free Format Text

The values captured in FFT will appear in SFD continually after property values without
any prefix.

VERSION 1.00
Supplier Part No:

In case Supplier part numbers are captured, then it will appear in SFD. However suppl i er
name will not appear.
Reference Numbers:
All captured Reference numbers will appear in SFD in the following sequences:
Reference numbers with prefix ‘REF’
Catalogue numbers with prefix ‘CAT’
Article number with prefix ‘ART’
Serial number with prefix ‘SER’
For equip model with prefix ‘F/M’
Note: Equip serial no and Tag/equip no will not appear in SFD.
Drawing number and Position Numbers:

Captured Drawing number(s) will appear in SFD with prefix “DWG
Captured Position number(s) will appear in SFD with prefix “POS”
Note: Revision numbers will not appear in SFD.
3.1.2 PURCHASE ORDER DESCRIPTION (POD) GENERATION
POD Algorithm
POD will be generated in the following sequence:
CLASS NAME: PROPERTY NAMES FOLLOWED BY PROPERTY VALUES AND UOM
(DEPENDS ON THE BEFORE/AFTER INDICATOR), FFT, PART NUMBER LABEL(S), PART
NUMBER(S) VALUE (OEM/MFR PN/SUPPLIER), MANUFACTURER NAME, REFERENCE
LABELS, REFERENCE NUMBER(S), MANUFACTURER NAME, DRAWING NUMBER WITH
PREFIX “DRAWING”, REVISION WITH PREFIX “REV”, POSITION NUMBER WITH PREFIX
“POSITION NUMBER”, END EQUIPMENT DETAILS WITH PREFIX “F/”
Typical POD:
VALVE GATE:SIZE 2IN, PRESSURE RATING 150LB, CONNECTION TYPE FLANGED RF,
BODY MATERIAL CS ASTM A216 GRADE WCC, OPERATED HANDWHEEL, PORT TYPE
REDUCED BORE, TRIM DISC INCONEL, SEAT SS, STEM DESIGN RISING OS&Y,
STANDARD ASME B16.5, FFT:FOR BOILER FEED WATER SYSTEM, MFR PART
NUMBER10285 VELAN, DRAWING 12359, REV 2, POSITION NUMBER 12

VERSION 1.00
Notes:
• After class colon symbol (:) will be used.
• Each set of value will be separated by comma symbol (,) followed by a space and the
next set of value will follow.
• After each prefix, a single space will be given to differentiate the suffix from the
value.
• All the values captured in any of the tabs will appear in POD. No abbreviations will be
made.
Rules followed in POD generation

Class:
Class as available in Dictionary will appear in POD followed by colon (:)
Property values:
All Captured Property Value (s) +UOM will appear in POD along with the prope rt y name s
depending on the Before/After indicator. A space will be provided between Property
name and Property value followed by UOM. A comma followed by blank space se parates
each set of Property values
Note: JSL should approve the Before/After indicator for all properties In the dictionary.
Free Format Text :

The values captured in FFT will appear continuously after the property values with a prefix
FFT followed by a colon (:).
Part Number(S):
All OEM/Manufacturer/Supplier Part numbers will appear in the following sequence.
1. Part number reference type (OEM part number or Supplier part number etc.)
2. Part number value captured
3. Corresponding Manufacturer name
Reference Numbers:
All captured Reference numbers will appear in POD in the following sequence
1. Reference type (Model number, reference number, Serial Number etc.)
2. Reference value captured
3. Corresponding Manufacturer (If available)
Drawing number and Position Numbers:

VERSION 1.00
All Captured Drawing number(s) will appear in POD with prefix DRAWING” followed by the
value and Revision numbers with prefix “REV” followed by the value and Position numbers
with prefix “POSITION NUMBER” followed by the value.
Note:
A space will be provided between the prefix and the value for each record.
Drawing numbers, Position numbers and revisions will be separated by comma (,).
3 STANDARDIZATION
What is Standardization?
Standardization is the process of improving consistency of the property values, names,
abbreviations that are captured in the system during the cataloguing process. This process
adheres to best industry practises across the world.
Advantages of Standardization
• Standard values can be compared effectively and efficiently, therefore increasing the
possibility of duplicate identification and resolution to a higher degree. Therefore
Standardization then allows for the Possible Duplication Resolution (PDR) proce ss to
be conducted. PiLog performs PDRs in two ways:
▪ PDR-1 is the process of identifying the materials which have same Part
number/Model number and different material numbers.
▪ PDR-2 is the process of identifying materials that do not have part numbe rs
and materials that have the same mandatory properties.
▪ PDR-1 and PDR-2 will be performed after data cleansing of total received
materials.
• Improved and more effective Search functions.
• Structured Description generation and more effective purchasing.
3.1 STANDARDIZATION METHODLOGY

Effective value standardization can be achieved by following a few simple steps from the
beginning of the project. Some important steps to be followed to achieve effective value
standardization are:
• Agree on standard formats of values.
• Educate Users to increase awareness on Standard formats to be used.
• Follow approved standard formats while entering values in the system.
• Check the system for any Non-standard values at the time of capturing the data and
correct the value to the standard format.
The following section explains Standard Value detail, which will be followed for
standardization purposes.

VERSION 1.00
3.1.1 FRACTIONS
Use oblique strokes (/) when expressing fractions, e.g. 3/8 IN. Use dashes ( -) between whole
numbers and fractions, e.g., 6-1/4 IN (No spaces).
A set of dimensions involving fractions would be shown as:
WD 15 FT 1/4 IN X LG 20 FT 4-1/2 IN X HT 6 FT 8-3/8 IN
3.1.2 DECIMALS
When a dimension is expressed in decimal form and is less than one (1), place a zero
preceding the decimal point, e.g., 0.125 MM.
When a dimension is expressed in decimal form has an ending zero, like 1.20, omit the ze ro
at the end as the last digit, e.g., 1.2
3.1.3 TOLERANCE FOR UNITS OF MEASURE
The symbols “+” shall be used for Plus, “-” for Minus and “+/-“ for Plus or Minus, whe re the
tolerance value is the same, for example:
Plus 0.0003” = +0.003 IN
Minus 0.003” = -0.003 IN
Plus or Minus 0.003” = +/-0.003 IN, for the same tolerance value.
Plus 0.003” or Minus 0.001” = +0.003 TO -0.001 IN
4 APPROVED STANDARDIZATION PRINCIPLES AND

GUIDELINES
4.1.1 SIZES/DIMENSIONS
There are many Templates where the Attribute SIZE/DIMENSIONS is split up into separate
Attributes. In these cases the order, in which the dimensions are to be reflected i n the l ong
description/Order Description is to be governed by the PPM Attribute order.
There are however, some templates where the Attribute SIZE/DIMENSIONS, is not spl i t up,
due to the nature of the Object. In such instances, the dimensions are captured in a string. In
order to ensure a standard format when referencing size/dimensions, list the val ue s i n the
following sequence:
• ID X OD
• ID X OD X LG
• ID X OD X THK
• ID X OD X LG X THK
• DIA X LG
• DIA X THK
• DIA X HT X DP
• DIA X LG X THK

VERSION 1.00
• DIA X DP .………………(Preferably HT should be used for DP)

• DIA X DP X THK…….. (Preferably HT should be used for DP)
• SQ X LG for (WD 10 X LG 300 X HT 10)
• SQ X THK for (WD 10 X LG 10 X THK 5)
• SQ X HT for (WD 10 X LG 10 X HT 25)
• WD X LG
• WD X LG X HT
• WD X LG X HT X DP
• WD X LG X THK
• WD X LG X HT X THK
• WD X HT X DP
Examples:
Source Value UOM
20MM ODX10MM IDX50MM LG ID 10 X OD 20 X LG 50 MM
45MM ODX 25MM IDX 12IN LG ID 25 MM X OD 45 MM X LG 12 IN N/A
Where - the UOM is the same for the total string of values, as per the example above,
always capture the UOM in the UOM Field and remove the UOM from the values.
Where - the UOM is different, as per the second line of the example above, always leave the
UOM in the value string and capture N/A (Not Applicable) in the UOM Field.
The UOM is written with a space between the values in all applications to avoid any possible
confusion.
When - multiple dimensions (Tapered/Reducing sizes) are captured in a string, each value
will be enclosed using parenthesis () followed by the next value dimension. For example:
Sleeve: OD 12 MM large end and 8 MM Small end x ID 10 MM large end and 6 MM Small end
x 80 MM long.
When - multiple dimensions (Tapered/Reducing sizes) are captured against an Attribute,

where not part of a string, parenthesis () must be omitted.
When - dealing with (Tapered/Reducing sizes) which are not adjustable e.g. Bushes,
Reducers, Sleeves, etc. Always capture the values from the largest to the smallest with Dash
(-), No spaces to separate the numerals, in order to maintain THE SAME standard.
Examples:
Source Value UOM
OD12MM/OD8MMXID10MM/ID6MMXLG80M
ID (10-6) X OD (12-8) X LG 80 MM
M
OD2MM/OD4MMXID1/2IN/ID3/4INXLG50MM ID (3/4 TO 1/2) IN X OD (4-2)MM X N/A

VERSION 1.00
LG 50MM
10MM X 6MM 10-6 MM
Note: When dealing with reducible values, e.g. Clamps, Heat shrinkable Sleeving, etc. Always
capture the values from the largest to the smallest with Dash (-) separating the numerals, i n
order to maintain THE SAME standard.
4.1.2 ELECTRICAL RATINGS
The UOM field must be utilized, as electrical values/ratings are also captured as UOM’s,
however the UOM field will remain N/A, when there are different UOM values in a string. Al l
values will be considered as AC values unless particularly specified as a DC val ue , and the n
just captured as “V” or “A”. See NOTE next page.
Examples:
Source Value UOM
120VAC 120 V(used to be VAC)
14A 14 A
120VAC15A 120 V 15 A N/A
180VDC 20A 180 V DC 20 A N/A
Since there are a number of variations reflecting electrical values for the different attributes,
the following Guidelines are given, bearing in mind, that a logical, non-confusing approach
should always be the key to ensure viable standards.
Note!
In order to enhance a more effective Duplicate Resolution Report (DPR 2) the de ci si on was
made to deviate from capturing Volt and Amp alternating current on its own in a UOM fi e l d
as either “VAC”, “V AC”, “A AC” as was the use in the past. A value will be taken as AC i f i t i s
not specified as DC and therefore then just be captured as either (“V”) volt or (“A”) amp
respectively. The UOM “V AC” (Volt alternating current) will be used in the val ue fi e ld onl y
when and if a DC value is also present to distinguish the two values. The same is appl i cable
to AMP ratings. Take careful note of the use of these UOM’s throughout the various
examples following here. The “DC” UOM’S “V DC” and “A DC” May be used alone in the
UOM field.
Also note that the UOM “VAC” as used in the past with no spaces between the letters
actually represents VOLT-AMP CAPACITANCE and not VOLT ALTERNATING CURRENT (which i s
“V AC” with the spacing).
4.1.2.1 GENERAL ORDER OF ELECTRICAL VALUES:
Volts – Amps – Phase – Watts - VA Rating – Horsepower - Ohm, etc) Hertz last.
e.g. - 220/110 V 6 A 3 PH 60 W 3 KVA 5 HP 10 OHM 50/60 HZ

VERSION 1.00
AC values are always captured before DC values.

Typical examples are given below for writing electrical rating values in a standard format.
These are the most commonly used electrical value strings and are given as guidelines only.
Examples: Ratings values
Source Value UOM
120VAC/120VDC 120 V AC/DC
220/110VAC 6A, 125VDC 4A 110/220 V AC 6 A; 125 V DC 4 A N/A
100VDC, 120VAC 120 V AC; 100 V DC N/A
220/110V 6A 3PH 50/60HZ 110/220 V 6 A 3 PH 50/60 HZ N/A
Note! Generally it is not a requirement that Hertz be captured for South African clients,
unless it is a special cycle range, outside the 50-60 Hz ranges. However for some client’s,
Hertz must always be captured.
Range Values: are indicated by means of a dash (-), Be sure that it is in fact a range and not a
rating.
Examples:
Source Value UOM
120VAC 6A to 160VAC 1A 120-160 V 6-1 A N/A
110/220VAC 6A, 125VDC 4A 110-220 V AC 6 A; 125 V DC 4 A N/A
120 to 440VAC 6 to 2A 120-440 V 6-2 A N/A
160VAC 1A to 120VAC 6A 120-160 V 6-1 A *** N/A
KEEP THE RELATING AMPS TO THE VOLTAGE IN THE SAME RESPECTIVE ORDER AND NOT IN
PARTICULAR FROM SMALL TO BIG LIKE EXAMPLE ABOVE – SO THE SMALLER VOLTAGE
“120” IS CAPTURED FIRST AND SO MUST IT’S RELATED “6A” BE CAPTURED FIRST, DO NOT
FOR EXAMPLE CAPTURE 1 A FIRST BECAUSE IT IS THE SMALLER AMPERAGE IN THIS CASE.
KEEP THE SEQUENCE REGARDLESS OF WHETHER THE AMPERAGES ARE THE BIGGER OR
SMALLER VALUE IN A STRING TYPE OF VALUE LIKE THIS ABOVE.
When different AC or DC Values with the same AMPS are given always indicate lowest
value first, and capture:
Examples:
Source Value UOM
120VAC 5A, 240VAC 5A 120/240 V 5 A N/A
120VDC 5A, 240VDC 5A 120/240 V DC 5 A N/A

VERSION 1.00
4.1.2.2 EXCEPTIONS:
• Use the word TO where different values or UOM’s are indicated: Example
600 V TO 1.2 KV
• When indicating a range from a negative to a positive value,
• When fractions are used as the value.
Examples: (Not electrical values, but shown here for the usage of the word “TO”)
Source Value UOM
negative 10 PSI to positive 200 -10 TO 200
PSI
PSI
1/2 - 1-1/2 in 1/2 TO 1-1/2 IN
The symbol +/- is to be used where a tolerance is to be indicated and not ranges.
Note: This exception applies to all commodities, not only to electrical values.
Examples:
Source Value UOM
500 ohm +10 ohm – 10 ohm 500 +/-10 OHM
+25VDC to -25VDC -25 TO 25 V DC
minus 10 OHM to plus 10 OHM tolerance -10 TO 10 OHM
Note! +15VDC/-15VDC is not acceptable.
Rating Values: are indicated by means of a slash (/)replacing “AND”.
Examples:
Source Value UOM
120VAC 6A and 160VAC 1A 120/160 V 6/1 A N/A
110/220VAC 6A and 125VDC 4A 110/220 V AC 6 A; 125 V DC 4 A N/A
120-240-380-440VAC 6/4/3/2A 120/240/380/440 V 6/4/3/2 A N/A
When multiple electrical values are used together in a string as one rating, spaces as shown
below should separate the values from each other.
Example:
Source Value UOM
240VAC5A6VA3PH50/60 HZ 240 V 5 A 6 VA 3 PH 50/60 HZ N/A
When multiple electrical values are used together in a string, with multiple ratings, a space is
to be used as shown below to separate the values from each other and a semicolon with a

VERSION 1.00
space (;) to separate the two different ratings. (AC ratings first and then DC ratings after the
semicolon)
Example:
Source Value UOM
240VAC5A/6VA3PH50/60HZ/ 110VDC 240 V AC 5 A 6 VA 3 PH 50/60 HZ;
N/A
8A 4VA 110 V DC 8 A 4 VA
There are however now mostly templates for electrical items where the Attribute “Electrical
rating”, is split into separate Attributes, like:
• CURRENT (Normally expressed as Ampere)
• POTENTIAL (Normally expressed as Voltage)
• POWER (Normally expressed as Wattage)
• Also be aware that the UOM’s “VA” or “KVA” is an Apparent POWER rating and
should not be captured at Potential or Current rating Attributes.
When VOLTS and AMPS are 1000 and over, convert to KILO (This is a general rule excluding
for TRANSFORMERS where the value must be captured as per source, and not converted.
Examples – other than Transformers:
Source Value UOM
10,000V 10 KV
40,000A 40 KA
Example typically for Transformers:

240000/600V 240000/600 V
Note! Exception
When power (WATTS) are over and including a 1000 Watt, convert to KW (Kilowatt). Also
convert backwards if you find a value for example as 0.2 KW – capture 200 W (Watt). This is a
general rule excluding for Motors where the value must be captured as per source for
example (0.5 KW), and not to be converted.
Furthermore:
It is important to select the appropriate value from a string of values like: 380VAC 4A
220VDC 0.1A, and to populate that value against the correctly identified Attribute within the
Template.
Example:
Source Info; 380VAC 4A 220VDC 0.1A
Attribute Value UOM

VERSION 1.00
POTENTIAL 380 V AC; 220 V DC N/A

CURRENT 4; 0.1 A
Note! It is of great importance that the definitions, which appear against the attributes in
the PPM, be read and to apply the example reflected in the Guideline Column
4.1.3 MATERIAL VALUES
The material values are a very complex and critical area of information and it is found that
the information given on information tags and the stock items are not very complete and
concise. It is therefore important that the values, as noted in the Approved Material Values
Section, be captured, and VS process to follow the guidelines as listed below to add to the
existing (captured) data.
Note! Clients are to determine which material standards are to be used.

When the Attribute ‘MATERIAL’ is used by itself, the available data will be captured as a
string. Depending on the data available or supplied, values must be listed in the following
logical sequence to maintain a standard:
• BASE MATERIAL (CARBON STEEL)
• SPECIFICATION (ASTM A105)
• GRADE (GRADE B)
• PROCESS (HOT ROLLED)
• FINISH (GALVANIZED) (This sequence does not address any abbreviations to be
used)
Note! Where the Template caters for the different elements of Material as separate
Attributes, the relevant values must be populated against the appropriate Attribute and
not be left in the FFT.
Examples: (as with the abbreviations to be used)
• CS ASTM A105 GR B HOT ROLLED GALV
• BRS CR PLTD
• SS 304
• SS ASTM A182 GR 316
• SS ASTM A315 GR CF8M
• (CS ASTM A216 GR WCB) (CS for: CARBON STEEL and NOT for CAST
STEEL).
Note! Use ‘CS’ for Carbon Steel and if the Carbon Steel is a casting, capture as ‘CS CAST
and Use ‘STL CAST’ for Cast Steel - - - SEE Material abbreviation list at the back of the book
for a full list.
• CI ASTM A48 GR CL30
• MI BLACK
In order to ensure Standard Values for the MATERIAL Attributes adhere to the following
rules:

VERSION 1.00
• Use abbreviations as abbreviated per the Approved Standards abbreviation

list.e.g. Brass – BRS; Bronze–BRZ; Polytetrafluoroethylene – PTFE.
• If you do not have one please see your Standards department to obtain one.
Note: Refrain from using Element Symbols as per Periodic tables
Interpret the (/) as AND for combinations of material. E.g. STL/WHITE METAL.
• Write OR where applicable.
• Write multiple material values in alphabetical order.
• Write multiple concepts in alphabetical order, use the (;) as a separator.
The following Attributes will be used for typical example values: MATERIAL and the Object
VALVE – Attribute: TRIM:
Examples:
Attribute Source Value
Material: STEEL, BRASS, ALUM ALLOY AL ALLOY/BRS/STL
Trim: 316SS STEM & BALL, PTFE SEAT BALL/STEM SS316; SEAT PTFE
SEAT PTFE, SS 416 STEM, BRASS
Trim: BALL BRS; SEAT PTFE; STEM SS416
BALL
TRIM, DISC & SEAT F6 STELLITED, CS BONNET CS FORGED ASTME
Trim:
FORGED BONNET ASTME SA 105 SA105;DISC/SEAT F6 STELLITED
The same discipline must be applied, where multiple values are captured for Attributes l i ke :
BODY MATERIAL, SOFT GOODS, etc.
Brand Names are often used as a material value.
Example: TEFLON, GRAFOIL, KLINGERITE, etc.
Material GLASSFIBER is referred to in various forms of spelling, like FIBREGLASS, GLASS
FIBRE, etc.; the following way of writing must comply with all variants, in orde r to ge t to an
acceptable standard: GLASS FIBER.
4.1.4 PRESSURE RATINGS
Use the design pressure rating at a predetermined temperature (if available) in the attributes
of Temperature Rating on Valves.
Examples:
Source Value UOM
1600 LB @ 600 DEG C 1600 LB AT 600 DEG C N/A
1200PSI @ 200DEG C and 1200 PSI AT 200 DEG C; 1200 PSI AT 280
1200psi at 280 Fahrenheit DEG F

VERSION 1.00
Be sure ratings are associated with the correct temperature.

Pipe Schedules may sometimes be used as a rating value e.g. SCH40, SCH60, CL1,
CL2(Standardized with no spaces).
The following rules are to be followed, in order to ensure Standard Values for PRESSURE
RATING Attributes:
• Interpret the (/) as AND for combinations of ratings. E.g. BAR/PSI.
• Write OR where applicable.
• Write multiple pressure rating values in alphabetical order, e.g. 15 BAR; 96 PSI
• Keep multiple values within a concept together, use the (,) as a separator.
• Write multiple concepts in alphabetical order, use the (;) as a separator.
Examples: of standardized pressure ratings are as following:

Source Value UOM
0-30 PRSR 0-30 PSI
0-30 LBS PSIG 0-30 PSIG
0-30 PSIG 0-30 PSIG
160 LB @ 60 DEG C 160LB AT60DEG C N/A
160 PSI @ 30 DEG C, 12 BAR @ 89 DEG
160PSI AT 30DEG C; 12BAR AT 89DEG F N/A
F
Note: Celsius value first, then Fahrenheit – regardless of any of the numeral values.
DO NOT Convert PSIG, PSID or PSIA Ratings.
DO NOT Convert PSI to LB for Pressure Gauges, Switches and Transmitters.
DO NOT Convert PSI to PSIG (Use as per Client’s original values.)
4.1.5 THREADS AND CONNECTIONS
4.1.5.1 FASTENERS: (BOLTS, SCREWS AND NUTS)
Fastener Threads: The data pertaining to screw/bolt threads are found in many different
ways and/or formats. It is therefore necessary to give some guidelines to ensure Value
Standards for fastener threads in general.
The general indicators for Thread Designations are as following:
• THREAD DIRECTION e.g. LEFT HAND - LH (No symbol required for right hand thread).
• THREAD SERIES SYMBOL e.g. UNC, UNRC, UNF, UNRF, UNEF, and UNREF.
• THREAD CLASS SYMBOL e.g. CLASS FIT.
• NUMBER OF THREADS PER INCH e.g. TPI
• FEMALE THREAD e.g. F

VERSION 1.00
• MALE THREAD e.g. M

• METRIC THREADS e.g. M10, etc.
• METRIC THREAD PITCH e.g. PITCH SIZE
Threads per Inch (TPI) is a Standard on all Unified Coarse-Thread Series (UNC; UNRC) and
Unified Fine-Thread Series (UNF; UNRF) and not used as a UOM for the Attribute, THREAD i n
these cases. Use the TPI as the UOM, when only the number of threads is supplied.
A typical example and breakdown of how thread data may be found is: LH1/4 IN-20UNC-2A,
• LH = if Left Hand (No symbol required for right hand thread).
• UNC = Thread series (Unified Coarse thread).
• 2A = Thread class symbol (A = External Tread and B = Internal Thread)
• 20 = Number of Threads Per Inch (TPI).
• 1/4 IN = Nominal Size. (Also called thread size or diameter – but not pitch)
This means that the data may have to be split, where the Template for an Object has
separate Attributes for SIZE/DIMENSIONS and for THREAD.
Examples: Typical formats to capture Values for the Attribute, THREAD from the above.
Source Value UOM
1/4-20UNC-2A 20UNC-2A (thread only) N/A
1/4-UNC 20UNC-2A (thread only) N/A
M10-1.5 PITCH 1.5 (thread only) MM
The Nominal Dimension of the thread is not captured in the Value Field wi th the Attri bute
THREAD; this must be captured as the value for the Attribute SIZE/DIMENSIONS, as
following:
Examples: Typical formats to capture Values for the Attribute, SIZE/DIMENSIONS from the
example mentioned above.
Source Value UOM
1/4-20UNC-2A 1/4 (size only) IN
1/4-UNC 1/4 (size only) IN
M10-1.5 PITCH M10 (size only) N/A
Examples: Typical formats to capture Values for the Attribute THREAD, where the templates
are not split, from the example mentioned above.
Source Value UOM
1/4-20UNC-2A 1/4 IN-20UNC-2A N/A
M10-1.5PITCH M10-1.5 N/A
1-1/4 12 TPI 1-1/4 IN-12 N/A
Where the thread type is not indicated and the tread size and TPI is indicated, the data must
be captured as per the last line in example above, to avoid any confusion.

VERSION 1.00
Note! Thread sizes like: 10-32 x 5/8, 4-40 x 7/8, etc. indicate the thread size x thread
length. In these cases the thread size must be captured as NO 10-32 or NO 4-40 and must
not be split.
4.1.6 PIPE AND TUBE FITTINGS: (ADAPTORS, ELBOWS, TEES, ETC.)

General Basic Rules: The information reflecting in the source data from the vari ous cl i e nts
vary substantially from client to client and also in the different sources. It is therefore
necessary to define some standard principles to reflect the data in a standard format wi thi n
the values field of the catalogue. Therefore, for combinations, always:
• Write reducing sizes/dimensions from the largest to the smallest
• Write male and female connections with male first
• Write male and female sizes/dimensions with male first
• Write taper and parallel thread with parallel first
• Specify left hand thread as LH, right hand is not specified
• If there is only male thread, do not specify the MALE, (This is an accepted norm
in the industry.)
• When male thread stands alone, do not specify, generally accepted
• The term TREADED (abbreviated THD) is to be used for SCREWED
• Nominal Bore (NB) or Bore Nominal (BN) should always be written as NB
• Nominal Diameter (ND) or Diameter Nominal (DN) should always be written as
DN
Note! In plumbing pipe size is referred to as nominal pipe size - NPS, or "Nominal Pipe
Size". The metric equivalent is called DN or "diameter nominal". The metric designations
conform to International Standards Organization (ISO) usage and apply to all plumbing,
natural gas, heating oil, and miscellaneous piping used in industry and buildings. Note!
(The above value has been altered from ND to DN for this reason also.)
Connection Threads
When referring to screwed (threaded) fittings, the following guidelines are given to ensure a
value standard in the cataloguing system.
If the CONNECTION is not a separate attribute from SIZE/DIMENSIONS, the value is capture d
as following:
• MALE X SIZE
• FEMALE X SIZE
Examples:
Source Value Abbreviation UOM
1 1/2IN MALE PIPE THREAD NATIONAL PIPE TAPER 1-1/2 NPT 1-1/2 IN

VERSION 1.00
PIPE THREAD FEMALE 1-3/4IN FEMALE NATIONAL PIPE TAPER 1-3/4 FNPT 1-3/4 IN
If SIZE/DIMENSIONS and CONNECTION are separate attributes, and the ends are different:
• The Attribute CONNECTION should be populated as following:
• MALE X INDUSTRY CONNECTION TYPE.
• FEMALE X INDUSTRY CONNECTION TYPE
Examples:
Source Value Abbreviation UOM
1 3/4IN FEMALE PIPE THD & 1 1/2IN MALE NATIONAL PIPE TAPER X
NPT X FNPT N/A
PIPE THD FEMALE NATIONAL PIPE TAPER
BRITISH STANDARD PIPE X
1ST END 1 1/2IN BSP MALE, 2ND END 1 3/4IN
FEMALE BRITISH STANDARD BSP X FBSP N/A
BSP FEMALE
PIPE
AND The Attribute SIZE/DIMENSIONS should be populated as following:
Source Value UOM

1 3/4IN FEMALE PIPE THD & 1 1/2IN MALE PIPE THD 1-1/2 X 1-3/4 IN
1ST END 1 1/2IN BSP MALE, 2ND END 1 3/4IN BSP FEMALE 1-1/2 X 1-3/4 IN
Note! Ensure the sizes associate with the correct connection, when the Attribute Size/Dimensions
are to be populated with its value. The sizes are to be in same order as the connection types in
the strings.
4.1.7 ATTRIBUTE,- CONNECTION TYPE:

Various combinations of thread types exist, especially where the inlet and the outlet
connection types are different. Some guideline examples are given to enhance standard
value inputs:
4.1.7.1 PRINCIPLE REMINDER FOR VALUE STANDARDIZATION:
• Always bear in mind that the purpose of this exercise is to get the values per
Object / Qualifier (Class) and Attributes (Properties) grouping to follow the same
disciplined order.
• Use these guidelines, experience and logical reasoning to achieve this objective.

VERSION 1.00
4.2 OBJECT SPECIFIC RULES

4.2.1 HOSE ASSEMBLIES
Where the thread data for Connection sizes in the original source is given as e.g. 1-
1/16-12 or Diameter 1-1/16in thread x 12 threads per inch, etc., the Connection size
must be populated as following:
Example:
Source Value UOM
1-1/16-12 1-1/16 IN-12 N/A
Diameter 1-1/16in thread x 12 threads per inch 1-1/16 IN-12 N/A
1/4-18 1/4 IN-18 N/A
4.2.2 NIPPLE: PIPE

Both ends threaded- one end male parallel and the other end taper:
Example:
Source Value UOM
PARALLEL THREAD M-TAPERED THREAD M THD (PARALLEL X TAPER) N/A
BSPP M-BSPT M BSPP X BSPT N/A
4.2.3 ELBOW: TUBE

One end 37 deg flared swivel, with the other end 37 deg flared.
Example:
Source Value UOM
37 DEG FLARE SWIVEL X 37 DEG SWIVEL (FLARE SWIVEL X SWIVEL) 37 DEG
One end 37 deg flared female swivel and the other end flared male:
Example:
Source Value UOM
37 DEG MALE FLARE SWIVEL AND 37 DEG FLARE (MALE X SWIVEL
DEG
FEMALE FLARE SWIVEL FEMALE) 37

VERSION 1.00
4.2.4 HOSE ASSEMBLIES: CONNECTION 1

Examples: (The same will apply for Connection 2.)
Source Value UOM
METRIC FEMALE SWIVEL ELBOW 90 SWIVEL ELBOW 90 DEG FEMALE METRIC N/A
FEMALE SWIVEL METRIC ELBOW 90 SWIVEL ELBOW 90 DEG FEMALE METRIC N/A
JIC FEMALE STRAIGHT SWIVEL JIC SWIVEL FEMALE STRAIGHT N/A
12S STRAIGHT METRIC FEMALE SWIVEL SWIVEL METRIC FEMALE STRAIGHT 12S N/A
Note! The above examples are key principles and must to be used as guidelines for all
types of pipe, tube and hose connectors.
When a tube connection, with a nut and ferrule is described, the connection value is,
COMPRESSION.
Below is some known Imperial thread type abbreviations – FEMALE is in general captured
in front of the particular kind of thread as can be seen below – “F” in the back of the abbr.
has other meanings as can also be seen below.
BSW BRITISH STANDARD WHITWORTH BSPP BRITISH STANDARD PIPE PARALLEL

BSF BRITISH STANDARD FINE BSPT BRITTISH STANDARD PIPE TAPER
UNC UNIFIED NATIONAL COARSE BSPF BRITISH STANDARD PIPE FITTING
UNF UNIFIED NATIONAL FINE NPS NATIONAL PIPE STRAIGHT
UNEF UNIFIED NATIONAL EXTRA FINE NST NATIONAL STANDARD THREAD
UNS UNIFIED NATIONAL SPECIAL NPT NATIONAL PIPE TAPER
UNIFIED NATIONAL ROUND (ROUND
UNR FPT FEMALE PIPE TAPER
ROOT)
BSP BRITTISH STANDARD PIPE FNPT FEMALE NATIONAL PIPE TAPER
FBSP FEMALE BRITTISH STANDARD PIPE MPT MALE PIPE TAPER
4.2.5 BEARINGS
4.2.5.1 ATTRIBUTE: STYLE
The Attribute STYLE must reflect whether the Bearing is sealed or not, and to what extend i t
is sealed. This information is generally reflected in the Part Number as follows:
• 6300 ZZ - Indicates: shielded both sides. (Metal)
• 6300 Z - Indicates: shielded one side. (Metal)
• 6202 2RS - Indicates: sealed both sides. (Non Metallic)
• 6202 RS - Indicates: sealed one side. (Non Metallic)
• 6303 - Indicates: Both sides open.

VERSION 1.00
These values are to be reflected as following:

Example:
Source Value UOM
ZZ DOUBLE SHIELD N/A
Z SHIELD N/A
2RS DOUBLE SEAL N/A
RS SEAL N/A
6303 OPEN N/A
Numeric values (2 shields or 1 seal) are not to be used in the Value Field.
4.2.5.2 BEARING TYPE

The alphabetical order principle must be used for the Attribute TYPE, to ensure a standard
for multiple value entries.
Example:
Source Value UOM
SELF ALIGNING, CONRAD, TAPERED CONRAD; SELF ALIGNING; TAPER N/A
4.2.5.3 BEARING: IBI NUMBERS AND MEASUREMENTS

The IBI number, for certain bearing types, are often given as two different IBI numbers, signifying the
number for the Cup- and the number for the Cone part, to make up a complete bearing. To establish
a standard for writing these numbers, and to save space, the following principle must be applied:
• Always write the IBI for the cup first. When and if they are not separated by class or
by attribute and has to be captured together. This rule applies to any other bearing
values – “CUP first” then CONE
• Use the semicolon and single space(;) as the separator between the IBI numbers and
other values.
Examples:
IBI - Source Value UOM
22020(CONE) AND 31040(CUP) CUP 31040;CONE22020 N/A
CUP 31074 AND CONE 22107 CUP 31074; CONE 22107 N/A
WIDTH - Source Value UOM
Widths is CONE 16.64 mm and CUP
CUP 12.07;CONE 16.64 MM
12.07 mm

VERSION 1.00
4.2.6 CLOTHINGAND FOOTWEAR
It is important to take note that there are many existing international standards for
the sizing of clothes and shoes of various types. In some standards, INCH (imperial) is
used and others CM’s (Metric) are used as the unit of measure (UOM). Some
manufacturers use the also known (S, M, L, XL, XXL etc.) which will by various
manufacturers be dedicated tables referring to specific chest, waist, hip, foot etc.
dimensions.
This has caused many challenges and the new European standard EN13402 se e ks to
address this problem, since it is an absolute scale and mandatory; there is no
mandatory clothing size standard in the U.S. The European Union has produce d thi s
standard EN13402 intended to replace existing standards in the member countri es.
This is not yet in common use at this stage. A few ISO standards also exist.
In order to establish a standardized method of capturing these different kinds of
received values follow the following guidelines:
4.2.6.1 SIZES
The clothing Industry generally marks the clothing sizes as highlighted in the table
below. For Standardizing purposes use the highlighted method.
Examples:
Small S
Medium M
Large L
Extra Large XL (do not capture 1XL)
Extra Extra Large, or XXL 2XL
Extra ExtraExtra Large, or XXXL 3XL
Extra ExtraExtraExtra Large, or XXXXL 4XL
Notes! 1. When the original source date contains more than one size format, e.g. 32 (102) XL,
the data must be populated in the following order: XL; 32; 102 with the UOM as N/A
when not supplied.
2. Never convert clothing sizes from centimetre to millimetres’ or meters.
If and when a UOM is supplied with the data it must be used and not be disposed of, (may
mostly be in CM)
Following is some examples of how to capture different values with and without UOM’s.
Examples:
Source Value UOM
Extra large 32, 102CM XL; 32; 102 CM N/A
2 values and the bigger with UOM 32; 102 CM N/A

VERSION 1.00
Just one value with UOM 102 CM

Smaller dimension with UOM 85 CM; 180 N/A
The same applies to all possible metric values given, and this standard also applies to all overall,
clothing, safety shoe, boots etc. Be sure not to place specific shoe STYLE types like for eg. (style
2050) as a size in the Size field. Alsotakennote that the GENDER where applicable, is always to be
captured as MENS or LADIES or UNISEX only. MALE, FEMALE and the like, is not to be used with
clothing, shoes and similar items.
Clothing Materials
In order to maintain consistency with clothing materials and the ir particular percentage blends
where available, the values must be captured as following;
A) Capture the different materials in alphabetical order with its particular percentage value after the
material, use (/) for the next material value, and when all are the same UOM capture i t i n the UOM
field.
B) When another concept with a UOM about this material is included in the string, do the same as
other values where it is distinguished with (;) and the uom’s captured in the string. J54, and si mi l ar
criteria may however be captured after an (,). There is no need to repeat the UOM PCT in a value
where more UOM’s are applicable, capture it once at the end of that particular blend.
Examples:
Source Value UOM
SUIT 100% POLYESTER POLYESTER 100 PCT
J 54 100 PERCENT COTTON COVERALL COTTON 100 PCT, J54 N/A
90 GR/ SQ METER POLYESTER 100 % POLYESTER 100 PCT; 90 G/M2 N/A
75/25 PERCENT POLYESTER AND VISCOSE BLEND POLYESTER 75/VISCOSE 25 PCT
240 G POLYESTER &COTTON 65/35 MIX COTTON 35/POLYESTER 65 PCT; 240 G N/A
This method is applicable to all objects where percentages blends and compositions are
applicable.
4.2.7 BATTERIES
4.2.7.1 SIZES/DIMENSIONS:
• For dry cell batteries can be letters e.g. AA, AAA, C, And D or codes e.g.
CR2032 for Button/Coin types.

VERSION 1.00
4.2.8 DRILLS
Drills may be:

• Imperial dimensions e.g. 1/2 IN, 3/4 IN
• Fractional dimensions e.g. 1/2 IN, 3/4 IN
• Number dimensions e.g. NO 1, NO 40, NO 60
• Metric dimensions e.g.10 MM, 25 MM or M10, M25
4.2.9 GASKETS
4.2.9.1 GASKET SIZE:
• Gaskets normally have dimensions such as WD X LG X THK or ID X OD X THK

Example: WD 50 X LG 100 X THK 2 MM or ID 3 X OD 4 X THK 1/8 IN
• If sizes are not specified, capture as per example.
Example: 50 X 100 X 2 (which resembles either WD x LG X THK or ID X OD
X THK)
* Note! This rule is applicable to all objects where unspecified dimensions like this is given
4.2.9.2 GASKET BOLT HOLES:
• Use DIA before the bolt hole size

Example: Bolt hole DIA 1/2 IN
• The quantity will always be enclosed by parenthesis ( ) if the number of
holes is specified
Example: (8) DIA 1/2 IN
• For other attribute values: Only where quantities are given together with
other values which also contains numbers/quantities, and could cause
confusion, the parenthesis ( ) rule will also apply
• Separate different hole size values, within the same value string, by a semi
colon (;). List the hole sizes from small to large
Example: (8) DIA 5; (3) DIA 8 MM
• The UOM must always be captured with the value string when there is more
than one value entered with different UOM’s and the UOM field must be
N/A.
Example:
Source Value UOM

VERSION 1.00
1 hole dia 1-1/2in and 1hole dia 40 (1) DIA 1-1/2 IN; (1) DIA
N/A
mm 40 MM
The UOM field in this instance must be N/A.
• Multiple holes of the same dimension must be captured with the number of
holes in brackets followed by the size of the holes.
Example:
Source Value UOM
6 holes dia 12 mm (6) DIA 12 MM
The UOM field in this instance must be MM (Capital letters).
• Multiple size holes, with the same UOM (Two or more different concepts, in
the same Attribute) must be captured with the number of holes in brackets
separated by a semicolon
Example:
Source Value UOM
5 holes dia 10 mm and 3 holes dia 15
(5) DIA 10; (3) DIA 15 MM
mm
The UOM field in this instance must be MM (Capital letters).
Note! This bolt hole rules also apply to other items like Flanges etc. where
applicable.
4.2.9.3 ATTRIBUTE, COLOR
When an item consist of more than one color, they will be captured alphabetically
using the (/) as a separator between the colors like BLACK/BLUE/GREEN/YELLOW
Never! Change the color code order of certain steel and other material codes like
RED/BLUE/WHITE, THE steels are stripe painted in this Specific order to be functional
to the type of steel it is. These must not be changed to alphabetical order. It wi l l be
required for you to make certain when capturing colors that it is not a code before
placing it in an alphabetical order. This is applicable to all attributes throughout.
Some clients prefer to capture the shade or tint of a color either in front or behind
the actual color, for example: NAVY BLUE and others BLUE NAVY or BROWN LIGHT –
Make certain which method is applicable to your project and be consistent with it.
4.2.9.4 ATTRIBUTE, SHAPE:
When a standard shape (e.g. round, square, rectangular, oval, oblong) can’t be used
to describe the shape of a Gasket, use IRREGULAR as the value.
Important: Approved abbreviations only, may be used in this field. Some regularly
used abbr. is RECT for Rectangular, RD for Round, SQ for Square, The rest is

VERSION 1.00
normally written in full as Triangular, Oval, Oblong, Octagonal and Irregular etc.
This general rule is valid for all objects where a shape is applicable.
4.2.10 GAS, MIXTURES
4.2.10.1 ATTRIBUTE, CONCENTRATION:
The data values for this attribute are invariably presented in many different ways,
depending on the information supplied. The mixture may consist of a number of
different gasses and their individual concentrated values. The full name or the
symbol which identifies the gasses are often used interchangeably and combi ne d i n
the same value expression as per the source.
In order to establish a standard for capturing the different supplied source

information, to enhance an ineffective DPR 2 report and not to have a lengthy val ue
description, the following rules are to be complied to:
• The appropriate symbol expressions are to utilized in place of the gas names,
• Where more than one gas is part of the concentration, the symbol
expressions must be populated in alphabetical order with its respective
concentration,
• The gas’s symbol together with its concentration value forms a concept and
must be separated by a semicolon and a space (; ).
Examples:
Source Value UOM
12% co in n2, certified +/- 2% accuracy, 12% N2, W/12 +/-2 PCT CO BY VOL
N/A
vol carbon monoxide in nitrogen CERTIFIED
CO 100 PPM; O2 17 PCT; LEL 50
100ppm CO, 50% LEL 17% O2 N/A
PCT
ARGON 75PCT CO2 25PCT AR 75/CO2 25 PCT
4.2.11 MOTORS (ELECTRICAL)
4.2.11.1 ATTRIBUTE, POTENTIAL:
The source data values for this attribute are often specified in different ways,
depending on the information supplied. In order to establish a standard for capturing
the different specified source information, the following rule must be followed:
Examples:
Source Value UOM
ARM 215: FIELD 230 VDC ROT 215; STAT 230 V DC

VERSION 1.00
ROTOR 435; STATOR 525 VAC ROT 435; STAT 525 V
When the source data values for this attribute are not specified, enter as per source
supplied.
Example:
Source Value UOM
115/230 VAC 115/230 V
90 VDC 90 V DC
Note! Exception
When capturing the Power (Wattage) of an Electrical motor, the value must be
captured as per source for example (0.5 KW), and not to be converted to 500 W
(Watt) as per the conversion for other electrical items.
4.2.12 NUTS
4.2.12.1 ATTRIBUTE, SIZE/DIMENSIONS:
Use nominal size only. Sometimes called; thread size, tube size, pipe size, stud size,
screw size or bolt size.
The diameter of a nut is the INSIDE DIAMETER, which relates to the diameter of the
bolt with which it is to be used.
All other dimensional information (thickness, distance across flats) will go to the Free
Form Text (Unless it is an attribute requirement as per the template).
Always use a delimiter (e.g. DIA, ID, OD etc) before the value when filling the
attribute of SIZE/DIMENSIONS (Unless it is an attribute requirement as per the
template).
4.2.13 O-RINGS
O-Rings are normally sized by the inside diameter and width, and are nominal si ze s.
An O-Ring gauge should be used when determining O-Ring Sizes. Never is an O-Ri ng
to be measured with a veinier, tape measure, ruler; etc.
Enrichment: (As per contract stipulations.) If there is a standard supplied, one must
cross reference this standard against the manufacturers list to acquire the correct
sizes. (Parker series numbers, Japanese G and P numbers, etc.)
Examples:
Value UOM
ID 1/2 X THK 1/4 IN
ID 15 X THK 3 MM

VERSION 1.00
ID 1/2 IN X THK 3MM N/A
4.2.14 SEALS
4.2.14.1 ATTRIBUTE, SEALING MEMBER:
The Sealing Member refers to the Lip Design of Oil Seals.

The following table identifies the most common lip designs. The lip designs below
represent those which will fill the needs of most seal requirements.
The following designations indicate the configuration of some of the sealing

members:
SINGLE LIP WIPER W/BRONZE SCRAPER

DOUBLE LIP TRIPLE LIP
SINGLE LIP, SPRING LOADED DOUBLE LIP, DOUBLE SPRING LOADED**
DOUBLE LIP, SPRING LOADED WIPER LIP DESIGN
** Take note that as in the above “SPRING LOADED” and similar values is onl y to be
captured in this manner when a particular attribute for it does not exist within the
particular client template, The value will otherwise then be split to the SPRING
LOADED attribute.
The source data values for this attribute are often specified in different ways,
depending on the information supplied. In order to establi sh a standard for capturing
the different specified source information, the following rule must be followed:
Example:
Source Value UOM
Single Lip SINGLE LIP N/A
2 Lip DOUBLE LIP N/A
3 LIP TRIPLE LIP N/A
4.2.15 SHAFTS
Shafts are a complex commodity and the sizes pertaining to the fitment of i te ms to
the shaft, like: Bearings, Gears, Impellers, etc. are critical . Therefore only the
information, which is found on the items or in available sources, must be used.
Never separate the tolerance measurement given with any dimension from the
actual measurement value. Always show the complete value as an entity, in
parenthesis () when part of a string.
Examples:
Source Value UOM

VERSION 1.00
Dia 30mm minus 0.01mm to plus 0mm x DIA (30 +0 TO -0.01) X

MM
length 50mm LG 50
Dia 30mm minus 0.01mm to plus 0.01mm x
DIA (30 +/-0.01) X LG 50 MM
length 50mm
Dia 30mm minus 0mm to plus 0.01mm x
DIA (30 +0.01) X LG 50 MM
length 50mm
The above principle will apply for all measurements where tolerances are given,
indicating that fitment is crucial.
4.2.16 SWITCH
4.2.16.1 ATTRIBUTE, CLASSIFICATION:
Values captured in this field must follow the following standard and sequence .
• CL1 DIV2 GR ABCD; CL1 DIV2 GR CDEF
• EEX IA IIC T1T4T6
4.2.17 TRANSFORMER, DISTRIBUTION
4.2.17.1 ATTRIBUTE, POTENTIAL (OR SIMILAR):
Values received from various client sources differ, like 230AC/12VDC or

230VAC:12VDC or input 230VAC output 12VDC, etc. It is therefore essential, in
order to establish a standard way of writing these different source values, for
effective duplicate resolution reports.
The following way of writing will therefore apply:
Example:
Source Value UOM
0/120/220-0/12/9V PRIM 0/120/220; SEC 0/12/9 V
PRIM 110/220 V AC; SEC 12/9
110/220 VAC:12/9VDC N/A
V DC
input 230VAC output 12VDC PRIM 230 V AC; SEC12 V DC N/A
• Also be aware that the UOM “VA” is an Apparent POWER rating and should not be
captured at Potential or Current rating Attributes.
4.2.18 VALVES
4.2.18.1 ATTRIBUTES: PIPE SIZE, PORT SIZE, ETC.:
Always capture the inlet size first, followed by the outlet size, if the values are
different. Where the inlet and outlet sizes is the same, capture the size only once . If
unknown, capture smallest first.

VERSION 1.00
Example:
Source Value UOM
INLET 3/4 IN OUTLET 1/2 IN 3/4 X 1/2 IN
OUTLET 20MM X INLET 10MM 10 X 20 MM
2 IN X 2 IN 2 IN
disciplined order.
• Use these guidelines, experience and logical reasoning to achieve this objective.
4.3 ADDITIONAL RULES

4.3.1 FREE FORMAT TEXT - (FFT)
Under no circumstances must data, which is reflected in the Original Source

descriptions, be “lost”. Therefore, it is important that:
• Information reflected in the Original Source (working description) must be
utilized in the attribute fields where applicable.
• Remaining data must be transferred to the FFT, ensuring that:
• Spelling mistakes in the Original Source data are corrected.
• Comma-space (, ) is used separate concepts.
4.3.2 THE ATTRIBUTE, TYPE-
(Means a generic kind OF ...)

It is often difficult to determine the correct value for the Attribute TYPE from the
source/data information available to you
Therefore make sure that:
• The generic value, which specifically identifies the item/object TYPE, is used. (As
specific as possible.)
• Any data/information supporting the specific TYPE data, for which an Attribute
does not exist, must be left in the FFT.
• The No Value (*****) must be used when the specific TYPE identification is not
available.
• The where used information is not used as the value for TYPE. It is reserved for
the Attribute APPLICATION.

VERSION 1.00
• Where the Attribute APPLICATION does not exist for a template, request for an
enhancement to the template, if important, or leave as is in the FFT.
• No invalid abbreviations are to be used in the TYPE value. (Don’t apply any
abbreviations just for shortening the text.) The data being captured is to be
written out in full
Note! Value presentation should always be in accordance with the respective
Object/Class/Descriptor and Property/Attribute values.Always use logical
reasoning when an item is described, as for example – “Valve seal” – that the
object will not be a “Valve”, it will be a “Seal”, because a seal cannot have a valve,
but certainly a valve can have a seal- so do not typically class this item as a VALVE –
TYPE – SEAL, it makes no sense at all.
4.3.3 THE ATTRIBUTES, SPECIAL FEATURES - V - FURNISHED ITEMS
It is most important not to get these two attributes mixed up and clearly
understand the difference between them to enhance standardization of values. In
order to achieve this, following is an explanation and some examples to the typical
attribute definitions that are applicable. Definitions may vary slightly between
some client dictionaries but the principle remains the same. Also be aware that
these illustrated below are typical classes, but variations of it may be in different
dictionaries.
Those unusual or unique characteristics or qualities of an item

SPECIALFEATURES
not covered in the other requirements and which are
(CHARACTERISTICS)
determined to be essential for identification.
The above defines it as an integral characteristic, part or issue about this item which is not a loose
object or accessory that can be either obtained or not, with the item in question. The word “WITH”
or “C/W” (complete with) in a description of an item very often causes one to think that a loose
item is involved here, which is definitely not always the case. It will be expected to understand the
item,
Example:
ITEM DESCRIPTION & CLASS ATTRIBUTE = SPECIALFEATURE
(VALUE) =HIGH BACK
OFFICE CHAIR, BLACK (if no specific other attribute in the template
LEATHER, C/WHIGH BACK…. addresses the back)
It is not a TYPE or FURNISHED ITEM just because it
OQ = CHAIR, OFFICE
states “C/W”, as the chair comes with a back, - it states
- “with a back” – it just means that it has a high back,
AND THAT makes it a feature (characteristic).

VERSION 1.00
Chair “TYPE” may have been – “OFFICE” IFthe class name has not already Qualified it as that
type.
FURNISHED ITEM/S Items furnished as accessories which are not specified

(ACCESSORIES) elsewhere.
The above defines it as accessories, (it may be loose items, tools, AND FASTENERS to secure the
item, a handle or just about anything that is not an integral part of the item in question). The
word “WITH” or “C/W” (complete with) may also be present here, but in this case the mentioned
items is in fact accessories.
Example.
ITEM DESCRIPTION & CLASS ATTRIBUTE = FURNISHED ITEM
(value) =TAPERLOCK BUSH 3020 X 100 MM
SHAFT COUPLING, FENNER, (if no specific other attribute in the template addresses the
HRC230 C/W TAPER LOCK bush)
BUSH 3020 X 100 MM …. It is not a TYPE or SPECIAL FEATURE, as this Coupling and Bush
may be obtained separately at any stage, but in this case they
OQ = COUPLING, SHAFT wish to have a particular dedicated bush 3020 design and bore
FLEXIBLE size with the item in question. Also remember that with the
shown value above – donot capture the UOM, MM in the uom
field as the 3020 value is not a MM rating but a bush
commercial number.
4.3.4 THE ATTRIBUTE, COMPRISING

This attribute is very similar to FURNISHED ITEMS but is different in the respect that it does not
describe extra accessories supplied “with” the item in question as such, but is typical l y use d wi th
SETS, KITS and various ASSEMBLY classes, where it describes “ALL” of the loose items that this cl ass
consists of.
4.3.5 MEASUREMENTS
Imperial measurements are often written in the fractional format for a commodi ty, whe re
the same measurement for that commodity is also reflected as a decimal value.
In order to establish a value standard to enhance Duplicate Resolution Type 2 resul ts more
effectively, all the Decimal values must be written to the specific fractional Imperial
equivalent value, according to the equivalent table.Capture in Decimal when not relating to
a fractional value.
Examples:
Source Value UOM
0.75” 3/4 IN
3.25IN 3-1/4 IN
.0156” 1/64 IN

VERSION 1.00
Important:
1. Under no Circumstances are Metric values to be converted to any form of
Imperial values and vice versa.
2. Where the measurement is given in different formats like, 12.7 mm (1/2 in).
Populate the Template Attribute with the Metric value and leave Imperial value,
1/2 IN, in the Free Form Text.
3. Where the Imperial value includes any tolerances, it is important to not do any
conversions as this will lead to confusion when the tolerance is to be measured,
e.g. Bore Diameters, etc.
Examples:
Source Value UOM
0.500; +0.001/-0.000 0.5 +0.001 TO -0.0 IN
0.750; +0.011/-0.000 0.75 +0.011 TO -0.0 IN
2.000 ; +0.000/-0.001 2 +0.000 TO -0.001 IN
The above principle will apply for all measurements where tolerances are given,
indicating that fitment is crucial.
Where the Imperial values from the original data indicate that the value is to be a
tolerance and not a taper value, like 2.124/2.1235, e.g. for Attributes, BORE and
BORE DIAMETER, the data must be populated as per the following examples
Examples:
Original Value Entered Value UOM
2.1235/2.124 in 2.124-2.1235 IN
(1.7505 X 1.7495) X (1.3745 X 1.375)in (1.7505-1.7495) X (1.375-1.3745) IN
(2-1/2 X 2.4995)-( 2 X 1.9995) IN (2-1/2 TO 2.4995) X (2 X 1.9995) IN
The above principle will apply for all measurements where tolerances are indicated,
and will be populated from the larger to the smaller value within the brackets, (the
value within the bracket reflects the measurement for one end only) indicating that
fitment is crucial.
Important: Where the value for Metric measurements larger than 999.999 MM is
given as Millimetres’ the value must be converted to Meters (M). Measurements
less than 1 Meter must be in Millimetres. Take note of the exceptions to this rule.
PLEASE see the conversion exceptions next page.
Examples:
Source Value UOM
2500MM 2.5 M
2501.5MM 2.502 M
2501.4MM 2.501 M
0.8M 800 MM

VERSION 1.00
4.3.5.1 TAPER VALUES (MM TO M CONVERSION EXCEPTION)

Where the metric value from the original data indicate, that the value is to be a taper
value within items, for instance taper shafts, shanks, inner tapers within objects, etc.
The data must be populated as per the following:
Examples:
Source Value UOM
1411-911mm DIA (1411-911) MM
The value may also be OD, ID, LG, WD, etc. For example:
Source Value UOM
Length 1810-890 LG (1810–890) MM
Where one of the metric values within a bracket (as per example above) is more
than 999 MM, it should be kept as MM and not to be converted to M (Meter). (Even
the 1000 MM value remains as is and not converted to 1 M)
Where all values are given as in Meter, all should remain in Meter val ue s (Unl ikel y
but not impossible to receive values like this).
4.3.5.2 OTHER CONVERSION EXCEPTIONS (MM TO M)

Timing belts and V belts are exceptions to the conversion rule (when a length is
given), where measurements must be populated as supplied by the manufacturer
and not to be converted to Meter.
Note!
Take care to identify the correct object in cases where data only specify a be l t wi th
no qualifier as per the following two instances by just being aware of the length
attribute:
a. Belt lengths, for example 1340 MM, 2040 MM, etc. is likely (but not
necessarily) to be a V Belt.
b. Extreme belt lengths like 20 Meter and 80 Meter is likely to be conveyor
belts.
Where Measurements are given in a Decimal format without indication whether it i s
a Metric or Imperial value, it must be taken as a Metric value. Also any values not i n
fractions where no UOM Abbreviations are indicated defaults to the applicable
Metric UOM Abbreviation.

VERSION 1.00
4.3.5.3 THE USE OF A WIDTH (WD) OR LENGTH (LG) WITH DIAMETERS (DIA)
The general guideline to be used when dedicating values from typical re se arch to a
dimension specification or when expected from you to determine which to use (WD,
LG or THK) with a particular round object like rings, sleeves, bushes, etc. will be as
following:
A) When the linear centreline measurement exceeds the (OD) outsi de di ameter of
the item (it is longer than the measurement of the OD) then use LG in the string.
B) When the centreline measurement is shorter than the measurement of the OD
then use WD
EXAMPLES:
Original Value Entered Value UOM Note

200 is bigger than 50
Item diameter 50 mm x 200 mm DIA 50 X LG 200 MM therefore LG is used
30 is smaller than 50
Item diameter 50 mm x 30 mm DIA 50 X WD30 MM therefore WD is used
Inside dia 1/4 in, outside dia 1- ID 1/4 X OD 1-1/2 X 6 IN is bigger than 1-1/2
IN IN, therefore LG is used
1/2 in, width 6 inch LG 6
Inside dia 1/4 in, outside dia 1- ID 1/4 X OD 1-1/2 X 1 IN is smaller than 1-1/2
IN IN, therefore WD is used
1/2 in X 1 inch WD 1
* Consult your standards department if a template does not allow you to capture
where it should be.
Note!
This is a general guideline to establish a norm but there will be deviations from this
like washers, shims and the like where the Thickness of the item is way much less than
it’s diameter, and logically therefore Thickness (THK) will always be used with these
items instead of Width or Length. Also always be well aware of the difference
between a thickness and a wall thickness when it comes to an item’s Diameters,
lengths and widths.
4.3.6 MASS/WEIGHT
There is a difference in the values between the Imperial and the Metric Ton. Some clients
differentiate between these by using the lower case (t) as the UOM for Imperial val ue s and
the upper case (T) for the Metric values.
In most cases it is not clear from the original text whether it is an Imperial or a Metric val ue .
Therefore the upper case (MT) will be used as the approved UOM for ton and wi l l be take n
as the Metric value.
Where it is clear from the text that it is an Imperial value, populate the value with the pre fi x
of Imp, with the UOM as TONNE. The uom “T” used to be acceptable but had a contradiction

VERSION 1.00
in the SI standards which we comply with, where “T” on its own is actually used for “ TESLA”
and therefore had to go this way to clear confusion on this values.
Examples:
Source Value UOM
2000 TONS 2000 MT
2000 tons, if Imperial IMP 2000 TONNE
4.3.7 METERS/GAGES
4.3.7.1 FACE SIZE:
It is generally taken that instrumentation like Meters, Gages, etc., are round in shape.
It is therefore not required to populate this Attribute or similar values as DIA 25mm.
It is however important to indicate when the instrument is not round in shape , e .g.
SQ for Square.
Examples:
Source Value UOM
25mm diameter 25 MM
3 IN wide x 4 IN long WD 3 X LG 4 IN
30 mm wide x 30 mm long SQ 30 MM
4.3.8 SPECIFICATIONS AND STANDARDS

If any Descriptions are created, edited, down loaded etc. in Lower case, all industrial
standards such as DIN, ISO, SABS, etc. should remain in Upper case.
Values for Properties, pertaining to Standards or Specifications, are often li sted as a
string of different Standard/Specification references. When this is the case, the
different references must be listed in alphabetical and/or numerical order, separated
by a Semicolon followed by a space, (; ).The spaces, separating the alpha characte rs
from the numerical characters should be deleted, to save space, except where thi s
could lead to confusion. This must also apply where only a single Value is entered.
This standardized format of capturing the value is necessary to enhance Duplicate
Resolution Type 2 actions, effectively.
Examples:
Source Value UOM
SAE100R2A; DIN20022; TEIL 2; NCB174 DIN20022; NCB174; SAE100R2A; TEIL2 N/A
SABS 776 SABS776 N/A
ISOA2-70 ISO A2-70 N/A
AISI136; ANSI198 AISI 136; ANSI 198 N/A

VERSION 1.00

disciplined order.
• Use these guidelines, experience and logical reasoning to achieve this obj ective.
4.4 SYMBOLS
Symbols are used by Valuator’s on the data capture forms or may appear in data sheets etc.,
but are not to be captured, as the system does not except odd characters like these below.
Source Value
DELTA
Y STAR
 THETA
 UM (for Micrometer or Micron) See Note Below
micron (µ); As a UOM the capital letter U was commonly used. However, it is found that
the form micrometer (µm) as a UOM UM is also used. Therefore, in order to be consistent
and to enhance effective Duplicate Resolution programs and in the light of the Standards
International (SI) accepted explanation, quote: (a metric unit of distance equal to one
millionth of a meter. "Micron" is simply a shorter name for the micrometer. In 1968 the
CGPM decided to drop the micron as an approved unit and recommend that micrometers
be used instead. Microns, however, are still in common use.), the use of the UOM U for
micron will be discontinued and be replaced by the UOM UM for micrometer.
Pound Per Square Inch (lbf/in2 or psi), will be standardized as PSI, in order to
accommodate PSIA, PSID and PSIG. Traditional symbols for pressure units used in
hydraulics and plumbing. PSI is a symbol for pound per square inch (see above). PSIG is a
symbol for pound per square inch gauge; this means that the pressure has been read from
a gauge which actually measures the difference between the pressure of the fluid and the
pressure of the atmosphere. PSIA means pound per square inch absolute, which is the
total pressure including the pressure of the atmosphere. PSID, pound per square inch
differential, is a symbol for a difference between two pressures, neither of which is
atmospheric pressure.
The following Symbols may however be used, if required, as the system wi ll accommodate
them without interference with the programming.
> Greater As
< Smaller As
4.5 UNITS OF MEASUREMENTS AND ABBREVIATIONS

It is important that reference should be made to the approved Units of Measurement and
Abbreviation tables, which are obtainable in an xls format on special request, as these tables

VERSION 1.00
are updated frequently and kept under version control in an Access format by the standards
department.
4.6 CONVERSION TABLE

(FRACTIONS/DECIMALS/MILLIMETERS)
Important: Never convert values supplied as imperial measurements to metric and vice versa
(table is informational). Also do not capture zero’s behind a value – example – 0.3750 is
captured as 0.375 or / and 6.3500 as 6.35
(Sorted small to big)

Fraction Decimal Fraction Decimal
MM MM
IN IN IN IN
1/64 0.0156 0.3969 ____ 33/64 0.5156 13.0969
1/32 0.0313 0.7938 17/32 0.5313 13.4938
3/64 0.0469 1.1906 35/64 0.5469 13.8906
1/16 0.0625 1.5875 9/16 0.5625 14.2875
5/64 0.0781 1.9844 37/64 0.5781 14.6844
3/32 0.0938 2.3813 19/32 0.5938 15.0813
7/64 0.1094 2.7781 39/64 0.6094 15.4781
1/8 0.1250 3.1750 5/8 0.6250 15.8750
9/64 0.1406 3.5719 41/64 0.6406 16.2719
5/32 0.1563 3.9688 21/32 0.6563 16.6688
11/64 0.1719 4.3656 43/64 0.6719 17.0656
3/16 0.1875 4.7625 11/16 0.6875 17.4625
13/64 0.2031 5.1594 45/64 0.7031 17.8594
7/32 0.2188 5.5563 23/32 0.7188 18.2563
15/64 0.2344 5.9531 47/64 0.7344 18.6531
1/4 0.2500 6.3500 3/4 0.7500 19.0500
17/64 0.2656 6.7469 49/64 0.7656 19.4469
9/32 0.2813 7.1438 25/32 0.7813 19.8438
19/64 0.2969 7.5406 51/64 0.7969 20.2406
5/16 0.3125 7.9375 13/16 0.8125 20.6375
21/64 0.3281 8.3344 53/64 0.8281 21.0344
11/32 0.3438 8.7313 27/32 0.8438 21.4313
23/64 0.3594 9.1281 55/64 0.8594 21.8281
3/8 0.3750 9.5250 7/8 0.8750 22.2250
25/64 0.3906 9.9219 57/64 0.8906 22.6219
13/32 0.4063 10.3188 29/32 0.9063 23.0188
27/64 0.4219 10.7156 59/64 0.9219 23.4156
7/16 0.4375 11.1125 15/16 0.9375 23.8125
29/64 0.4531 11.5094 61/64 0.9531 24.2094
15/32 0.4688 11.9063 31/32 0.9688 24.6063
31/64 0.4844 12.3031 63/64 0.9844 25.0031
1/2 0.5000 12.7000 1 1 25.4000
Material abbreviations

VERSION 1.00
NB - all materials shaded in this darker color is where the abbreviation is not used in general
(please make your own additional comments in the specifics / deviations column where
appropriate and as per the information received from our quality or standards departments
ABBR MATERIALS - APPROVED ABBREVIATIONS SPECIFICS / DEVIATIONS FROM USING ABBR

ABS ACRYLONITRILE BUTADIENE STYRENE PLASTIC
ACSR ALUMINUM CONDUCTOR STEEL REINFORCED
AG SILVER
AL ALUMINUM (ALUMINIUM )
AL ALLOY ALUMINUM ALLOY
APL ALUMINUM POLYETHYLENE LAMINATE
AS ALLOY STEEL
ASB ASBESTOS
AU GOLD
BMS BRIGHT MILD STEEL
BRS BRASS
BRS DZR BRASS DEZINCIFICATION-RESISTANT
BRZ BRONZE
C CARBON
CAF COMPRESSED ASBESTOS FIBER
CD CADMIUM
CI CAST IRON
CPE CHLORINATED POLYETHYLENE (CABLE JACKET)
CPVC CHLORINATED POLYVINYL CHLORIDE
CR CHROME
CR CHROMIUM
CRMO MOLYCHROME
CRMO CHROMEMOLY
CRS CHROME STEEL
CS CARBON STEEL
CSM CHEMICAL SAFETY MATERIAL
CSS CAST STAINLESS STEEL
CPPR COPPER
CPPR
WROUGHT COPPER / (WROT COPPER)
WROUGHT
CVS CHROME VANADIUM STEEL
DI DUCTILE IRON
DI DUCTIBLE IRON
EIPS EXTRA IMPROVED PLOUGH STEEL
EP ETHYLENE PROPYLENE
EPDM ETHYLENE PROPYLENE DIENE MONOMER
EPM ETHYLENE PROPYLENE RUBBER
EPR ETHYLENE PROPYLENE RUBBER
EPT ETHYLENE PROPYLENE TERPOLYMER

VERSION 1.00
EPTFE EXPANDED POLYTETRAFLUOROETHYLENE

ETFE ETHYLENE-TETRAFLUOROETHYLENE
ETHYLENE VINYL ACETATE OR POLYETHYLENE
EVA
VINYL ACETATE
FE IRON (Ferrum, Ferrite)
FEP FLUORINATED ETHYLENE PROPYLENE
FKM FLUORINATED ELASTOMERS
FLUOROELASTOMERS EG. FLUORO CARBON
FPM
RUBBER
FRAS FIRE RESISTANT ANTISTATIC
FRP FIBER REINFORCED POLYMER
FST FORGED STEEL
GE GERMANIUM
GI GALVANIZED IRON
GLASS
FOR: ALL VARIATIONS OF FIBER GLASS MATERIALS
FIBER
GMS GALVANIZED MILD STEEL
GRP GLASS REINFORCED PLASTIC
GS GALVANIZED STEEL
HCS HIGH CARBON STEEL
HDPE HIGH DENSITY POLYETHYLENE
HDPP HIGH DENSITY POLYPROPYLENE
HDPU HIGH DENSITY POLYURETHANE
HG MERCURY
HYDROGENATED ACRYLONITRILE-BUTADIENE
HNBR
RUBBER
HRS HOT ROLLED STEEL
HS HASSIUM
HSS HIGH SPEED STEEL
HTMAS HIGH TENSILE MICROALLOYED STEEL
HIGH CARBON SPRING STEEL WIRE
HTMB
IDENTIFICATION
HTS HIGH TENSILE STEEL
IRON IRON
LDPE LOW DENSITY POLYETHYLENE
LLDPE LINEAR LOW DENSITY POLYETHYLENE
LTS LOW TENSILE STEEL
MG MAGNESIUM
MGO MAGNESIUM OXIDE
MI MALLEABLE IRON
MN MANGANESE
MO MOLYBDENUM; MOLY
MPTFE MULTIFILL POLYTETRAFLUOROETHYLENE
MS MILD STEEL

VERSION 1.00
NITRILE BUTADIENE RUBBER (ACRYLONITRILE

NBR
BUTADIENE RUBBER)
NBR ACRYLONITRILE-BUTADIENE RUBBER
NI NICKEL
NICRFE NICKEL CHROME FERRETIC
NIMH NICKEL-METAL-HYDRIDE
OPVC ORGANIC POLYVINYL CHLORIDE
P PHOSPHORUS
PAC POLYACRYLONITRILE
PB LEAD
PBF PERMA BOND FIBERGLASS
PBS POLYBUTADIENE STYRENE
PBT POLYBUTYLENE TERAPHTHALATE
PBTB POLYBUTYLENE TERAPHTHALATE POLYMER
PC POLYCARBONATE
PE POLYETHYLENE
PEEK POLYETHER ETHER KETONE
PES POLYETHERSULFONE
PET POLYETHYLENE TEREPHTHALATE
PFA PERFLUOROALKOXY
POM POLYOXYMETHYLENE
PP POLYPROPYLENE
PPF PRECOMPRESSED POLYURETHANE FOAM
PPH POLYPROPYLENE HOMOPOLYMER
PPS POLYPHENYLENE SULPHIDE
PS POLYSTYRENE
PSC POROUS SILICON CARBIDE
PSF POLYESTER STAPLE FIBER
PT PLATINUM
PTFE POLYTETRAFLUOROETHYLENE
PTFEC PROPYL TRIFLUOROETHYL CARBONATE
PTMEG POLYTETRAMETHYLENEETHERGLYCOL
PU POLYURETHANE
PV POLYVINYL
PVA POLYVINYL ACETATE
PVC POLYVINYL CHLORIDE
PVDC POLYVINYLIDENE CHLORIDE
POLYVINYLIDENE DIFLUORIDE ALSO
PVDF
POLYVINYLIDENE FLUORIDE
PVS POLYVINYL SILOXANE
RH RHODIUM
RPTFE REINFORCED POLYTETRAFLUOROETHYLENE
RTFE REINFORCED POLYTETRAFLUOROETHYLENE
SBR STYRENE BUTADIENE RUBBER
SG STL SPHEROIDAL GRAPHITE STEEL

VERSION 1.00
SGI SPHEROIDAL GRAPHITE IRON

SI SILICON AND SILICONE
SIC SILICON CARBIDE
SN TIN
SS STAINLESS STEEL
STL STEEL
SWA SINGLE WIRE ARMOR
TFE TETRAFLUOROETHYLENE
TI TITANIUM
TRS TOUGH RUBBER SHEATHED
UHMWPE ULTRA-HIGH MOLECULAR WEIGHT POLYETHYLENE
UPVC UNPLASTICIZED POLYVINYL CHLORIDE
V VANADIUM
FOR: VELLAMOID AND ALL VARIATIONS OTHER
VALLUMOID
THAN VALLUMOID
WC TUNGSTEN CARBIDE
WI WROUGHT IRON (WROT IRON)
WS WROUGHT STEEL (WROT STEEL)
XLPE CROSS LINKED POLYETHYLENE
XSBR CARBOXYLATED STYRENE BUTADIENE RUBBER
ZN ZINC
ZR ZIRCONIUM
4.7 STANDARD THREAD PITCH TABLE

IMPERIAL THREADS PER INCH
INCH SIZE BSW BSF UNC UNF BSPF BSPT NPS / NPT ME
1/16" 60 TPI 27 TPI
3/32" 48 TPI
1/8" 40 TPI 40 TPI 28 TPI 27 TPI 40
5/32" 32 TPI 40
3/16" 24 TPI 32 TPI 40
7/32" 24 TPI 28 TPI 40
1/4" 20 TPI 26 TPI 20 TPI 28 TPI 19 TPI 18 TPI 40
9/32" 20 TPI 26 TPI 32
5/16" 18 TPI 22 TPI 18 TPI 24 TPI 32
7/16" 14 TPI 18 TPI 14 TPI 20 TPI 26
9/16" 12 TPI 16 TPI 12 TPI 18 TPI
5/8" 11 TPI 14 TPI 11 TPI 18 TPI 14 TPI
11/16" 11 TPI 14 TPI
3/4" 10 TPI 12 TPI 10 TPI 16 TPI 14 TPI 14 TPI

VERSION 1.00
7/8" 9 TPI 11 TPI 9 TPI 14 TPI 14 TPI

1" 8 TPI 10 TPI 8 TPI 12 TPI 11 TPI 11-1/2 TPI
1-1/8" 7 TPI 9 TPI 7 TPI 12 TPI
1-1/4" 7 TPI 9 TPI 7 TPI 12 TPI 11 TPI 11-1/2 TPI
1-3/8" 6 TPI 8 TPI 6 TPI 12 TPI
1-1/2" 6 TPI 8 TPI 6 TPI 12 TPI 11 TPI 11-1/2 TPI
1-5/8" 5 TPI 8 TPI
1-3/4" 5 TPI 7 TPI 5 TPI 11 TPI
4-1/2
1-7/8" TPI 7 TPI
4-1/2 4-1/2
2" TPI 7 TPI TPI 11 TPI 11-1/2 TPI
4-1/2
2-1/4" 4 TPI 6 TPI TPI 11 TPI
2-1/2" 4 TPI 6 TPI 11 TPI 8 TPI
3-1/2
2-3/4" TPI 6 TPI 11 TPI
3-1/2
3" TPI 5 TPI 11 TPI 8 TPI
3-1/4
3-1/4" TPI 5 TPI 11 TPI
3-1/4 4-1/2
3-1/2" TPI TPI 11 TPI 8 TPI
4-1/2
3-3/4" 3 TPI TPI 11 TPI
4-1/2
4" 3 TPI TPI 11 TPI 8 TPI
METRIC PITCH
SIZE PITCH MM BA SIZE PITCH MM
M2 0.4 16 0.19
M2.2 0.45 15 0.21
M2.5 0.45 14 0.23
M3 0.5 13 0.25
M3.5 0.6 12 0.28
M4 0.7 11 0.31
M4.5 0.75 10 0.35
M5 0.8 9 0.39
M6 1 8 0.43
M7 1 7 0.48
M8 1.25 6 0.53

VERSION 1.00
M9 1.25 5 0.59
M10 1.5 4 0.66
M11 1.5 3 0.73
M12 1.75 2 0.81
M14 2 1 0.9
M16 2 0 1
M18 2.5
M20 2.5
M22 2.5
M24 3
M27 3
M30 3.5
M33 3.5
M36 4
M39 4
M42 4.5
M45 4.5
M48 5
M52 5
M56 5.5
M60 5.5
IMPORTANT! (METRIC) This is a list of Standard diameters with their particular thread pitches – it
does not mean that you may not find for example a M36 with a 2 MM pitch (normally 4 MM).
Capture the pitch with the diameter as given and do not change it to the standard thread for that
DIA. It remains a METRIC thread and will also be captured M36-2 All METRIC threads are to be
preceded with the “M” even if not on this list –specials remains metric threads.
4.7.1 UNIT OF MEASURES (UOM)

UOM abbreviations will be according to the ISO standard. Only deviation will be that ALL
abbreviations will be in capital letters.
Unit of measure plays a vital role during procurement, hence accurate industry practiced
UOM need to be used while cataloguing the materials. Normally PiLog uses International
System of Units (SI) to describe the item and its characteristics, expect for the Commodi ti es
mentioned in the below table. The same SI units will be followed during catal ogui ng of JSL
spares, however if JSL desires to use other systems (such as CGS system, FPS system or other
systems) for certain commodities, PiLog should be informed of such specific commodities, in
the specific cases PiLog will use JSL suggested UOMs instead of SI UOMs.
Below are sample commodities demonstrating the SI Units system and its respective
equivalent Units in other systems. The commodities specified in the below table use either
SI or other Measurements specified, JSLwill need to confirm from the below table which of
the UOMs are correct for the commodities mentioned.

VERSION 1.00
Note: JSL spare parts data will use SI UOMs for all measurements except nominal diamete rs
of pipe, pipefittings, and values, which shall be expressed in “inches”.
Commodities SI Units CGS/FPS/British Units

Valve Sizes DN Inch
Pipe Sizes DN Inch
Pipe Lengths Meters Feet
Cable Lengths Meters Feet
Oils/Liquids QTY Liters Gallons
Tube Lengths Meters Feet
Chain Lengths Meters Feet
Weight Units Kilo Grams Pounds
Velocity Meters Per Second Feet per Second
Force Newton Dynes
Heat Calories Joules
Distance Kilo Meters Miles
Power Watts Horse Power
5 MDPM WORK FLOW
STEP 1 : Upload data to MDPM.

STEP 2 : Data manager will assign the work to Domain experts for class allocation.
STEP 3 : After allocation of classes Data Manager will assign the work to Cataloguers.
Cataloguers extract reference data and also Property values from the source
description and cataloguing will run all the Quality Verification (QC) tools.
STEP 4 : Data Manager will assign the catalogued items for QC.
STEP 5 : After completion of QC, Data Manager will prepare the batch of these items and wil l
check consistency across the whole batch.
STEP 6 : Data manager will release the batch in MDPM and will notify the client to review the
items.
STEP 7 : JSL Data Manager will retrieve the batch in MDPM and will assign the task to BU
SPOC to validate or assign to Client QC Person the descriptions.
STEP 8 : Material items are reviewed by JSL QC Personnel and are either approved or
returned to BU SPOC with rejection comments.
STEP 9 : BU SPOC will accept or return the items to PiLog based on Client QC Status.
STEP 10 : After JSL approves all the material items, PiLog will perform PDR-1 and PDR-2
PDR-1 : Potential duplicate resolution on part numbers/Model numbers.

VERSION 1.00
PDR-2 : Identify of possible duplicates across the material items, which do not have any
reference data i.e. part number or model number comparing populated mandatory
attribute values.
STEP 11 : JSL confirms potential duplicates identified by PiLog.
STEP 12 : Confirmed duplicate materials are then merged in warehouse locations by JSL and
eliminated from the ERP.
STEP 13 : After merging the resolved duplicates with Master materials, the cleansed
descriptions are uploaded into the ERP System.

MM Harmonization Document

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

MM Harmonization Document

Uploaded by

Copyright:

Available Formats

PiLog India Private Limited

MATERIAL MASTER HARMONIZATION

COPYRIGHT © 2018 PILOG

Rights to the contents of this document

Document Number PI-IND-5-04-001

Document Issue Version 1

Compiled By Koti Azmira

Effective Date 02 February 2019

Issue Date 02 February 2019

Controlled By Content Management Office

Electronic Media Media Media Identifier

Approval Position Name Signature Date

Doc. Issue Date Changed Chapter / No of Checked by

Copy Person Organisation Distr. E-Mail

1.2 LEVELS OF CATALOGUING

1.2.1 LEVEL 1: REFERENCE DATA EXTRACTION

1.2.2 LEVEL 2: ALLOCATION OF A PPO-OTD CLASS

1.2.3 LEVEL 3: VALUE EXTRACTION

1.2.4 LEVEL 4: DATA ENRICHMENT

Level 4 is further classified into two more levels as explained below.

1.2.4.1 LEVEL 4E: ENRICHMENT VIA RESEARCH

Level 4E data enrichment is performed through external research to generate additional

1 Issue Date 5 December 2016

COPYRIGHT © 2016 PILOG

1.2.4.2 LEVEL 4M: ENRICHMENT VIA PHYSICAL WALKDOWNEXCERCISE

1.3 CATALOGUING RULES

2 Issue Date 5 December 2016

COPYRIGHT © 2016 PILOG

2 LEVELS OF DATA HARMONIZATION

3 Issue Date 5 December 2016

COPYRIGHT © 2016 PILOG

Major exercise done at this level includes but not limited to

2.1.1 GENERAL EXTRACTION RULES

• All Original component Manufacturer (OCM)/ Original Equipment Manufacturer data

2.1.2 MANUFACTURER/SUPPLIER PART NUMBER EXTRACTION RULES

• If a clearly indicated part number and a name of a known manufacturer/supplier

4 Issue Date 5 December 2016

COPYRIGHT © 2016 PILOG

• Clearly indicated manufacturers will be extracted and marked as being a manufacture r.

The following table clearly explains all the above scenarios:

5 Issue Date 5 December 2016

COPYRIGHT © 2016 PILOG

2.1.3 OTHER REFERENCE DATA EXTRACTION RULES

2.2 LEVEL 2: CLASS ALLOCATION PROCEDURE

2.3 LEVEL 3: VALUE EXTRACTION

The main exercises performed in the level include.

6 Issue Date 5 December 2016

COPYRIGHT © 2016 PILOG

2.3.1 POPULATION OF CHARACTERISTIC/PROPERTY VALUES

2.3.2 CLEAN UP OF FFT AFTER LEVEL 2 & 3 PROCESSING

COPYRIGHT © 2016 PILOG

2.3.3 TECHNICAL VALUE STANDARDIZATION (TVS) OF PROPERTY VALUES

2.4 LEVEL 4 DATA ENRICHMENT

8 Issue Date 5 December 2016

COPYRIGHT © 2016 PILOG

3. DESCRIPTION GENERATION OR RENDERING

3.1 DESCRIPTION GENERATION OF RENDERING ALGORITHM

3.1.1 SHORT TEXT (SFD) GENERATION – LENGTH: 40 CHARACTERS

9 Issue Date 5 December 2016

COPYRIGHT © 2016 PILOG

Rules followed in SFD generation

Free Format Text

COPYRIGHT © 2016 PILOG

Supplier Part No: