At Sapphire 2026, SAP gave one of its oldest service products a new name. SAP Field Service Management is now SAP Field Service and Asset Management, or FSA.
If you run maintenance on SAP PM and keep up with SAP news, you have probably seen the name go by and wondered what it means for you.
Is FSA a new product? Does it replace what you already run? Is it built for plant maintenance, or is it purely for customer service?
This article answers those questions in plain English, including what separates FSA from the other SAP acronyms it keeps getting confused with.
What SAP announced with FSA.
FSA is the next step for the product SAP used to call Field Service Management (FSM). SAP introduced it at Sapphire 2026 alongside its Autonomous Enterprise announcement, and it reaches customers with the 2605 release (scheduled for June 2, 2026).
The rename is the visible part of something larger.
In its FSA product announcement, SAP sets out the five planning and execution products it is consolidating into FSA:
- SAP Multi Resource Scheduling (MRS).
- SAP Field Service Management (FSM).
- SAP S/4HANA Asset Management for Resource Scheduling (RSH).
- SAP Cloud 4 Projects Resource Management (C4P RM).
- SAP Maintenance Scheduling and Optimization (MSO).
Each of those grew up solving one slice of workforce scheduling, resource optimization, or field execution. SAP now wants one layer instead of five with FSA.
The history of SAP FSM and FSA.
To understand why FSA is the product doing the absorbing, it helps to know where FSM came from.
In 2018, SAP acquired Coresystems, a Swiss field service software company, and brought its product into the portfolio as the cloud product we know as FSM. The goal was to strengthen SAP’s service offering, particularly alongside SAP Cloud for Customer.
That history explains a couple of things about FSA.
FSM was shaped around external service calls rather than plant maintenance and it looked different from the rest of the SAP portfolio, because it was not built there.
As the German-speaking SAP user group DSAG puts it in its assessment of the rename, the bolt-on architecture brought the problems you would expect: broken handoffs between processes, and document management that does not run end to end.
FSA appears to be SAP’s attempt to close those gaps.
What actually shipped with release 2605.
The information on SAP’s What’s New page on the 2605 release for the general component contains two things.
The first is a Workload and Capacity view, a new view in the Planning and Dispatching application. It lets schedulers compare workload against the capacity available from work centers, so the most important work gets scheduled first.
The second is updated terminology. SAP enriched the existing terminology and added wording for asset-centric scenarios.
Put in clearer terms, the terminology update means that FSA carries two parallel vocabularies, one service-centric and one asset-centric. In the asset-centric scenario, the labels change to the ones your team already knows from SAP PM: region becomes work center, problem type becomes maintenance activity type, activity becomes operation, and service call becomes work order.
Service-centric terminology is the default for every account. And at the time of writing, SAP's documentation says instructions for enabling the asset-centric terminology will be added soon, so the switch is documented before it is usable.
What is on the roadmap for FSA.
The real substance behind the rename will arrive gradually.
Here's what we know from SAP's roadmap statements and DSAG's assessment of them:
Resource planning from MRS, folded into FSA, with backlog planning to follow.
A Fiori redesign, so the interface stops looking out of place. The widely used FSM mobile app is being rebuilt on its existing technology rather than replaced, so teams keep the app they know.
Joule functionality and AI agents, step by step rather than in one release. The AI documented for FSA today is assistive: filtering, summaries, briefings, and Joule.
SAP Cloud ERP integration, with general availability of the full solution planned for Q4 2026.
An Asset and Service Assistant that turns alerts and anomalies into prioritized work, planned for Q3 2026.
What does SAP recommend you do?
What SAP recommends today is more interesting than the roadmap, and it is worth reading carefully if anyone is pressuring you to act. SAP’s product announcement sets out a recommendation and a future direction for each of the products it is absorbing.
If you run FSM, you do nothing. SAP says existing customers do not need to change their subscription or contracts, and that the new capabilities will be enabled free of charge in your existing tenant under the Planning and Dispatching tile.
If you run MRS on ECC or S/4HANA with the dispatching scenario, SAP recommends continuing to use it for “the time being.” SAP describes MRS as being in maintenance mode with no major enhancements planned, and says it is planned to be sunset by 31 December 2030.
If you run RSH, SAP says you can continue using it for work center capacity-based scheduling while you revisit your license transition and migration to FSA concepts. RSH will not receive roadmap updates after the S/4HANA 2025 FPS0 release, and SAP says a fuller FAQ on the future of RSH and MRS inside FSA is still being written.
So FSM customers get the new capabilities free of charge. MRS customers, on the other hand, need a cloud subscription to move to FSA. DSAG called it unacceptable that existing MRS customers would need another license simply to keep using functionality they already have, and said it expects SAP to give ground. Whether SAP does so is worth tracking.
FSA, FSM, SSAM, and MRS: which SAP product is which.
FSA grew up in customer service, and SSAM grew up in plant maintenance.
By now you are probably thinking SAP has several products that sound like they do the same job. Particularly, where does SSAM stand?
FSA grew up in customer service, and SSAM grew up in plant maintenance
The short version: FSA grew up in customer service, and SSAM grew up in plant maintenance. Here is the current 2026 landscape.
So does FSA replace SSAM?
No. SAP has confirmed that SSAM stays in the portfolio and continues to be developed, and has since set out a new release strategy for the app.
What FSA includes, and what costs extra.
“One execution layer” is one product name, but several subscriptions.
The feature scope description sets out the Cloud Services, and states that each one needs its own subscription:
- FSA base.
- FSA mobile, commercialized as part of SAP Mobile Execution and Dynamic Forms.
- FSA optimization option.
- FSA SME option.
- FSA Crowd Service add-on.
- FSA test tenant.
- FSA AI-assisted services, metered as SAP AI Units under SAP Business AI.
The new asset-centric planning capabilities land free of charge for existing FSM customers. The packaging around them does not change.
“One execution layer” is one product name, but several subscriptions.
So four things stand out if you are costing this for a maintenance workforce:
- Mobile sits outside the base. The app your technicians hold is its own subscription.
- AI is consumption-priced. The AI features are billed as AI Units rather than included.
- Scheduling intelligence is tiered. The base gives you standard policies for skills, distance, and availability. Custom policies through the Policy Designer, and predictive routing, sit behind the supplemental services license.
- Working with subcontractors is an add-on. Crowd service, SAP’s model for giving work to external technicians and partner firms through a partner portal, is licensed separately.
There is one more restriction worth knowing before anyone builds a business case. The feature scope description documents two separate integration paths into your ERP:
- SAP Field Service and Asset Management, Native Integration, which SAP develops and maintains. The document scopes it to S/4HANA: on premise, Cloud Private Edition, and Public Cloud.
- SAP Field Service Management, connector for SAP ERP, a software component developed and maintained by Proaxia and sold under an OEM agreement by SAP. The document scopes it to SAP ECC, S/4HANA Cloud Private Edition, and S/4HANA on premise.
What FSA means if you run SAP PM.
SAP's product announcement names asset-intensive industries as an operational model FSA supports, and lists the maintenance technician as a persona it serves. This is a field service product walking deliberately onto plant maintenance ground.
If your service is customer-facing, meaning you dispatch technicians to customer equipment, track SLAs, and bill for service, FSA deserves a serious look.
If you run asset-heavy plant maintenance on SAP PM, nothing changes near term: PM stays your system of record.
Where Arkyn fits.
Arkyn is not a like-for-like FSA or FSM replacement. Arkyn is the scheduling, execution, and reporting layer that sits on top of SAP PM. Every FastApp writes back to SAP, so the more your team uses our apps, the more complete and current your SAP data becomes.
If you are mapping our apps against the SAP products mentioned above, it looks like this:
FastWork is the closest comparison to SSAM and the FSM mobile app. Native iOS and Android work order execution, offline, for technicians. We break the comparison down on FastWork vs SSAM.
FastPlan is similar to MRS and RSH. If you are facing a scheduling migration you did not ask for, FastPlan is worth a look as the alternative path: visual planning and scheduling with changes syncing back to SAP in seconds.
FastExternals is closest to the crowd service add-on in FSM and FSA. It manages subcontractors and distributes SAP PM work orders to them at the individual or company level, with a web portal for your managers and a native app for contractors. Every submission gets reviewed before it touches SAP.
FastForms does what Smartforms do in the FSM world, with a drag-and-drop builder, fields bound to SAP data, and submissions that write back as structured records. Smart distribution rules make sure that every form is associated with the right asset and/or work order when mandatory.
FastNotifications has no real SAP equivalent. It lets operators create SAP notifications from their phone with no SAP login and no SAP training. It’s also useful for documenting operator rounds of facilities and connecting findings into asset data.
FastCloud runs natively on SAP Business Technology Platform under all of our FastApps, and connects to your SAP system through the SAP Cloud Connector. There are no core modifications and no custom ABAP for your team to maintain, which lines up with SAP’s own clean core principles. We are an SAP Silver Partner, and FastCloud supports SAP ECC and S/4HANA, including the transition between them.
At Arkyn, we are building the Frontline OS for SAP maintenance teams: the scheduling, execution, and reporting layer that turns frontline work into data the rest of the SAP stack, and any agents on top of it, can actually use.