MRP Run
Net requirements across multi-level BOMs.
- Time-phased net requirements
- Action messages: release, reschedule, cancel
- Multi-plant netting
- Pegging up and down
- Frozen-zone respect
- Exception filtering
MRP 4 feature areas
MRP & DDMRP.
Classical MRP and Demand-Driven MRP under one roof. Buffer-driven planning that absorbs volatility.
DDMRP Buffers
Strategic decoupling and buffer profiles.
- Decoupling point analysis
- Buffer profiles by ADU and lead time
- Net flow equation
- Color-zone alerts (red, yellow, green)
- Buffer tuning recommendations
Average Daily Usage
The signal everything else listens to.
- Configurable ADU windows
- Forecast blending
- Outlier handling
- ADU drift alerts
- Per-SKU overrides
Execution Priority
Buffer status, not due date, drives the queue.
- Buffer-color execution lists
- On-hand alerts
- Spike management
- Lead-time monitoring
MRP FAQ
MRP & DDMRP — questions buyers actually ask.
Does NexliOne support both classical MRP and Demand-Driven MRP (DDMRP)?
Yes — both run under one engine. Classical MRP delivers time-phased net requirements with action messages (release, reschedule, cancel) across multi-level BOMs and multi-plant netting. DDMRP layers strategic decoupling, buffer profiles by ADU and lead time, the net flow equation, and color-zone execution alerts on top.
How does NexliOne DDMRP calculate buffer profiles?
Buffers are sized by Average Daily Usage (ADU), lead time, variability, and minimum order quantity. Decoupling-point analysis identifies which BOM positions hold buffers; profiles tune over time as ADU drifts, with buffer-tuning recommendations surfaced as exceptions.
Can NexliOne MRP run multi-plant netting with pegging?
Yes. Multi-plant netting runs across the network, with pegging up and down so you can trace any requirement to its driving demand and any supply to the demand it serves. Frozen-zone respect prevents the engine from rescheduling within the agreed planning fence.
Does NexliOne MRP generate action messages for release, reschedule, and cancel?
Yes. Action messages are exception-filtered so planners see only what needs decisions — releases, reschedules in or out, and cancellations. Filtering rules prevent the noise that makes traditional MRP exception lists unusable.
How does DDMRP color-zone execution differ from due-date scheduling?
Due dates assume the plan is correct; DDMRP color zones assume buffers are the truth. Execution priority is driven by buffer status (red, yellow, green) and the net flow equation rather than the original due date — the queue reflects what the system needs now, not what the MRP run expected last week.
Get started
Ready to spin up MRP & DDMRP?
Try every module free. Bring your existing systems — we'll connect them at no cost. Cloud or self-hosted.