At a high school in a US public school district, a newly installed chiller had been faulting and dropping offline. One Monday morning it failed again, on the same morning the district's own building automation system (BAS) front-end was down. The district's team could not see the chiller at all. PEAK could. It flagged the failure first thing, CIM's US engineering services partner ADG Energy confirmed the risk within the hour, and a technician was dispatched in time to correct the problem before teachers or students knew anything was wrong.
At a glance
- First thing Monday: PEAK flags a failed chiller status
- 30 to 60 minutes: for ADG Energy's chilled water trend to confirm the building was at real risk
- BAS front-end down: PEAK still collecting and reporting data throughout
- No disruption: fixed before staff or students noticed
- New plant: a recurring fault on recently installed equipment, on the record
Challenge
School maintenance teams live by the start of the school day. At this district, the team checks the BAS every morning for major failures, so that each school opens with working heating and cooling.
One of those schools had a new chiller that was not behaving like one. It had been faulting and dropping offline. A morning check catches a chiller that has already failed overnight, but it does not help with one that drops out mid-morning, or on a day when the BAS itself is not available.
ADG Energy, the district's engineering services partner, had recently brought the site onto PEAK, with the CIM team putting in extra hours over the preceding weeks to get the platform, and ADG Energy's team, up and running.
The morning
First thing on Monday, PEAK raised a failed chiller status alert.
An ADG Energy analyst went straight to the building controls, a Siemens Desigo system, to check additional parameters and validate the alert. The chiller was confirmed offline. But the building's chilled water temperatures had not yet started to climb: the thermal mass of the chilled water loop was buying time. He put the district on notice and kept watching.
Within 30 to 60 minutes, the trend told him the building was in real jeopardy. He called the district again: a technician needed to be dispatched immediately, or that part of the school would lose cooling with students in class.
The dispatch went out. The district's team found and corrected the problem before the people in the building were aware of it.
The blind spot
The detail that matters most is what the district could not see. Their BAS front-end was down that morning, so they had no view of the chiller's status at all. PEAK, connecting to the building's data independently of the front-end, was still collecting and reporting it.
Without that independent view, the first sign of trouble would have been rising classroom temperatures, followed by calls from teachers and the principal. By then, the fix would have come too late to prevent disruption. Instead, the problem was handled as a routine dispatch.
Why this one matters
Independent monitoring is a resilience layer, not a duplicate dashboard. A BAS front-end is a single point of visibility. When it goes down, the people responsible for the building lose sight of their plant at exactly the wrong moment. PEAK is BMS-agnostic and fully independent of any equipment, controls or BMS manufacturer, so it keeps watching when the site's own tools cannot.
New equipment is where fault detection earns its keep. It is tempting to assume new plant needs less monitoring. In practice, new equipment and new builds are where startup and commissioning problems surface, and where recurring faults can still be raised with the installer while the equipment is under warranty, rather than paid for twice by the owner. For another example of catching issues on new plant before they become the owner's cost, see how a defects liability period review of a student facility uncovered key system gaps before handover.
The platform works best in the hands of people who act on it. PEAK raised the alert, but it was the ADG Energy analyst who validated it, watched the trend, and made the call to dispatch at the right moment. CIM works with more than 20 engineering partners who use PEAK to deliver this kind of service to their own clients.
Results
- Failed chiller status flagged by PEAK first thing on a school-day morning
- Alert validated in the building controls and trended until the risk was clear
- Technician dispatched in time to prevent loss of cooling to occupied classrooms
- Full visibility maintained while the district's own BAS front-end was down
- Recurring fault on newly installed plant documented and acted on
