This topic introduces the 1D model in the sample database and guides you through key workflows for reviewing, designing, simulating, and analysing a drainage network.
You will learn how model data is structured, how supporting objects are used to configure simulations and design, and how to interpret results.
Open the 1D network from the Model Group in the Explorer Window to display it in the GeoPlan.
The model includes:
Select any object in the GeoPlan to view its properties. Use the Object properties window to inspect full datasets for the selected object. Nodes define key attributes such as levels, storage, and connectivity within the network.
Understanding how the model is structured and how object properties are organised allows you to confidently navigate and inspect network data before applying design or simulation workflows.
The sample model includes predefined objects that control validation, inputs, and outputs.
See Model group context menu for an overview of the features available through the menus visible on the image below.
Use validation to check the network against defined rules.
Validation highlights issues but does not prevent simulation, allowing you to review and correct problems without interrupting your workflow.
This helps you identify data inconsistencies early and ensures the network meets required design rules before running simulations or applying automated design.
See Validating networks.
Use inflow or level data to represent upstream conditions without modelling the full system.
This allows you to represent upstream conditions without modelling the full contributing system, reducing model complexity while preserving realistic hydraulic behaviour.
Use rainfall events to drive storm simulations.
Rainfall events define the driving input for storm simulations and determine how the network responds under different return periods and durations.
See Rainfall events.
Use wastewater profiles to simulate sanitary flow.
This enables you to represent realistic flow patterns over time, reflecting how demand varies throughout the day based on population and land use.
Control which outputs are generated during simulation.
This helps optimise simulation performance and storage by focusing only on the outputs that are relevant to your analysis.
See Results.
Long sections provide a profile view of the network along a selected path.
They are particularly useful for reviewing network connectivity and assessing design changes before and after applying Network design.
This provides a clear engineering view of network behaviour along a flow path, making it easier to identify connectivity issues, slope inconsistencies, and the impact of design changes.
See Long section window.
You can also automate long section generation using Ruby script.
Scripts can be used to generate multiple upstream-to-downstream paths and store them as selection lists.
Scenarios allow you to compare alternative network configurations.
Use scenarios to test design changes, alternative inputs, or different modelling assumptions.
This allows you to test alternative designs or assumptions without modifying the base model, making it easier to compare outcomes and evaluate different approaches.
Network design can be used to size pipes based on defined Design constraints and rainfall inputs.
Network design is a key workflow in this sample and allows you to automatically size pipes based on defined Design constraints available pipes (see Pipe network catalog) and rainfall inputs (see IDF curve).
The design workflow uses supporting objects:
You can:
The Design report explains how each design decision was made, including governing constraints such as flow, velocity, depth, or connectivity.
This enables you to automatically generate hydraulically consistent designs and understand how design decisions are made through the Design report, helping you optimise networks based on engineering priorities.
Simulations calculate how the network responds over time to rainfall, inflows, and other inputs.
To run a simulation:
Simulation parameters control how calculations are performed. Default values are configured for typical accuracy and do not normally require adjustment .
This allows you to evaluate how the network performs under defined conditions and assess whether it meets design and operational requirements.
Logs provide a record of simulation activity and highlight issues affecting reliability.
This enables you to diagnose issues, understand system behaviour over time, and identify areas of concern such as surcharge, flooding, or capacity limitations.
This allows you to observe how the network behaves during the simulation.
See Graphing.
Results include both time-varying values and summary values such as maximum depth and flow.
You can also use grid reports and result post-processing tools to compare outputs across multiple simulations and identify trends or worst-case conditions.
This model helps you learn how to:
You can extend this workflow by:
Proceed to 2D Sample Model: Workflows and capabilities to make the most out of the sample database.