4 Information requirements

This clause specifies the information requirements for the Assembly module usage view 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_usage_view_arm schema and identifies the necessary external references.

4.1 Required AM ARMs

The following EXPRESS interface statements specify the elements imported from the ARMs of other application modules.

EXPRESS specification:

*)
USE FROM Functional_assignment_to_part_arm;    --  ISO/TS 10303-1674



USE FROM Part_external_reference_arm;    --  ISO/TS 10303-1711



USE FROM Part_feature_function_arm;    --  ISO/TS 10303-1712
(*



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

Functional_assignment_to_part_arm	ISO/TS 10303-1674
Part_external_reference_arm	ISO/TS 10303-1711
Part_feature_function_arm	ISO/TS 10303-1712

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_interface_terminal   

An Assembly_module_interface_terminal is a type of Assembly_module_terminal. An Assembly_module_interface_terminal is the terminal accessed by an external application. The Assembly_module_interface_terminal is not supported by all systems, but is supplied for structural integrity in a multi-level hierarchy.

EXPRESS specification:

*)
ENTITY Assembly_module_interface_terminal
  SUBTYPE OF (Assembly_module_terminal);
DERIVE
  SELF\Part_terminal.interface_or_join_terminal : interface_or_join_terminal_enumeration := interface_or_join_terminal_enumeration.interface_terminal;
END_ENTITY;
(*

Attribute definitions:

interface_or_join_terminal: the terminal shall be an interface_terminal.

4.2.2 Assembly_module_terminal   

NOTE 1   The Assembly_module_terminal supports multi-level design, analysis, and verification in a multi-discipline environment. Explicit description of Assembly_module_terminals allows connectivity requirements to be explicitly stated and interference requirements to be identified early in the design and development cycle. The availability of explicit connector data provides the ability to more easily distinguish terminals that are physically part of different connectors, as well as letting the connector location transform locate all terminals for that connector.

NOTE 2   If there is a connector associated with the terminal, then the terminal is actually a terminal of that connector and not separate from that connector.

EXPRESS specification:

*)
ENTITY Assembly_module_terminal
  SUBTYPE OF (Part_terminal);
  SELF\Part_feature.associated_definition : Assembly_module_usage_view;
  reference_terminal : OPTIONAL Part_terminal;
  related_connector : OPTIONAL Next_assembly_usage;
WHERE
  WR1: NOT EXISTS(related_connector) OR (SELF\Shape_element.associated_definition = related_connector\Product_occurrence_definition_relationship.related_view);
  WR2: NOT EXISTS(related_connector) OR EXISTS(related_connector.location_indicator);
  WR3: NOT EXISTS(reference_terminal) OR (reference_terminal\Part_terminal.interface_or_join_terminal :=: interface_or_join_terminal_enumeration.interface_terminal);
END_ENTITY;
(*

Attribute definitions:

associated_definition: the Assembly_module_usage_view that has the Assembly_module_terminal.

reference_terminal: a Part_terminal that is an interface terminal of a Part_view_definition that is referenced by the related_connector. The value of this attribute need not be specified.

related_connector: a Next_assembly_usage that relates to a Product_occurrence that is defined by a Part_view_definition that is the associated_definition of the reference_terminal. The value of this attribute need not be specified.

Formal propositions:

WR1: If the related_connector exists then associated_definition shall be the assembly for the related_connector.

WR2: If the related_connector exists then location_indicator for that connector shall exist.

WR3: If the reference_terminal is defined, it shall be an interface terminal.

Informal propositions:

IP1: If a related_connector is specified, the position, shape, and orientation of the Assembly_module_terminal shall be overriden by the reference_terminal position, shape, and orientation.

IP2: A related_connector shall be specified if and only if the reference_terminal is specified.

4.2.3 Assembly_module_usage_view   

An Assembly_module_usage_view is a type of Part_usage_view. An Assembly_module_usage_view provides additional domain knowledge for the design organization.

NOTE 1   The Assembly_module_usage_view supports intellectual property protection. A design organization can control the amount of data they provide to a licensee or purchaser by including only a specifically tailored set of data in a usage view.

NOTE 2   Shape information is provided by Physical_unit_3d_shape_model or by Physical_unit_planar_shape_model.

NOTE 3   In order to exchange exact connector data as part of the usage view, members of Assembly_component_relationship may be populated to explicitly relate a connector definition to the usage view. Note that the connector view included may just be that required to satisfy the interface definition requirements and may not be the same connector view that exists in the design department archive for internal design purposes. WR1 inherited from Part_view_definition constrains the members of Assembly_module_usage_view for this purpose.

EXAMPLE 1   This data can include the information currently included in an interface control drawing (ICD). Other data included in an ICD might be members of Protocol_physical_layer_definition.

EXAMPLE 2   Figure 1 illustrates that the information in an Assembly_module_usage_view can be different from the information in a design view. The information in this illustration is sufficient to analyse airflow characteristics and interference characteristics, as well as information related to the connectors in the design.

EXPRESS specification:

*)
ENTITY Assembly_module_usage_view
  SUBTYPE OF (Part_usage_view);
  implemented_function : OPTIONAL Functional_unit_usage_view;
INVERSE
  access_mechanisms : SET[0:?] OF Assembly_module_terminal FOR associated_definition;
WHERE
  WR1: NOT EXISTS(SELF\Product_view_definition.additional_characterization);
END_ENTITY;
(*

Attribute definitions:

implemented_function: specifies the role of the Functional_unit_usage_view for the Assembly_module_usage_view. The value of this attribute need not be specified.

access_mechanisms: specifies an inverse relationship that specifies that the existence of the Assembly_module_usage_view is dependent on the existence of the Assembly_module_terminal that specifies the Assembly_module_usage_view as its associated_definition. There shall be zero or more Assembly_module_terminals for an Assembly_module_usage_view.

Formal propositions:

WR1: The additional_characterization shall not be populated.

Informal propositions:

IP1: The function implemented shall be the function whose terminals are mapped to the terminals of this assembly module usage view.

© ISO 2018 — All rights reserved