[step-manufacturing] EXTERNAL: Notes on Serial numbers
Richard Martin
richardm at tinwisle.com
Mon Jul 18 10:13:32 EDT 2022
Jan and Thomas,
An good identifier has four properties, all of which are context dependent:
Unambiguous - it is clearly the identifier
Unique - no other thing in that context has the same identifier
Meaningless - no meaning is embedded in the identifier itself
Persistent - the identifier stays with the thing identified
Of course, as the context changes, maintaining these properties becomes more
difficult. For that reason, managing context identification becomes an
additional task that complicates the use of identifiers. We have seen this
in the discussion of cascading identifiers in assembly. While UUID concepts
give us ubiquitous uniqueness, the thread of UUID's through assembly can get
daunting to implement.
Cheers,
Richard
From: step-manufacturing [mailto:step-manufacturing-bounces at steptools.com]
On Behalf Of De Nijs, Jan
Sent: Monday, July 18, 2022 8:07 AM
To: Thomas Thurman <thomas.r.thurman at imonmail.com>
Cc: step-manufacturing at steptools.com
Subject: Re: [step-manufacturing] EXTERNAL: Notes on Serial numbers
When it comes to serial numbers: Yes, there is a move to add more and more
significance to the "human-readable" serial number. If this is the only way
to identify a specific instance of a part number, then this will inevitably
lead to inconsistencies again. Just like what happened with part numbers.
In my view, there need to be 2 things, when it comes to serial numbers:
1. A human readable form.
This one can have as much significance as the user desires. Have it identify
product, where it was made, when it was made etc etc.
2. A UUID to track this specific instance.
This number would be used by the applications to identify specifically which
part we're dealing with.
The combination of both will always be unique. The human readable will
inevitably lead to duplication, or massive inconsistencies when people are
encouraged to re-use design on other assemblies.
I am advocating for human-readable/UUID combinations for many identifiers
such as:
1. Part Number
2. Serial Number
3. Engineering Requirement
4. Shop Order Number
5. Person operating the equipment
6. Etc.
We are still in a world where we do a lot of the manufacturing orchestration
by hand. That drives the need for human readable forms of these identifiers.
But long term, as orchestration processes get automated, there is a need for
UUID's. Since humans are going to be always in (or at the very least close
to) the loop, human readable forms are important. But the inconsistencies
that that brings, need to be countered by a UUID, which will take a more and
more central role as automation get s introduced.
Jan de Nijs
LM Fellow
Enterprise Digital Production
Lockheed Martin
Tel: (817) 762 2425 | Mobile: (817) 996 1552
<http://www.lockheedmartin.com/> Lockheed Martin
From: step-manufacturing <step-manufacturing-bounces at steptools.com
<mailto:step-manufacturing-bounces at steptools.com> > On Behalf Of Thomas
Thurman
Sent: Friday, July 15, 2022 10:49 AM
To: step-manufacturing at steptools.com
<mailto:step-manufacturing at steptools.com>
Subject: EXTERNAL: [step-manufacturing] Notes on Serial numbers
Dear All,
Some information on serial numbers:
I asked Phil Spiby about serial numbers in application of life-cycle support
and he mentioned two methods for as-built product he was aware of:
A-use the serial number as the product identifier
B-use a classification approach to not only add serial number but also
organizational information.
ISO/TS 10303-1147:2019 Application module: Manufacturing configuration
effectivity
is of interest.
A partial extract is provided for reference.
Best Regards,
Tom Thurman
scope:
This part of ISO 10303 specifies the application module Manufacturing
configuration effectivity. The following are within the scope of this part
of ISO 10303:
* serial number-based condition for the use of a component in a
product proposed to market;
* production lot number-based condition for the use of a component in
a product proposed to market;
* production date-based condition for the use of a component in a
product proposed to market.
Here are the ARM definitions
4.2 ARM entity definitions
This subclause specifies the ARM entities for this module. Each ARM
application entity is an atomic element that embodies a unique application
concept and contains attributes specifying the data elements of the entity.
The ARM entities and definitions are specified below.
4.2.1 Dated_configuration
A Dated_configuration is a type of
<file:///\\Users\tom\Library\Mobile%20Documents\com~apple~CloudDocs\step_par
ts\N11017_SMRL_v9_rc1_20220203\data\modules\manufacturing_configuration_effe
ctivity\sys\4_info_reqs.htm#manufacturing_configuration_effectivity_arm.manu
facturing_configuration> Manufacturing_configuration whose effectivity
domain is a time interval.
The interval of time during which the
<file:///\\Users\tom\Library\Mobile%20Documents\com~apple~CloudDocs\step_par
ts\N11017_SMRL_v9_rc1_20220203\data\modules\specified_product\sys\4_info_req
s.htm#specified_product_arm.product_specification> Product_specification has
been, is, or will be produced.
EXPRESS specification:
*)
ENTITY Dated_configuration
SUBTYPE OF (
<file:///\\Users\tom\Library\Mobile%20Documents\com~apple~CloudDocs\step_par
ts\N11017_SMRL_v9_rc1_20220203\data\modules\manufacturing_configuration_effe
ctivity\sys\4_info_reqs.htm#manufacturing_configuration_effectivity_arm.manu
facturing_configuration> Manufacturing_configuration);
SELF\
<file:///\\Users\tom\Library\Mobile%20Documents\com~apple~CloudDocs\step_par
ts\N11017_SMRL_v9_rc1_20220203\data\modules\configuration_effectivity\sys\4_
info_reqs.htm#configuration_effectivity_arm.item_usage_effectivity>
Item_usage_effectivity.effectivity_domain :
<file:///\\Users\tom\Library\Mobile%20Documents\com~apple~CloudDocs\step_par
ts\N11017_SMRL_v9_rc1_20220203\data\modules\effectivity\sys\4_info_reqs.htm#
effectivity_arm.dated_effectivity> Dated_effectivity;
END_ENTITY;
(*
Attribute definitions:
effectivity_domain: the
<file:///\\Users\tom\Library\Mobile%20Documents\com~apple~CloudDocs\step_par
ts\N11017_SMRL_v9_rc1_20220203\data\modules\effectivity\sys\4_info_reqs.htm#
effectivity_arm.dated_effectivity> Dated_effectivity that defines the
effectivity domain.
4.2.2 Lot_configuration
A Lot_configuration is a type of
<file:///\\Users\tom\Library\Mobile%20Documents\com~apple~CloudDocs\step_par
ts\N11017_SMRL_v9_rc1_20220203\data\modules\manufacturing_configuration_effe
ctivity\sys\4_info_reqs.htm#manufacturing_configuration_effectivity_arm.manu
facturing_configuration> Manufacturing_configuration whose effectivity
domain is identified by a production lot identifier.
The lot is a production lot of the
<file:///\\Users\tom\Library\Mobile%20Documents\com~apple~CloudDocs\step_par
ts\N11017_SMRL_v9_rc1_20220203\data\modules\specified_product\sys\4_info_req
s.htm#specified_product_arm.product_specification> Product_specification
under consideration.
EXPRESS specification:
*)
ENTITY Lot_configuration
SUBTYPE OF (
<file:///\\Users\tom\Library\Mobile%20Documents\com~apple~CloudDocs\step_par
ts\N11017_SMRL_v9_rc1_20220203\data\modules\manufacturing_configuration_effe
ctivity\sys\4_info_reqs.htm#manufacturing_configuration_effectivity_arm.manu
facturing_configuration> Manufacturing_configuration);
SELF\
<file:///\\Users\tom\Library\Mobile%20Documents\com~apple~CloudDocs\step_par
ts\N11017_SMRL_v9_rc1_20220203\data\modules\configuration_effectivity\sys\4_
info_reqs.htm#configuration_effectivity_arm.item_usage_effectivity>
Item_usage_effectivity.effectivity_domain :
<file:///\\Users\tom\Library\Mobile%20Documents\com~apple~CloudDocs\step_par
ts\N11017_SMRL_v9_rc1_20220203\data\modules\effectivity\sys\4_info_reqs.htm#
effectivity_arm.lot_effectivity> Lot_effectivity;
END_ENTITY;
(*
Attribute definitions:
effectivity_domain: the
<file:///\\Users\tom\Library\Mobile%20Documents\com~apple~CloudDocs\step_par
ts\N11017_SMRL_v9_rc1_20220203\data\modules\effectivity\sys\4_info_reqs.htm#
effectivity_arm.lot_effectivity> Lot_effectivity that defines the
effectivity domain.
4.2.3 Manufacturing_configuration
A Manufacturing_configuration is a type of
<file:///\\Users\tom\Library\Mobile%20Documents\com~apple~CloudDocs\step_par
ts\N11017_SMRL_v9_rc1_20220203\data\modules\configuration_effectivity\sys\4_
info_reqs.htm#configuration_effectivity_arm.item_usage_effectivity>
Item_usage_effectivity that specifies a condition for the use of a
<file:///\\Users\tom\Library\Mobile%20Documents\com~apple~CloudDocs\step_par
ts\N11017_SMRL_v9_rc1_20220203\data\modules\product_occurrence\sys\4_info_re
qs.htm#product_occurrence_arm.product_occurrence> Product_occurrence in a
product represented by an instance of
<file:///\\Users\tom\Library\Mobile%20Documents\com~apple~CloudDocs\step_par
ts\N11017_SMRL_v9_rc1_20220203\data\modules\specified_product\sys\4_info_req
s.htm#specified_product_arm.product_specification> Product_specification.
Only specializations of Manufacturing_configuration shall be instantiated.
EXPRESS specification:
*)
ENTITY Manufacturing_configuration
ABSTRACT SUPERTYPE OF (ONEOF (
<file:///\\Users\tom\Library\Mobile%20Documents\com~apple~CloudDocs\step_par
ts\N11017_SMRL_v9_rc1_20220203\data\modules\manufacturing_configuration_effe
ctivity\sys\4_info_reqs.htm#manufacturing_configuration_effectivity_arm.seri
al_configuration> Serial_configuration,
<file:///\\Users\tom\Library\Mobile%20Documents\com~apple~CloudDocs\step_par
ts\N11017_SMRL_v9_rc1_20220203\data\modules\manufacturing_configuration_effe
ctivity\sys\4_info_reqs.htm#manufacturing_configuration_effectivity_arm.date
d_configuration> Dated_configuration,
<file:///\\Users\tom\Library\Mobile%20Documents\com~apple~CloudDocs\step_par
ts\N11017_SMRL_v9_rc1_20220203\data\modules\manufacturing_configuration_effe
ctivity\sys\4_info_reqs.htm#manufacturing_configuration_effectivity_arm.lot_
configuration> Lot_configuration))
SUBTYPE OF (
<file:///\\Users\tom\Library\Mobile%20Documents\com~apple~CloudDocs\step_par
ts\N11017_SMRL_v9_rc1_20220203\data\modules\configuration_effectivity\sys\4_
info_reqs.htm#configuration_effectivity_arm.item_usage_effectivity>
Item_usage_effectivity);
concerned_organization : SET[0:?] OF
<file:///\\Users\tom\Library\Mobile%20Documents\com~apple~CloudDocs\step_par
ts\N11017_SMRL_v9_rc1_20220203\data\modules\person_organization\sys\4_info_r
eqs.htm#person_organization_arm.organization> Organization;
WHERE
WR1: ('MANUFACTURING_CONFIGURATION_EFFECTIVITY_ARM.' +
'PRODUCT_SPECIFICATION') IN TYPEOF(resolved_configuration.configuration);
WR2: ('PRODUCT_OCCURRENCE_ARM.' + 'PRODUCT_OCCURRENCE') IN
TYPEOF(item_usage_relationship\View_definition_relationship.related_view);
END_ENTITY;
(*
Attribute definitions:
concerned_organization: the set of
<file:///\\Users\tom\Library\Mobile%20Documents\com~apple~CloudDocs\step_par
ts\N11017_SMRL_v9_rc1_20220203\data\modules\person_organization\sys\4_info_r
eqs.htm#person_organization_arm.organization> Organization for which the
Manufacturing_configuration is valid.
In the case where the concerned_organization is an empty set, the
Manufacturing_configuration is relevant to any organization that may
consider the proposed product.
Formal propositions:
WR1: The context for which the configuration conditions are characterized
shall be a
<file:///\\Users\tom\Library\Mobile%20Documents\com~apple~CloudDocs\step_par
ts\N11017_SMRL_v9_rc1_20220203\data\modules\specified_product\sys\4_info_req
s.htm#specified_product_arm.product_specification> Product_specification.
WR2: The object for which a conditional use case is specified shall be a
<file:///\\Users\tom\Library\Mobile%20Documents\com~apple~CloudDocs\step_par
ts\N11017_SMRL_v9_rc1_20220203\data\modules\product_occurrence\sys\4_info_re
qs.htm#product_occurrence_arm.product_occurrence> Product_occurrence.
4.2.4 Serial_configuration
A Serial_configuration is a type of
<file:///\\Users\tom\Library\Mobile%20Documents\com~apple~CloudDocs\step_par
ts\N11017_SMRL_v9_rc1_20220203\data\modules\manufacturing_configuration_effe
ctivity\sys\4_info_reqs.htm#manufacturing_configuration_effectivity_arm.manu
facturing_configuration> Manufacturing_configuration whose effectivity
domain is an interval of serial numbers.
The serial numbers of the
<file:///\\Users\tom\Library\Mobile%20Documents\com~apple~CloudDocs\step_par
ts\N11017_SMRL_v9_rc1_20220203\data\modules\specified_product\sys\4_info_req
s.htm#specified_product_arm.product_specification> Product_specification
under consideration are in the given interval of serial numbers.
EXPRESS specification:
*)
ENTITY Serial_configuration
SUBTYPE OF (
<file:///\\Users\tom\Library\Mobile%20Documents\com~apple~CloudDocs\step_par
ts\N11017_SMRL_v9_rc1_20220203\data\modules\manufacturing_configuration_effe
ctivity\sys\4_info_reqs.htm#manufacturing_configuration_effectivity_arm.manu
facturing_configuration> Manufacturing_configuration);
SELF\
<file:///\\Users\tom\Library\Mobile%20Documents\com~apple~CloudDocs\step_par
ts\N11017_SMRL_v9_rc1_20220203\data\modules\configuration_effectivity\sys\4_
info_reqs.htm#configuration_effectivity_arm.item_usage_effectivity>
Item_usage_effectivity.effectivity_domain :
<file:///\\Users\tom\Library\Mobile%20Documents\com~apple~CloudDocs\step_par
ts\N11017_SMRL_v9_rc1_20220203\data\modules\effectivity\sys\4_info_reqs.htm#
effectivity_arm.serial_effectivity> Serial_effectivity;
END_ENTITY;
(*
Attribute definitions:
effectivity_domain: the
<file:///\\Users\tom\Library\Mobile%20Documents\com~apple~CloudDocs\step_par
ts\N11017_SMRL_v9_rc1_20220203\data\modules\effectivity\sys\4_info_reqs.htm#
effectivity_arm.serial_effectivity> Serial_effectivity that defines the
effectivity domain.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.steptools.com/pipermail/step-manufacturing/attachments/20220718/c4e2b2f0/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 999 bytes
Desc: not available
URL: <http://lists.steptools.com/pipermail/step-manufacturing/attachments/20220718/c4e2b2f0/attachment.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.gif
Type: image/gif
Size: 1000 bytes
Desc: not available
URL: <http://lists.steptools.com/pipermail/step-manufacturing/attachments/20220718/c4e2b2f0/attachment-0001.gif>
More information about the step-manufacturing
mailing list