| A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | CalTRACK Compliance Checklist | |||||||||||||||||||||||||
2 | CalTRACK Requirement | CalTRACK | Verification | Billing | Daily | Hourly | ||||||||||||||||||||
3 | Project data must include an intervention active date | 2.1.3.1.3 | eemeter | |||||||||||||||||||||||
4 | The baseline must be 365 days immediately prior to the intervention start date | 3.1.3 | eemeter | |||||||||||||||||||||||
5 | Unless fitting baseline models using hourly methods, the number of days of consumption and temperature data missing should not exceed 37 (10%). | 2.2.1.2 | eemeter | |||||||||||||||||||||||
6 | For hourly methods, baseline consumption data must be available for over 90% of hours in the same calendar month as well as in each of the previous and following calendar months in the previous year. | 2.2.1.2 | eemeter | |||||||||||||||||||||||
7 | Less than 50% of high-frequency data can be missing. Missing data must be imputed as average for the time period. | 2.2.2.1 | eemeter | |||||||||||||||||||||||
8 | Daily temperature data has been checked for 50% coverage, if higher frequency temperature data is being used to calculate data temperature | 2.2.2.3 / 2.2.3.3 | eemeter | |||||||||||||||||||||||
9 | Temperature data has been checked for coverage across billing periods so that high-frequency temperature data covers 90% of each averaged billing period | 2.2.3.2 | eemeter | |||||||||||||||||||||||
10 | CDD balance point range has been limited to between 30 and 90 degrees | 3.2.1.1 | eemeter | |||||||||||||||||||||||
11 | HDD balance point range has been limited to between 30 and 90 degrees | 3.2.1.2 | eemeter | |||||||||||||||||||||||
12 | Cooling balance point must be greater than or equal to the heating balance point | 3.2.2.1 | eemeter | |||||||||||||||||||||||
13 | Balance point search must check at least every 3 degrees (or fewer) within the range | 3.2.3 | eemeter | |||||||||||||||||||||||
14 | Regression model must follow the form: UPDp,i=μ+βH,i∗HDDp+βC,i∗CDDp+εp,i , | 3.3.2 | eemeter | |||||||||||||||||||||||
15 | Daily Average Usage has been correctly specified | 3.3.3.1 | eemeter | |||||||||||||||||||||||
16 | Cooling degree days have been correctly specified | 3.3.4.1.1 | eemeter | |||||||||||||||||||||||
17 | Heating degree days have been correctly specified | 3.3.5.1.1 | eemeter | |||||||||||||||||||||||
18 | Daily models are fit using ordinary least squares regression | 3.4.1 | eemeter | |||||||||||||||||||||||
19 | Billing models are fit using weighted least squares regression | 3.4.2 | eemeter | |||||||||||||||||||||||
20 | All combinations of candidate balance points are tried | 3.4.3.1 | eemeter | |||||||||||||||||||||||
21 | Only include candidate models where each parameter estimate is not negative | 3.4.3.2 | eemeter | |||||||||||||||||||||||
22 | Select the candidate model with the highest adjusted R-squared | 3.4.3.3 | eemeter | |||||||||||||||||||||||
23 | If a day in the reporting period is missing a temperature value, the corresponding consumption value for the day should be masked | 3.5.1.1 | eemeter | |||||||||||||||||||||||
24 | If a day in the reporting period is missing a consumption value, the corresponding counterfactual for that day should be masked | 3.5.2.1 | eemeter | |||||||||||||||||||||||
25 | Avoided energy use should not be calculated when consumption data is missing | 3.5.4.1 | eemeter | |||||||||||||||||||||||
26 | For daily and billing methods, avoided energy use should be calculated using the form: AEUp,i=np∗(μi+βH,i∗HDDp+βC,i∗CDDp−UPDp) | 3.6.1 | eemeter | |||||||||||||||||||||||
27 | For hourly methods, divide a week into 168 hourly intervals starting on Monday | 3.8.2 | eemeter | |||||||||||||||||||||||
28 | To determine occupancy status, fit a single HDD and CDD weighted least squares model to the baseline dataset using fixed balance points for heating (50 degrees) and cooling (65 degrees) using the following form: UPHpi=μi+βHiHDH50p+βCiCDH65p+ϵpi | 3.8.3 | eemeter | |||||||||||||||||||||||
29 | To determine occupancy states of a building for hourly methods, group the predictions of the occupancy model into occupied and unoccupied modes by time of the week | 3.8.4 | eemeter | |||||||||||||||||||||||
30 | To determine which of the temperature bins for the hourly methods to include in the regression design matrix, count the number of hours in each default bin and combine the bins with fewer than 20 hours | 3.9.1 | eemeter | |||||||||||||||||||||||
31 | To develop an hourly methods design matrix, first sort temperature values into bins to create a temperature matrix | 3.9.1 | eemeter | |||||||||||||||||||||||
32 | Compute an hourly methods design matrix comprising a dependent variable of total consumption per hour and independent variables of seven (or fewer) temperature features, 168 binary time-of-week dummy variables, and an occupancy binary variable. | 3.10.1 | eemeter | |||||||||||||||||||||||
33 | For hourly methods, avoided energy use should be calculated using the form: AEUpi=∑αtTOWp+∑βT,nTcn,p+∑occupiedαtTOWp+∑occupiedβT,nTcn,p−UPHp. | 3.12.1 | eemeter | |||||||||||||||||||||||
34 | A CVRMSE value should be used to define building-level model uncertainty | 4.3.2.1 | eemeter | |||||||||||||||||||||||
35 | CVRMSE should be calculated using the following form: CV(RMSE)=∑Pp=1(Up−Up^)2P−c‾‾‾‾‾‾‾‾‾‾‾√U⎯⎯⎯⎯⎯ | 4.3.2.2 | eemeter | |||||||||||||||||||||||
36 | ||||||||||||||||||||||||||
37 | Selected weather station must include latitude and longitude coordinates | 2.1.2.1 | eeweather | |||||||||||||||||||||||
38 | Weather station information must include IECC Climate Zone | 2.1.2.3 | eeweather | |||||||||||||||||||||||
39 | Weather station information must include IECC Moisture Regime | 2.1.2.4 | eeweather | |||||||||||||||||||||||
40 | Weather station information must include Building America Climate Zone | 2.1.2.5 | eeweather | |||||||||||||||||||||||
41 | If the site is in the state of California, weather station information must include California Building Climate Zone Area | 2.1.2.6 | eeweather | |||||||||||||||||||||||
42 | Weather station information must include observed dry-bulb temperature data | 2.1.2.7 | eeweather | |||||||||||||||||||||||
43 | When using hourly temperature data, data may not be missing for more than six (6) consecutive hours. Missing temperature data may be linearly interpolated for up to 6 consecutive missing hours. | 2.2.4.1 | eeweather | |||||||||||||||||||||||
44 | Weather data should be converted to hourly intervals using interpolation and downsampling | 2.3.4 | eeweather | |||||||||||||||||||||||
45 | Site should be matched to nearest weather station within the climate zones that meets data sufficiency requirements | 2.4.1 | eeweather | |||||||||||||||||||||||
46 | If no weather stations within the climate zone meet data sufficiency requirements, fallback to closest weather station that has complete data | 2.4.1.1 | eeweather | |||||||||||||||||||||||
47 | Weather station matches further than 200 km from the site should be flagged | 2.4.2 | eeweather | |||||||||||||||||||||||
48 | ||||||||||||||||||||||||||
49 | Consumption data frequency must be specified | 2.1.1.1 | Provider | |||||||||||||||||||||||
50 | If data from multiple meters is combined, must be noted | 2.1.1.2 | Provider | |||||||||||||||||||||||
51 | All consumption data must be converted to units of energy consumption | 2.1.1.3 | Provider | |||||||||||||||||||||||
52 | Presence of net metering must be flagged | 2.1.1.5 | Provider | |||||||||||||||||||||||
53 | Project data must include a project start date | 2.1.3.1.1 | Provider | |||||||||||||||||||||||
54 | Project data must include an Intervention completion date | 2.1.3.1.2 | Provider | |||||||||||||||||||||||
55 | Project data must include a baseline period end | 2.1.3.1.4 | Provider | |||||||||||||||||||||||
56 | Building site data must include latitude and longitude coordinates of at least four decimal places | 2.1.4.1 | Provider | |||||||||||||||||||||||
57 | If Building site data does not include requisite latitude and longitude coordinates, the latitude and longitude coordinates of the centroid of the ZIP Code Tabulation Area (ZCTA) may be used instead. | 2.1.4.1.1 | Provider | |||||||||||||||||||||||
58 | Building site data must include time zone | 2.1.6 | Provider | |||||||||||||||||||||||
59 | If data is marked as NULL, NaN, or similar, it is considered missing | 2.2.1.3 | Provider | |||||||||||||||||||||||
60 | Values of zero (0) are considered missing for electricity data, but not gas data | 2.2.1.4 | Provider | |||||||||||||||||||||||
61 | If periods are estimated, they should be combined with subsequent periods | 2.2.2.2 | Provider | |||||||||||||||||||||||
62 | Temperature and meter data has been checked to ensure they were recorded with the same time zone | Provider | ||||||||||||||||||||||||
63 | When using billing data, estimated periods should be combined with the next period up to a 70 day limit. Estimated periods are counted as missing dta for the purpose of determining data sufficiency. | 2.2.3.1 | Provider | |||||||||||||||||||||||
64 | Excessively long Billing Periods have been removed (>35 or >70 days) | 2.2.3.4 | Provider | |||||||||||||||||||||||
65 | Excessively short Billing Periods have been removed (< 25 days) | 2.2.3.4 | Provider | |||||||||||||||||||||||
66 | Excess consumption data should be trimmed prior to analysis | 2.2.5 | Provider | |||||||||||||||||||||||
67 | Projects should be excluded from analysis if net metering status changes during baseline period | 2.2.6 | Provider | |||||||||||||||||||||||
68 | Projects should be flagged if electric vehicle charging is installed during the baseline or reporting period | 2.2.7 | Provider | |||||||||||||||||||||||
69 | If using billing data and the date provided is impossible (e.g., January 32nd), use the first of the month | 2.3.1.1 | Provider | |||||||||||||||||||||||
70 | If using billing data and the month or year is impossible, flag the date and remove it from the dataset | 2.3.1.2 | Provider | |||||||||||||||||||||||
71 | Where two time series overlap, combine into a single time series by dropping duplicate records, using the most complete version possible. If timestamps conflict, flag for review. If multiple meters present, may be aggregated. | 2.3.2.1 | Provider | |||||||||||||||||||||||
72 | Ensure time zone and daylight savings consistency across meter and temperature data | 2.3.3 | Provider | |||||||||||||||||||||||
73 | Presence of negative meter data should be flagged as possible unreported net metering | 2.3.5 | Provider | |||||||||||||||||||||||
74 | Extreme values (more than 3 interquartile ranges larger than the median) should be flagged as outliers for manual review. | 2.3.6 | Provider | |||||||||||||||||||||||
75 | CDDs are not used as a variable in the calculation for gas data. | 3.2.1.1 | Provider | |||||||||||||||||||||||
76 | A baseline model must have at least 10 non-zero degree days and at least 20 degree days per year, unless using billing data | 3.2.2.2 | Provider | |||||||||||||||||||||||
77 | To aggregate single project results from individual time periods, the following should be calculated: AEUtotal,P=∑p=1P(AEUp,i) | 4.1.1 | Provider | |||||||||||||||||||||||
78 | To aggregate multiple project results from the same time periods, the following should be calculated: AEUp,S=∑i=1S(AEUp,i) | 4.2.1 | Provider | |||||||||||||||||||||||
79 | A Fractional Savings Uncertainty value should be used to define portfolio-level uncertainty | 4.3.2.3 | Provider | |||||||||||||||||||||||
80 | Fractional Savings Uncertainty should be calculated using the following form: FSUi=ΔUsave,QiUsave,Qi=t(aM2+bM+d)CV(RMSE)∗PP′(1+2P′)1Q‾‾‾‾‾‾‾‾‾‾‾‾√)F | 4.3.2.4 | Provider | |||||||||||||||||||||||
81 | Portfolio Fractional Savings Uncertainty should be calculated using the following form: FSUportfolio=∑Ni=1(ΔUsave,Qi)2‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾√∑Ni=1Usave,Qi | 4.3.2.5 | Provider | |||||||||||||||||||||||
82 | Site level Bias should be calculated using the following form: MBi=1P∑p=1P(yp−ypˆ) | 4.3.2.6.1 | Provider | |||||||||||||||||||||||
83 | Portfolio level Bias should be calculated using the following form: FBEportfolio=∑Ni=1(MBi)2∑Ni=1Usave,Qi | 4.3.2.6.1 | Provider | |||||||||||||||||||||||
84 | ||||||||||||||||||||||||||
85 | ||||||||||||||||||||||||||
86 | ||||||||||||||||||||||||||
87 | ||||||||||||||||||||||||||
88 | ||||||||||||||||||||||||||
89 | ||||||||||||||||||||||||||
90 | ||||||||||||||||||||||||||
91 | ||||||||||||||||||||||||||
92 | ||||||||||||||||||||||||||
93 | ||||||||||||||||||||||||||
94 | ||||||||||||||||||||||||||
95 | ||||||||||||||||||||||||||
96 | ||||||||||||||||||||||||||
97 | ||||||||||||||||||||||||||
98 | ||||||||||||||||||||||||||
99 | ||||||||||||||||||||||||||
100 | ||||||||||||||||||||||||||