Skip to content

Understanding Modelon Impact's update strategy🔗

Modelon is dedicated to delivering a state-of-the-art system engineering modeling and simulation platform that is trusted by leading engineering companies worldwide. To support the engineering needs of today and the future, the platform is constantly evolving. The update and deprecation strategy are set to balance the needs of evolving the platform with backwards compatibility.

This article offers a high-level overview of how improvements and new functionality are being added and deprecated functionality is being discontinued at Modelon Cloud.

Updates🔗

Modelon Impact is a platform that consists of several modules that are updated according to:

Always on latest🔗

  • Model Builder and Visualization Tools: The graphical user-interface is continuously updated with improvements and new functionality. Once a new GUI update has been deployed, a user will directly see and benefit from it.

  • Integrations: The public facing REST-API is continuously updated with improvements and new functionality. Once a new REST-API update has been deployed, a user will directly benefit from it.

  • Learn: The help center is continuously updated to reflect the latest version of Modelon Impact.

Multiple versions available🔗

To give users more control and ensure that results behave deterministically over updates, users can select which library and execution environment version to use.

  • Modelon Libraries: New versions of libraries are released and made available on Modelon Impact with at least a twice-a-year cadence. To use a new library version, a user needs to upgrade its workspace dependencies in the Workspace Configurator.

Note

Older library versions can be continued to be used according to their life cycle description below.

  • Solver: New versions of execution environments are released and made available on Modelon Impact with at least a twice-a-year cadence. By default, users will use the last released (stable) version. This is labeled as "stable" and this environment will automatically use the last released (stable) version. Users will directly benefit from the improvements. To use a fixed version, user needs to select a versioned execution environment in the server profile page. Furthermore, there is the "latests" execution environment, this version includes the latests changes that will later be available in the stable version. Note that this includes upcoming breaking changes. It is not recommended to use this execution environment by default, rather as an opportunity to verify upcoming changes and their implications on user models. Fixed versions are accessible according to their life cycle description below.

Note

Available execution environments will continuously be updated and enhanced through their lifecycle including security and compatibility fixes. Those patch updates are intended to be fully backward compatible.

Life cycle🔗

To balance the needs of evolving the platform with backwards compatibility, deprecated functionality and older versions of libraries and execution environment are removed from the platform according to:

Modelon Libraries🔗

The three most recent major releases of a library version are available. When a new major version is introduced, the oldest version is removed.

Note

Libraries that are not accessible by default can be manually imported using the Workspace configuration app.

Modelon Library life-cycle at Modelon Cloud

Disclaimer, the timeline below is an estimate and is subject to change without prior notice.

Library release General availability at Modelon Cloud Removal from Modelon Cloud
2023.2 June 2023 Q1 2025
2024.1 Feb 2024 Q3 2025
2024.2 Sep 2024 Q1 2025

Solver🔗

The two most recent major versions of an execution environment are available. When an additional major version is introduced, the oldest version is removed.

Execution environment life cycle at Modelon Cloud

Disclaimer, the timeline below is an estimate and is subject to change without prior notice. Modelon reserves the right to cancel a versioned execution environment earlier in the rare case of a critical vulnerability that can’t be resolved without breaking the integrity of the execution environment.

Versioned execution environment General availability at Modelon Cloud Removal from Modelon Cloud
2024.1 Feb 2024 Q1 2025
2024.2 Sep 2024 Q3 2025

Integrations🔗

The public facing REST-API applies a deprecation strategy in case of breaking changes. Deprecation notices will be announced at least 3 months before the functionality is removed or substantially changed. Notes:

  • Modelon does not consider the extension of API payloads to be breaking.

  • Future versions of the product will also announce deprecation warnings through standard mechanisms in the HTTP protocol. We advise customers to monitor for the headers Deprecation and Sunset as described by RFC 8594. Example:

    Deprecation: Sun, 11 Nov 2018 23:59:59 GMT 
    Sunset: Wed, 11 Nov 2020 23:59:59 GMT 
    Link: <https://api.example.com/v2/customers>; rel="successor-version", <https://developer.example.com/deprecation>; rel="deprecation"

The recommended best practice is to use Modelon Impact default behavior for the Execution environment and migrate to the latest versions of Modelon libraries. The recommendation is based on that the latest version include the most recent fixes, improvements, and functionality. For instructions on migration see: