To perform the audit you'll need to provide specific configuration files and parameters. This guide walks you through the required components and their formats.

How It Works

To perform the audit process we require careful preparation of configuration files to ensure optimal system performance. While this guide outlines the recommended standard formats, we understand that every water utility has unique data structures and requirements.

The setup requirements are organized into three main categories:

1. Network Model: The EPANET file that describes your water distribution system
2. Area Definitions: Geographical and operational information about your network zones
3. Sensor Configuration: Detailed specifications of your monitoring equipment

Each category has specific format requirements and essential parameters that must be provided for successful platform implementation. Let's examine each component in detail.

<aside> If your existing data formats differ from these specifications, please contact the HULO support team ([email protected]). We can work with you to accommodate custom data formats and help streamline the integration process.

</aside>

1. Network Model (EPANET INP File)

The EPANET INP file serves as the foundation of your water distribution network model. This file contains:

• Network topology (nodes, links, and their connections)
• Physical characteristics of pipes and other components
• Operational parameters and controls
• If Node and Link names do not match sensor_ids (see below 3. Sensor Configuration) please supply a CSV/XLSX how to map the sensors with the network model

<aside> ⚠️ Ensure your EPANET file is properly validated before uploading to HULO.

</aside>