Main Page: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
{{MainPageBanner}} | {{MainPageBanner}} | ||
{{Header box | |||
| title = Motivation | |||
| color = green | |||
| body = | |||
In less developed regions, such as rural areas and small towns in Africa, water distribution remains a significant challenge. While NGOs have been successfully supporting communities for decades by drilling wells, installing pumps, and sometimes building water towers, distributing water across a network on the surface is often difficult. | |||
Local initiatives that take on these projects frequently encounter a situation where operating the system manually becomes unsustainable, requiring constant attention. Qualified personnel are scarce, and suitable technology to support automated or semi-automated operation is either unavailable under local constraints or too expensive. | |||
This is where AOWIS aims to contribute: by providing an open standard for designing, deploying, and managing water and agricultural infrastructure in such environments. AOWIS supports both the planning phase—helping initiatives evaluate and design systems based on regional conditions such as topography—and the operational phase, including system monitoring, control, and maintenance. | |||
In addition, AOWIS aims to support the training of local technicians and to collaborate closely with experienced NGOs and local initiatives that already operate and maintain such systems, in order to improve sustainability and reduce operational burden. | |||
}} | |||
<div class="hbox-row"> | <div class="hbox-row"> | ||
Revision as of 02:53, 19 March 2026
In less developed regions, such as rural areas and small towns in Africa, water distribution remains a significant challenge. While NGOs have been successfully supporting communities for decades by drilling wells, installing pumps, and sometimes building water towers, distributing water across a network on the surface is often difficult.
Local initiatives that take on these projects frequently encounter a situation where operating the system manually becomes unsustainable, requiring constant attention. Qualified personnel are scarce, and suitable technology to support automated or semi-automated operation is either unavailable under local constraints or too expensive.
This is where AOWIS aims to contribute: by providing an open standard for designing, deploying, and managing water and agricultural infrastructure in such environments. AOWIS supports both the planning phase—helping initiatives evaluate and design systems based on regional conditions such as topography—and the operational phase, including system monitoring, control, and maintenance.
In addition, AOWIS aims to support the training of local technicians and to collaborate closely with experienced NGOs and local initiatives that already operate and maintain such systems, in order to improve sustainability and reduce operational burden.
AOWIS provides a unified framework...
- power is unreliable
- connectivity is intermittent
- equipment is diverse or aging
- trained staff may be limited
- safety and autonomy are essential
AOWIS enables systems that continue working safely — even when everything else fails.
Many communities rely on infrastructure that is fragile, manually operated, or dependent on unstable networks. AOWIS addresses this by defining:
- offline‑first operation
- human‑in‑the‑loop control
- safe fallback behavior
- modular, extensible logic
- shared infrastructure models
- transparent governance
The goal is to make essential systems **robust, maintainable, and locally operable**.
AOWIS is built around a three‑layer control model:
- Field Controller – Local, autonomous, safety‑critical
- Farm Controller – Coordination, scheduling, logic
- HQ Controller – Oversight, reporting, governance
Core principles include:
- Offline‑first
- Measurement‑driven
- Fail‑safe by design
- Human‑operable at all times
- Modular and extensible
- Transparent and auditable
If you are new to AOWIS, begin with:
- Design Philosophy
- Definitions
- Normative Requirements
- Module Template
- Contributor Guide
- Writing Style Guide
These pages explain how to read, use, and contribute to the standard.
The AOWIS standard is organized into dedicated namespaces. These sections form the technical backbone of the project.
- [[Standard:|Standard]] – Normative requirements and definitions
- [[Concepts:|Concepts]] – Philosophy, rationale, and real‑world context
- [[Architecture:|Architecture]] – System structure and controller design
- [[Infrastructure:|Infrastructure]] – Physical systems and components
- [[Measurement:|Measurement]] – Sensors, manual readings, derived values
- [[Data:|Data]] – Data models, logs, sync formats
- [[Operations:|Operations]] – Runtime logic and decision hierarchy
- [[Modules:|Modules]] – Domain‑specific extensions
- [[Databases:|Databases]] – Federated knowledge bases
- [[Governance:|Governance]] – Certification, compliance, licensing
- [[Training:|Training]] – Human capacity building
- [[Reference:|Reference]] – Examples, glossary, FAQ
For a full overview, see the Table of Contents.
AOWIS includes a transparent governance model to ensure:
- open participation
- clear certification processes
- stable versioning
- long‑term protection of the standard
See: [[Governance:|Governance]].
AOWIS is designed for practical use in:
- rural water systems
- smallholder agriculture
- community irrigation
- livestock and poultry systems
- greenhouses and controlled environments
Case studies and implementation examples can be found in the [[Reference:|Reference]] namespace.
AOWIS is an open, evolving standard. Contributions are welcome.
