Labs21 Sub-Metering Guidelines for Laboratory Facilities

Transcription

1 DRAFT OUTLINE Note: This draft outline is only a strawman to facilitate discussion. It is expected that it will be revised based on stakeholder review and input. Please provide comments using track changes and/or comment balloons. For this iteration, we recommend that you focus your comments on: Outline and Scope of the document Areas where you can provide more detailed input once the outline and scope have been finalized. i. Preface ii. Acknowledgements iii. Glossary 1 Introduction Labs21 Sub-Metering Guidelines for Laboratory Facilities 1.1 Purpose and Scope This section will describe the motivation for developing these guidelines (e.g. federal requirements, etc.); the scope (focus on laboratory buildings); how to use these guidelines; how not to use these guidelines; how they were developed; how they relate to other documents, etc. 1.2 Framework and Approach This section will explain the overall approach, as reflected in the diagram below. Applications Metrics Metering Req. Measure efficiency Measure GHG emissions Allocate energy costs Identify billing discrepancies Enable demand response Reduce peak demand Validate power quality Track infrastructure capacity. Total kbtu/sf EleckWh/sf Fuel kbtu/sf Annual CO2/sf $/sf Peak W/sf Ventilation W/cfm Cooling ton hrs. Hardware Elec facility Gas facility Chilled water BTU meter. Software Trending & Archiving Multi variable charting Prioritize applications Normal process : New construction & retrofits Identify metrics Derive metering req. Alternative process : Improve use of existing metering capability Identify viable applications Derive viable metrics Identify existing metering 1

2 2 Prioritize Applications This section will provide guidelines on how to identify and prioritize the list of organizational applications that require sub metering. The approach used will consider the relative importance of each application for different stakeholders using a matrix similar to the one shown below. The resultant weighted totals identify those business cases with the greatest stakeholder interests as well as business case priorities for each stakeholder. 2.1 Definition of Applications This section will be used to describe the need/benefit of each metering application. It is not intended to be an in-depth tutorial of the application, although links to such information should be provided (information hosted by Labs21) Measure Efficiency: The measurement of energy efficiency may be expressed in terms of square footage, hours of operation, type of operation Measure GhG Emissions: In order to effectively develop the CO2 footprint of the laboratory environment This CO2 footprint helps quantify the environmental consequences of the laboratory's total operation in terms of a functional CO2 common denominator. The use of such a universal metric allows the laboratory to make investment decisions; measure progress towards achieving carbon neutrality; benchmark performance against goals and other similar institutions; and in general, take responsibility for its actions (Sustainable NREL) Allocate Energy Costs: Identify Billing Discrepancies: Enable Demand Response Identify Load Shed Oppty: Reduce Peak Demand: Validate Power Quality: Track Infrastucture Capacity: Personnel Safety: 2

3 2.2 Definition of Stakeholders This section will be used to describe stakeholders and their areas of focus/concern (KPI s) related to submetering O&M Operations and Maintenance personnel EH&S Sustainability Finance etc 2.3 Analyze Stakeholder Priorities Upon finalizing stakeholders and business cases (maybe we limit to 10?), we will create an embedded tool that will build on each business case. For example, the business case of cost allocation will drive further decision tools around business processes, financing tools, hardware, software, etc... eventually linking to "like" business cases, additional topics of consideration (potential tax implications, complimentary natures of like applications, etc), and the on-line Benchmarking Tool Business Case Stakeholders O&M (PM) EH&S Sustainability Finance User 5 User 6 Energy Efficiency GhG Emissions Cost Allocation Billing ID Demand Response Peak Demand Analysis Power Quality Capacity/Utilizaiton

4 Metering Selctrion Criteria Intensity Capacity/Utilizaiton Power Quality Peak Demand Analysis ID Demand Response Billing Cost Allocation GhG Emissions Energy Efficiency 10 0 O&M (PM) EH&S Sustainability Finance User 5 User 6 Stakeholders 4

5 3 Identify and Prioritize Metrics This section will describe the metrics required for each of the applications. This is a manyto-many mapping i.e. each application requires multiple metrics and each metric may be used for multiple applications, as shown in the framework above. A summary table can be used to map and prioritize the metrics, as shown below. Applications Total kbtu/sf Elec kwh/sf Fuel kbtu/sf Annual CO2/sf Metrics Utility $/sf Peak W/sf Vent W/cfm Measure efficiency Measure GHG emissions Allocate energy costs Identify billing discrepancies 5 Enable demand response Reduce peak demand 5 Validate power quality Track infrastructure capacity Priorities: 1=Low, 5= High Cooling ton hrs. The rest of this section will describe how to compute and use each metric (e.g. similar to the LBNL self-benchmarking guideline: Total Site Energy Intensity How to Compute: This metric is the sum of the total site energy use per unit of gross building area etc. It is computed as: B1 = ((de1* (de2 + de3 + de4 + de5 + de6 + de7)*1000) db1 where: B1 = Annual site energy intensity (kbtu/sf-yr) de1: Annual electrical energy use (kwh) de2: Annual natural gas energy use (Million BTU) de3: Annual fuel oil energy use (Million BTU) de4: Annual other fuel energy use (Million BTU) de5: Annual district steam energy use (Million BTU) de6: Annual district hot water energy use (Million BTU) de7: Annual district chilled water energy use (Million BTU) db1: Building gross area (ft 2 ) See section 4 for more information on the metered data items How to use: This metric can be benchmarked relative to peer buildings in the Labs21 database..etc. 5

6 Include KPI s and define how the KPI is metered and calculated so that this information can be used to accurately measure one facility against another with normalized data; or include a reference to where this established documentation exists. 3.2 Annual GHG emissions Greenhouse gas emissions will be tracked and reported based on scope (scopes 1, 2 and 3) and fuel type. Further granularity will allow users to analyze GhG as a function of user defined metrics: CO2/sf CO2/occupant CO2/kilo of product 3.3 Etc. 6

7 4 Define Metering Hardware and Software Requirements This section will describe the metering hardware and software requirements for each metrics. This is a many-to-many mapping i.e. each metric may require multiple metering hardware and software items and each metering item may be used for multiple metrics. Include best practices for capitalizing on existing data collection systems (BAS, other control/monitoring systems (intelligent circuit breakers, relays, etc), shadow metering) and maximizing value of metering systems (disaggregating, virtual metering, etc.) What drives the cost of meters (and HW vs. Installed costs). How does accuracy impact the end value and validity of the data? A summary table can be used to determine the required and optional metering hardware and software items for each metric, as shown below. Metrics Elec facility Gas facility Metering Hardware and Software Items Chilled water BTU meter. Trending & Archiving Total kbtu/sf R R R Elec kwh/sf R R Fuel kbtu/sf R R Annual CO2/sf Utility $/sf R R Peak W/sf R O Vent W/cfm Cooling ton hrs R R. Key: R=Required, O= Optional Multivariable charting The rest of this section will provide more detailed specification for each of the metering hardware and software items. 4.1 Electricity Meter for Facility Business Case 0.2% Accuracy 0.5% Accuracy Peak Demand Power Quality Event Logging Alarming Energy Efficiency R R O O GhG Emissions R Cost Allocation O R R Billing R ID Demand Response R R O R R Peak Demand Analysis R R R R Power Quality R R R R O Capacity/Utilizaiton O R R O O O Key: R = Required, O= Optional Electrical Metering Hardware 4.2 Gas Meter for Facility 4.3 Etc. 7

8 4.4 Software Requirements Now that we ve outlined what data needs to be collected for each business case we will discuss the various methods of collecting, using (trending, modeling, etc.), archiving, and displaying the data. How can collected data be put to best use? Describe best practices for data usage: What does a typical software system entail, what are the main components (basic kwh reporting, calculating demand, alarming, CO2 emissions, forecasting, normalization (weather), modeling, etc ). M&V vs. sub-metering. Value, limitations of each. 1. Software for data collection only (include estimated costs?) 2. Software for data collection and cost allocation. 3. Software for data collection, cost allocation, and conducting operational analysis and building tune-up. 4. Software for data collection, cost allocation, conducting continual operational analysis and building commissioning Describe the various communication methods for data collection and reporting data Describe options for sharing the data and pertinent information with various stakeholders. Value in sharing (or limiting) energy information and methods of doing so Describe best practices for data storage/archiving 5 Comprehensive System discussion 5.1 Typical Savings and other realized value by business case 5.2 Case studies, tips. 8