CMMS for swimming pool maintenance

Swimming pool maintenance has a feature that sets it apart from almost everything else: much of the work isn’t repairing, it’s measuring. Chlorine, pH, turbidity, temperature, flow rate. And those readings aren’t an internal routine: they’re what you have to be able to show when someone asks.

Add to that the plant room machinery —pumps, filters, dosing units, chlorinator, heat exchanger, dehumidifier on indoor pools— which is classic maintenance, and the treatment of the facility against legionella, which has its own frequency and its own record.

Checks with a value, not a checkbox

This is the point where a CMMS adds the most value in this sector, and the one spreadsheets handle worst.

A report that says “water check: OK” is worthless. One that says “free chlorine 1.2 mg/l, pH 7.4, at 09:15, by So-and-so” is. The difference isn’t about rigor: it’s that the first doesn’t let you see a trend and the second does.

In GMAO Cloud, checklist fields support type, label and a minimum and maximum value. When a reading falls outside the range, it gets logged as an anomaly on the spot, not as a side comment no one will ever re-read. That turns the daily check into a data series you can then work with: which pool deviates the most, at what times, under what bather load.

The checklist is defined once per facility type and resolved in cascade —asset, model, subfamily, family— so a chain with twenty facilities doesn’t mean configuring twenty protocols.

Several schedules on the same site

A pool doesn’t have one maintenance plan: it has three or four overlapping ones. Water checks are daily or per shift; filter backwashing is weekly; pump and dosing unit inspection is monthly or quarterly; legionella checks and lab analyses have their own frequency; and seasonal start-up is annual.

Preventive maintenance supports several periods on the same asset, each with its own count of when it was last carried out, so the system knows which one is due next. And before generating the order it checks whether the day is a holiday and whether the technician is available, which matters more at a facility open on weekends than at a factory.

Plant room machinery as assets

Pumps, filters, dosing units, sensors, salt chlorinator, heat pump, dehumidifier. Each with its own asset record: model, serial number, installation date, warranty end date and location.

The warranty end date is one of the most appreciated pieces of data and one of the least loaded: in this sector it’s very common to pay for a repair on equipment that was still under warranty, simply because no one had it on hand when opening the order.

Every asset can carry its own custom fields with their unit —flow rate, power, pool volume, filter surface area— and its QR code, so the technician can scan it and have the history and documentation in front of them without calling anyone.

Recording where the work happens

A pool plant room is a damp basement with no coverage. It’s the exact scenario a true offline mode is designed for.

In the technician app, the technician fills in the checklist with its values, logs time with a stopwatch, consumes product against the warehouse, attaches photos and collects the facility manager’s signature. Everything queues up and syncs once signal returns, and if an action fails, it doesn’t disappear: it’s flagged with the reason.

The real alternative —writing it in a notebook and typing it into the computer in the afternoon— always produces the same result: hours rounded down and values rounded off.

Chemical product, stock and batch

Water treatment consumes product, and that product expires.

In warehouses and items each reference carries its cost, its minimum stock and its original reference, and the ones that need it are tracked by batch with manufacturing and expiry dates. Consumption is logged when the order closes, so stock and job cost update with what was actually used.

Minimum stock avoids the sector’s classic problem: discovering you’re out of product on the day you need to dose.

Alerting when something drifts

An out-of-range value shouldn’t have to wait for someone to look at the report. Alerts let a logged anomaly turn into work: it becomes an issue with a priority and an owner, and status changes can carry their own email notification.

That loop is what decides whether the system survives. If a technician logs a deviation and nothing happens, by the third time they’ll stop logging it.

What to look at afterward

A pool’s history answers questions that, without records, are just opinions — and almost all of them have a direct financial consequence.

Which pool deviates most, and when. If deviations cluster in the same time slots, the problem isn’t the treatment: it’s the dosing or the recirculation flow rate relative to the actual bather load.

How much product each facility consumes. With consumption logged at order closing, cost per facility stops being an estimate. A pool that uses twice as much as an equivalent one has an explanation, usually a miscalibrated sensor or a leak.

Which equipment concentrates the breakdowns. Reports on cost per equipment, downtime and MTBF tell you whether that pump gets repaired again or replaced. At a seasonal facility, that decision is made well in October and badly in July.

What proportion is preventive versus corrective. If corrective work doesn’t drop despite having the plan in place, the plan is watching the wrong things.

The documentary proof

This is the reason many facilities end up looking for a system.

Documentation hangs off the asset, the facility, the client or the order, with its visibility set —who sees it— and its expiry date when it has one, with a daily check on what’s about to expire. Certificates carry their number, scope, issuer and holder.

On top of that record rests mandatory maintenance for the facility. Worth knowing how it works in GMAO Cloud, because it isn’t a separate module: it’s done with the preventive maintenance mechanism, linking the inspection plan the regulation requires and its frequency. The proof comes from the order history, from the completed checklists with their values, and from the documentation with its dates.

To be precise: the system records and demonstrates what was done. The one who complies with the regulation is the facility owner.

If you manage several facilities

The most common case: a company handling pool maintenance for hotels, communities, gyms or municipal facilities.

What changes there is the scale of the linking: the maintenance plan is defined by family and rolled out across all facilities, reports are reviewed by site to see which concentrate the deviations, and the client has their own access to download their reports and see their upcoming visits without calling. Since licenses are unlimited on all three plans, giving everyone access doesn’t cost more.

If you’d like to see it with your own facilities and control protocols, you can request a demo.