An apparatus for commissioning a process automation system using a portable setup device

Abstract

Described herein are implementations for authorizing devices such as a distributed control node (DCN) to operate with a process automation system (PAS) using a portable setup device (PSD) and an "out-of-band" communication channel. In various implementations, an out-of-band communication channel can be established between the DCN and the PSD using static information conveyed by a passive data store of the DCN. The out-of-band communication channel can be separate from a process automation network that will communicatively couple the DCN with other process automation nodes of the PAS. The DCN can be authorized over the process automation system by exchanging operational technology (OT) data between the DCN and the PSD via the out-of-band communication channel to enable the DCN to coordinate with one or more of the other process automation nodes on the process automation network for the purpose of implementing at least a portion of an automated process.

Description

Background Art

[0001] A process automation system may include one or more process automation networks. A process automation network can be a major communication channel through which devices such as distributed control nodes (DCNs) communicate with other nodes of the process automation system, such as other DCNs, sensors, actuators, etc. Process automation networks are typically implemented using a reliable, high-speed communication technology with a fairly large bandwidth, such as Ethernet.

Summary of the Invention

Problems to be Solved by the Invention

[0002] In some process automation systems, the process automation network itself is used to operate as part of the process automation system, such as a DCN. However, this causes difficulties when additional devices, such as DCNs, are not configured using the parameters required to participate in the process automation network and receive and / or transmit data via the process automation network. This problem may be addressed by pre-configuring the additional devices to fit some known static network configuration. However, this may require a knowledgeable system integrator to set up another subnetwork to match the static network configuration of the devices before setting the devices to the preferred network configuration of the process automation network. In addition, device configuration, application deployment, or application upgrade is carried out as a manual process by the system integrator, which may lead to various negative results, especially errors, mistakes, and excessive use of resources. to operate as part of the process automation system commission in such a way used for

Means for Solving the Problem

[0003] For devices such as DCN, a portable setup device (PSD) and an "out-of-band" communication channel are used so that they can operate on a process automation network. by commissioning Embodiments for doing so are described herein. More specifically, without limitation, techniques for establishing an out-of-band communication channel between a DCN and a PSD, thereby enabling the PSD to acquire configuration data and provide and / or relay it to the DCN, are described herein. This PSD can be, by way of example, a mobile phone, a tablet computer, a laptop computer, a smartwatch, or is being commissioned any other mobile device that can be brought relatively close to the DCN.

[0004] The out-of-band communication channel is external to the process automation network used by devices such as DCN for communicating with each other, and thus can be separate from that process automation network. For example, in some embodiments, the out-of-band communication channel can be implemented using peer-to-peer (P2P) communication technologies such as Wi-Fi Direct, two-way near-field communication (NFC), Bluetooth, etc. (however, it is not essential that out-of-band communication be P2P in all cases). By utilizing such an out-of-band communication channel, more things can be done without manual intervention or effort than with device configuration. Furthermore, the process automation network itself does not bear or is not exposed to the data exchanged with devices such as DCN. Therefore, the techniques described herein can reduce errors, reduce the time, effort, and specialized knowledge required for the installation and / or replacement of devices such as DCN, and enhance the security of the process automation network. while commissioning without burdening or exposing it to the data exchanged with devices such as DCN. Therefore, the techniques described herein can reduce errors, reduce the time, effort, and specialized knowledge required for the installation and / or replacement of devices such as DCN, and enhance the security of the process automation network.

[0005] In various implementation forms, such as DCN commissioning Devices that are used can be equipped with a "passive data store" that contains static information that can be used to establish an out-of-band communication channel with the DCN. The passive data store that can be integrated with and / or fixed on the device can take various forms, including but not limited to visual displays such as barcodes and quick response (QR) codes, or passive electronic tags that use radio waves to transmit static information, such as radio frequency identification (RFID) transmitters and near field communication (NFC) transmitters. Similarly, the PSD can include one or more sensors (e.g., visual sensors, RFID sensors, etc.) configured to detect the static information transmitted by the passive data store. In some cases, such as when the passive data store is an RFID transmitter or an NFC transmitter, the sensors of the PSD can also activate the passive data store.

[0006] The static information transmitted by the passive data store can enable the PSD to establish an out-of-band connection with the DCN. For example, the static information can include identifiers of the DCN's P2P wireless interface, such as an Internet protocol (ID) address for Wi-Fi Direct or a Bluetooth address (BD_ADDR) for communication on a piconet. After establishing an out-of-band communication channel using this data, the PSD can provide (e.g., push, relay) information technology (IT) configuration data and / or operational technology (OT) configuration data to devices such as the DCN via the out-of-band communication channel. commissioning be provided (e.g., pushed, relayed).

[0007] IT configuration data can enable devices such as DCNs to participate in network communication with other nodes on the process automation network. IT configuration data can include networking parameters that can be used to participate in the process automation network and / or communicate via the process automation network. These parameters can include, for example, IP addresses, IP subnet masks, etc. IT configuration data can also include OT non-specific data related to the hardware or software of the device, such as firmware updates or operating system (OS) updates, redundancy policies, security policies, etc.

[0008] In contrast, OT configuration data can enable devices such as DCNs to cooperate (e.g., exchange commands and / or sensor data) with one or more actuators or sensors on the process automation network for the purpose of implementing at least partially automated processes. OT configuration data for DCNs can include, among other things, process automation applications to be installed on and / or operated by the DCN, scope limitations to be imposed on / by the DCN, preferred measurement units to be used by the DCN, update frequencies to be implemented by the DCN, one or more analog-to-digital conversion parameters to be used by the DCN, information about other nodes (e.g., their roles) within the process automation system, one or more signal conditioning parameters to be used by the DCN, security credentials to enable operation within the process automation system, error correction parameters (e.g., error correction code techniques) to be used by the DCN, etc.

