Method, system and computer program product for commissioning field devices in a control system

Abstract

The present invention can debug field devices in a control system by performing the following steps: (i) detecting a connection event including a field device and an I / O port communicatively coupled to a server through an interface; (ii) extracting a first field device identifier corresponding to the field device from a memory of the field device interface-connected to the I / O port; (iii) extracting field device configuration data associated with the I / O port from a non-transitory memory database communicatively coupled to the server; (iv) generating one of a transformed first field device identifier and a transformed second field device identifier based on predefined transformation data; (v) comparing the transformed first field device identifier with the second field device identifier, or comparing the first field device identifier with the transformed second field device identifier; (vi) generating a connection check output decision based on the comparison output; and (vii) optionally, triggering a connection check output event based on the connection check output decision.

Description

Technical Field

[0001] The present invention relates to the field of industrial automation and process control systems. More specifically, the present invention provides a method, system, and computer program product for performing a field device connection check during the commissioning process of field devices in a control system. Background Art

[0002] Industrial environments implement control systems (e.g., distributed process control systems) for operating and controlling processes for manufacturing, transforming, or producing. A control system typically includes one or more process controllers connected to one or more field devices. Field devices can include valves, valve actuators, switches, and transmitters (e.g., temperature sensors, pressure sensors, level sensors, and flow sensors) located in an industrial environment and are configured for physical control functions or process control functions. Examples of field device control functions include opening or closing a valve and measuring process parameters and / or environmental parameters (e.g., temperature or pressure) for controlling one or more processes in a processing plant or system.

[0003] On the other hand, a process controller in a control system can be configured to receive signals generated by field devices, where the received signals convey information corresponding to process parameters measured by the field devices and / or other information related to the state of the field devices. The process controller can additionally execute control applications that implement one or more control modules for making process control decisions. Control modules in the process controller send control signals to field devices via communication lines or connections to control the operation of one or more field devices. Input / output (I / O) devices can transfer data and control instructions between the process controller and field devices by converting electrical signals into digital values and sending and receiving such signals via one or more communication protocols, where the input / output (I / O) devices are arranged as communication intermediaries between the process controller and one or more field devices.

[0004] The control system in a processing plant may include one or more process controllers, and each controller is connected to one or more field devices via I / O cards and / or I / O ports. The one or more controllers store control applications and implement control strategies for controlling and operating the field devices. The control system can be configured to trace or collect data regarding individual plant assets or plant equipment, which assets and equipment include, but are not limited to, field devices, rotating equipment, and critical machinery. The control system stores device-related data and / or performance data for all devices or assets in a plant or a group of plants in an extractable manner to monitor the status and health of plant assets and perform maintenance work. Additionally, the control system can be configured to act as a communication intermediary between a plant operator or operator terminal on one side and one or more field devices on the other side to enable effective configuration, commissioning, inspection, and maintenance of such field devices.

[0005] For the present specification, it should be understood that a "field device" may include any one of a valve, valve actuator, switch, transmitter, smart transmitter, positioner, or other sensor device that may be located in an industrial process environment and configured for physical control functions or process control functions. Field devices may include "smart" field devices, i.e., devices that support digital communication protocols such as HART, Foundation Fieldbus communication protocol.

[0006] For the present specification, the "control system" should be understood to refer to any control system that can be implemented in a process control environment, industrial plant, or industrial environment, and should include a distributed control system (DCS) and / or a safety control system (SCS).

[0007] Figure 1 A process control environment 100 of the type that can be used for process control in an industrial environment is shown. The process control environment 100 includes an operator terminal 102, a control system 104, and a field device network 106.

[0008] The operator terminal 102 includes any processor-implemented terminal device or client device communicatively coupled to the control system 104. The operator terminal 102 can be configured such that an operator can transmit instructions to the control system 104 and receive data from the control system 104.

[0009] The control system 104 includes a control system server 104a, a control system database 104b, and a control system gateway interface 104c. The control system server 104a may include at least one processor and one or more transient memories and / or non-transient memories. The control system server 104a may be configured to implement one or more functions of the above process controller. The control system database 104b may include a non-transient memory-based database configured to store data records corresponding to field devices, including, for example, device parameter data, device configuration data, device description files, and corresponding device documentation. The control system gateway interface 104c may include a hardware network gateway or a software network gateway configured to be capable of sending and receiving communications through the control system 104.

[0010] During the process of setting up or upgrading a plant, new field devices are registered, installed, and configured in the control system of the plant facility. In Figure 2 The flowchart of shows the conventional process of registering, installing, and configuring field devices in the control system of a plant facility.

[0011] Figure 2 Step 202 of includes performing front end engineering design (FEED) for plant construction, where FEED focuses on identifying and formulating the technical requirements for a new or upgraded control system for entering the execution phase. Step 204 includes model selection of the field devices to be procured for the new or upgraded distributed control system to meet the technical requirements generated by FEED.

[0012] In step 206, the field devices identified in the model selection step are manufactured or procured by the manufacturer. In step 208, the field devices are installed in the plant facility. The installation step includes: coupling the field devices to the control system in a communicable manner; configuring the field devices for operation in the control system; and configuring the control system and / or the software implemented thereon to control the field devices and communicate with the installed field devices. It should be understood that for the purposes of the specification written in this article, coupling the field devices to the control system in a communicable manner includes: connecting the field devices to the I / O ports of the control system. The term "I / O port" refers to the terminals or terminal slots of the I / O cards coupled to the control system and is intended to represent various I / O ports known in the art, including but not limited to HART, Foundation Fieldbus I / O ports.

[0013] Pre-commissioning of the installed field devices is performed in step 210. The steps for pre-commissioning the field devices include: inspecting the equipment, checking whether each unit and facility conforms to the design (such as piping and instrumentation diagram (P&ID)), flushing, cleaning, pressure testing, functional testing, simulation, and one or more of other forms of device testing.

[0014] Then, step 212 includes commissioning the new or upgraded plant facilities, including verification and validation processes, to confirm that the field devices, equipment, facilities, or industrial plant will perform one or more functions specified according to the design objectives or specifications.

[0015] During the pre-commissioning phase (step 210) of the plant, pre-commissioning operations typically performed by an EPC (engineering, procurement, and construction) consultant / contractor (e.g., the plant builder) are applicable. One of these operations includes an inspection step that checks whether field devices connected to the control system I / O ports can be detected in the control system.

[0016] The step of inspecting the field devices connected to the control system I / O ports is typically the first task in the pre-commissioning task list performed by the EPC consultant / contractor and usually occurs after the physical wiring of the industrial plant is completed. Other tasks performed as part of the pre-commissioning process, either concurrently with or in the vicinity of the connection check step, include range checks, linearization checks, and loop checks.

[0017] The field devices are communicatively coupled to the control system in a manner such that each field device is typically connected one-to-one with an I / O port. Each I / O port is in turn communicatively coupled to a corresponding software function block or software control module, the corresponding software function block or software control module being associated with the I / O port and implemented in one or more processors in the control system. The software function block or software control module includes processor-executable instructions for controlling the functionality of the field device via the I / O port. Thus, it is to be understood that each field device is connected end-to-end to a corresponding software function block or software control module, or communicatively coupled to a corresponding software function block or software control module, and each such software function block or software control module is specifically written to control the function of a particular field device. The software function block or software control module for each I / O port is configured to operate based on one or more defined "field device specific" parameters. In certain cases, such "field device specific" parameters should allow for proper functioning of the field device and / or the control system, provided that they are applied to any field device of a particular field device type, but will not provide the desired or predictable output when applied to a field device of any other field device type. In other cases, the field device specific parameters may only be suitable for application to a particular instance of a field device and will not provide the desired or predictable output when applied to any other field device of the same field device type or any other field device type.

[0018] Accordingly, it is important that the commissioning or pre-commissioning process includes the step of, during the engineering phase of the control system, verifying that the field devices communicatively coupled to the I / O ports in the control system are in fact specifically identified as the particular field devices suitable for connection to such I / O ports. This ensures that the connected field devices are the same devices for which the software function blocks or software control modules corresponding to the I / O ports have been configured or written, and ensures that the software function blocks or software control modules are executed in a predictable and expected manner.

[0019] Figure 3 A conventional method for checking the field devices connected to the I / O ports of the control system is shown.

[0020] Step 302 includes detecting the connection between the field device and the I / O port of the control system. Based on signals generated or sent by the field device or by the I / O port or by the I / O card corresponding to the I / O port, the control system can detect the connection in response to the connection of the field device to the I / O port and what signals are received at the control system.

[0021] In step 304, the control system sends a connection check request to the field device that has been coupled to the I / O port.

[0022] In step 306, the control system receives a response to the connection check request from the field device, where the response typically includes basic information corresponding to the field device, including, for example, a physical device tag, manufacturer information, model information, device revision information, etc.

[0023] In step 308, in response to the control system receiving an initial response from the field device in step 304, further physical verification of the field device is performed, where an operator or other individual is required to: (i) visually view a display integrated into the field device itself, and / or (ii) disconnect the field device to ascertain that the field device has been correctly connected to the I / O port.

[0024] According to Figure 3 conventional methods taught have various drawbacks.

[0025] First, this method only checks whether a field device is physically connected and detected at the I / O port. However, the method cannot verify whether the correct field device has been coupled to the I / O port, and cannot verify whether the field device is thus correctly coupled or connected to a software function block or software control module configured to correctly control the device. Thus, as observed in a factory with a large number of field devices and I / O ports, it is possible that a field device connected to an I / O port is not the field device intended or designed to be connected to the particular I / O port, and thus cannot be correctly monitored or controlled by the software function block or software control module controlling the particular I / O port.

