Application module: Assembly physical interface requirement ISO/TS 10303-1647: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
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 definition

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

4 Information requirements

This clause specifies the information requirements for the Assembly physical interface requirement 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_interface_requirement_arm schema and identifies the necessary external references.

EXPRESS specification:

*)
SCHEMA Assembly_physical_interface_requirement_arm;
(*

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_functional_interface_requirement_arm;    --  ISO/TS 10303-1635

USE FROM Layered_3d_shape_arm;    --  ISO/TS 10303-1694

USE FROM Printed_physical_layout_template_arm;    --  ISO/TS 10303-1737

REFERENCE FROM Requirement_decomposition_arm    --  ISO/TS 10303-1740
  (get_rvd);
(*

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

Assembly_functional_interface_requirement_arm ISO/TS 10303-1635
Layered_3d_shape_arm ISO/TS 10303-1694
Printed_physical_layout_template_arm ISO/TS 10303-1737
Requirement_decomposition_arm ISO/TS 10303-1740

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 apir_requirement_assignment_item   EXPRESS-G

The apir_requirement_assignment_item type is an extension of the requirement_assignment_item type. It adds the data types Mating_connector_termination, Part_terminal, and Termination_constraint to the list of alternate data types.

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

EXPRESS specification:

*)
TYPE apir_requirement_assignment_item = EXTENSIBLE GENERIC_ENTITY SELECT BASED_ON requirement_assignment_item WITH
   (Mating_connector_termination,
    Part_terminal,
    Termination_constraint);
END_TYPE;
(*

4.2.2 mating_connector_definition_select   EXPRESS-G

The mating_connector_definition_select type allows for the designation of the data types Packaged_part_terminal and Printed_part_template_terminal.

EXPRESS specification:

*)
TYPE mating_connector_definition_select = SELECT
   (Packaged_part_terminal,
    Printed_part_template_terminal);
END_TYPE;
(*

4.2.3 three_dimensional_shape   EXPRESS-G

The three_dimensional_shape type allows for the designation of the data types Advanced_brep_shape_representation, Curve_swept_solid, and Geometrically_bounded_surface_shape_representation.

EXPRESS specification:

*)
TYPE three_dimensional_shape = SELECT
   (Advanced_brep_shape_representation,
    Curve_swept_solid,
    Geometrically_bounded_surface_shape_representation);
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 Interface_requirement   EXPRESS-GMapping table

An Interface_requirement is a type of Predefined_requirement_view_definition. An Interface_requirement may specify either the assembly interface to the next higher assembly or a physical layer of a protocol.

EXPRESS specification:

*)
ENTITY Interface_requirement
  SUBTYPE OF (Predefined_requirement_view_definition);
  interface_to_next_higher_assembly : OPTIONAL Next_higher_assembly_interface_requirement;
  reference_protocol : OPTIONAL Protocol_physical_layer_definition;
WHERE
  WR1: SELF\Product_view_definition.initial_context.life_cycle_stage = 'design';
END_ENTITY;
(*

Attribute definitions:

interface_to_next_higher_assembly: specifies the role of the Next_higher_assembly_interface_requirement for the Interface_requirement. This specifies the component in the next assembly that is the interface. The value of this attribute need not be specified.

reference_protocol: specifies the role of the Protocol_physical_layer_definition for the Interface_requirement. This specifies the physical layer of a protocol that is to be supported by the interface. The value of this attribute need not be specified.

Formal propositions:

WR1: The Product_view_definition.initial_context.life_cycle_stage shall be 'design'.

4.3.2 Mating_connector_placement_relationship   EXPRESS-GMapping table

A Mating_connector_placement_relationship is an association between the connector that the interface connector on the assembly must mate with in the next higher assembly, and the resultant placement of that mating connector in the assembly being designed for test and evaluation. The evaluation may include fit checks and evaluation of other material properties. The application of Mating_connector_placement_relationship is limited to three-dimensional geometric systems.

EXPRESS specification:

*)
ENTITY Mating_connector_placement_relationship;
  placed_connector : Mating_connector_usage;
  interface_context : Next_higher_assembly_interface_requirement;
  connector_placement : Axis_placement;
END_ENTITY;
(*

Attribute definitions:

placed_connector: specifies the role of the Mating_connector_usage for the Mating_connector_placement_relationship.

interface_context: specifies the role of the Next_higher_assembly_interface_requirement for the Mating_connector_placement_relationship. The coordinated system of the shape representing the Next_higher_assembly_interface_requirement shall be congruent with the coordinate system of the assembly being designed.

connector_placement: specifies the role of the Axis_placement for the Mating_connector_placement_relationship. The Axis_placement shall be an Axis_placement_3d.

4.3.3 Mating_connector_termination   EXPRESS-GMapping table

A Mating_connector_termination is a single terminal of a Mating_connector_usage.

EXPRESS specification:

*)
ENTITY Mating_connector_termination;
  name : STRING;
  definition : mating_connector_definition_select;
  accessed_connector : Mating_connector_usage;
DERIVE
  signal_definition : SET[0:?] OF Requirement_view_definition := get_rvd(SELF, 'signal definition');
UNIQUE
  UR1: definition, accessed_connector;
WHERE
  WR1: (SIZEOF(signal_definition) <= 1);
