House Resource Management Software: Difference between revisions
(→Inputs) |
(→Inputs) |
||
| Line 19: | Line 19: | ||
The house would have a rain-water harvesting sub-component that adapts the '''input''' of rain-water to the '''resource''' of 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. | |||
===Outputs=== | ===Outputs=== | ||
Revision as of 01:20, 25 July 2020
Introduction
Software to manage the resources of a house in a cyclical closed-loop system.
Sub-component of the Village Resource Management Software.
House resources are defined as:
- Water
- Food
- Energy
I/O
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.
Outputs
TODO: Define outputs.