| << last | Directory | next >> |
The database is required to serve several roles within the overall system. The design of the database must allow for the search of the database for specific records, the insertion of records, and the modification of the data stored.
The first role of the database is the cataloging of the physical components of the irrigation's system. During setup each of the physical components will be entered in to the database. The chaining together of the records will allow the system to "see" the layout of the pumps, pipes and valves. The system will then need to access this information to decide how to turn on a specific sprinkler. The system will also make use of this portion of the data base to determine flow rates and capacities.
The database must keep records of the pumps, valves, pipes and sprinklers. For the pumps, we need to store a user identifiable name, capacity, the supply pipe identification, the delivery pipe identification, a map location and the binary address used by the Relay Control. For the valves, we must store a user identifiable name, flow capacity, the supply pipe identification, the delivery pipe identification, a map location and the binary address used by the Relay Control. For the pipes we must store a flow capacity, length, diameter and a map location. For the sprinklers we need to store a user identifiable name, if it is a smart head (can flow be regulated at the head, and does it measure flow), flow capacity, the supply pipe identification, a map location and the binary address used by the Relay Control.
With the information stored about each of the components the system can then "assemble" a path for the water flow from the pump to the sprinkler. This information will then be used to determine which valves need to be turned on to get water out of a specific sprinkler.
The system must be able to store information needed to maintain user defined zones and schedules. The schedule section will keep track of the logical zones defined by the user, and which sprinklers are part of each zone. The database will store the past watering schedules for each zone. The database shall be used by the scheduler to store the future watering schedules.
Schedule information is stored as the turn on and off times for each zone in the system.
The database shall have the ability, through automatically executed scripts to make modifications to the contents of the database. The database will move current schedules to the historical section after the schedule has been delivered. The database will store data given to it from the weather sensors. The data points stored will include temperature, humidity and wind speed. These will become part of the historical record base with daily min. and max. for each of these. It will calculate and store an averaged daily and monthly min. and max. value for temperature, humidity, and wind velocity. The system will only store daily records for a period of two years. Records older then that will become part of the averaged record and be removed from the database to save space. The maximum data retention at any time shall be two years plus the long term averages.
The database shall store and retain data on the amount of water delivered to a zone. These records will be on a daily bases and the system will be able to take this information and calculate weekly and monthly averages. The database shall retain daily records for a period of five years at witch time the data shall be converted into weekly averages and totals to reduce space.
| << last | Directory | next >> |