Introduction to ICM

 General Overview of ICM

 Database Functionality
 Navigating the Network
 Version Control and Scenarios
 Urban Drainage Models
 Event Data
 Running a simulation
 Analysing the results
 Creating a simple 1D-2D Model
 Advanced Mesh Building
 New to the InfoWorks Suite

 Ability to model the complete above and below

ground drainage system (natural and engineered) in
one model

Evaporation

Precipitation

Evaporation

Surface runoff
Coast

Groundwater Estuary
 Single simulation engine
 Manholes, pipes, inlets
 Natural and man-made channels
 Catchment and floodplain
 Common hydrology
 1D and 2D integrated solution

 New User Interface

 New multi user version control system
 New editing methodology
 New grouping structure
 Recycle bin
 • New User Interface
 New Multi-User Version Control System
 More intuitive
 Less clicks
 Easier to use

• Latest Technologies
 Designed for Windows 7, Vista and Xp
 Supports all 64-bit operating systems

• Improved GIS experience

 Multi GIS platform support
 ESRI ArcGIS
 MapInfo Professional
 •Tree View
 New grouping structure
 New editing methodology
 Recycle bin

•Tabbed Windows
 Group docking windows together
 Easy switching between views
 Simulation Server
 Simulations can be run on
• Stand-alone workstations
• Within a Workgroup sharing computer resources
• Within an Enterprise System with dedicated servers and
central store
 Supports the concurrent running of multiple
simulations, even with a single licence
 Users are able to monitor and control the progress
of selected simulations
 Possible to re-schedule the queue and priority of
simulation jobs
  Hardware Support
 Support for a wide range of Intel and AMD CPU’s,
including multi-processor units
 InfoWorks ICM Simulation Engine is multi-core aware
(fully tested up to 32 cores)
14.00
13.00
12.00
Simulation Time (hrs)

11.00
10.00
9.00
8.00
7.00
6.00
5.00
4.00
3.00
2.00
1.00
0.00
2 4 6 8 10 12 14 16 18 20 22 24 26 28 30 32
Number of cores used
 GPU detection for accelerated 2D calculations
 Detects all nVidia CUDA enabled GPU’s with
Compute Level 2.0 or higher
• Tesla GPU Computing Products
• Quadro Products
• NVS Products
• GeForce 8, 9, 100, 200, 400, 500-series
 GPU Cards
 GPU acceleration is significant!
 Example : 2D Model, Auckland NZ
 1,500Ha area with rainfall on 100% of the mesh.
 Just under 1 million 2D elements.
Core2Duo T7700 – 32bit PC Dual Intel Xeon E5645 – 64bit
29hrs, 55 mins, 41 seconds with nVidia Telsa 2050 GPU

Dual Intel Xeon E5645 – 64bit 18 minutes, 7 seconds

2hrs, 20mins, 53 seconds
1.49Gb RAM
1.15Gb RAM
Database Functionality
 Database Functionality
 Master database
 Managing model data and contains all data including results and
ground models

 Transportable Databases
 Move data between databases within an organisation
 When sharing data with external organisations
 When sending data to Innovyze as part of a support request

 Snapshot files
 Hold network data only
 Setting up the database

 Setting up the database from the start menu:

 Create a new database

 No need for Admin program
 Updating Databases
 It is possible to update databases, this makes those
created by earlier versions of the software usable.
 The database is automatically saved before updating.
 This process is irreversible.
 User-defined flags
 Useful for QA and model auditing
 Tracking changes
 Default flags
 Can add your own
 Model Group
 Top level of data organisation.
 Contains run groups and work data
 Can have other Model Groups to further sub-divide your
data
 To Create a Model Group:
 Right-click on the master database, or an existing model group.
 Select ‘New’, then choose ‘Model Group’.
 Asset groups to store Infonet data
 Map Controls
 ArcGIS
 ArcEngine
 MapXtreme
 Map Free (i.e. no map control)
 Support for ArcGIS server map services
Navigating the Network
 Networks
 Contain the physical attributes of a model:
 Nodes: points at which computation takes place
 Links: connect nodes together
 Polygons: storage areas and subcatchments
 Survey Objects-Raw Data
 2D Objects
Navigating the Network
 Properties view
 Every network object has a property
sheet
 Geoplan view
 Visual display of the network
 Grid view
 Useful for global edits
 Properties View
 Every network object
 Change layouts
 Save layouts (can reset
layouts)
 Copy to Excel
 In-line validation to
instantaneously check values
 Can also view results in
Properties view
 Geoplan View
 Visual display of
network
 Zoom and pan
 Add background GIS
layout
 Add ground models
 Labels
 Properties and themes
 Grid Views
 Global Edits
 Cut, copy and
paste columns
 Set and adjust
values
 Can also view
