ISO/TS 10303-1648:2018-11 Assembly physical requirement allocation


Application module: Assembly physical requirement allocation	ISO/TS 10303-1648:2018-11(E) © ISO

Cover page
Table of contents
Copyright
Foreword
Introduction
1 Scope
2 Normative references
3 Terms, definitions and abbreviated terms
3.1 Terms and definitions
3.2 Abbreviated terms

4 Information requirements
4.1 Required AM ARMs
4.2 ARM type definitions
4.3 ARM entity definitions
5 Module interpreted model
5.1 Mapping specification
5.2 MIM EXPRESS short listing
5.2.1 MIM type definitions
5.2.2 MIM entity definitions

A MIM short names
B Information object registration
C ARM EXPRESS-G
D MIM EXPRESS-G
E Computer interpretable listings
F Change history
Bibliography
Index

5.1 Mapping specification

In the following, "Application element" designates any entity data type defined in Clause 4, any of its explicit attributes and any subtype constraint. "MIM element" designates any entity data type defined in Clause 5.2 or imported with a USE FROM statement, from another EXPRESS schema, any of its attributes and any subtype constraint defined in Clause 5.2 or imported with a USE FROM statement.

This clause contains the mapping specification that defines how each application element of this part of ISO 10303 (see Clause 4) maps to one or more MIM elements (see Clause 5.2).

The mapping for each application element is specified in a separate subclause below. The mapping specification of an attribute of an ARM entity is a subclause of the clause that contains the mapping specification of this entity. Each mapping specification subclause contains up to five elements.

Title: The clause title contains:

the name of the considered ARM entity or subtype constraint, or
the name of the considered ARM entity atribute when this attribute refers to a type that is not an entity data type or a SELECT type that contains or may contain entity data types, or
a composite expression, <attribute name> to <referred type>, when this attribute refers to a type that is not an entity data type or a SELECT type that contains or may contain entity data types.

MIM element: This section contains, depending on the considered application element:

the name of one or more MIM entity data types;
the name of a MIM entity attribute, presented with the syntax <entity name>.<attribute name>, when the considered ARM attribute refers to a type that is not an entity data type or a SELECT type that contains or may contain entity data types;
the term PATH, when the considered ARM entity attribute refers to an entity data type or to a SELECT type that contains or may contain entity data types;
the term IDENTICAL MAPPING, when both application objects involved in an application assertion map to the same instance of a MIM entity data type;
the term NO MAPPING EXTENSION PROVIDED, when the extension to an extensible SELECT TYPE has no impact;
the syntax /SUPERTYPE(<supertype name>)/, when the considered ARM entity is mapped as its supertype;
one or more constructs /SUBTYPE(<subtype name>)/, when the mapping of the considered ARM entity is the union of the mapping of its subtypes.

When the mapping of an application element involves more than one MIM element, each of these MIM elements is presented on a separate line in the mapping specification, enclosed between parentheses or brackets.

Source: This section contains:

the ISO standard number and part number in which the MIM element is defined, for those MIM elements that are defined in a common resource document;
the ISO standard number and part number of this part of ISO 10303, for those MIM elements that are defined in the MIM schema of this part.

This section is omitted when the keywords PATH or IDENTICAL MAPPING or NO MAPPING EXTENSION PROVIDED are used in the MIM element section.

Rules: This section contains the name of one or more global rules that apply to the population of the MIM entity data types listed in the MIM element section or in the reference path. When no rule applies, this section is omitted.

A reference to a global rule may be followed by a reference to the subclause in which the rule is defined.

Constraint: This section contains the name of one or more subtype constraints that apply to the population of the MIM entity data types listed in the MIM element section or in the reference path. When no subtype constraint applies, this section is omitted.

A reference to a subtype constraint may be followed by a reference to the subclause in which the subtype constraint is defined.

Reference path: This section contains:

the reference path to its supertypes in the common resources, for each MIM element created within this part of ISO 10303;
the specification of the relationships between MIM elements, when the mapping of an application element requires to relate instances of several MIM entity data types. In such a case, each line in the reference path documents the role of a MIM element relative to the referring MIM element or to the next referred MIM element.

For the expression of reference paths and of the constraints between MIM elements, the following notational conventions apply:

