To understand what to expect when upgrading to GENESIS64, I talked to Jotham Kildea, ICONICS Content and Competency Manager. Jotham has a Bachelor of Science degree in computer science from Worcester Polytechnic Institute and has worked for ICONICS for over thirteen years. For much of that time, he was involved in new customer project development and new opportunities with customers and users.
Naturally, Jotham mastered ICONICS software, particularly GENESIS64, which means he completely understands how it can be used, how to apply it to different requirements for different applications, and how to reach its highest potential. Even at the time he joined ICONICS, GENESIS32 was the older product in our company’s portfolio, so it wasn’t seeing a lot of new development or use. New projects or applications were being developed on GENESIS64. Given this, he has always thought of GENESIS32 as a legacy tool.
And that’s OK. GENESIS32 gets the job done but consider this analogy. If you are old enough to remember flip phones, then you can relate to the difference between these phones and smart phones. Both can be used for calling, messaging, and other basic capabilities, i.e., these get the job done. But the smart phone is in a whole other league. It's a sophisticated, multifunctional device that combines advanced telecommunications with computing power. The key distinction lies in its ability to connect to the internet, unlocking a vast array of fantastic capabilities and features that a flip phone simply cannot offer. The same holds true for GENESIS64. According to Jotham, GENESIS64 has a lot more “great and fun stuff”.
Another point to think about is that GENESIS32 is coming to its life cycle end. It has already reached the end of development (meaning no new features or patches will be added to the product) and will eventually see a sunset on customer support and new sales as well (see our GENESIS32 Lifecycle Update Letter for specific dates). Suffice it to say - it’s time. (You can read why in our blog Why Upgrading from GENESIS32 to GENESIS64 Is the Way to Go.)
Of course, for customers still using GENESIS32, it’s logical to wonder what this entails. So, what can you expect when you upgrade? I’ll let Jotham tell you.
Question #1: Before we get into what customers should expect when upgrading, what would you say is the most compelling reason(s) to upgrade?
I’d say the most compelling argument for upgrading is the capabilities GENESIS64 has to offer. Organizations want to be on track for future improvements and future developments, and these are happening in the 64-bit platform. New features/capabilities and new fixes will not be rolled out for GENESIS32, so if organizations want to continue growing and scaling with ICONICS, GENESIS64 is the place to do that. The continuing evolution of security and cybersecurity for software means that there is kind of a tit for tat between hackers and safeguarding a system. This situation necessitates that customers maintain updates and keep current with their software. And they can do this with GENESIS64.
Check out this short video where Jotham explains the importance of upgrading to GENESIS64:
Question #2: What can customers expect when upgrading?
Typically, the standard core components that users will be most familiar with - the graphical environment, the actual user interface that people see day in and day out, the alarming and the data logging and trending - have a direct upgrade path in the form of a conversion utility that allows them to import those configuration files.
ICONICS’ conversion assistant tool (ConverterWorX) will convert the 32-bit system over to an equivalent 64-bit graphic or 64-bit configuration. This tool will allow customers to deploy the configurations or graphics onto a new system so that core features upgrade smoothly.
More investigation may be needed for some of the other extensions and 3rd party components because there are a lot more connectivity aspects to address. Frequently the upgrade is a good time to discuss which appropriate data protocol(s) should be used for connectivity.
A lot of projects on 32-bit are using what we call OPC Classic, which is the Data Access-based protocol. Although it's out there, it's quite an old protocol at this point. Most applications have moved on to a newer protocol. When moving to 64-bit, it's probably a good time to reevaluate how that is going to be changed or how that is going to be redefined in the new setting.
Frequently, we see that it is not just about upgrading ICONICS software since our software is not often sitting in total isolation. Our software is integrated with other systems, for example, integrated with OPC servers or event notification systems. Whether it is work order management or whatever it might be, it is important to take the different points of third-party system integration into consideration. For this step, we often need to look at whether these third-party system integrations are still relevant to the organization and let that decision determine if these will be discontinued during an upgrade, ported over, or perhaps enhanced and expanded upon.
I always point out that when you move to 64-bit, yes, you'll be on the new platform. But you'll take advantage of new security and robustness of the system, and you will still effectively have the same configuration you had in the 32-bit. To be on the 64-bit platform, there are a lot of new capabilities that GENESIS64 has that have no equivalent in GENESIS32.
This the “fun stuff” I was alluding to earlier. There are a lot of new opportunities for adding innovative capabilities and for redesigning and optimizing your current system. But those would be new initiatives you'd take on after you do the conversion.
Question #3: What do you think is a common concern for customers considering upgrading?
I'd say the most common concerns are going to be: “What's it going to cost?” and “How disruptive it is going to be?”
For the cost, I recommend customers check with their local ICONICS or Mitsubishi Electric sales representative because we offer different conversion paths for long-term users. For the license transfer, customers will need to convert to a new license since the upgrade has modernized licensing mechanisms. Ordinarily, we can arrange for customers to have a transitionary period if they want to have the existing application running while they develop and deploy the new one.
And as far as interruptions to their operations are concerned, that really depends on how they choose to transact the upgrade. Ideally, if customers move to a new system, having a new virtual image or a new server makes it a lot easier because they can leave the existing 32-bit application in place. They can make a copy of the configurations and work with those in this new development environment to deploy the 64-bit equivalent version. They can then test in parallel and when they are ready, they can say, “OK, let's just switch over to using the new 64-bit system. We don't need the 32-bit system anymore.”
Alternatively, a conversion can also be done directly on a production system if that’s what the resources allow to be economical. GENESIS64 and GENESIS32 can both co-exist installed on the same server, and you can continue to operate the existing platform while doing your development and testing on the new one. This approach may require some minor downtime when “cutting over” to the new system. However, it is manageable and swift enough to avoid disrupting operations.
Commonly, if a customer does the conversion, they can still do some of the testing displays on the new system, so the cutover can happen pretty quickly. It’s easier to keep things clean when they are deploying a new system.
Question #4: What kind of help does ICONICS offer to customers wanting to upgrade?
Customers need to contact their ICONICS or Mitsubishi Electric point person who can explain what it's going to look like commercially for the transfer. ICONICS also has an application team that is familiar with the upgrade process, so we can offer this service. We also have a partner network of highly qualified integration partners who have completed many transfers and can recommend the path forward. And the conversion is also something that customers can undertake on their own if they wish. However, they might look to bring in an integration team if they want it done quickly and reliably.
Question #5: Can you think of anything else to add?
I'd love it if people moved over to GENESIS64. GENESIS32 is well due for replacement. For me, the best time to have upgraded would have been 10 years ago, but the second-best time to upgrade is now. It's time.
Concluding Thoughts
GENESIS32 has served us all well but alas, it is time to upgrade. You should now have a better idea of what to expect when upgrading to GENESIS64, and you can always contact us for further explanation.
Additionally, it’s extremely important to know that you are not alone. ICONICS and their partner network have a wealth of experience and expertise to smoothly and confidently guide you through this process. We’ve helped many customers so far, and we will help you too.
Before you contact us, have look at these three customer success stories to further your understanding of the benefits of upgrading: Blue Lagoon, Cucamonga Valley Water District, and Sussex IM.
Thinking about upgrading? Great, please tell us a little more about your application here, and we’ll help get you started.