Abstract: Implementations are described herein for commissioning a distributed control node (DCN) to a process automation network. In various implementations, one or more messages transmitted on the process automation network by the DCN announcing that the DCN has joined the process automation network may be detected. Based on the one or more messages, one or more operational technology (OT) capabilities of the DCN may be determined. Based on the one or more OT capabilities, the DCN may be commissioned to the process automation network, e.g., by configuring the DCN to cooperate with one or more other process automation nodes on the process automation network to implement an at least partially automated process.

Abstract: Implementations herein leverage knowledge about historical process automation facilities to automate designing a new process automation facility. A first level design input may be processed to generate a first embedding that encodes design aspect(s) of the requested process automation facility with a degree of detail commensurate with a first level of a hierarchy reflected by design documents typically used to design a process automation facility. The first embedding may be used to find first level reference embeddings that encode design aspects of reference process automation facilities. Second level reference embedding(s) may be identified based on mapping(s) from the selected first level reference embedding(s). Each second level reference embedding may encode design aspect(s) of a respective reference process automation facility with a degree of detail that is commensurate with a second level of the design document hierarchy.

Abstract: Implementations are described herein for automatic deployment of function block application programs (FBAPs) across process automation nodes of a process automation system. In various implementations, one or more constraints associated with execution of a FBAP may be identified. Based on the one or more constraints, a process automation system that includes a plurality of process automation nodes may be analyzed. Based on the analysis, a subset of two or more process automation nodes on which to distributively deploy the FBAP may be selected from the plurality of processing node. In response to selecting the subset, the FBAP may be distributively deployed across the two or more process automation nodes of the subset.

Abstract: Implementations are described herein for leveraging an “out-of-band” communication channel between nodes of a process automation system. In various implementations, an out-of-band communication channel may be established between two or more process automation nodes of a process automation system. The out-of-band communication channel may be outside of a process automation network through which the two or more process automation nodes are communicatively coupled with other process automation nodes of the process automation system. The two or more process automation nodes may cooperate with one or more of the other process automation nodes to implement an at least partially automated process. One or more characteristics of the process automation system may be monitored, and based on the monitoring, traffic may be selectively diverted from the process automation network to the out-of-band communication channel.

Abstract: Implementations are described herein for commissioning a device such as a distributed control node (DCN) for operation with a process automation system (PAS) using a portable setup device (PSD) and an “out-of-band” communication channel. In various implementations, static information conveyed by a passive data store of the DCN may be used to establish an out-of-band communication channel between the DCN and PSD. The out-of-band communication channel may be distinct from a process automation network through which the DCN is to be communicatively coupled with other process automation nodes of the PAS. The DCN may be commissioned to 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 cooperate with one or more of the other process automation nodes on the process automation network to implement an at least partially automated process.

Abstract: Implementations are described herein for provisioning a device such as a DCN with configuration data for operation on a process automation network using an “out-of-band” communication channel. In various implementations, a temporary out-of-band communication channel may be established between a first and second DCNs. The out-of-band communication channel may be distinct from a process automation network through which the first DCN is to be communicatively coupled with other process automation nodes of a process automation system. Provisioning data may be transmitted from the second DCN to the first DCN over the temporary out-of-band communication channel. The provisioning data may include: information technology (IT) configuration data and operational technology (OT) configuration data. Subsequent to the transmitting, the temporary out-of-band communication channel may be closed.

Abstract: Implementations are described herein for commissioning a distributed control node (DCN) to a process automation network. In various implementations, one or more messages transmitted on the process automation network by the DCN announcing that the DCN has joined the process automation network may be detected. Based on the one or more messages, one or more operational technology (OT) capabilities of the DCN may be determined. Based on the one or more OT capabilities, the DCN may be commissioned to the process automation network, e.g., by configuring the DCN to cooperate with one or more other process automation nodes on the process automation network to implement an at least partially automated process.

Abstract: Implementations are described herein for leveraging an “out-of-band” communication channel between nodes of a process automation system. In various implementations, an out-of-band communication channel may be established between two or more process automation nodes of a process automation system. The out-of-band communication channel may be outside of a process automation network through which the two or more process automation nodes are communicatively coupled with other process automation nodes of the process automation system. The two or more process automation nodes may cooperate with one or more of the other process automation nodes to implement an at least partially automated process. One or more characteristics of the process automation system may be monitored, and based on the monitoring, traffic may be selectively diverted from the process automation network to the out-of-band communication channel.

Abstract: An engineering apparatus according to the present disclosure generates generating executable code, which causes target hardware to operate, from a control application. The engineering apparatus includes an algorithm converter that converts control logic included in the control application into control logic code, a type management unit that outputs a type definition code corresponding to a data block structure of data held by a function block included in the control application, an instance management unit that outputs a memory allocation code that allocates an instance of the function block to memory, and a build controller that generates the executable code based on the control logic code, the type definition code, and the memory allocation code. Executable code for execution by target hardware is debugged while the executable code is in the form of a control application before conversion to a high-level language.

Abstract: A portion of executable code generated from a general-purpose high-level language can be changed easily while the executable code is running. An engineering apparatus (10) of the present disclosure includes an instance management unit (103) and a compiler/linker (104). When a control application is edited while the engineering apparatus (10) and target hardware (20) are connected online, the instance management unit (103) generates a list for control application switching and a program for control application switching. The list and the program are generated from the control application and expressed in a second programming language. The compiler/linker (104) generates executable code based on the list, the program, and a control service program. When the executable code is downloaded onto the target hardware (20), the control service program causes the program for control application switching to be executed on the target hardware (20).

Abstract: A portion of executable code generated from a general-purpose high-level language can be changed easily while the executable code is running. An engineering apparatus (10) of the present disclosure includes an instance management unit (103) and a compiler/linker (104). When a control application is edited while the engineering apparatus (10) and target hardware (20) are connected online, the instance management unit (103) generates a list for control application switching and a program for control application switching. The list and the program are generated from the control application and expressed in a second programming language. The compiler/linker (104) generates executable code based on the list, the program, and a control service program. When the executable code is downloaded onto the target hardware (20), the control service program causes the program for control application switching to be executed on the target hardware (20).

Abstract: An engineering apparatus (10) according to the present disclosure generates generating executable code, which causes target hardware (20) to operate, from a control application. The engineering apparatus (10) includes an algorithm converter (102) that converts control logic included in the control application into control logic code, a type management unit (103) that outputs a type definition code corresponding to a data block structure of data held by a function block included in the control application, an instance management unit (104) that outputs a memory allocation code that allocates an instance of the function block to memory, and a build controller (104) that generates the executable code based on the control logic code, the type definition code, and the memory allocation code. Executable code for execution by target hardware is debugged while the executable code is in the form of a control application before conversion to a high-level language.