Management should be able to queue paths in
Why: The scheduling will allow upfront planning and minimal user intervention. Therefor we reduce mistakes and enhance the level of automation.
The basic:
The webapp should allow creation and rearrangement of the paths execution scheduled (maybe by drag and drop).
Path should be in 99% of the cases not tied to a specific robot. When a robot become available, he will request a path which is the first one in the timetable.
Extra goals:
Show required time to execute the path and cumulated time expected to complete path
Save a choosen timetable into what a "scenario", this scenario can be loaded (automatically or manually) when the timetable is cleared
Different users have different capabilities, for example operator might request an execution. This is to deal with push or pull management and emergencies.
This feature might require some other feature to be developed concurrently:
Ability to reach the starting point of the next path
Arrowana
commented
8 years ago
Management should be able to queue paths in Why: The scheduling will allow upfront planning and minimal user intervention. Therefor we reduce mistakes and enhance the level of automation.
The basic:
Extra goals:
This feature might require some other feature to be developed concurrently: