Alias Configuration Reconciliation in Process Automation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional node identifiers in process automation facilities, such as connection strings and IP addresses, are not human-interpretable and do not easily scale, leading to challenges in tracking and managing distributed control nodes (DCNs), especially when changes occur in the system, causing the original alias configuration file to become stale.

Innovation Solution

Implement a method using a Global Discovery Server (GDS) to reconcile alias configuration files by querying registered aliases, verifying registrations, and generating an updated configuration file to identify discrepancies and unresponsive/malfunctioning nodes, enabling quick identification of changes and issues.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If traditional node identifiers (connection strings, IP addresses) are used to track DCNs, then the system can maintain basic connectivity, but the identifiers are not human-interpretable and do not easily scale

Engineering Contradiction:
Improvehuman interpretability of node identifiersVSAvoidcomplexity of node identification system
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent introduces an alias name service as an intermediary layer between human operators and the actual node identifiers. This service maintains a mapping between human-readable aliases and technical identifiers (connection strings, node IDs), allowing users to interact with the system using meaningful names while the underlying complex identifiers remain managed by the service. This resolves the contradiction by providing human interpretability without requiring changes to the underlying complex identification system.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If alias configuration files are created during system integration, then initial alias registration is achieved, but the configuration files become stale when system changes occur

Engineering Contradiction:
Improveaccuracy of alias configurationVSAvoidtime to update configuration files
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements a feedback mechanism where the system continuously monitors changes in the process automation facility and automatically updates the alias configuration files. The alias name service detects when new DCNs are added, existing ones are modified or removed, and accordingly updates the configuration files without manual intervention. This ensures the configuration files remain accurate (reliable) while eliminating the time loss associated with manual updates.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system performs self-updating of alias configuration files through automated detection and registration processes. When changes occur in the facility, the system automatically queries the alias name service, retrieves updated alias information, and updates its own configuration files without requiring manual intervention from operators. This self-service capability maintains configuration accuracy while eliminating the time investment required for manual updates.

Inventive Principle:
Principle #25Self-service

3Productivity

If manual tracking of DCN changes is performed, then configuration updates can be made, but the process is time-consuming and error-prone

Engineering Contradiction:
Improvespeed of configuration updatesVSAvoidaccuracy of configuration updates
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent replaces the manual mechanical process of tracking and updating DCN configurations with an automated electronic system. The alias name service and automated querying mechanisms electronically detect changes, retrieve updated information, and update configuration files programmatically. This substitution eliminates the human error-prone manual tracking process while increasing both the speed (productivity) and accuracy (reliability) of configuration updates simultaneously.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS12149500B2Alias configuration management
Publication Date: 2024.11.19 YOKOGAWA ELECTRIC CORP
  • US12149500B2 patent drawing
  • US12149500B2 patent drawing
  • US12149500B2 patent drawing

AI summary

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.