-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add "Energy Performance Score" to EnergyScore/ScoreType #39
Comments
This brings up an interesting issue re: building in Program, Utility, or My question is if we should we strive to avoid codifying Program, Utility, That said, there's an argument to be made that RESNET HERS and the DOE Home If the working group generally isn't concerned about this, this'll be the Thanks, On Fri, Oct 30, 2015 at 7:55 AM Brandon Gallagher notifications@github.com
|
Kevin, that’s a good point. I agree with you about the dangers of supporting the specific branding in HPXML. I think it would probably be better to not have any enumerated ScoreTypes. But if we are going to keep HERS and HES, then we should support more. Maybe we could make the ScoreType just a string rather than an enumerated list, and leave it up to each score provider to make it clear how their particular score should be expressed in HPXML. That way there could be consistency in the score name, but it wouldn’t be on HPXML to regulate it. FYI… I plan to rebrand all our marketing materials with “Kevin's Awesome Better Than The Rest Score”. It has a nice ring to it. -brandon From: Kevin Woley [mailto:notifications@github.com] This brings up an interesting issue re: building in Program, Utility, or My question is if we should we strive to avoid codifying Program, Utility, That said, there's an argument to be made that RESNET HERS and the DOE Home If the working group generally isn't concerned about this, this'll be the Thanks, On Fri, Oct 30, 2015 at 7:55 AM Brandon Gallagher <notifications@github.com mailto:notifications@github.com >
— |
Changing the nature of the existing element to a string will require On Mon, Nov 2, 2015 at 10:52 AM, Brandon Gallagher <notifications@github.com
|
I would suggest a middle ground here. Supporting a nationally branded score like HES is OK. But having to support state or regional specific scores may be more problematic from a maintenance point of view. It may be that the WG--5 votes on the inclusion of a branded score based on a set of criteria we develop. For state or regional specific scores we should create generic elements to accommodate these for now. Sent from Outlookhttp://aka.ms/Ox5hz3 On Mon, Nov 2, 2015 at 8:15 AM -0800, "GamalielL" <notifications@github.commailto:notifications@github.com> wrote: Changing the nature of the existing element to a string will require On Mon, Nov 2, 2015 at 10:52 AM, Brandon Gallagher <notifications@github.com
Reply to this email directly or view it on GitHubhttps://github.com//issues/39#issuecomment-153070106. |
@GamalielL 's suggestion might be a nice way to achieve that middle ground that @juliecaracino is talking about. Score types that get approved by WG-5 become enumerations listed in the standard. Those that don't, can use the "Other" enumeration and identify themselves in an (Optional) text field. Thank you all for the discussion here! |
This seems like a reasonable compromise. For the record, we already have an "other" enumeration for score type. It would just be a matter of adding the additional text description field. I also think we should have a date field to go with the score. I can't remember if I added that as another issue or not. |
I definitely agree with the date. -brandon |
The //BuildingSummary/BuildingConstruction/EnergyScore/ScoreType element has enumerations for different standard energy scores. Currently there's just HERS and Home Energy Score. I'd like to add one for "Energy Performance Score".
For convenience, I'd like to just add it as "Energy Performance Score".
However, the "Energy Performance Score" is being implemented slightly differently in different places. For example, the Energy Trust of Oregon uses one that presents a slightly adjusted score in MMBTU. Earth Advantage typically presents our score in kWhe. Some other programs want to present the score in MMBTU also. So we could add enumerations of EPS for kWhe and MMBTU if we want, but I'd say we don't need that complexity yet.
The text was updated successfully, but these errors were encountered: