This activity is used to define a task card that can be used on maintenance event types, i.e., interval maintenance, modifications, condition limits, faults, life limits, and post maintenance checks.
There can be one or more revisions of a certain task card. Each task card revision will contain information on the work that is to be performed when serials with the defined part revision are to be maintained. What, where, and the workload of the task card is defined here. Resources, material, zones, sign off requirements, task card criticality, condition measurements, event codes the task card is to be included on, and subtasks can be specified. At creation, the task card revision will automatically receive the Preliminary status. When the task card revision is in this status (or in the Active status) it will be possible to connect the task card to event codes, such as, maintenance codes, condition limits, modification codes, fault functions, life limits, and post maintenance check IDs.
Active task cards that are connected to maintenance event codes will be retrieved automatically to a maintenance order when a maintenance event with the event code is included on the order. This is applicable for maintenance orders with distribution type Work Order or Execution Logic Structure. In addition, active task cards may be connected to or canceled from a maintenance order based on your requirements. When releasing the maintenance order, all connected task cards (that are not already canceled) will be transferred to the work order.
Following is a summary of changes that can be made to a task card at the different statuses:
| Status | Description |
| Preliminary |
|
| Active |
|
| Obsolete |
|
Each task card is defined for the specific part revision, e.g., aircraft engine or locomotive bogie, on which the task card is applied. The affected part revision in the structure on which work is to be performed, for instance a pump in the aircraft engine or a wheel on the locomotive, can be indicated. You may also indicate where in the function structure the work is to be performed. If the work is to be performed directly on the part revision (aircraft engine/train), the affected part revision must be the same as the task card part revision.
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.
For each task card, you can specify where the work is to be performed by registering one of the following field combinations:
You can connect one or more documents to the selected task card via Documents in the Attachments. When the task card is deleted, the connection to the attached documents will also be deleted.
When registering a new revision of a part that requires new task cards, it is possible to copy the task card information from a previous part revision and then make changes to the task card for the new part revision. It is also possible to copy between revisions of different part numbers to reuse the task cards on parts with the same maintenance needs.
The following prerequisites depend on the values you will enter on the task card revision: