[step-manufacturing] EXTERNAL: Notes on Serial numbers

Nicolas Figay nicolas.figay at airbus.com
Mon Jul 18 09:33:47 EDT 2022 

IMHO it should be taken care concerning using serial numbers as
organisation information containers. What if the organisation changes? Do
we change the serial number?
When defining identifiers, you should have contextualisation information
about the identifier provider and/or process as separated and related
complementary objects (do we use the same identification system?)
Let's note that a way to ensure unicity of an identifier could be to rely
on categorisations creating partitions and naming process with naming
spaces. But this is a mean to create a unique identifier, not a way to
capture information, once again about the issues when this information
changes while the identifier persists.

On Mon, Jul 18, 2022 at 2:09 PM 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.
>
>
>
> 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
>
> Lockheed Martin  <http://www.lockheedmartin.com/>
>
>
>
> *From:* step-manufacturing <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
> *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   [image: EXPRESS-G]
> <http:///Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/modules/manufacturing_configuration_effectivity/armexpg2.htm>[image:
> Mapping table]
> <http:///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* whose
> effectivity domain is a time interval.
>
> The interval of time during which the *Product_specification* has been,
> is, or will be produced.
>
>
>
> *EXPRESS specification:*
>
> *)
> ENTITY Dated_configuration
>   SUBTYPE OF (Manufacturing_configuration);
>   SELF\Item_usage_effectivity.effectivity_domain : Dated_effectivity;
> END_ENTITY;
> (*
>
> *Attribute definitions:*
>
> *effectivity_domain: *the *Dated_effectivity* that defines the
> effectivity domain.
> 4.2.2 Lot_configuration   [image: EXPRESS-G]
> <http:///Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/modules/manufacturing_configuration_effectivity/armexpg2.htm>[image:
> Mapping table]
> <http:///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* whose
> effectivity domain is identified by a production lot identifier.
>
> The lot is a production lot of the *Product_specification* under
> consideration.
>
>
>
> *EXPRESS specification:*
>
> *)
> ENTITY Lot_configuration
>   SUBTYPE OF (Manufacturing_configuration);
>   SELF\Item_usage_effectivity.effectivity_domain : Lot_effectivity;
> END_ENTITY;
> (*
>
> *Attribute definitions:*
>
> *effectivity_domain: *the *Lot_effectivity* that defines the effectivity
> domain.
> 4.2.3 Manufacturing_configuration   [image: EXPRESS-G]
> <http:///Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/modules/manufacturing_configuration_effectivity/armexpg2.htm>[image:
> Mapping table]
> <http:///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* that
> specifies a condition for the use of a *Product_occurrence* in a product
> represented by an instance of *Product_specification*.
>
> Only specializations of *Manufacturing_configuration* shall be
> instantiated.
>
>
>
> *EXPRESS specification:*
>
> *)
> ENTITY Manufacturing_configuration
>   ABSTRACT SUPERTYPE OF (ONEOF (Serial_configuration,
>                                 Dated_configuration,
>                                 Lot_configuration))
>   SUBTYPE OF (Item_usage_effectivity);
>   concerned_organization : SET[0:?] OF 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* 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*.
>
> *WR2: *The object for which a conditional use case is specified shall be
> a *Product_occurrence*.
> 4.2.4 Serial_configuration   [image: EXPRESS-G]
> <http:///Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/modules/manufacturing_configuration_effectivity/armexpg2.htm>[image:
> Mapping table]
> <http:///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* whose
> effectivity domain is an interval of serial numbers.
>
> The serial numbers of the *Product_specification* under consideration are
> in the given interval of serial numbers.
>
>
>
> *EXPRESS specification:*
>
> *)
> ENTITY Serial_configuration
>   SUBTYPE OF (Manufacturing_configuration);
>   SELF\Item_usage_effectivity.effectivity_domain : Serial_effectivity;
> END_ENTITY;
> (*
>
> *Attribute definitions:*
>
> *effectivity_domain: *the *Serial_effectivity* that defines the
> effectivity domain.
>
>
> _______________________________________________
> step-manufacturing mailing list
> step-manufacturing at steptools.com
> http://lists.steptools.com/mailman/listinfo/step-manufacturing
>
The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised.
If you are not the intended recipient, please notify Airbus immediately and delete this e-mail.
Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately.
All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.steptools.com/pipermail/step-manufacturing/attachments/20220718/0f873578/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/0f873578/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/0f873578/attachment-0001.gif>

More information about the step-manufacturing mailing list