Dynamic Data Transport via Metadata-Driven ERP-Plant Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current systems for connecting Enterprise Requirement Planning (ERP) systems to physical plant data monitoring systems are inflexible, require extensive customization, and involve high maintenance costs due to their static data models and all-or-nothing integration approaches, making them unsuitable for adaptive and scalable solutions.
Innovation Solution
A dynamic data transport system utilizing a Protocol Agnostic Metadata Schema (PAMS) and Media Independent Messaging Service (MIMS) for seamless and self-configuring connections between ERP systems and physical plant devices, allowing for protocol-independent data management and automatic adaptation to changes in data interfaces.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If extensive programming of devices is performed to support information across the network, then connectivity between enterprise systems and business systems is achieved, but system complexity and maintenance requirements increase significantly
Solution Approach 1:
The patent introduces a gateway device as an intermediary between enterprise systems and business systems. This gateway contains a protocol converter that automatically translates between different communication protocols, eliminating the need for extensive programming of individual devices. The gateway handles protocol conversion centrally, reducing complexity at the device level while maintaining connectivity.
Solution Approach 2:
The gateway device is designed with multi-functional capabilities to support multiple communication protocols simultaneously. It can act as a universal interface that connects various business systems (PLC, PAC, PC, mobile devices) to enterprise systems without requiring custom programming for each device type, thereby reducing overall system complexity.
2Adaptability or versatility
If changes are made to devices connected to the network, then system adaptability improves, but reprogramming of devices throughout the network is required
Solution Approach 1:
The gateway serves as a buffer that isolates enterprise systems from changes in business systems. When devices in the business system are changed or upgraded, the gateway's protocol converter automatically adapts to new protocols without requiring changes to enterprise systems or other network devices, eliminating reprogramming time.
Solution Approach 2:
The protocol converter in the gateway is designed to dynamically adapt to changing communication protocols. It can automatically detect and adjust to new protocols from modified devices, allowing the system to remain flexible and adaptable without requiring static reprogramming of all network devices.
3Adaptability or versatility
If coordination among various devices in the network is implemented, then system integration is achieved, but implementation complexity and coordination overhead increase
Solution Approach 1:
The patent merges the coordination function into a single gateway device that handles all protocol conversions and communications between enterprise systems and business systems. This centralizes the coordination overhead in one location rather than requiring distributed coordination among multiple devices, simplifying implementation while achieving full system integration.
4Stability of the object's composition
If static data models are used in current systems, then system stability is maintained, but flexibility and scalability are reduced
Solution Approach 1:
The gateway's protocol converter implements a dynamic data model that can automatically adapt to changing data structures and communication protocols from various business systems. This dynamic approach allows the system to scale and integrate new devices without compromising stability, as the gateway dynamically adjusts its conversion rules rather than relying on fixed static models.
Data Source
AI summary
A data transport system includes nodes configured to communicate with local devices via independent native protocols and to store a metadata schema that defines a data interface for process variables. The data transport system includes a computing system programmed to communicate with an application and the nodes using a media independent messaging service that is layered over respective communication protocols associated with the application and the nodes. The computing system receives, from the nodes, metadata corresponding to the data interface and dynamically render a web application programming interface (API) that allows users of the application to access the process variables.