FlowsBook a callSign inCreate free accountSign up
Workflows by industry

How mining firms plan supply routes to remote sites

Fuel stops, towns with a clinic, road closures and rain on the haul road: how logistics teams at mines read the corridor to a remote site, and keep reading it every day.

Part of the guide Workflow automation

By the xMap team · · 6 min read

A mining firm plans a supply route to a remote site by treating the road as a chain of stops, not a line on a map. The logistics team lists every town, fuel point, workshop, place to sleep and clinic along the corridor, checks how far apart they are, and then watches the same road every morning for closures, roadworks and heavy rain. The route that wins is rarely the shortest one; it is the one where a broken-down truck, a sick driver or a washed-out section can be handled within a few hours.

This article is for supply chain, logistics and site services teams at mines, quarries and oil and gas operations, and for the contractors who haul for them. It walks through how to map a corridor, what to look for between the town and the gate, a made-up worked example, the common mistakes, and an AI employee that sends a short road note before the first convoy leaves.

Why remote routes are planned differently

In a city, a lorry that breaks down is a nuisance. On a 400 km haul road it can stop production. The questions change accordingly. How long can a convoy run before it needs fuel? Where can a driver rest legally? Where is the nearest hospital or airstrip if someone is hurt? Which towns can supply tyres, hoses or a welder at short notice? And which stretches flood, close for maintenance or carry heavy traffic on certain days?

None of this is answered by a single drive time. It is answered by an inventory of what sits along the road, and by a habit of checking the road before trucks commit to it.

What to map along the corridor

  • Fuel and truck stops. The gaps between them set the longest leg a convoy can run without carrying extra fuel.
  • Towns and their services. Workshops, tyre shops, hardware and industrial suppliers, hotels and campgrounds for contractors, food and supermarkets.
  • Medical cover. Hospitals, clinics and pharmacies, and the distance from each stretch of road to the nearest one. This feeds the site's emergency plan.
  • Road events. Closures, roadworks and incidents reported on online maps, read every morning for the corridor.
  • Weather. Rain totals and wind for each town and the site, because unsealed sections and river crossings change with the forecast.

In xMap Flows the corridor is set with the Area of interest block: draw the corridor as a few shapes, or drop points on each town and give them a radius. Nearby places then lists the kinds of place you pick inside those areas from xMap's places database, and Traffic incidents reads closures and roadworks in the same areas.

A worked example

Here is a made-up corridor to show the method. Say a copper project sits inland from Antofagasta in northern Chile, about five hours by road, with Calama as the main town on the way. The logistics lead draws three shapes: the port and its outskirts, a band along the highway, and a circle around Calama, then a small circle around the camp gate.

  1. Nearby places is set to fuel stations, truck stops, tyre shops, hardware stores, hotels, hospitals and clinics, and run once on all four areas.
  2. The list comes back grouped by area. In this invented case it shows plenty of everything in the port and in Calama, two fuel points on the highway band, and nothing at all within 30 km of the gate.
  3. The team sorts the highway stops by distance from the port and works out the longest gap. That gap, not the total distance, sets the fuel rule for the convoy.
  4. Hospitals and clinics are copied into the emergency plan with their distance from the gate.
  5. Tyre shops and workshops in Calama become the first calls when a supplier is needed in a hurry.

Nothing in that example is a measured figure; it shows the shape of the work. On a real corridor the numbers will be your own, and they should be checked by someone who has driven the road.

Watching the road every day

The inventory changes slowly. The road changes daily. Two checks catch most of what upsets a convoy: closures and roadworks on the corridor, and rain at the towns and the site. Weather forecast gives rain, wind and temperature for each place for up to 16 days, so a crossing that floods after heavy rain can be flagged a day or two ahead. Traffic incidents gives the closures that are reported right now, each with where it is.

Mistakes to avoid

  • Planning by the shortest route. A shorter road with no fuel or clinic for 200 km is a riskier road.
  • Trusting an empty map. No incident reported is not the same as an open road, especially on tracks few people drive.
  • Counting towns, not services. A town with no workshop does not help a truck with a split hose. List the services, not just the names.
  • Checking once. A corridor review done at the start of a project ages fast. New camps, closed stations and seasonal flooding all change it.
  • Leaving drivers out. The people on the road know which stop has diesel at night. Feed their corrections back into your list.

Doing it with an AI employee

Two AI employees cover the job: one that keeps the corridor inventory fresh, and one that writes the morning road note.

  1. Corridor inventory, monthly. Schedule on the first Monday, then Area of interest with your corridor shapes, then Nearby places with the kinds of place above, then What changed so only stops that closed or changed come through, then Email to the logistics lead and Show on a map.
  2. Morning road note, daily. Schedule at 05:00 local time, Area of interest with the same shapes, Traffic incidents, Weather forecast for the towns and the site, then an xMap LLM block told to write three lines for drivers, then Email or a WhatsApp message to the convoy leads.
  3. Deploy both. The first lands in the inbox once a month with any stop that changed; the second lands every morning with what is closed and where rain is expected.

The templates Truck stops and fuel along the haul corridor, Road closures on the convoy route each morning and Heavy rain at the mine: haul road safety are ready-made versions you can hire and adjust to your own corridor. For the medical side, Nearest hospitals and airports to each site builds the list the emergency plan needs.

Questions

Can xMap Flows plan the exact route a truck should take?

Route planner orders a set of stops into the best visiting order, but it is built for a day of visits, not for routing heavy vehicles. For a haul corridor, map the stops and watch the road; the route itself stays your team's decision.

Does it show road conditions on unsealed tracks?

Only what is reported on online maps. Remote tracks are often missing, so drivers' reports remain the main source there.

How far ahead can the rain check look?

The Weather forecast block looks up to 16 days ahead. Most teams use the next two or three days for convoy decisions, when forecasts are closest to what happens.

Can the morning note go to drivers on their phones?

Yes. The note can go by email, or through a messaging app you connect, such as WhatsApp Business or Slack, so it arrives where drivers already look.

Templates that do this

Read next

More on workflows by industry · Every article · Templates

Put it to work

An AI employee in xMap Flows does this on live data, on its own timetable. Start from a template or describe it in plain words.