JP2019106172A - Technique for evaluating and presenting field device commissioning information associated with process plant - Google Patents

Abstract

To provide a technique for evaluating and presenting a difference between current commissioning data of a set of process control devices in a process plant and respective baselines or defined commissioning parameters of the set of process control devices.SOLUTION: According to an embodiment, a system and a method may obtain current commissioning data from a set of process control devices and may access baseline parameters corresponding to commissioning data. The system and method may compare the current commissioning data with the baseline parameters to determine a set of differences, and may present the set of differences for review by an administrator via a user interface. In reviewing the set of differences, the administrator may facilitate different functions, including re-baselining or re-configuring process control devices.SELECTED DRAWING: Figure 1

Description

This application claims the benefit of US Provisional Patent Application No. 61 / 873,390, entitled "FIELD DEVICE INTERACTIONS", filed on Sep. 4, 2013, entitled "BULK FIELD DEVICE OPERATIONS. No. 14 / 477,266, filed on Sep. 4, 2014, claiming the benefit and priority of US patent application Ser. No. 14 / 477,266, the entire content of which is incorporated herein by reference. Be

  The present disclosure relates generally to process plants and process control systems, and more particularly to determining and evaluating the commissioning status of a set of process control devices in a process plant.

  Distributed process control systems, such as those used in chemical, petroleum, industrial or other process plants, for producing, purifying, transforming, producing or producing physical substances or products are typically Production with one or more process controllers communicatively coupled to one or more field devices via an analog bus, a digital bus, or an analog / digital combined bus, or via a wireless communication link or network object. For example, field devices that may be valves, valve positioners, switches, and transmitters (eg, temperature sensors, pressure sensors, level sensors, and flow sensors) are located within the process environment and generally open or close the valves. Perform physical or process control functions, such as measurement of process parameters such as temperature or pressure and / or environmental parameters to control one or more processes running in the process plant or system. Smart field devices, such as field devices conforming to the well-known Fieldbus protocol, may also perform control calculations, alarm functions, and other control functions commonly implemented in controllers. A process controller, also typically located within the plant environment, receives signals indicative of process measurements performed by the field device and / or other information regarding the field device, for example, to make process control decisions. , Generate control signals based on the received information, and cooperate with a control module or block implemented in a field device, such as HART®, WirelessHART®, and FOUNDATION® Fieldbus field devices, Run a controller application that runs different control modules. A control module in the controller sends control signals to the field device via the communication line or link, thereby controlling the operation of at least a portion of the process plant or system to operate or execute inside the plant or system For example, at least a portion of one or more industrial processes are controlled. For example, the controller and the field device control at least a portion of the process being controlled by the process plant or system. An I / O device, also typically located within the plant environment, is typically disposed between the controller and one or more field devices to communicate between them, eg, electrical It is enabled by converting the signal to digital values, and vice versa. As utilized herein, field devices and controllers are generally referred to as "process control devices."

Operator workstations, personal computers or computing devices, data history, report generators, centralized databases, where information from field devices and controllers are typically located in control rooms or elsewhere away from the harsher plant environment It is typically made available to one or more other hardware devices, such as, or other centrally managed computing devices, via a data highway or communication network. Each of these hardware devices is typically centralized across the process plant or a portion of the process plant. These hardware devices can, for example, be the operator changing the settings of the process control routine, modifying the operation of the control module in the controller or field device, viewing the current state of the process, alarms generated by the field device and the controller Can perform functions related to process control and / or process plant operations such as process browsing, personnel training or simulation of process operations for testing process control software, maintenance and updating of configuration databases, etc. Run an application that can be Utilizing a data highway with a hardware device, the controller and field device can include a wired communication path, a wireless communication path, or a combination of wired or wireless communication paths.

  As an example, the DeltaVTM control system, sold by Emerson Process Management, is stored in different devices located at various locations in the process plant, and has multiple applications executed by those different devices. Including. The configuration application, provided in one or more workstations or computing devices, allows the user to create or modify process control modules and download these process control modules to the dedicated distributed controller via the data highway Make it possible. Typically, these control modules are comprised of communicatively interconnected functional blocks, which perform functions within the control scheme based on their inputs and output within the control scheme. It is an object in an object oriented programming protocol that provides other functional blocks. In addition, the configuration application can use the operator interface used by the viewing application to display data to the operator and enable the operator to change settings such as set points in the process control routine. May allow to create or change. Each dedicated controller, and in some cases, one or more field devices, store the respective controller application that executes the assigned control module downloaded to them to implement the actual process control function. And execute. The viewing application may be run on one or more operator workstations (or one or more remote computing devices communicatively connected to the operator workstation and data highway), the viewing application may be data from the controller application Receive data via the highway and use the user interface to display this data to process control system designers, operators or users, some of the operator's views, engineer's views, technicians' views etc Can provide any of the different views of While the data history application is typically stored in and executed by a data history device that collects and stores some or all of the data provided across the data highway, the configuration database application is a current process A further remote computer attached to the data highway can be implemented to store the control routine configuration and the data associated therewith. Alternatively, the configuration database may be located on the same workstation as the configuration application.

In general, commissioning a process plant or system involves directing the various components of the plant or system to the point where the system or plant can operate as intended. Commissioning is a complicated and complicated process. For example, commissioning, among other things, identifies installed process control devices (such as field devices) and identifications of their connections, to uniquely identify process control systems within a process control system or plant, to name a few. Determining and providing tags, setting or configuring initial values of parameters, limit points, etc., verifying the correctness of installation of the device by manipulating the signals provided to the device, plant It may include actions or operations such as generating an as-built I / O list to indicate the actual physical connection of the internally implemented device. For some commissioning tasks, the user may utilize commissioning tools (eg, handheld or portable computing devices) locally at the target process control device or loop. Some commissioning tasks may be performed at the operator interface of the process control system, for example at the operator interface of an operator workstation included within the back end environment of the process plant.

  Typically, commissioning of a process plant requires physical devices, connections, wiring, etc. to be installed, set up, and interconnected within the field environment of the process plant. In the back end environment of the plant (eg, operator workstations, personal computers or computing devices, centralized databases, configuration tools, etc. typically located at a control room or other location away from the harsher field environment of the plant) Data that specifically identifies and / or specifies various devices, their configurations, and their interconnections, in a centrally managed computing device of . Thus, after physical hardware is installed and configured, identification information, logic instructions, and other instructions and / or data may be downloaded to various devices disposed within the field environment. If not, it is provided so that various devices can communicate with other devices.

  Typically, the components of the process plant are commissioned according to the set of desired parameters or specifications and may be identified by one or more documents and / or tools developed by the commissioner. The components are commissioned using system interfaces and utilities that are also used for other management functions within the process plant, including system configuration, maintenance and management activities during process plant operation. However, commissioning employees are often limited to the use of system interfaces and utilities, which causes commissioning employees to experience delays, conflicts, errors, and interactions with control systems and field devices. Not often leads to the implementation of limited proprietary tools and utilities. These processes are time consuming, prone to inconsistencies and errors, and can not be efficiently and effectively determined whether the field device is properly commissioned.

  Thus, there is an opportunity for a system and method to retrieve the latest commissioning state of the field device and to efficiently and effectively present the difference between the commissioning state of the field device and the intended commissioning parameters.

  Techniques, systems, devices, components, devices and methods for commissioning are disclosed herein. Such techniques, systems, devices, components, devices, and methods may be applied to industrial process control systems, environments, and / or plants, which are interchangeable herein. Also referred to as "industrial control", "process control" or "process" system, environment, and / or plant. Typically, such systems and plants operate in a distributed fashion to control one or more processes that operate to produce, purify, transform, produce, or produce a physical substance or product. provide.

The commissioning of the process control system and / or plant may be performed by various techniques, systems, devices, components and / or components that allow at least some of the commissioning processes to be performed locally and automatically and / or distributedly. Or the method, so that the device and / or other parts of the process plant are partially or before being turned on before being integrated or integrated into the plant or system as a whole. It can be commissioned entirely. Commissioning, for example, is built at different geographic locations (eg, at different “mod yards”) before various parts of the process control system are brought together and integrated at the resident location or site of the process plant, It is possible to be at least partially commissioned. As a result, commissioning enables parallel commissioning activities and actions to be taken.

  The process plant may be commissioned according to a baseline or set of defined parameters, the baseline or set of defined parameters specifying how each field device in the process plant should be commissioned. However, during operation, the field devices may not be commissioned according to their respective parameters, which may result in error conditions and alarms, and / or may require additional repair and maintenance.

  One embodiment of the disclosed technology is a computer-implemented method of accessing commissioning data associated with a set of devices in a process plant, wherein at least some of the sets of devices process such that the sets of processes are controlled. It is communicably connected to operate during operation in the plant. The method may include, for each of the set of devices at the computing device, commissioning state data of the respective device and accessing a set of defined commissioning parameters respectively associated with the set of devices. The method is defined by the computing device for determining the difference between the respective commissioning state data and the respective defined commissioning parameters for each of the set of devices, and in the user interface as a set of commissioning state data. And C. indicating a set of differences between the set of commissioning parameters.

  Another embodiment of these techniques is a system in a process plant for accessing commissioning data associated with the process plant. The system is respectively associated with a set of devices communicatively connected to operate in operation within the process plant to control the set of processes, a user interface for presenting content, and the set of devices. A memory storing the set of defined commissioning parameters and a processor communicating with the communication unit, the set of devices, the user interface, the memory and the communication unit may be included. The processor receives commissioning state data of the respective device from each of the set of devices via the communication unit, accesses from the memory a set of defined commissioning parameters respectively associated to the set of devices, and For each of the sets, determine the difference between the respective commissioning state data and the respective defined commissioning parameters, and in the user interface the difference between the set of commissioning state data and the set of defined commissioning parameters It may be configured to prompt the set.

