Sparkline representations of process control system alarms

Abstract

Operator interface device for a process control system comprising: a display (212); an operator display module (206) for displaying an operator application (208) on the display (212); an alarm presentation interface (300) which is displayed on the display (212) via the operator application (208), wherein the alarm presentation interface (300) includes a sparkline (310) associated with an alarm to graphically represent a trend of a process variable relative to an alarm threshold associated with the alarm, wherein the sparkline (310) represents a trend of the process variable during the most recent time period, and includes a symbol (316) that is displayed at a position on the sparkline (310) corresponding to the time of alarm activation and moves within the most recent time period and moves along an alarm threshold line (314) as time elapses.

Description

SUBJECT OF DISCLOSURE

[0001] This disclosure relates generally to process control systems and more particularly to sparkline representations of process control system alarms. BACKGROUND

[0002] Process control systems, such as those used in petroleum refining, chemical, or other operations, typically include one or more process controllers that are communicatively coupled to one or more field devices via analog, digital, or combination analog / digital buses. Field devices, which can be, for example, valves, valve positioners, switches and transmitters (e.g. temperature, pressure and flow sensors), perform a process control system function within the work process, such as opening or closing valves and measuring process parameters. The process controllers receive signals indicative of process measurements from field devices and then process that information to generate control signals and enact control programs, make other process control decisions, and trigger process control system alarms. Often, process control information can be recorded for long term historical purposes for post analysis and / or training.

[0003] Information from the field devices and / or the controller is typically provided through data highways or communications networks to one or more hardware devices, such as operator workstations, personal computers, data historians, report generators, centralized databases, etc. Such devices are typically located in control centers and / or on other locations away from the harsh production environment. These hardware units operate z. B. Applications that allow the operator to perform a variety of functions related to the operation of the process control system, such as seeing the progress currently being made, changing an operating state, changing settings of a control program, the operation of the process control and / or field devices to modify, to view alarms generated by field devices and / or process controllers, to simulate the operation of the process for personnel training and / or to evaluate the operation.

[0004] These hardware units typically include one or more user interfaces to display pertinent information regarding the operational status(es) of the control system and / or other devices within the control system. Display examples take the form of alarm displays that receive or show alarms generated by controllers or devices within the process control system, controller displays that indicate the operational status or states of the controller or controls of another device or devices within the process control system, etc.

[0005] In a process control system, it is common for thousands of alarms to be defined in the process control system to notify the operator of possible problems in the process control system. Alarms are defined, for example, to protect people and / or personnel, to prevent environmental incidents, and / or to ensure product quality during manufacture. Typically, each alert is defined by one or more settings (e.g., alert threshold) that define when a problem has arisen or is imminent, and / or to trigger the alert and set a priority (e.g., critical or warning). to define the importance of the alarm in relation to other alarms.

[0006] Typically, alarms are presented (e.g., presented) to the operator or operators in the form of a list or table. In such a format, each alarm is presented as a single line in the list with specific data informing the operator about the status of the control system. Data in a provided alarm list may include, for example, a description of the alarm and the time it was triggered.

[0007] It can also include the source of the alarm, the importance or priority of the alarm, the state of the alarm (e.g. acknowledged or not, active or not), the type of process variable that triggered the alarm, the value of the process variable, etc . As information is received from the process controllers and / or field devices, the alarm list can be updated in real time to allow operators access to all current information regarding all active alarms. SUMMARY

[0008] Methods and apparatus for displaying a sparkline representation of a process control system alarm are disclosed. In one example, a user interface apparatus for a process control system includes an operator display module to show an operator application on the display. The user interface also includes an alarm interface, which is presented on the display by the operator application. The alarm interface includes a sparkline associated with an alarm to graphically show the trend of a process variable relative to the alarm limit of an associated alarm.

[0009] In another example, a method includes obtaining process variable data from a process controller associated with a process variable; obtaining alarm data from an alarm associated with the process variable; generating a sparkline based on the process variable data and the alarm data to plot a trend of the process variable versus the alarm limit of the alarm; and displaying the sparkline using a user interface. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] figure Figure 12 is a schematic illustration of an example process control system.

[0011] figure illustrates an example method, the example of an operator station from figure and or figure to install.

[0012] figure illustrates an example of an alarm interface that may be used, an operator display and / or an application and / or more generally the example of the operator station of FIG figure to install.

[0013] figure illustrates another example of an alarm interface.

[0014] figure FIG. 12 is a flowchart representation of an example operation for the installation of the example operator station of FIG figure and or figure .

[0015] figure FIG. 12 is a schematic diagram of an example process platform that may be used and / or programmed to implement the example operation of FIG figure and / or more generally the e.g figure and or figure to install. DETAILED DESCRIPTION

[0016] Alarm displays are a primary tool by which process control system operators remain aware of potential problems in a process control system. A typical alarm interface includes a table of all active alarms. The information presented by an alarm interface for each active alarm may include the time the alarm was activated, the type of alarm (e.g., high, low, etc.), the threshold setting (e.g., 400 gal.), or the alarm limit and include the process variables (e.g. 408 gall.).

[0017] In addition, alarm displays are typically updated in real time to provide the operator with the most up-to-date information on the condition of the process control system. Even though operators have the most up-to-date data regarding a process control system, changing process variables associated with the active alarm has since been associated

[0018] alarms have been activated (i.e. the ongoing trends and / or behavior of the process variables) are not always freely accessible for analysis. Without this information, operators may misinterpret the meaning and / or sense of the alarm, resulting in ineffective corrective action. Operators can e.g. B. to get used to certain alarms that occur frequently from experience. Based on past experience, operators may make incorrect assumptions about the root cause (i.e. the original condition and / or condition of the process control system that caused the alarm) because although the same common alarms are triggered, the process dynamics are different. An operator can e.g. B. have become accustomed to a process variable that is normally in a state of slowly returning to normal (i.e. no alarm), due to normal process dynamics and / or because the alarm is not properly configured with too much hysteresis and / or off delay. This allows the operator to ignore such an alarm for a considerable period of time when quick action is actually needed because the actual state of the process control system is different from what the operator assumes. In other words, operators can become accustomed to responding to one or more alerts in some way that was effective in the past (e.g., waiting for a period of time before responding). However, if the real state of the process control system is different than assumed, but the same alarms are still being signaled, operators may not be able to see the differences in the process control system and can therefore react in the usual way with little or no effect. Just as misjudging the ongoing trends of process variables associated with specific alarms after those alarms have become active can lead to incorrect conclusions about the state of the process control system and / or the root cause, incorrectly understanding the behavior of process variables, that led to the triggering of appropriate alarms may also result in incorrect determination of root causes and / or ineffective operator response.

[0019] Accordingly, the examples described herein include a trend line graph (referred to herein as a sparkline) that can be used to show a visual representation of the behavior of a process variable, that behavior leading up to the alarm being triggered, as well as that that is after the triggering of the alarm occurs. The sparklines shown may be of fixed height and width, and need not include labels and scales, but must show the changing relationship of a process variable to a corresponding alarm limit over the most recent time period. The sparklines allow operators to query the alarm interface instead of reading relevant information to understand the behavior and / or state of a process variable relative to the alarm limit. Additionally, using sparklines, operators are able to determine whether the evolving state of a process variable associated with active alarms is an acceptable state with normal behavior, or is an exceptional deviation from normal behavior and thus requires special attention. In addition, because the ongoing behavior of a process variable is shown, operators can also see if their actions to correct the potential problems are working, or if they should take additional and / or different actions.

[0020] figure Figure 12 is a schematic illustration of an example process control system 100 . The process control system, for example 100 from figure includes one or more process control(s) (one of them as a reference number 102 designated) and one or more operator stations (one of them as a reference number 104 referred to) and one or more workstation(s) (one of which is referred to as a reference number 106 designated). The process control system, for example 102 , the example operator station 104 and the example workstation 106 are communicative via a bus and / or a local area network (LAN) 108coupled, which is usually referred to as Application Control Network (ACN).

[0021] For example the operator station 104 from figure allows the operator to view or operate one or more operator displays and / or applications that enable the operator to view process control system variables, view process control system states, view process control system requirements, view process control system alarms, and / or process control system settings to change (e.g. define limit values, recognize operating states, delete alarms, switch off alarms, etc.). An example installation method of an operator station 104 from figure is linked to below figure be used. Examples of operator display applications that can be used to display the operator station 104 to install will be related to below figure and figure 4 described.

[0022] For example, the operation station 104 includes and / or installs an alarm interface (e.g. the alarm interfaces of figure and figure 4) to display a sparkline for each associated active alarm and to enable the process control system operator to visually perceive the behavior of a process variable associated with each active alarm, during the time leading up to the alarm and after the alarm was raised until current state. In some examples, the sparkline associated with each alarm may be shown in a column of a conventional alarm list (e.g., the example alarm interface of figure ) along with additional information related to the alarm. In other examples, the sparkline associated with each alert can be shown as an independent interface or as a sidebar banner in conjunction with other elements of an alert interface (e.g., the example alert interface of figure ).

[0023] For example the operator station 106 from figure can be configured as an application station to run one or more information technology applications, interactive user applications and / or communications applications. The application station 106 can e.g. B. be configured to perform primary process control related applications, while other application stations (not shown) may be configured to perform primary communication applications, the process control system 100 enable communication with other devices or systems using any desired communication media (e.g. wireless, wired) and protocols (e.g. HTTP, SOAP, etc.). For example the operator station 104 and the example workstation 106 from figure may be installed using one or more workstations and / or other suitable computer systems and / or processing systems. The operator station 104 and / or workstation 106 can e.g. B. be installed with single processor personal computers, single or multi-processor workstations, etc.

[0024] The example LAN 108 from figure can be installed with any desired communication medium and protocol. For example, the example LAN 108 can be used with a wired and / or wireless Ethernet communication scheme. However, as will be appreciated by anyone skilled in the art, any other suitable communication medium and / or protocol may be used. Although a single LAN 108 in figure 1, more than one LAN and / or alternative pieces of communication hardware may also be used to provide additional existing communication paths between the example systems of FIG figure to provide.

[0025] For example the controller 102 from figure becomes a variety of intelligent field devices 110 , 112 and 114 through a digital data bus 116 and an input / output gateway 118 coupled. The intelligent field devices 110 , 112 and 114 can be fieldbus compliant valves, actuators, sensors, etc., in which case the intelligent field devices 110, 112 and 114 with the digital data bus 116 communicate through the well-known Foundation Fieldbus protocol. Of course, other types of intelligent field devices and communication protocols can be used instead. The intelligent field devices 110 , 112 and 114 could instead e.g. B. Profibus and / or HART-enabled devices through the data bus 116 communicate and use the well-known Profibus and HART communication protocols. Additional I / O devices similar and / or identical to I / O Gateway 118 are, can with the controller 102 be coupled so that additional groups of field devices, such. B. the Foundation Fieldbus devices, HART devices etc. with the controller 102 to be able to communicate.

[0026] In addition to the intelligent field devices, for example 110 , 112 and 114 can be one or more non-intelligent field devices 120 and 122 communicative with the controller 102 be paired. The non-intelligent field devices, for example 120 and 122 from figure can e.g. B. Conventional 4-20 milliamp (mA) or 0-10 volt direct current (VDC) devices that work with the controller 102 communicate via appropriate wired connections.

[0027] For example the controller 102 from figure can e.g. For example, a DeltaV™ controller sold by Fisher-Rosemount Systems Inc., an Emerson Process Management company. However, any other control can be used in its place. Although only one controller 102 in figure As shown, additional controllers and / or process control platforms of any desired type and / or combination could also be connected to the LAN 108 be paired. For example the controller 102 in any case, runs one or more process control programs in connection with the process control system 100 by a system engineer and / or system operator through the use of the operator station 104 were started, and those for control 102 downloaded or instantiated in it.

