4 Information requirements

This clause specifies the information requirements for the Assembly physical requirement allocation 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_physical_requirement_allocation_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 Assembly_physical_interface_requirement_arm;    --  ISO/TS 10303-1647



USE FROM Assembly_technology_arm;    --  ISO/TS 10303-1649



USE FROM Discrete_shield_arm;    --  ISO/TS 10303-1744
(*



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

Assembly_physical_interface_requirement_arm	ISO/TS 10303-1647
Assembly_technology_arm	ISO/TS 10303-1649
Discrete_shield_arm	ISO/TS 10303-1744

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

4.2 ARM type definitions

This subclause specifies the ARM types for this application module. The ARM types and definitions are specified below.

4.2.1 apra_requirement_assignment_item   

The apra_requirement_assignment_item type is an extension of the requirement_assignment_item type. It adds the data types component_or_feature, and Physical_shield to the list of alternate data types.

EXPRESS specification:

*)
TYPE apra_requirement_assignment_item = SELECT BASED_ON requirement_assignment_item WITH
   (component_or_feature,
    Physical_shield);
END_TYPE;
(*

4.2.2 component_or_feature   

The component_or_feature type is an extensible list of alternate data types that allows for the designation of the data types Assembly_component, Assembly_joint, and Component_feature.

NOTE   The list of entity data types may be extended in application modules that use the constructs of this module.

EXPRESS specification:

*)
TYPE component_or_feature = EXTENSIBLE GENERIC_ENTITY SELECT
   (Assembly_component,
    Assembly_joint,
    Component_feature);
END_TYPE;
(*

4.3 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.3.1 Assembly_requirement_allocation   

EXPRESS specification:

*)
ENTITY Assembly_requirement_allocation
  SUBTYPE OF (Requirement_assignment);
  SELF\Requirement_assignment.assigned_to : component_or_feature;
END_ENTITY;
(*

Attribute definitions:

assigned_to: an attribute inherited from Requirement_assignment that specifies a component_or_feature for the Assembly_requirement_allocation.

4.3.2 Assembly_separation_requirement_allocation   

An Assembly_separation_requirement_allocation is a type of Assembly_requirement_allocation. An Assembly_separation_requirement_allocation provides for the physical spacing required among components of the assembly. The Assembly_separation_requirement_allocation is for the purpose of specifying separation between items based on the Predefined_requirement_view_definition.

NOTE    Multiple members of this entity may be populated in order to specify all the sets with which a given set will be disjoint, either thermally or electromagnetically.

EXAMPLE    A typical usage of this AO is to reference a member of Layout_spacing_requirement as the requirement inherited from Assembly_requirement_allocation.

EXPRESS specification:

*)
ENTITY Assembly_separation_requirement_allocation
  SUBTYPE OF (Assembly_requirement_allocation);
  disjoint_assignment : SET[1:?] OF component_or_feature;
END_ENTITY;
(*

Attribute definitions:

disjoint_assignment: specifies a role of the component_or_feature for the Assembly_separation_requirement_allocation. There shall be one or more component_or_feature for the Assembly_separation_requirement_allocation. The disjoint_assignment shall be applied pairwise.

Informal propositions:

IP1: The type of characteristic inherited from assembly requirement allocation attribute requirement shall be Length_data_element.

4.3.3 Assembly_shield_allocation   

An Assembly_shield_allocation is a type of Requirement_assignment that assigns a Predefined_requirement_view_definition to a Physical_shield.

NOTE    Typical requirements are electromagnetic although other domains such as mechanical may be allocated.

EXPRESS specification:

*)
ENTITY Assembly_shield_allocation
  SUBTYPE OF (Requirement_assignment);
  SELF\Requirement_assignment.assigned_to : Physical_shield;
  SELF\Requirement_assignment.assigned_requirement RENAMED assigned_requirement_property : Predefined_requirement_view_definition;
WHERE
  WR1: assigned_requirement_property\Product_view_definition.initial_context\Initial_view_definition_context.application_domain = ps_initial_application_domain_enumeration.electrical;
END_ENTITY;
(*

Attribute definitions:

assigned_to: specifies a role of the Physical_shield for the Assembly_shield_allocation.

assigned_requirement_property: specifies a role of the Predefined_requirement_view_definition for the Assembly_shield_allocation.

Formal propositions:

WR1: The application_domain of initial_context of assigned_requirement_property shall be set to 'electrical'.

4.3.4 Electromagnetic_compatibility_requirement_allocation   

EXPRESS specification:

*)
ENTITY Electromagnetic_compatibility_requirement_allocation
  SUBTYPE OF (Assembly_requirement_allocation);
END_ENTITY;
(*

4.3.5 Interface_component_allocation   

EXPRESS specification:

*)
ENTITY Interface_component_allocation;
  mating_solution : Interface_component;
  mating_requirement : Mating_connector_usage;
END_ENTITY;
(*

Attribute definitions:

mating_solution: specifies the role of the Interface_component for the Interface_component_allocation.

mating_requirement: specifies the role of the Mating_connector_usage for the Interface_component_allocation.

4.3.6 Thermal_requirement_allocation   

EXPRESS specification:

*)
ENTITY Thermal_requirement_allocation
  SUBTYPE OF (Assembly_requirement_allocation);
  SELF\Requirement_assignment.assigned_to : Thermal_component;
  SELF\Requirement_assignment.assigned_requirement RENAMED assigned_requirement_property : Predefined_requirement_view_definition;
WHERE
  WR1: assigned_requirement_property\Product_view_definition.initial_context\Initial_view_definition_context.application_domain = ps_initial_application_domain_enumeration.thermal;
END_ENTITY;
(*

Attribute definitions:

assigned_to: specifies the role of the Thermal_component for the Thermal_requirement_allocation.

assigned_requirement_property: specifies the role of the Predefined_requirement_view_definition for the Thermal_requirement_allocation.

Formal propositions:

WR1: The application_domain of initial_context of assigned_requirement_property shall be set to 'thermal'.

© ISO 2018 — All rights reserved