EP2011009A2 - Procédé et interfaces utilisateur de configuration de soutien pour rationaliser l'installation de dispositifs de terrain de remplacement - Google Patents

Procédé et interfaces utilisateur de configuration de soutien pour rationaliser l'installation de dispositifs de terrain de remplacement

Info

Publication number
EP2011009A2
EP2011009A2 EP07760328A EP07760328A EP2011009A2 EP 2011009 A2 EP2011009 A2 EP 2011009A2 EP 07760328 A EP07760328 A EP 07760328A EP 07760328 A EP07760328 A EP 07760328A EP 2011009 A2 EP2011009 A2 EP 2011009A2
Authority
EP
European Patent Office
Prior art keywords
field device
instance
field
configuration
type
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
EP07760328A
Other languages
German (de)
English (en)
Other versions
EP2011009A4 (fr
Inventor
Scott S. Bump
Nestor J. Camino, Jr.
Validimir Kostadinov
Charles W. Piper
Richard L. Linscott
Johan I. Tegnell
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Schneider Electric Systems USA Inc
Original Assignee
Invensys Systems Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US11/403,228 external-priority patent/US20070078540A1/en
Priority claimed from US11/403,224 external-priority patent/US8527888B2/en
Priority claimed from US11/403,226 external-priority patent/US8799793B2/en
Application filed by Invensys Systems Inc filed Critical Invensys Systems Inc
Publication of EP2011009A2 publication Critical patent/EP2011009A2/fr
Publication of EP2011009A4 publication Critical patent/EP2011009A4/fr
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B19/00—Programme-control systems
    • G05B19/02—Programme-control systems electric
    • G05B19/418—Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS], computer integrated manufacturing [CIM]
    • G05B19/41845—Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS], computer integrated manufacturing [CIM] characterised by system universality, reconfigurability, modularity
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/30—Nc systems
    • G05B2219/31—From computer integrated manufacturing till monitoring
    • G05B2219/31121—Fielddevice, field controller, interface connected to fieldbus
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/30—Nc systems
    • G05B2219/31—From computer integrated manufacturing till monitoring
    • G05B2219/31132—FDT interfacing profibus field device drivers DTM with engineering tool
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/30—Nc systems
    • G05B2219/31—From computer integrated manufacturing till monitoring
    • G05B2219/31334—Database with devices, configuration, of plant
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/30—Nc systems
    • G05B2219/32—Operator till task planning
    • G05B2219/32137—Configure, connect, combine different program modules
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/30—Nc systems
    • G05B2219/32—Operator till task planning
    • G05B2219/32144—Define device description using dd files
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/02—Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]

Definitions

  • This invention relates generally to networked computerized industrial process control systems and, more particularly, relates to maintenance/replacement of intelligent field devices (e.g., transmitters, positioners, etc.) within such process control systems.
  • intelligent field devices e.g., transmitters, positioners, etc.
  • Data acquisition begins when a number of sensors measure aspects of an industrial process and periodically report their measurements back to a data collection and control system.
  • Such measurements come in a wide variety of forms and are used by industrial process control systems to regulate a variety of operations, both with respect to continuous and discrete manufacturing processes.
  • the measurements produced by a sensor/recorder include: a temperature, a pressure, a pH, a mass/volume flow of material, a quantity of bottles filled in an hour, a tallied inventory of packages waiting in a shipping line, or a photograph of a room in a factory.
  • Typical industrial processes today are extremely complex and comprise many intelligent transmitters and/or positioners.
  • sensors and control elements e.g., valve actuators
  • These sensors and control elements are subject to wearing out and/or failing over time.
  • a replacement field device often of same model and version, is installed in place of the failing/worn field device.
  • transmitters and positioners were comparatively simple components.
  • More contemporary field devices that include digital data transmitting capabilities and on-device digital processors referred to generally as "intelligent" field devices, require significantly more configuration effort when setting up a new field device to replace a previously existing field device - to match the application within which the existing device is used.
  • a set of parameters are set, within the new/replacement device, at either a device level (HART, PROFIBUS, FoxCOM, DeviceNet) or a block level within the device (FOUNDATIONTM fieldbus).
  • Replacing complex, intelligent devices requires the person performing the replacement activity to possess considerable knowledge of the specific device that is being replaced. Furthermore, during replacement a previously (bench) calibrated replacement field device is potentially disabled. The disabled replacement field device must be re-calibrated - which may require highly-specialized equipment and well trained technicians. In view of the significant consequences associated with disabling a field device during installation, users are generally informed regarding the following: parameters that must not be changed during device configuration; and parameters that configuration tools (software) adjust in response to particular configuration actions taken by the user.
  • the mere replacement of an existing field device with a field device having a same set of configurable parameters is still an operation requiring a relatively high degree of skill and knowledge by the person performing the replacement.
  • Such device-specific knowledge includes, but is not limited to, identifying a set of parameters that must be configured as well as parameters (e.g., calibration values) that must not be modified during configuration/installation.
  • the installer must potentially know specific methods/operations that need to be executed before a replacement device is fully operational in a particular application environment.
  • a method for replacing a previously configured device having corresponding parameters is described herein.
  • a method is presented wherein a set of parameters that require configuration during replacement of a particular type of field device are specified.
  • An application engineer/technician specifies, for a first instance of the particular type of field device, appropriate values for the set of parameters.
  • the values for the set of parameters are stored within a repository of device instance configuration information within a process control network.
  • a maintenance technician replaces the first instance of the field device with a second instance of the particular field device type on the process control network.
  • the technician invokes an automated device replacement operation, for downloading to the second field device instance the values for the set of parameters previously specified for the first instance and stored in the repository of device instance configuration information.
  • the technician invokes the operation through a simple user interface action such as, for example, selecting a Commissioning Operation.
  • process control network/system maintenance engineers and technicians who are generally assigned the task of performing final device setup or replacement in the field, are provided a tool for accelerating and simplifying the process of replacing a field device instance with another one of the same type (i.e., utilizing a same set of configurable/programmable parameters).
  • the above-described method and components facilitate streamlined device replacement by technicians having limited knowledge of configurable parameter values associated with replaced devices.
  • human error possibilities are significantly reduced in regard to setting configurable parameters on the replacement field devices.
  • Figure 1 is schematic diagram depicting an exemplary process control network environment wherein the present invention is potentially incorporated;
  • FIG. 2 is an exemplary user interface that displays a set of parameters associated with a particular type of field device
  • FIG. 3 is an exemplary user interface for configuring/customizing a Device
  • FIG. 4 is a flowchart summarizing a set of steps for creating a Device Commissioning configuration definition for a particular field device instance in a process control network
  • FIG. 5 is a flowchart summarizing a set of steps in accordance with an exemplary method for conducting a Device Commissioning operation wherein a replacement field device is initially configured in an instrument shop;
  • FIG. 6 is an exemplary user interface for selecting from an extensible set of operations involving replacement of a field device with another field device of a same type
  • FIG. 7 is a flowchart summarizing a set of steps in accordance with an exemplary method for conducting a Device Commissioning operation wherein a replacement field device is configured in the field.
  • a field device maintenance application comprising a set of components.
  • the set of components includes, by way of example, a user interface supporting invoking a device replacement operation; a user interface supporting user configuration of device type-specific replacement steps; a device description (DD) interpreter that facilitates presenting details associated with a particular device configuration; an automated field device replacement function that executes a device replacement script for a particular field device; a communications interface supporting transmitting configuration values to specified replacement field devices; a replacement progress monitor to verify successful completion of each step of the replacement process; and a user interface that displays the status of the replacement process and allows users to control the replacement process.
  • DD device description
  • the above-described set of components facilitate installing a replacement field device by merely identifying an instance-specific identification of the replaced field device having configuration information previously stored in a configuration archive to which an automated replacement field device application has access.
  • a workstation 102 comprising a variety of field device configuration and monitoring applications, provides an operator/engineering interface through which an engineer/technician monitors the components of an industrial process control system.
  • the workstation 102 comprises any of a variety of hardware/operating system platforms.
  • the workstation 102 comprises a personal computer running any of a variety of operating systems such as: Microsoft Windows, UNIX, Linux, Solaris, Mac OS-X, etc.
  • the workstation 102, device definition database 107 and application database 109 are connected in a redundant configuration via dual
  • Ethernet interfaces/wiring to redundant switches 104 and 106 The Ethernet switches 104 and 106 are commercially available and provided, for example, by Allied Telesyn (e.g., model AT-8088/MT). While not specifically depicted in FIG. 1, additional nodes, comprising workstations, servers and other elements (e.g., control module assemblies) of a supervisory portion of the process control system are potentially connected to the redundant switches 104 and 106.
  • a device definition database 107 and application database 109 store information regarding device types (templates) and device instances, respectively.
  • ETHERNET local area network links are depicted in FIG. 1 , such links over a local supervisory level process control network are alternatively carried out via wireless network interfaces.
  • the switches 104 and 106 are also communicatively coupled to a control module assembly 108.
  • the control module assembly 108 comprises one or more control modules (also referred to as control processors).
  • An illustrative example of such control module is a Foxboro CP model FCP270, by Invensys Systems, Inc.
  • process control functionality is carries out in any of a variety of control modules - even by control programs incorporated into the workstations, intelligent transmitters, or virtually any communicatively coupled device capable of executing control programs, loops, scripts, etc.
  • an I/O module assembly 110 is connected to the control module assembly 108.
  • the communications protocols utilized for carrying out communications between the I/O module assembly 110 and control module assembly 108 is potentially any one of a variety of proprietary/non-proprietary communications protocols.
  • the communications between the control module assembly 108 and I/O module assembly 110 are carried out via a 2 MBit HDLC communication bus. While only a single I/O module assembly 110 is depicted in the illustrative example, embodiments of the invention comprise many I/O module assemblies.
  • the I/O module assemblies in general, include a variety of interfaces for communicating directly and/or indirectly to a variety of devices including, for example, field devices.
  • the I/O module assembly 110 comprises a Foundation Fieldbus I/O module (e.g., an Invensys field bus module model FBM228) that supports communications between the control module assembly 108 and a Foundation Fieldbus network 111.
  • a set of representative intelligent field devices 114 and 116 containing multiple application-dependent configurable parameters, are connected to the Foundation Fieldbus network 111.
  • the field devices 114 and 116 operate at the lowest level of an industrial process control system to measure (transmitters) and control (positioners) plant activity.
  • a Termination Assembly 112 communicatively couples the I/O module assembly 110 to the field devices 114 and 116.
  • the termination assembly 112 provides power and power conditioning to the extent needed by the field devices 114 and 116 on the network 111.
  • the configuration of the Device Commissioning, and the commissioning step itself, is executed from the workstation 102.
  • the process control network schematically depicted in FIG. 1 is greatly simplified for purposes of illustration. Those skilled in the art will readily appreciate that both the number of components, at each depicted level of the exemplary process control system, is generally many times greater than the number of depicted components. This is especially the case with regard to the number of depicted field devices. In an actual process control environment, the number of field devices, comprising both input devices (e.g., transmitters) and output devices (e.g., positioners) number in the hundreds for an industrial process control system.
  • input devices e.g., transmitters
  • output devices e.g., positioners
  • an illustrative parameter display interface depicts a partial set of parameters associated with an instance of an intelligent field device.
  • the parameters potentially exist at both the device level and within block structures associated with the particular intelligent field device instances.
  • the parameters are generally defined by a data type and a value corresponding to the data type.
  • parameter instances potentially are associated with a status or data quality indication.
  • the device parameters could be any of a number of parameters including parameters for:
  • an aspect of an illustrative embodiment of the replacement method described herein comprises a replacement set-up phase.
  • This portion of the setup- phase defines the Device Commissioning operation for all device instances of a common device type.
  • a parameters portion 300 of the user interface presents a set of configurable parameters. The user designates, by selecting parameters from the parameters list, parameters which can be modified during device configuration and moving them to a writeable parameters portion 301 of the user interface. From the writeable parameters portion 301, the user selects parameters for automatic value specification from an archival copy during a Device Commissioning operation by setting them in a download list portion 302 of the user interface.
  • Device commissioning refers to a user invoking automatic setup, including filling of pre-designated parameter values, of a replacement field device by selecting a single operation.
  • the parameters in the download list portion 302 of the user interface correspond to the parameter for which a value will automatically be downloaded to the replacement field device.
  • the parameters selected for Device Commissioning represent parameter values that must be properly configured before a field device is fully operational.
  • a user interface such as the one depicted in FIG. 2, supports entry of values for the parameters in association with configuration of an original/first field device.
  • the relevant parameter values are extracted from the first field device or any other suitable storage location containing the first device's designated parameter values.
  • FIG. 3 depicts an exemplary set of parameters for which a set of values are stored to facilitate Device Commissioning/automatic downloading/replacement when the original/first field device instance is replaced by a second instance of a field device of the same type (supports a same set of parameters as those specified for Device Commissioning).
  • the user need only fill in the appropriate values for each parameter for the instance of the device.
  • devices may contain parameters which are not part of normal device configuration.
  • An exemplary set of such parameters are calibration parameters set in the device as part of calibration operations. For archival purposes these parameters must be read from the device as an upload step during Device Commissioning. In FIG. 3, the user specifies that device parameters will be read as part of Device Commissioning by selecting an upload parameters checkbox 303.
  • writing parameters to the device requires the device to be placed into the proper operational mode.
  • the user can select an automatic mode management option 304 to allow the Device Commissioning operation to automatically manage the device operational mode.
  • devices and their blocks are required to be in specific modes to allow parameter configuration. The objective of this feature is to minimize user interactions and the associated risk of human error.
  • FIG. 3 illustrates one type of interface that could be used to select the set of parameters that are automatically downloaded to a replacement device during Device Commissioning.
  • FIG. 3 illustrates one type of interface that could be used to select the set of parameters that are automatically downloaded to a replacement device during Device Commissioning.
  • the operations performed by the Commissioning function are not limited to loading previously archived parameter values onto a replacement field device. Rather, the replacement functionality comprises all aspects of configuring and bringing a replacement for a previously configured field device on-line.
  • FIG. 4 a flowchart depicts a set of steps performed for defining a field device replacement object template (stored in the device definition database 107) and creating a field device replacement object instance (stored in the application database 109), from the object template, corresponding to a specific field device installed on a process control network.
  • the replacement object While referred to herein as a "replacement" object, the replacement object potentially contains additional fields for describing a particular field device that facilitate a variety of additional functions associated with a specified field device instance.
  • the field device replacement object stored in the application database 109 facilitates streamlining the task of replacing a first field device, corresponding to a field device replacement object instance, by a second field device of the same type.
  • the setup steps are performed offline, before the original/first instance of a particular field device is rendered operational. In general, the setup steps are divided into two stages: (1) device type/application setup and (2) device instance setup.
  • a user During device type/application setup, a user, using a device definition tool (configurator), defines device objects for field devices of a particular type and application and stores the device object definitions within the device definition database 107 that is accessed by configuration components/editors.
  • a user opens a new device type definition in a device definition tool editor.
  • a user selects a new FIELDBUS FOUNDATION Device Description for a FIELDBUS FOUNDATION field device to add to the set of device types maintained in the device definition database accessible to a set of users seeking to configure field devices on a process control system depicted, by way of example, in FIG. 1.
  • step 402 the user proceeds to designate a set of parameters generally associated with the new device type definition (including a particular use of a field device) opened during step 400.
  • a user designates, via the device definition tool editor, one or more groups of parameters associated with a particular use of a particular field device (e.g., a pressure transmitter used to measure fluid level in a cylindrical tank).
  • One group (or subset) of the designated set of parameters comprises a Device Commissioning parameter set.
  • the Device Commissioning parameter set specifies parameters for which values from a first field device will be loaded into a second field device during execution of a Device Commissioning field device replacement operation described further herein below.
  • a user having administrator rights after designating the set of parameters during step 402, defines access privileges for all potential users that will seek access, through a field device configuration component/editor or any other applicable tool, to the new device type definition and the designated parameters contained therein.
  • the privileges ensure that only those with proper knowledge/rights are allowed to change the set of parameters associated with the device type definition.
  • a user defines potentially multiple copies/versions of the new device type defined during step 402.
  • Each version of the new device type is assigned a unique identification.
  • the versions facilitate specifying/defining new use-specific device types under the more general new device type.
  • the versions of a new device type share a common set of designated parameters. However, the initial values assigned to the versions differ based upon the particular use of the field device corresponding to the new device type definition.
  • a generally defined "differential pressure transmitter" device type is more specifically defined during step 406 for two distinct uses such as: (1) measuring fluid flow rate in a pipe and (2) measuring the level of a fluid in tank.
  • the versions of the differential pressure transmitter used to measure fluid level in a tank can be further distinguished based upon the shape/orientation of the tank.
  • Each use-specific version of the more generally defined device type (specified during step 402) is stored under a uniquely identified field device type definition to reflect differences between a set of initial values associated with the parameter sets for distinct uses of the identified field device.
  • the versions of the device type definition are stored in the device definition database 107.
  • the device type definitions stored in the form of device object templates, provide a structure for creating actual field device objects corresponding to actual field devices in a process control system.
  • a user creates a device object instance from the device type definition version (device template) previously stored during step 406 in the device definition database 107.
  • a user through a configuration component tool used to configure elements (e.g., field devices) of a process control system, creates a field device instance from the previously stored device type definition stored in the device definition database.
  • the field device instance is stored by the configuration component tool in the application database 109 comprising a set of application objects (including field device object instances) corresponding to components that make up a process control system application.
  • the configuration component tool is utilized to configure the field device instance created during step 408 for a particular application.
  • the use-specific field device object is customized for a particular application (actual installed field device) of a process control system.
  • the customized field device object is thereafter stored in the application database during step 412.
  • an instance of a field device object has been created and customized for a particular field device and contains all of the configuration information needed to define a field device.
  • the configuration information contains the information that facilitates a user subsequently completing a Device Commissioning field device installation as well as replacement of a previously installed field device. Such tasks are described further herein below.
  • Replacing a previously installed (first instance) field device with another (second instance) field device of the same type using streamlined "Device Commissioning" configuration techniques is potentially carried out in any of a variety of ways. Two such methods include: (1) pre-configuring a replacement field device in an instrument shop by performing "Device Commissioning” and then physically installing the replacement field device in a factory/plant floor environment to complete the configuration procedure (see FIG. 5), and (2) installing a non-configured replacement field device in the plant followed by performing "Device Commissioning" via a control system console user interface (see FIG. 7).
  • Both the first method and second method, identified above, incorporate "Device Commissioning" techniques that streamline replacing the first instance by the second instance using configuration information/settings stored in the application database 109 corresponding to the first instance of the field device.
  • FIG. 5 a sequence of steps are summarized for carrying out replacement of a FOUNDATION TM fieldbus device by initially setting up the replacement field device in an instrument shop (Device Commissioning) and thereafter physically installing the replacement field device in place of the old field device to complete the field device replacement procedure. These steps, in contrast to steps described herein below with reference to a Device Commissioning device replacement method (see, FIG. 7), are performed in-part in an instrument shop.
  • the replacement field device is communicatively connected to the network (e.g., one hosting the device definition database and application database) in an "instrument shop" environment comprising well known fixtures and network cabling to facilitate bench configuration of the replacement field device.
  • the technician initiates executing an automated Device Commissioning procedure 501.
  • an automated Device Commissioning procedure 501 By way of example, to invoke the Device
  • a user opens a configuration component interface (see, e.g., FIG. 6a) on a workstation or portable configuration tool.
  • the interface contains a list of field devices in a process control network.
  • the user selects an identified device from a displayed list of names corresponding to online field devices (filtered to present only devices coupled to a specified link/segment).
  • a user selects a particular Hl fieldbus link to view a set of connected, online fieldbus devices.
  • the user also selects a field device configuration definition (corresponding to the replaced field device) from the application database 109.
  • the user thereafter invokes the Device Commissioning procedure characterized by the set of exemplary steps 501 by, for example, selecting a Device Commissioning action option from a set of action options and then initiating the Device Commissioning action by actuating a graphical user interface button that becomes active once all the aforementioned Device Commissioning configuration options have been designated.
  • the Device Commissioning procedure commences, and an identification (ID) and network/communication address are set for the replacement field device to match the values from the device object in the database.
  • ID an identification
  • network/communication address are designated for the replacement field device.
  • the node address corresponds to the physical address of the field device when it is later installed in place of a replaced device in the field (e.g., on a plant floor).
  • FOUNDATION fieldbus devices contain individual function blocks that must be placed within special modes to allow configuration of the replacement field device, and such blocks enter these special modes during step 504.
  • configuration information corresponding to the device that is to be replaced, is retrieved from the application database 109 and used to configure parameters that govern the operation of program components executed within the replacement field device.
  • the retrieved configuration information corresponds to parameter values/settings (see, e.g., FIG. 3) for the field device that is to be replaced by the replacement field device.
  • the replacement device's transducer blocks and resource blocks are configured during step 506 based upon instance-specific values and settings associated with the replaced field device.
  • step 508 the operational state of the field device is restored to the state within which it existed before executing step 504.
  • block modes are reset to an operational state.
  • a final step 509 is performed to upload parameters from the device if that option was configured for the commissioning step.
  • the bench configured field device is now ready for installation on an operational process control network/system.
  • Step 509 completes the automated Device Commissioning procedure based upon a set of parameter values stored in a record (corresponding to the replaced field device) in the application database 109.
  • step 510 comprises issuing a command taking the old field device offline via a system management utility. Taking the old field device offline causes higher level control elements (e.g., a control processor or fieldbus module) to cease attempting to communicate with the old field device. Thereafter, at step 512 the old field device is physically disconnected from its field network link (e.g., Hl fieldbus segment/link). Physically disconnecting the old field device is by-passed when wireless communications are utilized by field devices to communicate with their respective fieldbus modules or other suitable higher level control elements (e.g., control processors).
  • a system management utility Taking the old field device offline causes higher level control elements (e.g., a control processor or fieldbus module) to cease attempting to communicate with the old field device.
  • the old field device is physically disconnected from its field network link (e.g., Hl fieldbus segment/link). Physically disconnecting the old field device is by-passed when wireless communications are utilized by field devices to communicate with their respective fieldbus modules or other suitable higher level control elements (
  • the replacement field device is physically connected to a field network segment (if not using wireless communications), such as an Hl fieldbus link, as well as any plant component (e.g., a tank) with which the replacement field device operates.
  • a field network segment if not using wireless communications
  • any plant component e.g., a tank
  • step 516 the replacement field device is brought online to facilitate communications between the replacement field device and other components of a distributed process control system.
  • step 516 comprises invoking a command identifying the replacement field device to be brought online.
  • step 516 comprises performing operations sufficient to register the replacement field device's presence on the field network link to which it was physically connected during step 514.
  • step 516 is fully automated. In other embodiments, user intervention is required to bring the replacement field device communicatively online.
  • step 518 device data (e.g., a field device serial number) that is unique to a specific instance of a particular field device type is uploaded from the replacement field device to the application database 109.
  • This data is generally distinct from data stored within the application database 109 that guides execution of the automated configuration operations performed during steps 506.
  • the user brings up a Comparison screen through which the user can determine the differences between the parameters in the field device and the parameters stored in the database.
  • An example of such a screen/utility is described in Bump et al., U.S. Patent Application Serial No.
  • FIG. 6a an exemplary configuration component graphical user interface is presented that facilitates invoking field device commissioning (see, e.g., FIG. 5, step 501) and uploading field device data to the application database 109 (see, e.g., step 509).
  • a maintenance graphical user interface launched via the configuration component depicted in FIG. 6a, includes a title bar 600.
  • a user selects a device from an Equipment Hierarchy tree 602 that corresponds to a device object instance (e.g., IASPTlO) in the application database 109.
  • a device object instance e.g., IASPTlO
  • a record is currently accessed that contains configuration parameters/values for a pressure transmitter assigned an identification text string "IASPTlO".
  • the transmitter identified as IASPTlO corresponds to a previously fully configured field device that has been (or soon will be) physically replaced on a process control field network by a replacement field device of the same type.
  • the field device record identified in object 602 is obtained through a tree interface that filters a list of potential device records according to a selected port/Hi link in a Foundation Fieldbus industrial process control network.
  • An action options list 604 of the exemplary user interface depicted in FIG. 6a enables a user to select from a set of automated operations relating to field device maintenance in a streamlined fashion.
  • the field device instances listed within a device candidates live list field 608 represent potential recipients/sources of parameter values and/or invoked methods - depending upon the option selected from the action options list 604 previously assigned to the device identified in object 602. In the illustrative embodiment of the invention, it is up to the user to select a proper device from a set of all field devices having enabled communications on a particular segment of a process control network connected to a field bus module port, identified in fieldbus segment box 610.
  • Each FBM has 4 separate ports.
  • the Port number is stored in the database and is illustrated on the Commissioning Dialog box 616.
  • its information line e.g., DEVICEl
  • a user invokes the selected task (i.e., commissioning the selected device) via Next button 614 after selecting a device instance from the list of device candidates via the exemplary configuration component user interface.
  • FIG. 7 an exemplary sequence of steps are summarized for directly replacing a field device on a plant floor (or other location in the field) - as opposed to performing initial setup in an instrument shop as described herein above with reference to FIG. 5.
  • a first field device is replaced by a second field device of the same type (having the same configurable parameters) using the "Device Commissioning" action option presented in the list of action options 604 described herein above with reference to FIG. 6a.
  • step 700 comprises invoking a command to take the field device offline.
  • step 702 the old field device is physically disconnected from its field network link (e.g., Hl fieldbus segment/link) and plant equipment. Physically disconnecting the old field device from the network is not performed when wireless communications are utilized by field devices to communicate with their respective fieldbus modules or other suitable higher level control elements (e.g., control processors).
  • embodiments of the invention contemplate automatically setting a field device to "offline" status in response to physically disconnecting the field device from a network link.
  • the user physically connects a non-configured replacement field device on the field network link (if not using wireless communications) to which the old field device was disconnected during the previous step.
  • the replacement field device is also connected to any plant component (e.g., a tank) with which the field device operates.
  • the user through the configuration component user interface depicted in FIG. 6a, initiates the Device Commissioning action operation (i.e., Commission) of the set of action options 604.
  • the automated Device Commissioning procedure 707 commences at step 708 wherein an identification (ID) and network/communication address for the replacement field device are specified for the replacement field device.
  • ID identification
  • network/communication address for the replacement field device are specified for the replacement field device.
  • the field device is a
  • FOUNDATION TM fieldbus device a PD Tag (ID) and Node (network) Address are designated for the replacement field device. These two values are utilized to reference the replacement field device on the field network during subsequent configuration and online runtime operations/communications. Thereafter continuing the automated Device Commissioning action, at step 710 the replacement field device is placed into a state or mode that permits configuration of the field device.
  • the replacement field device is placed into a state or mode that permits configuration of the field device.
  • the user/technician sets the blocks within such special modes.
  • step 712 configuration information previously stored within the application database 109 for the replaced field device is retrieved from the application database 109 and stored within appropriate configurable fields of the replacement field device that determine/configure the operation of the replacement field device.
  • parameter values are configured at a device level during step 712 while the replacement field device remains offline.
  • the replacement device's transducer blocks and resource blocks are configured during step 712.
  • step 714 function blocks that require communication with other components of the process control network (e.g., control processors) are configured in accordance with the automated steps of the Device Commissioning action invoked at step 706.
  • the function blocks are configured in accordance with values (see, e.g., FIG. 3) previously specified for the replaced field device and stored within the application database 109.
  • step 716 device data (e.g., a field device serial number) that is unique to a specific instance of a particular field device type is uploaded from the replacement field device to the application database 109.
  • the uploaded data is generally distinct from data stored within the application database 109 that guides execution of the automated configuration operations performed during step 506.
  • a unique manufacturer serial number assigned to the replacement field device is uploaded from the replacement field device to the application database 109.
  • Other instance-specific information, such as the installer, date/time of installation, etc. is also potentially uploaded during the device data upload step 716.
  • the Device Commissioning step automatically performs an "Upload Device Data" action if the Upload after Commissioning checkbox is set in Fig 3.
  • step 718 the operational states/modes of the field device's blocks are reset to the ones that existed before setting the configuration state of the replacement device at step 710. In the case of a FOUNDATIONTM fieldbus device, block modes are reset. At this point, the replacement field device is completely operational and setup to match the configuration of the replaced field device.
  • step 720 the replacement field device is brought online to facilitate communications between the replacement field device and other components of a distributed process control system.
  • step 720 comprises performing operations sufficient to register the replacement field device's presence on the field network link to which it is physically connected.
  • step 720 comprises invoking a command identifying the replacement field device.
  • steps 722 methods may be executed.
  • An example of such method is the "Auto-start" method on a field device.
  • One possible embodiment of method execution could be a user-configured method, or methods, that are automatically executed during device commissioning.
  • the steps described for device replacement can be applied to the initial commissioning of a plant. In the initial commissioning there is no failed device to replace, and therefore steps 700 and 702 are not performed.
  • Plant engineers connect all devices in the plant, or plant area to the system as a large scale step 704. When the plant or plant area is to be commissioned, the Device Commissioning action is performed on each device from a defined device instance in the application database. The commissioning action, starting with step 706 and continuing to the end, commissions the device to initiate plant operations.

Abstract

L'invention concerne un procédé et des interfaces utilisateur pour installer un dispositif de terrain destiné à remplacer un dispositif de terrain du même type installé antérieurement dans un système de commande de processus. Le procédé selon l'invention consiste notamment à spécifier initialement une définition de la mise en service du type de dispositif qui comprend un ensemble de paramètres spécifiques du type de dispositif. Un premier ensemble de valeurs paramétriques de configuration spécifique à l'instance est alors stocké pour un premier dispositif de terrain. Lors du remplacement du premier dispositif de terrain par un second dispositif de terrain du même type dans un réseau de commande de processus, la définition de la mise en service et les paramètres stockés précédemment pour le premier dispositif sont utilisés pour configurer automatiquement le second dispositif.
EP07760328A 2006-04-11 2007-04-09 Procédé et interfaces utilisateur de configuration de soutien pour rationaliser l'installation de dispositifs de terrain de remplacement Ceased EP2011009A4 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US11/403,228 US20070078540A1 (en) 2005-10-05 2006-04-11 Utility for comparing deployed and archived parameter value sets within a field device editor
US11/403,224 US8527888B2 (en) 2006-04-11 2006-04-11 Method and supporting configuration user interfaces for streamlining installing replacement field devices
US11/403,226 US8799793B2 (en) 2005-10-05 2006-04-11 Tool for creating customized user interface definitions for a generic utility supporting on-demand creation of field device editor graphical user interfaces
PCT/US2007/066244 WO2007121141A2 (fr) 2006-04-11 2007-04-09 Procédé et interfaces utilisateur de configuration de soutien pour rationaliser l'installation de dispositifs de terrain de remplacement

Publications (2)

Publication Number Publication Date
EP2011009A2 true EP2011009A2 (fr) 2009-01-07
EP2011009A4 EP2011009A4 (fr) 2011-06-29

Family

ID=38610315

Family Applications (2)

Application Number Title Priority Date Filing Date
EP07760328A Ceased EP2011009A4 (fr) 2006-04-11 2007-04-09 Procédé et interfaces utilisateur de configuration de soutien pour rationaliser l'installation de dispositifs de terrain de remplacement
EP07760453A Ceased EP2010991A4 (fr) 2006-04-11 2007-04-11 Outil d'édition de dispositif de terrain

Family Applications After (1)

Application Number Title Priority Date Filing Date
EP07760453A Ceased EP2010991A4 (fr) 2006-04-11 2007-04-11 Outil d'édition de dispositif de terrain

Country Status (3)

Country Link
EP (2) EP2011009A4 (fr)
CN (1) CN101460928B (fr)
WO (2) WO2007121141A2 (fr)

Families Citing this family (34)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE102008001886A1 (de) * 2008-05-20 2009-11-26 Endress + Hauser Flowtec Ag Verfahren zum Austausch von Parametrier- und Konfigurierdaten zwischen einem Konfigurier- oder Managementsystem und einem Feldgerät
DE102008043095A1 (de) * 2008-10-22 2010-04-29 Endress + Hauser Process Solutions Ag Verfahren zum Parametrieren eines Feldgerätes
US8832236B2 (en) 2010-06-21 2014-09-09 Fisher-Rosemount Systems, Inc. Methods, apparatus and articles of manufacture to replace field devices in process control systems
US9229947B2 (en) * 2010-09-27 2016-01-05 Fisher-Rosemount Systems, Inc. Methods and apparatus to manage process data
DE102010062908B4 (de) 2010-12-13 2012-10-31 Siemens Aktiengesellschaft Verfahren zum Parametrisieren eines Gerätes, parametrisierbares Gerät und Parametrisierungsvorrlchtung
DE102010055337B4 (de) * 2010-12-21 2021-12-16 Abb Ag Integration von Feldgeräten in ein verteiltes System
CN102148711B (zh) * 2011-04-08 2013-12-18 瑞斯康达科技发展股份有限公司 一种网络设备的备份方法和系统
US8713166B2 (en) 2011-05-31 2014-04-29 General Electric Company Systems and methods for facilitating communication with foundation fieldbus linking devices
US8868732B2 (en) 2011-05-31 2014-10-21 General Electric Company Systems and methods for facilitating communication with foundation fieldbus linking devices
US8762528B2 (en) 2011-05-31 2014-06-24 General Electric Company Systems and methods for write protecting foundation fieldbus linking devices
US9130853B2 (en) 2011-05-31 2015-09-08 General Electric Company Systems and methods for identifying foundation fieldbus linking devices
US8769072B2 (en) * 2011-05-31 2014-07-01 General Electric Company Systems and methods for identifying foundation fieldbus linking devices
US10185308B2 (en) * 2012-04-30 2019-01-22 Fisher Controls International Llc Methods and systems to provide update information of a device description of a field instrument
US9094299B1 (en) * 2013-01-08 2015-07-28 Juniper Networks, Inc. Auto-generation of platform-independent interface and operational scripts for configuring network devices
US9563188B2 (en) 2013-08-01 2017-02-07 General Electric Company Systems and methods for batch device commissioning and decommissioning
DE102013218971A1 (de) * 2013-09-20 2015-03-26 Vega Grieshaber Kg Kundenspezifische Konfiguration und Parametrierung von Füllstandmessgeräten beim Bestellvorgang
CN105830417B (zh) * 2013-11-22 2019-04-26 Abb瑞士股份有限公司 用于替换和调试现场设备的方法和系统
US10078034B2 (en) 2014-02-14 2018-09-18 Yokogawa Electric Corporation Field device commissioning system and field device commissioning method
US10018998B2 (en) 2014-02-14 2018-07-10 Yokogawa Electric Corporation Field device commissioning system and field device commissioning method
US9719887B2 (en) 2014-02-14 2017-08-01 Yokogawa Electric Corporation Field device commissioning system and field device commissioning method
DE102014007386A1 (de) * 2014-05-20 2015-11-26 Abb Technology Ag Verfahren und Einrichtung zur Verwaltung und Konfiguration von Feldgeräten einer Automatisierungsanlage
DE102014016819A1 (de) * 2014-11-14 2016-05-19 Abb Technology Ag Verfahren und Einrichtung zur Verwaltung und Konfiguration von Feldgeräten einer Automatisierungsanlage
US10623244B2 (en) * 2014-12-19 2020-04-14 Emerson Process Management Lllp Data transfer on an industrial process network
US9921569B2 (en) 2015-03-06 2018-03-20 Yokogawa Electric Corporation Field device commissioning system and method
CN105093937B (zh) * 2015-03-13 2018-09-18 霍尼韦尔环境自控产品（天津）有限公司 楼宇控制系统设计设备和方法
CN105093938B (zh) * 2015-03-13 2018-08-24 霍尼韦尔环境自控产品（天津）有限公司 楼宇控制系统设计及维护设备和方法
CN105093939B (zh) * 2015-03-13 2018-12-14 霍尼韦尔环境自控产品（天津）有限公司 楼宇控制系统设计及调试设备和方法
US10502340B2 (en) * 2015-08-17 2019-12-10 Honeywell International Inc. System for a valve setup
DE112016004669T8 (de) * 2015-10-12 2018-08-23 Fisher-Rosemount Systems, Inc. Automatischer Kreistest für einen Prozessregelkreis
DE102015120734A1 (de) * 2015-11-30 2017-06-01 Endress+Hauser Process Solutions Ag Verfahren und System zur Optimierung der Bedienung von zumindest einem einer Vielzahl von Feldgeräten der Automatisierungstechnik
DE102016120972A1 (de) * 2016-11-03 2018-05-03 Endress+Hauser Process Solutions Ag Bereitstellung von Informationen zu Zusatzfunktionalitäten von Feldbuskomponenten
US11714394B2 (en) * 2018-09-28 2023-08-01 Fisher-Rosemount Systems, Inc Bulk commissioning of field devices within a process plant
WO2022106885A1 (fr) * 2020-11-18 2022-05-27 Myomega Systems Gmbh Système de commande industrielle
CN115542766B (zh) * 2022-11-25 2023-04-07 苏州金梓树智能科技有限公司 基于模式场景进行智能节点控制的数据处理方法及系统

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6801920B1 (en) * 2000-07-05 2004-10-05 Schneider Automation Inc. System for remote management of applications of an industrial control system

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5617522A (en) * 1995-04-03 1997-04-01 Honeywell Inc. Methods and apparatus for providing and/or customizing display screens and operator interfaces for process control and measurement instruments
US5960169A (en) * 1997-02-27 1999-09-28 International Business Machines Corporation Transformational raid for hierarchical storage management system
US6342907B1 (en) * 1998-10-19 2002-01-29 International Business Machines Corporation Specification language for defining user interface panels that are platform-independent
US6754885B1 (en) * 1999-05-17 2004-06-22 Invensys Systems, Inc. Methods and apparatus for controlling object appearance in a process control configuration system
US6788980B1 (en) * 1999-06-11 2004-09-07 Invensys Systems, Inc. Methods and apparatus for control using control devices that provide a virtual machine environment and that communicate via an IP network
US6449715B1 (en) * 1999-10-04 2002-09-10 Fisher-Rosemount Systems, Inc. Process control configuration system for use with a profibus device network
US7797634B2 (en) * 2002-10-31 2010-09-14 Brocade Communications Systems, Inc. Method and apparatus for displaying network fabric data

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6801920B1 (en) * 2000-07-05 2004-10-05 Schneider Automation Inc. System for remote management of applications of an industrial control system

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
Profibus Nutzerorganisation: "PROFIBUS Guideline, Specification for PROFIBUS Device Description and Device Integration", 1 May 2001 (2001-05-01), Profibus Nutzerorganisation, XP002632935, vol. 3, pages 1-35, * the whole document * *
See also references of WO2007121141A2 *

Also Published As

Publication number Publication date
WO2007121218A2 (fr) 2007-10-25
CN101460928A (zh) 2009-06-17
CN101460928B (zh) 2012-02-08
WO2007121141A2 (fr) 2007-10-25
WO2007121218A3 (fr) 2008-09-18
WO2007121141A3 (fr) 2008-02-14
EP2010991A2 (fr) 2009-01-07
EP2011009A4 (fr) 2011-06-29
EP2010991A4 (fr) 2011-06-01

Similar Documents

Publication Publication Date Title
US8527888B2 (en) Method and supporting configuration user interfaces for streamlining installing replacement field devices
WO2007121141A2 (fr) Procédé et interfaces utilisateur de configuration de soutien pour rationaliser l'installation de dispositifs de terrain de remplacement
EP2531895B1 (fr) Déploiement de configuration pour dispositifs à champs multiples
US9513785B2 (en) Tool for creating customized user interface definitions for a generic utility supporting on-demand creation of field device editor graphical user interfaces
US8464168B2 (en) Device home page for use in a device type manager providing graphical user interfaces for viewing and specifying field device parameters
US8782539B2 (en) Generic utility supporting on-demand creation of customizable graphical user interfaces for viewing and specifying field device parameters
JP6904639B2 (ja) フィールド計装装置からの診断データのバックグラウンド収集
US20070078540A1 (en) Utility for comparing deployed and archived parameter value sets within a field device editor
US7836217B2 (en) Associating and evaluating status information for a primary input parameter value from a Profibus device
US9772617B2 (en) Systems and methods for function block instantiation
US6449715B1 (en) Process control configuration system for use with a profibus device network
US7984199B2 (en) Configuration of field devices on a network
US6446202B1 (en) Process control configuration system for use with an AS-Interface device network
US7272458B2 (en) Control system setting device
JP3499161B2 (ja) プロセス制御ネットワークで使用するためのシャドウ機能ブロックインターフェイス
US7761698B2 (en) Method for replacing a field device of automation technology
JP4786137B2 (ja) プロセスイベントのデータヒストリアンへの自動リンク
US8060872B2 (en) Method for transmitting a software code from a control unit to a field device of process automation technology
US20090157925A1 (en) Method for integrating device-objects into an object-based management system for field devices in automation technology
US20100064297A1 (en) Configuring And Providing Enhanced Access To Profibus Device Diagnostic Data
JP2020057389A (ja) プロセスプラント内のフィールド装置の一括立上げ
WO2008155596A1 (fr) Outil de configuration indépendant des protocoles normalisés pour dispositifs électroniques intelligents (ied)

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20081110

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC MT NL PL PT RO SE SI SK TR

AX Request for extension of the european patent

Extension state: AL BA HR MK RS

A4 Supplementary search report drawn up and despatched

Effective date: 20110530

DAX Request for extension of the european patent (deleted)
17Q First examination report despatched

Effective date: 20160624

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: SCHNEIDER ELECTRIC SYSTEMS USA, INC.

REG Reference to a national code

Ref country code: DE

Ref legal event code: R003

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN REFUSED

18R Application refused

Effective date: 20191125