results in grid
view
 Properties and Themes
 Change appearance of network objects
 Theme different properties (eg conduit width, node type)
 Add labels-Auto or Custom
 Theme model results
 Can save theme groups
 Properties and Themes
In the case of the conduit width there are too many
individual vales to have the theme set up this way, change Add a unique theme by Tailor‐make your legend by
this to a continuous range here incorporating an SQL editing these check boxes

To Auto-Scale the range and to Auto-Theme To add or remove the number of ranges
the colours simply double click on these tabs that your theme uses, use the
add/subtract icons
 Other Tools
 Long Profile

 3D View
 Ground Models
 Gridded or TIN DTM’s:
 Grids:
• ESRI *.asc
• MapInfo *.txt
• IW *.igm
 TIN
• ESRI *.shp
• ESRI (ArcInfo) *.tin
• IW *iim
 GIS Layer Control
 Add Background layers
 Aerial Photography
 GIS layers
 Web Map Services
 USGS EROS
 UK BGS
 Search network
 Search by X,Y Co-ordinate
 Search by Asset ID
 Search by GIS and street locations
 Tracing Tools
 Upstream/Downstream Trace
 Check Connectivity
 Pipe Direction Trace
 Check pipe direction
 Connectivity Trace
 Check non-connected sub-networks
 Intermediate Paths Trace
 Find routes between two selected nodes
 Proximity trace
 Check node connectivity within a specified distance
 Practical 1-2
 Database Functionality
 Navigating the Networks
Version Control and Scenarios
 Version Control and Scenarios
 Model created in a ‘Base’ network
 Changes ‘committed’ to the master database
 Uncommitted changes can be undone/redone
 Commit history-Keep Notes!
 Scenarios to test options
 Manage scenarios
Saving changes
 Save or ‘commit’ your
changes
 Work carried out prior to
committing changes is saved
to a temporary cache
 Closing Infoworks won’t
cause loss of data but
uncommitted data is not fixed
to the master database
 Similar to ‘check in’ on
Infoworks CS/RS/WS/SD
The Commit History
 Scenarios
 Scenarios to test options
 Full management of
scenarios-QA
 Each scenario needs
validating
 Can be branched from one
another
 Can run multiple scenarios
within a single run
 Validation
 Checks for missing data, common errors and
inconsistencies
 On-the-fly validation
 Prompted before commit
 Validation results are colour coded according to severity.
 Validation Colour Coding
 Red error messages:
 Action is required before run can take place.
 There is an error that needs to be resolved
 Yellow warnings message:
 Action might be required, although run can still be carried out.
 Messages should be reviewed and dealt with if necessary.
 Purple information messages:
 No action needed
 Practical 3
 Version Control and Scenarios
Building an Urban Drainage
Model
The basic components of an
Urban Drainage Network

Subcatchments Links Nodes

Represent a specific
Subcatchments are point in the
assigned to nodes and Links are structures that
network. There are
represent the physical connect nodes, these may
four different types
area from which a node be:
of nodes:
collects water.
Conduit
Subcatchment parameters
Flap Valve () Manholes:
Flume
detail how an event
Orifices ( ) Storage
(wastewater, rainfall,
Pump
trade waste, groundwater
River () Break:
etc) is applied to the
Screen
node. () Outfalls
Siphon
Sluice
Break nodes do not
User Control
allow for any
Weir
storage and should
be used only with
pressurised pipes.
Urban Drainage Model
 Nodes
 Represent a physical structure
 5 types of node:-
– Manholes-a node with shaft and chamber storage
representing a manhole or other point at which water enters the
system
– Outfalls-a node where water leaves the system
– Break Nodes-a node used at an intermediate point in a
conduit (ie, a change in gradient or dimension). Also used to
connect river reaches.
– Storage Nodes-a node used to define a storage structure
– 2D outfalls-an outfall node where flow discharges to a 2D
zone and vice versa.
Node Properties
 Links
 Represent the connection between 2 nodes
 Could be:
 A conduit joining two nodes
 A control, representing a weir, pump or other flow control device
 A bridge
 A channel
 A river reach
 A single node may have many links to other nodes
 Upstream/Downstream ends, name based on upstream
node.
Link Properties
 Subcatchments
 Area from which a manhole collects water
 Allocate:-
 Rainfall
 Groundwater baseflow
 Wastewater drainage
 Trade flow profile
 Population data
 Associated Landuse and runoff surfaces
 Various Runoff models and Routing methods
Subcatchment Properties
 Runoff Models
 Fixed Percentage Runoff
 Wallingford Procedure (Fixed) PR
 New UK (Variable) PR
 USA Soil Conservation Service method
 Green-Ampt
 Horton
 Constant Infiltration
 Horner
 ReFH
 Building an Urban drainage
network
 Open Data Import Centre
 Update from CSV
 Import from IWCS model
 Snapshot file from Infonet
 Add Manually directly to the network
 Open Data Import Centre

• CSV files
• MapInfo Tab/MIF GIS
files
• ArcGIS shape files
• Tab separated files
• Access database files
• Others (Oracle, SQL
servers, Geodatabases,
xml)
 Migrating from Infoworks CS…
 1 to 1 mapping from CS to ICM
 IWCS Admin Version 10.5 or later
 Right Click on master database
 Export to Infoworks ICM
 Select Model data to be exported
 …to ICM
 Right Click on Master Database
 Import model data from Infoworks CS Migration file
 Manually Editing Networks
 Nodes
 Links
 Raingauges
 Subcatchments/Storage Areas
 Point
 Line
 Polygons
 Inference
 Able to infer missing data
 Nodes
 Coordinates
 Ground levels from GM
 Ground levels from surrounding nodes
 Ground level from fixed cover level
 Ground level from adjacent nodes cover level
 Conduit
 Size and Shape
 Invert from Invert Level
 Invert from soffit level
 Invert from gradients
 Invert interpolate from inverts
 Headloss type and coefficient
 Can order Inference priority
 Control Structures
 Pumps
 Variable Speed
 Variable frequency
 Orifice
 Limiting discharge
 Weir
 Variable crest
 Variable width
 Sluice Gate
 Variable gate height
 Principle RTC Elements
 Regulators:-
 The device that performs the action (eg a pump, a gate).
 Ranges:-
 Describes when the regulator should operate (eg at a certain
level/flow).
 Rules:-
 Describes how the regulator should operate (eg, whether a
pump is on or off).
 RTC Editor

 Under Windows->Grid Windows->RTC Editor

 Practical 4
 Building and Importing an Urban Drainage
network
Building a River Model
 River Network
 Cross Sections
 River Reaches
 Banklines
 Break Nodes:-
 Junctions
 Inflows
 Structures
 Connecting urban drainage models
 Outfalls
 Importing Existing River
Networks
 Can be imported from:-
 Infoworks RS via csv files
 ISIS via .dat files
 HecRAS Converter coming soon…
 Cross-Sections and Survey
Lines
 Can be imported in a range of formats
 GIS files
 .csv files
 .txt files
 Represent the raw data
 Not used in modelling
 Build the River Reach
 Select Cross-Sections and River Centre Line
 Build Sections from Lines
 Dotted line indicates a River Section rather than Cross-
Section
 River Sections are linked
 Needs to be redone if changes made
 Adding River Banks
 Banklines represent flow from River channel to:-
 1D Storage Areas
 Other River reaches
 2D Zone

 Weir Equation

Process Required Data Bank Line Bank Line

Vertices path
Create from Cross-Section At cross- Follows cross-
Section Ends survey sections section ends

Create from Accurate and As specified by User defined

Ground Model high-resolution the user
ground model

Create from Accurate Bank At survey Where

Bank Survey Survey points surveyed
 Create From Section Ends
 Bank Lines follow edge of
cross-sections

 Option to follow river link

 Requires Cross-Section
Survey Data
 Create From Ground Model
 Can be any drawn line

 Sample Line Elevations

from Ground Model

 Choose Sampling Interval

 Build Banks from

Selected Lines

 Requires an Accurate
Ground Model
 Create From Survey Data
 Use Open Data Import
Centre to import survey
data

 Build banks from selected

lines

 Follows path of the bank

survey

 Requires Bank Survey

data
Set Discharge Coefficient and
Modular Limit
 Building a Boundary
 Creates a boundary polygon for a selected river reach
 Used for Flood Mapping
 Acts as a void for 2D Zones
 River Reach Creation Process
 Select River Centre Line

 Build Sections from Lines

 Create Banklines from Section Ends or Build banks from

selected Lines

 Select River Reach

 Build Boundary from Bank and section ends

 Build Bank Connections

River Reach Properties
 Practical 5
 Importing Survey data and building a river reach
Structures
 Structures and Ancillaries
 Infoworks ICM has a range of Ancillary links to control
flow:-
 Bridges
 Culvert inlet
 Culvert outlet
 Flap valves
 Flumes
 Inline banks
 Irregular weir
 Orifice controls
 Pumps
 Screens
 Siphons
 Sluice gates
 User defined controls
 Weirs
 Structures
 Link between to 2 break nodes
 Different Parameters for each structure
 Properties sheet
 See Help section for structure details
 Bridges
 Based on Afflux Estimator System (similar to HecRAS
approach)
 Calculates afflux
 Expansion and Contraction Reaches
 Multiple openings
 Bridges
 5 cross-sections:
 Upstream link (Y4)
 Upstream face (Y3)
 Downstream face (Y2)
 Downstream link (Y1)
 Deck Level (treated as Irregular weir)
 Contraction and Expansion
 Energy losses associated with the change in river shape