[0028] While figure an example of the process control system 100 in which the methods and apparatus for controlling information communicated to process control system operators (described in more detail below) may be employed to advantage, the methods and apparatus for controlling information communicated to operators herein may, if desired, disclosed, may be advantageously applied in other process plants and / or process control systems of greater or lesser complexity (e.g., there may be more than one controller, and in more than one geographic location, etc.) than the illustrated example of FIG figure to install.

[0029] figure illustrates an example method of installing the example operator station 104 from figure to install. For example the operator station 104 from figure includes at least one programmable processor 200 with a. The processor, for example 200 from figure executes encrypted instructions stored in memory 202 from the processor 200 are present (e.g. in random access memory (RAM) and / or read only memory (ROM)). The processor 200 can be any type of processing unit, such as a processor core, a processor and / or a microcontroller. The processor 200 may include an operating system 204 , an operator display module 206 , an operator application 208 and an alarm interface 201 to run. An example operating system 204 is an operating system from Microsoft ® . For example, the memory 202 from figure can e.g. B. of and / or in the processor 200 installed and / or may have one or more memory and / or data storage functionally associated with the processor 200 are coupled.

[0030] To allow the operator to interact with the example processor 200to enable includes the example operator station 104 from figure any type of display 212 . The display, for example 212 includes, but is not limited to, a computer monitor, computer screen, television, portable device (e.g., a smartphone, a Blackberry™ and / or an iPhone™), etc., and is capable of displaying user interfaces and / or applications that through the processor 200 and / or more usually by the operator station, for example 104 were installed.

[0031] For example, the operating system 204 from figure shows and / or allows to show the alarm interface 210 through and / or the display, for example 212 . To enable operator interaction with the applications created by the example station 104 have been implemented to allow, for example, the operating system 204 a programmable application interface (API) through which the e.g. operator display module 206 the alarm interface 210 using operator application 208 can define and / or select, including the operating system 204 can cause and / or instruct the defined and / or selected alarm interface 210 to display. An example alarm interface 210 will be linked below figure and figure 4 described.

[0032] To show process control system operator displays and / or applications includes the operator station 104 from figure an example operator display module 206 . For example, the operator station module 206 from figure collects alarm data and / or information from one or more process controllers (e.g. the controller, for example 102 from figure ) and / or other elements of a process control system and uses the accumulated alarm data and / or information to provide a specific alarm interface 210 to create and / or define (e.g. the alarm interface 300 from figure ) using the operator application 208 . As it does so, the e.g. operator display module stores or buffers 206 also temporary process variable data corresponding to all enabled and unsuppressed alarms or predefined groups of alarms of a certain type (e.g. security system (SIS) alarms) of the most recent period. The buffered process variable data can then be accessed and a sparkline created and / or defined to be used in the alarm interface 210 to be included, which graphically depicts the historical behavior of a process variable in relation to the corresponding alarm limit for the period of time where the data was buffered should a corresponding alarm subsequently be triggered. All process variables can be buffered without user installation and can be performed independently of any long-term historization function in the process control system. The created and / or defined alarm interface 210 is shown in the example display 212 from and / or through the operating system, for example 204 shown.

[0033] As an example method of installing an operator station 104 from figure in figure illustrated, the data structures, elements, processes, and devices illustrated in figure combined, subdivided, rearranged, omitted, removed and / or implemented in any other way. For example, the operating system 204 , the operator display module, for example 206 , the example alarm interface 210 , and / or more generally, the example station 104 from figure may also be installed with hardware, software and firmware and / or any other combination of hardware, software and / or firmware. In addition, the example operator station 104 may involve additional elements, processes and / or devices instead of or in addition to those contained in figure are illustrated and / or may include one or more of the illustrated data structures, elements, processes, and devices.

