4 Information requirements

This clause specifies the information requirements for the Assembly module with subassembly application module. The information requirements are specified as the Application Reference Model (ARM) of this application module.

NOTE 1  A graphical representation of the information requirements is given in Annex C.

NOTE 2  The mapping specification is specified in 5.1. It shows how the information requirements are met by using common resources and constructs defined or imported in the MIM schema of this application module.

This clause defines the information requirements to which implementations shall conform using the EXPRESS language as defined in ISO 10303-11. The following begins the Assembly_module_with_subassembly_arm schema and identifies the necessary external references.

4.1 Required AM ARM

The following EXPRESS interface statement specifies the elements imported from the ARM of another application module.

EXPRESS specification:

*)
USE FROM Assembly_module_design_arm;    --  ISO/TS 10303-1636
(*



NOTE 1   The schemas referenced above are specified in the following part of ISO 10303:

Assembly_module_design_arm

ISO/TS 10303-1636

NOTE 2   See Annex C, Figures C.1and C.2 for a graphical representation of this schema.

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 Assembly_module_component   

An Assembly_module_component is a type of Physical_component and a type of Single_instance. The Assembly_module_component represents the inclusion of a specific product version in the associated assembly.

NOTE 1   Assembly_module_component may be useful in a vertically integrated concurrent engineering environment, where full data sharing is allowed, as it permits visibility into the design definition of the component.

NOTE 2   An enterprise could use this capability in the case of co-design of assembly and integrated circuits.

NOTE 3   Hierarchical physical design does not require this capability, but this is the most explicit way to support hierarchical electrical traceability.

EXAMPLE    Consider a daughter board instance as an Assembly_module_component. The design organization maintains explicit traceability between the design of the mother-board and the design of the daughter-board.

EXPRESS specification:

*)
ENTITY Assembly_module_component
  SUBTYPE OF (Physical_component, Single_instance);
  SELF\Definition_based_product_occurrence.derived_from : Assembly_module_design_view;
DERIVE
  usage_view : Assembly_module_usage_view := derived_from\Part_design_view.usage_view;
INVERSE
  access_mechanisms : SET[2:?] OF Assembly_module_component_terminal FOR associated_definition;
WHERE
  WR1: NOT EXISTS(SELF\Product_view_definition.name);
  WR2: usage_view = access_mechanisms[1]\Assembly_module_component_terminal.definition\Assembly_module_terminal.associated_definition;
END_ENTITY;
(*

Attribute definitions:

derived_from: specifies the role of the Assembly_module_design_view for the Assembly_module_component.

usage_view: specifies the role of the Assembly_module_usage_view for the Assembly_module_component.

access_mechanisms: specifies an inverse relationship that specifies that the existence of the Assembly_module_component is dependent on the existence of the Assembly_module_component_terminal that specifies the Assembly_module_component as its associated_definition. There shall be two or more Assembly_module_component_terminal for an Assembly_module_component.

Formal propositions:

WR1: The name shall not be populated.

WR2: The Assembly_module_usage_view referenced by usage_view shall also be referenced by the definition of the Assembly_module_component_terminal that references the Assembly_module_component.

4.2.2 Assembly_module_component_terminal   

EXPRESS specification:

*)
ENTITY Assembly_module_component_terminal
  SUBTYPE OF (Physical_component_terminal);
  SELF\Component_feature.associated_definition : Assembly_module_component;
DERIVE
  SELF\Component_feature.definition : Component_path_shape_element := assigned_component_path_shape_element;
INVERSE
  assigned_component_path_shape_element : Component_path_shape_element FOR component_shape_element;
WHERE
  WR1: NOT EXISTS(SELF\Shape_element.description);
  WR2: 'PHYSICAL_COMPONENT_FEATURE_ARM.PHYSICAL_COMPONENT_TERMINAL' IN TYPEOF(definition);
END_ENTITY;
(*

Attribute definitions:

associated_definition: specifies the role of the Assembly_module_component for the Assembly_module_component_terminal.

definition: specifies the role of the Assembly_module_terminal for the Assembly_module_component_terminal.

assigned_component_path_shape_element: specifies an inverse relationship that specifies that the existence of the Assembly_module_component_terminal is dependent on the existence of the Component_path_shape_element that specifies the Assembly_module_component_terminal as its component_shape_element.

Formal propositions:

WR1: The description shall not be populated.

WR2: The definition shall be a Physical_component_feature.

© ISO 2019 — All rights reserved