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.