[0009] To protect against unrecognized PSDs and unrecognized process automation nodes, various security measures can be implemented. Specifically, in some implementations, to ensure that only recognized PSDs can establish out-of-band communication channels with the DCN, the static information transmitted by the passive data store can be encrypted in whole or in part. Only a device (e.g., PSD) provided with appropriate credentials (e.g., public key) should be able to decrypt this static information. These credentials can be provided to the recognized PSDs by the vendor system associated with the DCN being supplied to the process automation facility, as part of supplying the DCN. In some implementations, the PSD may need to be authenticated using, for example, a username and / or password, two-factor authentication, etc., before receiving the credentials. In addition or alternatively, various techniques can be implemented to ensure that the recognized DCN can communicate with the process automation system. In some implementations, at least some of the static information (e.g., serial number, credentials, etc.) contained within the passive data store can be cross-checked separately by the PSD against the list of DCNs that are supposed to be provided to the process automation facility. if commissioning In some implementations, the PSD may need to be authenticated using, for example, a username and / or password, two-factor authentication, etc., before receiving the credentials. In addition or alternatively, various techniques can be implemented to ensure that the recognized DCN can communicate with the process automation system. seems communicate with the process automation system is commissioned by doing so In some implementations, at least some of the static information (e.g., serial number, credentials, etc.) contained within the passive data store can be cross-checked separately by the PSD against the list of DCNs that are supposed to be provided to the process automation facility. by commissioning In some implementations, at least some of the static information (e.g., serial number, credentials, etc.) contained within the passive data store can be cross-checked separately by the PSD against the list of DCNs that are supposed to be provided to the process automation facility.

[0010] In some implementations, the DC N uses the PSD and the out-of-band communication channel by commissioning The process to be performed can be relatively free of human intervention. However, this is not essential. In some implementations, the PSD can have a display, and a graphical user interface (GUI) can be rendered on this display, and the graphical user interface (GUI) can be operable to control how at least a portion of the OT data and / or IT data is implemented / stored / installed on the DCN. For example, the GUI can enable a system integrator to adjust various networking parameters and / or OT parameters as needed. In some implementations, the GUI the can be operable to authenticate the stem integrator it may be possible to commission by doing so .

[0011] In some implementations, the DCN but as part of a process automation system commission to make can be implemented using one or more processors, and the method includes detecting static information transmitted by a passive data store of the DCN via one or more sensors of a portable setup device (PSD), and based on the static information, establishing an out-of-band communication channel between the DCN and the PSD, where the out-of-band communication channel is external to a process automation network that will communicatively couple the DCN to other process automation nodes of the process automation system, and establishing a DC N to the process automation system commission for by commissioning is exchanging operational technology (OT) data between the DCN and the PSD via the out-of-band communication channel so that the DCN can cooperate with one or more of the other process automation nodes on the process automation network for the purpose of implementing at least partially automated processes useless

[0012] In various implementationscommissioning This can include exchanging information technology (IT) data between the DCN and the PSD via an out-of-band communication channel to enable the DCN to participate in the process automation network.

[0013] In various implementations, the OT data can include one or more OT capabilities of the DCN, and the method is to send a request for OT configuration data from the PSD to a remote computing system, where the request for OT configuration data is generated based on one or more OT capabilities of the DCN, sending, receiving the OT configuration data at the PSD, and pushing the OT configuration data to the DCN via an out-of-band communication channel, installing the OT configuration data on the first DCN, and promoting cooperation between the DCN and one or more of the other process automation nodes of the process automation system for the purpose of implementing at least partially automated processes. pushing. In various implementations, the request can be sent from the PSD to the remote computing system via the process automation network. In various implementations, the request can be sent from the PSD to the remote computing system via a wireless network separate from the process automation network. In various implementations, the PSD can take the form of a mobile phone, and the wireless network can be a cellular network.

[0014] In various implementations, the passive data store can include visual displays or passive electronic tags that use radio waves to communicate static information. In various implementations, the static information communicated by the passive data store can be encrypted, and the method can include decrypting the static information at the PSD. In various implementations, the out-of-band communication channel can be implemented using Bluetooth, bi-directional near-field communication (NFC), or Wi-Fi Direct. In various implementations, the method can further include rendering a graphical user interface (GUI) on a display of the PSD, the GUI being operable to implement at least a portion of the OT data on the DCN.

[0015] In another aspect, the PSD receives static information detected from one or more sensors and from the passive data store of the distributed control node (DCN) among one or more of the sensors, this DC N is being operable to act as part of a process automation system commission to receiving, establishing an out-of-band communication channel with the DCN based on the static information, the out-of-band communication channel being external to a process automation network that will communicatively couple the DCN with other process automation nodes of the process automation system, relaying operational technology (OT) configuration data obtained from a remote computing system to the DCN via the out-of-band communication channel to cause the OT configuration data to be installed on the DCN, whereby the DC N cooperates with one or more of the other process automation nodes on the process automation network for the purpose of implementing at least partially automated processes commission in such a way and can include circuitry for doing so.

[0016] In another aspect, the DCN is a passive data store that is wirelessly readable by sensors of a first and second communication interface and a portable setup device (PSD), and is configured to communicate static information regarding establishing an out-of-band communication channel with the first communication interface of the DCN. The out-of-band communication channel is external to a process automation network that will communicatively couple the DCN to other process automation nodes of a process automation system via the second communication interface. The passive data store participates in the out-of-band communication channel between the first communication interface and the PSD, receives operational technology (OT) configuration data and information technology (IT) configuration data relayed from a remote computing system by the PSD via the out-of-band communication channel, communicatively couples the second communication interface to the process automation network based on the IT configuration data, and is configured to exchange data with one or more of the other process automation nodes on the process automation network for the purpose of implementing at least partially automated processes based on the OT configuration data, and may include a circuit configured as such.