A further embodiment of these techniques is an electronic device for managing commissioning data associated with a process plant. The electronic device has a user interface for presenting content, a transceiver for communicating with a set of devices communicatively connected to operate in operation within the process plant to control the set of processes, computer implemented A memory storing a set of possible instructions and a processor in communication with the user interface, the transceiver and the memory. The processor receives the selection of at least one of the set of devices via the user interface to the processor, and from one of the set of devices via the transceiver at least one of the set of devices Retrieving two commissioning state data, wherein the commissioning state data is associated with at least one of the retrieving and the at least one of the set of devices indicating the current configuration of the at least one of the set of devices Access to defined commissioning parameters, determining the difference between commissioning state data and the defined commissioning parameters, and in the user interface commissioning parameters defined as commissioning state data. And thereby instructing the difference between the data, to perform, it may be configured to execute a set of computer executable instructions.

  An additional embodiment of these techniques is a computer-implemented method in an electronic device that presents commissioning data associated with a set of devices in a process plant, wherein at least some of the set of devices comprise a set of processes. Can be communicatively connected to operate in operation within the process plant to control the The method comprises, for each of the set of devices from the controller, receiving commissioning state data of the respective device, accessing the set of defined commissioning parameters respectively associated with the set of devices, and For each of the sets, determining the difference between the respective commissioning state data and the respective defined commissioning parameters, and in the user interface between the set of commissioning state data and the set of commissioning parameters defined. Presenting a set of sections indicating at least some of the set of differences, and selecting a section of the set of sections via the user interface And receiving, at the user interface, associated with some of the set of differences corresponds to a section of the set of sections, and presenting the information may include.

By utilizing the commissioning techniques described herein, a block diagram is depicted illustrating an example of a process plant and components that may be at least partially commissioned. FIG. 1 shows a block diagram of a device configured to obtain, store and analyze data and parameters related to commissioning of a process plant. FIG. 7 shows signal diagrams associated with obtaining commissioning data associated with a process plant and comparing commissioning data with baseline parameters. 8 illustrates an exemplary interface associated with presenting commissioning data and comparing with baseline parameters. 8 illustrates an exemplary interface associated with presenting commissioning data and comparing with baseline parameters. 8 illustrates an exemplary interface associated with presenting commissioning data and comparing with baseline parameters. 8 illustrates an exemplary interface associated with presenting commissioning data and comparing with baseline parameters. 8 illustrates an exemplary interface associated with presenting commissioning data and comparing with baseline parameters. 8 illustrates an exemplary interface associated with presenting commissioning data and comparing with baseline parameters. 8 illustrates an exemplary interface associated with presenting commissioning data and comparing with baseline parameters. 8 illustrates an exemplary interface associated with presenting commissioning data and comparing with baseline parameters. 8 illustrates an exemplary interface associated with presenting commissioning data and comparing with baseline parameters. 8 illustrates an exemplary interface associated with presenting commissioning data and comparing with baseline parameters. FIG. 6 is a flow diagram of an example method of accessing commissioning data associated with a set of process control devices in a process plant.

FIG. 6 is a flow diagram of an example method of presenting commissioning data associated with a set of process control devices in a process plant.

  The process plant ensures that the system and components of the plant are designed, tested, installed, operated and maintained according to the owner or customer's operating requirements, thereby ensuring the process plant's feasibility, performance, reliability, Commissioned to ensure safety and information traceability.

  Commissioning a process plant may include configuration of field devices with a set of parameters, which may be default parameters, or may be modifiable by the process plant administrator. In particular aspects, field devices may be configured in bulk using configuration templates or similar techniques, such as those disclosed in the aforementioned US patent application Ser. No. 14 / 477,266. Before, simultaneously with, or after the field device is configured, the process control system includes identification of the installed process control device (field device etc.) and its connection, and uniquely identifies the process control device in the process control system or plant. ASBUILD I to determine and provide the tags that identify them, verify the correctness of device installation by manipulating the signals provided to the devices, and indicate the actual physical connection of the devices implemented in the plant May prompt additional commissioning operations to generate the / O list.

  In general, templates, requirements documents, etc. may include a set of defined commissioning parameters that specify how to commission the field devices of the process plant. In addition, the actual commissioning state, status or condition of the field device may be incorporated into commissioning state data of the field device. The systems and methods described herein obtain commissioning state data associated with a field device and compare the commissioning state data to a set of defined commissioning parameters, if (i) if present It is determined whether the field device is not commissioned according to the defined parameters and (ii) how far the determined field device deviates from the defined parameters.

The system and method may further generate a set of interfaces that can indicate the determined field devices and how far they deviate from the defined parameters. A user or administrator associated with the process plant may access a set of interfaces to review information, make selections, and initiate specific functions. In particular, the user or administrator may choose to modify the defined parameter (s), to reconfigure or recommit the field device to match the respective defined parameter (s) It may select and / or initiate other functions. In general, a "process control device", "control device" or "field device" is configured to initiate, implement and / or manage functions associated with them, including control devices, safety devices, monitoring devices etc. It may be any device within the plant environment to obtain.

  Thus, the present systems and methods provide a number of benefits. In particular, the systems and methods are effectively and efficiently integrated with the process control system to identify field devices that are not properly commissioned and display a set of interfaces detailing the differences in commissioning. Therefore, the manager of the process plant can efficiently and effectively measure which field device deviates from the defined parameters. The systems and methods may further enable the administrator to initiate corrective actions and / or other functions associated with commissioning of the field device. It should be understood that further advantages are envisaged.

  FIG. 1 is a block diagram of an example of a commissioned process plant, process control system or process control environment 5, at least a portion of which is commissioned in accordance with various techniques. The process plant 5 receives signals indicating process measurements made by the field device, processes this information to implement the control routine, and other fields via wired or wireless process control communication links or networks. It includes one or more process controllers that can be sent to the devices to generate control signals that control the operation of the processes in the plant 5. Typically, at least one field device performs a physical function (eg, opening or closing a valve, temperature increase or decrease, etc.) to control the operation of the process, and some types of field devices Communicate with the controller by using I / O devices. Process controllers, field devices and I / O devices may be wired or wireless, and any number and combination of wired and wireless process controllers, field devices and I / O devices are included in the process plant environment or system 5 It is good.

  For example, FIG. 1 shows a process controller 11, which is communicatively connected to the wired field devices 15-22 via input / output (I / O) cards 26 and 28, and a wireless gateway 35 and Process control data highway or backbone 10 (which may include one or more wired and / or wireless communication links and may be implemented using any desired or suitable or communication protocol, such as, for example, Ethernet protocol) Are communicably connected to the wireless field devices 40-46. In one embodiment, the controller 11 may be configured to use one or more communication protocols, such as Wi-Fi or other IEEE 802.11 compliant wireless local area network protocols, mobile communication protocols (eg, WiMAX, LTE, or others). ITU-R compliant protocol), Bluetooth (R), HART (R), WirelessHART (R), Profibus, FOUNDATION (R) Fieldbus, etc. any number of other wired or wireless communication links Are communicably connected to the wireless gateway 35 using one or more communication networks other than the backbone 10.

The controller 11, as an example, sold by Emerson Process Management, but may be a DeltaV ^(TM) controller, using at least some of the field devices 15-22 and 40-46, a batch process or a continuous May operate to implement the process. In one embodiment, in addition to being communicatively coupled to process control data highway 10, controller 11 may also, for example, be a standard 4-20 mA device, I / O card 26, 28, and / or Field devices 15-15 using any desired hardware and software associated with any smart communication protocol such as FOUNDATION ® Fieldbus protocol, HART ® protocol, WirelessHART ® protocol, etc. 22 and at least some of 40 to 46 are communicably connected. In FIG. 1, the controller 11, the field devices 15 to 22 and the I / O cards 26 and 28 are wired devices, and the field devices 40 to 46 are wireless field devices. Of course, wired field devices 15-22 and wireless field devices 40-46 may be any wired or wireless protocol including any other desired standard (s) or protocol, eg any standard or protocol to be developed in the future Can fit into.

  Process controller 11 of FIG. 1 includes a processor 30 that implements or oversees one or more process control routines 38 (eg, stored in memory 32). Processor 30 is configured to communicate with field devices 15-22 and 40-46 as well as other process control devices communicatively connected to controller 11. It should be noted that any of the control routines or modules described herein may, if so desired, have portions of them implemented or carried out by different controllers or other devices. Similarly, the control routines or modules 38 described herein implemented within process control system 5 may take any form, including software, firmware, hardware, etc. The control routines may be implemented in any desired software format, such as object oriented programming, ladder logic, sequential function charts, function lock diagrams, or any other software programming language or using a design paradigm. Control routines 38 may be stored in any desired type of memory 32, such as random access memory (RAM) or read only memory (ROM). Similarly, control routine 38 may be hard-coded into, for example, one or more EPROMs, EEPROMs, application specific integrated circuits (ASICs), or any other hardware or firmware element. Thus, controller 11 can be configured to implement control strategies or control routines in any desired manner.

  In some embodiments, controller 11 implements control strategies using what are commonly referred to as functional blocks, each functional block being an object or other portion (eg, a subroutine) of the overall control routine. And work with other function blocks (via communications called links) to implement the process control loop within the process control system 5. Control-based function blocks are typically transmitters, input functions associated with sensors or other process parameter measurement devices, PID, control functions associated with control routines that perform control such as fuzzy logic, or valves etc. Perform one of the output functions that control the operation of some of the devices to perform some physical functions within the process control system 5. Of course, there are hybrid and other kinds of functional blocks. The functional blocks are stored in the controller 11 and may be implemented by it, which are typically several types of such functional blocks such as standard 4-20 mA devices and HART® devices Or function blocks may be stored and implemented by the field device itself when it is used for or associated with a smart field device in the field of the FOUNDATION® Fieldbus device. It can be the case. The controller 11 may implement one or more control loops, and may include one or more control routines 38, which may be implemented by executing one or more of the functional blocks.

