ISO/TS 10303-1112:2019 Specification control


Application module: Specification control	ISO/TS 10303-1112:2019(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
4.4 ARM function definition
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
5.2.3 MIM rule definitions

A MIM short names
B Information object registration
C ARM EXPRESS-G
D MIM EXPRESS-G
E Computer interpretable listings
F Application module implementation and usage guide
G 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 attribute 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 are not supported in the present version of the application modules. However, use of predefined templates /MAPPING_OF/, /SUBTYPE/, and /SUPERTYPE/ is supported.

5.1.1 Breakdown_node_relationship

MIM element:	product_definition_usage
Source:	ISO 10303-44

5.1.1.1 description

MIM element:	product_definition_relationship.description
Source:	ISO 10303-41
Reference path:	product_definition_usage <= product_definition_relationship product_definition_relationship.description

5.1.1.2 relation_type

MIM element:	product_definition_relationship.name
Source:	ISO 10303-41
Reference path:	product_definition_usage <= product_definition_relationship product_definition_relationship.name

5.1.1.3 Breakdown_node_relationship to Alternative_solution (as relating)

MIM element:	PATH
Reference path:	product_definition_usage <= product_definition_relationship product_definition_relationship.relating_product_definition -> product_definition {product_definition.frame_of_reference -> product_definition_context <= application_context_element application_context_element.name = 'alternative definition'}

5.1.1.4 Breakdown_node_relationship to Breakdown_element (as related)

MIM element:	PATH
Reference path:	product_definition_usage <= product_definition_relationship product_definition_relationship.related_product_definition -> product_definition product_definition.formation -> product_definition_formation product_definition_formation.of_product -> /MAPPING_OF(Breakdown_element)/

5.1.1.5 Breakdown_node_relationship to Breakdown_element (as relating)

MIM element:	PATH
Reference path:	product_definition_usage <= product_definition_relationship product_definition_relationship.relating_product_definition -> product_definition product_definition.formation -> product_definition_formation product_definition_formation.of_product -> /MAPPING_OF(Breakdown_element)/

5.1.1.6 Breakdown_node_relationship to Functional_element_definition (as related)

MIM element:	PATH
Reference path:	product_definition_usage <= product_definition_relationship product_definition_relationship.related_product_definition -> product_definition {product_definition.frame_of_reference -> product_definition_context <= application_context_element application_context_element.name = 'functional definition'}

5.1.1.7 Breakdown_node_relationship to Functional_element_definition (as relating)

MIM element:	PATH
Reference path:	product_definition_usage <= product_definition_relationship product_definition_relationship.relating_product_definition -> product_definition {product_definition.frame_of_reference -> product_definition_context <= application_context_element application_context_element.name = 'functional definition'}

5.1.1.8 Breakdown_node_relationship to Part_view_definition (as related)

MIM element:	PATH
Reference path:	product_definition_usage <= product_definition_relationship product_definition_relationship.related_product_definition -> product_definition {product_definition.frame_of_reference -> product_definition_context <= application_context_element application_context_element.name = 'part definition'}

5.1.1.9 Breakdown_node_relationship to Part_view_definition (as relating)

MIM element:	PATH
Reference path:	product_definition_usage <= product_definition_relationship product_definition_relationship.relating_product_definition -> product_definition {product_definition.frame_of_reference -> product_definition_context <= application_context_element application_context_element.name = 'part definition'}

5.1.1.10 Breakdown_node_relationship to Physical_element_definition (as related)

MIM element:	PATH
Reference path:	product_definition_usage <= product_definition_relationship product_definition_relationship.related_product_definition -> product_definition {product_definition.frame_of_reference -> product_definition_context <= application_context_element application_context_element.name = 'conceptual definition'}

5.1.1.11 Breakdown_node_relationship to Physical_element_definition (as relating)

MIM element:	PATH
Reference path:	product_definition_usage <= product_definition_relationship product_definition_relationship.relating_product_definition -> product_definition {product_definition.frame_of_reference -> product_definition_context <= application_context_element application_context_element.name = 'conceptual definition'}

5.1.2 Class_breakdown_association

MIM element:	configuration_design
Source:	ISO 10303-44
Rules:	restrict_configuration_design_for_class_breakdown_association

5.1.2.1 description

MIM element:	configuration_design.description
Source:	ISO 10303-44

5.1.2.2 relation_type

MIM element:	configuration_design.name
Source:	ISO 10303-44

5.1.2.3 Class_breakdown_association to Functional_element_definition (as breakdown_element)

MIM element:

PATH

Reference path:

configuration_design
{configuration_design.configuration -> configuration_item
configuration_item.name = 'functional structure item'}
configuration_design.design -> configuration_design_item
configuration_design_item = product_definition
product_definition
{product_definition.frame_of_reference ->
product_definition_context <=
application_context_element
application_context_element.name = 'functional definition'}

5.1.2.4 Class_breakdown_association to Physical_element_definition (as breakdown_element)

MIM element:

PATH

Reference path:

configuration_design
{configuration_design.configuration -> configuration_item
configuration_item.name = 'conceptual structure item'}
configuration_design.design -> configuration_design_item
configuration_design_item = product_definition
product_definition
{product_definition.frame_of_reference ->
product_definition_context <=
application_context_element
application_context_element.name = 'conceptual definition'}

5.1.2.5 Class_breakdown_association to Product_class (as considered_class)

MIM element:	PATH
Reference path:	configuration_design.configuration -> configuration_item {(configuration_item.name = 'functional structure item') (configuration_item.name = 'conceptual structure item')} configuration_item.item_concept -> product_concept => product_class

5.1.3 Complex_node_relationship

MIM element:	product_definition_formation_relationship
Source:	ISO 10303-41

5.1.3.1 description

MIM element:	product_definition_formation_relationship.description
Source:	ISO 10303-41

5.1.3.2 relation_type

MIM element:	product_definition_formation_relationship.name
Source:	ISO 10303-41

5.1.3.3 Complex_node_relationship to Alternative_solution (as related)

MIM element:	PATH
Reference path:	product_definition_formation_relationship.related_product_definition_formation -> product_definition_formation {product_definition_formation.of_product -> product product <- product_related_product_category.products[i] product_related_product_category <= product_category product_category.name='alternative solution'}

5.1.3.4 Complex_node_relationship to Alternative_solution (as relating)

MIM element:	PATH
Reference path:	product_definition_formation_relationship.relating_product_definition_formation -> product_definition_formation {product_definition_formation.of_product -> product product <- product_related_product_category.products[i] product_related_product_category <= product_category product_category.name='alternative solution'}

5.1.3.5 Complex_node_relationship to Breakdown_element (as related)

MIM element:	PATH
Reference path:	product_definition_formation_relationship.related_product_definition_formation -> product_definition_formation product_definition_formation.of_product -> /MAPPING_OF(Breakdown_element)/

5.1.3.6 Complex_node_relationship to Breakdown_element (as relating)

MIM element:	PATH
Reference path:	product_definition_formation_relationship.relating_product_definition_formation -> product_definition_formation product_definition_formation.of_product -> /MAPPING_OF(Breakdown_element)/

5.1.3.7 Complex_node_relationship to Functional_element_definition (as related)

MIM element:	PATH
Reference path:	product_definition_formation_relationship.related_product_definition_formation -> product_definition_formation {product_definition_formation.of_product -> product product <- product_related_product_category.products[i] product_related_product_category <= product_category product_category.name='functionality'}

5.1.3.8 Complex_node_relationship to Functional_element_definition (as relating)

MIM element:	PATH
Reference path:	product_definition_formation_relationship.relating_product_definition_formation -> product_definition_formation {product_definition_formation.of_product -> product product <- product_related_product_category.products[i] product_related_product_category <= product_category product_category.name='functionality'}

5.1.3.9 Complex_node_relationship to Part_view_definition (as related)

MIM element:	PATH
Reference path:	product_definition_formation_relationship.related_product_definition_formation -> product_definition_formation product_definition_formation.of_product -> product {product_definition_formation.of_product -> product product <- product_related_product_category.products[i] product_related_product_category <= product_category product_category.name='part definition'}

5.1.3.10 Complex_node_relationship to Part_view_definition (as relating)

MIM element:	PATH
Reference path:	product_definition_formation_relationship.relating_product_definition_formation -> product_definition_formation product_definition_formation.of_product -> product {product_definition_formation.of_product -> product product <- product_related_product_category.products[i] product_related_product_category <= product_category product_category.name='part definition'}

5.1.3.11 Complex_node_relationship to Physical_element_definition (as related)

MIM element:	PATH
Reference path:	product_definition_formation_relationship.related_product_definition_formation -> product_definition_formation {product_definition_formation.of_product -> product product <- product_related_product_category.products[i] product_related_product_category <= product_category product_category.name='conceptual product'}

5.1.3.12 Complex_node_relationship to Physical_element_definition (as relating)

MIM element:	PATH
Reference path:	product_definition_formation_relationship.relating_product_definition_formation -> product_definition_formation {product_definition_formation.of_product -> product product <- product_related_product_category.products[i] product_related_product_category <= product_category product_category.name='conceptual product'}

5.1.4 Configuration

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

MIM element:	configured_effectivity_assignment
Source:	ISO 1033-1108

5.1.4.1 configuration_type

MIM element:	object_role.description
Reference path:	configured_effectivity_assignment <= effectivity_assignment effectivity_assignment.role -> object_role object_role.description {(object_role.description = 'exception') (object_role.description = 'inherited') (object_role.description = 'local')}

5.1.4.2 inheritance_type

MIM element:	object_role.name
Source:	ISO 10303-41
Reference path:	configured_effectivity_assignment <= effectivity_assignment effectivity_assignment.role -> object_role object_role.name {(object_role.name = 'design') (object_role.name = 'usage')}

5.1.4.3 Configuration to Alternative_solution (as configured_element)

MIM element:	PATH
Reference path:	configured_effectivity_assignment configured_effectivity_assignment.items[1] -> configured_effectivity_item configured_effectivity_item = product_definition product_definition {product_definition.frame_of_reference -> product_definition_context <= application_context_element application_context_element.name = 'alternative definition'}

5.1.4.4 Configuration to Class_condition_association (as is_solution_for)

MIM element:

PATH

Reference path:

configured_effectivity_assignment <=
effectivity_assignment <- effectivity_context_assignment.assigned_effectivity_assignment
{effectivity_context_assignment.role -> effectivity_context_role
effectivity_context_role.name = 'specification based condition'}
effectivity_context_assignment => configured_effectivity_context_assignment
configured_effectivity_context_assignment.items[1] -> configured_effectivity_context_item
configured_effectivity_context_item = product_concept_feature_association

5.1.4.5 Configuration to Class_specification_association (as is_solution_for)

MIM element:

PATH

Reference path:

5.1.5 Design_constraint_association

MIM element:	product_definition_relationship
Source:	ISO 10303-41
Rules:	restrict_product_definitions_for_design_constraint_association
Reference path:	{product_definition_relationship.name = 'design constraint association'}

5.1.5.1 name

MIM element:	product_definition_relationship.description
Source:	ISO 10303-41

5.1.5.2 Design_constraint_association to Alternative_solution (as constrained_object)

MIM element:	PATH
Reference path:	product_definition_relationship.related_product_definition -> product_definition {product_definition.frame_of_reference -> product_definition_context <= application_context_element application_context_element.name = 'alternative definition'}

5.1.5.3 Design_constraint_association to Breakdown_element (as constrained_object)

MIM element:	PATH
Reference path:	product_definition_relationship.related_product_definition -> product_definition {product_definition.frame_of_reference -> product_definition_context <= application_context_element application_context_element.name = 'breakdown definition'}

5.1.5.4 Design_constraint_association to Design_constraint_definition (as constraint_definition)

MIM element:	PATH
Reference path:	product_definition_relationship.relating_product_definition -> product_definition {product_definition.frame_of_reference -> product_definition_context <= application_context_element application_context_element.name = 'design constraint definition'}

5.1.5.5 Design_constraint_association to Functional_element_definition (as constrained_object)

MIM element:	PATH
Reference path:	product_definition_relationship.related_product_definition -> product_definition {product_definition.frame_of_reference -> product_definition_context <= application_context_element application_context_element.name = 'functional definition'}

5.1.5.6 Design_constraint_association to Part_view_definition (as constrained_object)

MIM element:	PATH
Reference path:	product_definition_relationship.related_product_definition -> product_definition {product_definition.frame_of_reference -> product_definition_context <= application_context_element application_context_element.name = 'part definition'}

5.1.5.7 Design_constraint_association to Physical_element_definition (as constrained_object)

MIM element:	PATH
Reference path:	product_definition_relationship.related_product_definition -> product_definition {product_definition.frame_of_reference -> product_definition_context <= application_context_element application_context_element.name = 'conceptual definition'}

5.1.6 Design_constraint_context_association

MIM element:	configuration_design
Source:	ISO 10303-44
Rules:	restrict_configuration_design_for_design_constraint
Reference path:	{configuration_design.name = 'design constraint usage'}

5.1.6.1 Design_constraint_context_association to Design_constraint_definition (as constraint_definition)

MIM element:	PATH
Reference path:	configuration_design.design -> configuration_design_item configuration_design_item = product_definition {product_definition.frame_of_reference -> product_definition_context <= application_context_element application_context_element.name = 'design constraint definition'}

5.1.6.2 Design_constraint_context_association to Product_class (as constraint_context)

MIM element:	PATH
Reference path:	configuration_design {configuration_design.name = 'design constraint usage'} configuration_design.configuration -> configuration_item {configuration_item.name = 'design constraint usage'} configuration_item.item_concept -> product_concept => product_class

5.1.7 Design_constraint_definition

MIM element:	product_definition
Source:	ISO 10303-41
Rules:	constraint_definition_requires_constraint_category
Reference path:	product_definition.frame_of_reference -> product_definition_context product_definition_context <= application_context_element {application_context_element.name = 'design constraint definition'}

5.1.8 Effectivity_assignment

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

5.1.8.1 Effectivity_assignment to Replaced_usage_relationship (as items)

Reference path:

applied_effectivity_assignment.items[i] -> effectivity_item
effectivity_item *> effectivity_specification_for_replacement
effectivity_specification_for_replacement = product_definition_substitute

5.1.9 Ineffectivity_assignment

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

5.1.9.1 Ineffectivity_assignment to Replaced_usage_relationship (as items)

Reference path:

applied_ineffectivity_assignment.items[i] -> effectivity_item
effectivity_item *> effectivity_specification_for_replacement
effectivity_specification_for_replacement = product_definition_substitute

5.1.10 Part_function_association

MIM element:	product_definition_relationship
Source:	ISO 10303-41

5.1.10.1 Part_function_association to Functional_element_definition (as relating_view)

MIM element:	PATH
Reference path:	product_definition_relationship.relating_product_definition -> product_definition {product_definition.frame_of_reference -> product_definition_context <= application_context_element application_context_element.name = 'functional definition'}

5.1.10.2 Part_function_association to Part_view_definition (as related_view)

MIM element:	PATH
Reference path:	product_definition_relationship.related_product_definition -> product_definition {product_definition.frame_of_reference -> product_definition_context <= application_context_element application_context_element.name = 'part definition'}

5.1.11 Part_occurrence_relationship

#1: If the Part_occurrence_relationship is not a Replaced_usage_relationship

MIM element:	product_definition_relationship
Source:	ISO 10303-41

#2: If the Part_occurrence_relationship is a Replaced_usage_relationship

MIM element:	product_definition_substitute
Source:	ISO 10303-41

5.1.11.1 Part_occurrence_relationship to Product_occurrence (as related_view)

#1: If the Part_occurrence_relationship is not a Replaced_usage_relationship

MIM element:	PATH
Reference path:	product_definition_relationship.related_product_definition -> product_definition {product_definition.frame_of_reference -> product_definition_context <= application_context_element application_context_element.name = 'part occurrence'}

#2: If the Part_occurrence_relationship is a Replaced_usage_relationship

MIM element:	PATH
Reference path:	product_definition_substitute product_definition_substitute.substitute_definition -> product_definition {product_definition.frame_of_reference -> product_definition_context <= application_context_element application_context_element.name = 'part occurrence'}

5.1.11.2 Part_occurrence_relationship to Product_occurrence (as relating_view)

#1: If the Part_occurrence_relationship is not a Replaced_usage_relationship

MIM element:	PATH
Reference path:	product_definition_relationship.relating_product_definition -> product_definition {product_definition.frame_of_reference -> product_definition_context <= application_context_element application_context_element.name = 'part occurrence'}

#2: If the Part_occurrence_relationship is a Replaced_usage_relationship

MIM element:	PATH
Reference path:	product_definition_substitute product_definition_substitute.context_relationship -> product_definition_relationship.relating_product_definition -> product_definition {product_definition.frame_of_reference -> product_definition_context <= application_context_element application_context_element.name = 'part occurrence'}

5.1.12 Replaced_usage_relationship

MIM element:	product_definition_substitute
Source:	ISO 10303-41

5.1.12.1 Replaced_usage_relationship to Collected_item_association (as usage_context)

MIM element:	PATH
Reference path:	product_definition_substitute product_definition_substitute.context_relationship -> product_definition_relationship {product_definition_relationship.name = 'collection membership'}

5.1.12.2 Replaced_usage_relationship to instance_usage_context_select (as usage_context)

MIM element:	PATH
Reference path:	product_definition_substitute product_definition_substitute.substitute_definition -> product_definition product_definition.frame_of_reference -> product_definition_context product_definition_context => instance_usage_context_assignment instance_usage_context_assignment.items[i] -> instance_usage_context_select

5.1.12.3 Replaced_usage_relationship to Solution_element (as usage_context)

MIM element:	PATH
Reference path:	product_definition_substitute product_definition_substitute.context_relationship -> product_definition_relationship => product_definition_usage {product_definition_relationship.name = 'realization'}

5.1.13 Specification_category_breakdown_influence

MIM element:	class_usage_effectivity_context_assignment
Source:	ISO 10303-1112

5.1.13.1 Specification_category_breakdown_influence to Class_category_association (as influencing_category)

MIM element:

PATH

Reference path:

class_usage_effectivity_context_assignment <=
effectivity_context_assignment
{effectivity_context_assignment.role ->
effectivity_context_role
effectivity_context_role.name = 'class usage influence'}
effectivity_context_assignment.assigned_effectivity_assignment ->
effectivity_assignment
{effectivity_assignment.assigned_effectivity ->
|effectivity|
effectivity.id = 'class usage'}
effectivity_assignment =>
applied_effectivity_assignment
applied_effectivity_assignment.items[i] ->
effectivity_item
effectivity_item = product_concept_feature_category_usage
product_concept_feature_category_usage

5.1.13.2 Specification_category_breakdown_influence to Functional_element_definition (as influenced_breakdown_node)

MIM element:	PATH
Reference path:	class_usage_effectivity_context_assignment class_usage_effectivity_context_assignment.items[1] -> class_usage_effectivity_context_item class_usage_effectivity_context_item = product_definition {product_definition_formation.of_product -> product product <- product_related_product_category.products[i] product_related_product_category <= product_category product_category.name='functional product'}

5.1.13.3 Specification_category_breakdown_influence to Physical_element_definition (as influenced_breakdown_node)

MIM element:	PATH
Reference path:	class_usage_effectivity_context_assignment class_usage_effectivity_context_assignment.items[1] -> class_usage_effectivity_context_item class_usage_effectivity_context_item = product_definition {product_definition_formation.of_product -> product product <- product_related_product_category.products[i] product_related_product_category <= product_category product_category.name='conceptual product'}