HONEYWELL TRACE TM DOCUMENTATION AND CHANGE MANAGEMENT SOFTWARE FOR BETTER DECISIONS. R121 Prerequisites Document

Transcription

1 HONEYWELL TRACE TM DOCUMENTATION AND CHANGE MANAGEMENT SOFTWARE FOR BETTER DECISIONS R121 Prerequisites Document

2 ABOUT THIS DOCUMENT This document is intended to help users plan a Trace installation.

3 Connected Mode - Honeywell Trace Installed at L3 and L3.5 INTERNET / INTRANET LEVEL 4 NETWORK FIREWALL L4 DOMAIN BUSINESS NETWORK L4 TRACE CLIENT LEVEL 3.5 NETWORK (DMZ) L3.5 SWITCH (DMZ) ROUTER L3.5 DOMAIN L3.5 TRACE CLIENT PHD DATABASE SERVER / SHADOW SERVER BUSINESS NETWORK L3.5 TRACE SERVER (OPTIONAL) LEVEL 3 NETWORK L3 SWITCH L3 DOMAIN L3 TRACE CLIENT PHD COLLECTOR OSIPI PROCESS NETWORK L3 TRACE SERVER FSC SPI SAFETY MANAGER L2 SWITCH YELLOW LEVEL 2 NETWORK L2 SWITCH GREEN L2 DOMAIN TRICONEX ES-C ESV (A/B) ESV-T (A/B) ES-T EXPERION CLUSTER INTEGRATED EXPERION CLUSTER

4 Connected Mode - Honeywell Trace Installed at L3 and L4 With Relay Server INTERNET / INTRANET LEVEL 4 NETWORK FIREWALL L4 DOMAIN BUSINESS NETWORK L4 TRACE CLIENT BUSINESS NETWORK L4 TRACE SERVER LEVEL 3.5 NETWORK (DMZ) L3.5 SWITCH (DMZ) ROUTER L3.5 DOMAIN L3.5 TRACE CLIENT PHD DATABASE SERVER / SHADOW SERVER RELAY SERVER (PROXY+) LEVEL 3 NETWORK L3 SWITCH L3 DOMAIN L3 TRACE CLIENT PHD COLLECTOR OSIPI PROCESS NETWORK L3 TRACE SERVER FSC SPI SAFETY MANAGER L2 SWITCH YELLOW LEVEL 2 NETWORK L2 SWITCH GREEN L2 DOMAIN TRICONEX ES-C ESV (A/B) ESV-T (A/B) ES-T EXPERION CLUSTER INTEGRATED EXPERION CLUSTER

5 Honeywell Trace Architecture Offline Mode CENTRAL OFFICE WITH OFFLINE TRACE SERVER FOR L3-L3.5 AND L3-L4 CONNECTIONS, SEE CONNECTED MODE LEVEL 3 NETWORK DOMAIN OFFLINE TRACE SERVER PACKAGE FILE IS COPIED FROM LAPTOP / PORTBALE DRIVE TRACE CLIENT PACKAGE FILE IS PHYSICALLY TRANSPORTED FROM SITE TO CENTRAL OFFICE REMOTE SITE WITH OFFLINE DATA COLLECTOR DATA COLLECTION IS DONE & PACKAGE FILE IS COPIED TO A LAPTOP / PORTBALE DRIVE LEVEL 3 NETWORK L3 SWITCH ROUTER SAFETY MANAGER L3 DOMAIN FSC OFFLINE DATA COLLECTOR * SPI PHD COLLECTOR OSIPI OFFLINE DATA COLLECTOR * L2 SWITCH YELLOW LEVEL 2 NETWORK L2 SWITCH GREEN * OFFLINE DATA COLLECTOR CAN BE AT LEVEL 2 OR LEVEL 3 L2 DOMAIN ES-C ESV (A/B) EXPERION CLUSTER ESV-T (A/B) ES-T INTEGRATED EXPERION CLUSTER TRICONEX

6 PLANNING Hardware / Software Requirements Trace Server / Offline Trace Server * Offline Data Collector Remote Node Where to install? Ready ( ) Ready ( ) Ready ( ) Ready ( ) L3 L3.5 / L4 Hardware (minimum required) For 50, 000 to 200,000 tags L3 L2 Client node of selected system Server Model PowerEdge R430 Hard Disk RAID GB X 4 Sufficient disk space to store collected data Sufficient disk space to store collected data RAM 32 GB 500 MB 500 MB CPU Processor 16 Core 2.5 MB Cache/Core Intel Xeon (2 processors) E v3 2.4GHz Virtual machine For 50,000 tags For 200,000 tags Hard Disk 500 GB 1 TB RAM 16 GB 32 GB CPU 5 Core 8 MB Cache 16 Core 2.5 MB Cache/Core Reservation 12 GB 24 GB NA NA Software (supported) Microsoft Windows Server 2016 Standard 64- bit Windows 7 (32 / 64- bit) OS Web browser Microsoft Windows Server 2012 R2 Standard 64-bit Windows 2012 Server Windows 2016 Server Minimum: Windows XP Professional SP 3 or later (32 / 64 bit) Recommended: Windows OS later than Win XP Microsoft Internet Explorer 11 Internet Explorer 11 Internet Explorer 11 Google Chrome V 50 or later Chrome V 50 or later Chrome V 50 or later * The Offline Trace Server resembles the Honeywell Trace Server in all respects except that you cannot perform data collection on it as it does not have network connectivity with remote nodes. Instead, the package created by the Offline Data Collector is uploaded to create the snapshot.

7 PLANNING USER GROUPS / USERS Do this first Person doing the installation must User groups ptwebuser Domain Run script on Domain Controller Run as Administrator Belong to Domain Admin group Run the script to create these groups. If not using the script, manually create these groups LSS-PT Engineers LSS-PT Managers LSS-PT Product admin LSS-PT Report Users LSS-PT DataCollection LSS-PT License Run the script to create this user. If not using the script, manually create this user. Workgroup Update Hosts file on Honeywell Trace Server, Remote node, and all client nodes. Belong to Local Administrators group Created by installer. (manual creation not required) Created by installer. (manual creation not required) 1. Assign domain users (if they already exist) to these groups. 2. If domain users do not exist already, create domain users (WebClientUser1, WebClientUser2, WebClientUserN) and then associate them to groups Assign domain users to one or multiple groups based on their role LSS-PT Engineers LSS-PT Managers LSS-PT Product admin LSS-PT Report Users Not Applicable Create these users manually and assign to groups Create users: WebClientUser1 WebClientUser2 WebClientUserN Assign the users you create to one or multiple groups based on the role: LSS-PT Engineers LSS-PT Managers LSS-PT Product admin LSS-PT Report Users

8 PLANNING REMOTE NODE SUPPORTED SYSTEMS & LICENSES REQUIRED System Supported Version Description License requirement Experion PKS Process Server R311.1 R400 R410 R430 R431 Flex node (You can either install a Remote Node package or Disconnected Mode. NOT both.) ES-C node Experion Server B (contains the System Performance (IAA) package only) 01 license per Experion cluster R500 R501 TPS R6xx or later ES-T node 01 license per LCN GUS node (running Windows XP SP3 or later) ESVT-B node (contains the System Performance (IAA) package only) Experion Integrated TPS R410.3 or later ES-T node ESVT-B node (contains the System Performance (IAA) package only) 01 Experion Integrated TPS license = 01 TPS + 05 ESV ATTENTION: GUS node is not supported for this system. Safety Manager R13x.x R14x.x R15x.x Safety Builder node. For manual collection, any node on which plant data is copied. 01 license per plant (not per controller) Triconex Tristation v4.6 Tristation node 01 license per controller For manual collection, any node on which plant data is copied. PHD R300 PHD Data Collector node 01 license per PHD collector R310 R320 FSC R6xx or later (on Trace R121 Patch1 or later) FSC Builder node For manual collection, any node on which plant data is copied. 01 license per controller OSIPI 2015 version ( ) OSIPI node where database is available 01 license per OSIPI database server SPI SPI 2009 SP4 HF10 SPI node 01 license Supported SPI database type is SQL Server

9 CROSS DOMAIN ACCESS ENABLE COMMUNICATION BETWEEN L3 & L3.5/L4 If installing on L3.5 Domain On the L3.5 Domain Controller, run the script provided to create groups and then add selected WebClient users to the LSSPT Application User group manually. Establish trust between L3.5 Domain Controller and L4 Domain Controller. This is to access data from L4 client nodes. Workgroup Create webclient users and them to the LSSPT Application User group manually Firewall configuration Between L3 and L3.5/L4 Open physical firewall port TCP 443 (https) If there is a Firewall between L3 Trace node & client nodes 139, 445 (for TCP) 137, 138 (for UDP) TCP 5985 (Windows XP) TCP 5986 (later versions of Windows) Update Hosts File In domain topology, to communicate between L3 node - L3.5 node Update Hosts file on L3 node with this information XX L3-5-Trace.domain.com where, XX is the IP address of the L3.5 Trace node L3-5-Trace.domain.com is the Fully Qualified Domain Name (FQDN) of the L3.5 Trace node Note that the IPs and names mentioned are examples only.

10 CROSS DOMAIN ACCESS ENABLE COMMUNICATION BETWEEN L3 & L4 USING RELAY SERVER (PROXY+) If installing on L4 Domain Install and configure Relay Server (Proxy+) node at the L3.5 level (DMZ) On L4 Domain Controller, run the script to create groups and then add selected webclient users to the LSSPT Application User group manually. Workgroup Install and configure Relay Server (Proxy+) node at L3.5 (DMZ). Firewall configuration Between L3 and L3.5/L4 Open physical firewall port TCP 443 (https) If there is a Firewall between L3 Trace node & client nodes 139, 445 (for TCP) 137, 138 (for UDP) TCP 5985 (Windows XP) TCP 5986 (later versions of Windows) Update Hosts File on the L3 and Relay Server (Proxy+) node In domain topology, to communicate between L3 node L4 node Update Hosts file on L3 node with this information YY L4-Trace.domain.com where, YY is the IP address of the Relay Server (Proxy +) L4-Trace.domain.com is the Fully Qualified Domain Name (FQDN) of the L4 Trace node On the Proxy + node XX L4-Trace.domain.com where, XX is the IP address of the L4 node L4-Trace.domain.com is the Fully Qualified Domain Name (FQDN) of the L4 Trace node Note that the IPs and names mentioned are examples only. In workgroup topology, to communicate between L3 server node in workgroup and remote nodes Trace L3 and Trace L3.5/L4 Update Hosts file On Client node, update IP address of Trace Server s IP address On Trace Server, update IP address of Remote nodes On Trace L3 server node, update IP address of the Trace L3.5 server node On Trace L3.5 server node, update IP address of the Trace L3 server node

11 SYSTEM SPECIFIC REQUIREMENTS Experion User privilege Configure temp qdb file Ensure that your Windows user account used for installation: has Local Administrator privileges on the computer belongs to a domain or workgroup and is part of the following groups: Experion DCS Admin group (applicable for domain accounts) Local Product Admin group (applicable for workgroup accounts Configure temporary qdb file for R3xx.x, R400.x and R410.x Set Display path On Experion Server B, open the Experion PKS Server Configuration Panel from the Start menu and set all display paths Configure switches (for Network View to appear in Honeywell Trace) Flex/ES-C/ES-T nodes On Experion Station where remote is installed, click Station > Connection Properties > Display tab and set all display paths RO community string configured for all switches must match the switch Read Community configured in Configuration Studio and loaded Configure SNMP in Experion server and in the switch. Top level Yellow and Green switch spanning must be configured (for yellow it is 4096 for green 8192) Optional: Add RW community string in the switch and update the same under Global Settings in the Data Collection page. On Flex/ES-C/ES-T, you can either install Remote node package or Disconnected Mode. NOT both. TPS User privilege System status Ensure that your Windows user account used for installation: has Local Administrator privileges on the computer belongs to a domain or workgroup and is part of the following groups: Experion DCS Admin group (for domain accounts) Local Product Admin group (for workgroup accounts Ensure that the LCNP status is OK checkpoints for all data owners are available on HM node communicates with Data Server Configure Honeywell File Transfer Ensure Honeywell File Transfer service is installed and is running Configure Honeywell File Transfer service with all available HMs on the network Check for LVRLOG file GUS display runtime package should be installed and running. ATTENTION: GUS Display Runtime is a separately licensed add-on feature of TPS Ensure the LVRLOG is configured and it is working. ATTENTION: Honeywell Trace Remote Node components and System Audit Tool (SAT) CAN NOT exist together on any of these nodes: Experion Flex, ESV-T, ES-C or ES-T. Uninstall SAT before installing Honeywell Trace Remote Node components on these nodes. Safety Builder Safety Builder database path If performing data collection manually: Copy the Metadata.xml file found at: <InstalledPath>\Honeywell\SafetyManager SMRxxx.x\Metadata.xml to the path where the Plant file (.CAC file) is located. PHD Users must be a part of the Product Administrators group For a PHD node to perform data collection. PHD Data Collection User must be present in PHD nodes (PHD collector, PHD shadow and/or database nodes).

12 ADDITIONAL REQUIREMENTS Configure System Time and Time Zone Configure the same System Time and Time Zone on the L3 and L3.5/L4 nodes. Changing the Time Zone after installing the Honeywell Trace application affects the functioning of the application. Passwords Ensure that the passwords you provide when installing Honeywell Trace have: A maximum of 32 characters A minimum of 8 characters (unless the password policy of your site recommends shorter passwords) At least one upper case letter At least one number At least one special character. However, the following special characters are NOT allowed / \ Server Name / IP Address prerequisites You cannot change Server Name after Trace Server installation. However, you can change the IP address of Trace Server using the Admin Console. Honeywell Process Solutions 1250 West Sam Houston Parkway South Houston, TX Honeywell House, Skimped Hill Lane Bracknell, Berkshire, England RG12 1EB UK Building #1, 555 Huanke Road, Zhangjiang Hi-Tech Industrial Park, Pudong New Area, Shanghai Honeywell Trace Prerequisites Document RevC 04/ Honeywell International Inc.