Database Items

Contains model data for InfoWorks networks that is specific to ICMLive. The ability to view and edit the data in the live group will depend on your current licence options.

Contains asset network data and associated information. The ability to edit the data in the asset group will depend on your current licence options.

(When an Asset group contains two or more of the same kind of object (and no other types), the Asset group icon is modified slightly to reflect that single contained type.)

This is a legacy database item. No new Assimilation items can be added to the database and any existing items cannot be used in a new or existing run.

Contains initial values and profile data affecting rainfall runoff. A blank Catchment initial conditions object can be included when importing event data to a time series database so that it gets populated with the event initial conditions.

See Catchment Initial Conditions for more details.

Used in InfoWorks networks only.

These provide a powerful method of creating and saving customised graphs. The colour of the icon differs with type of graph:

- Observed / Predicted report

- Object per page report (InfoWorks networks)

- Simulation per page report (InfoWorks networks)

- Flexible report

- Extreme value analysis report

See Custom Graphs for further details.

This is a customised Microsoft Excel report template. You can use this to generate your own reports on the data in your InfoWorks ICM database.

See Custom report for further details.

Used in InfoWorks networks only.

The Damage Function is used to store a set of curves defining the relationship between flood depth and damage (as a monetary value).

The curves are used by Risk analysis runs.

Used in InfoWorks networks only.

This database item contains sets of built in parameters for Engineering validation. It can also be used to create user defined validation rules.

Used in InfoWorks networks only.

The Episode collection is used to store the start and end times of episodes, or events that occur in the system.

Used in InfoWorks networks only.

Contains a rainfall event and observed data. See Flow Surveys for further information.

Contains gridded network ground models from which InfoWorks ICM can generate elevation data during model building and flood mapping information during simulations.

Note: A Ground Model (Grid) is only included in the Explorer window after the data has been imported.

See Importing and Exporting Gridded Ground Models for more details.

Stores ground infiltration events. These are a special type of event that contain the time varying elements needed for the Ground infiltration model.

See Ground Infiltration for more details.

Used in InfoWorks networks only.

The Ground model TIN database item contains triangular irregular network ground models from which InfoWorks ICM can generate elevation data during model building and flood mapping information during simulations. These ground models can be imported from several external GIS sources.

See Ground Models TIN for more details.

Stores information about sets of rules to be used when inferring missing network values from existing data, allowing you to fill in gaps in your data with reasonable values. See Inference for more information.

Used in InfoWorks networks only.

An Infinity System Configuration database item contains the InfoWorks ICM run, statistics template and model group objects that will be used when CSO monitoring and reporting is carried out in Infinity System.

This is a legacy object. New Infinity System Configuration objects can no longer be created although existing objects can still be used.

Used in InfoWorks networks only.

Stores Inflow event data.

See Inflow and Level Events for more details.

Contains initial values for level and inflow at nodes, and depth and flow at river reaches.

See Initial Conditions 1D for more details.

Used in InfoWorks networks only.

Contains initial values for level, depth and velocity within 2D Zones and 2D IC Zones. The database item can then be included in a simulation when scheduling a Run.

See Initial Conditions 2D for more details.

Used in InfoWorks networks only.

Stores information about a set of custom labels displayed on the GeoPlan Window or Long Section Window. The colour of the icon differs according to the window:

- Label list for GeoPlan

- Label list for Long Section

See Saving Custom Labels.

You can load additional map layers on the GeoPlan Window to display all types of geographical information such as roads and buildings, surveyed maps, or even aerial photographs. Layer lists provide a way of saving a set of additional layers as an object in the master database so they can be easily reloaded.

Stores Level event data.

See Inflow and Level Events for more details.

Contains the settings that are to be used to calibrate the parameter values of a PDM Descriptor associated with one or more subcatchments in a network. It is also used to perform the calibration operation.

See PDM Calibration for more information.

Used in InfoWorks networks only.

Contains objects that define the depth of fixed sediment in pipes. Pipe sediment data can be used in water quality simulations to override the Sediment Depth value set for conduits in the network.

See Pipe Sediment Data for more information.

Used in InfoWorks networks only.

Contains Pollutograph events that define pollutant inputs to the network for use in water quality simulations.

These pollutant inputs do not follow a 24 hour pattern. They are used with an inflow or level event that provides flow data. See Pollutograph Events.

Used in InfoWorks networks only.

Stores rainfall event data.

See Rainfall Events for more details.

Regulator events are used to provide direct and indirect control of regulator structures e.g. weir crest levels, pump switching, pump speed etc, and can be used in InfoWorks networks instead of Real Time Control (RTC), or to override RTC when directly controlling a regulator.

See Regulator Events for more details.

