Afritic Open Farming Standard

User Tools

Site Tools

You are here: Afritic Open Water and Farming Standard (AOWFS) » System Architecture Overview » HQ / Federated Controller Layer
Trace: • Electrical & Power Control Interfaces • Valves, Pumps & Actuation
architecture:hq_controller:start

Differences

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

Link to this comparison view

architecture:hq_controller:start [2026/01/21 20:35] – created bsamuelarchitecture:hq_controller:start [2026/01/21 20:36] (current) – bsamuel
Line 58: Line 58:
 ===== 4. Authority Rules ===== ===== 4. Authority Rules =====
  
-* **Safety authority:**   +  * **Safety authority:**   
-  - Field Controllers retain full authority for all safety-critical operations.   +    * Field Controllers retain full authority for all safety-critical operations.   
-  - HQ Controller cannot directly actuate pumps, valves, or override irrigation cutoffs.  +    * HQ Controller cannot directly actuate pumps, valves, or override irrigation cutoffs.  
  
-* **Supervisory authority:**   +  * **Supervisory authority:**   
-  - HQ Controller may propose schedules, thresholds, and configurations.   +    * HQ Controller may propose schedules, thresholds, and configurations.   
-  - Farm Controllers apply changes according to local rules and validation.  +    * Farm Controllers apply changes according to local rules and validation.  
  
-* **Conflict resolution:**   +  * **Conflict resolution:**   
-  - Timestamp precedence and operator approval at the farm level.   +    * Timestamp precedence and operator approval at the farm level.   
-  - Any conflicts that violate Field Controller rules are **blocked and logged**.  +    * Any conflicts that violate Field Controller rules are **blocked and logged**.  
  
 --- ---
Line 74: Line 74:
 ===== 5. Human Interface ===== ===== 5. Human Interface =====
  
-* Web-based dashboards for multi-farm monitoring.   +  * Web-based dashboards for multi-farm monitoring.   
-* Reporting modules for energy, water efficiency, and crop outcomes.   +  * Reporting modules for energy, water efficiency, and crop outcomes.   
-* Interfaces for authorized managers to submit configuration updates.   +  * Interfaces for authorized managers to submit configuration updates.   
-* Visualization of alerts, events, and historical performance.   +  * Visualization of alerts, events, and historical performance.   
-* No interface may bypass Field Controller safety rules.  +  * No interface may bypass Field Controller safety rules.  
  
 --- ---
Line 84: Line 84:
 ===== 6. Offline Operation ===== ===== 6. Offline Operation =====
  
-* HQ Controller may be offline; farm autonomy is **never compromised**.   +  * HQ Controller may be offline; farm autonomy is **never compromised**.   
-* Logs and updates queue until connectivity is restored.   +  * Logs and updates queue until connectivity is restored.   
-* HQ can continue analytics and dashboards locally with last synced data, but **cannot control irrigation in real-time** without live connection.+  * HQ can continue analytics and dashboards locally with last synced data, but **cannot control irrigation in real-time** without live connection.
  
 --- ---
Line 92: Line 92:
 ===== 7. Hardware & Integration ===== ===== 7. Hardware & Integration =====
  
-* Hardware: industrial servers, cloud instances, or on-prem appliances.   +  * Hardware: industrial servers, cloud instances, or on-prem appliances.   
-* Communication protocols: secure LAN, WiFi, cellular, or VPN tunnels.   +  * Communication protocols: secure LAN, WiFi, cellular, or VPN tunnels.   
-* Data storage: structured, versioned, and secure for multi-farm ingestion.   +  * Data storage: structured, versioned, and secure for multi-farm ingestion.   
-* Security: encryption for all communications; multi-factor authentication for operators.   +  * Security: encryption for all communications; multi-factor authentication for operators.   
-* Scalability: supports hundreds of farms, multiple Farm Controllers per farm.  +  * Scalability: supports hundreds of farms, multiple Farm Controllers per farm.  
  
 --- ---
Line 102: Line 102:
 ===== 8. Compliance Notes ===== ===== 8. Compliance Notes =====
  
-* HQ Controller **must never override Field Controller safety rules**.   +  * HQ Controller **must never override Field Controller safety rules**.   
-* All multi-farm pushes, pulls, and operator actions must be logged.   +  * All multi-farm pushes, pulls, and operator actions must be logged.   
-* Deterministic conflict resolution must be implemented for configuration and schedule synchronization.   +  * Deterministic conflict resolution must be implemented for configuration and schedule synchronization.   
-* Failure to respect authority hierarchy **invalidates AOFS compliance**.+  * Failure to respect authority hierarchy **invalidates AOFS compliance**.
  
 --- ---
Line 111: Line 111:
 ===== 9. References ===== ===== 9. References =====
  
-* [[architecture:start|System Architecture Overview]]   +  * [[architecture:start|System Architecture Overview]]   
-* [[architecture:farm_controller:start|Farm Controller Layer (Local / Federated)]]   +  * [[architecture:farm_controller:start|Farm Controller Layer (Local / Federated)]]   
-* [[hydraulics|Hydraulic & Water Systems]]   +  * [[hydraulics|Hydraulic & Water Systems]]   
-* [[electrical|Electrical & Control Interfaces]]   +  * [[electrical|Electrical & Control Interfaces]]   
-* [[sensors|Measuring, Monitoring & Documentation Systems]]+  * [[sensors|Measuring, Monitoring & Documentation Systems]]
  
architecture/hq_controller/start.1769027720.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