Data Management

InfoWorks ICM is a workgroup based, modelling and configuration management system that can also be used as a standalone product.

To facilitate both workgroup and standalone operation, InfoWorks ICM maintains data in a centralised, multi-user master database, consisting of a database and additional files.

Local working copies of parts of the master data, (such as networks with changes that have not yet been committed), are stored in each users Local Working Folder.

Information that relates to the master database, but is not stored in the database, such as ground model data, is stored in Remote Roots. The files containing this data can be very large so it is better to store them outside of the database.

Transportable databases are used to transfer information between master databases.

See the File Locations topic for further details.

Managing master database data

The master database provide a flexible hierarchy for managing data.

The top level of this hierarchical structure is the Model Group. All data within the master database must be contained in a Model Group.

The Model Group can contain the following:

See Database Items for a full list of item types available in InfoWorks ICM.

The Model Group is used to store all the data needed for carrying out a series of modelling tasks.

Data items of a particular type can be grouped together by storing them in Model groups nested within the top level Model Group.

Groups and items can be accessed and manipulated using a tree view. The Explorer window displays all the information about groups and items in the master database. It can be docked at the side of the main InfoWorks ICM window so it is always visible.

See Working with Database Items and the other topics in the section for more details about working with groups and items.

Version control

The version control system maintains a complete and permanent record of all changes to your data. Version control supports multiple users editing the same network at the same time, and includes tools to resolve any conflicting changes that may occur.

Should errors be found in the data, you can track when the erroneous changes were made, and who made them. Branching is supported should you need to go back to an earlier version of a network and continue working from there.

See the Managing Version Controlled Items topic for more information.

Master Database

Database Items

Managing Version Controlled Items