Resource Scheduling (RSH) in SAP S/4HANA maintenance

Resource Scheduling — often shortened to RSH and delivered as scope item 43R — gives maintenance planners a capacity, utilization and dispatch view at work-center level, on top of standard planning. It adds a scheduling board and KPIs where balancing shared resources is a recurring problem; smaller, stable plants usually don't need it.

What RSH adds

Standard SAP planning gets work ready; Resource Scheduling helps you balance and dispatch it. For maintenance planners it provides:

• KPI views per work center (load, readiness, schedule situation).
• A scheduling board to see who does what, and when.
• Utilization views to spot over- and under-loaded work centers.
• Dispatch of work to technicians or crews.

It is partly a process change, not just an extra app: planners and supervisors have to trust the board enough to stop "shadow planning" in spreadsheets.

When clients need it

Resource Scheduling earns its place when capacity balancing is a weekly pain, typically with:

• Larger maintenance teams.
• Shared resources that create frequent conflicts.
• Dispatch decisions that change daily or weekly.
• A management need for utilization transparency.

It needs mature data to pay off — credible work-center structures, durations, and calendars. Without those, the board shows noise.

When standard planning is enough

Stay with simpler standard planning when the resource base is small and stable, dispatch complexity is limited, capacity conflicts are rare, or data maturity is still low. Adding a scheduling board to a plant that doesn't feel a scheduling problem creates overhead without value.

Dispatching choices

Introducing RSH forces a few operating-model decisions: central versus local dispatch, dispatching to a named person versus a generic crew, and a day- versus week-level horizon. Clear ownership, stable calendars, and visible exceptions are what make dispatch decisions stick.

Common questions

Is RSH the same as standard maintenance scheduling? No — standard scheduling sets dates; Resource Scheduling adds capacity balancing, utilization, and a dispatch board at work-center level.

Which scope item is it? 43R (Resource Scheduling) in SAP S/4HANA Asset Management.

Do we need it from day one? Usually not. Start standard; add Resource Scheduling when dispatching is a real, recurring control problem.

---

Related: SAP EAM scope items · planning buckets · the maintenance order phase model. Want help deciding? Explore our SAP PM training.