Task specification ISO 10303-239 Representation

The following sections provide a detailed description on how to represent a Task Specification DEX using ISO 10303-239 PLCS. The representation of the Task Specification DEX is defined using PLCS capabilities, PLCS templates and PLCS reference data.

This description may be further tailored by specific parties by extending the reference data defined in the PLCS reference data library.

An overview of the information to be exchanged by the Task Specification DEX has been described in Section: Task Specification: Business Information Overview. A more detailed definition of the type of information that can be exchanged using the Task Specification DEX is provided in Section: Task Specification - Business Information Requirements. A summary of how this information is represented in PLCS is provided in Figure 19, and is expanded in subsequent sections.

Figure 19 —  Overview of PLCS constructs used to represent Task Specification

The rest of this section contains a step by step description on how each business information requirement defined in Section: Task Specification - Business Information Requirements is to be represented in PLCS, and is organized in accordance with the business information requirements.

Information related to a single task ISO 10303-239 representation - Table of content:

• Section: Product in focus;
• Section: Task definition;
• Section: Task resources;
• Section: Task trigger;
• Section: Task end item context;
• Section: Structured task;
• Section: Task effectivity / applicability;
• Section: Task compound conditions representation;
• Section: Task administrative information;
• Section: Task message;
• Section: Optional characterizations of templates;

Product in focus

Product in focus information includes:

• Identification;
• Name;
• Support classification.

Product in focus may be either a part or an element in a breakdown structure. These are represented as Part and Breakdown_element respectively, in PLCS.

NOTE    Detailed information requirements for describing the product in focus is defined in Section: Information requirements - Product in focus.

Part as product in focus

The PLCS representation for part as product in focus is described in Figure 20

Figure 20 —  PLCS representation of part as product in focus

Part identification

Basic representation of a part and its identification is done in accordance with the template representing_part. Template instantiation for a part being the product in focus within this DEX, must follow the rules defined in the template table: Template #1(Figure 20) below.

NOTE    Representation of version identification where the version identification is not known must follow the guidelines given in the assigning_identification template.

Additional part identifiers may be assigned to the Part using the template assigning_identification. Template instantiation for additional part identifiers must follow the rules defined in template table: Template #2(Figure 20) below.

NOTE    Additional characterizations of the respective identifier may be done in accordance with what is described under Section: Optional characterization of template assigning_identification .

Part name

Names may be assigned to the Part using the template assigning_identification. Template instantiation for part names must follow the rules defined in template table: Template #3(Figure 20) below.

NOTE    Additional characterizations of the respective name may be done in accordance with what is described under Section: Optional characterization of template assigning_identification .

Part support classification - repairability

Classification of the Part from a support perspective is done using the template assigning_reference_data. The basic support classification for a Part defines its repairability.

NOTE    Wherever the template assigning_reference_data is being used, it may be replaced by the usage of the assigning_code template.

Template instantiation for part support classification must follow the rules defined in template table: Template #4(Figure 20) below.

Breakdown element as product in focus

The PLCS representation for a breakdown element as being the product in focus is described in Figure 21

Figure 21 —  PLCS representation of breakdown element as the product in focus

Breakdown element identification

The basic representation of a breakdown element and its identification is done in accordance with the following templates:

• representing_breakdown_element, representing the breakdown element being the product in focus;
• representing_breakdown, for representation of the type of breakdown to which the breakdown element belongs;
• representing_part, for representation of the end item for which the breakdown is defined.

Instantiation of the respective template for this DEX must follow the rules defined in the respective template table below:

• template table: Template #5(Figure 21) for the end item;
• template table: Template #6(Figure 21) for the type of breakdown;
• template table: Template #7(Figure 21) for the breakdown element.

NOTE    Representation of version identification where the version identification is not known must follow the guidelines given in the assigning_identification template.

NOTE    Representation of version identification where the version identification is not known must follow the guidelines given in the assigning_identification template.

