Project capacity planning compares the effort demanded by network activities with the capacity available from people, work centres and equipment. SAP Project System can calculate activity capacity requirements when suitable work-centre information and formulas exist, helping planners identify overloads before committing to dates.
Why schedule feasibility is not enough
Two project teams can each present a sensible sequence but depend on the same specialist in the same week. Capacity planning asks whether the resource can do the work at the planned time. Ignoring the question leads to missed milestones, hidden overtime and unreliable commitments even if the original activity network was logically correct.
Work centres connect effort to capacity
In SAP Project System, internal-processing network activities can refer to work centres. Work-centre capacity and scheduling data determine how requirements are calculated. SAP documentation notes that without the relevant formula, scheduling may not generate a capacity requirement for an activity. Missing requirement data is not evidence that the team has spare time.
A cross-functional resource review
The project lead provides delivery priorities, the resource owner knows genuine availability and the scheduler checks timing. Together they examine planned work, capacity by period and the effect of competing assignments. They should agree on skill constraints and calendar assumptions before requesting more hours or moving a milestone.
Availability changes over time
Nominal staffing does not equal effective availability. Work calendars, shifts, absences, maintenance and concurrent assignments affect what can actually be delivered. SAP capacity data can distinguish personnel, machine and other capacity categories. The chosen planning model, work-centre assignments and requirements formulas should be checked before interpreting utilization as business truth.
Illustrative overload: 44 hours of demand
Suppose an integration team has 36 available specialist hours in the upcoming week, while active project activities request 44 hours. The eight-hour overload is a planning conflict, not a command to work unpaid overtime. Teams might sequence one task later, arrange qualified cover, reduce scope or negotiate the milestone; each decision has a cost and owner.
Workforce assignment adds another level
Work-centre totals do not always reflect an individual person’s commitments. SAP workforce planning supports allocation to personnel resources for internally processed project activities when the required HR and project setup exists. The exact integration and planning granularity are implementation-dependent. Ask whether the project allocates named people, pooled teams or machines.
Common errors to avoid
A flat weekly average can hide a two-day peak. Skills cannot always be swapped one-for-one. An unassigned activity can still require genuine work, while a resource shown as available may already be committed elsewhere. Use verified calendars, track competing work and distinguish a forecast from confirmed capacity before making a delivery promise.
Consultant thinking: compare demand to actual supply
Ask what activity work quantity, available capacity and period have been used. Check for missing work-centre formulas before believing a zero requirement. Record overloading by skill and period, agree which project has priority, and recheck the consequence of any proposed date change.
Read Project Scheduling, Network Activities, Project Planning Board, Work Breakdown Structure, and the SAP PS / EPPM hub.