SolverForge
Search docs Ctrl K

Field service routing

48 Bergamo service visits. 6 technicians. Skills, parts, shifts, and road-network routes.

Field service routing keeps technician-owned ordered routes together with skills, parts, time windows, shift capacity, territory preference, and route geometry.

48 Service visits
6 Technicians
26 Locations
10 Constraints
6 / 4 Hard / soft split
Retained Route geometry

This is not just dispatch. A valid plan has to decide which technician owns each visit, then order those visits against service duration, travel, time windows, skills, parts, shift capacity, and territory fit.

The current proof keeps map routes, technician route cards, a route timeline, data tables, score analysis, retained snapshots, route-geometry endpoints, and REST workflow on one inspectable surface.

Assignment coverage Every service visit must appear in exactly one technician route.
Reachability Invalid visit indexes and unreachable travel legs are hard route issues.
Skills and parts Technician skills and inventory must cover visit requirements.
Time and capacity Time windows and shift capacity constrain the service day.
Territory affinity Routes prefer territory fit without hiding legality.
Soft tradeoffs Travel time, workload balance, priority slack, and territory affinity remain visible.
Runtime walkthrough Watch technician routes form across Bergamo, then read skills, parts, shifts, and route geometry from the same solve. Narrated walkthrough (2:37): assignment, road-network routes, skills and parts pressure, score analysis, and the snapshot-bound route geometry of one retained FSR solve.
Route Map The map keeps technician route ownership, assigned visits, retained route geometry, and solver state visible together.
  1. The status and summary row expose assigned visits, hard issues, and current score without leaving the map.
  2. Colored route geometry comes from the retained route snapshot, not a separate drawing layer.
Route Focus Route focus lets an operator isolate one technician route while preserving the surrounding fleet context.
  1. Route cards expose technician, travel, service time, territory, and stop count.
  2. Focused route markers and path geometry make the selected technician's ordered work inspectable.
Route Timeline The route timeline shows the same plan as ordered technician lanes across the 08:00-18:00 service day.
  1. Each technician lane carries stops, travel, service time, and feasibility badges.
  2. Visit blocks show the ordered route against the service-day clock.
Score Analysis Score analysis makes all 10 constraints inspectable with weights, scores, and match counts.
  1. Hard route legality and soft routing tradeoffs are separated in the analysis modal.
  2. Match counts show where assignment, travel, priority, and territory pressure comes from.
Data View Data views keep routes, visits, locations, skills, parts, windows, and territory facts adjacent to the plan.
  1. Technician-route rows expose shifts, skills, inventory, territory, and assigned visit order.
  2. Service visits keep duration, windows, priority, skill masks, parts, and territory visible.
REST API REST endpoints expose demo data, retained jobs, snapshots, route geometry, SSE events, and analysis for integration.
  1. Retained-job endpoints expose creation, events, snapshots, and analysis.
  2. Route geometry is available through a snapshot-scoped endpoint for product integration.