"
Team:Cornell/project/drylab/functional requirements
From 2012.igem.org
(Difference between revisions)
| Line 60: | Line 60: | ||
<div class="func-req-desc"> | <div class="func-req-desc"> | ||
<h5>Continuous</h5> | <h5>Continuous</h5> | ||
| - | Pollution events can be hard to spot, making | + | Pollution events can be hard to spot, making discrete testing inadequate as well as expensive. Monitoring water quality is a 24 hour job. |
</div> | </div> | ||
</div> | </div> | ||
Revision as of 02:55, 27 October 2012
-
Dry Lab
- How It Works
- Functional Requirements
- Components
- Modeling
- Device Status
- 3D Model
Functional Requirements
Scroll over each icon to find out more about the functional requirements for our device!
Continuous
Pollution events can be hard to spot, making discrete testing inadequate as well as expensive. Monitoring water quality is a 24 hour job.
Field Deployable
Industrial water monitoring is needed in remote and rugged terrain. In order to be applicable in these terrains, our device should be durable, water-proof. Being out in the field also means all food for bacteria and power for electronics must be provided by the device itself.
Remote
To collect data in isolated locations, wireless communication is essential. This requires digital conversion of signals from our bacteria, so that it can be transmitted to the user and accessed online.
Electrical Output
Our device needs to output signal that is practical and intuitive. Electrical signal is easy to sense, process, and convert to digital signal.
Long Term
To monitor water quality in a truly continuous fashion, our device must be able to sustain itself without maintenance for long periods of time. Frequent maintenance is impractical.
