Application module: Task specification ISO/TS 10303-1262:2010-03(E)
© ISO

Cover page
Table of contents
Copyright
Foreword
Introduction
1 Scope
2 Normative references
3 Terms, definitions and abbreviations

4 Information requirements
   4.1 Required AM ARMs
   4.2 ARM type definitions
   4.3 ARM entity definitions
   4.4 ARM subtype constraint 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 definitions
     5.2.3 MIM subtype constraint 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
Bibliography
Index

4 Information requirements

This clause specifies the information requirements for the Task specification 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.

The following EXPRESS specification begins the Task_specification_arm schema and identifies the necessary external references.

EXPRESS specification:

*)
SCHEMA Task_specification_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 State_observed_arm;    --  ISO/TS 10303-1256

USE FROM Task_element_arm;    --  ISO/TS 10303-1480
(*

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

State_observed_arm ISO/TS 10303-1256
Task_element_arm ISO/TS 10303-1480

NOTE 2   See Annex C, Figures C.1, C.2, C.3and C.4 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 constraint_context   EXPRESS-G

The constraint_context type is an extensible list of alternate data types that allows for the designation of the data types Task_element and Task_method_version.

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

A constraint_context specifies the allowed contexts in which a Element_constraint may apply.

EXPRESS specification:

*)
TYPE constraint_context = EXTENSIBLE GENERIC_ENTITY SELECT
   (Task_element,
    Task_method_version);
END_TYPE;
(*

4.2.2 method_or_method_version   EXPRESS-G

The method_or_method_version type allows for the designation of the data types Task_method and Task_method_version.

EXPRESS specification:

*)
TYPE method_or_method_version = SELECT
   (Task_method,
    Task_method_version);
END_TYPE;
(*

4.2.3 state_or_state_definition_select   EXPRESS-G

The state_or_state_definition_select type allows for the designation of the data types Applied_state_assignment, Applied_state_definition_assignment, State and State_definition.

EXPRESS specification:

*)
TYPE state_or_state_definition_select = SELECT
   (Applied_state_assignment,
    Applied_state_definition_assignment,
    State,
    State_definition);
END_TYPE;
(*

4.2.4 task_classification_item   EXPRESS-G

The task_classification_item type is an extension of the classification_item type. It adds the data types Activity_method, Activity_method_relationship, Applied_activity_method_assignment, Task_element_state_relationship, Task_method, Task_method_state_relationship, Task_objective and Task_objective_state_relationship 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 task_classification_item = EXTENSIBLE GENERIC_ENTITY SELECT BASED_ON classification_item WITH
   (Activity_method,
    Activity_method_relationship,
    Applied_activity_method_assignment,
    Task_element_state_relationship,
    Task_method,
    Task_method_state_relationship,
    Task_objective,
    Task_objective_state_relationship);
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 Advisory_note   EXPRESS-GMapping table

An Advisory_note is the link between a task element with an advisory task step.

EXPRESS specification:

*)
ENTITY Advisory_note;
  advisory : Advisory_task_step;
  applies_to : Task_element;
END_ENTITY;
(*

Attribute definitions:

advisory: the Advisory_task_step used to provide the details of the note.

applies_to: the Task_element within which the note applies.

4.3.2 Advisory_task_step   EXPRESS-GMapping table

An Advisory_task_step is a type of Task_step. It conveys information.

NOTE    Some Task_methods may not require any action to be undertaken.

EXAMPLE    "Beware of hot exhausts", "do not use tool X this way" and similar messages.

EXPRESS specification:

*)
ENTITY Advisory_task_step
  SUBTYPE OF (Task_step);
END_ENTITY;
(*

4.3.3 Element_constraint   EXPRESS-GMapping table

An Element_constraint is a type of Task_element_relationship that signifies a constraint between Task_elements. The constraint may only apply within the context of a Task_method or Task_element, specified as the context.

EXPRESS specification:

*)
ENTITY Element_constraint
  SUBTYPE OF (Task_element_relationship);
  applies_in : OPTIONAL constraint_context;
END_ENTITY;
(*

Attribute definitions:

applies_in: the Task_element within which the constraint applies. The value of this attribute need not be specified.

EXAMPLE    Within a specific method, use of test equipment must be preceded by callibration. Or a 30 minute wait is required between stages of a method.

4.3.4 Simultaneous_elements   EXPRESS-GMapping table

A Simultaneous_elements is a type of Concurrent_elements that represents two or more actions to be performed together.

EXPRESS specification:

*)
ENTITY Simultaneous_elements
  SUBTYPE OF (Concurrent_elements);
