Skip to main content
Service Management

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.

Dispatch Board, Tuesday
Illustrative
08:0011:0014:0017:00
A. Mehta Refrigeration, F-Gas
Northvale Foods 08:15 to 11:00
Harrow Cold Store 12:30 to 15:00
R. Okafor Controls, HV ticket
Belsize Mills, PM visit 08:30 to 10:30
Quay Packaging 11:45 to 15:30
S. Kaur Mechanical, Level 2
Ardenne Bakery 09:00 to 11:15
Slack held for emergencies
Unassigned Needs F-Gas, part on van
Linfield Dairy, line down 4 hour SLA, contract
Entitlement is checked at logging, so the board already knows which jobs are chargeable.
2x
Cost of a repeat visit
1st
Time fix is the headline measure
4x
Van stock counts a year
0
Failed projects since 2021
Why It Matters

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.

The Installed Base

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.
Serialised equipment installed at a customer site with its service history record
Warranty, Contract or Chargeable

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.
Checking warranty and service contract entitlement before dispatching an engineer
What It Covers

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.

📌
Installed base and warranty
Serialised units at customer sites with configuration as sold, install and commissioning dates, warranty start and expiry, and the complete fault and repair history per unit. The record everything else reads from.
📜
Service contracts and entitlement
Coverage terms, response and fix time commitments, inclusions and exclusions, scheduled preventive visits and renewal dates. Entitlement resolved automatically the moment a job is raised against a covered unit.
📞
Ticket logging and triage
Requests captured from phone, email or a customer portal, graded by severity against the contract, and pushed through a first-line attempt to resolve remotely before anything is booked into an engineer diary.
📅
Scheduling and dispatch
Matching skills and certifications to the fault, travel time and geography, and confirming the part is on the van before anyone sets off. Utilisation targets balanced against the slack that emergencies need.
🔧
Field execution and van stock
A mobile job record with unit history and drawings, parts booked out of van stock against the job, time recorded, photos and a customer signature captured, and the whole thing working without signal.
💳
Service billing and profitability
Labour, parts, travel and callout converted from the completed job into an invoice within days. Margin reported per contract and per customer, so a loss-making agreement is visible before it renews.
How It Works

The service call cycle, request to invoice

1
Log the request
Phone, email or portal, captured against a serial number and a site, with severity set from the fault and the contract rather than from how loudly it was reported.
2
Check entitlement
Warranty, contract or chargeable, resolved automatically from the unit record. Chargeable work gets a rate and a quote before an engineer is committed.
3
Schedule and dispatch
Skill and certification matched to the fault, travel and geography weighed, part availability confirmed on the van or reserved from the store, then the job is released.
4
Complete on site
History and documentation on the device, parts consumed booked against the job, labour and travel time recorded, photos taken and the customer signature captured offline.
5
Invoice and close
Labour, parts, travel and callout billed on the entitlement already decided, the unit history updated, and SLA attainment and first-time fix recorded against the job.
What Is Included

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 Changes

What a properly run service operation looks like

Higher
First-time fix rate
Billed
Chargeable work, not written off
Lower
Mean time to repair
Visible
Margin per service contract
Counted
Stock on every van
Days
From job complete to invoice
Why Us

Why teams bring us in to set up service

1
We build the installed base first
Before any scheduling work, we reconstruct what you have out there from despatch records, invoices and engineer knowledge. Nothing downstream is reliable without it.
2
Entitlement is automated, not trusted to memory
Warranty and contract rules are configured as rules the system applies at logging. Engineers and administrators stop making commercial decisions on the fly.
3
We price the mobile app on speed
If a job takes twenty seconds to open, your engineers will use paper. We test the field app on real devices in bad signal before anyone signs off on it.
4
Van stock treated as real stock
Each vehicle becomes a location with levels, replenishment and a counting cycle, because spares that live in vans and are never counted are spares you are losing.
5
Honest about utilisation
A schedule packed to 100 percent collapses the first time a job overruns. We set a target that leaves room for the emergency call your contracts have promised.
6
Platform neutral advice
We deliver on ERPNext, Odoo and SAP. We will tell you where each one is weak on field service and what it will cost you to close the gap.
FAQ

Service management questions

How does the system decide whether a job is warranty, contract or chargeable?
By reading the serialised unit. When the ticket is raised against a serial number, the system looks up the install date, the warranty term attached to that model and any active contract covering that site or that unit, and returns an entitlement before anyone is dispatched. The engineer sees the answer on the job card and the invoice is raised on the same basis. The point is that the decision is made once, automatically, at logging time. If you leave it to an engineer standing in a plant room, or to an administrator arguing three weeks later, you will write the work off. Unbilled chargeable work is the largest and quietest loss in most service operations.
Can engineers work offline in the field?
Yes, and you should insist on it. Plant rooms, basements, lift shafts and rural sites do not have reliable signal, and a mobile job record that needs a connection to open is useless in exactly the places engineers work. The app should hold the day's jobs, the unit history and the documentation locally, accept parts, time, photos and a customer signature offline, then sync when the device gets a connection. Speed matters as much as offline capability. If the app takes twenty seconds to load a job, engineers will go back to paper and you will lose the data that everything else on this page depends on.
How are parts used on site tracked?
Each van is set up as a stock location in its own right, replenished from the main store like any other bin. When an engineer books a part to a job, stock moves out of that van at the correct valuation, the part is recorded against the serial number in the unit history, and it appears on the invoice line if the job is chargeable. Van stock also gets counted. A quarterly count per vehicle is not bureaucracy, it is the only thing standing between you and a slow leak of spares that never shows up as a loss anywhere visible.
How are service contracts priced and renewed?
A contract holds coverage terms, response and fix time commitments, what is included and excluded, the schedule of preventive visits and a renewal date. Pricing should start from the expected cost to serve, which means the preventive visits, the expected reactive calls for that equipment type and age, travel to that site, and parts you have agreed to cover. The failure we see most often is a contract priced once at sale and rolled forward for six years while the equipment ages and the visits get longer. Report margin per contract, review it before every renewal, and be willing to reprice or decline.
How is this different from an internal IT helpdesk?
Different job entirely. An internal helpdesk supports your own staff on your own systems and is a cost centre. Service management looks outward at equipment you sold to customers, so it carries a commercial layer that a helpdesk has no need for: an installed base of serialised units, warranty terms, contracts with financial consequences for missing an SLA, chargeable work, parts consumption at valuation and invoices. It is also distinct from plant maintenance, which applies the same field disciplines to your own machines rather than to customer equipment.
How does a completed service job become an invoice?
The job record is the source document. Labour hours at the applicable rate, parts consumed from van stock, travel and callout are already captured against the job by the engineer, so billing is a review and release rather than a rebuild. Entitlement decides what is charged and what is absorbed under warranty or contract. Do it within days, not weeks. Invoice a customer four weeks after the visit and someone will query the hours, nobody will remember the detail, and you will settle for less than the work was worth.

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.

Service Management Features

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.

Core Features

From the serialised unit to the paid invoice

Installed Base and Entitlement

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.
Serialised customer equipment recorded in an ERP installed base register
Triage, Scheduling and Dispatch

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.
A service coordinator scheduling engineer jobs on a dispatch board
Field Execution and Billing

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.
A field service engineer recording parts and time on a mobile job record
What You Get

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.