Water Heaters and CBECC Interface

[GoogleCodeExporter]

Issue related to  __user interface / __defaulting / __energy simulation

-Scott

We need to be able to assign/select a WaterHeater:Name (WtrHtr:Name) at the 
Envelope/SpaceData level within the CBECC interface.  Would it be possible to 
add a drop-down list within the SpaceData interface, just to the right of the 
HotWaterSchRef that shows all of the current WtrHtr:Name(s) that exist in the 
Mechanical Tab?  Ideally this drop-down list at the Space Data level would 
update as Water Heaters were created under the Mechanical Tab.
It would be great to get this by Monday afternoon so we can include this in the 
Water Heater XML we are trying to send to NREL.

Thanks !
-Noah

What version of CBECC-NRes are you using? On what operating system?

Please provide any additional information below.

Original issue reported on code.google.com by ncz...@archenergy.com on 18 Apr 2013 at 6:19

[GoogleCodeExporter]

Hi Noah,
Don't you mean a reference to the list of FluidSystem of Type=ServiceHotWater?

Original comment by da...@360-analytics.com on 18 Apr 2013 at 6:37

[GoogleCodeExporter]

Has such a reference property been added to the SDD Space object?  I did not 
scour the issues list or SDD master update spreadsheet, but did not see 
anything along these lines in either the latest SDD spreadsheet or ruleset data 
model.
This is the first step...

Original comment by scriswel...@gmail.com on 18 Apr 2013 at 6:40

[GoogleCodeExporter]

Scott and David

The SDD Term that I will need to add is:

RULE NEW Space:WtrHtrRef
LONGFORM WaterHeaterReference
DATATYPE FluidSys:WtrHtr (i think i just enter WaterHeater for DATATYPE)

Entering this new SDD term is all that I need to do to get this moving?  
Ideally the Users would see the actual WaterHeater:Name(s) (that were created 
in the Mechanical Tab) when they are assigning them to the SpaceData within the 
Envelope Tab.

Let me know if there is more i can do for this issue.
Thanks! Noah

Original comment by ncz...@archenergy.com on 18 Apr 2013 at 6:59

[GoogleCodeExporter]

Hi Scott,

I just added an SDD term to the Master Update List for Issue 206.
Here are the details:

RULE NEW Proj:Bldg:Story:Spc:SHWSysRef
DATATYPE
  FluidSystem
LONGFORM
  SHWSystemReference

Can you add this to the CBECC screen within the:
Envelope Tab 
    Space Data (To the right of the HotWtrHtgRt Schedule Reference)

Thanks!
Noah

Original comment by ncz...@archenergy.com on 18 Apr 2013 at 8:21

[GoogleCodeExporter]

SHW is not in the list of SDD acronyms, which would make the short and long 
form names ServiceHotWtrSysRef / ServiceHotWaterSystemReference.  My assumption 
is that SHW should get ADDED to the list of SDD acronyms, so I have gone ahead 
and added this property to the ruleset data model using your suggested naming.
We need to follow-up w/ others ASAP to make sure there are no objections to 
adding SHW to the acronym list, so that we don't create prototypes that will 
become unusable due to property name switches.

Original comment by scriswel...@gmail.com on 19 Apr 2013 at 2:34

[GoogleCodeExporter]

Adding SHW makes sense to me.

Original comment by da...@360-analytics.com on 19 Apr 2013 at 2:47

[GoogleCodeExporter]

SHW is not in the list of SDD acronyms, which would make the short and long 
form names ServiceHotWtrSysRef / ServiceHotWaterSystemReference.  My assumption 
is that SHW should get ADDED to the list of SDD acronyms, so I have gone ahead 
and added this property to the ruleset data model using your suggested naming.
We need to follow-up w/ others ASAP to make sure there are no objections to 
adding SHW to the acronym list, so that we don't create prototypes that will 
become unusable due to property name switches.

ANOTHER clarification - FluidSys has a Type property that (I assume) should 
dictate compatibility w/ this Space assignment, so that users cannot assign 
FluidSys objects whose Type = ChilledWater.
The question is - what types should be selectable for Space:SHWSysRef?
The FluidSys:Type options are ChilledWater, CondenserWater, HotWater & 
ServiceHotWater.  Chilled & Condenser are definitely out, SHW is in, but what 
about Type = HotWater.  Should users be allowed to assign HotWater FluidSys 
objects to Space:SHWSysRef?
For now, I have restricted the assignment to just FluidSys objects of type 
ServiceHotWater.

AND ... I assume that this property (Space:SHWSysRef) is an "Optional" user 
input and should be passed along to the simulation engine.

Re: UI Control position - I have added the control where you suggest, but am 
not crazy about that location because everything else in that area is defaulted 
from the SpcFuncDefaultsRef object.  This new control is the only thing in that 
portion of the screen that is not defaulted in that manner.
On the other hand - leaving it there keeps the SHW stuff together - tough 
call...
While we are on the topic - I assume that you do NOT want to add this property 
to SpcFuncDefaults and add it to the other Space defaulting in that way.  That 
would require more data model, ruleset & UI mods.

All mods as described above were made and will be checked in later tonight.
Changing owner to Noah to follow-up on outstanding questions here.

Original comment by scriswel...@gmail.com on 19 Apr 2013 at 3:26

[GoogleCodeExporter]

Original comment by scriswel...@gmail.com on 19 Apr 2013 at 3:30

• Changed state: Discussion

[GoogleCodeExporter]

Based on the conversation that David and I had last week we should add SHW to 
the list of SDD acronyms (Scott has taken care of this).

Keeping only the FluidSystem:Type:ServiceHotWater as a selection is the correct 
choice for now.  I will post an issue if Roger, David and I see a need to add 
additional types.

As you stated Scott, Space:SHWSysRef should be "Optional" to be passed to the 
simulation engine.

Keeping all of the Water Heater information together is important, but having 
all of it in that specific location is not imperative.

We do not need to add the SHW stuff to the SpcFuncDefaults, at least for now.  
I will look into this and post a new issue if this needs to change.

Original comment by ncz...@archenergy.com on 22 Apr 2013 at 4:51

[GoogleCodeExporter]

Original comment by ncz...@archenergy.com on 21 Oct 2013 at 4:17

• Changed state: DoneVerified