[0026] In this case, even if the prior art methods (of the type described in conjunction with Figure 3 are fully implemented for connection checking, the control system or the control system operator cannot determine whether an incorrect field device has been connected to a particular I / O port. Additionally, in the case where an incorrect device arrangement or connection is not detected during the pre-commissioning or commissioning phase, monitoring and controlling such an incorrectly connected field device by the control system will often result in unwanted or undesirable (and potentially catastrophic) results. As a result, at certain stages, when the error is finally detected, the EPC consultant or contractor will need to trace and fix the problem, which can be time-consuming and expensive, and often leads to more problems, especially due to the limited time available during the pre-commissioning or commissioning phase.

[0027] Therefore, a solution is needed that can identify the following situation, that is, the field device connected to the I / O port is not the correct field device, that is, it is different from the field device that the control system (or the software function block or software control module in the control system) is configured to monitor and / or control through a specific I / O port. SUMMARY OF THE INVENTION

[0028] The present invention relates to the field of industrial automation and process control systems. More specifically, the present invention provides a method, a system, and a computer program product for performing a field device connection check during commissioning of a field device in a control system.

[0029] In an embodiment, the present invention provides a method for commissioning a field device in a control system, the control system including at least one server and a plurality of input / output (I / O) ports communicatively coupled to the server. The method includes: (i) detecting a connection event, the connection event including a field device and an I / O port communicatively coupled to the server being connected through an interface, (ii) extracting a first field device identifier corresponding to the field device from a memory of the field device connected to the I / O port through the interface, (iii) extracting field device configuration data associated with the I / O port from a non-transitory memory database communicatively coupled to the server, wherein (a) a set of field device attributes includes a second field device identifier, and (b) at least one segment of the second field device identifier is different from a corresponding segment of the first field device identifier, (iv) generating one or both of a transformed first field device identifier and a transformed second field device identifier based on predefined transformation data, and (v) triggering an alert to be generated in a user interface in response to determining that (c) the transformed first field device identifier does not match the second field device identifier, (d) the transformed second field device identifier does not match the first field device identifier, or (e) the transformed first field device identifier does not match the transformed second field device identifier.

[0030] In an embodiment of the method, a rectification action may be implemented in response to determining that the transformed first field device identifier does not match the second field device identifier or the transformed second field device identifier does not match the first field device identifier. In implementing the rectification action, (i) the first field device identifier in the local memory of the field device may be modified or updated, (ii) the field device may be decoupled from the I / O port, or (iii) at the location of the field device having a mismatched first field device identifier, another field device having a first field device identifier that matches the second field device identifier may be coupled to the I / O port.

[0031] In a method embodiment, the field device configuration data can include a subset of engineering data, design data, or design specifications corresponding to a process control system.

[0032] In another method embodiment, the field device configuration data identifies a set of field device attributes corresponding to a specified field device that has been identified for interfacing with an I / O port.

[0033] In a particular method embodiment, a connection event includes coupling a field device to an I / O port.

[0034] In one embodiment of the method, the predefined conversion data includes a conversion table or conversion rules.

[0035] In a particular embodiment of the method, generating a converted first field device identifier includes the step of transforming the first field device identifier based on applying a conversion table or conversion rules to the first field device identifier.

[0036] In another embodiment of the method, generating a converted second field device identifier includes the step of transforming the second field device identifier based on applying a conversion table or conversion rules to the second field device identifier.

[0037] In another embodiment of the method, the predefined conversion data includes a conversion rule for converting a physical device label or system label represented by a first expression to a second expression.

[0038] In a particular method embodiment, (i) the predefined conversion data includes a conversion table that maps a first set of letters, numbers, or alphanumeric strings to a second set of letters, numbers, or alphanumeric strings, and (ii) converting the first field device identifier or the second field device identifier based on the conversion table includes: (i) identifying in the conversion table a mapping record that can convert at least a segment of the first field device identifier or the second field device identifier from a first expression to a second expression, and (ii) replacing a segment of the first field device identifier or the second field device identifier that matches the first letter, number, or alphanumeric string identified in the identified mapping record with the second letter, number, or alphanumeric string that is mapped to the first letter, number, or alphanumeric string in the identified mapping record.

[0039] In another embodiment of the method, (i) the predefined conversion data includes a conversion table that maps a first set of letters, numbers, or alphanumeric strings including one or more subsets of wildcards to a second set of letters, numbers, or alphanumeric strings also including one or more subsets of wildcards, (ii) a converted first field device identifier is generated based on the first field device identifier, and (iii) a converted second field device identifier is generated based on the second field device identifier, wherein converting each of the first field device identifier and the second field device identifier includes: (i) identifying in the conversion table a mapping record that can cause at least one segment of the first field device identifier or the second field device identifier to be converted from a first expression to a second expression, and (ii) replacing one or more non-wildcard segments in the first field device identifier or the second field device identifier that match the first non-wildcard segment in the identified mapping record's first letter, number, or alphanumeric string with one or more non-wildcard segments in the second letter, number, or alphanumeric string mapped to the identified mapping record's first letter, number, or alphanumeric string.

[0040] The present invention also provides a system for commissioning field devices in a control system, the control system including: at least one server and a plurality of input / output (I / O) ports communicatively coupled to the server. The system for commissioning field devices includes a memory and at least one processor configured to (i) detect a connection event, the connection event including a field device and an I / O port communicatively coupled to the server being connected through an interface, (ii) extract from the memory of the field device connected through the interface a first field device identifier corresponding to the field device, (iii) extract from a non-transitory memory database communicatively coupled to the server field device configuration data associated with the I / O port, wherein (a) a set of field device attributes includes a second field device identifier, and (b) at least one segment of the second field device identifier is different from a corresponding segment of the first field device identifier, (iii) generate one or both of a converted first field device identifier and a converted second field device identifier based on predefined conversion data, and (iv) in response to determining that (c) the converted first field device identifier does not match the second field device identifier, (d) the converted second field device identifier does not match the first field device identifier, or (e) the converted first field device identifier does not match the converted second field device identifier, trigger an alert to be generated in the user interface.

[0041] The system can be configured to perform a corrective action in response to determining that the converted first field device identifier does not match the second field device identifier, or in response to determining that the converted second field device identifier does not match the first field device identifier, wherein, in performing the corrective action, (i) the first field device identifier in the local memory of the field device can be modified or updated, (ii) the field device can be decoupled from the I / O port, or (iii) at the location of the field device having the mismatched first field device identifier, another field device having a first field device identifier that matches the second field device identifier can be coupled at the I / O port.

[0042] The system can be configured such that the field device configuration data is a subset of engineering data, design data, or design specifications corresponding to the control system.

[0043] In an embodiment of the system, the field device configuration data identifies a set of field device attributes corresponding to a specified field device that has been identified as being interfaced with the I / O port.

[0044] In another embodiment of the system, the connection event includes coupling the field device to the I / O port.

[0045] The system can be configured such that the predefined conversion data includes a conversion table or conversion rules.

[0046] In a particular embodiment of the system, generating the converted first field device identifier includes the step of transforming the first field device identifier based on the application of a conversion table or conversion rules to the first field device identifier.

[0047] The system can be configured such that generating the converted second field device identifier includes the step of transforming the second field device identifier based on the application of a conversion table or conversion rules to the second field device identifier.

[0048] In another embodiment, the system can be configured such that the predefined conversion data includes a conversion rule for converting a physical device tag or system tag represented by a first expression to a second expression.

[0049] In a particular embodiment of the system, (i) the predefined conversion data includes a conversion table that maps a first set of letters, numbers, or alphanumeric strings to a second set of letters, numbers, or alphanumeric strings, and (ii) converting the first field device identifier or the second field device identifier based on the conversion table includes: (i) identifying, in the conversion table, a mapping record that enables at least a segment of the first field device identifier or the second field device identifier to be converted from a first expression to a second expression, and (ii) replacing a segment of the first field device identifier or the second field device identifier that matches the first letter, number, or alphanumeric string identified in the identified mapping record with the second letter, number, or alphanumeric string that is mapped to the first letter, number, or alphanumeric string identified in the identified mapping record.

[0050] In another embodiment of the system, (i) the predefined conversion data includes a conversion table that maps a first set of letters, numbers, or alphanumeric strings, each of which includes one or more subsets each including a wildcard, to a second set of letters, numbers, or alphanumeric strings, each of which also includes one or more subsets each including a wildcard, (ii) generating a converted first field device identifier based on the first field device identifier, and (iii) generating a converted second field device identifier based on the second field device identifier, wherein converting each of the first field device identifier and the second field device identifier includes: (i) identifying, in the conversion table, a mapping record that enables at least a segment of the first field device identifier or the second field device identifier to be converted from a first expression to a second expression, and (ii) replacing one or more non-wildcard segments of the first field device identifier or the second field device identifier that match the first non-wildcard segment of the first letter, number, or alphanumeric string in the identified mapping record with one or more non-wildcard segments of the second letter, number, or alphanumeric string that is mapped to the first letter, number, or alphanumeric string identified in the identified mapping record.

[0051] The present invention also provides a computer program product for debugging field devices in a control system, the control system including at least one server and a plurality of input / output (I / O) ports communicatively coupled to the server. The computer program product includes a non-transitory computer-usable medium having computer-readable program code embedded therein, the computer-readable program code including instructions for performing the following steps in a processor-based computing system: (i) detecting a connection event, the connection event including a field device and an I / O port communicatively coupled to the server being connected through an interface, (ii) extracting a first field device identifier corresponding to the field device from a memory of the field device connected to the I / O port through the interface, (iii) extracting field device configuration data associated with the I / O port from a non-transitory in-memory database communicatively coupled to the server, wherein (a) a set of field device attributes includes a second field device identifier, and (b) at least one segment of the second field device identifier is different from a corresponding segment of the first field device identifier, (iv) generating one or both of a transformed first field device identifier and a transformed second field device identifier based on predefined transformation data, and (v) triggering an alert to be generated in a user interface in response to determining that (c) the transformed first field device identifier does not match the second field device identifier, (d) the transformed second field device identifier does not match the first field device identifier, or (e) the transformed first field device identifier does not match the transformed second field device identifier. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] Figure 1 illustrates a process control environment typically found in an industrial plant or environment;

[0053] Figure 2 is a flowchart showing a conventional process for upgrading or setting up plant facilities;

[0054] Figure 3 is a flowchart showing a conventional method for performing an inspection of a field device connected to a control system;

[0055] Figure 4 is a flowchart showing a method for performing an inspection of a field device connected to a control system that can be implemented in accordance with the teachings of the present invention;

