--- title: "The 5 Stages of ERP Grief (And the Sixth Nobody Talks About)" canonical: https://datanomix.io/2026/10/13/the-5-stages-of-erp-grief/ date: 2026-10-13 05:45:14 description: "We asked IMTS attendees what’s wrong with their ERP. Dozens of sticky notes later: ERP knows the plan. Your machines know what happened." keywords: "ERP Grief" categories: [The Datanomix Blog] tags: [ERP Insights, ERP Integration, ERPiphany] --- ## ERP grief is the frustration manufacturers feel when their ERP can’t tell them what’s actually happening on the shop floor. It runs through five stages, and the sixth is realizing your ERP is the system of record, not the system of insight. Table of Contents- [Final Rule Publication and Effective Date:](#final-rule-publication-and-effective-date) - [The CMMC 2.0 Framework Levels:](#the-cmmc-20-framework-levels) At IMTS 2026, we put up a kiosk, wrote “ERP Complaint Booth” on a whiteboard, and handed out sticky notes to attendees. People did not hold back. We figured we’d get a few laughs. We got dozens of sticky notes, and the only compliments were about having a complaint booth! One sticky note said it all: **“How many parts did we make today?”** That is a manufacturer who cannot get a basic answer out of a system that probably cost six figures and took a year to implement. Read enough of those notes, and a pattern shows up. It looks a lot like the stages of grief. ### Stage 1: Confusion “Confuses everyone!” “Naming is confusing.” “NOT intuitive.” This is where it starts. The system is supposed to be the backbone of the business, and half the people who touch it can’t figure out where anything lives. ### Stage 2: Anger “It’s old as HELL.” “It’s a piece of crap.” “TOO MANY CLICKS!” No translation needed. These are people who fight their software every day just to do their job. ### Stage 3: Bargaining “FREE my DATA!” “No free API!” “Licenses are too expensive to get more.” “Needs to talk to all the relevant adjacent tools.” This is the stage where you realize the data is in there. You just cannot get it out without another license, another module, or another consultant. ### Stage 4: Depression “Takes longer to use ERP than to just do the task.” “Takes a gazillion years to load.” “How many parts did we make today?” “No Support.” This is the one that stings. The system meant to save time is now the thing eating it. ### Stage 5: Acceptance “No one believes it, so everyone creates separate side systems.” Read that one twice. Acceptance on a shop floor looks like a whiteboard here, a spreadsheet there, and a [morning production meeting](https://datanomix.io/2024/01/22/monday-morning-quarterbacking-doesnt-change-anything/) that burns 60 to 90 minutes arguing about whose numbers are right. That is not acceptance. That is everyone quietly deciding to work around the system instead of through it. And then there was the note that simply read, “Another brilliant idea from the Executive Team.” We are not touching that one. Yet. ### System of Record vs. System of Insight The sticky notes are not about a bad vendor. They are about a bad job description. We keep treating the ERP like it is the factory. It is not. It is the commitment: quotes, routings, standards, due dates, what you promised the customer and what you expect to get paid. That work is real. It is also the only work it was designed to do. The conceptual error is treating commitment as if it were the shop floor. An ERP knows what somebody typed. It does not know what the spindle did, what the setup actually took, or which program revision hit the machine. Clock-ins, status codes, and reason codes are not production. They are a story about production, written after the fact, usually late and usually kind. That is why “Data not trusted” and “Don’t trust the data” both made the board. Manually entered data is late, incomplete, and optimistic. Someone wrote “[garbage in, garbage out](https://datanomix.io/2024/06/14/is-your-production-data-garbage/)” on a sticky note too. They were describing the model, not a glitch. So the booth is not a roast of your ERP brand. It indicts the idea that one system of record can also be the system of insight. It cannot. The plan lives in the ERP. What happened lives on the machine. What was supposed to happen lives in the program. Pretending those are the same thing is how you end up with so many sticky notes and zero compliments. ### What you do about it lives with the people. Look at the board again. Many of those notes aren’t really about modules or APIs. They are about a system that works against the people who have to run the place. Too many clicks. No support. Naming nobody understands. A morning meeting that burns an hour arguing whose numbers are right. Side systems because nobody believes the official one. That is not a data problem first. That is a collaboration problem created by software nobody can trust, so everyone builds their own version of the truth and spends the day defending it. Insight is not another screen. It is the same usable picture in front of the people who have to decide before the shift ends. If the system fights them, they will work around it. The sticky notes are the workarounds, written down. ### There’s a Sixth Stage. We Call It the ERPiphany. In April 2025, we published a comic called [Making More: A Manufacturing Evolution](https://datanomix.io/2025/04/28/datanomix-comix-the-missing-link/). One panel is a whiteboard covered in sticky notes. We drew it 18 months before we built the ERP complaint booth. [](https://datanomix.io/2025/04/28/datanomix-comix-the-missing-link/)DATANOMIX COMIX: The Manufacturing Evolution of Making More It opens in March 2025 with a manager asking a simple question: “Why don’t we have the right answers on our production performance?” The guy with the pointer has the answer: “We just need a new ERP!” A year later, the ERP goes live. The operator: “I thought this ERP was going to make me do less???” By September 2026, the manager still does not have the answers. The plan? “Give it another year! We’ll either get it right, or we’ll get a new ERP!” His thought bubble says what everyone is thinking: “I’ll be dead before we finish another new ERP implementation.” September 2026 is this month. The complaint booth played out almost panel for panel. Remember “Another brilliant idea from the Executive Team”? That is the guy with the pointer. In the comic, the ERPiphany shows up a year later. You do not have to wait that long. The signpost has two arrows: Double Down on ERP, or [Machine Data](https://datanomix.io/production-monitoring/). That fork is the [ERPiphany](https://datanomix.io/2025/04/16/making-more-a-manufacturing-evolution/). It is the moment you realize ERP alone will not cut it. Not because it is broken. Because it was never built to see the shop floor. The manager gets there: “I should’ve called Datanomix 18 months ago.” The guy with the pointer: “But I want a new ERP!” The answer to “How many parts did we make today?” already exists. Your machines know. Cycle times, setup times, part counts, utilization. Straight off the controller. [No Operator Input™](https://www.nooperatorinput.org/). ### Two Out of Three Gets You an Argument Most shops try to fix the ERP problem with two sources. A new ERP and, if they’re lucky, the machines. A third one sits on a DNC server, a shared drive, or a thumb drive in somebody’s toolbox. The program. It made the board, too. “No CAD file integration.” “Can’t find my data.” When the program lives in a folder nobody else can see, nobody can verify that the job does what it was actually supposed to do. Ground truth is what you get when ERP data, machine data, and G-code finally sit in the same place. - The ERP knows what you planned. Part numbers, quantities, due dates, routings, what you quoted, what you are getting paid. - The machine knows what actually happened. Cycle time, setup time, spindle load, feed override, door opens, downtime, alarms. Nobody typed any of it in. - The G-code knows what was supposed to happen. The program is the real process definition: the operations, the tool changes, the intended cycle, the rev you are running. Combine only two, and you get an argument. The ERP says the job was quoted at 12 minutes. The machine says it ran at 15. Was the quote wrong? Was the wrong rev loaded? Did somebody change a feed at the control and never tell anyone? Without the program, nobody can say. Put all three together, and you learn when, where, and why a job lost money. ERP Insights brings in the plan. [Production Monitoring](https://datanomix.io/production-monitoring/) captures what happened off the controller. [G-Code Cloud™ + DNC](https://datanomix.io/g-code-cloud/) keeps every program and every rev in one place, tied to the machine that ran it. Most shops think they are running at 80% utilization. The real number is closer to 40%. Your ERP will never show you that gap. Your machines will. ### Put the Plan and the Reality in the Same Room That is why we built [ERP Insights](https://datanomix.io/erp-insights/). It pulls job plans, labor targets, and due dates from your ERP and lines them up against what the machines are actually doing. - **Job Standard Insights:** are real cycle and setup times matching what you quoted? If not, you are giving away margin on every part. - **Labor Efficiency Insights:** clocked labor hours versus actual machine uptime, so you can see where capacity is leaking. - **On-Time Delivery Insights:** completion forecasts based on actual progress, with a warning when a job falls behind, before the customer calls. And for everyone who wrote “Free my data”: [Connect Any ERP](https://datanomix.io/2026/05/22/erp-data-meets-machine-reality/) works with SAP, Epicor, NetSuite, JobBOSS, GlobalShop, Infor, Plex, and nearly any other system, cloud or on-prem. No coding. No consultants. Shops running Fulcrum and ProShop are already doing it. Reata Engineering uses Datanomix + Fulcrum to improve on-time delivery. Ricaurte Precision pairs Datanomix with ProShop. [Garbage in, garbage](https://datanomix.io/2024/06/14/is-your-production-data-garbage/) out works in reverse too. Good machine data in, better plans out. Your ERP gets better when it is fed what actually happened. ### Stop Asking Your ERP to Do a Job It Was Not Built For Every note on that board came from someone who has been let down. We get it. Your ERP cannot tell you how many parts you made today because it only knows what somebody typed into it. Your machines know, and they have been recording it all along. Keep the ERP. Let it do the planning it does well. Let the machines tell you what happened. Let the program show what was supposed to happen. One truth instead of three arguments. [Request your Datanomix Pilot today.](https://datanomix.io/pilot-form/) We will put your ERP, your machines, and your programs side by side, and show you where the gap is. Your machines have been telling the story. Start listening. [EXPLORE ERP INSIGHTS](https://datanomix.io/erp-insights/) [REQUEST YOUR DEMO](https://datanomix.io/erp-insights/#demo) ### More on ERP + Production Reality - [ERP Data Meets Machine Reality: Are You Making Money? Are You On Time?](https://datanomix.io/2026/05/22/erp-data-meets-machine-reality/) - [The Mid-Market Margin Mystery: Solved](https://datanomix.io/2025/11/05/the-mid-market-margin-mystery-solved/) - [ERP or Production Monitoring Software? Which Do You Need?](https://datanomix.io/2024/02/26/erp-or-production-monitoring/) - [DATANOMIX COMIX: The Missing Link](https://datanomix.io/2025/04/28/datanomix-comix-the-missing-link/) ### Related FAQs ** Why can’t my ERP tell me what’s happening on the shop floor?** An ERP only knows what people type into it. Clock-ins, job status, and downtime reasons are entered by hand, which means they are late, incomplete, or skipped. Machine data comes straight off the controller. No human entry. More here: [_The Shop Floor Blind Spot: Why ERP Isn’t Enough for Modern Manufacturers_](https://datanomix.io/2026/04/06/podcast-why-erp-isnt-enough-for-modern-manufacturers/) **Do I need to replace my ERP to get accurate production data?** No. Machine monitoring runs alongside the ERP. The ERP keeps planning, quoting, and scheduling. Machine data fills in what actually happened. If you want the longer version: [_ERP or Production Monitoring Software? Which Do You Need?_](https://datanomix.io/2024/02/26/erp-or-production-monitoring/) **What’s the difference between ERP data and machine data?** ERP data is the plan: quantities, due dates, routings, quoted times. Machine data is the reality: cycle time, setup time, downtime, part counts. Comparing the two shows where jobs lose money. [ERP Insights](https://datanomix.io/erp-insights/) is how we put those two next to each other. --- ## Additional Context What Are the 5 Stages of ERP Grief? ERP grief is the frustration manufacturers feel when their ERP cannot tell them what is actually happening on the shop floor. It runs through five stages: confusion, anger, bargaining, depression, and acceptance. The sixth stage is the ERPiphany. It is the moment you realize your ERP is the system of record, not the system of insight, and the answers you need live on your machines.