Stores the geometry of a collection of points, lines and polygons that can be used to interrogate 2D mesh results.

See Results Analysis for more information.

Used in InfoWorks networks only.

Allows the selection of object types and attributes for which results are to be generated during a run.

See Results Selector for further information.

Used in InfoWorks networks only.

Contains the simulations run for a particular risk analysis exercise. Each risk analysis run contains the data to control the running of a risk analysis for one or more hydraulic runs.

Used in InfoWorks networks only.

Contains the simulations run for a particular modelling exercise in an InfoWorks network. Each run contains the data to control the running of the simulation engine for time varying input (rainfall event, flow survey or TSDB objects).

Within each run there may be one or more simulations. The status of the results of the simulation are indicated by the colour of the simulation icon:

• Results unavailable. There are no results available either locally or on the server. This may be because the simulation was carried out by a user on a different machine, or because the results have been deleted.
• Results are not available but but the local queue contains a job for this simulation that has not yet been completed. Note that it is not possible to tell if there is a job for this simulation queued on another machine.
• the simulation failed. The only results are in the log file and (optionally) the prn file, which will detail the reasons for failure.
• the simulation completed successfully and full results are available.
• the simulation completed, but with warnings, (for example a user threshold set in the Run Diagnostics was exceeded, or a depth exceeded the section height in a channel or river reach). Results are available.
• the simulation was ended due to failure to meet convergence criteria. Simulation results are available up to the point of failure. (Convergence problems relate to the 1D engine. The 2D engine does not experience convergence problems as it uses an explicit solver).

Simulation status displayed is the status of results on the user's computer, which may be different from the status on other computers.

If simulation results are available both locally and on the server, the local status takes priority. If local results are deleted, the status of results on the server (if any) become visible.

Used in InfoWorks networks only.

Contains lists of network objects that have been saved for future reference.

Stores in InfoWorks ICM spatial time varying data (TVD) coming from external data sources. See Spatial Time Series Database.

Contains statistical summary templates.

Contains SQL queries, which are used for selecting network objects according to specified criteria.

Stores climate-related values for evaporation and wind, as well as adjustment factors for temperature, evaporation rate, and rainfall.

See SWMM Climatology for more information.

Used in SWMM networks only.

Stores a pollutant inflow to the network for use in water quality simulations. They are used with an inflow or level event that provides flow data. See SWMM Pollutograph.

Used in SWMM networks only.

Contains the simulations run for a particular modelling exercise in a SWMM network. Each run contains the data to control the running of the simulation engine for time varying input (rainfall event, flow survey).

Within each run there may be one or more simulations. The status of the results of the simulation are indicated by the colour of the simulation icon:

• Results unavailable. There are no results available either locally or on the server. This may be because the simulation was carried out by a user on a different machine, or because the results have been deleted.
• Results are not available but but the local queue contains a job for this simulation that has not yet been completed.Note that it is not possible to tell if there is a job for this simulation queued on another machine.
• the simulation failed. The only results are in the log file which will detail the reasons for failure.
• the simulation completed successfully and full results are available.
• the simulation completed, but with warnings (for example a depth exceeded an open conduit height). Results are available.
• the simulation was ended due to failure to meet convergence criteria. Simulation results are available up to the point of failure.

Simulation status displayed is the status of results on the user's computer, which may be different from the status on other computers.

If simulation results are available both locally and on the server, the local status takes priority. If local results are deleted, the status of results on the server (if any) become visible.

Used in SWMM networks only.

The SWMM time pattern database item stores adjustment factors for Dry Weather Flow (DWF).

Used in SWMM networks only.

Stores in InfoWorks ICM scalar time varying data (TVD) coming from external data sources. See Time Series Database.

Stores themes set up on the GeoPlan Window for future use. See Saving Themes.

Stores Trade Waste event data.

See Trade and Waste Water Events for more details.

Used in InfoWorks networks only.

The UPM (Urban Pollution Management) River Data item contains data on the state of the river upstream of a spillage, the pollutants from combined sewer outfalls and sewage treatment works, and profiles of the river and parameters relating to the changes that will occur in the pollutants downstream.

Used in InfoWorks networks only.

The UPM Threshold item contains thresholds for mass balance frequency analysis and fundamental intermittent standards.

Used in InfoWorks networks only.

The Waste water database item stores Waste Water event data.

See Trade and Waste Water Events for more details.

Used in InfoWorks networks only.

Stores workspaces which save the settings and positions of open windows for future use. See Workspaces for further information.

The Recycle Bin stores database items that have been deleted from the database tree. An asterisk, displayed in brackets (*) to the right of the Recycle Bin, icon indicates that the bin contains deleted items. It is possible to empty the recycle bin and delete or restore individual items. See Recycle Bin for further details.