A net-change system processes only the items that have changed since the last planning run, rather than recalculating every item in the entire plan. This is the core truth that distinguishes it from other approaches to material requirements planning (MRP). If you encountered this question on an exam or certification, the correct answer almost certainly relates to this selective, change-only processing logic.
How a Net-Change System Works
In any manufacturing or supply chain environment, plans need constant updating. Orders come in, get cancelled, or change quantities. Inventory levels shift. Suppliers miss deliveries. A net-change system responds to these disruptions by identifying only the specific items affected and recalculating their requirements, leaving everything else untouched.
The types of changes that trigger a net-change update include: bill of material changes, inventory transactions, forecast adjustments, work order changes, purchase order changes, sales order changes, lead time updates, and changes in parent order requirements. Each of these events flags the affected items for inclusion in the next planning run. Items with no changes are skipped entirely.
Because it processes a smaller subset of data, a net-change system runs much faster than a full replanning cycle. This speed makes it practical to run daily or even multiple times per day, keeping plans closely aligned with real conditions on the ground.
Net-Change vs. Regenerative Planning
The alternative to net-change is regenerative planning, which wipes the slate clean and recalculates requirements for every single item in the system. Regenerative runs process the entire master data set from scratch, regardless of whether anything changed for a given item. This is thorough but computationally heavy, often requiring hours to complete in large operations.
Most organizations use both methods together. A common approach is to run regenerative planning once a month to ensure the entire plan is clean and consistent, while running net-change updates daily or weekly to capture ongoing changes between those full regenerations. This combination balances accuracy with processing efficiency.
The key distinction to remember: regenerative planning replans everything, net-change replans only what changed. On an exam, any answer stating that a net-change system “processes all items” or “replans the entire schedule” is describing regenerative planning, not net-change.
The Trade-Off: System Nervousness
Net-change systems introduce a well-known problem called system nervousness, sometimes called MRP nervousness. Because the system recalculates so frequently, it can produce order forecasts and schedules that show extreme variability from one period to the next. A supplier receiving updated plans every day might see quantities and timing shift dramatically each time, making it nearly impossible to plan their own production reliably.
This nervousness is a direct consequence of the netting step in MRP combined with frequent quantity updates. Every time a change ripples through the system, dependent items get rescheduled, which can cascade further down the supply chain. The more often you run net-change updates, the more opportunities exist for these cascading shifts.
Net-change planning essentially deals with uncertainty by rescheduling rather than buffering. Instead of holding extra safety stock to absorb variability, it tries to keep the plan perfectly current. This works well when there is sufficient lead time to actually execute the revised plans, but it creates chaos when changes arrive faster than the supply chain can respond to them.
Common Exam Statements About Net-Change Systems
If you’re answering a multiple-choice question, here are the statements that are true of a net-change system:
- It processes only items affected by changes since the last run. This is the defining characteristic.
- It is typically run more frequently than regenerative planning. Daily or weekly runs are standard.
- It requires less processing time than a full regeneration. Fewer items means faster computation.
- It can contribute to system nervousness. Frequent updates cause schedule instability.
- It updates an existing plan rather than creating a new one from scratch. The baseline plan remains; only affected portions change.
Statements that are false of a net-change system include claims that it processes all items, that it runs less frequently than regenerative planning, or that it eliminates the need for regenerative runs altogether. In practice, net-change supplements regenerative planning rather than replacing it.