[]	enclosed section constrains multiple MIM elements or sections of the reference path are required to satisfy an information requirement;
()	enclosed section constrains multiple MIM elements or sections of the reference path are identified as alternatives within the mapping to satisfy an information requirement;
{}	enclosed section constrains the reference path to satisfy an information requirement;
<>	enclosed section constrains at one or more required reference path;
\|\|	enclosed section constrains the supertype entity;
->	the attribute, whose name precedes the -> symbol, references the entity or select type whose name follows the -> symbol;
<-	the entity or select type, whose name precedes the <- symbol, is referenced by the entity attribute whose name follows the <- symbol;
[i]	the attribute, whose name precedes the [i] symbol, is an aggregate; any element of that aggregate is referred to;
[n]	the attribute, whose name precedes the [n] symbol, is an ordered aggregate; member n of that aggregate is referred to;
=>	the entity, whose name precedes the => symbol, is a supertype of the entity whose name follows the => symbol;
<=	the entity, whose name precedes the <= symbol, is a subtype of the entity whose name follows the <= symbol;
=	the string, select, or enumeration type is constrained to a choice or value;
\	the reference path expression continues on the next line;
*	one or more instances of the relationship entity data type may be assembled in a relationship tree structure. The path between the relationship entity and the related entities, is enclosed with braces;
--	the text following is a comment or introduces a clause reference;
*>	the select or enumeration type, whose name precedes the > symbol, is extended into the select or enumeration type whose name follows the > symbol;
<*	the select or enumeration type, whose name precedes the <* symbol, is an extension of the select or enumeration type whose name follows the <* symbol;
!{}	section enclosed by {} indicates a negative constraint placed on the mapping.

The definition and use of mapping templates is not supported in the present version of the application modules. However, use of predefined templates /SUBTYPE/ and /SUPERTYPE/ is supported.

5.1.1 Assembly_requirement_allocation

MIM element:	requirement_assignment
Source:	ISO 10303-41 41
Reference path:	requirement_assignment <= characterized_object {characterized_object.name = 'assembly requirement allocation'}

5.1.1.1 Assembly_requirement_allocation to Assembly_component (as assigned_to)

MIM element:	PATH
Reference path:	requirement_assignment <- requirement_assigned_object.assigned_group requirement_assigned_object requirement_assigned_object.items -> requirement_assigned_item = product_definition => component_definition => assembly_component

5.1.1.2 Assembly_requirement_allocation to Assembly_joint (as assigned_to)

MIM element:	PATH
Reference path:	requirement_assignment <- requirement_assigned_object.assigned_group requirement_assigned_object requirement_assigned_object.items -> requirement_assigned_item = shape_aspect shape_aspect => component_feature_joint => assembly_joint

5.1.1.3 Assembly_requirement_allocation to Component_feature (as assigned_to)

MIM element:	PATH
Reference path:	requirement_assignment <- requirement_assigned_object.assigned_group requirement_assigned_object requirement_assigned_object.items -> requirement_assigned_item (requirement_assigned_item = product_definition => component_definition) (requirement_assigned_item = shape_aspect => component_feature)

5.1.1.4 Assembly_requirement_allocation to component_or_feature (as assigned_to)

MIM element:	PATH
Reference path:	requirement_assignment <- requirement_assigned_object.assigned_group requirement_assigned_object requirement_assigned_object.items -> requirement_assigned_item (requirement_assigned_item = product_definition => component_definition) (requirement_assigned_item = shape_aspect)

5.1.2 Assembly_separation_requirement_allocation

MIM element:	requirement_assignment
Source:	ISO 10303-41 41
Reference path:	requirement_assignment <= characterized_object {[characterized_object.name = 'assembly requirement allocation'] [characterized_object.description = 'assembly separation requirement']}

5.1.2.1 Assembly_separation_requirement_allocation to Assembly_component (as disjoint_assignment)

MIM element:	PATH
Reference path:	requirement_assignment <= group <- group_assignment.assigned_group {group_assignment.role -> object_role object_role.name = 'disjoint assignment'} group_assignment => applied_group_assignment applied_group_assignment.items -> groupable_item groupable_item = product_definition product_definition => component_definition=> assembly_component

5.1.2.2 Assembly_separation_requirement_allocation to Assembly_joint (as disjoint_assignment)

MIM element:

PATH

Reference path:

requirement_assignment <=
group <-
group_assignment.assigned_group
{group_assignment.role -> object_role
object_role.name = 'disjoint assignment'}
group_assignment =>
applied_group_assignment
applied_group_assignment.items ->
groupable_item
(groupable_item = product_definition
product_definition =>
component_definition)
(groupable_item = shape_aspect
shape_aspect =>
component_feature_joint =>
assembly_joint)

5.1.2.3 Assembly_separation_requirement_allocation to Component_feature (as disjoint_assignment)

MIM element:	PATH
Reference path:	requirement_assignment <= group <- group_assignment.assigned_group {group_assignment.role -> object_role object_role.name = 'disjoint assignment'} group_assignment => applied_group_assignment applied_group_assignment.items -> groupable_item (groupable_item = product_definition product_definition => component_definition) (groupable_item = shape_aspect shape_aspect => component_feature)

5.1.2.4 Assembly_separation_requirement_allocation to component_or_feature (as disjoint_assignment)

MIM element:	PATH
Reference path:	requirement_assignment <= group <- group_assignment.assigned_group {group_assignment.role -> object_role object_role.name = 'disjoint assignment'} group_assignment => applied_group_assignment applied_group_assignment.items -> groupable_item (groupable_item = product_definition product_definition => component_definition) (groupable_item = shape_aspect shape_aspect)

