Product Lifecycle Policy Frequently Asked Questions (FAQs) 

Product Lifecycle Policy Overview

1. Why is Mitsubishi Electric Iconics Digital Solutions updating its product lifecycle policy now?

As global customers take on more security-critical infrastructure projects and embrace faster, more agile workflows, our product lifecycle policy must evolve accordingly. The updated policy aligns with modern development practices and supports the accelerated pace of digital transformation.

2.I’m a customer running with a version that is in the Supported phase, should I be planning an upgrade?

To ensure your system remains secure and aligned with evolving best practices, consider the following recommendations if you're running a version in the Supported phase:
  • The importance of information and cybersecurity is paramount. Only by continuously monitoring the fast-evolving threat landscape and updating the current software as necessary to stay secure can we ensure that users are protected at every stage of the project lifecycle.
  • The company recommends the use of a staging system for mid-size, large, complex and/or mission-critical systems with frequent updates to the production system.
  • The length of time a product version remains supported and available in the market has a strong correlation with the potential security risks associated with that version. With that, the company encourages all customers to be on the latest version of the software and will use a timed cadence of 18-48 months to release major versions, which will force older releases through the lifecycle phases.
  • The company will make every effort to provide security updates for the Current version of its products and will selectively backport updates to Supported version(s) when possible. To ensure maximum system security, customers are strongly encouraged to run the Current version with the most recent update. See the “Security Response Timeline Goals” question for more details.

3.What is the major version release cadence for this policy?

Version release cadence refers to how frequently major product versions are released. As part of the product versioning updates outlined in the Product Lifecycle policy, most applications will follow an 18–48 month release cadence—meaning a new major version will be released approximately 18 to 48 months after the previous one. Please note that the number and timing of updates within each major version may vary.

Version Naming and Numbering

4.Does the Product Lifecycle Policy cover any third-party software sold through the company?

No, this policy applies exclusively to the company’s core products: the GENESIS32 product family, GENESIS64 product family, GENESIS, and Hyper Historian. All other previously released products not listed here are in the End of Life (EOL) phase. Third-party products are governed by their own lifecycle policies, which can be obtained directly from the respective vendors.

5.How will product version naming and numbering work under the new Product Lifecycle Policy, especially when you compare GENESIS64 version 10 and GENESIS version 11?

As part of our application versioning changes, the company introduced a more consistent version naming and numbering scheme starting with GENESIS version 11.
The following table outlines a convention for GENESIS version 11 releases. The product version consists of 2 parts and is defined in the following form: NN.MM

 

This document was last updated on June 6, 2025.