Hour-by-hour capacity load shows whether the plan can actually run.
- Daily, weekly, and monthly buckets
- Available versus required hour charts
- Work center filtering
- Drill-through to work orders and planned orders
CRP 6 feature areas
Capacity Requirements Planning.
Match the work in front of you to the capacity behind it.
Capacity is modeled at the resource where constraints occur.
- Machine, labor, and combined capacity types
- Status, calendar, and bottleneck flags
- Effective capacity and utilization fields
- Import and export for capacity master data
Shifts, holidays, maintenance, and overtime change the available hours.
- Shift and holiday calendars
- Planned downtime and maintenance blocks
- Overtime and temporary capacity rules
- Calendar version history
Capacity risk is highlighted before the production schedule is committed.
- Upcoming overload forecast
- Critical, warning, and low-utilization states
- Top bottleneck list
- Alert routing by planner or work center
Planners can test overtime, alternate routes, and demand changes quickly.
- Scenario overlays
- Additional shift simulation
- Alternative routing suggestions
- Capacity impact comparison
CRP sits between planning recommendations and optimized scheduling.
- MRP planned-order load checks
- Exception feed to APS
- Capacity signoff before release
- Planner notes preserved across handoff
CRP FAQ
Capacity Requirements Planning — questions buyers actually ask.
What problem does Capacity Requirements Planning solve?
CRP makes sure the schedule MRP just produced is actually runnable. NexliOne CRP shows hour-by-hour load per work center, highlights overloads before they hit the floor, and lets planners shift load to alternative routings or re-balance the schedule.
Does NexliOne CRP show hour-by-hour load profiles per work center?
NexliOne is designed to support this workflow. Time-bucketed load is overlaid against capacity with overload highlighting and drill-through to the underlying work orders. Scenario overlays let you compare the as-is plan to a proposed change.
Can NexliOne CRP enforce skill-based and tooling constraints?
NexliOne is designed to support this workflow. Calendar-aware finite loading respects skill matrices and tooling availability — operations don't schedule onto a work center when the qualified operator or required tool isn't there. Predecessor enforcement holds the routing sequence.
How does NexliOne CRP highlight and resolve overloaded work centers?
Overloads surface with both numeric variance and visual overload bars in the load profile. Alternative routing suggestions propose where the load can shift; planners commit the change directly from the CRP view.
How does CRP differ from APS in NexliOne?
CRP focuses on visibility — does the plan fit the capacity. APS focuses on optimization — generating the best feasible schedule given constraints. CRP is faster to run and useful for daily/weekly planning; APS is what you reach for when you need an optimized schedule across the network.
Get started
Ready to evaluate Capacity Planning?
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.