<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://aowis.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Samuel</id>
	<title>AOWIS - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://aowis.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Samuel"/>
	<link rel="alternate" type="text/html" href="https://aowis.org/index.php/Special:Contributions/Samuel"/>
	<updated>2026-10-23T06:36:31Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.46.0</generator>
	<entry>
		<id>https://aowis.org/index.php?title=Governance:Non-Profit-Association&amp;diff=789</id>
		<title>Governance:Non-Profit-Association</title>
		<link rel="alternate" type="text/html" href="https://aowis.org/index.php?title=Governance:Non-Profit-Association&amp;diff=789"/>
		<updated>2026-10-05T12:57:00Z</updated>

		<summary type="html">&lt;p&gt;Samuel: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{AI-Generated&lt;br /&gt;
 | tool=ChatGPT&lt;br /&gt;
 | date=2026-10-05&lt;br /&gt;
 | scope=full page&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
= Konzept zur Gründung der AOWIS gUG =&lt;br /&gt;
&lt;br /&gt;
== Kurzfassung ==&lt;br /&gt;
&lt;br /&gt;
Für die langfristige institutionelle und gemeinnützige Trägerschaft von &#039;&#039;&#039;AOWIS (Afritic Open Water Infrastructure System)&#039;&#039;&#039; ist die Gründung einer &#039;&#039;&#039;gemeinnützigen Unternehmergesellschaft (gUG)&#039;&#039;&#039; vorgesehen.&lt;br /&gt;
&lt;br /&gt;
AOWIS ist ein offenes System für die Planung, den Entwurf, die Modellierung, den Bau, den Betrieb, die Überwachung, die Wartung und die Weiterentwicklung von Wasser- und Bewässerungsinfrastruktur über deren gesamten Lebenszyklus.&amp;lt;ref name=&amp;quot;AOWISMain&amp;quot;&amp;gt;https://aowis.org/index.php/Main_Page&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
AOWIS verbindet insbesondere:&lt;br /&gt;
&lt;br /&gt;
* Open-Source-Software,&lt;br /&gt;
* offene technische Standards,&lt;br /&gt;
* gemeinsame Infrastruktur- und Datenmodelle,&lt;br /&gt;
* Engineering-Methoden,&lt;br /&gt;
* Modellierung und Simulation,&lt;br /&gt;
* Monitoring und Steuerung,&lt;br /&gt;
* technische Dokumentation,&lt;br /&gt;
* Forschung und Evaluation,&lt;br /&gt;
* Ausbildung und Wissenstransfer.&lt;br /&gt;
&lt;br /&gt;
Die &#039;&#039;&#039;AOWIS gUG&#039;&#039;&#039; soll AOWIS institutionell tragen, weiterentwickeln und für gemeinnützige Zwecke einsetzen.&lt;br /&gt;
&lt;br /&gt;
Als zentraler gemeinnütziger Zweck bietet sich die &#039;&#039;&#039;Förderung der Entwicklungszusammenarbeit&#039;&#039;&#039; gemäß § 52 Abs. 2 Nr. 15 AO an.&amp;lt;ref name=&amp;quot;AO52&amp;quot;&amp;gt;https://www.gesetze-im-internet.de/ao_1977/__52.html&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Ergänzend kommen insbesondere in Betracht:&lt;br /&gt;
&lt;br /&gt;
* Förderung von Wissenschaft und Forschung,&lt;br /&gt;
* Förderung der Erziehung, Volks- und Berufsbildung,&lt;br /&gt;
* Förderung des Umweltschutzes.&lt;br /&gt;
&lt;br /&gt;
Die endgültige Formulierung der steuerbegünstigten Zwecke und des Gesellschaftsvertrags sollte vor der Gründung mit dem zuständigen Finanzamt abgestimmt werden.&lt;br /&gt;
&lt;br /&gt;
== Aufgaben der AOWIS gUG ==&lt;br /&gt;
&lt;br /&gt;
Die AOWIS gUG soll insbesondere:&lt;br /&gt;
&lt;br /&gt;
* AOWIS-Software entwickeln, pflegen und veröffentlichen,&lt;br /&gt;
* technische Standards und Datenmodelle entwickeln und dokumentieren,&lt;br /&gt;
* technische Dokumentation und Referenzmaterialien bereitstellen,&lt;br /&gt;
* Forschung und technische Evaluation durchführen oder unterstützen,&lt;br /&gt;
* Schulungs- und Ausbildungsmaterialien entwickeln,&lt;br /&gt;
* Workshops und Trainings durchführen,&lt;br /&gt;
* Pilot- und Demonstrationsprojekte durchführen,&lt;br /&gt;
* Projekte der Entwicklungszusammenarbeit unterstützen,&lt;br /&gt;
* Wissenstransfer und lokale technische Fähigkeiten fördern,&lt;br /&gt;
* mit Gemeinden, Betreibern, NGOs, Hochschulen, Forschungseinrichtungen und öffentlichen Stellen zusammenarbeiten,&lt;br /&gt;
* die langfristige Weiterentwicklung und Verfügbarkeit von AOWIS sicherstellen.&lt;br /&gt;
&lt;br /&gt;
== Gemeinnützige Zwecke ==&lt;br /&gt;
&lt;br /&gt;
=== Entwicklungszusammenarbeit ===&lt;br /&gt;
&lt;br /&gt;
Die &#039;&#039;&#039;Förderung der Entwicklungszusammenarbeit&#039;&#039;&#039; soll einen zentralen Zweck der AOWIS gUG bilden.&lt;br /&gt;
&lt;br /&gt;
AOWIS kann hierzu insbesondere beitragen durch:&lt;br /&gt;
&lt;br /&gt;
* Bereitstellung offener technischer Werkzeuge,&lt;br /&gt;
* Unterstützung bei Planung und Betrieb von Wasserinfrastruktur,&lt;br /&gt;
* Ausbildung lokaler Betreiber und Techniker,&lt;br /&gt;
* Aufbau lokaler technischer Fähigkeiten,&lt;br /&gt;
* Wissenstransfer,&lt;br /&gt;
* technische Dokumentation,&lt;br /&gt;
* Unterstützung gemeinnütziger und kommunaler Wasserprojekte,&lt;br /&gt;
* Verbesserung von Wartbarkeit und Betriebssicherheit,&lt;br /&gt;
* Unterstützung nachhaltiger Wasser- und Bewässerungsinfrastruktur.&lt;br /&gt;
&lt;br /&gt;
=== Wissenschaft und Forschung ===&lt;br /&gt;
&lt;br /&gt;
Die AOWIS gUG kann wissenschaftliche und technische Forschung durchführen oder fördern.&lt;br /&gt;
&lt;br /&gt;
Mögliche Bereiche sind insbesondere:&lt;br /&gt;
&lt;br /&gt;
* hydraulische Modellierung,&lt;br /&gt;
* Wasserqualität,&lt;br /&gt;
* Wasserverluste,&lt;br /&gt;
* Wasserressourcen,&lt;br /&gt;
* Hydrogeologie,&lt;br /&gt;
* Sensorik und Messverfahren,&lt;br /&gt;
* Telemetrie,&lt;br /&gt;
* Automatisierung,&lt;br /&gt;
* resilienter Infrastrukturbetrieb,&lt;br /&gt;
* Energieversorgung,&lt;br /&gt;
* Bewässerung,&lt;br /&gt;
* Datenmodelle und Modellkopplung.&lt;br /&gt;
&lt;br /&gt;
Forschungsergebnisse sollen grundsätzlich dokumentiert und öffentlich zugänglich gemacht werden.&lt;br /&gt;
&lt;br /&gt;
=== Erziehung, Volks- und Berufsbildung ===&lt;br /&gt;
&lt;br /&gt;
Die AOWIS gUG kann Bildungs- und Qualifizierungsangebote entwickeln und durchführen.&lt;br /&gt;
&lt;br /&gt;
Dazu können gehören:&lt;br /&gt;
&lt;br /&gt;
* Schulungen für Betreiber und Techniker,&lt;br /&gt;
* Workshops,&lt;br /&gt;
* technische Handbücher,&lt;br /&gt;
* Lernmaterialien,&lt;br /&gt;
* praktische Trainings,&lt;br /&gt;
* Weiterbildung für Ingenieure,&lt;br /&gt;
* Schulungen für Gemeinden und gemeinnützige Organisationen,&lt;br /&gt;
* Ausbildung im Umgang mit Modellierungs-, Simulations- und Monitoringwerkzeugen.&lt;br /&gt;
&lt;br /&gt;
=== Umweltschutz ===&lt;br /&gt;
&lt;br /&gt;
Die AOWIS gUG kann Projekte fördern oder durchführen, die insbesondere folgenden Zielen dienen:&lt;br /&gt;
&lt;br /&gt;
* nachhaltige Nutzung von Wasserressourcen,&lt;br /&gt;
* Verringerung von Wasserverlusten,&lt;br /&gt;
* effiziente Bewässerung,&lt;br /&gt;
* energieeffizienter Betrieb,&lt;br /&gt;
* Schutz von Grund- und Oberflächenwasser,&lt;br /&gt;
* Überwachung und Verbesserung der Wasserqualität,&lt;br /&gt;
* ressourcenschonende Infrastrukturplanung.&lt;br /&gt;
&lt;br /&gt;
== Vorschlag für den Gesellschaftszweck ==&lt;br /&gt;
&lt;br /&gt;
Der folgende Text ist ein Arbeitsentwurf für die weitere Abstimmung mit Finanzamt, Notar und gegebenenfalls steuerlicher oder rechtlicher Beratung.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
Zweck der Gesellschaft ist die Förderung der Entwicklungszusammenarbeit, die Förderung von Wissenschaft und Forschung, die Förderung der Erziehung, Volks- und Berufsbildung sowie die Förderung des Umweltschutzes.&lt;br /&gt;
&lt;br /&gt;
Die Gesellschaft verwirklicht ihre steuerbegünstigten Zwecke insbesondere durch die Entwicklung, Bereitstellung und Verbreitung offener technischer Grundlagen, Software, Dokumentation, Methoden und Bildungsangebote für die Planung, Modellierung, Errichtung, Überwachung, Steuerung, den Betrieb, die Wartung und die Weiterentwicklung von Wasser- und Bewässerungsinfrastruktur.&lt;br /&gt;
&lt;br /&gt;
Der Gesellschaftszweck wird insbesondere verwirklicht durch:&lt;br /&gt;
&lt;br /&gt;
1. die Entwicklung, Pflege und Veröffentlichung frei zugänglicher technischer Standards, Datenmodelle, Software und Referenzimplementierungen;&lt;br /&gt;
&lt;br /&gt;
2. die Erstellung und Veröffentlichung technischer Dokumentationen, Planungsunterlagen, Handbücher, Lehrmaterialien und Betriebsleitlinien;&lt;br /&gt;
&lt;br /&gt;
3. die Durchführung von Schulungen, Workshops, Qualifizierungsmaßnahmen und anderen Bildungsangeboten;&lt;br /&gt;
&lt;br /&gt;
4. die Durchführung und Unterstützung wissenschaftlicher Forschungs-, Entwicklungs- und Evaluierungsprojekte sowie die Veröffentlichung ihrer Ergebnisse;&lt;br /&gt;
&lt;br /&gt;
5. die Durchführung und Unterstützung von Pilot-, Demonstrations- und Entwicklungsprojekten im Bereich Wasser- und Bewässerungsinfrastruktur;&lt;br /&gt;
&lt;br /&gt;
6. die Förderung des Wissenstransfers und des Aufbaus lokaler technischer Fähigkeiten für Planung, Betrieb, Wartung und Weiterentwicklung von Wasserinfrastruktur;&lt;br /&gt;
&lt;br /&gt;
7. die Zusammenarbeit mit steuerbegünstigten Organisationen, Gemeinden, öffentlichen Stellen, Hochschulen, Forschungseinrichtungen und anderen geeigneten Projektpartnern;&lt;br /&gt;
&lt;br /&gt;
8. die Entwicklung und Verbreitung von Verfahren zur nachhaltigen Nutzung von Wasserressourcen, zur Verringerung von Wasserverlusten, zur Verbesserung der Wasserqualität sowie zur energie- und ressourceneffizienten Betriebsführung;&lt;br /&gt;
&lt;br /&gt;
9. die Dokumentation, Evaluation und Veröffentlichung praktischer Erfahrungen aus Planung, Bau, Betrieb und Wartung von Wasser- und Bewässerungsinfrastruktur.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
§ 60 AO verlangt, dass Satzungszwecke und die Art ihrer Verwirklichung so genau bestimmt werden, dass geprüft werden kann, ob die Voraussetzungen der Steuervergünstigung erfüllt sind.&amp;lt;ref name=&amp;quot;AO60&amp;quot;&amp;gt;https://www.gesetze-im-internet.de/ao_1977/__60.html&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Gemeinnützigkeitsrechtliche Anforderungen ==&lt;br /&gt;
&lt;br /&gt;
=== Selbstlosigkeit ===&lt;br /&gt;
&lt;br /&gt;
Die Gesellschaft muss selbstlos tätig sein und ihre Mittel für die satzungsmäßigen Zwecke verwenden.&amp;lt;ref name=&amp;quot;AO55&amp;quot;&amp;gt;https://www.gesetze-im-internet.de/ao_1977/__55.html&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Insbesondere:&lt;br /&gt;
&lt;br /&gt;
* erhalten Gesellschafter keine Gewinnanteile,&lt;br /&gt;
* dürfen keine unangemessenen Vergütungen oder sonstigen Begünstigungen gewährt werden,&lt;br /&gt;
* müssen Mittel für die steuerbegünstigten Zwecke verwendet werden,&lt;br /&gt;
* muss die Vermögensbindung bei Auflösung oder Wegfall steuerbegünstigter Zwecke sichergestellt sein.&lt;br /&gt;
&lt;br /&gt;
Angemessene Vergütungen für Geschäftsführung, Beschäftigte und externe Leistungen sind möglich.&lt;br /&gt;
&lt;br /&gt;
=== Ausschließlichkeit und Unmittelbarkeit ===&lt;br /&gt;
&lt;br /&gt;
Die Gesellschaft muss ihre steuerbegünstigten satzungsmäßigen Zwecke ausschließlich und unmittelbar verfolgen.&amp;lt;ref name=&amp;quot;AO56&amp;quot;&amp;gt;https://www.gesetze-im-internet.de/ao_1977/__56.html&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;AO57&amp;quot;&amp;gt;https://www.gesetze-im-internet.de/ao_1977/__57.html&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Dies kann insbesondere erfolgen durch:&lt;br /&gt;
&lt;br /&gt;
* eigene Softwareentwicklung,&lt;br /&gt;
* eigene Dokumentation,&lt;br /&gt;
* eigene Forschung,&lt;br /&gt;
* eigene Schulungen,&lt;br /&gt;
* eigene Pilot- und Entwicklungsprojekte,&lt;br /&gt;
* eigene Veröffentlichungen und Evaluationen.&lt;br /&gt;
&lt;br /&gt;
=== Vermögensbindung ===&lt;br /&gt;
&lt;br /&gt;
Die Vermögensbindung muss im Gesellschaftsvertrag entsprechend den gemeinnützigkeitsrechtlichen Vorgaben geregelt werden.&amp;lt;ref name=&amp;quot;AO61&amp;quot;&amp;gt;https://www.gesetze-im-internet.de/ao_1977/__61.html&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Die Formulierungen der Mustersatzung aus Anlage 1 zur AO sind dabei zu berücksichtigen.&amp;lt;ref name=&amp;quot;AOMuster&amp;quot;&amp;gt;https://www.gesetze-im-internet.de/ao_1977/anlage_1.html&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Tatsächliche Geschäftsführung ===&lt;br /&gt;
&lt;br /&gt;
Die tatsächliche Geschäftsführung muss den steuerbegünstigten Zwecken entsprechen.&amp;lt;ref name=&amp;quot;AO63&amp;quot;&amp;gt;https://www.gesetze-im-internet.de/ao_1977/__63.html&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Erforderlich sind insbesondere:&lt;br /&gt;
&lt;br /&gt;
* ordnungsgemäße Buchführung,&lt;br /&gt;
* dokumentierte Mittelverwendung,&lt;br /&gt;
* nachvollziehbare Projektabrechnung,&lt;br /&gt;
* dokumentierte Verträge,&lt;br /&gt;
* angemessene Vergütungen,&lt;br /&gt;
* nachvollziehbare Geschäfte mit Gesellschaftern oder verbundenen Unternehmen.&lt;br /&gt;
&lt;br /&gt;
== Gesellschaftsstruktur ==&lt;br /&gt;
&lt;br /&gt;
=== Gesellschafter ===&lt;br /&gt;
&lt;br /&gt;
Die Gesellschafter treffen die grundlegenden gesellschaftsrechtlichen Entscheidungen.&lt;br /&gt;
&lt;br /&gt;
Dazu gehören insbesondere:&lt;br /&gt;
&lt;br /&gt;
* Bestellung und Abberufung der Geschäftsführung,&lt;br /&gt;
* Änderungen des Gesellschaftsvertrags,&lt;br /&gt;
* grundlegende strategische Entscheidungen,&lt;br /&gt;
* Kapitalmaßnahmen,&lt;br /&gt;
* Feststellung des Jahresabschlusses.&lt;br /&gt;
&lt;br /&gt;
Eine Gesellschaft mit beschränkter Haftung kann durch eine oder mehrere Personen gegründet werden.&amp;lt;ref name=&amp;quot;GmbHG1&amp;quot;&amp;gt;https://www.gesetze-im-internet.de/gmbhg/__1.html&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Geschäftsführung ===&lt;br /&gt;
&lt;br /&gt;
Die Geschäftsführung führt die laufenden Geschäfte und vertritt die AOWIS gUG nach außen.&lt;br /&gt;
&lt;br /&gt;
Zu ihren Aufgaben gehören insbesondere:&lt;br /&gt;
&lt;br /&gt;
* operative Leitung,&lt;br /&gt;
* Finanzen,&lt;br /&gt;
* Personal,&lt;br /&gt;
* Verträge,&lt;br /&gt;
* Projekte,&lt;br /&gt;
* Fördermittel,&lt;br /&gt;
* Partnerschaften,&lt;br /&gt;
* technische Infrastruktur,&lt;br /&gt;
* Veröffentlichungen,&lt;br /&gt;
* Compliance,&lt;br /&gt;
* Kommunikation mit Behörden und Finanzamt.&lt;br /&gt;
&lt;br /&gt;
Die Gesellschaft muss mindestens einen Geschäftsführer haben.&amp;lt;ref name=&amp;quot;GmbHG6&amp;quot;&amp;gt;https://www.gesetze-im-internet.de/gmbhg/__6.html&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Finanzierung und wirtschaftliche Tätigkeiten ==&lt;br /&gt;
&lt;br /&gt;
Mögliche Einnahmen der AOWIS gUG sind insbesondere:&lt;br /&gt;
&lt;br /&gt;
* Spenden,&lt;br /&gt;
* Fördermittel,&lt;br /&gt;
* öffentliche Zuschüsse,&lt;br /&gt;
* Forschungsförderung,&lt;br /&gt;
* Projektfinanzierungen,&lt;br /&gt;
* zweckgebundene Zuwendungen,&lt;br /&gt;
* Einnahmen aus Schulungen,&lt;br /&gt;
* Forschungs- und Entwicklungsaufträge,&lt;br /&gt;
* technische Projektleistungen,&lt;br /&gt;
* Dienstleistungen,&lt;br /&gt;
* projektbezogene Verkäufe.&lt;br /&gt;
&lt;br /&gt;
Wirtschaftliche Tätigkeiten müssen ordnungsgemäß steuerlich eingeordnet und buchhalterisch erfasst werden.&lt;br /&gt;
&lt;br /&gt;
Je nach Tätigkeit kann es sich insbesondere um einen steuerbegünstigten Bereich, einen Zweckbetrieb oder einen steuerpflichtigen wirtschaftlichen Geschäftsbetrieb handeln.&amp;lt;ref name=&amp;quot;AO64&amp;quot;&amp;gt;https://www.gesetze-im-internet.de/ao_1977/__64.html&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;AO65&amp;quot;&amp;gt;https://www.gesetze-im-internet.de/ao_1977/__65.html&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Geschäfte mit Gesellschaftern oder verbundenen Unternehmen sollten besonders transparent dokumentiert werden.&lt;br /&gt;
&lt;br /&gt;
== Stammkapital und Rücklagen ==&lt;br /&gt;
&lt;br /&gt;
Für die Unternehmergesellschaft gelten die besonderen Regelungen des § 5a GmbHG.&amp;lt;ref name=&amp;quot;GmbHG5a&amp;quot;&amp;gt;https://www.gesetze-im-internet.de/gmbhg/__5a.html&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Vor der Anmeldung zum Handelsregister muss das Stammkapital vollständig eingezahlt sein.&lt;br /&gt;
&lt;br /&gt;
Sacheinlagen sind bei der Gründung ausgeschlossen.&lt;br /&gt;
&lt;br /&gt;
Ein Viertel des um einen Verlustvortrag verminderten Jahresüberschusses ist grundsätzlich in die gesetzliche Rücklage einzustellen.&amp;lt;ref name=&amp;quot;GmbHG5a&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Das tatsächliche Stammkapital sollte anhand des realistischen Finanzbedarfs der Anfangsphase festgelegt werden.&lt;br /&gt;
&lt;br /&gt;
Zu berücksichtigen sind insbesondere:&lt;br /&gt;
&lt;br /&gt;
* Gründungskosten,&lt;br /&gt;
* Buchhaltung,&lt;br /&gt;
* Versicherungen,&lt;br /&gt;
* Hosting und technische Infrastruktur,&lt;br /&gt;
* Personalkosten,&lt;br /&gt;
* Reisen,&lt;br /&gt;
* Projektvorfinanzierung,&lt;br /&gt;
* Hardware und Testsysteme.&lt;br /&gt;
&lt;br /&gt;
Gemeinnützige Körperschaften können außerdem unter den Voraussetzungen des § 62 AO Rücklagen bilden.&amp;lt;ref name=&amp;quot;AO62&amp;quot;&amp;gt;https://www.gesetze-im-internet.de/ao_1977/__62.html&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Gesellschaftsvertrag ==&lt;br /&gt;
&lt;br /&gt;
Der Gesellschaftsvertrag wird notariell beurkundet.&amp;lt;ref name=&amp;quot;GmbHG2&amp;quot;&amp;gt;https://www.gesetze-im-internet.de/gmbhg/__2.html&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Er muss insbesondere regeln:&lt;br /&gt;
&lt;br /&gt;
* Firma,&lt;br /&gt;
* Sitz,&lt;br /&gt;
* Unternehmensgegenstand,&lt;br /&gt;
* Stammkapital,&lt;br /&gt;
* Geschäftsanteile,&lt;br /&gt;
* steuerbegünstigte Zwecke,&lt;br /&gt;
* Art der Zweckverwirklichung,&lt;br /&gt;
* Selbstlosigkeit,&lt;br /&gt;
* Mittelverwendung,&lt;br /&gt;
* Vermögensbindung.&lt;br /&gt;
&lt;br /&gt;
Die gemeinnützigkeitsrechtlichen Formulierungen sollten vor der Beurkundung mit dem zuständigen Finanzamt abgestimmt werden.&lt;br /&gt;
&lt;br /&gt;
== Gründungsschritte ==&lt;br /&gt;
&lt;br /&gt;
=== 1. Grundstruktur festlegen ===&lt;br /&gt;
&lt;br /&gt;
Festzulegen sind:&lt;br /&gt;
&lt;br /&gt;
* endgültige Firma,&lt;br /&gt;
* Sitz,&lt;br /&gt;
* Gesellschafter,&lt;br /&gt;
* Geschäftsführung,&lt;br /&gt;
* Stammkapital,&lt;br /&gt;
* Geschäftsanteile,&lt;br /&gt;
* gemeinnützige Zwecke,&lt;br /&gt;
* Unternehmensgegenstand.&lt;br /&gt;
&lt;br /&gt;
=== 2. Gesellschaftsvertrag entwerfen ===&lt;br /&gt;
&lt;br /&gt;
Der Gesellschaftsvertrag wird auf Grundlage der geplanten Tätigkeit und der gemeinnützigkeitsrechtlichen Anforderungen erstellt.&lt;br /&gt;
&lt;br /&gt;
=== 3. Vorabstimmung mit dem Finanzamt ===&lt;br /&gt;
&lt;br /&gt;
Der Entwurf sollte vor der notariellen Gründung dem zuständigen Finanzamt zur Prüfung vorgelegt werden.&lt;br /&gt;
&lt;br /&gt;
Zu prüfen sind insbesondere:&lt;br /&gt;
&lt;br /&gt;
* steuerbegünstigte Zwecke,&lt;br /&gt;
* Zweckverwirklichung,&lt;br /&gt;
* Selbstlosigkeit,&lt;br /&gt;
* Mittelverwendung,&lt;br /&gt;
* Vermögensbindung.&lt;br /&gt;
&lt;br /&gt;
Die Feststellung der satzungsmäßigen Voraussetzungen richtet sich nach § 60a AO.&amp;lt;ref name=&amp;quot;AO60a&amp;quot;&amp;gt;https://www.gesetze-im-internet.de/ao_1977/__60a.html&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== 4. Notarielle Gründung ===&lt;br /&gt;
&lt;br /&gt;
Der Gesellschaftsvertrag wird notariell beurkundet und die Geschäftsführung bestellt.&lt;br /&gt;
&lt;br /&gt;
=== 5. Geschäftskonto und Stammkapital ===&lt;br /&gt;
&lt;br /&gt;
Ein Geschäftskonto wird eröffnet und das Stammkapital eingezahlt.&lt;br /&gt;
&lt;br /&gt;
=== 6. Handelsregister ===&lt;br /&gt;
&lt;br /&gt;
Die Gesellschaft wird über den Notar zur Eintragung in das Handelsregister angemeldet.&lt;br /&gt;
&lt;br /&gt;
=== 7. Steuerliche Erfassung ===&lt;br /&gt;
&lt;br /&gt;
Anschließend erfolgen die steuerliche Erfassung und die weitere Abstimmung zur Gemeinnützigkeit.&lt;br /&gt;
&lt;br /&gt;
=== 8. Geschäftsbetrieb aufsetzen ===&lt;br /&gt;
&lt;br /&gt;
Erforderlich sind insbesondere:&lt;br /&gt;
&lt;br /&gt;
* Buchhaltung,&lt;br /&gt;
* Geschäftskonto,&lt;br /&gt;
* Versicherungen,&lt;br /&gt;
* Projektverwaltung,&lt;br /&gt;
* Fördermittelverwaltung,&lt;br /&gt;
* Spendenverwaltung,&lt;br /&gt;
* Vertragsgrundlagen,&lt;br /&gt;
* Datenschutz,&lt;br /&gt;
* Dokumentation der Mittelverwendung.&lt;br /&gt;
&lt;br /&gt;
== Schutz der langfristigen Ausrichtung ==&lt;br /&gt;
&lt;br /&gt;
Im Gesellschaftsvertrag sollte geprüft werden, wie die langfristige gemeinnützige und offene Ausrichtung von AOWIS abgesichert werden kann.&lt;br /&gt;
&lt;br /&gt;
Relevant sind insbesondere:&lt;br /&gt;
&lt;br /&gt;
* Übertragung von Geschäftsanteilen,&lt;br /&gt;
* Zustimmungsvorbehalte bei Anteilsübertragungen,&lt;br /&gt;
* Änderungen des Gesellschaftszwecks,&lt;br /&gt;
* Interessenkonflikte,&lt;br /&gt;
* Vermögensbindung.&lt;br /&gt;
&lt;br /&gt;
Die Übertragung von Geschäftsanteilen kann im Gesellschaftsvertrag von zusätzlichen Voraussetzungen abhängig gemacht werden.&amp;lt;ref name=&amp;quot;GmbHG15&amp;quot;&amp;gt;https://www.gesetze-im-internet.de/gmbhg/__15.html&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Internationale Zusammenarbeit ==&lt;br /&gt;
&lt;br /&gt;
Die AOWIS gUG soll ihren Sitz in Deutschland haben und international tätig sein können.&lt;br /&gt;
&lt;br /&gt;
Bei Projekten sollen lokale Betreiber, Techniker, Gemeinden und andere Beteiligte frühzeitig einbezogen werden.&lt;br /&gt;
&lt;br /&gt;
Relevant sind dabei insbesondere:&lt;br /&gt;
&lt;br /&gt;
* vorhandene Infrastruktur,&lt;br /&gt;
* lokale Wasserressourcen,&lt;br /&gt;
* Hydrogeologie,&lt;br /&gt;
* Energieversorgung,&lt;br /&gt;
* Kommunikationsinfrastruktur,&lt;br /&gt;
* Wartungsmöglichkeiten,&lt;br /&gt;
* Ersatzteilverfügbarkeit,&lt;br /&gt;
* lokale technische Fähigkeiten,&lt;br /&gt;
* tatsächliche Betriebsabläufe.&lt;br /&gt;
&lt;br /&gt;
Ziel ist der Aufbau langfristig nutzbarer technischer Fähigkeiten und Infrastruktur.&lt;br /&gt;
&lt;br /&gt;
== Risiken ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Risiko&lt;br /&gt;
! Gegenmaßnahme&lt;br /&gt;
|-&lt;br /&gt;
| Unklare gemeinnützige Zwecksetzung&lt;br /&gt;
| Zwecke und konkrete Zweckverwirklichung präzise formulieren und vorab mit dem Finanzamt abstimmen.&lt;br /&gt;
|-&lt;br /&gt;
| Vermischung mit privaten wirtschaftlichen Interessen&lt;br /&gt;
| Interessenkonflikte offenlegen und Geschäfte mit Gesellschaftern oder verbundenen Unternehmen dokumentieren.&lt;br /&gt;
|-&lt;br /&gt;
| Fehlerhafte Einordnung wirtschaftlicher Tätigkeiten&lt;br /&gt;
| Tätigkeiten steuerlich prüfen und buchhalterisch sauber trennen.&lt;br /&gt;
|-&lt;br /&gt;
| Unzureichende Dokumentation&lt;br /&gt;
| Verträge, Projektakten, Buchhaltung und Mittelverwendung nachvollziehbar dokumentieren.&lt;br /&gt;
|-&lt;br /&gt;
| Zu geringes Anfangskapital&lt;br /&gt;
| Stammkapital und Finanzierung anhand einer realistischen Liquiditätsplanung festlegen.&lt;br /&gt;
|-&lt;br /&gt;
| Unklare Rechte an Software, Dokumentation und Marken&lt;br /&gt;
| Rechte, Lizenzen und Zuständigkeiten frühzeitig dokumentieren.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Nächste Schritte ==&lt;br /&gt;
&lt;br /&gt;
# Gesellschafter und Geschäftsführung festlegen.&lt;br /&gt;
# Sitz und endgültige Firma festlegen.&lt;br /&gt;
# Stammkapital und Geschäftsanteile festlegen.&lt;br /&gt;
# Gemeinnützige Zwecke endgültig auswählen.&lt;br /&gt;
# Gesellschaftszweck und Zweckverwirklichung ausformulieren.&lt;br /&gt;
# Gesellschaftsvertrag entwerfen.&lt;br /&gt;
# Entwurf mit dem Finanzamt abstimmen.&lt;br /&gt;
# Finanzplan für die ersten zwölf Monate erstellen.&lt;br /&gt;
# Bestehende AOWIS-Ressourcen und Rechte erfassen.&lt;br /&gt;
# Notarielle Gründung vorbereiten.&lt;br /&gt;
&lt;br /&gt;
== Kurzbeschreibung ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
Die AOWIS gUG ist die gemeinnützige Trägerorganisation des Afritic Open Water Infrastructure System (AOWIS).&lt;br /&gt;
&lt;br /&gt;
Sie entwickelt und verbreitet Open-Source-Software, technische Standards, Datenmodelle, Dokumentation, Engineering-Methoden und Bildungsangebote für Wasser- und Bewässerungsinfrastruktur.&lt;br /&gt;
&lt;br /&gt;
Schwerpunkte sind Entwicklungszusammenarbeit, Ausbildung, Forschung, Wissenstransfer sowie die Entwicklung sicherer, nachhaltiger und langfristig betreibbarer Wasserinfrastruktur.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Quellen ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Kategorie:AOWIS]]&lt;br /&gt;
[[Kategorie:gUG]]&lt;br /&gt;
[[Kategorie:Gemeinnützigkeit]]&lt;br /&gt;
[[Kategorie:Entwicklungszusammenarbeit]]&lt;/div&gt;</summary>
		<author><name>Samuel</name></author>
	</entry>
	<entry>
		<id>https://aowis.org/index.php?title=Governance:Non-Profit-Association&amp;diff=788</id>
		<title>Governance:Non-Profit-Association</title>
		<link rel="alternate" type="text/html" href="https://aowis.org/index.php?title=Governance:Non-Profit-Association&amp;diff=788"/>
		<updated>2026-10-05T12:44:06Z</updated>

		<summary type="html">&lt;p&gt;Samuel: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{AI-Generated&lt;br /&gt;
 | tool=ChatGPT&lt;br /&gt;
 | date=2026-10-05&lt;br /&gt;
 | scope=full page&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
= Konzept zur Gründung der AOWIS gUG =&lt;br /&gt;
&lt;br /&gt;
== Kurzfassung ==&lt;br /&gt;
&lt;br /&gt;
Für die langfristige institutionelle und gemeinnützige Trägerschaft von &#039;&#039;&#039;AOWIS (Afritic Open Water Infrastructure System)&#039;&#039;&#039; ist die Gründung einer &#039;&#039;&#039;gemeinnützigen Unternehmergesellschaft (gUG)&#039;&#039;&#039; vorgesehen.&lt;br /&gt;
&lt;br /&gt;
AOWIS ist ein offenes System für die Planung, den Entwurf, die Modellierung, den Bau, den Betrieb, die Überwachung, die Wartung und die Weiterentwicklung sicherer und zuverlässiger Wasser- und Bewässerungsinfrastruktur über deren gesamten Lebenszyklus.&amp;lt;ref name=&amp;quot;AOWISMain&amp;quot;&amp;gt;https://aowis.org/index.php/Main_Page&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Das Projekt verbindet unter anderem:&lt;br /&gt;
&lt;br /&gt;
* offene technische Standards,&lt;br /&gt;
* Open-Source-Software,&lt;br /&gt;
* gemeinsame Infrastrukturmodelle,&lt;br /&gt;
* Engineering-Methoden,&lt;br /&gt;
* Modellierung und Simulation,&lt;br /&gt;
* Monitoring und Steuerung,&lt;br /&gt;
* Referenzimplementierungen,&lt;br /&gt;
* Betriebs- und Wartungswissen,&lt;br /&gt;
* technische Dokumentation,&lt;br /&gt;
* Forschung und Evaluation,&lt;br /&gt;
* Ausbildung und Wissenstransfer.&lt;br /&gt;
&lt;br /&gt;
Die &#039;&#039;&#039;AOWIS gUG&#039;&#039;&#039; soll als rechtliche und organisatorische Trägerin dieses offenen Systems dienen. Sie soll insbesondere die langfristige Entwicklung und Verfügbarkeit von AOWIS sichern, gemeinnützige Projekte durchführen, Wissen offen zugänglich machen, Bildungsangebote entwickeln und den Einsatz geeigneter technischer Methoden und Werkzeuge in der Entwicklungszusammenarbeit fördern.&lt;br /&gt;
&lt;br /&gt;
Als zentraler gemeinnütziger Zweck bietet sich die &#039;&#039;&#039;Förderung der Entwicklungszusammenarbeit&#039;&#039;&#039; gemäß § 52 Abs. 2 Nr. 15 AO an.&amp;lt;ref name=&amp;quot;AO52&amp;quot;&amp;gt;https://www.gesetze-im-internet.de/ao_1977/__52.html&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Ergänzend kommen insbesondere in Betracht:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Förderung von Wissenschaft und Forschung&#039;&#039;&#039; gemäß § 52 Abs. 2 Nr. 1 AO,&lt;br /&gt;
* &#039;&#039;&#039;Förderung der Erziehung, Volks- und Berufsbildung&#039;&#039;&#039; gemäß § 52 Abs. 2 Nr. 7 AO,&lt;br /&gt;
* &#039;&#039;&#039;Förderung des Umweltschutzes&#039;&#039;&#039; gemäß § 52 Abs. 2 Nr. 8 AO.&lt;br /&gt;
&lt;br /&gt;
Welche dieser Zwecke tatsächlich in den Gesellschaftsvertrag aufgenommen werden, sollte sich an den dauerhaft geplanten Tätigkeiten der gUG orientieren.&lt;br /&gt;
&lt;br /&gt;
Die endgültige Formulierung des Gesellschaftsvertrags sollte vor der Gründung mit dem zuständigen Finanzamt abgestimmt und rechtlich beziehungsweise steuerlich geprüft werden.&lt;br /&gt;
&lt;br /&gt;
== AOWIS und die AOWIS gUG ==&lt;br /&gt;
&lt;br /&gt;
AOWIS und die AOWIS gUG sind voneinander zu unterscheiden.&lt;br /&gt;
&lt;br /&gt;
=== AOWIS ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;AOWIS&#039;&#039;&#039; bezeichnet das offene technische und organisatorische System.&lt;br /&gt;
&lt;br /&gt;
AOWIS soll eine gemeinsame Grundlage für Wasser- und Bewässerungsinfrastruktur über deren gesamten Lebenszyklus schaffen:&lt;br /&gt;
&lt;br /&gt;
: &#039;&#039;&#039;Erfassung und Planung → Engineering und Simulation → Bau → Inbetriebnahme → Monitoring → Steuerung → Wartung → Analyse → Erweiterung&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
AOWIS ist dabei nicht ausschließlich auf Entwicklungsprojekte oder ressourcenarme Regionen beschränkt.&lt;br /&gt;
&lt;br /&gt;
Die Standards, Software, Datenmodelle, Engineering-Methoden und Betriebsverfahren sollen grundsätzlich überall eingesetzt werden können, wo Wasser- und Bewässerungsinfrastruktur geplant, modelliert, betrieben oder weiterentwickelt wird.&lt;br /&gt;
&lt;br /&gt;
Ein besonderer Entwicklungsfokus liegt jedoch auf Umgebungen, in denen übliche technische oder organisatorische Voraussetzungen nicht zuverlässig vorhanden sind.&lt;br /&gt;
&lt;br /&gt;
Dazu gehören beispielsweise:&lt;br /&gt;
&lt;br /&gt;
* instabile oder begrenzte Stromversorgung,&lt;br /&gt;
* zeitweise oder vollständig fehlende Internetverbindung,&lt;br /&gt;
* heterogene oder ältere technische Anlagen,&lt;br /&gt;
* begrenzte Verfügbarkeit ausgebildeter Fachkräfte,&lt;br /&gt;
* eingeschränkter Zugang zu spezialisierter Engineering-Unterstützung,&lt;br /&gt;
* Bedarf an sicherem lokalem und autonomem Betrieb,&lt;br /&gt;
* begrenzte finanzielle und technische Ressourcen.&lt;br /&gt;
&lt;br /&gt;
AOWIS berücksichtigt diese Bedingungen unter anderem durch:&lt;br /&gt;
&lt;br /&gt;
* Offline-First-Betrieb,&lt;br /&gt;
* lokale autonome Betriebsfähigkeit,&lt;br /&gt;
* sichere Rückfallmechanismen,&lt;br /&gt;
* Human-in-the-Loop-Kontrolle,&lt;br /&gt;
* modulare und erweiterbare Architektur,&lt;br /&gt;
* gemeinsame Infrastrukturmodelle,&lt;br /&gt;
* offene Schnittstellen,&lt;br /&gt;
* zugängliche technische Dokumentation.&lt;br /&gt;
&lt;br /&gt;
AOWIS enthält außerdem eine Open-Source-Softwareplattform für Modellierung, Simulation, Visualisierung, Monitoring und Betrieb von Wasserinfrastruktur.&amp;lt;ref name=&amp;quot;AOWISMain&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== AOWIS gUG ===&lt;br /&gt;
&lt;br /&gt;
Die &#039;&#039;&#039;AOWIS gUG&#039;&#039;&#039; ist die geplante gemeinnützige Organisation, die AOWIS institutionell trägt.&lt;br /&gt;
&lt;br /&gt;
Zu ihren Aufgaben können insbesondere gehören:&lt;br /&gt;
&lt;br /&gt;
* Entwicklung, Pflege und Veröffentlichung von AOWIS-Software,&lt;br /&gt;
* Entwicklung und Pflege offener technischer Standards,&lt;br /&gt;
* Entwicklung und Dokumentation gemeinsamer Daten- und Infrastrukturmodelle,&lt;br /&gt;
* Erstellung technischer Dokumentation,&lt;br /&gt;
* Durchführung und Unterstützung von Forschung,&lt;br /&gt;
* Entwicklung von Schulungs- und Ausbildungsmaterialien,&lt;br /&gt;
* Durchführung von Workshops und Trainings,&lt;br /&gt;
* Unterstützung von Entwicklungsprojekten,&lt;br /&gt;
* Durchführung von Pilot- und Demonstrationsprojekten,&lt;br /&gt;
* technische Evaluation und Qualitätssicherung,&lt;br /&gt;
* Aufbau und Pflege technischer Wissensbestände,&lt;br /&gt;
* Zusammenarbeit mit Gemeinden, Versorgungsunternehmen, NGOs, Hochschulen, Forschungseinrichtungen und öffentlichen Stellen,&lt;br /&gt;
* Förderung des Austauschs zwischen lokalen und internationalen Fachkräften,&lt;br /&gt;
* langfristige Sicherung der offenen Verfügbarkeit und Weiterentwicklung von AOWIS.&lt;br /&gt;
&lt;br /&gt;
Die gUG soll damit nicht lediglich eine Verwaltungsorganisation für einen technischen Standard sein.&lt;br /&gt;
&lt;br /&gt;
Sie kann die organisatorische Trägerin des gesamten AOWIS-Systems einschließlich Software, Standards, Dokumentation, Forschung, Ausbildung und praktischer Projekte sein.&lt;br /&gt;
&lt;br /&gt;
== Warum eine gUG? ==&lt;br /&gt;
&lt;br /&gt;
AOWIS benötigt perspektivisch eine Organisation, die selbst rechtsfähig handeln und langfristige Verantwortung übernehmen kann.&lt;br /&gt;
&lt;br /&gt;
Eine gUG bietet hierfür insbesondere die Möglichkeit:&lt;br /&gt;
&lt;br /&gt;
* Verträge abzuschließen,&lt;br /&gt;
* Personal zu beschäftigen,&lt;br /&gt;
* Fördermittel zu beantragen und zu verwalten,&lt;br /&gt;
* Spenden und andere Zuwendungen entgegenzunehmen,&lt;br /&gt;
* Projektmittel zu verwalten,&lt;br /&gt;
* Software und technische Dokumentation zu entwickeln und zu veröffentlichen,&lt;br /&gt;
* Rechte und Vermögenswerte zu halten,&lt;br /&gt;
* Infrastruktur und technische Systeme zu betreiben,&lt;br /&gt;
* Forschungs- und Entwicklungsprojekte durchzuführen,&lt;br /&gt;
* Bildungsangebote durchzuführen,&lt;br /&gt;
* mit öffentlichen und privaten Partnern zusammenzuarbeiten,&lt;br /&gt;
* internationale Projekte organisatorisch zu tragen.&lt;br /&gt;
&lt;br /&gt;
Anders als bei einem eingetragenen Verein ist keine mitgliederbasierte Organisationsstruktur erforderlich.&lt;br /&gt;
&lt;br /&gt;
Gesellschaftsrechtlich bestehen insbesondere:&lt;br /&gt;
&lt;br /&gt;
* ein oder mehrere Gesellschafter,&lt;br /&gt;
* eine Gesellschafterversammlung,&lt;br /&gt;
* ein oder mehrere Geschäftsführer.&lt;br /&gt;
&lt;br /&gt;
Eine Gesellschaft mit beschränkter Haftung kann grundsätzlich durch eine oder mehrere Personen gegründet werden.&amp;lt;ref name=&amp;quot;GmbHG1&amp;quot;&amp;gt;https://www.gesetze-im-internet.de/gmbhg/__1.html&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Die Gesellschaft muss einen oder mehrere Geschäftsführer haben.&amp;lt;ref name=&amp;quot;GmbHG6&amp;quot;&amp;gt;https://www.gesetze-im-internet.de/gmbhg/__6.html&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Damit ist eine vergleichsweise klare operative Verantwortungsstruktur möglich.&lt;br /&gt;
&lt;br /&gt;
== Gemeinnützige Zwecke ==&lt;br /&gt;
&lt;br /&gt;
=== Entwicklungszusammenarbeit ===&lt;br /&gt;
&lt;br /&gt;
Als zentraler gemeinnütziger Zweck wird die &#039;&#039;&#039;Förderung der Entwicklungszusammenarbeit&#039;&#039;&#039; empfohlen.&lt;br /&gt;
&lt;br /&gt;
Dieser Zweck ist ausdrücklich in § 52 Abs. 2 Nr. 15 AO genannt.&amp;lt;ref name=&amp;quot;AO52&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
AOWIS kann zur Entwicklungszusammenarbeit insbesondere beitragen durch:&lt;br /&gt;
&lt;br /&gt;
* Verbesserung des Zugangs zu Engineering-Wissen,&lt;br /&gt;
* Bereitstellung frei zugänglicher technischer Werkzeuge,&lt;br /&gt;
* Unterstützung bei Planung und Betrieb von Wasserinfrastruktur,&lt;br /&gt;
* Ausbildung lokaler Betreiber und Techniker,&lt;br /&gt;
* Aufbau lokaler technischer Fähigkeiten,&lt;br /&gt;
* Wissenstransfer,&lt;br /&gt;
* Unterstützung gemeinnütziger und kommunaler Wasserprojekte,&lt;br /&gt;
* Verbesserung langfristiger Wartbarkeit,&lt;br /&gt;
* Verbesserung technischer Dokumentation,&lt;br /&gt;
* Aufbau nachhaltiger Betriebsstrukturen,&lt;br /&gt;
* Unterstützung sicherer und resilienter Wasser- und Bewässerungssysteme.&lt;br /&gt;
&lt;br /&gt;
Der Schwerpunkt liegt dabei nicht allein auf der Bereitstellung von Technik.&lt;br /&gt;
&lt;br /&gt;
Langfristig funktionierende Infrastruktur benötigt ebenfalls:&lt;br /&gt;
&lt;br /&gt;
* Wissen,&lt;br /&gt;
* Ausbildung,&lt;br /&gt;
* Dokumentation,&lt;br /&gt;
* Betriebsverfahren,&lt;br /&gt;
* Wartungsfähigkeit,&lt;br /&gt;
* nachvollziehbare technische Entscheidungen,&lt;br /&gt;
* geeignete Software und Daten,&lt;br /&gt;
* lokale technische Kompetenz.&lt;br /&gt;
&lt;br /&gt;
=== Wissenschaft und Forschung ===&lt;br /&gt;
&lt;br /&gt;
Die &#039;&#039;&#039;Förderung von Wissenschaft und Forschung&#039;&#039;&#039; ist gemäß § 52 Abs. 2 Nr. 1 AO ein anerkannter gemeinnütziger Zweck.&amp;lt;ref name=&amp;quot;AO52&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Dieser Zweck kann für AOWIS relevant sein, soweit die gUG tatsächlich wissenschaftliche oder methodisch nachvollziehbare Forschungsarbeit betreibt oder unterstützt.&lt;br /&gt;
&lt;br /&gt;
Mögliche Forschungsbereiche sind beispielsweise:&lt;br /&gt;
&lt;br /&gt;
* hydraulische Modellierung,&lt;br /&gt;
* Wasserqualität,&lt;br /&gt;
* Wasserverluste,&lt;br /&gt;
* Wasserressourcen,&lt;br /&gt;
* Hydrogeologie,&lt;br /&gt;
* Messverfahren,&lt;br /&gt;
* Sensorik,&lt;br /&gt;
* Telemetrie,&lt;br /&gt;
* Automatisierung,&lt;br /&gt;
* resilienter Infrastrukturbetrieb,&lt;br /&gt;
* technische Verfahren unter schwierigen Einsatzbedingungen,&lt;br /&gt;
* Energieversorgung von Wasserinfrastruktur,&lt;br /&gt;
* Bewässerung,&lt;br /&gt;
* Datenmodelle,&lt;br /&gt;
* Modellkopplung,&lt;br /&gt;
* modellgestützte Betriebsführung.&lt;br /&gt;
&lt;br /&gt;
Forschungsergebnisse sollten grundsätzlich dokumentiert und der Allgemeinheit zugänglich gemacht werden, soweit dem keine berechtigten Schutzinteressen entgegenstehen.&lt;br /&gt;
&lt;br /&gt;
Der Forschungszweck sollte nur aufgenommen werden, wenn entsprechende Tätigkeiten tatsächlich vorgesehen sind und dauerhaft verfolgt werden sollen.&lt;br /&gt;
&lt;br /&gt;
=== Erziehung, Volks- und Berufsbildung ===&lt;br /&gt;
&lt;br /&gt;
Die &#039;&#039;&#039;Förderung der Erziehung, Volks- und Berufsbildung&#039;&#039;&#039; ist gemäß § 52 Abs. 2 Nr. 7 AO als gemeinnütziger Zweck anerkannt.&amp;lt;ref name=&amp;quot;AO52&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Dieser Bereich passt unmittelbar zu den Ausbildungs- und Wissenstransferzielen von AOWIS.&lt;br /&gt;
&lt;br /&gt;
Mögliche Tätigkeiten sind:&lt;br /&gt;
&lt;br /&gt;
* Ausbildung lokaler Betreiber,&lt;br /&gt;
* technische Schulungen,&lt;br /&gt;
* Workshops,&lt;br /&gt;
* praktische Übungen,&lt;br /&gt;
* Online-Schulungsmaterialien,&lt;br /&gt;
* technische Handbücher,&lt;br /&gt;
* Lernmodule,&lt;br /&gt;
* Schulungen für NGOs und Gemeinden,&lt;br /&gt;
* Weiterbildung von Technikern und Ingenieuren,&lt;br /&gt;
* Ausbildung im Umgang mit Modellierungs- und Simulationswerkzeugen,&lt;br /&gt;
* Schulung für Monitoring und Anlagenbetrieb,&lt;br /&gt;
* Vermittlung grundlegender Engineering-Prinzipien.&lt;br /&gt;
&lt;br /&gt;
=== Umweltschutz ===&lt;br /&gt;
&lt;br /&gt;
Die &#039;&#039;&#039;Förderung des Umweltschutzes&#039;&#039;&#039; ist gemäß § 52 Abs. 2 Nr. 8 AO als gemeinnütziger Zweck anerkannt.&amp;lt;ref name=&amp;quot;AO52&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Für AOWIS kann dieser Zweck insbesondere relevant sein, wenn Projekte beispielsweise auf folgende Ziele ausgerichtet sind:&lt;br /&gt;
&lt;br /&gt;
* nachhaltige Nutzung von Wasserressourcen,&lt;br /&gt;
* Verringerung von Wasserverlusten,&lt;br /&gt;
* effiziente Bewässerung,&lt;br /&gt;
* energieeffizienten Betrieb,&lt;br /&gt;
* Schutz von Grund- und Oberflächenwasser,&lt;br /&gt;
* bessere Überwachung von Wasserqualität,&lt;br /&gt;
* ressourcenschonende Infrastrukturplanung,&lt;br /&gt;
* klimatisch resiliente Wasserinfrastruktur.&lt;br /&gt;
&lt;br /&gt;
Nicht jede technische Tätigkeit von AOWIS ist automatisch Umweltschutz.&lt;br /&gt;
&lt;br /&gt;
Die tatsächlichen Projekte müssen dem steuerbegünstigten Zweck konkret dienen.&lt;br /&gt;
&lt;br /&gt;
== Technische Zusammenarbeit ==&lt;br /&gt;
&lt;br /&gt;
Internationale oder lokale technische Zusammenarbeit ist kein eigener gemeinnütziger Zweck dieses Konzepts.&lt;br /&gt;
&lt;br /&gt;
Sie ist vielmehr ein wichtiges Mittel zur Verwirklichung insbesondere der Entwicklungszusammenarbeit, der Bildung und gegebenenfalls von Wissenschaft und Forschung.&lt;br /&gt;
&lt;br /&gt;
Die AOWIS gUG kann beispielsweise zusammenarbeiten mit:&lt;br /&gt;
&lt;br /&gt;
* lokalen Initiativen,&lt;br /&gt;
* Gemeinden,&lt;br /&gt;
* Wasserverbänden,&lt;br /&gt;
* Wasserversorgern,&lt;br /&gt;
* NGOs,&lt;br /&gt;
* gemeinnützigen Organisationen,&lt;br /&gt;
* Hochschulen,&lt;br /&gt;
* Forschungseinrichtungen,&lt;br /&gt;
* Schulen und Ausbildungsstätten,&lt;br /&gt;
* Ingenieuren und Technikern,&lt;br /&gt;
* öffentlichen Stellen,&lt;br /&gt;
* internationalen Organisationen,&lt;br /&gt;
* geeigneten Unternehmen und technischen Partnern.&lt;br /&gt;
&lt;br /&gt;
Die Zusammenarbeit mit Unternehmen ist grundsätzlich nicht ausgeschlossen.&lt;br /&gt;
&lt;br /&gt;
Sie darf jedoch die gemeinnützige Zielsetzung der gUG nicht in den Hintergrund drängen oder zu einer unangemessenen Förderung einzelner Unternehmen führen.&lt;br /&gt;
&lt;br /&gt;
== Vorschlag für den Gesellschaftszweck ==&lt;br /&gt;
&lt;br /&gt;
Der folgende Text ist ein &#039;&#039;&#039;Arbeitsentwurf&#039;&#039;&#039; und ausdrücklich noch keine endgültige Formulierung für den notariellen Gesellschaftsvertrag.&lt;br /&gt;
&lt;br /&gt;
Vor Verwendung sollte er mit dem zuständigen Finanzamt sowie gegebenenfalls mit steuerlicher und rechtlicher Beratung abgestimmt werden.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
Zweck der Gesellschaft ist die Förderung der Entwicklungszusammenarbeit, die Förderung von Wissenschaft und Forschung, die Förderung der Erziehung, Volks- und Berufsbildung sowie die Förderung des Umweltschutzes.&lt;br /&gt;
&lt;br /&gt;
Die Gesellschaft verwirklicht ihre steuerbegünstigten Zwecke insbesondere durch die Entwicklung, Bereitstellung und Verbreitung offener technischer Grundlagen, Software, Dokumentation, Methoden und Bildungsangebote für die Planung, Modellierung, Errichtung, Überwachung, Steuerung, den Betrieb, die Wartung und die Weiterentwicklung von Wasser- und Bewässerungsinfrastruktur.&lt;br /&gt;
&lt;br /&gt;
Der Gesellschaftszweck wird insbesondere verwirklicht durch:&lt;br /&gt;
&lt;br /&gt;
1. die Entwicklung, Pflege und Veröffentlichung frei zugänglicher technischer Standards, Datenmodelle, Software und Referenzimplementierungen;&lt;br /&gt;
&lt;br /&gt;
2. die Erstellung und Veröffentlichung von technischen Dokumentationen, Planungsunterlagen, Handbüchern, Lehrmaterialien und Betriebsleitlinien;&lt;br /&gt;
&lt;br /&gt;
3. die Durchführung von Schulungen, Workshops, Qualifizierungsmaßnahmen und anderen Bildungsangeboten für Betreiber, Techniker, Ingenieure, Studierende, gemeinnützige Organisationen, Gemeinden und andere Beteiligte;&lt;br /&gt;
&lt;br /&gt;
4. die Durchführung und Unterstützung wissenschaftlicher Forschungs-, Entwicklungs- und Evaluierungsprojekte sowie die Veröffentlichung ihrer Ergebnisse;&lt;br /&gt;
&lt;br /&gt;
5. die Durchführung und Unterstützung von Pilot-, Demonstrations- und Entwicklungsprojekten im Bereich Wasser- und Bewässerungsinfrastruktur;&lt;br /&gt;
&lt;br /&gt;
6. die Förderung des Wissenstransfers und des Aufbaus lokaler technischer Fähigkeiten für Planung, Betrieb, Wartung und Weiterentwicklung von Wasserinfrastruktur;&lt;br /&gt;
&lt;br /&gt;
7. die Zusammenarbeit mit steuerbegünstigten Organisationen, Gemeinden, öffentlichen Stellen, Hochschulen, Forschungseinrichtungen und anderen geeigneten Projektpartnern;&lt;br /&gt;
&lt;br /&gt;
8. die Entwicklung und Verbreitung von Verfahren zur nachhaltigen Nutzung von Wasserressourcen, zur Verringerung von Wasserverlusten, zur Verbesserung der Wasserqualität sowie zur energie- und ressourceneffizienten Betriebsführung;&lt;br /&gt;
&lt;br /&gt;
9. die Dokumentation, Evaluation und Veröffentlichung praktischer Erfahrungen aus Planung, Bau, Betrieb und Wartung von Wasser- und Bewässerungsinfrastruktur.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Die Aufnahme mehrerer gemeinnütziger Zwecke ist nur sinnvoll, wenn diese tatsächlich verfolgt werden.&lt;br /&gt;
&lt;br /&gt;
Der endgültige Gesellschaftsvertrag sollte möglichst präzise beschreiben, durch welche konkreten Tätigkeiten die jeweiligen steuerbegünstigten Zwecke verwirklicht werden.&lt;br /&gt;
&lt;br /&gt;
§ 60 AO verlangt, dass Satzungszwecke und die Art ihrer Verwirklichung so genau bestimmt werden, dass geprüft werden kann, ob die Voraussetzungen der Steuervergünstigung erfüllt sind.&amp;lt;ref name=&amp;quot;AO60&amp;quot;&amp;gt;https://www.gesetze-im-internet.de/ao_1977/__60.html&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Gemeinnützigkeitsrechtliche Anforderungen ==&lt;br /&gt;
&lt;br /&gt;
Die AOWIS gUG muss ihre steuerbegünstigten Zwecke nicht nur im Gesellschaftsvertrag festlegen, sondern auch tatsächlich entsprechend handeln.&lt;br /&gt;
&lt;br /&gt;
=== Selbstlosigkeit ===&lt;br /&gt;
&lt;br /&gt;
§ 55 AO verlangt eine selbstlose Tätigkeit.&amp;lt;ref name=&amp;quot;AO55&amp;quot;&amp;gt;https://www.gesetze-im-internet.de/ao_1977/__55.html&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Insbesondere gilt:&lt;br /&gt;
&lt;br /&gt;
* Mittel dürfen nur für die satzungsmäßigen Zwecke verwendet werden.&lt;br /&gt;
* Gesellschafter dürfen keine Gewinnanteile erhalten.&lt;br /&gt;
* Gesellschafter dürfen in ihrer Eigenschaft als Gesellschafter keine sonstigen Zuwendungen aus Mitteln der Gesellschaft erhalten.&lt;br /&gt;
* Niemand darf durch zweckfremde Ausgaben oder unverhältnismäßig hohe Vergütungen begünstigt werden.&lt;br /&gt;
* Bei Auflösung oder Wegfall steuerbegünstigter Zwecke muss die gemeinnützigkeitsrechtliche Vermögensbindung eingehalten werden.&lt;br /&gt;
&lt;br /&gt;
Eine angemessene Vergütung von Beschäftigten, Geschäftsführung oder Auftragnehmern ist damit nicht grundsätzlich ausgeschlossen.&lt;br /&gt;
&lt;br /&gt;
Entscheidend ist insbesondere, dass Vergütungen angemessen sind und einer tatsächlichen Tätigkeit für die Gesellschaft entsprechen.&lt;br /&gt;
&lt;br /&gt;
=== Ausschließlichkeit ===&lt;br /&gt;
&lt;br /&gt;
Nach § 56 AO liegt Ausschließlichkeit vor, wenn die Körperschaft nur ihre steuerbegünstigten satzungsmäßigen Zwecke verfolgt.&amp;lt;ref name=&amp;quot;AO56&amp;quot;&amp;gt;https://www.gesetze-im-internet.de/ao_1977/__56.html&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Die gUG darf daher nicht hauptsächlich als Instrument für private oder unternehmerische Interessen verwendet werden.&lt;br /&gt;
&lt;br /&gt;
=== Unmittelbarkeit ===&lt;br /&gt;
&lt;br /&gt;
Nach § 57 AO verwirklicht eine Körperschaft ihre steuerbegünstigten Zwecke grundsätzlich selbst.&amp;lt;ref name=&amp;quot;AO57&amp;quot;&amp;gt;https://www.gesetze-im-internet.de/ao_1977/__57.html&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Für AOWIS kann dies beispielsweise erfolgen durch:&lt;br /&gt;
&lt;br /&gt;
* eigene Softwareentwicklung,&lt;br /&gt;
* eigene technische Dokumentation,&lt;br /&gt;
* eigene Forschungsarbeit,&lt;br /&gt;
* eigene Schulungen,&lt;br /&gt;
* eigene Entwicklungsprojekte,&lt;br /&gt;
* eigene Pilotprojekte,&lt;br /&gt;
* eigene Veröffentlichungen,&lt;br /&gt;
* eigene Projektbegleitung.&lt;br /&gt;
&lt;br /&gt;
Auch die Einbindung von Hilfspersonen und Kooperationen ist im gesetzlichen Rahmen möglich.&lt;br /&gt;
&lt;br /&gt;
=== Vermögensbindung ===&lt;br /&gt;
&lt;br /&gt;
Die gemeinnützigkeitsrechtliche Vermögensbindung muss im Gesellschaftsvertrag eindeutig geregelt sein.&lt;br /&gt;
&lt;br /&gt;
§ 61 AO verlangt, dass der Verwendungszweck des verbleibenden Vermögens bei Auflösung, Aufhebung oder Wegfall steuerbegünstigter Zwecke so genau bestimmt ist, dass seine steuerbegünstigte Verwendung geprüft werden kann.&amp;lt;ref name=&amp;quot;AO61&amp;quot;&amp;gt;https://www.gesetze-im-internet.de/ao_1977/__61.html&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Die Mustersatzung in Anlage 1 zur AO enthält hierfür die maßgeblichen Grundformulierungen.&amp;lt;ref name=&amp;quot;AOMuster&amp;quot;&amp;gt;https://www.gesetze-im-internet.de/ao_1977/anlage_1.html&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Tatsächliche Geschäftsführung ===&lt;br /&gt;
&lt;br /&gt;
Nicht nur der Gesellschaftsvertrag, sondern auch die tatsächliche Tätigkeit muss der Gemeinnützigkeit entsprechen.&lt;br /&gt;
&lt;br /&gt;
§ 63 AO verlangt, dass die tatsächliche Geschäftsführung auf die ausschließliche und unmittelbare Erfüllung der steuerbegünstigten Zwecke gerichtet ist.&amp;lt;ref name=&amp;quot;AO63&amp;quot;&amp;gt;https://www.gesetze-im-internet.de/ao_1977/__63.html&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Die Gesellschaft muss dies durch ordnungsgemäße Aufzeichnungen über Einnahmen und Ausgaben nachweisen können.&lt;br /&gt;
&lt;br /&gt;
Für AOWIS bedeutet das insbesondere:&lt;br /&gt;
&lt;br /&gt;
* nachvollziehbare Buchführung,&lt;br /&gt;
* dokumentierte Projektmittel,&lt;br /&gt;
* nachvollziehbare Verträge,&lt;br /&gt;
* dokumentierte Mittelverwendung,&lt;br /&gt;
* klare Zuordnung von Ausgaben,&lt;br /&gt;
* angemessene Vergütungen,&lt;br /&gt;
* nachvollziehbare Entscheidungen bei Geschäften mit Gesellschaftern oder verbundenen Unternehmen.&lt;br /&gt;
&lt;br /&gt;
== Gesellschaftsrechtliche Struktur ==&lt;br /&gt;
&lt;br /&gt;
=== Gesellschafter ===&lt;br /&gt;
&lt;br /&gt;
Die Gesellschafter bilden die grundlegende gesellschaftsrechtliche Entscheidungsebene.&lt;br /&gt;
&lt;br /&gt;
Zu ihren Aufgaben gehören je nach Gesetz und Gesellschaftsvertrag insbesondere:&lt;br /&gt;
&lt;br /&gt;
* Bestellung und Abberufung der Geschäftsführung,&lt;br /&gt;
* grundlegende strategische Entscheidungen,&lt;br /&gt;
* Änderungen des Gesellschaftsvertrags,&lt;br /&gt;
* Kapitalmaßnahmen,&lt;br /&gt;
* Feststellung des Jahresabschlusses und Ergebnisverwendung,&lt;br /&gt;
* Entscheidungen über grundlegende Veränderungen der Gesellschaft.&lt;br /&gt;
&lt;br /&gt;
Die Anzahl der Gesellschafter muss nicht künstlich erhöht werden.&lt;br /&gt;
&lt;br /&gt;
Für die Gründung einer Gesellschaft mit beschränkter Haftung genügt grundsätzlich eine Person.&amp;lt;ref name=&amp;quot;GmbHG1&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Geschäftsführung ===&lt;br /&gt;
&lt;br /&gt;
Die Geschäftsführung führt die laufenden Geschäfte der AOWIS gUG und vertritt die Gesellschaft nach außen.&lt;br /&gt;
&lt;br /&gt;
Zu ihren Aufgaben können insbesondere gehören:&lt;br /&gt;
&lt;br /&gt;
* operative Leitung,&lt;br /&gt;
* Personal,&lt;br /&gt;
* Finanzen,&lt;br /&gt;
* Verträge,&lt;br /&gt;
* Projektmanagement,&lt;br /&gt;
* Fördermittel,&lt;br /&gt;
* Partnerschaften,&lt;br /&gt;
* Software- und Infrastrukturprojekte,&lt;br /&gt;
* Veröffentlichungen,&lt;br /&gt;
* Compliance,&lt;br /&gt;
* Kommunikation mit Finanzamt und Behörden,&lt;br /&gt;
* Umsetzung der von den Gesellschaftern vorgegebenen strategischen Richtung.&lt;br /&gt;
&lt;br /&gt;
Die Gesellschaft muss mindestens einen Geschäftsführer haben.&amp;lt;ref name=&amp;quot;GmbHG6&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Weitere Strukturen ===&lt;br /&gt;
&lt;br /&gt;
Zusätzliche Organe oder Beiräte sind für die Gründung nicht zwingend erforderlich.&lt;br /&gt;
&lt;br /&gt;
Ein technischer Beirat, wissenschaftlicher Beirat, Praxisbeirat oder andere beratende Strukturen können später eingerichtet werden, wenn dafür ein konkreter Bedarf besteht.&lt;br /&gt;
&lt;br /&gt;
AOWIS sollte nicht bereits in der Gründungsphase mit einer umfangreichen formalen Organisationsstruktur belastet werden, deren praktische Funktion noch nicht feststeht.&lt;br /&gt;
&lt;br /&gt;
== Technische Entwicklung und Beteiligung am AOWIS-Projekt ==&lt;br /&gt;
&lt;br /&gt;
Die gesellschaftsrechtliche Struktur der AOWIS gUG muss nicht sämtliche technischen Abläufe des AOWIS-Projekts formal regeln.&lt;br /&gt;
&lt;br /&gt;
Softwareentwicklung kann weiterhin über die bestehenden Entwicklungsplattformen, Repository-Strukturen, Issues, Reviews und Pull Requests erfolgen.&lt;br /&gt;
&lt;br /&gt;
Technische Dokumentation und Standards können über die bestehenden AOWIS-Dokumentations- und Review-Prozesse weiterentwickelt werden.&lt;br /&gt;
&lt;br /&gt;
Mit wachsender Beteiligung können bei Bedarf zusätzliche Regeln für technische Entscheidungen, Maintainer-Rollen, Reviews oder Arbeitsgruppen geschaffen werden.&lt;br /&gt;
&lt;br /&gt;
Eine umfangreiche eigenständige Projekt-Governance ist jedoch keine Voraussetzung für die Gründung der gUG.&lt;br /&gt;
&lt;br /&gt;
== Open Source und offenes Wissen ==&lt;br /&gt;
&lt;br /&gt;
Die offene Verfügbarkeit von AOWIS ist ein zentraler Bestandteil des Projekts.&lt;br /&gt;
&lt;br /&gt;
Die gUG soll deshalb langfristig sicherstellen, dass wesentliche technische Grundlagen öffentlich zugänglich bleiben.&lt;br /&gt;
&lt;br /&gt;
Dazu gehören insbesondere:&lt;br /&gt;
&lt;br /&gt;
* Quellcode,&lt;br /&gt;
* technische Standards,&lt;br /&gt;
* Schnittstellenbeschreibungen,&lt;br /&gt;
* Datenmodelle,&lt;br /&gt;
* Dokumentation,&lt;br /&gt;
* geeignete Referenzimplementierungen,&lt;br /&gt;
* öffentlich finanzierte oder für die Allgemeinheit bestimmte Forschungsergebnisse,&lt;br /&gt;
* geeignete Schulungs- und Informationsmaterialien.&lt;br /&gt;
&lt;br /&gt;
Dabei können unterschiedliche offene Lizenzen für Software, Dokumentation, Daten und andere Inhalte verwendet werden.&lt;br /&gt;
&lt;br /&gt;
Lizenzentscheidungen sollten so getroffen werden, dass langfristige Offenheit, Wiederverwendbarkeit, technische Zusammenarbeit und Rechtssicherheit gewährleistet bleiben.&lt;br /&gt;
&lt;br /&gt;
== Wirtschaftliche Tätigkeiten ==&lt;br /&gt;
&lt;br /&gt;
Gemeinnützigkeit bedeutet nicht, dass die AOWIS gUG keine Einnahmen erzielen oder keine wirtschaftlichen Tätigkeiten ausüben darf.&lt;br /&gt;
&lt;br /&gt;
Mögliche Einnahmen können beispielsweise sein:&lt;br /&gt;
&lt;br /&gt;
* Spenden,&lt;br /&gt;
* Fördermittel,&lt;br /&gt;
* öffentliche Zuschüsse,&lt;br /&gt;
* Forschungsförderung,&lt;br /&gt;
* Projektfinanzierungen,&lt;br /&gt;
* zweckgebundene Zuwendungen,&lt;br /&gt;
* Einnahmen aus Schulungen,&lt;br /&gt;
* Forschungs- und Entwicklungsaufträge,&lt;br /&gt;
* technische Projektleistungen,&lt;br /&gt;
* Dienstleistungen,&lt;br /&gt;
* Lizenz- oder Nutzungsentgelte, soweit im Einzelfall vorgesehen,&lt;br /&gt;
* Verkauf von Materialien oder Hardware im Zusammenhang mit Projekten,&lt;br /&gt;
* sonstige projektbezogene Einnahmen.&lt;br /&gt;
&lt;br /&gt;
Die steuerliche Einordnung ist jeweils gesondert zu prüfen.&lt;br /&gt;
&lt;br /&gt;
Tätigkeiten können insbesondere dem steuerbegünstigten Bereich, einem Zweckbetrieb oder einem steuerpflichtigen wirtschaftlichen Geschäftsbetrieb zuzuordnen sein.&lt;br /&gt;
&lt;br /&gt;
§ 64 AO regelt die Behandlung steuerpflichtiger wirtschaftlicher Geschäftsbetriebe.&amp;lt;ref name=&amp;quot;AO64&amp;quot;&amp;gt;https://www.gesetze-im-internet.de/ao_1977/__64.html&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
§ 65 AO bestimmt die allgemeinen Voraussetzungen eines Zweckbetriebs.&amp;lt;ref name=&amp;quot;AO65&amp;quot;&amp;gt;https://www.gesetze-im-internet.de/ao_1977/__65.html&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Eine wirtschaftliche Tätigkeit führt daher nicht automatisch zum Verlust der Gemeinnützigkeit.&lt;br /&gt;
&lt;br /&gt;
Sie muss jedoch korrekt organisiert, dokumentiert und steuerlich eingeordnet werden.&lt;br /&gt;
&lt;br /&gt;
== Verhältnis zu Unternehmen und kommerziellen Partnern ==&lt;br /&gt;
&lt;br /&gt;
AOWIS soll offen für Zusammenarbeit mit Unternehmen sein.&lt;br /&gt;
&lt;br /&gt;
Unternehmen können beispielsweise:&lt;br /&gt;
&lt;br /&gt;
* Software beitragen,&lt;br /&gt;
* Entwicklung finanzieren,&lt;br /&gt;
* Hardware bereitstellen,&lt;br /&gt;
* an Forschungsprojekten teilnehmen,&lt;br /&gt;
* Dienstleistungen erbringen,&lt;br /&gt;
* AOWIS-basierte Systeme implementieren,&lt;br /&gt;
* Mitarbeitende für technische Beiträge bereitstellen,&lt;br /&gt;
* Entwicklungs- oder Pilotprojekte unterstützen.&lt;br /&gt;
&lt;br /&gt;
Die gUG darf jedoch nicht als Instrument zur unangemessenen Förderung eines einzelnen Unternehmens verwendet werden.&lt;br /&gt;
&lt;br /&gt;
Besonders sorgfältig zu behandeln sind:&lt;br /&gt;
&lt;br /&gt;
* Geschäfte mit Gesellschaftern,&lt;br /&gt;
* Geschäfte mit Unternehmen von Gesellschaftern oder Geschäftsführern,&lt;br /&gt;
* exklusive Vertriebsvereinbarungen,&lt;br /&gt;
* Beschaffungsentscheidungen zugunsten verbundener Unternehmen,&lt;br /&gt;
* ungewöhnlich hohe Vergütungen,&lt;br /&gt;
* Übertragung von Rechten unter nicht marktgerechten Bedingungen,&lt;br /&gt;
* Konstruktionen, bei denen gemeinnützige Mittel überwiegend privaten wirtschaftlichen Interessen zugutekommen.&lt;br /&gt;
&lt;br /&gt;
Interessenkonflikte sollten offengelegt und nachvollziehbar behandelt werden.&lt;br /&gt;
&lt;br /&gt;
== Stammkapital und Rücklage ==&lt;br /&gt;
&lt;br /&gt;
Die Höhe des Stammkapitals wird im Gesellschaftsvertrag festgelegt.&lt;br /&gt;
&lt;br /&gt;
Bei der Unternehmergesellschaft gelten die besonderen Regeln des § 5a GmbHG.&amp;lt;ref name=&amp;quot;GmbHG5a&amp;quot;&amp;gt;https://www.gesetze-im-internet.de/gmbhg/__5a.html&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Vor der Anmeldung zum Handelsregister muss das Stammkapital vollständig eingezahlt sein.&lt;br /&gt;
&lt;br /&gt;
Sacheinlagen sind bei dieser Gründungsform ausgeschlossen.&lt;br /&gt;
&lt;br /&gt;
Außerdem ist grundsätzlich eine gesetzliche Rücklage zu bilden, der ein Viertel des um einen Verlustvortrag verminderten Jahresüberschusses zuzuführen ist.&amp;lt;ref name=&amp;quot;GmbHG5a&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Unabhängig vom gesetzlich möglichen Mindestbetrag sollte das tatsächliche Stammkapital so gewählt werden, dass die Gesellschaft ihre anfänglichen Verpflichtungen realistisch erfüllen kann.&lt;br /&gt;
&lt;br /&gt;
Für AOWIS sind dabei beispielsweise zu berücksichtigen:&lt;br /&gt;
&lt;br /&gt;
* Notar- und Registerkosten,&lt;br /&gt;
* Buchhaltung,&lt;br /&gt;
* Versicherungen,&lt;br /&gt;
* Hosting und technische Infrastruktur,&lt;br /&gt;
* Domains und Kommunikationsdienste,&lt;br /&gt;
* Reisekosten,&lt;br /&gt;
* mögliche Personalkosten,&lt;br /&gt;
* Projektvorfinanzierung,&lt;br /&gt;
* Hardware und Testsysteme.&lt;br /&gt;
&lt;br /&gt;
== Gesellschaftsvertrag ==&lt;br /&gt;
&lt;br /&gt;
Der Gesellschaftsvertrag bedarf der notariellen Form.&amp;lt;ref name=&amp;quot;GmbHG2&amp;quot;&amp;gt;https://www.gesetze-im-internet.de/gmbhg/__2.html&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Er muss insbesondere enthalten:&lt;br /&gt;
&lt;br /&gt;
* Firma,&lt;br /&gt;
* Sitz,&lt;br /&gt;
* Unternehmensgegenstand,&lt;br /&gt;
* Stammkapital,&lt;br /&gt;
* Geschäftsanteile der Gesellschafter.&lt;br /&gt;
&lt;br /&gt;
Diese Mindestanforderungen ergeben sich aus § 3 GmbHG.&amp;lt;ref name=&amp;quot;GmbHG3&amp;quot;&amp;gt;https://www.gesetze-im-internet.de/gmbhg/__3.html&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Für eine gemeinnützige Gesellschaft müssen zusätzlich die gemeinnützigkeitsrechtlichen Anforderungen der Abgabenordnung berücksichtigt werden.&lt;br /&gt;
&lt;br /&gt;
Besonders wichtig sind:&lt;br /&gt;
&lt;br /&gt;
* genaue steuerbegünstigte Zwecke,&lt;br /&gt;
* konkrete Art der Zweckverwirklichung,&lt;br /&gt;
* Selbstlosigkeit,&lt;br /&gt;
* ausschließliche Mittelverwendung,&lt;br /&gt;
* Verbot unangemessener Begünstigungen,&lt;br /&gt;
* Vermögensbindung.&lt;br /&gt;
&lt;br /&gt;
Die Formulierungen der Mustersatzung aus Anlage 1 zur AO sollten dabei berücksichtigt werden.&amp;lt;ref name=&amp;quot;AOMuster&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Gründungsschritte ==&lt;br /&gt;
&lt;br /&gt;
=== Schritt 1: Grundstruktur festlegen ===&lt;br /&gt;
&lt;br /&gt;
Zu entscheiden sind insbesondere:&lt;br /&gt;
&lt;br /&gt;
* endgültige Firma,&lt;br /&gt;
* Sitz der Gesellschaft,&lt;br /&gt;
* Gesellschafter,&lt;br /&gt;
* Höhe des Stammkapitals,&lt;br /&gt;
* Verteilung der Geschäftsanteile,&lt;br /&gt;
* Geschäftsführung,&lt;br /&gt;
* Vertretungsregelung,&lt;br /&gt;
* steuerbegünstigte Zwecke,&lt;br /&gt;
* konkrete Tätigkeiten zur Zweckverwirklichung.&lt;br /&gt;
&lt;br /&gt;
Als Arbeitsbezeichnung wird in diesem Konzept &#039;&#039;&#039;AOWIS gUG&#039;&#039;&#039; verwendet.&lt;br /&gt;
&lt;br /&gt;
=== Schritt 2: Gesellschaftsvertrag entwerfen ===&lt;br /&gt;
&lt;br /&gt;
Der Gesellschaftsvertrag sollte sowohl die gesellschaftsrechtlichen Anforderungen als auch die Anforderungen der Gemeinnützigkeit erfüllen.&lt;br /&gt;
&lt;br /&gt;
Insbesondere der Unternehmensgegenstand und die steuerbegünstigten Zwecke müssen miteinander abgestimmt sein.&lt;br /&gt;
&lt;br /&gt;
Ein ausschließlich auf die gesetzliche Minimalstruktur reduziertes Muster ist für AOWIS voraussichtlich nicht sinnvoll, da die gemeinnützige Zweckstruktur präzise abgebildet werden muss.&lt;br /&gt;
&lt;br /&gt;
=== Schritt 3: Gemeinnützigkeitsrechtliche Vorabstimmung ===&lt;br /&gt;
&lt;br /&gt;
Vor der notariellen Gründung sollte der Entwurf nach Möglichkeit mit dem zuständigen Finanzamt abgestimmt werden.&lt;br /&gt;
&lt;br /&gt;
Ziel ist insbesondere:&lt;br /&gt;
&lt;br /&gt;
* Prüfung der gemeinnützigen Zwecke,&lt;br /&gt;
* Prüfung der Zweckverwirklichung,&lt;br /&gt;
* Prüfung der Selbstlosigkeitsklauseln,&lt;br /&gt;
* Prüfung der Vermögensbindung,&lt;br /&gt;
* Vermeidung späterer kostspieliger Änderungen des Gesellschaftsvertrags.&lt;br /&gt;
&lt;br /&gt;
Die formelle Feststellung der satzungsmäßigen Voraussetzungen richtet sich nach § 60a AO.&amp;lt;ref name=&amp;quot;AO60a&amp;quot;&amp;gt;https://www.gesetze-im-internet.de/ao_1977/__60a.html&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Schritt 4: Notarielle Gründung ===&lt;br /&gt;
&lt;br /&gt;
Der Gesellschaftsvertrag wird notariell beurkundet.&lt;br /&gt;
&lt;br /&gt;
Dabei werden unter anderem:&lt;br /&gt;
&lt;br /&gt;
* der Gesellschaftsvertrag abgeschlossen,&lt;br /&gt;
* die Geschäftsanteile übernommen,&lt;br /&gt;
* die Geschäftsführung bestellt,&lt;br /&gt;
* die erforderlichen Gründungsunterlagen erstellt.&lt;br /&gt;
&lt;br /&gt;
=== Schritt 5: Geschäftskonto und Stammkapital ===&lt;br /&gt;
&lt;br /&gt;
Nach der notariellen Gründung wird ein Geschäftskonto eingerichtet.&lt;br /&gt;
&lt;br /&gt;
Das im Gesellschaftsvertrag festgelegte Stammkapital wird eingezahlt.&lt;br /&gt;
&lt;br /&gt;
Bei der Gründung nach § 5a GmbHG muss das Stammkapital vor der Handelsregisteranmeldung vollständig eingezahlt sein.&amp;lt;ref name=&amp;quot;GmbHG5a&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Schritt 6: Handelsregister ===&lt;br /&gt;
&lt;br /&gt;
Die Gesellschaft wird über den Notar zur Eintragung in das Handelsregister angemeldet.&lt;br /&gt;
&lt;br /&gt;
Mit der Eintragung werden unter anderem Firma, Sitz, Geschäftsanschrift, Unternehmensgegenstand, Stammkapital und Geschäftsführung im Handelsregister erfasst.&amp;lt;ref name=&amp;quot;GmbHG10&amp;quot;&amp;gt;https://www.gesetze-im-internet.de/gmbhg/__10.html&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Schritt 7: Steuerliche Erfassung und Gemeinnützigkeit ===&lt;br /&gt;
&lt;br /&gt;
Nach beziehungsweise im Zusammenhang mit der Gründung erfolgt die steuerliche Erfassung beim Finanzamt.&lt;br /&gt;
&lt;br /&gt;
Die satzungsmäßigen Voraussetzungen der Gemeinnützigkeit werden gemäß § 60a AO festgestellt.&amp;lt;ref name=&amp;quot;AO60a&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Für die dauerhafte steuerliche Begünstigung genügt jedoch nicht allein ein korrekter Gesellschaftsvertrag.&lt;br /&gt;
&lt;br /&gt;
Auch die tatsächliche Geschäftsführung muss den gemeinnützigen Vorgaben entsprechen.&amp;lt;ref name=&amp;quot;AO63&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Schritt 8: Weitere Registrierungen und Verwaltung ===&lt;br /&gt;
&lt;br /&gt;
Anschließend sind je nach konkreter Situation insbesondere zu erledigen oder zu prüfen:&lt;br /&gt;
&lt;br /&gt;
* Transparenzregister,&lt;br /&gt;
* steuerliche Registrierungen,&lt;br /&gt;
* gegebenenfalls Gewerbeanmeldung,&lt;br /&gt;
* Buchhaltung,&lt;br /&gt;
* Jahresabschluss,&lt;br /&gt;
* Geschäftskonto,&lt;br /&gt;
* Versicherungen,&lt;br /&gt;
* Lohnbuchhaltung bei Beschäftigten,&lt;br /&gt;
* Datenschutz,&lt;br /&gt;
* Vertragsvorlagen,&lt;br /&gt;
* Fördermittelverwaltung,&lt;br /&gt;
* Spendenverwaltung,&lt;br /&gt;
* Projektbuchhaltung,&lt;br /&gt;
* Dokumentation von Mittelverwendung und Entscheidungen.&lt;br /&gt;
&lt;br /&gt;
== Finanzielle Grundstruktur ==&lt;br /&gt;
&lt;br /&gt;
Die gUG sollte von Beginn an eine nachvollziehbare finanzielle Struktur besitzen.&lt;br /&gt;
&lt;br /&gt;
Sinnvoll sind insbesondere:&lt;br /&gt;
&lt;br /&gt;
* klare Kostenstellen beziehungsweise Projektzuordnungen,&lt;br /&gt;
* getrennte Erfassung zweckgebundener Mittel,&lt;br /&gt;
* nachvollziehbare Fördermittelabrechnung,&lt;br /&gt;
* dokumentierte Reisekosten,&lt;br /&gt;
* dokumentierte Beschaffungen,&lt;br /&gt;
* Verträge für externe Leistungen,&lt;br /&gt;
* nachvollziehbare Vergütungsentscheidungen,&lt;br /&gt;
* regelmäßige Liquiditätsplanung.&lt;br /&gt;
&lt;br /&gt;
Gerade bei internationalen Projekten sollte frühzeitig darauf geachtet werden, dass Zahlungen und Mittelweitergaben nachvollziehbar dokumentiert werden können.&lt;br /&gt;
&lt;br /&gt;
== Rücklagen und langfristige Finanzierung ==&lt;br /&gt;
&lt;br /&gt;
Gemeinnützige Körperschaften dürfen unter den gesetzlichen Voraussetzungen Rücklagen bilden.&lt;br /&gt;
&lt;br /&gt;
§ 62 AO regelt verschiedene zulässige Formen der Rücklagen- und Vermögensbildung.&amp;lt;ref name=&amp;quot;AO62&amp;quot;&amp;gt;https://www.gesetze-im-internet.de/ao_1977/__62.html&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Für AOWIS können Rücklagen beispielsweise relevant sein für:&lt;br /&gt;
&lt;br /&gt;
* langfristige Softwareentwicklung,&lt;br /&gt;
* geplante Forschungsprojekte,&lt;br /&gt;
* größere technische Anschaffungen,&lt;br /&gt;
* Server- und Infrastrukturkosten,&lt;br /&gt;
* Projektvorfinanzierung,&lt;br /&gt;
* Ersatzbeschaffungen,&lt;br /&gt;
* längerfristige Entwicklungsprogramme.&lt;br /&gt;
&lt;br /&gt;
Die gesellschaftsrechtliche Rücklage nach § 5a GmbHG und gemeinnützigkeitsrechtlich zulässige Rücklagen nach der AO sind dabei voneinander zu unterscheiden.&lt;br /&gt;
&lt;br /&gt;
== Schutz der langfristigen Ausrichtung ==&lt;br /&gt;
&lt;br /&gt;
Die Gesellschaftsstruktur sollte so gestaltet werden, dass der gemeinnützige Charakter von AOWIS langfristig geschützt wird.&lt;br /&gt;
&lt;br /&gt;
Zu berücksichtigen sind insbesondere:&lt;br /&gt;
&lt;br /&gt;
* Verteilung und Übertragbarkeit von Geschäftsanteilen,&lt;br /&gt;
* Zustimmungsvorbehalte bei Anteilsübertragungen,&lt;br /&gt;
* Regeln für Änderungen des Gesellschaftszwecks,&lt;br /&gt;
* Regeln für grundlegende Änderungen der offenen Ausrichtung,&lt;br /&gt;
* Interessenkonflikte,&lt;br /&gt;
* Vermögensbindung,&lt;br /&gt;
* Schutz wesentlicher Projektressourcen.&lt;br /&gt;
&lt;br /&gt;
Geschäftsanteile einer Gesellschaft mit beschränkter Haftung sind grundsätzlich übertragbar; der Gesellschaftsvertrag kann eine Übertragung jedoch von zusätzlichen Voraussetzungen, insbesondere einer Zustimmung der Gesellschaft, abhängig machen.&amp;lt;ref name=&amp;quot;GmbHG15&amp;quot;&amp;gt;https://www.gesetze-im-internet.de/gmbhg/__15.html&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Für AOWIS sollte deshalb geprüft werden, ob der Gesellschaftsvertrag geeignete Regeln enthält, um eine unerwünschte Übernahme oder Zweckverschiebung zu erschweren.&lt;br /&gt;
&lt;br /&gt;
== AOWIS als internationales Projekt ==&lt;br /&gt;
&lt;br /&gt;
Die AOWIS gUG soll ihren Sitz in Deutschland haben, AOWIS selbst ist jedoch international ausgerichtet.&lt;br /&gt;
&lt;br /&gt;
Die Arbeit kann daher Beteiligte und Projekte in unterschiedlichen Ländern umfassen.&lt;br /&gt;
&lt;br /&gt;
Insbesondere bei Entwicklungsprojekten sollte die Zusammenarbeit mit lokalen Akteuren nicht nur als Umsetzung bereits in Europa getroffener Entscheidungen verstanden werden.&lt;br /&gt;
&lt;br /&gt;
Lokale Betreiber, Techniker, Gemeinden und andere Beteiligte verfügen über Wissen, das für funktionierende Infrastruktur entscheidend ist.&lt;br /&gt;
&lt;br /&gt;
Zu berücksichtigen sind beispielsweise:&lt;br /&gt;
&lt;br /&gt;
* lokale Wasserquellen,&lt;br /&gt;
* vorhandene Infrastruktur,&lt;br /&gt;
* Wartungsmöglichkeiten,&lt;br /&gt;
* Ersatzteilverfügbarkeit,&lt;br /&gt;
* Energieversorgung,&lt;br /&gt;
* Kommunikationsinfrastruktur,&lt;br /&gt;
* lokale technische Fähigkeiten,&lt;br /&gt;
* soziale und organisatorische Strukturen,&lt;br /&gt;
* klimatische Bedingungen,&lt;br /&gt;
* Hydrogeologie,&lt;br /&gt;
* tatsächliche Betriebsabläufe.&lt;br /&gt;
&lt;br /&gt;
AOWIS soll technische Zusammenarbeit ermöglichen, bei der externe Expertise und lokales Wissen miteinander verbunden werden.&lt;br /&gt;
&lt;br /&gt;
== Abgrenzung zwischen Projekt und gemeinnützigem Zweck ==&lt;br /&gt;
&lt;br /&gt;
Nicht jede Entwicklung innerhalb von AOWIS muss unmittelbar ein Entwicklungsprojekt darstellen.&lt;br /&gt;
&lt;br /&gt;
AOWIS selbst ist eine allgemeine offene technische Grundlage.&lt;br /&gt;
&lt;br /&gt;
Beispielsweise kann eine Verbesserung des Simulationssystems, eines Datenmodells oder einer grafischen Oberfläche weltweit verwendet werden.&lt;br /&gt;
&lt;br /&gt;
Für die Tätigkeit der gUG ist jedoch entscheidend, dass ihre Ressourcen insgesamt zur Verwirklichung ihrer steuerbegünstigten Satzungszwecke eingesetzt werden.&lt;br /&gt;
&lt;br /&gt;
Die Gemeinnützigkeit darf daher nicht allein mit der Behauptung begründet werden, dass AOWIS Open Source ist.&lt;br /&gt;
&lt;br /&gt;
Open-Source-Software ist ein wichtiges Mittel.&lt;br /&gt;
&lt;br /&gt;
Der steuerbegünstigte Zweck ergibt sich jedoch aus der konkreten Förderung beispielsweise von:&lt;br /&gt;
&lt;br /&gt;
* Entwicklungszusammenarbeit,&lt;br /&gt;
* Bildung,&lt;br /&gt;
* Wissenschaft und Forschung,&lt;br /&gt;
* Umweltschutz.&lt;br /&gt;
&lt;br /&gt;
== Risiken und Gegenmaßnahmen ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Risiko&lt;br /&gt;
! Beschreibung&lt;br /&gt;
! Gegenmaßnahme&lt;br /&gt;
|-&lt;br /&gt;
| Unklare gemeinnützige Zwecksetzung&lt;br /&gt;
| Der Gesellschaftsvertrag beschreibt technische Aktivitäten, aber nicht ausreichend, welchem steuerbegünstigten Zweck sie dienen.&lt;br /&gt;
| Gemeinnützige Zwecke und konkrete Zweckverwirklichung klar miteinander verbinden; Vorabstimmung mit dem Finanzamt.&lt;br /&gt;
|-&lt;br /&gt;
| Zu viele Satzungszwecke&lt;br /&gt;
| Es werden vorsorglich zahlreiche gemeinnützige Zwecke aufgenommen, die später tatsächlich nicht verfolgt werden.&lt;br /&gt;
| Nur Zwecke aufnehmen, für die konkrete und dauerhafte Tätigkeiten vorgesehen sind.&lt;br /&gt;
|-&lt;br /&gt;
| Vermischung mit privaten Interessen&lt;br /&gt;
| Gesellschaftsmittel oder Projektchancen begünstigen Gesellschafter oder verbundene Unternehmen unangemessen.&lt;br /&gt;
| Interessenkonflikte offenlegen, Verträge dokumentieren und angemessene Konditionen sicherstellen.&lt;br /&gt;
|-&lt;br /&gt;
| Unklare wirtschaftliche Tätigkeiten&lt;br /&gt;
| Dienstleistungen oder Verkäufe werden steuerlich nicht korrekt eingeordnet.&lt;br /&gt;
| Tätigkeiten frühzeitig steuerlich prüfen und Buchhaltung entsprechend strukturieren.&lt;br /&gt;
|-&lt;br /&gt;
| Unzureichende Dokumentation&lt;br /&gt;
| Die tatsächliche gemeinnützige Geschäftsführung kann gegenüber dem Finanzamt nicht ausreichend nachgewiesen werden.&lt;br /&gt;
| Projektakten, Verträge, Buchhaltung, Beschlüsse und Mittelverwendung systematisch dokumentieren.&lt;br /&gt;
|-&lt;br /&gt;
| Zu geringes Anfangskapital&lt;br /&gt;
| Die Gesellschaft ist formal gegründet, verfügt aber nicht über ausreichende Mittel für ihre anfänglichen Verpflichtungen.&lt;br /&gt;
| Stammkapital und zusätzliche Finanzierung anhand eines realistischen Liquiditätsplans bestimmen.&lt;br /&gt;
|-&lt;br /&gt;
| Abhängigkeit von einzelnen Geldgebern&lt;br /&gt;
| Ein einzelner Förderer erhält faktisch übermäßigen Einfluss auf die technische oder organisatorische Ausrichtung.&lt;br /&gt;
| Finanzierung diversifizieren und grundlegende Entscheidungen unabhängig halten.&lt;br /&gt;
|-&lt;br /&gt;
| Unklare Rechte an Software und Dokumentation&lt;br /&gt;
| Später ist unklar, welche Rechte die gUG an Beiträgen, Marken, Domains, Software oder Dokumentation besitzt.&lt;br /&gt;
| Lizenzen, Contributor-Regeln, Rechteübertragungen und organisatorische Zuständigkeiten sauber dokumentieren.&lt;br /&gt;
|-&lt;br /&gt;
| Zweckverschiebung durch spätere Gesellschafter&lt;br /&gt;
| Die langfristige gemeinnützige und offene Ausrichtung wird durch Änderungen der Beteiligungsverhältnisse gefährdet.&lt;br /&gt;
| Anteilsübertragungen und grundlegende Satzungsänderungen im Gesellschaftsvertrag geeignet absichern.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Sofort umsetzbare Aufgaben ==&lt;br /&gt;
&lt;br /&gt;
=== Gesellschaft ===&lt;br /&gt;
&lt;br /&gt;
* endgültigen Namen festlegen,&lt;br /&gt;
* Sitz festlegen,&lt;br /&gt;
* Gesellschafter festlegen,&lt;br /&gt;
* Geschäftsführung festlegen,&lt;br /&gt;
* Höhe des Stammkapitals festlegen,&lt;br /&gt;
* Beteiligungsverhältnisse festlegen.&lt;br /&gt;
&lt;br /&gt;
=== Gemeinnützigkeit ===&lt;br /&gt;
&lt;br /&gt;
* endgültige gemeinnützige Zwecke auswählen,&lt;br /&gt;
* konkrete Zweckverwirklichung formulieren,&lt;br /&gt;
* Gesellschaftsvertrag entwerfen,&lt;br /&gt;
* Vermögensbindung festlegen,&lt;br /&gt;
* Entwurf mit dem Finanzamt abstimmen.&lt;br /&gt;
&lt;br /&gt;
=== Organisation ===&lt;br /&gt;
&lt;br /&gt;
* erste Jahresplanung erstellen,&lt;br /&gt;
* Liquiditätsplan erstellen,&lt;br /&gt;
* Buchhaltungslösung auswählen,&lt;br /&gt;
* Geschäftskonto vorbereiten,&lt;br /&gt;
* Projekt- und Fördermittelstruktur definieren,&lt;br /&gt;
* relevante Versicherungen prüfen,&lt;br /&gt;
* Datenschutz- und Vertragsgrundlagen vorbereiten.&lt;br /&gt;
&lt;br /&gt;
=== AOWIS ===&lt;br /&gt;
&lt;br /&gt;
* klären, welche bestehenden Projektressourcen langfristig von der gUG getragen werden sollen,&lt;br /&gt;
* Domains und technische Infrastruktur zuordnen,&lt;br /&gt;
* Lizenz- und Rechteübersicht erstellen,&lt;br /&gt;
* bestehende Software-Repositories und Dokumentation erfassen,&lt;br /&gt;
* laufende und geplante Entwicklungsprojekte dokumentieren,&lt;br /&gt;
* erste gemeinnützige Projekte und Bildungsaktivitäten definieren.&lt;br /&gt;
&lt;br /&gt;
== Mögliche Kurzbeschreibung der AOWIS gUG ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
Die AOWIS gUG fördert Entwicklungszusammenarbeit, Bildung, Forschung und den nachhaltigen Umgang mit Wasserressourcen durch offene technische Grundlagen für Wasser- und Bewässerungsinfrastruktur.&lt;br /&gt;
&lt;br /&gt;
Sie entwickelt und verbreitet Open-Source-Software, technische Standards, Datenmodelle, Dokumentation, Engineering-Methoden und Bildungsangebote und unterstützt damit Gemeinden, Betreiber, Fachkräfte, gemeinnützige Organisationen und andere Akteure bei der Planung, dem Betrieb und der langfristigen Weiterentwicklung sicherer und wartbarer Wasserinfrastruktur.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Mögliche Langbeschreibung der AOWIS gUG ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
Die AOWIS gUG ist die gemeinnützige Trägerorganisation des Afritic Open Water Infrastructure System (AOWIS).&lt;br /&gt;
&lt;br /&gt;
AOWIS ist ein offenes System für die Planung, den Entwurf, die Modellierung, den Bau, den Betrieb, die Überwachung, die Wartung und die Weiterentwicklung von Wasser- und Bewässerungsinfrastruktur über deren gesamten Lebenszyklus.&lt;br /&gt;
&lt;br /&gt;
Die AOWIS gUG entwickelt und pflegt hierfür Open-Source-Software, offene technische Standards, gemeinsame Infrastruktur- und Datenmodelle, Engineering-Methoden, Dokumentation, Referenzimplementierungen und Bildungsangebote.&lt;br /&gt;
&lt;br /&gt;
Ein besonderer Schwerpunkt liegt auf der Entwicklungszusammenarbeit und auf technischen Lösungen, die auch unter schwierigen Bedingungen praktikabel bleiben, beispielsweise bei instabiler Stromversorgung, eingeschränkter Konnektivität, begrenztem Zugang zu Spezialisten und der Notwendigkeit eines sicheren lokalen Betriebs.&lt;br /&gt;
&lt;br /&gt;
Die Gesellschaft fördert den Aufbau lokaler technischer Fähigkeiten, Wissenstransfer, Ausbildung, Forschung und praktische Zusammenarbeit mit Gemeinden, Betreibern, gemeinnützigen Organisationen, Hochschulen, Forschungseinrichtungen und öffentlichen Stellen.&lt;br /&gt;
&lt;br /&gt;
AOWIS selbst ist dabei nicht auf bestimmte Länder oder Regionen beschränkt. Die entwickelten Softwarekomponenten, Standards, Modelle und Methoden sollen als offene Grundlage für Wasser- und Bewässerungsinfrastruktur weltweit nutzbar sein.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Empfehlung für die nächste Arbeitsphase ==&lt;br /&gt;
&lt;br /&gt;
Die nächste Arbeitsphase sollte sich auf vier konkrete Dokumente konzentrieren:&lt;br /&gt;
&lt;br /&gt;
# &#039;&#039;&#039;Gesellschaftsvertrag der AOWIS gUG&#039;&#039;&#039; mit präziser gemeinnützigkeitsrechtlicher Zweckbestimmung.&lt;br /&gt;
# &#039;&#039;&#039;1–2-seitige Tätigkeitsbeschreibung&#039;&#039;&#039; für die Vorabstimmung mit dem Finanzamt.&lt;br /&gt;
# &#039;&#039;&#039;Gründungs- und Finanzplan&#039;&#039;&#039; mit Stammkapital, laufenden Kosten und Finanzierung der ersten zwölf Monate.&lt;br /&gt;
# &#039;&#039;&#039;Übersicht der AOWIS-Projektressourcen&#039;&#039;&#039; mit Software, Domains, Dokumentation, Lizenzen und technischen Diensten, die zukünftig von der gUG getragen werden sollen.&lt;br /&gt;
&lt;br /&gt;
Der Gesellschaftsvertrag sollte vor der notariellen Gründung mit dem zuständigen Finanzamt abgestimmt werden.&lt;br /&gt;
&lt;br /&gt;
== Rechtliche Hinweise ==&lt;br /&gt;
&lt;br /&gt;
Dieses Dokument ist ein Arbeits- und Planungspapier für die Gründung der AOWIS gUG.&lt;br /&gt;
&lt;br /&gt;
Es ersetzt keine Rechts- oder Steuerberatung.&lt;br /&gt;
&lt;br /&gt;
Insbesondere folgende Punkte sollten vor der Gründung fachlich geprüft werden:&lt;br /&gt;
&lt;br /&gt;
* genaue Formulierung der steuerbegünstigten Zwecke,&lt;br /&gt;
* Formulierung der Zweckverwirklichung,&lt;br /&gt;
* Vermögensbindung,&lt;br /&gt;
* Unternehmensgegenstand,&lt;br /&gt;
* Firma,&lt;br /&gt;
* Beteiligungsstruktur,&lt;br /&gt;
* Übertragung von Geschäftsanteilen,&lt;br /&gt;
* Geschäftsführerverträge und Vergütung,&lt;br /&gt;
* Behandlung wirtschaftlicher Tätigkeiten,&lt;br /&gt;
* umsatzsteuerliche Fragen,&lt;br /&gt;
* internationale Mittelverwendung und Projektfinanzierung.&lt;br /&gt;
&lt;br /&gt;
== Quellen ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Kategorie:AOWIS]]&lt;br /&gt;
[[Kategorie:gUG]]&lt;br /&gt;
[[Kategorie:Gemeinnützigkeit]]&lt;br /&gt;
[[Kategorie:Entwicklungszusammenarbeit]]&lt;br /&gt;
[[Kategorie:Governance]]&lt;/div&gt;</summary>
		<author><name>Samuel</name></author>
	</entry>
	<entry>
		<id>https://aowis.org/index.php?title=Governance:Non-Profit-Association&amp;diff=787</id>
		<title>Governance:Non-Profit-Association</title>
		<link rel="alternate" type="text/html" href="https://aowis.org/index.php?title=Governance:Non-Profit-Association&amp;diff=787"/>
		<updated>2026-10-05T12:21:48Z</updated>

		<summary type="html">&lt;p&gt;Samuel: /* Projektbezug */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
{{AI-Generated&lt;br /&gt;
 | tool=ChatGPT&lt;br /&gt;
 | date=2026-06-09&lt;br /&gt;
 | scope=full page&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
= Konzept zur Vereinsgründung für AOWIS =&lt;br /&gt;
&lt;br /&gt;
== Kurzfassung ==&lt;br /&gt;
&lt;br /&gt;
Für das Projekt AOWIS erscheint ein &#039;&#039;&#039;gemeinnütziger eingetragener Verein (e. V.)&#039;&#039;&#039; als geeignete Grundstruktur.&lt;br /&gt;
&lt;br /&gt;
Der Verein sollte nicht als Anbieter oder Verkäufer von Bewässerungs- oder Wassertechnik auftreten, sondern als gemeinnütziger Träger für:&lt;br /&gt;
&lt;br /&gt;
* offene technische Standards,&lt;br /&gt;
* Entwicklungszusammenarbeit,&lt;br /&gt;
* Wissenstransfer,&lt;br /&gt;
* Ausbildung lokaler Betreiber und Techniker,&lt;br /&gt;
* Pilot- und Demonstrationsprojekte,&lt;br /&gt;
* Dokumentation, Forschung und Qualitätssicherung,&lt;br /&gt;
* nachhaltige Wasser-, Bewässerungs- und Agrarinfrastruktur in ressourcenarmen Regionen.&lt;br /&gt;
&lt;br /&gt;
Der stärkste gemeinnützigkeitsrechtliche Hauptzweck ist die &#039;&#039;&#039;Förderung der Entwicklungszusammenarbeit&#039;&#039;&#039;. Dieser Zweck ist in § 52 Abs. 2 Nr. 15 Abgabenordnung ausdrücklich als gemeinnütziger Zweck genannt.&amp;lt;ref name=&amp;quot;AO52&amp;quot;&amp;gt;https://www.gesetze-im-internet.de/ao_1977/__52.html&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Ergänzend können — soweit tatsächlich umgesetzt — folgende gemeinnützige Zwecke aufgenommen werden:&lt;br /&gt;
&lt;br /&gt;
* Förderung von Bildung und Berufsbildung,&lt;br /&gt;
* Förderung von Wissenschaft und Forschung,&lt;br /&gt;
* Förderung des Umwelt- und Ressourcenschutzes,&lt;br /&gt;
* Förderung internationaler technischer Zusammenarbeit.&lt;br /&gt;
&lt;br /&gt;
== Projektbezug ==&lt;br /&gt;
&lt;br /&gt;
AOWIS steht für &#039;&#039;&#039;Afritic Open Water Infrastructure System&#039;&#039;&#039; und beschreibt einen offenen technischen Standard für sichere und zuverlässige Wasser Infrastruktur in ressourcenarmen Umgebungen.&amp;lt;ref name=&amp;quot;AOWISMain&amp;quot;&amp;gt;https://aowis.org/index.php/Main_Page&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Die Projektlogik ist besonders relevant für Regionen mit:&lt;br /&gt;
&lt;br /&gt;
* instabiler Stromversorgung,&lt;br /&gt;
* eingeschränkter Internetverbindung,&lt;br /&gt;
* knappen technischen Ressourcen,&lt;br /&gt;
* begrenzter Verfügbarkeit qualifizierter Fachkräfte,&lt;br /&gt;
* Bedarf an sicherem, robustem und lokal betreibbarem Betrieb,&lt;br /&gt;
* Problemen bei Wasserverteilung, Bewässerung und landwirtschaftlicher Infrastruktur.&lt;br /&gt;
&lt;br /&gt;
AOWIS verfolgt dabei keine reine Produktlogik. Der Kern liegt in offenen Standards, Planung, Betrieb, Monitoring, Wartung, Training, Governance, Transparenz und lokaler Nutzbarkeit.&amp;lt;ref name=&amp;quot;AOWISMain&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Für eine Vereinsgründung bedeutet das:&lt;br /&gt;
&lt;br /&gt;
: Der Verein sollte nicht primär Technik verkaufen, sondern gemeinnützige Voraussetzungen schaffen, damit robuste Wasser-, Bewässerungs- und Agrarsysteme in entwicklungsrelevanten Regionen sicher, offen, lokal betreibbar und langfristig wartbar werden.&lt;br /&gt;
&lt;br /&gt;
== Empfohlene Rechtsform ==&lt;br /&gt;
&lt;br /&gt;
Empfohlen wird die Gründung eines:&lt;br /&gt;
&lt;br /&gt;
: &#039;&#039;&#039;eingetragenen gemeinnützigen Vereins&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
also eines:&lt;br /&gt;
&lt;br /&gt;
: &#039;&#039;&#039;e. V. mit angestrebter Anerkennung als gemeinnützig&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Ein eingetragener Verein eignet sich besonders, wenn:&lt;br /&gt;
&lt;br /&gt;
* ideelle und gemeinnützige Zwecke im Vordergrund stehen,&lt;br /&gt;
* Mitglieder, Förderer, technische Beitragende und Partner eingebunden werden sollen,&lt;br /&gt;
* Spenden und Fördermittel eingeworben werden sollen,&lt;br /&gt;
* eine transparente Governance-Struktur entstehen soll,&lt;br /&gt;
* der Verein unabhängig von einzelnen Unternehmen oder Personen handeln soll.&lt;br /&gt;
&lt;br /&gt;
Für die Eintragung ins Vereinsregister sind mindestens sieben Mitglieder erforderlich. § 56 BGB bestimmt, dass die Eintragung nur erfolgen soll, wenn die Zahl der Mitglieder mindestens sieben beträgt.&amp;lt;ref name=&amp;quot;BGB56&amp;quot;&amp;gt;https://www.gesetze-im-internet.de/bgb/__56.html&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Gemeinnützigkeitslogik ==&lt;br /&gt;
&lt;br /&gt;
=== Hauptzweck ===&lt;br /&gt;
&lt;br /&gt;
Als Hauptzweck wird empfohlen:&lt;br /&gt;
&lt;br /&gt;
: &#039;&#039;&#039;Förderung der Entwicklungszusammenarbeit&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Begründung:&lt;br /&gt;
&lt;br /&gt;
AOWIS richtet sich auf Wasser-, Bewässerungs- und Agrarinfrastruktur in ressourcenarmen Regionen. Die Projektziele berühren damit zentrale Felder der Entwicklungszusammenarbeit:&lt;br /&gt;
&lt;br /&gt;
* Zugang zu sicherer und wartbarer Wasserinfrastruktur,&lt;br /&gt;
* Unterstützung lokaler Betreiber und Initiativen,&lt;br /&gt;
* technische Befähigung vor Ort,&lt;br /&gt;
* nachhaltige Landwirtschaft,&lt;br /&gt;
* resiliente Infrastruktur,&lt;br /&gt;
* Reduktion von Abhängigkeit von einzelnen Herstellern,&lt;br /&gt;
* Wissenstransfer und lokale Selbstbefähigung.&lt;br /&gt;
&lt;br /&gt;
=== Ergänzende Zwecke ===&lt;br /&gt;
&lt;br /&gt;
Je nach tatsächlicher Tätigkeit können ergänzend aufgenommen werden:&lt;br /&gt;
&lt;br /&gt;
==== Bildung und Berufsbildung ====&lt;br /&gt;
&lt;br /&gt;
Begründung:&lt;br /&gt;
&lt;br /&gt;
AOWIS sieht Training lokaler Techniker, Betreiber und Initiativen vor. Der Verein kann Schulungen, Lehrmaterial, Handbücher, Workshops und Ausbildungsprogramme entwickeln.&lt;br /&gt;
&lt;br /&gt;
==== Wissenschaft und Forschung ====&lt;br /&gt;
&lt;br /&gt;
Begründung:&lt;br /&gt;
&lt;br /&gt;
Der Verein kann offene Standards, Referenzarchitekturen, technische Dokumentation, Evaluierungen, Studien, Datenmodelle und Pilotprojekte entwickeln oder fördern.&lt;br /&gt;
&lt;br /&gt;
Wichtig:&lt;br /&gt;
&lt;br /&gt;
Dieser Zweck sollte nur aufgenommen werden, wenn tatsächlich Forschungs- oder Entwicklungsarbeit mit dokumentierter Methodik, Ergebnisoffenheit und Veröffentlichung geplant ist.&lt;br /&gt;
&lt;br /&gt;
==== Umwelt- und Ressourcenschutz ====&lt;br /&gt;
&lt;br /&gt;
Begründung:&lt;br /&gt;
&lt;br /&gt;
Wasser- und Energieeffizienz, robuste Solarversorgung, nachhaltige Bewässerung und klimatisch resiliente Landwirtschaft können dem Umwelt- und Ressourcenschutz dienen.&lt;br /&gt;
&lt;br /&gt;
==== Internationale technische Zusammenarbeit ====&lt;br /&gt;
&lt;br /&gt;
Begründung:&lt;br /&gt;
&lt;br /&gt;
Kooperationen mit NGOs, Hochschulen, lokalen Initiativen, Gemeinden, Technikern und öffentlichen Stellen können als praktische Umsetzung der Entwicklungszusammenarbeit dienen.&lt;br /&gt;
&lt;br /&gt;
== Gemeinnützigkeitsrechtliche Anforderungen ==&lt;br /&gt;
&lt;br /&gt;
Die Gemeinnützigkeit setzt voraus, dass der Verein seine Zwecke selbstlos, ausschließlich und unmittelbar verfolgt.&lt;br /&gt;
&lt;br /&gt;
=== Selbstlosigkeit ===&lt;br /&gt;
&lt;br /&gt;
Der Verein darf nicht in erster Linie eigenwirtschaftliche Zwecke verfolgen. § 55 AO beschreibt die Anforderungen an Selbstlosigkeit.&amp;lt;ref name=&amp;quot;AO55&amp;quot;&amp;gt;https://www.gesetze-im-internet.de/ao_1977/__55.html&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Praktisch bedeutet das:&lt;br /&gt;
&lt;br /&gt;
* keine Gewinnausschüttung an Mitglieder,&lt;br /&gt;
* keine unangemessenen Vergütungen,&lt;br /&gt;
* Mittelverwendung nur für satzungsmäßige Zwecke,&lt;br /&gt;
* keine verdeckte Förderung einzelner Unternehmen,&lt;br /&gt;
* keine private Aneignung von Vereinsvermögen,&lt;br /&gt;
* klare Regeln zu Interessenkonflikten.&lt;br /&gt;
&lt;br /&gt;
=== Ausschließlichkeit ===&lt;br /&gt;
&lt;br /&gt;
Der Verein darf seine Mittel grundsätzlich nur für seine steuerbegünstigten Satzungszwecke verwenden.&lt;br /&gt;
&lt;br /&gt;
Praktisch bedeutet das:&lt;br /&gt;
&lt;br /&gt;
* klare Projektbudgets,&lt;br /&gt;
* getrennte Buchführung für Spenden, Fördermittel und wirtschaftliche Aktivitäten,&lt;br /&gt;
* dokumentierte Mittelverwendung,&lt;br /&gt;
* keine Vermischung mit privaten oder unternehmerischen Interessen.&lt;br /&gt;
&lt;br /&gt;
=== Unmittelbarkeit ===&lt;br /&gt;
&lt;br /&gt;
Der Verein muss seine Zwecke grundsätzlich selbst verwirklichen.&lt;br /&gt;
&lt;br /&gt;
Das kann geschehen durch:&lt;br /&gt;
&lt;br /&gt;
* eigene Schulungen,&lt;br /&gt;
* eigene Dokumentation,&lt;br /&gt;
* eigene Standardentwicklung,&lt;br /&gt;
* eigene Pilotprojekte,&lt;br /&gt;
* eigene Kooperationen,&lt;br /&gt;
* eigene Projektbegleitung,&lt;br /&gt;
* eigene Evaluationen,&lt;br /&gt;
* rechtlich zulässige Mittelweitergabe an geeignete gemeinnützige oder öffentliche Partner.&lt;br /&gt;
&lt;br /&gt;
=== Satzungsbindung ===&lt;br /&gt;
&lt;br /&gt;
Die Satzung muss die gemeinnützigen Zwecke und deren Verwirklichung so genau beschreiben, dass das Finanzamt prüfen kann, ob die Voraussetzungen der Gemeinnützigkeit vorliegen.&lt;br /&gt;
&lt;br /&gt;
Die Mustersatzung aus Anlage 1 zur Abgabenordnung enthält zentrale Formulierungen, etwa zur Selbstlosigkeit, Mittelverwendung, Vermeidung unangemessener Begünstigungen und Vermögensbindung.&amp;lt;ref name=&amp;quot;AOMustersatzung&amp;quot;&amp;gt;https://www.gesetze-im-internet.de/ao_1977/anlage_1.html&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Vorschlag für den Vereinszweck ==&lt;br /&gt;
&lt;br /&gt;
Folgender Text ist ein Arbeitsentwurf und sollte vor Verwendung rechtlich und steuerlich geprüft werden.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
Zweck des Vereins ist die Förderung der Entwicklungszusammenarbeit, der Bildung, des Umwelt- und Ressourcenschutzes sowie der wissenschaftlich-technischen Zusammenarbeit.&lt;br /&gt;
&lt;br /&gt;
Der Satzungszweck wird insbesondere verwirklicht durch die Entwicklung, Pflege und Verbreitung offener technischer Standards für sichere, robuste und lokal betreibbare Wasser-, Bewässerungs- und Agrarinfrastruktur in ressourcenarmen Regionen.&lt;br /&gt;
&lt;br /&gt;
Der Verein verwirklicht seine Zwecke insbesondere durch:&lt;br /&gt;
&lt;br /&gt;
1. Entwicklung, Dokumentation und Pflege offener technischer Standards und Referenzarchitekturen;&lt;br /&gt;
2. Erstellung und Veröffentlichung von Schulungs-, Planungs- und Betriebsunterlagen;&lt;br /&gt;
3. Durchführung von Bildungs-, Trainings- und Qualifizierungsmaßnahmen für lokale Betreiber, Techniker, gemeinnützige Organisationen und Projektpartner;&lt;br /&gt;
4. Unterstützung von Pilot-, Demonstrations- und Modellprojekten im Bereich nachhaltiger Wasser-, Bewässerungs- und Agrarinfrastruktur;&lt;br /&gt;
5. Förderung von Wissenstransfer, technischer Selbstbefähigung und lokaler Wartbarkeit;&lt;br /&gt;
6. Kooperation mit gemeinnützigen Organisationen, Hochschulen, Forschungseinrichtungen, lokalen Initiativen, Gemeinden und öffentlichen Stellen;&lt;br /&gt;
7. Durchführung oder Unterstützung von Evaluierungen, Dokumentationen, Studien und Erfahrungsberichten;&lt;br /&gt;
8. Förderung transparenter, sicherer und auditierbarer Verfahren für Betrieb, Wartung, Qualitätssicherung und langfristige Weiterentwicklung entsprechender Infrastrukturen.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Zentrale Abgrenzung ==&lt;br /&gt;
&lt;br /&gt;
Der Verein sollte klar von einer wirtschaftlichen Produkt- oder Beratungsfirma abgegrenzt werden.&lt;br /&gt;
&lt;br /&gt;
=== Nicht empfehlenswert ===&lt;br /&gt;
&lt;br /&gt;
Der Verein sollte nicht so beschrieben werden:&lt;br /&gt;
&lt;br /&gt;
: Der Verein verkauft Bewässerungstechnik.&lt;br /&gt;
: Der Verein entwickelt kommerzielle Produkte.&lt;br /&gt;
: Der Verein zertifiziert gegen Entgelt im eigenen Marktinteresse.&lt;br /&gt;
: Der Verein ist Dienstleister für Implementierung und Betrieb kommerzieller Anlagen.&lt;br /&gt;
&lt;br /&gt;
=== Empfehlenswert ===&lt;br /&gt;
&lt;br /&gt;
Der Verein sollte so beschrieben werden:&lt;br /&gt;
&lt;br /&gt;
: Der Verein fördert gemeinnützige Entwicklungszusammenarbeit durch offene Standards, Bildung, Wissenstransfer, Pilotprojekte und technische Selbstbefähigung im Bereich nachhaltiger Wasser-, Bewässerungs- und Agrarinfrastruktur.&lt;br /&gt;
&lt;br /&gt;
Die technische Arbeit ist dabei Mittel zum gemeinnützigen Zweck, nicht Selbstzweck.&lt;br /&gt;
&lt;br /&gt;
== Mögliche Vereinsstruktur ==&lt;br /&gt;
&lt;br /&gt;
Die AOWIS-Governance beschreibt bereits Prinzipien wie Offenheit, Neutralität, Sicherheit, Praktikabilität, Rechenschaft, langfristige Stabilität und Einbeziehung lokaler Akteure.&amp;lt;ref name=&amp;quot;AOWISGovernance&amp;quot;&amp;gt;https://aowis.org/index.php/Governance:Main_Page&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Diese Logik lässt sich gut in eine Vereinsstruktur übertragen.&lt;br /&gt;
&lt;br /&gt;
=== Mitgliederversammlung ===&lt;br /&gt;
&lt;br /&gt;
Aufgaben:&lt;br /&gt;
&lt;br /&gt;
* Wahl und Abberufung des Vorstands,&lt;br /&gt;
* Beschluss über Satzungsänderungen,&lt;br /&gt;
* Entlastung des Vorstands,&lt;br /&gt;
* Beschluss über Beitragsordnung,&lt;br /&gt;
* strategische Grundsatzentscheidungen,&lt;br /&gt;
* Auflösung des Vereins.&lt;br /&gt;
&lt;br /&gt;
=== Vorstand nach § 26 BGB ===&lt;br /&gt;
&lt;br /&gt;
Aufgaben:&lt;br /&gt;
&lt;br /&gt;
* rechtliche Vertretung des Vereins,&lt;br /&gt;
* Finanzen und Buchhaltung,&lt;br /&gt;
* Gemeinnützigkeits- und Spendenverwaltung,&lt;br /&gt;
* Verträge und Kooperationen,&lt;br /&gt;
* Fördermittelmanagement,&lt;br /&gt;
* Kommunikation mit Finanzamt, Registergericht und Notar,&lt;br /&gt;
* operative Gesamtkoordination.&lt;br /&gt;
&lt;br /&gt;
Empfehlung:&lt;br /&gt;
&lt;br /&gt;
Der Vorstand sollte mindestens aus drei Personen bestehen:&lt;br /&gt;
&lt;br /&gt;
* Vorsitz,&lt;br /&gt;
* stellvertretender Vorsitz,&lt;br /&gt;
* Schatzmeister / Finanzen.&lt;br /&gt;
&lt;br /&gt;
Optional:&lt;br /&gt;
&lt;br /&gt;
* Vorstand für Technik und Standards,&lt;br /&gt;
* Vorstand für Internationale Zusammenarbeit,&lt;br /&gt;
* Vorstand für Bildung und Programme.&lt;br /&gt;
&lt;br /&gt;
=== Technischer Beirat ===&lt;br /&gt;
&lt;br /&gt;
Aufgaben:&lt;br /&gt;
&lt;br /&gt;
* technische Qualitätssicherung,&lt;br /&gt;
* Standardpflege,&lt;br /&gt;
* Prüfung von Sicherheitsanforderungen,&lt;br /&gt;
* Modul- und Architekturentscheidungen,&lt;br /&gt;
* Bewertung von Referenzimplementierungen,&lt;br /&gt;
* Schutz vor herstellerabhängiger Vereinnahmung.&lt;br /&gt;
&lt;br /&gt;
Mögliche Fachbereiche:&lt;br /&gt;
&lt;br /&gt;
* Wasserverteilung,&lt;br /&gt;
* Bewässerung,&lt;br /&gt;
* Solar- und Energiesysteme,&lt;br /&gt;
* Sensorik und Telemetrie,&lt;br /&gt;
* Offline-Kommunikation,&lt;br /&gt;
* Sicherheits- und Notfalllogik,&lt;br /&gt;
* Datenmodelle und Dokumentation,&lt;br /&gt;
* Open-Source- und Lizenzfragen.&lt;br /&gt;
&lt;br /&gt;
=== Field Advisory Council / Praxisbeirat ===&lt;br /&gt;
&lt;br /&gt;
Aufgaben:&lt;br /&gt;
&lt;br /&gt;
* Einbindung von lokalen Betreibern,&lt;br /&gt;
* Einbindung von NGOs,&lt;br /&gt;
* Rückmeldung aus realen Einsatzregionen,&lt;br /&gt;
* Prüfung praktischer Nutzbarkeit,&lt;br /&gt;
* Vermeidung rein fernentwickelter Lösungen,&lt;br /&gt;
* kulturelle und lokale Anschlussfähigkeit.&lt;br /&gt;
&lt;br /&gt;
Dieser Bereich ist für Entwicklungszusammenarbeit besonders wichtig, weil Standards, die Gemeinschaften betreffen, nicht nur aus der Ferne entworfen werden sollten.&amp;lt;ref name=&amp;quot;AOWISGovernance&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Arbeitsgruppen ===&lt;br /&gt;
&lt;br /&gt;
Mögliche Arbeitsgruppen:&lt;br /&gt;
&lt;br /&gt;
* AG Vereinsgründung und Satzung,&lt;br /&gt;
* AG Gemeinnützigkeit und Compliance,&lt;br /&gt;
* AG Technischer Standard,&lt;br /&gt;
* AG Training und Dokumentation,&lt;br /&gt;
* AG Pilotprojekte,&lt;br /&gt;
* AG Partnerschaften und Fördermittel,&lt;br /&gt;
* AG Übersetzung und lokale Anpassung,&lt;br /&gt;
* AG Evaluation und Monitoring.&lt;br /&gt;
&lt;br /&gt;
=== Compliance- und Interessenkonflikt-Struktur ===&lt;br /&gt;
&lt;br /&gt;
Aufgaben:&lt;br /&gt;
&lt;br /&gt;
* Offenlegung finanzieller oder organisatorischer Interessen,&lt;br /&gt;
* Schutz der Neutralität des Standards,&lt;br /&gt;
* Prüfung von Beschaffungs- und Zertifizierungsfragen,&lt;br /&gt;
* klare Trennung zwischen gemeinnütziger Tätigkeit und wirtschaftlichen Interessen,&lt;br /&gt;
* Dokumentation von Entscheidungen,&lt;br /&gt;
* Vermeidung einseitiger Kontrolle durch einzelne Personen, Unternehmen oder Geldgeber.&lt;br /&gt;
&lt;br /&gt;
Die AOWIS-Governance betont, dass der Standard nicht durch ein einzelnes Unternehmen, politische Akteure, Geberorganisationen oder Einzelpersonen kontrolliert werden soll.&amp;lt;ref name=&amp;quot;AOWISGovernance&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Gründungsschritte ==&lt;br /&gt;
&lt;br /&gt;
=== Schritt 1: Gründungsteam bilden ===&lt;br /&gt;
&lt;br /&gt;
Erforderlich für die Eintragung:&lt;br /&gt;
&lt;br /&gt;
* mindestens sieben Gründungsmitglieder,&lt;br /&gt;
* Bereitschaft zur Unterzeichnung der Satzung,&lt;br /&gt;
* Bereitschaft zur Teilnahme an der Gründungsversammlung.&lt;br /&gt;
&lt;br /&gt;
Empfohlen:&lt;br /&gt;
&lt;br /&gt;
* mindestens eine Person mit Finanz-/Buchhaltungskompetenz,&lt;br /&gt;
* mindestens eine Person mit technischer Kompetenz,&lt;br /&gt;
* mindestens eine Person mit Erfahrung in Entwicklungszusammenarbeit, NGO-Arbeit oder Projektkoordination,&lt;br /&gt;
* mindestens eine Person mit Kommunikations- oder Dokumentationskompetenz.&lt;br /&gt;
&lt;br /&gt;
=== Schritt 2: Vereinsname und Sitz festlegen ===&lt;br /&gt;
&lt;br /&gt;
Zu klären:&lt;br /&gt;
&lt;br /&gt;
* Name des Vereins,&lt;br /&gt;
* Kurzname,&lt;br /&gt;
* Sitz des Vereins,&lt;br /&gt;
* Eintragungsabsicht als e. V.,&lt;br /&gt;
* Gemeinnützigkeitsabsicht,&lt;br /&gt;
* Domain- und Markenfragen&lt;br /&gt;
&lt;br /&gt;
=== Schritt 3: Satzung entwerfen ===&lt;br /&gt;
&lt;br /&gt;
Die Satzung sollte mindestens regeln:&lt;br /&gt;
&lt;br /&gt;
* Name,&lt;br /&gt;
* Sitz,&lt;br /&gt;
* Eintragung ins Vereinsregister,&lt;br /&gt;
* Vereinszweck,&lt;br /&gt;
* Art der Zweckverwirklichung,&lt;br /&gt;
* Gemeinnützigkeit,&lt;br /&gt;
* Selbstlosigkeit,&lt;br /&gt;
* Mittelverwendung,&lt;br /&gt;
* Vermögensbindung,&lt;br /&gt;
* Mitgliedschaft,&lt;br /&gt;
* Rechte und Pflichten der Mitglieder,&lt;br /&gt;
* Beiträge,&lt;br /&gt;
* Beendigung der Mitgliedschaft,&lt;br /&gt;
* Organe des Vereins,&lt;br /&gt;
* Mitgliederversammlung,&lt;br /&gt;
* Vorstand,&lt;br /&gt;
* Vertretungsregelung,&lt;br /&gt;
* Beschlussfassung,&lt;br /&gt;
* Satzungsänderungen,&lt;br /&gt;
* Auflösung des Vereins,&lt;br /&gt;
* Protokollierung,&lt;br /&gt;
* Datenschutz und digitale Versammlungen, falls gewünscht.&lt;br /&gt;
&lt;br /&gt;
Das Bundesministerium der Justiz stellt Muster zum Vereinsrecht bereit, darunter eine Mustersatzung, ein Gründungsprotokoll und Muster für die Anmeldung zum Vereinsregister.&amp;lt;ref name=&amp;quot;BMJVereinsrecht&amp;quot;&amp;gt;https://www.bmjv.de/DE/service/formulare/muster_vereinsrecht/muster_vereinsrecht_node.html&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Schritt 4: Vorabprüfung durch das Finanzamt ===&lt;br /&gt;
&lt;br /&gt;
Vor der Gründungsversammlung sollte der Satzungsentwurf dem zuständigen Finanzamt zur Vorabprüfung vorgelegt werden.&lt;br /&gt;
&lt;br /&gt;
Ziel:&lt;br /&gt;
&lt;br /&gt;
* Prüfung der gemeinnützigkeitsrechtlichen Formulierungen,&lt;br /&gt;
* Vermeidung späterer Satzungsänderungen,&lt;br /&gt;
* bessere Sicherheit bei Spenden- und Förderfähigkeit,&lt;br /&gt;
* Klärung der passenden gemeinnützigen Zwecke.&lt;br /&gt;
&lt;br /&gt;
=== Schritt 5: Gründungsversammlung durchführen ===&lt;br /&gt;
&lt;br /&gt;
Tagesordnung:&lt;br /&gt;
&lt;br /&gt;
# Eröffnung und Feststellung der Anwesenheit,&lt;br /&gt;
# Wahl der Versammlungsleitung,&lt;br /&gt;
# Wahl der Protokollführung,&lt;br /&gt;
# Vorstellung des Vereinszwecks,&lt;br /&gt;
# Beratung und Beschluss der Satzung,&lt;br /&gt;
# Wahl des Vorstands,&lt;br /&gt;
# Beschluss über Vereinsregistereintragung,&lt;br /&gt;
# Beschluss über Beantragung der Gemeinnützigkeit,&lt;br /&gt;
# Beschluss über Beitragsordnung, falls vorgesehen,&lt;br /&gt;
# weitere organisatorische Beschlüsse.&lt;br /&gt;
&lt;br /&gt;
Erforderlich:&lt;br /&gt;
&lt;br /&gt;
* Anwesenheitsliste,&lt;br /&gt;
* beschlossene Satzung,&lt;br /&gt;
* Unterschriften der Gründungsmitglieder,&lt;br /&gt;
* Gründungsprotokoll,&lt;br /&gt;
* Vorstandswahl mit Annahme der Wahl.&lt;br /&gt;
&lt;br /&gt;
=== Schritt 6: Notar und Vereinsregister ===&lt;br /&gt;
&lt;br /&gt;
Der gewählte Vorstand meldet den Verein über einen Notar beim Vereinsregister an.&lt;br /&gt;
&lt;br /&gt;
Typische Unterlagen:&lt;br /&gt;
&lt;br /&gt;
* Satzung,&lt;br /&gt;
* Gründungsprotokoll,&lt;br /&gt;
* Nachweis der Vorstandswahl,&lt;br /&gt;
* Anmeldung zum Vereinsregister,&lt;br /&gt;
* Angaben zu vertretungsberechtigten Vorstandsmitgliedern.&lt;br /&gt;
&lt;br /&gt;
=== Schritt 7: Gemeinnützigkeit beantragen ===&lt;br /&gt;
&lt;br /&gt;
Nach der Gründung beziehungsweise nach Eintragung wird beim Finanzamt die Gemeinnützigkeit beantragt.&lt;br /&gt;
&lt;br /&gt;
Ziel ist die Feststellung der satzungsmäßigen Voraussetzungen der Gemeinnützigkeit nach § 60a AO.&amp;lt;ref name=&amp;quot;AOInhalt&amp;quot;&amp;gt;https://www.gesetze-im-internet.de/ao_1977/inhalts_bersicht.html&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Nach Anerkennung kann der Verein grundsätzlich:&lt;br /&gt;
&lt;br /&gt;
* Spendenbescheinigungen ausstellen,&lt;br /&gt;
* steuerbegünstigte Mittel empfangen,&lt;br /&gt;
* Fördermittel beantragen,&lt;br /&gt;
* gegenüber Partnern als gemeinnützige Organisation auftreten.&lt;br /&gt;
&lt;br /&gt;
=== Schritt 8: Betrieb aufsetzen ===&lt;br /&gt;
&lt;br /&gt;
Notwendig:&lt;br /&gt;
&lt;br /&gt;
* Vereinskonto,&lt;br /&gt;
* Buchhaltung,&lt;br /&gt;
* Belegsystem,&lt;br /&gt;
* Spendenverwaltung,&lt;br /&gt;
* Datenschutzgrundlagen,&lt;br /&gt;
* Mitgliederverwaltung,&lt;br /&gt;
* Projektakten,&lt;br /&gt;
* Mittelverwendungsnachweise,&lt;br /&gt;
* Dokumentationsstruktur,&lt;br /&gt;
* interne Freigabeprozesse,&lt;br /&gt;
* Interessenkonflikt-Policy,&lt;br /&gt;
* Fördermittel- und Partnerprüfung.&lt;br /&gt;
&lt;br /&gt;
== Einnahmen und wirtschaftliche Tätigkeiten ==&lt;br /&gt;
&lt;br /&gt;
Ein gemeinnütziger Verein darf Einnahmen haben. Entscheidend ist, wie diese steuerlich einzuordnen sind.&lt;br /&gt;
&lt;br /&gt;
Mögliche Einnahmen:&lt;br /&gt;
&lt;br /&gt;
* Mitgliedsbeiträge,&lt;br /&gt;
* Spenden,&lt;br /&gt;
* Fördermittel,&lt;br /&gt;
* Zuschüsse,&lt;br /&gt;
* projektbezogene Mittel,&lt;br /&gt;
* Teilnahmebeiträge für Schulungen,&lt;br /&gt;
* Verkauf von Materialien zum Selbstkostenpreis,&lt;br /&gt;
* Aufwandsersatz,&lt;br /&gt;
* zweckbezogene Beratungsleistungen.&lt;br /&gt;
&lt;br /&gt;
Zu prüfen ist jeweils, ob es sich handelt um:&lt;br /&gt;
&lt;br /&gt;
* ideellen Bereich,&lt;br /&gt;
* Zweckbetrieb,&lt;br /&gt;
* Vermögensverwaltung,&lt;br /&gt;
* wirtschaftlichen Geschäftsbetrieb.&lt;br /&gt;
&lt;br /&gt;
Besonders sensibel sind:&lt;br /&gt;
&lt;br /&gt;
* Zertifizierungen gegen Entgelt,&lt;br /&gt;
* technische Beratung gegen Entgelt,&lt;br /&gt;
* Implementierungsbegleitung gegen Entgelt,&lt;br /&gt;
* Verkauf von Hardware,&lt;br /&gt;
* exklusive Kooperationen mit Unternehmen,&lt;br /&gt;
* Einflussnahme auf Beschaffung oder Lieferantenauswahl.&lt;br /&gt;
&lt;br /&gt;
Empfehlung:&lt;br /&gt;
&lt;br /&gt;
Wirtschaftliche Tätigkeiten sollten nicht in der Gründungsphase dominant sein. Zunächst sollte der Verein klar gemeinnützig und standard-/bildungsorientiert aufgestellt werden.&lt;br /&gt;
&lt;br /&gt;
== Risiken und Gegenmaßnahmen ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Risiko&lt;br /&gt;
! Beschreibung&lt;br /&gt;
! Gegenmaßnahme&lt;br /&gt;
|-&lt;br /&gt;
| Verdeckte wirtschaftliche Tätigkeit&lt;br /&gt;
| Der Verein wirkt wie eine Firma im Vereinsmantel.&lt;br /&gt;
| Klare Satzung, transparente Mittelverwendung, keine Produktverkaufslogik.&lt;br /&gt;
|-&lt;br /&gt;
| Herstellerabhängigkeit&lt;br /&gt;
| Ein Unternehmen kontrolliert Standard, Zertifizierung oder Beschaffung.&lt;br /&gt;
| Offenlegung von Interessen, technischer Beirat, transparente Governance.&lt;br /&gt;
|-&lt;br /&gt;
| Zu breiter Satzungszweck&lt;br /&gt;
| Zu viele Zwecke wirken beliebig und schwer prüfbar.&lt;br /&gt;
| Entwicklungszusammenarbeit als Hauptzweck; Ergänzungen nur bei realer Umsetzung.&lt;br /&gt;
|-&lt;br /&gt;
| Fehlende lokale Legitimität&lt;br /&gt;
| Lösungen werden nur aus Europa heraus entworfen.&lt;br /&gt;
| Praxisbeirat mit lokalen Betreibern, NGOs und Technikern.&lt;br /&gt;
|-&lt;br /&gt;
| Unklare Mittelweitergabe&lt;br /&gt;
| Gelder fließen an ausländische Partner ohne ausreichende Dokumentation.&lt;br /&gt;
| Verträge, Projektberichte, Belege, Partnerprüfung, Mittelverwendungsnachweise.&lt;br /&gt;
|-&lt;br /&gt;
| Unklare IP- und Lizenzfragen&lt;br /&gt;
| Open Standard, Software, Dokumentation und Markenrechte sind nicht geregelt.&lt;br /&gt;
| Lizenzkonzept, Contributor-Regeln, Marken- und Namensstrategie.&lt;br /&gt;
|-&lt;br /&gt;
| Schwache Dokumentation&lt;br /&gt;
| Gemeinnützigkeit scheitert später an fehlenden Nachweisen.&lt;br /&gt;
| Projektakten, Beschlüsse, Finanzdokumentation, Wirkungsberichte.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Sofort umsetzbare Aufgabenliste ==&lt;br /&gt;
&lt;br /&gt;
=== Für den CEO ===&lt;br /&gt;
&lt;br /&gt;
* finalen Vereinsnamen vorschlagen: &#039;&#039;&#039;AOWIS.org&#039;&#039;&#039; bzw. &#039;&#039;&#039;AOWIS&#039;&#039;&#039;&lt;br /&gt;
* Sitz des Vereins klären,&lt;br /&gt;
* Gründungsteam mit mindestens sieben Personen identifizieren,&lt;br /&gt;
* Rollen für Vorstand und Beirat vorschlagen,&lt;br /&gt;
* Satzungszweck finalisieren,&lt;br /&gt;
* Finanzamt für Vorabprüfung bestimmen,&lt;br /&gt;
* Notar oder Registergericht-Zuständigkeit klären,&lt;br /&gt;
&lt;br /&gt;
=== Für das Team ===&lt;br /&gt;
&lt;br /&gt;
* Satzungsentwurf erstellen,&lt;br /&gt;
* Beitragsordnung entwerfen,&lt;br /&gt;
* Gründungsprotokoll vorbereiten,&lt;br /&gt;
* Mitgliederliste vorbereiten,&lt;br /&gt;
* Governance-Struktur entwerfen,&lt;br /&gt;
* Interessenkonflikt-Erklärung entwerfen,&lt;br /&gt;
* Projektbeschreibung auf 1–2 Seiten formulieren,&lt;br /&gt;
* Finanzplan für das erste Jahr erstellen,&lt;br /&gt;
* Liste möglicher Partner und Fördermittelgeber erstellen.&lt;br /&gt;
&lt;br /&gt;
== Mögliche Kurzbeschreibung des Vereins ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
Der Verein fördert Entwicklungszusammenarbeit durch offene technische Standards, Bildung und Wissenstransfer im Bereich nachhaltiger Wasser-, Bewässerungs- und Agrarinfrastruktur. Ziel ist es, lokale Initiativen, gemeinnützige Organisationen, Betreiber und technische Fachkräfte in ressourcenarmen Regionen dabei zu unterstützen, robuste, sichere, wartbare und unabhängig betreibbare Infrastrukturen aufzubauen und langfristig zu erhalten.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Mögliche Langbeschreibung des Vereins ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
Der Verein versteht sich als gemeinnütziger Träger für die Entwicklung, Pflege und Verbreitung offener Standards für Wasser-, Bewässerungs- und Agrarinfrastruktur in ressourcenarmen und entwicklungsrelevanten Regionen. Im Mittelpunkt stehen robuste, sichere, lokal wartbare und herstellerunabhängige Systeme, die auch bei instabiler Stromversorgung, eingeschränkter Konnektivität und begrenzter technischer Unterstützung betrieben werden können.&lt;br /&gt;
&lt;br /&gt;
Der Verein fördert Entwicklungszusammenarbeit durch technische Dokumentation, Schulung, Wissenstransfer, Pilotprojekte, Forschung, Evaluation und Kooperation mit lokalen Initiativen, NGOs, Hochschulen und öffentlichen Stellen. Ziel ist nicht der Verkauf technischer Produkte, sondern die gemeinnützige Befähigung lokaler Akteure zur Planung, zum Betrieb, zur Wartung und zur Weiterentwicklung nachhaltiger Infrastruktur.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Empfehlung für die nächste Arbeitsphase ==&lt;br /&gt;
&lt;br /&gt;
Die nächsten drei Dokumente sollten vorbereitet werden:&lt;br /&gt;
&lt;br /&gt;
# &#039;&#039;&#039;Satzungsentwurf&#039;&#039;&#039; mit gemeinnützigkeitsrechtlich geprüften Formulierungen.&lt;br /&gt;
# &#039;&#039;&#039;Gründungsprotokoll&#039;&#039;&#039; für die erste Mitgliederversammlung.&lt;br /&gt;
# &#039;&#039;&#039;1-seitige Projektbeschreibung&#039;&#039;&#039; für Finanzamt, Gründungsmitglieder und mögliche Partner.&lt;br /&gt;
&lt;br /&gt;
Erst danach sollte die Gründungsversammlung angesetzt werden.&lt;br /&gt;
&lt;br /&gt;
== Quellen ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Kategorie:AOWIS]]&lt;br /&gt;
[[Kategorie:Vereinsgründung]]&lt;br /&gt;
[[Kategorie:Gemeinnützigkeit]]&lt;br /&gt;
[[Kategorie:Entwicklungszusammenarbeit]]&lt;br /&gt;
[[Kategorie:Governance]]&lt;/div&gt;</summary>
		<author><name>Samuel</name></author>
	</entry>
	<entry>
		<id>https://aowis.org/index.php?title=Governance:Non-Profit-Association&amp;diff=786</id>
		<title>Governance:Non-Profit-Association</title>
		<link rel="alternate" type="text/html" href="https://aowis.org/index.php?title=Governance:Non-Profit-Association&amp;diff=786"/>
		<updated>2026-10-05T12:21:14Z</updated>

		<summary type="html">&lt;p&gt;Samuel: /* Projektbezug */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
{{AI-Generated&lt;br /&gt;
 | tool=ChatGPT&lt;br /&gt;
 | date=2026-06-09&lt;br /&gt;
 | scope=full page&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
= Konzept zur Vereinsgründung für AOWIS =&lt;br /&gt;
&lt;br /&gt;
== Kurzfassung ==&lt;br /&gt;
&lt;br /&gt;
Für das Projekt AOWIS erscheint ein &#039;&#039;&#039;gemeinnütziger eingetragener Verein (e. V.)&#039;&#039;&#039; als geeignete Grundstruktur.&lt;br /&gt;
&lt;br /&gt;
Der Verein sollte nicht als Anbieter oder Verkäufer von Bewässerungs- oder Wassertechnik auftreten, sondern als gemeinnütziger Träger für:&lt;br /&gt;
&lt;br /&gt;
* offene technische Standards,&lt;br /&gt;
* Entwicklungszusammenarbeit,&lt;br /&gt;
* Wissenstransfer,&lt;br /&gt;
* Ausbildung lokaler Betreiber und Techniker,&lt;br /&gt;
* Pilot- und Demonstrationsprojekte,&lt;br /&gt;
* Dokumentation, Forschung und Qualitätssicherung,&lt;br /&gt;
* nachhaltige Wasser-, Bewässerungs- und Agrarinfrastruktur in ressourcenarmen Regionen.&lt;br /&gt;
&lt;br /&gt;
Der stärkste gemeinnützigkeitsrechtliche Hauptzweck ist die &#039;&#039;&#039;Förderung der Entwicklungszusammenarbeit&#039;&#039;&#039;. Dieser Zweck ist in § 52 Abs. 2 Nr. 15 Abgabenordnung ausdrücklich als gemeinnütziger Zweck genannt.&amp;lt;ref name=&amp;quot;AO52&amp;quot;&amp;gt;https://www.gesetze-im-internet.de/ao_1977/__52.html&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Ergänzend können — soweit tatsächlich umgesetzt — folgende gemeinnützige Zwecke aufgenommen werden:&lt;br /&gt;
&lt;br /&gt;
* Förderung von Bildung und Berufsbildung,&lt;br /&gt;
* Förderung von Wissenschaft und Forschung,&lt;br /&gt;
* Förderung des Umwelt- und Ressourcenschutzes,&lt;br /&gt;
* Förderung internationaler technischer Zusammenarbeit.&lt;br /&gt;
&lt;br /&gt;
== Projektbezug ==&lt;br /&gt;
&lt;br /&gt;
AOWIS steht für &#039;&#039;&#039;Afritic Open Water Infrastructure System&#039;&#039;&#039; und beschreibt einen offenen technischen Standard für sichere und zuverlässige Wasser- und landwirtschaftliche Infrastruktur in ressourcenarmen Umgebungen.&amp;lt;ref name=&amp;quot;AOWISMain&amp;quot;&amp;gt;https://aowis.org/index.php/Main_Page&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Die Projektlogik ist besonders relevant für Regionen mit:&lt;br /&gt;
&lt;br /&gt;
* instabiler Stromversorgung,&lt;br /&gt;
* eingeschränkter Internetverbindung,&lt;br /&gt;
* knappen technischen Ressourcen,&lt;br /&gt;
* begrenzter Verfügbarkeit qualifizierter Fachkräfte,&lt;br /&gt;
* Bedarf an sicherem, robustem und lokal betreibbarem Betrieb,&lt;br /&gt;
* Problemen bei Wasserverteilung, Bewässerung und landwirtschaftlicher Infrastruktur.&lt;br /&gt;
&lt;br /&gt;
AOWIS verfolgt dabei keine reine Produktlogik. Der Kern liegt in offenen Standards, Planung, Betrieb, Monitoring, Wartung, Training, Governance, Transparenz und lokaler Nutzbarkeit.&amp;lt;ref name=&amp;quot;AOWISMain&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Für eine Vereinsgründung bedeutet das:&lt;br /&gt;
&lt;br /&gt;
: Der Verein sollte nicht primär Technik verkaufen, sondern gemeinnützige Voraussetzungen schaffen, damit robuste Wasser-, Bewässerungs- und Agrarsysteme in entwicklungsrelevanten Regionen sicher, offen, lokal betreibbar und langfristig wartbar werden.&lt;br /&gt;
&lt;br /&gt;
== Empfohlene Rechtsform ==&lt;br /&gt;
&lt;br /&gt;
Empfohlen wird die Gründung eines:&lt;br /&gt;
&lt;br /&gt;
: &#039;&#039;&#039;eingetragenen gemeinnützigen Vereins&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
also eines:&lt;br /&gt;
&lt;br /&gt;
: &#039;&#039;&#039;e. V. mit angestrebter Anerkennung als gemeinnützig&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Ein eingetragener Verein eignet sich besonders, wenn:&lt;br /&gt;
&lt;br /&gt;
* ideelle und gemeinnützige Zwecke im Vordergrund stehen,&lt;br /&gt;
* Mitglieder, Förderer, technische Beitragende und Partner eingebunden werden sollen,&lt;br /&gt;
* Spenden und Fördermittel eingeworben werden sollen,&lt;br /&gt;
* eine transparente Governance-Struktur entstehen soll,&lt;br /&gt;
* der Verein unabhängig von einzelnen Unternehmen oder Personen handeln soll.&lt;br /&gt;
&lt;br /&gt;
Für die Eintragung ins Vereinsregister sind mindestens sieben Mitglieder erforderlich. § 56 BGB bestimmt, dass die Eintragung nur erfolgen soll, wenn die Zahl der Mitglieder mindestens sieben beträgt.&amp;lt;ref name=&amp;quot;BGB56&amp;quot;&amp;gt;https://www.gesetze-im-internet.de/bgb/__56.html&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Gemeinnützigkeitslogik ==&lt;br /&gt;
&lt;br /&gt;
=== Hauptzweck ===&lt;br /&gt;
&lt;br /&gt;
Als Hauptzweck wird empfohlen:&lt;br /&gt;
&lt;br /&gt;
: &#039;&#039;&#039;Förderung der Entwicklungszusammenarbeit&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Begründung:&lt;br /&gt;
&lt;br /&gt;
AOWIS richtet sich auf Wasser-, Bewässerungs- und Agrarinfrastruktur in ressourcenarmen Regionen. Die Projektziele berühren damit zentrale Felder der Entwicklungszusammenarbeit:&lt;br /&gt;
&lt;br /&gt;
* Zugang zu sicherer und wartbarer Wasserinfrastruktur,&lt;br /&gt;
* Unterstützung lokaler Betreiber und Initiativen,&lt;br /&gt;
* technische Befähigung vor Ort,&lt;br /&gt;
* nachhaltige Landwirtschaft,&lt;br /&gt;
* resiliente Infrastruktur,&lt;br /&gt;
* Reduktion von Abhängigkeit von einzelnen Herstellern,&lt;br /&gt;
* Wissenstransfer und lokale Selbstbefähigung.&lt;br /&gt;
&lt;br /&gt;
=== Ergänzende Zwecke ===&lt;br /&gt;
&lt;br /&gt;
Je nach tatsächlicher Tätigkeit können ergänzend aufgenommen werden:&lt;br /&gt;
&lt;br /&gt;
==== Bildung und Berufsbildung ====&lt;br /&gt;
&lt;br /&gt;
Begründung:&lt;br /&gt;
&lt;br /&gt;
AOWIS sieht Training lokaler Techniker, Betreiber und Initiativen vor. Der Verein kann Schulungen, Lehrmaterial, Handbücher, Workshops und Ausbildungsprogramme entwickeln.&lt;br /&gt;
&lt;br /&gt;
==== Wissenschaft und Forschung ====&lt;br /&gt;
&lt;br /&gt;
Begründung:&lt;br /&gt;
&lt;br /&gt;
Der Verein kann offene Standards, Referenzarchitekturen, technische Dokumentation, Evaluierungen, Studien, Datenmodelle und Pilotprojekte entwickeln oder fördern.&lt;br /&gt;
&lt;br /&gt;
Wichtig:&lt;br /&gt;
&lt;br /&gt;
Dieser Zweck sollte nur aufgenommen werden, wenn tatsächlich Forschungs- oder Entwicklungsarbeit mit dokumentierter Methodik, Ergebnisoffenheit und Veröffentlichung geplant ist.&lt;br /&gt;
&lt;br /&gt;
==== Umwelt- und Ressourcenschutz ====&lt;br /&gt;
&lt;br /&gt;
Begründung:&lt;br /&gt;
&lt;br /&gt;
Wasser- und Energieeffizienz, robuste Solarversorgung, nachhaltige Bewässerung und klimatisch resiliente Landwirtschaft können dem Umwelt- und Ressourcenschutz dienen.&lt;br /&gt;
&lt;br /&gt;
==== Internationale technische Zusammenarbeit ====&lt;br /&gt;
&lt;br /&gt;
Begründung:&lt;br /&gt;
&lt;br /&gt;
Kooperationen mit NGOs, Hochschulen, lokalen Initiativen, Gemeinden, Technikern und öffentlichen Stellen können als praktische Umsetzung der Entwicklungszusammenarbeit dienen.&lt;br /&gt;
&lt;br /&gt;
== Gemeinnützigkeitsrechtliche Anforderungen ==&lt;br /&gt;
&lt;br /&gt;
Die Gemeinnützigkeit setzt voraus, dass der Verein seine Zwecke selbstlos, ausschließlich und unmittelbar verfolgt.&lt;br /&gt;
&lt;br /&gt;
=== Selbstlosigkeit ===&lt;br /&gt;
&lt;br /&gt;
Der Verein darf nicht in erster Linie eigenwirtschaftliche Zwecke verfolgen. § 55 AO beschreibt die Anforderungen an Selbstlosigkeit.&amp;lt;ref name=&amp;quot;AO55&amp;quot;&amp;gt;https://www.gesetze-im-internet.de/ao_1977/__55.html&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Praktisch bedeutet das:&lt;br /&gt;
&lt;br /&gt;
* keine Gewinnausschüttung an Mitglieder,&lt;br /&gt;
* keine unangemessenen Vergütungen,&lt;br /&gt;
* Mittelverwendung nur für satzungsmäßige Zwecke,&lt;br /&gt;
* keine verdeckte Förderung einzelner Unternehmen,&lt;br /&gt;
* keine private Aneignung von Vereinsvermögen,&lt;br /&gt;
* klare Regeln zu Interessenkonflikten.&lt;br /&gt;
&lt;br /&gt;
=== Ausschließlichkeit ===&lt;br /&gt;
&lt;br /&gt;
Der Verein darf seine Mittel grundsätzlich nur für seine steuerbegünstigten Satzungszwecke verwenden.&lt;br /&gt;
&lt;br /&gt;
Praktisch bedeutet das:&lt;br /&gt;
&lt;br /&gt;
* klare Projektbudgets,&lt;br /&gt;
* getrennte Buchführung für Spenden, Fördermittel und wirtschaftliche Aktivitäten,&lt;br /&gt;
* dokumentierte Mittelverwendung,&lt;br /&gt;
* keine Vermischung mit privaten oder unternehmerischen Interessen.&lt;br /&gt;
&lt;br /&gt;
=== Unmittelbarkeit ===&lt;br /&gt;
&lt;br /&gt;
Der Verein muss seine Zwecke grundsätzlich selbst verwirklichen.&lt;br /&gt;
&lt;br /&gt;
Das kann geschehen durch:&lt;br /&gt;
&lt;br /&gt;
* eigene Schulungen,&lt;br /&gt;
* eigene Dokumentation,&lt;br /&gt;
* eigene Standardentwicklung,&lt;br /&gt;
* eigene Pilotprojekte,&lt;br /&gt;
* eigene Kooperationen,&lt;br /&gt;
* eigene Projektbegleitung,&lt;br /&gt;
* eigene Evaluationen,&lt;br /&gt;
* rechtlich zulässige Mittelweitergabe an geeignete gemeinnützige oder öffentliche Partner.&lt;br /&gt;
&lt;br /&gt;
=== Satzungsbindung ===&lt;br /&gt;
&lt;br /&gt;
Die Satzung muss die gemeinnützigen Zwecke und deren Verwirklichung so genau beschreiben, dass das Finanzamt prüfen kann, ob die Voraussetzungen der Gemeinnützigkeit vorliegen.&lt;br /&gt;
&lt;br /&gt;
Die Mustersatzung aus Anlage 1 zur Abgabenordnung enthält zentrale Formulierungen, etwa zur Selbstlosigkeit, Mittelverwendung, Vermeidung unangemessener Begünstigungen und Vermögensbindung.&amp;lt;ref name=&amp;quot;AOMustersatzung&amp;quot;&amp;gt;https://www.gesetze-im-internet.de/ao_1977/anlage_1.html&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Vorschlag für den Vereinszweck ==&lt;br /&gt;
&lt;br /&gt;
Folgender Text ist ein Arbeitsentwurf und sollte vor Verwendung rechtlich und steuerlich geprüft werden.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
Zweck des Vereins ist die Förderung der Entwicklungszusammenarbeit, der Bildung, des Umwelt- und Ressourcenschutzes sowie der wissenschaftlich-technischen Zusammenarbeit.&lt;br /&gt;
&lt;br /&gt;
Der Satzungszweck wird insbesondere verwirklicht durch die Entwicklung, Pflege und Verbreitung offener technischer Standards für sichere, robuste und lokal betreibbare Wasser-, Bewässerungs- und Agrarinfrastruktur in ressourcenarmen Regionen.&lt;br /&gt;
&lt;br /&gt;
Der Verein verwirklicht seine Zwecke insbesondere durch:&lt;br /&gt;
&lt;br /&gt;
1. Entwicklung, Dokumentation und Pflege offener technischer Standards und Referenzarchitekturen;&lt;br /&gt;
2. Erstellung und Veröffentlichung von Schulungs-, Planungs- und Betriebsunterlagen;&lt;br /&gt;
3. Durchführung von Bildungs-, Trainings- und Qualifizierungsmaßnahmen für lokale Betreiber, Techniker, gemeinnützige Organisationen und Projektpartner;&lt;br /&gt;
4. Unterstützung von Pilot-, Demonstrations- und Modellprojekten im Bereich nachhaltiger Wasser-, Bewässerungs- und Agrarinfrastruktur;&lt;br /&gt;
5. Förderung von Wissenstransfer, technischer Selbstbefähigung und lokaler Wartbarkeit;&lt;br /&gt;
6. Kooperation mit gemeinnützigen Organisationen, Hochschulen, Forschungseinrichtungen, lokalen Initiativen, Gemeinden und öffentlichen Stellen;&lt;br /&gt;
7. Durchführung oder Unterstützung von Evaluierungen, Dokumentationen, Studien und Erfahrungsberichten;&lt;br /&gt;
8. Förderung transparenter, sicherer und auditierbarer Verfahren für Betrieb, Wartung, Qualitätssicherung und langfristige Weiterentwicklung entsprechender Infrastrukturen.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Zentrale Abgrenzung ==&lt;br /&gt;
&lt;br /&gt;
Der Verein sollte klar von einer wirtschaftlichen Produkt- oder Beratungsfirma abgegrenzt werden.&lt;br /&gt;
&lt;br /&gt;
=== Nicht empfehlenswert ===&lt;br /&gt;
&lt;br /&gt;
Der Verein sollte nicht so beschrieben werden:&lt;br /&gt;
&lt;br /&gt;
: Der Verein verkauft Bewässerungstechnik.&lt;br /&gt;
: Der Verein entwickelt kommerzielle Produkte.&lt;br /&gt;
: Der Verein zertifiziert gegen Entgelt im eigenen Marktinteresse.&lt;br /&gt;
: Der Verein ist Dienstleister für Implementierung und Betrieb kommerzieller Anlagen.&lt;br /&gt;
&lt;br /&gt;
=== Empfehlenswert ===&lt;br /&gt;
&lt;br /&gt;
Der Verein sollte so beschrieben werden:&lt;br /&gt;
&lt;br /&gt;
: Der Verein fördert gemeinnützige Entwicklungszusammenarbeit durch offene Standards, Bildung, Wissenstransfer, Pilotprojekte und technische Selbstbefähigung im Bereich nachhaltiger Wasser-, Bewässerungs- und Agrarinfrastruktur.&lt;br /&gt;
&lt;br /&gt;
Die technische Arbeit ist dabei Mittel zum gemeinnützigen Zweck, nicht Selbstzweck.&lt;br /&gt;
&lt;br /&gt;
== Mögliche Vereinsstruktur ==&lt;br /&gt;
&lt;br /&gt;
Die AOWIS-Governance beschreibt bereits Prinzipien wie Offenheit, Neutralität, Sicherheit, Praktikabilität, Rechenschaft, langfristige Stabilität und Einbeziehung lokaler Akteure.&amp;lt;ref name=&amp;quot;AOWISGovernance&amp;quot;&amp;gt;https://aowis.org/index.php/Governance:Main_Page&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Diese Logik lässt sich gut in eine Vereinsstruktur übertragen.&lt;br /&gt;
&lt;br /&gt;
=== Mitgliederversammlung ===&lt;br /&gt;
&lt;br /&gt;
Aufgaben:&lt;br /&gt;
&lt;br /&gt;
* Wahl und Abberufung des Vorstands,&lt;br /&gt;
* Beschluss über Satzungsänderungen,&lt;br /&gt;
* Entlastung des Vorstands,&lt;br /&gt;
* Beschluss über Beitragsordnung,&lt;br /&gt;
* strategische Grundsatzentscheidungen,&lt;br /&gt;
* Auflösung des Vereins.&lt;br /&gt;
&lt;br /&gt;
=== Vorstand nach § 26 BGB ===&lt;br /&gt;
&lt;br /&gt;
Aufgaben:&lt;br /&gt;
&lt;br /&gt;
* rechtliche Vertretung des Vereins,&lt;br /&gt;
* Finanzen und Buchhaltung,&lt;br /&gt;
* Gemeinnützigkeits- und Spendenverwaltung,&lt;br /&gt;
* Verträge und Kooperationen,&lt;br /&gt;
* Fördermittelmanagement,&lt;br /&gt;
* Kommunikation mit Finanzamt, Registergericht und Notar,&lt;br /&gt;
* operative Gesamtkoordination.&lt;br /&gt;
&lt;br /&gt;
Empfehlung:&lt;br /&gt;
&lt;br /&gt;
Der Vorstand sollte mindestens aus drei Personen bestehen:&lt;br /&gt;
&lt;br /&gt;
* Vorsitz,&lt;br /&gt;
* stellvertretender Vorsitz,&lt;br /&gt;
* Schatzmeister / Finanzen.&lt;br /&gt;
&lt;br /&gt;
Optional:&lt;br /&gt;
&lt;br /&gt;
* Vorstand für Technik und Standards,&lt;br /&gt;
* Vorstand für Internationale Zusammenarbeit,&lt;br /&gt;
* Vorstand für Bildung und Programme.&lt;br /&gt;
&lt;br /&gt;
=== Technischer Beirat ===&lt;br /&gt;
&lt;br /&gt;
Aufgaben:&lt;br /&gt;
&lt;br /&gt;
* technische Qualitätssicherung,&lt;br /&gt;
* Standardpflege,&lt;br /&gt;
* Prüfung von Sicherheitsanforderungen,&lt;br /&gt;
* Modul- und Architekturentscheidungen,&lt;br /&gt;
* Bewertung von Referenzimplementierungen,&lt;br /&gt;
* Schutz vor herstellerabhängiger Vereinnahmung.&lt;br /&gt;
&lt;br /&gt;
Mögliche Fachbereiche:&lt;br /&gt;
&lt;br /&gt;
* Wasserverteilung,&lt;br /&gt;
* Bewässerung,&lt;br /&gt;
* Solar- und Energiesysteme,&lt;br /&gt;
* Sensorik und Telemetrie,&lt;br /&gt;
* Offline-Kommunikation,&lt;br /&gt;
* Sicherheits- und Notfalllogik,&lt;br /&gt;
* Datenmodelle und Dokumentation,&lt;br /&gt;
* Open-Source- und Lizenzfragen.&lt;br /&gt;
&lt;br /&gt;
=== Field Advisory Council / Praxisbeirat ===&lt;br /&gt;
&lt;br /&gt;
Aufgaben:&lt;br /&gt;
&lt;br /&gt;
* Einbindung von lokalen Betreibern,&lt;br /&gt;
* Einbindung von NGOs,&lt;br /&gt;
* Rückmeldung aus realen Einsatzregionen,&lt;br /&gt;
* Prüfung praktischer Nutzbarkeit,&lt;br /&gt;
* Vermeidung rein fernentwickelter Lösungen,&lt;br /&gt;
* kulturelle und lokale Anschlussfähigkeit.&lt;br /&gt;
&lt;br /&gt;
Dieser Bereich ist für Entwicklungszusammenarbeit besonders wichtig, weil Standards, die Gemeinschaften betreffen, nicht nur aus der Ferne entworfen werden sollten.&amp;lt;ref name=&amp;quot;AOWISGovernance&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Arbeitsgruppen ===&lt;br /&gt;
&lt;br /&gt;
Mögliche Arbeitsgruppen:&lt;br /&gt;
&lt;br /&gt;
* AG Vereinsgründung und Satzung,&lt;br /&gt;
* AG Gemeinnützigkeit und Compliance,&lt;br /&gt;
* AG Technischer Standard,&lt;br /&gt;
* AG Training und Dokumentation,&lt;br /&gt;
* AG Pilotprojekte,&lt;br /&gt;
* AG Partnerschaften und Fördermittel,&lt;br /&gt;
* AG Übersetzung und lokale Anpassung,&lt;br /&gt;
* AG Evaluation und Monitoring.&lt;br /&gt;
&lt;br /&gt;
=== Compliance- und Interessenkonflikt-Struktur ===&lt;br /&gt;
&lt;br /&gt;
Aufgaben:&lt;br /&gt;
&lt;br /&gt;
* Offenlegung finanzieller oder organisatorischer Interessen,&lt;br /&gt;
* Schutz der Neutralität des Standards,&lt;br /&gt;
* Prüfung von Beschaffungs- und Zertifizierungsfragen,&lt;br /&gt;
* klare Trennung zwischen gemeinnütziger Tätigkeit und wirtschaftlichen Interessen,&lt;br /&gt;
* Dokumentation von Entscheidungen,&lt;br /&gt;
* Vermeidung einseitiger Kontrolle durch einzelne Personen, Unternehmen oder Geldgeber.&lt;br /&gt;
&lt;br /&gt;
Die AOWIS-Governance betont, dass der Standard nicht durch ein einzelnes Unternehmen, politische Akteure, Geberorganisationen oder Einzelpersonen kontrolliert werden soll.&amp;lt;ref name=&amp;quot;AOWISGovernance&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Gründungsschritte ==&lt;br /&gt;
&lt;br /&gt;
=== Schritt 1: Gründungsteam bilden ===&lt;br /&gt;
&lt;br /&gt;
Erforderlich für die Eintragung:&lt;br /&gt;
&lt;br /&gt;
* mindestens sieben Gründungsmitglieder,&lt;br /&gt;
* Bereitschaft zur Unterzeichnung der Satzung,&lt;br /&gt;
* Bereitschaft zur Teilnahme an der Gründungsversammlung.&lt;br /&gt;
&lt;br /&gt;
Empfohlen:&lt;br /&gt;
&lt;br /&gt;
* mindestens eine Person mit Finanz-/Buchhaltungskompetenz,&lt;br /&gt;
* mindestens eine Person mit technischer Kompetenz,&lt;br /&gt;
* mindestens eine Person mit Erfahrung in Entwicklungszusammenarbeit, NGO-Arbeit oder Projektkoordination,&lt;br /&gt;
* mindestens eine Person mit Kommunikations- oder Dokumentationskompetenz.&lt;br /&gt;
&lt;br /&gt;
=== Schritt 2: Vereinsname und Sitz festlegen ===&lt;br /&gt;
&lt;br /&gt;
Zu klären:&lt;br /&gt;
&lt;br /&gt;
* Name des Vereins,&lt;br /&gt;
* Kurzname,&lt;br /&gt;
* Sitz des Vereins,&lt;br /&gt;
* Eintragungsabsicht als e. V.,&lt;br /&gt;
* Gemeinnützigkeitsabsicht,&lt;br /&gt;
* Domain- und Markenfragen&lt;br /&gt;
&lt;br /&gt;
=== Schritt 3: Satzung entwerfen ===&lt;br /&gt;
&lt;br /&gt;
Die Satzung sollte mindestens regeln:&lt;br /&gt;
&lt;br /&gt;
* Name,&lt;br /&gt;
* Sitz,&lt;br /&gt;
* Eintragung ins Vereinsregister,&lt;br /&gt;
* Vereinszweck,&lt;br /&gt;
* Art der Zweckverwirklichung,&lt;br /&gt;
* Gemeinnützigkeit,&lt;br /&gt;
* Selbstlosigkeit,&lt;br /&gt;
* Mittelverwendung,&lt;br /&gt;
* Vermögensbindung,&lt;br /&gt;
* Mitgliedschaft,&lt;br /&gt;
* Rechte und Pflichten der Mitglieder,&lt;br /&gt;
* Beiträge,&lt;br /&gt;
* Beendigung der Mitgliedschaft,&lt;br /&gt;
* Organe des Vereins,&lt;br /&gt;
* Mitgliederversammlung,&lt;br /&gt;
* Vorstand,&lt;br /&gt;
* Vertretungsregelung,&lt;br /&gt;
* Beschlussfassung,&lt;br /&gt;
* Satzungsänderungen,&lt;br /&gt;
* Auflösung des Vereins,&lt;br /&gt;
* Protokollierung,&lt;br /&gt;
* Datenschutz und digitale Versammlungen, falls gewünscht.&lt;br /&gt;
&lt;br /&gt;
Das Bundesministerium der Justiz stellt Muster zum Vereinsrecht bereit, darunter eine Mustersatzung, ein Gründungsprotokoll und Muster für die Anmeldung zum Vereinsregister.&amp;lt;ref name=&amp;quot;BMJVereinsrecht&amp;quot;&amp;gt;https://www.bmjv.de/DE/service/formulare/muster_vereinsrecht/muster_vereinsrecht_node.html&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Schritt 4: Vorabprüfung durch das Finanzamt ===&lt;br /&gt;
&lt;br /&gt;
Vor der Gründungsversammlung sollte der Satzungsentwurf dem zuständigen Finanzamt zur Vorabprüfung vorgelegt werden.&lt;br /&gt;
&lt;br /&gt;
Ziel:&lt;br /&gt;
&lt;br /&gt;
* Prüfung der gemeinnützigkeitsrechtlichen Formulierungen,&lt;br /&gt;
* Vermeidung späterer Satzungsänderungen,&lt;br /&gt;
* bessere Sicherheit bei Spenden- und Förderfähigkeit,&lt;br /&gt;
* Klärung der passenden gemeinnützigen Zwecke.&lt;br /&gt;
&lt;br /&gt;
=== Schritt 5: Gründungsversammlung durchführen ===&lt;br /&gt;
&lt;br /&gt;
Tagesordnung:&lt;br /&gt;
&lt;br /&gt;
# Eröffnung und Feststellung der Anwesenheit,&lt;br /&gt;
# Wahl der Versammlungsleitung,&lt;br /&gt;
# Wahl der Protokollführung,&lt;br /&gt;
# Vorstellung des Vereinszwecks,&lt;br /&gt;
# Beratung und Beschluss der Satzung,&lt;br /&gt;
# Wahl des Vorstands,&lt;br /&gt;
# Beschluss über Vereinsregistereintragung,&lt;br /&gt;
# Beschluss über Beantragung der Gemeinnützigkeit,&lt;br /&gt;
# Beschluss über Beitragsordnung, falls vorgesehen,&lt;br /&gt;
# weitere organisatorische Beschlüsse.&lt;br /&gt;
&lt;br /&gt;
Erforderlich:&lt;br /&gt;
&lt;br /&gt;
* Anwesenheitsliste,&lt;br /&gt;
* beschlossene Satzung,&lt;br /&gt;
* Unterschriften der Gründungsmitglieder,&lt;br /&gt;
* Gründungsprotokoll,&lt;br /&gt;
* Vorstandswahl mit Annahme der Wahl.&lt;br /&gt;
&lt;br /&gt;
=== Schritt 6: Notar und Vereinsregister ===&lt;br /&gt;
&lt;br /&gt;
Der gewählte Vorstand meldet den Verein über einen Notar beim Vereinsregister an.&lt;br /&gt;
&lt;br /&gt;
Typische Unterlagen:&lt;br /&gt;
&lt;br /&gt;
* Satzung,&lt;br /&gt;
* Gründungsprotokoll,&lt;br /&gt;
* Nachweis der Vorstandswahl,&lt;br /&gt;
* Anmeldung zum Vereinsregister,&lt;br /&gt;
* Angaben zu vertretungsberechtigten Vorstandsmitgliedern.&lt;br /&gt;
&lt;br /&gt;
=== Schritt 7: Gemeinnützigkeit beantragen ===&lt;br /&gt;
&lt;br /&gt;
Nach der Gründung beziehungsweise nach Eintragung wird beim Finanzamt die Gemeinnützigkeit beantragt.&lt;br /&gt;
&lt;br /&gt;
Ziel ist die Feststellung der satzungsmäßigen Voraussetzungen der Gemeinnützigkeit nach § 60a AO.&amp;lt;ref name=&amp;quot;AOInhalt&amp;quot;&amp;gt;https://www.gesetze-im-internet.de/ao_1977/inhalts_bersicht.html&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Nach Anerkennung kann der Verein grundsätzlich:&lt;br /&gt;
&lt;br /&gt;
* Spendenbescheinigungen ausstellen,&lt;br /&gt;
* steuerbegünstigte Mittel empfangen,&lt;br /&gt;
* Fördermittel beantragen,&lt;br /&gt;
* gegenüber Partnern als gemeinnützige Organisation auftreten.&lt;br /&gt;
&lt;br /&gt;
=== Schritt 8: Betrieb aufsetzen ===&lt;br /&gt;
&lt;br /&gt;
Notwendig:&lt;br /&gt;
&lt;br /&gt;
* Vereinskonto,&lt;br /&gt;
* Buchhaltung,&lt;br /&gt;
* Belegsystem,&lt;br /&gt;
* Spendenverwaltung,&lt;br /&gt;
* Datenschutzgrundlagen,&lt;br /&gt;
* Mitgliederverwaltung,&lt;br /&gt;
* Projektakten,&lt;br /&gt;
* Mittelverwendungsnachweise,&lt;br /&gt;
* Dokumentationsstruktur,&lt;br /&gt;
* interne Freigabeprozesse,&lt;br /&gt;
* Interessenkonflikt-Policy,&lt;br /&gt;
* Fördermittel- und Partnerprüfung.&lt;br /&gt;
&lt;br /&gt;
== Einnahmen und wirtschaftliche Tätigkeiten ==&lt;br /&gt;
&lt;br /&gt;
Ein gemeinnütziger Verein darf Einnahmen haben. Entscheidend ist, wie diese steuerlich einzuordnen sind.&lt;br /&gt;
&lt;br /&gt;
Mögliche Einnahmen:&lt;br /&gt;
&lt;br /&gt;
* Mitgliedsbeiträge,&lt;br /&gt;
* Spenden,&lt;br /&gt;
* Fördermittel,&lt;br /&gt;
* Zuschüsse,&lt;br /&gt;
* projektbezogene Mittel,&lt;br /&gt;
* Teilnahmebeiträge für Schulungen,&lt;br /&gt;
* Verkauf von Materialien zum Selbstkostenpreis,&lt;br /&gt;
* Aufwandsersatz,&lt;br /&gt;
* zweckbezogene Beratungsleistungen.&lt;br /&gt;
&lt;br /&gt;
Zu prüfen ist jeweils, ob es sich handelt um:&lt;br /&gt;
&lt;br /&gt;
* ideellen Bereich,&lt;br /&gt;
* Zweckbetrieb,&lt;br /&gt;
* Vermögensverwaltung,&lt;br /&gt;
* wirtschaftlichen Geschäftsbetrieb.&lt;br /&gt;
&lt;br /&gt;
Besonders sensibel sind:&lt;br /&gt;
&lt;br /&gt;
* Zertifizierungen gegen Entgelt,&lt;br /&gt;
* technische Beratung gegen Entgelt,&lt;br /&gt;
* Implementierungsbegleitung gegen Entgelt,&lt;br /&gt;
* Verkauf von Hardware,&lt;br /&gt;
* exklusive Kooperationen mit Unternehmen,&lt;br /&gt;
* Einflussnahme auf Beschaffung oder Lieferantenauswahl.&lt;br /&gt;
&lt;br /&gt;
Empfehlung:&lt;br /&gt;
&lt;br /&gt;
Wirtschaftliche Tätigkeiten sollten nicht in der Gründungsphase dominant sein. Zunächst sollte der Verein klar gemeinnützig und standard-/bildungsorientiert aufgestellt werden.&lt;br /&gt;
&lt;br /&gt;
== Risiken und Gegenmaßnahmen ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Risiko&lt;br /&gt;
! Beschreibung&lt;br /&gt;
! Gegenmaßnahme&lt;br /&gt;
|-&lt;br /&gt;
| Verdeckte wirtschaftliche Tätigkeit&lt;br /&gt;
| Der Verein wirkt wie eine Firma im Vereinsmantel.&lt;br /&gt;
| Klare Satzung, transparente Mittelverwendung, keine Produktverkaufslogik.&lt;br /&gt;
|-&lt;br /&gt;
| Herstellerabhängigkeit&lt;br /&gt;
| Ein Unternehmen kontrolliert Standard, Zertifizierung oder Beschaffung.&lt;br /&gt;
| Offenlegung von Interessen, technischer Beirat, transparente Governance.&lt;br /&gt;
|-&lt;br /&gt;
| Zu breiter Satzungszweck&lt;br /&gt;
| Zu viele Zwecke wirken beliebig und schwer prüfbar.&lt;br /&gt;
| Entwicklungszusammenarbeit als Hauptzweck; Ergänzungen nur bei realer Umsetzung.&lt;br /&gt;
|-&lt;br /&gt;
| Fehlende lokale Legitimität&lt;br /&gt;
| Lösungen werden nur aus Europa heraus entworfen.&lt;br /&gt;
| Praxisbeirat mit lokalen Betreibern, NGOs und Technikern.&lt;br /&gt;
|-&lt;br /&gt;
| Unklare Mittelweitergabe&lt;br /&gt;
| Gelder fließen an ausländische Partner ohne ausreichende Dokumentation.&lt;br /&gt;
| Verträge, Projektberichte, Belege, Partnerprüfung, Mittelverwendungsnachweise.&lt;br /&gt;
|-&lt;br /&gt;
| Unklare IP- und Lizenzfragen&lt;br /&gt;
| Open Standard, Software, Dokumentation und Markenrechte sind nicht geregelt.&lt;br /&gt;
| Lizenzkonzept, Contributor-Regeln, Marken- und Namensstrategie.&lt;br /&gt;
|-&lt;br /&gt;
| Schwache Dokumentation&lt;br /&gt;
| Gemeinnützigkeit scheitert später an fehlenden Nachweisen.&lt;br /&gt;
| Projektakten, Beschlüsse, Finanzdokumentation, Wirkungsberichte.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Sofort umsetzbare Aufgabenliste ==&lt;br /&gt;
&lt;br /&gt;
=== Für den CEO ===&lt;br /&gt;
&lt;br /&gt;
* finalen Vereinsnamen vorschlagen: &#039;&#039;&#039;AOWIS.org&#039;&#039;&#039; bzw. &#039;&#039;&#039;AOWIS&#039;&#039;&#039;&lt;br /&gt;
* Sitz des Vereins klären,&lt;br /&gt;
* Gründungsteam mit mindestens sieben Personen identifizieren,&lt;br /&gt;
* Rollen für Vorstand und Beirat vorschlagen,&lt;br /&gt;
* Satzungszweck finalisieren,&lt;br /&gt;
* Finanzamt für Vorabprüfung bestimmen,&lt;br /&gt;
* Notar oder Registergericht-Zuständigkeit klären,&lt;br /&gt;
&lt;br /&gt;
=== Für das Team ===&lt;br /&gt;
&lt;br /&gt;
* Satzungsentwurf erstellen,&lt;br /&gt;
* Beitragsordnung entwerfen,&lt;br /&gt;
* Gründungsprotokoll vorbereiten,&lt;br /&gt;
* Mitgliederliste vorbereiten,&lt;br /&gt;
* Governance-Struktur entwerfen,&lt;br /&gt;
* Interessenkonflikt-Erklärung entwerfen,&lt;br /&gt;
* Projektbeschreibung auf 1–2 Seiten formulieren,&lt;br /&gt;
* Finanzplan für das erste Jahr erstellen,&lt;br /&gt;
* Liste möglicher Partner und Fördermittelgeber erstellen.&lt;br /&gt;
&lt;br /&gt;
== Mögliche Kurzbeschreibung des Vereins ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
Der Verein fördert Entwicklungszusammenarbeit durch offene technische Standards, Bildung und Wissenstransfer im Bereich nachhaltiger Wasser-, Bewässerungs- und Agrarinfrastruktur. Ziel ist es, lokale Initiativen, gemeinnützige Organisationen, Betreiber und technische Fachkräfte in ressourcenarmen Regionen dabei zu unterstützen, robuste, sichere, wartbare und unabhängig betreibbare Infrastrukturen aufzubauen und langfristig zu erhalten.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Mögliche Langbeschreibung des Vereins ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
Der Verein versteht sich als gemeinnütziger Träger für die Entwicklung, Pflege und Verbreitung offener Standards für Wasser-, Bewässerungs- und Agrarinfrastruktur in ressourcenarmen und entwicklungsrelevanten Regionen. Im Mittelpunkt stehen robuste, sichere, lokal wartbare und herstellerunabhängige Systeme, die auch bei instabiler Stromversorgung, eingeschränkter Konnektivität und begrenzter technischer Unterstützung betrieben werden können.&lt;br /&gt;
&lt;br /&gt;
Der Verein fördert Entwicklungszusammenarbeit durch technische Dokumentation, Schulung, Wissenstransfer, Pilotprojekte, Forschung, Evaluation und Kooperation mit lokalen Initiativen, NGOs, Hochschulen und öffentlichen Stellen. Ziel ist nicht der Verkauf technischer Produkte, sondern die gemeinnützige Befähigung lokaler Akteure zur Planung, zum Betrieb, zur Wartung und zur Weiterentwicklung nachhaltiger Infrastruktur.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Empfehlung für die nächste Arbeitsphase ==&lt;br /&gt;
&lt;br /&gt;
Die nächsten drei Dokumente sollten vorbereitet werden:&lt;br /&gt;
&lt;br /&gt;
# &#039;&#039;&#039;Satzungsentwurf&#039;&#039;&#039; mit gemeinnützigkeitsrechtlich geprüften Formulierungen.&lt;br /&gt;
# &#039;&#039;&#039;Gründungsprotokoll&#039;&#039;&#039; für die erste Mitgliederversammlung.&lt;br /&gt;
# &#039;&#039;&#039;1-seitige Projektbeschreibung&#039;&#039;&#039; für Finanzamt, Gründungsmitglieder und mögliche Partner.&lt;br /&gt;
&lt;br /&gt;
Erst danach sollte die Gründungsversammlung angesetzt werden.&lt;br /&gt;
&lt;br /&gt;
== Quellen ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Kategorie:AOWIS]]&lt;br /&gt;
[[Kategorie:Vereinsgründung]]&lt;br /&gt;
[[Kategorie:Gemeinnützigkeit]]&lt;br /&gt;
[[Kategorie:Entwicklungszusammenarbeit]]&lt;br /&gt;
[[Kategorie:Governance]]&lt;/div&gt;</summary>
		<author><name>Samuel</name></author>
	</entry>
	<entry>
		<id>https://aowis.org/index.php?title=Main_Page&amp;diff=785</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://aowis.org/index.php?title=Main_Page&amp;diff=785"/>
		<updated>2026-09-29T19:28:53Z</updated>

		<summary type="html">&lt;p&gt;Samuel: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{MainPageBanner}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Motivation&lt;br /&gt;
 | color = teal&lt;br /&gt;
 | body = &lt;br /&gt;
&lt;br /&gt;
[[File:Countryside.jpg|class=fullwidth|center]]&lt;br /&gt;
&lt;br /&gt;
In many rural and underserved regions, including parts of Africa, wells and pumps may exist while developing and operating a reliable distribution network remains difficult. Local initiatives can lack engineering capacity, trained personnel, suitable technology, and affordable tools for operating such infrastructure sustainably.&lt;br /&gt;
&lt;br /&gt;
This practical problem is an important motivation for AOWIS. AOWIS aims to make the engineering knowledge, technical foundations, software, and operational methods needed to develop and operate water infrastructure openly available and practically usable, while supporting local training and cooperation with experienced organizations and operators.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Why AOWIS is Needed&lt;br /&gt;
 | color = turquoise&lt;br /&gt;
 | body = &lt;br /&gt;
&lt;br /&gt;
[[File:Cooperation.jpg|400px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
Water and irrigation infrastructure must often be planned, built, expanded, and operated over many decades. In some places, existing infrastructure has become fragmented across different vendors, technologies, tools, and engineering approaches. In others, communities and organizations are building coherent water infrastructure for the first time and may have limited access to engineering capacity, technical guidance, suitable software, or established operational practices.&lt;br /&gt;
&lt;br /&gt;
AOWIS provides a shared open foundation for both situations. It brings together technical standards, engineering knowledge, software, reference implementations, operational guidance, and training to support the development of water infrastructure from initial planning and design through construction, operation, maintenance, and future expansion.&lt;br /&gt;
&lt;br /&gt;
The aim is to make infrastructure understandable, interoperable, maintainable, and extensible throughout its lifecycle, while reducing dependence on individual vendors, products, suppliers, or scarce specialist expertise.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Operating Conditions&lt;br /&gt;
 | color = lightblue&lt;br /&gt;
 | body =&lt;br /&gt;
&lt;br /&gt;
[[File:Village.jpg|250px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS is designed for environments where water infrastructure must remain useful and safe despite difficult technical and operational conditions. This is particularly important in rural and underserved regions, where reliable power, continuous connectivity, modern equipment, trained personnel, and specialist support cannot always be assumed.&lt;br /&gt;
&lt;br /&gt;
Typical conditions include:&lt;br /&gt;
&lt;br /&gt;
* unreliable or limited power supply&lt;br /&gt;
* intermittent or unavailable connectivity&lt;br /&gt;
* heterogeneous or aging equipment&lt;br /&gt;
* limited availability of trained technical personnel&lt;br /&gt;
* limited access to specialist engineering support&lt;br /&gt;
* the need for safe local operation without continuous remote supervision&lt;br /&gt;
&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Design Principles&lt;br /&gt;
 | color = lightblue&lt;br /&gt;
 | body =&lt;br /&gt;
&lt;br /&gt;
AOWIS addresses these conditions through principles including:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;offline-first operation&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;safe fallback behaviour&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;human-in-the-loop control&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;local autonomous operation&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;modular and extensible system design&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;shared infrastructure models&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;open interfaces and accessible technical documentation&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The goal is to make essential water infrastructure &#039;&#039;&#039;robust, understandable, maintainable, and locally operable&#039;&#039;&#039;, including where conventional assumptions about connectivity, technical resources, and institutional support do not hold.&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
| title = Software &amp;amp; Downloads&lt;br /&gt;
| color = green&lt;br /&gt;
| body =&lt;br /&gt;
[[File:GUI ky4 3d.png|400px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS includes an open-source software platform for &#039;&#039;&#039;modelling, simulating, visualizing, monitoring, and operating water infrastructure&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The current software includes a network editor and monitoring interface, hydraulic and water-quality simulation using [[External:EPANET:Main Page|EPANET]], geographic maps and terrain visualization, and support for local and standalone operation. Development of the AOWIS Controller is progressing toward a complete open-source SCADA and operational management platform..&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://download.aowis.org Download the AOWIS Controller (development snapshot)]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* [https://github.com/aowis-org Source code on GitHub]&lt;br /&gt;
* [[#Roadmap|Software development roadmap]]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Start Here&lt;br /&gt;
 | color = yellow&lt;br /&gt;
 | body =&lt;br /&gt;
If you are new to AOWIS, begin with:&lt;br /&gt;
&lt;br /&gt;
* [[Concepts:Design_Philosophy|Design Philosophy]]  &lt;br /&gt;
* [[Standard:Definitions|Definitions]]  &lt;br /&gt;
* [[Standard:Normative_Requirements|Normative Requirements]]  &lt;br /&gt;
* [[Modules:Module_Template|Module Template]]  &lt;br /&gt;
* [[AOWIS:Contributor_Guide_External|Contributor Guide - External]]&lt;br /&gt;
* [[AOWIS:Contributor_Guide_Internal|Contributor Guide - Internal]]&lt;br /&gt;
* [[AOWIS:Writing_Style_Guide|Writing Style Guide]]&lt;br /&gt;
* [[AOWIS:AI_Usage_Guide|AI Usage Guide]]&lt;br /&gt;
* [[AOWIS:Research_Form_Guide|Research Form Guide]]&lt;br /&gt;
* [[AOWIS:Naming_Convention_Specification|Naming Convention Specification]]&lt;br /&gt;
* [[AOWIS:Change_Log__Versioning|Change Log &amp;amp; Versioning]]&lt;br /&gt;
* [[AOWIS:Wiki|This Wiki]]&lt;br /&gt;
&lt;br /&gt;
These pages explain the foundations of AOWIS, how the AOWIS Standard is structured, and how to use and contribute to the project and its documentation.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = List of Requirement Pages&lt;br /&gt;
 | color = brown&lt;br /&gt;
 | body = &lt;br /&gt;
This index lists AOWIS pages that define normative requirements (MUST/SHOULD/MAY statements) and conformance rules.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Dev Rules&#039;&#039;&#039; — specs for writing and maintaining AOWIS&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;REQ-AI:&#039;&#039;&#039; [[AOWIS:AI_Usage_Guide|AI Usage Guide]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Technical Standard&#039;&#039;&#039; — system behavior and data models&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;REQ-MEAS, REQ-MEAS-UI:&#039;&#039;&#039; [[Measurement:Units|Unit System Requirements]]&lt;br /&gt;
* &#039;&#039;&#039;REQ-MEAS-UNI:&#039;&#039;&#039; [[Measurement:Canonical_Units|Canonical Units]]&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = AOWIS Documentation Structure&lt;br /&gt;
 | color = purple&lt;br /&gt;
 | body = &lt;br /&gt;
* [[Motivation:Main_Page|Motivation]] – Real-world problems, constraints, operating conditions, and practical needs that AOWIS is intended to address.&lt;br /&gt;
* [[Standard:Main_Page|Standard]] – The normative core of AOWIS. Defines requirements and definitions specifying what AOWIS-compliant systems MUST, SHOULD, or MAY do.&lt;br /&gt;
* [[Concepts:Main_Page|Concepts]] – Core concepts, design principles, terminology, and system-level ideas used throughout AOWIS.&lt;br /&gt;
* [[Architecture:Main_Page|Architecture]] – Overall system structure, including controllers, components, layers, interfaces, communication, data flows, responsibilities, and interactions between parts of an AOWIS system.&lt;br /&gt;
* [[Infrastructure:Main_Page|Infrastructure]] – Physical infrastructure, technologies, systems, and components that AOWIS is used to plan, design, model, build, monitor, control, operate, maintain, and extend.&lt;br /&gt;
* [[Measurement:Main_Page|Measurement]] – Physical quantities, units, measurement semantics, sensor and manual measurements, calibration, uncertainty, derived values, and the representation of measured information within AOWIS.&lt;br /&gt;
* [[Data:Main_Page|Data]] – Data models, schemas, identifiers, interchange formats, logging, synchronization, persistence, and data lifecycle rules.&lt;br /&gt;
* [[Operations:Main_Page|Operations]] – Monitoring, control, operational procedures, state management, fallback behaviour, decision-making, maintenance activities, and other processes involved in operating infrastructure.&lt;br /&gt;
* [[Modules:Main_Page|Modules]] – Reusable functional components that provide specific capabilities within AOWIS while integrating with the common system architecture and data model.&lt;br /&gt;
* [[Reference:Main_Page|Reference]] – Concrete implementations, engineering designs, example deployments, reference configurations, and validated patterns showing practical ways AOWIS systems can be built and used.&lt;br /&gt;
* [[Databases:Main_Page|Databases]] – Structured knowledge bases, registries, catalogues, and other organized information used by AOWIS and its implementations.&lt;br /&gt;
* [[Governance:Main_Page|Governance]] – Conformance, certification, review, auditing, versioning, licensing, trust, and organizational processes governing AOWIS and its development.&lt;br /&gt;
* [[Training:Main_Page|Training]] – Educational and practical material for operators, technicians, engineers, developers, contributors, communities, and others working with AOWIS and the infrastructure it supports.&lt;br /&gt;
* [[Regions:Main_Page|Regions]] – Place-specific information about geographic areas, including environmental, hydrological, climatic, socioeconomic, geological, infrastructure, water-resource, and field-project context.&lt;br /&gt;
* [[Geology:Main_Page|Geology]] – Geological, geomorphological, hydrogeological, hydrogeochemical, and geophysical knowledge relevant to water resources, groundwater occurrence and movement, subsurface investigation, borehole siting, and the understanding of local and regional geological conditions.&lt;br /&gt;
&lt;br /&gt;
* [[External:Main_Page|External]] – External standards, projects, technologies, tools, organizations, and systems relevant to AOWIS, its interoperability, or the domains in which it is used.&lt;br /&gt;
&lt;br /&gt;
For a full overview, see the [[AOWIS:Table_of_Contents|Table of Contents]].&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Roadmap&lt;br /&gt;
 | color = grey&lt;br /&gt;
 | body =&lt;br /&gt;
[[File:Boring.jpg|250px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS has progressed beyond its initial conceptual phase. A substantial software foundation for modelling, simulating, visualizing, and eventually operating water infrastructure is under active development.&lt;br /&gt;
&lt;br /&gt;
The current software stack already includes:&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Shared infrastructure model&#039;&#039;&#039;&lt;br /&gt;
: A common, solver-independent representation of water infrastructure used throughout the AOWIS software stack.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-MODEL GitHub AOWIS-SERVER-MODEL]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Hydraulic and water-quality simulation&#039;&#039;&#039;&lt;br /&gt;
: EPANET integration for hydraulic and water-quality simulation, network import/export, controls, rules, diagnostics, and simulation results. Integration of &#039;&#039;&#039;EPANET-MSX&#039;&#039;&#039; is also being developed.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-EPANET GitHub AOWIS-SERVER-EPANET]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Network editor and monitoring interface&#039;&#039;&#039;&lt;br /&gt;
: A graphical application for creating, inspecting, simulating, and visualizing water networks, including geographic maps and terrain-aware 3D visualization.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-GUI GitHub AOWIS-SERVER-GUI]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Geographic and terrain infrastructure&#039;&#039;&#039;&lt;br /&gt;
: Mapping, elevation data, basemaps, terrain visualization, geographic placement, and local caching.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-MAP GitHub AOWIS-SERVER-MAP]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Local and standalone operation&#039;&#039;&#039;&lt;br /&gt;
: Support for deployments that do not depend on continuous Internet or cloud connectivity.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-Standalone GitHub AOWIS-SERVER-Standalone]&lt;br /&gt;
&lt;br /&gt;
The software remains under active development and should not yet be considered a complete production SCADA system.&lt;br /&gt;
&lt;br /&gt;
The next major stage is to connect the existing modelling and simulation environment to &#039;&#039;&#039;real infrastructure in continuous operation&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The AOWIS software platform is intended to develop into a complete open-source SCADA, infrastructure modelling, simulation, and operational management platform in which planning, live monitoring, control, historical data, maintenance, and simulation operate on the same shared infrastructure model.&lt;br /&gt;
&lt;br /&gt;
This includes telemetry, sensors and actuators, alarms and historian functions, local and remote control, automation with safe fallback behaviour, and model-assisted operation using measured and simulated system behaviour.&lt;br /&gt;
&lt;br /&gt;
EPANET currently provides the primary hydraulic and water-quality simulation engine, but AOWIS is not designed solely as an EPANET frontend. EPANET is one solver integrated into a broader, solver-independent architecture.&lt;br /&gt;
&lt;br /&gt;
The long-term objective is to connect the complete infrastructure lifecycle:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;survey and planning → engineering and simulation → construction → commissioning → monitoring → control → maintenance → analysis → expansion&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[[AOWIS:Roadmap|Read the full roadmap →]]&#039;&#039;&#039;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
| title = Community &amp;amp; Participation&lt;br /&gt;
| color = blue&lt;br /&gt;
| body =&lt;br /&gt;
&lt;br /&gt;
AOWIS is an open project, and participation is welcome from anyone interested in its goals — including engineers, developers, NGOs, operators, researchers, technicians, students, and people with practical experience in water and irrigation infrastructure.&lt;br /&gt;
&lt;br /&gt;
For &#039;&#039;&#039;discussion, planning, questions, documentation, infrastructure, field projects, standards, research, and other forms of participation&#039;&#039;&#039;, AOWIS uses &#039;&#039;&#039;Matrix&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The AOWIS Matrix server has several &#039;&#039;&#039;public spaces and rooms&#039;&#039;&#039; for different topics. Join those relevant to your interests. For general questions or help finding the right place, start here:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://matrix.to/#/#support:aowis.org AOWIS Support — #support:aowis.org]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Any Matrix account can join public AOWIS spaces and rooms.&lt;br /&gt;
&lt;br /&gt;
If you are new to Matrix:&lt;br /&gt;
&lt;br /&gt;
* [https://matrix.org/try-matrix/ Learn about Matrix and create an account]&lt;br /&gt;
* [https://element.io/ Element] — Matrix client for web, desktop, and mobile&lt;br /&gt;
* [https://fluffychat.im/ FluffyChat] — simple Matrix client for several platforms&lt;br /&gt;
&lt;br /&gt;
The same Matrix account can be used with different clients.&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;AOWIS Matrix Accounts&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Participants may also request an account on the AOWIS Matrix homeserver, giving them an ID such as &#039;&#039;&#039;@name:aowis.org&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
To reduce automated registrations and abuse, accounts are created on request. Please send a short introduction telling us who you are, what interests you about AOWIS, and where you would like to participate: [[File:Mtx.png|120px|frameless|alt=Email address for requesting an AOWIS Matrix account]]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Software Development&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Software development happens on &#039;&#039;&#039;GitHub&#039;&#039;&#039;. Bug reports, pull requests, source-code contributions, and repository-specific development discussions should use the appropriate repository.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://github.com/aowis-org AOWIS on GitHub]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Matrix is for the broader AOWIS community and participation that does not naturally belong in a GitHub repository.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Governance &amp;amp; Legitimacy&lt;br /&gt;
 | color = turquoise&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS includes a transparent governance model to ensure:&lt;br /&gt;
&lt;br /&gt;
* open participation  &lt;br /&gt;
* clear certification processes  &lt;br /&gt;
* stable versioning  &lt;br /&gt;
* long-term stewardship and continuity&lt;br /&gt;
&lt;br /&gt;
See: [[Governance:Main_Page|Governance]].&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Navigation&lt;br /&gt;
 | color = grey&lt;br /&gt;
 | body =&lt;br /&gt;
* [[AOWIS:Table_of_Contents|Table of Contents]]  &lt;br /&gt;
* [[Reference:Glossary|Glossary]]  &lt;br /&gt;
* [[Reference:FAQ|FAQ]]  &lt;br /&gt;
* [[Reference:Change_Log|Change Log]]  &lt;br /&gt;
&lt;br /&gt;
* [https://github.com/aowis-org GitHub]&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Partners&lt;br /&gt;
 | color = indigo&lt;br /&gt;
 | body = &lt;br /&gt;
[[File:Afriticgroup.webp|250px|frameless|center|link=https://afriticgroup.com/]]&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Samuel</name></author>
	</entry>
	<entry>
		<id>https://aowis.org/index.php?title=Template:MainPageBanner&amp;diff=784</id>
		<title>Template:MainPageBanner</title>
		<link rel="alternate" type="text/html" href="https://aowis.org/index.php?title=Template:MainPageBanner&amp;diff=784"/>
		<updated>2026-09-29T18:57:27Z</updated>

		<summary type="html">&lt;p&gt;Samuel: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;div class=&amp;quot;mainpage-banner&amp;quot; style=&amp;quot;&lt;br /&gt;
background: var(--background-color-neutral-subtle, #f8f9fa);&lt;br /&gt;
border: 1px solid var(--border-color-base, #a2a9b1);&lt;br /&gt;
padding: 1.5em;&lt;br /&gt;
margin-bottom: 1.5em;&lt;br /&gt;
border-radius: 4px;&lt;br /&gt;
color: var(--color-base, #202122);&lt;br /&gt;
&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1 style=&amp;quot;&lt;br /&gt;
margin: 0 0 0.8em 0;&lt;br /&gt;
font-size: 2em;&lt;br /&gt;
font-weight: normal;&lt;br /&gt;
color: var(--color-base, #202122);&lt;br /&gt;
&amp;quot;&amp;gt;&lt;br /&gt;
&#039;&#039;&#039;AOWIS – Afritic Open Water Infrastructure System&#039;&#039;&#039;&lt;br /&gt;
&amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[File:Logo.png|frameless|right|150px]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div&amp;gt;&lt;br /&gt;
&amp;lt;p style=&amp;quot;margin: 0 0 0.6em 0; font-size: 1.15em;&amp;quot;&amp;gt;&lt;br /&gt;
&#039;&#039;&#039;AOWIS&#039;&#039;&#039; (&#039;&#039;&#039;A&#039;&#039;&#039;fritic &#039;&#039;&#039;O&#039;&#039;&#039;pen &#039;&#039;&#039;W&#039;&#039;&#039;ater &#039;&#039;&#039;I&#039;&#039;&#039;nfrastructure &#039;&#039;&#039;S&#039;&#039;&#039;ystem) is an open system for planning, designing, modelling, building, operating, maintaining, and extending safe and reliable &#039;&#039;&#039;water and irrigation infrastructure&#039;&#039;&#039; throughout its lifecycle.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p style=&amp;quot;margin: 0 0 0.6em 0; font-size: 1.15em;&amp;quot;&amp;gt;&lt;br /&gt;
AOWIS brings together open technical standards, open-source software, shared infrastructure models, engineering methods, reference implementations, operational guidance, and training. It provides a common foundation for modelling, simulation, monitoring, control, automation, data exchange, and day-to-day operation.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p style=&amp;quot;margin: 0; font-size: 1.15em;&amp;quot;&amp;gt;&lt;br /&gt;
It is intended for communities, utilities, organizations, engineers, and others involved in water infrastructure, while remaining practical under difficult conditions such as intermittent connectivity, unreliable power, limited technical resources, and the need for local autonomous operation.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;&lt;br /&gt;
margin-top: 0.8em;&lt;br /&gt;
font-size: 0.9em;&lt;br /&gt;
line-height: 1.5;&lt;br /&gt;
display: flex;&lt;br /&gt;
flex-wrap: wrap;&lt;br /&gt;
column-gap: 0.7em;&lt;br /&gt;
row-gap: 0.35em;&lt;br /&gt;
&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;span style=&amp;quot;white-space: nowrap;&amp;quot;&amp;gt;&#039;&#039;&#039;[[#Software &amp;amp; Downloads|Software &amp;amp; Downloads]]&#039;&#039;&#039; &amp;lt;span aria-hidden=&amp;quot;true&amp;quot;&amp;gt;·&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;span style=&amp;quot;white-space: nowrap;&amp;quot;&amp;gt;&#039;&#039;&#039;[[#Community &amp;amp; Participation|Community &amp;amp; Participation]]&#039;&#039;&#039; &amp;lt;span aria-hidden=&amp;quot;true&amp;quot;&amp;gt;·&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;span style=&amp;quot;white-space: nowrap;&amp;quot;&amp;gt;&#039;&#039;&#039;[[Standard:Main_Page|Access the Standard]]&#039;&#039;&#039;&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;/div&gt;</summary>
		<author><name>Samuel</name></author>
	</entry>
	<entry>
		<id>https://aowis.org/index.php?title=Template:MainPageBanner&amp;diff=783</id>
		<title>Template:MainPageBanner</title>
		<link rel="alternate" type="text/html" href="https://aowis.org/index.php?title=Template:MainPageBanner&amp;diff=783"/>
		<updated>2026-09-29T18:55:13Z</updated>

		<summary type="html">&lt;p&gt;Samuel: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;div class=&amp;quot;mainpage-banner&amp;quot; style=&amp;quot;&lt;br /&gt;
background: var(--background-color-neutral-subtle, #f8f9fa);&lt;br /&gt;
border: 1px solid var(--border-color-base, #a2a9b1);&lt;br /&gt;
padding: 1.5em;&lt;br /&gt;
margin-bottom: 1.5em;&lt;br /&gt;
border-radius: 4px;&lt;br /&gt;
color: var(--color-base, #202122);&lt;br /&gt;
&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1 style=&amp;quot;&lt;br /&gt;
margin: 0 0 0.8em 0;&lt;br /&gt;
font-size: 2em;&lt;br /&gt;
font-weight: normal;&lt;br /&gt;
color: var(--color-base, #202122);&lt;br /&gt;
&amp;quot;&amp;gt;&lt;br /&gt;
&#039;&#039;&#039;AOWIS – Afritic Open Water Infrastructure System&#039;&#039;&#039;&lt;br /&gt;
&amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[File:Logo.png|frameless|right|150px]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div&amp;gt;&lt;br /&gt;
&amp;lt;p style=&amp;quot;margin: 0 0 0.6em 0; font-size: 1.15em;&amp;quot;&amp;gt;&lt;br /&gt;
&#039;&#039;&#039;AOWIS&#039;&#039;&#039; (&#039;&#039;&#039;A&#039;&#039;&#039;fritic &#039;&#039;&#039;O&#039;&#039;&#039;pen &#039;&#039;&#039;W&#039;&#039;&#039;ater &#039;&#039;&#039;I&#039;&#039;&#039;nfrastructure &#039;&#039;&#039;S&#039;&#039;&#039;ystem) is an open system for planning, designing, modelling, building, operating, maintaining, and extending safe and reliable &#039;&#039;&#039;water and irrigation infrastructure&#039;&#039;&#039; throughout its lifecycle.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p style=&amp;quot;margin: 0 0 0.6em 0; font-size: 1.15em;&amp;quot;&amp;gt;&lt;br /&gt;
AOWIS brings together open technical standards, open-source software, shared infrastructure models, engineering methods, reference implementations, operational guidance, and training. It provides a common foundation for modelling, simulation, monitoring, control, automation, data exchange, and day-to-day operation.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p style=&amp;quot;margin: 0; font-size: 1.15em;&amp;quot;&amp;gt;&lt;br /&gt;
It is intended for communities, utilities, organizations, engineers, and others involved in water infrastructure, while remaining practical under difficult conditions such as intermittent connectivity, unreliable power, limited technical resources, and the need for local autonomous operation.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;margin-top: 0.8em; font-size: 0.9em; line-height: 1.5; display: flex; flex-wrap: wrap; gap: 0.4em 1.25em;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;span style=&amp;quot;white-space: nowrap;&amp;quot;&amp;gt;&#039;&#039;&#039;[[#Software &amp;amp; Downloads|Software &amp;amp; Downloads]]&#039;&#039;&#039;&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;span style=&amp;quot;white-space: nowrap;&amp;quot;&amp;gt;&#039;&#039;&#039;[[#Community &amp;amp; Participation|Community &amp;amp; Participation]]&#039;&#039;&#039;&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;span style=&amp;quot;white-space: nowrap;&amp;quot;&amp;gt;&#039;&#039;&#039;[[Standard:Main_Page|Access the Standard]]&#039;&#039;&#039;&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;/div&gt;</summary>
		<author><name>Samuel</name></author>
	</entry>
	<entry>
		<id>https://aowis.org/index.php?title=Measurement:Canonical_Units&amp;diff=782</id>
		<title>Measurement:Canonical Units</title>
		<link rel="alternate" type="text/html" href="https://aowis.org/index.php?title=Measurement:Canonical_Units&amp;diff=782"/>
		<updated>2026-09-25T00:38:27Z</updated>

		<summary type="html">&lt;p&gt;Samuel: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* Part of: [[Measurement:Main_Page]]&lt;br /&gt;
* Related to: [[Measurement:Units]]&lt;br /&gt;
&lt;br /&gt;
This page is the normative registry of canonical measurement quantities and units used by AOWIS.&lt;br /&gt;
&lt;br /&gt;
The representation and conversion rules governing these quantities are defined in [[Measurement:Units]].&lt;br /&gt;
&lt;br /&gt;
UCUM&amp;lt;ref name=&amp;quot;UCUM&amp;quot;&amp;gt;Unified Code for Units of Measure (UCUM) https://ucum.org&amp;lt;/ref&amp;gt; is used for machine-readable physical unit identifiers.&lt;br /&gt;
&lt;br /&gt;
== Identifier and Field-Naming Rules ==&lt;br /&gt;
&lt;br /&gt;
The canonical unit assigned to each measurement quantity in this registry is authoritative.&lt;br /&gt;
&lt;br /&gt;
When a unit identifier is explicitly represented, it MUST use the canonical UCUM identifier defined here.&lt;br /&gt;
&lt;br /&gt;
The AOWIS identifier suffix is an ASCII-safe naming convention used for fixed-schema field names, property names, database columns, and similar technical identifiers.&lt;br /&gt;
&lt;br /&gt;
The suffix convention is:&lt;br /&gt;
&lt;br /&gt;
* division is represented by &amp;lt;code&amp;gt;_per_&amp;lt;/code&amp;gt;;&lt;br /&gt;
* multiplication is represented by &amp;lt;code&amp;gt;_&amp;lt;/code&amp;gt;;&lt;br /&gt;
* unit symbols are normalized to lower case where required for identifier naming;&lt;br /&gt;
* quantity-specific semantic qualifiers MAY be included where a literal unit-only suffix would be ambiguous;&lt;br /&gt;
* dimensionless fields with canonical UCUM unit &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt; normally omit a unit suffix.&lt;br /&gt;
&lt;br /&gt;
For example:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
m3/h        -&amp;gt; m3_per_h&lt;br /&gt;
m/s         -&amp;gt; m_per_s&lt;br /&gt;
kW.h/m3     -&amp;gt; kw_h_per_m3&lt;br /&gt;
mm2/(100.m) -&amp;gt; mm2_per_100m&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The AOWIS identifier suffix is not itself a UCUM unit identifier.&lt;br /&gt;
&lt;br /&gt;
For generic or dynamically typed measurement values, the resolved measurement quantity determines the canonical unit through this registry.&lt;br /&gt;
&lt;br /&gt;
== Length and Distance Quantities ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Measurement Quantity Identifier !! Definition !! Canonical Unit !! UCUM Identifier !! AOWIS Identifier Suffix !! AOWIS Model / EPANET Mapping&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;length&amp;lt;/code&amp;gt; || Linear spatial extent along an object or path || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || Pipe and link length&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;elevation&amp;lt;/code&amp;gt; || Vertical height relative to an engineering or hydraulic datum || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || Junction, tank, reservoir, and terrain elevation&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;altitude&amp;lt;/code&amp;gt; || Vertical position reported by a geographic positioning source || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || Geographic altitude; not necessarily suitable as hydraulic elevation&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;distance&amp;lt;/code&amp;gt; || Spatial separation between positions || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || Derived geometric distance&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;vertical_offset&amp;lt;/code&amp;gt; || Vertical difference between referenced elevations or heads || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || Elevation, tank-bottom, and reservoir-head offsets&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;link_diameter&amp;lt;/code&amp;gt; || Internal or nominal diameter of a pipe or valve || millimetre (mm) || &amp;lt;code&amp;gt;mm&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;mm&amp;lt;/code&amp;gt; || EPANET pipe and valve diameter&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;tank_diameter&amp;lt;/code&amp;gt; || Internal diameter of a cylindrical storage tank || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || EPANET tank diameter&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;darcy_weisbach_roughness_height&amp;lt;/code&amp;gt; || Absolute pipe-wall roughness height used by the Darcy-Weisbach formulation || millimetre (mm) || &amp;lt;code&amp;gt;mm&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;mm&amp;lt;/code&amp;gt; || EPANET Darcy-Weisbach pipe roughness&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Geographic Coordinate Quantities ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Measurement Quantity Identifier !! Definition !! Canonical Unit !! UCUM Identifier !! AOWIS Identifier Suffix !! AOWIS Model / EPANET Mapping&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;latitude&amp;lt;/code&amp;gt; || Angular position north or south of the equator || degree (°) || &amp;lt;code&amp;gt;deg&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;deg&amp;lt;/code&amp;gt; || WGS 84 latitude&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;longitude&amp;lt;/code&amp;gt; || Angular position east or west of the prime meridian || degree (°) || &amp;lt;code&amp;gt;deg&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;deg&amp;lt;/code&amp;gt; || WGS 84 longitude&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;projected_easting&amp;lt;/code&amp;gt; || Eastward coordinate within a projected coordinate reference system || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || Projected-coordinate easting&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;projected_northing&amp;lt;/code&amp;gt; || Northward coordinate within a projected coordinate reference system || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || Projected-coordinate northing&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;local_x&amp;lt;/code&amp;gt; || X coordinate within an explicitly defined local engineering coordinate system || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || Local coordinates when the coordinate system is defined in metres&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;local_y&amp;lt;/code&amp;gt; || Y coordinate within an explicitly defined local engineering coordinate system || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || Local coordinates when the coordinate system is defined in metres&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Area and Volume Quantities ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Measurement Quantity Identifier !! Definition !! Canonical Unit !! UCUM Identifier !! AOWIS Identifier Suffix !! AOWIS Model / EPANET Mapping&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;area&amp;lt;/code&amp;gt; || Two-dimensional spatial extent || square metre (m²) || &amp;lt;code&amp;gt;m2&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m2&amp;lt;/code&amp;gt; || Tank cross-sectional area and other geometric areas&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;volume&amp;lt;/code&amp;gt; || Three-dimensional spatial extent or storage capacity || cubic metre (m³) || &amp;lt;code&amp;gt;m3&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m3&amp;lt;/code&amp;gt; || Tank volume&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Flow and Transport Quantities ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Measurement Quantity Identifier&lt;br /&gt;
!! Definition&lt;br /&gt;
!! Canonical Unit&lt;br /&gt;
!! UCUM Identifier&lt;br /&gt;
!! AOWIS Identifier Suffix&lt;br /&gt;
!! AOWIS Model / EPANET Mapping&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;volumetric_flow_rate&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Volume transported per unit time&lt;br /&gt;
|| cubic metre per hour (m³/h)&lt;br /&gt;
|| &amp;lt;code&amp;gt;m3/h&amp;lt;/code&amp;gt;&lt;br /&gt;
|| &amp;lt;code&amp;gt;m3_per_h&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Demand, link flow, leakage flow, emitter flow, and pump-curve flow&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;velocity&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Rate of linear movement&lt;br /&gt;
|| metre per second (m/s)&lt;br /&gt;
|| &amp;lt;code&amp;gt;m/s&amp;lt;/code&amp;gt;&lt;br /&gt;
|| &amp;lt;code&amp;gt;m_per_s&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Link flow velocity&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;molecular_diffusivity&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Molecular diffusion coefficient of a chemical species&lt;br /&gt;
|| square metre per second (m²/s)&lt;br /&gt;
|| &amp;lt;code&amp;gt;m2/s&amp;lt;/code&amp;gt;&lt;br /&gt;
|| &amp;lt;code&amp;gt;m2_per_s&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Physical molecular diffusivity used by the AOWIS multi-species model; backend-relative representations such as EPANET-MSX relative diffusivity are converted at the adapter boundary&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;longitudinal_dispersion_coefficient&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Longitudinal dispersion coefficient describing axial spreading of a transported species&lt;br /&gt;
|| square metre per second (m²/s)&lt;br /&gt;
|| &amp;lt;code&amp;gt;m2/s&amp;lt;/code&amp;gt;&lt;br /&gt;
|| &amp;lt;code&amp;gt;m2_per_s&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Multi-species longitudinal dispersion&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Hydraulic Head, Pressure, and Stress Quantities ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Measurement Quantity Identifier !! Definition !! Canonical Unit !! UCUM Identifier !! AOWIS Identifier Suffix !! AOWIS Model / EPANET Mapping&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;hydraulic_head&amp;lt;/code&amp;gt; || Total mechanical energy per unit weight of fluid expressed as an equivalent fluid-column height || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || Junction, reservoir, and tank hydraulic head&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;pressure_head&amp;lt;/code&amp;gt; || Fluid pressure expressed as an equivalent fluid-column height || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || EPANET node pressure, pressure-driven demand thresholds, and pressure-control valve settings&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;water_level&amp;lt;/code&amp;gt; || Height of a water surface relative to a defined local reference level || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || Initial, minimum, maximum, and simulated tank levels&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;head_gain&amp;lt;/code&amp;gt; || Increase in hydraulic head across an energy-adding component || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || Pump curves and pump simulation results&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;head_loss&amp;lt;/code&amp;gt; || Reduction in hydraulic head across a hydraulic component || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || Pipes, valves, and other energy-dissipating components&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;head_loss_gradient&amp;lt;/code&amp;gt; || Hydraulic head loss per unit pipe length || metre per kilometre (m/km) || &amp;lt;code&amp;gt;m/km&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m_per_km&amp;lt;/code&amp;gt; || EPANET pipe head-loss reporting&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;pressure&amp;lt;/code&amp;gt; || Normal force per unit area within a fluid system || kilopascal (kPa) || &amp;lt;code&amp;gt;kPa&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;kpa&amp;lt;/code&amp;gt; || Physical pressure measurements, sensors, SCADA data, and external exchange&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;stress&amp;lt;/code&amp;gt; || Internal force per unit area within a material || megapascal (MPa) || &amp;lt;code&amp;gt;MPa&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;mpa&amp;lt;/code&amp;gt; || Structural and material analysis&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Time Quantities ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Measurement Quantity Identifier&lt;br /&gt;
!! Definition&lt;br /&gt;
!! Canonical Unit&lt;br /&gt;
!! UCUM Identifier&lt;br /&gt;
!! AOWIS Identifier Suffix&lt;br /&gt;
!! AOWIS Model / EPANET Mapping&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;elapsed_time&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Time elapsed from a defined simulation or process origin&lt;br /&gt;
|| second (s)&lt;br /&gt;
|| &amp;lt;code&amp;gt;s&amp;lt;/code&amp;gt;&lt;br /&gt;
|| &amp;lt;code&amp;gt;s&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Simulation elapsed time and time-based control triggers&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;duration&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Length of a time interval&lt;br /&gt;
|| second (s)&lt;br /&gt;
|| &amp;lt;code&amp;gt;s&amp;lt;/code&amp;gt;&lt;br /&gt;
|| &amp;lt;code&amp;gt;s&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Simulation duration and time steps&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;time_of_day&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Time elapsed since the start of the current day&lt;br /&gt;
|| second (s)&lt;br /&gt;
|| &amp;lt;code&amp;gt;s&amp;lt;/code&amp;gt;&lt;br /&gt;
|| &amp;lt;code&amp;gt;s&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Simulation start time and clock-time controls&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The canonical unit second does not imply integral-second resolution. Sub-second durations and time steps are represented as fractional seconds. For example, a time step of one millisecond is represented canonically as &amp;lt;code&amp;gt;0.001 s&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
== Hydraulic Coefficients and Other Dimensionless Quantities ==&lt;br /&gt;
&lt;br /&gt;
The canonical UCUM unit identifier for all quantities in this section is &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;. The AOWIS unit suffix is omitted.&lt;br /&gt;
&lt;br /&gt;
Semantic terms such as &amp;lt;code&amp;gt;ratio&amp;lt;/code&amp;gt;, &amp;lt;code&amp;gt;factor&amp;lt;/code&amp;gt;, &amp;lt;code&amp;gt;coefficient&amp;lt;/code&amp;gt;, &amp;lt;code&amp;gt;multiplier&amp;lt;/code&amp;gt;, &amp;lt;code&amp;gt;number&amp;lt;/code&amp;gt;, and &amp;lt;code&amp;gt;exponent&amp;lt;/code&amp;gt; describe the quantity and are not unit suffixes.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Measurement Quantity Identifier&lt;br /&gt;
!! Definition&lt;br /&gt;
!! UCUM Identifier&lt;br /&gt;
!! AOWIS Identifier Suffix&lt;br /&gt;
!! AOWIS Model / EPANET Mapping&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;hazen_williams_roughness_coefficient&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Hazen-Williams pipe roughness coefficient&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| EPANET Hazen-Williams roughness&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;chezy_manning_roughness_coefficient&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Chezy-Manning pipe roughness coefficient&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| EPANET Chezy-Manning roughness&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;minor_loss_coefficient&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Coefficient representing local hydraulic losses&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| Pipe and valve minor loss; TCV setting&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;darcy_weisbach_friction_factor&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Darcy-Weisbach friction factor&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| Pipe simulation result&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;pump_speed_ratio&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Pump rotational speed relative to nominal or reference speed&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| Pump setting, result, pattern, control, and rule values&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;pattern_multiplier&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Factor applied by a hydraulic or energy pattern&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| EPANET pattern factor&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;demand_multiplier&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Global factor applied to base demands&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| EPANET demand multiplier&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;pressure_exponent&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Exponent used by the pressure-driven demand relation&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| EPANET pressure exponent&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;emitter_exponent&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Exponent used by the emitter pressure-flow relation&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| EPANET emitter exponent&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;reaction_order&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Order of a bulk, wall, or tank reaction equation&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| EPANET reaction order&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;specific_gravity&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Fluid density relative to a defined reference density&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| EPANET specific gravity&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;relative_viscosity&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Kinematic viscosity relative to the solver reference&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| EPANET relative viscosity&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;relative_diffusivity&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Molecular diffusivity relative to a defined solver reference diffusivity&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| EPANET and EPANET-MSX relative diffusivity representations&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;peclet_number&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Ratio characterizing advective transport relative to diffusive or dispersive transport&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| Multi-species dispersion; includes solver thresholds based on the Peclet number&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;mixing_fraction&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Fraction of tank volume assigned to the applicable mixing zone&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| EPANET tank mixing fraction&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;hydraulic_accuracy&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Relative hydraulic convergence criterion&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| EPANET hydraulic accuracy&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;hydraulic_damping_limit&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Relative threshold controlling solver damping or status checks&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| EPANET damping limit&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;relative_error&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Relative numerical error&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| Hydraulic and water-quality numerical error, tolerance, and simulation statistics&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;flow_balance_ratio&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Ratio of total outflow to total inflow&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| EPANET flow-balance reporting&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;quality_mass_balance_ratio&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Water-quality mass-conservation ratio&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| EPANET and multi-species quality mass-balance reporting&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Percentage Quantities ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Measurement Quantity Identifier !! Definition !! Canonical Unit !! UCUM Identifier !! AOWIS Identifier Suffix !! AOWIS Model / EPANET Mapping&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;efficiency&amp;lt;/code&amp;gt; || Ratio of useful output to total input expressed as a percentage || percent (%) || &amp;lt;code&amp;gt;%&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;percent&amp;lt;/code&amp;gt; || Pump efficiency and efficiency curves&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;relative_flow&amp;lt;/code&amp;gt; || Flow relative to a defined reference flow || percent (%) || &amp;lt;code&amp;gt;%&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;percent&amp;lt;/code&amp;gt; || Valve characteristic curves&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;valve_position&amp;lt;/code&amp;gt; || Valve opening position relative to its operating range || percent (%) || &amp;lt;code&amp;gt;%&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;percent&amp;lt;/code&amp;gt; || Position-control valves&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;source_trace_percentage&amp;lt;/code&amp;gt; || Proportion of water originating from a specified source node || percent (%) || &amp;lt;code&amp;gt;%&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;percent&amp;lt;/code&amp;gt; || EPANET source-trace analysis&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;operating_time_percentage&amp;lt;/code&amp;gt; || Fraction of a reporting period during which equipment operates || percent (%) || &amp;lt;code&amp;gt;%&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;percent&amp;lt;/code&amp;gt; || Pump energy reporting&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;demand_reduction_percentage&amp;lt;/code&amp;gt; || Reduction in delivered demand relative to requested demand || percent (%) || &amp;lt;code&amp;gt;%&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;percent&amp;lt;/code&amp;gt; || Hydraulic statistics&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;leakage_loss_percentage&amp;lt;/code&amp;gt; || Leakage loss relative to total system inflow || percent (%) || &amp;lt;code&amp;gt;%&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;percent&amp;lt;/code&amp;gt; || Leakage statistics&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Reaction and Leakage Quantities ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Measurement Quantity Identifier !! Definition !! Canonical Unit !! UCUM Identifier !! AOWIS Identifier Suffix !! AOWIS Model / EPANET Mapping&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;first_order_bulk_reaction_coefficient&amp;lt;/code&amp;gt; || First-order reaction-rate coefficient within the bulk fluid || per day (d⁻¹) || &amp;lt;code&amp;gt;/d&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;per_d&amp;lt;/code&amp;gt; || Global, pipe, and tank first-order bulk reactions&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;first_order_wall_reaction_coefficient&amp;lt;/code&amp;gt; || First-order reaction-rate coefficient at a pipe wall || metre per day (m/d) || &amp;lt;code&amp;gt;m/d&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m_per_d&amp;lt;/code&amp;gt; || Global and pipe first-order wall reactions&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;leak_area_per_100m_pipe_length&amp;lt;/code&amp;gt; || Effective leak area assigned per 100 metres of pipe length || square millimetre per 100 metres (mm²/100 m) || &amp;lt;code&amp;gt;mm2/(100.m)&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;mm2_per_100m&amp;lt;/code&amp;gt; || EPANET 2.3 FAVAD leak area; EPANET uses 100 project length units and the adapter converts when required&amp;lt;ref name=&amp;quot;EPANET23&amp;quot;&amp;gt;OWA-EPANET 2.3 release notes https://github.com/OpenWaterAnalytics/EPANET/blob/v2.3/ReleaseNotes2_3.md&amp;lt;/ref&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;leak_area_expansion_per_pressure_head&amp;lt;/code&amp;gt; || Increase in effective leak area per unit pressure head || square millimetre per metre of pressure head (mm²/m) || &amp;lt;code&amp;gt;mm2/m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;mm2_per_m_head&amp;lt;/code&amp;gt; || EPANET 2.3 FAVAD leak expansion&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Water Quality Quantities ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Measurement Quantity Identifier&lt;br /&gt;
!! Definition&lt;br /&gt;
!! Canonical Unit&lt;br /&gt;
!! UCUM Identifier&lt;br /&gt;
!! AOWIS Identifier Suffix&lt;br /&gt;
!! AOWIS Model / EPANET Mapping&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;chemical_mass_concentration&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Mass concentration of a chemical substance in water&lt;br /&gt;
|| milligram per litre (mg/L)&lt;br /&gt;
|| &amp;lt;code&amp;gt;mg/L&amp;lt;/code&amp;gt;&lt;br /&gt;
|| &amp;lt;code&amp;gt;mg_per_l&amp;lt;/code&amp;gt;&lt;br /&gt;
|| EPANET chemical quality; multi-species bulk species using a mass basis&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;chemical_amount_concentration&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Amount-of-substance concentration of a chemical substance in water&lt;br /&gt;
|| millimole per litre (mmol/L)&lt;br /&gt;
|| &amp;lt;code&amp;gt;mmol/L&amp;lt;/code&amp;gt;&lt;br /&gt;
|| &amp;lt;code&amp;gt;mmol_per_l&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Multi-species bulk species using an amount-of-substance basis&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;chemical_surface_mass_density&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Mass of a chemical species associated with a surface per unit surface area&lt;br /&gt;
|| milligram per square metre (mg/m²)&lt;br /&gt;
|| &amp;lt;code&amp;gt;mg/m2&amp;lt;/code&amp;gt;&lt;br /&gt;
|| &amp;lt;code&amp;gt;mg_per_m2&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Multi-species wall species using a mass basis&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;chemical_surface_amount_density&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Amount of a chemical species associated with a surface per unit surface area&lt;br /&gt;
|| millimole per square metre (mmol/m²)&lt;br /&gt;
|| &amp;lt;code&amp;gt;mmol/m2&amp;lt;/code&amp;gt;&lt;br /&gt;
|| &amp;lt;code&amp;gt;mmol_per_m2&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Multi-species wall species using an amount-of-substance basis&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;chemical_mass_flow_rate&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Chemical mass introduced into or transported through the system per unit time&lt;br /&gt;
|| milligram per minute (mg/min)&lt;br /&gt;
|| &amp;lt;code&amp;gt;mg/min&amp;lt;/code&amp;gt;&lt;br /&gt;
|| &amp;lt;code&amp;gt;mg_per_min&amp;lt;/code&amp;gt;&lt;br /&gt;
|| EPANET mass-booster source strength; multi-species MASS source using a mass basis&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;chemical_amount_flow_rate&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Amount of chemical substance introduced into or transported through the system per unit time&lt;br /&gt;
|| millimole per minute (mmol/min)&lt;br /&gt;
|| &amp;lt;code&amp;gt;mmol/min&amp;lt;/code&amp;gt;&lt;br /&gt;
|| &amp;lt;code&amp;gt;mmol_per_min&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Multi-species MASS source using an amount-of-substance basis&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;water_age&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Time elapsed since water entered the modelled distribution system&lt;br /&gt;
|| hour (h)&lt;br /&gt;
|| &amp;lt;code&amp;gt;h&amp;lt;/code&amp;gt;&lt;br /&gt;
|| &amp;lt;code&amp;gt;h&amp;lt;/code&amp;gt;&lt;br /&gt;
|| EPANET water-age analysis&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Power, Energy, and Electrical Quantities ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Measurement Quantity Identifier !! Definition !! Canonical Unit !! UCUM Identifier !! AOWIS Identifier Suffix !! AOWIS Model / EPANET Mapping&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;power&amp;lt;/code&amp;gt; || Rate of energy transfer || kilowatt (kW) || &amp;lt;code&amp;gt;kW&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;kw&amp;lt;/code&amp;gt; || Pump power and electrical power&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;energy&amp;lt;/code&amp;gt; || Work performed or energy transferred || kilowatt-hour (kWh) || &amp;lt;code&amp;gt;kW.h&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;kw_h&amp;lt;/code&amp;gt; || Pump energy consumption&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;energy_intensity&amp;lt;/code&amp;gt; || Energy consumed per unit volume || kilowatt-hour per cubic metre (kWh/m³) || &amp;lt;code&amp;gt;kW.h/m3&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;kw_h_per_m3&amp;lt;/code&amp;gt; || Pump energy-use reporting&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;electric_current&amp;lt;/code&amp;gt; || Rate of electric charge flow || ampere (A) || &amp;lt;code&amp;gt;A&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;a&amp;lt;/code&amp;gt; || Electrical model&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;voltage&amp;lt;/code&amp;gt; || Electric potential difference || volt (V) || &amp;lt;code&amp;gt;V&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;v&amp;lt;/code&amp;gt; || Electrical model&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;electrical_resistance&amp;lt;/code&amp;gt; || Opposition to electric current flow || ohm (Ω) || &amp;lt;code&amp;gt;Ohm&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;ohm&amp;lt;/code&amp;gt; || Electrical model&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;capacitance&amp;lt;/code&amp;gt; || Ability to store electric charge || farad (F) || &amp;lt;code&amp;gt;F&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;f&amp;lt;/code&amp;gt; || Electrical model&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Context-Dependent Quantity Resolution ==&lt;br /&gt;
&lt;br /&gt;
Some Model concepts resolve to different registered measurement quantities depending on their context. The representation requirements for such values are defined in [[Measurement:Units]] and, where applicable, the corresponding Measurement subsystem specification.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Model Concept&lt;br /&gt;
!! Resolved Measurement Quantity&lt;br /&gt;
|-&lt;br /&gt;
| Valve setting&lt;br /&gt;
|| PRV, PSV, and PBV: &amp;lt;code&amp;gt;pressure_head&amp;lt;/code&amp;gt;; FCV: &amp;lt;code&amp;gt;volumetric_flow_rate&amp;lt;/code&amp;gt;; TCV: &amp;lt;code&amp;gt;minor_loss_coefficient&amp;lt;/code&amp;gt;; PCV: &amp;lt;code&amp;gt;valve_position&amp;lt;/code&amp;gt;; GPV: curve reference rather than a measurement value&lt;br /&gt;
|-&lt;br /&gt;
| Pump setting&lt;br /&gt;
|| &amp;lt;code&amp;gt;pump_speed_ratio&amp;lt;/code&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Control trigger&lt;br /&gt;
|| &amp;lt;code&amp;gt;water_level&amp;lt;/code&amp;gt;, &amp;lt;code&amp;gt;pressure_head&amp;lt;/code&amp;gt;, &amp;lt;code&amp;gt;elapsed_time&amp;lt;/code&amp;gt;, or &amp;lt;code&amp;gt;time_of_day&amp;lt;/code&amp;gt;, depending on control type&lt;br /&gt;
|-&lt;br /&gt;
| Control or rule action setting&lt;br /&gt;
|| The measurement quantity supported by the target link type&lt;br /&gt;
|-&lt;br /&gt;
| Rule premise value&lt;br /&gt;
|| The measurement quantity selected by the rule variable&lt;br /&gt;
|-&lt;br /&gt;
| Initial or simulated standard water quality&lt;br /&gt;
|| &amp;lt;code&amp;gt;chemical_mass_concentration&amp;lt;/code&amp;gt;, &amp;lt;code&amp;gt;water_age&amp;lt;/code&amp;gt;, or &amp;lt;code&amp;gt;source_trace_percentage&amp;lt;/code&amp;gt;, depending on quality-analysis mode&lt;br /&gt;
|-&lt;br /&gt;
| Standard quality-source strength&lt;br /&gt;
|| &amp;lt;code&amp;gt;chemical_mass_concentration&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;chemical_mass_flow_rate&amp;lt;/code&amp;gt;, depending on source type&lt;br /&gt;
|-&lt;br /&gt;
| Multi-species bulk quality value&lt;br /&gt;
|| Mass-basis species: &amp;lt;code&amp;gt;chemical_mass_concentration&amp;lt;/code&amp;gt;; amount-of-substance-basis species: &amp;lt;code&amp;gt;chemical_amount_concentration&amp;lt;/code&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Multi-species wall quality value&lt;br /&gt;
|| Mass-basis species: &amp;lt;code&amp;gt;chemical_surface_mass_density&amp;lt;/code&amp;gt;; amount-of-substance-basis species: &amp;lt;code&amp;gt;chemical_surface_amount_density&amp;lt;/code&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Multi-species initial quality&lt;br /&gt;
|| The same quantity as the corresponding species value: bulk species resolve to &amp;lt;code&amp;gt;chemical_mass_concentration&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;chemical_amount_concentration&amp;lt;/code&amp;gt;; wall species resolve to &amp;lt;code&amp;gt;chemical_surface_mass_density&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;chemical_surface_amount_density&amp;lt;/code&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Multi-species absolute error tolerance&lt;br /&gt;
|| The same measurement quantity as the corresponding species value&lt;br /&gt;
|-&lt;br /&gt;
| Multi-species relative error tolerance&lt;br /&gt;
|| &amp;lt;code&amp;gt;relative_error&amp;lt;/code&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Multi-species source strength&lt;br /&gt;
|| CONCEN, SETPOINT, and FLOWPACED sources resolve to &amp;lt;code&amp;gt;chemical_mass_concentration&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;chemical_amount_concentration&amp;lt;/code&amp;gt; according to the species basis; MASS sources resolve to &amp;lt;code&amp;gt;chemical_mass_flow_rate&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;chemical_amount_flow_rate&amp;lt;/code&amp;gt;. Wall species are not valid node-source species.&lt;br /&gt;
|-&lt;br /&gt;
| Reaction coefficient&lt;br /&gt;
|| The applicable reaction-coefficient quantity determined by reaction order&lt;br /&gt;
|-&lt;br /&gt;
| Molecular diffusion coefficient&lt;br /&gt;
|| &amp;lt;code&amp;gt;molecular_diffusivity&amp;lt;/code&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Fixed longitudinal dispersion coefficient&lt;br /&gt;
|| &amp;lt;code&amp;gt;longitudinal_dispersion_coefficient&amp;lt;/code&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Peclet-number dispersion threshold&lt;br /&gt;
|| &amp;lt;code&amp;gt;peclet_number&amp;lt;/code&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Emitter coefficient&lt;br /&gt;
|| Equation-dependent coefficient in &amp;lt;code&amp;gt;Q = C H^n&amp;lt;/code&amp;gt;; no single fixed canonical unit applies independently of &amp;lt;code&amp;gt;n&amp;lt;/code&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Generic curve coordinate&lt;br /&gt;
|| The measurement quantity defined by the curve type&lt;br /&gt;
|-&lt;br /&gt;
| Report threshold&lt;br /&gt;
|| The measurement quantity of the corresponding report field&lt;br /&gt;
|-&lt;br /&gt;
| EPANET map or backdrop coordinate&lt;br /&gt;
|| The applicable geographic, projected, or local coordinate quantity after the coordinate representation is resolved&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;/div&gt;</summary>
		<author><name>Samuel</name></author>
	</entry>
	<entry>
		<id>https://aowis.org/index.php?title=Measurement:Canonical_Units&amp;diff=781</id>
		<title>Measurement:Canonical Units</title>
		<link rel="alternate" type="text/html" href="https://aowis.org/index.php?title=Measurement:Canonical_Units&amp;diff=781"/>
		<updated>2026-09-25T00:29:09Z</updated>

		<summary type="html">&lt;p&gt;Samuel: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* Part of: [[Measurement:Main_Page]]&lt;br /&gt;
* Related to: [[Measurement:Units]]&lt;br /&gt;
&lt;br /&gt;
This page is the normative registry of canonical measurement quantities and units used by AOWIS.&lt;br /&gt;
&lt;br /&gt;
The representation and conversion rules governing these quantities are defined in [[Measurement:Units]].&lt;br /&gt;
&lt;br /&gt;
UCUM&amp;lt;ref name=&amp;quot;UCUM&amp;quot;&amp;gt;Unified Code for Units of Measure (UCUM) https://ucum.org&amp;lt;/ref&amp;gt; is used for machine-readable physical unit identifiers.&lt;br /&gt;
&lt;br /&gt;
== Identifier and Field-Naming Rules ==&lt;br /&gt;
&lt;br /&gt;
The canonical unit assigned to each measurement quantity in this registry is authoritative.&lt;br /&gt;
&lt;br /&gt;
When a unit identifier is explicitly represented, it MUST use the canonical UCUM identifier defined here.&lt;br /&gt;
&lt;br /&gt;
The AOWIS identifier suffix is an ASCII-safe naming convention used for fixed-schema field names, property names, database columns, and similar technical identifiers.&lt;br /&gt;
&lt;br /&gt;
The suffix convention is:&lt;br /&gt;
&lt;br /&gt;
* division is represented by &amp;lt;code&amp;gt;_per_&amp;lt;/code&amp;gt;;&lt;br /&gt;
* multiplication is represented by &amp;lt;code&amp;gt;_&amp;lt;/code&amp;gt;;&lt;br /&gt;
* unit symbols are normalized to lower case where required for identifier naming;&lt;br /&gt;
* quantity-specific semantic qualifiers MAY be included where a literal unit-only suffix would be ambiguous;&lt;br /&gt;
* dimensionless fields with canonical UCUM unit &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt; normally omit a unit suffix.&lt;br /&gt;
&lt;br /&gt;
For example:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
m3/h        -&amp;gt; m3_per_h&lt;br /&gt;
m/s         -&amp;gt; m_per_s&lt;br /&gt;
kW.h/m3     -&amp;gt; kw_h_per_m3&lt;br /&gt;
mm2/(100.m) -&amp;gt; mm2_per_100m&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The AOWIS identifier suffix is not itself a UCUM unit identifier.&lt;br /&gt;
&lt;br /&gt;
For generic or dynamically typed measurement values, the resolved measurement quantity determines the canonical unit through this registry.&lt;br /&gt;
&lt;br /&gt;
== Length and Distance Quantities ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Measurement Quantity Identifier !! Definition !! Canonical Unit !! UCUM Identifier !! AOWIS Identifier Suffix !! AOWIS Model / EPANET Mapping&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;length&amp;lt;/code&amp;gt; || Linear spatial extent along an object or path || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || Pipe and link length&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;elevation&amp;lt;/code&amp;gt; || Vertical height relative to an engineering or hydraulic datum || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || Junction, tank, reservoir, and terrain elevation&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;altitude&amp;lt;/code&amp;gt; || Vertical position reported by a geographic positioning source || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || Geographic altitude; not necessarily suitable as hydraulic elevation&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;distance&amp;lt;/code&amp;gt; || Spatial separation between positions || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || Derived geometric distance&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;vertical_offset&amp;lt;/code&amp;gt; || Vertical difference between referenced elevations or heads || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || Elevation, tank-bottom, and reservoir-head offsets&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;link_diameter&amp;lt;/code&amp;gt; || Internal or nominal diameter of a pipe or valve || millimetre (mm) || &amp;lt;code&amp;gt;mm&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;mm&amp;lt;/code&amp;gt; || EPANET pipe and valve diameter&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;tank_diameter&amp;lt;/code&amp;gt; || Internal diameter of a cylindrical storage tank || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || EPANET tank diameter&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;darcy_weisbach_roughness_height&amp;lt;/code&amp;gt; || Absolute pipe-wall roughness height used by the Darcy-Weisbach formulation || millimetre (mm) || &amp;lt;code&amp;gt;mm&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;mm&amp;lt;/code&amp;gt; || EPANET Darcy-Weisbach pipe roughness&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Geographic Coordinate Quantities ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Measurement Quantity Identifier !! Definition !! Canonical Unit !! UCUM Identifier !! AOWIS Identifier Suffix !! AOWIS Model / EPANET Mapping&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;latitude&amp;lt;/code&amp;gt; || Angular position north or south of the equator || degree (°) || &amp;lt;code&amp;gt;deg&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;deg&amp;lt;/code&amp;gt; || WGS 84 latitude&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;longitude&amp;lt;/code&amp;gt; || Angular position east or west of the prime meridian || degree (°) || &amp;lt;code&amp;gt;deg&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;deg&amp;lt;/code&amp;gt; || WGS 84 longitude&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;projected_easting&amp;lt;/code&amp;gt; || Eastward coordinate within a projected coordinate reference system || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || Projected-coordinate easting&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;projected_northing&amp;lt;/code&amp;gt; || Northward coordinate within a projected coordinate reference system || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || Projected-coordinate northing&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;local_x&amp;lt;/code&amp;gt; || X coordinate within an explicitly defined local engineering coordinate system || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || Local coordinates when the coordinate system is defined in metres&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;local_y&amp;lt;/code&amp;gt; || Y coordinate within an explicitly defined local engineering coordinate system || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || Local coordinates when the coordinate system is defined in metres&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Area and Volume Quantities ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Measurement Quantity Identifier !! Definition !! Canonical Unit !! UCUM Identifier !! AOWIS Identifier Suffix !! AOWIS Model / EPANET Mapping&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;area&amp;lt;/code&amp;gt; || Two-dimensional spatial extent || square metre (m²) || &amp;lt;code&amp;gt;m2&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m2&amp;lt;/code&amp;gt; || Tank cross-sectional area and other geometric areas&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;volume&amp;lt;/code&amp;gt; || Three-dimensional spatial extent or storage capacity || cubic metre (m³) || &amp;lt;code&amp;gt;m3&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m3&amp;lt;/code&amp;gt; || Tank volume&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Flow and Transport Quantities ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Measurement Quantity Identifier&lt;br /&gt;
!! Definition&lt;br /&gt;
!! Canonical Unit&lt;br /&gt;
!! UCUM Identifier&lt;br /&gt;
!! AOWIS Identifier Suffix&lt;br /&gt;
!! AOWIS Model / EPANET Mapping&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;volumetric_flow_rate&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Volume transported per unit time&lt;br /&gt;
|| cubic metre per hour (m³/h)&lt;br /&gt;
|| &amp;lt;code&amp;gt;m3/h&amp;lt;/code&amp;gt;&lt;br /&gt;
|| &amp;lt;code&amp;gt;m3_per_h&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Demand, link flow, leakage flow, emitter flow, and pump-curve flow&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;velocity&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Rate of linear movement&lt;br /&gt;
|| metre per second (m/s)&lt;br /&gt;
|| &amp;lt;code&amp;gt;m/s&amp;lt;/code&amp;gt;&lt;br /&gt;
|| &amp;lt;code&amp;gt;m_per_s&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Link flow velocity&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;molecular_diffusivity&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Molecular diffusion coefficient of a chemical species&lt;br /&gt;
|| square metre per second (m²/s)&lt;br /&gt;
|| &amp;lt;code&amp;gt;m2/s&amp;lt;/code&amp;gt;&lt;br /&gt;
|| &amp;lt;code&amp;gt;m2_per_s&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Multi-species molecular diffusion&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;longitudinal_dispersion_coefficient&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Longitudinal dispersion coefficient describing axial spreading of a transported species&lt;br /&gt;
|| square metre per second (m²/s)&lt;br /&gt;
|| &amp;lt;code&amp;gt;m2/s&amp;lt;/code&amp;gt;&lt;br /&gt;
|| &amp;lt;code&amp;gt;m2_per_s&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Multi-species longitudinal dispersion&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Hydraulic Head, Pressure, and Stress Quantities ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Measurement Quantity Identifier !! Definition !! Canonical Unit !! UCUM Identifier !! AOWIS Identifier Suffix !! AOWIS Model / EPANET Mapping&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;hydraulic_head&amp;lt;/code&amp;gt; || Total mechanical energy per unit weight of fluid expressed as an equivalent fluid-column height || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || Junction, reservoir, and tank hydraulic head&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;pressure_head&amp;lt;/code&amp;gt; || Fluid pressure expressed as an equivalent fluid-column height || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || EPANET node pressure, pressure-driven demand thresholds, and pressure-control valve settings&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;water_level&amp;lt;/code&amp;gt; || Height of a water surface relative to a defined local reference level || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || Initial, minimum, maximum, and simulated tank levels&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;head_gain&amp;lt;/code&amp;gt; || Increase in hydraulic head across an energy-adding component || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || Pump curves and pump simulation results&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;head_loss&amp;lt;/code&amp;gt; || Reduction in hydraulic head across a hydraulic component || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || Pipes, valves, and other energy-dissipating components&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;head_loss_gradient&amp;lt;/code&amp;gt; || Hydraulic head loss per unit pipe length || metre per kilometre (m/km) || &amp;lt;code&amp;gt;m/km&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m_per_km&amp;lt;/code&amp;gt; || EPANET pipe head-loss reporting&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;pressure&amp;lt;/code&amp;gt; || Normal force per unit area within a fluid system || kilopascal (kPa) || &amp;lt;code&amp;gt;kPa&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;kpa&amp;lt;/code&amp;gt; || Physical pressure measurements, sensors, SCADA data, and external exchange&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;stress&amp;lt;/code&amp;gt; || Internal force per unit area within a material || megapascal (MPa) || &amp;lt;code&amp;gt;MPa&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;mpa&amp;lt;/code&amp;gt; || Structural and material analysis&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Time Quantities ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Measurement Quantity Identifier&lt;br /&gt;
!! Definition&lt;br /&gt;
!! Canonical Unit&lt;br /&gt;
!! UCUM Identifier&lt;br /&gt;
!! AOWIS Identifier Suffix&lt;br /&gt;
!! AOWIS Model / EPANET Mapping&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;elapsed_time&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Time elapsed from a defined simulation or process origin&lt;br /&gt;
|| second (s)&lt;br /&gt;
|| &amp;lt;code&amp;gt;s&amp;lt;/code&amp;gt;&lt;br /&gt;
|| &amp;lt;code&amp;gt;s&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Simulation elapsed time and time-based control triggers&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;duration&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Length of a time interval&lt;br /&gt;
|| second (s)&lt;br /&gt;
|| &amp;lt;code&amp;gt;s&amp;lt;/code&amp;gt;&lt;br /&gt;
|| &amp;lt;code&amp;gt;s&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Simulation duration and time steps&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;time_of_day&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Time elapsed since the start of the current day&lt;br /&gt;
|| second (s)&lt;br /&gt;
|| &amp;lt;code&amp;gt;s&amp;lt;/code&amp;gt;&lt;br /&gt;
|| &amp;lt;code&amp;gt;s&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Simulation start time and clock-time controls&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The canonical unit second does not imply integral-second resolution. Sub-second durations and time steps are represented as fractional seconds. For example, a time step of one millisecond is represented canonically as &amp;lt;code&amp;gt;0.001 s&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
== Hydraulic Coefficients and Other Dimensionless Quantities ==&lt;br /&gt;
&lt;br /&gt;
The canonical UCUM unit identifier for all quantities in this section is &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;. The AOWIS unit suffix is omitted.&lt;br /&gt;
&lt;br /&gt;
Semantic terms such as &amp;lt;code&amp;gt;ratio&amp;lt;/code&amp;gt;, &amp;lt;code&amp;gt;factor&amp;lt;/code&amp;gt;, &amp;lt;code&amp;gt;coefficient&amp;lt;/code&amp;gt;, &amp;lt;code&amp;gt;multiplier&amp;lt;/code&amp;gt;, &amp;lt;code&amp;gt;number&amp;lt;/code&amp;gt;, and &amp;lt;code&amp;gt;exponent&amp;lt;/code&amp;gt; describe the quantity and are not unit suffixes.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Measurement Quantity Identifier&lt;br /&gt;
!! Definition&lt;br /&gt;
!! UCUM Identifier&lt;br /&gt;
!! AOWIS Identifier Suffix&lt;br /&gt;
!! AOWIS Model / EPANET Mapping&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;hazen_williams_roughness_coefficient&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Hazen-Williams pipe roughness coefficient&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| EPANET Hazen-Williams roughness&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;chezy_manning_roughness_coefficient&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Chezy-Manning pipe roughness coefficient&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| EPANET Chezy-Manning roughness&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;minor_loss_coefficient&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Coefficient representing local hydraulic losses&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| Pipe and valve minor loss; TCV setting&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;darcy_weisbach_friction_factor&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Darcy-Weisbach friction factor&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| Pipe simulation result&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;pump_speed_ratio&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Pump rotational speed relative to nominal or reference speed&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| Pump setting, result, pattern, control, and rule values&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;pattern_multiplier&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Factor applied by a hydraulic or energy pattern&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| EPANET pattern factor&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;demand_multiplier&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Global factor applied to base demands&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| EPANET demand multiplier&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;pressure_exponent&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Exponent used by the pressure-driven demand relation&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| EPANET pressure exponent&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;emitter_exponent&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Exponent used by the emitter pressure-flow relation&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| EPANET emitter exponent&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;reaction_order&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Order of a bulk, wall, or tank reaction equation&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| EPANET reaction order&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;specific_gravity&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Fluid density relative to a defined reference density&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| EPANET specific gravity&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;relative_viscosity&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Kinematic viscosity relative to the solver reference&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| EPANET relative viscosity&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;relative_diffusivity&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Molecular diffusivity relative to the solver reference&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| EPANET relative diffusivity&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;peclet_number&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Ratio characterizing advective transport relative to diffusive or dispersive transport&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| Multi-species dispersion; includes solver thresholds based on the Peclet number&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;mixing_fraction&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Fraction of tank volume assigned to the applicable mixing zone&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| EPANET tank mixing fraction&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;hydraulic_accuracy&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Relative hydraulic convergence criterion&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| EPANET hydraulic accuracy&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;hydraulic_damping_limit&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Relative threshold controlling solver damping or status checks&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| EPANET damping limit&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;relative_error&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Relative numerical error&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| Hydraulic and water-quality numerical error, tolerance, and simulation statistics&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;flow_balance_ratio&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Ratio of total outflow to total inflow&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| EPANET flow-balance reporting&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;quality_mass_balance_ratio&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Water-quality mass-conservation ratio&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| EPANET and multi-species quality mass-balance reporting&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Percentage Quantities ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Measurement Quantity Identifier !! Definition !! Canonical Unit !! UCUM Identifier !! AOWIS Identifier Suffix !! AOWIS Model / EPANET Mapping&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;efficiency&amp;lt;/code&amp;gt; || Ratio of useful output to total input expressed as a percentage || percent (%) || &amp;lt;code&amp;gt;%&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;percent&amp;lt;/code&amp;gt; || Pump efficiency and efficiency curves&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;relative_flow&amp;lt;/code&amp;gt; || Flow relative to a defined reference flow || percent (%) || &amp;lt;code&amp;gt;%&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;percent&amp;lt;/code&amp;gt; || Valve characteristic curves&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;valve_position&amp;lt;/code&amp;gt; || Valve opening position relative to its operating range || percent (%) || &amp;lt;code&amp;gt;%&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;percent&amp;lt;/code&amp;gt; || Position-control valves&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;source_trace_percentage&amp;lt;/code&amp;gt; || Proportion of water originating from a specified source node || percent (%) || &amp;lt;code&amp;gt;%&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;percent&amp;lt;/code&amp;gt; || EPANET source-trace analysis&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;operating_time_percentage&amp;lt;/code&amp;gt; || Fraction of a reporting period during which equipment operates || percent (%) || &amp;lt;code&amp;gt;%&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;percent&amp;lt;/code&amp;gt; || Pump energy reporting&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;demand_reduction_percentage&amp;lt;/code&amp;gt; || Reduction in delivered demand relative to requested demand || percent (%) || &amp;lt;code&amp;gt;%&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;percent&amp;lt;/code&amp;gt; || Hydraulic statistics&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;leakage_loss_percentage&amp;lt;/code&amp;gt; || Leakage loss relative to total system inflow || percent (%) || &amp;lt;code&amp;gt;%&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;percent&amp;lt;/code&amp;gt; || Leakage statistics&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Reaction and Leakage Quantities ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Measurement Quantity Identifier !! Definition !! Canonical Unit !! UCUM Identifier !! AOWIS Identifier Suffix !! AOWIS Model / EPANET Mapping&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;first_order_bulk_reaction_coefficient&amp;lt;/code&amp;gt; || First-order reaction-rate coefficient within the bulk fluid || per day (d⁻¹) || &amp;lt;code&amp;gt;/d&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;per_d&amp;lt;/code&amp;gt; || Global, pipe, and tank first-order bulk reactions&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;first_order_wall_reaction_coefficient&amp;lt;/code&amp;gt; || First-order reaction-rate coefficient at a pipe wall || metre per day (m/d) || &amp;lt;code&amp;gt;m/d&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m_per_d&amp;lt;/code&amp;gt; || Global and pipe first-order wall reactions&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;leak_area_per_100m_pipe_length&amp;lt;/code&amp;gt; || Effective leak area assigned per 100 metres of pipe length || square millimetre per 100 metres (mm²/100 m) || &amp;lt;code&amp;gt;mm2/(100.m)&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;mm2_per_100m&amp;lt;/code&amp;gt; || EPANET 2.3 FAVAD leak area; EPANET uses 100 project length units and the adapter converts when required&amp;lt;ref name=&amp;quot;EPANET23&amp;quot;&amp;gt;OWA-EPANET 2.3 release notes https://github.com/OpenWaterAnalytics/EPANET/blob/v2.3/ReleaseNotes2_3.md&amp;lt;/ref&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;leak_area_expansion_per_pressure_head&amp;lt;/code&amp;gt; || Increase in effective leak area per unit pressure head || square millimetre per metre of pressure head (mm²/m) || &amp;lt;code&amp;gt;mm2/m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;mm2_per_m_head&amp;lt;/code&amp;gt; || EPANET 2.3 FAVAD leak expansion&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Water Quality Quantities ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Measurement Quantity Identifier&lt;br /&gt;
!! Definition&lt;br /&gt;
!! Canonical Unit&lt;br /&gt;
!! UCUM Identifier&lt;br /&gt;
!! AOWIS Identifier Suffix&lt;br /&gt;
!! AOWIS Model / EPANET Mapping&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;chemical_mass_concentration&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Mass concentration of a chemical substance in water&lt;br /&gt;
|| milligram per litre (mg/L)&lt;br /&gt;
|| &amp;lt;code&amp;gt;mg/L&amp;lt;/code&amp;gt;&lt;br /&gt;
|| &amp;lt;code&amp;gt;mg_per_l&amp;lt;/code&amp;gt;&lt;br /&gt;
|| EPANET chemical quality; multi-species bulk species using a mass basis&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;chemical_amount_concentration&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Amount-of-substance concentration of a chemical substance in water&lt;br /&gt;
|| millimole per litre (mmol/L)&lt;br /&gt;
|| &amp;lt;code&amp;gt;mmol/L&amp;lt;/code&amp;gt;&lt;br /&gt;
|| &amp;lt;code&amp;gt;mmol_per_l&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Multi-species bulk species using an amount-of-substance basis&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;chemical_surface_mass_density&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Mass of a chemical species associated with a surface per unit surface area&lt;br /&gt;
|| milligram per square metre (mg/m²)&lt;br /&gt;
|| &amp;lt;code&amp;gt;mg/m2&amp;lt;/code&amp;gt;&lt;br /&gt;
|| &amp;lt;code&amp;gt;mg_per_m2&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Multi-species wall species using a mass basis&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;chemical_surface_amount_density&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Amount of a chemical species associated with a surface per unit surface area&lt;br /&gt;
|| millimole per square metre (mmol/m²)&lt;br /&gt;
|| &amp;lt;code&amp;gt;mmol/m2&amp;lt;/code&amp;gt;&lt;br /&gt;
|| &amp;lt;code&amp;gt;mmol_per_m2&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Multi-species wall species using an amount-of-substance basis&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;chemical_mass_flow_rate&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Chemical mass introduced into or transported through the system per unit time&lt;br /&gt;
|| milligram per minute (mg/min)&lt;br /&gt;
|| &amp;lt;code&amp;gt;mg/min&amp;lt;/code&amp;gt;&lt;br /&gt;
|| &amp;lt;code&amp;gt;mg_per_min&amp;lt;/code&amp;gt;&lt;br /&gt;
|| EPANET mass-booster source strength; multi-species MASS source using a mass basis&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;chemical_amount_flow_rate&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Amount of chemical substance introduced into or transported through the system per unit time&lt;br /&gt;
|| millimole per minute (mmol/min)&lt;br /&gt;
|| &amp;lt;code&amp;gt;mmol/min&amp;lt;/code&amp;gt;&lt;br /&gt;
|| &amp;lt;code&amp;gt;mmol_per_min&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Multi-species MASS source using an amount-of-substance basis&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;water_age&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Time elapsed since water entered the modelled distribution system&lt;br /&gt;
|| hour (h)&lt;br /&gt;
|| &amp;lt;code&amp;gt;h&amp;lt;/code&amp;gt;&lt;br /&gt;
|| &amp;lt;code&amp;gt;h&amp;lt;/code&amp;gt;&lt;br /&gt;
|| EPANET water-age analysis&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Power, Energy, and Electrical Quantities ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Measurement Quantity Identifier !! Definition !! Canonical Unit !! UCUM Identifier !! AOWIS Identifier Suffix !! AOWIS Model / EPANET Mapping&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;power&amp;lt;/code&amp;gt; || Rate of energy transfer || kilowatt (kW) || &amp;lt;code&amp;gt;kW&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;kw&amp;lt;/code&amp;gt; || Pump power and electrical power&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;energy&amp;lt;/code&amp;gt; || Work performed or energy transferred || kilowatt-hour (kWh) || &amp;lt;code&amp;gt;kW.h&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;kw_h&amp;lt;/code&amp;gt; || Pump energy consumption&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;energy_intensity&amp;lt;/code&amp;gt; || Energy consumed per unit volume || kilowatt-hour per cubic metre (kWh/m³) || &amp;lt;code&amp;gt;kW.h/m3&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;kw_h_per_m3&amp;lt;/code&amp;gt; || Pump energy-use reporting&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;electric_current&amp;lt;/code&amp;gt; || Rate of electric charge flow || ampere (A) || &amp;lt;code&amp;gt;A&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;a&amp;lt;/code&amp;gt; || Electrical model&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;voltage&amp;lt;/code&amp;gt; || Electric potential difference || volt (V) || &amp;lt;code&amp;gt;V&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;v&amp;lt;/code&amp;gt; || Electrical model&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;electrical_resistance&amp;lt;/code&amp;gt; || Opposition to electric current flow || ohm (Ω) || &amp;lt;code&amp;gt;Ohm&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;ohm&amp;lt;/code&amp;gt; || Electrical model&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;capacitance&amp;lt;/code&amp;gt; || Ability to store electric charge || farad (F) || &amp;lt;code&amp;gt;F&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;f&amp;lt;/code&amp;gt; || Electrical model&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Context-Dependent Quantity Resolution ==&lt;br /&gt;
&lt;br /&gt;
Some Model concepts resolve to different registered measurement quantities depending on their context. The representation requirements for such values are defined in [[Measurement:Units]] and, where applicable, the corresponding Measurement subsystem specification.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Model Concept&lt;br /&gt;
!! Resolved Measurement Quantity&lt;br /&gt;
|-&lt;br /&gt;
| Valve setting&lt;br /&gt;
|| PRV, PSV, and PBV: &amp;lt;code&amp;gt;pressure_head&amp;lt;/code&amp;gt;; FCV: &amp;lt;code&amp;gt;volumetric_flow_rate&amp;lt;/code&amp;gt;; TCV: &amp;lt;code&amp;gt;minor_loss_coefficient&amp;lt;/code&amp;gt;; PCV: &amp;lt;code&amp;gt;valve_position&amp;lt;/code&amp;gt;; GPV: curve reference rather than a measurement value&lt;br /&gt;
|-&lt;br /&gt;
| Pump setting&lt;br /&gt;
|| &amp;lt;code&amp;gt;pump_speed_ratio&amp;lt;/code&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Control trigger&lt;br /&gt;
|| &amp;lt;code&amp;gt;water_level&amp;lt;/code&amp;gt;, &amp;lt;code&amp;gt;pressure_head&amp;lt;/code&amp;gt;, &amp;lt;code&amp;gt;elapsed_time&amp;lt;/code&amp;gt;, or &amp;lt;code&amp;gt;time_of_day&amp;lt;/code&amp;gt;, depending on control type&lt;br /&gt;
|-&lt;br /&gt;
| Control or rule action setting&lt;br /&gt;
|| The measurement quantity supported by the target link type&lt;br /&gt;
|-&lt;br /&gt;
| Rule premise value&lt;br /&gt;
|| The measurement quantity selected by the rule variable&lt;br /&gt;
|-&lt;br /&gt;
| Initial or simulated standard water quality&lt;br /&gt;
|| &amp;lt;code&amp;gt;chemical_mass_concentration&amp;lt;/code&amp;gt;, &amp;lt;code&amp;gt;water_age&amp;lt;/code&amp;gt;, or &amp;lt;code&amp;gt;source_trace_percentage&amp;lt;/code&amp;gt;, depending on quality-analysis mode&lt;br /&gt;
|-&lt;br /&gt;
| Standard quality-source strength&lt;br /&gt;
|| &amp;lt;code&amp;gt;chemical_mass_concentration&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;chemical_mass_flow_rate&amp;lt;/code&amp;gt;, depending on source type&lt;br /&gt;
|-&lt;br /&gt;
| Multi-species bulk quality value&lt;br /&gt;
|| Mass-basis species: &amp;lt;code&amp;gt;chemical_mass_concentration&amp;lt;/code&amp;gt;; amount-of-substance-basis species: &amp;lt;code&amp;gt;chemical_amount_concentration&amp;lt;/code&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Multi-species wall quality value&lt;br /&gt;
|| Mass-basis species: &amp;lt;code&amp;gt;chemical_surface_mass_density&amp;lt;/code&amp;gt;; amount-of-substance-basis species: &amp;lt;code&amp;gt;chemical_surface_amount_density&amp;lt;/code&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Multi-species initial quality&lt;br /&gt;
|| The same quantity as the corresponding species value: bulk species resolve to &amp;lt;code&amp;gt;chemical_mass_concentration&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;chemical_amount_concentration&amp;lt;/code&amp;gt;; wall species resolve to &amp;lt;code&amp;gt;chemical_surface_mass_density&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;chemical_surface_amount_density&amp;lt;/code&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Multi-species absolute error tolerance&lt;br /&gt;
|| The same measurement quantity as the corresponding species value&lt;br /&gt;
|-&lt;br /&gt;
| Multi-species relative error tolerance&lt;br /&gt;
|| &amp;lt;code&amp;gt;relative_error&amp;lt;/code&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Multi-species source strength&lt;br /&gt;
|| CONCEN, SETPOINT, and FLOWPACED sources resolve to &amp;lt;code&amp;gt;chemical_mass_concentration&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;chemical_amount_concentration&amp;lt;/code&amp;gt; according to the species basis; MASS sources resolve to &amp;lt;code&amp;gt;chemical_mass_flow_rate&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;chemical_amount_flow_rate&amp;lt;/code&amp;gt;. Wall species are not valid node-source species.&lt;br /&gt;
|-&lt;br /&gt;
| Reaction coefficient&lt;br /&gt;
|| The applicable reaction-coefficient quantity determined by reaction order&lt;br /&gt;
|-&lt;br /&gt;
| Molecular diffusion coefficient&lt;br /&gt;
|| &amp;lt;code&amp;gt;molecular_diffusivity&amp;lt;/code&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Fixed longitudinal dispersion coefficient&lt;br /&gt;
|| &amp;lt;code&amp;gt;longitudinal_dispersion_coefficient&amp;lt;/code&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Peclet-number dispersion threshold&lt;br /&gt;
|| &amp;lt;code&amp;gt;peclet_number&amp;lt;/code&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Emitter coefficient&lt;br /&gt;
|| Equation-dependent coefficient in &amp;lt;code&amp;gt;Q = C H^n&amp;lt;/code&amp;gt;; no single fixed canonical unit applies independently of &amp;lt;code&amp;gt;n&amp;lt;/code&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Generic curve coordinate&lt;br /&gt;
|| The measurement quantity defined by the curve type&lt;br /&gt;
|-&lt;br /&gt;
| Report threshold&lt;br /&gt;
|| The measurement quantity of the corresponding report field&lt;br /&gt;
|-&lt;br /&gt;
| EPANET map or backdrop coordinate&lt;br /&gt;
|| The applicable geographic, projected, or local coordinate quantity after the coordinate representation is resolved&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;/div&gt;</summary>
		<author><name>Samuel</name></author>
	</entry>
	<entry>
		<id>https://aowis.org/index.php?title=Measurement:Canonical_Units&amp;diff=780</id>
		<title>Measurement:Canonical Units</title>
		<link rel="alternate" type="text/html" href="https://aowis.org/index.php?title=Measurement:Canonical_Units&amp;diff=780"/>
		<updated>2026-09-25T00:01:14Z</updated>

		<summary type="html">&lt;p&gt;Samuel: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* Part of: [[Measurement:Main_Page]]&lt;br /&gt;
* Related to: [[Measurement:Units]]&lt;br /&gt;
&lt;br /&gt;
This page is the normative registry of canonical measurement quantities and units used by AOWIS.&lt;br /&gt;
&lt;br /&gt;
The representation and conversion rules governing these quantities are defined in [[Measurement:Units]].&lt;br /&gt;
&lt;br /&gt;
UCUM&amp;lt;ref name=&amp;quot;UCUM&amp;quot;&amp;gt;Unified Code for Units of Measure (UCUM) https://ucum.org&amp;lt;/ref&amp;gt; is used for machine-readable physical unit identifiers.&lt;br /&gt;
&lt;br /&gt;
== Identifier and Field-Naming Rules ==&lt;br /&gt;
&lt;br /&gt;
The canonical unit assigned to each measurement quantity in this registry is authoritative.&lt;br /&gt;
&lt;br /&gt;
When a unit identifier is explicitly represented, it MUST use the canonical UCUM identifier defined here.&lt;br /&gt;
&lt;br /&gt;
The AOWIS identifier suffix is an ASCII-safe naming convention used for fixed-schema field names, property names, database columns, and similar technical identifiers.&lt;br /&gt;
&lt;br /&gt;
The suffix convention is:&lt;br /&gt;
&lt;br /&gt;
* division is represented by &amp;lt;code&amp;gt;_per_&amp;lt;/code&amp;gt;;&lt;br /&gt;
* multiplication is represented by &amp;lt;code&amp;gt;_&amp;lt;/code&amp;gt;;&lt;br /&gt;
* unit symbols are normalized to lower case where required for identifier naming;&lt;br /&gt;
* quantity-specific semantic qualifiers MAY be included where a literal unit-only suffix would be ambiguous;&lt;br /&gt;
* dimensionless fields with canonical UCUM unit &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt; normally omit a unit suffix.&lt;br /&gt;
&lt;br /&gt;
For example:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
m3/h        -&amp;gt; m3_per_h&lt;br /&gt;
m/s         -&amp;gt; m_per_s&lt;br /&gt;
kW.h/m3     -&amp;gt; kw_h_per_m3&lt;br /&gt;
mm2/(100.m) -&amp;gt; mm2_per_100m&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The AOWIS identifier suffix is not itself a UCUM unit identifier.&lt;br /&gt;
&lt;br /&gt;
For generic or dynamically typed measurement values, the resolved measurement quantity determines the canonical unit through this registry.&lt;br /&gt;
&lt;br /&gt;
== Length and Distance Quantities ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Measurement Quantity Identifier !! Definition !! Canonical Unit !! UCUM Identifier !! AOWIS Identifier Suffix !! AOWIS Model / EPANET Mapping&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;length&amp;lt;/code&amp;gt; || Linear spatial extent along an object or path || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || Pipe and link length&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;elevation&amp;lt;/code&amp;gt; || Vertical height relative to an engineering or hydraulic datum || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || Junction, tank, reservoir, and terrain elevation&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;altitude&amp;lt;/code&amp;gt; || Vertical position reported by a geographic positioning source || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || Geographic altitude; not necessarily suitable as hydraulic elevation&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;distance&amp;lt;/code&amp;gt; || Spatial separation between positions || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || Derived geometric distance&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;vertical_offset&amp;lt;/code&amp;gt; || Vertical difference between referenced elevations or heads || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || Elevation, tank-bottom, and reservoir-head offsets&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;link_diameter&amp;lt;/code&amp;gt; || Internal or nominal diameter of a pipe or valve || millimetre (mm) || &amp;lt;code&amp;gt;mm&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;mm&amp;lt;/code&amp;gt; || EPANET pipe and valve diameter&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;tank_diameter&amp;lt;/code&amp;gt; || Internal diameter of a cylindrical storage tank || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || EPANET tank diameter&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;darcy_weisbach_roughness_height&amp;lt;/code&amp;gt; || Absolute pipe-wall roughness height used by the Darcy-Weisbach formulation || millimetre (mm) || &amp;lt;code&amp;gt;mm&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;mm&amp;lt;/code&amp;gt; || EPANET Darcy-Weisbach pipe roughness&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Geographic Coordinate Quantities ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Measurement Quantity Identifier !! Definition !! Canonical Unit !! UCUM Identifier !! AOWIS Identifier Suffix !! AOWIS Model / EPANET Mapping&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;latitude&amp;lt;/code&amp;gt; || Angular position north or south of the equator || degree (°) || &amp;lt;code&amp;gt;deg&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;deg&amp;lt;/code&amp;gt; || WGS 84 latitude&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;longitude&amp;lt;/code&amp;gt; || Angular position east or west of the prime meridian || degree (°) || &amp;lt;code&amp;gt;deg&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;deg&amp;lt;/code&amp;gt; || WGS 84 longitude&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;projected_easting&amp;lt;/code&amp;gt; || Eastward coordinate within a projected coordinate reference system || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || Projected-coordinate easting&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;projected_northing&amp;lt;/code&amp;gt; || Northward coordinate within a projected coordinate reference system || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || Projected-coordinate northing&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;local_x&amp;lt;/code&amp;gt; || X coordinate within an explicitly defined local engineering coordinate system || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || Local coordinates when the coordinate system is defined in metres&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;local_y&amp;lt;/code&amp;gt; || Y coordinate within an explicitly defined local engineering coordinate system || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || Local coordinates when the coordinate system is defined in metres&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Area and Volume Quantities ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Measurement Quantity Identifier !! Definition !! Canonical Unit !! UCUM Identifier !! AOWIS Identifier Suffix !! AOWIS Model / EPANET Mapping&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;area&amp;lt;/code&amp;gt; || Two-dimensional spatial extent || square metre (m²) || &amp;lt;code&amp;gt;m2&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m2&amp;lt;/code&amp;gt; || Tank cross-sectional area and other geometric areas&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;volume&amp;lt;/code&amp;gt; || Three-dimensional spatial extent or storage capacity || cubic metre (m³) || &amp;lt;code&amp;gt;m3&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m3&amp;lt;/code&amp;gt; || Tank volume&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Flow and Transport Quantities ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Measurement Quantity Identifier&lt;br /&gt;
!! Definition&lt;br /&gt;
!! Canonical Unit&lt;br /&gt;
!! UCUM Identifier&lt;br /&gt;
!! AOWIS Identifier Suffix&lt;br /&gt;
!! AOWIS Model / EPANET Mapping&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;volumetric_flow_rate&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Volume transported per unit time&lt;br /&gt;
|| cubic metre per hour (m³/h)&lt;br /&gt;
|| &amp;lt;code&amp;gt;m3/h&amp;lt;/code&amp;gt;&lt;br /&gt;
|| &amp;lt;code&amp;gt;m3_per_h&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Demand, link flow, leakage flow, emitter flow, and pump-curve flow&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;velocity&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Rate of linear movement&lt;br /&gt;
|| metre per second (m/s)&lt;br /&gt;
|| &amp;lt;code&amp;gt;m/s&amp;lt;/code&amp;gt;&lt;br /&gt;
|| &amp;lt;code&amp;gt;m_per_s&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Link flow velocity&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;molecular_diffusivity&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Molecular diffusion coefficient of a chemical species&lt;br /&gt;
|| square metre per second (m²/s)&lt;br /&gt;
|| &amp;lt;code&amp;gt;m2/s&amp;lt;/code&amp;gt;&lt;br /&gt;
|| &amp;lt;code&amp;gt;m2_per_s&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Multi-species molecular diffusion&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;longitudinal_dispersion_coefficient&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Longitudinal dispersion coefficient describing axial spreading of a transported species&lt;br /&gt;
|| square metre per second (m²/s)&lt;br /&gt;
|| &amp;lt;code&amp;gt;m2/s&amp;lt;/code&amp;gt;&lt;br /&gt;
|| &amp;lt;code&amp;gt;m2_per_s&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Multi-species longitudinal dispersion&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Hydraulic Head, Pressure, and Stress Quantities ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Measurement Quantity Identifier !! Definition !! Canonical Unit !! UCUM Identifier !! AOWIS Identifier Suffix !! AOWIS Model / EPANET Mapping&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;hydraulic_head&amp;lt;/code&amp;gt; || Total mechanical energy per unit weight of fluid expressed as an equivalent fluid-column height || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || Junction, reservoir, and tank hydraulic head&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;pressure_head&amp;lt;/code&amp;gt; || Fluid pressure expressed as an equivalent fluid-column height || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || EPANET node pressure, pressure-driven demand thresholds, and pressure-control valve settings&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;water_level&amp;lt;/code&amp;gt; || Height of a water surface relative to a defined local reference level || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || Initial, minimum, maximum, and simulated tank levels&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;head_gain&amp;lt;/code&amp;gt; || Increase in hydraulic head across an energy-adding component || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || Pump curves and pump simulation results&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;head_loss&amp;lt;/code&amp;gt; || Reduction in hydraulic head across a hydraulic component || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || Pipes, valves, and other energy-dissipating components&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;head_loss_gradient&amp;lt;/code&amp;gt; || Hydraulic head loss per unit pipe length || metre per kilometre (m/km) || &amp;lt;code&amp;gt;m/km&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m_per_km&amp;lt;/code&amp;gt; || EPANET pipe head-loss reporting&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;pressure&amp;lt;/code&amp;gt; || Normal force per unit area within a fluid system || kilopascal (kPa) || &amp;lt;code&amp;gt;kPa&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;kpa&amp;lt;/code&amp;gt; || Physical pressure measurements, sensors, SCADA data, and external exchange&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;stress&amp;lt;/code&amp;gt; || Internal force per unit area within a material || megapascal (MPa) || &amp;lt;code&amp;gt;MPa&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;mpa&amp;lt;/code&amp;gt; || Structural and material analysis&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Time Quantities ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Measurement Quantity Identifier&lt;br /&gt;
!! Definition&lt;br /&gt;
!! Canonical Unit&lt;br /&gt;
!! UCUM Identifier&lt;br /&gt;
!! AOWIS Identifier Suffix&lt;br /&gt;
!! AOWIS Model / EPANET Mapping&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;elapsed_time&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Time elapsed from a defined simulation or process origin&lt;br /&gt;
|| second (s)&lt;br /&gt;
|| &amp;lt;code&amp;gt;s&amp;lt;/code&amp;gt;&lt;br /&gt;
|| &amp;lt;code&amp;gt;s&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Simulation elapsed time and time-based control triggers&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;duration&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Length of a time interval&lt;br /&gt;
|| second (s)&lt;br /&gt;
|| &amp;lt;code&amp;gt;s&amp;lt;/code&amp;gt;&lt;br /&gt;
|| &amp;lt;code&amp;gt;s&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Simulation duration and time steps&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;time_of_day&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Time elapsed since the start of the current day&lt;br /&gt;
|| second (s)&lt;br /&gt;
|| &amp;lt;code&amp;gt;s&amp;lt;/code&amp;gt;&lt;br /&gt;
|| &amp;lt;code&amp;gt;s&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Simulation start time and clock-time controls&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The canonical unit second does not imply integral-second resolution. Sub-second durations and time steps are represented as fractional seconds. For example, a time step of one millisecond is represented canonically as &amp;lt;code&amp;gt;0.001 s&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
== Hydraulic Coefficients and Other Dimensionless Quantities ==&lt;br /&gt;
&lt;br /&gt;
The canonical UCUM unit identifier for all quantities in this section is &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;. The AOWIS unit suffix is omitted.&lt;br /&gt;
&lt;br /&gt;
Semantic terms such as &amp;lt;code&amp;gt;ratio&amp;lt;/code&amp;gt;, &amp;lt;code&amp;gt;factor&amp;lt;/code&amp;gt;, &amp;lt;code&amp;gt;coefficient&amp;lt;/code&amp;gt;, &amp;lt;code&amp;gt;multiplier&amp;lt;/code&amp;gt;, &amp;lt;code&amp;gt;number&amp;lt;/code&amp;gt;, and &amp;lt;code&amp;gt;exponent&amp;lt;/code&amp;gt; describe the quantity and are not unit suffixes.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Measurement Quantity Identifier&lt;br /&gt;
!! Definition&lt;br /&gt;
!! UCUM Identifier&lt;br /&gt;
!! AOWIS Identifier Suffix&lt;br /&gt;
!! AOWIS Model / EPANET Mapping&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;hazen_williams_roughness_coefficient&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Hazen-Williams pipe roughness coefficient&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| EPANET Hazen-Williams roughness&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;chezy_manning_roughness_coefficient&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Chezy-Manning pipe roughness coefficient&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| EPANET Chezy-Manning roughness&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;minor_loss_coefficient&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Coefficient representing local hydraulic losses&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| Pipe and valve minor loss; TCV setting&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;darcy_weisbach_friction_factor&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Darcy-Weisbach friction factor&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| Pipe simulation result&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;pump_speed_ratio&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Pump rotational speed relative to nominal or reference speed&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| Pump setting, result, pattern, control, and rule values&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;pattern_multiplier&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Factor applied by a hydraulic or energy pattern&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| EPANET pattern factor&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;demand_multiplier&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Global factor applied to base demands&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| EPANET demand multiplier&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;pressure_exponent&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Exponent used by the pressure-driven demand relation&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| EPANET pressure exponent&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;emitter_exponent&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Exponent used by the emitter pressure-flow relation&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| EPANET emitter exponent&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;reaction_order&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Order of a bulk, wall, or tank reaction equation&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| EPANET reaction order&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;specific_gravity&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Fluid density relative to a defined reference density&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| EPANET specific gravity&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;relative_viscosity&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Kinematic viscosity relative to the solver reference&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| EPANET relative viscosity&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;relative_diffusivity&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Molecular diffusivity relative to the solver reference&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| EPANET relative diffusivity&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;peclet_number&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Ratio characterizing advective transport relative to diffusive or dispersive transport&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| Multi-species dispersion; includes solver thresholds based on the Peclet number&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;mixing_fraction&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Fraction of tank volume assigned to the applicable mixing zone&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| EPANET tank mixing fraction&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;hydraulic_accuracy&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Relative hydraulic convergence criterion&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| EPANET hydraulic accuracy&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;hydraulic_damping_limit&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Relative threshold controlling solver damping or status checks&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| EPANET damping limit&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;relative_error&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Relative numerical error&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| Hydraulic and water-quality numerical error, tolerance, and simulation statistics&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;flow_balance_ratio&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Ratio of total outflow to total inflow&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| EPANET flow-balance reporting&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;quality_mass_balance_ratio&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Water-quality mass-conservation ratio&lt;br /&gt;
|| &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;&lt;br /&gt;
|| none&lt;br /&gt;
|| EPANET and multi-species quality mass-balance reporting&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Percentage Quantities ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Measurement Quantity Identifier !! Definition !! Canonical Unit !! UCUM Identifier !! AOWIS Identifier Suffix !! AOWIS Model / EPANET Mapping&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;efficiency&amp;lt;/code&amp;gt; || Ratio of useful output to total input expressed as a percentage || percent (%) || &amp;lt;code&amp;gt;%&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;percent&amp;lt;/code&amp;gt; || Pump efficiency and efficiency curves&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;relative_flow&amp;lt;/code&amp;gt; || Flow relative to a defined reference flow || percent (%) || &amp;lt;code&amp;gt;%&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;percent&amp;lt;/code&amp;gt; || Valve characteristic curves&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;valve_position&amp;lt;/code&amp;gt; || Valve opening position relative to its operating range || percent (%) || &amp;lt;code&amp;gt;%&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;percent&amp;lt;/code&amp;gt; || Position-control valves&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;source_trace_percentage&amp;lt;/code&amp;gt; || Proportion of water originating from a specified source node || percent (%) || &amp;lt;code&amp;gt;%&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;percent&amp;lt;/code&amp;gt; || EPANET source-trace analysis&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;operating_time_percentage&amp;lt;/code&amp;gt; || Fraction of a reporting period during which equipment operates || percent (%) || &amp;lt;code&amp;gt;%&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;percent&amp;lt;/code&amp;gt; || Pump energy reporting&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;demand_reduction_percentage&amp;lt;/code&amp;gt; || Reduction in delivered demand relative to requested demand || percent (%) || &amp;lt;code&amp;gt;%&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;percent&amp;lt;/code&amp;gt; || Hydraulic statistics&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;leakage_loss_percentage&amp;lt;/code&amp;gt; || Leakage loss relative to total system inflow || percent (%) || &amp;lt;code&amp;gt;%&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;percent&amp;lt;/code&amp;gt; || Leakage statistics&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Reaction and Leakage Quantities ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Measurement Quantity Identifier !! Definition !! Canonical Unit !! UCUM Identifier !! AOWIS Identifier Suffix !! AOWIS Model / EPANET Mapping&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;first_order_bulk_reaction_coefficient&amp;lt;/code&amp;gt; || First-order reaction-rate coefficient within the bulk fluid || per day (d⁻¹) || &amp;lt;code&amp;gt;/d&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;per_d&amp;lt;/code&amp;gt; || Global, pipe, and tank first-order bulk reactions&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;first_order_wall_reaction_coefficient&amp;lt;/code&amp;gt; || First-order reaction-rate coefficient at a pipe wall || metre per day (m/d) || &amp;lt;code&amp;gt;m/d&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m_per_d&amp;lt;/code&amp;gt; || Global and pipe first-order wall reactions&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;leak_area_per_100m_pipe_length&amp;lt;/code&amp;gt; || Effective leak area assigned per 100 metres of pipe length || square millimetre per 100 metres (mm²/100 m) || &amp;lt;code&amp;gt;mm2/(100.m)&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;mm2_per_100m&amp;lt;/code&amp;gt; || EPANET 2.3 FAVAD leak area; EPANET uses 100 project length units and the adapter converts when required&amp;lt;ref name=&amp;quot;EPANET23&amp;quot;&amp;gt;OWA-EPANET 2.3 release notes https://github.com/OpenWaterAnalytics/EPANET/blob/v2.3/ReleaseNotes2_3.md&amp;lt;/ref&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;leak_area_expansion_per_pressure_head&amp;lt;/code&amp;gt; || Increase in effective leak area per unit pressure head || square millimetre per metre of pressure head (mm²/m) || &amp;lt;code&amp;gt;mm2/m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;mm2_per_m_head&amp;lt;/code&amp;gt; || EPANET 2.3 FAVAD leak expansion&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Water Quality Quantities ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Measurement Quantity Identifier&lt;br /&gt;
!! Definition&lt;br /&gt;
!! Canonical Unit&lt;br /&gt;
!! UCUM Identifier&lt;br /&gt;
!! AOWIS Identifier Suffix&lt;br /&gt;
!! AOWIS Model / EPANET Mapping&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;chemical_mass_concentration&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Mass concentration of a chemical substance in water&lt;br /&gt;
|| milligram per litre (mg/L)&lt;br /&gt;
|| &amp;lt;code&amp;gt;mg/L&amp;lt;/code&amp;gt;&lt;br /&gt;
|| &amp;lt;code&amp;gt;mg_per_l&amp;lt;/code&amp;gt;&lt;br /&gt;
|| EPANET chemical quality; multi-species bulk species using a mass basis&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;chemical_amount_concentration&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Amount-of-substance concentration of a chemical substance in water&lt;br /&gt;
|| millimole per litre (mmol/L)&lt;br /&gt;
|| &amp;lt;code&amp;gt;mmol/L&amp;lt;/code&amp;gt;&lt;br /&gt;
|| &amp;lt;code&amp;gt;mmol_per_l&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Multi-species bulk species using an amount-of-substance basis&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;chemical_surface_mass_density&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Mass of a chemical species associated with a surface per unit surface area&lt;br /&gt;
|| milligram per square metre (mg/m²)&lt;br /&gt;
|| &amp;lt;code&amp;gt;mg/m2&amp;lt;/code&amp;gt;&lt;br /&gt;
|| &amp;lt;code&amp;gt;mg_per_m2&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Multi-species wall species using a mass basis&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;chemical_surface_amount_density&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Amount of a chemical species associated with a surface per unit surface area&lt;br /&gt;
|| millimole per square metre (mmol/m²)&lt;br /&gt;
|| &amp;lt;code&amp;gt;mmol/m2&amp;lt;/code&amp;gt;&lt;br /&gt;
|| &amp;lt;code&amp;gt;mmol_per_m2&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Multi-species wall species using an amount-of-substance basis&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;chemical_mass_flow_rate&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Chemical mass introduced into or transported through the system per unit time&lt;br /&gt;
|| milligram per minute (mg/min)&lt;br /&gt;
|| &amp;lt;code&amp;gt;mg/min&amp;lt;/code&amp;gt;&lt;br /&gt;
|| &amp;lt;code&amp;gt;mg_per_min&amp;lt;/code&amp;gt;&lt;br /&gt;
|| EPANET mass-booster source strength; multi-species MASS source using a mass basis&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;chemical_amount_flow_rate&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Amount of chemical substance introduced into or transported through the system per unit time&lt;br /&gt;
|| millimole per minute (mmol/min)&lt;br /&gt;
|| &amp;lt;code&amp;gt;mmol/min&amp;lt;/code&amp;gt;&lt;br /&gt;
|| &amp;lt;code&amp;gt;mmol_per_min&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Multi-species MASS source using an amount-of-substance basis&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;water_age&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Time elapsed since water entered the modelled distribution system&lt;br /&gt;
|| hour (h)&lt;br /&gt;
|| &amp;lt;code&amp;gt;h&amp;lt;/code&amp;gt;&lt;br /&gt;
|| &amp;lt;code&amp;gt;h&amp;lt;/code&amp;gt;&lt;br /&gt;
|| EPANET water-age analysis&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Power, Energy, and Electrical Quantities ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Measurement Quantity Identifier !! Definition !! Canonical Unit !! UCUM Identifier !! AOWIS Identifier Suffix !! AOWIS Model / EPANET Mapping&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;power&amp;lt;/code&amp;gt; || Rate of energy transfer || kilowatt (kW) || &amp;lt;code&amp;gt;kW&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;kw&amp;lt;/code&amp;gt; || Pump power and electrical power&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;energy&amp;lt;/code&amp;gt; || Work performed or energy transferred || kilowatt-hour (kWh) || &amp;lt;code&amp;gt;kW.h&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;kw_h&amp;lt;/code&amp;gt; || Pump energy consumption&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;energy_intensity&amp;lt;/code&amp;gt; || Energy consumed per unit volume || kilowatt-hour per cubic metre (kWh/m³) || &amp;lt;code&amp;gt;kW.h/m3&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;kw_h_per_m3&amp;lt;/code&amp;gt; || Pump energy-use reporting&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;electric_current&amp;lt;/code&amp;gt; || Rate of electric charge flow || ampere (A) || &amp;lt;code&amp;gt;A&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;a&amp;lt;/code&amp;gt; || Electrical model&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;voltage&amp;lt;/code&amp;gt; || Electric potential difference || volt (V) || &amp;lt;code&amp;gt;V&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;v&amp;lt;/code&amp;gt; || Electrical model&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;electrical_resistance&amp;lt;/code&amp;gt; || Opposition to electric current flow || ohm (Ω) || &amp;lt;code&amp;gt;Ohm&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;ohm&amp;lt;/code&amp;gt; || Electrical model&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;capacitance&amp;lt;/code&amp;gt; || Ability to store electric charge || farad (F) || &amp;lt;code&amp;gt;F&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;f&amp;lt;/code&amp;gt; || Electrical model&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Context-Dependent Quantity Resolution ==&lt;br /&gt;
&lt;br /&gt;
Some Model concepts resolve to different registered measurement quantities depending on their context. The representation requirements for such values are defined in [[Measurement:Units]] and, where applicable, the corresponding Measurement subsystem specification.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Model Concept&lt;br /&gt;
!! Resolved Measurement Quantity&lt;br /&gt;
|-&lt;br /&gt;
| Valve setting&lt;br /&gt;
|| PRV, PSV, and PBV: &amp;lt;code&amp;gt;pressure_head&amp;lt;/code&amp;gt;; FCV: &amp;lt;code&amp;gt;volumetric_flow_rate&amp;lt;/code&amp;gt;; TCV: &amp;lt;code&amp;gt;minor_loss_coefficient&amp;lt;/code&amp;gt;; PCV: &amp;lt;code&amp;gt;valve_position&amp;lt;/code&amp;gt;; GPV: curve reference rather than a measurement value&lt;br /&gt;
|-&lt;br /&gt;
| Pump setting&lt;br /&gt;
|| &amp;lt;code&amp;gt;pump_speed_ratio&amp;lt;/code&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Control trigger&lt;br /&gt;
|| &amp;lt;code&amp;gt;water_level&amp;lt;/code&amp;gt;, &amp;lt;code&amp;gt;pressure_head&amp;lt;/code&amp;gt;, &amp;lt;code&amp;gt;elapsed_time&amp;lt;/code&amp;gt;, or &amp;lt;code&amp;gt;time_of_day&amp;lt;/code&amp;gt;, depending on control type&lt;br /&gt;
|-&lt;br /&gt;
| Control or rule action setting&lt;br /&gt;
|| The measurement quantity supported by the target link type&lt;br /&gt;
|-&lt;br /&gt;
| Rule premise value&lt;br /&gt;
|| The measurement quantity selected by the rule variable&lt;br /&gt;
|-&lt;br /&gt;
| Initial or simulated standard water quality&lt;br /&gt;
|| &amp;lt;code&amp;gt;chemical_mass_concentration&amp;lt;/code&amp;gt;, &amp;lt;code&amp;gt;water_age&amp;lt;/code&amp;gt;, or &amp;lt;code&amp;gt;source_trace_percentage&amp;lt;/code&amp;gt;, depending on quality-analysis mode&lt;br /&gt;
|-&lt;br /&gt;
| Standard quality-source strength&lt;br /&gt;
|| &amp;lt;code&amp;gt;chemical_mass_concentration&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;chemical_mass_flow_rate&amp;lt;/code&amp;gt;, depending on source type&lt;br /&gt;
|-&lt;br /&gt;
| Multi-species bulk quality value&lt;br /&gt;
|| Mass-basis species: &amp;lt;code&amp;gt;chemical_mass_concentration&amp;lt;/code&amp;gt;; amount-of-substance-basis species: &amp;lt;code&amp;gt;chemical_amount_concentration&amp;lt;/code&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Multi-species wall quality value&lt;br /&gt;
|| Mass-basis species: &amp;lt;code&amp;gt;chemical_surface_mass_density&amp;lt;/code&amp;gt;; amount-of-substance-basis species: &amp;lt;code&amp;gt;chemical_surface_amount_density&amp;lt;/code&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Multi-species initial quality&lt;br /&gt;
|| The same quantity as the corresponding species value: bulk species resolve to &amp;lt;code&amp;gt;chemical_mass_concentration&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;chemical_amount_concentration&amp;lt;/code&amp;gt;; wall species resolve to &amp;lt;code&amp;gt;chemical_surface_mass_density&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;chemical_surface_amount_density&amp;lt;/code&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Multi-species absolute error tolerance&lt;br /&gt;
|| The same measurement quantity as the corresponding species value&lt;br /&gt;
|-&lt;br /&gt;
| Multi-species relative error tolerance&lt;br /&gt;
|| &amp;lt;code&amp;gt;relative_error&amp;lt;/code&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Multi-species source strength&lt;br /&gt;
|| CONCEN, SETPOINT, and FLOWPACED sources resolve to &amp;lt;code&amp;gt;chemical_mass_concentration&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;chemical_amount_concentration&amp;lt;/code&amp;gt; according to the species basis; MASS sources resolve to &amp;lt;code&amp;gt;chemical_mass_flow_rate&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;chemical_amount_flow_rate&amp;lt;/code&amp;gt;. Wall species are not valid node-source species.&lt;br /&gt;
|-&lt;br /&gt;
| Reaction coefficient&lt;br /&gt;
|| The applicable reaction-coefficient quantity determined by reaction order&lt;br /&gt;
|-&lt;br /&gt;
| Molecular diffusion coefficient&lt;br /&gt;
|| &amp;lt;code&amp;gt;molecular_diffusivity&amp;lt;/code&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Fixed longitudinal dispersion coefficient&lt;br /&gt;
|| &amp;lt;code&amp;gt;longitudinal_dispersion_coefficient&amp;lt;/code&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Peclet-number dispersion threshold&lt;br /&gt;
|| &amp;lt;code&amp;gt;peclet_number&amp;lt;/code&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Symbolic reaction expression&lt;br /&gt;
|| Measurement values remain canonical in the AOWIS domain model. Where numerical interpretation of the expression depends on a concentration, surface-area, time, or other unit convention, that convention is retained as explicit expression-unit-context metadata and applied only at the expression-evaluation boundary.&lt;br /&gt;
|-&lt;br /&gt;
| Emitter coefficient&lt;br /&gt;
|| Equation-dependent coefficient in &amp;lt;code&amp;gt;Q = C H^n&amp;lt;/code&amp;gt;; no single fixed canonical unit applies independently of &amp;lt;code&amp;gt;n&amp;lt;/code&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Generic curve coordinate&lt;br /&gt;
|| The measurement quantity defined by the curve type&lt;br /&gt;
|-&lt;br /&gt;
| Report threshold&lt;br /&gt;
|| The measurement quantity of the corresponding report field&lt;br /&gt;
|-&lt;br /&gt;
| EPANET map or backdrop coordinate&lt;br /&gt;
|| The applicable geographic, projected, or local coordinate quantity after the coordinate representation is resolved&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;/div&gt;</summary>
		<author><name>Samuel</name></author>
	</entry>
	<entry>
		<id>https://aowis.org/index.php?title=Measurement:Canonical_Units&amp;diff=779</id>
		<title>Measurement:Canonical Units</title>
		<link rel="alternate" type="text/html" href="https://aowis.org/index.php?title=Measurement:Canonical_Units&amp;diff=779"/>
		<updated>2026-09-24T23:58:02Z</updated>

		<summary type="html">&lt;p&gt;Samuel: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* Part of: [[Measurement:Main_Page]]&lt;br /&gt;
* Related to: [[Measurement:Units]]&lt;br /&gt;
&lt;br /&gt;
This page is the normative registry of canonical measurement quantities and units used by AOWIS.&lt;br /&gt;
&lt;br /&gt;
The representation and conversion rules governing these quantities are defined in [[Measurement:Units]].&lt;br /&gt;
&lt;br /&gt;
UCUM&amp;lt;ref name=&amp;quot;UCUM&amp;quot;&amp;gt;Unified Code for Units of Measure (UCUM) https://ucum.org&amp;lt;/ref&amp;gt; is used for machine-readable physical unit identifiers.&lt;br /&gt;
&lt;br /&gt;
== Identifier and Field-Naming Rules ==&lt;br /&gt;
&lt;br /&gt;
The canonical unit assigned to each measurement quantity in this registry is authoritative.&lt;br /&gt;
&lt;br /&gt;
When a unit identifier is explicitly represented, it MUST use the canonical UCUM identifier defined here.&lt;br /&gt;
&lt;br /&gt;
The AOWIS identifier suffix is an ASCII-safe naming convention used for fixed-schema field names, property names, database columns, and similar technical identifiers.&lt;br /&gt;
&lt;br /&gt;
The suffix convention is:&lt;br /&gt;
&lt;br /&gt;
* division is represented by &amp;lt;code&amp;gt;_per_&amp;lt;/code&amp;gt;;&lt;br /&gt;
* multiplication is represented by &amp;lt;code&amp;gt;_&amp;lt;/code&amp;gt;;&lt;br /&gt;
* unit symbols are normalized to lower case where required for identifier naming;&lt;br /&gt;
* quantity-specific semantic qualifiers MAY be included where a literal unit-only suffix would be ambiguous;&lt;br /&gt;
* dimensionless fields with canonical UCUM unit &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt; normally omit a unit suffix.&lt;br /&gt;
&lt;br /&gt;
For example:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
m3/h        -&amp;gt; m3_per_h&lt;br /&gt;
m/s         -&amp;gt; m_per_s&lt;br /&gt;
kW.h/m3     -&amp;gt; kw_h_per_m3&lt;br /&gt;
mm2/(100.m) -&amp;gt; mm2_per_100m&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The AOWIS identifier suffix is not itself a UCUM unit identifier.&lt;br /&gt;
&lt;br /&gt;
For generic or dynamically typed measurement values, the resolved measurement quantity determines the canonical unit through this registry.&lt;br /&gt;
&lt;br /&gt;
== Length and Distance Quantities ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Measurement Quantity Identifier !! Definition !! Canonical Unit !! UCUM Identifier !! AOWIS Identifier Suffix !! AOWIS Model / EPANET Mapping&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;length&amp;lt;/code&amp;gt; || Linear spatial extent along an object or path || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || Pipe and link length&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;elevation&amp;lt;/code&amp;gt; || Vertical height relative to an engineering or hydraulic datum || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || Junction, tank, reservoir, and terrain elevation&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;altitude&amp;lt;/code&amp;gt; || Vertical position reported by a geographic positioning source || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || Geographic altitude; not necessarily suitable as hydraulic elevation&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;distance&amp;lt;/code&amp;gt; || Spatial separation between positions || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || Derived geometric distance&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;vertical_offset&amp;lt;/code&amp;gt; || Vertical difference between referenced elevations or heads || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || Elevation, tank-bottom, and reservoir-head offsets&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;link_diameter&amp;lt;/code&amp;gt; || Internal or nominal diameter of a pipe or valve || millimetre (mm) || &amp;lt;code&amp;gt;mm&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;mm&amp;lt;/code&amp;gt; || EPANET pipe and valve diameter&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;tank_diameter&amp;lt;/code&amp;gt; || Internal diameter of a cylindrical storage tank || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || EPANET tank diameter&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;darcy_weisbach_roughness_height&amp;lt;/code&amp;gt; || Absolute pipe-wall roughness height used by the Darcy-Weisbach formulation || millimetre (mm) || &amp;lt;code&amp;gt;mm&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;mm&amp;lt;/code&amp;gt; || EPANET Darcy-Weisbach pipe roughness&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Geographic Coordinate Quantities ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Measurement Quantity Identifier !! Definition !! Canonical Unit !! UCUM Identifier !! AOWIS Identifier Suffix !! AOWIS Model / EPANET Mapping&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;latitude&amp;lt;/code&amp;gt; || Angular position north or south of the equator || degree (°) || &amp;lt;code&amp;gt;deg&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;deg&amp;lt;/code&amp;gt; || WGS 84 latitude&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;longitude&amp;lt;/code&amp;gt; || Angular position east or west of the prime meridian || degree (°) || &amp;lt;code&amp;gt;deg&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;deg&amp;lt;/code&amp;gt; || WGS 84 longitude&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;projected_easting&amp;lt;/code&amp;gt; || Eastward coordinate within a projected coordinate reference system || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || Projected-coordinate easting&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;projected_northing&amp;lt;/code&amp;gt; || Northward coordinate within a projected coordinate reference system || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || Projected-coordinate northing&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;local_x&amp;lt;/code&amp;gt; || X coordinate within an explicitly defined local engineering coordinate system || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || Local coordinates when the coordinate system is defined in metres&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;local_y&amp;lt;/code&amp;gt; || Y coordinate within an explicitly defined local engineering coordinate system || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || Local coordinates when the coordinate system is defined in metres&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Area and Volume Quantities ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Measurement Quantity Identifier !! Definition !! Canonical Unit !! UCUM Identifier !! AOWIS Identifier Suffix !! AOWIS Model / EPANET Mapping&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;area&amp;lt;/code&amp;gt; || Two-dimensional spatial extent || square metre (m²) || &amp;lt;code&amp;gt;m2&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m2&amp;lt;/code&amp;gt; || Tank cross-sectional area and other geometric areas&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;volume&amp;lt;/code&amp;gt; || Three-dimensional spatial extent or storage capacity || cubic metre (m³) || &amp;lt;code&amp;gt;m3&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m3&amp;lt;/code&amp;gt; || Tank volume&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Flow and Transport Quantities ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Measurement Quantity Identifier&lt;br /&gt;
!! Definition&lt;br /&gt;
!! Canonical Unit&lt;br /&gt;
!! UCUM Identifier&lt;br /&gt;
!! AOWIS Identifier Suffix&lt;br /&gt;
!! AOWIS Model / EPANET Mapping&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;volumetric_flow_rate&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Volume transported per unit time&lt;br /&gt;
|| cubic metre per hour (m³/h)&lt;br /&gt;
|| &amp;lt;code&amp;gt;m3/h&amp;lt;/code&amp;gt;&lt;br /&gt;
|| &amp;lt;code&amp;gt;m3_per_h&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Demand, link flow, leakage flow, emitter flow, and pump-curve flow&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;velocity&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Rate of linear movement&lt;br /&gt;
|| metre per second (m/s)&lt;br /&gt;
|| &amp;lt;code&amp;gt;m/s&amp;lt;/code&amp;gt;&lt;br /&gt;
|| &amp;lt;code&amp;gt;m_per_s&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Link flow velocity&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;molecular_diffusivity&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Molecular diffusion coefficient of a chemical species&lt;br /&gt;
|| square metre per second (m²/s)&lt;br /&gt;
|| &amp;lt;code&amp;gt;m2/s&amp;lt;/code&amp;gt;&lt;br /&gt;
|| &amp;lt;code&amp;gt;m2_per_s&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Multi-species molecular diffusion&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;longitudinal_dispersion_coefficient&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Longitudinal dispersion coefficient describing axial spreading of a transported species&lt;br /&gt;
|| square metre per second (m²/s)&lt;br /&gt;
|| &amp;lt;code&amp;gt;m2/s&amp;lt;/code&amp;gt;&lt;br /&gt;
|| &amp;lt;code&amp;gt;m2_per_s&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Multi-species longitudinal dispersion&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Hydraulic Head, Pressure, and Stress Quantities ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Measurement Quantity Identifier !! Definition !! Canonical Unit !! UCUM Identifier !! AOWIS Identifier Suffix !! AOWIS Model / EPANET Mapping&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;hydraulic_head&amp;lt;/code&amp;gt; || Total mechanical energy per unit weight of fluid expressed as an equivalent fluid-column height || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || Junction, reservoir, and tank hydraulic head&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;pressure_head&amp;lt;/code&amp;gt; || Fluid pressure expressed as an equivalent fluid-column height || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || EPANET node pressure, pressure-driven demand thresholds, and pressure-control valve settings&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;water_level&amp;lt;/code&amp;gt; || Height of a water surface relative to a defined local reference level || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || Initial, minimum, maximum, and simulated tank levels&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;head_gain&amp;lt;/code&amp;gt; || Increase in hydraulic head across an energy-adding component || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || Pump curves and pump simulation results&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;head_loss&amp;lt;/code&amp;gt; || Reduction in hydraulic head across a hydraulic component || metre (m) || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m&amp;lt;/code&amp;gt; || Pipes, valves, and other energy-dissipating components&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;head_loss_gradient&amp;lt;/code&amp;gt; || Hydraulic head loss per unit pipe length || metre per kilometre (m/km) || &amp;lt;code&amp;gt;m/km&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m_per_km&amp;lt;/code&amp;gt; || EPANET pipe head-loss reporting&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;pressure&amp;lt;/code&amp;gt; || Normal force per unit area within a fluid system || kilopascal (kPa) || &amp;lt;code&amp;gt;kPa&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;kpa&amp;lt;/code&amp;gt; || Physical pressure measurements, sensors, SCADA data, and external exchange&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;stress&amp;lt;/code&amp;gt; || Internal force per unit area within a material || megapascal (MPa) || &amp;lt;code&amp;gt;MPa&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;mpa&amp;lt;/code&amp;gt; || Structural and material analysis&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Time Quantities ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Measurement Quantity Identifier&lt;br /&gt;
!! Definition&lt;br /&gt;
!! Canonical Unit&lt;br /&gt;
!! UCUM Identifier&lt;br /&gt;
!! AOWIS Identifier Suffix&lt;br /&gt;
!! AOWIS Model / EPANET Mapping&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;elapsed_time&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Time elapsed from a defined simulation or process origin&lt;br /&gt;
|| second (s)&lt;br /&gt;
|| &amp;lt;code&amp;gt;s&amp;lt;/code&amp;gt;&lt;br /&gt;
|| &amp;lt;code&amp;gt;s&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Simulation elapsed time and time-based control triggers&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;duration&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Length of a time interval&lt;br /&gt;
|| second (s)&lt;br /&gt;
|| &amp;lt;code&amp;gt;s&amp;lt;/code&amp;gt;&lt;br /&gt;
|| &amp;lt;code&amp;gt;s&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Simulation duration and time steps&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;time_of_day&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Time elapsed since the start of the current day&lt;br /&gt;
|| second (s)&lt;br /&gt;
|| &amp;lt;code&amp;gt;s&amp;lt;/code&amp;gt;&lt;br /&gt;
|| &amp;lt;code&amp;gt;s&amp;lt;/code&amp;gt;&lt;br /&gt;
|| Simulation start time and clock-time controls&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The canonical unit second does not imply integral-second resolution. Sub-second durations and time steps are represented as fractional seconds. For example, a time step of one millisecond is represented canonically as &amp;lt;code&amp;gt;0.001 s&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
== Hydraulic Coefficients and Other Dimensionless Quantities ==&lt;br /&gt;
&lt;br /&gt;
The canonical UCUM unit identifier for all quantities in this section is &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;. The AOWIS unit suffix is omitted.&lt;br /&gt;
&lt;br /&gt;
Semantic terms such as &amp;lt;code&amp;gt;ratio&amp;lt;/code&amp;gt;, &amp;lt;code&amp;gt;factor&amp;lt;/code&amp;gt;, &amp;lt;code&amp;gt;coefficient&amp;lt;/code&amp;gt;, &amp;lt;code&amp;gt;multiplier&amp;lt;/code&amp;gt;, and &amp;lt;code&amp;gt;exponent&amp;lt;/code&amp;gt; describe the quantity and are not unit suffixes.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Measurement Quantity Identifier !! Definition !! UCUM Identifier !! AOWIS Identifier Suffix !! AOWIS Model / EPANET Mapping&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;hazen_williams_roughness_coefficient&amp;lt;/code&amp;gt; || Hazen-Williams pipe roughness coefficient || &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt; || none || EPANET Hazen-Williams roughness&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;chezy_manning_roughness_coefficient&amp;lt;/code&amp;gt; || Chezy-Manning pipe roughness coefficient || &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt; || none || EPANET Chezy-Manning roughness&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;minor_loss_coefficient&amp;lt;/code&amp;gt; || Coefficient representing local hydraulic losses || &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt; || none || Pipe and valve minor loss; TCV setting&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;darcy_weisbach_friction_factor&amp;lt;/code&amp;gt; || Darcy-Weisbach friction factor || &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt; || none || Pipe simulation result&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;pump_speed_ratio&amp;lt;/code&amp;gt; || Pump rotational speed relative to nominal or reference speed || &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt; || none || Pump setting, result, pattern, control, and rule values&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;pattern_multiplier&amp;lt;/code&amp;gt; || Factor applied by a hydraulic or energy pattern || &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt; || none || EPANET pattern factor&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;demand_multiplier&amp;lt;/code&amp;gt; || Global factor applied to base demands || &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt; || none || EPANET demand multiplier&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;pressure_exponent&amp;lt;/code&amp;gt; || Exponent used by the pressure-driven demand relation || &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt; || none || EPANET pressure exponent&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;emitter_exponent&amp;lt;/code&amp;gt; || Exponent used by the emitter pressure-flow relation || &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt; || none || EPANET emitter exponent&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;reaction_order&amp;lt;/code&amp;gt; || Order of a bulk, wall, or tank reaction equation || &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt; || none || EPANET reaction order&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;specific_gravity&amp;lt;/code&amp;gt; || Fluid density relative to a defined reference density || &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt; || none || EPANET specific gravity&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;relative_viscosity&amp;lt;/code&amp;gt; || Kinematic viscosity relative to the solver reference || &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt; || none || EPANET relative viscosity&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;relative_diffusivity&amp;lt;/code&amp;gt; || Molecular diffusivity relative to the solver reference || &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt; || none || EPANET relative diffusivity&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;mixing_fraction&amp;lt;/code&amp;gt; || Fraction of tank volume assigned to the applicable mixing zone || &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt; || none || EPANET tank mixing fraction&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;hydraulic_accuracy&amp;lt;/code&amp;gt; || Relative hydraulic convergence criterion || &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt; || none || EPANET hydraulic accuracy&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;hydraulic_damping_limit&amp;lt;/code&amp;gt; || Relative threshold controlling solver damping or status checks || &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt; || none || EPANET damping limit&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;relative_error&amp;lt;/code&amp;gt; || Relative numerical error || &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt; || none || Hydraulic simulation statistics&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;flow_balance_ratio&amp;lt;/code&amp;gt; || Ratio of total outflow to total inflow || &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt; || none || EPANET flow-balance reporting&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;quality_mass_balance_ratio&amp;lt;/code&amp;gt; || Water-quality mass-conservation ratio || &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt; || none || EPANET quality mass-balance reporting&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Percentage Quantities ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Measurement Quantity Identifier !! Definition !! Canonical Unit !! UCUM Identifier !! AOWIS Identifier Suffix !! AOWIS Model / EPANET Mapping&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;efficiency&amp;lt;/code&amp;gt; || Ratio of useful output to total input expressed as a percentage || percent (%) || &amp;lt;code&amp;gt;%&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;percent&amp;lt;/code&amp;gt; || Pump efficiency and efficiency curves&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;relative_flow&amp;lt;/code&amp;gt; || Flow relative to a defined reference flow || percent (%) || &amp;lt;code&amp;gt;%&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;percent&amp;lt;/code&amp;gt; || Valve characteristic curves&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;valve_position&amp;lt;/code&amp;gt; || Valve opening position relative to its operating range || percent (%) || &amp;lt;code&amp;gt;%&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;percent&amp;lt;/code&amp;gt; || Position-control valves&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;source_trace_percentage&amp;lt;/code&amp;gt; || Proportion of water originating from a specified source node || percent (%) || &amp;lt;code&amp;gt;%&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;percent&amp;lt;/code&amp;gt; || EPANET source-trace analysis&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;operating_time_percentage&amp;lt;/code&amp;gt; || Fraction of a reporting period during which equipment operates || percent (%) || &amp;lt;code&amp;gt;%&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;percent&amp;lt;/code&amp;gt; || Pump energy reporting&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;demand_reduction_percentage&amp;lt;/code&amp;gt; || Reduction in delivered demand relative to requested demand || percent (%) || &amp;lt;code&amp;gt;%&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;percent&amp;lt;/code&amp;gt; || Hydraulic statistics&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;leakage_loss_percentage&amp;lt;/code&amp;gt; || Leakage loss relative to total system inflow || percent (%) || &amp;lt;code&amp;gt;%&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;percent&amp;lt;/code&amp;gt; || Leakage statistics&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Reaction and Leakage Quantities ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Measurement Quantity Identifier !! Definition !! Canonical Unit !! UCUM Identifier !! AOWIS Identifier Suffix !! AOWIS Model / EPANET Mapping&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;first_order_bulk_reaction_coefficient&amp;lt;/code&amp;gt; || First-order reaction-rate coefficient within the bulk fluid || per day (d⁻¹) || &amp;lt;code&amp;gt;/d&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;per_d&amp;lt;/code&amp;gt; || Global, pipe, and tank first-order bulk reactions&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;first_order_wall_reaction_coefficient&amp;lt;/code&amp;gt; || First-order reaction-rate coefficient at a pipe wall || metre per day (m/d) || &amp;lt;code&amp;gt;m/d&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;m_per_d&amp;lt;/code&amp;gt; || Global and pipe first-order wall reactions&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;leak_area_per_100m_pipe_length&amp;lt;/code&amp;gt; || Effective leak area assigned per 100 metres of pipe length || square millimetre per 100 metres (mm²/100 m) || &amp;lt;code&amp;gt;mm2/(100.m)&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;mm2_per_100m&amp;lt;/code&amp;gt; || EPANET 2.3 FAVAD leak area; EPANET uses 100 project length units and the adapter converts when required&amp;lt;ref name=&amp;quot;EPANET23&amp;quot;&amp;gt;OWA-EPANET 2.3 release notes https://github.com/OpenWaterAnalytics/EPANET/blob/v2.3/ReleaseNotes2_3.md&amp;lt;/ref&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;leak_area_expansion_per_pressure_head&amp;lt;/code&amp;gt; || Increase in effective leak area per unit pressure head || square millimetre per metre of pressure head (mm²/m) || &amp;lt;code&amp;gt;mm2/m&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;mm2_per_m_head&amp;lt;/code&amp;gt; || EPANET 2.3 FAVAD leak expansion&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Water Quality Quantities ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Measurement Quantity Identifier !! Definition !! Canonical Unit !! UCUM Identifier !! AOWIS Identifier Suffix !! AOWIS Model / EPANET Mapping&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;chemical_concentration&amp;lt;/code&amp;gt; || Mass concentration of a chemical substance in water || milligram per litre (mg/L) || &amp;lt;code&amp;gt;mg/L&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;mg_per_l&amp;lt;/code&amp;gt; || Chemical quality input and results&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;chemical_mass_flow_rate&amp;lt;/code&amp;gt; || Chemical mass introduced into or transported through the system per unit time || milligram per minute (mg/min) || &amp;lt;code&amp;gt;mg/min&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;mg_per_min&amp;lt;/code&amp;gt; || EPANET mass-booster source strength and source mass rate&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;water_age&amp;lt;/code&amp;gt; || Time elapsed since water entered the modelled distribution system || hour (h) || &amp;lt;code&amp;gt;h&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;h&amp;lt;/code&amp;gt; || EPANET water-age analysis&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Power, Energy, and Electrical Quantities ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Measurement Quantity Identifier !! Definition !! Canonical Unit !! UCUM Identifier !! AOWIS Identifier Suffix !! AOWIS Model / EPANET Mapping&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;power&amp;lt;/code&amp;gt; || Rate of energy transfer || kilowatt (kW) || &amp;lt;code&amp;gt;kW&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;kw&amp;lt;/code&amp;gt; || Pump power and electrical power&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;energy&amp;lt;/code&amp;gt; || Work performed or energy transferred || kilowatt-hour (kWh) || &amp;lt;code&amp;gt;kW.h&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;kw_h&amp;lt;/code&amp;gt; || Pump energy consumption&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;energy_intensity&amp;lt;/code&amp;gt; || Energy consumed per unit volume || kilowatt-hour per cubic metre (kWh/m³) || &amp;lt;code&amp;gt;kW.h/m3&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;kw_h_per_m3&amp;lt;/code&amp;gt; || Pump energy-use reporting&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;electric_current&amp;lt;/code&amp;gt; || Rate of electric charge flow || ampere (A) || &amp;lt;code&amp;gt;A&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;a&amp;lt;/code&amp;gt; || Electrical model&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;voltage&amp;lt;/code&amp;gt; || Electric potential difference || volt (V) || &amp;lt;code&amp;gt;V&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;v&amp;lt;/code&amp;gt; || Electrical model&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;electrical_resistance&amp;lt;/code&amp;gt; || Opposition to electric current flow || ohm (Ω) || &amp;lt;code&amp;gt;Ohm&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;ohm&amp;lt;/code&amp;gt; || Electrical model&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;capacitance&amp;lt;/code&amp;gt; || Ability to store electric charge || farad (F) || &amp;lt;code&amp;gt;F&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;f&amp;lt;/code&amp;gt; || Electrical model&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Context-Dependent Quantity Resolution ==&lt;br /&gt;
&lt;br /&gt;
Some Model concepts resolve to different registered measurement quantities depending on their context. The representation requirements for such values are defined in [[Measurement:Units]] and, where applicable, the corresponding Measurement subsystem specification.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Model Concept !! Resolved Measurement Quantity&lt;br /&gt;
|-&lt;br /&gt;
| Valve setting || PRV, PSV, and PBV: &amp;lt;code&amp;gt;pressure_head&amp;lt;/code&amp;gt;; FCV: &amp;lt;code&amp;gt;volumetric_flow_rate&amp;lt;/code&amp;gt;; TCV: &amp;lt;code&amp;gt;minor_loss_coefficient&amp;lt;/code&amp;gt;; PCV: &amp;lt;code&amp;gt;valve_position&amp;lt;/code&amp;gt;; GPV: curve reference rather than a measurement value&lt;br /&gt;
|-&lt;br /&gt;
| Pump setting || &amp;lt;code&amp;gt;pump_speed_ratio&amp;lt;/code&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Control trigger || &amp;lt;code&amp;gt;water_level&amp;lt;/code&amp;gt;, &amp;lt;code&amp;gt;pressure_head&amp;lt;/code&amp;gt;, &amp;lt;code&amp;gt;elapsed_time&amp;lt;/code&amp;gt;, or &amp;lt;code&amp;gt;time_of_day&amp;lt;/code&amp;gt;, depending on control type&lt;br /&gt;
|-&lt;br /&gt;
| Control or rule action setting || The measurement quantity supported by the target link type&lt;br /&gt;
|-&lt;br /&gt;
| Rule premise value || The measurement quantity selected by the rule variable&lt;br /&gt;
|-&lt;br /&gt;
| Initial or simulated quality || &amp;lt;code&amp;gt;chemical_concentration&amp;lt;/code&amp;gt;, &amp;lt;code&amp;gt;water_age&amp;lt;/code&amp;gt;, or &amp;lt;code&amp;gt;source_trace_percentage&amp;lt;/code&amp;gt;, depending on quality-analysis mode&lt;br /&gt;
|-&lt;br /&gt;
| Quality-source strength || &amp;lt;code&amp;gt;chemical_concentration&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;chemical_mass_flow_rate&amp;lt;/code&amp;gt;, depending on source type&lt;br /&gt;
|-&lt;br /&gt;
| Reaction coefficient || The applicable reaction-coefficient quantity determined by reaction order&lt;br /&gt;
|-&lt;br /&gt;
| Emitter coefficient || Equation-dependent coefficient in &amp;lt;code&amp;gt;Q = C H^n&amp;lt;/code&amp;gt;; no single fixed canonical unit applies independently of &amp;lt;code&amp;gt;n&amp;lt;/code&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Generic curve coordinate || The measurement quantity defined by the curve type&lt;br /&gt;
|-&lt;br /&gt;
| Report threshold || The measurement quantity of the corresponding report field&lt;br /&gt;
|-&lt;br /&gt;
| EPANET map or backdrop coordinate || The applicable geographic, projected, or local coordinate quantity after the coordinate representation is resolved&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;/div&gt;</summary>
		<author><name>Samuel</name></author>
	</entry>
	<entry>
		<id>https://aowis.org/index.php?title=Main_Page&amp;diff=778</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://aowis.org/index.php?title=Main_Page&amp;diff=778"/>
		<updated>2026-09-24T21:01:42Z</updated>

		<summary type="html">&lt;p&gt;Samuel: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
&lt;br /&gt;
{{MainPageBanner}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Motivation&lt;br /&gt;
 | color = teal&lt;br /&gt;
 | body = &lt;br /&gt;
&lt;br /&gt;
[[File:Countryside.jpg|class=fullwidth|center]]&lt;br /&gt;
&lt;br /&gt;
In many rural and underserved regions, including parts of Africa, wells and pumps may exist while developing and operating a reliable distribution network remains difficult. Local initiatives can lack engineering capacity, trained personnel, suitable technology, and affordable tools for operating such infrastructure sustainably.&lt;br /&gt;
&lt;br /&gt;
This practical problem is an important motivation for AOWIS. AOWIS aims to make the engineering knowledge, technical foundations, software, and operational methods needed to develop and operate water infrastructure openly available and practically usable, while supporting local training and cooperation with experienced organizations and operators.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Why AOWIS is Needed&lt;br /&gt;
 | color = turquoise&lt;br /&gt;
 | body = &lt;br /&gt;
&lt;br /&gt;
[[File:Cooperation.jpg|400px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
Water and irrigation infrastructure must often be planned, built, expanded, and operated over many decades. In some places, existing infrastructure has become fragmented across different vendors, technologies, tools, and engineering approaches. In others, communities and organizations are building coherent water infrastructure for the first time and may have limited access to engineering capacity, technical guidance, suitable software, or established operational practices.&lt;br /&gt;
&lt;br /&gt;
AOWIS provides a shared open foundation for both situations. It brings together technical standards, engineering knowledge, software, reference implementations, operational guidance, and training to support the development of water infrastructure from initial planning and design through construction, operation, maintenance, and future expansion.&lt;br /&gt;
&lt;br /&gt;
The aim is to make infrastructure understandable, interoperable, maintainable, and extensible throughout its lifecycle, while reducing dependence on individual vendors, products, suppliers, or scarce specialist expertise.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Operating Conditions&lt;br /&gt;
 | color = lightblue&lt;br /&gt;
 | body =&lt;br /&gt;
&lt;br /&gt;
[[File:Village.jpg|250px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS is designed for environments where water infrastructure must remain useful and safe despite difficult technical and operational conditions. This is particularly important in rural and underserved regions, where reliable power, continuous connectivity, modern equipment, trained personnel, and specialist support cannot always be assumed.&lt;br /&gt;
&lt;br /&gt;
Typical conditions include:&lt;br /&gt;
&lt;br /&gt;
* unreliable or limited power supply&lt;br /&gt;
* intermittent or unavailable connectivity&lt;br /&gt;
* heterogeneous or aging equipment&lt;br /&gt;
* limited availability of trained technical personnel&lt;br /&gt;
* limited access to specialist engineering support&lt;br /&gt;
* the need for safe local operation without continuous remote supervision&lt;br /&gt;
&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Design Principles&lt;br /&gt;
 | color = lightblue&lt;br /&gt;
 | body =&lt;br /&gt;
&lt;br /&gt;
AOWIS addresses these conditions through principles including:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;offline-first operation&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;safe fallback behaviour&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;human-in-the-loop control&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;local autonomous operation&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;modular and extensible system design&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;shared infrastructure models&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;open interfaces and accessible technical documentation&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The goal is to make essential water infrastructure &#039;&#039;&#039;robust, understandable, maintainable, and locally operable&#039;&#039;&#039;, including where conventional assumptions about connectivity, technical resources, and institutional support do not hold.&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
| title = Software &amp;amp; Downloads&lt;br /&gt;
| color = green&lt;br /&gt;
| body =&lt;br /&gt;
[[File:GUI ky4 3d.png|400px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS includes an open-source software platform for &#039;&#039;&#039;modelling, simulating, visualizing, monitoring, and operating water infrastructure&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The current software includes a network editor and monitoring interface, hydraulic and water-quality simulation using [[External:EPANET:Main Page|EPANET]], geographic maps and terrain visualization, and support for local and standalone operation. Development of the AOWIS Controller is progressing toward a complete open-source SCADA and operational management platform..&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://download.aowis.org Download the AOWIS Controller (development snapshot)]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* [https://github.com/aowis-org Source code on GitHub]&lt;br /&gt;
* [[#Roadmap|Software development roadmap]]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Start Here&lt;br /&gt;
 | color = yellow&lt;br /&gt;
 | body =&lt;br /&gt;
If you are new to AOWIS, begin with:&lt;br /&gt;
&lt;br /&gt;
* [[Concepts:Design_Philosophy|Design Philosophy]]  &lt;br /&gt;
* [[Standard:Definitions|Definitions]]  &lt;br /&gt;
* [[Standard:Normative_Requirements|Normative Requirements]]  &lt;br /&gt;
* [[Modules:Module_Template|Module Template]]  &lt;br /&gt;
* [[AOWIS:Contributor_Guide_External|Contributor Guide - External]]&lt;br /&gt;
* [[AOWIS:Contributor_Guide_Internal|Contributor Guide - Internal]]&lt;br /&gt;
* [[AOWIS:Writing_Style_Guide|Writing Style Guide]]&lt;br /&gt;
* [[AOWIS:AI_Usage_Guide|AI Usage Guide]]&lt;br /&gt;
* [[AOWIS:Research_Form_Guide|Research Form Guide]]&lt;br /&gt;
* [[AOWIS:Naming_Convention_Specification|Naming Convention Specification]]&lt;br /&gt;
* [[AOWIS:Change_Log__Versioning|Change Log &amp;amp; Versioning]]&lt;br /&gt;
* [[AOWIS:Wiki|This Wiki]]&lt;br /&gt;
&lt;br /&gt;
These pages explain the foundations of AOWIS, how the AOWIS Standard is structured, and how to use and contribute to the project and its documentation.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = List of Requirement Pages&lt;br /&gt;
 | color = brown&lt;br /&gt;
 | body = &lt;br /&gt;
This index lists AOWIS pages that define normative requirements (MUST/SHOULD/MAY statements) and conformance rules.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Dev Rules&#039;&#039;&#039; — specs for writing and maintaining AOWIS&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;REQ-AI:&#039;&#039;&#039; [[AOWIS:AI_Usage_Guide|AI Usage Guide]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Technical Standard&#039;&#039;&#039; — system behavior and data models&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;REQ-MEAS, REQ-MEAS-UI:&#039;&#039;&#039; [[Measurement:Units|Unit System Requirements]]&lt;br /&gt;
* &#039;&#039;&#039;REQ-MEAS-UNI:&#039;&#039;&#039; [[Measurement:Canonical_Units|Canonical Units]]&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = AOWIS Documentation Structure&lt;br /&gt;
 | color = purple&lt;br /&gt;
 | body = &lt;br /&gt;
* [[Motivation:Main_Page|Motivation]] – Real-world problems, constraints, operating conditions, and practical needs that AOWIS is intended to address.&lt;br /&gt;
* [[Standard:Main_Page|Standard]] – The normative core of AOWIS. Defines requirements and definitions specifying what AOWIS-compliant systems MUST, SHOULD, or MAY do.&lt;br /&gt;
* [[Concepts:Main_Page|Concepts]] – Core concepts, design principles, terminology, and system-level ideas used throughout AOWIS.&lt;br /&gt;
* [[Architecture:Main_Page|Architecture]] – Overall system structure, including controllers, components, layers, interfaces, communication, data flows, responsibilities, and interactions between parts of an AOWIS system.&lt;br /&gt;
* [[Infrastructure:Main_Page|Infrastructure]] – Physical infrastructure, technologies, systems, and components that AOWIS is used to plan, design, model, build, monitor, control, operate, maintain, and extend.&lt;br /&gt;
* [[Measurement:Main_Page|Measurement]] – Physical quantities, units, measurement semantics, sensor and manual measurements, calibration, uncertainty, derived values, and the representation of measured information within AOWIS.&lt;br /&gt;
* [[Data:Main_Page|Data]] – Data models, schemas, identifiers, interchange formats, logging, synchronization, persistence, and data lifecycle rules.&lt;br /&gt;
* [[Operations:Main_Page|Operations]] – Monitoring, control, operational procedures, state management, fallback behaviour, decision-making, maintenance activities, and other processes involved in operating infrastructure.&lt;br /&gt;
* [[Modules:Main_Page|Modules]] – Reusable functional components that provide specific capabilities within AOWIS while integrating with the common system architecture and data model.&lt;br /&gt;
* [[Reference:Main_Page|Reference]] – Concrete implementations, engineering designs, example deployments, reference configurations, and validated patterns showing practical ways AOWIS systems can be built and used.&lt;br /&gt;
* [[Databases:Main_Page|Databases]] – Structured knowledge bases, registries, catalogues, and other organized information used by AOWIS and its implementations.&lt;br /&gt;
* [[Governance:Main_Page|Governance]] – Conformance, certification, review, auditing, versioning, licensing, trust, and organizational processes governing AOWIS and its development.&lt;br /&gt;
* [[Training:Main_Page|Training]] – Educational and practical material for operators, technicians, engineers, developers, contributors, communities, and others working with AOWIS and the infrastructure it supports.&lt;br /&gt;
* [[Regions:Main_Page|Regions]] – Place-specific information about geographic areas, including environmental, hydrological, climatic, socioeconomic, geological, infrastructure, water-resource, and field-project context.&lt;br /&gt;
* [[Geology:Main_Page|Geology]] – Geological, geomorphological, hydrogeological, hydrogeochemical, and geophysical knowledge relevant to water resources, groundwater occurrence and movement, subsurface investigation, borehole siting, and the understanding of local and regional geological conditions.&lt;br /&gt;
&lt;br /&gt;
* [[External:Main_Page|External]] – External standards, projects, technologies, tools, organizations, and systems relevant to AOWIS, its interoperability, or the domains in which it is used.&lt;br /&gt;
&lt;br /&gt;
For a full overview, see the [[AOWIS:Table_of_Contents|Table of Contents]].&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Roadmap&lt;br /&gt;
 | color = grey&lt;br /&gt;
 | body =&lt;br /&gt;
[[File:Boring.jpg|250px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS has progressed beyond its initial conceptual phase. A substantial software foundation for modelling, simulating, visualizing, and eventually operating water infrastructure is under active development.&lt;br /&gt;
&lt;br /&gt;
The current software stack already includes:&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Shared infrastructure model&#039;&#039;&#039;&lt;br /&gt;
: A common, solver-independent representation of water infrastructure used throughout the AOWIS software stack.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-MODEL GitHub AOWIS-SERVER-MODEL]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Hydraulic and water-quality simulation&#039;&#039;&#039;&lt;br /&gt;
: EPANET integration for hydraulic and water-quality simulation, network import/export, controls, rules, diagnostics, and simulation results. Integration of &#039;&#039;&#039;EPANET-MSX&#039;&#039;&#039; is also being developed.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-EPANET GitHub AOWIS-SERVER-EPANET]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Network editor and monitoring interface&#039;&#039;&#039;&lt;br /&gt;
: A graphical application for creating, inspecting, simulating, and visualizing water networks, including geographic maps and terrain-aware 3D visualization.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-GUI GitHub AOWIS-SERVER-GUI]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Geographic and terrain infrastructure&#039;&#039;&#039;&lt;br /&gt;
: Mapping, elevation data, basemaps, terrain visualization, geographic placement, and local caching.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-MAP GitHub AOWIS-SERVER-MAP]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Local and standalone operation&#039;&#039;&#039;&lt;br /&gt;
: Support for deployments that do not depend on continuous Internet or cloud connectivity.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-Standalone GitHub AOWIS-SERVER-Standalone]&lt;br /&gt;
&lt;br /&gt;
The software remains under active development and should not yet be considered a complete production SCADA system.&lt;br /&gt;
&lt;br /&gt;
The next major stage is to connect the existing modelling and simulation environment to &#039;&#039;&#039;real infrastructure in continuous operation&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The AOWIS software platform is intended to develop into a complete open-source SCADA, infrastructure modelling, simulation, and operational management platform in which planning, live monitoring, control, historical data, maintenance, and simulation operate on the same shared infrastructure model.&lt;br /&gt;
&lt;br /&gt;
This includes telemetry, sensors and actuators, alarms and historian functions, local and remote control, automation with safe fallback behaviour, and model-assisted operation using measured and simulated system behaviour.&lt;br /&gt;
&lt;br /&gt;
EPANET currently provides the primary hydraulic and water-quality simulation engine, but AOWIS is not designed solely as an EPANET frontend. EPANET is one solver integrated into a broader, solver-independent architecture.&lt;br /&gt;
&lt;br /&gt;
The long-term objective is to connect the complete infrastructure lifecycle:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;survey and planning → engineering and simulation → construction → commissioning → monitoring → control → maintenance → analysis → expansion&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[[AOWIS:Roadmap|Read the full roadmap →]]&#039;&#039;&#039;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
| title = Community &amp;amp; Participation&lt;br /&gt;
| color = blue&lt;br /&gt;
| body =&lt;br /&gt;
&lt;br /&gt;
AOWIS is an open project, and participation is welcome from anyone interested in its goals — including engineers, developers, NGOs, operators, researchers, technicians, students, and people with practical experience in water and irrigation infrastructure.&lt;br /&gt;
&lt;br /&gt;
For &#039;&#039;&#039;discussion, planning, questions, documentation, infrastructure, field projects, standards, research, and other forms of participation&#039;&#039;&#039;, AOWIS uses &#039;&#039;&#039;Matrix&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The AOWIS Matrix server has several &#039;&#039;&#039;public spaces and rooms&#039;&#039;&#039; for different topics. Join those relevant to your interests. For general questions or help finding the right place, start here:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://matrix.to/#/#support:aowis.org AOWIS Support — #support:aowis.org]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Any Matrix account can join public AOWIS spaces and rooms.&lt;br /&gt;
&lt;br /&gt;
If you are new to Matrix:&lt;br /&gt;
&lt;br /&gt;
* [https://matrix.org/try-matrix/ Learn about Matrix and create an account]&lt;br /&gt;
* [https://element.io/ Element] — Matrix client for web, desktop, and mobile&lt;br /&gt;
* [https://fluffychat.im/ FluffyChat] — simple Matrix client for several platforms&lt;br /&gt;
&lt;br /&gt;
The same Matrix account can be used with different clients.&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;AOWIS Matrix Accounts&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Participants may also request an account on the AOWIS Matrix homeserver, giving them an ID such as &#039;&#039;&#039;@name:aowis.org&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
To reduce automated registrations and abuse, accounts are created on request. Please send a short introduction telling us who you are, what interests you about AOWIS, and where you would like to participate: [[File:Mtx.png|120px|frameless|alt=Email address for requesting an AOWIS Matrix account]]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Software Development&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Software development happens on &#039;&#039;&#039;GitHub&#039;&#039;&#039;. Bug reports, pull requests, source-code contributions, and repository-specific development discussions should use the appropriate repository.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://github.com/aowis-org AOWIS on GitHub]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Matrix is for the broader AOWIS community and participation that does not naturally belong in a GitHub repository.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Governance &amp;amp; Legitimacy&lt;br /&gt;
 | color = turquoise&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS includes a transparent governance model to ensure:&lt;br /&gt;
&lt;br /&gt;
* open participation  &lt;br /&gt;
* clear certification processes  &lt;br /&gt;
* stable versioning  &lt;br /&gt;
* long-term stewardship and continuity&lt;br /&gt;
&lt;br /&gt;
See: [[Governance:Main_Page|Governance]].&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Navigation&lt;br /&gt;
 | color = grey&lt;br /&gt;
 | body =&lt;br /&gt;
* [[AOWIS:Table_of_Contents|Table of Contents]]  &lt;br /&gt;
* [[Reference:Glossary|Glossary]]  &lt;br /&gt;
* [[Reference:FAQ|FAQ]]  &lt;br /&gt;
* [[Reference:Change_Log|Change Log]]  &lt;br /&gt;
&lt;br /&gt;
* [https://github.com/aowis-org GitHub]&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Partners&lt;br /&gt;
 | color = indigo&lt;br /&gt;
 | body = &lt;br /&gt;
[[File:Afriticgroup.webp|250px|frameless|center|link=https://afriticgroup.com/]]&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Samuel</name></author>
	</entry>
	<entry>
		<id>https://aowis.org/index.php?title=Main_Page&amp;diff=777</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://aowis.org/index.php?title=Main_Page&amp;diff=777"/>
		<updated>2026-09-24T21:00:46Z</updated>

		<summary type="html">&lt;p&gt;Samuel: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
&lt;br /&gt;
{{MainPageBanner}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Motivation&lt;br /&gt;
 | color = teal&lt;br /&gt;
 | body = &lt;br /&gt;
&lt;br /&gt;
[[File:Countryside.jpg|class=fullwidth|center]]&lt;br /&gt;
&lt;br /&gt;
In many rural and underserved regions, including parts of Africa, wells and pumps may exist while developing and operating a reliable distribution network remains difficult. Local initiatives can lack engineering capacity, trained personnel, suitable technology, and affordable tools for operating such infrastructure sustainably.&lt;br /&gt;
&lt;br /&gt;
This practical problem is an important motivation for AOWIS. AOWIS aims to make the engineering knowledge, technical foundations, software, and operational methods needed to develop and operate water infrastructure openly available and practically usable, while supporting local training and cooperation with experienced organizations and operators.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Why AOWIS is Needed&lt;br /&gt;
 | color = turquoise&lt;br /&gt;
 | body = &lt;br /&gt;
&lt;br /&gt;
[[File:Cooperation.jpg|400px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
Water and irrigation infrastructure must often be planned, built, expanded, and operated over many decades. In some places, existing infrastructure has become fragmented across different vendors, technologies, tools, and engineering approaches. In others, communities and organizations are building coherent water infrastructure for the first time and may have limited access to engineering capacity, technical guidance, suitable software, or established operational practices.&lt;br /&gt;
&lt;br /&gt;
AOWIS provides a shared open foundation for both situations. It brings together technical standards, engineering knowledge, software, reference implementations, operational guidance, and training to support the development of water infrastructure from initial planning and design through construction, operation, maintenance, and future expansion.&lt;br /&gt;
&lt;br /&gt;
The aim is to make infrastructure understandable, interoperable, maintainable, and extensible throughout its lifecycle, while reducing dependence on individual vendors, products, suppliers, or scarce specialist expertise.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Operating Conditions&lt;br /&gt;
 | color = lightblue&lt;br /&gt;
 | body =&lt;br /&gt;
&lt;br /&gt;
[[File:Village.jpg|250px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS is designed for environments where water infrastructure must remain useful and safe despite difficult technical and operational conditions. This is particularly important in rural and underserved regions, where reliable power, continuous connectivity, modern equipment, trained personnel, and specialist support cannot always be assumed.&lt;br /&gt;
&lt;br /&gt;
Typical conditions include:&lt;br /&gt;
&lt;br /&gt;
* unreliable or limited power supply&lt;br /&gt;
* intermittent or unavailable connectivity&lt;br /&gt;
* heterogeneous or aging equipment&lt;br /&gt;
* limited availability of trained technical personnel&lt;br /&gt;
* limited access to specialist engineering support&lt;br /&gt;
* the need for safe local operation without continuous remote supervision&lt;br /&gt;
&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Design Principles&lt;br /&gt;
 | color = lightblue&lt;br /&gt;
 | body =&lt;br /&gt;
&lt;br /&gt;
AOWIS addresses these conditions through principles including:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;offline-first operation&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;safe fallback behaviour&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;human-in-the-loop control&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;local autonomous operation&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;modular and extensible system design&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;shared infrastructure models&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;open interfaces and accessible technical documentation&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The goal is to make essential water infrastructure &#039;&#039;&#039;robust, understandable, maintainable, and locally operable&#039;&#039;&#039;, including where conventional assumptions about connectivity, technical resources, and institutional support do not hold.&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
| title = Software &amp;amp; Downloads&lt;br /&gt;
| color = green&lt;br /&gt;
| body =&lt;br /&gt;
[[File:GUI ky4 3d.png|400px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS includes an open-source software platform for &#039;&#039;&#039;modelling, simulating, visualizing, monitoring, and operating water infrastructure&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The current software includes a network editor and monitoring interface, hydraulic and water-quality simulation using [[External:EPANET:Main Page|EPANET]], geographic maps and terrain visualization, and support for local and standalone operation. Development of the AOWIS Controller is progressing toward a complete open-source SCADA and operational management platform..&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://download.aowis.org Download the AOWIS Controller (development snapshot)]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* [https://github.com/aowis-org Source code on GitHub]&lt;br /&gt;
* [[#Roadmap|Software development roadmap]]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Start Here&lt;br /&gt;
 | color = yellow&lt;br /&gt;
 | body =&lt;br /&gt;
If you are new to AOWIS, begin with:&lt;br /&gt;
&lt;br /&gt;
* [[Concepts:Design_Philosophy|Design Philosophy]]  &lt;br /&gt;
* [[Standard:Definitions|Definitions]]  &lt;br /&gt;
* [[Standard:Normative_Requirements|Normative Requirements]]  &lt;br /&gt;
* [[Modules:Module_Template|Module Template]]  &lt;br /&gt;
* [[AOWIS:Contributor_Guide_External|Contributor Guide - External]]&lt;br /&gt;
* [[AOWIS:Contributor_Guide_Internal|Contributor Guide - Internal]]&lt;br /&gt;
* [[AOWIS:Writing_Style_Guide|Writing Style Guide]]&lt;br /&gt;
* [[AOWIS:AI_Usage_Guide|AI Usage Guide]]&lt;br /&gt;
* [[AOWIS:Research_Form_Guide|Research Form Guide]]&lt;br /&gt;
* [[AOWIS:Naming_Convention_Specification|Naming Convention Specification]]&lt;br /&gt;
* [[AOWIS:Change_Log__Versioning|Change Log &amp;amp; Versioning]]&lt;br /&gt;
* [[AOWIS:Wiki|This Wiki]]&lt;br /&gt;
&lt;br /&gt;
These pages explain the foundations of AOWIS, how the AOWIS Standard is structured, and how to use and contribute to the project and its documentation.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = List of Requirement Pages&lt;br /&gt;
 | color = brown&lt;br /&gt;
 | body = &lt;br /&gt;
This index lists AOWIS pages that define normative requirements (MUST/SHOULD/MAY statements) and conformance rules.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Dev Rules&#039;&#039;&#039; — specs for writing and maintaining AOWIS&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;REQ-AI:&#039;&#039;&#039; [[AOWIS:AI_Usage_Guide|AI Usage Guide]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Technical Standard&#039;&#039;&#039; — system behavior and data models&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;REQ-MEAS, REQ-MEAS-UI:&#039;&#039;&#039; [[Measurement:Units|Unit System Requirements]]&lt;br /&gt;
* &#039;&#039;&#039;REQ-MEAS-UNI:&#039;&#039;&#039; [[Measurement:Canonical_Units|Canonical Units]]&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = AOWIS Documentation Structure&lt;br /&gt;
 | color = purple&lt;br /&gt;
 | body = &lt;br /&gt;
* [[Motivation:Main_Page|Motivation]] – Real-world problems, constraints, operating conditions, and practical needs that AOWIS is intended to address.&lt;br /&gt;
* [[Standard:Main_Page|Standard]] – The normative core of AOWIS. Defines requirements and definitions specifying what AOWIS-compliant systems MUST, SHOULD, or MAY do.&lt;br /&gt;
* [[Concepts:Main_Page|Concepts]] – Core concepts, design principles, terminology, and system-level ideas used throughout AOWIS.&lt;br /&gt;
* [[Architecture:Main_Page|Architecture]] – Overall system structure, including controllers, components, layers, interfaces, communication, data flows, responsibilities, and interactions between parts of an AOWIS system.&lt;br /&gt;
* [[Infrastructure:Main_Page|Infrastructure]] – Physical infrastructure, technologies, systems, and components that AOWIS is used to plan, design, model, build, monitor, control, operate, maintain, and extend.&lt;br /&gt;
* [[Measurement:Main_Page|Measurement]] – Physical quantities, units, measurement semantics, sensor and manual measurements, calibration, uncertainty, derived values, and the representation of measured information within AOWIS.&lt;br /&gt;
* [[Data:Main_Page|Data]] – Data models, schemas, identifiers, interchange formats, logging, synchronization, persistence, and data lifecycle rules.&lt;br /&gt;
* [[Operations:Main_Page|Operations]] – Monitoring, control, operational procedures, state management, fallback behaviour, decision-making, maintenance activities, and other processes involved in operating infrastructure.&lt;br /&gt;
* [[Modules:Main_Page|Modules]] – Reusable functional components that provide specific capabilities within AOWIS while integrating with the common system architecture and data model.&lt;br /&gt;
* [[Reference:Main_Page|Reference]] – Concrete implementations, engineering designs, example deployments, reference configurations, and validated patterns showing practical ways AOWIS systems can be built and used.&lt;br /&gt;
* [[Databases:Main_Page|Databases]] – Structured knowledge bases, registries, catalogues, and other organized information used by AOWIS and its implementations.&lt;br /&gt;
* [[Governance:Main_Page|Governance]] – Conformance, certification, review, auditing, versioning, licensing, trust, and organizational processes governing AOWIS and its development.&lt;br /&gt;
* [[Training:Main_Page|Training]] – Educational and practical material for operators, technicians, engineers, developers, contributors, communities, and others working with AOWIS and the infrastructure it supports.&lt;br /&gt;
* [[Regions:Main_Page|Regions]] – Place-specific information about geographic areas, including environmental, hydrological, climatic, socioeconomic, geological, infrastructure, water-resource, and field-project context.&lt;br /&gt;
* [[Geology:Main_Page|Geology]] – Geological, geomorphological, hydrogeological, hydrogeochemical, and geophysical knowledge relevant to water resources, groundwater occurrence and movement, subsurface investigation, borehole siting, and the understanding of local and regional geological conditions.&lt;br /&gt;
* [[External:Main_Page|External]] – External standards, projects, technologies, tools, organizations, and systems relevant to AOWIS, its interoperability, or the domains in which it is used.&lt;br /&gt;
&lt;br /&gt;
For a full overview, see the [[AOWIS:Table_of_Contents|Table of Contents]].&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Roadmap&lt;br /&gt;
 | color = grey&lt;br /&gt;
 | body =&lt;br /&gt;
[[File:Boring.jpg|250px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS has progressed beyond its initial conceptual phase. A substantial software foundation for modelling, simulating, visualizing, and eventually operating water infrastructure is under active development.&lt;br /&gt;
&lt;br /&gt;
The current software stack already includes:&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Shared infrastructure model&#039;&#039;&#039;&lt;br /&gt;
: A common, solver-independent representation of water infrastructure used throughout the AOWIS software stack.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-MODEL GitHub AOWIS-SERVER-MODEL]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Hydraulic and water-quality simulation&#039;&#039;&#039;&lt;br /&gt;
: EPANET integration for hydraulic and water-quality simulation, network import/export, controls, rules, diagnostics, and simulation results. Integration of &#039;&#039;&#039;EPANET-MSX&#039;&#039;&#039; is also being developed.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-EPANET GitHub AOWIS-SERVER-EPANET]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Network editor and monitoring interface&#039;&#039;&#039;&lt;br /&gt;
: A graphical application for creating, inspecting, simulating, and visualizing water networks, including geographic maps and terrain-aware 3D visualization.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-GUI GitHub AOWIS-SERVER-GUI]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Geographic and terrain infrastructure&#039;&#039;&#039;&lt;br /&gt;
: Mapping, elevation data, basemaps, terrain visualization, geographic placement, and local caching.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-MAP GitHub AOWIS-SERVER-MAP]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Local and standalone operation&#039;&#039;&#039;&lt;br /&gt;
: Support for deployments that do not depend on continuous Internet or cloud connectivity.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-Standalone GitHub AOWIS-SERVER-Standalone]&lt;br /&gt;
&lt;br /&gt;
The software remains under active development and should not yet be considered a complete production SCADA system.&lt;br /&gt;
&lt;br /&gt;
The next major stage is to connect the existing modelling and simulation environment to &#039;&#039;&#039;real infrastructure in continuous operation&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The AOWIS software platform is intended to develop into a complete open-source SCADA, infrastructure modelling, simulation, and operational management platform in which planning, live monitoring, control, historical data, maintenance, and simulation operate on the same shared infrastructure model.&lt;br /&gt;
&lt;br /&gt;
This includes telemetry, sensors and actuators, alarms and historian functions, local and remote control, automation with safe fallback behaviour, and model-assisted operation using measured and simulated system behaviour.&lt;br /&gt;
&lt;br /&gt;
EPANET currently provides the primary hydraulic and water-quality simulation engine, but AOWIS is not designed solely as an EPANET frontend. EPANET is one solver integrated into a broader, solver-independent architecture.&lt;br /&gt;
&lt;br /&gt;
The long-term objective is to connect the complete infrastructure lifecycle:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;survey and planning → engineering and simulation → construction → commissioning → monitoring → control → maintenance → analysis → expansion&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[[AOWIS:Roadmap|Read the full roadmap →]]&#039;&#039;&#039;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
| title = Community &amp;amp; Participation&lt;br /&gt;
| color = blue&lt;br /&gt;
| body =&lt;br /&gt;
&lt;br /&gt;
AOWIS is an open project, and participation is welcome from anyone interested in its goals — including engineers, developers, NGOs, operators, researchers, technicians, students, and people with practical experience in water and irrigation infrastructure.&lt;br /&gt;
&lt;br /&gt;
For &#039;&#039;&#039;discussion, planning, questions, documentation, infrastructure, field projects, standards, research, and other forms of participation&#039;&#039;&#039;, AOWIS uses &#039;&#039;&#039;Matrix&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The AOWIS Matrix server has several &#039;&#039;&#039;public spaces and rooms&#039;&#039;&#039; for different topics. Join those relevant to your interests. For general questions or help finding the right place, start here:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://matrix.to/#/#support:aowis.org AOWIS Support — #support:aowis.org]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Any Matrix account can join public AOWIS spaces and rooms.&lt;br /&gt;
&lt;br /&gt;
If you are new to Matrix:&lt;br /&gt;
&lt;br /&gt;
* [https://matrix.org/try-matrix/ Learn about Matrix and create an account]&lt;br /&gt;
* [https://element.io/ Element] — Matrix client for web, desktop, and mobile&lt;br /&gt;
* [https://fluffychat.im/ FluffyChat] — simple Matrix client for several platforms&lt;br /&gt;
&lt;br /&gt;
The same Matrix account can be used with different clients.&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;AOWIS Matrix Accounts&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Participants may also request an account on the AOWIS Matrix homeserver, giving them an ID such as &#039;&#039;&#039;@name:aowis.org&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
To reduce automated registrations and abuse, accounts are created on request. Please send a short introduction telling us who you are, what interests you about AOWIS, and where you would like to participate: [[File:Mtx.png|120px|frameless|alt=Email address for requesting an AOWIS Matrix account]]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Software Development&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Software development happens on &#039;&#039;&#039;GitHub&#039;&#039;&#039;. Bug reports, pull requests, source-code contributions, and repository-specific development discussions should use the appropriate repository.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://github.com/aowis-org AOWIS on GitHub]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Matrix is for the broader AOWIS community and participation that does not naturally belong in a GitHub repository.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Governance &amp;amp; Legitimacy&lt;br /&gt;
 | color = turquoise&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS includes a transparent governance model to ensure:&lt;br /&gt;
&lt;br /&gt;
* open participation  &lt;br /&gt;
* clear certification processes  &lt;br /&gt;
* stable versioning  &lt;br /&gt;
* long-term stewardship and continuity&lt;br /&gt;
&lt;br /&gt;
See: [[Governance:Main_Page|Governance]].&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Navigation&lt;br /&gt;
 | color = grey&lt;br /&gt;
 | body =&lt;br /&gt;
* [[AOWIS:Table_of_Contents|Table of Contents]]  &lt;br /&gt;
* [[Reference:Glossary|Glossary]]  &lt;br /&gt;
* [[Reference:FAQ|FAQ]]  &lt;br /&gt;
* [[Reference:Change_Log|Change Log]]  &lt;br /&gt;
&lt;br /&gt;
* [https://github.com/aowis-org GitHub]&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Partners&lt;br /&gt;
 | color = indigo&lt;br /&gt;
 | body = &lt;br /&gt;
[[File:Afriticgroup.webp|250px|frameless|center|link=https://afriticgroup.com/]]&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Samuel</name></author>
	</entry>
	<entry>
		<id>https://aowis.org/index.php?title=Main_Page&amp;diff=776</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://aowis.org/index.php?title=Main_Page&amp;diff=776"/>
		<updated>2026-09-24T20:56:29Z</updated>

		<summary type="html">&lt;p&gt;Samuel: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
&lt;br /&gt;
{{MainPageBanner}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Motivation&lt;br /&gt;
 | color = teal&lt;br /&gt;
 | body = &lt;br /&gt;
&lt;br /&gt;
[[File:Countryside.jpg|class=fullwidth|center]]&lt;br /&gt;
&lt;br /&gt;
In many rural and underserved regions, including parts of Africa, wells and pumps may exist while developing and operating a reliable distribution network remains difficult. Local initiatives can lack engineering capacity, trained personnel, suitable technology, and affordable tools for operating such infrastructure sustainably.&lt;br /&gt;
&lt;br /&gt;
This practical problem is an important motivation for AOWIS. AOWIS aims to make the engineering knowledge, technical foundations, software, and operational methods needed to develop and operate water infrastructure openly available and practically usable, while supporting local training and cooperation with experienced organizations and operators.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Why AOWIS is Needed&lt;br /&gt;
 | color = turquoise&lt;br /&gt;
 | body = &lt;br /&gt;
&lt;br /&gt;
[[File:Cooperation.jpg|400px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
Water and irrigation infrastructure must often be planned, built, expanded, and operated over many decades. In some places, existing infrastructure has become fragmented across different vendors, technologies, tools, and engineering approaches. In others, communities and organizations are building coherent water infrastructure for the first time and may have limited access to engineering capacity, technical guidance, suitable software, or established operational practices.&lt;br /&gt;
&lt;br /&gt;
AOWIS provides a shared open foundation for both situations. It brings together technical standards, engineering knowledge, software, reference implementations, operational guidance, and training to support the development of water infrastructure from initial planning and design through construction, operation, maintenance, and future expansion.&lt;br /&gt;
&lt;br /&gt;
The aim is to make infrastructure understandable, interoperable, maintainable, and extensible throughout its lifecycle, while reducing dependence on individual vendors, products, suppliers, or scarce specialist expertise.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Operating Conditions&lt;br /&gt;
 | color = lightblue&lt;br /&gt;
 | body =&lt;br /&gt;
&lt;br /&gt;
[[File:Village.jpg|250px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS is designed for environments where water infrastructure must remain useful and safe despite difficult technical and operational conditions. This is particularly important in rural and underserved regions, where reliable power, continuous connectivity, modern equipment, trained personnel, and specialist support cannot always be assumed.&lt;br /&gt;
&lt;br /&gt;
Typical conditions include:&lt;br /&gt;
&lt;br /&gt;
* unreliable or limited power supply&lt;br /&gt;
* intermittent or unavailable connectivity&lt;br /&gt;
* heterogeneous or aging equipment&lt;br /&gt;
* limited availability of trained technical personnel&lt;br /&gt;
* limited access to specialist engineering support&lt;br /&gt;
* the need for safe local operation without continuous remote supervision&lt;br /&gt;
&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Design Principles&lt;br /&gt;
 | color = lightblue&lt;br /&gt;
 | body =&lt;br /&gt;
&lt;br /&gt;
AOWIS addresses these conditions through principles including:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;offline-first operation&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;safe fallback behaviour&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;human-in-the-loop control&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;local autonomous operation&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;modular and extensible system design&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;shared infrastructure models&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;open interfaces and accessible technical documentation&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The goal is to make essential water infrastructure &#039;&#039;&#039;robust, understandable, maintainable, and locally operable&#039;&#039;&#039;, including where conventional assumptions about connectivity, technical resources, and institutional support do not hold.&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
| title = Software &amp;amp; Downloads&lt;br /&gt;
| color = green&lt;br /&gt;
| body =&lt;br /&gt;
[[File:GUI ky4 3d.png|400px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS includes an open-source software platform for &#039;&#039;&#039;modelling, simulating, visualizing, monitoring, and operating water infrastructure&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The current software includes a network editor and monitoring interface, hydraulic and water-quality simulation using [[External:EPANET:Main Page|EPANET]], geographic maps and terrain visualization, and support for local and standalone operation. Development of the AOWIS Controller is progressing toward a complete open-source SCADA and operational management platform..&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://download.aowis.org Download the AOWIS Controller (development snapshot)]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* [https://github.com/aowis-org Source code on GitHub]&lt;br /&gt;
* [[#Roadmap|Software development roadmap]]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Start Here&lt;br /&gt;
 | color = yellow&lt;br /&gt;
 | body =&lt;br /&gt;
If you are new to AOWIS, begin with:&lt;br /&gt;
&lt;br /&gt;
* [[Concepts:Design_Philosophy|Design Philosophy]]  &lt;br /&gt;
* [[Standard:Definitions|Definitions]]  &lt;br /&gt;
* [[Standard:Normative_Requirements|Normative Requirements]]  &lt;br /&gt;
* [[Modules:Module_Template|Module Template]]  &lt;br /&gt;
* [[AOWIS:Contributor_Guide_External|Contributor Guide - External]]&lt;br /&gt;
* [[AOWIS:Contributor_Guide_Internal|Contributor Guide - Internal]]&lt;br /&gt;
* [[AOWIS:Writing_Style_Guide|Writing Style Guide]]&lt;br /&gt;
* [[AOWIS:AI_Usage_Guide|AI Usage Guide]]&lt;br /&gt;
* [[AOWIS:Research_Form_Guide|Research Form Guide]]&lt;br /&gt;
* [[AOWIS:Naming_Convention_Specification|Naming Convention Specification]]&lt;br /&gt;
* [[AOWIS:Change_Log__Versioning|Change Log &amp;amp; Versioning]]&lt;br /&gt;
* [[AOWIS:Wiki|This Wiki]]&lt;br /&gt;
&lt;br /&gt;
These pages explain the foundations of AOWIS, how the AOWIS Standard is structured, and how to use and contribute to the project and its documentation.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = List of Requirement Pages&lt;br /&gt;
 | color = brown&lt;br /&gt;
 | body = &lt;br /&gt;
This index lists AOWIS pages that define normative requirements (MUST/SHOULD/MAY statements) and conformance rules.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Dev Rules&#039;&#039;&#039; — specs for writing and maintaining AOWIS&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;REQ-AI:&#039;&#039;&#039; [[AOWIS:AI_Usage_Guide|AI Usage Guide]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Technical Standard&#039;&#039;&#039; — system behavior and data models&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;REQ-MEAS, REQ-MEAS-UI:&#039;&#039;&#039; [[Measurement:Units|Unit System Requirements]]&lt;br /&gt;
* &#039;&#039;&#039;REQ-MEAS-UNI:&#039;&#039;&#039; [[Measurement:Canonical_Units|Canonical Units]]&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = AOWIS Documentation Structure&lt;br /&gt;
 | color = purple&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS documentation is organized into dedicated namespaces with clearly separated purposes.&lt;br /&gt;
&lt;br /&gt;
* [[Motivation:Main_Page|Motivation]] – Real-world problems, constraints, operating conditions, and practical needs that AOWIS is intended to address.&lt;br /&gt;
* [[Standard:Main_Page|Standard]] – The normative core of AOWIS. Defines requirements and definitions specifying what AOWIS-compliant systems MUST, SHOULD, or MAY do.&lt;br /&gt;
* [[Concepts:Main_Page|Concepts]] – Core concepts, design principles, terminology, and system-level ideas used throughout AOWIS.&lt;br /&gt;
* [[Architecture:Main_Page|Architecture]] – Overall system structure, including controllers, components, layers, interfaces, communication, data flows, responsibilities, and interactions between parts of an AOWIS system.&lt;br /&gt;
* [[Infrastructure:Main_Page|Infrastructure]] – Physical infrastructure, technologies, systems, and components that AOWIS is used to plan, design, model, build, monitor, control, operate, maintain, and extend.&lt;br /&gt;
* [[Measurement:Main_Page|Measurement]] – Physical quantities, units, measurement semantics, sensor and manual measurements, calibration, uncertainty, derived values, and the representation of measured information within AOWIS.&lt;br /&gt;
* [[Data:Main_Page|Data]] – Data models, schemas, identifiers, interchange formats, logging, synchronization, persistence, and data lifecycle rules.&lt;br /&gt;
* [[Operations:Main_Page|Operations]] – Monitoring, control, operational procedures, state management, fallback behaviour, decision-making, maintenance activities, and other processes involved in operating infrastructure.&lt;br /&gt;
* [[Modules:Main_Page|Modules]] – Reusable functional components that provide specific capabilities within AOWIS while integrating with the common system architecture and data model.&lt;br /&gt;
* [[Reference:Main_Page|Reference]] – Concrete implementations, engineering designs, example deployments, reference configurations, and validated patterns showing practical ways AOWIS systems can be built and used.&lt;br /&gt;
* [[Databases:Main_Page|Databases]] – Structured knowledge bases, registries, catalogues, and other organized information used by AOWIS and its implementations.&lt;br /&gt;
* [[Governance:Main_Page|Governance]] – Conformance, certification, review, auditing, versioning, licensing, trust, and organizational processes governing AOWIS and its development.&lt;br /&gt;
* [[Training:Main_Page|Training]] – Educational and practical material for operators, technicians, engineers, developers, contributors, communities, and others working with AOWIS and the infrastructure it supports.&lt;br /&gt;
* [[Regions:Main_Page|Regions]] – Place-specific information about geographic areas, including environmental, hydrological, climatic, socioeconomic, geological, infrastructure, water-resource, and field-project context.&lt;br /&gt;
* [[Geology:Main_Page|Geology]] – Geological, geomorphological, hydrogeological, hydrogeochemical, and geophysical knowledge relevant to water resources, groundwater occurrence and movement, subsurface investigation, borehole siting, and the understanding of local and regional geological conditions.&lt;br /&gt;
* [[External:Main_Page|External]] – External standards, projects, technologies, tools, organizations, and systems relevant to AOWIS, its interoperability, or the domains in which it is used.&lt;br /&gt;
&lt;br /&gt;
For a full overview, see the [[AOWIS:Table_of_Contents|Table of Contents]].&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Roadmap&lt;br /&gt;
 | color = grey&lt;br /&gt;
 | body =&lt;br /&gt;
[[File:Boring.jpg|250px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS has progressed beyond its initial conceptual phase. A substantial software foundation for modelling, simulating, visualizing, and eventually operating water infrastructure is under active development.&lt;br /&gt;
&lt;br /&gt;
The current software stack already includes:&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Shared infrastructure model&#039;&#039;&#039;&lt;br /&gt;
: A common, solver-independent representation of water infrastructure used throughout the AOWIS software stack.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-MODEL GitHub AOWIS-SERVER-MODEL]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Hydraulic and water-quality simulation&#039;&#039;&#039;&lt;br /&gt;
: EPANET integration for hydraulic and water-quality simulation, network import/export, controls, rules, diagnostics, and simulation results. Integration of &#039;&#039;&#039;EPANET-MSX&#039;&#039;&#039; is also being developed.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-EPANET GitHub AOWIS-SERVER-EPANET]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Network editor and monitoring interface&#039;&#039;&#039;&lt;br /&gt;
: A graphical application for creating, inspecting, simulating, and visualizing water networks, including geographic maps and terrain-aware 3D visualization.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-GUI GitHub AOWIS-SERVER-GUI]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Geographic and terrain infrastructure&#039;&#039;&#039;&lt;br /&gt;
: Mapping, elevation data, basemaps, terrain visualization, geographic placement, and local caching.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-MAP GitHub AOWIS-SERVER-MAP]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Local and standalone operation&#039;&#039;&#039;&lt;br /&gt;
: Support for deployments that do not depend on continuous Internet or cloud connectivity.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-Standalone GitHub AOWIS-SERVER-Standalone]&lt;br /&gt;
&lt;br /&gt;
The software remains under active development and should not yet be considered a complete production SCADA system.&lt;br /&gt;
&lt;br /&gt;
The next major stage is to connect the existing modelling and simulation environment to &#039;&#039;&#039;real infrastructure in continuous operation&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The AOWIS software platform is intended to develop into a complete open-source SCADA, infrastructure modelling, simulation, and operational management platform in which planning, live monitoring, control, historical data, maintenance, and simulation operate on the same shared infrastructure model.&lt;br /&gt;
&lt;br /&gt;
This includes telemetry, sensors and actuators, alarms and historian functions, local and remote control, automation with safe fallback behaviour, and model-assisted operation using measured and simulated system behaviour.&lt;br /&gt;
&lt;br /&gt;
EPANET currently provides the primary hydraulic and water-quality simulation engine, but AOWIS is not designed solely as an EPANET frontend. EPANET is one solver integrated into a broader, solver-independent architecture.&lt;br /&gt;
&lt;br /&gt;
The long-term objective is to connect the complete infrastructure lifecycle:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;survey and planning → engineering and simulation → construction → commissioning → monitoring → control → maintenance → analysis → expansion&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[[AOWIS:Roadmap|Read the full roadmap →]]&#039;&#039;&#039;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
| title = Community &amp;amp; Participation&lt;br /&gt;
| color = blue&lt;br /&gt;
| body =&lt;br /&gt;
&lt;br /&gt;
AOWIS is an open project, and participation is welcome from anyone interested in its goals — including engineers, developers, NGOs, operators, researchers, technicians, students, and people with practical experience in water and irrigation infrastructure.&lt;br /&gt;
&lt;br /&gt;
For &#039;&#039;&#039;discussion, planning, questions, documentation, infrastructure, field projects, standards, research, and other forms of participation&#039;&#039;&#039;, AOWIS uses &#039;&#039;&#039;Matrix&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The AOWIS Matrix server has several &#039;&#039;&#039;public spaces and rooms&#039;&#039;&#039; for different topics. Join those relevant to your interests. For general questions or help finding the right place, start here:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://matrix.to/#/#support:aowis.org AOWIS Support — #support:aowis.org]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Any Matrix account can join public AOWIS spaces and rooms.&lt;br /&gt;
&lt;br /&gt;
If you are new to Matrix:&lt;br /&gt;
&lt;br /&gt;
* [https://matrix.org/try-matrix/ Learn about Matrix and create an account]&lt;br /&gt;
* [https://element.io/ Element] — Matrix client for web, desktop, and mobile&lt;br /&gt;
* [https://fluffychat.im/ FluffyChat] — simple Matrix client for several platforms&lt;br /&gt;
&lt;br /&gt;
The same Matrix account can be used with different clients.&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;AOWIS Matrix Accounts&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Participants may also request an account on the AOWIS Matrix homeserver, giving them an ID such as &#039;&#039;&#039;@name:aowis.org&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
To reduce automated registrations and abuse, accounts are created on request. Please send a short introduction telling us who you are, what interests you about AOWIS, and where you would like to participate: [[File:Mtx.png|120px|frameless|alt=Email address for requesting an AOWIS Matrix account]]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Software Development&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Software development happens on &#039;&#039;&#039;GitHub&#039;&#039;&#039;. Bug reports, pull requests, source-code contributions, and repository-specific development discussions should use the appropriate repository.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://github.com/aowis-org AOWIS on GitHub]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Matrix is for the broader AOWIS community and participation that does not naturally belong in a GitHub repository.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Governance &amp;amp; Legitimacy&lt;br /&gt;
 | color = turquoise&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS includes a transparent governance model to ensure:&lt;br /&gt;
&lt;br /&gt;
* open participation  &lt;br /&gt;
* clear certification processes  &lt;br /&gt;
* stable versioning  &lt;br /&gt;
* long-term stewardship and continuity&lt;br /&gt;
&lt;br /&gt;
See: [[Governance:Main_Page|Governance]].&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Navigation&lt;br /&gt;
 | color = grey&lt;br /&gt;
 | body =&lt;br /&gt;
* [[AOWIS:Table_of_Contents|Table of Contents]]  &lt;br /&gt;
* [[Reference:Glossary|Glossary]]  &lt;br /&gt;
* [[Reference:FAQ|FAQ]]  &lt;br /&gt;
* [[Reference:Change_Log|Change Log]]  &lt;br /&gt;
&lt;br /&gt;
* [https://github.com/aowis-org GitHub]&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Partners&lt;br /&gt;
 | color = indigo&lt;br /&gt;
 | body = &lt;br /&gt;
[[File:Afriticgroup.webp|250px|frameless|center|link=https://afriticgroup.com/]]&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Samuel</name></author>
	</entry>
	<entry>
		<id>https://aowis.org/index.php?title=Geology:Main_Page&amp;diff=775</id>
		<title>Geology:Main Page</title>
		<link rel="alternate" type="text/html" href="https://aowis.org/index.php?title=Geology:Main_Page&amp;diff=775"/>
		<updated>2026-09-24T20:50:45Z</updated>

		<summary type="html">&lt;p&gt;Samuel: Created page with &amp;quot;{{AI-Generated  | tool=ChatGPT  | date=2026-09-24  | scope=this page }}  The &amp;#039;&amp;#039;&amp;#039;Geology&amp;#039;&amp;#039;&amp;#039; section covers geological, geomorphological, hydrogeological, hydrogeochemical, and geophysical topics relevant to water resources, groundwater development, subsurface investigation, and infrastructure.  == Topics ==  * &amp;#039;&amp;#039;&amp;#039;Hydrogeology&amp;#039;&amp;#039;&amp;#039; – Groundwater occurrence, storage, movement, recharge, discharge, aquifers, fractures, weathered zones, and groundwate...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{AI-Generated&lt;br /&gt;
 | tool=ChatGPT&lt;br /&gt;
 | date=2026-09-24&lt;br /&gt;
 | scope=this page&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;Geology&#039;&#039;&#039; section covers geological, geomorphological, hydrogeological, hydrogeochemical, and geophysical topics relevant to water resources, groundwater development, subsurface investigation, and infrastructure.&lt;br /&gt;
&lt;br /&gt;
== Topics ==&lt;br /&gt;
&lt;br /&gt;
* [[Geology:Hydrogeology|&#039;&#039;&#039;Hydrogeology&#039;&#039;&#039;]] – Groundwater occurrence, storage, movement, recharge, discharge, aquifers, fractures, weathered zones, and groundwater–surface water interaction.&lt;br /&gt;
&lt;br /&gt;
* [[Geology:Geomorphology|&#039;&#039;&#039;Geomorphology&#039;&#039;&#039;]] – Landforms, drainage systems, erosion, deposition, terrain development, and their relevance to groundwater and infrastructure.&lt;br /&gt;
&lt;br /&gt;
* [[Geology:Groundwater_Chemistry|&#039;&#039;&#039;Groundwater Chemistry&#039;&#039;&#039;]] – Hydrogeochemical processes, mineralization, salinity, hardness, groundwater mixing, residence time, and geological influences on water quality.&lt;br /&gt;
&lt;br /&gt;
* [[Geology:Geophysics|&#039;&#039;&#039;Geophysics&#039;&#039;&#039;]] – Geophysical investigation methods used to characterize subsurface structures, geological boundaries, weathered zones, fractures, and groundwater-related features.&lt;br /&gt;
&lt;br /&gt;
* [[Geology:Groundwater_Prospecting|&#039;&#039;&#039;Groundwater Prospecting&#039;&#039;&#039;]] – Investigation and interpretation methods used to identify and evaluate groundwater potential.&lt;br /&gt;
&lt;br /&gt;
* [[Geology:Borehole_Siting|&#039;&#039;&#039;Borehole Siting&#039;&#039;&#039;]] – Geological, hydrogeological, geophysical, environmental, and practical considerations involved in selecting drilling locations.&lt;br /&gt;
&lt;br /&gt;
== Geological Environments ==&lt;br /&gt;
&lt;br /&gt;
* [[Geology:Hydrogeology/Fractured_Basement|Fractured Basement]]&lt;br /&gt;
* [[Geology:Hydrogeology/Weathered_Basement|Weathered Basement]]&lt;br /&gt;
* [[Geology:Hydrogeology/Sedimentary_Aquifers|Sedimentary Aquifers]]&lt;br /&gt;
* [[Geology:Hydrogeology/Alluvial_Aquifers|Alluvial Aquifers]]&lt;br /&gt;
&lt;br /&gt;
== Investigation and Interpretation ==&lt;br /&gt;
&lt;br /&gt;
* [[Geology:Geological_Mapping|Geological Mapping]]&lt;br /&gt;
* [[Geology:Remote_Sensing|Remote Sensing]]&lt;br /&gt;
* [[Geology:Drainage_Analysis|Drainage Analysis]]&lt;br /&gt;
* [[Geology:Geophysics/Electrical_Resistivity|Electrical Resistivity]]&lt;br /&gt;
* [[Geology:Borehole_Logs|Borehole Logs]]&lt;br /&gt;
* [[Geology:Pumping_Tests|Pumping Tests]]&lt;br /&gt;
* [[Geology:Groundwater_Level_Monitoring|Groundwater Level Monitoring]]&lt;br /&gt;
&lt;br /&gt;
== Water Quality and Hydrogeochemistry ==&lt;br /&gt;
&lt;br /&gt;
* [[Geology:Groundwater_Chemistry/Salinity|Salinity]]&lt;br /&gt;
* [[Geology:Groundwater_Chemistry/Hardness|Hardness]]&lt;br /&gt;
* [[Geology:Groundwater_Chemistry/Mineralization|Mineralization]]&lt;br /&gt;
* [[Geology:Groundwater_Chemistry/Redox|Redox Conditions]]&lt;br /&gt;
&lt;br /&gt;
== Regional Application ==&lt;br /&gt;
&lt;br /&gt;
Place-specific geology, hydrogeology, wells, surveys, field observations, and interpretations are documented under [[Regions:Main_Page|Regions]].&lt;br /&gt;
&lt;br /&gt;
Regional pages may reference the general methods, geological environments, and interpretation guidance documented here.&lt;br /&gt;
&lt;br /&gt;
== Related Sections ==&lt;br /&gt;
&lt;br /&gt;
* [[Regions:Main_Page|Regions]]&lt;br /&gt;
* [[Infrastructure:Main_Page|Infrastructure]]&lt;br /&gt;
* [[Measurement:Main_Page|Measurement]]&lt;br /&gt;
* [[Data:Main_Page|Data]]&lt;br /&gt;
* [[Reference:Main_Page|Reference]]&lt;/div&gt;</summary>
		<author><name>Samuel</name></author>
	</entry>
	<entry>
		<id>https://aowis.org/index.php?title=Main_Page&amp;diff=774</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://aowis.org/index.php?title=Main_Page&amp;diff=774"/>
		<updated>2026-09-24T20:40:21Z</updated>

		<summary type="html">&lt;p&gt;Samuel: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
&lt;br /&gt;
{{MainPageBanner}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Motivation&lt;br /&gt;
 | color = teal&lt;br /&gt;
 | body = &lt;br /&gt;
&lt;br /&gt;
[[File:Countryside.jpg|class=fullwidth|center]]&lt;br /&gt;
&lt;br /&gt;
In many rural and underserved regions, including parts of Africa, wells and pumps may exist while developing and operating a reliable distribution network remains difficult. Local initiatives can lack engineering capacity, trained personnel, suitable technology, and affordable tools for operating such infrastructure sustainably.&lt;br /&gt;
&lt;br /&gt;
This practical problem is an important motivation for AOWIS. AOWIS aims to make the engineering knowledge, technical foundations, software, and operational methods needed to develop and operate water infrastructure openly available and practically usable, while supporting local training and cooperation with experienced organizations and operators.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Why AOWIS is Needed&lt;br /&gt;
 | color = turquoise&lt;br /&gt;
 | body = &lt;br /&gt;
&lt;br /&gt;
[[File:Cooperation.jpg|400px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
Water and irrigation infrastructure must often be planned, built, expanded, and operated over many decades. In some places, existing infrastructure has become fragmented across different vendors, technologies, tools, and engineering approaches. In others, communities and organizations are building coherent water infrastructure for the first time and may have limited access to engineering capacity, technical guidance, suitable software, or established operational practices.&lt;br /&gt;
&lt;br /&gt;
AOWIS provides a shared open foundation for both situations. It brings together technical standards, engineering knowledge, software, reference implementations, operational guidance, and training to support the development of water infrastructure from initial planning and design through construction, operation, maintenance, and future expansion.&lt;br /&gt;
&lt;br /&gt;
The aim is to make infrastructure understandable, interoperable, maintainable, and extensible throughout its lifecycle, while reducing dependence on individual vendors, products, suppliers, or scarce specialist expertise.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Operating Conditions&lt;br /&gt;
 | color = lightblue&lt;br /&gt;
 | body =&lt;br /&gt;
&lt;br /&gt;
[[File:Village.jpg|250px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS is designed for environments where water infrastructure must remain useful and safe despite difficult technical and operational conditions. This is particularly important in rural and underserved regions, where reliable power, continuous connectivity, modern equipment, trained personnel, and specialist support cannot always be assumed.&lt;br /&gt;
&lt;br /&gt;
Typical conditions include:&lt;br /&gt;
&lt;br /&gt;
* unreliable or limited power supply&lt;br /&gt;
* intermittent or unavailable connectivity&lt;br /&gt;
* heterogeneous or aging equipment&lt;br /&gt;
* limited availability of trained technical personnel&lt;br /&gt;
* limited access to specialist engineering support&lt;br /&gt;
* the need for safe local operation without continuous remote supervision&lt;br /&gt;
&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Design Principles&lt;br /&gt;
 | color = lightblue&lt;br /&gt;
 | body =&lt;br /&gt;
&lt;br /&gt;
AOWIS addresses these conditions through principles including:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;offline-first operation&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;safe fallback behaviour&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;human-in-the-loop control&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;local autonomous operation&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;modular and extensible system design&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;shared infrastructure models&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;open interfaces and accessible technical documentation&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The goal is to make essential water infrastructure &#039;&#039;&#039;robust, understandable, maintainable, and locally operable&#039;&#039;&#039;, including where conventional assumptions about connectivity, technical resources, and institutional support do not hold.&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
| title = Software &amp;amp; Downloads&lt;br /&gt;
| color = green&lt;br /&gt;
| body =&lt;br /&gt;
[[File:GUI ky4 3d.png|400px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS includes an open-source software platform for &#039;&#039;&#039;modelling, simulating, visualizing, monitoring, and operating water infrastructure&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The current software includes a network editor and monitoring interface, hydraulic and water-quality simulation using [[External:EPANET:Main Page|EPANET]], geographic maps and terrain visualization, and support for local and standalone operation. Development of the AOWIS Controller is progressing toward a complete open-source SCADA and operational management platform..&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://download.aowis.org Download the AOWIS Controller (development snapshot)]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* [https://github.com/aowis-org Source code on GitHub]&lt;br /&gt;
* [[#Roadmap|Software development roadmap]]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Start Here&lt;br /&gt;
 | color = yellow&lt;br /&gt;
 | body =&lt;br /&gt;
If you are new to AOWIS, begin with:&lt;br /&gt;
&lt;br /&gt;
* [[Concepts:Design_Philosophy|Design Philosophy]]  &lt;br /&gt;
* [[Standard:Definitions|Definitions]]  &lt;br /&gt;
* [[Standard:Normative_Requirements|Normative Requirements]]  &lt;br /&gt;
* [[Modules:Module_Template|Module Template]]  &lt;br /&gt;
* [[AOWIS:Contributor_Guide_External|Contributor Guide - External]]&lt;br /&gt;
* [[AOWIS:Contributor_Guide_Internal|Contributor Guide - Internal]]&lt;br /&gt;
* [[AOWIS:Writing_Style_Guide|Writing Style Guide]]&lt;br /&gt;
* [[AOWIS:AI_Usage_Guide|AI Usage Guide]]&lt;br /&gt;
* [[AOWIS:Research_Form_Guide|Research Form Guide]]&lt;br /&gt;
* [[AOWIS:Naming_Convention_Specification|Naming Convention Specification]]&lt;br /&gt;
* [[AOWIS:Change_Log__Versioning|Change Log &amp;amp; Versioning]]&lt;br /&gt;
* [[AOWIS:Wiki|This Wiki]]&lt;br /&gt;
&lt;br /&gt;
These pages explain the foundations of AOWIS, how the AOWIS Standard is structured, and how to use and contribute to the project and its documentation.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = List of Requirement Pages&lt;br /&gt;
 | color = brown&lt;br /&gt;
 | body = &lt;br /&gt;
This index lists AOWIS pages that define normative requirements (MUST/SHOULD/MAY statements) and conformance rules.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Dev Rules&#039;&#039;&#039; — specs for writing and maintaining AOWIS&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;REQ-AI:&#039;&#039;&#039; [[AOWIS:AI_Usage_Guide|AI Usage Guide]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Technical Standard&#039;&#039;&#039; — system behavior and data models&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;REQ-MEAS, REQ-MEAS-UI:&#039;&#039;&#039; [[Measurement:Units|Unit System Requirements]]&lt;br /&gt;
* &#039;&#039;&#039;REQ-MEAS-UNI:&#039;&#039;&#039; [[Measurement:Canonical_Units|Canonical Units]]&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = AOWIS Documentation Structure&lt;br /&gt;
 | color = purple&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS documentation is organized into dedicated namespaces with clearly separated purposes.&lt;br /&gt;
&lt;br /&gt;
The [[Standard:Main_Page|Standard]] namespace contains the normative requirements and definitions that specify AOWIS compliance. The other namespaces contain the concepts, engineering knowledge, system architecture, operational guidance, implementation material, regional information, training, and supporting knowledge needed to plan, design, build, operate, maintain, extend, and develop AOWIS systems and the infrastructure they support.&lt;br /&gt;
&lt;br /&gt;
* [[Motivation:Main_Page|Motivation]] – Real-world problems, constraints, operating conditions, and practical needs that AOWIS is intended to address.&lt;br /&gt;
* [[Standard:Main_Page|Standard]] – The normative core of AOWIS. Defines requirements and definitions specifying what AOWIS-compliant systems MUST, SHOULD, or MAY do.&lt;br /&gt;
* [[Concepts:Main_Page|Concepts]] – Core concepts, design principles, terminology, and system-level ideas used throughout AOWIS.&lt;br /&gt;
* [[Architecture:Main_Page|Architecture]] – Overall system structure, including controllers, components, layers, interfaces, communication, data flows, responsibilities, and interactions between parts of an AOWIS system.&lt;br /&gt;
* [[Infrastructure:Main_Page|Infrastructure]] – Physical infrastructure, technologies, systems, and components that AOWIS is used to plan, design, model, build, monitor, control, operate, maintain, and extend.&lt;br /&gt;
* [[Measurement:Main_Page|Measurement]] – Physical quantities, units, measurement semantics, sensor and manual measurements, calibration, uncertainty, derived values, and the representation of measured information within AOWIS.&lt;br /&gt;
* [[Data:Main_Page|Data]] – Data models, schemas, identifiers, interchange formats, logging, synchronization, persistence, and data lifecycle rules.&lt;br /&gt;
* [[Operations:Main_Page|Operations]] – Monitoring, control, operational procedures, state management, fallback behaviour, decision-making, maintenance activities, and other processes involved in operating infrastructure.&lt;br /&gt;
* [[Modules:Main_Page|Modules]] – Reusable functional components that provide specific capabilities within AOWIS while integrating with the common system architecture and data model.&lt;br /&gt;
* [[Reference:Main_Page|Reference]] – Concrete implementations, engineering designs, example deployments, reference configurations, and validated patterns showing practical ways AOWIS systems can be built and used.&lt;br /&gt;
* [[Databases:Main_Page|Databases]] – Structured knowledge bases, registries, catalogues, and other organized information used by AOWIS and its implementations.&lt;br /&gt;
* [[Governance:Main_Page|Governance]] – Conformance, certification, review, auditing, versioning, licensing, trust, and organizational processes governing AOWIS and its development.&lt;br /&gt;
* [[Training:Main_Page|Training]] – Educational and practical material for operators, technicians, engineers, developers, contributors, communities, and others working with AOWIS and the infrastructure it supports.&lt;br /&gt;
* [[Regions:Main_Page|Regions]] – Place-specific information about geographic areas, including environmental, hydrological, climatic, socioeconomic, geological, infrastructure, water-resource, and field-project context.&lt;br /&gt;
* [[Geology:Main_Page|Geology]] – Geological, geomorphological, hydrogeological, hydrogeochemical, and geophysical knowledge relevant to water resources, groundwater occurrence and movement, subsurface investigation, borehole siting, and the understanding of local and regional geological conditions.&lt;br /&gt;
* [[External:Main_Page|External]] – External standards, projects, technologies, tools, organizations, and systems relevant to AOWIS, its interoperability, or the domains in which it is used.&lt;br /&gt;
&lt;br /&gt;
For a full overview, see the [[AOWIS:Table_of_Contents|Table of Contents]].&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Roadmap&lt;br /&gt;
 | color = grey&lt;br /&gt;
 | body =&lt;br /&gt;
[[File:Boring.jpg|250px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS has progressed beyond its initial conceptual phase. A substantial software foundation for modelling, simulating, visualizing, and eventually operating water infrastructure is under active development.&lt;br /&gt;
&lt;br /&gt;
The current software stack already includes:&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Shared infrastructure model&#039;&#039;&#039;&lt;br /&gt;
: A common, solver-independent representation of water infrastructure used throughout the AOWIS software stack.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-MODEL GitHub AOWIS-SERVER-MODEL]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Hydraulic and water-quality simulation&#039;&#039;&#039;&lt;br /&gt;
: EPANET integration for hydraulic and water-quality simulation, network import/export, controls, rules, diagnostics, and simulation results. Integration of &#039;&#039;&#039;EPANET-MSX&#039;&#039;&#039; is also being developed.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-EPANET GitHub AOWIS-SERVER-EPANET]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Network editor and monitoring interface&#039;&#039;&#039;&lt;br /&gt;
: A graphical application for creating, inspecting, simulating, and visualizing water networks, including geographic maps and terrain-aware 3D visualization.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-GUI GitHub AOWIS-SERVER-GUI]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Geographic and terrain infrastructure&#039;&#039;&#039;&lt;br /&gt;
: Mapping, elevation data, basemaps, terrain visualization, geographic placement, and local caching.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-MAP GitHub AOWIS-SERVER-MAP]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Local and standalone operation&#039;&#039;&#039;&lt;br /&gt;
: Support for deployments that do not depend on continuous Internet or cloud connectivity.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-Standalone GitHub AOWIS-SERVER-Standalone]&lt;br /&gt;
&lt;br /&gt;
The software remains under active development and should not yet be considered a complete production SCADA system.&lt;br /&gt;
&lt;br /&gt;
The next major stage is to connect the existing modelling and simulation environment to &#039;&#039;&#039;real infrastructure in continuous operation&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The AOWIS software platform is intended to develop into a complete open-source SCADA, infrastructure modelling, simulation, and operational management platform in which planning, live monitoring, control, historical data, maintenance, and simulation operate on the same shared infrastructure model.&lt;br /&gt;
&lt;br /&gt;
This includes telemetry, sensors and actuators, alarms and historian functions, local and remote control, automation with safe fallback behaviour, and model-assisted operation using measured and simulated system behaviour.&lt;br /&gt;
&lt;br /&gt;
EPANET currently provides the primary hydraulic and water-quality simulation engine, but AOWIS is not designed solely as an EPANET frontend. EPANET is one solver integrated into a broader, solver-independent architecture.&lt;br /&gt;
&lt;br /&gt;
The long-term objective is to connect the complete infrastructure lifecycle:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;survey and planning → engineering and simulation → construction → commissioning → monitoring → control → maintenance → analysis → expansion&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[[AOWIS:Roadmap|Read the full roadmap →]]&#039;&#039;&#039;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
| title = Community &amp;amp; Participation&lt;br /&gt;
| color = blue&lt;br /&gt;
| body =&lt;br /&gt;
&lt;br /&gt;
AOWIS is an open project, and participation is welcome from anyone interested in its goals — including engineers, developers, NGOs, operators, researchers, technicians, students, and people with practical experience in water and irrigation infrastructure.&lt;br /&gt;
&lt;br /&gt;
For &#039;&#039;&#039;discussion, planning, questions, documentation, infrastructure, field projects, standards, research, and other forms of participation&#039;&#039;&#039;, AOWIS uses &#039;&#039;&#039;Matrix&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The AOWIS Matrix server has several &#039;&#039;&#039;public spaces and rooms&#039;&#039;&#039; for different topics. Join those relevant to your interests. For general questions or help finding the right place, start here:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://matrix.to/#/#support:aowis.org AOWIS Support — #support:aowis.org]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Any Matrix account can join public AOWIS spaces and rooms.&lt;br /&gt;
&lt;br /&gt;
If you are new to Matrix:&lt;br /&gt;
&lt;br /&gt;
* [https://matrix.org/try-matrix/ Learn about Matrix and create an account]&lt;br /&gt;
* [https://element.io/ Element] — Matrix client for web, desktop, and mobile&lt;br /&gt;
* [https://fluffychat.im/ FluffyChat] — simple Matrix client for several platforms&lt;br /&gt;
&lt;br /&gt;
The same Matrix account can be used with different clients.&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;AOWIS Matrix Accounts&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Participants may also request an account on the AOWIS Matrix homeserver, giving them an ID such as &#039;&#039;&#039;@name:aowis.org&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
To reduce automated registrations and abuse, accounts are created on request. Please send a short introduction telling us who you are, what interests you about AOWIS, and where you would like to participate: [[File:Mtx.png|120px|frameless|alt=Email address for requesting an AOWIS Matrix account]]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Software Development&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Software development happens on &#039;&#039;&#039;GitHub&#039;&#039;&#039;. Bug reports, pull requests, source-code contributions, and repository-specific development discussions should use the appropriate repository.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://github.com/aowis-org AOWIS on GitHub]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Matrix is for the broader AOWIS community and participation that does not naturally belong in a GitHub repository.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Governance &amp;amp; Legitimacy&lt;br /&gt;
 | color = turquoise&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS includes a transparent governance model to ensure:&lt;br /&gt;
&lt;br /&gt;
* open participation  &lt;br /&gt;
* clear certification processes  &lt;br /&gt;
* stable versioning  &lt;br /&gt;
* long-term stewardship and continuity&lt;br /&gt;
&lt;br /&gt;
See: [[Governance:Main_Page|Governance]].&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Navigation&lt;br /&gt;
 | color = grey&lt;br /&gt;
 | body =&lt;br /&gt;
* [[AOWIS:Table_of_Contents|Table of Contents]]  &lt;br /&gt;
* [[Reference:Glossary|Glossary]]  &lt;br /&gt;
* [[Reference:FAQ|FAQ]]  &lt;br /&gt;
* [[Reference:Change_Log|Change Log]]  &lt;br /&gt;
&lt;br /&gt;
* [https://github.com/aowis-org GitHub]&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Partners&lt;br /&gt;
 | color = indigo&lt;br /&gt;
 | body = &lt;br /&gt;
[[File:Afriticgroup.webp|250px|frameless|center|link=https://afriticgroup.com/]]&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Samuel</name></author>
	</entry>
	<entry>
		<id>https://aowis.org/index.php?title=Main_Page&amp;diff=773</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://aowis.org/index.php?title=Main_Page&amp;diff=773"/>
		<updated>2026-09-24T20:37:59Z</updated>

		<summary type="html">&lt;p&gt;Samuel: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
&lt;br /&gt;
{{MainPageBanner}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Motivation&lt;br /&gt;
 | color = teal&lt;br /&gt;
 | body = &lt;br /&gt;
&lt;br /&gt;
[[File:Countryside.jpg|class=fullwidth|center]]&lt;br /&gt;
&lt;br /&gt;
In many rural and underserved regions, including parts of Africa, wells and pumps may exist while developing and operating a reliable distribution network remains difficult. Local initiatives can lack engineering capacity, trained personnel, suitable technology, and affordable tools for operating such infrastructure sustainably.&lt;br /&gt;
&lt;br /&gt;
This practical problem is an important motivation for AOWIS. AOWIS aims to make the engineering knowledge, technical foundations, software, and operational methods needed to develop and operate water infrastructure openly available and practically usable, while supporting local training and cooperation with experienced organizations and operators.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Why AOWIS is Needed&lt;br /&gt;
 | color = turquoise&lt;br /&gt;
 | body = &lt;br /&gt;
&lt;br /&gt;
[[File:Cooperation.jpg|400px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
Water and irrigation infrastructure must often be planned, built, expanded, and operated over many decades. In some places, existing infrastructure has become fragmented across different vendors, technologies, tools, and engineering approaches. In others, communities and organizations are building coherent water infrastructure for the first time and may have limited access to engineering capacity, technical guidance, suitable software, or established operational practices.&lt;br /&gt;
&lt;br /&gt;
AOWIS provides a shared open foundation for both situations. It brings together technical standards, engineering knowledge, software, reference implementations, operational guidance, and training to support the development of water infrastructure from initial planning and design through construction, operation, maintenance, and future expansion.&lt;br /&gt;
&lt;br /&gt;
The aim is to make infrastructure understandable, interoperable, maintainable, and extensible throughout its lifecycle, while reducing dependence on individual vendors, products, suppliers, or scarce specialist expertise.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Operating Conditions&lt;br /&gt;
 | color = lightblue&lt;br /&gt;
 | body =&lt;br /&gt;
&lt;br /&gt;
[[File:Village.jpg|250px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS is designed for environments where water infrastructure must remain useful and safe despite difficult technical and operational conditions. This is particularly important in rural and underserved regions, where reliable power, continuous connectivity, modern equipment, trained personnel, and specialist support cannot always be assumed.&lt;br /&gt;
&lt;br /&gt;
Typical conditions include:&lt;br /&gt;
&lt;br /&gt;
* unreliable or limited power supply&lt;br /&gt;
* intermittent or unavailable connectivity&lt;br /&gt;
* heterogeneous or aging equipment&lt;br /&gt;
* limited availability of trained technical personnel&lt;br /&gt;
* limited access to specialist engineering support&lt;br /&gt;
* the need for safe local operation without continuous remote supervision&lt;br /&gt;
&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Design Principles&lt;br /&gt;
 | color = lightblue&lt;br /&gt;
 | body =&lt;br /&gt;
&lt;br /&gt;
AOWIS addresses these conditions through principles including:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;offline-first operation&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;safe fallback behaviour&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;human-in-the-loop control&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;local autonomous operation&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;modular and extensible system design&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;shared infrastructure models&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;open interfaces and accessible technical documentation&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The goal is to make essential water infrastructure &#039;&#039;&#039;robust, understandable, maintainable, and locally operable&#039;&#039;&#039;, including where conventional assumptions about connectivity, technical resources, and institutional support do not hold.&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
| title = Software &amp;amp; Downloads&lt;br /&gt;
| color = green&lt;br /&gt;
| body =&lt;br /&gt;
[[File:GUI ky4 3d.png|400px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS includes an open-source software platform for &#039;&#039;&#039;modelling, simulating, visualizing, monitoring, and operating water infrastructure&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The current software includes a network editor and monitoring interface, hydraulic and water-quality simulation using [[External:EPANET:Main Page|EPANET]], geographic maps and terrain visualization, and support for local and standalone operation. Development of the AOWIS Controller is progressing toward a complete open-source SCADA and operational management platform..&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://download.aowis.org Download the AOWIS Controller (development snapshot)]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* [https://github.com/aowis-org Source code on GitHub]&lt;br /&gt;
* [[#Roadmap|Software development roadmap]]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Start Here&lt;br /&gt;
 | color = yellow&lt;br /&gt;
 | body =&lt;br /&gt;
If you are new to AOWIS, begin with:&lt;br /&gt;
&lt;br /&gt;
* [[Concepts:Design_Philosophy|Design Philosophy]]  &lt;br /&gt;
* [[Standard:Definitions|Definitions]]  &lt;br /&gt;
* [[Standard:Normative_Requirements|Normative Requirements]]  &lt;br /&gt;
* [[Modules:Module_Template|Module Template]]  &lt;br /&gt;
* [[AOWIS:Contributor_Guide_External|Contributor Guide - External]]&lt;br /&gt;
* [[AOWIS:Contributor_Guide_Internal|Contributor Guide - Internal]]&lt;br /&gt;
* [[AOWIS:Writing_Style_Guide|Writing Style Guide]]&lt;br /&gt;
* [[AOWIS:AI_Usage_Guide|AI Usage Guide]]&lt;br /&gt;
* [[AOWIS:Research_Form_Guide|Research Form Guide]]&lt;br /&gt;
* [[AOWIS:Naming_Convention_Specification|Naming Convention Specification]]&lt;br /&gt;
* [[AOWIS:Change_Log__Versioning|Change Log &amp;amp; Versioning]]&lt;br /&gt;
* [[AOWIS:Wiki|This Wiki]]&lt;br /&gt;
&lt;br /&gt;
These pages explain the foundations of AOWIS, how the AOWIS Standard is structured, and how to use and contribute to the project and its documentation.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = List of Requirement Pages&lt;br /&gt;
 | color = brown&lt;br /&gt;
 | body = &lt;br /&gt;
This index lists AOWIS pages that define normative requirements (MUST/SHOULD/MAY statements) and conformance rules.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Dev Rules&#039;&#039;&#039; — specs for writing and maintaining AOWIS&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;REQ-AI:&#039;&#039;&#039; [[AOWIS:AI_Usage_Guide|AI Usage Guide]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Technical Standard&#039;&#039;&#039; — system behavior and data models&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;REQ-MEAS, REQ-MEAS-UI:&#039;&#039;&#039; [[Measurement:Units|Unit System Requirements]]&lt;br /&gt;
* &#039;&#039;&#039;REQ-MEAS-UNI:&#039;&#039;&#039; [[Measurement:Canonical_Units|Canonical Units]]&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = AOWIS Documentation Structure&lt;br /&gt;
 | color = purple&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS documentation is organized into dedicated namespaces with clearly separated purposes.&lt;br /&gt;
&lt;br /&gt;
The [[Standard:Main_Page|Standard]] namespace contains the normative requirements and definitions that specify AOWIS compliance. The other namespaces contain the concepts, engineering knowledge, system architecture, operational guidance, implementation material, regional information, training, and supporting knowledge needed to plan, design, build, operate, maintain, extend, and develop AOWIS systems and the infrastructure they support.&lt;br /&gt;
&lt;br /&gt;
* [[Motivation:Main_Page|Motivation]] – Real-world problems, constraints, operating conditions, and practical needs that AOWIS is intended to address.&lt;br /&gt;
* [[Standard:Main_Page|Standard]] – The normative core of AOWIS. Defines requirements and definitions specifying what AOWIS-compliant systems MUST, SHOULD, or MAY do.&lt;br /&gt;
* [[Concepts:Main_Page|Concepts]] – Core concepts, design principles, terminology, and system-level ideas used throughout AOWIS.&lt;br /&gt;
* [[Architecture:Main_Page|Architecture]] – Overall system structure, including controllers, components, layers, interfaces, communication, data flows, responsibilities, and interactions between parts of an AOWIS system.&lt;br /&gt;
* [[Infrastructure:Main_Page|Infrastructure]] – Physical infrastructure, technologies, systems, and components that AOWIS is used to plan, design, model, build, monitor, control, operate, maintain, and extend.&lt;br /&gt;
* [[Measurement:Main_Page|Measurement]] – Physical quantities, units, measurement semantics, sensor and manual measurements, calibration, uncertainty, derived values, and the representation of measured information within AOWIS.&lt;br /&gt;
* [[Data:Main_Page|Data]] – Data models, schemas, identifiers, interchange formats, logging, synchronization, persistence, and data lifecycle rules.&lt;br /&gt;
* [[Operations:Main_Page|Operations]] – Monitoring, control, operational procedures, state management, fallback behaviour, decision-making, maintenance activities, and other processes involved in operating infrastructure.&lt;br /&gt;
* [[Modules:Main_Page|Modules]] – Reusable functional components that provide specific capabilities within AOWIS while integrating with the common system architecture and data model.&lt;br /&gt;
* [[Reference:Main_Page|Reference]] – Concrete implementations, engineering designs, example deployments, reference configurations, and validated patterns showing practical ways AOWIS systems can be built and used.&lt;br /&gt;
* [[Databases:Main_Page|Databases]] – Structured knowledge bases, registries, catalogues, and other organized information used by AOWIS and its implementations.&lt;br /&gt;
* [[Governance:Main_Page|Governance]] – Conformance, certification, review, auditing, versioning, licensing, trust, and organizational processes governing AOWIS and its development.&lt;br /&gt;
* [[Training:Main_Page|Training]] – Educational and practical material for operators, technicians, engineers, developers, contributors, communities, and others working with AOWIS and the infrastructure it supports.&lt;br /&gt;
* [[External:Main_Page|External]] – External standards, projects, technologies, tools, organizations, and systems relevant to AOWIS, its interoperability, or the domains in which it is used.&lt;br /&gt;
* [[Regions:Main_Page|Regions]] – Place-specific information about geographic areas, including environmental, hydrological, climatic, socioeconomic, geological, infrastructure, water-resource, and field-project context.&lt;br /&gt;
* [[Geology:Main_Page|Geology]] – Geological, geomorphological, hydrogeological, hydrogeochemical, and geophysical knowledge relevant to water resources, groundwater occurrence and movement, subsurface investigation, borehole siting, and the understanding of local and regional geological conditions.&lt;br /&gt;
&lt;br /&gt;
For a full overview, see the [[AOWIS:Table_of_Contents|Table of Contents]].&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Roadmap&lt;br /&gt;
 | color = grey&lt;br /&gt;
 | body =&lt;br /&gt;
[[File:Boring.jpg|250px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS has progressed beyond its initial conceptual phase. A substantial software foundation for modelling, simulating, visualizing, and eventually operating water infrastructure is under active development.&lt;br /&gt;
&lt;br /&gt;
The current software stack already includes:&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Shared infrastructure model&#039;&#039;&#039;&lt;br /&gt;
: A common, solver-independent representation of water infrastructure used throughout the AOWIS software stack.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-MODEL GitHub AOWIS-SERVER-MODEL]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Hydraulic and water-quality simulation&#039;&#039;&#039;&lt;br /&gt;
: EPANET integration for hydraulic and water-quality simulation, network import/export, controls, rules, diagnostics, and simulation results. Integration of &#039;&#039;&#039;EPANET-MSX&#039;&#039;&#039; is also being developed.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-EPANET GitHub AOWIS-SERVER-EPANET]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Network editor and monitoring interface&#039;&#039;&#039;&lt;br /&gt;
: A graphical application for creating, inspecting, simulating, and visualizing water networks, including geographic maps and terrain-aware 3D visualization.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-GUI GitHub AOWIS-SERVER-GUI]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Geographic and terrain infrastructure&#039;&#039;&#039;&lt;br /&gt;
: Mapping, elevation data, basemaps, terrain visualization, geographic placement, and local caching.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-MAP GitHub AOWIS-SERVER-MAP]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Local and standalone operation&#039;&#039;&#039;&lt;br /&gt;
: Support for deployments that do not depend on continuous Internet or cloud connectivity.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-Standalone GitHub AOWIS-SERVER-Standalone]&lt;br /&gt;
&lt;br /&gt;
The software remains under active development and should not yet be considered a complete production SCADA system.&lt;br /&gt;
&lt;br /&gt;
The next major stage is to connect the existing modelling and simulation environment to &#039;&#039;&#039;real infrastructure in continuous operation&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The AOWIS software platform is intended to develop into a complete open-source SCADA, infrastructure modelling, simulation, and operational management platform in which planning, live monitoring, control, historical data, maintenance, and simulation operate on the same shared infrastructure model.&lt;br /&gt;
&lt;br /&gt;
This includes telemetry, sensors and actuators, alarms and historian functions, local and remote control, automation with safe fallback behaviour, and model-assisted operation using measured and simulated system behaviour.&lt;br /&gt;
&lt;br /&gt;
EPANET currently provides the primary hydraulic and water-quality simulation engine, but AOWIS is not designed solely as an EPANET frontend. EPANET is one solver integrated into a broader, solver-independent architecture.&lt;br /&gt;
&lt;br /&gt;
The long-term objective is to connect the complete infrastructure lifecycle:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;survey and planning → engineering and simulation → construction → commissioning → monitoring → control → maintenance → analysis → expansion&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[[AOWIS:Roadmap|Read the full roadmap →]]&#039;&#039;&#039;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
| title = Community &amp;amp; Participation&lt;br /&gt;
| color = blue&lt;br /&gt;
| body =&lt;br /&gt;
&lt;br /&gt;
AOWIS is an open project, and participation is welcome from anyone interested in its goals — including engineers, developers, NGOs, operators, researchers, technicians, students, and people with practical experience in water and irrigation infrastructure.&lt;br /&gt;
&lt;br /&gt;
For &#039;&#039;&#039;discussion, planning, questions, documentation, infrastructure, field projects, standards, research, and other forms of participation&#039;&#039;&#039;, AOWIS uses &#039;&#039;&#039;Matrix&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The AOWIS Matrix server has several &#039;&#039;&#039;public spaces and rooms&#039;&#039;&#039; for different topics. Join those relevant to your interests. For general questions or help finding the right place, start here:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://matrix.to/#/#support:aowis.org AOWIS Support — #support:aowis.org]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Any Matrix account can join public AOWIS spaces and rooms.&lt;br /&gt;
&lt;br /&gt;
If you are new to Matrix:&lt;br /&gt;
&lt;br /&gt;
* [https://matrix.org/try-matrix/ Learn about Matrix and create an account]&lt;br /&gt;
* [https://element.io/ Element] — Matrix client for web, desktop, and mobile&lt;br /&gt;
* [https://fluffychat.im/ FluffyChat] — simple Matrix client for several platforms&lt;br /&gt;
&lt;br /&gt;
The same Matrix account can be used with different clients.&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;AOWIS Matrix Accounts&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Participants may also request an account on the AOWIS Matrix homeserver, giving them an ID such as &#039;&#039;&#039;@name:aowis.org&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
To reduce automated registrations and abuse, accounts are created on request. Please send a short introduction telling us who you are, what interests you about AOWIS, and where you would like to participate: [[File:Mtx.png|120px|frameless|alt=Email address for requesting an AOWIS Matrix account]]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Software Development&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Software development happens on &#039;&#039;&#039;GitHub&#039;&#039;&#039;. Bug reports, pull requests, source-code contributions, and repository-specific development discussions should use the appropriate repository.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://github.com/aowis-org AOWIS on GitHub]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Matrix is for the broader AOWIS community and participation that does not naturally belong in a GitHub repository.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Governance &amp;amp; Legitimacy&lt;br /&gt;
 | color = turquoise&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS includes a transparent governance model to ensure:&lt;br /&gt;
&lt;br /&gt;
* open participation  &lt;br /&gt;
* clear certification processes  &lt;br /&gt;
* stable versioning  &lt;br /&gt;
* long-term stewardship and continuity&lt;br /&gt;
&lt;br /&gt;
See: [[Governance:Main_Page|Governance]].&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Navigation&lt;br /&gt;
 | color = grey&lt;br /&gt;
 | body =&lt;br /&gt;
* [[AOWIS:Table_of_Contents|Table of Contents]]  &lt;br /&gt;
* [[Reference:Glossary|Glossary]]  &lt;br /&gt;
* [[Reference:FAQ|FAQ]]  &lt;br /&gt;
* [[Reference:Change_Log|Change Log]]  &lt;br /&gt;
&lt;br /&gt;
* [https://github.com/aowis-org GitHub]&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Partners&lt;br /&gt;
 | color = indigo&lt;br /&gt;
 | body = &lt;br /&gt;
[[File:Afriticgroup.webp|250px|frameless|center|link=https://afriticgroup.com/]]&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Samuel</name></author>
	</entry>
	<entry>
		<id>https://aowis.org/index.php?title=Main_Page&amp;diff=772</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://aowis.org/index.php?title=Main_Page&amp;diff=772"/>
		<updated>2026-09-24T20:37:08Z</updated>

		<summary type="html">&lt;p&gt;Samuel: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
&lt;br /&gt;
{{MainPageBanner}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Motivation&lt;br /&gt;
 | color = teal&lt;br /&gt;
 | body = &lt;br /&gt;
&lt;br /&gt;
[[File:Countryside.jpg|class=fullwidth|center]]&lt;br /&gt;
&lt;br /&gt;
In many rural and underserved regions, including parts of Africa, wells and pumps may exist while developing and operating a reliable distribution network remains difficult. Local initiatives can lack engineering capacity, trained personnel, suitable technology, and affordable tools for operating such infrastructure sustainably.&lt;br /&gt;
&lt;br /&gt;
This practical problem is an important motivation for AOWIS. AOWIS aims to make the engineering knowledge, technical foundations, software, and operational methods needed to develop and operate water infrastructure openly available and practically usable, while supporting local training and cooperation with experienced organizations and operators.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Why AOWIS is Needed&lt;br /&gt;
 | color = turquoise&lt;br /&gt;
 | body = &lt;br /&gt;
&lt;br /&gt;
[[File:Cooperation.jpg|400px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
Water and irrigation infrastructure must often be planned, built, expanded, and operated over many decades. In some places, existing infrastructure has become fragmented across different vendors, technologies, tools, and engineering approaches. In others, communities and organizations are building coherent water infrastructure for the first time and may have limited access to engineering capacity, technical guidance, suitable software, or established operational practices.&lt;br /&gt;
&lt;br /&gt;
AOWIS provides a shared open foundation for both situations. It brings together technical standards, engineering knowledge, software, reference implementations, operational guidance, and training to support the development of water infrastructure from initial planning and design through construction, operation, maintenance, and future expansion.&lt;br /&gt;
&lt;br /&gt;
The aim is to make infrastructure understandable, interoperable, maintainable, and extensible throughout its lifecycle, while reducing dependence on individual vendors, products, suppliers, or scarce specialist expertise.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Operating Conditions&lt;br /&gt;
 | color = lightblue&lt;br /&gt;
 | body =&lt;br /&gt;
&lt;br /&gt;
[[File:Village.jpg|250px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS is designed for environments where water infrastructure must remain useful and safe despite difficult technical and operational conditions. This is particularly important in rural and underserved regions, where reliable power, continuous connectivity, modern equipment, trained personnel, and specialist support cannot always be assumed.&lt;br /&gt;
&lt;br /&gt;
Typical conditions include:&lt;br /&gt;
&lt;br /&gt;
* unreliable or limited power supply&lt;br /&gt;
* intermittent or unavailable connectivity&lt;br /&gt;
* heterogeneous or aging equipment&lt;br /&gt;
* limited availability of trained technical personnel&lt;br /&gt;
* limited access to specialist engineering support&lt;br /&gt;
* the need for safe local operation without continuous remote supervision&lt;br /&gt;
&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Design Principles&lt;br /&gt;
 | color = lightblue&lt;br /&gt;
 | body =&lt;br /&gt;
&lt;br /&gt;
AOWIS addresses these conditions through principles including:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;offline-first operation&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;safe fallback behaviour&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;human-in-the-loop control&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;local autonomous operation&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;modular and extensible system design&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;shared infrastructure models&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;open interfaces and accessible technical documentation&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The goal is to make essential water infrastructure &#039;&#039;&#039;robust, understandable, maintainable, and locally operable&#039;&#039;&#039;, including where conventional assumptions about connectivity, technical resources, and institutional support do not hold.&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
| title = Software &amp;amp; Downloads&lt;br /&gt;
| color = green&lt;br /&gt;
| body =&lt;br /&gt;
[[File:GUI ky4 3d.png|400px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS includes an open-source software platform for &#039;&#039;&#039;modelling, simulating, visualizing, monitoring, and operating water infrastructure&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The current software includes a network editor and monitoring interface, hydraulic and water-quality simulation using [[External:EPANET:Main Page|EPANET]], geographic maps and terrain visualization, and support for local and standalone operation. Development of the AOWIS Controller is progressing toward a complete open-source SCADA and operational management platform..&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://download.aowis.org Download the AOWIS Controller (development snapshot)]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* [https://github.com/aowis-org Source code on GitHub]&lt;br /&gt;
* [[#Roadmap|Software development roadmap]]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Start Here&lt;br /&gt;
 | color = yellow&lt;br /&gt;
 | body =&lt;br /&gt;
If you are new to AOWIS, begin with:&lt;br /&gt;
&lt;br /&gt;
* [[Concepts:Design_Philosophy|Design Philosophy]]  &lt;br /&gt;
* [[Standard:Definitions|Definitions]]  &lt;br /&gt;
* [[Standard:Normative_Requirements|Normative Requirements]]  &lt;br /&gt;
* [[Modules:Module_Template|Module Template]]  &lt;br /&gt;
* [[AOWIS:Contributor_Guide_External|Contributor Guide - External]]&lt;br /&gt;
* [[AOWIS:Contributor_Guide_Internal|Contributor Guide - Internal]]&lt;br /&gt;
* [[AOWIS:Writing_Style_Guide|Writing Style Guide]]&lt;br /&gt;
* [[AOWIS:AI_Usage_Guide|AI Usage Guide]]&lt;br /&gt;
* [[AOWIS:Research_Form_Guide|Research Form Guide]]&lt;br /&gt;
* [[AOWIS:Naming_Convention_Specification|Naming Convention Specification]]&lt;br /&gt;
* [[AOWIS:Change_Log__Versioning|Change Log &amp;amp; Versioning]]&lt;br /&gt;
* [[AOWIS:Wiki|This Wiki]]&lt;br /&gt;
&lt;br /&gt;
These pages explain the foundations of AOWIS, how the AOWIS Standard is structured, and how to use and contribute to the project and its documentation.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = List of Requirement Pages&lt;br /&gt;
 | color = brown&lt;br /&gt;
 | body = &lt;br /&gt;
This index lists AOWIS pages that define normative requirements (MUST/SHOULD/MAY statements) and conformance rules.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Dev Rules&#039;&#039;&#039; — specs for writing and maintaining AOWIS&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;REQ-AI:&#039;&#039;&#039; [[AOWIS:AI_Usage_Guide|AI Usage Guide]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Technical Standard&#039;&#039;&#039; — system behavior and data models&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;REQ-MEAS, REQ-MEAS-UI:&#039;&#039;&#039; [[Measurement:Units|Unit System Requirements]]&lt;br /&gt;
* &#039;&#039;&#039;REQ-MEAS-UNI:&#039;&#039;&#039; [[Measurement:Canonical_Units|Canonical Units]]&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = AOWIS Documentation Structure&lt;br /&gt;
 | color = purple&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS documentation is organized into dedicated namespaces with clearly separated purposes.&lt;br /&gt;
&lt;br /&gt;
The [[Standard:Main_Page|Standard]] namespace contains the normative requirements that define AOWIS compliance. The other namespaces provide the motivation, concepts, engineering knowledge, architectures, operational models, implementation guidance, reference designs, training material, and supporting information needed to understand, implement, and operate AOWIS systems.&lt;br /&gt;
&lt;br /&gt;
* [[Motivation:Main_Page|Motivation]] – Causal justification of design requirements based on real-world failures, constraints, and operational realities.&lt;br /&gt;
* [[Standard:Main_Page|Standard]] – The normative core of AOWIS. Defines requirements and definitions specifying what AOWIS-compliant systems MUST, SHOULD, or MAY do.&lt;br /&gt;
* [[Concepts:Main_Page|Concepts]] – Core ideas, philosophy, rationale, and contextual understanding that explain AOWIS without prescribing a specific implementation.&lt;br /&gt;
* [[Architecture:Main_Page|Architecture]] – High-level system structure, including controllers, layers, communication, data flows, and their interactions.&lt;br /&gt;
* [[Infrastructure:Main_Page|Infrastructure]] – Physical technologies, systems, and components used in AOWIS deployments. Infrastructure pages describe classes of physical systems rather than specific implementation blueprints.&lt;br /&gt;
* [[Measurement:Main_Page|Measurement]] – Definition and handling of sensor data, manual measurements, calibration, uncertainty, and derived physical values.&lt;br /&gt;
* [[Data:Main_Page|Data]] – Data models, schemas, logging structures, synchronization formats, and data lifecycle rules.&lt;br /&gt;
* [[Operations:Main_Page|Operations]] – Runtime behavior, control logic, state transitions, fallback behavior, and decision-making during system operation.&lt;br /&gt;
* [[Modules:Main_Page|Modules]] – Reusable functional extensions that provide domain-specific capabilities within AOWIS.&lt;br /&gt;
* [[Reference:Main_Page|Reference]] – Non-normative concrete implementations, engineering blueprints, example deployments, and validated design patterns showing specific ways AOWIS systems may be built.&lt;br /&gt;
* [[Databases:Main_Page|Databases]] – Federated knowledge bases and structured supporting information used by AOWIS implementations.&lt;br /&gt;
* [[Governance:Main_Page|Governance]] – Certification, compliance, auditing, trust, licensing, versioning, and organizational governance.&lt;br /&gt;
* [[Training:Main_Page|Training]] – Operator education, technical training, field guidance, documentation literacy, and capacity building.&lt;br /&gt;
* [[External:Main_Page|External]] – External projects, standards, technologies, and systems that relate to or influence AOWIS.&lt;br /&gt;
&lt;br /&gt;
* [[Regions:Main_Page|Regions]] – Geographic, environmental, hydrological, climatic, socioeconomic, and infrastructure context for areas in which AOWIS is researched, planned, or deployed.&lt;br /&gt;
&lt;br /&gt;
* [[Geology:Main_Page|Geology]] - &lt;br /&gt;
&lt;br /&gt;
For a full overview, see the [[AOWIS:Table_of_Contents|Table of Contents]].&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Roadmap&lt;br /&gt;
 | color = grey&lt;br /&gt;
 | body =&lt;br /&gt;
[[File:Boring.jpg|250px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS has progressed beyond its initial conceptual phase. A substantial software foundation for modelling, simulating, visualizing, and eventually operating water infrastructure is under active development.&lt;br /&gt;
&lt;br /&gt;
The current software stack already includes:&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Shared infrastructure model&#039;&#039;&#039;&lt;br /&gt;
: A common, solver-independent representation of water infrastructure used throughout the AOWIS software stack.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-MODEL GitHub AOWIS-SERVER-MODEL]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Hydraulic and water-quality simulation&#039;&#039;&#039;&lt;br /&gt;
: EPANET integration for hydraulic and water-quality simulation, network import/export, controls, rules, diagnostics, and simulation results. Integration of &#039;&#039;&#039;EPANET-MSX&#039;&#039;&#039; is also being developed.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-EPANET GitHub AOWIS-SERVER-EPANET]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Network editor and monitoring interface&#039;&#039;&#039;&lt;br /&gt;
: A graphical application for creating, inspecting, simulating, and visualizing water networks, including geographic maps and terrain-aware 3D visualization.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-GUI GitHub AOWIS-SERVER-GUI]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Geographic and terrain infrastructure&#039;&#039;&#039;&lt;br /&gt;
: Mapping, elevation data, basemaps, terrain visualization, geographic placement, and local caching.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-MAP GitHub AOWIS-SERVER-MAP]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Local and standalone operation&#039;&#039;&#039;&lt;br /&gt;
: Support for deployments that do not depend on continuous Internet or cloud connectivity.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-Standalone GitHub AOWIS-SERVER-Standalone]&lt;br /&gt;
&lt;br /&gt;
The software remains under active development and should not yet be considered a complete production SCADA system.&lt;br /&gt;
&lt;br /&gt;
The next major stage is to connect the existing modelling and simulation environment to &#039;&#039;&#039;real infrastructure in continuous operation&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The AOWIS software platform is intended to develop into a complete open-source SCADA, infrastructure modelling, simulation, and operational management platform in which planning, live monitoring, control, historical data, maintenance, and simulation operate on the same shared infrastructure model.&lt;br /&gt;
&lt;br /&gt;
This includes telemetry, sensors and actuators, alarms and historian functions, local and remote control, automation with safe fallback behaviour, and model-assisted operation using measured and simulated system behaviour.&lt;br /&gt;
&lt;br /&gt;
EPANET currently provides the primary hydraulic and water-quality simulation engine, but AOWIS is not designed solely as an EPANET frontend. EPANET is one solver integrated into a broader, solver-independent architecture.&lt;br /&gt;
&lt;br /&gt;
The long-term objective is to connect the complete infrastructure lifecycle:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;survey and planning → engineering and simulation → construction → commissioning → monitoring → control → maintenance → analysis → expansion&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[[AOWIS:Roadmap|Read the full roadmap →]]&#039;&#039;&#039;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
| title = Community &amp;amp; Participation&lt;br /&gt;
| color = blue&lt;br /&gt;
| body =&lt;br /&gt;
&lt;br /&gt;
AOWIS is an open project, and participation is welcome from anyone interested in its goals — including engineers, developers, NGOs, operators, researchers, technicians, students, and people with practical experience in water and irrigation infrastructure.&lt;br /&gt;
&lt;br /&gt;
For &#039;&#039;&#039;discussion, planning, questions, documentation, infrastructure, field projects, standards, research, and other forms of participation&#039;&#039;&#039;, AOWIS uses &#039;&#039;&#039;Matrix&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The AOWIS Matrix server has several &#039;&#039;&#039;public spaces and rooms&#039;&#039;&#039; for different topics. Join those relevant to your interests. For general questions or help finding the right place, start here:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://matrix.to/#/#support:aowis.org AOWIS Support — #support:aowis.org]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Any Matrix account can join public AOWIS spaces and rooms.&lt;br /&gt;
&lt;br /&gt;
If you are new to Matrix:&lt;br /&gt;
&lt;br /&gt;
* [https://matrix.org/try-matrix/ Learn about Matrix and create an account]&lt;br /&gt;
* [https://element.io/ Element] — Matrix client for web, desktop, and mobile&lt;br /&gt;
* [https://fluffychat.im/ FluffyChat] — simple Matrix client for several platforms&lt;br /&gt;
&lt;br /&gt;
The same Matrix account can be used with different clients.&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;AOWIS Matrix Accounts&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Participants may also request an account on the AOWIS Matrix homeserver, giving them an ID such as &#039;&#039;&#039;@name:aowis.org&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
To reduce automated registrations and abuse, accounts are created on request. Please send a short introduction telling us who you are, what interests you about AOWIS, and where you would like to participate: [[File:Mtx.png|120px|frameless|alt=Email address for requesting an AOWIS Matrix account]]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Software Development&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Software development happens on &#039;&#039;&#039;GitHub&#039;&#039;&#039;. Bug reports, pull requests, source-code contributions, and repository-specific development discussions should use the appropriate repository.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://github.com/aowis-org AOWIS on GitHub]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Matrix is for the broader AOWIS community and participation that does not naturally belong in a GitHub repository.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Governance &amp;amp; Legitimacy&lt;br /&gt;
 | color = turquoise&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS includes a transparent governance model to ensure:&lt;br /&gt;
&lt;br /&gt;
* open participation  &lt;br /&gt;
* clear certification processes  &lt;br /&gt;
* stable versioning  &lt;br /&gt;
* long-term stewardship and continuity&lt;br /&gt;
&lt;br /&gt;
See: [[Governance:Main_Page|Governance]].&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Navigation&lt;br /&gt;
 | color = grey&lt;br /&gt;
 | body =&lt;br /&gt;
* [[AOWIS:Table_of_Contents|Table of Contents]]  &lt;br /&gt;
* [[Reference:Glossary|Glossary]]  &lt;br /&gt;
* [[Reference:FAQ|FAQ]]  &lt;br /&gt;
* [[Reference:Change_Log|Change Log]]  &lt;br /&gt;
&lt;br /&gt;
* [https://github.com/aowis-org GitHub]&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Partners&lt;br /&gt;
 | color = indigo&lt;br /&gt;
 | body = &lt;br /&gt;
[[File:Afriticgroup.webp|250px|frameless|center|link=https://afriticgroup.com/]]&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Samuel</name></author>
	</entry>
	<entry>
		<id>https://aowis.org/index.php?title=Main_Page&amp;diff=771</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://aowis.org/index.php?title=Main_Page&amp;diff=771"/>
		<updated>2026-09-24T20:04:01Z</updated>

		<summary type="html">&lt;p&gt;Samuel: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
&lt;br /&gt;
{{MainPageBanner}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Motivation&lt;br /&gt;
 | color = teal&lt;br /&gt;
 | body = &lt;br /&gt;
&lt;br /&gt;
[[File:Countryside.jpg|class=fullwidth|center]]&lt;br /&gt;
&lt;br /&gt;
In many rural and underserved regions, including parts of Africa, wells and pumps may exist while developing and operating a reliable distribution network remains difficult. Local initiatives can lack engineering capacity, trained personnel, suitable technology, and affordable tools for operating such infrastructure sustainably.&lt;br /&gt;
&lt;br /&gt;
This practical problem is an important motivation for AOWIS. AOWIS aims to make the engineering knowledge, technical foundations, software, and operational methods needed to develop and operate water infrastructure openly available and practically usable, while supporting local training and cooperation with experienced organizations and operators.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Why AOWIS is Needed&lt;br /&gt;
 | color = turquoise&lt;br /&gt;
 | body = &lt;br /&gt;
&lt;br /&gt;
[[File:Cooperation.jpg|400px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
Water and irrigation infrastructure must often be planned, built, expanded, and operated over many decades. In some places, existing infrastructure has become fragmented across different vendors, technologies, tools, and engineering approaches. In others, communities and organizations are building coherent water infrastructure for the first time and may have limited access to engineering capacity, technical guidance, suitable software, or established operational practices.&lt;br /&gt;
&lt;br /&gt;
AOWIS provides a shared open foundation for both situations. It brings together technical standards, engineering knowledge, software, reference implementations, operational guidance, and training to support the development of water infrastructure from initial planning and design through construction, operation, maintenance, and future expansion.&lt;br /&gt;
&lt;br /&gt;
The aim is to make infrastructure understandable, interoperable, maintainable, and extensible throughout its lifecycle, while reducing dependence on individual vendors, products, suppliers, or scarce specialist expertise.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Operating Conditions&lt;br /&gt;
 | color = lightblue&lt;br /&gt;
 | body =&lt;br /&gt;
&lt;br /&gt;
[[File:Village.jpg|250px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS is designed for environments where water infrastructure must remain useful and safe despite difficult technical and operational conditions. This is particularly important in rural and underserved regions, where reliable power, continuous connectivity, modern equipment, trained personnel, and specialist support cannot always be assumed.&lt;br /&gt;
&lt;br /&gt;
Typical conditions include:&lt;br /&gt;
&lt;br /&gt;
* unreliable or limited power supply&lt;br /&gt;
* intermittent or unavailable connectivity&lt;br /&gt;
* heterogeneous or aging equipment&lt;br /&gt;
* limited availability of trained technical personnel&lt;br /&gt;
* limited access to specialist engineering support&lt;br /&gt;
* the need for safe local operation without continuous remote supervision&lt;br /&gt;
&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Design Principles&lt;br /&gt;
 | color = lightblue&lt;br /&gt;
 | body =&lt;br /&gt;
&lt;br /&gt;
AOWIS addresses these conditions through principles including:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;offline-first operation&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;safe fallback behaviour&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;human-in-the-loop control&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;local autonomous operation&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;modular and extensible system design&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;shared infrastructure models&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;open interfaces and accessible technical documentation&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The goal is to make essential water infrastructure &#039;&#039;&#039;robust, understandable, maintainable, and locally operable&#039;&#039;&#039;, including where conventional assumptions about connectivity, technical resources, and institutional support do not hold.&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
| title = Software &amp;amp; Downloads&lt;br /&gt;
| color = green&lt;br /&gt;
| body =&lt;br /&gt;
[[File:GUI ky4 3d.png|400px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS includes an open-source software platform for &#039;&#039;&#039;modelling, simulating, visualizing, monitoring, and operating water infrastructure&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The current software includes a network editor and monitoring interface, hydraulic and water-quality simulation using [[External:EPANET:Main Page|EPANET]], geographic maps and terrain visualization, and support for local and standalone operation. Development of the AOWIS Controller is progressing toward a complete open-source SCADA and operational management platform..&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://download.aowis.org Download the AOWIS Controller (development snapshot)]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* [https://github.com/aowis-org Source code on GitHub]&lt;br /&gt;
* [[#Roadmap|Software development roadmap]]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Start Here&lt;br /&gt;
 | color = yellow&lt;br /&gt;
 | body =&lt;br /&gt;
If you are new to AOWIS, begin with:&lt;br /&gt;
&lt;br /&gt;
* [[Concepts:Design_Philosophy|Design Philosophy]]  &lt;br /&gt;
* [[Standard:Definitions|Definitions]]  &lt;br /&gt;
* [[Standard:Normative_Requirements|Normative Requirements]]  &lt;br /&gt;
* [[Modules:Module_Template|Module Template]]  &lt;br /&gt;
* [[AOWIS:Contributor_Guide_External|Contributor Guide - External]]&lt;br /&gt;
* [[AOWIS:Contributor_Guide_Internal|Contributor Guide - Internal]]&lt;br /&gt;
* [[AOWIS:Writing_Style_Guide|Writing Style Guide]]&lt;br /&gt;
* [[AOWIS:AI_Usage_Guide|AI Usage Guide]]&lt;br /&gt;
* [[AOWIS:Research_Form_Guide|Research Form Guide]]&lt;br /&gt;
* [[AOWIS:Naming_Convention_Specification|Naming Convention Specification]]&lt;br /&gt;
* [[AOWIS:Change_Log__Versioning|Change Log &amp;amp; Versioning]]&lt;br /&gt;
* [[AOWIS:Wiki|This Wiki]]&lt;br /&gt;
&lt;br /&gt;
These pages explain the foundations of AOWIS, how the AOWIS Standard is structured, and how to use and contribute to the project and its documentation.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = List of Requirement Pages&lt;br /&gt;
 | color = brown&lt;br /&gt;
 | body = &lt;br /&gt;
This index lists AOWIS pages that define normative requirements (MUST/SHOULD/MAY statements) and conformance rules.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Dev Rules&#039;&#039;&#039; — specs for writing and maintaining AOWIS&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;REQ-AI:&#039;&#039;&#039; [[AOWIS:AI_Usage_Guide|AI Usage Guide]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Technical Standard&#039;&#039;&#039; — system behavior and data models&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;REQ-MEAS, REQ-MEAS-UI:&#039;&#039;&#039; [[Measurement:Units|Unit System Requirements]]&lt;br /&gt;
* &#039;&#039;&#039;REQ-MEAS-UNI:&#039;&#039;&#039; [[Measurement:Canonical_Units|Canonical Units]]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = AOWIS Documentation Structure&lt;br /&gt;
 | color = purple&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS documentation is organized into dedicated namespaces with clearly separated purposes.&lt;br /&gt;
&lt;br /&gt;
The [[Standard:Main_Page|Standard]] namespace contains the normative requirements that define AOWIS compliance. The other namespaces provide the motivation, concepts, engineering knowledge, architectures, operational models, implementation guidance, reference designs, training material, and supporting information needed to understand, implement, and operate AOWIS systems.&lt;br /&gt;
&lt;br /&gt;
* [[Motivation:Main_Page|Motivation]] – Causal justification of design requirements based on real-world failures, constraints, and operational realities.&lt;br /&gt;
* [[Standard:Main_Page|Standard]] – The normative core of AOWIS. Defines requirements and definitions specifying what AOWIS-compliant systems MUST, SHOULD, or MAY do.&lt;br /&gt;
* [[Concepts:Main_Page|Concepts]] – Core ideas, philosophy, rationale, and contextual understanding that explain AOWIS without prescribing a specific implementation.&lt;br /&gt;
* [[Architecture:Main_Page|Architecture]] – High-level system structure, including controllers, layers, communication, data flows, and their interactions.&lt;br /&gt;
* [[Infrastructure:Main_Page|Infrastructure]] – Physical technologies, systems, and components used in AOWIS deployments. Infrastructure pages describe classes of physical systems rather than specific implementation blueprints.&lt;br /&gt;
* [[Measurement:Main_Page|Measurement]] – Definition and handling of sensor data, manual measurements, calibration, uncertainty, and derived physical values.&lt;br /&gt;
* [[Data:Main_Page|Data]] – Data models, schemas, logging structures, synchronization formats, and data lifecycle rules.&lt;br /&gt;
* [[Operations:Main_Page|Operations]] – Runtime behavior, control logic, state transitions, fallback behavior, and decision-making during system operation.&lt;br /&gt;
* [[Modules:Main_Page|Modules]] – Reusable functional extensions that provide domain-specific capabilities within AOWIS.&lt;br /&gt;
* [[Reference:Main_Page|Reference]] – Non-normative concrete implementations, engineering blueprints, example deployments, and validated design patterns showing specific ways AOWIS systems may be built.&lt;br /&gt;
* [[Databases:Main_Page|Databases]] – Federated knowledge bases and structured supporting information used by AOWIS implementations.&lt;br /&gt;
* [[Governance:Main_Page|Governance]] – Certification, compliance, auditing, trust, licensing, versioning, and organizational governance.&lt;br /&gt;
* [[Training:Main_Page|Training]] – Operator education, technical training, field guidance, documentation literacy, and capacity building.&lt;br /&gt;
* [[External:Main_Page|External]] – External projects, standards, technologies, and systems that relate to or influence AOWIS.&lt;br /&gt;
&lt;br /&gt;
* [[Regions:Main_Page|Regions]] – Geographic, environmental, hydrological, climatic, socioeconomic, and infrastructure context for areas in which AOWIS is researched, planned, or deployed.&lt;br /&gt;
&lt;br /&gt;
* [[Geology:Main_Page|Geology]] - &lt;br /&gt;
&lt;br /&gt;
For a full overview, see the [[AOWIS:Table_of_Contents|Table of Contents]].&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Roadmap&lt;br /&gt;
 | color = grey&lt;br /&gt;
 | body =&lt;br /&gt;
[[File:Boring.jpg|250px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS has progressed beyond its initial conceptual phase. A substantial software foundation for modelling, simulating, visualizing, and eventually operating water infrastructure is under active development.&lt;br /&gt;
&lt;br /&gt;
The current software stack already includes:&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Shared infrastructure model&#039;&#039;&#039;&lt;br /&gt;
: A common, solver-independent representation of water infrastructure used throughout the AOWIS software stack.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-MODEL GitHub AOWIS-SERVER-MODEL]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Hydraulic and water-quality simulation&#039;&#039;&#039;&lt;br /&gt;
: EPANET integration for hydraulic and water-quality simulation, network import/export, controls, rules, diagnostics, and simulation results. Integration of &#039;&#039;&#039;EPANET-MSX&#039;&#039;&#039; is also being developed.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-EPANET GitHub AOWIS-SERVER-EPANET]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Network editor and monitoring interface&#039;&#039;&#039;&lt;br /&gt;
: A graphical application for creating, inspecting, simulating, and visualizing water networks, including geographic maps and terrain-aware 3D visualization.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-GUI GitHub AOWIS-SERVER-GUI]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Geographic and terrain infrastructure&#039;&#039;&#039;&lt;br /&gt;
: Mapping, elevation data, basemaps, terrain visualization, geographic placement, and local caching.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-MAP GitHub AOWIS-SERVER-MAP]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Local and standalone operation&#039;&#039;&#039;&lt;br /&gt;
: Support for deployments that do not depend on continuous Internet or cloud connectivity.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-Standalone GitHub AOWIS-SERVER-Standalone]&lt;br /&gt;
&lt;br /&gt;
The software remains under active development and should not yet be considered a complete production SCADA system.&lt;br /&gt;
&lt;br /&gt;
The next major stage is to connect the existing modelling and simulation environment to &#039;&#039;&#039;real infrastructure in continuous operation&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The AOWIS software platform is intended to develop into a complete open-source SCADA, infrastructure modelling, simulation, and operational management platform in which planning, live monitoring, control, historical data, maintenance, and simulation operate on the same shared infrastructure model.&lt;br /&gt;
&lt;br /&gt;
This includes telemetry, sensors and actuators, alarms and historian functions, local and remote control, automation with safe fallback behaviour, and model-assisted operation using measured and simulated system behaviour.&lt;br /&gt;
&lt;br /&gt;
EPANET currently provides the primary hydraulic and water-quality simulation engine, but AOWIS is not designed solely as an EPANET frontend. EPANET is one solver integrated into a broader, solver-independent architecture.&lt;br /&gt;
&lt;br /&gt;
The long-term objective is to connect the complete infrastructure lifecycle:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;survey and planning → engineering and simulation → construction → commissioning → monitoring → control → maintenance → analysis → expansion&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[[AOWIS:Roadmap|Read the full roadmap →]]&#039;&#039;&#039;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
| title = Community &amp;amp; Participation&lt;br /&gt;
| color = blue&lt;br /&gt;
| body =&lt;br /&gt;
&lt;br /&gt;
AOWIS is an open project, and participation is welcome from anyone interested in its goals — including engineers, developers, NGOs, operators, researchers, technicians, students, and people with practical experience in water and irrigation infrastructure.&lt;br /&gt;
&lt;br /&gt;
For &#039;&#039;&#039;discussion, planning, questions, documentation, infrastructure, field projects, standards, research, and other forms of participation&#039;&#039;&#039;, AOWIS uses &#039;&#039;&#039;Matrix&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The AOWIS Matrix server has several &#039;&#039;&#039;public spaces and rooms&#039;&#039;&#039; for different topics. Join those relevant to your interests. For general questions or help finding the right place, start here:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://matrix.to/#/#support:aowis.org AOWIS Support — #support:aowis.org]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Any Matrix account can join public AOWIS spaces and rooms.&lt;br /&gt;
&lt;br /&gt;
If you are new to Matrix:&lt;br /&gt;
&lt;br /&gt;
* [https://matrix.org/try-matrix/ Learn about Matrix and create an account]&lt;br /&gt;
* [https://element.io/ Element] — Matrix client for web, desktop, and mobile&lt;br /&gt;
* [https://fluffychat.im/ FluffyChat] — simple Matrix client for several platforms&lt;br /&gt;
&lt;br /&gt;
The same Matrix account can be used with different clients.&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;AOWIS Matrix Accounts&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Participants may also request an account on the AOWIS Matrix homeserver, giving them an ID such as &#039;&#039;&#039;@name:aowis.org&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
To reduce automated registrations and abuse, accounts are created on request. Please send a short introduction telling us who you are, what interests you about AOWIS, and where you would like to participate: [[File:Mtx.png|120px|frameless|alt=Email address for requesting an AOWIS Matrix account]]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Software Development&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Software development happens on &#039;&#039;&#039;GitHub&#039;&#039;&#039;. Bug reports, pull requests, source-code contributions, and repository-specific development discussions should use the appropriate repository.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://github.com/aowis-org AOWIS on GitHub]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Matrix is for the broader AOWIS community and participation that does not naturally belong in a GitHub repository.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Governance &amp;amp; Legitimacy&lt;br /&gt;
 | color = turquoise&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS includes a transparent governance model to ensure:&lt;br /&gt;
&lt;br /&gt;
* open participation  &lt;br /&gt;
* clear certification processes  &lt;br /&gt;
* stable versioning  &lt;br /&gt;
* long-term stewardship and continuity&lt;br /&gt;
&lt;br /&gt;
See: [[Governance:Main_Page|Governance]].&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Navigation&lt;br /&gt;
 | color = grey&lt;br /&gt;
 | body =&lt;br /&gt;
* [[AOWIS:Table_of_Contents|Table of Contents]]  &lt;br /&gt;
* [[Reference:Glossary|Glossary]]  &lt;br /&gt;
* [[Reference:FAQ|FAQ]]  &lt;br /&gt;
* [[Reference:Change_Log|Change Log]]  &lt;br /&gt;
&lt;br /&gt;
* [https://github.com/aowis-org GitHub]&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Partners&lt;br /&gt;
 | color = indigo&lt;br /&gt;
 | body = &lt;br /&gt;
[[File:Afriticgroup.webp|250px|frameless|center|link=https://afriticgroup.com/]]&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Samuel</name></author>
	</entry>
	<entry>
		<id>https://aowis.org/index.php?title=Regions:Chad/Gu%C3%A9ra&amp;diff=770</id>
		<title>Regions:Chad/Guéra</title>
		<link rel="alternate" type="text/html" href="https://aowis.org/index.php?title=Regions:Chad/Gu%C3%A9ra&amp;diff=770"/>
		<updated>2026-09-24T16:44:16Z</updated>

		<summary type="html">&lt;p&gt;Samuel: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{AI-Generated&lt;br /&gt;
 | tool = ChatGPT&lt;br /&gt;
 | date = 2026-09-18&lt;br /&gt;
 | scope = full page&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Guéra&#039;&#039;&#039; is a province in central [[Regions:Chad|Chad]]. Its provincial capital is &#039;&#039;&#039;Mongo&#039;&#039;&#039;. The province includes the town of [[Regions:Chad/Guéra/Bitkine|Bitkine]], where AOWIS is currently involved in local water-supply work and groundwater assessment.&lt;br /&gt;
&lt;br /&gt;
Guéra lies across the transition from the Sahelian zone in the north to more humid Sudanian conditions in the south. Its mountainous crystalline basement, strongly seasonal rainfall, lack of permanent rivers, and highly variable groundwater productivity make water supply a major engineering challenge.&lt;br /&gt;
&lt;br /&gt;
== Geography and administration ==&lt;br /&gt;
&lt;br /&gt;
The 2022 &#039;&#039;Schéma Provincial d&#039;Aménagement du Territoire du Guéra&#039;&#039; gives an area of approximately &#039;&#039;&#039;61,279 km²&#039;&#039;&#039;. Following the 2021 administrative restructuring, the province consists of five departments:&amp;lt;ref name=&amp;quot;spat&amp;quot;&amp;gt;[https://apef-conservation.org/ressources-documentaires/ APEF / Republic of Chad, &#039;&#039;Schéma Provincial d&#039;Aménagement du Territoire du Guéra 2022–2032&#039;&#039;, 2022.]&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Guéra&#039;&#039;&#039;, capital Mongo;&lt;br /&gt;
* &#039;&#039;&#039;Abtouyour&#039;&#039;&#039;, capital [[Regions:Chad/Guéra/Bitkine|Bitkine]];&lt;br /&gt;
* &#039;&#039;&#039;Mangalmé&#039;&#039;&#039;, capital Mangalmé;&lt;br /&gt;
* &#039;&#039;&#039;Barh Signaka&#039;&#039;&#039;, capital Chinguil;&lt;br /&gt;
* &#039;&#039;&#039;Garada&#039;&#039;&#039;, capital Melfi.&lt;br /&gt;
&lt;br /&gt;
The same planning document gives a projected population of &#039;&#039;&#039;635,822 inhabitants in 2020&#039;&#039;&#039;, based on the 2009 national census and subsequent INSEED projections. The population is concentrated particularly in Guéra and Abtouyour.&amp;lt;ref name=&amp;quot;spat&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Terrain and surface water ==&lt;br /&gt;
&lt;br /&gt;
The landscape is dominated by plains interrupted by large granitic massifs, inselbergs, plateaus, and exposed bedrock.&lt;br /&gt;
&lt;br /&gt;
The central Chadian massif reaches some of its highest elevations in Guéra. The Mont Guéra reaches approximately &#039;&#039;&#039;1,613 m&#039;&#039;&#039; in the Bitkine area, while Mont Guédi east of Mongo reaches approximately &#039;&#039;&#039;1,506 m&#039;&#039;&#039;.&amp;lt;ref name=&amp;quot;spat&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
There are no major permanent rivers across most of the province. Surface drainage is dominated by seasonal watercourses, locally known as &#039;&#039;&#039;barhs&#039;&#039;&#039; or &#039;&#039;&#039;ouadis&#039;&#039;&#039;, which flow during the rainy season and may retain water temporarily in depressions and ponds.&lt;br /&gt;
&lt;br /&gt;
Seasonal streams draining the Guéra massif include the Bolong, Bang-Bang, Zilla, Zerzer and Melmele systems. Water from some northern catchments ultimately contributes toward Lake Fitri.&amp;lt;ref name=&amp;quot;spat&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Surface-water availability therefore changes strongly between the rainy and dry seasons, increasing dependence on groundwater for permanent water supply.&lt;br /&gt;
&lt;br /&gt;
== Climate ==&lt;br /&gt;
&lt;br /&gt;
Guéra spans several climatic zones. The north is predominantly Sahelian, the centre is Sahelo-Sudanian, and the southern part of the province approaches Sudanian conditions.&lt;br /&gt;
&lt;br /&gt;
The main seasons are:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;rainy season:&#039;&#039;&#039; approximately May to September;&lt;br /&gt;
* &#039;&#039;&#039;dry season:&#039;&#039;&#039; approximately October to April.&lt;br /&gt;
&lt;br /&gt;
July and August account for a large fraction of annual rainfall in hydrogeological studies of the central and northern part of the province.&amp;lt;ref name=&amp;quot;palomar&amp;quot;&amp;gt;[https://nextcloud.aowis.org/s/j7Gy7bMrFr5Gsew Pierre Palomar, &#039;&#039;Conceptualisation hydrogéologique et recommandations pour les prospections géophysiques et l&#039;implantation des forages — Province du Guéra, Tchad&#039;&#039;, SEVES, 2024.]&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The provincial planning document reports annual precipitation increasing broadly from around &#039;&#039;&#039;800 mm in the north to 1,100 mm in the south&#039;&#039;&#039;. Hydrogeological studies covering more restricted parts of Guéra use lower ranges, including approximately &#039;&#039;&#039;430–867 mm/year&#039;&#039;&#039;. These values refer to different geographic extents and datasets and should not be treated as a single uniform rainfall value for the province.&amp;lt;ref name=&amp;quot;spat&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;palomar&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Mean annual temperature is around &#039;&#039;&#039;28 °C&#039;&#039;&#039;, with high temperatures and long dry periods contributing to evaporation, drying of seasonal ponds, and strong seasonal pressure on water supplies.&amp;lt;ref name=&amp;quot;spat&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Geology ==&lt;br /&gt;
&lt;br /&gt;
Much of the Guéra massif consists of &#039;&#039;&#039;crystalline basement rock&#039;&#039;&#039;. Nouradine&#039;s regional hydrogeological work describes the study area as being dominated by granitoids and metamorphic rocks.&amp;lt;ref name=&amp;quot;nouradine&amp;quot;&amp;gt;[https://nextcloud.aowis.org/s/tCJgPAa2G6Lws83 Haroun Nouradine, &#039;&#039;Évaluation des ressources en eau dans les aquifères de socle dans la région du Guéra (Tchad) : combinaison d&#039;approches géologiques, hydrogéologiques, géophysiques, géochimiques et d&#039;apprentissage automatique&#039;&#039;, doctoral thesis, Sorbonne Université, 2023.]&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Around Bitkine, the basement includes:&lt;br /&gt;
&lt;br /&gt;
* granite;&lt;br /&gt;
* biotite granite;&lt;br /&gt;
* diorite;&lt;br /&gt;
* granodiorite;&lt;br /&gt;
* dolerite.&lt;br /&gt;
&lt;br /&gt;
The lithology strongly influences groundwater productivity. Biotite granites can develop permeable weathered and fractured horizons, while alteration of diorites, granodiorites and dolerites can produce larger amounts of clay, reducing infiltration and hydraulic conductivity.&amp;lt;ref name=&amp;quot;palomar&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Hydrogeology ==&lt;br /&gt;
&lt;br /&gt;
Groundwater in Guéra does not occur as one large continuous regional aquifer. The principal groundwater resources are associated with:&lt;br /&gt;
&lt;br /&gt;
* weathered crystalline basement;&lt;br /&gt;
* fractured and fissured bedrock;&lt;br /&gt;
* alluvial deposits;&lt;br /&gt;
* sands and sediments along seasonal drainage systems.&lt;br /&gt;
&lt;br /&gt;
The basement aquifers are therefore &#039;&#039;&#039;heterogeneous and discontinuous&#039;&#039;&#039;. Two boreholes located relatively close to one another can encounter substantially different conditions.&lt;br /&gt;
&lt;br /&gt;
A simplified basement-aquifer structure consists of:&lt;br /&gt;
&lt;br /&gt;
# superficial material and soil;&lt;br /&gt;
# weathered basement, or &#039;&#039;&#039;alterites&#039;&#039;&#039;;&lt;br /&gt;
# a fractured basement horizon;&lt;br /&gt;
# progressively less fractured competent bedrock at greater depth.&lt;br /&gt;
&lt;br /&gt;
The weathered horizon can provide substantial groundwater storage. Hydraulic transmissivity is often associated particularly with the upper fractured basement beneath it.&amp;lt;ref name=&amp;quot;nouradine&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Nouradine&#039;s regional analysis found that important water inflows commonly occur at approximately &#039;&#039;&#039;30–60 m depth&#039;&#039;&#039;. Productivity generally decreases where drilling continues far into relatively unfractured basement.&amp;lt;ref name=&amp;quot;nouradine&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Groundwater occurrence and borehole productivity depend on the combined effects of:&lt;br /&gt;
&lt;br /&gt;
* lithology;&lt;br /&gt;
* thickness and permeability of the weathered zone;&lt;br /&gt;
* development of the fractured horizon;&lt;br /&gt;
* geomorphology;&lt;br /&gt;
* recharge conditions;&lt;br /&gt;
* local drainage;&lt;br /&gt;
* position within the landscape.&lt;br /&gt;
&lt;br /&gt;
Low-lying areas and locations favourable to infiltration and recharge can provide substantially better groundwater conditions than nearby elevated or poorly weathered basement.&lt;br /&gt;
&lt;br /&gt;
== Borehole productivity ==&lt;br /&gt;
&lt;br /&gt;
Obtaining productive boreholes is a major difficulty in Guéra.&lt;br /&gt;
&lt;br /&gt;
Data analysed for boreholes constructed between 2010 and 2016 show that, among &#039;&#039;&#039;137 boreholes&#039;&#039;&#039; considered by the SEVES study:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;47%&#039;&#039;&#039; were unsuccessful during drilling and were not equipped;&lt;br /&gt;
* &#039;&#039;&#039;42%&#039;&#039;&#039; produced too little water for connection to an AEP water-supply network;&lt;br /&gt;
* only &#039;&#039;&#039;11%&#039;&#039;&#039; provided an exploitable yield of approximately &#039;&#039;&#039;4 m³/h for 8 hours per day&#039;&#039;&#039;.&amp;lt;ref name=&amp;quot;palomar&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The broader dataset analysed by Nouradine contains technical information from &#039;&#039;&#039;798 boreholes&#039;&#039;&#039;, together with approximately &#039;&#039;&#039;700 EM34 profiles&#039;&#039;&#039; and &#039;&#039;&#039;592 electrical-resistivity tomography profiles&#039;&#039;&#039;.&amp;lt;ref name=&amp;quot;nouradine&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;article&amp;quot;&amp;gt;[https://doi.org/10.1007/s10040-024-02766-2 H. Nouradine et al., &#039;&#039;Integrating geological, hydrogeological and geophysical data to identify groundwater resources in granitic basement areas (Guéra Massif, Chad)&#039;&#039;, Hydrogeology Journal 32, 759–784, 2024.]&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The mean borehole yield in the analysed basement-aquifer dataset is approximately &#039;&#039;&#039;1 m³/h&#039;&#039;&#039;. More productive boreholes are associated particularly with well-developed weathered and fractured horizons and favourable granite or biotite-granite formations.&amp;lt;ref name=&amp;quot;nouradine&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The difficulty is therefore not simply drilling deep enough. Successful groundwater development requires identifying favourable combinations of geology, weathering, fractures, topography and recharge.&lt;br /&gt;
&lt;br /&gt;
== Groundwater recharge ==&lt;br /&gt;
&lt;br /&gt;
Recharge is closely linked to the short rainy season.&lt;br /&gt;
&lt;br /&gt;
Direct infiltration across exposed or poorly permeable uplands can be limited, while runoff concentrates water in lower terrain, seasonal drainage channels, alluvial deposits and favourable fractured zones.&lt;br /&gt;
&lt;br /&gt;
The strongly seasonal rainfall regime means groundwater recharge can vary substantially between years. Quantifying long-term recharge remains an important uncertainty for sustainable groundwater development in Guéra.&amp;lt;ref name=&amp;quot;palomar&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Groundwater availability must therefore be evaluated not only in terms of instantaneous borehole yield, but also in terms of seasonal variation and sustainable long-term abstraction.&lt;br /&gt;
&lt;br /&gt;
== Groundwater quality ==&lt;br /&gt;
&lt;br /&gt;
Regional groundwater studies generally describe Guéra groundwater as relatively weakly mineralised compared with strongly saline groundwater systems elsewhere in Chad.&lt;br /&gt;
&lt;br /&gt;
Earlier regional studies cited by Nouradine reported dissolved mineral content generally below approximately &#039;&#039;&#039;250 mg/L&#039;&#039;&#039;, with bicarbonate-dominated groundwater and relatively low chloride and sulfate concentrations.&amp;lt;ref name=&amp;quot;nouradine&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
More recent geochemical work by Nouradine analysed &#039;&#039;&#039;211 groundwater samples&#039;&#039;&#039;, principally in and around the Mongo study area. Electrical conductivity ranged from approximately &#039;&#039;&#039;83 to 1,183 µS/cm&#039;&#039;&#039;, with an overall mean of approximately &#039;&#039;&#039;427 µS/cm&#039;&#039;&#039;.&amp;lt;ref name=&amp;quot;nouradine&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Mineralisation increases in some deeper or fractured groundwater systems. Mean conductivity in the study was approximately:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Water source&lt;br /&gt;
! Mean electrical conductivity&lt;br /&gt;
|-&lt;br /&gt;
| Shallow rural wells&lt;br /&gt;
| ~175 µS/cm&lt;br /&gt;
|-&lt;br /&gt;
| Rural boreholes in fractured basement&lt;br /&gt;
| ~445 µS/cm&lt;br /&gt;
|-&lt;br /&gt;
| Urban boreholes in fractured basement&lt;br /&gt;
| ~526 µS/cm&lt;br /&gt;
|-&lt;br /&gt;
| Wells intersecting both weathered and fractured horizons&lt;br /&gt;
| ~677 µS/cm&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
These figures describe the sampled areas around Mongo and should &#039;&#039;&#039;not&#039;&#039;&#039; be assumed to represent every groundwater body in Guéra.&lt;br /&gt;
&lt;br /&gt;
Local groundwater chemistry can vary strongly because individual boreholes may intercept different weathered zones, fracture systems and groundwater residence times.&lt;br /&gt;
&lt;br /&gt;
=== Local salinity ===&lt;br /&gt;
&lt;br /&gt;
Saline or noticeably mineralised boreholes occur locally in the Guéra region, including around Bitkine.&lt;br /&gt;
&lt;br /&gt;
AOWIS field observations around Bitkine indicate substantial local variation in water quality, with potable and saline groundwater occurring within the same general area. Some saline wells are unsuitable for drinking but remain in use for washing, construction, irrigation or other non-potable purposes.&lt;br /&gt;
&lt;br /&gt;
This local variability is consistent with the discontinuous fractured-basement hydrogeology of the area. Salinity at one borehole does not establish that neighbouring groundwater will have the same composition.&lt;br /&gt;
&lt;br /&gt;
Electrical conductivity, TDS and full chemical analysis should therefore be measured individually for each water point before treatment requirements or desalination systems are designed.&lt;br /&gt;
&lt;br /&gt;
== Bitkine and Abtouyour ==&lt;br /&gt;
&lt;br /&gt;
[[Regions:Chad/Guéra/Bitkine|Bitkine]] is the capital of the Abtouyour department and one of the main current areas of groundwater investigation in Guéra.&lt;br /&gt;
&lt;br /&gt;
The 2023–2024 work carried out by SEVES, UMR METIS of Sorbonne Université and ANTEA concentrated specifically on the Bitkine area. Pierre Palomar reinterpreted &#039;&#039;&#039;61 existing electrical-resistivity tomography surveys&#039;&#039;&#039; and associated borehole information to develop a local hydrogeological model and improve future borehole siting.&amp;lt;ref name=&amp;quot;palomar&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The work builds directly on Nouradine&#039;s regional research, which had concentrated particularly on the Mongo and Barlo areas.&lt;br /&gt;
&lt;br /&gt;
The Bitkine study found that geology and weathering pattern are critical to borehole performance and that geophysical anomalies cannot be interpreted reliably as fractures without considering the geological and geomorphological context.&amp;lt;ref name=&amp;quot;palomar&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
A dedicated page covers the local conditions and water-supply work:&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;[[Regions:Chad/Guéra/Bitkine]]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
== Water supply ==&lt;br /&gt;
&lt;br /&gt;
Much of Guéra depends on boreholes, hand-pumped wells and small piped drinking-water systems.&lt;br /&gt;
&lt;br /&gt;
The combination of low borehole yields, high drilling failure rates, seasonal demand and uncertain recharge makes reliable water supply difficult, particularly during the dry season.&lt;br /&gt;
&lt;br /&gt;
The provincial development plan reported substantial deficits in both rural hand-pump coverage and piped AEP systems.&amp;lt;ref name=&amp;quot;spat&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the Bitkine area, &#039;&#039;&#039;SEVES&#039;&#039;&#039; and its Chadian partner &#039;&#039;&#039;ADES&#039;&#039;&#039; have been working with the Commune of Bitkine and the regional water authorities through the &#039;&#039;&#039;REAVIA&#039;&#039;&#039; programme.&lt;br /&gt;
&lt;br /&gt;
Recent groundwater-development work reported by SEVES included:&lt;br /&gt;
&lt;br /&gt;
* a new borehole at Bitkine producing approximately &#039;&#039;&#039;6 m³/h&#039;&#039;&#039;;&lt;br /&gt;
* rehabilitation of a borehole at Koubo Adougoul producing approximately &#039;&#039;&#039;4 m³/h&#039;&#039;&#039;;&lt;br /&gt;
* a new borehole at Koubo Adougoul producing approximately &#039;&#039;&#039;7 m³/h&#039;&#039;&#039;.&amp;lt;ref name=&amp;quot;reavia&amp;quot;&amp;gt;[https://www.asso-seves.org/tchad-mobilisation-de-la-ressource-en-eau-pour-les-services-d-eau-potable-de.html SEVES, &#039;&#039;Mobilisation de la ressource en eau pour les services d&#039;eau potable de Bitkine et Koubo Adougoul dans la province du Guéra — REAVIA&#039;&#039;.]&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
These yields are high relative to many of the boreholes represented in the regional datasets.&lt;br /&gt;
&lt;br /&gt;
== Hydrogeological research ==&lt;br /&gt;
&lt;br /&gt;
Recent groundwater research in Guéra has produced an unusually large combined hydrogeological and geophysical dataset for a crystalline-basement region.&lt;br /&gt;
&lt;br /&gt;
=== Nouradine 2023 ===&lt;br /&gt;
&lt;br /&gt;
Haroun Nouradine&#039;s doctoral research combined:&lt;br /&gt;
&lt;br /&gt;
* geological analysis;&lt;br /&gt;
* hydrogeology;&lt;br /&gt;
* electrical geophysics;&lt;br /&gt;
* groundwater chemistry;&lt;br /&gt;
* stable isotopes;&lt;br /&gt;
* piezometric monitoring;&lt;br /&gt;
* machine learning.&lt;br /&gt;
&lt;br /&gt;
The underlying datasets include:&lt;br /&gt;
&lt;br /&gt;
* 798 boreholes;&lt;br /&gt;
* 700 EM34 profiles;&lt;br /&gt;
* 592 electrical-resistivity tomography profiles;&lt;br /&gt;
* 211 geochemical and isotopic groundwater samples.&lt;br /&gt;
&lt;br /&gt;
The work established a conceptual model of Guéra&#039;s crystalline-basement aquifers and identified factors controlling borehole productivity.&amp;lt;ref name=&amp;quot;nouradine&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Full thesis:&#039;&#039;&#039;  &lt;br /&gt;
:[https://nextcloud.aowis.org/s/tCJgPAa2G6Lws83 &#039;&#039;Évaluation des ressources en eau dans les aquifères de socle dans la région du Guéra (Tchad)&#039;&#039;, Haroun Nouradine, 2023]&lt;br /&gt;
&lt;br /&gt;
=== Palomar / SEVES 2024 ===&lt;br /&gt;
&lt;br /&gt;
Pierre Palomar&#039;s study, carried out within SEVES in collaboration with Sorbonne Université&#039;s UMR METIS and ANTEA, applies the regional hydrogeological model specifically to the Bitkine area.&lt;br /&gt;
&lt;br /&gt;
It includes:&lt;br /&gt;
&lt;br /&gt;
* a review of basement-aquifer hydrogeology;&lt;br /&gt;
* evaluation of geophysical prospecting methods;&lt;br /&gt;
* reinterpretation of existing ERT surveys;&lt;br /&gt;
* comparison with borehole results;&lt;br /&gt;
* a hydrogeological conceptual model for the Bitkine area;&lt;br /&gt;
* recommendations for future groundwater prospecting and borehole siting.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Full report:&#039;&#039;&#039;  &lt;br /&gt;
:[https://nextcloud.aowis.org/s/j7Gy7bMrFr5Gsew &#039;&#039;Conceptualisation hydrogéologique et recommandations pour les prospections géophysiques et l&#039;implantation des forages — Province du Guéra, Tchad&#039;&#039;, Pierre Palomar / SEVES, 2024]&lt;br /&gt;
&lt;br /&gt;
== AOWIS work ==&lt;br /&gt;
&lt;br /&gt;
Guéra is a current AOWIS field region, with initial work concentrated around [[Regions:Chad/Guéra/Bitkine|Bitkine]].&lt;br /&gt;
&lt;br /&gt;
Current work includes documentation of existing water points, seasonal borehole yields, water quality, groundwater salinity, opportunities for cooperation between existing well operators, and options for additional storage, treatment and distribution infrastructure.&lt;br /&gt;
&lt;br /&gt;
The combination of highly variable groundwater productivity and local differences in groundwater chemistry makes the region particularly relevant to integrated water-resource monitoring and planning.&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== External resources ==&lt;br /&gt;
&lt;br /&gt;
* [https://nextcloud.aowis.org/s/tCJgPAa2G6Lws83 Nouradine 2023 doctoral thesis — AOWIS-hosted PDF]&lt;br /&gt;
* [https://nextcloud.aowis.org/s/j7Gy7bMrFr5Gsew Palomar / SEVES Guéra and Bitkine hydrogeology report — AOWIS-hosted PDF]&lt;br /&gt;
* [https://doi.org/10.1007/s10040-024-02766-2 Nouradine et al. 2024 — Hydrogeology Journal]&lt;br /&gt;
* [https://www.asso-seves.org/implantation-des-forages-dans-la-province-du-guera-autchad.html SEVES — hydrogeology and borehole siting in Guéra]&lt;br /&gt;
* [https://apef-conservation.org/ressources-documentaires/ Schéma Provincial d&#039;Aménagement du Territoire du Guéra 2022–2032]&lt;br /&gt;
&lt;br /&gt;
[[Category:Chad]]&lt;br /&gt;
[[Category:Guéra]]&lt;br /&gt;
[[Category:Groundwater]]&lt;br /&gt;
[[Category:Hydrogeology]]&lt;br /&gt;
[[Category:Water supply]]&lt;/div&gt;</summary>
		<author><name>Samuel</name></author>
	</entry>
	<entry>
		<id>https://aowis.org/index.php?title=Regions:Chad/Gu%C3%A9ra&amp;diff=769</id>
		<title>Regions:Chad/Guéra</title>
		<link rel="alternate" type="text/html" href="https://aowis.org/index.php?title=Regions:Chad/Gu%C3%A9ra&amp;diff=769"/>
		<updated>2026-09-24T15:57:50Z</updated>

		<summary type="html">&lt;p&gt;Samuel: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
BASE: {{BASEPAGENAME}}&lt;br /&gt;
SUB: {{SUBPAGENAME}}&lt;br /&gt;
PARENT: [[../]]&lt;br /&gt;
&lt;br /&gt;
{{AI-Generated&lt;br /&gt;
 | tool = ChatGPT&lt;br /&gt;
 | date = 2026-09-18&lt;br /&gt;
 | scope = full page&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Guéra&#039;&#039;&#039; is a province in central [[Regions:Chad|Chad]]. Its provincial capital is &#039;&#039;&#039;Mongo&#039;&#039;&#039;. The province includes the town of [[Regions:Chad/Guéra/Bitkine|Bitkine]], where AOWIS is currently involved in local water-supply work and groundwater assessment.&lt;br /&gt;
&lt;br /&gt;
Guéra lies across the transition from the Sahelian zone in the north to more humid Sudanian conditions in the south. Its mountainous crystalline basement, strongly seasonal rainfall, lack of permanent rivers, and highly variable groundwater productivity make water supply a major engineering challenge.&lt;br /&gt;
&lt;br /&gt;
== Geography and administration ==&lt;br /&gt;
&lt;br /&gt;
The 2022 &#039;&#039;Schéma Provincial d&#039;Aménagement du Territoire du Guéra&#039;&#039; gives an area of approximately &#039;&#039;&#039;61,279 km²&#039;&#039;&#039;. Following the 2021 administrative restructuring, the province consists of five departments:&amp;lt;ref name=&amp;quot;spat&amp;quot;&amp;gt;[https://apef-conservation.org/ressources-documentaires/ APEF / Republic of Chad, &#039;&#039;Schéma Provincial d&#039;Aménagement du Territoire du Guéra 2022–2032&#039;&#039;, 2022.]&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Guéra&#039;&#039;&#039;, capital Mongo;&lt;br /&gt;
* &#039;&#039;&#039;Abtouyour&#039;&#039;&#039;, capital [[Regions:Chad/Guéra/Bitkine|Bitkine]];&lt;br /&gt;
* &#039;&#039;&#039;Mangalmé&#039;&#039;&#039;, capital Mangalmé;&lt;br /&gt;
* &#039;&#039;&#039;Barh Signaka&#039;&#039;&#039;, capital Chinguil;&lt;br /&gt;
* &#039;&#039;&#039;Garada&#039;&#039;&#039;, capital Melfi.&lt;br /&gt;
&lt;br /&gt;
The same planning document gives a projected population of &#039;&#039;&#039;635,822 inhabitants in 2020&#039;&#039;&#039;, based on the 2009 national census and subsequent INSEED projections. The population is concentrated particularly in Guéra and Abtouyour.&amp;lt;ref name=&amp;quot;spat&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Terrain and surface water ==&lt;br /&gt;
&lt;br /&gt;
The landscape is dominated by plains interrupted by large granitic massifs, inselbergs, plateaus, and exposed bedrock.&lt;br /&gt;
&lt;br /&gt;
The central Chadian massif reaches some of its highest elevations in Guéra. The Mont Guéra reaches approximately &#039;&#039;&#039;1,613 m&#039;&#039;&#039; in the Bitkine area, while Mont Guédi east of Mongo reaches approximately &#039;&#039;&#039;1,506 m&#039;&#039;&#039;.&amp;lt;ref name=&amp;quot;spat&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
There are no major permanent rivers across most of the province. Surface drainage is dominated by seasonal watercourses, locally known as &#039;&#039;&#039;barhs&#039;&#039;&#039; or &#039;&#039;&#039;ouadis&#039;&#039;&#039;, which flow during the rainy season and may retain water temporarily in depressions and ponds.&lt;br /&gt;
&lt;br /&gt;
Seasonal streams draining the Guéra massif include the Bolong, Bang-Bang, Zilla, Zerzer and Melmele systems. Water from some northern catchments ultimately contributes toward Lake Fitri.&amp;lt;ref name=&amp;quot;spat&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Surface-water availability therefore changes strongly between the rainy and dry seasons, increasing dependence on groundwater for permanent water supply.&lt;br /&gt;
&lt;br /&gt;
== Climate ==&lt;br /&gt;
&lt;br /&gt;
Guéra spans several climatic zones. The north is predominantly Sahelian, the centre is Sahelo-Sudanian, and the southern part of the province approaches Sudanian conditions.&lt;br /&gt;
&lt;br /&gt;
The main seasons are:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;rainy season:&#039;&#039;&#039; approximately May to September;&lt;br /&gt;
* &#039;&#039;&#039;dry season:&#039;&#039;&#039; approximately October to April.&lt;br /&gt;
&lt;br /&gt;
July and August account for a large fraction of annual rainfall in hydrogeological studies of the central and northern part of the province.&amp;lt;ref name=&amp;quot;palomar&amp;quot;&amp;gt;[https://nextcloud.aowis.org/s/j7Gy7bMrFr5Gsew Pierre Palomar, &#039;&#039;Conceptualisation hydrogéologique et recommandations pour les prospections géophysiques et l&#039;implantation des forages — Province du Guéra, Tchad&#039;&#039;, SEVES, 2024.]&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The provincial planning document reports annual precipitation increasing broadly from around &#039;&#039;&#039;800 mm in the north to 1,100 mm in the south&#039;&#039;&#039;. Hydrogeological studies covering more restricted parts of Guéra use lower ranges, including approximately &#039;&#039;&#039;430–867 mm/year&#039;&#039;&#039;. These values refer to different geographic extents and datasets and should not be treated as a single uniform rainfall value for the province.&amp;lt;ref name=&amp;quot;spat&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;palomar&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Mean annual temperature is around &#039;&#039;&#039;28 °C&#039;&#039;&#039;, with high temperatures and long dry periods contributing to evaporation, drying of seasonal ponds, and strong seasonal pressure on water supplies.&amp;lt;ref name=&amp;quot;spat&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Geology ==&lt;br /&gt;
&lt;br /&gt;
Much of the Guéra massif consists of &#039;&#039;&#039;crystalline basement rock&#039;&#039;&#039;. Nouradine&#039;s regional hydrogeological work describes the study area as being dominated by granitoids and metamorphic rocks.&amp;lt;ref name=&amp;quot;nouradine&amp;quot;&amp;gt;[https://nextcloud.aowis.org/s/tCJgPAa2G6Lws83 Haroun Nouradine, &#039;&#039;Évaluation des ressources en eau dans les aquifères de socle dans la région du Guéra (Tchad) : combinaison d&#039;approches géologiques, hydrogéologiques, géophysiques, géochimiques et d&#039;apprentissage automatique&#039;&#039;, doctoral thesis, Sorbonne Université, 2023.]&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Around Bitkine, the basement includes:&lt;br /&gt;
&lt;br /&gt;
* granite;&lt;br /&gt;
* biotite granite;&lt;br /&gt;
* diorite;&lt;br /&gt;
* granodiorite;&lt;br /&gt;
* dolerite.&lt;br /&gt;
&lt;br /&gt;
The lithology strongly influences groundwater productivity. Biotite granites can develop permeable weathered and fractured horizons, while alteration of diorites, granodiorites and dolerites can produce larger amounts of clay, reducing infiltration and hydraulic conductivity.&amp;lt;ref name=&amp;quot;palomar&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Hydrogeology ==&lt;br /&gt;
&lt;br /&gt;
Groundwater in Guéra does not occur as one large continuous regional aquifer. The principal groundwater resources are associated with:&lt;br /&gt;
&lt;br /&gt;
* weathered crystalline basement;&lt;br /&gt;
* fractured and fissured bedrock;&lt;br /&gt;
* alluvial deposits;&lt;br /&gt;
* sands and sediments along seasonal drainage systems.&lt;br /&gt;
&lt;br /&gt;
The basement aquifers are therefore &#039;&#039;&#039;heterogeneous and discontinuous&#039;&#039;&#039;. Two boreholes located relatively close to one another can encounter substantially different conditions.&lt;br /&gt;
&lt;br /&gt;
A simplified basement-aquifer structure consists of:&lt;br /&gt;
&lt;br /&gt;
# superficial material and soil;&lt;br /&gt;
# weathered basement, or &#039;&#039;&#039;alterites&#039;&#039;&#039;;&lt;br /&gt;
# a fractured basement horizon;&lt;br /&gt;
# progressively less fractured competent bedrock at greater depth.&lt;br /&gt;
&lt;br /&gt;
The weathered horizon can provide substantial groundwater storage. Hydraulic transmissivity is often associated particularly with the upper fractured basement beneath it.&amp;lt;ref name=&amp;quot;nouradine&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Nouradine&#039;s regional analysis found that important water inflows commonly occur at approximately &#039;&#039;&#039;30–60 m depth&#039;&#039;&#039;. Productivity generally decreases where drilling continues far into relatively unfractured basement.&amp;lt;ref name=&amp;quot;nouradine&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Groundwater occurrence and borehole productivity depend on the combined effects of:&lt;br /&gt;
&lt;br /&gt;
* lithology;&lt;br /&gt;
* thickness and permeability of the weathered zone;&lt;br /&gt;
* development of the fractured horizon;&lt;br /&gt;
* geomorphology;&lt;br /&gt;
* recharge conditions;&lt;br /&gt;
* local drainage;&lt;br /&gt;
* position within the landscape.&lt;br /&gt;
&lt;br /&gt;
Low-lying areas and locations favourable to infiltration and recharge can provide substantially better groundwater conditions than nearby elevated or poorly weathered basement.&lt;br /&gt;
&lt;br /&gt;
== Borehole productivity ==&lt;br /&gt;
&lt;br /&gt;
Obtaining productive boreholes is a major difficulty in Guéra.&lt;br /&gt;
&lt;br /&gt;
Data analysed for boreholes constructed between 2010 and 2016 show that, among &#039;&#039;&#039;137 boreholes&#039;&#039;&#039; considered by the SEVES study:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;47%&#039;&#039;&#039; were unsuccessful during drilling and were not equipped;&lt;br /&gt;
* &#039;&#039;&#039;42%&#039;&#039;&#039; produced too little water for connection to an AEP water-supply network;&lt;br /&gt;
* only &#039;&#039;&#039;11%&#039;&#039;&#039; provided an exploitable yield of approximately &#039;&#039;&#039;4 m³/h for 8 hours per day&#039;&#039;&#039;.&amp;lt;ref name=&amp;quot;palomar&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The broader dataset analysed by Nouradine contains technical information from &#039;&#039;&#039;798 boreholes&#039;&#039;&#039;, together with approximately &#039;&#039;&#039;700 EM34 profiles&#039;&#039;&#039; and &#039;&#039;&#039;592 electrical-resistivity tomography profiles&#039;&#039;&#039;.&amp;lt;ref name=&amp;quot;nouradine&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;article&amp;quot;&amp;gt;[https://doi.org/10.1007/s10040-024-02766-2 H. Nouradine et al., &#039;&#039;Integrating geological, hydrogeological and geophysical data to identify groundwater resources in granitic basement areas (Guéra Massif, Chad)&#039;&#039;, Hydrogeology Journal 32, 759–784, 2024.]&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The mean borehole yield in the analysed basement-aquifer dataset is approximately &#039;&#039;&#039;1 m³/h&#039;&#039;&#039;. More productive boreholes are associated particularly with well-developed weathered and fractured horizons and favourable granite or biotite-granite formations.&amp;lt;ref name=&amp;quot;nouradine&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The difficulty is therefore not simply drilling deep enough. Successful groundwater development requires identifying favourable combinations of geology, weathering, fractures, topography and recharge.&lt;br /&gt;
&lt;br /&gt;
== Groundwater recharge ==&lt;br /&gt;
&lt;br /&gt;
Recharge is closely linked to the short rainy season.&lt;br /&gt;
&lt;br /&gt;
Direct infiltration across exposed or poorly permeable uplands can be limited, while runoff concentrates water in lower terrain, seasonal drainage channels, alluvial deposits and favourable fractured zones.&lt;br /&gt;
&lt;br /&gt;
The strongly seasonal rainfall regime means groundwater recharge can vary substantially between years. Quantifying long-term recharge remains an important uncertainty for sustainable groundwater development in Guéra.&amp;lt;ref name=&amp;quot;palomar&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Groundwater availability must therefore be evaluated not only in terms of instantaneous borehole yield, but also in terms of seasonal variation and sustainable long-term abstraction.&lt;br /&gt;
&lt;br /&gt;
== Groundwater quality ==&lt;br /&gt;
&lt;br /&gt;
Regional groundwater studies generally describe Guéra groundwater as relatively weakly mineralised compared with strongly saline groundwater systems elsewhere in Chad.&lt;br /&gt;
&lt;br /&gt;
Earlier regional studies cited by Nouradine reported dissolved mineral content generally below approximately &#039;&#039;&#039;250 mg/L&#039;&#039;&#039;, with bicarbonate-dominated groundwater and relatively low chloride and sulfate concentrations.&amp;lt;ref name=&amp;quot;nouradine&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
More recent geochemical work by Nouradine analysed &#039;&#039;&#039;211 groundwater samples&#039;&#039;&#039;, principally in and around the Mongo study area. Electrical conductivity ranged from approximately &#039;&#039;&#039;83 to 1,183 µS/cm&#039;&#039;&#039;, with an overall mean of approximately &#039;&#039;&#039;427 µS/cm&#039;&#039;&#039;.&amp;lt;ref name=&amp;quot;nouradine&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Mineralisation increases in some deeper or fractured groundwater systems. Mean conductivity in the study was approximately:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Water source&lt;br /&gt;
! Mean electrical conductivity&lt;br /&gt;
|-&lt;br /&gt;
| Shallow rural wells&lt;br /&gt;
| ~175 µS/cm&lt;br /&gt;
|-&lt;br /&gt;
| Rural boreholes in fractured basement&lt;br /&gt;
| ~445 µS/cm&lt;br /&gt;
|-&lt;br /&gt;
| Urban boreholes in fractured basement&lt;br /&gt;
| ~526 µS/cm&lt;br /&gt;
|-&lt;br /&gt;
| Wells intersecting both weathered and fractured horizons&lt;br /&gt;
| ~677 µS/cm&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
These figures describe the sampled areas around Mongo and should &#039;&#039;&#039;not&#039;&#039;&#039; be assumed to represent every groundwater body in Guéra.&lt;br /&gt;
&lt;br /&gt;
Local groundwater chemistry can vary strongly because individual boreholes may intercept different weathered zones, fracture systems and groundwater residence times.&lt;br /&gt;
&lt;br /&gt;
=== Local salinity ===&lt;br /&gt;
&lt;br /&gt;
Saline or noticeably mineralised boreholes occur locally in the Guéra region, including around Bitkine.&lt;br /&gt;
&lt;br /&gt;
AOWIS field observations around Bitkine indicate substantial local variation in water quality, with potable and saline groundwater occurring within the same general area. Some saline wells are unsuitable for drinking but remain in use for washing, construction, irrigation or other non-potable purposes.&lt;br /&gt;
&lt;br /&gt;
This local variability is consistent with the discontinuous fractured-basement hydrogeology of the area. Salinity at one borehole does not establish that neighbouring groundwater will have the same composition.&lt;br /&gt;
&lt;br /&gt;
Electrical conductivity, TDS and full chemical analysis should therefore be measured individually for each water point before treatment requirements or desalination systems are designed.&lt;br /&gt;
&lt;br /&gt;
== Bitkine and Abtouyour ==&lt;br /&gt;
&lt;br /&gt;
[[Regions:Chad/Guéra/Bitkine|Bitkine]] is the capital of the Abtouyour department and one of the main current areas of groundwater investigation in Guéra.&lt;br /&gt;
&lt;br /&gt;
The 2023–2024 work carried out by SEVES, UMR METIS of Sorbonne Université and ANTEA concentrated specifically on the Bitkine area. Pierre Palomar reinterpreted &#039;&#039;&#039;61 existing electrical-resistivity tomography surveys&#039;&#039;&#039; and associated borehole information to develop a local hydrogeological model and improve future borehole siting.&amp;lt;ref name=&amp;quot;palomar&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The work builds directly on Nouradine&#039;s regional research, which had concentrated particularly on the Mongo and Barlo areas.&lt;br /&gt;
&lt;br /&gt;
The Bitkine study found that geology and weathering pattern are critical to borehole performance and that geophysical anomalies cannot be interpreted reliably as fractures without considering the geological and geomorphological context.&amp;lt;ref name=&amp;quot;palomar&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
A dedicated page covers the local conditions and water-supply work:&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;[[Regions:Chad/Guéra/Bitkine]]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
== Water supply ==&lt;br /&gt;
&lt;br /&gt;
Much of Guéra depends on boreholes, hand-pumped wells and small piped drinking-water systems.&lt;br /&gt;
&lt;br /&gt;
The combination of low borehole yields, high drilling failure rates, seasonal demand and uncertain recharge makes reliable water supply difficult, particularly during the dry season.&lt;br /&gt;
&lt;br /&gt;
The provincial development plan reported substantial deficits in both rural hand-pump coverage and piped AEP systems.&amp;lt;ref name=&amp;quot;spat&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the Bitkine area, &#039;&#039;&#039;SEVES&#039;&#039;&#039; and its Chadian partner &#039;&#039;&#039;ADES&#039;&#039;&#039; have been working with the Commune of Bitkine and the regional water authorities through the &#039;&#039;&#039;REAVIA&#039;&#039;&#039; programme.&lt;br /&gt;
&lt;br /&gt;
Recent groundwater-development work reported by SEVES included:&lt;br /&gt;
&lt;br /&gt;
* a new borehole at Bitkine producing approximately &#039;&#039;&#039;6 m³/h&#039;&#039;&#039;;&lt;br /&gt;
* rehabilitation of a borehole at Koubo Adougoul producing approximately &#039;&#039;&#039;4 m³/h&#039;&#039;&#039;;&lt;br /&gt;
* a new borehole at Koubo Adougoul producing approximately &#039;&#039;&#039;7 m³/h&#039;&#039;&#039;.&amp;lt;ref name=&amp;quot;reavia&amp;quot;&amp;gt;[https://www.asso-seves.org/tchad-mobilisation-de-la-ressource-en-eau-pour-les-services-d-eau-potable-de.html SEVES, &#039;&#039;Mobilisation de la ressource en eau pour les services d&#039;eau potable de Bitkine et Koubo Adougoul dans la province du Guéra — REAVIA&#039;&#039;.]&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
These yields are high relative to many of the boreholes represented in the regional datasets.&lt;br /&gt;
&lt;br /&gt;
== Hydrogeological research ==&lt;br /&gt;
&lt;br /&gt;
Recent groundwater research in Guéra has produced an unusually large combined hydrogeological and geophysical dataset for a crystalline-basement region.&lt;br /&gt;
&lt;br /&gt;
=== Nouradine 2023 ===&lt;br /&gt;
&lt;br /&gt;
Haroun Nouradine&#039;s doctoral research combined:&lt;br /&gt;
&lt;br /&gt;
* geological analysis;&lt;br /&gt;
* hydrogeology;&lt;br /&gt;
* electrical geophysics;&lt;br /&gt;
* groundwater chemistry;&lt;br /&gt;
* stable isotopes;&lt;br /&gt;
* piezometric monitoring;&lt;br /&gt;
* machine learning.&lt;br /&gt;
&lt;br /&gt;
The underlying datasets include:&lt;br /&gt;
&lt;br /&gt;
* 798 boreholes;&lt;br /&gt;
* 700 EM34 profiles;&lt;br /&gt;
* 592 electrical-resistivity tomography profiles;&lt;br /&gt;
* 211 geochemical and isotopic groundwater samples.&lt;br /&gt;
&lt;br /&gt;
The work established a conceptual model of Guéra&#039;s crystalline-basement aquifers and identified factors controlling borehole productivity.&amp;lt;ref name=&amp;quot;nouradine&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Full thesis:&#039;&#039;&#039;  &lt;br /&gt;
:[https://nextcloud.aowis.org/s/tCJgPAa2G6Lws83 &#039;&#039;Évaluation des ressources en eau dans les aquifères de socle dans la région du Guéra (Tchad)&#039;&#039;, Haroun Nouradine, 2023]&lt;br /&gt;
&lt;br /&gt;
=== Palomar / SEVES 2024 ===&lt;br /&gt;
&lt;br /&gt;
Pierre Palomar&#039;s study, carried out within SEVES in collaboration with Sorbonne Université&#039;s UMR METIS and ANTEA, applies the regional hydrogeological model specifically to the Bitkine area.&lt;br /&gt;
&lt;br /&gt;
It includes:&lt;br /&gt;
&lt;br /&gt;
* a review of basement-aquifer hydrogeology;&lt;br /&gt;
* evaluation of geophysical prospecting methods;&lt;br /&gt;
* reinterpretation of existing ERT surveys;&lt;br /&gt;
* comparison with borehole results;&lt;br /&gt;
* a hydrogeological conceptual model for the Bitkine area;&lt;br /&gt;
* recommendations for future groundwater prospecting and borehole siting.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Full report:&#039;&#039;&#039;  &lt;br /&gt;
:[https://nextcloud.aowis.org/s/j7Gy7bMrFr5Gsew &#039;&#039;Conceptualisation hydrogéologique et recommandations pour les prospections géophysiques et l&#039;implantation des forages — Province du Guéra, Tchad&#039;&#039;, Pierre Palomar / SEVES, 2024]&lt;br /&gt;
&lt;br /&gt;
== AOWIS work ==&lt;br /&gt;
&lt;br /&gt;
Guéra is a current AOWIS field region, with initial work concentrated around [[Regions:Chad/Guéra/Bitkine|Bitkine]].&lt;br /&gt;
&lt;br /&gt;
Current work includes documentation of existing water points, seasonal borehole yields, water quality, groundwater salinity, opportunities for cooperation between existing well operators, and options for additional storage, treatment and distribution infrastructure.&lt;br /&gt;
&lt;br /&gt;
The combination of highly variable groundwater productivity and local differences in groundwater chemistry makes the region particularly relevant to integrated water-resource monitoring and planning.&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== External resources ==&lt;br /&gt;
&lt;br /&gt;
* [https://nextcloud.aowis.org/s/tCJgPAa2G6Lws83 Nouradine 2023 doctoral thesis — AOWIS-hosted PDF]&lt;br /&gt;
* [https://nextcloud.aowis.org/s/j7Gy7bMrFr5Gsew Palomar / SEVES Guéra and Bitkine hydrogeology report — AOWIS-hosted PDF]&lt;br /&gt;
* [https://doi.org/10.1007/s10040-024-02766-2 Nouradine et al. 2024 — Hydrogeology Journal]&lt;br /&gt;
* [https://www.asso-seves.org/implantation-des-forages-dans-la-province-du-guera-autchad.html SEVES — hydrogeology and borehole siting in Guéra]&lt;br /&gt;
* [https://apef-conservation.org/ressources-documentaires/ Schéma Provincial d&#039;Aménagement du Territoire du Guéra 2022–2032]&lt;br /&gt;
&lt;br /&gt;
[[Category:Chad]]&lt;br /&gt;
[[Category:Guéra]]&lt;br /&gt;
[[Category:Groundwater]]&lt;br /&gt;
[[Category:Hydrogeology]]&lt;br /&gt;
[[Category:Water supply]]&lt;/div&gt;</summary>
		<author><name>Samuel</name></author>
	</entry>
	<entry>
		<id>https://aowis.org/index.php?title=Main_Page&amp;diff=768</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://aowis.org/index.php?title=Main_Page&amp;diff=768"/>
		<updated>2026-09-23T16:21:30Z</updated>

		<summary type="html">&lt;p&gt;Samuel: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
&lt;br /&gt;
{{MainPageBanner}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Motivation&lt;br /&gt;
 | color = teal&lt;br /&gt;
 | body = &lt;br /&gt;
&lt;br /&gt;
[[File:Countryside.jpg|class=fullwidth|center]]&lt;br /&gt;
&lt;br /&gt;
In many rural and underserved regions, including parts of Africa, wells and pumps may exist while developing and operating a reliable distribution network remains difficult. Local initiatives can lack engineering capacity, trained personnel, suitable technology, and affordable tools for operating such infrastructure sustainably.&lt;br /&gt;
&lt;br /&gt;
This practical problem is an important motivation for AOWIS. AOWIS aims to make the engineering knowledge, technical foundations, software, and operational methods needed to develop and operate water infrastructure openly available and practically usable, while supporting local training and cooperation with experienced organizations and operators.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Why AOWIS is Needed&lt;br /&gt;
 | color = turquoise&lt;br /&gt;
 | body = &lt;br /&gt;
&lt;br /&gt;
[[File:Cooperation.jpg|400px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
Water and irrigation infrastructure must often be planned, built, expanded, and operated over many decades. In some places, existing infrastructure has become fragmented across different vendors, technologies, tools, and engineering approaches. In others, communities and organizations are building coherent water infrastructure for the first time and may have limited access to engineering capacity, technical guidance, suitable software, or established operational practices.&lt;br /&gt;
&lt;br /&gt;
AOWIS provides a shared open foundation for both situations. It brings together technical standards, engineering knowledge, software, reference implementations, operational guidance, and training to support the development of water infrastructure from initial planning and design through construction, operation, maintenance, and future expansion.&lt;br /&gt;
&lt;br /&gt;
The aim is to make infrastructure understandable, interoperable, maintainable, and extensible throughout its lifecycle, while reducing dependence on individual vendors, products, suppliers, or scarce specialist expertise.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Operating Conditions&lt;br /&gt;
 | color = lightblue&lt;br /&gt;
 | body =&lt;br /&gt;
&lt;br /&gt;
[[File:Village.jpg|250px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS is designed for environments where water infrastructure must remain useful and safe despite difficult technical and operational conditions. This is particularly important in rural and underserved regions, where reliable power, continuous connectivity, modern equipment, trained personnel, and specialist support cannot always be assumed.&lt;br /&gt;
&lt;br /&gt;
Typical conditions include:&lt;br /&gt;
&lt;br /&gt;
* unreliable or limited power supply&lt;br /&gt;
* intermittent or unavailable connectivity&lt;br /&gt;
* heterogeneous or aging equipment&lt;br /&gt;
* limited availability of trained technical personnel&lt;br /&gt;
* limited access to specialist engineering support&lt;br /&gt;
* the need for safe local operation without continuous remote supervision&lt;br /&gt;
&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Design Principles&lt;br /&gt;
 | color = lightblue&lt;br /&gt;
 | body =&lt;br /&gt;
&lt;br /&gt;
AOWIS addresses these conditions through principles including:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;offline-first operation&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;safe fallback behaviour&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;human-in-the-loop control&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;local autonomous operation&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;modular and extensible system design&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;shared infrastructure models&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;open interfaces and accessible technical documentation&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The goal is to make essential water infrastructure &#039;&#039;&#039;robust, understandable, maintainable, and locally operable&#039;&#039;&#039;, including where conventional assumptions about connectivity, technical resources, and institutional support do not hold.&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
| title = Software &amp;amp; Downloads&lt;br /&gt;
| color = green&lt;br /&gt;
| body =&lt;br /&gt;
[[File:GUI ky4 3d.png|400px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS includes an open-source software platform for &#039;&#039;&#039;modelling, simulating, visualizing, monitoring, and operating water infrastructure&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The current software includes a network editor and monitoring interface, hydraulic and water-quality simulation using [[External:EPANET:Main Page|EPANET]], geographic maps and terrain visualization, and support for local and standalone operation. Development of the AOWIS Controller is progressing toward a complete open-source SCADA and operational management platform..&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://download.aowis.org Download the AOWIS Controller (development snapshot)]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* [https://github.com/aowis-org Source code on GitHub]&lt;br /&gt;
* [[#Roadmap|Software development roadmap]]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Start Here&lt;br /&gt;
 | color = yellow&lt;br /&gt;
 | body =&lt;br /&gt;
If you are new to AOWIS, begin with:&lt;br /&gt;
&lt;br /&gt;
* [[Concepts:Design_Philosophy|Design Philosophy]]  &lt;br /&gt;
* [[Standard:Definitions|Definitions]]  &lt;br /&gt;
* [[Standard:Normative_Requirements|Normative Requirements]]  &lt;br /&gt;
* [[Modules:Module_Template|Module Template]]  &lt;br /&gt;
* [[AOWIS:Contributor_Guide_External|Contributor Guide - External]]&lt;br /&gt;
* [[AOWIS:Contributor_Guide_Internal|Contributor Guide - Internal]]&lt;br /&gt;
* [[AOWIS:Writing_Style_Guide|Writing Style Guide]]&lt;br /&gt;
* [[AOWIS:AI_Usage_Guide|AI Usage Guide]]&lt;br /&gt;
* [[AOWIS:Research_Form_Guide|Research Form Guide]]&lt;br /&gt;
* [[AOWIS:Naming_Convention_Specification|Naming Convention Specification]]&lt;br /&gt;
* [[AOWIS:Change_Log__Versioning|Change Log &amp;amp; Versioning]]&lt;br /&gt;
* [[AOWIS:Wiki|This Wiki]]&lt;br /&gt;
&lt;br /&gt;
These pages explain the foundations of AOWIS, how the AOWIS Standard is structured, and how to use and contribute to the project and its documentation.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = List of Requirement Pages&lt;br /&gt;
 | color = brown&lt;br /&gt;
 | body = &lt;br /&gt;
This index lists AOWIS pages that define normative requirements (MUST/SHOULD/MAY statements) and conformance rules.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Dev Rules&#039;&#039;&#039; — specs for writing and maintaining AOWIS&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;REQ-AI:&#039;&#039;&#039; [[AOWIS:AI_Usage_Guide|AI Usage Guide]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Technical Standard&#039;&#039;&#039; — system behavior and data models&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;REQ-MEAS, REQ-MEAS-UI:&#039;&#039;&#039; [[Measurement:Units|Unit System Requirements]]&lt;br /&gt;
* &#039;&#039;&#039;REQ-MEAS-UNI:&#039;&#039;&#039; [[Measurement:Canonical_Units|Canonical Units]]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = AOWIS Documentation Structure&lt;br /&gt;
 | color = purple&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS documentation is organized into dedicated namespaces with clearly separated purposes.&lt;br /&gt;
&lt;br /&gt;
The [[Standard:Main_Page|Standard]] namespace contains the normative requirements that define AOWIS compliance. The other namespaces provide the motivation, concepts, engineering knowledge, architectures, operational models, implementation guidance, reference designs, training material, and supporting information needed to understand, implement, and operate AOWIS systems.&lt;br /&gt;
&lt;br /&gt;
* [[Motivation:Main_Page|Motivation]] – Causal justification of design requirements based on real-world failures, constraints, and operational realities.&lt;br /&gt;
* [[Standard:Main_Page|Standard]] – The normative core of AOWIS. Defines requirements and definitions specifying what AOWIS-compliant systems MUST, SHOULD, or MAY do.&lt;br /&gt;
* [[Concepts:Main_Page|Concepts]] – Core ideas, philosophy, rationale, and contextual understanding that explain AOWIS without prescribing a specific implementation.&lt;br /&gt;
* [[Architecture:Main_Page|Architecture]] – High-level system structure, including controllers, layers, communication, data flows, and their interactions.&lt;br /&gt;
* [[Infrastructure:Main_Page|Infrastructure]] – Physical technologies, systems, and components used in AOWIS deployments. Infrastructure pages describe classes of physical systems rather than specific implementation blueprints.&lt;br /&gt;
* [[Measurement:Main_Page|Measurement]] – Definition and handling of sensor data, manual measurements, calibration, uncertainty, and derived physical values.&lt;br /&gt;
* [[Data:Main_Page|Data]] – Data models, schemas, logging structures, synchronization formats, and data lifecycle rules.&lt;br /&gt;
* [[Operations:Main_Page|Operations]] – Runtime behavior, control logic, state transitions, fallback behavior, and decision-making during system operation.&lt;br /&gt;
* [[Modules:Main_Page|Modules]] – Reusable functional extensions that provide domain-specific capabilities within AOWIS.&lt;br /&gt;
* [[Reference:Main_Page|Reference]] – Non-normative concrete implementations, engineering blueprints, example deployments, and validated design patterns showing specific ways AOWIS systems may be built.&lt;br /&gt;
* [[Databases:Main_Page|Databases]] – Federated knowledge bases and structured supporting information used by AOWIS implementations.&lt;br /&gt;
* [[Governance:Main_Page|Governance]] – Certification, compliance, auditing, trust, licensing, versioning, and organizational governance.&lt;br /&gt;
* [[Training:Main_Page|Training]] – Operator education, technical training, field guidance, documentation literacy, and capacity building.&lt;br /&gt;
* [[External:Main_Page|External]] – External projects, standards, technologies, and systems that relate to or influence AOWIS.&lt;br /&gt;
&lt;br /&gt;
* [[Regions:Main_Page|Regions]] – Geographic, environmental, hydrological, climatic, socioeconomic, and infrastructure context for areas in which AOWIS is researched, planned, or deployed.&lt;br /&gt;
&lt;br /&gt;
For a full overview, see the [[AOWIS:Table_of_Contents|Table of Contents]].&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Roadmap&lt;br /&gt;
 | color = grey&lt;br /&gt;
 | body =&lt;br /&gt;
[[File:Boring.jpg|250px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS has progressed beyond its initial conceptual phase. A substantial software foundation for modelling, simulating, visualizing, and eventually operating water infrastructure is under active development.&lt;br /&gt;
&lt;br /&gt;
The current software stack already includes:&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Shared infrastructure model&#039;&#039;&#039;&lt;br /&gt;
: A common, solver-independent representation of water infrastructure used throughout the AOWIS software stack.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-MODEL GitHub AOWIS-SERVER-MODEL]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Hydraulic and water-quality simulation&#039;&#039;&#039;&lt;br /&gt;
: EPANET integration for hydraulic and water-quality simulation, network import/export, controls, rules, diagnostics, and simulation results. Integration of &#039;&#039;&#039;EPANET-MSX&#039;&#039;&#039; is also being developed.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-EPANET GitHub AOWIS-SERVER-EPANET]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Network editor and monitoring interface&#039;&#039;&#039;&lt;br /&gt;
: A graphical application for creating, inspecting, simulating, and visualizing water networks, including geographic maps and terrain-aware 3D visualization.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-GUI GitHub AOWIS-SERVER-GUI]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Geographic and terrain infrastructure&#039;&#039;&#039;&lt;br /&gt;
: Mapping, elevation data, basemaps, terrain visualization, geographic placement, and local caching.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-MAP GitHub AOWIS-SERVER-MAP]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Local and standalone operation&#039;&#039;&#039;&lt;br /&gt;
: Support for deployments that do not depend on continuous Internet or cloud connectivity.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-Standalone GitHub AOWIS-SERVER-Standalone]&lt;br /&gt;
&lt;br /&gt;
The software remains under active development and should not yet be considered a complete production SCADA system.&lt;br /&gt;
&lt;br /&gt;
The next major stage is to connect the existing modelling and simulation environment to &#039;&#039;&#039;real infrastructure in continuous operation&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The AOWIS software platform is intended to develop into a complete open-source SCADA, infrastructure modelling, simulation, and operational management platform in which planning, live monitoring, control, historical data, maintenance, and simulation operate on the same shared infrastructure model.&lt;br /&gt;
&lt;br /&gt;
This includes telemetry, sensors and actuators, alarms and historian functions, local and remote control, automation with safe fallback behaviour, and model-assisted operation using measured and simulated system behaviour.&lt;br /&gt;
&lt;br /&gt;
EPANET currently provides the primary hydraulic and water-quality simulation engine, but AOWIS is not designed solely as an EPANET frontend. EPANET is one solver integrated into a broader, solver-independent architecture.&lt;br /&gt;
&lt;br /&gt;
The long-term objective is to connect the complete infrastructure lifecycle:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;survey and planning → engineering and simulation → construction → commissioning → monitoring → control → maintenance → analysis → expansion&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[[AOWIS:Roadmap|Read the full roadmap →]]&#039;&#039;&#039;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
| title = Community &amp;amp; Participation&lt;br /&gt;
| color = blue&lt;br /&gt;
| body =&lt;br /&gt;
&lt;br /&gt;
AOWIS is an open project, and participation is welcome from anyone interested in its goals — including engineers, developers, NGOs, operators, researchers, technicians, students, and people with practical experience in water and irrigation infrastructure.&lt;br /&gt;
&lt;br /&gt;
For &#039;&#039;&#039;discussion, planning, questions, documentation, infrastructure, field projects, standards, research, and other forms of participation&#039;&#039;&#039;, AOWIS uses &#039;&#039;&#039;Matrix&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The AOWIS Matrix server has several &#039;&#039;&#039;public spaces and rooms&#039;&#039;&#039; for different topics. Join those relevant to your interests. For general questions or help finding the right place, start here:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://matrix.to/#/#support:aowis.org AOWIS Support — #support:aowis.org]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Any Matrix account can join public AOWIS spaces and rooms.&lt;br /&gt;
&lt;br /&gt;
If you are new to Matrix:&lt;br /&gt;
&lt;br /&gt;
* [https://matrix.org/try-matrix/ Learn about Matrix and create an account]&lt;br /&gt;
* [https://element.io/ Element] — Matrix client for web, desktop, and mobile&lt;br /&gt;
* [https://fluffychat.im/ FluffyChat] — simple Matrix client for several platforms&lt;br /&gt;
&lt;br /&gt;
The same Matrix account can be used with different clients.&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;AOWIS Matrix Accounts&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Participants may also request an account on the AOWIS Matrix homeserver, giving them an ID such as &#039;&#039;&#039;@name:aowis.org&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
To reduce automated registrations and abuse, accounts are created on request. Please send a short introduction telling us who you are, what interests you about AOWIS, and where you would like to participate: [[File:Mtx.png|120px|frameless|alt=Email address for requesting an AOWIS Matrix account]]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Software Development&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Software development happens on &#039;&#039;&#039;GitHub&#039;&#039;&#039;. Bug reports, pull requests, source-code contributions, and repository-specific development discussions should use the appropriate repository.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://github.com/aowis-org AOWIS on GitHub]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Matrix is for the broader AOWIS community and participation that does not naturally belong in a GitHub repository.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Governance &amp;amp; Legitimacy&lt;br /&gt;
 | color = turquoise&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS includes a transparent governance model to ensure:&lt;br /&gt;
&lt;br /&gt;
* open participation  &lt;br /&gt;
* clear certification processes  &lt;br /&gt;
* stable versioning  &lt;br /&gt;
* long-term stewardship and continuity&lt;br /&gt;
&lt;br /&gt;
See: [[Governance:Main_Page|Governance]].&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Navigation&lt;br /&gt;
 | color = grey&lt;br /&gt;
 | body =&lt;br /&gt;
* [[AOWIS:Table_of_Contents|Table of Contents]]  &lt;br /&gt;
* [[Reference:Glossary|Glossary]]  &lt;br /&gt;
* [[Reference:FAQ|FAQ]]  &lt;br /&gt;
* [[Reference:Change_Log|Change Log]]  &lt;br /&gt;
&lt;br /&gt;
* [https://github.com/aowis-org GitHub]&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Partners&lt;br /&gt;
 | color = indigo&lt;br /&gt;
 | body = &lt;br /&gt;
[[File:Afriticgroup.webp|250px|frameless|center|link=https://afriticgroup.com/]]&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Samuel</name></author>
	</entry>
	<entry>
		<id>https://aowis.org/index.php?title=Main_Page&amp;diff=767</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://aowis.org/index.php?title=Main_Page&amp;diff=767"/>
		<updated>2026-09-23T16:02:19Z</updated>

		<summary type="html">&lt;p&gt;Samuel: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
&lt;br /&gt;
{{MainPageBanner}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Motivation&lt;br /&gt;
 | color = teal&lt;br /&gt;
 | body = &lt;br /&gt;
&lt;br /&gt;
[[File:Countryside.jpg|class=fullwidth|center]]&lt;br /&gt;
&lt;br /&gt;
In many rural and underserved regions, including parts of Africa, wells and pumps may exist while developing and operating a reliable distribution network remains difficult. Local initiatives can lack engineering capacity, trained personnel, suitable technology, and affordable tools for operating such infrastructure sustainably.&lt;br /&gt;
&lt;br /&gt;
This practical problem is an important motivation for AOWIS. AOWIS aims to make the engineering knowledge, technical foundations, software, and operational methods needed to develop and operate water infrastructure openly available and practically usable, while supporting local training and cooperation with experienced organizations and operators.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Why AOWIS is Needed&lt;br /&gt;
 | color = turquoise&lt;br /&gt;
 | body = &lt;br /&gt;
&lt;br /&gt;
[[File:Cooperation.jpg|400px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
Water and irrigation infrastructure must often be planned, built, expanded, and operated over many decades. In some places, existing infrastructure has become fragmented across different vendors, technologies, tools, and engineering approaches. In others, communities and organizations are building coherent water infrastructure for the first time and may have limited access to engineering capacity, technical guidance, suitable software, or established operational practices.&lt;br /&gt;
&lt;br /&gt;
AOWIS provides a shared open foundation for both situations. It brings together technical standards, engineering knowledge, software, reference implementations, operational guidance, and training to support the development of water infrastructure from initial planning and design through construction, operation, maintenance, and future expansion.&lt;br /&gt;
&lt;br /&gt;
The aim is to make infrastructure understandable, interoperable, maintainable, and extensible throughout its lifecycle, while reducing dependence on individual vendors, products, suppliers, or scarce specialist expertise.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Operation Conditions&lt;br /&gt;
 | color = lightblue&lt;br /&gt;
 | body =&lt;br /&gt;
[[File:Village.jpg|250px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS is designed to operate under the real-world conditions faced by local initiatives. These include, among others:&lt;br /&gt;
&lt;br /&gt;
* unreliable power supply&lt;br /&gt;
* intermittent connectivity&lt;br /&gt;
* diverse or aging equipment&lt;br /&gt;
* limited availability of trained personnel&lt;br /&gt;
* the need for safety and autonomous operation&lt;br /&gt;
&lt;br /&gt;
AOWIS enables systems that continue to function safely and reliably, even under degraded or adverse conditions.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Facing the Challenges&lt;br /&gt;
 | color = lightblue&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS addresses these operational challenges through the following principles:&lt;br /&gt;
&lt;br /&gt;
* human-in-the-loop control&lt;br /&gt;
* offline-first operation&lt;br /&gt;
* safe fallback behavior&lt;br /&gt;
* modular and extensible logic&lt;br /&gt;
* shared infrastructure models&lt;br /&gt;
* training programs for local operators&lt;br /&gt;
* transparent governance&lt;br /&gt;
&lt;br /&gt;
The goal is to make essential systems &#039;&#039;&#039;robust, maintainable, and locally operable&#039;&#039;&#039;.&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
| title = Software &amp;amp; Downloads&lt;br /&gt;
| color = green&lt;br /&gt;
| body =&lt;br /&gt;
[[File:GUI ky4 3d.png|400px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS includes an open-source software platform for &#039;&#039;&#039;modelling, simulating, visualizing, monitoring, and operating water infrastructure&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The current software includes a network editor and monitoring interface, hydraulic and water-quality simulation using [[External:EPANET:Main Page|EPANET]], geographic maps and terrain visualization, and support for local and standalone operation. Development of the AOWIS Controller is progressing toward a complete open-source SCADA and operational management platform..&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://download.aowis.org Download the AOWIS Controller (development snapshot)]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* [https://github.com/aowis-org Source code on GitHub]&lt;br /&gt;
* [[#Roadmap|Software development roadmap]]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Start Here&lt;br /&gt;
 | color = yellow&lt;br /&gt;
 | body =&lt;br /&gt;
If you are new to AOWIS, begin with:&lt;br /&gt;
&lt;br /&gt;
* [[Concepts:Design_Philosophy|Design Philosophy]]  &lt;br /&gt;
* [[Standard:Definitions|Definitions]]  &lt;br /&gt;
* [[Standard:Normative_Requirements|Normative Requirements]]  &lt;br /&gt;
* [[Modules:Module_Template|Module Template]]  &lt;br /&gt;
* [[AOWIS:Contributor_Guide_External|Contributor Guide - External]]&lt;br /&gt;
* [[AOWIS:Contributor_Guide_Internal|Contributor Guide - Internal]]&lt;br /&gt;
* [[AOWIS:Writing_Style_Guide|Writing Style Guide]]&lt;br /&gt;
* [[AOWIS:AI_Usage_Guide|AI Usage Guide]]&lt;br /&gt;
* [[AOWIS:Research_Form_Guide|Research Form Guide]]&lt;br /&gt;
* [[AOWIS:Naming_Convention_Specification|Naming Convention Specification]]&lt;br /&gt;
* [[AOWIS:Change_Log__Versioning|Change Log &amp;amp; Versioning]]&lt;br /&gt;
* [[AOWIS:Wiki|This Wiki]]&lt;br /&gt;
&lt;br /&gt;
These pages explain the foundations of AOWIS, how the AOWIS Standard is structured, and how to use and contribute to the project and its documentation.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = List of Requirement Pages&lt;br /&gt;
 | color = brown&lt;br /&gt;
 | body = &lt;br /&gt;
This index lists AOWIS pages that define normative requirements (MUST/SHOULD/MAY statements) and conformance rules.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Dev Rules&#039;&#039;&#039; — specs for writing and maintaining AOWIS&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;REQ-AI:&#039;&#039;&#039; [[AOWIS:AI_Usage_Guide|AI Usage Guide]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Technical Standard&#039;&#039;&#039; — system behavior and data models&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;REQ-MEAS, REQ-MEAS-UI:&#039;&#039;&#039; [[Measurement:Units|Unit System Requirements]]&lt;br /&gt;
* &#039;&#039;&#039;REQ-MEAS-UNI:&#039;&#039;&#039; [[Measurement:Canonical_Units|Canonical Units]]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = AOWIS Documentation Structure&lt;br /&gt;
 | color = purple&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS documentation is organized into dedicated namespaces with clearly separated purposes.&lt;br /&gt;
&lt;br /&gt;
The [[Standard:Main_Page|Standard]] namespace contains the normative requirements that define AOWIS compliance. The other namespaces provide the motivation, concepts, engineering knowledge, architectures, operational models, implementation guidance, reference designs, training material, and supporting information needed to understand, implement, and operate AOWIS systems.&lt;br /&gt;
&lt;br /&gt;
* [[Motivation:Main_Page|Motivation]] – Causal justification of design requirements based on real-world failures, constraints, and operational realities.&lt;br /&gt;
* [[Standard:Main_Page|Standard]] – The normative core of AOWIS. Defines requirements and definitions specifying what AOWIS-compliant systems MUST, SHOULD, or MAY do.&lt;br /&gt;
* [[Concepts:Main_Page|Concepts]] – Core ideas, philosophy, rationale, and contextual understanding that explain AOWIS without prescribing a specific implementation.&lt;br /&gt;
* [[Architecture:Main_Page|Architecture]] – High-level system structure, including controllers, layers, communication, data flows, and their interactions.&lt;br /&gt;
* [[Infrastructure:Main_Page|Infrastructure]] – Physical technologies, systems, and components used in AOWIS deployments. Infrastructure pages describe classes of physical systems rather than specific implementation blueprints.&lt;br /&gt;
* [[Measurement:Main_Page|Measurement]] – Definition and handling of sensor data, manual measurements, calibration, uncertainty, and derived physical values.&lt;br /&gt;
* [[Data:Main_Page|Data]] – Data models, schemas, logging structures, synchronization formats, and data lifecycle rules.&lt;br /&gt;
* [[Operations:Main_Page|Operations]] – Runtime behavior, control logic, state transitions, fallback behavior, and decision-making during system operation.&lt;br /&gt;
* [[Modules:Main_Page|Modules]] – Reusable functional extensions that provide domain-specific capabilities within AOWIS.&lt;br /&gt;
* [[Reference:Main_Page|Reference]] – Non-normative concrete implementations, engineering blueprints, example deployments, and validated design patterns showing specific ways AOWIS systems may be built.&lt;br /&gt;
* [[Databases:Main_Page|Databases]] – Federated knowledge bases and structured supporting information used by AOWIS implementations.&lt;br /&gt;
* [[Governance:Main_Page|Governance]] – Certification, compliance, auditing, trust, licensing, versioning, and organizational governance.&lt;br /&gt;
* [[Training:Main_Page|Training]] – Operator education, technical training, field guidance, documentation literacy, and capacity building.&lt;br /&gt;
* [[External:Main_Page|External]] – External projects, standards, technologies, and systems that relate to or influence AOWIS.&lt;br /&gt;
&lt;br /&gt;
* [[Regions:Main_Page|Regions]] – Geographic, environmental, hydrological, climatic, socioeconomic, and infrastructure context for areas in which AOWIS is researched, planned, or deployed.&lt;br /&gt;
&lt;br /&gt;
For a full overview, see the [[AOWIS:Table_of_Contents|Table of Contents]].&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Roadmap&lt;br /&gt;
 | color = grey&lt;br /&gt;
 | body =&lt;br /&gt;
[[File:Boring.jpg|250px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS has progressed beyond its initial conceptual phase. A substantial software foundation for modelling, simulating, visualizing, and eventually operating water infrastructure is under active development.&lt;br /&gt;
&lt;br /&gt;
The current software stack already includes:&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Shared infrastructure model&#039;&#039;&#039;&lt;br /&gt;
: A common, solver-independent representation of water infrastructure used throughout the AOWIS software stack.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-MODEL GitHub AOWIS-SERVER-MODEL]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Hydraulic and water-quality simulation&#039;&#039;&#039;&lt;br /&gt;
: EPANET integration for hydraulic and water-quality simulation, network import/export, controls, rules, diagnostics, and simulation results. Integration of &#039;&#039;&#039;EPANET-MSX&#039;&#039;&#039; is also being developed.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-EPANET GitHub AOWIS-SERVER-EPANET]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Network editor and monitoring interface&#039;&#039;&#039;&lt;br /&gt;
: A graphical application for creating, inspecting, simulating, and visualizing water networks, including geographic maps and terrain-aware 3D visualization.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-GUI GitHub AOWIS-SERVER-GUI]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Geographic and terrain infrastructure&#039;&#039;&#039;&lt;br /&gt;
: Mapping, elevation data, basemaps, terrain visualization, geographic placement, and local caching.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-MAP GitHub AOWIS-SERVER-MAP]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Local and standalone operation&#039;&#039;&#039;&lt;br /&gt;
: Support for deployments that do not depend on continuous Internet or cloud connectivity.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-Standalone GitHub AOWIS-SERVER-Standalone]&lt;br /&gt;
&lt;br /&gt;
The software remains under active development and should not yet be considered a complete production SCADA system.&lt;br /&gt;
&lt;br /&gt;
The next major stage is to connect the existing modelling and simulation environment to &#039;&#039;&#039;real infrastructure in continuous operation&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The AOWIS software platform is intended to develop into a complete open-source SCADA, infrastructure modelling, simulation, and operational management platform in which planning, live monitoring, control, historical data, maintenance, and simulation operate on the same shared infrastructure model.&lt;br /&gt;
&lt;br /&gt;
This includes telemetry, sensors and actuators, alarms and historian functions, local and remote control, automation with safe fallback behaviour, and model-assisted operation using measured and simulated system behaviour.&lt;br /&gt;
&lt;br /&gt;
EPANET currently provides the primary hydraulic and water-quality simulation engine, but AOWIS is not designed solely as an EPANET frontend. EPANET is one solver integrated into a broader, solver-independent architecture.&lt;br /&gt;
&lt;br /&gt;
The long-term objective is to connect the complete infrastructure lifecycle:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;survey and planning → engineering and simulation → construction → commissioning → monitoring → control → maintenance → analysis → expansion&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[[AOWIS:Roadmap|Read the full roadmap →]]&#039;&#039;&#039;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
| title = Community &amp;amp; Participation&lt;br /&gt;
| color = blue&lt;br /&gt;
| body =&lt;br /&gt;
&lt;br /&gt;
AOWIS is an open project, and participation is welcome from anyone interested in its goals — including engineers, developers, NGOs, operators, researchers, technicians, students, and people with practical experience in water and irrigation infrastructure.&lt;br /&gt;
&lt;br /&gt;
For &#039;&#039;&#039;discussion, planning, questions, documentation, infrastructure, field projects, standards, research, and other forms of participation&#039;&#039;&#039;, AOWIS uses &#039;&#039;&#039;Matrix&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The AOWIS Matrix server has several &#039;&#039;&#039;public spaces and rooms&#039;&#039;&#039; for different topics. Join those relevant to your interests. For general questions or help finding the right place, start here:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://matrix.to/#/#support:aowis.org AOWIS Support — #support:aowis.org]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Any Matrix account can join public AOWIS spaces and rooms.&lt;br /&gt;
&lt;br /&gt;
If you are new to Matrix:&lt;br /&gt;
&lt;br /&gt;
* [https://matrix.org/try-matrix/ Learn about Matrix and create an account]&lt;br /&gt;
* [https://element.io/ Element] — Matrix client for web, desktop, and mobile&lt;br /&gt;
* [https://fluffychat.im/ FluffyChat] — simple Matrix client for several platforms&lt;br /&gt;
&lt;br /&gt;
The same Matrix account can be used with different clients.&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;AOWIS Matrix Accounts&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Participants may also request an account on the AOWIS Matrix homeserver, giving them an ID such as &#039;&#039;&#039;@name:aowis.org&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
To reduce automated registrations and abuse, accounts are created on request. Please send a short introduction telling us who you are, what interests you about AOWIS, and where you would like to participate: [[File:Mtx.png|120px|frameless|alt=Email address for requesting an AOWIS Matrix account]]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Software Development&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Software development happens on &#039;&#039;&#039;GitHub&#039;&#039;&#039;. Bug reports, pull requests, source-code contributions, and repository-specific development discussions should use the appropriate repository.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://github.com/aowis-org AOWIS on GitHub]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Matrix is for the broader AOWIS community and participation that does not naturally belong in a GitHub repository.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Governance &amp;amp; Legitimacy&lt;br /&gt;
 | color = turquoise&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS includes a transparent governance model to ensure:&lt;br /&gt;
&lt;br /&gt;
* open participation  &lt;br /&gt;
* clear certification processes  &lt;br /&gt;
* stable versioning  &lt;br /&gt;
* long-term stewardship and continuity&lt;br /&gt;
&lt;br /&gt;
See: [[Governance:Main_Page|Governance]].&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Navigation&lt;br /&gt;
 | color = grey&lt;br /&gt;
 | body =&lt;br /&gt;
* [[AOWIS:Table_of_Contents|Table of Contents]]  &lt;br /&gt;
* [[Reference:Glossary|Glossary]]  &lt;br /&gt;
* [[Reference:FAQ|FAQ]]  &lt;br /&gt;
* [[Reference:Change_Log|Change Log]]  &lt;br /&gt;
&lt;br /&gt;
* [https://github.com/aowis-org GitHub]&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Partners&lt;br /&gt;
 | color = indigo&lt;br /&gt;
 | body = &lt;br /&gt;
[[File:Afriticgroup.webp|250px|frameless|center|link=https://afriticgroup.com/]]&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Samuel</name></author>
	</entry>
	<entry>
		<id>https://aowis.org/index.php?title=Main_Page&amp;diff=766</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://aowis.org/index.php?title=Main_Page&amp;diff=766"/>
		<updated>2026-09-23T15:59:58Z</updated>

		<summary type="html">&lt;p&gt;Samuel: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
&lt;br /&gt;
{{MainPageBanner}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Motivation&lt;br /&gt;
 | color = teal&lt;br /&gt;
 | body = &lt;br /&gt;
&lt;br /&gt;
[[File:Countryside.jpg|class=fullwidth|center]]&lt;br /&gt;
&lt;br /&gt;
In many rural and underserved regions, including parts of Africa, wells and pumps may exist while developing and operating a reliable distribution network remains difficult. Local initiatives can lack engineering capacity, trained personnel, suitable technology, and affordable tools for operating such infrastructure sustainably.&lt;br /&gt;
&lt;br /&gt;
This practical problem is an important motivation for AOWIS. AOWIS aims to make the engineering knowledge, technical foundations, software, and operational methods needed to develop and operate water infrastructure openly available and practically usable, while supporting local training and cooperation with experienced organizations and operators.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Why AOWIS is Needed&lt;br /&gt;
 | color = turquoise&lt;br /&gt;
 | body = &lt;br /&gt;
&lt;br /&gt;
[[File:Cooperation.jpg|400px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
Water and irrigation infrastructure must often be planned, built, expanded, and operated over many decades. In some places, existing infrastructure has become fragmented across different vendors, technologies, tools, and engineering approaches. In others, communities and organizations are building coherent water infrastructure for the first time and may have limited access to engineering capacity, technical guidance, suitable software, or established operational practices.&lt;br /&gt;
&lt;br /&gt;
AOWIS provides a shared open foundation for both situations. It brings together technical standards, engineering knowledge, software, reference implementations, operational guidance, and training to support the development of water infrastructure from initial planning and design through construction, operation, maintenance, and future expansion.&lt;br /&gt;
&lt;br /&gt;
The aim is to make infrastructure understandable, interoperable, maintainable, and extensible throughout its lifecycle, while reducing dependence on individual vendors, products, suppliers, or scarce specialist expertise.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Operation Conditions&lt;br /&gt;
 | color = lightblue&lt;br /&gt;
 | body =&lt;br /&gt;
[[File:Village.jpg|250px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS is designed to operate under the real-world conditions faced by local initiatives. These include, among others:&lt;br /&gt;
&lt;br /&gt;
* unreliable power supply&lt;br /&gt;
* intermittent connectivity&lt;br /&gt;
* diverse or aging equipment&lt;br /&gt;
* limited availability of trained personnel&lt;br /&gt;
* the need for safety and autonomous operation&lt;br /&gt;
&lt;br /&gt;
AOWIS enables systems that continue to function safely and reliably, even under degraded or adverse conditions.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Facing the Challenges&lt;br /&gt;
 | color = lightblue&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS addresses these operational challenges through the following principles:&lt;br /&gt;
&lt;br /&gt;
* human-in-the-loop control&lt;br /&gt;
* offline-first operation&lt;br /&gt;
* safe fallback behavior&lt;br /&gt;
* modular and extensible logic&lt;br /&gt;
* shared infrastructure models&lt;br /&gt;
* training programs for local operators&lt;br /&gt;
* transparent governance&lt;br /&gt;
&lt;br /&gt;
The goal is to make essential systems &#039;&#039;&#039;robust, maintainable, and locally operable&#039;&#039;&#039;.&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
| title = Software &amp;amp; Downloads&lt;br /&gt;
| color = green&lt;br /&gt;
| body =&lt;br /&gt;
[[File:GUI ky4 3d.png|400px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS includes an open-source software platform for &#039;&#039;&#039;modelling, simulating, visualizing, monitoring, and operating water infrastructure&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The current software includes a network editor and monitoring interface, hydraulic and water-quality simulation using [[External:EPANET:Main Page|EPANET]], geographic maps and terrain visualization, and support for local and standalone operation. Development of the AOWIS Controller is progressing toward a complete open-source SCADA and operational management platform..&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://download.aowis.org Download the AOWIS Controller (development snapshot)]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* [https://github.com/aowis-org Source code on GitHub]&lt;br /&gt;
* [[#Roadmap|Software development roadmap]]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Start Here&lt;br /&gt;
 | color = yellow&lt;br /&gt;
 | body =&lt;br /&gt;
If you are new to AOWIS, begin with:&lt;br /&gt;
&lt;br /&gt;
* [[Concepts:Design_Philosophy|Design Philosophy]]  &lt;br /&gt;
* [[Standard:Definitions|Definitions]]  &lt;br /&gt;
* [[Standard:Normative_Requirements|Normative Requirements]]  &lt;br /&gt;
* [[Modules:Module_Template|Module Template]]  &lt;br /&gt;
* [[AOWIS:Contributor_Guide_External|Contributor Guide - External]]&lt;br /&gt;
* [[AOWIS:Contributor_Guide_Internal|Contributor Guide - Internal]]&lt;br /&gt;
* [[AOWIS:Writing_Style_Guide|Writing Style Guide]]&lt;br /&gt;
* [[AOWIS:AI_Usage_Guide|AI Usage Guide]]&lt;br /&gt;
* [[AOWIS:Research_Form_Guide|Research Form Guide]]&lt;br /&gt;
* [[AOWIS:Naming_Convention_Specification|Naming Convention Specification]]&lt;br /&gt;
* [[AOWIS:Change_Log__Versioning|Change Log &amp;amp; Versioning]]&lt;br /&gt;
* [[AOWIS:Wiki|This Wiki]]&lt;br /&gt;
&lt;br /&gt;
These pages explain the foundations of AOWIS, how the AOWIS Standard is structured, and how to use and contribute to the project and its documentation.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = List of Requirement Pages&lt;br /&gt;
 | color = brown&lt;br /&gt;
 | body = &lt;br /&gt;
This index lists AOWIS pages that define normative requirements (MUST/SHOULD/MAY statements) and conformance rules.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Dev Rules&#039;&#039;&#039; — specs for writing and maintaining AOWIS&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;REQ-AI:&#039;&#039;&#039; [[AOWIS:AI_Usage_Guide|AI Usage Guide]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Technical Standard&#039;&#039;&#039; — system behavior and data models&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;REQ-MEAS, REQ-MEAS-UI:&#039;&#039;&#039; [[Measurement:Units|Unit System Requirements]]&lt;br /&gt;
* &#039;&#039;&#039;REQ-MEAS-UNI:&#039;&#039;&#039; [[Measurement:Canonical_Units|Canonical Units]]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = AOWIS Documentation Structure&lt;br /&gt;
 | color = purple&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS documentation is organized into dedicated namespaces with clearly separated purposes.&lt;br /&gt;
&lt;br /&gt;
The [[Standard:Main_Page|Standard]] namespace contains the normative requirements that define AOWIS compliance. The other namespaces provide the motivation, concepts, engineering knowledge, architectures, operational models, implementation guidance, reference designs, training material, and supporting information needed to understand, implement, and operate AOWIS systems.&lt;br /&gt;
&lt;br /&gt;
* [[Motivation:Main_Page|Motivation]] – Causal justification of design requirements based on real-world failures, constraints, and operational realities.&lt;br /&gt;
* [[Standard:Main_Page|Standard]] – The normative core of AOWIS. Defines requirements and definitions specifying what AOWIS-compliant systems MUST, SHOULD, or MAY do.&lt;br /&gt;
* [[Concepts:Main_Page|Concepts]] – Core ideas, philosophy, rationale, and contextual understanding that explain AOWIS without prescribing a specific implementation.&lt;br /&gt;
* [[Architecture:Main_Page|Architecture]] – High-level system structure, including controllers, layers, communication, data flows, and their interactions.&lt;br /&gt;
* [[Infrastructure:Main_Page|Infrastructure]] – Physical technologies, systems, and components used in AOWIS deployments. Infrastructure pages describe classes of physical systems rather than specific implementation blueprints.&lt;br /&gt;
* [[Measurement:Main_Page|Measurement]] – Definition and handling of sensor data, manual measurements, calibration, uncertainty, and derived physical values.&lt;br /&gt;
* [[Data:Main_Page|Data]] – Data models, schemas, logging structures, synchronization formats, and data lifecycle rules.&lt;br /&gt;
* [[Operations:Main_Page|Operations]] – Runtime behavior, control logic, state transitions, fallback behavior, and decision-making during system operation.&lt;br /&gt;
* [[Modules:Main_Page|Modules]] – Reusable functional extensions that provide domain-specific capabilities within AOWIS.&lt;br /&gt;
* [[Reference:Main_Page|Reference]] – Non-normative concrete implementations, engineering blueprints, example deployments, and validated design patterns showing specific ways AOWIS systems may be built.&lt;br /&gt;
* [[Databases:Main_Page|Databases]] – Federated knowledge bases and structured supporting information used by AOWIS implementations.&lt;br /&gt;
* [[Governance:Main_Page|Governance]] – Certification, compliance, auditing, trust, licensing, versioning, and organizational governance.&lt;br /&gt;
* [[Training:Main_Page|Training]] – Operator education, technical training, field guidance, documentation literacy, and capacity building.&lt;br /&gt;
* [[External:Main_Page|External]] – External projects, standards, technologies, and systems that relate to or influence AOWIS.&lt;br /&gt;
&lt;br /&gt;
* [[Regions:Main_Page|Regions]] – Geographic, environmental, hydrological, climatic, socioeconomic, and infrastructure context for areas in which AOWIS is researched, planned, or deployed.&lt;br /&gt;
&lt;br /&gt;
For a full overview, see the [[AOWIS:Table_of_Contents|Table of Contents]].&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Roadmap&lt;br /&gt;
 | color = grey&lt;br /&gt;
 | body =&lt;br /&gt;
[[File:Boring.jpg|250px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS has progressed beyond its initial conceptual phase. A substantial software foundation for modelling, simulating, visualizing, and eventually operating water infrastructure is under active development.&lt;br /&gt;
&lt;br /&gt;
The current software stack already includes:&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Shared infrastructure model&#039;&#039;&#039;&lt;br /&gt;
: A common, solver-independent representation of water infrastructure used throughout the AOWIS software stack.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-MODEL GitHub AOWIS-SERVER-MODEL]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Hydraulic and water-quality simulation&#039;&#039;&#039;&lt;br /&gt;
: EPANET integration for hydraulic and water-quality simulation, network import/export, controls, rules, diagnostics, and simulation results. Integration of &#039;&#039;&#039;EPANET-MSX&#039;&#039;&#039; is also being developed.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-EPANET GitHub AOWIS-SERVER-EPANET]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Network editor and monitoring interface&#039;&#039;&#039;&lt;br /&gt;
: A graphical application for creating, inspecting, simulating, and visualizing water networks, including geographic maps and terrain-aware 3D visualization.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-GUI GitHub AOWIS-SERVER-GUI]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Geographic and terrain infrastructure&#039;&#039;&#039;&lt;br /&gt;
: Mapping, elevation data, basemaps, terrain visualization, geographic placement, and local caching.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-MAP GitHub AOWIS-SERVER-MAP]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Local and standalone operation&#039;&#039;&#039;&lt;br /&gt;
: Support for deployments that do not depend on continuous Internet or cloud connectivity.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-Standalone GitHub AOWIS-SERVER-Standalone]&lt;br /&gt;
&lt;br /&gt;
The software remains under active development and should not yet be considered a complete production SCADA system.&lt;br /&gt;
&lt;br /&gt;
The next major stage is to connect the existing modelling and simulation environment to &#039;&#039;&#039;real infrastructure in continuous operation&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The AOWIS software platform is intended to develop into a complete open-source SCADA, infrastructure modelling, simulation, and operational management platform in which planning, live monitoring, control, historical data, maintenance, and simulation operate on the same shared infrastructure model.&lt;br /&gt;
&lt;br /&gt;
This includes telemetry, sensors and actuators, alarms and historian functions, local and remote control, automation with safe fallback behaviour, and model-assisted operation using measured and simulated system behaviour.&lt;br /&gt;
&lt;br /&gt;
EPANET currently provides the primary hydraulic and water-quality simulation engine, but AOWIS is not designed solely as an EPANET frontend. EPANET is one solver integrated into a broader, solver-independent architecture.&lt;br /&gt;
&lt;br /&gt;
The long-term objective is to connect the complete infrastructure lifecycle:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;survey and planning → engineering and simulation → construction → commissioning → monitoring → control → maintenance → analysis → expansion&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[[AOWIS:Roadmap|Read the full roadmap →]]&#039;&#039;&#039;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
| title = Community &amp;amp; Participation&lt;br /&gt;
| color = blue&lt;br /&gt;
| body =&lt;br /&gt;
&lt;br /&gt;
AOWIS is an open project, and participation is welcome from anyone interested in its goals — including engineers, developers, NGOs, operators, researchers, technicians, students, and people with practical experience in water and irrigation infrastructure.&lt;br /&gt;
&lt;br /&gt;
For &#039;&#039;&#039;discussion, planning, questions, documentation, infrastructure, field projects, standards, research, and other forms of participation&#039;&#039;&#039;, AOWIS uses &#039;&#039;&#039;Matrix&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The AOWIS Matrix server has several &#039;&#039;&#039;public spaces and rooms&#039;&#039;&#039; for different topics. Join those relevant to your interests. For general questions or help finding the right place, start here:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://matrix.to/#/#support:aowis.org AOWIS Support — #support:aowis.org]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Any Matrix account can join public AOWIS spaces and rooms.&lt;br /&gt;
&lt;br /&gt;
If you are new to Matrix:&lt;br /&gt;
&lt;br /&gt;
* [https://matrix.org/try-matrix/ Learn about Matrix and create an account]&lt;br /&gt;
* [https://element.io/ Element] — Matrix client for web, desktop, and mobile&lt;br /&gt;
* [https://fluffychat.im/ FluffyChat] — simple Matrix client for several platforms&lt;br /&gt;
&lt;br /&gt;
The same Matrix account can be used with different clients.&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;AOWIS Matrix Accounts&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Participants may also request an account on the AOWIS Matrix homeserver, giving them an ID such as &#039;&#039;&#039;@name:aowis.org&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
To reduce automated registrations and abuse, accounts are created on request. Please send a short introduction telling us who you are, what interests you about AOWIS, and where you would like to participate: [[File:Mtx.png|120px|frameless|alt=Email address for requesting an AOWIS Matrix account]]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Software Development&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Software development happens on &#039;&#039;&#039;GitHub&#039;&#039;&#039;. Bug reports, pull requests, source-code contributions, and repository-specific development discussions should use the appropriate repository.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://github.com/aowis-org AOWIS on GitHub]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Matrix is for the broader AOWIS community and participation that does not naturally belong in a GitHub repository.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Governance &amp;amp; Legitimacy&lt;br /&gt;
 | color = turquoise&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS includes a transparent governance model to ensure:&lt;br /&gt;
&lt;br /&gt;
* open participation  &lt;br /&gt;
* clear certification processes  &lt;br /&gt;
* stable versioning  &lt;br /&gt;
* long‑term protection of the standard  &lt;br /&gt;
&lt;br /&gt;
See: [[Governance:Main_Page|Governance]].&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Navigation&lt;br /&gt;
 | color = grey&lt;br /&gt;
 | body =&lt;br /&gt;
* [[AOWIS:Table_of_Contents|Table of Contents]]  &lt;br /&gt;
* [[Reference:Glossary|Glossary]]  &lt;br /&gt;
* [[Reference:FAQ|FAQ]]  &lt;br /&gt;
* [[Reference:Change_Log|Change Log]]  &lt;br /&gt;
&lt;br /&gt;
* [https://github.com/aowis-org GitHub]&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Partners&lt;br /&gt;
 | color = indigo&lt;br /&gt;
 | body = &lt;br /&gt;
[[File:Afriticgroup.webp|250px|frameless|center|link=https://afriticgroup.com/]]&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Samuel</name></author>
	</entry>
	<entry>
		<id>https://aowis.org/index.php?title=Main_Page&amp;diff=765</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://aowis.org/index.php?title=Main_Page&amp;diff=765"/>
		<updated>2026-09-23T15:59:10Z</updated>

		<summary type="html">&lt;p&gt;Samuel: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
&lt;br /&gt;
{{MainPageBanner}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Motivation&lt;br /&gt;
 | color = teal&lt;br /&gt;
 | body = &lt;br /&gt;
&lt;br /&gt;
[[File:Countryside.jpg|class=fullwidth|center]]&lt;br /&gt;
&lt;br /&gt;
In many rural and underserved regions, including parts of Africa, wells and pumps may exist while developing and operating a reliable distribution network remains difficult. Local initiatives can lack engineering capacity, trained personnel, suitable technology, and affordable tools for operating such infrastructure sustainably.&lt;br /&gt;
&lt;br /&gt;
This practical problem is an important motivation for AOWIS. AOWIS aims to make the engineering knowledge, technical foundations, software, and operational methods needed to develop and operate water infrastructure openly available and practically usable, while supporting local training and cooperation with experienced organizations and operators.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Why AOWIS is Needed&lt;br /&gt;
 | color = turquoise&lt;br /&gt;
 | body = &lt;br /&gt;
&lt;br /&gt;
[[File:Cooperation.jpg|400px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
Water and irrigation infrastructure must often be planned, built, expanded, and operated over many decades. In some places, existing infrastructure has become fragmented across different vendors, technologies, tools, and engineering approaches. In others, communities and organizations are building coherent water infrastructure for the first time and may have limited access to engineering capacity, technical guidance, suitable software, or established operational practices.&lt;br /&gt;
&lt;br /&gt;
AOWIS provides a shared open foundation for both situations. It brings together technical standards, engineering knowledge, software, reference implementations, operational guidance, and training to support the development of water infrastructure from initial planning and design through construction, operation, maintenance, and future expansion.&lt;br /&gt;
&lt;br /&gt;
The aim is to make infrastructure understandable, interoperable, maintainable, and extensible throughout its lifecycle, while reducing dependence on individual vendors, products, suppliers, or scarce specialist expertise.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Operation Conditions&lt;br /&gt;
 | color = lightblue&lt;br /&gt;
 | body =&lt;br /&gt;
[[File:Village.jpg|250px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS is designed to operate under the real-world conditions faced by local initiatives. These include, among others:&lt;br /&gt;
&lt;br /&gt;
* unreliable power supply&lt;br /&gt;
* intermittent connectivity&lt;br /&gt;
* diverse or aging equipment&lt;br /&gt;
* limited availability of trained personnel&lt;br /&gt;
* the need for safety and autonomous operation&lt;br /&gt;
&lt;br /&gt;
AOWIS enables systems that continue to function safely and reliably, even under degraded or adverse conditions.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Facing the Challenges&lt;br /&gt;
 | color = lightblue&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS addresses these operational challenges through the following principles:&lt;br /&gt;
&lt;br /&gt;
* human-in-the-loop control&lt;br /&gt;
* offline-first operation&lt;br /&gt;
* safe fallback behavior&lt;br /&gt;
* modular and extensible logic&lt;br /&gt;
* shared infrastructure models&lt;br /&gt;
* training programs for local operators&lt;br /&gt;
* transparent governance&lt;br /&gt;
&lt;br /&gt;
The goal is to make essential systems &#039;&#039;&#039;robust, maintainable, and locally operable&#039;&#039;&#039;.&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
| title = Software &amp;amp; Downloads&lt;br /&gt;
| color = green&lt;br /&gt;
| body =&lt;br /&gt;
[[File:GUI ky4 3d.png|400px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS includes an open-source software platform for &#039;&#039;&#039;modelling, simulating, visualizing, monitoring, and operating water infrastructure&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The current software includes a network editor and monitoring interface, hydraulic and water-quality simulation using [[External:EPANET:Main Page|EPANET]], geographic maps and terrain visualization, and support for local and standalone operation. Development of the AOWIS Controller is progressing toward a complete open-source SCADA and operational management platform..&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://download.aowis.org Download the AOWIS Controller (development snapshot)]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* [https://github.com/aowis-org Source code on GitHub]&lt;br /&gt;
* [[#Roadmap|Software development roadmap]]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Start Here&lt;br /&gt;
 | color = yellow&lt;br /&gt;
 | body =&lt;br /&gt;
If you are new to AOWIS, begin with:&lt;br /&gt;
&lt;br /&gt;
* [[Concepts:Design_Philosophy|Design Philosophy]]  &lt;br /&gt;
* [[Standard:Definitions|Definitions]]  &lt;br /&gt;
* [[Standard:Normative_Requirements|Normative Requirements]]  &lt;br /&gt;
* [[Modules:Module_Template|Module Template]]  &lt;br /&gt;
* [[AOWIS:Contributor_Guide_External|Contributor Guide - External]]&lt;br /&gt;
* [[AOWIS:Contributor_Guide_Internal|Contributor Guide - Internal]]&lt;br /&gt;
* [[AOWIS:Writing_Style_Guide|Writing Style Guide]]&lt;br /&gt;
* [[AOWIS:AI_Usage_Guide|AI Usage Guide]]&lt;br /&gt;
* [[AOWIS:Research_Form_Guide|Research Form Guide]]&lt;br /&gt;
* [[AOWIS:Naming_Convention_Specification|Naming Convention Specification]]&lt;br /&gt;
* [[AOWIS:Change_Log__Versioning|Change Log &amp;amp; Versioning]]&lt;br /&gt;
* [[AOWIS:Wiki|This Wiki]]&lt;br /&gt;
&lt;br /&gt;
These pages explain the foundations of AOWIS, how the AOWIS Standard is structured, and how to use and contribute to the project and its documentation.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = List of Requirement Pages&lt;br /&gt;
 | color = brown&lt;br /&gt;
 | body = &lt;br /&gt;
This index lists AOWIS pages that define normative requirements (MUST/SHOULD/MAY statements) and conformance rules.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Dev Rules&#039;&#039;&#039; — specs for writing and maintaining AOWIS&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;REQ-AI:&#039;&#039;&#039; [[AOWIS:AI_Usage_Guide|AI Usage Guide]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Technical Standard&#039;&#039;&#039; — system behavior and data models&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;REQ-MEAS, REQ-MEAS-UI:&#039;&#039;&#039; [[Measurement:Units|Unit System Requirements]]&lt;br /&gt;
* &#039;&#039;&#039;REQ-MEAS-UNI:&#039;&#039;&#039; [[Measurement:Canonical_Units|Canonical Units]]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = AOWIS Documentation Structure&lt;br /&gt;
 | color = purple&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS documentation is organized into dedicated namespaces with clearly separated purposes.&lt;br /&gt;
&lt;br /&gt;
The [[Standard:Main_Page|Standard]] namespace contains the normative requirements that define AOWIS compliance. The other namespaces provide the motivation, concepts, engineering knowledge, architectures, operational models, implementation guidance, reference designs, training material, and supporting information needed to understand, implement, and operate AOWIS systems.&lt;br /&gt;
&lt;br /&gt;
* [[Motivation:Main_Page|Motivation]] – Causal justification of design requirements based on real-world failures, constraints, and operational realities.&lt;br /&gt;
* [[Standard:Main_Page|Standard]] – The normative core of AOWIS. Defines requirements and definitions specifying what AOWIS-compliant systems MUST, SHOULD, or MAY do.&lt;br /&gt;
* [[Concepts:Main_Page|Concepts]] – Core ideas, philosophy, rationale, and contextual understanding that explain AOWIS without prescribing a specific implementation.&lt;br /&gt;
* [[Architecture:Main_Page|Architecture]] – High-level system structure, including controllers, layers, communication, data flows, and their interactions.&lt;br /&gt;
* [[Infrastructure:Main_Page|Infrastructure]] – Physical technologies, systems, and components used in AOWIS deployments. Infrastructure pages describe classes of physical systems rather than specific implementation blueprints.&lt;br /&gt;
* [[Measurement:Main_Page|Measurement]] – Definition and handling of sensor data, manual measurements, calibration, uncertainty, and derived physical values.&lt;br /&gt;
* [[Data:Main_Page|Data]] – Data models, schemas, logging structures, synchronization formats, and data lifecycle rules.&lt;br /&gt;
* [[Operations:Main_Page|Operations]] – Runtime behavior, control logic, state transitions, fallback behavior, and decision-making during system operation.&lt;br /&gt;
* [[Modules:Main_Page|Modules]] – Reusable functional extensions that provide domain-specific capabilities within AOWIS.&lt;br /&gt;
* [[Reference:Main_Page|Reference]] – Non-normative concrete implementations, engineering blueprints, example deployments, and validated design patterns showing specific ways AOWIS systems may be built.&lt;br /&gt;
* [[Databases:Main_Page|Databases]] – Federated knowledge bases and structured supporting information used by AOWIS implementations.&lt;br /&gt;
* [[Governance:Main_Page|Governance]] – Certification, compliance, auditing, trust, licensing, versioning, and organizational governance.&lt;br /&gt;
* [[Training:Main_Page|Training]] – Operator education, technical training, field guidance, documentation literacy, and capacity building.&lt;br /&gt;
* [[External:Main_Page|External]] – External projects, standards, technologies, and systems that relate to or influence AOWIS.&lt;br /&gt;
&lt;br /&gt;
* [[Regions:Main_Page|Regions]] – Geographic, environmental, hydrological, climatic, socioeconomic, and infrastructure context for areas in which AOWIS is researched, planned, or deployed.&lt;br /&gt;
&lt;br /&gt;
For a full overview, see the [[AOWIS:Table_of_Contents|Table of Contents]].&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Roadmap&lt;br /&gt;
 | color = grey&lt;br /&gt;
 | body =&lt;br /&gt;
[[File:Boring.jpg|250px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS has progressed beyond its initial conceptual phase. A substantial software foundation for modelling, simulating, visualizing, and eventually operating water infrastructure is under active development.&lt;br /&gt;
&lt;br /&gt;
The current software stack already includes:&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Shared infrastructure model&#039;&#039;&#039;&lt;br /&gt;
: A common, solver-independent representation of water infrastructure used throughout the AOWIS software stack.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-MODEL GitHub AOWIS-SERVER-MODEL]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Hydraulic and water-quality simulation&#039;&#039;&#039;&lt;br /&gt;
: EPANET integration for hydraulic and water-quality simulation, network import/export, controls, rules, diagnostics, and simulation results. Integration of &#039;&#039;&#039;EPANET-MSX&#039;&#039;&#039; is also being developed.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-EPANET GitHub AOWIS-SERVER-EPANET]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Network editor and monitoring interface&#039;&#039;&#039;&lt;br /&gt;
: A graphical application for creating, inspecting, simulating, and visualizing water networks, including geographic maps and terrain-aware 3D visualization.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-GUI GitHub AOWIS-SERVER-GUI]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Geographic and terrain infrastructure&#039;&#039;&#039;&lt;br /&gt;
: Mapping, elevation data, basemaps, terrain visualization, geographic placement, and local caching.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-MAP GitHub AOWIS-SERVER-MAP]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Local and standalone operation&#039;&#039;&#039;&lt;br /&gt;
: Support for deployments that do not depend on continuous Internet or cloud connectivity.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-Standalone GitHub AOWIS-SERVER-Standalone]&lt;br /&gt;
&lt;br /&gt;
The software remains under active development and should not yet be considered a complete production SCADA system.&lt;br /&gt;
&lt;br /&gt;
The next major stage is to connect the existing modelling and simulation environment to &#039;&#039;&#039;real infrastructure in continuous operation&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The AOWIS software platform is intended to develop into a complete open-source SCADA, infrastructure modelling, simulation, and operational management platform in which planning, live monitoring, control, historical data, maintenance, and simulation operate on the same shared infrastructure model.&lt;br /&gt;
&lt;br /&gt;
This includes telemetry, sensors and actuators, alarms and historian functions, local and remote control, automation with safe fallback behaviour, and model-assisted operation using measured and simulated system behaviour.&lt;br /&gt;
&lt;br /&gt;
EPANET currently provides the primary hydraulic and water-quality simulation engine, but AOWIS is not designed solely as an EPANET frontend. EPANET is one solver integrated into a broader, solver-independent architecture.&lt;br /&gt;
&lt;br /&gt;
The long-term objective is to connect the complete infrastructure lifecycle:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;survey and planning → engineering and simulation → construction → commissioning → monitoring → control → maintenance → analysis → expansion&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[[AOWIS:Roadmap|Read the full roadmap →]]&#039;&#039;&#039;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
| title = Community &amp;amp; Participation&lt;br /&gt;
| color = blue&lt;br /&gt;
| body =&lt;br /&gt;
&lt;br /&gt;
AOWIS is an open project, and participation is welcome from anyone interested in its goals — including engineers, developers, NGOs, operators, researchers, technicians, students, and people with practical experience in water and irrigation infrastructure.&lt;br /&gt;
&lt;br /&gt;
For &#039;&#039;&#039;discussion, planning, questions, documentation, infrastructure, field projects, standards, research, and other forms of participation&#039;&#039;&#039;, AOWIS uses &#039;&#039;&#039;Matrix&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The AOWIS Matrix server has several &#039;&#039;&#039;public spaces and rooms&#039;&#039;&#039; for different topics. Join those relevant to your interests. For general questions or help finding the right place, start here:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://matrix.to/#/#support:aowis.org AOWIS Support — #support:aowis.org]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Any Matrix account can join public AOWIS spaces and rooms.&lt;br /&gt;
&lt;br /&gt;
If you are new to Matrix:&lt;br /&gt;
&lt;br /&gt;
* [https://matrix.org/try-matrix/ Learn about Matrix and create an account]&lt;br /&gt;
* [https://element.io/ Element] — Matrix client for web, desktop, and mobile&lt;br /&gt;
* [https://fluffychat.im/ FluffyChat] — simple Matrix client for several platforms&lt;br /&gt;
&lt;br /&gt;
The same Matrix account can be used with different clients.&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;AOWIS Matrix Accounts&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Participants may also request an account on the AOWIS Matrix homeserver, giving them an ID such as &#039;&#039;&#039;@name:aowis.org&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
To reduce automated registrations and abuse, accounts are created on request. Please send a short introduction telling us who you are, what interests you about AOWIS, and where you would like to participate: [[File:Mtx.png|120px|frameless|alt=Email address for requesting an AOWIS Matrix account]]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Software Development&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Software development remains on &#039;&#039;&#039;GitHub&#039;&#039;&#039;. Bug reports, pull requests, source-code contributions, and repository-specific development discussions should use the appropriate repository.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://github.com/aowis-org AOWIS on GitHub]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Matrix is for the broader AOWIS community and participation that does not naturally belong in a GitHub repository.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Governance &amp;amp; Legitimacy&lt;br /&gt;
 | color = turquoise&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS includes a transparent governance model to ensure:&lt;br /&gt;
&lt;br /&gt;
* open participation  &lt;br /&gt;
* clear certification processes  &lt;br /&gt;
* stable versioning  &lt;br /&gt;
* long‑term protection of the standard  &lt;br /&gt;
&lt;br /&gt;
See: [[Governance:Main_Page|Governance]].&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Navigation&lt;br /&gt;
 | color = grey&lt;br /&gt;
 | body =&lt;br /&gt;
* [[AOWIS:Table_of_Contents|Table of Contents]]  &lt;br /&gt;
* [[Reference:Glossary|Glossary]]  &lt;br /&gt;
* [[Reference:FAQ|FAQ]]  &lt;br /&gt;
* [[Reference:Change_Log|Change Log]]  &lt;br /&gt;
&lt;br /&gt;
* [https://github.com/aowis-org GitHub]&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Partners&lt;br /&gt;
 | color = indigo&lt;br /&gt;
 | body = &lt;br /&gt;
[[File:Afriticgroup.webp|250px|frameless|center|link=https://afriticgroup.com/]]&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Samuel</name></author>
	</entry>
	<entry>
		<id>https://aowis.org/index.php?title=Main_Page&amp;diff=764</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://aowis.org/index.php?title=Main_Page&amp;diff=764"/>
		<updated>2026-09-23T15:57:58Z</updated>

		<summary type="html">&lt;p&gt;Samuel: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
&lt;br /&gt;
{{MainPageBanner}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Motivation&lt;br /&gt;
 | color = teal&lt;br /&gt;
 | body = &lt;br /&gt;
&lt;br /&gt;
[[File:Countryside.jpg|class=fullwidth|center]]&lt;br /&gt;
&lt;br /&gt;
In many rural and underserved regions, including parts of Africa, wells and pumps may exist while developing and operating a reliable distribution network remains difficult. Local initiatives can lack engineering capacity, trained personnel, suitable technology, and affordable tools for operating such infrastructure sustainably.&lt;br /&gt;
&lt;br /&gt;
This practical problem is an important motivation for AOWIS. AOWIS aims to make the engineering knowledge, technical foundations, software, and operational methods needed to develop and operate water infrastructure openly available and practically usable, while supporting local training and cooperation with experienced organizations and operators.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Why AOWIS is Needed&lt;br /&gt;
 | color = turquoise&lt;br /&gt;
 | body = &lt;br /&gt;
&lt;br /&gt;
[[File:Cooperation.jpg|400px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
Water and irrigation infrastructure must often be planned, built, expanded, and operated over many decades. In some places, existing infrastructure has become fragmented across different vendors, technologies, tools, and engineering approaches. In others, communities and organizations are building coherent water infrastructure for the first time and may have limited access to engineering capacity, technical guidance, suitable software, or established operational practices.&lt;br /&gt;
&lt;br /&gt;
AOWIS provides a shared open foundation for both situations. It brings together technical standards, engineering knowledge, software, reference implementations, operational guidance, and training to support the development of water infrastructure from initial planning and design through construction, operation, maintenance, and future expansion.&lt;br /&gt;
&lt;br /&gt;
The aim is to make infrastructure understandable, interoperable, maintainable, and extensible throughout its lifecycle, while reducing dependence on individual vendors, products, suppliers, or scarce specialist expertise.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Operation Conditions&lt;br /&gt;
 | color = lightblue&lt;br /&gt;
 | body =&lt;br /&gt;
[[File:Village.jpg|250px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS is designed to operate under the real-world conditions faced by local initiatives. These include, among others:&lt;br /&gt;
&lt;br /&gt;
* unreliable power supply&lt;br /&gt;
* intermittent connectivity&lt;br /&gt;
* diverse or aging equipment&lt;br /&gt;
* limited availability of trained personnel&lt;br /&gt;
* the need for safety and autonomous operation&lt;br /&gt;
&lt;br /&gt;
AOWIS enables systems that continue to function safely and reliably, even under degraded or adverse conditions.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Facing the Challenges&lt;br /&gt;
 | color = lightblue&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS addresses these operational challenges through the following principles:&lt;br /&gt;
&lt;br /&gt;
* human-in-the-loop control&lt;br /&gt;
* offline-first operation&lt;br /&gt;
* safe fallback behavior&lt;br /&gt;
* modular and extensible logic&lt;br /&gt;
* shared infrastructure models&lt;br /&gt;
* training programs for local operators&lt;br /&gt;
* transparent governance&lt;br /&gt;
&lt;br /&gt;
The goal is to make essential systems &#039;&#039;&#039;robust, maintainable, and locally operable&#039;&#039;&#039;.&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
| title = Software &amp;amp; Downloads&lt;br /&gt;
| color = green&lt;br /&gt;
| body =&lt;br /&gt;
[[File:GUI ky4 3d.png|400px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS includes an open-source software platform for &#039;&#039;&#039;modelling, simulating, visualizing, monitoring, and operating water infrastructure&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The current software includes a network editor and monitoring interface, hydraulic and water-quality simulation using [[External:EPANET:Main Page|EPANET]], geographic maps and terrain visualization, and support for local and standalone operation. Development of the AOWIS Controller is progressing toward a complete open-source SCADA and operational management platform..&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://download.aowis.org Download the AOWIS Controller (development snapshot)]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* [https://github.com/aowis-org Source code on GitHub]&lt;br /&gt;
* [[#Roadmap|Software development roadmap]]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Start Here&lt;br /&gt;
 | color = yellow&lt;br /&gt;
 | body =&lt;br /&gt;
If you are new to AOWIS, begin with:&lt;br /&gt;
&lt;br /&gt;
* [[Concepts:Design_Philosophy|Design Philosophy]]  &lt;br /&gt;
* [[Standard:Definitions|Definitions]]  &lt;br /&gt;
* [[Standard:Normative_Requirements|Normative Requirements]]  &lt;br /&gt;
* [[Modules:Module_Template|Module Template]]  &lt;br /&gt;
* [[AOWIS:Contributor_Guide_External|Contributor Guide - External]]&lt;br /&gt;
* [[AOWIS:Contributor_Guide_Internal|Contributor Guide - Internal]]&lt;br /&gt;
* [[AOWIS:Writing_Style_Guide|Writing Style Guide]]&lt;br /&gt;
* [[AOWIS:AI_Usage_Guide|AI Usage Guide]]&lt;br /&gt;
* [[AOWIS:Research_Form_Guide|Research Form Guide]]&lt;br /&gt;
* [[AOWIS:Naming_Convention_Specification|Naming Convention Specification]]&lt;br /&gt;
* [[AOWIS:Change_Log__Versioning|Change Log &amp;amp; Versioning]]&lt;br /&gt;
* [[AOWIS:Wiki|This Wiki]]&lt;br /&gt;
&lt;br /&gt;
These pages explain the foundations of AOWIS, how the AOWIS Standard is structured, and how to use and contribute to the project and its documentation.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = List of Requirement Pages&lt;br /&gt;
 | color = brown&lt;br /&gt;
 | body = &lt;br /&gt;
This index lists AOWIS pages that define normative requirements (MUST/SHOULD/MAY statements) and conformance rules.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Dev Rules&#039;&#039;&#039; — specs for writing and maintaining AOWIS&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;REQ-AI:&#039;&#039;&#039; [[AOWIS:AI_Usage_Guide|AI Usage Guide]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Technical Standard&#039;&#039;&#039; — system behavior and data models&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;REQ-MEAS, REQ-MEAS-UI:&#039;&#039;&#039; [[Measurement:Units|Unit System Requirements]]&lt;br /&gt;
* &#039;&#039;&#039;REQ-MEAS-UNI:&#039;&#039;&#039; [[Measurement:Canonical_Units|Canonical Units]]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = AOWIS Documentation Structure&lt;br /&gt;
 | color = purple&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS documentation is organized into dedicated namespaces with clearly separated purposes.&lt;br /&gt;
&lt;br /&gt;
The [[Standard:Main_Page|Standard]] namespace contains the normative requirements that define AOWIS compliance. The other namespaces provide the motivation, concepts, engineering knowledge, architectures, operational models, implementation guidance, reference designs, training material, and supporting information needed to understand, implement, and operate AOWIS systems.&lt;br /&gt;
&lt;br /&gt;
* [[Motivation:Main_Page|Motivation]] – Causal justification of design requirements based on real-world failures, constraints, and operational realities.&lt;br /&gt;
* [[Standard:Main_Page|Standard]] – The normative core of AOWIS. Defines requirements and definitions specifying what AOWIS-compliant systems MUST, SHOULD, or MAY do.&lt;br /&gt;
* [[Concepts:Main_Page|Concepts]] – Core ideas, philosophy, rationale, and contextual understanding that explain AOWIS without prescribing a specific implementation.&lt;br /&gt;
* [[Architecture:Main_Page|Architecture]] – High-level system structure, including controllers, layers, communication, data flows, and their interactions.&lt;br /&gt;
* [[Infrastructure:Main_Page|Infrastructure]] – Physical technologies, systems, and components used in AOWIS deployments. Infrastructure pages describe classes of physical systems rather than specific implementation blueprints.&lt;br /&gt;
* [[Measurement:Main_Page|Measurement]] – Definition and handling of sensor data, manual measurements, calibration, uncertainty, and derived physical values.&lt;br /&gt;
* [[Data:Main_Page|Data]] – Data models, schemas, logging structures, synchronization formats, and data lifecycle rules.&lt;br /&gt;
* [[Operations:Main_Page|Operations]] – Runtime behavior, control logic, state transitions, fallback behavior, and decision-making during system operation.&lt;br /&gt;
* [[Modules:Main_Page|Modules]] – Reusable functional extensions that provide domain-specific capabilities within AOWIS.&lt;br /&gt;
* [[Reference:Main_Page|Reference]] – Non-normative concrete implementations, engineering blueprints, example deployments, and validated design patterns showing specific ways AOWIS systems may be built.&lt;br /&gt;
* [[Databases:Main_Page|Databases]] – Federated knowledge bases and structured supporting information used by AOWIS implementations.&lt;br /&gt;
* [[Governance:Main_Page|Governance]] – Certification, compliance, auditing, trust, licensing, versioning, and organizational governance.&lt;br /&gt;
* [[Training:Main_Page|Training]] – Operator education, technical training, field guidance, documentation literacy, and capacity building.&lt;br /&gt;
* [[External:Main_Page|External]] – External projects, standards, technologies, and systems that relate to or influence AOWIS.&lt;br /&gt;
&lt;br /&gt;
* [[Regions:Main_Page|Regions]] – Geographic, environmental, hydrological, climatic, socioeconomic, and infrastructure context for areas in which AOWIS is researched, planned, or deployed.&lt;br /&gt;
&lt;br /&gt;
For a full overview, see the [[AOWIS:Table_of_Contents|Table of Contents]].&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Roadmap&lt;br /&gt;
 | color = grey&lt;br /&gt;
 | body =&lt;br /&gt;
[[File:Boring.jpg|250px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS has progressed beyond its initial conceptual phase. A substantial software foundation for modelling, simulating, visualizing, and eventually operating water infrastructure is under active development.&lt;br /&gt;
&lt;br /&gt;
The current software stack already includes:&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Shared infrastructure model&#039;&#039;&#039;&lt;br /&gt;
: A common, solver-independent representation of water infrastructure used throughout the AOWIS software stack.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-MODEL GitHub AOWIS-SERVER-MODEL]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Hydraulic and water-quality simulation&#039;&#039;&#039;&lt;br /&gt;
: EPANET integration for hydraulic and water-quality simulation, network import/export, controls, rules, diagnostics, and simulation results. Integration of &#039;&#039;&#039;EPANET-MSX&#039;&#039;&#039; is also being developed.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-EPANET GitHub AOWIS-SERVER-EPANET]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Network editor and monitoring interface&#039;&#039;&#039;&lt;br /&gt;
: A graphical application for creating, inspecting, simulating, and visualizing water networks, including geographic maps and terrain-aware 3D visualization.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-GUI GitHub AOWIS-SERVER-GUI]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Geographic and terrain infrastructure&#039;&#039;&#039;&lt;br /&gt;
: Mapping, elevation data, basemaps, terrain visualization, geographic placement, and local caching.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-MAP GitHub AOWIS-SERVER-MAP]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Local and standalone operation&#039;&#039;&#039;&lt;br /&gt;
: Support for deployments that do not depend on continuous Internet or cloud connectivity.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-Standalone GitHub AOWIS-SERVER-Standalone]&lt;br /&gt;
&lt;br /&gt;
The software remains under active development and should not yet be considered a complete production SCADA system.&lt;br /&gt;
&lt;br /&gt;
The next major stage is to connect the existing modelling and simulation environment to &#039;&#039;&#039;real infrastructure in continuous operation&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The AOWIS software platform is intended to develop into a complete open-source SCADA, infrastructure modelling, simulation, and operational management platform in which planning, live monitoring, control, historical data, maintenance, and simulation operate on the same shared infrastructure model.&lt;br /&gt;
&lt;br /&gt;
This includes telemetry, sensors and actuators, alarms and historian functions, local and remote control, automation with safe fallback behaviour, and model-assisted operation using measured and simulated system behaviour.&lt;br /&gt;
&lt;br /&gt;
EPANET currently provides the primary hydraulic and water-quality simulation engine, but AOWIS is not designed solely as an EPANET frontend. EPANET is one solver integrated into a broader, solver-independent architecture.&lt;br /&gt;
&lt;br /&gt;
The long-term objective is to connect the complete infrastructure lifecycle:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;survey and planning → engineering and simulation → construction → commissioning → monitoring → control → maintenance → analysis → expansion&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[[AOWIS:Roadmap|Read the full roadmap →]]&#039;&#039;&#039;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
| title = Community &amp;amp; Participation&lt;br /&gt;
| color = blue&lt;br /&gt;
| body =&lt;br /&gt;
&lt;br /&gt;
AOWIS is an open project, and participation is welcome from anyone interested in its goals — including engineers, developers, NGOs, operators, researchers, technicians, students, and people with practical experience in water and irrigation infrastructure.&lt;br /&gt;
&lt;br /&gt;
For &#039;&#039;&#039;discussion, planning, questions, documentation, infrastructure, field projects, standards, research, and other forms of participation&#039;&#039;&#039;, AOWIS uses &#039;&#039;&#039;Matrix&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The AOWIS Matrix server has several &#039;&#039;&#039;public spaces and rooms&#039;&#039;&#039; for different topics. Join those relevant to your interests. For general questions or help finding the right place, start here:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://matrix.to/#/#support:aowis.org AOWIS Support — #support:aowis.org]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
You do &#039;&#039;&#039;not&#039;&#039;&#039; need an AOWIS account to participate. Any Matrix account can join public AOWIS spaces and rooms.&lt;br /&gt;
&lt;br /&gt;
If you are new to Matrix:&lt;br /&gt;
&lt;br /&gt;
* [https://matrix.org/try-matrix/ Learn about Matrix and create an account]&lt;br /&gt;
* [https://element.io/ Element] — Matrix client for web, desktop, and mobile&lt;br /&gt;
* [https://fluffychat.im/ FluffyChat] — simple Matrix client for several platforms&lt;br /&gt;
&lt;br /&gt;
The same Matrix account can be used with different clients.&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;AOWIS Matrix Accounts&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Participants may also request an account on the AOWIS Matrix homeserver, giving them an ID such as &#039;&#039;&#039;@name:aowis.org&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
To reduce automated registrations and abuse, accounts are created on request. Please send a short introduction telling us who you are, what interests you about AOWIS, and where you would like to participate: [[File:Mtx.png|120px|frameless|alt=Email address for requesting an AOWIS Matrix account]]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Software Development&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Software development remains on &#039;&#039;&#039;GitHub&#039;&#039;&#039;. Bug reports, pull requests, source-code contributions, and repository-specific development discussions should use the appropriate repository.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://github.com/aowis-org AOWIS on GitHub]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Matrix is for the broader AOWIS community and participation that does not naturally belong in a GitHub repository.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Governance &amp;amp; Legitimacy&lt;br /&gt;
 | color = turquoise&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS includes a transparent governance model to ensure:&lt;br /&gt;
&lt;br /&gt;
* open participation  &lt;br /&gt;
* clear certification processes  &lt;br /&gt;
* stable versioning  &lt;br /&gt;
* long‑term protection of the standard  &lt;br /&gt;
&lt;br /&gt;
See: [[Governance:Main_Page|Governance]].&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Navigation&lt;br /&gt;
 | color = grey&lt;br /&gt;
 | body =&lt;br /&gt;
* [[AOWIS:Table_of_Contents|Table of Contents]]  &lt;br /&gt;
* [[Reference:Glossary|Glossary]]  &lt;br /&gt;
* [[Reference:FAQ|FAQ]]  &lt;br /&gt;
* [[Reference:Change_Log|Change Log]]  &lt;br /&gt;
&lt;br /&gt;
* [https://github.com/aowis-org GitHub]&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Partners&lt;br /&gt;
 | color = indigo&lt;br /&gt;
 | body = &lt;br /&gt;
[[File:Afriticgroup.webp|250px|frameless|center|link=https://afriticgroup.com/]]&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Samuel</name></author>
	</entry>
	<entry>
		<id>https://aowis.org/index.php?title=Main_Page&amp;diff=763</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://aowis.org/index.php?title=Main_Page&amp;diff=763"/>
		<updated>2026-09-23T15:56:59Z</updated>

		<summary type="html">&lt;p&gt;Samuel: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
&lt;br /&gt;
{{MainPageBanner}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Motivation&lt;br /&gt;
 | color = teal&lt;br /&gt;
 | body = &lt;br /&gt;
&lt;br /&gt;
[[File:Countryside.jpg|class=fullwidth|center]]&lt;br /&gt;
&lt;br /&gt;
In many rural and underserved regions, including parts of Africa, wells and pumps may exist while developing and operating a reliable distribution network remains difficult. Local initiatives can lack engineering capacity, trained personnel, suitable technology, and affordable tools for operating such infrastructure sustainably.&lt;br /&gt;
&lt;br /&gt;
This practical problem is an important motivation for AOWIS. AOWIS aims to make the engineering knowledge, technical foundations, software, and operational methods needed to develop and operate water infrastructure openly available and practically usable, while supporting local training and cooperation with experienced organizations and operators.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Why AOWIS is Needed&lt;br /&gt;
 | color = turquoise&lt;br /&gt;
 | body = &lt;br /&gt;
&lt;br /&gt;
[[File:Cooperation.jpg|400px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
Water and irrigation infrastructure must often be planned, built, expanded, and operated over many decades. In some places, existing infrastructure has become fragmented across different vendors, technologies, tools, and engineering approaches. In others, communities and organizations are building coherent water infrastructure for the first time and may have limited access to engineering capacity, technical guidance, suitable software, or established operational practices.&lt;br /&gt;
&lt;br /&gt;
AOWIS provides a shared open foundation for both situations. It brings together technical standards, engineering knowledge, software, reference implementations, operational guidance, and training to support the development of water infrastructure from initial planning and design through construction, operation, maintenance, and future expansion.&lt;br /&gt;
&lt;br /&gt;
The aim is to make infrastructure understandable, interoperable, maintainable, and extensible throughout its lifecycle, while reducing dependence on individual vendors, products, suppliers, or scarce specialist expertise.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Operation Conditions&lt;br /&gt;
 | color = lightblue&lt;br /&gt;
 | body =&lt;br /&gt;
[[File:Village.jpg|250px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS is designed to operate under the real-world conditions faced by local initiatives. These include, among others:&lt;br /&gt;
&lt;br /&gt;
* unreliable power supply&lt;br /&gt;
* intermittent connectivity&lt;br /&gt;
* diverse or aging equipment&lt;br /&gt;
* limited availability of trained personnel&lt;br /&gt;
* the need for safety and autonomous operation&lt;br /&gt;
&lt;br /&gt;
AOWIS enables systems that continue to function safely and reliably, even under degraded or adverse conditions.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Facing the Challenges&lt;br /&gt;
 | color = lightblue&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS addresses these operational challenges through the following principles:&lt;br /&gt;
&lt;br /&gt;
* human-in-the-loop control&lt;br /&gt;
* offline-first operation&lt;br /&gt;
* safe fallback behavior&lt;br /&gt;
* modular and extensible logic&lt;br /&gt;
* shared infrastructure models&lt;br /&gt;
* training programs for local operators&lt;br /&gt;
* transparent governance&lt;br /&gt;
&lt;br /&gt;
The goal is to make essential systems &#039;&#039;&#039;robust, maintainable, and locally operable&#039;&#039;&#039;.&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
| title = Software &amp;amp; Downloads&lt;br /&gt;
| color = green&lt;br /&gt;
| body =&lt;br /&gt;
[[File:GUI ky4 3d.png|400px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS includes an open-source software platform for &#039;&#039;&#039;modelling, simulating, visualizing, monitoring, and operating water infrastructure&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The current software includes a network editor and monitoring interface, hydraulic and water-quality simulation using [[External:EPANET:Main Page|EPANET]], geographic maps and terrain visualization, and support for local and standalone operation. Development of the AOWIS Controller is progressing toward a complete open-source SCADA and operational management platform..&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://download.aowis.org Download the AOWIS Controller (development snapshot)]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* [https://github.com/aowis-org Source code on GitHub]&lt;br /&gt;
* [[#Roadmap|Software development roadmap]]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Start Here&lt;br /&gt;
 | color = yellow&lt;br /&gt;
 | body =&lt;br /&gt;
If you are new to AOWIS, begin with:&lt;br /&gt;
&lt;br /&gt;
* [[Concepts:Design_Philosophy|Design Philosophy]]  &lt;br /&gt;
* [[Standard:Definitions|Definitions]]  &lt;br /&gt;
* [[Standard:Normative_Requirements|Normative Requirements]]  &lt;br /&gt;
* [[Modules:Module_Template|Module Template]]  &lt;br /&gt;
* [[AOWIS:Contributor_Guide_External|Contributor Guide - External]]&lt;br /&gt;
* [[AOWIS:Contributor_Guide_Internal|Contributor Guide - Internal]]&lt;br /&gt;
* [[AOWIS:Writing_Style_Guide|Writing Style Guide]]&lt;br /&gt;
* [[AOWIS:AI_Usage_Guide|AI Usage Guide]]&lt;br /&gt;
* [[AOWIS:Research_Form_Guide|Research Form Guide]]&lt;br /&gt;
* [[AOWIS:Naming_Convention_Specification|Naming Convention Specification]]&lt;br /&gt;
* [[AOWIS:Change_Log__Versioning|Change Log &amp;amp; Versioning]]&lt;br /&gt;
* [[AOWIS:Wiki|This Wiki]]&lt;br /&gt;
&lt;br /&gt;
These pages explain the foundations of AOWIS, how the AOWIS Standard is structured, and how to use and contribute to the project and its documentation.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = List of Requirement Pages&lt;br /&gt;
 | color = brown&lt;br /&gt;
 | body = &lt;br /&gt;
This index lists AOWIS pages that define normative requirements (MUST/SHOULD/MAY statements) and conformance rules.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Dev Rules&#039;&#039;&#039; — specs for writing and maintaining AOWIS&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;REQ-AI:&#039;&#039;&#039; [[AOWIS:AI_Usage_Guide|AI Usage Guide]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Technical Standard&#039;&#039;&#039; — system behavior and data models&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;REQ-MEAS, REQ-MEAS-UI:&#039;&#039;&#039; [[Measurement:Units|Unit System Requirements]]&lt;br /&gt;
* &#039;&#039;&#039;REQ-MEAS-UNI:&#039;&#039;&#039; [[Measurement:Canonical_Units|Canonical Units]]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = AOWIS Documentation Structure&lt;br /&gt;
 | color = purple&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS documentation is organized into dedicated namespaces with clearly separated purposes.&lt;br /&gt;
&lt;br /&gt;
The [[Standard:Main_Page|Standard]] namespace contains the normative requirements that define AOWIS compliance. The other namespaces provide the motivation, concepts, engineering knowledge, architectures, operational models, implementation guidance, reference designs, training material, and supporting information needed to understand, implement, and operate AOWIS systems.&lt;br /&gt;
&lt;br /&gt;
* [[Motivation:Main_Page|Motivation]] – Causal justification of design requirements based on real-world failures, constraints, and operational realities.&lt;br /&gt;
* [[Standard:Main_Page|Standard]] – The normative core of AOWIS. Defines requirements and definitions specifying what AOWIS-compliant systems MUST, SHOULD, or MAY do.&lt;br /&gt;
* [[Concepts:Main_Page|Concepts]] – Core ideas, philosophy, rationale, and contextual understanding that explain AOWIS without prescribing a specific implementation.&lt;br /&gt;
* [[Architecture:Main_Page|Architecture]] – High-level system structure, including controllers, layers, communication, data flows, and their interactions.&lt;br /&gt;
* [[Infrastructure:Main_Page|Infrastructure]] – Physical technologies, systems, and components used in AOWIS deployments. Infrastructure pages describe classes of physical systems rather than specific implementation blueprints.&lt;br /&gt;
* [[Measurement:Main_Page|Measurement]] – Definition and handling of sensor data, manual measurements, calibration, uncertainty, and derived physical values.&lt;br /&gt;
* [[Data:Main_Page|Data]] – Data models, schemas, logging structures, synchronization formats, and data lifecycle rules.&lt;br /&gt;
* [[Operations:Main_Page|Operations]] – Runtime behavior, control logic, state transitions, fallback behavior, and decision-making during system operation.&lt;br /&gt;
* [[Modules:Main_Page|Modules]] – Reusable functional extensions that provide domain-specific capabilities within AOWIS.&lt;br /&gt;
* [[Reference:Main_Page|Reference]] – Non-normative concrete implementations, engineering blueprints, example deployments, and validated design patterns showing specific ways AOWIS systems may be built.&lt;br /&gt;
* [[Databases:Main_Page|Databases]] – Federated knowledge bases and structured supporting information used by AOWIS implementations.&lt;br /&gt;
* [[Governance:Main_Page|Governance]] – Certification, compliance, auditing, trust, licensing, versioning, and organizational governance.&lt;br /&gt;
* [[Training:Main_Page|Training]] – Operator education, technical training, field guidance, documentation literacy, and capacity building.&lt;br /&gt;
* [[External:Main_Page|External]] – External projects, standards, technologies, and systems that relate to or influence AOWIS.&lt;br /&gt;
&lt;br /&gt;
* [[Regions:Main_Page|Regions]] – Geographic, environmental, hydrological, climatic, socioeconomic, and infrastructure context for areas in which AOWIS is researched, planned, or deployed.&lt;br /&gt;
&lt;br /&gt;
For a full overview, see the [[AOWIS:Table_of_Contents|Table of Contents]].&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Roadmap&lt;br /&gt;
 | color = grey&lt;br /&gt;
 | body =&lt;br /&gt;
[[File:Boring.jpg|250px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS has progressed beyond its initial conceptual phase. A substantial software foundation for modelling, simulating, visualizing, and eventually operating water infrastructure is under active development.&lt;br /&gt;
&lt;br /&gt;
The current software stack already includes:&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Shared infrastructure model&#039;&#039;&#039;&lt;br /&gt;
: A common, solver-independent representation of water infrastructure used throughout the AOWIS software stack.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-MODEL GitHub AOWIS-SERVER-MODEL]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Hydraulic and water-quality simulation&#039;&#039;&#039;&lt;br /&gt;
: EPANET integration for hydraulic and water-quality simulation, network import/export, controls, rules, diagnostics, and simulation results. Integration of &#039;&#039;&#039;EPANET-MSX&#039;&#039;&#039; is also being developed.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-EPANET GitHub AOWIS-SERVER-EPANET]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Network editor and monitoring interface&#039;&#039;&#039;&lt;br /&gt;
: A graphical application for creating, inspecting, simulating, and visualizing water networks, including geographic maps and terrain-aware 3D visualization.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-GUI GitHub AOWIS-SERVER-GUI]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Geographic and terrain infrastructure&#039;&#039;&#039;&lt;br /&gt;
: Mapping, elevation data, basemaps, terrain visualization, geographic placement, and local caching.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-MAP GitHub AOWIS-SERVER-MAP]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Local and standalone operation&#039;&#039;&#039;&lt;br /&gt;
: Support for deployments that do not depend on continuous Internet or cloud connectivity.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-Standalone GitHub AOWIS-SERVER-Standalone]&lt;br /&gt;
&lt;br /&gt;
The software remains under active development and should not yet be considered a complete production SCADA system.&lt;br /&gt;
&lt;br /&gt;
The next major stage is to connect the existing modelling and simulation environment to &#039;&#039;&#039;real infrastructure in continuous operation&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The AOWIS software platform is intended to develop into a complete open-source SCADA, infrastructure modelling, simulation, and operational management platform in which planning, live monitoring, control, historical data, maintenance, and simulation operate on the same shared infrastructure model.&lt;br /&gt;
&lt;br /&gt;
This includes telemetry, sensors and actuators, alarms and historian functions, local and remote control, automation with safe fallback behaviour, and model-assisted operation using measured and simulated system behaviour.&lt;br /&gt;
&lt;br /&gt;
EPANET currently provides the primary hydraulic and water-quality simulation engine, but AOWIS is not designed solely as an EPANET frontend. EPANET is one solver integrated into a broader, solver-independent architecture.&lt;br /&gt;
&lt;br /&gt;
The long-term objective is to connect the complete infrastructure lifecycle:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;survey and planning → engineering and simulation → construction → commissioning → monitoring → control → maintenance → analysis → expansion&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[[AOWIS:Roadmap|Read the full roadmap →]]&#039;&#039;&#039;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
| title = Community &amp;amp; Participation&lt;br /&gt;
| color = blue&lt;br /&gt;
| body =&lt;br /&gt;
&lt;br /&gt;
AOWIS is an open project, and participation is welcome from anyone interested in its goals — including engineers, developers, NGOs, operators, researchers, technicians, students, and people with practical experience in water and agricultural infrastructure.&lt;br /&gt;
&lt;br /&gt;
For &#039;&#039;&#039;discussion, planning, questions, documentation, infrastructure, field projects, standards, research, and other forms of participation&#039;&#039;&#039;, AOWIS uses &#039;&#039;&#039;Matrix&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The AOWIS Matrix server has several &#039;&#039;&#039;public spaces and rooms&#039;&#039;&#039; for different topics. Join those relevant to your interests. For general questions or help finding the right place, start here:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://matrix.to/#/#support:aowis.org AOWIS Support — #support:aowis.org]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
You do &#039;&#039;&#039;not&#039;&#039;&#039; need an AOWIS account to participate. Any Matrix account can join public AOWIS spaces and rooms.&lt;br /&gt;
&lt;br /&gt;
If you are new to Matrix:&lt;br /&gt;
&lt;br /&gt;
* [https://matrix.org/try-matrix/ Learn about Matrix and create an account]&lt;br /&gt;
* [https://element.io/ Element] — Matrix client for web, desktop, and mobile&lt;br /&gt;
* [https://fluffychat.im/ FluffyChat] — simple Matrix client for several platforms&lt;br /&gt;
&lt;br /&gt;
The same Matrix account can be used with different clients.&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;AOWIS Matrix Accounts&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Participants may also request an account on the AOWIS Matrix homeserver, giving them an ID such as &#039;&#039;&#039;@name:aowis.org&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
To reduce automated registrations and abuse, accounts are created on request. Please send a short introduction telling us who you are, what interests you about AOWIS, and where you would like to participate: [[File:Mtx.png|120px|frameless|alt=Email address for requesting an AOWIS Matrix account]]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Software Development&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Software development remains on &#039;&#039;&#039;GitHub&#039;&#039;&#039;. Bug reports, pull requests, source-code contributions, and repository-specific development discussions should use the appropriate repository.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://github.com/aowis-org AOWIS on GitHub]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Matrix is for the broader AOWIS community and participation that does not naturally belong in a GitHub repository.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Governance &amp;amp; Legitimacy&lt;br /&gt;
 | color = turquoise&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS includes a transparent governance model to ensure:&lt;br /&gt;
&lt;br /&gt;
* open participation  &lt;br /&gt;
* clear certification processes  &lt;br /&gt;
* stable versioning  &lt;br /&gt;
* long‑term protection of the standard  &lt;br /&gt;
&lt;br /&gt;
See: [[Governance:Main_Page|Governance]].&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Navigation&lt;br /&gt;
 | color = grey&lt;br /&gt;
 | body =&lt;br /&gt;
* [[AOWIS:Table_of_Contents|Table of Contents]]  &lt;br /&gt;
* [[Reference:Glossary|Glossary]]  &lt;br /&gt;
* [[Reference:FAQ|FAQ]]  &lt;br /&gt;
* [[Reference:Change_Log|Change Log]]  &lt;br /&gt;
&lt;br /&gt;
* [https://github.com/aowis-org GitHub]&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Partners&lt;br /&gt;
 | color = indigo&lt;br /&gt;
 | body = &lt;br /&gt;
[[File:Afriticgroup.webp|250px|frameless|center|link=https://afriticgroup.com/]]&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Samuel</name></author>
	</entry>
	<entry>
		<id>https://aowis.org/index.php?title=Main_Page&amp;diff=762</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://aowis.org/index.php?title=Main_Page&amp;diff=762"/>
		<updated>2026-09-23T15:55:04Z</updated>

		<summary type="html">&lt;p&gt;Samuel: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
&lt;br /&gt;
{{MainPageBanner}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Motivation&lt;br /&gt;
 | color = teal&lt;br /&gt;
 | body = &lt;br /&gt;
&lt;br /&gt;
[[File:Countryside.jpg|class=fullwidth|center]]&lt;br /&gt;
&lt;br /&gt;
In many rural and underserved regions, including parts of Africa, wells and pumps may exist while developing and operating a reliable distribution network remains difficult. Local initiatives can lack engineering capacity, trained personnel, suitable technology, and affordable tools for operating such infrastructure sustainably.&lt;br /&gt;
&lt;br /&gt;
This practical problem is an important motivation for AOWIS. AOWIS aims to make the engineering knowledge, technical foundations, software, and operational methods needed to develop and operate water infrastructure openly available and practically usable, while supporting local training and cooperation with experienced organizations and operators.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Why AOWIS is Needed&lt;br /&gt;
 | color = turquoise&lt;br /&gt;
 | body = &lt;br /&gt;
&lt;br /&gt;
[[File:Cooperation.jpg|400px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
Water and irrigation infrastructure must often be planned, built, expanded, and operated over many decades. In some places, existing infrastructure has become fragmented across different vendors, technologies, tools, and engineering approaches. In others, communities and organizations are building coherent water infrastructure for the first time and may have limited access to engineering capacity, technical guidance, suitable software, or established operational practices.&lt;br /&gt;
&lt;br /&gt;
AOWIS provides a shared open foundation for both situations. It brings together technical standards, engineering knowledge, software, reference implementations, operational guidance, and training to support the development of water infrastructure from initial planning and design through construction, operation, maintenance, and future expansion.&lt;br /&gt;
&lt;br /&gt;
The aim is to make infrastructure understandable, interoperable, maintainable, and extensible throughout its lifecycle, while reducing dependence on individual vendors, products, suppliers, or scarce specialist expertise.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Operation Conditions&lt;br /&gt;
 | color = lightblue&lt;br /&gt;
 | body =&lt;br /&gt;
[[File:Village.jpg|250px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS is designed to operate under the real-world conditions faced by local initiatives. These include, among others:&lt;br /&gt;
&lt;br /&gt;
* unreliable power supply&lt;br /&gt;
* intermittent connectivity&lt;br /&gt;
* diverse or aging equipment&lt;br /&gt;
* limited availability of trained personnel&lt;br /&gt;
* the need for safety and autonomous operation&lt;br /&gt;
&lt;br /&gt;
AOWIS enables systems that continue to function safely and reliably, even under degraded or adverse conditions.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Facing the Challenges&lt;br /&gt;
 | color = lightblue&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS addresses these operational challenges through the following principles:&lt;br /&gt;
&lt;br /&gt;
* human-in-the-loop control&lt;br /&gt;
* offline-first operation&lt;br /&gt;
* safe fallback behavior&lt;br /&gt;
* modular and extensible logic&lt;br /&gt;
* shared infrastructure models&lt;br /&gt;
* training programs for local operators&lt;br /&gt;
* transparent governance&lt;br /&gt;
&lt;br /&gt;
The goal is to make essential systems &#039;&#039;&#039;robust, maintainable, and locally operable&#039;&#039;&#039;.&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
| title = Software &amp;amp; Downloads&lt;br /&gt;
| color = green&lt;br /&gt;
| body =&lt;br /&gt;
[[File:GUI ky4 3d.png|400px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS includes an open-source software platform for &#039;&#039;&#039;modelling, simulating, visualizing, monitoring, and operating water infrastructure&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The current software includes a network editor and monitoring interface, hydraulic and water-quality simulation using [[External:EPANET:Main Page|EPANET]], geographic maps and terrain visualization, and support for local and standalone operation. Development of the AOWIS Controller is progressing toward a complete open-source SCADA and operational management platform..&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://download.aowis.org Download the AOWIS Controller (development snapshot)]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* [https://github.com/aowis-org Source code on GitHub]&lt;br /&gt;
* [[#Roadmap|Software development roadmap]]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Start Here&lt;br /&gt;
 | color = yellow&lt;br /&gt;
 | body =&lt;br /&gt;
If you are new to AOWIS, begin with:&lt;br /&gt;
&lt;br /&gt;
* [[Concepts:Design_Philosophy|Design Philosophy]]  &lt;br /&gt;
* [[Standard:Definitions|Definitions]]  &lt;br /&gt;
* [[Standard:Normative_Requirements|Normative Requirements]]  &lt;br /&gt;
* [[Modules:Module_Template|Module Template]]  &lt;br /&gt;
* [[AOWIS:Contributor_Guide_External|Contributor Guide - External]]&lt;br /&gt;
* [[AOWIS:Contributor_Guide_Internal|Contributor Guide - Internal]]&lt;br /&gt;
* [[AOWIS:Writing_Style_Guide|Writing Style Guide]]&lt;br /&gt;
* [[AOWIS:AI_Usage_Guide|AI Usage Guide]]&lt;br /&gt;
* [[AOWIS:Research_Form_Guide|Research Form Guide]]&lt;br /&gt;
* [[AOWIS:Naming_Convention_Specification|Naming Convention Specification]]&lt;br /&gt;
* [[AOWIS:Change_Log__Versioning|Change Log &amp;amp; Versioning]]&lt;br /&gt;
* [[AOWIS:Wiki|This Wiki]]&lt;br /&gt;
&lt;br /&gt;
These pages explain the foundations of AOWIS, how the AOWIS Standard is structured, and how to use and contribute to the project and its documentation.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = List of Requirement Pages&lt;br /&gt;
 | color = brown&lt;br /&gt;
 | body = &lt;br /&gt;
This index lists AOWIS pages that define normative requirements (MUST/SHOULD/MAY statements) and conformance rules.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Dev Rules&#039;&#039;&#039; — specs for writing and maintaining AOWIS&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;REQ-AI:&#039;&#039;&#039; [[AOWIS:AI_Usage_Guide|AI Usage Guide]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Technical Standard&#039;&#039;&#039; — system behavior and data models&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;REQ-MEAS, REQ-MEAS-UI:&#039;&#039;&#039; [[Measurement:Units|Unit System Requirements]]&lt;br /&gt;
* &#039;&#039;&#039;REQ-MEAS-UNI:&#039;&#039;&#039; [[Measurement:Canonical_Units|Canonical Units]]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = AOWIS Documentation Structure&lt;br /&gt;
 | color = purple&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS documentation is organized into dedicated namespaces with clearly separated purposes.&lt;br /&gt;
&lt;br /&gt;
The [[Standard:Main_Page|Standard]] namespace contains the normative requirements that define AOWIS compliance. The other namespaces provide the motivation, concepts, engineering knowledge, architectures, operational models, implementation guidance, reference designs, training material, and supporting information needed to understand, implement, and operate AOWIS systems.&lt;br /&gt;
&lt;br /&gt;
* [[Motivation:Main_Page|Motivation]] – Causal justification of design requirements based on real-world failures, constraints, and operational realities.&lt;br /&gt;
* [[Standard:Main_Page|Standard]] – The normative core of AOWIS. Defines requirements and definitions specifying what AOWIS-compliant systems MUST, SHOULD, or MAY do.&lt;br /&gt;
* [[Concepts:Main_Page|Concepts]] – Core ideas, philosophy, rationale, and contextual understanding that explain AOWIS without prescribing a specific implementation.&lt;br /&gt;
* [[Architecture:Main_Page|Architecture]] – High-level system structure, including controllers, layers, communication, data flows, and their interactions.&lt;br /&gt;
* [[Infrastructure:Main_Page|Infrastructure]] – Physical technologies, systems, and components used in AOWIS deployments. Infrastructure pages describe classes of physical systems rather than specific implementation blueprints.&lt;br /&gt;
* [[Measurement:Main_Page|Measurement]] – Definition and handling of sensor data, manual measurements, calibration, uncertainty, and derived physical values.&lt;br /&gt;
* [[Data:Main_Page|Data]] – Data models, schemas, logging structures, synchronization formats, and data lifecycle rules.&lt;br /&gt;
* [[Operations:Main_Page|Operations]] – Runtime behavior, control logic, state transitions, fallback behavior, and decision-making during system operation.&lt;br /&gt;
* [[Modules:Main_Page|Modules]] – Reusable functional extensions that provide domain-specific capabilities within AOWIS.&lt;br /&gt;
* [[Reference:Main_Page|Reference]] – Non-normative concrete implementations, engineering blueprints, example deployments, and validated design patterns showing specific ways AOWIS systems may be built.&lt;br /&gt;
* [[Databases:Main_Page|Databases]] – Federated knowledge bases and structured supporting information used by AOWIS implementations.&lt;br /&gt;
* [[Governance:Main_Page|Governance]] – Certification, compliance, auditing, trust, licensing, versioning, and organizational governance.&lt;br /&gt;
* [[Training:Main_Page|Training]] – Operator education, technical training, field guidance, documentation literacy, and capacity building.&lt;br /&gt;
* [[External:Main_Page|External]] – External projects, standards, technologies, and systems that relate to or influence AOWIS.&lt;br /&gt;
&lt;br /&gt;
* [[Regions:Main_Page|Regions]] – Geographic, environmental, hydrological, climatic, socioeconomic, and infrastructure context for areas in which AOWIS is researched, planned, or deployed.&lt;br /&gt;
&lt;br /&gt;
For a full overview, see the [[AOWIS:Table_of_Contents|Table of Contents]].&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Roadmap&lt;br /&gt;
 | color = grey&lt;br /&gt;
 | body =&lt;br /&gt;
[[File:Boring.jpg|250px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS has progressed beyond its initial conceptual phase. A substantial software foundation for modelling, simulating, visualizing, and eventually operating water infrastructure is under active development.&lt;br /&gt;
&lt;br /&gt;
The current software stack already includes:&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Shared infrastructure model&#039;&#039;&#039;&lt;br /&gt;
: A common, solver-independent representation of water infrastructure used throughout the AOWIS software stack.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-MODEL GitHub AOWIS-SERVER-MODEL]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Hydraulic and water-quality simulation&#039;&#039;&#039;&lt;br /&gt;
: EPANET integration for hydraulic and water-quality simulation, network import/export, controls, rules, diagnostics, and simulation results. Integration of &#039;&#039;&#039;EPANET-MSX&#039;&#039;&#039; is also being developed.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-EPANET GitHub AOWIS-SERVER-EPANET]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Network editor and monitoring interface&#039;&#039;&#039;&lt;br /&gt;
: A graphical application for creating, inspecting, simulating, and visualizing water networks, including geographic maps and terrain-aware 3D visualization.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-GUI GitHub AOWIS-SERVER-GUI]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Geographic and terrain infrastructure&#039;&#039;&#039;&lt;br /&gt;
: Mapping, elevation data, basemaps, terrain visualization, geographic placement, and local caching.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-MAP GitHub AOWIS-SERVER-MAP]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Local and standalone operation&#039;&#039;&#039;&lt;br /&gt;
: Support for deployments that do not depend on continuous Internet or cloud connectivity.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-Standalone GitHub AOWIS-SERVER-Standalone]&lt;br /&gt;
&lt;br /&gt;
The software remains under active development and should not yet be considered a complete production SCADA system.&lt;br /&gt;
&lt;br /&gt;
The next major stage is to connect the existing modelling and simulation environment to &#039;&#039;&#039;real infrastructure in continuous operation&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
AOWIS is intended to develop into a complete open-source &#039;&#039;&#039;SCADA, infrastructure modelling, simulation, and operational management platform&#039;&#039;&#039; in which planning, live monitoring, control, historical data, maintenance, and simulation operate on the same shared infrastructure model.&lt;br /&gt;
&lt;br /&gt;
This includes telemetry, sensors and actuators, alarms and historian functions, local and remote control, automation with safe fallback behaviour, and model-assisted operation using measured and simulated system behaviour.&lt;br /&gt;
&lt;br /&gt;
EPANET currently provides the primary hydraulic and water-quality simulation engine, but AOWIS is not designed solely as an EPANET frontend. EPANET is one solver integrated into a broader, solver-independent architecture.&lt;br /&gt;
&lt;br /&gt;
The long-term objective is to connect the complete infrastructure lifecycle:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;survey and planning → engineering and simulation → construction → commissioning → monitoring → control → maintenance → analysis → expansion&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[[AOWIS:Roadmap|Read the full roadmap →]]&#039;&#039;&#039;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
| title = Community &amp;amp; Participation&lt;br /&gt;
| color = blue&lt;br /&gt;
| body =&lt;br /&gt;
&lt;br /&gt;
AOWIS is an open project, and participation is welcome from anyone interested in its goals — including engineers, developers, NGOs, operators, researchers, technicians, students, and people with practical experience in water and agricultural infrastructure.&lt;br /&gt;
&lt;br /&gt;
For &#039;&#039;&#039;discussion, planning, questions, documentation, infrastructure, field projects, standards, research, and other forms of participation&#039;&#039;&#039;, AOWIS uses &#039;&#039;&#039;Matrix&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The AOWIS Matrix server has several &#039;&#039;&#039;public spaces and rooms&#039;&#039;&#039; for different topics. Join those relevant to your interests. For general questions or help finding the right place, start here:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://matrix.to/#/#support:aowis.org AOWIS Support — #support:aowis.org]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
You do &#039;&#039;&#039;not&#039;&#039;&#039; need an AOWIS account to participate. Any Matrix account can join public AOWIS spaces and rooms.&lt;br /&gt;
&lt;br /&gt;
If you are new to Matrix:&lt;br /&gt;
&lt;br /&gt;
* [https://matrix.org/try-matrix/ Learn about Matrix and create an account]&lt;br /&gt;
* [https://element.io/ Element] — Matrix client for web, desktop, and mobile&lt;br /&gt;
* [https://fluffychat.im/ FluffyChat] — simple Matrix client for several platforms&lt;br /&gt;
&lt;br /&gt;
The same Matrix account can be used with different clients.&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;AOWIS Matrix Accounts&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Participants may also request an account on the AOWIS Matrix homeserver, giving them an ID such as &#039;&#039;&#039;@name:aowis.org&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
To reduce automated registrations and abuse, accounts are created on request. Please send a short introduction telling us who you are, what interests you about AOWIS, and where you would like to participate: [[File:Mtx.png|120px|frameless|alt=Email address for requesting an AOWIS Matrix account]]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Software Development&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Software development remains on &#039;&#039;&#039;GitHub&#039;&#039;&#039;. Bug reports, pull requests, source-code contributions, and repository-specific development discussions should use the appropriate repository.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://github.com/aowis-org AOWIS on GitHub]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Matrix is for the broader AOWIS community and participation that does not naturally belong in a GitHub repository.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Governance &amp;amp; Legitimacy&lt;br /&gt;
 | color = turquoise&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS includes a transparent governance model to ensure:&lt;br /&gt;
&lt;br /&gt;
* open participation  &lt;br /&gt;
* clear certification processes  &lt;br /&gt;
* stable versioning  &lt;br /&gt;
* long‑term protection of the standard  &lt;br /&gt;
&lt;br /&gt;
See: [[Governance:Main_Page|Governance]].&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Navigation&lt;br /&gt;
 | color = grey&lt;br /&gt;
 | body =&lt;br /&gt;
* [[AOWIS:Table_of_Contents|Table of Contents]]  &lt;br /&gt;
* [[Reference:Glossary|Glossary]]  &lt;br /&gt;
* [[Reference:FAQ|FAQ]]  &lt;br /&gt;
* [[Reference:Change_Log|Change Log]]  &lt;br /&gt;
&lt;br /&gt;
* [https://github.com/aowis-org GitHub]&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Partners&lt;br /&gt;
 | color = indigo&lt;br /&gt;
 | body = &lt;br /&gt;
[[File:Afriticgroup.webp|250px|frameless|center|link=https://afriticgroup.com/]]&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Samuel</name></author>
	</entry>
	<entry>
		<id>https://aowis.org/index.php?title=Main_Page&amp;diff=761</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://aowis.org/index.php?title=Main_Page&amp;diff=761"/>
		<updated>2026-09-23T15:52:02Z</updated>

		<summary type="html">&lt;p&gt;Samuel: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
&lt;br /&gt;
{{MainPageBanner}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Motivation&lt;br /&gt;
 | color = teal&lt;br /&gt;
 | body = &lt;br /&gt;
&lt;br /&gt;
[[File:Countryside.jpg|class=fullwidth|center]]&lt;br /&gt;
&lt;br /&gt;
In many rural and underserved regions, including parts of Africa, wells and pumps may exist while developing and operating a reliable distribution network remains difficult. Local initiatives can lack engineering capacity, trained personnel, suitable technology, and affordable tools for operating such infrastructure sustainably.&lt;br /&gt;
&lt;br /&gt;
This practical problem is an important motivation for AOWIS. AOWIS aims to make the engineering knowledge, technical foundations, software, and operational methods needed to develop and operate water infrastructure openly available and practically usable, while supporting local training and cooperation with experienced organizations and operators.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Why AOWIS is Needed&lt;br /&gt;
 | color = turquoise&lt;br /&gt;
 | body = &lt;br /&gt;
&lt;br /&gt;
[[File:Cooperation.jpg|400px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
Water and irrigation infrastructure must often be planned, built, expanded, and operated over many decades. In some places, existing infrastructure has become fragmented across different vendors, technologies, tools, and engineering approaches. In others, communities and organizations are building coherent water infrastructure for the first time and may have limited access to engineering capacity, technical guidance, suitable software, or established operational practices.&lt;br /&gt;
&lt;br /&gt;
AOWIS provides a shared open foundation for both situations. It brings together technical standards, engineering knowledge, software, reference implementations, operational guidance, and training to support the development of water infrastructure from initial planning and design through construction, operation, maintenance, and future expansion.&lt;br /&gt;
&lt;br /&gt;
The aim is to make infrastructure understandable, interoperable, maintainable, and extensible throughout its lifecycle, while reducing dependence on individual vendors, products, suppliers, or scarce specialist expertise.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Operation Conditions&lt;br /&gt;
 | color = lightblue&lt;br /&gt;
 | body =&lt;br /&gt;
[[File:Village.jpg|250px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS is designed to operate under the real-world conditions faced by local initiatives. These include, among others:&lt;br /&gt;
&lt;br /&gt;
* unreliable power supply&lt;br /&gt;
* intermittent connectivity&lt;br /&gt;
* diverse or aging equipment&lt;br /&gt;
* limited availability of trained personnel&lt;br /&gt;
* the need for safety and autonomous operation&lt;br /&gt;
&lt;br /&gt;
AOWIS enables systems that continue to function safely and reliably, even under degraded or adverse conditions.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Facing the Challenges&lt;br /&gt;
 | color = lightblue&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS addresses these operational challenges through the following principles:&lt;br /&gt;
&lt;br /&gt;
* human-in-the-loop control&lt;br /&gt;
* offline-first operation&lt;br /&gt;
* safe fallback behavior&lt;br /&gt;
* modular and extensible logic&lt;br /&gt;
* shared infrastructure models&lt;br /&gt;
* training programs for local operators&lt;br /&gt;
* transparent governance&lt;br /&gt;
&lt;br /&gt;
The goal is to make essential systems &#039;&#039;&#039;robust, maintainable, and locally operable&#039;&#039;&#039;.&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
| title = Software &amp;amp; Downloads&lt;br /&gt;
| color = green&lt;br /&gt;
| body =&lt;br /&gt;
[[File:GUI ky4 3d.png|400px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS includes an open-source software platform for &#039;&#039;&#039;modelling, simulating, visualizing, monitoring, and operating water infrastructure&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The current software includes a network editor and monitoring interface, hydraulic and water-quality simulation using [[External:EPANET:Main Page|EPANET]], geographic maps and terrain visualization, and support for local and standalone operation. Development is progressing toward a complete AOWIS-compatible SCADA platform.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://download.aowis.org Download the AOWIS Controller (development snapshot)]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* [https://github.com/aowis-org Source code on GitHub]&lt;br /&gt;
* [[#Roadmap|Software development roadmap]]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Start Here&lt;br /&gt;
 | color = yellow&lt;br /&gt;
 | body =&lt;br /&gt;
If you are new to AOWIS, begin with:&lt;br /&gt;
&lt;br /&gt;
* [[Concepts:Design_Philosophy|Design Philosophy]]  &lt;br /&gt;
* [[Standard:Definitions|Definitions]]  &lt;br /&gt;
* [[Standard:Normative_Requirements|Normative Requirements]]  &lt;br /&gt;
* [[Modules:Module_Template|Module Template]]  &lt;br /&gt;
* [[AOWIS:Contributor_Guide_External|Contributor Guide - External]]&lt;br /&gt;
* [[AOWIS:Contributor_Guide_Internal|Contributor Guide - Internal]]&lt;br /&gt;
* [[AOWIS:Writing_Style_Guide|Writing Style Guide]]&lt;br /&gt;
* [[AOWIS:AI_Usage_Guide|AI Usage Guide]]&lt;br /&gt;
* [[AOWIS:Research_Form_Guide|Research Form Guide]]&lt;br /&gt;
* [[AOWIS:Naming_Convention_Specification|Naming Convention Specification]]&lt;br /&gt;
* [[AOWIS:Change_Log__Versioning|Change Log &amp;amp; Versioning]]&lt;br /&gt;
* [[AOWIS:Wiki|This Wiki]]&lt;br /&gt;
&lt;br /&gt;
These pages explain the foundations of AOWIS, how the AOWIS Standard is structured, and how to use and contribute to the project and its documentation.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = List of Requirement Pages&lt;br /&gt;
 | color = brown&lt;br /&gt;
 | body = &lt;br /&gt;
This index lists AOWIS pages that define normative requirements (MUST/SHOULD/MAY statements) and conformance rules.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Dev Rules&#039;&#039;&#039; — specs for writing and maintaining AOWIS&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;REQ-AI:&#039;&#039;&#039; [[AOWIS:AI_Usage_Guide|AI Usage Guide]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Technical Standard&#039;&#039;&#039; — system behavior and data models&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;REQ-MEAS, REQ-MEAS-UI:&#039;&#039;&#039; [[Measurement:Units|Unit System Requirements]]&lt;br /&gt;
* &#039;&#039;&#039;REQ-MEAS-UNI:&#039;&#039;&#039; [[Measurement:Canonical_Units|Canonical Units]]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = AOWIS Documentation Structure&lt;br /&gt;
 | color = purple&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS documentation is organized into dedicated namespaces with clearly separated purposes.&lt;br /&gt;
&lt;br /&gt;
The [[Standard:Main_Page|Standard]] namespace contains the normative requirements that define AOWIS compliance. The other namespaces provide the motivation, concepts, engineering knowledge, architectures, operational models, implementation guidance, reference designs, training material, and supporting information needed to understand, implement, and operate AOWIS systems.&lt;br /&gt;
&lt;br /&gt;
* [[Motivation:Main_Page|Motivation]] – Causal justification of design requirements based on real-world failures, constraints, and operational realities.&lt;br /&gt;
* [[Standard:Main_Page|Standard]] – The normative core of AOWIS. Defines requirements and definitions specifying what AOWIS-compliant systems MUST, SHOULD, or MAY do.&lt;br /&gt;
* [[Concepts:Main_Page|Concepts]] – Core ideas, philosophy, rationale, and contextual understanding that explain AOWIS without prescribing a specific implementation.&lt;br /&gt;
* [[Architecture:Main_Page|Architecture]] – High-level system structure, including controllers, layers, communication, data flows, and their interactions.&lt;br /&gt;
* [[Infrastructure:Main_Page|Infrastructure]] – Physical technologies, systems, and components used in AOWIS deployments. Infrastructure pages describe classes of physical systems rather than specific implementation blueprints.&lt;br /&gt;
* [[Measurement:Main_Page|Measurement]] – Definition and handling of sensor data, manual measurements, calibration, uncertainty, and derived physical values.&lt;br /&gt;
* [[Data:Main_Page|Data]] – Data models, schemas, logging structures, synchronization formats, and data lifecycle rules.&lt;br /&gt;
* [[Operations:Main_Page|Operations]] – Runtime behavior, control logic, state transitions, fallback behavior, and decision-making during system operation.&lt;br /&gt;
* [[Modules:Main_Page|Modules]] – Reusable functional extensions that provide domain-specific capabilities within AOWIS.&lt;br /&gt;
* [[Reference:Main_Page|Reference]] – Non-normative concrete implementations, engineering blueprints, example deployments, and validated design patterns showing specific ways AOWIS systems may be built.&lt;br /&gt;
* [[Databases:Main_Page|Databases]] – Federated knowledge bases and structured supporting information used by AOWIS implementations.&lt;br /&gt;
* [[Governance:Main_Page|Governance]] – Certification, compliance, auditing, trust, licensing, versioning, and organizational governance.&lt;br /&gt;
* [[Training:Main_Page|Training]] – Operator education, technical training, field guidance, documentation literacy, and capacity building.&lt;br /&gt;
* [[External:Main_Page|External]] – External projects, standards, technologies, and systems that relate to or influence AOWIS.&lt;br /&gt;
&lt;br /&gt;
* [[Regions:Main_Page|Regions]] – Geographic, environmental, hydrological, climatic, socioeconomic, and infrastructure context for areas in which AOWIS is researched, planned, or deployed.&lt;br /&gt;
&lt;br /&gt;
For a full overview, see the [[AOWIS:Table_of_Contents|Table of Contents]].&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Roadmap&lt;br /&gt;
 | color = grey&lt;br /&gt;
 | body =&lt;br /&gt;
[[File:Boring.jpg|250px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS has progressed beyond its initial conceptual phase. A substantial software foundation for modelling, simulating, visualizing, and eventually operating water infrastructure is under active development.&lt;br /&gt;
&lt;br /&gt;
The current software stack already includes:&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Shared infrastructure model&#039;&#039;&#039;&lt;br /&gt;
: A common, solver-independent representation of water infrastructure used throughout the AOWIS software stack.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-MODEL GitHub AOWIS-SERVER-MODEL]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Hydraulic and water-quality simulation&#039;&#039;&#039;&lt;br /&gt;
: EPANET integration for hydraulic and water-quality simulation, network import/export, controls, rules, diagnostics, and simulation results. Integration of &#039;&#039;&#039;EPANET-MSX&#039;&#039;&#039; is also being developed.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-EPANET GitHub AOWIS-SERVER-EPANET]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Network editor and monitoring interface&#039;&#039;&#039;&lt;br /&gt;
: A graphical application for creating, inspecting, simulating, and visualizing water networks, including geographic maps and terrain-aware 3D visualization.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-GUI GitHub AOWIS-SERVER-GUI]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Geographic and terrain infrastructure&#039;&#039;&#039;&lt;br /&gt;
: Mapping, elevation data, basemaps, terrain visualization, geographic placement, and local caching.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-MAP GitHub AOWIS-SERVER-MAP]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Local and standalone operation&#039;&#039;&#039;&lt;br /&gt;
: Support for deployments that do not depend on continuous Internet or cloud connectivity.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-Standalone GitHub AOWIS-SERVER-Standalone]&lt;br /&gt;
&lt;br /&gt;
The software remains under active development and should not yet be considered a complete production SCADA system.&lt;br /&gt;
&lt;br /&gt;
The next major stage is to connect the existing modelling and simulation environment to &#039;&#039;&#039;real infrastructure in continuous operation&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
AOWIS is intended to develop into a complete open-source &#039;&#039;&#039;SCADA, infrastructure modelling, simulation, and operational management platform&#039;&#039;&#039; in which planning, live monitoring, control, historical data, maintenance, and simulation operate on the same shared infrastructure model.&lt;br /&gt;
&lt;br /&gt;
This includes telemetry, sensors and actuators, alarms and historian functions, local and remote control, automation with safe fallback behaviour, and model-assisted operation using measured and simulated system behaviour.&lt;br /&gt;
&lt;br /&gt;
EPANET currently provides the primary hydraulic and water-quality simulation engine, but AOWIS is not designed solely as an EPANET frontend. EPANET is one solver integrated into a broader, solver-independent architecture.&lt;br /&gt;
&lt;br /&gt;
The long-term objective is to connect the complete infrastructure lifecycle:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;survey and planning → engineering and simulation → construction → commissioning → monitoring → control → maintenance → analysis → expansion&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[[AOWIS:Roadmap|Read the full roadmap →]]&#039;&#039;&#039;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
| title = Community &amp;amp; Participation&lt;br /&gt;
| color = blue&lt;br /&gt;
| body =&lt;br /&gt;
&lt;br /&gt;
AOWIS is an open project, and participation is welcome from anyone interested in its goals — including engineers, developers, NGOs, operators, researchers, technicians, students, and people with practical experience in water and agricultural infrastructure.&lt;br /&gt;
&lt;br /&gt;
For &#039;&#039;&#039;discussion, planning, questions, documentation, infrastructure, field projects, standards, research, and other forms of participation&#039;&#039;&#039;, AOWIS uses &#039;&#039;&#039;Matrix&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The AOWIS Matrix server has several &#039;&#039;&#039;public spaces and rooms&#039;&#039;&#039; for different topics. Join those relevant to your interests. For general questions or help finding the right place, start here:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://matrix.to/#/#support:aowis.org AOWIS Support — #support:aowis.org]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
You do &#039;&#039;&#039;not&#039;&#039;&#039; need an AOWIS account to participate. Any Matrix account can join public AOWIS spaces and rooms.&lt;br /&gt;
&lt;br /&gt;
If you are new to Matrix:&lt;br /&gt;
&lt;br /&gt;
* [https://matrix.org/try-matrix/ Learn about Matrix and create an account]&lt;br /&gt;
* [https://element.io/ Element] — Matrix client for web, desktop, and mobile&lt;br /&gt;
* [https://fluffychat.im/ FluffyChat] — simple Matrix client for several platforms&lt;br /&gt;
&lt;br /&gt;
The same Matrix account can be used with different clients.&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;AOWIS Matrix Accounts&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Participants may also request an account on the AOWIS Matrix homeserver, giving them an ID such as &#039;&#039;&#039;@name:aowis.org&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
To reduce automated registrations and abuse, accounts are created on request. Please send a short introduction telling us who you are, what interests you about AOWIS, and where you would like to participate: [[File:Mtx.png|120px|frameless|alt=Email address for requesting an AOWIS Matrix account]]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Software Development&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Software development remains on &#039;&#039;&#039;GitHub&#039;&#039;&#039;. Bug reports, pull requests, source-code contributions, and repository-specific development discussions should use the appropriate repository.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://github.com/aowis-org AOWIS on GitHub]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Matrix is for the broader AOWIS community and participation that does not naturally belong in a GitHub repository.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Governance &amp;amp; Legitimacy&lt;br /&gt;
 | color = turquoise&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS includes a transparent governance model to ensure:&lt;br /&gt;
&lt;br /&gt;
* open participation  &lt;br /&gt;
* clear certification processes  &lt;br /&gt;
* stable versioning  &lt;br /&gt;
* long‑term protection of the standard  &lt;br /&gt;
&lt;br /&gt;
See: [[Governance:Main_Page|Governance]].&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Navigation&lt;br /&gt;
 | color = grey&lt;br /&gt;
 | body =&lt;br /&gt;
* [[AOWIS:Table_of_Contents|Table of Contents]]  &lt;br /&gt;
* [[Reference:Glossary|Glossary]]  &lt;br /&gt;
* [[Reference:FAQ|FAQ]]  &lt;br /&gt;
* [[Reference:Change_Log|Change Log]]  &lt;br /&gt;
&lt;br /&gt;
* [https://github.com/aowis-org GitHub]&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Partners&lt;br /&gt;
 | color = indigo&lt;br /&gt;
 | body = &lt;br /&gt;
[[File:Afriticgroup.webp|250px|frameless|center|link=https://afriticgroup.com/]]&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Samuel</name></author>
	</entry>
	<entry>
		<id>https://aowis.org/index.php?title=Main_Page&amp;diff=760</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://aowis.org/index.php?title=Main_Page&amp;diff=760"/>
		<updated>2026-09-23T15:43:53Z</updated>

		<summary type="html">&lt;p&gt;Samuel: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
&lt;br /&gt;
{{MainPageBanner}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Motivation&lt;br /&gt;
 | color = teal&lt;br /&gt;
 | body = &lt;br /&gt;
&lt;br /&gt;
[[File:Countryside.jpg|class=fullwidth|center]]&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
This is where AOWIS aims to contribute: by providing an open system for planning, designing, developing, deploying, operating, maintaining, and managing water and agricultural infrastructure in such environments. AOWIS combines a common technical standard with open-source software, engineering guidance, shared knowledge, and operational practices. It supports the full infrastructure lifecycle—from early assessment and conceptual planning, through design and implementation, to monitoring, control, maintenance, adaptation, and long-term operation.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Why AOWIS is Needed&lt;br /&gt;
 | color = turquoise&lt;br /&gt;
 | body = &lt;br /&gt;
&lt;br /&gt;
[[File:Cooperation.jpg|400px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
Water and irrigation infrastructure must often be planned, built, expanded, and operated over many decades. In some places, existing infrastructure has become fragmented across different vendors, technologies, tools, and engineering approaches. In others, communities and organizations are building structured water infrastructure for the first time and may have limited access to engineering capacity, technical guidance, suitable software, or established operational practices.&lt;br /&gt;
&lt;br /&gt;
AOWIS provides a shared open foundation for both situations. It brings together technical standards, engineering knowledge, software, reference implementations, operational guidance, and training to support the development of water infrastructure from initial planning and design through construction, operation, maintenance, and future expansion.&lt;br /&gt;
&lt;br /&gt;
The aim is to make infrastructure understandable, interoperable, maintainable, and extensible throughout its lifecycle, while reducing dependence on individual vendors, products, suppliers, or scarce specialist expertise.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Operation Conditions&lt;br /&gt;
 | color = lightblue&lt;br /&gt;
 | body =&lt;br /&gt;
[[File:Village.jpg|250px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS is designed to operate under the real-world conditions faced by local initiatives. These include, among others:&lt;br /&gt;
&lt;br /&gt;
* unreliable power supply&lt;br /&gt;
* intermittent connectivity&lt;br /&gt;
* diverse or aging equipment&lt;br /&gt;
* limited availability of trained personnel&lt;br /&gt;
* the need for safety and autonomous operation&lt;br /&gt;
&lt;br /&gt;
AOWIS enables systems that continue to function safely and reliably, even under degraded or adverse conditions.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Facing the Challenges&lt;br /&gt;
 | color = lightblue&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS addresses these operational challenges through the following principles:&lt;br /&gt;
&lt;br /&gt;
* human-in-the-loop control&lt;br /&gt;
* offline-first operation&lt;br /&gt;
* safe fallback behavior&lt;br /&gt;
* modular and extensible logic&lt;br /&gt;
* shared infrastructure models&lt;br /&gt;
* training programs for local operators&lt;br /&gt;
* transparent governance&lt;br /&gt;
&lt;br /&gt;
The goal is to make essential systems &#039;&#039;&#039;robust, maintainable, and locally operable&#039;&#039;&#039;.&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
| title = Software &amp;amp; Downloads&lt;br /&gt;
| color = green&lt;br /&gt;
| body =&lt;br /&gt;
[[File:GUI ky4 3d.png|400px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS includes an open-source software platform for &#039;&#039;&#039;modelling, simulating, visualizing, monitoring, and operating water infrastructure&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The current software includes a network editor and monitoring interface, hydraulic and water-quality simulation using [[External:EPANET:Main Page|EPANET]], geographic maps and terrain visualization, and support for local and standalone operation. Development is progressing toward a complete AOWIS-compatible SCADA platform.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://download.aowis.org Download the AOWIS Controller (development snapshot)]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* [https://github.com/aowis-org Source code on GitHub]&lt;br /&gt;
* [[#Roadmap|Software development roadmap]]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Start Here&lt;br /&gt;
 | color = yellow&lt;br /&gt;
 | body =&lt;br /&gt;
If you are new to AOWIS, begin with:&lt;br /&gt;
&lt;br /&gt;
* [[Concepts:Design_Philosophy|Design Philosophy]]  &lt;br /&gt;
* [[Standard:Definitions|Definitions]]  &lt;br /&gt;
* [[Standard:Normative_Requirements|Normative Requirements]]  &lt;br /&gt;
* [[Modules:Module_Template|Module Template]]  &lt;br /&gt;
* [[AOWIS:Contributor_Guide_External|Contributor Guide - External]]&lt;br /&gt;
* [[AOWIS:Contributor_Guide_Internal|Contributor Guide - Internal]]&lt;br /&gt;
* [[AOWIS:Writing_Style_Guide|Writing Style Guide]]&lt;br /&gt;
* [[AOWIS:AI_Usage_Guide|AI Usage Guide]]&lt;br /&gt;
* [[AOWIS:Research_Form_Guide|Research Form Guide]]&lt;br /&gt;
* [[AOWIS:Naming_Convention_Specification|Naming Convention Specification]]&lt;br /&gt;
* [[AOWIS:Change_Log__Versioning|Change Log &amp;amp; Versioning]]&lt;br /&gt;
* [[AOWIS:Wiki|This Wiki]]&lt;br /&gt;
&lt;br /&gt;
These pages explain the foundations of AOWIS, how the AOWIS Standard is structured, and how to use and contribute to the project and its documentation.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = List of Requirement Pages&lt;br /&gt;
 | color = brown&lt;br /&gt;
 | body = &lt;br /&gt;
This index lists AOWIS pages that define normative requirements (MUST/SHOULD/MAY statements) and conformance rules.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Dev Rules&#039;&#039;&#039; — specs for writing and maintaining AOWIS&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;REQ-AI:&#039;&#039;&#039; [[AOWIS:AI_Usage_Guide|AI Usage Guide]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Technical Standard&#039;&#039;&#039; — system behavior and data models&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;REQ-MEAS, REQ-MEAS-UI:&#039;&#039;&#039; [[Measurement:Units|Unit System Requirements]]&lt;br /&gt;
* &#039;&#039;&#039;REQ-MEAS-UNI:&#039;&#039;&#039; [[Measurement:Canonical_Units|Canonical Units]]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = AOWIS Documentation Structure&lt;br /&gt;
 | color = purple&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS documentation is organized into dedicated namespaces with clearly separated purposes.&lt;br /&gt;
&lt;br /&gt;
The [[Standard:Main_Page|Standard]] namespace contains the normative requirements that define AOWIS compliance. The other namespaces provide the motivation, concepts, engineering knowledge, architectures, operational models, implementation guidance, reference designs, training material, and supporting information needed to understand, implement, and operate AOWIS systems.&lt;br /&gt;
&lt;br /&gt;
* [[Motivation:Main_Page|Motivation]] – Causal justification of design requirements based on real-world failures, constraints, and operational realities.&lt;br /&gt;
* [[Standard:Main_Page|Standard]] – The normative core of AOWIS. Defines requirements and definitions specifying what AOWIS-compliant systems MUST, SHOULD, or MAY do.&lt;br /&gt;
* [[Concepts:Main_Page|Concepts]] – Core ideas, philosophy, rationale, and contextual understanding that explain AOWIS without prescribing a specific implementation.&lt;br /&gt;
* [[Architecture:Main_Page|Architecture]] – High-level system structure, including controllers, layers, communication, data flows, and their interactions.&lt;br /&gt;
* [[Infrastructure:Main_Page|Infrastructure]] – Physical technologies, systems, and components used in AOWIS deployments. Infrastructure pages describe classes of physical systems rather than specific implementation blueprints.&lt;br /&gt;
* [[Measurement:Main_Page|Measurement]] – Definition and handling of sensor data, manual measurements, calibration, uncertainty, and derived physical values.&lt;br /&gt;
* [[Data:Main_Page|Data]] – Data models, schemas, logging structures, synchronization formats, and data lifecycle rules.&lt;br /&gt;
* [[Operations:Main_Page|Operations]] – Runtime behavior, control logic, state transitions, fallback behavior, and decision-making during system operation.&lt;br /&gt;
* [[Modules:Main_Page|Modules]] – Reusable functional extensions that provide domain-specific capabilities within AOWIS.&lt;br /&gt;
* [[Reference:Main_Page|Reference]] – Non-normative concrete implementations, engineering blueprints, example deployments, and validated design patterns showing specific ways AOWIS systems may be built.&lt;br /&gt;
* [[Databases:Main_Page|Databases]] – Federated knowledge bases and structured supporting information used by AOWIS implementations.&lt;br /&gt;
* [[Governance:Main_Page|Governance]] – Certification, compliance, auditing, trust, licensing, versioning, and organizational governance.&lt;br /&gt;
* [[Training:Main_Page|Training]] – Operator education, technical training, field guidance, documentation literacy, and capacity building.&lt;br /&gt;
* [[External:Main_Page|External]] – External projects, standards, technologies, and systems that relate to or influence AOWIS.&lt;br /&gt;
&lt;br /&gt;
* [[Regions:Main_Page|Regions]] – Geographic, environmental, hydrological, climatic, socioeconomic, and infrastructure context for areas in which AOWIS is researched, planned, or deployed.&lt;br /&gt;
&lt;br /&gt;
For a full overview, see the [[AOWIS:Table_of_Contents|Table of Contents]].&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Roadmap&lt;br /&gt;
 | color = grey&lt;br /&gt;
 | body =&lt;br /&gt;
[[File:Boring.jpg|250px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS has progressed beyond its initial conceptual phase. A substantial software foundation for modelling, simulating, visualizing, and eventually operating water infrastructure is under active development.&lt;br /&gt;
&lt;br /&gt;
The current software stack already includes:&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Shared infrastructure model&#039;&#039;&#039;&lt;br /&gt;
: A common, solver-independent representation of water infrastructure used throughout the AOWIS software stack.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-MODEL GitHub AOWIS-SERVER-MODEL]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Hydraulic and water-quality simulation&#039;&#039;&#039;&lt;br /&gt;
: EPANET integration for hydraulic and water-quality simulation, network import/export, controls, rules, diagnostics, and simulation results. Integration of &#039;&#039;&#039;EPANET-MSX&#039;&#039;&#039; is also being developed.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-EPANET GitHub AOWIS-SERVER-EPANET]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Network editor and monitoring interface&#039;&#039;&#039;&lt;br /&gt;
: A graphical application for creating, inspecting, simulating, and visualizing water networks, including geographic maps and terrain-aware 3D visualization.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-GUI GitHub AOWIS-SERVER-GUI]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Geographic and terrain infrastructure&#039;&#039;&#039;&lt;br /&gt;
: Mapping, elevation data, basemaps, terrain visualization, geographic placement, and local caching.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-MAP GitHub AOWIS-SERVER-MAP]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Local and standalone operation&#039;&#039;&#039;&lt;br /&gt;
: Support for deployments that do not depend on continuous Internet or cloud connectivity.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-Standalone GitHub AOWIS-SERVER-Standalone]&lt;br /&gt;
&lt;br /&gt;
The software remains under active development and should not yet be considered a complete production SCADA system.&lt;br /&gt;
&lt;br /&gt;
The next major stage is to connect the existing modelling and simulation environment to &#039;&#039;&#039;real infrastructure in continuous operation&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
AOWIS is intended to develop into a complete open-source &#039;&#039;&#039;SCADA, infrastructure modelling, simulation, and operational management platform&#039;&#039;&#039; in which planning, live monitoring, control, historical data, maintenance, and simulation operate on the same shared infrastructure model.&lt;br /&gt;
&lt;br /&gt;
This includes telemetry, sensors and actuators, alarms and historian functions, local and remote control, automation with safe fallback behaviour, and model-assisted operation using measured and simulated system behaviour.&lt;br /&gt;
&lt;br /&gt;
EPANET currently provides the primary hydraulic and water-quality simulation engine, but AOWIS is not designed solely as an EPANET frontend. EPANET is one solver integrated into a broader, solver-independent architecture.&lt;br /&gt;
&lt;br /&gt;
The long-term objective is to connect the complete infrastructure lifecycle:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;survey and planning → engineering and simulation → construction → commissioning → monitoring → control → maintenance → analysis → expansion&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[[AOWIS:Roadmap|Read the full roadmap →]]&#039;&#039;&#039;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
| title = Community &amp;amp; Participation&lt;br /&gt;
| color = blue&lt;br /&gt;
| body =&lt;br /&gt;
&lt;br /&gt;
AOWIS is an open project, and participation is welcome from anyone interested in its goals — including engineers, developers, NGOs, operators, researchers, technicians, students, and people with practical experience in water and agricultural infrastructure.&lt;br /&gt;
&lt;br /&gt;
For &#039;&#039;&#039;discussion, planning, questions, documentation, infrastructure, field projects, standards, research, and other forms of participation&#039;&#039;&#039;, AOWIS uses &#039;&#039;&#039;Matrix&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The AOWIS Matrix server has several &#039;&#039;&#039;public spaces and rooms&#039;&#039;&#039; for different topics. Join those relevant to your interests. For general questions or help finding the right place, start here:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://matrix.to/#/#support:aowis.org AOWIS Support — #support:aowis.org]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
You do &#039;&#039;&#039;not&#039;&#039;&#039; need an AOWIS account to participate. Any Matrix account can join public AOWIS spaces and rooms.&lt;br /&gt;
&lt;br /&gt;
If you are new to Matrix:&lt;br /&gt;
&lt;br /&gt;
* [https://matrix.org/try-matrix/ Learn about Matrix and create an account]&lt;br /&gt;
* [https://element.io/ Element] — Matrix client for web, desktop, and mobile&lt;br /&gt;
* [https://fluffychat.im/ FluffyChat] — simple Matrix client for several platforms&lt;br /&gt;
&lt;br /&gt;
The same Matrix account can be used with different clients.&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;AOWIS Matrix Accounts&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Participants may also request an account on the AOWIS Matrix homeserver, giving them an ID such as &#039;&#039;&#039;@name:aowis.org&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
To reduce automated registrations and abuse, accounts are created on request. Please send a short introduction telling us who you are, what interests you about AOWIS, and where you would like to participate: [[File:Mtx.png|120px|frameless|alt=Email address for requesting an AOWIS Matrix account]]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Software Development&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Software development remains on &#039;&#039;&#039;GitHub&#039;&#039;&#039;. Bug reports, pull requests, source-code contributions, and repository-specific development discussions should use the appropriate repository.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://github.com/aowis-org AOWIS on GitHub]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Matrix is for the broader AOWIS community and participation that does not naturally belong in a GitHub repository.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Governance &amp;amp; Legitimacy&lt;br /&gt;
 | color = turquoise&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS includes a transparent governance model to ensure:&lt;br /&gt;
&lt;br /&gt;
* open participation  &lt;br /&gt;
* clear certification processes  &lt;br /&gt;
* stable versioning  &lt;br /&gt;
* long‑term protection of the standard  &lt;br /&gt;
&lt;br /&gt;
See: [[Governance:Main_Page|Governance]].&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Navigation&lt;br /&gt;
 | color = grey&lt;br /&gt;
 | body =&lt;br /&gt;
* [[AOWIS:Table_of_Contents|Table of Contents]]  &lt;br /&gt;
* [[Reference:Glossary|Glossary]]  &lt;br /&gt;
* [[Reference:FAQ|FAQ]]  &lt;br /&gt;
* [[Reference:Change_Log|Change Log]]  &lt;br /&gt;
&lt;br /&gt;
* [https://github.com/aowis-org GitHub]&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Partners&lt;br /&gt;
 | color = indigo&lt;br /&gt;
 | body = &lt;br /&gt;
[[File:Afriticgroup.webp|250px|frameless|center|link=https://afriticgroup.com/]]&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Samuel</name></author>
	</entry>
	<entry>
		<id>https://aowis.org/index.php?title=Main_Page&amp;diff=759</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://aowis.org/index.php?title=Main_Page&amp;diff=759"/>
		<updated>2026-09-23T15:37:00Z</updated>

		<summary type="html">&lt;p&gt;Samuel: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
&lt;br /&gt;
{{MainPageBanner}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Motivation&lt;br /&gt;
 | color = teal&lt;br /&gt;
 | body = &lt;br /&gt;
&lt;br /&gt;
[[File:Countryside.jpg|class=fullwidth|center]]&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
This is where AOWIS aims to contribute: by providing an open system for planning, designing, developing, deploying, operating, maintaining, and managing water and agricultural infrastructure in such environments. AOWIS combines a common technical standard with open-source software, engineering guidance, shared knowledge, and operational practices. It supports the full infrastructure lifecycle—from early assessment and conceptual planning, through design and implementation, to monitoring, control, maintenance, adaptation, and long-term operation.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Why an Open System is Needed&lt;br /&gt;
 | color = turquoise&lt;br /&gt;
 | body = &lt;br /&gt;
&lt;br /&gt;
[[File:Cooperation.jpg|400px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
Water and irrigation infrastructure is often developed and expanded over decades by many different actors, using equipment, software, technologies, and engineering approaches from different vendors and manufacturers. Over time, this can result in fragmented systems in which operators must work with incompatible tools, data formats, interfaces, and workflows.&lt;br /&gt;
&lt;br /&gt;
Such fragmentation makes planning, construction, operation, maintenance, expansion, integration, and staff training increasingly difficult and costly. It can also create long-term dependencies on particular products, suppliers, software, or specialist expertise that may no longer be available over the full lifecycle of the infrastructure.&lt;br /&gt;
&lt;br /&gt;
AOWIS provides a shared open foundation intended to keep infrastructure understandable, interoperable, maintainable, and extensible as it grows and changes. Common models, interfaces, engineering principles, software, and operational practices allow different parts of the infrastructure to work together without tying its long-term operation to any single vendor or product.&lt;br /&gt;
&lt;br /&gt;
AOWIS is designed for real-world conditions including long infrastructure lifecycles, heterogeneous equipment, limited technical resources, intermittent connectivity, unreliable power, and the need for local autonomous operation.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Operation Conditions&lt;br /&gt;
 | color = lightblue&lt;br /&gt;
 | body =&lt;br /&gt;
[[File:Village.jpg|250px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS is designed to operate under the real-world conditions faced by local initiatives. These include, among others:&lt;br /&gt;
&lt;br /&gt;
* unreliable power supply&lt;br /&gt;
* intermittent connectivity&lt;br /&gt;
* diverse or aging equipment&lt;br /&gt;
* limited availability of trained personnel&lt;br /&gt;
* the need for safety and autonomous operation&lt;br /&gt;
&lt;br /&gt;
AOWIS enables systems that continue to function safely and reliably, even under degraded or adverse conditions.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Facing the Challenges&lt;br /&gt;
 | color = lightblue&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS addresses these operational challenges through the following principles:&lt;br /&gt;
&lt;br /&gt;
* human-in-the-loop control&lt;br /&gt;
* offline-first operation&lt;br /&gt;
* safe fallback behavior&lt;br /&gt;
* modular and extensible logic&lt;br /&gt;
* shared infrastructure models&lt;br /&gt;
* training programs for local operators&lt;br /&gt;
* transparent governance&lt;br /&gt;
&lt;br /&gt;
The goal is to make essential systems &#039;&#039;&#039;robust, maintainable, and locally operable&#039;&#039;&#039;.&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
| title = Software &amp;amp; Downloads&lt;br /&gt;
| color = green&lt;br /&gt;
| body =&lt;br /&gt;
[[File:GUI ky4 3d.png|400px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS includes an open-source software platform for &#039;&#039;&#039;modelling, simulating, visualizing, monitoring, and operating water infrastructure&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The current software includes a network editor and monitoring interface, hydraulic and water-quality simulation using [[External:EPANET:Main Page|EPANET]], geographic maps and terrain visualization, and support for local and standalone operation. Development is progressing toward a complete AOWIS-compatible SCADA platform.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://download.aowis.org Download the AOWIS Controller (development snapshot)]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* [https://github.com/aowis-org Source code on GitHub]&lt;br /&gt;
* [[#Roadmap|Software development roadmap]]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Start Here&lt;br /&gt;
 | color = yellow&lt;br /&gt;
 | body =&lt;br /&gt;
If you are new to AOWIS, begin with:&lt;br /&gt;
&lt;br /&gt;
* [[Concepts:Design_Philosophy|Design Philosophy]]  &lt;br /&gt;
* [[Standard:Definitions|Definitions]]  &lt;br /&gt;
* [[Standard:Normative_Requirements|Normative Requirements]]  &lt;br /&gt;
* [[Modules:Module_Template|Module Template]]  &lt;br /&gt;
* [[AOWIS:Contributor_Guide_External|Contributor Guide - External]]&lt;br /&gt;
* [[AOWIS:Contributor_Guide_Internal|Contributor Guide - Internal]]&lt;br /&gt;
* [[AOWIS:Writing_Style_Guide|Writing Style Guide]]&lt;br /&gt;
* [[AOWIS:AI_Usage_Guide|AI Usage Guide]]&lt;br /&gt;
* [[AOWIS:Research_Form_Guide|Research Form Guide]]&lt;br /&gt;
* [[AOWIS:Naming_Convention_Specification|Naming Convention Specification]]&lt;br /&gt;
* [[AOWIS:Change_Log__Versioning|Change Log &amp;amp; Versioning]]&lt;br /&gt;
* [[AOWIS:Wiki|This Wiki]]&lt;br /&gt;
&lt;br /&gt;
These pages explain the foundations of AOWIS, how the AOWIS Standard is structured, and how to use and contribute to the project and its documentation.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = List of Requirement Pages&lt;br /&gt;
 | color = brown&lt;br /&gt;
 | body = &lt;br /&gt;
This index lists AOWIS pages that define normative requirements (MUST/SHOULD/MAY statements) and conformance rules.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Dev Rules&#039;&#039;&#039; — specs for writing and maintaining AOWIS&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;REQ-AI:&#039;&#039;&#039; [[AOWIS:AI_Usage_Guide|AI Usage Guide]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Technical Standard&#039;&#039;&#039; — system behavior and data models&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;REQ-MEAS, REQ-MEAS-UI:&#039;&#039;&#039; [[Measurement:Units|Unit System Requirements]]&lt;br /&gt;
* &#039;&#039;&#039;REQ-MEAS-UNI:&#039;&#039;&#039; [[Measurement:Canonical_Units|Canonical Units]]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = AOWIS Documentation Structure&lt;br /&gt;
 | color = purple&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS documentation is organized into dedicated namespaces with clearly separated purposes.&lt;br /&gt;
&lt;br /&gt;
The [[Standard:Main_Page|Standard]] namespace contains the normative requirements that define AOWIS compliance. The other namespaces provide the motivation, concepts, engineering knowledge, architectures, operational models, implementation guidance, reference designs, training material, and supporting information needed to understand, implement, and operate AOWIS systems.&lt;br /&gt;
&lt;br /&gt;
* [[Motivation:Main_Page|Motivation]] – Causal justification of design requirements based on real-world failures, constraints, and operational realities.&lt;br /&gt;
* [[Standard:Main_Page|Standard]] – The normative core of AOWIS. Defines requirements and definitions specifying what AOWIS-compliant systems MUST, SHOULD, or MAY do.&lt;br /&gt;
* [[Concepts:Main_Page|Concepts]] – Core ideas, philosophy, rationale, and contextual understanding that explain AOWIS without prescribing a specific implementation.&lt;br /&gt;
* [[Architecture:Main_Page|Architecture]] – High-level system structure, including controllers, layers, communication, data flows, and their interactions.&lt;br /&gt;
* [[Infrastructure:Main_Page|Infrastructure]] – Physical technologies, systems, and components used in AOWIS deployments. Infrastructure pages describe classes of physical systems rather than specific implementation blueprints.&lt;br /&gt;
* [[Measurement:Main_Page|Measurement]] – Definition and handling of sensor data, manual measurements, calibration, uncertainty, and derived physical values.&lt;br /&gt;
* [[Data:Main_Page|Data]] – Data models, schemas, logging structures, synchronization formats, and data lifecycle rules.&lt;br /&gt;
* [[Operations:Main_Page|Operations]] – Runtime behavior, control logic, state transitions, fallback behavior, and decision-making during system operation.&lt;br /&gt;
* [[Modules:Main_Page|Modules]] – Reusable functional extensions that provide domain-specific capabilities within AOWIS.&lt;br /&gt;
* [[Reference:Main_Page|Reference]] – Non-normative concrete implementations, engineering blueprints, example deployments, and validated design patterns showing specific ways AOWIS systems may be built.&lt;br /&gt;
* [[Databases:Main_Page|Databases]] – Federated knowledge bases and structured supporting information used by AOWIS implementations.&lt;br /&gt;
* [[Governance:Main_Page|Governance]] – Certification, compliance, auditing, trust, licensing, versioning, and organizational governance.&lt;br /&gt;
* [[Training:Main_Page|Training]] – Operator education, technical training, field guidance, documentation literacy, and capacity building.&lt;br /&gt;
* [[External:Main_Page|External]] – External projects, standards, technologies, and systems that relate to or influence AOWIS.&lt;br /&gt;
&lt;br /&gt;
* [[Regions:Main_Page|Regions]] – Geographic, environmental, hydrological, climatic, socioeconomic, and infrastructure context for areas in which AOWIS is researched, planned, or deployed.&lt;br /&gt;
&lt;br /&gt;
For a full overview, see the [[AOWIS:Table_of_Contents|Table of Contents]].&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Roadmap&lt;br /&gt;
 | color = grey&lt;br /&gt;
 | body =&lt;br /&gt;
[[File:Boring.jpg|250px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS has progressed beyond its initial conceptual phase. A substantial software foundation for modelling, simulating, visualizing, and eventually operating water infrastructure is under active development.&lt;br /&gt;
&lt;br /&gt;
The current software stack already includes:&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Shared infrastructure model&#039;&#039;&#039;&lt;br /&gt;
: A common, solver-independent representation of water infrastructure used throughout the AOWIS software stack.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-MODEL GitHub AOWIS-SERVER-MODEL]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Hydraulic and water-quality simulation&#039;&#039;&#039;&lt;br /&gt;
: EPANET integration for hydraulic and water-quality simulation, network import/export, controls, rules, diagnostics, and simulation results. Integration of &#039;&#039;&#039;EPANET-MSX&#039;&#039;&#039; is also being developed.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-EPANET GitHub AOWIS-SERVER-EPANET]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Network editor and monitoring interface&#039;&#039;&#039;&lt;br /&gt;
: A graphical application for creating, inspecting, simulating, and visualizing water networks, including geographic maps and terrain-aware 3D visualization.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-GUI GitHub AOWIS-SERVER-GUI]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Geographic and terrain infrastructure&#039;&#039;&#039;&lt;br /&gt;
: Mapping, elevation data, basemaps, terrain visualization, geographic placement, and local caching.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-MAP GitHub AOWIS-SERVER-MAP]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Local and standalone operation&#039;&#039;&#039;&lt;br /&gt;
: Support for deployments that do not depend on continuous Internet or cloud connectivity.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-Standalone GitHub AOWIS-SERVER-Standalone]&lt;br /&gt;
&lt;br /&gt;
The software remains under active development and should not yet be considered a complete production SCADA system.&lt;br /&gt;
&lt;br /&gt;
The next major stage is to connect the existing modelling and simulation environment to &#039;&#039;&#039;real infrastructure in continuous operation&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
AOWIS is intended to develop into a complete open-source &#039;&#039;&#039;SCADA, infrastructure modelling, simulation, and operational management platform&#039;&#039;&#039; in which planning, live monitoring, control, historical data, maintenance, and simulation operate on the same shared infrastructure model.&lt;br /&gt;
&lt;br /&gt;
This includes telemetry, sensors and actuators, alarms and historian functions, local and remote control, automation with safe fallback behaviour, and model-assisted operation using measured and simulated system behaviour.&lt;br /&gt;
&lt;br /&gt;
EPANET currently provides the primary hydraulic and water-quality simulation engine, but AOWIS is not designed solely as an EPANET frontend. EPANET is one solver integrated into a broader, solver-independent architecture.&lt;br /&gt;
&lt;br /&gt;
The long-term objective is to connect the complete infrastructure lifecycle:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;survey and planning → engineering and simulation → construction → commissioning → monitoring → control → maintenance → analysis → expansion&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[[AOWIS:Roadmap|Read the full roadmap →]]&#039;&#039;&#039;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
| title = Community &amp;amp; Participation&lt;br /&gt;
| color = blue&lt;br /&gt;
| body =&lt;br /&gt;
&lt;br /&gt;
AOWIS is an open project, and participation is welcome from anyone interested in its goals — including engineers, developers, NGOs, operators, researchers, technicians, students, and people with practical experience in water and agricultural infrastructure.&lt;br /&gt;
&lt;br /&gt;
For &#039;&#039;&#039;discussion, planning, questions, documentation, infrastructure, field projects, standards, research, and other forms of participation&#039;&#039;&#039;, AOWIS uses &#039;&#039;&#039;Matrix&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The AOWIS Matrix server has several &#039;&#039;&#039;public spaces and rooms&#039;&#039;&#039; for different topics. Join those relevant to your interests. For general questions or help finding the right place, start here:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://matrix.to/#/#support:aowis.org AOWIS Support — #support:aowis.org]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
You do &#039;&#039;&#039;not&#039;&#039;&#039; need an AOWIS account to participate. Any Matrix account can join public AOWIS spaces and rooms.&lt;br /&gt;
&lt;br /&gt;
If you are new to Matrix:&lt;br /&gt;
&lt;br /&gt;
* [https://matrix.org/try-matrix/ Learn about Matrix and create an account]&lt;br /&gt;
* [https://element.io/ Element] — Matrix client for web, desktop, and mobile&lt;br /&gt;
* [https://fluffychat.im/ FluffyChat] — simple Matrix client for several platforms&lt;br /&gt;
&lt;br /&gt;
The same Matrix account can be used with different clients.&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;AOWIS Matrix Accounts&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Participants may also request an account on the AOWIS Matrix homeserver, giving them an ID such as &#039;&#039;&#039;@name:aowis.org&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
To reduce automated registrations and abuse, accounts are created on request. Please send a short introduction telling us who you are, what interests you about AOWIS, and where you would like to participate: [[File:Mtx.png|120px|frameless|alt=Email address for requesting an AOWIS Matrix account]]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Software Development&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Software development remains on &#039;&#039;&#039;GitHub&#039;&#039;&#039;. Bug reports, pull requests, source-code contributions, and repository-specific development discussions should use the appropriate repository.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://github.com/aowis-org AOWIS on GitHub]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Matrix is for the broader AOWIS community and participation that does not naturally belong in a GitHub repository.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Governance &amp;amp; Legitimacy&lt;br /&gt;
 | color = turquoise&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS includes a transparent governance model to ensure:&lt;br /&gt;
&lt;br /&gt;
* open participation  &lt;br /&gt;
* clear certification processes  &lt;br /&gt;
* stable versioning  &lt;br /&gt;
* long‑term protection of the standard  &lt;br /&gt;
&lt;br /&gt;
See: [[Governance:Main_Page|Governance]].&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Navigation&lt;br /&gt;
 | color = grey&lt;br /&gt;
 | body =&lt;br /&gt;
* [[AOWIS:Table_of_Contents|Table of Contents]]  &lt;br /&gt;
* [[Reference:Glossary|Glossary]]  &lt;br /&gt;
* [[Reference:FAQ|FAQ]]  &lt;br /&gt;
* [[Reference:Change_Log|Change Log]]  &lt;br /&gt;
&lt;br /&gt;
* [https://github.com/aowis-org GitHub]&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Partners&lt;br /&gt;
 | color = indigo&lt;br /&gt;
 | body = &lt;br /&gt;
[[File:Afriticgroup.webp|250px|frameless|center|link=https://afriticgroup.com/]]&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Samuel</name></author>
	</entry>
	<entry>
		<id>https://aowis.org/index.php?title=Template:MainPageBanner&amp;diff=758</id>
		<title>Template:MainPageBanner</title>
		<link rel="alternate" type="text/html" href="https://aowis.org/index.php?title=Template:MainPageBanner&amp;diff=758"/>
		<updated>2026-09-23T15:35:52Z</updated>

		<summary type="html">&lt;p&gt;Samuel: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;div class=&amp;quot;mainpage-banner&amp;quot; style=&amp;quot;&lt;br /&gt;
    background: var(--background-color-neutral-subtle, #f8f9fa);&lt;br /&gt;
    border: 1px solid var(--border-color-base, #a2a9b1);&lt;br /&gt;
    padding: 1.5em;&lt;br /&gt;
    margin-bottom: 1.5em;&lt;br /&gt;
    border-radius: 4px;&lt;br /&gt;
    color: var(--color-base, #202122);&lt;br /&gt;
&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1 style=&amp;quot;&lt;br /&gt;
    margin: 0 0 0.8em 0;&lt;br /&gt;
    font-size: 2em;&lt;br /&gt;
    font-weight: normal;&lt;br /&gt;
    color: var(--color-base, #202122);&lt;br /&gt;
&amp;quot;&amp;gt;&lt;br /&gt;
    &#039;&#039;&#039;AOWIS – Afritic Open Water Infrastructure System&#039;&#039;&#039;&lt;br /&gt;
&amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[File:Logo.png|frameless|right|150px]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;flex: 1;&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;p style=&amp;quot;margin: 0 0 0.6em 0; font-size: 1.15em;&amp;quot;&amp;gt;&lt;br /&gt;
        &#039;&#039;&#039;AOWIS&#039;&#039;&#039; (&#039;&#039;&#039;A&#039;&#039;&#039;fritic &#039;&#039;&#039;O&#039;&#039;&#039;pen &#039;&#039;&#039;W&#039;&#039;&#039;ater &#039;&#039;&#039;I&#039;&#039;&#039;nfrastructure &#039;&#039;&#039;S&#039;&#039;&#039;ystem) is an open system for planning, designing, modelling, building, operating, maintaining, and extending safe and reliable &#039;&#039;&#039;water and irrigation infrastructure&#039;&#039;&#039; throughout its lifecycle.&lt;br /&gt;
    &amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;p style=&amp;quot;margin: 0 0 0.6em 0; font-size: 1.15em;&amp;quot;&amp;gt;&lt;br /&gt;
        AOWIS brings together open technical standards, open-source software, shared infrastructure models, engineering methods, reference implementations, operational guidance, and training. It provides a common foundation for modelling, simulation, monitoring, control, automation, data exchange, and day-to-day operation.&lt;br /&gt;
    &amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;p style=&amp;quot;margin: 0; font-size: 1.15em;&amp;quot;&amp;gt;&lt;br /&gt;
        It is intended for communities, utilities, organizations, engineers, and others involved in water infrastructure, while remaining practical under difficult conditions such as intermittent connectivity, unreliable power, limited technical resources, and the need for local autonomous operation.&lt;br /&gt;
    &amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;div class=&amp;quot;plainlinks&amp;quot; style=&amp;quot;&lt;br /&gt;
    margin-top: 0.8em;&lt;br /&gt;
    font-size: 0.9em;&lt;br /&gt;
    white-space: nowrap;&lt;br /&gt;
&amp;quot;&amp;gt;&#039;&#039;&#039;[[#Software &amp;amp; Downloads|Software &amp;amp; Downloads]]&#039;&#039;&#039; &amp;amp;nbsp;·&amp;amp;nbsp; &#039;&#039;&#039;[[#Community &amp;amp; Participation|Community &amp;amp; Participation]]&#039;&#039;&#039; &amp;amp;nbsp;·&amp;amp;nbsp; &#039;&#039;&#039;[[Standard:Main_Page|Access the Standard]]&#039;&#039;&#039;&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;/div&gt;</summary>
		<author><name>Samuel</name></author>
	</entry>
	<entry>
		<id>https://aowis.org/index.php?title=Template:MainPageBanner&amp;diff=757</id>
		<title>Template:MainPageBanner</title>
		<link rel="alternate" type="text/html" href="https://aowis.org/index.php?title=Template:MainPageBanner&amp;diff=757"/>
		<updated>2026-09-23T15:26:28Z</updated>

		<summary type="html">&lt;p&gt;Samuel: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;div class=&amp;quot;mainpage-banner&amp;quot; style=&amp;quot;&lt;br /&gt;
    background: var(--background-color-neutral-subtle, #f8f9fa);&lt;br /&gt;
    border: 1px solid var(--border-color-base, #a2a9b1);&lt;br /&gt;
    padding: 1.5em;&lt;br /&gt;
    margin-bottom: 1.5em;&lt;br /&gt;
    border-radius: 4px;&lt;br /&gt;
    color: var(--color-base, #202122);&lt;br /&gt;
&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1 style=&amp;quot;&lt;br /&gt;
    margin: 0 0 0.8em 0;&lt;br /&gt;
    font-size: 2em;&lt;br /&gt;
    font-weight: normal;&lt;br /&gt;
    color: var(--color-base, #202122);&lt;br /&gt;
&amp;quot;&amp;gt;&lt;br /&gt;
    &#039;&#039;&#039;AOWIS – Afritic Open Water Infrastructure System&#039;&#039;&#039;&lt;br /&gt;
&amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[File:Logo.png|frameless|right|150px]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;flex: 1;&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;p style=&amp;quot;margin: 0 0 0.6em 0; font-size: 1.15em;&amp;quot;&amp;gt;&lt;br /&gt;
        &#039;&#039;&#039;AOWIS&#039;&#039;&#039; (&#039;&#039;&#039;A&#039;&#039;&#039;fritic &#039;&#039;&#039;O&#039;&#039;&#039;pen &#039;&#039;&#039;W&#039;&#039;&#039;ater &#039;&#039;&#039;I&#039;&#039;&#039;nfrastructure &#039;&#039;&#039;S&#039;&#039;&#039;ystem) is an open system for designing, modelling, operating, and maintaining safe and reliable &#039;&#039;&#039;water and irrigation infrastructure&#039;&#039;&#039;.&lt;br /&gt;
    &amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;p style=&amp;quot;margin: 0 0 0.6em 0; font-size: 1.15em;&amp;quot;&amp;gt;&lt;br /&gt;
        It provides a common foundation for infrastructure modelling, monitoring, control, automation, data exchange, engineering practice, and day-to-day operation. AOWIS combines an open technical standard with open-source software, reference implementations, engineering knowledge, operational guidance, and training.&lt;br /&gt;
    &amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;p style=&amp;quot;margin: 0; font-size: 1.15em;&amp;quot;&amp;gt;&lt;br /&gt;
        AOWIS is intended for use by communities, utilities, organizations, and other operators of water infrastructure, while remaining practical under difficult conditions such as intermittent connectivity, unreliable power, limited technical resources, and the need for local autonomous operation.&lt;br /&gt;
    &amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;div class=&amp;quot;plainlinks&amp;quot; style=&amp;quot;&lt;br /&gt;
    margin-top: 0.8em;&lt;br /&gt;
    font-size: 0.9em;&lt;br /&gt;
    white-space: nowrap;&lt;br /&gt;
&amp;quot;&amp;gt;&#039;&#039;&#039;[[#Software &amp;amp; Downloads|Software &amp;amp; Downloads]]&#039;&#039;&#039; &amp;amp;nbsp;·&amp;amp;nbsp; &#039;&#039;&#039;[[#Community &amp;amp; Participation|Community &amp;amp; Participation]]&#039;&#039;&#039; &amp;amp;nbsp;·&amp;amp;nbsp; &#039;&#039;&#039;[[Standard:Main_Page|Access the Standard]]&#039;&#039;&#039;&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;/div&gt;</summary>
		<author><name>Samuel</name></author>
	</entry>
	<entry>
		<id>https://aowis.org/index.php?title=Main_Page&amp;diff=756</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://aowis.org/index.php?title=Main_Page&amp;diff=756"/>
		<updated>2026-09-23T15:21:52Z</updated>

		<summary type="html">&lt;p&gt;Samuel: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
&lt;br /&gt;
{{MainPageBanner}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Motivation&lt;br /&gt;
 | color = teal&lt;br /&gt;
 | body = &lt;br /&gt;
&lt;br /&gt;
[[File:Countryside.jpg|class=fullwidth|center]]&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
This is where AOWIS aims to contribute: by providing an open system for planning, designing, developing, deploying, operating, maintaining, and managing water and agricultural infrastructure in such environments. AOWIS combines a common technical standard with open-source software, engineering guidance, shared knowledge, and operational practices. It supports the full infrastructure lifecycle—from early assessment and conceptual planning, through design and implementation, to monitoring, control, maintenance, adaptation, and long-term operation.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Why an Open System is Needed&lt;br /&gt;
 | color = turquoise&lt;br /&gt;
 | body = &lt;br /&gt;
&lt;br /&gt;
[[File:Cooperation.jpg|400px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
In environments where infrastructure is developed over decades by many different actors using solutions from different vendors and manufacturers, systems often become fragmented. Operators are then forced to work with multiple incompatible tools, technologies, data formats, and workflows, making planning, construction, daily operation, maintenance, expansion, integration, and staff training increasingly complex and costly.&lt;br /&gt;
&lt;br /&gt;
This fragmentation can also create dependencies on specific products, suppliers, software, or specialist expertise that may no longer be available over the full lifecycle of the infrastructure.&lt;br /&gt;
&lt;br /&gt;
AOWIS addresses this by providing a shared open system for planning, designing, building, operating, maintaining, extending, and managing water and agricultural infrastructure. It combines a common technical standard with open-source software, engineering guidance, shared knowledge, reference implementations, and operational practices.&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;AOWIS Standard&#039;&#039;&#039; forms the normative technical core of this system, providing common requirements and interfaces that support interoperability and help infrastructure remain understandable, maintainable, and extensible independently of any single vendor or product.&lt;br /&gt;
&lt;br /&gt;
AOWIS is designed for real-world operational conditions, including long infrastructure lifecycles, heterogeneous equipment, limited technical resources, intermittent connectivity, unreliable power, and the need for local autonomous operation.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Operation Conditions&lt;br /&gt;
 | color = lightblue&lt;br /&gt;
 | body =&lt;br /&gt;
[[File:Village.jpg|250px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS is designed to operate under the real-world conditions faced by local initiatives. These include, among others:&lt;br /&gt;
&lt;br /&gt;
* unreliable power supply&lt;br /&gt;
* intermittent connectivity&lt;br /&gt;
* diverse or aging equipment&lt;br /&gt;
* limited availability of trained personnel&lt;br /&gt;
* the need for safety and autonomous operation&lt;br /&gt;
&lt;br /&gt;
AOWIS enables systems that continue to function safely and reliably, even under degraded or adverse conditions.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Facing the Challenges&lt;br /&gt;
 | color = lightblue&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS addresses these operational challenges through the following principles:&lt;br /&gt;
&lt;br /&gt;
* human-in-the-loop control&lt;br /&gt;
* offline-first operation&lt;br /&gt;
* safe fallback behavior&lt;br /&gt;
* modular and extensible logic&lt;br /&gt;
* shared infrastructure models&lt;br /&gt;
* training programs for local operators&lt;br /&gt;
* transparent governance&lt;br /&gt;
&lt;br /&gt;
The goal is to make essential systems &#039;&#039;&#039;robust, maintainable, and locally operable&#039;&#039;&#039;.&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
| title = Software &amp;amp; Downloads&lt;br /&gt;
| color = green&lt;br /&gt;
| body =&lt;br /&gt;
[[File:GUI ky4 3d.png|400px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS includes an open-source software platform for &#039;&#039;&#039;modelling, simulating, visualizing, monitoring, and operating water infrastructure&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The current software includes a network editor and monitoring interface, hydraulic and water-quality simulation using [[External:EPANET:Main Page|EPANET]], geographic maps and terrain visualization, and support for local and standalone operation. Development is progressing toward a complete AOWIS-compatible SCADA platform.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://download.aowis.org Download the AOWIS Controller (development snapshot)]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* [https://github.com/aowis-org Source code on GitHub]&lt;br /&gt;
* [[#Roadmap|Software development roadmap]]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Start Here&lt;br /&gt;
 | color = yellow&lt;br /&gt;
 | body =&lt;br /&gt;
If you are new to AOWIS, begin with:&lt;br /&gt;
&lt;br /&gt;
* [[Concepts:Design_Philosophy|Design Philosophy]]  &lt;br /&gt;
* [[Standard:Definitions|Definitions]]  &lt;br /&gt;
* [[Standard:Normative_Requirements|Normative Requirements]]  &lt;br /&gt;
* [[Modules:Module_Template|Module Template]]  &lt;br /&gt;
* [[AOWIS:Contributor_Guide_External|Contributor Guide - External]]&lt;br /&gt;
* [[AOWIS:Contributor_Guide_Internal|Contributor Guide - Internal]]&lt;br /&gt;
* [[AOWIS:Writing_Style_Guide|Writing Style Guide]]&lt;br /&gt;
* [[AOWIS:AI_Usage_Guide|AI Usage Guide]]&lt;br /&gt;
* [[AOWIS:Research_Form_Guide|Research Form Guide]]&lt;br /&gt;
* [[AOWIS:Naming_Convention_Specification|Naming Convention Specification]]&lt;br /&gt;
* [[AOWIS:Change_Log__Versioning|Change Log &amp;amp; Versioning]]&lt;br /&gt;
* [[AOWIS:Wiki|This Wiki]]&lt;br /&gt;
&lt;br /&gt;
These pages explain the foundations of AOWIS, how the AOWIS Standard is structured, and how to use and contribute to the project and its documentation.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = List of Requirement Pages&lt;br /&gt;
 | color = brown&lt;br /&gt;
 | body = &lt;br /&gt;
This index lists AOWIS pages that define normative requirements (MUST/SHOULD/MAY statements) and conformance rules.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Dev Rules&#039;&#039;&#039; — specs for writing and maintaining AOWIS&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;REQ-AI:&#039;&#039;&#039; [[AOWIS:AI_Usage_Guide|AI Usage Guide]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Technical Standard&#039;&#039;&#039; — system behavior and data models&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;REQ-MEAS, REQ-MEAS-UI:&#039;&#039;&#039; [[Measurement:Units|Unit System Requirements]]&lt;br /&gt;
* &#039;&#039;&#039;REQ-MEAS-UNI:&#039;&#039;&#039; [[Measurement:Canonical_Units|Canonical Units]]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = AOWIS Documentation Structure&lt;br /&gt;
 | color = purple&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS documentation is organized into dedicated namespaces with clearly separated purposes.&lt;br /&gt;
&lt;br /&gt;
The [[Standard:Main_Page|Standard]] namespace contains the normative requirements that define AOWIS compliance. The other namespaces provide the motivation, concepts, engineering knowledge, architectures, operational models, implementation guidance, reference designs, training material, and supporting information needed to understand, implement, and operate AOWIS systems.&lt;br /&gt;
&lt;br /&gt;
* [[Motivation:Main_Page|Motivation]] – Causal justification of design requirements based on real-world failures, constraints, and operational realities.&lt;br /&gt;
* [[Standard:Main_Page|Standard]] – The normative core of AOWIS. Defines requirements and definitions specifying what AOWIS-compliant systems MUST, SHOULD, or MAY do.&lt;br /&gt;
* [[Concepts:Main_Page|Concepts]] – Core ideas, philosophy, rationale, and contextual understanding that explain AOWIS without prescribing a specific implementation.&lt;br /&gt;
* [[Architecture:Main_Page|Architecture]] – High-level system structure, including controllers, layers, communication, data flows, and their interactions.&lt;br /&gt;
* [[Infrastructure:Main_Page|Infrastructure]] – Physical technologies, systems, and components used in AOWIS deployments. Infrastructure pages describe classes of physical systems rather than specific implementation blueprints.&lt;br /&gt;
* [[Measurement:Main_Page|Measurement]] – Definition and handling of sensor data, manual measurements, calibration, uncertainty, and derived physical values.&lt;br /&gt;
* [[Data:Main_Page|Data]] – Data models, schemas, logging structures, synchronization formats, and data lifecycle rules.&lt;br /&gt;
* [[Operations:Main_Page|Operations]] – Runtime behavior, control logic, state transitions, fallback behavior, and decision-making during system operation.&lt;br /&gt;
* [[Modules:Main_Page|Modules]] – Reusable functional extensions that provide domain-specific capabilities within AOWIS.&lt;br /&gt;
* [[Reference:Main_Page|Reference]] – Non-normative concrete implementations, engineering blueprints, example deployments, and validated design patterns showing specific ways AOWIS systems may be built.&lt;br /&gt;
* [[Databases:Main_Page|Databases]] – Federated knowledge bases and structured supporting information used by AOWIS implementations.&lt;br /&gt;
* [[Governance:Main_Page|Governance]] – Certification, compliance, auditing, trust, licensing, versioning, and organizational governance.&lt;br /&gt;
* [[Training:Main_Page|Training]] – Operator education, technical training, field guidance, documentation literacy, and capacity building.&lt;br /&gt;
* [[External:Main_Page|External]] – External projects, standards, technologies, and systems that relate to or influence AOWIS.&lt;br /&gt;
&lt;br /&gt;
* [[Regions:Main_Page|Regions]] – Geographic, environmental, hydrological, climatic, socioeconomic, and infrastructure context for areas in which AOWIS is researched, planned, or deployed.&lt;br /&gt;
&lt;br /&gt;
For a full overview, see the [[AOWIS:Table_of_Contents|Table of Contents]].&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Roadmap&lt;br /&gt;
 | color = grey&lt;br /&gt;
 | body =&lt;br /&gt;
[[File:Boring.jpg|250px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS has progressed beyond its initial conceptual phase. A substantial software foundation for modelling, simulating, visualizing, and eventually operating water infrastructure is under active development.&lt;br /&gt;
&lt;br /&gt;
The current software stack already includes:&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Shared infrastructure model&#039;&#039;&#039;&lt;br /&gt;
: A common, solver-independent representation of water infrastructure used throughout the AOWIS software stack.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-MODEL GitHub AOWIS-SERVER-MODEL]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Hydraulic and water-quality simulation&#039;&#039;&#039;&lt;br /&gt;
: EPANET integration for hydraulic and water-quality simulation, network import/export, controls, rules, diagnostics, and simulation results. Integration of &#039;&#039;&#039;EPANET-MSX&#039;&#039;&#039; is also being developed.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-EPANET GitHub AOWIS-SERVER-EPANET]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Network editor and monitoring interface&#039;&#039;&#039;&lt;br /&gt;
: A graphical application for creating, inspecting, simulating, and visualizing water networks, including geographic maps and terrain-aware 3D visualization.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-GUI GitHub AOWIS-SERVER-GUI]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Geographic and terrain infrastructure&#039;&#039;&#039;&lt;br /&gt;
: Mapping, elevation data, basemaps, terrain visualization, geographic placement, and local caching.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-MAP GitHub AOWIS-SERVER-MAP]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Local and standalone operation&#039;&#039;&#039;&lt;br /&gt;
: Support for deployments that do not depend on continuous Internet or cloud connectivity.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-Standalone GitHub AOWIS-SERVER-Standalone]&lt;br /&gt;
&lt;br /&gt;
The software remains under active development and should not yet be considered a complete production SCADA system.&lt;br /&gt;
&lt;br /&gt;
The next major stage is to connect the existing modelling and simulation environment to &#039;&#039;&#039;real infrastructure in continuous operation&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
AOWIS is intended to develop into a complete open-source &#039;&#039;&#039;SCADA, infrastructure modelling, simulation, and operational management platform&#039;&#039;&#039; in which planning, live monitoring, control, historical data, maintenance, and simulation operate on the same shared infrastructure model.&lt;br /&gt;
&lt;br /&gt;
This includes telemetry, sensors and actuators, alarms and historian functions, local and remote control, automation with safe fallback behaviour, and model-assisted operation using measured and simulated system behaviour.&lt;br /&gt;
&lt;br /&gt;
EPANET currently provides the primary hydraulic and water-quality simulation engine, but AOWIS is not designed solely as an EPANET frontend. EPANET is one solver integrated into a broader, solver-independent architecture.&lt;br /&gt;
&lt;br /&gt;
The long-term objective is to connect the complete infrastructure lifecycle:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;survey and planning → engineering and simulation → construction → commissioning → monitoring → control → maintenance → analysis → expansion&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[[AOWIS:Roadmap|Read the full roadmap →]]&#039;&#039;&#039;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
| title = Community &amp;amp; Participation&lt;br /&gt;
| color = blue&lt;br /&gt;
| body =&lt;br /&gt;
&lt;br /&gt;
AOWIS is an open project, and participation is welcome from anyone interested in its goals — including engineers, developers, NGOs, operators, researchers, technicians, students, and people with practical experience in water and agricultural infrastructure.&lt;br /&gt;
&lt;br /&gt;
For &#039;&#039;&#039;discussion, planning, questions, documentation, infrastructure, field projects, standards, research, and other forms of participation&#039;&#039;&#039;, AOWIS uses &#039;&#039;&#039;Matrix&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The AOWIS Matrix server has several &#039;&#039;&#039;public spaces and rooms&#039;&#039;&#039; for different topics. Join those relevant to your interests. For general questions or help finding the right place, start here:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://matrix.to/#/#support:aowis.org AOWIS Support — #support:aowis.org]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
You do &#039;&#039;&#039;not&#039;&#039;&#039; need an AOWIS account to participate. Any Matrix account can join public AOWIS spaces and rooms.&lt;br /&gt;
&lt;br /&gt;
If you are new to Matrix:&lt;br /&gt;
&lt;br /&gt;
* [https://matrix.org/try-matrix/ Learn about Matrix and create an account]&lt;br /&gt;
* [https://element.io/ Element] — Matrix client for web, desktop, and mobile&lt;br /&gt;
* [https://fluffychat.im/ FluffyChat] — simple Matrix client for several platforms&lt;br /&gt;
&lt;br /&gt;
The same Matrix account can be used with different clients.&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;AOWIS Matrix Accounts&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Participants may also request an account on the AOWIS Matrix homeserver, giving them an ID such as &#039;&#039;&#039;@name:aowis.org&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
To reduce automated registrations and abuse, accounts are created on request. Please send a short introduction telling us who you are, what interests you about AOWIS, and where you would like to participate: [[File:Mtx.png|120px|frameless|alt=Email address for requesting an AOWIS Matrix account]]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Software Development&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Software development remains on &#039;&#039;&#039;GitHub&#039;&#039;&#039;. Bug reports, pull requests, source-code contributions, and repository-specific development discussions should use the appropriate repository.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://github.com/aowis-org AOWIS on GitHub]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Matrix is for the broader AOWIS community and participation that does not naturally belong in a GitHub repository.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Governance &amp;amp; Legitimacy&lt;br /&gt;
 | color = turquoise&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS includes a transparent governance model to ensure:&lt;br /&gt;
&lt;br /&gt;
* open participation  &lt;br /&gt;
* clear certification processes  &lt;br /&gt;
* stable versioning  &lt;br /&gt;
* long‑term protection of the standard  &lt;br /&gt;
&lt;br /&gt;
See: [[Governance:Main_Page|Governance]].&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Navigation&lt;br /&gt;
 | color = grey&lt;br /&gt;
 | body =&lt;br /&gt;
* [[AOWIS:Table_of_Contents|Table of Contents]]  &lt;br /&gt;
* [[Reference:Glossary|Glossary]]  &lt;br /&gt;
* [[Reference:FAQ|FAQ]]  &lt;br /&gt;
* [[Reference:Change_Log|Change Log]]  &lt;br /&gt;
&lt;br /&gt;
* [https://github.com/aowis-org GitHub]&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Partners&lt;br /&gt;
 | color = indigo&lt;br /&gt;
 | body = &lt;br /&gt;
[[File:Afriticgroup.webp|250px|frameless|center|link=https://afriticgroup.com/]]&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Samuel</name></author>
	</entry>
	<entry>
		<id>https://aowis.org/index.php?title=Main_Page&amp;diff=755</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://aowis.org/index.php?title=Main_Page&amp;diff=755"/>
		<updated>2026-09-23T15:14:38Z</updated>

		<summary type="html">&lt;p&gt;Samuel: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
&lt;br /&gt;
{{MainPageBanner}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Motivation&lt;br /&gt;
 | color = teal&lt;br /&gt;
 | body = &lt;br /&gt;
&lt;br /&gt;
[[File:Countryside.jpg|class=fullwidth|center]]&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
This is where AOWIS aims to contribute: by providing an open system for planning, designing, developing, deploying, operating, maintaining, and managing water and agricultural infrastructure in such environments. AOWIS combines a common technical standard with open-source software, engineering guidance, shared knowledge, and operational practices. It supports the full infrastructure lifecycle—from early assessment and conceptual planning, through design and implementation, to monitoring, control, maintenance, adaptation, and long-term operation.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Why an Open System is Needed&lt;br /&gt;
 | color = turquoise&lt;br /&gt;
 | body = &lt;br /&gt;
&lt;br /&gt;
[[File:Cooperation.jpg|400px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
In environments where infrastructure is developed over decades by many different actors using solutions from different vendors and manufacturers, systems often become fragmented. Operators are then forced to work with multiple incompatible tools, technologies, data formats, and workflows, making planning, construction, daily operation, maintenance, expansion, integration, and staff training increasingly complex and costly.&lt;br /&gt;
&lt;br /&gt;
This fragmentation can also create dependencies on specific products, suppliers, software, or specialist expertise that may no longer be available over the full lifecycle of the infrastructure.&lt;br /&gt;
&lt;br /&gt;
AOWIS addresses this by providing a shared open system for planning, designing, building, operating, maintaining, extending, and managing water and agricultural infrastructure. It combines a common technical standard with open-source software, engineering guidance, shared knowledge, reference implementations, and operational practices.&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;AOWIS Standard&#039;&#039;&#039; forms the normative technical core of this system, providing common requirements and interfaces that support interoperability and help infrastructure remain understandable, maintainable, and extensible independently of any single vendor or product.&lt;br /&gt;
&lt;br /&gt;
AOWIS is designed for real-world operational conditions, including long infrastructure lifecycles, heterogeneous equipment, limited technical resources, intermittent connectivity, unreliable power, and the need for local autonomous operation.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Operation Conditions&lt;br /&gt;
 | color = lightblue&lt;br /&gt;
 | body =&lt;br /&gt;
[[File:Village.jpg|250px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS is designed to operate under the real-world conditions faced by local initiatives. These include, among others:&lt;br /&gt;
&lt;br /&gt;
* unreliable power supply&lt;br /&gt;
* intermittent connectivity&lt;br /&gt;
* diverse or aging equipment&lt;br /&gt;
* limited availability of trained personnel&lt;br /&gt;
* the need for safety and autonomous operation&lt;br /&gt;
&lt;br /&gt;
AOWIS enables systems that continue to function safely and reliably, even under degraded or adverse conditions.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Facing the Challenges&lt;br /&gt;
 | color = lightblue&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS addresses these operational challenges through the following principles:&lt;br /&gt;
&lt;br /&gt;
* human-in-the-loop control&lt;br /&gt;
* offline-first operation&lt;br /&gt;
* safe fallback behavior&lt;br /&gt;
* modular and extensible logic&lt;br /&gt;
* shared infrastructure models&lt;br /&gt;
* training programs for local operators&lt;br /&gt;
* transparent governance&lt;br /&gt;
&lt;br /&gt;
The goal is to make essential systems &#039;&#039;&#039;robust, maintainable, and locally operable&#039;&#039;&#039;.&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
| title = Software &amp;amp; Downloads&lt;br /&gt;
| color = green&lt;br /&gt;
| body =&lt;br /&gt;
[[File:GUI ky4 3d.png|400px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS includes an open-source software platform for &#039;&#039;&#039;modelling, simulating, visualizing, monitoring, and operating water infrastructure&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The current software includes a network editor and monitoring interface, hydraulic and water-quality simulation using [[External:EPANET:Main Page|EPANET]], geographic maps and terrain visualization, and support for local and standalone operation. Development is progressing toward a complete AOWIS-compatible SCADA platform.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://download.aowis.org Download the AOWIS Controller (development snapshot)]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* [https://github.com/aowis-org Source code on GitHub]&lt;br /&gt;
* [[#Roadmap|Software development roadmap]]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Start Here&lt;br /&gt;
 | color = yellow&lt;br /&gt;
 | body =&lt;br /&gt;
If you are new to AOWIS, begin with:&lt;br /&gt;
&lt;br /&gt;
* [[Concepts:Design_Philosophy|Design Philosophy]]  &lt;br /&gt;
* [[Standard:Definitions|Definitions]]  &lt;br /&gt;
* [[Standard:Normative_Requirements|Normative Requirements]]  &lt;br /&gt;
* [[Modules:Module_Template|Module Template]]  &lt;br /&gt;
* [[AOWIS:Contributor_Guide_External|Contributor Guide - External]]&lt;br /&gt;
* [[AOWIS:Contributor_Guide_Internal|Contributor Guide - Internal]]&lt;br /&gt;
* [[AOWIS:Writing_Style_Guide|Writing Style Guide]]&lt;br /&gt;
* [[AOWIS:AI_Usage_Guide|AI Usage Guide]]&lt;br /&gt;
* [[AOWIS:Research_Form_Guide|Research Form Guide]]&lt;br /&gt;
* [[AOWIS:Naming_Convention_Specification|Naming Convention Specification]]&lt;br /&gt;
* [[AOWIS:Change_Log__Versioning|Change Log &amp;amp; Versioning]]&lt;br /&gt;
* [[AOWIS:Wiki|This Wiki]]&lt;br /&gt;
&lt;br /&gt;
These pages explain how to read, use, and contribute to the standard.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = List of Requirement Pages&lt;br /&gt;
 | color = brown&lt;br /&gt;
 | body = &lt;br /&gt;
This index lists AOWIS pages that define normative requirements (MUST/SHOULD/MAY statements) and conformance rules.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Dev Rules&#039;&#039;&#039; — specs for writing and maintaining AOWIS&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;REQ-AI:&#039;&#039;&#039; [[AOWIS:AI_Usage_Guide|AI Usage Guide]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Technical Standard&#039;&#039;&#039; — system behavior and data models&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;REQ-MEAS, REQ-MEAS-UI:&#039;&#039;&#039; [[Measurement:Units|Unit System Requirements]]&lt;br /&gt;
* &#039;&#039;&#039;REQ-MEAS-UNI:&#039;&#039;&#039; [[Measurement:Canonical_Units|Canonical Units]]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = AOWIS Documentation Structure&lt;br /&gt;
 | color = purple&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS documentation is organized into dedicated namespaces with clearly separated purposes.&lt;br /&gt;
&lt;br /&gt;
The [[Standard:Main_Page|Standard]] namespace contains the normative requirements that define AOWIS compliance. The other namespaces provide the motivation, concepts, engineering knowledge, architectures, operational models, implementation guidance, reference designs, training material, and supporting information needed to understand, implement, and operate AOWIS systems.&lt;br /&gt;
&lt;br /&gt;
* [[Motivation:Main_Page|Motivation]] – Causal justification of design requirements based on real-world failures, constraints, and operational realities.&lt;br /&gt;
* [[Standard:Main_Page|Standard]] – The normative core of AOWIS. Defines requirements and definitions specifying what AOWIS-compliant systems MUST, SHOULD, or MAY do.&lt;br /&gt;
* [[Concepts:Main_Page|Concepts]] – Core ideas, philosophy, rationale, and contextual understanding that explain AOWIS without prescribing a specific implementation.&lt;br /&gt;
* [[Architecture:Main_Page|Architecture]] – High-level system structure, including controllers, layers, communication, data flows, and their interactions.&lt;br /&gt;
* [[Infrastructure:Main_Page|Infrastructure]] – Physical technologies, systems, and components used in AOWIS deployments. Infrastructure pages describe classes of physical systems rather than specific implementation blueprints.&lt;br /&gt;
* [[Measurement:Main_Page|Measurement]] – Definition and handling of sensor data, manual measurements, calibration, uncertainty, and derived physical values.&lt;br /&gt;
* [[Data:Main_Page|Data]] – Data models, schemas, logging structures, synchronization formats, and data lifecycle rules.&lt;br /&gt;
* [[Operations:Main_Page|Operations]] – Runtime behavior, control logic, state transitions, fallback behavior, and decision-making during system operation.&lt;br /&gt;
* [[Modules:Main_Page|Modules]] – Reusable functional extensions that provide domain-specific capabilities within AOWIS.&lt;br /&gt;
* [[Reference:Main_Page|Reference]] – Non-normative concrete implementations, engineering blueprints, example deployments, and validated design patterns showing specific ways AOWIS systems may be built.&lt;br /&gt;
* [[Databases:Main_Page|Databases]] – Federated knowledge bases and structured supporting information used by AOWIS implementations.&lt;br /&gt;
* [[Governance:Main_Page|Governance]] – Certification, compliance, auditing, trust, licensing, versioning, and organizational governance.&lt;br /&gt;
* [[Training:Main_Page|Training]] – Operator education, technical training, field guidance, documentation literacy, and capacity building.&lt;br /&gt;
* [[External:Main_Page|External]] – External projects, standards, technologies, and systems that relate to or influence AOWIS.&lt;br /&gt;
&lt;br /&gt;
* [[Regions:Main_Page|Regions]] – Geographic, environmental, hydrological, climatic, socioeconomic, and infrastructure context for areas in which AOWIS is researched, planned, or deployed.&lt;br /&gt;
&lt;br /&gt;
For a full overview, see the [[AOWIS:Table_of_Contents|Table of Contents]].&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Roadmap&lt;br /&gt;
 | color = grey&lt;br /&gt;
 | body =&lt;br /&gt;
[[File:Boring.jpg|250px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS has progressed beyond its initial conceptual phase. A substantial software foundation for modelling, simulating, visualizing, and eventually operating water infrastructure is under active development.&lt;br /&gt;
&lt;br /&gt;
The current software stack already includes:&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Shared infrastructure model&#039;&#039;&#039;&lt;br /&gt;
: A common, solver-independent representation of water infrastructure used throughout the AOWIS software stack.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-MODEL GitHub AOWIS-SERVER-MODEL]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Hydraulic and water-quality simulation&#039;&#039;&#039;&lt;br /&gt;
: EPANET integration for hydraulic and water-quality simulation, network import/export, controls, rules, diagnostics, and simulation results. Integration of &#039;&#039;&#039;EPANET-MSX&#039;&#039;&#039; is also being developed.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-EPANET GitHub AOWIS-SERVER-EPANET]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Network editor and monitoring interface&#039;&#039;&#039;&lt;br /&gt;
: A graphical application for creating, inspecting, simulating, and visualizing water networks, including geographic maps and terrain-aware 3D visualization.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-GUI GitHub AOWIS-SERVER-GUI]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Geographic and terrain infrastructure&#039;&#039;&#039;&lt;br /&gt;
: Mapping, elevation data, basemaps, terrain visualization, geographic placement, and local caching.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-MAP GitHub AOWIS-SERVER-MAP]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Local and standalone operation&#039;&#039;&#039;&lt;br /&gt;
: Support for deployments that do not depend on continuous Internet or cloud connectivity.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-Standalone GitHub AOWIS-SERVER-Standalone]&lt;br /&gt;
&lt;br /&gt;
The software remains under active development and should not yet be considered a complete production SCADA system.&lt;br /&gt;
&lt;br /&gt;
The next major stage is to connect the existing modelling and simulation environment to &#039;&#039;&#039;real infrastructure in continuous operation&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
AOWIS is intended to develop into a complete open-source &#039;&#039;&#039;SCADA, infrastructure modelling, simulation, and operational management platform&#039;&#039;&#039; in which planning, live monitoring, control, historical data, maintenance, and simulation operate on the same shared infrastructure model.&lt;br /&gt;
&lt;br /&gt;
This includes telemetry, sensors and actuators, alarms and historian functions, local and remote control, automation with safe fallback behaviour, and model-assisted operation using measured and simulated system behaviour.&lt;br /&gt;
&lt;br /&gt;
EPANET currently provides the primary hydraulic and water-quality simulation engine, but AOWIS is not designed solely as an EPANET frontend. EPANET is one solver integrated into a broader, solver-independent architecture.&lt;br /&gt;
&lt;br /&gt;
The long-term objective is to connect the complete infrastructure lifecycle:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;survey and planning → engineering and simulation → construction → commissioning → monitoring → control → maintenance → analysis → expansion&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[[AOWIS:Roadmap|Read the full roadmap →]]&#039;&#039;&#039;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
| title = Community &amp;amp; Participation&lt;br /&gt;
| color = blue&lt;br /&gt;
| body =&lt;br /&gt;
&lt;br /&gt;
AOWIS is an open project, and participation is welcome from anyone interested in its goals — including engineers, developers, NGOs, operators, researchers, technicians, students, and people with practical experience in water and agricultural infrastructure.&lt;br /&gt;
&lt;br /&gt;
For &#039;&#039;&#039;discussion, planning, questions, documentation, infrastructure, field projects, standards, research, and other forms of participation&#039;&#039;&#039;, AOWIS uses &#039;&#039;&#039;Matrix&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The AOWIS Matrix server has several &#039;&#039;&#039;public spaces and rooms&#039;&#039;&#039; for different topics. Join those relevant to your interests. For general questions or help finding the right place, start here:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://matrix.to/#/#support:aowis.org AOWIS Support — #support:aowis.org]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
You do &#039;&#039;&#039;not&#039;&#039;&#039; need an AOWIS account to participate. Any Matrix account can join public AOWIS spaces and rooms.&lt;br /&gt;
&lt;br /&gt;
If you are new to Matrix:&lt;br /&gt;
&lt;br /&gt;
* [https://matrix.org/try-matrix/ Learn about Matrix and create an account]&lt;br /&gt;
* [https://element.io/ Element] — Matrix client for web, desktop, and mobile&lt;br /&gt;
* [https://fluffychat.im/ FluffyChat] — simple Matrix client for several platforms&lt;br /&gt;
&lt;br /&gt;
The same Matrix account can be used with different clients.&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;AOWIS Matrix Accounts&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Participants may also request an account on the AOWIS Matrix homeserver, giving them an ID such as &#039;&#039;&#039;@name:aowis.org&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
To reduce automated registrations and abuse, accounts are created on request. Please send a short introduction telling us who you are, what interests you about AOWIS, and where you would like to participate: [[File:Mtx.png|120px|frameless|alt=Email address for requesting an AOWIS Matrix account]]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Software Development&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Software development remains on &#039;&#039;&#039;GitHub&#039;&#039;&#039;. Bug reports, pull requests, source-code contributions, and repository-specific development discussions should use the appropriate repository.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://github.com/aowis-org AOWIS on GitHub]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Matrix is for the broader AOWIS community and participation that does not naturally belong in a GitHub repository.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Governance &amp;amp; Legitimacy&lt;br /&gt;
 | color = turquoise&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS includes a transparent governance model to ensure:&lt;br /&gt;
&lt;br /&gt;
* open participation  &lt;br /&gt;
* clear certification processes  &lt;br /&gt;
* stable versioning  &lt;br /&gt;
* long‑term protection of the standard  &lt;br /&gt;
&lt;br /&gt;
See: [[Governance:Main_Page|Governance]].&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Navigation&lt;br /&gt;
 | color = grey&lt;br /&gt;
 | body =&lt;br /&gt;
* [[AOWIS:Table_of_Contents|Table of Contents]]  &lt;br /&gt;
* [[Reference:Glossary|Glossary]]  &lt;br /&gt;
* [[Reference:FAQ|FAQ]]  &lt;br /&gt;
* [[Reference:Change_Log|Change Log]]  &lt;br /&gt;
&lt;br /&gt;
* [https://github.com/aowis-org GitHub]&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Partners&lt;br /&gt;
 | color = indigo&lt;br /&gt;
 | body = &lt;br /&gt;
[[File:Afriticgroup.webp|250px|frameless|center|link=https://afriticgroup.com/]]&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Samuel</name></author>
	</entry>
	<entry>
		<id>https://aowis.org/index.php?title=Main_Page&amp;diff=754</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://aowis.org/index.php?title=Main_Page&amp;diff=754"/>
		<updated>2026-09-23T15:11:10Z</updated>

		<summary type="html">&lt;p&gt;Samuel: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
&lt;br /&gt;
{{MainPageBanner}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Motivation&lt;br /&gt;
 | color = teal&lt;br /&gt;
 | body = &lt;br /&gt;
&lt;br /&gt;
[[File:Countryside.jpg|class=fullwidth|center]]&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
This is where AOWIS aims to contribute: by providing an open system for planning, designing, developing, deploying, operating, maintaining, and managing water and agricultural infrastructure in such environments. AOWIS combines a common technical standard with open-source software, engineering guidance, shared knowledge, and operational practices. It supports the full infrastructure lifecycle—from early assessment and conceptual planning, through design and implementation, to monitoring, control, maintenance, adaptation, and long-term operation.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Why an Open Standard is Needed&lt;br /&gt;
 | color = turquoise&lt;br /&gt;
 | body = &lt;br /&gt;
&lt;br /&gt;
[[File:Cooperation.jpg|400px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
AOWIS defines such a foundation for water and agricultural infrastructure under real-world operational constraints.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Operation Conditions&lt;br /&gt;
 | color = lightblue&lt;br /&gt;
 | body =&lt;br /&gt;
[[File:Village.jpg|250px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS is designed to operate under the real-world conditions faced by local initiatives. These include, among others:&lt;br /&gt;
&lt;br /&gt;
* unreliable power supply&lt;br /&gt;
* intermittent connectivity&lt;br /&gt;
* diverse or aging equipment&lt;br /&gt;
* limited availability of trained personnel&lt;br /&gt;
* the need for safety and autonomous operation&lt;br /&gt;
&lt;br /&gt;
AOWIS enables systems that continue to function safely and reliably, even under degraded or adverse conditions.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Facing the Challenges&lt;br /&gt;
 | color = lightblue&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS addresses these operational challenges through the following principles:&lt;br /&gt;
&lt;br /&gt;
* human-in-the-loop control&lt;br /&gt;
* offline-first operation&lt;br /&gt;
* safe fallback behavior&lt;br /&gt;
* modular and extensible logic&lt;br /&gt;
* shared infrastructure models&lt;br /&gt;
* training programs for local operators&lt;br /&gt;
* transparent governance&lt;br /&gt;
&lt;br /&gt;
The goal is to make essential systems &#039;&#039;&#039;robust, maintainable, and locally operable&#039;&#039;&#039;.&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
| title = Software &amp;amp; Downloads&lt;br /&gt;
| color = green&lt;br /&gt;
| body =&lt;br /&gt;
[[File:GUI ky4 3d.png|400px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS is accompanied by an open-source software platform for &#039;&#039;&#039;modelling, simulating, visualizing, monitoring, and operating water infrastructure&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The current software includes a network editor and monitoring interface, hydraulic and water-quality simulation using [[External:EPANET:Main Page|EPANET]], geographic maps and terrain visualization, and support for local and standalone operation. Development is progressing toward a complete AOWIS-compatible SCADA platform.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://download.aowis.org Download the AOWIS Controller (development snapshot)]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* [https://github.com/aowis-org Source code on GitHub]&lt;br /&gt;
* [[#Roadmap|Software development roadmap]]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Start Here&lt;br /&gt;
 | color = yellow&lt;br /&gt;
 | body =&lt;br /&gt;
If you are new to AOWIS, begin with:&lt;br /&gt;
&lt;br /&gt;
* [[Concepts:Design_Philosophy|Design Philosophy]]  &lt;br /&gt;
* [[Standard:Definitions|Definitions]]  &lt;br /&gt;
* [[Standard:Normative_Requirements|Normative Requirements]]  &lt;br /&gt;
* [[Modules:Module_Template|Module Template]]  &lt;br /&gt;
* [[AOWIS:Contributor_Guide_External|Contributor Guide - External]]&lt;br /&gt;
* [[AOWIS:Contributor_Guide_Internal|Contributor Guide - Internal]]&lt;br /&gt;
* [[AOWIS:Writing_Style_Guide|Writing Style Guide]]&lt;br /&gt;
* [[AOWIS:AI_Usage_Guide|AI Usage Guide]]&lt;br /&gt;
* [[AOWIS:Research_Form_Guide|Research Form Guide]]&lt;br /&gt;
* [[AOWIS:Naming_Convention_Specification|Naming Convention Specification]]&lt;br /&gt;
* [[AOWIS:Change_Log__Versioning|Change Log &amp;amp; Versioning]]&lt;br /&gt;
* [[AOWIS:Wiki|This Wiki]]&lt;br /&gt;
&lt;br /&gt;
These pages explain how to read, use, and contribute to the standard.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = List of Requirement Pages&lt;br /&gt;
 | color = brown&lt;br /&gt;
 | body = &lt;br /&gt;
This index lists AOWIS pages that define normative requirements (MUST/SHOULD/MAY statements) and conformance rules.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Dev Rules&#039;&#039;&#039; — specs for writing and maintaining AOWIS&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;REQ-AI:&#039;&#039;&#039; [[AOWIS:AI_Usage_Guide|AI Usage Guide]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Technical Standard&#039;&#039;&#039; — system behavior and data models&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;REQ-MEAS, REQ-MEAS-UI:&#039;&#039;&#039; [[Measurement:Units|Unit System Requirements]]&lt;br /&gt;
* &#039;&#039;&#039;REQ-MEAS-UNI:&#039;&#039;&#039; [[Measurement:Canonical_Units|Canonical Units]]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = AOWIS Documentation Structure&lt;br /&gt;
 | color = purple&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS documentation is organized into dedicated namespaces with clearly separated purposes.&lt;br /&gt;
&lt;br /&gt;
The [[Standard:Main_Page|Standard]] namespace contains the normative requirements that define AOWIS compliance. The other namespaces provide the motivation, concepts, engineering knowledge, architectures, operational models, implementation guidance, reference designs, training material, and supporting information needed to understand, implement, and operate AOWIS systems.&lt;br /&gt;
&lt;br /&gt;
* [[Motivation:Main_Page|Motivation]] – Causal justification of design requirements based on real-world failures, constraints, and operational realities.&lt;br /&gt;
* [[Standard:Main_Page|Standard]] – The normative core of AOWIS. Defines requirements and definitions specifying what AOWIS-compliant systems MUST, SHOULD, or MAY do.&lt;br /&gt;
* [[Concepts:Main_Page|Concepts]] – Core ideas, philosophy, rationale, and contextual understanding that explain AOWIS without prescribing a specific implementation.&lt;br /&gt;
* [[Architecture:Main_Page|Architecture]] – High-level system structure, including controllers, layers, communication, data flows, and their interactions.&lt;br /&gt;
* [[Infrastructure:Main_Page|Infrastructure]] – Physical technologies, systems, and components used in AOWIS deployments. Infrastructure pages describe classes of physical systems rather than specific implementation blueprints.&lt;br /&gt;
* [[Measurement:Main_Page|Measurement]] – Definition and handling of sensor data, manual measurements, calibration, uncertainty, and derived physical values.&lt;br /&gt;
* [[Data:Main_Page|Data]] – Data models, schemas, logging structures, synchronization formats, and data lifecycle rules.&lt;br /&gt;
* [[Operations:Main_Page|Operations]] – Runtime behavior, control logic, state transitions, fallback behavior, and decision-making during system operation.&lt;br /&gt;
* [[Modules:Main_Page|Modules]] – Reusable functional extensions that provide domain-specific capabilities within AOWIS.&lt;br /&gt;
* [[Reference:Main_Page|Reference]] – Non-normative concrete implementations, engineering blueprints, example deployments, and validated design patterns showing specific ways AOWIS systems may be built.&lt;br /&gt;
* [[Databases:Main_Page|Databases]] – Federated knowledge bases and structured supporting information used by AOWIS implementations.&lt;br /&gt;
* [[Governance:Main_Page|Governance]] – Certification, compliance, auditing, trust, licensing, versioning, and organizational governance.&lt;br /&gt;
* [[Training:Main_Page|Training]] – Operator education, technical training, field guidance, documentation literacy, and capacity building.&lt;br /&gt;
* [[External:Main_Page|External]] – External projects, standards, technologies, and systems that relate to or influence AOWIS.&lt;br /&gt;
&lt;br /&gt;
* [[Regions:Main_Page|Regions]] – Geographic, environmental, hydrological, climatic, socioeconomic, and infrastructure context for areas in which AOWIS is researched, planned, or deployed.&lt;br /&gt;
&lt;br /&gt;
For a full overview, see the [[AOWIS:Table_of_Contents|Table of Contents]].&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Roadmap&lt;br /&gt;
 | color = grey&lt;br /&gt;
 | body =&lt;br /&gt;
[[File:Boring.jpg|250px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS has progressed beyond its initial conceptual phase. A substantial software foundation for modelling, simulating, visualizing, and eventually operating water infrastructure is under active development.&lt;br /&gt;
&lt;br /&gt;
The current software stack already includes:&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Shared infrastructure model&#039;&#039;&#039;&lt;br /&gt;
: A common, solver-independent representation of water infrastructure used throughout the AOWIS software stack.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-MODEL GitHub AOWIS-SERVER-MODEL]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Hydraulic and water-quality simulation&#039;&#039;&#039;&lt;br /&gt;
: EPANET integration for hydraulic and water-quality simulation, network import/export, controls, rules, diagnostics, and simulation results. Integration of &#039;&#039;&#039;EPANET-MSX&#039;&#039;&#039; is also being developed.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-EPANET GitHub AOWIS-SERVER-EPANET]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Network editor and monitoring interface&#039;&#039;&#039;&lt;br /&gt;
: A graphical application for creating, inspecting, simulating, and visualizing water networks, including geographic maps and terrain-aware 3D visualization.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-GUI GitHub AOWIS-SERVER-GUI]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Geographic and terrain infrastructure&#039;&#039;&#039;&lt;br /&gt;
: Mapping, elevation data, basemaps, terrain visualization, geographic placement, and local caching.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-MAP GitHub AOWIS-SERVER-MAP]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Local and standalone operation&#039;&#039;&#039;&lt;br /&gt;
: Support for deployments that do not depend on continuous Internet or cloud connectivity.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-Standalone GitHub AOWIS-SERVER-Standalone]&lt;br /&gt;
&lt;br /&gt;
The software remains under active development and should not yet be considered a complete production SCADA system.&lt;br /&gt;
&lt;br /&gt;
The next major stage is to connect the existing modelling and simulation environment to &#039;&#039;&#039;real infrastructure in continuous operation&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
AOWIS is intended to develop into a complete open-source &#039;&#039;&#039;SCADA, infrastructure modelling, simulation, and operational management platform&#039;&#039;&#039; in which planning, live monitoring, control, historical data, maintenance, and simulation operate on the same shared infrastructure model.&lt;br /&gt;
&lt;br /&gt;
This includes telemetry, sensors and actuators, alarms and historian functions, local and remote control, automation with safe fallback behaviour, and model-assisted operation using measured and simulated system behaviour.&lt;br /&gt;
&lt;br /&gt;
EPANET currently provides the primary hydraulic and water-quality simulation engine, but AOWIS is not designed solely as an EPANET frontend. EPANET is one solver integrated into a broader, solver-independent architecture.&lt;br /&gt;
&lt;br /&gt;
The long-term objective is to connect the complete infrastructure lifecycle:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;survey and planning → engineering and simulation → construction → commissioning → monitoring → control → maintenance → analysis → expansion&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[[AOWIS:Roadmap|Read the full roadmap →]]&#039;&#039;&#039;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
| title = Community &amp;amp; Participation&lt;br /&gt;
| color = blue&lt;br /&gt;
| body =&lt;br /&gt;
&lt;br /&gt;
AOWIS is an open project, and participation is welcome from anyone interested in its goals — including engineers, developers, NGOs, operators, researchers, technicians, students, and people with practical experience in water and agricultural infrastructure.&lt;br /&gt;
&lt;br /&gt;
For &#039;&#039;&#039;discussion, planning, questions, documentation, infrastructure, field projects, standards, research, and other forms of participation&#039;&#039;&#039;, AOWIS uses &#039;&#039;&#039;Matrix&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The AOWIS Matrix server has several &#039;&#039;&#039;public spaces and rooms&#039;&#039;&#039; for different topics. Join those relevant to your interests. For general questions or help finding the right place, start here:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://matrix.to/#/#support:aowis.org AOWIS Support — #support:aowis.org]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
You do &#039;&#039;&#039;not&#039;&#039;&#039; need an AOWIS account to participate. Any Matrix account can join public AOWIS spaces and rooms.&lt;br /&gt;
&lt;br /&gt;
If you are new to Matrix:&lt;br /&gt;
&lt;br /&gt;
* [https://matrix.org/try-matrix/ Learn about Matrix and create an account]&lt;br /&gt;
* [https://element.io/ Element] — Matrix client for web, desktop, and mobile&lt;br /&gt;
* [https://fluffychat.im/ FluffyChat] — simple Matrix client for several platforms&lt;br /&gt;
&lt;br /&gt;
The same Matrix account can be used with different clients.&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;AOWIS Matrix Accounts&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Participants may also request an account on the AOWIS Matrix homeserver, giving them an ID such as &#039;&#039;&#039;@name:aowis.org&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
To reduce automated registrations and abuse, accounts are created on request. Please send a short introduction telling us who you are, what interests you about AOWIS, and where you would like to participate: [[File:Mtx.png|120px|frameless|alt=Email address for requesting an AOWIS Matrix account]]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Software Development&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Software development remains on &#039;&#039;&#039;GitHub&#039;&#039;&#039;. Bug reports, pull requests, source-code contributions, and repository-specific development discussions should use the appropriate repository.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://github.com/aowis-org AOWIS on GitHub]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Matrix is for the broader AOWIS community and participation that does not naturally belong in a GitHub repository.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Governance &amp;amp; Legitimacy&lt;br /&gt;
 | color = turquoise&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS includes a transparent governance model to ensure:&lt;br /&gt;
&lt;br /&gt;
* open participation  &lt;br /&gt;
* clear certification processes  &lt;br /&gt;
* stable versioning  &lt;br /&gt;
* long‑term protection of the standard  &lt;br /&gt;
&lt;br /&gt;
See: [[Governance:Main_Page|Governance]].&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Navigation&lt;br /&gt;
 | color = grey&lt;br /&gt;
 | body =&lt;br /&gt;
* [[AOWIS:Table_of_Contents|Table of Contents]]  &lt;br /&gt;
* [[Reference:Glossary|Glossary]]  &lt;br /&gt;
* [[Reference:FAQ|FAQ]]  &lt;br /&gt;
* [[Reference:Change_Log|Change Log]]  &lt;br /&gt;
&lt;br /&gt;
* [https://github.com/aowis-org GitHub]&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Partners&lt;br /&gt;
 | color = indigo&lt;br /&gt;
 | body = &lt;br /&gt;
[[File:Afriticgroup.webp|250px|frameless|center|link=https://afriticgroup.com/]]&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Samuel</name></author>
	</entry>
	<entry>
		<id>https://aowis.org/index.php?title=Main_Page&amp;diff=753</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://aowis.org/index.php?title=Main_Page&amp;diff=753"/>
		<updated>2026-09-23T15:04:38Z</updated>

		<summary type="html">&lt;p&gt;Samuel: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
&lt;br /&gt;
{{MainPageBanner}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Motivation&lt;br /&gt;
 | color = teal&lt;br /&gt;
 | body = &lt;br /&gt;
&lt;br /&gt;
[[File:Countryside.jpg|class=fullwidth|center]]&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
This is where AOWIS aims to contribute: by providing an open system for designing, deploying, operating, and maintaining water and agricultural infrastructure in such environments. AOWIS combines a common technical standard with open-source software, engineering guidance, shared knowledge, and operational practices. It supports both the planning phase—helping initiatives assess regional conditions such as topography and design appropriate infrastructure—and the operational phase, including system monitoring, control, maintenance, and long-term management.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Why an Open Standard is Needed&lt;br /&gt;
 | color = turquoise&lt;br /&gt;
 | body = &lt;br /&gt;
&lt;br /&gt;
[[File:Cooperation.jpg|400px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
AOWIS defines such a foundation for water and agricultural infrastructure under real-world operational constraints.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Operation Conditions&lt;br /&gt;
 | color = lightblue&lt;br /&gt;
 | body =&lt;br /&gt;
[[File:Village.jpg|250px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS is designed to operate under the real-world conditions faced by local initiatives. These include, among others:&lt;br /&gt;
&lt;br /&gt;
* unreliable power supply&lt;br /&gt;
* intermittent connectivity&lt;br /&gt;
* diverse or aging equipment&lt;br /&gt;
* limited availability of trained personnel&lt;br /&gt;
* the need for safety and autonomous operation&lt;br /&gt;
&lt;br /&gt;
AOWIS enables systems that continue to function safely and reliably, even under degraded or adverse conditions.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Facing the Challenges&lt;br /&gt;
 | color = lightblue&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS addresses these operational challenges through the following principles:&lt;br /&gt;
&lt;br /&gt;
* human-in-the-loop control&lt;br /&gt;
* offline-first operation&lt;br /&gt;
* safe fallback behavior&lt;br /&gt;
* modular and extensible logic&lt;br /&gt;
* shared infrastructure models&lt;br /&gt;
* training programs for local operators&lt;br /&gt;
* transparent governance&lt;br /&gt;
&lt;br /&gt;
The goal is to make essential systems &#039;&#039;&#039;robust, maintainable, and locally operable&#039;&#039;&#039;.&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
| title = Software &amp;amp; Downloads&lt;br /&gt;
| color = green&lt;br /&gt;
| body =&lt;br /&gt;
[[File:GUI ky4 3d.png|400px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS is accompanied by an open-source software platform for &#039;&#039;&#039;modelling, simulating, visualizing, monitoring, and operating water infrastructure&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The current software includes a network editor and monitoring interface, hydraulic and water-quality simulation using [[External:EPANET:Main Page|EPANET]], geographic maps and terrain visualization, and support for local and standalone operation. Development is progressing toward a complete AOWIS-compatible SCADA platform.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://download.aowis.org Download the AOWIS Controller (development snapshot)]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* [https://github.com/aowis-org Source code on GitHub]&lt;br /&gt;
* [[#Roadmap|Software development roadmap]]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Start Here&lt;br /&gt;
 | color = yellow&lt;br /&gt;
 | body =&lt;br /&gt;
If you are new to AOWIS, begin with:&lt;br /&gt;
&lt;br /&gt;
* [[Concepts:Design_Philosophy|Design Philosophy]]  &lt;br /&gt;
* [[Standard:Definitions|Definitions]]  &lt;br /&gt;
* [[Standard:Normative_Requirements|Normative Requirements]]  &lt;br /&gt;
* [[Modules:Module_Template|Module Template]]  &lt;br /&gt;
* [[AOWIS:Contributor_Guide_External|Contributor Guide - External]]&lt;br /&gt;
* [[AOWIS:Contributor_Guide_Internal|Contributor Guide - Internal]]&lt;br /&gt;
* [[AOWIS:Writing_Style_Guide|Writing Style Guide]]&lt;br /&gt;
* [[AOWIS:AI_Usage_Guide|AI Usage Guide]]&lt;br /&gt;
* [[AOWIS:Research_Form_Guide|Research Form Guide]]&lt;br /&gt;
* [[AOWIS:Naming_Convention_Specification|Naming Convention Specification]]&lt;br /&gt;
* [[AOWIS:Change_Log__Versioning|Change Log &amp;amp; Versioning]]&lt;br /&gt;
* [[AOWIS:Wiki|This Wiki]]&lt;br /&gt;
&lt;br /&gt;
These pages explain how to read, use, and contribute to the standard.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = List of Requirement Pages&lt;br /&gt;
 | color = brown&lt;br /&gt;
 | body = &lt;br /&gt;
This index lists AOWIS pages that define normative requirements (MUST/SHOULD/MAY statements) and conformance rules.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Dev Rules&#039;&#039;&#039; — specs for writing and maintaining AOWIS&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;REQ-AI:&#039;&#039;&#039; [[AOWIS:AI_Usage_Guide|AI Usage Guide]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Technical Standard&#039;&#039;&#039; — system behavior and data models&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;REQ-MEAS, REQ-MEAS-UI:&#039;&#039;&#039; [[Measurement:Units|Unit System Requirements]]&lt;br /&gt;
* &#039;&#039;&#039;REQ-MEAS-UNI:&#039;&#039;&#039; [[Measurement:Canonical_Units|Canonical Units]]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = AOWIS Documentation Structure&lt;br /&gt;
 | color = purple&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS documentation is organized into dedicated namespaces with clearly separated purposes.&lt;br /&gt;
&lt;br /&gt;
The [[Standard:Main_Page|Standard]] namespace contains the normative requirements that define AOWIS compliance. The other namespaces provide the motivation, concepts, engineering knowledge, architectures, operational models, implementation guidance, reference designs, training material, and supporting information needed to understand, implement, and operate AOWIS systems.&lt;br /&gt;
&lt;br /&gt;
* [[Motivation:Main_Page|Motivation]] – Causal justification of design requirements based on real-world failures, constraints, and operational realities.&lt;br /&gt;
* [[Standard:Main_Page|Standard]] – The normative core of AOWIS. Defines requirements and definitions specifying what AOWIS-compliant systems MUST, SHOULD, or MAY do.&lt;br /&gt;
* [[Concepts:Main_Page|Concepts]] – Core ideas, philosophy, rationale, and contextual understanding that explain AOWIS without prescribing a specific implementation.&lt;br /&gt;
* [[Architecture:Main_Page|Architecture]] – High-level system structure, including controllers, layers, communication, data flows, and their interactions.&lt;br /&gt;
* [[Infrastructure:Main_Page|Infrastructure]] – Physical technologies, systems, and components used in AOWIS deployments. Infrastructure pages describe classes of physical systems rather than specific implementation blueprints.&lt;br /&gt;
* [[Measurement:Main_Page|Measurement]] – Definition and handling of sensor data, manual measurements, calibration, uncertainty, and derived physical values.&lt;br /&gt;
* [[Data:Main_Page|Data]] – Data models, schemas, logging structures, synchronization formats, and data lifecycle rules.&lt;br /&gt;
* [[Operations:Main_Page|Operations]] – Runtime behavior, control logic, state transitions, fallback behavior, and decision-making during system operation.&lt;br /&gt;
* [[Modules:Main_Page|Modules]] – Reusable functional extensions that provide domain-specific capabilities within AOWIS.&lt;br /&gt;
* [[Reference:Main_Page|Reference]] – Non-normative concrete implementations, engineering blueprints, example deployments, and validated design patterns showing specific ways AOWIS systems may be built.&lt;br /&gt;
* [[Databases:Main_Page|Databases]] – Federated knowledge bases and structured supporting information used by AOWIS implementations.&lt;br /&gt;
* [[Governance:Main_Page|Governance]] – Certification, compliance, auditing, trust, licensing, versioning, and organizational governance.&lt;br /&gt;
* [[Training:Main_Page|Training]] – Operator education, technical training, field guidance, documentation literacy, and capacity building.&lt;br /&gt;
* [[External:Main_Page|External]] – External projects, standards, technologies, and systems that relate to or influence AOWIS.&lt;br /&gt;
&lt;br /&gt;
* [[Regions:Main_Page|Regions]] – Geographic, environmental, hydrological, climatic, socioeconomic, and infrastructure context for areas in which AOWIS is researched, planned, or deployed.&lt;br /&gt;
&lt;br /&gt;
For a full overview, see the [[AOWIS:Table_of_Contents|Table of Contents]].&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Roadmap&lt;br /&gt;
 | color = grey&lt;br /&gt;
 | body =&lt;br /&gt;
[[File:Boring.jpg|250px|frameless|right]]&lt;br /&gt;
&lt;br /&gt;
AOWIS has progressed beyond its initial conceptual phase. A substantial software foundation for modelling, simulating, visualizing, and eventually operating water infrastructure is under active development.&lt;br /&gt;
&lt;br /&gt;
The current software stack already includes:&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Shared infrastructure model&#039;&#039;&#039;&lt;br /&gt;
: A common, solver-independent representation of water infrastructure used throughout the AOWIS software stack.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-MODEL GitHub AOWIS-SERVER-MODEL]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Hydraulic and water-quality simulation&#039;&#039;&#039;&lt;br /&gt;
: EPANET integration for hydraulic and water-quality simulation, network import/export, controls, rules, diagnostics, and simulation results. Integration of &#039;&#039;&#039;EPANET-MSX&#039;&#039;&#039; is also being developed.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-EPANET GitHub AOWIS-SERVER-EPANET]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Network editor and monitoring interface&#039;&#039;&#039;&lt;br /&gt;
: A graphical application for creating, inspecting, simulating, and visualizing water networks, including geographic maps and terrain-aware 3D visualization.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-GUI GitHub AOWIS-SERVER-GUI]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Geographic and terrain infrastructure&#039;&#039;&#039;&lt;br /&gt;
: Mapping, elevation data, basemaps, terrain visualization, geographic placement, and local caching.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-MAP GitHub AOWIS-SERVER-MAP]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Local and standalone operation&#039;&#039;&#039;&lt;br /&gt;
: Support for deployments that do not depend on continuous Internet or cloud connectivity.&lt;br /&gt;
: [https://github.com/aowis-org/AOWIS-SERVER-Standalone GitHub AOWIS-SERVER-Standalone]&lt;br /&gt;
&lt;br /&gt;
The software remains under active development and should not yet be considered a complete production SCADA system.&lt;br /&gt;
&lt;br /&gt;
The next major stage is to connect the existing modelling and simulation environment to &#039;&#039;&#039;real infrastructure in continuous operation&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
AOWIS is intended to develop into a complete open-source &#039;&#039;&#039;SCADA, infrastructure modelling, simulation, and operational management platform&#039;&#039;&#039; in which planning, live monitoring, control, historical data, maintenance, and simulation operate on the same shared infrastructure model.&lt;br /&gt;
&lt;br /&gt;
This includes telemetry, sensors and actuators, alarms and historian functions, local and remote control, automation with safe fallback behaviour, and model-assisted operation using measured and simulated system behaviour.&lt;br /&gt;
&lt;br /&gt;
EPANET currently provides the primary hydraulic and water-quality simulation engine, but AOWIS is not designed solely as an EPANET frontend. EPANET is one solver integrated into a broader, solver-independent architecture.&lt;br /&gt;
&lt;br /&gt;
The long-term objective is to connect the complete infrastructure lifecycle:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;survey and planning → engineering and simulation → construction → commissioning → monitoring → control → maintenance → analysis → expansion&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[[AOWIS:Roadmap|Read the full roadmap →]]&#039;&#039;&#039;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
| title = Community &amp;amp; Participation&lt;br /&gt;
| color = blue&lt;br /&gt;
| body =&lt;br /&gt;
&lt;br /&gt;
AOWIS is an open project, and participation is welcome from anyone interested in its goals — including engineers, developers, NGOs, operators, researchers, technicians, students, and people with practical experience in water and agricultural infrastructure.&lt;br /&gt;
&lt;br /&gt;
For &#039;&#039;&#039;discussion, planning, questions, documentation, infrastructure, field projects, standards, research, and other forms of participation&#039;&#039;&#039;, AOWIS uses &#039;&#039;&#039;Matrix&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The AOWIS Matrix server has several &#039;&#039;&#039;public spaces and rooms&#039;&#039;&#039; for different topics. Join those relevant to your interests. For general questions or help finding the right place, start here:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://matrix.to/#/#support:aowis.org AOWIS Support — #support:aowis.org]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
You do &#039;&#039;&#039;not&#039;&#039;&#039; need an AOWIS account to participate. Any Matrix account can join public AOWIS spaces and rooms.&lt;br /&gt;
&lt;br /&gt;
If you are new to Matrix:&lt;br /&gt;
&lt;br /&gt;
* [https://matrix.org/try-matrix/ Learn about Matrix and create an account]&lt;br /&gt;
* [https://element.io/ Element] — Matrix client for web, desktop, and mobile&lt;br /&gt;
* [https://fluffychat.im/ FluffyChat] — simple Matrix client for several platforms&lt;br /&gt;
&lt;br /&gt;
The same Matrix account can be used with different clients.&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;AOWIS Matrix Accounts&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Participants may also request an account on the AOWIS Matrix homeserver, giving them an ID such as &#039;&#039;&#039;@name:aowis.org&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
To reduce automated registrations and abuse, accounts are created on request. Please send a short introduction telling us who you are, what interests you about AOWIS, and where you would like to participate: [[File:Mtx.png|120px|frameless|alt=Email address for requesting an AOWIS Matrix account]]&lt;br /&gt;
&lt;br /&gt;
; &#039;&#039;&#039;Software Development&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Software development remains on &#039;&#039;&#039;GitHub&#039;&#039;&#039;. Bug reports, pull requests, source-code contributions, and repository-specific development discussions should use the appropriate repository.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[https://github.com/aowis-org AOWIS on GitHub]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Matrix is for the broader AOWIS community and participation that does not naturally belong in a GitHub repository.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hbox-row&amp;quot;&amp;gt;&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Governance &amp;amp; Legitimacy&lt;br /&gt;
 | color = turquoise&lt;br /&gt;
 | body = &lt;br /&gt;
AOWIS includes a transparent governance model to ensure:&lt;br /&gt;
&lt;br /&gt;
* open participation  &lt;br /&gt;
* clear certification processes  &lt;br /&gt;
* stable versioning  &lt;br /&gt;
* long‑term protection of the standard  &lt;br /&gt;
&lt;br /&gt;
See: [[Governance:Main_Page|Governance]].&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Navigation&lt;br /&gt;
 | color = grey&lt;br /&gt;
 | body =&lt;br /&gt;
* [[AOWIS:Table_of_Contents|Table of Contents]]  &lt;br /&gt;
* [[Reference:Glossary|Glossary]]  &lt;br /&gt;
* [[Reference:FAQ|FAQ]]  &lt;br /&gt;
* [[Reference:Change_Log|Change Log]]  &lt;br /&gt;
&lt;br /&gt;
* [https://github.com/aowis-org GitHub]&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Header box&lt;br /&gt;
 | title = Partners&lt;br /&gt;
 | color = indigo&lt;br /&gt;
 | body = &lt;br /&gt;
[[File:Afriticgroup.webp|250px|frameless|center|link=https://afriticgroup.com/]]&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Samuel</name></author>
	</entry>
	<entry>
		<id>https://aowis.org/index.php?title=Template:MainPageBanner&amp;diff=752</id>
		<title>Template:MainPageBanner</title>
		<link rel="alternate" type="text/html" href="https://aowis.org/index.php?title=Template:MainPageBanner&amp;diff=752"/>
		<updated>2026-09-23T14:28:24Z</updated>

		<summary type="html">&lt;p&gt;Samuel: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;div class=&amp;quot;mainpage-banner&amp;quot; style=&amp;quot;&lt;br /&gt;
    background: var(--background-color-neutral-subtle, #f8f9fa);&lt;br /&gt;
    border: 1px solid var(--border-color-base, #a2a9b1);&lt;br /&gt;
    padding: 1.5em;&lt;br /&gt;
    margin-bottom: 1.5em;&lt;br /&gt;
    border-radius: 4px;&lt;br /&gt;
    color: var(--color-base, #202122);&lt;br /&gt;
&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1 style=&amp;quot;&lt;br /&gt;
    margin: 0 0 0.8em 0;&lt;br /&gt;
    font-size: 2em;&lt;br /&gt;
    font-weight: normal;&lt;br /&gt;
    color: var(--color-base, #202122);&lt;br /&gt;
&amp;quot;&amp;gt;&lt;br /&gt;
    &#039;&#039;&#039;AOWIS – Afritic Open Water Infrastructure System&#039;&#039;&#039;&lt;br /&gt;
&amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[File:Logo.png|frameless|right|150px]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;flex: 1;&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;p style=&amp;quot;margin: 0 0 0.6em 0; font-size: 1.15em;&amp;quot;&amp;gt;&lt;br /&gt;
        &#039;&#039;&#039;AOWIS&#039;&#039;&#039; (&#039;&#039;&#039;A&#039;&#039;&#039;fritic &#039;&#039;&#039;O&#039;&#039;&#039;pen &#039;&#039;&#039;W&#039;&#039;&#039;ater &#039;&#039;&#039;I&#039;&#039;&#039;nfrastructure &#039;&#039;&#039;S&#039;&#039;&#039;ystem) is an open system for designing, modelling, operating, and maintaining safe and reliable &#039;&#039;&#039;water and irrigation infrastructure&#039;&#039;&#039;.&lt;br /&gt;
    &amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;p style=&amp;quot;margin: 0 0 0.6em 0; font-size: 1.15em;&amp;quot;&amp;gt;&lt;br /&gt;
        It provides a common foundation for infrastructure modelling, monitoring, control, automation, data exchange, engineering practice, and day-to-day operation. AOWIS combines an open technical standard with open-source software, reference implementations, engineering knowledge, operational guidance, and training.&lt;br /&gt;
    &amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;p style=&amp;quot;margin: 0; font-size: 1.15em;&amp;quot;&amp;gt;&lt;br /&gt;
        The &#039;&#039;&#039;[[Standard:Main_Page|AOWIS Standard]]&#039;&#039;&#039; forms the normative core of the system. AOWIS is intended for use by communities, utilities, organizations, and other operators of water infrastructure, while remaining practical under difficult conditions such as intermittent connectivity, unreliable power, limited technical resources, and the need for local autonomous operation.&lt;br /&gt;
    &amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;div class=&amp;quot;plainlinks&amp;quot; style=&amp;quot;&lt;br /&gt;
    margin-top: 0.8em;&lt;br /&gt;
    font-size: 0.9em;&lt;br /&gt;
    white-space: nowrap;&lt;br /&gt;
&amp;quot;&amp;gt;&#039;&#039;&#039;[[#Software &amp;amp; Downloads|Software &amp;amp; Downloads]]&#039;&#039;&#039; &amp;amp;nbsp;·&amp;amp;nbsp; &#039;&#039;&#039;[[#Community &amp;amp; Participation|Community &amp;amp; Participation]]&#039;&#039;&#039; &amp;amp;nbsp;·&amp;amp;nbsp; &#039;&#039;&#039;[[Standard:Main_Page|Access the Standard]]&#039;&#039;&#039;&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;/div&gt;</summary>
		<author><name>Samuel</name></author>
	</entry>
	<entry>
		<id>https://aowis.org/index.php?title=Regions:Chad/Gu%C3%A9ra/Bitkine/Groundwater_prospecting&amp;diff=751</id>
		<title>Regions:Chad/Guéra/Bitkine/Groundwater prospecting</title>
		<link rel="alternate" type="text/html" href="https://aowis.org/index.php?title=Regions:Chad/Gu%C3%A9ra/Bitkine/Groundwater_prospecting&amp;diff=751"/>
		<updated>2026-09-20T22:57:12Z</updated>

		<summary type="html">&lt;p&gt;Samuel: Created page with &amp;quot;{{DISPLAYTITLE:Groundwater prospecting around Bitkine}} {{AI-Generated | tool = ChatGPT | date = 2026-09-21 | scope = full page }}  This page documents &amp;#039;&amp;#039;&amp;#039;groundwater prospecting, candidate drilling areas and hydrogeological hypotheses&amp;#039;&amp;#039;&amp;#039; around Bitkine.  Existing wells and boreholes are documented separately under Water points.  == Prospecting approach ==  Groundwater around Bitkine occurs in h...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{DISPLAYTITLE:Groundwater prospecting around Bitkine}}&lt;br /&gt;
{{AI-Generated | tool = ChatGPT | date = 2026-09-21 | scope = full page }}&lt;br /&gt;
&lt;br /&gt;
This page documents &#039;&#039;&#039;groundwater prospecting, candidate drilling areas and hydrogeological hypotheses&#039;&#039;&#039; around [[Regions:Chad/Guéra/Bitkine|Bitkine]].&lt;br /&gt;
&lt;br /&gt;
Existing wells and boreholes are documented separately under [[Regions:Chad/Guéra/Bitkine/Water_points|Water points]].&lt;br /&gt;
&lt;br /&gt;
== Prospecting approach ==&lt;br /&gt;
&lt;br /&gt;
Groundwater around Bitkine occurs in heterogeneous weathered and fractured crystalline basement.&lt;br /&gt;
&lt;br /&gt;
Potential drilling sites should therefore be evaluated using a combination of:&lt;br /&gt;
&lt;br /&gt;
* geology;&lt;br /&gt;
* topography;&lt;br /&gt;
* seasonal drainage;&lt;br /&gt;
* weathering;&lt;br /&gt;
* electrical-resistivity tomography (ERT);&lt;br /&gt;
* nearby drilling results;&lt;br /&gt;
* nearby groundwater quality;&lt;br /&gt;
* sanitary risks.&lt;br /&gt;
&lt;br /&gt;
Proximity to a visible drainage feature alone is not sufficient evidence for a productive aquifer.&lt;br /&gt;
&lt;br /&gt;
Likewise, a deep conductive anomaly on an ERT profile should not automatically be interpreted as a productive fracture without geological and geomorphological context.&lt;br /&gt;
&lt;br /&gt;
== Southern Bitkine sector ==&lt;br /&gt;
&lt;br /&gt;
The Bitkine-specific hydrogeophysical study by Pierre Palomar found that favourable A and A* aquifer configurations occur more frequently south of Bitkine toward the Mont Guéra massif.&amp;lt;ref name=&amp;quot;palomar&amp;quot;&amp;gt;[https://nextcloud.aowis.org/s/j7Gy7bMrFr5Gsew Pierre Palomar, &#039;&#039;Conceptualisation hydrogéologique et recommandations pour les prospections géophysiques et l&#039;implantation des forages — Province du Guéra, Tchad&#039;&#039;, SEVES, 2024.]&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This sector is therefore considered a preferred area for further groundwater investigation.&lt;br /&gt;
&lt;br /&gt;
The interpretation is consistent with the local landscape. Seasonal runoff from the Mont Guéra massif becomes concentrated along valleys and wadis before entering flatter piedmont terrain north of the mountains.&lt;br /&gt;
&lt;br /&gt;
Where these drainage systems overlie permeable weathered material and fractured basement, they may form important groundwater-recharge zones.&lt;br /&gt;
&lt;br /&gt;
== Drainage corridors and sanitary protection ==&lt;br /&gt;
&lt;br /&gt;
The middle of an active wadi may provide strong recharge but can also present significant disadvantages for a drinking-water borehole.&lt;br /&gt;
&lt;br /&gt;
Potential risks include:&lt;br /&gt;
&lt;br /&gt;
* direct infiltration of microbiological contamination;&lt;br /&gt;
* livestock contamination;&lt;br /&gt;
* runoff from settlements;&lt;br /&gt;
* nitrate contamination;&lt;br /&gt;
* flood damage;&lt;br /&gt;
* erosion;&lt;br /&gt;
* sediment accumulation.&lt;br /&gt;
&lt;br /&gt;
A site slightly outside the active drainage channel may therefore be preferable where the same underlying aquifer can be intercepted.&lt;br /&gt;
&lt;br /&gt;
The objective is not simply to maximise recharge, but to obtain a productive aquifer with adequate sanitary protection.&lt;br /&gt;
&lt;br /&gt;
== Mont Doli candidate area ==&lt;br /&gt;
&lt;br /&gt;
AOWIS has identified a preliminary groundwater investigation area east of &#039;&#039;&#039;Mont Doli&#039;&#039;&#039; at approximately:&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;11.948855° N, 18.187213° E&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
This is a &#039;&#039;&#039;prospecting hypothesis only&#039;&#039;&#039;. No existing successful borehole at this point is currently known to AOWIS.&lt;br /&gt;
&lt;br /&gt;
The location was selected from topography and seasonal satellite imagery.&lt;br /&gt;
&lt;br /&gt;
Dry-season imagery shows the mountain-front terrain and drainage depressions.&lt;br /&gt;
&lt;br /&gt;
Rainy-season imagery shows a much clearer network of active drainage routes carrying runoff northward from the massif.&lt;br /&gt;
&lt;br /&gt;
The candidate lies near, but not directly within, one of the principal visible drainage corridors.&lt;br /&gt;
&lt;br /&gt;
This may be favourable because the location could potentially intercept groundwater recharged through the nearby drainage system while avoiding some of the sanitary and flood risks associated with drilling directly in the active channel.&lt;br /&gt;
&lt;br /&gt;
The broader area has several characteristics that justify further investigation:&lt;br /&gt;
&lt;br /&gt;
* proximity to the Mont Guéra catchment;&lt;br /&gt;
* concentrated seasonal runoff;&lt;br /&gt;
* mountain-front / piedmont terrain;&lt;br /&gt;
* visible drainage convergence;&lt;br /&gt;
* potential weathered and fractured basement;&lt;br /&gt;
* location in the southern Bitkine sector identified as generally favourable by the existing hydrogeophysical study.&lt;br /&gt;
&lt;br /&gt;
These observations do &#039;&#039;&#039;not&#039;&#039;&#039; demonstrate the presence of productive or potable groundwater.&lt;br /&gt;
&lt;br /&gt;
== Proposed geophysical investigation ==&lt;br /&gt;
&lt;br /&gt;
Before drilling, ERT should be used to compare the candidate point with the nearby drainage corridor.&lt;br /&gt;
&lt;br /&gt;
A useful survey geometry would include:&lt;br /&gt;
&lt;br /&gt;
# one profile crossing the principal drainage corridor and both flanks;&lt;br /&gt;
# one profile crossing or passing close to the original candidate point;&lt;br /&gt;
# where practical, an additional intersecting profile to constrain the three-dimensional geometry.&lt;br /&gt;
&lt;br /&gt;
The investigation should look for:&lt;br /&gt;
&lt;br /&gt;
* thickness of the weathered horizon;&lt;br /&gt;
* continuity of the weathered material;&lt;br /&gt;
* fractured upper basement;&lt;br /&gt;
* lateral discontinuities;&lt;br /&gt;
* possible buried drainage or palaeochannel structures;&lt;br /&gt;
* changes in lithology;&lt;br /&gt;
* isolated deep conductive features.&lt;br /&gt;
&lt;br /&gt;
A favourable target would ideally combine a developed weathered horizon with an underlying fractured zone rather than depending solely on one isolated deep fracture.&lt;br /&gt;
&lt;br /&gt;
== Water-quality hypothesis ==&lt;br /&gt;
&lt;br /&gt;
A groundwater system receiving relatively frequent recharge from runoff generated on the Mont Guéra massif may contain younger and less mineralised groundwater than a poorly connected deep fracture system.&lt;br /&gt;
&lt;br /&gt;
A conceptual sequence is:&lt;br /&gt;
&lt;br /&gt;
:rainfall → mountain runoff → drainage concentration → infiltration → weathered basement → connected fractures&lt;br /&gt;
&lt;br /&gt;
Shorter groundwater residence time would generally provide less opportunity for water-rock interaction to increase mineralisation.&lt;br /&gt;
&lt;br /&gt;
This is a hydrogeological hypothesis and has not yet been demonstrated for the Mont Doli candidate area.&lt;br /&gt;
&lt;br /&gt;
Electrical conductivity and major-ion chemistry of nearby existing wells should therefore be mapped before water quality is predicted for a new borehole.&lt;br /&gt;
&lt;br /&gt;
== Site-selection criteria ==&lt;br /&gt;
&lt;br /&gt;
A final drilling location should preferably combine:&lt;br /&gt;
&lt;br /&gt;
* favourable geology;&lt;br /&gt;
* developed weathering;&lt;br /&gt;
* connected fractured basement;&lt;br /&gt;
* evidence of seasonal recharge;&lt;br /&gt;
* acceptable distance from contamination sources;&lt;br /&gt;
* protection from direct flooding;&lt;br /&gt;
* favourable ERT response;&lt;br /&gt;
* positive nearby borehole evidence;&lt;br /&gt;
* acceptable groundwater chemistry in neighbouring sources.&lt;br /&gt;
&lt;br /&gt;
The geophysical target and the sanitary location should be considered together.&lt;br /&gt;
&lt;br /&gt;
== Related pages ==&lt;br /&gt;
&lt;br /&gt;
* [[Regions:Chad/Guéra/Bitkine|Bitkine]]&lt;br /&gt;
* [[Regions:Chad/Guéra/Bitkine/Water_points|Water points]]&lt;br /&gt;
* [[Regions:Chad/Guéra|Guéra]]&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Bitkine]]&lt;br /&gt;
[[Category:Groundwater]]&lt;br /&gt;
[[Category:Hydrogeology]]&lt;br /&gt;
[[Category:Groundwater prospecting]]&lt;/div&gt;</summary>
		<author><name>Samuel</name></author>
	</entry>
	<entry>
		<id>https://aowis.org/index.php?title=Regions:Chad/Gu%C3%A9ra/Bitkine/Water_points&amp;diff=750</id>
		<title>Regions:Chad/Guéra/Bitkine/Water points</title>
		<link rel="alternate" type="text/html" href="https://aowis.org/index.php?title=Regions:Chad/Gu%C3%A9ra/Bitkine/Water_points&amp;diff=750"/>
		<updated>2026-09-20T22:56:37Z</updated>

		<summary type="html">&lt;p&gt;Samuel: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{DISPLAYTITLE:Water points around Bitkine}}&lt;br /&gt;
{{AI-Generated | tool = ChatGPT | date = 2026-09-21 | scope = full page }}&lt;br /&gt;
&lt;br /&gt;
This page documents &#039;&#039;&#039;actual known wells, boreholes and other water sources&#039;&#039;&#039; around [[Regions:Chad/Guéra/Bitkine|Bitkine]].&lt;br /&gt;
&lt;br /&gt;
It is intended as a field inventory. Geological interpretation and proposed future drilling locations are documented separately under [[Regions:Chad/Guéra/Bitkine/Groundwater_prospecting|Groundwater prospecting]].&lt;br /&gt;
&lt;br /&gt;
Water-point information should distinguish clearly between:&lt;br /&gt;
&lt;br /&gt;
* measured values;&lt;br /&gt;
* information reported by owners or operators;&lt;br /&gt;
* approximate or historical values;&lt;br /&gt;
* observations that still require confirmation.&lt;br /&gt;
&lt;br /&gt;
== Inventory ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable sortable&amp;quot;&lt;br /&gt;
! Name&lt;br /&gt;
! Type&lt;br /&gt;
! Location&lt;br /&gt;
! Depth&lt;br /&gt;
! Yield&lt;br /&gt;
! Water quality&lt;br /&gt;
! EC&lt;br /&gt;
! Current use&lt;br /&gt;
! Status&lt;br /&gt;
|-&lt;br /&gt;
| Restaurant Complex&lt;br /&gt;
| Borehole / well&lt;br /&gt;
| &#039;&#039;coordinates to add&#039;&#039;&lt;br /&gt;
| &#039;&#039;unknown&#039;&#039;&lt;br /&gt;
| ~3 m³/h during March–June&lt;br /&gt;
| &#039;&#039;to confirm&#039;&#039;&lt;br /&gt;
| &#039;&#039;not yet measured&#039;&#039;&lt;br /&gt;
| Local use&lt;br /&gt;
| Existing&lt;br /&gt;
|-&lt;br /&gt;
| Djaborona Church&lt;br /&gt;
| Borehole / well&lt;br /&gt;
| &#039;&#039;coordinates to add&#039;&#039;&lt;br /&gt;
| &#039;&#039;unknown&#039;&#039;&lt;br /&gt;
| ~2 m³/h during March–June&lt;br /&gt;
| &#039;&#039;to confirm&#039;&#039;&lt;br /&gt;
| &#039;&#039;not yet measured&#039;&#039;&lt;br /&gt;
| Local use&lt;br /&gt;
| Existing&lt;br /&gt;
|-&lt;br /&gt;
| Elie Tchere&lt;br /&gt;
| Borehole / well&lt;br /&gt;
| &#039;&#039;coordinates to add&#039;&#039;&lt;br /&gt;
| &#039;&#039;unknown&#039;&#039;&lt;br /&gt;
| ~3 m³/h during March–June&lt;br /&gt;
| &#039;&#039;to confirm&#039;&#039;&lt;br /&gt;
| &#039;&#039;not yet measured&#039;&#039;&lt;br /&gt;
| Local use&lt;br /&gt;
| Existing&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The reported yields above are field information and should be replaced or supplemented by measured pumping-test data where available.&lt;br /&gt;
&lt;br /&gt;
Additional known water points should be added as their location and ownership are confirmed.&lt;br /&gt;
&lt;br /&gt;
== Water quality ==&lt;br /&gt;
&lt;br /&gt;
Local observations indicate that both potable and noticeably saline groundwater occur around Bitkine.&lt;br /&gt;
&lt;br /&gt;
At present, water described as &#039;&#039;salty&#039;&#039; is primarily a field description. The actual hydrochemical type has not yet been established for most local sources.&lt;br /&gt;
&lt;br /&gt;
Electrical conductivity should therefore be measured for every accessible water point.&lt;br /&gt;
&lt;br /&gt;
A minimal field record should include:&lt;br /&gt;
&lt;br /&gt;
* electrical conductivity (µS/cm);&lt;br /&gt;
* temperature;&lt;br /&gt;
* pH;&lt;br /&gt;
* pumping rate;&lt;br /&gt;
* duration of pumping before sampling;&lt;br /&gt;
* taste or other field observations;&lt;br /&gt;
* current use of the water.&lt;br /&gt;
&lt;br /&gt;
For selected representative wells, laboratory analysis should include:&lt;br /&gt;
&lt;br /&gt;
* sodium;&lt;br /&gt;
* potassium;&lt;br /&gt;
* calcium;&lt;br /&gt;
* magnesium;&lt;br /&gt;
* chloride;&lt;br /&gt;
* sulfate;&lt;br /&gt;
* bicarbonate / alkalinity;&lt;br /&gt;
* nitrate;&lt;br /&gt;
* fluoride;&lt;br /&gt;
* iron;&lt;br /&gt;
* manganese;&lt;br /&gt;
* microbiological parameters.&lt;br /&gt;
&lt;br /&gt;
Different dissolved salts do not necessarily produce the same taste. A water described as salty may be dominated by sodium chloride, sodium bicarbonate, calcium or magnesium salts, or a mixture of several major ions.&lt;br /&gt;
&lt;br /&gt;
== Electrical conductivity ==&lt;br /&gt;
&lt;br /&gt;
Electrical conductivity is one of the most useful rapid measurements for comparing local groundwater.&lt;br /&gt;
&lt;br /&gt;
Conductivity is recorded in &#039;&#039;&#039;microsiemens per centimetre (µS/cm)&#039;&#039;&#039; and provides an indication of the total concentration of dissolved ions.&lt;br /&gt;
&lt;br /&gt;
Repeated measurements are preferable to a single value, particularly in fractured-rock boreholes.&lt;br /&gt;
&lt;br /&gt;
A useful pumping record is:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Time&lt;br /&gt;
! Pumping rate&lt;br /&gt;
! Water level&lt;br /&gt;
! EC&lt;br /&gt;
! Temperature&lt;br /&gt;
! pH&lt;br /&gt;
! Notes&lt;br /&gt;
|-&lt;br /&gt;
| Before pumping&lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| 5 min&lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| 15 min&lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| 30 min&lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| 1 h&lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| 2 h&lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| 4 h&lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| 8 h&lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Changes in EC during pumping can indicate changing contributions from different fractures.&lt;br /&gt;
&lt;br /&gt;
A decreasing EC may indicate displacement of stagnant or more mineralised water by a fresher source.&lt;br /&gt;
&lt;br /&gt;
An increasing EC may indicate that continued drawdown is recruiting a more mineralised fracture or groundwater body.&lt;br /&gt;
&lt;br /&gt;
Such interpretations require repeated measurements and should not be inferred from taste alone.&lt;br /&gt;
&lt;br /&gt;
== Seasonal behaviour ==&lt;br /&gt;
&lt;br /&gt;
Water-point yield should be recorded throughout the year.&lt;br /&gt;
&lt;br /&gt;
The late dry season is particularly important because a well that performs well shortly after the rainy season may provide substantially less water several months later.&lt;br /&gt;
&lt;br /&gt;
For each important water point, useful seasonal observations include:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Date&lt;br /&gt;
! Season&lt;br /&gt;
! Static water level&lt;br /&gt;
! Pumping rate&lt;br /&gt;
! Pumping duration&lt;br /&gt;
! EC&lt;br /&gt;
! Notes&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Where possible, the same pumping method should be used for repeated measurements so that results remain comparable.&lt;br /&gt;
&lt;br /&gt;
== Individual water-point pages ==&lt;br /&gt;
&lt;br /&gt;
Water points with sufficient information may receive dedicated subpages.&lt;br /&gt;
&lt;br /&gt;
Suggested structure:&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Regions:Chad/Guéra/Bitkine/Water_points/Restaurant_Complex&#039;&#039;&#039;&lt;br /&gt;
:&#039;&#039;&#039;Regions:Chad/Guéra/Bitkine/Water_points/Djaborona_Church&#039;&#039;&#039;&lt;br /&gt;
:&#039;&#039;&#039;Regions:Chad/Guéra/Bitkine/Water_points/Elie_Tchere&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
An individual page can contain:&lt;br /&gt;
&lt;br /&gt;
* precise coordinates;&lt;br /&gt;
* photographs;&lt;br /&gt;
* owner or operator;&lt;br /&gt;
* construction date;&lt;br /&gt;
* borehole depth;&lt;br /&gt;
* casing and screen information;&lt;br /&gt;
* pump type;&lt;br /&gt;
* measured yield;&lt;br /&gt;
* seasonal behaviour;&lt;br /&gt;
* EC measurements;&lt;br /&gt;
* laboratory chemistry;&lt;br /&gt;
* pumping-test results;&lt;br /&gt;
* current use;&lt;br /&gt;
* maintenance history;&lt;br /&gt;
* nearby water points;&lt;br /&gt;
* field notes.&lt;br /&gt;
&lt;br /&gt;
== Data quality ==&lt;br /&gt;
&lt;br /&gt;
Field information should retain its source.&lt;br /&gt;
&lt;br /&gt;
Values reported verbally by an owner should be marked as reported values until they are independently measured.&lt;br /&gt;
&lt;br /&gt;
Approximate coordinates should not be presented as survey-quality positions.&lt;br /&gt;
&lt;br /&gt;
Water described as potable should not be considered microbiologically safe without appropriate testing.&lt;br /&gt;
&lt;br /&gt;
== Related pages ==&lt;br /&gt;
&lt;br /&gt;
* [[Regions:Chad/Guéra/Bitkine|Bitkine]]&lt;br /&gt;
* [[Regions:Chad/Guéra/Bitkine/Groundwater_prospecting|Groundwater prospecting]]&lt;br /&gt;
* [[Regions:Chad/Guéra|Guéra]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Bitkine]]&lt;br /&gt;
[[Category:Water points]]&lt;br /&gt;
[[Category:Groundwater]]&lt;br /&gt;
[[Category:Water supply]]&lt;/div&gt;</summary>
		<author><name>Samuel</name></author>
	</entry>
	<entry>
		<id>https://aowis.org/index.php?title=Regions:Chad/Gu%C3%A9ra/Bitkine/Water_points&amp;diff=749</id>
		<title>Regions:Chad/Guéra/Bitkine/Water points</title>
		<link rel="alternate" type="text/html" href="https://aowis.org/index.php?title=Regions:Chad/Gu%C3%A9ra/Bitkine/Water_points&amp;diff=749"/>
		<updated>2026-09-20T22:56:13Z</updated>

		<summary type="html">&lt;p&gt;Samuel: Created page with &amp;quot;{{AI-Generated | tool = ChatGPT | date = 2026-09-21 | scope = full page }}  {{DISPLAYTITLE:Water points around Bitkine}}  This page documents &amp;#039;&amp;#039;&amp;#039;actual known wells, boreholes and other water sources&amp;#039;&amp;#039;&amp;#039; around Bitkine.  It is intended as a field inventory. Geological interpretation and proposed future drilling locations are documented separately under Groundwater prospecting.  Water-po...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{AI-Generated | tool = ChatGPT | date = 2026-09-21 | scope = full page }}&lt;br /&gt;
&lt;br /&gt;
{{DISPLAYTITLE:Water points around Bitkine}}&lt;br /&gt;
&lt;br /&gt;
This page documents &#039;&#039;&#039;actual known wells, boreholes and other water sources&#039;&#039;&#039; around [[Regions:Chad/Guéra/Bitkine|Bitkine]].&lt;br /&gt;
&lt;br /&gt;
It is intended as a field inventory. Geological interpretation and proposed future drilling locations are documented separately under [[Regions:Chad/Guéra/Bitkine/Groundwater_prospecting|Groundwater prospecting]].&lt;br /&gt;
&lt;br /&gt;
Water-point information should distinguish clearly between:&lt;br /&gt;
&lt;br /&gt;
* measured values;&lt;br /&gt;
* information reported by owners or operators;&lt;br /&gt;
* approximate or historical values;&lt;br /&gt;
* observations that still require confirmation.&lt;br /&gt;
&lt;br /&gt;
== Inventory ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable sortable&amp;quot;&lt;br /&gt;
! Name&lt;br /&gt;
! Type&lt;br /&gt;
! Location&lt;br /&gt;
! Depth&lt;br /&gt;
! Yield&lt;br /&gt;
! Water quality&lt;br /&gt;
! EC&lt;br /&gt;
! Current use&lt;br /&gt;
! Status&lt;br /&gt;
|-&lt;br /&gt;
| Restaurant Complex&lt;br /&gt;
| Borehole / well&lt;br /&gt;
| &#039;&#039;coordinates to add&#039;&#039;&lt;br /&gt;
| &#039;&#039;unknown&#039;&#039;&lt;br /&gt;
| ~3 m³/h during March–June&lt;br /&gt;
| &#039;&#039;to confirm&#039;&#039;&lt;br /&gt;
| &#039;&#039;not yet measured&#039;&#039;&lt;br /&gt;
| Local use&lt;br /&gt;
| Existing&lt;br /&gt;
|-&lt;br /&gt;
| Djaborona Church&lt;br /&gt;
| Borehole / well&lt;br /&gt;
| &#039;&#039;coordinates to add&#039;&#039;&lt;br /&gt;
| &#039;&#039;unknown&#039;&#039;&lt;br /&gt;
| ~2 m³/h during March–June&lt;br /&gt;
| &#039;&#039;to confirm&#039;&#039;&lt;br /&gt;
| &#039;&#039;not yet measured&#039;&#039;&lt;br /&gt;
| Local use&lt;br /&gt;
| Existing&lt;br /&gt;
|-&lt;br /&gt;
| Elie Tchere&lt;br /&gt;
| Borehole / well&lt;br /&gt;
| &#039;&#039;coordinates to add&#039;&#039;&lt;br /&gt;
| &#039;&#039;unknown&#039;&#039;&lt;br /&gt;
| ~3 m³/h during March–June&lt;br /&gt;
| &#039;&#039;to confirm&#039;&#039;&lt;br /&gt;
| &#039;&#039;not yet measured&#039;&#039;&lt;br /&gt;
| Local use&lt;br /&gt;
| Existing&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The reported yields above are field information and should be replaced or supplemented by measured pumping-test data where available.&lt;br /&gt;
&lt;br /&gt;
Additional known water points should be added as their location and ownership are confirmed.&lt;br /&gt;
&lt;br /&gt;
== Water quality ==&lt;br /&gt;
&lt;br /&gt;
Local observations indicate that both potable and noticeably saline groundwater occur around Bitkine.&lt;br /&gt;
&lt;br /&gt;
At present, water described as &#039;&#039;salty&#039;&#039; is primarily a field description. The actual hydrochemical type has not yet been established for most local sources.&lt;br /&gt;
&lt;br /&gt;
Electrical conductivity should therefore be measured for every accessible water point.&lt;br /&gt;
&lt;br /&gt;
A minimal field record should include:&lt;br /&gt;
&lt;br /&gt;
* electrical conductivity (µS/cm);&lt;br /&gt;
* temperature;&lt;br /&gt;
* pH;&lt;br /&gt;
* pumping rate;&lt;br /&gt;
* duration of pumping before sampling;&lt;br /&gt;
* taste or other field observations;&lt;br /&gt;
* current use of the water.&lt;br /&gt;
&lt;br /&gt;
For selected representative wells, laboratory analysis should include:&lt;br /&gt;
&lt;br /&gt;
* sodium;&lt;br /&gt;
* potassium;&lt;br /&gt;
* calcium;&lt;br /&gt;
* magnesium;&lt;br /&gt;
* chloride;&lt;br /&gt;
* sulfate;&lt;br /&gt;
* bicarbonate / alkalinity;&lt;br /&gt;
* nitrate;&lt;br /&gt;
* fluoride;&lt;br /&gt;
* iron;&lt;br /&gt;
* manganese;&lt;br /&gt;
* microbiological parameters.&lt;br /&gt;
&lt;br /&gt;
Different dissolved salts do not necessarily produce the same taste. A water described as salty may be dominated by sodium chloride, sodium bicarbonate, calcium or magnesium salts, or a mixture of several major ions.&lt;br /&gt;
&lt;br /&gt;
== Electrical conductivity ==&lt;br /&gt;
&lt;br /&gt;
Electrical conductivity is one of the most useful rapid measurements for comparing local groundwater.&lt;br /&gt;
&lt;br /&gt;
Conductivity is recorded in &#039;&#039;&#039;microsiemens per centimetre (µS/cm)&#039;&#039;&#039; and provides an indication of the total concentration of dissolved ions.&lt;br /&gt;
&lt;br /&gt;
Repeated measurements are preferable to a single value, particularly in fractured-rock boreholes.&lt;br /&gt;
&lt;br /&gt;
A useful pumping record is:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Time&lt;br /&gt;
! Pumping rate&lt;br /&gt;
! Water level&lt;br /&gt;
! EC&lt;br /&gt;
! Temperature&lt;br /&gt;
! pH&lt;br /&gt;
! Notes&lt;br /&gt;
|-&lt;br /&gt;
| Before pumping&lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| 5 min&lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| 15 min&lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| 30 min&lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| 1 h&lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| 2 h&lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| 4 h&lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| 8 h&lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Changes in EC during pumping can indicate changing contributions from different fractures.&lt;br /&gt;
&lt;br /&gt;
A decreasing EC may indicate displacement of stagnant or more mineralised water by a fresher source.&lt;br /&gt;
&lt;br /&gt;
An increasing EC may indicate that continued drawdown is recruiting a more mineralised fracture or groundwater body.&lt;br /&gt;
&lt;br /&gt;
Such interpretations require repeated measurements and should not be inferred from taste alone.&lt;br /&gt;
&lt;br /&gt;
== Seasonal behaviour ==&lt;br /&gt;
&lt;br /&gt;
Water-point yield should be recorded throughout the year.&lt;br /&gt;
&lt;br /&gt;
The late dry season is particularly important because a well that performs well shortly after the rainy season may provide substantially less water several months later.&lt;br /&gt;
&lt;br /&gt;
For each important water point, useful seasonal observations include:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Date&lt;br /&gt;
! Season&lt;br /&gt;
! Static water level&lt;br /&gt;
! Pumping rate&lt;br /&gt;
! Pumping duration&lt;br /&gt;
! EC&lt;br /&gt;
! Notes&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Where possible, the same pumping method should be used for repeated measurements so that results remain comparable.&lt;br /&gt;
&lt;br /&gt;
== Individual water-point pages ==&lt;br /&gt;
&lt;br /&gt;
Water points with sufficient information may receive dedicated subpages.&lt;br /&gt;
&lt;br /&gt;
Suggested structure:&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Regions:Chad/Guéra/Bitkine/Water_points/Restaurant_Complex&#039;&#039;&#039;&lt;br /&gt;
:&#039;&#039;&#039;Regions:Chad/Guéra/Bitkine/Water_points/Djaborona_Church&#039;&#039;&#039;&lt;br /&gt;
:&#039;&#039;&#039;Regions:Chad/Guéra/Bitkine/Water_points/Elie_Tchere&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
An individual page can contain:&lt;br /&gt;
&lt;br /&gt;
* precise coordinates;&lt;br /&gt;
* photographs;&lt;br /&gt;
* owner or operator;&lt;br /&gt;
* construction date;&lt;br /&gt;
* borehole depth;&lt;br /&gt;
* casing and screen information;&lt;br /&gt;
* pump type;&lt;br /&gt;
* measured yield;&lt;br /&gt;
* seasonal behaviour;&lt;br /&gt;
* EC measurements;&lt;br /&gt;
* laboratory chemistry;&lt;br /&gt;
* pumping-test results;&lt;br /&gt;
* current use;&lt;br /&gt;
* maintenance history;&lt;br /&gt;
* nearby water points;&lt;br /&gt;
* field notes.&lt;br /&gt;
&lt;br /&gt;
== Data quality ==&lt;br /&gt;
&lt;br /&gt;
Field information should retain its source.&lt;br /&gt;
&lt;br /&gt;
Values reported verbally by an owner should be marked as reported values until they are independently measured.&lt;br /&gt;
&lt;br /&gt;
Approximate coordinates should not be presented as survey-quality positions.&lt;br /&gt;
&lt;br /&gt;
Water described as potable should not be considered microbiologically safe without appropriate testing.&lt;br /&gt;
&lt;br /&gt;
== Related pages ==&lt;br /&gt;
&lt;br /&gt;
* [[Regions:Chad/Guéra/Bitkine|Bitkine]]&lt;br /&gt;
* [[Regions:Chad/Guéra/Bitkine/Groundwater_prospecting|Groundwater prospecting]]&lt;br /&gt;
* [[Regions:Chad/Guéra|Guéra]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Bitkine]]&lt;br /&gt;
[[Category:Water points]]&lt;br /&gt;
[[Category:Groundwater]]&lt;br /&gt;
[[Category:Water supply]]&lt;/div&gt;</summary>
		<author><name>Samuel</name></author>
	</entry>
	<entry>
		<id>https://aowis.org/index.php?title=Regions:Chad/Gu%C3%A9ra/Bitkine&amp;diff=748</id>
		<title>Regions:Chad/Guéra/Bitkine</title>
		<link rel="alternate" type="text/html" href="https://aowis.org/index.php?title=Regions:Chad/Gu%C3%A9ra/Bitkine&amp;diff=748"/>
		<updated>2026-09-20T22:54:44Z</updated>

		<summary type="html">&lt;p&gt;Samuel: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{AI-Generated | tool = ChatGPT | date = 2026-09-21 | scope = full page }}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Bitkine&#039;&#039;&#039; is a town in the [[Regions:Chad/Guéra|Guéra]] province of central [[Regions:Chad|Chad]] and the capital of the &#039;&#039;&#039;Abtouyour&#039;&#039;&#039; department. It lies immediately north of the Mont Guéra massif, where strongly seasonal runoff from the mountains reaches the flatter plains around the town.&lt;br /&gt;
&lt;br /&gt;
Groundwater is the principal dependable water resource. The local aquifers occur in weathered and fractured crystalline basement and are highly heterogeneous. Boreholes separated by relatively short distances may therefore encounter very different yields and water quality.&lt;br /&gt;
&lt;br /&gt;
Bitkine has become an important study area for groundwater prospecting in Guéra. A 2023–2024 investigation by SEVES, Sorbonne Université&#039;s UMR METIS and ANTEA analysed existing boreholes and electrical-resistivity surveys around the town to improve the siting of future water-supply boreholes.&amp;lt;ref name=&amp;quot;palomar&amp;quot;&amp;gt;[https://nextcloud.aowis.org/s/j7Gy7bMrFr5Gsew Pierre Palomar, &#039;&#039;Conceptualisation hydrogéologique et recommandations pour les prospections géophysiques et l&#039;implantation des forages — Province du Guéra, Tchad&#039;&#039;, SEVES, 2024.]&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Physical setting ==&lt;br /&gt;
&lt;br /&gt;
Bitkine lies on the northern side of the Mont Guéra massif. The massif rises abruptly south of the town and forms a major local catchment for seasonal rainfall.&lt;br /&gt;
&lt;br /&gt;
The terrain between the massif and Bitkine is crossed by seasonal drainage systems. During the rainy season, runoff is concentrated into valleys, wadis and branching channels before spreading across lower terrain farther north.&lt;br /&gt;
&lt;br /&gt;
This relationship between steep uplands, seasonal drainage and piedmont areas is important for groundwater recharge. Rain falling on exposed or relatively impermeable mountain slopes may run off rapidly, while infiltration can become concentrated where this water reaches flatter terrain, weathered rock, sandy deposits and fractured basement.&lt;br /&gt;
&lt;br /&gt;
== Geology ==&lt;br /&gt;
&lt;br /&gt;
The Bitkine area forms part of the crystalline basement of the Guéra massif.&lt;br /&gt;
&lt;br /&gt;
The local geology includes:&lt;br /&gt;
&lt;br /&gt;
* granite;&lt;br /&gt;
* biotite granite;&lt;br /&gt;
* granodiorite;&lt;br /&gt;
* diorite;&lt;br /&gt;
* dolerite;&lt;br /&gt;
* locally other intrusive and metamorphic rocks.&lt;br /&gt;
&lt;br /&gt;
The wider Guéra basement is dominated by granitoids rather than one homogeneous granite body.&amp;lt;ref name=&amp;quot;nouradine&amp;quot;&amp;gt;[https://nextcloud.aowis.org/s/tCJgPAa2G6Lws83 Haroun Nouradine, &#039;&#039;Évaluation des ressources en eau dans les aquifères de socle dans la région du Guéra (Tchad) : combinaison d&#039;approches géologiques, hydrogéologiques, géophysiques, géochimiques et d&#039;apprentissage automatique&#039;&#039;, doctoral thesis, Sorbonne Université, 2023.]&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;article&amp;quot;&amp;gt;[https://doi.org/10.1007/s10040-024-02766-2 H. Nouradine et al., &#039;&#039;Integrating geological, hydrogeological and geophysical data to identify groundwater resources in granitic basement areas (Guéra Massif, Chad)&#039;&#039;, Hydrogeology Journal 32, 759–784, 2024.]&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Rock type influences development of the aquifer. Weathering of granite tends to produce relatively sandy material, while weathering of more mafic rocks such as diorite can produce more clay-rich material. Thick clay-rich alteration can inhibit infiltration, whereas permeable weathered granite together with an underlying fractured horizon can provide favourable groundwater conditions.&amp;lt;ref name=&amp;quot;palomar&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The area around Mont Doli southwest of Bitkine contains both granitic and dioritic/granodioritic formations and should not be treated as geologically uniform.&lt;br /&gt;
&lt;br /&gt;
== Groundwater system ==&lt;br /&gt;
&lt;br /&gt;
Groundwater around Bitkine occurs mainly in &#039;&#039;&#039;discontinuous hard-rock aquifers&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
A simplified local profile consists of:&lt;br /&gt;
&lt;br /&gt;
# soil, alluvium or superficial deposits;&lt;br /&gt;
# weathered crystalline basement;&lt;br /&gt;
# a fractured or fissured basement horizon;&lt;br /&gt;
# progressively less fractured competent bedrock.&lt;br /&gt;
&lt;br /&gt;
The weathered horizon can provide groundwater storage, while the fractured horizon beneath it can provide the principal pathways through which groundwater moves toward a borehole.&lt;br /&gt;
&lt;br /&gt;
Unweathered crystalline rock has very low primary porosity. Productive groundwater therefore depends on the local development and hydraulic connection of weathered material and fractures.&lt;br /&gt;
&lt;br /&gt;
This makes the aquifer highly heterogeneous. A productive borehole does not imply that another borehole a few hundred metres away will encounter the same water-bearing structure.&lt;br /&gt;
&lt;br /&gt;
== Groundwater recharge ==&lt;br /&gt;
&lt;br /&gt;
Recharge is strongly seasonal.&lt;br /&gt;
&lt;br /&gt;
During the rainy season, runoff becomes concentrated along temporary channels draining the Mont Guéra massif. These channels can collect water from catchments considerably larger than the immediate area around a borehole.&lt;br /&gt;
&lt;br /&gt;
Important recharge may occur particularly in:&lt;br /&gt;
&lt;br /&gt;
* valleys;&lt;br /&gt;
* wadis and talwegs;&lt;br /&gt;
* piedmont depressions;&lt;br /&gt;
* alluvial deposits;&lt;br /&gt;
* permeable weathered zones;&lt;br /&gt;
* fractures hydraulically connected to these features.&lt;br /&gt;
&lt;br /&gt;
The centre of an active drainage channel is not necessarily the preferred position for a drinking-water borehole. Although such locations may receive strong recharge, they are also more exposed to flooding, erosion and rapid infiltration of surface contamination.&lt;br /&gt;
&lt;br /&gt;
A productive fractured aquifer intercepted from the flank of a drainage corridor may therefore provide a better compromise between recharge and sanitary protection.&lt;br /&gt;
&lt;br /&gt;
Quantification of long-term recharge remains uncertain. Sustainable groundwater development requires repeated monitoring of groundwater level, pumping rate and seasonal behaviour rather than reliance on a single pumping test.&amp;lt;ref name=&amp;quot;palomar&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Hydrogeophysical investigation ==&lt;br /&gt;
&lt;br /&gt;
Pierre Palomar&#039;s study reinterpreted &#039;&#039;&#039;61 electrical-resistivity tomography (ERT) sites&#039;&#039;&#039; around Bitkine and compared the geophysical profiles with available drilling information.&amp;lt;ref name=&amp;quot;palomar&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The study classified local hydrogeophysical conditions into several conceptual models.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;A and A*&#039;&#039;&#039; represent sites with relatively well-developed weathered and fractured horizons and are generally the most favourable classes for productive boreholes.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;B and B*&#039;&#039;&#039; represent conditions where alteration is poorly developed or where production depends more strongly on an isolated fracture in otherwise competent basement.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;C&#039;&#039;&#039; represents strong lateral discontinuities such as fractures, dykes, veins or changes in lithology.&lt;br /&gt;
&lt;br /&gt;
A* sites performed particularly well in the analysed dataset. Approximately &#039;&#039;&#039;31% of A* sites produced at least 5 m³/h&#039;&#039;&#039;. For A sites, approximately &#039;&#039;&#039;14% produced at least 5 m³/h&#039;&#039;&#039; and approximately &#039;&#039;&#039;36% produced at least 3 m³/h&#039;&#039;&#039;.&amp;lt;ref name=&amp;quot;palomar&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Geophysical anomalies alone do not guarantee groundwater. ERT must be interpreted together with geology, topography, weathering, drainage and nearby drilling results.&lt;br /&gt;
&lt;br /&gt;
== South of Bitkine ==&lt;br /&gt;
&lt;br /&gt;
One of the most important results of the Bitkine study is the geographic distribution of the hydrogeophysical models.&lt;br /&gt;
&lt;br /&gt;
North of Bitkine, many investigated sites belong to the B* class, in which groundwater production depends largely on deeper fractures.&lt;br /&gt;
&lt;br /&gt;
South of Bitkine, toward the Mont Guéra massif, A and A* sites are more common. Palomar therefore identifies the southern sector as a &#039;&#039;&#039;preferred area for drinking-water prospecting&#039;&#039;&#039;.&amp;lt;ref name=&amp;quot;palomar&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This does not mean that any location south of Bitkine will contain productive or potable groundwater. It indicates that geological and weathering conditions associated with productive basement aquifers occur more frequently there in the available dataset.&lt;br /&gt;
&lt;br /&gt;
The mountain-front setting may also favour relatively frequent recharge where runoff from the massif enters weathered and fractured terrain. Whether such recharge also produces systematically less mineralised groundwater remains to be demonstrated through local water-quality measurements.&lt;br /&gt;
&lt;br /&gt;
Current AOWIS prospecting work is documented separately:&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;[[Regions:Chad/Guéra/Bitkine/Groundwater_prospecting|Groundwater prospecting around Bitkine]]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
== Borehole productivity ==&lt;br /&gt;
&lt;br /&gt;
Groundwater development around Bitkine remains difficult even after hydrogeophysical prospecting.&lt;br /&gt;
&lt;br /&gt;
The wider Guéra dataset analysed by Palomar shows that among 137 historical boreholes:&lt;br /&gt;
&lt;br /&gt;
* 47% were unsuccessful during drilling and were not equipped;&lt;br /&gt;
* 42% had yields considered too low for connection to a piped drinking-water network;&lt;br /&gt;
* only 11% provided approximately 4 m³/h for 8 hours per day.&amp;lt;ref name=&amp;quot;palomar&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The study concludes that a town of Bitkine&#039;s size cannot normally be expected to depend on one exceptionally productive borehole. A more robust supply is likely to require a &#039;&#039;&#039;well field consisting of several moderate-yield boreholes&#039;&#039;&#039;.&amp;lt;ref name=&amp;quot;palomar&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Under the REAVIA programme, SEVES and ADES reported a newly developed borehole at Bitkine producing approximately &#039;&#039;&#039;6 m³/h&#039;&#039;&#039;. Several unsuccessful drillings were also encountered during the same groundwater-development work.&amp;lt;ref name=&amp;quot;reavia&amp;quot;&amp;gt;[https://www.asso-seves.org/tchad-mobilisation-de-la-ressource-en-eau-pour-les-services-d-eau-potable-de.html SEVES, &#039;&#039;Mobilisation de la ressource en eau pour les services d&#039;eau potable de Bitkine et Koubo Adougoul dans la province du Guéra — REAVIA&#039;&#039;.]&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Groundwater quality and salinity ==&lt;br /&gt;
&lt;br /&gt;
Water quality can vary substantially over short distances around Bitkine.&lt;br /&gt;
&lt;br /&gt;
This is compatible with the fractured-basement aquifer system. Nearby boreholes may intersect different fracture networks with different recharge, residence times and geochemical histories.&lt;br /&gt;
&lt;br /&gt;
Regional geochemical work by Nouradine was concentrated primarily around Mongo rather than Bitkine. It therefore provides a conceptual framework but should not be used as direct evidence for the chemistry of individual Bitkine boreholes.&lt;br /&gt;
&lt;br /&gt;
The Guéra data show that deeper fractured groundwater is generally more mineralised than shallow groundwater. Prolonged water-rock interaction with silicate minerals can increase dissolved sodium, calcium, magnesium, potassium and bicarbonate. Older or poorly renewed fracture water may consequently be more mineralised than groundwater receiving frequent recent recharge.&amp;lt;ref name=&amp;quot;nouradine&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Water described locally as &#039;&#039;salty&#039;&#039; should not automatically be assumed to be sodium-chloride water. Determining the actual hydrochemical type requires analysis of the major dissolved ions.&lt;br /&gt;
&lt;br /&gt;
Particularly useful measurements include electrical conductivity, temperature, pH, sodium, potassium, calcium, magnesium, chloride, sulfate, alkalinity/bicarbonate, nitrate, fluoride, iron, manganese and microbiological parameters.&lt;br /&gt;
&lt;br /&gt;
Actual Bitkine water points and their measured properties are documented separately:&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;[[Regions:Chad/Guéra/Bitkine/Water_points|Bitkine water points]]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
== Water services ==&lt;br /&gt;
&lt;br /&gt;
Since 2022, &#039;&#039;&#039;SEVES&#039;&#039;&#039; and its Chadian partner &#039;&#039;&#039;ADES&#039;&#039;&#039; have been supporting water services in Bitkine and surrounding smaller centres.&amp;lt;ref name=&amp;quot;palomar&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
SEVES reports that existing services frequently experience interruptions or are unable to meet demand, particularly during the dry season, largely because insufficient groundwater has been successfully mobilised.&amp;lt;ref name=&amp;quot;palomar&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The REAVIA programme combines groundwater prospecting and drilling with support for the organisation and long-term operation of local water services. Work is conducted with the regional delegation of the ministry responsible for water and with the Commune of Bitkine.&amp;lt;ref name=&amp;quot;seves&amp;quot;&amp;gt;[https://www.asso-seves.org/implantation-des-forages-dans-la-province-du-guera-autchad.html SEVES, &#039;&#039;Implantation des forages dans la province du Guéra au Tchad&#039;&#039;, 2024.]&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== AOWIS work ==&lt;br /&gt;
&lt;br /&gt;
AOWIS work around Bitkine combines field documentation of existing water sources with investigation of additional groundwater resources and future infrastructure.&lt;br /&gt;
&lt;br /&gt;
The current work includes:&lt;br /&gt;
&lt;br /&gt;
* inventory and monitoring of existing water points;&lt;br /&gt;
* groundwater-quality measurements;&lt;br /&gt;
* seasonal yield measurements;&lt;br /&gt;
* investigation of additional borehole sites;&lt;br /&gt;
* evaluation of storage, pumping, treatment and distribution;&lt;br /&gt;
* development of methods for combining local field observations with hydrogeological and geophysical information.&lt;br /&gt;
&lt;br /&gt;
Detailed field data belong in the relevant subpages rather than in this regional overview.&lt;br /&gt;
&lt;br /&gt;
== Related pages ==&lt;br /&gt;
&lt;br /&gt;
* [[Regions:Chad/Guéra/Bitkine/Water_points|Water points]]&lt;br /&gt;
* [[Regions:Chad/Guéra/Bitkine/Groundwater_prospecting|Groundwater prospecting]]&lt;br /&gt;
* [[Regions:Chad/Guéra|Guéra]]&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== External resources ==&lt;br /&gt;
&lt;br /&gt;
* [https://nextcloud.aowis.org/s/tCJgPAa2G6Lws83 Nouradine 2023 doctoral thesis — AOWIS-hosted PDF]&lt;br /&gt;
* [https://nextcloud.aowis.org/s/j7Gy7bMrFr5Gsew Palomar / SEVES Bitkine hydrogeology report — AOWIS-hosted PDF]&lt;br /&gt;
* [https://doi.org/10.1007/s10040-024-02766-2 Nouradine et al. 2024 — Hydrogeology Journal]&lt;br /&gt;
* [https://www.asso-seves.org/implantation-des-forages-dans-la-province-du-guera-autchad.html SEVES — groundwater prospecting in Guéra]&lt;br /&gt;
&lt;br /&gt;
[[Category:Chad]]&lt;br /&gt;
[[Category:Guéra]]&lt;br /&gt;
[[Category:Bitkine]]&lt;br /&gt;
[[Category:Groundwater]]&lt;br /&gt;
[[Category:Hydrogeology]]&lt;br /&gt;
[[Category:Water supply]]&lt;/div&gt;</summary>
		<author><name>Samuel</name></author>
	</entry>
	<entry>
		<id>https://aowis.org/index.php?title=Regions:Chad/Gu%C3%A9ra/Bitkine&amp;diff=747</id>
		<title>Regions:Chad/Guéra/Bitkine</title>
		<link rel="alternate" type="text/html" href="https://aowis.org/index.php?title=Regions:Chad/Gu%C3%A9ra/Bitkine&amp;diff=747"/>
		<updated>2026-09-20T22:28:42Z</updated>

		<summary type="html">&lt;p&gt;Samuel: Created page with &amp;quot;{{AI-Generated | tool = ChatGPT | date = 2026-09-21 | scope = full page }}  &amp;#039;&amp;#039;&amp;#039;Bitkine&amp;#039;&amp;#039;&amp;#039; is a town in the Guéra province of central Chad and the capital of the &amp;#039;&amp;#039;&amp;#039;Abtouyour&amp;#039;&amp;#039;&amp;#039; department. It lies immediately north of the Mont Guéra massif, in an area where strongly seasonal runoff from the mountains meets the flatter plains around the town.  Groundwater is the principal dependable water resource, but obtaining productive and co...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{AI-Generated | tool = ChatGPT | date = 2026-09-21 | scope = full page }}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Bitkine&#039;&#039;&#039; is a town in the [[Regions:Chad/Guéra|Guéra]] province of central [[Regions:Chad|Chad]] and the capital of the &#039;&#039;&#039;Abtouyour&#039;&#039;&#039; department. It lies immediately north of the Mont Guéra massif, in an area where strongly seasonal runoff from the mountains meets the flatter plains around the town.&lt;br /&gt;
&lt;br /&gt;
Groundwater is the principal dependable water resource, but obtaining productive and consistently potable boreholes is difficult. The local aquifers occur in weathered and fractured crystalline basement and can vary substantially over short distances. Boreholes in the same general area may therefore differ greatly in yield and water quality.&lt;br /&gt;
&lt;br /&gt;
Bitkine has become an important local study area for groundwater prospecting in Guéra. A 2023–2024 hydrogeophysical investigation by SEVES, Sorbonne Université&#039;s UMR METIS and ANTEA specifically analysed existing boreholes and electrical-resistivity surveys around the town to improve the siting of future boreholes.&amp;lt;ref name=&amp;quot;palomar&amp;quot;&amp;gt;[https://nextcloud.aowis.org/s/j7Gy7bMrFr5Gsew Pierre Palomar, &#039;&#039;Conceptualisation hydrogéologique et recommandations pour les prospections géophysiques et l&#039;implantation des forages — Province du Guéra, Tchad&#039;&#039;, SEVES, 2024.]&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Physical setting ==&lt;br /&gt;
&lt;br /&gt;
Bitkine lies on the northern side of the Mont Guéra massif. The massif rises abruptly south of the town and forms a major local catchment for seasonal rainfall.&lt;br /&gt;
&lt;br /&gt;
The terrain between the mountain front and Bitkine is crossed by seasonal drainage systems. During the rainy season, runoff from the massif is concentrated into valleys, wadis and branching channels before spreading across the lower terrain north of the mountains.&lt;br /&gt;
&lt;br /&gt;
This relationship between steep uplands, seasonal drainage and low-lying piedmont areas is important for groundwater recharge. Rainfall falling on exposed or relatively impermeable mountain slopes may run off rapidly, while infiltration can become concentrated where this water reaches flatter terrain, weathered rock, sandy deposits and fractured basement.&lt;br /&gt;
&lt;br /&gt;
== Geology ==&lt;br /&gt;
&lt;br /&gt;
The Bitkine area forms part of the crystalline basement of the Guéra massif.&lt;br /&gt;
&lt;br /&gt;
The local geology includes:&lt;br /&gt;
&lt;br /&gt;
* granite;&lt;br /&gt;
* biotite granite;&lt;br /&gt;
* granodiorite;&lt;br /&gt;
* diorite;&lt;br /&gt;
* dolerite;&lt;br /&gt;
* locally other intrusive and metamorphic rocks.&lt;br /&gt;
&lt;br /&gt;
The wider Guéra basement is dominated by granitoids rather than one homogeneous granite body.&amp;lt;ref name=&amp;quot;nouradine&amp;quot;&amp;gt;[https://nextcloud.aowis.org/s/tCJgPAa2G6Lws83 Haroun Nouradine, &#039;&#039;Évaluation des ressources en eau dans les aquifères de socle dans la région du Guéra (Tchad) : combinaison d&#039;approches géologiques, hydrogéologiques, géophysiques, géochimiques et d&#039;apprentissage automatique&#039;&#039;, doctoral thesis, Sorbonne Université, 2023.]&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;article&amp;quot;&amp;gt;[https://doi.org/10.1007/s10040-024-02766-2 H. Nouradine et al., &#039;&#039;Integrating geological, hydrogeological and geophysical data to identify groundwater resources in granitic basement areas (Guéra Massif, Chad)&#039;&#039;, Hydrogeology Journal 32, 759–784, 2024.]&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Rock type influences the development of the aquifer. Weathering of granite tends to produce relatively sandy material, while weathering of more mafic rocks such as diorite can produce more clay-rich material. Thick clay-rich alteration can inhibit infiltration, whereas permeable weathered granite together with an underlying fractured horizon can provide favourable groundwater conditions.&amp;lt;ref name=&amp;quot;palomar&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The area around Mont Doli, southwest of Bitkine, contains both granitic and dioritic/granodioritic formations and should therefore not be treated as geologically uniform.&lt;br /&gt;
&lt;br /&gt;
== Groundwater system ==&lt;br /&gt;
&lt;br /&gt;
Groundwater around Bitkine occurs mainly in &#039;&#039;&#039;discontinuous hard-rock aquifers&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
A simplified local profile consists of:&lt;br /&gt;
&lt;br /&gt;
# soil, alluvium or superficial deposits;&lt;br /&gt;
# weathered crystalline basement;&lt;br /&gt;
# a fractured or fissured basement horizon;&lt;br /&gt;
# progressively less fractured competent bedrock.&lt;br /&gt;
&lt;br /&gt;
The weathered horizon can provide groundwater storage, while the fractured horizon beneath it can provide the main pathways through which groundwater moves toward a borehole.&lt;br /&gt;
&lt;br /&gt;
Unweathered crystalline rock has very low primary porosity. Productive groundwater therefore depends on the local development and hydraulic connection of weathered material and fractures.&lt;br /&gt;
&lt;br /&gt;
This makes the aquifer highly heterogeneous. A productive borehole does not imply that another borehole a few hundred metres away will encounter the same water-bearing structure.&lt;br /&gt;
&lt;br /&gt;
== Hydrogeophysical investigation ==&lt;br /&gt;
&lt;br /&gt;
Pierre Palomar&#039;s study reinterpreted &#039;&#039;&#039;61 electrical-resistivity tomography (ERT) sites&#039;&#039;&#039; around Bitkine and compared the geophysical profiles with available drilling information.&amp;lt;ref name=&amp;quot;palomar&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The study classified hydrogeophysical conditions into several conceptual models.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;A and A*&#039;&#039;&#039; represent sites with relatively well-developed weathered and fractured horizons. These were the most favourable classes for obtaining productive boreholes.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;B and B*&#039;&#039;&#039; represent conditions where alteration is poorly developed or where production depends more strongly on an isolated fracture in otherwise competent basement.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;C&#039;&#039;&#039; represents strong lateral discontinuities such as fractures, dykes, veins or changes in lithology, where the interpretation and drilling result can be less predictable.&lt;br /&gt;
&lt;br /&gt;
In the analysed dataset, A* sites performed particularly well. Approximately &#039;&#039;&#039;31% of A* sites produced at least 5 m³/h&#039;&#039;&#039;. For A sites, approximately &#039;&#039;&#039;14% produced at least 5 m³/h&#039;&#039;&#039; and approximately &#039;&#039;&#039;36% produced at least 3 m³/h&#039;&#039;&#039;.&amp;lt;ref name=&amp;quot;palomar&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The results nevertheless show that geophysical prospecting cannot guarantee a successful borehole. ERT must be interpreted together with geology, topography, weathering, drainage and drilling information.&lt;br /&gt;
&lt;br /&gt;
== South of Bitkine ==&lt;br /&gt;
&lt;br /&gt;
One of the most important results of the Bitkine-specific study is the geographic distribution of the hydrogeophysical models.&lt;br /&gt;
&lt;br /&gt;
North of Bitkine, many investigated sites belong to the B* class, in which groundwater production depends largely on deeper fractures.&lt;br /&gt;
&lt;br /&gt;
South of Bitkine, toward the Mont Guéra massif, A and A* sites are more common. Palomar therefore identifies the southern sector as a &#039;&#039;&#039;preferred area for drinking-water prospecting&#039;&#039;&#039;.&amp;lt;ref name=&amp;quot;palomar&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This does not mean that any point south of Bitkine will produce water. It indicates that the geological and weathering conditions associated with productive basement aquifers occur more frequently there in the available dataset.&lt;br /&gt;
&lt;br /&gt;
The relationship with the massif is also hydrologically significant. Surface runoff from Mont Guéra is channelled toward lower terrain north of the mountains. Low areas, seasonal drainage corridors and their margins can therefore receive concentrated recharge.&lt;br /&gt;
&lt;br /&gt;
A potentially favourable setting consists of:&lt;br /&gt;
&lt;br /&gt;
* a catchment draining the massif;&lt;br /&gt;
* a mountain-front or piedmont position;&lt;br /&gt;
* permeable superficial or weathered material;&lt;br /&gt;
* a sufficiently developed weathered basement horizon;&lt;br /&gt;
* an underlying fractured horizon connected to recharge;&lt;br /&gt;
* geophysical characteristics corresponding to an A or A* type structure.&lt;br /&gt;
&lt;br /&gt;
The active centre of a wadi is not necessarily the preferred location for a drinking-water borehole. While it may receive strong recharge, it is also more exposed to flooding and rapid infiltration of microbiological and chemical contamination from surface runoff. A favourable fractured aquifer intercepted from the side of a drainage corridor may provide a better compromise between recharge and sanitary protection.&lt;br /&gt;
&lt;br /&gt;
== Groundwater recharge ==&lt;br /&gt;
&lt;br /&gt;
Recharge is strongly seasonal.&lt;br /&gt;
&lt;br /&gt;
During the rainy season, runoff becomes visible along a dense network of temporary channels draining the Mont Guéra massif. These channels can concentrate water from a catchment considerably larger than the immediate area around a borehole.&lt;br /&gt;
&lt;br /&gt;
The most important recharge may therefore occur during relatively short rainfall events in:&lt;br /&gt;
&lt;br /&gt;
* valleys;&lt;br /&gt;
* wadis and talwegs;&lt;br /&gt;
* piedmont depressions;&lt;br /&gt;
* alluvial deposits;&lt;br /&gt;
* permeable weathered zones;&lt;br /&gt;
* fractures hydraulically connected to these features.&lt;br /&gt;
&lt;br /&gt;
Quantification of recharge remains a major uncertainty. SEVES notes that the sustainability of the groundwater resource around Bitkine cannot yet be determined confidently because long-term piezometric measurements and systematic records of abstraction volumes are lacking.&amp;lt;ref name=&amp;quot;palomar&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Borehole productivity ==&lt;br /&gt;
&lt;br /&gt;
Groundwater development around Bitkine is difficult even after hydrogeophysical prospecting.&lt;br /&gt;
&lt;br /&gt;
The wider Guéra dataset analysed by Palomar shows that among 137 historical boreholes:&lt;br /&gt;
&lt;br /&gt;
* 47% were unsuccessful during drilling and were not equipped;&lt;br /&gt;
* 42% had yields considered too low for connection to a piped drinking-water network;&lt;br /&gt;
* only 11% provided approximately 4 m³/h for 8 hours per day.&amp;lt;ref name=&amp;quot;palomar&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The Bitkine study therefore concludes that a town of this size cannot normally be supplied from one exceptionally productive borehole. A reliable supply is more likely to require a &#039;&#039;&#039;well field consisting of several moderate-yield boreholes&#039;&#039;&#039;.&amp;lt;ref name=&amp;quot;palomar&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Under the REAVIA programme, SEVES and ADES reported a newly developed borehole at Bitkine producing approximately &#039;&#039;&#039;6 m³/h&#039;&#039;&#039;. Several unsuccessful drillings were also encountered during the same groundwater-development work.&amp;lt;ref name=&amp;quot;reavia&amp;quot;&amp;gt;[https://www.asso-seves.org/tchad-mobilisation-de-la-ressource-en-eau-pour-les-services-d-eau-potable-de.html SEVES, &#039;&#039;Mobilisation de la ressource en eau pour les services d&#039;eau potable de Bitkine et Koubo Adougoul dans la province du Guéra — REAVIA&#039;&#039;.]&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Water quality and salinity ==&lt;br /&gt;
&lt;br /&gt;
Water quality varies locally around Bitkine.&lt;br /&gt;
&lt;br /&gt;
AOWIS field observations include both potable and noticeably saline groundwater sources within the same general area. Saline water is in some cases unsuitable for drinking while remaining usable for washing, construction or other non-potable purposes.&lt;br /&gt;
&lt;br /&gt;
This spatial variability is compatible with the fractured-basement aquifer system. Nearby boreholes may intersect different fracture networks with different recharge, residence times and geochemical histories.&lt;br /&gt;
&lt;br /&gt;
Regional geochemical work by Nouradine was concentrated primarily around Mongo rather than Bitkine. It therefore provides a useful conceptual framework but should not be used as direct evidence for the chemistry of individual Bitkine boreholes.&lt;br /&gt;
&lt;br /&gt;
The Guéra data show that deeper fractured groundwater is generally more mineralised than shallow groundwater. Prolonged water-rock interaction with silicate minerals can increase dissolved sodium, calcium, magnesium, potassium and bicarbonate. Older or poorly renewed fracture water may therefore become more mineralised than groundwater receiving frequent recent recharge.&amp;lt;ref name=&amp;quot;nouradine&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This provides one possible explanation for local differences around Bitkine, but the origin of the saline water has &#039;&#039;&#039;not yet been established by adequate local chemical analysis&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
In particular, water described locally as &#039;&#039;salty&#039;&#039; should not automatically be assumed to be sodium-chloride water. Determining the actual hydrochemical type requires analysis of the major dissolved ions.&lt;br /&gt;
&lt;br /&gt;
Useful measurements include:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Measurement&lt;br /&gt;
! Purpose&lt;br /&gt;
|-&lt;br /&gt;
| Electrical conductivity (EC)&lt;br /&gt;
| Rapid indication of total ionic mineralisation&lt;br /&gt;
|-&lt;br /&gt;
| Temperature&lt;br /&gt;
| Required for comparable conductivity measurements&lt;br /&gt;
|-&lt;br /&gt;
| pH&lt;br /&gt;
| General water chemistry&lt;br /&gt;
|-&lt;br /&gt;
| TDS&lt;br /&gt;
| Approximate total dissolved mineral content&lt;br /&gt;
|-&lt;br /&gt;
| Na, K&lt;br /&gt;
| Major alkali cations&lt;br /&gt;
|-&lt;br /&gt;
| Ca, Mg&lt;br /&gt;
| Hardness and hydrochemical classification&lt;br /&gt;
|-&lt;br /&gt;
| Cl&lt;br /&gt;
| Identification of chloride-rich salinity&lt;br /&gt;
|-&lt;br /&gt;
| SO&amp;lt;sub&amp;gt;4&amp;lt;/sub&amp;gt;&lt;br /&gt;
| Sulfate contribution&lt;br /&gt;
|-&lt;br /&gt;
| HCO&amp;lt;sub&amp;gt;3&amp;lt;/sub&amp;gt; / alkalinity&lt;br /&gt;
| Bicarbonate-dominated basement groundwater&lt;br /&gt;
|-&lt;br /&gt;
| NO&amp;lt;sub&amp;gt;3&amp;lt;/sub&amp;gt;&lt;br /&gt;
| Important indicator of surface contamination&lt;br /&gt;
|-&lt;br /&gt;
| F&lt;br /&gt;
| Drinking-water quality&lt;br /&gt;
|-&lt;br /&gt;
| Fe, Mn&lt;br /&gt;
| Common groundwater quality problems&lt;br /&gt;
|-&lt;br /&gt;
| Microbiological analysis&lt;br /&gt;
| Required to establish drinking-water safety&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Electrical conductivity should preferably be measured directly in &#039;&#039;&#039;µS/cm&#039;&#039;&#039; rather than relying only on the calculated &#039;&#039;ppm&#039;&#039; value displayed by inexpensive TDS meters.&lt;br /&gt;
&lt;br /&gt;
== Seasonal behaviour ==&lt;br /&gt;
&lt;br /&gt;
Local groundwater availability changes substantially through the year.&lt;br /&gt;
&lt;br /&gt;
AOWIS field observations indicate that some potable boreholes can maintain considerably higher yield after the rainy season and decline during the late dry season. Other local wells provide only moderate yields during the March–June period.&lt;br /&gt;
&lt;br /&gt;
This behaviour makes a single short pumping test insufficient for understanding the long-term capacity of a source.&lt;br /&gt;
&lt;br /&gt;
For important water points, monitoring should include:&lt;br /&gt;
&lt;br /&gt;
* pumping rate;&lt;br /&gt;
* pumping duration;&lt;br /&gt;
* static and pumping water level;&lt;br /&gt;
* electrical conductivity;&lt;br /&gt;
* temperature;&lt;br /&gt;
* seasonal changes in yield.&lt;br /&gt;
&lt;br /&gt;
For saline or mildly saline boreholes, EC should also be recorded during prolonged pumping. In a fractured aquifer, water quality can change during pumping as the relative contribution of different fractures changes. A declining EC may indicate displacement of stagnant or more mineralised water by a fresher source, while an increasing EC may indicate recruitment of a more mineralised fracture. Such behaviour must be demonstrated by measurement rather than assumed.&lt;br /&gt;
&lt;br /&gt;
== Existing water services ==&lt;br /&gt;
&lt;br /&gt;
Since 2022, &#039;&#039;&#039;SEVES&#039;&#039;&#039; and its Chadian partner &#039;&#039;&#039;ADES&#039;&#039;&#039; have been supporting the water services of Bitkine and surrounding smaller centres.&amp;lt;ref name=&amp;quot;palomar&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
SEVES reports that existing services frequently experience interruptions or are unable to meet demand, particularly during the dry season, largely because insufficient groundwater has been successfully mobilised.&amp;lt;ref name=&amp;quot;palomar&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The REAVIA programme combines groundwater prospecting and drilling with support for the organisation and long-term operation of the water services. Work is conducted with the regional delegation of the Ministry responsible for water and with the Commune of Bitkine.&amp;lt;ref name=&amp;quot;seves&amp;quot;&amp;gt;[https://www.asso-seves.org/implantation-des-forages-dans-la-province-du-guera-autchad.html SEVES, &#039;&#039;Implantation des forages dans la province du Guéra au Tchad&#039;&#039;, 2024.]&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== AOWIS field work ==&lt;br /&gt;
&lt;br /&gt;
AOWIS work around Bitkine is currently focused on building a more detailed local picture of the available groundwater resources.&lt;br /&gt;
&lt;br /&gt;
Local work includes:&lt;br /&gt;
&lt;br /&gt;
* identifying existing boreholes and wells;&lt;br /&gt;
* recording GPS position;&lt;br /&gt;
* recording dry- and wet-season yield;&lt;br /&gt;
* distinguishing potable and saline sources;&lt;br /&gt;
* measuring electrical conductivity and other water-quality parameters;&lt;br /&gt;
* documenting borehole depth where available;&lt;br /&gt;
* recording ownership and willingness to participate in a shared water-supply system;&lt;br /&gt;
* investigating additional groundwater sources;&lt;br /&gt;
* evaluating storage, pumping, treatment and distribution options.&lt;br /&gt;
&lt;br /&gt;
Several private well owners have agreed to cooperate in the local water-supply work. Field observations already show that useful groundwater resources are distributed across multiple relatively modest sources rather than one known large aquifer.&lt;br /&gt;
&lt;br /&gt;
The immediate objective is therefore not only to find new water, but also to understand how the existing sources are hydraulically and chemically related and how they could be used together sustainably.&lt;br /&gt;
&lt;br /&gt;
== Mont Doli investigation area ==&lt;br /&gt;
&lt;br /&gt;
AOWIS has identified a &#039;&#039;&#039;preliminary groundwater investigation area east of Mont Doli&#039;&#039;&#039; at approximately:&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;11.948855° N, 18.187213° E&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
This location is a &#039;&#039;&#039;prospecting hypothesis only&#039;&#039;&#039;. No successful borehole at this point is currently known to AOWIS.&lt;br /&gt;
&lt;br /&gt;
The site was selected from topography and seasonal satellite imagery. It lies north of the massif in terrain crossed by seasonal drainage from the mountains.&lt;br /&gt;
&lt;br /&gt;
Dry-season imagery shows the mountain-front morphology and drainage depressions. Rainy-season imagery makes the active drainage system considerably clearer and shows runoff being concentrated from the high ground toward larger channels farther north.&lt;br /&gt;
&lt;br /&gt;
The broader setting is consistent with several characteristics considered favourable for groundwater prospecting:&lt;br /&gt;
&lt;br /&gt;
* proximity to the Mont Guéra catchment;&lt;br /&gt;
* concentrated seasonal runoff;&lt;br /&gt;
* relatively low mountain-front terrain;&lt;br /&gt;
* potential recharge through drainage and piedmont deposits;&lt;br /&gt;
* location in the southern Bitkine sector where A and A* hydrogeophysical models are more common.&lt;br /&gt;
&lt;br /&gt;
These observations do not establish the presence, depth, yield or quality of groundwater at the candidate point.&lt;br /&gt;
&lt;br /&gt;
Before drilling, the site and the adjacent drainage corridor should be investigated geophysically.&lt;br /&gt;
&lt;br /&gt;
A useful survey would include ERT profiles crossing:&lt;br /&gt;
&lt;br /&gt;
# the principal seasonal drainage route;&lt;br /&gt;
# its flanks;&lt;br /&gt;
# the original candidate point.&lt;br /&gt;
&lt;br /&gt;
This would allow comparison of the weathered and fractured basement beneath each setting.&lt;br /&gt;
&lt;br /&gt;
For a potable-water borehole, a productive target on the &#039;&#039;&#039;flank of the principal drainage corridor&#039;&#039;&#039; may be preferable to a location directly within the active channel. This could retain hydraulic connection to the recharge area while reducing exposure to direct floodwater, erosion and surface contamination.&lt;br /&gt;
&lt;br /&gt;
Any final drilling location should be selected from the combined evidence of:&lt;br /&gt;
&lt;br /&gt;
* geology;&lt;br /&gt;
* topography;&lt;br /&gt;
* drainage;&lt;br /&gt;
* ERT;&lt;br /&gt;
* nearby borehole results;&lt;br /&gt;
* nearby groundwater chemistry;&lt;br /&gt;
* sanitary risks.&lt;br /&gt;
&lt;br /&gt;
== Research priorities ==&lt;br /&gt;
&lt;br /&gt;
The main remaining uncertainties around Bitkine concern both &#039;&#039;&#039;quantity&#039;&#039;&#039; and &#039;&#039;&#039;quality&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
A useful local groundwater programme should establish a consistent dataset for each important water point containing:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Parameter&lt;br /&gt;
! Unit / information&lt;br /&gt;
|-&lt;br /&gt;
| Position&lt;br /&gt;
| latitude / longitude&lt;br /&gt;
|-&lt;br /&gt;
| Borehole depth&lt;br /&gt;
| m&lt;br /&gt;
|-&lt;br /&gt;
| Static water level&lt;br /&gt;
| m&lt;br /&gt;
|-&lt;br /&gt;
| Pumping water level&lt;br /&gt;
| m&lt;br /&gt;
|-&lt;br /&gt;
| Pumping rate&lt;br /&gt;
| m³/h&lt;br /&gt;
|-&lt;br /&gt;
| Seasonal yield&lt;br /&gt;
| m³/h&lt;br /&gt;
|-&lt;br /&gt;
| Electrical conductivity&lt;br /&gt;
| µS/cm&lt;br /&gt;
|-&lt;br /&gt;
| Temperature&lt;br /&gt;
| °C&lt;br /&gt;
|-&lt;br /&gt;
| pH&lt;br /&gt;
| —&lt;br /&gt;
|-&lt;br /&gt;
| Potability / use&lt;br /&gt;
| drinking, washing, irrigation, construction, etc.&lt;br /&gt;
|-&lt;br /&gt;
| Major-ion chemistry&lt;br /&gt;
| mg/L&lt;br /&gt;
|-&lt;br /&gt;
| Microbiology&lt;br /&gt;
| laboratory result&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Repeated measurements are particularly important. A single yield or EC value does not describe the long-term behaviour of a fractured basement borehole.&lt;br /&gt;
&lt;br /&gt;
Once sufficient observations are available, the combination of groundwater chemistry, borehole performance, ERT interpretation and terrain analysis should allow the local water sources to be grouped into different hydrogeological systems.&lt;br /&gt;
&lt;br /&gt;
== Hydrogeological research ==&lt;br /&gt;
&lt;br /&gt;
The principal recent technical sources for the Bitkine groundwater system are the regional doctoral work of Haroun Nouradine and the later Bitkine-focused study by Pierre Palomar.&lt;br /&gt;
&lt;br /&gt;
=== Nouradine 2023 ===&lt;br /&gt;
&lt;br /&gt;
Nouradine developed a regional conceptual model for the crystalline-basement aquifers of Guéra using geological, hydrogeological, geophysical, geochemical and isotopic information.&lt;br /&gt;
&lt;br /&gt;
Although the detailed geochemical investigation concentrated primarily around Mongo, the work provides the principal regional framework for understanding groundwater occurrence, recharge, productivity and mineralisation.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Full thesis:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:[https://nextcloud.aowis.org/s/tCJgPAa2G6Lws83 &#039;&#039;Évaluation des ressources en eau dans les aquifères de socle dans la région du Guéra (Tchad)&#039;&#039;, Haroun Nouradine, 2023]&lt;br /&gt;
&lt;br /&gt;
=== Palomar / SEVES 2024 ===&lt;br /&gt;
&lt;br /&gt;
Palomar&#039;s work specifically extends this approach to the Bitkine area.&lt;br /&gt;
&lt;br /&gt;
The study:&lt;br /&gt;
&lt;br /&gt;
* reinterprets 61 existing ERT sites;&lt;br /&gt;
* compares the geophysics with drilling results;&lt;br /&gt;
* develops a local hydrogeophysical classification;&lt;br /&gt;
* identifies characteristics associated with productive boreholes;&lt;br /&gt;
* demonstrates a geographic difference between the northern and southern Bitkine sectors;&lt;br /&gt;
* gives practical recommendations for future groundwater prospecting.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Full report:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:[https://nextcloud.aowis.org/s/j7Gy7bMrFr5Gsew &#039;&#039;Conceptualisation hydrogéologique et recommandations pour les prospections géophysiques et l&#039;implantation des forages — Province du Guéra, Tchad&#039;&#039;, Pierre Palomar / SEVES, 2024]&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== External resources ==&lt;br /&gt;
&lt;br /&gt;
* [[Regions:Chad/Guéra|Guéra regional overview]]&lt;br /&gt;
* [https://nextcloud.aowis.org/s/tCJgPAa2G6Lws83 Nouradine 2023 doctoral thesis — AOWIS-hosted PDF]&lt;br /&gt;
* [https://nextcloud.aowis.org/s/j7Gy7bMrFr5Gsew Palomar / SEVES Bitkine hydrogeology report — AOWIS-hosted PDF]&lt;br /&gt;
* [https://doi.org/10.1007/s10040-024-02766-2 Nouradine et al. 2024 — Hydrogeology Journal]&lt;br /&gt;
* [https://www.asso-seves.org/implantation-des-forages-dans-la-province-du-guera-autchad.html SEVES — groundwater prospecting in Guéra]&lt;br /&gt;
* [https://www.asso-seves.org/tchad-mobilisation-de-la-ressource-en-eau-pour-les-services-d-eau-potable-de.html SEVES — REAVIA groundwater development at Bitkine and Koubo Adougoul]&lt;br /&gt;
&lt;br /&gt;
[[Category:Chad]]&lt;br /&gt;
[[Category:Guéra]]&lt;br /&gt;
[[Category:Bitkine]]&lt;br /&gt;
[[Category:Groundwater]]&lt;br /&gt;
[[Category:Hydrogeology]]&lt;br /&gt;
[[Category:Water supply]]&lt;/div&gt;</summary>
		<author><name>Samuel</name></author>
	</entry>
	<entry>
		<id>https://aowis.org/index.php?title=Regions:Main_Page&amp;diff=746</id>
		<title>Regions:Main Page</title>
		<link rel="alternate" type="text/html" href="https://aowis.org/index.php?title=Regions:Main_Page&amp;diff=746"/>
		<updated>2026-09-20T22:27:41Z</updated>

		<summary type="html">&lt;p&gt;Samuel: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{AI-Generated&lt;br /&gt;
 | tool = ChatGPT&lt;br /&gt;
 | date = 2026-09-18&lt;br /&gt;
 | scope = full page&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;Regions&#039;&#039;&#039; namespace documents the geographic, environmental, hydrological, and infrastructural conditions of places relevant to AOWIS.&lt;br /&gt;
&lt;br /&gt;
Water systems cannot be planned independently of their physical setting. Climate, topography, geology, groundwater conditions, water quality, settlement structure, existing infrastructure, energy supply, and logistics all influence how water can be sourced, treated, stored, distributed, monitored, and operated.&lt;br /&gt;
&lt;br /&gt;
Regional pages bring this information together as practical background for planning and engineering.&lt;br /&gt;
&lt;br /&gt;
== Regional knowledge ==&lt;br /&gt;
&lt;br /&gt;
Information documented here might include aspects like:&lt;br /&gt;
&lt;br /&gt;
* geography and topography;&lt;br /&gt;
* climate and seasonal rainfall;&lt;br /&gt;
* geology and hydrogeology;&lt;br /&gt;
* aquifers and groundwater occurrence;&lt;br /&gt;
* groundwater levels and borehole yields;&lt;br /&gt;
* groundwater and surface-water quality;&lt;br /&gt;
* salinity and mineralisation;&lt;br /&gt;
* rivers, wadis, lakes, reservoirs, and other water resources;&lt;br /&gt;
* settlements and population distribution;&lt;br /&gt;
* existing water-supply and sanitation infrastructure;&lt;br /&gt;
* energy, transport, communications, and logistics;&lt;br /&gt;
* hydrogeological, geophysical, and water-quality studies;&lt;br /&gt;
* field observations and measurements.&lt;br /&gt;
&lt;br /&gt;
Regional conditions may vary substantially over short distances. This is particularly important in fractured-rock aquifers, where nearby boreholes can differ greatly in depth, yield, recharge, and water quality.&lt;br /&gt;
&lt;br /&gt;
Measurements and observations should therefore be associated with their actual location and source wherever possible.&lt;br /&gt;
&lt;br /&gt;
== Chad ==&lt;br /&gt;
&lt;br /&gt;
AOWIS work in Chad currently focuses particularly on the [[Regions:Chad/Guéra|Guéra region]] in central Chad.&lt;br /&gt;
&lt;br /&gt;
The area includes crystalline basement aquifers, strongly seasonal rainfall, substantial dependence on groundwater, and significant local variation in borehole productivity and water quality.&lt;br /&gt;
&lt;br /&gt;
Current regional documentation includes:&lt;br /&gt;
&lt;br /&gt;
* [[Regions:Chad]]&lt;br /&gt;
* [[Regions:Chad/Guéra]]&lt;br /&gt;
* [[Regions:Chad/Guéra/Bitkine]]&lt;br /&gt;
&lt;br /&gt;
== Related AOWIS documentation ==&lt;br /&gt;
&lt;br /&gt;
Regional conditions provide the physical context for the systems described elsewhere in AOWIS.&lt;br /&gt;
&lt;br /&gt;
* [[Infrastructure:Main_Page|Infrastructure]] documents water infrastructure and treatment technologies.&lt;br /&gt;
* [[Reference:Main_Page|Reference]] documents concrete implementations and deployments.&lt;br /&gt;
* [[Measurement:Main_Page|Measurement]] defines quantities, units, and measurement conventions.&lt;br /&gt;
* [[Databases:Main_Page|Databases]] documents structured AOWIS knowledge bases.&lt;br /&gt;
* [[External:Main_Page|External]] documents relevant external projects, technologies, standards, and organisations.&lt;br /&gt;
&lt;br /&gt;
[[Category:AOWIS]]&lt;/div&gt;</summary>
		<author><name>Samuel</name></author>
	</entry>
	<entry>
		<id>https://aowis.org/index.php?title=Regions:Main_Page&amp;diff=745</id>
		<title>Regions:Main Page</title>
		<link rel="alternate" type="text/html" href="https://aowis.org/index.php?title=Regions:Main_Page&amp;diff=745"/>
		<updated>2026-09-20T22:27:20Z</updated>

		<summary type="html">&lt;p&gt;Samuel: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{DISPLAYTITLE:Regions}}&lt;br /&gt;
&lt;br /&gt;
{{AI-Generated&lt;br /&gt;
 | tool = ChatGPT&lt;br /&gt;
 | date = 2026-09-18&lt;br /&gt;
 | scope = full page&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;Regions&#039;&#039;&#039; namespace documents the geographic, environmental, hydrological, and infrastructural conditions of places relevant to AOWIS.&lt;br /&gt;
&lt;br /&gt;
Water systems cannot be planned independently of their physical setting. Climate, topography, geology, groundwater conditions, water quality, settlement structure, existing infrastructure, energy supply, and logistics all influence how water can be sourced, treated, stored, distributed, monitored, and operated.&lt;br /&gt;
&lt;br /&gt;
Regional pages bring this information together as practical background for planning and engineering.&lt;br /&gt;
&lt;br /&gt;
== Regional knowledge ==&lt;br /&gt;
&lt;br /&gt;
Information documented here might include aspects like:&lt;br /&gt;
&lt;br /&gt;
* geography and topography;&lt;br /&gt;
* climate and seasonal rainfall;&lt;br /&gt;
* geology and hydrogeology;&lt;br /&gt;
* aquifers and groundwater occurrence;&lt;br /&gt;
* groundwater levels and borehole yields;&lt;br /&gt;
* groundwater and surface-water quality;&lt;br /&gt;
* salinity and mineralisation;&lt;br /&gt;
* rivers, wadis, lakes, reservoirs, and other water resources;&lt;br /&gt;
* settlements and population distribution;&lt;br /&gt;
* existing water-supply and sanitation infrastructure;&lt;br /&gt;
* energy, transport, communications, and logistics;&lt;br /&gt;
* hydrogeological, geophysical, and water-quality studies;&lt;br /&gt;
* field observations and measurements.&lt;br /&gt;
&lt;br /&gt;
Regional conditions may vary substantially over short distances. This is particularly important in fractured-rock aquifers, where nearby boreholes can differ greatly in depth, yield, recharge, and water quality.&lt;br /&gt;
&lt;br /&gt;
Measurements and observations should therefore be associated with their actual location and source wherever possible.&lt;br /&gt;
&lt;br /&gt;
== Chad ==&lt;br /&gt;
&lt;br /&gt;
AOWIS work in Chad currently focuses particularly on the [[Regions:Chad/Guéra|Guéra region]] in central Chad.&lt;br /&gt;
&lt;br /&gt;
The area includes crystalline basement aquifers, strongly seasonal rainfall, substantial dependence on groundwater, and significant local variation in borehole productivity and water quality.&lt;br /&gt;
&lt;br /&gt;
Current regional documentation includes:&lt;br /&gt;
&lt;br /&gt;
* [[Regions:Chad]]&lt;br /&gt;
* [[Regions:Chad/Guéra]]&lt;br /&gt;
* [[Regions:Chad/Guéra/Bitkine]]&lt;br /&gt;
&lt;br /&gt;
== Related AOWIS documentation ==&lt;br /&gt;
&lt;br /&gt;
Regional conditions provide the physical context for the systems described elsewhere in AOWIS.&lt;br /&gt;
&lt;br /&gt;
* [[Infrastructure:Main_Page|Infrastructure]] documents water infrastructure and treatment technologies.&lt;br /&gt;
* [[Reference:Main_Page|Reference]] documents concrete implementations and deployments.&lt;br /&gt;
* [[Measurement:Main_Page|Measurement]] defines quantities, units, and measurement conventions.&lt;br /&gt;
* [[Databases:Main_Page|Databases]] documents structured AOWIS knowledge bases.&lt;br /&gt;
* [[External:Main_Page|External]] documents relevant external projects, technologies, standards, and organisations.&lt;br /&gt;
&lt;br /&gt;
[[Category:AOWIS]]&lt;/div&gt;</summary>
		<author><name>Samuel</name></author>
	</entry>
	<entry>
		<id>https://aowis.org/index.php?title=Regions:Main_Page&amp;diff=744</id>
		<title>Regions:Main Page</title>
		<link rel="alternate" type="text/html" href="https://aowis.org/index.php?title=Regions:Main_Page&amp;diff=744"/>
		<updated>2026-09-18T05:35:27Z</updated>

		<summary type="html">&lt;p&gt;Samuel: /* Regional knowledge */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{DISPLAYTITLE:Regions}}&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;Regions&#039;&#039;&#039; namespace documents the geographic, environmental, hydrological, and infrastructural conditions of places relevant to AOWIS.&lt;br /&gt;
&lt;br /&gt;
Water systems cannot be planned independently of their physical setting. Climate, topography, geology, groundwater conditions, water quality, settlement structure, existing infrastructure, energy supply, and logistics all influence how water can be sourced, treated, stored, distributed, monitored, and operated.&lt;br /&gt;
&lt;br /&gt;
Regional pages bring this information together as practical background for planning and engineering.&lt;br /&gt;
&lt;br /&gt;
== Regional knowledge ==&lt;br /&gt;
&lt;br /&gt;
Information documented here might include aspects like:&lt;br /&gt;
&lt;br /&gt;
* geography and topography;&lt;br /&gt;
* climate and seasonal rainfall;&lt;br /&gt;
* geology and hydrogeology;&lt;br /&gt;
* aquifers and groundwater occurrence;&lt;br /&gt;
* groundwater levels and borehole yields;&lt;br /&gt;
* groundwater and surface-water quality;&lt;br /&gt;
* salinity and mineralisation;&lt;br /&gt;
* rivers, wadis, lakes, reservoirs, and other water resources;&lt;br /&gt;
* settlements and population distribution;&lt;br /&gt;
* existing water-supply and sanitation infrastructure;&lt;br /&gt;
* energy, transport, communications, and logistics;&lt;br /&gt;
* hydrogeological, geophysical, and water-quality studies;&lt;br /&gt;
* field observations and measurements.&lt;br /&gt;
&lt;br /&gt;
Regional conditions may vary substantially over short distances. This is particularly important in fractured-rock aquifers, where nearby boreholes can differ greatly in depth, yield, recharge, and water quality.&lt;br /&gt;
&lt;br /&gt;
Measurements and observations should therefore be associated with their actual location and source wherever possible.&lt;br /&gt;
&lt;br /&gt;
== Chad ==&lt;br /&gt;
&lt;br /&gt;
AOWIS work in Chad currently focuses particularly on the [[Regions:Chad/Guéra|Guéra region]] in central Chad.&lt;br /&gt;
&lt;br /&gt;
The area includes crystalline basement aquifers, strongly seasonal rainfall, substantial dependence on groundwater, and significant local variation in borehole productivity and water quality.&lt;br /&gt;
&lt;br /&gt;
Current regional documentation includes:&lt;br /&gt;
&lt;br /&gt;
* [[Regions:Chad]]&lt;br /&gt;
* [[Regions:Chad/Guéra]]&lt;br /&gt;
* [[Regions:Chad/Guéra/Bitkine]]&lt;br /&gt;
&lt;br /&gt;
== Related AOWIS documentation ==&lt;br /&gt;
&lt;br /&gt;
Regional conditions provide the physical context for the systems described elsewhere in AOWIS.&lt;br /&gt;
&lt;br /&gt;
* [[Infrastructure:Main_Page|Infrastructure]] documents water infrastructure and treatment technologies.&lt;br /&gt;
* [[Reference:Main_Page|Reference]] documents concrete implementations and deployments.&lt;br /&gt;
* [[Measurement:Main_Page|Measurement]] defines quantities, units, and measurement conventions.&lt;br /&gt;
* [[Databases:Main_Page|Databases]] documents structured AOWIS knowledge bases.&lt;br /&gt;
* [[External:Main_Page|External]] documents relevant external projects, technologies, standards, and organisations.&lt;br /&gt;
&lt;br /&gt;
[[Category:AOWIS]]&lt;/div&gt;</summary>
		<author><name>Samuel</name></author>
	</entry>
	<entry>
		<id>https://aowis.org/index.php?title=Regions:Main_Page&amp;diff=743</id>
		<title>Regions:Main Page</title>
		<link rel="alternate" type="text/html" href="https://aowis.org/index.php?title=Regions:Main_Page&amp;diff=743"/>
		<updated>2026-09-18T05:31:23Z</updated>

		<summary type="html">&lt;p&gt;Samuel: /* Regional knowledge */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{DISPLAYTITLE:Regions}}&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;Regions&#039;&#039;&#039; namespace documents the geographic, environmental, hydrological, and infrastructural conditions of places relevant to AOWIS.&lt;br /&gt;
&lt;br /&gt;
Water systems cannot be planned independently of their physical setting. Climate, topography, geology, groundwater conditions, water quality, settlement structure, existing infrastructure, energy supply, and logistics all influence how water can be sourced, treated, stored, distributed, monitored, and operated.&lt;br /&gt;
&lt;br /&gt;
Regional pages bring this information together as practical background for planning and engineering.&lt;br /&gt;
&lt;br /&gt;
== Regional knowledge ==&lt;br /&gt;
&lt;br /&gt;
Information documented here might include:&lt;br /&gt;
&lt;br /&gt;
* geography and topography;&lt;br /&gt;
* climate and seasonal rainfall;&lt;br /&gt;
* geology and hydrogeology;&lt;br /&gt;
* aquifers and groundwater occurrence;&lt;br /&gt;
* groundwater levels and borehole yields;&lt;br /&gt;
* groundwater and surface-water quality;&lt;br /&gt;
* salinity and mineralisation;&lt;br /&gt;
* rivers, wadis, lakes, reservoirs, and other water resources;&lt;br /&gt;
* settlements and population distribution;&lt;br /&gt;
* existing water-supply and sanitation infrastructure;&lt;br /&gt;
* energy, transport, communications, and logistics;&lt;br /&gt;
* hydrogeological, geophysical, and water-quality studies;&lt;br /&gt;
* field observations and measurements.&lt;br /&gt;
&lt;br /&gt;
Regional conditions may vary substantially over short distances. This is particularly important in fractured-rock aquifers, where nearby boreholes can differ greatly in depth, yield, recharge, and water quality.&lt;br /&gt;
&lt;br /&gt;
Measurements and observations should therefore be associated with their actual location and source wherever possible.&lt;br /&gt;
&lt;br /&gt;
== Chad ==&lt;br /&gt;
&lt;br /&gt;
AOWIS work in Chad currently focuses particularly on the [[Regions:Chad/Guéra|Guéra region]] in central Chad.&lt;br /&gt;
&lt;br /&gt;
The area includes crystalline basement aquifers, strongly seasonal rainfall, substantial dependence on groundwater, and significant local variation in borehole productivity and water quality.&lt;br /&gt;
&lt;br /&gt;
Current regional documentation includes:&lt;br /&gt;
&lt;br /&gt;
* [[Regions:Chad]]&lt;br /&gt;
* [[Regions:Chad/Guéra]]&lt;br /&gt;
* [[Regions:Chad/Guéra/Bitkine]]&lt;br /&gt;
&lt;br /&gt;
== Related AOWIS documentation ==&lt;br /&gt;
&lt;br /&gt;
Regional conditions provide the physical context for the systems described elsewhere in AOWIS.&lt;br /&gt;
&lt;br /&gt;
* [[Infrastructure:Main_Page|Infrastructure]] documents water infrastructure and treatment technologies.&lt;br /&gt;
* [[Reference:Main_Page|Reference]] documents concrete implementations and deployments.&lt;br /&gt;
* [[Measurement:Main_Page|Measurement]] defines quantities, units, and measurement conventions.&lt;br /&gt;
* [[Databases:Main_Page|Databases]] documents structured AOWIS knowledge bases.&lt;br /&gt;
* [[External:Main_Page|External]] documents relevant external projects, technologies, standards, and organisations.&lt;br /&gt;
&lt;br /&gt;
[[Category:AOWIS]]&lt;/div&gt;</summary>
		<author><name>Samuel</name></author>
	</entry>
	<entry>
		<id>https://aowis.org/index.php?title=Regions:Chad/Gu%C3%A9ra&amp;diff=742</id>
		<title>Regions:Chad/Guéra</title>
		<link rel="alternate" type="text/html" href="https://aowis.org/index.php?title=Regions:Chad/Gu%C3%A9ra&amp;diff=742"/>
		<updated>2026-09-18T00:43:24Z</updated>

		<summary type="html">&lt;p&gt;Samuel: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
{{AI-Generated&lt;br /&gt;
 | tool = ChatGPT&lt;br /&gt;
 | date = 2026-09-18&lt;br /&gt;
 | scope = full page&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Guéra&#039;&#039;&#039; is a province in central [[Regions:Chad|Chad]]. Its provincial capital is &#039;&#039;&#039;Mongo&#039;&#039;&#039;. The province includes the town of [[Regions:Chad/Guéra/Bitkine|Bitkine]], where AOWIS is currently involved in local water-supply work and groundwater assessment.&lt;br /&gt;
&lt;br /&gt;
Guéra lies across the transition from the Sahelian zone in the north to more humid Sudanian conditions in the south. Its mountainous crystalline basement, strongly seasonal rainfall, lack of permanent rivers, and highly variable groundwater productivity make water supply a major engineering challenge.&lt;br /&gt;
&lt;br /&gt;
== Geography and administration ==&lt;br /&gt;
&lt;br /&gt;
The 2022 &#039;&#039;Schéma Provincial d&#039;Aménagement du Territoire du Guéra&#039;&#039; gives an area of approximately &#039;&#039;&#039;61,279 km²&#039;&#039;&#039;. Following the 2021 administrative restructuring, the province consists of five departments:&amp;lt;ref name=&amp;quot;spat&amp;quot;&amp;gt;[https://apef-conservation.org/ressources-documentaires/ APEF / Republic of Chad, &#039;&#039;Schéma Provincial d&#039;Aménagement du Territoire du Guéra 2022–2032&#039;&#039;, 2022.]&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Guéra&#039;&#039;&#039;, capital Mongo;&lt;br /&gt;
* &#039;&#039;&#039;Abtouyour&#039;&#039;&#039;, capital [[Regions:Chad/Guéra/Bitkine|Bitkine]];&lt;br /&gt;
* &#039;&#039;&#039;Mangalmé&#039;&#039;&#039;, capital Mangalmé;&lt;br /&gt;
* &#039;&#039;&#039;Barh Signaka&#039;&#039;&#039;, capital Chinguil;&lt;br /&gt;
* &#039;&#039;&#039;Garada&#039;&#039;&#039;, capital Melfi.&lt;br /&gt;
&lt;br /&gt;
The same planning document gives a projected population of &#039;&#039;&#039;635,822 inhabitants in 2020&#039;&#039;&#039;, based on the 2009 national census and subsequent INSEED projections. The population is concentrated particularly in Guéra and Abtouyour.&amp;lt;ref name=&amp;quot;spat&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Terrain and surface water ==&lt;br /&gt;
&lt;br /&gt;
The landscape is dominated by plains interrupted by large granitic massifs, inselbergs, plateaus, and exposed bedrock.&lt;br /&gt;
&lt;br /&gt;
The central Chadian massif reaches some of its highest elevations in Guéra. The Mont Guéra reaches approximately &#039;&#039;&#039;1,613 m&#039;&#039;&#039; in the Bitkine area, while Mont Guédi east of Mongo reaches approximately &#039;&#039;&#039;1,506 m&#039;&#039;&#039;.&amp;lt;ref name=&amp;quot;spat&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
There are no major permanent rivers across most of the province. Surface drainage is dominated by seasonal watercourses, locally known as &#039;&#039;&#039;barhs&#039;&#039;&#039; or &#039;&#039;&#039;ouadis&#039;&#039;&#039;, which flow during the rainy season and may retain water temporarily in depressions and ponds.&lt;br /&gt;
&lt;br /&gt;
Seasonal streams draining the Guéra massif include the Bolong, Bang-Bang, Zilla, Zerzer and Melmele systems. Water from some northern catchments ultimately contributes toward Lake Fitri.&amp;lt;ref name=&amp;quot;spat&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Surface-water availability therefore changes strongly between the rainy and dry seasons, increasing dependence on groundwater for permanent water supply.&lt;br /&gt;
&lt;br /&gt;
== Climate ==&lt;br /&gt;
&lt;br /&gt;
Guéra spans several climatic zones. The north is predominantly Sahelian, the centre is Sahelo-Sudanian, and the southern part of the province approaches Sudanian conditions.&lt;br /&gt;
&lt;br /&gt;
The main seasons are:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;rainy season:&#039;&#039;&#039; approximately May to September;&lt;br /&gt;
* &#039;&#039;&#039;dry season:&#039;&#039;&#039; approximately October to April.&lt;br /&gt;
&lt;br /&gt;
July and August account for a large fraction of annual rainfall in hydrogeological studies of the central and northern part of the province.&amp;lt;ref name=&amp;quot;palomar&amp;quot;&amp;gt;[https://nextcloud.aowis.org/s/j7Gy7bMrFr5Gsew Pierre Palomar, &#039;&#039;Conceptualisation hydrogéologique et recommandations pour les prospections géophysiques et l&#039;implantation des forages — Province du Guéra, Tchad&#039;&#039;, SEVES, 2024.]&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The provincial planning document reports annual precipitation increasing broadly from around &#039;&#039;&#039;800 mm in the north to 1,100 mm in the south&#039;&#039;&#039;. Hydrogeological studies covering more restricted parts of Guéra use lower ranges, including approximately &#039;&#039;&#039;430–867 mm/year&#039;&#039;&#039;. These values refer to different geographic extents and datasets and should not be treated as a single uniform rainfall value for the province.&amp;lt;ref name=&amp;quot;spat&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;palomar&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Mean annual temperature is around &#039;&#039;&#039;28 °C&#039;&#039;&#039;, with high temperatures and long dry periods contributing to evaporation, drying of seasonal ponds, and strong seasonal pressure on water supplies.&amp;lt;ref name=&amp;quot;spat&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Geology ==&lt;br /&gt;
&lt;br /&gt;
Much of the Guéra massif consists of &#039;&#039;&#039;crystalline basement rock&#039;&#039;&#039;. Nouradine&#039;s regional hydrogeological work describes the study area as being dominated by granitoids and metamorphic rocks.&amp;lt;ref name=&amp;quot;nouradine&amp;quot;&amp;gt;[https://nextcloud.aowis.org/s/tCJgPAa2G6Lws83 Haroun Nouradine, &#039;&#039;Évaluation des ressources en eau dans les aquifères de socle dans la région du Guéra (Tchad) : combinaison d&#039;approches géologiques, hydrogéologiques, géophysiques, géochimiques et d&#039;apprentissage automatique&#039;&#039;, doctoral thesis, Sorbonne Université, 2023.]&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Around Bitkine, the basement includes:&lt;br /&gt;
&lt;br /&gt;
* granite;&lt;br /&gt;
* biotite granite;&lt;br /&gt;
* diorite;&lt;br /&gt;
* granodiorite;&lt;br /&gt;
* dolerite.&lt;br /&gt;
&lt;br /&gt;
The lithology strongly influences groundwater productivity. Biotite granites can develop permeable weathered and fractured horizons, while alteration of diorites, granodiorites and dolerites can produce larger amounts of clay, reducing infiltration and hydraulic conductivity.&amp;lt;ref name=&amp;quot;palomar&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Hydrogeology ==&lt;br /&gt;
&lt;br /&gt;
Groundwater in Guéra does not occur as one large continuous regional aquifer. The principal groundwater resources are associated with:&lt;br /&gt;
&lt;br /&gt;
* weathered crystalline basement;&lt;br /&gt;
* fractured and fissured bedrock;&lt;br /&gt;
* alluvial deposits;&lt;br /&gt;
* sands and sediments along seasonal drainage systems.&lt;br /&gt;
&lt;br /&gt;
The basement aquifers are therefore &#039;&#039;&#039;heterogeneous and discontinuous&#039;&#039;&#039;. Two boreholes located relatively close to one another can encounter substantially different conditions.&lt;br /&gt;
&lt;br /&gt;
A simplified basement-aquifer structure consists of:&lt;br /&gt;
&lt;br /&gt;
# superficial material and soil;&lt;br /&gt;
# weathered basement, or &#039;&#039;&#039;alterites&#039;&#039;&#039;;&lt;br /&gt;
# a fractured basement horizon;&lt;br /&gt;
# progressively less fractured competent bedrock at greater depth.&lt;br /&gt;
&lt;br /&gt;
The weathered horizon can provide substantial groundwater storage. Hydraulic transmissivity is often associated particularly with the upper fractured basement beneath it.&amp;lt;ref name=&amp;quot;nouradine&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Nouradine&#039;s regional analysis found that important water inflows commonly occur at approximately &#039;&#039;&#039;30–60 m depth&#039;&#039;&#039;. Productivity generally decreases where drilling continues far into relatively unfractured basement.&amp;lt;ref name=&amp;quot;nouradine&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Groundwater occurrence and borehole productivity depend on the combined effects of:&lt;br /&gt;
&lt;br /&gt;
* lithology;&lt;br /&gt;
* thickness and permeability of the weathered zone;&lt;br /&gt;
* development of the fractured horizon;&lt;br /&gt;
* geomorphology;&lt;br /&gt;
* recharge conditions;&lt;br /&gt;
* local drainage;&lt;br /&gt;
* position within the landscape.&lt;br /&gt;
&lt;br /&gt;
Low-lying areas and locations favourable to infiltration and recharge can provide substantially better groundwater conditions than nearby elevated or poorly weathered basement.&lt;br /&gt;
&lt;br /&gt;
== Borehole productivity ==&lt;br /&gt;
&lt;br /&gt;
Obtaining productive boreholes is a major difficulty in Guéra.&lt;br /&gt;
&lt;br /&gt;
Data analysed for boreholes constructed between 2010 and 2016 show that, among &#039;&#039;&#039;137 boreholes&#039;&#039;&#039; considered by the SEVES study:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;47%&#039;&#039;&#039; were unsuccessful during drilling and were not equipped;&lt;br /&gt;
* &#039;&#039;&#039;42%&#039;&#039;&#039; produced too little water for connection to an AEP water-supply network;&lt;br /&gt;
* only &#039;&#039;&#039;11%&#039;&#039;&#039; provided an exploitable yield of approximately &#039;&#039;&#039;4 m³/h for 8 hours per day&#039;&#039;&#039;.&amp;lt;ref name=&amp;quot;palomar&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The broader dataset analysed by Nouradine contains technical information from &#039;&#039;&#039;798 boreholes&#039;&#039;&#039;, together with approximately &#039;&#039;&#039;700 EM34 profiles&#039;&#039;&#039; and &#039;&#039;&#039;592 electrical-resistivity tomography profiles&#039;&#039;&#039;.&amp;lt;ref name=&amp;quot;nouradine&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;article&amp;quot;&amp;gt;[https://doi.org/10.1007/s10040-024-02766-2 H. Nouradine et al., &#039;&#039;Integrating geological, hydrogeological and geophysical data to identify groundwater resources in granitic basement areas (Guéra Massif, Chad)&#039;&#039;, Hydrogeology Journal 32, 759–784, 2024.]&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The mean borehole yield in the analysed basement-aquifer dataset is approximately &#039;&#039;&#039;1 m³/h&#039;&#039;&#039;. More productive boreholes are associated particularly with well-developed weathered and fractured horizons and favourable granite or biotite-granite formations.&amp;lt;ref name=&amp;quot;nouradine&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The difficulty is therefore not simply drilling deep enough. Successful groundwater development requires identifying favourable combinations of geology, weathering, fractures, topography and recharge.&lt;br /&gt;
&lt;br /&gt;
== Groundwater recharge ==&lt;br /&gt;
&lt;br /&gt;
Recharge is closely linked to the short rainy season.&lt;br /&gt;
&lt;br /&gt;
Direct infiltration across exposed or poorly permeable uplands can be limited, while runoff concentrates water in lower terrain, seasonal drainage channels, alluvial deposits and favourable fractured zones.&lt;br /&gt;
&lt;br /&gt;
The strongly seasonal rainfall regime means groundwater recharge can vary substantially between years. Quantifying long-term recharge remains an important uncertainty for sustainable groundwater development in Guéra.&amp;lt;ref name=&amp;quot;palomar&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Groundwater availability must therefore be evaluated not only in terms of instantaneous borehole yield, but also in terms of seasonal variation and sustainable long-term abstraction.&lt;br /&gt;
&lt;br /&gt;
== Groundwater quality ==&lt;br /&gt;
&lt;br /&gt;
Regional groundwater studies generally describe Guéra groundwater as relatively weakly mineralised compared with strongly saline groundwater systems elsewhere in Chad.&lt;br /&gt;
&lt;br /&gt;
Earlier regional studies cited by Nouradine reported dissolved mineral content generally below approximately &#039;&#039;&#039;250 mg/L&#039;&#039;&#039;, with bicarbonate-dominated groundwater and relatively low chloride and sulfate concentrations.&amp;lt;ref name=&amp;quot;nouradine&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
More recent geochemical work by Nouradine analysed &#039;&#039;&#039;211 groundwater samples&#039;&#039;&#039;, principally in and around the Mongo study area. Electrical conductivity ranged from approximately &#039;&#039;&#039;83 to 1,183 µS/cm&#039;&#039;&#039;, with an overall mean of approximately &#039;&#039;&#039;427 µS/cm&#039;&#039;&#039;.&amp;lt;ref name=&amp;quot;nouradine&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Mineralisation increases in some deeper or fractured groundwater systems. Mean conductivity in the study was approximately:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Water source&lt;br /&gt;
! Mean electrical conductivity&lt;br /&gt;
|-&lt;br /&gt;
| Shallow rural wells&lt;br /&gt;
| ~175 µS/cm&lt;br /&gt;
|-&lt;br /&gt;
| Rural boreholes in fractured basement&lt;br /&gt;
| ~445 µS/cm&lt;br /&gt;
|-&lt;br /&gt;
| Urban boreholes in fractured basement&lt;br /&gt;
| ~526 µS/cm&lt;br /&gt;
|-&lt;br /&gt;
| Wells intersecting both weathered and fractured horizons&lt;br /&gt;
| ~677 µS/cm&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
These figures describe the sampled areas around Mongo and should &#039;&#039;&#039;not&#039;&#039;&#039; be assumed to represent every groundwater body in Guéra.&lt;br /&gt;
&lt;br /&gt;
Local groundwater chemistry can vary strongly because individual boreholes may intercept different weathered zones, fracture systems and groundwater residence times.&lt;br /&gt;
&lt;br /&gt;
=== Local salinity ===&lt;br /&gt;
&lt;br /&gt;
Saline or noticeably mineralised boreholes occur locally in the Guéra region, including around Bitkine.&lt;br /&gt;
&lt;br /&gt;
AOWIS field observations around Bitkine indicate substantial local variation in water quality, with potable and saline groundwater occurring within the same general area. Some saline wells are unsuitable for drinking but remain in use for washing, construction, irrigation or other non-potable purposes.&lt;br /&gt;
&lt;br /&gt;
This local variability is consistent with the discontinuous fractured-basement hydrogeology of the area. Salinity at one borehole does not establish that neighbouring groundwater will have the same composition.&lt;br /&gt;
&lt;br /&gt;
Electrical conductivity, TDS and full chemical analysis should therefore be measured individually for each water point before treatment requirements or desalination systems are designed.&lt;br /&gt;
&lt;br /&gt;
== Bitkine and Abtouyour ==&lt;br /&gt;
&lt;br /&gt;
[[Regions:Chad/Guéra/Bitkine|Bitkine]] is the capital of the Abtouyour department and one of the main current areas of groundwater investigation in Guéra.&lt;br /&gt;
&lt;br /&gt;
The 2023–2024 work carried out by SEVES, UMR METIS of Sorbonne Université and ANTEA concentrated specifically on the Bitkine area. Pierre Palomar reinterpreted &#039;&#039;&#039;61 existing electrical-resistivity tomography surveys&#039;&#039;&#039; and associated borehole information to develop a local hydrogeological model and improve future borehole siting.&amp;lt;ref name=&amp;quot;palomar&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The work builds directly on Nouradine&#039;s regional research, which had concentrated particularly on the Mongo and Barlo areas.&lt;br /&gt;
&lt;br /&gt;
The Bitkine study found that geology and weathering pattern are critical to borehole performance and that geophysical anomalies cannot be interpreted reliably as fractures without considering the geological and geomorphological context.&amp;lt;ref name=&amp;quot;palomar&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
A dedicated page covers the local conditions and water-supply work:&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;[[Regions:Chad/Guéra/Bitkine]]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
== Water supply ==&lt;br /&gt;
&lt;br /&gt;
Much of Guéra depends on boreholes, hand-pumped wells and small piped drinking-water systems.&lt;br /&gt;
&lt;br /&gt;
The combination of low borehole yields, high drilling failure rates, seasonal demand and uncertain recharge makes reliable water supply difficult, particularly during the dry season.&lt;br /&gt;
&lt;br /&gt;
The provincial development plan reported substantial deficits in both rural hand-pump coverage and piped AEP systems.&amp;lt;ref name=&amp;quot;spat&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the Bitkine area, &#039;&#039;&#039;SEVES&#039;&#039;&#039; and its Chadian partner &#039;&#039;&#039;ADES&#039;&#039;&#039; have been working with the Commune of Bitkine and the regional water authorities through the &#039;&#039;&#039;REAVIA&#039;&#039;&#039; programme.&lt;br /&gt;
&lt;br /&gt;
Recent groundwater-development work reported by SEVES included:&lt;br /&gt;
&lt;br /&gt;
* a new borehole at Bitkine producing approximately &#039;&#039;&#039;6 m³/h&#039;&#039;&#039;;&lt;br /&gt;
* rehabilitation of a borehole at Koubo Adougoul producing approximately &#039;&#039;&#039;4 m³/h&#039;&#039;&#039;;&lt;br /&gt;
* a new borehole at Koubo Adougoul producing approximately &#039;&#039;&#039;7 m³/h&#039;&#039;&#039;.&amp;lt;ref name=&amp;quot;reavia&amp;quot;&amp;gt;[https://www.asso-seves.org/tchad-mobilisation-de-la-ressource-en-eau-pour-les-services-d-eau-potable-de.html SEVES, &#039;&#039;Mobilisation de la ressource en eau pour les services d&#039;eau potable de Bitkine et Koubo Adougoul dans la province du Guéra — REAVIA&#039;&#039;.]&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
These yields are high relative to many of the boreholes represented in the regional datasets.&lt;br /&gt;
&lt;br /&gt;
== Hydrogeological research ==&lt;br /&gt;
&lt;br /&gt;
Recent groundwater research in Guéra has produced an unusually large combined hydrogeological and geophysical dataset for a crystalline-basement region.&lt;br /&gt;
&lt;br /&gt;
=== Nouradine 2023 ===&lt;br /&gt;
&lt;br /&gt;
Haroun Nouradine&#039;s doctoral research combined:&lt;br /&gt;
&lt;br /&gt;
* geological analysis;&lt;br /&gt;
* hydrogeology;&lt;br /&gt;
* electrical geophysics;&lt;br /&gt;
* groundwater chemistry;&lt;br /&gt;
* stable isotopes;&lt;br /&gt;
* piezometric monitoring;&lt;br /&gt;
* machine learning.&lt;br /&gt;
&lt;br /&gt;
The underlying datasets include:&lt;br /&gt;
&lt;br /&gt;
* 798 boreholes;&lt;br /&gt;
* 700 EM34 profiles;&lt;br /&gt;
* 592 electrical-resistivity tomography profiles;&lt;br /&gt;
* 211 geochemical and isotopic groundwater samples.&lt;br /&gt;
&lt;br /&gt;
The work established a conceptual model of Guéra&#039;s crystalline-basement aquifers and identified factors controlling borehole productivity.&amp;lt;ref name=&amp;quot;nouradine&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Full thesis:&#039;&#039;&#039;  &lt;br /&gt;
:[https://nextcloud.aowis.org/s/tCJgPAa2G6Lws83 &#039;&#039;Évaluation des ressources en eau dans les aquifères de socle dans la région du Guéra (Tchad)&#039;&#039;, Haroun Nouradine, 2023]&lt;br /&gt;
&lt;br /&gt;
=== Palomar / SEVES 2024 ===&lt;br /&gt;
&lt;br /&gt;
Pierre Palomar&#039;s study, carried out within SEVES in collaboration with Sorbonne Université&#039;s UMR METIS and ANTEA, applies the regional hydrogeological model specifically to the Bitkine area.&lt;br /&gt;
&lt;br /&gt;
It includes:&lt;br /&gt;
&lt;br /&gt;
* a review of basement-aquifer hydrogeology;&lt;br /&gt;
* evaluation of geophysical prospecting methods;&lt;br /&gt;
* reinterpretation of existing ERT surveys;&lt;br /&gt;
* comparison with borehole results;&lt;br /&gt;
* a hydrogeological conceptual model for the Bitkine area;&lt;br /&gt;
* recommendations for future groundwater prospecting and borehole siting.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Full report:&#039;&#039;&#039;  &lt;br /&gt;
:[https://nextcloud.aowis.org/s/j7Gy7bMrFr5Gsew &#039;&#039;Conceptualisation hydrogéologique et recommandations pour les prospections géophysiques et l&#039;implantation des forages — Province du Guéra, Tchad&#039;&#039;, Pierre Palomar / SEVES, 2024]&lt;br /&gt;
&lt;br /&gt;
== AOWIS work ==&lt;br /&gt;
&lt;br /&gt;
Guéra is a current AOWIS field region, with initial work concentrated around [[Regions:Chad/Guéra/Bitkine|Bitkine]].&lt;br /&gt;
&lt;br /&gt;
Current work includes documentation of existing water points, seasonal borehole yields, water quality, groundwater salinity, opportunities for cooperation between existing well operators, and options for additional storage, treatment and distribution infrastructure.&lt;br /&gt;
&lt;br /&gt;
The combination of highly variable groundwater productivity and local differences in groundwater chemistry makes the region particularly relevant to integrated water-resource monitoring and planning.&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== External resources ==&lt;br /&gt;
&lt;br /&gt;
* [https://nextcloud.aowis.org/s/tCJgPAa2G6Lws83 Nouradine 2023 doctoral thesis — AOWIS-hosted PDF]&lt;br /&gt;
* [https://nextcloud.aowis.org/s/j7Gy7bMrFr5Gsew Palomar / SEVES Guéra and Bitkine hydrogeology report — AOWIS-hosted PDF]&lt;br /&gt;
* [https://doi.org/10.1007/s10040-024-02766-2 Nouradine et al. 2024 — Hydrogeology Journal]&lt;br /&gt;
* [https://www.asso-seves.org/implantation-des-forages-dans-la-province-du-guera-autchad.html SEVES — hydrogeology and borehole siting in Guéra]&lt;br /&gt;
* [https://apef-conservation.org/ressources-documentaires/ Schéma Provincial d&#039;Aménagement du Territoire du Guéra 2022–2032]&lt;br /&gt;
&lt;br /&gt;
[[Category:Chad]]&lt;br /&gt;
[[Category:Guéra]]&lt;br /&gt;
[[Category:Groundwater]]&lt;br /&gt;
[[Category:Hydrogeology]]&lt;br /&gt;
[[Category:Water supply]]&lt;/div&gt;</summary>
		<author><name>Samuel</name></author>
	</entry>
	<entry>
		<id>https://aowis.org/index.php?title=Regions:Chad/Gu%C3%A9ra&amp;diff=741</id>
		<title>Regions:Chad/Guéra</title>
		<link rel="alternate" type="text/html" href="https://aowis.org/index.php?title=Regions:Chad/Gu%C3%A9ra&amp;diff=741"/>
		<updated>2026-09-18T00:43:00Z</updated>

		<summary type="html">&lt;p&gt;Samuel: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
{{AI-Generated&lt;br /&gt;
 | model = ChatGPT&lt;br /&gt;
 | date = 2026-09-18&lt;br /&gt;
 | scope = full page&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Guéra&#039;&#039;&#039; is a province in central [[Regions:Chad|Chad]]. Its provincial capital is &#039;&#039;&#039;Mongo&#039;&#039;&#039;. The province includes the town of [[Regions:Chad/Guéra/Bitkine|Bitkine]], where AOWIS is currently involved in local water-supply work and groundwater assessment.&lt;br /&gt;
&lt;br /&gt;
Guéra lies across the transition from the Sahelian zone in the north to more humid Sudanian conditions in the south. Its mountainous crystalline basement, strongly seasonal rainfall, lack of permanent rivers, and highly variable groundwater productivity make water supply a major engineering challenge.&lt;br /&gt;
&lt;br /&gt;
== Geography and administration ==&lt;br /&gt;
&lt;br /&gt;
The 2022 &#039;&#039;Schéma Provincial d&#039;Aménagement du Territoire du Guéra&#039;&#039; gives an area of approximately &#039;&#039;&#039;61,279 km²&#039;&#039;&#039;. Following the 2021 administrative restructuring, the province consists of five departments:&amp;lt;ref name=&amp;quot;spat&amp;quot;&amp;gt;[https://apef-conservation.org/ressources-documentaires/ APEF / Republic of Chad, &#039;&#039;Schéma Provincial d&#039;Aménagement du Territoire du Guéra 2022–2032&#039;&#039;, 2022.]&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Guéra&#039;&#039;&#039;, capital Mongo;&lt;br /&gt;
* &#039;&#039;&#039;Abtouyour&#039;&#039;&#039;, capital [[Regions:Chad/Guéra/Bitkine|Bitkine]];&lt;br /&gt;
* &#039;&#039;&#039;Mangalmé&#039;&#039;&#039;, capital Mangalmé;&lt;br /&gt;
* &#039;&#039;&#039;Barh Signaka&#039;&#039;&#039;, capital Chinguil;&lt;br /&gt;
* &#039;&#039;&#039;Garada&#039;&#039;&#039;, capital Melfi.&lt;br /&gt;
&lt;br /&gt;
The same planning document gives a projected population of &#039;&#039;&#039;635,822 inhabitants in 2020&#039;&#039;&#039;, based on the 2009 national census and subsequent INSEED projections. The population is concentrated particularly in Guéra and Abtouyour.&amp;lt;ref name=&amp;quot;spat&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Terrain and surface water ==&lt;br /&gt;
&lt;br /&gt;
The landscape is dominated by plains interrupted by large granitic massifs, inselbergs, plateaus, and exposed bedrock.&lt;br /&gt;
&lt;br /&gt;
The central Chadian massif reaches some of its highest elevations in Guéra. The Mont Guéra reaches approximately &#039;&#039;&#039;1,613 m&#039;&#039;&#039; in the Bitkine area, while Mont Guédi east of Mongo reaches approximately &#039;&#039;&#039;1,506 m&#039;&#039;&#039;.&amp;lt;ref name=&amp;quot;spat&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
There are no major permanent rivers across most of the province. Surface drainage is dominated by seasonal watercourses, locally known as &#039;&#039;&#039;barhs&#039;&#039;&#039; or &#039;&#039;&#039;ouadis&#039;&#039;&#039;, which flow during the rainy season and may retain water temporarily in depressions and ponds.&lt;br /&gt;
&lt;br /&gt;
Seasonal streams draining the Guéra massif include the Bolong, Bang-Bang, Zilla, Zerzer and Melmele systems. Water from some northern catchments ultimately contributes toward Lake Fitri.&amp;lt;ref name=&amp;quot;spat&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Surface-water availability therefore changes strongly between the rainy and dry seasons, increasing dependence on groundwater for permanent water supply.&lt;br /&gt;
&lt;br /&gt;
== Climate ==&lt;br /&gt;
&lt;br /&gt;
Guéra spans several climatic zones. The north is predominantly Sahelian, the centre is Sahelo-Sudanian, and the southern part of the province approaches Sudanian conditions.&lt;br /&gt;
&lt;br /&gt;
The main seasons are:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;rainy season:&#039;&#039;&#039; approximately May to September;&lt;br /&gt;
* &#039;&#039;&#039;dry season:&#039;&#039;&#039; approximately October to April.&lt;br /&gt;
&lt;br /&gt;
July and August account for a large fraction of annual rainfall in hydrogeological studies of the central and northern part of the province.&amp;lt;ref name=&amp;quot;palomar&amp;quot;&amp;gt;[https://nextcloud.aowis.org/s/j7Gy7bMrFr5Gsew Pierre Palomar, &#039;&#039;Conceptualisation hydrogéologique et recommandations pour les prospections géophysiques et l&#039;implantation des forages — Province du Guéra, Tchad&#039;&#039;, SEVES, 2024.]&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The provincial planning document reports annual precipitation increasing broadly from around &#039;&#039;&#039;800 mm in the north to 1,100 mm in the south&#039;&#039;&#039;. Hydrogeological studies covering more restricted parts of Guéra use lower ranges, including approximately &#039;&#039;&#039;430–867 mm/year&#039;&#039;&#039;. These values refer to different geographic extents and datasets and should not be treated as a single uniform rainfall value for the province.&amp;lt;ref name=&amp;quot;spat&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;palomar&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Mean annual temperature is around &#039;&#039;&#039;28 °C&#039;&#039;&#039;, with high temperatures and long dry periods contributing to evaporation, drying of seasonal ponds, and strong seasonal pressure on water supplies.&amp;lt;ref name=&amp;quot;spat&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Geology ==&lt;br /&gt;
&lt;br /&gt;
Much of the Guéra massif consists of &#039;&#039;&#039;crystalline basement rock&#039;&#039;&#039;. Nouradine&#039;s regional hydrogeological work describes the study area as being dominated by granitoids and metamorphic rocks.&amp;lt;ref name=&amp;quot;nouradine&amp;quot;&amp;gt;[https://nextcloud.aowis.org/s/tCJgPAa2G6Lws83 Haroun Nouradine, &#039;&#039;Évaluation des ressources en eau dans les aquifères de socle dans la région du Guéra (Tchad) : combinaison d&#039;approches géologiques, hydrogéologiques, géophysiques, géochimiques et d&#039;apprentissage automatique&#039;&#039;, doctoral thesis, Sorbonne Université, 2023.]&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Around Bitkine, the basement includes:&lt;br /&gt;
&lt;br /&gt;
* granite;&lt;br /&gt;
* biotite granite;&lt;br /&gt;
* diorite;&lt;br /&gt;
* granodiorite;&lt;br /&gt;
* dolerite.&lt;br /&gt;
&lt;br /&gt;
The lithology strongly influences groundwater productivity. Biotite granites can develop permeable weathered and fractured horizons, while alteration of diorites, granodiorites and dolerites can produce larger amounts of clay, reducing infiltration and hydraulic conductivity.&amp;lt;ref name=&amp;quot;palomar&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Hydrogeology ==&lt;br /&gt;
&lt;br /&gt;
Groundwater in Guéra does not occur as one large continuous regional aquifer. The principal groundwater resources are associated with:&lt;br /&gt;
&lt;br /&gt;
* weathered crystalline basement;&lt;br /&gt;
* fractured and fissured bedrock;&lt;br /&gt;
* alluvial deposits;&lt;br /&gt;
* sands and sediments along seasonal drainage systems.&lt;br /&gt;
&lt;br /&gt;
The basement aquifers are therefore &#039;&#039;&#039;heterogeneous and discontinuous&#039;&#039;&#039;. Two boreholes located relatively close to one another can encounter substantially different conditions.&lt;br /&gt;
&lt;br /&gt;
A simplified basement-aquifer structure consists of:&lt;br /&gt;
&lt;br /&gt;
# superficial material and soil;&lt;br /&gt;
# weathered basement, or &#039;&#039;&#039;alterites&#039;&#039;&#039;;&lt;br /&gt;
# a fractured basement horizon;&lt;br /&gt;
# progressively less fractured competent bedrock at greater depth.&lt;br /&gt;
&lt;br /&gt;
The weathered horizon can provide substantial groundwater storage. Hydraulic transmissivity is often associated particularly with the upper fractured basement beneath it.&amp;lt;ref name=&amp;quot;nouradine&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Nouradine&#039;s regional analysis found that important water inflows commonly occur at approximately &#039;&#039;&#039;30–60 m depth&#039;&#039;&#039;. Productivity generally decreases where drilling continues far into relatively unfractured basement.&amp;lt;ref name=&amp;quot;nouradine&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Groundwater occurrence and borehole productivity depend on the combined effects of:&lt;br /&gt;
&lt;br /&gt;
* lithology;&lt;br /&gt;
* thickness and permeability of the weathered zone;&lt;br /&gt;
* development of the fractured horizon;&lt;br /&gt;
* geomorphology;&lt;br /&gt;
* recharge conditions;&lt;br /&gt;
* local drainage;&lt;br /&gt;
* position within the landscape.&lt;br /&gt;
&lt;br /&gt;
Low-lying areas and locations favourable to infiltration and recharge can provide substantially better groundwater conditions than nearby elevated or poorly weathered basement.&lt;br /&gt;
&lt;br /&gt;
== Borehole productivity ==&lt;br /&gt;
&lt;br /&gt;
Obtaining productive boreholes is a major difficulty in Guéra.&lt;br /&gt;
&lt;br /&gt;
Data analysed for boreholes constructed between 2010 and 2016 show that, among &#039;&#039;&#039;137 boreholes&#039;&#039;&#039; considered by the SEVES study:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;47%&#039;&#039;&#039; were unsuccessful during drilling and were not equipped;&lt;br /&gt;
* &#039;&#039;&#039;42%&#039;&#039;&#039; produced too little water for connection to an AEP water-supply network;&lt;br /&gt;
* only &#039;&#039;&#039;11%&#039;&#039;&#039; provided an exploitable yield of approximately &#039;&#039;&#039;4 m³/h for 8 hours per day&#039;&#039;&#039;.&amp;lt;ref name=&amp;quot;palomar&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The broader dataset analysed by Nouradine contains technical information from &#039;&#039;&#039;798 boreholes&#039;&#039;&#039;, together with approximately &#039;&#039;&#039;700 EM34 profiles&#039;&#039;&#039; and &#039;&#039;&#039;592 electrical-resistivity tomography profiles&#039;&#039;&#039;.&amp;lt;ref name=&amp;quot;nouradine&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;article&amp;quot;&amp;gt;[https://doi.org/10.1007/s10040-024-02766-2 H. Nouradine et al., &#039;&#039;Integrating geological, hydrogeological and geophysical data to identify groundwater resources in granitic basement areas (Guéra Massif, Chad)&#039;&#039;, Hydrogeology Journal 32, 759–784, 2024.]&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The mean borehole yield in the analysed basement-aquifer dataset is approximately &#039;&#039;&#039;1 m³/h&#039;&#039;&#039;. More productive boreholes are associated particularly with well-developed weathered and fractured horizons and favourable granite or biotite-granite formations.&amp;lt;ref name=&amp;quot;nouradine&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The difficulty is therefore not simply drilling deep enough. Successful groundwater development requires identifying favourable combinations of geology, weathering, fractures, topography and recharge.&lt;br /&gt;
&lt;br /&gt;
== Groundwater recharge ==&lt;br /&gt;
&lt;br /&gt;
Recharge is closely linked to the short rainy season.&lt;br /&gt;
&lt;br /&gt;
Direct infiltration across exposed or poorly permeable uplands can be limited, while runoff concentrates water in lower terrain, seasonal drainage channels, alluvial deposits and favourable fractured zones.&lt;br /&gt;
&lt;br /&gt;
The strongly seasonal rainfall regime means groundwater recharge can vary substantially between years. Quantifying long-term recharge remains an important uncertainty for sustainable groundwater development in Guéra.&amp;lt;ref name=&amp;quot;palomar&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Groundwater availability must therefore be evaluated not only in terms of instantaneous borehole yield, but also in terms of seasonal variation and sustainable long-term abstraction.&lt;br /&gt;
&lt;br /&gt;
== Groundwater quality ==&lt;br /&gt;
&lt;br /&gt;
Regional groundwater studies generally describe Guéra groundwater as relatively weakly mineralised compared with strongly saline groundwater systems elsewhere in Chad.&lt;br /&gt;
&lt;br /&gt;
Earlier regional studies cited by Nouradine reported dissolved mineral content generally below approximately &#039;&#039;&#039;250 mg/L&#039;&#039;&#039;, with bicarbonate-dominated groundwater and relatively low chloride and sulfate concentrations.&amp;lt;ref name=&amp;quot;nouradine&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
More recent geochemical work by Nouradine analysed &#039;&#039;&#039;211 groundwater samples&#039;&#039;&#039;, principally in and around the Mongo study area. Electrical conductivity ranged from approximately &#039;&#039;&#039;83 to 1,183 µS/cm&#039;&#039;&#039;, with an overall mean of approximately &#039;&#039;&#039;427 µS/cm&#039;&#039;&#039;.&amp;lt;ref name=&amp;quot;nouradine&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Mineralisation increases in some deeper or fractured groundwater systems. Mean conductivity in the study was approximately:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Water source&lt;br /&gt;
! Mean electrical conductivity&lt;br /&gt;
|-&lt;br /&gt;
| Shallow rural wells&lt;br /&gt;
| ~175 µS/cm&lt;br /&gt;
|-&lt;br /&gt;
| Rural boreholes in fractured basement&lt;br /&gt;
| ~445 µS/cm&lt;br /&gt;
|-&lt;br /&gt;
| Urban boreholes in fractured basement&lt;br /&gt;
| ~526 µS/cm&lt;br /&gt;
|-&lt;br /&gt;
| Wells intersecting both weathered and fractured horizons&lt;br /&gt;
| ~677 µS/cm&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
These figures describe the sampled areas around Mongo and should &#039;&#039;&#039;not&#039;&#039;&#039; be assumed to represent every groundwater body in Guéra.&lt;br /&gt;
&lt;br /&gt;
Local groundwater chemistry can vary strongly because individual boreholes may intercept different weathered zones, fracture systems and groundwater residence times.&lt;br /&gt;
&lt;br /&gt;
=== Local salinity ===&lt;br /&gt;
&lt;br /&gt;
Saline or noticeably mineralised boreholes occur locally in the Guéra region, including around Bitkine.&lt;br /&gt;
&lt;br /&gt;
AOWIS field observations around Bitkine indicate substantial local variation in water quality, with potable and saline groundwater occurring within the same general area. Some saline wells are unsuitable for drinking but remain in use for washing, construction, irrigation or other non-potable purposes.&lt;br /&gt;
&lt;br /&gt;
This local variability is consistent with the discontinuous fractured-basement hydrogeology of the area. Salinity at one borehole does not establish that neighbouring groundwater will have the same composition.&lt;br /&gt;
&lt;br /&gt;
Electrical conductivity, TDS and full chemical analysis should therefore be measured individually for each water point before treatment requirements or desalination systems are designed.&lt;br /&gt;
&lt;br /&gt;
== Bitkine and Abtouyour ==&lt;br /&gt;
&lt;br /&gt;
[[Regions:Chad/Guéra/Bitkine|Bitkine]] is the capital of the Abtouyour department and one of the main current areas of groundwater investigation in Guéra.&lt;br /&gt;
&lt;br /&gt;
The 2023–2024 work carried out by SEVES, UMR METIS of Sorbonne Université and ANTEA concentrated specifically on the Bitkine area. Pierre Palomar reinterpreted &#039;&#039;&#039;61 existing electrical-resistivity tomography surveys&#039;&#039;&#039; and associated borehole information to develop a local hydrogeological model and improve future borehole siting.&amp;lt;ref name=&amp;quot;palomar&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The work builds directly on Nouradine&#039;s regional research, which had concentrated particularly on the Mongo and Barlo areas.&lt;br /&gt;
&lt;br /&gt;
The Bitkine study found that geology and weathering pattern are critical to borehole performance and that geophysical anomalies cannot be interpreted reliably as fractures without considering the geological and geomorphological context.&amp;lt;ref name=&amp;quot;palomar&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
A dedicated page covers the local conditions and water-supply work:&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;[[Regions:Chad/Guéra/Bitkine]]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
== Water supply ==&lt;br /&gt;
&lt;br /&gt;
Much of Guéra depends on boreholes, hand-pumped wells and small piped drinking-water systems.&lt;br /&gt;
&lt;br /&gt;
The combination of low borehole yields, high drilling failure rates, seasonal demand and uncertain recharge makes reliable water supply difficult, particularly during the dry season.&lt;br /&gt;
&lt;br /&gt;
The provincial development plan reported substantial deficits in both rural hand-pump coverage and piped AEP systems.&amp;lt;ref name=&amp;quot;spat&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the Bitkine area, &#039;&#039;&#039;SEVES&#039;&#039;&#039; and its Chadian partner &#039;&#039;&#039;ADES&#039;&#039;&#039; have been working with the Commune of Bitkine and the regional water authorities through the &#039;&#039;&#039;REAVIA&#039;&#039;&#039; programme.&lt;br /&gt;
&lt;br /&gt;
Recent groundwater-development work reported by SEVES included:&lt;br /&gt;
&lt;br /&gt;
* a new borehole at Bitkine producing approximately &#039;&#039;&#039;6 m³/h&#039;&#039;&#039;;&lt;br /&gt;
* rehabilitation of a borehole at Koubo Adougoul producing approximately &#039;&#039;&#039;4 m³/h&#039;&#039;&#039;;&lt;br /&gt;
* a new borehole at Koubo Adougoul producing approximately &#039;&#039;&#039;7 m³/h&#039;&#039;&#039;.&amp;lt;ref name=&amp;quot;reavia&amp;quot;&amp;gt;[https://www.asso-seves.org/tchad-mobilisation-de-la-ressource-en-eau-pour-les-services-d-eau-potable-de.html SEVES, &#039;&#039;Mobilisation de la ressource en eau pour les services d&#039;eau potable de Bitkine et Koubo Adougoul dans la province du Guéra — REAVIA&#039;&#039;.]&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
These yields are high relative to many of the boreholes represented in the regional datasets.&lt;br /&gt;
&lt;br /&gt;
== Hydrogeological research ==&lt;br /&gt;
&lt;br /&gt;
Recent groundwater research in Guéra has produced an unusually large combined hydrogeological and geophysical dataset for a crystalline-basement region.&lt;br /&gt;
&lt;br /&gt;
=== Nouradine 2023 ===&lt;br /&gt;
&lt;br /&gt;
Haroun Nouradine&#039;s doctoral research combined:&lt;br /&gt;
&lt;br /&gt;
* geological analysis;&lt;br /&gt;
* hydrogeology;&lt;br /&gt;
* electrical geophysics;&lt;br /&gt;
* groundwater chemistry;&lt;br /&gt;
* stable isotopes;&lt;br /&gt;
* piezometric monitoring;&lt;br /&gt;
* machine learning.&lt;br /&gt;
&lt;br /&gt;
The underlying datasets include:&lt;br /&gt;
&lt;br /&gt;
* 798 boreholes;&lt;br /&gt;
* 700 EM34 profiles;&lt;br /&gt;
* 592 electrical-resistivity tomography profiles;&lt;br /&gt;
* 211 geochemical and isotopic groundwater samples.&lt;br /&gt;
&lt;br /&gt;
The work established a conceptual model of Guéra&#039;s crystalline-basement aquifers and identified factors controlling borehole productivity.&amp;lt;ref name=&amp;quot;nouradine&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Full thesis:&#039;&#039;&#039;  &lt;br /&gt;
:[https://nextcloud.aowis.org/s/tCJgPAa2G6Lws83 &#039;&#039;Évaluation des ressources en eau dans les aquifères de socle dans la région du Guéra (Tchad)&#039;&#039;, Haroun Nouradine, 2023]&lt;br /&gt;
&lt;br /&gt;
=== Palomar / SEVES 2024 ===&lt;br /&gt;
&lt;br /&gt;
Pierre Palomar&#039;s study, carried out within SEVES in collaboration with Sorbonne Université&#039;s UMR METIS and ANTEA, applies the regional hydrogeological model specifically to the Bitkine area.&lt;br /&gt;
&lt;br /&gt;
It includes:&lt;br /&gt;
&lt;br /&gt;
* a review of basement-aquifer hydrogeology;&lt;br /&gt;
* evaluation of geophysical prospecting methods;&lt;br /&gt;
* reinterpretation of existing ERT surveys;&lt;br /&gt;
* comparison with borehole results;&lt;br /&gt;
* a hydrogeological conceptual model for the Bitkine area;&lt;br /&gt;
* recommendations for future groundwater prospecting and borehole siting.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Full report:&#039;&#039;&#039;  &lt;br /&gt;
:[https://nextcloud.aowis.org/s/j7Gy7bMrFr5Gsew &#039;&#039;Conceptualisation hydrogéologique et recommandations pour les prospections géophysiques et l&#039;implantation des forages — Province du Guéra, Tchad&#039;&#039;, Pierre Palomar / SEVES, 2024]&lt;br /&gt;
&lt;br /&gt;
== AOWIS work ==&lt;br /&gt;
&lt;br /&gt;
Guéra is a current AOWIS field region, with initial work concentrated around [[Regions:Chad/Guéra/Bitkine|Bitkine]].&lt;br /&gt;
&lt;br /&gt;
Current work includes documentation of existing water points, seasonal borehole yields, water quality, groundwater salinity, opportunities for cooperation between existing well operators, and options for additional storage, treatment and distribution infrastructure.&lt;br /&gt;
&lt;br /&gt;
The combination of highly variable groundwater productivity and local differences in groundwater chemistry makes the region particularly relevant to integrated water-resource monitoring and planning.&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== External resources ==&lt;br /&gt;
&lt;br /&gt;
* [https://nextcloud.aowis.org/s/tCJgPAa2G6Lws83 Nouradine 2023 doctoral thesis — AOWIS-hosted PDF]&lt;br /&gt;
* [https://nextcloud.aowis.org/s/j7Gy7bMrFr5Gsew Palomar / SEVES Guéra and Bitkine hydrogeology report — AOWIS-hosted PDF]&lt;br /&gt;
* [https://doi.org/10.1007/s10040-024-02766-2 Nouradine et al. 2024 — Hydrogeology Journal]&lt;br /&gt;
* [https://www.asso-seves.org/implantation-des-forages-dans-la-province-du-guera-autchad.html SEVES — hydrogeology and borehole siting in Guéra]&lt;br /&gt;
* [https://apef-conservation.org/ressources-documentaires/ Schéma Provincial d&#039;Aménagement du Territoire du Guéra 2022–2032]&lt;br /&gt;
&lt;br /&gt;
[[Category:Chad]]&lt;br /&gt;
[[Category:Guéra]]&lt;br /&gt;
[[Category:Groundwater]]&lt;br /&gt;
[[Category:Hydrogeology]]&lt;br /&gt;
[[Category:Water supply]]&lt;/div&gt;</summary>
		<author><name>Samuel</name></author>
	</entry>
	<entry>
		<id>https://aowis.org/index.php?title=Regions:Chad/Gu%C3%A9ra&amp;diff=740</id>
		<title>Regions:Chad/Guéra</title>
		<link rel="alternate" type="text/html" href="https://aowis.org/index.php?title=Regions:Chad/Gu%C3%A9ra&amp;diff=740"/>
		<updated>2026-09-18T00:40:52Z</updated>

		<summary type="html">&lt;p&gt;Samuel: Created page with &amp;quot; {{AI-generated  | model = ChatGPT  | date = 2026-09-18  | scope = full page }}  &amp;#039;&amp;#039;&amp;#039;Guéra&amp;#039;&amp;#039;&amp;#039; is a province in central Chad. Its provincial capital is &amp;#039;&amp;#039;&amp;#039;Mongo&amp;#039;&amp;#039;&amp;#039;. The province includes the town of Bitkine, where AOWIS is currently involved in local water-supply work and groundwater assessment.  Guéra lies across the transition from the Sahelian zone in the north to more humid Sudanian conditions in the south. Its mountai...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
{{AI-generated&lt;br /&gt;
 | model = ChatGPT&lt;br /&gt;
 | date = 2026-09-18&lt;br /&gt;
 | scope = full page&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Guéra&#039;&#039;&#039; is a province in central [[Regions:Chad|Chad]]. Its provincial capital is &#039;&#039;&#039;Mongo&#039;&#039;&#039;. The province includes the town of [[Regions:Chad/Guéra/Bitkine|Bitkine]], where AOWIS is currently involved in local water-supply work and groundwater assessment.&lt;br /&gt;
&lt;br /&gt;
Guéra lies across the transition from the Sahelian zone in the north to more humid Sudanian conditions in the south. Its mountainous crystalline basement, strongly seasonal rainfall, lack of permanent rivers, and highly variable groundwater productivity make water supply a major engineering challenge.&lt;br /&gt;
&lt;br /&gt;
== Geography and administration ==&lt;br /&gt;
&lt;br /&gt;
The 2022 &#039;&#039;Schéma Provincial d&#039;Aménagement du Territoire du Guéra&#039;&#039; gives an area of approximately &#039;&#039;&#039;61,279 km²&#039;&#039;&#039;. Following the 2021 administrative restructuring, the province consists of five departments:&amp;lt;ref name=&amp;quot;spat&amp;quot;&amp;gt;[https://apef-conservation.org/ressources-documentaires/ APEF / Republic of Chad, &#039;&#039;Schéma Provincial d&#039;Aménagement du Territoire du Guéra 2022–2032&#039;&#039;, 2022.]&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Guéra&#039;&#039;&#039;, capital Mongo;&lt;br /&gt;
* &#039;&#039;&#039;Abtouyour&#039;&#039;&#039;, capital [[Regions:Chad/Guéra/Bitkine|Bitkine]];&lt;br /&gt;
* &#039;&#039;&#039;Mangalmé&#039;&#039;&#039;, capital Mangalmé;&lt;br /&gt;
* &#039;&#039;&#039;Barh Signaka&#039;&#039;&#039;, capital Chinguil;&lt;br /&gt;
* &#039;&#039;&#039;Garada&#039;&#039;&#039;, capital Melfi.&lt;br /&gt;
&lt;br /&gt;
The same planning document gives a projected population of &#039;&#039;&#039;635,822 inhabitants in 2020&#039;&#039;&#039;, based on the 2009 national census and subsequent INSEED projections. The population is concentrated particularly in Guéra and Abtouyour.&amp;lt;ref name=&amp;quot;spat&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Terrain and surface water ==&lt;br /&gt;
&lt;br /&gt;
The landscape is dominated by plains interrupted by large granitic massifs, inselbergs, plateaus, and exposed bedrock.&lt;br /&gt;
&lt;br /&gt;
The central Chadian massif reaches some of its highest elevations in Guéra. The Mont Guéra reaches approximately &#039;&#039;&#039;1,613 m&#039;&#039;&#039; in the Bitkine area, while Mont Guédi east of Mongo reaches approximately &#039;&#039;&#039;1,506 m&#039;&#039;&#039;.&amp;lt;ref name=&amp;quot;spat&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
There are no major permanent rivers across most of the province. Surface drainage is dominated by seasonal watercourses, locally known as &#039;&#039;&#039;barhs&#039;&#039;&#039; or &#039;&#039;&#039;ouadis&#039;&#039;&#039;, which flow during the rainy season and may retain water temporarily in depressions and ponds.&lt;br /&gt;
&lt;br /&gt;
Seasonal streams draining the Guéra massif include the Bolong, Bang-Bang, Zilla, Zerzer and Melmele systems. Water from some northern catchments ultimately contributes toward Lake Fitri.&amp;lt;ref name=&amp;quot;spat&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Surface-water availability therefore changes strongly between the rainy and dry seasons, increasing dependence on groundwater for permanent water supply.&lt;br /&gt;
&lt;br /&gt;
== Climate ==&lt;br /&gt;
&lt;br /&gt;
Guéra spans several climatic zones. The north is predominantly Sahelian, the centre is Sahelo-Sudanian, and the southern part of the province approaches Sudanian conditions.&lt;br /&gt;
&lt;br /&gt;
The main seasons are:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;rainy season:&#039;&#039;&#039; approximately May to September;&lt;br /&gt;
* &#039;&#039;&#039;dry season:&#039;&#039;&#039; approximately October to April.&lt;br /&gt;
&lt;br /&gt;
July and August account for a large fraction of annual rainfall in hydrogeological studies of the central and northern part of the province.&amp;lt;ref name=&amp;quot;palomar&amp;quot;&amp;gt;[https://nextcloud.aowis.org/s/j7Gy7bMrFr5Gsew Pierre Palomar, &#039;&#039;Conceptualisation hydrogéologique et recommandations pour les prospections géophysiques et l&#039;implantation des forages — Province du Guéra, Tchad&#039;&#039;, SEVES, 2024.]&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The provincial planning document reports annual precipitation increasing broadly from around &#039;&#039;&#039;800 mm in the north to 1,100 mm in the south&#039;&#039;&#039;. Hydrogeological studies covering more restricted parts of Guéra use lower ranges, including approximately &#039;&#039;&#039;430–867 mm/year&#039;&#039;&#039;. These values refer to different geographic extents and datasets and should not be treated as a single uniform rainfall value for the province.&amp;lt;ref name=&amp;quot;spat&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;palomar&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Mean annual temperature is around &#039;&#039;&#039;28 °C&#039;&#039;&#039;, with high temperatures and long dry periods contributing to evaporation, drying of seasonal ponds, and strong seasonal pressure on water supplies.&amp;lt;ref name=&amp;quot;spat&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Geology ==&lt;br /&gt;
&lt;br /&gt;
Much of the Guéra massif consists of &#039;&#039;&#039;crystalline basement rock&#039;&#039;&#039;. Nouradine&#039;s regional hydrogeological work describes the study area as being dominated by granitoids and metamorphic rocks.&amp;lt;ref name=&amp;quot;nouradine&amp;quot;&amp;gt;[https://nextcloud.aowis.org/s/tCJgPAa2G6Lws83 Haroun Nouradine, &#039;&#039;Évaluation des ressources en eau dans les aquifères de socle dans la région du Guéra (Tchad) : combinaison d&#039;approches géologiques, hydrogéologiques, géophysiques, géochimiques et d&#039;apprentissage automatique&#039;&#039;, doctoral thesis, Sorbonne Université, 2023.]&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Around Bitkine, the basement includes:&lt;br /&gt;
&lt;br /&gt;
* granite;&lt;br /&gt;
* biotite granite;&lt;br /&gt;
* diorite;&lt;br /&gt;
* granodiorite;&lt;br /&gt;
* dolerite.&lt;br /&gt;
&lt;br /&gt;
The lithology strongly influences groundwater productivity. Biotite granites can develop permeable weathered and fractured horizons, while alteration of diorites, granodiorites and dolerites can produce larger amounts of clay, reducing infiltration and hydraulic conductivity.&amp;lt;ref name=&amp;quot;palomar&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Hydrogeology ==&lt;br /&gt;
&lt;br /&gt;
Groundwater in Guéra does not occur as one large continuous regional aquifer. The principal groundwater resources are associated with:&lt;br /&gt;
&lt;br /&gt;
* weathered crystalline basement;&lt;br /&gt;
* fractured and fissured bedrock;&lt;br /&gt;
* alluvial deposits;&lt;br /&gt;
* sands and sediments along seasonal drainage systems.&lt;br /&gt;
&lt;br /&gt;
The basement aquifers are therefore &#039;&#039;&#039;heterogeneous and discontinuous&#039;&#039;&#039;. Two boreholes located relatively close to one another can encounter substantially different conditions.&lt;br /&gt;
&lt;br /&gt;
A simplified basement-aquifer structure consists of:&lt;br /&gt;
&lt;br /&gt;
# superficial material and soil;&lt;br /&gt;
# weathered basement, or &#039;&#039;&#039;alterites&#039;&#039;&#039;;&lt;br /&gt;
# a fractured basement horizon;&lt;br /&gt;
# progressively less fractured competent bedrock at greater depth.&lt;br /&gt;
&lt;br /&gt;
The weathered horizon can provide substantial groundwater storage. Hydraulic transmissivity is often associated particularly with the upper fractured basement beneath it.&amp;lt;ref name=&amp;quot;nouradine&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Nouradine&#039;s regional analysis found that important water inflows commonly occur at approximately &#039;&#039;&#039;30–60 m depth&#039;&#039;&#039;. Productivity generally decreases where drilling continues far into relatively unfractured basement.&amp;lt;ref name=&amp;quot;nouradine&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Groundwater occurrence and borehole productivity depend on the combined effects of:&lt;br /&gt;
&lt;br /&gt;
* lithology;&lt;br /&gt;
* thickness and permeability of the weathered zone;&lt;br /&gt;
* development of the fractured horizon;&lt;br /&gt;
* geomorphology;&lt;br /&gt;
* recharge conditions;&lt;br /&gt;
* local drainage;&lt;br /&gt;
* position within the landscape.&lt;br /&gt;
&lt;br /&gt;
Low-lying areas and locations favourable to infiltration and recharge can provide substantially better groundwater conditions than nearby elevated or poorly weathered basement.&lt;br /&gt;
&lt;br /&gt;
== Borehole productivity ==&lt;br /&gt;
&lt;br /&gt;
Obtaining productive boreholes is a major difficulty in Guéra.&lt;br /&gt;
&lt;br /&gt;
Data analysed for boreholes constructed between 2010 and 2016 show that, among &#039;&#039;&#039;137 boreholes&#039;&#039;&#039; considered by the SEVES study:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;47%&#039;&#039;&#039; were unsuccessful during drilling and were not equipped;&lt;br /&gt;
* &#039;&#039;&#039;42%&#039;&#039;&#039; produced too little water for connection to an AEP water-supply network;&lt;br /&gt;
* only &#039;&#039;&#039;11%&#039;&#039;&#039; provided an exploitable yield of approximately &#039;&#039;&#039;4 m³/h for 8 hours per day&#039;&#039;&#039;.&amp;lt;ref name=&amp;quot;palomar&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The broader dataset analysed by Nouradine contains technical information from &#039;&#039;&#039;798 boreholes&#039;&#039;&#039;, together with approximately &#039;&#039;&#039;700 EM34 profiles&#039;&#039;&#039; and &#039;&#039;&#039;592 electrical-resistivity tomography profiles&#039;&#039;&#039;.&amp;lt;ref name=&amp;quot;nouradine&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;article&amp;quot;&amp;gt;[https://doi.org/10.1007/s10040-024-02766-2 H. Nouradine et al., &#039;&#039;Integrating geological, hydrogeological and geophysical data to identify groundwater resources in granitic basement areas (Guéra Massif, Chad)&#039;&#039;, Hydrogeology Journal 32, 759–784, 2024.]&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The mean borehole yield in the analysed basement-aquifer dataset is approximately &#039;&#039;&#039;1 m³/h&#039;&#039;&#039;. More productive boreholes are associated particularly with well-developed weathered and fractured horizons and favourable granite or biotite-granite formations.&amp;lt;ref name=&amp;quot;nouradine&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The difficulty is therefore not simply drilling deep enough. Successful groundwater development requires identifying favourable combinations of geology, weathering, fractures, topography and recharge.&lt;br /&gt;
&lt;br /&gt;
== Groundwater recharge ==&lt;br /&gt;
&lt;br /&gt;
Recharge is closely linked to the short rainy season.&lt;br /&gt;
&lt;br /&gt;
Direct infiltration across exposed or poorly permeable uplands can be limited, while runoff concentrates water in lower terrain, seasonal drainage channels, alluvial deposits and favourable fractured zones.&lt;br /&gt;
&lt;br /&gt;
The strongly seasonal rainfall regime means groundwater recharge can vary substantially between years. Quantifying long-term recharge remains an important uncertainty for sustainable groundwater development in Guéra.&amp;lt;ref name=&amp;quot;palomar&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Groundwater availability must therefore be evaluated not only in terms of instantaneous borehole yield, but also in terms of seasonal variation and sustainable long-term abstraction.&lt;br /&gt;
&lt;br /&gt;
== Groundwater quality ==&lt;br /&gt;
&lt;br /&gt;
Regional groundwater studies generally describe Guéra groundwater as relatively weakly mineralised compared with strongly saline groundwater systems elsewhere in Chad.&lt;br /&gt;
&lt;br /&gt;
Earlier regional studies cited by Nouradine reported dissolved mineral content generally below approximately &#039;&#039;&#039;250 mg/L&#039;&#039;&#039;, with bicarbonate-dominated groundwater and relatively low chloride and sulfate concentrations.&amp;lt;ref name=&amp;quot;nouradine&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
More recent geochemical work by Nouradine analysed &#039;&#039;&#039;211 groundwater samples&#039;&#039;&#039;, principally in and around the Mongo study area. Electrical conductivity ranged from approximately &#039;&#039;&#039;83 to 1,183 µS/cm&#039;&#039;&#039;, with an overall mean of approximately &#039;&#039;&#039;427 µS/cm&#039;&#039;&#039;.&amp;lt;ref name=&amp;quot;nouradine&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Mineralisation increases in some deeper or fractured groundwater systems. Mean conductivity in the study was approximately:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Water source&lt;br /&gt;
! Mean electrical conductivity&lt;br /&gt;
|-&lt;br /&gt;
| Shallow rural wells&lt;br /&gt;
| ~175 µS/cm&lt;br /&gt;
|-&lt;br /&gt;
| Rural boreholes in fractured basement&lt;br /&gt;
| ~445 µS/cm&lt;br /&gt;
|-&lt;br /&gt;
| Urban boreholes in fractured basement&lt;br /&gt;
| ~526 µS/cm&lt;br /&gt;
|-&lt;br /&gt;
| Wells intersecting both weathered and fractured horizons&lt;br /&gt;
| ~677 µS/cm&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
These figures describe the sampled areas around Mongo and should &#039;&#039;&#039;not&#039;&#039;&#039; be assumed to represent every groundwater body in Guéra.&lt;br /&gt;
&lt;br /&gt;
Local groundwater chemistry can vary strongly because individual boreholes may intercept different weathered zones, fracture systems and groundwater residence times.&lt;br /&gt;
&lt;br /&gt;
=== Local salinity ===&lt;br /&gt;
&lt;br /&gt;
Saline or noticeably mineralised boreholes occur locally in the Guéra region, including around Bitkine.&lt;br /&gt;
&lt;br /&gt;
AOWIS field observations around Bitkine indicate substantial local variation in water quality, with potable and saline groundwater occurring within the same general area. Some saline wells are unsuitable for drinking but remain in use for washing, construction, irrigation or other non-potable purposes.&lt;br /&gt;
&lt;br /&gt;
This local variability is consistent with the discontinuous fractured-basement hydrogeology of the area. Salinity at one borehole does not establish that neighbouring groundwater will have the same composition.&lt;br /&gt;
&lt;br /&gt;
Electrical conductivity, TDS and full chemical analysis should therefore be measured individually for each water point before treatment requirements or desalination systems are designed.&lt;br /&gt;
&lt;br /&gt;
== Bitkine and Abtouyour ==&lt;br /&gt;
&lt;br /&gt;
[[Regions:Chad/Guéra/Bitkine|Bitkine]] is the capital of the Abtouyour department and one of the main current areas of groundwater investigation in Guéra.&lt;br /&gt;
&lt;br /&gt;
The 2023–2024 work carried out by SEVES, UMR METIS of Sorbonne Université and ANTEA concentrated specifically on the Bitkine area. Pierre Palomar reinterpreted &#039;&#039;&#039;61 existing electrical-resistivity tomography surveys&#039;&#039;&#039; and associated borehole information to develop a local hydrogeological model and improve future borehole siting.&amp;lt;ref name=&amp;quot;palomar&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The work builds directly on Nouradine&#039;s regional research, which had concentrated particularly on the Mongo and Barlo areas.&lt;br /&gt;
&lt;br /&gt;
The Bitkine study found that geology and weathering pattern are critical to borehole performance and that geophysical anomalies cannot be interpreted reliably as fractures without considering the geological and geomorphological context.&amp;lt;ref name=&amp;quot;palomar&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
A dedicated page covers the local conditions and water-supply work:&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;[[Regions:Chad/Guéra/Bitkine]]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
== Water supply ==&lt;br /&gt;
&lt;br /&gt;
Much of Guéra depends on boreholes, hand-pumped wells and small piped drinking-water systems.&lt;br /&gt;
&lt;br /&gt;
The combination of low borehole yields, high drilling failure rates, seasonal demand and uncertain recharge makes reliable water supply difficult, particularly during the dry season.&lt;br /&gt;
&lt;br /&gt;
The provincial development plan reported substantial deficits in both rural hand-pump coverage and piped AEP systems.&amp;lt;ref name=&amp;quot;spat&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the Bitkine area, &#039;&#039;&#039;SEVES&#039;&#039;&#039; and its Chadian partner &#039;&#039;&#039;ADES&#039;&#039;&#039; have been working with the Commune of Bitkine and the regional water authorities through the &#039;&#039;&#039;REAVIA&#039;&#039;&#039; programme.&lt;br /&gt;
&lt;br /&gt;
Recent groundwater-development work reported by SEVES included:&lt;br /&gt;
&lt;br /&gt;
* a new borehole at Bitkine producing approximately &#039;&#039;&#039;6 m³/h&#039;&#039;&#039;;&lt;br /&gt;
* rehabilitation of a borehole at Koubo Adougoul producing approximately &#039;&#039;&#039;4 m³/h&#039;&#039;&#039;;&lt;br /&gt;
* a new borehole at Koubo Adougoul producing approximately &#039;&#039;&#039;7 m³/h&#039;&#039;&#039;.&amp;lt;ref name=&amp;quot;reavia&amp;quot;&amp;gt;[https://www.asso-seves.org/tchad-mobilisation-de-la-ressource-en-eau-pour-les-services-d-eau-potable-de.html SEVES, &#039;&#039;Mobilisation de la ressource en eau pour les services d&#039;eau potable de Bitkine et Koubo Adougoul dans la province du Guéra — REAVIA&#039;&#039;.]&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
These yields are high relative to many of the boreholes represented in the regional datasets.&lt;br /&gt;
&lt;br /&gt;
== Hydrogeological research ==&lt;br /&gt;
&lt;br /&gt;
Recent groundwater research in Guéra has produced an unusually large combined hydrogeological and geophysical dataset for a crystalline-basement region.&lt;br /&gt;
&lt;br /&gt;
=== Nouradine 2023 ===&lt;br /&gt;
&lt;br /&gt;
Haroun Nouradine&#039;s doctoral research combined:&lt;br /&gt;
&lt;br /&gt;
* geological analysis;&lt;br /&gt;
* hydrogeology;&lt;br /&gt;
* electrical geophysics;&lt;br /&gt;
* groundwater chemistry;&lt;br /&gt;
* stable isotopes;&lt;br /&gt;
* piezometric monitoring;&lt;br /&gt;
* machine learning.&lt;br /&gt;
&lt;br /&gt;
The underlying datasets include:&lt;br /&gt;
&lt;br /&gt;
* 798 boreholes;&lt;br /&gt;
* 700 EM34 profiles;&lt;br /&gt;
* 592 electrical-resistivity tomography profiles;&lt;br /&gt;
* 211 geochemical and isotopic groundwater samples.&lt;br /&gt;
&lt;br /&gt;
The work established a conceptual model of Guéra&#039;s crystalline-basement aquifers and identified factors controlling borehole productivity.&amp;lt;ref name=&amp;quot;nouradine&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Full thesis:&#039;&#039;&#039;  &lt;br /&gt;
:[https://nextcloud.aowis.org/s/tCJgPAa2G6Lws83 &#039;&#039;Évaluation des ressources en eau dans les aquifères de socle dans la région du Guéra (Tchad)&#039;&#039;, Haroun Nouradine, 2023]&lt;br /&gt;
&lt;br /&gt;
=== Palomar / SEVES 2024 ===&lt;br /&gt;
&lt;br /&gt;
Pierre Palomar&#039;s study, carried out within SEVES in collaboration with Sorbonne Université&#039;s UMR METIS and ANTEA, applies the regional hydrogeological model specifically to the Bitkine area.&lt;br /&gt;
&lt;br /&gt;
It includes:&lt;br /&gt;
&lt;br /&gt;
* a review of basement-aquifer hydrogeology;&lt;br /&gt;
* evaluation of geophysical prospecting methods;&lt;br /&gt;
* reinterpretation of existing ERT surveys;&lt;br /&gt;
* comparison with borehole results;&lt;br /&gt;
* a hydrogeological conceptual model for the Bitkine area;&lt;br /&gt;
* recommendations for future groundwater prospecting and borehole siting.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Full report:&#039;&#039;&#039;  &lt;br /&gt;
:[https://nextcloud.aowis.org/s/j7Gy7bMrFr5Gsew &#039;&#039;Conceptualisation hydrogéologique et recommandations pour les prospections géophysiques et l&#039;implantation des forages — Province du Guéra, Tchad&#039;&#039;, Pierre Palomar / SEVES, 2024]&lt;br /&gt;
&lt;br /&gt;
== AOWIS work ==&lt;br /&gt;
&lt;br /&gt;
Guéra is a current AOWIS field region, with initial work concentrated around [[Regions:Chad/Guéra/Bitkine|Bitkine]].&lt;br /&gt;
&lt;br /&gt;
Current work includes documentation of existing water points, seasonal borehole yields, water quality, groundwater salinity, opportunities for cooperation between existing well operators, and options for additional storage, treatment and distribution infrastructure.&lt;br /&gt;
&lt;br /&gt;
The combination of highly variable groundwater productivity and local differences in groundwater chemistry makes the region particularly relevant to integrated water-resource monitoring and planning.&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== External resources ==&lt;br /&gt;
&lt;br /&gt;
* [https://nextcloud.aowis.org/s/tCJgPAa2G6Lws83 Nouradine 2023 doctoral thesis — AOWIS-hosted PDF]&lt;br /&gt;
* [https://nextcloud.aowis.org/s/j7Gy7bMrFr5Gsew Palomar / SEVES Guéra and Bitkine hydrogeology report — AOWIS-hosted PDF]&lt;br /&gt;
* [https://doi.org/10.1007/s10040-024-02766-2 Nouradine et al. 2024 — Hydrogeology Journal]&lt;br /&gt;
* [https://www.asso-seves.org/implantation-des-forages-dans-la-province-du-guera-autchad.html SEVES — hydrogeology and borehole siting in Guéra]&lt;br /&gt;
* [https://apef-conservation.org/ressources-documentaires/ Schéma Provincial d&#039;Aménagement du Territoire du Guéra 2022–2032]&lt;br /&gt;
&lt;br /&gt;
[[Category:Chad]]&lt;br /&gt;
[[Category:Guéra]]&lt;br /&gt;
[[Category:Groundwater]]&lt;br /&gt;
[[Category:Hydrogeology]]&lt;br /&gt;
[[Category:Water supply]]&lt;/div&gt;</summary>
		<author><name>Samuel</name></author>
	</entry>
</feed>