Test File Version Reversion in Distributed Material Testing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional material testing systems face challenges in managing file versions effectively, leading to potential disruptions when issues arise with the active test file version, necessitating a solution that allows for reverting to an older, obsolete version while ensuring all users and systems use the same test file version for consistency and compliance.
Innovation Solution
A distributed material testing system with a central data repository manages file versions by designating an 'active' version and allowing higher-permission users to revert to older versions, while restricting lower-permission users to the active version, ensuring consistent testing and compliance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Stability of the object's composition
If a single active file version is enforced for all users, then version consistency and compliance are improved, but system reliability deteriorates when issues arise with the active version
Solution Approach 1:
The patent segments the file version system into multiple independent version branches (active version and obsolete versions). Each version can be managed independently, allowing the system to maintain the active version for consistency while preserving obsolete versions as fallback options. This segmentation enables users to switch between versions without affecting the overall system structure.
Solution Approach 2:
The patent implements parameter changes by allowing dynamic modification of file version status. The system can change a file's version state between active and obsolete, and enable reverting to previous versions when issues occur. This parameter flexibility resolves the contradiction by maintaining version consistency as the default while providing reliability through version reversal capabilities.
2Stability of the object's composition
If users are restricted to the active file version, then compliance and consistency are improved, but adaptability deteriorates when issues require alternative versions
Solution Approach 1:
The patent introduces dynamic version management where the system can transition from a static single-version model to a dynamic multi-version model when needed. Users normally operate on the active version for consistency, but the system dynamically enables access to obsolete versions when adaptability is required, such as when bugs need to be worked around or compliance requirements change.
Solution Approach 2:
The patent applies preliminary action by maintaining obsolete versions in advance before they are needed. Instead of creating versions only when required, the system proactively preserves previous versions in the repository, ready for potential reversal. This preliminary preservation of alternative versions enables quick adaptation when issues arise without compromising normal operational consistency.
3Reliability
If obsolete file versions are preserved for reversal, then reliability is improved, but device complexity increases
Solution Approach 1:
The patent introduces an intermediary version control mechanism that manages the complexity of multiple file versions. This intermediary system tracks version states, enforces permission rules, and coordinates reversals between active and obsolete versions. By placing this intermediary management layer, the system preserves reliability through version availability while containing complexity within the management mechanism rather than scattering it throughout the entire system.
Solution Approach 2:
The patent implements feedback mechanisms that monitor the state of file versions and automatically enforce version policies. The system provides feedback to users about which versions are available and what permissions they have, reducing the perceived complexity. When reversal is needed, the feedback loop guides users through the process, maintaining reliability while managing complexity through automated status tracking and permission enforcement.
Data Source
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.