This patent relates generally to performing diagnostics and maintenance in a process plant, and more particularly to preserving and displaying statistical data relating to process variable data recorded by smart process control field devices and other process related field equipment.
Process control systems, like those used in chemical, petroleum or other processes, typically include one or more centralized or decentralized process controllers. Process controllers may be communicatively coupled to at least one host or operator workstation and to one or more process control and instrumentation device. Process control and instrumentation devices may comprise, for example, field devices. The one or more centralized or decentralized controllers may be communicatively coupled to the at least one host or workstation and the one or more process control and instrumentation devices via one or more analog, digital or combined analog/digital buses. Field devices, which may be, for example, valves, valve positioners, switches, transmitters, and sensors (e.g., temperature, pressure, and flow rate sensors), are typically located within the process plant environment. The field devices perform functions within the process such as opening or closing valves, measuring process parameters, increasing or decreasing fluid flow, etc. Smart field devices such as field devices conforming to the well-known F
The process controllers, which are typically located within the process plant environment, receive signals indicative of process measurements or process variables made by or associated with the field devices and/or other information pertaining to the field devices, and execute controller applications. The controller applications implement, for example, different control modules that make process control decisions, generate control signals based on the received information, and coordinate with the control modules or control blocks in field devices such as HART® and fieldbus field devices. The control modules in the process controllers send the control signals over the communication lines or signal paths to the field devices, to thereby control the operation of the process.
Information from the field devices and the process controllers is typically made available to one or more other hardware devices such as, for example, operator workstations, maintenance workstations, personal computers, handheld devices, data historians, report generators, centralized databases, etc. to enable an operator or a maintenance person to perform desired functions with respect to the process such as, for example, changing settings of the process control routine, modifying the operation of the control modules within the process controllers or the smart field devices, viewing the current state of the process or of particular devices within the process plant, viewing alarms generated by field devices and process controllers, simulating the operation of the process for the purpose of training personnel or testing the process control software, diagnosing problems or hardware failures within the process plant, etc.
While a typical process plant has many process control and instrumentation devices such as valves, transmitters, sensors, etc. connected to one or more process controllers, there are many other supporting devices that are also necessary for or related to process operation. These additional devices include, for example, power supply equipment, power generation and distribution equipment, rotating equipment such as turbines, motors, etc., which are located at numerous places in a typical plant. While this additional equipment does not necessarily create or use process variables and, in many instances, is not controlled or even coupled to a process controller for the purpose of affecting the process operation, this equipment is nevertheless important to, and ultimately necessary for proper operation of the process.
As is known, problems frequently arise within a process plant environment, especially a process plant having a large number of field devices and supporting equipment. These problems may take the form of broken or malfunctioning devices, logic elements such as software routines being in improper modes, improperly tuned process control loops, one or more failures in communications between devices within the process plant, etc. These and other problems, while numerous in nature, generally result in the process operating in an abnormal state (i.e., the process plant being in an abnormal condition) which is usually associated with suboptimal performance of the process plant.
Many diagnostic tools and applications have been developed to detect and determine the cause of problems within a process plant and to assist an operator or a maintenance person to diagnose and correct problems once the problems have occurred and have been detected. For example, operator workstations, which are typically connected to the process controllers through communication connections such as a direct or wireless bus, Ethernet, modem, phone line, and the like, have processors and memories that are adapted to run software or firmware, such as the DeltaV™ and Ovation control systems, sold by Emerson Process Management, which includes numerous control module and control loop diagnostic tools. Likewise, maintenance workstations, which may be connected to the process control devices, such as field devices, via the same communication connections as the controller applications, or via different communication connections, such as object linking and embedding (OLE) for process control (OPC) connections, handheld connections, etc., typically include one or more applications designed to view maintenance alarms and alerts generated by field devices within the process plant, to test devices within the process plant and to perform maintenance activities on the field devices and other devices within the process plant. Similar diagnostic applications have been developed to diagnose problems within the supporting equipment within the process plant.
Thus, for example, the Asset Management Solutions (AMS™) Suite: Intelligent Device Manager application (at least partially disclosed in U.S. Pat. No. 5,960,214 entitled “Integrated Communication Network for use in a Field Device Management System”) sold by Emerson Process Management, enables communication with and stores data pertaining to field devices to ascertain and track the operating state of the field devices. In some instances, the AMS™ application may be used to communicate with a field device to change parameters within the field device, to cause the field device to run applications on itself such as, for example, self-calibration routines or self-diagnostic routines, to obtain information about the status or health of the field device, etc. This information may include, for example, status information (e.g., whether an alarm or other similar event has occurred), device configuration information (e.g., the manner in which the field device is currently or may be configured and the type of measuring units used by the field device), device parameters (e.g., the field device range values and other parameters), etc. Of course, a maintenance person may use this information to monitor, maintain, and/or diagnose problems with field devices.
Similarly, many process plants include equipment monitoring and diagnostic applications such as, for example, AMS™ Suite: Machinery Health Manager provided by Emerson Process Management, or any other known applications used to monitor, diagnose, and optimize the operating state of various rotating equipment. Maintenance personnel usually use these applications to maintain and oversee the performance of rotating equipment in the plant, to determine problems with the rotating equipment, and to determine when and if the rotating equipment must be repaired or replaced. Similarly, many process plants include power control and diagnostic applications such as those provided by, for example, the Liebert and ASCO companies, to control and maintain the power generation and distribution equipment. It is also known to run control optimization applications such as, for example, AMS™ Suite: Real-Time Optimizer, within a process plant to optimize the control activities of the process plant. Such optimization applications typically use complex algorithms and/or models of the process plant to predict how inputs may be changed to optimize operation of the process plant with respect to some desired optimization variable such as, for example, profit.
These and other diagnostic and optimization applications are typically implemented on a system-wide basis in one or more of the operator or maintenance workstations, and may provide preconfigured displays to the operator or maintenance personnel regarding the operating state of the process plant or the devices and equipment within the process plant. Typical displays include alarming displays that receive alarms generated by the process controllers or other devices within the process plant, control displays indicating the operating state of the process controllers and other devices within the process plant, maintenance displays indicating the operating state of the devices within the process plant, etc. Likewise, these and other diagnostic applications may enable an operator or a maintenance person to retune a control loop or to reset other control parameters, to run a test on one or more field devices to determine the current status of those field devices, to calibrate field devices or other equipment, or to perform other problem detection and correction activities on devices and equipment within the process plant.
As mentioned above, data from field devices and process controllers may be made available to hardware devices such as operator workstations, maintenance work stations, personal-computers, hand-held devices, data historians, report generators, centralized databases, and the like. This information may be provided to operators or maintenance personnel to allow them to perform various functions related to the process. The amount of data that may be displayed on such devices, however, may be limited by the communication channel over which the data are communicated. For example, smart field devices can often acquire process control data at a much higher data sampling rate than can be communicated to a process controller or other process control device over a typical process control system communication bus.
When abnormal situations occur in a process plant it is often desirable to have as much data on hand as possible in order to analyze the conditions that led to the abnormal situation. Because most field devices can gather process control data at a much higher sampling rate than can be communicated to a process controller, most of the data acquired by the field devices are never forwarded to the controller. As a result, vast amounts of process control data collected by the field devices are not available to operators or other maintenance personnel for analysis after abnormal situations occur. In many cases, data obtained by field devices in the normal course of operation may provide important clues as to the causes or circumstances that lead to abnormal situations. Therefore, when abnormal situations occur, it is desirable to preserve as much of this data as possible in a manner that will allow the data to be communicated to a process controller or other hardware device to be presented to operators or maintenance personnel to help them understand what was happening in the process at the time the abnormal situation occurred. In most cases, it is helpful to know what was happening to the process before, during, and after an abnormal event. Thus, it is desirable to capture data over an extended period that begins well before, and ends well after the abnormal situation is detected. In addition to preserving the process variable data obtained by the field devices, it is also necessary to develop techniques for communicating the preserved data to other devices within the limiting constraints of the communication bus and the communication protocol employed by the process control system installed in the particular process plant in which the process is being controlled.
The present invention relates to a system and method for preserving process variable data relating to the operation of a process in a process plant. The systems and methods of the present invention are adapted to preserve process variable data obtained before, during and after the occurrence of an abnormal situation or event. The preserved process variable data may be communicated from a smart field device or other intelligent field equipment to a process controller or other higher level control device. The process controller or other higher level control device may then cause the preserved data to be displayed for an operator or other maintenance personnel. The preserved data may also be provided to other process control modules or abnormal situation prevention systems for further analysis to develop methods for preventing the abnormal situation from recurring in the future, or for taking additional steps based on the abnormal situation data to minimize or prevent a further deterioration of the process operation.
Accordingly, an embodiment of the invention provides a system for processing data related to an abnormal process event in a controlled process. The system includes a controller, a communication channel, and an intelligent device. The intelligent device may be a field device for controlling the process, or any other equipment related to carrying out the process. The intelligent device includes a processor, a memory, and an input device. The input device is adapted to receive process variable data. The processor is configured to temporarily store statistical data related to the received process variable data in the memory. The statistical data related to the received process variable data are stored in the memory at a first sample rate. The processor is further configured to communicate the statistical data stored in the memory to the controller over the communication channel. The statistical data are communicated at a second sample rate. According to an embodiment, the first sample rate is greater than the second sample rate. The processor may also be configured to execute an abnormal situation prevention routine to detect the occurrence of an abnormal process event based on the received process variable data. When an abnormal process event is detected, the processor may take steps to preserve a portion of the statistical data related to the received process variable data covering a time period beginning before the abnormal process event is detected and ending after the abnormal process event has been detected. The processor may transmit the preserved portion of the statistical data to a process controller in multiple data packets to overcome any limitations of the communication channel.
In another embodiment, a smart device for controlling at least one aspect of a process is provided. The smart device includes a memory, an input adapted to receive process variable data, and a processor. In this embodiment the processor is configured to store statistical data associated with the process variable data received by the input in the memory. The statistical data are stored in the memory at a first data sample rate. The processor is also configured to communicate the statistical data stored in the memory to an external device. The statistical data are communicated to the external device at a second data sample rate. The first data sample rate is greater than the second data sample rate.
The processor may be further configured to store the statistical data in the memory according to a moving time window of a predetermined length. The statistical data are stored in the memory for a period of time corresponding to the length moving time window. Furthermore, the statistical data are stored in the memory on a first-in first-out basis such that older statistical data stored in the memory at a time corresponding to a trailing edge of the moving time window are discarded as new data are received and stored in the memory at a time corresponding to a leading edge of the moving time window. The processor may be further configured to preserve a portion of the statistical data stored in the memory such that the preserved data cover a predefined period of time before the occurrence of an abnormal event and a predefined period of time after the occurrence of the abnormal event.
In still another embodiment, a method of preserving process control data associated with an abnormal situation is provided. The method calls for receiving process control data associated with a process and temporarily storing statistical data associated with the received process control data in a memory. The statistical data are stored in the memory at a first data sample rate. The method further calls for detecting an abnormal situation associated with the process. A portion of the statistical data stored in the memory is preserved when the abnormal situation is detected. The method calls for communicating the preserved portion of the statistical data over a communication channel at a second data sample rate. The first data sample rate is greater than the second data sample rate. The preserved statistical data communicated over the communication channel may then be displayed on an appropriated interface device. The preserved statistical data communicated over the communication channel may also be analyzed to determine a cause of the abnormal situation.
According to this embodiment, temporarily storing the statistical data may include defining a moving time window of a predetermined length. The statistical data may be continually written to a memory as they become available and temporarily stored in the memory for a length of time at least equal to the length of the moving time window. The statistical data may be stored in the memory on a first-in first-out basis such that the oldest data stored in the memory are discarded as new data are stored. The portion of the statistical data that is preserved after an abnormal situation is detected may include a first portion of the statistical data corresponding to a predetermined length of time before the abnormal situation was detected, and a second portion of the statistical data corresponding to a predetermined length of time after the abnormal situation was detected. Finally, the preserved portion of the statistical data may be communicated over the communication channel as a plurality of data packets, each data packet including an amount of data smaller than the preserved portion of the statistical data.
Further aspects and advantages will be apparent to those of ordinary skill in the art from a review of the following detailed description, taken in conjunction with the drawings. While the compositions and methods are susceptible of embodiments in various forms, the description hereafter includes specific embodiments with the understanding that the disclosure is illustrative, and is not intended to limit the invention to the specific embodiments described herein.
Referring now to
Still further, maintenance systems, such as computers executing the monitoring, diagnostics and communication applications described below may be connected to the process control systems 12 and 14 or to the individual devices therein to perform maintenance, monitoring, and diagnostics activities. For example, a maintenance computer 18 may be connected to the controller 12B and/or to the devices 15 via any desired communication lines or networks (including wireless or handheld device networks) to communicate with and, in some instances, reconfigure or perform other maintenance activities on the devices 15. Similarly, maintenance applications such as the AMS™ application may be installed in and executed by one or more of the user interfaces 14A associated with the distributed process control system 14 to perform maintenance and monitoring functions, including data collection related to the operating status of the devices 16.
The process plant 10 also includes various rotating (and other) equipment 20, such as turbines, motors, etc. which are connected to a maintenance computer 22 via some permanent or temporary communication link (such as a bus, a wireless communication system or hand held devices which are connected to the equipment 20 to take readings and are then removed). The maintenance computer 22 may store and execute any number of monitoring and diagnostic applications 23, including commercially available applications, such as those provided by Emerson Process Management, as well the applications, modules, and tools described below, to diagnose, monitor and optimize the operating state of the rotating equipment 20 and other equipment in the plant. Maintenance personnel usually use the applications 23 to maintain and oversee the performance of rotating equipment 20 in the plant 10, to determine problems with the rotating equipment 20 and to determine when and if the rotating equipment 20 must be repaired or replaced. In some cases, outside consultants or service organizations may temporarily acquire or measure data pertaining to the equipment 20 and use this data to perform analyses for the equipment 20 to detect problems, poor performance or other issues effecting the equipment 20. In these cases, the computers running the analyses may not be connected to the rest of the system 10 via any communication line or may be connected only temporarily.
Similarly, a power generation and distribution system 24 having power generating and distribution equipment 25 associated with the plant 10 is connected via, for example, a bus, to another computer 26 which runs and oversees the operation of the power generating and distribution equipment 25 within the plant 10. The computer 26 may execute known power control and diagnostics applications 27 such as those provided by, for example, Liebert and ASCO or other companies to control and maintain the power generation and distribution equipment 25. Again, in many cases, outside consultants or service organizations may use service applications that temporarily acquire or measure data pertaining to the equipment 25 and use this data to perform analyses for the equipment 25 to detect problems, poor performance or other issues effecting the equipment 25. In these cases, the computers (such as the computer 26) running the analyses may not be connected to the rest of the system 10 via any communication line or may be connected only temporarily.
As illustrated in
Generally speaking, the abnormal situation prevention system 35 may communicate with (or include) abnormal operation detection systems, modules or tools (not shown in
By way of background, OPC is a standard that establishes a mechanism for accessing process data from the plant or process control system. Typically, an OPC server is implemented in a process control system to expose or provide process information from, for example, field devices. An OPC client creates a connection to an OPC server and writes or reads process information to or from a field device. OPC servers use OLE technology (i.e., Component Object Model or COM) to communicate with such clients so that the software applications implemented by the clients can access data from the field devices or other process plant equipment.
The portion 50 of the process plant 10 illustrated in
In any event, one or more user interfaces or computers 72 and 74 (which may be any types of personal computers, workstations, etc.) accessible by plant personnel such as configuration engineers, process control operators, maintenance personnel, plant managers, supervisors, etc. are coupled to the process controllers 60 via a communication line or bus 76 which may be implemented using any desired hardwired or wireless communication structure, and using any desired or suitable communication protocol such as, for example, an Ethernet protocol. In addition, a database 78 may be connected to the communication bus 76 to operate as a data historian that collects and stores configuration information as well as on-line process variable data, parameter data, status data, and other data associated with the process controllers 60 and field devices 64 and 66 within the process plant 10. Thus, the database 78 may operate as a configuration database to store the current configuration, including process configuration modules, as well as control configuration information for the process control system 54 as downloaded to and stored within the process controllers 60 and the field devices 64 and 66. Likewise, the database 78 may store historical abnormal situation prevention data, including statistical data collected by the field devices 64 and 66 within the process plant 10, statistical data determined from process variables collected by the field devices 64 and 66, and other types of data that will be described below.
While the process controllers 60, I/O devices 68 and 70, and field devices 64 and 66 are typically located down within and distributed throughout the sometimes harsh plant environment, the workstations 72 and 74, and the database 78 are usually located in control rooms, maintenance rooms or other less harsh environments easily accessible by operators, maintenance personnel, etc.
Generally speaking, the process controllers 60 store and execute one or more controller applications that implement control strategies using a number of different, independently executed, control modules or blocks. The control modules may each be made up of what are commonly referred to as function blocks, wherein each function block is a part or a subroutine of an overall control routine and operates in conjunction with other function blocks (via communications called links) to implement process control loops within the process plant 10. Function blocks typically perform one of an input function, such as that associated with a transmitter, a sensor or other process parameter measurement device, a control function, such as that associated with a control routine that performs PID, fuzzy logic, etc. control, or an output function, which controls the operation of some device, such as a valve, to perform some physical function within the process plant 10. Of course, hybrid and other types of complex function blocks exist, such as model predictive controllers (MPCs), optimizers, etc. It is to be understood that while the fieldbus protocol and the DeltaV™ system use control modules and function blocks designed and implemented in an object-oriented programming language, the control modules may be designed using any desired control programming scheme including, for example, sequential function blocks, ladder logic, etc., and are not limited to being designed using function blocks or any other particular programming technique.
As illustrated in
Each of one or more of the field devices 64 and 66 may include a memory (not shown) for storing routines such as routines for implementing statistical data collection pertaining to one or more process variables sensed by sensing device and/or routines for abnormal operation detection, which will be described below. Each of one or more of the field devices 64 and 66 may also include a processor (not shown) that executes routines such as routines for implementing statistical data collection and/or routines for abnormal operation detection. Statistical data collection and/or abnormal operation detection need not be implemented by software. Rather, one of ordinary skill in the art will recognize that such systems may be implemented by any combination of software, firmware, and/or hardware within one or more field devices and/or other devices.
As shown in
Generally speaking, the blocks 80 and 82 or sub-elements of these blocks, collect data, such as process variable data, from the device in which they are located and/or from other devices. Additionally, the blocks 80 and 82 or sub-elements of these blocks may process the variable data and perform an analysis on the data for any number of reasons. For example, the block 80, which is illustrated as being associated with a valve, may have a stuck valve detection routine which analyzes the valve position to determine if the valve is in a stuck condition. In addition, the block 80 may include a set of one or more statistical process monitoring (SPM) blocks or units such as blocks SPM1-SPM4 which may collect process variable or other data within the field device and perform one or more statistical calculations on the collected data to determine, for example, a mean, a median, a standard deviation, a root-mean-square (RMS), a rate of change, a range, a minimum, a maximum, etc. of the collected data and/or to detect events such as drift, bias, noise, spikes, etc., in the collected data. Neither the specific statistical data generated, nor the method in which it is generated, is critical. Thus, different types of statistical data can be generated in addition to, or instead of, the specific types described above. Additionally, a variety of techniques, including known techniques, can be used to generate such data. The term statistical process monitoring (SPM) block is used herein to describe functionality that performs statistical process monitoring on at least one process variable or other process parameter, and may be performed by any desired software, firmware or hardware within the device or even outside of a device for which data is collected. It will be understood that, because the SPM blocks are generally located in the devices where the device data is collected, the SPM blocks can acquire quantitatively more and qualitatively more accurate process variable data. As a result, the SPM blocks are generally capable of determining better statistical calculations with respect to the collected process variable data than a block located outside of the device in which the process variable data is collected.
It is to be understood that although the blocks 80 and 82 are shown to include SPM blocks in
It is to be understood that although the blocks 80 and 82 are shown to include SPM blocks in
The block 82 of
Further details regarding the implementation and configuration of abnormal situation prevention systems and components thereof can be found in U.S. Pat. Publ. No. 2005/0197803, now U.S. Pat. No. 7,079,984 (“abnormal situation prevention in a process plant”), U.S. Pat. Publ. No. 2005/0197806 (“Configuration system and method for abnormal situation prevention in a process plant”), and U.S. Pat. Publ. No. 2005/0197805 (“Data presentation system for abnormal situation prevention in the process plant”), each of which is hereby incorporated by reference for all purposes.
In the abnormal situation prevention systems and techniques described above and in the referenced documents, the SPM (or abnormal situation prevention) blocks 80, 82 may be associated with, or considered components of, one or more abnormal situation prevention modules. While abnormal situation prevention blocks may reside in a controller 60 or other host system or device, such as a computer or workstation 72, 74, the abnormal situation prevention modules may take data from one or more abnormal situation prevention blocks and use the data to make a decision about the larger system. More generally, an abnormal situation prevention module may be developed and configured to receive data from one or more function blocks (e.g., abnormal situation prevention blocks) to support diagnostics for each type of field device, instrumentation or other equipment (e.g., valve, pump, etc.). Nonetheless, the function blocks associated with an abnormal situation prevention module may reside and be implemented by devices other than the specific equipment for which it was developed. In such cases, the abnormal situation prevention module has a distributed nature. Other abnormal situation prevention modules may be implemented entirely within one device, such as the process controller 60, despite being directed toward diagnostics for a specific field device. In any event, a diagnostics routine or technique may be developed for each equipment type for detecting, predicting and preventing abnormal situations or abnormal operation of the equipment (or process). For ease in description only, the term “abnormal situation prevention module” will be used herein to refer to such routines or techniques. An abnormal situation prevention module is therefore responsive to a set of measurements needed to perform the diagnostics, and further includes (i) a set of abnormal conditions to be detected by the module, and (ii) a set of rules, which link a change in the measurements to a corresponding abnormal condition. Furthermore, references to abnormal situation prevention modules in the description of the disclosed techniques to follow are set forth with the understanding that the techniques may be utilized in conjunction with abnormal situation prevention blocks as well.
In some cases, the configuration application 38 or other component of the abnormal situation prevention system 35 may support the development or generation of a template for each abnormal situation prevention module. For example, the configuration and development platform provided by the DeltaV™ control system may be used to create specific instances, or instantiations, of abnormal situation prevention modules from corresponding composite template blocks.
Although shown and described in connection with
As described above, and as shown in
The abnormal situation prevention blocks located in various field devices 15,16, rotating equipment 20, power generation equipment 25 or other equipment, may be configured to collect data, perform statistical process monitoring (SPM) on collected data, and perform statistical analysis on collected data and various statistical measures calculated by SPM blocks to evaluate various operating conditions of the process and to detect the occurrence of abnormal situations. For example, an abnormal situation prevention block may be configured to detect whether a valve is stuck in an improper position, or whether a process line is plugged, as indicated by the abnormal situation prevention blocks 80, 82 shown in
abnormal situation prevention modules and SPM blocks located within the process control equipment from which they receive data are capable of sampling the data at a much faster rate than is possible when the abnormal situation prevention and SPM modules are remote from the devices that actually sense the data, due to limitations of the communication channel and the communication protocol. Therefore, an advantage of locating an abnormal situation prevention block and any associated SPM blocks directly within the device from which the data are generated is that the amount and quality of the data that may be analyzed is significantly improved. Therefore, the accuracy of the calculations, the quality of the analysis, and the confidence one may have in the conclusions drawn therefrom are improved as well.
An abnormal situation prevention block detects an abnormal situation when one or more measured process variables or statistical measures run contrary to the rule defining the corresponding abnormal condition. When an abnormal situation prevention block detects an abnormal situation or the occurrence of an abnormal event, the abnormal situation prevention block alerts the controller 60 or other control device that an abnormal situation exists, or that an abnormal event has occurred. The abnormal situation prevention block sends the alert via the communication bus 76. The host controller 60 or other control device in turn forwards information regarding the abnormal situation to the abnormal situation prevention computer 30 so that the interface application 40 may cause an alarm or other indicator to be displayed on the display device 30C to alert an operator or other maintenance personnel of the abnormal situation. The operator or other maintenance personnel may then take appropriate steps to resolve the problem that caused the detected abnormal situation.
In addition to detecting the presence of abnormal operating conditions, the data and statistical measures acquired by an abnormal situation prevention module and calculated by the abnormal situation prevention module's associated SPM blocks are used for locally monitoring the particular process control equipment in which they are located and implementing process control functions that are performed by the equipment. Typically, data and statistical calculations underlying the operation of an abnormal situation prevention module and its associated SPM blocks need not be communicated to the higher levels of the distributed process control system. This is especially true when the data are collected at the device at a rate far in excess of the rate at which data may be communicated to the controller or other higher level control device over the communication channel. Nonetheless, the data acquired before and after an abnormal situation arises may provide important clues as to how the abnormal situation arose and how similar abnormal situations may be prevented in the future. For example, data recorded before and immediately following the occurrence of an abnormal situation may include characteristic patterns that would allow a skilled operator or maintenance technician to identify the root cause of the abnormal condition and take steps to prevent it from occurring in the future. Other characteristic patterns in the received data may be sufficient to predict upcoming abnormal situations well in advance so that steps may be taken to prevent the predicted abnormal condition from actually occurring. For example, a sensor that is about to fail may begin exhibiting erratic readings that are nonetheless within an acceptable range as far as the process is concerned. Recognizing the erratic behavior and replacing the sensor before it completely fails may avoid a costly process control failure in the future.
In order to preserve process control data acquired before and after the occurrence of an abnormal event, a smart field device or other intelligent device or equipment implementing an abnormal situation prevention module may include a memory for temporarily storing process control data both in the form of raw variable data, and/or statistical data calculated by SPM blocks associated with the abnormal situation prevention module. The memory may be organized as a first-in-first out memory so that older data are discarded as newer data are recorded. The memory may be sized so that it can store all of the data, including all of the raw process variable values and calculated statistical measures, acquired by the abnormal situation prevention module over a designated period of time. The length of time for which data are collected and stored can be determined based on the amount of data necessary to analyze the particular abnormal event being detected. For example, for a particular abnormal event it may be beneficial to analyze all of the data acquired by an abnormal situation prevention block in the minute immediately preceding the occurrence of abnormal event and the first minute immediately following the occurrence of the abnormal event. In this case, the memory must be large enough to store two minutes worth of acquired data. In another case, it may only be necessary to view only 15 seconds worth of data before the abnormal event and 45 seconds of data following the event. In this case, the memory must be capable of storing just one minute of acquired data. One may envision scenarios in which widely varying amounts of data may need to be stored in the memory associated with a smart device for future off-line analysis to discover the causes of various abnormal situations and to prevent their occurrence in the future.
As mentioned above, the buffer memory may be organized as a first-in first-out memory such that the oldest data stored in the memory are discarded as new process variable data are acquired and stored. In effect, the data stored in the memory provide a “rolling window” or “snapshot” of the process variable data acquired by the abnormal situation prevention module over a period of time. The rolling window or snapshot moves forward in time, always including the most recently acquired data and discarding older data. When the abnormal situation prevention module detects an abnormal situation it freezes the data stored in the memory, preserving a snapshot of the data acquired by the abnormal situation prevention module at a particular moment in time, namely the period immediately preceding the abnormal event and, if desired, the period immediately following.
Operation of a smart field device or other intelligent device equipped with an abnormal situation prevention module adapted to retain data and statistical measurements acquired before, during and after the occurrence of an abnormal event is best explained by way of example.
The memory 112 is configured as a first-in first-out memory. Data that are older than one minute are discarded as new data are acquired and stored in the memory 112. Thus, the data stored in the memory 112 represents a continuously moving window or snapshot of the data acquired by the abnormal situation prevention module. The moving snapshot effect can be seen in
Returning to
Forty-five seconds after the occurrence of the abnormal event, the memory 112 holds all the historical process variable data from the desired time period 132, namely the fifteen seconds recorded before the occurrence of the abnormal situation and the forty-five seconds following the occurrence of the abnormal situation, as shown in
The data captured in the buffer memory 112 is captured at a rate that is faster than the rate at which the captured data can be communicated to the controller 102 or to other higher level control devices over the communication bus 104. Therefore, the data may not be communicated to the controller as they are captured in real time. However, once the data surrounding the occurrence of an abnormal event have been preserved in the memory 112, they may be communicated to the controller 102 or to another control device at a later time and at a slower rate that is compatible with the limitations of the communication bus 104. Furthermore, the data may be broken up into smaller quantities or data packets and sent to the controller 102 or other control device piecemeal to further reduce the demands on the communication bus 102.
The preserved process variable data may eventually be displayed by the abnormal situation prevention interface application 40 (
The present invention has been described with reference to specific examples. These examples are intended to be illustrative only and should not be read as limiting the invention in any way. It will be apparent to those of ordinary skill in the art that changes, additions or deletions may be made to the disclosed embodiments without departing from the spirit and scope of the invention.
Number | Name | Date | Kind |
---|---|---|---|
3096434 | King | Jul 1963 | A |
3404264 | Kugler | Oct 1968 | A |
3701280 | Stroman | Oct 1972 | A |
3705516 | Reis | Dec 1972 | A |
3981836 | Pangle, Jr. et al. | Sep 1976 | A |
RE29383 | Gallatin et al. | Sep 1977 | E |
4058275 | Banks et al. | Nov 1977 | A |
4099413 | Ohte et al. | Jul 1978 | A |
4322976 | Sisson et al. | Apr 1982 | A |
4337516 | Murphy et al. | Jun 1982 | A |
4408285 | Sisson et al. | Oct 1983 | A |
4425798 | Nagai et al. | Jan 1984 | A |
4435770 | Shiohata et al. | Mar 1984 | A |
4493042 | Shima et al. | Jan 1985 | A |
4517468 | Kemper et al. | May 1985 | A |
4527271 | Hallee et al. | Jul 1985 | A |
4530234 | Cullick et al. | Jul 1985 | A |
4607325 | Horn | Aug 1986 | A |
4635214 | Kasai et al. | Jan 1987 | A |
4642782 | Kemper et al. | Feb 1987 | A |
4644478 | Stephens et al. | Feb 1987 | A |
4644749 | Somes | Feb 1987 | A |
4649515 | Thompson et al. | Mar 1987 | A |
4657179 | Aggers et al. | Apr 1987 | A |
4683542 | Taniguti | Jul 1987 | A |
4707796 | Calabro et al. | Nov 1987 | A |
4734873 | Malloy et al. | Mar 1988 | A |
4758964 | Bittner et al. | Jul 1988 | A |
4763243 | Barlow et al. | Aug 1988 | A |
4764862 | Barlow et al. | Aug 1988 | A |
4770543 | Burghoff et al. | Sep 1988 | A |
4777585 | Kokawa et al. | Oct 1988 | A |
4819233 | Delucia et al. | Apr 1989 | A |
4831564 | Suga et al. | May 1989 | A |
4843557 | Ina et al. | Jun 1989 | A |
4853175 | Book, Sr. | Aug 1989 | A |
4858144 | Marsaly et al. | Aug 1989 | A |
4873655 | Kondraske | Oct 1989 | A |
4885694 | Pray et al. | Dec 1989 | A |
4885707 | Nichol et al. | Dec 1989 | A |
4907167 | Skeirik | Mar 1990 | A |
4910691 | Skeirik | Mar 1990 | A |
4922412 | Lane et al. | May 1990 | A |
4924418 | Bachman et al. | May 1990 | A |
4934196 | Romano | Jun 1990 | A |
4942514 | Miyagaki et al. | Jul 1990 | A |
4944035 | Roger et al. | Jul 1990 | A |
4956793 | Bonne et al. | Sep 1990 | A |
4964125 | Kim | Oct 1990 | A |
4965742 | Skeirik | Oct 1990 | A |
4980844 | Demjanenko et al. | Dec 1990 | A |
4992965 | Holter et al. | Feb 1991 | A |
5005142 | Lipchak et al. | Apr 1991 | A |
5006992 | Skeirik | Apr 1991 | A |
5008810 | Kessel et al. | Apr 1991 | A |
5015934 | Holley et al. | May 1991 | A |
5018215 | Nasr et al. | May 1991 | A |
5043862 | Takahashi et al. | Aug 1991 | A |
5043863 | Bristol et al. | Aug 1991 | A |
5050095 | Samad | Sep 1991 | A |
5053815 | Wendell | Oct 1991 | A |
5070458 | Gilmore et al. | Dec 1991 | A |
5081598 | Bellows et al. | Jan 1992 | A |
5089978 | Lipner et al. | Feb 1992 | A |
5089984 | Struger et al. | Feb 1992 | A |
5094107 | Schoch | Mar 1992 | A |
5098197 | Shepard et al. | Mar 1992 | A |
5099436 | McCown et al. | Mar 1992 | A |
5103409 | Shimizu et al. | Apr 1992 | A |
5111531 | Grayson et al. | May 1992 | A |
5121467 | Skeirik | Jun 1992 | A |
5122976 | Bellows et al. | Jun 1992 | A |
5130936 | Sheppard et al. | Jul 1992 | A |
5134574 | Beaverstock et al. | Jul 1992 | A |
5140530 | Guha et al. | Aug 1992 | A |
5142612 | Skeirik | Aug 1992 | A |
5148378 | Shibayama et al. | Sep 1992 | A |
5158667 | Barlow et al. | Oct 1992 | A |
5161013 | Rylander et al. | Nov 1992 | A |
5167009 | Skeirik | Nov 1992 | A |
5175678 | Frerichs et al. | Dec 1992 | A |
5187674 | Bonne | Feb 1993 | A |
5189232 | Shabtai et al. | Feb 1993 | A |
5193143 | Kaemmerer et al. | Mar 1993 | A |
5197114 | Skeirik | Mar 1993 | A |
5197328 | Fitzgerald | Mar 1993 | A |
5200028 | Tatsumi et al. | Apr 1993 | A |
5200958 | Hamilton et al. | Apr 1993 | A |
5210704 | Husseiny | May 1993 | A |
5212765 | Skeirik | May 1993 | A |
5214582 | Gray | May 1993 | A |
5224203 | Skeirik | Jun 1993 | A |
5228780 | Shepard et al. | Jul 1993 | A |
5235527 | Ogawa et al. | Aug 1993 | A |
5251151 | Demjanenko et al. | Oct 1993 | A |
5258113 | Edgerton et al. | Nov 1993 | A |
5265031 | Malczewski | Nov 1993 | A |
5265222 | Nishiya et al. | Nov 1993 | A |
5274572 | O'Neill et al. | Dec 1993 | A |
5282131 | Rudd et al. | Jan 1994 | A |
5282261 | Skeirik | Jan 1994 | A |
5291190 | Scarola et al. | Mar 1994 | A |
5293585 | Morita | Mar 1994 | A |
5301101 | MacArthur et al. | Apr 1994 | A |
5303181 | Stockton | Apr 1994 | A |
5305230 | Matsumoto et al. | Apr 1994 | A |
5311421 | Nomura et al. | May 1994 | A |
5311447 | Bonne | May 1994 | A |
5311562 | Palosamy et al. | May 1994 | A |
5315521 | Hanson et al. | May 1994 | A |
5317520 | Castle | May 1994 | A |
5325522 | Vaughn | Jun 1994 | A |
5327357 | Feinstein et al. | Jul 1994 | A |
5329443 | Bonaquist et al. | Jul 1994 | A |
5333240 | Matsumoto et al. | Jul 1994 | A |
5333298 | Bland et al. | Jul 1994 | A |
5347449 | Meyer et al. | Sep 1994 | A |
5349541 | Alexandro, Jr. et al. | Sep 1994 | A |
5351184 | Lu et al. | Sep 1994 | A |
5353207 | Keeler et al. | Oct 1994 | A |
5353315 | Scarola et al. | Oct 1994 | A |
5361612 | Voiculescu et al. | Nov 1994 | A |
5369581 | Ohsuga et al. | Nov 1994 | A |
5369599 | Sadjadi et al. | Nov 1994 | A |
5373452 | Guha | Dec 1994 | A |
5384698 | Jelinek | Jan 1995 | A |
5384699 | Levy et al. | Jan 1995 | A |
5386373 | Keeler et al. | Jan 1995 | A |
5390287 | Obata et al. | Feb 1995 | A |
5390326 | Shah | Feb 1995 | A |
5394341 | Kepner | Feb 1995 | A |
5394543 | Hill et al. | Feb 1995 | A |
5396415 | Konar et al. | Mar 1995 | A |
5398303 | Tanaka | Mar 1995 | A |
5400246 | Wilson et al. | Mar 1995 | A |
5404064 | Mermelstein et al. | Apr 1995 | A |
5408406 | Mathur et al. | Apr 1995 | A |
5408586 | Skeirik | Apr 1995 | A |
5414645 | Hirano et al. | May 1995 | A |
5419197 | Ogi et al. | May 1995 | A |
5430642 | Nakajima et al. | Jul 1995 | A |
5431460 | Hass et al. | Jul 1995 | A |
5440478 | Fisher et al. | Aug 1995 | A |
5442544 | Jelinek | Aug 1995 | A |
5461570 | Wang et al. | Oct 1995 | A |
5467355 | Umeda et al. | Nov 1995 | A |
5469735 | Watanabe et al. | Nov 1995 | A |
5483387 | Bauhahn et al. | Jan 1996 | A |
5485753 | Burns et al. | Jan 1996 | A |
5486920 | Killpatrick et al. | Jan 1996 | A |
5486996 | Samad et al. | Jan 1996 | A |
5488697 | Kaemmerer et al. | Jan 1996 | A |
5489831 | Harris | Feb 1996 | A |
5499188 | Kline, Jr. et al. | Mar 1996 | A |
5500941 | Gil et al. | Mar 1996 | A |
5504863 | Yoshida et al. | Apr 1996 | A |
5511004 | Dubost et al. | Apr 1996 | A |
5511442 | Tame | Apr 1996 | A |
5519647 | DeVille | May 1996 | A |
5521814 | Teran et al. | May 1996 | A |
5521842 | Yamoda | May 1996 | A |
5528510 | Kraft | Jun 1996 | A |
5533413 | Kobayashi et al. | Jul 1996 | A |
5537310 | Tanake et al. | Jul 1996 | A |
5541833 | Bristol et al. | Jul 1996 | A |
5546301 | Agrawal et al. | Aug 1996 | A |
5548528 | Keeler et al. | Aug 1996 | A |
5552984 | Crandall et al. | Sep 1996 | A |
5559690 | Keeler et al. | Sep 1996 | A |
5561599 | Lu | Oct 1996 | A |
5566065 | Hansen et al. | Oct 1996 | A |
5570282 | Hansen et al. | Oct 1996 | A |
5570300 | Henry et al. | Oct 1996 | A |
5572420 | Lu | Nov 1996 | A |
5574638 | Lu | Nov 1996 | A |
5586066 | White et al. | Dec 1996 | A |
5596704 | Geddes et al. | Jan 1997 | A |
5598521 | Kilgore et al. | Jan 1997 | A |
5600148 | Cole et al. | Feb 1997 | A |
5602757 | Haseley et al. | Feb 1997 | A |
5602761 | Spoerre et al. | Feb 1997 | A |
5604914 | Kabe | Feb 1997 | A |
5606513 | Louwagie et al. | Feb 1997 | A |
5610339 | Haseley et al. | Mar 1997 | A |
5623598 | Voigt et al. | Apr 1997 | A |
5625574 | Griffiths et al. | Apr 1997 | A |
5628994 | Kaper et al. | May 1997 | A |
5631825 | van Weele et al. | May 1997 | A |
5640491 | Bhat et al. | Jun 1997 | A |
5640493 | Skeirik | Jun 1997 | A |
5646350 | Robinson et al. | Jul 1997 | A |
5654841 | Hobson et al. | Aug 1997 | A |
5665906 | Bayer | Sep 1997 | A |
5666297 | Britt et al. | Sep 1997 | A |
5671335 | Davis et al. | Sep 1997 | A |
5671351 | Wild et al. | Sep 1997 | A |
5675504 | Serodes et al. | Oct 1997 | A |
5680409 | Qin et al. | Oct 1997 | A |
5682309 | Bartusiak et al. | Oct 1997 | A |
5687090 | Chen et al. | Nov 1997 | A |
5691895 | Kurtzberg et al. | Nov 1997 | A |
5692158 | Degeneff et al. | Nov 1997 | A |
5698788 | Mol et al. | Dec 1997 | A |
5704011 | Hansen et al. | Dec 1997 | A |
5715158 | Chen | Feb 1998 | A |
5719767 | Jang et al. | Feb 1998 | A |
5729661 | Keeler et al. | Mar 1998 | A |
5740324 | Mathur et al. | Apr 1998 | A |
5742513 | Bouhenguel et al. | Apr 1998 | A |
5753802 | Falkler | May 1998 | A |
5754451 | Williams | May 1998 | A |
5757371 | Oran et al. | May 1998 | A |
5757748 | Kiyoura et al. | May 1998 | A |
5761518 | Boehling et al. | Jun 1998 | A |
5764891 | Warrior | Jun 1998 | A |
5768119 | Havekost et al. | Jun 1998 | A |
5777872 | He | Jul 1998 | A |
5781432 | Keeler et al. | Jul 1998 | A |
5781878 | Mizoguchi et al. | Jul 1998 | A |
5790898 | Kishima et al. | Aug 1998 | A |
5796602 | Wellan et al. | Aug 1998 | A |
5796606 | Spring | Aug 1998 | A |
5796609 | Tao et al. | Aug 1998 | A |
5798939 | Ochoa et al. | Aug 1998 | A |
5803724 | Oortwijn et al. | Sep 1998 | A |
5805442 | Crater et al. | Sep 1998 | A |
5809490 | Guiver et al. | Sep 1998 | A |
5812394 | Lewis et al. | Sep 1998 | A |
5819050 | Boehling et al. | Oct 1998 | A |
5819232 | Shipman | Oct 1998 | A |
5825645 | Konar et al. | Oct 1998 | A |
5826249 | Skeirik | Oct 1998 | A |
5838561 | Owen et al. | Nov 1998 | A |
5842189 | Keeler et al. | Nov 1998 | A |
5847952 | Samad | Dec 1998 | A |
5848365 | Coverdill | Dec 1998 | A |
5855791 | Hays et al. | Jan 1999 | A |
5859773 | Keeler et al. | Jan 1999 | A |
5859885 | Rusnica et al. | Jan 1999 | A |
5859964 | Wang et al. | Jan 1999 | A |
5875420 | Piety et al. | Feb 1999 | A |
5877954 | Klimasauskas et al. | Mar 1999 | A |
5880716 | Kunugi | Mar 1999 | A |
5892679 | He | Apr 1999 | A |
5892939 | Call et al. | Apr 1999 | A |
5898869 | Anderson | Apr 1999 | A |
5901058 | Steinman et al. | May 1999 | A |
5903455 | Sharpe, Jr. et al. | May 1999 | A |
5905989 | Biggs | May 1999 | A |
5907701 | Hanson | May 1999 | A |
5909370 | Lynch | Jun 1999 | A |
5909541 | Sampson et al. | Jun 1999 | A |
5909586 | Anderson | Jun 1999 | A |
5914875 | Monta et al. | Jun 1999 | A |
5918233 | La Chance et al. | Jun 1999 | A |
5922963 | Piety et al. | Jul 1999 | A |
5924086 | Mathur et al. | Jul 1999 | A |
5940290 | Dixon | Aug 1999 | A |
5948101 | David et al. | Sep 1999 | A |
5949417 | Calder | Sep 1999 | A |
5951654 | Avsan et al. | Sep 1999 | A |
5960214 | Sharpe, Jr. et al. | Sep 1999 | A |
5960441 | Bland et al. | Sep 1999 | A |
5975737 | Crater et al. | Nov 1999 | A |
5984502 | Calder | Nov 1999 | A |
5988847 | McLaughlin et al. | Nov 1999 | A |
5995916 | Nixon et al. | Nov 1999 | A |
5997167 | Crater et al. | Dec 1999 | A |
6006171 | Vines et al. | Dec 1999 | A |
6008985 | Lake et al. | Dec 1999 | A |
6014598 | Duyar et al. | Jan 2000 | A |
6014612 | Larson et al. | Jan 2000 | A |
6014876 | Taylor | Jan 2000 | A |
6017143 | Eryurek et al. | Jan 2000 | A |
6026352 | Burns et al. | Feb 2000 | A |
6033257 | Lake et al. | Mar 2000 | A |
6035339 | Agraharam et al. | Mar 2000 | A |
6038486 | Saitoh et al. | Mar 2000 | A |
6041263 | Boston et al. | Mar 2000 | A |
6047220 | Eryurek | Apr 2000 | A |
6047221 | Piche et al. | Apr 2000 | A |
6055483 | Lu | Apr 2000 | A |
6061603 | Papadopoulos et al. | May 2000 | A |
6061640 | Tanaka et al. | May 2000 | A |
6067505 | Bonoyer et al. | May 2000 | A |
6076124 | Korowitz et al. | Jun 2000 | A |
6078843 | Shavit | Jun 2000 | A |
6093211 | Hamielec et al. | Jul 2000 | A |
6106785 | Havlena et al. | Aug 2000 | A |
6108616 | Borchers et al. | Aug 2000 | A |
6110214 | Klimasauskas | Aug 2000 | A |
6119047 | Eryurek et al. | Sep 2000 | A |
6122555 | Lu | Sep 2000 | A |
6128279 | O'Neil et al. | Oct 2000 | A |
6134032 | Kram et al. | Oct 2000 | A |
6134574 | Oberman et al. | Oct 2000 | A |
6144952 | Keeler et al. | Nov 2000 | A |
6169980 | Keeler et al. | Jan 2001 | B1 |
6185470 | Pado et al. | Feb 2001 | B1 |
6197480 | Iguchi et al. | Mar 2001 | B1 |
6246950 | Bessler et al. | Jun 2001 | B1 |
6246972 | Klimasauskas | Jun 2001 | B1 |
6259959 | Martin | Jul 2001 | B1 |
6266726 | Nixon et al. | Jul 2001 | B1 |
6298377 | Hartikainen et al. | Oct 2001 | B1 |
6298454 | Schleiss et al. | Oct 2001 | B1 |
6317638 | Schreder et al. | Nov 2001 | B1 |
6317701 | Pyotsia et al. | Nov 2001 | B1 |
6332110 | Wolfe | Dec 2001 | B1 |
6387114 | Adams | May 2002 | B2 |
6389331 | Jensen et al. | May 2002 | B1 |
6391114 | Kirimura | May 2002 | B1 |
6397114 | Eryurek | May 2002 | B1 |
6400681 | Bertin et al. | Jun 2002 | B1 |
6418465 | Hirosawa et al. | Jul 2002 | B1 |
6421571 | Spriggs et al. | Jul 2002 | B1 |
6445963 | Blevins et al. | Sep 2002 | B1 |
6507797 | Kliman et al. | Jan 2003 | B1 |
6529780 | Soergel et al. | Mar 2003 | B1 |
6532392 | Eryurek et al. | Mar 2003 | B1 |
6535769 | Konar et al. | Mar 2003 | B1 |
6539267 | Eryurek et al. | Mar 2003 | B1 |
6549130 | Joao | Apr 2003 | B1 |
6567718 | Campbell et al. | May 2003 | B1 |
6571273 | Shirai et al. | May 2003 | B1 |
6591260 | Schwarzhoff et al. | Jul 2003 | B1 |
6594589 | Coss, Jr. et al. | Jul 2003 | B1 |
6601005 | Eryurek et al. | Jul 2003 | B1 |
6601995 | Harrison et al. | Aug 2003 | B1 |
6609036 | Bickford | Aug 2003 | B1 |
6609040 | Brunnemann | Aug 2003 | B1 |
6615090 | Blevins et al. | Sep 2003 | B1 |
6628994 | Turicchi, Jr. et al. | Sep 2003 | B1 |
6633782 | Schleiss et al. | Oct 2003 | B1 |
6651012 | Bechhoefer | Nov 2003 | B1 |
6654697 | Eryurek et al. | Nov 2003 | B1 |
6690274 | Bristol | Feb 2004 | B1 |
6704689 | Hogan et al. | Mar 2004 | B1 |
6717513 | Sandelman et al. | Apr 2004 | B1 |
6721609 | Wojsznis | Apr 2004 | B1 |
6732191 | Baker et al. | May 2004 | B1 |
6738388 | Stevenson et al. | May 2004 | B1 |
6758168 | Koskinen et al. | Jul 2004 | B2 |
6760782 | Swales | Jul 2004 | B1 |
6769171 | Jung et al. | Aug 2004 | B2 |
6774786 | Havekost | Aug 2004 | B1 |
6813532 | Eryurek et al. | Nov 2004 | B2 |
6836705 | Hellmann et al. | Dec 2004 | B2 |
6907383 | Eryurek et al. | Jun 2005 | B2 |
6965806 | Eryurek et al. | Nov 2005 | B2 |
7076380 | Michel | Jul 2006 | B2 |
7079984 | Eryurek et al. | Jul 2006 | B2 |
7085610 | Eryurek et al. | Aug 2006 | B2 |
7233834 | McDonald, Jr. et al. | Jun 2007 | B2 |
7395139 | Burton et al. | Jul 2008 | B2 |
7533070 | Guralnik et al. | May 2009 | B2 |
20020022894 | Eryurek et al. | Feb 2002 | A1 |
20020029130 | Eryurek et al. | Mar 2002 | A1 |
20020038156 | Eryurek et al. | Mar 2002 | A1 |
20020067370 | Forney et al. | Jun 2002 | A1 |
20020077711 | Nixon et al. | Jun 2002 | A1 |
20020107858 | Lundahl et al. | Aug 2002 | A1 |
20020133320 | Wegerich et al. | Sep 2002 | A1 |
20020147511 | Eryurek et al. | Oct 2002 | A1 |
20020161940 | Eryurek et al. | Oct 2002 | A1 |
20020163427 | Eryurek et al. | Nov 2002 | A1 |
20030002969 | Risser | Jan 2003 | A1 |
20030009572 | Thurner | Jan 2003 | A1 |
20030014226 | Loecher et al. | Jan 2003 | A1 |
20030014500 | Schleiss et al. | Jan 2003 | A1 |
20030028268 | Eryurek et al. | Feb 2003 | A1 |
20030028269 | Spriggs et al. | Feb 2003 | A1 |
20030065409 | Raeth et al. | Apr 2003 | A1 |
20030074159 | Bechhoefer et al. | Apr 2003 | A1 |
20030121330 | Muhle et al. | Jul 2003 | A1 |
20030172002 | Spira et al. | Sep 2003 | A1 |
20030195934 | Peterson et al. | Oct 2003 | A1 |
20030236579 | Hauhia et al. | Dec 2003 | A1 |
20040052526 | Jones et al. | Mar 2004 | A1 |
20040064465 | Yadav et al. | Apr 2004 | A1 |
20040067645 | Chen et al. | Apr 2004 | A1 |
20040068392 | Mylaraswamy | Apr 2004 | A1 |
20040075689 | Schleiss et al. | Apr 2004 | A1 |
20040078171 | Wegerich et al. | Apr 2004 | A1 |
20040095237 | Chen et al. | May 2004 | A1 |
20040158772 | Pan et al. | Aug 2004 | A1 |
20040167686 | Baker et al. | Aug 2004 | A1 |
20040181364 | Reeves et al. | Sep 2004 | A1 |
20040249583 | Eryurek et al. | Dec 2004 | A1 |
20050007249 | Eryurek et al. | Jan 2005 | A1 |
20050015624 | Ginter et al. | Jan 2005 | A1 |
20050060103 | Chamness | Mar 2005 | A1 |
20050143873 | Wilson | Jun 2005 | A1 |
20050197792 | Haeuptle | Sep 2005 | A1 |
20050197803 | Eryurek et al. | Sep 2005 | A1 |
20050197805 | Eryurek et al. | Sep 2005 | A1 |
20050197806 | Eryurek et al. | Sep 2005 | A1 |
20050240289 | Hoyte et al. | Oct 2005 | A1 |
20050251579 | Ngo et al. | Nov 2005 | A1 |
20050256601 | Lee et al. | Nov 2005 | A1 |
20050267709 | Heavner et al. | Dec 2005 | A1 |
20060020423 | Sharpe, Jr. | Jan 2006 | A1 |
20060047489 | Scheidt et al. | Mar 2006 | A1 |
20060052991 | Pflugl et al. | Mar 2006 | A1 |
20060067388 | Sedarat | Mar 2006 | A1 |
20060074598 | Emigholz et al. | Apr 2006 | A1 |
20060157029 | Suzuki et al. | Jul 2006 | A1 |
20060206288 | Brahmajosyula et al. | Sep 2006 | A1 |
20060265625 | Dubois et al. | Nov 2006 | A1 |
20070005298 | Allen et al. | Jan 2007 | A1 |
20070010900 | Kavaklioglu et al. | Jan 2007 | A1 |
20070017291 | Cypes et al. | Jan 2007 | A1 |
20070097873 | Ma et al. | May 2007 | A1 |
20070109301 | Smith | May 2007 | A1 |
20080027678 | Miller | Jan 2008 | A1 |
20090112335 | Mehta et al. | Apr 2009 | A1 |
Number | Date | Country |
---|---|---|
1007757 | Apr 1990 | CN |
1097804 | Jan 1995 | CN |
1267373 | Sep 2000 | CN |
35 40 204 | Sep 1986 | DE |
40 08 560 | Sep 1990 | DE |
44 33 593 | Jun 1995 | DE |
195 02 499 | Aug 1996 | DE |
101 14 206 | Nov 2001 | DE |
102 32 164 | Feb 2004 | DE |
0 122 622 | Oct 1984 | EP |
0 362 386 | Apr 1990 | EP |
0 377 736 | Jul 1990 | EP |
0 413 814 | Feb 1991 | EP |
0 487 419 | May 1992 | EP |
0 581 451 | Feb 1994 | EP |
0 594 227 | Apr 1994 | EP |
0 612 039 | Aug 1994 | EP |
0 624 847 | Nov 1994 | EP |
0 626 697 | Nov 1994 | EP |
0 644 470 | Mar 1995 | EP |
0 715 160 | Jun 1996 | EP |
0 827 096 | Mar 1998 | EP |
0 959 398 | Nov 1999 | EP |
0 961 184 | Dec 1999 | EP |
0 964 325 | Dec 1999 | EP |
0 965 897 | Dec 1999 | EP |
1 630 348 | Mar 2006 | EP |
1 669 827 | Jun 2006 | EP |
2 083 258 | Mar 1982 | GB |
2 294 129 | Apr 1996 | GB |
2 294 793 | May 1996 | GB |
2 347 234 | Aug 2000 | GB |
2 360 357 | Sep 2001 | GB |
2 379 749 | Mar 2003 | GB |
2 380 833 | Apr 2003 | GB |
2 394 312 | Apr 2004 | GB |
05-7138472 | Aug 1982 | JP |
05-033537 | Feb 1993 | JP |
06-242192 | Sep 1994 | JP |
06-331507 | Dec 1994 | JP |
07-127320 | May 1995 | JP |
07-152714 | Jun 1995 | JP |
07-234988 | Sep 1995 | JP |
08-261886 | Oct 1996 | JP |
10-039728 | Feb 1998 | JP |
10-320039 | Dec 1998 | JP |
11-231924 | Aug 1999 | JP |
2000-305620 | Nov 2000 | JP |
2001-016662 | Jan 2001 | JP |
WO 9838585 | Sep 1998 | WO |
WO 9913418 | Mar 1999 | WO |
WO 0017721 | Mar 2000 | WO |
WO 0050851 | Aug 2000 | WO |
WO 0055700 | Sep 2000 | WO |
WO 0062256 | Oct 2000 | WO |
WO 0179947 | Oct 2001 | WO |
WO 0206919 | Jan 2002 | WO |
WO 0223405 | Mar 2002 | WO |
WO 02071168 | Sep 2002 | WO |
WO 02071169 | Sep 2002 | WO |
WO 02071170 | Sep 2002 | WO |
WO 02071171 | Sep 2002 | WO |
WO 02071172 | Sep 2002 | WO |
WO 02071173 | Sep 2002 | WO |
WO 02095509 | Nov 2002 | WO |
WO 02095510 | Nov 2002 | WO |
WO 02095633 | Nov 2002 | WO |
WO 03019304 | Mar 2003 | WO |
WO 03075206 | Sep 2003 | WO |
WO 2005019948 | Mar 2005 | WO |
WO 2005093531 | Oct 2005 | WO |
WO 2005093534 | Oct 2005 | WO |
WO 2005093535 | Oct 2005 | WO |
WO 2006026340 | Mar 2006 | WO |
WO 2006107933 | Oct 2006 | WO |
WO 2007087729 | Aug 2007 | WO |
WO 2008014349 | Jan 2008 | WO |
WO-2008039992 | Apr 2008 | WO |
WO-2008085706 | Jul 2008 | WO |
Number | Date | Country | |
---|---|---|---|
20090062933 A1 | Mar 2009 | US |