Active Test File Rollback in Distributed Material Testing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional material testing systems face challenges in managing file versions effectively, leading to inconsistencies and potential disruptions when issues arise with the active test file version, necessitating a solution for seamless version management and user authorization.
Innovation Solution
A system and method for active file management in distributed material testing systems, allowing users with higher permissions to revert to an older version of a test file, while ensuring most users use the active version, with permission-based access and review mechanisms to maintain stability and compliance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Stability of the object's composition
If a single active test file version is enforced across all users, then testing consistency and compliance are improved, but system flexibility and ability to respond to issues are worsened
Solution Approach 1:
The patent segments user access rights into different permission levels (e.g., standard users vs. administrators), allowing standard users to access only the active version while administrators can access and revert to previous versions. This segmentation resolves the contradiction by maintaining testing consistency for most users while preserving version flexibility for administrators who need to respond to issues.
Solution Approach 2:
The patent applies local quality by providing different file access qualities to different user groups. Standard users receive read-only access to the active version for consistent testing, while administrators receive enhanced access including modification and version reversion capabilities. This localized differentiation maintains overall system stability while allowing targeted flexibility where needed.
2Adaptability or versatility
If users can freely access and modify any file version, then adaptability and problem-solving are improved, but system stability and compliance are worsened
Solution Approach 1:
The patent extracts the version reversion capability from general user access and isolates it to administrators only. This extraction ensures that while administrators maintain the flexibility to revert to previous versions for problem-solving, standard users cannot inadvertently disrupt system stability by modifying or switching versions.
Solution Approach 2:
The patent introduces an intermediary permission system that mediates between users and file versions. This permission framework acts as a gatekeeper, allowing administrators to access all versions for problem-solving while blocking standard users from accessing previous versions, thus maintaining system stability.
3Adaptability or versatility
If multiple file versions are stored and accessible, then adaptability to fix issues is improved, but device complexity and storage requirements are worsened
Solution Approach 1:
The patent implements dynamic access control where the set of accessible versions changes based on user permissions. For standard users, the system dynamically presents only the active version, while for administrators, it dynamically presents all historical versions. This dynamic behavior allows the system to maintain simplicity for most users while providing comprehensive version management capabilities to administrators.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Described herein are examples of distributed material testing systems that allow users with higher level and/or administrative permissions to revert to use of an older (and/or obsolete) version of a test file (and/or other file) as the "active" file version for testing. In some examples, users with lower level permissions are restricted to using the "active" version of a test file for testing, so as to ensure that most users and/or material testing systems use the same test file version. However, some users are authorized to make an older, obsolete, test file version the "active" test file version in case, for example, there is some issue with the current active test file version. Through this reversion, testing may be able to continue in at least some capacity while a new test file is prepared and/or the issues with the prior active test file are resolved.