ICM versioning and database compatibility

00:03

When managing ICM, it is important to understand version numbering, especially if data is shared internally or externally.

00:11

Each release has a product version number denoting the major version year, followed by the minor version,

00:18

and, in some cases, a final patch number.

00:21

You will see the two-digit number displayed on the windows icons.

00:26

The three-digit number is displayed on download and installation information.

00:31

There is a separate build number.

00:33

The first number is the major version, the next number is the minor version, and the last is a patch number.

00:42

This version number is available in the About dialog box.

00:46

Note that, because they are managed separately,

00:48

the InfoWorks ICM Client and Workgroup Server components may have separate build numbers for the same release version.

00:56

Different major versions of InfoWorks ICM can be installed side-by-side on the same computer.

01:02

This means, for example, that ICM 2023 and ICM 2024 can be installed on the same machine,

01:10

allowing users to work on existing projects with an older version.

01:14

Ensuring that the correct version of ICM is used is critical, as it controls who can access the data, the functionality available to the user,

01:23

and the replicability of results.

01:25

From version 2023, ICM databases have been made backwards compatible.

01:31

So, you can use a version of ICM that is newer than the database.

01:36

This means that you can create a 2024.0 version database with ICM 2025.2.

01:44

This allows the user to be in the latest version, but the data can still be shared with other parties using version 2023.0 or newer.

01:53

However, be aware that while connected to an older version database, new functionality will not be available.

01:60

It is not possible to connect ICM to a database that is newer than the version of ICM.

02:06

It is also not possible to copy from a newer database version into an older version.

02:12

If you are using the current version of ICM and database, then it will use the latest version of the simulation engine.

02:19

If you are using an older database version, then ICM uses the current Agent to replicate the previous Agent.

02:26

Note that bug fixes will be included in the newer Agent, so differences may exist.

02:31

To ensure consistency between simulation results, users should rerun simulations in the same version, or check after upgrading.

02:40

Cloud capabilities, including databases and simulations, are only available from version 2024 onwards.

02:48

Note that when using the Cloud, typically only the latest and preceding simulation engine version will be available for use.

02:55

Users will be notified as engines are decommissioned.

02:60

For those managing distributed simulation environments, the remote agent and the client version must match exactly.

03:07

This means that the major, minor, and patch numbers must match in order for an agent to be available for remote simulation.

03:15

If a matching Agent is not found, a “no engine available” message will be displayed against the machine.

03:22

Administrators should manage deployments so that agents and clients update at the same time.

03:27

This is to ensure consistency of results.

03:31

For the latest versioning information,

03:33

see the support document Autodesk Policy on Versioning for InfoWorks ICM and InfoWorks WS Pro.