No more open-ended man-day invoices.Buy outcomes, not man-days.We offer Implement at a fixed price based on the validated scope.

MindDX Blog

Not What Your ERP Does, but What It Changes on the Shop Floor · abas ERP

Topicsabas ERPArtificial IntelligenceTechnology Solutions

MindDX cover: a typographic graphic with the article title and four of its sections, from «Contents» to «Conclusion».

Reading time: 4 minutes | Published in August 2026 | Relevant for: Manufacturing · ERP · abas · Production planning · OEE · Delivery · CFO · Digital transformation

“What does your ERP do?” — This is the question most often asked when a technology decision comes up in a manufacturing company. But it is the wrong question. Because a feature is a promise; what really matters is what that feature changes on the shop floor. The value of software is measured not by how eye-catching it looks on the demo screen, but by what the planner sees on their screen at 07:00 on Monday morning, and by whether the shift supervisor’s job has become easier. The right question should not be “what does it do” but “what does it change”.

Summary — The real value of manufacturing technology is seen not in the feature list but in four concrete results that emerge on the shop floor: the quality of the information the planner has in hand in the morning, the shift supervisor’s real-time visibility, the speed at which an order flows into production, and the customer receiving feedback without having to call. In this article, in the context of abas ERP, we look at the right questions to ask to test whether an ERP or artificial intelligence (AI) feature has achieved its purpose, the distinction between “evidence and promise”, and how to evaluate a solution provider properly.

Contents

  • The wrong question: “What is this software for?”
  • The right questions: What did it change on the shop floor?
  • The planner’s Monday 07:00
  • The shift supervisor, the order flow and delivery
  • Asking for evidence is nothing to be ashamed of, it is a standard
  • Conclusion: A commitment to results, not features

The Wrong Question: “What is this software for?”

The longer the feature list gets, the harder — not easier — the decision becomes. Because a feature is a promise; a result is evidence. The fact that a module exists does not mean it will work in your plant, with your product range or with your shift pattern. A situation frequently observed in the industry is this: the purchasing decision is made on the basis of a demo, but success or failure is decided on the shop floor. Two different environments.

The real question should not be “what does it do”, but “what does it change”. And this change should be measurable not in the abstract, but through concrete people and moments.

The Right Questions: What Did It Change on the Shop Floor?

You can test whether an ERP or artificial intelligence (AI) feature really works in a manufacturing company with four concrete questions.

Did the planner start work at 07:00 on Monday with more comprehensive information? Are work orders, capacity and material status up to date on a single screen, or does the planner still start the day by merging three separate Excel files? In a system focused on discrete and job-shop manufacturing like abas ERP, the integrated operation of the PP (production planning) and MM (materials management) modules is what makes the difference on that morning.

Has the shift supervisor’s job become easier? Can the person on the shop floor see a stopped machine or a missing material in the system immediately, or do they find out by phone? Without OEE and machine status visibility, the shift supervisor manages by looking at the past; with visibility, they manage the future.

Did the order reach the right place faster? Has the process from sales to production, and from production to shipping, become shorter? Integration between SD (sales) and production ensures that the delivery date is a commitment rather than an estimate.

Did the customer receive feedback without having to call? Was a delivery delay noticed before the customer complained? This is the clearest indicator of whether the system is proactive or reactive.

If the answer to these four questions is “I am not sure”, the feature has not yet achieved its purpose.

Asking for evidence is nothing to be ashamed of, it is normal

Manufacturing companies have patiently put up with technology promises for a long time. The standard now expected from the supplier is clear: evidence, not promises; results, not features; the customer, not capacity. Instead of asking a solution provider “What does your artificial intelligence do?”, asking “What did it change on the shop floor in a manufacturing business similar to yours?” puts your decision on a much more solid footing. Ask for results, not a demo.

At MindDX, we set ourselves the following goal in abas ERP implementations: we measure success not on the screen that goes live, but on the planner’s Monday morning and in the delivery for which the customer did not have to call.

▶ abas ERP Demo Video

Conclusion: A Commitment to Results, Not Features

Choosing manufacturing technology is not a feature contest but a commitment to results. When you ask the right question — “what does it change on the shop floor?” — it becomes easier to identify both the right solution and the right partner. If you would like to discuss what the manufacturing-focused structure of abas ERP could change in your plant, you can schedule an assessment meeting with the MindDX team.

Talk to MindDXAsk the AssistantAll articles on MindDX Blog

Start your project with a measurement, not an estimate.

Talk to MindDX