Smart Process Modules and Objects in Process Plants

The present invention relates generally to process plants and especially an intelligent operator environment that enables distributed control at the system level of a process plant a viewing and Detektierfunktionalität the conditions of facilities.

Distributed process control systems, as applied in the processes of chemical or petroleum industry or other processes have, characteristically one or more process controllers communicatively coupled to one or more field devices via analog, digital or combined analog / digital buses. The field devices (eg. As temperature, pressure, level and Durchflußratensensoren) can be, for example valves, valve positioners, switches and transducers are located within the process environment and perform process functions such as open about it or closing valves, measuring of process parameters from etc. Intelligent field devices, such as those that are consistent with the well-known Fieldbus protocol may also perform control calculations, warning functions and other control functions commonly implemented within the controller. The process controllers, which are also arranged characteristic within the plant environment, receive signals made by the field devices process measurements and / or other information indicate that relate to the field devices and execute a controller application that operated for example, various control modules, take the process control decisions , generated based on the received information and control signals produces the co-ordination with the control modules or blocks that are executed in the field devices such as HART and Fieldbus field devices. The control modules in the controller send the control signals on the transmission lines to the field devices to thereby control the operation of the process.

Information from the field devices and the controller is usually made via a data bus for one or more other hardware devices such as operator workstations, personal computers, data root store, report generators, centralized databases, etc. available, typically in control rooms or other locations, the rougher of the plant environment are removed, are arranged. These hardware devices run applications that allow, for example, an operator to perform functions with respect to the process, such as changing settings of the process control routine, changing the operation of the control modules within the controller or the field device, the viewing of the current process state, viewing generated by field devices and controls alarms, simulating the process operation for the purpose of training personnel or testing the process control software, maintaining and updating a configuration database, etc.

Exemplary, the DeltaV^TM Control system sold by Fisher-Rosemount Systems, Inc., has a plurality of applications that are stored in different facilities at various locations within a process plant and running of these. A configuration application, which is present in one or more operator workstations, enables users to create process control modules or to change and to download these process control modules via a data bus at certain distributed controllers. Typically, these control modules consist of communicatively interconnected function blocks which are objects in an object oriented programming protocol and perform functions within the control scheme based on received inputs and provide outputs to other function blocks within the control scheme. The configuration application may allow a designer also to create user interfaces or change to that used by a viewing application to display data to an operator and to enable the operator to change settings such as setpoints within the process control routine. Each dedicated controller and, in some cases, field devices stores and executes a controller application that runs the assigned and downloaded control modules to implement actual process control functionality. The viewing applications, which can run on one or more operator workstations, receive data from the controller application via the data and these data demonstrate process control system designers, -Bedienern or computing communities on utilizing the user interface, and can use any of a number of different views such as an operator's view, an engineer view, a technician view and so provide. A Datenhistorian application (data master storage application) is typically stored in a Datenhistorian device and executed by this; This collects and stores some or all data passing through the data bus, while a configuration database application on yet another computer can run, which is assigned to the data bus to store the current process control routine configuration and extraneous data. Alternatively, the configuration database in<?page 3?>the same workstation as the configuration application are.

As mentioned above, operator display applications are typically implemented on a system wide basis in one or more workstations and provide preconfigured displays to the operator or maintenance personnel regarding the operating state of the control system or the devices within the plant. Characteristic these ads have received the form of warnings, the warnings or alarms that are generated by controllers or devices within the process plant, by level indicators that indicate the operating state of the controllers and other devices within the process plant, maintenance displays that the operating state of the facilities designate, within the process plant, etc. generally, these ads or displays are preconfigured to display it in a known manner the information or data received from the process control modules or the devices within the process plant. In some known systems, displays are created by the use of objects which have a graphical representation in conjunction with a physical or logical element which is coupled to the physical or logical element communicatively so that it receives data about the physical or logical element. The object, the graphic change on the display screen based on the received data to display, for example, that a tank is half full, to represent the values ​​measured by a flow sensor flow, etc. The information required for the display are the true of the facilities or configuration database sent within the process plant, this information is only used to provide an indication to provide the user that contains this information. Consequently, should any information and programming, which is used to generate alarms to detect problems within the system, etc., from the plant associated various devices such as controllers and field devices during configuration of the process plant control system are generated and configured by these , Only then this information is sent to the operator display to be displayed during the process operation.

The error detection and other programming is useful, for detecting conditions, errors, alarms, etc., the control loops associated with that run at the various controls, and problems associated within the individual institutions, but it is difficult to process plant so to program that recognizes conditions or errors at the system level, which must be detected by the analysis of data from various, possibly very different devices arranged within the process plant. Furthermore, operator displays are characteristic not used to indicate or present such information about conditions at the system level for the operator or maintenance personnel, and in any case it is difficult objects within operator displays with these alternate information or data sources for the various elements within the display to animate. In addition, there are no organized way of detecting certain conditions within a facility such as by flow conditions and mass balances, while materials are moved through a system, and much less, there is a readily deployable system to perform these functions on the basis of system levels.

The <patcit><text>US 6201996 B1</text></patcit>. <patcit><text>US 5818736 A</text></patcit> and <patcit><text>DE 100 11 661 A1</text></patcit> describe generic server environments a process control system that allow system level of a process plant having a distributed control viewing and Detektierfunktionalität the conditions of facilities.

The problems and disadvantages of the known devices described above are achieved with an object unit with the features of claim 1, a process flow module system with the features of claim 21, a process flow tracking system with the features of claim 36 and a connector object unit with the features of claim 46th

An operator workstation or other computer can run an execution machine running Prozeßflußmodule which consist of interconnected smart process objects, each of which displays information about a specific unit within the process and may include behaviors or methods, respectively, which can be used to detect conditions or conditions within the plant. The Prozeßflußmodule can also practices or methods that are called Flußalgorithmen included, which can be used to detect process conditions, in particular based on a system level. The smart process objects may have: a display element is displayed to the operator, data storage means for storing data relating to an associated entity within a plant and be received by this, inputs and outputs for communication with other smart process objects and methods that can be performed on the stored and received data to detect plant or facility conditions such as leaks, errors, and other conditions.&lt;?page 4?&gt;The smart process objects may be communicatively connected to each other to create a Prozeßflußmodul which provides an indication of a system unit such as an area, means an element, a module etc. and it implements a set of rules.

In one embodiment, each smart process object of a system unit such as a field device, a controller or a logic element is assigned, and includes a data memory for the parameter or variable data belonging to this unit. The smart process object is communicatively coupled to the unit, either directly or through a configuration database to receive belonging to this unit data. Each smart process object may also be communicatively coupled to other smart process objects within the user interface to send data to the other smart process objects and receive communications, and can methods or routines have to operation on the data available for the smart process object to conditions to detect that belong to the device or system. For example, a smart process object for a tank with smart process objects for pumps or Durchflußmeßwandler on the up and downstream of the tank may be coupled and receive data indicative of the upstream and downstream flow into or out of the tank. A tank object associated method can detect leaks in the tank in that the level of the tank with the expected level in the tank based on the inlets and outlets in and out of the tank is compared. In addition, the Prozeßflußmodule may have Flußalgorithmen that can be implemented on the combination of units therein to detect conditions on a system basis, for example, material balances, flow conditions, etc. to detect.

The smart process objects and Prozeßflußmodule enable the implementation of state and Fehlerdetektierroutinen on the operator display device and can work together with the controller and the field devices of the system or eliminate the need to provide this functionality within the controller and the field devices. These smart process objects and Prozeßflußmodule also allow the operator an additional degree of programming flexibility within the process plant, which can be used to provide better and more complete information to the operator, and yet easy to use at the same time and is to be implemented. Furthermore, the operator displays can be animated with information, which are determined by the Flußalgorithmen Prozeßflußmodule or calculated them.

<figref>1</figref> is a block diagram of a distributed process control network located within a process plant, with an operator workstation that implements a display routine that uses smart process objects and Prozeßflußmodule for analyzing the process plant;

<figref>2</figref> is a logical block diagram of a set of applications and other units, with smart process objects and Prozeßflußmodulen, the applications in the operator workstation of <figref>1</figref> are stored and can be used to implement some advanced functionality in a process plant;

<figref>3</figref> shows a configuration screen that is used by an operator to generate a display process, in which smart process objects are used, which are stored in an object library;

<figref>4</figref> is a screen display showing a user interface that is generated by a Prozeßflußmodul using a plurality of smart process objects; and

<figref>5</figref> is a logical block diagram of a way how smart process objects Prozeßflußmodule used can be created in an existing process control network and implemented it.

According to <figref>1</figref> uses a process control <figref>10</figref> a distributed process control system having one or more controllers <figref>12</figref>, Each with one or more field devices <figref>14</figref> and <figref>16</figref> via input / output or I / O devices or cards <figref>18</figref> are connected, which may be so, for example, Fieldbus interfaces, Profibus interfaces, HART interfaces, standard 4-20 ma interfaces. The controls<figref>12</figref> are also provided with one or more main or operator workstations <figref>20</figref> and <figref>22</figref> via a data bus <figref>24</figref> connected, which may be an Ethernet transmission link, for example. Further, a database<figref>28</figref> to the data bus <figref>24</figref> be connected and serve as Datenhistorian, the parameter, status and other data collects and stores belonging to the controllers and field devices within the plant <figref>10</figref> belong, and / or serve as a configuration database that the current configuration of the process control system within the plant <figref>10</figref> so stores as to the controls <figref>12</figref> and field devices <figref>14</figref> and <figref>16</figref> has been downloaded and stored therein. The controls<figref>12</figref>, I / O cards <figref>18</figref> and field devices <figref>14</figref> and <figref>16</figref> are typically located within the rough &lt;?page 5?&gt;Investment environment and dispersed therein, the operator workstations <figref>20</figref> and <figref>22</figref> and the database <figref>28</figref> but are usually located in control wait or other less harsh environments, which is easily accessible for inspection or maintenance personnel.

It is known that each control <figref>12</figref>, For example, the DeltaV control by Fisher-Rosemount Systems, Inc., may be a control application includes stored and executes that implements a control strategy using a number of different, independently executed control modules or control blocks. The control modules may each be made of functional blocks as they are commonly called, are made, each function block is a part or a subroutine of an overall control routine and in conjunction with other function blocks (via designated as sections compounds) is effective to process control loops within the process plant<figref>10</figref> to implement. It is well known that functional blocks, the objects may be in an object oriented programming protocol, typically one of an input function, such as that which is associated with a transducer, a sensor or other Prozeßparametermeßeinrichtung, a control function such as that associated with a control routine a PID, fuzzy logic, etc. control executes, or an output function, perform the operation of a device such as a valve to a physical function within the process plant<figref>10</figref> perform. There are of course hybrid and other types of complex function blocks such as model predictive controllers (MPCs), optimizers, etc. The Fieldbus protocol namely the DeltaV system protocol use control modules and function blocks designed and implemented in an object oriented programming protocol, the control modules could but under application of any desired control programming scheme be formed, which, for example, sequential function blocks, ladder logic includes, etc., and are not limited to, that they are using technology function block or any other particular programming technique.

In the in <figref>1</figref> shown system can with the controls <figref>12</figref> connected field devices <figref>14</figref> and <figref>16</figref> Standard 4-20 ma devices, intelligent field devices such as HART, Profibus, or FOUNDATION^TM Fieldbus field devices, which include a processor and a memory, or any other desired type of device. Some of these devices, such as Fieldbus field devices (with<figref>16</figref> in <figref>1</figref> hereinafter) can modules or sub-modules such as function blocks in the control of the <figref>12</figref> implemented control strategy associated with, store and execute. function blocks<figref>30</figref>, in the <figref>1</figref> are shown as two different the Fieldbus field devices <figref>16</figref> are arranged in association with the execution of the control modules within the controllers <figref>12</figref> are executed to implement process control, as is well known. Of course, the field devices<figref>14</figref> and <figref>16</figref> be any type of devices, such as sensors, valves, sensors, positioners, etc. and the I / O devices <figref>18</figref> can be any type of I / O devices that match any desired communication or controller protocol such as HART, Fieldbus, Profibus, etc..

