This article explains scores as logic modules, how they precisely reflect building performance efficiency, and how users can create and view them.
What are Scores?
Scores are special logic modules that enable users to benchmark equipment performance. Scores are summarized in the scores dashboard, allowing users to compare their equipment performance across time periods, sites and portfolios.
Figure 67. Scores Dashboard.
Scores were created to summarize large volumes of complex alerts into simple, standardized and comparable figures. There are three levels of score roll-up: ‘Equipment’, ‘Equipment Type’ and ‘Site’ (Building). The 'roll-up' process is shown below.
Figure 68. Scores Roll-up.
How Scores Work
A score can be understood as 'the amount of time the given equipment was performing within its performance target over the amount of time it was enabled.'
A score works in the same way as a logic module - it creates alerts when its logic conditions are met. What distinguishes a score from a logic module is that the former goes through a secondary processing step after its alerts are created.
The secondary calculation determines, for a given time period, the amount of time the module was not in alert over the amount of time some given condition, called the enabling condition, was ’TRUE’.
So in other words:
Score = (tenabling condition − talert) / (tenabling condition)
For example, a score for a VAV box called 'Score: Space Temperature Performance' discovers the amount of time the space served by the VAV is within 1°C of the space temperature setpoint. In other words, this score will indicate how well the VAV performs in maintaining the space temperature.
In this case, the enabling condition would be when the VAV point 'Occupancy Status' is equal to 'ON'. That is, the VAV performance is only evaluated when the VAV is working to condition the space.
Figure 69. Example Score: Space Temperature Performance.
Scores live in the Logic Builder alongside regular logic modules and are created in the same way, except for one key difference - the specification of one or more enabling conditions.
Each score module has one or more enabling condition layers, and a score cannot exist without this layer. This layer looks identical to any other logic layer, with the only difference being that the 'Enabling Condition for Performance Benchmarking' checkbox is ticked in the layer properties. Selecting this checkbox turns any logic module into a score.
For the 'Hot Water System delta-T performance' module below, the enabling condition checkbox has been ticked in the 'MechBoilerCount' layer. This means that the score is evaluated for periods of time where the MechBoilerCount' is > 0, as per the logic layer.
Figure 70. Enabling Condition Check Boxes.
Figure 71. Enabling Condition Layers.
While any logic module can be turned into a score, scores should be created to be used specifically as scores, as they work best when a few simple principles are followed.
- Prefix the module name with ‘Score:’
- Use the 'Low' severity category - the generated alerts will not be viewed, so they should be kept discrete.
- Capture all variations of the logic within the module. For example, a temperature score should include both above and below setpoint conditions in the module, rather than breaking into two separate modules.
Since scores generate alerts, their raw output can be viewed in Alerts Analysis like any other logic module. If users follow the principles above, alerts can be filtered by the term ‘Score:’, displaying all the alerts generated by the deployed scores.
Navigate to Alerts Analysis through:
→ Alerts Analysis
→ Alerts Analysis
Figure 72. Scores Alerts in Alert Analysis.
In the Scores Dashboard, users can view scores data over different time periods, categories and sites. The full set of view options in this feature are not detailed in this document, but users are encouraged to learn through their own practical exploration.
Figure 73. Scores Dashboard.