Why 80% of GCC PPM Schedules Exist on Paper and Fail in Practice

Every FM contract in the GCC includes a Planned Preventive Maintenance schedule. Every RFP asks for one. Every site audit checks for one. Walk into almost any building across Dubai, Abu Dhabi, Riyadh, or Doha — commercial tower, residential community, logistics hub, data centre — and you will find a folder, a spreadsheet, or a CAFM module with a PPM schedule attached to it.

Most of them are fiction.

Not in the sense that they were deliberately falsified — though that happens too. Fiction in the deeper sense: the schedule exists as an administrative artefact, disconnected from the actual physical condition of the assets, the available manpower, the spare parts pipeline, and the real failure patterns of the equipment it claims to maintain.

After twenty years of building, auditing, and inheriting PPM programmes across airports, defence facilities, master communities, data centres, and commercial portfolios in the GCC — the pattern is consistent. The schedule looks right. The execution rate does not survive contact with operational reality. And the client, sitting two management layers above the technician doing the work, has no way to tell the difference until something breaks.

Reason 1 — The Schedule Is Built for the Proposal, Not the Building

The most common origin story for a failing PPM schedule: it was written to win a contract, then handed to an operations team who had no input into it.

In the GCC FM procurement cycle, the PPM schedule is typically submitted as part of the technical proposal. The estimating team, under commercial pressure to produce a competitive bid, builds a schedule based on OEM recommendations — often lifted directly from manufacturer manuals — without ever setting foot in the building, reviewing the as-built drawings, or understanding what equipment is actually installed.

The result: a schedule that is technically correct for a generic version of the asset class, and operationally useless for the specific building it is supposed to serve. Frequencies are copy-pasted. Task durations are theoretical. The manpower assumptions behind the schedule bear no relationship to the headcount the FM company actually mobilises on site.

When the operations team receives a schedule they cannot physically execute, one of two things happens: they attempt to execute it and fail visibly, or they quietly redefine what "completion" means. In practice, it is almost always the latter. Task sign-offs accumulate in the system. The completion rate in the CAFM looks acceptable. The actual condition of the assets does not reflect the schedule at all.

Reason 2 — No Asset Register, No Real Schedule

A PPM schedule is only as accurate as the asset register it is built on. In most GCC buildings, the asset register is either missing, incomplete, or was last updated at handover — five, eight, ten years ago.

Buildings in the GCC age differently than buildings in temperate climates. Cooling systems run at maximum load for nine months of the year. Facade and waterproofing systems are subject to extreme UV and thermal cycling. MEP infrastructure in master developments was often installed in phases, by multiple contractors, to varying standards. The as-installed condition and the as-documented condition diverge within the first operational cycle.

A PPM schedule built on a 55% accurate asset register will miss, at minimum, 30–40% of maintenance events — not because the FM team failed to execute, but because the schedule did not include those assets in the first place. The result looks like a high completion rate against a fundamentally incomplete scope.

Reason 3 — Frequencies Are OEM Defaults, Not GCC Operating Realities

OEM maintenance frequencies are designed for temperate climates, moderate ambient conditions, and average operating hours. The GCC is none of those things.

A chiller system in Dubai runs at 90–100% load for seven to nine months of the year. The OEM manual, written for a European or North American context, recommends annual condenser cleaning. In the Gulf, quarterly cleaning is the minimum for efficient operation — and in dusty environments near construction activity or coastal areas, monthly inspection with cleaning as required is the standard that protects the machine's life.

The same logic applies across asset categories: air handling units accumulate dust at three to four times the rate of equivalent equipment in northern Europe. External waterproofing and sealants degrade faster under UV exposure exceeding 2,200 hours per year. Cooling tower drift eliminators require more frequent inspection due to higher biological load in warm, humid air streams.

• Chiller condenser tube cleaning: OEM recommendation 1× annual. GCC operational reality: 3–4× annual in coastal and dusty environments.
• AHU filter replacement: OEM recommendation quarterly. GCC reality: monthly in construction-adjacent sites, bi-monthly in established developments.
• Cooling tower chemical dosing review: OEM recommendation monthly. GCC reality: bi-weekly during summer peak — Legionella risk rises steeply above 37°C ambient.
• External sealant inspection: OEM recommendation every 3 years. GCC reality: annual inspection with proactive replacement at 5 years, not 10.
• Generator load bank testing: OEM recommendation 6-monthly. Data centre and critical facility standard: quarterly minimum, monthly preferred for Tier 3 and above.

FM contractors using OEM-default frequencies in the GCC are not maintaining assets — they are running scheduled visits that confirm the asset is still working. The actual degradation happens in the interval between visits that is two to four times longer than the operating environment demands.

Reason 4 — CAFM Systems That Track Completion, Not Condition

The rise of CAFM (Computer-Aided Facilities Management) platforms in the GCC over the past decade has created an unexpected problem: it has made it easier to disguise a failing PPM programme with an impressive-looking compliance dashboard.

The default metric in almost every CAFM system is task completion rate — the percentage of scheduled work orders that have been signed off within the reporting period. This metric measures process conformance. It does not measure maintenance effectiveness, asset condition, or whether the completed task was executed to the required standard.

This is not a CAFM problem. It is a programme design problem. CAFM platforms can capture condition data, require photographic evidence, enforce step-by-step task procedures, and flag anomalies against baselines. Almost nobody configures them to do this, because doing so requires time, expertise, and a client who is asking for condition data rather than completion rates.

