Feature Requests

We occasionally encounter FSR planning requests that fail with the following error: “Location (latitude=53.480602, longitude=12.831824) not found in map (possibly due to an incorrect map, transport type, or a max distance-from-road parameter that is too restrictive).” In a production environment, it would be highly preferable to skip visits whose coordinates are too far from a mapped road, rather than aborting the entire planning request.

This is a request to make it possible to export the output of a model run to spreadsheet format ( .csv or Excel), to be able to share the output with the rest of the business to validate & spot-check the plan. Today only an option to download the .json is available.

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.

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.

Some jobs require (limited) equipment or tools to be used while executing a task. Some task also require spare parts to be taken along. Given that the number of tools is finite, this introduces an additional constraint to the optimisation process, ensuring that tool availability is factored into production schedules. Potentially that equipment needs to be cleaned or charged in between use.

This is a request to prefer routes of vehicles to start far away and then move closer to home, as technicians like leaving early to avoid traffic, but don't like being stuck in traffic at end of a shift.

This is a request to be able to account for depot stock levels of non-renewable materials when optimizing field service routes. In some scenarios, visits require specific consumable materials or parts (for example, wood from a depot). The model should consider the availability of these non-renewable resources when assigning visits to technicians and depots, ensuring that planned visits are feasible given current stock levels. This would help prevent infeasible plans and improve coordination between inventory management and route optimization.

This request is to allow configuring traffic impact on various dimensions (time, region etc) to adjust expected travel time for known traffic impact.

Right now we can view the input and output for plans, however when we use the recommendation api we cannot view those details. It would also be great if those can also be viewed in that UI for troubleshooting purposed.

We send a week of unpinned shifts but for WorkingHours Act we need to send 52 weeks in the past and future of pinned shifts. So most shifts that are returned are pinned. We have to filter them. This makes the answer from Timefold much bigger than we need. It would be great if we can tell to Timefold to only send the unpinned shifts back.