← Back to standards
AS/NZS 3666.2Pending revision

Microbial control — operation and maintenance

A practical guide to routine operation, inspection, cleaning, cooling-water maintenance, competent servicing and the records needed to manage building air-handling and water systems over time.

01

“We service filters and call a contractor every month. Does that mean our HVAC microbial-control maintenance program is adequate?”

A maintenance contract can look active while the actual integrity of the system record is weak. The engineering question is whether the right plant is being inspected, defects are being rectified, cleaning and treatment are effective and the evidence is retained.

02

The practical answer

An adequate program is more than a calendar of contractor visits. It should define the assets, tasks, frequencies, competent personnel, defects, rectification, manuals and records needed to preserve system cleanliness and control microbial risk.

AS/NZS 3666.2 sets minimum requirements for routine operation and maintenance of building air-handling and water systems. It distinguishes routine maintenance from emergency response to a known outbreak.

The Standard emphasizes competent maintenance, safe access, equipment shutdown during relevant work, routine inspection and cleaning, cooling-water management and site-available records.

The most common weakness in existing buildings is not total absence of maintenance; it is a fragmented program where contractors complete tasks but the owner cannot show a coherent asset history or close out repeated defects.

AS Applied rule of thumbChoose the scope, design basis and evidence pathway first. Do not start by hunting for a single clause, percentage or formula that makes the preferred answer work.
03

Where this Standard fits

Common starting points
  • Routine AHU and air-distribution maintenance
  • Outdoor-air intake and exhaust inspection
  • Cooling towers and cooling water systems
  • Seasonal shutdown and restart of water systems
  • Maintenance manuals and service records
  • Buildings with recurring odour, moisture or cleanliness complaints
Do not assume
  • A design Standard for new systems
  • Proof that a monthly contractor visit covers all required assets
  • An emergency Legionella outbreak procedure
  • A reason to ignore defects because cleaning was completed
  • A substitute for regulatory water-system requirements
  • A program that can exist without records and manuals
04

Is the maintenance program actually controlling the system?

Follow the chain from asset list to task, evidence, defect and rectification. A visit frequency alone does not prove control.

1Define the maintained assetsAHUs, intakes, filters, coils, terminal units, cooling towers, water treatment and other covered systems.
2Map tasks and frequenciesInspection, cleaning, testing, treatment, calibration and seasonal procedures should be explicit.
3Check access and safetyMaintenance should be practical, safely accessible and performed by competent personnel.
4Review reports for defectsFind repeated observations, blocked drains, wet components, poor water quality or inaccessible items that remain unresolved.
5Verify close-outA defect notification should lead to rectification, not disappear into a service report archive.
6Maintain the asset historyCurrent manuals, alterations, reports, test results and service records should remain available and understandable.
The most common failure is a broken chain of assumptions.

A good result needs the equipment definition, loads, design method, fabrication, inspection and operating limits to describe the same real system.

05

Key engineering concepts to understand

01

Maintenance is a management system

Tasks, competent people, records and defect close-out should work together rather than existing as disconnected contractor visits.

02

Inspection and cleaning are different

An asset may need inspection at one interval and cleaning when condition indicates; the program should record both.

03

Defects need ownership

A service report that identifies a problem but does not trigger rectification is weak evidence of control.

04

Seasonal systems need restart discipline

Shutdown systems can deteriorate or stagnate; restart should restore treatment and controlled operating condition.

05

Cooling water requires ongoing control

Inspection, cleaning, treatment and records are lifecycle activities, not one-off commissioning tasks.

06

Records protect future decisions

A good history helps engineers distinguish recurring design defects from isolated maintenance failures.

06

Detailed engineering case studies

The examples below show how the Standard changes a real engineering decision. They are not clause summaries or universal answers; each case starts with the equipment, task and evidence available.

Case study 1 · Commercial office maintenance

Monthly service visits but recurring wet filters and blocked drains

01
Project context

A commercial office has a comprehensive HVAC service contract. Despite monthly visits, several AHUs repeatedly show wet filters, blocked drains and odour complaints.

Why this Standard matters

AS/NZS 3666.2 shifts the question from ‘Was the contractor on site?’ to whether inspection, cleaning, defect reporting and rectification are managing the actual condition.

What made the job difficult

  • Service reports mention the same defects over several months.
  • Different technicians use inconsistent asset names.
  • The owner receives PDF reports but has no defect register.
  • Some root causes may be design problems under AS/NZS 3666.1.

How the engineering review should proceed

  1. Build a clear asset register linking each AHU and component to the maintenance tasks.
  2. Review repeated defects and separate cleaning tasks from unresolved design or drainage problems.
  3. Create a defect close-out pathway with owners, due dates and verification evidence.
  4. Escalate recurring moisture issues for engineering review rather than accepting endless cleaning.
Practical outcome

The maintenance program becomes condition- and evidence-based. Repeated cleaning is no longer treated as successful maintenance when the underlying defect remains active.

Also investigate
AS/NZS 3666.1Asset registerDefect management
Case study 2 · Seasonal cooling tower

Cooling-water system restarted after months offline

02
Project context

A facility operates a cooling tower only during the warmer season. After several months offline, the plant is scheduled to restart quickly when temperatures rise.

Why this Standard matters

Seasonal shutdown and restart can create microbial-control risk if draining, drying, circulation, treatment and recommissioning actions are not managed deliberately.

What made the job difficult

  • The previous shutdown record is incomplete.
  • Some pipe sections may have retained water.
  • The water-treatment contractor has changed.
  • Operations want immediate availability because of a heatwave forecast.

How the engineering review should proceed

  1. Confirm how the system was left at shutdown and whether it remained dry or under maintained treatment/circulation.
  2. Inspect and clean as necessary before restart rather than assuming the previous season’s condition remains valid.
  3. Restore and verify the treatment program before normal duty.
  4. Record the restart condition so the next seasonal cycle begins with a known history.
Practical outcome

The restart becomes a controlled maintenance event with documented condition and treatment, not simply a pump-start command after months of inactivity.

Also investigate
Water treatmentAS/NZS 3666.1 designRegulatory requirements
Case study 3 · Maintenance records

Building owner cannot reconstruct five years of cooling-tower service history

03
Project context

During an audit, a building owner discovers that maintenance has been split across several contractors and records are stored in emails, portals and paper folders.

Why this Standard matters

AS/NZS 3666.2 treats manuals and maintenance records as part of the control system. Without a coherent history, the owner cannot easily show what was inspected, found or rectified.

What made the job difficult

  • Asset names differ between contractors.
  • Calibration and treatment records are incomplete.
  • Reported defects cannot be linked to close-out evidence.
  • Alterations are not reflected in the current manual.

How the engineering review should proceed

  1. Create a single asset index and map historical records to each system.
  2. Identify mandatory information gaps and unresolved defects rather than merely digitizing every document.
  3. Update operating and maintenance manuals to reflect current plant and alterations.
  4. Establish a standard reporting and retention process for future service work.
Practical outcome

The owner ends with a usable maintenance history, not just a larger document archive. Missing evidence and unresolved defects are visible and can be managed explicitly.

Also investigate
Facility management systemContractor reportingRegulatory access to records
07

Common mistakes

Equating attendance with maintenance

A contractor visit is only useful if the right asset is inspected and findings are recorded and acted upon.

No defect close-out

Repeated problems remain open across multiple reports with no engineering or repair owner.

Inconsistent asset naming

The history becomes unreliable when the same AHU or tower is described differently each visit.

Restarting seasonal systems casually

Shutdown condition, treatment and restart actions should be controlled.

Storing reports without a program

A document archive is not the same as a maintenance strategy and record system.

Cleaning around a design defect

Recurring moisture or access problems should be escalated to design review under AS/NZS 3666.1.

08

Information to gather before making the decision

Current asset register

Operating and maintenance manuals

Preventive maintenance task list

Inspection and cleaning frequencies

Service reports and test results

Defect register and close-out evidence

Water treatment records

Sensor and probe calibration records

Seasonal shutdown and restart procedures

Cooling-tower cleaning history

Recent plant alterations

Regulatory requirements for the site

09

What should happen next?

1

Program exists but complaints recur

Review defect trends and identify design issues that routine cleaning cannot solve.

2

Cooling tower or water system

Check inspection, cleaning, treatment, shutdown and restart records together.

3

Records are fragmented

Build a single asset-based history and expose missing evidence or unresolved defects.

4

New system handover

Ensure AS/NZS 3666.1 commissioning information feeds directly into the ongoing maintenance program.

5

Ventilation quantity complaint

Use AS 1668.2; maintenance records alone do not establish outdoor-air adequacy.

Related AS Applied content

10

Source basis & limitations

  • The page does not reproduce the Standard’s detailed frequency schedules or chemical-management provisions.
  • The current Standards Australia catalogue lists AS/NZS 3666.2:2011 as pending revision; project users should confirm the current edition before relying on status-sensitive requirements.
Project-specific engineering

Need the Standard applied to real equipment?

AS Applied helps frame the question. Detailed assessment, design, FEA, repair design, verification and RPEQ services are provided through XPO Engineers.

Ask an engineer