Feature Requests

When planning multiday itineraries (e.g. a technician traveling to a distant location for several days), the current workaround is to model a single long shift with hotel breaks. This leads to wrong cost calculations. We'd like a way to link individual daily shifts together, so that costs are calculated per working day rather than across the full multiday span. This would produce accurate cost reporting and prevent the optimizer from generating solutions where visits are clustered on a single day while costs are counted for the entire week.

When visits have different due times set via latestSlaEndTime, it would be useful if the scheduler automatically prioritized visits with tighter deadlines earlier in the planning period — reducing the risk of SLA breaches. Currently, visits with close due times may not be scheduled early enough, leading to unnecessary violations that could have been avoided with deadline-aware ordering.

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.