Finning Retired Two Regional FTP Servers and Closed a Near-20-Hour Telemetry Blind Spot With Files.com—Without Reconfiguring a Truck

Finning International is the world's largest Caterpillar dealer. Its 13,000 employees sell, rent and service the heavy equipment that mining and construction run on, across Western Canada, South America, and the UK and Ireland. The machines are the visible half of the business. The other half is data: condition monitoring is a Finning service line in its own right, and the company helped bring one of the world's largest autonomous haul-truck fleets into operation in the oil sands.

That service depends on telemetry. More than 1,900 connected trucks and machines report fuel consumption, failure codes and warning codes from sites on three continents, and Finning'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. South American trucks uploaded to an on-premise FTP server run locally in the region. UK trucks uploaded to another. Canadian trucks 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 where the same failure could hide.

The hiding was the real cost. Monitoring was a manual check, done roughly once a day, and under it a missed delivery once went nearly 20 hours before anyone noticed. That gap matters more here than in most file workflows, for two reasons. Downstream, Finning's pipeline collects each upload about 15 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. A feed that goes quiet and stays unnoticed is not late telemetry. It is telemetry lost for good.

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 trucks don't speak anything but plain old FTP, and they don't speak hostnames. They speak IPs. Old stuff.”

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 plain FTP and SFTP from devices that dial 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 that accepts an unencrypted protocol 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 the thing the old estate never had, which is monitoring that notices when expected data does not arrive.

Finning selected Files.com to be that single ingestion plane.

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

Finning stood up a dedicated Files.com site for its VIMS telemetry traffic.

Between September and November 2024, Finning redirected the traffic. Finning's firewall and telecom providers redirected traffic for the existing South American and UK addresses into the Files.com VIMS site—South America first, then the UK—joining the Canadian 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. About 15 minutes later, Finning'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 Finning closed the monitoring gap. Using Files.com Expectations with Event Channels on the South American and UK 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. Nobody has to remember to check.

One Ingestion Plane, and a Blind Spot Closed

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

• Telemetry from more than 1,900 connected machines across three regions lands on one platform, part of a Files.com workload that runs to roughly 3.5 million sessions a month.
• The on-premise FTP servers in South America and the UK are retired. Nobody hosts, patches or watches a regional telemetry server anymore.
• A feed that stops arriving raises an alert within hours through Expectations, instead of surfacing at the next day's manual check. The near-20-hour blind spot is closed, and with it the risk of a truck quietly overwriting data nobody knew was missing.
• 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 mine site in Chile uploads its telemetry the way it always has: plain FTP, to a fixed address. Everything behind that address is different. The regional servers are gone, the daily manual check is gone, and the first sign of a missing feed is an alert measured in hours rather than a discovery measured most of a day later.

That is the part of Finning'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.