[0034] figure illustrates an example alarm interface 300 that can be used, an operator display and / or application and / or more generally an e.g. operator station 104 as in figure to install. For example, the alarm interface 300 may be presented as an independent interface or as a sidebar banner in conjunction with other elements (not shown) of an alert interface. The alarm interface 300 includes an alarm box 302 , which contains basic information regarding each active alarm of a process control system, including the alarm priority (represented by the shape and / or color of an icon 304 is displayed), the type of alarm (which is indicated by the designation 306 displayed) and the alarm day 308 to turn off the alarm box alarm 302 to be marked accordingly. The alarm boxes 302 also include sparklines 310 corresponding to each active alarm. Any Sparkline 310 includes a trend line 312 , showing the behavior of a process variable in relation to an alarm limit, represented by an alarm limit line 314 for the most recent time period (e.g. the past hour).

[0035] The current state of the process variable corresponds to the sparkline 310 and can e.g. B. by a symbol, like a tick 318 at the extreme right end of the trend line 312 be shown graphically. The horizontal scale represents the most recent epoch that the process variable data was buffered. The alarm activation time is shown on the spark line 310 graphically e.g. B. by another symbol, like a point 316 , shown. Between the time since the alarm was first triggered (i.e., when the process variable exceeded the alarm limit) and the current time, the dot moves 316 along the alarm limit line 314 to the left until more time elapses than those corresponding to the width of the sparkline 310 corresponds, and until then the point 316 is no longer displayed. Any Sparkline 310 can also be in the alarm interface 300 set to a common latitude and timescale, and aligned vertically (e.g. by inserting the alarm box 302 in a vertical column) to enable the operator to make a quick visual comparison between multiple alarms and identify possible confounding process variables.

[0036] As in figure shown does not include every sparkline 310 Labels or scales to express in numbers the magnitude of the variation of the corresponding process variable. However, the vertical scale of each sparkline becomes 310 automatically adjusted to fit a specified height to enable the operator to quickly identify the volatility of a process variable, as well as the current slope and direction of the process variable relative to the appropriate alarm limit. The alarm interface 300 can also (e.g. with a red border 320 ) or otherwise the appearance of the alarm box 302 highlight or change when the difference between a process variable and the corresponding alarm limit increases, using a recent segment (e.g. 30 seconds) of a sparkline 310 shown period. When a process variable deviates from a normal state, the operator can use visual signaling to detect alarms that may require additional actions to change the direction of the process variable without risking confusion as to whether a process variable's increasing or decreasing corresponds to an acceptable or problematic condition.

[0037] figure illustrates another example alarm interface 400 . The alarm interface 400 includes an alarm list 402 , which contains a list of active alarms in a process control system, with columns 404 , which contain relevant information, each in the alarm list 402 listed alarm. The example alarm list 402 contains a sparkline column 406 showing a sparkline408 includes everyone in the alarm list 402 contained alarm. The spark lines 408 are installed in the same way as related to above figure to install. Because the sparklines 408 but not in an alarm box 302 are included when a process variable deviates from a corresponding alarm limit, then the sparkline 408 highlighted (e.g. with a red border 410 ) to graphically alert the operator to the alarms that correspond to a process condition and might require action.

[0038] figure is a flow chart showing a sample application for installing the operator station 104 from figure and or figure represents. The example application of figure may be performed by a processor, controller, and / or any other suitable processing device. The example application of figure can e.g. B. contained in encrypted instructions (e.g. computer-readable instructions) in a physically tangible machine or readable medium, such as a flash memory, a ROM and / or random access memory connected to a processor (e.g. the e.g. processor 602 , linked to below figure ). The term physically tangible computer-readable medium, as used herein, is expressly defined to include any type of imperishable computer-readable storage (and exclude propagating signals) or any other storage medium in which information can be stored for any duration (e.g., e.g., for extended periods of time, permanently, temporarily, for temporary buffering, and / or for information caching).

