AOWIS - User contributions [en]

External:EPANET:Main Page

2026-06-04T15:43:49Z

Samuel:

* Part of [[External:Main_Page|External]]

EPANET is a software tool provided by the EPA (Environemt Protection Agency). This is the description of this project as found at [https://www.epa.gov/water-research/epanet EPANET]:

<blockquote>
Application for Modeling Drinking Water Distribution Systems

EPANET is a software application used throughout the world to model water distribution systems. It was developed as a tool for understanding the movement and fate of drinking water constituents within distribution systems, and can be used for many different types of applications in distribution systems analysis.

Today, engineers and consultants use EPANET to design and size new water infrastructure, retrofit existing aging infrastructure, optimize operations of tanks and pumps, reduce energy usage, investigate water quality problems, and prepare for emergencies. It can also be used to model contamination threats and evaluate resilience to security threats or natural disasters.
</blockquote>

* [https://en.wikipedia.org/wiki/EPANET EPANET at Wikipedia]
* [https://www.epa.gov/water-research/epanet The official site at EPA] - Current latest Version is ''2.2''
* [https://github.com/USEPA/EPANET2.2 EPANET GitHub] - Alternative Source at GitHub

== Open Water Analytics - OWA ==

This is the self-description of this project as found at [http://wateranalytics.org Open Water Analytics]:

<blockquote>
Open Water Analytics is the home of the community projects for EPANET and SWMM, and related tools and technologies. We are an open community for the exchange of information and ideas related to computing and analysis in the water & wastewater industries. This informal collective in an umbrella that covers many groups and projects; members with varying affiliations work together to craft the current and future development of these mission-critical software tools.
</blockquote>

=== OWA-EPANET ===

* [http://wateranalytics.org/EPANET OWA-EPANET Documentation]

==== GitHub ====
* [https://github.com/OpenWaterAnalytics OpenWaterAnalytics] - OpenWaterAnalytics Main GitHub
** [https://github.com/OpenWaterAnalytics/EPANET OWA-EPANET] - OWA-EPANET Main Repo
** [https://github.com/OpenWaterAnalytics/EPANET-UI OWA-EPANET GUI] - Graphical User Interface
*** [https://sites.google.com/view/epanet-ui OWA-EPANET GUI downloads] - Download Compiled Executables for Linux & Windows

===== Python Wrappers =====
* [https://github.com/OpenWaterAnalytics/epanet-python OWA-EPANET Python] - Auto-Generated Python-Wrapper
** [https://pypi.org/project/owa-epanet PyPI] - Auto-Generated Python Wrapper for OWA-EPANET
* [https://github.com/OpenWaterAnalytics/EPyT OWA-EPANET EPyT] - A more sophisticated Python Library provided by [https://www.kios.ucy.ac.cy KIOS Research and Innovation Center of Excellence, University of Cyprus]

=== OWA-StormWater-Management-Model (SWMM) ===

Storm Water Management Model (SWMM) is a computer model used to simulate how rainfall becomes runoff and moves through urban drainage systems.

It was developed by the United States Environmental Protection Agency and is one of the most widely used tools worldwide for stormwater, sewer, and urban drainage analysis.

So while EPANET answers ''"How does water flow through a drinking water distribution network?"'', SWMM answers ''"What happens when it rains?"''

==== GitHub ====
* [https://github.com/pyswmm/Stormwater-Management-Model Stormwater Management Model (SWMM)]

== epanet-js ==
* [https://github.com/epanet-js epanet-js GitHub]
* [https://app.epanetjs.com Online Demo]

External:EPANET:Main Page

2026-06-04T15:43:21Z

2026-06-03T22:38:58Z

Samuel: Samuel uploaded a new version of File:Logo.png

Samuel:

External:EPANET:Main Page

2026-06-03T01:13:52Z

Samuel:

External:Main Page

2026-06-03T01:06:24Z

Samuel:

== Related Projects ==
* [https://sdgs.un.org/goals THE 17 GOALS - Sustainable Development Goals (SDGs)]
** [https://www.bmz.de/de/agenda-2030 German Version]

* [[External:Horizon Europe:Main Page|Horizon Europe]]
** [[External:Water4All:Main Page|Water4All]] - Successor of ''Water JPI''
*** [[External:WaterJPI:Main Page|WaterJPI]] - Water Joint Programming Initiative
**** [[External:WaterJPI:IoT_H20|IoT.H20]] - Managing Water Networks with IoT Tech ([[Architecture:Protocols:LoRa/LoRaWAN|LoRaWAN]])

== Basic Concepts ==
=== SCADA ===
AOWIS is basically a SCADA (Supervisory Control and Data Acquisition) system, or at least closely related. While established SCADA systems are usually too expensive for smaller organizations or local initiatives, AOWIS tries to fill in this gap by going an approach closer to modern IoT ideas, but still keep everything robust and offline-first.

== Software ==
* [[External:EPANET:Main Page|EPANET]] - Software for Simulating Drinking Water Distribution Networks

=== Internet Links ===
* [https://thingsboard.io Thingsboard] - OpenSource IoT Platform

2026-05-24T17:22:57Z

Samuel:

Main Page

2026-05-24T17:08:29Z

Samuel:

{{MainPageBanner}}

{{Header box
| title = Motivation
| color = teal
| body =

[[File:Countryside.jpg|class=fullwidth|center]]

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

{{Header box
| title = Why an Open Standard is Needed
| color = turquoise
| body =

[[File:Cooperation.jpg|500px|frameless|right]]

In environments where infrastructure is built over decades by many different actors using solutions from different vendors and manufacturers, systems become fragmented, forcing operators to manage multiple incompatible tools and workflows while making daily operation, maintenance, expansion, and staff training increasingly complex and costly.

This fragmentation often results in vendor lock-in, where systems depend on specific tools, expertise, or suppliers that may not remain available over the full lifecycle of the infrastructure.

An open standard provides a shared technical foundation that enables interoperability and ensures systems can be maintained and extended independently of any single product or provider.

AOWIS defines such a foundation for water and agricultural infrastructure under real-world operational constraints.
}}

<div class="hbox-row">
{{Header box
| title = Operation Conditions of AOWIS
| color = lightblue
| body =
[[File:Village.jpg|250px|frameless|right]]

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

{{Header box
| title = Facing the Challenges
| color = lightblue
| body =
AOWIS addresses these operational challenges through the following principles:

* human-in-the-loop control
* offline-first operation
* safe fallback behavior
* modular and extensible logic
* shared infrastructure models
* training programs for local operators
* transparent governance

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

<div class="hbox-row">
{{Header box
| title = How AOWIS Works
| color = brown
| body =
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
}}

{{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_External|Contributor Guide - External]]
* [[AOWIS:Contributor_Guide_Internal|Contributor Guide - Internal]]
* [[AOWIS:Writing_Style_Guide|Writing Style Guide]]
* [[AOWIS:AI_Usage_Guide|AI Usage Guide]]
* [[AOWIS:Research_Form_Guide|Research Form Guide]]
* [[AOWIS:Naming_Convention_Specification|Naming Convention Specification]]
* [[AOWIS:Change_Log__Versioning|Change Log & Versioning]]
* [[AOWIS:Wiki|This Wiki]]

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.
These sections form the technical backbone of the project.

* [[Motivation:Main_Page|'''Motivation''']] - Causal justification of design requirements based on real-world failures, constraints, and operational realities
* [[Standard:Main_Page|'''Standard''']] – Normative requirements and definitions that specify what AOWIS-compliant systems must do.
* [[Concepts:Main_Page|'''Concepts''']] – Core ideas, philosophy, and contextual understanding that explain the system but do not prescribe implementation.
* [[Architecture:Main_Page|'''Architecture''']] – High-level system structure, including controllers, layers, and their interactions.
* [[Infrastructure:Main_Page|'''Infrastructure''']] – Physical and deployed systems such as pumps, pipes, valves, energy systems, and field hardware.
* [[Measurement:Main_Page|'''Measurement''']] – Definition and handling of sensor data, manual measurements, calibration, and derived physical values.
* [[Data:Main_Page|'''Data''']] – Data models, schemas, logging structures, synchronization formats, and data lifecycle rules.
* [[Operations:Main_Page|'''Operations''']] – Runtime behavior, control logic, state transitions, and decision-making hierarchy during system execution.
* [[Modules:Main_Page|'''Modules''']] – Reusable functional extensions that implement domain-specific capabilities within the system.
* [[Reference:Main_Page|'''Reference''']] – Concrete examples, reference implementations, sample deployments, and illustrative systems.
* [[Databases:Main_Page|'''Databases''']] – Federated and distributed knowledge bases, storage backends, and data persistence systems.
* [[Governance:Main_Page|'''Governance''']] – Rules for certification, compliance, auditing, trust, licensing, and organizational control structures.
* [[Training:Main_Page|'''Training''']] – Human skill development, operator training, documentation literacy, and capacity building systems.
* [[External:Main_Page|'''External''']] - External projects, standards, technologies, and systems that relate to or influence AOWIS.

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

{{Header box
| title = Roadmap
| color = grey
| body =
[[File:Boring.jpg|250px|frameless|right]]

At this stage, AOWIS is in an early development and conceptualization phase. The following areas outline the current technical priorities:

=== Research ===
* Decide which [[Architecture:Protocols:Main_Page|Wireless Protocols]] could or should be used for AOWIS.
** Result: The first iteration will be built with [[Architecture:Protocols:LoRa/LoRaWAN|LoRaWAN]] and [[Architecture:Protocols:MQTT|MQTT]]

=== Hardware ===
* Develop sensors for measuring water levels in reservoirs.
* Develop voltage monitoring to support sizing and management of solar battery systems.
* Design mechanisms for emergency shutdown of electrical systems within milliseconds in case of overvoltage or critical faults.
** This should be done low-tech with regular electrician solutions.

=== Software ===
* Begin conceptualization of the core controller.
** The controller must be capable of modeling and evaluating complex graphs representing water distribution networks in real time, enabling dynamic adaptation to changing conditions.
}}

<div class="hbox-row">
{{Header box
| title = Governance & Legitimacy
| color = turquoise
| body =
AOWIS includes a transparent governance model to ensure:

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

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

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

* [https://github.com/aowis-org GitHub]
}}
</div>

{{Header box
| title = Partners
| color = indigo
| body =
test
}}

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

Main Page

2026-05-24T17:08:08Z

Samuel:

{{MainPageBanner}}

{{Header box
| title = Motivation
| color = green
| body =

[[File:Countryside.jpg|class=fullwidth|center]]

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

{{Header box
| title = Why an Open Standard is Needed
| color = turquoise
| body =

[[File:Cooperation.jpg|500px|frameless|right]]

In environments where infrastructure is built over decades by many different actors using solutions from different vendors and manufacturers, systems become fragmented, forcing operators to manage multiple incompatible tools and workflows while making daily operation, maintenance, expansion, and staff training increasingly complex and costly.

This fragmentation often results in vendor lock-in, where systems depend on specific tools, expertise, or suppliers that may not remain available over the full lifecycle of the infrastructure.

An open standard provides a shared technical foundation that enables interoperability and ensures systems can be maintained and extended independently of any single product or provider.

AOWIS defines such a foundation for water and agricultural infrastructure under real-world operational constraints.
}}

<div class="hbox-row">
{{Header box
| title = Operation Conditions of AOWIS
| color = lightblue
| body =
[[File:Village.jpg|250px|frameless|right]]

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

{{Header box
| title = Facing the Challenges
| color = lightblue
| body =
AOWIS addresses these operational challenges through the following principles:

* human-in-the-loop control
* offline-first operation
* safe fallback behavior
* modular and extensible logic
* shared infrastructure models
* training programs for local operators
* transparent governance

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

<div class="hbox-row">
{{Header box
| title = How AOWIS Works
| color = brown
| body =
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
}}

{{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_External|Contributor Guide - External]]
* [[AOWIS:Contributor_Guide_Internal|Contributor Guide - Internal]]
* [[AOWIS:Writing_Style_Guide|Writing Style Guide]]
* [[AOWIS:AI_Usage_Guide|AI Usage Guide]]
* [[AOWIS:Research_Form_Guide|Research Form Guide]]
* [[AOWIS:Naming_Convention_Specification|Naming Convention Specification]]
* [[AOWIS:Change_Log__Versioning|Change Log & Versioning]]
* [[AOWIS:Wiki|This Wiki]]

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.
These sections form the technical backbone of the project.

* [[Motivation:Main_Page|'''Motivation''']] - Causal justification of design requirements based on real-world failures, constraints, and operational realities
* [[Standard:Main_Page|'''Standard''']] – Normative requirements and definitions that specify what AOWIS-compliant systems must do.
* [[Concepts:Main_Page|'''Concepts''']] – Core ideas, philosophy, and contextual understanding that explain the system but do not prescribe implementation.
* [[Architecture:Main_Page|'''Architecture''']] – High-level system structure, including controllers, layers, and their interactions.
* [[Infrastructure:Main_Page|'''Infrastructure''']] – Physical and deployed systems such as pumps, pipes, valves, energy systems, and field hardware.
* [[Measurement:Main_Page|'''Measurement''']] – Definition and handling of sensor data, manual measurements, calibration, and derived physical values.
* [[Data:Main_Page|'''Data''']] – Data models, schemas, logging structures, synchronization formats, and data lifecycle rules.
* [[Operations:Main_Page|'''Operations''']] – Runtime behavior, control logic, state transitions, and decision-making hierarchy during system execution.
* [[Modules:Main_Page|'''Modules''']] – Reusable functional extensions that implement domain-specific capabilities within the system.
* [[Reference:Main_Page|'''Reference''']] – Concrete examples, reference implementations, sample deployments, and illustrative systems.
* [[Databases:Main_Page|'''Databases''']] – Federated and distributed knowledge bases, storage backends, and data persistence systems.
* [[Governance:Main_Page|'''Governance''']] – Rules for certification, compliance, auditing, trust, licensing, and organizational control structures.
* [[Training:Main_Page|'''Training''']] – Human skill development, operator training, documentation literacy, and capacity building systems.
* [[External:Main_Page|'''External''']] - External projects, standards, technologies, and systems that relate to or influence AOWIS.

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

{{Header box
| title = Roadmap
| color = grey
| body =
[[File:Boring.jpg|250px|frameless|right]]

At this stage, AOWIS is in an early development and conceptualization phase. The following areas outline the current technical priorities:

=== Research ===
* Decide which [[Architecture:Protocols:Main_Page|Wireless Protocols]] could or should be used for AOWIS.
** Result: The first iteration will be built with [[Architecture:Protocols:LoRa/LoRaWAN|LoRaWAN]] and [[Architecture:Protocols:MQTT|MQTT]]

=== Hardware ===
* Develop sensors for measuring water levels in reservoirs.
* Develop voltage monitoring to support sizing and management of solar battery systems.
* Design mechanisms for emergency shutdown of electrical systems within milliseconds in case of overvoltage or critical faults.
** This should be done low-tech with regular electrician solutions.

=== Software ===
* Begin conceptualization of the core controller.
** The controller must be capable of modeling and evaluating complex graphs representing water distribution networks in real time, enabling dynamic adaptation to changing conditions.
}}

<div class="hbox-row">
{{Header box
| title = Governance & Legitimacy
| color = turquoise
| body =
AOWIS includes a transparent governance model to ensure:

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

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

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

* [https://github.com/aowis-org GitHub]
}}
</div>

{{Header box
| title = Partners
| color = teal
| body =
test
}}

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

Main Page

2026-05-24T17:07:49Z

Samuel:

{{MainPageBanner}}

{{Header box
| title = Motivation
| color = green
| body =

[[File:Countryside.jpg|class=fullwidth|center]]

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

{{Header box
| title = Why an Open Standard is Needed
| color = turquoise
| body =

[[File:Cooperation.jpg|500px|frameless|right]]

In environments where infrastructure is built over decades by many different actors using solutions from different vendors and manufacturers, systems become fragmented, forcing operators to manage multiple incompatible tools and workflows while making daily operation, maintenance, expansion, and staff training increasingly complex and costly.

This fragmentation often results in vendor lock-in, where systems depend on specific tools, expertise, or suppliers that may not remain available over the full lifecycle of the infrastructure.

An open standard provides a shared technical foundation that enables interoperability and ensures systems can be maintained and extended independently of any single product or provider.

AOWIS defines such a foundation for water and agricultural infrastructure under real-world operational constraints.
}}

<div class="hbox-row">
{{Header box
| title = Operation Conditions of AOWIS
| color = lightblue
| body =
[[File:Village.jpg|250px|frameless|right]]

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

{{Header box
| title = Facing the Challenges
| color = lightblue
| body =
AOWIS addresses these operational challenges through the following principles:

* human-in-the-loop control
* offline-first operation
* safe fallback behavior
* modular and extensible logic
* shared infrastructure models
* training programs for local operators
* transparent governance

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

<div class="hbox-row">
{{Header box
| title = How AOWIS Works
| color = brown
| body =
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
}}

{{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_External|Contributor Guide - External]]
* [[AOWIS:Contributor_Guide_Internal|Contributor Guide - Internal]]
* [[AOWIS:Writing_Style_Guide|Writing Style Guide]]
* [[AOWIS:AI_Usage_Guide|AI Usage Guide]]
* [[AOWIS:Research_Form_Guide|Research Form Guide]]
* [[AOWIS:Naming_Convention_Specification|Naming Convention Specification]]
* [[AOWIS:Change_Log__Versioning|Change Log & Versioning]]
* [[AOWIS:Wiki|This Wiki]]

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.
These sections form the technical backbone of the project.

* [[Motivation:Main_Page|'''Motivation''']] - Causal justification of design requirements based on real-world failures, constraints, and operational realities
* [[Standard:Main_Page|'''Standard''']] – Normative requirements and definitions that specify what AOWIS-compliant systems must do.
* [[Concepts:Main_Page|'''Concepts''']] – Core ideas, philosophy, and contextual understanding that explain the system but do not prescribe implementation.
* [[Architecture:Main_Page|'''Architecture''']] – High-level system structure, including controllers, layers, and their interactions.
* [[Infrastructure:Main_Page|'''Infrastructure''']] – Physical and deployed systems such as pumps, pipes, valves, energy systems, and field hardware.
* [[Measurement:Main_Page|'''Measurement''']] – Definition and handling of sensor data, manual measurements, calibration, and derived physical values.
* [[Data:Main_Page|'''Data''']] – Data models, schemas, logging structures, synchronization formats, and data lifecycle rules.
* [[Operations:Main_Page|'''Operations''']] – Runtime behavior, control logic, state transitions, and decision-making hierarchy during system execution.
* [[Modules:Main_Page|'''Modules''']] – Reusable functional extensions that implement domain-specific capabilities within the system.
* [[Reference:Main_Page|'''Reference''']] – Concrete examples, reference implementations, sample deployments, and illustrative systems.
* [[Databases:Main_Page|'''Databases''']] – Federated and distributed knowledge bases, storage backends, and data persistence systems.
* [[Governance:Main_Page|'''Governance''']] – Rules for certification, compliance, auditing, trust, licensing, and organizational control structures.
* [[Training:Main_Page|'''Training''']] – Human skill development, operator training, documentation literacy, and capacity building systems.
* [[External:Main_Page|'''External''']] - External projects, standards, technologies, and systems that relate to or influence AOWIS.

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

{{Header box
| title = Roadmap
| color = grey
| body =
[[File:Boring.jpg|250px|frameless|right]]

At this stage, AOWIS is in an early development and conceptualization phase. The following areas outline the current technical priorities:

=== Research ===
* Decide which [[Architecture:Protocols:Main_Page|Wireless Protocols]] could or should be used for AOWIS.
** Result: The first iteration will be built with [[Architecture:Protocols:LoRa/LoRaWAN|LoRaWAN]] and [[Architecture:Protocols:MQTT|MQTT]]

=== Hardware ===
* Develop sensors for measuring water levels in reservoirs.
* Develop voltage monitoring to support sizing and management of solar battery systems.
* Design mechanisms for emergency shutdown of electrical systems within milliseconds in case of overvoltage or critical faults.
** This should be done low-tech with regular electrician solutions.

=== Software ===
* Begin conceptualization of the core controller.
** The controller must be capable of modeling and evaluating complex graphs representing water distribution networks in real time, enabling dynamic adaptation to changing conditions.
}}

<div class="hbox-row">
{{Header box
| title = Governance & Legitimacy
| color = turquoise
| body =
AOWIS includes a transparent governance model to ensure:

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

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

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

* [https://github.com/aowis-org GitHub]
}}
</div>

{{Header box
| title = Partners
| color = orange
| body =
test
}}

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