A Semiconductor Company Uses Files.com for Modem-Log Collection Across Three Simultaneous Carrier Assessments

A global semiconductor company designs the modems inside mobile handsets. That position carries a field obligation. When a mobile network underperforms, the handset side of the measurement is the chipmaker’s side, and its engineers are the ones who go find out why.

Each assessment produces modem logs captured off individual handsets, and single log files routinely reach several gigabytes. The systems that turn those logs into answers live on servers inside the company’s own network, reachable only over VPN. So the data is born in the field, at a carrier site, and the analysis happens on-prem. The whole problem lives in the distance between those two facts.

Files.com ultimately turned that gap into a shared collection workflow: three contractor teams could upload from the field without VPN access while the company’s analysis systems stayed on-prem.

Multi-Gigabyte Logs, Stranded Where They Were Captured

From a carrier market, the company’s internal servers were often out of reach. VPN connectivity from field sites was unreliable at best, which meant a day of capture could leave an engineer holding gigabytes of logs with no way to deliver them until they were back inside the network. Analysis waited on travel.

The obvious fixes were closed off. The files were far too large for email or consumer sharing tools. The analysis systems were on-prem and were staying on-prem, so the answer could never be broader network access. And external contractors could not be given internal access at all.

The field team already used a Files.com site for individual captures. When an engineer was working a market and could not connect internally, the captures went through the site, and the volume stayed modest. Files.com had handled individual captures. Its role as a program-wide collection layer had not yet been tested.

Three Markets at Once Made the Site the Shared Collection Layer

In 2025 it was tested. A carrier engagement required network performance assessments in three markets simultaneously, an effort substantially larger than the team’s normal cadence. The company brought in three contractor teams, one per market, and none of them had, or could have, access to the company’s internal infrastructure.

The program needed a collection point that worked from any market with no VPN, accepted single files in the multi-gigabyte range, gave three outside firms and the company’s own engineers shared access to the same folders at the same time, and let back-end engineers pull everything down into the on-prem analysis systems. The field team’s Files.com site became that collection point for the entire program.

One Files.com Site Between the Handsets and the On-Prem Estate

The architecture is deliberately thin. The Files.com site holds user accounts for the company’s engineers and for each contractor team, all working in shared folders. Field teams upload through the web or SFTP from wherever they are. Multi-gigabyte log files go up whole, with no splitting and no staging.

On the other side, back-end engineers pull logs down from the site into the company’s internal systems for processing. The internal servers never open to the field and never touch a contractor credential; only the collection layer is hosted. Because the two sides are decoupled, they overlap. While a market is still capturing, an engineer on the back end is already pulling that morning’s logs off the site and processing them.

Analysis Starts While the Field Is Still Capturing

With Files.com in place as the collection layer, the company replaced a field workflow bounded by VPN reachability with one bounded by what the teams can capture.

• Three contractor teams covered three carrier markets simultaneously through one site, working alongside company staff with no VPN and no internal accounts.
• Log processing begins while capture is still running in the field, instead of waiting for logs to make it back inside the network.
• Monthly volume grew to several terabytes as the program ramped, absorbed without any change to the on-prem analysis systems.
• Adoption spread on its own: other teams at the company that collect logs in the field began asking for access to the same site.

The compounding result is the quieter one. The next field program, whatever its size, starts with folders and user accounts rather than a network project.

The Back End Never Had to Change

Today a field engineer finishes a capture at a carrier site and uploads the logs before leaving the market. A contractor firm joins a program by receiving a Files.com account, not by asking the company’s network team for an exception. And the analysis systems the whole operation feeds sit exactly where they always did: internal, on-prem, untouched.

Files.com became the reachable layer between where the company’s modem logs are created and where they are understood. Field collection did not have to wait for the VPN, and the back end did not have to move, for an operation that once ran one market at a time to run three at once.