Template:— representing_task (reptask)
Capability:representing_task |
Date: 2007/09/28 12:44:09
Revision: 1.5
|
![[warning:]](../../../../images/dex/warning.gif)
Error T1: There is no template_proxy in the capability representing_task for the template representing_task
This section specifies the template representing_task.
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.
This template describes how to represent a task specification.
A task specification is a procedural description of how to do something. A task specification does not plan, schedule, or
record what is done. This template is used to define the essential meta information for the specification, that is:
- The task identifier, its version and variant;
- The task name and description;
- The item that the task is specified against;
- The end item that the task is specified for;
For example, task number 123 version 2 "Change Chain" may be specified for a 'Gears-r-us' type 3 Sturmley-Archer gear fitted
to a 'Muddy-Badger' model 42 bicycle.
The details of the specification our outside the scope of this template, as is the effectivity of the specification. These
are further considered in the REPRESENTING_TASK capability. For discussion of the meaning of version and variant and the paramaters
involved, see the REFERENCING_TASK template.
This template is designed for generic tasks specified against a specific type of end product, that is one which can be identified
by a part number, as opposed to against a general product configuration, or a task written against a specific individual,
for example, as a repair for specific damage.
The EXPRESS-G diagram in
Figure
1
shows the templates and EXPRESS entities that are required
to represent the template
"representing_task".
The text highlighted in blue shows the template parameters.
Error model_diag_1: Either delete A DESCRIPTION OF THE DIAGRAM or provide a description
A DESCRIPTION OF THE DIAGRAM
Figure 1 — An EXPRESS-G representation of the Information model for representing_task
The graphic for the template to be used in other EXPRESS-G diagrams
is shown in Figure
2
below.
Error model_diag_1: Either delete A DESCRIPTION OF THE DIAGRAM or provide a description
A DESCRIPTION OF THE DIAGRAM
Figure 2 — The graphical representation of the representing_task template
The following input parameters are defined for this template:
The task identifier, e.g. the task number.
The class of the task method identifier.
The following classes and their sub-classes can be used:
classifications: [task_method_identification_code]Error RDL1: The class task_method_identification_code does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
The identifier of the
External_class_library
storing the definition of the class referenced by the parameter @task_id_class_name.
The name or identifier of the organization that owns the task id.
The name of the class being used to classify the identification (
Identification_assignment)
of the organization responsible for creating the task specification
The following classes and their sub-classes can be used:
The identifier of the
External_class_library storing the
definition of the class used to classify the organization identifier.
The task version identifier, for example, the sequence number of the version.
The class of the task method version identifier.
The following classes and their sub-classes can be used:
classifications: [progression_code]Error RDL1: The class progression_code does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
The identifier of the
External_class_library
storing the definition of the class referenced by the parameter @task_ver_id_class_name.
The name or identifier of the organization that owns the task version identifer.
The name of the class being used to classify the identification (
Identification_assignment)
of the organization responsible for creating the task specification version.
The following classes and their sub-classes can be used:
The identifier of the
External_class_library storing the
definition of the class used to classify the organization identifier.
The task variant identifier. Multiple variants of a task version may be defined, customised to particular conditions.
The class of the task method variant identifier.
The following classes and their sub-classes can be used:
classifications: [task_method_varient_identification_code]Error RDL1: The class task_method_varient_identification_code does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
The identifier of the
External_class_library
storing the definition of the class referenced by the parameter @task_vart_id_class_name.
The name or identifier of the organization that owns the task variant identifier. This may not be the same as owner of the
task identifier, for example, when an organization customises a task to use to its own specific resouces.
The name of the class being used to classify the variant identification (
Identification_assignment)
of the organization responsible for creating the task specification variant
The following classes and their sub-classes can be used:
The identifier of the
External_class_library storing the
definition of the class used to classify the organization identifier.
The common or informal name by which the task specification is known, such as "change chain".
The common or informal description or abstract, intended to confirm to the user that this specification is the one they are
looking for.
task_description (Type='STRING', Optional)
![[warning:]]()
Error T9: Input parameter task_description is not unique in template representing_task
The common or informal description or abstract, intended to confirm to the user that this specification is the one they are
looking for.
The part identifier for the end item to which the task is applicable, e.g. Muddy-Badger Model 42 (M042).
The following classes and their sub-classes can be used:
The name or identifier of the organization that owns the part id.
The name of the class being used to classify the identification (
Identification_assignment)
of the organization responsible for creating the part representation
The following classes and their sub-classes can be used:
The identifier of the
External_class_library storing the
definition of the class used to classify the organization identifier.
The version identifier of the end part version
The following classes and their sub-classes can be used:
The name or identifier of the organization owns the end part version id.
The name of the class being used to classify the identification (
Identification_assignment)
of the organization responsible for providing the end part version
The following classes and their sub-classes can be used:
The identifier of the target part
The following classes and their sub-classes can be used:
The name or identifier of the organization that owns the part id.
The name of the class being used to classify the identification (
Identification_assignment)
of the organization responsible for creating the part representation
The following classes and their sub-classes can be used:
The identifier of the
External_class_library storing the
definition of the class used to classify the organization identifier.
The version identifier of the part version
The following classes and their sub-classes can be used:
The name or identifier of the organization owns the part version id.
The name of the class being used to classify the identification (
Identification_assignment)
of the organization responsible for providing the part version representation
The following classes and their sub-classes can be used:
part_vn_org_id_ecl_id (Default=urn:plcs:rdl:std,Type='URN', Optional)
![[warning:]]()
Error T9: Input parameter part_vn_org_id_ecl_id is not unique in template representing_task
The identifier of the
External_class_library storing the
definition of the class used to classify the organization identifier.
The following reference parameters are defined for this template:
task_method_version(Type='ENTITY (
![[warning:]]()
Error ER1: The entity Task_method_ version does not existTask_method_ version)')
Allow the
![[warning:]]()
Error ER1: The entity Task_method_ version does not existTask_method_ version
entity instantiated in this path to be referenced when this template is used.
Note: The
![[warning:]]()
Error ER1: The entity Task_method_ version does not existTask_method_ version
entity can be referenced in a template path by:
%^target = $representing_task.task_method_version%
where
target
is the parameter to which the
![[warning:]]()
Error ER1: The entity Task_method_ version does not existTask_method_ version
is bound.
![[warning:]]()
Error EXP-1: The EXPRESS entity Task_method_ version
does not exist in data/schemas/ap239_arm_lf.xml.
The reference to a task during its usage phase is always a reference to a task version, so consequently Task_version
is the only entity referencable in this template.
Allow the
External_class
entity instantiated in this path to be referenced when this template is used.
Note: The
External_class
entity can be referenced in a template path by:
%^target = $representing_task.ext_class%
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.
Identification_assignment-- Mark the Identification_assignment entity as -- referable when this template is used by binding it to the reference -- parameter id_assgn %^id_assgn =
Identification_assignment%
![[warning:]]()
Error P8: the template representing_task does not have a parameter name [id].Identification_assignment.identifier =
@idIdentification_assignment.role = '/IGNORE'
Identification_assignment.description = '/NULL'
![[warning:]]()
Error P4: the template representing_task does not have a parameter name [items].Identification_assignment.items ->
@items-- provide the role of the identification by classifying the Identification_assignment /
assigning_reference_data(
items=^id_assgn,
class_name=@id_class_name,
ecl_id=@id_ecl_id)/
![[warning:]]()
Error t3: the template representing_task does not have a parameter name [id_class_name]. Parameters are: task_id task_id_class_name
task_ecl_id task_org_id task_org_id_class_name task_org_id_ecl_id task_ver_id task_ver_id_class_name task_ver_ecl_id task_ver_org_id
task_ver_org_id_class_name task_ver_org_id_ecl_id task_vart_id task_vart_id_class_name task_vart_ecl_id task_vart_org_id task_vart_org_id_class_name
task_vart_org_id_ecl_id task_name task_description task_description end_part_id end_part_id_class_name end_part_id_ecl_id
end_part_org_id end_part_org_id_class_name end_part_org_id_ecl_id end_part_vn_id end_part_vn_id_class_name end_part_vn_id_ecl_id
end_part_vn_org_id end_part_vn_org_id_class_name part_vn_org_id_ecl_id target_part_id target_part_id_class_name target_part_id_ecl_id
target_part_org_id target_part_org_id_class_name part_org_id_ecl_id part_vn_id part_vn_id_class_name part_vn_id_ecl_id part_vn_org_id
part_vn_org_id_class_name part_vn_org_id_ecl_id items class_name ecl_id![[warning:]]()
Error t3: the template representing_task does not have a parameter name [id_ecl_id]. Parameters are: task_id task_id_class_name
task_ecl_id task_org_id task_org_id_class_name task_org_id_ecl_id task_ver_id task_ver_id_class_name task_ver_ecl_id task_ver_org_id
task_ver_org_id_class_name task_ver_org_id_ecl_id task_vart_id task_vart_id_class_name task_vart_ecl_id task_vart_org_id task_vart_org_id_class_name
task_vart_org_id_ecl_id task_name task_description task_description end_part_id end_part_id_class_name end_part_id_ecl_id
end_part_org_id end_part_org_id_class_name end_part_org_id_ecl_id end_part_vn_id end_part_vn_id_class_name end_part_vn_id_ecl_id
end_part_vn_org_id end_part_vn_org_id_class_name part_vn_org_id_ecl_id target_part_id target_part_id_class_name target_part_id_ecl_id
target_part_org_id target_part_org_id_class_name part_org_id_ecl_id part_vn_id part_vn_id_class_name part_vn_id_ecl_id part_vn_org_id
part_vn_org_id_class_name part_vn_org_id_ecl_id items class_name ecl_id-- assign an organization to the identifier and classify it as 'Owner_of' /
assigning_organization(
items=^id_assgn,
org_id=@org_id,
org_id_class_name=@org_id_class_name,
org_id_ecl_id=@org_id_ecl_id,
org_assgn_class_name='Owner_of',
org_assgn_ecl_id='http://www.plcsinc.org/plcs-proposed')/
![[warning:]]()
Error t3: the template representing_task does not have a parameter name [org_id]. Parameters are: task_id task_id_class_name
task_ecl_id task_org_id task_org_id_class_name task_org_id_ecl_id task_ver_id task_ver_id_class_name task_ver_ecl_id task_ver_org_id
task_ver_org_id_class_name task_ver_org_id_ecl_id task_vart_id task_vart_id_class_name task_vart_ecl_id task_vart_org_id task_vart_org_id_class_name
task_vart_org_id_ecl_id task_name task_description task_description end_part_id end_part_id_class_name end_part_id_ecl_id
end_part_org_id end_part_org_id_class_name end_part_org_id_ecl_id end_part_vn_id end_part_vn_id_class_name end_part_vn_id_ecl_id
end_part_vn_org_id end_part_vn_org_id_class_name part_vn_org_id_ecl_id target_part_id target_part_id_class_name target_part_id_ecl_id
target_part_org_id target_part_org_id_class_name part_org_id_ecl_id part_vn_id part_vn_id_class_name part_vn_id_ecl_id part_vn_org_id
part_vn_org_id_class_name part_vn_org_id_ecl_id items class_name ecl_id![[warning:]]()
Error t3: the template representing_task does not have a parameter name [org_id_class_name]. Parameters are: task_id task_id_class_name
task_ecl_id task_org_id task_org_id_class_name task_org_id_ecl_id task_ver_id task_ver_id_class_name task_ver_ecl_id task_ver_org_id
task_ver_org_id_class_name task_ver_org_id_ecl_id task_vart_id task_vart_id_class_name task_vart_ecl_id task_vart_org_id task_vart_org_id_class_name
task_vart_org_id_ecl_id task_name task_description task_description end_part_id end_part_id_class_name end_part_id_ecl_id
end_part_org_id end_part_org_id_class_name end_part_org_id_ecl_id end_part_vn_id end_part_vn_id_class_name end_part_vn_id_ecl_id
end_part_vn_org_id end_part_vn_org_id_class_name part_vn_org_id_ecl_id target_part_id target_part_id_class_name target_part_id_ecl_id
target_part_org_id target_part_org_id_class_name part_org_id_ecl_id part_vn_id part_vn_id_class_name part_vn_id_ecl_id part_vn_org_id
part_vn_org_id_class_name part_vn_org_id_ecl_id items class_name ecl_id![[warning:]]()
Error t3: the template representing_task does not have a parameter name [org_id_ecl_id]. Parameters are: task_id task_id_class_name
task_ecl_id task_org_id task_org_id_class_name task_org_id_ecl_id task_ver_id task_ver_id_class_name task_ver_ecl_id task_ver_org_id
task_ver_org_id_class_name task_ver_org_id_ecl_id task_vart_id task_vart_id_class_name task_vart_ecl_id task_vart_org_id task_vart_org_id_class_name
task_vart_org_id_ecl_id task_name task_description task_description end_part_id end_part_id_class_name end_part_id_ecl_id
end_part_org_id end_part_org_id_class_name end_part_org_id_ecl_id end_part_vn_id end_part_vn_id_class_name end_part_vn_id_ecl_id
end_part_vn_org_id end_part_vn_org_id_class_name part_vn_org_id_ecl_id target_part_id target_part_id_class_name target_part_id_ecl_id
target_part_org_id target_part_org_id_class_name part_org_id_ecl_id part_vn_id part_vn_id_class_name part_vn_id_ecl_id part_vn_org_id
part_vn_org_id_class_name part_vn_org_id_ecl_id items class_name ecl_id
The following entities are instantiated with attributes as specified:
The instance diagram in Figure
3
shows an example of the EXPRESS entities and templates that are instantiated by the template:
/representing_task(items='#1', class_name='Safety_critical', ecl_id='urn:plcs:rdl:std')/
(an illustration of the consolidated representing_task template is shown in
Figure
4 below.)
Figure 3 — Entities instantiated by representing_task template
The instance model in STEP ASCII exchange file format (ISO 10303 Part
21 syntax) is:
#1 = TASK_METHOD($,$,$,$,());
#2 = EXTERNAL_CLASS('/IGNORE','Safety_critical',$,#3);
#3 = EXTERNAL_CLASS_LIBRARY('urn:plcs:rdl:std',$);
#4 = CLASSIFICATION_ASSIGNMENT(#2,(#1),'/IGNORE');
The instance model in STEP XML exchange file format (ISO 10303 Part
28 ed.2 syntax) is:
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:
/representing_task(items='#1', class_name='Safety_critical', ecl_id='urn:plcs:rdl:std')/
Figure 4 — Instantiation of representing_task template
The following section details how the
representing_task
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 Assigning date
NOTE this characterization is optional.
