Abstract: Implementations described herein relate to a scalable alias update framework for process automation. In various implementations, an alias server detects one or more changes to one or more aliases registered to one or more nodes of a process automation facility, each node including a sensor or actuator, and the process automation facility including a plurality of distributed control nodes (DCNs) operably coupled via a process automation network. The alias server formulates one or more alias change notifications signaling one or more alias changes. The alias server takes one or more mitigative actions to mitigate an anticipated surge of incoming network traffic at the alias server responsive to the alias change notification message. The alias server broadcasts the one or more alias change notifications over one or more asynchronous publish-subscribe (PUB/SUB) channels that are subscribed to by at least some subscriber clients hosted by one or more of the DCNs.

Abstract: Implementations obtain a current set of operating data that includes multiple disparate types of data and for each of the multiple disparate types of data, a corresponding most recently determined instance thereof. The current set of operating data is processed using a trained machine learning model to generate output that indicates a current operating condition of a process automation server. The process automation server operates on server hardware that is located within a process automation facility, and controls one or more aspects of a process performed within the process automation facility. Based on the output generated using the machine learning model, a determination is made regarding whether the current operating condition of the process automation server is normal. In response to determining that the current operating condition of the process automation server is not normal, automatic performance of remediating action(s) is caused.

Abstract: Implementations disclosed herein are directed to process automation server prioritization. In various implementations, a first priority may be assigned to a first subscriber process that subscribes to one or more input/output (I/O) channels managed by a platform-independent server hosted by a distributed control node (DCN) of a process automation facility, the one or more I/O channels including one or more of a sensor or an actuator. A second priority may be assigned to a second subscriber process that subscribes to one or more of the I/O channels hosted by the platform-independent server hosted by the DCN, the second priority being lower than the first priority. In response to determining that the server is experiencing performance degradation, interaction of the platform-independent server with the first subscriber process may be prioritized over the second subscriber process, based on the first and second priorities.

Abstract: Various implementations described herein relate to managing redundant aliases. In various implementations, an alias registered to multiple nodes of a process automation facility may be identified, each node including a sensor or actuator. The method includes using the alias, concurrently subscribing to first and second nodes of the multiple nodes. While concurrently subscribed to both the first and second nodes, and while a first criterion is satisfied, the method includes exchanging data with the first and second nodes. The method further includes, based on the data exchanged with the first node, contributing to a process control loop of the process automation facility. The method further includes disregarding data received from the second node. Upon determining that the first criterion is no longer satisfied or that a second criterion is satisfied, the method includes exchanging data with at least the second node.

Abstract: Methods, systems, and apparatus are disclosed for rendering a visualization of alias relationships of one or more components. A client device may receive alias information from an alias name service (ANS) of a global discovery server (GDS) and may render content based on the received alias information. For example, a client device otherwise limited to exclusively providing content indicating a component’s default nomenclature (e.g., “DCN 132.546”), e.g., without alias information, may instead provide aliased content indicative of a component’s function (e.g., “DCN Water Filtration”). Further, a client device otherwise limited to exclusively providing textual content may instead provide graphic content (e.g., schematics, flowcharts, etc.) in addition to and/or in lieu of the textual content based on received alias information.

Abstract: Implementations relate to generating, updating, and/or deploying process automation alarms in a process automation system, such as a system that includes distributed and/or heterogeneous hardware and/or software. Some of those 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 distributed control node (DCN), for local utilization by the DCN in alarm monitoring based on a function block having the function block 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: 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.