In the process plant <figref>10</figref> from <figref>1</figref> includes the Workstation <figref>20</figref> a family of operator interface applications and other data structures <figref>32</figref>To which any authorized user (referred to as operator) can have access to a functionality in terms of within the process plant <figref>10</figref> to look at related facilities and to allow. The family of operator interface applications<figref>32</figref> is in a memory <figref>34</figref> the workstation <figref>20</figref> stored, and any of the applications or units within the family of applications <figref>32</figref> can on a processor <figref>36</figref> be executed, the workstation <figref>20</figref> assigned. The entire family of applications<figref>32</figref> is as in the workstation <figref>20</figref> represented saved, but some of these applications or other entities could in other workstations or computer devices within the plant <figref>10</figref> or this may be stored assigned and executed. In addition, the family of applications display outputs can be connected to a display screen<figref>37</figref> supply of the workstation <figref>20</figref> is assigned, or to provide any other desired display screen or any other display device, which includes mobile devices, laptops, other workstations, printers and so on. Likewise, the applications within the family of applications<figref>32</figref> be distributed and executed on two or more computers or machines and be configured so that they are operated in conjunction with each other.

<figref>2</figref> shows some of the applications and data structures or other entities within the family of applications (and other units) <figref>32</figref> the workstation <figref>20</figref>, In particular, the family of applications includes<figref>32</figref> a Prozeßflußmodul Configuration Application <figref>38</figref>That is used by an operator to create Prozeßflußmodule (and associated displays) using one or more smart process objects. A library<figref>40</figref> of smart process objects <figref>42</figref> includes examples or templates of smart process objects that can be done on the access, the copied and the configuration application <figref>38</figref> can be used to Prozeßflußmodule <figref>44</figref> to create. It is understood that the&lt;?page 6?&gt;configuration application <figref>38</figref> may serve one or more Prozeßflußmodule <figref>44</figref> to create, each of which consists of one or more smart process objects and one or more Prozeßflußalgorithmen <figref>45</figref> may contain in a Prozeßflußmodulspeicher <figref>46</figref> stored. One of Prozeßflußmodule<figref>44b</figref> is in <figref>2</figref> shown in expanded form and includes a set of process elements such as valves, tanks, sensors and Durchflußmeßwandler, which are connected together by connecting members, the tubes, pipes, wires, conveyor, etc., may be.

An execution engine <figref>48</figref> operates or implements each of Prozeßflußmodule <figref>44</figref> during the term to one or more process displays for an operator as defined by the Prozeßflußmodule <figref>44</figref> generate and implement additional functionality that the Prozeßflußmodulen <figref>44</figref> and the smart process objects within the Prozeßflußmodule <figref>44</figref> assigned. The execution engine<figref>48</figref> can a rules database <figref>50</figref> use the the Prozeßflußmodulen <figref>44</figref> whole and specifically defined in the smart process objects within these modules to implement logic. The execution engine<figref>48</figref> can also be a connection matrix <figref>52</figref> use, the connections between the process elements within the plant <figref>10</figref> and within the Prozeßflußmodule <figref>44</figref> defined to the functionality for Prozeßflußmodule <figref>44</figref> to implement.

<figref>2</figref> shows one of the smart process objects <figref>42e</figref> in detail. The smart process object<figref>42e</figref> is illustrated as one of the template smart process objects, it should be understood that other smart process objects in general, the same or similar elements, features, parameters comprise, etc., as with respect to the smart process object <figref>42e</figref> are described, and that the typical details or values ​​of these elements, features and parameters of a smart process object to the next, depending on the nature and use of that smart process object may be changed or varied. Although Furthermore, the smart process objects<figref>42e</figref> be an object within an object oriented programming environment and thus include their associated data memory, inputs and outputs and methods, this smart process object can however be memo produced by any other desired programming paradigm or and implemented it.

It is understood that the smart process object <figref>42e</figref> is an object that a particular unit, such as a physical or logical entity within the process plant <figref>10</figref> from <figref>1</figref> assigned. The smart process object<figref>42e</figref> includes a data memory <figref>53</figref>Which serves to store data from the logic unit, with which the smart process object <figref>42e</figref> are cooperating, received or relate to. The data memory<figref>53</figref> generally comprises a data memory <figref>53a</figref>, The general or permanent information about the unit stores, which the smart process object <figref>42e</figref> is associated, such as manufacturer, revision, name, type data, etc. A data store <figref>53b</figref> may store variable or changing data, such as parameter data, status data, input and output data or other data on the unit, which the smart process object <figref>42e</figref> is assigned, including data relating to the unit, as it existed in the past or as it now within the process plant <figref>10</figref> exists. Of course, the smart process object<figref>42e</figref> be configured or programmed to this information on a periodic or non-periodic basis by the unit itself via any desired communication link, of the Historian <figref>28</figref> via the Ethernet bus <figref>24</figref> or receiving in any other desired manner. A data storage<figref>53c</figref> may include a graphical representation of the unit to which the smart process object <figref>42e</figref> is assigned and which is used for actual display to the operator via an operator interface, such as the screen <figref>37</figref>, Of the workstation <figref>20</figref> from <figref>1</figref> assigned. Of course, the graphical representation have placeholders (with underscores within the data memory<figref>53c</figref> labeled) for information on the unit, such as information defined by the parameter or other variable data about the unit and in the data memory <figref>53b</figref> stored. This parameter data can be displayed in the graphical place holders when the graphical representation of the operator on a display device<figref>37</figref> is presented. The graphical representation (and the smart process object<figref>42e</figref>) May also be predefined connection points (by an "X" in the data memory <figref>53c</figref> marked) which allow an operator to add up or downstream components to the process element, as shown by the graphical representation. Course allow these connection points also the smart process object<figref>42e</figref>Which can be seen with this smart object related elements according to the configuration within a Prozeßflußmoduls.

The smart process object <figref>42e</figref> may also include one or more inputs <figref>54</figref> and outputs <figref>56</figref> have to communicate with other smart process objects within or outside a Prozeßflußmoduls in which the smart process object <figref>42</figref> is, to allow. The connections of the inputs<figref>54</figref> and outputs <figref>56</figref> with other smart process objects may by an operator when configuring a &lt;?page 7?&gt;configure Prozeßflußmoduls simply by other smart process objects to these inputs and outputs are connected or by certain communications are referred to, to be held between smart process objects. Some of these inputs and outputs may be defined so that they are connected to the smart process objects connected at the predefined connection points for the smart process object as discussed above. These inputs<figref>54</figref> and outputs <figref>56</figref> can also by a set of rules within the rule database <figref>50</figref> and the connection matrix <figref>52</figref> be determined or defined, the links between different institutions or units within the plant <figref>10</figref> define. The inputs<figref>54</figref> and the outputs <figref>56</figref>That contain data memory or data buffer associated with them, are generally speaking, used to transfer data from other smart process objects to the smart process object <figref>42e</figref> or allow the transfer of data stored in the smart process object <figref>42e</figref> stored or generated thereof to allow to other smart process objects. These inputs and outputs can also be used, communications between the smart process object<figref>42e</figref> and other objects within the process control system, such as control modules within the controllers <figref>12</figref>, Field devices <figref>14</figref>. <figref>16</figref> etc, permit.

As <figref>2</figref> shows the smart process object comprises <figref>42e</figref> also a method memory <figref>58</figref>, Which serves to zero, one or more methods <figref>60</figref> (As methods <figref>60a</figref>. <figref>60b</figref> and <figref>60c</figref> in <figref>2</figref> shown) to store received from the smart process object <figref>42e</figref> during execution of a Prozeßflußmoduls by the execution engine <figref>48</figref> are to be implemented. In general use the methods in the memory<figref>58</figref> stored methods <figref>60</figref> the data in the data storage regions <figref>53a</figref> and <figref>53b</figref> are stored, and from other smart process objects via the inputs <figref>54</figref> and the outputs <figref>56</figref> obtained data or data from other sources such as the configuration database or the Historian <figref>28</figref>To provide information about the process plant <figref>10</figref> or a unit within the facility <figref>10</figref> to determine. For example, the methods<figref>60</figref> insufficient or poor operating conditions determine the intelligent of the process object <figref>42e</figref> attributable defined unit, errors that these or other entities within the process plant <figref>10</figref> attributable, etc. The methods <figref>60</figref> may be preconfigured or provided based on the type or class of smart process objects and are generally carried out every time the smart process object <figref>42e</figref> within the execution engine <figref>48</figref> is executed during the runtime. Some exemplary methods<figref>60</figref>That within a smart process object, such as the smart process object <figref>42e</figref> may be provided include detecting leaks, dead band, dead time, movement, variability, condition monitoring or other unit of the associated conditions. The methods<figref>60</figref> may also be provided for the calculation of material balances, flow rates and other conditions at the system level that the plant <figref>10</figref> assigned to be supported,. Of course, these are just a few of the methods that can be stored in a smart process object and can function well, and there may be many other methods that can be used, and these methods generally by the type of unit shown, the way how this unit is inserted in a process plant and used therein, and other factors are determined. The smart process object<figref>42e</figref> can indeed save methods and run that detect states, errors, and so on the system level, these methods can however also be used in order other information about devices, logical elements, such as process control modules and Grinding and other entities that do not belong to the system level to determine. If desired, the methods can<figref>60</figref> programmed or references to applicable rules in any desired programming language such as C, C ++, C # etc. be provided or can or applicable rules within the rule database <figref>50</figref> define that for the smart process object <figref>42e</figref> should take place during the execution.

During execution of the smart process object through the execution engine <figref>48</figref> implements the machine <figref>48</figref> the communications defined by the inputs <figref>54</figref> and outputs <figref>56</figref> to each of the smart process objects in a Prozeßflußmodul <figref>44</figref> are defined, and the methods can <figref>60</figref> implement for each of these objects to the methods by which <figref>60</figref> execute functionality provided. As noted above, the functionality of the methods<figref>60</figref> lie in programming within the smart process object or by a set of rules within the rule database <figref>50</figref> be defined by the machinery <figref>48</figref> is executed, and on the basis of the type, class, identification, tag name, etc. of a smart process object, to implement the rules defined by this functionality.

It is to be noted that the smart process object <figref>42e</figref> an assigned identifier, or a special name has, which can serve to message transmissions to and from the smart process object <figref>42e</figref> to permit, and of the execution engine <figref>48</figref> is used during the running time as a reference. Further, the parameters of the smart process object<figref>42e</figref> simple parameters, such as simple values ​​or &lt;?page 8?&gt;be smart parameters that know the expected units accompanying them. Intelligent parameters of the process rules engine or execution engine<figref>48</figref> be interpreted and used to ensure that all signals are sent in the same units or converted properly. Smart rules can also be used to groups of alarms for the smart process objects (or Prozeßflußmodule) on and off to create a smart alarm strategy and / or interface for the operator. Further, smart process object classes equipment and module classes within the process control strategy of the plant<figref>10</figref> be assigned to create a well-known connection between a smart process object and the process variables that can interpret it or on which it is to take access.

Intelligent process objects may further comprise mode, status, and alarm behavior so that these smart objects may be put in different modes or modes during runtime, such as the manual, the cascade or the automatic mode, a belonging to the object status on the can provide the basis of its current operating state and alarms 'limited' based on detected conditions, such as 'parameter out of range', 'high variability', etc., can supply. Intelligent process objects may also have a class / subclass hierarchy which enables them to be categorized in class libraries, etc. to be combined into a composite structure Further, smart process objects from other elements such as control modules and other objects are detected and released, to identify to enable the smart process object when its associated unit is busy or, for example, by a batch control process within the plant<figref>10</figref> has been acquired.

Smart process objects may be associated with any desired process entity, such as physical devices like pumps, tanks, valves, etc., or logical entities such as process areas, the process loops, process control elements, such as process control modules, etc. In some cases, smart process objects connecting means such as tubes, pipes, wiring, conveyors, or be assigned to any other body or unit, and so moves the material, electricity, gas from a point within the process to another. Intelligent process objects that connectors are assigned, which are referred to as intelligent intermediate connectors are also provided with an identifier (even if the device or the connector itself has no identification or not capable, within the process plant<figref>10</figref> to communicate) and generally serve to illustrate the process flow between smart process objects.

