-
Notifications
You must be signed in to change notification settings - Fork 22
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 SimpleImpactAnalysis and CostCategory to PackageOfMeasures #205
Conversation
> f. Estimated level (high, medium, low) of return on investment (ROI) | ||
> g. Priority (high, medium, low) | ||
|
||
Additionally, Standard 211 is explicit in discriminating the "Low-Cost and No-Cost" recommendations (section 6.1.5) from the "Capital" recommendations (section 6.1.6), so it might not be a bad idea to add a category to specify this. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it can be argued that this discrimination is unnecessary/redundant because we apready specify the estimated cost (high, medium, low). Something to consider.
This is a breaking change, but it should be feasible to implement in Audit Template. Audit Template's current usage profile for the
All appear to be moved by this PR to the new |
Waiting to fully finish 211 <> BuildingSync mapping before making final decisions about the proposal. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes look good, thanks.
No description provided.