GE URRHH FlexLogic ™ Basic Pilot Program Elements

Description

The Universal Relay (UR) is a family of leading edge protection and control products built on a common modular platform. All UR products feature high-performance protection, expandable I/O options, integrated monitoring and metering, high-speed communications, and extensive programming and configuration capabilities. The UR forms the basis of simplified power management for the protection of critical assets, either as a stand-alone device or within an overall power automation system.

The UR is managed and programmed through EnerVista Launchpad. This powerful software package, which is included with each relay, not only allows the setpoints of the relay to be programmed, but also provides the capability to manage setpoint files, automatically access the latest versions of firmware/ documentation and provide a window into the substation automation system.

The UR can be supplied in a variety of configurations and is available as a 19-inch rack horizontal mount unit or a reduced size (¾) vertical mount unit. The UR consists of the following modules: power supply, CPU, CT/VT input, digital input/output, transducer input/output, inter-relay communications, communication switch and IEC Process Bus. All hardware modules and software options can be specified at the time of ordering.

The UR provides advanced communications technologies for remote data and engineering access, making it easy and flexible to use and integrate into new and existing infrastructures. Direct support for fiber optic Ethernet provides high-bandwidth communications allowing for low-latency controls and high-speed file transfers of relay fault and event record information. The available redundant Ethernet option provides the means to create fault tolerant communication architectures in an easy, cost-effective manner without the need for intermediary communication hardware. The UR supports the most popular industry standard protocols enabling easy, direct integration into DCS and SCADA systems.

• IEC 61850 with 61850-90-5 support

• DNP 3.0 (serial & TCP/IP)

• Ethernet Global Data (EGD)

• IEC 60870-5-103 and IEC 60870-5-104

• Modbus RTU, Modbus TCP/IP

• HTTP, TFTP

• SNTP and IEEE 1588 for time synchronization

• PRP as per IEC 62439-3

In the late 1990s, the monitoring software for operator stations began to modularize, separating display and drive. After 2000, the host computer was basically PC, and the operator station software was divided into a display part and a database part. In addition, there were driver software. In order to interconnect with third-party applications, the operator station software used OPC, DDE, ODBC, API, and other methods. In addition, there were interfaces for users to write software, provide training for system operators, and provide analysis of the controlled object and control system simulation by users’ technical personnel, To minimize the faults of the control system itself and test the control system’s ability to cope with faults in the controlled object.

Before 1995, the operator stations of DCS did not have the above functions. Since the mid-1990s, operator stations have started to have software interfaces such as OPC and API, especially general monitoring software. There are already suites, simulation interfaces, and rich scripts available. They have inherent advantages as alternative operator stations for DCS. Some DCS manufacturers are developing some functions a bit slowly. For example, although the CONNECTOR NT operator station of INFI90 was introduced to the market in the mid to late 1990s, the development of the operator station functions appears to be somewhat different from the trend, and there are occasional crashes in the early stages of use.

The communication system extended by DCS can be divided into three parts. Firstly, it is the data source, which reads real-time data from DCS and sends it to software called “applications”. Usually it is a historical site, optimization control calculation, web, etc. Usually, historical stations and databases are separated. For example, HONEYWELL’s PHD, ASPEN’s IP.21, OSI’s PI, etc. Finally, you need to send the data to a relational database for storage, such as SQL or ORACLE, or you can embed the relational database into a historical site. The exchange of data between data sources and applications can be done using OPC, DDE, ODBC, API, etc. DCS is easily connected to historical stations in the information system. The information system adopts Ethernet connection. The connection method can be star shaped, circular shaped, etc. Ring is a relatively new method of connection.

UR-6UH
UR-7DH
UR-7GH
UR-7HH
UR-7IH
UR-7KH
UR-7QH
UR-7SH
UR-81H
UR8AH
UR-8AH
UR8CH
UR-8CH
UR8FH
UR-8FH
UR-8FV