by ivan.gordeyev Mon Dec 09, 2019 6:14 pm
This is a great question. Many vendors already solved that 'queue/work management' within their software.
jking, I am sorry to disagree.
You might be thinking of schedules, where one schedule has a 'running' status when started.
The robots can be started multiple times and they can manage the work e.g. one gets item 1, one gets item 2, then first gets item 3 etc this can be achieved by many options [file management, allocation management, specific rules, inputs etc]. We are now at a space where we can achieve scalability in the time of excess workload, which means the only limit is our license and infrastructure capacity.
There is however a benefit in 'breaking up' the process into separate robots, but sometimes this creates duplication, dependencies and inefficiencies, plus design of the hand-over point, re-work avoidance,
Ad-hoc reporting and other type of additional logic required. However, Jking is right, this still sometimes one of the best things you can do.
Good news is: that Kofax have taken steps to help us
https://smarthub.kofax.com/details/queue-manager/Have a look at the above URL.
This means not only queue management can be done, but also, reporting can be standardised, unfortunately at a cost to capacity and some additional infrastructure requirements.