JP2016530647A - Batch field device operation - Google Patents

Abstract

A computer-implemented method for configuring a plurality of field devices is provided. The method (240) includes defining a configuration template and mapping the configuration template to a plurality of field devices. The defined configuration template is automatically applied to the plurality of field devices. A method (300) for verifying field device configuration information is also provided.

Description

  Field devices, such as process variable transmitters, are used in the process control industry to remotely detect process variables. Field devices, such as process actuators, are used in the process control industry to remotely control process physical parameters such as flow rate, temperature, and the like. Process variables can be sent from the field device to the control room to provide information about the process to the controller. The controller may then send control information to another field device, such as an actuator, to change the process parameters. For example, information regarding the pressure of the process fluid can be sent to the control room and used to control the process, such as petroleum refining.

An intelligent field device is a field device that includes processing circuitry and performs digital communication over a process communication loop or segment. Examples of such digital process communication include process communication protocols such as Highway Addressable Remote Transducer (HART ™) protocol, FOUNDATION ^TM Fieldbus protocol, Profibus , WirelessHART (such as those according to IEC62591), etc. Additional examples of digital communications include communications over a MUX network, a Wireless Gateway network, a modem network, or other suitable digital communications network. These intelligent field devices are more complex than the analog field devices they are replacing. However, intelligent field devices can provide additional information and control functions compared to analog 4-20 mA field devices.

  Before intelligent field devices can be used on a process communication loop or segment, they are properly configured to efficiently communicate valid process data to the control system, programmable logic controller, and / or remote terminal unit. Must be. Field devices also provide valuable diagnostic information regarding their normal operability and normal operability of the process. In order to take advantage of this functionality and avoid false alarms, it is important to set the diagnostic function and alarm level correctly. However, setting up intelligent field devices can be a time consuming and error prone process. Given such a large processing plant, a plant where hundreds if not thousands of intelligent field devices can be used to control, monitor and maintain production processes within safety limits The required effort is unusual.

  Historically, intelligent field devices have been under handheld communication devices such as the model name Model 475 Field Communicator available from Emerson Process Management in Austin, Texas. It has been set individually using what is sold. Instead, intelligent field devices were also individually configured using configuration software such as that sold under the trade name AMS Device Manager available from Emerson Process Management.

  A computer implemented method for configuring a plurality of field devices is provided. The method includes defining a configuration template and mapping the configuration template to a plurality of field devices. The defined configuration template is automatically applied to a plurality of field devices. A method for verifying field device configuration information is also provided.

