Asset, time and displayed event
Record the unit or room and the event as shown in available records. Preserve the distinction between a controller timestamp and when someone first noticed the condition.
CRITICAL COOLING PLANNING GUIDE
Critical Cooling Alarms: Build a Clear Handoff
A CRAC alarm on a controller is not the same as a message received by the right person. Use this handoff record to connect the equipment event, notification route, acknowledgement and next responsible action.
Describe the issue in your own words. Start with the information you have.
Critical cooling
NYC & Northern NJ
- EventWhat the unit reported
- NotificationWhat reached the platform and contact
- ActionAcknowledgement and responsible next step
AT A GLANCE
Track the event through to a human decision
A cooling unit can report an event locally, a monitoring system can receive it, and a person can still miss the notification. Those are separate stages. The worksheet below helps facilities and IT record each stage and identify where a cooling incident handoff is incomplete without changing live controls.
Alarm handoff record — use available event records and site-approved communication; this is not a live-controls test procedure.
Scroll horizontally to view all columns.
| Stage | Record from the incident | Responsible contact | Gap to resolve |
|---|---|---|---|
| Unit event | Asset, displayed event and controller timestamp | Equipment / mechanical contact | Is the original event identifiable? |
| Observed impact | Affected room, reported condition and observation time | Site facilities / IT contact | Are facts separated from an assumed cause? |
| Platform receipt | Event record and receipt time, if available | Controls / monitoring contact | Did the event reach the expected platform? |
| Notification delivery | Destination, delivery evidence and time | Notification-system owner | Did the intended person receive it? |
| Acknowledgement | Named responder and acknowledgement time | Designated incident contact | Who owns escalation if there is no response? |
| Assigned action | Mechanical, controls, IT or site action accepted | Named responsible team | What is the next agreed action? |
| Resolution record | Service finding and agreed return-to-service status | Responsible site and service contacts | What evidence supports closure beyond a cleared message? |
01 · PRACTICAL GUIDANCE
Keep the original event identifiable
The service team needs to know what the equipment reported.
Observed operating impact
Note the reported room condition and affected equipment separately from an assumed cause. An alarm name alone is not a diagnosis or instruction to replace a component.
02 · PRACTICAL GUIDANCE
Follow the notification route
A message must cross several interfaces before someone can act.
Controller to platform
Identify the responsible controls or monitoring team and whether the event was recorded in the expected system. A local display and a platform record are different evidence.
Platform to responsible person
Record the configured destination, actual receipt and acknowledgement. Escalation should have an owner when the initial contact is unavailable.
03 · PRACTICAL GUIDANCE
Close the loop after the handoff
Acknowledgement does not mean the fault has been repaired.
Who owns the next action?
Distinguish site incident decisions, mechanical service, controls investigation and IT action. Record the assigned person or team and the action they accepted.
What established resolution?
Document the service finding and the agreed return-to-service status. A cleared message alone should not be treated as proof that the underlying problem was corrected.
Follow one event through the worksheet
Choose a real historical event when records are available, or a clearly labeled tabletop scenario. Begin with what the cooling equipment reported and when. Then follow the evidence through the monitoring platform, message delivery, acknowledgement and assigned action. Do not skip from an equipment alarm directly to an assumption that someone responded.
For a hypothetical event that appears in the monitoring log but never reaches the on-call contact, the missing step is different from a unit that never reports its condition. The worksheet helps locate that break. The equipment controls and the notification route may need different specialists, so the finding should identify the stage rather than call everything an HVAC alarm problem.
Different records can describe different stages of the same event
A unit event log, a monitoring receipt and a notification record do not necessarily represent the same moment. When tracing an incident, preserve the event identity and the meaning of each timestamp. If timing or identity cannot be reconciled, record that uncertainty for the responsible platform team.
This avoids concluding that an alert was delayed solely because two records appear different. The worksheet should show which stage each record supports and where evidence is missing. It is a tool for clarifying the handoff, not for assigning a cause from an unexplained time difference.
Acknowledgement is not the same as completed action
A message can be acknowledged while the mechanical problem remains unresolved. The handoff should identify who accepts responsibility for the next action, what that action is and how another person knows it has occurred. A receipt or read status may establish message delivery without establishing that a service request was placed.
This distinction matters when several teams share responsibility. Facilities may investigate the mechanical condition, IT may manage equipment operation and a monitoring provider may administer notifications. Their responsibilities should connect clearly. Airplex does not automatically receive or monitor a site’s alerts because it services the cooling equipment; any monitoring or response arrangement must be expressly established.
Review the chain without creating an uncontrolled equipment event
An owner-level review can use existing logs and contact records to identify gaps. Compare timestamps and event identifiers where available, and record missing evidence as unknown. This can reveal an outdated contact route or unassigned action without changing live cooling controls.
If an end-to-end demonstration is needed, the responsible technical and site teams should agree a suitable authorized method. This guide does not instruct an operator to stop cooling, force a fault or change an alarm threshold. The purpose is to verify the handoff safely within the site’s procedures, with the actual equipment and monitoring responsibilities respected.
Close the review by assigning each gap and identifying the evidence needed to resolve it. A repaired cooling unit, a corrected notification route and an updated contact responsibility are separate outcomes. After staffing, platform or equipment changes, revisit the relevant part of the chain so an old successful handoff is not assumed to describe a new arrangement.
COMMON QUESTIONS
Critical Cooling Alarm Handoff questions
Does an alarm prove the cooling unit has failed?
No. It is information that must be interpreted with the model, event sequence and operating findings.
Can I reset the controller to clear the problem?
This guide does not authorize resets or control changes. Follow the site’s approved process and have qualified personnel investigate the event.
Does Airplex monitor my alarms automatically?
Monitoring is a separate service arrangement. Confirm who receives alerts, who responds and what attendance or follow-up is included.
Who should receive a critical-cooling alert?
The facility should define responsible contacts and escalation based on its operations. The worksheet makes that arrangement visible; it does not assign responsibility without agreement.
What if the alarm was acknowledged but nobody called for service?
That suggests a gap between acknowledgement and assigned action. Identify what the acknowledgement was intended to mean, who owned the next step and what record should show that step occurred. The fix may concern the incident process or monitoring arrangement rather than the cooling unit itself.
Can we review the handoff without generating a real cooling fault?
Yes, existing event records and a tabletop scenario can help identify missing stages or responsibilities. Any functional demonstration should use a method agreed by the responsible technical and site teams. Do not stop equipment or alter live settings just to create an alarm for the worksheet.
RELATED GUIDES & SERVICES
Find the service for the work you need
FURTHER READING
Technical references
AIRPLEX MECHANICAL
Discuss a Cooling Alarm Issue
If cooling is failing now, call Airplex first and follow your site’s incident procedure. For recurring notification problems, use the worksheet to identify the missing handoff.