User Tools
architecture:field_controller:start
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| architecture:field_controller:start [2026/01/21 20:34] – created bsamuel | architecture:field_controller:start [2026/02/22 22:21] (current) – [4. Optional Weather-Aware Control] bsamuel | ||
|---|---|---|---|
| Line 60: | Line 60: | ||
| --- | --- | ||
| - | ===== 4. Authority Rules ===== | + | ===== 4. Optional Weather-Aware Control ===== |
| + | |||
| + | * Field Controllers operate fully offline by default using local sensors, operational logic, and historical data | ||
| + | * 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 | ||
| + | * Controllers can temporarily maintain minimum water levels in tanks, suspend irrigation, or adjust equipment operation to prevent structural damage | ||
| + | * Forecasts may also inform reservoir management, overflow routing, irrigation sequencing, and protective actions for farm structures | ||
| + | * Local wind measurement devices are recommended at every farm to provide **real-time, | ||
| + | * Controllers evaluate wind conditions continuously for all critical infrastructure | ||
| + | * Immediate actions are triggered if an asset is at risk (e.g., tanks, greenhouses, | ||
| + | * Actions may include maintaining minimum ballast, suspending irrigation, adjusting movable structures, or sending operator alerts | ||
| + | * All forecast- and wind-informed actions are **non-normative** and optional; offline/ | ||
| + | * Actions based on wind measurements or forecasts **must never override core safety-critical rules** | ||
| + | * All such preventive actions and alerts are logged for auditability | ||
| + | |||
| + | --- | ||
| + | |||
| + | ===== 5. Authority Rules ===== | ||
| * Field Controller is **fully authoritative** for all safety-critical operations. | * Field Controller is **fully authoritative** for all safety-critical operations. | ||
| Line 68: | Line 85: | ||
| --- | --- | ||
| - | ===== 5. Human Interface ===== | + | ===== 6. Human Interface ===== |
| * Minimal embedded UI for operators: | * Minimal embedded UI for operators: | ||
| Line 79: | Line 96: | ||
| --- | --- | ||
| - | ===== 6. Hardware & Integration ===== | + | ===== 7. Hardware & Integration ===== |
| * Embedded microcontrollers (ESP32, Arduino, or industrial equivalent). | * Embedded microcontrollers (ESP32, Arduino, or industrial equivalent). | ||
| Line 91: | Line 108: | ||
| --- | --- | ||
| - | ===== 7. Compliance Notes ===== | + | ===== 8. Compliance Notes ===== |
| * AOFS compliance **requires each field site to have a Field Controller**. | * AOFS compliance **requires each field site to have a Field Controller**. | ||
| Line 100: | Line 117: | ||
| --- | --- | ||
| - | ===== 8. References ===== | + | ===== 9. References ===== |
| * [[architecture: | * [[architecture: | ||
architecture/field_controller/start.1769027642.txt.gz · Last modified: by bsamuel
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