at a bridge
 Loss coefficients:-
 Expansion loss
 Contraction loss
 Bridge Opening
 Conduit link for each bridge opening
 Piers and a user-defined pier loss coefficient
 Openings should not be blocked.
 Bridge Losses
 Contraction losses – based on the changes between the u/s link
section and u/s bridge section

 Inlet losses* – based on the geometry of the u/s bridge opening

 Friction losses – based on the roughness and length of the bridge

opening

 Pier losses*

 Outlet losses* – based on the geometry of the d/s bridge opening

 Expansion losses – based on the changes between the d/s bridge

section and d/s link section

*optional
 Connecting an Urban drainage
network to a river network
 A river break node is required for all junctions
 Level is important
 Connect urban drainage network via the appropriate
link:-
 Conduit
 Flap valve
 Culvert outlet
 Practical 6 and 7
 Building a bridge and adding ancillaries
 Linking a River and Urban Drainage Model
Event and Boundary Data
 Event Data
 Store time-varying boundary information for a network
 Can have multiple event objects for one network.
 Types of event data:-
 Inflow
 Rainfall Event
 Trade waste
 Waste water
 Level
 Ground infiltration data
 Pollutograph data
 Event Data
 Typical upstream boundaries are:
 Flow-time data
 Subcatchment Hydrological boundary based on rainfall runoff
model ( ReFH, Wallingford procedure etc…)
 Waste/Trade Inflows
 Typical downstream boundaries are:
 Stage-time data
 Stage-flow data (rating curve)
 Outfall
 Improper specification of boundary conditions often
leads to model instability.
 Rainfall
 Subcatchments are assigned a rainfall profile
 Design or Observed
 Design:-
 Australian
 FEH
 French (Desbordes)
 Hong Kong
 Malaysia
 Qm French
 ReFH
 SCS/NRC
 UK
 Design Rainfall Generator
Initial Conditions: Set the
catchment initial states Antecedent Depth: This is the
here. rainfall depth in mm that has
fallen in the hour immediately
prior to the storm.
UCWI: The Urban
Catchment Wetness
Index. The antecedent
wetness of the
catchment for the
Wallingford Runoff
Model Set a profile: Summer, winter or
Synthetic

Duration: The duration of the

Return Period: The rainfall event in minutes
average period between
occurrences of an event
greater than or equal to Multiplying factor: Factor allowing scaling of the design rainfall
a given values
 Observed Rainfall
 Manually
 Event file (old Hydroworks format)
 From CSV files (Infoworks format)
 Generic .csv files
 StormPac files
 Downstream Boundaries
 Level-Time varying level data which can only be applied to an
outfall. Relative to a datum.

 Outfall-Node where flow leaves the system.

 Stage-Discharge Relationship-added as a user control link

with a head-discharge relationship. Needs converting, relative to the
invert level.

 2D Outfall-Discharges to the 2D mesh (and can use 2D level as

inflow to 1D network)
 Practical 8
 Setting up Event Data
Running a Simulation
 Running a Simulation
 Simulation Parameters

 Initialisation: This will set up the initial state of your

model prior to the modelling runs

 Start from empty and fill up until a steady state is

reached-No need for Initial Conditions

 Simulation: Modelling runs

Running a simulation
New Simulation Server

GPGPU GPGPU
 Simulation Control
 Manage existing and queued runs (and 2D meshing
jobs)
 Pause
 Cancel
 Re-schedule
 Re-Prioritise
 Details of existing run
 Status
 Machine
 Simulation Progress Window
 Control initialisation and simulation of a run
 Pause
 Continue
 Stop
 Cancel
 Provide convergence info
 1D Only
 Link/Node fails

 Will cycle through simulating jobs

 Simulation Icons
 The colour of the icon represents the degree of success.

 Results unavailable
 Results currently unavailable
 The simulation failed
 The simulation completed successfully
 The simulation complete with minor errors
 The simulation failed with convergence failure
 Practical 9
 Running a simulation
Analysing Results
 Results Analysis
 Text-Based
 Grid Results
 Graphical Results
 Results Themes
 Results Export
 Run logs
 The run logs show:
 Overview of run parameters
 Timestep information
 Warnings and error messages
 Details of non-convergence
 Performance of simulation
 Accessed by right-clicking
on coloured simulation icon.
 PRN Files
 Overview of network results
 Maximum results for nodes and links
Result-Properties
Results-Graphs and Grids
Results-Geoplan Themes and
Long Profile
 Results
 More options when exporting results to csv
 Ability to compare results at certain locations.
 Results SQL
 Expressions
 SQL Select
 Powerful Tool
 Standard SQL language
 Practical 10
 Analysing the results
1D-2D Modelling
 Why 2D?
 2D allows for the depth-averaged solution of the St
Venant Equations, for depth and velocity in two
dimensions

 Why?
 Represent routing of flow in 2 directions
 Accounts for mass as well as momentum
 Urban Environments
 Complex river/floodplain systems
 ICM 2D
 ICM allows for the depth-averaged solution of the St
