Patent Grant
7272531
The present invention relates generally to process control systems within process plants and, more particularly, to the index aggregation to determine indices at varying levels of hierarchy within and among process plants.
Process control systems, like those used in chemical, petroleum or other processes, typically include one or more centralized or decentralized process controllers communicatively coupled to at least one host or operator workstation and to one or more process control and instrumentation devices, such as field devices, via 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), perform functions within the process such as opening or closing valves and measuring process parameters. The process controller receives 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, uses this information to implement a control routine and then generates control signals which are sent over one or more of the buses to the field devices to control the operation of the process. Information from the field devices and the controller is typically made available to one or more applications executed by an operator workstation to enable an operator to perform desired functions with respect to the process, such as viewing the current state of the process, modifying the operation of the process, etc.
While a typical process control system has many process control and instrumentation devices, such as valves, transmitters, sensors, etc. connected to one or more process controllers which execute software that controls these devices during the operation of the process, there are many other supporting devices which 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, etc., which are located at numerous places in a typical plant.
The various devices within the process plant may be interconnected in physical and/or logical groups to create a logical process, such as a control loop. Likewise, a control loop may be interconnected with other control loops and/or devices to create sub-units. A sub-unit may be interconnected with other sub-units to create a unit, which in turn, may be interconnected with other units to create an area. Process plants generally include interconnected areas, and business entities generally include process plants which may be interconnected. As a result, a process plant includes numerous levels of hierarchy having interconnected assets, and a business enterprise may include interconnected process plants. In other words, assets related to a process plant, or process plants themselves, may be grouped together to form assets at higher levels.
In the typical plant or process, different people are involved in different functions. For example, functions associated with the process control activities, the device and equipment maintenance and monitoring activities, and the business activities such as process performance monitoring may each have a different interest in various levels of the process plant or among process plant. Process control operators generally oversee the day to day operation of the process and are primarily responsible for assuring the quality and continuity of the process operation typically affect the process by setting and changing set points within the process, tuning loops of the process, scheduling process operations such as batch operations, etc. As a result, process control operators may be primarily interested in the status of process loops, sub-unit, units and areas. Of course, this is not always the case, and process control operators may also be interested in the status of devices which may have an effect on the loops, sub-units, unit, areas, etc., for example.
On the other hand, maintenance personnel are primarily responsible for assuring that the actual equipment within the process is operating efficiently and for repairing and replacing malfunctioning equipment, use tools such as maintenance interfaces, as well and many other diagnostic tools which provide information about operating states of the devices within the process. As such, maintenance personnel may be primarily interested the status of devices and control loops, though maintenance personnel may further be interested in the status of sub-unit, units, etc.
Still further, other persons may be responsible for business applications, such as ordering parts, supplies, raw materials, etc., making strategic business decisions such as choosing which products to manufacture, what variables to optimize within the plant, etc. based on process performance measures. Likewise, managers or other persons may want to have access to certain information within the process plant or from other computer systems associated with the process plant for use in overseeing the plant operation and in making long term strategic decisions. Such persons may primarily be interested in status information pertaining to areas within a process plant, the process plant itself and even process plants that make up a business enterprise. As a result, a process plant may involve several persons interested in the status of devices, loops, sub-units, units, areas or the process plant at different hierarchical levels.
Because, for the most part, different personnel are interested in the status of different hierarchical levels within or among process plants, various systems within a process plant monitor and report the status of various devices that are connected to the process control systems of the plant, such as the relative health, performance, utilization, variability of the devices. For example, various systems may monitor the individual devices within a process plant. However, beyond the device level, the problem with this approach is that there are thousands of devices in a typical plant and the status of any single device generally cannot be used to determine the overall status of the loop, sub-unit, unit, area or process plant where the device is found.
Some solutions exist for determining the status of devices, loops, sub-units, units, area and/or plants. For example, it is currently known to provide an asset utilization expert that includes an index generation routine to generate indices related to the health, performance, utilization and variability of various plant assets at different levels of hierarchy. The creation of such indices is disclosed in Eryurek et al., U.S. Pat. No. 6,813,532 entitled “Creation and Display of Indices Within Process Plant” which was filed on Feb. 28, 2002 and issued on Nov. 2, 2004, and which is hereby expressly incorporated by reference herein. One manner in which an index could be generated by the index generation routine was to interconnect various models representing loops, sub-units, units, areas, etc. within the process plant to produce information regarding the operation of each loop, sub-unit, unit, area, etc. and generate an index from the data. Another manner in which an index was generated by the index generation routine was to create an index for each device and create an aggregate index at least level in the system hierarchy. The aggregate index could be a weighted average or a weighted combination of the indices of the assets that made up the larger asset.
However, within a typical process plant, some assets are considered more important than other assets within a group of assets. For example, some devices are considered more critical to the larger loop, sub-unit, unit, area, etc. of which the devices are a part. If such a device were to fail, it would have more of an impact on the loop, sub-unit, unit, area, etc. than if the other devices were to fail. Such a device would therefore deserve priority over the other devices. In turn, the remaining devices may have varying degrees of importance within the loop, sub-unit, unit or area. Likewise, some loops are more important than others among a group of loops interconnected to form a sub-unit, unit, area, etc. Similar situations exist among sub-units, units, area and even among plants. The importance of assets among a group of assets may greatly affect the overall status of the group. However, in the past, the varying degrees of importance among assets were not necessarily taken into account when determining the overall status of a group of assets.
A system and method of monitoring an entity having a plurality of lower level entities, is described herein, which accounts for varying degrees of importance among the lower level entities. In one aspect, use indices pertaining to status information of the lower level entities is acquired. Further, weighting values are acquired. Generally, the weighing value pertains to the importance of a lower level entity among the plurality of lower level, such as the priority or criticality of the lower level entity. The weighing values may be based on the impact and frequency of failure of the lower level entity. The impact and/or frequency of failure may, in turn, be based on maintenance information, process data, diagnostic data, on-line monitoring data and/or heuristic data. An aggregate use index representing status information regarding the entity is creating from a combination of the lower level use indices and weighting values. The aggregate use index may be an aggregate health index indicating the health of the entity, an aggregate performance index indicating the relative performance of the entity, an aggregate variability index indicating an amount of deviation of a parameter of the entity or an aggregate utilization index indicating a degree of exploitation of the entity. The combination of the lower level use indices and weighting values may be a normalized expression, such that the range of values for the use indices is the same among the lower level entities. The combination may involve creating a weighted average of the use indices of the lower level entities.
Referring now to
Still further, maintenance systems, such as computers executing the AMS application or any other device monitoring and communication applications may be connected to the process control systems 12 and 14 or to the individual devices therein to perform maintenance and monitoring 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 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 known monitoring and diagnostic applications 23, for example RBMware™ sold by CSI Systems of Knoxville, Tenn. or other any other known applications used to diagnose, monitor and optimize the operating state of the rotating equipment 20. 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.
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.
A computer system 30 is provided which is communicatively connected to the computers or interfaces associated with the various functional systems within the plant 10, including the process control functions 12 and 14, the maintenance functions such as those implemented in the computers 18, 14A, 22 and 26 and the business functions. In particular, the computer system 30 is communicatively connected to the traditional process control system 12 and to the maintenance interface 18 associated with that control system, is connected to the process control and/or maintenance interfaces 14A of the distributed process control system 14, is connected to the rotating equipment maintenance computer 22 and to the power generation and distribution computer 26, all via a bus 32. The bus 32 may use any desired or appropriate local area network (LAN) or wide area network (WAN) protocol to provide communications.
As illustrated in
In one embodiment, the communications over the bus 32 occur using the XML/XSL protocol. Here, data from each of the computers 12A, 18, 14A, 22, 26, 35, 36, etc. is wrapped in an XML/XSL wrapper and is sent to an XML/XSL data server which may be located in, for example, the computer 30. Because XML/XSL is a descriptive language, the server can process any type of data. At the server, if necessary, the data is encapsulated with a new XML/XSL wrapper, i.e., this data is mapped from one XML/XSL schema to one or more other XML/XSL schemas which are created for each of the receiving applications. Thus, each data originator can wrap its data using a schema understood or convenient for that device or application, and each receiving application can receive the data in a different schema used for or understood by the receiving application. The server is configured to map one schema to another schema depending on the source and destination(s) of the data. If desired, the server may also perform certain data processing functions or other functions based on the receipt of data. The mapping and processing function rules are set up and stored in the server prior to operation of the system described herein. In this manner, data may be sent from any one application to one or more other applications.
Generally speaking, the computer 30 stores and executes an asset utilization expert 50 that collects data and other information generated by the process control systems 12 and 14, the maintenance systems 18, 22 and 26 and the business systems 35 and 36 as well as information generated by data analysis tools executed in each of these systems. The asset utilization expert 50 may be based on, for example, the OZ expert system currently provided by NEXUS. However, the asset utilization expert 50 may be any other desired type of expert system including, for example, any type of data mining system. Importantly, the asset utilization expert 50 operates as a data and information clearinghouse in the process plant 10 and is able to coordinate the distribution of data or information from one functional area, such as the maintenance area, to other functional areas, such as the process control or the business functional areas. The asset utilization expert 50 may also use the collected data to generate new information or data which can be distributed to one or more of the computer systems associated with the different functions within the plant 10. Still further, the asset utilization expert 50 may execute or oversee the execution of other applications that use the collected data to generate new types of data to be used within the process plant 10.
In particular, the asset utilization expert 50 may include or execute index generation software 51 that creates indices associated with devices, like process control and instrumentation devices, power generation devices, rotating equipment, units, areas, etc, or that are associated with process control entities, like loops, etc. within the plant 10. The asset utilization expert 50 may further include or execute an index aggregation routine 60. The index aggregation routine 60 utilizes indices generated by the index generation routine 51 or other index generation routines to create indices associated with various levels within a process control system, or more generally an asset utilization system, which may include one or more process control systems. The index aggregation routine 60 further includes a weighting value when creating an aggregate index associated with a process, unit, area, The index aggregation routine 60 may be provided as a separate routine or as part of the index generation routine 50.
The indices generated by the index generation routine 51 and/or the index aggregation routine 60 can then be provided to the process control applications to help optimize process control and can be provided to the business software or business applications to provide the business persons more complete or understandable information associated with the operation of the plant 10. The asset utilization expert 50 can also provide maintenance data (such as device status information) and business data (such as data associated with scheduled orders, timeframes, etc.) to a control expert 52 associated with, for example, the process control system 14 to help an operator perform control activities such as optimizing control. The control expert 52 may be located in, for example, the user interface 14A or any other computer associated with the control system 14 or within the computer 30 if desired. In one embodiment, the control expert 52 may be, for example, the control expert described in U.S. patent application Ser. Nos. 09/256,585 and 09/499,445 identified above.
Additionally, the asset utilization expert 50 can send information to one or more optimizers 55 within the plant 10. For example, a control optimizer 55 can be located in the computer 14A and can run one or more control optimization routines 55A, 55B, etc. Additionally or alternatively, optimizer routines 55 could be stored in and executed by the computer 30 or any other computer, and the data necessary therefore could be sent by the asset utilization expert 50. If desired, the plant 10 may also include models 56 that model certain aspects of the plant 10 and these models 56 can be executed by the asset utilization expert 50 or a control or other expert such as the control expert 52 to perform modeling functions, the purpose of which is described in greater detail in U.S. patent application Ser. No. 10/085,439 entitled “Creation and Display of Indices in a Process Plant,” which was filed on Feb. 28, 2002, which is expressly incorporated by reference herein. Generally speaking, however, the models 56 can be used to determine device, area, unit, loop, etc. parameters, to detect faulty sensors or other faulty equipment, as part of optimizer routines 55, to generate indices such as performance and utilization indices for use in the plant 10, to perform performance or condition monitoring, as well as for many other uses. The models 56 may be models such as those created by and sold by MDC Technology located in Teeside, England or may be any other desired types of models. Some of the data generated by the models 56 may be used by the index generation routine 51 to generate indices which are used in other applications, such as business and process control applications.
The asset utilization expert 50 receives data as it is generated or at certain periodic times over, for example, the bus 32 or other any communication network within the process plant 10. Thereafter, periodically or as needed, the asset utilization expert 50 redistributes the data to other applications or uses that data to generate and provide other information useful in different aspects of the control or operation of the process plant 10 to other function systems within the plant 10. In particular, the asset utilization expert 50 may supply data to cause the index generation routine 51 to create a series of composite indices such as a performance index, a utilization index, a health index and a variability index associated with one or more of the devices, units, loops, areas, or other entities within the process plant 10. The generation and use of these indices will also be discussed in more detail herein.
As a result of the above discussion, it can be seen that the use of models provides many new types of data or information for the business applications, process control applications and asset maintenance and monitoring applications. In particular, the models can be used to perform performance monitoring and to produce a performance index which indicates the relative performance of a device, unit, area, etc. within a plant. This performance index may be a measure of the performance of an entity with respect to the possible performance of that entity. Furthermore, while device and unit models have been discussed above, similar models could be made and executed for process control entities, such as loops, units, etc. to provide performance measures and optimization criteria for these types of entities as well. Also, as indicated above, models may, in some cases, be used to measure or indicate the health of certain devices or other entities and to provide a health index indicative of these entities. For example, the error measurements of certain input and output sensors as determined by the regression analysis used on certain models may be used as or converted into an indication of the health of those devices. Also, other information not otherwise available to the process controller, such as model parameters and virtual sensor measurements based on the models could be provided to the process controllers or to the business persons for use in numerous manners.
Besides performance and health indices, the asset utilization expert 50 can assist the index generation routine 51 in creating other types of indices such as a utilization index and a variability index. A variability index indicates how much some signal into or out of, or some other parameter associated with a device, loop, unit, etc. varies as compared to how much this signal or parameter is expected to vary. The data needed to create this variability index may be collected by the asset utilization expert 50 and provided to the index generation routine 51 at any desired or convenient times. Of course, the normal amount of variation of a signal or parameter may be set by a manufacturer, engineer, operator or maintenance person familiar with the entity or may be based on a statistical measure (such as an average, standard deviation, etc.) associated with that or other similar entities within the plant and this normal or expected variation may be stored by or updated within the index generation routine 51 or the index aggregation routine 60.
The utilization index, in one form or another, tracks or reflects the utilization of individual devices, units, loops, or other entities and may provide some indication as to whether these entities are being over utilized or under utilized based on previously determined bench marks or operational goals. A utilization index can be generated based on measured uses of the actual device. For example, a device may be measured as to how often it is being used within a process or is being left idle and this index may be compared to a desired utilization for that entity to determine if the entity is being over or under utilized. The utilization index might identify devices, units, loops, etc. which are not being utilized as often as they could be or should be or, on the other hand, which are being utilized too much and, thus, are being over used. In some instances, a utilization index might be determined based on the business decisions made regarding the appropriate or desired use of a particular device.
Referring now to
As mentioned above, the index aggregation routine 60 receives information from various data sources, which may include data collectors, data generators or data tools including index generation routines 51, model generation routines 56, control routines 62, maintenance system applications 64, data historians 66, diagnostic routines 68, etc. In one embodiment, the index aggregation routine 60 may receive information from the asset utilization expert 50 described above, and which is described further in U.S. patent application Ser. No. 10/085,439 referred to above. This information may include indices related to the health, performance, utilization and variability of a particular device, loop, unit, area, etc. This data can take on any desired form based on how the data is generated or used by other functional systems. Still further, this data may be sent to the index aggregation routine 60 using any desired or appropriate data communication protocol and communication hardware, such as the XML/XSL protocol discussed above.
Information received from the index generation routines 51, model generation routines 56, control routines 62, maintenance system applications 64, data historians 66, diagnostic routines 68, etc. may be used to create and assign a weighting value to each of the devices within a logical and/or physical group of device. For example, each device within a logical process (e.g., control loop), sub-unit, unit, area or plant may be assigned a weighting value. Further, weighting values may be created and assigned to logical and/or physical groups including a logical process, a sub-unit, an area or a plant.
The weighting value generally relate to the importance or priority of a device, loop, sub-unit, etc. among the corresponding devices, loops, sub-units, etc. within the same physical and/or logical grouping. In other words, each asset within a group is ranked according to system criticality, operational criticality, asset criticality, etc. based upon an assessment of each asset within the group, and a weighing value is assigned to each asset based upon its importance. For example, within a sub-unit that includes a plurality of devices and/or loops, a particular piece of rotating equipment 20 may be considered more critical to the operation of the overall sub-unit than a field device 16. If both the rotating equipment 20 and the field device 16 require maintenance, the rotating equipment 20 may receive priority over the field device 16 in terms of resources allocated to maintenance. As a result, the rotating equipment 20 is assigned a weighting value greater than the weighting value assigned to the field device 16. Similarly, among the sub-units and/or units within an area, a particular sub-unit may be considered more important to the area than another sub-unit, and is weighted accordingly. It should be recognized that areas within a plant may be weighted according to importance, and plants within a business enterprise may likewise be weighted. It should further be recognized that assets within a grouping need not be limited to an immediately preceding level. For example, weighting values may be assigned to each device, loop, sub-unit and/or unit within an area, rather than just each unit within an area. Likewise, weighting values may be assigned to each device, loop, sub-unit, unit and/or area in a plant. A user may define the groupings in a manner most helpful to the user, and weighting values may be assigned accordingly. As a result, each device, loop, sub-unit, unit, area, plant, etc. may be weighted according to its importance within a particular grouping, such that each asset within a given group is assigned a weighting value.
Generally, the importance of a device, loop, sub-unit, unit, area, etc., and its corresponding weighting value, is based on two contributing factors: the impact on the group when the asset fails and the frequency of failure. For example, a device that has little impact on an area when it fails may be weighted lower than a device that has a high impact on an area during failure. Likewise, a device that has a low frequency of failure may be weighted lower than a device with a high frequency of failure. The impact and the frequency of failure may be quantified, with the product of the impact and frequency of failure resulting in the weighting value. The evaluation of impact and frequency of failure may be based on a variety of factors, including, but not limited to, process information, on-line monitoring information, historical information, maintenance information, diagnostic information, and heuristic information based on experience of process plant personnel.
The index aggregation routine 60 may acquire weighting values related to each device, loop, sub-unit, unit, area, plant, etc. within a group by receiving each weighting value from another source or by creating each weighting value based on information from a variety of sources. For example, the index aggregation routine 60 may receive data relating to the impact and frequency of failure of each device, loop, sub-unit, unit, area, plant, etc. within a group and create each weighting value based on the impact and frequency of failure, (e.g., the product of the impact and frequency of failure).
In yet another example, the index aggregation routine 60 may receive information relating to each device, loop, sub-unit, unit, area, plant, etc within a group to evaluate the impact and frequency of failure of each asset within the group, and to further create a weighting value for each asset within the group. The information may include process information, on-line monitoring information, historical information, maintenance information, diagnostic information, and heuristic information as described above. Accordingly, the index aggregation routine 60 is communicatively coupled to model generation routines 56, control routines 62, maintenance system applications 64, data historians 66, diagnostic routines 68, or other data sources as shown in
In addition to acquiring weighting values pertaining to each device, loop, sub-unit, unit, area, plant, etc within a group, the index aggregation routine 60 acquires indices pertaining to the status of each device, loop, sub-unit, unit, area, plant, etc within the group. The indices may be acquired from the index generation routine 51, and each index may include a health index, a utilization index, a performance index or a variability index as described above. Examples of each index and its creation are described further below and described further in U.S. patent application Ser. No. 10/085,439 referred to above. However, it should be understood that various other indices may be used by the index aggregation routine 60 to determine an aggregate index for a group.
Accordingly, weighting values may be acquired by receiving the weighting values, by receiving impact and frequency of failure information to create the weighting values or by receiving information from the model generation routines 56, control routines 62, maintenance system applications 64, data historians 66, diagnostic routines 68, etc. to evaluate the impact and frequency of failure and create a weighting value for each of the devices, loops, sub-unit, units, areas and/or plants, etc. within a logical and/or physical group. Further, indices pertaining to each devices, loops, sub-unit, units, areas and/or plants, etc. within the logical and/or physical group may be acquired by the index aggregation routine 60. Using the weighting values and indices, the index aggregation routine 60 may create an aggregate index pertaining to the overall status of the group, such as an aggregate health index, an aggregate utilization index, an aggregate performance index or an aggregate variability index. The index aggregation routine 60 may calculate the aggregate index as a weighted average according to the following general equation:
wherein:
As seen by the above equation, the aggregate index for a group is created as a normalized expression in which the range of the aggregate index is within the range of the indices used to create the aggregate index. This allows the above expression to be used with various index ranges, and allows the aggregate index to be used with various asset groups having assets of differing importance. In particular, the index value for each asset within the group is within a common range of index values and the weighting value for each asset within the group within a common range of weighting values. As a result, the aggregate index for the group will be within the same range and the range used for the indices of the assets within the group. For example, the value for ui may be a number from 0 to 100, where “0” corresponds to known use index that is low (e.g., poor health, poor performance, low utilization, high variability, etc.) and “100” corresponds to a high index (e.g., excellent health, excellent performance, high utilization, low variability, etc.). Accordingly, the aggregate index u is provided as a number from 0 to 100, which corresponds to the range of indices used by the assets within the group. Further, wi may be a number from 0 to 100, where “0” corresponds to a known, yet low, importance and “100” corresponds to a high importance.
Although the above example shows ui and wi having the same range of values, the range of values for the indices may be different from the range used for the weighting values. In some instances, an index and/or a weighting value may not be known or otherwise available for a particular asset within the group, in which case it is difficult to make assumptions about a particular asset's index and/or importance. As such, the value for ui and/or wi is set to null to avoid skewing the resulting aggregate index. In a scenario where all weighting values are zero, the aggregate index defaults to zero to avoid division by zero. The above ranges are provided as examples only, and different ranges may be used consistent with the above parameters.
In operation, the index aggregation routine 60 acquires indices pertaining to the status of each asset within a group and acquires weighting values pertaining to the importance (e.g., criticality, priority) of each asset within a particular group to create an aggregate index pertaining to the overall group. For example, an area may include several devices, loops, sub-units and units. By acquiring the health index values and weighting values for each device within the area, the overall health of the area may be determined. Alternatively, the aggregate health index of the area may be calculated based on the loops, sub-units or units within the area, or based on a combination of devices, loops, sub-units and units within the area. In turn, the index aggregation routine 60 may calculate the health index of each area within a plant, or receive the area health indices from the index generation routine 51, acquire a weighting value for each area within the plant and generate an aggregate health index corresponding to the overall health of the plant. Similar aggregate indices may be determined for loops, sub-units, units, business enterprises or at any other level of hierarchy.
In general, each of the indices generated by the index generator routine 51 may be calculated for individual devices, for logical and/or physical groupings of devices, for logical processes (e.g., control loops), for logical groupings of devices such as units and areas, plant, etc. On the other hand, each of the indices generated by the index aggregation routine 60 may be calculated based on indices provided by the index generation routine 51, based on indices previously determined by the index aggregation routine 60, or other sources of indices, and further based on weighting values associated with each of the devices, logical and/or physical groupings of devices, logical processes, units, areas, plant, etc. to calculate aggregate indices for logical and/or physical groupings of devices, for logical processes (e.g., control loops), for logical groupings of devices such as units and areas, plant, etc. In other words, the indices may, in principal, be calculated at each level of the equipment and logical hierarchy of a process control system or, more generally, an asset utilization system, which may include one or more process control systems. However, the meaning of a particular index may depend on the context (i.e., whether the index corresponds to a logical or a physical grouping of devices and/or parameters) in which the index is generated and displayed and may depend on the level of the hierarchy at which it is displayed. For example, at the lowest level of the equipment hierarchy, indices correspond to physical devices such as valves, temperature sensors, actuators, etc. Thus, each device may have a unique set of indices that may be generated within the device or for the device based on information stored within the device at the time the device is manufactured. Accordingly, each device may generate and provide its indices to higher levels of the hierarchy and to the asset utilization expert 50 as needed.
Similarly, units or loops, each of which is composed of one or more devices or function blocks may each have a unique set of indices. However, the index values for each unit or loop may be generated by mathematically combining the index values for the individual devices or function blocks used within the unit or loop. Thus, if a unit or loop is composed of a pressure transmitter, a valve and a pump (or function blocks associated with the operation of these devices), the index values for the unit or loop may be based on various mathematical combinations of the index values generated for or by each of those devices or function blocks making up the unit or the loop. Likewise, because sub-unit and unit levels of the hierarchy are composed of one or more loops which, in turn, are composed of devices, the index values for each sub-unit and unit may be generated by mathematically combining loop or device index values. Still further, area indices may be determined as combinations of the units, loops, devices, etc. within the area.
Also, generally speaking, the one or more user interface routines 58 can be stored in and executed by one or more of the computers within the plant 10. For example, the computer 30, the user interface 14A, the business system computer 35 or any other computer may run a user interface routine 58. Each user interface routine 58 can receive or subscribe to information from the asset optimization expert 50, including the index generation routine 51 and either the same or different sets of data may be sent to each of the user interface routines 58. Any one of the user interface routines 58 can provide different types of information using different screens to different users. For example, one of the user interface routines 58 may provide a screen or set of screens to a control operator or to a business person to enable that person to set constraints or to choose optimization variables for use in a standard control routine or in a control optimizer routine. The user interface routine 58 may provide a control guidance tool that enables a user to view the indices created by the index generation software 51 in some coordinated manner. This operator guidance tool may also enable the operator or any other person to obtain information about the states of devices, control loops, units, etc. and to easily see the information related to the problems with these entities, as that information has been detected by other software within the process plant 10. The user interface routine 58 may also provide performance monitoring screens using performance monitoring data provided by or generated by the tools 23 and 27, the maintenance programs such as the AMS application or any other maintenance programs. Of course, the user interface routine 58 may provide any user access to and enable the user to change preferences or other variables used in many or all functional areas of the plant 10.
One important aspect of the system of
Preferably, but not necessarily, the GUI may be implemented using a familiar graphical windows-based structure and appearance, in which a plurality of interlinked graphical views or pages include one or more pull-down menus that enable a user to navigate through the pages in a desired manner to view and/or retrieve a particular type of information. The features and/or capabilities of the asset utilization expert 50 described above may be represented, accessed, invoked, etc. through one or more corresponding pages, views or displays of the GUI. Furthermore, the various displays making up the GUI may be interlinked in a logical manner to facilitate a user's quick and intuitive navigation through the displays to retrieve a particular type of information or to access and/or invoke a particular capability of the asset utilization expert 50.
Generally speaking, the GUI described herein provides intuitive graphical depictions or displays of process control areas, units, loops, devices, etc. Each of these graphical displays may include numerical status and indices (some or all of which may be generated by the index generator routine 51 and the index aggregation routine 60 described above) that are associated with a particular view being displayed by the GUI. For example, a display depicting a process control area may provide a set of indices reflecting the status and performance of that area (i.e., a particular portion of the process control system at a particular level of the equipment hierarchy). On the other hand, a display depicting a loop may provide a set of status and performance indices associated with that particular loop. In any event, a user may use the indices shown within any view, page or display to quickly assess whether a problem exists within any of the devices, loops, etc. depicted within that display.
Additionally, the GUI described herein may automatically, or may in response to a request by a user, provide maintenance information to the user. The maintenance information may be provided by any portion of the asset utilization expert 50. Similarly, the GUI may display alarm information, process control information, etc., which may also be provided by the asset utilization expert 50. Still further, the GUI may provide messages to the user in connection with a problem that has occurred or which may be about to occur within the plant 10. These messages may include graphical and/or textual information that describes the problem, suggests possible changes to the system which may be implemented to alleviate a current problem or which may be implemented to avoid a potential problem, describes courses of action that may be pursued to correct or to avoid a problem, etc.
Generally speaking, the GUI described herein provides intuitive graphical depictions or displays of process control areas, units, loops, devices, etc. Each of these graphical displays may include numerical status and performance indices (some or all of which may be generated by the index generator routine 51 described above) that are associated with a particular view being displayed by the GUI. For example, a display depicting a process control area may provide a set of indices reflecting the status and performance of that area (i.e., a particular portion of the process control system at a particular level of the equipment hierarchy). On the other hand, a display depicting a loop may provide a set of status and performance indices associated with that particular loop. In any event, a user may use the indices shown within-any view, page or display to quickly assess whether a problem exists within any of the devices, loops, etc. depicted within that display.
Additionally, the GUI described herein may automatically, or may in response to a request by a user, provide maintenance information to the user. The maintenance information may be provided by any portion of the asset utilization expert 50. Similarly, the GUI may display alarm information, process control information, etc., which may also be provided by the asset utilization expert 50. Still further, the GUI may provide messages to the user in connection with a problem that has occurred or which may be about to occur within the plant 10. These messages may include graphical and/or textual information that describes the problem, suggests possible changes to the system which may be implemented to alleviate a current problem or which may be implemented to avoid a potential problem, describes courses of action that may be pursued to correct or to avoid a problem, etc.
Importantly, the GUI display shown in
Indices generated by the index generation routine 51 and the index aggregation routine 60, including, but not limited to a performance index, a health index, a variability index and a utilization index, may be displayed by the GUI as described in detail herein in connection with the various displays of the GUI, additional and/or different indices may be generated by the asset utilization expert 50 and displayed via the GUI without departing from the scope of the invention.
As discussed in greater detail above, the mathematical combination of device index values to form index values for loop, sub-unit, unit and area levels of the hierarchy may use weighted summations or averages, or any other suitable mathematical combination. Of course, the calculation of one or more of the performance, health, variability and utilization indices may not be appropriate, required or useful for every level of the logical and equipment hierarchies.
Further,
The HI for a loop, on the other hand, is preferably, but not necessarily, a mathematical combination (such as, for example, a weighted summation or average) of the HI values for the individual devices or functions blocks that make up the loop. Likewise, the HI values for the sub unit and unit levels may also be a mathematical combination of the underlying HI values for loops and sub units. Thus, ultimately, the HI values hierarchy for levels above the device level are based on one or more HI values for devices that have been formed into composite values.
As is also shown in
In a similar manner, the HI for the unit 100 may be calculated as a weighted average of the HI values for all of the devices (and/or loops) that make up the unit 100. A table such as that shown in
It will also be understood that a user may view successively lower and lower entities within a plant and be provided information about the indices associated with each of these different entities or views. Thus, for example, a user may look at a view of the plant and see a particular set of indices for the plant. The user may then focus on one area, such as by clicking on one of the areas within the plant view, and see the indices associated with that area. Similarly, by clicking on units within the displayed area, the indices for different units may be viewed. Likewise indices for loops, sub units, devices etc. may then be viewed by focusing in on these different entities from a view of an entity in which these entities are located. In this manner, a user can quickly find the cause of a lower than (or higher than) expected index at any point or level of the plant.
While the asset utilization expert 50, index generation routine 51, index aggregation routine 60 and other process elements have been described as preferably being implemented in software, they may be implemented in hardware, firmware, etc., and may be implemented by any other processor associated with the process control system 10. Thus, the elements described herein may be implemented in a standard multi-purpose CPU or on specifically designed hardware or firmware such as an application-specific integrated circuit (ASIC) or other hard-wired device as desired. When implemented in software, the software routine may be stored in any computer readable memory such as on a magnetic disk, a laser disk, or other storage medium, in a RAM or ROM of a computer or processor, in any database, etc. Likewise, this software may be delivered to a user or a process plant via any known or desired delivery method including, for example, on a computer readable disk or other transportable computer storage mechanism or over a communication channel such as a telephone line, the internet, wireless communication, etc. (which are viewed as being the same as or interchangeable with providing such software via a transportable storage medium).
Thus, while the present invention has been described with reference to specific examples, which are intended to be illustrative only and not to be limiting of the invention, 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 | May 1989 | A |
| 4843557 | Ina et al. | Jun 1989 | A |
| 4873655 | Kondraska | 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 | Backman et al. | May 1990 | A |
| 4934196 | Romano | Jun 1990 | A |
| 4942514 | Miyagaki et al. | Jul 1990 | A |
| 4944035 | Aagardl 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 |
| 5161013 | Rylander et al. | Nov 1992 | A |
| 5167009 | Skeirik | Nov 1992 | A |
| 5175678 | Frerichs et al. | Dec 1992 | A |
| 5187674 | Bonne | Feb 1993 | A |
| 5193143 | Kaemmerer et al. | Mar 1993 | A |
| 5197114 | Skeirik | Mar 1993 | A |
| 5197328 | Fitzgerald | Mar 1993 | A |
| 5200028 | Tatsumi | 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 |
| 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 |
| 5311562 | Palusamy | 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 |
| 5329465 | Arcella et al. | Jul 1994 | A |
| 5333240 | Matsumoto 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 |
| 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 | 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 | May 1995 | A |
| 5419197 | Ogi et al. | May 1995 | A |
| 5430642 | Nakajima 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 | Nov 1995 | A |
| 5483387 | Bauhahn et al. | Jan 1996 | A |
| 5485753 | Burns 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 et al. | Mar 1996 | A |
| 5500941 | Gil | Mar 1996 | A |
| 5511004 | Dubost et al. | Apr 1996 | A |
| 5511442 | Tame | Apr 1996 | A |
| 5521814 | Teran | May 1996 | A |
| 5528510 | Kraft | Jun 1996 | A |
| 5533413 | Kobayashi | 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 |
| 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 |
| 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 |
| 5640493 | Skeirik | Jun 1997 | A |
| 5646350 | Robinson et al. | Jul 1997 | A |
| 5666297 | Britt 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 |
| 5729661 | Keeler et al. | Mar 1998 | A |
| 5740324 | Mathur et al. | Apr 1998 | A |
| 5742513 | Bouhenguel et al. | Apr 1998 | A |
| 5754451 | Williams et al. | May 1998 | A |
| 5757371 | Oran | 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 |
| 5805442 | Crater et al. | Sep 1998 | A |
| 5809490 | Guiver 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 | 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 |
| 5905989 | Biggs | May 1999 | A |
| 5906214 | Gueret | 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 |
| 5917840 | Cheney 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 | Sep 1999 | A |
| 5960214 | Sharpe 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 | Dec 1999 | A |
| 6008985 | Lake et al. | Dec 1999 | A |
| 6014612 | Larson et al. | Jan 2000 | A |
| 6017143 | Eryurek et al. | Jan 2000 | A |
| 6026352 | Burns | Feb 2000 | A |
| 6033257 | Lake et al. | Mar 2000 | A |
| 6035339 | Agraharam | Mar 2000 | A |
| 6038486 | Saitoh | Mar 2000 | A |
| 6041263 | Boston et al. | Mar 2000 | A |
| 6047221 | Piche et al. | Apr 2000 | A |
| 6055483 | Lu | Apr 2000 | A |
| 6061603 | Papadopoulos | 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 |
| 6122555 | Lu | Sep 2000 | A |
| 6128279 | O'Neil 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 |
| 6246972 | Klimasauskas | Jun 2001 | B1 |
| 6259959 | Martin | Jul 2001 | B1 |
| 6266726 | Nixon et al. | Jul 2001 | B1 |
| 6298377 | Hartikainen | 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 |
| 6389331 | Jensen et al. | May 2002 | B1 |
| 6397114 | Eryurek et al. | May 2002 | B1 |
| 6400681 | Bertin | Jun 2002 | B1 |
| 6418465 | Hirosawa | 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 | Mar 2003 | B1 |
| 6535769 | Komar | Mar 2003 | B1 |
| 6549130 | Joao | Apr 2003 | B1 |
| 6567718 | Campbell et al. | May 2003 | B1 |
| 6571273 | Shirai | May 2003 | B1 |
| 6591260 | Schwarzhoff | Jul 2003 | B1 |
| 6609040 | Brunnemann | Aug 2003 | B1 |
| 6628994 | Turicchi, Jr. et al. | Sep 2003 | B1 |
| 6631305 | Newmark | Oct 2003 | B2 |
| 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 et al. | Apr 2004 | B1 |
| 6732191 | Baker | May 2004 | B1 |
| 6738388 | Stevenson et al. | May 2004 | B1 |
| 6758168 | Hoskinen et al. | Jul 2004 | B2 |
| 6760782 | Swales | Jul 2004 | B1 |
| 6774786 | Havekost et al. | Aug 2004 | B1 |
| 6813532 | Eryurek et al. | Nov 2004 | B2 |
| 6907383 | Eryurek et al. | Jun 2005 | B2 |
| 20020022894 | Eryurek et al. | Feb 2002 | A1 |
| 20020029130 | Eryurek et al. | Mar 2002 | A1 |
| 20020067370 | Forney et al. | Jun 2002 | A1 |
| 20020077711 | Schliess et al. | Jun 2002 | A1 |
| 20020147511 | Eryurek et al. | Oct 2002 | A1 |
| 20020161940 | Eryurek et al. | Oct 2002 | A1 |
| 20020163427 | Eryurek et al. | Nov 2002 | A1 |
| 20020169514 | Eryurek et al. | Nov 2002 | A1 |
| 20030002969 | Risser | Jan 2003 | A1 |
| 20030009572 | Thurner | Jan 2003 | A1 |
| 20030014500 | Schleiss et al. | Jan 2003 | A1 |
| 20030028268 | Eryurek et al. | Feb 2003 | A1 |
| 20030195934 | Peterson et al. | Oct 2003 | A1 |
| 20040075689 | Schleiss et al. | Apr 2004 | A1 |
| 20040181364 | Reeves et al. | Sep 2004 | A1 |
| 20040186927 | Eryurek et al. | Sep 2004 | A1 |
| 20040249583 | Eryurek et al. | Dec 2004 | A1 |
| 20050007249 | Eryurek et al. | Jan 2005 | A1 |
| 20050027379 | Dyk et al. | Feb 2005 | A1 |
| 20050033466 | Eryurek et al. | Feb 2005 | A1 |
| 20050240289 | Hoyte | Oct 2005 | A1 |
| 20060036404 | Wiklund et al. | Feb 2006 | A1 |
| Number | Date | Country |
|---|---|---|
| 1097804 | Jan 1995 | CN |
| 40 08 560 | Sep 1990 | DE |
| 44 33 593 | Jun 1995 | DE |
| 195 02 499 | Aug 1996 | DE |
| 0 122 622 | Oct 1984 | EP |
| 0 377 736 | Jul 1990 | EP |
| 0 413 814 | Feb 1991 | EP |
| 0 487 419 | May 1992 | EP |
| 0 594 227 | Apr 1994 | EP |
| 0 362 386 | Jun 1995 | EP |
| 0 626 697 | Jul 1997 | EP |
| 0 624 847 | Aug 1999 | EP |
| 0 964 325 | Aug 2002 | EP |
| 0 961 184 | Dec 2003 | EP |
| 2 294 129 | Apr 1996 | GB |
| 2 294 793 | May 1996 | GB |
| 2 347 234 | Aug 2000 | GB |
| 2 380 833 | Apr 2003 | GB |
| 06242192 | Feb 1994 | JP |
| 07234988 | May 1995 | JP |
| WO9838585 | Sep 1998 | WO |
| WO 0050851 | Aug 2000 | WO |
| WO 02023405 | Mar 2002 | WO |
| WO 02095509 | Nov 2002 | WO |
| WO 02095633 | Nov 2002 | WO |
| WO9913418 | Mar 2003 | WO |
| WO 03075206 | Sep 2003 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 20070067142 A1 | Mar 2007 | US |
