Application module: Process plan ISO/TS 10303-1803: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 entity definitions

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 Process plan 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 Process_plan_arm schema and identifies the necessary external references.

EXPRESS specification:

*)
SCHEMA Process_plan_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 Activity_method_arm;    --  ISO/TS 10303-1049

USE FROM Item_definition_structure_arm;    --  ISO/TS 10303-1345

USE FROM Product_view_definition_arm;    --  ISO/TS 10303-1019

USE FROM Resource_item_arm;    --  ISO/TS 10303-1268

USE FROM Support_resource_arm;    --  ISO/TS 10303-1800

USE FROM Shape_property_assignment_arm;    --  ISO/TS 10303-1032

USE FROM Specification_control_arm;    --  ISO/TS 10303-1112

USE FROM Time_interval_assignment_arm;    --  ISO/TS 10303-1365
(*

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

Activity_method_arm ISO/TS 10303-1049
Item_definition_structure_arm ISO/TS 10303-1345
Product_view_definition_arm ISO/TS 10303-1019
Resource_item_arm ISO/TS 10303-1268
Support_resource_arm ISO/TS 10303-1800
Shape_property_assignment_arm ISO/TS 10303-1032
Specification_control_arm ISO/TS 10303-1112
Time_interval_assignment_arm ISO/TS 10303-1365

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

The pl_additional_application_domain_enumeration provides pre-defined identifiers for the additional application domains of Product_view_definitions.

EXPRESS specification:

*)
TYPE pl_additional_application_domain_enumeration = ENUMERATION BASED_ON additional_application_domain_enumeration WITH
   (process_state);
END_TYPE;
(*

Enumerated item definitions:

process_state: the application domain is process state.

4.2.2 process_operation_input_or_output_select   EXPRESS-G

The process_operation_input_or_output_select type is an extensible list of alternate data types that allows for the designation of the data types Assembly_component_relationship, Part_view_definition, and Product_occurrence.

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

EXPRESS specification:

*)
TYPE process_operation_input_or_output_select = EXTENSIBLE GENERIC_ENTITY SELECT
   (Assembly_component_relationship,
    Part_view_definition,
    Product_occurrence);
END_TYPE;
(*

4.2.3 process_state_relationship_direction   EXPRESS-G

The process_state_relationship_direction type is an identification of the direction of a Process_state_relationship.

EXPRESS specification:

*)
TYPE process_state_relationship_direction = ENUMERATION OF
   (bidirectional_process_state_relationship,
    unidirectional_process_state_relationship);
END_TYPE;
(*

Enumerated item definitions:

bidirectional_process_state_relationship: the direction is bidirectional.

unidirectional_process_state_relationship: the direction is unidirectional.

4.2.4 resource_definition_select   EXPRESS-G

The resource_definition_select type is an extensible list of alternate data types that allows for the designation of the data types Product_occurrence, Part_view_definition, and Resource_requirement_type.

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

EXPRESS specification:

*)
TYPE resource_definition_select = EXTENSIBLE GENERIC_ENTITY SELECT
   (Product_occurrence,
    Part_view_definition,
    Resource_requirement_type);
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 Process_operation_definition   EXPRESS-GMapping table

A Process_operation_definition is a specification of an activity that may be included in a Process_plan. A Process_operation_definition characterizes a manufacturing or control operation.

NOTE 1   Process_operation_definition as well as Process_operation_occurrence may be associated with organizational data, e.g., Organization_or_person_in_organization_assignment. The reason for having these data available for both types of objects is the requirement to associate Process_operation_definition with organizational data in both a context-independent and a context-dependent way (the context is a particular Process_plan).

NOTE 2   In the case where an instance of Process_operation_definition is associated with, e.g., two Organization objects (e.g., as location), once context-independent and once context-dependent, the two locations need not be the same but should be related in a way that the context-dependent location should be a specialization of the context-independent location (e.g., a particular assembly line in a plant).

EXPRESS specification:

*)
ENTITY Process_operation_definition;
  id : STRING;
  name : OPTIONAL label;
  process_type : STRING;
  description : OPTIONAL text;
  version_id : OPTIONAL STRING;
END_ENTITY;
(*

Attribute definitions:

id: specifies the identifier of the Process_operation_definition that shall be unique within the scope of the associated Process_plan.

name: specifies the word or group of words by which the Process_operation_definition is referred to.

EXAMPLE    'operation Z10.114' is an example of a name.

The value of this attribute need not be specified.

process_type: specifies the type of Process_operation_definition.

description: specifies additional information about the Process_operation_definition. The value of this attribute need not be specified.

version_id: specifies the identification of a particular version of a Process_operation_definition. The value of this attribute need not be specified.

4.3.2 Process_operation_definition_relationship   EXPRESS-GMapping table

A Process_operation_definition_relationship is a relationship between two Process_operation_definition objects.

EXPRESS specification:

*)
ENTITY Process_operation_definition_relationship;
  relation_type : STRING;
  description : text;
  relating : Process_operation_definition;
  related : Process_operation_definition;
END_ENTITY;
(*

Attribute definitions:

relation_type: specifies the meaning of the relationship. Where applicable the following values shall be used:

description: specifies additional information about the Process_operation_definition_relationship.

relating: specifies the first of the two objects related by the Process_operation_definition_relationship.

NOTE 1   The semantics of this attribute is defined by the attribute relation_type.

related: specifies the second of the two objects related by the Process_operation_definition_relationship.

NOTE 2   The semantics of this attribute is defined by the attribute relation_type.

4.3.3 Process_operation_input_or_output   EXPRESS-GMapping table

A Process_operation_input_or_output is an input or expected result of a Process_operation_definition.

EXPRESS specification:

*)
ENTITY Process_operation_input_or_output;
  role : STRING;
  description : OPTIONAL text;
  operation : Process_operation_occurrence;
  element : process_operation_input_or_output_select;
  placement : OPTIONAL Geometric_relationship_with_placement_transformation;
  concerned_shape : SET[0:?] OF Shape_element;
END_ENTITY;
(*

Attribute definitions:

role: specifies whether the identified element plays the role of an input or an output for the operation.

description: specifies additional information about the Process_operation_input_or_output. The value of this attribute need not be specified.

operation: specifies the Process_operation_occurrence that the Process_operation_input_or_output is associated with.

element: specifies the element that plays the role of the input or the output for the operation.

placement: specifies the geometrical transformation between the local coordinate system of the element acting as Process_operation_input_or_output, and the reference coordinate system. The reference coordinate system is either the coordinate system of the reference tool, if present, for the concerned Process_operation_occurrence or, if no reference tool is present, the coordinate system of the Process_operation_occurrence itself. This value of this attribute need not be specified.

concerned_shape: specifies the set of Shape_element objects that are affected by the Process_operation_occurrence. There shall exist zero or more Shape_elements for the Process_operation_input_or_output.

4.3.4 Process_operation_occurrence   EXPRESS-GMapping table

A Process_operation_occurrence is a usage of a Process_operation_definition in a Process_plan. This association states that the Process_operation_definition is part of the Process_plan.

NOTE    This mechanism enables the reuse of a Process_operation_definition in the context of more than one Process_plan.

EXPRESS specification:

*)
ENTITY Process_operation_occurrence;
  id : STRING;
  plan : Process_plan;
  operation_definition : Process_operation_definition;
  is_defined_in : OPTIONAL Geometric_coordinate_space;
END_ENTITY;
(*

Attribute definitions:

id: specifies the identifier of the Process_operation_occurrence.

plan: specifies the Process_plan to which the Process_operation_occurrence is assigning a Process_operation_definition.

operation_definition: specifies the Process_operation_definition that defines the Process_operation_occurrence in a Process_plan.

is_defined_in: specifies the Geometric_coordinate_space of the Process_operation_occurrence for the case where none of the tools associated by Process_operation_input_or_output plays the role of a reference tool defining the reference coordinate space. The value of this attribute need not be specified.

4.3.5 Process_operation_occurrence_relationship   EXPRESS-GMapping table

A Process_operation_occurrence_relationship is a relationship between two Process_operation_occurrence objects.

NOTE 1   The relating Process_operation_occurrence and the related Process_operation_occurrence need not belong to the same Process_plan version.

EXPRESS specification:

*)
ENTITY Process_operation_occurrence_relationship;
  relation_type : STRING;
  description : OPTIONAL text;
  relating : Process_operation_occurrence;
  related : Process_operation_occurrence;
  cycle_time : OPTIONAL Time_interval_with_bounds;
  waiting_time : OPTIONAL Duration;
END_ENTITY;
(*

Attribute definitions:

relation_type: specifies the meaning of the relationship. Where applicable the following values shall be used:

description: additional information about the Process_operation_occurrence_relationship. The value of this attribute need not be specified.

relating: specifies the first of the two Process_operation_occurrence objects related by a Process_operation_occurrence_relationship.

NOTE 4   The semantics of this attribute are defined by the attribute relation_type.

related: specifies the second of the two Process_operation_occurrence objects related by a Process_operation_occurrence_relationship.

NOTE 5   The semantics of this attribute are defined by the attribute relation_type.

cycle_time: specifies the interval of time within which both Process_operation_occurrence objects have to take place in order to be declared as simultaneous. The value of this attribute need not be specified.

waiting_time: specifies the time which shall elapse, at least, between the completion of the relating Process_operation_occurrence and the start of the related Process_operation_occurrence. The referenced shall have a definition that is a Duration. The value of this attribute need not be specified.

4.3.6 Process_operation_resource_assignment   EXPRESS-GMapping table

A Process_operation_resource_assignment is a mechanism to associate a resource with a Process_operation_occurrence.

EXPRESS specification:

*)
ENTITY Process_operation_resource_assignment;
  reference_tool : BOOLEAN;
  operation : Process_operation_occurrence;
  reason : OPTIONAL STRING;
  resource_definition : resource_definition_select;
  placement : OPTIONAL Geometric_relationship_with_placement_transformation;
END_ENTITY;
(*

Attribute definitions:

reference_tool: specifies whether or not the resource identified by the Process_operation_resource_assignment plays the role of the reference tool for the occurrence of an operation.

In the case where the value of this attribute is 'true', all geometric transformations within the scope of the Process_operation_occurrence are defined with respect to the local coordinate system of the resource identified by the Process_operation_resource_assignment. There must not be more than one resource playing the role of the reference tool for one Process_operation_occurrence.

In the case where the resource is not represented as a Part_view_definition the value of the reference_tool shall be 'false'.

operation: specifies the Process_operation_occurrence with which the resource is associated.

reason: specifies the rationale behind the use of the resource for a particular Process_operation_occurrence. The value of this attribute need not be specified.

resource_definition: specifies the tool that is used to perform the operation.

placement: specifies the geometrical transformation between the local coordinate system of the Process_operation_resource_assignment and the reference coordinate system. This value of this attribute need not be specified.

NOTE    The reference coordinate system is either the coordinate system of the reference tool (if present) for the concerned Process_operation_definition or (if no reference tool is present) the coordinate system of the Process_operation_definition itself. In the case where the value of the attribute reference_tool is 'true', no transformation shall be defined.

4.3.7 Process_plan   EXPRESS-GMapping table

A Process_plan is a manufacturing planning information, necessary to realize or produce a particular version of a Part.

EXPRESS specification:

*)
ENTITY Process_plan;
  plan_id : identifier;
  name : OPTIONAL label;
  description : OPTIONAL text;
  version_id : OPTIONAL identifier;
  produced_output : OPTIONAL SET[1:?] OF Part_version;
END_ENTITY;
(*

Attribute definitions:

plan_id: specifies the identifier of the Process_plan that shall be unique within the scope of an organization.

name: specifies the word or group of words by which the Process_plan is referred to. The value of this attribute need not be specified.

description: specifies additional information about the Process_plan. The value of this attribute need not be specified.

version_id: specifies the identification of a particular version of a Process_plan.

produced_output: specifies the set of Part_version objects that are produced by the operations of the Process_plan. The value of this attribute need not be specified.

4.3.8 Process_plan_relationship   EXPRESS-GMapping table

A Process_plan_relationship is a relationship between two Process_plan objects.

EXAMPLE    If an item shall be manufactured at two different manufacturing sites, e.g., one at Paris and the other at Bordeaux, there will be two different process plans, that may be related by a Process_plan_relationship.

EXPRESS specification:

*)
ENTITY Process_plan_relationship;
  relation_type : STRING;
  description : OPTIONAL text;
  relating : Process_plan;
  related : Process_plan;
END_ENTITY;
(*

Attribute definitions:

relation_type: specifies the meaning of the relationship. Where applicable the following values shall be used:

description: specifies additional information about the Process_plan_relationship. The value of this attribute need not be specified.

relating: specifies the first of the two Process_plan objects related by a Process_plan_relationship.

NOTE 1   The semantics of this attribute are defined by the attribute relation_type.

related: specifies the second of the two Process_plan objects related by a Process_plan_relationship.

NOTE 2   The semantics of this attribute are defined by the attribute relation_type.

4.3.9 Process_state_relationship   EXPRESS-GMapping table

A Process_state_relationship is a type of Part_definition_relationship. A Process_state_relationship is a relationship between two Part_view_definition objects where the relating Part_view_definition is an in-process-part definition of a particular version of a part. It characterizes a state of the Part_version that occurs before the state identified by the related Part_view_definition.

NOTE    A Process_state_relationship may be used to characterize intermediate states of the Part_version, if this Part_version is one of the produced outputs of a Process_plan.

EXPRESS specification:

*)
ENTITY Process_state_relationship
  SUBTYPE OF (Part_definition_relationship);
  direction : OPTIONAL process_state_relationship_direction;
END_ENTITY;
(*

Attribute definitions:

direction: specifies on whether the relationship is unidirectional from the related to the relating Part_view_definition or bidirectional. If not specified, the direction is not known.

4.3.10 Product_resource   EXPRESS-GMapping table

A Product_resource is a type of Product that also specifies a resource for a Process_plan.

EXPRESS specification:

*)
ENTITY Product_resource
  SUBTYPE OF (Resource_item, Product);
END_ENTITY;
(*

4.3.11 Product_version_resource   EXPRESS-GMapping table

A Product_version_resource is a type of Product_version that also specifies a resource for a Process_plan.

EXPRESS specification:

*)
ENTITY Product_version_resource
  SUBTYPE OF (Resource_item, Product_version);
END_ENTITY;
(*

4.3.12 Product_view_resource   EXPRESS-GMapping table

A Product_view_resource is a type of Product_view_definition that also specifies a resource for a Process_plan.

EXPRESS specification:

*)
ENTITY Product_view_resource
  SUBTYPE OF (Resource_item, Product_view_definition);
END_ENTITY;
(*

4.3.13 Resource_requirement_type   EXPRESS-GMapping table

A Resource_requirement_type is a definition of a kind of a requirement for a resource.

EXPRESS specification:

*)
ENTITY Resource_requirement_type;
  name : label;
  description : text;
END_ENTITY;
(*

Attribute definitions:

name: specifies the word or group of words by which the Resource_requirement_type is referred to.

description: specifies additional information about the Resource_requirement_type.

4.3.14 Same_time_machining_relationship   EXPRESS-GMapping table

A Same_time_machining_relationship is a type of Part_occurrence_relationship A Same_time_machining_relationship is a relationship between two Product_occurrence objects that specifies that those two objects shall be manufactured together within the same Process_operation_occurrence.

EXPRESS specification:

*)
ENTITY Same_time_machining_relationship
  SUBTYPE OF (Part_occurrence_relationship);
END_ENTITY;
(*



*)
END_SCHEMA;  -- Process_plan_arm
(*


© ISO 2019 — All rights reserved