NOTE    Representation of version identification where the version identification is not known must follow the guidelines given in the assigning_identification template.

Additional identifications may be assigned to the Breakdown_element using the template assigning_identification. Template instantiation for additional breakdown element identifiers must follow the rules defined in template table: Template #8(Figure 21) below.

NOTE    Additional characterizations of the respective identifier may be done in accordance with what is described under Section: Optional characterization of template assigning_identification .

Breakdown element name

Names may be assigned to the Breakdown_element using the template assigning_identification. Template instantiation for breakdown element names must follow the rules defined in template table: Template #9(Figure 21) below.

NOTE    Additional characterizations of the respective name may be done in accordance with what is described under Section: Optional characterization of template assigning_identification .

Breakdown element support classification

Classification of the Breakdown_element as being important from a support perspective is done using the template assigning_reference_data.

NOTE    A Breakdown_element may have many different support classifications, e.g. 'Maintenance significant item' and 'Line replaceable'.

NOTE    Wherever the template assigning_reference_data is being used, it may be replaced by the usage of the assigning_code template.

Template instantiation for breakdown element support classification must follow the rules defined in template table: Template #10(Figure 21) below.

Task definition

Task definition information includes:

• Task identification and revisioning;
• Task assignment;
• Task name;
• Task categorization;
• Task description;
• Task objective;
• Task justification;
• Task criticality;
• Task precondition;
• Task post condition;
• Task legal, health and safety advisories;
• Task elapsed time;
• Task labour time;
• Task document reference;
• Task special requirements indication;
• Task note / remark.

NOTE    Detailed information requirements for task definition are defined in Section: Information requirements - Task definition.

The PLCS representation for task definition is described in Figure 22

Figure 22 —  PLCS representation of Task definition

NOTE    The first sections of the DEX focuses on defining a simple Task. Representation of a structured task is defined in Section: Task structure.

Task identification and revisioning

Basic representation of a task and its identification is done in accordance with the template representing_task_simple. A simple task in PLCS is represented using the following entities:

• Task_method, representing the overall task;
• Task_method_version, representing a version (revision) of the task;
• Task_step, representing the details of the task.

Template instantiation for a simple task must follow the rules defined in the template table: Template #11(Figure 22) below.

NOTE    Representation of version identification where the version identification is not known must follow the guidelines given in the assigning_identification template.

Additional identifications for a task may be assigned to the Task_method using the template assigning_identification. Template instantiation for additional task identifiers must follow the rules defined in template table: Template #13(Figure 22) below.

NOTE    Additional characterizations of the respective identifier may be done in accordance with what is described under Section: Optional characterization of template assigning_identification .

Task assignment

Assignment of a task to the product in focus is done in accordance with the template assigning_task_method_version. Template instantiation for the assignment of the task to the product in focus must follow the rules defined in template table: Template #12(Figure 22) below.

Task name

A mandatory task name is part of the template table: Template #11(Figure 22) defined under Section: Task identification and revisioning above.

Additional task names may be assigned to the Task_method using the template assigning_identification. Template instantiation for additional task names must follow the rules defined in template table: Template #14(Figure 22) below.

NOTE    Additional characterizations of the respective task name may be done in accordance with what is described under Section: Optional characterization of template assigning_identification .

Task categorization

Task categorization can be assigned to the Task_method using the template assigning_reference_data.

NOTE    Wherever the template assigning_reference_data is being used, it can be replaced by the usage of the assigning_code template.

Template instantiation for task categorization must follow the rules defined in template table: Template #15(Figure 22) below.

Task description

A mandatory task description is part of the template table: Template #11(Figure 22) defined under Section: Task identification and revisioning above.

Additional task descriptions can be assigned to the Task_step using the template assigning_descriptor. Template instantiation for additional task descriptions must follow the rules defined in template table: Template #16(Figure 22) below.

