WO2005101196A2 - Integrated configuration system for use in a process plant - Google Patents
Integrated configuration system for use in a process plant Download PDFInfo
- Publication number
- WO2005101196A2 WO2005101196A2 PCT/US2005/009371 US2005009371W WO2005101196A2 WO 2005101196 A2 WO2005101196 A2 WO 2005101196A2 US 2005009371 W US2005009371 W US 2005009371W WO 2005101196 A2 WO2005101196 A2 WO 2005101196A2
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- configuration
- ofthe
- user
- entity
- viewing
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/34—Graphical or visual programming
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/36—Software reuse
Definitions
- the present disclosure relates generally to configuring a process plant and, more particularly, to an integrated configuration system for use in a process plant that integrates the viewing and configuration activities associated with multiple applications used within the process plant.
- DESCRIPTION OF THE RELATED ART typically include one or more centralized or decentralized process controllers communicatively coupled to at least one host or operator workstation and to one or more process control and instrumentation devices such as, for example, field devices, via analog, digital or combined analog/digital buses.
- Field devices which may be, for example, valves, valve positioners, switches, transmitters, and sensors (e.g., temperature, pressure, and flow rate sensors), are located within the process plant environment, and perform functions within the process such as opening or closing valves, measuring process parameters, increasing or decreasing fluid flow, etc.
- Smart field devices such as field devices conforming to the well-known FOUNDATIONTM Fieldbus (hereinafter “Fieldbus”) protocol may also perform control calculations, alarming functions, and other control functions commonly implemented within the process controller.
- Fieldbus Fieldbus
- the process controllers which are typically located within the process plant environment, receive signals indicative of process measurements or process variables made by or associated with the field devices and/or other information pertaining to the field devices, and execute controller applications.
- the controller applications implement, for example, different control modules that make process control decisions, generate control signals based on the received information, and coordinate with the control modules or blocks being performed in the field devices such as HART ® and Fieldbus field devices.
- the control modules in the process controllers send the control signals over the communication lines to the field devices to thereby control the operation ofthe process.
- Information from the field devices and the process controllers is typically made available to one or more other hardware devices such as, for example, operator workstations, personal computers, handheld devices, data historians, report generators, centralized databases, etc.
- Additional devices include, for example, power supply equipment, power generation and distribution equipment, rotating equipment such as turbines, motors, etc., which are located at numerous places in a typical plant. While this additional equipment does not necessarily create or use process variables and, in many instances, is not controlled or even coupled to a process controller for the purpose of affecting the process operation, this I equipment is nevertheless important to, and ultimately necessary for proper operation ofthe process.
- Operator workstations which are typically connected to the process controllers through communication connections such as a direct or wireless bus, Ethernet, modem, phone line, and the like, have processors and memories that are adapted to run software or firmware such as process control configuration applications.
- each ofthe DeltaNTM and Ovation control systems sold by Emerson Process Management, includes multiple applications stored within and executed by different devices located at diverse places within a process plant.
- a process control configuration application which may reside in one or more operator workstations, enables a user to create or change process control modules and download these process control modules via a data highway to distributed process controllers or field devices in the DeltaNTM and Ovation systems.
- control modules are made up of communicatively interconnected function blocks, which are objects in an object- oriented programming protocol that perform functions within the control scheme based on inputs thereto, and provide outputs to other function blocks within the control scheme.
- Each process controller and, in some cases, the smart field devices may store and execute a controller application that runs the control modules assigned and downloaded thereto to implement actual process control functionality.
- the process control configuration application may also allow a user to create or change user interfaces, which are used by user interface applications to display data to an operator and to enable the operator to change settings, such as set points, within the process control routine.
- the user interface applications which may be run on one or more operator workstations, receive data from the controller applications via the data highway and display this data to configuration engineers, process control operators, maintenance personnel, plant managers or supervisors, etc. using the user interfaces, and may provide any of a number of different views such as an engineering view, an operator's view, a maintenance view, a management view, etc.
- User interface applications are typically implemented on a system-wide basis in one or more ofthe operator workstations, and provide preconfigured displays to the operator or maintenance personnel regarding the operating state ofthe process plant, or the devices within the process plant.
- these displays take the form of alarming displays that receive alarms generated by the process controllers or other devices withiri the process plant, control displays indicating the operating state ofthe process controllers and other devices within the process plant, maintenance displays indicating the operating state ofthe devices within the process plant, etc.
- the AMS application may be used to communicate with a field device to change parameters within the field device, to cause the field device to run applications on itself such as, for example, self-calibration routines or self-diagnostic routines, to obtain information about the status or health ofthe field device, etc.
- This information may include, for example, status information (e.g., whether an alarm or other similar event has occurred), device configuration information (e.g., the manner in which the field device is currently or may be configured and the type of measuring units used by the field device), device parameters (e.g., the field device range values and other parameters), etc.
- This information may be stored within the field device or within a field device database associated with the field device, and may be used by a maintenance person to monitor, maintain, and/or diagnose these field devices.
- process plants include equipment momtoring and diagnostic applications such as, for example, RBMware provided by CSI Systems, or any other known applications used to monitor, diagnose, and optimize the operating state of various rotating equipment. Maintenance personnel usually use these applications, to maintain and oversee the performance of rotating equipment in the plant, to determine problems with the rotating equipment, and to determine when and if the rotating equipment must be repaired or replaced.
- process plants include power control and diagnostic applications such as those provided by, for example, Liebert and ASCO companies, to control and maintain the power generation and distribution equipment.
- an expert system or application such as, for example, the OZ expert system currently provided by NEXUS, or any other type of expert system including, for example, any type of data mining system that uses process control variables and limited information about the operating condition ofthe process control routines, or function blocks or modules associated with the process control routines, to detect poorly operating loops and to provide information to an operator about suggested courses of action to correct the problem.
- control optimizer applications such as, for example, real-time optimizers (RTO+), within a process plant to optimize the control activities ofthe process plant.
- Such optimizer applications typically use complex algorithms and/or models ofthe process plant to predict how inputs may be changed to optimize operation ofthe process plant with respect to some desired optimization variable such as, for example, profit.
- many process plants have other computers associated therewith that execute applications related to business functions such as applications associated with ordering raw materials, and replacement parts or devices for the process plant, as well as applications related to forecasting sales and production needs.
- the various applications used in the same process plant are set up to be used by and configured by different people associated with the process plant.
- configuration activities for each of these applications include providing information as to the types, locations, names, etc. ofthe devices disposed within the process plant as well as the manner in which the devices are communicatively interconnected to enable the applications to access information from or about those devices for use in control, maintenance and optimizer activities. Because these applications are run separately, by different people, the same configuration information is typically entered separately into the various applications at different times, resulting in the repetition of configuration activities.
- the process control configuration application and maintenance application typically used in the process plant are different, stand-alone programs in which a user must configure and view process set-up and other information using a process control configuration application running on a workstation.
- a user may switch, to a separate application (or even a separate workstation) to configure a maintenance application (entering the same or similar information or data already provided to configure the process control configuration application) to view field device specific information.
- the configuration information may also be separately provided to an optimizer application, a business application, etc.
- An integrated configuration viewing system for use in a process plant includes a computer readable memory and a plurality of template configuration objects stored on the computer readable memory.
- Each ofthe plurality of template configuration objects includes a graphical representation of a physical entity within the process plant, a parameter storage adapted fo communicate with the process plant to obtain and store device parameter information associated with the physical entity within the process plant, and a configuration storage adapted to store configuration parameters associated with the physical entity within the process plant.
- a first routine is stored on the computer readable memory and adapted to be executed on the processor to present a library section on a user interface.
- the library section is adapted to present depictions ofthe plurality of template configuration objects to a user via the user interface.
- a second routine is stored on the computer readable memory and adapted to be executed on the processor to present a configuration area on the user interface.
- a third routine is stored on the computer readable memory and adapted to be executed on the processor to enable a user to select one ofthe plurality of template configuration objects from the library section and to place the selected template configuration object within the configuration area to create a process configuration module within the configuration area.
- Fig. 1 is an exemplary block diagram of a distributed process control network located within a process plant including an operator workstation that executes an integrated process plant configuration system using configuration objects to form process configuration modules, which provide enhanced control, display, and simulation functions within the process plant;
- Fig. 2 is a logical block diagram of a configuration application and other entities, including configuration objects and process configuration modules, stored in the operator workstation of Fig. 1;
- Fig. 3 is a simplified depiction of a configuration screen that may be used by a configuration engineer to create a process configuration module using configuration objects stored in an object library;
- FIG. 4 is a simplified depiction of a configuration screen illustrating a process configuration module that includes several unit objects interconnected together;
- Fig. 5 is a simplified depiction of a configuration screen that illustrates an area bject that may be stored in the object library
- Fig. 6 is a simplified depiction of a screen display of a portion of a process plant that may be generated by the process configuration modules using the configuration objects;
- Fig. 7 is an exemplary block diagram ofthe integrated configuration system, which includes the process configuration modules and a plurality of applications that access data from and provide data to the process configuration modules;
- Fig. 8 illustrates a screen display of a control operator's view of particular entities associated with the process plant
- Fig. 9 illustrates a screen display of a maintenance operator's view of particular entities associated with the process plant.
- Fig. 10 illustrates a screen display of a plant manager's view of particular entities associated with the process plant.
- an example process plant 10 includes an integrated configuration viewing system that uses configuration objects to form process configuration modules 39 to provide enhanced control, display, and simulation functions within the plant environment.
- the process plant 10 includes a distributed process control system having one or more process controllers 12, which may be a pair of redundant controllers.
- Each process controller 12 is connected to one or more field devices 14 and 16 via input/output (I/O) cards or devices 18 and 19, which may be any types of I/O devices conforming to any desired communication or controller protocol.
- the field devices 14 and 16 may be any types of field devices such as, for example, sensors, valves, transmitters, positioners, etc., and may conform to any desired open, proprietary or other communication or programming protocol.
- the process plant 10 also includes one or more user interfaces or computers 20 and 22 (which may be any types of personal computers, workstations, etc.) that are accessible by plant personnel such as configuration engineers, process control operators, maintenance personnel, plant managers or supervisors, etc.
- the workstations 20 and 22 are coupled to the process controllers 12 via a communication line or bus 24 which may be implemented using any desired hardwired or wireless communication structure, and using any desired or suitable communication protocol such as, for example, an Ethernet protocol.
- the process controllers 12, the I/O devices 18 and 19, and the field devices 14 and 16 generally make up a process control system.
- a database 28 may be connected to the communication bus 24 and operates as a data historian that collects and stores configuration information as well as online process parameter, status, and other data associated with the process controllers 12 and field devices 14 and 16 within the process plant 10.
- the database 28 may operate as a configuration database to store the current configuration, including process configuration modules as described below, as well as control configuration information for the process control system within the plant 10 as downloaded to and stored within the process controllers 12 and the field devices 14 and 16.
- the process controllers 12, I/O devices 18 and 19, and field devices 14 and 16 are typically located down within and distributed throughout the sometimes harsh plant environment, the workstations 20 and 22, and the database 28 are usually located in control rooms or other less harsh environments easily accessible by operators, maintenance personnel, etc.
- control modules may each be made up of what are commonly referred to as function blocks, wherein each function block is a part or a subroutine of an overall control routine and operates in conjunction with other function blocks (via communications called links) to implement process control loops within the process plant 10.
- function blocks which may be objects in an object-oriented programming protocol, typically perform one of an input function, such as that associated I with a transmitter, a sensor or other process parameter measurement device, a control function, such as that associated with a control routine that performs PID, fuzzy logic, etc. control, or an output function, which controls the operation of some device, such as a valve, to perform some physical function within the process plant 10.
- an input function such as that associated I with a transmitter
- a sensor or other process parameter measurement device such as that associated with a control routine that performs PID, fuzzy logic, etc. control
- an output function which controls the operation of some device, such as a valve, to perform some physical function within the process plant 10.
- MPCs model predictive controllers
- optimizers etc.
- control modules 29 may be designed using any desired control programming scheme including, for example, sequential function blocks, ladder logic, etc., and are not limited to being designed using function blocks or any other particular programming technique.
- the field devices connected to the process controllers 12 may be conventional (i.e., non-smart) field devices 14 such as, for example, standard 4-20 mA devices that communicate over analog lines to the I/O device 18.
- the field devices may be smart field devices 16 having a processor and a memory such as, for example, HART ® , PROFIBUS ® , Ethernet, or Fieldbus field devices, which communicate over a digital bus to the I/O device 19 using Fieldbus protocol communications.
- Smart field devices 16 may store and execute modules, or sub-modules such as function blocks 30 associated with the control strategy implemented in the process controllers 12. Function blocks 30, which are illustrated in Fig.
- the Fieldbus field devices 16 may be executed in conjunction with the execution ofthe control modules 29 within the process controllers 12 to implement process control as is well known.
- the field devices 14 and 16 may be any types of devices, such as sensors, valves, transmitters, positioners, etc.
- the I/O devices 18 and 19 may be any types of I/O devices conforming to any desired communication or controller protocol such as HART ® , PROFIBUS ® , Fieldbus, etc. ⁇
- the process plant 10 also includes various rotating equipment 21 such as, for example, turbines, motors, etc. connected to the communication bus 24.
- power generating and distribution equipment 25 associated with the process plant 10 may also be connected to the communication bus 24.
- any other equipment and process control devices may be attached to or be part ofthe process plant 10, and the system described herein is not limited to the equipment specifically illustrated in Fig. 1, but may, instead or in addition, include any other types of process control equipment or devices.
- the workstation 20 includes a plurality of applications and other data structures 32, which may be accessed by any authorized user such as, for example, a configuration engineer, a process operator, a maintenance person, a plant manager or supervisor, etc. to view and provide functionality with respect to devices, units, equipment, etc. located within the process plant 10.
- the plurality of applications 32 is stored in a computer readable memory 34 ofthe workstation 20, and each ofthe applications or entities within the plurality of applications 32 is adapted to be executed on a processor 36 associated with the workstation 20.
- the workstation 20 may further include user interface routines or applications 35 that receive and display information pertaining to the process plant 10 (or entities within or associated with the process plant 10) on a display screen 37 or display device associated with the workstation 20 such as, for example, a handheld device, laptop, other workstation, printer, etc.
- the user interface applications 35 may generate one or more user displays, such as, for example, operator, maintenance and manager displays that enable a user to view and/or retrieve relevant information about different portions ofthe process plant, and that enable a user to graphically browse or navigate to different portions of the propess plant in a desired manner based on depictions or displays of process control areas, units, loops, devices, etc. within the process plant 10.
- user displays such as, for example, operator, maintenance and manager displays that enable a user to view and/or retrieve relevant information about different portions ofthe process plant, and that enable a user to graphically browse or navigate to different portions of the propess plant in a desired manner based on depictions or displays of process control areas, units, loops, devices, etc. within the process plant 10.
- the plurality of applications 32 may be used in conjunction with and configured using a set of process configuration modules 39, which may provide a simulation of an operation associated with a portion of a process plant 10.
- the process configuration modules 39 have graphics associated therewith to create process graphic displays, which generally provide a display pertaining to a portion ofthe process plant 10.
- the process graphic display elements which will be described in more detail below, are generally elements that are used by an operator's display, an engineer's display, a maintenance person's display, a plant manager's or supervisor's display, or other displays to provide information to I a user, such as an operator, about the operation, configuration, or set-up ofthe process plant 10 and the elements therein.
- An example of a process configuration module 39 is disclosed in U.S. Patent Application Ser. No. 10/278,469 entitled "Smart Process Modules and Objects in Process Plants” (filed Oct. 22, 2002), which is hereby expressly incorporated by reference herein.
- the process configuration modules 39 may be used to simulate the operation of the process plant 10, or of some ofthe different elements therein connected in the manner depicted in the process graphic displays and, additionally, may be used to provide views to different users, such as operators, maintenance persons, business persons, etc. The views provide various information to these users including information generated by the applications 32.
- the process configuration modules 39 are illustrated as being stored in and executed by the workstation 20, the process configuration modules 39 maybe downloaded to and executed in any other computer associated with the process plant 10 such as, for example, workstation 22, a laptop, a handheld device, etc.
- Fig. 2 illustrates some ofthe applications and data structures or other entities within the plurality of applications 32 stored in the computer readable memory 35 ofthe workstation 20.
- a configuration application 38 may be used by, for example, a configuration engineer to create process configuration modules 39. (also called process flow modules) and the associated graphic displays. More particularly, the configuration application 38 may create process configuration modules 39 using one or more configuration objects 42, the I nature of which will be described in more detail below. Furthermore, while one configuration application 38 may create the process configuration modules 39, these process configuration modules 39 may be created by separate configuration applications. Still further, different ones ofthe plurality of applications 32 may be located in different geographical locations from each other and/or the process plant 10 and may be adapted to communicate via any suitable communication network such as, for example, the Internet, or other open network.
- any suitable communication network such as, for example, the Internet, or other open network.
- a plurality of configuration objects 42 may be stored on the computer readable memory 34 in a library 40 of predefined, example or template configuration objects 42.
- the library 40 may be accessed, copied, and used by the configuration application 38 to create one or more process configuration modules 39.
- Each process configuration module 39 is made up of or created from one or more configuration objects 42 and may include any number of objects connected together.
- each configuration object 42 may include one or more process flow or simulation algorithms 45, which are stored in a process configuration module memory 46.
- the configuration application 38 may be used to create one or more graphic displays 41 , each of which is made up of or created from one or more configuration objects, and may include any number of display elements connected together.
- One ofthe graphic displays 41 is illustrated in Fig. 2 in expanded form, and includes a depiction of a set of process elements such as, for example, valves, tanks, sensors, and flow transmitters, interconnected by connection elements, which may be, for example, pipes, conduits, electrical cables, conveyors, etc.
- An execution engine 48 executes or implements each ofthe process configuration modules 39 during runtime to create one or more process displays for an operator as defined by the graphic displays 41, and to implement simulation functionality associated with the process configuration modules 39.
- the execution engine 48 may use a rules database 50 defining the logic to be implemented on the process configuration modules 39 as a whole, and the configuration objects 42 within those modules' 39 in particular.
- the execution engine 48 may also use a connection matrix 52, which defines the connections between the process elements within the process plant 10 as well as within the process configuration modules 39 to implement the functionality for the process configuration modules 39.
- Fig. 2 illustrates one ofthe configuration objects 42e in more detail. While the configuration object 42e is illustrated as being one ofthe template configuration objects, it should be understood that other configuration objects will generally include the same or similar elements, features, parameters, etc!' as described with respect to the configuration object 42e. In addition, it should be understood that the specifics or values of these elements, features and parameters may be changed or varied from configuration object 42 to configuration object 42 depending on the nature and use of that configuration object 42. Furthermore, while the configuration object 42e may be an object within an object-oriented programming environment and thus include data stores, inputs and outputs, and methods associated therewith, this configuration object 42e may be created by and implemented within any other desired programming paradigm or protocol.
- the configuration object 42e before being instantiated, is an object that is associated with a particular entity such as a physical or a logical entity within the process plant 10 of Fig. 1. However, after being copied and instantiated, the configuration object 42e may be tied to a particular entity within the process plant 10 so as to simulate the operation of that particular entity. In any event, the configuration object 42e includes a data store 53 that is used to communicate with the entity within the process plant 10 to which the configuration object 42e pertains and store device parameter information or data received from or pertaining to the entity with which the configuration object 42e is associated.
- the data store 53 generally includes a data store 53a that stores general of permanent information about the entity to which the configuration object 42e pertains, like manufacturer, revision, name, type, etc.
- a data store 53b may store variable or changing data, such as parameter data, status data, input and output data, cost or other data about the entity to which the configuration object 42e pertains, including configuration parameters associated with the entity, as well as data associated with the entity as it has existed in the past or as it now exists within the process plant 10.
- the configuration object 42e may be configured or programmed to receive this data (e.g., cost data) on a periodic or non- periodic basis, from the entity itself via any desired communication link, from the historian 28 via the communication bus 24, or in any other desired manner.
- a data store 53c may store a graphical representation ofthe entity within the process plant 10 to which the configuration object 42e pertains, and which is used to produce the graphic displays 41 to the operator via an operator interface, such as the display screen 37 associated with the workstation 20 of Fig. 1.
- the graphical representation may include place holders (marked by underlines within the data store 53c) for information about the entity such as information defined by the parameter or other variable data about the entity as stored in the data store 53b. This parameter data may be displayed in the graphical place holders when the graphical representation is presented to the operator on the display device 37 as part ofthe graphic displays 41.
- the graphical representation (and the configuration object 42e) may also include predefined connection points (marked by an "X" in the data store 53c) that enable a configuration engineer or operator to attach upstream or downstream components to the process element, as depicted by the graphical representation.
- these connection points also enable the configuration object 42e to be aware ofthe elements connected to that configuration object as configured within a process configuration module 39 and may specify a type of connection element that may be used such as, for example, a pipe, a duct, a stream associated with that element, etc.
- the configuration object 42e may also include one or more inputs 54 and outputs 56 to enable communication with other configuration objects within or outside of a process configuration module 39 in which the configuration. object 42e is used.
- connections ofthe inputs 54 and outputs 56 to other configuration objects 42 may be configured by a configuration engineer during configuration ofthe process plant 10 by simply connecting other configuration objects 42 to these inputs 54 and outputs 56, or by specifying particular communications that are to take place between configuration objects 42.
- Some of these inputs 54 and outputs 56 may be defined as being connected to the I configuration objects connected at the predefined connection points for the configuration object as discussed above. These inputs 54 and outputs 56 may also be determined or defined by a set of rules within the rules database 50 and the connection matrix 52 defining the connections between different devices or entities within the process plant 10.
- the inputs 54 and the outputs 56 which include data stores or buffers associated therewith will. generally be used to provide communications of data from other configuration objects to the configuration object 42e, or to provide communications of data stored within or generated by the configuration object 42e to other configuration objects.
- These inputs 54 and outputs 56 may also be used to provide communications between the configuration object 42e and other objects within the process control system such as, for example, control modules 29 located within the process controllers 12, smart field devices 16, etc.
- the configuration object 42e also includes a method storage 58 that is used to store zero, one or more methods 60 (illustrated as methods 60a, 60b and 60c in Fig. 2) to be implemented by the configuration object 42e during execution of a process configuration module 39 by the execution engine 48.
- the methods 60 stored in the method storage 58 will use the data stored within the data storage portions 53a and 53b and data obtained from other configuration objects or even data from other sources such as, for example, the configuration database or historian 28, via the inputs 54 and the outputs 56 to determine information about the process plant 10 or an entity within the process plant 10.
- the methods 60 may determine poor or bad operating conditions associated with the entity defined by the configuration object 42e, errors associated with that or other entities within the process plant 10, etc.
- the methods 60 may be preconfigured or provided based on the type or class of configuration object and will generally be executed each time the configuration object 42e is executed within the execution engine 48 during runtime.
- Some example methods 60 that may be provided within a configuration object such as, for example, the configuration object 42e, include detecting leaks, dead band, dead time, movement, variability, condition monitoring, computing costs, or other conditions associated with the entity.
- the methods 60 may also be provided to help simulate the operation ofthe process entity associated with the configuration object or the material flowing through that process entity.
- 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 process plant 10 to simulate operation ofthe element and calculate expected outputs based on provided inputs, etc.
- these are , but a few ofthe methods 60 that may be stored 1 in and run by a configuration 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 10 as well as other factors.
- the configuration object 42e may store and execute methods 60 that detect system-level conditions, errors, etc.
- these methods 60 may also be used to determine other information about devices, logical elements such as, for example, process configuration modules 39 and loops, and other non-system-level entities.
- the methods 60 may be programmed or provided in any desired programming language or infrastructure, such as C, C++, C#, XML, XSL, .NET, etc., or may be referenced to or may define applicable rules within the rules database 50 that should be run for the configuration object 42e during execution.
- a user or configuration engineer may run or execute the configuration application 38 to define the component devices, interconnections, and interrelationships within the process control environment by creating one or more process configuration modules 39 (using the configuration objects 42), which model the arrangement of physical entities and logical entities within the process plant 10.
- the configuration display 64 includes a library or template section 65 (which includes the library 40 of Fig. 2) and a configuration section 66.
- the configuration application 38 may include a routine stored on the computer readable memory 35 and adapted to be executed on the processor 36 to present the ' library or template section 65 (which includes the library 40 of Fig. 2) on the user interface or workstation 20.
- the configuration application 38 may include a routine stored on the computer readable memory 35 and adapted to be executed on the processor 36 to present a configuration display or area 64 on the 1 user interface or workstation 20, such as that illustrated in Fig. 3, to the configuration engineer (or other user).
- the library or template section 65 is adapted to present a graphical depiction of sets of template configuration objects 67, which may include the configuration objects 42 of Fig. 2, to a user via the user interface or workstation 20.
- the template configuration object 67 may be associated with any desired process entity such as, for example, a device object 67a representative of a device within the process plant 10, a connection object 67b representative of a connector element within the process plant 10, a unit object 67c representative of a unit within the process plant 10, and an area object 67d representative of an area ofthe process plant 10.
- Device objects 67a may be associated with physical devices within the plant 10 that perform some function with respect to a stream of material such as, for example, valves, sensors, transmitters, pumps, eductors, dampers, feeders, etc.
- Connection objects 67b define the manner in which materials within the process plant 10 such as, for example, solid materials, liquid, vapor, electricity, and gases are delivered or carried from one device to another. More particularly, connection objects 67b may include pipes, ducts, conduits, conveyors, electrical cables, or any other device or entity that moves material from one point to another point within the process. Pipes are generally used to illustrate (and simulate) liquid and high pressure vapor or gas flow within the plant 10.
- connection objects 67b are generally used to illustrate (and simulate) low pressure gas flow within the plant 10. Conveyors are generally used to illustrate (and simulate) the movement of solid material between processing units. And electrical cables are used to illustrate (and simulate) power flow in electro-chemical processes, etc Arrows may be displayed with these connection objects 67b to show the direction ofthe material flow.
- Each connection object 67b defines the type of connection that is used to provide material at the input or output of a device. In other words, a connection object 67b may begin at a device object 67a output or a unit object 67c output, and may terminate at a device object 67a input or a unit object 67c input. In addition, if an upstream output is common to two connections, a "T" element may be included in the connection object 67b. Similarly, "T" elements may be used to combine multiple outputs.
- a particular type of device object 67a may only be used with a specific type of connection object 67b.
- a pipe may be used with only a valve, pump, eductor, or feeder.
- a duct object may be set up to be used with a draft fan or damper drive or other device that provides flow of gas.
- a conveyor may be used, with only a feeder and a motor drive to simulate and depict the flow of solid materials.
- Unit objects 67c may include a logical grouping of device objects 67a and connection objects 67b interconnected together, as well as other plant equipment that process or perform a function on the materials or streams in the plant 10 in some manner. Generally, all inputs and outputs to and from unit objects 67c may be made through connection objects 67b. Standard unit objects 67c include tanks (vertical and horizontal), mixers, reactors, air heaters, heat exchangers, compressors, turbines, distillation columns, evaporators, separators, boilers, or any other elements that perform some type of simple or standard processing activity, as well as the various device objects 67a and connection objects 67b associated with these units.
- area objects 67d may include a logical grouping of unit objects 67c, device objects 67a and connection objects 67b interconnected together, as well as other plant equipment that process or perform a function on the materials or streams in the plant 10 in some manner.
- the template configuration objects 67 are generic objects that may be provided from the system manufacturer to the user and that may be selected, dragged, and dropped onto the configuration section 66 to create an instance of a configuration object within a process configuration module 39. More particularly, to create a process configuration module 39, the configuration application 38 may include a routine stored on the computer readable memory 35 and adapted to be executed on the processor 36 that enables the configuration engineer (or some other user) to create the process configuration module 39 by selecting one ofthe template configuration objects 67 from the library or template section 65, dragging the selected template configuration object 67 to a desired location within the I configuration section 66, and dropping or placing the selected template configuration object 67 within the desired location on the configuration section 66.
- the configuration engineer "selects" particular template configuration objects 67 in any conventional windowing manner such as, for example, by double-clicking on a template configuration object 67 with a mouse, by tapping or touching a particular template configuration object 67 on a touch-sensitive screen, or by entering a command on a keyboard.
- the routine may enable the configuration engineer (or some other user) to store the configuration parameters ofthe selected template configuration object within the data store 53 to create the process configuration module 39.
- the routine may further enable the configuration engineer (or some other user) to store data indicative of a communication attribute associated with the physical entity.
- the communication attribute may include a communication protocol, a communication connection type, a number of communication inputs/outputs, and/or a type of communication connection input/output.
- the device objects 67 may be used to create higher-level configuration objects such as, for example, custom unit objects.
- template unit objects may be used to create even higher-level objects such as, for example, custom area objects, etc., for each level ofthe equipment and logical hierarchy of a process control system. All ofthe custom or user- defined higher-level configuration objects may be stored in the library 40 along with the predefined template configuration objects 42 and later reused or used as a starting point for the creation of other custom configuration objects, including other unit and area configuration objects.
- Fig. 3 illustrates an example of a process configuration module 39 for a flow loop that may be created using the template configuration objects 67 and the configuration application 38 described above.
- the configuration engineer may create the process configuration module 39 by selecting, dragging, and dropping template device objects 67a, e.g., a valve 102 and a transmitter 104, onto the configuration section 66 in a desired location.
- the configuration engineer may interconnect the valve 102 and transmitter 104 by selecting, dragging, and dropping a template connection object 67b, e.g., a pipe 106, between the valve 102 and the transmitter 104.
- a template connection object 67b e.g., a pipe 106
- a connection object may be created by holding the left mouse button down over an object output (such as, for example, a device object output or a unit object output) and, while holding down a button on the mouse, positioning the cursor over an object input (such as, for example, a device object input or a unit object input).
- object output such as, for example, a device object output or a unit object output
- object input such as, for example, a device object input or a unit object input.
- the configuration application 38 allows a configuration engineer to specify the attributes or properties associated with each process configuration module 39 (and the configuration objects 42 within the process configuration modules 39) using, for example, a pull-up menu, a pull-down menu, a pictographic menu, a dialog box, a pop-up menu, etc. associated with the configuration display 64. More particularly, each process configuration module 39 (and the configuration objects 42 within the process configuration module 39) may include physical or engineering attributes, control attributes, maintenance attributes, and management attributes.
- a configuration engineer may completely define the attributes, methods, etc. for each process configuration module 39 of the process control system, and store the configuration information or parameters (e.g., the physical or engineering attributes, the communication attributes, the control attributes, the maintenance attributes, the process management information or business attributes, one or more display formats for displaying the device parameter information, etc.) in the data store 53 .
- the configuration information or parameters e.g., the physical or engineering attributes, the communication attributes, the control attributes, the maintenance attributes, the process management information or business attributes, one or more display formats for displaying the device parameter information, etc.
- Physical or engineering attributes may include a, type, a size, a flow capacity, a volume,' a surface area, a number of process input/output connections, a type of process input/output connections, a timing parameter, etc. associated with the actual physical object I
- valve object (such as a device, a unit, an area, etc.) being modeled by the process configuration module 39.
- physical or engineering attributes associated with a valve object may include the valve type (e.g., linear, quick opening, equal percentage, etc.), the valve size, the stroke time from open to close, the valve manufacturer and part number, the type of material flowing through the valve, and an indication of one or more engineering applications or tools that may access and use the device parameter information and/or configuration parameters to perform a data processing function with respect to the physical entity associated with the process configuration module and to produce process information related to the physical I entity.
- Control attributes may include a control strategy or routine, (including the function blocks that make up the control strategy), a type of control strategy or routine used to control the physical entity, values for one or more control parameters associated with control ofthe physical entity, references to the electrical inputs and outputs ofthe function blocks associated with the control strategy, setpoints, the initial values ofthe attributes, the default values (if appropriate) ofthe attributes, the range, i.e., high and low values, ofthe attributes, measurement units, limits, dead band, etc.
- the plurality of template configuration objects 67 may also include a simulation algorithm adapted to simulate operation of any entity within the process plant 10.
- a configuration engineer might create a control strategy for a tank unit object in which a fluid level in a tank is read by a level sensor, and compared with a predetermined desired level.
- the control strategy may then open or close a feed valve based on whether the fluid level is lower or higher than the predetermined desired level.
- the simulation algorithm may simulate the fluid level o the tank unit object, as read by the level sensor, and display an indication ofthe sensed fluid level on the display device 37.
- Control attributes associated with a valve object may include the control strategy such as, for example, the function blocks, that are used to define and access a particular function to control the valve.
- a configuration engineer may associate the electrical inputs and outputs ofthe function blocks (i.e., Al, AO, Dl, DO, etc.) with electrical signals or values produced or generated by various configuration objects (e.g., device objects 67a or unit objects 67b) that make up the process configuration module 39.
- the configuration application 38 relates each ofthe functions defined by the function blocks according to the interconnections ofthe objects within the process configuration module 39 specified by the configuration engineer.
- each ofthe control function blocks incl ⁇ des an algorithm for performing a particular function and fixed parameters upon which the algorithm may operate to use the electrical inputs and outputs to provide the desired process control function.
- a configuration engineer may specify the parameters such as, for example, the setpoint, mode, status, etc. ofthe associated function block controlling that valve when setting or configuring a valve object, either by itself or as part of a higher-level process configuration module, such as a unit object, an area object, etc.
- control attributes that may be associated with or specified for the process configuration module 39 by a configuration engineer include an indication of one or more control diagnostic applications or tools (e.g., DeltaN Inspect, RTO+, process control applications, control optimizer applications, process optimizer applications, modeling tools, expert applications, tuning routines, etc.) that may access and use the device parameter information and/or configuration parameters associated with the process configuration module to perform diagnostics with respect to controlling the physical entity and to produce process information related to the physical entity.
- control diagnostic applications or tools e.g., DeltaN Inspect, RTO+, process control applications, control optimizer applications, process optimizer applications, modeling tools, expert applications, tuning routines, etc.
- control attributes may further include an indication of one or more alarm applications related to alarms and how alarms generated by the process configuration module 39 (and configuration objects within the process configuration module 39) are managed.
- one or more alarm applications may be related to specifying the criticality of alarms.
- Control attributes may further include trending applications associated with the process configuration module 39 (and the configuration objects 42 within the process configuration module 39). Examples of applications or systems related to alarms are disclosed in U.S. Patent No. 5,768,119 entitled “Process Control System Including Alarm Priority Adjustment” (filed Apr. 12, 1996), U.S. Patent Pub. No. 2002/0055790 entitled "Enhanced Device Alarms in a Process Control System” (filed Apr. 19, 2001), U.S. Patent Pub. No.
- Maintenance attributes may include information associated with operation ofthe physical entity that may be used by maintenance persons such as, for example, alarm configuration information (e.g., how alarms are to be setup, displayed and treated), device health information (e.g., the manner of displaying device health information), maintenance diagnostics information, an indication of one or more maintenance applications (e.g., device diagnostics applications, equipment maintenance applications and root cause applications) that may access and use the device parameter information and/or configuration parameters to perform maintenance-related data processing function with respect to the physical entity associated with the process configuration module arid to produce process information related to the physical entity.
- maintenance attributes may include an indication of and ' configurations for any other maintenance-related data to provide access to such data and the manner of processing or viewing such data.
- business or process management attributes may include an indication of one or more applications that may access and use the device parameter information and/or configuration parameters associated with the process configuration module to perform an appropriate data processing function (e.g., creating graphs), as well as to produce and provide process information that a manager needs to make decisions about what to produce, whether the plant is operating satisfactorily, etc.
- an appropriate data processing function e.g., creating graphs
- the process configuration module 39 may include simulation algorithms that calculate parameters associated with a device such as, for example, the discharge pressure, mass flow, liquid temperature, liquid composition, inlet pressure, outlet pressure, etc. of a valve.
- parameters associated with a device such as, for example, the discharge pressure, mass flow, liquid temperature, liquid composition, inlet pressure, outlet pressure, etc. of a valve.
- the simulation algorithms available to simulate the operation of a valve or the material flowing through the valve may be dependent upon the type of valve and sizing information, which were provided as engineering attributes. As discussed in further detail below, these simulated or calculated parameters may be exposed in a process operator's view, if so desired.
- a configuration engineer may also specify maintenance attributes associated with the valve object such as, for example, an indication of one or more applications (e.g., the AMS application, data analysis and diagnostic tools, control diagnostic applications, device diagnostic applications, index generation applications, performance tracking tools, root cause applications, plugged line detection applications, device status applications, equipment monitoring applications, power management and power equipment monitoring and analysis tools, etc. ) that may access and use the device parameter information and/or configuration I parameters associated with the process configuration module to perform a data processing function with respect to the physical entity associated with the process configuration module and to produce process information related to the physical entity. Examples of applications or systems that are related to maintenance and/or diagnostics are disclosed in U.S. Patent Np.
- a configuration engineer may specify the business or process management attributes associated with the process configuration module 39 such as, for example, a product type, a throughput, an efficiency, an uptime, a downtime, a yield, an indication of one or more applications (e.g., RTO+, enterprise resource planning applications, materials resource planning applications, plant management applications, process management applications, index generation applications, work order generation applications, etc.) that may access and use the device parameter information and/or configuration parameters associated with the process configuration module 39 to perform a data processing function with respect to the physical entity and to produce process information related to the physical entity. Examples of applications or systems that are related to business or management functions are disclosed in U.S. Patent Pub. No.
- the configuration engineer may store a process configuration module 39 in the configuration object library 40 as a custom or user-defined device object 67a to create a device process module representative of a field device within the process plant 10.
- the configuration engineer may store a process configuration module 39 in the configuration object library 40 as a unit object 67c such as, for example, a flow loop unit I object 100 (illustrated in Fig. 3) to create a unit process module representative of a unit within the process plant 10. Still further, the configuration engineer may store a process configuration module 39 in the configuration object library 40 as a custom or user-defined area object 67d to create an area process module representative of an area within the process plant 10. Each ofthe custom or user-defined device, unit and area objects 67a, 67c and 67d may include their own data store 53, inputs 54, outputs 56 and methods 60 associated therewith. In this manner, the configuration engineer may access and reuse the flow loop unit object 100, for example, when configuring or creating other higher-level process configuration modules 39.
- Fig. 4 illustrates a manner in which different unit objects 100,
- the unit object 120 is made by connecting the flow loop unit object 100 of Fig. 3, as well as other unit objects 110, 112, 114, and 116, which may be either predefined, template unit objects 67c (such as, for example, the template heat exchanger unit object 110) or custom, user-defined unit objects.
- a configuration engineer may connect the outputs ofthe input flow loop unit objects 112 and 114 to inputs ofthe heat exchanger device object 110 using any desired drag-and-drop technique, any pull-down menus, etc. Similarly, the configuration engineer may connect the outputs ofthe heat exchanger device object 110 to the inputs ofthe output flow loop unit objects 100 and 116 in any desired manner. The configuration engineer may then store the created configuration object 120 in the configuration object library 40 as either a unit object (such as a heat exchanger unit object) or as part of an area object.
- Fig. 5 illustrates an example ofthe unit object 120 that may be created and stored in the library 40, using the display routine of Fig. 4 so that it may be accessed and used by the configuration engineer.
- the created unit object 120 incl ⁇ des its own data store 53, inputs 54, outputs 56, and methods 60.
- the unit object 120 contains all ofthe attributes (e.g., engineering attributes, control attributes, maintenance attributes, management attributes, etc.) specified for the process configuration modules 39 ofthe lower- level device or unit objects, the configuration engineer does not need to specify the attributes associated with the unit objects (and device objects that make up the unit object).
- the unit object 120 may automatically include and have access to all ofthe attributes stored for each of those objects, which the unit object 120 contains.
- additional attributes including control, maintenance, management, etc. attributes maybe specified for the unit object 120 as a whole.
- Fig. 6 illustrates an example screen display 130 for an area object that may be created using lower-level process configuration modules 39 and the configuration application 38 discussed above.
- the interconnected entities on the screen display 130 maybe configured by a configuration engineer using the configuration application 38 described above, and may be displayed on the display device 37 by the execution engine 48 during runtime of a process configuration module 39.
- each ofthe entities such as, for example, the tanks, flow transmitters, valves, etc., as well as the connectors therebetween, depicted on the screen 130 may be generated by or associated with configuration objects 42 within a process configuration module 39 and the graphical representations associated with the configuration objects.
- any other process entities including hardware devices and software or logical elements such as control loops, control modules, function blocks, etc. may be depicted within the screen display 130 in any desired configuration.
- the engine 48 During execution of a process configuration module 39 by the execution engine 48, the engine 48 implements the communications defined by the inputs 54 and outputs 56 to each ofthe configuration objects in the process configuration module 39, and may implement the methods 60 for each of those objects to perform the functionality provided by the methods 60.
- the functionality ofthe methods 60 may be located in programming within the configuration object, or defined by a set of rules within the rules database 50 that the engine 48 executes based on the type, class, identification, tag name, etc. of a configuration object to implement the functionality defined by those rules.
- an instance ofthe configuration object has a tag or unique name within the context ofthe process configuration module 39 with which the configuration object is associated. This tag or unique name may be used to provide communications to and from the configuration object, and may be referenced by the execution engine 48 during runtime.
- Process configuration module tags may be unique within the process control system configuration. This tagging convention enables elements within the process configuration modules 39 to be referenced by elements within others ofthe process configuration modules 39.
- the parameters ofthe configuration object may be simple parameters such as simple values, structured parameters, or parameters that know the expected units and attributes associated therewith. Smart parameters may be interpreted and used by the process rules engine or execution engine 48 to assure that all signals are being sent in the same units, or are converted properly. Smart rules may also be used to turn on and turn off groups of alarms for the configuration objects (or process configuration modules 39) to create a smart alarm strategy and/or interface for the operator. Still further, configuration object classes may be associated with equipment and module classes within the process control strategy of the plant 10 to provide a known linkage between a configuration object and the process variables it will need to interpret or access.
- Configuration objects when used in process configuration modules 39, may also include mode of operation, status, and alarm behavior so that these configuration objects may i be put in different modes during runtime such as, for example, 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, for example, a parameter out of range, limited, high variability, etc.
- Configuration 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, configuration objects may use information from other elements such as, for example, process configuration modules 39 and other objects to enable the configuration object to recognize when its associated entity is busy or, for example, acquired by a batch control process within the process plant 10. ,
- Configuration objects that are associated with connectors 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 such as turbulent or nonturbulent, 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 ofthe source and destination object to which the smart link connects, match and, if not, may perform a conversion.
- the methods ofthe smart link may also model the flow through the connector using a model or an algorithm to estimate the speed or nature ofthe flow through the actual connectors, length and size ofthe physical connections, transport delay, etc.
- the stored parameters for the configuration object (such as friction parameters) may be used in these methods.
- the smart links or connection objects enable configuration objects to be aware ofthe other upstream and downstream objects or entities.
- 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 ofthe entities, which other entities are upstream and downstream ofthe entity for this configuration object, the direction of material, fluid, electric flow, etc. in any desired or convenient manner.
- connection matrix 52 may be created prior to execution of the process configuration modules 39, and may define for the smart links the interconnections between the different devices within the process plant 10 and, therefore, the interconnections between the different configuration objects.
- the execution engine 48 may use the matrix 52 to ascertain the upstream and downstream entities, and thereby define the communications between the configuration objects and the methods associated with the configuration objects.
- one or more set of rules may be provided to be used by the configuration objects to interact with each other, to obtain data from each other as needed for the methods within the configuration objects, and to resolve the impact of configuration objects associated with output connections.
- the configuration object 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) ofthe device to which the configuration object 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, etc.
- 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 ofthe system software such as, for example, maintenance requests, records of operational problems, etc.
- hot links may be user configurable or changeable to provide the ability to add knowledge links to objects in the 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 ofthe object.
- the execution engine 48 may include a routine stored on the computer readable memory 35 and adapted to be executed on the processor 36 that executes or implements each ofthe process configuration modules 39 during runtime to obtain device parameter information from the process plant 10 pertaining to the entity associated with the process configuration module 39 and to make the obtained device parameter information and the process information produced by the various applications available to the user via the user interfaces or workstations 20 and 22 in conjunction with the graphical representation ofthe entity. More specifically, the routine may display the device parameter information on the user interfaces or workstations 20 and 22 according to one or more display formats specified during configuration ofthe process plant 10.
- the device parameter information and the process information produced by the various applications may be made available to or presented on the user interfaces or workstations 20 and 22 by creating one or more process displays or views for a user as defined by the graphic displays 41 and the display format.
- the graphic displays 41 created by execution ofthe process configuration modules 39 are designed to dynamically show online measurements and actuators that interface with the process control system.
- unmeasured parameters, which reflect process operation may be calculated using online process simulation provided in the process configuration, modules 39 and may be shown as an integral part ofthe associated graphic displays.
- the user may, as part ofthe process configuration module 39 creation or configuration process, attach or provide process flow algorithms 45 to the process configuration module 39.
- process flow algorithms 45 may be preconfigured to calculate or determine certain process or system-level properties such as, for example, mass balance calculations, flow calculations, efficiency calculations, economic calculations, etc. with respect to the process depicted or modeled by the process configuration module 39.
- the process configuration modules 39 themselves may have mode, status, and alarm behavior, may be assigned to workstations, and may be downloaded. as part ofthe display downloads.
- the flow algorithms may be executed by a separate or different execution engine or by the execution engine 48 to perform mass or heat balancing, flow routing, flow efficiency, flow optimization, economic calculations related to flow, or other desired flow- • related calculations using the data provided in the process objects ofthe process flow module 39. Still further, these flow algorithms 45 may access parameters from the control strategy and may, conversely, provide data or information to the control strategy.
- process configuration modules'39 are constructed or built by building graphic displays 41 for these modules 39, and then by specifying flow algorithms 45 to be used in or associated with these process configuration modules 39.
- individual process configuration modules 39 may be spread across and executed by different computers, and process configuration modules 39 may be communicatively coupled to one another to operate in conjunction with each other, either on the same or on different computers.
- process configuration modules may be built up and interconnected as described above to create a model ofthe physical and logical layout ofthe process control system in a manner such that the configuration, control, and display activities may be integrated.
- process configuration modules may be used by different applications to obtain information from the process plant 10 and to create different views or display formats for use by different users to provide different types of information to those different users.
- process configuration modules once created for a process plant, may be accessed by any application to enable the application to obtain the device parameter information, configuration parameters, online data, etc. that the application needs to operate and to perform the various data processing functions (e.g., the maintenance, control, business, optimizer, etc. functions), as well as to produce process information.
- data processing functions e.g., the maintenance, control, business, optimizer, etc. functions
- process configuration modules are created for a process plant, additional, separate configuration activities need not generally be performed because all of the process plant supporting applications, such as business, maintenance, optimizer and control applications, may be communicatively coupled to the appropriate process configuration modules to obtain the information (e.g., configuration parameters and/or device parameter information) these applications need from the process plant.
- This information may be obtained from the appropriate process configuration modules because all ofthe process plant information flows through the process configuration modules.
- the process configuration modules (because they include the engineering, maintenance, control and management attributes) may include an indication of or use one or more supporting applications to create or enable a display or view to be created.
- the display or view created by the process configuration modules may provide different types of information to different users by using the device parameter information and/or the configuration parameters.
- Fig. 7 illustrates a manner in which supporting applications, including the plurality of applications 32, may access data from and provide data to the process configuration modules 39 as they are being executed on the execution engine 48.
- maintenance system applications 200, optimizer applications 202, expert system or predictive control applications 204, and equipment monitoring applications 206, as well as any desired business applications 208 are communicatively coupled to the process configuration modules 39 and may obtain any desired information from these process configuration modules 39 for any desired purposes.
- the applications 200-208 may communicate with the process configuration modules 39 (as they are being executed in the execution engine 48) using the tags associated with the process configuration modules 39.
- one ofthe applications 200-208 may obtain the information it needs from the process configuration modules 39 as already set up, instead of having to be configured separately to identify where the application needs to go (within the process plant 10) to access or obtain the information it needs.
- process configuration modules 39 are configured to include engineering, maintenance, control and management attributes, these process configuration modules 39 may automatically refer to specific ones ofthe applications 200- 208, or specific information provided by these applications 200-208 which are relevant to these different activities.
- the user interface routines 35 may create different user displays or views for different users (e.g., business persons, maintenance persons, control operators, etc.) automatically from the process configuration modules 39.
- the user interface routines 35 may use the graphic displays 41 associated with the process configuration modules 39, the attributes specified for the process configuration modules 39, and one or more display formats to enable users to view different types of information about any portion ofthe process plant 10.
- Figs. 8-10 illustrate different views for the unit object 120 illustrated in Figs. 4 and 5 that may be created by the user interface routines 35 using information provided by the process configuration module 39 for that unit object 120.
- a different graphical view may be provided for each ofthe process operators, maintenance persons, plant managers or supervisors, and the like to enable these different users to view a particular portion ofthe process plant 10 in terms relevant to their responsibilities.
- Fig. 8 illustrates an example of an operator's display for the unit object 120 of Figs. 4 and 5.
- a unit object 120 for the heat exchanger portion is depicted within the operator's display shown in Fig. 8, any other portion ofthe plant 10 such as, for example, a loop, device, area, etc. may be shown instead to achieve the same or similar results.
- the operator's display illustrates the basic graphic (established during the creation ofthe unit object 120) graphically depicting this unit as including two input flow control units (made up of valves, transmitters, etc.) and two output flow control units (made up of valves, transmitters, and other devices) connected to a heat exchanger.
- control-related information 300 may be needed by the control operator to understand what is happening within the process. For example, flows, measured sensor values (such as pressures, temperatures, etc.), and other typical control information 300 may be illustrated to the operator next to the depiction ofthe device or area in the unit object 120 to which these values apply. These values may be online values either measured by the actual devices within the process plant 10 or developed by devices such as field devices, control routines, etc. during operation ofthe process plant 10 and provided to the process configuration module 39 during execution ofthe process configuration module 39.
- the process configuration modules 39 and configuration objects that make up the process configuration modules 39 are communicatively tied to, and obtain data from the different devices with which they are associated and may display this data on the operator's view.
- the configuration object for a pump within the graphic of Fig. 8 may be aware that it is connected to the flow transmitter, and may receive data from the configuration object for this entity.
- the configuration object for the flow transmitter may obtain the readings ofthe flow through the actual device as measured by the device in the process plant 10.
- a method associated with the configuration object for the pump may receive the data from the configuration object for the flow transmitter, and determine the variability ofthe flow as measured by the flow transmitter and this information may be displayed on the operator's display.
- a method associated with the configuration object for the flow transmitter may determine the variability of that transmitter, or an application within the transmitter itself may determine the transmitter variability, and provide this determination as data to the configuration object for the transmitter.
- the operator's display may include an alarm banner 305 illustrating one or more pending alarms that have been received for any ofthe devices or elements depicted in or associated with the unit object 120.
- the specifics ofthe alarm banner 305, or the application which produces it, may be specified as a control attribute for the unit object 120.
- Each ofthe alarms within the alarm banner 305 may be represented using an alphanumeric indicator that is uniquely associated with the devices or elements that generated the alarm. In the example display of Fig.
- each I ofthe alarms within the alarm banner 305 may also include an information button 310, which may be selected by the operator to view more information relating to that particular alarm, to turn off or acknowledge the alarm, etc.
- a diagnostic graphic 330 entitled DeltaN Inspect illustrates the number of control modules (associated with the control routines used in the unit object 120) that are in the incorrect mode, that are in limited control, that have uncertain input and large variability.
- a diagnostic graph may indicate the number of assets being monitored (in this case 211) and of that number, how many have failed, need maintenance or some other attention soon, have an advisory condition, or are no longer communicating. It will be noted that this graphic 330 may be generated by, or the information within this graphic 330 may be obtained or generated by a control diagnostic application, which may be one ofthe applications 200-208 of Fig. 7.
- this information may be provided to the user interface routines 35 as part ofthe operator's display because this information may be referenced as an attribute by the appropriate process configuration module 39.
- the operator's display may be configured to obtain this information automatically from the appropriate applications 200-208 either separately, or because this information is referred to as a control attribute within the unit object 120.
- a production level graph 340 may also be provided on the operator's display. Again, the production level graph 340 may be generated by one ofthe applications 200-208 and provided automatically as part ofthe operator's display in the same manner as the diagnostic graph 330. It will be understood that the operator viewing the display of Fig. 8 may select any ofthe elements thereof to obtain more detailed information pertaining to that element.
- the operator may select any ofthe physical elements depicted in the display of Fig. 8 to drill down into that element to obtain more information about that element.
- selecting a valve on the display of Fig. 8 may call up the display for the Valve enabling the operator to view detailed device status and performance information only about the valve, including alarm information for the valve, the diagnostic displays configured for the valve (which may be the same as or different than the diagnostic or other displays illustrated for the unit object 120 in which the valve is located).
- the operator may select one ofthe graphs 330, 340 on the operator's display to pull up or obtain more information or even to access the application that generated that graph 330, 340.
- the operator may select displayed information to, for example, determine the origin of that information, or to determine other data related to the displayed information.
- the operator may drill down into physical elements on the display to obtain information about those elements, the operator may also go to a higher level, such as to the area in which the unit object 120 is located to view information about that area. In this manner, the operator may obtain access to wider or narrower portions ofthe process plant 10 to thereby browse around or view control information about these wider or narrower portions ofthe process plant 10. Additionally, the operator, by drilling down into different portions of a process plant 10, may view the control information 300 related to these different portions of the process plant 10. Still further, it will be understood that, if desired, the information displayed on the operator's view may be limited or specific to the portion ofthe process plant 10 depicted on the view.
- the graphs 330 and 340 and other information created by supporting applications 200-208 and placed on the operator's display may be limited to including data associated with the devices depicted on the operator's display.
- the operator may select the scope of information he or she wishes to see based on the physical portion ofthe process plant 10 depicted in the operator's display.
- the operator may move or browse to different portions ofthe process plant 10 based on the graphical depiction ofthe process plant 10 on the display, and thereby view the configuration and control information 300 associated with those different portions ofthe process plant 10 without the need for navigational tree structures, as is currently used by most process plant.applications, such as control and maintenance applications.
- the operator may select the amount of data and the area ofthe process plant 10 for which he or she wishes to see data by ⁇ browsing to the appropriate graphical depiction of that section ofthe plant 10, instead of by moving through a navigational tree structure.
- the user interface routines 35 may create a maintenance display for maintenance persons to enable maintenance persons to view the information in which they are most interested.
- maintenance persons who are primarily responsible for assuring that the actual devices and equipment within the process are operating efficiently, and for repairing and replacing malfunctioning equipment are typically concerned with and view information about the operating states ofthe devices and equipment within the process 10.
- Fig. 9 illustrates an example of a maintenance display in which a maintenance person may view device-specific information about devices and equipment within the plant 10.
- the maintenance display of Fig. 9 is associated with the unit object 120 of Figs. 4 and 5, and includes the same graphic display ofthe physical elements associated with the unit object 120, as depicted in the operator's display of Fig. 8.
- this maintenance display may be created by or associated with the process configuration module 39 for the unit object 120.
- device maintenance information (which may be obtained by the process configuration module 39 for the unit object 120) is displayed at relevant locations ofthe maintenance display.
- status or health information for devices may be displayed in the form of graphic meters or gauges 400 (i.e., the partially-shaded, semi-circular features) illustrating, for example, green (good) and red (bad).
- This health information may be measured or determined by the devices themselves (which is currently available with some devices sold by Emerson Process Management) or may be determined by one or more other applications, such as, for example, one ofthe maintenance applications 200 of Fig. 7.
- Health information for the unit, the area, and the plant may be a weighted aggregation of all the health information below the respected plant hierarchy.
- the graphic meters or gauges 400 indicate different levels of health for the different devices within the unit object 120 to provide the maintenance operator with an easy manner of determining the status or health of the device.
- a user may quickly ascertain whether an area is performing properly and will continue to perform properly. Furthermore, a maintenance person or other user may also quickly identify those devices, units, etc. that may need attention and/or which may be causing a particular problem via the maintenance display. ' , 1 . . '' ' '
- maintenance graphs 402-406 illustrating the operation ofthe unit object 120 are illustrated in the maintenance view to help a maintenance person or other user understand the current operation of this unit from a maintenance standpoint.
- these graphs 402-406 may be generated by one or more maintenance applications 200 (or other applications if so desired), arid may be selected by a maintenance person (or other user) to obtain more access to these applications.
- a maintenance person may select one ofthe graphs 402-406 to cause the application that generated the graph to change the parameters used to create the graph.
- a maintenance person or other user may view other information about a device such as, for example, the unit object 120, via an asset portal application (which has a display 408 illustrated in Fig. 9) to obtain online information provided about that device from, for example, a maintenance database.
- the maintenance display of Fig. 9 includes a maintenance alarm banner 410 that illustrates the maintenance or device alarms currently active for the devices displayed within the maintenance display.
- maintenance alarms are active for a pump named PUMP- 120, a valve controller named DVC-1800, and a flow transmitter named FT-1 10.
- the maintenance alarm banner 410 may be produced by an alarm display application that is referred to by the process configuration module 39 for the unit object 120 as a maintenance attribute.
- a maintenance person may browse to other areas, units, devices, etc. ofthe process plant 10 via the graphic display in the same manner that a control operator (or other user) does via the operator's display of Fig. 8.
- a maintenance person may access other or additional information provided by the maintenance applications by selecting one or more'of the maintenance graphs 402-406 for these applications and have these applications operate on the data or provide additional data or analysis associated with the devices currently depicted within the maintenance display.
- Fig. 10 illustrates an example of a plant manager's display for the unit object 120 of Figs. 4 and 5. While using the same graphics for the physical devices as used by the operator and the maintenance displays of Figs. 8 and 9, respectively, the manager's display may provide other types of information about the unit object 120 relevant to a manager making decisions about what to manufacture, the current level of production versus the target level, the deviation cost information, etc.
- management graphs 502, 504 may be created by the business applications 208 of Fig. 7, and the information may be configured to be part ofthe manager's display as an attribute ofthe process configuration module for the unit object 120.
- a manager (or other user) may drill down or up in the graphic display of Fig. 10 in the same manner as described above with respect to the operator and maintenance displays of Figs. 8 and 9, respectively, to view and obtain additional or different information via the display from the same or other applications designed to produce this information.
- the integrated configuration system is described herein using a unit object 120 as an example, it will be understood that similar displays and configuration activities may be performed and generated for any other entity or level of entity within the process plant 10, including physical devices (such as field devices), units, areas, the entire plant 10, as well as for logical entities such as control entities. Still further, it will be understood that the process configuration modules 39, which are created only once, are created in such a manner that they may be accessed by other applications 200-208 without the need to provide configuration infonnation to those applications 200-208. Instead, all ofthe applications 200- 208 may rely oh the process configuration modules 39 for a specification ofthe configuration ofthe process plant 10. Likewise, the process configuration modules 39 include control, maintenance, business, optimizer, etc.
- process configuration modules 39 include graphic displays depicting the devices and other entities associated therewith, including the manner in which these devices are interconnected, a user of any kind may browse to obtain information about different parts ofthe process plant 10 by browsing to a graphic display associated with that section ofthe plant 10.
- the integrated configuration system and the other applications described herein are preferably implemented in software, they may be implemented in hardware, firmware, etc., and may be implemented by any other processor associated with the process control system.
- the elements described herein may be implemented in a standard multi-purpose CPU or on specifically designed hardware or fi ⁇ nware such as an application- specific integrated circuit (ASIC) or other hard-wired device as desired.
- ASIC application- specific integrated circuit
- the software routine may be stored in any computer readable memory such as on a magnetic disk, a laser disk (such as a DVD) or other storage medium, in a RAM or ROM of a computer or processor, in any database, etc.
- this software may be delivered to a user or a process plant via any known or desired delivery method including, for example, on a computer readable disk or other transportable computer storage mechanism or over a communication channel such as a telephone line, the internet, etc. (which are viewed as being the same as or interchangeable with providing such software via a transportable storage medium).
Abstract
Description
Claims
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2007506229A JP5133681B2 (en) | 2004-03-30 | 2005-03-22 | Integrated configuration system for use in process plants |
EP05732127A EP1735695A2 (en) | 2004-03-30 | 2005-03-22 | Integrated configuration system for use in a process plant |
CN2005800107934A CN101287743B (en) | 2004-03-30 | 2005-03-22 | Integrated configuration system for use in a process plant |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/812,752 US7515977B2 (en) | 2004-03-30 | 2004-03-30 | Integrated configuration system for use in a process plant |
US10/812,752 | 2004-03-30 |
Publications (2)
Publication Number | Publication Date |
---|---|
WO2005101196A2 true WO2005101196A2 (en) | 2005-10-27 |
WO2005101196A8 WO2005101196A8 (en) | 2007-10-18 |
Family
ID=35045438
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2005/009371 WO2005101196A2 (en) | 2004-03-30 | 2005-03-22 | Integrated configuration system for use in a process plant |
Country Status (5)
Country | Link |
---|---|
US (1) | US7515977B2 (en) |
EP (1) | EP1735695A2 (en) |
JP (1) | JP5133681B2 (en) |
CN (1) | CN101287743B (en) |
WO (1) | WO2005101196A2 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9043003B2 (en) | 2009-07-31 | 2015-05-26 | Fisher-Rosemount Systems, Inc. | Graphical view sidebar for a process control system |
Families Citing this family (140)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7474929B2 (en) * | 2000-01-20 | 2009-01-06 | Fisher-Rosemount Systems, Inc. | Enhanced tool for managing a process control network |
US7174468B2 (en) * | 2002-08-01 | 2007-02-06 | Texas Instruments Incorporated | Methodology for coordinating and tuning application power |
US7117052B2 (en) * | 2003-02-18 | 2006-10-03 | Fisher-Rosemount Systems, Inc. | Version control for objects in a process plant configuration system |
US7526347B2 (en) * | 2003-02-18 | 2009-04-28 | Fisher-Rosemount Systems, Inc. | Security for objects in a process plant configuration system |
US7369912B2 (en) * | 2003-05-29 | 2008-05-06 | Fisher-Rosemount Systems, Inc. | Batch execution engine with independent batch execution processes |
WO2005086331A2 (en) | 2004-03-02 | 2005-09-15 | Rosemount, Inc. | Process device with improved power generation |
US8538560B2 (en) * | 2004-04-29 | 2013-09-17 | Rosemount Inc. | Wireless power and communication unit for process field devices |
JP2007536634A (en) | 2004-05-04 | 2007-12-13 | フィッシャー−ローズマウント・システムズ・インコーポレーテッド | Service-oriented architecture for process control systems |
US7729789B2 (en) | 2004-05-04 | 2010-06-01 | Fisher-Rosemount Systems, Inc. | Process plant monitoring based on multivariate statistical analysis and on-line process simulation |
US8145180B2 (en) | 2004-05-21 | 2012-03-27 | Rosemount Inc. | Power generation for process devices |
US7043960B1 (en) * | 2004-06-17 | 2006-05-16 | The United States Of America As Represented By The Administrator Of The National Aeronautics And Space Administration | Self-calibrating pressure transducer |
US7262693B2 (en) | 2004-06-28 | 2007-08-28 | Rosemount Inc. | Process field device with radio frequency communication |
US8160535B2 (en) | 2004-06-28 | 2012-04-17 | Rosemount Inc. | RF adapter for field device |
US7836457B2 (en) * | 2004-07-19 | 2010-11-16 | Sap Ag | Hybrid contextual floor plans for object instances |
US7864158B1 (en) * | 2004-10-06 | 2011-01-04 | Mcgeever Daniel Robert | Use of graphical information to control processes |
US9184364B2 (en) | 2005-03-02 | 2015-11-10 | Rosemount Inc. | Pipeline thermoelectric generator assembly |
US7313448B2 (en) * | 2005-08-15 | 2007-12-25 | Honeywell International Inc. | Method and apparatus for providing a standard control system with custom application capability |
US7444191B2 (en) | 2005-10-04 | 2008-10-28 | Fisher-Rosemount Systems, Inc. | Process model identification in a process control system |
US8036760B2 (en) * | 2005-10-04 | 2011-10-11 | Fisher-Rosemount Systems, Inc. | Method and apparatus for intelligent control and monitoring in a process control system |
US7738975B2 (en) * | 2005-10-04 | 2010-06-15 | Fisher-Rosemount Systems, Inc. | Analytical server integrated in a process control network |
DE102005051795A1 (en) * | 2005-10-27 | 2007-05-03 | Endress + Hauser Wetzer Gmbh + Co Kg | Display device for process automation engineering, has microcontroller for evaluating digital current signal and for controlling display unit, which represents actual measuring value and corresponding status information of transducer |
US7738973B2 (en) * | 2005-11-14 | 2010-06-15 | Rockwell Automation Technologies, Inc. | Distributed historian architecture and interfaces |
US7831317B2 (en) * | 2005-11-14 | 2010-11-09 | Rockwell Automation Technologies, Inc. | Distributed historian architecture |
FR2896716B1 (en) * | 2006-01-31 | 2009-06-26 | Abb Mc Soc Par Actions Simplif | METHOD FOR CONTROLLING A ROBOTIZED WORK STATION AND CORRESPONDING ROBOTIC STATION |
US7463940B2 (en) * | 2006-03-30 | 2008-12-09 | Invensys Systems, Inc. | Multiple model development using subflowsheet functionality |
US7913566B2 (en) | 2006-05-23 | 2011-03-29 | Rosemount Inc. | Industrial process device utilizing magnetic induction |
US7721212B2 (en) * | 2006-06-28 | 2010-05-18 | Sap Ag | Configuring enterprise computing system |
FR2905018B1 (en) * | 2006-08-17 | 2008-10-10 | Peugeot Citroen Automobiles Sa | THREE-DIMENSIONAL GRAPHICAL MODELING METHOD |
US8188359B2 (en) | 2006-09-28 | 2012-05-29 | Rosemount Inc. | Thermoelectric generator assembly for field process devices |
US20080092067A1 (en) * | 2006-10-16 | 2008-04-17 | Invensys Systems, Inc. | Custom properties for automation control |
US20080255681A1 (en) * | 2007-04-10 | 2008-10-16 | Cindy Alsup Scott | Methods and apparatus to manage process plant alarms |
US20090012631A1 (en) * | 2007-07-03 | 2009-01-08 | Dale Fuller | Automation safety life cycle |
JP2009116718A (en) * | 2007-11-08 | 2009-05-28 | Hitachi Ltd | Plant monitoring control system |
WO2009154748A2 (en) | 2008-06-17 | 2009-12-23 | Rosemount Inc. | Rf adapter for field device with low voltage intrinsic safety clamping |
US9043716B2 (en) * | 2008-03-26 | 2015-05-26 | Fisher-Rosemount Systems, Inc. | Methods and apparatus to create process control graphics based on process control information |
US8250924B2 (en) | 2008-04-22 | 2012-08-28 | Rosemount Inc. | Industrial process device utilizing piezoelectric transducer |
US8847571B2 (en) | 2008-06-17 | 2014-09-30 | Rosemount Inc. | RF adapter for field device with variable voltage drop |
US8929948B2 (en) | 2008-06-17 | 2015-01-06 | Rosemount Inc. | Wireless communication adapter for field devices |
US8049361B2 (en) | 2008-06-17 | 2011-11-01 | Rosemount Inc. | RF adapter for field device with loop current bypass |
US8694060B2 (en) | 2008-06-17 | 2014-04-08 | Rosemount Inc. | Form factor and electromagnetic interference protection for process device wireless adapters |
US8219935B2 (en) | 2008-06-24 | 2012-07-10 | Signature Control Systems, Inc. | Method and system for providing isolated detail information about stations which are simultaneously active in an irrigation system |
US9417626B2 (en) * | 2008-09-29 | 2016-08-16 | Fisher-Rosemount Systems, Inc. | Efficient design and configuration of elements in a process control system |
US9582234B2 (en) * | 2008-09-30 | 2017-02-28 | Rockwell Automation Technologies, Inc. | System and method for the automatic aggregation of industrial automation displays |
WO2010039225A2 (en) * | 2008-10-01 | 2010-04-08 | Rosemount Inc. | Process control system having on-line and off-line test calculation for industrial process transmitters |
US7977924B2 (en) | 2008-11-03 | 2011-07-12 | Rosemount Inc. | Industrial process power scavenging device and method of deriving process device power from an industrial process |
IT1399165B1 (en) * | 2009-03-10 | 2013-04-11 | Ansaldo Energia Spa | MONITORING AND DIAGNOSTIC SYSTEM OF A PLANT FOR THE PRODUCTION OF ELECTRICITY |
WO2010102875A1 (en) * | 2009-03-13 | 2010-09-16 | Abb Technology Ag | A method for control in a process control system implemented in part by one or more computer implemented run-time processes |
US8881039B2 (en) | 2009-03-13 | 2014-11-04 | Fisher-Rosemount Systems, Inc. | Scaling composite shapes for a graphical human-machine interface |
RU2522312C2 (en) * | 2009-05-15 | 2014-07-10 | Фишер-Роузмаунт Системз, Инк. | Portable tool for in-situ servicing with perfected functions |
US9532232B2 (en) | 2009-05-15 | 2016-12-27 | Fisher-Rosemount Systems, Inc. | Detection and location of wireless field devices |
US9674976B2 (en) | 2009-06-16 | 2017-06-06 | Rosemount Inc. | Wireless process communication adapter with improved encapsulation |
US8626087B2 (en) | 2009-06-16 | 2014-01-07 | Rosemount Inc. | Wire harness for field devices used in a hazardous locations |
US9256219B2 (en) * | 2009-08-11 | 2016-02-09 | Fisher-Rosemount Systems, Inc. | System configuration using templates |
US9207143B2 (en) * | 2009-08-18 | 2015-12-08 | Innovative Pressure Testing, Llc | System and method for determining leaks in a complex system |
US10031042B2 (en) | 2009-08-18 | 2018-07-24 | Innovative Pressure Testing, Llc | System and method for detecting leaks |
DE102009047544A1 (en) * | 2009-12-04 | 2011-06-09 | Endress + Hauser Process Solutions Ag | Method for setting parameters of a field device power supply module |
US9557735B2 (en) * | 2009-12-10 | 2017-01-31 | Fisher-Rosemount Systems, Inc. | Methods and apparatus to manage process control status rollups |
US8825183B2 (en) * | 2010-03-22 | 2014-09-02 | Fisher-Rosemount Systems, Inc. | Methods for a data driven interface based on relationships between process control tags |
EP2383668A1 (en) * | 2010-04-16 | 2011-11-02 | Siemens Aktiengesellschaft | Simulation model |
US8555190B2 (en) | 2010-06-30 | 2013-10-08 | Honeywell International Inc. | Apparatus and method for optimizing maintenance and other operations of field devices in a process control system using user-defined device configurations |
US9709973B2 (en) | 2010-07-28 | 2017-07-18 | Fisher-Rosemount Systems, Inc. | Handheld field maintenance tool with improved diagnostics |
US10761524B2 (en) | 2010-08-12 | 2020-09-01 | Rosemount Inc. | Wireless adapter with process diagnostics |
US9448556B2 (en) | 2010-10-22 | 2016-09-20 | Honeywell International Inc. | Apparatus and method for advanced alarming in field device protocols |
CN102163051A (en) * | 2010-12-10 | 2011-08-24 | 中国广东核电集团有限公司 | Digital control method and system of primary circuit hydrostatic test of pressurized water reactor nuclear power station |
JP5390502B2 (en) * | 2010-12-22 | 2014-01-15 | 日立Geニュークリア・エナジー株式会社 | Drawing display device |
US9524285B2 (en) | 2011-03-05 | 2016-12-20 | Kapaleeswar Madireddi | Stream flow chemical process information system and method |
US8468461B2 (en) | 2011-03-05 | 2013-06-18 | Flowatch Llc | Form-based user-configurable processing plant management system and method |
DE102011017305A1 (en) * | 2011-04-15 | 2012-10-18 | Abb Technology Ag | Operating and monitoring system for technical installations |
US9927788B2 (en) | 2011-05-19 | 2018-03-27 | Fisher-Rosemount Systems, Inc. | Software lockout coordination between a process control system and an asset management system |
EP2533148A1 (en) * | 2011-06-08 | 2012-12-12 | Siemens Aktiengesellschaft | Graphical editor for developing programs for process control based on templates and detecting the differences between hierarchical data structures |
US20130042195A1 (en) * | 2011-08-08 | 2013-02-14 | Luda Svoyatsky | Managing Workflow of Multiple Dependent Processes |
US20130100136A1 (en) * | 2011-10-24 | 2013-04-25 | Kim Ordean Van Camp | Sparkline presentations of process control system alarms |
US9310794B2 (en) | 2011-10-27 | 2016-04-12 | Rosemount Inc. | Power supply for industrial process field device |
US9318078B2 (en) | 2011-10-31 | 2016-04-19 | Invensys Systems, Inc. | Intelligent memory management system and method for visualization of information |
EP3264271B1 (en) * | 2012-02-07 | 2020-09-09 | Mts Systems Corporation | Mobile or cloud communication platform for test system applications, mobile application tool and graphical user interface |
GB2501757A (en) * | 2012-05-04 | 2013-11-06 | Ibm | Instrumentation of software applications for configuration thereof |
US8793638B2 (en) * | 2012-07-26 | 2014-07-29 | Taiwan Semiconductor Manufacturing Company, Ltd. | Method of optimizing design for manufacturing (DFM) |
JP2014134918A (en) * | 2013-01-09 | 2014-07-24 | Azbil Corp | Apparatus management device and apparatus management method |
US9430589B2 (en) * | 2013-02-05 | 2016-08-30 | Rockwell Automation Technologies, Inc. | Safety automation builder |
US9665088B2 (en) | 2014-01-31 | 2017-05-30 | Fisher-Rosemount Systems, Inc. | Managing big data in process control systems |
US9558220B2 (en) | 2013-03-04 | 2017-01-31 | Fisher-Rosemount Systems, Inc. | Big data in process control systems |
US10649449B2 (en) | 2013-03-04 | 2020-05-12 | Fisher-Rosemount Systems, Inc. | Distributed industrial performance monitoring and analytics |
US10649424B2 (en) | 2013-03-04 | 2020-05-12 | Fisher-Rosemount Systems, Inc. | Distributed industrial performance monitoring and analytics |
US10678225B2 (en) | 2013-03-04 | 2020-06-09 | Fisher-Rosemount Systems, Inc. | Data analytic services for distributed industrial performance monitoring |
US10909137B2 (en) | 2014-10-06 | 2021-02-02 | Fisher-Rosemount Systems, Inc. | Streaming data for analytics in process control systems |
US10223327B2 (en) | 2013-03-14 | 2019-03-05 | Fisher-Rosemount Systems, Inc. | Collecting and delivering data to a big data machine in a process control system |
US10866952B2 (en) | 2013-03-04 | 2020-12-15 | Fisher-Rosemount Systems, Inc. | Source-independent queries in distributed industrial system |
US10386827B2 (en) | 2013-03-04 | 2019-08-20 | Fisher-Rosemount Systems, Inc. | Distributed industrial performance monitoring and analytics platform |
US10282676B2 (en) | 2014-10-06 | 2019-05-07 | Fisher-Rosemount Systems, Inc. | Automatic signal processing-based learning in a process plant |
CN107885494B (en) * | 2013-03-15 | 2021-09-10 | 费希尔-罗斯蒙特系统公司 | Method and computer system for analyzing process control data |
US11573672B2 (en) | 2013-03-15 | 2023-02-07 | Fisher-Rosemount Systems, Inc. | Method for initiating or resuming a mobile control session in a process plant |
US20140309793A1 (en) * | 2013-04-15 | 2014-10-16 | General Cybernation Group, Inc. | Method and apparatus of self-organizing actuation and control |
US20140305507A1 (en) * | 2013-04-15 | 2014-10-16 | General Cybernation Group, Inc. | Self-organizing multi-stream flow delivery process and enabling actuation and control |
DE102013015925A1 (en) * | 2013-09-24 | 2015-03-26 | Abb Technology Ag | Tool for configuring a freely programmable control device |
WO2015057228A1 (en) | 2013-10-17 | 2015-04-23 | Innovative Pressure Testing, Llc | System and method for a benchmark pressure test |
BR112016008245B1 (en) | 2013-10-17 | 2021-03-16 | Innovative Pressure Testing, Llc | method and system for determining the presence of a leak in a pressure system |
US9734470B2 (en) * | 2013-11-14 | 2017-08-15 | Honeywell International Inc. | Apparatus and method for providing customized viewing and control of field devices through custom groups and actions in a process control system |
GB2522338B (en) * | 2014-01-03 | 2020-12-16 | Fisher Rosemount Systems Inc | Reusable graphical elements with quickly editable features for use in user displays of plant monitoring systems |
EP3114538B1 (en) * | 2014-03-06 | 2019-10-16 | ABB Schweiz AG | Optimized method for sorting alarms |
DE102014004754A1 (en) * | 2014-04-01 | 2015-10-01 | Abb Technology Ag | Method and device for managing and configuring field devices of an automation system |
US9720396B2 (en) * | 2014-05-23 | 2017-08-01 | Fisher-Rosemount Systems, Inc. | Methods and apparatus to configure process control systems based on generic process system libraries |
US10168691B2 (en) | 2014-10-06 | 2019-01-01 | Fisher-Rosemount Systems, Inc. | Data pipeline for process control system analytics |
WO2016056297A1 (en) * | 2014-10-07 | 2016-04-14 | 株式会社テイエルブイ | Fluid leakage data management apparatus and management system |
US20160132037A1 (en) * | 2014-11-11 | 2016-05-12 | Yokogawa Electric Corporation | Process control systems and systems and methods for configuration thereof |
US9851712B2 (en) | 2014-11-12 | 2017-12-26 | Yokogawa Electric Corporation | Process control system and configuration system for an industrial plant |
US10108183B2 (en) * | 2014-11-12 | 2018-10-23 | Yokogawa Electric Corporation | Process control system and configuration system |
DE102014016819A1 (en) | 2014-11-14 | 2016-05-19 | Abb Technology Ag | Method and device for managing and configuring field devices of an automation system |
US10739171B2 (en) | 2015-02-10 | 2020-08-11 | Schneider Electric Systems Usa, Inc. | Vortex flowmeter |
WO2016151744A1 (en) * | 2015-03-24 | 2016-09-29 | 三菱電機株式会社 | Plant monitor/control device |
DE102015215513A1 (en) * | 2015-08-13 | 2017-02-16 | Avl List Gmbh | System for monitoring a technical device |
DE112016004669T8 (en) * | 2015-10-12 | 2018-08-23 | Fisher-Rosemount Systems, Inc. | Automatic circle test for a process control loop |
DE102015221517A1 (en) * | 2015-11-03 | 2017-05-04 | Krones Ag | Operating module for operating a machine in the food industry |
US10503483B2 (en) | 2016-02-12 | 2019-12-10 | Fisher-Rosemount Systems, Inc. | Rule builder in a process control network |
EP3226184A1 (en) * | 2016-03-30 | 2017-10-04 | Tata Consultancy Services Limited | Systems and methods for determining and rectifying events in processes |
JP6725934B2 (en) * | 2016-05-25 | 2020-07-22 | ケーズクリエイション合同会社 | Data management device, data management method in the device, data management program, and data management system |
GB2601080B (en) * | 2016-10-24 | 2022-10-19 | Fisher Rosemount Systems Inc | Systems and methods for merging modular control systems into a process plant |
GB2568786B (en) * | 2017-10-02 | 2022-11-09 | Fisher Rosemount Systems Inc | Plant/project standards and display themes in a process control plant |
GB2568785B (en) * | 2017-10-02 | 2023-02-15 | Fisher Rosemount Systems Inc | Systems and methods for configuring and presenting a display navigation hierarchy in a process plant |
GB2568586B (en) * | 2017-10-02 | 2022-11-23 | Fisher Rosemount Systems Inc | Systems and methods for configuring and presenting a display navigation hierachy in a process plant |
US10788972B2 (en) * | 2017-10-02 | 2020-09-29 | Fisher-Rosemount Systems, Inc. | Systems and methods for automatically populating a display area with historized process parameters |
US10564993B2 (en) * | 2017-11-07 | 2020-02-18 | General Electric Company | Contextual digital twin runtime environment |
US11150632B2 (en) * | 2018-03-16 | 2021-10-19 | Yokogawa Electric Corporation | System and method for field device management using class parameter set |
US11079743B2 (en) | 2018-09-27 | 2021-08-03 | Rockwell Automation Technologies, Inc. | Project autonomy in industrial automation design environments |
US11567486B2 (en) | 2018-09-27 | 2023-01-31 | Rockwell Automation Technologies, Inc. | Automated industrial process testing via cross-domain object types |
US10761514B2 (en) | 2018-09-27 | 2020-09-01 | Rockwell Automation Technologies, Inc. | Intelligent binding and selection of hardware via automation control objects |
US11119463B2 (en) | 2018-09-27 | 2021-09-14 | Rockwell Automation Technologies, Inc. | Automation objects for integrated design environments |
US11714394B2 (en) * | 2018-09-28 | 2023-08-01 | Fisher-Rosemount Systems, Inc | Bulk commissioning of field devices within a process plant |
US20210382450A1 (en) * | 2018-10-10 | 2021-12-09 | Cip Control Ltd. | System and method for computerized programing of a controller of an industrial system |
EP3715984B1 (en) * | 2019-03-28 | 2024-03-20 | ABB Schweiz AG | Automatic process graphic generation |
BE1027263A9 (en) * | 2019-05-10 | 2020-12-14 | Automotion Nv | CONTROL OF INDUSTRIAL INSTALLATIONS |
US11442439B2 (en) * | 2019-09-27 | 2022-09-13 | Rockwell Automation Technologies, Inc. | System and method for industrial automation device library |
CN112859757B (en) * | 2019-11-27 | 2022-04-22 | 宁波舜宇智能科技有限公司 | Edge calculation control method, edge calculation control device, edge computer and readable storage medium |
CN110851132A (en) * | 2020-01-15 | 2020-02-28 | 汉谷云智(武汉)科技有限公司 | Graphical modeling computer program product, method and device based on web |
CN111736558A (en) * | 2020-07-01 | 2020-10-02 | 佛山科学技术学院 | Production line equipment control method and control system |
CN111966066B (en) * | 2020-08-18 | 2021-12-10 | 北京联合普肯工程技术股份有限公司 | Equipment data processing method and device and electronic equipment |
US11449028B2 (en) * | 2020-09-03 | 2022-09-20 | Rockwell Automation Technologies, Inc. | Industrial automation asset and control project analysis |
US11294360B2 (en) | 2020-09-09 | 2022-04-05 | Rockwell Automation Technologies, Inc. | Industrial automation project code development guidance and analysis |
US11561517B2 (en) | 2020-09-09 | 2023-01-24 | Rockwell Automation Technologies, Inc. | Industrial development hub vault and design tools |
US11415969B2 (en) | 2020-09-21 | 2022-08-16 | Rockwell Automation Technologies, Inc. | Connectivity to an industrial information hub |
US11796983B2 (en) | 2020-09-25 | 2023-10-24 | Rockwell Automation Technologies, Inc. | Data modeling and asset management using an industrial information hub |
Family Cites Families (137)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4607325A (en) | 1981-10-21 | 1986-08-19 | Honeywell Inc. | Discontinuous optimization procedure modelling the run-idle status of plural process components |
US4527271A (en) | 1982-08-17 | 1985-07-02 | The Foxboro Company | Process control system with improved fault isolation |
US4734873A (en) | 1984-02-02 | 1988-03-29 | Honeywell Inc. | Method of digital process variable transmitter calibration and a process variable transmitter system utilizing the same |
US4763243A (en) | 1984-06-21 | 1988-08-09 | Honeywell Bull Inc. | Resilient bus system |
US4657179A (en) | 1984-12-26 | 1987-04-14 | Honeywell Inc. | Distributed environmental/load control system |
US4827423A (en) | 1987-01-20 | 1989-05-02 | R. J. Reynolds Tobacco Company | Computer integrated manufacturing system |
US5541833A (en) | 1987-03-30 | 1996-07-30 | The Foxboro Company | Multivariable feedforward adaptive controller |
US5043863A (en) | 1987-03-30 | 1991-08-27 | The Foxboro Company | Multivariable adaptive feedforward controller |
US4885694A (en) | 1987-04-29 | 1989-12-05 | Honeywell Inc. | Automated building control design system |
US4965742A (en) | 1987-09-30 | 1990-10-23 | E. I. Du Pont De Nemours And Company | Process control system with on-line reconfigurable modules |
US4910691A (en) | 1987-09-30 | 1990-03-20 | E.I. Du Pont De Nemours & Co. | Process control system with multiple module sequence options |
US4907167A (en) | 1987-09-30 | 1990-03-06 | E. I. Du Pont De Nemours And Company | Process control system with action logging |
US5006992A (en) | 1987-09-30 | 1991-04-09 | Du Pont De Nemours And Company | Process control system with reconfigurable expert rules and control modules |
US5488697A (en) | 1988-01-12 | 1996-01-30 | Honeywell Inc. | Problem state monitoring system |
US5193143A (en) | 1988-01-12 | 1993-03-09 | Honeywell Inc. | Problem state monitoring |
US5050095A (en) | 1988-05-31 | 1991-09-17 | Honeywell Inc. | Neural network auto-associative memory with two rules for varying the weights |
US4956793A (en) | 1988-06-24 | 1990-09-11 | Honeywell Inc. | Method and apparatus for measuring the density of fluids |
US4944035A (en) | 1988-06-24 | 1990-07-24 | Honeywell Inc. | Measurement of thermal conductivity and specific heat |
US5373452A (en) | 1988-09-02 | 1994-12-13 | Honeywell Inc. | Intangible sensor and method for making same |
US5008810A (en) | 1988-09-29 | 1991-04-16 | Process Modeling Investment Corp. | System for displaying different subsets of screen views, entering different amount of information, and determining correctness of input dependent upon current user input |
US5140530A (en) | 1989-03-28 | 1992-08-18 | Honeywell Inc. | Genetic algorithm synthesis of neural networks |
US5070458A (en) | 1989-03-31 | 1991-12-03 | Honeywell Inc. | Method of analyzing and predicting both airplane and engine performance characteristics |
US5015934A (en) | 1989-09-25 | 1991-05-14 | Honeywell Inc. | Apparatus and method for minimizing limit cycle using complementary filtering techniques |
US5187674A (en) | 1989-12-28 | 1993-02-16 | Honeywell Inc. | Versatile, overpressure proof, absolute pressure sensor |
US5442544A (en) | 1990-01-26 | 1995-08-15 | Honeywell Inc. | Single input single output rate optimal controller |
US5134574A (en) | 1990-02-27 | 1992-07-28 | The Foxboro Company | Performance control apparatus and method in a processing plant |
US5018215A (en) | 1990-03-23 | 1991-05-21 | Honeywell Inc. | Knowledge and model based adaptive signal processor |
DE69122313T2 (en) | 1990-06-21 | 1997-03-20 | Honeywell Inc | Adaptive control based on a variable horizon with means for minimizing operating costs |
US5282261A (en) | 1990-08-03 | 1994-01-25 | E. I. Du Pont De Nemours And Co., Inc. | Neural network process measurement and control |
US5197114A (en) | 1990-08-03 | 1993-03-23 | E. I. Du Pont De Nemours & Co., Inc. | Computer neural network regulatory process control system and method |
US5167009A (en) | 1990-08-03 | 1992-11-24 | E. I. Du Pont De Nemours & Co. (Inc.) | On-line process control neural network using data pointers |
US5142612A (en) | 1990-08-03 | 1992-08-25 | E. I. Du Pont De Nemours & Co. (Inc.) | Computer neural network supervisory process control system and method |
US5224203A (en) | 1990-08-03 | 1993-06-29 | E. I. Du Pont De Nemours & Co., Inc. | On-line process control neural network using data pointers |
US5121467A (en) | 1990-08-03 | 1992-06-09 | E.I. Du Pont De Nemours & Co., Inc. | Neural network/expert system process control system and method |
US5212765A (en) | 1990-08-03 | 1993-05-18 | E. I. Du Pont De Nemours & Co., Inc. | On-line training neural network system for process control |
EP0480654B1 (en) | 1990-10-10 | 1998-03-04 | Honeywell Inc. | Process system identification |
EP0496570B1 (en) | 1991-01-22 | 1998-06-03 | Honeywell Inc. | Two-level system identifier apparatus with optimization |
US5291190A (en) | 1991-03-28 | 1994-03-01 | Combustion Engineering, Inc. | Operator interface for plant component control system |
US5161013A (en) | 1991-04-08 | 1992-11-03 | Honeywell Inc. | Data projection system with compensation for nonplanar screen |
US5333298A (en) | 1991-08-08 | 1994-07-26 | Honeywell Inc. | System for making data available to an outside software package by utilizing a data file which contains source and destination information |
EP0612405B1 (en) | 1991-10-23 | 2001-08-01 | Honeywell Inc. | Apparatus for combustionless measuring fuel gas quality |
US5396415A (en) | 1992-01-31 | 1995-03-07 | Honeywell Inc. | Neruo-pid controller |
US5398303A (en) | 1992-02-28 | 1995-03-14 | Yamatake-Honeywell Co., Ltd. | Fuzzy data processing method and data smoothing filter |
US5917840A (en) | 1992-03-13 | 1999-06-29 | Foxboro Company | Protection against communications crosstalk in a factory process control system |
US5353207A (en) | 1992-06-10 | 1994-10-04 | Pavilion Technologies, Inc. | Residual activation neural network |
US5369599A (en) | 1992-08-04 | 1994-11-29 | Honeywell Inc. | Signal metric estimator |
US5692158A (en) | 1992-08-28 | 1997-11-25 | Abb Power T&D Company Inc. | Methods for generating models of non-linear systems and components and for evaluating parameters in relation to such non-linear models |
US5384698A (en) | 1992-08-31 | 1995-01-24 | Honeywell Inc. | Structured multiple-input multiple-output rate-optimal controller |
US5477444A (en) | 1992-09-14 | 1995-12-19 | Bhat; Naveen V. | Control system using an adaptive neural network for target and path optimization for a multivariable, nonlinear process |
JP2794142B2 (en) | 1992-09-14 | 1998-09-03 | 株式会社山武 | Information processing device |
US5729661A (en) | 1992-11-24 | 1998-03-17 | Pavilion Technologies, Inc. | Method and apparatus for preprocessing input data to a neural network |
CA2149913A1 (en) | 1992-11-24 | 1994-06-09 | James David Keeler | Method and apparatus for operating a neural network with missing and/or incomplete data |
US5486996A (en) | 1993-01-22 | 1996-01-23 | Honeywell Inc. | Parameterized neurocontrollers |
US5351184A (en) | 1993-01-26 | 1994-09-27 | Honeywell Inc. | Method of multivariable predictive control utilizing range control |
WO1994020887A2 (en) | 1993-03-02 | 1994-09-15 | Pavilion Technologies, Inc. | Method and apparatus for analyzing a neural network within desired operating parameter constraints |
US5390326A (en) | 1993-04-30 | 1995-02-14 | The Foxboro Company | Local area network with fault detection and recovery |
US5909541A (en) | 1993-07-14 | 1999-06-01 | Honeywell Inc. | Error detection and correction for data stored across multiple byte-wide memory devices |
US5594858A (en) | 1993-07-29 | 1997-01-14 | Fisher-Rosemount Systems, Inc. | Uniform control template generating system and method for process control programming |
US5486920A (en) | 1993-10-01 | 1996-01-23 | Honeywell, Inc. | Laser gyro dither strippr gain correction method and apparatus |
US5408406A (en) | 1993-10-07 | 1995-04-18 | Honeywell Inc. | Neural net based disturbance predictor for model predictive control |
US5596704A (en) | 1993-11-11 | 1997-01-21 | Bechtel Group, Inc. | Process flow diagram generator |
JP2929259B2 (en) | 1993-12-27 | 1999-08-03 | 株式会社山武 | controller |
US5666297A (en) | 1994-05-13 | 1997-09-09 | Aspen Technology, Inc. | Plant simulation and optimization software apparatus and method using dual execution models |
US5546301A (en) | 1994-07-19 | 1996-08-13 | Honeywell Inc. | Advanced equipment control system |
US5687090A (en) | 1994-09-01 | 1997-11-11 | Aspen Technology, Inc. | Polymer component characterization method and process simulation apparatus |
US5704011A (en) | 1994-11-01 | 1997-12-30 | The Foxboro Company | Method and apparatus for providing multivariable nonlinear control |
US5566065A (en) | 1994-11-01 | 1996-10-15 | The Foxboro Company | Method and apparatus for controlling multivariable nonlinear processes |
US5570282A (en) | 1994-11-01 | 1996-10-29 | The Foxboro Company | Multivariable nonlinear process controller |
CA2216862A1 (en) | 1995-03-31 | 1996-10-03 | Abb Power T & D Company Inc. | System for optimizing power network design reliability |
US5574638A (en) | 1995-04-03 | 1996-11-12 | Lu; Zhuxin J. | Method of optimal scaling of variables in a multivariable predictive controller utilizing range control |
US5572420A (en) | 1995-04-03 | 1996-11-05 | Honeywell Inc. | Method of optimal controller design for multivariable predictive control utilizing range control |
US5561599A (en) | 1995-06-14 | 1996-10-01 | Honeywell Inc. | Method of incorporating independent feedforward control in a multivariable predictive controller |
US5812394A (en) | 1995-07-21 | 1998-09-22 | Control Systems International | Object-oriented computer program, system, and method for developing control schemes for facilities |
US6076124A (en) * | 1995-10-10 | 2000-06-13 | The Foxboro Company | Distributed control system including a compact easily-extensible and serviceable field controller |
US6033257A (en) * | 1995-11-20 | 2000-03-07 | The Foxboro Company | I/O connector module for a field controller in a distributed control system |
US5940290A (en) * | 1995-12-06 | 1999-08-17 | Honeywell Inc. | Method of predictive maintenance of a process control system having fluid movement |
US5761518A (en) | 1996-02-29 | 1998-06-02 | The Foxboro Company | System for replacing control processor by operating processor in partially disabled mode for tracking control outputs and in write enabled mode for transferring control loops |
US5819050A (en) | 1996-02-29 | 1998-10-06 | The Foxboro Company | Automatically configurable multi-purpose distributed control processor card for an industrial control system |
US5819232A (en) | 1996-03-22 | 1998-10-06 | E. I. Du Pont De Nemours And Company | Method and apparatus for inventory control of a manufacturing or distribution process |
US7085610B2 (en) * | 1996-03-28 | 2006-08-01 | Fisher-Rosemount Systems, Inc. | Root cause diagnostics |
US5768119A (en) | 1996-04-12 | 1998-06-16 | Fisher-Rosemount Systems, Inc. | Process control system including alarm priority adjustment |
US5838563A (en) | 1996-04-12 | 1998-11-17 | Fisher-Rosemont Systems, Inc. | System for configuring a process control environment |
US5940294A (en) * | 1996-04-12 | 1999-08-17 | Fisher-Rosemont Systems, Inc. | System for assisting configuring a process control environment |
US5809490A (en) | 1996-05-03 | 1998-09-15 | Aspen Technology Inc. | Apparatus and method for selecting a working data set for model development |
US5877954A (en) | 1996-05-03 | 1999-03-02 | Aspen Technology, Inc. | Hybrid linear-neural network process control |
US6047221A (en) * | 1997-10-03 | 2000-04-04 | Pavilion Technologies, Inc. | Method for steady-state identification based upon identified dynamics |
US5742513A (en) | 1996-05-15 | 1998-04-21 | Abb Power T&D Company Inc. | Methods and systems for automatic testing of a relay |
US5918233A (en) | 1996-05-30 | 1999-06-29 | The Foxboro Company | Methods and systems for providing electronic documentation to users of industrial process control systems |
US5715158A (en) | 1996-05-31 | 1998-02-03 | Abb Industrial Systems, Inc. | Method and apparatus for controlling an extended process |
US5907701A (en) | 1996-06-14 | 1999-05-25 | The Foxboro Company | Management of computer processes having differing operational parameters through an ordered multi-phased startup of the computer processes |
US5847952A (en) | 1996-06-28 | 1998-12-08 | Honeywell Inc. | Nonlinear-approximator-based automatic tuner |
US5892679A (en) | 1996-09-13 | 1999-04-06 | Honeywell-Measurex Corporation | Method and system for controlling a multiple input/output process with minimum latency using a pseudo inverse constant |
US5777872A (en) | 1996-09-13 | 1998-07-07 | Honeywell-Measurex Corporation | Method and system for controlling a multiple input/output process with minimum latency |
US5796609A (en) | 1996-09-13 | 1998-08-18 | Honeywell-Measurex Corporation | Method and apparatus for internal model control using a state variable feedback signal |
US5898869A (en) | 1996-09-20 | 1999-04-27 | The Foxboro Company | Method and system for PCMCIA card boot from dual-ported memory |
US6041263A (en) * | 1996-10-01 | 2000-03-21 | Aspen Technology, Inc. | Method and apparatus for simulating and optimizing a plant model |
US5818736A (en) * | 1996-10-01 | 1998-10-06 | Honeywell Inc. | System and method for simulating signal flow through a logic block pattern of a real time process control system |
US5892939A (en) | 1996-10-07 | 1999-04-06 | Honeywell Inc. | Emulator for visual display object files and method of operation thereof |
US5909586A (en) | 1996-11-06 | 1999-06-01 | The Foxboro Company | Methods and systems for interfacing with an interface powered I/O device |
US5905989A (en) | 1996-11-27 | 1999-05-18 | Bently Nevada Corporation | Knowledge manager relying on a hierarchical default expert system: apparatus and method |
US5970498A (en) * | 1996-12-06 | 1999-10-19 | International Business Machines Corporation | Object oriented framework mechanism for metering objects |
US6078843A (en) * | 1997-01-24 | 2000-06-20 | Honeywell Inc. | Neural network including input normalization for use in a closed loop control system |
US6067505A (en) * | 1997-04-10 | 2000-05-23 | The Foxboro Company | Method and apparatus for self-calibration of a coordinated control system for an electric power generating station |
US6055483A (en) * | 1997-05-05 | 2000-04-25 | Honeywell, Inc. | Systems and methods using bridge models to globally optimize a process facility |
US6106785A (en) * | 1997-06-30 | 2000-08-22 | Honeywell Inc. | Polymerization process controller |
US5901058A (en) | 1997-08-22 | 1999-05-04 | Honeywell Inc. | System and methods for achieving heterogeneous data flow between algorithm blocks in a distributed control system |
US6192321B1 (en) * | 1997-09-29 | 2001-02-20 | Fisher Controls International, Inc. | Method of and apparatus for deterministically obtaining measurements |
US6014612A (en) * | 1997-10-02 | 2000-01-11 | Fisher Controls International, Inc. | Remote diagnostics in a process control network having distributed control functions |
US6175934B1 (en) * | 1997-12-15 | 2001-01-16 | General Electric Company | Method and apparatus for enhanced service quality through remote diagnostics |
US6194600B1 (en) * | 1997-12-18 | 2001-02-27 | Eprova A.G. | Method of producing aminocyanoacetamide |
US5909370A (en) | 1997-12-22 | 1999-06-01 | Honeywell Inc. | Method of predicting overshoot in a control system response |
US6093211A (en) * | 1998-04-09 | 2000-07-25 | Aspen Technology, Inc. | Polymer property distribution functions methodology and simulators |
US7562135B2 (en) * | 2000-05-23 | 2009-07-14 | Fisher-Rosemount Systems, Inc. | Enhanced fieldbus device alerts in a process control system |
US7206646B2 (en) * | 1999-02-22 | 2007-04-17 | Fisher-Rosemount Systems, Inc. | Method and apparatus for performing a function in a plant using process performance monitoring with process equipment monitoring and control |
US7346404B2 (en) * | 2001-03-01 | 2008-03-18 | Fisher-Rosemount Systems, Inc. | Data sharing in a process plant |
AU7729300A (en) * | 1999-10-01 | 2001-05-10 | Global Graphics Software Limited | Method and system for arranging a workflow using graphical user interface |
US6510353B1 (en) * | 1999-11-04 | 2003-01-21 | Fisher-Rosemount Systems, Inc. | Determining tuning parameters for a process controller from a robustness map |
US6606744B1 (en) * | 1999-11-22 | 2003-08-12 | Accenture, Llp | Providing collaborative installation management in a network-based supply chain environment |
US7130807B1 (en) * | 1999-11-22 | 2006-10-31 | Accenture Llp | Technology sharing during demand and supply planning in a network-based supply chain environment |
US6671818B1 (en) * | 1999-11-22 | 2003-12-30 | Accenture Llp | Problem isolation through translating and filtering events into a standard object format in a network based supply chain |
US6421571B1 (en) * | 2000-02-29 | 2002-07-16 | Bently Nevada Corporation | Industrial plant asset management system: apparatus and method |
US6721609B1 (en) * | 2000-06-14 | 2004-04-13 | Fisher-Rosemount Systems, Inc. | Integrated optimal model predictive control in a process control system |
US6577908B1 (en) * | 2000-06-20 | 2003-06-10 | Fisher Rosemount Systems, Inc | Adaptive feedback/feedforward PID controller |
US6789030B1 (en) * | 2000-06-23 | 2004-09-07 | Bently Nevada, Llc | Portable data collector and analyzer: apparatus and method |
EP1298510A4 (en) * | 2000-07-04 | 2005-01-26 | Asahi Engineering | System for diagnosing facility apparatus, managing apparatus and diagnostic apparatus |
US7113085B2 (en) * | 2000-11-07 | 2006-09-26 | Fisher-Rosemount Systems, Inc. | Enhanced device alarms in a process control system |
JP4160399B2 (en) * | 2001-03-01 | 2008-10-01 | フィッシャー−ローズマウント システムズ, インコーポレイテッド | Creating and displaying indicators in the process plant |
WO2003001376A1 (en) * | 2001-06-22 | 2003-01-03 | Wonderware Corporation | A customizable system for creating supervisory process control and manufacturing information applications |
US6813587B2 (en) * | 2001-06-22 | 2004-11-02 | Invensys Systems, Inc. | Remotely monitoring/diagnosing distributed components of a supervisory process control and manufacturing information application from a central location |
US6970750B2 (en) * | 2001-07-13 | 2005-11-29 | Fisher-Rosemount Systems, Inc. | Model-free adaptation of a process controller |
US7080066B1 (en) * | 2001-08-09 | 2006-07-18 | Ncr Corporation | Systems and methods for refining a decision-making process via executable sequences |
US7174342B1 (en) * | 2001-08-09 | 2007-02-06 | Ncr Corp. | Systems and methods for defining executable sequences to process information from a data collection |
US7568000B2 (en) * | 2001-08-21 | 2009-07-28 | Rosemount Analytical | Shared-use data processing for process control systems |
US7218775B2 (en) * | 2001-09-17 | 2007-05-15 | Her Majesty The Queen In Right Of Canada, As Represented By The Minister Of Agriculture And Agrifood | Method and apparatus for identifying and quantifying characteristics of seeds and other small objects |
DE10232659A1 (en) * | 2002-07-18 | 2004-02-05 | Siemens Ag | Process and configurator for creating a system concept from a number of system components |
US7165226B2 (en) * | 2002-08-23 | 2007-01-16 | Siemens Aktiengesellschaft | Multiple coupled browsers for an industrial workbench |
US7146231B2 (en) * | 2002-10-22 | 2006-12-05 | Fisher-Rosemount Systems, Inc.. | Smart process modules and objects in process plants |
-
2004
- 2004-03-30 US US10/812,752 patent/US7515977B2/en active Active
-
2005
- 2005-03-22 WO PCT/US2005/009371 patent/WO2005101196A2/en active Application Filing
- 2005-03-22 CN CN2005800107934A patent/CN101287743B/en active Active
- 2005-03-22 EP EP05732127A patent/EP1735695A2/en not_active Ceased
- 2005-03-22 JP JP2007506229A patent/JP5133681B2/en active Active
Non-Patent Citations (2)
Title |
---|
No Search * |
See also references of EP1735695A2 * |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9043003B2 (en) | 2009-07-31 | 2015-05-26 | Fisher-Rosemount Systems, Inc. | Graphical view sidebar for a process control system |
Also Published As
Publication number | Publication date |
---|---|
JP2007538310A (en) | 2007-12-27 |
WO2005101196A8 (en) | 2007-10-18 |
CN101287743A (en) | 2008-10-15 |
EP1735695A2 (en) | 2006-12-27 |
JP5133681B2 (en) | 2013-01-30 |
CN101287743B (en) | 2012-03-07 |
US7515977B2 (en) | 2009-04-07 |
US20050222698A1 (en) | 2005-10-06 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7515977B2 (en) | Integrated configuration system for use in a process plant | |
US7647126B2 (en) | Integration of process modules and expert systems in process plants | |
US8135481B2 (en) | Process plant monitoring based on multivariate statistical analysis and on-line process simulation | |
US9904268B2 (en) | Updating and utilizing dynamic process simulation in an operating process environment | |
US7146231B2 (en) | Smart process modules and objects in process plants | |
US9904263B2 (en) | Smart process objects used in a process plant modeling system | |
GB2418030A (en) | A process flow tracking system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A2 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SM SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A2 Designated state(s): BW GH GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LT LU MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
WWE | Wipo information: entry into national phase |
Ref document number: 5344/DELNP/2006 Country of ref document: IN |
|
WWE | Wipo information: entry into national phase |
Ref document number: 200580010793.4 Country of ref document: CN |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2007506229 Country of ref document: JP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWW | Wipo information: withdrawn in national office |
Ref document number: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2005732127 Country of ref document: EP |
|
WWP | Wipo information: published in national office |
Ref document number: 2005732127 Country of ref document: EP |