ISO 10303-238

CHARACTERISTICS, MATERIALS & TRACEABILITY HARMONIZATION.

Document Index

Introduction: Harmonization strategy.

Part 1: Characteristics harmonization.
Part 2: Materials harmonization.
Part 3: Process traceability proposal.
3.1 Adding Traceability Capabilities to NC-programs.
3.2 Tracing controller events.
3.3 Modeling process traceability proposal into AP238 ARM.
Part 4: Open Questions.

Part 5: Appendix:
A1: More Harmonization graphics
A2: Traceability Activity Model

Introduction: Harmonization strategy.

Characteristics are a wide concept, as each STEP-NC manufactured product may specify hundreds of
different types of characteristics. Characteristics must be defined, registered, stored, audited, and validated.

So it is important to take into account that characteristics data is BI-DIRECTIONAL, flowing from design to
manufacture and back again from manufacture to design. The downstream path in STEP-enabled manufacturing
environments is already proposed for characteristics in frameworks as AP224, AP240 and other all-inclusive APs like
223 (tables below). Therefore, characteristics specification may be “harmonized” across these APs through the
“properties” UOF.

AP224
Shape
Part Model Features
Representation
Properties Tolerances Materials
Process Administrative
Requisitions
Control Data
Process
requirement
Documents

Table I. AP224 defines administrative Data as Part Administration Data (Approval, Person & Organization and Orders).

AP240
Shape
Part Model Features
Representation
Properties Tolerances Materials
Machine tool Administrative Process Plan &
Resources Data Process Activities
Process
requirement
Documents

Table II. AP240 defines process Requirement Documents as Contracts, Controller Program, Drawings and Illustrations,
Specifications, Documents, and Machine Tool Resources as WorkStation, Work Cell, Machine.
 AP223
Shape
Part Model Features
Representation
Materials &
Properties Tolerances
composition
Casting Administrative Process Plan &
Requeriments Data Process Activities
Quality
Control Cast Process
Mold Design
Records & Simulation
Documents

Table III. AP223 “all-inclusive” protocol

AP238
Features
Tolerances
Administrative
Data
(Management
UOF)
Milling, Turning &
EDM Processes
(ISO 14649)

Table IV. Current AP238.

AP238
Features
Tolerances
Administrative
Properties
Data
(Characteristics
(Management
Data)
UOF)
Traceability Milling, Turning &
requeriments EDM Processes
Data (ISO 14649)

Table V. AP238 harmonization PROPOSAL for traceability & characteristics data.

PART 1. CHARACTERISTICS HARMONIZATION.
CAD/CAM

CAD CADD CAM CNC CONTROL

Design Detailing Path Planning Manufacturing

AP203 AP203ed2 AP238
AP224

“to be” “as is”

properties and material properties and material
characteristics characteristics
Figure 1. Bidirectional characteristics data.

Characteristics data is BI-Directional (figure 1). Once characteristics are specified in the design, (AP224 could be
used as input data for generating and configuring “to be” characteristics), these specifications would need to be
translated into the corresponding AP238, to allow machine interpretation (instructions or workingsteps needed for
characteristics recording – for example “touch_probing” instructions -). But, there are not placeholders for
automatic registering the characteristics data (“as is” data). If STEP is supposed to integrate all information and
avoid unnecessary data format translations in order to minimize information lost, characteristics data should also be
communicated back in STEP format. As a proposal, properties could be used as place holders for registered
characteristics data. That is, when a AP238 file goes to the controller, properties hold characteristics definitions (to
be), while when an AP238 comes back from the controller (after machining), same properties would hold now the
characteristic recorded data (as is).

So what its missing to harmonize characteristics into AP238?. Products characteristics could be referred to
product, and so, they could be ARM-linked with the “workpiece” entity representing the product version, in the same
fashion AP223,224,240 property_characteristics, linked to Part entity. This could be defined in the new harmonized
characteristic model as its_traceable_charectistics (figure 2), an optional unbounded set of AP223, AP224, AP240
harmonized “property” entities1.

1,66 (40,40,29,5,5,2)

its_id

global_tolerance

Workpiece its_geometry
(AP238)
clamping_positions S[0:?]

its_material
its_traceable_characteristics S[0:?]
standard_identifier
Material
(AP238) material_identifier
Property (AP224)
material_property S[0:?]

