Why do material shortages keep hitting production lines that plan ahead?

How does the app calculate what needs to be ordered before the line knows it needs it?

What does Material Requirements Planning give your team?

• Time-phased material planning from live demand plus forecast data. When a new sales order arrives or inventory is adjusted, the requirements calculation reflects that change immediately. The plan your team reviews this afternoon includes everything that moved this morning.
• Automatic net requirements calculation after netting on-hand inventory and open orders. The system deducts what is already in stock plus what is already on order before calculating what still needs to be procured. Planners see what is genuinely short rather than gross requirements that ignore existing coverage.
• Multi-level BOM explosion down to purchased components. Requirements cascade through every sub-assembly level in the BOM, offset by each component's current lead time. Lower-level shortages surface in the planning run, not when the assembly line hits them.
• Purchase order suggestions generated from planning output. The MRP run produces a list of recommended purchase orders with quantities and required-by dates. Planners review, adjust if needed, plus release directly to the Purchase Orders module without rekeying the data.
• Lead time and reorder point logic maintained at the component level. Each purchased item carries its own lead time record. When a supplier's lead time changes, updating that record immediately affects every future planning calculation that involves that component, not just the ones the planner thinks to adjust manually.
• Exception reporting that surfaces only the items that need a decision. The system flags items where current lead times make it impossible to meet the required date, items approaching reorder points without an open purchase order, plus items where the plan has changed since the last review. Planners spend time on problems rather than on scanning a complete requirements list for issues.
• On-screen overrides with immediate recalculation plus full audit trail. A planner who adjusts a lead time or overrides a suggested quantity sees the updated requirements immediately. The original system value and the override are both preserved in the planning log.
• Full integration with purchasing and inventory so the plan stays connected to execution. Released orders land in the Purchase Orders module in the same step. When goods arrive and a receipt closes, the inventory update flows back into the next planning run without a manual sync step.

What changes operationally after deploying this app?

• Material shortages surface three to four weeks before they would stop production rather than the day the line is already waiting. The time-phased calculation shows the gap while there is still time to expedite or substitute.
• Excess inventory stops accumulating because procurement quantities are calculated from actual net requirements rather than from round-number reorder quantities a planner set years ago and nobody has revisited.
• Lower-level BOM component shortages get caught in the planning run rather than at the assembly station. A sub-component that was short shows up as an exception before the finished goods build starts rather than after materials have been kitted.
• Supplier lead time changes get reflected in procurement timing the same day they are updated rather than living in a planner's personal notes while the system keeps generating late purchase orders.
• Planning decisions become auditable. When a supply chain audit or a production post-mortem asks why a particular purchase order was placed late or why a quantity differed from the system suggestion, the planning log shows the exact override, who made it, plus what the system had originally recommended.

Frequently Asked Questions

How many BOM levels does the MRP calculation handle?

+

The MRP calculation handles multi-level BOMs without a defined ceiling on depth. PCG configures the BOM structure during deployment to match your product architecture. Whether your finished goods require two levels of sub-assembly or six, the explosion follows the structure all the way down to purchased components and offsets each level by its lead time. Planners see the full picture of what needs to be ordered across all levels in a single planning run rather than having to run separate calculations per BOM level.

Can planners override MRP suggestions without affecting the underlying system parameters?

+

Yes. On-screen overrides apply to a specific planning run without changing the underlying lead times, reorder points, or BOM quantities. A planner who knows a particular supplier is running long this week can adjust that component's lead time for the current run without affecting the system parameter that all future runs use as a default. The override is logged separately from the system parameter so the audit trail shows exactly what changed, when, plus whether it was a system default or a planner adjustment.

How does the app handle components that are shared across multiple finished goods BOMs?

+

Shared components are netted across all BOMs that reference them in a single pass. If Component A is used in three different finished goods and all three have active production requirements, the MRP calculation aggregates the total demand for Component A, nets it against current on-hand inventory plus open purchase orders, and generates a single net requirement. The planner sees the consolidated picture rather than three separate requirement lines for the same component that would need to be manually combined to understand total exposure.

Does MRP use forecast data, actual orders, or both?

+

Both, configured by planning horizon. For the near-term horizon where confirmed production orders exist, MRP runs against actual demand. For the forward horizon where only forecast data is available, MRP uses the demand plan from the Demand Planning module. The transition point between actual and forecast demand is configurable. Operations that run to order with short lead times may use actual demand only. Operations with long procurement lead times that require forward visibility run against forecast data for the extended horizon.

How does exception reporting work and what triggers an exception flag?

+

Exception flags appear when the planning run identifies a condition that requires a planner decision rather than a routine procurement action. The main triggers: a required date that cannot be met given the current supplier lead time, a component approaching its reorder point with no open purchase order in the system, a demand change since the last planning run that affects an already-released purchase order, plus a BOM component with no defined supplier or lead time. The exceptions list shows only flagged items so the planner works through decisions rather than reviewing every line in the requirements output.

Can MRP generate purchase orders automatically or does a planner always review first?

+

PCG configures the release rules during deployment to match your operational preference. Some operations prefer full planner review before any purchase order is released. Others set auto-release rules for routine replenishment items below a quantity threshold, with planner review required only for items above that threshold or flagged as exceptions. Either approach works within the same system. The planning log records whether an order was auto-released or manually approved regardless of which rule applies.

How long does MRP deployment take for a manufacturer currently planning from spreadsheets?

+

PCG loads your BOM structures, configures lead times per component, plus sets up the integration with inventory and purchase orders during deployment. Most manufacturing teams run their first live MRP planning cycle within three to four weeks of starting. Complex BOM structures take longer to load initially. Full deployment, including exception reporting configuration plus integration with Demand Planning, typically completes in weeks rather than months. PCG has deployed MRP for operations ranging from small custom fabricators to high-volume manufacturers running hundreds of active component SKUs.