Rough-cut capacity planning is the feasibility check that sits between a master production schedule and the detailed material plan. It answers one question before anyone commits materials or releases orders: can the critical resources actually deliver the schedule the master scheduler just wrote? APICS/ASCM defines RCCP as the process of converting the master production schedule into requirements for key resources, often including labor, machinery, warehouse space, suppliers’ capabilities, and in some cases money (APICS Dictionary, via Number Analytics). The Institute of Business Forecasting frames it the same way: translate the MPS into requirements for key resources, then compare against available capacity to confirm the schedule is achievable (IBF glossary).
RCCP is deliberately coarse. Oracle’s capacity documentation calls it a gross capacity planning technique that does not consider scheduled receipts or on-hand inventory when calculating capacity requirements (Oracle Capacity Help). That is the point. It trades precision for speed so the plan can be validated and renegotiated while there is still time to change it.
Where RCCP sits in the planning hierarchy
Capacity gets validated at three levels, each tied to a different planning level, horizon, and degree of detail. The pattern is the same at every level: derive required capacity, compare to available capacity, resolve the gap.
| Process | Tied to | Horizon | Detail | What it validates |
|---|---|---|---|---|
| Resource Requirements Planning (RRP) | Production plan / S&OP (aggregate, product-family) | Long range, often 12+ months | Lowest | Does the aggregate plan fit long-lead resources (plant, major equipment, headcount)? |
| Rough-Cut Capacity Planning (RCCP) | Master Production Schedule (MPS) | Medium range, roughly 4 to 12 weeks and out | Key resources only | Is the MPS feasible at bottleneck work centers, key labor, key suppliers? |
| Capacity Requirements Planning (CRP) | MRP (detailed orders) | Short range | Highest, every work center | Are the actual released and planned orders feasible hour by hour? |
RRP is the highest-level check and works off the aggregate production plan set in the S&OP and IBP Process, confirming long-lead resources before volumes are locked. CRP is the detailed counterpart that runs after MRP explodes the schedule into orders. It considers scheduled receipts and on-hand inventory and uses routings and time standards to translate open and planned orders into hours of work by work center by time period (Reid & Sanders, Operations Management, 5th ed.). The practical split: RCCP shows whether the program is broadly feasible across a handful of constraints, CRP shows exactly which work center overloads in which week (Symestic).
The three RCCP techniques
The techniques differ in how much routing and timing detail they carry. More detail means more accuracy and more maintenance.
1. Capacity Planning Using Overall Factors (CPOF)
The least detailed method. CPOF uses historical ratios plus the MPS to estimate load: take the total standard hours per unit, apply historical percentage splits to allocate those hours across work centers, and multiply by MPS quantities (Software Connect).
- Data needed: MPS quantities, total time per unit, historical share of load by work center.
- Tradeoff: Fast and easy, but insensitive to product mix. If the mix shifts away from the historical average, the per-work-center split is wrong (Smartsheet).
2. Capacity Bills (Bill of Capacity / Bill of Resources)
Also called the bill-of-labor approach. It builds a direct link between MPS quantities and the hours each end product consumes at each work center, rather than relying on an overall historical ratio. Required hours per resource = sum over products of (capacity bill factor x MPS quantity) (Smartsheet).
- Data needed: A bill of capacity per product (standard hours per unit at each key work center); MPS by product.
- Tradeoff: More accurate than CPOF and responsive to product mix, the common choice for multi-product plants. It still ignores when in the lead time the load falls.
3. Resource Profiles
The most detailed RCCP method. It takes the capacity bill and time-phases it across the lead time, offsetting each requirement to the period in which the work is actually performed rather than dumping all load in the completion period (Smartsheet).
- Data needed: Everything the capacity bill needs, plus lead-time offsets per operation.
- Tradeoff: Highest accuracy for timing, highest maintenance. Worth it when lead times are long enough that load lands in earlier periods than the MPS due date suggests.
Inputs, outputs, and the bottleneck focus
Inputs: the master production schedule, a definition of the key/critical resources, and standard hours or rates per unit at those resources.
Output: required versus available capacity at each key resource, usually expressed as a capacity load ratio: required capacity / available capacity. A ratio above 1.0 means the schedule asks for more than the resource can deliver (Smartsheet).
RCCP intentionally checks only key resources, not every work center. Checking everything is CRP’s job and requires the full MRP order set. RCCP focuses on the constraints that govern throughput, the bottleneck work centers, scarce skilled labor, gating equipment, and capacity-constrained suppliers, because under Theory of Constraints logic the bottleneck sets the output of the whole system. If the constraint can carry the plan, the non-constraints almost always can. Validating a few resources fast beats validating all of them slowly while the schedule is still moveable.
Worked example (illustrative)
A plant master-schedules two products, P1 and P2, and checks the Press work center, its known bottleneck, for one week. Numbers are illustrative.
Capacity bill (standard press-hours per unit):
- P1: 0.50 hr/unit at Press
- P2: 0.80 hr/unit at Press
MPS for the week: P1 = 160 units, P2 = 80 units.
Required capacity (load):
- P1: 160 x 0.50 = 80 hr
- P2: 80 x 0.80 = 64 hr
- Total Press load = 144 hr
Available capacity: 2 presses x 16 hr/day (two shifts) x 5 days = 160 gross hr, then x 0.90 utilization x 0.95 efficiency = 136.8 effective hr.
Capacity load ratio = 144 / 136.8 = 1.05. The Press is overloaded by about 5 percent for the week. A planner seeing this would level some load into an adjacent week, add overtime or a third shift, or send the MPS back for adjustment before releasing it to MRP. The single-method calculation form (hours = units x hours per unit, summed) mirrors Oracle’s routing-based RCCP, where 10 units at 24 hr/unit yields 240 required hours (Oracle Capacity Help).
When RCCP matters and how it fails
RCCP matters most when capacity is tight, the product mix is volatile, or a single constraint governs the plant. It runs after demand is shaped in Demand Planning and Forecasting and the MPS is drafted, but before MRP commits materials. Skipping it produces the classic failure mode: an overstated master schedule that orders more materials than the production resources can complete, which builds shop-floor queues and missed due dates (Smartsheet).
Common failure modes:
- Wrong constraint. Checking a resource that is not the real bottleneck. RCCP is only as good as the choice of key resources.
- Stale factors. CPOF historical splits or capacity-bill standards that no longer match current routings or mix.
- Treating the ratio as a hard yes/no. A load ratio near 1.0 leaves no room for variability; plan to a target utilization below 100 percent.
- No feedback loop. RCCP that flags an overload but does not feed a renegotiation of the MPS or available capacity adds no value.
APICS/ASCM terminology
This is standard APICS CPIM and Master Planning of Resources content. The APICS body of knowledge defines the three-tier capacity hierarchy explicitly: resource requirements planning at the aggregate level, rough-cut capacity planning at the master-scheduling level, and capacity requirements planning at the MRP level (Number Analytics summarizing the APICS Dictionary). The three RCCP techniques, CPOF, capacity bills, and resource profiles, are the named methods in that same framework.