Afritic Open Farming Standard

User Tools

Site Tools

You are here: Afritic Open Water and Farming Standard (AOWFS) » System Architecture Overview » Farm Controller Layer (Local / Federated)
Trace: • Farm Controller Layer (Local / Federated) • HQ / Federated Controller Layer • Water Towers • Field Controller Layer • Electrical & Power Control Interfaces
architecture:farm_controller:start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision		Previous revision
architecture:farm_controller:start [2026/01/21 20:29] – created bsamuelarchitecture:farm_controller:start [2026/01/21 20:32] (current) – [1. Responsibilities] bsamuel
Line 13: Line 13:
  
   * Aggregate telemetry from Field Controllers:   * Aggregate telemetry from Field Controllers:
-    - Soil moisture sensors +    * Soil moisture sensors 
-    - Tank levels +    * Tank levels 
-    - Flow meters +    * Flow meters 
-    - Power usage +    * Power usage 
-    - Optical monitoring data+    * Optical monitoring data
   * Provide a **local operator interface** for monitoring and configuration.   * Provide a **local operator interface** for monitoring and configuration.
   * Validate all operator requests against Field Controller safety rules.   * Validate all operator requests against Field Controller safety rules.
Line 64: Line 64:
 When multiple controllers modify configurations or schedules: When multiple controllers modify configurations or schedules:
  
-  1. **Timestamp precedence:**  +  - **Timestamp precedence:**  
      * The most recent authorized change takes effect.        * The most recent authorized change takes effect.  
  
-  2. **Operator approval:**  +  - **Operator approval:**  
      * In case of conflicting schedule changes, local farm operators must approve before applying.        * In case of conflicting schedule changes, local farm operators must approve before applying.  
  
-  3. **Field Controller enforcement:**  +  - **Field Controller enforcement:**  
      * Field Controller always vetoes any configuration that violates **safety constraints**.        * Field Controller always vetoes any configuration that violates **safety constraints**.  
  
-  4. **Logging:**  +  - **Logging:**  
      * All conflict events must be logged with timestamps, operator ID, and resolution outcome.      * All conflict events must be logged with timestamps, operator ID, and resolution outcome.
  
Line 96: Line 96:
 ===== 6. Human Interface ===== ===== 6. Human Interface =====
  
-* The Farm Controller **must provide a full local UI**:   +  * The Farm Controller **must provide a full local UI**:   
-  - Monitoring dashboards for all irrigation zones   +    - Monitoring dashboards for all irrigation zones   
-  - Configuration of schedules and thresholds   +    - Configuration of schedules and thresholds   
-  - Alerts and notifications for operators   +    - Alerts and notifications for operators   
-* Operator actions are validated against Field Controller safety rules.   +  * Operator actions are validated against Field Controller safety rules.   
-* The interface supports **manual requests**, but these cannot bypass critical safety decisions.+  * The interface supports **manual requests**, but these cannot bypass critical safety decisions.
  
 --- ---
Line 107: Line 107:
 ===== 7. Implementation Notes ===== ===== 7. Implementation Notes =====
  
-* Hardware: Industrial-grade single-board computers (e.g., NanoPi, Raspberry Pi).   +  * Hardware: Industrial-grade single-board computers (e.g., NanoPi, Raspberry Pi).   
-* Communication protocols: LAN, WiFi, or cellular for synchronization.   +  * Communication protocols: LAN, WiFi, or cellular for synchronization.   
-* Data format: Structured, versioned, and compatible with HQ controller ingestion.   +  * Data format: Structured, versioned, and compatible with HQ controller ingestion.   
-* Security: All communications must be encrypted; operator authentication is required.   +  * Security: All communications must be encrypted; operator authentication is required.   
-* Scalability: Supports multiple Field Controllers per farm; multiple zones; multi-farm federation.+  * Scalability: Supports multiple Field Controllers per farm; multiple zones; multi-farm federation.
  
 --- ---
Line 117: Line 117:
 ===== 8. Compliance Notes ===== ===== 8. Compliance Notes =====
  
-* Any AOFS-compliant Farm Controller **must implement offline operation, federation, logging, and safety validation**.   +  * Any AOFS-compliant Farm Controller **must implement offline operation, federation, logging, and safety validation**.   
-* Failure to preserve Field Controller authority or provide audit logs **invalidates compliance**.   +  * Failure to preserve Field Controller authority or provide audit logs **invalidates compliance**.   
-* Synchronization conflicts must follow the deterministic resolution rules defined above.+  * Synchronization conflicts must follow the deterministic resolution rules defined above.
  
  
architecture/farm_controller/start.1769027381.txt.gz · Last modified: by bsamuel

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki