Template:— representing_assembly_structure (rep_assy) Date: 2008/03/03 06:04:43
Revision: 1.15
CoverContentsDescriptionModel diags.Input params.Ref. params.Instantiation pathInstance diags.CharacterizationsIssues

This section specifies the template representing_assembly_structure.

NOTE  An explanation of a template and the associated instantiation path is provided in the Template overview section.

Description

This template describes how to represent the relationship between a component and its immediate parent assembly in a product structure, e.g. a parts assembly. As components and assemblies, different instances of Product_view_definition (or subtypes thereof) may be related together. Subtypes of this entity that correspond to entities such as; Part, (e.g. Part_view_definition), Product_as_individual, (e.g. Product_as_individual_view), Attachment_slot, (e.g. Attachment_slot_definition), Interface_specification, (e.g. Interface_specification_definition), and Interface_connection, (e.g. Interface_connector_definition) may therefore, be used.

This template should in particular be used to create the assembly structures that represent traditional Bill of Material structures (i.e. design and manufacturing part structures), as well as simple product structures for real products. For more complex structures, especially when several product structures are used to represent the product across many life cycle stages and domain views, it is probably better to use breakdown structures (see C004: representing_breakdown_structure (NB Capabilities are not documented in this release of the PLCS standard) ).

Model diagrams
The EXPRESS-G diagram in Figure 1 shows the templates and EXPRESS entities that are required to represent the template "representing_assembly_structure". The text highlighted in blue shows the template parameters.
Entities and templates in grey areas are not part of this template, but is shown for completeness. Optional templates (dashed borders) are not instantiated by the template, but may be used to characterize the template (see Characterizations below).


Figure 1 —  An EXPRESS-G representation of the Information model for representing_assembly_structure

Figure 1 —  An EXPRESS-G representation of the Information model for representing_assembly_structure

The graphic for the template to be used in other EXPRESS-G diagrams is shown in Figure  2 below.
The diagram shows the abbreviated symbol to the left, and the expanded symbol to the right.


Figure 2 —  The graphical representation of the representing_assembly_structure template

Figure 2 —  The graphical representation of the representing_assembly_structure template

Input parameters
The following input parameters are defined for this template:
parent (Type= 'ENTITY (Product_view_definition)' )
The immediate parent Product_view_definition in the assembly.
child (Type= 'ENTITY (Product_view_definition)' )
The immediate child Product_view_definition in the assembly.
location_indicator (Type='STRING', Optional)
A string indicating the location of the child in the parent, e.g. right wing.
quantity (Default=1,Type= 'TYPE (any_number_value)' )
The quantity of the child in parent assembly. If unspecified, '1' is assumed.
unit (Default=Count,Type='CLASS')
The name of the class used to represent the units of the corresponding quantity.
The following classes and their sub-classes can be used:
classifications: "Unit" (urn:plcs:rdl:std:Unit)
unit_ecl_id (Default=urn:plcs:rdl:std,Type='URN')
The identifier of the External_class_library storing the definition of the class referenced by the parameter @unit.
si_unit (Default=false,Type='BOOLEAN')
Value should be set to true if the unit is a SI base unit defined by ISO, i.e. kilogram (kg) for Mass, second (s) for Time, metre (m) for Displacement, ampere (A) for Electrical current, kelvin (K) for Temperature, mole (mol) for Amount of substance, and candela (cd) for Luminous intensity. If this is not the case it should be set to false.
Note that the representation of true and false depends on exchange format. In Part 11 (a STEP file) true is represented by the string ".T.", and false by ".F.", while in Part 28 (XML) they are represented by text strings "true" and "false".
Reference parameters
The following reference parameters are defined for this template:
nau(Type='ENTITY (Next_assembly_usage)')
Allow the Next_assembly_usage entity instantiated in this path to be referenced when this template is used.
Note: The Next_assembly_usage entity can be referenced in a template path by:
%^target = $representing_assembly_structure.nau%
where target is the parameter to which the Next_assembly_usage is bound.
Instantiation path
The instantiation path shown below specifies the entities that are to be instantiated by the template.
A description of templates and the syntax for the instantiation path is provided in the Templates Help/Information section.
-- Create Next_assembly_usage instance
Next_assembly_usage
Next_assembly_usage.id = '/IGNORE'
Next_assembly_usage.relation_type = '/IGNORE'
Next_assembly_usage.description = '/IGNORE'
Next_assembly_usage.location_indicator = @location_indicator
%^nau = Next_assembly_usage%

-- Provide the quantity through template representing_quantity
-- and assign reference parameter ^quantity to its
-- reference param ^quantity
/representing_quantity(
    value= @quantity,
    unit_class_name=@unit,
    si_unit=@si_unit,
    unit_ecl_id=@unit_ecl_id)/
%^quantity = $representing_quantity.quantity%

-- instantiate relations to Next_assembly_usage
Next_assembly_usage.quantity -> ^quantity
Next_assembly_usage.relating_view -> @parent
Next_assembly_usage.related_view -> @child
The following entities are instantiated with attributes as specified:
Entity in path Value Inherited from
Next_assembly_usage.id '/IGNORE' View_definition_relationship.id
Next_assembly_usage.relation_type '/IGNORE' View_definition_relationship.relation_type
Next_assembly_usage.description '/IGNORE' View_definition_relationship.description
Next_assembly_usage.location_indicator @location_indicator Assembly_component_relationship.location_indicator
Instance diagrams
The instance diagram in Figure  3 shows an example of the EXPRESS entities and templates that are instantiated by the template:
/representing_assembly_structure(parent='#1', child='#62', location_indicator='$', quantity='ANY_NUMBER_VALUE(2)', unit='Count', unit_ecl_id='urn:plcs:rdl:std', si_unit='false')/
(an illustration of the consolidated representing_assembly_structure template is shown in Figure 4 below.)
The diagram below shows a relationship between a parts "sleeve" and "gasket", with the quantity "2". This means that the sleeve contains two gaskets. There is no information provided for the location of these gaskets in this example.


Figure 3 —  Entities instantiated by representing_assembly_structure template

Figure 3 —  Entities instantiated by representing_assembly_structure template

The instance diagram in Figure 4 shows the graphic symbol for the template that is to be used in other instance diagrams. The example template is:
/representing_assembly_structure(parent='#1', child='#62', location_indicator='$', quantity='ANY_NUMBER_VALUE(2)', unit='Count', unit_ecl_id='urn:plcs:rdl:std', si_unit='false')/
Note that the default values of the template representing_quantity have been used, i.e. no values are given for parameters where the default value will suffice.


Figure 4 —  Instantiation of representing_assembly_structure template

Figure 4 —  Instantiation of representing_assembly_structure template

Characterizations
The following section details how the representing_assembly_structure template can be optionally characterized by assigning other constructs to it. These are characterizations commonly applied to the template. The ISO 10303-239 EXPRESS model may enable other assignments to the entities instantiated by the template.
The EXPRESS-G diagram in Figure 5 shows the possible characterizations of the template "representing_assembly_structure".


Figure 5 —  Characterizations of the representing_assembly_structure template

Figure 5 —  Characterizations of the representing_assembly_structure template

The following characterizations may apply:
Characterization Assigning classification

NOTE   this characterization is optional.

The Next_assembly_usage may be classified using external reference data, as described in assigning_reference_data. The class must be a subtype of "Next assembly usage" (urn:plcs:rdl:std:Next assembly usage). Example of classes (not standardized) are manufacturing assembly illustrated parts list

NOTE    The assignment of date and time information is described the capability C010: assigning_reference_data (NB Capabilities are not documented in this release of the PLCS standard) .

Characterization Assigning identification

NOTE   this characterization is optional.

A Next_assembly_usage may be given an identifier, using assigning_identification. The identifier shall be classified as "Relationship identification code" (urn:plcs:rdl:std:Relationship identification code) or one of its subclasses, and should have an organization as owner.

NOTE    The assignment of identifiers is described the capability C001: assigning_identifiers (NB Capabilities are not documented in this release of the PLCS standard) .

Characterization Assigning date and time

NOTE   this characterization is optional.

The Next_assembly_usage may be assigned a date and time, e.g. to indicate when it was created. Such a time-stamp could be used to infer dated effectivity for the assembly structure, but if that is the reason, it is recommended that effectivity shall be used (as described below), instead.

A date and time may be assigned to a Next_assembly_usage using assigning_time. If only the date is desired, the time parameters shall be set to "0".

The date and time shall be classified using a subclass of "Date actual" (urn:plcs:rdl:std:Date actual) or "Date planned" (urn:plcs:rdl:std:Date planned).

NOTE    The assignment of dates is described the capability C036: assigning_date_time (NB Capabilities are not documented in this release of the PLCS standard) .

Characterization Assigning effectivity

NOTE   this characterization is optional.

An effectivity may be assigned to the Next_assembly_usage. This shall be done using entity Effectivity_assignment.

For example, a dated effectivity shall be assigned using template assigning_dated_effectivity.

NOTE    The assignment of effectivities is described in capability C006: assigning_effectivity (NB Capabilities are not documented in this release of the PLCS standard) .

Characterization Assigning descriptor

NOTE   this characterization is optional.

A description of the relationship may be provided using the template assigning_descriptor. This shall be applied to the ^next_assembly_usage reference parameter. The following template call shows how this shall be instantiated.

/assigning_descriptor(descr='This relationship describes an assembly of a parent element from a constituent child element.', class_name='Description', ecl_id='urn:plcs:rdl:std', is_assigned_to='@123')/

NOTE    The assignment of description information is described the capability C095: assigning_descriptor (NB Capabilities are not documented in this release of the PLCS standard) .

© OASIS 2010 — All rights reserved