[0056] Figure 5 illustrates an exemplary display interface for importing engineering data for a method for Figure 4 ;

[0057] Figure 6 illustrates a display interface for displaying exemplary field device configuration data generated according to the method steps of Figure 4 ;

[0058] Figure 7shows a first embodiment of a display interface that displays exemplary conversion data generated according to Figure 4 the method steps;

[0059] Figure 8 shows a second embodiment of a display interface that displays exemplary conversion data generated according to Figure 4 the method steps;

[0060] Figure 9A is a flowchart that describes a specific embodiment of the steps for connection check according to Figure 4 the method steps;

[0061] Figure 9B shows an exemplary user interface for the steps of connection check for an embodiment for implementing the method steps according to Figure 9A the method steps;

[0062] Figure 10 shows an exemplary interface for comparing a physical device tag and a system device tag corresponding to a specific I / O port;

[0063] Figure 11 shows an exemplary connection check report that can be generated as the output of the type of Figure 4 the method steps;

[0064] Figure 12 shows a process control environment configured according to the teachings of the present invention;

[0065] Figure 13 shows an exemplary computer system according to which various embodiments of the present invention can be implemented. DETAILED DESCRIPTION

[0066] The present invention relates to the field of industrial automation and process control systems. More specifically, the present invention provides methods, systems, and computer program products that are capable of performing field device connection checks during commissioning of field devices in a control system.

[0067] For the purposes of the specification written hereinafter, the terms "field device" and "sensor" may be used interchangeably and should be understood to refer to such a device or component that is configured to monitor or control parameters corresponding to one or more assets, devices, components, tags, hardware, software, or data parameters in an industrial environment.

[0068] For the purposes of the specification written below, the term "physical device tag" shall mean the device name or device identifier associated with an actual field device. Ideally, each field device located in an industrial environment or coupled to a control system in an industrial environment is provided with a unique physical device tag. Generally, each field device is provided with local memory, and the physical device tag corresponding to the field device is stored in the local memory in an extractable manner. When the field device is coupled to the control system, for the operation, control, or monitoring of the field device, the control system can extract and read the physical device tag corresponding to the field device and use such physical device tag as the unique identifier corresponding to the field device.

[0069] For the purposes of the specification written below, the term "system tag" shall mean the name or identifier uniquely associated with a software function block or software control module in a control system, the software function block or software control module being configured to control, monitor, or interface with a particular field device. Ideally, each software function block of the software control module configured to control, monitor, or interface with a field device is provided with a unique system tag. The system tag is used by the control system to implement, control, and / or operate the corresponding software function block or software control module.

[0070] The purpose of the field device connection check according to the present invention is to support the evaluation and inspection of field devices and their corresponding connections to the control system. The expected result of the field device connection check is to minimize or eliminate the connection of field devices at incorrect locations and / or incorrect I / O ports in the control system. In various embodiments, the connection check may include any one or more of the following:

[0071] · Communication check - The control system determines whether it can communicate with the field device

[0072] · Obtain device information and perform tag comparison - The control system evaluates whether the field device information imported from the engineering data based on which the control system has been configured matches the field device information extracted from the field device actually connected to the control system.

[0073] · Physical check - Check the actual location of the field device in the industrial plant and may include one or more of the following:

[0074] ο LCD test - The connected field device is triggered by the control system to display one or more items of inspection data (e.g., a predefined display pattern) on an LCD or other display unit integrated with the connected field device, and the operator visually verifies whether the field device is displaying the inspection data triggered by the control system.

[0075] οSQUAWK Test - The connected field device is triggered by the control system using HART command 72, which causes the field device to visually indicate on its integrated LCD or other display unit the command it has received.

[0076] οDisconnection Test - In the case where the field device in question does not support both the LCD test and the SQUAWK test, disconnect or decouple the connected field device and check the control system to determine whether the status of the field device has changed from "connected" to "disconnected".

[0077] As part of the connection check process (specifically, as part of the check involving evaluating whether the field device information imported from the engineering data of the control system based on its configuration matches the field device information extracted from the field device actually connected to the control system), it has been found that a particularly effective method for connection check is to extract the physical device tag from the local memory of the field device connected to the I / O port or I / O card of the control system and compare this physical device tag with the system tag assigned to the software function block or software control module, where the software function block or software control module is configured to control the field device connected to the I / O port or I / O card. In the case where it is found that the physical device tag and the system tag refer to the same field device, it can be concluded that the field device connected to the I / O port or I / O card is indeed the correct field device that should be connected to the I / O port or I / O card according to the engineering data or design of the control system.

[0078] However, it has also been found that in many applications, the physical device tag corresponding to the field device intended to be connected to the I / O port or I / O card does not accurately match the system tag corresponding to the I / O port or I / O card. For example, even though the physical device tag and its corresponding system tag are "substantially similar", observable differences exist in the "Instrument Type" substring between the two.

[0079] The term "Instrument Type" refers to the type of measurement using the field device. For example, in the case of a field device configured to measure the fluid temperature in a fuel tank, (i) its physical device tag may include the instrument type "TT" (which is an abbreviation for "Temperature Transmitter"), and (ii) the corresponding system tag for this field device may include the instrument type "TI" (which is an abbreviation for "Temperature Indicator").

[0080] Therefore, while an exemplary physical device tag for temperature sensing of a field device may include the identifier "3100-TT-100", the corresponding system tag associated with the I / O card or I / O port intended to be coupled to the field device may include the identifier "3100" TI"100". Since there is such a difference even between the physical device tag and the system tag that match each other, the step of performing a connection check for matching based on the physical device tag and the system tag cannot be carried out by directly matching the two. One object of the present invention is to enable the physical device tag and the system tag to be accurately matched despite the difference in the basic directory used to name such tags.

[0081] Another object of the present invention is that in response to determining that the system tag information associated with the I / O port does not match the physical device tag information corresponding to the actual field device actually connected to the I / O port, the field device can be disconnected or decoupled from the I / O port, or alternatively, the physical device tag information stored in the local memory of the field device can be modified or updated to match or conform to the system tag information associated with the I / O port, or alternatively, at the location of the field device with a mismatched physical device tag, another field device with a physical device tag that matches the system tag information associated with the I / O port can be connected at the I / O port.

[0082] Figure 4 is a flowchart showing a method for performing an inspection on a field device connected to a control system.

[0083] Step 402 includes importing engineering data from a control system data repository. The engineering data includes data defining the design, structure, operation, and components of an industrial plant and / or a control system in the industrial plant. The engineering data is defined during the front-end engineering design phase of plant design and construction and provides a basis for constructing, setting up, configuring for operation, and / or operating an industrial plant and / or a control system in the industrial plant. For the purposes of the present invention, it should be understood that the engineering data includes data defining or describing any of the following: the number, type, and communication configuration or operation configuration of one or more control components in the control system, one or more field devices or sensors in the control system, and / or one or more data communication devices in the control system. In Figure 4 a specific embodiment of the method, the engineering data imported in step 402 includes at least an engineered I / O list, which includes a list of software function blocks or software control modules configured to control one or more field devices, system tags corresponding to the listed software function blocks or software control modules, and information specifying the I / O cards and / or I / O ports identified for enabling the I / O function for the corresponding software function blocks or software control modules. Figure 5 is something that can be used in Figure 4 a screenshot 500 of an exemplary display interface for importing engineering data in step 404 of the method. As Figure 5As shown, the interface can be configured to be capable of importing engineering data from multiple engineering data source files, and the multiple engineering data source files can be selected automatically, manually, or based on a combination of automatic and manual selection.

[0084] Step 404 includes extracting from the imported engineering data (i) system tag data, (ii) I / O card data and / or I / O port data, and (iii) data identifying the association between each system tag and an I / O port or an I / O card.

[0085] The system tag data extracted in step 404 includes system tags corresponding to one or more software function blocks or software control modules in the control system.

[0086] The I / O card data and / or I / O port data extracted in step 404 includes data for identifying the I / O card and / or I / O port, where the I / O card and / or I / O port is associated with one or more software function blocks or software control modules corresponding to the system tags extracted in step 402, and the I / O card and / or I / O port enables the I / O function of the corresponding function block or software control module.

[0087] The data extracted in step 404 for identifying the association between each system tag and the corresponding I / O port or I / O card may include any data or data record capable of associating (i) the identified software function block and / or software control module, and (ii) the corresponding system tag associated with the identified software function block and / or software control module.

[0088] Step 406 includes: generating field device configuration data for one or more I / O ports or I / O cards identified based on the data extracted in step 404. The generated field device configuration data associated with the I / O port or I / O card includes: data corresponding to the I / O port that has been extracted in step 404. In Figure 4 In a specific embodiment of the method, the field device configuration data associated with the I / O port or I / O card may include any of the following: (i) data for identifying the software function block or software control module associated with or connected to the I / O port or I / O card, (ii) system tag data for describing the system tags corresponding to the software function block or software control module associated with or connected to the I / O port or I / O card, and (iii) data for identifying the association data between the I / O port or I / O card and the system tag, where the system tag corresponds to the software function block or software control module associated with or linked to the I / O port or I / O card.

[0089] Figure 6 Shows the display according to Figure 4The display interface 600 of the exemplary field device configuration data generated by method step 406. As shown in the exemplary embodiment of the field device configuration data in the display interface 600, the field device configuration data generated in step 406 may include data records that map two or more of the following data columns together: (i) device tag (i.e., the physical device tag corresponding to the field device connected to the I / O port or I / O card), (ii) system tag name (i.e., the system tag corresponding to the software function block or software control module associated with or connected to the I / O port or I / O card), (iii) connection type data (i.e., the data indicating the connection type of the relevant field device and / or the corresponding function block), (iv) terminal data (i.e., the data for identifying the terminal number of the system connected to the device), (v) block type data (i.e., the data for identifying the type of the software function block or software control module), (vi) station data (i.e., the data for identifying the domain number and station number of the software function block or software control module), (vii) engineering unit data (i.e., the data for identifying the engineering unit used by the software function block or software control module), (ix) upper limit data (i.e., the data for identifying the metric upper limit value set in the software function block or software control module), and (x) lower limit data (i.e., the data for identifying the metric lower limit value set in the software function block or software control module).

