An engine does not care what your spreadsheet says. Put its whole service life on one record.

An engine does not care what your spreadsheet says. It has run the hours it has run, been overhauled when it was overhauled, and consumed the parts it consumed — and somewhere between the AMC register, the engineer's diary and the parts godown, most service organisations lose the thread of those facts. Genset service management software exists to hold the thread, and xMatix holds it in production today — engine service jobs, contract management and spare parts run live on this platform, which is why this page can be specific. The organising principle: the asset is the record. Every contract, visit, reading, overhaul and part in its life attaches to it, so the machine's history is a query — not an argument between three registers.

The asset has a service history, not a file

Every genset, engine and machine is an asset record with an identity — serial, model, site, customer — and a life that accumulates on it: commissioning, readings from every visit, jobs done, parts fitted, contracts held. When a customer calls about the DG set at their Pune site, the desk opens the machine and knows more than the customer does: last service, hours at last reading, the injector replaced in March, the AMC's remaining entitlement. Multi-asset customers — the operator with forty gensets across twelve sites — stop being forty separate mysteries, because the fleet view rolls the same records up: which units are due, which sites consume abnormally, which machine is quietly eating parts.

The record starts at commissioning: the installation job that brings a machine into service is itself a dispatched, checklisted, evidence-carrying job, and it creates the asset with its warranty clock started from a recorded fact rather than a remembered one. Service campaigns then work the installed base in waves — the injector-batch inspection across every affected serial, the pre-summer load-test sweep across a region — each campaign a scheduled pass over a defined slice of the fleet, measured by completion rather than by intention.

Contracts that meter and renew themselves

Equipment AMCs are metered promises — services owed by calendar or running hours, whichever arrives first — and a promise nobody meters becomes a dispute. Contracts on xMatix meter themselves: readings captured on every visit drive the projection, entitlements burn down visibly, grace bands absorb the real world's untidiness, and preventive schedules generate the next job before it is due. As expiry approaches, the contract raises its own renewal lead with the asset's history attached — the strongest renewal pitch there is. The honest version of "predictive": not telemetry we do not ingest, but metering against hours and calendar, thresholds that raise a job, and a history that makes the next failure predictable to the engineer reading it. The DG-specific rhythm — dual metering, standby versus prime duty, the 2 a.m. breakdown — has its own page: diesel generator service.

Overhaul jobs: parts, labour and sublet on one record

An overhaul is the heaviest document in the service business — weeks of work, a bill of parts that reads like a purchase order, machining sent out to a sublet shop, and a customer who will question every line. The overhaul job card carries all of it as typed lines: parts issued from stock as consumed, labour by technician with timesheets, sublet work with its vendor cost, photos and readings at strip-down and rebuild. Estimates route through customer approval before the crane moves; variations found at strip-down are added and re-approved rather than argued at billing. When the job invoices, the margin is a fact per overhaul — parts, hours, sublet against price — which is the number overhaul businesses usually cannot produce without a week of forensics. Multiply it across the year and the workshop learns which overhaul classes make money and which have been quietly subsidised by the AMC book — the kind of finding that changes what the sales team is told to sell.

The engineer's visit, offline at site

Genset work happens where the network isn't: basements, plant rooms, sites two hours past coverage. The engineer's day runs on an offline-first app — jobs, asset history, checklists and parts available with zero signal, readings and photos and the customer's signature captured at the machine, everything queued in a durable outbox that syncs on the drive back. Geofenced arrival and disclosed GPS trails make the visit provable when a customer disputes it; the guided checklist makes the service consistent whether it was the senior engineer or the new hire — and technician skills and certifications live on the resource record, so the 500 kVA overhaul is dispatched to someone certified for it rather than someone nearby. The full field mechanics are on field execution — this industry simply uses all of them, hard.

Spare parts across the service network

A machine down for want of a part costs more than the part ever will, so the parts picture has to be network-wide: central store, branch stock, and the engineer's van as a real inventory location — because the part on the back seat is stock, not a rumour. Replenishment projects from consumption, so fast-movers reorder from evidence; a down machine raises its part's urgency from the job itself; and consumption reconciles per job, which ends the quiet leak of parts that left the store but never reached an invoice. Batch and serial identity survive every movement, so the injector's provenance is on record when the warranty question comes.

Billing, warranty and the books

Every job ends in money moving correctly: covered lines consume contract entitlement, warranty lines become claims with the evidence attached, chargeable lines invoice with GST split correctly across parts and labour — and all of it posts to real books as it happens, so the service business's profitability is readable per contract, per overhaul and per customer rather than guessed at year-end. Estimates for chargeable work route through customer approval before the work — on the portal or at the machine — and the approval stamps the document and its lines, which is what keeps the 90-day-credit corporate account from becoming a 190-day argument. The commercial machinery — schemes, claims, dealer settlements — is the same engine the rest of the platform runs, which is why a service organisation that also distributes parts or machines does not need a second system for the second business. A multi-branch operation runs branches as locations on one ledger — each with its stock, engineers and jobs, all consolidating without a spreadsheet — and the regional manager reads utilisation, contract coverage and parts exposure per branch from the same records the branches work in.