1 is a schematic diagram of a process control and monitoring system employing a number of intelligent field devices in which embodiments of the present invention are particularly useful. FIG. 3 is a schematic diagram of operator interaction with an asset management system for performing a collective operation of a plurality of field devices according to an embodiment of the present invention. 3 is a flowchart of a method for collectively setting intelligent field devices according to an embodiment of the present invention. FIG. 6 is an example screen of a user interface that allows a user to define a configuration template that can be applied to multiple field devices, according to an embodiment of the present invention. FIG. 4 is an example screen of a user interface that allows a user to create a mapping between user settings and one or more respective field devices, according to an embodiment of the present invention. 6 is a screen example of a user interface that enables a user to perform a batch operation on a plurality of field devices according to an embodiment of the present invention. FIG. 4 is a schematic diagram of a method for verification and / or authentication of intelligent field device setting information according to an embodiment of the present invention. 4 is an example screen of a user interface that allows a user to select settings for creating a report, according to an embodiment of the invention. It is an example of a user interface screen that provides device parameter search results related to a batch search operation applied to a plurality of field devices according to an embodiment of the present invention. FIG. 3 is a schematic diagram of one exemplary computing environment in which the asset management system shown with respect to FIG. 2 may be incorporated.

  Embodiments of the present invention generally provide a template or generic configuration that defines configuration information for a plurality of intelligent field devices of the same type, and the template is connected to one or more connected and activated intelligent field devices or virtual devices. A method is provided for application to equipment (eg, placeholders set during process plant planning). In such a project, many such virtual field devices can be identified with similar device configurations. Accordingly, the embodiments provided herein provide a way for a user employing an asset management system to configure multiple intelligent field devices substantially simultaneously. By adopting such a template, user enterprise standards can be easily defined and implemented on a process plant basis, across plants, across enterprises.

  Two different batch operations are described below. A first batch operation is provided for configuring a plurality of intelligent field devices based on a user configuration template. A second batch operation is provided to allow the user to perform field device verification and validation based on the user configuration template. However, those skilled in the art will recognize that additional bulk field device operations may be performed by the various embodiments described herein.

  FIG. 1 is a schematic diagram of a process control and monitoring system in which embodiments of the present invention are particularly useful. The process control and monitoring system 10 includes one or more process controllers 11 connected to one or more host workstations or computers 13 (which may include any suitable computing device) having a user interface with a screen and input devices. Is included. Process controller 11 is coupled to intelligent field devices 16-22 through appropriate input / output cards or modules. The process controller 11 may be any suitable process controller. The process controller 11 and other communication interface devices shown in FIG. 1 are communicatively coupled to the host workstation 13 via an Ethernet connection or any suitable data communication protocol. The process controller 11 is also communicatively coupled to the intelligent field devices 16-22 using a suitable smart communication protocol, such as FOUNDATION ™ fieldbus protocol, HART ™ protocol, or the like. Further examples of digital communications include MUX networks, Wireless Gateway networks, modem networks, or other suitable digital communications protocol communications.

  Intelligent field devices 16-22 can be any suitable intelligent field device, such as a process variable transmitter, valve, positioner, and the like. The input / output card or module may be any suitable type of equipment that follows standard process communication protocols. For example, one I / O card can be a HART ™ I / O card that communicates with intelligent field devices 16, 17, 18 according to the HART ™ protocol. Further, another I / O card or module is FOUNDATION ™ that allows the process controller 11 to communicate with intelligent field devices 19, 20, 21, and 22 according to the FOUNDATION ™ fieldbus protocol. A fieldbus card may be used.

  The process controller 11 implements or monitors one or more process control routines (stored in memory) and controls the intelligent field devices 16-22 and the host computer 13 to control the process in some desired manner. Includes a communicating processor. Thereby, the process controller 11 or other suitable communication interface allows the workstation 13 to interact with the process via the intelligent field devices 16-22. The process controller 11 and any I / O modules employed therein are shown as one exemplary environment in which communication with multiple field devices occurs. However, embodiments of the present invention may be implemented in any environment where digital communication with multiple field devices is possible through any suitable interface.

  FIG. 2 is a schematic diagram of user interaction with the asset management system 200 for performing bulk field device operations, according to one embodiment of the present invention. The asset management system 200 generally runs one or more software applications running on one or more workstations 13 to provide a high level of interaction between the user and individual intelligent field devices of the process control and monitoring system. Contains. Such high level interactions include diagnostics, maintenance, configuration, etc. While workstation 13 may have one or more locally executing asset management system applications, embodiments of the present invention include user interaction with remote asset management system 200 via a data communication network. It is out. In this manner, the user 202 seated at the workstation 13 interacts with the asset management system 200 to perform various high-level functions for the intelligent field device 204 regardless of the physical location of the user 202. be able to.

  In accordance with an embodiment of the present invention, the user 202 generates a user settings process 206 in which the user provides templates / user settings and instances of intelligent field devices, as shown schematically at reference numeral 208. be able to. A user setting is a set of device parameters customized by the user to be used as a model for other device configurations. In addition, the user 202 can provide additional inputs, such as a “no download” list and a “no matching” list. These are lists of intelligent device parameters that are exempt from the batch operation application. Once the user 202 provides the request information, the user settings are stored in the database in some suitable format. In the embodiment shown in FIG. 2, the user settings are stored in the asset management system database 210. Next, the user 202 defines a mapping for the defined user settings. This is another suitable data structure that links files or the user settings to individual device tags or identifiers of intelligent field devices. This is indicated by reference numeral 212 in FIG. Next, the user 202 performs a batch operation as indicated by block 214.

  In the embodiment shown in FIG. 2, the batch operation is a batch transfer of user configuration information to a plurality of field devices. The batch operation takes as input the no download / no match list 216, the mapping file generated in block 212, and the defined user configuration stored in the asset management system database 210. However, embodiments of the present invention may be implemented where the database is a database of a suitable control system. The batch transfer process 214 then provides a device tag mapping 218 that is also preferably stored in a number of user settings and asset management system databases 210 as output. Furthermore, the batch transfer utility can transfer user setting data to one or more placeholders 220 in the process controller 11. Finally, as indicated by block 222, the user 202 is involved in the equipment activation process. When this occurs, the asset management system 200 receives the user setting and device tag mapping stored from the asset management database 210 and automatically sends the user setting information to the device tag described in the mapping 218. Applies to intelligent field devices that have matching device tags. In this way, the user engages with the process of automatically setting up a significant number of field devices without having to address each intelligent field device individually.

  FIG. 3 is a flowchart of a method for batch setting of intelligent field devices according to an embodiment of the present invention. The method 240 begins at block 242, where a user (eg, user 202) generates a user configuration template. In creating the template, the user can easily define and implement appropriate corporate standards across individual processing plant units, across processing plants, or across the enterprise. At block 244, the user generates a mapping table of the template or templates defined at block 242 to one or more intelligent field devices. An intelligent field device may be defined by any suitable identifier, such as a device tag or some other suitable identifier. In addition, the mapping can be stored in any suitable format, such as a Microsoft Excel spreadsheet or any suitable data structure. Next, at block 246, batch transfer of configuration information is initiated in the asset management system. At block 248, collective operation of field devices is performed, where each individual field device comprises setting information stored in a user template that is mapped to that individual field device. While batch operation of field devices can occur simultaneously, it can also occur sequentially unless another user interaction is required as a batch operation step through each intelligent field device. Thus, from the user's point of view, a single command to perform collective operation or configuration of intelligent field devices is an operation that is automatically performed either in parallel or in series on a specified intelligent field device. become.

  FIG. 4 is an example screen of a user interface that allows a user to generate one or more user settings according to an embodiment of the present invention. The user interface 250 has a user setting name field 252 under which two different user settings are listed. Specifically, uc1 and uc2 are shown. In addition, an interactive screen 254 is shown that allows the user to set block transfers for the selected user settings (in this case uc2). A number of parameters and Windows 256 that receives values for such parameters are displayed. Once the user has entered user settings for batch transfer or otherwise set, the user settings can be saved via button 258.

  FIG. 5 is an example of a screen for mapping user settings to device tags according to an embodiment of the present invention. In example screen 260, a number of user settings are displayed in column 262, while a number of device tags are displayed in column 264. In the mapping shown in FIG. 5, each row (for example, row number 2) is an association between a specified user setting and a device tag listed in the list. For example, in the highlight row 7, the user setting “UC_Name — 1” is associated with “Device_Tag — 6”. However, as noted above, the mapping between one or more intelligent field devices and a given user configuration may be provided in any suitable form. In the embodiment shown in FIG. 5, the mapping is a document, for example, under a spreadsheet, eg, Excel, available from Microsoft Corporation of Redmond, Washington. Provided in what is sold to.

  FIG. 6 is a schematic screen example of a user interface that allows a user to start a batch operation on a plurality of field devices according to an embodiment of the present invention. The example screen 270 includes a “device search” window 272 that lists or otherwise lists the various intelligent field devices supported by the AMS suite: Intelligent Device Manager 273. As shown, these intelligent field devices can be enumerated hierarchically based on plant location, individual plant, and individual equipment. The example screen 270 also shows an interaction window 274 provided to begin collective operation of the same type of intelligent field device. The dialog window 274 includes a file name field 276 that identifies one or more defined user configuration template files for various field devices. In addition, the dialog window 274 may include a worksheet name field 278 that defines the worksheet in a file having mapping information. However, as noted above, any suitable data structure or file format can be used for the mapping function. Next, field 280 is provided to allow the user to define the portion of the mapping that should be excluded. For example, row 1 may contain a header and thus no user settings and field device mapping. Thus, exempting row 1 from batch operations guarantees robust execution of the operation by defining the starting row as row 2. The interaction window 274 also includes a device column field 282. This field 282 allows the user to specify a particular column in the worksheet within field 278 of file 276 that contains a particular intelligent field device identifier, eg, device tag. Similarly, field 284 allows the user to specify the user settings field. In the example shown in FIG. 6, the user setting column is selected as column A, while the device column is selected as column B. Returning to the screen example of FIG. 5, the user setting information is described in the column A, while the device tag information is described in the column B. In addition, row 1 of the worksheet shown in the example screen 260 includes header information and thus should not be executed during the operation. Therefore, the batch transfer information entered in the dialog window 274 is appropriate for the mapping file shown for FIG.

  FIG. 7 is a schematic diagram of a method for performing a collective verification operation and / or a collective authentication operation for a plurality of intelligent field devices according to an embodiment of the present invention. Before the method 300 begins execution by the reporting tool 302, a number of preliminary steps are required, as described in block 303. In particular, one or more user configurations must be defined for each one or more individual intelligent field devices. In addition, each intelligent field device must be mapped to a user configuration. In addition, the user configuration must be applied to the mapped intelligent field device, and the intelligent field device must be activated by user settings. Accordingly, the preliminary process shown at block 304 is essentially represented above in the embodiment described with respect to FIGS.

  The reporting tool 302 provides an efficient way for a user to verify that intelligent field devices are set up according to the user configuration specified for each respective intelligent field device. In this way, the user does not need to communicate with each intelligent field device to provide such authentication. As can be appreciated, verifying device configuration settings for hundreds or thousands of intelligent field devices using conventional methods is a waste of time. Thus, employing method 300 significantly reduces the time required to provide such verification.

  The method 300 begins at block 304 where a single user selects one or more user configurations defined within the asset management system. As described above, these user configurations are defined by the user and are typically stored in the asset management database 210. At block 306, the reporting tool 302 exports one or more selected user-configured configuration data and mapped devices from the asset management system. At block 308, the configuration data is imported into the reporting database 310 or another suitable storage facility. Alternatively, configuration data can be retrieved from live field devices and imported into a standard format, such as XML. At block 312, the configuration data for each intelligent field device is compared to that specified in the user configuration template that can be applied, and a report is generated identifying discrepancies and / or incorrect settings. If there are any incorrect settings, as determined at block 314, the user is prompted at block 316 to correct the configuration settings for the specified intelligent field device. Once such a correction is made, the reporting tool 312 repeats the method by returning to block 304, as indicated by line 318.

  FIG. 8 is an example screen shot of a user interface that allows a user to select one or more user configurations to create a report according to an embodiment of the present invention. Screen example 350 includes a column 352 listing a number of defined user configurations adjacent to each check box 354. The user selects one or more of the listed user configurations by placing a check or x in box 354 adjacent to the desired user configuration. Once one or more user configurations have been selected, the user can initiate the reporting process by pressing the generate button 356. The example screen 350 also lists the reports in which the user interface was generated for the different user configurations in column 360, and the date and time that each respective report was created in column 362. A window 358 is included. Further, the status of each report is given in column 364. As shown in FIG. 8, reporting for user configuration 1 and user configuration 2 is in progress, while reporting for user configurations 3-7 is complete. For each report that is generated, all of the reports can be viewed by pressing the “View All” button 366. For convenience, the user can simply desire a display between the configuration information described in each intelligent field device and the specified one in the user configuration that can be applied by pressing the “View Differences” button 368. . When the report is generated, the user configuration and device configuration data of the mapped intelligent field device will be displayed in a single table in one embodiment. Reporting may include the ability to view, compare, and retrieve device configuration data and quickly identify devices that have “incorrect” device configuration settings. Thus, the embodiments provided herein allow users to efficiently compare hundreds of intelligent field devices at once, while ensuring plant compliance and enterprise technical standards.

  FIG. 9 is a screen example of a device parameter search result according to an embodiment of the present invention. Screen example 380 shows two devices (V11RZ2C02CH01 and V11RZ2C0ZCH02) compared with user configuration (template) UC2-FF. In addition, device parameters that meet one or more search criteria defined for the report are shown in various columns placed in the example screen 380. This allows the user to quickly identify intelligent field devices that may have incorrect device configuration settings, as described above.

  FIG. 10 is a schematic diagram of one computing environment in which one or more applications of the asset management system may be executed. Further, it is explicitly indicated that the asset management system may comprise multiple computing devices that cooperate or individually execute one or more individual software applications within the asset management suite. With reference to FIG. 10, one exemplary system for implementing some implementations includes a general purpose computing device in the form of a computer 810. The components of the computer 810 may include a processing unit 820 (which may include a processor 114), a system memory 830, and a system bus 830 that couples various system components including the system memory to the processing unit 820. However, it is not limited to these. The system bus 821 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using various bus architectures. The memory and program described with respect to FIG. 2 may be employed in corresponding portions of FIG.

  Computer 810 illustratively includes a variety of computer readable media. Computer readable media can be any available media that can be accessed by computer 810 and includes both volatile and nonvolatile media, removable and non-removable media. By way of example, and not limitation, computer readable media can include computer storage media and communication media. A computer storage medium is different from and does not contain a modulated data signal or carrier wave. It is both volatile and non-volatile and removable and non-removable media implemented by any method or technique for storing information, eg computer readable instructions, data structures, program modules or other data A hardware storage medium including Computer storage media can be RAM, ROM, EEPROM, flash memory or another memory technology, CD-ROM, digital general purpose disc (DVD) or other optical disc storage, magnetic cassette, magnetic tape, magnetic disc storage or other magnetic storage device Or any other medium that may be used to store desired information and that may be accessed by computer 810. Communication media can embody computer readable instructions, data structures, program modules, or other data in a transfer mechanism and includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal.

  The system memory 830 includes computer storage media, such as read only memory (ROM) 831 and random access memory (RAM) 832, in the form of general purpose and / or non general purpose memory. A basic input / output system 833 (BIOS) that includes basic routines that help to transfer information between elements within computer 810 is typically stored in ROM 831 during, for example, startup. The RAM 832 typically stores data and / or program modules that are directly accessible by the processing unit 820 and / or that are currently being operated on. By way of example and not limitation, FIG. 10 illustrates an operating system 834, application programs 835, other program modules 836, and program data 837.

  The computer 810 may also include other removable / non-removable, volatile / nonvolatile computer storage media. As an example only, FIG. 10 shows a hard disk drive 841 that reads from or writes to a non-removable, non-volatile magnetic disk 852, and a magnetic disk drive 851 that reads from or writes to a removable non-volatile magnetic disk 852. And a removable, non-volatile optical disk 856, such as an optical disk drive 855 that reads from or writes to a CD-ROM or another optical medium. Other removable / non-removable, volatile / nonvolatile computer storage media that may be used in the illustrated operating environment are magnetic tape cassettes, flash storage cards, digital universal disks, digital video tapes, semiconductor RAMs, and semiconductors Although ROM etc. are included, there is no intent to limit to these. The hard disk drive 841 is typically connected to the system bus 821 via a non-removable memory interface, eg, interface 840, and the magnetic disk drive 851 and optical disk drive 855 are typically removable memory interfaces, For example, the interface 850 is connected to the system bus 821.

  Alternatively or additionally, the functionality described herein may be performed at least in part by one or more hardware logic components. For example, without limitation, illustrative types of hardware logic components that can be used include field programmable gate arrays (FPGAs), integrated circuits for applications (ASICs), standard products for programs (PSSPs), systems Includes on-chip systems (SOCs), complex programmable logic devices (CPLDs), and the like.

  As discussed above and shown in FIG. 10, the driver and the associated computer storage medium comprise a storage of computer readable instructions, data structures, program modules, and other data relating to the computer 810. In FIG. 10, for example, hard disk drive 841 is shown as storage operating system 844, application program 845, other program modules 846, and program data 847. These components can be the same as or different from operating system 834, application programs 835, other program modules 836, and program data 837. Operating system 844, application program 845, other program modules 846, and program data 847 are given different numbers here to at least indicate that they are different copies.

  A user may enter commands and information into the computer 810 through input devices such as a keyboard 862, a microphone 863, and a pointing device 861, such as a mouse, trackball or touch panel. Another input device (not shown) may include a joystick, game pad, scanner, or the like. These and other input devices are frequently connected to the processing unit 820 through a user input interface 860 coupled to the system bus, but other interfaces and bus structures, such as parallel ports, game ports or general purpose serial buses ( USB). An image display 891 or another type of display device is also connected to the system bus 821 via an interface, such as a video interface 890. In addition to the monitor, the computer may also include other peripheral output devices, such as speakers 897 and a printer 896, which can be connected through an output peripheral interface 895.

  Computer 810 operates in a network environment that uses logical connections (eg, local area network-LAN or wide area network-WAN) to one or more computers, eg, remote computer 880. When used in a LAN networking environment, the computer 810 is connected to the LAN 871 through a network interface or adapter 870. When used in a WAN network environment, the computer 810 typically includes a modem 872 or WAN 873, eg, another means for establishing communications over the Internet. In a networked environment, program modules can be stored on a remote memory storage device. FIG. 10 shows, for example, that a remote application program 885 exists on the remote computer 880.

