Overnight Stay Behavior and Limitations
• The return drive time (time required to travel from the ONS location back to the technician’s home location) is added to the ONS event if the overnight stay event is the last element in the route and there are no other elements scheduled for the next day.
• Long overnight stay events, such as ONS events created for two or more days, may occur. This can happen when an ONS is proposed by the Scheduling Optimization and the next day(s) are non-working days or inactive routes. In the following example, the ONS was created on Saturday, April 27th, and ended on Monday, April 29th.
• The overnight stay considers the Drive on own time before configured in the dispatch process. For example, if:
◦ The technician's working hours set to 9:00 AM to 6:00 PM
◦ The drive on own time before is defined as 15 minutes in the Dispatch process
then an ONS event is created till 8:45 AM if the work order scheduled after ONS uses the entire drive before time. If the work order after ONS is utilizing only 10 mins of the drive before time, then ONS event is created till 8:50 AM.
• The Scheduling optimization may propose Overnight stay events that start beyond regular working hours. For example, if a technician's working hours are from 9:00 AM to 6:00 PM and the overtime tolerance is set to 30 minutes in the Dispatch process, if the last work order ends at 6:15 PM, exceeding regular hours, then an overnight stay event is created from 6:15 PM onwards.
• The scheduling optimization can propose overnight stays for work orders that are part of a dependency group based on resource availability, dependency group configuration, and other defined constraints.
 | Dependency management is a soft constraint and hence, the optimization engine can unassign the dependency work orders. |
• The ONS is not supported in LTP.
• The ONS are supported for multi-day work orders.