Wired field devices 15-22 may be any type of device such as sensors, valves, transmitters, positioners, etc. while I / O cards 26 and 28 are any suitable for any desired communication or controller protocol. Type I / O device. In FIG. 1, field devices 15-18 are I / O cards 26 (herein "non-smart" or "dumb" through analog lines or analog digital coupled lines).
Devices are also standard 4-20 mA devices or HART® devices that communicate with devices), while field devices 19-22 use the FOUNDATION® Fieldbus communication protocol to A smart device such as a FOUNDATION® Fieldbus field device that communicates with the I / O card 28 through. However, in some embodiments, at least some of the wired field devices 15, 16 and 18-21 and / or at least some of the I / O cards 26, 28 additionally or alternatively It may communicate with controller 11 using control data highway 10 and / or by using other suitable control system protocols (e.g., Profilebus, DeviceNet, Foundation Fieldbus, ControlNet, Modbus, HART, etc.) .

  In FIG. 1, the wireless field devices 40-46 communicate over the wireless process control communication network 70 using a wireless protocol such as the WirelessHART® protocol. Such wireless field devices 40-46 are in direct communication with one or more other devices or nodes of wireless network 70 that are also configured to wirelessly communicate (eg, using a wireless protocol or another wireless protocol) It can communicate. In order to communicate with one or more other nodes not configured to communicate wirelessly, the wireless field devices 40-46 may be wireless gateways connected to the process control data highway 10 or another process control communication network You may use 35. Wireless gateway 35 provides access to the various wireless devices 40-58 of wireless communication network 70. In particular, the wireless gateway 35 provides communicable coupling between the wireless devices 40-58, the wired devices 11-28 and / or other nodes or devices of the process control plant 5. For example, the wireless gateway 35 provides communicable coupling by using the process control data highway 10 and / or by using one or more other communication networks of the process plant 5.

  As with the wired field devices 15-22, the wireless field devices 40-46 of the wireless network 70 within the process plant 5 perform physical control functions, such as opening or closing of valves, or obtaining measurements of process parameters. Run. However, wireless field devices 40-46 are configured to communicate using the wireless protocol of network 70. Thus, the wireless field devices 40-46, the wireless gateway 35, and the other wireless nodes 52-58 of the wireless network 70 are producers and consumers of wireless communication packets.

In some configurations of process plant 5, wireless network 70 includes non-wireless devices. For example, in FIG. 1, the field device 48 of FIG. 1 is a conventional 4-20 mA device and the field device 50 is a wired HART® device. To communicate within network 70, field devices 48 and 50 are connected to wireless communication network 70 via wireless adapters 52a, 52b. The wireless adapters 52a, 52b support wireless protocols such as WirelessHART, and may also support one or more other communication protocols such as Foundation® Fieldbus, PROFIBUS, DeviceNet, and the like. In addition, in some configurations, wireless network 70 may be an independent physical device in wired communication with wireless gateway 35 or may be provided within wireless gateway 35 as an integrated device Includes points 55a, 55b. Also, wireless network 70 may also include one or more routers 58 for forwarding packets from one wireless device to another wireless device within wireless communication network 70. In FIG. 1, wireless devices 40-46 and 52-58 communicate with each other and with wireless gateway 35 via wireless link 60 of wireless communication network 70 and / or via process control data highway 10.

  In FIG. 1, process control system 5 includes one or an operator workstation 71 communicatively connected to a data highway. Through the operator workstation 71, the operator may take any diagnostic, corrective, maintenance, and / or other actions that may be necessary in addition to viewing and monitoring the real time operation of the process plant 5. At least some of the operator workstations 71 may be located in various protected areas in or near the plant 5 and in some situations at least some of the operator workstations 71 may be remotely Although positioned, it may nevertheless be communicatively connected to the plant 5. The operator workstation 71 may be a wired or wireless computing device.

  Process control system 5 includes an asset management system 68 configured to facilitate the specific functions described herein. The asset management system 68 may communicate and communicate with some or all of the field devices 15-22 and 40-46 via the process controller 11 and / or the wireless gateway 35 or the like. According to an embodiment, asset management system 68 may request and retrieve commissioning data associated with field devices 15-22 and 40-46 from field devices 15-22 and 40-46.

  The asset management system 68 is generally associated with the user-controlled field devices 15-22 and 40-46 of the process control system 5 running on one or more work stations (such as operator workstation (s) 71). One or more software applications may be included that allow for review of the commissioning data. Such interactions may include diagnostics, maintenance, configuration, evaluation, etc. The workstation (s) may have one or more asset management system applications running locally, but the user may remotely communicate with the asset management system 68 via a data communication network. Thus, a user located at the workstation (s) interacts with the asset management system 68 to facilitate various functions associated with the process control system 5, regardless of the user's physical location. obtain.

The exemplary process control system 5 is further shown as including a configuration application 72a and a configuration database 72b, each of which is also communicatively coupled to the data highway 10. The various instances of configuration application 72a allow the creation or modification of process control modules by the user and the downloading of these modules to controller 11 via data highway 10, as well as within the process control routine by the operator. One or more computing devices (not shown) may be run to allow the user to create or change the operator interface through being able to view data at and change data settings at . Configuration database 72b stores created (eg, configured) modules and / or operator interfaces. In addition, configuration database 72b stores a set of defined or baseline commissioning parameters associated with any of field devices 15-22, 40-46. In general, configuration application 72a and configuration database 72b are centralized and single to process control system 5, even though multiple instances of configuration application 72a may be simultaneously executed within process control system 5. And the configuration database 72b may be implemented across multiple data storage devices. Thus, configuration application 72a, configuration database 72b, and a user interface (not shown) thereto, include a configuration or development system 72 for control and / or display modules. Typically, the user interface of configuration system 72 is utilized by the configuration and development engineers, regardless of whether plant 5 is operating in real time, so the user interface of configuration system 72 is configured with operator workstation 71 The operator workstation 71, which is different but not necessarily so, is utilized by the operator during real time operation of the process plant 5.

  The example process control system 5 also includes a data history application 73a and a data history database 73b, each of which is also communicatively connected to the data highway 10. Data history application 73a is operable to collect some or all of the data provided across data highway 10 and to history the data or store it in history database 73b for long term storage. Do. Similar to the configuration application 72a and the configuration database 72b, the data history application 73a and the history database 73b are centralized, although multiple instances of the data history application 73a may be simultaneously executed within the process control system 5. And may have a single logical appearance to the process control system 5, and the data history 73b may be implemented across multiple physical data storage devices.

  In some configurations, process control system 5 may include other wireless protocols such as Wi-Fi or other IEEE 802.11 compliant wireless local area network protocols, mobile communication protocols such as WiMAX (Worldwide Interoperability for Microwave Access), LTE (Long Term Evolution) or other ITU-R (International Telecommunication Union Radio Communication Sector) compatible protocol, shortwave radio communication such as near field communication (NFC) and Bluetooth, or other Communicate with other devices using wireless communication protocols And one or more other wireless access points 74 to communicate. Typically, such wireless access points 74 are hand-held or otherwise via a respective wireless process control communication network, different from the wireless network 70 and supporting a different wireless protocol than the wireless network 70. Communication by a portable computing device (e.g., user interface device 75). For example, the wireless or portable user interface device 75 may be a mobile workstation or diagnostic test equipment utilized by an operator (eg, an instance of one of the operator workstations 71) in the process plant 5. In some scenarios, in addition to portable computing devices, one or more process control devices (e.g., controller 11, field devices 15-22, I / O devices 26, 28 or wireless devices 35, 40-58) Also communicate using wireless protocols supported by access point 74.

The exemplary process control system 5 may also include one or more commissioning tools 135a, 135b used in the field environment 122 to commission the process control devices of the process plant 5. An example of the commissioning tools 135a, 135b is the AMS TrexTM device communicator marketed by Emerson Process Management. In an embodiment, the commissioning tools 135a, 135b may automatically synchronize data with the asset management system 68. The commissioning tools 135a, 135b may be portable computing devices such as laptop computers, tablets or handheld smart devices, wearable computing devices and the like. The commissioning tool 135a may be used to commission the non-smart field devices 15-18, the smart field devices 19-22 and / or other devices disposed in the field environment 122 of the process plant 5. In order to commission the non-smart field devices 15-18, the commissioning tool 135a may wirelessly link 76a via the I / O card 26 or any other suitable component connected to the non-smart field devices 15-18. (Eg, via RFID, NFC, etc.). In this manner, the commissioning tool 135a may be configured to electronically marshal non-smart field devices 15-18 commissioning data (eg, device tags) to the corresponding I / O card 26 or I / O card 26. May be transferred to an element (as described in more detail below). To commission the smart field devices 19-22, the commissioning tool 135b may communicate with the smart field devices 19-22 directly via the wireless link 76b. In this way, the commissioning tool 135b may transfer commissioning data (eg, device tags) directly to the smart field devices 19-22.

  In some embodiments, the process control device may be pre-configured, for example while in the factory, and so default commissioning data is stored before being installed or commissioned. In other embodiments, the process control device may arrive from the factory without any commissioning data stored therein. For example, if the I / O device is communicatively connected to the non-smart field device, the I / O device may continue to the non-smart field device until the commissioning tool 135 transfers the commissioning data to the I / O device. Do not store commissioning data.

  FIG. 1 is single with a finite number of field devices 15-22 and 40-46, wireless gateway 35, wireless adapter 52, access point 55, router 58, and process control communication network 70 contained within the illustrated process plant 5. It is noted that although only showing the wireless controller 11, this is only an exemplary and non-limiting embodiment. Any number of controllers 11 may be included in the process control plant or system 5 and any of the controllers 11 may be any number of wired or wireless devices and networks 15-22, 40-46, 35, 52 , 55, 58, and 70 to control the processes in the plant 5.

  Further, it is noted that the process plant or control system 5 of FIG. 1 includes a field environment 122 (eg, “process plant floor 122”) and a back end environment 125 communicatively connected by data highway 10 . As shown in FIG. 1, the field environment 122 is disposed, installed and interconnected therein and is a physical component (eg, process control device, network, network) that operates to control the process during operation. Element etc.). For example, controller 11, I / O cards 26, 28, field devices 15-22, and other devices and network components 40-46, 35, 52, 55, 58 and 70 may be located or disposed. Or otherwise included in the field environment 122 of the process plant 5. Generally speaking, in the field environment 122 of the process plant 5, the raw materials are received and processed using physical components disposed therein to produce one or more products.

The back end environment 125 of the process plant 5 includes various components such as computing devices, operator workstations, databases or data banks shielded and / or protected from the harsh conditions and materials of the field environment 122. Referring to FIG. 1, the back end environment 125 may include, for example, an operator workstation 71, a configuration or development system 72 for controlling modules and other executable modules, a data history system 73, and / or run time operation of the process plant 5. Including other centralized management systems, computing devices, and / or functionality that support In some configurations, the various computing devices, databases, and other components and equipment included in the back end environment 125 of the process plant 5 may be physically located at different physical locations, some of which May be local to the process plant 5, some of which may be remote.

  As described herein, the configuration database (s) 72b may be disposed in the back end environment 125 of the process plant 5 and used for commissioning purposes. Configuration database (s) 72b specifically identifies and / or interconnects various devices or components that are planned or desired to be implemented in the process plant floor or field environment 122, among others. Or it may store data and other information to address. Some of this commissioning data may be provided to components in field environment 122 for use in commissioning devices and loops therein, some of this data may be processed in backend environment 125, for example, processes. It may be utilized for the preparation of design, development and control modules and / or operator interface modules operating in conjunction with the field environment 122 during operation of the plant 5.

  FIG. 2 shows a simplified block diagram of an exemplary device 212 (also referred to herein as system or apparatus 212) specifically configured to obtain, store and analyze data and parameters associated with commissioning of a process plant. . In some situations, device 212 may be utilized to commission field devices and other process elements. Device 212 may be a computer or computing device, to name a few, or device 212 may be another system specifically configured to support the techniques, methods, and systems of the present disclosure, It may be an apparatus or device including, but not limited to, a cell phone, smart phone, tablet or other wireless device, personal digital assistant, media player, appliance. Device 212 may be one or more of the components of process plant 5 (eg, operator workstation (s) 71, configuration application (s) 72a, user interface device 75, etc.) as described with respect to FIG. It can be incorporated. However, for ease of explanation and not limitation, device 212 is referred to herein as computing device 212.

  Exemplary computing device 212 includes processor 215 for executing computer-executable instructions, program memory 218 for permanently storing data associated with computer-executable instructions, temporary data associated with computer-executable instructions. Including random access memory (RAM) 220 and input / output (I / O) circuitry 222, all of which may be interconnected via address / data bus 225. In some configurations, processor 215 is a multi-core processor or processor having co-processing capabilities (eg, quantum, cells, chemistry, photonics, bio-chemicals, biological processing techniques and / or other suitable co-processing techniques) . In some configurations, memory 218 and / or RAM 220 may be high density, such as solid state drive memory, flash memory, semiconductor memory, optical memory, molecular memory, biological memory or any other suitable high density memory technology Implemented using memory technology. In the exemplary configuration, computing device 212 includes a multi-core processor and / or high density memory technology.

Although only one processor 215 is shown in FIG. 2, it should be understood that the computing device 212 may include multiple processors 215. Similarly, the memory of computing device 212 may include multiple RAMs (random access memory) 220 and / or multiple program memories 218. The RAM 220 (s) and / or program memory 218 may, for example, be one or more semiconductor memories, flash memories, magnetically readable memories, optically readable memories, biological memories and / or other It may be implemented as a tangible non-transitory computer readable storage medium. Additionally, although I / O circuit 222 is shown as a single block, it should be understood that I / O circuit 222 may include several different types of I / O circuits. For example, the first I / O circuit may correspond to the display device 228 of the device 212, and the first or second I / O circuit may correspond to the user interface 230 of the device 212. User interface 230 may include, for example, a keyboard, mouse, touch screen, voice activated device, and / or any other known user interface device. In some embodiments, display device 228 and user interface 230 may be jointly integrated into a single physical device, such as a touch screen. Additionally or alternatively, display device 228 and / or user interface 230 may be incorporated into a separate device from computing device 212. For example, computing device 212 may be implemented in operator workstation 71, and display device 228 and / or user interface 230 may be implemented in user interface device 75.

  The computing device 212 includes one or more networks or communication interfaces 232 and is accessed via one or more respective links 235 to one or more respective communication or data networks. Communication interface 232 may include an interface to a communication and / or data network specific to one or more process controls, eg, Fieldbus, Profibus, HART, 4-20 mA loop, WirelessHART, process control big data, etc. For example, computing device 212 includes an interface to a process control big data network. Additionally or alternatively, communication interface 232 may include one or more interfaces to a general purpose communication and / or data network such as Ethernet, NFC, RFID, Wi-Fi, etc. The link 235 to the communication or data network may be a memory access function and / or the link 235 may be wired, wireless or multistage connection. Many types of interfaces 232 and links 235 are known in the field of networking and may be used with computing device 212.

  Computing device 212 includes one or more sets of particular computer executable instructions 240 stored thereon, such that computing device 212 stores one or more particular ones stored thereon. It is specifically configured by at least a portion of the set of instructions 240. As used herein, the terms "computer-executable instructions", "computer executable instructions" and "instructions" are used interchangeably. As shown in FIG. 2, instructions 240 are stored in memory 218 and are executable by processor 215 to perform any part or all of the methods and / or techniques described herein. The set of one or more instructions 240 may include one or more engines, routines, applications or programs. The set of applications 248 may be included as part of a set of one or more instructions 240. In some embodiments, a set of applications 248 may be associated with the asset management system 68 to obtain and analyze commissioning data for field devices and store commissioning data data as described further herein. A commissioning analysis application 252 may be included that is configured to compare the received parameters and determine the information to present via the display device 228 and / or the user interface 230. The set of applications 248 may include the set of other applications 254.

  Of course, although not shown in FIG. 2, computing device 212 may additionally or alternatively include other sets of instructions 240 and / or other elements or components.

  FIG. 3 depicts a signal diagram 300 associated with accessing and analyzing commissioning data associated with a set of process control devices in a process plant. Signal diagram 300 includes a set of process control devices 310, a database or memory 312, a computer processor 314 and a display device or user interface 316. In one implementation, one or more of memory 312, processor 314 and user interface 316 may be incorporated into a single electronic device 318, or with separate components incorporated into separate devices or components. May be there. The set of process control devices 310, memory 312, processor 314 and user interface 316 may communicate with one another via various wired or wireless interfaces as described herein.

  The electronic device 318 may be a workstation such as one of the operator workstation (s) 71 as described with respect to FIG. 1 and the workstation may be an asset manager as described with respect to FIG. The software application (s) associated with the system 68 may be supported and executed, with the software application (s) associating a set of interfaces that may be displayed by the user interface 316.

  Signaling diagram 300 begins when processor 314 optionally receives, from user interface 316, a request to commission data associated with at least one of the set of process control devices 310 (320). obtain. In an embodiment, the user of the user interface 316 may initiate a request, via the display indicating the set of process control devices 310 and the information associated therewith, at least one of the set of process control devices 310 You may choose. For example, a user may request commissioning data for a set of process control devices associated with a boiler in a process plant.

  Processor 314 may send a request to commission the data to optionally identified process control device (s) 310 (322). The request may correspond to the request received at (320) or may be a separate request, and the request may identify at least one (or all) process control device (s) 310. In general, the request may indicate one or more portions of commissioning data such as, for example, device information, device health, configuration data, connectivity status, commissioning status and / or the like. In particular embodiments, processor 314 may automatically, eg, at periodic intervals (eg, once per minute, once per hour, etc.), or trigger (eg, a request from a user, updated commissioning data) Request may be sent in response to the presence of

  Process control device (s) 310 may send commissioning data to processor 314 (324). The commissioning data may correspond to the request received at (322), or the process control device (s) 310 may automatically, eg, at periodic intervals (eg, once / minute, once) The commissioning data may be sent at / one hour, etc.) or in response to a trigger (eg, due to data changes, presence of updated commissioning data, etc.). Commissioning data may include, for example, device information, device health, configuration data, connectivity status, commissioning status, and / or the like.

Processor 314 may optionally examine the commissioning data (325) to identify the type of data included in the commissioning data. In particular, the commissioning data may include one or more parts, such as, for example, device information, configuration data, connectivity status, commissioning status and / or others. Processor 314 may retrieve the parameters defined for the commissioning data (326). In particular, processor 314 may retrieve the defined parameter (s) according to the type of data included in the commissioning data. For example, if the commissioning data includes valve timing settings associated with the boiler, the processor 314 may retrieve parameters corresponding to the valve timing settings. According to embodiments, the defined parameters may represent a desired commissioning state of the process control device (s) 310. In general, memory 312 may maintain defined parameters that allow an administrator or user associated with the process control system to enter, modify, update, or add to the defined parameters.

  After receiving the defined parameters, processor 314 determines 330 a set of differences between the commissioning data and the defined parameters. For example, the defined parameters may specify that a particular valve has an active connection between 8 am and 5 pm, and the commissioning data at 10 am when the particular valve is active. You may indicate that you do not have it. Thus, this difference may indicate this difference in connection status. As a further example, the defined parameters may specify that the flow sensor triggers an alarm when the corresponding flow rate exceeds 5.0 cc / min, and the commissioning data indicates that the flow sensor corresponds to a flow rate of 10.0 cc / min. It may indicate that it is configured to trigger an alarm when it exceeds a minute. Thus, this difference may indicate a difference in the flow value.

  Processor 314 may send the indication of the difference (s) to user interface 316 (332). In particular, processor 314 may generate a visual layout, interface, graphics, etc. that indicate the difference (s) determined in (330), the visual layout being configured for display by user interface 316 You may Thus, the user interface 316 may present the difference (s) (334). Thus, the user may access the user interface 316 to review the difference (s) and evaluate whether any action is needed to address the difference (s). According to embodiments, user interface 316 may use various interfaces, graphics, arrangements, etc. that may include visual and / or graphic content of various texts in presenting differences. Various of these visual interfaces are described with respect to FIGS. 4A-4J.

  The user interface 316 may support interaction with the user via, for example, touch screen input or input detected from a peripheral device such as a mouse or keyboard. In particular, user interface 316 may allow search by particular process control devices, classification, integration and / or other modifications or interactions, and the like. In an embodiment, the user may choose to review additional information associated with the process control device (s) 310, such as information not displayed on the user interface 316. Thus, user interface 316 may detect whether more information has been requested (336). If the user interface 316 does not detect that more information is requested ("NO"), the process may end, repeat, or proceed to another function.

