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: Methods, systems, and apparatus are disclosed for implementing a request for filtered updated resources associated with aliases. A CPC may be configured to request a filtered updated list of registered aliases associated with one or more resources. The updated list may be filtered based on a state of a DCN, on which the CPC is hosted. For example, the updated list may be filtered based on a timestamp associated with receipt of a previous list, based on a group the DCN is associated with, based on manufacturers, and/or based on security level (associated with the DCN, and/or associated with updates).

Abstract: Implementations relate to receiving, from a distributed control node (DCN) that includes a corresponding active alarm engine, an alarm configuration transmission that includes a network addressable DCN identifier of the DCN and also includes a direct or indirect indication that the DCN is implementing alarm monitoring that is based on function block(s) of a process automation system. Implementations further relate to, in response to receiving the alarm configuration transmission and determining that no persistent connection-oriented communication session is established between an alarm viewer and the DCN indicated by the addressable DCN identifier of the alarm configuration transmission, causing the alarm viewer to establish a persistent connection-oriented communication session with the DCN using the addressable DCN identifier.

Abstract: Implementations transmit, to a distributed control node (DCN), default alarm configuration file(s) that are determined based on a particular type of function block. Those implementations transmit the default alarm configuration file(s) to the DCN based on determining that the DCN is executing a function block that is of the particular type and/or is utilizing a function block, that is of the particular type, in alarm monitoring. A default alarm configuration file that is transmitted to a DCN can be stored locally at the DCN to enable viewing and/or editing thereof via human-machine interface (HMI) interfacing with the DCN. Implementations additionally or alternatively relate to reflecting, in an alarms database accessible via a process automation network, local updates that are made via an HMI to a default alarm configuration file locally stored at a DCN.

Abstract: Methods, systems, and apparatus are disclosed for implementing a request for filtered updated resources associated with aliases. A CPC may be configured to request a filtered updated list of registered aliases associated with one or more resources. The updated list may be filtered based on a state of a DCN, on which the CPC is hosted. For example, the updated list may be filtered based on a timestamp associated with receipt of a previous list, based on a group the DCN is associated with, based on manufacturers, and/or based on security level (associated with the DCN, and/or associated with updates).

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 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 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: Methods, systems, and apparatus are disclosed for implementing a request for filtered updated resources associated with aliases. A CPC may be configured to request a filtered updated list of registered aliases associated with one or more resources. The updated list may be filtered based on a state of a DCN, on which the CPC is hosted. For example, the updated list may be filtered based on a timestamp associated with receipt of a previous list, based on a group the DCN is associated with, based on manufacturers, and/or based on security level (associated with the DCN, and/or associated with updates).

Abstract: Implementations relate to providing an alarm configuration GUI via which a user can interact in defining corresponding alarms for corresponding function block identifiers of a process automation system. For example, a user can interact with the alarm configuration GUI in selecting a function block identifier and in defining parameter(s) for an alarm configuration file to be assigned to the function block identifier. Some implementations additionally or alternatively relate to transmitting the alarm configuration file to a DCN, for local utilization by the DCN in alarm monitoring based on a function block having the function block identifier. The transmitting can be responsive to determining that the DCN implements local alarm monitoring based on the function block, and the alarm configuration file being assigned to the function block identifier.

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: Methods, systems, and apparatus for implementing a redundant DCN system over a process automation network. In one aspect, a redundant DCN system includes a primary DCN, a backup DCN, and a keep alive process configured to determine whether the primary DCN becomes unavailable, wherein in response to the primary DCN being determined as unavailable, the backup DCN is reassigned as a new primary DCN, and assumes functions previously executed by the former primary DCN. Each DCN in the redundant DCN system may have a unique virtual IP address or transfer a common virtual IP address. Virtual IP addresses may impact communications between DCNs and other devices.

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 relate to storing, in alarms database for a process automation system, an association of an alarm configuration file to a function block identifier of a function block that corresponds to the alarm configuration file. Some implementations relate to a node transmitting, via a process automation network, an alarm configuration request that includes the function block identifier and receiving, in response to the request and via the network, the alarm configuration file. The node can include the function block identifier in the alarm configuration request based on the corresponding function block being executed by the node and/or being utilized in alarm monitoring by the node. Some implementations additionally or alternatively relate to receiving the alarm configuration request, and identifying the alarm configuration file based on it being stored, in the alarms database, in association with the function block identifier of the alarm configuration request.

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 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 reconciling alias configuration files. In various implementations, networking information may be retrieved from an alias server. The networking information may correspond to registered aliases of a plurality of data sources made accessible by a plurality of distributed control nodes (DCNs) of a process automation facility. The plurality of DCNs may be interrogated based on the networking information corresponding to the registered aliases. Based on responses to the interrogating, an updated alias configuration file may be generated and compared with a previously utilized alias configuration file.

Abstract: Implementations are described herein for determining whether to allow a cross-platform process automation client to write to an I/O channel controlled by a cross-platform process automation server. In various implementations, the cross-platform process automation client transmits a request to access a writer account of the cross-platform process automation server to the cross-platform process automation server, to write to the I/O channel. In response to receiving the request to access the writer account, the cross-platform process automation server determines whether the writer account is available. If the writer account is determined as being unavailable (e.g., currently being used by another cross-platform process automation client), the cross-platform process automation server can deny the request from the cross-platform process automation client to access the writer account, and/or provide the cross-platform process automation client access to a reader account.