ServiceMax Explained: Core, Asset 360, AI and How It Fits Salesforce

What Is ServiceMax?

ServiceMax is field service management software from PTC for companies that install, maintain and repair equipment. It runs on the Salesforce platform and covers work orders, technician scheduling, a mobile app, installed base and asset history, service contracts and entitlements, preventive maintenance, parts and returns, and service analytics, with ServiceMax AI on top.

PTC describes ServiceMax Core as "asset-centric field service management software" (PTC: ServiceMax Core). In practice, that means the record at the centre of everything is the machine in the field, with its configuration, location, warranty and service history, rather than the customer account alone. Use this as a quick fit check.

Who Owns ServiceMax Now, and What Has Changed?

PTC owns ServiceMax. It completed the acquisition in January 2023, buying the company from an entity majority-owned by Silver Lake, and still sells it under the ServiceMax brand as part of its service lifecycle management portfolio. In October 2026, Schneider Electric agreed to acquire PTC itself; that deal is pending.

Four changes matter to anyone running or buying ServiceMax today:

• The website moved. ServiceMax product information now lives on PTC's site (PTC: ServiceMax), and the acquisition is documented in PTC's January 2023 announcement.
• The parent company may change again. On 5 October 2026, Schneider Electric and PTC announced a definitive agreement for Schneider Electric to acquire PTC, with closing expected by the third quarter of 2027, subject to shareholder and regulatory approvals (PTC announcement). The announcement does not name ServiceMax, so treat any product impact as unknown until PTC says more.
• Releases are being unified. From 2027, ServiceMax products follow a single PTC release schedule with one preview period, one set of release notes and one testing cycle. The December 2026 release moved to January 2027 and was renamed 2027.0 (PTC release schedule). Adjust your sandbox testing calendar now.
• Salesforce renamed its own product. Salesforce Field Service is now "Agentforce Field Service and Operations" in Salesforce Help (Salesforce Help). Asset 360 runs on top of it, so the rename affects how you read both vendors' documentation.

The Three ServiceMax Offerings in 2026

PTC sells ServiceMax in three offerings, all built on the Salesforce platform with a shared architecture: ServiceMax Core, a complete field service suite with its own objects and apps; ServiceMax Asset 360 for Salesforce Field Service, which adds asset depth to Salesforce's standard field service objects; and FieldFX, for energy service organisations.

That three-way split is PTC's own description (PTC: ServiceMax). Most confusion in older articles, including our own 2024 post, comes from describing "ServiceMax" as one product when the right answer depends on which of the three you mean.

Sources: ServiceMax Core, ServiceMax Asset 360 for Salesforce and ServiceMax FieldFX. Do not confuse ServiceMax Asset 360 with "PTC Asset 360", a separate PTC asset data product now renamed PTC Orbit.

ServiceMax Core vs Asset 360: Which Data Model Are You Choosing?

Choose ServiceMax Core when you want ServiceMax's own objects, mobile app and scheduling board. Choose Asset 360 when you want to stay on Salesforce Field Service's standard objects and mobile app, and add ServiceMax's asset, contract and returns depth on top. The choice decides your data model, your technician app and your upgrade path.

PTC documents Asset 360 as "natively built on Salesforce Field Service" and "primarily built on Salesforce Field Service's core data model" (PTC: About Asset 360). It installs as a managed package and receives automatic upgrades (AppExchange listing). Core uses its own ServiceMax object names. The practical differences:

Two points are easy to miss. First, Core and Asset 360 are not a simple version upgrade of each other: the object models differ, so moving from one to the other is a data migration project, not a package update. When Asset 360 launched in 2020, ServiceMax said it would keep investing in Core, and both are still released in 2026: Core 30.0 shipped in June 2026 and Asset 360 15.0 reached production in October 2026 (Core release schedule, Asset 360 releases). Second, an Asset 360 deployment includes Salesforce Field Service by design, so you license and configure both.

What ServiceMax Does, Area by Area

ServiceMax covers the full service lifecycle of an asset: creating and executing work orders, scheduling and dispatch, technician mobility, installed base management, contracts and entitlements, preventive maintenance, parts, returns and depot repair, customer and partner collaboration, and service analytics. Each area below names the modules involved.

Work Orders and Guided Service Processes

Execution

Modules: ServiceMax Core work order management, Service Flow Manager (Core), Service Process Manager (Asset 360).

Work orders can be created from cases, customer requests, installed products, preventive maintenance plans or IoT signals, and carry the asset, location and entitlement data with them. Service Flow Manager is described by PTC as "a powerful business workflow engine that ensures consistent service execution across mobile and web platforms without coding" (PTC: Core). Core 30.0 (June 2026) added task dependencies with timing offsets in Work Plans, repeat tasks and Field Change Order enhancements (Core 30.0 release notes). Our guide to optimising work order management in ServiceMax goes deeper.

Technician Mobility

Mobile

Modules: ServiceMax Go and DataGuide (Core); the Salesforce Field Service app (Asset 360).

PTC describes ServiceMax Go as "a technician mobile app that runs on any device, regardless of connectivity", with full and incremental sync, offline close of jobs, pricing engines, document generation and signature capture. DataGuide adds advanced forms and checklists such as inspections (PTC: ServiceMax Go). Offline capability matters more than it sounds: plant rooms, basements, hospitals and remote sites are exactly where signal drops.

Scheduling and Dispatch

Dispatch

Modules: Service Board and Schedule Optimization (Core).

Service Board is ServiceMax's scheduling environment, with assisted scheduling, crew management and shift plans, asset-centric views, project scheduling that imports from tools such as Microsoft Project and Primavera, and real-time optimisation. Schedule Optimization "automates scheduling and workforce management" (PTC: Service Board). PTC's Spring 2026 release themed this as "Adaptive Scheduling", with a new AI console and current-day optimisation improvements for dispatchers (PTC: What's new).

Installed Base and Asset History

Assets

Modules: Installed Base (Core); Asset Hierarchy, Asset Timeline and Technical Attributes (Asset 360).

The installed base is the list of every serviceable machine at every customer site, with its components, configuration and history. Recent Core releases added product structures and bills of materials, installed base validation against those structures, technical attribute templates and an IB Tree hierarchy view (Core release notes). In Asset 360, Technical Attributes can consume readings from IoT platforms and sensor-equipped equipment. See our post on installed product management and the 360 asset view.

Contracts, Warranties and Entitlements

Revenue

Modules: Entitlements and service contracts (Core); Entitlement Engine, Service Threshold and Contract Negotiated Pricing (Asset 360).

Entitlement checks answer one question before work starts: is this asset covered, and on what terms? Asset 360's Entitlement Engine provides "automated, rules-driven entitlement verification, upon the creation of cases, work orders, and return orders" (PTC: Asset 360). Getting this right stops free work on expired contracts and gives sales a clean list of renewals and upsell opportunities.

Customers, Contractors and Collaboration

Engagement

Modules: Engage, Zinc and Partner Communities (Core).

Engage is a mobile-first app for your end customers: they see appointments, the technician's real-time location and ETA, and asset data, and it can be white-labelled (PTC: Engage). Zinc is a secure messaging and collaboration layer embedded in ServiceMax Go, Engage, Service Board and Salesforce, so technicians reach experts without switching to consumer chat apps (PTC: Zinc). Partner Communities share work orders and asset data with third-party contractors.

Service Analytics

Insight

Modules: Core dashboards and Service Performance Metrics; Asset 360 Service Analytics.

Core ships prebuilt dashboards for first-time fix rate, attach rate, mean time to repair, cost to serve and service profitability (PTC: Core). Asset 360's dashboards cover cost to serve, service profitability, contract, asset and location insights. Because everything sits on Salesforce, these metrics can be reported next to sales and customer data rather than in a separate tool.

What Does ServiceMax AI Add in 2026?

ServiceMax AI is PTC's generative and agentic AI layer for ServiceMax. It launched in February 2025 and reached version 7.0 in October 2026. It gives technicians an AI assistant in ServiceMax Go, Salesforce and Zinc, lets admins build governed AI Actions, and adds a troubleshooting agent and access to knowledge stored in Salesforce, SharePoint and OneDrive.

The product was previewed as "ServiceMax Copilot" in 2024 and launched as ServiceMax AI on 12 February 2025, letting technicians ask about jobs, assets, documentation and scheduling in natural language (PTC launch announcement). Since then PTC has added:

Sources: PTC: ServiceMax AI, ServiceMax AI documentation and AI release notes.

If you run Asset 360, compare this with Salesforce's own Agentforce for Field Service, announced in April 2025 for appointment scheduling, schedule-gap resolution, pre-work briefs, onsite troubleshooting and post-work summaries (Salesforce announcement). Decide which AI layer owns which job before switching both on. As with any AI, results depend on the quality of your work order notes, asset data and knowledge articles.

ServiceMax vs Salesforce Field Service: How to Choose

It is rarely either-or. Salesforce Field Service covers work orders, scheduling, inventory, maintenance plans and an offline mobile app. ServiceMax Asset 360 adds asset, entitlement, returns and depot depth on top of it. ServiceMax Core replaces the execution layer with ServiceMax's own apps. Choose by how central the asset and the contract are to your service.

Salesforce Field Service, now titled Agentforce Field Service and Operations, includes work orders, service territories, inventory tracking, maintenance plans, service reports, a dispatch console, scheduling optimisation and an offline-friendly mobile app, in Enterprise, Unlimited and Developer editions (Salesforce Help). PTC positions ServiceMax as best for "complex, asset-centric service operations with deep lifecycle tracking and contract management". Work through these questions in order:

Pricing is not part of this framework because PTC publishes no ServiceMax price list; quotes come through PTC sales. Budget for the licences of both platforms where Asset 360 is involved.

Is ServiceMax Right for a Growing or Mid-Market Company?

It can be, when equipment complexity rather than headcount drives the need. PTC itself describes ServiceMax as ideal for large, asset-intensive organisations with 50+ technicians, complex equipment and service contracts. A mid-market manufacturer or dealer with fewer technicians but high-value equipment and contract revenue can still justify it; a small, asset-light team usually cannot.

That 50+ technician guidance comes from PTC's own product FAQ (PTC: ServiceMax). In our experience, the better test for growing and mid-market companies is the cost of getting service wrong:

• Strong signals: service contracts are a meaningful share of revenue; warranty leakage or free work is a known problem; regulators or customers expect a full asset service history; parts and returns tie up cash; you manage third-party contractors.
• Weak signals: jobs are short and standard; equipment history rarely changes the fix; scheduling is the main pain. Salesforce Field Service alone, well configured, often solves that.
• Phase it: start with the asset and contract foundation, then add scheduling optimisation, customer apps and AI as volume grows. ServiceMax's modular extensions suit that path.

Which Industries Use ServiceMax?

ServiceMax is built for asset-intensive industries. PTC lists industrial equipment and heavy machinery, medical devices, electronics and high-tech, equipment dealers, oil and gas and energy, and building and construction, including HVAC. What they share is expensive, long-lived equipment where uptime, compliance and contract revenue depend on service.

Industry list and regulated-industry features from PTC's ServiceMax page. For manufacturers, see also our Salesforce for Manufacturing page.

How to Implement ServiceMax: A Practical Plan

A ServiceMax implementation goes best in six stages: discovery and baseline, choosing Core or Asset 360, asset and contract data preparation, sandbox build and integration, a pilot with one team, then phased rollout. A focused implementation for a single business unit typically runs 8 to 14 weeks, and most risk sits in data preparation.

1. 1

   Discovery and baseline. Map service types, contract types, the asset lifecycle and the systems involved (ERP, IoT, billing). Record today's first-time fix rate, mean time to repair, technician utilisation and contract attach rate so you can prove the result later.

2. 2

   Choose the offering. Decide Core, Asset 360 or FieldFX using the framework above, and confirm the editions and licences you need for both PTC and Salesforce.

3. 3

   Asset and contract data. Clean and load the installed base, locations, product structures, warranties and contracts. Entitlements, PM plans, scheduling and AI all depend on this layer.

4. 4

   Sandbox build and integration. Configure work processes, mobile, scheduling and entitlements, then connect ERP for parts, inventory, contracts and financials. Asset 360 runs only in Lightning Experience and its process templates sit in Salesforce Flow.

5. 5

   Pilot. Go live with one region or team, test offline mobile use on real sites, and fix friction before it spreads.

6. 6

   Rollout and optimisation. Move remaining teams in waves, then add Schedule Optimization, customer apps and ServiceMax AI once the basics are stable. Build a regression test pack for every release.

The 8 to 14 week estimate is the range we publish for a focused single-business-unit implementation on our ServiceMax services page; multi-region or heavily integrated programmes take longer. For the Salesforce Field Service side of an Asset 360 project, see our Salesforce Field Service implementation services.

ServiceMax Pitfalls Most Guides Skip

These come from PTC and Salesforce documentation and from what we see in ServiceMax orgs that need rescuing.

How Twopir Consulting Helps With ServiceMax

We implement, rescue, optimize, and integrate complex CRM and revenue systems. For service organisations, that means implementing ServiceMax Core or Asset 360, configuring and extending existing ServiceMax orgs, and connecting them with ERP, billing and the rest of your Salesforce platform. See our ServiceMax implementation and integration services.

A recent example: for a US manufacturing client running Salesforce and ServiceMax, technicians were logging machine hours by hand after every work order. We built an Apex trigger that calculates runtime the moment a work order closes, and a Lightning Web Component dashboard on each installed product that shows usage by machine and date. The result, as published in our ServiceMax utilisation dashboard case study: zero manual meter readings after go-live, with the dashboard updating on every work order close and no middleware to license or maintain.

We work with growing, mid-market, and enterprise organizations. Whether you are choosing between Core and Asset 360, inheriting a ServiceMax org nobody fully understands, or preparing for the 2027 release changes, we start with your service model and the outcomes you need to report, then design backwards.

The Bottom Line

ServiceMax remains one of the most complete options for asset-centric field service on Salesforce, and PTC is still releasing it actively in 2026. The decision that matters most is not whether to use ServiceMax, but which form: Core for ServiceMax's full execution stack, Asset 360 to deepen Salesforce Field Service, or FieldFX for energy services.

1. 1

   ServiceMax is a PTC product built on Salesforce; a Schneider Electric acquisition of PTC is pending, with no announced ServiceMax changes.

2. 2

   Core and Asset 360 differ in data model, mobile app and scheduling. Choose before you build.

3. 3

   Its value is in installed base, contracts, preventive maintenance, parts and returns; asset-light teams may not need it.

4. 4

   Clean asset data, release testing and a measured baseline decide whether the project pays off.

Frequently Asked Questions