[0039] Otherwise, some or all of the example methods of figure by using any combination(s) of application specific integrated circuit(s) (ASIC(s)), programmable logic device(s) (PLD(s)), field programmable logic circuit(s) (FPLD(s)), discrete logic, hardware, firmware etc. to be installed. There may also be one or more procedures in figure may be installed manually or as any combination of the above techniques, for example, any combination of firmware, software, discrete logic, and / or hardware. Even if, moreover, the exemplary methods of figure with reference to the flowchart of figure are described, it will be appreciated by those skilled in the art that there are many other methods of installing the example method of figure can be used. The execution sequence of the blocks can be B. be changed, and / or some of the described blocks can be changed, removed, subdivided or combined. Some or all of the example methods of figure may also be executed sequentially and / or in parallel, for example by separate processing threads, processors, devices, discrete logic, circuitry, etc.

[0040] The procedure of figure starts at block 500 to, with an operator station (e.g. the station 104 from figure ) that runs the operator display module (for example, the operator display module 206 ) to an alarm interface (e.g. alarm interface 210 ) at block 502 to show. At block 504 receives the operator station (e.g. the example operator station 104 ) process variable data for all enabled alarms or any predefined subdivision of alarms of a certain type (e.g. modules and SIS alarms) and buffers the data for the most recent epoch. At block 506 receives the operator station (e.g. the example operator station 104 ) new and / or updated data via process controls (e.g. the control 102 ). At block 508 specifies an operator application (e.g. the example operator application 208 ) whether data for each buffered process variable corresponds to an active alarm. For each buffered process variable that does not correspond to an active alarm, the process goes back to block 504to continue buffering process variables. For each process variable that corresponds to an active alarm, the process goes to Block 510 , where the operator application (such as the example application 208 ) determines the current trend for the process variable (i.e., whether the process variable is deviating from or approaching the appropriate alarm limit) and the current state of the process variable. At block 512 creates and / or updates the operator application (e.g. the operator application 208 ) a sparkline that corresponds to each active alarm, as well as determining other changes that need to be made to the alarm interface (e.g. the example alarm interface 210 ) and then notifies the operator display module (e.g. the for example operator display module 206 ) about the changes. Control then goes back to block 502 to show the updated alarm interface (e.g. the example alarm interface 210 ).

[0041] figure Figure 1 is a schematic diagram of an example processor platform 600 , used to carry out the exemplary method of figure can be used and / or programmed and / or more generally to the e.g. operator station 104 from figure and or figure to install. The processor platform 600 can e.g. B. be installed by one or more general purpose processors, processor cores, microcontrollers, etc.

[0042] The processor platform 600 of the example of figure includes at least one general purpose programmable processor 602 . The processor 602 carries encrypted instructions 604 and or 608 due to which is in the processor's memory 602 are (e.g. in a RAM 606 and / or a ROM 610 ). The processor 602 can be any type of processing unit, such as a processor core, a processor and / or a microcontroller. The processor 602 can, among other things, the example method of figure carry out to install the operator station described there, for example.

[0043] The processor 602 communicates with memory (including ROM 610 and / or the RAM 606 ) via a bus 612 . The RAM 606 can be installed by DRAM, SDRAM and / or any type of RAM memory and the ROM 610 may be implemented by flash memory and / or any other desired type of memory. access to storage 606 and 610 can be controlled by memory controllers (not shown).

[0044] The processor platform 600 includes an interface circuit 614 . The interface circuit 614 can be implemented by any interface standard, such as a USB interface, a Bluetooth interface, an external storage interface, a serial interface, general purpose input / output, etc. One or more input devices 616 and one or more output devices 618 are connected to the interface circuit. The input devices 616 and / or output devices 618 can for example for providing the alarm interface 210 from the example display 212 from figure be used.

[0045] Although specific methods, apparatus and articles of manufacture have been described herein, the scope of this patent is not so limited. Such examples are meant as non-limiting, illustrative examples. On the contrary, this patent covers all methods, apparatus and articles of manufacture which fall reasonably within the scope of the appended claims, either literally or by the doctrine of equivalents.

Claims

[1] Operator interface device for a process control system comprising: a display; an operator display module to display an operator application on the display; an alarm presentation interface that is displayed on the display via the operator application, wherein the alarm presentation interface includes a sparkline associated with an alarm to graphically represent a trend of a process variable relative to an alarm threshold associated with the alarm. [2] Operator interface device according to claim 1, wherein a vertical scale of the sparkline is automatically adjusted to fit into a specified height of the sparkline. [3] Operator interface device according to claim 1 or 2, wherein the sparkline associated with an alarm has a width and time scale that is equal to a second sparkline associated with a second alarm, in order to enable the operator to visually compare the first and second sparklines. [4] Operator interface device according to one of claims 1 to 3, wherein the sparkline contains a trend of the process variable during a time period before the alarm was triggered. [5] Operator interface device according to any one of claims 1 to 4, wherein the sparkline contains a trend of the process variable during a time period after an alarm has been triggered. [6] Operator interface device according to any one of claims 1 to 5, wherein the sparkline contains a trend of the process variable during the most recent time period. [7] Operator interface device according to claim 6, further comprising a memory to buffer data associated with the trend of the process variable for the most recent time period, independent of long-term historiography of the trend data of the process variable. [8] Operator interface device according to claim 6 or 7, wherein the sparkline includes a graphical display of when the alarm was triggered, in relation to the most recent time period. [9] Operator interface device according to any one of claims 1 to 8, wherein the sparkline includes a graphical display of the current state of the process variable in relation to the alarm threshold. [10] Operator interface device according to one of claims 1 to 9, wherein the sparkline is integrated into an alarm list of the alarm presentation interface. [11] Operator interface device according to one of claims 1 to 10, wherein the sparkline is integrated into a sidebar banner display of the alarm presentation interface. [12] Operator interface device according to any one of claims 1 to 11, wherein the sparkline is highlighted when the difference between the process variable and the alarm limit increases, in order to graphically indicate to the operator when further action may be required to correct the process variable. [13] Procedure encompassing: Receiving data of the process variable from a process controller that is connected to a process variable is associated; Receiving alarm data from an alarm associated with the process variable; generating a sparkline based on the process variable data and the alarm data. to graphically show a trend of the process variable in relation to the alarm threshold. to represent and Displaying the sparkline via an operator interface. [14] Method according to claim 13, further comprising an automatic adjustment of a vertical scale of the sparkline to fit into the specified height of the sparkline. [15] Method according to claim 13 or 14, wherein the sparkline associated with the alarm has a width and time scale that is equal to a second sparkline associated with a second alarm, in order to enable the operator to visually compare the first and second sparklines. [16] Method according to any one of claims 13 to 15, wherein the sparkline contains a trend of the process variable during a time period before the alarm was triggered. [17] Method according to any one of claims 13 to 16, wherein the sparkline contains a trend of the process variable during a time period after an alarm has been triggered. [18] Method according to any one of claims 13 to 17, wherein the sparkline contains a trend of the process variable during the most recent time period. [19] The method of claim 18, further comprising buffering the data of the process variable for a period corresponding to the most recent time period, irrespective of a long-term historiography of the trend of the process variable. [20] Method according to any one of claims 13 to 19, further comprising highlighting the sparkline when the difference between the process variable and the alarm threshold increases, in order to graphically indicate to an operator when further action may be required to correct the process variable. [21] A movable manufactured article that stores machine-readable instructions If executed, arrange for the following: To receive data from a process variable in conjunction with process variables; to receive alarm data associated with the process variable; to generate a sparkline based on the process variable data and the alarm data in order to graphically represent a trend of the process variable in relation to the alarm threshold. to display; and to show this sparkline via an operator interface. [22] A movable manufactured article according to claim 21, wherein the sparkline comprises a graphical display of when the alarm was triggered in relation to the most recent time period. [23] A movable manufactured article according to claim 21 or 22, wherein the instructions, when carried out, cause the system to buffer the process variable data for a period corresponding to the most recent time period, irrespective of a long-term historical analysis of the process variable trend. [24] A movable manufactured article according to any one of claims 21 to 23, wherein the instructions, when executed, cause the system to highlight the sparkline when the difference between the process variable and the alarm threshold increases, in order to graphically show the operator when further action may be required to correct the process variable.

Images