This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| architecture:field_controller:start [2026/02/22 22:15] – bsamuel | architecture:field_controller:start [2026/02/22 22:21] (current) – [4. Optional Weather-Aware Control] bsamuel | ||
|---|---|---|---|
| Line 65: | Line 65: | ||
| * When internet connectivity is available, controllers may fetch local or global weather forecasts | * When internet connectivity is available, controllers may fetch local or global weather forecasts | ||
| * High wind, storm, or extreme precipitation warnings trigger automated alerts to operators | * High wind, storm, or extreme precipitation warnings trigger automated alerts to operators | ||
| - | * Controller | + | * Controllers |
| - | * Irrigation schedules or pump operation may be suspended or adjusted proactively based on forecast data | + | * Forecasts may also inform reservoir management, overflow routing, irrigation sequencing, and protective actions for farm structures |
| - | * Forecasts may also inform reservoir management, overflow routing, | + | * Local wind measurement devices are recommended at every farm to provide **real-time, |
| - | * All forecast-based actions are **non-normative** and optional; offline/ | + | * Controllers evaluate wind conditions continuously for all critical infrastructure |
| - | * Forecast-informed actions must **never override core safety-critical rules** | + | * Immediate actions are triggered if an asset is at risk (e.g., tanks, greenhouses, |
| - | * All forecast-based adjustments | + | * Actions may include maintaining minimum ballast, suspending irrigation, adjusting movable structures, or sending operator alerts |
| + | * All forecast- | ||
| + | * Actions based on wind measurements or forecasts | ||
| + | * All such preventive actions and alerts | ||
| --- | --- | ||