Message Engine Protocol Normalization for Industrial Plants
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The complexity of information management in industrial settings due to varying messaging protocols and configurations leads to issues like failed communications, delayed responses, and increased overhead in processing cycles, making it difficult to configure and manage messaging systems effectively.
Innovation Solution
A message engine that normalizes messaging protocols and formats, providing a consistent interface for event exchange across systems, and supports real-time messaging, filtering, bridging, routing, and monitoring, while reducing the need for glue code through appropriate mapping and routing of messages.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If messaging protocols and formats are normalized through a message engine, then communication reliability and consistency are improved, but device complexity increases due to the need for protocol translation and mapping layers
Solution Approach 1:
A message engine is introduced as an intermediary component between disparate messaging systems. The message engine receives messages from various protocols (MQTT, HTTP, AMQP, etc.), normalizes them into a standard internal format, and routes them to appropriate destinations. This mediator approach improves communication reliability by ensuring consistent message handling while managing protocol complexity centrally rather than at each endpoint.
Solution Approach 2:
The message engine is designed with multi-functional capabilities to handle multiple messaging protocols (MQTT, HTTP, AMQP, JMS), perform normalization, routing, filtering, and monitoring. By consolidating these diverse functions into a single universal component, the system improves reliability through consistent message processing while avoiding the need for separate specialized components for each protocol.
2Adaptability or versatility
If custom glue code is used to integrate systems with different protocols and formats, then adaptability is improved, but ease of operation deteriorates due to difficult configuration and management
Solution Approach 1:
The message engine utilizes configurable parameters and metadata within messages to dynamically determine routing, filtering, and transformation rules. Instead of hard-coded glue code, the system changes its behavior based on message parameters, headers, and configured rules, enabling adaptable integration while maintaining ease of operation through centralized configuration management.
Solution Approach 2:
The message engine incorporates automatic protocol detection, message normalization, and routing decision-making capabilities. The system serves itself by automatically adapting to different protocols and formats without requiring manual customization of integration code for each scenario, thereby maintaining adaptability while significantly improving ease of operation.
3Productivity
If message routing and filtering are performed without normalization, then processing speed is improved, but manufacturing precision deteriorates due to inconsistent message handling
Solution Approach 1:
The message engine performs protocol normalization and format standardization as a preliminary action before messages enter the routing and filtering stages. By pre-processing messages into a consistent internal format, the system enables subsequent high-speed routing and filtering operations while maintaining manufacturing precision through consistent message handling throughout the processing pipeline.
Data Source
AI summary
Systems and methods that facilitate messaging capabilities within a plant (e.g., a unified plant model—UPM) via employing a message engine that normalizes messaging of various messaging protocols and formats, wherein various systems of such plant can map to the message engine; and provide a consistent interface where events are sent/received consistently across such system. Such messaging engines can facilitate communication (e.g., via preferred channels) to other services/products, wherein the configuration and management of messaging is consistent across the system.