MES vs spreadsheets: when the workbook stops scaling.
Half the floors we visit run on spreadsheets, and plenty of them work. This is the honest version of the comparison: where a workbook is still the right tool, where it starts costing you, and what actually changes when the record moves into an MES.
| Job | Part | Qty | Status | Updated | |
|---|---|---|---|---|---|
| 2 | JOB-2211 | 5015-A | 240 | Running | 09:12 |
| 3 | JOB-2212 | 5015-B | 120 | Done | 11:04 |
| 4 | JOB-2213 | 4402-C | 60 | #REF! | — |
| 5 | JOB-2213 | 4402-C | 60 | Done? | yesterday |
| 6 | JOB-2214 | 7781-A | 480 |
Two people answered the same job. One formula lost its column. Nobody did anything wrong.
Spreadsheets aren't the enemy. Scale is.
Excel is the most successful manufacturing software ever shipped: free, familiar and endlessly bendable. The question isn't whether spreadsheets work; it's whether they still work at the size you've reached.
Where a spreadsheet still wins
One person, one question, one afternoon. Nothing beats a fresh sheet.
- One-off analysis and what-if models
- Quoting experiments before a job is real
- Data one person owns end to end
- A two-person shop running one job at a time
Where it starts costing you
The workbook fails quietly, not with an error, but with a morning meeting arguing about whose export is right.
- Three people editing the same tracker at once
- A customer asking for the full trace on a part
- An auditor asking who changed a number, and when
- The morning meeting running on yesterday's export
- Every site keeping its own version of the truth
The workbook vs the system.
Dimension by dimension, with credit where the spreadsheet deserves it. Eleven things a floor does every day, and what each one costs on either side.
| Dimension | On the workbookExcel · Sheets · exports | On the recordBulk, the live system |
|---|---|---|
| Getting data in | ||
| Data entry | Re-keyed at the end of the shift, from paper notes and memory. | Captured at the workstation as work happens: starts, stops, counts. |
| Duplicate copiesERP · tracker · whiteboard | The same order keyed into the ERP, a tracker and a whiteboard. | One record. Every module reads the same row.One data thread |
| Seeing the floor | ||
| Real-time visibility | Accurate at the moment someone exported it. | Live this second, on workstations, boards and TVs. |
| OEE & reporting | Formulas one person maintains; every workbook defines OEE its own way. | Computed from operator timers. One definition everywhere.OEE & Analytics |
| Proving it | ||
| Traceability | VLOOKUP archaeology across tabs and file versions. | Job → part → test → document, linked: a trace in clicks, not an afternoon. |
| Audit trail | Cell history if you're lucky; edits overwrite the past. | Immutable who-did-what-when, kept by default.Audit trail |
| Working together | ||
| Many hands | Locked files, merge conflicts and v7_FINAL_final.xlsx. | Concurrent by design, with role-based access down to the action. |
| Quality & NCRs | A "defects" tab nobody owns. | A numbered NCR queue with an owner on every problem.Quality & NCR |
| Multi-site | One consolidation workbook, one analyst-week per month. | Every plant on one drillable board, live to the second.Multi-site roll-up |
| Changing it | ||
| Cost of change | Formula spaghetti only its author understands. | Fields, statuses and numbering changed on a settings screen, live. |
| Who keeps it alive | The one person who built it. Hope they stay. | The platform: hosted, backed up, updated. |
Row by row is one thing. Watching your own jobs run live is another.Bring us your worst workbook
Retire the workbook, keep the truth.
The floor stops reporting what happened and starts recording it: one live record instead of a Friday export.
- Live, not stale
This second,
not last weekBoards, workstations and TVs read the same record the floor is writing right now.
- One record
One thread,
zero forksOrders, jobs, tests and documents link on one data thread. No duplicate keying, no rival versions.
- Audit-ready
Who, what, when:
kept for youEvery action lands as an immutable record, so the history exists before anyone asks for it.
- Trace in clicks
A recall trace
in minutesFollow a job to its parts, tests and documents without opening a single workbook.
Four steps, no rip-out.
You don't migrate a decade of spreadsheets in a weekend. You stop feeding them. Bulk runs alongside what you already have; the workbook retires when it's earned it.
- 01
Map the workbook
List what each sheet actually tracks: columns, statuses, numbering. That's the spec of how your floor works today.
day one - 02
Shape Bulk to match
Recreate those fields, statuses and numbering on a settings screen, shaped to your process, not the other way round.
shaped, not forced - 03
Run one line in parallel
Point incoming orders at intake (PDF, scan or spreadsheet) and run a single line both ways until you trust it.
intake reads sheets - 04
Retire the workbook
The floor writes the record at the workstation; Excel keeps the one-off analysis it was always best at.
the floor runs live
Where the workbook goes next.
The comparison in depth: the thread that replaces the copies, the numbers it feeds and the floors that made the switch.
- One data threadWhy one linked record beats four copies of the same order.
- OEE & AnalyticsOEE computed from operator timers, not end-of-week formulas.
- Shaped, not forcedFields, statuses and numbering set on a settings screen. No code.
- Multi-site roll-upEvery plant on one drillable board, live to the second.
- OEE dashboards vs spreadsheetsThe deep dive on tracking OEE in Excel, and where it breaks.
- Bulk vs TulipWeighing vendors instead? The honest platform-vs-system comparison.
Questions, answered.
Can a spreadsheet work as an MES?
At small scale, honestly, yes. One person, a handful of jobs and a disciplined owner can run a floor from a workbook. The comparison changes when several people write to the record at once, or when someone outside the company asks you to prove what happened.
When should a manufacturer replace spreadsheets with an MES?
The reliable signals: three people editing the same tracker, a customer asking for a full trace, an auditor asking who changed a number, morning meetings run on yesterday's export, or sites keeping rival versions of the truth. Any two of those and the workbook is costing more than it saves.
What does an MES track that Excel can't?
Less what it tracks than how the record is made: an MES captures work as it happens (starts, stops, counts) concurrently from many stations, keeps an immutable audit trail by default, and links jobs, parts and tests so a trace is a click, not a VLOOKUP. In Bulk, those operator timers also feed live OEE.
Do we have to replace our ERP to get off spreadsheets?
No. Bulk runs on the floor alongside your ERP. Approved orders flow in as jobs and the live production record flows back out, so your system of record stays where it is.
How do we migrate years of spreadsheet data?
You mostly don't have to. Shape Bulk's fields and statuses to match how you already work, let intake read incoming orders (they arrive as PDFs and spreadsheets anyway) and run one line in parallel until you trust it. Old workbooks stay as archive, and ready-made templates cover the forms they grew out of.
Can we still use Excel after moving to an MES?
Yes, for what it's good at. Every record exports, and the REST API can feed a workbook for ad-hoc analysis. What ends is Excel as the system of record on the floor.
Bring us your worst workbook.
Send us the tracker with the forked tabs and the #REF! column. We'll map it to Bulk field by field and show you the same jobs running live.