Figure 2. Proposed entry point for traceable_characteristics in AP238.

1
Valid for all document figures.
„ Green: Entities already present in the original AP model.
„ Red: New entities proposed for “Traceability & Charaectiristics” in AP238
AP harmonized entities, needing some redefinition, like “sub-typing”, or “super-typing”, for
„ Orange:
harmonization between AP, or to add new attributes to cover new information requirements.
„ Gray Attributes or entities not necessary in AP238 scope.
Figure 3 presents the proposed harmonized data model for characteristics in AP238, harmonized with the properties
concept of other manufacturing STEP APs, and adding place for specific information requirements, as for instance
characteristics properties associated with features and workingsteps.

Workpiece.its_traceable_characteristi
(INV) applied_to
Workpiece = AP238 Part

SPECIFICATION
(AP223/223/240)

property_name
STRING
Material
property_characteristic S[0:?] (AP224)
Shape_aspect/Shape_element

material_characteristic S[0:?] material_characteristic S[0:?]

Material_
property (AP224)

part_property_ characteristic S[0:?] property_

Part_ characteristic S[0:?]
property (AP224)
Property
(AP224) process_ characteristic S[0:?] property_
Process_ characteristic S[0:?]
property (AP224)

surface_ characteristic S[0:?] property_

Surface_ characteristic S[0:?]
property (AP224)

feature_ characteristic S[0:?]

Feature_
property (AP238)

property_
characteristic S[0:?]
Property_parameter (AP224)

its_feature
(ABS) manufacturing_feature (AP238)

workingstep _ characteristic S[0:?]

WorkingStep_
property (AP238)

property_
characteristic S[0:?]
Property_parameter (AP224)
its_workingstep

(ABS) workingstep (AP238)

Figure 3. Proposal for “characteristics” information requirements in AP238 (AP223,224 & 240 harmonized).
PART 2. MATERIALS HARMONIZATION.
Material properties can be regarded as an “special” kind of product characteristics. AP238 covers material properties
with the “material_property” attribute of the “material” entity included in the “workpiece” UOF (figure 4), but in a
limited fashion, as these are modeled as a set of “property parameter”.

Materials data covers both characteristics and general traceability information (as raw material lot id), so it would
necessary harmonize the material concept between APs, but also extend it by adding some extra information
requirements.

1,66 (40,40,29,5,5,2)

its_id

global_tolerance

Workpiece its_geometry

clamping_positions S[0:?]

its_material

standard_identifier

material_identifier
Material
material_property S[0:?]
property parameter

Figure 4. Material Entity from AP238 workpiece UOF.

Part & Materials properties defined in APs (223,224,238,240), if interpreted as characteristics, should be interpreted
as “as to be” data, as they are requirements and specifications used to control manufacturing conditions, but again,
in terms of AP238, there is no data placeholder for specified characteristics.

material_specification S[0:?]
SPECIFICATION
(AP223/223/240)
stock_size (AP224)
STRING
standard_identifier (AP238)
label

Material material_identifier (AP224 material_id)

(AP224) label

traced_item (traceability UOF)

label

lot_id
traced_lot (traceability UOF) LOT label
(AP223)
production_date (AP223)
date

property_characteristics S[0:?]
material_property S[0:?] = AP223/224/240 Material_ property_parameter
material_characteristics S[0:?] _property
(AP223/ material_hardness S[0:?]
AP224/ Hardness
AP240)

Figure 5. Proposed harmonized version for Material Entity in AP238.

Figure 5 show a harmonized material entity, where AP238, material_property has been added an additional level of
indirection, through Material_Property entity, to harmonize like concepts with AP223, AP224, AP240 materials.
Inclusion of greyed entitles should be discussed. For instance, material hardness could be considered as an
specialize Material property characteristic, and at NC-manufacturing level this specification could be no relevant.
Moreover, the inclusion of these entities would force to include many others.

It is important to note also here the distinction between material_identifier and standard (they identify the type of
material used: as for example in AP223: “The material_id specifies a word or group of words that make up the unique
designation of the material.”), and the added LOT/ITEM identifiers needed for traceability purposes, identifying the
batch of used material and possible the concrete unit in this material lot.

PART 3. PROCESS TRACEABILITY PROPOSAL.

