12 Advanced On Process Migration Implemetation r500

Automation College
Experion PKS: Advanced -

On-Process Migration Implementation
EXP-90 R500 AT/VT Student Guide

Rev 01.1 06/2017
Book 1 of 1
.
Notices
While this information is presented in good faith and believed to be accurate, Honeywell assumes
no responsibility for any errors that may appear in this courseware. The courseware is presented
on an “as-is” basis. Honeywell disclaims the implied warranties of merchantability and fitness for a
particular purpose, and makes no express warranties except as may be stated in its written
agreement with and for its customer.
In no event is Honeywell liable to anyone for any indirect, special or consequential damages even
if Honeywell is informed of the possibility of these damages. The information and specifications in
this courseware are subject to change without notice.
No part of this courseware may be reproduced or transmitted in any form or by any means. It is
intended for the use of the original purchaser only. Copying, duplicating, selling or otherwise
distributing the courseware is a violation of law. The materials and workbooks comprising the
courseware may not, in whole or part, be copied, photocopied, reproduced, translated or reduced
to any electronic medium or machine-readable form without prior consent in writing from
Honeywell.
This courseware is the confidential and proprietary information of Honeywell. The courseware may
only be used by the person who attended the Honeywell class. The courseware may only be used
in conjunction with a Honeywell system at the company that paid for the class. Only Honeywell
may use the courseware for training purposes.
This class has special equipment configurations that are appropriate only for training and should
not be used for any other purpose.
Experion, Da Vinci, IntelliMap, MXOpen, MXProLine, TotalPlant, PlantScape, TDC 3000,

Uniformance, Universal Control Network, ControlEdge RTU, and ControlEdge PLC are registered
trademarks of Honeywell International.
These commodities, technology or software were exported from the United States in accordance
with the Export Administration Regulations. Division contrary to U.S. law prohibited.
Copyright © 2017 Honeywell Inc.
Honeywell International, Inc.

Automation College
Global Learning Services
Program Objectives
EXP-90 R500 (AT/VT)

Tab Lesson Objectives
1 Migration Introduction
Class Introduction
Architecture and Sequence of Class System
Describe the On Process Migration Procedures
Describe the Off Process Migration Procedures
Describe the Server/Client Migration Paths
Describe Controller Migration Paths
2 Plan the Migration
Plan the Migration
Setting up the ESIS
Migration Considerations
3 Check the System for Migration Readiness
Perform Pre-Migration Checks
(E) Instructions for performing labs in virtual
environment
(E) Install Component User Guide
(E)Prepare for Running Upgrade Tool
(E) Run Upgrade Tool
Review and Correct Any Issues Listed in the
System Event Logs
(E) Prepare Premigration Checklist
(E) Perform Premigration Checks
4 Migrate Server B
Describe the On Process Migration Procedure for
Server B
Server/Station Migration with Operating System
Installation
Adding Shortcuts Manually
Download and Add Patches from OLS Website
(E) Migrate Server B using ESIS
(E) Join the Domain
(E) Set Up NTP Time Server
(E)Verify LCNP Configuration
Updating Display Files
(E) Migrating Database
(E) Migrate Quick Builder Database
(E) Update Custom Station Files
(E) Rebuilding Checkpont Files
(E) Saving Checkpoint Manually
Check to See if Server B is Working
(E) Verify Server B Operation
5 Migrate First Experion Client node (ES-F /ES-C)
Migrate First ES-C
(E) Migrate Console Station using ESIS
(E) Join Domain
Honeywell Confidential and Proprietary Page: 1 of 2 2017/05/01

Program Objectives
(E) Verify Console Station Operation
(E)Disabling TPS System Alarms
6 Migrate Server A and Synchronize
Migrate Server A
(E) Migrate Server A Using ESIS
(E) Join the Domain
(E) Set up NTP Time Server
(E) Post Migration Tasks
7 Migrate Controllers
Migrate Controllers
Searching for Unsupported Modules
Initiate Controller Migration of Selected Chassis
Describe Freeze and Switchover
Describe Spare Parts Migration
8 Migrate Server B and Abort Migration and Go to Old Release
Canceling (Aborting) Migration
9 Migrate Domain Controller
Migration of Domain Controller Does Not Affect
Migration
(E) Verify Completeness of Experion Installation
(E) Migrate Domain Controller
(E) Run Link Domain Groups
(E) Restoring the Autocheckpoint Task Scheduling
(E) Installing Diagnostic Studio on Server and
Client Nodes
(E) Installing PDF Collection
10 EMDB Merging and Splitting
Splitting and Merging EMDB Procedures
11 Wrap Up
Wrap Up
12 Migration Checklists
(E) Prepare Migrate Server B Checklist
(E) Prepare Migrate Server A Checklist
(E) Prepare Migrate Console Station Checklist
(E) Prepare Post-Migration Checklist
(E) Prepare Controller Migratation Checklist
(E) Prepare Virtualization Checklist
13 ACE Rapid Restart (Reference Only)
Describe ACE Rapid Restart
Honeywell Confidential and Proprietary Page: 2 of 2 2017/05/01

Class Introduction
Honeywell Confidential
Migration Introduction Copyright © 2017 Honeywell International Inc. Class Introduction
1 5/8/2017
Class Introduction
EXP90R500 On-Process Migration Workshop
• We will be migrating a R431.1 system to R500.1
• Seventy-five percent will be a hands-on lab
NOTE
Forget everything you know about previous migrations. Migration to
R500 Experion is totally different. Significant changes have been
made to the installation process as well as many other features
2 5/8/2017
1
A Migration is a Migration
NOT SO!
• Experion R500.x introduces the following new features and functions not
present in previous releases
– Upgrade Tool Enhancement
• Detect C300 controller replacement CC-PCNT02 and new Ethernet Interface
Module (EIM) CC-PEIM01
– Experion Batch Manager enhancement for Migration
– EHPM and IEC 61850M can be migrated using Controller Migration Wizard
– Automatic Execution of ECC Repair Scripts from Upgrade Tool
– Support for migration from N-3 release
• Additionally, many more enhancements to the functions and features to
the Experion System will be presented in this training
3 5/8/2017
Things to Know
• Register migrations through the Migration COE Help Desk for both:
– On-Process Migration (OPM); regardless of the path
– Off-Process Migration
– Email: LSS.Migration.COE@honeywell.com
• The pre-analysis of your system by the Migration COE Help Desk may require
Global Technical Assistance Center (GTAC) support for areas of concern relating
to found issues
– Honeywell Process Solution website contains supportive information for both internal
and external customers logged in: http://www.honeywellprocess.com
– Note: A non-registered (non-analyzed) migration will receive “Commercially
Reasonable Effort” support from GTAC if problems occur during the migration process
• Software upgrade order forms (updated for R500.x ) available from:
– Download the Software upgrade form the following link
http://teams.honeywell.com/sites/SRM/Shared%20Documents/Forms/AllItems.aspx
– Honeywell Process Solution website http://www.honeywellprocess.com
4 5/8/2017
2
One Stop Shopping for Information and Processes
• Migration Help Desk
– Pre-Migration analysis
• On-Line Support (OLS) website
– Software and patch update downloads
– Priority Notification and Beware documentation
– Experion Update Matrix
– Software Change Notice (SCN)
– Getting Started with Experion Software User’s Guide (GSG)
– Experion Migration User’s Guide (EMUG)
– Integrated Experion-TPS Nodes (ES-T, ESVT, & ACE-T) User’s Guide
5 5/8/2017
Migration Helpdesk
ATTENTION
When planning to perform system migration
contact the Honeywell Migration COE Help Desk
LSS.Migration.COE@honeywell.com
Migration COE Help Desk, working with TAC, can
offer valuable information and guidance in
planning and executing a complete system
migration
6 5/8/2017
3
Honeywell Process Solution Website
• Link: http://www.honeywellprocess.com
• Valid logon account required
7 5/8/2017
Important Reference Documents

• Getting Started with Experion Software Guide (GSG)
– Overview of the tasks involved
– Information of all Experion node
– Procedure to create a ESIS node
• Software Change Notice (SCN)
– Contains specific information about the release and must be reviewed before starting
migration activities
– Used in conjunction with the EMUG and is equally important
• Experion Migration User Guide (EMUG) and Migration Planning Guide
– Roadmap to successful migration
– Short cutting steps or bypassing steps will only render a failed migration. This will
increase time for the migration and create more work and poor visibility with the
customer
• Experion Software Installation User’s Guide (SIUG)
– Installation procedure for all Experion nodes
• Integrated Experion-TPS Nodes (ES-T, ESVT, & ACE-T) User’s Guide
– Additional steps and configuration required for Experion TPS nodes
• Priority Notices and Beware documents
– Identifies specific issues impacting migration activities and system functionality
8 5/8/2017
4
Installation - Custom Install Path
• Experion installation supports custom installation paths:
– Allows various Experion components to be installed on paths other than
default paths
– Users can choose to retain default or specify custom paths at time of
configuration file generation
Default Path Custom Path
9 5/8/2017
Custom Installation Path

• Custom installation path can be
selected for the following components:
– Experion PKS software: Consists of
deliverable that are part of Experion
installer and third party software
– Experion PKS runtime data: Consists
of the all the files and folders available
at “C:\ProgramData\Honeywell\” path
for the Experion release and the
Experion SQL databases
• Following files comes under this
category
Component available
– Runtime data
on ESV/ESV-T,
– Experion created SQL data ACE/ACE-T, SCE and
files EHG nodes
– Experion PKS SQL logs: Consists of
SQL database log files generated
during installation
10 5/8/2017
5
Custom Install Path Folder Security
• Experion installation applies same security to Custom Install Path
folders as default installation folders
Default Path Custom Path

C:\Program Files
(x86)\Honeywell\Experion PKS\ D:\Experion\Programs\Honeywell
UserB C:\ProgramData\Honeywell\
UserB D:\Experion\Data\Honeywell
Operator Operator
UserA C:\ProgramData\Honeywell\ UserA D:\Experion\Data\Honeywell\

Product Product
Administrator Administrator
Same Security as
Default Path
11 5/8/2017
Custom Install Path Restrictions (Contd..)

• Operating system has to be installed always in drive
• Only local drives supported:
– Network drives, USB's and Removable hard disks are not supported
• If the drive doesn't exist:
– an appropriate error message will appear, and the user can modify the drive
name
• Special characters supported in folder name:

– hyphen (-), space ( ) , forward slash (\), and underscore (_)
• Path length limit, up to 50 characters
• Only drive letter can be entered as the path:
– For ex: path can be only “D:\”
12 5/8/2017
6
• All nodes within an Experion Cluster must have the same Custom Install Path's defined
• Experion Software path cannot be same as Runtime Data path and SQL Logs path
• Custom and default paths to the same data cannot be combined in the same cluster
• Overlapping of Experion Software path with either of Runtime path or SQL Logs paths are
not supported
13 5/8/2017

• The Experion SQL logs path can be a subdirectory of the Experion
Runtime Data Custom Install Path
• The Experion Runtime Data path cannot be a subdirectory of the

Experion SQL logs path
14 5/8/2017
7
• Runtime Data path can be same as Experion SQL Logs path
• Experion PKS Software path should not begin with:

– C:\ProgramData, C:\Windows, C:\Users, C:\Documents and Settings or C:\Program
• Runtime Data and Experion SQL logs paths should not begin with:
– C:\Program Files, C:\Windows, C:\Users, C:\Documents and Settings or C:\Program
15 5/8/2017
R500 Installation Enhancements- Software Licensing

• Pre-R500 License Certificate
– Microsoft Word File containing a long string of Authorization Key
• In R500 License Certificate
– No authorization key
– XML based license file name is provided in place of authorization key
– License file enables the authorized features
16 5/8/2017
8
R500 Installation Enhancements
• Windows OS Platform Update
– Windows Server 2016 Standard for Experion Server/ACE/E-Server/E-APP
etc
– Windows 2010 Enterprise 2016 LTSB (x64) for Station Nodes
• Introduction of Experion PKS Installation Media 2
– Experion installation will now have the Experion Installation media 2, instead
of Experion PKS Support Software media
• Integration of Experion PDF Collection installation with Experion
installation
– Experion PDF Collection installation is integrated with Experion. An option to
select Experion PDF Collection appears in the Feature Selection dialog box
during installation
17 5/8/2017
Other Platform Changes with Experion PKS R500

• Microsoft SQL Server 2014 R2 Standard
Edition SP1
– Runs on Experion Servers and Experion
Redundant Servers
• Microsoft Visual Studio 2012 for CAB
• Microsoft Internet Explorer 11.0
• Microsoft Office
– MS Office 2013, MS Office 2010 and MS Office
2007
• Antivirus
– McAfee VirusScan Enterprise 8.8 Patch 7
– Symantec End Point Protection 12.1 RU6 MP5
• For Latest updated / qualified supported
versions of Antivirus or MS Office click on link
below:
Antivirus Software Guidelines
Certified Microsoft Office Packages
18 5/8/2017
9
Installation - Maintenance Tool
• Go to Start>Honeywell Experion Tools>All Honeywell Tools> Maintenance Tool
• Provides information on installed packages, optional features, and patches
• Provides option to remove above components
• Provides ability to view, modify or uninstall previous or new installation option
19 5/8/2017
Experion R500 Maintenance Tool

• In R500 MAINTENANCE TOOL optional features has Modify & Add
Option
– Based on optional feature selected user is prompted for media
20 5/8/2017
10
Install Optional Features from Maintenance Tool
• Select Add Optional Experion PKS Features option
21 5/8/2017
This page intentionally left blank
22
11
Architecture and Sequence of Class System
Migration Introduction Copyright © 2017 Honeywell International Inc. Architecture and Sequence of Class System
23 5/8/2017
Class System Architecture-In center
Crossover Cable
S01 S02
AD Y Y
G G
Domain Controller
DC#P
ACE OPC
HM AM
LCN
Y
Y Y Y
G G G
Experion Software EPKS Server A EPKS Server B Experion Station-TPS

Installation Server
(ESIS)
24 5/8/2017
12
Class System Architecture-Remote Class
Crossover Cable
S01 S02
AD
Domain Controller
DC#P
Y
Y Y Y Y
Y Y G
G G G
G G
Experion Software EPKS Server A EPKS Server B Experion Station Experion Station
ESV (DSA Node) OPC Installation Server
(ESIS)/Simulation Node
25 5/8/2017
Recommended Sequence
In Class In Class
Server B One ES-F One ES-C ES-CE
Perform
Compatibility
Tests
All ES-CE All ES-C All ES-F
Next Slide
26 5/8/2017
13
Recommended Sequence
Previous
Slide
eServer Server A ACE/SIM

(OFFPM only) (OFFPM only)
In Class
SCADA device Control

Controllers
communications Firewall (CF9)
Migration
Complete
27 5/8/2017
Migrate Domain Controller

• When migrating Experion system that is a member of Domain
– Domain Controller used in an Experion system operates as an independent
node
– Domain with Windows 2008 R2 Server operating system (OS) supports
Experion R500.x, R432.x,R431.x R430.x, R410.x, R400.x domain controller
packages
– Domain with Windows server 2012 operating system supports only Experion
R430.x,R431.x,R500.x
– Must update the Experion High Security Model package to the most recent
version when migrating the system
– Domain with Windows server 2016 operating system supports only Experion
R500.x
28 5/8/2017
14
Describe the On Process Migration
Procedures
Migration Introduction Copyright © 2017 Honeywell International Inc. Describe the On Process Migration Procedures
29 5/8/2017
On-Process Migration (OPM)

• What is On-Process Migration?
– On-Process Migration (OPM) is an ability to migrate Experion components,
while maintaining a view and control of process operations
– Performed only on redundant Experion components, specifically redundant
servers and controllers
• System migration involves two major stages:

– Server Migration (Software Migration of Experion Servers and Clients)
– Controller Migration (Firmware Migration of Experion Process Controllers
and I/O Hardware Components)
30 5/8/2017
15
Learn the OPM Process
• Understand the Concept of OPM

– Goal is to upgrade Experion PKS Software components without losing view
or control of the process at any time
– OPM procedures, checklists, tools, and pre-requisites are constantly

changing as the process matures
– On-Line Support is your best source of current OPM information
31 5/8/2017
Server, Controller, and Common Components

• Server / Client Portion of Experion PKS
– Developed primarily in Sydney, Australia
– Includes Experion server, redundancy, Station, DSA, Scripting, OPC,
history, SCADA Interface etc…
• Controller / Engineering Tools portion of Experion PKS

– Developed primarily in Ft. Washington, PA, USA
– Includes C200/C300 controller, Control Builder, ERDB database, NTools,
CTools etc…
• Common Components of Experion PKS

– Developed primarily in Phoenix, AZ, USA
– Includes FTE, System Management, RDM, Safeview, HCI Runtime, SES,
SPS etc…
• TPS Components for Experion PKS

– Developed primarily in Phoenix AZ, USA
– Includes components for TPS Interface, Gus packages, File Transfer etc…
32 5/8/2017
16
Experion PKS Databases
ffparameters
Server Database ps_erdb
OPCIntegrator
VersionControl
wlsparameters
hwsystem
EMDB
EMSEvents
Database Loaded
dasconfig
EMSPlayback
EMSOnline
..\Honeywell\ Data .. Files..
SQL Server Databases

33 5/8/2017

• ps_erdb:
– Has EPKS cluster’s control/display information
• EMDB (epks_emdb):
– Has EPKS Enterprise Model asset information
• ffparameters:
– Has EPKS FF device standard information. Used for FF device building into
library contained in ps_erdb
• wlsparameters:
– Has EPKS Wireless device standard information. Used for wireless device
building into library contained in ps_erdb
• Version Control:
– Has EPKS version control (QVCS) checkout information
• OPC Integrator:
– Has EPKS process server OPC connection information
34 5/8/2017
17
• emsevents:
– Has EPKS process server events
• EMSOnline/EMSPlayback:
– EMSOnline and EMSPlayback databases serve the purpose of allowing
operators access to past event data
35 5/8/2017
Experion PKS Databases – Operational View
Server / Client Controller / Engineering Tools
EMDB
Server
Database
Project
ERDB
EMS Events
Monitoring C200 / C300
Controllers
OPC
Integrator Version Control
36 5/8/2017
18
Experion PKS Databases – OPM View
Server Controller
On Process Migration On Process Migration
EMDB
Server
Database
Project
ERDB
EMS Events
Monitoring C200 / C300
Controllers
OPC
Integrator Version Control
37 5/8/2017
Goals
• Migrate Redundant Experion servers from R431.x to R500.x online
without interrupting process operations
– Migrate using ESIS
• Migrate Stations from Experion R431.x to Experion R500.x (General

Release)
– Migrate using Experion Software Installation Server (ESIS) node
• Migrate C200 Redundant Chassis Pair and C300 Redundant Controllers

to R500.x without interrupting control
38 5/8/2017
19
Prepare for On-Process Migration
Get latest MRT & Acknowledge Alarms

ECCfiles from
Honeywell Process Take Checkpoint
Solution Website *
Disable ERDB & EMDB

Run MRT/UT** to Verify
Replication ***
if System is ready
Fix issues (if any) Disable backup defined

in flbkup.def file
Secure all software * OLS Website:

media and patches www.honeywellprocess.com
** If base release is R400 and higher
then run Upgrade Tool only
Pre-Migration Checklist *** Prevents replication during migration
to avoid inconsistency
39 5/8/2017
On-Process Migration Flow – Experion Server and Client
Start Migrate Server B
Migrate One Client Revert to

Base Image
Migrate All PASS Server B and Client FAIL

other Clients Compatibility Check
Migrate Server A
Post-Migration task
Re-install Honeywell/
End
Third Party Packages
40 5/8/2017
20
On-Process Migration Flow – C200/C200E/C300 Controller
Start
Controller is NO
Redundant?
YES
On-Process Off-Process
Migration Migration
YES IO Modules
Migrate selected
Migration
IO Components
Required?
NO
End
41 5/8/2017
Supported Migration Path - Server/Client

• Migration Paths illustrate the path for an Experion System Migration
from the base release (or currently loaded software release) to the
target release (new release).
Migration Path to R500.1 OPM OFFPM Reference
R400.x (R400.1, R400.2 and R400.3)to
X X EMP
R500.1
R410.x (R410.1and R410.2) to R500.1 X X EMP
R430.1 to R500.x X X EMP
• EMP: Experion Migration Planning Guide EPDOC-XX70-en-5001A

Please refer Software Change Notice for latest information
42 5/8/2017
21
Supported Migration Path - Controller
• The following figure shows the valid migration paths supported for controllers
Migration Path to R500.1 OPM OFFPM Reference

R400.x (R400.1, R400.2 and R400.3)to
X X EMP
R500.1
R410.x (R410.1and R410.2) to R500.1 X X EMP
• EMP: Experion Migration Planning Guide EPDOC-XX70-en-5001A

Please refer Software Change Notice for latest information
43 5/8/2017

• Qualified Controller Migration Paths for interface module and I/O module
firmware are found using the Migration Readiness Tool
• When migrating C200 (CPM), SIM and LIOM modules, the firmware is
migrated to the latest available firmware, which is R311.x.
– There is no R4xx/R5xx firmware for C200 (CPM), SIM and LIOM
Even though the C200 firmware is freezed at R311.

C200 controllers are compatible with Experion R500
44 5/8/2017
22
• Typical controller migration scenarios are described in the following
table
Experion Control Hardware On-process migration Off-process
(Only if redundant) Migration
Controllers: C200 (CPM), C200E & C300 X X
EHPM & IEC61850M X X
Interface Modules:
RM, IOLIM, FIM, FIM4, FIM8, FTEB, X X
CNI, LIOM
I/O Modules: Series C IOM’s X X
Series A IOMs, Series H IOMs
X
(non-redundant)
Application Environments:
X
ACE, SCE, SIMLIOM
EHG X
45 5/8/2017
On-Process Migration Requirements

• Experion Systems requires a license to conduct On-Process Migration of
system software
• Starting with Experion R300.1 Systems, the OPM license is combined

with the Server Redundancy Purchasable Option
– OPM License information is enabled on Redundant Servers
• Controllers must be Redundant to perform OPM

– Controller Migration Wizard will not allow OPM if not redundant
• R500 License Key is required before starting migration to R500.x
46 5/8/2017
23
OPM Tools – Upgrade Tool
• Upgrade Tool (UT) is a software application that performs prerequisite
checks on the System and its components
– Launched from Configuration Studio
– Ensures Experion System’s readiness for migration
– Run prior to starting a migration
– The UT is run for
– Servers
– Controllers
– I/O chassis
– Remote Chassis Modules
– Control Network Platforms
– Once the UT is run, a report is generated to indicate the readiness of the
System and its components for migration
– Download the latest version of UT files from the Honeywell Online Support
Website www.honeywellprocess.com User needs to register with Honeywell
to access this website
– UT is not used for SCADA System
47 5/8/2017
OPM Tools – ERDB Consistency Checker

• ERDB Consistency Checker Utility performs a check on the Engineering
Repository Database for any inconsistencies:-
– These inconsistencies may cause a problem during a migration or cause a
migration to fail
– Run this check before you start a migration in order to detect and eliminate
problems which might appear during or perhaps even after the migration
– Download the latest version of ERDB Consistency Checker files from the
Honeywell Online Support Website www.honeywellprocess.com
(Registration is required to access this site)
– ERDB Consistency Checker is not used for SCADA System
48 5/8/2017
24
OPM Tools – Controller Migration Wizard
• Controller Migration Wizard Application migrates (upgrades) the
firmware in Experion Control Hardware to a newer release:-
– Experion Control Hardware includes:-
• Process Controllers
• I/O Interface components and associated I/O Modules
• Install Sequencer coordinates the migration of system software to the

target release for servers and clients and:
– Automates many migration tasks performed manually in previous
releases
– Runs on a server/client to be migrated
– Allows for hardware and operating system upgrades during the
migration process
– Manages reloading of system database to server after installation of
new release
49 5/8/2017
OPM Tools – BOOTP Checker Tool

• BOOTP Checker utility is used to detect the BOOTP Server on the FTE
and Control Net (via Ethernet) Communications Network in a Process
System
– Queries the local database to verify whether the NTP Servers are configured
on the Local Server
– Use this tool before a migration to check whether there are multiple BOOTP
Servers configured on the network
• There should be only one BOOTP Server running on the network
– Download the latest version of this utility from the Honeywell HPS Online
Support site at www.honeywellprocess.com (Registration required for site
access)
– The BOOTP Checker is not used for SCADA Systems
50 5/8/2017
25
OPM Tools – RTools
• RTOOLS assists the HPS Migration Helpdesk to gather files from your
System. Most of these files are not currently collected in a DCT
51 5/8/2017

• To run RTOOLS, double-click RTOOLS.EXE and select the “Click to Run RTOOLS”
button.
• RTOOLS collects the following information from the system (if available). An RTOOLS
subfolder will be created with several subfolders to store the following files.
– a) Windows Event Logs (System, Application, Security)
– b) Experion Windows Event Logs (FTE, HwSysEvt)
– c) Windows HOST File
– d) Honeywell Registry Information
– e) Experion Installation Options File
– f) Experion software Update Log
– g) Experion setup Log
– h) Current Experion Server Log File
– i) Product Version File
– j) Product Contents File
– k) Contents of Install Folder (Directory Listing)
– l) Engineering Tools Error Logs
– m) Common Components Log
– n) Windows Time Zone Information
52 5/8/2017
26
• Once running, RTOOLS will provide a status update of the data it is current
collecting
• When complete, RTOOLS will compress the above files into a single CAB file
and then delete the copy of the files it has made.
• Please include the Computername_RTOOLS.CAB file in the data being sent to

the Migration COE Helpdesk.
• If you have any questions or feedback about RTOOLS, please contact mail
to:LSS.Migration.COE@Honeywell.com
53 5/8/2017
Upgrade Tool
• Upgrade Tool is Migration and Interoperability Tool to :-
– Increase scope of existing M&I tools from Experion Server and Controllers to
other nodes in Experion Server Cluster
– Reduce the time and effort being spent by site engineer in collecting and
analyzing site data. This helps Migration COE Help Desk and TAC to reduce
the time taken for site preparation.
– Have capability to determine the possibility of Experion PKS system to break
other subsystems while migration
– Make migration process easy and reduce the dependency on EMUG while
migration
– Analyze and identify the current problems in Migration process and make
some improvements
54 5/8/2017
27
Upgrade Tool - Features
• Gets installed as part of Experion Server installation
– In case of redundant servers gets installed on both servers
• Uses the existing migration tools like Migration Readiness Tool, ERDB
consistency checker, BootP checker etc
• Utilizes features of Experion like System Management, EMDB,
Configuration Studio, Diagnostic Studio etc
• Does not depend on any specific Experion topology
• Records all level 1, 2 and 3 hardware components and their
software/firmware versions
• Depends on Plug-in Architecture
– Invoke the plug-ins on the nodes to perform data collection, diagnostic data
capture, readiness check
• Applicable only for migration from R400 to further releases
– Can be used for Controller Migration from R3xx.x to R400 once the servers
are upgraded
• Available for both On-Process Migration and Off-Process Migration
55 5/8/2017
Upgrade Tool - Functions

• Upgrade Tool automates the manual cluster preparation tasks in the
migration process
• It performs the following functions
– Collect system data and diagnostic data from all migrating nodes
– Analyze the nodes in cluster for migration readiness
– Validate each and every node and component that can be upgraded
– Analyze the data collected to generate upgrade instructions
– Present the data in form of reports to analyze and to improve the migration process
Upgrade Tool
Data Diagnostic
Collection Data Capture
Readiness Upgrade
Checks Instructions
Reports
56 5/8/2017
28
Upgrade Tool
• I/O rendition in Upgrade Tool:
– Upgrade tool displays the following I/O rendition:
• Green color - For latest firmware version supported for migration
• Cyan color - If the firmware is new, the same color (cyan ) for most recent
identified firmware in ver_rev text file is used
• Red color - For firmware versions that are not supported for migration
• Support for Readiness Checks in Upgrade Tool for Off-process Migration:
– Readiness checks for off-process migration are supported using the Upgrade tool
OPM
OFFPM
57 5/8/2017
Upgrade Tool- Prepare Upgrade Tool Cluster

• In R431 three questions introduced in Migration method section of GI
page :
– Are you planning for the hardware change?
– Are you planning for the virtual environment?
– Are you planning for a operating system change?
Mandatory questions are marked with an asterisk (*)

1. First 3 questions under "Migration Methods" section;
default selection will be Hardware (No), Virtual (No) and
OS (Yes)
2. If the user is not changing answers to any of the
mandatory questions, guides will be added based on
the default selection only.
3.If the answer to any of the mandatory question has
changed, guides will be added based on the changed
user selection.
58 5/8/2017
29
Cont…
• Upon navigating to the Customize Instructions (CI) page,
– The guides added to the list in the left pane are based on the selections that
were made to the answers under the "Migration Methods" section of the GI
page
59 5/8/2017
Upgrade Tool (Contd..)

• Migration Guides
– Upgrade Tool uses the Migration Guides available on the Experion Upgrade Tool
Components media
• Depending on the site configuration, generates the site-specific migration guides
– Applicable for migration from R400.x to further release
• For migration from R31x scenario-specific migration guides has to be used
60 5/8/2017
30
Upgrade Tool (Contd..)
• Experion PKS Upgrade Tool Component Media
– Until R431,site specific guides could be generated only on Experion nodes
using the Upgrade Tool
– Starting Experion R431,a new tool is introduced to generate site-specific
guides on non-Experion nodes
• The new Tool-Experion PKS Upgrade Instruction Management Tool (UIMT)
– UIMT fulfils the need for migration guide generation
– Use of UIMT allows you to become familiar with the process of migrating
Experion system without the need to access a live system
– Applicable for migration from R400.x to further releases
61 5/8/2017
Upgrade Instructions (UI)

• Clicking "Next" button on CI page navigates to the Upgrade Instructions
(UI) page:
– The instructions that were listed in the left pane of the CI page are brought
forward to the list in the UI page
• User will have the documents merged into a single document by clicking
the save icon
• Document save in .XPS format.
62 5/8/2017
31
3rd Party Hardware detection from Upgrade Tool
• In the General Data Collection page 3rd party Hardware's are shown as:
• In the Customize Instructions page 3rd party Hardware’s are shown as:
63 5/8/2017
3rd Party Hardware detection from Upgrade Tool Contd.

• In the Upgrade Instructions page 3rd party Hardware’s are shown as:
64 5/8/2017
32
GDC Discovery and Data Collection Separation
Server B or Standalone L2 Node and L1 Nodes

by default checkbox checked and disabled
L1 discovery and data collection comes by

default, checkbox is checked and disabled
L2 Nodes discovery happens only at very first

time
GDC Tree will NOT show any other "ServerB

and StandAloneServer" nodes
Select the L2 nodes from left side tree and click

on "START" button
Data collection for selected nodes start
After GDC completion user can see selected L2
nodes information on right side of the panel
65 5/8/2017
Add Computer Popup
Add Computer popup will NOT show any

other "ServerB and StandAloneServer"
nodes
66 5/8/2017
33
GDC Page Delete Computer Button
67 5/8/2017
Migration Type Selection from GDC Popup

• Users can generate "On-Process/Off-Process" readiness check and
Migration Guides according to the migration selection.
68 5/8/2017
34
Cont…
• User can switch on-process to off-process and click on "Proceed" button
– Changes will be reflecting in RC/CI/UI pages according to the migration type
69 5/8/2017
COE Rules of Engagement : Process Map

• Solution Architect Requests for COE Support
• FSM/FOL/PM Request for COE Support
70 5/8/2017
35
Flow Chart: Register COE Support Request
• For all COE support requests, a completed Scope Definition Form must be
provided which contains the minimum information required for review.
• Service Request is then created and assigned in the appropriate COE queue.
• Resources are then assigned and Travel approvals are obtained.
• The COE calendar is then updated.
71 5/8/2017
Flow Chart: COE Scope or RFQ Support

• Upon receipt for a request for support COE can assist sales to check technical
feasibility and technical scope of a project.
• Using the completed Scope Definition Form, customer data and customer
requirements.
– The COE Engineer will review all the information and ensure that the proposed
solution is technically feasible.
72 5/8/2017
36
Flow Chart: COE Execution Preparation
• Using the information gathered during the system analysis, the Execution Plan is
created
– The solutions for Known Errors are included within the execution plan and are
documented for correction on site
73 5/8/2017
Flow Chart: COE Execution Support

• This procedure documents the steps required to execute the project.
• At the end of this process the work is performed and accepted by the customer
74 5/8/2017
37
Describe the Off Process Migration
Procedures
Migration Introduction Copyright © 2017 Honeywell International Inc. Describe the Off Process Migration Procedures
75 5/8/2017
Off Process Migration

• Migration of an Experion Control System or Migration of an Experion
System Component while it is not controlling the process and there is no
view of the process
– Integrated Experion-TPS Nodes can maintain view of the process through
the TPN while the Experion Off-Process Migration is in progress.
– Non-redundant Experion System and control components must be migrated
Off-process
• Develop an Off Process Migration Plan if it is scheduled during plant

maintenance shutdown
– Off Process Migration plan is necessary to ensure resource availability
during the migration
• Use Migration Applications and Tools to verify System Readiness and

perform Off-Process Migration
– Different Migration Tools are available to verify if System is ready for
Migration
76 5/8/2017
38
Off Process Migration
• Node or Controllers that are migrated Off-Process are:
– Server/Client (Off-Process)
– eServer
– Application Control Environment (ACE)
– Application Control Environment – LCN Connected (ACE-T)
– Simulation Environment
– EHG Server (EXXON only)
– Non-redundant C200’s/C200E’s/C300’s
• Release interoperability may not be necessary when you migrate a

system Off-process
– As all system components are migrated before re-starting the process
77 5/8/2017
Off Process Migration Scenarios

Both Server OFFPM and Controller OFFPM are supported in the following seven cases:
Redundant C200 on Ethernet does not support OPM SCADA devices does not support OPM
Station Station
Single or
802.3 Station Dual
802.3
802.3
EPKS
EPKS Server EPKS Optional
Server 802.3 Server 802.3 or
802.3 ControlNet
Controller
SCADA
Controller Controller
device
Station Station ACE

Station
802.3
802.3 FTE
Station ACE
EPKS EPKS
ACE EPKS FTE
Server ACE
ControlNet Server Server
ControlNet EPKS ControlNet
Controller
Server
Controller Controller
Controller
ACE does not support OPM
78 5/8/2017
39
Describe the Server/Client Migration Paths
Migration Introduction Copyright © 2017 Honeywell International Inc. Describe the Server/Client Migration Paths
79 5/8/2017
Server/Client Migration
• Server/Client Migration
– Migration of Experion PKS Servers, Stations and their loaded software
– Upgrades or re-install Operating System Software
– Perform a Platform Change – replacing or upgrading the computer hardware
• Adding more memory to a server, or even upgrading to a newer
computer or operating system.
• Note that it is possible to migrate only the servers and then migrate
other components at a later date.
80 5/8/2017
40
Migration Types
• On-process Migration, OPM
– These are Migrations between two Functional Releases
– The Redundant EPKS Server software is updated without losing the
view of the process
– The Redundant Controllers are updated without losing the view of the
process
– Some Non-redundant Components are updated Off-line
• Off-process Migration, OFFPM
– All Components are updated Off-line
• Controller OPM
– Only the Redundant Controllers are Updated without losing the view
of the process (migration or updating)
• Server OPM
– Only the Redundant EPKS Server Software is upgraded without
losing the view of the Process (migration or Updation)
81 5/8/2017
Special Migration Types

• On-Process Updation, OPU
– These are the upgrades within a functional release, in form of
hotfixes, patches, updates, point releases, and maintenance
releases
– Special conditions in R210 Series System Updates
• EHG Migration OPM
– These are the EHG Specific System Updates
• SCADA Migration OPM
– These are special cases in Migration to R301
• SCADA Migration OFFPM
– These are special cases in Migration to R301
• SCADA to Process Conversion
– These are special cases in Migration to R310.2 & R400.1
• Extended On-process Migration
– This functionality is released in R400.1
• Patch Reinstallation is Required
– The source patch has to be reapplied in the target release
82 5/8/2017
41
Hotfix Migrations and System Updates
• Restricted Hotfixes
– These Hotfixes have to be uninstalled before the subsequent Migration
or System Update
– The OPM is not available with restricted hotfixes
• Non-restricted Hotfixes in Migration
– These Hotfixes have to be Uninstalled during the Subsequent Migration
– The OPM is available with non-restricted hotfixes
• Non-restricted Hotfixes in System Updation
– These Hotfixes have to be Uninstalled during the Subsequent System
Update
– The OPU is available with Non-restricted Hotfixes
• Prerelease Hotfixes in System Update
– These Hotfixes will not require any actions during the Subsequent
System Update
– The OPU is available with Prerelease Hotfixes
• ECC list all Restricted and Non-restricted Hotfixes starting in R300.
These are known as Patches starting in R301.2 and R310.2
83 5/8/2017
Supported Migration Paths

• The picture here presents a very simplified version of Supported
Migration Paths (On-Process or Off-Process)
R400.1, R400.2 and R400.3
R400.x R410.1, R410.2

R410.x
On-process Migration
R430.1
R430.x
Off-process Migration R431.1
R431.x R432.1
R432.x
R500.1
84 5/8/2017
42
Migration
• Support for N-3 Release
– On-Process Migration (OPM) in Experion Release R500, supports Migration
of Nodes from N-3 Release to N Release
• Example: Nodes on R400.1 Release can be directly Migrated to R500.1
Release
Release Release Release Release N

N-3 N-2 N-1
OPM OPM OPM
OPM
– Supports Migration of TPS Connected Experion Systems

– Supports Migration of Dongle Protected Experion Systems
85 5/8/2017
Migration Scenarios – Server/Client

• Experion R500 Server/Client Migration is supported
– Using Application Software Media Set
– Using Experion Software Installation Server (ESIS) which can be created on
• Local Hard Disk that can be accessed using Network Share
• USB Pen Drive
• Removable Hard Disk
• Some Migration scenarios may require a hardware upgrade or re-
installation of the Operating System for Servers and Clients
– See table on the next page
86 5/8/2017
43
Migration Scenarios – Server/Client (Cont..)
Operating System Installed Experion Release Installed Install Sequencer Behavior
Windows Server 2016 Standard None
Performs a clean install of Experion R500.1
(64 bit)
Windows 10 Enterprise 2016 LTSB None
Performs a clean install of Experion R500.1
(64 bit)
Detects the previous version of Experion on the
computer. Starts the install Sequencer to
Windows Server 2008 R2 Experion R431.1/R432.1 perform migration to Experion R500.1 with an
operating system change to Windows Server
2016 Standard(64 bit).
Windows 7 Professional (64 bit) Experion R431.1/R432.1 perform migration to Experion R500.1 with an
operating system change to Windows 10
Enterprise 2016 LTSB(64 bit)
Windows Server 2008 R2 Experion R410.1/R410.2/R430.1 perform migration to Experion R500.1 with an
operating system change to Windows Server
2016 Standard(64 bit).
Windows 7 Professional (64 bit) Experion R410.1/R410.2/R430.1 perform migration to Experion R500.1 with an
operating system change to Windows 10
Enterprise 2016 LTSB(64 bit)
87 5/8/2017
Migration Scenarios – Server/Client (Cont..)

Operating System Installed Experion Release Installed Install Sequencer Behavior
computer. Starts the Install Sequencer to perform
Experion
Windows Server 2008 (32 bit) migration to Experion R500.1 with an operating
R400.1/R400.2/R400.3
system change to Windows Server 2016 Standard(64
bit).
computer. Starts the Install Sequencer to perform
Windows 7 Professional (32 bit) Experion R400.1/R400.2/R400.3 migration to Experion R431.1 with an operating
system change to Windows 10 Enterprise 2016
LTSB(64 bit)
88 5/8/2017
44
TPN Software
• Minimum Release Level of TPN Software that is fully compatible with Experion Released
Software
Compatibility for... LCN Software Release

ES-T and ESVT Integration with any Experion Release TPN R652.1 or Higher
ACE-T Integration with any Experion Release TPN R652.1 or Higher
• Migration COE migration analysis always recommends updating to the latest TPN release
Experion Releases TPN Compatibility

R201, R21x , R301.x R641.2
TPN R535.1 or later R5xx releases in this series
R400.x, R410.x, R430.xR431.x and R500.x
TPN R652.1 or later R6xx releases in this series.
TPN R683.2 or later and Experion R410.x (R410.1 and R410.2) is required for:
• New TPS Console/System alarm integration
•Fully functioning integration for HMI web TPS Detail Displays
89 5/8/2017
Honeywell Experion PKS Localization Media

• Localized Experion System to be migrated will need additional software
– Experion PKS R500 EUI Pack – For the Language of the Base System
• For Windows Server 2008 R2:
– Windows Server 2008 R2 MUI Pack CD for desired language
– Microsoft Office 2007 MUI Pack CD
• For Windows 7 (64bit):
– Experion PKS R500 EUI Pack CD
– Contains the Language Pack Installer (LPI) which is used for installing the
Language Pack
– Microsoft Office 2007 MUI Pack CD
90 5/8/2017
45
SCADA System Communication Protocols
• Experion SCADA Server communicates with a variety of SCADA
Devices using different Protocols (such as Modbus, Allen-Bradley, etc).
• Most of these Protocols are not under control of Honeywell, but the
majority of these Protocols have not changed.
– Unless there is a Protocol change, it can be assumed that the new Releases
of Experion Server will continue to be compatible with existing SCADA
Devices
91 5/8/2017
Migrating Other Honeywell Products and Applications

• Following Honeywell Applications installed on nodes within an Experion System
are not Migrated as part of Experion Migration
– Alarm Pager – Process History Database (PHD)
– Control Component Libraries (CCLs) – Process Performance
– Digital Video Manager (DVM) – Profit Suite
– Field Device Manager (FDM) – Safety Manager
– Asset Manager – Simulation
– DaVinci Server, Quality Server, – TPB
MxProLine Server – User Alert
– OMS – Uniformance
– BMA 400 – EBR
• Specific considerations for some of these applications when Migrating Experion
Software are given in EMUG
• Migration Application detects and prompts software applications (both Honeywell
and third-party applications) that will not be migrated
– Appropriate actions should be taken to preserve these applications and user settings
so that they can be restored after migration
92 5/8/2017
46
Migrating Non-Experion Third-Party Applications
• Most non-Experion Applications are not migrated as part of Experion
Migration
– Consider a strategy for saving the data and configuration files for these non-
Honeywell (Third Party) Applications
– This is required so that the data and user settings are restored with the
application after Experion Migration is completed
• Following is an example of Third-party Software Applications

– Virus Protection Services Applications which are not migrated
• Experion R500.x Operates with Windows Firewall Enabled

– Verify Third-party Applications are set to Operate in a Firewall Environment
93 5/8/2017
94
47
Describe Controller Migration Paths
Migration Introduction Copyright © 2017 Honeywell International Inc. Describe Controller Migration Paths
95 5/8/2017
Controller Migration
• Controller Migration is the migration of firmware installed in Experion Control
Hardware to a newer version release
– Includes C200/C200E, C300, Series C FIM4s, Series C FIM8s, Series A, Series H,
Series C IO and LIOM.
– Migration of C200 Controllers may include CPMs, RMs, one or more FIMs and IOLIMs
which are installed in the controller chassis and any I/O components associated with a
controller
– For Series C Control Hardware, migration includes loading newer firmware to C300
Controller Modules, FIM4s, FIM8s and any I/O Modules
• Only Redundant Chassis Pairs (RCPs) can be Migrated while On-process
– An RCP is a pair of chassis that include Single ICP Enclosures with backplane, power
supply, communication(s), and in most cases controller module(s) configured for
Redundant Operation
– RCP may also be a pair of modules, such as two FIMs, IOLIMs or other Chassis
Modules that are Redundant, where each is installed in Redundant Chassis (Primary
and Secondary)
– I/O Components associated with the controllers are Migrated Off-process; after the
Controller and/or after I/O Interface Modules have been Migrated
96 5/8/2017
48
• Redundant Controller Interface components in an RCP can be selected
for On-process Migration, such as FIMs and IOLIMs.
– When a Redundant Interface Module in an RCP is selected for Migration,
both Primary and Secondary Modules are Migrated
• Redundant Series C Control Hardware can be Migrated On-process as

well as Off-process,
– Non-redundant Series C Hardware can only be Migrated Off-Process
• Controller Migration Wizard Application is used to Migrate Controller and

Control Hardware Firmware
– Wizard automates many of the tasks performed in Controller Migration and
can be used for both On-Process and Off-Process Migration
– Controller Migration Wizard is invoked from Control Builder
97 5/8/2017
Enabling OPM of SPM and SVPM

• Enable OPM of SPM and SVPM:-
– SPM and SVPM can be used outside turbine control application
– Capabilities similar to series C hardware required for SPM and SVPM
– Non-TC application, SPM and SVPM can be upgraded on process
– TC application, use of standard OPM tool permitted
– Enables system upgrades during maintenance period when
– Control is active
– Taking care of auxiliary tasks
OPM is possible only from

R410 to further releases
98 5/8/2017
49
• Controller Migration is the upgrade of firmware installed in Experion
Control Hardware to a newer version release
– Only Control Hardware that is Redundant can be Migrated On-Process
– Non-redundant Control Hardware can only be Migrated Off-process
Experion Control Hardware Comment
Controllers: C200 Controller includes a Redundancy
C200* (CPM), C200E, C300/C300 with EHB Module (RM) and may contain any of the
personality following interface modules: IOLIM, FIM,
EHPM and IEC61850M can be migrated FTEB, CNI, LIOM. C200 Controller may also
using Controller Migration Wizard. contain I/O Modules.
Interface Modules: RM, IOLIM, FIM, FTEB, These modules support Redundancy and
CNI, LIOM, Series C FIM4 and FIM8 & PGM can be Migrated On-process
I/O Modules: These modules support Redundancy and
Series C IOMs can be Migrated On-process
Series A IOMs, Series H IOMs (Non- Non-redundant Modules support only Off-
redundant) Process Migration
*Redundant C200 Controllers, which comprise a Redundant Chassis Pair (RCP),
contain identical Chassis Modules.
99 5/8/2017
Migration Scenarios – Controller

• Controller Migration is performed after Server/client Migration
• Depending on System Topology and the installed I/O, migration of
controllers and control hardware can be performed a number of ways
– Typical Scenarios are explained in the table below and on the next slide
Use the Controller Migration Wizard

Controller Migration Scenario
and…
On-Process Migration Scenarios
Select Redundant C200 Controller Chassis (Primary and
Redundant C200 Controller Chassis – which
Secondary chassis) at one time for On-process
includes redundant controller modules, such as
Migration. All redundant components in the Controller
CPM, RM, CNI, IOLIM, FTEB and FIM. The
Chassis will be Migrated at once. Also, Individual
controller may reside either on the Supervisory
Controller Interface Components in an RCP that are
Network or on a I/O Network (currently not
Redundant can be selected for Migration, such as FIMs
supported for the CPM and IOLIM modules).
and IOLIMs.
On-Process Migration, Redundant C300
Select Redundant Controller Modules for Migration.
Controllers
On-Process Migration, Redundant Select Redundant Fieldbus Interface Modules
FIM4/FIM8/PGM (FIM4/FIM8/PGM) for Migration.
100 5/8/2017
50
Migration Scenarios – Controller
Use the Controller Migration Wizard
Controller Migration Scenario
and…
Off-process Migration Scenarios
Perform Migration of Redundant Controller Chassis Off-process.
Off-process Migration, Redundant Chassis All Redundant Components in the Controller Chassis will be
Migrated at Once
Select a Non-redundant Controller Chassis for Off-process
Off-process Migration, Non-Redundant Chassis Migration. All Components in the Controller Chassis (except I/O)
are migrated at once
Off-process Migration, Redundant C300 Controllers Select Redundant Controller Modules for Migration
Off-process Migration, Non-redundant C300 Controllers Select Individual Controller Modules for Migration
Off-process Migration, Non-redundant Controller
Select Individual Controller Modules for Off-process Migration
Modules, (CPM, CNI, IOLIM, FIM, FTEB and LIOM)
Select Redundant Fieldbus Interface Modules and PGM for
Off-process Migration, Redundant FIM4/FIM8/PGM
Migration
Select individual Redundant Fieldbus Interface Modules and PGM
Off-process Migration, Non-redundant FIM4/FIM8
for Migration
Off-process Migration, Associated I/O Modules Select Individual I/O Modules for Off-process Migration
Select individual ACE/SIM-ACE or SIM-C200 Control Nodes for
Off-process Migration, ACE/SIM-ACE and SIM-C200
Off-process Migration
Off-process Migration, Redundant EHPM Select redundant EHPM for migration
Off-process Migration, Non-Redundant EHPM Select individual EHPM for migration
101 5/8/2017
Controller Migration Path

• Valid Migration Paths supported for Experion R500.1 Controllers
R400.1 CPX, R400.2 CPX. R410.1 CPX, R410.2 R430.1 and R430.2
R400.3, R400.4 R410.3, R410.4
R431.1 and R432.1
R500.1
102 5/8/2017
51
This page was intentionally left blank.
Copyright © 2016 Honeywell International Inc.

HPS Automation College written permission required to distribute
Honeywell Confidential and Proprietary
Plan the Migration
Plan the Migration Copyright © 2017 Honeywell International Inc. Plan the Migration
1 5/8/2017
Migration Planning
• A System may contain one Experion Cluster, or in a Larger System, a
number of Experion Clusters
– Experion Cluster consist of computers that host Redundant Servers, Clients
(both Flex and Console Stations), and associated controllers
• Large plants may contain number of Control Systems that have many
Experion Clusters populated throughout the plant
– Larger Experion Clusters may consist of Redundant Servers; associated
clients (both Flex and Console Stations), an ACE Node and a set of
Controller Components
– During Planning, it may be decided to migrate Nodes within one Cluster and
then migrate all, none, or a portion of the Controller Components of that
Cluster
– The Servers in all the Experion Clusters of a Control System may be
selected for migration now,
• Controller Migration could be scheduled for a later time.
– Interoperability of System components is possible with some restrictions.
• Migrate and operate servers and clients on the new release software
and operate controllers and other system nodes running at the base
release
2 5/8/2017
1
Migration Planning
• Create a Migration Plan
– Planning minimizes problems during migration and helps to ensure migration
is successful
• When planning for Migration, the following must be considered:
– Structure and size of the Control System
– Process controlled by Experion
– Consider hardware changes to the System
– Use ESIS or Physical DVD
• Develop a Comprehensive Migration Strategy
• Develop a Migration Timetable
• Review Software Requirements
• Migration of other Honeywell products and applications
– Review the EMUG for a listing of these products and reconfiguration
requirements
• Migration of other 3rd party application
– Most 3rd party applications are not migrated as part of the OPM
3 5/8/2017
Migration Planning
• Experion Software Installation Server (ESIS)
– ESIS is a file server/file share hosting Server Operating System
– ESIS can be accessed over the network or removable disk for installation
and migration
– Windows node capable of hosting a share with account security
– Has available disk space to host the Experion Installation Media
– Refer to the GSG for detail procedure on setting up ESIS Node
• Experion Migration Storage Node (EMSN)
– EMSN is a shared folder used to store and retrieve database and
configuration information contained on Experion Node
– EMSN Node must have sufficient disk storage so that information can be
copied from server or client being migrated
– Space availability is:
• automatically checked during migration to ensure enough storage space for the
server/client.
• done to estimate space required for Honeywell Software Migration. Non-
Honeywell packages are not considered in this estimate
Note: A quick manual check is recommended prior to starting actual migration
• ESIS and EMSN cannot be hosted on the same node
4 5/8/2017
2
EMSN on Removal Media
• Experion releases 400.3, 410.2 and later support EMSN being hosted
on removal media
– USB storage media
• Provides ability to isolate migration process from Process Control
Network
• Provides ability to install Server B off network in case of Platform change
scenario
– Cancel migration after Phase 1 and install Server B off network
• Restore Server B for normal redundant operation
Experion Node
Migration Phase 1: Data Backup
USB Storage Media
5 5/8/2017
Migration Planning
• Network Topology changes are not allowed during the Migration
• Platform Change and Product Change supported
– SCADA to Process Product Change
– Platform Change from obsolete to newly supported platform
• Migration of combined Experion PKS and TPS Systems
– Experion Server/Client - TPS (ESVT/EST) are migrated when migrating to
R500.x
• Interoperability Restrictions
– Ability of a version to work with another version simultaneously
• Pre-migration Checks
– Checks will minimize or eliminate errors/faults encountered during an On-
Process Migration
• Migration Considerations - IMPORTANT!
– EPKS System allows various options to be selected during installation.
Installation requirements need to be decided prior to starting installation.
6 5/8/2017
3
Migration Planning
• Post Migration Task
– Complete tasks to restore the System to Full Performance and enable new
features available in Experion Release R500.x
• Some of these tasks are:
– Remove configuration for ESIS Installation/Migration
– Set Up a new BootP Server and NTP Server on R431.x Nodes
– Reconfigure Ethernet Switches and FTEB Modules if required
– Enable new features that are now available (These will be discussed later)
– Restore Honeywell Products and applications that were not part of the
Experion Migration
– Reinstallation of third-party applications
• Supplementary Installation Task Guide
– Additional post-installation and post-migration tasks
– Available in PDF collection
7 5/8/2017
Log Locations
• There is now only one version file that shows all the Experion software
and patches that are installed or uninstalled on a Node. It is located at:
C:\Program Files (x86)\Honeywell\Experion PKS…ProductVersion
• All Install Log Files are located in one folder at

C:\Program Files (x86)\Honeywell\Experion PKS\Install
• There is an Overall Installation Summary file that indicates what the

software install choices and options were; the date/time of the
installations including reboots and what the overall status of the
installation. It is located at
C:\Program Files (x86)\Honeywell\Experion
PKS\Install\InstallationSummary.txt
8 5/8/2017
4
Simple Timesavers for OPM
• If using an ESIS for migration, then ensure the ESIS is setup and
configured
– Not required if migrating using Physical DVD
• Map out all Data Paths into/out of Server
• Create one display with representative data from each data source – to
use as overview of System Health.
– Controller Data
– SCADA Channel Data
– OPC Data
– DSA Data
– Script-updated Data
– Make a CD containing
• all Server, Controller, and Common Components Patches for your target
release.
• with the latest Microsoft Security Patches
9 5/8/2017
10
5
Setting up the ESIS
Plan the Migration Copyright © 2017 Honeywell International Inc. Setting up the ESIS
11 5/8/2017
Experion Software Installation Server Setup

• ESIS is a Windows Networking Based Node
– Capable of hosting a share with Account Security
– Has available disk space to host the Experion installation Media
• ESIS can be accessed over the Control Network for installation and migration of
System software on multiple Experion System Nodes undergoing migration
• Eliminates DVD Swapping
• ESIS and EMSN cannot be hosted on the same Physical Nodes
• The ESIS Hardware Platform must support one of the following Operating
Systems:
– Windows 7 Professional 64-bit
– Windows 10 64-bit
– Windows Server 2008 (64-bit)
– Windows Server 2016 Standard (64-bit)
• Server OS is recommended for ESIS
12 5/8/2017
6
Experion ESIS Setup Restrictions
• The ESIS should be located as close as possible to the nodes to be migrated to
optimize network traffic during migrations and installations
• The ESIS does slightly impact Network Traffic Bandwidth
• ACE and SCE Migration are not supported
• On-Process Migrations – do not perform more than two nodes simultaneously
• Off-Process Migrations – assuming that other control devices may be on the

network, it may be possible to migrate up to four nodes simultaneously
depending on network bandwidth
• For Clean Installations – assuming that there are no critical control systems
running, there are no limitations concerning the number of nodes that may be
setup simultaneously
• For adding nodes on an existing running system, the limit is two nodes
simultaneously
13 5/8/2017
Experion ESIS Setup

• The ESIS will require approximately 33GB of the hard drive
• Planning is very critical for establishing the ESIS and the EMSN required
for migrations
• The network link speed on the node where ESIS is being set up, must
match the link speed on the switch to which the node is connected
– Link speed is 100 Mbps Full Duplex for an FTE-based Network
14 5/8/2017
7
Experion ESIS Setup
• Insert the Experion PKS Installation Media into the designated ESIS
Node DVD Drive
– If the OS supports the “Autorun”, user will select the option to “Setup an
Experion Software Installation Server”.
– If the System does not support ”Autorun,” browse to the Root of the DVD
and run the “cdbrowse.exe”. This will start the Installer. Selection of the
ESIS is now possible.
Click to
setup ESIS
15 5/8/2017
Experion ESIS Setup

• The installation of the ESIS will launch the following screen.
• If the ESIS Preparation Utility is launched on the node for the first time,
the option “Create a new ESIS Repository” is pre-selected and all the
other options are grayed out
• Click Next
16 5/8/2017
8
Experion ESIS Setup
• Select the destination folder for ESIS Repository
• The destination folder can be

– USB Removable Drives
– Portable USB Hard Drives
– Local System Drives
• If “Local System Drives” is selected, a message to share the destination

folder appears
17 5/8/2017
Experion ESIS Setup

• Select OK to share the destination folder
• Enter the Share Name and assign the permission
18 5/8/2017
9
Experion ESIS Setup
• It is recommended to give “read” permissions to the share
• Permissions to the ESIS share must be given to a single user account
• Share access permissions must not be given to “Everyone” or Groups
• User account to which share access is provided must not be present on

the System on which installation is performed
• Ensure that HPSInstall account is not present on the ESIS Server
19 5/8/2017
Experion ESIS Setup
• Mandatory Medias are Pre Selected
• Other media can be selected as part of share creation by selecting the

check box
• Selecting “Start” will copy the selected media to destination

– Sufficient space must be available on destination
20 5/8/2017
10
Experion ESIS Setup
• Successful setup will display the following message

• Click “Finish”
21 5/8/2017
Experion ESIS Setup

• User can perform additional operations mentioned below
– Upgrade existing ESIS Repository
• Available for Successful Shares
– Resume a Failed ESIS Repository Creation
• Available for Unsuccessful Shares
– Remove Existing ESIS Repository
• Available for All Shares
• To perform the above operations, go to C:\Program Files

(x86)\Honeywell\Experion PKS\Utilities\ESIS and double click on
ESISPrepUtil
• A Welcome Dialog Box appears

where all the options are available
for user selection
22 5/8/2017
11
Plan the Migration Copyright © 2017 Honeywell International Inc. Migration Considerations
23 5/8/2017
• There are several features introduced in R500 that should be taken into
consideration when planning a migration
– If the System being migrated is using any of these features or contains
certain configurations, then it is necessary to evaluate the effect that it could
have on your System and take precautions to backup data files and follow
any workarounds listed in the EMUG
• Examples of Features that need to be considered

