Cross-Domain Automation Objects for Reusable Industrial Process Testing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The industrial automation industry lacks software that bridges the gap between design engineers with little or no computer science background and those with a computer science background, making it difficult to effectively design and test automation routines due to the lack of standardized testing tools and reusable test scripts.
Innovation Solution
A software framework that allows for the selection and integration of software automation objects from a library, enabling drag-and-drop functionality for creating test scripts that can be applied to individual or combined objects, reducing the need for custom scripting and facilitating efficient testing across various automation routines.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If standardized testing tools and reusable test scripts are implemented, then productivity and efficiency of testing automation routines is improved, but device complexity increases due to the need for software framework integration
Solution Approach 1:
The software automation objects are designed to be self-testing, with built-in test scripts that automatically execute when objects are added to the automation routine. The testing framework automatically discovers and runs relevant test scripts without requiring manual intervention, allowing the system to test itself
Solution Approach 2:
The testing framework is designed to be universally applicable across different automation objects and routines. A single framework infrastructure supports multiple object types (pumps, valves, tanks, sensors, belts) and can execute various test scripts through a common interface, eliminating the need for separate testing systems for each object type
2Reliability
If software automation objects with built-in test layers are created, then reliability of testing is improved, but manufacturing precision decreases due to the complexity of integrating multiple layers (control device, HMI, testing)
Solution Approach 1:
Each software automation object is segmented into distinct functional layers: the automated control device layer, the human machine interface layer, and the testing layer. This segmentation allows each layer to be developed, tested, and maintained independently while maintaining clear interfaces between them
Solution Approach 2:
The testing layer is merged with the software automation objects themselves, rather than being a separate external system. This integration ensures that testing capabilities are inherently part of each object, guaranteeing that reliability testing is performed consistently across all objects
3Adaptability or versatility
If virtualized industrial controllers are used to execute test scripts, then adaptability of the testing system is improved, but loss of time increases due to the overhead of virtualization
Solution Approach 1:
Virtualized industrial controllers create virtual copies of physical controllers to execute test scripts. These virtual copies replicate the essential functionality and behavior of real controllers, allowing tests to be run in a controlled environment without requiring actual industrial equipment, thus enabling adaptability across different controller types
Data Source
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.