OT-IT Data Mapping via Microservices for Industrial Automation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Industrial automation systems face challenges in integrating legacy systems with newer technologies, particularly in the IoT context, due to limitations in data transmission and integration between operation technology (OT) and information technology (IT) systems, which leads to inefficiencies in data management and analysis.

Innovation Solution

An OT/IT mapping system that uses microservices to dynamically map and route OT data to appropriate storage locations in an IT network without pre-defined point-to-point mappings, enabling seamless data integration and analysis across different formats and volumes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If pre-defined point-to-point mappings are used to connect OT devices to IT devices, then data transmission is straightforward and reliable, but the system complexity increases and adaptability to new technologies decreases

Engineering Contradiction:
Improvedata transmission reliabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a data namespace service as an intermediary layer between OT devices and IT systems. This service receives data from OT devices, standardizes it using data namespaces, and routes it to appropriate IT consumers. The intermediary abstracts the complexity of point-to-point mappings while maintaining reliable data transmission through standardized interfaces and routing mechanisms.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The data namespace service provides universal functionality by handling multiple types of data routing, transformation, and standardization through a single platform. Instead of requiring separate point-to-point connections for each device pair, the universal service manages all data flows, reducing overall system complexity while maintaining reliability.

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

2Stability of the object's composition

If pre-defined point-to-point mappings are used to integrate legacy systems, then integration is stable, but adaptability to IoT technologies and new systems is reduced

Engineering Contradiction:
Improveintegration stabilityVSAvoidadaptability to new technologies
Core Design Contradiction:
Stability of the object's compositionVSAdaptability or versatility

Solution Approach 1:

The patent implements dynamic data routing where the data namespace service can adapt routing paths and transformations based on real-time conditions, device types, and consumer requirements. This dynamic approach maintains stability through consistent standardized interfaces while enabling adaptability to new IoT devices and systems without pre-defined mappings.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system changes parameters such as data formats, protocols, and routing paths dynamically based on the source device type and target consumer requirements. This allows stable integration of legacy systems while adapting to new technologies by transforming data parameters rather than requiring fixed point-to-point connections.

Inventive Principle:
Principle #35Parameter changes

3Measurement precision

If manual data mapping and routing is performed, then data accuracy is maintained, but time consumption and productivity are reduced

Engineering Contradiction:
Improvedata accuracyVSAvoiddata processing speed
Core Design Contradiction:
Measurement precisionVSProductivity

Solution Approach 1:

The data namespace service implements self-service automation where the system automatically discovers data sources, determines appropriate routing paths, transforms data formats, and delivers data to consumers without manual intervention. This automation maintains data accuracy through consistent transformation rules while dramatically improving processing speed and productivity.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary actions by pre-configuring data namespace templates, transformation rules, and routing policies that automatically apply to incoming data. This preliminary setup enables rapid automated processing while maintaining accuracy through pre-validated transformation logic, eliminating the need for manual data mapping for each new device or consumer.

Inventive Principle:
Principle #10Preliminary action

4Stability of the object's composition

If standardized data analysis is implemented, then data consistency is improved, but system complexity increases

Engineering Contradiction:
Improvedata consistencyVSAvoidsystem complexity
Core Design Contradiction:
Stability of the object's compositionVSDevice complexity

Solution Approach 1:

The patent segments the data standardization process into distinct modular components including data reception, namespace resolution, format transformation, and routing. Each segment handles a specific aspect of standardization independently, making the overall system more manageable despite the increased complexity. The segmentation allows for targeted complexity in each module while maintaining overall data consistency.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS11409687B2Systems and methods for automatically mapping between operation technology data and information technology data
Publication Date: 2022.08.09 ROCKWELL AUTOMATION TECH INC
  • US11409687B2 patent drawing
  • US11409687B2 patent drawing
  • US11409687B2 patent drawing

AI summary

A system may include a data delivery pipeline communicatively coupled to one or more microservices that receive a dataset transmitted through the data delivery pipeline. The system may also include a first microservice that receives a first dataset corresponding to operation technology (OT) data or information technology (IT) data and determines a second dataset based on the first dataset. The system may also include a second microservice that receives the second dataset from the first microservice via the data delivery pipeline, determines an action to perform in an industrial automation component of an industrial automation system based on an analysis of the second dataset, and transmits the action to the industrial automation component via the data delivery pipeline.