– Time Synchronization during Migration
• NTP Server/s
• BOOTP
– Ethernet Network and Migration
• Using Fault Tolerant Ethernet Bridges
• Control Firewall Upgrade
24 5/8/2017
12
• Expression used in Control Strategies
– Date and Time Constants
– OPC Type Casting in ACE
– Comma as a list Operator
– Short and Long Names in Control Builder
– Two Dimension Arrays
• Custom Displays and HMI Web Displays
• Custom .stn Files are Not Migrated
• Display Path for Upgraded Stations
• Migrating Multiple Clusters
– Standalone and Single EMDB Cluster
– Multiple EMDB Cluster
25 5/8/2017
• OPC Integrator ---------Caution----------
– OPC Integrator Groups are Disabled on Server B during OPM; this is to
avoid Data Transfer in Dual Primary Mode
– These Groups must be Manually Enabled when Migrating Server A
• Local Windows Groups and Local User Accounts ---------Caution----------
– All Custom Local User Groups, Custom Local User Accounts, and any User
Defined Security Policies (such as access control lists on files and
directories) are not saved during and Experion Migration
• Enterprise Model – Shared Alarm Groups
• Experion Backup and Restore (EBR)
• Localized Experion PKS
• Rebuilding of Checkpoint Files during Migration
26 5/8/2017
13
Migration Considerations – Common Security Model
• Experion PKS R5xx Security has evolved to meet Windows and
Experion security requirements
• Similar to Security in Experion R3xx and TPS 4xx
• Differences Originate from:

– Windows 10 and Windows Server 2016 Security Changes
– Closer adherence to Windows Logo Requirements
– Support for Industry Standards – ISA99
– Simplification of the Security Model
– Incremental Improvements in Experion Security
– Better integration of Experion Operator and Windows Security Models
27 5/8/2017

• Specific set of privileges, permissions, and policies can be assigned on
a user-by-user basis
• Roles are used to define Sets of Users that have common
responsibilities and thus common security needs
• Experion PKS R400, the roles are implemented using Windows Groups
• In Experion PKS R4xx, Product Administrator Group replaces the
Honeywell Administrator Group
• Roles that carry forward from R3xx:
– Operator
– Engineer - Ack View-Only user
– Supervisor - View-Only user
• Roles discontinued from prior releases:
– Continuous Control - Program
– Intimate User - Point Builder
– ER Admin
28 5/8/2017
14
• Role Description is used to define the set of operations a user is allowed to
perform
• All operations within Experion are enabled by role
• Roles are evolving to be discrete rather than hierarchical
Role Description
Windows Administrator Configure and maintain the Operating System and network: software installation, network settings,
account creation and maintenance
Product Administrator Administers Honeywell Experion software: SQL administration, HCI and other component
configuration
Engineer Engineering functions: display creation and deployment, CAB block development, point definition
Supervisor Privileged operational activities

Operator Normal operational activities
Ack View‐Only user View privilege plus acknowledge alarms
View‐Only user View privilege

User No Experion privilege
Server/Service Non‐interactive accounts that may be used for the identity of services that do not fit with
Microsoft’s built‐in accounts and servers/COM servers that need an identity to RunAs
29 5/8/2017

• Roles and security levels associated to Windows and Experion
application set by default in R4xx, are shown in the table below.
Role Operator Security Windows Local Groups Windows Global

(Domain) Groups
System Administrator Administrators Domain Admins
Product Administrator MNGR Product Administrators DCS Administrators

Engineer ENGR Local Engineers Engineers
Supervisor SUPV Local Supervisors Supervisors
Operator OPER Local Operators Operators
Ack View-Only User ACK ONLY Local ACK View Only Ack View Only Users
Users
View-Only User VIEW ONLY Local View Only Users View Only Users
User Users Domain Users
Server/Service Local Servers Domain Servers
30 5/8/2017
15
• Security model:-
– Built-in Administrator disabled by
Operator
default Role Security
– Local Group “Honeywell Levels
Administrators” is now “Product
Product Administrator MNGR
Administrators”
– Windows Local Account MNGR is Engineer ENGR
reserved for servers – not allowed to Supervisor SUPV
be interactive
– Several accounts are no longer Operator OPER
created by Experion Ack View Only ACK ONLY
– Better separation of roles View Only VIEW ONLY
– Local lockdown procedure has been
removed
– Roles are pre-populated in Experion
operator database
• On clean installs only
31 5/8/2017

• Local Windows Account mngr is a Non-interactive account reserved for
server
– Local Windows Account "mngr" is a member of "Local Servers" and "Local
Engineers," this must not be changed.
– If Local Windows Account MNGR is used as an Interactive User on R3xx
Nodes; this is not allowed on R4xx, so the site must create and maintain an
alternate account and assign it to the appropriate local group or groups
• Roles Assignment
– Carefully assign roles to users in order to perform the functions required
– Role Privilege is assigned via Local Group Membership for Local and
Domain Accounts, and Global Group Membership for Domain Accounts
• Several accounts are no longer created by Experion
– Experion now only creates the accounts it requires to run
• TPSComServer Domain Account: instead use DCSComServer
• TPSApp Domain Account: if needed, creates Site-specific Account
• TPSLocalServer local account: use LocalComServer on R4xx Nodes
• GUS Local Account: this account was discontinued in R310
32 5/8/2017
16
Domain Controller Considerations
• Domain Controller used in Experion system:-
– Operates as an independent node with either Microsoft Windows Server
2003 (32-bit), Microsoft Windows Server 2008 Standard or, Microsoft
Windows Server 2008 R2, or, Microsoft Windows Server operating system
installed
– If you are using Microsoft Windows Server 2003 (32-bit) currently as the
domain controller’s operating system, and do not upgrade the operating
system, you must install the R500.1 Experion High Security Policy on the
domain controller before you start migration
– Existing established security/distribution groups remain and new groups can
be added.
33 5/8/2017
• Review Hardware Requirements
– Migrating an existing Experion System to New System Software may require
that the hardware platform (Computer System) which supports software
operation to be upgraded
– Hardware Platforms may be configured as an Experion Servers, Flex
Stations, Consoles, ACE or SIM-C200 nodes, or other client nodes
– A New Computer System may be needed to meet the performance
requirements for Experion Software Operation
– Typical Upgrades may include adding memory cards, installing additional
disk drives, and upgrading to newer interface cards
• If Hardware Upgrades are necessary, identify which components need

to be upgraded or replaced
34 5/8/2017
17
Hardware Platforms - Server
R43x R500 T‐Nodes LCNP4e LCNP4e2
Dell Platforms
Dell T610
Dell R710XL
Dell T310 Server non RAID
Dell T310 Server RAID5
HP DL380 Rack Server PowerEdge T330
Dell R320 Server
Dell T320 Server
Dell T130 / Dell R330 Servers
Dell T330 Servers
Dell R430 Server
HP Platforms
HP DL360p Rack Server PowerEdge T130
Dell R320
This information is available
in the Experion Update matrix
35 5/8/2017
Hardware Platforms - Workstations

R43x R500 T-Nodes LCNP4e LCNP4e2
Dell Platforms
Dell WS490
Dell T3400
Dell T5400 RAID1 or non RAID
Dell T5500 RAID1 or non RAID
Dell T3500
Dell Optiplex 3020
Dell R5500XL RAID1 or non
Dell Optiplex 3010
Dell T3600XL RAID1 Quad Core
Dell Optiplex 3020
Dell R7610
Dell R7910XL
Dell T5810XL
Dell Optiplex XE2 HP Z440
HP Platforms
HP Z620 RAID1 Quad Core
HP Z440
This information is available

in the Experion Update matrix
Dell Optiplex XE2
36 5/8/2017
18
• TPS Nodes
– TPS components will continue to be On-process during the migration of
Experion System components and ES-Ts will continue to have view and
control capabilities to the TPS System during the Migration Process
• Migrating DSA-connected Experion/TPN Systems

– The ESVTs and ESTs in Experion Clusters that are connected to TPN can
be migrated without affecting the operation of the TPN
– The version of TPN required for the Integrated Experion-TPS Nodes in
R500.x has not changed since R210, so there is no requirement to upgrade
it
37 5/8/2017
• Multi-cluster Migration Scenarios
– For R400.x (R400.1, R400.2, and R400.3), R410.x (R410.1 and R410.2),
R430.1 ,R431.x,R432.1 and R500.x systems, you can migrate the servers in
any order
– If you are migrating from R400.x to R500, you must ensure both EMDB and
non-EMDB servers are migrated to R500 before using Upgrade Tool
38 5/8/2017
19
Multi-cluster Migration from R400.x,R410.x,R430.x,R431.x and R432.x
39 5/8/2017
Cluster X and Y on Target EMDB location EMDB Notes
Base Release Release Interoperability
for between clusters
Cluster on different
s X and releases
Y
R400.x, R500.1 EAS non- YES Migration order is not restricted
R410.x ,R430. Redundant
Experion Server
x, and R431.x
(EMDB Sever)
(Two clusters
sharing a EAS Cluster X YES Migration order is not restricted
or non redundant Cluster Y YES Migration order is not restricted
Experion Server
(EMDB Sever))
R400.x, R500.1 Cluster X No Because there are two EMs
R410.x ,R430. And Cluster Y existing in two systems, shared
x, and R431.x assets can be created to exist in
(Two clusters each EM.
with each
hosting an
EMDB.)
40 5/8/2017
20
Considerations for Multi-cluster Migrations
• The following important considerations must be reviewed to determine if
any apply to your System in a Migration Scenario:-
– Table on the previous slide describes Migration Scenarios for Two Clusters.
The same scenarios are valid for All Clusters within a System
– In All Migration Scenarios, DSA and OPC Data Interoperability is available
throughout the Migration Process except for the node that is currently being
updated
– Do not make any engineering changes until all clusters within a system have
been migrated
– Do not make any engineering changes until all systems have been migrated
– Do not download or upload EMDB Data when either the EMDB Hosting,
EPKS Server, or the Target EPKS Server is in Dual Primary State
– Minimize the amount of time that clusters running on different releases
– All nodes within the FTE communities used by any of the migrating clusters
must be updated to the latest version of Common Components before
starting a migration
– All FTE system preferences and FTE driver configurations must be the same
for all clusters in the FTE community
41 5/8/2017
Considerations for Multi-cluster Migrations (cont.)

– The BOOTP server must be running on the latest release server of the
cluster. You must run the BOOTP checker before migrating or rebooting any
controllers
– Interoperability is supported only between clusters (servers) operating on
two different releases and only between releases in which migration is
supported. Interoperability between clusters (servers) operating on more
than two different releases is not supported
Server 1
R500
Server 2 Server 3
R431 R301
42 5/8/2017
21
Additional Migration Considerations
• Interoperability Restrictions
– During migration while servers are in Dual Primary State
• Configuration changes are restricted to ensure system integrity
• Server and its associated client must be at the same release and update
level in order to connect
• No engineering changes must be made to a cluster until all nodes within
that cluster have been migrated to the same release and update level
• Alarms and Point Data are typically accessible via DSA between clusters
of different releases and update levels both during and after migration
– After Migration
• In some cases, configurations from previous releases must be updated
to the latest version before changes can be made. For example after
migration, user defined custom display and shape files need to be
updated to the current release so that they can be used in Station
• Engineering tasks may be different at previous and current release
43 5/8/2017
OPM Prechecks and Considerations

• Additional Considerations:
– Check SCADA Scan Statistics for overloads or lost requests
– Check and record cache settings for TPNServer, cda, gda
– Verify license for destination release has same options as source
– Verify that all ISR’s are included in destination release
– Check Server Logging Rate – cleanup errors
– Verify EMSEvents Subsystem is working – check database size
– Check Alarms on both Flex and Console Station – logged in as mngr
– Check Server Scripting Status and Script Event Rate
– Check SES and SPS Status
– Log Display Callup Performance
– Check for Raid or multiple drives in PC. See R200.1 Experion System
Initialization Media for details.
44 5/8/2017
22
More OPM Prechecks and Considerations
– FTE Status Check – copy fteNodeList.log from Source System
• For R31x Nodes
– Create and Historize System Sinewave Point in fast history
– Check Windows Event activity and fix any problems
– Ensure WinZip is on both servers
– Run a Manual File Replication – correct any errors
– Check DSA Connections – record and reset statistics
– Check CDA and FTE Statistics on Controllers – record and reset
– Check for Cisco Switch Configuration Changes
– Check for compatible versions of Honeywell Solution Pack
– Consolidate into one Quickbuilder File
– RDM Considerations
– Verify that applications are supported on new release
• Including Total Plant Batch and PHD
– Verify availability of Latest Patches
45 5/8/2017
46
23

Check the System for Migration Readiness Copyright © 2017 Honeywell International Inc. Perform Pre-Migration Checks
1 5/8/2017
Pre-Migration Checks
• Make sure that all CD/DVD drives installed in Experion Station
computers are in working order and accessible
– Some older Flex Stations may not contain DVD drives and may not provide
support for migration. Use External DVD drive, if necessary
• Ensure that all Communications Networks are intact
• Verify that system hardware is supported on the target release
• Perform pre-migration tasks for localized systems or nodes
– Perform the pre-migration tasks procedure on each node that has
localization applied
2 5/8/2017
1
Pre-Migration Readiness Server Checks
• Download latest copy of the Migration Readiness Tool (MRT) from
Honeywell On-Line Support (OLS) website
https://www.honeywellprocess.com/library/support/software-
downloads/Experion/mrt-datafiles.zip
• Only registered user can access and download MRT files from OLS
website
– Login into the Online Support website and navigate to desired location
• Shown in following slides
– Download the “MRT Data Files.zip”
– Extract them to a temp folder on Server A and Server B
– Double click on the file “copy_mrt_datafiles.bat”
– MRT files must be copied on both servers
MRT is not required to be run if
the base release is R400.x or
above. Readiness checks will be
performed using Upgrade Tool
3 5/8/2017
Honeywell Process Solution – Login and Support
• MRT Data Files access:

– Logon to
www.HoneywellProcess.com
– Click the SUPPORT link
– Click on Latest Downloads
– Type MRT in the search text
field
– Click the Search button
– Result:
• Latest MRT files are listed
4 5/8/2017
2
Honeywell Process Solution – Navigation (Experion Update Matrix)
5 5/8/2017
Honeywell Process Solution – Experion Update Matrix
6 5/8/2017
3
Pre-Migration Checks – Tools Used
• Controller Database Inconsistency Checker

– Used to fix problems between Control Builder database and image loaded to
the controller
– Run from Control Builder anytime – regardless of OPM License exists or not
• ERDB checker (check-erdb.sql.zip)
– Release independent
– Only does SQL Checks of ERDB database
– Does not fix or change anything
– Repair Scripts available for selected errors
– Must load latest SQL files from www.HoneywellProcess.com
• Migration Readiness Tool (MRT)
– Provides Server and Controller checks
– Compares ERDB to controller
– Does not fix or change anything
• ERDB Migration
– Occurs automatically when you Migrate your server
7 5/8/2017
Pre-Migration Checks – Tools Used (cont.)

• RTools
– RTOOLS assists the Migration COE team to gather files from your system
8 5/8/2017
4
Migration Readiness Tool Background
• Provides pre-checks for On and Off Process Migration
– Server Migration Readiness
– Controller Migration Readiness
• Used to prepare and plan for an OPM
– Should not be run for the first time during an OPM!
• MRT data files supplied on On-line Support website
– Provides information about supported migration paths
– Forward migration path information isn’t available when a new release is shipped
– MRT Data Files are cumulative, so latest version can be used for any Release
– Not required when migrating from R400.x or above to target release
• When Should It Be Run?
• When planning to do a Migration
– Before a Server Migration
– Before a Controller Migration
• About the Checks:
– MRT examines system status
– MRT will not modify system components
– Run only one instance of MRT at a time
– MRT will NOT verify version of the mr_readinessInfo file that you use
• Ensure running the latest version – see On-Line Support website
9 5/8/2017
How to Run MRT

• Run on a Server Node
– Select Configuration Studio and connect to Server
– Expand the Server and select On Process Migration, and then click on
Migration Readiness Tool
• From Readiness Check menu select Server migration or Controller
Migration option
• If Server Migration is selected, a dialog appears with
– Server Name
– Current system release
– Network topology (Cnet, Ethernet, FTE)
– Drop down to Select Target Release
– Generate Report button
• Enabled only when the user selects the target release
10 5/8/2017
5
Launch Migration Readiness Tool (MRT)
• Launch Configuration Studio and select On Process Migration
Click on Migration
Readiness Tool
11 5/8/2017
Server Readiness

the base release is R400.x or
above. Readiness checks will be
Use Readiness Check performed using the Upgrade Tool
menu to select
• “Server Migration”
12 5/8/2017
6
Server Migration Readiness
• Select Target
Release
– Download MRT
data files from
OLS
13 5/8/2017
Server Check Summary

• Once Target is selected, Checks are listed
• Select ‘Generate Report’ to perform Check Click to Run

Checks
14 5/8/2017
7
Generate Report (for Server)
Color Coded Status
15 5/8/2017
Server Checks
• Are Servers Synchronized?
– Check only applies to Redundant Servers
– OPM will be prevented if Servers are not Synchronized
• Is ‘A’ Primary and ‘B’ Secondary Server?
– Check only applies to Redundant Servers
– OPM cannot be Started if Server A is not Primary
• Are there Active Locks?
– All ERDB Locks must be cleared before migration starts
– Server Migration will be prevented if Locks are not cleared
– NOTE: MRT does not Check EMDB Locks. It is recommended that it be
verified that EMDB Locks are cleared
• Are there Checked Out Elements?
– This will list all Elements Checked Out from QVCS
– For information only
16 5/8/2017
8
Server Checks
• Is OPM License Enabled?
– OPM will not be allowed if there is no OPM License
• Is HART Multiplexer service running?
– If the HART Multiplexer is not stopped, the FDM tool won’t work properly
after the EPKS Servers are upgraded
• Is ERDB Language other than English?
– This check is performed to warn the user that ERDB Language will be
changed to English if the servers are On Process Migrated
• Equality of password on ServerA and ServerB
– This refers to the local windows mngr account
– Check this manually
• Is the Primary and Secondary Servers Time Synchronized?
– Compares the date and time of Primary and Secondary Servers and reports
the difference
• Is NTP server(s) Configured?
– Verifies that the Experion Servers have at least one NTP Server configured.
Migration may fail to complete if no NTP Servers are configured
17 5/8/2017
Server Checks – (cont.)

• Use Windows Services & DCOM Servers Log-on Tool on Experion
Servers with all Releases
• Available in Start > All Programs > Honeywell Experion PKS > System
Management > Windows Services & DCOM Servers Log-on Tool
Incorrect
Password
Correct Password
18 5/8/2017
9
MRT Run on Server A - Primary
19 5/8/2017
MRT Run on Server B - Backup
20 5/8/2017
10
MRT Report Output – HTML Format
• Report can be saved in CSV or HTML Format
Report in
HTML Format
21 5/8/2017
Upgrade Tool - Functions

• General Data Collection
– Following type of information is collected from all nodes in Experion PKS
Server cluster
• General Information
– Windows OS, Dell Version, Node Name, Node Type etc
• System Configuration Information
– Installed Honeywell Software Packages and Versions
• Experion Server System Information
– Specific information regarding each subsystem (Server, Console
Station, Flex Station)
– Application Specific Log Files
• Readiness Checks
– Pre-requisite checks like Interoperability, Consistency, Stability,
Synchronization checks are performed
– Provides short description of workarounds and Repair scripts for failed
readiness check
• Diagnostic Data Capture
– User can select to Capture Server Log, Error Log etc
– By default, Diagnostic Data for Nodes and Components is collected
22 5/8/2017
11
Upgrade Tool – Functions – (cont.)
• Upgrade Instructions
– Migration steps for each node and component is generated based on the
data collected and results of readiness checks
• Customize Instructions
– Details of the upgrade instruction can be customized based on the answers
given by the user to specific questions asked by Upgrade Tool
• Process Summary
– Reports can be generated for each task in Upgrade Tool
– These reports are used to analyze and improve the migration process
• Post Upgrade Analysis
– Provides Post Upgrade data and summary reports
• These reports can be used to study the overall migration process
carried out on the site
• Upgrade Tool information can be saved in a Upgrade Tool Project File
(. utp)
23 5/8/2017
Upgrade Tool - Limitation

• Cannot Communicate with the Nodes across Windows Firewall
• Does not Differentiate between Migration, Updation and Patching
• Cannot acquire the installation information of applications that do not
follow the standard Experion Installation
• Does not automatically detect the L1 Modules connected to Experion
System using a Gateway Module
– Example the PMIO Modules connected through IOLINK Interface Module
• Cannot Perform Conversion Related Readiness Checks.
– Example, Upgrade tool cannot provide readiness status for a CNI to FTE
network conversion or a SCADA to process system conversion
24 5/8/2017
12
Upgrade Tool - Dependencies
EMDB: Configuration Studio

Configuration To fetch the list of Experion
clusters Information Service:
Studio: To fetch the list of EMDB
To launch the Upgrade and nodes in the cluster
systems having host
Tool server configured
EPKS Installation:
To get information of
Upgrade ERDB:
installation carried out during
To fetch information about
migration. This information is Tool
configured L1 modules
used while doing post
upgrade analysis
Single Version
Wizard:
To get information of firmware
Information File/WMI:
upgrade carried out during Component Upgrade To fetch information about
installed components and
migration. This information is Guide:
used while doing post upgrade their patches
Used while creating
analysis upgrade instructions.
25 5/8/2017
Upgrade Tool - Launch

• Upgrade Tool can be run only from
– Experion Server B Node in case of Redundant Experion Server
– Experion Server Node in case of Standalone Experion Server
• Only one instance of Upgrade Tool can be run at a time in a cluster
• To use the Upgrade Tool, a user must be the member of Local

Engineers or Product Administrators Group
• Install Component User Guides media before running Upgrade Tool
26 5/8/2017
13
Launch Upgrade Tool
• Open Configuration Studio on the Server corresponding to the Experion
Server Cluster to be migrated
Used for Readiness

Checks, Diagnostic
Data, and Upgrade
Instruction
Used for Upgrade

Instruction only
27 5/8/2017
General Information
• Enter the Required Details
Enter a Share
folder name
28 5/8/2017
14
General Data
• Collects General Information for
– Computer Nodes
• Operating System, hardware platform, disk drives, Experion Release and software
components, etc.
– L1 Modules – C200, C300, CF9, FIM, PGM, WDM
• Device Index, Application Version and Boot Version, MAC Address etc.
If Enable Throttling Option (File Menu) is

selected, the Readiness Checks screen
shows status as Pending. The status is
Click to Add Pending because either the physical
Computers not memory utilization is more than 75% or CPU
memory utilization is more than 60%.
in the list
29 5/8/2017
Readiness Checks
• Performs Checks similar to MRT for Servers and Controllers
Select to
Run checks
for single
node
“27_28”- Device
Index
Select to Run
checks for all
30 5/8/2017
15
Result - Servers
Details of checks covered

earlier in this presentation
Click to see
details
31 5/8/2017
Result - Controllers
Details of Checks covered

later in this presentation
• Status Legends are shown below
32 5/8/2017
16
Readiness Check - Generate Report
• From the Summary Tab, select the Node for which the report is to be
generated and Click on Generate Report
• Report can be saved or printed
33 5/8/2017
Report Details
• To view the Details, click on the Details option
• Error should be corrected before migration
34 5/8/2017
17
Diagnostic Data Capture
• Includes Application Logs, Error Logs, and other logs useful for analyzing nodes
health
• Logs are copied to Diagnostic Data Storage path provided at the General
Information page
– Only applicable logs are collected
• Reports can be generated similar to Readiness Checks
Node A
Node B
Differs from
Node to Node
35 5/8/2017
Process Summary
• Displays results of all Nodes for following status
– Data Collection
– Readiness Checks
– Diagnostic Data Capture
36 5/8/2017
18
Customize Instruction
• Shows list of Nodes with Current and Target Release
37 5/8/2017
Upgrade Instruction
• Contains set of instructions for upgrading an Experion Cluster
– Generated for a specific site depending on the configuration of that site
• Provides instructions only for the Nodes/Modules that successfully
complete the Readiness Checks
38 5/8/2017
19
Upgrade Instruction (cont.)
Add Custom
Instruction
Browse and Attach

Documents
Add Alternative
Document
39 5/8/2017
Upgrade Tool – Auto Proceed

• All steps are performed Automatically
– Reports and Upgrade Instruction saved at C:\ProgramData\Honeywell\Experion PKS\Upgrade
Tool\Data
40 5/8/2017
20
Controller Readiness - MRT

the base release is R400.x.
Readiness checks will be
Use Readiness Check performed using the Upgrade Tool
Menu to select
“Controller Migration”
41 5/8/2017
Controller Migration Readiness

• Supported for
– Migration to New Release
– Migration to a Patch or Update
• Select Module
– Cx00, FIM, IOLIM, ACE, Simulation Environment (SIM-Cx00, SIM-ACE),
EHG
– Checks are performed against all modules found in the chassis
• Select Target Release
– Release Option tests Migration to a New Release,
Or
– Service Pack Option Tests Migration to a patch/update
– Download MRT Data Files from www.HoneywellProcess.com
42 5/8/2017
21
Controller Check Summary
• Checks are listed, Select ‘Generate Report’ to perform Check
43 5/8/2017
Generate Report (for Controller)
Color
Coded
Status
Links to
Details
44 5/8/2017
22
MRT Report Output – Controller Readiness
45 5/8/2017
Controller Checks
• Are the RM’s Synchronized?
– Check performed on Redundant controllers
– To correct:
• Restart the backup chassis
– OPM will halt if this is not corrected!
• Is Auto Synchronization state set to conditional?
– To correct:
• Set “Auto Synchronization state” of the RM to “Conditional” from the
Module Properties dialog of the RM.
– OPM will be prevented if this is not corrected!
• Are the Controllers Synchronized?
– Performed only on redundant C300 controllers
– Checks if both Primary and Secondary controllers are synchronized
• Is there enough free CPU and Memory available in controller?
– Checks for 20% of free CPU memory
– Could cause OPM to halt
46 5/8/2017
23
Controller Checks (cont.)
• Is Base Execution Period not set to "Default"?
– Performed only if a CPM or LIOM module is present.
– Verifies that the CEE “Base Execution Period” is not set to the default value
• Is OPM License enabled?
– OPM will not be allowed if there is no OPM License
• Are there any Legacy CNI modules?
– Detects unsupported CNI such as TC-CCN012 or TC-CCR012
• Identifies the slot and MAC ID of the CNI
– To correct:
• Replace CNI with TC-CCN013 or TC-CCR013 before starting OPM
• Are there more than one CPM in a chassis?
– Checks if there are more than one controller present in a chassis
– To correct:
• Move extra CPM to another chassis
– OPM will be prevented if this is not corrected!
47 5/8/2017

• Dangling Peer and Control Connections
– Connection exists, but ‘other’ end is not found
– Lists the strategy and parameter that ‘owns’ the connection
– To correct:
• Delete the tag with the dangling connection from monitor
Or
• Delete the dangling connection from project and reload tag
Or
• Load the ‘other’ end of the connection
• Unsupported Modules/Firmware
– Checks for Module Chassis and Remote Chassis
– Identifies modules and firmware that are not listed in ver_rev.text file
– To correct:
• Replace module or firmware revision
48 5/8/2017
24
• Are there any Unidentified/ Incompatible Firmware?
– Performed only for the FIM Controller
– Detects any unidentified/incompatible firmware version installed in FIM
controller
• Modules and firmware versions not listed in the ver_rev.txt file
– Unidentified modules must be replaced with module types that are supported
• Must be loaded with a supported firmware version
• Are there any unsupported Modules/Firmware on Remote Chassis?
– Performed for all the remote chassis associated with the selected controller
chassis
– Detects the presence of any unsupported modules and firmware versions
installed in all non-redundant remote chassis associated with the controller
chassis
• Are there any Malfunctioning Peer References?
– Verifies that all Peer References in the CPM are performing properly
– Indicate a configuration mismatch between the ERDB and the controller
49 5/8/2017

• Are there any Peer References to Secondary Blocks?
– Checks for any peer references to secondary chassis modules
• Must be removed to perform an on-process migration
• Unassigned Modules
– List IOMs that are loaded to monitoring and not being used
– Warning – For Information
• Unconnected Pins
– Lists pins that are exposed, but have no connection
– Warning – For Information
• Are there Active Locks?
– All ERDB Locks must be cleared for tags assigned to the selected module
(controller, IOLIM, FIM)
– Controller Migration will be prevented if Locks are not cleared
• Is HART Multiplexer Service Running?
– Detects whether HART Multiplexer Service is running on the Server/s.
– Must be stopped on the associated servers before beginning a migration.
50 5/8/2017
25
Controller Checks - Ghosts/Inconsistent Modules
• Checks are not performed on FIM, IOLIM, EHG
• Ghost Modules
– Tags that exist in the controller but not in the ERDB
• MRT may not be able to identify name of tag
– To Correct
• Use ‘Identify ERDB Controller Inconsistencies’ feature in CB
• Inconsistent Modules
– Basic Blocks and Connections that exist in the controller but not in the ERDB
– Tags where ERDB and controller are different
– To Correct
• Load Module from monitor (to force ERDB and controller to be
consistent)
51 5/8/2017
Ghosts/Inconsistent Modules
• Controller Migration Wizard will not allow OPM if these inconsistencies
are not resolved!
• This Check is available in Control Builder
– Identify ERDB Controller Inconsistencies
52 5/8/2017
26
Identify ERDB Controller Inconsistencies
• Performs Ghosts/Inconsistent Module Check in CB
• Supports ability to delete Ghost Modules
• Access from Menu when Controller is selected
53 5/8/2017
Display Ghost Modules and Inconsistencies
54 5/8/2017
27
Delete a Ghost Module
• Select the modules and press Delete
55 5/8/2017
Second Confirmation for Active Ghost

