search

impactlab / eemeter

‼️ MOVED TO https://github.com/openeemeter/eemeter - Core computation engine for the Open Energy Efficiency Meter
https://eemeter.readthedocs.io/
MIT License
25 stars 13 forks source link

Create a model that conforms to the ANSI BPI-2400 specification #13

Closed philngo closed 9 years ago

philngo commented 9 years ago

See the specification linked in the docs.

jgagliano commented 9 years ago

Phil

Which section of the std are you referring to. I co-authored it, so i should be able to help you.

philngo commented 9 years ago

Thanks, Jerone! We want the Open EE Meter to be as helpful as possible at any point in the process of calculating savings, so I thought maybe we would start with the following aspects of the standard, which are both very straightforward:

  1. verifying whether or not utility bills meet the requirements for detailed calibration (3.2.2)
  2. verifying that all the detailed (or simplified) model calibration acceptance criteria are met (3.4)

From there, although we aren't planning to create any sort of complex engineering models in the near future, I do think that in order to get as close as possible to completing a system that spits out a final qualified savings estimate, we would be interested developing out connections to third party software which can use its calibrated pre-retrofit and post-retrofit models to produce savings estimates.

One way or another, implementing as much of the standard as we can will help inform the process of calculating portfolio-level savings as accurately as possible even when such detailed information is widely unavailable.

jgagliano commented 9 years ago

Ok, so it sounds like you understand what you need to do and the algorithms are spelled out in the standard. If you need interpretation of the standard or have questions, let me know.

Jerone

From: Phil Ngo [mailto:notifications@github.com] Sent: Thursday, March 05, 2015 10:30 PM To: impactlab/eemeter Cc: Jerone Gagliano Subject: Re: [eemeter] Create a model that conforms to the ANSI BPI-2400 specification (#13)

Thanks, Jerone! We want the Open EE Meter to be as helpful as possible at any point in the process of calculating savings, so I thought maybe we would start with the following aspects of the standard, which are both very straightforward:

  1. verifying whether or not utility bills meet the requirements for detailed calibration (3.2.2)
  2. verifying that all the detailed (or simplified) model calibration acceptance criteria are met (3.4)

From there, although we aren't planning to create any sort of complex engineering models in the near future, I do think that in order to get as close as possible to completing a system that spits out a final qualified savings estimate, we would be interested developing out connections to third party software which can use its calibrated pre-retrofit and post-retrofit models to produce savings estimates.

One way or another, implementing as much of the standard as we can will help inform the process of calculating portfolio-level savings as accurately as possible even when such detailed information is widely unavailable.

— Reply to this email directly or view it on GitHubhttps://github.com/impactlab/eemeter/issues/13#issuecomment-77500869.

IMPORTANT NOTICE: This email message is intended to be received only by persons entitled to receive the confidential information it may contain. Email messages to clients of Performance Systems Development may contain information that is confidential and legally privileged. Please do not read, copy, forward, or store this message unless you are an intended recipient of it. If you have received this message in error, please forward it to the sender and delete it completely from your computer system.

philngo commented 9 years ago

0f29cce76199c5165591239e8b6163473a0759c6 is a start at implementing section 3.2.2 - verifying quality and completeness utility bill data in conjunction with heating degree days and cooling degree days for electricity and natural gas.

philngo commented 9 years ago

756476d709f7937599adbd0afca3eb29fa549b03 completes an implementation of section 3.2.2. Closing this issue and opening a new one specifically for section 3.4 (#63). Plan: open new issues for specific sections of the BPI2400 spec.