NOTE    Additional characterizations of the respective description may be done in accordance with what is described under Section: Optional characterization of template assigning_descriptor .

Task objective

Task objective is represented as an instance of the Task_objective entity. A textual description of the task objective is represented as a description being assigned to the Task_objective, using the assigning_descriptor template. Template instantiation for the description of the Task objective must follow the rules defined in template table: Template #17(Figure 22).

NOTE    Additional characterizations of the respective task objective description may be done in accordance with what is described under Section: Optional characterization of template assigning_descriptor .

Task justification

Task justification can be assigned to the Task_method_version using the template assigning_justification. Template instantiation for task justification must follow the rules defined in template table: Template #18(Figure 22) below.

NOTE    Additional characterizations of the justification and its description, can be done in accordance with what is described under Section: Optional characterization of template assigning_justification and Section: Optional characterization of template assigning_descriptor .

Task criticality

Task criticality can be assigned to the Task_method using the template assigning_reference_data.

NOTE    Wherever the template assigning_reference_data is being used, it can be replaced by the usage of the assigning_code template.

Template instantiation for task criticality must follow the rules defined in template table: Template #19(Figure 22) below.

Task precondition

The simplest representation of task precondition(s) is done using the template assigning_condition_text_based. This template provides the ability to textually describe the task precondition. Task precondition is assigned to the Task_step. Template instantiation for task precondition must follow the rules defined in template table: Template #20(Figure 22) below.

NOTE    For representation of compound preconditions see Section: Task compound conditions representation below .

NOTE    Task preconditions may also be represented as task steps in a structured task. See Section: Structured task.

Task post condition

The simplest representation of task post condition(s) is done using the template assigning_condition_text_based. This template provides the ability to textually describe the task post condition. Task post condition is assigned to the Task_step. Template instantiation for task post condition must follow the rules defined in template table: Template #21(Figure 22) below.

NOTE    For representation of compound post conditions see Section: Task compound conditions representation below .

NOTE    Task post conditions may also be represented as task steps in a structured task. See Section: Structured task.

Task legal, health and safety advisories

Task legal, health and safety advisories are represented as an instance of the Advisory_task_step entity. A textual description of task legal, health and safety advisories is represented as a description being assigned to the Advisory_task_step, using the assigning_descriptor template. Template instantiation for the description of task legal, health and safety advisories must follow the rules defined in template table: Template #22(Figure 22).

NOTE    Additional characterizations of the respective description may be done in accordance with what is described under Section: Optional characterization of template assigning_descriptor .

Task elapsed time

Task elapsed time is represented as a property being assigned to the Task_step entity, using the assigning_process_property and process_property_numeric templates. Template instantiation for the task elapsed time must follow the rules defined in template table: Template #23(Figure 22) and template table: Template #24(Figure 22).

NOTE    Additional characterizations of the respective template used for representing the elapsed time property and its value, may be done in accordance with what is described under Section: Optional characterization of templates for property representation .

NOTE    The usage of the template process_property_numeric may be replaced by the usage of:

• process_property_limit;
• process_property_range;
• process_property_text;
• process_property_w_tolerances.

Task labour time

Task labour time is represented as a property being assigned to the Task_step entity, using the assigning_process_property and process_property_numeric templates. Template instantiation for the task labour time must follow the rules defined in template table: Template #25(Figure 22) and template table: Template #26(Figure 22).

NOTE    Additional characterizations of the respective template used for representing the labour time property and its value, may be done in accordance with what is described under Section: Optional characterization of templates for property representation .

NOTE    The usage of the template process_property_numeric may be replaced by the usage of:

• process_property_limit;
• process_property_range;
• process_property_text;
• process_property_w_tolerances.

Task document references

Task document references are represented as Document_version being assigned to the Task_step entity, using either the assigning_document_reference or the assigning_partial_document_reference template. Template instantiation for task document reference must follow the rules defined in template table: Template #27(Figure 22) or in template table: Template #28(Figure 22).

