Comment #1Amendment: Proposed Standard Amendment on Software PersistencePage Number: 1Comment Intent: ObjectionComment Type: GeneralComment: As more states move toward using updated energy codes, many rater's find that a substantial portion of their work comes from low income/senior/affordable housing projects, most of which take a year or more to complete. If state or federal funds are commited to the project based upon a projected HERS index calculated from plans and specs before construction begins, changing the REM version midstream will likely cause unnecessary complications and headaches once the project and its REM reports are completed.
As more states move toward using updated energy codes, many rater's find that a substantial portion of their work comes from low income/senior/affordable housing projects, most of which take a year or more to complete. If state or federal funds are commited to the project based upon a projected HERS index calculated from plans and specs before construction begins, changing the REM version midstream will likely cause unnecessary complications and headaches once the project and its REM reports are completed.
Comment #2Amendment: Proposed Standard Amendment on Software PersistencePage Number: 1Comment Intent: ObjectionComment Type: GeneralComment: Most construction projects last well more than 6 months beyond the permit date. The way this reads, it is based upon software release date. Shouldn't it be tied to a fixed date? Say Jan 1? Proposed Change: 103.2.1 Confirmed or Sampled Ratings on homes with a permit date that is on or after the 6 month anniversary of the date stipulated by RESNET to begin using the most recent version (Currently Jan 1, 2017) release of the software must utilize the newly released software 103.2.2 Homes with a permit date before the 6 month anniversary of the date stipulated by RESNET to begin using the most recent version (Currently Jan 1, 2017) release of the software shall be allowed to complete a Confirmed or Sampled Rating based on the previous version of the software that was utilized for the Projected Rating.
Most construction projects last well more than 6 months beyond the permit date. The way this reads, it is based upon software release date. Shouldn't it be tied to a fixed date? Say Jan 1?
103.2.1 Confirmed or Sampled Ratings on homes with a permit date that is on or after the 6 month anniversary of the date stipulated by RESNET to begin using the most recent version (Currently Jan 1, 2017) release of the software must utilize the newly released software
103.2.2 Homes with a permit date before the 6 month anniversary of the date stipulated by RESNET to begin using the most recent version (Currently Jan 1, 2017) release of the software shall be allowed to complete a Confirmed or Sampled Rating based on the previous version of the software that was utilized for the Projected Rating.
Comment #3Amendment: Proposed Standard Amendment on Software PersistencePage Number: 1Paragraph / Figure / Table / Note: 103.2Comment Intent: ObjectionComment Type: TechnicalComment: Software providers often update software version numbers for a wide variety of reasons that do not impinge on the underlying calculations, including improvements to the user interface or other elements of the software like improvements in user input constraints. As worded, this section may lead users to believe that they should not use improved versions of software just because the version number of the software has changed. I do not believe that was the intent of this section of the proposed change. Proposed Change: Modify section 103.2 to read as follows: 103.2 Rating Software Changes. When RESNET accredited software programs release new versions that result in changes to the HERS Index, users of RESNET accredited software, shall be required to transition to the new version based on the following schedule:
Software providers often update software version numbers for a wide variety of reasons that do not impinge on the underlying calculations, including improvements to the user interface or other elements of the software like improvements in user input constraints. As worded, this section may lead users to believe that they should not use improved versions of software just because the version number of the software has changed. I do not believe that was the intent of this section of the proposed change.
Modify section 103.2 to read as follows:
103.2 Rating Software Changes. When RESNET accredited software programs release new versions that result in changes to the HERS Index, users of RESNET accredited software, shall be required to transition to the new version based on the following schedule:
Comment #4Amendment: Proposed Standard Amendment on Software PersistencePage Number: 1Paragraph / Figure / Table / Note: 103.2.1Comment Intent: Not an ObjectionComment Type: EditorialComment: This section uses the term "permit" without specifying what type of permit is being specified. A superior specification would be "building permit." Proposed Change: Modify Section 103.2.1 as follows: 103.2.1 Confirmed or Sampled Ratings on homes with a building permit date that is on or after the 6 month anniversary of the release of the software must utilize the newly released software
This section uses the term "permit" without specifying what type of permit is being specified. A superior specification would be "building permit."
Modify Section 103.2.1 as follows:
103.2.1 Confirmed or Sampled Ratings on homes with a building permit date that is on or after the 6 month anniversary of the release of the software must utilize the newly released software
Comment #5Amendment: Proposed Standard Amendment on Software PersistencePage Number: 1Paragraph / Figure / Table / Note: 103Comment Intent: Not an ObjectionComment Type: TechnicalComment: My initial thought is that the requirements for persistence/software is in the wrong chapter. Chapter 1 is titled National Standards for Quality Assurance Providers. While they must use the correct version this does not seem to make sense for where the overall persistence should be defined. Chapter 3 National Home Energy Rating Technical Standards section 303.3 addresses HERS Rating Tools. It would appear more appropriate to address persistence under this section. Additionally, RESNET policy 024 addresses effective dates of amendments. I'm not sure if you can tie an ANSI/RESNET standard to a RESNET policy but, since it is an amendment to the standards that is driving the change to the software (software bug fixes should not impact persistence), the effective date of the amendment should tie to the persistence so that all parties are working off of the same date. Below I provide my suggested language for persistency in Chapter 3. Lastly, a building permit and the start of construction do not necessarily coincide. In some jurisdictions a permit may be pulled up to a year before construction begins. As the proposed language is written a home with a permit pulled 5 month and 30 days after the anniversary of the software release may not receive its confirmed rating until well beyond a year and a half after that anniversary date. I believe this is too long. Proposed Change: 303.3 HERS Rating Tools 303.3.1 All RESNET-accredited HERS Rating Tools shall prohibit printing of Confirmed and Sampled HERS Ratings until such rating has been registered with the National RESNET Registry and a unique registration identification has been assigned. Said registration identification shall be prominently displayed on all printed HERS Rating reports. 303.3.2 For the purposes of conducting Home Energy Ratings, as defined in these Standards, all users shall be required to use the most current version of one of the RESNET accredited rating software programs contained in the “National Registry of Accredited Rating Software Programs” posted on the RESNET website. 303.3.2.1 Rating Software Changes. When RESNET accredited software programs release new versions in response to amendments to ANSI/RESNET 301 HERS Index calculation standards that affect the calculated results of the home energy rating, users shall be required to transition to the new version based on the following schedule: 303.3.2.1.1 Confirmed or Sampled Ratings on a home with a permit date that is on or after the 6 month anniversary of the amendment effective date (as established by RESNET Policy 024) and/or a confirmation or sampling date (completion of the home) that is on or after the 12 month anniversary of the amendment effective date, must utilize the newly released software. 303.3.2.1.2 Homes with a permit date before the 6 month anniversary of the release of the software shall be allowed to complete a Confirmed or Sampled Rating based on the previously accredited version of the software that was utilized for the Projected Rating. 303.3.2.1.3 The RESNET Board of Directors may stipulate a timeframe other than the 6 month anniversary of the permit date.
My initial thought is that the requirements for persistence/software is in the wrong chapter.
Chapter 1 is titled National Standards for Quality Assurance Providers. While they must use the correct version this does not seem to make sense for where the overall persistence should be defined.
Chapter 3 National Home Energy Rating Technical Standards section 303.3 addresses HERS Rating Tools. It would appear more appropriate to address persistence under this section.
Additionally, RESNET policy 024 addresses effective dates of amendments. I'm not sure if you can tie an ANSI/RESNET standard to a RESNET policy but, since it is an amendment to the standards that is driving the change to the software (software bug fixes should not impact persistence), the effective date of the amendment should tie to the persistence so that all parties are working off of the same date. Below I provide my suggested language for persistency in Chapter 3.
Lastly, a building permit and the start of construction do not necessarily coincide. In some jurisdictions a permit may be pulled up to a year before construction begins. As the proposed language is written a home with a permit pulled 5 month and 30 days after the anniversary of the software release may not receive its confirmed rating until well beyond a year and a half after that anniversary date. I believe this is too long.
303.3 HERS Rating Tools
303.3.1 All RESNET-accredited HERS Rating Tools shall prohibit printing of Confirmed and Sampled HERS Ratings until such rating has been registered with the National RESNET Registry and a unique registration identification has been assigned. Said registration identification shall be prominently displayed on all printed HERS Rating reports.
303.3.2 For the purposes of conducting Home Energy Ratings, as defined in these Standards, all users shall be required to use the most current version of one of the RESNET accredited rating software programs contained in the “National Registry of Accredited Rating Software Programs” posted on the RESNET website.
303.3.2.1 Rating Software Changes. When RESNET accredited software programs release new versions in response to amendments to ANSI/RESNET 301 HERS Index calculation standards that affect the calculated results of the home energy rating, users shall be required to transition to the new version based on the following schedule:
303.3.2.1.1 Confirmed or Sampled Ratings on a home with a permit date that is on or after the 6 month anniversary of the amendment effective date (as established by RESNET Policy 024) and/or a confirmation or sampling date (completion of the home) that is on or after the 12 month anniversary of the amendment effective date, must utilize the newly released software.
303.3.2.1.2 Homes with a permit date before the 6 month anniversary of the release of the software shall be allowed to complete a Confirmed or Sampled Rating based on the previously accredited version of the software that was utilized for the Projected Rating.
303.3.2.1.3 The RESNET Board of Directors may stipulate a timeframe other than the 6 month anniversary of the permit date.
Return to Proposed Standard Amendment on Software Persistence