Aftermarket service software for OEMs

A service call begins with a machine and a customer problem. It can touch entitlement, diagnosis, engineering, skills, schedule, travel, van stock, supplier parts, safety, field work, customer acceptance, asset configuration, invoice and follow-up. The next contract renewal or upgrade proposal depends on what happened in that chain.

No software category owns all of it by default. ERP and enterprise service suites control inventory, contracts, costing and billing. Field-service products control work orders, dispatch and mobile execution. PLM controls service definition and product configuration. Aftermarket specialists handle parts planning, price and warranty. CRM controls the account and pipeline. OEMs often buy one product and discover that employees still bridge the gaps by email and spreadsheet.

This guide compares Bourne, IFS Cloud, ServiceMax, Dynamics 365 Field Service, SAP, Oracle, Syncron and Makula. It also gives you one evaluation process that follows real service work from request to cash and back into the installed equipment record.

Start with the service business you want to run

Software should support the commercial model, not force every job into break/fix field service. List the offers you sell now and the offers you plan to sell in the next three years. The data, schedule, coverage and billing rules differ.

The shortlist

These products have different centers. Use the strongest-fit column to decide which products deserve a full demonstration. Do not send a generic request for information to all eight.

A complete service chain has twelve handoffs

Map the handoffs before product selection. A field-service demo often begins after triage and ends at technician signature. The OEM still has to decide coverage, get a part, update the machine, bill correctly and turn the result into the next commercial action.

1. Bourne: best when people still connect the service stack by hand

Bourne fits an OEM that already owns service, ERP, PLM and CRM systems but cannot get one piece of work through them without manual search and rekeying. It reads the customer request and service files, identifies the installed asset, assembles configuration and coverage, pulls product and part evidence, and prepares the next action for the responsible person.

A support engineer can receive an email with a photo and alarm code. Bourne can match the customer and asset, retrieve the relevant service history and current configuration, find the procedure and similar resolved cases, check contract coverage and draft the remote steps or field-service scope. If the customer needs a visit, the case can create the work order with the evidence already attached.

After completion, Bourne can read the technician debrief, reconcile parts and labor, prepare the asset update, identify a repeat failure and create the warranty, engineering or commercial follow-up. People approve uncertain diagnosis, configuration change, coverage and customer communication.

Choose Bourne when your bottleneck sits between systems and in unstructured evidence. If you have no work-order, inventory, contract or billing backbone, implement that foundation too. Bourne can coordinate it, but finance and inventory still need systems built for those records.

2. IFS Cloud: best for an integrated service business

IFS Cloud combines installed-base objects with service requests, work tasks, planning and scheduling, mobile work, contracts, parts, repair, projects and financials. The same service object can carry model, part, serial, parties, skills, measurements, recurring service, history, costs, contracts and recommended spares.

IFS service-object documentation shows that depth at the asset level. The wider suite supports the transaction chain around it. An OEM can design the service offer, register the request, evaluate the object and contract, schedule work, consume parts, record cost and bill without handing the job across unrelated vendors.

IFS is strongest for companies that want service as a core enterprise operation and accept a broad implementation. It also supports complex equipment, mobile work and outcome-oriented service better than a light ticket-and-dispatch product.

Test contract and project economics on your service model. Show planned versus actual labor and material, SLA performance, subcontracted work, travel, warranty recovery and revenue recognition. Then test how the result updates the installed object and feeds product improvement.

3. ServiceMax: best for asset-centric field execution

ServiceMax is purpose-built for field service around high-value equipment. It covers installed-base visibility, work orders, scheduling, mobile and offline execution, preventive maintenance, parts, returns, depot repair, contracts, warranties, entitlement and service analytics.

ServiceMax Asset 360 adds multi-level asset hierarchy, asset timeline, IoT attributes, contract and warranty automation, service thresholds, return flows, depot repair and maintenance templates on Salesforce Field Service. ServiceMax Core provides its broader field-service suite with asset lifecycle, mobile, parts, customer engagement and analytics.

