SAP Asset & Maintenance
SAP Field Service and Asset Management (FSA), formerly SAP Field Service Management (FSM), is SAP’s AI-enabled cloud solution for scheduling, dispatching, and tracking field technicians. We implement it for asset-intensive companies that also service customer equipment: one schedule for internal crews, subsidiaries, and service partners, mobile execution at the customer site, and full integration with your SAP back end.
SAP asset management, field service, and mobility
go-lives, Evora Group
mobile users
SAP Gold Partner
The solution
SAP FSA is a comprehensive, AI-enabled cloud solution that provides tools for scheduling, dispatching, and tracking field technicians. It integrates front- and back-office processes and enables effective collaboration while keeping customers informed: jobs and workers are scheduled, dispatched, and tracked in real time, assisted by AI and presented as a Gantt chart or in map view, and customers receive automated messages about service appointments, technician arrivals, and service completion.
The product carries the capabilities that were formerly sold as SAP Field Service Management (FSM) and Resource Scheduling (RSH): automated scheduling with a best-matching technician, a policy designer, and appointment booking; long-cycle scheduling that breaks long-term work into meaningful milestones; native offline-first mobile applications with guided workflows and smart forms; a crowd service platform for an ecosystem of partners and technicians; and embedded charts and advanced reporting for data-driven decisions.
We see a strong need among our customers to manage their field resources efficiently, serve their own customers well, and run all of it fully integrated with their SAP environment. That is where we focus: the integration between SAP FSA and the SAP system, whether SAP ECC or SAP S/4HANA, the planning and scheduling rules for your scenarios, the onboarding of subsidiaries, service partners, and freelancers into one schedule, and the mobile setup for the field. SAP FSA can be used standalone or fully integrated with SAP Plant Maintenance (PM) and Customer Service, or with SAP Service Cloud. If you implement it now and move to SAP S/4HANA later, the transition is achieved with low effort.
We set up scheduling on SAP FSA (formerly Resource Scheduling / RSH): capacity, availability, and windows.
We bring dispatch and mobile work to your technicians, subsidiaries, and service partners, online or offline, on FSA mobile.
We keep internal plant maintenance (SAP Plant Maintenance and SSAM) and customer-facing field work (SAP FSA) on one SAP data core.
We deliver service management and customer engagement, from tickets and quotes to contracts, omnichannel, and billing, together with SAP Customer Experience, our neighboring Evora Group portfolio element: one group, no handovers between teams.
Mobile workforce enablement: native offline-first applications, guided workflows and smart forms, location tracking and time recording, service confirmation and reporting.
Crowd services: a crowd marketplace, a partner portal, optimized scheduling and an offline mobile app for partners, and integrated procurement, to expand geographical coverage.
Customer notification, reporting, and frontline worker optimization: automated appointment messages, embedded charts and advanced reporting, and augmented reality to connect workers on site and remotely.
Methods
The steps below are the ones our implementation projects follow. The sequence holds for a single-country rollout and for a platform that goes live country by country; what changes is the number of waves.
Step 1
We document the field service scenarios, the SLAs and appointment windows, the internal and external workforce, and the SAP back end, and design the target solution on SAP FSA against them, including which processes stay in SAP Plant Maintenance (PM), Customer Service, or SAP Service Cloud.
Your service, dispatch, and IT leads bring the scenarios and the constraints.
Step 2
We connect SAP FSA to your SAP back end through standard integration content and APIs: service orders, equipment, business partners, and confirmations flow in both directions, on SAP ECC or SAP S/4HANA.
Your SAP basis and integration team provides access and reviews the integration design.
Step 3
We configure the scheduling logic: skills, availability, locations, SLAs, and travel times, and the scenarios that run automatically through the policy designer. Everything outside those scenarios stays with the dispatcher on the planning board.
Your dispatchers decide which scenarios are automated first.
Step 4
We set up the offline-first mobile app for technicians, subsidiaries, and service partners: guided workflows, smart forms and checklists, time recording, and service confirmation, with self-service onboarding for externals.
Your technicians and partners test the app on their devices in the field.
Step 5
One region or one team goes live first. The pilot proves the schedule, the integration, and the mobile flow end to end, with planners and technicians trained before the first day.
Your pilot team works the schedule for real and reports what breaks.
Outcome
We roll out in waves, per region or country, with training for planners and technicians and post-go-live optimization built into the project. Where the platform goes live country by country, a reusable rollout template carries the configuration forward, and application management services keep the live countries stable.
You set the rollout sequence; we run the waves.
1
2
3
4
5
Step 1
We document the field service scenarios, the SLAs and appointment windows, the internal and external workforce, and the SAP back end, and design the target solution on SAP FSA against them, including which processes stay in SAP Plant Maintenance (PM), Customer Service, or SAP Service Cloud.
Your service, dispatch, and IT leads bring the scenarios and the constraints.
Step 2
We connect SAP FSA to your SAP back end through standard integration content and APIs: service orders, equipment, business partners, and confirmations flow in both directions, on SAP ECC or SAP S/4HANA.
Your SAP basis and integration team provides access and reviews the integration design.
Step 3
We configure the scheduling logic: skills, availability, locations, SLAs, and travel times, and the scenarios that run automatically through the policy designer. Everything outside those scenarios stays with the dispatcher on the planning board.
Your dispatchers decide which scenarios are automated first.
Step 4
We set up the offline-first mobile app for technicians, subsidiaries, and service partners: guided workflows, smart forms and checklists, time recording, and service confirmation, with self-service onboarding for externals.
Your technicians and partners test the app on their devices in the field.
Step 5
One region or one team goes live first. The pilot proves the schedule, the integration, and the mobile flow end to end, with planners and technicians trained before the first day.
Your pilot team works the schedule for real and reports what breaks.
Outcome
We roll out in waves, per region or country, with training for planners and technicians and post-go-live optimization built into the project. Where the platform goes live country by country, a reusable rollout template carries the configuration forward, and application management services keep the live countries stable.
You set the rollout sequence; we run the waves.
Outcome
Condair runs one global field service platform on SAP FSA with SAP ERP integration:
80+ technicians in 6 countries, with ongoing application management services.
Connect governance, architecture, and implementation so platform decisions become stable, measurable execution.
Connect governance, architecture, and implementation so platform decisions become stable, measurable execution.
Connect governance, architecture, and implementation so platform decisions become stable, measurable execution.
SAP FSA runs standalone or fully integrated with SAP Plant Maintenance (PM) and Customer Service, or with SAP Service Cloud. It exchanges service orders, equipment, business partners, and confirmations with your SAP back end through standard integration content and APIs.
SAP FSA runs standalone or fully integrated with SAP Plant Maintenance (PM) and Customer Service, or with SAP Service Cloud. It exchanges service orders, equipment, business partners, and confirmations with your SAP back end through standard integration content and APIs.
SAP FSA runs standalone or fully integrated with SAP Plant Maintenance (PM) and Customer Service, or with SAP Service Cloud. It exchanges service orders, equipment, business partners, and confirmations with your SAP back end through standard integration content and APIs.
SAP FSA runs standalone or fully integrated with SAP Plant Maintenance (PM) and Customer Service, or with SAP Service Cloud. It exchanges service orders, equipment, business partners, and confirmations with your SAP back end through standard integration content and APIs.
SAP FSA runs standalone or fully integrated with SAP Plant Maintenance (PM) and Customer Service, or with SAP Service Cloud. It exchanges service orders, equipment, business partners, and confirmations with your SAP back end through standard integration content and APIs.
SAP FSA runs standalone or fully integrated with SAP Plant Maintenance (PM) and Customer Service, or with SAP Service Cloud. It exchanges service orders, equipment, business partners, and confirmations with your SAP back end through standard integration content and APIs.
FAQ
SAP Field Service and Asset Management (FSA) is SAP’s cloud solution for customer-facing field work:
scheduling, dispatching, and tracking field technicians, assisted by AI. It was formerly SAP Field Service
Management (FSM), and it also carries the capabilities of Resource Scheduling (RSH). It is ideal for
organizations with customer-facing service teams, external partners, SLAs, and complex appointment
windows.
SAP FSA connects to SAP back ends via standard integration content and APIs, exchanging data such as
service orders, equipment, business partners, and confirmations. It can be used as a standalone product or
fully integrated with SAP Plant Maintenance (PM) and Customer Service, or with SAP Service Cloud. Our
team has a strong focus on that integration, whether the back end is SAP ECC or SAP S/4HANA.
SAP FSA focuses on planning, dispatching, AI-based scheduling, customer self-service, and partner
management for customer-facing field work. SAP Service and Asset Manager (SSAM) focuses on mobile
execution for internal plant maintenance: your assets, your technicians, your work orders, online or fully
offline. Asset-intensive companies that also service customer equipment run both, on one SAP foundation.
The optimization engine evaluates technician skills, availability, location, SLAs, and travel times to suggest
or automatically create assignments and routes. Planners fine-tune the suggestions on the graphical
planning board. In practice this reduces travel time, balances workload, and increases adherence to
customer appointments. The scenarios that run automatically are defined in the policy designer; everything
else stays with the dispatcher.
Yes. One of the most frequently requested use cases is the easy onboarding and integration of externals.
SAP FSA integrates subsidiaries, service partners, and freelancers into the same planning and dispatch,
with fast onboarding and self-service for externals, so the dispatcher works from one schedule rather than
from an internal plan plus a set of phone calls.
Yes. SAP FSA provides native offline-first mobile applications with guided workflows and smart forms,
location tracking and time recording, and service confirmation and reporting. The field team completes the
physical work online or offline, and the confirmations synchronize back to the SAP back end when the device
reconnects.
Yes. If you implement SAP FSA now and want to transition to SAP S/4HANA later, the move can be
achieved with low effort, because SAP FSA connects to the back end through standard integration content
and APIs rather than through custom code in the SAP standard. The integration is set up once and carried
over.
SAP Multiresource Scheduling (MRS) is deeply embedded in the SAP back end and ideal for high-volume,
planner-driven resource scheduling; it is still widely used in manual and automatic scheduling scenarios.
SAP FSA is a cloud service with a modern UI, strong mobile integration, AI-based scheduling, and easy
onboarding of external partners. Which one fits depends on whether the work is internal maintenance or
customer-facing field service.
Speak with an expert
Tell us your challenge — right expert within 24h.
