Excel Is the Best MES System Ever Made

That’s sarcasm. The problem is how many people didn’t catch it.

I said it in a client meeting recently. “Excel is your best MES system.”

The guy across the table nodded. Seriously nodded. Took it as a compliment to his team.

That’s when I realized I’d delivered it far too straight — and also that he wasn’t entirely wrong about how his plant actually runs.

For the record: Excel is the worst MES system ever made. And it is quietly running a meaningful share of manufacturing in this country.

The spreadsheets are genuinely impressive

This isn’t a post about people being lazy or unsophisticated. The opposite, usually.

I have seen extraordinary work inside these files. Macros that query external databases. Naming conventions with real discipline behind them. Nested sheets that encode years of process knowledge no documentation ever captured. Someone built that, maintained it, and made it work.

The skill isn’t the problem. The architecture is.

What a spreadsheet cannot do

It isn’t connected to anything.

If you believe the numbers in that file reflect live system state, you are looking at a photograph and calling it a window. It was accurate the moment someone pasted it in. Everything after that is decay.

There are more copies than you think.

There is a copy on the shared drive. A copy on a laptop. A copy someone emailed to a supplier in March. A copy named _FINAL_v3_USE THIS ONE. Nobody can tell you with confidence which one the floor is actually working from right now — and the honest answer is usually “different people are using different ones.”

The clever macros are a liability, not a mitigation.

The macros that pull from external databases are the most impressive thing in the file and the most dangerous. They work until a schema changes, a credential rotates, or the person who wrote them leaves. Then they fail — and frequently they fail silently, returning stale data that looks exactly like fresh data.

It has no concept of current.

A real system of record knows what the latest revision is and refuses to let you use the wrong one. A spreadsheet will cheerfully let you build to a two-year-old configuration and won’t say a word.

Where this actually bites

The failure mode isn’t the spreadsheet being wrong. It’s the spreadsheet being out of date while looking completely authoritative.

The classic version: a global company where one site works in inches and another in millimeters. Somewhere in the chain, a human retypes a value and forgets the conversion. Nothing errors. The number looks reasonable. It flows downstream into procurement, into manufacturing, into a part that doesn’t fit.

And that’s the deeper issue — if a person is in the loop transcribing data between systems, they will make a mistake eventually. Not because they’re careless. Because they’re a person, and that’s what the hundredth repetition of a manual task produces.

The point of connecting systems isn’t elegance. It’s removing the transcription step entirely.

What actually replaces it

Not “a better spreadsheet.” Not a stricter naming convention. Not a SharePoint folder with permissions.

What you need is a system that provides three things a spreadsheet structurally cannot:

• Visibility — one place, and everyone knows it’s the place.

• Accuracy — values that come from the system that owns them, not from someone’s copy.

• Currency — a definition of “latest” that’s enforced rather than agreed upon.

For manufacturing process data specifically, that usually means the manufacturing BOM and process plans living in your PLM system with a live link back to the engineering BOM — so when engineering releases a change, the manufacturing side gets told, instead of finding out on the floor. That’s what MPMLink does inside Windchill.

Be honest about the transition

The spreadsheet exists because it solved a real problem faster than IT could. Whoever built it was being resourceful, and telling them their work is garbage is both unkind and counterproductive.

The pitch that actually works is simpler: you built this because you needed visibility nobody else was giving you. Let’s give you that visibility in something that won’t rot.

The knowledge in that file is valuable. The container isn’t.

The short version

• Excel is running production process data at more manufacturers than anyone wants to admit.

• The spreadsheets are often skillfully built — the problem is architectural, not a competence issue.

• Failure modes: no live connection, uncontrolled copies, silently-breaking macros, no concept of “current.”

• Any human retyping data between systems will eventually introduce an error.

• The fix is a connected system of record, and the migration is a people problem more than a technical one.

If your manufacturing process data currently lives in a spreadsheet, the first question isn’t which tool to buy. It’s what that spreadsheet is doing that no other system in your business is doing. That answer usually defines the requirement.

Element Consulting helps manufacturers move process data out of spreadsheets and into connected PLM systems people actually use. Related reading: eBOM vs. mBOM. Talk to a Windchill expert →