An OEM's service contract has a hard job: sold in one company, executed by another, honoured over years on a machine that moves. xMatix makes the contract itself the system of record — created at invoicing, metered by the machine's own life, executed by whichever dealer is closest.
Born at the sale, attached to the asset
Invoicing a contract item — warranty, extended coverage, AMC — creates the service contract on the installed asset automatically: validity derived from the sale, usage-hour and meter windows with grace bands, and the covered scope written out line by line. Entitlements burn down visibly as services consume them.
Metered by time, hours or usage
A genset's contract meters on hour readings, a machine tool's on cycles, a compressor's on the calendar — each captured by the dealer technician on the job and rolled into the contract's position. (The service company's own version of these contract shapes lives on warranty & AMC management for equipment.) The next preventive service is computable from the asset's own readings, not from a spreadsheet's optimism.
Schedules and campaigns that generate the work
Maintenance schedules generate the dealer's job before the failure; service campaigns sweep the installed base — by serial range, model or region — in reminder waves, creating leads and jobs for every asset due. The network's after-sales calendar fills itself; dealers execute; the OEM sees coverage. Renewals surface inside the reminder horizon — while there is still time to win them.
One contract, many payers
Contract posting treatment decides each job line's payer up front — OEM, dealer share, customer — so execution flows into claims and invoices without a negotiation per job. Attach rates and renewal rates become KPIs on the same records that ran the work.
Common questions
How do OEM service contracts get created?
Automatically, at invoicing: contract items on the sale create matching contracts on the installed asset with validity, usage windows, grace bands and scope lines derived from the sale — across the network, without a dealer setting them up by hand.
How does usage-based metering work across dealers?
Dealer technicians capture hour and meter readings on every job; the contract's position updates from those readings, so entitlement, due services and expiry reflect the machine's actual life regardless of which dealer serviced it last.
Can campaigns target part of the installed base?
Yes — campaigns scope by serial or model range, region or contract state and run in reminder waves, generating leads and jobs per matching asset. A safety campaign or a lapsed-AMC win-back is a configured sweep, not a mail-merge project.
How do renewals get chased?
Contracts approaching expiry fall into the reminder horizon and generate renewal leads with the asset's service history attached — the strongest renewal pitch there is, made while the customer is still covered.