Task Synchronization
Features
If a task that has related tasks is created during the Critical Time Window (CTW), the task and its related tasks may receive a synchronization priority boost according to their Latest Starting Date (LSD) priority values.
If a task that has related tasks is selected during the CTW, its related tasks may receive a synchronization priority boost according to their LSD priority values.
NoteExample
You define the CTW for both LSD and synchronization priority purposes as beginning 60 minutes before the LSD and ending when the LSD is reached.
Task A1 is created from request X two minutes after the commencement of its CTW. Since it has no related tasks, it is not given a synchronization priority.
Task A2 (related to task is created from request X four minutes later, three minutes after the commencement of its CTW.
Task A1 receives a synchronization priority value of 10 since 10% (six minutes) of its CTW has elapsed.
Task A2 receives a synchronization priority value of 5 since 5% (three minutes) of its CTW has elapsed.
Task A3 is created from request X twelve minutes later, six minutes after the commencement of its CTW.
Both tasks A1 and A2 receive a synchronization priority value boost of 20 since a further 20% of their CTWs have elapsed.
Task A3 receives a synchronization priority value of 10 since 10% of its CTW has elapsed.
Task A1 is selected three minutes later.
Both tasks A2 and A3 receive a synchronization priority value boost of 5 since a further 5% of their CTWs have elapsed.
Task A2 is selected after another fifteen minutes.
Task A3 receives a synchronization priority value boost of 25 since a further 25% of its CTW has elapsed.
Thus Tasks A1, A2 and A3 receive synchronization priority values as follows:
Synchro Priorities |
Creation |
Selection |
Total Synchro Priority Value |
|||
Task A1 |
Task A2 |
Task A3 |
Task A1 |
Task A2 |
||
Task A1 |
- |
+ 10 |
+ 20 |
30 |
||
Task A2 |
- |
+ 5 |
+ 20 |
+ 5 |
30 |
|
Task A3 |
- |
+ 10 |
+ 5 |
+ 25 |
40 |
|
At task selection , these synchronization priority values are multiplied by the relevant weighting factors to influence the tasks’ static & synchronization priority model entities and, ultimately, the total priorities of the tasks.