[step-manufacturing] Notes on Serial numbers

Thomas Thurman thomas.r.thurman at imonmail.com
Sat Jul 16 20:38:08 EDT 2022 

Martin,
The standard reference for design (pdm) aspects of the product and related entities is the pdm usage guide, version 4.3, available here:
PDF Usage Guide for the STEP PDM Schema V1.2 Release 4.3 January 2002 <https://www.cax-if.org/documents/pdmug_release4_3.pdf>

Note that my recommendations adhere to the guide. Reference clause 1 in particular of linked document.

It would be good if we could update that reference document and add additional recommendations for the manufactured product.

Regards,
Tom

> On Jul 16, 2022, at 6:06 PM, Thomas Thurman <thomas.r.thurman at imonmail.com> wrote:
> 
> Martin,
> 
> I don't see the connection between what Phil said, what is in ISO 10303-41 and your statements below.
> 
> Here is an extract from part 41. The second way to represent the concept of a real object would be e.g., an engineering prototype of which there may several as the
> design progresses. This prototype is directly reflective and bound to the evolving CAD design model by implication by the statement that the product_definition application is for the design phase.
> There are two ways to represent the concept of real object:
> 
> a real object can be represented by an instance of product if the subject of an annotated Express schema is concerned with real objects or if it is needed to describe a real object at various life-cycle stages and in various configurations; in this case, if an real object is identified by a serial number, this serial number can be stored in the id attribute of the product;
> EXAMPLE 6 <>   An airplane, in service during 30 years, may have different configurations during its life.
> 
> a real object can be represented by an instance of product_definition if the subject of an annotated Express schema is primarily concerned with the design phase of products and if the concept of real object is considered as a particular stage in the design phase of a product; in this case, if a real object is identified by a serial number, this serial_number can be stored in the id attribute of the product_definition.
> EXAMPLE 7 <>   A prototype may be considered as a particular definition of a product.
> 
> 
> 
> It is bad object-flavored modeling practice to have two objects with the same identifier. 
> STEP expects that APs or exchange agreements will specify the context for identifiers, so yes, standard practice in STEP is to NOT have duplicate records for the
> same product identifier.
> 
> If we use serial number for the as-manufactured product identifier, we can provide a product_relationship to tie it back to the design object.
> It is my strong recommendation to use the product identifier as serial number and product_relationship method.
> 
> Below is product_relationship.
> 21.4.22 product_relationship <>   <expg.gif> <file:///Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/resources/product_definition_schema/product_definition_schemaexpg2.htm>
> A product_relationship is a relationship between two instances of the entity data type product <file:///Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/resource_docs/fundamentals_of_product_description_and_support/sys/21_schema.htm#product_definition_schema.product> and provides an identification and description of their relationship.
> 
> NOTE 1 <>   The role of product_relationship can be defined in the annotated EXPRESS schemas that use or specialize this entity, or by default, in an agreement of common understanding between the partners sharing this information.
> 
> NOTE 2 <>   Relationships represented using this entity may be parent child relationship. Annotated EXPRESS schemas that use or specialize this entity specify whether or not the relationship is directed.
> 
> NOTE 3 <>   This entity, together with the product <file:///Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/resource_docs/fundamentals_of_product_description_and_support/sys/21_schema.htm#product_definition_schema.product> entity, is based on the relationship template that is described in annex E.3.
> 
> 
> EXPRESS specification:
> 
> *)
> ENTITY product_relationship;
>   id : identifier <file:///Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/resource_docs/fundamentals_of_product_description_and_support/sys/26_schema.htm#support_resource_schema.identifier>;
>   name : label <file:///Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/resource_docs/fundamentals_of_product_description_and_support/sys/26_schema.htm#support_resource_schema.label>;
>   description : OPTIONAL text <file:///Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/resource_docs/fundamentals_of_product_description_and_support/sys/26_schema.htm#support_resource_schema.text>;
>   relating_product : product <file:///Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/resource_docs/fundamentals_of_product_description_and_support/sys/21_schema.htm#product_definition_schema.product>;
>   related_product : product <file:///Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/resource_docs/fundamentals_of_product_description_and_support/sys/21_schema.htm#product_definition_schema.product>;
> END_ENTITY;
> (*
> 
> Attribute definitions:
> 
> id:  <>the identifier <file:///Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/resource_docs/fundamentals_of_product_description_and_support/sys/26_schema.htm#support_resource_schema.identifier> that distinguishes the product_relationship.
> 
> NOTE 4 <>   The context in which id is used as a discriminating characteristic can be identified in an annotated Express schema that uses or specializes this entity, or by default, in an agreement of common understanding between partners sharing this information.
> 
> name:  <>the label <file:///Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/resource_docs/fundamentals_of_product_description_and_support/sys/26_schema.htm#support_resource_schema.label> by which the product_relationship is known.
> 
> description:  <>the text <file:///Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/resource_docs/fundamentals_of_product_description_and_support/sys/26_schema.htm#support_resource_schema.text> that characterizes the product_relationship. The value of the attribute need not be specified.
> 
> relating_product:  <>one of the instances of product <file:///Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/resource_docs/fundamentals_of_product_description_and_support/sys/21_schema.htm#product_definition_schema.product> that is a part of the relationship.
> 
> NOTE 5 <>   The meaning of this attribute can be defined in the annotated EXPRESS schemas that use or specialize this entity, or in an agreement of common understanding between the partners sharing this information.
> 
> related_product:  <>the other instance of product <file:///Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/resource_docs/fundamentals_of_product_description_and_support/sys/21_schema.htm#product_definition_schema.product> that is a part of the relationship. If one element of the relationship is dependent up on the other, this attribute shall be the dependent one.
> 
> NOTE 6 <>   The meaning of this attribute can be defined in the annotated EXPRESS schemas that use or specialize this entity, or in an agreement of common understanding between the partners sharing this information.
> 
> 
>> On Jul 16, 2022, at 4:08 AM, Martin Hardwick <hardwick at steptools.com <mailto:hardwick at steptools.com>> wrote:
>> 
>> Thanks Tom and Phil Its good to know there is a simple solution, and something more comprehensive when we need it.
>> 
>> So we are allowed to have two or more instances of a product in a STEP file. The instances have the same prototype (to use the DT terminology), but different characteristics.
>> 
>> At the start of manufacturing, they may only have different placements, but later on they may get different colors, properties and features, and they may need to meet different assembly constraints.
>> 
>> In the data, each instance (digital twin) is defined by the same product, the same product_definition_formation, and a different product_definition with its own serial number.
>> 
>> Martin
>> 
>> On 7/15/2022 11:48 AM, Thomas Thurman wrote:
>>> 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 <>   <expg.gif> <file:///Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/modules/manufacturing_configuration_effectivity/armexpg2.htm><mapping.gif> <file:///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 <>   <expg.gif> <file:///Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/modules/manufacturing_configuration_effectivity/armexpg2.htm><mapping.gif> <file:///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 <>   <expg.gif> <file:///Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/modules/manufacturing_configuration_effectivity/armexpg2.htm><mapping.gif> <file:///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 <>   <expg.gif> <file:///Users/tom/Library/Mobile%20Documents/com~apple~CloudDocs/step_parts/N11017_SMRL_v9_rc1_20220203/data/modules/manufacturing_configuration_effectivity/armexpg2.htm><mapping.gif> <file:///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.
>>> 
>>> 
>> -- 
>> Martin Hardwick
>> President STEP Tools, Inc.
>> Cell: 518 253-0596
>> "There are billions of STEP files and millions of STEP-NC files"
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.steptools.com/pipermail/step-manufacturing/attachments/20220716/546b3d79/attachment.htm>

More information about the step-manufacturing mailing list