Automation Application Testing via Code-Derived Safety Scenarios

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The increasing complexity of automation solutions makes it difficult to test application programs for safety, particularly due to limitations in automation languages used for programmable logic controllers, which hinder flexible and comprehensive testing.

Innovation Solution

A method and device for testing automation applications by processing data from automation languages in a test environment, which includes actual systems or simulations, and involves extracting input/output variables, adapting data types, generating test classes, and validating systems by comparing real and simulated behaviors.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual entry of test scenarios is used, then testing can be performed, but the process becomes cumbersome and time-consuming

Engineering Contradiction:
Improvesafety testingVSAvoidtest scenario entry time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by automatically generating test scenarios from the automation program code before actual testing begins. The test scenario generation unit parses the automation program and creates comprehensive test cases in advance, eliminating the need for manual entry during the testing phase and significantly reducing time loss.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The testing system applies self-service by enabling the automation program itself to generate its own test scenarios through automated parsing and analysis. The system extracts test data, variables, and execution paths directly from the program code, allowing the system to serve its own testing needs without external manual intervention.

Inventive Principle:
Principle #25Self-service

2Extent of automation

If automation languages for programmable logic controllers are used, then automation programs can be implemented, but flexible and comprehensive testing is limited

Engineering Contradiction:
Improveautomation program implementationVSAvoidtesting flexibility
Core Design Contradiction:
Extent of automationVSAdaptability or versatility

Solution Approach 1:

The patent introduces an intermediary layer consisting of the test scenario generation unit and test data extraction unit that sits between the automation language and the testing execution. This intermediary automatically translates automation program code into comprehensive test scenarios, bridging the gap between the limited automation language capabilities and the need for flexible, comprehensive testing.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system applies parameter changes by dynamically extracting and analyzing various parameters from the automation program code, including variables, data types, execution conditions, and safety parameters. This allows the testing framework to adapt to different automation programs and their specific parameters, enhancing testing versatility without changing the core automation language.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If complex test scenarios are manually created, then safety testing can be attempted, but the process is cumbersome and limited to a subset of scenarios

Engineering Contradiction:
Improvesafety-critical area protectionVSAvoidtest scenario complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies the extraction principle by separating test scenario generation from manual creation processes. The test scenario generation unit automatically extracts all necessary test information, variables, and execution paths directly from the automation program code, removing the burden of manually creating complex test scenarios while ensuring comprehensive safety coverage.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system applies copying by creating virtual copies of the automation program's execution paths and logic flows as test scenarios. Instead of manually designing each test case, the system automatically generates copies of the program's operational logic as executable test sequences, ensuring complete scenario coverage without manual intervention.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS20250061054A1Testing of Automation Applications
Publication Date: 2025.02.20 SIEMENS AG
  • US20250061054A1 patent drawing
  • US20250061054A1 patent drawing
  • US20250061054A1 patent drawing

AI summary

Device and method for testing automation applications in a manner that improves the testing of the automation application, wherein data of an automation language for a test environment is processed, where the test environment includes a test environment for the actual system of the automation application and/or for at least one simulation of the automation application, and where at least one test of the test environment is performed such that. It is that the improved testing advantageous enables a safer automation solution.