ServiceMax Asset 360: worth adding to Field Service?

ServiceMax Asset 360 is a managed package from PTC that adds asset functions to Salesforce Field Service: an entitlement engine, maintenance plans based on time, condition or IoT data, technical attributes and more than 60 preconfigured workflows. It stores everything on Salesforce’s standard objects and requires Service Cloud and at least one Field Service licence. Since 2024 Salesforce has sold its own add-on for similar tasks, Asset Service Lifecycle Management. I would look at Asset 360 when automatic entitlement checks or PTC PLM tip the balance, and evaluate the Salesforce add-on first otherwise.

What is ServiceMax Asset 360 for Salesforce?

ServiceMax has two products on Salesforce. ServiceMax Core brings its own data model; I compare it with Salesforce Field Service in ServiceMax vs Salesforce Field Service: which one?. Asset 360 takes the other route. The AppExchange listing1 describes it as natively built on Salesforce Field Service, and PTC’s documentation shows how: the work order2 is the standard WorkOrder object, and Asset 360 adds its own fields with the SVMXA360 namespace.

For you this means: dispatchers keep planning with Salesforce’s scheduling engine, technicians keep working in the Salesforce Field Service mobile app. Asset 360 puts its workflows on top. The requirements are in the ServiceMax SaaS Service Description3 of 1 February 2025: Service Cloud, at least one Field Service licence and an active Salesforce agreement for the whole term.

1. Sep 2020Asset 360 for Salesforce launches on AppExchange
2. Jan 2023PTC completes the acquisition of ServiceMax
3. Mar 2024Release 24R1 brings workflows into the Field Service app
4. Mar 2026Release 26R1 (version 14.0)
5. Sep 2026Release 26R2 (version 15.0)

Asset 360 adds an entitlement engine and more than 60 workflows

The product page4 names four areas. I checked them against the documentation:

• Entitlement engine. According to the documentation5 it checks on cases, work orders and return orders which service the customer is entitled to. In interactive mode it lists all matching warranties and service contracts; in automatic mode it picks one by rule. If an asset has both a warranty and a contract, you decide which takes priority. One limit is stated explicitly: the engine does not handle entitlements linked directly to an account or asset without a service contract.
• Installed base. A view of the asset, its subcomponents, service history and contract coverage.
• Maintenance planning. Plans based on time, frequency, condition or IoT data, with templates and automatically created work orders.
• Preconfigured workflows. PTC names more than 60. Since release 24R1, Service Process Manager and wizards run in the Salesforce Field Service mobile app according to PTC’s blog6, with technical attributes on site. Release 24R2 added connections to Windchill and Servigistics7.

If you know the maintenance plans in the base licence, you see the overlap: Field Service handles maintenance by operating hours itself, see usage-based maintenance. The added value of Asset 360 lies in entitlement checks and the ready-made workflows.

Where does Asset 360 overlap with Asset Service Lifecycle Management?

In several places. Salesforce announced Asset Service Lifecycle Management (ASLM) as an add-on in June 2024 and sells it at $75 per user and month. Its contents are in Asset Service Lifecycle Management: worth the add-on?. The comparison based on both vendors’ documents:

Area	ServiceMax Asset 360	Salesforce ASLM
Entitlement check	Engine, interactive and by rule, on case, work order, return	Asset Coverage View with selection on case or work order
Asset hierarchy	View of subcomponents	Interactive hierarchy
Campaigns	Product service campaigns with search by technical attributes	Product service campaigns
Returns, depot	Automated return and workshop processes per references	Depot repair, advanced exchange
PLM	Windchill, Servigistics	No PLM connection of its own
Vendors	PTC and Salesforce	Salesforce
Price	Not published	$75 per user and month

Both work on the same standard objects. If you buy both, you get two solutions for coverage checks in one org. Decide per workflow which one owns it.

What I have seen with entitlement checks

I have not implemented Asset 360 myself. From this experience I take two checks. First: if your entitlements hang directly on the asset or account without a service contract today, the engine does not fit without rework, according to the documentation. Second: return and inventory workflows in Asset 360 meet an ERP that owns stock. Where I draw that line is in Spare parts between ERP and Salesforce.

A second managed package adds two releases a year

According to its release schedule8, Asset 360 ships twice a year: 26R1 on 5 March 2026, 26R2 on 9 September 2026. Patches only ship when agreed fixes are due. Salesforce ships three times a year. PTC publishes an assessment of the Salesforce release updates9 for each round, which helps with testing. Your team still tests two packages against every Salesforce release.

Then there are the contract points from the service description. The availability commitment of the PTC agreement does not apply to the ServiceMax suites, and Salesforce is responsible for the Salesforce environment. There is no public price. The AppExchange listing says from $50 per user and month but was last updated in 2022. I would not plan with that figure.

When is Asset 360 worth it?

In my view in three cases:

1. Entitlement checks should run automatically. If the help desk and dispatch should get warranty or contract by rule on every order, the engine is the strongest point.
2. Your PLM and spare parts planning come from PTC. Then the connections to Windchill and Servigistics are a real advantage.
3. You want ready-made workflows instead of custom builds. More than 60 preconfigured workflows save build time if your processes fit them.

If none of these applies, I would evaluate ASLM first. One vendor means less coordination, and there is no second managed package to test twice a year.

List your own asset workflows

1. List your asset workflows: coverage checks, maintenance, campaigns, returns, depot.
2. Check where your entitlements sit today: on the service contract, the asset or the account.
3. Request quotes for Asset 360 and ASLM and ask which users need a licence in each case. The role logic of Field Service is in Salesforce Field Service licences by role.
4. Calculate both options over three years including release testing. How I set up such comparisons is described under make-or-buy and licence forecasts.

Sources9

1. 1AppExchange listing (opens in a new tab)appexchange.salesforce.com
2. 2work order (opens in a new tab)support.ptc.com
3. 3ServiceMax SaaS Service Description (opens in a new tab)ptc-p-001.sitecorecontenthub.cloud
4. 4product page (opens in a new tab)ptc.com
5. 5documentation (opens in a new tab)support.ptc.com
6. 6PTC’s blog (opens in a new tab)ptc.com
7. 7connections to Windchill and Servigistics (opens in a new tab)arcweb.com
8. 8release schedule (opens in a new tab)support.ptc.com
9. 9assessment of the Salesforce release updates (opens in a new tab)support.ptc.com