Aligning Lean Manufacturing with Your ERP: Making Pull and MRP Coexist
Aligning lean manufacturing with ERP means configuring the ERP to support pull systems, flow, and waste elimination instead of fighting them - because a stock MRP implementation pushes batches, inflates queues, and buries value streams in transactions, which is why lean consultants and ERP teams so often end up at war. The war is unnecessary. MRP and kanban solve different problems: MRP excels at long-lead procurement and demand visibility; pull excels at execution control on the floor. Plants that assign each tool its proper layer get both supplier planning and one-piece flow. This guide shows the configuration patterns that make it work in Infor SyteLine, LN, and M3.
Why Stock MRP Implementations Fight Lean
Classic MRP embeds anti-lean assumptions as defaults: fixed lead times that institutionalize queues, lot-sizing rules (EOQ, period order quantity) that create batches, and work order release logic that pushes material to the floor regardless of downstream readiness. The transactional model compounds it - if every move between adjacent cells requires a reported transaction, the ERP taxes exactly the flow lean is trying to create. The symptoms are recognizable: a plant with 30-minute total cycle time quoting 4-week lead times, WIP queues at every work center because MRP released everything on its computed start date, and operators spending more time reporting than the lean team saved with the last kaizen. None of this is inherent to ERP - it is default configuration. The alignment work is deciding, item by item and loop by loop, which material is planned by MRP, which is executed by pull, and which transactions the ERP genuinely needs versus which it merely inherited.
The Layered Model: MRP Plans, Kanban Executes
The proven pattern assigns each system a layer. MRP owns planning: forecasting, long-lead procurement, supplier schedules, and capacity visibility months out. Kanban owns execution: authorizing production and movement in the short horizon based on actual consumption. The boundary runs item by item, set by demand variability and lead time.
- Runners (stable, repetitive demand): kanban-controlled replenishment loops; MRP sees them for procurement of their components but does not release work orders
- Strangers (lumpy, low-volume, ETO): stay MRP work-order controlled - kanban on erratic demand just builds inventory of the wrong things
- Supplier kanban: convert stable purchased items to faxban or EDI-triggered pull against blanket POs, with MRP providing the forecast the supplier plans capacity against
- Size loops with the standard formula - daily demand times replenishment lead time times (1 plus safety factor), divided by container quantity - and recalculate quarterly as kaizen shrinks lead times
Configuring It in SyteLine, LN, and M3
The Infor ERPs all support pull patterns if configured deliberately. In SyteLine, use order minimum/multiple with reorder-point planning for kanban items (exempting them from MRP order generation), Kanban-style replenishment through the built-in material planning flags, and backflushing at operation or job close to eliminate per-move transactions. Infor LN is stronger still: it has explicit repetitive manufacturing and kanban functionality with automated replenishment signals. M3 supports rate-based scheduling suited to higher-volume repetitive flows.
- Backflush runner materials at pay points (cell exit, final assembly) rather than transacting every move - one transaction where there were six
- Flatten BOMs for cells: intermediate part numbers that exist only because departments once reported separately are pure transactional waste - use phantoms
- Keep lot and serial capture where compliance demands it (AS9100D, ITAR programs) even inside pull loops - backflush can still consume specific lots if capture is at the pay point
- Report production against rate schedules or daily buckets for repetitive lines instead of discrete work orders per batch
Value Stream Costing and the Metrics That Reinforce Lean
Standard cost accounting quietly rewards anti-lean behavior: absorption metrics reward overproduction because building inventory absorbs overhead, and efficiency variances punish operators who stop the line for quality. Aligning the ERP includes the numbers. Value stream costing assigns actual costs to value streams rather than allocating overhead through labor hours, and treats inventory growth as the cost it is, not the asset absorption pretends. Practically, that means restructuring ERP cost centers to mirror value streams, replacing individual labor efficiency reporting with flow metrics - dock-to-dock time, first-pass yield, on-time delivery, and average cost per unit shipped - and presenting box-score dashboards from live ERP data rather than month-end variance packets. Plants do not need to abandon GAAP-compliant standard costing in the GL to do this; they need the operational reporting layer to speak lean while finance keeps its books - a reporting configuration, not a reimplementation.
How Netray AI Agents Accelerate Lean-ERP Alignment
Netray configures Infor ERPs for lean execution and deploys AI agents that do the continuous-improvement math humans rarely keep up with. A kanban-sizing agent recalculates every loop monthly from actual ERP consumption and lead time data, recommending container and card changes as demand shifts - eliminating the stale-loop problem that quietly refills plants with inventory two years after the lean launch. A transaction-waste agent audits the ERP transaction stream for reporting steps that no downstream process consumes and quantifies the labor cost of each, feeding kaizen with hard data. A runner-stranger agent reclassifies items quarterly as demand patterns change, keeping the MRP-versus-pull boundary current. Deployed on-prem for defense manufacturers, clients typically cut shop transactions 40-60 percent, reduce WIP 25-35 percent, and sustain kanban loop accuracy without dedicating an engineer to card math.
Frequently Asked Questions
Can kanban and MRP work together?
Yes - the proven model layers them. MRP handles planning: forecasts, long-lead procurement, supplier visibility, and capacity projection. Kanban handles execution: authorizing production and material movement based on actual consumption in the short horizon. Stable, repetitive items (runners) run on kanban loops while lumpy or engineer-to-order items (strangers) stay work-order controlled. MRP still plans components feeding kanban loops; it simply stops pushing work orders for items that pull governs.
What is backflushing in ERP and when should you use it?
Backflushing automatically issues component material and optionally labor when a downstream event is reported - typically operation completion or job close - instead of requiring separate issue transactions for every part. Use it for stable, repetitive production with accurate BOMs, where it can replace five or six transactions with one. Avoid it where component substitution is common, scrap is variable, or lot-level traceability requires capturing specific lots at consumption - though lot-controlled backflush at pay points can satisfy AS9100D traceability if scanning happens there.
Does lean manufacturing eliminate the need for ERP?
No. Lean eliminates waste in execution, but manufacturers still need ERP for what pull systems cannot do: procurement of long-lead materials, demand forecasting, supplier scheduling, financial and inventory valuation, and compliance records like lot traceability under AS9100D or DFARS. The failure mode is running ERP defaults that push batches against lean flow. Aligned correctly - MRP planning above, kanban execution below, backflushed transactions, value stream reporting - the ERP becomes lean's information backbone rather than its enemy.
Key Takeaways
- 1Why Stock MRP Implementations Fight Lean: Classic MRP embeds anti-lean assumptions as defaults: fixed lead times that institutionalize queues, lot-sizing rules (EOQ, period order quantity) that create batches, and work order release logic that pushes material to the floor regardless of downstream readiness. The transactional model compounds it - if every move between adjacent cells requires a reported transaction, the ERP taxes exactly the flow lean is trying to create.
- 2The Layered Model: MRP Plans, Kanban Executes: The proven pattern assigns each system a layer. MRP owns planning: forecasting, long-lead procurement, supplier schedules, and capacity visibility months out.
- 3Configuring It in SyteLine, LN, and M3: The Infor ERPs all support pull patterns if configured deliberately. In SyteLine, use order minimum/multiple with reorder-point planning for kanban items (exempting them from MRP order generation), Kanban-style replenishment through the built-in material planning flags, and backflushing at operation or job close to eliminate per-move transactions.
Put this into numbers
Free interactive tools for exactly this problem. No signup to use them.
Shop Floor Digitization Scorecard
A 10-question scorecard measuring how much of your shop floor still runs on paper - and which digitization gaps are costing you the most.
Free ToolSafety Stock Calculator
Size statistically defensible safety stock using demand variability, lead time variability, and your target service level, then see what that buffer costs to carry.
Free ToolS&OP Maturity Assessment
Assess your sales and operations planning process across cadence, data quality, scenario capability, and accountability, and get a staged roadmap to the next maturity level.
Terms used in this article
Ask Netray for a lean-ERP alignment assessment - we will identify every configuration and transaction working against your value streams.
Related Resources
Finite Capacity Scheduling: A Practical Guide
Finite capacity scheduling explained: how it differs from infinite MRP loading, APS options for SyteLine and LN, data prerequisites, and AI-assisted scheduling.
ERPManufacturing Costing Methods Compared: Standard, Actual, Average
Standard, actual, and average costing compared for manufacturers: variance analysis, ERP setup in SyteLine and LN, DFARS considerations, and AI cost intelligence.
ERPShop Floor Data Collection: Connecting Machines to ERP
Shop floor data collection guide: connect CNC machines, barcode scanning, and IIoT sensors to ERP. Covers OPC UA, MTConnect, Factory Track, costs, and AI agents.