Define Subtask

Explanation

This activity is used to define a subtask.

Task cards are commonly broken down into more detailed activities referred to as subtasks. A subtask will contain similar information as the task card. For instance, the location at which the work is to be performed, execution phase, functional breakdown, resources, material, zones, access panels, and sign off requirements.

The number of required levels in the function breakdown is managed by object property settings. For serial parts, the valid object property is FUNCTION_LEVEL_INSTR. For vehicle parts it is FUNC_LEVEL_INSTR_VEH. Legal values for these settings will be 0, 1, 2 and 3. The object properties can be found in Object Properties page.

You can connect one or more documents to the selected subtask via Documents in the Attachments. When the subtask is deleted, the connection to the attached documents will also be deleted.

Note that is it possible to remove a subtask if it is not connected to a task card. All task cards to which the subtask is connected can be viewed in the Subtask/Task Cards tab.

Prerequisites

• A valid part revision must exist.

The following prerequisites depend on the values you will enter on the subtask:

• When defining subtasks, the template structure together with its product, model and function structure must exist.
• Task card types, locations, strategies, and execution phases must exist.

System Effects

• Subtasks are defined and resources, material, zones and sign off requirements can be entered on the subtask.
• Subtasks of the same part number and revision can be connected to task cards. To use the subtask to an active task card, at least one resource with the Person demand type must be specified on the subtask.

Pages

Subtask
Subtasks

Activity Diagrams

Define Task Cards