Shopfloor Matters
Foundations

What is ERP, and why every manufacturer needs a good one

ERP is the backbone of a manufacturing business: finance, orders, purchasing, planning and costing on one set of data. What it does well, and where specialist applications take over.

Illustration: What is ERP?

Every manufacturer I've ever worked with runs on an ERP. Some love it, some grumble about it. Very few could run the business without it.

So before we talk about the systems that sit around ERP, let's give it the credit it deserves.

What ERP actually is

ERP stands for Enterprise Resource Planning. It's the system that runs the business side of a manufacturing company on one shared set of data.

A customer places an order. ERP records it, checks stock, plans what needs making, raises purchase orders for the materials, books the receipts, values the inventory, invoices the customer and posts every transaction to the ledger.

Everything is one record, so the whole business works from a single version of the truth.

Before ERP, each of those steps lived in a different system, or a different spreadsheet, owned by a different department. Reconciling them took days. Month end took weeks.

What a good ERP does well

Most modern ERPs cover a broad footprint. In manufacturing, the core usually looks like this:

  • Finance and accounting. General ledger, payables, receivables, fixed assets, consolidation across entities and currencies.
  • Sales and customer orders. Quotes, orders, pricing, credit checks, delivery promises and invoicing.
  • Purchasing and supply. Suppliers, purchase orders, receipts and three-way matching.
  • Planning. MRP to work out what to make and buy, and when, based on demand, stock and lead times.
  • Inventory and costing. Stock by location, valuation, standard and actual costs, and margin by product or customer.
  • Production orders. Creating the orders, the bills of materials and routings behind them, and booking the results.

ERP is where production is planned and accounted for. It knows what should be made, from what, at what cost, by when.

Why it's worth getting right

I'll be honest, ERP gets a hard time it often doesn't deserve. When it's implemented well, it gives a manufacturer something genuinely valuable.

Control of the money. Every order, every purchase and every stock movement flows through to the ledger. Leadership sees margin by product and by customer, without anyone building a spreadsheet.

Promises you can keep. When sales confirms a delivery date, it's based on real stock, real lead times and a real plan rather than a guess.

A common language. Item codes, customers, suppliers, units of measure and cost centres mean the same thing in every department and every site. You only notice how much that's worth when you work somewhere without it.

A platform to grow on. Adding a plant or a new legal entity becomes a configuration task rather than a new system.

The modern trend towards cloud and composable ERP has made all of this more accessible too. Upgrades arrive continuously. Mid-sized manufacturers now get capability that only the largest could afford a decade ago.

Where ERP stops, by design

ERP is brilliant at running the business. It was never designed to run every operation inside it at the level of detail those operations need.

An ERP knows that 500 units of an order should be made this week. It doesn't need to know which operator ran the line at 2.14am, which batch of resin went into machine 7, why the line stopped for 11 minutes, or whether the torque on station 4 was in tolerance.

That level of detail lives elsewhere. Not because ERP is weak, but because it's a different job, with different users and different data.

ERP Specialist operations applications
Time horizon Days to months Seconds to shifts
Main users Finance, sales, planning, purchasing Operators, supervisors, quality, maintenance, warehouse
Typical question What should we make, and what did it cost? What's happening right now, and is it right?
Data Transactions and summaries Events, measurements, genealogy and test results

That said, ERPs aren't all the same. Some were designed with manufacturing in mind and cover more of the production side than others, such as detailed routings and shopfloor reporting. If you run one of those, it will already handle more of the operational detail than a general-purpose ERP would. And that's helpful for shopfloor applications like MES/MOM, because there's a smaller gap to the extra detail those systems need.

What MES/MOM adds is a different layer of data: finer detail, captured in real time at the point of work, with every event tied to its order, batch, machine and operator. That context is what turns a production record into something you can act on in the moment and learn from over time.

That's where specialist applications come in, as a complement to ERP rather than a replacement for it.

The applications that sit alongside ERP

A good ERP becomes even more valuable when it's surrounded by the right specialists, each doing one job very well and sharing data with the core:

  • MES/MOM runs the shopfloor across all four pillars: production (executing orders and recording output, scrap and downtime), quality (checks, SPC and holds), inventory (material movements, genealogy and traceability) and maintenance (breakdowns and planned work), feeding real actuals back to ERP.
  • Connected worker puts instructions, checklists, skills and handover in front of the people doing the work.
  • WMS handles complex warehousing, picking and storage strategies.
  • APS produces detailed, constraint-based schedules when MRP's view isn't fine enough.
  • CPQ configures complex products and quotes them accurately, and passes a buildable specification downstream.
  • PLM owns the product definition and engineering changes before they reach ERP.

How they connect is a choice in itself. Some go through ERP, some go straight to MES/MOM, and most manufacturers end up with a mix. Have a play with the patterns below.

Interactive

How the strategic applications connect

ERP Runs the business MES/MOM Runs the operation Machines, PLCs and people OPC UA, MQTT and a unified namespace PLMProduct definition CPQConfigure and quote APSDetailed scheduling LIMSLab and samples WMSWarehouse QMSEnterprise quality EAM / CMMSMaintenance Connected workerFrontline apps

Pick an application to see what flows where, and why.

Some ERP vendors offer genuinely best-of-breed options for several of these. Others partner. Either way, the principle is the same: a strong ERP core with specialist applications around it, all working from the same master data.

Be wary of anyone who tells you it has to be one or the other. The best-run manufacturers I see treat ERP as the backbone and add specialists where the operation genuinely needs them.

Next on the line

That's the core. The rest of this learning path looks at each of the specialists around it: what they do and where the boundary with ERP sits, so you can decide whether you actually need one.

Next stop, the smart factory tech stack, system by system. Which of these is your business already stretching ERP to do?

Matt Barber
Written by

Matt Barber

VP & General Manager for MES at Infor. Started as an MES developer, then ran projects, solution design and product. Writes about the smart factory, shopfloor AI and the MES/MOM foundations underneath them.

Keep reading

The newsletter

Get the next one in your inbox

New articles on shopfloor AI, smart factory strategy and the MES/MOM lessons I wish someone had told me before my first implementation.

Prefer LinkedIn? Follow me there →

  • Vendor-neutral, practical guidance
  • Written from real implementations, not brochures
  • Shopfloor AI, smart manufacturing and MES/MOM
  • No hype, no buzzword bingo