A Heavy Equipment Dealer Consolidated Global Truck Telemetry Onto Files.com Without Reconfiguring a Truck

A global heavy equipment dealer sells, rents and services the machines that mining and construction run on, across three regions on three continents. The machines are the visible half of the business. The other half is data: condition monitoring is a service line in its own right.

That service depends on telemetry. Connected trucks and machines report fuel consumption, failure codes and warning codes from sites on three continents, and the dealer's customers use that data to decide when to service a machine before it fails in the pit. Every one of those machines has to upload its data somewhere. For years, "somewhere" depended on which continent the truck was standing on.

Three Regions, Three Places for the Same Data to Land

Telemetry from the same global fleet arrived by three separate routes. Trucks in one overseas region uploaded to an on-premise FTP server run locally in that region. Trucks in a second overseas region uploaded to another. Trucks in the home market reported in through a pathway of their own. One business-critical data flow, three ingestion estates: separate servers to run and patch in each region, and three different places to watch.

The dealer wanted one destination for the whole fleet, with arrival monitoring on every feed. Monitoring matters more here than in most file workflows, for two reasons. Downstream, the dealer's pipeline collects each upload minutes after it arrives, so the business is built around fresh data. Upstream, the trucks hold only so much: a device that cannot upload keeps recording until its onboard storage fills, then starts overwriting the oldest data. The requirement was an alert within hours of a feed going quiet.

The Trucks Could Not Change, So the Destination Had To

Consolidating three ingestion estates into one sounds like a routine infrastructure project until you look at what feeds them.

The telemetry units on the trucks are fixed-function devices, and changing where one uploads means a technician physically touching that machine. With hundreds of trucks in each region configured against fixed addresses, there was no fleet-wide reprogramming to reach for. Any replacement for the regional servers had to meet the fleet where it is: accept the FTP and SFTP the devices already speak, from fixed IP addresses, and be reachable by redirecting the existing regional endpoints at the network layer, so the trucks keep connecting exactly as they always have.

It also had to be defensible. An endpoint reachable from the field needed fencing: access limited to the countries where the trucks actually operate, and source addresses whitelisted, with repeated bad passwords locked out automatically. And it needed monitoring that notices when expected data does not arrive.

The dealer selected Files.com to be that single ingestion plane.

One Files.com Site Behind the Addresses the Trucks Already Dial

The dealer stood up a dedicated Files.com site for its telemetry traffic.

Between September and November 2024, the dealer redirected the traffic. The dealer's firewall and telecom providers redirected traffic for the two overseas regions' existing addresses into the Files.com telemetry site, one region at a time, joining the home market's trucks already reporting into Files.com. From a truck's point of view, nothing happened: it dials the same address over the same protocol, and the upload lands on Files.com instead of a server run in a regional office. Minutes later, the dealer's pipeline collects the file and runs it through the processing layers that turn raw sensor data into the condition monitoring its customers see.

Then the dealer added arrival monitoring. Using Files.com Expectations with Event Channels on the two overseas inbound paths, the team defined what a healthy feed looks like: which files should arrive, where, and by when. When a feed goes quiet, Files.com raises the alarm within a configured window measured in hours. The alert goes out on its own.

One Ingestion Plane for the Whole Fleet

With the redirects complete at the end of November 2024, the dealer had replaced three regional ingestion pathways with a single flow into Files.com.

• Telemetry from connected machines across three regions lands on one platform.
• The on-premise FTP servers in both overseas regions are retired. Nobody hosts, patches or watches a regional telemetry server anymore.
• A feed that stops arriving raises an alert within hours through Expectations, well inside the window before a truck's onboard storage begins to overwrite.
• Ingestion no longer scales by geography. The pattern is one destination for the whole fleet, so growth in any region lands on the same plane instead of justifying another server.

The Fleet Never Noticed

Today a haul truck at a remote mine site uploads its telemetry the way it always has: the same protocol, to a fixed address. Everything behind that address is different. The regional servers are gone, and the first sign of a missing feed is an alert measured in hours.

That is the part of the dealer's story worth carrying away. The company did not modernize thousands of fixed-function devices in order to modernize its ingestion. It left the fleet exactly as it was and moved the destination instead. Files.com speaks the trucks' old protocol on one side and carries the geo-blocking, the whitelisting and the delivery monitoring on the other, which is what let a global telemetry consolidation happen without a single truck being touched.