From MRS to SAP FSM and RSH: How to make your resource planning future-proof

Many companies have been planning their maintenance and service operations for years using SAP Multi Resource Scheduling (MRS). From a functional standpoint, this often still works – but strategically, the direction is clear: SAP is focusing on S/4HANA, the cloud, and new solutions for resource planning. Anyone using MRS productively today will, in the next few years, face the question: What comes next – and which option is the better fit for us: SAP FSM, RSH, or both?

That was exactly the focus of the webinar: we looked at the current state of MRS, positioned SAP Field Service Management (SAP FSM) and RSH, and outlined a pragmatic path from the current state to a future target architecture.

MRS was introduced as an SAP add-on in the mid-2000s and enhanced over many years. The last major release for S/4HANA comes from the 10.x line. With the S/4HANA strategy, however, SAP has clearly set the course:

• ECC customers: end of maintenance in 2027 – which also ends the comfortable environment for running MRS on the old platform.

• S/4HANA customers: have a bit more time, but MRS is clearly no longer at the core of the future roadmap.

At the same time, MRS systems in the real world are highly customized: custom logic, tailored cockpits, and complex master data routing. There is no such thing as a 1:1 migration to a new tool. The goal instead is to understand today’s processes and map them to the new building blocks:

• RSH for capacity and resource planning in SAP EAM on S/4HANA

• SAP Field Service Management for service and maintenance operations, especially in the field

Evora deliberately takes an analysis-first approach: Which functions do you use in MRS today? Which of them are business-critical? Where does RSH fit better, where SAP FSM – and where does a combination of the two make the most sense?

RSH (S/4HANA Asset Management for Resource Scheduling) sits directly in S/4HANA Asset Management and is clearly aimed at maintenance planners. The solution is Fiori-based, uses SAP EAM master data, and focuses on medium- and long-term capacity and resource planning.

In practice, it looks like this:

You start with a dashboard that visualizes key metrics:

• upcoming work orders in the next few weeks by priority

• work orders from recent months that have not yet been confirmed

• utilization of relevant work centers

• unassigned work, sorted by criticality

From there, you can jump into Fiori apps such as work center utilization control or into the maintenance planning board. In the planning board, you see:

• orders and operations along the timeline

• capacity utilization per work center per day/week

• visual highlighting of overload situations

You can drag and drop orders into different time slots or assign them to a second work center. RSH immediately recalculates utilization. This lets you make sure, for example, that a work center stays consistently between 70 and 90% utilization instead of spiking into the red.

Another building block is the use of scheduling plans: similar work orders (e.g., for an overhaul) are grouped into a defined time window. You define the start and end, let the system schedule, and can later analyze how well the plan matched reality. This is particularly useful for campaigns and bundled maintenance activities.

It’s important to note: RSH stays within the logic of internal maintenance – work centers, capacities, technical objects. For classic field service with customers, travel times, and qualifications, RSH alone is usually not enough.

SAP Field Service Management (SAP FSM) is the second pillar in the post-MRS landscape – but with a very different focus. It is a cloud solution designed to plan and control service and maintenance operations efficiently – including field technicians, travel times, and customer communication.

From a dispatcher’s perspective, daily work looks like this:

You work in a planning board with technicians (or resources) on the vertical axis and a time scale horizontally. Service jobs (service calls/activities) can be:

• assigned manually by dragging and dropping them to technicians and time slots

• assigned semi-automatically: SAP FSM suggests suitable technicians

• assigned fully automatically overnight using defined policies

The semi-automatic assignment uses rules you define, for example:

• Qualifications: Which skills does the activity require? Which technicians have them?

• Distance: How far is the technician from the customer site?

• Working hours: Does the job fit into the available time window? Are overbookings allowed?

• Priorities: Should breakdowns be scheduled before planned maintenance?

A key difference from RSH: qualifications and tools are embedded directly in the SAP FSM standard. Technicians have skills; jobs require skills; and the system checks during planning whether that is a match. Tools and special equipment such as pallet jacks or ladders can be assigned to a job, checked for availability, and reserved.

For field service, map integration is also critical:

• start and end points are derived from the technician’s home base and the customer address

• travel times are calculated and shown as gray blocks in the Gantt chart

• routes can be adjusted on the map, for example if a different sequence of jobs is more efficient

This is complemented by functions such as Crowd Service (integrating partners), Customer Self-Service (customers report issues and propose appointments), AI-based assistance, and standard dashboards, for example in combination with SAP Analytics Cloud. And of course, there is a dedicated mobile app enabling technicians to handle jobs, time, materials, and checklists.

The core message from the webinar: there is no single standard migration “MRS → Product X”. The path is always process-driven. Evora typically proceeds as follows:

First, we work out in detail how MRS is used today:

• Which planning level dominates – work centers, teams, individual technicians?

• How relevant are qualifications and travel times in reality?

• Which custom developments do you use in MRS – additional fields, special logic, cockpits?

On this basis, we derive a decommissioning recommendation:

• Scenario 1: RSH covers the essential requirements, for example in predominantly internal maintenance without strong field service.

• Scenario 2: SAP Field Service Management is the better option because field service and service customers are in focus.

• Scenario 3: A combination of RSH and FSM makes sense – rough-cut planning in RSH, detailed technician-level planning in FSM.

It is crucial to clarify early which MRS functions are truly indispensable – and where the transition is an opportunity to streamline overloaded processes. Evora brings experience from many projects with SAP EAM, SAP FSM, SAP Service and Asset Manager, and SAP Application Management Services. This helps ensure you don’t just introduce a new tool, but make your overall resource scheduling more robust.

If you’d like to see how companies are moving from MRS to modern planning approaches with SAP FSM and RSH, we recommend our on-demand webinar. We present typical target architectures, real migration scenarios, and proven approaches for phasing out MRS.

👉 On-demand webinar “Service – but with structure: from SAP MRS to SAP FSM”:
https://www.evorait.com/de/events/service-aber-mit-struktur-von-sap-mrs-zu-sap-fsm/