In the initial phase, tasks are being created by the dispatchers (alternatively, external systems can be linked to pull task data). Then, the logic for determining the staff certification required for each job is determined from both the description and the path of the task.
The computing of optimum allocations is done via pre-defined rules
The service not only fidns the best allocation, it finds all possible allocations and ranks them based on cost and time optimization factors.
Allocation to tasks done globally, not for each individualy
In order to find the best result, our system encourages all tasks to be defined before the allocation process begins. Through this practice, the application can find a global optimum solution for the incoming tasks, and not just "locally" optimum allocations as it would if tasks would be considered on a one by one basis.
Dispatchers are first presented with the most optimum allocation. At this point, they are expected to confirm with the proposed employees their availability for the task they have been paired with.
Next allocation will only be shown if employee confirmed unavailable
Dispatchers will only be allowed to move to the next best allocation when they have confirmed with one of the involved employees that they are unavailable. They are expected to confirm the name of the employee, as well as the time of contact.
Allocation confirmed and calendar updates
When a proposed allocation is confirmed with all involved personnel, the dispatcher will note all confirmation timestamps and hit Confirm. The system will then update the calendar of all employees with the expected commute and the expected task duration. At this point, these employees will not be available for other allocations that start before the end of the current assignment.
The application will follow the updates of a transportations and take timely decissions of emergency staff changes if their task is running late and they are expected to hit their legal work time limits.
The system automatically sends personnel to rest when required
At the end of each task, all involved personnel is automatically sent to rest if they are close to hit their work time limit. Whether this involves commuting home to rest or sleep at company's barrack, the service will always compute the optimum resting place considering incoming tasks.
Communication between system and operating personnel
Depending on already existing architecture, the decissions that are made by the system can be either communicated to the operating personnel either via the dispatchers, or via existing automated communication systems. The Cargoquant product offers possiblity of integration with such external services to create a fully autonomous allocation flow.