TPS Integration Basics PDF

TPS Integration Basics 29 February 2024 10:57 This module is optional and applies only to an Experion system that has been integrated with a TPS system. The Experion nodes that will be are: Experion Server TPS(ESVT) Experion Station TPS(ES-T) Before going to the module you must have experien...

TPS Integration Basics 29 February 2024 10:57 This module is optional and applies only to an Experion system that has been integrated with a TPS system. The Experion nodes that will be are: Experion Server TPS(ESVT) Experion Station TPS(ES-T) Before going to the module you must have experience with TPS system configuration. Here is an architecture diagram with the Network Interface Module (NIM). We are going to concentrate on two items: the ESVT and the ES-T, which stands for Experion Server TPS and Experion Station TPS. However, both have an LCN connection, so are both directly connected to the TPS system. The ESVT and the EST are also connected to Fault Tolerant Ethernet, and therefore, also have direct access to any C200, C300, UOC, and vUOC which is to the FTE network. The connection to a C200 is shown in this diagram. The ESVT also has access to SCADA controllers. In this diagram, you can see the architecture with the Enhanced Network Interface Module (ENIM) and the Enhanced High Performance Manager (EHPM). We are going to concentrate on the ENIM and the EHPM. An ENIM is a Fault Tolerant Ethernet based node that provides the interface between the LCN and the E U C N connected nodes like the EHPM. The EUCN is the Universal Control Network (UCN) over an Ethernet network, using FTE technology. FTE is a Honeywell patented implementation of Ethernet. In the architecture diagram, you can see two Enhanced TPS Nodes (ETN). We are going to concentrate on the connections of physical nodes, as well as virtual nodes, to their respective E T N. The virtual nodes are executed within an E S X I host node Each physical server, virtual server, and console station, is E. An E T N remove the need to have an LCNP card in an E S V T, or in an E S T, and, allows the integration of F T E based servers, and console stations, with the LCN network. With the E L C N, classic LCN connections to Experion TPS nodes are no longer required. The E L C N bridge is the only Experion LCN node connected to the classic LCN. For all other E L C N nodes, the communication with the LCN occurs through the E L C N bridge. ELCN nodes like the A M, and the E N I M are connected to FTE at Level 2. First, Experion and TPS systems are integrated into one system. The existing TPS functionality is carried forward as Experion, which continues to evolve. From R 400, the GUS applications are hosted on an E S T, while the TPS App node is replaced with an Experion App node. EPKS L1 P2 Page 1 TPS R421 was the last separate release for the TPS software. Starting with Experion release 400, the TPS functionality is available only in Experion nodes. Experion includes support for LCN release 535. Refer to the table, which shows how TPS, and Experion software has over the years, along with the supported operating systems. Note: Starting from Experion release 501, TPS personality files are integrated into the standard installation and migration processes. An option is provided in the 'Features and Options selection' dialog to install personality files during the installation of E S V T, ACE T, and EST nodes. Let's start with the basics. What are the steps of TPS configuration? First, the E S V T and the E S T need to be configured in the network configuration file(NCF). An ES VT is configured as an Application Module in the NCF, and the E S T is configured as a Universal Station. Next, configure Experion using Configuration Studio. A TPS System Interface is to determine how the Experion server will interface with the TPS system. Among other things, the TPS System Interface will map TPS units to Experion assets. Each EST is configured as a console station. Station connection properties must also be configured on the each console station. Finally, console extension stations are configured. Each EST is configured with the number of console extension stations it will host. Also, station connection properties must be configured on the each of the console extension stations. A maximum of 5 Experion clusters can share the same LCN. This is possible when TPS units are divided among the ESVTs. EPKS L1 P2 Page 2