Venant Equations, for depth and velocity in two
dimensions

 The solution uses a finite volume method, based on a

Gudonov Scheme and the so-called Riemann Solvers

 The model is semi-implicit and therefore, Courant

Friedrichs Lewy condition must be met
 2D Mesh
 The area to be modelled is discretised into a triangular
mesh

 This is based on user defined parameters such as

maximum triangle area

 These triangles may be aggregated, based on the

minimum virtual element area
2D Zone Properties
 Mesh Resolution
 A higher resolution mesh will more accurately
represent the underlying topography than a lower
resolution mesh

 A higher resolution mesh will take longer to run than a

lower resolution mesh

 Compromise between detail and speed of simulation

 Mesh Messages
 QA
 Spot Errors
 Check visually
 If a mesh vertex coincides
with a hole in the ground
model it will reduce the
triangle or element
elevation leading to
spurious results
 Long thin elements
 Mesh Info

 Mesh Summary field

appended
automatically

 Useful to keep track

of which ground
model was used to
create mesh
 1D-2D Modelling
 Traditionally models are 1-dimensional.
 Struggle to represent complex floodplain flow
mechanisms.
 Use 2D models
 Couple them together
 Point and linear coupling:-
 2D Manholes
 2D Gullies
 2D Inlets
 2D Outfalls
 Banklines
 Inline banks
Point vs Linear Coupling
Point Linear

Type 2D Outfall, 2D Bankline, inline

Manhole, 2D bank
Gullies, 2D Inlets
2D Applied to a Applied to
single mesh multiple mesh
element elements
Approach Variable Weir Equation

Uses Manholes, Gullies Gullies, River

banks, River
channels
 Banklines
 Banklines and Inline Banks
 Connect from 1D-2D based on weir equation

Water surface in channel Spill from Spill from

channel to storage to
storage channel Water surface in 2D Zone

Embankment top
+ve -ve
No free Drowned free
flow flow flow flow Datum
Section 1 Section 2
 Nodes with 2D Flood Types
 Can also connect sub-surface nodes (Manhole, Outfall
2D) to 2D
 Exchange of water depends on flood type:-
 2D-weir equation where weir crest level is ground level and crest
length is node shaft circumference

 Gully 2D-head discharge relationship as specified

 Outfall 2D-discharges into 2D mesh element

 Inlet 2D-user defined inlet parameters

 2D Inlet Nodes
 Head Discharge
 User Specified Equation
 Flow Efficiency
 User Entered parameters*
 Continuous grate Inlet
 Continuous curb-opening Inlet
 Continuous UPC Grate Inlet
 Sag Grate Inlet
 Sag Curb-opening Inlet
 Sag Combination Inlet
* based on FHWA HEC 22 Urban Drainage Manual
 2D Zone Boundaries
 Boundary types:

 Vertical wall
 Normal Boundary
 Critical condition
 Supercritical condition
 Dry

 Note these options specify how water

leaves the 2D Zones

 Water can only enter through a

designated boundary or connection
 2D Boundaries
 2D Line Boundary
 2D Point Source
 Direct Rainfall
 Infiltration Polygon
 2D Run Options
 Depth:
 Depth threshold used to
determine whether to
consider a mesh element
wet or dry.

 Mesh elements with depth

of water below this value
will be considered dry and
a zero depth will be
displayed in the results.

 Only mass conservation

will be considered in
elements with depth below
this threshold.

 Typical value: 0.001 m

 2D Run Options
 Momentum:
 Depth threshold used to
determine whether to
consider momentum in a
mesh element or not.

 Movement of water will not

be calculated for mesh
elements with depth of
water below this value; only
mass conservation will be
taken into account.

 Typical value: 0.001-0.01 m

 Default value: 0.001 m

 2D Run Options
 Velocity
 Mesh elements with water
velocity below this value
will have velocity reset to
zero in terms of momentum
calculations.

 Typical value: 0 m/s

 2D Run Options
 Advanced
 Ignore rain falling on dry
elements
• used to speed up sims
when direct rainfall used
 Adjust bank levels based
on adjacent element
ground levels
• used to overcome
instabilities caused if bank
level is higher than mesh
elevation
 Link 1D and 2D
Calculations at minor
timesteps
• Used to overcome flow
oscillations at banklines
GPU Cards
 GPU Cards
 GPU acceleration is significant!
 Example : 2D Model, Auckland NZ
 1,500Ha area with rainfall on 100% of the mesh.
 Just under 1 million 2D elements.

Core2Duo T7700 – 32bit PC Dual Intel Xeon E5645 – 64bit

29hrs, 55 mins, 41 seconds with nVidia Telsa 2050 GPU

Dual Intel Xeon E5645 – 64bit 18 minutes, 7 seconds

