What is the role of ERP in production planning?

ERP usually owns the business-level production plan: what needs to be made, by when, for which demand signal, using which materials, inventory, suppliers, and broad capacity assumptions. It is important, but it is not the whole production control system. In regulated manufacturing, ERP planning only works well when master data, routings, inventory accuracy, engineering changes, and shop-floor feedback are reliable.

What ERP typically does

In production planning, ERP commonly supports material requirements planning, work order creation, purchasing signals, inventory visibility, customer order alignment, and high-level capacity planning. It helps operations and supply chain teams understand demand, material availability, due dates, and planned production load.

ERP is usually the financial and commercial system of record. That matters because production plans are tied to sales orders, forecasts, costing, inventory valuation, procurement, and revenue commitments. A plan that ignores ERP will usually create problems in purchasing, finance, customer commitments, or inventory control.

What ERP usually does not handle well by itself

ERP should not be assumed to manage detailed shop-floor execution on its own. Many ERP systems can generate work orders and planned dates, but they often do not provide the level of control needed for operator instructions, step-level traceability, in-process quality checks, equipment integration, rework loops, electronic records, or real-time dispatching.

Those responsibilities often sit partly or fully in MES, QMS, PLM, maintenance systems, spreadsheets, or local scheduling tools. The exact boundary is site-specific. Some plants run more execution in ERP; others use ERP mainly for planning and financial control while MES manages production execution.

Where the handoffs matter

ERP production planning depends heavily on the quality of handoffs with other systems:

• PLM provides product structures, approved designs, and engineering change information.
• MES often manages dispatching, work instructions, labor capture, WIP status, and execution traceability.
• QMS may control nonconformances, deviations, corrective actions, and quality holds that affect what can be produced or shipped.
• Maintenance or EAM systems affect capacity when equipment availability, calibration, or preventive maintenance constrains production.
• Warehouse and inventory systems affect whether material availability in ERP reflects physical reality.

If these handoffs are weak, ERP can produce a plan that looks valid in the system but fails on the floor.

Common failure modes

The most common planning failures are not caused by ERP alone. They usually come from bad or stale data: inaccurate inventory, unmaintained lead times, incorrect routings, missing alternate parts, poor scrap assumptions, late engineering changes, or WIP status that is updated after the fact.

Capacity planning is another common weak point. ERP may model work centers and lead times, but it may not reflect actual constraints such as shared tooling, inspection bottlenecks, qualified operator availability, machine downtime, test equipment capacity, or quality hold queues. In high-mix, low-volume and regulated operations, those constraints often determine the real schedule.

Another risk is treating the ERP schedule as executable without validation against the shop floor. A planned order date is not the same as a controlled execution sequence.

Brownfield reality

In established plants, ERP rarely operates in a clean system landscape. It usually coexists with legacy MES, PLM, QMS, spreadsheets, supplier portals, maintenance tools, and local scheduling practices. Replacing all of those with ERP is usually unrealistic in aerospace-grade and similarly regulated environments because of qualification burden, validation cost, downtime risk, integration complexity, traceability obligations, change control, and long equipment lifecycles.

A more practical approach is to define clear ownership: ERP for demand, supply, orders, inventory, procurement, and financial planning; MES and related systems for controlled execution and real-time production evidence. The exact split should be documented, validated where required, and governed through change control.

Practical boundary

ERP is central to production planning, but it is only as useful as the data and integrations behind it. It can tell the organization what should be made and what materials are expected to be available. It does not automatically prove that the work was executed correctly, that all constraints were respected, or that records will satisfy customer, quality, or regulatory expectations.