• Second Confirmation is asked before deleting the Ghost Module.
• Click Yes to Confirm
56 5/8/2017
28
Run the Check Again
• Rerun the Check once all the modules are deleted
57 5/8/2017
ERDB Checker Background

• Created By DE to help analyze customer issues
• Extended to add Checks for OPM
– Made available to be run by customers
• It has evolved into:
– Release Independent Mechanism to find possible anomalies in customer
ERDB
• Is updated often
• www.HoneywellProcess.com should be checked for new version before
running
• Will help DE to fix problems
– Output is sometimes crude and contains false positives
• Not intended for customer view!!
• Should be analyzed by TAC and/or DE
58 5/8/2017
29
On-Line Support Website – ERDB Checker
• The latest version of ERDB checker is available on Honeywell On-Line
Support (OLS) website
– https://www.honeywellprocess.com/library/support/software-
downloads/Experion/check-erdb.sql.zip
• Only registered user can access and download the ECC tool from OLS
website
– Login into the Online Support website
– Download the “check-erdb.sql.zip” file
– Extract to the server that consists the active ERDB; typically Server A on
non-redundant server, Server B on a redundant server pair
– Install the Honeywell_ECC_Installer package
59 5/8/2017
When Should It Be Run?

• Before a Server Migration
• After a Server Migration
• Before Controller Migration
• After Significant Configuration Changes
– During Project Configuration, daily
• Periodically as a part of a Preventive Maintenance routine.
60 5/8/2017
30
About the Checks
• All Checks should be evaluated before proceeding with an OPM
• Checks warn of possible issues that could occur during OPM
– Many Checks identify issues that will be resolved by a patch or update
– Sometimes Checks require GTAC investigation
– In some cases, a check corresponds to documented notifications, such as
presence of Custom CCLs
• ERDB Consistency Checks often Identify Anomalies that we don’t:
– Know how to reproduce
– Have a fix for
61 5/8/2017
What to Do with the Checker Output

• Follow instructions in checker output:
– Attempt to correct/analyze the problem
• Re-run the checker to verify issue has been corrected
• If workaround doesn’t clear issue, follow steps below
• “No workaround specified, Please contact DE.”
– Projects, contact TAC
– TAC, contact DE
– Send the following information:
• Checker Output
• ERDB Backup
• Information about what configuration steps were performed leading up
to issue
62 5/8/2017
31
Some General Information
• When Root.Name appears, assume ‘Name’
– This query assumes tag.bb
• . .Name assume User Defined Template
63 5/8/2017
How to Run ERDB Consistency Checker?

• Get the latest version from www.HoneywellProcess.com
– Download the file to a non-Experion Directory
• The Check should be run on the Primary ERDB Node
– Server B for Redundant Servers
• Run from the Desktop
– Copy the Honeywell_ECC_Installer.exe in temp folder and install
– Double-Click on ERDB Consistency Checker shortcut created on desktop
– Hit ENTER to run OPM and Database check

64 5/8/2017
32
How Do You Run It?
• The out is stored to c:\temp
– File Name looks like this:
_CheckErdb+03-
004+EXP25ESVTXXB+ps_erdb+B81712A05F59.ChkErdb.html
– Use Internet Explorer to OPEN the file
Scanning in
Progress Scanning
Completed
65 5/8/2017
Format of Output with No Issue Found

• Checks with no issue found:
– Category: OPM SPECIFIC CHECKS
• None of the these checks failed in this category
– Category: ERDB CONSISTENCY CHECKS (FATAL & NON FATAL)
– Category: INVALID CONFIGURATION CHECKS
• Checks with Issue found:
– Header information should include:
• What is the problem?
• If this is a temporary problem, when it’s fixed
• How to work around it?
• For issues that have no workaround:
– No workaround specified, Please contact DE
– Non TAC personnel should contact TAC
• End of the file contains summary information
66 5/8/2017
33
Sample Output with No Issue Found
67 5/8/2017
Sample Output with Issue Found
68 5/8/2017
34
OPM Specific Checks
• Expression Syntax
• Custom CCLs
• RampSoak
• Lost Data
• I/O modules with Incorrect Catalog Number
• Duplicate Names of Loaded Strategies
69 5/8/2017
OPM Specific Checks – Custom CCLs

• Two Checks Identify CCLs:
– List of Installed Custom CCLs
– List of where Custom CCLs are loaded to Controllers
• Identifies
– Custom CCLs and associated releases in the ERDB
– Strategies that use the custom CCLs
• How to Workaround
– If there is a custom CCL for the release the server is running on, no action is required
– If CCLs are missing for the release, new CCLs must be obtained and installed into the
ERDB
• It must be verified that the custom CCLs support OPM
Or
– Strategies that use CCLs must be deleted from monitor
• What happens if these are ignored?
– If CCLs are missing for the release:
• OPM will halt, user will have to use NTools to restore ‘old’ firmware
– If CCL doesn’t support OPM
• Blocks in listed strategies will be cold initialized
70 5/8/2017
35
OPM Specific Checks – Lost Data
• Multiple Checks identify Problem:
– List of Strategies where the STEP block IC.BYPREQ and SC.BYPREQ
Parameter Data will be lost on OPM
– List of Strategies where Parameter Data will be lost on OPM
– List of Strategies that store to Parameter Data that will be lost on OPM
• Occurs during Controller Migration:
– Until the user has migrated to the new firmware version listed
• Caused by Controller OPM Bugs
– Evaluate the impact of the lost data
– If the loss could adversely affect the process, the OPM should be delayed
until the Modules that use the data may be taken off-line.
– Parameter values will be set to default value on OPM
• Release Fixed
– Various – information included in checker output
71 5/8/2017
OPM Specific Checks – I/O with Bad Catalog Number

• Check that identifies Problem:
– List of configured IO Modules which have a wrong Catalog Number in
ERDB
• Caused by Bug in Off Process Beta Configurations only
– Download DeleteInvalidCatalogNumber.bat from OLS and execute
– Controller Migration Wizard will prevent OPM
72 5/8/2017
36
OPM Specific Checks – Duplicate Names
• Check that identifies Problem:
– Duplicate Names of Tagged Loaded Strategies
• Occurs
– When two loaded strategies share the same name
• Caused by
– Bug in CB
– Inactive one of the duplicate CM. This will appear to inactive both the CMs.
– Delete the CM from monitor.
– Inactivate the second duplicate CM and delete from monitor
– Rename one of the duplicate CMs from Project
– Load both CMs
– OPM will halt, user will have to use NTools to restore ‘old’ firmware
• Release Fixed
– No fix available yet
• Run checker prior to load to ensure no duplicates exist
73 5/8/2017
ERDB ‘Consistency’ Checks

• Four Levels of checks
– Category 1 & 2 – Fatal and Non-Fatal
• Many checks identify anomalies that we don’t:
– Know what caused it
– How to fix it
• This discussion will only apply to checks that include workarounds
– Category 7 – Invalid Configuration
– Category 8 – For your information only
• Checks under this category are optional
• Issues identified often won’t affect the outcome of an OPM
– Should be analyzed before OPM starts
74 5/8/2017
37
ERDB ‘Consistency’ Checks – Fatal
• Assigned Blocks sharing same EEC-IOC-DOC
– If possible, please perform the following steps:
• Delete the listed strategies from monitor
• Un-assign and reassign the strategies
• Run Check again
• If strategies no longer appear in list, load from project
• else, contact DE
• System Template of Strategy, not Equal System Template of Base Template
– If all blocks listed are FF Basic Blocks derived from user defined templates, this result
set may be ignored.
– For all other cases, there is no workaround, contact DE
• Duplicate Names
– Duplicate Names of Tagged User Defined Templates or System Templates
– Duplicate Names of Tagged Project Strategies
– Name of Tagged UDT duplicated as Tagged Strategy Name
– Please rename one of the objects listed in each row to eliminate duplicate names
75 5/8/2017
ERDB ‘Consistency’ Checks – Fatal for FF

• Checks only report for FF Configurations
• CMs that contain FF Blocks with unused VCRS:
– Reload the Control Modules to cleanup VCRs
– DO NOT delete any of the CMs listed below from Monitor!!!
• CMs and SCMs that have Major Structure Changes:
– If any of the strategies are to be loaded from Project and contain FieldBus
Blocks:
• Load from Project Tree
• Update to Project
• Load from Project Tree again
76 5/8/2017
38
ERDB ‘Consistency’ Checks – Non-Fatal
• Show Missing Associated Connections:
– If blocks listed are FF Basic Blocks, please contact DE
– All other cases may be ignored
• Show Missing Hidden Connections:
– This result set may list strategies that do not have a problem.
– Monitor strategies (negative value in second column) in rows that do not
have a 'partner' row are likely to have a problem and should be reloaded
in the same load operation as it's 'partner' strategy.
– For listed Project Strategies (positive value in second column), the
connection should be deleted and re-formed.
– Other rows may be ignored. In order to clear this result set, all strategies
listed should be reloaded in the same load operation.
– In the case that the results are not cleared from these procedures, please
contact DE
77 5/8/2017
How to Find Hidden Connection Partners

• Show Missing Hidden Connections:
• This result set may list strategies that do not have a problem.
• Monitor strategies (negative value in second column) in rows

• that do not have a 'partner' row are likely to have a problem
• and should be reloaded in the same load operation as it's
• 'partner' strategy.
• For listed Project strategies, the

• connection should be deleted and re-formed.
• Other rows may be ignored. In order to clear this result set,

• all strategies listed should be reloaded in the same load operation.
• In the case that the results are not cleared from these procedures,
• please contact DE.
• ProjConn connid HiddenConn AssocConn ToParam FromParam

• ----------- ----------- ----------- ----------- ------------------------------------------------------------ ------------------------------------------------------------ -------------- --
• 414115 -2147069533 -2147069532 0 D2502001_D0001.SWITCHA.X[2] F2502003_D0001.SWITCHA.OP[0]
• 254204 -2147229444 -2147229445 0 F2502003_D0001.SWITCHA.BACKCALCIN[0] D2502001_D0001.SWITCHA.BACKCALCOUT[2]
• 9786 -2147473862 -2147473861 0 08FC0120.PIDA.SP[0] 08FC0120_ChrgX.AUTOMANA.OPEU[0]
78 5/8/2017
39
ERDB ‘Consistency’ Checks – Non-Fatal (2)
• Lifecycle Checks
– Lifecycle State in Project Strategy greater than Lifecycle in corresponding
Monitor Strategies:
– Project Strategies with Lifecycle = 2-Loaded but with no corresponding
Monitor strategy:
– Lifecycle State of loaded Block other then 2-Loaded on Project or Monitor:
– These anomalies may be cleared by a reload of the listed strategies
• Duplicate Names of Libraries:
– These anomalies may cause a problem on import or ERDB Migration, or
creation of Custom Blocks.
– When using a release that support Library Rename, the Custom Library
should be renamed to eliminate the duplicate
– In cases that the Library can not be renamed, please contact DE
79 5/8/2017
ERDB ‘Consistency’ Checks – Unfinished Configuration
• Dangling Connections:
– This check identifies cases where the ‘active’ end of the connection has
been loaded, but the other end of the connection has not been loaded.
– This check is FYI only, please do not contact DE
80 5/8/2017
40
Sample Checker Output
• The attached file is a ERDB Checker out file. This is available in

C:\Temp
_CheckErdb+03-003+EXP25ESVTXXB+ps_erdb+6A79A6D3D5BA.ChkErdb.html
81 5/8/2017
Why Are We Talking About This?

• Need to be able to understand when it’s OK to continue when errors are
reported during Controller OPM
• Failure to remedy Severe Errors could result in failed OPM
– Unpredictable Behavior
– Controller Crash
82 5/8/2017
41
How to Identify Severity of Error
• There’s no explicit text in message
• EXPKS_E_IOM NotFound (1L .101.2050)

ZDevCtlLib.EXECSTATE: Warning: IO channel could not locate associated IOM
• EXPKS_E_RangeLimitEr (2L .101.2058)
CM_PosProp0.PULSECOUNTA.POPERIOD: Limit Or Range Exceeded
• EXPKS_E_InvalBlkType (6L .101.2009)
Z161308_HAO081: Invalid Block Type
Severity is the first set For 2xxx errors

of digits (reported by controller)
83 5/8/2017
Severity Levels
• Warning (1L)
– Can be ignored
• Fail (2L)
– Can usually be ignored
– Typically configuration related
– If not usual to load with errors, should evaluate
– Especially if controller/ERDB inconsistencies could exist
• Severe Fail (6L)
– These should never be ignored!
– Should always be corrected before proceeding with OPM
84 5/8/2017
42
How to Workaround
• Errors reported from Controller during Checkpoint Restore Operation
– Last operation where OPM can be backed out
• Cancel the OPM
• Use NTools/CTools to restore firmware to Secondary
– Restore same version as running on Primary
• Use Error Logs to analyze problems and correct
– Probably need to reload modules where problems occur
• Contact TAC/DE if there are questions on how to proceed
85 5/8/2017
Technical Documentation
• Several sources of Technical Documentation which are required for an
OPM
– Solution Support On-Line – Software Revision Checklist
– Software Change Notices for destination release and patches / Updates
– Software Installation and Migration Guide
– On-Process Migration Planning Guide
– Be-Aware Advisories
– Priority Notifications
– TAC
This information is available in

Experion Update Matrix
86 5/8/2017
43
Current Revision of Your Experion System
• Server Software Revision
– Select About from Server /Console Station Control Panel
• See next slide
– Server-related installation logs are all in Setup folder
• C:\Program Files\Honeywell\Experion PKS\Server\Setup\ (For R3xx and
R400.x)
• C:\Program Files (x86)\Honeywell\Experion PKS\Server\Setup (For
R410.x and R430.x)
– Patches and updates listed in software_update_log.txt
• C:\Program Files\Honeywell\Experion PKS\Server\Setup\ (For R3xx and
R400.x)
• C:\Program Files (x86)\Honeywell\Experion PKS\Server\Setup (For
R410.x and R430.x)
– Separate Version for Station and HMIWeb Display Builder
• Select help -> About from within Station or HMIWeb DB
• Client installation files kept in Setup folder – with server setup files
87 5/8/2017
Revision Level Check

• To check the Revision level got to
– For R31x Start Programs Honeywell Experion PKS Server Start-Stop
Experion PKS Server
– For R4xx Start All Programs Honeywell Experion PKS Server Start-Stop
Experion PKS Server
88 5/8/2017
44
Version of Engineering Tools/Controller
• Engineering Tools / Controller Software Revision
– View Product Version.txt file
• In C:\Program Files\Honeywell\Experion PKS (For R3xx and R400.x)
and C:\Program Files (x86)\Honeywell\Experion PKS (For R410.x)
• Alternatively, check revision in Control Builder Help  About
• Patches / Updates to Engineering Tools are registered in Add/Remove
Programs
– Controllers have Firmware and Boot Revisions
• View using NTools
89 5/8/2017
Common Components Revisions

• Common Components include FTE, System Management, Redirection
Manager, Safeview, HCI Runtime, SES, SPS.
• All Common Component installs are logged in Install.log file in
– C:\Program Files\Honeywell
– Can also check Add/Remove Programs
• Patches to Common Components are Not always logged – have to
check specific file versions to determine exact version loaded
• Common Components Software Change Notice is best source of file
revisions for Common Components
90 5/8/2017
45
The Problem with Patches…
• Patches / Updates / Service Packs
• Consider Server/Client, Controller/Engineering Tools, and Common
Components areas separately
• Each DE organization has their own installation methods
• Patches – generally a specific fix ( also ISR’s on the Server )
• Updates – generally a collection of fixes (not necessarily related )
• Service Packs – Larger Collection of Fixes – covering wide area of
product
• Patch / Update ending in C denotes “cumulative”
• A cross-functional team is actively working to revamp and improve the
Patch / Update / Service Pack process
– Reference the Software Revision Sheet on Online Support website
91 5/8/2017
92
46
Review and Correct Any Issues Listed in the
System Event Logs
Check the System for Migration Readiness Review
Copyright © 2017 Honeywell International Inc. and Correct Any Issues Listed in the System Event Logs
93 5/8/2017
System Error Logs

• Review the System Event Viewer and correct any errors that may be
logged in the journals
– Security Log
– Application Log
– System Log
• Errors in these journals could be from communication to controllers,

DCOM, security issues that would prevent communications, .dll errors,
etc
– These errors could prevent the migration from being successful
• Warnings are to be reviewed but may not create errors during the
migration
– It is best to have error free journals
94 5/8/2017
47
Troubleshooting Logs
• Engineering Limitations for those system having Controllers running with
older release firmware on the Migrated Experion Servers.
• Considerations when controllers remain on R400.x (R400.1, R400.2,
and R400.3), R410.x (R410.1 and R410.2), R430.x, R431.x , R432.x
and servers are migrated to R500.x
– Do not use these functional blocks while:
• Configuring new strategies, when the controller is running with Old
firmware
• Modifying existing logics and creating new logics.
• For more information refer guide mentioned below:-
– Controller_Interoperability_Reference_for_Controller_Migration_EPDOC-
X240-en-500
95 5/8/2017
96
48
Topic: Check the System for Migration Readiness
Contents
(E) Instructions for performing labs in virtual environment .................................................................... 3
(E) Install Component User Guide ......................................................................................................... 9
(E)Prepare for Running Upgrade Tool .................................................................................................11
(E) Run Upgrade Tool..........................................................................................................................15
(E) Prepare Premigration Checklist .....................................................................................................19
(E) Perform Premigration Checks........................................................................................................21
5/8/2017 Copyright © 2017 Honeywell International Inc. 1

2 Copyright © 2017 Honeywell International Inc. 5/8/2017

Check the System for Migration Readiness
(E) Instructions for performing labs in virtual environment

In this lab, you will familiarize yourself with virtual environment and also with few Skytap
environment operational procedures.
 Step Action
Node Names in Class
1 The below table shows how the nodes are referenced in labs and their corresponding
equivalence for remote class:
Node Node Name
Experion Server A ESV2501A

Experion Server B ESV2501B
Console Station ESC2501
Domain Controller EXP25DC01

OPC EXP25OPC1
DSA Server ESV25
SCE EXP25CSIM
Console station ESC04
ATTENTION
Only following nodes will be migrated in the labs

followed,
Server B,( ESV2501B)
Console Station, (ESC2501)
Server A,( ESV2501A)
Domain Controller (EXP25DC01)
Special Instructions

 Step Action
ATTENTION
Partition sheet, User guides, and SCN are available on

the shared drive at Z:\

 Step Action
3
ATTENTION
During On-process migration, monitor the process on

the console station ESC04.
After migration of first console station(EC2501), you
can continue to monitor the process from ESC2501
ATTENTION
During On-process migration, monitor the process by

using following custom displays from Station
1.Overview
2.T_100
3.D_100
4. E_100
5. Tankfarm
You can call display individually or launch them from
Toolbar on Station
For Monitoring DSA Communication Status from

Station, use DSA Servers Display from
Configure>System Hardware>Distributed Servers
and observe that DSA status is Ok.
Check the DSA status on Server A/B and Standalone
Server (ESV25)
For Monitoring OPC Communication Status from

Station, use OPC Integrator Display from
Configure>System Hardware> OPC Integrator and
observe that OPC Integrator Group1 Status is Ok.
RDM component is already configured on OPC Node

as a part of Class setup.
For Monitoring RDM component status, on OPC node
launch the OPC explorer from Desktop shortcut, select
RDM Component “Honeywell.Redirect.1” then right
click to connect. The RDM component gets connected.
Open system management display and observe the

RDM component “RDMESVAESVB” appears under
OPC Node.
Select and right click on the component to open the
Auxiliary display to see the communication status of
RDM.

 Step Action
ATTENTION
C200 is in simulation environment so consider

references as SIM-C200E.
TPS references are not applicable for remote
simulation environment.
All SCADA points are simulated by Modbus simulator
Ensure Modbus Simulator is running on EXP25CSIM
node.
Run Mod_RSim from C:\ Modbus\Mod_RSim76exe
Attach ISO to a Skytap machine
4 If lab asks you to insert DVD then for class you need to attach ISO of that particular
media. The procedure to do so is explained below.
5 Select Load ISO Button under the required machine in skytap environment

 Step Action
6 In the load ISO dialogue box Select the ISO image to be loaded. Click Load ISO
Modify BIOS to Boot from System Init media
7 If lab asks you to boot from initialization media, procedure to do so is explained below
8 Restart the machine, On Booting, press F2. the node will display BIOS setup utility.
10 Select the Boot tab.
ATTENTION
Use right arrow button from keyboard to select the

boot tab
11 Using +/- keys make the CD-ROM drive as the first option:
12 Press F10.

 Step Action
13 Select Yes and press Enter.


In this lab, you will install Upgrade Tool Components media on Server B.
 Step Action
Install Upgrade Tool Component Media
ATTENTION

2 Logon on to Server B with domain administrative privileges, in class as Student
ATTENTION
Refer partition sheet for Computer name and IP

address of Server node
Refer partition sheet for Domain Name
3 Refer to the procedure in the following document to Install Upgrade Tool Components
Upgrade tool components media - Software Change Notice (EPDOC-X153-en-500)
Section 5 Installing Experion Upgrade tool components
Sub Section To install Experion PKS Upgrade Tool Components on Experion
(migration)
ATTENTION
Step 2: Mount Experion PKS Upgrade Tool

Components media ISO

 Step Action
Enable XPS Viewer
ATTENTION
XPS Viewer is required to view the Components guide

generated by Upgrade Tool.
On Experion nodes this is done during Installation by
Initialization media. But on non Experion (in class
Domain Controller) ensure that this is enabled. If not,
then perform the steps below.
5 Logon on to Domain Controller with domain administrative privileges, in class as Student
ATTENTION

address of DC node
6 Refer to the procedure in the following document to Components media

Upgrade tool components media - Software Change Notice (EPDOC-X153-en-500)
Section 3.3.1 Enabling XPS Viewer
Sub Section To enable the XPS viewer for Windows Server 2008 R2


In this lab, you will perform steps required before running Upgrade Tool
 Step Action
Verify Server Synchronization
ATTENTION

