FEATURE WIRELESS TECHNOLOGY
Wireless remote asset shutdown for challenging environments
A wireless telemetry remote shutdown system from SignalFire offers wireless remote asset shutdown for process manufacturers in challenging environments
I
Figure 1: The SignalFire Gateway may be configured to monitor and control remote well sites as a standalone system, using a PLC to offload sensor data. In this diagram, the SignalFire Gateway is configured to update the remote RSDS nodes based on the status of tank levels as received from tank sensors. For example, a radar-level sensor in the tank would send data wirelessly to the Gateway, which would be configured to update the remote nodes appropriately. A sample logic: If tank level from sensor A is greater than X.X feet, set relay B on remote node C to be de-energised
n challenging environments, such as oil fields, equipment often must be shut
down remotely. For instance, when a tank that collects oil or water from several wells becomes full, wells must be shut down to prevent overflow. Because of the oil-field layout, the decision to shut-in a well (usually conducted near the tanks) is often made far away from the actual wells. For this type of monitoring and control,
Figure 2: The diagram shows the SignalFire Remote Shutdown System in a PLC- controlled configuration. In this scenario, tank-level information is monitored by any variety of sensors (switch, level sensors, pressure sensors, etc.), with data sent to a local PLC. Tank sensors may be directly connected to the PLC or via a SignalFire wireless system. The PLC monitors the data and determines whether the tank is in an alarmed state. This tank status information is sent to the SignalFire Gateway via a Modbus RS485 connection for transmission to the remote nodes at the well sites
SignalFire Wireless Telemetry offers the Remote Shutdown System (RSDS), which can shut down assets remotely with the fail-safe logic necessary for wireless operation of critical systems. Eliminating the need for costly conduit runs, this long-range (3+ miles) wireless telemetry system can be configured with either a PLC monitoring system or a SignalFire Gateway-controlled standalone system that can monitor inputs and generate control commands autonomously. The SignalFire RSDS interfaces with any type of sensor and transmits the data wirelessly to a SignalFire Gateway. When operating autonomously, the Gateway generates commands and offloads data to a PLC. The Gateway can be configured to additionally send signals to remotely- located shutdown nodes that will shut-in the well (Figure 1 shows the Gateway- controlled system). When the SignalFire RSDS is configured as a PLC-controlled system (see Figure 2), a local PLC makes the decision to shut down the remote wells. If monitoring
tanks in the oil fields for overflow conditions, tank sensors could be directly connected to the PLC that monitors data and decide if the tank is in an alarmed state. Alternatively, the data could be sent wirelessly, with the PLC obtaining tank-level data from the Gateway. The PLC, then, determines whether the well should be operating or shut-in, and sends the proper command to the shutdown nodes located at the well site. Both RSDS communication systems
support a large number of wireless sensors and incorporate SignalFire’s exclusive CommSafe software that guards against system failure if wireless communication is interrupted. In addition to being used extensively in upstream oil and gas applications, the RSDS is ideal for water-tank control and industrial situations where tank monitoring and pump control are necessary. To view a video that explains the
SignalFire Remote Shutdown System configuration and describes how to install an RSDS in a well site to monitor a tank battery, download
https://www.youtube.com/watch?v=f66h F6tP7zs . For more detailed specifications on the RSDS, visit SignalFire’s website at
http://www.signal-
fire.com/products/remote_shutdown/
SignalFire T: +1 978 212 2868 E:
info@signal-fire.com
Software simplifies access to HART field devices
Emerson Process Management and OSIsoft have introduced the OSIsoft PI Connector for HART-IP, a link between HART field devices and OSIsoft’s PI System enterprise software infrastructure for managing streaming sensor data in real-time. The PI Connector for HART-IP automatically and seamlessly maps wired
and WirelessHART devices to the asset structure in the PI Server, eliminating effort and chances for error. It enables end users to gain benefits from their intelligent field networks faster, more easily, and at lower overall cost. Emerson is developing and deploying numerous diagnostic and optimisation packages that analyse field device information to help improve process management, energy consumption and plant safety and reliability. The PI Connector for HART-IP leverages the widely used PI System to serve up information to these application suites. The connector was jointly developed as an integral extension of OSIsoft’s capability.
40 OCTOBER 2015 | AUTOMATION
The PI Connector for HART-IP reduces the cost and effort needed to access and use information from Emerson’s Smart Wireless Gateways and HART multiplexers. Prior to this release, some information from HART devices was only available through OPC connections that had to be made on a point-by-point basis. With the PI Connector for HART-IP all of the necessary linkages populate to their respective applications automatically, giving the user instant access to valuable process and diagnostic information. The software is based on the Microsoft operating system and is both
modular and scalable. It can run on its own server or on the PI System infrastructure hardware. Information from wireless gateways and multiplexers goes directly to the PI System and is not dependent on the plant’s basic process control system.
Emerson
www.emerson.com www.osisoft.com /AUTOMATION
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44 |
Page 45 |
Page 46 |
Page 47 |
Page 48 |
Page 49 |
Page 50 |
Page 51 |
Page 52 |
Page 53 |
Page 54 |
Page 55 |
Page 56 |
Page 57 |
Page 58 |
Page 59 |
Page 60 |
Page 61 |
Page 62 |
Page 63 |
Page 64 |
Page 65 |
Page 66 |
Page 67 |
Page 68 |
Page 69 |
Page 70 |
Page 71 |
Page 72