# MRP Net Change vs Regenerative Run Time Calculator

> Source: https://netray.co/tools/mrp-net-change-vs-regenerative-run-time-calculator
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Estimate how long a full regenerative MRP run takes compared with a net change run, and how much time net change saves.

## Category

erp-operations

## Audience

- ERP administrator
- Planning manager
- IT operations

## Tool

**Kind:** calculator

**Inputs:**

#### Planned items

**Key:** items

**Type:** number

**Default:** 60000

**Min:** 0

**Step:** 1000

**Unit:** items

#### Average processing time per item

**Key:** ms_item

**Type:** number

**Default:** 45

**Min:** 0

**Step:** 1

**Unit:** ms

**Help:** Total run time divided by items from a past run, multiplied by threads.

#### Parallel processes

**Key:** threads

**Type:** number

**Default:** 4

**Min:** 1

**Max:** 64

**Step:** 1

**Unit:** processes

#### Items with changes since last run

**Key:** changed

**Type:** slider

**Default:** 8

**Min:** 0

**Max:** 100

**Step:** 1

**Unit:** %

#### Affected items per changed item

**Key:** ripple

**Type:** number

**Default:** 2.5

**Min:** 1

**Step:** 0.1

**Help:** Changes ripple to components and parents, so more items are replanned than changed.

**Outputs:**

#### Regenerative run time

**Key:** regen_min

**Expr:** items * ms_item / 1000 / threads / 60

**Format:** minutes

**Primary:** true

#### Items replanned in net change

**Key:** nc_items

**Expr:** min(items, items * changed / 100 * ripple)

**Format:** integer

#### Net change run time

**Key:** nc_min

**Expr:** nc_items * ms_item / 1000 / threads / 60

**Format:** minutes

**Primary:** true

#### Time saved by net change

**Key:** saved

**Expr:** regen_min - nc_min

**Format:** minutes

#### Share of time saved

**Key:** saved_pct

**Expr:** if(gt(regen_min,0), saved / regen_min * 100, 0)

**Format:** percent

**Chart:**

#### Run time vs percent of items changed

**Type:** line

**X:** changed

**From:** 1

**To:** 60

**Steps:** 30

**Series:**

- regen_min
- nc_min

**Disclaimer:** A linear model. Real runs also spend time on setup, database locking and writes, and speedup from parallel processes is rarely perfect. Calibrate with your own run logs.

## Content

**Intro:** Regenerative MRP replans every item. Net change replans only items affected by changes since the last run. This calculator estimates both durations so you can size a batch window or decide when each mode makes sense.

**Sections:**

#### How to use it

**Body:** Take the item count and runtime from a recent regenerative log, and work out the average time per item per process. Enter the percentage of items with changes since the last run, such as new demand, receipts or BOM edits, and a ripple factor for how many items each change touches. The calculator shows both run times and the saving.

**Bullets:**

- Use run logs, not vendor benchmarks.
- Estimate the ripple factor from a past net change run.
- Test the busy day case with a higher change percentage.

#### The method

**Body:** Regenerative time equals items times processing time per item, divided by the number of parallel processes. Net change replaces the item count with the items actually replanned, which equals changed items times the ripple factor, capped at the full set. The crossover occurs when the changed share multiplied by the ripple reaches 100 percent, after which net change gives no advantage.

#### Reading the result

**Body:** With 60,000 items, 45 ms per item and 4 processes, a full run takes about 11 minutes. At 8 percent change and a ripple of 2.5, net change replans 12,000 items in about 2 minutes. The chart shows both lines converging as changes grow. Use it to justify running net change during the day and a regenerative run weekly to clear drift.

#### Common mistakes

**Body:** Teams run net change forever and never regenerate, which lets small data inconsistencies build up. Others assume linear speedup from more processes while the database becomes the bottleneck. Remember that terminology and options differ between ERPs, and some modern systems replan continuously, which changes the question entirely.

**Cta:** If MRP windows are creeping into the working day, Netray can review run logs and planning parameters and suggest where run time is being spent.

**Faq:**

#### When should I use regenerative MRP?

**Answer:** Run it periodically, often weekly or after mass data changes, to rebuild all planning results from scratch and clear accumulated inconsistencies. Net change handles the days between.

#### Why is net change not always faster?

**Answer:** A single change, such as an engineering change to a common component, can affect thousands of parents. When the ripple is large, net change approaches a full run.

#### Does adding processes always help?

**Answer:** Not linearly. Database locking, shared low level code and memory limits cap the speedup. Test increments and watch database wait times.

#### Is run time the right metric?

**Answer:** It is one of them. Also track exception volume, planner trust in the results, and how fresh the plan is when planners start their day.

## Search terms

mrp run time estimate, net change vs regenerative mrp, mrp performance tuning, mrp run duration calculator, regenerative mrp, net change mrp, mrp batch window, mrp parallel processing

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json