& Construction

Integrated BIM tools, including Revit, AutoCAD, and Civil 3D
& Manufacturing

Professional CAD/CAM tools built on Inventor and AutoCAD
Integrated BIM tools, including Revit, AutoCAD, and Civil 3D
Professional CAD/CAM tools built on Inventor and AutoCAD
Transcript
00:03
In ICM, all modeling data is saved into a database.
00:08
This includes all networks, event objects, and ground models.
00:13
The database is either a standalone, workgroup, or cloud database.
00:19
Result files are associated to the database files, but they are stored separately.
00:25
A standalone database is saved as an .icmm file and has an associated unique identifier folder.
00:32
The folder will contain all of the database information.
00:36
The .icmm file and associated folder must be kept together.
00:41
The standalone database is designed for a single user and should not be saved on a network drive or file share.
00:48
A workgroup database is saved as an .sndb folder.
00:53
The folder will contain all of the database information.
00:56
The workgroup databases are managed via the InfoWorks Workgroup Server service, which is installed separately.
01:03
This can be run locally to manage an individual's databases or from a centralized location to enable multi-user access.
01:12
The 2024 release of ICM introduced cloud databases, which allow users to store and manage project data in the cloud.
01:20
Users can access databases within their assigned regional Hubs.
01:25
Using an integrated cloud database manager,
01:28
administrators can back up and recover model data from an accessible web-based environment.
01:33
In this view, admins can review databases that their team are working on, as well as the date a backup was created for each version.
01:41
They can manually create new backups, restore from an existing backup, or delete a database that is no longer needed.
01:49
The behavior of on-premise and Cloud databases does differ.
01:54
For more information, refer to the InfoWorks ICM Help topic, ‘Differences Between Working with Cloud and On-premise Databases'.
02:02
Regardless of which type of database is in use, you can transfer data using a transportable database file.
02:09
A new transportable database is created from the file menu within the user interface.
02:15
Data is then copied into the transportable file.
02:19
Upon closing, it is compressed into a single .icmt file and can be shared externally.
02:25
When creating a transportable database, you can select which database version should be created.
02:31
This is important to ensure that the person receiving the data is able to open it.
02:36
Note that you cannot copy data from a newer version into an older version transportable database.
02:43
The copy option will not be available.
02:46
For an up-to-date view of compatibility between different databases, refer to the ICM Help topic, Copying Data Between Databases.
02:54
A snapshot file is also available to transfer model network data.
02:59
The .isfm snapshot file contains network object data only and is not a complete copy of the database.
03:07
This can allow you to move network data into an older version, but any new objects or fields will be lost during the transfer.
03:15
Many of the dataset files used in these tutorials are stored in transportable databases.
03:21
Open .icmt files from the File menu and copy the contents into your database.
03:27
For snapshots, begin the lesson by importing the .isfm file into a blank network that is open in the GeoPlan.
03:36
As an individual or group of users, you can have as many or few databases as you desire.
03:42
There is no size limit to a database, although excessively large databases may suffer in performance and be cumbersome to navigate.
03:50
Best practice is to plan how to structure your databases around your projects to manage access and resources.
03:57
It is recommended that all users utilize the workgroup database over the standalone.
Video transcript
00:03
In ICM, all modeling data is saved into a database.
00:08
This includes all networks, event objects, and ground models.
00:13
The database is either a standalone, workgroup, or cloud database.
00:19
Result files are associated to the database files, but they are stored separately.
00:25
A standalone database is saved as an .icmm file and has an associated unique identifier folder.
00:32
The folder will contain all of the database information.
00:36
The .icmm file and associated folder must be kept together.
00:41
The standalone database is designed for a single user and should not be saved on a network drive or file share.
00:48
A workgroup database is saved as an .sndb folder.
00:53
The folder will contain all of the database information.
00:56
The workgroup databases are managed via the InfoWorks Workgroup Server service, which is installed separately.
01:03
This can be run locally to manage an individual's databases or from a centralized location to enable multi-user access.
01:12
The 2024 release of ICM introduced cloud databases, which allow users to store and manage project data in the cloud.
01:20
Users can access databases within their assigned regional Hubs.
01:25
Using an integrated cloud database manager,
01:28
administrators can back up and recover model data from an accessible web-based environment.
01:33
In this view, admins can review databases that their team are working on, as well as the date a backup was created for each version.
01:41
They can manually create new backups, restore from an existing backup, or delete a database that is no longer needed.
01:49
The behavior of on-premise and Cloud databases does differ.
01:54
For more information, refer to the InfoWorks ICM Help topic, ‘Differences Between Working with Cloud and On-premise Databases'.
02:02
Regardless of which type of database is in use, you can transfer data using a transportable database file.
02:09
A new transportable database is created from the file menu within the user interface.
02:15
Data is then copied into the transportable file.
02:19
Upon closing, it is compressed into a single .icmt file and can be shared externally.
02:25
When creating a transportable database, you can select which database version should be created.
02:31
This is important to ensure that the person receiving the data is able to open it.
02:36
Note that you cannot copy data from a newer version into an older version transportable database.
02:43
The copy option will not be available.
02:46
For an up-to-date view of compatibility between different databases, refer to the ICM Help topic, Copying Data Between Databases.
02:54
A snapshot file is also available to transfer model network data.
02:59
The .isfm snapshot file contains network object data only and is not a complete copy of the database.
03:07
This can allow you to move network data into an older version, but any new objects or fields will be lost during the transfer.
03:15
Many of the dataset files used in these tutorials are stored in transportable databases.
03:21
Open .icmt files from the File menu and copy the contents into your database.
03:27
For snapshots, begin the lesson by importing the .isfm file into a blank network that is open in the GeoPlan.
03:36
As an individual or group of users, you can have as many or few databases as you desire.
03:42
There is no size limit to a database, although excessively large databases may suffer in performance and be cumbersome to navigate.
03:50
Best practice is to plan how to structure your databases around your projects to manage access and resources.
03:57
It is recommended that all users utilize the workgroup database over the standalone.
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.
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.
Saved as an .sndb folder.
Manage via InfoWorks Workgroup Server service (installed separately), which can be run locally or in a centralized location.
Introduced in 2024 release.
Use an integrated cloud database manager to back up and recover model data.
Admins can:
For more information, refer to the Autodesk Help topic, Differences Between Working with Cloud and On-premise Databases.
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.
For up-to-date compatibility information, refer to ICM Help topic, Copying Data Between Databases.
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.
For transportable databases:
For snapshots:
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.
How to buy
Privacy | Do not sell or share my personal information | Cookie preferences | Report noncompliance | Terms of use | Legal | © 2025 Autodesk Inc. All rights reserved
Sign in to start learning
Sign in for unlimited free access to all learning content.Save your progress
Take assessments
Receive personalized recommendations
May we collect and use your data?
Learn more about the Third Party Services we use and our Privacy Statement.May we collect and use your data to tailor your experience?
Explore the benefits of a customized experience by managing your privacy settings for this site or visit our Privacy Statement to learn more about your options.