Jump to content

Main Page: Difference between revisions

From AOWIS
No edit summary
 
No edit summary
Tag: Reverted
Line 1: Line 1:
<strong>MediaWiki has been installed.</strong>
= AOWIS – 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.''


Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software.
AOWIS defines how infrastructure can be operated by sensors, humans, or both — even with unstable power, limited connectivity, and minimal technical support.


== Getting started ==
----
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]
 
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
== What AOWIS Is ==
* [https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/ MediaWiki release mailing list]
AOWIS provides a unified framework for designing, operating, and governing water and agricultural infrastructure. 
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]
It is built for environments where:
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]
 
* 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 
 
----
 
== 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 '''[[AOWIS:Table_of_Contents|Official Table of Contents]]'''.
 
----
 
== Start Here ==
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]] 
 
These pages explain how to read, use, and contribute to the standard.
 
----
 
== 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.
 
----
 
== Navigation ==
* [[AOWIS:Table_of_Contents|Table of Contents]]
* [[Reference:Glossary|Glossary]] 
* [[Reference:FAQ|FAQ]]
* [[Reference:Change_Log|Change Log]] 
 
----
 
''AOWIS is an open, evolving standard. Contributions are welcome.''

Revision as of 01:48, 18 March 2026

AOWIS – 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 for designing, operating, and governing water and agricultural infrastructure. It is built for environments where:

  • 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

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 Official Table of Contents.


Start Here

If you are new to AOWIS, begin with:

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


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.