Patent Grant
8127241
The present invention relates generally to process plant user interfaces and, more particularly, to an intelligent control and simulation environment that enables user viewing, simulation and control to be integrated at the system level of the process plant control architecture.
Distributed process control systems, like those used in chemical, petroleum or other processes, typically include one or more process controllers communicatively coupled to one or more field devices via analog, digital or combined analog/digital buses. The field devices, which may be, for example, valves, valve positioners, switches and transmitters (e.g., temperature, pressure, level and flow rate sensors), are located within the process environment and perform process functions such as opening or closing valves, measuring process parameters, etc. Smart field devices, such as the field devices conforming to the well-known Fieldbus protocol, may also perform control calculations, alarming functions, and other control functions commonly implemented within the controller. The process controllers, which are also typically located within the plant environment, receive signals indicative of process measurements made by the field devices and/or other information pertaining to the field devices and execute a controller application that runs, for example, different control modules which make process control decisions, generate control signals based on the received information and coordinate with the control modules or blocks being performed in the field devices, such as HART and Fieldbus field devices. The control modules in the controller send the control signals over the communication lines to the field devices to thereby control the operation of the process.
Information from the field devices and the controller is usually made available over a data highway to one or more other hardware devices, such as operator workstations, personal computers, data historians, report generators, centralized databases, etc., typically placed in control rooms or other locations away from the harsher plant environment. These hardware devices run applications that may, for example, enable an operator to perform functions with respect to the process, such as changing settings of the process control routine, modifying the operation of the control modules within the controller or the field devices, viewing the current state of the process, viewing alarms generated by field devices and controllers, simulating the operation of the process for the purpose of training personnel or testing the process control software, keeping and updating a configuration database, etc.
As an example, the DeltaV™ control system, sold by Emerson Process Management includes multiple applications stored within and executed by different devices located at diverse places within a process plant. A configuration application, which resides in one or more operator workstations, enables users to create or change process control modules and download these process control modules via a data highway to dedicated distributed controllers. Typically, these control modules are made up of communicatively interconnected function blocks, which are objects in an object oriented programming protocol, which perform functions within the control scheme based on inputs thereto and which provide outputs to other function blocks within the control scheme. The configuration application may also allow a designer to create or change operator interfaces which are used by a viewing application to display data to an operator and to enable the operator to change settings, such as set points, within the process control routine. Each dedicated controller and, in some cases, field devices, stores and executes a controller application that runs the control modules assigned and downloaded thereto to implement actual process control functionality. The viewing applications, which may be run on one or more operator workstations, receive data from the controller application via the data highway and display this data to process control system designers, operators, or users using the user interfaces, and may provide any of a number of different views of the process control routine or module, such as an operator's view, an engineer's view, a technician's view, etc. A data historian application is typically stored in and executed by a data historian device that collects and stores some or all of the data provided across the data highway while a configuration database application may run in a still further computer attached to the data highway to store the current process control routine configuration and data associated therewith. Alternatively, the configuration database may be located in the same workstation as the configuration application.
As the number and type of control and support applications used in a process control environment have increased, different graphical display applications have been provided to enable users to effectively configure and use these applications. For example, graphical display applications have been used to support control configuration applications to enable a configuration engineer to graphically create control programs to be downloaded to the control devices within a process plant. Additionally, graphical display applications have been used to enable control operators to view the current functioning of the process plant, or areas of the process plant, to enable maintenance personnel to view the state of hardware devices within the process plant, to enable simulation of the process plant, etc. However, these graphical display applications have, in the past, been separately created as part of, or to independently support the specific applications with which they are associated, and thus are generally limited in usefulness to the specific process function for which they were created. For example, it is difficult, if not impossible, to use a graphical program created to support a control operator in a context involving maintenance, configuration, or simulation functions.
As a particular example, some process control configuration applications presently include a library of template objects, such as function block template objects and, in some cases, control module template objects, which are used to create a control strategy for a process plant. The template objects have default properties, settings and methods associated therewith and the engineer using a graphical configuration application can select these template objects and essentially place copies of the selected template objects into a configuration screen to develop a control module. During the process of selecting and placing the template objects into the configuration screen, the engineer interconnects the inputs and outputs of these objects and changes their parameters, names, tags and other properties to create a specific control module for a specific use in the process plant. After creating one or more such control modules, the engineer can then instantiate the control module and download it to the appropriate controller or controllers and field devices for execution during operation of the process plant.
Thereafter, the engineer may use a different graphical display creation application to create one or more separate, independent displays for operator, maintenance and other personnel within the process plant by selecting and building display objects in the display creation application. These displays are typically implemented on a system wide basis in one or more of the workstations, which provide the preconfigured displays to the operator or maintenance persons regarding the operating state of the control system or the devices within the plant. These displays generally take the form of alarming displays that receive and display alarms generated by controllers or devices within the process plant, control displays indicating the operating state of the controllers and other devices within the process plant, maintenance displays indicating the functioning state of the devices within the process plant, etc. However, these displays are generally preconfigured to display, in known manners, information or data received from the process control modules or the devices within the process plant. In some known systems, displays are created through the use of objects that have a graphic associated with a physical or logical element and that is communicatively tied to the physical or logical element to receive data about the physical or logical element. The object may change the graphic on the display screen based on the received data to illustrate, for example, that a tank is half full, to illustrate the flow measured by a flow sensor, etc. However, these graphical displays used for configuration, operator control, maintenance and simulation activities are generally created separately from one another using different graphical editors.
Thus, while graphic displays have been provided in and associated with different applications used for different general activities performed within a process plant, these graphic displays and associated graphic display editors were generally added on at the functional level of the application for which they were created to support. As a result, the graphical editors, to the extent they existed, have only enabled the user to create graphics that support specific functionality needed by a specific application. Previous process plants did not provide a graphical display editor that could be used by or that could support the graphical needs of various or multiple activities being performed in the context of plant configuration and support. Thus, for example, a graphical display editor used to support or enable control configuration activities only enabled the user to create control programs and did not support the needs or functionality of operator or maintenance displays. Similarly, graphic display editors used for creating operator or maintenance views to be provided to a control operator or maintenance technician during operation of a plant, did not support functionality associated with configuration activities, simulation activities, etc. As a result of the graphic display needs being supported at the individual functional levels of the process plant, such as at the control configuration, maintenance support, control operator support and simulation support functional levels, different ones of the displays created by these various editors end up modeling and depicting the same components within the plant, which results in the duplication of graphical display efforts by various different personnel with the process plant. This duplication of effort is manifested not only in the effort needed to create the different graphical displays depicting the same process element for different uses, but also in the effort needed to tie the graphical elements used in different display applications to the actual hardware or software elements within the process plant to which they are associated.
Because graphical support for various process plant activities has been provided after the fact, and as part of the actual activity being performed, graphical support is not integrated in the plant environment in a manner that enables common graphics to be created and used within the plant at the various different functional levels of the plant. This non-integration of graphics leads to the graphics actually created for the different functions being different from function to function or from application to application, which can lead to confusion on the part of users who, while familiar with one specific type of graphical display, might occasionally need to view different displays associated with different operations or functions within the plant. Likewise, as noted above, the provision of graphical display support at the various different functional levels of the plant leads to the duplication of graphic support, both in creating displays and properly connecting the elements within the displays to actual hardware or software elements within the plant.
In accordance with one aspect of the disclosure, a method of providing a user interface for a process plant includes generating information for a plurality of content layers of a process graphic display of process plant elements of the process plant, determining a content layer of the plurality of content layers to display, and displaying via the user interface the determined content layer.
In some cases, the generating step includes processing runtime data received from the process plant in connection with the process plant elements. The determining step may include selecting the determined content layer based on a user profile characteristic. When the user profile characteristic includes an indication for operator access, the displaying step may then include rendering an operator content layer of the plurality of content layers based on the runtime data.
The generating step may also or alternatively include processing simulation data in connection with simulated operation of the process plant elements. When the user profile characteristic includes an indication for maintenance access, the displaying step may then include rendering a maintenance content layer of the plurality of content layers based on the simulation data.
In some embodiments, the method further includes introducing simulated disturbances into the simulated operation of the process plant elements. In such cases, the displaying step may include rendering an instructor content layer of the plurality of content layers to support the introducing step when the user profile characteristic includes an indication for training instructor access.
More generally, the generating step may include implementing object methods defined in a plurality of objects respectively modeling the process plant elements depicted in the process graphic display. Each object of the plurality of objects may further define a graphical depiction of the process plant element for each content layer of the plurality of content layers.
In accordance with another aspect of the disclosure, disclosed is a user interface system for a process plant. The user interface system includes a computer-readable medium, a display device, and an object having information stored in the computer-readable medium regarding operation of a process plant element of the process plant. An execution engine of the user interface system utilizes the object information in a runtime environment to generate a content for a plurality of content layers of a process graphic display. The display device then depicts a specified content layer of the plurality of content layers.
The object information may related to receiving runtime data from the process plant in connection with on-line operation of the process plant element. In cases where the user profile characteristic includes an indication for operator access, the specified content layer may be directed to a customized depiction of the runtime data in an operator content layer of the plurality of content layers. Alternatively, or in addition, the object information relates to generating simulation data in connection with simulated operation of the process plant element. In cases where the user profile characteristic includes an indication for maintenance access, the specified content layer may be directed to a customized depiction of the simulation data in a maintenance content layer of the plurality of content layers. Furthermore, the object may also include information related to a simulated disturbance of the simulated operation of the process plant element. In cases where the user profile characteristic includes an indication for training instructor access, the specified content layer may be directed to a customized depiction of the simulation data arising from the simulated disturbance in an instructor content layer of the plurality of content layers.
In accordance with yet another aspect of the disclosure, a method of providing a user interface for a process plant is disclosed. The method includes generating information for a plurality of different types of users of the user interface by processing data regarding on-line and simulated operation of the process plant, and rendering a selected portion of the content in a customized depiction of the process plant by determining the selected portion of the content in accordance with a current user type of the plurality of different user types.
In some embodiments, the customized depiction is rendered by determining whether the process plant is on-line to further determine the selected portion of the content for the customized depiction.
In accordance with a still further aspect of the disclosure, disclosed is a method of generating a user interface for a process plant. The method includes creating a process graphic display of a plurality of graphic display elements representative of a plurality of process plant elements of the process plant, respectively. The plurality of graphic display elements are configured by defining parameters related to operation of the corresponding process plant elements and by defining simulation parameters to support simulated operation of the corresponding process plant elements. The method also includes establishing a plurality of content layers for selectively displaying information related to the operation and simulated operation of the process plant elements via customized views of the process graphic display.
In some embodiments, the method further includes the step of storing a plurality of objects for the plurality of graphic display elements, respectively. Each object may then include the respective parameters related to on-line operation and the simulation parameters.
Disclosed is a user interface method and system for a process plant. The user interface solution disclosed herein generally includes displaying a customized graphical depiction of process plant elements of the process plant via a display device of the user interface, where information for potential display with the graphical depiction is generated by processing data regarding both on-line and simulated operation of the process plant. The customized nature of the graphical depiction is provided by determining or specifying a content layer of the generated information. The content layer may be determined by, or specified via, a selection based on a user profile characteristic of the current user viewing the display device of the user interface.
A plurality of content layers of a process graphic display are available to support a number of different user types. Examples of user types include operators, maintenance personnel, training instructors, engineering personnel, and management. In this way, an operator may view a customized content layer of the process graphic display that presents runtime data received from the process plant in connection with the process plant elements depicted. Simulation data may also be presented in connection with a model of the process plant elements such that maintenance personnel may view a customized content layer depicting the simulation data. A simulated disturbance may also be introduced into the model of the process plant elements by a training instructor having access to an instructor content layer of the process graphic display.
The use of a plurality of content layers of a process graphic display provides an integrated approach to process plant user interfaces that avoids requiring configuration engineers and designers to create separate displays for the various personnel monitoring the process plant from different on-line and off-line perspectives. As described below, the runtime and simulation information to support the plurality of content layers is generated in an integrated manner via smart process objects that specify routines, instructions, behaviors or methods for implementation by an execution engine. The rendering of graphic display elements in a customized content layer may then involve a selection of a portion of the information generated in accordance with the methods, behaviors, etc. defined by the smart process objects. Examples of how portions of such information may be included in, or excluded from, specific content layers are presented below in connection with a number of different user profile characteristics.
Referring now to
As is known, each of the controllers 12, which may be by way of example, the DeltaV™ controller sold by Emerson Process Management, stores and executes a controller application that implements a control strategy using any number of different, independently executed, control modules or blocks 29. Each of the control modules 29 can 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. As is well known, function blocks, which may be objects in an object oriented programming protocol, 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 that 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. While the Fieldbus protocol and the DeltaV system protocol use control modules and function blocks designed and implemented in an object oriented programming protocol, the control modules could be designed using any desired control programming scheme including, for example, sequential function block, ladder logic, etc. and are not limited to being designed and implemented using the function block or any other particular programming technique.
In the plant 10 illustrated in
In the process plant 10 of
Generally speaking, the suite of applications 32 provides for or enables the creation and use of three different types of entities, the operation of which may be integrated together to provide for enhanced control, simulation, and display functions within the process plant 10. More particularly, the suite of applications 32 may be used to create and implement process graphic displays 35 (which generally provide an operator display pertaining to a portion of the process plant), process modules 39 (which generally provide a simulation of a portion of a process plant) and process control modules, such as the control modules 29, which generally provide or perform on-line control of the process. The process control modules 29 are generally well known in the art and may include any type of control module, such as function block control modules, etc. The process graphic display elements 35, which will be described in more detail below, are generally elements that are used by an operator, engineer or other displays to provide information to a user, such as an operator, about the operation, configuration or set-up of the process plant and the elements therein. The process modules 39 are generally closely tied to the process graphic display elements 35 and may be used to perform simulations of the operation of the process plant or of some of the different elements therein connected in the manner depicted in the process graphic displays 35. The process graphic displays 35 and process modules 39 are illustrated as being stored in and executed by the workstations 20 and 22, although the process graphic displays 35 and the process modules 39 could be downloaded to and executed in any other computer associated with the process control plant 10, including laptops, handheld devices, etc.
A library 40 of smart process objects 42 includes example or template smart process objects 42 that may be accessed, copied and used by the configuration application 38 to create process modules 39 and graphic displays 35. As will be understood, the configuration application 38 may be used to create one or more process modules 39, each of which is made up of or created from one or more smart process objects 42 and may include one or more process flow or simulation algorithms 45, which are stored in a process module memory 46. Additionally, the configuration application 38 may be used to create one or more graphic displays 35, each of which is made up of or created from one or more smart process objects 42 and may include any number of display elements connected together. One of the graphic displays 35b is illustrated in
An execution engine 48 operates or implements each of the graphic displays 35 and the process modules 39 during runtime to create one or more process displays for an operator as defined by the graphic displays 35 and to implement simulation functionality associated with the process modules 39. The execution engine 48 may use a rules database 50 defining the logic to be implemented on the process modules 39 as a whole and the smart process objects within those modules in particular. The execution engine 48 may also use a connection matrix 52 which defines the connections between the process elements within the plant 10 as well as within the process modules 39 to implement the functionality for the process modules 39.
As will be understood, the smart process object 42e, before being instantiated, is an object that is associated with a particular type of entity, such as a physical or a logical entity, within the process plant 10 of
The smart process object 42e may also include one or more inputs 54 and outputs 56 to enable communication with other smart process objects within or outside of a process module in which the smart process object 42 is used. The connections of the inputs 54 and outputs 56 to other smart process objects may be configured by a configuration engineer during configuration of a process module by simply connecting other smart process objects to these inputs and outputs or by specifying particular communications that are to take place between smart process objects. Some of these inputs and outputs may be defined as being connected to the smart process objects connected at the predefined connection points for the smart process object as discussed above. These inputs 54 and outputs 56 may also be determined or defined by a set of rules within the rule database 50 and the connection matrix 52 defining the connections between different devices or entities within the plant 10. The inputs 54 and the outputs 56, which include data stores or buffers associated therewith will, generally speaking, be used to provide communications of data from other smart process objects to the smart process object 42e or to provide communications of data stored within or generated by the smart process object 42e to other smart process objects. These inputs and outputs may also be used to provide communications between the smart process object 42e and other objects within the process control system, such as control modules within the controllers 12, field devices 14, 16, etc.
As illustrated in
The methods 60 may also be provided to help simulate the operation of the process entity associated with the smart process object on the material flowing through that process entity. Thus, the methods 60 may be provided to calculate mass balances, energy balances, flows, temperatures, compositions, vapor states, and other system-level or stream level parameters associated with the material in the plant 10, to simulate operation of the element so as to calculate expected outputs based on provided inputs, etc. Of course, these are but a few of the methods that can be stored in and run by a smart process object 42e, and there are many other methods that may be used, with such methods generally being determined by the type of entity being represented, the manner in which that entity is connected in and used in a process plant as well as other factors. It is important to note that, while the smart process object 42e may store and execute methods that detect system-level conditions, errors, etc., these methods may also be used to determine other information about devices, logical elements, such as process control modules and loops, and other non-system-level entities. If desired, the methods 60 may be programmed or provided in any desired programming language, such as C, C++, C#, etc. or may be referenced to or may define applicable rules within the rule database 50 that should be run for the smart process object 42e during execution.
If desired, each smart process object may include a library of applicable algorithms or methods which may be used to define the simulation behavior of the smart process object when connected within a process module. Such a library is illustrated in a pull down menu 61 for the smart process object 42e of
If desired, the configuration engineer may instead provide a proprietary or other user supplied algorithm to define the simulation behavior of the process element defined by the smart process block. Such a user defined algorithm (illustrated as the “user defined” entry in the pull down menu 61) may be provided to and stored in a smart process object when that smart process object is placed within or used within a process module 39. This functionality enables the simulation behavior to be customized by the user to thereby provide for better or more accurate simulation. If desired, and as will be described in more detail later, the smart process objects 42 or each process module 39 may include an operator actuatable switch (such as an electronic switch or a flag) that disables the use of the simulation algorithms within the smart process objects and that, instead, causes the behavior of the process module to be determined by a high fidelity simulation package or program, such as one provided by HYSYS. In this case, the smart process object or the process module obtains simulated parameter data from the high fidelity simulation, as opposed to using the simulation algorithms within the smart process objects themselves.
During execution of a graphic display 35 or a process module 39 by the execution engine 48, the engine 48 implements the communications defined by the inputs 54 and outputs 56 to each of the smart process objects in the graphic display 35 or process module 39 and may implement the methods 60 for each of those objects to perform the functionality provided by the methods 60. As noted above, the functionality of the methods 60 may be located in programming within the smart process object or defined by a set of rules within the rule database 50 that the engine 48 executes, based on the type, class, identification, tag name, etc. of a smart process object, to implement the functionality defined by those rules.
It will be noted that an instance of the smart process object 42e has a tag or unique name within the context of the process module with which the smart process object 42e is associated and this tag or unique name may be used to provide communications to and from the smart process object 42e and may be referenced by the execution engine 48 during runtime. Process module tags should be unique within the control system configuration. This tagging convention enables elements within the process modules 39 to be referenced by elements within others of the process graphic displays 35, process modules 39 and even the control modules 29. Still further, the parameters of the smart process object 42e can be simple parameters, such as simple values, structured parameters or smart parameters that know the expected units and attributes associated therewith. Smart parameters can be interpreted and used by the process rules engine or execution engine 48 to assure all signals are being sent in the same units or are converted properly. Smart rules can also be used to turn on and turn off groups of alarms for the smart process objects (or process modules) to create a smart alarm strategy and/or interface for the operator. Still further, smart process object classes can be associated with equipment and module classes within the process control strategy of the plant 10 to provide a known linkage between a smart process object and the process variables it will need to interpret or access.
Smart process objects, when used in process graphic displays or process modules, may also include mode of operation, status, and alarm behavior so that these smart objects may be put in different modes during runtime, such as the off, start-up, and normal modes, may provide a status associated with the object based on its current operating state, and may provide alarms based on detected conditions, such as a parameter out of range, limited, high variability, etc. Smart process objects may also have a class/subclass hierarchy which enables them to be categorized in class libraries, to be collected together in a composite structure, etc. Still further, smart process objects may utilize information from other elements, such as control modules and other objects to enable the smart process object to recognize when its associated entity is busy or, for example, acquired by a batch control process within the plant 10.
Smart process objects may be associated with any desired process entity, such as physical devices like pumps, tanks, valves, etc., or logical entities such as process areas, measurements or actuators, control strategies, etc. In some cases, smart process objects may be associated with connectors, such a piping, conduit, wiring, conveyors, or any other device or entity that moves material, electricity, gas, etc. from one point to another point within the process. Smart process objects that are associated with connectors, sometimes referred to herein as smart links or connector elements, are also tagged (even though the actual device or connector itself may not be tagged or able to communicate within the process plant 10), and are generally used to represent material flow between other elements in the process.
Smart links will typically include properties or parameters that define how different materials or phenomena (such as electricity) flow through the connection (e.g. steam, electricity, water, sewage, etc.) These parameters may indicate the type and nature of flow (such as the general speed, friction coefficients, type of flow like turbulent or non-turbulent, electromagnetic, etc.) through the connector and the possible direction or directions of flow through the connector. Smart links may include programming or methods that ensure that the units of the source and destination object to which the smart link connects, match and, if not, may perform a conversion. The methods of the smart link may also model the flow through the connector using a model or an algorithm to estimate the speed or nature of the flow through the actual connectors, length and size of the physical connections, transport delay, etc. The stored parameters for the smart process object (such as friction parameters) may be used in these methods. Thus, in essence, the smart links or connector elements enable smart process objects to be aware of the other upstream and downstream objects or entities. Of course, smart links may, for example, define the connections between other objects, the type of fluid, such as liquid, gas, electricity, etc. within the system, the upstream and downstream side of the entities, which other entities are upstream and downstream of the entity for this smart process object, the direction of material, fluid, electric flow, etc. in any desired or convenient manner. In one embodiment, the matrix 52 may be created prior to execution of process flow modules and may define for the smart links the interconnections between the different devices within the plant and, therefore, the interconnections between the different smart process objects. In fact, the execution engine 48 may use the matrix 52 to ascertain the upstream and downstream entities and thereby define the communications between the smart process objects and the methods associated with the smart process objects. Still further, one or more sets of rules may be provided to be used by the smart process objects to interact with each other and to obtain data from each other as needed for the methods within the smart process objects and to resolve the impact of smart objects associated with output connections.
If desired, the smart process object 42e may also include hot links, such as URLs, to key documentation which may be applicable to the type of object, or which may be specific to the instance (depending on the criticality and application) of the device to which the smart process object 42e pertains. The documentation may be vendor supplied as well as user-specific. Some examples of documentation include configuration, start-up and shut-down procedures, operational and maintenance documentation. If desired, an operator may click on the object as displayed in an operator display to bring up the instance specific (if any) and generic documentation for the object or associated device. Also, the operator may be able to add/delete/change documentation independently of the system software such as maintenance requests, records of operational problems, etc. Furthermore, these hot links may be user configurable or changeable to provide the ability to add knowledge links to objects in the an operator interface, to provide for quick navigation to appropriate information associated with the object and to provide the ability to add work instructions specific to the customer, to the specific object type or even to the specific instance of the object.
While the process modules and process graphics are described above as being created together by the interconnection of different smart process objects, they may be created separately. For example, a process graphic may be created using smart process objects and, when completed, a process module for that graphic may be generated based on graphic elements and their interconnections in the graphic display. Alternatively, the process module may be first created using smart process objects and, once created, a graphic display for that process module may be automatically generated by the configuration application 38 using the graphic display elements in the smart process objects used to create the process module. Still further, a process module and a graphic display may be created separately and the individual elements within these two entities may be tied together manually by referencing one another (e.g., using the tag properties of the elements within the graphic display and the process module). Through this mechanism, a smart process object may be referenced by multiple displays. In any event, once created, a process graphic display and an associated process module may be run independently or separately, although they will typically communicate parameters and information back and forth as desired or needed.
Generally speaking, a set of predefined graphic elements may be provided in the configuration application to enable a user to construct process graphic displays that reflect the process plant. These displays have graphic display elements designed to dynamically show on-line measurements and actuators that interface with the control system and, as a result, may present information typically monitored and utilized by operators or other personnel involved in on-line operations. In addition, unmeasured parameters that reflect process operation may be calculated using on-line process simulation provided in the process modules and may be shown as an integral part of the associated graphic displays. In these and other ways, the process graphic displays may provide information typically monitored and utilized by plant personnel other than operators, such as engineering personnel or management.
Additionally, in an offline environment that may be used for engineering or training simulation purposes, the process simulation values provided by the process modules may be used and/or displayed in place of the actual process measurement values otherwise provided by the graphic elements and the associated control modules. These simulation values, which may be calculated by the associated process modules or a third-party simulation application (e.g., HYSYS), may be based on actual plant settings (e.g., an actuator position or state) as well as user-specified disturbance settings or values that may be established via, and depicted in, the process graphic displays and their respective graphic display elements. To these ends, a content layer of the process graphic display customized for an offline view of the process graphic displays may be generated and made available in, for instance, a training context. Further details regarding this content layer of the process graphic display are set forth below.
More generally, the process graphic displays may be used in a variety of contexts involving both on-line or control situations, and off-line or simulation situations, by a number of different types of personnel. To this end, each process graphic display may have a plurality of content layers dedicated to these different contexts, situations and personnel. Unlike past systems having separate, independent displays, these dedicated content layers are integrated portions of the objects used to define them, in the sense that the same object or objects have associated therewith the information necessary to generate all of the different content layers. As a result, the content layers of a single process graphic display provide customized views without requiring a configuration engineer or other design personnel to create a separate display for each of the views.
The breadth of information required to generate customized user interface displays for the different functions (operations, engineering, maintenance, management, etc.) is provided and supported by a flexible and extensible set of graphic display elements and the simulation algorithms associated therewith. These graphic display elements, which may correspond with a number of different types of process plant elements, including stream elements, process connection elements, actuator elements, processing elements, measurement elements and estimated property elements, may be predefined or otherwise made available for use in creating the process graphics display and its broad functionality. Custom elements may also be created or generated by a configuration engineer to cover specific types of the foregoing process plant elements, composites of such elements, and entirely new elements composed from basic graphic shapes (e.g., lines, circles, etc.).
Stream elements generally define a stream of material in the process plant and may be exposed in the graphic display to show the composition, density, flow, temperature, pressure, weight, and/or any other parameters defining the stream of material. Stream elements may be defined at the input of the process module and provided to elements within the process module to thereby enable the flow of material through the process module to be modeled and depicted in the graphic display. Similarly, stream elements may be illustrated at the output or end of the process module to illustrate in the graphic display the material output of the portion of the process plant depicted by the graphic display. Stream elements also may be used to define how different graphic displays (and the associated process modules) are connected with one another. For example, the output stream in one process module may be the input stream in another process module and may supply the values used at the input stream of the other process module. Streams may contain the following four parts: name (e.g., pH stream), direction (e.g., flow input), measurement (e.g., flow, pressure, temperature), and composition (e.g., nitrogen, ammonia, etc.) However, streams could have other parts or parameters if so desired.
Process connection elements define the manner in which materials within the plant, such as solid materials, liquid and vapor, and gases are delivered or carried from one device to another. To clearly illustrate the material flow through the process, three different types of process connections including piping, ducts and conveyors may be used. Of course other connection elements, such as electrical cables to address power flow in electrochemical processes, etc. may be used as well. Piping is generally used to illustrate (and simulate) liquid and high pressure vapor or gas flow within the plant. Ducts are generally used to illustrate (and simulate) low pressure gas flow within the plant. Conveyors are generally used to illustrate (and simulate) the movement of solid material between processing units. As a result, each process connection element defines the type of connection, such as a pipe connection, a duct connection or a conveyor connection that is used to provide material at the input or output of a device.
If desired, the properties of the material that is being transferred by a connection are determined by the upstream input. This information plus a connection status variable defining if the connection is complete may be made available as properties of the connection element on the graphic display. A connection element may start at a processing element output, an actuator element output or a stream element output. In a similar manner, a connection element may terminate at a processing element input, an actuator element input or a stream input.
The properties of a connection element may be automatically displayed when the cursor is placed over the connection element in the graphic display. Also, the properties associated with a connection element may be exposed for permanent display by placing a measurement or estimated property element (defined below) on the connection element. If desired, a connection element may be created by holding the left mouse button down over an element output (such as a stream output, a processing element output or an actuator element output) and, while holding down a button on the mouse, positioning the cursor over an element input. For the connection to be established successfully, the input and the output types (pipe, duct, or conveyor) of the upstream and the downstream elements must match. The connection will automatically take on the type of the upstream element.
If desired, piping elements can be shown or depicted in the process graphic display as a pipe connection, duct elements (e.g., air or gas) can be shown as a duct, and conveyor elements may be shown as conveyor belts. Piping, duct and conveyor element connections can be automatically routed between processing elements and arrows may be displayed outside the depiction of these elements to show the direction of the flow. If an upstream output is common to two connections, then a “T” element may be included in the pipe, duct or conveyor. Similarly, “T” elements may be used to combine multiple outputs. The color or other graphic property of a conveyor element may change to indicate its status, e.g., running/stopped, flowing/not flowing, plugged, etc. Generally speaking, the material flow along a conveyor is determined by the motor drive connected to the conveyor. Thus, a motor drive actuator (which is an actuator element described in more detail below) may be connected to the conveyor. Additionally, measurement elements (described below) can be connected to pipe, duct and conveyor elements to make it possible to expose measurements associated with the pipe, duct or conveyor elements, such as the speed of the conveyor or the flow of material in a pipe or duct, the properties of the material on or in the conveyor, pipe or duct, e.g. moisture or weight. Also, an exposed property element may be added to display properties of the material on or in the pipe, duct or conveyor that are not measured, for example, the composition of the material.
If desired, each of the piping, duct and conveyor connection elements may graphically and dynamically reflect a lost connection (e.g., by a color change), and that a selected property (pressure, temperature, length, etc.) is outside configured limits (e.g., by a color change). Furthermore, parameters calculated by the associated process module may be exposed in the graphic. For example, properties provided by the upstream connection, whether the connection status is bad or good, limits on one or more selected parameters of the connection element, etc. may be exposed in the graphic display to provide information to the operator about the connection element or the stream being transferred by the connection element.
Generally speaking, actuator elements are elements that perform some actuation function with respect to the stream and may be placed between different connection elements or between a processing element and a connection element. Examples of actuator elements include a regulating valve (with actuator), an on-off valve (with actuator), a pump (with motor), a force draft fan (with motor), an induced draft fan (with motor), an eductor (with on-off valve), a damper (with drive), a feeder (with variable speed motor), a conveyor motor drive (which may be attached to a conveyor element), etc.
The graphic depiction of the valve elements may dynamically reflect the implied valve position (by animation, for example), valve failure (by a color change, for example), the valve full open/closed position (by a color change, for example), and the AO, DO, DC, setpoint, PV, OUT, mode, etc. (by a numeric string or other indication, for example) of the associated control block controlling that valve. The simulation element associated with the valve elements (used in the process module) may have simulation algorithms that calculate parameters associated with the valve actuator, such as the discharge pressure, mass flow, liquid temperature, liquid composition, inlet pressure, and outlet pressure. These simulated or calculated parameters may be exposed in the process graphic, if so desired. However, the user or configuration engineer must usually configure the reference to an AO, DO or DC block in a control module associated with the valve as well as the valve type (e.g., linear, quick opening, equal percentage, valve sizing, etc.) and the stroke time from open to close. Of course, the simulation algorithms available to simulate the operation of the valve on the material flowing through the valve may be dependent upon the type of the valve and sizing information.
The graphic depiction of pump elements may dynamically reflect the motor status (using, for example, a color change), the associated DO or DC function block mode and setpoint (using, for example, strings), the motor speed (if variable speed drive is used), the AO setpoint, PV, OUT mode (if variable speed drive is used) and other desired parameters. Likewise, the process simulation (used in the process module) for this element may determine or calculate parameters such as the discharge pressure, liquid composition, liquid temperature, and mass flow, which parameters may be exposed in the graphic display. The user may need to define a pump curve based on the pump type. However, the user may configure the reference to the DO or DC block associated with the motor start/stop, the reference to the associated AO function block for variable speed drive (if used), and the pump curve (e.g., pressure versus flow) for the defining the operation of the pump.
The graphic depiction of a force draft or an induced fan actuator element may have a depiction that dynamically reflects the motor status, DO or DC function block mode and setpoint, motor speed (if variable speed drive is used), the AO setpoint, PV, OUT, DO or DC function block mode (if variable speed drive is used) and other desired parameters, any of which may be exposed in the graphic display. The process simulation element (used in a process module) for this element may determine or calculate parameters such as the discharge pressure, gas composition, gas temperature, and gas mass flow, which parameters may be exposed in the graphic display. The user may configure the reference to the associated DC block for motor start/stop, the reference to an AO block for variable speed drive (if used), and the fan curve (pressure versus flow) for defining the simulated operation of the fan.
In some cases a particular type of actuator may only be used with a specific type of connection, e.g., a pipe, a duct or a conveyor. The table below defines some example connection limitations for typical actuator elements.
Processing elements include plant equipment that processes the materials or streams in the plant in some manner. Generally speaking, all inputs and outputs to and from processing elements will be made through connection elements. Standard processing elements include tanks (vertical and horizontal), heaters, static mixers, reactors, mixers, air heaters and any other elements that perform some type of simple or standard processing activity. For standard processing elements, the user may specify the number of inputs and outputs to the element along with the physical equipment properties e.g. size, volume, etc. The simulation algorithm and static representation of these standard processing elements may be set so that they cannot be modified by the user but may be selectable as described above at configuration time. Of course, if desired, other, typically more complex plant equipment (such as distillation columns, evaporators, separators, boilers, etc.) may be implemented as custom processing elements. The static representation, number of inputs and outputs and the simulation algorithm of such custom processing elements may be modified to meet the user interface requirements. Once a custom processing element has been defined, it may be saved as a composite or template that may be reused or used as a starting point in the creation of other processing elements.
The tank standard processing element (either vertical or horizontal) may be configured based on the pipe connections to the tank and the tank element may dynamically reflect the level in the tank (using, e.g., dynamic animation), and the level at 100% or empty (using a color change, for example). The process module simulation for the tank may calculate and expose, via the graphic display, parameters such as the outlet temperature, the outlet composition, the liquid temperature and the simulated level of the tank. However, to tie the tank into the system, the user or configuration engineer may need to configure the number of input and output connections, the complete connections to the tank, the tank properties, such as size (e.g., diameter and height), etc.
The heater processing element may dynamically calculate and reflect, via the graphic display, the heat transfer coefficient (e.g., using a color change), the outlet product temperature, the inlet product temperature, the outlet pressure (assuming fixed drop), etc. A user or configuration engineer may need to configure the complete connections to the heater, the heater surface area and the heat transfer coefficient when clean.
Of course, other processing elements such as a static mixer, a reactor, a mixer, an air heater, a heat exchanger, etc. may have display and simulation capabilities that are tailored to these types of devices. Non-standard processing elements, such as distillation columns, evaporators, separators, boilers, etc. may be represented graphically using a custom processing element in which the simulation associated with the vessel may be user defined if not included in a standard selection. The processing in these elements may be described or defined as a step response model relating each input to each output of the vessel. Inputs may be gas and/or liquid streams. Optionally, the user may define the equations that describe the relationships between the inputs and outputs of the processing element and these equations may be stored in the process module using that element to perform simulation. If desired, some simple static graph representations may be provided to help the user quickly create the static graphics associated with a custom processing element. If these simple graphics are used, then the user may need to only specify the desired number of input and output connections and the type of connection supported (e.g., pipe, duct, or conveyor) supported by the custom processing element. In response, the graphic item will be displayed and can be immediately used in the creation of the operator graphic. If desired, the gains and any dynamics associated with each input and output of the process element may be specified if the user elects to specify the simulation algorithm as step responses. If the user selects a custom algorithm, then an expression editor may be provided for the user to define the simulation algorithm. Based on the method selected, the properties of the custom processing element outputs may be calculated differently. Furthermore, the user may reference one or more of the algorithms that they have defined in a separate software assembly.
Additionally, several pre-defined composites or templates may be provided for creating custom processing elements. These templates may include, for example, a boiler template having a custom algorithm that calculates the exit gas O2, the exit gas CO, the steam generated, the boiler drum level and the boiler draft. Such a template may be based on a single fuel input. However, by modifying the template, it is possible to simulate boilers with multiple fuels. Other pre-defined templates may include a specialized vessel-cyclone separator template, which may be used with in conjunction with a spray dryer custom processing element, and which may include a step response model to model the operation of the separator. Likewise, a column template, a spray dryer, and an evaporator body may utilize a step response model to define the expected process response. In an evaporator, based on the energy input and the concentration of the input flow, the concentration of the outlet flow and vapor release can be calculated. Multiple evaporator elements may be connected together along with heat exchanger and eductor elements to create a multiple-effect evaporator. Similarly, a specialized vessel-stack custom template processing element may be used with the boiler processing element. In this case, the properties of the inlet may be carried through the stack with no modifications if so desired, or to reflect emissions reductions performed in the stack.
Other types of elements that can be used to create process graphic displays and process modules include measurement elements and property elements. Measurement elements include transmitter elements, which may be used in the graphic display to access the measurement value associated with a physical transmitter, and switch elements. Generally, the transmitter element may dynamically reflect bad or uncertain status, the mode of the associated AI function block in the control module, the measurement value and units, etc. associated with an actual transmitter (sensor) or other data associated with the actual transmitter. In an off-line mode (or simulation mode) the transmitter element may be used to access and display the simulation value provided by the process module rather than the value associated with the AI or PCI block or may be used to provide a measurement value to the associated AI block in the control module as a measurement to be used in the simulated control routine. The transmitter element can be added to a connection element or to a processing element and, when such a transmitter element is added to the display, the user will generally need to identify the associated AI, PCI or DI block in controller scheme that is providing the measurement. In the on-line mode, the value of the measurement may be shown next to this measurement element. In the off-line mode (or simulation mode) the simulated value of the measurement (as developed by the corresponding process module) may be automatically displayed. In on-line operation, the user can elect to switch control and display to the simulated value in the event of a measurement failure.
A switch element may dynamically reflect a bad or uncertain status, the mode of the associated DI (e.g., manual or OS), and the discrete value of a switch (on, off, etc.) When in an off-line simulation mode, the user may use the switch display element to access and change the switch parameters in the graphic display and control module by selecting a simulation value or a manual value and status and by manually entering the value and status of the switch. However, a user may generally configure the switch element by providing a reference to an associated DI block in the control scheme, a reference to the element property that triggers the switch, and the limit and deadband associated with a change of state of the switch.
An estimated property element generally exposes an estimated property of the system as determined by the process module and may be added to a connection or processing element to display any property of that element. When this element is placed on a connection element or on a piece of equipment, the user can browse and select the properties that will be displayed. Thus, simulated properties that are not available through a physical measurement may be exposed through the use of the estimated properties element. Such an estimated property element may dynamically reflect a good/bad connection, the estimated property value(s), and a property that is outside of an associated limit or change. A user must generally configure the reference to property(s) to be displayed and the limits and color changes for the element if the property is outside of the limits.
As will be understood, by attaching transmitter elements and estimated property elements to processing elements, actuator elements and connection elements, the properties associated with the inputs and outputs of these process plant elements may be referenced during on-line operation or off-line simulation. These properties may also be made visible in the process graphic display.
Generally speaking, an operator may run or execute the configuration application 38 to create one or more process modules 39 or process graphic displays for implementation during operation of the process 10 or for implementation in a simulation environment. The configuration application 38 presents a configuration display, such as that illustrated in
When creating a graphic display, such as the graphic display 35c (or a process module), the configuration engineer may select and drag the smart process objects 67 and the elements 68 illustrated in the template section 65 onto the configuration section 66 and drop them there in any desired location. Generally, the configuration engineer will select and drag one or more smart device process objects 67a or non-smart elements 68 depicting devices onto the configuration section 66. The configuration engineer will then interconnect the smart device process objects within the configuration section 66 with smart connector process objects 67b and may place input and output streams 67c into the display. Moreover, non-smart elements may be added to the display. The configuration engineer may change the properties of each of the smart process objects during this process using pop-up properties menus, etc. and, in particular, may change the methods, parameters, tags, names, hot links, modes, classes, inputs and outputs, etc. associated with these smart process objects. When the process or configuration engineer has created a process module with each of the desired elements, typically representing a process configuration, area, etc., the configuration engineer may define rules or other functionality associated with the module. Such rules may be execution rules such as those associated with the performance of system-level methods, like mass balance and flow calculations. The process engineer or operator may also decide to add trends and faceplates that would be useful when the process display is on-line. After creating the graphic display 35c, the configuration engineer may save that display in a memory and may, at that time, or later, instantiate and download that display to the execution engine 48 in a manner that the execution engine 48 may provide a graphic display. Of course, the configuration engineer could create a process module in the same or similar manner although different graphics may be depicted for process module elements as opposed to process graphic display elements. Furthermore, the operator may elect to turn on levels of detail while they are running the plant. For example, one of the levels of detail would show the composition at each connection.
As noted above, the process graphic or process module may be provided with a specific tag. For example, smart process object elements within a graphics display or a process module may be provided a tag including an alias that can be filled in or selected at runtime by, for example, the execution engine 48 based on other factors, such as a piece of equipment or a route selected within the process control system. The use of alias names and indirect referencing in process control systems is discussed in detail in U.S. Pat. No. 6,385,496, which is assigned to the assignee of the present invention and which is hereby expressly incorporated by reference herein. Any of these techniques may be used to provide and resolve aliases in tags for the smart process objects described herein. With the use of aliases and the like, the same process module may include or be used to support different views for sets of equipment, etc.
The configuration application 38 may be used to design the display 64 of
Before further discussing the customized content layers made available to different types of users, the nature and configuration of process graphic displays are now described both generally and in connection with an exemplary display. Generally, when the configuration engineer creates a process module or a graphic display, the configuration application 38 automatically stores the smart process objects, along with the connections therebetween, in a database. This database may then be used to create other process modules and graphic displays using one or more of the same smart process objects. As such, when creating the further displays, the configuration engineer can simply reference the smart process object, as already created and stored within the database, and any methods, etc. stored therewith to place that smart process object in the further display. In this manner, the database may be populated as the process control modules and graphic displays are created and the database may be used at any time to create and execute other displays and modules using smart process objects which already exist within the process flow database. Using such a database, each smart process object within the database may support or be used in process modules and referenced in multiple graphic displays. As will also be understood, the process modules may be constructed by building displays for these modules and then specifying flow algorithms to be used in or associated with process modules. Of course, individual process modules may be spread across and executed by different computers and process modules may be communicatively connected to one other to operate in conjunction with each other, either on the same or on different computers. When this is done, input and output streams will be externally referenced to tie process modules together.
As noted above, the configuration engineer may, as part of the process module or graphic display creation, attach or provide the simulation algorithm of the process module. These simulation algorithms may be preconfigured to calculate or determine certain process or system-level properties, such as mass balance calculations, flow calculations, efficiency calculations, economic calculations, etc. with respect to the process depicted or modeled by the process module. As a result, the process modules themselves may have mode, status, and alarm behavior, can be assigned to workstations, and may be downloaded as part of the display downloads. If desired, the simulation algorithms may be executed by the execution engine 48 to perform mass or heat balancing, flow routing, flow efficiency, flow optimization, economic calculations related to process simulation or other desired calculations using the data provided in the smart process objects of the process module. Still further, these simulation algorithms may access parameters from the control strategy, i.e., the control modules associated with and downloaded to the controllers, field devices, etc. and may, conversely, provide data or information to these control modules.
It will be understood that the execution engine 48 is needed to enable the process algorithms to execute across an amalgamation of all process objects and links configured on all displays. Thus, the simulation algorithms (within the process modules) will generally execute regardless of whether any associated graphic display is loaded, i.e., called up and currently displaying information to a user. Of course, the simulation algorithms may be cross-checked across the entire process 10 or across defined subsets of the process 10. It will also be understood that, during execution of any particular process module, the execution engine 48 may provide a display to an operator (or other user type) on a display device depicting the interconnected objects or entities within the process module based on the graphic display associated with that process module. The parameters, graphics, etc. of the display will be determined by the configuration and interconnection of the smart elements within the process module. Furthermore, alarms and other information to be provided on this or other displays may be defined and generated by the methods within the smart process objects and the simulation algorithms associated with a particular process module. If desired, the execution engine 48 may provide a display for a process module to more than one operator interface or may be configured or set to provide no display, even though the execution engine 48 continues to execute the process flow module and thereby perform the methods, alarm behavior, flow algorithms, etc. associated therewith.
As can be easily seen, an output of the mixer 108 is connected to a heat exchanger 122 via piping and two transmitters 124 and 126. The cooling water stream 102 is delivered to the heat exchanger 122 via a valve 128 and exits the heat exchanger via a valve 130 to produce a return water stream element 131. Likewise, the output of the heat exchanger 122 is delivered through a transmitter element 132 and a valve 134 to provide an output Acetic Acid stream element 136. While not always called out in particular, the elements in the graphic display are in all cases connected with one another via piping connection elements.
It will be understood that display boxes 140, which may be generated as properties of the display elements themselves or which may be separate elements in the form of transmitter and estimated property elements or elements that reference blocks in control modules, are illustrated in the graphic display 100 to indicate or expose parameters, such as process variable (PV) values, setpoint (SP) values, OUT values, etc. associated with the different elements. Additionally, if the user were to place a cursor over some of the elements, the display 100 may illustrate other values associated with the referenced elements. For example, placing the cursor over one of the stream elements (such as the Acetic Acid stream output 136), may cause the graphic to indicate the composition, pressure, temperature, density, flow rate, etc. of the acid stream at this point in the process. Of course, the values and parameters displayed on the graphic display 100 may be delivered from an actual referenced transmitter within the process control system (such as from an AI block in the control system), or from a process module simulation element that simulates the functionality of the element. The graphic display 100 of
It will be understood that the functionality of the smart process objects, the graphic display elements and the process modules described herein may operate in the operator workstation 20 and does not need to be downloaded to and configured within the controllers, field devices, etc. within the plant 10, which makes this functionality easier to implement, view, change, etc. Further, this functionality enables system level determinations to be made more easily than within the process devices, controllers, etc. because the information pertaining to the devices on a system level is all typically available to the operator workstation 20 in general and to the execution engine 48 in particular whereas all of this information is not typically made available to each controller and field device within the process plant 10. However, when it is advantageous to do so, some of the logic associated with the process modules, such as primitives, may be embedded in the devices, equipment and controllers down within the process plant. The use of smart process objects to create integrated process control modules and graphic displays enables the execution engine 48 to, for example, automatically detect leaks and produce smart alarms with minimal amounts of user configuration activities, to calculate and track flow and mass balances within the plant 10, to track losses within the plant 10 and to provide higher level diagnostics for the plant 10 and to simulate the operation of the plant during engineering design and operator training.
As described above and shown in the exemplary process graphic display of
Before proceeding to describe further details regarding the smart process objects and the process graphic displays created therefrom, it should be noted that further information regarding smart process objects and process graphic displays and their use with process modules, may also be found in (i) U.S. patent application Ser. No. 10/278,469, entitled “Smart Process Modules and Objects in Process Plants,” which was filed on Oct. 22, 2002, (ii) U.S. patent application Ser. No. 10/625,481, entitled “Integration of Graphic Display Elements, Process Modules and Control Modules in Process Plants,” which was filed on Jul. 21, 2003, and (iii) U.S. patent application Ser. No. 11/014,307, entitled “Process Plant Simulation Using Smart Connection Elements,” which was filed Dec. 16, 2004, the entire disclosures of which are hereby expressly incorporated by reference in their entirety herein. For instance, in U.S. patent application Ser. No. 11/014,307, reference is made to FIGS. 5-8 thereof and the corresponding textual subject matter set forth in paragraphs [0075] to [0107], where FIG. 5 thereof shows nested process graphic displays, FIG. 6 thereof shows an association of a process module associated with a process graphic display, FIGS. 7A and 7B thereof show the communication interconnections between, and the integration of, a process graphic display, a process module and a control module, and FIG. 8 thereof shows an interconnected process and control modules providing advanced control and simulation capabilities.
As described above, the configuration application enables the construction of one or more graphic displays that generally reflect areas or portions of the process plant. More specifically, each graphic display includes a number of process graphic elements tied to respective process module elements of a process module designed to simulate a portion of the process plant. Each process graphic element and process module element may be data linked via, for example, the process control system, to a corresponding process plant element, which may be, for instance, a measurement element (e.g., a transmitter), an actuator (e.g., a motor), or a processing element (e.g., a reactor). Once configured, the process graphic elements are designed to dynamically depict information and content related to the on-line operation of the process plant elements, such as process measurements and status indications, by interfacing with the control system. In addition, unmeasured parameters that reflect on-line process operation may be calculated using the process simulation parameters, algorithms, etc. provided in the process modules, or process module elements thereof, and may be shown as an integral part of the associated graphic displays. As further described above, the process simulation provided by the process modules may also be used in an off-line environment used for engineering or training simulation purposes.
In support of the above-described off-line and on-line functionality, each process graphic display may be configured to include a plurality of customized views, or layers, each of which may reflect content or information specifically directed to (i) the current runtime context (e.g., on-line operation or off-line simulated operation), and (ii) the current user viewing the graphic displays. Potential uses when the process plant is off-line include operator training, instruction, and any other simulation contexts. When the process plant is on-line, a variety of types of operators and maintenance and other personnel may view the process graphic displays to interface with the process plant. In each case, the process graphic display may include or exclude certain content or information to suit the perspective of the user. In this way, the same process graphic display—together with the entirety of configuration information contained therein—is advantageously utilized in a variety of user contexts, uses and activities, thereby avoiding the need for creation and configuration of separate displays for each different context, use or activity.
Generally speaking, each process graphic display, or process graphic element, is defined to include multiple different views of content and information. These views are generally arranged as multiple layers of content of a specific graphic display. The data, information and content displayed in the layers are generated, calculated and stored in connection with the respective smart process objects represented in the graphic display. As described further below, portions of the content shown via the graphic display may appear static across the various layers, while other content may be added or dropped as appropriate for the specific context or current user. The added content may be specific to a particular process plant element (e.g., an actuator), or may be generally associated with the entire process module, process graphic display, plant area being depicted thereby, or any portion or process plant element thereof. The added content may present any information suitable for the process plant elements depicted via the graphic display given the user currently logged into the workstation displaying the graphic display and given the context in which the process module is executing (e.g., off-line or on-line).
In one embodiment, the content shown via the process graphic display may be determined or specified automatically given a user profile of the current user of the workstation or other display device on which the process graphic display is depicted. The user profile may specify or indicate one or more characteristics (e.g., an identification code) that are relied upon to make the determination. To this end, the user profile may have fields dedicated to process graphic display authorization levels or privileges. Alternatively, the user profile may specify or indicate characteristics or other details generally (i.e., not specifically as part of the graphic display authorization process). Alternatively, or in addition, the user profile may specify a security or other clearance level that determines which process graphic information or view (or views) may be accessed by the user. In cases where users have access to multiple content views or layers, a specific layer may be accessed via selection of a tab as shown in
With reference now to
The operations view of the graphic display 300 may include a center panel 302 in which a group of process graphic display elements are disposed. Each of the graphic display elements may have both static and dynamic portions to depict the operation (or simulated operation) of the corresponding process plant elements being depicted. Such dynamic depictions may include three-dimensional views, animation, and continuous or periodic updates of data shown in a data panel dedicated to a particular process plant element. As described above, each graphic display element may be tied in one-to-one correspondence with a process module element of a process module, which, in turn, may be tied in one-to-one correspondence with an element of the process plant. For the exemplary process module represented by the graphic display 300, the graphic display elements include representations of a reactor 304, a pump 306 disposed in a line carrying output from the reactor 304, a valve 308 controlling flow downstream of the pump 306, and a level sensor transmitter 310 in communication with the fluid in the reactor 304. The process module (not shown) corresponding with the graphic display 300 accordingly includes process module elements that could be shown in much the same manner as the process module shown in FIG. 7A of the above-referenced applications.
An operations view, or operator layer, of the graphic display 300 generally includes data panels indicating current, on-line parameters or values for the process plant element(s) with which the data panel is associated. For example, the level sensor transmitter 310 has a data panel 312 having a dynamic data field showing that the current fluid level in the reactor 304 is 2 meters. The data panel 312 also specifies a unit (M) for the measurement, which may be static or dynamic. The data panel 312 may also include a detailed display button 314, the selection of which by the operator generally produces a faceplate (not shown) providing further information regarding the level sensor, the level sensor transmitter, or any other process plant instrumentation or equipment associated with the value or parameter being sensed.
As described above, the value, parameter or, more generally, content displayed via the data panel 312 may be indicative of the actual, on-line operation of the process plant or of simulated operation in the event of, for instance, a failed measurement element. More generally, the operator content layer shown in
In another exemplary use of the operator layer, an operator in training may be viewing the graphic display 300 during a training exercise. In this case, the process graphic 300 may appear much the same, if not identically, to the manner in which it is displayed during on-line operation, thereby providing the operator in training an accurate representation of the actual workstation environment experienced by an operator of the process plant. However, in this training context, as well as other off-line contexts, the process graphic 300 may include an indication (not shown) signaling to the user that the process is off-line, and simulated operation is under way.
As described above, the graphics display shown in
The maintenance content layer 320 or view may provide content or information incorporating data from a simulated operation of the process plant in either a direct or indirect manner. For instance, the content layer 320 may display simulation content directly via a faceplate (which may be generated via, for instance, a selection button). In such cases, the simulation content may be representative of unmeasured or non-measurable process parameters, such as a mixture composition. Alternatively, or in addition, the graphic display 300 may include graphic elements having information or content calculated via the simulation. Such simulation content may be continuously displayed in a panel 322 having a directed shape to denote association with the process graphic element, such as the reactor 304. On the other hand, measured parameters that may assist in the diagnosis of process plant equipment may be compared with values generated from the simulation. To this end, the maintenance view or layer 320 may display one or both of the actual and simulated parameter values.
In one embodiment, the comparison of actual and simulated parameter values may be displayed in the layer 320 via a health indication or indicator. As shown in
The manner in which the health of process instrumentation or equipment is depicted via the graphic display 300 may vary between embodiments, as desired. In fact, the graphic editor provided with the configuration application may provide a user with the opportunity or capability to design the shape and other details regarding the manner in which a health indication is displayed. For example, the graphic editor may be used to configure a graphic display element having a new graphic element that renders a numerical health indication displayed as a dynamic field of a data panel. The health information or related content may be displayed via a faceplate or any other desired graphical element. In some cases, the faceplate may provide a multi-dimensional health assessment-instead of a single value (e.g., 60%). More generally, the maintenance view or layer 320 may include or utilize any number of different health indicators across the various instrumentation and equipment being monitored, and is not in any way limited to the exemplary type or approach shown in
In some embodiments, the health indications 324 and 326 may provide a link to an asset management routine or module, such as the Asset Management Solution (AMS) available from the Rosemount division of Emerson Process Management (www.rosemount.com). For instance, health indications and other content involving a comparison or calculation of actual operational and/or simulation data may be generated by the process module element (or process block), an abnormal situation prevention (ASP) block, or other fault detection element associated with the process plant element or device. The ASP block may be integrated with the process block or act independently thereof as part of an ASP environment executing during run-time. The functionality provided by the ASP block may generally involve statistical analysis and/or expert analysis to determine if a fault condition exists. Conventional multivariate statistical process control (MSPC) analysis or principal component analysis (PCA) may also or alternatively be utilized, and may be integrated and configured into the process control system as described in the commonly assigned international application concurrently filed herewith and also claiming priority to the U.S. provisional application referenced above and entitled “Integration Of Process Modules And Expert Systems In Process Plants,” the entire disclosure of which is hereby incorporated by reference, including those portions thereof directed to the aforementioned subject matter regarding MSPC analysis, PCA analysis, or other expert or expert-related analysis (see, e.g.,
The health indications 324 and 326 are examples of process graphic elements, or aspects thereof, that, while always included with every instantiation of the process graphic element, are not always shown in the graphic display 300. In other words, when the process module, process graphic display, or graphic display element, is being created or configured, a user may select from a palette the graphic element for placement in a canvas section, or work area, depicting the process module being built. Selection and placement of the process graphic element creates a specific instance thereof for the process module being built, thereby duplicating all of the methods, algorithms, settings, features or other aspects that define it. After placement, the element may be further configured and connected within the process graphic display (and associated process module). But unlike prior systems, this instance of the process graphic element (and the process module and graphic display) in which it resides will be used in the user interfaces for operations, maintenance, and other contexts, and for a variety of users via the multiple layers or views discussed herein. In this way, the element is only created and configured once, despite the variety of uses and contexts. The current user or context will determine how the element will be displayed, and specifically whether certain content or information associated therewith (e.g., a health indication) will be displayed.
The health indications 324 and 326 are also examples of items or aspects of a process graphic element that are produced automatically when the respective view or content layer is determined for depiction. Maintenance and other personnel for which the maintenance content layer is made available therefore receive the health indication content whenever the graphic display is produced or rendered for their use. This automatic production of content via a customized display layer may be determined by the user profile of the current user logged into the workstation. However, in alternative embodiments producing multiple content layers for a specific user, the health indication and other customized content or information may be produced in the graphic display at the user's discretion via selection of a layer tab or other command or option (e.g., “Show Health Indications”).
In the exemplary embodiment shown in
Other exemplary types of data that may be shown in an engineering content layer include or involve simulation information, such as estimated stream properties or properties of a unit, such as a calculated operating efficiency. The selection and placement of such content in the process graphic display may be accomplished using an estimated property element provided in a palette of pre-defined display elements in, for instance, a measurement category. Estimated property elements may be useful in, for instance, displaying a calculated pump discharge pressure. As noted above, the display of such estimated property elements is not limited to any one particular content layer, and may be specified and defined by the configuration engineer designing the process graphic display for use in any one or more content layers or views, as desired.
The content or information shown in the engineering content layer 330 may only be made available to users having engineering access privileges or, for example, an appropriate or sufficient security level or clearance. More generally, these and other characteristics of a user profile may be relied upon to determine whether a user has access to one or more of the customized views or content layer. To this end, the user profile may provide any one of a variety of indications of an access level, privilege or other clearance.
Another exemplary content layer for which access privileges or security clearance information in a user profile may be determinative of whether the content layer is displayed is a management content layer or view. An exemplary management view or content layer 340 is shown in
The management layer 340 shown in
Instead of having to create separate displays for both operators-in-training and their instructors,
A training instructor view 370 corresponding with the operator-in-training view 350 is shown in
The exemplary instructor layer 370 of
The introduction of simulated disturbances may be provided in connection with any of the graphic display elements, including, as described above, one of the manual valves 372, 374, 376, 378. More generally, if the instructor selects (e.g., clicks on or near) a graphic display element, such as a sensor or transmitter 382 on the outlet side of the pump 360, then a faceplate 384 may be provided as shown in
As used herein, a process plant element may refer to a single field device or other plant component, or a set of any such plant components. For instance, a single component may be an actuator (e.g., valve), a processing element (e.g., a reactor), a measurement or instrumentation element (e.g., a sensor or transmitter), a connection element (e.g., pipe), a stream element, etc. A set of process plant components may, but need not, refer to any subset of process plant elements that are depicted in a process graphic display.
When implemented, any of the software described herein 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, etc. Likewise, this software may be delivered to a user, a process plant or an operator workstation using 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, the World Wide Web, any other local area network or wide area network, etc. (which delivery is viewed as being the same as or interchangeable with providing such software via a transportable storage medium). Furthermore, this software may be provided directly without modulation or encryption or may be modulated and/or encrypted using any suitable modulation carrier wave and/or encryption technique before being transmitted over a communication channel.
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.
This application is a regular filed application of, and claims, for the purposes of priority, the benefit of U.S. Provisional Application Ser. No. 60/567,980, entitled “Graphical User Interface for Representing, Monitoring, and Interacting with Process Control Systems,” which was filed on May 4, 2004, and which this application hereby expressly incorporates by reference herein in its entirety. This application is also related to U.S. patent application Ser. No. 10/625,481, entitled “Integration of Graphic Display Elements, Process Modules and Control Modules in Process Plants,” which was filed on Jul. 21,2003, and which published as U.S. Publication No. 2004/0153804 on Aug. 5, 2004, which, in turn, is a Continuation-in-Part of U.S. patent application Ser. No. 10/278,469, entitled “Smart Process Modules and Objects in Process Plants,” which was filed on Oct. 22, 2002, and which published as U.S. Publication No. 2004/0075689 on Apr. 22, 2004, the entire disclosures of which are hereby expressly incorporated by reference herein in their entirety. This application is also related to U.S. patent application Ser. No. 10/368,151 entitled “Module Class Objects in a Process Plant Configuration System,” which was filed on Feb. 18, 2003, and which published as U.S. Publication No. 2004/0199925 on Oct. 7, 2004, the entire disclosure of which is hereby expressly incorporated by reference herein in its entirety. This application is also related to the following patent applications, which are being filed as International (PCT) applications on the same date as this application and which this application hereby expressly incorporates by reference herein in their entirety: “Associated Graphic Displays in a Process Environment” Ser. No. 10/589,712; “User Configurable Alarms and Alarm Trending for Process Control Systems” Ser. No. 10/574,570; “Integration of Process Modules and Expert Systems in Process Plants” Ser. No. 10/590,573; “Scripted Graphics in a Process Environment” Ser. No. 10/589,845; “Graphics Integration into a Process Configuration and Control Environment” Ser. No. 10/591,804; “Graphic Element with Multiple Visualizations in a Process Environment” Ser. No. 10/590,574; “System for Configuring Graphic Display Elements and Process Modules in Process Plants” Ser. No. 10/575,022; “Graphic Display Configuration Framework for Unified Process Control System Interface” Ser. No. 10/575,173; “Markup Language-Based, Dynamic Process Graphics in a Process Plant User Interface” Ser. No. 10/590,550; “Methods and Apparatus for Modifying Process Control Data” PCT/US05/15596 and Ser. No. 11/556,612; “Methods and Apparatus for Accessing Process Control Data” PCT/US05/15585 and Ser. No. 11/556,445; “Integrated Graphical Runtime Interface for Process Control Systems” PCT/US05/15439 and Ser. No. 11/556,347; “Service-Oriented Architecture for Process Control Systems” PCT/US05/15394 and Ser. No. 11/556,554.
| Filing Document | Filing Date | Country | Kind | 371c Date |
|---|---|---|---|---|
| PCT/US2005/015392 | 5/4/2005 | WO | 00 | 8/10/2007 |
| Publishing Document | Publishing Date | Country | Kind |
|---|---|---|---|
| WO2005/109124 | 11/17/2005 | WO | A |
| Number | Name | Date | Kind |
|---|---|---|---|
| RE30280 | Berman et al. | May 1980 | E |
| 4244385 | Hotine | Jan 1981 | A |
| 4506324 | Healy | Mar 1985 | A |
| 4512747 | Hitchens et al. | Apr 1985 | A |
| 4628435 | Tashiro et al. | Dec 1986 | A |
| 4663704 | Jones et al. | May 1987 | A |
| 4736320 | Bristol | Apr 1988 | A |
| 4843538 | Lane et al. | Jun 1989 | A |
| 4885717 | Beck et al. | Dec 1989 | A |
| 4972328 | Wu et al. | Nov 1990 | A |
| 4977529 | Gregg et al. | Dec 1990 | A |
| 4985857 | Bajpai et al. | Jan 1991 | A |
| 5014208 | Wolfson | May 1991 | A |
| 5021947 | Campbell et al. | Jun 1991 | A |
| 5041964 | Cole et al. | Aug 1991 | A |
| 5051898 | Wright et al. | Sep 1991 | A |
| 5079731 | Miller et al. | Jan 1992 | A |
| 5092449 | Bolin et al. | Mar 1992 | A |
| 5097412 | Orimo et al. | Mar 1992 | A |
| 5119468 | Owens | Jun 1992 | A |
| 5168441 | Onarheim et al. | Dec 1992 | A |
| 5218709 | Fijany et al. | Jun 1993 | A |
| 5268834 | Sanner et al. | Dec 1993 | A |
| 5321829 | Zifferer | Jun 1994 | A |
| 5347446 | Iino et al. | Sep 1994 | A |
| 5347466 | Nichols et al. | Sep 1994 | A |
| 5361198 | Harmon et al. | Nov 1994 | A |
| 5408412 | Hogg et al. | Apr 1995 | A |
| 5408603 | Van de Lavoir et al. | Apr 1995 | A |
| 5421017 | Scholz et al. | May 1995 | A |
| 5428555 | Starkey et al. | Jun 1995 | A |
| 5485600 | Joseph et al. | Jan 1996 | A |
| 5485620 | Sadre et al. | Jan 1996 | A |
| 5499333 | Doudnikoff et al. | Mar 1996 | A |
| 5509116 | Hiraga et al. | Apr 1996 | A |
| 5530643 | Hodorowski | Jun 1996 | A |
| 5546301 | Agrawal et al. | Aug 1996 | A |
| 5555385 | Osisek | Sep 1996 | A |
| 5576946 | Bender et al. | Nov 1996 | A |
| 5594858 | Blevins | Jan 1997 | A |
| 5603018 | Terada et al. | Feb 1997 | A |
| 5611059 | Benton et al. | Mar 1997 | A |
| 5631825 | van Weele et al. | May 1997 | A |
| 5680409 | Qin et al. | Oct 1997 | A |
| 5706455 | Benton et al. | Jan 1998 | A |
| 5752008 | Bowling | May 1998 | A |
| 5768119 | Havekost et al. | Jun 1998 | A |
| 5782330 | Mehlert et al. | Jul 1998 | A |
| 5796602 | Wellan et al. | Aug 1998 | A |
| 5801942 | Nixon et al. | Sep 1998 | A |
| 5806053 | Tresp et al. | Sep 1998 | A |
| 5812394 | Lewis et al. | Sep 1998 | A |
| 5818736 | Leibold | Oct 1998 | A |
| 5821934 | Kodosky et al. | Oct 1998 | A |
| 5826060 | Santoline et al. | Oct 1998 | A |
| 5828851 | Nicon et al. | Oct 1998 | A |
| 5838563 | Dove et al. | Nov 1998 | A |
| 5841654 | Verissimo et al. | Nov 1998 | A |
| 5857102 | McChesney et al. | Jan 1999 | A |
| 5862052 | Nixon et al. | Jan 1999 | A |
| 5892939 | Call et al. | Apr 1999 | A |
| 5898860 | Leibold | Apr 1999 | A |
| 5901313 | Wolf et al. | May 1999 | A |
| 5903455 | Sharpe, Jr. et al. | May 1999 | A |
| 5909368 | Nixon et al. | Jun 1999 | A |
| 5909916 | Foster et al. | Jun 1999 | A |
| 5926177 | Hatanaka et al. | Jul 1999 | A |
| 5929855 | Benton et al. | Jul 1999 | A |
| 5940294 | Dove | Aug 1999 | A |
| 5950006 | Crater et al. | Sep 1999 | A |
| 5960214 | Sharpe, Jr. et al. | Sep 1999 | A |
| 5970430 | Burns et al. | Oct 1999 | A |
| 5980078 | Krivoshein et al. | Nov 1999 | A |
| 5995753 | Walker | Nov 1999 | A |
| 5995916 | Nixon et al. | Nov 1999 | A |
| 6003037 | Kassabgi et al. | Dec 1999 | A |
| 6023644 | Kinsman | Feb 2000 | A |
| 6028998 | Gloudeman et al. | Feb 2000 | A |
| 6032208 | Nixon et al. | Feb 2000 | A |
| 6041171 | Blaisdell et al. | Mar 2000 | A |
| 6052130 | Bardon et al. | Apr 2000 | A |
| 6078320 | Dove et al. | Jun 2000 | A |
| 6094600 | Sharpe, Jr. et al. | Jul 2000 | A |
| 6098116 | Nixon et al. | Aug 2000 | A |
| 6138174 | Keeley | Oct 2000 | A |
| 6146143 | Huston et al. | Nov 2000 | A |
| 6157864 | Schwenke et al. | Dec 2000 | A |
| 6161051 | Hafemann et al. | Dec 2000 | A |
| 6167316 | Gloudeman et al. | Dec 2000 | A |
| 6173208 | Park et al. | Jan 2001 | B1 |
| 6178393 | Irvin | Jan 2001 | B1 |
| 6192390 | Berger et al. | Feb 2001 | B1 |
| 6195591 | Nixon et al. | Feb 2001 | B1 |
| 6201996 | Crater et al. | Mar 2001 | B1 |
| 6233586 | Chang et al. | May 2001 | B1 |
| 6268853 | Hoskins et al. | Jul 2001 | B1 |
| 6298454 | Schleiss et al. | Oct 2001 | B1 |
| 6362839 | Hamilton et al. | Mar 2002 | B1 |
| 6385496 | Irwin et al. | May 2002 | B1 |
| 6396516 | Beatty | May 2002 | B1 |
| 6421571 | Spriggs et al. | Jul 2002 | B1 |
| 6442515 | Varma et al. | Aug 2002 | B1 |
| 6445963 | Blevins et al. | Sep 2002 | B1 |
| 6449624 | Hammack et al. | Sep 2002 | B1 |
| 6477435 | Ryan et al. | Nov 2002 | B1 |
| 6477527 | Carey et al. | Nov 2002 | B2 |
| 6480860 | Monday | Nov 2002 | B1 |
| 6505519 | Henry et al. | Jan 2003 | B2 |
| 6510351 | Blevins et al. | Jan 2003 | B1 |
| 6515683 | Wright | Feb 2003 | B1 |
| 6522934 | Irwin et al. | Feb 2003 | B1 |
| 6535122 | Bristol | Mar 2003 | B1 |
| 6546297 | Gaston et al. | Apr 2003 | B1 |
| 6571133 | Mandl et al. | May 2003 | B1 |
| 6577908 | Wojsznis et al. | Jun 2003 | B1 |
| 6587108 | Guerlain et al. | Jul 2003 | B1 |
| 6591244 | Jim et al. | Jul 2003 | B2 |
| 6615090 | Blevins et al. | Sep 2003 | B1 |
| 6618630 | Jundt et al. | Sep 2003 | B1 |
| 6618745 | Christensen et al. | Sep 2003 | B2 |
| 6633782 | Schleiss et al. | Oct 2003 | B1 |
| 6646545 | Bligh | Nov 2003 | B2 |
| 6647315 | Sherriff et al. | Nov 2003 | B1 |
| 6668257 | Greef et al. | Dec 2003 | B1 |
| 6684261 | Orton et al. | Jan 2004 | B1 |
| 6684385 | Bailey et al. | Jan 2004 | B1 |
| 6687698 | Nixon et al. | Feb 2004 | B1 |
| 6691280 | Dove et al. | Feb 2004 | B1 |
| 6704737 | Nixon et al. | Mar 2004 | B1 |
| 6711629 | Christensen et al. | Mar 2004 | B1 |
| 6754885 | Dardinski et al. | Jun 2004 | B1 |
| 6758102 | Henry et al. | Jul 2004 | B2 |
| 6760711 | Gillett et al. | Jul 2004 | B1 |
| 6788980 | Johnson | Sep 2004 | B1 |
| 6795798 | Eryurek et al. | Sep 2004 | B2 |
| 6810337 | Ashcraft et al. | Oct 2004 | B1 |
| 6826521 | Hess et al. | Nov 2004 | B1 |
| 6904415 | Krahn et al. | Jun 2005 | B2 |
| 6948173 | Isom | Sep 2005 | B1 |
| 6957110 | Wewalaarachchi et al. | Oct 2005 | B2 |
| 6973508 | Shepard et al. | Dec 2005 | B2 |
| 6981424 | Henry et al. | Jan 2006 | B2 |
| 7043311 | Nixon et al. | May 2006 | B2 |
| 7050083 | Yoo et al. | May 2006 | B2 |
| 7050863 | Mehta et al. | May 2006 | B2 |
| 7062718 | Kodosky et al. | Jun 2006 | B2 |
| 7065476 | Dessureault et al. | Jun 2006 | B2 |
| 7086009 | Resnick et al. | Aug 2006 | B2 |
| 7110835 | Blevins et al. | Sep 2006 | B2 |
| 7113834 | Wojsznis et al. | Sep 2006 | B2 |
| 7117052 | Lucas et al. | Oct 2006 | B2 |
| 7146231 | Schleiss et al. | Dec 2006 | B2 |
| 7165226 | Thurner et al. | Jan 2007 | B2 |
| 7210039 | Rodgers et al. | Apr 2007 | B2 |
| 7210095 | Mor | Apr 2007 | B1 |
| 7219306 | Kodosky et al. | May 2007 | B2 |
| 7234138 | Crevatin | Jun 2007 | B2 |
| 7308473 | Thomas et al. | Dec 2007 | B1 |
| 7320005 | Li et al. | Jan 2008 | B2 |
| 7330768 | Scott et al. | Feb 2008 | B2 |
| 7376661 | Larson | May 2008 | B2 |
| 7404476 | Yoshida | Jul 2008 | B2 |
| 7526347 | Lucas et al. | Apr 2009 | B2 |
| 7647126 | Blevins et al. | Jan 2010 | B2 |
| 7647558 | Ucar et al. | Jan 2010 | B2 |
| 7680546 | Gilbert et al. | Mar 2010 | B2 |
| 7702409 | Lucas et al. | Apr 2010 | B2 |
| 7703032 | Wells | Apr 2010 | B2 |
| 7707550 | Resnick et al. | Apr 2010 | B2 |
| 20010007984 | Fattah et al. | Jul 2001 | A1 |
| 20010010053 | Ben-Shachar et al. | Jul 2001 | A1 |
| 20010051949 | Carey et al. | Dec 2001 | A1 |
| 20020004796 | Vange et al. | Jan 2002 | A1 |
| 20020010571 | Daniel et al. | Jan 2002 | A1 |
| 20020019672 | Paunonen | Feb 2002 | A1 |
| 20020022894 | Eryurek et al. | Feb 2002 | A1 |
| 20020022895 | Genise et al. | Feb 2002 | A1 |
| 20020046290 | Andersson et al. | Apr 2002 | A1 |
| 20020055790 | Havekost | May 2002 | A1 |
| 20020059282 | Andersson et al. | May 2002 | A1 |
| 20020077711 | Nixon et al. | Jun 2002 | A1 |
| 20020123864 | Eryurek et al. | Sep 2002 | A1 |
| 20020156872 | Brown | Oct 2002 | A1 |
| 20020184521 | Lucovsky et al. | Dec 2002 | A1 |
| 20020184610 | Chong et al. | Dec 2002 | A1 |
| 20020193888 | Wewalaarachchi et al. | Dec 2002 | A1 |
| 20020199123 | McIntyre et al. | Dec 2002 | A1 |
| 20030005169 | Perks et al. | Jan 2003 | A1 |
| 20030009754 | Rowley et al. | Jan 2003 | A1 |
| 20030014500 | Schleiss et al. | Jan 2003 | A1 |
| 20030028269 | Spriggs et al. | Feb 2003 | A1 |
| 20030028683 | Yorke et al. | Feb 2003 | A1 |
| 20030033037 | Yuen et al. | Feb 2003 | A1 |
| 20030041130 | Harrisville-Wolff et al. | Feb 2003 | A1 |
| 20030084201 | Edwards et al. | May 2003 | A1 |
| 20030126136 | Omoigui | Jul 2003 | A1 |
| 20030153988 | Shepard et al. | Aug 2003 | A1 |
| 20030191803 | Chinnici et al. | Oct 2003 | A1 |
| 20030200062 | Dessureault et al. | Oct 2003 | A1 |
| 20030226009 | Maeda et al. | Dec 2003 | A1 |
| 20030236576 | Resnick et al. | Dec 2003 | A1 |
| 20030236577 | Clinton | Dec 2003 | A1 |
| 20040021679 | Chapman et al. | Feb 2004 | A1 |
| 20040036698 | Thurner et al. | Feb 2004 | A1 |
| 20040059929 | Rodgers et al. | Mar 2004 | A1 |
| 20040075689 | Schleiss et al. | Apr 2004 | A1 |
| 20040075857 | Akiyoshi et al. | Apr 2004 | A1 |
| 20040078182 | Nixon et al. | Apr 2004 | A1 |
| 20040133487 | Hanagan et al. | Jul 2004 | A1 |
| 20040153804 | Blevins et al. | Aug 2004 | A1 |
| 20040162792 | Satou et al. | Aug 2004 | A1 |
| 20040181746 | McLure et al. | Sep 2004 | A1 |
| 20040186927 | Eryurek et al. | Sep 2004 | A1 |
| 20040199925 | Nixon et al. | Oct 2004 | A1 |
| 20040205656 | Reulein et al. | Oct 2004 | A1 |
| 20040249483 | Wojsznis et al. | Dec 2004 | A1 |
| 20040267515 | McDaniel et al. | Dec 2004 | A1 |
| 20050005079 | Boudou et al. | Jan 2005 | A1 |
| 20050015439 | Balaji et al. | Jan 2005 | A1 |
| 20050027376 | Lucas et al. | Feb 2005 | A1 |
| 20050039034 | Doyle et al. | Feb 2005 | A1 |
| 20050062677 | Nixon et al. | Mar 2005 | A1 |
| 20050096872 | Blevins et al. | May 2005 | A1 |
| 20050164684 | Chen et al. | Jul 2005 | A1 |
| 20050182758 | Seitz et al. | Aug 2005 | A1 |
| 20050197786 | Kataria et al. | Sep 2005 | A1 |
| 20050197803 | Eryurek et al. | Sep 2005 | A1 |
| 20050197805 | Eryurek et al. | Sep 2005 | A1 |
| 20050197806 | Eryurek et al. | Sep 2005 | A1 |
| 20050217971 | Kim | Oct 2005 | A1 |
| 20050222698 | Eryurek et al. | Oct 2005 | A1 |
| 20050277403 | Schmidt et al. | Dec 2005 | A1 |
| 20060031354 | Patrick et al. | Feb 2006 | A1 |
| 20060031481 | Patrick et al. | Feb 2006 | A1 |
| 20060136555 | Patrick et al. | Jun 2006 | A1 |
| 20060259524 | Horton | Nov 2006 | A1 |
| 20070006149 | Resnick et al. | Jan 2007 | A1 |
| 20070061786 | Zhou et al. | Mar 2007 | A1 |
| 20070078529 | Thiele et al. | Apr 2007 | A1 |
| 20070129917 | Blevins et al. | Jun 2007 | A1 |
| 20070156264 | Schleiss et al. | Jul 2007 | A1 |
| 20070165031 | Gilbert et al. | Jul 2007 | A1 |
| 20070170037 | Kuroda | Jul 2007 | A1 |
| 20070211079 | Nixon et al. | Sep 2007 | A1 |
| 20070244582 | Wolf | Oct 2007 | A1 |
| 20070282480 | Pannese et al. | Dec 2007 | A1 |
| 20080034367 | Patrick et al. | Feb 2008 | A1 |
| 20080116035 | Ogimura | May 2008 | A1 |
| 20080140760 | Conner et al. | Jun 2008 | A1 |
| 20100168874 | Lucas et al. | Jul 2010 | A1 |
| Number | Date | Country |
|---|---|---|
| 1130460 | Sep 1996 | CN |
| 101833289 | Sep 2010 | CN |
| 101893861 | Nov 2010 | CN |
| 0 482 523 | Apr 1992 | EP |
| 0813129 | Dec 1997 | EP |
| 1 030 251 | Aug 2000 | EP |
| 1122652 | Aug 2001 | EP |
| 1 204 033 | May 2002 | EP |
| 1 284 446 | Feb 2003 | EP |
| 1 538 619 | Jun 2005 | EP |
| 2 083 258 | Mar 1982 | GB |
| 2 328 523 | Feb 1999 | GB |
| 2 370 665 | Jul 2000 | GB |
| 2 348 020 | Sep 2000 | GB |
| 2349958 | Nov 2000 | GB |
| 2 355 545 | Apr 2001 | GB |
| 2 371 884 | Aug 2002 | GB |
| 2372365 | Aug 2002 | GB |
| 2 377 045 | Dec 2002 | GB |
| 2 395 801 | Jun 2004 | GB |
| 2 398 659 | Aug 2004 | GB |
| 2 415 809 | Jan 2006 | GB |
| 2 417 574 | Mar 2006 | GB |
| 2 417 575 | Mar 2006 | GB |
| 2 418 030 | Mar 2006 | GB |
| 2 418 031 | Mar 2006 | GB |
| 2 429 388 | Feb 2007 | GB |
| 2 446 343 | Aug 2008 | GB |
| 1-298389 | Dec 1979 | JP |
| 60-075909 | Apr 1985 | JP |
| 62-223778 | Oct 1987 | JP |
| 62-223778 | Oct 1987 | JP |
| 1-116706 | May 1989 | JP |
| 1-120593 | May 1989 | JP |
| 01-241589 | Sep 1989 | JP |
| 1-241589 | Sep 1989 | JP |
| 2-310602 | Dec 1990 | JP |
| 3-257509 | Nov 1991 | JP |
| 03-257509 | Nov 1991 | JP |
| 5-54277 | Mar 1993 | JP |
| 05-079858 | Mar 1993 | JP |
| 5-079858 | Mar 1993 | JP |
| 6-26093 | Feb 1994 | JP |
| 6-044479 | Feb 1994 | JP |
| 6-274297 | Sep 1994 | JP |
| 7-036538 | Feb 1995 | JP |
| 7-248941 | Sep 1995 | JP |
| 8-190422 | Jul 1996 | JP |
| 8-314760 | Nov 1996 | JP |
| 09-500996 | Jan 1997 | JP |
| 9-500996 | Jan 1997 | JP |
| 9-134213 | May 1997 | JP |
| 9-330013 | Dec 1997 | JP |
| 10-505179 | May 1998 | JP |
| 10-149207 | Jun 1998 | JP |
| 11-007315 | Jan 1999 | JP |
| 11-345023 | Dec 1999 | JP |
| 2000-050531 | Feb 2000 | JP |
| 2000-249782 | Sep 2000 | JP |
| 2000-259228 | Sep 2000 | JP |
| 2000-311004 | Nov 2000 | JP |
| 2000-346299 | Dec 2000 | JP |
| 2001-195121 | Jul 2001 | JP |
| 2002-108600 | Apr 2002 | JP |
| 2002-140114 | May 2002 | JP |
| 2002-215221 | Jul 2002 | JP |
| 2002-258936 | Sep 2002 | JP |
| 2002-258936 | Sep 2002 | JP |
| 2002-268737 | Sep 2002 | JP |
| 2002-303564 | Oct 2002 | JP |
| 2004-199655 | Jul 2004 | JP |
| 2003-34629 | Sep 2004 | JP |
| 9-288512 | Nov 2007 | JP |
| WO-9119237 | Dec 1991 | WO |
| WO-9504314 | Feb 1995 | WO |
| WO-9727540 | Jul 1997 | WO |
| WO-9738362 | Oct 1997 | WO |
| WO-9745778 | Dec 1997 | WO |
| WO-9853398 | Nov 1998 | WO |
| WO-0023798 | Apr 2000 | WO |
| WO-0070417 | Nov 2000 | WO |
| WO-0109690 | Feb 2001 | WO |
| WO-0165322 | Sep 2001 | WO |
| WO-02071169 | Sep 2002 | WO |
| WO-03003198 | Jan 2003 | WO |
| WO-03038584 | May 2003 | WO |
| WO-03048922 | Jun 2003 | WO |
| WO-03075206 | Sep 2003 | WO |
| WO-03075206 | Sep 2003 | WO |
| WO-2004025437 | Mar 2004 | WO |
| WO-2004086160 | Oct 2004 | WO |
| WO-2005107409 | Nov 2005 | WO |
| WO-2005107410 | Nov 2005 | WO |
| WO-2005107416 | Nov 2005 | WO |
| WO-2005109122 | Nov 2005 | WO |
| WO-2005109123 | Nov 2005 | WO |
| WO-2005109124 | Nov 2005 | WO |
| WO-2005109125 | Nov 2005 | WO |
| WO-2005109126 | Nov 2005 | WO |
| WO-2005109127 | Nov 2005 | WO |
| WO-2005109128 | Nov 2005 | WO |
| WO-2005109129 | Nov 2005 | WO |
| WO-2005109130 | Nov 2005 | WO |
| WO-2005109131 | Nov 2005 | WO |
| WO-2005109250 | Nov 2005 | WO |
| WO-2005119381 | Dec 2005 | WO |
| WO-2007067645 | Jun 2007 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 20080066004 A1 | Mar 2008 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60567980 | May 2004 | US |
