Locus Robotics Ideas Portal
Could we somehow apply a 'Shift' label at the user/user-tag level (either shift, or shiftdate&shift) and then pass this label to Task/TaskHistory at the completion of the task (along with ExecUser).
This would help solve the problem of exact start/end times, and if a unique identifier was applied based on date (date at start of shift?) then it would also solve shifts overlapping date changes.
One difficulty is managing/recording these shifts, applying them to users for each day/shift.
|
Problem/opportunity trying to be solved
Several clients have asked for a way report out by shift, either in Portal reports or LocusView. |
|
|
Quantify the problem/opportunity
Frequent request, does not impact performance or business case, more of a nice-to-have. |
|
|
What is the root cause of the problem/opportunity
Requires a high degree of configurability/flexibility. Shifts are different at every site, can start earlier than expected, can end later than expected, can overlap a date change, etc... |
|
| Customer need date | Dec 31, 2022 |
| Urgent request | No |
