Storing and sharing ICM Data
As an administrator, you will understand how ICM data is stored and shared.
In ICM, all modeling data, including networks, event objects, and ground models, is saved to a database. Result files are associated to the database files but stored separately.
Standalone database:
Saved as .icmm file and has associated unique identifier folder—must be kept together.
Folder contains all database information.
Designed for a single user and should not be saved on a network drive or file share.
Workgroup database:
Saved as an .sndb folder.
Manage via InfoWorks Workgroup Server service (installed separately), which can be run locally or in a centralized location.
Cloud database:
Introduced in 2024 release.
Use an integrated cloud database manager to back up and recover model data.
Admins can:
- Review databases
- Review backup creation dates
- Create, restore, and delete a database
For more information, refer to the Autodesk Help topic, Differences Between Working with Cloud and On-premise Databases.
Transportable database:
Created from the File menu within the user interface.
Copies data to a transportable file—compressed into .icmt file for external sharing.
Can select which database version should be created.
- Ensure person receiving data can open it.
- Cannot copy data from a newer version to an older database.
For up-to-date compatibility information, refer to ICM Help topic, Copying Data Between Databases.
Snapshot files:
Another way to transfer model network data.
An .isfm file contains network data only—not a complete database copy.
Allows network data to be moved to an older version, but new objects or fields will be lost in transfer.
Tutorial example files:
For transportable databases:
- Open .icmt files from the File menu.
- Copy contents.
For snapshots:
- Open a blank network in the GeoPlan.
- Import .isfm file.
Recommendations:
No size limit to database, but excessively large databases can result in hindered performance and cumbersome navigation.
Plan how to structure databases around projects to manage access and resources.
Recommended that users utilize workgroup database over the standalone.