Classical time-phased planning nets demand, inventory, supply, and policy.
- Time-phased net requirements
- Multi-level BOM explosion
- Multi-plant netting
- Frozen-zone and planning-fence respect
MRP 10 feature areas
MRP & DDMRP.
Classical MRP and Demand-Driven MRP under one roof. Buffer-driven planning that absorbs volatility.
Demand-driven buffers absorb variability where the network needs decoupling.
- Buffer profiles by ADU and lead time
- Red, yellow, and green zone alerts
- Net flow equation support
- Buffer tuning recommendations
Demand signal quality drives buffer quality.
- Configurable ADU windows
- Forecast and actual blending
- Outlier handling
- SKU-level ADU overrides
Decoupling points are chosen by structure, variability, and service objective.
- BOM-position decoupling analysis
- Lead-time compression view
- Variability and demand-risk scoring
- What-if decoupling scenarios
Planned orders become purchase, transfer, or production work with traceability.
- Planned purchase, transfer, and production orders
- Order release suggestions
- Lot sizing and minimum order quantity rules
- Supplier and plant sourcing policies
Planners can trace a recommendation back to the demand that caused it.
- Pegging up and down the BOM
- Demand-source drill-through
- Supply-to-demand allocation view
- Exception history per item
The planner sees decisions, not noise.
- Release, reschedule, expedite, defer, and cancel messages
- Exception filtering and grouping
- Priority by service impact
- Acknowledge and suppress controls
MRP recommendations are checked against practical capacity and material limits.
- Critical material visibility
- Supplier and work-center constraint flags
- Lead-time risk indicators
- Handoff to CRP and APS for feasibility
DDMRP execution queues prioritize buffer health over stale due dates.
- Buffer-color execution lists
- Spike management
- On-hand and on-order alerts
- Planner workbench by item and buffer status
Planners work by impact, owner, and due date from one queue.
- Exception severity by item and location
- Bulk acknowledge and assign
- Root-cause tags for recurring messages
- Planner notes and follow-up reminders
MRP FAQ
MRP & DDMRP — questions buyers actually ask.
Does NexliOne support both classical MRP and Demand-Driven MRP (DDMRP)?
NexliOne is designed to support this workflow — 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?
NexliOne is designed to support this workflow. 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?
NexliOne is designed to support this workflow. 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 evaluate MRP & DDMRP?
Tell us what you run today and what this workflow needs to fix. We will map the module, implementation path, and expected cost before you commit.