Reading the jam factor to choose delivery slots at your sites
The jam factor rates roads from 0 to 10. Read every half hour outside your shops or kitchens for a few weeks, it shows when suppliers should be booked in.
Part of the guide Location intelligence automation
To choose delivery slots with the jam factor, record it on the roads next to each of your sites every half hour across the morning for two or three weeks, then average it by site, weekday and time. Book suppliers into the half hours where it stays low, keep the high ones for walk-in trade, and give each site its own timetable instead of one rule for the whole chain. The jam factor is a single number per road from 0 for free-flowing to 10 for standstill, which makes it easy to compare times and places.
This is for operations managers at restaurant groups, convenience chains and clinics who receive goods at many addresses, and for the suppliers who book drop slots with them. It explains the scale, how to collect readings that mean something, a made-up timetable, and an AI employee that keeps the timetable current.
What the jam factor tells you, and what it does not
Traffic Flow measures the roads around each place at the moment a flow runs. For each place it gives the current speed and the free-flow speed in km/h, the congestion as a percentage, a jam factor from 0 to 10, a level in words (free flowing, light, moderate, heavy or standstill), how many road stretches were measured, how many are closed, and the busiest road.
- Below about 2: traffic moves close to free flow. A lorry can stop and unload without blocking anyone for long.
- Around 4 to 6: slow, stop-start roads. Arrival times slip and double parking causes queues.
- 8 and above: close to standstill, or a closed road counted at the top of the scale.
Those bands are a practical reading, not an official rule; set your own after a few weeks of data. The jam factor does not count vehicles, has no history of its own and gives no peak hours. It describes now. To learn your sites' pattern, you take the reading yourself at the times you care about and keep it.
Collecting readings that mean something
- List your sites with their positions in a table in My data.
- Measure the adjacent roads only. A wider circle mixes in a motorway the lorry never uses.
- Take a reading every 30 minutes across the window in which suppliers could come, for example 05:30 to 11:30.
- Keep every reading, with the site, the date and the time. Save to my database writes each run into a table of your own, or send it to a Google Sheets sheet.
- Collect for at least two full weeks, ideally three, so each weekday has several mornings.
A made-up timetable
Say a made-up restaurant group in Istanbul runs eight kitchens and takes bread, produce and drinks deliveries every weekday. After three weeks of readings, the average jam factor on the road outside three of its kitchens looks like this. The figures are invented.
| Kitchen | 06:00 | 07:30 | 09:00 | 10:30 | Slot chosen |
|---|---|---|---|---|---|
| Waterfront | 1.2 | 6.8 | 7.4 | 3.1 | Before 06:30, or after 10:30 |
| Old town | 0.9 | 2.4 | 5.9 | 6.6 | 06:00 to 08:00 |
| Business district | 1.5 | 7.9 | 4.2 | 2.0 | After 10:00 |
A made-up example for an imaginary restaurant group. Average jam factor on the adjacent road, weekdays.
One rule for all eight kitchens, such as 'deliveries between 7 and 9', would have put the waterfront and business district drops into their worst hour. Each kitchen gets its own window, the supplier gets one booking sheet, and the drivers stop circling.
Mistakes to avoid
- Deciding from one morning. A single reading catches a crash or a festival. Average several of the same weekday.
- Averaging Fridays with Mondays. Keep weekdays apart until you know they behave alike.
- Ignoring roads_closed. A closed stretch pushes the jam factor up and may mean the van cannot reach the door at all.
- Forgetting school terms and holidays. Mornings change with the school run. Record again when term starts.
- Reading speed alone. A road with a low free-flow speed can be fine at 20 km/h. The jam factor and the congestion percentage compare against each road's own normal.
How to do it with an AI employee
Two AI employees in xMap Flows handle this: one collects, one explains.
- The collector: a Schedule every 30 minutes from 05:30 to 11:30 on weekdays reads your sites from My data.
- Traffic Flow measures the adjacent roads around each site.
- Save to my database adds the readings to your table.
- The analyst: every Monday, Database query reads the last three weeks of readings.
- Data analyst works out the average jam factor by site, weekday and half hour and picks each site's two lowest windows.
- An Email sends the timetable to operations and the suppliers' booking contact.
Every Monday the operations manager receives a table of each site's best delivery windows for each weekday, with the average jam factor beside them, and a line when a site's best window has moved, for example because roadworks started on its street.
Questions
Does the jam factor count cars?
No. It rates how jammed the roads are from 0 to 10 at the moment of the reading. It never counts vehicles.
Is there a history of past jam factors?
Not in Traffic Flow itself. Run it on a timetable and save each reading to build your own history.
How many weeks of readings do I need?
Two to three weeks, so each weekday has several mornings to average. Take new readings when school terms or roadworks change.
What jam factor is acceptable for a delivery?
Set your own line after looking at the data. Many teams treat readings under about 2 as easy and above 6 as slots to avoid.