NOTE    Representation of version identification where the version identification is not known must follow the guidelines given in the assigning_identification template.

NOTE    Representation of version identification where the version identification is not known must follow the guidelines given in the assigning_identification template.

Task special requirements indication

Task special requirements indication can be assigned to the Task_step using the template assigning_reference_data.

NOTE    Wherever the template assigning_reference_data is being used, it can be replaced by the usage of the assigning_code template.

Template instantiation for task special requirements indication must follow the rules defined in template table: Template #29(Figure 22) below.

Task note / remark

Task notes/remarks can be assigned to the Task_method_version using the template assigning_descriptor. Template instantiation for task notes/remarks must follow the rules defined in template table: Template #30(Figure 22) below.

NOTE    Additional characterizations of the respective note or remark may be done in accordance with what is described under Section: Optional characterization of template assigning_descriptor .

Task resources

Task required resources information includes:

• Resource identification;
• Resource description (specification);
• Resource document reference;
• Resource realization;
  • Material resource realization, including the following additional material resource related information;
    • Material resource identification;
    • Material resource name;
    • Material resource hazardous classification;
    • Material resource document reference;
    • Material resource support classification;
  • Human resource realization;
    • Human resource name;
  • Organizational resource realization;
    • Organizational resource identification;
    • Organizational resource name;
  • Document resource realization;
    • Document resource identification;
    • Document resource name;
• Resource assignment;
• Resource role;
• Required quantity, including quantity determination;
• Resource probability;
• Estimated resource cost;
• Estimated resource elapsed time;
• Resource usage indication;
• Human resource estimated labour time;
• Alternative / substitute resource requirement.

NOTE    Detailed information requirements for task resources are defined in Section: Information requirements - Task Resources.

The PLCS representation for task resources is described in Figure 23

Figure 23 —  PLCS representation of Task resources

Resource identification

Basic representation of a resource and its identification is done in accordance with the template representing_resource_item, where the Resource_item entity defines the resource.

NOTE    A Resource_item may have one or many realizations, e.g. Parts, Type_of_persons etc, as described in the next section.

Template instantiation for the basic representation of a resource must follow the rules defined in the template table: Template #31(Figure 23) below.

NOTE    Additional characterizations of the respective resource can be done in accordance with what is described under the characterization section in the representing_resource_item template.

Proposed characterizations of representing_resource_item template (i.e. the Resource_item entity) includes:

• assigning_identification, for additional identification codes and/or names of the identified resource;

Template instantiation for the assignment of additional identification codes and/or names to the Resource_item entity, instantiated within the template table: Template #31(Figure 23), must follow the rules defined in the template table: Template #32(Figure 23) below.

NOTE    Additional characterizations of the respective identifier/name may be done in accordance with what is described under Section: Optional characterization of template assigning_identification .

Resource description (specification)

Resource description (specification) can be assigned to the Resource_item using the template assigning_descriptor. Template instantiation for resource description (specification) must follow the rules defined in template table: Template #33(Figure 23) below.

NOTE    Additional characterizations of the respective description/specification may be done in accordance with what is described under Section: Optional characterization of template assigning_descriptor .

Resource document reference

Resource document references are represented as Document_version being assigned to the Resource_item entity, using the assigning_document_reference template. Template instantiation for resource document reference must follow the rules defined in template table: Template #34(Figure 23) below.

NOTE    Representation of version identification where the version identification is not known must follow the guidelines given in the assigning_identification template.

NOTE    The use of the assigning_document_reference template may be replaced by the use of assigning_partial_document_reference. For instantiation of the assigning_partial_document_reference template see template table: Template #28(Figure 22).

NOTE    Additional characterizations of the respective referenced document (including partial document) may be done in accordance with what is described under Section: Optional characterization of template assigning referenced document .

Resource realization

Resource realizations includes:

