The Insights page is a running list of all the automated insights that Noda has captured for the current building, filtered by the selected timeframe in the top right. See the full list of insights here. You can filter the table using any of the dropdown options above the table.

Click on any insight in the table if you would like to dig in further.

At the top of this screen you’ll see the title of the insight – this gives you an initial indication of the fault that has been identified. For example, "AHU unable to provide cooling to space."

Below the title is the second part of the error message - this provides more detail on what the issue is. It also gives an indication of what points on which equipment the rule is looking at.

In the example shown, the cooling command is on, but the temperature split across the coil is less than 4 degrees Fahrenheit. This insight is looking at both the cooling command point and the temperature set points in a specific AHU. It’s indicating that the unit is not cooling as it should be.

The final part of the insight message, next to the flashlight icon, is a suggested next step to further analyze and ideally resolve the problem. The Noda Analytics team writes these messages for each rule in our library.

Other useful information is contained in the tables directly below the messages. The equipment name is hyperlinked to the equipment page where you’ll find all of the data associated with that equipment, not just the detail on the point in fault.

Other important pieces of information to consider as you’re reviewing the insight is the date range, the last occurrence, and the active/inactive status. This will give you an idea of how long this issue has been happening and at what interval. It will help you prioritize efforts to find a resolution and it will also help you contextualize the issue against other issues that you know occurred during that same time period.

The Insight slide out also contains four tabs for additional detail, defaulting on the Activity tab. The chart that shows here is pre-populated with the exact points this insight is measuring and the date range you’re looking at. To add more points to this chart, click the three dots to the right of the EXPORT button. If you’re working with contractors to further analyze or resolve this issue, you can easily export the chart as a CSV or PNG to share to those outside the Noda system.

Occurrences offers a table view of all the times this Insight has sparked within the date range of your original filter. We find this helpful in the first phase of triage to quickly assess the severity of the problem and to start analyzing the potential underlying issue.

Notes are a helpful place to put information you uncover as you go about resolving the issue. The notes stay with the analytic itself, so if the Insight pops up again, you’ll have the notes from the last time you worked on it to easily refer back to.

Work Requests are a great way to turn Insights into action. We will cover it in a separate Help Center article.

A natural starting place with Insights is the Priority filter. This is a dynamic setting so insights can become higher or lower priority based on several factors, including how long they have been occurring. Higher priority issues also have the greatest potential to impact things like energy consumption, comfort or equipment longevity. If you want to effect the most amount of change with the shortest amount of time, filter your Insights page by Priority.

Another great way to filter a long list of Insights is by Equipment. For example, if you have a service technician scheduled to check out your RTU, you may want to put as much on his plate as possible for that visit. A filtered list of Insights by equipment can help you do that.

In order to take action on an insight, you have a few options:

These options can be found by clicking the + button on the right side.