FSM and RSH in comparison – planning with perspective.
08 January 2026
SAP Field Service Management (SAP FSM) takes a different route. The solution is cloud-based and designed for service and maintenance operations – especially where travel times, qualifications, and customer communication play a major role.
On the planning board, you don’t just see work orders, but also see service calls and activities for each technician. Three planning patterns work hand in hand:
Manual planning
Dispatchers drag and drop activities onto technicians and time slots. In the daily or weekly view, this creates a clear to-do list for each technician.
Semi-automated planning
For an individual job, the system can propose “suitable technicians” with a single click – for example based on distance and qualifications. For a larger number of activities, you can place them in a queue and let the system distribute them to technicians according to defined rules.
Fully automated planning
Volumes of work that can be easily standardized can be scheduled automatically overnight. In the morning, the dispatcher reviews the result, makes adjustments, and releases the jobs.
The key difference compared to MRS: SAP FSM is driven by a rules engine that you, as the customer, can control. You define whether qualifications, distance, or earliest possible start are weighted more heavily. Training, absences, and working hours are taken into account as well. And via Business Rules you can define additional triggers or follow-up actions (e.g., for high-priority jobs).
Particularly important for field service:
Qualifications are maintained on both technician and job level and actively checked.
Crews and teams can be modeled when jobs only make sense in specific combinations.
Tools and special equipment such as pallet jacks or special ladders can be planned, checked, and reserved.
Travel times are calculated and visualized on a map; the technician’s route can be adjusted as needed.
SAP Field Service Management therefore closes the gap where MRS was previously used as a dispatcher tool for service – now on a modern, cloud-ready platform tightly integrated with SAP S/4HANA.
From a customer perspective, the key takeaway from the webinar is that there is no single “MRS successor.” Instead, it pays to clearly sort your scheduling scenarios:
Do you primarily have internal maintenance, many assets, maintenance plans, and the need to bundle downtimes cleanly?
→ Then RSH is usually the core tool.Do you have a strong field service component, technicians at customer sites, significant travel times, and qualification requirements?
→ Then SAP FSM is typically the right choice.Do you have both in parallel – workshop maintenance and field service?
→ Then a combination of RSH and FSM is often the cleanest business solution.
A practical target architecture looks like this:
RSH handles rough-cut planning: which orders are due when, how loaded each work center is, what do campaigns and overhauls look like?
SAP Field Service Management takes over detailed planning at technician level: which person goes to which customer, with which qualification, via which route, and with which tool or piece of equipment?
The crucial point is this: the decision is not made in the tool, but in the process. This is exactly where Evora comes in. First, we analyze how MRS is used today, which functions are indispensable, and where custom extensions are hidden. Only then do we make a recommendation for RSH, FSM, or a combined solution – including an honest view of where customization efforts will be required.
Because the timeline is clear. Support deadlines for ECC and MRS are expiring, and S/4HANA projects require lead time. If you are actively using MRS today, you should decide early how capacity planning and dispatching will work in the future – not shortly before the cutoff dates.
For pure maintenance planning in SAP EAM, RSH can cover many typical MRS scenarios: planning board, capacity leveling, asset view, and operation dependencies. Typical field service functions such as skill logic or map views, however, are not its focus.
FSM has different priorities: service calls, activities, automatic dispatching, qualifications, crews, tools, maps, and routes. It is not a 1:1 clone of MRS, but a modern service scheduling solution. You will find some MRS capabilities again, others in a different form, and some are simply no longer there.
Yes. Many customers use RSH for medium-term planning of work centers in maintenance and SAP FSM for operational dispatching in field service. It is important to clearly define interfaces and responsibilities to avoid duplicate data maintenance.
Almost every MRS system has project-specific features: Z-tables, additional logic, custom cockpits. As part of the transition, these need to be identified. Then you decide whether there is a standard function in RSH or FSM, whether an extension is necessary, or whether you consciously retire certain features.
Experience shows: less from technology, more from process clarification. Who plans what, with which planning horizon, at what level? Who is responsible for the final technician assignment? What is the current data quality in SAP EAM, and where does cleanup need to happen first?
Initially, the UI changes: different planning boards, different terminology (activities instead of requirements), different filter options. In many projects, the transition is also a good opportunity to sharpen roles, responsibilities, and planning principles – which relieves dispatchers in the long run but requires guided change management at the beginning.
Evora supports the entire journey: analyzing current MRS usage, defining the target architecture with RSH and/or SAP Field Service Management, prototyping in the system, piloting, and rollout. Throughout, business requirements and technical implementation are closely aligned so that the new solution works in day-to-day operations – not just on paper.