• Spare parts, consumables, tools, test equipments with specific part numbers, where the resource identification/specification might be e.g. a NATO Stock Number;
• Type of persons, e.g. skill levels;
• Organizations, both in terms of specific organizations and types of organizations (e.g. line of maintenance, or work centre identified through e.g. discipline such as electrical, mechanical etc;
• Documents (e.g. check list, form etc), where the resource identification/specification might be a requirement for a feedback form.

NOTE    Facilities and infrastructure resources are normally just defined as Resource_items, using the representing_resource_item template above, i.e. they do not have a corresponding realization.

NOTE    In business situations where the resource requirement refers directly to a Part, Type_of_person etc, i.e. there is no notion of a resource concept within the business domain, there still needs to be a Resource_item in between the task and the resource.

Representation of a resource realization is done in accordance with the template representing_resource_item_realization.

Template instantiation for a resource realization must follow the rules defined in the template table: Template #35(Figure 23) below.

Detailed representation of material resource realizations is done in accordance with the template representing_part and the part name is represented in accordance with assigning_identification.

Template instantiations for a material resource realization, and its name, must follow the rules defined in the template table: Template #36(Figure 23) and template table: Template #37(Figure 23) below.

Additional optional characterization of a material resource realization includes:

• Material resource hazardous classification;
• Material resource document reference;
• Material resource maturity classification.

Template instantiations for these optional characterizations of a material resource realization must follow the rules defined in:

• Section: Material resource hazardous classification Material resource hazardous classification;
• Section: Material resource document reference Material resource document reference;
• Section: Material resource support classification Material resource maturity classification.

NOTE    Representation of version identification where the version identification is not known must follow the guidelines given in the assigning_identification template.

NOTE    Additional characterizations of the respective name may be done in accordance with what is described under Section: Optional characterization of template assigning_identification .

Material resource hazardous classification

Material hazardous classification is assigned to a Part_view_definition of the Part representing the material resource, using the template assigning_reference_data.

NOTE    Wherever the template assigning_reference_data is being used, it can be replaced by the usage of the assigning_code template.

Template instantiation for material hazardous classification must follow the rules defined in template table: Template #54(Figure 23) below.

Material resource document reference

Material resources such as spares may have document references e.g. exploded views.

Material resource document reference is represented as a Document_version being assigned to the Part_version of the Part representing the material resource, using the assigning_document_reference template. Template instantiation for each material resource document reference must follow the rules defined in the template table: Template #55(Figure 23) below.

NOTE    Representation of version identification where the version identification is not known must follow the guidelines given in the assigning_identification template.

NOTE    The use of the assigning_document_reference template may be replaced by the use of assigning_partial_document_reference. For instantiation of the assigning_partial_document_reference template see template table: Template #28(Figure 22).

NOTE    Additional characterizations of the respective referenced document (including partial document) may be done in accordance with what is described under Section: Optional characterization of template assigning referenced document .

Material resource support classification

Material resource support classification, e.g. part maturity, is assigned to a Part_view_definition of the Part representing the material resource, using the template assigning_reference_data.

NOTE    Wherever the template assigning_reference_data is being used, it can be replaced by the usage of the assigning_code template.

Template instantiation for material resource maturity classification must follow the rules defined in template table: Template #56(Figure 23) below.

Detailed representation of human resource realizations is done in accordance with the template referencing_person_typical.

Template instantiation for a human resource realization must follow the principles defined in the template table: Template #38(Figure 23) below.

NOTE    In a data exchange the usage of reference data within template table: Template #38(Figure 23) may be replaced by the usage of codes in order to determine type of person (also see template assigning_code).

Detailed representation of document resource realizations is done in accordance with the template representing_document. An optional document name is represented in accordance with the assigning_identification template.

Template instantiation for a document resource realization and its name must follow the principles defined in the template table: Template #39(Figure 23) and template table: Template #40(Figure 23) below.

NOTE    Representation of version identification where the version identification is not known must follow the guidelines given in the assigning_identification template.

NOTE    Additional characterizations of the respective name may be done in accordance with what is described under Section: Optional characterization of template assigning_identification .

Detailed representation of organizational resource realizations is done in accordance with the templates representing_organization_typical and representing_organization.

Template instantiation for a organizational resource realization must follow the principles defined in template table: Template #41(Figure 23) and template table: Template #42(Figure 23) templates below.

NOTE    In a data exchange the usage of reference data within template table: Template #41(Figure 23) may be replaced by the usage of codes in order to determine type of organization (also see template assigning_code).

Resource assignment

Resource requirements are assigned to the task details, i.e. the Task_step.

Detailed representation of assigning a required resource to a task is done in accordance with the template assigning_required_resource.

Template instantiation for a assigning a required resource must follow the principles defined in the template table: Template #43(Figure 23) below.

NOTE    Subclasses of "Required_resource" (urn:plcs:rdl:std:Required_resource) defines the role for the Resource_item within the task under consideration. Examples of roles can be; spare, test equipment, supervisor, etc. The same Resource_item may have different roles in different tasks.

Resource role

The role of the required resource is part of template table: Template #43(Figure 23). The role is determined using the 'class_name' and 'ecl_id' input parameters for template table: Template #43(Figure 23).

Resource quantity

Required resource quantity is represented as a property being assigned to the Required_resource_by_resource_item entity, using the assigning_resource_property and resource_property_numeric templates. Template instantiation for the required resource quantity must follow the rules defined in template table: Template #44(Figure 23) and template table: Template #45(Figure 23).

NOTE    Additional characterizations of the respective template used for representing the required quantity and its value, may be done in accordance with what is described under Section: Optional characterization of templates for property representation .

NOTE    The usage of the template resource_property_numeric may be replaced by the usage of either of:

• resource_property_limit;
• resource_property_range;
• resource_property_text;
• resource_property_w_tolerances.

Resource quantity determination

Resource quantity determination can represented, either by specialization of the "Quantity" (urn:plcs:rdl:std:Quantity) class in the reference data library, or by classification of the Resource_property_representation entity instantiated in template table: Template #45(Figure 23).

Resource quantity determination by classification is done using the template assigning_reference_data.

NOTE    Wherever the template assigning_reference_data is being used, it can be replaced by the usage of the assigning_code template.

Template instantiation for resource quantity determination must follow the rules defined in template table: Template #46(Figure 23) below.

Resource probability

Required probability is represented as a property being assigned to the Required_resource_by_resource_item entity, using the assigning_resource_property and resource_property_probability_numeric templates. Template instantiation for the required resource quantity must follow the rules defined in template table: Template #47(Figure 23) and template table: Template #48(Figure 23) below.

Estimated resource cost

Estimated resource cost is represented as a property being assigned to the Required_resource_by_resource_item entity, using the assigning_resource_property and resource_property_numeric templates. Template instantiation for the estimated resource cost must follow the rules defined in template table: Template #49(Figure 23) and template table: Template #50(Figure 23).

NOTE    Additional characterizations of the respective template used for representing the estimated cost and its value, may be done in accordance with what is described under Section: Optional characterization of templates for property representation .

NOTE    The usage of the template resource_property_numeric may be replaced by the usage of either of:

• resource_property_limit;
• resource_property_range;
• resource_property_text;
• resource_property_w_tolerances.

Estimated resource elapsed time

Estimated resource elapsed time is represented as a property being assigned to the Required_resource_by_resource_item entity, using the assigning_resource_property and resource_property_numeric templates. Template instantiation for the resource elapsed time must follow the rules defined in template table: Template #51(Figure 23) and template table: Template #52(Figure 23).

NOTE    Additional characterizations of the respective template used for representing resource elapsed time and its value, may be done in accordance with what is described under Section: Optional characterization of templates for property representation .

NOTE    The usage of the template resource_property_numeric may be replaced by the usage of either of:

• resource_property_limit;
• resource_property_range;
• resource_property_text;
• resource_property_w_tolerances.

Resource usage indicator

Resource usage indicator is assigned to the Required_resource_by_resource_item using the template assigning_reference_data.

NOTE    Wherever the template assigning_reference_data is being used, it can be replaced by the usage of the assigning_code template.

Template instantiation for resource usage indicator must follow the rules defined in template table: Template #53(Figure 23) below.

Human resource estimated labour time

Human resource estimated labour time is represented as a property being assigned to the Required_resource_by_resource_item entity, using the assigning_resource_property and resource_property_numeric templates. Template instantiation for the human resource estimated labour time must follow the rules defined in template table: Template #57(Figure 23) and template table: Template #58(Figure 23).

NOTE    Additional characterizations of the respective template used for representing resource labour time and its value, may be done in accordance with what is described under Section: Optional characterization of templates for property representation .

NOTE    The usage of the template resource_property_numeric may be replaced by the usage of either of:

• resource_property_limit;
• resource_property_range;
• resource_property_text;
• resource_property_w_tolerances.

Alternative / substitute resource requirement

Alternative or substitute resource requirements can be defined using the template representing_required_resource_relationship.

Template instantiation for alternative or substitute resource requirements must follow the rules defined in template table: Template #59(Figure 23) below.

Task trigger

Task trigger information includes:

• Scheduled task triggers, e.g.;
  • Operating time;
  • Calendar time;
  • Number of units of use;
• Event based task triggers, e.g.;
  • Pre operative;
  • Post operative;
  • Condition based;
  • Failure;
  • Role change;
  • Opportunistic.

NOTE    Detailed information requirements for task triggers are defined in Section: Information requirements - Task Trigger.

The PLCS representation for task trigger is described in Figure 24

Figure 24 —  PLCS representation of Task trigger

All types of task triggers are represented as Conditions, along with a Condition_assignment being classified as "Trigger" (urn:plcs:rdl:std:Trigger), or subclass thereof. The Condition_assignment is assigned to the Task_method_version_assignment representing the assignment of a task to the product in focus (Part_version defined in template table: Template #1(Figure 20) or Breakdown_element_version defined in template table: Template #7(Figure 21)).

Scheduled task triggers

Scheduled task triggers may either be defined in a way that they are computable, or just defined as a text string in which case the content need to be analyzed by a human in order to decide when the condition defined in the task trigger is being fulfilled.

Computable scheduled task triggers

Computable scheduled task triggers relates to a measurable value, e.g. calendar time, flight hours etc. Scheduled task trigger parameters are represented as Independent_property being referenced from the Condition_parameter entity.

The simplest form of computable scheduled task triggers contains just one parameter, and is represented using the assigning_condition template.

Template instantiation for computable scheduled task triggers, containing one parameter, must follow the rules defined in template table: Template #60(Figure 24), below.

NOTE    Representation of task triggers that requires advanced logical expressions in terms of e.g. AND/OR/XOR conditions are described in Section: Task compound conditions representation below.

The property that defines the parameter for the computable scheduled task trigger is represented using the representing_independent_property template.

Template instantiation for the property defining the computable scheduled task trigger parameter must follow the rules defined in template table: Template #61(Figure 24) below.

The property value for the task trigger parameter can be represented as either:

• A single numerical value using the independent_property_numeric template;
• A single limit value using the independent_property_limit template;
• A range including numerical values for lower and upper limits using the independent_property_range template;
• A single numerical value with tolerances using the independent_property_w_tolerances.

Template instantiation for the value of the task trigger property must follow the rules defined in either of the following template tables below:

• template table: Template #62(Figure 24) for single numerical value;
• template table: Template #63(Figure 24) for single limit value;
• template table: Template #64(Figure 24) for a range including numerical values with lower and upper limits;