END_ENTITY;
(*

4.3.5 Task_element_levels   EXPRESS-GMapping table

A Task_element_levels is a type of Task_element that provides two or more different descriptions in place of a single method. The actual work will be the same whichever alternative Task_element is followed.

NOTE    This can be used to provide defferent levels of description of a task for people with varying levels of experience or expertise.

EXPRESS specification:

*)
ENTITY Task_element_levels
  SUBTYPE OF (Task_element);
  alternatives : SET[2:?] OF Task_element;
END_ENTITY;
(*

Attribute definitions:

alternatives: the Task_elements describing two or more ways in which the same work may be undertaken.

4.3.6 Task_element_state_relationship   EXPRESS-GMapping table

A Task_element_state_relationship is an type of Activity_method_relationship. It is an association between a State or a State_definition and a Task_element. The meaning of the entity is determined by classification. Candidate meanings include:

EXPRESS specification:

*)
ENTITY Task_element_state_relationship;
  state : state_or_state_definition_select;
  task_element : Task_element;
END_ENTITY;
(*

Attribute definitions:

state: the State or State_definition being related.

task_element: the Task_element being related.

4.3.7 Task_invocation   EXPRESS-GMapping table

A Task_invocation is a type of Task_element. It is an instruction to perform another task.

EXAMPLE    A Task_element calls a pre-defined task to perform an instrument calibration.

EXPRESS specification:

*)
ENTITY Task_invocation
  SUBTYPE OF (Task_element);
  task_method : method_or_method_version;
END_ENTITY;
(*

Attribute definitions:

task_method: the Task_method to be invoked.

4.3.8 Task_method   EXPRESS-GMapping table

A Task_method is a type of Activity_method. It is a specification of work.

NOTE    The task method may be implemented using people, machines or a combination.

EXPRESS specification:

*)
ENTITY Task_method
  SUBTYPE OF (Activity_method);
  objective : SET[0:?] OF Task_objective;
END_ENTITY;
(*

Attribute definitions:

objective: the intended result or results of the task.

4.3.9 Task_method_assignment   EXPRESS-GMapping table

A Task_method_assignment is a type of Applied_activity_method_assignment. It is an association of a Task_method with product or activity data.

EXPRESS specification:

*)
ENTITY Task_method_assignment
  SUBTYPE OF (Applied_activity_method_assignment);
  SELF\Applied_activity_method_assignment.assigned_activity_method : Task_method;
  SELF\Applied_activity_method_assignment.items : SET[1:?] OF task_item;
END_ENTITY;
(*

Attribute definitions:

assigned_activity_method: the Task_method being assigned.

items: the set of things that are associated to the Task_method.

4.3.10 Task_method_relationship   EXPRESS-GMapping table

A Task_method_relationship is a type of Activity_method_relationship. It relates two task methods.

NOTE    The nature of the relationship is determined from its classification.

EXPRESS specification:

*)
ENTITY Task_method_relationship
  SUBTYPE OF (Activity_method_relationship);
  SELF\Activity_method_relationship.relating_method : Task_method;
  SELF\Activity_method_relationship.related_method : Task_method;
END_ENTITY;
(*

Attribute definitions:

relating_method: one of the instances of Task_methods that is a part of the relationship.

related_method: the other instance of Task_method that is a part of the relationship. If one element of the relationship is dependent upon the other, this attribute shall be the dependent one.

4.3.11 Task_method_state_relationship   EXPRESS-GMapping table

A Task_method_state_relationship is a relationship between a state and a Task_method.

NOTE    The meaning of the entity is determined by classification. Candidate meanings include:

EXPRESS specification:

*)
ENTITY Task_method_state_relationship;
  state : state_or_state_definition_select;
  task_method : Task_method_version;
END_ENTITY;
(*

Attribute definitions:

state: the mode of being that is related.

task_method: the Task_method being related.

4.3.12 Task_method_version   EXPRESS-GMapping table

A Task_method_version is a type of Activity_method which allows the explicit reference to versions of a Task_methodand to track changes against a Task_method.

EXPRESS specification:

*)
ENTITY Task_method_version
  SUBTYPE OF (Activity_method);
  content : OPTIONAL Task_element;
  of_task_method : Task_method;
END_ENTITY;
(*

Attribute definitions:

content: the way in which the task is to be carried out. The value of this attribute need not be specified.

of_task_method: the Task_method which this is a version of.

4.3.13 Task_method_version_assignment   EXPRESS-GMapping table

A Task_method_version_assignment is a type of Applied_activity_method_assignment. It is an association of a Task_method_version with product or activity data.

EXPRESS specification:

*)
ENTITY Task_method_version_assignment
  SUBTYPE OF (Applied_activity_method_assignment);
  SELF\Applied_activity_method_assignment.assigned_activity_method RENAMED assigned_task_method : Task_method_version;
  SELF\Applied_activity_method_assignment.items : SET[1:?] OF task_item;
END_ENTITY;
(*

Attribute definitions:

assigned_task_method: the Task_method_version being assigned.

items: the set of things that the Task_method_version is assigned to.

4.3.14 Task_method_version_relationship   EXPRESS-GMapping table

A Task_method_version_relationship is a type of Activity_method_relationship. It relates two instances of Task_method_version.

EXPRESS specification:

*)
ENTITY Task_method_version_relationship
  SUBTYPE OF (Activity_method_relationship);
  SELF\Activity_method_relationship.relating_method RENAMED relating_task_method : Task_method_version;
  SELF\Activity_method_relationship.related_method RENAMED related_task_method : Task_method_version;
END_ENTITY;
(*

Attribute definitions:

relating_task_method: one instance of Task_method_version that is a part of the relationship

related_task_method: the other instance of Task_method_version that is a part of the relationship. If one element of the relationship is dependent upon the other, this attribute shall be the dependent one.

4.3.15 Task_objective   EXPRESS-GMapping table

A Task_objective is a result or objective that is reached by undertaking a Task_method.

NOTE    More than one Task_method may be defined for a given objective, if there can be several ways to accomplish the objective.

EXPRESS specification:

*)
ENTITY Task_objective;
  name : STRING;
  description : STRING;
END_ENTITY;
(*

Attribute definitions:

name: the word or group of words by which the Task_objective is known.

description: the text that provides further information about the Task_objective.

4.3.16 Task_objective_state_relationship   EXPRESS-GMapping table

A Task_objective_state_relationship is a relationship between a state and a Task_objective.

NOTE    The meaning of the entity is determined by classification. Candidate meanings include:

EXPRESS specification:

*)
ENTITY Task_objective_state_relationship;
  state : state_or_state_definition_select;
  task_objective : Task_objective;
END_ENTITY;
(*

Attribute definitions:

state: the mode of being that is related.

task_objective: the Task_objective being related.

4.4 ARM subtype constraint definitions

This subclause specifies the ARM subtype constraints for this module. Each subtype constraint places constraints on the possible super-type / subtype instantiations. The ARM subtype constraints and definitions are specified below.

4.4.1 restrict_activity_method_relationship   EXPRESS-GMapping table

The restrict_activity_method_relationship constraint specifies that instances of subtypes of Activity_method_relationship shall not be simultaneously of type Task_element_relationship, Task_method_relationship and Task_method_version_relationship.

EXPRESS specification:

*)
SUBTYPE_CONSTRAINT restrict_activity_method_relationship FOR Activity_method_relationship;
  ONEOF (Task_element_relationship,
         Task_method_relationship,
         Task_method_version_relationship);
END_SUBTYPE_CONSTRAINT;
(*

4.4.2 restrict_activity_method_subtypes   EXPRESS-GMapping table

The restrict_activity_method_subtypes constraint specifies that instances of subtypes of Activity_method shall not be simultaneously of type Task_element, Task_method and Task_method_version.

EXPRESS specification:

*)
SUBTYPE_CONSTRAINT restrict_activity_method_subtypes FOR Activity_method;
  ONEOF (Task_element,
         Task_method,
         Task_method_version);
END_SUBTYPE_CONSTRAINT;
(*

4.4.3 restrict_task_element_subtypes   EXPRESS-GMapping table

The restrict_task_element_subtypes constraint specifies that instances of subtypes of Task_element shall not be simultaneously of type End_task, Exit_loop, Structured_task_element, Task_element_levels, Task_invocation and Task_step.

EXPRESS specification:

*)
SUBTYPE_CONSTRAINT restrict_task_element_subtypes FOR Task_element;
  ONEOF (End_task,
         Exit_loop,
         Structured_task_element,
         Task_element_levels,
         Task_invocation,
         Task_step);
END_SUBTYPE_CONSTRAINT;
(*



*)
END_SCHEMA;  -- Task_specification_arm
(*

© ISO 2009 — All rights reserved