[0017] In addition, some implementations include one or more processors of one or more computing devices, the one or more processors being operable to execute instructions stored in an associated memory, and the instructions being configured to cause an implementation of any of the methods described above. Some implementations also include one or more non-transitory computer-readable storage media storing computer instructions executable by one or more processors for implementing any of the methods described above.

[0018] It should be understood that all combinations of the foregoing concepts, as well as additional concepts described in more detail herein, are contemplated as being part of the subject matter disclosed herein. For example, all combinations of the subject matter claimed in the claims that appear at the end of this disclosure are contemplated as being part of the subject matter disclosed herein.

Brief Description of the Drawings

[0019]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Modes for Carrying Out the Invention

[0020] As used herein, a "process that is at least partially automated" includes any process that is cooperatively performed by multiple devices within a process automation system with little or no human intervention. A common example of a process that is at least partially automated is a process loop in which one or more actuators operate automatically (without human intervention) based on the output of one or more sensors. Some processes that are at least partially automated can be sub-processes of an entire process automation system workflow, such as the single process loop described above. Other processes that are at least partially automated can include all or a significant portion of the entire process automation system workflow. In some cases, the degree to which a process is automated can exist along a gradient, range, or scale of automation. A process that is partially automated but still requires human intervention can be at or near one end of the scale. A process that requires less human intervention can be closer to the other end of the scale that represents a fully autonomous process. Process automation can generally be used to automate processes in a variety of fields, such as the manufacture, development, and / or improvement of chemical substances (e.g., chemical processing), catalysts, machinery, and the like.

[0021] Referring now to FIG. 1, an exemplary environment 100 in which various aspects of the present disclosure can be implemented is schematically illustrated. Within a process automation facility 108, a process automation management system 102 is operably coupled to a process automation network 106. (Also referred to herein alternatively as the "process automation system 108") The process automation facility 108 can take many forms and can be designed to perform any number of processes that are at least partially automated. For example, the process automation facility 108 can comprise all or a part of a chemical processing plant, an oil or natural gas refinery, a catalyst factory, a manufacturing facility, and the like.

[0022] The process automation network 106 can be implemented using various wired and / or wireless networks, including but not limited to the Institute of Electrical and Electronics Engineers (IEEE) 802.3 standard (Ethernet), IEEE 802.11 (Wi-Fi), 3GPP (registered trademark) Long Term Evolution (LTE) and other wireless protocols such as 3G, 4G, 5G, and subsequent generations, as well as cellular networks, and / or other types of communication networks with various types of topologies (e.g., mesh). Process automation is often used in scenarios where the cost of failure tends to be high in terms of both human safety and financial costs to stakeholders. Therefore, in various implementation forms, the process automation network 106 can be configured using redundancy and / or backup to enable high availability (HA) and / or high quality of service (QoS).

[0023] The process automation management system 102 can include commissioning module 104 and but the process automation facility 108, commission a new device for for commission to a database 105 that stores information used by module 104. commissioning Various aspects of the process automation management system 102, such as module 104, can be implemented using any combination of hardware and software. In some implementations, the process automation management system 102 can be implemented across multiple computer systems as part of what is often referred to as a "cloud infrastructure" or simply "the cloud." However, this is not essential, and in FIG. 1, by way of example, the process automation management system 102 is implemented within a process automation facility 108, for example, within a single building or across a single campus or other industrial infrastructure consisting of multiple buildings. In such an implementation, the process automation management system 102 can be implemented on one or more local computing systems, such as on one or more server computers.

[0024] In addition to the process automation management system 102, a variety of other nodes / devices are operably / communicatively coupled to the process automation network 106. In FIG. 1, by way of example, N (a positive integer) DCNs 110-1 through 110-N are operably / communicatively coupled to the process automation network 106. Each DCN can include circuitry or logic 112 that can take various forms, such as a processor that executes instructions in memory, a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), etc. Each DCN 110 can have a specific role to play within the process automation facility 108. By way of example, a "compute" DCN can control a process loop (e.g., a chemical process loop) in which various "field" devices (e.g., devices having sensors and / or actuators) interface with each other to implement several functional control blocks (FBs).

[0025] Each DCN 110 can have at least a portion of its OT capabilities, more generally, various input / output (I / O) and other hardware components that define its role in the process automation facility 108. The OT capabilities can vary significantly across industries. In some cases, the OT capabilities can include, but are not limited to, the number of I / O channels, one or more types of one or more I / O channels (e.g., type of actuator, type of sensor, etc.), range limits, nominal measurement units, nominal update frequencies, one or more analog-to-digital conversion parameters, one or more signal conditioning parameters, supported open standard protocols such as Open Platform Communications (OPC) Unified Architecture (OPC UA) and / or Modbus, or any combination thereof. In FIG. 1, by way of example, the first DCN 110-1 includes a float transmitter (FT) component 114-1 and an actuator (e.g., valve) 116-1. The second DCN 110-2 includes the FT component 114-2 but does not include an actuator. The third DCN 110-3 includes a sensor 118-3 but does not include an actuator.

[0026] Actuator 116 can be any electrical, hydraulic, mechanical, and / or pneumatic component that can be controlled to affect some aspect of the process automation workflow performed in process automation facility 108. In many cases, actuator 116 can perform its function in response to various signals, such as sensor signals or commands from compute DCNs (which can themselves monitor for the presence of sensor signals). Some non-limiting examples of actuator 116 include, but are not limited to, valves, pistons, rotors, switches, heaters, coolers, stirrers, injectors, vacuum-producing devices, belts, tracks, gears, grippers, motors, relays, servo mechanisms, and the like. Sensor 118 can take various forms. Some examples of sensor 118 include, but are not limited to, pressure sensors, temperature sensors, flow sensors (e.g., FT component 114), various types of proximity sensors, optical sensors (e.g., photodiodes), pressure wave sensors (e.g., microphones), humidity sensors (e.g., hygrometers), radiation dosimeters, laser absorption spectrometers (e.g., multipass optical cells), and the like.

