PDM-UG: Supplied Part Identification

From WikiSTEP

Jump to: navigation, search

This page belongs to the PDM Usage Guide.

Supplied part identification is realized by an 'alias relationship' concept. It is specific for supplied parts that allow the renumbering of vendor parts.

In all realms of design and manufacturing business, it is common to buy parts from a vendor and renumber them under an internal numbering scheme. In today's practice, this is done through envelope, specification and source control drawings.

  • An envelope drawing is used for a simple renumber of a part where the part is referenced on the envelope drawing and assigned a new part number via the associated parts list.
  • A specification control drawing renumbers a part to show that it meets or exceeds the specifications defined on the drawing and to recommend sources for the part.
  • A source control drawing renumbers a part and creates a restricted list of suppliers that are qualified to produce the part based on the specifications.

All of these relationships are supported by the product_definition_formation_relationship entity. This entity is used for the identification of part suppliers. The product_definition_formation_relationship may be used for the renumbering of parts. The supplied part relationship relates the "new" part master product_definition_formation in the relating_product_definition_formation attribute to the "old" part master product_definition_formation in the related_product_definition_formation attribute.

Contents

The Instance Model: EXPRESS entities and attributes

The EXPRESS entities and attributes essential to support the requirements of supplied part identification are illustrated in Diagram 31.

Image:Diagram_31_Supplied_Part_Instance_Diagram.png
Diagram 31: Supplied Part Instance Diagram

Product definition formation relationship

The product_definition_formation_relationship entity generally relates two product_definition_formation instances in a specified relationship type - the identification of the relationship type is given in the name attribute.

Attributes

  • The id attribute provides an identifier of the relationship.
  • The name attribute specifies this relationship represents 'supplied item'.
  • The relating_product_definition_formation attribute references the internal part version information.
  • The related_product_definition_formation attribute references the supplied part version information.


ENTITY product_definition_formation_relationship Attribute Population Remarks
id type: identifier = string  
name type: label = string shall be 'supplied item'
description type: text = string OPTIONAL
related_product_definition_formation type : entity = product_definition_formation supplied part version information
relating_product_definition_formation Type : entity = product_definition_formation internal part version

===Preprocessor Recommendations=== The value 'supplied item' for the name attribute identifies this as the supplied item relationship. There is no standard mapping for the description attribute in a product_definition_formation_relationship. The id attribute must be unique with respect to the relationship, but there is no standard mapping for the value.

===Postprocessor Recommendations=== Since there are no standard mapping for the description attributes for a product_definition_formation_relationship, it is recommended that postprocessors not assign any processing significance to this value.

===Related Entities=== Certification of suppliers can be indicated through the supplied item relationship. This is done by relating an applied_certification_assignment to the product_definition_formation_relationship, which associates a certification to the relationship. The applied_certification_assignment entity may have a role associated with it through the entity role_association and its related object_role entity. There are no standard mappings for the values of the role, or the name and purpose attributes of the certification entity.

The Instance Model: STEP exchange file format (ISO10303 Part 21 syntax)

/* primary application context for design assembly life cycle */
#1000 = APPLICATION_CONTEXT('mechanical design');
#220 = PRODUCT_CONTEXT('', #1000, '');
#230 = PRODUCT_DEFINITION_CONTEXT('part definition', #1000, 'design');

/* part type discrimination */
#100=PRODUCT_RELATED_PRODUCT_CATEGORY('part',$,(#2, #9));

/* solid cube - supplied part */
#2=PRODUCT('11000','solid cube','description for part 11000',(#220));
#3=PRODUCT_DEFINITION_FORMATION('A', 'description of version A for solid cube',#2);
#4=PRODUCT_DEFINITION('D1','detailed drawing as planned for STEP conformance testing',#3,#230);

/* solid box - internal part */
#9=PRODUCT('11111','Solid Box','part 11111 made from raw material 11000',(#220));
#10=PRODUCT_DEFINITION_FORMATION('A', 'description of version A for part 11111',#9);
#11=PRODUCT_DEFINITION('D2','detailed drawing',#10,#230);

#16=PRODUCT_DEFINITION_FORMATION_RELATIONSHIP('id','supplied item',$,#10,#3);
Example 26: exchange file for supplied part
Personal tools