4 Information requirements

This clause specifies the information requirements for the Part feature location 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 Part_feature_location_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 Shape_feature_arm;    --  ISO/TS 10303-1764



USE FROM Physical_unit_usage_view_arm;    --  ISO/TS 10303-1732
(*



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

Shape_feature_arm	ISO/TS 10303-1764
Physical_unit_usage_view_arm	ISO/TS 10303-1732

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 feature_or_non_feature_usage   

The feature_or_non_feature_usage type is an extensible list of alternate data types. Additional alternate data types are specified in select data types that extend the feature_or_non_feature_usage type.

NOTE   This empty extensible select requires extension in a further module to ensure that entities that refer to it have at least one valid instantiation.

EXPRESS specification:

*)
TYPE feature_or_non_feature_usage = EXTENSIBLE GENERIC_ENTITY SELECT;
END_TYPE;
(*

4.2.2 usage_concept   

The usage_concept type is an extensible list of alternate data types that allows for the designation of the data type Part_feature.

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

EXPRESS specification:

*)
TYPE usage_concept = EXTENSIBLE GENERIC_ENTITY SELECT
   (Part_feature);
END_TYPE;
(*

4.3 ARM entity definition

This subclause specifies the ARM entity for this module. The ARM entity is an atomic element that embodies a unique application concept and contains attributes specifying the data elements of the entity. The ARM entity and definition is specified below.

4.3.1 Usage_concept_usage_relationship   

A Usage_concept_usage_relationship is a type of Geometric_placement_operation A Usage_concept_usage_relationship is the association between a usage_concept as a source and a feature_or_non_feature_usage as a target. This relationship positions and orients the geometric model of the source into the model of the target using a transformation.

EXPRESS specification:

*)
ENTITY Usage_concept_usage_relationship
  SUBTYPE OF (Geometric_placement_operation);
  SELF\Geometric_placement_operation.template_definition RENAMED associated_shape_definition : Geometric_model;
  associated_usage : usage_concept;
  associating_usage_shape : feature_or_non_feature_usage;
INVERSE
  composed_model : SET[1:1] OF Geometric_model FOR items;
WHERE
  WR1: associating_usage_shape = composed_model[1];
  WR2: NOT EXISTS(SELF\Representation_item.name);
  WR3: ('ELEMENTAL_GEOMETRIC_SHAPE_ARM.GEOMETRIC_PLACEMENT' IN TYPEOF(SELF)) OR ('ELEMENTAL_GEOMETRIC_SHAPE_ARM.GEOMETRIC_OPERATOR_TRANSFORMATION' IN TYPEOF(SELF));
  WR4: NOT('CONTEXTUAL_SHAPE_POSITIONING_ARM.GEOMETRIC_PLACEMENT_MODEL' IN TYPEOF(composed_model[1]));
END_ENTITY;
(*

Attribute definitions:

associated_shape_definition: specifies the role of the Geometric_model for the Usage_concept_usage_relationship.

associated_usage: specifies the role of the usage_concept for the Usage_concept_usage_relationship.

associating_usage_shape: specifies the role of the feature_or_non_feature_usage for the Usage_concept_usage_relationship.

composed_model: an inverse relationship that specifies that the existence of the Usage_concept_usage_relationship is dependent on the the existence of the Geometric_model that specifies the Usage_concept_usage_relationship as its items. There shall exist exactly one Geometric_model for the Usage_concept_usage_relationship.

Formal propositions:

WR1: The associating_usage_shape shall refer same instance as composed_model.

WR2: The name shall not be populated.

WR3: The Usage_concept_usage_relationship shall be a complex with either Geometric_placement or Geometric_operator_transformation.

WR4: The composed_model shall not be of type Geometric_placement_model.

Informal propositions:

IP1: All necessary geometric model relationships to support this requirement shall be included.

© ISO 2018 — All rights reserved