Emerson Exchange 365

• Not Answered

DeltaV version upgrade: OPC settings change?

Dear all,

we are currently planning to upgrade our DeltaV from 9.3v to 13.3v. However, hook-up to this system, we have a few systems exchanging data via OPC. Therefore, would it be required any changes (major changes) to the OPC connection? Would the upgrade cause any loss of data on the OPC connection? Additionally, another OPC connection would have to be set/established? 

Existing System Details - 9.3v

OPC communication PC: Windows XP, Service Pack 2, WORKGROUP Environment

DeltaV Workstation(AWS): Windows Server 2003, Service Pack 1, WORKGROUP Environment

 

Proposed Upgradation Details - 13.3v

DeltaV Workstation(AWS): Windows Server 2008/2013, DOMAIN Environment

Please kindly advise.

Best Regards

Fermar

• deltaV upgrade
• OPC

fermar

• 15 Jul 2016 2:00 PM
• Cancel

2 Replies

• Andre Dicaire

  

  • 15 Jul 2016 9:58 PM

  During the upgrade of the OPC Server host computer, there will be some disruption as the computer OS will be updated, or the computer replaced. If you are replacing the computer, you can prepare the new computer as much as possible, but since it is a Domain computer, it must join the domain as part of the installation/configuration of the DeltaV software. That requires the new computer to be connected to the DC, and DeltaV networks.
  
  So there will be a disruption for a short while.
  
  Although your new computer will be in a domain, you will still want to create a local user account on the new computer to act as the DeltaV account for the OPC client log on. Create this account using the local User Manager on the server and it can be the same name and password you have need using in the Workgroup computer. This will match up with the other OPC server you are communicating with. You may want to consider creating a new computer with a new name so that you can connect and completely configure the system prior to decommissioning the existing server. This will allow you install the server, join the Domain, complete DeltaV configuration, set up the OPC clients and Windows accounts, establish network connections. Then, you can shutdown the current server, delete the node in DeltaV, assign the licenses to the new node and download.
  
  Integration of OPC Data requires a client application to read and write data to the server. OPC Mirror is a multi server client that allows the movement of data between servers. Are you using OPC MIrror or another client application? And is this installed on the current OPC Server computer? Is the other OPC Server installed on the DeltaV node? Are these applications compatible with Server 2008R2? (DeltaV 13.3.1 will support both Server 2008R2 and Server2016, but is not available until early 2017)
  
  It is always a good idea to stage the upgrade so that procedures for server replacement/upgrade are performed at least once prior to the actual plant upgrade. This will uncover any unexpected challenges and ensure a smooth execution. For an Online Upgrade, you should involve Emerson Services to have someone with experience involved on the team. Since your plant is running v9.3, it appears to have been a long time since any upgrade was performed, let alone an on-line upgrade.

  Andre Dicaire

  • Cancel
• fermar

  

  • 18 Jul 2016 6:44 AM

  In reply to Andre Dicaire:

  Thank you a lot Andre. I'll verify internally your questions, and get back to you.
  
  Once again, I appreciate your support.
  
  Best regards
  
  Fermar

  • Cancel