The Installed Base Is Usually Worth More Than the Original Sale
Every unit you shipped is a stream of contracts, spares and chargeable visits running for a decade or more. Most manufacturers cannot collect it properly, because nobody can say with confidence what is out there, who is still in warranty and what was done on the last visit. That is a record problem before it is a scheduling problem. The service module fixes the record first.
50+ ERP and software projects. Zero failed projects since 2021.
Most service operations do not have a scheduling problem
They have a data problem. Once entitlement, the installed base and parts are accurate, a great deal of the scheduling difficulty resolves itself. Buying sophisticated route optimisation on top of an installed base record nobody trusts is the wrong order, and it is an expensive way to find that out.
If you cannot name the unit, you cannot bill the visit
The foundation of the module is a serialised record of every unit sitting at a customer site: model, configuration and options as sold, install date, commissioning record, warranty terms and the full service history against that specific serial number. Without it, nobody can answer the only question that matters when the phone rings, which is whether this job is covered or chargeable. That gap is exactly where revenue leaks, quietly, one job at a time, and it never appears in a report because the work was simply never invoiced.
- Serial, configuration and install date per unit, not per customer.
- Warranty term and expiry held against the unit, not in a folder.
- Every visit, part and fault written back to the same record.

Decide entitlement when the job is raised, not on site
This is the single most valuable control on the page. The system should determine entitlement at the moment the ticket is logged, by reading the serial number, the warranty term and any active contract covering that unit or site. It should not be left to an engineer guessing in a plant room, and it should not be settled by an administrator arguing with a customer three weeks after the visit, because that argument is one you usually lose. Unbilled chargeable work is the largest and quietest loss in most service operations, and it is the easiest one to stop.
- Entitlement returned automatically at logging, printed on the job card.
- Contract inclusions and exclusions applied as rules, not as memory.
- Out of warranty and out of contract work quoted before dispatch.

Six areas, from the installed unit to the paid invoice
Each one feeds the next. Break the first and the last one stops working, which is why service operations that start with dispatch software rarely see the margin improve.
The service call cycle, request to invoice
What we set up when we configure this module
Installed base register
Serial numbers, configuration as sold, install and commissioning dates, warranty terms and full service history against each unit at each site.
Contract and SLA rules
Coverage, response and fix targets by severity, inclusions and exclusions, preventive visit schedules and renewal dates with escalation on price.
Automatic entitlement check
Warranty, contract or chargeable decided at logging from the serial number, printed on the job card and carried through to the invoice.
Dispatch board
Engineer diaries with skills, certifications and geography, part availability checked before release, and deliberate slack held for emergency calls.
Mobile job record
Unit history and documentation on the device, parts and time booked against the job, photos and signature captured, all of it working offline.
Van stock control
Each vehicle as a stock location with min and max levels, replenishment from the main store, and a counting cycle so shrinkage shows up early.
What a properly run service operation looks like
What this connects to
Service starts where the sale ends, shares its disciplines with plant maintenance, and gets quieter when routine requests are triaged before they reach a person.
Why teams bring us in to set up service
Service management questions
How does the system decide whether a job is warranty, contract or chargeable?
Can engineers work offline in the field?
How are parts used on site tracked?
How are service contracts priced and renewed?
How is this different from an internal IT helpdesk?
How does a completed service job become an invoice?
Find Out What Your Installed Base Is Worth
Book a free consultation. We will look at how you record units in the field, how entitlement is decided today, how parts move through your vans and how long a completed job takes to reach an invoice, then tell you straight where the money is going.
Book a Free Consultation →No commitment. A practical review of your service operation, whichever ERP you run.
What the Service Module Actually Does
The record of what you have out there, the rule that says who pays, the board that sends the right engineer with the right part, and the invoice that follows within days. Here is how each of those is built, and where they usually break.
From the serialised unit to the paid invoice
One record that decides who pays for the visit
Every unit at a customer site carries its serial number, the configuration and options as sold, its install and commissioning dates, the warranty term and the full history of faults, parts and visits. Contracts sit on top: coverage, response and fix commitments by severity, inclusions and exclusions, preventive visit schedules and renewal dates. When a ticket is raised against a serial number, the system reads all of that and returns warranty, contract or chargeable before anyone leaves the depot.
- Serialised units with configuration, install date and warranty expiry.
- Contract terms held as rules the system applies, not as a PDF.
- Entitlement resolved at logging and carried onto the invoice.

Resolve it on the phone, or send the right van once
Requests arrive by phone, email or portal and are graded by severity against the contract. First line tries to close it remotely, because every job resolved without a van is the cheapest job you will ever do, which makes first-line resolution rate a real measure rather than a vanity one. What is left goes to the board, matched on skill and certification, travel time and geography, with part availability confirmed before release. Be honest about utilisation: a schedule packed to 100 percent collapses the first time a job overruns.
- Severity and response clock set from the contract at logging.
- Skills, certifications and geography matched before the job is released.
- Deliberate slack in the day so emergency calls do not break the schedule.

The engineer captures it once, billing releases it
On site, the engineer opens a mobile job record holding the unit history and documentation, books parts out of van stock against the job, records labour and travel time, takes photos and captures a customer signature, all of it working offline because signal is not guaranteed in a plant room. Each van is a stock location with levels, replenishment from the main store and a counting cycle. Billing then converts the job into an invoice for labour, parts, travel and callout within days, while the detail is still fresh enough to defend.
- Offline mobile job record with history, drawings and signature capture.
- Van stock as a real location, replenished and counted like any other.
- Invoice raised from the job, not rebuilt from notes weeks later.

Everything the module delivers
Serialised installed base
Every unit at every site, with configuration as sold, install date, warranty expiry and its own fault and repair history.
Contracts with live SLA clocks
Response and fix targets by severity, inclusions, exclusions, preventive visit schedules and renewal dates with priced escalation.
Multi-channel ticket intake
Phone, email and customer portal logging into one queue, with a first-line attempt to resolve before a job is created.
Skills-aware dispatch board
Certifications, travel time, geography and part availability weighed together, with slack reserved for emergency calls.
Offline mobile app
Job history, documentation, parts, time, photos and customer signature captured without signal and synced on reconnection.
Service performance reporting
First-time fix rate, SLA attainment, mean time to repair, engineer utilisation and margin per contract, all from the job record.