address of Server node
` 2 Open Station application from following location

Start > All Programs > Honeywell Experion PKS > Server > Station
3 From Menu Bar select View > System Status > Server Redundancy
4 If the servers are not synchronized then, Synchronize the servers
ATTENTION
The station security level must be changed to mngr
Make Server A Primary and Synchronize

 Step Action
5 From the Redundant Server display check the Primary server name
6 If Server B is primary then switchover to Server A by clicking Manual Failover button
ATTENTION
If the Server A is shown as primary, there is no need to

perform Manual Failover
7 The station will disconnect and reconnect to Server A
8 Synchronize the servers again with Server A as primary
ATTENTION
Refer step 3 and 4 (Verify Server Synchronization)
Verify the Experion Server as an NTP server
ATTENTION
Perform this (step 1 to 5) on your Experion Server both A and B to

verify NTP configuration
In Windows Explorer, browse to the folder C:\Program Files (x86)\Honeywell\Experion

PKS\Utilities\NTPSetup
10 Double-click the NTPConfig.exe file. The NTP Configuration dialog box open

 Step Action
11
ATTENTION
BEFORE you click the “Setup Secondary Server”

button, note that NTPCONFG indicates that the NTP
Server (on this node) is currently Inactive. Also note
that NTP Server type and NTP Server Source are Not
Configured. If NTP Server is currently Active then
skip the procedure to run NTPSetup
Click Setup Secondary Server.

 Step Action
12 Verify that the NTP Server Configuration has changed and that the NTP Server is now
active on this node.
TIP
Note the change in NTP Configuration which indicates

NTP Server is currently Active.
NTP Server type is configured as Domain Integrated
Secondary Server while NTP Server Source is
configured as Windows Domain.
Configuring NTP Clients
13
ATTENTION
Perform this step on your Console Station.
In Windows Explorer, browse to the folder

C:\ Program Files (x86)\Honeywell\Experion PKS\Utilities\NTPSetup
14 Double-click the NTPConfig.exe file. The NTP Configuration dialog box open
15 Click Change/Configure Client.
16 Click Exit


In this lab, you will perform steps to run Upgrade Tool
 Step Action
Launch Upgrade Tool
2 Refer to Upgrade_Tool_Users_Guide_EPDOC-X146-en-431A
Section 3.2 Starting Experion PKS Cluster Upgrade
Subsection To start Experion PKS Cluster Upgrade
ATTENTION
Step 2 Refer partition sheet for Server Name

Step 2 Login to Server dialog box does not appear for R4xx
nodes
Step 4 Select Prepare the Cluster for an Upgrade option
Prepare Cluster for an Upgrade

 Step Action
3 Refer procedure in the following document to run Upgrade Tool

Upgrade_Tool_Users_Guide_EPDOC-X146-en-431A
Section 6.6.1 Performing readiness checks, capturing diagnostic data, and
generating upgrade instructions
Subsection To perform readiness checks, capture diagnostic data, and
generate upgrade instructions
ATTENTION
Before Except Configuration studio close all other applications on Server

Step 1 B
Step 4 Select Migrate to Release option. This is the default selection
Step 5 Refer partition sheet and Select Target Release from the drop
down menu.
Step 6 Refer partition sheet for diagnostic data storage path
Step 7 Refer partition and fill Customer Information
Before From File Menu uncheck Enable Throttling option
Step 8
Step 8 Retain Default and click Next. If asked, enter password for Student
account
Step 9 Skip this step
Step 10 Ensure Servers, Console stations, are selected. Click Start
Step11 Skip
& 12
Step 16 Ensure Servers, Console stations are selected for readiness
check.
Step 18 Ensure Diagnostic Data Capture, Readiness Checks,
Customize Instructions, and Upgrade Instructions are selected
in the Select Tasks to perform toolbar.
Step Skip these steps
22, 23
Step 24 Contact your instructor if readiness check fails. Re run the checks
after correcting errors

 Step Action
ATTENTION
Step 26 From the Readiness checks step click Next

Step 27 Select Servers and Console Station from list of nodes.
Retain default diagnostic data checks in Data pane
Step 28 Refer partition sheet and enter password for Student
account if asked
Step 35 Refer partition sheet for location to save the report
After Click Next on Process Summary display.
Step 35
A
B Customize Instructions screen is displayed. Click
Next
C Upgrade Instructions screen is displayed. Save the
User guide on Domain Controller node. Refer partition
sheet for location.
Click NO
For "Do you want collaboration station migration guide
in the final migration document?"
D Close the Upgrade Tool window. Click No when asked
to save information



In this lab, you will prepare the checklist for Servers and Console Station. The items in the checklist
are the pre migration steps you need to perform before starting the migration
 Step Action
1 Refer the Pre migration task section of the guide generated by Upgrade Tool and mark
the tasks applicable to each node type.
Task Server B Server A Cstn
Verify Windows mngr account password

Verify communication status
Verify Network Configuration
Verify the base IP Address

Verify Subnet Mask Settings
Verify the default gateway
Verify Quick Builder project
Perform an upload with contents
Perform an update to project
Run the ERDB Consistency Checker
Verify license key
Record Windows Network Configuration Settings
Acknowledge all Process and System Alarms
Save Checkpoint Manually
Verify and Disable ERDB Replication

 Step Action
2
Verify and Disable EMDB Replication

Disabling File Replication
Save and Disable File Backup
Create shared folder on the EMSN

Check synchronization status
Perform points database check
Activate On-process Migration

In this lab, you will perform pre migration checks listed in previous lab
 Step Action
Verify Windows mngr password
1 Refer procedure in guide generated by Upgrade Tool to verify windows mngr password
Section Verifying the Windows mngr and Administrator account passwords
Subsection To verify the password using Windows Services & DCOM Servers
Log-on Tool
2 Close the Set Log on Account and Password on Servers window
3 Refer procedure in guide generated by Upgrade Tool to verify the communication status
Section Verifying the communication status
Subsection To verify the communication status
4 Refer procedure in guide generated by Upgrade Tool to verify network configuration

Topic Pre-migration tasks
Section Verifying network configuration
Subsection To verify the FTE network adapter connections
And
Subsection To verify link speed settings
Verify Base IP Address

 Step Action
5 Refer procedure in guide generated by Upgrade Tool to verify base IP address

Section Verifying the base IP address
Subsection To verify the address settings
ATTENTION
Step 1 Go to Start > All Programs > Honeywell Experion

PKS > Configuration Studio
Step 2 Configuration studio Login dialog box does not show
up for R4xx nodes
Refer partition sheet for System name and Base IP
Address
6 Refer procedure in guide generated by Upgrade Tool to verify subnet mask setting
Section Verifying/changing Subnet Mask settings
7 If subnet mask in above step is zero then refer procedure in guide generated by Upgrade
Tool to change subnet mask setting. Otherwise skip this step
Section Verifying/changing Subnet Mask settings
Subsection To change the Subnet Mask range
ATTENTION
Refer partition sheet for Subnet mask
Verify Default Gateway Settings

 Step Action
8 Refer procedure in guide generated by Upgrade Tool to verify default gateway setting
Section Verifying the default gateway
ATTENTION
Refer partition sheet for Default Gateway setting.

The default gateway must be either default entry
(0.0.0.0) or the Gateway IP. For this lab do not change
the default entry.
9 Refer procedure in guide generated by Upgrade Tool to verify Quick Builder project
Section Verifying the Quick Builder project
Subsection To verify Quick Builder project
Perform an Upload with Contents
10 Refer procedure in guide generated by Upgrade Tool to perform an upload with contents
Section Performing an upload with contents
Subsection To perform an upload with contents
ATTENTION
Perform the step for SCE_Sim controller.

Step 2: Select “Upload/Update to Project With
Contents” option

 Step Action
11
ATTENTION
Install ECC Tool on Server B by running

Honeywell_ECC_Installer from C:\StudentDB
12 Refer to Upgrade_Tool_Users_Guide_EPDOC-X146-en-431A
Section 5.2 Performing ERDB consistency checks
Subsection To perform ERDB consistency checks
ATTENTION
Step 3 Refer Partition sheet for SR # for this site OPM and
Master SID Number [MSID/ESID/ASSET] fields
Be patient, ERDB consistency checker may take few
minutes to finish. Contact your Instructor if the ERDB
consistency checker reports any error
ATTENTION
The ECC tool will report an error

ERDB_0_Blocks_Types_WithfloatingPt_OPCRef_
Comparision under the OPM Specific Checks
category
Note: Ignore this error and errors under For Your
Information category and proceed with migration
Verify license key
13 Refer procedure in guide generated by Upgrade Tool to verify license key

Section Verifying the license key

 Step Action
14 Refer procedure in guide generated by Upgrade Tool to record windows network

configuration settings
Section Recording Windows network configuration settings
Subsection To record the Windows network configuration settings
ATTENTION
Step 3 Record the network settings. Do not print
Record LCN parameters
15 Refer procedure in guide generated by Upgrade Tool to record LCN parameters

Section Recording LCN parameters
Subsection To record LCN parameters
ATTENTION
Skip this step in Remote class.

Refer to Demonstration Video
Record_LCN_Parameters
16 Refer procedure in guide generated by Upgrade Tool to acknowledge all Process and
System alarms
Section Acknowledging all process and system alarms
Subsection To view the system alarms
ATTENTION
Step 2 For System Alarms select View > System Status

Display
Save checkpoint manually

 Step Action
17 Refer procedure in guide generated by Upgrade Tool to save checkpoint manually

Section Saving checkpoint manually
Subsection To save checkpoint manually
ATTENTION
Step 1 Select any controller first and then perform Step 1

Step 2 Select SCE_Sim (SimC200E)
Step 6 Click OK on the Save Checkpoint message box
Step 7 On Station open the Event summary display from View
> Events > Event Summary and ensure that
Checkpoint save succeeded message exists for all the
controllers you have selected
Verify ERDB Synchronization
18 Refer procedure in guide generated by Upgrade Tool to verify ERDB synchronization

Section Verifying ERDB synchronization
Subsection To verify that the ERDB is synchronized between server A and
Server B
ATTENTION

Step 2 Refer partition sheet for System name
Step 3 Skip this step. Login dialog box does not appear for
R4xx node
Disable ERDB Synchronization

 Step Action
19 Refer procedure in guide generated by Upgrade Tool to disable ERDB synchronization

Section Disabling ERDB replication
Subsection To disable Experion ERDB replication
ATTENTION

R4xx node
Verify EMDB Synchronization
20 Refer procedure in guide generated by Upgrade Tool to verify EMDB synchronization

Section Verifying EMDB synchronization
Subsection To verify that the EMDB is synchronized between Server A and
Server B
ATTENTION

R4xx node
Disable EMDB Synchronization

 Step Action
21 Refer procedure in guide generated by Upgrade Tool to disable EMDB synchronization

Section Disabling EMDB replication
Subsection To disable Experion EMDB replication
ATTENTION

R4xx node
Disable File Replication
22 Refer procedure in guide generated by Upgrade Tool to disable File Replication

Section Disabling file replication before migration
Subsection To disable file replication
ATTENTION
Perform Step 1 to 3 only
Save File backup
23 Refer procedure in guide generated by Upgrade Tool to save File backup

Section Save file backup (flbkup.def)
Subsection To save flbkup.def before migration
ATTENTION
Step 2 Save flbkup.def file to EMSN node. Refer partition

sheet for location
Disable File backup

 Step Action
24 Refer procedure in guide generated by Upgrade Tool to disable File backup

Section Disabling file backup (flbkup.def)
Subsection To disable file backups through flbkup.def before migration
ATTENTION
Step 2 Put an “X” for an entry with “S” but without “*”
25 Refer procedure in guide generated by Upgrade Tool to create shared folder on the
EMSN
Section Creating a shared folder on the EMSN
Subsection Creating a shared folder on the EMSN
ATTENTION
Do not create shared folders in class.

Following shared folders are already created on EMSN
node at E:\
Diagnostic Report
flbkup
Server B
Server A
CStn
26 To check synchronization status perform following steps:

1. Log on to the station running on Server A.
2. Change to the mngr security level.
3. To open the Server Redundancy display, choose View > System Status >
Server Redundancy.
4. Ensure that the backup server (Server B) is running and that the servers are
synchronized.
5. If Server B is not running, start Server B to system running status.
6. If Server B is running and, the servers are not synchronized, click Synchronize.

 Step Action
27 Refer procedure in guide generated by Upgrade Tool to perform points database check
Section Performing a points database check
Subsection To perform a points database check on the server
Activate On Process Migration
28 Refer procedure in guide generated by Upgrade Tool to On Process Migration

Section Activating on-process migration
Subsection To activate on-process migration

Describe the On Process Migration
Procedure for Server B
Migrate Server B Copyright © 2017 Honeywell International Inc.Describe the On Process Migration Procedure for Server B
1 5/8/2017
Warning
• If the node being migrated has multiple hard drives, the secondary
drives have to be disabled in the BIOS of the machine
• Dual disk partition issue is observed if the Experion R3xx (when R3xx is
the base release) installation was performed using dual partition option
– If the secondary drives are not disabled, subsequently all drives will be
reformatted during the installation of the OS losing any data that may be on
the secondary drives.
– This is not applicable to USB drives attached to the node being migrated.
• Once the OS has been installed, the secondary drives can be re-
enabled in the BIOS.
2 5/8/2017
1
Migrate Server B
• Why Migrate Server B First?
– The Master ERDB and EMDB resides on Server B which is normally running
as the Backup Server
– Replication of the Database to other Nodes is performed by Server B
• Determine which type of Migration will be preformed.

– Experion Software only
– Experion Software/Operating System (Installation of Windows 2016 Server)
• If Migrating is from earlier release of Experion, then change OS
(Windows 2003 Server / Windows 2008 Server/ 2008 R2 Server to
Windows 2016 Server)
– Experion Software/Hardware Platform
• Recommended to have New Hardware Platform Pre-loaded, with
Windows 2016 Server before Migration is Started (to save time)
– Off Process Migration
– Use EMUG as a guide
3 5/8/2017
Migrate Server B
• Media needed
– Experion PKS System Initialization Media
– Experion PKS System Initialization Updates Media
– Experion PKS Installation Media
– Experion PKS Installation Media 2
– Experion PDF collection Media
– Microsoft Visual Studio 2012 integrated with CAB
– Experion ESM Media to install both Server and Client components
– Microsoft SQL Server 2014 Standard Edition SP1 (64-bit) Media
– Windows 2016 OS Re-installation Media or Microsoft Windows 2016 Media
ATTENTION:
• Some Third-party Applications and Programs not integrated with the Experion
PKS Installation DVD WILL NOT be MIGRATED FORWARD. Compatibility of
existing applications to the Experion target release must be determined prior to
starting the migration
• Follow the instructions provided with the Migration Application during the
Migration Process and perform migration of the applications manually
• Refer to the EMUG Section, Review Software Requirements, for specific
information regarding handling of these applications
4 5/8/2017
2
Migrate Server B
5 5/8/2017
On Process Migration – Concept Overview
Server A Server B
R431.x Sync‘d R431.x
Primary Backup
CS 1 CS 2 CS 3
R431.x R431.x R431.x
C300
ACE
C200 C200 C300
6 5/8/2017
3
On Process Migration – Station Display
7 5/8/2017
On Process Migration – Station Display (Activate OPM)
Click to
Activate
8 5/8/2017
4
On Process Migration – Station Display
9 5/8/2017
On Process Migration – Dual Primary
Not Synchronized
Use “Migrate Database”
Server A Server B from OPM Screen to
R431.x R500.x establish Dual Primary
(Server A Database is
Primary Primary Migrated to Server B)
CS 1 CS 2 CS 3
R431.x R431.x R431.x
C300
ACE
C200 C200 C300
10 5/8/2017
5
On Process Migration – Dual Primary w/ CStn
Not Synchronized
NOTE:
Server A Server B Must delete Console
Station Definition
R431.x R500.x from R431 A Server
Primary Primary
CS 1 CS 2 CS 3
R431.x R431.x R500.x
C300
ACE
C200 C200 C300
11 5/8/2017
On Process Migration – Dual Primary More CStn’s
Not Synchronized
Server A Server B
R431.x R500.x
Primary Primary
CS 1 CS 2 CS 3
R431.x R500.x R500.x
C300
ACE
C200 C200 C300
12 5/8/2017
6
On Process Migration – Finishing Sever Side
Server A Server B
R500.x Sync’d R500.x
Backup Primary
CS 2 CS 2 CS 3
R431.x R500.x R500.x
C300
ACE
C200 C200 C300
13 5/8/2017
On Process Migration – Sever OPM Complete
Server A Server B
R500.x Sync’d R500.x
Backup Primary
CS 1 CS 2 CS 3
R500.x R500.x R500.x
C300
ACE
C200 C200 C300
14 5/8/2017
7
Server/Station Migration with Operating
System Installation
Migrate Server B Server/Station Migration with Operating System Installation
15 5/8/2017
Migrate Server B
• These are the steps to migrate Server B to R500.x from

R431.x
– Migrate Server B following the procedures in EMUG
– Add Shortcuts
– Set up NTP Time server
– Join the Domain
– Run the Link Domain Scripts
– Migrate Server B Database
– Synchronize Server B with Server A
– Check for Server B compatibility
– Defrag the hard disk
NOTE : Patches should be installed after both servers are migrated!
16 5/8/2017
8
Migrate Server B – Migration Steps
• Before starting migration, add ESIS and EMSN to the Internet Explorer
Local Intranet site list
• Open Internet Explorer
• Go to Tools Internet Options
• Select Security Tab
• Select Local Intranet
• Click on Sites Button
17 5/8/2017

• Go to Start Run and type <\\<ESISServer IP>\<ShareName>
• Enter Logon Credentials
• Double click Setup.exe. The Installer Screen appears
• If the Installer Screen does not appear:
• Using Windows Explorer, browse to the drive, double click on Setup.exe to
Start the Install Sequencer
• NOTE: Major tasks that are performed by the Migration Application are
listed at the left in the dialog. The block next to each task indicates the
status of the task, where:
• Green (Blinking) – Indicates the current task
• Green (Steady) – Indicates the task is completed
• White – Indicates the task has not been performed
18 5/8/2017
9
• Select Product Migration
• Enter ESIS Path
• Enter User Name and Password
• Click Next
Syntax for
User name
Select for
Migration
19 5/8/2017

• Welcome to the Honeywell Experion PKS R500.1 Migration. The Setup
Wizard Screen is displayed
• Click Next
20 5/8/2017
10
• Accept the License Agreement and click Next
• Select the type of node to migrate and click Next
21 5/8/2017

• User and License Information Dialog screen appears
• Browse licenses .xml and Click Next
• Existing Packages Details screen appears.
• Click Next
22 5/8/2017
11
• Create a shared folder on another node as location for backup data.
This Remote Computer is referred to as EMSN
• Enter the drive letter which is assigned to the mapped EMSN shared
folder, in the Select Drive, to connect Network Folder list
• Enter the full path in the Network Folder text box
– Example \\<IP Address of a EMSN>\EMSN
• Enter the User Name and Password to connect to the folder
• Click Next
23 5/8/2017

• Enter Security Password
24 5/8/2017
12
• Retain or Change the Installation paths
– Click the Change button if you want to specify the Custom Installation Path
• Click Next
25 5/8/2017
• Experion Network Selection screen is displayed.

• Make appropriate selections and Click Next to proceed
26 5/8/2017
13
• Click Next to accept the FTE BootP and NTP IP Address Configuration
– Appears only for Process Server Migration with FTE
• Features and Options Selection dialog box is displayed.
– Features already installed are pre-selected
– Allows selection of features introduced in new release
• Click Next to continue
“Typical” for “Custom” for Required

Default Components
Components
27 5/8/2017

• Migration Application validates the EMSN information and checks for
space on the EMSN
• Experion Accounts Password Entry dialog box is displayed
• Enter appropriate passwords for all the accounts
• Click Next
28 5/8/2017
14
• Enter Experion Account Password for Secure Communication Service
– Click Next
29 5/8/2017

• Summary screen is displayed
• Click Install to proceed
30 5/8/2017
15
• Operating System Configuration dialog box is displayed. Confirm
selections
• Click Next
31 5/8/2017

• Operating System Configuration is evaluated and the following dialog
box is displayed. Enter User Name and Password
• Click Next
32 5/8/2017
16
• Network and Input/Output Device Information is displayed. Confirm
selections
• Click Next
33 5/8/2017

• Configuration Summary is displayed
• Save the Configuration File
• Click Finish
Click to Save the

Configuration File
34 5/8/2017
17
Steps
Completed
Step in
Progress
35 5/8/2017

• Phase 1 completes here
• Insert Experion PKS Initialization Media and reboot the System to
continue with the Migration
36 5/8/2017
18
• When the System boots from Experion PKS System Initialization DVD,
Experion PKS System Initialization PreInstall Utility screen appears
• Browse the configuration files and select the InitMediaOptions.xml file.
Click Next
• Check Use Drive C option to format only C drive
– Minimum Primary Partition Size is 100GB in cases of multiple partition
• Select Source Network/DVD/USB
• If Network ESIS is selected then enter ESIS path <IP address>\<share
name>
• Enter Logon Credentials to ESIS
• Select Static IP option and enter the IP Address of the server
• Click Next
• Accept the License Agreement and click Install
37 5/8/2017

• Experion Installation completes here
• Click Yes to Reboot the System
38 5/8/2017
19
Migrate Server B
• Re-install Virus Protection
• Re-install any third party applications and software
• Configure/verify FTE Properties
• Add Shortcuts
• Setup NTP Time Server
• Review any other topics in the Supplementary Installation Task Guide to
determine if other tasks are required for your System.
– If you cancel the On-process Migration now, you MUST restore or re-install
the previous version of Server B to return the system to a Redundant Server
State.
– If you restore Server B from a Ghost Image and it was previously a member
of a domain, it has to be removed from the domain and re-added to establish
a Trust Relationship.
NOTE: Defrag Hard Drives and Add Patches after both Servers are Migrated!
39 5/8/2017
Migrate Server B
• Migrate Server B Database.
– If your PC was a member of a domain, ensure that you have added the PC back to
the domain before you continue the migration.
• Ensure that the DNS is the same as the address recorded on the Pre-migration
Checklist.
• Run LinkDomainGroups.vbs
– C:\Program Files (x86)\Honeywell\Wkstasecurity\
• Default installation Path. This will be different if Custom Path is
selected
OR
– Start > Honeywell Experion Tools > All Honeywell Tools > System
Management
– If you have an LCN Connected Nodes Server (ESVT), install your TPS Personality
Software now, before you Migrate the Database
– Restart Server B to ensure all of the services have started properly.
– Migrate the Server B Database.
• Start the Database.
• Logon to Station connected to Server A with mngr access.
• Choose Configure>System Hardware>On Process Migration to call up the OPM
Display.
• Click Migrate DataBase then Yes to Start the Migration.
• You will be in Dual Primary state when this is complete
40 5/8/2017
20
Migrate Server B
• A Synchronization lost error is expected and does not require action
• If Server B remains as the Backup Server or is stopped, you must do the
following:
– Unload the Database on Server B
– Return Server B to the System running
– Verify that the Migrate Database button on server A is enabled
– Contact TAC team
• Otherwise, Server B is in Dual Primary
– There could be up to a 10 second loss of history
– Continuous Synchronization between Servers is Disabled
– If you cancel now, you must Restore from Old Images or Re-install
– You must Migrate at least One Client Computer
41 5/8/2017
Migrate Server B
• In Summary, these are the steps taken to Migrate Server B to R500.x
from R431.x
• Migrate Server B, following the procedures in EMUG
• Add Shortcuts
• Set up NTP Time Server
• Join the Domain
• Run the Link Domain Scripts
• Migrate Server B Database
• Synchronize Server B with Server A
• Check for Server B Compatibility
NOTE: These two steps should be done after both Servers are Migrated!
Download and Add Patches from OLS
Defrag the Hard Disk
42 5/8/2017
21
Adding Shortcuts Manually
Migrate Server B Copyright © 2017 Honeywell International Inc. Adding Shortcuts Manually
43 5/8/2017
Shortcuts
• Never add a shortcut for QuickBuilder!!!!!
– Shortcuts will allow you to have multiple project files using different file
names
– When QuickBuilder is launched, it looks for only the one QDB file on the
primary server
• If you are connected to Server B which is a Backup Server, then shortcut
referring to QuickBuilder file on Server B would be incorrect
Migrate Server B Copyright © 2017 Honeywell International Inc. Adding Shortcuts Manually
44 5/8/2017
22
Download and Add Patches from OLS
Website
Migrate Server B Copyright © 2017 Honeywell International Inc. Download and Add Patches from OLS Website
45 5/8/2017
The Problem with Patches…

• Patches / Updates / Service Packs
• Consider Server/Client, Controller/Engineering Tools, and Common
Components areas separately
• Each DE Organization has their own installation methods
• Patches – generally a specific fix ( also ISRs on the Server )
• Updates – generally a collection of fixes (not necessarily related)
• Service Packs – larger collection of fixes – covering wide area of product
• Patch / Update ending in C denotes “cumulative”
• A cross-functional team is actively working to revamp and improve the Patch /
Update / Service Pack Process
• Reference the Experion Update Matrix on OLS
Migrate Server B Copyright © 2017 Honeywell International Inc. Download and Add Patches from OLS Website
46 5/8/2017
23
Updating Display Files
Migrate Server B Copyright © 2017 Honeywell International Inc. Updating Display Files
47 5/8/2017
Migrating Display Files

• To migrate the displays after migrating the node to the target release,
use “Bulk Display Migration tool” to update/migrate custom display
(.htm) and shape (.sha) files.
• Run and apply the HMIWeb Bulk Display Migrator tool to the abstract
folder or any other folder containing custom displays.
48 5/8/2017
24
Migrating Display Files (cont.)
• If the display files are stored in C:\Program Files\<folder> before
migration:
– Select the option Convert “Program files” path string to “Program Data”.
– The migrated custom displays are moved to the new location i.e. “Program
Data”.
49 5/8/2017
To Migrate Display and Shape Files

• Backup all the display files.
• On the server where display and shape files are located, go to,
– C:\Program Files (x86)\Honeywell\ExperionPKS\Client\HMIWeb Display
Builder.
• For custom installation path, navigate to:
– C:\Honeywell\Experion PKS\Client\HMIWeb Display Builder.
This path can differ if custom

install path selected is different
• Right-click BulkDisplayMigrator.exe and select Run as administrator.

• Browse to the abstract folder (C:\ProgramData\Honeywell\Experion
PKS\Client\Abstract) or any other folder that contains any custom
display (.htm) files.
50 5/8/2017
25
Check to See if Server B is Working
Migrate Server B Copyright © 2017 Honeywell International Inc. Check to See if Server B is Working
51 5/8/2017
Post Migration Verifications

• Considerations:
– SCADA Controllers may only support one connection, which remains with
Server A. Therefore, these controllers will not report values, changes, or
alarms to server B, unless you disable the connection from Server A and
enable the connection from Server B
– Operations performed on Server A and Server B; such as changing

parameters, acknowledging alarms, and so on, will not be seen nor recorded
on Server B and Server A respectively
– Script engines are Disabled on server B. Running the same scripts

concurrently on Server A and server B may result in unpredictable behavior.
You can enable the script engine on server B
– If the redundant server pair is part of a Distributed System Architecture

(DSA), server B can only subscribe to data within the DSA. Other servers
within the DSA remain connected to Server A
52 5/8/2017
26
• Considerations cont’d
– CDA Hardware items will continue to appear on the Alarm Summary Display
within the asset that has the same name as the area to which the hardware
item was assigned in the previous Experion release
– CDA Hardware items will not appear in the System Status Display until you
download the hardware items to the Experion server. The completing On-
process Migration task will instruct you when to complete this step
53 5/8/2017

Step Action
1 On Server A and Server B:
 Start Station.
 Ensure that the Station running on Server B connects to Server B. The server name is displayed on the
Station’s Status Line. You can change the server connection by choosing Station > Connect, and then
clicking Server B in the Server list.
 Call up displays, trends, and so on.
 Compare the displays on the Station connected to Server A with the Station connected to Server B.
2 Control selected addresses on each controller and confirm correct operation.

3 If the Redundant Server pair is part of a Distributed System Architecture (DSA), confirm that data is being
correctly received by Server A and Server B
4 Enable any SCADA Channels that support multiple connections, such as OPC Channels, and test for correct
operation
5 SCADA Devices that support only one connection can be tested on server B by disabling the connection on
Server A and enabling the connection on Server B
6 Test the operation of Console Stations connected to server B

7 If the Redundant OPM Server pair is part of a Distributed System Architecture (DSA), force any DSA Servers
connected to Server A to connect to Server B and confirm that DSA Data is being received from Server B.
To do this, on each primary DSA Server connected to the Redundant OPM Server pair, call up the DSA Status
Page for the Redundant OPM Server pair and select the Test On Process Migration (Connect to Server B)
check box
Migrate Server B 54 Check to See if Server B is Working
5/8/2017
27

Topic: Migrate Server B
Contents
(E) Migrate Server B using ESIS ........................................................................................................... 3
(E) Join the Domain ............................................................................................................................... 9
(E) Set Up NTP Time Server ...............................................................................................................11
(E) Migrating Database ........................................................................................................................13
(E) Migrate Quick Builder Database ....................................................................................................15
(E) Update Custom Station Files .........................................................................................................17
(E) Rebuilding Checkpont Files ...........................................................................................................19
(E) Saving Checkpoint Manually .........................................................................................................21
(E) Verify Server B Operation ..............................................................................................................23


Migrate Server B

In this lab, you will Migrate Server B using ESIS
 Step Action

Migrate Server B
 Step Action
ATTENTION
During On-process migration, monitor the process on

the console station ESC04.
After migration of first console station(EC2501), you
can continue to monitor the process from ESC2501
ATTENTION

1.Overview
2.T_100
3.D_100
4. E_100
5. Tankfarm
Toolbar on Station

Server (ESV25)

On OPC Node, open system management display and

observe the RDM component “RDMESVAESVB”
appears under OPC Node.
RDM
Configure Internet Explorer Security

Migrate Server B
 Step Action
ATTENTION

4 Refer to the procedure in the guide generated by the Upgrade Tool to Configure Internet
Explorer Security
Topic Migrating Server B on-process
Section Configuring the Internet Explorer security
Subsection To configure the Internet Explorer security
ATTENTION
Step 1 Right click on the Internet Explorer icon and select Run as
Administrator
Step 3 Do not click Advanced, there is no Advance button
Step 4 Skip step 4
Step 5 Refer Partition sheet for IP address of EMSN node
Step 6 Refer Partition sheet for IP address of ESIS node
Migrate Server B
5 Refer to the procedure in the guide generated by the Upgrade Tool to perform Server B
migration
Topic Migrating an Experion node and installing the operating system
Section To start the migration application for ESIS-based migrations from a
Network share

Migrate Server B
 Step Action
migration
Section To continue with the migration application
ATTENTION
Step 4
Skip this step.
and 5
Step 7 Refer partition sheet for license details.

Step 8 Skip this Step. This option does not appear for Server
and 9 node
On Experion Migration Storage Node and Advanced
Step 10 Migration Options screen appears.
Then enter following details using partition sheet
a. Network Folder location i.e IP address of
EMSN node and share folder name (ServerB)
b. User name and Password to access share
folder
Click Next
Step 15 Retain default installation paths
Step 19 Select Custom and check Experion PKS System
Documentation & Experion PKS SCN, Installation
and Migration options to install PDF collection for
R500.
Note:- After Server B migration, Install Adobe Reader
from ESISR500\D_PDF folder
node

Migrate Server B
 Step Action
migration
Section To proceed with system information collection
ATTENTION
Step 2 Refer partition sheet for passwords

Before Password entry for Secure Communications Services dialog box
Step 3 appears. Refer partition sheet and enter the password
Step 5 Retain Default
Step 6 Refer partition sheet and Enter User Account Name and Password
Step 9 RPS option is not available for selection for Server node. Click Next
Step 11 Save Configuration files on C:\Student
After Insert the Initialization media
Step 13
and 15

Migrate Server B
 Step Action
migration
Topic Installing the operating system using Experion PKS System Initialization
media
Section To complete the operating system installation
ATTENTION
Step 1 Skip step 1

Step 2 Insert the Initialization media
Step 4 Browse to local C:\Student for InitmediaOptions.xml file
Step 6 If multiple drives are available, select Use drive C: (System) option else
select single partition option
Select ESIS from Network. Refer partition sheet for path of ESIS and for
security password
After Click Yes on message box that pops up after clicking Install
Step 10
Step 12 Skip this step as we are performing ESIS based installation
All steps are automated as we are using ESIS. No user intervention is
required.
Installation will take about 4 hours to complete.
After installation completes click Yes on the Experion PKS R500 – Status
Display to reboot the node
9 After reboot, login to server B with Local Administrative privileges, in class as Student
10 Add Student user to Product Administrators group
ATTENTION
Right Click on Start Menu (Windows icon) Select Computer

Management>Local users and Groups > Users>student
11 Sign Out and Sign In as Student
ATTENTION
Right Click on Start Menu (Windows icon) Select Shut down or Sign out >
Sign out

Migrate Server B
(E) Join the Domain
(E) Join the Domain

In this lab, you will Join Server B to the Domain
 Step Action
Add Node to Domain
12 If not already, logon on to Server B with administrative privileges, in class as Student
13 Configure the Honeywell FTE MUX-IM Virtual Miniport Driver – Internet Protocol Version
(TCP/IPv4) properties – DNS Server IP address to be the IP address of your domain
controller
14 Refer to the procedure in the guide generated by the Upgrade Tool to add node to
Domain
Section Add a node to a Windows domain
Sub Section To add a node to a Windows domain
ATTENTION
Step 1 Right click on start menu(windows Icon) to get the System

option
Step 4 Refer partition sheet for Domain Name. Click OK after specifying
the Domain name
Step 5 In class, enter User Name as Student. Refer partition sheet for
password
Step 6 After acknowledging the message click Close on System
Properties window and then click Restart Now
15 Refer to the procedure in the guide generated by the Upgrade Tool to run the link
Domain Groups
Section Run Link Domain Groups
Sub Section To run Link Domain Groups
ATTENTION
Step 2 Choose Start > Honeywell Experion Tools > All Honeywell
Tools >System Management and then right click "Link
Domain Groups" run as Administrator

Migrate Server B
(E) Join the Domain

Migrate Server B

In this lab, you will Setup Server B as Secondary Time Server
 Step Action
Run the NTP Config Utility
1 Logon on to Server B with Administrative privileges, in class as Student
2 In Windows Explorer, navigate to C:\Program Files (x86)\Honeywell\Experion

PKS\Utilities\NTPSetup . For custom installation path, navigate to <User selected
path>\Honeywell\Experion PKS\Utilities \NTPSetup
3 Right-click NTPConfg.exe and select Run as administrator. The NTP Configuration

dialog box is displayed.
4 To restore previous NTP configuration settings, click Yes.
The previous NTP configuration settings are restored.
5 If NTP configuration settings is not restored due to a file mismatch, then the following
message is displayed.
Click OK.

Migrate Server B
 Step Action
6 If the NTP configuration settings are not restored, refer to the Experion Supplementary
Installation Tasks Guide and Experion Server and Client Planning Guide to reconfigure
the NTP settings.
ATTENTION
Experion Supplementary Installation Tasks Guide

Section NTP adjustment on a workgroup system that
was recently added to a domain
Subsection Adjusting NTP Servers
Step Skip the Steps
3 to 5

Migrate Server B

In this lab, you will Migrate the Database
 Step Action
Migrate Database
1 Refer to the procedure in the guide generated by the Upgrade Tool to Migrate Database
Section Migrating the database

Migrate Server B

Migrate Server B

In this lab, you will migrate the Quick Builder Database
 Step Action
Migrate Quick Builder Database
1 Refer to the procedure in the guide generated by the Upgrade Tool to Upgrade the Quick
Builder Database
Section Updating the Quick Builder database
Sub Section To open Quick Builder database
ATTENTION
Launch Configuration Studio on Server B, Connect to

server B
Step 1 Choose Start > Honeywell Experion Tools >

Configuration Studio > Server > Control Strategy >
Build Channels

Migrate Server B

Migrate Server B

In this lab, you will update the Custom Station File
 Step Action
Updating custom setup files
1 Refer to the procedure in the guide generated by the Upgrade Tool to update Custom
.Stn file
Section Updating custom setup and toolbar files
Subsection To update the custom setup files (*.stn)
ATTENTION
Step 4 Select the .Stn file connecting to Server A and Click

Edit Connection
Step 5 Skip these steps
and 6
Step 8 If required, Change the path containing System >
R431 to current location containing System > R500,
folder in class
PKS\Client\System\R500
2 Refer to the procedure in the guide generated by the Upgrade Tool to update Display
and Shape files.
Section Updating display files
Subsection To migrate Display and Shape files
ATTENTION
Step 4 To View Program Data Folder This PC > C Drive >View

Tab> Options> change search and folder Options.
On Folder Options Window Select View Tab>Hidden
Files Folders > select Show hidden files,folders,and
drives
Step5 Skip this step

In Class select “ Migrate the read only files.Do not take
the backup of original files” option

Migrate Server B

Migrate Server B

In this lab, you will rebuild the checkpoint files
 Step Action
Rebuild Checkpoint Files
1 Refer to the procedure in the guide generated by the Upgrade Tool, to rebuild checkpoint
files
Section Rebuilding Checkpoint files
Subsection To initiate checkpoint rebuild

Migrate Server B

Migrate Server B

In this lab, you will save checkpoint manually
 Step Action
1 Refer to the procedure in the guide generated by the Upgrade Tool, to save checkpoint
manually
Section Saving Checkpoint Manually

Migrate Server B

Migrate Server B

In this lab, you will Check Server B for Compatibility
 Step Action
Check Server B for Compatibility
1 After performing the Migrate Database step, both Servers should be running as Primary;
known as Dual Primary State.
Check the status of both the Servers
2 Open Station Application on Server B. The Station should get connected to Server B
3 Launch Configuration Studio on Server B. Your System must be listed twice; one
showing Server A as Primary and other showing Server B

Migrate Server B
 Step Action
4 Connect to System showing server B as primary

Migrate Server B
 Step Action
5 Launch Control Builder. All controllers, IOMs, and Control Strategies must show ‘online’
in monitoring mode
6 The status line in Control Builder must show as below
ATTENTION
Contact your Instructor if any of the above check fails

Migrate Server B
 Step Action
ATTENTION

1.Overview
2.T_100
3.D_100
4. E_100
5. Tankfarm
Toolbar on Station

Server (ESV25)


RDM

Migrate First ES-C
Migrate First Experion Client node (ES-F /ES-C) Copyright © 2017 Honeywell International Inc. Migrate First ES-C
1 7/5/2017
Migrate Console Station

• Migration of the first Console Station allows an operation to access the
process with the R500.x System without using the Server
• Some Honeywell Applications and Third Party Software will NOT

MIGRATE and must be Re-installed
• Be sure to enter the same mngr Password used in the beginning of the
migration checklist
• Disconnect Station from ServerA.

– You should be connected to Server A.
– Server B should be in Dual Primary Mode.
2 7/5/2017
1
• Close any Windows Applications prior to starting
• Disable any Virus Protection Software
• Create a backup of Console station and record the location
• Determine which type of migration will be performed

– Migration WITHOUT an Operating System Change
– Migration WITH an Operating System Change
– Migration WITH Hardware Change
3 7/5/2017

• Steps to Migrate Console are the same as a Server with the following
few exceptions
– Type of Node to Migrate is Console Station
– User and License Information is Displayed
– Experion Server Name is Displayed
2
1
4 7/5/2017
2
• Check for Compatibility.
– If Station passes compatibility tests, continue migrating all Stations until all
are operating on R500.x
• If the Migrate Station Task cannot be successfully completed, DO NOT
PROCEED any further with the On-process Migration. Contact your
Honeywell Technical Assistance Center (TAC).
5 7/5/2017
6
3

Topic: Migrate First Experion Client node (ES-F /ES-C)
Contents
(E) Migrate Console Station using ESIS................................................................................................ 3
(E) Join Domain ..................................................................................................................................... 7
(E) Set Up NTP Time Server ................................................................................................................. 9
(E) Verify Console Station Operation ..................................................................................................13


Migrate First Experion Client node (ES-F /ES-C)

In this lab, you will Migrate Console Station using ESIS
 Step Action
Configure Internet Explorer Security
ATTENTION

2 Logon Console Station with Domain Administrative Privileges, in class as Student
Explorer Security
Topic Migrating Console Stations
Section Configuring the Internet Explorer Security
Subsection To Configure the Internet Explorer Security
ATTENTION
Step 1 Right click on the Internet Explorer icon and select Run
as Administrator
Step 5 Refer to the Partition sheet for IP Address of EMSN Node
Step 6 Refer to the Partition sheet for IP Address of ESIS Node
Migrate Console
4 Refer to the Procedure in the guide generated by the Upgrade Tool to perform Console
Station Migration
Topic Migrating an Experion Node and installing the Operating System
Section To start the Migration Application for ESIS-Based Migrations from a
Network share

 Step Action
5 Refer to the procedure in the guide generated by the Upgrade Tool to perform Console
Station Migration
Topic Migrating an Experion Node and Installing the Operating System
Section To Continue with the Migration Application
ATTENTION

and 5
Step 7 Skip this step. This option does not appear for Console Station
Step 8 Skip this Step as we are not installing CAB or PMD HMI
and 9 Extension features
On Experion Migration Storage Node and Advanced Migration
Step 10 Options screen appears.
Select Platform Hardware Change option
a. Network Folder location i.e IP address of EMSN node
and share folder name (Cstn).
b. User name and Password to access share folder
If the network computers are not visible in the Browse for
folder window, turn on Network discovery from Network
and sharing Center
Click Next
Step 16 Retain default
Documentation & Experion PKS SCN, Installation and
Migration options to install PDF collection for R500.
Note:- After Console Station Migration, Install Adobe Reader

 Step Action
Station Migration
Section To proceed with System Information Collection
ATTENTION

Step 4 Select Server platform and Win2016 Operating System.
Note: For Console Station both Win2016 and Win10 operating
systems are supported.
Step 9 There is no RPS so skip this step. Click Next
Step 13
and 16

 Step Action
Station Migration
Topic Installing the Operating System using Experion PKS System
Initialization Media
Section To Complete the Operating System Installation
ATTENTION
Step 1 Skip step 1

Select ESIS from Network. Refer partition sheet for ESIS path and for
Security Password
Step 10
required.
8 After reboot, login to the Console Station with Local Administrative privileges, in class as
Student
9 Add the Student user to Product Administrators group
ATTENTION

ATTENTION
Sign out

(E) Join Domain
(E) Join Domain

In this lab, you will join Console Station to the Domain
 Step Action
Add Node to Domain
11 If not already, logon to Console Station with administrative privileges, in class as

Student
(TCP/IPv4) properties – DNS Server IP Address to be the IP address of your Domain
Controller
13 Refer to the procedure in the guide generated by the Upgrade Tool to add Node to the
Domain
Section Add a Node to a Windows Domain
Sub Section To Add a Node to a Windows Domain
ATTENTION
Step 1 Right click on start menu(windows Icon) to get the System

option
Step 4 Refer to the Partition Sheet for the Domain Name. Click OK
after specifying the Domain Name
Step 5 In class, enter the User Name as Student. Refer to the
Partition Sheet for Password
Step 6 After acknowledging the message, click Close on the
System Properties window and then click Restart Now
Domain Groups
ATTENTION
Step 2 Choose Start > Honeywell Experion Tools > All

Honeywell Tools >System Management and then right
click "Link Domain Groups" run as Administrator

(E) Join Domain


In this lab, you will synchronize the time between client node and the time server
 Step Action
1 Logon on to the Client Node with Administrative privileges, in class as Student
2 Refer to the procedure in the guide generated by the Upgrade Tool to setup NTP Server

Section Setting up time synchronization
Sub Section To run the NTPConfig utility



 Step Action
1 Refer to the procedure in the guide generated by the Upgrade Tool to update Custom
.Stn file
ATTENTION
Step 4 Select the .Stn file and Click Edit Connection

and 6
folder in class
ATTENTION
Display and Shape files must be updated after this step
2 Refer to the procedure in the guide generated by the Upgrade Tool to update Display
and Shape files.
Section Updating display files
Subsection To migrate Display and Shape files
ATTENTION
Step 5 In class, Select Migrate the read-only file. Do not take a backup of the
original files.



In this lab, you will Check Console Station for Compatibility
 Step Action
Check Console Station for Compatibility
1 Open the Station Application on Server B
2 From the Menu Bar, select Configure > System Hardware > Console Stations
3 Ensure that the Console Station is listed on the display
4 Click on the Console Station name. The Node Status should show Status as OK
5 Open the Station Application on Console Station
6 Ensure that the Console Station is in Synchronization with Server B
ATTENTION
After migration of first console station, continue to

monitor process through migrated console station
ESC2501

 Step Action
ATTENTION

1.Overview
2.T_100
3.D_100
4. E_100
5. Tankfarm
Toolbar on Station

Server (ESV25)


RDM.
Check this status on ESC04 node, or add nodes to
System Management Display on ESC2501 and then
check this status.

Migrate Server A
Migrate Server A and Synchronize Copyright © 2017 Honeywell International Inc. Migrate Server A
1 5/8/2017
Migrate Server A
• Steps to Migrate Server A are the same as Server B with a few
exceptions
• When Server B is on R500.x and Sever A is on

R400.x/R410.x/R430.x/R431.x/R432.x, Servers are running in Dual
Primary Mode. When the migration starts for Server A, Server B
becomes the Primary Server. All nodes connected to Server A will loose
view to the database
• Replication is only disabled on Server B since it is the Master ERDB and

EMDB. You can not access Admin Tasks on Server A
• After you have Migrated Server A, its status should go to Backup
• Add the Server back to the Domain and run the LinkDomainGroups.vbs
• Synchronize the Servers

2 5/8/2017
1
Migrate Server A
• Check the appropriate File Replication check boxes that were previously
unchecked in the Prepare for Migration Checklist. These are the
flbkup.def files
• These files were previously marked with a “S” before migration.
– For example: * Copy history archive to the backup
S \Server\archive
After Migration: To re-enable file backups that are added to the
flbkp.def file of server, re- apply the “S” to each
file that was recorded before migration and
close the file
• Enable ERDB and EMDB Replication

• Open Enterprise Model Builder and perform LOAD ENTIRE MODEL for
both Assets and Alarms Groups
3 5/8/2017
4
2
Topic: Migrate Server A and Synchronize
Contents
(E) Migrate Server A Using ESIS .......................................................................................................... 3
(E) Join the Domain ............................................................................................................................... 9
(E) Set up NTP Time Server ................................................................................................................11
(E) Post Migration Tasks .....................................................................................................................15


Migrate Server A and Synchronize

In this lab, you will Migrate Server A using ESIS
 Step Action
Enable SCADA Channels on Server B
1 Logon to Server B with Domain Administrative Privileges, in class as Student
2 Open the Station Application on Server B
3 Select View > System Status > SCADA Controllers
4 Enable all SCADA Channels
5 Select View > System Status > OPC Integrator
6 Enable all OPC Integrator groups
7 From the Services panel, ensure that Experion PKS CDA –SP service is running
Disable SCADA Channels on Server A
8 Logon to Server A with Domain Administrative Privileges, in class as Student
9 Open the Station Application on Server A
10 Select Configure > System Hardware > Channels
11 Disable all SCADA Channels(Except CONUSE0)
12 Select View > System Status > OPC Integrator

Disable OPC Integrator groups.
Configure Internet Explorer Security on Server A
13 Logon to Server A with Domain Administrative Privileges, in class as Student

 Step Action
Explorer Security
Topic Migrating Server A On-process
Section Configuring the Internet Explorer Security
Subsection To Configure the Internet Explorer Security
ATTENTION
Step 1 Right click on the Internet Explorer icon and select

Run as Administrator
Step 3 DO NOT click Advanced, there is no Advanced Button
Step 4 Skip
Step 5 Refer to the Partition Sheet for the IP Address of
EMSN Node
Step 6 Refer to the Partition Sheet for the IP Address of ESIS
Node
Migrate Server A
15 Refer to the procedure in the guide generated by the Upgrade Tool to perform Server A
Migration
Section To start the Migration Application for ESIS-based Migrations from a
Network share

 Step Action
Migration
Section To Continue with the Migration Application
ATTENTION
Step 4
Skip this step.
and 5
Step 7 Refer partition sheet for license details.

and 9 node
On Experion Migration Storage Node and Advanced
Step 10 Migration Options screen appears.
a. Network Folder location i.e IP address of
EMSN node and share folder name
b. User name and Password to access share
folder
Click Next
Documentation & Experion PKS SCN, Installation
and Migration options to install PDF collection for
R500.
Note:- After Server B migration, Install Adobe Reader
node

 Step Action
Migration
Section To Proceed with System Information Collection
ATTENTION

Before Password entry for Secure Communications Services dialog box
Step 3 appears. Refer partition sheet and enter the password
Step 9 RPS option is not available for selection for Server node. Click Next
Step 13
and 16

 Step Action
Migration
Topic Installing the Operating System using Experion PKS System
Initialization Media
Section To Complete the Operating System installation
ATTENTION
Step 1 Skip step 1

Select ESIS from Network. Refer partition sheet for ESIS path
Step 10
required.
19 After reboot, login to Server A with Local Administrative privileges, in class as Student
20 Add Student user to Product Administrators group
ATTENTION

ATTENTION
Sign out


(E) Join the Domain
(E) Join the Domain

In this lab, you will Join Server A to Domain
 Step Action
Add Node to Domain
22 If not already, logon to Server A with Administrative Privileges, in class as Student
(TCP/IPv4) properties – DNS Server IP Address to be the IP Address of your Domain
Controller
24 Refer to the procedure in the guide generated by the Upgrade Tool to add Node to
Domain
Section Adding a Node to a Windows Domain
Sub Section To add a Node to a Windows Domain
ATTENTION
Step 1 Right click on start menu(windows Icon) to get the System option
Step 4 Refer to the partition sheet for the Domain Name. Click OK after
specifying the Domain Name
Step 5 In Class, enter the User Name as Student. Refer to the partition
sheet for the Password
Step 6 After acknowledging the message, click Close on the System
Properties window and then click Restart Now
Domain Groups
ATTENTION
Step 2 Choose Start > Honeywell Experion Tools > All Honeywell Tools
>System Management and then right click "Link Domain Groups"
run as Administrator

(E) Join the Domain


In this lab, you will Setup Server A as Secondary Time Server
 Step Action
1 Logon on to Server A with Domain administrative privileges, in class as Student
2 Refer to the procedure in the guide generated by the Upgrade Tool to setup NTP Server
Topic MIGRATING SERVER A ON-PROCESS

Section Setting up time synchronization
Sub -Section To run the NTPConfig utility



 Step Action
1 Refer to the procedure in the guide generated by the Upgrade Tool to Custom .Stn File
Topic Migrating Server A on-Process
ATTENTION
Step 4 Select the .Stn file connecting to Server B and Click

Edit Connection
and 6
folder in class



In this lab, you will perform Post Migration Steps
 Step Action
Synchronize Servers from Server B
1 Refer to the procedure in the guide generated by the Upgrade Tool to Synchronize the
Servers
Section Synchronizing the Servers
Subsection To Synchronize the Servers
Enabling ERDB Replication
2 Refer to the procedure in the guide generated by the Upgrade Tool to enable ERDB
Replication
Section Enabling ERDB Replication
Subsection To Enable Experion ERDB Replication
ATTENTION
Perform these steps only on Server B.

Enabling EMDB Replication
3 Refer to the procedure in the guide generated by the Upgrade Tool to enable EMDB
replication
Section Enabling EMDB Replication
Subsection To enable Experion EMDB Replication
ATTENTION
Perform these steps only on Server B

Enabling File Replication

 Step Action
4 Refer to the procedure in the guide generated by the Upgrade Tool to enable File
Replication
Topic Migrating Server A on-Process
Section Enabling file Replication
Subsection To enable file replication after migration
ATTENTION
Step 2 Skip this step.

Step 3 "New Replication objects created in R500 are already
enabled. Enable replication only for the objects that
were disabled before migration"
Enabling File Backup
5 Refer to the procedure in the guide generated by the Upgrade Tool to enable the File
Backup. Perform this step on both Server B and Server A
Section Enabling File Backup (flbkup.def)
Subsection To enable file backups after migration
ATTENTION
Step 1 Run the Notepad as Administrator

Step 2 In the classroom, ensure that the OPCIntegrator
Directory has an “S” at the beginning
Rebuilding Checkpoint Files

 Step Action
6 Refer to the procedure in the guide generated by the Upgrade Tool to rebuild Checkpoint
Files
Section Rebuilding Checkpoint Files
Subsection To initiate Checkpoint Rebuild
ATTENTION
Perform these steps on Server B

Step 2 Refer to the partition sheet and connect to your
System
Step 6 Select SCE_Sim
Saving Checkpoint Manually
7 Refer to the procedure in the guide generated by the Upgrade Tool, to save Checkpoint
Manually
Section Saving Checkpoint Manually
Subsection To Save Checkpoint Manually
ATTENTION

Step 3 SCE-Sim to To be Saved: box
Load Assets and Alarm Group models

 Step Action
8 Refer to the procedure in the guide generated by the Upgrade Tool, To load the Asset
and Alarm Group Models
Section Loading the Asset and Alarm Group Models
Subsection To load the Asset and Alarm Group Models
ATTENTION

Changing the Server A to Primary
9 Refer to the procedure in the guide generated by the Upgrade Tool, to change server A
to primary
Section Changing the Server A to Primary
Subsection To verify the server status
Monitor the Process

 Step Action
10
ATTENTION

1.Overview
2.T_100
3.D_100
4. E_100
5. Tankfarm
Toolbar on Station

Server (ESV25)


RDM


Migrate Controllers
Migrate Controllers Copyright © 2017 Honeywell International Inc. Migrate Controllers
1 5/8/2017
Controller Migration Procedure

• Obtain latest ERDB Consistency Checker tool from the Online Support
Website
• Perform Pre-migration Checks and check for Migration Readiness
– Run Upgrade Tool and ERDB Consistency Checker
• Correct any issues with Controller Database, such as Dangling
Connections and Inconsistencies between ERDB and Controller
– Run Upgrade Tool Checks and ERDB Consistency Checker again
• Search for any unsupported modules in the Redundant Chassis Pair
(RCP).
– Manually change the firmware for any unsupported modules using
NTools/CTools.
• Synchronize the Redundant Chassis Pair (RCP) or Redundant
Controllers
• Initiate Controller Migration
• Post Migration Checks
Migrate Controllers Copyright © 2017 Honeywell International Inc. Migrate Controllers
2 5/8/2017
1
Migrate Controllers Copyright © 2017 Honeywell International Inc. Perform Pre-Migration Checks
3 5/8/2017
Upgrade Tool
• Select the Controller and Run Readiness Check
Migrate Controllers Copyright © 2017 Honeywell International Inc. Perform Pre-Migration Checks
4 5/8/2017
2
Searching for Unsupported Modules
Migrate Controllers Copyright © 2017 Honeywell International Inc. Searching for Unsupported Modules
5 5/8/2017
Check for Unsupported Modules

To check for Unsupported Modules:
NTools*
1. Choose Start>Run
2. For Control Net Supervisory Networks, type: ntools –c –u –pg
3. For Ethernet Supervisory Networks, type: ntools –e –u –pg
4. Click OK to launch NTools application
5. Click the Resume button on the toolbar to initiate a Network Scan
6. In the Desktop Tree, click the required Supervisory Communication Interface
7. Wait for the Chassis Details to display in the Detail Pane
CTools for C300
1. Choose Start>Run
2. Click the Browse button to open the Browse dialog.
3. Navigate to this directory location: C:\Program Files(x86)\Honeywell\Experion
PKS\Engineering Tools\system\bin\CTools
4. CTools can also be opened by typing CTools in RUN and click Enter
6 5/8/2017
3
Check for Unsupported Modules
Results
• The Controller Migration Wizard does not support modules that have a
firmware version displayed in Red or Yellow or Cyan.
• A Red Firmware version indicates a recognized module type with an

unknown firmware version. You must perform an Off-process Correction
to the firmware version using the Network Tools Application
• A Yellow Firmware version indicates the module type is not recognized.

You must perform an Off-process replacement with an Equivalent
Supported Module Type
• A Cyan Firmware version indicates that the module F/W is newer than
the most recent identified in ver_rev text file
7 5/8/2017
8
4
Initiate Controller Migration of Selected
Chassis
Migrate Controllers Copyright © 2017 Honeywell International Inc. Initiate Controller Migration of Selected Chassis
9 5/8/2017
IMPORTANT:
• The Migration updates the Firmware of all the components in the
selected Redundant Chassis Pair without loss of control.
– There may be a Freeze in Control (up to 10 seconds) on C200, and (up to
20 seconds) on C300 Controllers (depending on the size of the Control
Strategy),
– SCMs in Peer Controllers may experience delay during the Control Freeze
Period, resulting in Step Timeout or Failure Notifications.
• Before starting the Migration
– Run the Readiness Check using the Upgrade Tool
– All errors have to be corrected before proceeding.
– Run the ERDB Consistency Checker to check for any Dangling Connection
or Inconsistencies between ERDB and Controller Database.
– If your System has Fault Tolerant Ethernet Bridge Modules (FTEBs), verify
the Switch Port Settings.
10 5/8/2017
5
Migration Prerequisites
• Purchase the Redundancy License required to enable the On-Process
Migration
• The associated Experion Servers must be migrated (does not apply for
service pack or software update releases)
• Run the BOOTP Checker tool to verify the proper BOOTP Server
Configuration
• Synchronize the Redundant Chassis Pair (RCP) or the Controllers
• RCP must only contain CNI Module numbers CCN013/CCR013 or

CCN014/CCR014 for On-process Migration
• Ensure CNI Modules are at latest firmware version, manually upgrade

the CNI Modules to latest firmware using NTools
11 5/8/2017
• ControlNet Communication Paths with FIMs or HART I/O Modules must
only contain CNI Module numbers CCN013/CCR013 or
CCN014/CCR014
– Legacy CNI Modules CCN012 or CCR012 can reside in Non-redundant
Controllers or I/O Chassis that do not contain FIMs or HART I/O Modules.
• Ensure RM Modules are at the latest firmware version; manually

upgrade the RM Modules to latest firmware version using NTools
12 5/8/2017
6
• Stop the HART Software Multiplexer Service
• Controller Migration Wizard supports only Honeywell qualified Module
Types and Firmware Versions
• If the System uses any CCL Blocks, then create a backup of the CCL,
and record the Path Name to the Backup
• Ensure that all Peer-to-Peer References in the C200/C300 CEE are
working as expected before starting the On-process Migration
• Make sure that all required Experion software updates are installed
before starting Controller on-process Migration
• Ensure all the Base Execution Period of every CEE FB (BASEPERIOD
parameter) is not set to DEFAULT
• Ensure no active locks in the Engineering Repository Database (ERDB)
13 5/8/2017
• Ensure that Auto Synchronization State of each Redundancy Module is
set to Conditional
• If the System contains Series C Control Hardware, (C300 Controllers,
FIM4s) you must upgrade the CF9 Control Firewall to the latest firmware
before you Migrate the Series C Hardware
• Obtain the latest version of the ERDB Consistency Checker utility from
the HPS Online Support site
• Run the Identify ERDB/Controller Inconsistencies check from Control
Builder on the controllers that are to be Migrated
• Perform a Manual Checkpoint save for each controller, prior to start of
Migration
• Make any required modifications to the control strategies (for example,
time syntax in expression blocks)
• Perform the Controller Migration Readiness Checks using the Upgrade
Tool
14 5/8/2017
7
• Several things must also be considered for a successful Migration
• Valid Modules are CPM (C200), FIM, IOLM, C300, and FIM4/FIM8
• Select the Primary to commence Controller Migration
• In RCP (Redundant Chassis Pair) the Controller Migration Wizard
identifies associated components such as RMs, CNI Modules, FTEBs
and any Remote Modules
• Migrated components maintain control during Migration Process
• On-Process Migration leverages the redundancy of the controller
• Controller Migration Wizard automatically updates Firmware
• The Control Builder Application should be the only application running
on the computer when Migrating Controllers
15 5/8/2017
Controller Migration Wizard

• The Controller Migration Wizard may need to be run multiple times for
the same controller
– For example: For a Redundant Controller with Remote IO, you may run an
On- Process migration of the Redundant Controller chassis, and then run the
Controller Migration Wizard to perform an Off-Process migration of the
controllers associated Remote IO
• Only Redundant Controllers can be Migrated On-process
• NTools and CTools are not replaced by the Migration Wizard for
migrating existing control components
– Use NTools and CTools for updating firmware for new or replacement
components
• Red:- unknown firmware version
• Yellow:- module type is not recognized
• Cyan:- F/W is newer than the most recent
16 5/8/2017
8
Controller Checks
• This screen shows the Controller Migration Checks from the Readiness
Check Menu
• Correct any errors before starting the migration or the controllers will
abort the Migration. Information concerning errors contained in EMUG
17 5/8/2017
• Controller Migration must be started from Control Builder running on a
Server. On a Redundant Server System, it must be started from Server B
• In Configuration Studio:
– Select a Server and CONTROL STRATEGY in the Tree View
– Select Configure Process Control Strategies from the task list to launch
Control Builder
– Log on to Control Builder with Engineering (ENGR) Security Permissions
– In the Control Builder Monitor/Assignment tab, select the module to be

Migrated
18 5/8/2017
9
• Choose Controller>Migrate… to start the Controller Migration Wizard
19 5/8/2017
• Confirmation message box is displayed click Yes. Click NEXT on the Welcome
dialog box
• Select the Release for Migration:

– Migrate Components to the Latest release
• For example: If the Experion Servers have been Migrated to R500.x, use this
option to Migrate R31x.x/R400.x/R410.x/R43x.x Controller to R500.x Firmware
– Migrate Components to Latest Service Pack
• This will Migrate the Controller to the latest service pack or patch available for their
current release. You cannot use a service pack in a chassis where the CPM is
Migrated to R500.1, but the FIM is using R31x.x/R400.x/R410.x/R43x.x Firmware

– The wizard collects data about each component to determine if the component is
mismatched and requires Migration
20 5/8/2017
10
• Select the On-Process Migration of All Components in the Redundant
Chassis Pair check box and select Next
• Review the list of components to be On-process Migrated
• Click Yes to start the migration. The Wizard then performs the following:
– Creates a Checkpoint. This only applies to C200 and C300s
– Migrates selected components
• Click Finish
• Rerun the Controller Migration Wizard to check for any associated IO
Modules that still need to be Migrated
21 5/8/2017
• The Wizard indicates the following process steps:
– Updating Components in Secondary Chassis
– Performing Synchronization and Switchover of Redundant Chassis Pair
– Updating Components in New Secondary Chassis
– Performing Synchronization of Redundant Chassis Pair
– On Process Migration complete
– Once the migration is complete, a summary of all completed component
updates is displayed
– Click Finish
– Rerun the Wizard or use NTools / CTools to determine if there are any
associated I/O modules that needs migration
22 5/8/2017
11
Describe Freeze and Switchover
Migrate Controllers Copyright © 2017 Honeywell International Inc. Describe Freeze and Switchover
23 5/8/2017
Freeze and Switchover

• While performing Controller On-process Migration, controllers on
different firmware versions are synchronized using Indirect
Synchronization
• Performing C200/C200E/C300 OPM that forces Indirect Synchronization

when the Primary & Secondary Controllers have identical firmware
versions and is referred to as Freeze and Switchover
– Used to De-fragment the C300 Controller Memory that is used by CAB
programs once the CAB programs are deleted
– Can be used to upgrade the Custom CCLs without migrating the server or
modifying the ver_rev.txt File
• It is supported only for Redundant C200,C200E, and C300 Controllers
24 5/8/2017
12
Freeze and Switchover
• Freeze and Switchover Process of controller’s has the following
sequence of steps
– Rebuild the Checkpoint
– Disable Synchronization between the Controllers
– Restore the Checkpoint on Secondary Controller
– Perform Indirect Synchronization between the Controllers
• Transfers only Dynamic State Data from Primary Controller to
Secondary Controller
• De-fragments the Controller Memory (In case of C300 Controller)
– Switchover between Two Controllers
• Secondary Controller becomes the New Primary Controller and the
Primary Controller becomes the New Secondary Controller
– Synchronize the Two Controllers
25 5/8/2017
Freeze and Switchover - Wizard

• Open Control Builder
• Right click on the Redundant C200/C200E/C300 Controller in the
Monitoring Window and Select Freeze and Switchover
26 5/8/2017
13
• Message Window is displayed for confirmation to proceed with Freeze
and Switchover. Click Yes to continue
– This will invoke the Freeze and Switchover Wizard
27 5/8/2017

• Welcome Screen appears. Click Next to continue
28 5/8/2017
14
• Wizard collects the information of the selected component and identifies
the components associated with the object selected for Freeze and
Switchover
• List of Components is displayed. Click Next to continue
29 5/8/2017

• Confirmation Message box is displayed. Click Yes to continue
• Checkpoint Rebuild. Click Next to continue
30 5/8/2017
15
• Freeze and Switchover Process begins
31 5/8/2017

• After successful completion, the Completion Screen appears
• Click Finish to close the Wizard
32 5/8/2017
16
Describe Spare Parts Migration
Migrate Controllers Copyright © 2017 Honeywell International Inc. Describe Spare Parts Migration
33 5/8/2017
Spare Part Migration

• Migration of Spare Parts connected to the Local Chassis and Remote
Chassis of C200/C200E Controllers is possible
• Spare Parts are the I/O Modules connected to the Local or Remote
Chassis but not configured in Control Builder
• Can be used to Migrate the Spare Parts from R400 to further releases
• For Non-redundant C200/C200E, Spare Parts connected to both Main

and Remote Chassis will be Migrated
• For Redundant C200/C200E, Spare Parts connected to Remote Chassis

will be Migrated
34 5/8/2017
17
Configurations Supporting Spare Parts Migration
• Redundant C200/C200E with Spare Parts connected to Remote Chassis
– At least one I/O Module from Remote Chassis must be configured in Control
Builder
• Non-redundant C200/C200E with Spare Parts connected to Local Chassis

and Remote Chassis
– For Remote Chassis, at least one I/O Module must be configured in Control
Builder
35 5/8/2017
Naming Convention for Spare Parts

• Spare Parts Connected to Local Chassis
$FTEB_23_ TC_OAV081_10
Name Starts with $ Symbol

Module Type Slot No. of Module
FTEB/CNI Index# Connected to
For e.g. FTEB_09/CNI_09 Chassis
• Spare Parts Connected to Remote Chassis

$FTEB_23_ 05_06_TC-OAV081_10
Name Starts with $ Symbol Slot no. of Module

Connected to Chassis
FTEB/CNI Index#
For e.g. FTEB_09/CNI_09 Module Type
Local Chassis Remote Chassis

CNI Index CNI Index
Number(0-99) Number(0-99)
36 5/8/2017
18
Spare Parts Migration
• Open Control Builder
• Right click on the C200/C200E Controller in the Monitoring Window and
Select Migrate
37 5/8/2017

• Confirmation Message box appears. Click Yes to continue
• Welcome Message is displayed. Click Next
38 5/8/2017
19
• Select the Release or Point Release version and continue to the
Available Migration Options page
39 5/8/2017

• Migration Wizard gathers information and displays a list of available
Migration Options
• Select Off-Process Migration Spare Parts in the Local or Remote
Chassis. Click Next
40 5/8/2017
20
• List of Modules which needs migration appears
Modules in Local
Chassis
Verify the List. Click

Select the Components to
Next
be Migrated. Click Next
41 5/8/2017

• Confirmation Check Box appears. Click Yes
• Migration Wizard creates a Checkpoint for the Controller
Click Next to Proceed
42 5/8/2017
21
• Status of the Migration Process can be observed
• Migration Completed’ page is displayed on completing the Migration
Click Finish to
Close the Wizard
43 5/8/2017
44
22
Canceling (Aborting) Migration
Migrate Server B and Abort Migration and Go to Old ReleaseCopyright © 2017 Honeywell International Inc. Canceling (Aborting) Migration
1 5/8/2017
Aborting Migration
• Be aware that after reaching certain points in the migration process, if
the migration fails, the only method of recovery is to reload the previous
image from the ghost image created during the Pre-migration Checklist
• The Migration Wizard, will prompt you at locations, that the Migration
can be restarted without Re-imaging from the previous version
• The only method of recovery for the Controller Migration is to revert back
to a previous version of the Controller
Migrate Server B and Abort Migration and Go to Old ReleaseCopyright © 2017 Honeywell International Inc. Canceling (Aborting) Migration
2 5/8/2017
1

Migration of Domain Controller Does Not
Affect Migration
Migrate Domain Controller Copyright © 2017 Honeywell International Inc. Migration of Domain Controller Does Not Affect Migration
1 5/8/2017
Domain Controller in an Experion System

• Domain Controller (Server), used in an Experion System, operates as an
Independent Node and is migrated separately
• Domain Controller, used in an Experion System, can operate with either
Windows Server 2008 R2, Microsoft Windows Server 2012, Microsoft
Windows Server 2012 R2 or Microsoft Windows Server 2016 operating
system installed
Domain Controller Experion Server Releases
Operating System
R400.X R410 R430 R431 R500
Windows 2003 Supported Supported Supported Supported
Windows 2008 SP2 Supported Supported Supported Supported
(32 or 64bit)
Windows 2008R2 Supported Supported Supported Supported Supported
Windows 2012 Supported Supported Supported
Windows 2012 R2 Supported Supported
Windows 2016 Supported
2 5/8/2017
1
Interoperability - Domain Controller in an Experion System
• If you are using Windows Server 2008 R2 as the Domain Controller
Operating System and choose to upgrade the Operating System to
Windows Server 2016
– Use the procedure in the Windows Domain Implementation Guide for
Windows Server 2016 EPDOC-X472-en-A.pdf, Chapter 6
• If you choose to upgrade your Domain Controller Operating System to

Windows Server 2012
– Use the procedure in the Windows Domain Implementation Guide for
Windows Server 2012, EPDOC-X263-en.pdf, Chapter 7 (from 2008R2)
• After the Operating System Upgrade is complete, install the R500.x

Experion High Security Package on the Domain Controller
3 5/8/2017
Domain Controller Considerations

• Domain Controllers used in Experion
– In order to establish the link to the new domain groups needed for R500.x,
you must load the new R500.x High Security Package
– Old domain groups remain with the new domain groups appended
4 5/8/2017
2
Optional Packages Considerations
• Optional Features are dependent of the Domain Controller operating
System
– R500 packages can only be installed on Windows 2008 R2 Server or
Windows 2012 Server or Windows 2012 R2 Server or Windows 2016 OS
– For Domain Controller compatibility with Experion, see table below
R311.X R400.X R410 R430 R431 R500

Windows 2003 Supporte
d
Windows 2008 SP2 Supported
(32 or 64bit)
Windows 2008R2 Supported Supporte Supported Supported
d
Windows 2012 Supporte Supported Supported
d
Windows 2012 R2 Supported Supported
Windows 2016 Supported
5 5/8/2017
6
3

Topic: Migrate Domain Controller
Contents
(E) Verify Completeness of Experion Installation .................................................................................. 3
(E) Migrate Domain Controller ............................................................................................................... 5
(E) Run Link Domain Groups ................................................................................................................ 7
(E) Restoring the Autocheckpoint Task Scheduling .............................................................................. 9
(E) Installing Diagnostic Studio on Server and Client Nodes ..............................................................11
(E) Installing PDF Collection ................................................................................................................13



In this lab, you will verify the completeness of Experion installation. Perform these steps on all the
migrated nodes.
 Step Action
To Verify Completeness of Experion Installation
1 Using Notepad, open the ProductVersion.txt file from the path

C:\Program Files(X86)\Honeywell\Experion PKS
2 Verify the ProductVersion.txt for the following:

+Experion PKS R500.1<Node Name> install completed on MM/DD/YYYY HH:MM:SS
AM/PM
Installation is successful if the above line is present
ATTENTION
Future Patch installation may fail if you realign the drive letter after
Experion installation



In this lab, you will remove the R431 version of the Domain Controller Package and install R500
Domain Controller Package retaining the Operating System
 Step Action
Uninstall R431 DC Package
1 Logon on to Domain Controller Node with the Domain Administrative Privileges, in class
as Student
2 Refer to the procedure in the guide generated by the Upgrade Tool to uninstall the DC
Package
Topic Post-Migration Tasks
Section Installing the Domain Controller Package
Subsection To Remove the Domain Controller Package
ATTENTION
Step 3 If you are not able to see the Honeywell Security Model-
Domain Controller program then run below steps
1. Open the Command Prompt.
2. Change the directory to
PKS\Install
3. Run HWINST_MAINT.exe /u
4. Click OK on the HWINST_MAINT.exe Message Box
Install R500 DC Package
3 Refer to the procedure in the guide generated by the Upgrade Tool to Install the DC
Package
Topic Post-Migration Tasks
Section Installing the Domain Controller Package
Subsection To Install the Domain Controller Package
ATTENTION
Step 1 Browse and open D_EID1 folder on the Root of ESIS

to 3



In this lab, you will run the Link Domain Groups. Perform the below steps on all nodes in the
domain
 Step Action
Run the Link Domain Groups
1 Logon on to node with Domain administrative privileges, in class as Student
2 Refer to the procedure in the guide generated by the Upgrade Tool to run the Link
Domain Group
Topic MIGRATING AN EXPERION NODE AND INSTALLING THE
OPERATING SYSTEM
ATTENTION
Step 1 Skip this step. Domain Controller package is updated.

Step 2 Choose Start > Honeywell Experion Tools > All
Honeywell Tools >System Management and then
right click "Link Domain Groups" run as Administrator
Step 6 In Class Sign Out and Sign In
ATTENTION
For Class :- Ignore the Get Update Prompt by

Windows, Click on get update and close the update
Window



In this lab, you will restore the autocheckpoint task schedule
 Step Action
Restore Autocheckpoint Task Schedule
1 Refer to the procedure in the guide generated by the Upgrade Tool, to restore
autocheckpoint task schedule
Topic Post-migration tasks
Section Restoring the autocheckpoint task scheduling
Subsection To restore the auto checkpoint task schedule


(E) Installing Diagnostic Studio on Server and Client Nodes

In this lab, you will install Diagnostic Studio on server and client nodes
 Step Action
Installing Diagnostic Studio on Server and Client Nodes
1 Refer to the procedure in the guide generated by the Upgrade Tool, to install diagnostic
studio
Section Installing Diagnostic Studio on server and client nodes
Subsection To start migration application for ESIS based migration from a
Network Share
Subsection To continue with the migration application



In this lab, you will install PDF Collection
 Step Action
Installing PDF Collection
1 Refer to the procedure in the guide generated by the Upgrade Tool, to install PDF
collection
Section Installing PDF Collection
Subsection Installing Experion PDF collection
ATTENTION
PDF Collection is already installed as a part of

Migration, Install Adobe Reader from
ESISR500Rev4\D_PDF\Adobe Reader\AR 11.0.0
If not already installed.


Splitting and Merging EMDB Procedures
EMDB Merging and Splitting Copyright © 2017 Honeywell International Inc. Splitting and Merging EMDB Procedures
1 5/8/2017
Big Picture
• Merge or Split EMDBs
System 1 System 1
EMDB EMDB
ERDB ERDB
RTDB Merge RTDB
DSA Split DSA
EMDB
ERDB ERDB ERDB ERDB
RTDB RTDB RTDB RTDB
System 2
2 5/8/2017
1
Review – Contents of the EMDB
• System Model (Servers)
• Asset Model
• Alarm Group Model
• Network Model (Network Equipment)
EMDB1
Servers
Assets
Alarm Groups
Network Equipment
Merged EMDB1
Servers
Assets
Alarm Groups
EMDB2 Network Equipment
Servers
Assets
Alarm Groups
Network Equipment
3 5/8/2017
Merge (or Move) Procedure Overview

1 Activate (Install) EMDB on Server (if not already installed on the desired server)
2 Backup EMDBs Using DB Admin Tasks
3 Resolve duplicate names in Models of the EMDBs (includes “external” Servers)
4 Export System, Asset, and Alarm Group Models from old EMDB(s)
5 Import Models into Master (or new) EMDB
6 Inactivate (remove) EMDB from old EMDB Server(s)
7 Manually Build/Modify Network Tree
8 Load New EMDB Models
3
Student1 2
1
EMDB
2 5
6
EMDB 8
ERDB
4 7
ERDB RTDB
RTDB
ERDB
RTDB
Student2
4 5/8/2017
2
Activate (Install) EMDB on Server
• Only necessary if not installed as part of Server Installation
• Execute:
– C:\Program Files (x86)\Honeywell\Experion PKS\Utilities\EPKS_Modify\EPKS_Modify.exe
• Default Installation Path. This will be different if Custom Installation Path is selected
EPKS_Modify Server Installation
2
4
SAM mngr 5
5 5/8/2017
Backup EMDBs Before Merging or Splitting

• Configuration Studio > Administer the System Data Base > EMDB Admin Tasks
Must be stored locally.

Trying to store to a
mapped network drive
will generate an error.
6 5/8/2017
3
Resolve Duplicate Names in Models of the EMDBs
• Tag Names and Full Item Names must be “unique” within each Model
EMDB1
Tag Name Full Item Name
T1 Assets / Tank1 T2 (& T3) will generate
T2 Assets / Tank2 an error during Merged EMDB1
merge (but will work)
T3 Assets / Tank3 Tag Name Full Item Name
T1 Assets / Tank1
T2 Assets / Tank2
Merge 2 T3 Assets / Tank3
T4 Assets / Tank4
EMDB2 (modified)
T2 Assets / Tank2
T3 Assets / Tank3
T4 Assets / Tank4 I prefer the term “consistent” rather than “unique”.
After the “resolve,” the following item is consistent
1 from EMDB1 to EMDB2, but it is not unique:
EMDB2 (original) Tag Name = T2 ItemName = Assets / Tank2
Tag Name Full Item Name Consistent & Unique:

T2 Assets / Tank2A Tag Name = T1 ItemName = Assets / Tank1
T3A Assets / Tank3
T4 Assets / Tank4
7 5/8/2017
Results of Merging With Duplicate Tag or Item Names
This will generate

an error during
merge (but will work)
EMDB2 EMDB1 Merged EMDB1

Tag Name Full Item Name Tag Name Full Item Name Tag Name Full Item Name
T1 Assets / Tank1 T1 Assets / Tank1 T1 Assets / Tank1
Merged EMDB1
EMDB2 EMDB1
Tag Name Full Item Name Tag Name Full Item Name T2 Assets / Tank2
T2 Assets / Tank2A T2 Assets / Tank2 OR
(if Overwrite) Assets /Tank2A

T3A Assets / Tank3 T3 Assets / Tank3 T3A Assets /Tank3_1

T5 Assets / Tank5 T4 Assets / Tank4 T5 Assets / Tank5
8 5/8/2017
4
Generate Reports to Find Inconsistent Names
• Config Studio > Configure Assets; File > Reports; Export
• Config Studio > Configure Alarm Groups; File > Reports; Export
• Select Format – CSV (Comma-separated Values) Generate Asset and
• Sort Alarm Group reports
for each EMDB Server,
– 1st Tag Name, 2nd Full Item Name then compare the
• Manually compare Reports.
9 5/8/2017
Update References to Assets (or Full Item Names)

• When renaming an asset (or the item name), references to the asset (or
full item name) needs to be updated
– Alarm Groups, Points, Displays, Scripts, Applications
– Children Assets will also be affected
• This could be a significant amount of work
EMDB2 (modified)
T2 Assets / Tank2
T3 Assets / Tank3
T4 Assets / Tank4
EMDB2 (original)
T2 Assets / Tank2A
T3A Assets / Tank3
T4 Assets / Tank4
10 5/8/2017
5
Modify Point Asset Assignment
• When the Tag Name of the
asset is changed from T3A to
Change Tag Name T3, points assigned to T3A will
From: T3A To: T3 be “assigned” to Unassigned
Items
– Changing the Item Name does
not require tag rebuild (point is
not put in Unassigned Items)
Modify Point
& Download
11 5/8/2017
Identify Items Needing Modification for Asset Change

• Config Studio > Determine where an object is used in the System
• Results are shown on Tabs
– Number of references shown on the tab
After Merging the two

EMDBs, there will be two
Sinewave2 Tags:
Server1P:Sinewave2 &
Server2P:Sinewave2
Both will be assigned to T2.
Normally, this is not allowed.
12 5/8/2017
6
Remove Duplicate Server(s) From EMDBs
• Remove the Servers which currently are part of another System, but will
be added to the Merged System
– These will be defined as External to System (in the Master EMDB)
EMDB1 EMDB1
Student1
Server1P
EMDB
ERDB
RTD
B
EMDB2 EMDB2
Server2P
EMDB
ERDB
Server3P
RTD
B
ERDB
RTD
Student2 B
13 5/8/2017
Export the System, Asset, and Alarm Group Models

• Can be saved anywhere that is accessible to both the exporting Server,
and the Server which will import the file
14 5/8/2017
7
Import Models Into Master (or New) EMDB
• Ensure ALL Nodes (ex: servers) are in the Hosts file of the Master EMDB Node
• Import only the correct Model Type
– Ex: select only Asset Model(s) when importing into the merged Asset Model
• Select All is used when all of the listed models are of the Same Type
– Ex: when all Models shown are Asset Models
If Errors, they will

be shown in Import
Wndow.
15 5/8/2017
How Import Errors Are Displayed

• If there are Errors during the import, clicking the View Log button displays
the IXP_log.txt file where the errors are logged.
• If there were No Errors during the import, the display from which the
import was invoked will appear (ex: Enterprise Model Builder for Assets)
Duplicate
Assets in the
two EMDBs.
16 5/8/2017
8
Inactivate (Remove) EMDB From Old EMDB Server(s)
• C:\Program Files (x86)\Honeywell\Experion PKS\Utilities\EPKS_Modify\EPKS_Modify.exe
This is Default Path.
This will be different
Server2 if Custom Install
Path is Selected
EMDB
ERDB
Server3
RTDB
ERDB
RTDB
Student2
17 5/8/2017
Manually Build/Modify Network Tree

• Use Standard Configuration Studio Method
18 5/8/2017
9
Load New EMDB Models (Including Network Tree)
• Load All Models – Select Force Load Option
– System, Asset, Alarm Group, Network
• Loaded to RTDB of All Servers in the System
Server1P Server2P
EMDB EMDB
ERDB ERDB
RTDB RTDB
Server3P
EMDB
ERDB
Student1 RTDB
If any Duplicates or
Inconsistencies exist, it may
be necessary to load twice.
First load will Fail, Second
will be Successful.
19 5/8/2017
Alternative Method of Merging EMDBs (Not Recommended)

• Server2P and Server3P could have been added Manually (not using
Export/Import) to Server1P’s EMDB
• Assets and Alarm Groups get “migrated” by selecting Continue
• Potential Problems and possible Loss of EMDB configuration (from the
EMDB being eliminated)
– Lack of Error Handling when the Duplicate Tag Names and Full Item Names
Exist
• This is NOT the Recommended Method
20 5/8/2017
10
Split EMDB Procedure Overview
1 Plan: How will the EMDB be Distributed?
2 Backup the EMDB Using DB Admin Tasks
3 Export System, Asset, and Alarm Group Models from the EMDB
4 Activate (install) EMDB on New EMDB Server(s) – done on both A & B
5 Initialize EMDB on New EMDB Server(s)
6 Import Models into New EMDBs
7 Modify the Models on each EMDB Server (remove items for other EMDBs)
8 Manually Build/Modify Network Tree
9 Load New EMDB Models
10 Validate New Configuration
Student1 2
1
7
5 4 3 EMDB
6 8
7 EMDB 9
ERDB
8 9
ERDB RTDB
RTDB
ERDB
RTDB
Student2
21 5/8/2017
22
11

Wrap Up
Wrap Up Copyright © 2017 Honeywell International Inc. Wrap Up
1 5/8/2017
Troubleshooting
• The EMUG contains information and guidance on Clearing Errors
encountered during the Migration Process. It contains References for
Errors relating to:
– Server Migration
– Database Migration
– Cab File Migrations
– FTE Network Issues
– Controller Migrations
• It also covers instructions of the data that needs collecting for analysis in
the event of errors and in case GTAC investigation is required.
Wrap Up Copyright © 2017 Honeywell International Inc. Wrap Up
2 5/8/2017
1

Topic: Wrap Up
Contents
Wrap Up ................................................................................................................................................. 3


Wrap Up
Wrap Up
Wrap Up
Fieldbus Engineering Operations Procedures

Version: 1.07
Revision History
Rev Date Author Description of Changes Made
1.00 Raj Bandekar New
1.01
1.02
3/17/06
4/26/06
Raj Bandekar
Raj Bandekar
Helen Muth
Updated for SP2, added Rule #6
Minor Editorial changes for clarifications
Updated to reflect R300.1 applicability
1.03 5/22/06 Raj Bandekar Refined Rule 4, added new definition in “Key definitions” section
1.04 5/24/06 Raj Bandekar Comments from Internal Review. Send out for External Review
1.05 6/1/06 Raj Bandekar Added Rules 7&8. Comments from External Review
1.06 10/09/06 Raj Bandekar Comments from Marketing
1.07 10/11/06 Raj Bandekar Comments from Program Management for Release Numbering
Introduction
Following document applies to Experion Fieldbus Users except Rule 4 which applies to
other users as well.
Rule #1 applies only to Release 201 Customers who do not have Update 24
Release 210 Customer who do not have SP2
Rule #2 applies only to Release 201 Customers who do not have Update 23
Release 210 Customer who do not have Update 9 or Update 10
Rule #3 applies only to R201 Customers R210 Customers
Rule #4 applies to ALL Customers for ALL Releases Rule #5 applies only to
R201 Customers R210 Customers who do not have SP2.1
Rule #6 applied only to R210 Customers
Key definitions
Structural Changes: Generally, changes made on the CM or SCM chart. This applies to
only the Project side of the Fieldbus Configuration. Some of the typical changes are:
• Assigning and/or un-assigning Basic Blocks in CMs
• Making and/or deleting connections between basic blocks in CMs
• Adding and/or deleting basic blocks in CM
• Adding/deleting block pins
• Adding/deleting parameters on the faceplate
• Changing colors and Viewing options
Structural changes will cause a change flag (yellow triangle)

Wrap Up
Wrap Up
Parameter Changes: Changes made to Parametric Data such as Ranges, Tuning

Constants, Transducer Channels etc. Generally, these are changes made on a
Configuration Form. Changes made from the Project Side will cause Engineering
Database Changes and therefore a Change Flag (yellow triangle) will be set. Changes
made on a Monitoring Configuration Form do not cause any Engineering Database
Changes and therefore do Not Trigger a Change Flag (yellow triangle). Parameter
Connectors: Named connections between Basic Blocks that reside in Multiple CMs
Control Connection: Initializable Connections between Control Blocks e.g. RegCtl and AO
Definition Block: Basic Block that Publishes a Value
Reference Block: Basic Block that Subscribes to the Value Published by another Basic
Block.
VCR: Virtual Communication Relationship
Foundation Fieldbus™ defined Communication Channel which Manages Data Flow
between various Fieldbus Datalink Entities
Number of VCRs used by Link Side of the Fieldbus Connection
Number of VCRs used on a Physical FIM/Link can be found from the Link Form on the
Monitor Tab. The Link Form Network Management (Basic) Tab displays the Value “Num of
Currently Configured VCRs” OR “LSTCHAR.NUMCURCONFD” in the VCR List
Characteristics Box.
Every Fieldbus Control Connection between Experion Block and FF Block that use VCRs
will have one VCR on the FIM/Link side and another on the Field Device side.
This calculation shows how many VCRs are used by FIM/Link side.
Total # VCRs used by Physical FIM/Link = 2+ 2*(# of loaded FF Devices) + 2*(# of
uncommisioned FF Devices) + Wires_FFDevice_to_CPM+2*(#Wires_CPM_to_FFDevice)
Total # VCRs used by Control Builder Project Side = 2+ 2*(# of loaded FF Devices) +
(# of un-loaded FF Devices) +
Wires_FFDevice_to_CPM+2*(#Wires_CPM_to_FFDevice)
An example of #Wires_CPM_to_FFDevice would be a connection from PID.OP to
AO.CAS_IN where the PID is in Experion and AO is in FF Device.
Additional details and examples can be found in Foundation Fieldbus Integration Product
Specification Document.
DEF
Block
REF
Block
OP SP

Wrap Up
Wrap Up
Engineering Operations
Rule 1: (Not Applicable to Releases Post and including R210 SP2)
User Action: When Loading Structural Changes to CMs from Project:

• Perform ‘Load’ from Project Tree
• Perform ‘Update to Project’ from Monitor Tree
• Perform ‘Load’ From Project Tree again
A Structural Change can be detected prior to load in the following manner:

• For CM’s that have never been loaded, a Chevron is displayed next to the Strategy
in the Project Tree.
• For CM’s that have been previously loaded, run _CheckErdb.sql.cmd to
determine if a structural change has been made. A Structural Change has been
made if the following Check reports a finding on the CM :
CM's and SCMs that have Major Structure Changes

PAR 1-1J55XN addresses this issue Post and including R210 SP2
Rule 2: (Not Applicable to Releases Post and Including R210 Update9)
User Action: ‘Delete’ from Monitor Tree

Do not ‘Delete’ a CM from Monitor Tree if Fieldbus connection changes have been made
on the Project Tree.
The change can be detected prior to ‘Delete’ from Monitor Tree by running
_CheckErdb.sql.cmd. The Delete of the CM should not be performed if the following Check
reports a finding on the CM to be deleted :
CM’s that contain FF blocks with unused VCRS

Workaround: Load the CM from the Project Tree and Re-run _CheckErdb.sql.cmd. The
CM should no longer report the finding and may now be Deleted from the Monitor Tree.
This rule is needed because of a PAR 1-18XLSH. The PAR has been fixed in R201
Update 23 as well as post R210 Update 9.

Wrap Up
Wrap Up
Rule 3: (Not Applicable to Releases Post and Including R300.1)

User Action: ‘Update to Project’ of CM
Special actions may need to be taken after Update to Project of a CM if there are any
Structural Changes on the Project version of the CM prior to the Update to. If Structural
Changes have been made to Project, the Update to Project may be Performed.
When this occurs, VCR (Fieldbus Connections) may be Rendered Unavailable for Re-use
until the CM is Reloaded. This can be detected after the ‘Update to Project’ by Running
_CheckErdb.sql.cmd. Look for the following Check to report a finding on the CM that was
Updated:
CM’s that Contain FF Blocks with Unused VCRS
If the CM reports a finding, the VCRs will only be made available by a Reload of the CM:
• In the case, if the CM can be Reloaded at this time, it Should be Reloaded.
• For the case that the CM Can Not be Reloaded, it should be Planned to be
Reloaded in the Future. A possible Method to Track this is to Force a Delta Flag on
the Tree by opening from the DESC Parameter) and Saving the Change.

Wrap Up
Wrap Up
Rule 4: (Applicable to all Releases for Fieldbus and non Fieldbus

Points)
User Action: Loading Control Modules, SCMs and RCMs Involving

Parameter Connectors or Expressions
If a Configuration Change involves Deleting/Modifying Parameter Connectors or
Expressions of Loaded CMs from Project, then it is desired that Both the Definition Block
CM and Reference Block CM be Loaded in the Same Load Operation or Two Different
Load Operations.
This Rule applies to the following specific cases; however, it would be easier to Remember
to Load Both such CMs.
See the following use Cases and Scenarios where this Rule is Applicable. If none of the
following cases apply, then a Reload of Both Ends is Not Needed.
1. When the Parameter Connectors are Control Connections.
• Fieldbus Example CM1.PIDA.OP is connected to CM2.AO.CASIN. The reference
side for forward connection is CM2.PIDA.CASIN and CM1.PIDA.BACKCALCIN for
back initialization (hidden connection) Both the CMs have to be loaded from Project
if the forward connection is changed by the user
• Non Fieldbus Example CM3.PIDA.OP is connected to CM4.PIDA.SP. The reference
side for forward connection is CM4.PIDA.SP and the reference side for back
initialization connection is or CM3.PIDA.BACKCALCIN. Both the CMs have to be
loaded from Project if the forward connection is changed by the user
2. Un-assign or Delete a DEF Block from Project CM and replace this with another Block
of the Same or Different Type.
• Fieldbus Example CM1.AI.OUT is connected to CM2.DACA.P1. Replace AI Block
with AI from Same or a Different Device. Both CM1 and CM2 have to be reloaded
from Project.
• Non Fieldbus Example CM3.NUMERIC.PV is connected to CM4.DACA.P1. Replace
NUMBERIC Block with another NUMERIC. Both CM3 and CM4 have to be
Reloaded.
Note: The above examples intentionally uses the Same Name for the Replaced Block to
show that the User may assume or lose track of such a Change later. The Replaced Block
Does Not have to have the Same Name, but then this case would be obvious to the User
when they see that a Connection is Not Working.

Wrap Up
Wrap Up
3. Rename a DEF Block followed by a Reload of an already Loaded CM. In this situation
the CM containing the REF Block also needs to be loaded except when the DEF Blocks
are Fieldbus, PMIO or Series C IO Channel Blocks.
4. Un-assign a CM containing DEF Block from one Controller and Reassign it to any other
Controller including Itself. In this situation, the CM containing the REF Block also needs
to be loaded except when the DEF Blocks are Fieldbus, PMIO or Series C IO Channel
Blocks.
5. Un-assign CM containing REF Block with Control Connections from one Controller and
Reassign it to any other Controller including Iitself. In this situation, the CM containing
the DEF Block also needs to be Loaded except when the REF Blocks are Fieldbus,
PMIO or Series C IO Channel Blocks.
6. Physical Address Change (Slot Number or FTE Address) of Controller with CM

containing DEF Block followed by Load of this CM. In this situation, the CM containing
the REF Block also needs to be Loaded
7. Physical Address Change of Fieldbus Device whose Function Block is used as a DEF
Block. In this situation, the CM containing REF Block need to be Reloaded.
Rule 5: (Not Applicable to Releases Post and Including R300.1)
User Action: ‘Update to Project’ of Multiple CMs for Fieldbus Links

Using More than 50% of VCR Count.
See the Definition Section for How to Count VCRs. If #VCRs used on an FF Link are > 32,
first time Update to Project need to be Performed in Multiple Steps. For each Step, select
only as many CMs such that Total Number of VCRs used by these CMs is Less than 64-
total # of VCRs used by Control Builder on Project Side.
Control Builder provides Flexibility to Reconfigure Connections between Fieldbus Blocks
on Project Tab while they are still loaded on the Monitor Tab. Therefore, the Project Side
and Monitor Side both keep count of Used VCRs. If a User Keeps Reconfiguring
Connections on the Project Side without loading, this may Run Out of VCRs because the
combination or total for both sides exceeds the 64 max for any link. The reload of the
project side would then free up, VCRs on the monitor side, thus releasing VCRs from the
total used by both Project and Monitor.

Wrap Up
Wrap Up
Rule 6: (Not Applicable to Releases Post and Including R210 SP2.1)
User Action: Loading Control Modules

If during load of a Control Module you get “FF Schedule Exceeds Macro Cycle” error there
could be Two Situations for this.
1. The CM that is being loaded does not truly fit the Macro Cycle of the Loaded Link
Schedule. This can be seen by opening the Schedule UI on the Monitor Side and see
the available Time for unscheduled Traffic. A Minimum of 60% Time is necessary for
Unscheduled Traffic. If by adding this CM, the time available for Unscheduled Traffic is
going to get Below 60%; this is then a Legitimate Error and you could either Optimize
the Schedule if not already optimized or Increase the Macro Cycle or Delete some CMs
from the Monitoring Side of this Link.
2. If #1 is not the case, then the problem here could be that the Schedule on the
Monitoring Side got Un-optimized although it was supposed to be optimized. This could
happen because of a PAR 1-1YEA8J. The Root Cause for this is; that if Connections
between Functions Blocks in a Control Modules on the Project Side for a particular link
are modified and these CMs are not downloaded, but some other CMs from the Project
Side on the same Link are attempted to be downloaded. The Schedule Optimization
Algorithm cannot find all the necessary connections to optimize the Schedule for this
particular Link and hence Defaults to an Unoptimized Schedule.
If the User gets into the 2nd Situation, user should , run _CheckErdb.sql.cmd to determine if
a structural change (connections which is also a structural change in this case) has been
made to such CMs previous loaded. A structural change has been made if the following
Check Reports a finding on the CM :
CM's and SCMs that have major structure changes
Look for the CMs under this Link in this report and load from the Project Tree.

Wrap Up
Wrap Up
Rule 7: (Not Applicable to Releases Post and Including R210 SP2.1)

Bulk Edit should not be used to edit or Build Control Modules containing Fieldbus Blocks
with connections to Experion Blocks, if these Fieldbus Devices or Control Modules are
already loaded and when the Number of VCRs exceed 50% of the total specified for a
given Link. This happens because of PAR 1-1WT5X4
Rule 8: (Not Applicable to releases post and including R210 Update SP3)
Bulk Build and Import should not be used to Build Control Modules containing Fieldbus
Blocks with connections to Experion Blocks, if these Fieldbus Devices or Control Modules
are already loaded and when the Number of VCRs exceed 50% of the total specified
for a given Link.
This happens because of PARs 1-2JTQG1 1-2HAAON Post R210 SP3, import and Bulk
Build is prevented on loaded Tagged Objects.
For Rule 7 and Rule 8 please refer to CPN 2006-03
Information about _CheckErdb.sql.cmd
This is a Utility that could be downloaded from SSOL Web site at the following location,
Experion PKS>Software Library > opm Tools.
The ERDB Consistency Check will provide Status of the ERDB. The Check should be run
on the same node as the primary ERDB (Server B). To run the checker:
• Double Click on the _CheckErdb.sql.cmd Icon on the Desktop
Enter ‘D’ and click on Enter to Execute the DB Checks.
If Errors are detected, the output will display as follows:
When abnormalities are detected, the output is stored in c:\temp. The file has no
extension. This is an example of an Output File Name:
• _CheckErdb+02-006+PA62D- PWKS065A+ps_erdb+E773E128E0DC.ChkErdb
Information about Checks Related to this Document CM's and SCMs that have Major
Structure Changes
An Example of Output that has Detected Structural Changes:
######################################################################B
EGIN CAT 1 - ERDB INCONSISTENCY CHECKS
######################################################################
--+ CM's and SCMs that have major structure changes:
If any of the strategies listed below are to be loaded from Project
and contain FieldBus Blocks:
- Load from project tree
- Update to project
- Load from project tree again
StrategyName Project_SructRev
--------------- ----------------
08AI0158A 131071
08FA0711 131071
08FA0828 131071
08FA0829 131071
08FA0830 131071

Wrap Up
Wrap Up
An Example of Output where No Structural Changes have been Detected:

######################################################################
BEGIN CAT 1 - ERDB INCONSISTENCY CHECKS
######################################################################
…
--+ CM's and SCMs that have major structure changes: NONE
…
CM’s that Contain FF Blocks with Unused VCRS
An Example of Output that has Detected Unused VCRs:
--+ CM's that contain FF Blocks with unused VCRS:
Reload the following Control Modules to Cleanup VCRs
DO NOT Delete any of the CM's listed below from Monitor!!!
CMName LinkorResource Value ParamIndex
--------------- -------------- ---------------
08AI0158A E08FIM21 S08L2 -1 0
08AI0158A E08FIM21 S08L2 -1 1
08PI0125 E08FIM21 S08L2 -1 2
An Example of Output that has NOT Detected Unused VCRs:
--+ CM's that contain FF blocks with unused VCRS: NONE
Parameter Value found without Strategy
An Example of Output that has Detected the Anomaly:
--+ Number of Entries in the Strategy Parameter Value Table without a Strategy:
No Workaround: Contact TAC Immediately before proceeding with Configuration
SPVNoStrategy
--------------------------------------------------------------------------------
ORDERINCM - Parameter Value Exists, no Strategy Found
An Example of Output that has NOT Detected the Anomaly:
--+ Number of Entries in the Strategy Parameter Value Table without a strategy: NONE
Multi User Control Builder Considerations
Control Builder supports Multi-user Functionality, however, it should be noted that there
are some operations that are restricted.
Specifically, loads should only be carried out from a single machine at a time. This can be
achieved by nominating a Load Machine, and only allowing loads from that machine,
thereby ensuring that two machines will not load simultaneously. Additionally, if a load or a
delete is carried out at the same time as server database modifications are in progress,
then these operations may fail, displaying related error messages.
Examples of such errors include:
• Database Modification in Progress, Try Again Later
• Point Build Error
In Extreme Cases, these Errors may cause the Control Builder to Stop Functioning. If this
happens, you should Restart the Control Builder and Reload the Server Points to ensure
that the changes take effect. Data should not be affected.
Also check for Locks using DB Admin Tool. If all Control Builders are shut down and you
still see Locks, clear Locks before continuing.

Wrap Up
Wrap Up

Topic: Migration Checklists
Contents
(E) Prepare Premigration Checklist ....................................................................................................... 3
(E) Prepare Migrate Server B Checklist ................................................................................................ 7
(E) Prepare Migrate Server A Checklist ................................................................................................ 9
(E) Prepare Migrate Console Station Checklist ...................................................................................11
(E) Prepare Post-Migration Checklist ..................................................................................................13
(E) Prepare Controller Migratation Checklist .......................................................................................15
(E) Prepare Virtualization Checklist .....................................................................................................17


Migration Checklists

are the pre migration steps you need to perform before starting the migration
 Step Action
1 Refer the Pre migration task section of the guide generated by Upgrade Tool and mark
Verify Windows mngr account password

Verify availability of latest Patches
Verify the CD and DVD drives

Change the default password for OneWireless
Verify the communication network
Verify the system hardware
Verify software versions of TPN, TPS, and

Common Components
Prepare localized systems for migration

Prepare a system with custom server
applications for migration
Removing phantom devices
Verify the status of Experion Services
Verify primary disk partition
Verify the base IP Address
Verify the default gateway
Proceed with OneWireless migration
Obtain the latest MRT data files
Verify server readiness for migration

Verify controller readiness for migration

 Step Action
2

Address performance issues
Perform an upload with contents
Perform an update to project

Qualify Custom CCLs
Verify router configuration

Perform system backup
Run CheckDisk utility
Calculate the disk space

Verify license key
Record LCN Parameters

Record NTP settings
Stop System Management services

Verify and Disable ERDB Replication
Verify and Disable EMDB Replication
Disabling File Replication
Save and Disable File Backup
Record custom local user groups and accounts


 Step Action
3
Choose the source for Experion migration

(ESIS/non-ESIS)
Verify the time and time zone settings
Verify Honeywell Remote Peripheral Solution

patches
Considerations for systems with Matrox QID”
Considerations for systems with nVIDIA Quadro

NVS 450
Prepare LIOM software for a migration
Activate On-process Migration



In this lab, you will prepare the checklist for Server B migration. The items in the checklist are the
migration steps you need to perform during Server B migration
 Step Action
1 Refer the Migrate Server B on-process section of the guide generated by Upgrade Tool
and mark the tasks applicable.
Task Server B
Considerations before migrating Server B

Close the Windows applications
Disable the antivirus software
Check/remove the Terminal Server

service/services
Configure the Internet Explorer security
Update the Experion PKS System Initialization

utility (DVD-based migration)
Choose the migration method
Install and restore RSLinx Classic settings
Proceed with on-process migration
Install the Microsoft security updates
Reinstall antivirus software
Upgrade to the latest TPN release
Configure Enhanced TPS Node (ETN) settings
Reinstall software applications that are not

migrated
Restore localized application settings
Local Windows groups and local user accounts
Defragment the hard disk
Set up time synchronization
Add Experion standard groups to the operator

account
Update custom setup and toolbar files
Update display files

 Step Action
2
Task Server B
Callout conversion process

Check the Server B log files
Migrate the database
Remove SQL Server 2005 backward compatibility

Update the Quick Builder database
BOOTP service
Rebuild checkpoint files

Troubleshoot Server B migration issues
Considerations after Server B migration

Connect Console Stations on systems using FTE
community point


In this lab, you will prepare the checklist for Server A migration. The items in the checklist are the
migration steps you need to perform during Server A migration
 Step Action
1 Refer the Migrate Server A on-process section of the guide generated by Upgrade Tool
and mark the tasks applicable.
Task Server A
Considerations before migrating Server A

Enable OPC Integrator groups, SCADA channels
script engines on Server B
Migrate remaining Flex Stations
Migrate remaining Console Stations

Check/remove the Terminal Server

service/services

Install and restore RSLinx Classic settings

Proceed with on-process migration

migrated
Local Windows groups and local user accounts

 Step Action
2
Task Server A

account
Synchronize the servers
Enable ERDB replication

Enable EMDB replication
Enable file replication
Enable file backup (flbkup.def)
Rebuild checkpoint files
Load the Asset and Alarm Group models
Change Server A to primary


In this lab, you will prepare the checklist for Console Station migration. The items in the checklist
are the migration steps you need to perform during Console Station migration
Step Action
3 Refer the Migrate Console Stations on-process section of the guide generated by
Upgrade Tool and mark the tasks applicable.
Task Cstn

Disable the on-board audio controller



migrated

account
Update display files
Callout conversion process
Update Electronic Signatures after migration

Disable TPS system alarms
Perform migration and compatibility checks

during dual primary state
Considerations after migrating a Console Station


are the post migration steps you need to perform after the migration
 Step Action
4 Refer the Post migration task section of the guide generated by Upgrade Tool and mark
Verify completeness of Experion installation

Set up the NTP server
Reconfiguring ethernet, FTE networks after

migration
Start System Management services
Migrate ACE, SCE and/or eServer nodes
Upgrade Windows domain controller
Install the domain controller package
Reestablish Engineering user groups
Restore the autocheckpoint task scheduling
Update LIOM software for off-process migration
Update and migrating LIOM software for on-

process migration
Install Diagnostic Studio on server and client
nodes
Restore device help content
Configure secure communication settings
Install PDF Collection



In this lab, you will prepare the checklist for Controller Pre migration. The items in the checklist are
the migration steps you need to perform before migrating the controller
 Step Action
1 Refer the Pre-migration checks for controller migration section of the guide generated by
Upgrade Tool and mark the tasks applicable.
Task Done?
Ensure Server A and Server B are migrated

Verify BOOTP server configuration
Verify Redundant Chassis Pair (RCP) or

Redundant Controllers are Synchronized
Verify RCP contains only CCN013/CCR013 or

CCN014/CCR014 CNI modules for migration
Verify CNI module is running on latest firmware
Verify ControlNet communication paths with

FIMs or HART I/O modules only contain
CCN013/CCR013 or CCN014/CCR014 CNI
modules.
Create CCL backup and record the path name

Verify that all peer-to-peer references in the
controller are working as expected before
starting the migration.
Verify that there are no active locks in the

Engineering Repository DataBase (ERDB).
Verify that Auto Synchronization State of each
Redundancy module is set to Conditional.
Verify CF9 control firewall is running on latest

firmware before migrating Series C hardware
Verify latest version of the ERDB Consistency
Checker tool is used
Perform a manual checkpoint save for each

controller, prior to start of migration.
Stop any checkpoint scheduling tasks, which
apply to the controller that is to be migrated.

 Step Action
2
Task Done?
Make any required modifications to the control

strategies
Run Upgrade Tool / MRT to verify controller
readiness
Perform an upload with contents.


In this lab, you will prepare the checklist to migrate Experion Systems in Virtualized Environment.
The items in the checklist are the steps you need to perform to Migrate Physical / Virtual Experion
Systems to Virtualized Environment
 Step Action
1 To prepare the virtualized environment refer the Migrating Experion systems in a

Virtualized Environment (Section 12) of the On process migration guide (EPDOC-X106-
en-5001A) and mark the tasks applicable.
Task Done?
Implement new virtual infrastructure
Prepare the ESIS virtual hard disk
Preparing the utility virtual hard disk
Maintenance of ESIS and utility virtual hard disks
Choosing the migration method for moving to

virtualized environment

 Step Action
2 To Migrate Physical Experion Systems to Virtual, refer the Migrating Physical Experion
systems to a virtualized environment (Section 12.6) of the On process migration guide
(EPDOC-X106-en-5001A) and mark the tasks applicable.
Task Done?
Start the migration

Create the new Experion virtual machine for the
node type being migrated
Connect a virtual machine to networks
Connect a USB device
Prepare the virtual machine and copy ESIS virtual

hard disks
Prepare the configuration files device for
connection to virtual machine
Power on the new virtual machine
Install the operating system using Experion PKS

System Initialization media
Completing the Experion node migration

 Step Action
3 To Migrate Virtual Experion Systems to Virtual, refer the Migrating Virtual Experion
systems within a virtualized environment (Section 12.7) of the On process migration
guide (EPDOC-X106-en-5001A) and mark the tasks applicable.
Task Done?
Start the migration

Create the new Experion virtual machine for the
node type being migrated
Prepare the virtual machine and copy ESIS virtual
hard disks
Prepare the configuration files device for
connection to virtual machine
Power on the new virtual machine
Install the operating system using Experion PKS
System Initialization media
Completing the Experion node migration


Describe ACE Rapid Restart
ACE Rapid Restart (Reference Only) Copyright © 2017 Honeywell International Inc. Describe ACE Rapid Restart
1 5/8/2017
Introduction
• In this module we will learn about the Experion R500 ACE Rapid
Restart Enhancement
– ACE Network Configurator Tool
– Upgrade Tool – Generate Cutover Instructions after Cutover Tool
Preparation
– ACE Cutover Tool
• This feature can be used to migrate ACE from R500 to post R500
release
• In R500 this feature can be used while applying windows upgrades and
EPKS patches
This functionality
supports only
from the Experion
R500 onwards
2 5/8/2017
1
Abbreviations used in the module
ACE – Application Control Environment
FTE – Fault Tolerant Ethernet
FIP – Floating IP
ACE RR – ACE Rapid Restart
CAB – Custom Algorithm Block
3 5/8/2017
Prior to R500
• ACE being a non-redundant node, upgrading this node requires shutting
down
– ACE downtime leads to loss of the supervisory control functions till the time
ACE is brought back online.
• Constraints during ACE upgrade process
– Loss of view to the ACE node
– Loss of Control/advanced control
– Loss or disruption to L3 applications and its functionality.
– Control Strategies depending on the ACE gets interrupted
– Cascade control across clusters using ICG (Inter Cluster Gateway) gets
interrupted.
– Complex manual operations are required to bring the supervisory functions
under manual control shed
• ACE upgrade process includes
– Microsoft Patch updates
– Experion software upgrade both point release and general release
• ON-Process Migration is not supported
4 5/8/2017
2
In R500
• ACE Rapid Restart is a Licensed Option in Experion PKS
• ACE Supports ON – Process Migration from R500 to future
release/patches. ACE upgrade includes
– Microsoft Patch updates
– Experion software upgrade both point release and general release
• All functions are supported for cutover in ACE node
• ACE Rapid Restart is not supported for ACE- T Nodes
• Creates a temporary ACE node, used during migration or upgrades
– Can be a Physical or Virtual machine
• Upgrade of ACE nodes requires three steps
– Prepare for Cutover – Upgrade Tool
– Create the Backup ACE node
– Perform Cutover to the Backup ACE node
5 5/8/2017
Pre-Requisites for ACE Migration

ACE Cutover must be performed only if the following operations are
completed:
• The backup ACE node used for ACE cutover is created and configured
• The Backup ACE node used for cutover is up to date
• The network configurations in the ACE node used for ACE cutover are
completed
• The readiness checks are completed
• The ERDB/Controller inconsistencies is checked on all controllers
• To run upload with contents for all the controllers.
• Ensure that no auto saving is occurring, and stop all scheduled auto
checkpoint tasks for the selected controller
6 5/8/2017
3
Supported scenarios for creating backup ACE node
• The following scenarios are supported for creating the backup ACE
nodes:
• Create a new backup ACE node to the desired patch level using the
clean installation
• Backup from a physical ACE machine and restore to a physical ACE
machine
• Backup from a physical ACE machine and restore to a virtual ACE
machine
• Backup from a virtual ACE machine and restore to a physical ACE
machine
• Backup from a virtual ACE machine and restore to a virtual ACE
machine
After restoring the
Machine, use NCT
tool to rename the
system and change
the IP address
7 5/8/2017
Steps for ACE Rapid Restart

• Step 1 - Prepare ACE nodes for Cutover – Upgrade Tool
– Run the Upgrade tool for the Pre-Migration checks in the ServerB
• Step 2 - Create the Backup ACE node
– Install new ACE node with all necessary upgrades
– Make the existing ACE Machine as Primary and clean installed/cloned ACE
node as Backup using the “ACE Network Configurator Tool”
• Step 3 - Perform Cutover to the Backup ACE node – Migration
– Run the Cutover Wizard in Control Builder in Experion Server to migrate
the ACE node to the new upgraded Backup ACE node.
8 5/8/2017
4
Introduction to Upgrade Tool
• Upgrade tool collects the General, System and Installed Honeywell
Software information of ACE node . It generates process summary which
gives General Information, General Data Collection and Readiness
Checks performed on ACE node
Primary ACE Backup ACE
Cluster ESV
9 5/8/2017
Prepare ACE nodes for Cutover – Upgrade Tool

• For Pre-Migration
checks of the
ACE node, need
to run the Prepare
ACE for Cutover
Tool from
Configuration
Studio
“Prepare ACE nodes

for Cutover” and
“Launch ACE Cutover
Guide” options
available under
“Experion PKS Cluster
Upgrade”
10 5/8/2017
5
Upgrade Tool – General information
• The Upgrade Tool
checks the upgrade
readiness of the ACE
nodes in an Experion
System
• General Information
collects data of Site and
migration specific data
from an engineer
The ACE Cutover solution

Guide provides
information about the pre-
requisites of the ACE
node before the Cutover
11 5/8/2017
Upgrade Tool – General Data Collection

• In this step, Upgrade tool collects general information, system
configuration information and the information of installed Honeywell
software
12 5/8/2017
6
Upgrade Tool - Readiness Checks
13 5/8/2017
Process Summary
14 5/8/2017
7
Process Summary
15 5/8/2017


16 5/8/2017
8
Create Backup ACE Node
• Create the Backup ACE node –
– Clean install ACE node or
– Cloning of existing ACE node and upgrade it to new Experion point release
or General release and Microsoft Security Updates
ACE ACE
“New Upgraded
ACE Machine for
Migration Purpose”
ESV
Cluster
17 5/8/2017
ACE Network Configurator Tool
ACE ACE
Cluster ESV
18 5/8/2017
9
ACE Network Configurator Tool
• This tool is used to configure the ACE node as Primary and Backup
• Configuring of ACE as Primary or Backup needs one Floating IP
• Two IP’s are required for an each ACE node
– FTE Adapter IP address : This is configured at the time of installation of the
ACE node
– Floating IP(FIP) address : This is configured in the ACE Network
Configurator Tool for Switchover purpose
If “Subnet Range Error”
appears while configuring the
Floating IP address, please
ensure that the FTE Adapter
name is “ Honeywell FTE
Adapter # 1”
Floating IP
19 5/8/2017
ACE Network Configurator Tool continued

• Configure ACE as Primary and Backup using ACE Network Configurator
tool as shown below
New ACE Node
Cluster ACE Node
FTE IP : 199.63.44.182
FTE IP : 199.63.44.180
FIP : 199.63.44.183
FIP : 199.63.44.181
Primary Primary Backup

Floating IP Floating IP Floating IP
Cluster ACE Node : ACE node under the Cluster

New ACE node: It is updated New ACE node ready for Migration
20 5/8/2017
10



21 5/8/2017
Configuration of ACE in Control Builder

• Configure ACE in Control builder by using the Floating IP of Primary
ACE
• Select the Option ACE Has Backup
Enable “ACE
Has Backup”
checkbox
Primary
Floating IP
Not the ACE
FTE Adaptor IP
Note : To perform Cutover

from Primary ACE to Backup
ACE,“ACE Has Backup”
checkbox should be enabled.
22 5/8/2017
11
Configuration of ACE in Control Builder continued
• For CAB blocks,
there is an option
to start CAB
block
automatically Atomic CAB type for ACE and
when cutover C300 start automatically after
migration (Warm Start).
happens
This functionality is supported only
for the Distributed CAB for ACE
only.
By selecting the option Distributed
CAB will run “Cold Start” after
migration completed
Enable to Start
CAB after
Cutover
23 5/8/2017
Cutover Wizard
• In Control Builder, Cutover option is available under
– Controller menu
– Right Click on ACE node in Monitoring window
• Cutover option will launch the ACE Cutover Wizard to perform ACE
cutover from Control Builder
• ACE Cutover menu option is enabled only when:
– ACE Node is Loaded and Running in Monitoring window
– ACE node is Primary (RDNROLESTATE)
– “ACE Has Backup ” option is enabled
24 5/8/2017
12
Working Functionality of Cutover Tool
• As the first step, Cutover wizard will fetch the floating IP of the backup
node automatically
• The Wizard creates the backup ACE nodes with that IP. The backup
blocks are created and loaded in control builder for temporary purpose
while switching from Primary to Backup ACE
– These temporary blocks are deleted once cutover process is completed
• Backup Blocks created while Cutover
– ACE Node
– ICG (Intercluster Gateway)
– OPCG (OPC Gateway)
• After creating the backup blocks, Checkpoint file of the ACE node gets
built
• The created Checkpoint file is restored on the backup nodes
• After Checkpoint is restored successfully, the dynamic data is
transferred
• During the dynamic data transfer the execution will freeze
• The freeze time depends on the number of blocks and the amount of the
dynamic data will be transferred
25 5/8/2017
Working Functionality of Cutover Tool

• After Dynamic data transfer, switchover (IP Swap) will happen. At the
time of Switchover, the Primary Floating IP switches to the Backup
Floating IP address to maintain the connectivity with server
• After the wizard completes the switchover and the user selects Finish
button the secondary nodes that are created will be deleted by the
wizard
26 5/8/2017
13
Procedure for ACE Migration
Cutover Wizard
Migrates the database of the Primary ACE to Backup ACE node & Cutover
Backup Blocks Creates new Database Synchronize “Floating IP
Created in Control Checkpoint File of between Primary and address
Builder Primary ACE node Backup ACE Exchanged”
ACE, OPCG, ICG
Floating IP Exchanged
Primary ACE Backup ACE
Database
At the time of Database

The reason Synchronization the ACE node
behind freezes
configuring the Cluster ESV
FIP other than
FTE IP in Control
Builder is
Primary ACE Node Backup ACE Node
Migration
FTE IP : 199.63.44.180 FTE IP : 199.63.44.182
FIP : 199.63.44.181 FIP : 199.63.44.183
27 5/8/2017
Procedure for ACE Migration

Cutover Wizard
Migrates the database of the Primary ACE to Backup ACE node & Cutover
Backup Blocks Creates new Database Synchronize “Floating IP “Cutover from
Created in Control Checkpoint File of between Primary and address Primary to
Builder Primary ACE node Backup ACE Exchanged” Backup
ACE, OPCG, ICG
Backup ACE Cutover

Primary ACE
After Cutover the Backup ACE

node can be re-used for
cutover with other ACE nodes
in cluster ESV Cluster
New Backup ACE Node New Primary ACE Node
FTE IP : 199.63.44.180 Floating IP exchanged to maintain FTE IP : 199.63.44.182

FIP : 199.63.44.183 FIP : 199.63.44.181
ACE connectivity with server
28 5/8/2017
14
ACE Cutover Wizard Process
Follow the pre-requisites for

ACE migration in Migration
user guide document before
starting the Cutover Wizard
29 5/8/2017
Cutover Wizard Process
30 5/8/2017
15
Cutover Wizard process
31 5/8/2017
32 5/8/2017
16
33 5/8/2017
34 5/8/2017
17
35 5/8/2017
36 5/8/2017
18
37 5/8/2017
Migration Sequence
• ACE supports interoperability like controller’s
• ACE migration done after the Servers migration
• For example: A cluster contains Redundant Servers, Flex, Console,
ACE & C300
Server B
Console
Flex
Server A
ACE
C300
38 5/8/2017
19
ACE Block Properties
Cutover
Role Status
Cutover History will

be populated when
Cutover wizard is
Running
Cutover Link
Status
Floating IP
of PRIMARY
ACE NODE
Partner
Floating IP
Address
39 5/8/2017
Summary
• In this module, we have learned the following things
– ACE Network Configurator tool
– Upgrade Tool
– ACE Cutover Wizard
40 5/8/2017
20
More Information
To learn more about Automation College,
view a list of global locations and available
training, visit www.automationcollege.com
or email HPSWeb@Honeywell.com
.
Honeywell
Performance Materials & Technologies
Honeywell Process Solutions
Automation College
January 2017
www.honeywellprocess.com © 2017 Honeywell International Inc.

12 Advanced On Process Migration Implemetation r500

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

12 Advanced On Process Migration Implemetation r500

Uploaded by

Copyright:

Available Formats

Automation College

Experion PKS: Advanced -

EXP-90 R500 AT/VT Student Guide

Experion, Da Vinci, IntelliMap, MXOpen, MXProLine, TotalPlant, PlantScape, TDC 3000,

Copyright © 2017 Honeywell Inc.

Honeywell International, Inc.

EXP-90 R500 (AT/VT)

Honeywell Confidential and Proprietary Page: 1 of 2 2017/05/01

Honeywell Confidential and Proprietary Page: 2 of 2 2017/05/01

Important Reference Documents

Default Path Custom Path

Custom Installation Path

Default Path Custom Path

UserA C:\ProgramData\Honeywell\ UserA D:\Experion\Data\Honeywell\

Custom Install Path Restrictions (Contd..)

• Special characters supported in folder name:

Custom Install Path Restrictions (Contd..)

• The Experion Runtime Data path cannot be a subdirectory of the

• Experion PKS Software path should not begin with:

R500 Installation Enhancements- Software Licensing

Other Platform Changes with Experion PKS R500

Experion R500 Maintenance Tool

This page intentionally left blank

Class System Architecture-In center

Experion Software EPKS Server A EPKS Server B Experion Station-TPS

Server B One ES-F One ES-C ES-CE

All ES-CE All ES-C All ES-F

eServer Server A ACE/SIM

SCADA device Control

Migrate Domain Controller

On-Process Migration (OPM)

• System migration involves two major stages:

• Understand the Concept of OPM

– OPM procedures, checklists, tools, and pre-requisites are constantly

– On-Line Support is your best source of current OPM information

Server, Controller, and Common Components

• Controller / Engineering Tools portion of Experion PKS

• Common Components of Experion PKS

• TPS Components for Experion PKS

..\Honeywell\ Data .. Files..

SQL Server Databases

Experion PKS Databases

Experion PKS Databases – Operational View

Server / Client Controller / Engineering Tools

On Process Migration On Process Migration

• Migrate Stations from Experion R431.x to Experion R500.x (General

• Migrate C200 Redundant Chassis Pair and C300 Redundant Controllers

Get latest MRT & Acknowledge Alarms

Disable ERDB & EMDB

Fix issues (if any) Disable backup defined

Secure all software * OLS Website:

On-Process Migration Flow – Experion Server and Client

Start Migrate Server B

Migrate One Client Revert to

Migrate All PASS Server B and Client FAIL

Supported Migration Path - Server/Client

• EMP: Experion Migration Planning Guide EPDOC-XX70-en-5001A

Migration Path to R500.1 OPM OFFPM Reference

• EMP: Experion Migration Planning Guide EPDOC-XX70-en-5001A

Supported Migration Path - Controller

Even though the C200 firmware is freezed at R311.

On-Process Migration Requirements

• Starting with Experion R300.1 Systems, the OPM license is combined