Evaluating capacity load

Capacity evaluation answers simple questions: which work centers are overloaded, when, by how much, and which orders cause it? SAP S/4HANA offers several tools. In current releases the main one for planners is the Fiori app Manage Work Center Capacity.

Manage Work Center Capacity

According to SAP Learning, the app's overview lists the selected work center capacities with aggregated figures for an evaluation horizon: maximum load, time of the first overload, backlog of overdue orders, total requirements, average load, time of first critical load, overall percentage load and total available capacity. A chart shows utilization per period, colored for normal load, critical load and overload, and the thresholds for those bands can be set individually.

From the overview you navigate to a single work center. The detail view shows the chart and the pegged requirements: the operations and orders that make up each period's load. It also shows the work center's shifts, which a planner can change interactively, for example to add an extra shift in a peak week.

Other evaluation tools

A practical weekly routine for the Detroit planner: open the overview for the plant’s critical work centers and the next four to six weeks; sort by time of first overload; drill into the earliest one; read the pegged orders; then decide between moving work, adding capacity or escalating. Record the decision in the order or the meeting notes so that the next evaluation can be compared with it.

Evaluation is also where data quality shows up. A work center with no available capacity maintained will look permanently overloaded; a routing with standard values in the wrong unit will create absurd loads; an operation with a control key that should not be capacity-relevant will add phantom load. Treat strange numbers as master data findings first.

Walkthrough: the Monday capacity review

1. Open Manage Work Center Capacity with the variant "Detroit critical" (WIND-10, ASSY-10, TEST-10; horizon four weeks; daily buckets).
2. Sort by time of first overload. ASSY-10 is overloaded on Monday of week 2 at 122%.
3. Open ASSY-10 and read the pegged requirements: two production orders for CMC-ALT-100 and one planned order from MRP controller 101.
4. Check the backlog figure: one order from last week is overdue because it was built but never finally confirmed. Ask the supervisor to confirm it; the phantom load disappears.
5. For the real overload, decide: level (lesson 3), add a shift in the app, or escalate. Record the decision in the planning meeting notes.

Classic SAP GUI reports such as CM01 (load overview), CM07 (variable overview) and the capacity evaluations still exist in SAP S/4HANA Private Edition, which helps planners during the transition. SAP positions the Fiori apps as the target, and SAP S/4HANA Cloud Public Edition offers only the apps.