Files.com BYOIP Makes Finning CAT’s 1,900-Truck Hardcoded-IP Migration Routine Maintenance

Finning International has sold, rented and serviced Caterpillar equipment since 1933 and is the world's largest Caterpillar dealer: a $10.6 billion business with more than 13,000 employees serving mining and construction operators across Western Canada, South America, and the UK and Ireland. Its work sits at the hard end of the industry. Finning supplied and supported the 363-tonne haul trucks behind one of the world's largest autonomous mining fleets in the Canadian oil sands.

Increasingly, that dealership runs on data as much as on parts. Every CAT machine carries VIMS, an onboard system that records fuel consumption, failure codes and warning codes and uploads them over the network. Finning ingests that telemetry, processes it, and turns it into the maintenance and repair decisions its customers rely on to keep mines running. The whole service depends on roughly 1,900 connected trucks, working in remote pits on three continents, being able to phone home.

And the systems doing the phoning are old.

Instead of making the trucks able to follow a moving address, make the address stop moving.

The Fleet Was Programmed With Addresses Finning Didn't Own

“The trucks don't speak anything but plain old FTP, and they don't speak hostnames. They speak IPs. Old stuff.”

Each truck is programmed with the literal numeric address it uploads to. There is no DNS in the loop, which means there is no way to change a truck's destination from a desk. Someone has to stand at the machine.

The addresses programmed into the fleet, meanwhile, belonged to other companies. Truck traffic in South America and the UK reached Finning's ingestion platform through IP ranges controlled by telecom and firewall vendors, and connections in Chile routed through a paid third-party FTP proxy. Jason McOnie of Finning's Global Core Infrastructure team put the operational dependency plainly:

“If they change their IP addresses tomorrow, we'd have to send out techs to every single truck as quickly as possible to reconfigure our trucks.”

Reprogramming a truck means a technician at the machine while it sits out of service, and downtime on these machines runs about $10,000 per hour. The machines themselves are roughly $10 million assets. A vendor rotating an IP range, a decision Finning had no vote in and no notice of, could start that clock on every truck at once, across mine sites in Canada, Chile and the UK.

Why the Address Had to Become Permanent

The usual fix does not exist here. Pointing a hostname at a new address does nothing for a device that cannot resolve hostnames, and the onboard systems cannot be taught DNS. Every address change is a hands-on visit during a service window, so a coordinated cutover across 1,900 machines on three continents was never a real option. Having consolidated its regional telemetry pathways onto a single global ingestion site, Finning now had one destination the entire fleet would eventually point at, which made the question of who controls that destination's addresses permanent.

That meant public IP addresses Finning owns outright rather than borrows, reachable from every region the fleet operates in, serving the plain FTP the trucks require, with every old address kept alive until the last machine is touched.

Finning selected Files.com to be that permanent front door. Files.com could announce and globally route a /24 block of address space Finning already owned, serve the plain FTP the trucks required, and keep the old destinations operating throughout the multiyear transition.

Finning's Own Block, Announced By Files.com

Finning's network team handled the registry side, setting up RPKI and the route origin authorizations that permitted Files.com to announce the block. Within weeks, Files.com made Finning's previously unrouted /24 globally reachable, with an address assigned to each fleet region and another held in reserve.

Behind those addresses sits the Files.com site that ingests the fleet's telemetry, accepting the unencrypted FTP the trucks require, with access restricted to the countries where the fleet actually operates. The dedicated IPs the fleet already pointed at were kept in service with no retirement date, so any truck not yet reprogrammed keeps uploading exactly as before.

The migration itself runs at fleet pace by design: region by region, one machine at a time, each truck reprogrammed during a service visit that was already scheduled, over a plan spanning three to four years. The network side took weeks. The fleet side takes as long as the fleet takes, and nothing about the architecture requires it to go faster.

A Migration at Fleet Pace, Not a Fire Drill

With Files.com announcing addresses Finning owns, Finning replaced addressing rented from vendors it could not control with addressing that is permanently its own. Everything that changed follows from that.

• Every new address programmed into a truck belongs to Finning for good. A truck touched once never needs touching again for addressing, no matter which telecom or firewall vendor changes its ranges.
• The rollout began with roughly 800 trucks in the South American operation, with reprogramming folded into routine service. At $10,000 per hour of downtime, folding the migration into maintenance that was happening anyway is the difference between a rollout and an emergency campaign.
• The paid FTP proxy in Chile is retired. Trucks there connect directly to Finning's addresses, hosted and routed by Files.com.
• Each region has its own address out of the block, so a future networking change in one region does not touch trucks in the other two.

Routine Service Work Instead of a Standing Emergency

Before this, Finning's regional fleet connections depended on vendor-controlled addresses: a decision made in a telecom office somewhere could have started a $10,000-an-hour reconfiguration scramble across three continents. Today a technician in a service bay programs a truck once, with an address that will still be Finning's when the machine is eventually retired, and the truck goes back to hauling. Files.com's job is to keep that address announced, routed and answering everywhere the fleet works.

The lesson travels well beyond mining. A fleet of field devices hardcoded to IP addresses never needed a synchronized cutover. It needed the addresses to become permanent, and once Files.com made them permanent, a global device migration turned into ordinary maintenance.