When ERP and MES Go Down: How to Keep Production Running Without Digital Systems
Digitalisation · 4 min read · 19.11.2026

At half past eleven in the morning, the line stopped. It wasn't on the sheet — there were no sheets. Dispatching had no orders, the warehouse couldn't issue material because the system hadn't confirmed the reservation, and label printing was sending into the void. The foreman went looking for paper job tickets, scrapped three years earlier "as redundant". This scenario isn't hypothetical. A recent global IT outage hit manufacturing companies too, and showed that firms that digitalized quickly and without a fallback mode had built a single point of failure. When the cloud went down, the shop floor stood still. At Foreast, in our projects at manufacturing companies, we keep seeing the same pattern: the more smoothly digitalization runs, the less anyone asks what happens the day it stops running.
Prioritize Systems by Whether They Stop Production or Just Slow It Down
The first step is trivial. Most companies have never done it. List all your digital systems and sort them into two columns. First column — stops production. Second — only slows work down. The first typically includes MES, ERP with material reservations, production label and document printing, CNC program management, and gauge calibration tied to a server. The second includes reporting, BI dashboards, training records, the intranet.
For each system in the first column, assign two numbers: how long before an outage shows up in production (5 minutes in some places, 4 hours in others), and how many hours you can last without it before a customer delivery fails. Typical result for a mechanical engineering company under 200 people: MES stops assembly within 20 minutes. ERP slows shipping within 2 hours. A label printing outage blocks shipping immediately — without a label, goods must not be released.
This matrix is the foundation of Plan B. Without it, you invest in backups at random. Most often where the IT folks are shouting, not where blood is actually flowing.
A digital company without a fallback mode isn't efficient. It's a company with a single off switch held by someone entirely different.

An Emergency Paper Kit for the Shop Floor
The second step is physical. A box in the workshop — ideally locked and sealed — containing what you need for 8 hours of production without systems. Not "somewhere on a drive", but on paper. When the cloud goes down, you don't have access to PDFs either.
What belongs in it:
- Current order list — printed once a week, with the print date in the header. An old version is worse than none.
- Copies of production standards and drawings for orders running in the next 14 days. The rest isn't needed.
- Label templates — at least for the top 10 items. The printer stays; only the system feeding it goes down.
- Contact list — who decides on stopping production, who communicates with customers, IT support, suppliers of critical material. Phone numbers, not emails.
- Manual material receipt and issue procedure — one sheet: what to record, who signs, where to file the paper so it can be entered back into ERP after recovery.
The kit has a named owner and a refresh schedule. Replace the order list once a month, check the entire contents once a quarter. Without an owner, the box is outdated within a year — and dangerous in a real outage.
Practicing the Outage Like a Fire Drill
Fire evacuation works because it's practiced. A system outage follows the same principle. Once a quarter, set aside 2 hours and simulate an outage for real: the foreman announces "MES and ERP unavailable", the shop floor switches to the paper kit, and an actual order runs through manually.
During the drill, three things get resolved that reading a procedure never reveals:
- Who decides. One person declares the emergency mode, one ends it. Otherwise the outage turns into 40 minutes of arguing over who has the authority.
- Working with data. Every manually filled-in paper should have a prescribed format so that, after recovery, one person enters the data into the system — not everyone on their own. Otherwise you pay for duplicate receipts and zero stock levels for a week after recovery.
- Customer communication. A prepared message and a clear rule on who calls. A customer will forgive a 4-hour delay with timely information. Silence, they won't forgive.
After each drill, 15 minutes of feedback: what was missing from the kit, which procedure couldn't be followed, who was overloaded. Write the changes into the kit within 48 hours. Otherwise they get forgotten.
Key Takeaways
- Divide systems into those that stop production and those that only slow it down — and assign to each how many hours you can last without them.
- Put together a locked paper kit for the shop floor: orders, standards, label templates, contacts, and a manual material receipt and issue procedure.
- Practice the outage once a quarter for 2 hours — with a clear person in charge, a format for papers to be re-entered, and prepared customer communication.
- A measurable goal: production can handle 4–8 hours without systems with no loss of output and no data chaos after recovery.
The global outage of a single software vendor showed once again that digitalization without a Plan B isn't efficiency. It's risk relocated to someone else's server. The goal isn't to go back to paper — paper is a fire extinguisher that should be tucked away but functional. The goal is for the shop floor to run on its own for 4–8 hours and for the data to come back clean after recovery. If you want to know where your company stands, take a look at the production digital resilience audit — in two days on site, we'll tell you exactly where an outage would stop the line and what to do about it first.
Your first cobot on the shop floor: how to choose the operation and calculate the payback
From Estimates to 49% OEE: How an Automotive Supplier Moved to Online Machine Monitoring
On-Time Delivery at 71%: How a Switchgear Manufacturer Moved from Paper to a Digital Work Order