1 / 12

BEDES-AUC Status Update

BEDES-AUC Status Update. Bob Hendron and Michael Deru BEDES TWG Meeting February 25, 2014. BEDES-AUC Project Overview. Objectives Improve consistency of audit data collection and reporting Provide a common language for data communication, analysis, and aggregation

joella
Télécharger la présentation

BEDES-AUC Status Update

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. BEDES-AUCStatus Update Bob Hendron and Michael Deru BEDESTWG Meeting February 25, 2014

  2. BEDES-AUC Project Overview • Objectives • Improve consistency of audit data collection and reporting • Provide a common language for data communication, analysis, and aggregation • Improve the quality and lower the long-term cost of audits • Strategies • Leverage existing databases, data forms, and data schemas • Integrate with the overall BEDES structure • Consider relationship of audit fields to other use cases • Obtain input from stakeholders • Technical Advisory Group (TAG) • Peer reviewers • Pilot project partners

  3. Project Timeline

  4. Overall TAG Mission and Schedule • Mission • Collaborate with NREL to develop a viable first draft of the BEDES-AUC • Advise NREL throughout development, piloting, and deployment of the BEDES-AUC • Schedule

  5. TAG Process • Electronic Review • Google Spreadsheet allows comments and edits from multiple reviewers in real time • Replies to comments indicate agreement or disagreement • If nobody expresses opposition to a comment, NREL makes the appropriate change without further discussion • Conference Calls • TAG reviews and comments on the relevant sections of the “strawman” during the week leading up to the call • Issues of significant controversy identified in “Comments” are discussed first, followed by an open forum

  6. Data Categories/Organization • BEDES Category • New Category

  7. Draft BEDES-AUC Data Fields • Launch Google Drive https://docs.google.com/spreadsheet/ccc?key=0AtHYfZ-jQvJ7dGJwSlo0VnBQcTRYaHV6NmVneVU3ekE&usp=drive_web#gid=0

  8. Overall BEDES-AUC Hierarchy (Draft) Audit Site Commercial Facility Customer Measure Report Description Baseline Energy Use Activity Area Owner Contact Info Measure Energy Savings Baseline Water Use System Property Manager Contact Info Measure Cost Data EEM Package Cost/Energy Savings See “System Hierarchy”

  9. BEDES-AUC Systems Hierarchy (Draft) System Location Year Installed Global Elements Fuel Type Remaining Life Miscellaneous HVAC Equipment Envelope Air Distribution Walls Lighting IT Systems Process Loads Central Heating Domestic Hot Water Roof/ Ceiling Conveyance Cooking Local Heating Fenestration Storage/ Generation Refrigeration Central Cooling Foundation Pool Dishwashing Local Cooling Other Water Fixtures Laundry Other HVAC Pumps/ Fans/ Motors

  10. BEDES-AUC Hot Water System Hierarchy (Draft)

  11. BEDES-AUC Measures Hierarchy (Draft)

  12. High Level Issues Deferred to BEDESTWG • What level of “implied” hierarchy should be used for data fields? (e.g. boiler pump efficiency, pump efficiency, or efficiency) • Should we require specific units, or allow alternative units to minimize errors? • What metadata fields are necessary for QA? (e.g. measured, default, estimated, nameplate) • Should calculated fields be included? If so, do we need to include the equations so they are calculated the same way by all users? • Should we establish constraints on numerical data (maximum/minimum, significant digits, etc.)

More Related