[0090] Step 408 includes generating conversion data configured to enable the physical device tag to be mapped to the system tag extracted in step 404. The step of generating the conversion data is necessary due to the fact that the physical device tag corresponding to the field device coupled to the I / O port (i.e., the physical device tag assigned to an individual field device by the device manufacturer or by any other individual / enterprise (such as an operator, end user, EPC contractor, etc.) and stored in the local memory of the field device) may be different from the system tag assigned to the software function block or software control module that has been designated to control, monitor, or operate the field device via the I / O port or I / O card to which the software function block or software control module is communicatively coupled or connected.

[0091] The difference between the physical device label for a field device intended to be coupled to an I / O port or I / O card and the corresponding system label assigned to a software function block or software control module communicatively coupled or connected to the I / O port or I / O card may be trivial or may be more substantial. However, it can be generally said that: (i) at least one segment of the physical device label for a field device intended to be coupled to an I / O port or I / O card is different from the corresponding segment of the system label of a software function block or software control module communicatively coupled or connected to the I / O port or I / O card, and (ii) optionally, at least one other segment of the physical device label is the same as the corresponding segment of the system label. Exemplary Table 1 includes specific examples of physical device labels and corresponding system labels to explain the types of differences commonly observed.

[0092] Table 1

[0093] Example Physical device label System label Example 1 12EJX910 <![CDATA[12EJX910 PVI1 > Example 2 3100-TT-100 <![CDATA[3100 TI 100]]> Example 3 RMA803 <![CDATA[RM803 PVI1 >

[0094] As shown in Example 1 above, the system label 12EJX910PVI1 corresponding to the physical device label 12EJX910 includes the additional suffix " PVI1 ". In Example 2, the system label includes the character " TI " between number 3100 and number 100, while the corresponding physical device label includes the character " -TT- " between number 3100 and number 100. In Example 3, when comparing the system label RM803PV1 with its corresponding physical device label RMA803, it can be observed that (i) the physical device label includes the character "A" between "RM" and "803", while the corresponding system label does not include the character "A", and (ii) the system label includes the additional suffix " PVI1 " that does not exist in the physical device label.

[0095] Due to the differences between the physical device label and the corresponding system label, generally the two cannot be directly matched to determine whether the field device connected to the I / O port or I / O card corresponds to the system label assigned to the software function block or software control module communicatively coupled or connected to the I / O port or I / O card. Therefore, the conversion data generated in step 408 is data capable of converting one of the system label or physical device label represented by the first expression into a second expression that can be used to compare the converted system label with the corresponding physical device label or can be used to compare the converted physical device label with the corresponding system label.

[0096] The conversion data generated in step 408 may include any of the following:

[0097] · One or more conversion rules that define steps for converting a physical device tag or system tag represented by a first expression into a second expression different from the first expression.

[0098] · A mapping table that maps a first set of letters, numbers, or alphanumeric strings to a second set of letters, numbers, or alphanumeric strings, wherein converting a physical device tag or system tag based on the mapping table involves: (i) identifying in the mapping table a mapping record suitable for converting the physical device tag or system tag, and (ii) replacing a segment in the physical device tag or system tag that matches a first identified letter, number, or alphanumeric string in the identified mapping record with a second letter, number, or alphanumeric string that is mapped to the first identified letter, number, or alphanumeric string in the identified mapping record.

[0099] · A mapping table that maps a first set of one or more subsets of letters, numbers, or alphanumeric strings that include wildcards to a second set of one or more subsets of letters, numbers, or alphanumeric strings that also include wildcards, wherein converting a physical device tag or system tag based on this mapping table involves: (i) identifying in the mapping table a mapping record applicable to converting the physical device tag and system tag, and (ii) replacing at least one non - wildcard segment in the physical device tag or system tag that matches a first non - wildcard segment in the first identified letter, number, or alphanumeric string in the identified mapping record with a second non - wildcard segment in the second letter, number, or alphanumeric string that is mapped to the first identified letter, number, or alphanumeric string in the identified mapping record.

[0100] Next, a more detailed explanation of the conversion data generated in step 408 and the manner in which such conversion data can be used for physical device tag conversion or system tag conversion is provided in the present written specification.

[0101] After the generation of the conversion data (step 408), step 410 includes performing a connection check for each field device coupled to an I / O port or I / O card of a control system. The connection check includes: (i) extracting the physical device tag from the local memory of the coupled field device, (ii) extracting the system tag associated with the I / O port or I / O card to which the field device is coupled, and (iii) performing a comparison based on the physical device tag and the system tag to determine whether the physical device tag is the correct field device that needs to be connected to the I / O port or I / O card, wherein a match determination based on the comparison of the physical device tag and the system tag confirms that the correct field device is coupled to the I / O port or I / O card, and a mismatch determination based on the comparison of the physical device tag and the system tag confirms that the correct field device is not coupled to the I / O port or I / O card.

[0102] Step 412 includes initiating a connection check output event for one or more field devices, wherein the initiated connection check output event is selected based on the output of the connection check (performed in step 410) for a particular field device. In an embodiment of the method, in response to the connection check in step 410 being a match determination (i.e., determining that the correct field device is coupled to the I / O port or I / O card of interest), the connection check output event includes presenting a connection check report on a display or operator terminal, confirming that the correct field device is coupled to the I / O port or I / O card of interest. In another embodiment of the method, in response to the connection check in step 410 being a mismatch determination (i.e., determining that the correct field device is not coupled to the I / O port or I / O card of interest), the connection check output event includes presenting a connection check report on a display or operator terminal, confirming that the correct field device is not coupled to the I / O port or I / O card of interest. In yet another embodiment of the method, in response to the connection check in step 410 being a mismatch determination (i.e., determining that the correct field device is not coupled to the I / O port or I / O card of interest), the connection check output event includes corrective actions regarding the field device that is not correctly or properly coupled to the I / O port or I / O card of interest.

[0103] The corrective actions can include any of the following: (i) updating or modifying a first field device identifier in the local memory of the field device that is not correctly or properly coupled to the I / O port or I / O card of interest, (ii) decoupling the field device that is not correctly or properly coupled to the I / O port or I / O card of interest from the I / O port, or (iii) coupling another field device having a first field device identifier that matches a second field device identifier at the I / O port in place of the field device having a mismatched first field device identifier.

[0104] Figure 11 An exemplary connection check report 1100 that can be generated as part of the connection check output event of step 412 is shown. As Figure 11 shown, a connection check report regarding whether the correct field device is connected to a particular I / O port or I / O card can be transmitted to a user or operator.

[0105] Returning to Figure 4 step 408, as described above, the conversion data generated at step 408 can include one or more conversion rules that define the steps for converting a physical device label or system label represented by a first expression to a second expression different from the first expression. Exemplary conversion rules for explaining the function of such conversion rules are provided below:

[0106] · If the physical device label includes the substring “-TT-” between two numerical substrings, then the transformed physical device label is produced by replacing the substring “-TT-” with the substring “-TI-” in the physical device label. It should be understood that this illustrative transformation rule can be used to transform the physical device label of Example 2 in Table 1 to match the corresponding system label.

[0107] In another embodiment of method step 408, the generated transformation data may include a mapping table or mapping data that maps a first set of letters, numbers, or alphanumeric strings to a second set of letters, numbers, or alphanumeric strings, where transforming a physical device label or system label based on the mapping table involves: (i) identifying in the mapping table a mapping record applicable to transforming the physical device label or system label (i.e., capable of transforming at least a segment of the physical device label or system label from a first expression to a second expression), and (ii) replacing in the physical device label or system label a segment that matches the identified first letter, number, or alphanumeric string in the identified mapping record with the second letter, number, or alphanumeric string that is mapped to the identified first letter, number, or alphanumeric string in the identified mapping record.

[0108] Figure 7 A display interface 700 showing an exemplary mapping table of the type described above is shown. As Figure 7 shown, the mapping table maps substrings from the physical device label to corresponding substrings from the system label such that (i) the physical device label can be transformed by identifying a first substring in the mapping table, where the first substring is classified under the column item “Device Label” that forms part of the physical device label, (ii) a second substring is identified from the mapping table, where the second substring is classified under the column item “System Label” and is associated with the identified first substring in the mapping table, and (iii) the transformed physical device label is produced by replacing the identified first substring with the identified second substring in the physical device label. Considered from another perspective, the mapping table maps substrings from the system label to corresponding substrings from the physical device label such that (i) the system label can be transformed by identifying a first substring in the mapping table, where the first substring is classified under the column item “System Label” that forms part of the system label, (ii) a second substring is identified from the mapping table, where the second substring is classified under the column item “Device Label” and is associated with the identified first substring in the mapping table, and (iii) the transformed system label is produced by replacing the identified first substring with the identified second substring in the system label.

[0109] Thus, by way of example, if the physical device label is “1234-PT-7220”, then applying Figure 7The conversion data of the mapping table will cause the following steps: (i) Identify in the mapping table the first substring that is classified under the column item "device label" and forms part of the physical device label, which in this case is the first substring "PT", (ii) Identify from the mapping table the second substring that is classified under the column item "system label" and is associated with the identified first substring in the mapping table, which in this case is the second substring "PI", and (iii) Generate the converted physical device label by replacing the identified first substring in the physical device label with the identified second substring, i.e., generate the converted physical device label "1234- PI -7220".

[0110] Similarly, if the system label is "1234-PI-7220", then applying Figure 7 the conversion data of the mapping table will cause the following steps: (i) Identify in the mapping table the first substring that is classified under the column item "system label" and forms part of the system label, which in this case is the first substring "PI", (ii) Identify from the mapping table the second substring that is classified under the column item "device label" and is associated with the identified first substring in the mapping table, which in this case is the second substring "PT", and (iii) Generate the converted system label by replacing the identified first substring in the system label with the identified second substring, i.e., generate the converted system label "1234-PT-7220".

[0111] In another embodiment of method step 408, the generated conversion data may include a mapping table or mapping data that maps a first set of one or more subsets of letters, numbers, or alphanumeric strings including wildcards to a second set of one or more subsets of letters, numbers, or alphanumeric strings also including wildcards, wherein converting a physical device label or system label based on the mapping table involves: (i) Identifying in the mapping table a mapping record applicable to converting the physical device label or system label, and (ii) Replacing at least one non-wildcard segment in the physical device label or system label that matches the first non-wildcard segment in the first letter, number, or alphanumeric string in the identified mapping record with the second non-wildcard segment in the second letter, number, or alphanumeric string mapped to the identified first letter, number, or alphanumeric string in the mapping record.

[0112] Figure 8 A display interface 800 showing an exemplary mapping table of the type described above is shown.

[0113] For the written specification and drawings, it should be understood that the character "!" is a wildcard representing a single matching digit character, the character "?" is a wildcard representing any single letter, digit, or special character, and the character "*" is a wildcard representing a string of any length including any letter, digit, or special character.

[0114] As Figure 8 shown, the mapping table maps (i) to (ii), where (i) is a mixed first string expression that includes a combination of wildcard substrings and non-wildcard substrings and represents a generalized expression of the device label format, and (ii) is a mixed second string expression that includes a combination of wildcard substrings and non-wildcard substrings and represents a generalized expression of the system label format.

[0115] Specifically, Figure 8 the shown mixed first string expression includes the string "UNT!!!-FI-!!!", which includes in order a first non-wildcard substring (including three consecutive non-wildcard characters "UNT"), a second wildcard substring (including three consecutive wildcard characters "!!!"), a third non-wildcard substring (including four consecutive non-wildcard characters "-FI-"), and a fourth wildcard substring (including three consecutive wildcard characters "!!!"). As a result of incorporating wildcards into the string expression, the mixed first string expression represents all such strings that include in order a first non-wildcard substring (including three consecutive non-wildcard characters "UNT"), a second wildcard substring (including any three consecutive letters, digits, or special characters), a third non-wildcard substring (including four consecutive non-wildcard characters "-FI-"), and a fourth wildcard substring (including any three consecutive letters, digits, or special characters).

[0116] Figure 8 the shown mixed second string expression includes the string "UN!!!!FIC!!!", which includes in order a first non-wildcard substring (including two consecutive non-wildcard characters "UN"), a second wildcard substring (including four consecutive wildcard characters "!!!!"), a third non-wildcard substring (including three consecutive non-wildcard characters "FIC"), and a fourth wildcard substring (including three consecutive wildcard characters "!!!"). As a result of incorporating wildcards into the string expression, the mixed second string expression represents all such strings that include in order a first substring (including two consecutive non-wildcard characters "UN"), a second substring (including any four consecutive letters, digits, or special characters), a third substring (including three consecutive non-wildcard characters "FIC"), and a fourth substring (including any three consecutive letters, digits, or special characters).

[0117] Based on Figure 8The conversion data represented in the mapping table can convert the physical device label to generate a converted physical device label. The following explains the process of converting a physical device label using the conversion data in the mapping table in conjunction with the exemplary physical device label "UNT123-FI-456". Figure 8 The process of converting a physical device label using the conversion data in the mapping table.

[0118] · In response to receiving the physical device label ("UNT123-FI-456") for conversion, search or parse the "Device Label" column entry of the mapping table ( Figure 8 ) to identify the mixed first string expression that has a general expression of the device label format with which the physical device label conforms or corresponds. For this example, since the mixed first string expression ("UNT!!!-FI-!!!") provides a general expression of the device label format with which the physical device label ("UNT123-FI-456") conforms or corresponds, this will result in the identification of the mixed first string expression "UNT!!!-FI-!!!" in the "Device Label" column entry of the mapping table ( Figure 8 ).

[0119] · Then, search or parse the "System Label" column of the mapping table ( Figure 8 ) to identify the mixed second string expression associated with the identified mixed first string expression ("UNT!!!-FI-!!!") in the mapping table. For this example, since the mixed second string expression ("UN!!!FIC!!!?") is associated with the identified mixed first string expression ("UNT!!!-FI-!!!") in the mapping table of Figure 8 , this will result in the identification of the mixed second string expression UN!!!FIC!!!? in the "System Label" column entry of the mapping table ( Figure 8 ).

[0120] · Convert the physical device label ("UNT123-FI-456") through the following steps to generate a converted physical device label:

[0121] ο Identify a first set of non-wildcard substrings in the mixed first string expression (“UNT!!!-FI-!!!”), and identify the position attributes of each non-wildcard substring in the first set of non-wildcard substrings. For this example, this will result in identifying a first set of non-wildcard substrings that includes: (a) a first non-wildcard substring “UNT” that has a position attribute that confirms it is the first substring (i.e., non-wildcard substring) starting exactly at the left side of the mixed first string expression (“UNT!!!-FI-!!!”), and (b) a second non-wildcard substring “-FI-” that has a position attribute that confirms it is the third substring counted from the left side of the mixed first string expression (“UNT!!!-FI-!!!”), and it is exactly to the right of the second wildcard substring (“!!!”), and the second wildcard substring (“!!!”) is exactly to the right of the first non-wildcard substring (“UNT”) that starts the mixed first string expression (“UNT!!!-FI-!!!”).

[0122] ο Identify a second set of non-wildcard substrings in the mixed second string expression (“UN!!!FIC!!!?”), where each non-wildcard substring in the second set of non-wildcard substrings has the same set of position attributes as the non-wildcard substrings in the first set of non-wildcard substrings (the first set of non-wildcard substrings includes the substrings “UNT” and “-FI-”). For this example, this will result in identifying a second set of non-wildcard substrings in the mixed second string expression (“UN!!!FIC!!!?”), where the second set of non-wildcard substrings includes: (a) a first non-wildcard substring “UN” that has a position attribute that confirms it is the first substring (i.e., non-wildcard substring) starting exactly at the left side of the mixed second string expression (“UN!!!FIC!!!?”), and (b) a second non-wildcard substring “FIC” that has a position attribute that confirms it is the third substring counted from the left side of the mixed second string expression (“UN!!!FIC!!!?”), and it is just to the right of the second wildcard substring (“!!!”), and the second wildcard substring (“!!!”) is just to the right of the first non-wildcard substring (“UN”) that starts the mixed second string expression (“UN!!!FIC!!!?”).

[0123] ο Identify a third set of substrings that represent a string expression of a physical device label (“UNT123-FI-456”), where each substring in the third set of substrings is the same as the corresponding non-wildcard substring in a first set of non-wildcard substrings (the first set of non-wildcard substrings includes the substrings “UNT” and “-FI-”) in terms of length and position attributes. For this example, this results in identifying a third set of substrings in the physical device label (“UNT123-FI-456”), where the third set includes a first substring “UNT” and a second substring “-FI-”, where the first substring “UNT” has a length of 3 characters and a position attribute that confirms it as a substring starting from the left side of the physical device label, and the second substring “-FI-” has a length of 4 characters and a position attribute that confirms it starts after the sixth character counted from the left side of the physical device label.

[0124] ο Generate a transformed physical device label by the following steps: Replace each substring in the third set of substrings (the third set of non-wildcard substrings includes the substrings “UNT” and “-FI-”) in the physical device label (“UNT123-FI-456”), where the replacement includes removing each substring (included in the third set of substrings) from the physical device label (“UNT123-FI-456”), and replacing each removed substring in the physical device label with a corresponding replaceable substring in a second set of non-wildcard substrings (the second set of non-wildcard substrings includes the substrings “UN” and “FIC”), where each replacement substring (“UN” and “FIC”) in the second set of non-wildcard substrings has the same set of position attributes as the non-wildcard substring, where the non-wildcard substring is (a) a non-wildcard substring included in a first set of non-wildcard substrings (the first set of non-wildcard substrings includes the substrings “UNT” and “-FI-”), and (b) the same non-wildcard substring as the substring in the third set of substrings (“UNT” and “-FI-”) replaced in the physical device label (“UNT123-FI-456”). For this example, this results in replacing the non-wildcard substring “UNT” with “UN” and the non-wildcard substring “-FI-” with “FIC” in the physical device label (“UNT123-FI-456”), and as a result, the original physical device label “UNT123-FI-456” is transformed into “UN123FIC456”.

[0125] Conversely, based on Figure 8 the conversion data expressed in the mapping table, the system label can be converted to generate a transformed system device label. The process of converting the system device label using the conversion data in the Figure 8 mapping table is explained below with reference to the exemplary system label “UN123FIC456”.

[0126] ·Convert in response to receiving the system tag (“UN123FIC456”), search or parse the “system tag” column entry of the mapping table ( Figure 8 ) to identify the mixed first string expression that has a general expression of the system tag format with which the system tag (“UN123FIC456”) conforms or corresponds. For this example, this will result in identifying the mixed first string expression “UN!!!FIC!!!?” in the “system tag” column entry of the mapping table ( Figure 8 ), because this mixed first string expression (“UN!!!FIC!!!?”) provides a general expression of the system tag format with which the system tag (“UN123FIC456”) conforms or corresponds.

[0127] ·Then, search or parse the “device tag” column entry of the mapping table ( Figure 8 ) to identify the mixed second string expression associated with the identified mixed first string expression (“UN!!!FIC!!!?”) in the mapping table. For this example, since this mixed second string expression (“UNT!!!-FI-!!!”) is associated with Figure 8 the identified mixed first string expression (“UN!!!FIC!!!?”) in the mapping table, this will result in identifying the mixed second string expression “UNT!!!-FI-!!!” in the “device tag” column entry of the mapping table ( Figure 8 ).

[0128] ·Convert the system tag (“UN123FIC456”) through the following steps to produce a converted system tag:

[0129] ο Identify the first set of non-wildcard substrings in the mixed first string expression (“UN!!!FIC!!!?”), and identify the position attributes of each non-wildcard substring in the first set of non-wildcard substrings. For this example, this will result in identifying the first set of non-wildcard substrings that includes (a) the first non-wildcard substring “UN” that has the position attribute of verifying that the first substring (i.e., non-wildcard substring) starts just to the left of the mixed first string expression (“UN!!!FIC!!!?”), and (b) the second non-wildcard substring “FIC” that has the position attribute of verifying that it is the third substring counted from the left of the mixed first string expression (“UN!!!FIC!!!?”), and it is exactly to the right of the second wildcard substring (“!!!”), and the second wildcard substring (“!!!”) is exactly to the right of the first non-wildcard substring (“UN”) that starts the mixed first string expression (“UN!!!FIC!!!?”).

[0130] ο Identify a second set of non-wildcard substrings in the mixed second string expression (“UNT!!!-FI-!!!”), where each non-wildcard substring in the second set of non-wildcard substrings has the same set of position attributes as the non-wildcard substrings in the first set of non-wildcard substrings (the first set of non-wildcard substrings includes the substrings “UN” and “FIC”). For this example, this will result in identifying a second set of non-wildcard substrings in the mixed second string expression (“UNT!!!-FI-!!!”), which includes (a) a first non-wildcard substring “UNT” that has position attributes that confirm the start of a first substring (i.e., a non-wildcard substring) just to the left of the mixed second string expression (“UNT!!!-FI-!!!”), and (b) a second non-wildcard substring “-FI-” that has position attributes that confirm the third substring counted from the left of the mixed second string expression (“UNT!!!-FI-!!!”) and that is immediately to the right of a second wildcard substring (“!!!”), the second wildcard substring (“!!!”) being immediately to the right of the first non-wildcard substring (“UNT”) that starts the mixed second string expression (“UNT!!!-FI-!!!”).

[0131] ο Identify a third set of substring expressions of a system label (“UN123FIC456”), where each substring in the third set of substrings is the same (in terms of length and position attributes) as the corresponding non-wildcard substring in the first set of non-wildcard substrings (the first set of non-wildcard substrings includes the substrings “UN” and “FIC”). For this example, this results in identifying a third set of substrings in the system label (“UN123FIC456”), which includes a first substring “UN” and a second substring “FIC”, the first substring “UN” having a 2-character length and position attributes that confirm it as a substring starting at the left of the system label, and the second substring “FIC” having a 3-character length and position attributes that confirm it as starting after the fifth character counted from the left of the system label.

[0132] ο Generate the converted system label through the following steps: Replace each substring in the third set of substrings (the third set of non-wildcard substrings includes the substrings "UN" and "FIC") in the system label ("UN123FIC456"), where the replacement includes: Remove each substring (included in the third set of substrings) from the system label ("UN123FIC456"), and replace each removed substring in the system label with the corresponding replaceable substring in the second set of non-wildcard substrings (the second set of non-wildcard substrings includes the substrings "UNT" and "-FI-"), where each replacement substring ("UNT" and "-FI-") in the second set of non-wildcard substrings has the same set of position attributes as the non-wildcard substring, and the non-wildcard substring is (a) a non-wildcard substring included in the first set of non-wildcard substrings (the first set of non-wildcard substrings includes the substrings "UN" and "FIC"), and (b) the same as the substring in the third set of substrings ("UN" and "FIC") that is replaced in the system label ("UN123FIC456"). For this example, this results in replacing the non-wildcard substring "UN" with "UNT" in the system label ("UN123FIC456"), and replacing the non-wildcard substring "FIC" with "-FI-", so that the original system label "UN123FIC456" is converted to "UNT123-FI-456".

[0133] Although Figure 8 represent specific instances of the mapping of the hybrid string expression, it should be understood that they are not exhaustive, and other specific examples of suitable wildcard-based mappings are provided below in conjunction with Tables 2 to 4.

[0134] If the physical device label is "UNT200-FI-101" and the corresponding system label is "UN200FIC101", then the appropriate conversion data for implementing the necessary conversion can be achieved through the mapping expression in Table 2 below.

[0135] Table 2

[0136] Device label System label UNT!!!-FI-!!! UN!!!FIC!!! UNT*-FI-* UN*FIC*

[0137] If the physical device label is UNT200-FI-101, and there are corresponding multiple system labels "UN200FIC101A", "UN200FIC101B", and "UN200FIC101C", then the appropriate conversion data for implementing the necessary conversion can be achieved through the mapping expression in Table 3 below.

[0138] Table 3

[0139] Device label System label UNT!!!-FI-!!! UN!!!FIC!!!?

[0140] If the physical device label is UNT-LAB-200-FI-101 and there is a corresponding system label UN200FIC101, then suitable conversion data for implementing the necessary conversion can be achieved through the mapping expression in Table 4 below.

[0141] Table 4

[0142] Device label System label UNT-LAB-!!!-FI-!!! UN!!!FIC!!!

[0143] Figure 9A is a flowchart depicting a specific embodiment of a connection check step for the method steps according to Figure 4 , that is, a flowchart of an embodiment for implementing method step 410 of Figure 4 . In an embodiment of the present invention, one or more steps of the method of Figure 9A can be implemented at the control system server or the control system processor.

[0144] Step 902 includes detecting a connection event, which includes a field device and an I / O port communicatively coupled to the control system being connected through an interface. The connection event can be detected in a variety of ways. In an embodiment, it includes: receiving an electrical signal or a data signal from the I / O port or an I / O card (which is connected to the I / O port) by the control system processor or the control system server, and notifying the control system processor or the control system server that the field device is currently coupled to the I / O port (or I / O card) or connected through an interface.

[0145] Step 904 includes extracting a first field device identifier corresponding to the field device from the local memory of the field device connected to the I / O port through an interface. In an embodiment, the first field device identifier extracted from the local memory of the field device includes the physical device label of the type described above.

[0146] Step 906 includes extracting field device configuration data associated with the I / O port (or an I / O card that controls, monitors, or is connected to the I / O port through an interface) from a non-transitory memory database communicatively coupled to the control system processor or the control system server. The field device configuration data extracted in step 904 may include that combined with Figure 4Any field device configuration data of the type discussed in step 406. In a particular embodiment, the extracted field device configuration data includes one or more of the following: (i) data for identifying software function blocks or software control modules associated with or linked to I / O ports (or I / O cards that control or monitor I / O ports); (ii) system tag data for describing and corresponding to system tags of software function blocks or software control modules associated with or linked to I / O ports or I / O cards; and (iii) data for identifying the association between I / O ports or I / O cards and system tags, where the system tags correspond to software function blocks or software control modules associated with or linked to I / O ports or I / O cards. In a particular embodiment, the field device configuration data includes at least a second field device identifier, where at least one segment of the second field device identifier is different from the corresponding segment of the first field device identifier. In an embodiment, the second field device identifier extracted in step 906 is a system tag uniquely associated with a software function block or software control module that controls an I / O port, monitors an I / O port, or is connected to an I / O port through an interface. For Figure 9A the method shown, it should be understood that the system tag extracted in step 906 is different from the physical device tag at step 904 in one or more constituent substrings.

[0147] Step 908 includes generating one or both of a transformed first field device identifier and a transformed second field device identifier based on predefined transformation data. The transformation data used to generate the transformed identifier in step 908 may include any transformation data of the type discussed in Figure 4 step 408, and the method of generating the transformed identifier based on such predefined transformation data may include any method known to those skilled in the art, and in a particular embodiment, may include in combination with Figure 4Any of the conversion methods discussed in step 408. In one embodiment of step 908, where the conversion data for generating the converted identifier includes one or more conversion rules that define the steps for converting a physical device tag or a system tag, step 908 may include generating one of a converted first field device identifier and a converted second field device identifier based on the conversion rules. In one embodiment of step 908, the conversion data for generating the converted identifier includes a mapping table that maps a first set of letters, numbers, or alphanumeric strings to a second set of letters, numbers, or alphanumeric strings, and step 908 may include generating one of a converted first field device identifier and a converted second field device identifier based on the mapping table. In one embodiment of step 908, the conversion data for generating the converted identifier includes a mapping table that maps a first set of letters, numbers, or alphanumeric strings that includes one or more subsets with wildcards to a second set of letters, numbers, or alphanumeric strings that also includes one or more subsets with wildcards, and step 908 includes generating both a converted first field device identifier and a converted second field device identifier based on the mapping table. In a particular embodiment of step 908, (i) generating a converted first field device identifier, where the first field device identifier may include a physical device tag extracted from the local memory of the field device and converting the physical device tag by using predefined conversion data to generate the converted first field device identifier, and / or (ii) generating a converted second field device identifier, where the second field device identifier may include a system tag uniquely associated with a control I / O port, a monitoring I / O port, or a software function block or software control module interfaced with the I / O port and converting the system tag by using predefined conversion data to generate the converted second field device identifier.

[0148] Step 910 includes (i) comparing the converted first field device identifier with the second field device identifier, or (ii) comparing the first field device identifier with the converted second field device identifier, or (iii) comparing the converted first field device identifier with the converted second field device identifier.

[0149] In an embodiment of the method, step 908 includes generating only the transformed first field device identifier (e.g., based on a set of transformation rules or based on a mapping table that maps a first set of letters, numbers, or alphanumeric strings to a second set of letters, numbers, or alphanumeric strings), and step 910 includes comparing the transformed first field device identifier with a second field device identifier to identify a match therebetween. In one embodiment of the method, step 908 includes generating only the transformed second field device identifier (e.g., based on a set of transformation rules or based on a mapping table that maps a first set of letters, numbers, or alphanumeric strings to a second set of letters, numbers, or alphanumeric strings), and step 910 includes comparing the first field device identifier with the transformed second field device identifier to identify a match therebetween. In one embodiment of the method, step 908 includes generating both the transformed first field device identifier and the transformed second field device identifier (based on a mapping table that maps a first set of letters, numbers, or alphanumeric strings that includes one or more subsets with wildcards to a second set of letters, numbers, or alphanumeric strings that also includes one or more subsets with wildcards), and step 910 includes comparing the transformed first field device identifier with the transformed second field device identifier to identify a match therebetween.

[0150] Thus, in one embodiment, where the first field device identifier is a physical device tag, the second field device identifier is a system tag, and the conversion step 908 (e.g., converts the original physical device tag based on a set of conversion rules or based on a mapping table that maps a first set of letters, numbers, or alphanumeric strings to a second set of letters, numbers, or alphanumeric strings) causes a converted physical device tag to be generated, step 910 includes comparing the converted physical device tag with the extracted system tag to identify whether they match. In an alternative embodiment, where the first field device identifier is a physical device tag, the second field device identifier is a system tag, and the conversion step 908 (e.g., converts the original system tag based on a set of conversion rules or based on a mapping table that maps a first set of letters, numbers, or alphanumeric strings to a second set of letters, numbers, or alphanumeric strings) causes a converted system tag to be generated, step 910 includes comparing the extracted physical device tag with the converted system tag to determine whether they match. In yet another embodiment, where the first field device identifier is a physical device tag, the second field device identifier is a system tag, and the conversion step 908 (e.g., converts both tags based on a mapping table that maps a first set of letters, numbers, or alphanumeric strings including one or more subsets with wildcards to a second set of letters, numbers, or alphanumeric strings also including one or more subsets with wildcards) causes both a converted physical device tag and a converted system tag to be generated, step 910 includes comparing the converted physical device tag with the converted system tag to determine whether they match. It should be understood that the comparison of step 910 can be implemented by any comparison method known to those skilled in the art, including any of the comparison methods discussed above in connection with Figure 4 the method.

[0151] Subsequent step 912 includes generating a connection check output decision based on the comparison output of step 910. The connection check output decision may include a "match determination" or a "mismatch determination". In an embodiment, if (in the case of converting the first field device identifier using the conversion data and comparing the converted first field device identifier with the second field device identifier) it is determined that the converted first field device identifier matches the second field device identifier, or if (in the case of converting the second field device identifier using the conversion data and comparing the converted second field device identifier with the first field device identifier) it is found that the first field device identifier matches the converted second field device identifier, or if (in the case of converting both the first field device identifier and the second field device identifier using the conversion data and comparing the converted first field device identifier with the converted second field device identifier) it is determined that the converted first field device identifier matches the converted second field device identifier, then the connection check output decision is a "match determination". In another embodiment, if it is determined that the converted first field device identifier does not match the second field device identifier, or if it is determined that the first field device identifier does not match the converted second field device identifier, then the connection check output decision is a "mismatch determination".

[0152] Figure 9B illustrates an example user interface 900B for steps implementing connection check according to an embodiment of the method steps of Figure 9A . In the Figure 9B exemplary illustration, the control system detects that a field device with a physical device tag of "3100-TT-100" is connected to an I / O port. The I / O port has a corresponding system tag "3100TI100" assigned to the software function block or software control module associated with the I / O port, and Figure 9B the interface shown is capable of comparing the two and generating a connection check output decision according to the teachings of Figure 4 discussed above and the method of FIG. 9.

[0153] Figure 10 illustrates an example user interface 900B for steps implementing connection check according to an embodiment of the method steps of Figure 4Alternative example user interface 1000 for comparing physical device tags and system device tags corresponding to a particular I / O port, and / or method steps of FIG. 9. To utilize user interface 1000, both the physical device tag for the field device connected to the I / O port and the system tag corresponding to that I / O port are entered under the corresponding form fields in interface 1000, and the verification function is implemented by selecting the action button labeled "Verify". In response to initiating the "Verify" function, the control system searches the predetermined mapping data for a mapping data record that matches the physical device tag, and converts the physical device tag before comparing it to the system tag to determine whether the physical device tag matches the corresponding system tag for that particular I / O port. However, it should be understood that alternatively, the control system should also search the predetermined mapping data for a mapping data record that matches the system tag, and then convert the system tag before comparing it to the physical device tag to determine whether the physical device tag matches the corresponding system tag for that particular I / O port.

[0154] Figure 12 Illustrates a process control environment configured in accordance with the teachings of the present invention.

[0155] Process control environment 1200 includes an operator terminal 1202, a control system 1204, and a field device network 1206.

[0156] Operator terminal 1202 includes a terminal device or client device implemented by any processor communicatively coupled to control system 1204, and is configured to enable an operator to send instructions to and receive data from control system 1204.

[0157] Field device network 1206 includes a plurality of field devices communicatively coupled to a plant resource management server 1004. In Figure 12 this example, field device network 1206 includes field device 1 (12062), field device 2 (12064) through field device n (1206n). The field devices 12062 through 1206n in field device network 1206 can include any of valves, valve actuators, switches, transmitters, or other sensor devices that may be located in a plant processing environment and configured for physical control functions or process control functions.

[0158] Control system 1204 includes a server implemented by one or more processors, arranged as a communication intermediary between operator terminal 1202 and field device network 1206.

[0159] The control system 1204 may include (i) a display 12042, (ii) a processor 12043 configured to control data processing operations in the control system 1204, (iii) an I / O controller 12044 configured to enable input / output functions associated with the control system 1204, and (iv) a memory 12045 including a transient memory and / or a non-transient memory.

[0160] In an embodiment, the memory 12045 may store therein: (i) an operating system 12046 configured to manage device hardware and software resources and provide common services for software programs implemented in the control system 1204, (ii) an operator interface 12047 configured to enable an operator to configure or control the control system 1204, (iii) an engineering data import controller 12048 configured to import / extract engineering data (for configuring the control system based on the engineering data) from an engineering data repository coupled to the control system 1204 according to Figure 4 method step 402, (iv) a field device configuration data recorder 12049 configured to generate field device configuration data for one or more I / O ports or I / O cards coupled to the control system 1204 according to Figure 4 method step 406, (v) a conversion data generator 12050 configured to generate conversion data for mapping physical device tags to corresponding system tags according to Figure 4 method step 406, (vi) a connection check controller 12051 configured to perform a connection check for one or more field devices coupled to the I / O ports or I / O cards of the control system 1204 based on Figure 4 method step 410 and / or the method steps of FIG. 9, (vii) an output event controller 12052 configured to initiate a connection check output event for one or more field devices that have undergone a connection check according to Figure 4 method step 412, and (viii) a field device interface 12053 configured to enable the control system 1204 to communicate data with and control communication between the field device network 1206 and / or each field device 12062 to 1206n in the field device network 1206.

[0161] Figure 13 An exemplary computer system is shown in which various embodiments of the present invention may be implemented.

[0162] System 1300 includes computer system 1302, and computer system 1302 includes one or more processors 1304 and at least one memory 1306. The processor 1304 is configured to execute program instructions and can be a real processor or a virtual processor. It should be understood that computer system 1302 does not impose any limitation on the scope of use and functionality of the embodiments. Computer system 1302 may include, but is not limited to, a general-purpose computer, a programmed microprocessor, a microcontroller, an integrated circuit, and one or more of other devices or device arrangements capable of implementing the steps of the methods constituting the present invention. Exemplary embodiments of computer system 1302 according to the present invention may include one or more servers, desktops, laptops, tablets, smart phones, mobile phones, mobile communication devices, tablet computers, phablets, and personal digital assistants. In an embodiment of the present invention, the memory 1306 may store software for implementing various embodiments of the present invention. Computer system 1302 may have additional components. For example, computer system 1302 may include one or more communication channels 1308, one or more input devices 1310, one or more output devices 1312, and a storage 1314. An interconnection mechanism (not shown), such as a bus, a controller, or a network, interconnects the components of computer system 1302. In various embodiments of the present invention, an operating system software (not shown) provides an operating environment for the various software executed in computer system 1302 by using the processor 1304 and manages the different functions of the components of computer system 1302.

[0163] The communication channel 1308 allows communication with various other computing entities via a communication medium. The communication medium provides information such as program instructions or data in the communication medium. The communication medium includes, but is not limited to, wired or wireless methods implemented via electricity, light, RF, infrared, acoustic, microwave, Bluetooth, or other transmission media.

[0164] The input device 1310 may include, but is not limited to, a touch screen, a keyboard, a mouse, a pen, a pointing stick, a trackball, a voice device, a scanning device, or any other device capable of providing input to computer system 1302. In an embodiment of the present invention, the input device 1310 may be a sound card or a similar device that receives audio input in analog or digital form. The output device 1312 may include, but is not limited to, a user interface on a CRT, an LCD, an LED display, or any other display associated with any one of a server, a desktop, a laptop, a tablet, a smart phone, a mobile phone, a mobile communication device, a tablet computer, a phablet, and a personal digital assistant, a printer, a speaker, a CD / DVD burner, or any other device that provides output from computer system 1302.

[0165] The storage 1314 may include, but is not limited to, magnetic disks, magnetic tapes, CD-ROMs, CD-RWs, DVDs, any type of computer memory, magnetic strips, smart cards, printed barcodes, or any other transient or non-transient medium that can be used to store information and can be accessed by the computer system 1302. In various embodiments of the present invention, the storage 1314 may contain program instructions for implementing any one of the embodiments.

[0166] In an embodiment of the present invention, the computer system 1302 is part of a distributed network or part of a collection of cloud resources.

[0167] The present invention can be implemented in various ways, including: as a system, a method, or a computer program product such as a computer-readable recording medium, or a computer network in which programming instructions are transmitted from a remote location.

[0168] The present invention can be suitably implemented as a computer program product for the computer system 1302. The methods described herein are generally implemented as computer program products, including a set of program instructions executed by the computer system 1302 or any other similar device. The set of program instructions can be a series of computer-readable codes stored on a tangible medium, or a series of computer-readable codes that can be transmitted to the computer system 1302 via a modem or other interface device on a tangible medium (including, but not limited to, optical or analog communication channels 1308), such as a computer-readable storage medium (storage 1314), for example, a floppy disk, a CD-ROM, a ROM, a flash drive, or a hard disk. The present invention implemented as a computer program product can be in an intangible form using wireless technologies, including, but not limited to, microwave, infrared, Bluetooth, or other transmission technologies. These instructions can be pre-loaded into the system or recorded on a storage medium such as a CD-ROM, or can be downloaded via a network such as the Internet or a mobile phone network. The series of computer-readable instructions can implement all or part of the functions described previously herein.

[0169] Based on the above, it is obvious that the present invention provides significant advantages. Specifically, the present invention can not only check whether a field device has been physically connected or detected at an I / O port, but also verify that the connected field device has been coupled to the correct I / O port, and thus can verify that it is correctly coupled or linked to a software function block or software control module that has been configured to appropriately control such a device. It has been found that this significantly reduces or even completely eliminates the possibility that a field device connected to an I / O port is actually not a field device intended or designed to be connected to a specific I / O port, and thus cannot be correctly monitored or controlled by a software function block or software control module that controls the specific I / O port. Therefore, the present invention also avoids the consequences that after the pre-commissioning or commissioning phase, the time and cost required to track and correct incorrect device arrangements or connections must be incurred, and can also avoid any adverse consequences resulting from incorrect field devices being coupled to specific I / O ports.

[0170] Although exemplary embodiments of the present invention have been described and illustrated herein, it should be understood that they are merely illustrative. Those skilled in the art should understand that various modifications can be made in form and detail without departing from the spirit and scope of the present invention as defined by the claims or conflicting therewith. Additionally, the present invention disclosed illustratively herein can be practiced appropriately without any element not specifically disclosed herein - and in the specific embodiments specifically contemplated, the present invention is intended to be practiced without any one or more elements not specifically disclosed herein.

Claims

1. A method for debugging field devices in a control system, the control system including at least one server and a plurality of input / output (I / O) ports communicatively coupled to the server, the method comprising: Detect a connection event, where the connection event includes a field device and an I / O port communicatively coupled to the server being connected through an interface; Extract a first field device identifier corresponding to the field device from the memory of the field device connected to the I / O port through the interface; Extract field device configuration data associated with the I / O port from a non-transitory memory database communicatively coupled to the server, where the field device configuration data includes at least a second field device identifier; and at least one segment of the second field device identifier is different from the corresponding segment of the first field device identifier; Generate one or both of a converted first field device identifier and a converted second field device identifier based on predefined conversion data; and In response to determining (i) that the converted first field device identifier does not match the second field device identifier, or (ii) that the converted second field device identifier does not match the first field device identifier, or (iii) that the converted first field device identifier does not match the converted second field device identifier, trigger an alert to be generated on the user interface.

2. The method according to claim 1, comprising: In response to determining that the converted first field device identifier does not match the second field device identifier, or in response to determining that the converted second field device identifier does not match the first field device identifier, perform a corrective action, where the corrective action includes any one of the following: Update or modify the first field device identifier in the local memory of the field device connected to the I / O port through the interface; or Decouple the field device connected to the I / O port through the interface from the I / O port; or At the location of the field device connected to the I / O port through the interface, couple another field device to the I / O port, where the another field device has a first field device identifier that matches the second field device identifier.

3. The method according to claim 1, wherein The field device configuration data is a subset of engineering data, design data, or design specifications corresponding to the control system.

4. The method according to claim 3, wherein The field device configuration data identifies a set of field device attributes corresponding to a specified field device that has been identified for connection to the I / O port through the interface.

5. The method according to claim 1, wherein The connection event includes coupling the field device to the I / O port.

6. The method according to claim 1, wherein The predefined conversion data includes a conversion table or conversion rules.

7. The method according to claim 6, wherein Generating the converted first field device identifier includes the step of transforming the first field device identifier based on the application of the conversion table or the conversion rule to the first field device identifier.

8. The method according to claim 6, wherein Generating the converted second field device identifier includes the step of transforming the second field device identifier based on the application of the conversion table or the conversion rule to the second field device identifier.

9. The method according to claim 6, wherein The predefined conversion data includes a conversion rule for converting a physical device tag or system tag represented by a first expression into a second expression.

10. The method according to claim 6, wherein The predefined conversion data includes a conversion table that maps a first set of letters, numbers, or alphanumeric strings to a second set of letters, numbers, or alphanumeric strings; and Converting the first field device identifier or the second field device identifier based on the conversion table includes: (i) Identify, in the conversion table, a mapping record capable of converting at least a segment of the first field device identifier or the second field device identifier from a first expression to a second expression, and (ii) replace, in the identified mapping record, a segment of the first field device identifier or the second field device identifier that matches the identified first letter, digit, or alphanumeric string with a second letter, digit, or alphanumeric string that is mapped to the identified first letter, digit, or alphanumeric string in the identified mapping record.

11. The method according to claim 6, wherein the predefined conversion data includes a conversion table that maps a first set of letters, numbers, or alphanumeric strings, which includes one or more subsets of wildcards, to a second set of letters, numbers, or alphanumeric strings, which also includes one or more subsets of wildcards; Generate a converted first field device identifier based on the first field device identifier; And Generate a converted second field device identifier based on the second field device identifier; Wherein, converting each of the first field device identifier and the second field device identifier includes: (i) identifying, in the conversion table, a mapping record capable of converting at least a segment of the first field device identifier or the second field device identifier from a first expression to a second expression, and (ii) replacing one or more non-wildcard segments of the first field device identifier or the second field device identifier that match a first non-wildcard segment of the identified first letter, digit, or alphanumeric string in the identified mapping record with one or more non-wildcard segments of the second letter, digit, or alphanumeric string that is mapped to the identified first letter, digit, or alphanumeric string in the identified mapping record.

12. A system for debugging field devices in a control system, the control system including at least one server and a plurality of input / output (I / O) ports communicatively coupled to the server, the system for debugging field devices including: Memory; And At least one processor configured to: Detect a connection event, the connection event including a connection of a field device and an I / O port communicatively coupled to the server through an interface; Extract a first field device identifier corresponding to the field device from the memory of the field device connected to the I / O port through the interface; Extract field device configuration data associated with the I / O port from a non-transitory memory database communicatively coupled to the server, where The field device configuration data at least includes a second field device identifier; and At least a segment of the second field device identifier is different from a corresponding segment of the first field device identifier; Generate one or both of a converted first field device identifier and a converted second field device identifier based on predefined conversion data; And In response to determining (i) that the converted first field device identifier does not match the second field device identifier, or (ii) that the converted second field device identifier does not match the first field device identifier, or (iii) that the converted first field device identifier does not match the converted second field device identifier, trigger an alert to be generated in the user interface.

13. The system according to claim 12, configured to implement a corrective action in response to determining that the converted first field device identifier does not match the second field device identifier, or in response to determining that the converted second field device identifier does not match the first field device identifier, wherein The corrective action includes any of the following: Update or modify the first field device identifier in the local memory of the field device connected to the I / O port through the interface; Or Disconnect the field device connected to the I / O port through the interface from the I / O port; or At the location of the field device already connected to the I / O port through an interface, another field device is coupled at the I / O port, and the other field device has a first field device identifier that matches the second field device identifier.

14. The system according to claim 12, configured such that the field device configuration data is a subset of engineering data, design data, or design specifications corresponding to the control system.

15. The system according to claim 14, wherein The field device configuration data identifies a set of field device attributes corresponding to a specified field device that has been identified as being connected to the I / O port through an interface.

16. The system according to claim 12, wherein The connection event includes connecting the field device to the I / O port.

17. The system according to claim 12, configured such that the predefined conversion data includes a conversion table or a conversion rule.

18. The system according to claim 17, configured such that: Generating the converted first field device identifier includes the step of transforming the first field device identifier based on the conversion table or the conversion rule being applied to the first field device identifier.

19. The system according to claim 17, configured such that: Generating the converted second field device identifier includes the step of transforming the second field device identifier based on the conversion table or the conversion rule being applied to the second field device identifier.

20. The system according to claim 17, configured such that the predefined conversion data includes a conversion rule for converting a physical device label or a system label represented by a first expression into a second expression.

21. The system according to claim 17, configured such that: The predefined conversion data includes a conversion table that maps a first set of letters, numbers, or alphanumeric strings to a second set of letters, numbers, or alphanumeric strings; and Converting the first field device identifier or the second field device identifier based on the conversion table includes: (i) In the conversion table, identify a mapping record that can cause at least one segment of the first field device identifier or the second field device identifier to be converted from a first expression to a second expression, and (ii) replace a segment of the first field device identifier or the second field device identifier that matches the first letter, digit, or alphanumeric string identified in the identified mapping record with the second letter, digit, or alphanumeric string mapped to the first letter, digit, or alphanumeric string in the identified mapping record.

22. The system according to claim 17, configured such that: The predefined conversion data includes a conversion table that maps a first set of letters, numbers, or alphanumeric strings including one or more subsets with wildcards to a second set of letters, numbers, or alphanumeric strings also including one or more subsets with wildcards; Generate a converted first field device identifier based on the first field device identifier; And Generate a converted second field device identifier based on the second field device identifier; Wherein, converting each of the first field device identifier and the second field device identifier includes: (i) in the conversion table, identifying a mapping record that can cause at least one segment of the first field device identifier or the second field device identifier to be converted from a first expression to a second expression, and (ii) replacing one or more non-wildcard segments of the first field device identifier or the second field device identifier that match the first non-wildcard segment of the first letter, digit, or alphanumeric string in the identified mapping record with one or more non-wildcard segments of the second letter, digit, or alphanumeric string mapped to the first letter, digit, or alphanumeric string in the identified mapping record.

23. A computer program product for debugging field devices in a control system, the control system including at least one server and a plurality of input / output (I / O) ports communicatively coupled to the server, the computer program product including a non-transitory computer-usable medium having computer-readable program code embedded therein, the computer-readable program code including instructions for performing the following steps in a processor-based computing system: Detecting a connection event, the connection event including a field device and an I / O port communicatively coupled to the server being connected through an interface; Extract the first field device identifier corresponding to the field device from the memory of the field device connected to the I / O port through an interface; Extract field device configuration data associated with the I / O port from a non-transitory memory database communicatively coupled to the server, where The field device configuration data includes at least a second field device identifier; and At least one segment of the second field device identifier is different from the corresponding segment of the first field device identifier; Generate one or both of a converted first field device identifier and a converted second field device identifier based on predefined conversion data; and In response to determining (i) that the converted first field device identifier does not match the second field device identifier, or (ii) that the converted second field device identifier does not match the first field device identifier, or (iii) that the converted first field device identifier does not match the converted second field device identifier, trigger an alert to be generated in the user interface.

Images