The database provides a flexible hierarchy for managing data.
The top level of this hierarchical structure is the Model group. All other database items within the database must be contained in a model group.
Database items can be version controlled or non-version controlled.
The names of version controlled items must be unique within a database.
All other names must be unique within that type. For example, two database items of different types within a models group can have the same name, but two database items of the same type must have different names.
Chapters on version controlled items are marked with a special icon while those for other objects are marked with the standard page icon .
Version controlled items
Version controlled items with local changes that have not yet been committed to the database are displayed with a red symbol in the bottom right hand corner, for example .
Icon |
Item Type |
Description |
---|---|---|
|
InfoWorks network |
The asset data for nodes, links and subcatchments. |
|
SWMM network |
The asset data for nodes, links and subcatchments. |
|
GeoExplorer |
The GeoExplorer provides a geographic view of the models within the database. Associated models groups, networks and workspaces can be opened via the GeoExplorer. |
|
Digitisation template |
The Digitisation template stores user defined digitisation defaults for use when creating new network objects. |
Non version controlled items
Icon |
Item Type |
Description |
||
---|---|---|---|---|
Group | Can be used as the top level of the organisation. The Group contains Model groups and Asset groups. | |||
|
Model group |
|
||
Live group |
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. |
|||
Asset group |
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.) Not available in cloud databases. |
|||
Assimilation |
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. |
|||
|
Catchment initial conditions |
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. |
||
|
Custom graph |
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. |
||
|
Custom report |
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. |
||
Damage Function |
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. Risk analysis runs can only be carried out if the Risk option is enabled on your licence. Used in InfoWorks networks only. Not available in cloud databases. |
|||
|
Engineering validation |
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. |
||
Episode collection |
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. |
|||
|
Flow survey |
Contains a rainfall event and observed data. See Flow Surveys for further information. |
||
|
Gridded ground model |
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. |
||
|
Ground infiltration |
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. |
||
|
Ground model TIN |
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. |
||
|
Inference |
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. |
||
|
Inflow |
Stores Inflow event data. See Inflow and Level Events for more details. |
||
Initial conditions 1D |
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. |
|||
|
Initial conditions 2D |
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. |
||
|
Label list |
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. |
||
|
Layer list |
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 a database so they can be easily reloaded. |
||
|
Level |
Stores Level event data. See Inflow and Level Events for more details. |
||
|
PDM Calibration |
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. Not available in cloud databases. |
||
|
Pipe sediment data |
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. |
||
|
Pollutograph |
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. |
||
|
Rainfall event |
Stores rainfall event data. See Rainfall Events for more details. |
||
|
Regulator |
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. |
||
|
Results analysis |
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. |
||
Results selector |
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. |
|||
Risk analysis run |
Risk analysis runs can only be carried out if the Risk option is enabled on your licence. 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. Not available in cloud databases. |
|||
|
Run |
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 or 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:
Note: For cloud simulations, results that are available locally may contain full results or summary results only depending on what type of results were selected to be downloaded from the cloud. See the
Download Cloud Results Dialog
or
Downloading Results topics for further information.
The simulation status displayed is the status of results on the user's computer, which may be different from the status on other computers. If results for on-premise simulations 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. If results for cloud simulation are not available locally, they can be downloaded from the cloud. Used in InfoWorks networks only. |
||
|
Selection list |
Contains lists of network objects that have been saved for future reference. |
||
|
Spatial time series database |
TSDB functionality is only available if the TSDB option is enabled on your licence. Stores in InfoWorks ICM spatial time varying data (TVD) coming from external data sources. See Spatial Time Series Database. Not available in cloud databases. |
||
|
Statistics template |
Contains statistical summary templates. |
||
|
Stored query |
Contains SQL queries, which are used for selecting network objects according to specified criteria. |
||
|
SWMM climatology |
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. |
||
|
SWMM pollutograph |
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. |
||
|
SWMM run |
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:
Note: For cloud simulations, results that are available locally may contain full results or summary results only depending on what type of results were selected to be downloaded from the cloud. See the
Download Cloud Results Dialog
or
Downloading Results topics for further information.
Simulation status displayed is the status of results on the user's computer, which may be different from the status on other computers. If results for on-premise simulations 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. If results for cloud simulations are not available locally, they can be downloaded from the cloud. Used in SWMM networks only. |
||
|
SWMM time pattern |
The SWMM time pattern database item stores adjustment factors for Dry Weather Flow (DWF). Used in SWMM networks only. |
||
|
Time series database |
TSDB functionality is only available if the TSDB option is enabled on your licence. Stores in InfoWorks ICM scalar time varying data (TVD) coming from external data sources. See Time Series Database. Not available in cloud databases. |
||
|
Theme |
Stores themes set up on the GeoPlan Window for future use. See Saving Themes. |
||
|
Trade waste |
Stores Trade Waste event data. See Trade and Waste Water Events for more details. Used in InfoWorks networks only. |
||
|
UPM River Data |
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. |
||
|
UPM Threshold |
The UPM Threshold item contains thresholds for mass balance frequency analysis and fundamental intermittent standards. Used in InfoWorks networks only. |
||
|
Waste water |
The Waste water database item stores Waste Water event data. See Trade and Waste Water Events for more details. Used in InfoWorks networks only. |
||
|
Workspace |
Stores workspaces which save the settings and positions of open windows for future use. See Workspaces for further information. |
||
|
Recycle Bin |
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. Note:
Cloud database items are stored in the Recycle Bin for 30 days. After this, they will automatically be permanently deleted.
See Recycle Bin for further details. |