representing_task

Template:— representing_task_invocation (rep_task_invoc)
Capability:representing_task

Date: 2011/05/20 08:59:06
Revision: 1.6

Cover Contents Description Model diags.Input params.Ref. params.Instantiation path Instance diags.Characterizations Issues in situ

This section specifies the template representing_task_invocation.

NOTE The template has been defined in the context of the capability representing_task which provides an overall description of the relevant parts of the ISO 10303-239 information model and a description of related templates.

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 invocation of another task_method (_version) as a task_step in the invoking task_method.

Model diagrams

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

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

The graphic for the template to be used in other EXPRESS-G diagrams is shown in Figure 2 below.

Figure 2 — The graphical representation of the representing_task_invocation template

Input parameters

The following input parameters are defined for this template:

task_step_id (Type='STRING')

The task step identifier..

task_step_id_class_name (Default=Task_step_identification_code,Type='CLASS')

The name of the class being used to classify the task step identifier (@task_step_id)

The following classes and their sub-classes can be used:

classifications: "Task_step_identification_code" (urn:plcs:rdl:std:Task_step_identification_code), "Task_step_name" (urn:plcs:rdl:std:Task_step_name)

task_step_id_ecl_id (Default=urn:plcs:rdl:std,Type='URN')

The identifier of the External_class_library storing the definition of the class referenced by the parameter @task_step_id_class_name.

task_step_org_id (Type='STRING')

The name or identifier of the Organization that owns the @task_step_id.

task_step_org_id_class_name (Default=Organization_name,Type='CLASS')

The name of the class being used to classify the identification of the Organization responsible for creating the @task_step_id.

The following classes and their sub-classes can be used:

classifications: "Organization_identification_code" (urn:plcs:rdl:std:Organization_identification_code), "Organization_name" (urn:plcs:rdl:std:Organization_name)

task_step_org_id_ecl_id (Default=urn:plcs:rdl:std,Type='URN')

The identifier of the External_class_library storing the definition of the class referenced by the parameter @task_step_org_id_class_name.

task_step_category (Type='CLASS')

Categorization of the invoked task in relation to the task from which it's being invoked.

The following classes and their sub-classes can be used:

classifications: "Task_invocation" (urn:plcs:rdl:std:Task_invocation)

task_step_category_ecl_id (Default=urn:plcs:rdl:std,Type='URN')

The identifier of the External_class_library storing the definition of the class referenced by the parameter @task_step_category.

invoked_task_method (Type= 'SELECT (method_or_method_version)' )

The Task_method or Task_method_version that is invoked as a series of steps by the Task_invocation entity instance.

Reference parameters

The following reference parameters are defined for this template:

task_inv(Type='ENTITY (Task_invocation)')

Allow the Task_invocation entity instantiated in this path to be referenced when this template is used.

Note: The Task_invocation entity can be referenced in a template path by:

%^target = $representing_task_invocation.task_inv%

where target is the parameter to which the Task_invocation is bound.

Uniqueness constraints

The following parameter combinations specify a uniqueness constraint:

Unique constraint: Task invocation

Each instance of the entity (Task_invocation) within the data set shall be uniquely identified by a combination of the following parameters on this template (representing_task_invocation) namely: task_step_id, task_step_id_class_name, task_step_id_ecl_id, task_step_org_id, task_step_org_id_class_name, task_step_org_id_ecl_id, task_step_category, task_step_category_ecl_id, invoked_task_method.
The instance is referenced by the following template parameter: task_inv.

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 Templates Help/Information section.

Task_invocation
%^task_inv = Task_invocation%
Task_invocation.name = '/IGNORE'
Task_invocation.description = '/IGNORE'
Task_invocation.consequence = '/IGNORE'
Task_invocation.purpose = '/IGNORE'
Task_invocation.task_method -> @invoked_task_method

-- Identify the Task_invocation
/assigning_identification(
    items= ^task_inv,
    id= @task_step_id,
    id_class_name= @task_step_id_class_name,
    id_ecl_id= @task_step_id_ecl_id,
    org_id= @task_step_org_id,
    org_id_class_name= @task_step_org_id_class_name,
    org_id_ecl_id= @task_step_org_id_ecl_id )/
/assigning_reference_data(
    items=^task_inv,
    class_name=@task_step_category,
    ecl_id=@task_step_category_ecl_id)/

The following entities are instantiated with attributes as specified:

Entity in path	Value	Inherited from
Task_invocation.name	'/IGNORE'	Activity_method.name
Task_invocation.description	'/IGNORE'	Activity_method.description
Task_invocation.consequence	'/IGNORE'	Activity_method.consequence
Task_invocation.purpose	'/IGNORE'	Activity_method.purpose

Instance diagrams

The instance diagram in Figure 3 shows an example of the EXPRESS entities and templates that are instantiated by the template:

/representing_task_invocation(task_step_id='25', task_step_id_class_name='Task_step_identification_code', task_step_id_ecl_id='urn:plcs:rdl:std', task_step_org_id='The Bike Company Ltd', task_step_org_id_class_name='Organization_name', task_step_org_id_ecl_id='urn:plcs:rdl:std', task_step_category='Required_condition', task_step_category_ecl_id='urn:plcs:rdl:sample', invoked_task_method='#6')/

(an illustration of the consolidated representing_task_invocation template is shown in Figure 4 below.)

Figure 3 — Entities instantiated by representing_task_invocation template

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


          #1 = TASK_ELEMENT_SEQUENCE('/IGNORE','/IGNORE','/IGNORE','/IGNORE',$,(#2,#3));
          #2 = TASK_STEP('/IGNORE','/IGNORE','/IGNORE','/IGNORE',$);
          #3 = TASK_INVOCATION('/IGNORE','/IGNORE','/IGNORE','/IGNORE',$,#6);
          #4 = TASK_METHOD_VERSION('/IGNORE','/IGNORE','/IGNORE','/IGNORE',#1,#5);
          #5 = TASK_METHOD('/IGNORE','/IGNORE','/IGNORE','/IGNORE',());
          #6 = TASK_METHOD('/IGNORE','/IGNORE','/IGNORE','/IGNORE',());
          #8 = IDENTIFICATION_ASSIGNMENT('25','/IGNORE','/IGNORE',(#3));
          #10 = CLASSIFICATION_ASSIGNMENT(#11,(#8),'/IGNORE');
          #11 = EXTERNAL_CLASS('/NULL','Task_step_identification_code','/IGNORE',#12);
          #12 = EXTERNAL_CLASS_LIBRARY('urn:plcs:rdl:std','/IGNORE');
          #15 = ORGANIZATION('/IGNORE','/IGNORE');
          #17 = IDENTIFICATION_ASSIGNMENT('The Bike Company Ltd','/IGNORE','/IGNORE',(#15));
          #19 = CLASSIFICATION_ASSIGNMENT(#20,(#17),'/IGNORE');
          #20 = EXTERNAL_CLASS('/NULL','Organization_name','/IGNORE',#12);
          #22 = ORGANIZATION_OR_PERSON_IN_ORGANIZATION_ASSIGNMENT(#15,'/IGNORE',(#8));
          #24 = CLASSIFICATION_ASSIGNMENT(#25,(#22),'/IGNORE');
          #25 = EXTERNAL_CLASS('/NULL','Owner_of','/IGNORE',#12);
          #28 = CLASSIFICATION_ASSIGNMENT(#29,(#3),'/IGNORE');
          #29 = EXTERNAL_CLASS('/NULL','Required_condition','/IGNORE',#30);
          #30 = EXTERNAL_CLASS_LIBRARY('urn:plcs:rdl:sample','/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 representing_task_invocation template

Characterizations

No common characterizations of the template representing_task_invocation have been identified. However, the ISO 10303-239 EXPRESS model may enable other assignments to the entities instantiated by the template.