Emerson Exchange 365

Hi Colin. You're almost there! I've added a couple of notes to your sequence from the best practices I've developed for the systems I manage in New England.

• Make sure the preferred active Batch Exec is running the process.
  • If the Preferred Standby (_S) Batch Exec is in the Current Active spot during reboot, "bad things" can happen.
  • These "bad things" are dependent on your DeltaV version and patch level, so I take the conservative route and do it one way for all the systems I manage.
• Make sure the Batch Exec REDU subsystem has good integrity.
• Hold all running batches
  • Not explicitly necessary. The switchover should (!) be seamless.
• Force a manual switchover in Diagnostics   (Batch Executive Application Station  → Redundancy → [Right Click] Redundancy Switch-Over)
• Confirm switch-over has occurred by checking the WinName parameter
• Restart all previously held batches
• Confirm operations have returned to normal
  • Batch Exec REDU subsystem returns to good integrity.
  • Batch Historian (if used) has switched its interface to the new Batch Exec.
  • External clients (PI EMDVB, MES/SOA clients, etc..., if used) are receiving data from the current Batch Exec.

Best regards.

Ray