House Resource Management Software

Basics

• Software to manage the resources of a house in a cyclical closed-loop system.
• Sub-component of the Village Resource Management Software.

In Depth View

House resources are defined as:

• Water
• Food
• Energy

Thus, a House, in the software can be thought of as a generic interface with the following methods:

• getWater()
• getFood()
• getEnergy()

Plant UML Source

@startuml
interface House {
  getWater()
  getFood()
  getEnergy()
}
@enduml

You may have several implementations of this generic House interface to meet the needs of people in different bio-regions.

For example, a mid-western house.

Plant UML Source

@startuml
interface House {
  getWater()
  getFood()
  getEnergy()
}

class MidWesternHouse implements House {
  getWater()
  getFood()
  getEnergy()
}

' Responsible for the collection, storage, and purification of rain-water
class RainWaterHarvester << (M,#FF7700) >> {
  getWater()
}


class AquaponicGreenHouse << (M,#FF7700) >> {
  getFood()
}


class SolarPanelArray << (M,#FF7700) >> {
  getEnery()
}

MidWesternHouse ..> RainWaterHarvester
MidWesternHouse ..-> AquaponicGreenHouse
MidWesternHouse ..> SolarPanelArray
@enduml

TODO: In reality, a house would likely have multiple sources for any one resource. For example, energy may come from solar, wind, and bio-gas digestion. The above diagrams don't account for this yet. Expand this to waterSources, foodSources, and energySources?

Material Flows

• A house can be defined in terms of I/O, or inputs and outputs.

Inputs

• Inputs are unique to a geographic location or bio-region, and result in resource generation. For example, in the mid-west of the United States, an input to a house may be rain-water . The house would have a rain-water harvesting sub-component that adapts the input of rain-water to the resource of water. Other geographic locations may have different inputs that lead to water resource generation such as ground-water, salt-water, river-water, glacier-water, or spring-water -- and each water input would need a different sub-component to adapt it to a water resource ready for human consumption.
• Is this software for ONLY self sufficient homes, or does it integrate with the Village Resource Management Software as well? Utilities in would use this, if not just rain etc?
• Possible Utilities:
  • Potable/Drinking Water
  • Electricity
  • Fuel Gas (if plumbed)
  • Internet
  • Phone

Outputs

• Again Depends on if closed loop or not
• Possible outputs:
  • Flue Gasses (SHOULD be scrubbbed to near pure h20+co2)
  • Vent Gas Out (Mainly Air, perhaps with some small concentrations of "nasties" due to the indoors being more concentrated etc)
  • Possibly Slag and/or Anerobic Digestate Solids
  • Potentially small amounts of household hazerdous waste, or non-recyclables (at least what can't be done home-scale)

Principles

See Village Resource Management Software#Principles.

Internal Links

• IOT