The ABCAT is initially set up in a building through the following sequence of steps:
The baseline period should correspond to a time when the building mechanical systems are known to be operating correctly, typically post new building commissioning (Cx) or retro-commissioning (RCx). The length of baseline can be a minimum of four weeks if during the swing seasons where a wide range of outside air temperatures is experienced and heating and cooling systems are both operating. Required measurements include whole building heating (WBHeat) whole building cooling (WBCool), whole building electric (WBElec),
ambient outside air temperature and relative humidity or dew point temperature, all recorded in hourly intervals. Figure 1 describes the consumption monitoring that is required for the ABCAT. Ideally the WBHeat and the WBCool would be
obtained by Btu metering of chilled and hot water, but these values could also be obtained by modeling the chiller and boiler if interval meters exist that monitor chiller electric loads and natural gas consumption. A slight decrease in the ABCAT detection sensitivity would be expected in these cases due to this added modeling step and the associated uncertainties involved.
2. Obtain Building and Air Handling Unit System Details
The required information includes: floor area, exterior surface area type, orientation and U-values; AHU type, AHU air flow rates, outside air total or % of total flowrate, operating schedule, supply air temperature schedule, space set point temperatures, economizer settings, estimated occupancy and occupancy schedule, and economizer and humidifier operation details if they exist. 3. Establish Initial Values of Inputs for the Simulation Model and Calibrate
the Model
Generate an input file for simulation based on measured data and system information, and calibrate or tune the model inputs until desired accuracy is achieved
4. Correct for Bias in Model
Provide a final adjustment to simulation model by calculating the mean bias error (MBE) and subtracting this amount from to the model so that the MBE of the model is zero for the baseline period. Even a small systematic bias in the simulation will decrease the sensitivity of the fault detection process.
5. Program Regular Data Transfer to ABCAT
Develop a method by which the required measured inputs can regularly be updated and passed to the ABCAT program. In the current test facilities, Visual Basic for Applications programs link the ABCAT with consumption data files. The programs sort, fill missing data with linear interpolation when applicable, summarize and import the data into the ABCAT program in its required format. Once the ABCAT is configured for the particular building through the steps described above, the program is ready for execution. Figure 2 is a process flow diagram which visually describes the following five steps in the ABCAT methodology:
1. Import Measured Data
Evoke the program developed in step 5 of the initial setup steps above from the ABCAT program.
The required inputs are passed to the energy simulation routine, where the heating and cooling consumption is simulated.
3. Data Analysis
The simulated consumption and measured consumption are passed to the data analysis routine that generates the building performance plots, compares and performs calculations on the two values, applies fault detection methods, and reports diagnostic and energy consumption statistics.
4. Evaluation
The user of the tool is to evaluate the data presented and determine whether or not a fault exists that requires action. The user plays an important role in defining fault triggers and manipulating the plotted data with easily adjustable parameters to suit their site specific preferences. Abnormal periods of
consumption can sometimes be explained by irregular activities (i.e. shutdowns, holidays, snow days, power outages, etc) in the building, or by an incomplete or faulty measured data collection process. The user in this step applies their knowledge of the building to determine if any known but unaccounted for factors in the ABCAT model contributed to the fault. If no significant fault is identified, or if the faulty performance persisted only for a short period and is explainable, then no action is needed. If this is not the case, and action is required, then the process moves to the next step.
5. Action
The type of action taken will depend on whether the faulty condition observed is the result of a required change in operations or whether it was caused by a system or component failure or a change in control to a less than optimal setting. In the case of the latter, the user or other experts can use the diagnostic information provided by the ABCAT to help identify and correct the fault, and follow up observations should review a return to expected performance. If required changes in operation (such as work schedule changes or construction retrofits) are behind the observed deviations in energy performance, and the new energy performance in the building is considered to be “correct”, then the ABCAT simulation must be recalibrated to reflect the new building
Data Storage Simulation Routine Is Action Required? Is Cause Due to Required Change in Operation No Do Nothing Continue Yes
Evaluation
Address Fault No ReCalibrate Simulation Yes WBCool WBHeat WBElec Outdoor Tdb HumBuilding Specific Import Function
Tdb, Hum, WBElec WBCool& WBHeat
ABCAT Software
Measurement
ABCAT PROCESS FLOW
User Interpretation 1 2 3 4 5 Data Analysis Data Manipulation Alarm Thresholds Periods Analyzed Utility Costs Data Visualization Fault Detection Diagnostic Data Consumption Totals Data Manipulation Measured Simulated