SAP FSM vs. RSH: Resource planning with a field service lens

Anyone responsible for scheduling work sits between two worlds: internal maintenance focused on work centers and assets – and field service with customers, travel times, and skills. SAP Field Service Management (SAP FSM) and Resource Scheduling (RSH) are positioned exactly at this intersection. In this article, we look at both solutions strictly from a field service perspective and clarify when each one fits – and when the combination delivers the greatest value.

Many companies are coming from the MRS world – a long-established dispatching tool moves into the background in an SAP S/4HANA landscape. Today, two solutions are in focus:

• RSH as an add-on in SAP EAM for medium- and long-term capacity planning

• SAP FSM as a cloud solution for operational, fine-grained dispatching

So the question is not: “What replaces MRS?” but rather: Which requirements are covered by RSH? Which ones are covered by FSM? And how do the two work together in a sensible way?

RSH thinks in terms of work centers, capacities, and assets. FSM thinks in terms of technicians, skills, tools, routes, and customer communication. For internal maintenance, RSH is often sufficient – but in field service, organizations far more often rely on FSM.

RSH is embedded directly in S/4HANA Asset Management and focuses on structural planning: work centers, asset hierarchies, and long-term utilization.

Capacity control by work center

On the planning board, schedulers see at a glance:

• how high the utilization of each work center will be over the coming weeks

• which work orders can reasonably be shifted

• how changes immediately impact capacity and dates

This makes RSH an excellent fit for medium- and long-term planning: maintenance, inspections, or campaigns that are known early and can be incorporated into weekly planning in a structured way.

Short-term planning is possible, but it’s not the core use case. RSH is primarily used as a rough-cut planning tool.

Asset view and dependencies

RSH also shows the technical structure of assets, planned downtimes, and existing work orders. In practice, this means:

• downtimes become transparent

• multiple activities can be bundled into a downtime window

• dependencies between operations can be maintained directly

For internal maintenance processes, this perspective is a clear advantage – especially for large plants or planned overhauls.

You can find more details on our solution page for SAP EAM and resource planning.

In field service, priorities shift significantly: the main resource is not the work center but the person – including qualifications, location, team assignment, and tool requirements. This is exactly where SAP FSM plays to its strengths.

Qualifications, teams, and tools

FSM works with a resource model that is essential in field service:

• Qualifications are checked before a job is assigned

• Crews and teams can be formed and scheduled flexibly

• Tools and special equipment can be reserved – with built-in conflict checks

If two dispatchers try to allocate the same special tool at the same time, FSM detects that immediately. For service organizations with complex equipment, this is a crucial advantage.

Automatic dispatching, travel times, and map view

The planning board in FSM is designed for operational dispatching:

• travel times between jobs are calculated automatically

• map views display routes and customer locations

• semi- and fully automated planning assigns jobs based on defined rules

• AI-powered suggestions propose suitable technicians

For service organizations with a high volume of calls and tight deadlines, this functionality is hard to live without – and it’s not part of RSH’s scope.

A deeper overview is available on our SAP Field Service Management solution page.

From a field service perspective, three standard scenarios emerge.

1. Classic internal maintenance

Here, RSH is often enough:

• planning along work centers

• using existing downtime windows

• capacity steering with a weekly and monthly view

FSM only becomes relevant when additional requirements come into play, such as skills logic, route optimization, or customer communication.

2. Field service with travel times and qualifications

As soon as jobs take place mainly at the customer site, there are strong arguments for SAP FSM:

• travel time becomes a key factor

• qualifications determine whether a technician can take on a job

• customers expect appointment proposals and status updates

• external service providers need to be integrated

RSH does not cover these needs.

3. Hybrid model: RSH + FSM

In many companies, the combination is the cleanest solution from a business perspective:

• RSH ensures work centers, downtimes, and internal capacities are planned in a structured way

• FSM takes over detailed dispatching at technician and routing level

For organizations that run both internal maintenance and field service, this model is particularly attractive. Evora supports exactly these scenarios on a regular basis – from target architecture through implementation to stable operations as part of our SAP Application Management Services (AMS).

You can find more information in our offerings around resource planning and SAP FSM.

If you’d like to see how SAP FSM and RSH work together in real-world scenarios, we recommend our on-demand webinar. We showcase realistic planning scenarios, the difference between rough-cut and detailed planning, and concrete recommendations for organizations that still work with MRS or mixed tool landscapes today.

👉 On-demand webinar “Experience SAP FSM & RSH live: modern resource scheduling in practice”:
https://www.evorait.com/de/events/sap-fsm-rsh-live-erleben-moderne-einsatzplanung-in-der-praxis/