If user interface 316 detects that more information is requested ("YES"), user interface 316 may retrieve additional information from processor 314 (338). In some embodiments, processor 314 may retrieve additional information from memory 312 or from appropriate process control device (s) 310. For example, the additional information may include a set of measurements detected by the pressure sensor. After retrieving the additional information, the user interface 316 may present the additional information for access and review by the user (340).

  4A-4J illustrate exemplary interfaces associated with the system and method. An electronic device, such as any of the electronic devices or computing devices described herein (e.g., the workstation of operator workstation (s) 71) displays the interface on the user interface and / or It may be configured to receive selections and inputs via a user interface. Further, the interface may be associated with software application (s) associated with asset management system 68, as described with respect to FIG. In general, the interface may include data and content associated with the commissioning state of the process control device (s) in the process plant. One or more dedicated applications configured to operate on the electronic device may display an interface, and an individual may have the appropriate credentials to access the application (s).

  The electronic device may receive content included in the interface from one or more components, such as, for example, process control device (s) 310, memory 312, and / or processor 314, as described with respect to FIG. . It should be understood that the interface is merely an example and alternative or additional content is envisioned.

  FIG. 4A shows an interface 400 that may represent the home or launch screen of an application. The interface 400 may be a selectable part or section, ie a project section 401, which may indicate the latest commissioning projects scheduled, completed or in process in the process plant, and the monitoring status of the process control device (eg Monitoring section 402 that may indicate non-responsive, bad, degraded, unknown, and calibration section 403 that may indicate calibration scheduled states (eg, delay, current, impending, later) of the process control device; And a configuration section 404 that may indicate the configuration status of the device (e.g., non-matching, non-baselined, unavailable, etc.).

  FIG. 4B shows an interface 405 that the electronic device may display after detecting the selection of configuration section 404 of FIG. 4A. The interface 405 includes a set of information and content that depicts the configuration of the process control device and how it is compared to the baseline or defined parameters. For example, interface 405 is such that 25 process control devices are "mismatched" (ie, have a configuration that does not match the corresponding defined parameters) and 30 process control devices are not "baselined" A chart that indicates (ie, does not have corresponding defined parameters), that 45 process control devices are "not available" and 800 process control devices are classified as "other" May be included. The interface 405 renders the same information as the chart 406 but may further include a chart 407 shown as a historical line graph. The individual reviews the content in interface 405 and determines the amount and percentage of devices with commissioning data that are inconsistent, otherwise not baselined or otherwise unavailable to the corresponding defined parameters. Can be evaluated effectively and efficiently. In addition, the interface 405 may include selectable content that allows a review of additional information associated with the rendered information by the individual.

FIG. 4C shows an interface 410 that includes process control device specific information. In an embodiment, the electronic device may display interface 410 after detecting a selection of one of the “mismatched” categories, as depicted in interface 405 of FIG. 4B. The interface 410 may include a list 411 of process control devices and information related to a mismatch in commissioning status. For example, the list 411 includes the device "ABB MAG 50XM2000" that is included in "Device Group 1" and has a mismatch of 4 hours with the defined parameters. The individual may review interface 410 to evaluate the state of the process control device (s) and to determine any corrective action to take to correct the difference.

  FIG. 4D illustrates an interface 415 that may include information corresponding to a selected process control device, such as one of the process control devices depicted in interface 410 of FIG. 4C. Interface 415 may include an information section 416 that may indicate commissioning data associated with the selected process control device. In an embodiment, the information section 416 may indicate that the commissioning state data of the process control device does not match the defined parameters, and via the selection 417 of the commissioning state data of the individual and / or of the defined parameters. It may allow access to additional information, such as any or all. Thus, an individual may review the information section 416 to assess the state of the process control device and to determine any corrective action to take to correct the differences.

  FIG. 4E shows an interface 420 that includes information that the electronic device may display after the individual selects selection 417 of FIG. 4D. The interface 420 may include a section 421 detailing the latest known configuration for the process control device and the baseline configuration assigned to the process control device, thereby enabling the assessment of any differences by the individual. Section 421 may be a set of choices selectable by the individual, ie, when selected, may prompt the electronic device to set the baseline configuration of the process control device to the latest known configuration of the process control device Rebaseline selection 422, and when selected, match selection 423, which, when selected, may prompt the electronic device to configure the process control device to match the baseline configuration, and when selected, the electronic device And ignoring selection 421, which may cause section 421 to be dismissed and / or another interface displayed.

  FIG. 4F shows an interface 425 that may include information corresponding to the selected process control device. In an embodiment, the electronic device may display interface 425 after the individual has selected either rebaseline selection 422 or match selection 423 to render in FIG. 4E. As depicted in FIG. 4F, interface 425 indicates that the latest known configuration of the process control device matches the baseline template corresponding to the process control device (426).

  FIG. 4G shows an interface 430 that the electronic device may display after detecting the selection of the project section 401 of FIG. 4A. The interface 430 includes a set of information and content that renders the status of the commissioning project in the process plant (as shown, the "Extend to dual isolation process" project section 401 project). For example, interface 430 may include various charts and graphs that indicate the status (eg, tab / position, connected, device check, system check) of the process control device associated with the commissioning project. The individual may review the content in interface 430 to effectively and efficiently assess the status of the commissioning project. In addition, interface 430 may include selectable content that may allow review of additional information associated with the rendered information by the individual.

FIG. 4H shows an interface 435 that contains process control device specific information. In an embodiment, the electronic device may display interface 435 after detecting a selection included in interface 430 (or another interface). The interface 435 includes a list 436 of process control devices specific to “project X” and information associated with the process control devices. For example, the list 436 includes the device “ABB MAG 50XM2000” included in “device group 1”. The individual may review interface 436 to assess the state of the process control device (s) and to determine any corrective action to correct the error.

  FIG. 4I illustrates an interface 440 that may include information corresponding to a selected process control device, such as one of the process control devices depicted at interface 435 of FIG. 4H. Interface 440 may include an information section 441 that may indicate commissioning status information associated with the selected process control device. Thus, an individual may review the information section 441 to assess the commissioning status of the process control device and to determine any corrective action to correct the error.

  FIG. 4J shows an interface 445 that may include a summary of the commissioning project. In particular, interface 445 indicates scheduled, in-process and / or completed commissioning projects (such as those included in project section 401 of FIG. 4A) as well as their status (eg, in progress, planned, completed). It can. Thus, an individual may review interface 455 to evaluate the status of the commissioning project efficiently and effectively.

  FIG. 5 depicts a block diagram of an exemplary method 500 for accessing commissioning data associated with a set of process control devices in a process plant or simply the devices. According to an embodiment, at least some of the set of process control devices are communicatively coupled to operate in operation within the process plant to control the set of processes. Method 500 may be facilitated by a computing device having one or more process control devices, memory, a user interface and a processor or controller (such as processor 314 described with respect to FIG. 3) that may be in communication with an electronic device.

  Method 500 may begin when the computing device optionally receives a request for commissioning state data associated with the set of process control devices from a user interface (block 505). In embodiments, the user interface may be incorporated as part of a computing device or as another electronic device associated with a process plant.

  The computing device may obtain commissioning state data for each of the set of process control devices (block 510). In an embodiment, the computing device may obtain commissioning status data in response to receiving the request at block 505, or may obtain commissioning status data automatically or in response to another trigger. . In order to obtain commissioning state data, the computing device may retrieve commissioning state data directly (or indirectly) from each of the set of process control devices.

The computing device may access a set of defined commissioning parameters respectively associated with the set of process control devices (block 515). In embodiments, the set of defined commissioning parameters may be stored in memory, may be default parameters, and / or may be modifiable by an individual associated with the process plant. In general, the commissioning state data may include the current configuration of each process control device, and the defined commissioning parameters may include the desired configuration of each process control device.

  The computing device may determine, for each of the set of process control devices, the difference between the respective commissioning state data and the respective defined commissioning parameters (block 520). In an embodiment, the computing device may determine, for each of the set of process control devices, the difference between the respective current configuration and the respective desired configuration. Additionally or alternatively, the computing device may be configured such that a portion of the set of process control devices matches a portion of each of the defined set of commissioning parameters, and a remaining portion of the set of process control devices May be determined to not match the remaining part of each of the defined set of commissioning parameters.

  The computing device may cause the user interface to indicate a set of differences between the set of commissioning state data and the set of defined commissioning parameters (block 525). In embodiments, the user interface may be incorporated as part of a computing device or as another electronic device associated with a process plant. In causing the user interface to indicate the set of differences, the computing device may cause the user interface to select a portion of the set of process control devices that matches a portion of each of the defined set of commissioning parameters, Indicate the remaining part of the set of process control devices that does not match the remaining part of each of the defined set of commissioning parameters. In one implementation, the computing device may receive, via the user interface, a selection of one of the set of process control devices, thus visually distinctive manner (e.g. highlighting) on the user interface Indicate the differences associated with one of the set of process control devices.

  The computing device optionally enables the user to input updates for commissioning state data of at least one of the set of process control devices (block 530). In an embodiment, the user may enter the update via the user interface. Thus, the computing device may store updates to commissioning state data for subsequent access.

  FIG. 6 depicts a block diagram of an exemplary method 600 of presenting a set of process control devices in a process plant or simply commissioning data associated with the devices. According to an embodiment, at least some of the set of process control devices are communicatively coupled to operate in operation within the process plant to control the set of processes. Method 600 may be facilitated by an electronic device having a user interface, or otherwise communicate with a user interface through which the electronic device may communicate with one or more process control devices, memory and other computing devices. Can be configured to

The method 600 may begin when the electronic device receives commissioning status data of a respective process control device for each of the set of process control devices from the controller (block 605). In embodiments, the electronic device may receive commissioning status data, either automatically or in response to a trigger. The electronic device may access a set of defined commissioning parameters respectively associated with the set of process control devices (block 610). In embodiments, the set of defined commissioning parameters may be stored in memory, may be default parameters, and / or may be modifiable by an individual associated with the process plant. In general, the commissioning state data may include the current configuration of each process control device, and the defined commissioning parameters may include the desired configuration of each process control device.

  The electronic device may determine, for each of the set of process control devices, the difference between the respective commissioning state data and the respective defined commissioning parameters (block 615). In embodiments, the electronic device may determine, for each of the set of process control devices, the difference between the respective current configuration and the respective desired configuration. Additionally or alternatively, the electronic device may be configured such that a part of the set of process control devices corresponds to a part of each of the defined set of commissioning parameters and the rest of the set of process control devices It may be determined that a part of A does not coincide with each remaining part of the defined set of commissioning parameters.

  The electronic device may present a set of sections indicating at least some of the set of differences between the set of commissioning state data and the set of defined commissioning parameters in the user interface (block 620). In embodiments, the electronic device may present at least one of a project section, a monitoring section, a calibration section and a configuration section.

  The electronic device may receive a selection of sections of the set of sections via the user interface (block 625). In response to receiving the selection, the electronic device may be associated with a portion of the set of differences at the user interface to present information corresponding to the sections of the set of sections (block 630). In an embodiment, the electronic device may present at least one graph indicating information associated with a portion of the set of differences, the at least one graph indicating a history progression of the portion of the set of differences. Can be instructed. Additionally or alternatively, the electronic device may present a list of some of the set of process control devices having commissioning state data different from the defined commissioning parameters.

  The electronic device may optionally present to the user interface an option to rebaseline the process control device of the set of process control devices and an option to match the baseline of the process control device, with corresponding selections May be detected (block 635). The electronic device modifies the defined commissioning parameters of the process control device to match the commissioning state data of the process control device when the option selection to rebase the process control device is received ("REBASELINE") Do it (block 640) or allow it to be modified (eg, update the defined commissioning parameters stored in memory). If an option selection is received that matches the baseline of the process control device ("MATCH"), does the electronic device configure the process control device according to the defined commissioning parameters of the process control device (block 645), or Let it be configured. In particular, the electronic device may be provided to the process control device with appropriate configuration data for implementation thereon.

  Embodiments of the technology described in this disclosure may include any number of the following aspects, either alone or in combination.

1. A computer-implemented method for accessing commissioning data associated with a set of devices in a process plant, wherein at least some of the set of devices are operating while operating in the process plant to control the set of processes Communicatively connected to each other, the method obtaining, for each of the set of devices at the computing device, commissioning state data of the respective device and a defined commissioning respectively associated with the set of devices Accessing the set of parameters and for each of the set of devices by the computing device between the respective commissioning state data and the respective defined commissioning parameters And determining different, the user interface includes possible to instruct a set of differences between the set of commissioning parameter defined as a set of commissioning state data, the computer-implemented method.

  2. The commissioning state data includes the current configuration of each device, the defined commissioning parameters include the desired configuration for each device, and determining the difference is for each of the set of devices. The computer-implemented method of claim 1, comprising determining a difference between the configuration and each desired configuration.

  3. For each set of devices, it is possible to determine the difference between the respective commissioning state data and the respective defined commissioning parameters, (i) a set of commissioning parameters in which a part of the set of devices is defined And (ii) determine that the remaining part of the set of devices does not match the respective remaining parts of the defined set of commissioning parameters The computer-implemented method of claim 1, comprising:

  4. Having the user interface indicate a set of differences causes the user interface to (i) define a portion of the set of devices that matches a portion of each of the defined set of commissioning parameters, and (ii) define 4. The computer-implemented method of claim 3, comprising: causing the remaining portions of the set of devices that do not match the remaining portions of the set of commissioning parameters to be indicated.

  5. 5. The computer-implemented method of any of the preceding claims, further comprising enabling the user to input an update to the commissioning state data of at least one of the set of devices.

  6. 6. The computer-implemented method of claim 5, wherein enabling the user to input updates to the commissioning state data comprises enabling the user to input updates to the commissioning state data via the user interface.

  7. Receiving a selection of one of the set of devices via the user interface and having the user interface indicate differences associated with one of the set of devices in a visually distinctive manner The computer-implemented method of any one of the preceding claims, further comprising

  8. Obtaining, for each set of devices at the computing device, commissioning state data of the respective device, receiving the request for commissioning state data from the user interface, and the device in response to receiving the request The computer implemented method according to any one of claims 1 to 7, comprising retrieving commissioning state data of the respective device for each of the set of.

9. A system in a process plant for accessing commissioning data associated with the process plant of a device communicatively connected to operate in operation in the process plant to control a set of processes A set, a user interface for presenting content, a memory storing a set of defined commissioning parameters respectively associated with the set of devices, a communication unit, a set of devices, a user interface, a memory and a communication unit Communicate and receive commissioning status data of the respective device from each of the set of devices via the communication unit, and from the memory, defined commissioning parameters respectively associated with the set of devices The set of data is accessed to determine, for each set of devices, the difference between the respective commissioning state data and the respective defined commissioning parameters, and defined in the user interface as the set of commissioning state data A processor configured to cause a set of differences between the set of commissioning parameters to be indicated.

  10. The commissioning state data comprises the current configuration of the respective device, the defined commissioning parameters comprise the desired configuration for the respective device, and the processor determines for each of the set of devices in order to determine the difference. The system of claim 9, wherein the system is configured to determine the difference between the current configuration of and each desired configuration.

  11. In order to determine, for each of the set of devices, the difference between the respective commissioning state data and the respective defined commissioning parameters, the processor (i) a commissioning in which a part of the set of devices is defined Matching part of each of the set of parameters, and (ii) remaining part of the set of devices not matching each remaining part of the defined set of commissioning parameters The system according to claim 9, configured to determine and.

  12. The user interface includes (i) a portion of the set of devices that matches a portion of each of the set of defined commissioning parameters, and (ii) a remaining one of the set of defined commissioning parameters. The system of claim 11, indicating a remaining part of each of the set of devices not matching the part.

  13. The system according to any one of claims 9 to 12, wherein the processor communicates with the user interface via a wireless network connection.

  14. 14. The processor according to any one of claims 9 to 13, wherein the processor is further configured to enable input of updates to commissioning state data of at least one of the set of devices by the user via the user interface. The system described in.

  15. The user interface is configured to receive a selection of one of the set of devices and to indicate, in a visually distinctive manner, a difference associated with one of the set of devices, The system according to any one of claims 9-14.

16. An electronic device for managing commissioning data associated with a process plant, wherein the user interface for presenting content and the electronic device for communicating to operate in operation in the process plant to control a set of processes A transceiver for communicating with a computing device communicatively connected to a set of devices connected to the memory, a memory storing a set of computer executable instructions, a user interface, the transceiver and the memory, and a processor Receiving at least one selection of the set of devices via the user interface; commissioning of at least one of the set of devices from one of the set of devices via the transceiver Retrieving data, wherein commissioning state data indicates a current configuration of at least one of the set of devices, retrieving, defined, associated with at least one of the set of devices Accessing the commissioning parameters, determining the difference between the commissioning state data and the defined commissioning parameters, and causing the user interface to indicate the difference between the commissioning state data and the defined commissioning parameters, A processor configured to execute a set of computer-executable instructions that cause an electronic device to execute.

  17. The processor causes the processor to further cause: (i) the option to rebaseline the devices in the set of devices and (ii) the option to match the device baselines The electronic device of claim 16, configured to execute a set of computer executable instructions.

  18. The processor receiving, via the user interface, the selection of the option to rebase the device through the user interface, and modifying the device's defined commissioning parameters to match the device's commissioning state data 20. The electronic device of claim 17, configured to execute computer-executable instructions to cause further execution.

  19. The processor receiving, via the user interface, the selection of options matching the baseline of the device, and causing the device to be configured to comply with the defined commissioning parameters of the device; 18. The electronic device of claim 17, configured to execute a set of computer executable instructions that further cause:.

  20. The commissioning state data includes the current configuration of each device, and the defined commissioning parameters include the desired configuration for each device, and the processor determines at least one of the set of devices to determine the difference. 20. The electronic device of claims 16-19, configured to determine, for each one, the difference between a respective current configuration and a respective desired configuration.

  21. The processor executes a set of computer executable instructions to further cause the processor to, via the user interface, input of an update to the commissioning state data of the at least one of the set of devices by the user The electronic device according to any one of claims 16 to 20, wherein the electronic device is configured as follows.

  22. A processor is associated with the processor, in response to receiving a selection of at least one of the set of devices, to at least one of the set of devices in a visually distinctive manner to the user interface 22. The electronic device of any of claims 16-21, configured to execute a set of computer executable instructions that further cause the difference to be indicated.

23. A computer implemented method in an electronic device for presenting commissioning data associated with a set of devices in a process plant, wherein at least some of the set of devices control the set of processes in the process plant Communicatively connected to operate during operation, a method is defined for receiving commissioning state data of the respective device for each of the set of devices from the controller and defined respectively associated with the set of devices Accessing the set of commissioning parameters and determining for each of the set of devices by the processor the difference between the respective commissioning state data and the respective defined commissioning parameters; At the user interface, presenting a set of sections indicating at least some of the set of differences between the set of commissioning state data and the set of defined commissioning parameters, and through the user interface Receiving a selection of sections of the set of sections, and presenting information associated with some of the set of differences in the user interface corresponding to the sections of the set of sections; Including computer implemented methods.

  24. Presenting a set of sections indicating at least some of the set of differences in the user interface presenting at least one of a projection section, a monitoring section, a calibration section and a configuration section in the user interface 24. The computer implemented method of claim 23, comprising:

  25. Presenting information associated with some of the set of differences in the user interface presents at least one graph indicating information associated with some of the set of differences in the user interface 25. A computer implemented method according to any one of claims 23 or 24, including.

  26. 26. The computer of claim 25, wherein presenting at least one graph in the user interface comprises presenting at least one graph indicating historical progression of a portion of the set of differences in the user interface. Implementation method.

  27. Presenting information associated with some of the set of differences in the user interface is a list of some of the set of devices having commissioning state data different from the defined commissioning parameters in the user interface 25. The computer-implemented method of any one of claims 23 or 24, comprising presenting.

  28. 28. The user interface according to any of claims 23-27, further comprising presenting (i) an option to re-baseline a device of the set of devices and (ii) an option to match the device's baseline. A computer implemented method according to any one of the preceding claims.

  29. Claim further comprising receiving a selection of options to rebase the device via the user interface, and modifying the defined commissioning parameters of the device to match the commissioning state data of the device. 29. The computer implemented method of claim 28.

  30. 29. The computer of claim 28, further comprising: receiving, via a user interface, a selection of options to match a baseline of the device; and causing the device to conform to defined commissioning parameters of the device. Implementation method.

  In addition, the foregoing aspects of the present disclosure are merely exemplary and are not intended to limit the scope of the present disclosure.

The following additional considerations apply to the above considerations. Throughout the specification, operations described as being performed by any device or routine generally refer to an operation or process of a processor that manipulates or converts data in accordance with machine-readable instructions. Machine readable instructions may be stored on and obtained from a memory device communicatively coupled to the processor. In other words, the methods described herein may be embodied by a series of machine executable instructions stored on a computer readable medium (ie, on a memory device). The instructions, when executed by one or more processors of corresponding devices (eg, operator workstations, commissioning tools, etc.), cause the processors to perform the method. An instruction, routine, module, process, service, program, and / or application is "stored" and is referred to herein as being stored or stored on computer readable memory or on computer readable media. The term "saved" is intended to exclude temporal signals.

  In addition, the terms “operator”, “personnel”, “person”, “user”, “technician”, “administrator”, and Similar other terms are used to describe persons in the process plant environment that may use or interact with the systems, devices, and methods described herein, but these terms are: It is not intended to be limiting. Where specific terms are used in the description, the terms are used, in part, due to the conventional activities that plant employees engage in, but to limit the employees who can engage in specific activities. Not intended.

  Additionally, throughout the specification, cases may implement components, operations, or structures described as a single case. Although individual acts of one or more methods are illustrated and described as separate acts, one or more of the individual acts may be performed simultaneously, and the acts need to be performed in the order illustrated. Absent. Structures and functionality presented as separate components in the exemplary configuration may be implemented as a combined structure or component. Similarly, structures and functionality presented as a single component may be implemented as separate components. These and other variations, modifications, additions and improvements are within the scope of the subject matter herein.

  For example, unless stated otherwise, for example, "processing", "computing", "calculating", "determining", "identifying" Using words such as "presenting", "causing to be presented", "causing to be displayed", "displaying" The discussion herein may refer to one or more memories (eg, volatile memory, non-volatile memory, or a combination thereof), registers, or other machine configuration that receives, stores, transmits, or displays information. Motonai physical (e.g., electrical, magnetic, biological or optical) machine to manipulate or transform data represented as the amount (e.g., a computer) may refer to operation or process.

When implemented in software, any of the applications, services, and engines described herein may be magnetic disks, laser disks, solid state memory devices, molecular memory storage devices, or other such as RAM or ROM in a computer or processor. May be stored in any tangible non-transitory computer readable memory, such as a storage medium. Although the exemplary systems disclosed herein are disclosed to include, among other components, software and / or firmware executing on hardware, such systems are merely exemplary. It should be noted that there is only one and should not be considered limiting. For example, it is contemplated that any or all of these hardware, software, and firmware components may be embedded only in hardware, only in software, or in any combination of hardware and software. . Thus, one skilled in the art will readily understand that the provided examples are not the only way of implementing such a system.

  Thus, although the present invention has been described with respect to specific examples, these examples are merely illustrative and are not intended to be limiting of the present invention, and changes, additions, or omissions may be made. It will be apparent to those skilled in the art that the disclosed embodiments may be practiced without departing from the spirit and scope of the invention.

A term is defined in this patent to mean "herein ... (As used herein, the term '________' is hereby
defined to mean. . . Unless the context of the document is clearly defined using the statement "or similar statement," it is intended to limit the meaning of the term either explicitly or implicitly beyond its plain or ordinary meaning. It should be understood that such terms are not to be construed as limiting the scope based on any statement made in any of the patent's terms (except in the language of the claims). It should not be done. At the end of this patent it is merely for clarity not to confuse the reader, that any term stated in the claims at the end of the patent is mentioned in this patent in a manner consistent with a single meaning. It is not, however, intended that such claimed language is intended to be limiting or otherwise limiting to that single meaning. Finally, the scope of elements of any claim is inferred unless elements of the claims are defined by listing the word "means" and functions without the recitation of any structure. It is not intended to be interpreted based on the application of US Patent Act 112 (f) and / or former US Patent Act 112, sixth paragraph.

  Further, while the above text provides a detailed description of many different embodiments, it is understood that the scope of this patent is defined by the terms of the claims set forth at the end of this patent. It should. The detailed description is to be construed as merely illustrative, and it is impractical, if not impossible, to describe every possible embodiment, so that all possible embodiments It is not an explanation. Many alternative embodiments may be implemented using either current technology or technology developed after the filing date of this patent, but these will still fall within the scope of the claims. I will.

Claims (30)

A computer-implemented method for accessing commissioning data associated with a set of devices in a process plant, wherein at least some of the sets of devices are operating in the process plant to control the set of processes. Communicatively connected to operate in the above method,
Obtaining commissioning status data of the respective device at each of the set of devices at a computing device;
Accessing a set of defined commissioning parameters respectively associated with the set of devices;
Determining for each of the set of devices by the computing device the difference between the respective commissioning state data and the respective defined commissioning parameters;
And C. causing the user interface to indicate the set of differences between the set of commissioning state data and the set of defined commissioning parameters. Said commissioning state data comprising the current configuration of said respective device, said defined commissioning parameters comprising the desired configuration for said respective device, and determining said differences;
The computer-implemented method of claim 1, comprising determining, for each of the set of devices, the difference between the respective current configuration and the respective desired configuration. Determining the difference between the respective commissioning state data and the respective defined commissioning parameters for each of the set of devices;
(I) a part of the set of devices corresponds to a part of each of the set of defined commissioning parameters; and (ii) a remaining part of the set of devices is the The computer-implemented method of claim 1, including determining not to match a portion of each of the defined set of commissioning parameters. Having the user interface indicate the set of differences;
In the user interface, (i) the portion of the set of devices that matches the portion of the defined set of commissioning parameters and (ii) the set of defined commissioning parameters 4. The computer-implemented method of claim 3, comprising: causing the remaining portion of the set of devices not to match the portion of the respective remaining portion of the.   The computer-implemented method of claim 1, further comprising enabling the user to input updates to the commissioning state data of at least one of the set of devices. Allowing the user to input the update to the commissioning state data by:
The computer-implemented method of claim 5, comprising enabling input of the update to the commissioning state data by the user via the user interface. Receiving a selection of one of the set of devices via the user interface;
The computer-implemented method of claim 1, further comprising: causing the user interface to indicate the difference associated with the one of the set of devices in a visually distinctive manner. Obtaining the commissioning status data of the respective device for each of the set of devices at the computing device;
Receiving a request for the commissioning state data from the user interface;
The computer-implemented method of claim 1, comprising, in response to receiving the request, retrieving the commissioning state data of the respective device for each of the set of devices. A system in the process plant for accessing commissioning data associated with the process plant, the system
A set of devices communicatively connected to operate in operation within said process plant to control a set of processes;
A user interface for presenting content;
A memory storing a set of defined commissioning parameters associated with each of the set of devices;
Communication unit,
Communicating with the set of devices, the user interface, the memory and the communication unit, and receiving commissioning status data of the respective devices from each of the set of devices via the communication unit;
Accessing from the memory a set of the defined commissioning parameters respectively associated with the set of devices;
Determining the difference between the respective commissioning state data and the respective defined commissioning parameters for each of the set of devices;
A processor configured to cause the user interface to indicate the set of differences between the set of commissioning state data and the set of defined commissioning parameters. The commissioning state data comprises the current configuration of the respective device, the defined commissioning parameters comprise the desired configuration for the respective device, and in order to determine the difference, the processor is configured to:
10. The system of claim 9, wherein for each of the set of devices, the difference between the respective current configuration and the respective desired configuration is determined. The processor, for each of the set of devices, determines the difference between the respective commissioning state data and the respective defined commissioning parameters,
(I) a part of the set of devices corresponds to a part of each of the set of defined commissioning parameters; and (ii) a remaining part of the set of devices is the 10. The system of claim 9, configured to determine that it does not match a portion of each of the defined set of commissioning parameters.   The user interface comprises (i) the portion of the set of devices that matches the portion of the set of defined commissioning parameters, and (ii) the set of defined commissioning parameters. The system of claim 11, indicating a portion of the remaining of the set of devices not matching the portion of the respective remaining ones of the.   The system of claim 9, wherein the processor communicates with the user interface via a wireless network connection. Said processor
The system according to claim 9, further configured to enable input of updates to the commissioning state data of at least one of the set of devices by a user via the user interface. The user interface
Receive a selection of one of the set of devices,
10. The system of claim 9, configured to indicate the difference associated with one of the set of devices in a visually distinctive manner. An electronic device for managing commissioning data associated with a process plant, comprising:
A user interface for presenting content;
A transceiver for communicating with a computing device communicatively connected to the set of devices communicatively connected to operate in operation within the process plant to control the set of processes;
A memory for storing a set of computer executable instructions;
In communication with the user interface, the transceiver and the memory, and to the processor,
Receiving a selection of at least one of the set of devices via the user interface;
Retrieving said at least one commissioning state data of said set of devices from said one of said set of devices via said transceiver, said commissioning state data being of said set of devices Indicating, retrieving, the current configuration of the at least one of:
Accessing defined commissioning parameters associated with the at least one of the set of devices;
Determining the difference between the commissioning state data and the defined commissioning parameter, and causing the user interface to indicate the difference between the commissioning state data and the defined commissioning parameter A processor configured to execute the set of computer-executable instructions. The processor is operable to:
The computer further causing the user interface to present (i) an option to rebaseline a device of the set of devices and (ii) an option to match the baseline of the device. The electronic device of claim 16 configured to execute a set of executable instructions. The processor is operable to:
Receiving a selection of the option to rebaseline the device via the user interface;
Claiming is also made to execute the set of computer executable instructions further causing modifying the defined commissioning parameters of the device to match the commissioning state data of the device. The electronic device according to 17. The processor is operable to:
Receiving, via the user interface, a selection of the option that matches a baseline of the device;
18. The computer readable medium of claim 17 configured to execute the set of computer executable instructions to further cause the device to be configured to follow the defined commissioning parameters of the device. Electronic device as described. The commissioning state data comprises the current configuration of the respective device, the defined commissioning parameters comprise the desired configuration for the respective device, and in order to determine the difference, the processor is configured to:
The electronic of claim 16 configured to determine, for each of the at least one of the set of devices, the difference between the respective current configuration and the respective desired configuration. device. The processor is operable to:
To execute the set of computer-executable instructions that further cause a user to input updates to the commissioning state data of the at least one of the set of devices via the user interface The electronic device of claim 16 configured. The processor is operable to:
Associated with the at least one of the set of devices in a visually distinctive manner to the user interface in response to receiving the selection of the at least one of the set of devices 17. The electronic device of claim 16, configured to execute the set of computer executable instructions to further cause indicating the difference. A computer-implemented method in an electronic device for presenting commissioning data associated with a set of devices in a process plant, wherein at least some of the sets of devices control the set of processes. Communicably connected to operate in operation within the said method,
Receiving commissioning status data of the respective device from the controller for each of the set of devices;
Accessing a set of defined commissioning parameters respectively associated with the set of devices;
Determining by the processor, for each of the set of devices, the difference between the respective commissioning state data and the respective defined commissioning parameters;
Presenting in the user interface a set of sections indicating at least some of the set of differences between the set of commissioning state data and the set of defined commissioning parameters;
Receiving a selection of a section of the set of sections via the user interface;
Presenting information associated with a portion of the set of differences and corresponding to the section of the set of sections in the user interface. Presenting in the user interface the set of sections indicating the at least some of the set of differences;
24. The computer-implemented method of claim 23, comprising presenting at least one of a projection section, a monitoring section, a calibration section, and a configuration section in the user interface. Presenting the information associated with the portion of the set of differences in the user interface;
24. The computer-implemented method of claim 23, comprising presenting at least one graph indicating the information associated with the portion of the set of differences in the user interface. Presenting the at least one graph in the user interface;
26. The computer-implemented method of claim 25, comprising presenting the at least one graph indicating history progression of the portion of the set of differences in the user interface. Presenting the information associated with the portion of the set of differences in the user interface;
24. The computer-implemented method of claim 23, comprising presenting, at the user interface, a list of some of the set of devices having commissioning state data different from the defined commissioning parameters.   24. The method of claim 23, further comprising: presenting at the user interface (i) an option to rebaseline a device of the set of devices and (ii) an option to match the baseline of the device. The computer-implemented method described in. Receiving a selection of the option to rebaseline the device via the user interface;
29. The computer-implemented method of claim 28, further comprising: modifying the defined commissioning parameters of the device to match the commissioning state data of the device. Receiving, via the user interface, a selection of the option that matches a baseline of the device;
29. The computer-implemented method of claim 28, further comprising: causing the device to follow the defined commissioning parameters of the device.