DYNAMICS 365 AGREEMENTS + OPTIMIZATION ENGINE
Dynamics 365 Field Service generates work orders from agreements against customer assets in Dynamics 365. Agreement booking setups produce booking dates, incident types, service tasks, products and services on a defined cadence; the Schedule Board renders the result and Resource Scheduling Optimization can fill configured scopes. That covers a wide band of agreement-driven service work cleanly. At thousands of recurring stops, with SLAs that vary by agreement or incident, with cadence drift to keep capacity balanced, and where the recurring program interacts with reactive break-fix for the same resources, work-order generation is no longer the same thing as optimization. eLogii’s engine models task and route template groups as constraint inputs to the optimizer.
Service agreements help you schedule recurring service for your customers. You can use agreements to automatically generate work orders, invoices, and bookings on a defined cadence.
From learn.microsoft.com/dynamics365/field-service/set-up-customer-agreements. Dynamics 365 Field Service positions the agreement and the customer asset as the spine of recurring service. Agreement booking setups generate work orders on the right cadence. Constraint-aware optimization across thousands of generated stops with interacting SLAs is its own decision layer. Verified June 2026.
Microsoft covers recurring service against the customer-asset base through agreements:
The platform tracks the parent agreement and the child work orders, holds time on the Schedule Board, manages the contract documentation, and runs the route calculation between assigned stops (or fills the board with Resource Scheduling Optimization within a configured scope). The vocabulary is generation-first: produce the work orders from the agreement, hold them on the Schedule Board, manage the contract paperwork, route between them.
What neither the Schedule Board nor Resource Scheduling Optimization positions as the lead capability is constraint-aware optimization across the generated work orders at full scale. The recurring program at scale isn’t just a calendar problem; it’s an assignment problem where SLAs interact (agreement anniversaries, quarterly preventive cycles, customer service contracts), cadences drift, characteristic requirements pin specific resources to specific assets, and capacity has to balance across the recurring program and the daily reactive break-fix.
The recurring programs that outgrow the Schedule Board are concrete:
In each case, the engine doesn’t replace Dynamics 365’s work-order generation from agreements. It optimizes what the generation produces.
A commercial maintenance service organization running monthly, quarterly and annual PMs across a portfolio of customer sites. Fifty-five engineers in the field. Around 3,500 recurring work orders per month generated from agreements, plus daily reactive break-fix for the same engineers. SLA windows vary by agreement: anniversaries pinned to fixed dates, calibration on a hard 6-month cycle, regulatory inspections within calendar months, commercial programs at four-week intervals.
Dynamics 365 Field Service generates the recurring work orders cleanly: stops appear on the Schedule Board at the right cadence, Field Service Mobile carries the job sheets and PM checklists, completion data flows back to Dynamics 365 and Power BI. The planning task that grows past the dispatch surface is the balancing: reactive break-fix for the same engineers landing on top of recurring work orders; cadence drift to keep capacity even across the month; SLA windows that need protection from the optimizer rather than from a dispatcher spotting them in time. Resource Scheduling Optimization can be configured for a single territory and a stable scope, but expanding it to span the agreement-driven program plus reactive break-fix across multiple territories turns brittle. Template-group optimization absorbs cadence drift within rules, protects SLA-locked stops, balances against reactive, and outputs one plan that’s already reconciled across the book. The agreement and customer-asset data model stays in Dynamics 365 Field Service; eLogii owns the optimization across it.
The workaround is the same as for the wider planning problem: the dispatcher carries it, with Resource Scheduling Optimization in a supporting role within a scope. The generated work orders appear on the Schedule Board; the dispatcher assigns them to engineers, balances against reactive break-fix, allows cadence drift to keep capacity even, and signs off on the day. At small recurring books, this is straightforward. At several thousand recurring work orders a month, with SLAs and cadences interacting, the dispatcher becomes the optimizer. The friction shows up as SLA misses on specific agreements, drive-time creep on the recurring book, and over-reliance on the one or two dispatchers who know the recurring rules best.
Recurring programs are modeled as task and route template groups feeding the optimizer. Each template carries the cadence, characteristic requirements, SLA windows and depot rules; the optimizer treats them as first-class inputs alongside the daily flexible work.
Dynamics 365 Field Service stays in place as the system of record for the work order, customer asset, agreement and inventory. Work-order generation from agreements continues to run in Dynamics 365 Field Service. eLogii reads the generated work orders, plus the reactive break-fix, plus the bookable resource / vehicle / territory model, runs the optimization across them, and writes back optimized bookings and ETAs.
Most teams complete the connector build in 3 to 5 weeks. Typical first wave: the recurring program that is leaking the most against SLAs today, or the contract book where cadence interactions are hardest.
30-minute custom simulation with your actual agreement book, bookable resources and SLAs. Projected savings in drive time, SLA hit rate and dispatcher hours.
Yes, at the workflow layer. Agreements in Dynamics 365 Field Service model recurring service against customer assets, generating booking dates and work orders at the right cadence with incident types, service tasks, products and services pre-populated, and entitlement validation tied in. The assignment and route between the generated work orders is then handled by the Schedule Board, with Resource Scheduling Optimization filling configured scopes. What neither positions as the lead capability is constraint-aware optimization across thousands of recurring work orders with interacting SLAs, cadences and characteristic requirements, balanced against daily reactive break-fix for the same resources in one solver run. That decision layer is where eLogii adds value.
Agreement-driven work-order generation: produce a list of work orders at the right cadence (monthly PMs, quarterly preventive, weekly commercial maintenance) against customer assets and incident types. Recurring program optimization: take the generated work orders, plus the daily reactive break-fix, plus the resource pool, plus the SLAs and cadences, and decide assignments and routes that respect all of them at once. Dynamics 365 Field Service does the first cleanly. eLogii does the second, modeled directly through task and route template groups that feed the optimizer as constraint inputs.
When the recurring program runs to hundreds or thousands of work orders per month, when SLAs vary by agreement or incident, when cadence drift (a stop shifting from week 1 to week 2 to keep capacity balanced) becomes a planning task, when Resource Scheduling Optimization scopes can’t span the agreement-driven program plus reactive break-fix in one run, and when the recurring program interacts with daily reactive break-fix for the same resources. PM programs across hospital networks, multi-site PMs for industrial customers, recurring commercial maintenance contracts, inspection programs across regions: each of these hits the optimization decision layer rather than the work-order generation layer.
Through task and route template groups: weekly, monthly, quarterly and bespoke cadences are modeled directly as inputs to the optimizer. Each template carries characteristic requirements, time-window constraints, SLA targets and cadence rules. When the run happens, the optimizer balances the recurring program against the daily flexible work, protects SLA-locked stops, allows cadence drift within rules, and outputs one consistent plan. Bristow & Sutor routes 200,000+ recurring case visits per year on eLogii.
Custom integration against the Dataverse Web API (OData v4) and eLogii’s REST API. eLogii reads agreements and the generated work orders from Dynamics 365, plus the daily reactive break-fix and the bookable resource / vehicle / territory model. The optimization run considers them together. Bookings and ETAs are written back to Dynamics 365; Field Service Mobile picks up the assignments. Completion data flows back to the work-order record. Typical connector build: 3 to 5 weeks.
Last updated: June 2026. Dynamics 365 Field Service scope is drawn from Microsoft Learn: customer agreements and the Dynamics 365 Field Service overview. eLogii capabilities documented at elogiiapidocs.apidog.io.
Custom simulation
A 30-minute working session with our solutions team. We take a sample of your real jobs, depots, vehicles and SLAs, run them through the eLogii engine, and show you the projected delta against how you plan today. No slides, no generic benchmarks.
