Automated Test Plan Generation for Vehicle Components

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The manual creation of test plans for vehicle components is time-consuming and resource-intensive, with complex information being exchanged between individuals via different data packets, leading to redundant data storage and memory inefficiencies.

Innovation Solution

A system with bi-directional user interfaces and a cloud-based test tool that allows for the selection and generation of component-specific and test-case-specific plans, using pre-defined attributes to automate the creation of test orders and documentation, reducing manual input and optimizing data exchange.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If manual creation of test plans is used, then test plans can be customized for each component and test case, but the process is very time-consuming and resource-intensive

Engineering Contradiction:
Improvecustomization of test plansVSAvoidtime consumption
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The system segments test plans into reusable templates and components that can be independently configured. Test plans are divided into modular elements (test cases, procedures, parameters) that can be selected and combined automatically based on component attributes, eliminating the need to manually create entire test plans from scratch for each component-test case combination.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system dynamically generates test plans based on input parameters such as component type, test case selection, and configuration attributes. The test plan structure adapts automatically to the specific component being tested, providing customization without manual intervention for each individual test plan creation.

Inventive Principle:
Principle #15Dynamics

2Manufacturing precision

If manual creation of test plans is used, then detailed specifications can be defined, but complex information must be exchanged between people via data packets taking up large memory space

Engineering Contradiction:
Improvetest plan specification precisionVSAvoiddata storage requirements
Core Design Contradiction:
Manufacturing precisionVSQuantity of substance

Solution Approach 1:

The system uses standardized data structures and schemas to represent test plan information, replacing redundant data packets with efficient digital representations. Test plan templates serve as reusable copies that can be instantiated multiple times without duplicating the entire plan definition, significantly reducing memory requirements while maintaining specification precision.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system implements a universal data exchange format that can represent multiple test plan configurations using a single standardized structure. This multi-functional data structure eliminates the need for separate data packets for different test scenarios, reducing overall data storage requirements while preserving detailed specification capabilities.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS20240354237A1System and method for testing different components using different test cases
Publication Date: 2024.10.24 DR ING H C F PORSCHE AG
  • US20240354237A1 patent drawing

AI summary

A system for testing different components using different test cases has a first user interface (12) for inputting component attributes across components and test attributes across test cases. Each component is defined by plurality component attributes across components and each test case is defined by plural test attributes across test cases. A computer-based test tool (30) has a test plan module (40), in which a test case-specific and component-specific test plan can be determined in each case from plural component attributes across components and a plurality test attributes across test cases. A second user interface (16) is provided for outputting a test-specific and component-specific test plan.