External:Main Page

2026-06-17T21:35:25Z

Samuel:

2026-06-13T12:27:58Z

Samuel: Samuel reverted File:Cooperation.jpg to an old version

File:Cooperation.jpg

2026-06-12T23:46:18Z

Samuel: Samuel uploaded a new version of File:Cooperation.jpg

2026-06-10T19:35:42Z

Samuel: /* Electrical Quantities */

* Part of: [[Measurement:Main_Page]]
* Related to: [[Measurement:Units]]

AOWIS defines a canonical set of unit identifiers used in all system interfaces, storage formats, APIs, and inter-system data exchanges.

All unit identifiers MUST be ASCII-only strings and MUST NOT contain Unicode characters, superscripts, or typographic symbols.

Units are machine-readable tokens and are not intended to represent typographic or human-rendered SI notation.

== General Rules ==

* All unit identifiers MUST be ASCII-only.
* Unit identifiers MUST be unambiguous and consistent across all AOWIS-compliant systems.
* Each physical quantity MUST map to exactly one canonical unit.
* Units MUST NOT be context-dependent or system-dependent.
* Units MUST be stable identifiers suitable for JSON, databases, and file formats.

== Requirements ==

<pre>
REQ-MEAS-UNI-001: Unit identifiers MUST be ASCII-only strings.

REQ-MEAS-UNI-002: Unit identifiers MUST NOT contain Unicode characters, superscripts, or typographic symbols.

REQ-MEAS-UNI-003: Each physical quantity in AOWIS MUST map to exactly one canonical unit identifier.

REQ-MEAS-UNI-004: Units MUST be used consistently across all AOWIS system interfaces and storage formats.

REQ-MEAS-UNI-005: Units MUST NOT be context-dependent or implementation-defined.

REQ-MEAS-UNI-006: Semantic meaning MUST be derived from the quantity field, not from the unit identifier.
</pre>

== Canonical Unit Identifiers ==

=== Length and Spatial Quantities ===

{| class="wikitable"
! Quantity !! Definition !! Canonical Unit !! EPANET Mapping
|-
| length || Linear spatial extent || m || Pipe/link length (SI-normalized EPANET model)
|-
| elevation || Vertical height relative to datum || m || Node elevation (SI-normalized EPANET model)
|-
| distance || Spatial separation between points || m || Derived geometric quantity
|-
| position_offset || Relative spatial offset magnitude || m || Not explicitly represented in EPANET
|}

=== Area and Volume ===

{| class="wikitable"
! Quantity !! Definition !! Canonical Unit !! EPANET Mapping
|-
| area || Two-dimensional spatial extent || m2 || Not directly used
|-
| volume || Storage volume || m3 || Tank volume (SI-normalized EPANET model)
|}

=== Flow and Transport ===

{| class="wikitable"
! Quantity !! Definition !! Canonical Unit !! EPANET Mapping
|-
| volumetric_flow_rate || Volume per unit time || m3_s || Link flow (SI-normalized EPANET model)
|-
| mass_flow_rate || Mass per unit time || kg_s || Not directly represented (derived)
|}

=== Pressure and Stress ===

{| class="wikitable"
! Quantity !! Definition !! Canonical Unit !! EPANET Mapping
|-
| pressure || Force per unit area in fluid system || Pa || Node pressure (SI-normalized EPANET model)
|-
| stress || Internal material stress || Pa || Not represented
|}

=== Time ===

{| class="wikitable"
! Quantity !! Definition !! Canonical Unit !! EPANET Mapping
|-
| time || Simulation or observation time || s || Simulation time (EPANET internal time normalized to seconds)
|-
| duration || Time interval length || s || Simulation duration / reporting intervals
|}

=== Electrical Quantities ===

{| class="wikitable"
! Quantity !! Definition !! Canonical Unit
|-
| current || Rate of electric charge flow || A
|-
| voltage || Electric potential difference || V
|-
| resistance || Opposition to electric current flow || ohm
|-
| power || Rate of energy transfer || W
|-
| energy || Work or transferred electrical energy || J
|-
| capacitance || Ability to store electric charge || F
|}

== Data Representation Format ==

All AOWIS measurement values MUST use the following structure:

<pre>
{
"quantity": "<physical_quantity>",
"value": <numeric_value>,
"unit": "<canonical_unit>"
}
</pre>

Example:

<pre>
{
"quantity": "pipe_length",
"value": 1200,
"unit": "m"
}
</pre>

Measurement:Units

2026-06-10T19:29:26Z

Samuel: /* Notes */

Main Page

2026-06-10T19:28:15Z

Samuel:

{{MainPageBanner}}

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

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

