Test and tag in data centres: AS/NZS 3760 intervals, scope and registers

A data centre looks like the easiest test and tag site there is: clean, cool, secure, and full of equipment that never moves. Then a tenant moves in with three pallets of servers, a contractor crew arrives for a fit-out with their own leads and tools, and the operator asks for a register that ties every tag to a hall, row and rack. Test and tag in a data centre is less about the testing and more about scope, intervals and records.

This guide covers how AS/NZS 3760 intervals apply across a data centre, which items are usually in scope, what operators expect from tags and the asset register, and how to line re-test cycles up with tenant moves.

Intervals by area

AS/NZS 3760 sets maximum intervals by the environment equipment works in, not by the building. A single data centre spans several environments. Our AS/NZS 3760 intervals guide has the full schedule; this is how it typically maps to a data centre.

These are the standard’s indicative intervals. The operator’s site rules, a risk assessment or your state’s WHS regulations can all shorten them, and many operators set one cycle for all contractor equipment regardless of the standard.

One exemption is worth knowing. AS/NZS 3760 treats equipment over 18 kg as stationary, and says stationary equipment on a cord that is not flexed, not exposed to damage and not in a hostile environment does not need routine in-service testing. Where it is only unplugged for maintenance or cleaning, a visual inspection and an earth continuity test are enough. Many racked servers and storage arrays sit in that group. Operators often ask for the five-year cycle anyway, so agree in writing which applies before you quote.

What is in scope

AS/NZS 3760 covers equipment connected to the supply by a flexible cord and plug. On a data centre that usually means:

• Contractors’ power tools, extension leads, power boards and portable RCDs.
• Rack PDUs that plug into a socket-outlet, and the cord sets that feed them.
• Servers, switches and storage plugged into rack PDUs.
• Office and network operations centre equipment: monitors, chargers, kitchen appliances.
• Cleaning equipment, portable fans, heaters and dehumidifiers.
• Staging and loading dock equipment, including battery chargers.

Out of scope is the fixed installation: busway, tap-off units, outlets and hard-wired equipment. Those are verified under AS/NZS 3000 and on the operator’s periodic verification cycle, covered in our data centre periodic verification checklist.

Agree who tests what. In colocation sites tenant equipment is often the tenant’s responsibility, while the operator covers house equipment and requires contractors to bring their own gear already tested and tagged. Get the split in writing before you quote, and record the owner against every asset.

Testing racked IT equipment

Powering a production server down for an insulation resistance test is rarely an option, and a 500 V DC test can stress equipment with built-in surge protection. AS/NZS 3760 allows a protective conductor or touch leakage current measurement as the alternative for equipment like this, with the limit set by the equipment class. Plan these tests inside the tenant’s maintenance window, one cord of a dual-corded server at a time, so the server stays up on its other supply.

Fixed RCDs on rack feeds are a separate job with their own schedule. See the RCD testing schedule for data centres.

Lining re-tests up with tenant moves

Tenant moves are where data centre registers go wrong. Equipment arrives, leaves and changes racks between scheduled visits, and the register drifts. A few habits keep it accurate:

• Move-in. Brand-new equipment does not need a test under AS/NZS 3760. It is examined for damage and given a tag that says new to service, with the date it entered service, the next due date and a note that it has not been tested to AS/NZS 3760. Second-hand or relocated equipment from another site is tested before it goes into service.
• Re-stacks. Equipment that is unplugged and moved should be inspected when it lands, and its location updated in the register the same day.
• Move-out. Mark departed equipment as removed from service. Keep its history instead of deleting it.
• Batch by tenant and hall. Set each tenant’s cycle from the anniversary of their move-in, and test a hall or cage in one visit. Items tagged mid-cycle can be pulled forward to the next batch so the whole cage falls due together.

Tags and the asset register

At a minimum each tag identifies the item and shows it passed. Data centre operators usually want more from the register behind the tags:

• An asset ID that matches the operator’s maintenance system.
• Location down to hall, row and rack.
• Owner: operator, tenant or contractor.
• Equipment class, test results, verdict and next due date.
• Who tested it, and the instrument used with its calibration due date.
• Failed items, where they were quarantined and what happened to them.

Place tags near the plug end where they can be read without unplugging anything, and use tags rated for the heat if they live in a hot aisle. Construction zones often use a colour-coded tag scheme so out-of-date equipment is obvious at a glance; follow the site’s scheme.

Contractor equipment at induction

Most operators check contractor equipment at the door. Expect security or the site’s electrical lead to look for a current tag on every tool, lead and power board before it enters the hall, and to turn away anything out of date. On a large fit-out with a three-month cycle, that check catches crews every quarter.

The simple fix is to test your own kit on a fixed date ahead of each cycle, keep the register on your phone, and be able to show the result for any item when asked. A tag that can be scanned to show its record settles the question in seconds.

Gaps auditors commonly find

• Tags with no matching entry in the register, or the reverse.
• Equipment that moved racks or halls while the register still shows its old location.
• Failed items with no record of where they went.
• Racked equipment put on a five-year cycle when it is regularly unplugged and moved.
• No record of which instrument was used, or an instrument past its calibration date.

Documenting the work in Field Efficient

Field Efficient has a test and tag workflow built around AS/NZS 3760.

• QR asset tags. Print durable tags on a Bluetooth label printer as each item passes, with the next due date on the tag. Anyone can scan the QR to check the result; you scan it to open the item’s full record on the next visit. More on label printing.
• Limits by class. Results are checked against the AS/NZS 3760 limits for the equipment class, including the leakage current alternative, and the retest date is set from the environment you choose.
• Any tester. Import results from your PAT tester’s export, whatever the brand, or connect a supported tester directly over Wi-Fi.
• Calibration register. Your testers and their calibration due dates are in one place, with a reminder before calibration falls due.
• Signed reports anyone can check. The register goes to the operator as a signed PDF with a verification link.
• Works with no signal. Keep tagging in shielded halls and basements; results sync once you are back in range.
• Fixed wiring in the same job. Board-by-board verification and RCD results sit beside the test and tag register, so the operator gets one set of records.

Related guides

• Data centre periodic verification checklist
• RCD testing schedule for data centres
• Test and tag intervals: the AS/NZS 3760 schedule
• Test and tag labels that verify themselves
• Free test and tag due date calculator

This guide is general information, not compliance advice. Always work to the current editions of AS/NZS 3760 and AS/NZS 3012, the site’s rules, and your state or territory’s WHS requirements.