The clients who are asking the right questions are moving from task completion rates to these metrics instead:

1. 01
   Mean Time Between Failures (MTBF) by asset category

   Tracks actual equipment reliability over time. A declining MTBF on a maintained asset is a direct signal that the maintenance programme is not arresting degradation.
2. 02
   Reactive-to-Planned Maintenance Ratio

   A well-executed PPM programme targets 70–80% planned, 20–30% reactive. Ratios above 50% reactive indicate the PPM schedule is not functional regardless of what the completion dashboard shows.
3. 03
   Repeat Fault Rate

   Percentage of reactive calls that are repeat faults on the same asset within a 90-day window. Above 15% signals a root-cause issue the PPM programme is not addressing.
4. 04
   First-Time Fix Rate

   Percentage of reactive calls resolved without returning within 48 hours. Below 75% indicates a skills, spares, or diagnostic capability gap that drives hidden cost into the reactive budget.

Reason 5 — Spare Parts Pipelines That Don't Exist

A PPM task that requires a specific consumable — filter, belt, gasket, dosing chemical, bearing — cannot be executed if that consumable is not on site. In the GCC, where the distribution network for specialist FM spare parts is genuinely thin outside Dubai and Abu Dhabi, this is not an edge case. It is a structural constraint that determines the real-world ceiling of PPM execution.

The standard GCC FM contract structure does not resolve this. The FM company is responsible for the maintenance programme. The material procurement responsibility is often shared, disputed, or ambiguous — sitting in a grey zone between the FM company's operational budget and the client's capital budget, with no pre-approved spend authority for the FM team to act without escalation.

The FM companies that execute PPM programmes well do not rely on reactive procurement. They maintain a pre-approved, site-specific spare parts inventory — funded from the maintenance budget, verified against the asset register, and refreshed on a rolling cycle. The initial inventory build typically costs AED 25,000–80,000 depending on portfolio size. It is the single operational investment that has the most direct impact on PPM execution rates.

Reason 6 — Manpower Planning That Ignores Real Scheduling Constraints

The GCC FM workforce operates under constraints that are invisible in a scheduling spreadsheet: visa processing timelines, annual leave cycles concentrated around Eid and summer school calendars, the practical loss of productivity during Ramadan working hours, and the operational reality that a single-trade technician cannot execute multi-trade PPM tasks regardless of what the schedule assumes.

A PPM schedule that distributes tasks evenly across twelve months — the default in every CAFM template — will fail in a GCC context because February, June, and October are not operationally equivalent months. June through August is peak cooling load — technicians are running reactive calls on overtaxed HVAC equipment. March is often a compressed month with accommodation transitions. Ramadan shifts the effective working day by two to three hours.

Effective PPM scheduling in the GCC requires weighted monthly planning — front-loading spring and autumn windows for tasks that cannot be safely or practically executed during peak summer, and protecting the reactive capacity of the HVAC team from June to September by deliberately reducing their planned maintenance load and building float into the annual schedule.

Reason 7 — No Formal Review Cycle

The final and most systemic failure: the PPM schedule is written at contract mobilisation and never formally reviewed. It runs on autopilot for the duration of the contract — typically three to five years — regardless of what changes in the building, the asset base, the operating profile, or the maintenance findings from year one and two.

A schedule that was accurate at mobilisation will diverge from operational reality within 18 months in most GCC buildings. New tenants modify electrical loads. Fit-out works alter ventilation zones. Major equipment is replaced with different specifications. Building occupancy patterns change. None of this is captured in the original PPM schedule unless there is a formal mechanism to review and update it.

What a Functioning PPM Programme Actually Looks Like

The gap between a compliant PPM schedule and an effective one is not about technology, software platforms, or contractor selection. It is about design intent. The schedule either exists to satisfy a requirement, or it exists to protect assets. The two are not automatically the same thing.

In twenty years, the characteristics of PPM programmes that actually work — the ones that hold completion rates above 85%, maintain reactive ratios below 30%, and generate measurable asset life extension — are consistent regardless of building type or location:

• 01
  Built on a physically verified asset register

  Not the handover documentation. A boots-on-ground survey with tagged assets, confirmed specifications, and reconciled quantities. Done before the first task is scheduled.
• 02
  Frequencies calibrated to GCC operating conditions

  OEM defaults as a floor, not a ceiling. Adjusted for ambient temperatures, operating hours, dust exposure, and the specific failure history of the asset class in the local context.
• 03
  Manpower-balanced against available capacity

  Total task hours in the schedule must be achievable with the contracted headcount. Seasonally weighted to protect reactive capacity during peak HVAC months.
• 04
  Condition data collected at task completion

  Not just sign-off — fouling level, operating parameters, anomalies. Photographs for critical assets. Enough data to show trend, not just presence.
• 05
  Spare parts inventory pre-positioned and pre-approved

  Consumables for the first annual cycle on site before mobilisation. Spend authority pre-approved for replenishment below a defined threshold.
• 06
  Formally reviewed at 90 days, 6 months, and annually

  Reviewed, revised, and signed off by client and FM team. Not an email. A documented update to the programme with tracked changes.

None of this is complicated. All of it requires deliberate choices — in contract design, in mobilisation planning, in how the client defines performance. The 80% that fail do so because nobody in the procurement process insisted on these conditions before the contract was signed.