Part 4 of our series on ERP for Maltese businesses, by sector.

The engineer arrives at the job in Sliema at nine. He looks at the unit, works out what's wrong in about four minutes, and then discovers the part he needs is not in the van. It might be in the store. It might be in the other van. It might be on order.

So he calls the office. The office checks. Nobody's sure. He does what he can, tells the customer someone will be back, and drives to the next job - which he's now late for.

Later that week he comes back, fits the part in twenty minutes, and leaves. Two visits, two lots of travel, one irritated customer, for a job that was always going to be a twenty-minute fix.

Multiply that by however often it happens in your business. That's the number this article is about.

Why field service is different from every other sector

Most businesses happen in one place. Field service happens everywhere except the place where the information lives.

Your productive capacity is people in vehicles, and it decays constantly. Travel time, waiting time, a job that overruns and pushes everything back. Unlike a workshop, you can't see it happening.

Your stock isn't in a warehouse. It's in five vans, a store, and a few customers' plant rooms. And it moves without anyone recording it, because the person moving it is on a ladder.

The person doing the work isn't the person who quoted it or the person who'll bill it. Information has to survive three handovers, and it usually does so on a paper job sheet in someone's back pocket.

And Malta adds its own version of the problem. Distances are short, so travel feels trivial, but the traffic isn't, and a badly ordered route still costs an hour a day. Parts come from abroad with real lead times. And demand is intensely seasonal: air conditioning work in July doesn't resemble air conditioning work in February, but your fixed costs don't care.

The five things that cost you money

1. First-time fix rate

This is the metric that matters most in field service and the one almost nobody in Malta measures.

Every job that needs a second visit costs you twice the travel, twice the scheduling, and a chunk of the customer's goodwill. The causes are usually mundane: the van didn't have the part, the engineer didn't know the equipment model before arriving, or the fault description taken over the phone was too vague to prepare for.

All three are information problems, not skill problems.

2. Scheduling on a whiteboard

The board in the office, a WhatsApp group, and someone's memory. It works, until someone calls in sick, or an emergency comes in, or a job overruns by three hours.

Then the rescheduling happens by phone, urgently, while other work waits. And the customer who was booked for Thursday afternoon finds out at four o'clock that nobody's coming.

The deeper cost is that nobody can see capacity. When a customer asks how soon you can come, the answer is a guess, and guesses that turn out wrong are how service businesses lose accounts.

3. Paper job sheets, and the billing delay behind them

The engineer fills in a sheet on site. It comes back to the office at the end of the day, or the end of the week, or when someone remembers to empty the van.

Then somebody deciphers the handwriting, works out which parts were used, and raises the invoice. By the time it goes out, the job is three weeks old. Customers query old invoices far more than recent ones, and some jobs never get billed at all because the sheet never came back.

Paper isn't just slow. It's a direct revenue leak.

4. Van stock nobody can see

Ask what's in each van right now. Most businesses genuinely cannot answer.

The consequences run both ways. You buy parts you already have, sitting in a van somewhere. And you don't have parts you assumed you did, causing the second visit described at the top of this article. Meanwhile, a meaningful amount of capital is tied up in stock spread across vehicles, and none of it appears properly in your accounts.

5. Service contracts that leak free work

If you run maintenance contracts, warranties or service agreements, the questions come up constantly. Is this customer covered? Is this job inside the contract or chargeable? Has their annual service been done? Did that warranty expire in March?

When the answer lives in a folder or in someone's head, the default answer becomes "just do it." Over a year, that's a lot of unbilled work and separately, missed scheduled services mean missed revenue you'd already agreed to earn.

What good looks like

Setting software aside, a well-run field service business looks like this:

• Every job carries the customer's equipment history and the fault description before the engineer sets off
• The schedule is visible to everyone, adjustable in seconds, and reflects real capacity
• Engineers record what they did, the time taken and the parts used on a phone, on site, before they leave
• The customer signs on the device, and the job can be invoiced the same day
• Van stock is tracked, so parts consumed come off the right location and replenishment is automatic
• Contracts and warranties are attached to the customer, so entitlement is a fact rather than a judgement call
• Recurring maintenance visits generate themselves rather than depending on someone's diary
• You can see which job types, which customers and which engineers are actually profitable

Where Odoo fits

Field service is one of the clearer cases for a single connected system, because the whole difficulty is that scheduling, stock, the job record and the invoice are all the same event happening in four different places.

Field Service with mobile job records. Jobs are created as tasks with the customer, site, equipment and fault details attached. Engineers work from a phone or tablet, seeing what they need before arriving.

Custom worksheets per job type. Odoo lets you build worksheet templates so an AC service, an electrical inspection and a plumbing callout each capture the right information — readings, checks, photos, notes. That's the digital replacement for the paper sheet, and it's structured, so you can report on it later.

Time and parts recorded on site. The engineer logs hours and adds the parts used directly to the job. Those parts come off stock and go onto the invoice without anyone retyping anything.

Customer signature on the device. Sign-off happens at the job, attached to the record. Disputes about whether work was completed become much rarer.

Invoice from the job. Because time and materials are already on the task, invoicing is a click rather than a reconstruction. Same-day billing becomes realistic.

Scheduling and dispatch. Odoo's Planning view shows who is assigned to what and when, with a map view of jobs so routes can be ordered sensibly. Rescheduling is drag-and-drop rather than a round of phone calls.

Vans as stock locations. Each vehicle can be modelled as its own location, so van stock is visible, consumption is recorded when parts are used on a job, and replenishment rules top vans back up. This is usually the single biggest practical win for an installation business.

Recurring maintenance. Repeating jobs generate automatically on schedule, so contracted annual services stop depending on someone remembering.

Contracts and subscriptions. Maintenance agreements can be held as recurring contracts that bill automatically and make entitlement visible when a call comes in.

Equipment history per customer site. What's installed, when it was serviced, what failed last time. This is what raises first-time fix rate more than anything else — an engineer who knows the model before arriving can bring the right part.

Helpdesk for incoming calls. Customer calls and emails become tickets that convert into field jobs, so nothing falls between the phone and the schedule.

One honest note. The success of a field service implementation rests almost entirely on whether your engineers use the mobile side. If the app is fiddly, if the site has no signal, or if nobody trained them properly, you'll end up with a good office system and paper still coming back in vans. Any implementation worth doing spends real time on the engineer experience, not just the back office.

How these projects usually run

Sensible phasing: get the job records and scheduling working first, so the office has visibility, then move engineers onto mobile worksheets, then add van stock, then contracts and recurring maintenance. Van stock before mobile recording tends to fail, because the parts data only becomes accurate once engineers are recording consumption at the job.

Avoid going live in your peak season. For most Maltese field service businesses that rules out early summer.

Where to start

Three things you can do this month, without buying anything:

Count your second visits. Go back over the last month and mark every job that needed a return trip because something wasn't ready. Work out the travel and labour hours involved. That figure is usually the entire business case on its own.

Stock-take one van, unannounced. Compare it to whatever you believed was in it. The gap tells you how much capital is drifting around in vehicles.

Time the gap between job completion and invoice. Take twenty recent jobs and measure the days between the work being done and the invoice going out. If the average is over a week, you're financing your customers for free — and some of those jobs are probably never getting billed.

If any of that is hard to measure, the difficulty is the point.

Centric Malta is an Odoo implementation partner based in Birkirkara, working with Maltese installation, maintenance and field service businesses. If you'd like to talk through how your scheduling, van stock and billing currently connect  and what it would take to see them in one place — get in touch.

Mob +356 7746 9333 | Tel +356 2746 3333 | info@centricmt.com

Previously in this series: ERP for small manufacturers and workshops in Malta.