Define Where Task Cards Should Be Used
Explanation
This activity is used to define where task cards should be used, i.e., the task cards that should be performed
when maintenance is carried out.
Task cards can be used on maintenance event types such as interval maintenance, condition limits, modifications,
faults, life limits, and post maintenance checks. You can define a task card to use with one event type exclusively
(for instance, one specific type of interval maintenance) or for multiple event types at the same time (for
instance, on three different types of interval maintenance, two types of modifications and five types of condition
limits).
Task cards are commonly broken down into more detailed activities, referred to as subtasks. For more information
on connecting subtasks to task cards, refer the online help file Define Subtasks for Task Cards.
Maintenance codes can be connected to a task card in the Maintenance Event Codes per Task
Card page as described below. This page can be opened directly or by clicking on the Connect
Maintenance Event Codes option in the Task Card page.
- For interval maintenance and convenience tasks, connect the required maintenance codes.
- For condition based maintenance, connect the required condition category and condition code.
- For modifications, connect the required modification revision and execution type.
- For fault repairs, connect the required function and fault code.
- For LLP replacements, connect the required stress rating ID and part revision. Connected task card(s) will be
used to remove the LLP from its parent once the LLP expires.
- For PMCs, connect the required PMC definition.
This activity is similar to the Add or Remove Connection to Task Card activity. The difference is that
instead of connecting task cards in the dedicated pages such as, Task Cards per Maintenance
Code, you are connecting the required event code(s) to the task card in a single page.
Prerequisites
- A task card must be defined for the part revision.
- To register interval maintenance data for a task card, maintenance codes must be defined.
- To register condition limits for a task card, the condition limits must be predefined on the part
revision.
- In order to connect modifications to a task card, a modification must be defined. Furthermore, parts and part
revisions including the part revision for which the task card is created must be assigned to the
modification.
- To connect fault functions to a task card, fault codes must have been connected for the functions of the
relevant product model.
- To register task cards for an LLP (life limited part), the part must be defined as an LLP and have stress
ratings connected to it.
- To connect post maintenance checks to a task card, the post maintenance check must be defined. Further, the
part revision for which the task card is created must be assigned to the post maintenance check.
System Effects
- The task cards connected to the event codes are retrieved automatically when the corresponding maintenance
event is included on a maintenance order.
- When a fault is reported, and the given product model and function structure has predefined task cards, these
task cards will be retrieved automatically for the fault. This information can be viewed in the
Manage Fault Information/Task Cards tab.
- If subtasks are connected to the task card, these can be viewed in the Subtasks tab per event
code, e.g., in the Task Cards per Maintenance Code page.