Monitoring-Based Commissioning: A Case Study in Higher Education. Janelle H. Griffin, PE, CCP, LEED AP

Transcription

1 Monitoring-Based Commissioning: A Case Study in Higher Education Janelle H. Griffin, PE, CCP, LEED AP

2 AIA Quality Assurance The Commissioning Association is a Registered Provider with The American Institute of Architects Continuing Education Systems (AIA/CES). Credit(s) earned on completion of this program will be reported to AIA/CES for AIA members. Certificates of the Completion for both AIA members and non-aia members are available upon request. This program is registered with AIA/CES for continuing professional education. As such, it does not include content that may be deemed or construed to be an approval or endorsement by the AIA of any material of construction or any method or manner of handling, using, distributing, or dealing in any material or product. Questions related to specific materials, methods, and services will be addressed at the conclusion of this presentation. 2

3 Learning Objectives 1. Describe one approach to integrating a monitoring-based platform to the BAS and meters within a secure IT network 2. Identify the potential of applying rules-based analytics and filtered feedback on building performance to harness the power of big data in their existing systems 3. Understand the MBCx process in an integrated model where the MBCx provider guides the owner in a results-oriented process 4. Understand how an ongoing MBCx platform can augment their maintenance program 3

4 Monitoring-Based Commissioning An extension to a facilities BAS designed to collect and analyze equipment and environmental data to provide notification and operational recommendations resulting in a continuously commissioned facility Benefits: 1. Reduce Total Cost of Ownership (energy and maintenance) 2. Improve Performance 3. Provide Feedback Mechanisms for Energy Managers (RCx, ESPC, MBCx) 4

5 What Makes a Good Candidate for MBCx? Availability: Meters, DDC vs. Pneumatic, Trends & Trending Capability, Integration Requirements Opportunities for Improvement: EUI, Maintenance Cost Enhanced M&V: Previous RCx, ESPC 5

6 Case Study: Candidate s 1. Undergraduate Science Laboratory Analog Phoenix lab terminal unit controllers Niagara R2 71,000 SF, Constructed kbtu/sf 2. Research Lab and Teaching All DDC Niagara R2 45,000 SF, Constructed kbtu/sf 3. Plant Sciences 42,000 SF, Complete HVAC Renovation 2014 JCI Metasys Process Loads on CHW Loop; standalone controls 683 kbtu/sf 6

7 Step 1: Transfer of 1. 7

8 Architecture BAS data Facility data Analytics Apps Utility data Production data Time Series base Weather data 1 8

9 Transfer of Assess Existing Sources and Capabilities 1. Collect Information and Documentation 2. Verify Availability and Quality a. Meters integration capabilities and current setup b. BAS data production system vs. trend archive c. Existing Trends vs. Creation of New Trends d. Investigate as Required programming, functional testing 1 9

10 Transfer of $ Web Services Open Protocols RDBMS Automated Export $$ Proprietary Drivers Integration Existing Hardware $$$ Full Integration, New Hardware 1 10

11 Transfer of BAS from Niagara R2 with SiteNet Server 1. obix driver at R2 Jace licensed but trends setup at server 2. obix driver at R2 Server not licensed for obix 3. SQL archive database locally copy historical trend database Final Method: SQL database Replication Copy, Transfer, Import Scripts query for data from desired buildings Zip, transfer (through VPN), import manual process every 1-2 days 1 11

12 Transfer of BAS from JCI Metasys 1. BACnet to Existing AX or Dewberry SoftJace unacceptable data transfer over subnets (BBMD) 2. SQL archive database.. Locally copy historical trend database (> 100 GB) 3. Ongoing SQL database transfer Understand the SQL database structure Scripts query for desired points and time ranges (similar to R2 process) 1 12

13 Transfer of Lessons Learned and Best Practices 1. Fully understand the Client s System Architecture and Network a. Look under the hood b. Do not make assumptions architecture, licenses, etc. 2. Requires a multi-disciplinary approach: Controls, Networking, and Engineering 3. Plan multiple options for data transfer for any project 4. Allow ample time for investigation and trial and error 5. Respect the owner s system limitations and preferences 1 13

14 Analysis and Notification 2. 14

15 Analytics Supports Monitoring-Based Commissioning Existing Cx versus MBCx Similarities: Apply engineering and systems knowledge to provide recommendations for system operation Differences: Analytics applied to a richer data set Analytics support on-going testing and verification; corollary to repeating functional testing every day Analytics are limited to recorded data points and granularity available through integrated system 2 15

16 Analytics Applied Case Study 1. Controllability AHU supply temperature, VAV airflow, CHW / HW plant temperature, hydronic / airside DP) 2. Sequencing economizers, simultaneous heating and cooling, equipment following occupancy schedules 3. Equipment Failures or Malfunction valve/damper leak-by, coil not receiving CHW/HW, fan/pump capacity, VAV cooling capacity, reheat capacity, sensor failures 4. System Overrides fan/pump speed in hand, no temperature setbacks 5. Opportunities for Improvements reduce unneeded runtime, supply air temp reset, static pressure reset, temperature/airflow setbacks, setpoints vs. design basis 2 16

17 Analytics Example #1: Sequencing Disabled Economizer RAT 74 F OA Temp 54.8 F Program OA Flow into at Analytics: Min Stpt, OA Outside damper Air 26% Temperature < (Supply Air Temp Stpt - 5 ) SAT 55 F AND Chilled Water Valve > 0% CHW Valve 84% 2 17

18 Analytics Ex. #2: Equipment Failures or Malfunction Preheat Valve Leak-by Program into Analytics: Supply Air Temp > (Mixed Air Temp + 5 ) AND Preheat Valve = 0% 2 18

19 Analytics Ex. #3: Opportunities for Improvements Duct Static Pressure Reset Program into Analytics: All VAV Damper Positions < 70% for 30 minutes 2 19

20 Results of Analytics to Notifications Analytics: Tests for Conditions Engineer Review & 2 20

21 Notifications Level of Automation Single person on owner side to own the system Notification Formats Equipment & List of Failures Cx Provider Drafted recommendations Issues Log, Ticket System, Interactivity Integration into work order system 2 21

22 Analytics and Notifications Lessons Learned and Best Practices Analytics: program to be flexible, widely applicable across similar (but not identical) types of equipment Consistent data storage format project-haystack.org Plan for data gaps and anomalies especially when reviewing large historical data set Prioritization of action items avoid information overload Understand how the owner will disseminate information and recommendations 2 22

23 and Verification 3. 23

24 Lessons Learned and Best Practices Prioritize: 80/20 rule Simple changes (scheduling and removing overrides) should be first. Focus on programming changes that can be easily replicated across multiple pieces of equipment Scale of Implementation Communicate changes in the language of the action taker Follow up: Use analytics to verify functionality afterward and communicate back to the O&M team the visible proof Setup diagnostics to alert if issue arises again

25 Savings 4. 25

26 Savings Quantify savings for justification of the investment Spend savings on proactive O&M using direction from MBCx Proactively replace frequently failing components identified through MBCx Invest if refined rules and analytics based on results of the first round of MBCx Adjust O&M program to work more interactively with MBCx 4 26

27 Summary 3 buildings 1600 points 2 BAS Systems 3 Meters 30 Analytics 55 Measures Identified 38 Measures Targeted for Implementation 27

28 Janelle H. Griffin, PE, CCP Project Manager Dewberry