[0027] Unlike DCNs 110-1 through 110-3, DCN 110-N does not include any input / output (actuators or sensors). Instead, DCN 110-N can be a "compute-only" DCN whose role is to facilitate cooperation between itself and one or more other DCNs 110 on process automation network 106 for the purpose of implementing at least partially automated processes. For example, DCN 110-N can control a single process loop (e.g., a chemical process control loop) in which one or more other DCNs 110 are involved. In some cases, such a compute DCN 110 can perform a role similar to that of an autopilot on an aircraft, i.e., the compute DCN 110 can receive various signals and, based on those signals as well as various criteria and / or thresholds, control various actuators. For example, compute DCN 110 can monitor various sensors 118 and / or FT components 114 to check data regarding chemical level, flow rate (e.g., through a valve), tank temperature, control rate, etc., and can control one or more actuators 116 based on this data and / or based on a comparison of this data with various criteria and / or thresholds. As an example, compute DCN 110-N can control actuator 116-1 by sending corresponding commands to DCN 110-1 that may optionally conform to the protocol specific to DCN 110-1.

[0028] As previously mentioned, whether as a new addition, replacement, or upgrade, DC N to process automation network 106 commission for can be, for example commissioning complicated and cumbersome because the process is at least partially carried out by exchanging data via process automation network 106. Thus, devices such as DCN 110 to , a portable setup device (PSD) 120 and an "out-of-band" communication channel 109 are used to enable operation on a process automation network by commissioning Improved techniques for doing so are described herein. More specifically, without limitation, techniques for establishing an out-of-band communication channel 109 between a DCN 110 and a PSD 120, thereby enabling the PSD 120 to acquire configuration data and provide and / or relay it to the DCN 110, are described herein. DCN11 0 is The techniques described herein can be used in a variety of situations, such as expanding the capabilities of a process automation facility 108, replacing low-performance, malfunctioning, disabled, or legacy nodes, reusing nodes for other purposes, and bringing the process automation facility 108 into compliance with various standards by commissioning can be done.

[0029] Figures 1 and 2 show a first DCN 110 - 1 is to enable operation within a process automation facility 108 is commissioned to Shows the scenario in progress. In FIGS. 1 and 2, each DCN110 includes a corresponding communication interface 113, and its communication interface 113 can be used to establish an out-of-band communication channel 109 between DCN110-1 and PSD120. As described above, PSD120 can take various form factors. In FIG. 1, PSD120 can take the form of a mobile phone, but in other implementations, PSD120 can be a mobile device with different form factors, such as a tablet computer, a laptop computer, a wearable smart device such as a smartwatch or a head-mounted display. Interfaces 113-1 to 113-N may all support the same communication technology, or they may support different communication technologies, and they may or may not be wireless personal area network (PAN) interfaces. For example, interface 113-1 may enable Bluetooth communication, and interface 113-2 may facilitate NFC or Wi-Fi Direct.

[0030] The out-of-band communication channel 109 established between the interface 113 of DCN110-1 and PSD120 is outside the process automation network 106. The out-of-band communication channel 109 may or may not be temporary. In a scenario where the process automation network 106 is implemented using Ethernet, the connection 107 between DCN110 and the process automation network 106 can be a registered jack (RJ) 45 connection in some implementations. In various implementations, the out-of-band communication channel 109 can be implemented using different communication technologies, such as NFC, Bluetooth, Wi-Fi Direct, etc. In many implementations, the out-of-band communication channel 109 can be wireless, but this is not necessarily required in all cases.

[0031] Each DCN 110 in FIGS. 1 and 2 includes a passive data store 115. The passive data store 115 can be a mechanism that transmits static information that enables other devices, such as PSD 120, to establish an out-of-band communication channel 109 with the DCN 110. In various implementations, the passive data store 115 can be integrated with and / or fixed on each DCN 110. The passive data store 115 may be able to transmit this static information to other devices within a specific range, for example, within a relatively close vicinity.

[0032] The passive data store 115 is referred to as "passive" herein because it may be able to communicate only unidirectionally, i.e., it may not be able to receive data. In many implementations, the passive data store 115 can be battery-free. For example, the passive data store 115 can take the form of a passive electronic tag that uses visual displays such as barcodes or quick response (QR) codes, or wireless waves to transmit static information, such as radio frequency identification (RFID) transmitters, near field communication (NFC) transmitters. In other implementations, the passive data store 115 can be powered and can take the form of a low energy transmitter such as a Bluetooth beacon.

[0033] PSD120 can include one or more sensors configured to detect static information transmitted by the passive data store 115, as indicated by the one-way arrow 117 in FIG. 1. In some cases, such as when the passive data store is a wireless power transmitter such as an RFID transmitter or an NFC transmitter, the sensors of the PSD can also activate the passive data store. In FIG. 1, PSD120 includes one or more visual sensors 122 (e.g., front and / or rear digital cameras commonly found on smartphones) capable of detecting static information transmitted by visual displays such as barcodes and QR codes (registered trademarks). Alternatively, the digital images captured by the visual sensors 122 may be subjected to optical character recognition (OCR) processing to detect static information in the form of text, for example, disposed on the surface of the DCN110. PSD120 also includes a wireless sensor 124 that can operate to detect static information from other forms of passive data stores 115 such as RFID tags, NFC tags, Bluetooth beacons, etc.

