Alarm Configuration Deployment by Function Block in Distributed Control Nodes

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In process automation systems with distributed and heterogeneous hardware and software, deploying and updating alarms is cumbersome and error-prone due to the need for manual configuration and assignment of alarm configuration files, leading to potential hazardous conditions and inaccurate monitoring.

Innovation Solution

Assigning alarms to unique function block identifiers, enabling DCNs to request and retrieve appropriate alarm configuration files through a centralized alarm configuration service using function block identifiers, independent of DCN identifiers, facilitating robust and accurate alarm deployment and adaptation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual configuration and assignment of alarm configuration files is performed in distributed systems, then alarms can be deployed, but the deployment process becomes cumbersome and error-prone

Engineering Contradiction:
Improvealarm deployment accuracyVSAvoidalarm configuration complexity
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The alarm configuration file is automatically assigned to the appropriate distributed control node by the alarm configuration service based on function block identifiers. The system self-configures by matching the function block identifier in the alarm configuration request with the corresponding alarm configuration file in the database, eliminating manual intervention and reducing errors.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The alarm configuration service receives alarm configuration requests from distributed control nodes, queries the database using function block identifiers, and returns the appropriate alarm configuration files. This automated feedback loop ensures accurate deployment without manual errors while simplifying the operator's task.

Inventive Principle:
Principle #23Feedback

2Adaptability or versatility

If alarm configuration files are manually assigned to distributed control nodes, then alarms can be configured, but updates become difficult to manage across the distributed system

Engineering Contradiction:
Improvealarm update capabilityVSAvoidconfiguration management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The alarm configuration service provides a universal mechanism for both initial configuration and updates of alarm configuration files across all distributed control nodes. The same service infrastructure handles both deployment and updates, providing adaptability while managing complexity centrally rather than at each node.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The alarm configuration files are pre-stored in the database with their associated function block identifiers. When updates are needed, the system can efficiently retrieve and deploy updated files to the appropriate nodes without manual reconfiguration, enabling easy adaptation while maintaining simple node-level operations.

Inventive Principle:
Principle #10Preliminary action

3Ease of repair

If DCNs are replaced or reconfigured in distributed systems, then system maintenance can be performed, but alarm configuration files must be manually reassigned

Engineering Contradiction:
ImproveDCN replacement efficiencyVSAvoidreconfiguration time
Core Design Contradiction:
Ease of repairVSLoss of time

Solution Approach 1:

When a distributed control node is replaced or reconfigured, the new node automatically sends an alarm configuration request with its function block identifier. The alarm configuration service automatically retrieves the corresponding alarm configuration file from the database and assigns it to the new node, enabling rapid replacement without manual reconfiguration and reducing downtime.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The alarm configuration files are stored as reusable templates in the database associated with function block identifiers rather than being physically bound to specific nodes. When nodes are replaced, the configuration files are copied to the new nodes through automated retrieval, eliminating manual reassignment and reducing reconfiguration time.

Inventive Principle:
Principle #26Copying

4Extent of automation

If centralized alarm configuration service is implemented, then automated alarm deployment is achieved, but network communication requirements increase

Engineering Contradiction:
Improvealarm configuration automationVSAvoidnetwork infrastructure complexity
Core Design Contradiction:
Extent of automationVSDevice complexity

Solution Approach 1:

The alarm configuration service acts as an intermediary between distributed control nodes and the alarm configuration database. It receives standardized requests from nodes, performs automated lookup and assignment using function block identifiers, and returns appropriate configuration files. This intermediary approach achieves high automation while managing network complexity centrally through a single service point rather than peer-to-peer communications.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12406570B2Deploying process automation alarms to distributed control nodes
Publication Date: 2025.09.02 YOKOGAWA ELECTRIC CORP
  • US12406570B2 patent drawing
  • US12406570B2 patent drawing
  • US12406570B2 patent drawing

AI summary

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.