The latest roadmap for SAP Field Service and Asset Management (SAP FSAM) focuses on the 2611 release with a broader view of planned developments.
From AI agents and smarter scheduling to mobile capabilities, crew management and SAP S/4HANA integration, the roadmap includes developments across planning, dispatching, field execution and system administration.
For organisations using or considering SAP Field Service and Asset Management, this update is an early view of how day-to-day functionality is expected to develop alongside a move towards more AI-assisted and autonomous processes.
As this is a roadmap update, the final scope and timelines may change.
AI and agents across SAP Field Service and Asset Management
SAP’s wider autonomous enterprise vision extends into field service and asset management through planned AI agents for specific roles, tasks and processes.
Planned AI agents are intended to connect asset data, strategy, planning and execution. These agents are designed as building blocks: organisations may use an individual agent for a specific task or combine agents across the product to support wider workflows and decision-making.
The roadmap includes a first wave of agents in upcoming releases, with more planned over time. These include a first version of a dispatcher agent and an agent designed to help users build and understand scheduling policies.
Another planned development is the Joule for SAP FSAM transition from a customer-managed to a fully SAP-managed service. This is intended to reduce setup and integration complexity. Customers would select their region through a guided procedure, while SAP would manage the necessary account creation, prerequisites, service provisioning and integrations.
Capacity planning and scheduling
The roadmap indicates a progression from providing schedulers with information towards using AI to assist more actively with their work.
SAP intends to introduce holiday-aware capacity calculation. By incorporating technician-specific holiday calendars, this is intended to provide a more realistic view of available capacity and utilisation.
SAP also plans a Joule scheduling agent for workload and capacity insights. Schedulers will be able to ask natural-language questions about workload, capacity and utilisation across regions, work centres and time periods. The agent is intended to provide summaries and recommendations that help identify capacity bottlenecks and workload imbalances.
Another planned enhancement is a workload-by-order-type chart, providing visibility into which work categories contribute to capacity demand.
Further roadmap developments include graphical scheduling for workload and capacity, overdue-work insights, schedule snapshots for comparison over time and additional AI-supported optimisation.
Longer-term roadmap areas include AI-based scheduling scorecards, automated scheduling and load balancing, predictive workload and capacity planning, and planning that accounts for wider operational constraints. These are future roadmap areas rather than confirmed 2611 functionality.
Planning and dispatching in 2611
Several features are specifically planned for the 2611 planning and dispatching experience.
One is improved time-zone handling. SAP plans to calculate the activity’s time zone from its address and display technician working and non-working hours according to the technician’s local time. For dispatchers managing teams across regions, this is designed to reduce the risk of scheduling work during inappropriate local hours.
SAP also plans a service dispatcher agent, bringing conversational dispatching through Joule. Dispatchers will be able to use natural-language prompts to check availability, plan jobs, and reschedule work.
The agent is intended to consider operational context, including technician skills, SLA urgency and geographical proximity, when recommending and carrying out planning decisions.
The planning board activity card is also due to be redesigned. Configurable layouts will allow planners and dispatchers to tailor the information displayed to their operational requirements, bringing important job information directly into the planning view.
Service Map and Crowd Service developments
For the Service Map, changes to technician-location handling are planned to support regional data-privacy requirements. The intention is to allow planners to assign work using regional availability and general proximity without exposing exact technician locations where this is not appropriate.
AI filters for Service Map objects are also planned, designed to surface high-priority assets and urgent jobs while reducing background information.
Support for multi-polygon geometry through the Spatial Data API would allow organisations to define service territories made up of separate or disconnected geographical areas under a single region or technician.
In Crowd Service, planned developments include improved filtering and grouping in the Partner Portal. Configurable rejection-reason categories and the mandatory capture of rejection reasons are also intended to give central dispatchers greater clarity when external service partners reject assignments.
Daily crew planning and resource management
Crew planning is another area highlighted for 2611.
SAP plans to introduce a daily crew planner with an initial minimum viable product (MVP) scope. It is intended to help dispatchers and crew leads assemble, adjust and reassign personnel to crews, including responding to absences and changing requirements.
The roadmap includes a resource reservation agent, intended to analyse capacity, overlapping commitments and availability constraints to help prevent scheduling conflicts and respond to changing priorities.
Another planned agent would help configure crews and assign work. This agent is expected to evaluate constraints such as required certifications, geographical proximity and individual skill levels when recommending crew configurations and assignments.
Mobile developments for field technicians
Several developments are planned for the SAP Field Service and Asset Management mobile application.
Joule is expected to become accessible directly within the mobile workflow. Natural-language interaction could be used to generate daily work summaries and access information about routes, work details and expected effort. Technicians will also be able to use native voice-to-text functionality.
Background synchronisation is another significant planned enhancement. This will allow technicians to continue working while the application synchronises in the background, which may be particularly useful in poor network conditions.
Upcoming APIs will enable Progressive Web Applications to communicate with the mobile application’s offline database. Progressive Web Applications will respect the mobile application’s existing access permissions. The mobile application will synchronise any changes they make using its existing synchronisation process.
Other 2611 mobile developments include background GPS tracking for Android and iOS, clearer time-zone information, the option to return directly to activity details after opening an HTML report, and support for iOS and Windows font and display settings.
Continuing SAP S/4HANA integration
Integration forms a substantial part of the roadmap.
For SAP S/4HANA Cloud Public Edition, planned integration for proactive and emergency maintenance is intended to connect maintenance planning in SAP S/4HANA with workload and capacity balancing, scheduling and dispatching in SAP Field Service and Asset Management, technician execution and confirmation, and subsequent review and closure.
Planned synchronisation of equipment-related attachments will give technicians access to technical drawings, manuals and certificates relevant to the equipment and job.
Another roadmap area is an Event Mesh-free service order integration approach, being developed to simplify the integration architecture and reduce complexity for customers.
For SAP S/4HANA Cloud Private Edition and on-premise scenarios, further roadmap developments include external workforce integration, tool integration, enterprise organisational structures, serialised parts and measurement points.
Additional integration plans cover skills and proficiency, workload and capacity, crew and multi-activity requirements, reduced dependency on SAP HR objects for certain scenarios, and support for distributing technician time across different activities.
Administration, configuration and business rules
Planned developments across SAP FSAM administration, configuration and business rules also include wider use of AI.
SAP plans an agent for managing system customisation, intended to allow user interface definitions to be created and modified using natural language. Another agent under development will check custom extension code for quality and identify potential issues.
Other near-term foundation developments include support for customising the mobile home screen, native WalkMe integration for customers with a WalkMe licence, and configurable retention periods for different object types.
For business rules, SAP plans a business rule management agent. Administrators and consultants will be able to use natural-language queries to investigate why a rule is not behaving as expected, analyse its execution history and receive proposed corrective actions.
Further along the roadmap, SAP intends to develop the ability to generate and modify business rules using natural language, alongside further AI-assisted administration capabilities.
What should SAP FSAM customers take from the 2611 roadmap?
For us at On Device Solutions, one of the most notable aspects of this roadmap is the breadth of development across the field service process.
SAP’s investment in AI and agents is clear, but the roadmap is not solely about AI. The planned developments also address practical operational priorities: scheduling work across regions, managing crews and resources, supporting technicians when connectivity remains limited, connecting field and back-office processes, and administering the system more efficiently.
The roadmap also indicates how SAP is approaching AI within SAP FSAM: embedding assistance into specific roles and workflows rather than treating it as a standalone capability.
For organisations using SAP Field Service and Asset Management, the next step is to understand which developments are relevant to their processes and distinguish planned SAP FSAM 2611 functionality from SAP’s longer-term roadmap.
As an SAP Gold Partner specialising in enterprise mobility and SAP Field Service and Asset Management, On Device Solutions continues to follow these developments closely and assess what upcoming changes could mean for your field service and mobile operations.
Talk to an ODS specialist about what the SAP FSAM roadmap could mean for your field service operations.
