Boiler:Fuel, Chiller:Fuel, Furnace:Type?

[GoogleCodeExporter]

What SDD Object:Property(s) are relevant to this issue?
Boiler:Fuel, Chiller:Fuel, CoilHeating:FuelSource

Explanation of addition, revision, or clarification:
the two fuel terms, the list includes "Oil, Electric and NaturalGasBoiler" or 
"Electric, HotWater, Oil, Steam and NaturalGasChiller".  Under FuelSource the 
list includes GasFurnace. NaturalGasBoiler, NaturalGasChiller and GasFurnace 
are not fuels.   

Proposed resolution:
Change the options for all three terms to include NaturalGas.

Please provide any additional information below.

Original issue reported on code.google.com by rhedr...@archenergy.com on 11 Feb 2013 at 8:31

[GoogleCodeExporter]

I think we need to pick a consistent way of defining these specifications.  

I suggest for all objects that use/supply energy, to define them through the 
use of two, 'high level' properties:

2) Type: This is context specific: For boilers, it is HotWater, Steam...  For 
CoilHeating, it is HotWater, Steam, HeatPump, ElectricResistance, Furnace...  
For chillers, it is Centrifugal, Screw, etc...

1) Fuel (or FuelSource, I lean towards FuelSource or FuelType): Oil, 
NaturalGas, Electric, Propane, None (this covers objects like water and steam 
coils).

Not all combinations are valid, but the rules and conditional enumerations can 
be used to manage user data.

What do you all think of this approach? I didn't get the impression you are 
actually proposing to change structure Roger, but thought it was a good 
opportunity to make sure this structure is acceptable and that we are 
consistent across the various objects...

Thoughts?

Original comment by da...@360-analytics.com on 14 Feb 2013 at 1:30

[GoogleCodeExporter]

I agree w/ David - lets standardize these property names and selections across 
all pertinent object types.
I am leaning slightly toward FuelSource, but no strong feelings here.

Original comment by scriswel...@gmail.com on 14 Feb 2013 at 3:30

[GoogleCodeExporter]

I concur.  Let's use FuelSource.  So changes are:
Boiler:Fuel -> Boiler:FuelSource w/ NaturalGas, Oil, Electric as enums
Chiller:Fuel -> Chiller:FuelSource w/ Electric, Steam, HotWater, NaturalGas 
(delete oil)

CoilHeating:FuelSource should have enumerations of: NaturalGas, Electric, 
HotWater, Steam, Oil
CoilHeating:Type should have enumerations of: Furnace, HotWater, Steam, 
HeatPump, Resistance (or ElectricResistance?)

Original comment by rhedr...@archenergy.com on 14 Feb 2013 at 4:51

[GoogleCodeExporter]

I agree, this is a cleaner approach, but then the ACM would have to include the 
conditional enumerations to specify the restrictions on which combinations can 
be entered (for example, there could be a table showing the allowed fuel types 
for each boiler type and chiller type).  If you just have one input, you would 
have a larger list, but then the user wouldn't need to make two selections.

I'll work on making changes to the ACM per the above guidance.

Original comment by JohnJArent on 11 Mar 2013 at 5:27

• Changed state: Discussion

[GoogleCodeExporter]

I was just looking at Roger's list and wondered if it made sense to have 
redundancy in both Type and FuelSource.  For example, for CoilHeating, HotWater 
and Steam are listed for both enumerations.  I had assumed that if the 
component did not use a fuel directly (i.e electricity, furnace, etc), the 
FuelSource property would be undefined/not specified by the user. 

John, I think a matrix that shows the combinations of Type and FuelSource for 
each component would be very informative and clear, and also help identify the 
appropriate enumerations for both.  

Original comment by da...@360-analytics.com on 11 Mar 2013 at 9:05

[GoogleCodeExporter]

