Collaborative D&E Platform for Reusable Industrial Data Transformation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing technologies face challenges in efficiently sharing solutions for industrial data transformation problems, including inefficiencies in data transformation, lack of transparency in solution implementation, and the need for complex customization processes that require specialized skills and resources.

Innovation Solution

A development and execution (D&E) platform that provides a graphical user interface for accessing a process flow editor and code editor, allowing users to arrange programming blocks, edit source code, compile, and execute them sequentially to transform data, while also enabling caching of output data and user feedback mechanisms.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If engineers develop custom solutions for data transformation tasks, then the specific data transformation problem is solved, but the solution cannot be easily shared or reused by other engineers

Engineering Contradiction:
Improvesolution effectivenessVSAvoidsolution sharing
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The patent implements a centralized solution repository where developed solutions are stored as reusable templates. Other engineers can copy these solutions and apply them to similar data transformation tasks without redeveloping from scratch. The system tracks solution usage and allows replication of successful patterns across multiple projects.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system pre-processes and structures solutions in a standardized format during development, adding metadata, tags, and documentation automatically. This preliminary organization enables easy retrieval and reuse by other engineers without requiring them to analyze the original code structure.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If engineers invest considerable resources into developing a solution, then the data transformation problem is solved, but the solution remains undocumented and undiscovered by colleagues

Engineering Contradiction:
Improveproblem resolutionVSAvoidsolution documentation
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The system automatically generates feedback reports when solutions are executed, capturing success metrics, performance data, and usage patterns. This feedback is stored and made visible to the engineering community, allowing others to learn from the effectiveness of documented solutions without needing to read through all the code.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system automatically documents solutions as they are developed and executed, extracting relevant information from code comments, variable names, and execution logs. This self-documentation reduces the burden on engineers to manually document their work while still making solutions discoverable and understandable to colleagues.

Inventive Principle:
Principle #25Self-service

3Adaptability or versatility

If conventional channels are used for customization requests, then the solution can be customized, but the process is complex and time-consuming

Engineering Contradiction:
Improvesolution customizationVSAvoidcustomization process time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system divides solutions into modular, independently customizable components or parameters. Users can modify specific aspects of a solution without affecting the entire system, enabling rapid customization through parameter adjustment rather than full redevelopment.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system provides dynamic configuration capabilities where solutions can be adjusted in real-time based on user needs. Parameters, data sources, and transformation rules can be modified on-the-fly without requiring formal change requests or lengthy approval processes.

Inventive Principle:
Principle #15Dynamics

4Reliability

If the entire software program is recompiled each time source code changes, then the updated code can be executed, but the testing process becomes tedious and time-consuming

Engineering Contradiction:
Improvecode execution accuracyVSAvoidrecompilation and testing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system compiles only the specific modules or functions that have been modified rather than the entire software program. This incremental compilation approach maintains code reliability while significantly reducing the time required to update and test changes.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary syntax checking and static analysis on modified code segments before full compilation, identifying obvious errors early. This preliminary validation reduces the need for extensive retesting after compilation and ensures that only valid code changes proceed to full build.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12321721B2Collaborative industrial integrated development and execution environment
Publication Date: 2025.06.03 SCHNEIDER ELECTRIC SYSTEMS USA INC
  • US12321721B2 patent drawing
  • US12321721B2 patent drawing
  • US12321721B2 patent drawing

AI summary

A method for providing access to a development and execution (D&E) platform for development of industrial software, including providing while the D&E platform is being accessed a GUI with a development tool having process flow and code editors and an execution tool and arranging two or more programming blocks of a process flow responsive to input from an author when the process flow editor is accessed. The two or more programming blocks, when arranged, are configured to be executed. The method further includes editing source code of the two or more programming blocks responsive to input from the author when the code editor is accessed, compiling at least one of the two or more programming blocks responsive to input from the author when the execution tool is accessed, and executing the compiled at least one programming block responsive to input from the author when the execution tool is accessed.