Emerson Exchange 365

Delta-V Zone Compatibility

I am working on a project where we need a ZONE server for communicating between two DELTA-V systems. The old (Existing) System in a M-Series Delta-V with old Safety Logic Solvers while the new one will be the latest S Series System with traditional acrds for Process and SZ controller with Charms for Safety.

Is there any Version Compatibility we need to check? ( for an older M series System to communicate with the new S Series one).

Also, through Zone Controller, can we get the Historian and Asset Management Tags to the existing system ( without having Historian and Asset Management in the new system)?

Thanks for the help in advance.

• Zone Server
• Versions
• Delta V

ENGRIMRANTAHIR

• 11 Jan 2018 7:04 PM
• Cancel

3 Replies

• ENGRIMRANTAHIR

  

  • 16 Jan 2018 5:17 PM

  Hi, anyone - with any answers/help?

  • Cancel
• Alexandre Peixoto

  

  • 16 Jan 2018 6:15 PM

  My first advise is to check content available on our DeltaV Zones product datasheet at www2.emersonprocess.com/.../PDS_Zones.pdf, which includes the pre-requisites for DeltaV Zones being version 9.3 and higher applicable - this is not dependent on the DeltaV Controller type.
  
  The Plant Event Historian (PEH) is indicated to integrate historian data (including alarms and events) from multiple zones into a single database.
  
  AMS Device View might be a good option for what you are trying to achieve in the Asset Management realm.
  
  Hope this helps!
  
  Regards,
  
  Alex

  • Cancel
• Andre Dicaire

  

  • 16 Jan 2018 8:15 PM

  In reply to ENGRIMRANTAHIR:

  The Zone server only serves runtime data between the two systems. It does not provide access to Historians or for AMS data.
  
  The Plant Wide Event Historian only consolidates Event Chronicle Data. It will not consolidate continuous Historian data.
  
  You can install the AMS Device Manager software to collect data from multiple DeltaV Systems. You would need to license the AMS DM for the total number of smart devices to be integrated. Typically, you would install an L3 network to span both systems and that is where you would install the PEH and AMS servers. There are options to consider for the connectivity.
  
  Both systems have some global items that should be aligned so that data is presented consistently in both systems. For example, Named Sets, Alarm Types, Alarm Priorities and Alarm Colors should be reviewed and aligned. The type of controllers has no bearing and will not be an issue.

  Andre Dicaire

  • Cancel