District Cooling Plant Maintenance in the Gulf: The Assets That Drive Every Complaint

Customer comfort is an end-to-end plant outcome

A work order status should answer three questions: what decision has been made, who owns the next action, and which fields or transactions are now allowed. If it only changes the colour of a dashboard tile, it is decoration.

A district-cooling maintenance model must connect plant state, customer impact, asset condition, work status and restoration evidence. Generic progress labels cannot explain why supply temperature or differential pressure left its operating envelope.

The nine statuses below are a practical canonical lifecycle. Map the native codes in your CMMS or EAM to them for cross-site reporting; do not force every site to rename its system.

Map the assets behind supply temperature and pressure

Status	What it means	Minimum evidence before moving on	Owner of the next move
1. Draft	A record exists, but has not entered the controlled queue	Asset or location, short description, source	Requester or planner
2. Requested	The need is submitted and awaiting triage	Reported time, requester, symptom, operational impact	Supervisor or helpdesk
3. Approved	The work is valid, in scope and assigned a priority	Priority rationale, work type, responsibility, target date	Planner
4. Planned	The job is ready in method and resources	Job steps, craft, estimated hours, parts, permits, isolations	Scheduler
5. Scheduled	A crew and execution window are committed	Scheduled start, assigned labour, material availability	Supervisor or technician
6. In Progress	Physical work has started	Actual start, attending technician, initial condition	Technician
7. On Hold	Work has stopped for a named constraint	Hold reason, responsible party, next review date	Named constraint owner
8. Completed	Physical work is finished and technical history submitted	Actual labour, parts, readings, action, failure data, downtime	Supervisor or reliability reviewer
9. Closed	Technical and commercial checks are complete; the record is history	Completion review, follow-on work, cost and reservation reconciliation	Authorised closer

Cancelled is a terminal outcome, not a stage. It should be reachable only before physical work starts, require a reason code, and remain reportable. Rejected and duplicate requests are also outcomes of triage. Treating them as ordinary lifecycle stages distorts cycle-time reporting because they never had an execution path.

Chillers, compressors and refrigerant circuits

Draft is useful where a mobile user may save an incomplete record or an integration creates a shell before enrichment. It should not count in backlog, SLA response or demand reporting. Requested is the first controlled state: the clock starts, the record cannot quietly disappear, and triage has an owner.

Approval is not permission to start an unprepared job. It means the request is genuine, in scope and prioritised against a defined consequence matrix. The approval gate should resolve duplicates, warranty responsibility, landlord-versus-tenant scope and whether the record is actually maintenance. A request for a new installation may be a project; a comfort complaint may be an operating adjustment.

Do not ask requesters to diagnose failure modes. They can reliably describe symptoms: leaking, noisy, stopped, hot, intermittent. Diagnosis belongs after inspection. Forcing a failure code at request time produces confident fiction that survives into history.

Pumps, towers and heat-rejection assets

Planned means ready to execute: the scope is understood, method is safe, skills and duration are estimated, parts are identified, and access, permits and isolations are known. Scheduled means that ready work has been placed into a dated labour window.

Combining the two hides the constraint. A job can be fully planned but unscheduled because capacity is unavailable. It can also appear on next Tuesday's schedule while lacking a bearing, permit or isolation plan. Calling both states “Assigned” makes schedule compliance impossible to interpret.

Material availability belongs as a condition or hold reason rather than an uncontrolled free-text note. Structure the reason when work waits for materials, plant conditions, isolation, specialist support or customer access. Whether these are separate statuses or reason codes under On Hold depends on reporting needs, but the cause must be structured.

Heat exchangers, strainers and customer energy-transfer stations

The transition to In Progress should be triggered by arrival at the asset or the first physical task, not by dispatch and not by a supervisor bulk-starting the morning's list. It establishes the actual start time and identifies who attended.

This is where the first data loss occurs because consumption happens faster than administration. A technician takes another filter from the van, receives help from an electrician for forty minutes, changes the repair method and observes that the unit was already unavailable. If labour, materials, readings and downtime are deferred until the end of the shift, detail is reconstructed from memory or omitted.

The answer is not a longer completion form. Capture actuals at the point they occur:

• start, pause and resume timestamps from the mobile job;
• parts issued or scanned against the work order, including van stock;
• meter readings with units and acceptable ranges;
• photos tied to a defined step, not dumped into a general attachment list;
• additional labour booked by the person who supplied it;
• follow-on defects raised as linked work, rather than buried in notes.

A work order left In Progress overnight must mean one of two things: work genuinely continues, or the record is wrong. If access, materials, production or a permit blocks the job, move it to On Hold and name the constraint.

Water chemistry and fouling control

On Hold is usually where overdue work goes to become invisible. A useful hold state requires three fields: a reason code, the person or team responsible for clearing it, and a review date. “Pending” and “Other” are not reason codes.

Separate clock treatment from operational truth. An SLA may legitimately pause for denied access or customer authorisation while continuing for a missing internal spare. That is a contractual calculation based on the hold reason; it should not change the factual timestamps. Never overwrite elapsed time to make compliance look better.

Report hold ageing by reason and owner. A queue dominated by Waiting for Material is a planning or supply problem. One dominated by Access Required is a scheduling and stakeholder problem. A single On Hold count diagnoses neither.

Controls, sensors, meters and electrical reliability

Completed should mean the physical task is finished and the technical record is ready for review. It is not the same as Closed. IBM describes Completed as the point at which physical work is finished, while Closed finalises the order, removes unused inventory reservations and turns it into history. SAP similarly distinguishes technical completion from business completion.

The second—and larger—data loss happens here. The technician is under pressure to reach the next job, so the close-out becomes “checked and fixed”. That sentence cannot support reliability analysis, warranty recovery, repeat-failure investigation, spares forecasting or maintenance strategy.

For corrective work, require structured answers to four different questions:

1. What was observed? The symptom or condition as found.
2. What failed? The maintainable item or component.
3. How did it fail? The failure mode: leak, seizure, open circuit, drift, blockage.
4. Why did it fail? The cause, where evidence supports one. “Unknown” is more honest than a guessed cause.

Also capture action taken, actual labour and materials, service-restored time, downtime, readings after work, and whether follow-on work is required. ISO 14224:2016 provides the underlying discipline: equipment, failure and maintenance data, including cause, consequence, action, resources used and downtime, in a standardised format. It is industry-specific, but the data-quality principle travels well.

Do not make every field mandatory for every job. A statutory inspection, lubrication task and breakdown repair need different completion schemas. Conditional forms by work type improve completeness and reduce meaningless values entered only to satisfy validation.

Distribution networks, valves and thermal storage

Closure is the point of no casual editing. An authorised reviewer checks that the correct asset was used, completion codes are coherent, follow-on defects have linked orders, unused reservations are released, service entries or contractor costs are reconciled, and any required customer acceptance is attached.

This should be a risk-based control. Automatically close low-risk routine work that passes validation. Sample completed work by technician and work type. Route safety-critical, statutory, high-cost and repeat-failure jobs for explicit review. Making a supervisor manually close every filter change creates a rubber stamp; reviewing none exports bad data directly into the asset history.

If history must be corrected later, keep an audit trail showing the original value, revised value, reason, person and timestamp. Silent edits destroy trust in every reliability metric downstream.

Trace every complaint through operating and asset data

Transition	Control that matters
Draft → Requested	Required identification and reported timestamp
Requested → Approved	Scope, duplicate and priority check
Approved → Planned	Job plan and resource readiness
Planned → Scheduled	Committed labour window and constraint check
Scheduled → In Progress	Actual start by the attending worker
In Progress → On Hold	Structured constraint, owner and review date
In Progress → Completed	Work-type-specific technical close-out
Completed → Closed	Risk-based quality and cost review

Measure transition quality, not just the number of jobs in each status. Useful controls include the share of jobs started before approval, scheduled without a complete plan, completed with no actual labour or parts, closed with free-text-only failure data, held past their review date, and reopened within 30 days.

Cycle time should be split by state. One average from request to close cannot tell whether delay sits in approval, planning, scheduling, execution, constraint clearance or review.

Build maintenance around four service outcomes

The plant exists to deliver adequate cooling at the agreed hydraulic and thermal conditions. Organise the maintenance plan around four outcomes: supply temperature, differential pressure, available capacity and water quality. Each outcome has a chain of contributing assets and measurements. A temperature complaint may begin with chiller loading, condenser approach, fouling, bypass, sensor bias, low secondary flow or a customer-side heat exchanger. A pressure complaint may begin with pump availability, valve position, network leakage, strainer blockage or a bad transmitter.

