Relationship Category

Valid Relationships

Planning

• "Block Schedule” - Indicates that the set of tasks need to be carried out under a primary task for planning.  Example C-Check –primary task can have T1, T2, T3 etc; as child tasks.

Note: When you select a primary task in Block Schedule relationship for processing, such as defining maintenance programs, planning documents or execution documents, the system picks only those child tasks that are defined for the primary task. The child tasks of any of the child tasks related to the primary task are not taken into consideration for any process. For example, primary task T1 comprises T2, T3 and T4 as base tasks; base task T4 in turn shares a Block Schedule relationship with T10 and T12. Let us assume you include T1 in a visit package. Now, the system automatically includes all the base tasks (T2, T3 and T4) into the visit package but does not take into account the Block Schedule relationship of the base task T4. This happens because the system only considers the first level in the hierarchy of a Block Schedule relationship.

Execution

• “Concurrent Exec. - Group” - Indicates that the primary task and the related task as a group must be executed concurrently. Example if T1 is the primary task, the related Task T2 will be executed concurrently.

• “Concurrent Exec. - Specific” - Indicates that the   primary task can be executed only if the other related task has been executed. Example, only after executing T2 - related task, the primary task T1 must be executed.

• “Concurrent Exec. - Conditional” - Indicates that the primary task and related task are executed on conditional basis. Example, After executing T1-primary task, its outcome will decide whether to perform the related task- T2 or T3.

Note: When you select a primary task sharing “Concurrent Exec.” relationship for processing, such as defining maintenance programs, planning documents or execution documents, the system automatically picks all child tasks defined for the primary task as well as all child tasks of any child task bound by the “Concurrent Exe.” relationship from the entire hierarchy of tasks till redundancy. For example, task T1 shares “Concurrent Exec.” relationship with task T2 and T3; while T3 shares “Concurrent Exec.” relationship with T4 and T5; child task T5 is in “Concurrent Exec.” Relationship with task T6; T6 is bound to T1 by “Concurrent Exec.” relationship. In such a scenario, the system picks up tasks T2, T3, T4, T5, and T6 for processing. The system stops from picking up any more tasks after T6, as T1, its child task is the first primary task in the hierarchy of task relationship and any further selection of tasks will lead to repetition.

• “Predecessor - Constrained” - Indicates that the related task is executed based on the completion of the predecessor task. Example, if T1 is the predecessor task, the task T2 will be executed only on completion of the T1.

• “Conflict” – Indicates that the two tasks are conflicting and cannot be executed simultaneously. Example, the primary task T1 and the related task T2 are two tasks which cannot be executed simultaneously.

Post Compliance

• “Initiate Schedule” - Indicates the initiation of a related task after the completion of the primary task. Example, the related task, T2 will be initiated only on completion of the primary task T1.

• “Initiate Records Follow - Up” - Indicates the initiation of records follow -up after the completion of the task.

• “Terminate Schedule”- Indicates the termination of a related task after the completion of primary task. Example, the related task, T2 will be terminated on compliance of the primary task T1.

• “Supersede” – Indicates the duly completion of a related task on completion of the parent task. Example, if the primary task T1 is completed, the related task T2 will also be marked as completed.

• "Conditional" - "Indicates follow-up action subsequent to completion and, evaluation of the follow-up action is mandatory for a task. You can record details of follow-up action for a task in the “Edit Parameter Reading / Conditional Maint. Evaluation” page of the Edit Task activity.