Managing Tyres Across Multiple Mine Sites

Managing tyres at one mine site is hard enough. Managing them across several sites, often hundreds or thousands of kilometres apart, adds a different kind of problem. Each site builds its own habits, its own spreadsheets and its own way of describing the same thing. By the time head office asks a simple question, such as which site gets the best life from a given tyre, nobody can answer it with confidence.

This article looks at why multi-site tyre management breaks down and what a well-run multi-site tyre programme looks like.

Why multi-site tyre data falls apart

Most multi-site operations did not plan their tyre data. It grew site by site, and the result usually looks like this:

• Different definitions. One site counts tyre life in hours from the hour meter, another estimates it from fitment dates. One records a removal as "worn out", another as "scrap", another as "end of life".
• Different tools. Paper sheets at one site, a local spreadsheet at another, a tyre supplier's portal at a third.
• Different position naming. Position 1 on a haul truck at one site is the front left. At another it is the front right.
• Local knowledge. A handful of experienced tyre fitters know the history of each tyre. When they move on, that history goes with them.

Every one of these differences makes cross-site comparison unreliable. You end up comparing numbers that look similar but measure different things.

The cost of not being able to compare

The biggest gains in a tyre programme often come from learning across sites. If one site consistently gets more hours from the same tyre on similar trucks, there is something worth understanding: pressure discipline, haul road maintenance, inspection frequency, rotation practice or loading.

Without comparable data, those lessons stay local. Head office cannot tell whether a difference is real or just a quirk of how each site records data. Decisions on tyre brands, supplier contracts and spares holding end up being made on anecdote.

There is also a time cost. When reports depend on someone at each site pulling numbers together by hand, monthly reporting takes days, and the answers are already out of date when they arrive.

Step 1: Agree a common data standard

Before any system can help, the sites need to describe tyres the same way. A practical data standard covers:

• Tyre identity. How each tyre is identified, for example by serial number, and how that is recorded at receipt.
• Position naming. A single convention for wheel positions on each vehicle model.
• Hours and distance. Where operating hours come from and how they are attributed to each tyre.
• Removal reasons. A short, fixed list of reason codes used at every site.
• Pressure targets. Target cold pressures by tyre specification and position, agreed with your tyre supplier.
• Costs. What goes into the cost of a tyre, including purchase, repairs and retreads.

Keep the standard short and practical. Fitters need to be able to follow it during a busy shift, not just in a training room.

Step 2: Put every site in one system

A shared standard only holds if every site records data in the same place. A single tyre management system for all sites means:

• Everyone uses the same lists of positions, removal reasons and tyre specifications
• Data from every site is available to head office as soon as it is recorded
• Reports compare like with like, because the definitions are built into the system

The system also has to suit each site's reality. Remote pits need a mobile app that works offline and syncs when connectivity returns, otherwise one site's data will always lag behind the others.

Step 3: Track transfers properly

Tyres and vehicles move between sites more often than many reports suggest. A tyre may be fitted at one site, removed, sent to a central workshop for repair, then fitted to a truck at another site.

If each move is recorded as a new tyre, its history is lost. Cost per hour is understated at one site and overstated at another, and premature failures cannot be traced back to their cause.

A good multi-site process records every transfer against the tyre itself, so its full history follows it from site to site. The same applies to vehicles moved between operations.

Step 4: Benchmark carefully

Once data is consistent, you can compare sites. But a fair comparison takes some care. Mine sites differ in ways that affect tyre life no matter how well tyres are managed:

• Haul road length, grade and surface
• Payload and cycle times
• Climate, especially heat on long hauls
• Material, from soft overburden to sharp, abrasive rock

Compare like with like. Benchmark the same tyre size on the same truck model, and look at trends within each site as well as the absolute numbers between them. A site that improves its cost per hour steadily over a year may be doing more right than a site with an easier haul road and a lower starting figure.

Step 5: Give each level the view it needs

Multi-site operations have very different users:

• Field operators need fast, simple screens for inspections and tyre changes at their own site.
• Site superintendents need their site's KPIs, open issues and upcoming work.
• Corporate or fleet managers need the cross-site picture, trends and benchmarks.

Role-based access keeps each group focused on what matters to them and stops sensitive cost data from being visible to everyone. It also makes it clear who is responsible for the data at each site.

Step 6: Set up a simple governance rhythm

Tools and standards drift over time without someone looking after them. A light governance structure keeps things on track:

• A central tyre lead owns the data standard and the cross-site reporting.
• Each site has a tyre champion, often a senior fitter or tyre engineer, who keeps local practice aligned.
• A regular cross-site review, monthly or quarterly, looks at the same small set of KPIs for every site and agrees actions.

The review is where the real value appears. It is the moment one site's improvement becomes every site's practice.

Conclusion

Multi-site tyre management is less about software and more about consistency: the same definitions, the same processes and the same data in one place. Once that is in place, cross-site benchmarking turns tyres from a cost that is simply reported into one that is actively managed.

TyreMetric was built for multi-site operations. Every site sits in one platform with shared tyre specifications and reason codes, transfers keep each tyre's history intact, site benchmark reports compare performance across your operation, and role-based access gives fitters, superintendents and managers the view they need. To see how it would work across your sites, request a demo.