2hrs, 20mins, 53 seconds
1.49Gb RAM
1.15Gb RAM
 2D Steady State
 Steady State
 Turns on ‘Sleep mode’
 Automatic globally
 Can be switched on for local elements
 Practical 11
 Creating a Simple 1D-2D Model
2D Results
 Results
 Flood extents can be shown for a 2D model results using
either:
 2D triangles
 Flood

 Flood extents for 1D model results always use the Flood

(thememapper) approach

 If both methods are used, results will be superimposed

on each other, important to ensure only one method
selected
 Results
 2D triangles:

 Edit 2D Zone Theme

 For depth2d, min value

must be larger than zero

 Can create expressions

based on initial conditions
(joined) or results (sim)
 Results
 2D triangles:
 Can be themed on many
variables

 Hazard2d always max

• HR = d x (v + 0.5) + DF
– Where:
– d = depth flooding (m)
– v = velocity (m/s)
– DF = Debris Factor
• Debris Factor:
– 0.5 for depths < 0.25m
– 1.0 for depths > 0.25m
 Results
 Flood:

 Edit Flood Theme

 Min depth can be set to

zero
 Results
 2D arrows:

 Right click in GeoPlan,

select Themes, 2D arrows
 Results
 Pick 2D mesh:

 Gives results information

about a mesh triangle
 Results
 2D Results

 Results Points (2D)

• Depth
• Direction
• Elevation
• Froude Number
• Speed
• Unit Flow
 Results Lines (2D)
• Flow through line
 Results Polygons (2D)
• Flow through polygon
boundary
• Volume enclosed by polygon
 Results
 Export 2d results mesh to
shapefile

 Collection of polygons
(triangles), with properties
associated

 This functionality will

allow the users to
manipulate 2d results
outside of the IW
environment
3D Results
Advanced Mesh Building
 Roughness Zones & Polygons
 Roughness zone created in from new other objects
window

 Roughness type must be set to ‘value’

 Roughness polygon (with geographical attributes)

created and associated with roughness zone

 Allows roughness’ to vary within a 2D simulation polygon

Roughness Polygons
 Exclude option – allows
user to force triangles
along roughness zone
boundary
 If selected, roughness for
triangle will be taken as
roughness at triangle
centroid
 Mesh Polygons
 Able to edit mesh directly
 ‘Unblock’ blockages to flow
routes
 Increase mesh resolution
 Update outdated ground
levels
 Determine true extent of
flooding
 Mesh Polygon
 Allows for the triangle
size to vary within a
singular 2D simulation
polygon

 Maximum triangle size

must be greater than the
minimum mesh element
size specified in the 2D
simulation polygon
property sheet unless
new minimum element
size selected
 Mesh Polygon
 The elevation of the mesh
can be adjusted using the
mesh polygon

 Either raised or lowered

with respect to the ground
model or set to an
elevation
 Practical 12
 Adding Mesh Zones and Roughness Zones
 Creating the 2D Mesh

 Voids, breaklines
and walls can be
included in the
meshing process

 These can be:

• External files (shp,
tab…)
• Layers currently
displayed in the
GeoPlan (dwg…)
• Polylines/polygons
(must all have the same
category specified in
order to select them)
 Voids
 Polygons which have vertical walls
 Can be used to exclude areas from the mesh, to
simulate flow round buildings for example
 Voids
 Voids can cross the boundary of a 2D simulation
polygon, as long as it does not cross a bankline

 If this occurs, an error will occur during meshing and no

mesh will be created
 Breaklines
 Enforces mesh triangle edges to lie along the polyline

 If stored within IW ICM, must be as a general line with an

associated category

 Aggregation of mesh triangles (into mesh elements) can

occur across a breakline
 Walls/Porous Walls
 Walls, with an infinite height, can be included in the
meshing process as a general line with an associated
category

 Alternatively, a porous wall can be used, these are

picked up automatically and do not need to be specified
in the mesh generation property sheet
 Walls/Porous Walls

 Porous wall options:

 Porosity:
• 0 – no flow allowed though
• 1 – as if wall does not exist

 Crest level:
• Infinite
• Height (m above ground model)
• Level (m AD)

 Collapsing Walls
 Walls/Porous Walls
 Porous wall options:
 Collapsing Walls:
• Allows for the wall to be breached
based on a threshold
 Either:
• Never
• Partially – only segment of wall
adjacent to element in which
threshold met will collapse
• Fully – complete collapse when one
or more elements adjacent to wall
reach threshold
 Thresholds:
• Depth
• Elevation
• Velocity
• Unit Flow
• Total Head
• Force per unit length
 Porous Polygons
 Porous Polygon options:
 As porous walls
 2D Linear Structures
 Walls and Weirs:
 Crest level (constant or variable)
 Porosity, headloss and a friction coefficient
 Flow direction (unidirectional or bidirectional)
 Orifices/Sluice Gates to come in ICM 3.0
 2D Bridges in the future