[0034] PSD120 can use the static information collected at 117 to establish an out-of-band communication channel 109 with the first interface 113-1 of the first DCN110-1. Then, the first DCN110-1 and PSD120 use the out-of-band communication channel 109 to 1 exchange IT data and / or OT data that can be used to operate within the process automation facility 108. commission to In some implementations, PSD120 can obtain the IP configuration and / or OT configuration required to do so from a remote computing system such as the process automation management system 102. In some such implementations, as shown in FIG. 2, PSD120 can establish and / or participate in a communication channel network 125 with the process automation management system 102. commission 1 commissioning of commissioning The communication channel network 125 may or may not be separate from the process automation network 106 and can be implemented in various ways. In some implementations commissioning The communication channel network 125 can be wirelessly established between the PSD 120 and the process automation management system 102 via, for example, one or more Wi-Fi networks or cellular networks.

[0035] For example, the first DCN 110-1 can send data indicating its OT capabilities to the PSD 120 via the out-of-band communication channel 109. Based on these OT capabilities, the PSD 120 commissioning can use the communication channel network 125 to request, for example, if commissioning OT configuration data from the module 104 or another DCN 110, and then the PSD 120 can send (e.g., push, relay) this OT configuration data to the first DCN 110-1 via the out-of-band communication channel 109. This OT configuration data can be used, for example, by the first DCN 110-1 to cooperate with other process nodes (e.g., DCNs 110-2 to 110-N) for the purpose of implementing at least partially automated processes within the process automation facility 108.

[0036] Similarly, the PSD 120 commissioning can use the communication channel network 125 to request, for example, if commissioning Module 104 can also request IT configuration data, and then PSD120 can transmit (e.g., push, relay) this IT configuration data to the first DCN110-1 via the out-of-band communication channel 109. In various implementations, the IT configuration data can include an IP address (e.g., a new IP address if the first DCN110-1 is being added to the process automation facility 108, or the IP address of another node being replaced by the first DCN110-1), and / or networking parameters such as a subnet mask, as well as other networking parameters and / or tools such as a public encryption key, a certificate, time-sensitive networking parameters, a domain name system (DNS) lookup table, etc. This IT configuration data can be installed on the first DCN110-1 so that the first DCN110-1 can participate in the process automation network 106 and exchange data via the process automation network 106.

[0037] In some implementations, for example, before the PSD can provide OT configuration data and / or IT configuration data to the first DCN110-1 via the out-of-band communication channel 109, PSD120 and / or is commissioning Module 104 can authenticate the first DCN110-1 to ensure that the first DCN110-1 is legitimate and does not pose a security risk to the process automation network 106. In FIG. 1, by way of example, PSD120 is operably coupled to one or more vendor systems 123 via one or more networks 126 (e.g., a cellular network, the Internet). The vendor system 123 may be associated with a vendor (not shown) of one or more components (e.g., DCNs 110-1 to 110-N) used within the process automation facility 108.

[0038] In some cases, the vendor system 123 can be configured to authenticate various types of credentials transferred to it by the PSD 120 (or the process automation management system 102) using a variety of different authentication techniques. As a non-limiting example, each DCN 110 can be provided with a public key from its corresponding vendor. The PSD 120 and / or the process automation management system 102 can use this public key to encrypt some handshake data, which is then sent to each vendor system 123. The vendor system 123 can decrypt the handshake data using its own private key. If the decryption is successfully performed, the DCN 110 can be authenticated, and the PSD 120 can allow the DCN 11 commissioning 0 to perform its role therein. Other variations of public key cryptography are contemplated. In other implementations, the PSD 120 can provide other credentials, such as digital certificates, and each vendor system 123 verifies the validity of the other credentials before the DC N Process automation facility 108 commission for PSD 120 can be allowed to implement the techniques herein for.

[0039] In some implementations, the vendor system 123 can verify not only that the DCN 110 is legitimate, but also whether the DCN 110 complies with the desired / required criteria related to the process automation facility 108. For example, various identification information related to the added DCN 110, such as serial number, model number, lot number, etc., can be cross-referenced with the purchase order and / or work order created for the process automation facility 108. In addition or alternatively, the IT capabilities and / or OT capabilities of the added DCN 110 can be compared with the known parameters of the process automation facility 108 and / or the process automation network 106 to ensure compliance. In some implementations, the vendor system 123 pushes digital keys / certificates, and / or other data containing this data, to the process automation management system 102 to commissioning enable the module 104 to perform these checks locally. As an example, for a large purchase order of DCNs, the vendor system 123 can provide a file or list of relevant information (such as serial / model number, capabilities, etc.) regarding the new DCN, and commission the module 104 can use it locally to perform these checks.

[0040] Referring now to Figure 3, the DCN 310 to be provisioned, the PSD 120, and the process automation network 106 commissioning An exemplary process flow between module 104 is schematically shown. In FIG. 3, time progresses downward on the page. In some cases, the process can start from DCN 310 (including actuator 316) being physically connected to process automation network 106, for example, using RJ-45 connection 107, but this is not essential. If such a physical connection is made, DCN 310 may initially be unable to participate in process automation network 106 or exchange data via process automation network 106 because DCN 310 lacks appropriate network parameters.

[0041] On the other hand, in FIG. 3, PSD 120 is brought close enough to DCN 310 (e.g., within the wireless range of DCN 310 or close enough to detect a visual display) to detect static information provided by a passive data store (not shown in FIG. 3, 115 in FIGS. 1-2). Using this static information (e.g., IP address, BD_ADDR), PSD establishes an out-of-band communication channel 109 with DCN 310.

[0042] In some implementations, as shown by the next arrow below it in FIG. 3, PSD 120 may need to authenticate itself to module 104 (e.g., by presenting credentials to process automation management system 102) before proceeding. PSD 120 can perform various types of authentication, such as username and / or password, digital certificate authentication, two-factor authentication. In some implementations where process automation network 106 includes a Wi-Fi subnet, PSD 120 may need to already be authenticated to participate in the Wi-Fi subnet, and in that case, the authentication may be carried over when PSD 120 operates to do so to process automation network 106. commission 0 before proceeding, it may be necessary for PSD 120 to authenticate itself to module 104 (e.g., by presenting credentials to process automation management system 102) ) commissioning There may be cases where authentication to module 104 is required. PSD 120 can perform various types of authentication, such as username and / or password, digital certificate authentication, two-factor authentication. In some implementations where process automation network 106 includes a Wi-Fi subnet, PSD 120 may need to already be authenticated to participate in the Wi-Fi subnet, and in that case, the authentication may be carried over when PSD 120 operates to do so to process automation network 106. 0 process automation network 106 commission for and carried over when PSD 120 operates to do so to process automation network 106.