END_ENTITY;
(*

Attribute definitions:

name: the words by which the Mating_connector_termination is known.

definition: specifies the role of the mating_connector_definition_select for the Mating_connector_termination. The definition specifies either a Packaged_part_terminal or a Printed_part_template_terminal for the Mating_connector_termination.

accessed_connector: specifies the role of the Mating_connector_usage for the Mating_connector_termination.

signal_definition: specifies the role of the Requirement_view_definition for the Mating_connector_termination. The value of this attribute need not be specified.

Formal propositions:

UR1: The combination of accessed_connector and definition shall be unique within a population of Mating_connector_termination.

WR1: If signal_definition is provided then its size shall be one.

4.3.4 Mating_connector_usage   EXPRESS-GMapping table

A Mating_connector_usage is a type of Product_view_definition. A Mating_connector_usage is a connector on the next higher assembly with which a connector on the assembly must mate. A Mating_connector_usage may be specified in the role of mating_requirement by an Interface_component_allocation.

EXPRESS specification:

*)
ENTITY Mating_connector_usage
  SUBTYPE OF (Product_view_definition);
  definition : Product_view_definition;
  reference_designation : OPTIONAL STRING;
INVERSE
  placement_context : Mating_connector_placement_relationship FOR placed_connector;
END_ENTITY;
(*

Attribute definitions:

definition: specifies the Product_view_definition for the Mating_connector_usage. The definition specifies a Specification_definition, a Packaged_connector, or a Printed_connector_template for the Mating_connector_usage.

reference_designation: specifies the string for the Mating_connector_usage. The reference_designation specifies the name that serves as the identifier of the location of the Mating_connector_usage in the next level of assembly. The value of this attribute need not be specified.

placement_context: specifies an inverse relationship that specifies that the existence of the Mating_connector_usage is dependent on the existence of the Mating_connector_placement_relationship that specifies the Mating_connector_usage as its placed_connector.

4.3.5 Next_higher_assembly_interface_requirement   EXPRESS-GMapping table

A Next_higher_assembly_interface_requirement is an association between the version of the next higher assembly and a shape that simulates the fit characteristics of the next higher assembly. The coordinate system of the shape is congruent with the coordinate system of the current design. The shape simulates a maximum material condition state of the next higher assembly.

EXPRESS specification:

*)
ENTITY Next_higher_assembly_interface_requirement;
  shape : three_dimensional_shape;
  version_of_next_higher_assembly : Product_version;
END_ENTITY;
(*

Attribute definitions:

shape: specifies the three_dimensional_shape for the Next_higher_assembly_interface_requirement. The shape specifies either an Advanced_brep_shape_representation, or a Curve_swept_solid, or a Geometrically_bounded_surface_shape_representation for the Next_higher_assembly_interface_requirement.

version_of_next_higher_assembly: specifies the role of the Product_version for the Next_higher_assembly_interface_requirement.

4.3.6 Protocol_requirement_allocation_to_part_terminal   EXPRESS-GMapping table

A Protocol_requirement_allocation_to_part_terminal is a type of Requirement_assignment for which the Interface_requirement is the allocated requirement. A Protocol_requirement_allocation_to_part_terminal is the relationship between a Part_terminal and a Functional_unit_usage_view_terminal_definition that is included by a design or support activity. The Interface_requirement specifies a Protocol_physical_layer_definition in order to make the relationship unambiguous.

EXPRESS specification:

*)
ENTITY Protocol_requirement_allocation_to_part_terminal
  SUBTYPE OF (Requirement_assignment);
  SELF\Requirement_assignment.assigned_to : Part_terminal;
  protocol_signal : Functional_unit_usage_view_terminal_definition;
  SELF\Requirement_assignment.assigned_requirement RENAMED assigned_requirement_property : Interface_requirement;
WHERE
  WR1: EXISTS(assigned_requirement_property\Interface_requirement.reference_protocol);
  WR2: protocol_signal IN assigned_requirement_property\Interface_requirement.reference_protocol.host_functional_definition\Functional_unit_usage_view.access_mechanism;
END_ENTITY;
(*

Attribute definitions:

assigned_to: specifies the role of the Part_terminal for the Protocol_requirement_allocation_to_part_terminal.

protocol_signal: specifies the role of the Functional_unit_usage_view_terminal_definition for the Protocol_requirement_allocation_to_part_terminal.

assigned_requirement_property: specifies the role of the Interface_requirement for the Protocol_requirement_allocation_to_part_terminal.

Formal propositions:

WR1: The reference_protocol of assigned_requirement_property shall be provided.

WR2: The protocol_signal shall be a member of access_mechanism of host_functional_definition of reference_protocol of assigned_requirement_property.

4.3.7 Termination_constraint   EXPRESS-GMapping table

A Termination_constraint is a type of Constraint_occurrence. A Termination_constraint is a constraint that requires a set of two or more Mating_connector_terminations to satisfy a Predefined_requirement_view_definition.

EXPRESS specification:

*)
ENTITY Termination_constraint
  SUBTYPE OF (Constraint_occurrence);
  constrained_termination : SET[2:?] OF Mating_connector_termination;
DERIVE
  termination_usage_constraint : SET[0:?] OF Requirement_view_definition := get_rvd(SELF, 'termination usage constraint');
WHERE
  WR1: (SIZEOF(termination_usage_constraint) <= 1);
END_ENTITY;
(*

Attribute definitions:

constrained_termination: specifies the role of the Mating_connector_termination for the Termination_constraint. There shall be two or more Mating_connector_terminations for the Termination_constraint.

termination_usage_constraint: specifies the role of the Requirement_view_definition for the Termination_constraint. The value of this attribute need not be specified.

Formal propositions:

WR1: If termination_usage_constraint exists then its size shall be one.



*)
END_SCHEMA;  -- Assembly_physical_interface_requirement_arm
(*


© ISO 2019 — All rights reserved