2D Linear Structures
 Practical 13
 Adding Mesh Editing
IT Implementation
 Database Types
 Standalone
 Individual Users
 Small groups over a reliable LAN

 Workgroup
 Multiple Users
 WAN
 Requires a workgroup co-ordinator running to
manage communications with the master databases
 Component Parts
 Infoworks ICM Workgroup Client
 User Interface
 Simulation Engine
 Infoworks ICM Remote Agent
 Simulation Engine
 No User Interface
 Infoworks ICM Workgroup Data Server
 Available in 32- and 64-Bit editions
 Licensee can mix ‘n’ match model build and simulation
seats as required
 IT Setup
Specialised Dedicated
Engine Server Engine Server
GPGPU
Remote Remote
Agent Agent
Engine Engine
Central Server

Remote
Agent
Results Coordinator
Store
High Performance
Computer Server

Local
Local
Agent UI
Local Agent
Agent
Engine UI
UI
UI Terminal
UI
User PC Server
User PC
 IT Implementation
 Supports GPU
 Supports Multi-Core Processing
 Multiple Runs with a single license
 Hardware Support
 Hardware Support
 Multiple Simulation jobs can execute concurrently on a given
agent with a single licence
 A limit can be set on the number of threads used by an individual
simulation job
 Summary
 Database functionality
 Version control
 ICM Interface
 Urban Drainage Networks
 River Networks
 Bridges and Structures
 Running Simulations
 Analysing Results
 1D-2D Modelling
 IT Implementation
Water Quality Modelling in ICM
 Structure
 Introduction
 Determinants
 Inputs
 Dissolved Oxygen
 2D
 Results
 Introduction
• Dynamic transport simulation module for 1- and 2-
dimensional river and estuarine networks
• Water Quality and cohesive sediment transport
• Uses flows generated by ICM
• Based on ISIS Quality
Water Quality Modelling Process
Inflow and Level
hydrographs

Runoff Hydraulic Model Hydraulic Results

Trade and Wastewater

Network Initial State
Inflows

Washoff Water Quality Model Pollutant Results

Pollutant Graph
 Water Quality Variables
 Capable of simulating a range of water quality variables
including:-
 Conservative Determinants
 Decaying determinants
 Coliforms
 Sediment
 Salt
 PH
 Temperature
 Dissolved Oxygen
 Determinants
 Biological Oxygen Demand (BOD), Chemical Oxygen
Demand (COD), Dissolved Oxygen (DO)*
 Nitrogen
 Total Kjeldhal Nitrogen (TKN)
 Ammoniacal Nitrogen (NH4)
 Nitrites and Nitrates (NO3 and NO2)*
 Phosphorus
 pH*
 Salt*
 Water Temperature*
 Coliforms*
 User defined determinants
 Water Quality Input Data
• Pollutographs-Concentration data specified at flow
boundaries
– rivers
– other large inputs ( sewage treatment works)

– downstream boundary (estuaries)

• Trade and wastewater events

• Surface Washoff/Gully Pot Flushing
 Pollutographs
 Defines concentrations for dissolved determinants and
sediment fractions.
 Applied to a particular node, 2D Point source or 2D
Boundary.
 Associated with an Inflow event.
 Each determinant treated separately.
 Trade/Wastewater Events
 Daily patterns of trade or domestic waste from one or
more sub-catchments.
 Wastewater event describes per-capita flow
 Trade flow describes single source flow.
 Weekday/Weekend Settings
 Trade/Wastewater events are essentially the same.
 Trade Events

Should be
set to 1
Wastewater Events
 Surface Washoff and Gully Pot
Flushing
 Sediments, and any pollutants attached to sediments
can be washed off the surface into the drainage system

 Surface runoff entering the drainage system can wash

dissolved pollutants from gully pots into the network.

 These two processes are modelled completely

independently by InfoWorks ICM.
Surface Washoff and Gully Pot
Flushing
Surface Pollutant Editor
 Surface build-up and washoff
 The build-up of surface sediment and pollutants and
pollutants in gully pots prior to the current simulation is
calculated

 Parameters used in the runoff and washoff calculations

are initialised

 The simulation is started and runoff and washoff

calculations are made at every timestep.
 Dissolved and Attached
Pollutants
 Dissolved-Dissolved in water within the network.
Specified as a concentration.

 Attached-Linked to sediment fraction (can specify 2 SF).

Specified as a potency factor.

 3 Sediment Transport models:-

 Ackers-White
 Velikanov
 KUL Model
 Conservative Determinants
 Determinants are modelled as conservative unless:
 Decay parameters are specified or
 determinant is used as part of the dissolved oxygen
process.
 Modelled as a transported substance which does not:
 grow or decay over time, and
 interact with any other variable.
 Conservative