[0043] Once certified, the PSD120 will commission to via the communication channel network 125 or via another network, e.g. if commissioning Requesting IT configuration data from module 104 and / or if commissioning The PSD 120 may obtain / receive IT configuration data from the module 104. The PSD 120 may then transmit (e.g., push, relay) all or a portion of this IT configuration data to the DCN 310 via an out-of-band communication channel 109. This IT configuration data may be usable by the DCN 310 to participate in the process automation network 106.

[0044] Similarly, the PSD120, as shown in Figure 3, commission to via the communication channel network 125 or via another network, e.g. if commissioning Requesting OT configuration data from the module 104 and / or if commissioning It may also receive OT configuration data from the module 104. The PSD 120 may then transmit (e.g., push, relay) all or a portion of this OT configuration data to the DCN 310 via an out-of-band communication channel 109. This OT configuration data may be usable by the DCN 310 to coordinate with other nodes on the process automation network 106 to perform at least a portion of an automated process.

[0045] 3, the IT configuration data is pushed to the DCN 310 by the PSD 120 before the OT configuration data. However, this is not intended to be limiting. In other implementations, the OT configuration data may be pushed before the IT configuration data, or the IT and OT configuration data may be pushed to the DCN 310 by the PSD 120 in parallel. commissioning As indicated by the dashed arrow from module 104 to DCN 310, in some implementations, when DCN 310 successfully joins the process automation network 106, OT configuration data can be pushed directly to DCN 310 rather than being relayed to DCN 310 by PSD 120.

[0046] The DCN 310 can then coordinate with various other process automation nodes that are communicatively coupled to the process automation network 106, for example, by exchanging commands and / or sensor data therewith via the process automation network 106 for purposes of performing an at least partially automated process. Once the DCN 310 is able to exchange data via the process automation network 106, in some implementations the DCN 310 or the PSD 120 can close the out-of-band communication channel 109.

[0047] FIG. 4 is a block diagram of a DC N To be able to operate as part of a process automation system commission to 4 illustrates a flowchart of an exemplary method 400 for performing a process automation management system according to an embodiment of the present invention. For convenience, the operations of the flowchart are described with reference to a system that performs those operations. The system may include various components of various computer systems, such as one or more components of the process automation management system 102, and / or other devices, such as the PSD 120 and / or the DCN 110 / 310. Additionally, although the operations of the method 400 are shown in a particular order, this is not intended to be limiting. One or more operations may be rearranged, omitted, or added.

[0048] In block 402, the system can detect static information transmitted by the passive data store (e.g., 115) of the DCN via one or more sensors (e.g., 122, 124), for example, by the PSD120. Based on the static information, in block 404, the system can establish an out-of-band communication channel (e.g., 109) between the DCN and the PSD, for example, by the PSD120. In various implementations, the out-of-band communication channel may be external to the process automation network (e.g., 106) that will communicatively couple the DCN to other process automation nodes of the process automation system.

[0049] In block 406, the system can, for example, by the PSD120, DC N to the process automation system commission for can do. In some implementations, block 406 commissioning of doing so can include, in block 408, exchanging IT data between the DCN and the PSD via the out-of-band communication channel to enable the DCN to participate in the process automation network. Similarly, block 406 commissioning of doing so can include, in block 410, exchanging OT data between the DCN and the PSD via the out-of-band communication channel to enable the DCN to cooperate with one or more of the other process automation nodes on the process automation network for the purpose of implementing at least partially automated processes.

[0050] In some implementations, method 400 can be fully automated, albeit to varying degrees. However, in some implementations, a user, such as a system integrator, commissioning It may be possible to intervene in the process, for example, to adjust parameters according to a specific process automation environment. For example, in block 412, the system can render, for example, by PSD120, a GUI on the display that is operable to implement IT data and / or OT data on the DCN. In some implementations, the PSD or DCN can configure the IT configuration / OT configuration in a specific (default) manner, but the GUI allows the user to make adjustments as needed.

[0051] Figure 5 is a flowchart showing an exemplary method 500 that can be implemented to practice selected aspects of the present disclosure by a PSD such as PSD120 according to the implementations disclosed herein. The operations of method 500 are shown in a particular order, but this is not intended to be limiting. One or more operations can be rearranged, omitted, or added.

[0052] In block 502, a PSD (e.g., 120) can receive static information detected from one or more of its sensors (e.g., 122, 124) from a passive data store (e.g., 115) of a distributed control node (DCN), where this DC N is is to operate as part of a process automation system commission to has been made. Based on the static information, in block 504, the PSD can establish an out-of-band communication channel (e.g., 109) with the DCN. As mentioned above, the out-of-band communication channel can be external to a process automation network that will communicatively couple the DCN to other process automation nodes of the process automation system.

[0053] In block 506, the PSD can be identified and / or authenticated using a remote computing system, such as by using the process automation management system 102 and / or the vendor system 123. Assuming that the authentication is successfully performed, in block 508, the PSD can relay the operational technology (OT) configuration data it obtained from the remote computing system to the DCN via an out-of-band communication channel. Thereby, the OT configuration data is installed on the DCN, for example, by the PSD and / or by the DCN, whereby the DC N is to cooperate with one or more of the other process automation nodes on the process automation network for the purpose of implementing at least partially automated processes commission in such a way can be made possible.

