Skip to content

Domestic Water Heater class #777

Description

@jahrling

I'm looking on where to place Domestic_Water_Heater, and it looks like it should be a subclassof Water_Heater. This is related to #215

Also think it needs some subclasses:

brick:Domestic_Water_Heater
├── brick:Storage_Water_Heater
│ ├── brick:Gas_Storage_Water_Heater
│ │ ├── brick:Atmospheric_Gas_Water_Heater
│ │ └── brick:Power_Vent_Gas_Water_Heater
│ ├── brick:Electric_Storage_Water_Heater
│ ├── brick:Heat_Pump_Water_Heater
│ └── brick:Solar_Water_Heater

├── brick:Tankless_Water_Heater (also: instantaneous / on-demand)
│ ├── brick:Gas_Tankless_Water_Heater
│ └── brick:Electric_Tankless_Water_Heater

├── brick:Indirect_Water_Heater (uses a hydronic boiler as heat source)

└── brick:Semi_Instantaneous_Water_Heater (small buffer storage + instantaneous coil)

Couple Q's:
Q1. brick:Boiler overlap: Should brick:Indirect_Water_Heater have a brick:isHeatedBy relationship pointing to a brick:Boiler? Or is that a relationship to be defined, not a subclass distinction?

Q2. Condensing vs. non-condensing: For gas heaters, thermal efficiency (condensing ≥ 90% AFUE) matters for controls modeling and energy simulation. Should this be a subclass or a property?

Q3. Commercial vs. residential: ASPE distinguishes "commercial water heaters" (>75,000 BTU/hr input) from residential, and DOE recognizes 200,000 BTU/hr as the threshold. Is this a subclass distinction, a capacity property, or out of scope for Brick? I'm thinking that it should be left out for now.

Q4. brick:Storage_Tank relationship: There is already a brick:Storage_Tank class. Should brick:Storage_Water_Heater be defined as a brick:Water_Heater that brick:hasPart a brick:Storage_Tank? Or is the combined appliance a distinct class? Also, sometimes these tanks (especially in heat pump applications) can have a small heater inside to overcome the minor loads in a building.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions