CMMS for town councils and municipal services

Municipal maintenance has a combination of difficulties that doesn’t occur in the private sector. The asset base is very heterogeneous — administrative buildings, schools, sports centers, street lighting, parks, vehicles, water facilities — a good part of the work is carried out by different contractors, requests often come from a citizen who doesn’t know how to describe the problem, and every expense has to be justifiable.

A CMMS covers that scenario, but it has to be configured with those four things in mind. These are the pieces that matter.

The inventory, which almost never exists

The starting point for almost every town council is the same: there’s no reliable list of which assets are maintained. There’s one for buildings, another for vehicles, and a rough idea of the street lighting.

In asset management each piece of equipment carries its location — including its geographic position —, its model, its serial number, its installation date, its cost and warranty end date, plus any custom fields needed, each with its own type and unit. Assets are grouped by system, family and model, which is what later lets you configure once what applies to hundreds of identical points.

Each asset can carry its own QR code. On a municipal site, that solves a practical problem: the worker scans it and knows exactly which piece of equipment it is, without depending on a naming convention each contractor writes their own way.

The citizen’s request and the municipal technician’s request

Requests arrive through very different channels and with very different quality, and if they don’t all end up in the same place, there’s no complete to-do list.

In GMAO Cloud an incident can come in from the backend, from a dedicated access point, or from a mailbox that the system empties and automatically turns into requests. Each one carries its type and subtype, its priority, the address, the affected asset and who’s handling it, and each status can carry its own maximum time, so that what’s overdue shows up in a list instead of being discovered when someone complains again.

That last point is the one that stands out the most in a public administration: the response to a citizen stops depending on who happened to answer the phone.

Contractors inside the system

A good part of municipal work is done by outside companies. If they work outside the system, the town council loses the history, and with it the ability to check whether the contract terms are being met.

Suppliers are registered and receive the work orders that correspond to them, so that what they do gets recorded just like in-house work: times, materials, documentation and signatures. Since licenses are unlimited across all three plans, registering every contractor isn’t a budget decision.

There’s also a connector between GMAO Cloud sites for when the contractor also uses it, so that work passes from one system to another without an intermediate file.

Preventive maintenance for what can’t be skipped

On a municipal site, a good part of maintenance isn’t decided by anyone: a regulation sets it. Low-voltage electrical installations, elevators, fire protection, legionella in water facilities, boiler rooms, playgrounds.

It’s worth understanding how this works in GMAO Cloud, because it isn’t a separate module: legal maintenance uses the general preventive maintenance mechanism. The checklist required by the regulation is attached to the asset, its model or an entire family, the frequency is defined, and the system generates the orders on its own, checking beforehand whether the day is a holiday and whether the technician is available.

Proof that the work was done comes from the order history, from completed checklists — with their values, not just checkboxes — and from the associated documentation with its dates. To put it precisely: the system records and proves; the administration is the one who complies with the regulation.

Documentation that expires

Official inspection certificates, maintenance contracts, insurance policies, permits, certifications. In a public administration, any of those documents expiring is a serious problem, and it’s uncomfortably often discovered too late.

The document manager lets you attach documents to the asset, the building, the contractor, the order or the incident, decide who can see them, and set an expiration date. There’s a daily check on what’s about to expire that triggers an alert. Certificates also carry their number, scope, issuer and holder.

Justifying the spend

This is the main difference from a private company: it’s not enough to control the cost, you have to be able to explain it.

The reports let you view it by building, by asset, by contractor and by type of work: cost per piece of equipment, hours charged, downtime, annual preventive plan executed, order log, anomalies detected. That answers a question that has no answer without a history: what portion of the budget goes to preventive maintenance and what portion to corrective, and whether that ratio is improving.

And it enables the deeper conversation: whether there are buildings where overspending happens because the frequency is too high, and buildings where overspending happens because it’s too low. Both things usually happen at the same time.

Staff and in-house resources

Besides contractors, almost every town council has its own maintenance crew, and planning for them has constraints a system needs to account for: shifts, working hours, vacation, local holidays, and work teams with their own supervisor.

In staff management that information exists for what’s needed here, which is planning: availability affects how preventive orders are generated, and logged hours later allow cost to be split by building. It’s worth clarifying the scope to avoid a wrong expectation: this isn’t HR software — there’s no payroll, no contracts, no performance reviews — it’s the staffing piece that maintenance needs.

Personal protective equipment also falls under this, with its assignment per person and its expiration alerts, which in a public administration is a matter of liability, not just logistics.

Where to start

Not with the town’s full inventory, which is a years-long project. Start with a defined group — buildings with mandatory maintenance, for example — with their checklists and frequencies. Within days there’s preventive maintenance being generated and orders closing with real data, and you find out what needs adjusting before rolling it out further.

If you want to see how this would look with your buildings and facilities, you can request a demo or get in touch.