BlueScope Used Files.com to Replace Bespoke SFTP Plumbing and Grow Workday and Oracle Integrations

BlueScope Buildings North America is the North American arm of BlueScope Steel, and through brands including Butler Manufacturing and Varco Pruden it describes itself as the largest manufacturer of engineered building solutions in North America. Butler helped launch the pre-engineered building industry, while the wider North American group spans steelmaking, coil painting, and building manufacturing.

Those are genuinely different businesses, several of them acquired over the years, run under a centralized North America IT services model. That structure puts one central team in charge of something every unit depends on: moving files between the systems the group shares. Workday holds HR. Oracle holds finance. Timesheets have to reach internal servers for processing, invoice transactions have to reach the bank, and data feeds have to reach reporting and analytics platforms. Every one of those is a file crossing between systems owned by different teams and different vendors, and that crossing is where BlueScope's problem lived.

BlueScope had run Files.com since 2020, largely as a secure file transfer and sharing tool. Over the last two years, it made Files.com the governed middle layer for those crossings and began retiring legacy SFTP servers and scripts workflow by workflow. Outbound integrations grew from 2 to 10 on that repeatable pattern.

A Server and a Script for Every Integration

The way those crossings got made was bespoke, unit by unit. Business units ran their own on-prem SFTP servers for system integrations, and custom PowerShell scripts driven by Task Scheduler moved data out of Oracle and on to wherever it needed to go next.

The cost of that arrangement was paid on every integration. Each new flow was its own build. Each server was one more piece of infrastructure a unit had to patch and keep online. Each script was plumbing somebody had to keep alive, understood mostly by the person who wrote it. Nothing repeated: when the next business unit needed the same kind of Workday or ERP flow, it built its own version. Across a group of businesses consolidating under one IT organization, with integration volume growing, a fragmented transfer estate had stopped being something the central team could keep absorbing.

The Fix Could Not Be a Direct Integration

The obvious answer, wiring the systems to each other, was ruled out deliberately. BlueScope's leadership did not want direct system-to-system integrations between Workday, Oracle, banking, and reporting platforms. The endpoints belong to different teams and different vendors, and a point-to-point connection binds two of them together permanently.

So the requirement was specific: something that sits governably in the middle of each system pair, reaches on-prem servers behind each business unit's firewall, handles SSH keys and PGP encryption for external counterparties, and repeats identically for the next business unit brought into the fold.

Files.com became that middle layer: the sanctioned platform every migrated file flow crosses on its way between systems.

“Files.com and us are tied together — we typically use Files.com as our middleman between our HR systems, such as Workday, to securely transfer over to our servers for processing, like timesheets.”

An Agent Behind Each Firewall, One Layer in the Middle

The architecture is what Shilo calls the "middleman" made literal. Systems on either end never talk to each other. Each one talks to Files.com.

Reaching the internal side is the job of the Files.com Agent. Seven active Agents run on servers inside the group's networks, supporting Oracle finance workflows, Workday integrations, reporting systems, and on-prem file movement. Each Agent holds an outbound-only connection to Files.com, so an internal server joins the platform without any inbound firewall port being opened. Workday output lands on Files.com and syncs down to the processing servers that need it; Oracle output moves through the same governed layer toward downstream systems, including banking and reporting platforms.

The same layer handles external flows through standard SFTP, SSH key authentication, and Files.com Remote Server Sync. It also manages PGP encryption inside the workflow: tax forms arrive encrypted from a services vendor, Files.com decrypts them as they sync, and the platform distributes them to the employees who need them.

“Files.com does make PGP key management easier than other solutions that offer the same thing.”

The structure repeats per business unit. North Star, the steel mill, runs as a child site under the parent, administered by its own infrastructure team without touching the rest of the group. New Agent versions and sync upgrades are validated in a test environment before they reach production. And the rollout runs unit by unit: as workflows move onto the platform, their legacy SFTP servers and scripts can retire with them.

From Two Outbound Integrations to Ten

With Files.com in the middle, BlueScope replaced per-unit servers and bespoke scripts for migrated workflows with one repeatable integration pattern, and the estate grew on that pattern rather than in spite of it.

• Outbound integrations grew from 2 to 10 in roughly a year, spanning Workday timesheet processing, Oracle finance and invoice flows, HR automations, and analytics feeds into the group's reporting platforms.
• The business units brought onto the platform retired their on-prem SFTP servers, removing the associated patching and maintenance. BlueScope reports the platform is significantly easier to manage than maintaining separate SFTP infrastructure and custom integrations.
• One system administrator operates the Files.com integration estate. Standing up a new flow is typically configuration on the platform, not a new engineering build.

“They see it as magic, and I'm sitting here going, it's pretty easy to set up, all things considered.”

The compounding result sits underneath those numbers. What began in 2020 as a small file transfer tool is now the group's operational integration layer. The same pattern can support another system pairing with a sync and credentials, or another business unit with an Agent behind its firewall.

One Pattern for the Next Business Unit

The rollout is still in progress. An Agent for the next business unit can take an afternoon to add, but BlueScope Coated Products continues to run its Oracle-to-bank flow on a Progress SFTP server, and some Oracle workflows still depend on Task Scheduler and PowerShell while BlueScope works toward a more direct Oracle-to-Files.com connection.

That is already a different operating condition from the one BlueScope started with, where every system pairing meant a server some unit had to patch and a script some person had to remember. BlueScope did not wire its systems together. It gave them one governed place to meet, and each workflow moved onto the platform becomes a repeat of a pattern rather than a new engineering project.