You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is currently possible to create events with zero duration, or events that overlap. While this in itself isn't a problem, the start and end times are critical when allocating vehicles to an event. It should not be possible to allocate a vehicle to an event or duty such that it has to get from one to the next in less time than would be available. If it's at an event in Corby until 5.30pm, it can possibly be allocated to a duty rider in Reading to start at 6pm for instance.
We discussed some sort of fixed time periods along the lines of am, pm or evening where these reflect the current split of controller times of 8-1, 1-7, 7-8. The start/end data could still be stored as datetime values, albeit with fixed times, in the back end, but would be shown to the user as simply as starting/ending AM, PM or Evening This means an event could span any one or several periods but that would set the start and end and thus align with duty allocations.
The text was updated successfully, but these errors were encountered:
It is currently possible to create events with zero duration, or events that overlap. While this in itself isn't a problem, the start and end times are critical when allocating vehicles to an event. It should not be possible to allocate a vehicle to an event or duty such that it has to get from one to the next in less time than would be available. If it's at an event in Corby until 5.30pm, it can possibly be allocated to a duty rider in Reading to start at 6pm for instance.
We discussed some sort of fixed time periods along the lines of am, pm or evening where these reflect the current split of controller times of 8-1, 1-7, 7-8. The start/end data could still be stored as datetime values, albeit with fixed times, in the back end, but would be shown to the user as simply as starting/ending AM, PM or Evening This means an event could span any one or several periods but that would set the start and end and thus align with duty allocations.
The text was updated successfully, but these errors were encountered: