4 Systems, 4 Ship Dates, 1 Problem

“What's the ship date on the Johnson order?” Sarah asks. Mike checks the ERP: the 15th. His inbox says the 22nd. Sarah's Excel tracker says the 18th. The supplier portal shows the 20th. He calls the supplier directly and hears the 25th. Four systems, four answers, one order — and this isn't an edge case. It's Tuesday.

The system of record is a lie

Manufacturing has always operated on a comforting principle: pick one system of record and treat it as the single source of truth. In practice, that truth never holds. Suppliers communicate over email. Buyers keep spreadsheets. Planners work in local files. Quality lives in a separate compliance portal. Distributed work produces distributed data — and no amount of migration policy changes that.

The reflex is to consolidate everything into one platform. But by the time the consolidation project ships, there's already a newer email with another change. The map is always one step behind the territory.

Static files are first-class citizens

The mistake is treating PDFs, emails, and spreadsheets as inferior data — temporary workarounds waiting to be cleaned up and keyed into “the real system.” They aren't workarounds. They're where the current answer actually lives.

A virtual data layer reads directly from those sources as they arrive — the email, the PDF, the tracker — capturing each change in real time instead of waiting on a manual re-entry queue in IT. The static file becomes a legitimate input, not a second-class one.

Map by field, not by system

Stop asking which system owns “the supplier.” Ask which system owns which field. Ownership is granular:

• Legal name lives in the ERP, for invoicing.
• Approved parts live in the MES, for production validation.
• Current lead times live in Sarah's Excel tracker, updated from supplier calls.
• The ship date for this specific PO lives in the most recent email.
• Compliance certificates live as PDFs in the portal.

Once ownership is mapped at the field level, you can build infrastructure that connects the right field from the right source — instead of forcing every fact into a single repository that's wrong the moment it's written.

Stop fighting the chaos. Connect it.

Distributed data isn't a defect to eliminate; it's the reality to design around. When Mike asks for a ship date, Sarah checks one interface where all four sources converge — showing the most current value with full lineage back to where it came from.

The shift is from spending months consolidating systems to building a layer that treats Excel, PDFs, email, and portals as equal citizens alongside the ERP — and connects them in hours, not months.