3.1 Adding Traceability Capabilities to NC-Machines.

Traceability (and characteristics data) is to be automated and embedded in AP238 STEP-NC. So NC-machine
programs must provide resources (control code) to execute traceability recording. These operations or (traceability
workingsteps ??) should be configured to be traced, and therefore translated into NC-executable instructions in
AP238, to be executed by the NC-machine when manufacturing the piece (figure 6).

executable

PROGRAM WorkingSteps NC_functions (2)

STRUCTURE

Machinning_workingstep

Rapad_movement

Touch_probing (1)

WORKPLAN

Figure 6. Some Identified actions to be performed by a NC TRACEABILITY-enabled machine. (axis movement

operations)

There could be a great number of data recording operations for both traceability and characteristics that can be
performed through “Touch_Probing” workingsteps. These data recording operations(1) would include all kind of
operations which imply machine axis movement to perform the recording operation. However there are other set of
operations that could be performed by the NC-controller, which don’t imply machine axis movements, and they could
be also grouped under the NC-functions. Figure 7 and 8 details some of the already identified actions, as for
example:

get_time : that will instruct the controller to get current time for and register this data in the associated
traceability data placeholder for the selected operation. This code should be used for registering starting
and ending times for traced operations, as figure 7 depicts, for example for registering the starting and
ending time of a workingstep.
 Program flow

Instructions for AP 238

WS
traced Workingstep
#10
# get_time (&Start_time)
#axis_movement(………...)
………………………………
#load tool(…………………)
WS
………………………………
#11
………………………………
………………………………
………………………………
………………………………
………………………………
………………………………
………………………………
………………………………
#get_time(&End_time) WS
#20

Figure 7. Getting Workinstep Execution Time.

get_tool_data : as NC-controllers have access to the tool database, which must contain all information
necessary for identifying the employed tool, it could be functions to allow translate this information into
traceability data.

get_Non_Machinning_Data: more generic execution instruction to get for example, the codebar,
identifying the worker which has manipulated the NC-machine, etc.

more to_be_defined… ?

ABS(nc_function)

program_stop optional_stop
get _Non_Machinning_data

exchange_pallet set_mark wait_for_mark Its_recorded

_data

index_pallet
(ABS)Data_
placeHolder
index_table

display_message

load_tool

unload_tool (ABS)Data_
Its_recorded placeHolder
_data
get_tool_data
Its_recorded
_time
get_time Date

nc_legacy_fucntion

Figure 8. Some Identified Actions to perform by a NC TRACEABILITY-enabled machine. (non-axis movement

operations)
3.2 Tracing controller events.

When adding traceability to NC-manufacturing, it is also extremely important to have knowledge of the NC controller
running exceptions because, in automation and control systems, problems came, not in the normal cycle execution of
the processes, but when the cycle stops. This may happen because there is an Alarm or because the operator
decides to stop it (to don’t do nothing, just wait, or to make a manual operation). When the process resumes, it may
continue in the same point before it had stopped or it may go back to a previous execution point, depending on the
control program decisions.

But, every control program is different one from other, one has an auto mode, a manual mode and a stop mode;
other have also an alarm mode, etc. Just for clarification, and as an example, see Figure 8.
ƒ Automatic mode: the controller execute the program.
ƒ Manual mode: the controller do not execute the program and only make specific actions in response to
manual commands.
ƒ Alarm mode. If a Alarm show up. The controller stops the execution. To go on, the alarm has to disappear
and the operator has to “ack” and resume the process.
ƒ Stop mode: some times the execution just stops because a manual decision.
ƒ Warnings: There are soft alarms that do not halt the execution of the automatic mode.
ƒ …..

Controller Traceable Status

& Events

Alarm
AUTOMATIC
WARNING mode
mode

Resume
No Alarm Change to
Manual

STOP MANUAL
mode mode
Change to Auto

Figure 9. Example of the controller state modes

But, although there is not a common structure for “operation mode” schema, to really know in the future what has
happened during production it is very important to track these stops, (and it is enough, it is not necessary know the
internal mode organization of the controller program) to know the source of the stops, to know what has happened
during the stop time (for instance, if a manual operation has been performed), and to know how the process has
continue. Next figure (Figure 10) is an example of possible execution events while making, for instance, a drill
workingstep.

