Odoo Maintenance: Preventive Work on the Equipment That Actually Runs

The equipment register, which is the whole foundation

Equipment records the asset, its category, the technician or team responsible, its location, its serial number, the vendor, warranty dates, and where relevant the work centre it belongs to.

Building this register is the real work of implementing the module and it is tempting to do it thinly. Resist that for the fields that will be asked about later: warranty expiry, because knowing an asset is still covered before you pay for a repair pays for itself quickly, and assigned owner, because equipment with no owner accumulates requests that go to nobody.

Start with the equipment whose failure actually stops something. A complete register of every desk fan and an incomplete one of your production line is the wrong way round.

Corrective requests, which are what people will actually use

A corrective request is raised when something breaks. It moves through stages on a kanban board: new, in progress, repaired, scrapped.

Let operators raise these directly. The instinct is to route reports through a supervisor for filtering, and the result is that small faults go unreported until they become large ones. The form is short, and a slightly noisy request queue is far more useful than a quiet one.

The value compounds silently. After a year, the request history against a machine answers whether it is worth repairing again, whether a fault is recurring, and whether a supplier's equipment is as reliable as they claimed.

Preventive maintenance and the shift that matters

Preventive requests are generated on a schedule, either by time or by a usage meter on the equipment.

Usage-based is the better mechanism wherever a meter exists. A machine that ran flat out for six weeks and one that sat idle should not be serviced on the same calendar, and a time-based schedule either over-services the idle one or under-services the busy one.

The metric worth tracking is the ratio of preventive to corrective work. A maintenance operation that is entirely corrective is firefighting, however efficiently it does it. Moving that ratio is the whole point of the module, and it is a slow move that needs somebody watching it, otherwise the preventive schedule quietly gets deferred every time production is busy.

Where Odoo Maintenance will fight you

Sustaining it is harder than starting it. The register goes stale, preventive requests get closed without being done, and within a year the data is worse than useless because it looks authoritative. This needs an owner, not just a configuration.

Spare parts are not modelled as a maintenance workflow. Spares are Inventory, and the link between a repair and the parts it consumed is something you have to design. For parts-heavy maintenance operations this is a real gap.

Reporting is basic. Request counts, categories and durations are available. Formal reliability metrics such as mean time between failures are not presented, though the underlying data supports deriving them.

It is not a full asset-management system. Depreciation, asset valuation and capital planning belong in Accounting, not here.

How it connects to everything else

Equipment links to work centres in Manufacturing, so maintenance affects visible production capacity and downtime attributes to a specific machine. Equipment can also be assigned to employees, which covers laptops and vehicles as well as machinery. Quality failures traced to equipment rather than material can raise maintenance requests. Fleet handles vehicles specifically, and the two overlap, so decide which owns vehicles rather than recording them in both.

Where to start

Register only the equipment whose failure stops work, and fill in warranty and owner properly for those. Let operators raise corrective requests themselves from day one. Add preventive schedules for a handful of critical assets, using meters rather than dates where a meter exists. Give the whole thing a named owner. Then check the preventive-to-corrective ratio after two quarters, because that single number tells you whether the module is being used or merely installed.