Intelligent interconnector typically include properties or parameters that define how different materials or phenomena (such as electricity) through the connection flow (eg., Steam, electricity, water, sewage, etc.). These parameters can type and nature of flow (such as the overall speed, the friction coefficient, the type of flow such as swirls or nichtverwirbelt, electromagnetic, etc.) denote through the connector and the possible direction or directions of flow through the connector. Intelligent interconnector may include programming or methods that ensure that the units of the source and the target object, the intelligent interconnector is connected match, and, if that is not the case, perform a conversion. The methods of intelligent intermediate connector may also represent the flow through the connector using a model or an algorithm in the model to estimate the speed or nature of the flow through the actual connectors. The stored parameters for the smart process object (such as friction parameters) may be employed in these methods. Thus, the intelligent interconnect substantially allowing the smart process objects to know the other objects in its upward and downstream. Naturally intelligent interconnector example the connections between other objects, the type of fluid, such as liquid, gas, electricity, etc. within the system, the up and downstream of the units, which other units for on the up and downstream of the unit this smart process object are, define the direction of material, fluid, electric flow, etc. in any desired or convenient manner. In one embodiment, the matrix<figref>52</figref> be generated prior to execution of Prozeßflußmodulen and may the connections between the different devices for intelligent interconnect within the system and thus define the connections between the different smart process objects. In fact, the execution engine<figref>48</figref> the matrix <figref>52</figref> use to determine the upstream and downstream entities and thereby define the communications between the smart process objects and their associated methods. Further, a set of rules or multiple sets of rules may be provided to be used by the smart process objects to dialogue with each other and to obtain data from each other, as is required for the methods in the smart process objects.

&lt;?page 9?&gt;If desired, the smart process object <figref>42e</figref> provide automatic links such as URL to key documentation which may be applicable to the type of object or (depending on the critical state) of the device may be specific to the case, to which the smart process object <figref>42e</figref> relates. The documentation may be provided by the manufacturer, as well as user-specific. Some examples of documentation include configuration, operation and maintenance documentation. If desired, a user can click on the object as it is displayed on an operator display, to the case-specific (if applicable) display and generic documentation for the object or associated device. Also, the operator may be able to documentation regardless of the system software to add / delete / change. In addition, this automatic links by the user may be configurable or changeable to the possibility to provide objects in the operator interface to add knowledge links to enable a quick navigation to appropriate information associated with the object, and the ability to offer, for the client or add specific work instructions for the object type or for the case of the object.

Generally speaking, an operator can configure application <figref>38</figref> run or run to one or more Prozeßflußmodule <figref>44</figref> to implement during operation of the process <figref>10</figref> to create. In one embodiment, the configuration application presents<figref>38</figref> the operator to configure the display as under <figref>3</figref>, Wi e<figref>3</figref> shows configuration comprises a display <figref>64</figref> a library or template section <figref>65</figref> and a configuration section <figref>66</figref>, The template section<figref>65</figref> includes a representation of groups of intelligent templates process objects <figref>67</figref> (The smart process objects <figref>42</figref> from <figref>2</figref> may have) and non-intelligent elements <figref>68</figref>, Are substantially the stencils<figref>67</figref> and <figref>68</figref> generic objects to the configuration section <figref>66</figref> can be drawn to create a case of a smart process object within a Prozeßflußmoduls. A partially completed Prozeßflußmodul<figref>44c</figref> is shown and includes a valve, two containers, two pumps, one Durchflußmeßwandler and two sensors that are connected to each other via Durchflußwegverbinder, which may be intelligent intermediate connector. It should be noted that the Prozeßflußmodul<figref>44c</figref> can consist of both smart process objects as well as from non-intelligent elements.

When generating a Prozeßflußmoduls such as the Prozeßflußmoduls <figref>44c</figref> the operator can smart process objects <figref>67</figref> and the elements <figref>68</figref>That in the template section <figref>65</figref> are shown, select and the configuration section <figref>66</figref> drag and drop them there in any desired location. Generally, the operator selects one or more intelligent setup process objects<figref>67a</figref> or non-intelligent elements <figref>68</figref>Show, and bring them up the configuration section, the facilities <figref>66</figref>, The operator then connects the intelligent setup process objects and non-intelligent elements, the configuration section within the<figref>66</figref> can be seen, with smart connector process objects <figref>67b</figref> or non-intelligent elements <figref>68</figref>show the connector. The operator can the features of each of the smart process objects and non-intelligent elements during this process change using pop-up feature menus, etc. and in particular, the methods, parameters, identifiers, names, automatic links, modes, classes, inputs and outputs, etc., which these smart process objects are associated with change. When the operator has created a Prozeßflußmodul with each of the desired elements, which is typically a process configuration, an area representing etc., the operator rules or other module associated functionalities may define. Such rules may be run rules such as those that are associated with the system-level embodiment of the methods, such as material balance and Durchflußberechnungen, during operation of the module<figref>44c</figref> are to be executed. After the generation of the module<figref>44c</figref> the operator of this module in the module memory <figref>46</figref> from <figref>2</figref> secure and can at this time or later the Prozeßflußmodul instantiate and in the execution engine <figref>48</figref> Download in such a manner that the execution engine <figref>48</figref> the Prozeßflußmodul <figref>44c</figref> can operate.

If desired, the smart process objects may be provided within a Prozeßflußmoduls with a specific identifier, or an identifier that contains an alias that during the term, for example by the execution engine <figref>48</figref> can be filled or selected, and on the basis of other factors such as a system component or a route that is selected within the process control system. The use of aliases and indirect references in process control systems is described in detail in<patcit><text>U.S. Patent No. 6,385,496</text></patcit> discussed, which is assigned to the assignee of the present invention and is incorporated herein by reference. Each of these techniques can be applied to in identifiers for the smart process objects that are described herein provide and resolve aliases. By using aliases and like the same Prozeßflußmodul may have different views of device groups or be used to support such views, etc.

&lt;?page 10?&gt;the display <figref>64</figref> from <figref>3</figref> shows flags (View1, View2 and View3) for different views of the Prozeßflußmoduls <figref>44c</figref>, These banners can serve in various views that the Prozeßflußmodul<figref>44c</figref> cooperate to access and create it using some of the same smart process objects therein. The use of aliases in one or more of these views for example, allows a routing supervisor or a Leitwegansicht which / that defines a route for the process flow within the process plant during the term, the module<figref>44c</figref> View1 of use, although different actual devices that are used within the particular route, after the generation of Prozeßflußmoduls <figref>44c</figref> are designated. In fact, the smart process objects with different process units can be connected at various times during the period and these are assigned. By using aliases, the Prozeßflußmodule are therefore not limited to the static binding between the graphical user display and the Prozeßflußdatenbank. For example, a view (such as View2 from<figref>3</figref>) Be assigned to a routing routine which is used by an operator to select a route by different ones of the process units. When selecting the particular route, whereby certain process units are referred to, the identifier names or aliases can be filled in the other views, whereby the behavior of these views changed or designated.

Generally speaking, stores the configuration application <figref>38</figref> Then, when the operator creates a Prozeßflußmodul, automatically the smart process objects, along with the links between them in a Prozeßflußdatenbank. This Prozeßflußdatenbank can then be used to generate other Prozeßflußmodule that provide, for example, one of them different view with the use of one or more of the same smart process objects. So when the second view is created, the user can just as it has already been generated and stored in the Prozeßflußdatenbank health refer to the smart process object as well to all methods, etc. stored therewith, to this smart process object in the second view to place. In this way the Prozeßflußdatenbank can be filled while the process control modules are created, and the Prozeßflußdatenbank may at any time be used to generate and execute other views, modules and graphical displays, which smart process objects are used, which are already present within the Prozeßflußdatenbank. By using such a Prozeßflußdatenbank, each smart process object support various Prozeßflußmodule within Prozeßflußdatenbank or used therein and are used in different views or displays for this Prozeßflußmodule. It is further understood that the Prozeßflußmodule be formed or constructed by building displays for these modules and then designating Flußalgorithmen who use these Prozeßflußmodulen or these are attributable. Of course, individual Prozeßflußmodule can be distributed over several computers and run it, and Prozeßflußmodule may be communicatively connected to each other, to work together with one another, either on the same computer or on different computers.

As noted above, the operator can attach as part of the process of forming or configuring the Prozeßflußmoduls Prozeßflußalgorithmen to the Prozeßflußmodul or provide for it. This Prozeßflußalgorithmen may be configured to determine certain characteristics of the process or the system level, such as material balance calculations, Flußberechnungen, efficiency calculations, economic calculations, etc. with respect to the process, which is indicated by the Prozeßflußmodul or shown as a model. Consequently, the Prozeßflußmodule may itself have mode, status, and alarm behavior, workstations can be assigned and can be downloaded as part of the display downloads. If desired, the Flußalgorithmen of a separate or other execution engine or by the execution engine can<figref>48</figref> be performed to material or heat balance, Flußleitweg-, Flußeffizienz-, Flußoptimierungs-, perform feasibility studies, which are based on the river, or other desired riverine perform calculations using the data contained in the smart process objects of Prozeßflußmoduls. In addition, these Flußalgorithmen can access parameters from the control strategy, ie. To the control modules which are the controllers, field devices, etc. associated with and downloaded to these, and can conversely, provide data or information to these control modules

The execution of these Flußalgorithmen can be enabled and disabled by the operator at any time, module by module. Likewise, the operation of this Flußalgorithmen can be tested and verified in any desired manner, before the Prozeßflußmodul in execution engine<figref>48</figref> is downloaded. Similarly, the smart process objects can Prozeßflußmodule or their associated Flußalgorithmen from other units within the process control system or plant<figref>10</figref> be acquired and released. In order for this intelligent behavior is achieved, can&lt;?page 11?&gt;Displays are built for Prozeßflußmodule of display classes, are those associated with optional one or more of Prozeßflußalgorithmen. To activate a Prozeßflußalgorithmus the user can select the display and activate the specific behavior (eg. As material balance, Flußberechnung etc.), which will be effective on the scope of the defined on the display smart process objects. To perform these functions the Prozeßflußalgorithmen a specific workstation should be assigned, which can be defined as a property of the display or the display class.

It is understood that the execution engine <figref>48</figref> is required to activate the Prozeßflußalgorithmen to the effect that they run on a collection of all process objects and links that are configured on all displays. Thus Prozeßflußalgorithmen generally lead regardless of whether there is any display is loaded, that is called, and a user views information. Of course, the Prozeßflußalgorithmen can throughout the process<figref>10</figref> or via defined subsets of the process <figref>10</figref> be cross-checked. It is further understood that during the execution of a particular execution engine Prozeßflußmoduls<figref>48</figref> can provide an operator at an operator interface, a display, which displays the objects or units connected to each other within the Prozeßflußmoduls, and on the basis of the graphical representations of the smart process objects and the non-intelligent elements within this Prozeßflußmoduls. The parameters, graphics, etc. of the display are determined by the configuration and connection of the intelligent and non-intelligent elements within the Prozeßflußmoduls. Furthermore, alarms and other information to be made available on this display or other displays, defined and generated by the methods within the smart process objects and the Flußalgorithmen that are associated with a particular Prozeßflußmodul. If desired, the execution engine<figref>48</figref> send a theme for a Prozeßflußmodul to more than one operator interface or can be configured or adjusted so that no display is provided, even though the execution engine <figref>48</figref> continues to execute the Prozeßflußmodul and thereby the associated methods, alarm behavior, Flußalgorithmen performs so.

<figref>4</figref> is an exemplary screen display <figref>70</figref>, That of the operator interface application <figref>32</figref> on the display <figref>37</figref> the workstation <figref>20</figref> from <figref>1</figref> can be generated. The screen display<figref>70</figref> includes a representation of numerous process plant units, such as those in the system <figref>10</figref> from <figref>1</figref> are set up and configured. In particular, the flow of fluid from a storage tank to a pump takes place<figref>72</figref>, The liquid through a Durchflußmeßwandler <figref>74</figref> to a tank <figref>76</figref> promotes at which a measuring device such as a level sensor / transducer <figref>78</figref> is attached. A pump<figref>80</figref> promotes liquid from the tank <figref>76</figref> through a valve <figref>82</figref>, A Durchflußmeßwandler <figref>84</figref> and a heat exchanger <figref>86</figref> to a second tank <figref>88</figref>At which a sensor / transducer means (or Transmitte device) <figref>89</figref> is attached. The Tank<figref>88</figref> provides a first amount released by a Durchflußmeßwandler and a heat exchanger <figref>92</figref> to a third tank <figref>94</figref>On which a measuring or sensor device <figref>95</figref> is arranged. The Tank<figref>94</figref> provides a discharge rate through a heat exchanger <figref>96</figref> and a Durchflußmeßwandler <figref>98</figref> to a distillation column. The Tank<figref>94</figref> further provides a discharge amount by a pump <figref>100</figref>, A Durchflußmeßwandler (or Transmitter) <figref>101</figref> and a valve <figref>102</figref> back to the entrance of the heat exchanger <figref>86</figref>, Similarly, a second amount of the tank<figref>88</figref> by means of a pump <figref>104</figref> through a valve <figref>106</figref> and a Durchflußmeßwandler (or Transmitter) <figref>108</figref> conveyed to a Stufendestilliersäule. The in-screen display<figref>70</figref> Units shown comprise tanks, pumps, Durchflußmeßwandler, valves, pipes, etc. that are connected in a specific configuration with one another, but all other process units including hardware devices and software or logic elements such as control loops, control modules, function blocks, etc., can within the screen display <figref>70</figref> be displayed in any desired configuration. Further, each of these devices, such as the tanks, sensors, valves, etc. as well as the connections between them, the on-screen<figref>70</figref> are shown, generated by smart process objects within or associated Prozeßflußmoduls intended for the production of the display <figref>70</figref> is used during the term of this module.

