Plainfield Public Schools Put Fragmented Data Pipelines on Neutral Ground With Files.com

Plainfield Public Schools is a K–12 district in Union County, New Jersey, serving several thousand students across 16 schools.

Behind those classrooms runs the data estate every modern district accumulates: a student information system (Genesis), a financial system (SchoolFi), an assessment platform, a graduation-progress tool, and an analytics dashboard, each from a different vendor. Every vendor holds a piece of the district's data, and some refuse to exchange it directly with a competitor. When Plainfield set out to pull all of that data into one dashboard, it found that the only party positioned to connect its systems was the district itself. Files.com gave its data team a district-controlled hub for doing it.

Ten Systems, Two Vendors That Compete, and a Server Behind Another Team

The dashboard was Abre, and it needed file ingestion from roughly ten external systems and vendors. Getting those files was manual and political at once.

The manual half: of the departments feeding a given dashboard, roughly half could drop their reports over SFTP automatically. The rest needed a person to generate the file and upload it by hand, every time the data had to refresh. Teachers and counselors, meanwhile, reached into system after system to assemble the picture they needed on a student.

The political half was harder. The district's assessment vendor and its dashboard vendor were direct competitors and would not exchange data directly, so the assessment extract went to a separate SFTP server owned by LinkIt rather than the district's hub. The refusal was commercial, not technical.

And the one piece of exchange infrastructure inside the district, an on-premises SFTP server, sat inside another team's infrastructure. Tafari Anderson, the Supervisor of Instructional Technology who owned the district's data pipelines, could not change or run anything on it without going through networking.

“I'm at the mercy of networking, and I don't like to feel like I'm at the mercy of networking.”

That was the diagnosis: nobody who owned the district's data pipelines controlled the infrastructure those pipelines ran on. Every connection between systems belonged to whichever vendor or team happened to host it. A districtwide analytics dashboard cannot run on hand-carried files and vendor goodwill, so the fragmentation stopped being survivable the day the dashboard project started.

What the fix had to do was clear before any product entered the picture. The district needed a staging area in the middle, controlled by neither a source-system vendor nor another internal team, where systems could drop files and Abre could collect them. It had to speak the SFTP those systems already used. It had to place files into specific storage locations automatically once they arrived. And it had to be run directly by the team that owned the pipelines. Plainfield selected Files.com to be that neutral middle layer.

A Hub the Data Team Runs Itself

Files.com became the district-controlled exchange point for connected systems moving files in either direction. Anderson configured the site himself, without a ticket to anyone.

Abre drew on roughly ten external systems and vendors. The feeds already connected to Files.com landed at the district's hosted SFTP endpoint, giving source systems a common destination instead of requiring their vendors to integrate directly with one another. The LinkIt assessment extract remained the exception: it still landed on LinkIt's separate SFTP server while the district waited for a vendor-side configuration change to move the drop into Files.com.

Routing runs without people. Files.com Automations fire as files land, moving each drop into the specific folder Abre expects, so data from an automated source travels from system to dashboard with nobody generating, downloading, or re-uploading anything along the way.

The hub carries data both ways. Graduation-progress files from Zello flow through it to the district's counselors, who work the data, and their changes flow back into the dashboard. Teachers and principals make decisions on current numbers instead of last month's export.

The same endpoint retired the on-premises server. Genesis and SchoolFi now run against Files.com as their secure exchange point, trading files daily, hourly, and on demand. The district also centralized access control with sign-in federated across its Microsoft Azure and Google directories and IP whitelisting alongside it.

From Hand-Carried Files to a Standing Pattern

With the hub in production, Plainfield replaced an exchange built on vendor goodwill and hand-carried files with a staging layer its own team runs.

• Roughly ten systems and vendors feed Abre, with Files.com serving as the common exchange point for the sources already connected.
• Every automated source runs end to end with nobody touching a file: the system drops it, a Files.com Automation places it, and the dashboard collects it.
• The instructional technology team changes its own file exchange the day it needs to, with no request to networking and no waiting on another team's server.
• The student information and financial systems exchange files through the same endpoint on daily, hourly, and on-demand cadences, and the on-premises SFTP server is gone.

The immediate result is a dashboard whose automated feeds refresh without hand-carried files. Teachers and principals can open one dashboard instead of assembling a view across several vendor systems. The compounding result is a pattern: for any system that can deliver its file, connecting it to the district's data no longer requires new exchange infrastructure. It becomes another drop point on a hub that is already running.

The District Controls the Ground Its Data Crosses

Plainfield never persuaded its competing vendors to connect to each other. Instead, a neutral staging layer on Files.com, controlled by the district's data team, connects systems without requiring their vendors to integrate directly. The assessment feed still landing on LinkIt's server is the remaining exception—and now has a district-controlled destination ready when the vendor-side configuration allows it.