Experion Server, Station and their Connections PDF

Experion Server, Station and their Connections 27 February 2024 10:24 Let us look at the functions of a Server: Server contains the global database having all the data from the various controllers configured to communicate. It collects history, available in Station trends. Station group displays, an...

Experion Server, Station and their Connections 27 February 2024 10:24 Let us look at the functions of a Server: Server contains the global database having all the data from the various controllers configured to communicate. It collects history, available in Station trends. Station group displays, and reports are also available much of the functionality is tied to global database. It allows efficient communications. All the different controllers that are configured, are set up to communicate efficiently. It is scalable. When you load up process server, it contains all the available functions. For instance: When you purchased the Server originally you had 1,000 points and now you decide that you need 2000 points, there's nothing extra to load, all you need is a different license. It uses standard and open PC hardware To be assisted by our Technical Assistance Center, it is that you use Dell and HP models that are approved by Honeywell. Since many generations of their hardware and the Experion software have been by It provides on-process migration. With the redundancy option, you can go with on- process migration. This will allow you to migrate from one release to the next without shutting down the Server. Station is the human interface to the Experion Server real-time database called HMlWeb Station because it uses the language of the web. If you are connected to an e-Server, you will be using a web browser and not a Station however, the graphics will be the same. There are no exports required. Station uses open hardware and is a bit more open than the Server. It uses off-the-shelf PC hardware, which can also be an ICON Station. EPKS L2 Page 1 It uses off-the-shelf PC hardware, which can also be an ICON Station. Shown on this screen is an ICON Station. It can be more complex than a simple station. It can have up to four flat screens, plus a custom operations panel. Information is coming into the real time database from the C200/C200E, C300 and UOC/vUOC controllers and also any SCADA controllers. It contains automatically published data, alarms and events which can be viewed using Station. There are three types of station Flex Stations, also called an ES-F, is the simplest type of Station. It gets all its data from the Server as indicated by the arrows. If we have redundant servers, there is a time lag of 15-30 seconds from the primary to the secondary swap depending on your database size. During this swap—over time a Flex Station does not have a window to the process, for this we have console stations. Console Stations: As the green arrows indicate, a console Station gets its data directly from the C200/C200E, C300 and UOC/vUOC controllers via Fault Tolerant Ethernet. Hence, during a redundant swap or in case of a primary and secondary servers failure, the Console Stations have a live window to the alarms and events and process data of the controllers. The console station still does require the server for history, SCADA information and Console Extension: The third type of Station is the Console Station extension. Similar to Flex Station, except that it gets all its data from the Console station. So, during a redundant swap, if an operator is sitting at an ESCE, a console extension, they still have live information of the process controllers C200/C200E, C300 and UOC/vUOC. The Server and the Console Stations discover the tags as required and have a dynamic cache. EPKS L2 Page 2 The Server and the Console Stations discover the tags as required and have a dynamic cache. Points come in and out of the dynamic cache as they are used. The dynamic cache is synchronized back and forth automatically between the Console Stations and the Server. But, the console station still depends on the server for SCADA data and alarms. The Experion Orion Console is a control room furniture for the process operators, process engineers, and plant managers. The Orion Console is Honeywell's next generation control room furniture. It contains 55—inch, ultra—high definition 4K screens that provide the operator with an workspace. Due to their large size, allow contextual displays which gives information to operators. This allows for faster operator response to process situations. It has an Alarm fight panel that provides visual notification throughout the control room which in turn allows fast operator response. Along with other interfaces in a station the Orion Console is available as a standard product in two sizes that is 2 operating positions and 3 operating positions. That means, each operating position has a separate computer (physical or virtual), and mouse, thin client and a monitor. Each set of equipment is associated with one operating position, and will be connected to separate power feeds. Therefore there is no single point of failure. The Operator Touch Panel is a touch-enabled screen with innovative software that is the primary process control interface for the operator. It supports HMlWeb (Human Machine Interface Web) displays which are for the operators specific needs. It is more intuitive, direct and faster than existing interface devices such as a mouse and this is particularly important in situations where unexpected equipment failure occurs and the process operator has to quickly take action to avoid wider such as process trips. EPKS L2 Page 3 The desktop height of an Orion console can be adjusted and locked to the required position. This allows the operator to perform operations in either a sitting or standing position as per their requirement thereby reducing fatigue. The Distributed System Architecture (DSA) option enables multiple Experion servers to share data, alarms, alerts, events, messages, and history without the need for duplicate configuration on any It extends a single database to very large systems It is effective for distributed systems, for logically separate Experion systems located in different parts of a plant, and for combinations of the two. It fully utilizes redundant servers, networks, Fault Tolerant Ethernet (FTE), and simple to configure. It is supported across multiple software releases. EPKS L2 Page 4 In this example, two operators are sitting at stations which are connected to the same server. Operator 1 says, Hey, Could you call up a graphic with the parameter FICIOI.PIDA.PV"? Operator 2 replies, Sure. Here, operator 2 calls up the graphic; the Server makes a connection to the process controller that contains that parameter, and the screen is populated. But, what if operator 2 is sitting at a station that is connected to a different server? If Operator 2 displays a point that is not on the local server, the server goes out among the DSA partners and finds out which server is the owner of this point It automatically creates a temporary or cache point for that item so that the next time the operator calls it up, it knows who owns it, makes the connection and very quickly displays the information on the Station screen. Hence, you just have to configure the one—point database in a system and its partners in DSA discover the tags as required. Due to DSA, FICIOI is now shared among the Control Room 1 and Control Room 2 Servers, and the same would happen if the operator was sitting at Control Room 3. EPKS L2 Page 5 TPS can be extended into Experion with the help of a server called an, Experion Server TPS (ESVT) and a console station Experion Station TPS (an EST) This allows the TPS points to be auto-discovered by the ESVT and also seen by the EST There is no duplicate tag configuration or maintenance required, and the TPS database is automatically made part of the Experion PKS global database. TPS process alarms also appear in the Experion Alarm Summary. One can acknowledge TPS alarms from an Experion Station, and go directly to a detail display for a TPS point from the Alarm Summary. ATPS system alarm appears in Experion System Status display. TPS events appear in the Event Summary, and TPS messages appear in the Message Summary. So, all that happens automatically. TPS data can be incorporated into Experion PKS history and trends but that has to be configured. This allows you to run half the plant on TPS, half on Experion, and the Experion displays will combine both systems. Let us now review all these Station types and TPS - ESVT, ESV-Server, Flex station, console station and extension. So, the servers get their data from their controllers. If it's an ESVT they also have a connection to the LCN so they automatically discover TPS points. Servers supply information to the flex stations, and also supply information to each other through Distributed System Architecture. The console stations get data from the server but they also have a direct connection. If it's an ESC there can be a to the C200/C.900E, C300 and UOC/vUOC. Console stations connected to the LCN are ESTs and are a direct connect to the UOC/vUOC, C200/C200E, C300 and LCN. The console stations EPKS L2 Page 6 ESTs and are a direct connect to the UOC/vUOC, C200/C200E, C300 and LCN. The console stations cannot operate without their server because there is information available to the server that the console stations don't have. DSA mechanism is used to share this data. The extension stations get their information directly from the console stations they're configured on. The dynamic cache where the point information is synchronized back and forth between the console Station and its Server, automatically. FTE is the connection between stations, and the process controllers. 1. It is a patented technology that makes standard Ethernet more compatible with process control. 2. There is no single point of failure 3. There is full redundancy with the C200/C200E provided you're using the Fault Tolerant Ethernet Bridge with the C300 and OOC through Fault Tolerant Ethernet. 4. It is also available to third-party applications on different PCs. 5. I f your device cannot handle Fault Tolerant Ethernet, can still communicate; they connect through single Ethenet instead of FTE. 6. Finally, FTE is transparent to other applications running on the machine. Let us see how FTE works. Here, we have got three different cluster servers through an FTE community. A cluster is a Server with all of its Stations, ACEs and controllers with multiple paths. Let's say that we are sitting in Cluster 1 and need some information from a controller that's Located EPKS L2 Page 7 Let's say that we are sitting in Cluster 1 and need some information from a controller that's Located in Cluster 2 and has a DSA connection. Now, one way to get this information is by going through the "A" switches and another is by the "B" switches; With FTE you have redundant switches along with dual Network interface cards (NIC) cards in the machines. So, we can go A to A or B to B, but we also have another way to go. There is a cross—over cable between the A and the B switch at the highest level and can make use of this cross-over cable to pick up two more paths. So, here is one of the paths: Information can go from Unit 1 using the A switch, go across the cross-over cable to the B switch and back down into Unit 2. OR It can, go through the B switch in Unit 1, cross over to the A switch and go back down through the A path to Unit 2. So, in total, there are four different pathsAtoA B to B, AtoB, BtoA. FTE monitors all these paths, it allocates traffic efficiently among the four paths, and if something should happen to one of the paths, it quickly switches traffic over to one of the other three paths still available. EPKS L2 Page 8