TwinWorX: Fault to Fixed

How does your team get from alarm to a verified fix today?

8:40 a.m. Air handler 3 can't hold its supply air temperature, even with the cooling valve commanded fully open. Fourteen rooms are getting warm.

In most buildings, that's fourteen alarms, a technician walking floors, and a ticket that says "too hot on 4."

Here's the same morning with TwinWorX:

1️⃣ Detect. A fault rule fires only once the fan is proven, start-up is over and the condition has persisted, so a passing blip wakes no one up. TwinWorX ships with ~1,075 rule templates across 120+ equipment classes.

2️⃣ Root cause. TwinWorX follows the model upstream: fourteen symptoms, one source, AHU-3. Probable cause: cooling isn't reaching the coil, so the valve is the first place to look.

3️⃣ Locate. The fault shows on the AHU in its mechanical room, and on the floor plans, every space it serves.

4️⃣ Work order. One ticket goes to your maintenance system, carrying the asset, location, priority, probable cause and the trend that proves it. The technician knows where to start, and what to bring.

5️⃣ Close the loop. When the work order closes, the status comes back to TwinWorX. The fault is watched through the next period of cooling demand and reopened if it returns.

From fault to fixed, and proven.

The Workflow Engine that runs this journey runs sequences and logic across every connected system — this is one of many.

How does your team get from alarm to a verified fix today?