[0054] FIG. 6 is a flowchart showing an exemplary method 600 that can be implemented to practice a selected aspect of the present disclosure by a DCN, such as any of DCNs 110-1 to 110-N or DCN 310, according to the implementations disclosed herein. The operations of method 600 are shown in a particular order, but this is not intended to be limiting. One or more operations can be rearranged, omitted, or added.

[0055] In block 602, the DCN can participate in an out-of-band communication channel established between a first communication interface (such as a wireless PAN interface 113 in FIGS. 1-2) and the PSD (such as 120). In block 604, the DCN can receive, via the out-of-band communication channel, OT configuration data and IT configuration data relayed from a remote computing system by the PSD, as shown, for example, in FIG. 3.

[0056] Based on the IT configuration data received at block 604, the DCN can communicatively couple another communication interface (e.g., 107 of FIGS. 1 - 2) to the process automation network. Based on the OT configuration data received at block 604, the DCN can exchange data with one or more of the other process automation nodes on the process automation network for the purpose of implementing a process in which at least a part is automated.

[0057] FIG. 7 is a block diagram of an exemplary computing device 710 that can optionally be utilized to implement one or more aspects of the techniques disclosed herein. Computing device 710 typically includes at least one processor 714 that communicates with several peripheral devices via a bus subsystem 712. These peripheral devices can include a storage subsystem 724 that includes, for example, a memory subsystem 725 and a file storage subsystem 726, a user interface output device 720, a user interface input device 722, and a network interface subsystem 716. The input and output devices enable user interaction with computing device 710. The network interface subsystem 716 provides an interface to an external network and is coupled to a corresponding interface device within other computing devices.

[0058] The user interface input device 722 can include a keyboard, a pointing device (such as a mouse, trackball, touchpad, or graphics tablet), a scanner, a touch screen incorporated in a display, an audio input device (such as a speech recognition system, microphone, etc.), and / or other types of input devices. Generally, the use of the term "input device" is intended to include any and all types of devices and means for inputting information into the computing device 710 or onto a communication network.

[0059] The user interface output device 720 can include a display subsystem, a printer, a fax device, or a non-visual display such as an audio output device. The display subsystem can include a cathode ray tube (CRT), a flat panel device such as a liquid crystal display (LCD), a projection device, or any other mechanism for creating a visible image. The display subsystem can also provide a non-visual display, such as via an audio output device. Generally, the use of the term "output device" is intended to include any and all types of devices and means for outputting information from the computing device 710 to the user or to another machine or computing device.

[0060] The storage subsystem 724 stores the programming structures and data structures that provide the functionality of some or all of the modules described herein. For example, the storage subsystem 724 can include logic for implementing selected aspects of the methods of FIGS. 4-6 and for implementing the various components shown in FIGS. 1-3.

[0061] These software modules are generally executed by the processor 714 alone or in combination with other processors. The memory 725 used within the storage subsystem 724 can include several memories, such as a main random access memory (RAM) 730 for storing instructions and data during program execution, as well as a read-only memory (ROM) 732 in which fixed instructions are stored. The file storage subsystem 726 can provide persistent storage for program files and data files and can include a hard disk drive, a floppy disk drive and associated removable media, a CD-ROM drive, an optical drive, or a removable media cartridge. Modules implementing the functionality of some implementations can be stored by the file storage subsystem 726 within the storage subsystem 724 or within other machines accessible from the processor 714.

[0062] The bus subsystem 712 provides a mechanism for enabling the various components and subsystems of the computing device 710 to communicate with each other as intended. Although the bus subsystem 712 is shown schematically as a single bus, multiple buses can be used in alternative implementations of the bus subsystem.

[0063] The computing device 710 can be of various types, including a workstation, a server, a computing cluster, a blade server, a server farm, or any other data processing system or computing device. Due to the ever-changing nature of computers and networks, the description of the computing device 710 shown in FIG. 7 is intended only as a specific example for the purpose of illustrating some implementations. Many other configurations of the computing device 710 are possible that have more or fewer components than the computing device shown in FIG. 7.

[0064] Above, several implementation forms have been described and illustrated in this specification. However, various other means and / or structures can be utilized to implement the functions described in this specification and / or to obtain one or more of the advantages described in this specification, and such variations and / or modifications are each considered to be within the scope of the implementation forms described in this specification. More generally, all parameters, dimensions, materials, and configurations described in this specification are intended to be exemplary, and the actual parameters, dimensions, materials, and / or configurations are determined according to one or more specific application examples in which this teaching is used. Those skilled in the art will recognize, or be able to confirm through only ordinary experimentation, many equivalents of the specific implementation forms described in this specification. Therefore, it should be understood that the foregoing implementation forms are presented as merely an example, and that the implementation forms can be practiced in ways other than those specifically described and claimed within the scope of the appended claims and their equivalents. The implementation forms of this disclosure are directed to each individual feature, system, article, material, kit, and / or method described in this specification. In addition, any combination of two or more such features, systems, articles, materials, kits, and / or methods is included within the scope of this disclosure if such features, systems, articles, materials, kits, and / or methods do not conflict with each other.

Description of Reference Numerals

[0065] 100 Environment 102 Process Automation Management System 104 commissioning Module 105 Database 106 Process Automation Network 107 RJ-45 Connection 108 Process Automation Facility, Process Automation System 109 Out-of-Band Communication Channel 110 DCN, Compute DCN 110-1 First DCN 110-2 Second DCN 110-3 Third DCN 110-N Computing DCN 112 Circuit or Logic 113 Communication Interface 113-1 First Interface 113-2 Interface 113-3 Interface 113-N Interface 114 FT Component 114-1 Float Transmitter (FT) Component 114-2 FT Component 115 Passive Data Store 116 Actuator 116-1 Actuator 117 One-way Arrow 118 Sensor 118-3 Sensor 120 Portable Setup Device (PSD) 122 Visual Sensor 123 Vendor System 124 Wireless Sensor 125 commissioning Communication Channel Network 126 Network 310 DCN 316 Actuator 400 Method 500 Method 600 Method 710 Computing Device 712 Bus Subsystem 714 Processor 716 Network Interface Subsystem 720 User Interface Output Device 722 User Interface Input Device 724 Storage Subsystem 725 Memory Subsystem, Memory 726 File Storage Subsystem 730 Main Random Access Memory (RAM) 732 Read Only Memory (ROM)

Claims

1. A method for commissioning a distributed control node (DCN) to operate as part of a process automation system, the method being implemented using one or more processors, detecting, via one or more sensors of a portable setup device (PSD), static information transmitted by a passive data store of the DCN, the static information including an identifier usable to establish an out-of-band communication channel between the DCN and the PSD, establishing the out-of-band communication channel between the DCN and the PSD using the identifier within the static information, the out-of-band communication channel being external to a process automation network that will communicatively couple the DCN to other process automation nodes of the process automation system, commissioning the DCN with respect to the process automation system, including exchanging operational technology (OT) data via the out-of-band communication channel between the DCN and the PSD such that the DCN can cooperate with one or more actuators or sensors under other DCNs on the process automation network for the purpose of implementing at least partially automated processes, comprising the method.

2. The method of claim 1, wherein the commissioning step further includes exchanging information technology (IT) data via the out-of-band communication channel between the DCN and the PSD such that the DCN can participate in the process automation network.

3. The OT data includes one or more OT capabilities of the DCN, and the method includes sending, from the PSD to a remote computing system, a request for OT configuration data, the request for OT configuration data being generated based on the one or more OT capabilities of the DCN, receiving the OT configuration data at the PSD, A step of pushing the OT configuration data to the DCN via the out-of-band communication channel, including installing the OT configuration data on a first DCN and facilitating the cooperation between the DCN and one or more of the other process automation nodes of the process automation system for the purpose of implementing the at least partially automated process. The method according to claim 1 or 2, including this.

4. The method according to claim 3, wherein the request is transmitted from the PSD to the remote computing system via the process automation network.

5. The method according to claim 3 or 4, wherein the request is transmitted from the PSD to the remote computing system via a wireless network different from the process automation network.

6. The method according to claim 5, wherein the PSD includes a mobile phone and the wireless network includes a cellular network.

7. The method according to any one of claims 1 to 6, wherein the passive data store includes a visual display or a passive electronic tag that uses radio waves to transmit the static information.

8. The method according to any one of claims 1 to 7, wherein the static information transmitted by the passive data store is encrypted, and the method further includes a step of decrypting the static information at the PSD.

9. The method according to any one of claims 1 to 8, wherein the out-of-band communication channel is implemented using Bluetooth, two-way short-range wireless communication (NFC), or Wi-Fi Direct.

10. The method according to any one of claims 1 to 9, further including a step of rendering a graphical user interface (GUI) on the display of the PSD, wherein the GUI is operable to implement at least a part of the OT data on the DCN.

11. A portable setup device (PSD), including one or more sensors, Receiving static information detected from one or more of the sensors from a passive data store of a distributed control node (DCN), where the DCN is to be commissioned to operate as part of a process automation system, and the static information includes an identifier that can be used to establish an out-of-band communication channel with the DCN, and Using the identifier within the static information to establish an out-of-band communication channel with the DCN, where the out-of-band communication channel is external to a process automation network that will communicatively couple the DCN with other process automation nodes of the process automation system, and Relaying operations technology (OT) configuration data obtained from a remote computing system to the DCN via the out-of-band communication channel to install the OT configuration data on the DCN, thereby commissioning the DCN to cooperate with one or more actuators or sensors under other DCNs on the process automation network for the purpose of implementing at least partially automated processes and A circuit for performing and A portable setup device (PSD) comprising.

12. The PSD according to claim 11, wherein the OT configuration data is received from the remote computing system via the process automation network.

13. The PSD according to claim 11 or 12, wherein the OT configuration data is received from the remote computing system via a wireless network separate from the process automation network.

14. The PSD according to any one of claims 11 to 13, wherein one or more of the sensors are vision sensors and the passive data store comprises a barcode or a quick response (QR) code.

15. The PSD according to any one of claims 11 to 14, wherein the circuit is configured to identify the remote computing system based on the static information.

16. The PSD according to any one of claims 11 to 15, wherein the circuit is configured to identify the remote computing system based on data exchanged via the out-of-band communication channel.

17. The PSD according to any one of claims 11 to 16, wherein the circuit is configured to relay information technology (IT) data from the remote computing system to the DCN via the out-of-band communication channel, and the IT data enables the DCN to participate in the process automation network.

18. The PSD according to any one of claims 11 to 17, further comprising a display, wherein the circuit is configured to render a graphical user interface (GUI) operable to control on the display how the OT configuration data is installed on the DCN.

19. A distributed control node (DCN), a first and a second communication interface, and a passive data store wirelessly readable by a sensor of a portable setup device (PSD), the passive data store being configured to transmit static information including an identifier usable to establish an out-of-band communication channel with the first communication interface of the DCN, the out-of-band communication channel being external to a process automation network that will communicatively couple the DCN to other process automation nodes of a process automation system via the second communication interface, a passive data store, participating in the out-of-band communication channel between the first communication interface and the PSD, receiving, via the out-of-band communication channel, operational technology (OT) configuration data and information technology (IT) configuration data relayed from a remote computing system by the PSD, coupling the second communication interface communicatively to the process automation network based on the IT configuration data, exchanging data with one or more actuators or sensors under another DCN on the process automation network for the purpose of implementing at least partially automated processes based on the OT configuration data a circuit configured as such A distributed control node (DCN) comprising... **Claim 20** The DCN according to claim 19, wherein the first communication interface comprises a wireless personal area network (PAN) interface and the second communication interface comprises an Ethernet interface.

Images