Data centre periodic verification checklist (Australia)

A data hall’s electrical installation never sits still. Tenants move in and out, racks are re-stacked, rack PDUs are swapped, new tap-off units go onto the busway and circuits are re-allocated between the A and B feeds. Each of those changes touches the fixed installation, and the operator expects signed, traceable evidence for every circuit that was touched, plus a periodic re-check of the circuits that weren’t.

This guide is for the electrical contractors who do that ongoing work on live Australian data centres. It sets out what gets re-tested on a data hall distribution board and floor PDU, maps each check to the AS/NZS 3000 and AS/NZS 3017 test types, and finishes with a checklist you can print and take to the board.

Two reasons a data hall board gets re-tested

Re-testing on a data hall falls into two buckets, and the rules behind each are different.

A fit-out alteration is new electrical work, so it carries the same verification duty as any other installation, and in most states it also needs the state’s certificate of compliance. Our certificates by state guide covers which form applies where. Periodic verification is different: it checks that an installation already in service is still safe. AS/NZS 3019:2022 calls this periodic assessment, though most contractors still say periodic verification. How often it happens is set by the operator’s maintenance plan, the insurer and the site’s risk assessment rather than by one fixed number. Many operators settle on an annual cycle for data hall distribution, with RCDs on their own shorter cycle (see the RCD testing schedule for data centres).

Where the fixed installation ends in a data hall

Data hall power typically runs from the main switchboard through the UPS to output distribution boards, then on to floor PDUs, remote power panels or overhead busway with tap-off units, and finally to the socket-outlet that feeds each rack. Everything up to and including that outlet or tap-off is fixed installation, and that is what this checklist covers.

The rack PDU plugged into that outlet, and the IT equipment plugged into the rack PDU, are cord-connected equipment. They are in-service equipment under AS/NZS 3760, not fixed wiring. Our test and tag in data centres guide covers that side.

The tests, mapped to a data hall

The test types are the same ones AS/NZS 3000 requires for any installation (see our AS/NZS 3000 verification guide for the general sequence). What changes on a data hall is where the faults hide and how you get the circuit dead long enough to test it.

The pass and fail values (insulation resistance minimums, the loop impedance limit for a given protective device, RCD trip times) come from AS/NZS 3000 and AS/NZS 3017 and depend on the circuit and device. Our free maximum earth fault-loop impedance lookup and RCD trip time limit lookup cover two of the most common questions.

Testing on a live data hall

Nothing in a data hall gets switched off casually. In practice, every periodic visit runs under a method of procedure the operator has approved, inside a change window, with a permit to work. The usual pattern looks like this:

1. Confirm the B feed (or whichever side stays live) is healthy and carrying the load before isolating the A side.
2. Identify any single-corded equipment on the circuits you plan to isolate. It needs a static transfer switch, a rack-level transfer switch or an agreed tenant outage before you touch it.
3. Isolate, lock out and prove dead, then run the dead tests for that side.
4. Restore, confirm both feeds are back and the load has rebalanced, then repeat for the other side.
5. Run the live tests last, one circuit at a time.

Expect the operator to ask for your instruments’ calibration certificates at induction, and to check that the serial numbers on your results match them.

Printable checklist: data hall board or floor PDU

One checklist per distribution board, remote power panel or floor PDU. Print the page, or keep it open on your phone at the board.

Before you start

• Method of procedure approved and change window confirmed with the operator
• Permit to work issued; isolation points and lock-out locations agreed
• Current circuit schedule and A/B feed drawings on hand
• Single-corded loads on the affected circuits identified and dealt with
• Instrument calibration certificates current and available

Visual inspection

• Board, PDU or panel labelling matches the circuit schedule
• Protective devices match the schedule for rating, type and RCD marking
• No signs of overheating, discolouration or loose terminations
• Covers, escutcheons and blanking plates all in place
• Outlets and tap-off units undamaged and correctly identified as A or B
• Bonding connections to rack frames and cable tray intact, where the design calls for them

Dead tests

• Continuity of protective earthing conductors to every outlet or tap-off
• Continuity of equipotential bonding conductors, where installed
• Insulation resistance with rack PDUs and surge protection disconnected
• Polarity at every re-terminated outlet and tap-off unit
• Correct circuit connections, including A and B feed allocation

Live tests

• Earth fault-loop impedance by the method the design documents
• RCD operation: push-button test and instrument trip-time test, both half-cycles
• Phase sequence on three-phase outlets and tap-off units
• Both feeds restored and load rebalanced before you leave the board

Records and hand-back

• Every reading recorded against its circuit, with the instrument used
• Defects listed with location, severity and the action you recommend
• Circuit schedule updated if anything changed
• Signed results issued to the operator; certificate lodged if the work was an alteration
• Next periodic due date recorded for the board

Documenting the work in Field Efficient

Field Efficient is built to produce exactly the evidence this checklist ends with.

• One board per test session. Each distribution board or floor PDU is captured as its own session, and the report groups results by board, so the operator can find any circuit fast.
• Any tester. Import exports from your installation tester’s software, or a photo of a results sheet, whatever the brand. Supported testers connect directly, and anything else can be keyed in by hand or by voice.
• Checked as you capture. Readings are checked against AS/NZS 3000 and AS/NZS 3017 limits as you enter them, and the clause is printed on the report.
• Calibration register. Your instruments and their calibration due dates live in one register, the instrument used is recorded with the results, and you get a reminder before calibration falls due.
• Signed reports anyone can check. The PDF is signed, and its verification link shows the operator who signed it, when, and a fingerprint to confirm their copy is unaltered.
• Works with no signal. Data halls and plant rooms often have poor reception. Readings queue on the device and sync once you are back in range.
• Retest reminders. Each board carries its retest date, and a reminder goes out before it falls due.

Related guides

• RCD testing schedule for data centres
• Test and tag in data centres
• AS/NZS 3000 verification: the tests every installation needs
• Australian electrical certificates by state

This guide is general information, not compliance advice. Always work to the current editions of AS/NZS 3000, AS/NZS 3017 and AS/NZS 3019, the site’s method of procedure, and your state or territory’s requirements.