This action is available on an unassigned task/assigned task resulting the Work Task Dependency to be shown in an dialog. With this simple click, the dispatcher can quickly go through all types of dependencies defined for the Task namely Finish To Start, Start To Start, Combined and Ordered along with its dependency attributes. After referring to the dependencies dispatcher can simply use the drag and drop option on the Gantt to allocate it to the right resource in the right time slot not violating any dependencies. In case if there are any Dependency violation it will be indicated on the Work Assignment by an exception sign and Dispatcher can use Reassign command available on the card to resolve the raised exception manually. Only "Finish To Start" and "Start To Start" Dependency types are validated in drag and drop to support the Manual scheduling process.
Finish To Start dependency type can be used when there is a task that must be
started/completed before another task can commence.
Consider two tasks configured
as follows:
task_id1 = Work Task A
task_id2 = Work Task B
If Work Task
A must be done before Work Task B, Then Work Task A will be set as a "Finish
To Start" for Work Task B.
Start To Start dependency type can be used when there are two tasks that must
be scheduled at the same time. A typical example would be a two-person job, which
would be defined as two Start To Start tasks, so that it may appear on each resource’s
timeline at the same time.
Consider two tasks configured as follows:
task_id1
= Work Task A
task_id2 = Work Task B
If Work Task A must be started at the
same time of Work Task B, Then Work Task A will be set as a "Start To Start" for
Work Task B.
Combined tasks are similar to Start To Start tasks, except that they may also
be scheduled, one after the other, to a single resource. So they are like a piece
of work that could be done by one person, but it would be done in half the time
if two people did it.
Consider two tasks configured as follows:
task_id1
= Work Task A
task_id2 = Work Task B
If the above are scheduled back-to-back
then the ordering may be either A-B or B-A. Then Work Task A will be set as a "Combined"
for Work Task B.
It is possible to specify that two tasks must be done together, one immediately
after the other, if they are scheduled. This is useful if there is a sensible order
in which to do a number of tasks that are at the same location e.g. in a block of
flats. This can also be used to define a suggested order between the tasks. If task
A should be done immediately before task B, the data should be set as follows:
task_id1 = Work Task A
task_id2 = Work Task B
To specify that the tasks should
be done one after the other in either direction, set we can use ORDER_TWO_WAY.
An active Dataset need to be defined for the desired company. Dispatch console
has to be loaded with data mainly Resources and Unfulfilled demand lines. Resources
must be connected to Resource Group, Competencies, Licenses and Regions etc. Dependencies
has to be defined for the task along with related dependency attributes.
As a result of this activity a dialog will be open up on top of the Dispatch console Page visualizing dependencies relevant to the selected task.