A Musical Fountain Maintenance Checklist

Water: the System Everything Else Stands In

Begin every cycle with the water, because every other system's faults are amplified by it. Check level against the design mark — low water starves pumps and exposes fixtures; high water changes jet behaviour and floods details meant to sit dry. Check clarity and the treatment regime's readings, and keep the filtration cycle honest: filters loaded with a season's debris quietly tax every pump in the plant. Skim and remove debris on the surface and at the grilles; a basin is a leaf trap with a show attached, and autumn is its busiest season.

Water chemistry is a materials decision as much as a hygiene one. The treatment that keeps water safe and clear must also be the treatment your stainless components and fixture seals were specified for — which is why changes to the treatment regime belong in a conversation with the system's documentation, not just the chemical supplier. In dry deck installations the stakes double: the water is played in, so treatment checks move from routine to non-negotiable, on the operator's daily list rather than the weekly one.

• Water level at the design mark; top up or drain as the log requires
• Filtration running and backwashed on schedule; strainers cleared
• Treatment readings taken and logged; dosing adjusted, never guessed
• Surface and grilles cleared of leaves and debris
• Basin floor inspected for silt build-up around nozzles and lights

Jets and Nozzles: Where Drift Shows First

Walk the show — or run a test sequence — and watch each effect family with a fault-finder's eye. A fan that feathers at one edge, a swing unit whose travel has shortened, a laminar arc that leaves its nozzle already rough: each is a small sentence in a language operators learn to read. Blockages announce themselves as shape changes before they become failures, and most are cleared with the nozzle removed, cleaned and reseated — work that is trivial monthly and miserable annually.

Motion units deserve their own line. Run each axis through its travel and listen: drives announce wear acoustically before they announce it visually. Check that position feedback agrees with the jet you see — a unit whose reported angle and real angle have divorced will quietly corrupt every pattern its zone performs. Record lazy units even when the show still passes; the record is what turns a surprise replacement into a planned one.

• Test sequence run; every effect family observed from the audience side
• Nozzles checked for blockage by pattern shape; cleaned as found
• Motion units exercised through full travel on each axis; unusual noise logged
• Reported versus actual unit positions compared on a sample of units
• Laminar arcs inspected for roughness at the nozzle exit

Light and Control: the Invisible Half

Lighting faults hide in daylight, so check them in the dark or not at all. Run the lighting program at dusk and look for the fixture that has shifted colour, dimmed, or filled with condensation — each is a small failure the audience will read as shabbiness without knowing why. Compare zones against each other; drift is easiest to see as asymmetry.

Control maintenance is mostly housekeeping with consequences. Keep the cabinet environment dry and ventilated; confirm the show schedule still matches the venue's real timetable — a fountain performing its gala program to an empty Tuesday square is a maintenance failure of the calendar, not the kit. Back up the show programs and configuration whenever they change, and keep the backup where a successor operator can find it. Verify that the safety interlocks and level protections still trip and reset as designed; protective systems that are never tested are decorations.

• Lighting program run at dusk; colour, output and condensation checked per zone
• Cabinet interior dry; ventilation clear; connections visually sound
• Show schedule reconciled with the venue timetable
• Programs and configuration backed up after any change
• Interlocks and level protections test-tripped and reset

Fault Patterns Worth Recognising Early

Experience compresses into pattern recognition, and a few patterns repay learning early. The single weak jet in a strong field is almost never the nozzle's character; it is supply — a strainer loading, a valve drifting, a line sharing its duty with a new demand — and it will recruit neighbours if ignored. The light that warms in colour while its twins stay true is announcing its own retirement on a schedule; replace it in a planned visit and it is a component, ignore it and it becomes an opening-night story.

The chase that has lost its snap — patterns arriving almost together that once travelled — points at timing, not machinery: a configuration restored from an old backup, an offset lost in an update, a unit replaced and never re-registered in the program's map. And the show that audiences describe as 'fine, but…' in the season after a triumphant opening is usually a program problem wearing a maintenance costume: the water is honest, the cues have drifted, and the cure is a programming review rather than a plant-room one.

Each pattern makes the same argument from a different side: the checklist's value is not the catching of faults but the dating of them. A fault found by the list is found in the week it began, when it is a cleaning, an adjustment or a setting. The same fault found by the audience has been compounding for a season. Walk the list, and let the fountain's small confessions stay small.

Seasonal Work and the Record That Makes It Real

Seasonal work brackets the operating year. Opening: full system test, treatment regime re-established, every unit exercised, programs reviewed against the season's calendar. Closing, where climate demands: drain-down of exposed lines, protection of fixtures and units as the system's documentation directs, and the deep clean that is only possible with the water out. Between seasons, the deepest maintenance truth applies — the winter work you skip becomes the opening week's emergency.

Underpinning all of it is the log. A fountain maintained from memory is maintained by whoever happens to remember, and staff change. The log — levels, readings, faults found, units cleaned, programs changed — is the difference between a system with a history and a system with anecdotes. Keep it dull, keep it current, and review it at each seasonal opening: patterns in small faults are how big ones announce themselves while they are still cheap.

None of this requires heroics. It requires a list, a rhythm and an operator who walks the show. Fountains reward that modest discipline with the only thing they are really for: evenings that work, year after year, as if water simply behaved that way.