Integrated BIM tools, including Revit, AutoCAD, and Civil 3D
Professional CAD/CAM tools built on Inventor and AutoCAD
Describe how versions, scenarios, and committed changes affect the network, allow for multiple simulation analyses, and promote a multi-user environment.
Type:
Tutorial
Length:
2 min.
Transcript
00:04
InfoWorks ICM includes a multi-user version control system that allows concurrent editing of a network,
00:11
making it easy for teams to work on one hydraulic model together.
00:15
However, even if you are a single user, the version control system helps you easily keep track of your network model changes.
00:24
As you add more and larger networks, it is increasingly important for your team to collaborate.
00:30
This is done by making local changes and then committing them to a workgroup database.
00:36
GeoExplorers, networks, and digitization templates are all version-controlled.
00:42
Also, there are many additional tools in ICM that help with network model management.
00:47
A good best practice is to enter a note at the prompts when you have made a change to a version-controlled object.
00:54
That way, a record is kept of the model history that helps you and your colleagues understand how the network model evolved.
01:02
The Commit History is a great tool for comparing differences between versions or copying a previous version into a new network.
01:09
There is also an Object Commit History for version-controlled objects.
01:14
The Object Commit details show you a table view of the object attributes that includes the changes from one version to the next,
01:21
with the most recent versions highlighted in dark red.
01:25
Using scenarios allows for flexibility as models are developed for possible solutions to current and future designs.
01:33
The Base model data is filtered to all scenarios, but the scenarios themselves are not linked, though they can be copied.
01:40
These features allow users to explore even more model possibilities.
Video transcript
00:04
InfoWorks ICM includes a multi-user version control system that allows concurrent editing of a network,
00:11
making it easy for teams to work on one hydraulic model together.
00:15
However, even if you are a single user, the version control system helps you easily keep track of your network model changes.
00:24
As you add more and larger networks, it is increasingly important for your team to collaborate.
00:30
This is done by making local changes and then committing them to a workgroup database.
00:36
GeoExplorers, networks, and digitization templates are all version-controlled.
00:42
Also, there are many additional tools in ICM that help with network model management.
00:47
A good best practice is to enter a note at the prompts when you have made a change to a version-controlled object.
00:54
That way, a record is kept of the model history that helps you and your colleagues understand how the network model evolved.
01:02
The Commit History is a great tool for comparing differences between versions or copying a previous version into a new network.
01:09
There is also an Object Commit History for version-controlled objects.
01:14
The Object Commit details show you a table view of the object attributes that includes the changes from one version to the next,
01:21
with the most recent versions highlighted in dark red.
01:25
Using scenarios allows for flexibility as models are developed for possible solutions to current and future designs.
01:33
The Base model data is filtered to all scenarios, but the scenarios themselves are not linked, though they can be copied.
01:40
These features allow users to explore even more model possibilities.
The version control system in InfoWorks ICM allows concurrent editing of a network and easy tracking of network model changes.
When adding more and larger networks, collaborate by making local changes and then commit them to a workgroup database.
GeoExplorers, networks, and digitization templates are version controlled.
BEST PRACTICE: Enter a note at the prompts when you have made a change to version-controlled objects. This creates a record of the model history that displays how the network model evolved.
The Commit History tool allows comparison between network versions. Object Commit History provides comparison between version-controlled objects.
The Object Commit details show a table view of the object attributes, including changes from one version to the next, with recent versions highlighted.
Scenarios allow for flexibility as models are developed for current and future design solutions:
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 for the best experience
Save your progress
Get access to courses
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.