COMPARISON
ServiceMax, a PTC business, is the asset-centric FSM: installed base, work orders, warranty, contracts, parts, mobile execution. eLogii is the routing and optimization layer that runs alongside ServiceMax when the planning problem grows past what the built-in dispatch surface is designed to solve. Two engines, six configurable modes, multi-day, multi-depot, recurring patterns, rule-based re-optimization, all callable over REST.
TRUSTED BY HUNDREDS OF HAPPY CUSTOMERS
ServiceMax and eLogii do different jobs in the same field-service stack. ServiceMax is the asset-centric FSM: the system of record for the installed base, the work order, the warranty, the contract and the parts. eLogii is the routing engine for operations where the optimizer needs to do the heavy lifting across multi-day, multi-depot and constraint-heavy plans, and where the dispatcher needs the engine to decide assignments, not just place them.
The combined deployment pattern: ServiceMax stays the system of record for the asset, the work order, warranty, contracts, parts and mobile field execution. eLogii reads work orders, assets, technicians, vehicles, depots and recurring service templates from ServiceMax (via the ServiceMax REST APIs in Core, or the Salesforce Platform APIs underneath Asset 360), runs the optimization across the routing horizons the built-in dispatch surface is not designed for, and writes optimized routes and ETAs back. The technician opens the Salesforce Field Service app or ServiceMax Go on site; the route they take is the one eLogii planned. ServiceMax keeps the asset-centric workflows it owns end to end; eLogii owns the optimization decision layer.
ServiceMax is the asset-centric FSM. eLogii is the routing engine for the optimization-driven side of the problem. The table below isolates where each side leads.
| eLogii adds | ServiceMax today | |
|---|---|---|
| Optimizer-driven assignment under heavy constraint | Engine decides which technician takes which work order under skills, capacity, time-window, SLA and depot constraints, as the primary surface | Service Board scheduling rides on Salesforce Field Service optimization in Asset 360 or the native scheduler in Core; tuned for asset-centric workflows rather than constraint-heavy dispatch |
| Multi-depot routing in one pass | Route across multiple depots, branches and home start locations as a single optimization input | Territory-based routing; cross-territory and cross-depot rebalancing as operator work in the Service Board |
| Multi-day, long-haul, full-month horizons | Plan a single day or an entire month in one run; multi-day routes with overnight stops | Multi-day work orders supported in the asset record; not solved as a single multi-day optimization across crews |
| Recurring service programs at scale | Task and route template groups: weekly, monthly, quarterly, bespoke cadences modeled as inputs to the optimizer | Maintenance plans generate work orders against assets; the cross-program optimization across reactive work is left to the scheduler |
| Two engines, six configurable modes | Default + Advanced engines, three assignment modes + three load-balancing modes, all REST-callable | No public ServiceMax-built optimization engine documented separately from the underlying scheduler stack |
| Rule-based re-optimization the dispatcher can see | Operator-visible rules; live re-optimize while protecting locked SLAs and customer-confirmed slots | Reshuffle on exception is handled in the Service Board; optimization rules live inside the underlying engine |
| Slot booking co-pilot | Route-aware availability calculation: only slots that fit the current optimized plan, returned to your booking layer over REST | Customer self-service portal supports booking; route-aware availability not the lead workflow |
Sources: PTC ServiceMax, ServiceMax Asset 360 on AppExchange, ServiceMax Core on AppExchange; eLogii optimization engines. Verified June 2026.
| eLogii | ServiceMax | |
|---|---|---|
| API style | REST, JSON over SSL, ApiKey authentication, predictable resource URLs | REST APIs across accounts, work orders, assets, contracts and parts; Salesforce Platform APIs underneath Asset 360; OData via DataDirect |
| API access | Included as part of the platform; documented at elogiiapidocs.apidog.io | Available to ServiceMax customers and partners; tier and quota confirmed against the deal |
| Sandbox environment | Full API parity at api-sandbox.elogii.com | Salesforce sandbox model in Asset 360; ServiceMax-arranged sandbox in Core |
| Bulk operations | POST /tasks/createOrUpdateMany handles hundreds of tasks per call | Salesforce Bulk API patterns in Asset 360; per-resource endpoints in Core |
| Webhooks / streaming | Seven event types including Driver/Task Tracking Update with live GPS stream and Route ETAs Update | Salesforce Platform Events and Change Data Capture in Asset 360; webhook surface in Core varies by integration partner |
| Optimization callable via API | All six modes callable via REST; lock specific routes, manually reorder stops, re-run with new constraints | No public ServiceMax-built optimization endpoint; scheduling and optimization sit inside Salesforce Field Service in Asset 360 or the Dispatch Console in Core |
Sources: eLogii API documentation; ServiceMax API tracker; SAP ServiceMax connector. Verified June 2026.
| eLogii | ServiceMax | |
|---|---|---|
| Role in the stack | The routing and optimization decision layer. Runs alongside an FSM, never replaces it. | The asset-centric FSM: installed base, work order, warranty, contracts, parts. Asset 360 on Salesforce Field Service, Core on the native ServiceMax stack, FieldFX for energy services and oilfield ticketing. |
| Where it shines | Operations where the optimizer needs to decide assignments under heavy constraints across days, depots and crews | OEMs servicing their own installed base: medical devices and lab instruments, industrial equipment, energy services, semiconductor equipment, elevators, power and utilities |
| Reference customers | J-Club, NHS, Belfast City Council, Vergo, Bristow & Sutor, Greenix, Porcelanosa, Brymec, Heatleys | Schneider Electric (8,000+ end users across 80+ countries including 4,000+ field technicians); Elekta (medical linear accelerators) |
| Ownership | Independent platform focused on routing and optimization | PTC business |
| Security certifications | ISO 27001 + SOC 2 Type 2, publicly listed | Enterprise security controls under PTC; confirm current attestations directly |
| Typical implementation | 3 to 5 weeks including building the connector against ServiceMax’s REST API or the Salesforce Platform APIs underneath Asset 360 | Consultant-led implementations typically run weeks to months; Asset 360 deployments also depend on the Salesforce Field Service rollout underneath |
| Pricing model | Platform fee, banded by field staff/drivers/jobs per day/modules, from $3,000/mo. Composes with what ServiceMax charges per user. | No public pricing. Third-party aggregators cite USD 150 to USD 300 per user per month for enterprise deals, plus Salesforce Field Service licensing underneath Asset 360. |
| Customer review stance | 3 to 4× ROI within 6 months typical; fast time-to-value cited | G2 and TrustRadius reviewers praise the asset-centric depth and warranty/entitlement workflow; common review notes flag Dispatch Console performance, mobile sync latency and the lift required for third-party integrations |
Sources: PTC acquisition announcement, PTC completes acquisition (Jan 2023), Schneider Electric case study, Elekta case study, G2 reviews, TrustRadius reviews, ITQlick pricing. Verified June 2026.
ServiceMax’s scheduling is built around the asset and the work order, surfaced in the Service Board (Salesforce Field Service in Asset 360, native Dispatch Console in Core, the field-ticketing surface in FieldFX). What no ServiceMax product positions as the lead capability is constraint-heavy optimization across multi-day, multi-technician and multi-depot operations in one solver run, recurring service programs at thousands of stops in a single optimization input, or a public REST surface for the optimizer itself. eLogii’s optimizer covers exactly that side, callable over REST.
eLogii’s optimizer is built around two engines and six configurable modes, all callable via REST and exposed to the dispatcher as controls they can see and adjust.
Beyond the modes, eLogii ships the operational surface the ServiceMax dispatch board isn’t designed to lead on: multi-day and long-haul routing (“plan a single day or an entire month in one run”), multi-depot (“route across multiple depots, branches, or home start locations in a single run”), recurring service patterns via task and route template groups (weekly, monthly, quarterly, bespoke cadences modeled as inputs to the optimizer, not as generated work orders to be hand-rebalanced), multi-technician crew jobs with skills, capacity and SLA constraints, and rule-based re-optimization the operator can see and steer.
If the dispatcher’s morning routine is “open the Service Board, confirm the entitlement, assign the work order to the territory technician, let the underlying engine handle the route”, ServiceMax (in either product) is the right tool and adding eLogii would be over-engineering. If the dispatcher’s morning routine is “run the optimizer against today’s open work orders across three depots, balance against next week’s recurring maintenance book, protect the SLA-locked entitlement stops, route around the technician who’s off Tuesday”, the Service Board is being asked to do a job it wasn’t built for. eLogii covers that side via REST API; ServiceMax stays in place for the asset, the work order, the warranty and the parts.
eLogii has fundamentally transformed the way we operate. The productivity gains, enhanced visibility, and ability to scale confidently have been game-changing. The rollout was smooth, the support exceptional, and the results speak for themselves.
Paul Clark, Co-Chief Operating Officer, Richburns · nationwide UK field services team
ServiceMax covers asset-centric service well across medical devices, lab instruments, industrial OEMs, energy services and similar OEM-services-its-own-installed-base patterns. The signal that the routing problem has grown past the dispatch surface tends to be operational rather than headcount-based. Three patterns show up:
Where any of these is the dominant shape of the work, eLogii is the routing layer. Where none of them is, ServiceMax’s built-in dispatch surface is the right tool and adding eLogii is over-engineering. The honest answer for many ServiceMax customers is “you don’t need eLogii.” The honest answer for the operations where the optimizer is the bottleneck is that eLogii is built for exactly that.
ServiceMax continues to do the asset-centric FSM work it’s built for. The difference shows up where the routing problem used to dominate. Brymec lifted productivity 30% and routing efficiency 20% on eLogii. ATS Building Products improved deliveries per route by ~98%. Porcelanosa runs eLogii with 95%+ ETA accuracy on daily distribution. Unimasters runs eLogii across a multi-country operation and achieved 50% less planning time and 49% fewer service calls. These are operational outcomes that come from moving the assignment problem from the dispatcher’s morning into the optimizer:
The typical asset-centric field service stack: an FSM for the asset, work order and contract (ServiceMax, Salesforce Field Service standalone, MS Dynamics 365 Field Service, IFS Field Service Management), an ERP for finance and customer master data (SAP, Oracle, NetSuite, MS Dynamics 365 BC), telematics for the vehicles (Samsara, Geotab, TomTom), an IIoT layer for condition-based service (ThingWorx under PTC), and a routing decision layer alongside the dispatch surface for operations where the optimizer is the bottleneck.
eLogii is built for that shape. It plugs into ServiceMax (in either product), leaving the asset record, work-order lifecycle, warranty, contracts, parts and mobile field execution where they already are. The technician opens the Salesforce Field Service app or ServiceMax Go on site; eLogii plans the route they take to get there, surfaces the live ETAs, picks up GPS, and pushes completion back into ServiceMax. The common patterns:
What makes the stack pattern straightforward:
api-sandbox.elogii.com so integration work can run in parallel with the existing FSM/ERP rollout.POST /tasks/createOrUpdateMany handles hundreds of tasks per call, built for high-volume ingest from any FSM or ERP.ServiceMax exposes REST APIs to customers and partners, with Asset 360 reachable through the Salesforce Platform APIs underneath. The two APIs combine cleanly: eLogii calls ServiceMax to read work orders, assets, technicians, vehicles, sites and recurring service templates, runs the optimization across the routing horizons the built-in dispatch surface is not designed to solve, and writes optimized routes and ETAs back. The Salesforce Field Service app or ServiceMax Go picks up the planned route; completion data flows back into ServiceMax for asset history, warranty, parts and reporting.
Both sides expose REST APIs. ServiceMax’s is the integration surface for an asset-centric FSM data model across Core, Asset 360 and FieldFX, with Asset 360 reachable through the Salesforce Platform APIs underneath. eLogii’s is the integration surface for a routing and optimization engine, with the optimizer itself callable as REST endpoints.
api-sandbox.elogii.com, full parity with production at api-35.elogii.com.POST /tasks/createOrUpdateMany handles hundreds of tasks per call, built for high-volume ingest from any FSM or ERP.For an integration team, the typical pattern when ServiceMax and eLogii are both in the stack: ServiceMax owns the system of record for assets, work orders, contracts, entitlements, parts and technicians; eLogii reads work orders/assets/technicians/vehicles/sites from ServiceMax over the API (directly in Core, via the Salesforce Platform APIs in Asset 360, via the FieldFX REST surface for energy-services tickets), runs the optimization across the horizons the built-in dispatch surface is not designed for, writes optimized routes and ETAs back; the Salesforce Field Service app, ServiceMax Go or the FieldFX mobile app shows the route to the technician; completion writes back to ServiceMax for asset history, warranty and parts.
eLogii runs alongside ServiceMax; it does not replace what you’re paying PTC today. The question is what eLogii adds on top, and what it costs to add it.
eLogii pricing starts from $3,000 per month as a platform fee, banded by field staff, drivers, jobs per day and the modules required. Each band includes a quota; cost steps up when the operation crosses a band, not when you add an individual seat. Customers typically report 3 to 4× return on investment within 6 months, and combined ServiceMax + eLogii rollouts complete in 3 to 5 weeks including the connector build.
ServiceMax does not publish pricing; deals are consultant-led and enterprise. Third-party aggregators report typical pricing in the USD 150 to USD 300 per user per month band for enterprise deployments, with smaller-band quotes anywhere from USD 60 to USD 135 per user per month depending on volume. Asset 360 additionally requires Salesforce Field Service licensing underneath as a separate subscription. The pricing models compose: ServiceMax charges per user for the asset-centric FSM (plus Salesforce in Asset 360), eLogii charges a platform fee for the routing layer. There is no per-seat cost from eLogii.
30-minute custom simulation with your real ServiceMax work orders, assets and field-service plans. Projected savings in drive time, fuel and dispatcher hours from adding eLogii on top.
We’d never go back to the way we were planning before. eLogii is the backbone as well as the brain of our planning operations, translating actively to our bottom line.
Jord Van Dijk, IT Director, J-Club · 9,000+ stores routed on eLogii
Three steps for ServiceMax customers whose dispatch problem has grown past what the built-in surface is designed to solve. ServiceMax stays in place for the asset-centric FSM; eLogii layers on as the routing engine.
Technicians, vehicles, depots, customers, assets, work orders, entitlements and recurring service templates sync from ServiceMax via its REST API (directly in Core, via Salesforce Platform APIs in Asset 360). Technician home locations, certifications and skill sets, customer sites and asset hierarchies map to eLogii drivers, depots and constraints. ServiceMax maintenance plans become eLogii task and route template groups. Read-write integration designed so ServiceMax stays the system of record for the asset.
Weeks 1–2Custom data simulation against your historical ServiceMax work orders so you can validate the modeling and project savings before go-live. Side-by-side comparison: what the built-in dispatch surface produces today vs. what eLogii’s optimizer produces with multi-day, multi-depot or recurring-program optimization on the same data.
Weeks 2–3Start with the business unit where ServiceMax’s built-in dispatch is leaking the most: usually a multi-depot regional service book, a large recurring maintenance program, or the part of the operation where the dispatcher is hand-rebalancing every morning. Run it on eLogii, prove the lift on real work orders, then expand. ServiceMax keeps owning the asset, the work order, warranty and parts in parallel. Most teams complete the transition in 3 to 5 weeks total including the connector build.
Weeks 3–5Unimasters runs eLogii across a multi-country operation and achieved 50% less planning time and 49% fewer service calls. Multi-country rollouts deploy in weeks, not quarters.
ServiceMax’s dispatch surface is excellent at asset-centric service. Four patterns where the optimization decision layer alongside it is the bottleneck, each with its own deep dive:
Service Board (Asset 360), Dispatch Console (Core) and FieldFX surface place work orders against territories. The constraint-based assignment engine that decides under skills, capacity, SLAs and depots is its own decision layer.
ServiceMax models territory cleanly. Regional service networks need cross-territory rebalancing as a single optimization input. eLogii covers it.
ServiceMax generates work orders from maintenance plans against assets and contracted entitlements. Optimizing the generated stops at scale, against reactive break-fix, needs an engine.
ServiceMax has a customer self-service portal. Route-aware availability that respects the current optimized plan is its own layer.
A single overview of the four patterns where the ServiceMax dispatch surface reaches its design ceiling, plus diagnostic signals for spotting them.
Complement, in most cases. ServiceMax, a PTC business, owns the asset-centric FSM stack: installed base, work orders, warranty and entitlements, contracts, parts inventory, mobile execution, customer self-service. eLogii is the routing and optimization layer that runs alongside ServiceMax when the planning problem starts to dominate: multi-depot field-service operations, dense same-day plans with hundreds of competing time-window constraints, optimizer-driven assignment across crews. ServiceMax stays the system of record for the asset. the integration runs over ServiceMax’s REST API on one side and eLogii’s REST API on the other.
When the dispatch surface stops being the right place to solve the optimization problem. In Asset 360, scheduling sits on Salesforce Field Service’s optimization engine, which descends from the ClickSoftware tech Salesforce acquired in 2019. In ServiceMax Core, scheduling runs on the native Dispatch Console. Both are valid for asset-centric service. eLogii layers on when the operation needs constraint-aware assignment across multi-day, multi-depot and recurring patterns in one optimization run, programmatic re-optimization with operator-visible rules, and slot booking that respects the current optimized plan.
Yes at the FSM-workflow level. ServiceMax supports multi-resource jobs, crew composition, asset hierarchies and territory-based scheduling. Asset 360 inherits Salesforce Field Service’s scheduling and optimization surface; ServiceMax Core uses the native Dispatch Console. What neither product positions as the lead capability is constraint-heavy optimization across multi-day plans, multi-depot rebalancing as a single optimization input, recurring service programs at thousands of stops in one solver run, or programmatic re-optimization as a public REST surface. That’s where eLogii’s two engines and six configurable modes add depth, with ServiceMax staying the system of record for the asset, the work order, warranty, contracts and parts.
Integration runs over the ServiceMax REST API on whichever product is in use. eLogii’s REST API has 70+ endpoints, ApiKey auth, a full-parity sandbox at api-sandbox.elogii.com and seven webhook events including live driver GPS and Route ETAs Update. ServiceMax exposes REST APIs for accounts, work orders, assets, contracts and parts across Core, Asset 360 and FieldFX; Asset 360 is a Salesforce managed package, so integration teams typically reach data via Salesforce Platform APIs and middleware (MuleSoft is common). The typical pattern, Typically: eLogii reads work orders, assets, technicians, vehicles, depots and recurring service templates from ServiceMax; runs the optimization across the routing horizons the built-in dispatch surface is not designed to solve; writes optimized routes and ETAs back. Completion writes back to ServiceMax for asset history, warranty and parts.
ServiceMax does not publish pricing. Third-party aggregators report enterprise deals in the USD 150 to USD 300 per user per month band, with smaller-band quotes ranging from around USD 60 to USD 135 depending on volume. Asset 360 additionally requires Salesforce Field Service licensing underneath as a separate subscription. eLogii is a platform fee, banded by field staff, drivers, jobs per day and modules, from USD 3,000 per month. The pricing models compose: ServiceMax charges per user for the asset-centric FSM (plus Salesforce in Asset 360), eLogii charges a platform fee for the routing layer. Customers typically report 3 to 4× return on investment within 6 months on eLogii.
Typically 3 to 5 weeks from kickoff to a phased go-live, including building the custom connector against ServiceMax’s REST API or the Salesforce Platform APIs underneath Asset 360. eLogii reads work orders, assets, technicians, vehicles, depots and recurring service templates from ServiceMax; routes, ETAs and completion data flow back. Most teams start with the business unit where the built-in dispatch surface is leaking the most: usually a multi-depot regional field-service book, a recurring service program at scale, or the part of the operation where the dispatcher is hand-rebalancing every morning. ServiceMax stays in place for everything else.
Three reasons. First, ServiceMax was built to manage the asset and its service workflow end to end; routing is exposed via the Service Board UI and the underlying optimization engine (Salesforce Field Service in Asset 360, the native scheduler in Core). Once the operation needs constraint-heavy multi-day, multi-depot optimization as the daily input, that surface is not the tool. Second, eLogii customers at scale report operational outcomes that go past what FSM scheduling alone delivers: Brymec 30% productivity and 20% routing efficiency; ATS Building Products 98% improvement in deliveries per route; Porcelanosa 60%+ planning time cut; Unimasters 50% less planning time and 49% fewer service calls. Third, eLogii exposes the optimizer itself as REST endpoints with seven webhook events, so the routing layer integrates cleanly with the rest of the stack.
Yes. eLogii runs operations at scale: J-Club (9,000+ stores), NHS, Belfast City Council, Vergo Pest Management (400 technicians, Tyro Group), Bristow & Sutor (200+ enforcement agents, 200,000+ case visits routed annually), Porcelanosa, Caldic and Berkmann Wine Cellars. ISO 27001 and SOC 2 Type 2 certified.
Last updated: June 2026. Information about ServiceMax is drawn from PTC ServiceMax, PTC’s 2022 acquisition announcement and January 2023 completion release, the Asset 360 AppExchange listing, the ServiceMax Core AppExchange listing, the Schneider Electric and Elekta customer stories, G2 and TrustRadius reviews, and aggregator pricing reports. Information about eLogii is drawn from elogii.com and the eLogii API documentation.
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.