ServiceMax is a strong choice when field execution and service profitability cause the pain. The product gives technicians and dispatchers an asset-centered operation and gives service leadership contract, coverage and cost-to-serve views.

Test the boundary with engineering, supply chain and finance. Show how the as-built and current configuration arrive, how a replacement changes PLM and ERP, how pricing and tax enter the quote, and how the invoice posts. The field workflow can be excellent while the complete OEM chain still depends on those integrations.

4. Dynamics 365 Field Service: best for Microsoft-centered service operations

Dynamics 365 Field Service provides customer assets, work orders, scheduling, mobile execution, inventory, purchasing, returns, agreements, entitlements, IoT alerts and Power Platform automation. It fits companies already using Dynamics 365 Sales, Customer Service, Business Central, Project Operations, Microsoft 365 and Azure.

Microsoft’s work-order architecture ties the service account, customer asset, location, products, services and tasks together. Agreements can generate recurring work and invoices, while entitlements alter work-order pricing. Connected Field Service can turn an IoT alert into a case and work order.

Choose Dynamics when the Microsoft platform already carries customer and operational context and your team can configure the OEM-specific model in Dataverse and Power Platform. It offers a capable field-service base without requiring Salesforce or a full IFS program.

Review the financial target architecture carefully. Microsoft states that the current Field Service and finance and operations integration will end on February 28, 2027 and is moving toward Field Service and Project Operations integration. Use the current documentation for the exact release and products you plan to deploy.

5. SAP: best when service must use the SAP backbone

SAP can connect equipment and functional locations to service and maintenance orders, materials, inventory, contracts, pricing, finance and field execution. SAP Field Service and Asset Management adds dispatch, technician workflows, mobile work and service contracts around S/4HANA master and transaction data.

SAP publishes a field map between S/4HANA and Field Service and Asset Management for equipment, functional locations, service orders, service contracts, parts, stock and confirmations. Its service-contract model supports recurring and non-recurring agreements and can define included materials.

SAP is the logical first evaluation for a manufacturer that already runs SAP material, serial, customer, service, supply chain and finance. Native records and financial controls can outweigh a cleaner standalone field-service interface.

Demand one architecture, not a list of SAP capabilities. Name the owning product for request, installed asset, contract, schedule, mobile job, parts, confirmation and invoice. Run the same service event across that target design and show latency, errors and reconciliation.

6. Oracle Fusion: best for service logistics and Oracle supply chain

Oracle’s service story becomes strongest when the job depends on Oracle product data, inventory, sourcing, pricing, order management, maintenance, contracts and billing. Oracle Service Logistics connects field work to the supply-chain and financial transactions that make service economically complete.

Oracle Service Logistics lets technicians or administrators source and order parts, record labor and expense, update inventory and installed-base configuration, calculate charges and create billing data. It can work with Oracle Field Service and third-party service requests and work orders.

Choose Oracle when the company already runs Fusion SCM and wants service parts, returns, depot repair, cost and billing inside that backbone. The value lies in the transaction chain, especially for service organizations with complex part movement.

Test the CX boundary. Oracle documents a choice between the installed-base asset and the default asset object in B2B Service, with limits on sales and extensibility for the installed-base option. Show how the same asset supports service, contract, aftermarket sales and account work in your chosen design.

7. Syncron: best for the economics of the aftermarket

Syncron focuses on the domains that determine parts and warranty profitability: service-parts planning, parts pricing, dealer inventory, warranty and contract management. It is less of a general work-order system and more of an aftermarket decision and transaction suite.

Syncron’s current product portfolio covers demand and stocking across a parts network, value-based and segmented parts pricing, dealer inventory and warranty claim control. That makes it relevant to OEMs whose largest aftermarket problem sits in availability, excess stock, price leakage, claim leakage or supplier recovery.

Choose Syncron when parts or warranty economics justify specialist depth. A global equipment OEM can pair Syncron with SAP, Oracle, IFS, Salesforce or another system that runs the asset and field work.

Test the data contract between products. Which installed-base and usage data drives parts demand? Which supersession and service BOM governs fit? How do approved prices reach quotes and orders? How do warranty findings and recoveries return to finance and engineering? Specialist value depends on clean operational feeds and write-back.