5.1.3 Assembly_shield_allocation

MIM element:	assembly_shield_allocation
Source:	ISO 10303-1648
Reference path:	assembly_shield_allocation <= electromagnetic_compatibility_requirement_allocation

5.1.3.1 Assembly_shield_allocation to Physical_shield (as assigned_to)

MIM element:	PATH
Reference path:	assembly_shield_allocation <= electromagnetic_compatibility_requirement_allocation <= requirement_assignment <- requirement_assigned_object.assigned_group requirement_assigned_object requirement_assigned_object.items -> requirement_assigned_item requirement_assigned_item = product_definition => component_definition => assembly_component => physical_component => physical_shield

5.1.3.2 Assembly_shield_allocation to Predefined_requirement_view_definition (as assigned_requirement_property)

MIM element:	PATH
Reference path:	assembly_shield_allocation <= electromagnetic_compatibility_requirement_allocation <= requirement_assignment <- assigned_requirement.assigned_group assigned_requirement assigned_requirement.items -> product_definition => predefined_requirement_view_definition

5.1.4 Electromagnetic_compatibility_requirement_allocation

MIM element:	electromagnetic_compatibility_requirement_allocation
Source:	ISO 10303-1648
Reference path:	{electromagnetic_compatibility_requirement_allocation <= requirement_assignment <= characterized_object {characterized_object.name = 'assembly requirement allocation'}}

5.1.5 Interface_component_allocation

MIM element:	product_definition_relationship
Source:	ISO 10303-41
Reference path:	{product_definition_relationship product_definition_relationship.name = 'interface component allocation'}

5.1.5.1 Interface_component_allocation to Interface_component (as mating_solution)

MIM element:

PATH

Reference path:

product_definition_relationship
product_definition_relationship.related_product_definition ->
product_definition
{product_definition
[product_definition =>
component_definition =>
assembly_component =>
physical_component =>
interface_component]}
{product_definition <-
product_definition_relationship.related_product_definition
{product_definition_relationship
product_definition_relationship.name = 'instantiated part'}
product_definition_relationship
product_definition_relationship.relating_product_definition ->
product_definition =>
physical_unit}

5.1.5.2 Interface_component_allocation to Mating_connector_usage (as mating_requirement)

MIM element:	PATH
Reference path:	product_definition_relationship product_definition_relationship.relating_product_definition -> {product_definition product_definition.description = 'mating connector'} product_definition => product_definition_with_associated_documents

5.1.6 Requirement_assignment

This application object, Requirement_assignment, is defined in the module requirement_assignment. This mapping section extends the mapping of Requirement_assignment, to include assertions defined in this module.

5.1.6.1 Requirement_assignment to Assembly_component (as assigned_to)

Reference path:

requirement_assignment <-
requirement_assigned_object.assigned_group
requirement_assigned_object
requirement_assigned_object.items ->
requirement_assigned_item
requirement_assigned_item *> apra_requirement_assigned_item
apra_requirement_assigned_item = product_definition
product_definition =>
component_definition =>
assembly_component

5.1.6.2 Requirement_assignment to Assembly_joint (as assigned_to)

Reference path:

requirement_assignment <-
requirement_assigned_object.assigned_group
requirement_assigned_object
requirement_assigned_object.items ->
requirement_assigned_item
requirement_assigned_item *> apra_requirement_assigned_item
apra_requirement_assigned_item = shape_aspect
shape_aspect =>
component_feature_joint =>
assembly_joint

5.1.6.3 Requirement_assignment to Component_feature (as assigned_to)

Reference path:

5.1.6.4 Requirement_assignment to component_or_feature (as assigned_to)

Reference path:

5.1.6.5 Requirement_assignment to Physical_shield (as assigned_to)

Reference path:

5.1.7 Thermal_requirement_allocation

MIM element:	thermal_requirement_allocation
Source:	ISO 10303-1648
Reference path:	thermal_requirement_allocation <= requirement_assignment <= characterized_object {characterized_object characterized_object.name = 'assembly requirement allocation'}

5.1.7.1 Thermal_requirement_allocation to Predefined_requirement_view_definition (as assigned_requirement_property)

MIM element:	PATH
Reference path:	thermal_requirement_allocation <= requirement_assignment <- assigned_requirement.assigned_group assigned_requirement assigned_requirement.items -> product_definition => predefined_requirement_view_definition

5.1.7.2 Thermal_requirement_allocation to Thermal_component (as assigned_to)

MIM element:

PATH

Reference path:

thermal_requirement_allocation <=
requirement_assignment <-
requirement_assigned_object.assigned_group
requirement_assigned_object
requirement_assigned_object.items ->
requirement_assigned_item
requirement_assigned_item = product_definition
{product_definition
product_definition.description = 'thermal component'}
product_definition =>
component_definition =>
assembly_component =>
thermal_component