NOV-DEC 2017

Issue link:

Contents of this Issue


Page 17 of 61

18 INTECH NOVEMBER/DECEMBER 2017 WWW.ISA.ORG PROCESS AUTOMATION Now that data in modern historians is more readily available via the use of standard SQL structures and open in- terfaces, it is possible to use commer- cially available software for analysis and reporting, integrating with corpo- rate standards and removing the need for specialist skills. Historian suppliers and system integrators have created a wide variety of specialized analysis packages (figure 2) for alarm manage- ment, safety system monitoring, asset management, mass balancing, off-sites management, and power and energy consumption. In many cases, these application packages were developed by suppliers and users to solve specific end user problems and challenges, and then they were made into universal so lutions available to other users. Distributing information Thanks to the cloud, IIoT, and open in- terfaces, historian data can now be made available to anyone and any software sys- tem with proper access credentials. As shown in the applications section, histori- an data can be viewed locally, globally, and from centralized locations. For example, a dashboard display for an alarm monitor- ing application allows engineers to "drill down" into alarm activities. Clicking one of the colored discs in a heat map might take the user to the chattering alarms report, prefiltered for the day of interest. The user can continue to drill down until ultimately the raw alarm and events are displayed, which can be used for root-cause analysis and displaying filtered events before, dur- ing, and after an alarm incident. This capability allows engineers at a central location to monitor conditions from company sites all over the world— but it also allows engineers at each plant to see the same data as it applies to their specific plant. In addition, users are no longer limited to accessing historian data via a local PC. Data can be viewed on any desktop PC, laptop PC, smartphone, or tablet con- nected to the corporate intranet or to the Internet (figure 3). What is possible with today's histori- ans? With the availability of application packages and open interfaces, virtually any kind of analysis of plant data is now possible, as shown in the examples below. Alarm management at a gas field In Europe, a large facility extracting gas from dozens of widely dispersed well heads and tank farms is fully automated. Each well head or tank farm is linked to a central control and monitoring center to form one of the largest distributed con- trol systems in the world. The facility, with more than 750,000 potential alarms, requires an alarm man- agement solution for safe, effective, and efficient operation. The alarm manage- ment system has to be used by all plant personnel, includ- ing operators, engi- neers, and manag- ers. Alarm reporting and analysis is used to help identify and eliminate faulty and incorrectly config- ured alarms, reduc- ing the number of alarms presented to an operator. The well heads and tank farms are linked to the central monitoring and control cen- ter via seven Web servers. A process historian monitors the 750,000 potential alarms, analyzes how operators respond, and produces reports (figure 4) at the end of each shift to show: l standing alarms at the end of a shift l top 10 alarms by number of occur- rences during the shift l alarms suppressed by an operator at the end of the shift l alarms in calibration at the end of the shift l mean alarm rate for the shift l alarm rate distribution by the clock hour Weekly and monthly summary reports are available for management and plan - ning meetings. The alarm management solution follows EEMUA 191 and ANSI/ ISA-18.2 guidelines. Valve travel times At a large oil production facility, reports on high-integrity pressure protection sys- tem (HIPPS) activations were being gen- erated with a custom application package running on a legacy DCS, which needed to be replaced. The company wanted a standardized solution independent from the DCS, so that it could be implemented across many locations with minimal con- figuration at each site. The DCS-independent historian solu- tion receives sequence of events (SOE) data from the HIPPS to generate HIPPS activations and event travel time reports. This solution has been deployed at two sites so far, each with a different DCS. At one site, the SOE data is collected through an OPC server connected directly to the historian. At the other site, SOE data is collected through the remote data syn- chronization application that provides a robust communication method to ad- dress low bandwidth and intermittent Figure 2. Specialized packages, such as alarm reporting software in Yokogawa's Exaquantum historian, can be used by any system. Figure 3. Historian data can be accessed from tablet computers.

Articles in this issue

Links on this page

Archives of this issue

view archives of InTech - NOV-DEC 2017