8. Makula: best for a focused machinery service operation

Makula provides a machine-centric installed base, documents, preventive maintenance, tickets, work orders, service reports, customer portal and aftermarket views for machinery manufacturers and distributors. It gives a smaller service organization a coherent product without the breadth of IFS, SAP or Oracle.

Makula’s installed-base module organizes equipment by customer and site, links machine-specific documents and service history, manages preventive plans and exposes service and commercial context. The customer portal and distributor orientation suit OEMs that share service with channels and customers.

Choose Makula when the current process lives in spreadsheets, PDFs, folders and basic ERP records and the team needs visible improvement quickly. The product can become the working service layer without a multi-year enterprise transformation.

Test complexity early. Use the largest equipment hierarchy, hardest contract, offline site, dealer boundary and ERP integration in scope. Show part fit, serialized component movement, global permissions and historical configuration. A fast start only helps if the model survives the real machine.

Field service software is only one part of aftermarket service

A dispatcher can schedule the right technician and still send the wrong part. A technician can close the job and still leave the installed configuration stale. Finance can invoice accurately while sales misses the renewal. Engineering can issue a bulletin while nobody identifies the affected fleet.

Decide which adjacent products the service platform must connect. The deeper the equipment and offer, the less credible an isolated field-service purchase becomes.

Test entitlement before dispatch

Revenue leaks when the service team decides coverage after the work. The system should evaluate the exact asset or component, contract, warranty, customer, service type, date, usage, response level, labor, travel, part and prior consumption before commitment.

Use three cases in the demo: a fully covered repair, an excluded failure and a job where two coverages may apply. Ask the product to explain the decision and price the uncovered scope. Then change one fact, such as operating hours or unauthorized modification, and show the new result.

Test parts from diagnosis through reconciliation

Parts create several distinct questions: which part fits, whether a successor needs a kit, where stock exists, when it can arrive, what it costs, what to charge, which serial entered the machine and what happened to the removed unit. One green “parts management” box cannot answer them.

Run one advanced exchange. The system should reserve or source the replacement, ship it, track the defective return, receive and inspect it, decide repair or scrap, settle any core charge, update inventory and record the installed and removed serials against the asset. This scenario separates field-service inventory from a complete service logistics process.

The next article on spare-parts quoting for industrial equipment goes deeper on fit, supersession, availability and price.

Test the mobile closeout that updates the machine

Give the technician the real offline conditions, equipment hierarchy and form length. They should identify the target object, see the relevant history and procedure, record measurements, consume parts, scan serialized movement, add evidence, capture customer acceptance and note remaining work.

The closeout should update service history, physical configuration, meter, inventory, cost, entitlement consumption and billing support without another employee interpreting a PDF report. If a field change needs engineering approval, route it before the system changes the governed state.

Make service profitability visible by asset and contract

Revenue by service department hides bad contracts and bad machines. Track quoted, contracted, delivered, accrued and billed value against the asset, customer, contract and work. Include labor burden, travel, parts, freight, subcontractor, concession, repeat visit and warranty recovery.

Then separate performance by offer. A preventive contract may look profitable until emergency callouts and unrecovered travel enter. A break/fix customer may produce strong parts margin but consume technical support that nobody records. The software should let finance and service see the full delivery cost without turning every technician into an accountant.

Include customers and channel partners in the design

A portal should do useful work. The customer should identify the asset, submit evidence, see entitlement and schedule, approve a quote, access the right documents, track work and confirm completion. Dealers need scoped access to their accounts and machines, with a path to report service, parts and configuration changes back to the OEM.

Test permissions with an ownership transfer, multi-site account, dealer-serviced machine and third-party technician. A portal that exposes every asset under the sold-to account can leak information across business units or owners. A portal that cannot update the OEM record becomes another stale view.

Treat AI claims as workflow tests

“AI scheduling,” “AI service” and “copilot” can mean a summary, a forecast, a scheduling solver or an agent that completes work. Ask the product to perform a bounded task on your records. Diagnose the request. Select the affected asset. Find the applicable contract. Check a part. Draft the field scope. Explain every source and stop when evidence conflicts.