Define a normal operating envelope for each season and load band. Record expected chiller approach temperatures, pump curves, tower performance, differential pressure, flow, conductivity, chemical residuals and meter confidence. Alarms should identify deviation from an engineered envelope, not merely a fixed number copied from commissioning. When the plant configuration changes, approve and version the new envelope.

Chillers and compressors need performance trending

Calendar servicing alone will not reveal slow efficiency loss. Trend capacity, power, approach temperature, refrigerant condition, oil indicators, starts, run hours, vibration and control demand by machine and operating condition. Compare like-for-like load and condenser conditions. A machine that appears healthy at low load may be unable to carry peak duty efficiently.

Connect every tube clean, refrigerant intervention, sensor replacement and control change to the performance trend. This makes the benefit visible and prevents repeated work based on symptoms. Preserve OEM limits, alarm histories and baseline tests, but let actual condition and duty refine the maintenance decision.

Pumps, towers and water treatment form one reliability system

Pumps should be assessed through flow, head, power, vibration, seal condition, bearing temperature, alignment and valve position—not run hours alone. Cooling towers require fan, gearbox, fill, basin, distribution, drift and water-treatment controls. Fouling or biological growth can increase energy and reduce capacity long before it creates an obvious failure.

Water chemistry records must connect sample point, time, operating state, result, limit, corrective dose and verification. Separate condenser, chilled-water, make-up and any thermal-storage circuits. A generic monthly report marked “acceptable” cannot explain corrosion, scaling or microbiological risk after the event.

Customer stations belong in the maintenance strategy

Energy-transfer stations sit at the boundary between network performance and building operation. Maintain plate heat exchangers, control valves, differential-pressure controllers, meters, strainers, sensors and local panels as named assets. Capture primary and secondary temperatures, flow and valve position during a complaint. Without those readings, plant teams and building teams can blame each other while the underlying restriction or control error remains.

Prioritise stations by cooling load, complaint history, critical occupancy, access difficulty and hydraulic sensitivity. Plan strainer cleaning and heat-exchanger inspection from condition and pressure-drop evidence. Verify meter and sensor accuracy because poor measurement can create billing disputes and also mislead plant dispatch.

Turn every complaint into reliability information

Classify complaints by location, time, service symptom, severity and verified operating condition. Link them to plant configuration, weather, load, supply temperature, differential pressure, network alarms and station readings. Record whether the fault was central plant, distribution, customer station, building secondary system or unconfirmed.

Measure repeat complaints within a defined window, time to restore the service outcome and the number of visits that found no fault. Review clusters by branch, building and load period. The purpose is not to close tickets quickly; it is to find the asset or control pattern creating customer impact and prevent recurrence.

The weekly reliability review should pair the complaint map with chiller availability, pump and tower defects, water-quality exceptions, network losses, control overrides and station restrictions. Assign one technical owner to each recurring pattern and require a testable cause statement. Where evidence is incomplete, define the readings or inspections needed during the next occurrence instead of closing the issue as “no fault found.” This disciplined loop turns customer experience into condition data and helps the plant direct maintenance effort toward the few assets, settings and network locations that drive disproportionate service loss.

FAQ

Must a work order have exactly nine statuses? No. Nine is a useful canonical reporting model, not a standard. A simple operation may combine Draft with Requested or Planned with Scheduled. Add a status only when it represents a real decision, changes ownership or controls what can happen next.

Should Waiting for Parts be its own status? Use a distinct status where material delay is operationally significant and someone manages that queue. Otherwise use On Hold with a mandatory reason. The important point is structured, owned and aged constraint data.

When should the SLA stop? According to the contract and the hold reason. Preserve factual timestamps, then calculate paused and unpaused duration separately. Do not let users manually change elapsed time.

Who should close the work order? The technician should submit technical completion. Closure can be automated for validated low-risk work and assigned to a supervisor, planner or contract administrator for exceptions and higher-risk work.

Where a system helps

Good workflow makes the right action easier at the moment it matters: mobile actuals during execution, a completion form that changes by work type, structured hold ownership, and a review queue driven by risk rather than volume. The result is not merely a cleaner dashboard. It is asset history reliable enough to change a PPM interval, challenge a repeat contractor failure or defend a replacement decision. See eAMS for asset management.

Related reading: What Is a CMMS? (KB-129) and What Is Planned Preventive Maintenance? (KB-130).

Sources

• ISO 55001:2024, Asset Management Systems
• ISO 14224, Reliability and Maintenance Data