Differences

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

--- sensors:start [2026/01/21 22:01] – [1. Sensor Categories] bsamuel
+++ sensors:start [2026/01/22 22:07] (current) – [5. Water / Water Energy Monitoring] bsamuel
@@ Line 1: / Line 1: @@
 ====== Measuring, Monitoring & Documentation Systems ======
-The **Sensors Layer** defines all devices and measurement systems used by AOFS controllers to monitor irrigation, energy usage, water distribution, and environmental conditions.
+The **Sensors Layer** defines all devices and documentation systems used by AOFS controllers to ensure **safe operation, authoritative control, and auditable farm management**.
 All AOFS-compliant deployments **must implement the sensors and documentation systems specified here**.
-===== 1. Sensor Categories =====
+===== 1. Sensor Layer Scope & Authority =====
-AOFS uses six main sensor categories:
+AOFS sensors are classified by **operational authority**, not by technology type.
-  * **Soil Monitoring Sensors**
+Sensor inputs fall into four functional roles:
-  * **Weather Monitoring Sensors**
-  * **Water Monitoring Sensors**
-  * **Power / Energy Sensors**
-  * **Optical / Camera Monitoring Systems**
-  * **Human Input / External Event Logging**
-**Notes:**
+  * **Safety enforcement** (prevent damage or loss)
-  * “Human Input” refers to events or actions manually logged by farm staff, such as fertilizer application, pruning, or other field activities.
+  * **Authoritative control inputs** (drive irrigation decisions)
-  * AOFS treats these logs as **first-class data**, integrated with automated sensor measurements for analytics and experimental comparisons.
+  * **Documentation & audit**
+  * **Optimization & research**
----
+AOFS controllers **must never depend on remote systems** to interpret or validate sensor data.
-===== 2. Soil Monitoring Sensors =====
-**Purpose:** Measure soil conditions to optimize irrigation schedules.
+===== 2. Critical Safety & Protection Sensors =====
-**Required Measurements:**
+**Purpose:** Prevent equipment damage, flooding, dry-run pumps, and unsafe operating states.
-  * Soil moisture (volumetric water content) per zone
-  * Soil temperature (optional but recommended)
-  * Electrical conductivity (optional; for salinity monitoring)
-**Placement Guidelines:**
+**Mandatory Measurements:**
-  * At least one sensor per irrigation zone
+  * Tank levels: LOW and FULL float switches
-    * Multiple sensors for large or heterogeneous fields
+  * Flow meters on main and zoned pipelines
-  * Sensors should be placed at root depth appropriate to the crop type
+  * Pressure sensors on pumps and main distribution lines
+  * Rainfall measurement for irrigation lockout
-**Data Collection:**
+**Safety Requirements:**
-  * Sample at a frequency suitable for crop needs (typically 15–60 min)
+  * These sensors **must directly enforce Field Controller fail-safes**
-  * Data logged locally in Field Controller and synced with Farm/HQ controllers
+  * Operation must be fully local and offline
+  * Loss or invalid data from these sensors must trigger safe shutdown or degraded mode
-**Calibration & Maintenance:**
-  * Sensors must be calibrated according to manufacturer recommendations
-  * Regular inspection to prevent soil compaction or damage
----
+===== 3. Primary Agronomic Control Sensors =====
-===== 3. Weather Monitoring Sensors =====
+==== Soil Monitoring Sensors ====
-**Purpose:** Monitor on-site weather conditions to inform irrigation decisions and safety lockouts.
+**Purpose:** Provide authoritative inputs for irrigation scheduling.
 **Required Measurements:**
-  * Rainfall (e.g., tipping bucket rain gauge)
+  * Soil moisture (volumetric water content) per irrigation zone
-  * Ambient temperature
-  * Relative humidity
+**Optional but Recommended:**
-  * Wind speed (optional but recommended)
+  * Soil temperature
-  * Solar radiation / light intensity (optional)
+  * Electrical conductivity (salinity)
 **Placement Guidelines:**
