ServiceMax

Current owner: PTC Inc., since January 2023. That is the question this product most needs answered, because it has changed hands repeatedly. The reported chain is: independent ServiceMax, acquired by GE Digital in 2016 for a reported 915 million, then held by a Silver Lake majority-owned entity, then acquired by PTC which completed the purchase on 4 January 2023 for a reported 1.46 billion. No ownership change after 2023 was found in any source. servicemax.com now 301-redirects to ptc.com/en/products/servicemax. PTC own press releases confirming this are behind a 403, so the ownership fact here rests on trade press plus the absence of any later sale report.

This profile is deliberately thin, and the reason is a block. ptc.com returned HTTP 403 on every path tried, in four locales, including the product page, the company facts page and a 2026 news item. support.ptc.com has reachable ServiceMax Core help pages, but only narrow customisation topics. The consequence is that almost every functional capability is recorded as unknown. Work orders, scheduling, dispatch and invoicing are described in PTC product-page copy that surfaced in search results, but because that page was never opened, those capabilities are not recorded as supported. That is the rule working as intended, and it is better than publishing a full profile built on search snippets.

What could be verified is the extension surface and the architecture. PTC publishes a ServiceMax API section documenting Apex utilities intended for public use, plus a JavaScript snippet API. The help set path is literally servicemaxcore, and the customisation documentation is Apex and Visualforce based, which confirms the product runs on the Salesforce platform. That is architecturally important for buyers: Salesforce-native admin, security and ecosystem tooling carry over, but Salesforce platform licensing and governor limits become part of your total cost and your design constraints.

• Four owners in roughly seven years is a real roadmap-continuity question to put to PTC directly, not a reason to rule the product out.
• Asset 360 is not confirmed as a current product name. It appeared only in an older executive interview, so it is not used here.
• No pricing is obtainable either. PTC pricing pages are inaccessible, so this profile records no figure. Review aggregators do publish figures for ServiceMax, and they are excluded deliberately: a product that has changed hands four times is exactly the case where aggregator pricing is most likely to describe a commercial arrangement that no longer exists.

Good fit: enterprise, asset-heavy service organisations, which is how PTC positions it: manufacturers, medical device companies and industrial equipment makers servicing a serialised installed base. Organisations already running Salesforce have a genuine advantage, since the product is built on that platform and the admin, security and extension model is familiar. Organisations already running PTC for PLM or IoT have a second reason to look, since the acquisition rationale was joining service data to product data.

Poor fit: small and mid-size contractors, by positioning. Also a poor fit for anyone who wants to shortlist from published evidence, because PTC web properties are closed to automated and public reading, and no pricing, no feature documentation beyond customisation topics and no offline specification could be obtained. Buyers who are not already Salesforce customers should price the underlying Salesforce platform licences before comparing against products that do not carry that dependency.

Typical use cases: OEM and manufacturer installed-base service, medical device field engineering with compliance record-keeping, and industrial equipment service where asset history matters more than route density. Treat every functional requirement as something to demo rather than something this profile can confirm, and ask PTC directly about roadmap continuity given the ownership history.