This is an old revision of the document!
See overview: System Architecture Overview
The HQ / Federated Controller Layer provides multi-farm oversight, analytics, and management. It sits above Farm Controllers in the AOFS hierarchy, enabling federation, global reporting, and configuration distribution while never bypassing Field Controller safety rules.
The HQ Controller:
—
1. Telemetry Aggregation
2. Analytics & Reporting
3. Configuration Distribution
4. Audit Logging
—
The HQ Controller operates as part of AOFS’ decentralized federation network:
—
* Safety authority:
* Supervisory authority:
* Conflict resolution:
—
* Web-based dashboards for multi-farm monitoring. * Reporting modules for energy, water efficiency, and crop outcomes. * Interfaces for authorized managers to submit configuration updates. * Visualization of alerts, events, and historical performance. * No interface may bypass Field Controller safety rules.
—
* HQ Controller may be offline; farm autonomy is never compromised. * 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.
—
* Hardware: industrial servers, cloud instances, or on-prem appliances. * Communication protocols: secure LAN, WiFi, cellular, or VPN tunnels. * Data storage: structured, versioned, and secure for multi-farm ingestion. * Security: encryption for all communications; multi-factor authentication for operators. * Scalability: supports hundreds of farms, multiple Farm Controllers per farm.
—
* HQ Controller must never override Field Controller safety rules. * All multi-farm pushes, pulls, and operator actions must be logged. * Deterministic conflict resolution must be implemented for configuration and schedule synchronization. * Failure to respect authority hierarchy invalidates AOFS compliance.
—