STD 211, 6.2.2.1.d requires the following for Historical Monthly Utility Data
A description of the submetering installed in the building (if present), including a listing of the systems metered, the frequency of data recording, and a description of the data acquisition system (fixed, portable, or integrated with the BAS), shall be provided.
BuildingSync's concept of submetering occurs at //auc:Utilities/auc:Utility/auc:MeteringConfiguration where the options are
Direct metering
Master meter without sub metering
Master meter with sub metering
Other
Unknown
For our current schematron requirements, every auc:ResourceUse must have a one-to-one link with an auc:Utility (ie exactly one ResourceUse per Utility). We can add the requirements of defining an auc:MeteringConfiguration, but it wouldn't fully meet 211's specifications.
Some options might be to:
have users drop everything into something like auc:UtilityNotes
implement a new metering system. From Cory's notes:
Characteristics:
Link to a ResourceUse
Be able to have sub-meters (or connect somehow)
MeterID
Sampling frequency
Data acquisition system configuration
Don't require users to report this.
Note that the Normative Spreadsheet doesn't seem to fully meet these requirements either, they just require what's specified in auc:MeteringConfiguration which was mentioned above.
STD 211, 6.2.2.1.d requires the following for Historical Monthly Utility Data
BuildingSync's concept of submetering occurs at
//auc:Utilities/auc:Utility/auc:MeteringConfiguration
where the options areFor our current schematron requirements, every auc:ResourceUse must have a one-to-one link with an auc:Utility (ie exactly one ResourceUse per Utility). We can add the requirements of defining an auc:MeteringConfiguration, but it wouldn't fully meet 211's specifications.
Some options might be to:
auc:UtilityNotes
Note that the Normative Spreadsheet doesn't seem to fully meet these requirements either, they just require what's specified in auc:MeteringConfiguration which was mentioned above.