CRAC and CRAH Quarterly Data Center Preventive Maintenance Inspection

It covers the core preventive maintenance checks for data center CRAC and CRAH units, including filter condition and differential pressure, humidifier performance, sensor calibration, underfloor pressure mapping, airflow obstructions, and visible electrical condition. It also includes documentation fields for deficiencies, corrective actions, and photo evidence. The template is built for a walk-through inspection that supports both performance and reliability. It is not a full OEM service manual or a commissioning checklist.

This template is designed for quarterly use, which fits most preventive maintenance programs for critical cooling equipment. Some sites may run additional monthly checks for alarms, condensate, or filter loading if the environment is dusty or the unit is heavily loaded. If your site has stricter uptime requirements, you can clone the template and add interim inspections without changing the quarterly baseline. The key is to keep the cadence consistent so trends in pressure, humidity, and sensor drift are visible.

A qualified facilities technician, data center engineer, or HVAC maintenance contractor should perform it, depending on site policy and equipment access rules. Anyone opening panels or working near energized components should follow lockout-tagout and electrical safety procedures, and only authorized personnel should perform internal checks. If your site uses a BMS or BAS, the inspector should also know how to verify alarms and setpoints against site requirements. The template is structured so a single inspector can complete it, but it can also support a two-person safety workflow.

Yes, it supports preventive maintenance practices commonly used under OSHA general industry requirements, especially where lockout-tagout, PPE, and electrical exposure are involved. It also fits well with ANSI/ASSP safety program practices and NFPA guidance for electrical and fire-life-safety awareness in critical spaces. For food or healthcare facilities with specialized environmental controls, the same inspection logic can be adapted to site policies and internal SOPs. The template is not a substitute for code compliance review, but it helps document the checks that support it.

A common mistake is recording only yes/no answers without capturing actual readings for differential pressure, humidity, or sensor calibration. Another is skipping underfloor pressure mapping and relying on a quick visual check, which can miss airflow imbalance. Teams also sometimes forget to document bypass leakage around filter racks or to attach photos for abnormal conditions. The template is most useful when the inspector records measurable values and notes the exact location of any deficiency.

Yes, and you should. Add your site-specific target ranges for filter differential pressure, humidity, supply air temperature, underfloor pressure, and alarm thresholds so the inspector is comparing against local requirements. You can also add OEM model fields, asset tags, and links to your CMMS or work order system. If your data hall has different unit types or zones, clone the template and create variants by room, row, or criticality level.

The template is easy to pair with a CMMS because it captures the fields that usually trigger work orders: failed filters, sensor drift, leaks, abnormal vibration, and alarm faults. It also supports BMS or BAS verification by prompting the inspector to confirm communication status, setpoints, and alarm thresholds. Many teams use the inspection as the field record and then push corrective actions into the CMMS for assignment and closure. If you want tighter integration, add equipment IDs and status fields that match your system naming convention.

Anything that affects cooling reliability, moisture control, or electrical safety should trigger a corrective action. Examples include filter differential pressure outside the acceptable range, a leaking condensate line, sensor calibration drift, failed BMS communication, or visible wiring damage. If the issue could reduce airflow, create water intrusion, or cause an alarm to be missed, it should not stay as a comment only. The template is set up to separate normal observations from true deficiencies so follow-up is clear.