OT Workflow Namespace Mapping for Low-Code Device Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current IT low-code development tools are challenging for OT engineers and junior IT engineers to use effectively, as they are often designed for IT domains and not well-suited for OT domains, making it difficult to collect data and control OT domain processes without programming.
Innovation Solution
The implementation of an information processing method that generates workflows in the OT domain using a universal namespace rule, maps element IDs to a master controller's runtime, and determines target functions and bodies to execute, enabling easy control of OT devices without programming.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If IT low-code development tools are used for OT domain, then ease of operation is improved, but device complexity increases due to domain mismatch
Solution Approach 1:
The patent creates a universal low-code development platform that serves both IT and OT domains by establishing a unified namespace system. This namespace system allows the same low-code tools to work across different domains without requiring domain-specific adaptations, thereby maintaining ease of operation while reducing the complexity introduced by domain mismatches.
2Manufacturing precision
If universal namespace rule is implemented, then manufacturing precision is improved through accurate device control, but device complexity increases due to mapping requirements
Solution Approach 1:
The patent introduces a namespace mapping mechanism that acts as an intermediary layer between the unified namespace system and the actual OT devices. This mapping layer translates universal namespace identifiers into device-specific identifiers, enabling precise device control while abstracting away the complexity of direct device addressing from the low-code development process.
3Adaptability or versatility
If OT domain workflow is generated with universal namespace, then adaptability is improved, but device complexity increases due to runtime mapping
Solution Approach 1:
The patent implements a universal namespace system that enables workflows to be portable across different OT devices and domains. By using standardized namespace identifiers instead of device-specific identifiers, workflows gain adaptability and can be deployed to various devices without modification, while the runtime mapping infrastructure handles the complexity of translating these universal identifiers to device-specific contexts.
Data Source
AI summary
Various embodiments of the teachings herein include an information processing method. An example method includes: generating a workflow in an operations technology (OT) domain based on an instruction entered by a user, wherein the workflow defines an operation to be performed by a work cell in the OT domain, and identifications (IDs) of elements in the workflow are named using a universal namespace rule; mapping the IDs of the elements in the workflow to runtime of a master controller of the work cell; and determining a target function to be executed in the workflow based on the IDs of the elements that are mapped to the runtime and a target body to execute the target function.