• Any pollutant can be set as conservative
• The following should always be set as conservative:-
• Salt

– included in calculation of saturation concentration of dissolved

oxygen (defined in water quality parameters).
• Temperature
– used to control biochemical reaction rates (defined in water
quality parameters).
• pH
– Hydrogen ion concentration is treated as a conservative
pollutant (default 7).
 Concentration vs Mass Flow
 Concentration is a measure of the strength of the
pollutant in kg/m3.

 Mass flow is a measure of the flux of pollutant in Kg/s.

 Workshop
 Workshop 1: Conservative Dissolved Pollutants
 Workshop 2: Conservative Attached Pollutants
 Non-Conservative Determinants
 Decaying Pollutants
 Decay types available:-
 None
 Linear
 Exponential Concentration
 Exponential time
 Exponential both
 Coliforms behave as an exponential time decay.
 User-defined Processes
 2 types:
 Growth/Decay
 s 2  p3  s3
Rate  s1  p1  p2 
s3  p4 
 Equilibrium

Rate  p2   p1  s1 
 Where S1,2,3 are determinant concentrations and P1,2,3,4 are
coefficients
 Workshop
 Workshop 3: Non-Conservative Decaying Pollutants
 Dissolved Oxygen (DO)
 DO concentration is often used as the main indicator of
the health of a river or estuary

 In the absence of a specified value, DO will be set to

DOS which is calculated using salinity and water
temperature:-
DOS  1.4310.291  0.2809T  0.006009T  0.0000632T   0.607 S (0.1161  0.003922T  0.0000631T )
2 3 2

 Re-aeration

 Ultimate Oxygen Demand (UOD)

 Denitrification
 Re-aeration
 Process by which O2 dissolves in water
 Rate is proportional to the oxygen deficit:-

 K air DOS  DO 
dDO
dt
 The re-aeration rate, Kair, can be calculated as a function
of temperature and hydraulic depth (default), or

 Re-aeration rate can also be calculated within Sim

Engine as a function of velocity and depth.
 Re-aeration
 Re-aeration rate calculated within Sim Engine as a
function of velocity and depth:-

 Owen’s Eq if d< 2.12:-

K air  5.32u 0.67 d 1.85

 O’Connor and Dobbin’s Eq if d>2.12 and u<1.68d0.3689-
1.433:-
K air  3.93u 0.5 d 1.5
 Churchill’s Eq for all else:
K air  5.026u 0.969
d 1.67
 Re-aeration at structures
 For WQ, a structure is considered to be any control link
except for pumps.

 Global aeration coefficient

 Can be overridden for individual structures.

Ultimate Oxygen Demand (UOD)
 Total amount of O2 required for micro-organisms to
decompose organic matter (leads to reduction in DO)

 Can use Biochemical Oxygen Demand (BOD) or

Chemical Oxygen Demand (COD)

 BOD is a measure of the DO required by aquatic

microbes to breakdown organic matter

 COD is a measure of the amount of DO required for

chemical oxidation of pollutants
 BOD
 BOD commonly expressed in terms of the 5-day BOD
 Related to UOD via:-

BOD5
UOD  5 k
(1  e )
• Where k=BOD5 decay rate (1/day)
 COD
 Where COD is selected, COD is taken as the equivalent
to UOD:-

UOD  COD
 Nitrification and denitrification
 Under usual conditions, oxidation of Ammoniacal
nitrogen to nitrite and nitrate.

 Calculated using temperature, salinity and suspended

solids.

 Under low oxygen (<5%) the nitrification of ammonia

(NH4 to NO2) ceases as does:-
 NO2 to NO3
 DO decay from NH4, NO2 and UOD

 NO3 and NO2 are then used as a source of O2 to satisfy

BOD by denitrification
 Results
 1D river model:
 Outputs
 Water Quality Results for chosen determinants
 Concentration (kg/m3)
 Mass Flow (kg/s)

 Graph tool
 Grid View
 Theme sections
 2D Results
 Animation
 Workshop
 Workshop 4: Dissolved Oxygen Processes
 2D
 Represents Advection and Diffusion* of determinants

 Available sources of pollutants in a 2D zone:-

 River Banks
 Manholes
 Point Sources
 External boundaries.

 2D Initial Conditions Zones for Water Quality

*Diffusion is not calculated in the 1D engine

 Results
 1D river model with 2D floodplains
 :
 Workshop
 Workshop 5: 2D Water Quality Modelling
 Water Quality Calculations
 Decay of pollutants

 Concentration of dissolved pollutants and suspended

sediment at all nodes

 Concentration of dissolved pollutants and suspended

sediment along each conduit.

 Erosion and deposition in each conduit.

 Summary
 Various Determinants
 Various Input formats
 Conservative vs non-Conservative
 User-Defined Processes
 Built-in Dissolved Oxygen Processes
 2D