I agree, let's avoid the redundancy.  So my list becomes: 
Boiler:Fuel -> Boiler:FuelSource w/ NaturalGas, Oil, Electric as enums
Chiller:Fuel -> Chiller:FuelSource w/ Electric, Steam, HotWater, NaturalGas 
(delete oil)

CoilHeating:FuelSource should have enumerations of: NaturalGas, Oil, (or 
undefined)
CoilHeating:Type should have enumerations of: Furnace, HotWater, Steam, 
HeatPump, Electric

Original comment by rhedr...@archenergy.com on 8 Apr 2013 at 10:46

• Changed state: Resolved

[GoogleCodeExporter]

David, In the master update list, #177, I see you included electric as an 
option for CoilHeating:FuelSource.  If we retain that, then electric would be 
included as both FuelSource and Type.  Is that what we should do?  I personally 
prefer limiting FuelSource to gas and oil, but I'm flexible.  

While we're at it, are there really oil fired furnaces in CA new construction?  
If not, we could delete CoilHeating:FuelSource completely.  If it is a furnace, 
then the fuel is gas.  The Type would describe both terms.    

Original comment by rhedr...@archenergy.com on 8 Apr 2013 at 10:55

• Changed state: Discussion

[GoogleCodeExporter]

The idea here was that all coils (both htg and clg) that use energy directly 
(i.e. furnace, HP, DX etc), the FuelSrc would specify the source energy.  Coils 
that don't use energy directly (i.e. hot water, steam), the FuelSrc is 
undefined.

To eliminate the name redundancy, we could revise the ClgHtg:Type enum to 
"Resistance" rather than reduce the list of FuelSrc enums.

Regarding the Oil enum, I don't know if oil furnaces are common in CA, but I 
think we should include it for proposed reporting/TDV calculation purposes and 
that it may be relevant outside of CA.

Original comment by da...@360-analytics.com on 9 Apr 2013 at 1:14

[GoogleCodeExporter]

OK, so I think we have reached agreement.

Boiler:Fuel -> Boiler:FuelSource w/ NaturalGas, Oil, Electric as enums
Chiller:Fuel -> Chiller:FuelSource w/ Electric, Steam, HotWater, NaturalGas 
(delete oil)

CoilHeating:FuelSource should have enumerations of: NaturalGas, Oil, Electric
CoilHeating:Type should have enumerations of: Furnace, HotWater, Steam, 
HeatPump, Resistance

Original comment by rhedr...@archenergy.com on 9 Apr 2013 at 3:49

• Changed state: Resolved

[GoogleCodeExporter]

Sorry, in my last response I was only focused on the questions regarding 
heating coils....  As they stand, the chiller Type and FuelSrc enums are not 
consistent with the convention proposed in comment #1 and the convention used 
for coils.  Here is a proposed outline of enums for the primary equipment (not 
including water heaters) that I think are consistent with the Type/FuelSrc 
convention:

Boiler:FuelSrc,
NaturalGas
Oil
Electric
None

Boiler:Type,
HotWater
Steam
Resistance

Chiller:FuelSrc,
Electric
NaturalGas
None  (used for Steam, etc)

Chiller:Type,
Centrifugal
Reciprocating
Screw
Scroll
Absorption
HeatPump

Chiller:AbsorptionHeatSource, (NEW)
Direct (this would be used for direct-fired models, FuelSrc = NaturalGas)
Steam
HotWater

Chiller:AbsorptionEffect, (NEW))
Single
Double
Triple

Chiller:HeatRecoveryMethod (NEW)
DoubleBundled
EngineJacket
None (default)
** Need to define additional properties for handling heat recovery

Original comment by da...@360-analytics.com on 9 Apr 2013 at 5:39

[GoogleCodeExporter]

Looks good to me.

Original comment by rhedr...@archenergy.com on 9 Apr 2013 at 5:42

[GoogleCodeExporter]

Original comment by rhedr...@archenergy.com on 17 Sep 2013 at 8:20

• Changed state: DoneVerified