In less developed regions, such as rural areas and small towns in Africa, water distribution remains a significant challenge. While NGOs have been successfully supporting communities for decades by drilling wells, installing pumps, and sometimes building water towers, distributing water across a network on the surface is often difficult.

Local initiatives that take on these projects frequently encounter a situation where operating the system manually becomes unsustainable, requiring constant attention. Qualified personnel are scarce, and suitable technology to support automated or semi-automated operation is either unavailable under local constraints or too expensive.

This is where AOWIS aims to contribute: by providing an open standard for designing, deploying, and managing water and agricultural infrastructure in such environments. AOWIS supports both the planning phase—helping initiatives evaluate and design systems based on regional conditions such as topography—and the operational phase, including system monitoring, control, and maintenance.

In addition, AOWIS aims to support the training of local technicians and to collaborate closely with experienced NGOs and local initiatives that already operate and maintain such systems, in order to improve sustainability and reduce operational burden.
}}

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

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

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

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

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

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

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

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

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

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

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

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

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

<div class="hbox-row">

{{Header box
| title = Start Here
| color = yellow
| body =
If you are new to AOWIS, begin with:

* [[Concepts:Design_Philosophy|Design Philosophy]]
* [[Standard:Definitions|Definitions]]
* [[Standard:Normative_Requirements|Normative Requirements]]
* [[Modules:Module_Template|Module Template]]
* [[AOWIS:Contributor_Guide_External|Contributor Guide - External]]
* [[AOWIS:Contributor_Guide_Internal|Contributor Guide - Internal]]
* [[AOWIS:Writing_Style_Guide|Writing Style Guide]]
* [[AOWIS:AI_Usage_Guide|AI Usage Guide]]
* [[AOWIS:Research_Form_Guide|Research Form Guide]]
* [[AOWIS:Naming_Convention_Specification|Naming Convention Specification]]
* [[AOWIS:Change_Log__Versioning|Change Log & Versioning]]
* [[AOWIS:Wiki|This Wiki]]

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

{{Header box
| title = List of Requirement Pages
| color = brown
| body =
This index lists AOWIS pages that define normative requirements (MUST/SHOULD/MAY statements) and conformance rules.

'''Dev Rules''' — specs for writing and maintaining AOWIS

* '''REQ-AI:''' [[AOWIS:AI_Usage_Guide|AI Usage Guide]]

'''Technical Standard''' — system behavior and data models

* '''REQ-MEAS:''' [[Measurement:Units|Unit System Requirements]]
* '''REQ-MEAS-UNI:''' [[Measurement:Unit_Identifiers|Unit Identifiers]]
}}

</div>

{{Header box
| title = Access the Standard
| color = purple
| body =
The AOWIS standard is organized into dedicated namespaces.
These sections form the technical backbone of the project.

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

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

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

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

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

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

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

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

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

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

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

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

{{Header box
| title = Partners
| color = indigo
| body =
[[File:Afriticgroup.webp|250px|frameless|center|link=https://afriticgroup.com/]]
}}

''AOWIS is an open, evolving standard. Contributions are welcome. For contact, please visit us on [https://github.com/aowis-org GitHub]''

Main Page

2026-06-10T19:27:50Z

Samuel:

{{MainPageBanner}}

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

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

In less developed regions, such as rural areas and small towns in Africa, water distribution remains a significant challenge. While NGOs have been successfully supporting communities for decades by drilling wells, installing pumps, and sometimes building water towers, distributing water across a network on the surface is often difficult.

Local initiatives that take on these projects frequently encounter a situation where operating the system manually becomes unsustainable, requiring constant attention. Qualified personnel are scarce, and suitable technology to support automated or semi-automated operation is either unavailable under local constraints or too expensive.

This is where AOWIS aims to contribute: by providing an open standard for designing, deploying, and managing water and agricultural infrastructure in such environments. AOWIS supports both the planning phase—helping initiatives evaluate and design systems based on regional conditions such as topography—and the operational phase, including system monitoring, control, and maintenance.

In addition, AOWIS aims to support the training of local technicians and to collaborate closely with experienced NGOs and local initiatives that already operate and maintain such systems, in order to improve sustainability and reduce operational burden.
}}

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

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

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

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

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

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

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

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

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

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

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

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

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

<div class="hbox-row">

{{Header box
| title = Start Here
| color = yellow
| body =
If you are new to AOWIS, begin with:

* [[Concepts:Design_Philosophy|Design Philosophy]]
* [[Standard:Definitions|Definitions]]
* [[Standard:Normative_Requirements|Normative Requirements]]
* [[Modules:Module_Template|Module Template]]
* [[AOWIS:Contributor_Guide_External|Contributor Guide - External]]
* [[AOWIS:Contributor_Guide_Internal|Contributor Guide - Internal]]
* [[AOWIS:Writing_Style_Guide|Writing Style Guide]]
* [[AOWIS:AI_Usage_Guide|AI Usage Guide]]
* [[AOWIS:Research_Form_Guide|Research Form Guide]]
* [[AOWIS:Naming_Convention_Specification|Naming Convention Specification]]
* [[AOWIS:Change_Log__Versioning|Change Log & Versioning]]
* [[AOWIS:Wiki|This Wiki]]

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

{{Header box
| title = List of Requirement Pages
| color = brown
| body =
This index lists AOWIS pages that define normative requirements (MUST/SHOULD/MAY statements) and conformance rules.

'''Dev Rules''' — specs for writing and maintaining AOWIS

* '''REQ-AI:''' [[AOWIS:AI_Usage_Guide|AI Usage Guide]]

'''Technical Standard''' — system behavior and data models

* '''REQ-MEAS:''' [[Measurement:Units|Unit System Requirements]]
* '''REQ-MEAS-UNI:''' [[Measurement:Unit_Identifiers|Unit Names & Strings]]
}}

</div>

{{Header box
| title = Access the Standard
| color = purple
| body =
The AOWIS standard is organized into dedicated namespaces.
These sections form the technical backbone of the project.

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

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

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

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

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

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

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

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

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

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

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

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

{{Header box
| title = Partners
| color = indigo
| body =
[[File:Afriticgroup.webp|250px|frameless|center|link=https://afriticgroup.com/]]
}}

''AOWIS is an open, evolving standard. Contributions are welcome. For contact, please visit us on [https://github.com/aowis-org GitHub]''

Measurement:Main Page

2026-06-10T19:27:40Z

Samuel:

= Measurement =

Measurements are fundamental to AOWIS operations. Decisions in monitoring, control, maintenance, planning, safety, and research depend on reliable measurement data.

This Domain defines how AOWIS represents, records, exchanges, validates, and interprets measurements across water, agricultural, environmental, and infrastructure systems.

== Core Specifications ==

* [[Measurement:Units|Unit System Requirements (SI)]]
* [[Measurement:Unit_Identifiers|Unit Identifiers]]

== Subsystems ==

* [[Measurement:Elevation]]
* [[Measurement:Time]]
* [[Measurement:Quality]]
* [[Measurement:Calibration]]

== Supporting Concepts ==

* Measurement sources
* Data validation
* Uncertainty handling
* Storage & exchange rules

Measurement:Units

2026-06-10T19:27:27Z

Samuel:

Measurement:Unit Identifiers

2026-06-10T19:26:56Z

Samuel: Samuel moved page Measurement:UnitStrings to Measurement:Unit Identifiers without leaving a redirect

* Part of: [[Measurement:Main_Page]]
* Related to: [[Measurement:Units]]

AOWIS defines a canonical set of unit identifiers used in all system interfaces, storage formats, APIs, and inter-system data exchanges.

All unit identifiers MUST be ASCII-only strings and MUST NOT contain Unicode characters, superscripts, or typographic symbols.

Units are machine-readable tokens and are not intended to represent typographic or human-rendered SI notation.

== General Rules ==

* All unit identifiers MUST be ASCII-only.
* Unit identifiers MUST be unambiguous and consistent across all AOWIS-compliant systems.
* Each physical quantity MUST map to exactly one canonical unit.
* Units MUST NOT be context-dependent or system-dependent.
* Units MUST be stable identifiers suitable for JSON, databases, and file formats.

== Requirements ==

<pre>
REQ-MEAS-UNI-001: Unit identifiers MUST be ASCII-only strings.

REQ-MEAS-UNI-002: Unit identifiers MUST NOT contain Unicode characters, superscripts, or typographic symbols.

REQ-MEAS-UNI-003: Each physical quantity in AOWIS MUST map to exactly one canonical unit identifier.

REQ-MEAS-UNI-004: Units MUST be used consistently across all AOWIS system interfaces and storage formats.

REQ-MEAS-UNI-005: Units MUST NOT be context-dependent or implementation-defined.

REQ-MEAS-UNI-006: Semantic meaning MUST be derived from the quantity field, not from the unit identifier.
</pre>

== Canonical Unit Identifiers ==

=== Length and Spatial Quantities ===

{| class="wikitable"
! Quantity !! Definition !! Canonical Unit !! EPANET Mapping
|-
| length || Linear spatial extent || m || Pipe/link length (SI-normalized EPANET model)
|-
| elevation || Vertical height relative to datum || m || Node elevation (SI-normalized EPANET model)
|-
| distance || Spatial separation between points || m || Derived geometric quantity
|-
| position_offset || Relative spatial offset magnitude || m || Not explicitly represented in EPANET
|}

=== Area and Volume ===

{| class="wikitable"
! Quantity !! Definition !! Canonical Unit !! EPANET Mapping
|-
| area || Two-dimensional spatial extent || m2 || Not directly used
|-
| volume || Storage volume || m3 || Tank volume (SI-normalized EPANET model)
|}

=== Flow and Transport ===

{| class="wikitable"
! Quantity !! Definition !! Canonical Unit !! EPANET Mapping
|-
| volumetric_flow_rate || Volume per unit time || m3_s || Link flow (SI-normalized EPANET model)
|-
| mass_flow_rate || Mass per unit time || kg_s || Not directly represented (derived)
|}

=== Pressure and Stress ===

{| class="wikitable"
! Quantity !! Definition !! Canonical Unit !! EPANET Mapping
|-
| pressure || Force per unit area in fluid system || Pa || Node pressure (SI-normalized EPANET model)
|-
| stress || Internal material stress || Pa || Not represented
|}

=== Time ===

{| class="wikitable"
! Quantity !! Definition !! Canonical Unit !! EPANET Mapping
|-
| time || Simulation or observation time || s || Simulation time (EPANET internal time normalized to seconds)
|-
| duration || Time interval length || s || Simulation duration / reporting intervals
|}

=== Electrical Quantities ===

{| class="wikitable"
! Quantity !! Definition !! Canonical Unit
|-
| current || Rate of electric charge flow || A
|-
| voltage || Electric potential difference || V
|-
| resistance || Opposition to electric current flow || ohm
|-
| power || Rate of energy transfer || W || Not represented
|-
| energy || Work or transferred electrical energy || J
|-
| capacitance || Ability to store electric charge || F
|}

== Data Representation Format ==

All AOWIS measurement values MUST use the following structure:

<pre>
{
"quantity": "<physical_quantity>",
"value": <numeric_value>,
"unit": "<canonical_unit>"
}
</pre>

Example:

<pre>
{
"quantity": "pipe_length",
"value": 1200,
"unit": "m"
}
</pre>

File:Cooperation.jpg

2026-06-10T19:12:59Z

Samuel: Samuel uploaded a new version of File:Cooperation.jpg

File:Cooperation.jpg

2026-06-10T19:10:31Z

Samuel: Samuel uploaded a new version of File:Cooperation.jpg

Measurement:Units

2026-06-10T18:44:25Z

Samuel:

* Part of: [[Measurement:Main_Page]]
* Related to: [[Measurement:UnitStrings]]

AOWIS systems, components, and data models MUST use the International System of Units (SI) as the canonical unit system.<ref name="BIPM-SI">International Bureau of Weights and Measures (BIPM) — International System of Units (SI) https://www.bipm.org/en/measurement-units/si-base-units</ref><ref name="NIST-SI">NIST — The International System of Units (SI) https://www.nist.gov/pml/owm/metric-si/si-units</ref>

SI is the globally accepted standard for scientific and technical measurement and is defined and maintained by the International Bureau of Weights and Measures (BIPM).<ref name="Wikipedia-SI">Wikipedia — International System of Units https://en.wikipedia.org/wiki/International_System_of_Units</ref>

== Purpose ==

This specification establishes a single authoritative unit system for all physical quantities represented by AOWIS.

The use of a single unit system reduces implementation complexity, eliminates ambiguity during data exchange, simplifies validation and testing, and improves interoperability between independent AOWIS implementations.

== Requirements ==
<pre>
REQ-MEAS-000: The International System of Units (SI) is the authoritative unit system for all physical quantities represented by AOWIS.

REQ-MEAS-001: All numerical values representing physical quantities within an AOWIS-compliant system MUST be represented using SI units.

REQ-MEAS-002: Implementations MUST produce results that are numerically consistent with SI-based processing.

REQ-MEAS-003: Implementations MUST NOT introduce conversion artifacts, rounding errors, or precision loss that are outside the documented precision of the measurement.

REQ-MEAS-004: Interfaces between AOWIS-compliant and non-AOWIS-compliant systems MUST convert all non-SI physical quantities to SI units before they become part of the AOWIS measurement model and MUST convert from SI units when exporting data to systems requiring non-SI units.

REQ-MEAS-005: User interfaces MUST clearly indicate the unit associated with every displayed or entered numerical value representing a physical quantity.

REQ-MEAS-006: Each physical quantity in AOWIS MUST be mapped to exactly one canonical SI unit.
</pre>

== Notes ==

This specification governs how physical quantities are represented within AOWIS.

External systems MAY use alternative unit systems. Any required conversion between such systems and AOWIS is performed at the system boundary in accordance with REQ-MEAS-004.

== References ==
<references />