search

kbenne / cbecc

Automatically exported from code.google.com/p/cbecc
0 stars 0 forks source link

Lighting System - New vs. Existing #831

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Luke,

When Compliance Type is changed from "New Complete" to "Existing Altered", all 
lighting systems in all spaces remain as Status = "New".

Users in the training classes felt that this was confusing since all other 
envelope and mechanical components were changed to existing but they had to 
manually go through and change the value at the space or lighting system from 
"New" to "Existing".

Is this something you can change?

Noah

Original issue reported on code.google.com by ncz...@archenergy.com on 23 Oct 2014 at 6:08

GoogleCodeExporter commented 9 years ago 
This is something that can be changed, and I am open to team/user feedback on 
how it should be handled.  The logic I used to arrive at the current 
functionality is as follows:

For "Existing Altered" compliance, lighting can either be New, Altered or 
Existing.  Of the three possibilities, the baseline is most stringent for the 
New case - in the other two cases, proposed lighting gets passed through to the 
baseline model.  My approach has been to always default to the most stringent 
case, such that if users miss, ignore or otherwise leave defaults alone, they 
do not recieve a less stringent baseline.

Let me know how the team prefers to move forward.

Original comment by lu...@360-analytics.com on 30 Oct 2014 at 12:32