Fault Detection Overview

Fault Detection and Diagnostics (FDD) continuously monitors equipment data, detects faults as they occur, and helps identify their probable root causes. This lets operators and maintenance personnel act on problems before they lead to equipment failure, wasted energy, or loss of occupant comfort. Fault Detection is industry agnostic and you can apply it to any equipment modeled in Assets.

How Fault Detection Works

Fault Detection works in two parts:

• Fault detection—Fault rules defined on equipment in Assets evaluate live data against a condition, such as a temperature exceeding a threshold for a set duration or simultaneous heating and cooling. When a rule is true, the Fault Detection engine raises a fault and logs it as a fault incident. Each fault has a severity, an optional cost expression to help prioritize repairs, and up to 20 related values captured when the fault occurs. Learn more

• Fault diagnostics—A diagnostic model relates possible causes to the symptoms they produce, with a weighting for each pairing. Symptoms are mapped to expressions or alarms on the equipment. When symptoms appear, Fault Detection evaluates them against the model and lists the possible causes sorted by probability. Learn more

Fault rules and symptom mappings belong to the equipment, on its Fault Detection tab in Assets. When you add the tab to an equipment class, every piece of equipment created from the class inherits the same faults. Diagnostic models are configured separately, under Analytics > Fault Detection in Workbench, so a single model can serve all equipment of the same type.

Viewing Faults

Faults are exposed as OPC UA alarms. You can examine faults and their related values in Fault Viewer in GraphWorX.