Many work orders, few crews: who goes where, in what order?
Assigns work orders arriving from the call centre, citizen requests and the periodic maintenance programme to crews by zone and skill, and inserts an urgent job arriving during the day into the nearest suitable crew's plan.
Arrival order: crews cross each otherBy zone and skill; urgent job inserted
Jobs are handed out in arrival order; crews criss-cross the district.
Municipal field work starts at the call centre: a pothole, a pavement, a water leak, a blocked sewer, a broken street light. The request is routed to a unit, the unit hands it to a crew. Most municipalities keep a daily activity list and some publish it on the e-Government portal, but the list has no order and no route. The crew leaves the yard in the morning and works through the jobs in arrival order.
The result: two trips to opposite ends of the district on the same day, the asphalt crew dropping by an electrical job, and the urgent fault left to the end of the day. An Istanbul district measured the average response time for infrastructure maintenance requests at 15 days in its strategic plan, set a target of 12, and listed vehicle, machinery and material coordination among its risks.
- Average response time for infrastructure requests (an Istanbul district, 2024)
- 15 days
- Calls routed to field units in one metropolitan municipality (2024)
- 340,000
- Daily fault work orders at one metropolitan water utility (2023)
- ~280
Sources: the 2025–2029 strategic plan of an Istanbul district municipality; a metropolitan municipality's 2024 call centre statement; a metropolitan water and sewerage authority's 2023 annual report (56,714 water and 46,886 sewer faults a year). The figures show the scale of the workload.
What does the job plan take into account?
| Rule | What it means |
|---|---|
| Crew skill | Electrical jobs to the electrical crew, asphalt jobs to the asphalt crew; multi-skilled crews can take both. |
| Job duration and time window | Each job's estimated duration and the hours it can be done (school surroundings, traffic, water cut announcements). |
| Priority | Urgent faults go ahead of planned maintenance; jobs that generate complaints when delayed are scheduled early. |
| Urgent jobs during the day | When a new job arrives the plan is regenerated in minutes; the crew's remaining jobs are kept. |
| Equipment and vehicle type | Jobs needing a crane, an excavator or a water tanker go only to a crew that has one. |
| Material resupply | Yard returns for asphalt, water refills or materials are in the plan. |
| Periodic jobs | Repeating tasks such as irrigation, pruning and spraying sit in the weekly plan at a fixed frequency. |
| Shift and zone | The plan stays within the shift; crew zones are kept or redrawn for load balance. |
The rules are compiled from the technician routing and scheduling literature and from studies on Turkish field data.
How we work
Export your work orders
A list exported from your call centre or work order software is enough; your existing system does not change.
Crew and skill list
Crews, their skills, vehicles and equipment, shift hours and yard location are defined.
Daily job plan
Job order and route for each crew; the crew sees the next job on a phone and marks it done. The end-of-day report goes back to the work order system.
Getting started
Akılkent's route solver was validated with real data in municipal solid waste operations; the same core runs with this sector's rules. The constraints above are defined for your operation in the first conversation and computed with your own data in the free pre-analysis. We review the results together and, if it fits, start with a trial in one area.
See it with your own data
With your vehicle list and point locations we compute the savings potential of your operation and review the result together. A request is not a purchase commitment.
Request a free pre-analysis