|
|
| Line 3: |
Line 3: |
| = Afritic Open Water Infrastructure Standard (AOWIS) = | | = Afritic Open Water Infrastructure Standard (AOWIS) = |
|
| |
|
| '''Afritic Open Water Infrastructure Standard (AOWIS)''' defines a '''trusted, production-grade architecture for autonomous water and agricultural control and management systems'''. | | '''AOWIS''' defines a '''trusted, production-grade architecture''' for autonomous water and agricultural control and management systems. It supports both '''irrigation and community water infrastructure''', including wells, pumps, storage tanks, water towers, and distribution networks — critical for '''food production, public health, and rural development'''. |
|
| |
|
| AOWIS supports both '''irrigation and community water infrastructure''', including wells, pumps, storage tanks, water towers, and distribution networks. These systems are critical for '''food production, public health, and rural development''', particularly in regions where water infrastructure must operate under difficult conditions.
| | The standard ensures '''safety, scalability, energy efficiency, and reliable operation''', particularly in '''off-grid, weak-grid, and climate-stressed regions'''. By combining '''local autonomy, automation, sensing, and digital supervision''', AOWIS enables '''productive use of electricity (PUE)''' for '''sustainable agriculture and reliable water supply''', while remaining '''offline-first and fail-safe'''. |
|
| |
|
| The standard ensures '''safety, scalability, energy efficiency, and reliable operation''' under real-world environments, especially in '''off-grid, weak-grid, and climate-stressed regions'''.
| | Reliable access to '''water for both agriculture and human consumption''' is fundamental for '''food security, public health, and economic stability'''. AOWIS treats '''water infrastructure and agricultural systems as equal, first-class domains'''. |
| | |
| By combining '''local autonomy, automation, sensing, and digital supervision''', AOWIS enables the '''productive use of electricity (PUE)''' for both '''sustainable agriculture and reliable water supply''', while remaining '''offline-first and fail-safe'''.
| |
| | |
| Reliable access to '''water for both agriculture and human consumption''' is a fundamental prerequisite for '''food security, public health, and economic stability'''. AOWIS therefore treats '''water infrastructure and agricultural systems as equal, first-class system domains'''. | |
| | |
| == Water Infrastructure & Community Supply ==
| |
| | |
| AOWIS is designed not only for '''agricultural irrigation''' but also for '''community water infrastructure in rural areas and small towns''', particularly across Africa and other low-infrastructure environments.
| |
| | |
| In many regions, the '''same physical infrastructure serves both agricultural and community needs'''. A single borehole, pump, or water tower may provide irrigation water during certain periods while supplying '''drinking water and household use''' at other times.
| |
| | |
| AOWIS explicitly supports this '''shared infrastructure model''', enabling safe and reliable operation of:
| |
| | |
| * '''Wells and boreholes'''
| |
| * '''Pumping stations'''
| |
| * '''Water towers and storage tanks'''
| |
| * '''Village distribution systems'''
| |
| * '''Farm irrigation networks'''
| |
| | |
| Local initiatives demonstrate that '''simple water infrastructure — wells, pumps, and storage towers — forms the backbone of rural water supply'''. AOWIS provides a control and monitoring architecture that allows such systems to operate '''reliably, safely, and with minimal technical overhead'''.
| |
| | |
| AOWIS enables:
| |
| | |
| * '''Integration of existing infrastructure:''' Pumps, tanks, water towers, and distribution systems can be directly connected to AOWIS controllers.
| |
| * '''Safe and reliable control:''' Offline-capable automation ensures water distribution continues during power outages or unstable grid conditions.
| |
| * '''Shared infrastructure operation:''' Systems can safely support both irrigation and community supply using the same hardware.
| |
| * '''Scalability:''' From a single well to village-scale systems and small-town water networks.
| |
| * '''Local autonomy:''' Safety-critical functions such as pump protection, overflow prevention, and minimum supply operate independently of internet connectivity.
| |
| * '''Community participation:''' Residents may act as '''active agents''' in monitoring and control by performing measurements, operating valves manually, and participating in structured data logging.
| |
| * '''Resilient operation under constraints:''' Systems remain functional with limited technical support, minimal maintenance capacity, and low-connectivity environments.
| |
| | |
| This approach aligns with AOWIS’s '''offline-first, fail-safe design philosophy''', ensuring that water infrastructure continues to operate '''even under harsh and resource-constrained conditions'''.
| |
| | |
| '''Related Sections:''' [[Hydraulics|Hydraulic & Water Systems]], [[Reference Implementations]]
| |
|
| |
|
| == Key Principles == | | == Key Principles == |
| | * '''Local Autonomy:''' Safety-critical operations occur independently of external connectivity. |
| | * '''Fail-Safe Operation:''' Hardware and software safeguards prevent over- or under-irrigation, flooding, or equipment damage. |
| | * '''Separation of Control and Supervision:''' Field controllers make operational decisions; higher-level controllers supervise and audit. |
| | * '''Scalability & Replicability:''' Applicable from single wells to village-scale and regional systems. |
| | * '''Shared Infrastructure Support:''' Community and agricultural use coexist safely on the same infrastructure. |
| | * '''Human-in-the-Loop:''' Residents and farm personnel act as sensors and actuators, with all actions logged and auditable. |
| | * '''Offline-First Resilience:''' Systems remain functional during power outages, low connectivity, or device failure. |
| | * '''Modular & Extendable:''' Core framework supports additional modules (livestock, greenhouse, poultry, etc.) without compromising safety. |
|
| |
|
| * '''Local Autonomy:''' All safety-critical functions operate independently of external connectivity.
| | == Documentation Structure == |
| * '''Fail-Safe Operation:''' Hardware and software protections prevent flooding or drying out, crop stress, pump damage, and water supply failures.
| |
| * '''Separation of Control and Supervision:''' Decisions affecting safety occur locally; remote systems supervise, configure, and audit.
| |
| * '''Scalability:''' Applicable from smallholder plots and village water systems to large commercial farms and regional water infrastructure.
| |
| | |
| == What AOWIS Is — And What It Is Not == | |
| | |
| AOWIS is '''not''' a technology playground, demonstration platform, or experimental showcase for novelty-driven automation.
| |
| | |
| AOWIS is designed for '''real agricultural and water infrastructure operations under hard constraints''' — unreliable electricity, limited water availability, harsh environments, and minimal technical support.
| |
| | |
| In many regions, particularly across Africa, irrigation and water supply systems must operate:
| |
| | |
| * With '''unstable or low-quality power supply'''
| |
| * Under '''strict water scarcity'''
| |
| * With '''limited or no internet connectivity'''
| |
| * With '''minimal maintenance capacity'''
| |
| * In environments where '''system failure directly impacts livelihoods and public health'''
| |
| | |
| AOWIS therefore prioritizes '''operational robustness over technological sophistication'''.
| |
| | |
| This means:
| |
| | |
| * Systems must remain functional during power outages and brownouts
| |
| * Water distribution and irrigation decisions must be conservative and resource-efficient
| |
| * Automation must degrade safely rather than fail catastrophically
| |
| * Manual intervention must always remain possible and documented
| |
| * Advanced analytics or AI are optional and never safety-critical
| |
| | |
| Crucially, AOWIS treats '''humans as integral system components''', not as an afterthought:
| |
| | |
| * Farm or community personnel may act as '''sensors''', performing measurements and observations
| |
| * Personnel may act as '''actuators''', executing irrigation or control actions manually
| |
| * All human actions and observations are structured, logged, and auditable
| |
| | |
| To further increase resilience, AOWIS explicitly acknowledges that '''electronics may not always be available'''.
| |
| | |
| As a result, AOWIS supports the concept of '''paper-based operation''' as a formal part of the standard:
| |
| | |
| * Standardized paper questionnaires and data capture sheets
| |
| * Paper-based instruction and task lists derived from AOWIS logic
| |
| * Direct compatibility between paper records and AOWIS‑DB data models
| |
| | |
| This ensures that AOWIS-aligned operations can continue:
| |
| | |
| * During prolonged power outages
| |
| * In the absence of functioning electronic devices
| |
| * In emergency or transitional scenarios
| |
| | |
| AOWIS explicitly rejects:
| |
| | |
| * Cloud-dependent control loops
| |
| * Unverified “smart” behavior without physical safeguards
| |
| * Experimental features that increase operational risk
| |
| * Designs that assume continuous power, water, connectivity, or electronics
| |
| | |
| Instead, AOWIS defines a '''practical engineering standard for water and agricultural infrastructure''' that works '''when conditions are bad, not only when they are ideal''' — and that remains usable in the '''everyday reality of farmers and rural communities''', not just in laboratory or pilot environments.
| |
| | |
| == Research, Optimization & Collaboration ==
| |
| | |
| At the same time, AOWIS provides a '''stable, production-grade baseline''' that enables '''applied agricultural and water infrastructure research under real operating conditions'''. By standardizing data models, control boundaries, and safety constraints, AOWIS allows research activities to be conducted '''without compromising operational systems'''.
| |
| | |
| Research within AOWIS is explicitly anchored in the '''real, day-to-day operations of farmers and rural communities''', operating under practical constraints such as unreliable power supply, water scarcity, limited connectivity, and minimal maintenance capacity.
| |
| | |
| This enables:
| |
| | |
| * Long-term observation of crops, soils, and water use under difficult conditions
| |
| * Comparative studies across regions and climates using compatible data
| |
| * Validation of agricultural methods '''as part of real, everyday operations''', not isolated test environments
| |
| * Collaboration with '''universities, research institutes, NGOs, and public agencies'''
| |
| * Evidence-based optimization of irrigation strategies, crop selection, and water resource management
| |
| | |
| AOWIS actively '''embraces cooperation''' with research institutions and non-governmental organizations. Such cooperation is a '''core design objective''' of the standard, not an optional add-on.
| |
| | |
| Research and optimization activities within AOWIS:
| |
| | |
| * Are strictly '''non-intrusive to safety-critical control'''
| |
| * Operate through '''supervision, analysis, and recommendation layers'''
| |
| * Can be deployed incrementally and disabled without operational impact
| |
| * Respect farm and community operational sovereignty and decision authority
| |
| * Feed validated improvements back into AOWIS defaults and AOWIS‑Databases where appropriate
| |
| | |
| Through this approach, AOWIS serves both as:
| |
| | |
| * A '''reliable operational standard''' for farmers and rural water systems today
| |
| * A '''shared research foundation''' for universities, NGOs, and public institutions to improve agriculture and water access under constrained real-world conditions
| |
| | |
| == Modular & Extendable Architecture ==
| |
| | |
| AOWIS is a '''modular framework''' that defines a common controller architecture while allowing domain-specific extensions.
| |
| | |
| * '''Core System:''' Water infrastructure control, crop irrigation, sensors, actuation logic, and human input logging.
| |
| * '''Module Interface:''' Standardized integration with Field, Farm, and HQ controllers.
| |
| * '''Selective Adoption:''' Farms and water operators implement only the modules relevant to their operations.
| |
| | |
| '''Example Modules:'''
| |
| | |
| * Crop Irrigation (core) – soil, water, weather, optical sensing, human input
| |
| * Poultry Farming – feed, water, egg production, climate monitoring
| |
| * Livestock / Animal Husbandry – veterinary records, grooming, breeding, production metrics
| |
| * Greenhouse / Hydroponics – nutrient dosing, CO₂, lighting, climate control
| |
| * Custom / Research Modules – farm- or project-specific extensions
| |
| | |
| '''Module Requirements:'''
| |
| | |
| * Standardized data logging compatible with AOWIS controllers
| |
| * Offline-first operation with optional synchronization
| |
| * Optional analytics or AI must not interfere with safety or core compliance
| |
| | |
| '''Benefits:'''
| |
| | |
| * Enables cross-domain experimentation and long-term optimization
| |
| * Supports third-party module development
| |
| * Future-proofs AOWIS for diverse agricultural and water management use cases
| |
| | |
| == AOWIS‑DB ==
| |
| | |
| AOWIS includes an optional [[Databases:Knowledge Base]] providing '''curated default parameters for crops, soils, and farm operations''', derived from aggregated global data.
| |
| | |
| '''Purpose:'''
| |
| | |
| * Provide reliable starting parameters for irrigation, crops, and nutrients
| |
| * Enable knowledge transfer to new or underserved regions
| |
| * Support research-driven improvement of farm operations
| |
| | |
| '''Offline-First & Federated Operation:'''
| |
| | |
| * Fully functional without internet connectivity
| |
| * Data synchronization via network or '''physical transfer (USB / SD cards)'''
| |
| * Field Controllers log locally; Farm Controllers aggregate; HQ Controllers merge datasets
| |
| | |
| '''Data Contribution Model:'''
| |
| | |
| * Farms may optionally contribute anonymized operational data
| |
| * Contributors receive '''full access to AOWIS‑DB'''
| |
| * Only aggregated, privacy-preserving data is used globally
| |
| | |
| '''Database Content Examples:'''
| |
| | |
| * Crop growth and irrigation parameters
| |
| * Soil profiles and water-holding characteristics
| |
| * Sensor thresholds and measurement guidance
| |
| * Regional environmental defaults
| |
| * Research and human intervention logs
| |
| | |
| == Purpose & Motivation ==
| |
| | |
| AOWIS provides a '''safe, neutral, and verifiable foundation''' for modern farming systems, prioritizing '''smallholder farmers, humanitarian programs, and public-sector deployments''' over proprietary or cloud-dependent solutions.
| |
| | |
| AOWIS‑DB complements AOWIS by offering '''trusted defaults and decision support''', curated and maintained within the AOWIS ecosystem.
| |
| | |
| == Key Motivations ==
| |
| | |
| * '''Humanitarian Impact:''' Support food security, reliable water access, and resilience for vulnerable communities.
| |
| * '''Reliable Decision Support:''' Provide geo-aware crop suitability and operational guidance.
| |
| * '''Offline-First Inclusion:''' Ensure full participation without permanent connectivity.
| |
| * '''Data-Driven Improvement:''' Use aggregated data to improve global recommendations.
| |
| * '''Climate Insight:''' Enable long-term analysis of climate impacts on agriculture.
| |
| * '''Non-Extractive Model:''' Sustain AOWIS through governments, NGOs, and aid programs rather than profit-driven data extraction.
| |
| | |
| == Normative Language ==
| |
| | |
| The following terms define requirement levels used in AOWIS documentation:
| |
| | |
| * MUST – indicates an absolute requirement for compliance with the standard.
| |
| * MUST NOT – indicates an absolute prohibition.
| |
| * SHOULD – indicates a strong recommendation, though alternative approaches may exist.
| |
| * SHOULD NOT – indicates a discouraged practice.
| |
| * MAY – indicates an optional feature or capability.
| |
| | |
| These definitions follow common engineering standard conventions ([[rfc:2119|RFC 2119]], [[rfc:8174|RFC 8174]]) and ensure that AOWIS specifications can be interpreted consistently across implementations.
| |
| | |
| == Versioning ==
| |
| | |
| AOWIS follows the [https://semver.org/?utm_source=copilot.com semantic versioning model]:
| |
| | |
| * Major versions introduce architectural changes
| |
| * Minor versions introduce new modules or capabilities
| |
| * Patch versions introduce clarifications and corrections
| |
| | |
| Implementations SHOULD declare the AOWIS version they comply with.
| |
| | |
| == Summary ==
| |
| | |
| * AOWIS defines a '''robust, modular, and fail-safe architecture for water and farm infrastructure control'''.
| |
| * AOWIS supports both '''irrigation systems and community water supply infrastructure'''.
| |
| * AOWIS‑DB provides '''curated agricultural knowledge and operational defaults''' within the AOWIS framework.
| |
| * Together, they enable '''resilient, efficient, and sustainable farming and water management''', especially in regions where reliability matters most.
| |
| | |
| = AOWIS Documentation Structure =
| |
| | |
| == 1. Foundations ==
| |
| * [[Principles:Core_Principles_&_Design_Philosophy|Core Principles & Design Philosophy]] | | * [[Principles:Core_Principles_&_Design_Philosophy|Core Principles & Design Philosophy]] |
| * [[Principles:Research_Partner_Positioning]] | | * [[Principles:Research_Partner_Positioning|Research Partner Positioning]] |
| * [[Principles:Robustness]] | | * [[Principles:Robustness|System Robustness]] |
| * [[Principles:Real_World_Mapping]] | | * [[Principles:Real_World_Mapping|Real-World Mapping]] |
| * [[Principles:Terminology_&_Definitions|Terminology & Definitions]] | | * [[Principles:Terminology_&_Definitions|Terminology & Definitions]] |
|
| |
|
| == 2. System Architecture ==
| |
| * [[Architecture:System_Architecture_Overview|System Architecture Overview]] | | * [[Architecture:System_Architecture_Overview|System Architecture Overview]] |
| ** [[Architecture:Field_Controller_Layer|Field Controller Layer]] | | ** [[Architecture:Field_Controller_Layer|Field Controller Layer]] |
| Line 250: |
Line 32: |
| ** [[Architecture:Communication_Protocols|Communication Protocols & Standards]] | | ** [[Architecture:Communication_Protocols|Communication Protocols & Standards]] |
|
| |
|
| == 3. Infrastructure & Control Interfaces ==
| |
| * [[Infrastructure:Hydraulic_&_Water_Systems|Hydraulic & Water Systems]] | | * [[Infrastructure:Hydraulic_&_Water_Systems|Hydraulic & Water Systems]] |
| * [[Infrastructure:Electrical_&_Power_Control_Interfaces|Electrical & Power Control Interfaces]] | | * [[Infrastructure:Electrical_&_Power_Control_Interfaces|Electrical & Power Control Interfaces]] |
| * [[Infrastructure:Valves,_Pumps_&_Actuation|Valves, Pumps & Actuation]] | | * [[Infrastructure:Valves,_Pumps_&_Actuation|Valves, Pumps & Actuation]] |
|
| |
|
| == 4. Measurement, Monitoring & Documentation ==
| |
| * [[Measurement:Sensors_&_Environmental_Monitoring|Sensors & Environmental Monitoring]] | | * [[Measurement:Sensors_&_Environmental_Monitoring|Sensors & Environmental Monitoring]] |
| * [[Measurement:Data_Models_&_Documentation_Standards|Data Models & Documentation Standards]] | | * [[Measurement:Data_Models_&_Documentation_Standards|Data Models & Documentation Standards]] |
|
| |
|
| == 5. Operation & Safety ==
| |
| * [[Operations:Operational_Logic_&_Decision_Hierarchy|Operational Logic & Decision Hierarchy]] | | * [[Operations:Operational_Logic_&_Decision_Hierarchy|Operational Logic & Decision Hierarchy]] |
| * [[Operations:Safety,_Fail-Safe_&_Bypass_Mechanisms|Safety, Fail-Safe & Bypass Mechanisms]] | | * [[Operations:Safety,_Fail-Safe_&_Bypass_Mechanisms|Safety, Fail-Safe & Bypass Mechanisms]] |
|
| |
|
| == 6. Reference & Compliance ==
| |
| * [[Reference:Reference_Implementations|Reference Implementations]] | | * [[Reference:Reference_Implementations|Reference Implementations]] |
| * [[Reference:Certification,_Compliance_&_Auditing|Certification, Compliance & Auditing]] | | * [[Reference:Certification,_Compliance_&_Auditing|Certification, Compliance & Auditing]] |
| * [[Reference:Non-Profit_Governance_&_Protection_Strategy|Non-Profit Governance & Protection Strategy]] | | * [[Reference:Non-Profit_Governance_&_Protection_Strategy|Non-Profit Governance & Protection Strategy]] |
|
| |
|
| == 7. Training & Professional Certification ==
| |
| * [[Training:Training_Programs|Training Programs]] | | * [[Training:Training_Programs|Training Programs]] |
| * [[Training:Professional_Certification_Levels|Professional Certification Levels]] | | * [[Training:Professional_Certification_Levels|Professional Certification Levels]] |
|
| |
|
| == 8. Modular & Optional Modules ==
| |
| * [[Modules:Crop_Irrigation_Core_Module|Crop Irrigation (Core Module)]] | | * [[Modules:Crop_Irrigation_Core_Module|Crop Irrigation (Core Module)]] |
| * [[Modules:Poultry_Farming_Module|Poultry Farming Module]] | | * [[Modules:Poultry_Farming_Module|Poultry Farming Module]] |
| Line 279: |
Line 55: |
| * [[Modules:Custom_Third-Party_Modules|Custom / Third-Party Modules]] | | * [[Modules:Custom_Third-Party_Modules|Custom / Third-Party Modules]] |
|
| |
|
| == 9. AOWIS Databases == | | == Databases == |
| * [[Databases:AOWIS-Agro-DB|Knowledge Base (Crops, Soils, Climate)]]
| | AOWIS supports a modular database system. Each database provides curated operational knowledge while maintaining offline-first, federated functionality: |
| * [[Databases:AOWIS-Hardware-DB|Hardware Database]]
| |
| * [[Databases:AOWIS-Device-DB|Certified Devices Database]]
| |
|
| |
|
| == 10. Supporting Material == | | * [[Databases:AOWIS-Agro-DB|Agricultural Knowledge Base]] – crops, soils, climate zones, irrigation parameters. |
| | * [[Databases:AOWIS-Hardware-DB|Hardware Database]] – pumps, valves, sensors, tanks. |
| | * [[Databases:AOWIS-Device-DB|Certified Devices Database]] – supported controllers, sensors, and actuators. |
| | |
| | == Supporting Material == |
| * [[Supporting:Glossary|Glossary]] | | * [[Supporting:Glossary|Glossary]] |
| * [[Supporting:Change_Log_&_Versioning|Change Log & Versioning]] | | * [[Supporting:Change_Log_&_Versioning|Change Log & Versioning]] |
| * [[Supporting:Hardware_Database|Hardware Database Reference]] | | * [[Supporting:Hardware_Database|Hardware Database Reference]] |
|
| |
|
| | == Summary == |
| | * AOWIS defines a '''robust, modular, and fail-safe architecture''' for water and farm infrastructure control. |
| | * Supports both '''irrigation systems and community water supply infrastructure'''. |
| | * Modular databases provide '''curated knowledge and operational defaults'''. |
| | * Designed for '''resilient, efficient, and sustainable agriculture''' in low-infrastructure, climate-stressed regions. |
| | |
| | == Featured Article == |
| {{Box | | {{Box |
| | title = Featured article | | | title = Featured article |