The strongest AI result reduces skilled search and preparation while leaving material judgment with the right person. A generic work-order summary saves little if the engineer still opens six systems to decide what the technician should do.

Use an ownership map instead of a connector list

For each object, name one owner: customer, site, installed asset, product definition, part, inventory, contract, work, schedule, cost, invoice, device and opportunity. Then map events across them. A connector logo does not explain whether an update is one-way, nightly, recoverable or authoritative.

Worked example: a press line stops on second shift

At 9:14 p.m., a customer emails the OEM’s support address with a phone photo of alarm E-417 and a short note: the transfer press stops after the lubrication cycle. The customer names the plant and line but not the machine serial. The service system must match the sender, site, line position and installed equipment before anyone promises a response.

The installed record shows two presses at the site. Only one occupies Line 3 / Transfer. Its current configuration includes controller software 8.2, lubrication manifold LM-44 Rev C and a customer-approved guarding modification. The service contract covers remote support around the clock and field labor the next business day. Parts and travel remain billable. The last three work orders show one low-pressure event but no repeat E-417 alarm.

Remote support asks the customer for the lubrication-pressure trend and a photo of the local indicator. The pressure drops during the cycle. Engineering confirms that alarm E-417 on software 8.2 can follow either a failed pressure switch or a sticking manifold valve. The system prepares two diagnostic checks from the correct service procedure. The customer performs the first safely with remote guidance and confirms that the switch changes state. The manifold needs field inspection.

Scheduling finds a technician with press and hydraulic authorization, checks the SLA and assigns the next morning. Parts planning identifies the current valve and its approved successor. The successor requires seal kit SK-18 for Rev C manifolds. A regional depot has both. The job reserves the valve and kit, shows the covered labor and priced parts, and sends the customer the arrival window and parts estimate for approval.

The technician works offline inside the plant, records contamination at the valve, replaces it, scans the installed part and captures the pressure test. Closeout consumes the depot stock, adds labor and travel, updates the manifold position, stores the removed valve for supplier analysis and creates the billable lines. The asset history now shows the exact valve and test result.

The process does not end at signature. Warranty checks whether the supplier covers the failed valve. Engineering receives the contamination finding with the affected part revision. Account management receives a proposal task for the filtration retrofit already approved on newer machines at the site. A complete aftermarket platform must move this one event through technical, field, supply, financial and commercial work without losing the asset context.

Recommendation by situation

Choose IFS when you want one broad service and enterprise backbone. Choose ServiceMax when asset-centric field execution, entitlement and mobile work lead the requirement. Choose Dynamics 365 when Microsoft already anchors customer and operational applications and your team can configure the OEM layer. Choose SAP or Oracle when either vendor already owns the supply-chain and financial transaction path.

Choose Syncron when parts planning, parts price or warranty economics create the largest opportunity. Choose Makula when a machinery OEM needs a focused installed base, portal and service operation with a smaller implementation. Choose Bourne when the products already exist and the missing layer is the intelligence and workflow that turns their records, documents and people into one completed service or commercial action.

Many mature OEMs will use two or three of these categories. The architecture works when each product owns a clear record or decision and the service event closes across all of them.

Run the pilot on a real service event

Select one product family, one active customer contract and ten to twenty recent cases. Include a remote resolution, covered field repair, uncovered repair, missing part, advanced exchange, dealer job and engineering escalation. Reproduce them in each finalist and then run one new case live.

Measure elapsed time, skilled preparation time, avoidable handoffs, part readiness, entitlement accuracy, technician rework, closeout completeness, invoice delay and installed-base update. Price the integration and operating work needed for that exact flow.

The pilot passes when the team can accept the request, make the service decision, execute the work, post the financial result, update the equipment and trigger the next action without rebuilding context between steps.

Buğra Gündüz

Buğra Gündüz is the co-founder and CEO of Bourne and co-founder of HockeyStack. He built HockeyStack into an eight-figure AI business. At Bourne, he works with entrepreneurs and established companies to create AI products and services.