Network Test Instrument Interface for Failed Result Tracking

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In network testing, technicians often avoid saving failed test results, leading to inefficiencies and missed corrections, and less experienced technicians may struggle with complex test instruments, requiring improved tracking and guidance for project management and next operational steps.

Innovation Solution

A network test instrument with a user-friendly interface that displays project completion percentages, moves failed results to the top for easy identification, and provides 'FIX LATER' and 'TEST AGAIN' options, along with suggested next operational steps, helping technicians manage their workflow and prioritize retesting.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If technicians save all test results including failed tests, then complete documentation is achieved, but technicians experience psychological resistance and prefer to retest later

Engineering Contradiction:
Improvetest results documentationVSAvoidtechnician willingness to save results
Core Design Contradiction:
Loss of informationVSEase of operation

Solution Approach 1:

The test results are segmented into different categories (passed, failed, retested) with distinct visual indicators. Failed tests are separated and highlighted independently, allowing technicians to document all results without the psychological burden of mixing failures with successes. This segmentation makes the documentation process more manageable and less intimidating.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Different colors are used to indicate different test outcomes and statuses. Passed tests, failed tests, and retested items are displayed with distinct color coding, providing immediate visual feedback. This color-coding system makes it easier for technicians to track and document results without feeling overwhelmed by uniform presentation of all data.

Inventive Principle:
Principle #32Color changes

2Adaptability or versatility

If complex test instruments with multiple options are provided, then comprehensive testing capabilities are achieved, but less experienced technicians become confused about what test to perform

Engineering Contradiction:
Improvetesting capabilitiesVSAvoidtechnician understanding of test options
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The system introduces an intelligent intermediary layer that analyzes the network installation context and automatically recommends appropriate test suites. This intermediary processes the complexity of multiple test options and translates it into simple, context-appropriate recommendations, shielding less experienced technicians from overwhelming choices while maintaining comprehensive testing capabilities.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system provides feedback to technicians based on their experience level and the specific installation context. It learns from technician interactions and adjusts recommendations accordingly, guiding less experienced users through appropriate test selections while allowing experienced users to access full functionality. This feedback mechanism bridges the gap between complex capabilities and user expertise.

Inventive Principle:
Principle #23Feedback

3Reliability

If technicians retest failed cables later after corrective adjustments, then correction opportunities are preserved, but testing efficiency decreases and items may be missed

Engineering Contradiction:
Improvecorrection trackingVSAvoidtesting efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system performs preliminary organization of failed tests into a dedicated retest list with scheduled timing. Instead of waiting for technicians to remember to retest later, the system proactively prepares and manages the retesting workflow, tracking which cables need retesting and when. This preliminary organization maintains correction opportunities while significantly improving efficiency by preventing items from being missed.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The manual process of remembering and tracking failed tests for later retesting is replaced with an automated computer-based system. The instrument automatically tracks failed tests, maintains them in a retest queue, and prompts for retesting as needed. This substitution eliminates the inefficiency of manual tracking while preserving the necessary correction process.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

4Measurement precision

If individual cable test results are displayed separately, then detailed test information is provided, but technicians must move between screens and scroll to locate particular segments

Engineering Contradiction:
Improvetest result detailVSAvoidtime to locate cable results
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system merges the display of individual cable test results into a single comprehensive screen that shows all cables and their statuses simultaneously. Instead of requiring technicians to navigate between multiple screens for different cable segments, all results are combined in one view with visual indicators. This merging maintains detailed measurement precision while eliminating the time loss associated with screen navigation and scrolling.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentEP2627041B1Method and apparatus for testing and displaying test results
Publication Date: 2022.12.14 FLUKE CORP
  • EP2627041B1 patent drawingFigure 1
  • EP2627041B1 patent drawingFigure 2~5
  • EP2627041B1 patent drawingFigure 6~7

AI summary

A test instrument provides suggested next operational step function to provide a user with assistance during testing. A display is provided to show the amount of a project that has been completed, for example as a percentage completed value. Individual test results may be saved to a 'fix later' list, which may be later accessed to re-test items that may not have passed on initial testing.