Template:— assigning_task_method_version (ass_task_mv) Date: 2008/03/05 15:29:12
Revision: 1.4
CoverContentsDescriptionModel diags.Input params.Ref. params.Instantiation pathInstance diags.CharacterizationsIssues

This section specifies the template assigning_task_method_version.

NOTE  An explanation of a template and the associated instantiation path is provided in the Template overview section.

Description

This template describes how to represent an assignment relationship between a Task_method_version and the assignment target. In effect, this template does nothing more that define the rule that a Task_method_version_assignment must be classified with reference data that defines the assignment role. For a detailed discussion of the principle uses of assignment and the roles applicable, see the capability C090: representing_task_associations (NB Capabilities are not documented in this release of the PLCS standard)

Model diagrams
The EXPRESS-G diagram in Figure 1 shows the templates and EXPRESS entities that are required to represent the template "assigning_task_method_version". The text highlighted in blue shows the template parameters.

The diagram shows the use of a Task_method_version_assignment to link a Task_method_version to the target in the role given by the reference data. How to use this template in practice is described in the capability C090: representing_task_associations (NB Capabilities are not documented in this release of the PLCS standard) .

NOTE    At the time of writing, the syntax for templates does not correctly deal with multiple targets, which are used when asserting that a given set of characterizations must be treated as applying as a whole to a list of targets, and that the characterization cannot logically have different values in the assignments.



Figure 1 —  An EXPRESS-G representation of the Information model for assigning_task_method_version

Figure 1 —  An EXPRESS-G representation of the Information model for assigning_task_method_version

The graphic for the template to be used in other EXPRESS-G diagrams is shown in Figure  2 below.
The diagram shows the template in full and abbreviated form.


Figure 2 —  The graphical representation of the assigning_task_method_version template

Figure 2 —  The graphical representation of the assigning_task_method_version template

Input parameters
The following input parameters are defined for this template:
assignment_role (Type='CLASS')
The role of the assignment.
The following classes and their sub-classes can be used:
classifications: "Task_method_version_assignment" (urn:plcs:rdl:std:Task_method_version_assignment)
role_ecl_id (Default=urn:plcs:rdl:std,Type='URN')
The External_class_library storing the definition of the class referenced by the parameter @assignment_role
item (Type= 'SELECT (task_item)' )
The target element of the assignment.
task_method_version (Type= 'ENTITY (Task_method_version)' )
The Task_method_version that is being assigned.
Reference parameters
The following reference parameters are defined for this template:
task_mv_asg(Type='ENTITY (Task_method_version_assignment)')
Allow the Task_method_version_assignment entity instantiated in this path to be referenced when this template is used.
Note: The Task_method_version_assignment entity can be referenced in a template path by:
%^target = $assigning_task_method_version.task_mv_asg%
where target is the parameter to which the Task_method_version_assignment is bound.
Instantiation path
The instantiation path shown below specifies the entities that are to be instantiated by the template.
A description of templates and the syntax for the instantiation path is provided in the Reading Capability Templates help section.
Task_method_version_assignment
%^task_mv_ass = Task_method_version_assignment%
Task_method_version_assignment.role = '/IGNORE'
Task_method_version_assignment.assigned_task_method -> @task_method_version
/assigning_reference_data(
    items=^task_mv_ass,
    class_name=@assignment_role,
    ecl_id= @role_ecl_id)/
The following entities are instantiated with attributes as specified:
Entity in path Value Inherited from
Task_method_version_assignment.role '/IGNORE' Applied_activity_method_assignment.role
Instance diagrams
The instance diagram in Figure  3 shows an example of the EXPRESS entities and templates that are instantiated by the template: (an illustration of the consolidated template is shown in Figure 4 below.)


Figure 3 —  Entities instantiated by assigning_task_method_version template

Figure 3 —  Entities instantiated by assigning_task_method_version template

The instance model in STEP ASCII exchange file format (ISO 10303 Part 21 syntax) is: 

#21 = CLASSIFICATION_ASSIGNMENT(#22,(#24),'/IGNORE');
#22 = EXTERNAL_CLASS('/NULL','Task_affected_item','/IGNORE',#23);
#23 = EXTERNAL_CLASS_LIBRARY('urn:plcs:rdl:sample',$);
#24 = TASK_METHOD_VERSION_ASSIGNMENT(#25,(#26),'/IGNORE');
#25 = TASK_METHOD_VERSION('/IGNORE','/IGNORE','/IGNORE','/IGNORE',$,$);
#26 = PART_VERSION('/IGNORE','/IGNORE',$);
The instance diagram in Figure 4 shows the graphic symbol for the template that is to be used in other instance diagrams. The example template is:


Figure 4 —  Instantiation of assigning_task_method_version template

Figure 4 —  Instantiation of assigning_task_method_version template

Characterizations
The following section details how the assigning_task_method_version template can be optionally characterized by assigning other constructs to it. These are characterizations commonly applied to the template. The ISO 10303-239 EXPRESS model may enable other assignments to the entities instantiated by the template.
The following characterizations may apply:
Characterization - see capability

NOTE   this characterization is optional.

For characterizations, see the capability C090: representing_task_associations (NB Capabilities are not documented in this release of the PLCS standard)

© OASIS — All rights reserved