[step-manufacturing] EXTERNAL: Notes on Serial numbers

Thomas Thurman thomas.r.thurman at imonmail.com
Mon Jul 18 10:27:38 EDT 2022 

Jan,
See below.
A concern I have about this meta-data discussion is that it is in the realm of ERP.
Do we have any ERP subject matter experts on the team?
If so, could you raise your hand and help provide guidance here?
Tom

> On Jul 18, 2022, at 6:06 AM, De Nijs, Jan <jan.de.nijs at lmco.com> wrote:
> 
> 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.
Jan, is there any published research on "what happened with part numbers"? 
The only use case I know of is where the design owner changes to a different organization.
Recording design owner changes is documented in MIL-STD-130 (if I recall correctly), and is possible to exchange using STEP but there was never a recommended
practice written to guide the implementors.  This is an area of overlap with the LOTAR project, so it may be beneficial to have a joint discussion with them at some point.
>  
> In my view, there need to be 2 things, when it comes to serial numbers:
> 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.
> 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 above doesn't comply with common and standard practice. 
Serial number is unique within the context of a part number
So the tuple (pn,sn) is unique and drives the generation of a UUIDv5, (or UUIDv4 if one adds it to the tuple that is internally controlled)
pn = 33, sn = 1, UUID = x3d
pn = 55, sn = 1, UUID = xcfdd
> The human readable will inevitably lead to duplication, or massive inconsistencies when people are encouraged to re-use design on other assemblies.
We can't control human fallacies by data exchange standards. 
>  
> I am advocating for human-readable/UUID combinations for many identifiers such as:
> Part Number
> Serial Number
> Engineering Requirement
> Shop Order Number
> Person operating the equipment
> 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
> Lockheed Martin  <http://www.lockheedmartin.com/>
>  
> 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    <><image001.gif> <x-msg://24/Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/modules/manufacturing_configuration_effectivity/armexpg2.htm><image002.gif> <x-msg://24/Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/modules/manufacturing_configuration_effectivity/sys/5_mapping.htm#aeentitydated_configuration>
> A Dated_configuration is a type of Manufacturing_configuration <file:///Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/modules/manufacturing_configuration_effectivity/sys/4_info_reqs.htm#manufacturing_configuration_effectivity_arm.manufacturing_configuration> whose effectivity domain is a time interval.
> The interval of time during which the Product_specification <file:///Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/modules/specified_product/sys/4_info_reqs.htm#specified_product_arm.product_specification> has been, is, or will be produced.
>  
> EXPRESS specification:
> *)
> ENTITY Dated_configuration
>   SUBTYPE OF (Manufacturing_configuration <file:///Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/modules/manufacturing_configuration_effectivity/sys/4_info_reqs.htm#manufacturing_configuration_effectivity_arm.manufacturing_configuration>);
>   SELF\Item_usage_effectivity <file:///Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/modules/configuration_effectivity/sys/4_info_reqs.htm#configuration_effectivity_arm.item_usage_effectivity>.effectivity_domain : Dated_effectivity <file:///Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/modules/effectivity/sys/4_info_reqs.htm#effectivity_arm.dated_effectivity>;
> END_ENTITY;
> (*
> Attribute definitions:
> effectivity_domain: the Dated_effectivity <file:///Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/modules/effectivity/sys/4_info_reqs.htm#effectivity_arm.dated_effectivity> that defines the effectivity domain.
> 
> 4.2.2 Lot_configuration   <image001.gif> <x-msg://24/Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/modules/manufacturing_configuration_effectivity/armexpg2.htm><image002.gif> <x-msg://24/Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/modules/manufacturing_configuration_effectivity/sys/5_mapping.htm#aeentitylot_configuration>
> A Lot_configuration is a type of Manufacturing_configuration <file:///Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/modules/manufacturing_configuration_effectivity/sys/4_info_reqs.htm#manufacturing_configuration_effectivity_arm.manufacturing_configuration> whose effectivity domain is identified by a production lot identifier.
> The lot is a production lot of the Product_specification <file:///Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/modules/specified_product/sys/4_info_reqs.htm#specified_product_arm.product_specification> under consideration.
>  
> EXPRESS specification:
> *)
> ENTITY Lot_configuration
>   SUBTYPE OF (Manufacturing_configuration <file:///Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/modules/manufacturing_configuration_effectivity/sys/4_info_reqs.htm#manufacturing_configuration_effectivity_arm.manufacturing_configuration>);
>   SELF\Item_usage_effectivity <file:///Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/modules/configuration_effectivity/sys/4_info_reqs.htm#configuration_effectivity_arm.item_usage_effectivity>.effectivity_domain : Lot_effectivity <file:///Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/modules/effectivity/sys/4_info_reqs.htm#effectivity_arm.lot_effectivity>;
> END_ENTITY;
> (*
> Attribute definitions:
> effectivity_domain: the Lot_effectivity <file:///Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/modules/effectivity/sys/4_info_reqs.htm#effectivity_arm.lot_effectivity> that defines the effectivity domain.
> 
> 4.2.3 Manufacturing_configuration   <image001.gif> <x-msg://24/Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/modules/manufacturing_configuration_effectivity/armexpg2.htm><image002.gif> <x-msg://24/Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/modules/manufacturing_configuration_effectivity/sys/5_mapping.htm#aeentitymanufacturing_configuration>
> A Manufacturing_configuration is a type of Item_usage_effectivity <file:///Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/modules/configuration_effectivity/sys/4_info_reqs.htm#configuration_effectivity_arm.item_usage_effectivity> that specifies a condition for the use of a Product_occurrence <file:///Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/modules/product_occurrence/sys/4_info_reqs.htm#product_occurrence_arm.product_occurrence> in a product represented by an instance of Product_specification <file:///Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/modules/specified_product/sys/4_info_reqs.htm#specified_product_arm.product_specification>.
> Only specializations of Manufacturing_configuration shall be instantiated.
>  
> EXPRESS specification:
> *)
> ENTITY Manufacturing_configuration
>   ABSTRACT SUPERTYPE OF (ONEOF (Serial_configuration <file:///Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/modules/manufacturing_configuration_effectivity/sys/4_info_reqs.htm#manufacturing_configuration_effectivity_arm.serial_configuration>,
>                                 Dated_configuration <file:///Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/modules/manufacturing_configuration_effectivity/sys/4_info_reqs.htm#manufacturing_configuration_effectivity_arm.dated_configuration>,
>                                 Lot_configuration <file:///Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/modules/manufacturing_configuration_effectivity/sys/4_info_reqs.htm#manufacturing_configuration_effectivity_arm.lot_configuration>))
>   SUBTYPE OF (Item_usage_effectivity <file:///Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/modules/configuration_effectivity/sys/4_info_reqs.htm#configuration_effectivity_arm.item_usage_effectivity>);
>   concerned_organization : SET[0:?] OF Organization <file:///Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/modules/person_organization/sys/4_info_reqs.htm#person_organization_arm.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 Organization <file:///Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/modules/person_organization/sys/4_info_reqs.htm#person_organization_arm.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 Product_specification <file:///Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/modules/specified_product/sys/4_info_reqs.htm#specified_product_arm.product_specification>.
> 
> WR2: The object for which a conditional use case is specified shall be a Product_occurrence <file:///Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/modules/product_occurrence/sys/4_info_reqs.htm#product_occurrence_arm.product_occurrence>.
> 
> 4.2.4 Serial_configuration   <image001.gif> <x-msg://24/Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/modules/manufacturing_configuration_effectivity/armexpg2.htm><image002.gif> <x-msg://24/Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/modules/manufacturing_configuration_effectivity/sys/5_mapping.htm#aeentityserial_configuration>
> A Serial_configuration is a type of Manufacturing_configuration <file:///Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/modules/manufacturing_configuration_effectivity/sys/4_info_reqs.htm#manufacturing_configuration_effectivity_arm.manufacturing_configuration> whose effectivity domain is an interval of serial numbers.
> The serial numbers of the Product_specification <file:///Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/modules/specified_product/sys/4_info_reqs.htm#specified_product_arm.product_specification> under consideration are in the given interval of serial numbers.
>  
> EXPRESS specification:
> *)
> ENTITY Serial_configuration
>   SUBTYPE OF (Manufacturing_configuration <file:///Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/modules/manufacturing_configuration_effectivity/sys/4_info_reqs.htm#manufacturing_configuration_effectivity_arm.manufacturing_configuration>);
>   SELF\Item_usage_effectivity <file:///Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/modules/configuration_effectivity/sys/4_info_reqs.htm#configuration_effectivity_arm.item_usage_effectivity>.effectivity_domain : Serial_effectivity <file:///Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/modules/effectivity/sys/4_info_reqs.htm#effectivity_arm.serial_effectivity>;
> END_ENTITY;
> (*
> Attribute definitions:
> effectivity_domain: the Serial_effectivity <file:///Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/modules/effectivity/sys/4_info_reqs.htm#effectivity_arm.serial_effectivity> that defines the effectivity domain.
> 
>  

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.steptools.com/pipermail/step-manufacturing/attachments/20220718/11d6b926/attachment.htm>

More information about the step-manufacturing mailing list