Planned preventive maintenance against reactive callouts

A planned preventive maintenance schedule sets out what gets serviced, how often, and by whom, before anything fails. Dubai does not leave that entirely to a building's own judgement. Clause 502.14 of Al Sa'fat, the Dubai Green Building System published by Dubai Municipality, requires that in every new and existing air-conditioned building, all mechanical, electrical and plumbing systems be serviced and maintained regularly, under a manual and schedule the building operator has to keep on file.

The same document draws the line precisely. Preventative maintenance is defined there as "maintenance service or procedures intended to prevent or reduce equipment failure or damage." Corrective maintenance is its opposite: work "carried out in response to a fault and not planned." What follows is where the numbers in a schedule actually come from, what an asset register has to hold before a schedule can be built on it, and the point at which skipping the planned route turns out to be the expensive choice, not the cheap one.

Where a schedule's numbers come from

Three routes, in practice. The manufacturer's own instructions rank first, because they are specific to the machine actually installed, not to the building type it sits in. Where none exist, or an engineer needs a general benchmark for commercial HVAC, ANSI/ASHRAE/ACCA Standard 180-2018 sets minimum inspection and maintenance requirements for the systems in new and existing commercial buildings, covering thermal comfort, energy efficiency and indoor air quality. Anything else has to be approved by Dubai Municipality specifically. The clause does not pre-approve a substitute.

For everything outside HVAC, lifts, fire systems, electrical distribution, plumbing, a widely used equivalent is SFG20, the building maintenance specification first published in 1990 by the Building Engineering Services Association. It now covers more than 1,500 schedules across 110-plus asset classes, each flagged as statutory, mandatory or discretionary.

The asset register comes before the schedule

None of the sources above can be applied to a building until someone has listed what is actually in it. ISO 55000:2024, the vocabulary and principles standard for asset management published by ISO's technical committee 251 in July 2024, frames this as an organisation's asset portfolio: the assets it holds, and the value it intends to realise from each one over its life. ISO 41001:2018, the facility management systems standard from ISO's technical committee 267, sets requirements for the wider system that portfolio sits inside, without prescribing the register or the schedule directly. SFG20 uses a plainer term for the same starting point, and puts it first in its workflow: import the asset register, before a schedule can be mapped to a machine.

A register that reads only "chiller, roof" does not carry enough for either exercise. It has to identify one specific piece of equipment, distinct from every other one like it, before a frequency, a criticality rating or a statutory flag can attach to it. That work is unglamorous, and on most sites it is done once, at handover, then never corrected. Every later schedule inherits the gap.

Frequency and criticality, not one calendar for everything

A single interval applied to every asset wastes money on some of them and under-serves others. SFG20's schedules are filtered by criticality and frequency for that reason: a fire damper and a decorative light fitting do not carry the same consequence if a service gets missed. Its colour-coding separates tasks that are statutory, meaning a specific law or code requires them, from tasks left to the building's own judgement.

Clause 502.14 reaches the same result from the regulator's side without dictating a number itself. It does not fix how often a chiller gets serviced. It fixes who is allowed to set that number: the manufacturer, ASHRAE 180, or Dubai Municipality's own sign-off on an alternative, and leaves the actual frequency to that source. A schedule copied from a similar building down the road answers none of those three tests.

What the log book has to prove

• Mechanical systems installed with adequate access, so equipment can be inspected, maintained and cleaned without removing or dismantling building components
• A written maintenance manual and schedule based on manufacturer instructions, ASHRAE Standard 180, or an alternative Dubai Municipality has approved
• A service contract with a Dubai Municipality-approved maintenance company, or evidenced competence among the building's own staff
• A service log book covering both preventive and corrective work, kept onsite and available for inspection by Dubai Municipality staff

That definition is exacting on purpose. A spreadsheet with a date column and nothing else is not a service log book under it; the record needs the work actually done and the name of whoever did it, for corrective visits as much as planned ones. Dubai Municipality's inspectors can ask to see that record. So, eventually, can an insurer after a loss, or an equipment manufacturer assessing a warranty claim.

Most of Al Sa'fat's other clauses apply only to new construction, or only above the mandatory Silver tier, with Golden and Platinum layered on top of it. Clause 502.14 carries neither qualifier. It reaches every air-conditioned building already standing in Dubai, rated or not.

The economics manufacturers can actually measure

Figures on the cost of reactive maintenance specific to buildings are hard to pin to one checkable source. The most rigorously documented numbers come from manufacturing, not facilities, and they still make the underlying point. The U.S. National Institute of Standards and Technology surveyed discrete manufacturers for the year 2016 and published the results as report NIST AMS 100-34.

The same survey put average reliance on reactive maintenance, across the manufacturers it covered, at 45.7 per cent of all maintenance activity that year. None of that is a Dubai figure, or a facilities figure specifically. It is evidence, from a national standards body rather than a vendor, that businesses leaning hardest on fixing things after they break carry measurably worse outcomes than the ones that do not.

Where reactive starts costing more

The mechanism clause 502.14 assumes is a simple one. A manual built on the manufacturer's own instructions is also, in practice, close to the manufacturer's warranty condition. Skip the service interval the manufacturer specified, and a claim on that same equipment can be refused on exactly that basis, whether or not the fault turns out to be related to the missed task.

Reactive work also arrives without warning, and a fault left running can damage more than the part that started it: a seized pump overheating a motor, a blocked condensate line flooding the ceiling below. That does not show up in a simple comparison of one planned visit against one emergency callout. It shows up in what the callout was actually called out for.

Under clause 502.14, the log book is the entire defence a building operator has. A record with no date, no description of the work and no name against it proves nothing to an inspector, a warranty desk or an insurer, however many visits actually took place.