Sample workinstep execution (drill a hole)

 1. NORMAL EXECUTION
(ABS)
Execution timming Samples Traced_WorkingStep

0s 5s 10s
workinstep_time

execution_events S[0:?] TimeStamp

START END
Event

0 5

2. EXECUTION with WARNINGS (no stop) (ABS)

Traced_WorkingStep

0s 1 1.5 2 5s 10s
workinstep_time

execution_events S[0:?] TimeStamp

START END
Event
WARNINGS
0 5

WARNING 1

WARNING 1.5

WARNING 2

3. EXECUTION WITH ALARM (stop & resume)

0s 1 3 8s 10s
(ABS)
Traced_WorkingStep

workinstep_time
END
START
GO ON
ALARM
execution_events S[0:?] TimeStamp
+ STOP
Event

0 8

ALARM 1

STOP 1.5

GO ON 3
 4. EXECUTION WITH MANUAL GO THROUGH

0s 1 5 6 10s
(ABS)
Traced_WorkingStep

START

execution_events S[0:?] workinstep_time

MANUAL GO ON
TimeStamp
ALARM, STOP Event

0 10

ALARM 1

STOP 1

MANUAL 5

operations

operations

GO ON 6

5. FAILED EXECUTION (stop & exit)

0s 1 10s
(ABS)
Traced_WorkingStep

START
execution_events S[0:?] workinstep_time

TimeStamp
ALARM, STOP Event
EXIT & JUMP

0 ¿?
Previous
workinstep
ALARM 1

STOP 1

EXIT 1

Jump point
 6. EXECUTION WITH RESTART

0s 1 10s (ABS)
Traced_WorkingStep

START
workinstep_time
execution_events S[0:?]
TimeStamp
ALARM, STOP, Event
RESTART
0 ¿?
0s 2 7 10s
ALARM 1

STOP 1
RESTART END

RESTART 1

(ABS)
Traced_WorkingStep

workinstep_time

TimeStamp

2 7
 6.1 EXECUTION WITH RESTART & CHANGE TOOLS

0s 1 10s (ABS)
Traced_WorkingStep

START
workinstep_time
execution_events S[0:?]
TimeStamp
ALARM, STOP, Event
RESTART
0 ¿?
0s 2 7 10s
ALARM 1

STOP 1
RESTART END

CHANGE RESTART 1
TOOLS

(ABS)
Traced_WorkingStep

workinstep_time
Execution
_events S[0:?] TimeStamp

Event

2 7

TOOL CHANGE X

used_tools S[0:?]
ToolData

Figure 10. Controller events.

3.3. Modeling process traceability proposal into AP238 ARM.
WorkPiece UOF specifies the mechanical product that is to be produced by a machining program. This description
may include material, surface condition, features and the AS-IS and TO-BE shape of the product. An AP238 Project
can have several workpieces, and then, Traceability should be as per MANUFACTURED PRODUCT basis (figure
11).

1,66 (40,40,29,5,5,2)

its_id

global_tolerance

Workpiece its_geometry

clamping_positions S[0:?]

its_material

its_workpiece
Traced_Workpiece

Figure 11. Main Entry point for traceability Data in the AP238 ARM Schema.

Traced_Workpiece is Linked to a Workpiece, specifies the physical_identification of the produced Piece. It gives a
TRACEABILITY VIEW of the manufactured product. Next two figures expand this entity.
 description
its_workpiece STRING

Item_identification
Traced_Workpiece label
traced_lot (traceability UOF)

LOT
(AP223)
used_machine

Production
lot_id _date
(AP223)

requirements_documented_by L[1:?] label date

(ABS) Document_file Could be group under an Identification SELECT entity

requirements_specified_by L[1:?]
id
Specification

comapny_model
Traceability_authorization L[1:?] Machine
(AP240)
Approval comapny_name

Management HARMONIZED data

Traced_Operations controlled_by
S[0:?]
controlled_name
(ABS)
Traced_WorkingStep controlled_mode
Controller
controlled_specification

Use Machine AP240 HARMONIZED

 start time
(ABS)
Traced_WorkingStep TimeStamp
workinstep_time Date

end_time

working_step_description
STRING

Traceability_remarks
STRING
Workingstep_data

start time

