In Situ System Testing Scheduler for Parallel Component Validation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Testing complex systems like HVAC systems is inefficient due to the need for in situ testing, where establishing and coordinating multiple operating conditions across multiple tests is challenging, and existing tools lack the ability to validate these conditions effectively.

Innovation Solution

A testing system that uses a scheduling algorithm and finite-state machines to dynamically coordinate component tests, allowing for parallel execution, monitoring of operating conditions, and managing constraints to minimize total testing time, while ensuring system safety and validity through test enabler and safety sets.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If in situ testing is performed on complex systems with multiple components, then system integration errors can be detected, but the total testing time increases significantly due to the need to establish and coordinate multiple operating conditions

Engineering Contradiction:
Improvesystem integration error detectionVSAvoidtotal testing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent divides the complex system into multiple independent components, each with its own finite-state machine (FSM) that can be tested separately. The system descriptor file parses component interconnections to identify independent testable units, allowing parallel testing of segmented components while maintaining system-level integration validation.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent performs preliminary actions by automatically establishing required operating conditions before each component test using tools that can set and validate conditions in advance. The scheduler pre-coordinates multiple operating conditions and validates their compatibility before executing tests, eliminating the need to establish conditions during test execution.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 3:

The patent implements dynamic test coordination through a scheduler that continuously monitors system state and adapts the testing sequence. Finite-state machines dynamically transition between test states based on current system conditions, allowing the testing process to flexibly adjust to changing operating conditions and enable parallel execution when conditions permit.

Inventive Principle:
Principle #15Dynamics

2Productivity

If automated tools are used to establish operating conditions, then testing efficiency improves, but the ability to coordinate and validate multiple operating conditions across multiple tests remains insufficient

Engineering Contradiction:
Improvetesting efficiencyVSAvoidcoordination and validation capability
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent creates a universal testing framework that handles multiple operating conditions across different components through a single coordinated system. The scheduler and finite-state machines provide multi-functional capabilities to establish, coordinate, and validate any combination of operating conditions for any component, replacing the need for separate specialized tools for each condition.

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

Solution Approach 2:

The patent implements feedback mechanisms where the scheduler continuously monitors the status of operating conditions and test execution, validating that conditions remain appropriate throughout testing. The finite-state machines provide feedback on component state, allowing the scheduler to adjust and re-coordinate conditions dynamically, ensuring continuous validation of multiple operating conditions.

Inventive Principle:
Principle #23Feedback

3Measurement precision

If component tests are executed sequentially to ensure proper coordination of operating conditions, then test accuracy is maintained, but the total testing time increases

Engineering Contradiction:
Improvetest accuracyVSAvoidtotal testing time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The patent segments the testing process into independent component tests that can be executed in parallel. Each component's finite-state machine manages its own test sequence, allowing sequential accuracy within each component while enabling parallel execution across components, thus maintaining test accuracy while reducing total time.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent dynamically determines which component tests can be executed in parallel by the scheduler based on operating condition compatibility. The system transitions from static sequential execution to dynamic parallel execution, maintaining accuracy through continuous validation of operating conditions while maximizing throughput by running independent tests simultaneously.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentEP3384268B1Systems for and methods of automatically scheduling and executing in situ tests on systems
Publication Date: 2023.10.25 NEXTPOWER LLC US
  • EP3384268B1 patent drawingFigure 1
  • EP3384268B1 patent drawingFigure 2
  • EP3384268B1 patent drawingFigure 3

AI summary

A testing platform tests an electrical and mechanical system such as an HVAC unit according to an algorithm that reduces the total testing time of the components of the system, while ensuring the safety of the system during system-wide testing. The platform uses constraints that are checked both before and during the testing to ensure that HVAC operating conditions are acceptable for starting and maintaining component tests. Preferably, the platform uses finite-state machines for each device to organize the component tests, allowing for monitoring of constraints and starting, pausing, and stopping component tests. Preferably, total test execution time is reduced by running component tests in parallel, running component tests based on loads of the components, or combinations of both.