Claims (22)

A computer-implemented method for configuring a plurality of field devices, the method comprising:
Defining configuration templates,
Mapping the configuration template to a plurality of field devices;
Automatically applying the defined configuration template to the plurality of field devices;
Including,
A method implemented in the computer.   The computer-implemented method of claim 1, wherein defining a configuration template includes receiving a set of device configurations to be used as a model for a plurality of device configurations through a user interface.   The computer-implemented method of claim 1, wherein the defined configuration template is stored in a database.   The computer-implemented method of claim 3, wherein the database is an asset management system database.   The computer-implemented method of claim 3, wherein the database is a control system database.   The computer-implemented method of claim 1, wherein mapping the configuration template to a plurality of field devices includes generating an association between the name of the configuration template and a single field device identifier.   The computer-implemented method of claim 6, wherein at least one of the plurality of field devices is a virtual field device.   The computer-implemented method of claim 6, wherein the only field device identifier is a device tag.   The computer-implemented method of claim 6, wherein associations between the plurality of field devices and the configuration are individually listed in a document.   The computer-implemented method of claim 9, wherein the document is a spreadsheet.   Applying the defined configuration to the plurality of field devices automatically engages the device operation process of the asset management system for applying the configuration to each field device according to the defined configuration template. The computer-implemented method of claim 1, comprising:   The computer-implemented method of claim 1, wherein the method is implemented in an asset management system. A computer-implemented method for verifying configuration information of a plurality of field devices, the method comprising:
Access the configuration template,
Accessing a map associating the configuration template with a plurality of field devices, and automatically comparing information stored in the configuration template with field device configuration information for each field device mapped to the configuration;
With
A method implemented in the computer.   The computer-implemented method of claim 13, wherein the configuration template includes a set of device configurations that serve as a model for a plurality of field device configurations.   The computer-implemented method of claim 13, wherein the method is performed by a reporting tool.   The computer-implemented method of claim 13, further comprising generating a report specifying configuration information for each field device.   The computer-implemented method of claim 16, further comprising receiving search criteria for the report and providing responsive search results based on the search criteria.   The computer-implemented method of claim 16, further comprising providing a status identifier for the report.   14. The computer-implemented method of claim 13, further comprising creating a report that points out incorrect configuration information for each field device. A system,
Processor,
A storage device coupled with the processor;
A user interface component configured to generate a user interface for receiving a user configuration template and a map relating the user configuration template to a plurality of intelligent field devices;
And the processor is configured to automatically perform operations on each field device defined in the map based on the defined user configuration template.
Above system.   21. The system of claim 20, wherein the operation is a field device activation operation.   The system of claim 20, wherein the operation is a field device verification operation.