used_tools S[0:?] ABS(PlaceHolder

Subtype) TimeStamp Date
ToolData
end_time

Item_identification
Label

lot_id
Label
LOT
(AP223) production_date ???
traced_lot Date
(traceability UOF)

execution_events S[0:?] event_time

Event Date

event_description
STRING

event_type event_operations
STRING
Controller_Event
event_break_point
(WARNING, ALARM, MANUAL/AUTO ??STRING
MODE, HARD RESTART, SOFT
RESTART, STOP, PAUSE, ERROR ..) event_return_point
??STRING
PART 4. Open Questions.

4.1 Is the proposal about using properties (part 1) to handle characteristic data fine? (if it
is, it means that AP224,223,240 properties have to be included in AP238).

4.2 Is the proposal (part 2) about redefine material definition (harmonized and extended)
fine?

4.3 Is the proposal (part 3.1) about including traceability executable actions (get_time,
get_tool_data, …) fine?

4.4 Is the proposal (part 3.2) about tracing controller events fine or it goes to much
beyond the scope?

4.5 To make traceability requirements configurations, for example, to communicate those

characteristics has to be trace, or a feature process, etc), it could be some options:
1. Make a kina of conformance classes, for example:
CNC without tracing.
CNC with characteristic tracing.
CNC with resources tracing (material, tools, etc)
CNC with process tracing.
CNC with full traceability.
….
2. Set a boolean attribute is every traceable entity to specify it is should be traced
or not.
3. Both
4. ¿????.
PART 5. Appendix.

A1: More Harmonization graphics

CAD/CAM

CAD CADD CAM CNC CONTROL

Design Detailing Path Planning Manufacturing

AP203 AP203ed2 AP238
AP224

AP238 (configuration
data) Manufacturing
Customer View
(Design, Detailing & Path
Planning) +
TRACEABILITY
REQUISITES
(Configuration)

Traceability DATA

Framework for traceability application in STEP-NC.

AP224/203Ed2 + AP240 + AP238

Part Model Shape Representation Features
Materials
Properties Tolerances
(Process Planning View)
Machine Tool Resource Process Plan & Process
Administrative Data
(Process Planning View) Activities
Process Requirment
Documents + Milling Turning & EDM
TRACEABILITY Requeriment Processes
Documents & DATA

A STEP Manufacturing “all inclusive” data environment.

AP238
Features
Tolerances
Administrative
Properties
Data
(Characteristics
(Management
Data)
UOF)
Traceability Milling, Turning &
requeriments EDM Processes
Data (ISO 14649)

AP238 Information requirements needs for traceability & characteristics data.

A2: Traceability Activity Model

Customer Regulations Standards and NC machine

Specifications Traceability specifications Traceability capabilities

Traceability manufacturing
process data
Part/Workpiece
Data Info (descirption) Characteristics part
Trace a part data
(Workpiece)
Traceability Analysis
A0 Audit/check/Test…

Machine Machine
Tools operators

Trace Process in STEP manufacturing Activity Model (Preliminary)

AP-238 Traceability
Traceability
Specifications
Scope

Traceability manufacturing info:

Workpiece/ NC-Traceabilty program code
Part info
Configure
Traceability
A01
Manufacturing
process
NC-program info
Execute
WorkPiece/ Traceability
Part Info
Processes
A11 WorkPiece/
Part info Traceability
(Analysis)
Traceability Data Analyze
(traceability results)
Traceability
Data
A12
Traceability Data
(traceability &
Characterisitcs)

REQUISITES ANALYSIS
(AP203/224/240) (APs ???)

Activity Model detail. (Preliminary)

It is important to notice that if for example, logistic information is to be added with traceability data, “Shipping
container” data could be added harmonized with the Activity Model presented for AP223. (figure 11)
 Traceability
Specifications

Traceability manufacturing info:

Workpiece/ NC-Traceabilty program code
Part info
Configure
Traceability
A01
Manufacturing
process
NC-program info
Execute
WorkPiece/ Traceability
Part Info
Processes
A11 WorkPiece/
Part info Traceability
(Analysis)
Traceability Data Analyze
(traceability results)
Traceability
Data
A12
Traceability Data
(traceability &
Characterisitcs)

Part
Shipping Package
Containers Data Packaged
A13 Part

Adding capabilities to the Activity Model detail. (Preliminary)