Feature Requests

When visits have dependencies, the default behavior is to leave the preceding visit unassigned if assigning it would prevent the dependent visit from also being assigned. In some scenarios, it is preferable to assign the preceding visit anyway, even if the follow-up cannot be scheduled. It should be possible to configure this behavior, both per individual dependency and as a dataset-wide default.

Many of our clients manage visits that span multiple days, where the duration of a single job exceeds one day. Currently, this scenario cannot be properly handled within their Timefold integration. One possible workaround would be to split a multi-day visit into separate shifts for each day. However, this approach creates practical challenges.

Currently, the input needs to specify which technicians can travel during the planning period (by including multi days shifts with hotel breaks). However, is some cases travelling is not strictly necessary and all itineraries could be performed with technicians leaving from and returning to their home location. This might produce confusing outputs and/or suboptimal schedules. See https://app.timefold.ai/e185e9c6-19a8-4f90-afcc-56bce43ff6a5/models/field-service-routing/v1/runs/288d5b97-9e69-4e88-8969-1ea6dc42c110 Visit 6517503 is only performed on Friday with an assumed waiting time of 4days.

When defining a dependency: splitting a multi-day task into separate visits, it could be useful to define that the second part needs to be finished on the next working day. This will allow the first part to be scheduled on a Friday.