Capacity-Constrained Supply Plan with Component Shortage
A discrete manufacturer runs a weekly supply plan in Oracle Cloud SCM for two assembly plants. Plant A builds 8,000 units per week of a subassembly; Plant B can build 5,000 but is not currently planned. A key component has a 6-week lead time and a single approved supplier. Marketing forecasts 12,000 units for the next 8 weeks, while the constrained plan shows 9,200 achievable. The plan recommends expediting 1,800 components at a premium and moving 600 units of production to Plant B, but the transfer would add 4 days of transit and Plant B has a different routing. Customer priority tiers are A (contractual, 70%), B (strategic, 20%), and C (spot, 10%). Safety stock is 1,200 units and is included in the plan. The planner notices that the plan consumes the forecast at the item level but not at the customer tier level.
1. Why does the plan recommend both expediting components and transferring production to Plant B instead of choosing only one lever?
Read the worked answer
The two recommendations address different constraints, so treating them as alternatives would miss the real bottleneck.
- Component supply limits the build even if assembly capacity exists. The 6-week lead time means the 1,800-unit expedite is the only way to close part of the near-term component gap. Transferring more production to Plant B does not create components.
- Assembly capacity limits Plant A to roughly 8,000 units per week. The gap between 12,000 demand and 9,200 achievable is 2,800 units. Plant B has 5,000 units of unused capacity, but the plan moves only 600 because the 4-day transit and different routing make additional transfers infeasible within the response window or too costly relative to the component constraint.
- The plan is therefore solving a multi-constraint problem: expedite relieves the component constraint, while a limited transfer relieves the capacity constraint. If the planner canceled the transfer, Plant A would still be capacity-bound; if the planner canceled the expedite, Plant B would still be component-starved.
The correct judgment is to validate the expedite cost against the value of priority-A demand and to confirm that Plant B can actually build the routed variant before releasing either recommendation.
2. Available supply is 9,200 units against 12,000 units of demand. How should the planner allocate the 2,800-unit shortfall across customer tiers, and what role should safety stock play?
Read the worked answer
Start by converting tier percentages into units: A = 8,400, B = 2,400, C = 1,200. With 9,200 available, a priority-based allocation fully covers A (8,400) and leaves 800 for B; C receives zero unless supply improves.
That arithmetic is only the starting point. The planner should check firm orders versus forecast within each tier. If A's 8,400 includes forecast but only 7,000 is firm, the planner should not reserve phantom demand ahead of firm B orders. The allocation rule should use demand priority and firm-order status, not tier percentage alone.
Safety stock of 1,200 is already inside the plan. Releasing it would raise available supply to 10,400, but it also raises the risk of missing A's later orders. A defensible judgment is to release safety stock only for confirmed A orders with penalties, and to keep the rest as buffer because the component lead time is 6 weeks.
Finally, the planner should document the allocation and communicate it to sales. A plan that silently starves C is acceptable only if the business has explicitly decided that spot demand is the shock absorber.
3. The plan consumes forecast at item level but not at customer tier level. What configuration changes would make the plan more useful for this allocation decision?
Read the worked answer
The missing tier-level consumption prevents the planner from seeing which priority class actually has unfilled demand. The planner should introduce a demand class at the sales order and forecast level so that forecast consumption and allocation can be evaluated by tier rather than only by item.
Specific changes to consider:
- Assign demand classes A, B, and C to customers or order types, then use demand priority rules in the plan so that constrained supply is allocated in the intended sequence.
- Set forecast consumption to respect the demand class; otherwise a C order can consume A forecast and distort the shortage picture.
- Review the sourcing rule for Plant B. If transfers are intended as a regular lever, the rule needs the correct transfer lead time and routing so the plan does not understate the 4-day transit.
- Revisit component safety stock. A 6-week lead time and a single approved supplier justify a higher buffer than 1,200 units if expedite premiums are unacceptable.
- Add a plan exception for capacity overload at Plant A and for component shortage so the planner sees both constraints separately.
The test is whether the next plan run can answer 'how much A demand is at risk?' without manual spreadsheet work. If not, the configuration is still too coarse.