SAP has de-prioritised RSH, Resource Scheduling for S/4HANA Asset Management, withdrawing active investment and roadmap development.
For organisations running field operations on RSH today, a decision that has been sitting at the bottom of the backlog just moved up to the top of the agenda.
If your operations run on MRS in SAP ECC, a separate clock is ticking: SAP’s maintenance for MRS on ECC ends in 2027. SAP has been explicit about its intent — the company is “not actively positioning this solution for new customers.”
Two out of three SAP scheduling tools are no longer part of SAP’s long-term strategic direction. One remains under active investment.
The Three-Product Landscape and Why Two No Longer Have a Future
To understand what this means for your organisation, it helps to see where SAP arrived and how.
SAP offered three distinct resource scheduling products:
- MRS (Multi-Resource Scheduling) — The legacy scheduling engine, primarily used with SAP ECC. Maintenance ends in 2027. SAP no longer positions it for new deployments.
- RSH (Resource Scheduling in S/4HANA Asset Management) — The S/4HANA-era product for asset-intensive industries. De-prioritised, with no active roadmap.
- FSM (Field Service Management) — SAP’s cloud-native field service platform. Active, AI-enabled, and named a Leader in the IDC MarketScape for the second consecutive year.
MRS, RSH, and FSM: A Direct Comparison
Understanding why FSM is the forward path requires understanding what each product was actually designed to do — and where each falls short.
Product Overview
| MRS | RSH | FSM | |
| Full name | Multi-Resource Scheduling | Resource Scheduling for S/4HANA Asset Management | Field Service Management |
| Platform | SAP ECC (on-premise) | SAP S/4HANA (on-premise or cloud) | Cloud-native SaaS |
| UI framework | SAP GUI / Web Dynpro | SAP Fiori | Modern web + native mobile app |
| Primary users | Maintenance planners | Maintenance planners | Dispatchers, technicians, customers |
| SAP status | Maintenance ends in 2027 | De-prioritised, no active roadmap | Active investment, AI roadmap |
| New deployments | Not recommended | Not recommended | Recommended |
Scheduling Capabilities
| Capability | MRS | RSH | FSM |
| Scheduling scope | Multi-resource across work centres | Work centre capacity (medium/long term) | Individual technician, daily/hourly dispatch |
| Planning horizon | Medium-term | Medium to long-term | Operational — today through next weeks |
| Planning model | Work centres and capacity | Work centres, assets, downtime windows | Technicians, skills, routes, parts, customer slots |
| Technician skill matching | Limited | None | Native, AI-assisted |
| Travel time optimisation | None | None | Automatic route calculation |
| Asset/downtime bundling | Yes | Yes (stronger) | Limited |
| Crew/team scheduling | Limited | No | Yes |
| Contractor workforce | No | No | Yes |
| Auto-scheduling / AI dispatch | None | None | Yes — Joule AI assistant, auto-scheduling engine |
Field Execution and Customer Layer
| Capability | MRS | RSH | FSM |
| Mobile field execution | None | Limited Fiori apps | Full native mobile app (iOS/Android), offline-capable |
| Offline operation | No | No | Yes — full offline sync for field technicians |
| Digital checklists/Smartforms | No | No | Yes |
| Customer communication | None | None | Appointment portals, arrival windows, status updates |
| Parts/truck stock visibility | Basic (ECC MM) | S/4HANA MM | Native parts reservation + truck stock tracking |
| Real-time dispatch board | Basic planning board | Fiori planning board | Modern Gantt + map view |
| Reporting | ECC standard reports | S/4HANA Analytics | Built-in FSM analytics + Query API |
Integration and Deployment
| Capability | MRS | RSH | FSM |
| ERP dependency | ECC required | S/4HANA required | ERP-agnostic (ECC, S/4HANA, Business One, or standalone) |
| Integration method | ECC native | S/4HANA native (Fiori/OData) | SAP BTP + Cloud Integration iFlows + Cloud Connector |
| Standalone deployment | No | No | Yes |
| S/4HANA migration required? | N/A | Yes | No |
FSM is Not a Replacement – It is a Platform
This distinction matters more than it might seem, especially for leadership making investment decisions.
A replacement covers the same scope as what it replaces, just on newer infrastructure. FSM is not that.
FSM covers the full field service lifecycle: planning, dispatch, mobile execution, parts management, and analytics — in one environment. RSH handled one slice: scheduling. Everything else (the technician’s experience in the field, the customer’s visibility into when someone will arrive, the parts that need to be on the truck, the data captured at the job site) lived in other systems, in spreadsheets, or in undocumented operational processes.
The real ROI comparison is not RSH versus FSM. It is RSH plus all the adjacent tools, manual processes, and institutional knowledge that compensate for what RSH cannot do—unlike FSM, which operates as a single operating environment.
What FSM does that RSH never attempted:
Mobile-first field execution. FSM provides guided workflows for technicians on mobile devices, including full offline capability. Jobs don’t stall because a technician is in a basement or a remote facility without a signal. The technician gets the assignment, checklist, parts information, and customer details on their device. Data flows back to the system without a dispatch call or manual entry back at the depot.
Contractor workforce support. FSM supports both employed and contractor workforces within the same scheduling and dispatch environment. For organisations with mixed workforce models — most of which run significant field operations — this eliminates the need for parallel systems that never quite stay in sync.
Customer communication. RSH has no native customer-facing layer. FSM puts customers in the loop — arrival windows, technician assignments, job status updates — as part of the same platform. That is a service revenue and customer retention capability, not just an operational convenience.
Real-time operational visibility. Leadership and operations managers see what is happening across the field in real time, not in yesterday’s batch report. That visibility changes how quickly organisations respond to delays, escalations, and capacity shifts — as well as what conversations between operations and leadership are even possible.
None of these is future roadmap items. They are live capabilities in the current platform.
Key Architectural Characteristics
| Aspect | Detail |
| Deployment model | SaaS — SAP-hosted, single tenant on isolated cluster |
| Release cadence | Monthly releases (e.g., 2505 = May 2025) |
| Mobile platform | Native iOS + Android; full offline sync |
| ERP coupling | Loosely coupled — FSM operates independently of ERP upgrade cycles |
| Integration middleware | SAP BTP Cloud Integration (iFlows) for all ERP backends |
| On-premise bridge | SAP Cloud Connector — runs as an on-premise agent linking ECC/S/4HANA to BTP |
| Data replication | Data Replication Framework (DRF) distributes master and transactional data |
| API surface | REST APIs + Query API for reporting; Webhooks for event-driven integration |
| AI layer | Joule embedded in dispatch workflow; auto-scheduling optimisation engine |
| Scheduling algorithm | Constraint-based with skill, location, parts, availability, route optimisation. |
AI Has Arrived in FSM and It’s Already Transforming Dispatch
Leadership evaluating enterprise software has become appropriately sceptical of AI claims. Most vendor AI announcements describe capabilities that are 18 months away, require custom implementations, or do something so narrow that calling it “AI” is a marketing decision rather than a technical one.
FSM’s AI is different, and the proof is specific.
In the FSM 2505 release, SAP shipped Joule for Dispatchers — an AI assistant embedded directly into the dispatch workflow. Dispatchers use natural language to find activities, identify the best-matching technicians, apply scheduling policies, and assign or release work. The interaction is not “generate a summary.” It is “find the best available technician with the required certification, closest to this job site, with the earliest opening in their schedule” — and Joule executes that against live scheduling data.
The operational implication is significant. Dispatchers currently managing dozens of variables simultaneously — technician skills, locations, parts availability, customer priority, travel time — make dozens of judgment calls per hour. Joule compresses the research phase of every one of those decisions. An experienced dispatcher with AI-assisted tooling makes better decisions faster, with less cognitive load. Across hundreds of dispatches per day for a large field operation, that compounds.
There is a talent risk dimension too. Many organisations have tenured dispatch staff who carry institutional knowledge that isn’t documented anywhere. Joule narrows the gap between what a veteran dispatcher knows intuitively and what a newer team member can execute — which is worth quantifying before that knowledge walks out the door.
SAP’s investment in these capabilities is not happening without external validation. SAP was named Leader in the IDC MarketScape for AI-Enabled Field Service Management Applications 2025 — for the second consecutive year. IDC’s framing is direct: “AI-enabled tools are revolutionising field service management, transforming reactive operations into predictive excellence.”
No ERP Transformation Required
One concern that surfaces in nearly every leadership conversation about FSM: “Does this require us to migrate to S/4HANA first?”
No — and that changes the ROI calculus significantly.
FSM runs independently of SAP’s Cloud ERP. It integrates with SAP ECC, S/4HANA, and SAP Business One — using SAP’s Business Technology Platform as the integration layer for ECC environments. Organisations on ECC can adopt FSM now, years before any S/4HANA migration appears on the planning horizon. The two projects run on separate tracks and do not depend on each other.
Consider what this looks like in practice. An organisation running SAP ECC with a multi-year S/4HANA migration on the horizon can deploy FSM now, connect it to existing work order and asset management data, and run full AI-assisted dispatch — without touching the ERP at all. When the S/4HANA migration eventually arrives, it connects to an FSM environment that is already mature, already running production workflows, already embedded in how dispatchers and technicians operate. The modernisation phases naturally rather than landing as a simultaneous overhaul. That is how large organisations de-risk complex infrastructure change: one layer at a time, each stage building on what came before rather than replacing everything at once.
This matters because the default assumption in most leadership conversations — “we can’t change field service scheduling until we sort out the ERP roadmap” — is factually wrong. FSM does not need a big-bang transformation as a prerequisite. It connects to the system you already have, and it delivers value while that system is still in place.
For organisations with complex multi-system environments, this difference is not minor. It separates an 8-week project from a 3-year program.
The ODS Path: From POC to Production in Under Three Months
Knowing FSM is the right platform is different from knowing how to get there without organisational disruption. Implementation risk is real. Large enterprise software projects that exceed scope, budget, and timeline have earned the skepticism leadership brings to them.
On Device Solutions (ODS) reduces that risk.
ODS is an SAP Gold Partner with 15+ years of field workforce expertise and two structured deployment tracks built specifically to de-risk FSM adoption:
Track 1: 4-Week Proof of Concept. In four weeks, ODS delivers a working FSM environment configured for your organisation’s specific workflows. Dispatchers can use it. Technicians can use it. Leadership can see it. The POC runs on your use cases and your workforce model — not generic product demos. Stakeholders see a real system, not a slide deck.
Track 2: 8–10 Week Fixed-Scope Go-Live. For organisations ready to commit, ODS delivers full production deployment in 8–10 weeks. Fixed scope means the timeline and cost are defined from the start — not estimates that expand when complexity surfaces mid-project. For leadership building the internal investment case, a defined cost ceiling and timeline make it through budget approval in a way that open-ended estimates do not.
Together, these tracks mean an organisation starting a POC today could have FSM in production within a single quarter.
On Device Solutions brings more than project management. Fifteen years of field workforce implementations mean they have already solved the problems that make these projects hard: workflow redesign for dispatch teams who have their own way of doing things, change management for technicians who are not power users, integration with legacy work order and asset management systems, mobile rollout logistics for field staff who may be geographically dispersed. Leadership does not have to solve those problems. ODS brings experience from addressing these challenges across previous field service deployments.
If you’re currently running MRS or RSH, now is the time to evaluate your long-term field service strategy. ODS can help you assess your current landscape, identify risks, and determine whether FSM is the right fit for your operational model.