-  * Rain gauges placed in open areas, away from obstructions
+  * At least one sensor per irrigation zone
-  * Temperature and humidity sensors shielded from direct sunlight and precipitation
+  * Additional sensors for heterogeneous fields
-  * Wind sensors mounted at standard height for consistent readings
+  * Placement at crop-appropriate root depth
-**Data Collection:**
+==== Weather Monitoring Sensors ====
-  * Sample at frequency sufficient for crop and irrigation needs (typically 10–30 min)
-  * Logs sent to Field Controller for local decision-making and later synced with Farm/HQ controllers
-**Integration with AOFS:**
+**Purpose:** Modify irrigation behavior and enforce environmental lockouts.
-  * Rainfall triggers **irrigation suspension / rain lockout**
-  * Temperature and humidity can refine irrigation thresholds and scheduling
-  * Optional predictive analytics using solar radiation and wind
-**Calibration & Maintenance:**
+**Required Measurements:**
-  * Regular inspection and cleaning of rain gauges
+  * Rainfall
-  * Sensors must be calibrated according to manufacturer specifications
+  * Ambient temperature
-  * Logs of calibration and maintenance events must be maintained
+  * Relative humidity
----
+**Optional Measurements:**
+  * Wind speed
+  * Solar radiation / light intensity
-===== 4. Water Monitoring Sensors =====
+**Integration with AOFS:**
+  * Rainfall triggers irrigation suspension
+  * Weather data refines thresholds and scheduling
-**Purpose:** Ensure safe and efficient water delivery.
+===== 4. Power / Energy Monitoring =====
+**Purpose:** Protect electrical systems and support energy-aware operation.
 **Required Measurements:**
-  * Tank levels: FULL and LOW float switches
+  * Pump power consumption
-  * Flow meters on main and zoned pipelines
+  * Valve power consumption
-  * Pressure sensors for distribution lines
-  * Optional: rain gauges (redundant, for additional verification)
-**Placement Guidelines:**
+**Optional Measurements:**
-  * Tank sensors at critical fill/drain points
+  * Battery voltage and current
-  * Flow meters before distribution manifolds
+  * Solar panel output
-  * Pressure sensors after pumps and at main lines
-**Safety Requirements:**
+**Integration:**
-  * Water sensors must enforce Field Controller fail-safes (pump cutoff, overflow prevention)
+  * Low-voltage or overload conditions must trigger fail-safe behavior
-  * Must function independently of network connection
+  * Energy data may inform event prioritization and anomaly detection
----
+==== Grid Power Monitoring & Predictive Use ====
-===== 5. Power / Energy Sensors =====
+**Purpose:** Enable AOFS to safely use intermittent grid power and optimize energy costs.
-**Purpose:** Monitor energy consumption and optimize PUE (productive use of electricity).
+**Required Measurements (if grid is available):**
+  * Grid voltage, current, and frequency
+  * Short-term fluctuations and harmonics
+  * Availability signal (on/off)
-**Required Measurements:**
+**Optional Measurements:**
-  * DC battery voltage and current
+  * Historical grid availability patterns
-  * Pump energy consumption
+  * Probabilistic prediction of grid power for upcoming hours
-  * Valve power usage
-  * Optional: solar panel output monitoring
-**Placement Guidelines:**
+**Integration & Control Logic:**
-  * Measure energy at the main DC bus and key loads
+  * AOFS must only allow grid power usage if parameters are within safe thresholds
-  * Optional per-zone energy monitoring for detailed efficiency analysis
+  * Automatic relays and actuators must cut off grid supply immediately on overvoltage, under-voltage, or unsafe frequency
+  * Predictive patterns can inform decisions, e.g., delaying high-load pump operations until grid is likely available
+  * All local safety thresholds remain authoritative and override probabilistic logic
-**Integration:**
+===== 5. Water / Water Energy Monitoring =====
-  * Data feeds into Field Controller for fail-safe shutdowns on low voltage
-  * Logged for auditing and analytics
----
+**Purpose:** Monitor and optimize water supply sources, including grid water, local wells, and storage tanks.
-===== 6. Optical / Camera Monitoring Systems =====
+**Required Measurements:**
+  * Tank LOW and FULL levels
+  * Flow rate in main and zoned pipelines
+  * Flow rate and pressure of grid water supply (if available)
+  * Availability signal for grid water (on/off)
-**Purpose:** Supplement sensor data with visual field observations. Cameras are used primarily for **documentation**, not for automated decision-making. Only **still images** are part of AOFS; full video surveillance is outside the standard and can be implemented separately. Images are intended to be reviewed by HQ or Farm staff.
+**Optional Measurements:**
+  * Historical grid water supply patterns
+  * Probability of grid water availability in next hours or days
+  * Water quality indicators (salinity, turbidity)
-**Use Cases:**
+**Integration & Control Logic:**
-  * Crop growth monitoring
+  * AOFS may delay pumping from wells if probability of grid water availability is high
-  * Pest or disease detection (optional, non-critical for irrigation)
+  * Partial tank fill strategies: maintain mandatory minimum levels locally, avoid overfilling if grid water is likely
-  * Soil surface moisture and coverage assessment
+  * Safety thresholds for tank levels must always be enforced, independent of probabilistic logic
+  * Logging of decisions, sensor readings, and probabilities is required for learning and optimization
-**Guidance on Operational Schedule (example only):**
+===== 6. Human Input / External Event Logging =====
-  * Cameras may capture images at key times, e.g.:
-    * Daily at a consistent time (e.g., noon)
-    * Before and after irrigation events
-  * AOFS-compliant implementations **must allow configurable capture schedules**; exact timing is left to farm operators.
-**Requirements:**
+**Purpose:** Capture critical farm activities not measurable by sensors.
-  * Cameras must be oriented for optimal coverage of zones
-  * Images must be **timestamped and logged**
-  * Data should integrate with Field Controller for storage and review
-  * No mandatory AI analysis; **optional AI-based image analysis interfaces** may be implemented
-  * All AI processing must not interfere with manual review or core logging functions
-**Data Logging & Access:**
+AOFS treats human input as **first-class data**, equal to automated sensor measurements.
-  * All images must be stored locally on the Field Controller and synced to Farm/HQ controllers
-  * Metadata must include timestamp, irrigation event reference (if applicable), and camera ID
-===== 7. Data Logging & Documentation =====
+**Examples of Loggable Events:**
+  * Fertilizer application
+  * Manual irrigation or drainage
+  * Pest or disease treatment
+  * Planting, pruning, or harvest activities
-  * All sensor readings **must be logged locally** on the Field Controller
+**Requirements:**
-  * Logs include timestamp, sensor ID, measured value, and status/quality flags
+  * All events must be timestamped
-  * Data must be synced with Farm Controller for aggregation and with HQ Controller for analytics
+  * Events must be linked to a field or irrigation zone
-  * Field workers may document crop growth, harvest outcomes, and environmental observations via **Field Survey Interfaces**, complementing automated measurements
+  * Operator identity must be recorded
+  * Full audit trail for edits or deletions is required
----
+===== 7. Optical / Camera Documentation Systems =====
-===== 8. Calibration & Maintenance =====
+**Purpose:** Provide visual documentation for review, auditing, and optional analysis.
-  * All sensors **must be regularly calibrated** according to manufacturer specifications
+**AOFS Scope:**
-  * Field inspections are required to prevent sensor drift, damage, or misplacement
+  * Still images only
-  * AOFS-compliant deployments **must maintain logs of calibration and maintenance events**
+  * No video streaming requirements
----
+**Use Cases:**
+  * Crop development tracking
+  * Soil surface condition documentation
+  * Pest or disease observation
-===== 9. Compliance Notes =====
+**Requirements:**
+  * Images must be timestamped
+  * Camera ID and zone reference required
+  * Images stored locally on the Field Controller
+  * Optional synchronization with Farm and HQ Controllers
-  * All AOFS deployments **must implement at minimum**:
+AI-based image analysis is **explicitly optional** and must not interfere with core logging or manual review.
-    * Soil moisture per irrigation zone
-    * Tank LOW/FULL switches
-    * Flow meters and pressure sensors on all irrigation manifolds
-    * Power monitoring for pumps and valves
-    * Rainfall measurement for irrigation lockout
-  * Optional sensors (temperature, conductivity, wind speed, solar radiation, cameras) are recommended for **advanced optimization**, but not mandatory
+===== 8. Data Logging & Synchronization Rules =====
-  * All data must be **timestamped, logged locally, and synchronized** according to federation rules
+  * All sensor readings and human-input events **must be logged locally**
+  * Logs must include:
+    * Timestamp
+    * Source or sensor ID
+    * Measured value or event data
+    * Status or quality flags
+  * Synchronization follows AOFS federation rules
+  * Loss of connectivity must never result in data loss
+  * Grid power and water predictive measurements and decisions must be logged, including:
+    - Probability estimates for predictive logic
+    - Decisions made (pump on/off, fill levels)
+    - Outcome of the decisions for future optimization
----
+===== 9. Calibration & Maintenance =====
-===== 10. External Event Logging =====
+  * All sensors must be calibrated according to manufacturer specifications
+  * AOFS deployments must log:
+    * Calibration events
+    * Maintenance actions
+    * Sensor replacements
+  * Calibration and maintenance logs are auditable and synchronized
-**Purpose:** Allow farm staff to document activities and events that are **not captured by sensors**, enabling data-driven research and experimental comparisons.
+===== 10. Compliance Requirements =====
-**Examples of Loggable Events:**
+Minimum mandatory implementation:
-  * Fertilizer application (type, amount, field/zone, date/time)
-  * Manual irrigation or drainage events
-  * Pest or disease treatments
-  * Planting, pruning, or harvest activities
-  * Any other relevant operational actions
-**Requirements:**
-  * All events **must be timestamped and linked to a field or zone**
-  * Data entered by farm workers should be integrated with Field Controller logs
-  * Event entries should be **editable only by authorized personnel**
-  * Optional tags or categories can be used for easier filtering and analysis
-**Integration with AOFS:**
-  * Logs can be synchronized with Farm and HQ Controllers for analysis and reporting
-  * Combined with automated sensor data, these logs enable **farm-level experiments and optimization studies**
-  * Supports structured comparisons between fields, irrigation regimes, crop varieties, or treatment methods
-**Best Practices:**
+  * Soil moisture sensors per irrigation zone
-  * Encourage consistent data entry formats for reliable analysis
+  * Tank LOW and FULL level sensors
-  * Include guidance for field workers on what to log and how
+  * Flow meters and pressure sensors on irrigation systems
-  * Enable audit trails for any edits or deletions
+  * Power monitoring for pumps and valves
+  * Rainfall measurement for irrigation lockout
+Optional sensors enhance optimization and research but **do not affect baseline compliance**.
 ===== 11. References =====
   * [[architecture:field_controller:start|Field Controller Layer]]
   * [[architecture:farm_controller:start|Farm Controller Layer (Local / Federated)]]
-  * [[hydraulics|Hydraulic & Water Systems]]
+  * [[hydraulics:start|Hydraulic & Water Systems]]
-  * [[electrical|Electrical & Control Interfaces]]
+  * [[electrical:start|Electrical & Control Interfaces]]

Afritic Open Farming Standard

User Tools

Site Tools

Differences

Page Tools