Cross-Domain Test Objects for Reusable Industrial Automation Testing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The industrial automation industry lacks software that bridges the gap between engineers with little or no computer science background and those with a background in computer science, requiring custom creation of test scripts for each routine, leading to increased time, resources, and processing costs.
Innovation Solution
A test framework that allows software automation objects to be selected from a library, integrated into a user interface via drag and drop, and executed with associated test scripts, reducing the need for custom script creation and storage of large files by reusing scripts across routines.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If custom test scripts are created for each automation routine, then testing can be performed, but time and resources increase significantly
Solution Approach 1:
The patent implements a library of reusable software automation objects that can be copied and reused across multiple automation routines. Instead of creating custom test scripts for each routine, engineers can select pre-built software objects from the library and reuse them across different projects and routines, significantly reducing script creation time while maintaining testing capability.
Solution Approach 2:
The patent creates universal software automation objects that can serve multiple functions across different automation routines. These objects are designed to be adaptable and reusable in various contexts, allowing a single software object to be deployed across multiple projects and routines, thereby reducing the overall number of scripts needed and decreasing development time.
2Reliability
If custom test scripts are created for each automation routine, then testing can be performed, but processing costs increase
Solution Approach 1:
By implementing a library of reusable software automation objects, the system eliminates the need to recreate test scripts for each routine. The same software objects can be copied and reused across multiple projects, reducing processing costs associated with script creation and maintenance while preserving full testing capability.
Solution Approach 2:
The patent enables recovery and reuse of test scripts through the software object library. Instead of discarding scripts after a single use, the system recovers and stores them as reusable software objects that can be applied to future automation routines, thereby reducing processing costs associated with repeated script creation.
3Reliability
If custom test scripts are created for each automation routine, then testing can be performed, but resources increase
Solution Approach 1:
The patent implements universal software automation objects that can be used across multiple automation routines. This universality reduces the total quantity of test scripts that need to be stored and managed, as a single software object can serve multiple purposes across different projects and routines, thereby reducing storage requirements while maintaining comprehensive testing capability.
Solution Approach 2:
By using a library of reusable software objects that can be copied rather than storing duplicate scripts for each routine, the system efficiently manages storage resources. The software objects are stored once in the library and then copied as needed for different automation routines, significantly reducing the total storage requirement compared to maintaining separate custom scripts for each routine.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
The present disclosure is directed to systems, methods and devices for assisting with testing automated industrial process routines. The addition of a software automation object to a test execution user interface may be received. The software automation object may be added to the test execution user interface from a software object library comprising a plurality of software objects. Each of the software automation objects may include an automated control device layer, a human machine interface layer, and a testing layer. A request to initiate an operational test of the software automation object in the test execution user interface may be received. Upon receiving the request, the operational test may be executed, and test results for the operational test of the automation software object may be displayed on the test execution user interface.