A Tier-1 Automotive Supplier Uses Files.com to Find and Resend Missing Shipment Files in Just-in-Sequence Delivery

A tier-1 automotive supplier produces door, window, and related components for OEMs. Its North American manufacturing footprint spans plants in three countries.

Some of that work ships just-in-sequence. At its sequencing plant, the supplier builds parts in the exact order the assembly line will install them. In just-in-sequence supply there is no inventory buffer: each part is built for a specific vehicle and has to reach the line in the order the vehicles come down it.

That order travels as data. The sequencing program on each plant’s sequencing server emits broadcast files. Sequentially numbered shipment files go out to a third-party shipper, each one representing a load on a truck. Serial numbers pass between the PLEX ERP and the sequencing servers. Every one of those files has to arrive, arrive exactly once, and arrive in order. For the supplier, keeping the sequence intact was never optional; it is the product.

Every File Had to Arrive Once, and in Order

Before Files.com, that data moved over a point-to-point estate. The Boomi integration platform made direct SFTP connections to individual servers. Other file exchange with suppliers and customers ran through on-premises FTP servers.

The sequentially numbered files headed to the shipper required a way to verify the run and recover any missing file, because the order feeding downstream sequencing depends on every number being present. The supplier wanted that check built into the transfer layer itself. A point-to-point connection does not provide one.

Exactly-once handling was the second requirement. Processes picked files up from folders on polling intervals, and a file that lingered in a folder risked being processed twice.

The Fix Had to Reach the Plant Floor Without Stopping It

That estate had survived because it was inseparable from live production. The sequencing program is file-triggered legacy software: it consumes a .csv and a matching .done file from a local folder, and it was not going to be rewritten. The sequencing servers sit inside plant networks in three countries and could not be exposed to inbound connections. And all of it carried live just-in-sequence data to automotive customers, so there was no window to take the pipeline down and rebuild it.

What the supplier needed was an integration layer that could reach on-premises folders in three countries without opening the plants to inbound traffic, guarantee that interval-polling processes handled each file exactly once, verify that sequential deliveries were actually sequential and repair the gaps itself, retry through transient outages on its own, and keep the archive all of this leaves behind under control. The supplier selected Files.com to provide that layer and built it out workload by workload while production kept shipping.

Agents on the Sequencing Servers, Automations in Between

The Files.com Agent was installed as a system service on the sequencing servers at two plants, and later at a third in another country. Each Agent made an outbound-only connection to Files.com and mounted the plant’s local folders as Remote Server Mounts, so cloud automations could work directly against on-premises folders with no inbound firewall change. The Agent underpinning the plants has run reliably and smoothly.

The mounts let the supplier keep the sequencing program unchanged while Files.com worked directly with its local folders. When Boomi pulled new-part serial numbers from the PLEX ERP into a .csv, Files.com landed the file and its matching .done trigger on the sequencing server. The sequencing program processed them exactly as it always had.

The same Files.com layer replaced three direct SFTP connections from Boomi to individual servers and staged broadcast files for downstream delivery. To prevent duplicate processing, a read-triggered Files.com Automation moved each file to the archive as soon as it was downloaded, so the next polling pass never saw it. For sequential deliveries to the shipper, an automated check verified that every file in the run was present in number order. Where one was missing, the workflow found it and resent it.

Transient failures resolved themselves too because the Automations retried on their own.

Behind the pipeline, Files.com Data Governance rules organized the archive into dated monthly subfolders, and File Expiration cleared anything past its retention window, including on the Agent-mounted folders at the plants.

A Pipeline That Polices Itself

With the Files.com layer in production across all three countries, the supplier turned a set of direct point-to-point connections into a pipeline that enforces its own rules.

A missing shipment file is now found and resent with no one involved. Move-after-read became the standard pattern for the pipeline’s file handling, so every interval-polling process sees each file exactly once. Production integration processes now use Files.com folders, mounts, and Automations as their staging and archiving layer. The archive manages itself, organized into monthly folders and cleared automatically as files age out, on the plant servers as well as in the cloud.

The pattern also compounds. Bringing another plant into the pipeline means installing an Agent on its sequencing server; that is how a rollout that began at two plants reached a third country. Each new workflow inherits exactly-once handling, automatic retries, and archive governance instead of reinventing them.

Sequence Integrity Now Lives in the Transfer Layer

The supplier did not bolt monitoring onto point-to-point connections. It moved just-in-sequence data onto a layer where integrity is a property of the transfer itself. For a supplier whose product is parts arriving in order, sequence integrity is no longer something people check after the fact. The file transfer layer enforces it.