It will be appreciated that at least some of the interconnected units within the screen display <figref>70</figref> using the configuration application <figref>38</figref> are configured and the display screen <figref>70</figref> by the execution engine <figref>48</figref> can be displayed during the term of a Prozeßflußmoduls based on the smart process objects and other elements within the currently executing Prozeßflußmoduls. For example, the tanks<figref>76</figref>. <figref>88</figref> and <figref>94</figref>That Durchflußmeßwandler <figref>74</figref>. <figref>84</figref>. <figref>90</figref>. <figref>98</figref>. <figref>101</figref> and <figref>108</figref> and the sensor / Meßwandlereinrichtungen <figref>78</figref>. <figref>89</figref> and <figref>95</figref> and one or more of the connectors connecting these elements, on the display screen <figref>70</figref> are generated by the associated smart process objects. Of course, only some of these units smart process objects need to be assigned.

&lt;?page 12?&gt;During operation, the execution engine <figref>48</figref> gain to the units of the in <figref>4</figref> shown module associated smart process objects data from the actual hardware devices (or software units) that are assigned to them, and this data may in some cases for the operator on the screen <figref>70</figref> Show as part of graphic elements of the smart process object or in association with this. Exemplary information displays are for Durchflußmeßwandler<figref>74</figref>. <figref>84</figref>. <figref>90</figref> and <figref>98</figref> and for level sensors <figref>78</figref> and <figref>89</figref> shown. Of course, certain of smart process objects be communicatively coupled with each other to send data to each other and to receive data from each other so that they can perform their associated methods. For example, the intelligent connector data with respect to the flow, etc. from other smart process objects within the in<figref>4</figref> get shown Prozeßflußmoduls. As indicated above, the methods for the smart process objects to perform any other functions on the data received from the smart process objects and these are transmitted to operating and other conditions within the plant<figref>10</figref> to detect what comprises errors or other adverse (or potentially good) conditions associated with the process plant <figref>10</figref> or their institutions are related.

In one example, the tank can <figref>88</figref>Which Sensormeßwandler (or Transmitter <figref>89</figref>), Which may be a level sensor, and the flow transducer (or Transmitter) <figref>84</figref>. <figref>90</figref>. <figref>101</figref> and <figref>108</figref> (The Durchflußsensoreinrichtungen are) to be associated with each other smart process object and the screen <figref>70</figref> are generated using a smart process object. These smart process objects are communicatively coupled to the various bodies to which they are assigned, coupled and retrieve data from them. Thus obtained the smart process objects for Durchflußmeßwandler<figref>84</figref>. <figref>90</figref>. <figref>101</figref> and <figref>108</figref> the measured values ​​of the flow through these actual devices as these devices in the system <figref>10</figref> be measured. Similarly, the smart process object for the Sensormeßwandler<figref>89</figref> with the actual sensor in the level tank <figref>88</figref> concerns, coupled and receives the measured values ​​of which exported. Similarly, a smart process object for the tank<figref>88</figref> with each of the smart process objects for Durchflußmeßwandler <figref>84</figref>. <figref>90</figref>. <figref>101</figref> and <figref>108</figref> and the smart process object for the level sensor <figref>89</figref> be communicatively coupled. The tank with the<figref>88</figref> connected intelligent interconnector, the direction of flow and upstream and Abstromstellen denote that the Durchflußmeßwandlern <figref>84</figref>. <figref>90</figref>. <figref>101</figref> and <figref>108</figref> assigned. A method that in the smart process object for the tank<figref>88</figref> stored or associated with, the data from the smart process objects for the transducers can <figref>84</figref>. <figref>90</figref>. <figref>101</figref>. <figref>108</figref> and <figref>89</figref> and heat exchanger <figref>86</figref> and <figref>92</figref> use to determine whether the tank <figref>88</figref> leaks or heat units loses (heat balance calculations). This method can be effective by first the (current, average, integral etc.) inflow into the tank<figref>88</figref> than the sum of the Durchflußmeßwandlern <figref>84</figref> and <figref>101</figref> determined measured flow rates and then held from the tank drain than the sum of the Durchflußmeßwandlern <figref>90</figref> and <figref>108</figref> measured flows is determined. The method can then the difference between these flow rates integrated over time as the amount of fluid to determine which tank the<figref>88</figref> is added (or subtracted). The method can determine next whether this change in the amount of fluid in the tank<figref>88</figref> over a period of time in the difference of the filling level of the tank <figref>88</figref> as measured by the level sensor <figref>89</figref> reflects. When the level rises above the given period of time, for example less than expected, then the the tank<figref>88</figref> detect associated method and bring the operator to indicate that any fluid from the tank <figref>88</figref> exits. Similarly, can be used on the basis of measured values ​​obtained to an increase in the level over the expected amount of addition, a faulty sensor or a faulty measuring device in this part of the plant<figref>10</figref> to detect or determine. This technique can also be used to obtain a redundancy of measurements to perform, for example, a cross-check of data measurements or other related measurements, so that actually more measurements are carried out than is absolutely necessary. Of course, any difference between the expected level and the measured level will be displayed to the operator as an error or an alarm such as a pre-alarm.

