Jump to content

Main Page: Difference between revisions

From AOWIS
No edit summary
No edit summary
Line 17: Line 17:


{{Header box
{{Header box
  | title = What AOWIS Is
  | title = Operation Conditions of AOWIS
  | color = lightblue
  | color = lightblue
  | body =
  | body =
AOWIS provides a unified framework...
AOWIS is designed to operate under the real-world conditions faced by local initiatives. These include, among others:


* power is unreliable
* unreliable power supply
* connectivity is intermittent
* intermittent connectivity
* equipment is diverse or aging
* diverse or aging equipment
* trained staff may be limited
* limited availability of trained personnel
* safety and autonomy are essential
* the need for safety and autonomous operation


AOWIS enables systems that continue working safely even when everything else fails.
AOWIS enables systems that continue to function safely and reliably, even under degraded or adverse conditions.
}}
}}



Revision as of 03:02, 19 March 2026

AOWIS – Afritic Open Standard for Water & Agricultural Infrastructure

AOWIS is an open technical standard for safe and reliable water and agricultural infrastructure, designed for low-resource environments.

It defines how systems are operated through sensors and actuators, either autonomously, manually, or in combination. AOWIS is designed to function under conditions such as unstable power, limited connectivity, and minimal technical support, supporting both online and offline operation.

Motivation

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.

Operation Conditions of AOWIS

AOWIS is designed to operate under the real-world conditions faced by local initiatives. These include, among others:

  • unreliable power supply
  • intermittent connectivity
  • diverse or aging equipment
  • limited availability of trained personnel
  • the need for safety and autonomous operation

AOWIS enables systems that continue to function safely and reliably, even under degraded or adverse conditions.

Why AOWIS Exists

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**.

How AOWIS Works

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
Start Here

If you are new to AOWIS, begin with:

These pages explain how to read, use, and contribute to the standard.

Access 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.

Governance & Legitimacy

AOWIS includes a transparent governance model to ensure:

  • open participation
  • clear certification processes
  • stable versioning
  • long‑term protection of the standard

See: [[Governance:|Governance]].

Real‑World Impact

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.