Jump to content

Main Page: Difference between revisions

From AOWIS
No edit summary
No edit summary
 
(7 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{MainPageBanner}}
{{MainPageBanner}}
<div class="hbox-row">


{{Header box
{{Header box
  | title = What AOWIS Is
  | title = What AOWIS Is
  | color = blue
  | color = lightblue
  | body =
  | body =
AOWIS provides a unified framework...
AOWIS provides a unified framework...
Line 16: Line 18:
}}
}}


 
{{Header box
== What AOWIS Is ==
| title = Why AOWIS Exists
AOWIS provides a unified framework for designing, operating, and governing water and agricultural infrastructure. 
  | color = lightblue
It is built for environments where:
  | body =  
 
* 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.
 
----
 
== Why AOWIS Exists ==
Many communities rely on infrastructure that is fragile, manually operated, or dependent on unstable networks.   
Many communities rely on infrastructure that is fragile, manually operated, or dependent on unstable networks.   
AOWIS addresses this by defining:
AOWIS addresses this by defining:
Line 43: Line 33:


The goal is to make essential systems **robust, maintainable, and locally operable**.
The goal is to make essential systems **robust, maintainable, and locally operable**.
}}
</div>


----
<div class="hbox-row">


== How AOWIS Works ==
{{Header box
| title = How AOWIS Works
| color = brown
| body =  
AOWIS is built around a three‑layer control model:
AOWIS is built around a three‑layer control model:


Line 61: Line 57:
* Modular and extensible   
* Modular and extensible   
* Transparent and auditable   
* Transparent and auditable   
}}


----
{{Header box
| title = Start Here
| color = yellow
| body =
If you are new to AOWIS, begin with:
 
* [[Concepts:Design_Philosophy|Design Philosophy]] 
* [[Standard:Definitions|Definitions]] 
* [[Standard:Normative_Requirements|Normative Requirements]] 
* [[Modules:Module_Template|Module Template]] 
* [[AOWIS:Contributor_Guide|Contributor Guide]]
* [[AOWIS:Writing_Style_Guide|Writing Style Guide]]


== Access the Standard ==
These pages explain how to read, use, and contribute to the standard.
}}
 
</div>
 
{{Header box
| title = Access the Standard
| color = purple
| body =  
The AOWIS standard is organized into dedicated namespaces.   
The AOWIS standard is organized into dedicated namespaces.   
These sections form the technical backbone of the project.
These sections form the technical backbone of the project.
Line 82: Line 98:


For a full overview, see the '''[[AOWIS:Table_of_Contents|Table of Contents]]'''.
For a full overview, see the '''[[AOWIS:Table_of_Contents|Table of Contents]]'''.
}}


----
<div class="hbox-row">


== Start Here ==
{{Header box
If you are new to AOWIS, begin with:
| title = Governance & Legitimacy
 
  | color = turquoise
* [[Concepts:Design_Philosophy|Design Philosophy]] 
  | body =  
* [[Standard:Definitions|Definitions]]  
* [[Standard:Normative_Requirements|Normative Requirements]] 
* [[Modules:Module_Template|Module Template]]  
* [[AOWIS:Contributor_Guide|Contributor Guide]]
* [[AOWIS:Writing_Style_Guide|Writing Style Guide]]
 
These pages explain how to read, use, and contribute to the standard.
 
----
 
== Governance & Legitimacy ==
AOWIS includes a transparent governance model to ensure:
AOWIS includes a transparent governance model to ensure:


Line 108: Line 114:


See: [[Governance:|Governance]].
See: [[Governance:|Governance]].
}}


----
{{Header box
 
| title = Real‑World Impact
== Real‑World Impact ==
| color = green
| body =  
AOWIS is designed for practical use in:
AOWIS is designed for practical use in:


Line 121: Line 129:


Case studies and implementation examples can be found in the [[Reference:|Reference]] namespace.
Case studies and implementation examples can be found in the [[Reference:|Reference]] namespace.
}}


----
</div>


== Navigation ==
{{Header box
| title = Navigation
| color = grey
| body =
* [[AOWIS:Table_of_Contents|Table of Contents]]   
* [[AOWIS:Table_of_Contents|Table of Contents]]   
* [[Reference:Glossary|Glossary]]   
* [[Reference:Glossary|Glossary]]   
* [[Reference:FAQ|FAQ]]   
* [[Reference:FAQ|FAQ]]   
* [[Reference:Change_Log|Change Log]]   
* [[Reference:Change_Log|Change Log]]   
 
}}
----


''AOWIS is an open, evolving standard. Contributions are welcome.''
''AOWIS is an open, evolving standard. Contributions are welcome.''

Latest revision as of 06:29, 18 March 2026

AOWIS – Afritic Open Standard for Water & Agricultural Infrastructure

AOWIS is an open technical standard for safe, reliable, offline‑capable water and agricultural systems in low‑resource environments.

AOWIS defines how infrastructure can be operated by sensors, humans, or both — even with unstable power, limited connectivity, and minimal technical support.

What AOWIS Is

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.

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.