Emerson Exchange 365

• Not Answered

Deltav 9 upgrade to higher version

hi people . we are running deltav 9 in a plant .  i know that deltav wont upgrade more than 2 major versions . so here is the question . can we upgrade from 9 to 11 and then 11 to 13 and finally 13 to 14.3 ? what about license and hardware compatibility ?

easyacer

• 4 Apr 2019 9:00 AM
• Cancel

7 Replies

• MC_Chow

  

  • 4 Apr 2019 1:20 PM

  I strongly recommend you discuss this with and involve your local Emerson service organization. This is a major upgrade and needs to be properly planned and executed.

  • Cancel
• easyacer

  

  • 4 Apr 2019 1:53 PM

  In reply to MC_Chow:

  I have no access to any official emerson service and i just want unofficial comments from experienced users but i have the chance to make as many mistakes it takes to accomplish the process . Thanks for sharing

  • Cancel
• Rein

  

  • 4 Apr 2019 5:54 PM

  Yes, to your first question.
  License and hardware upgrade also.
  What type of workstations, controllers, and I/O cards are you using?
  The upgrade process will be very complicated and you will definitely encounter a lot of problems.
  Better engage the service of the experts. Else, you may start building a new project based on v14.

  • Cancel
• easyacer

  

  • 4 Apr 2019 6:13 PM

  In reply to Rein:

  Thanks for sharing . Starting a whole new project based on v14 is an option and all options are on the table . The main reason i want to upgrade the system is getting rid of windows xp installed on powerful new workstations which hangs and restarts frequently with no reason . V11 or v13 is also good for my purpose but why not more ? ;-)

  • Cancel
• Andre Dicaire

  

  • 5 Apr 2019 6:09 PM

  In reply to easyacer:

  There are two sides to an upgrade, one is the system configuration and the other is the ability to migrate online.
  
  Configuration migration requires the FHX files to be processed with the Migration Tool, which verifies the FHX for known items that need to be modified in order to import successfully to the new version. Support for migration of versions is identified in the release notes and such, but generally, you need to process the configuration through supported paths to ensure the configuration is brought current with all items addressed. To do that, you need to have the interim versions of the migration tool.
  
  If you are doing an offline migration, where you will be able to do a total download to all the nodes, that would be best in your case, due to the number of versions involved. If you are attempting an online upgrade, you've created a lot of unknowns that should be identified and explored through offline testing. As TC points out, you should engage the Emerson SureServices group and get someone with experience to guide this effort. If this is an Offline migration, you will still want to do the equivalent of an FAT on the migrated system to ensure your configuration is behaving as expected. You'll want to review all the release notes and known issues and evaluate your risks.
  
  If you migrate and FAT the configuration, these items should be found out and not be an issue.
  
  On the hardware side of things, you will likely have to replace hardware that is no longer supported in the software. In v14, MD controllers and all earlier versions are not supported and must be replaced. MDPlus will still work in v14. You should also verify the IO cards. Of course you computers will not be current as well. you may also have to consider your Network Switch Hardware. You will not be able to achieve Cybersecurity levels with older switches. You will need to verify if there are any configuration changes to be made to 3rd party switches and what OS is supported in them.
  
  Since you need Guardian Support to obtain the v14 license, you should make use of this to register your system content. The lifecycle report from Guardian will help you identify which components our no longer current and what their support profile looks like. Then you can evaluate what hardware you need to purchase.
  
  As for licensing, yes licensing has changed. As you migrate your FHX files, the license content will be converted/modified to leave you with equivalent capabilities. In some cases you will gain capacity. For instance, the DST licensed Operator stations will become Full Span of control as the DST sizing component of Operator stations was discontinued. The DST licensing changes in v12 may leave you with more "free" DST licenses, which you will be able to use in the future. ( This depends on your configuration/IO device content.)
  
  Each system ends up being highly customized to meet the varying needs of customers. Customers perform system upgrades sporadically, maybe every two years, likely closer to 4 or 5 years. You will want to benefit from the experience of Emerson engineers that are involved in dozens of upgrades per year, and have migrated many customers through many revisions. You should at least engage them to develop your migration plan, help decide the staffing for the migration, and have them aware of your activity. the fact you are migrating from v9 tells me you've not done many DeltaV upgrades. Strongly recommend you get some help.

  Andre Dicaire

  • Cancel
• easyacer

  

  • 5 Apr 2019 8:50 PM

  In reply to Andre Dicaire:

  Thanks for sharing . We can perform total offline upgrade with FAT but Writing a whole new project based on newer versions seems too much easier than the upgrade process specially when we have no access to official representative .

  • Cancel
• Andre Dicaire

  

  • 5 Apr 2019 10:02 PM

  In reply to easyacer:

  What do you mean no access to a representative? How did you obtain new versions of software and licenses to run newer versions of DeltaV? Do you have Guardian support? Emerson has service capabilities around the world.

  Andre Dicaire

  • Cancel