In another example, a smart process object for the pump <figref>72</figref> and Durchflußmeßwandler <figref>74</figref> are created and implemented. The smart process object for the pump<figref>72</figref> may be known to it with facilities within the tank farm and the Durchflußmeßwandler <figref>74</figref> is connected, and it can receive data from the smart process objects for these units. An intelligent process object for the pump<figref>72</figref> associated method, the data from the smart process object for the Durchflußmeßwandler <figref>74</figref> received and the variability of by the Durchflußmeßwandler <figref>74</figref> measured flow rate determined. (If desired, the intelligent process object for the Durchflußmeßwandler<figref>74</figref> associated method to determine the variability of this transducer, or an application within the transducer <figref>74</figref> itself, the variability of &lt;?page 13?&gt;determine transducer and this provision as data to the smart process object for the transducer <figref>74</figref> ) In each case. Deliver, if the variability of the transducer <figref>74</figref> exceeds a certain limit, set the method for the smart process object of the pump the operator of the high variability among discontinuation of an alarm such as a pre-alarm in knowledge. Of course, these are only a few methods that can be implemented to perform at the level of the operator interface functionality to states such as problems, errors, alarms, etc. within the plant<figref>10</figref> to detect, and other methods may also be provided and applied.

Furthermore, the execution engine <figref>48</figref> (May have separate execution machinery to implement displays and smart process objects associated methods and to implement Prozeßflußmodulen assigned Flußalgorithmen) implement Flußalgorithmen associated one or more Prozeßflußmodulen to mass balances, flow rates, etc. in the field of investment represented by these modules to calculate. The execution engine<figref>48</figref> can data or information to the other elements as part of this process within the process plant <figref>10</figref> provide, approximately at the process control modules, which in the controls <figref>12</figref> the plant <figref>10</figref> to run.

It is understood that the functionality of the smart process objects and Prozeßflußmodule in the operator workstation <figref>20</figref> is effective and not in the controllers, field devices, etc. in the system <figref>10</figref> must be downloaded and configured therein, which makes it easier to implement this functionality, consider to change, etc. In addition, it makes this functionality possible that provisions on system level easier than within the process devices, controllers, etc. are feasible because the information relating to the facilities at a system level, typically all of the operator workstation <figref>20</figref> in general, and for the execution engine <figref>48</figref> are available in particular, while this entire information not typically each controller and each field device within the process plant <figref>10</figref> is made available. to act, however, if it is advantageous, so a portion of the Prozeßflußmodulen associated logic such as basic elements in the facilities, equipment and control systems to be embedded within the process plant. The use of smart process objects allows the execution engine<figref>48</figref>, For example, automatically detect leaks and to generate alarms, without or with only minimal user-side configuration acts to flow and mass balances within the plant <figref>10</figref> to calculate and track losses within the plant <figref>10</figref> to trace and diagnostic options at a higher level for the plant <figref>10</figref> to provide.

If desired, methods or rules can be created and applied generically for various smart process objects and Prozeßflußmodule generally or on a system wide basis to losses, currents, variability, etc. within the plant <figref>10</figref> to detect and track as well as the detection of errors and other conditions within the plant <figref>10</figref> based on the configuration of the system <figref>10</figref>, As reflected in the smart process objects and Prozeßflußmodulen allow. These rules can be applied based on the type and nature of the smart process objects, the support material such as liquid, gas, electricity, etc., and the connections between the objects as defined by the connection matrix described above<figref>52</figref> or by any other information that the connections between the devices within the plant <figref>10</figref> defined, and thus the connections between the smart process objects.

<figref>5</figref> shows one possible way of integrating the execution engine <figref>48</figref> and Prozeßflußmodule characterized used within a process plant is associated with a distributed control strategy. As<figref>5</figref> shows the display class definitions are <figref>120</figref>As of the Prozeßflußmodulen for providing displays for an operator during the execution by the execution engine <figref>48</figref> are generated, the control system configuration database / programming tools <figref>122</figref> supplied, which can use these display class definitions in any desired manner within the control strategy documentation and organize. Prozeßflußalgorithmen<figref>124</figref> may be connected to these display class definitions prior to runtime point, and then the display class definitions and corresponding Flußalgorithmen be instantiated and the Prozeßflußmodul runtime environment <figref>126</figref> supplied (in the form of one or more embodiments machines <figref>48</figref> may be implemented in various operator workstations). The Prozeßflußmodul runtime environment<figref>126</figref> uses a download script parser <figref>128</figref> parsing the code during execution (ie the implementation of just-in-time object code conversion) and uses a rule-based execution engine <figref>130</figref> for executing Flußalgorithmen or other rule-based operations that are intended for display classes or bound by them. During this process the Prozeßflußmodul runtime environment can<figref>126</figref> with the control module runtime environment <figref>132</figref>That can be executed in controllers and field devices that are associated with the process, communicate to the data or information to the control module runtime environment <figref>132</figref> or to provide access to data or other information from the control module runtime environment <figref>132</figref> to take. Of course, the Prozeßflußmodul runtime<figref>126</figref> with the control module runtime environment <figref>132</figref> using any desired or preconfigured communication network such as the Ethernet bus <figref>24</figref> from <figref>1</figref>Communicate. Of course, other methods of integrating Prozeßflußmodule and smart process objects that have been discussed here are applied in a standard process control system or a process plant.

In the implementation, each part of the software described herein in any computer readable memory such as on a magnetic disk, a laser disk, or other storage medium, in a RAM or ROM of a computer or processor, etc. are stored. Similarly, this software can a user, a process plant or an operator workstation using any known or desired delivery method are supplied, for example, on a computer readable disk or other portable computer storage mechanism or over a communication channel such as a telephone line, the Internet, the World Wide Web, any other local area network or wide area network, etc. (which delivery is considered to be equal to or interchangeable with the supply of software by means of a portable storage medium). Furthermore, this software can be delivered either directly without modulation or encryption or may be modulated and / or encrypted using any suitable modulation carrier wave and / or encryption technique before being transmitted over a communication channel.

The present invention will be described with reference to certain examples, which are intended to be exemplary only and not intended to limit the invention, but for the expert it is apparent that changes, additions, or omissions may be made to the described embodiments without departing from the scope of the invention ,