Active file management in distributed materials testing systems

Abstract

This system provides a distributed materials testing system that allows users with higher-level administrative permissions to revert to older versions of test files as the "active" file version for testing. [Solution] To ensure that most users and / or the material testing system 100 use the same test file version, users with lower-level permissions are restricted to using the "active" version of the test file for testing. On the other hand, if there are any problems with the current active test file version, some users are granted the authority to make an older, deprecated test file version the "active" test file version.

Description

Technical Field

[0001] [Cross - Reference to Related Applications] This application claims the priority and benefit of U.S. Provisional Patent Application No. 63 / 694,972, filed on September 16, 2024, entitled "ACTIVE FILE MANAGEMENT IN DISTRIBUTED MATERIAL TESTING SYSTEMS". The entire content of this U.S. Provisional Patent Application is incorporated herein by reference.

[0002] This disclosure relates generally to distributed material testing systems, and more particularly to active file management in distributed material testing systems.

Background Art

[0003] Material testing machines are used to test the attributes (e.g., tensile strength / compressive strength) of various material specimens. Specific test methods (also referred to as test procedures) can vary for each material specimen and / or material testing machine.

[0004] By comparing such systems with the present disclosure described in the remainder of this application with reference to the drawings, the limitations and disadvantages of conventional and traditional approaches will become apparent to those skilled in the art.

Summary of the Invention

[0005] This disclosure relates to active file management in a distributed material testing system that is substantially illustrated by and / or described with respect to at least one of the figures and more fully described in the claims.

[0006] In addition to these and other advantages, aspects, and novel features of the present disclosure, the detailed content of the illustrated examples of the present disclosure will be more fully understood from the following description and the drawings.

Brief Description of the Drawings

[0007] [Figure 1] This figure shows an example of a materials testing system according to an aspect of the present disclosure.

[0008] [Figure 2] This is a block diagram of the material testing system illustrated in Figure 1, according to an aspect of this disclosure.

[0009] [Figure 3] This is a block diagram of an exemplary dispersed materials testing system according to the embodiments of this disclosure.

[0010] [Figure 4] This is a block diagram of a central data repository in an example of the distributed materials testing system illustrated in Figure 3, according to the aspects of this disclosure.

[0011] [Figure 5] This flowchart shows the test file management process for an example of the distributed materials testing system shown in Figure 3, according to the aspects of this disclosure.

[0012] [Figure 6a] This figure shows an example of a graphical user interface (GUI) that may be shown in the test file management process in Figure 5 according to an aspect of this disclosure. [Figure 6b] This figure shows an example of a GUI that may be shown during the test file management process in Figure 5, according to an aspect of this disclosure. [Figure 6c] This figure shows an example of a GUI that may be shown during the test file management process in Figure 5, according to an aspect of this disclosure. [Figure 6d] This figure shows an example of a GUI that may be shown during the test file management process in Figure 5, according to an aspect of this disclosure. [Figure 6e] This figure shows an example of a GUI that may be shown during the test file management process in Figure 5, according to an aspect of this disclosure. [Figure 6f]This figure shows an example of a GUI that may be shown during the test file management process in Figure 5, according to an aspect of this disclosure. [Figure 6g] This figure shows an example of a GUI that may be shown during the test file management process in Figure 5, according to an aspect of this disclosure. [Figure 6h] This figure shows an example of a GUI that may be shown during the test file management process in Figure 5, according to an aspect of this disclosure. [Modes for carrying out the invention]

[0013] The figures are not necessarily on a uniform scale. Where appropriate, the same or similar reference numerals are used in the figures to refer to the same or identical elements. For example, reference numerals with letters (e.g., gripping part 124a, gripping part 124b) refer to the same reference numerals without letters (e.g., gripping part 124).

[0014] This specification discloses examples of distributed materials testing systems that allow users with higher permissions and / or administrative permission to revert to using older (and / or obsolete) versions of test files (and / or other files) as the “active” file version for testing. In some examples, to ensure that most users and / or materials testing systems use the same test file version, users with lower-level permissions are restricted to using the “active” version of the test file for testing. On the other hand, if, for example, there is a problem with the current active test file version, users with higher permissions and / or administrative permission are authorized to make an older, obsolete test file version the “active” test file version. By reverting to an older, obsolete test file version in this way, testing can be made possible to continue at least to some extent while a new version of the test file is prepared and / or the problem with the previous “active” version of the test file is resolved.

[0015] Some examples of the present disclosure relate to a non-temporary computer-readable medium, which includes a first version of a file, a second version of a file, version control data indicating that the first version of the file is the active version of the file and the second version of the file is the obsolete version of the file, authorization data indicating that a first user is granted access or execution rights to the active version of the file but not permission to modify the active version of the file, and that the first user is not granted access, modification, or execution rights to the obsolete version of the file, and that a second user is granted access, modification, and execution rights to both the active version and the obsolete version of the file, and a machine-readable instruction, when executed by a processing circuit, causes the processing circuit to modify the version control data so that the second version of the file is again the active version of the file and the first version of the file is the obsolete version of the file, in response to a return request from a second user via a user interface.

[0016] In some examples, the file includes a test file that defines a test method, and the test method includes a method for performing a test on a sample subject using a material testing system, or a method for analyzing the test results of a test. In some examples, the material testing system includes a material testing machine, which comprises a testing machine sensor, a testing machine actuator, and a testing machine controller configured to control the testing machine actuator, and a test workstation that is communicatively connected to the material testing machine. In some examples, the version control data includes a version history indicating that a second version of the file was the active version of the file before it was modified to indicate that the second version of the file was an obsolete version of the file.

[0017] In some examples, the non - transitory computer - readable medium further includes machine - readable instructions that, when executed by the processing circuitry, cause the processing circuitry to determine, based on the authorization data, whether a review of the return request is required before the version management data is changed in response to receiving the return request. In some examples, the non - transitory computer - readable medium further includes machine - readable instructions that, when executed by the processing circuitry, cause the processing circuitry to change the version management data to indicate that the second version of the file is again the active version of the file and the first version of the file is the obsolete version of the file in response to a determination that a review is not required. In some examples, the non - transitory computer - readable medium further includes machine - readable instructions that, when executed by the processing circuitry, cause the processing circuitry to change the version management data to indicate that the second version of the file is pending review, notify a third user that the second version of the file is waiting for review by the third user, and change the version management data to indicate that the second version of the file is the active version of the file and the first version of the file is the obsolete version of the file in response to receiving a review approval input from the third user.

[0018] Some examples of the present disclosure are a central data repository communicating with a materials testing system, the central data repository having a first version of a test file, the test file defining a test method, the test method including a method for performing a test on a sample subject using the materials testing system, or a method for analyzing the test results of the test, a second version of the test file, version control data indicating that the first version of the test file is the active version of the test file and the second version of the test file is the obsolete version of the test file, and that a first user is granted access or execution rights to the active version of the test file but not permission to modify the active version of the test file, and that the first user is granted access or execution rights to the obsolete version of the test file The system comprises a central data repository that stores permission data indicating that the second user is not granted access, modification, or execution rights, the permission data further indicating that the second user is granted access, modification, and execution rights to the active and deprecated versions of the test file; a user interface configured to receive a return request from the second user; and a central server that has the central data repository or communicates with the central data repository, and includes a central server processing circuit unit configured to change version control data in response to a return request so that the second version of the test file is again the active version of the test file and the first version of the test file is a deprecated version of the test file.

[0019] In some examples, the central data repository communicates with a plurality of materials testing systems including the above materials testing system, and the test method defined by the test file is executable by each of two or more of the plurality of materials testing systems. In some examples, the materials testing system is a materials testing machine, comprising a tester sensor, a tester actuator, and a tester controller configured to control the tester actuator, and a test workstation communicably connected to the materials testing machine. In some examples, in response to the test workstation receiving an execution request from a first user or a second user to execute the active version of the test file, the test workstation communicates with the tester controller that controls the materials testing machine and is configured to implement the test method defined by the active version of the test file.

[0020] In some examples, the central server processing circuit is further configured to determine, based on the permission data, whether a review of the return request is required before the version management data is changed, in response to receiving the return request. In some examples, in response to determining that a review is not required, the central server processing circuit is configured to change the version management data to indicate that the second version of the file is again the active version of the file and the first version of the file is the obsolete version of the file. In some examples, in response to determining that a review is required, the central server processing circuit is configured to change the version management data to indicate that the second version of the file is on hold for review, notify a third user that the review hold version of the file is awaiting review by the third user, and, in response to receiving a review approval input from the third user, change the version management data to indicate that the second version of the file is the active version of the file and the first version of the file is the obsolete version of the file.

[0021] Some examples of this disclosure include a central data repository communicating with a materials testing system, which contains a first version of a test file, where the test file defines a test method, and the test method includes a method for performing a test on a sample subject using the materials testing system, or a method for analyzing the test results of the test; a second version of the test file; version control data indicating that the first version of the test file is the active version of the test file and the second version of the test file is an obsolete version of the test file; and permission data indicating that a first user is granted access or execution rights to the active version of the test file, but is not granted permission to modify the active version of the test file. The method includes storing permission data indicating that the first user is not granted access, modification, or execution rights to the deprecated version of the test file, and that the second user is granted access, modification, and execution rights to the active version and the deprecated version of the test file; receiving a return request from the second user via a user interface; and, in response to receiving the return request from the second user, modifying the version control data via the central server processing circuit of the central server to indicate that the second version of the test file is again the active version of the test file and the first version of the test file is the deprecated version of the test file.

[0022] In some examples, a central data repository communicates with multiple material testing systems, including the material testing system described above, and the test method defined by the test file can be performed by each of the two or more material testing systems among the multiple material testing systems. In some examples, the material testing system comprises a material testing machine, which includes a test machine sensor, a test machine actuator, and a test machine controller configured to control the test machine actuator, and a test workstation communicatively connected to the material testing machine. In some examples, the method further includes performing the test method defined by the active version of the test file via the material testing machine in response to receiving an execution request from a first or second user via a user interface to execute the active version of the test file.

[0023] In some examples, the method further includes, upon receiving a return request, determining, via a central server processing circuit, based on authorization data, whether a review of the return request is required before the version control data is modified; and, upon determining that a review is not required, modifying the version control data so that the second version of the file is again the active version of the file and the first version of the file is the obsolete version of the file. In some examples, the method further includes, upon receiving a return request, determining, via a central server processing circuit, based on authorization data, whether a review of the return request is required before the version control data is modified;, upon determining that a review is required, modifying the version control data via central server processing so that the second version of the file is pending review; notifying a third user via central server processing that the pending version of the file is awaiting review by the third user; and, upon receiving review approval input from the third user, modifying the version control data via central server processing so that the second version of the file is the active version of the file and the first version of the file is the obsolete version of the file.

[0024] Figure 1 shows an illustrative materials testing system 100. As shown, the materials testing system 100 includes a materials testing machine 102 (also known as a general-purpose testing machine) and a computing system 200 connected to the materials testing machine 102 via a cable 106. The connection is shown as physically connected, but in some examples it may be wireless instead of wired.

[0025] In the example shown in Figure 1, the material testing machine 102 includes a frame 112. In some examples, the frame 112 provides rigid structural support to other components of the material testing machine 102. As shown, the frame 112 includes an upper plate 114 and a bottom base 116 connected by two support columns 118. In some examples, the support columns 118 of the frame 112 may house guide rails and / or drive shafts 212 of the material testing machine 102 (see, for example, Figure 2).

[0026] In the example in Figure 1, the movable crosshead 120 extends between the support columns 118. In some examples, the movable crosshead 120 may be connected to a guide rail and / or drive shaft 212 housed in the support columns 118 and / or configured to move toward and away from the base 116 through the (e.g., motorized) operation of the drive shaft(s) 212. In the example in Figure 1, one movable crosshead 120 is shown, but in some examples, the material testing machine 102 may have multiple movable crossheads 120 and / or other movable members.

[0027] In the example in Figure 1, the fixture 122 is attached to the bottom base 116 of the frame 112 and to the movable crosshead 120. As shown, the lower fixture 122a includes a gripping portion 124a, and the upper fixture 122b includes both the test sensor 126 and the gripping portion 124b. In the example in Figure 1, one test sensor 126 and two gripping portions 124 are shown, but in some examples, the testing machine 102 may include more or fewer test sensors 126 and / or gripping portions 124.

[0028] In the example in Figure 1, the gripping section 124 holds the test subject 128. The test subject 128 is shown as a rope / wire (e.g., made of steel), but in some examples it may be made of some other type of material and / or component. The gripping sections 124a and / or 124b are shown as rope holders, but in some examples they may be configured as bolt holders, wedge grips, side-acting grips, manual grips, roller grips, capstan grips, and / or syringe holders, either as an alternative or in addition thereto. In some examples one or both of the gripping sections 124 may be replaced by a compression platen configured to compress the test subject 128.

[0029] In the example shown in Figure 1, the test sensor 126 is connected to the gripping portion 124 so that it can measure the force acting on the gripping portion 124 (and / or the subject 128, crosshead 120, etc.). In some examples, the test sensor 126 may be a load cell. In some examples, the test sensor 126 may be some other type of sensor.

[0030] In some examples, the material testing machine 102 may be configured for static mechanical testing. For example, the material testing machine 102 may be configured for compressive strength testing, tensile strength testing, shear strength testing, bending strength testing, deflection strength testing, tear strength testing, peel strength testing (e.g., strength of adhesive bonds), torsional strength testing, and / or any other compressive and / or tensile tests. In addition to or alternative to this, the material testing machine 102 may be configured to perform dynamic testing.

[0031] In some examples, the material testing machine 102 is configured to interface with a computing system 200 to carry out a test method. For example, the computing system 200 may communicate with the controller 214 of the material testing machine 102 (see, for example, Figure 2) to carry out a test method.

[0032] Figure 2 is a block diagram showing details of the calculation system 200 and additional details of the material testing machine 102. In the example in Figure 2, the exemplary material testing machine 102 includes one or more actuators 210 connected to one or more drive shafts 212. In some examples, the actuators 210 may be used to provide force to the drive shafts 212 and / or to guide the movement of the drive shafts 212. In some examples, the actuators 210 may include electric motors, pneumatic actuators, hydraulic actuators, piezoelectric actuators, repeaters, and / or switches.

[0033] The drive shaft 212 is further shown connected to the movable crosshead 120 such that the movement of the drive shaft(s) 212 via the actuator(s) 210 results in the movement of the movable crosshead 120. In the example of Figure 2, the term drive shaft 212 is used, but in some examples, the drive shaft 212 may be any other mechanical means that moves the movable crosshead 120 despite the guidance of the actuator(s) 210.

[0034] The exemplary material testing machine 102 further includes a controller 214 that electrically communicates with actuators 210(or actuators) 210. In some examples, the controller 214 may include a processing circuit and / or a memory circuit. In some examples, the controller 214 may be configured to control the material testing machine 102 based on one or more commands, control inputs, and / or test parameters. In some examples, the controller 214 may be configured to convert commands, control inputs, and / or test parameters (e.g., received from a computing system 200) into appropriate (e.g., electrical) signals that can be delivered to actuators 210(or actuators) 210, thereby controlling the operation of the material testing machine 102 (e.g., via actuators 210(or actuators) 210). For example, the controller 214 may provide one or more signals that instruct actuators 210(or actuators) 210 to increase or decrease the force applied by them.

[0035] In the example in Figure 2, the controller 214 further communicates electrically with the fixture 122 (e.g., the gripping unit 124 and the test sensor(s) 126). In some examples, the controller 214 may be configured to convert commands, control inputs, and / or test parameters (e.g., received from the computing system 200) into appropriate (e.g., electrical) signals that can be delivered to the gripping unit 124, thereby controlling the operation of the gripping unit 124 (e.g., gripping or releasing). In some examples, the controller 214 may be configured to convert commands, control inputs, and / or parameters (e.g., received from the computing system 200) into appropriate (e.g., electrical) signals that can be delivered to the sensor(s) 126, thereby controlling the operation of the sensor(s) 126. In some examples, the controller 214 may be configured to convert measurement data received from the sensor(s) 126 and / or to transmit the measurement data to the computing system 200.

[0036] The exemplary controller 214 further communicates electrically with the control panel 216 of the material testing machine 102. In some examples, the control panel 216 may include one or more input devices (e.g., buttons, switches, slides, knobs, microphones, dials, and / or other electromechanical input devices). In some examples, the control panel 216 may be used by an operator to directly control the material testing machine 102. In some examples, the controller 214 may be configured to control the material testing machine 102 by converting commands, control inputs, and / or test parameters received via the control panel 216 into appropriate (e.g., electrical) signals that can be delivered to the actuator(s) 210 and / or gripping(s) 124.

[0037] The controller 214 is also illustrated as communicating electrically with the communication interface 218b of the material testing machine 102. In some examples, the communication interface 218b includes a network interface. In some examples, the communication interface 218b includes hardware, firmware, and / or software for connecting the material testing machine 102 to a complementary workstation communication interface 218a of the computing system 200. In some examples, the controller 214 may receive information (e.g., commands) from the computing system 200 through the communication interface 218 and / or transmit information (e.g., measurement data from sensors 126) to the computing system 200 through the workstation communication interface 218.

[0038] In the example shown in Figure 2, the computing system 200 includes a test workstation 202 and a user interface (UI) 204 interconnected with each other. As shown, the UI 204 may include one or more input devices 206 configured to receive input from the user and one or more output devices 208 configured to provide output to the user.

[0039] In some examples, one or more input devices 206 may include one or more touchscreens, mice, keyboards, buttons, switches, slides, knobs, microphones, dials, and / or other input devices 206. In some examples, one or more output devices 208 may include one or more displays / touchscreens, speakers, lighting, haptic devices, and / or other output devices 208. In some examples, the output device(s) 208 (e.g., display screens) of the UI 204 may output one or more representations of a material testing process 250 configured to enable a user to set up and / or run a test method and / or analyze the test results of a test method. In some examples, the input device(s) 206 of the UI 204 may receive input from a user and send input data representing user input to the test workstation 202.

[0040] In the example in Figure 2, the exemplary test workstation 202 includes a workstation communication interface 218a. In some examples, one or more of the workstation communication interfaces 218a are network interfaces. In some examples, one or more of the workstation communication interfaces 218a include hardware, firmware, and / or software configured to facilitate communication between the workstation 202 and one or more external networks, servers, systems, and / or devices.

[0041] As shown, one workstation communication interface 218a communicates with the communication interface 218b of the material tester 102 via cable 106. As shown, the test workstation 202 further includes a workstation communication interface 218a that communicates with a network 220 (e.g., the Internet). In the example in Figure 2, the test workstation 202 communicates with a remote interface 230 via the network 220 and the workstation communication interface 218a. In some examples, the test workstation 202 may communicate with one or more other test systems, servers, data repositories, and / or other devices via the network and / or workstation communication interface(s) 218a. As shown, the workstation communication interface 218a is electrically connected to the common electrical bus 219 of the test workstation 202.

[0042] In some examples, the test workstation 202 may be a computing device. In the example in Figure 2, the test workstation 202 includes a workstation processing circuit 224 connected to a common electric bus 219. In some examples, the workstation processing circuit 224 may include one or more processors. In some examples, the workstation processing circuit 224 is configured to process information received from the UI 204, a data import device(s) 108, and / or a material tester 102.

[0043] In some examples, the workstation processing circuit 224 is configured to transmit commands and / or test parameters to the material testing machine 102 (for example, via a communication interface(s) 218a). In some examples, the workstation processing circuit 224 is configured to output information to the operator through the UI 204. In some examples, the workstation processing circuit 224 is configured to execute machine-readable instructions stored in the workstation memory circuit 226.

[0044] In the example in Figure 2, the test workstation 202 further includes a workstation memory circuit unit 226 connected to a common electric bus 219. As shown, the workstation memory circuit unit 226 includes a material testing process 250. In some examples, the material testing process 250 includes machine-readable instructions. In some examples, the workstation processing circuit unit 224 is configured to execute the machine-readable instructions of the material testing process 250 and communicate with the material testing machine 102 (e.g., the controller 214 of the material testing machine 102) to set up the test of the material sample 128, perform the test of the material sample 128, and / or analyze the test results of the test of the material sample 128 (e.g., according to the parameters of the test file 450).

[0045] In some examples, the test of the material subject 128 is carried out according to a specific test method (and / or the test results are analyzed). In some examples, the test method is defined (at least partially) by parameters in a test file 450 (see, for example, Figure 4). When used herein, test file 450 refers to a collection of data (e.g., stored data) representing one or more parameters (e.g., test, sample / subject, analysis, etc.) that define (at least partially) a test method.

[0046] In some examples, the test parameters may include the date the test is performed, test identification information (e.g., number, name, type, description, etc.), target start / end positions of gripping section(s) 124, target start / end positions of crosshead 120, target distance / direction moved by crosshead 120, target speed of crosshead 120, expected test results(s) (e.g., location / type of fracture, distance moved before fracture, force applied before fracture, post-test characteristics of the specimen, etc.), time(s) when(s) sensors(s) 126 should perform measurements(s), and / or other information relevant to the specific test method.

[0047] In some examples, the subject parameters may include the date on which subject 128 was manufactured / shipped / packaged, identification information of subject 128 (e.g., number, name, description, etc.), pre-test characteristics of subject 128 (e.g., actual size / dimensions, material type, weight, color, shape, coefficient, maximum tensile strength, etc.), and / or other information relevant to a particular subject 128. In some examples, the analysis parameters may include one or more algorithms that may be used to evaluate the results of the test method (and / or generate additional test results), one or more test result report formats, and / or one or more thresholds and / or threshold ranges (e.g., which can be used to make a ruling on the test result to determine whether subject 128 passed or failed the test).

[0048] In some cases, some or all of the subject parameters, test parameters, and / or analysis parameters are stored in (and / or specified by) the test file 450. In some cases, the subject parameters, test parameters, and / or analysis parameters in the test file 450 are used by the test workstation 202 when performing the material testing process 250, conducting tests on the material subject 128, and / or analyzing the test results of the tests on the material subject 128.

[0049] Figure 3 shows an example of a distributed materials testing system 300 having a central data repository 400 (see Figure 4) that stores multiple test files 450 that can be used by multiple materials testing systems 100. In the example in Figure 3, the central data repository 400 is shown as part of the server memory circuit section 304 of the central server 302. In some examples, the central data repository 400 may instead be separate from the central server 302, as shown by the dotted line in Figure 3.

[0050] In the example in Figure 3, some material testing systems 100 are also shown as being connected to (and / or communicating with) a central server 302 (and consequently, a central data repository 400). In particular, the material testing systems 100 are shown as being connected to (and / or communicating with) the central server 302 through the central server communication interface 308 and network 220 (and / or the communication interfaces (which may be multiple) 218 ​​of the test workstations 202). A certain number of communication interfaces 218 / 308 are shown in the examples in Figures 2 and 3, but this number is merely illustrative. In some examples, there may be more or fewer communication interfaces 218 / 308 present.

[0051] In some examples, the server communication interface(s) 308 enable and / or facilitate connection and / or communication with the network 220 and / or the material testing system 100 (via the workstation communication interface(s) 218). In some examples, one or more of the server communication interfaces 308 are network interfaces. In some examples, one or more of the server communication interfaces 308 include hardware, firmware, and / or software configured to facilitate communication between the central management server 302 and one or more external networks, systems, and / or devices (e.g., network 220 and / or the material testing system 100).

[0052] In the example shown in Figure 3, the server communication interface(s) 308 (which may be multiple) is connected to (and / or communicates with) the server processing circuit 306 of the central server 302. In some examples, the server processing circuit 306 may comprise one or more processors. In some examples, the server processing circuit 224 is configured to execute machine-readable instructions stored in the server memory circuit 304 and / or to query / access the central data repository 400.

[0053] Figure 4 shows an example of a central data repository 400. In the example in Figure 4, the central data repository 400 is shown as storing authorization data 402, version control data 404, and several different test files 450. Although not shown, in some examples the central data repository 400 also stores several other files and / or other types of files (e.g., document files, image files, test result files, etc.).

[0054] In some cases, storing a file (e.g., test file 450) in a central data repository 400 can be useful when there are several material testing systems 100 that need to use the file. In particular, test file 450 (and / or other files) may be used by any material testing system 100 that is connected to and / or communicates with the central data repository 400 when it is stored centrally. In addition, instead of each material testing system 100 having its own copy, a single copy of test file 450 may be stored. Storing a single central copy of test file 450 in the central data repository 400 saves memory space and also helps ensure that each material testing system 100 is using the same test file 450 (and thereby operating the same test method), which may be important for documentation and / or adherence to certain rules.

[0055] In the example in Figure 4, the central data repository 400 also stores different versions 499 of each test file 450. In some examples, each version 499 of a file shares certain features, characteristics, and / or attributes (e.g., file name) with each other version 499 of the same file. In some examples, the data containing the test file 450 (and / or other files), version(s) 499, and / or version control data 404 may indicate the identity and / or values ​​of the shared features, characteristics, and / or attributes of each version 499.

[0056] In some cases, each version 499 of test file 450 (and / or other files) differs from each other version 499 of test file 450 (and / or other files) in at least one respect. For example, if a new version 499 of test file 450 is created, or if an existing version 499 of test file 450 is modified, both the new / modified version 499 and the old / existing version 499 are retained and / or saved as different versions 499 (it is not the case that the old / existing version 499 is overwritten and / or deleted while only the new / modified version 499 is retained). In some cases, older versions 499 of test file 450 (and / or other files) may be marked as “obsolete” to avoid confusion with newer versions 499.

[0057] In some cases, there may be usefulness in maintaining and / or enabling access to older versions 499 of test file 450 (and / or other files). For example, if a problem occurs with a newer version 499 of test file 450 (e.g., an error, abnormal result, etc.), it may be useful to revert to an older version 499 of test file 450, which is known to be stable and / or reliable, while the problem with the newer version 499 is being resolved and / or while the newer version 499 is being prepared. In addition, comparing a newer version (or multiple version) 499 with an older version (or multiple version) 499 may be helpful in identifying changes that may be contributing to some problem.

[0058] While it may be useful to maintain previous versions 499 of some specific test files 450 (and / or other files), there may also be usefulness in ensuring that all (or at least most) users and / or material testing systems 100 use the same version 499 of test files 450 (and / or other files). For example, ensuring that the same version 499 of test file 450 is used to test specific material subjects 128 (and / or specific types of material subjects 128) may be important for documentation and / or compliance purposes, regardless of which user and / or material testing system 100 is performing the test. To ensure that the same version 499 of test file 450 is used, in some examples, the distributed material testing system 100 designates a specific version 499 of test file 450 (and / or other files) as the "active" version 499 (e.g., public version 499).

[0059] In some examples, version control data 404 stored by the central data repository 400 indicates which version 499 of a particular test file 450 (and / or other files) is the "active" version 499. In some examples, version control data 404 additionally or alternatively indicates which file version 499 is the "obsolete" version 499 (e.g., a previous "active" version 499). In some examples, version control data 404 additionally or alternatively indicates which file version 499 is the "draft" version 499 (e.g., still in the preparation / development stage).

[0060] In some cases, there may be several different “obsolete” and / or “draft” versions 499 of a particular test file 450 (and / or other files) simultaneously, but there can only be one “active” version 499 of the file at any given time. In some cases, most users and / or material testing systems 100 are only granted access and / or execution permissions for the “active” version 499 of test file 450 (and / or other files). In some cases, through this “active” version 499 mechanism, the distributed material testing system 100 ensures that most users and / or material testing systems 100 use the same version 499 of the same test file 450 (and / or other files) when performing tests (this may be important for documentation and / or compliance with certain specific rules).

[0061] In some cases, a select few users with higher-level permissions and / or administrative permissions are granted access, modification, and / or execution permissions to all different versions 499 of test file 450 (and / or other files). In some cases, users with higher-level permissions and / or administrative permissions are also granted permission to change which version 499 of the file is the "active" version 499. Thus, the distributed materials testing system 100 maintains a mechanism to change and / or revert the "active" version 499 of test file 450, which is used by most users, to a previous version 499 as needed (for example, if a newer version 499 begins to cause errors, malfunctions, abnormal results, etc.).

[0062] In the example in Figure 4, the central data repository 400 is also shown to store authorization data 402 (and / or authorization settings). In some examples, authorization data 402 indicates which users are granted access, modification, open, and / or execution permissions for which version 499 of which test file 450 (and / or other files). In some examples, authorization data 402 indicates which users are granted access, modification, open, and / or execution permissions for which version type (e.g., "active", "draft", "obsolete", etc.) of test file 450 (and / or other files).

[0063] For example, authorization data 402 may indicate that a user with basic authorization and / or lower-level authorization (e.g., a production line tester) is granted access, open, and / or execute permissions only for the "active" version 499 of test file 450 (and / or other files). Alternatively, authorization data 402 may indicate that a user with higher-level authorization and / or administrative authorization (e.g., an R&D tester, manager, administrator, etc.) is granted access, modify, open, and / or execute permissions for all versions 499 of test file 450 (and / or other files) stored in the central data repository 400 (and / or server memory circuit unit 304).

[0064] In the example in Figure 3, the server memory circuit 304 of the central server 302 is shown as being connected to (and / or communicating with) the server processing circuit 306. In some examples, the server processing circuit 306 may comprise one or more processors. In some examples, the server processing circuit 224 is configured to execute machine-readable instructions stored in the server memory circuit 304 and / or query the central data repository 400.

[0065] In the example in Figure 3, the server memory circuit 226 is shown as storing the file management process 500. Although the file management process 500 is shown as part of the server memory circuit 226 in the example in Figure 3, in some examples it may be implemented using discrete circuit sections (e.g., the server processing circuit 306). In some examples the file management process 500 is implemented using non-temporary machine-readable instructions stored in the server memory circuit 226 and / or executed by the server processing circuit 306.

[0066] In some examples, the file management process 500 is configured to restrict access, opening, and / or execution of the “active” version 499 of the test files 450 (and / or other files) stored in the central data repository 400 to users with basic / lower level privileges. In some examples, the file management process 500 is configured to allow users with higher level privileges and / or administrative privileges to access, open, modify, and / or execute any and / or all versions 499 of the test files 450 (and / or other files) stored in the central data repository 400. In some examples, the file management process 500 is configured to allow users with higher level privileges and / or administrative privileges to change which version 499 of the test files 450 (and / or other files) is the active version 499.

[0067] Figure 5 is a flowchart illustrating the operation of an example of the file management process 500. In some examples, before using and / or proceeding with the file management process 500, the user may be required to log in and / or be authenticated (e.g., using user credentials, biometrics, RFID / NFC / Bluetooth® / barcode device, UI204, remote interface 230, etc.). In some examples, different instances of the file management process 500 may be executed for different users. Hereinafter, for the sake of understanding and convenience, the file management process 500 may be described as performing some specific operations, but it should be understood that one or more of the above-described components of the distributed materials testing system 300 (e.g., server processing circuit unit 306, remote interface(s) 230, materials testing system(s) 100, etc.) may undertake these operations on behalf of (and / or in accordance with the instructions of the file management process 500).

[0068] In the example in Figure 5, the file management process 500 starts in block 502, where it determines the permission level of the logged-in user. In some examples, the permission level is determined based on permission data 402 stored in the central data repository 400. In some examples, in block 502, the file management process 500 further identifies the files and / or file versions 499 to which the user has been granted access, modification, open, and / or execute permissions, based on the permission level and / or permission data.

[0069] After block 502, the file management process 500 proceeds to block 504, in which block 504, the file management process 500 identifies files and / or file versions 499 stored in the central data repository 400 to which the user has been granted access, modification, open, and / or execute permissions. In some examples, the identification in block 504 is based on the determination in block 502. In some examples, the identification in block 504 is additionally or alternatively based on version control data 404.

[0070] In block 504, the file management process 500 additionally or alternatively provides one or more human-perceivable outputs (e.g., via UI 204 and / or remote interface 230) that display files and / or file versions 499 to which the user has been granted access, modification, open, and / or execute permissions. In some examples, the human-perceivable outputs may be visual outputs, audio outputs, tactile outputs, text outputs, graphic outputs, video outputs, and / or other outputs that are perceivable and / or interpretable by humans.

[0071] In some cases, one or more human-perceivable outputs of block 504 allow a user to select one or more of the identified files and / or file versions 499. In some cases, one or more human-perceivable outputs of block 504 allow a user to additionally or alternatively request access, modification, opening, and / or execution of the selected file version 499 (depending on permissions / permissions). In some cases, one or more human-perceivable outputs of block 504 allow a user with a higher level of permission and / or administrative level permission to request that a different file version 499 be made the "active" version 499.

[0072] Figures 6a to 6d show examples of graphical user interfaces (GUIs) 600 that can be output in block 504 (for example, via UI 204 and / or remote interface 230). Figure 6a shows an example of a first basic file system GUI 600a that can be output for users with basic permissions and / or lower-level permissions.

[0073] As illustrated, the first basic file system GUI 600a includes a file folder explorer window that allows the user to select different file folders. Next to the file folder explorer window is a file list window that enumerates the files in the selected file folder that are accessible to the user. Below the file folder explorer window and the file list window is a file attributes window that shows some specific attributes and / or characteristics (e.g., version 499) of the test file 450 selected via the file list window. In some examples, the attributes and / or characteristics (and / or other attributes and / or characteristics) shown in the file attributes window in Figure 6a may be stored in the central data repository 400 (e.g., as part of the file and / or file version 499 and / or associated with them).

[0074] The file attributes window in GUI600a also displays "Open" and "Execute" buttons that the user can choose to open and / or execute the "active" version 499 of the selected file. In particular, in the example in Figure 6a, only the active version 499 of the file is displayed in the file list window and file attributes window, and / or is selectable, openable, and / or executable. There are no available options that would allow the user to access, open, and / or execute different versions 499 of the selected test file 450 (for example, because the logged-in user only has basic permissions and / or lower-level permissions).

[0075] Figure 6b shows the Advanced File System GUI 600b, which can be output for users with higher permissions, higher-level permissions, and / or administrative permissions that allow users to view any / all file versions 499. The Advanced File System GUI 600b is similar to the Basic File System GUI 600a, except that it has a "View Versions" selectable button within the File Attributes window. In some examples, selecting the "View Versions" button allows the user to access, modify, open, and / or execute different versions 499 of the selected file.

[0076] Figure 6c shows the first file version GUI600c that can be output to the user after selecting "View Versions" in the advanced file system GUI600b. The first file version GUI600c is shown as listing five different versions 499 of the selected screw test file 450. Each version has its own dialog box. The first file version GUI600c further shows the type of each version 499 (e.g., active, draft, obsolete, etc.). The first file version GUI600c in Figure 6c is shown with an additional selectable plus ("+") sign next to each version 499. In some examples, this sign, when selected, results in the display of additional details about the selected version 499.

[0077] Figure 6d shows the Extended File Version GUI600d, which can be displayed after selecting the selectable plus ("+") sign next to the second version 499 of the selected screw test file 450 in the first file version GUI600c of Figure 6c. As illustrated, the Extended File Version GUI600d enumerates detailed characteristics and / or attributes related to the selected second version 499 within the Extended dialog box. In some examples, the characteristics and / or attributes (and / or other attributes and / or characteristics) shown in the Extended File Version GUI600d may be stored in the Central Data Repository 400 (for example, as part of the file and / or file version 499 and / or associated with them). While certain characteristics and / or attributes are shown in the example of Figure 6d, in some examples, additional or alternative characteristics and / or attributes may be displayed and / or stored.

[0078] In the examples in Figures 6c and 6d, the “Make Active” button is also shown within the dialog box for each version 499 of the selected screw test file 450 (excluding the currently active version 499). In some examples, selecting the “Make Active” button submits a request to change the selected version 499 to the active version 499 and / or change the currently active version 499 to the deprecated version 499.

[0079] In some cases, the requested changes may be made immediately after the request (e.g., if the user has administrative permissions). In some cases, the requested changes may only be made after review (e.g., if the user has higher-level permissions). In such cases, the status of the selected version 499 will be changed to under review until the request is approved by a different user (e.g., a user with administrative-level permissions). In some cases, whether the requested changes require review depends on the user's permissions (e.g., whether the permissions are higher-level or administrative).

[0080] In the examples in Figures 6c and 6d, the “Open” and “Run” buttons are also shown within the dialog boxes for each version 499. In some examples, selecting the “Open” button results in opening the selected file version 499, while selecting the “Run” button results in running the selected file version 499. In some examples, the “Run” button may only be displayed for executable files (for example, in Figures 6c and 6d and / or both Figures 6a and 6b).

[0081] In the example in Figure 5, after block 504, the file management process 500 proceeds to block 506, where it checks whether the user has selected to open and / or execute the file. If so, the file management process 500 proceeds to block 508, where the file version 499 is determined and / or that file version 499 is opened and / or executed. In some examples, the correct file version 499 to open / execute is determined based on the association between the selected button and the file, the file version 499, and / or the version type. In some examples, the correct file version to open / execute is additionally or alternatively determined based on version control data 404 and / or the version type of the selected file version 499.

[0082] In some examples, opening and / or executing file version 499 involves downloading the file to a specific material testing system 100 and / or test workstation. In some examples where the file is test file 450, opening and / or executing version 499 of test file 450 may involve executing a test method defined by the parameters of test file 450 via the material testing system 100 and / or material testing process 250. After block 508, the file management process 500 terminates (however, in some examples, the file management process 500 may not terminate and return to block 502).

[0083] In the example in Figure 5, if the user has not selected to open and / or run file version 499 in block 506, the file management process 500 then proceeds to block 510, where it checks whether the user has requested a change (for example, via the "Activate" buttons in GUI 600c and GUI 600d) to determine which file version 499 is the active file version 499. If no such request has been made, the file management process 500 returns to block 502. If such a request has been made, the file management process 500 proceeds to block 512.

[0084] In block 512, the file management process 500 determines whether a review of the requested change is required before commencing the change. In some examples, this determination is based on authorization data 402, the authorization level of the logged-in user, and / or the corresponding permissions. If the file management process 500 determines that a review is not required, it proceeds to block 520 (discussed below). If the file management process 500 determines that a review is required, it proceeds to block 514.

[0085] In block 514, the file management process 500 changes the version type of the selected file version 499 to one for review (for example, by changing version control data 404). In some examples, in block 514, the file management process 500 additionally or alternatively notifies one or more reviewers (for example, users with administrative level permissions) of a request to make the selected file version 499 the active file version 499.

[0086] Figure 6e shows the second file version GUI600e, which can be displayed in block 514. As shown, the status of the second version 499 of screw test file 450 has been changed from obsolete to under review. Meanwhile, the request to make the second version 499 of screw test file 450 the active version 499 has not yet been reviewed and / or approved, so the fourth version 499 of screw test file 450 remains the active version 499.

[0087] Figure 6f shows the reviewer GUI 600f as it may appear to the reviewer after block 514. As illustrated, the reviewer GUI 600f includes dialog boxes for both the current active file version 499 and the requested new active file version 499. Each dialog box is expandable to provide the reviewer with more information about each version 499, as described above. Each dialog box can be further opened and / or executed via the corresponding button within the dialog box for each version 499.

[0088] In the example reviewer GUI600f shown in Figure 6f, a selectable "Approve Request" button is displayed at the bottom of the reviewer GUI600f. In some examples, the selectable "Approve Request" button gives the reviewer the option to approve a request to activate the selected file version 499 and / or deactivate the currently active file version 499. A selectable "Deny Request" button is also shown. In some examples, the selectable "Deny Request" button gives the reviewer the option to deny a request to activate the selected file version 499 and / or deactivate the currently active file version 499.

[0089] A selectable "Keep as Draft" button is also shown. In some examples, the selectable "Keep as Draft" button gives the reviewer the option to make the selected file version 499 a draft (so that file version 499 can be modified and then resubmitted for review), and / or to keep the currently active file version 499 as is for the time being. Space for comments is also provided, as well as space to enter credentials and / or review selections to authenticate the reviewer's "signature".

[0090] In the example in Figure 5, the file management process 500 checks in block 516 whether the reviewer has completed the review. If not, the file management process 500 returns to block 514. If completed, the file management process 500 proceeds to block 518, where it checks whether the reviewer has approved or rejected the request. If the file management process 500 determines that the reviewer has rejected the request, the file management process 500 terminates (or returns to block 502). In the example where the reviewer chooses to keep the selected file version 499 as a draft, the file management process 500 modifies the version control data 404 to change the version type of the selected file version 499 to draft, and treats any other selection as rejected.

[0091] If the file management process 500 determines in block 518 that the reviewer has approved the request to make the selected file version 499 the active file version 499, the file management process 500 proceeds to block 520. In block 520, the file management process 500 modifies the version control data 404 to make the selected file version 499 the active file version 499 and / or changes the version type of the previously active file version 499 from active to obsolete. In some examples, the attributes and / or characteristics of file version 499 are also updated to reflect the date / time of their changes and / or any comments associated with them. In the example in Figure 5, the file management process 500 terminates after block 520 (however, in some examples, the file management process 500 may not terminate and return to block 502).

[0092] Figure 6g shows an example of a third file version GUI 600g that can be shown to users with higher-level permissions and / or administrative permissions after the second file version 499 has been approved as active. As shown, the dialog box for the second version 499 of the screw test file 450 indicates that the second version 499 is the active version at this time. On the other hand, the dialog box for the fourth version 499 of the screw test file indicates that the fourth version 499 is the deprecated version 499 at this time.

[0093] Figure 6h shows an example of the second basic file system GUI 600h, which can be shown to a user with basic permissions after the second file version 499 has been approved as active. As shown, both the file list window and the file attributes window indicate that the active version 499 of the screw test file 450 at this time is the second version 499 and not the fourth version 499. The "active" second version 499 of the screw test file 450 is opened / executed by the user's choice to open or run the screw test file 450 via the second basic file system GUI 600h.

[0094] The disclosed distributed materials testing system 300 and / or file management process 500 allows users with higher-level authorization and / or administrative authorization to change which version 499 of the centrally stored test file 450 (and / or other files) is the "active" version 499 of the test file 450 (and / or other files). In some cases, to ensure that most users and / or materials testing systems 100 use the same test file version 499 (which may be important for documentation and / or compliance purposes), users with lower-level authorization are restricted to using the "active" version 499 of the test file 450 for testing. On the other hand, if, for example, there is a problem with the current active test file version 499, users with higher-level authorization and / or administrative authorization are authorized to make an older, deprecated test file version 499 the "active" test file version 499. By reverting in this manner to the older, deprecated test file version 499, the test can be made continue to function at least to some extent while a new version 499 of test file 450 is prepared and / or while issues with the previous "active" version 499 of test file 450 are resolved.

[0095] The method and / or system can be implemented in hardware, software, and / or a combination of hardware and software. The method and / or system can be implemented centrally in at least one computing system, or in a distributed manner in which different elements are distributed across several interconnected computing or cloud systems. Any type of computing system or other device adapted to perform the method described herein is suitable. A typical combination of hardware and software may be a general-purpose computing system with a program or other code that, once loaded and executed, controls the computing system to perform the method described herein. Another typical embodiment may include an application-specific integrated circuit or chip. Some embodiments may include a non-temporary machine-readable (e.g., computer-readable) medium (e.g., flash drive, optical disk, magnetic storage disk, etc.) which stores one or more lines of machine-executable code, thereby causing a machine to perform a process such as that described herein.

[0096] While the Method and / or System has been described with reference to several specific embodiments, those skilled in the art will understand that various modifications and substitutions can be made without departing from the scope of the Method and / or System. In addition, many modifications can be made without departing from the scope of the Disclosure to adapt the teachings of the Disclosure to specific circumstances or materials. Thus, the Method and / or System is not limited to the specific embodiments disclosed, but is intended to include all embodiments that fall within the scope of the appended claims.

[0097] As used herein, "and / or" means any one or more items in the list linked by "and / or". For example, "x and / or y" means any element of the three-element set {(x), (y), (x,y)}. In other words, "x and / or y" means "one or both of x and y". As another example, "x, y and / or z" means any element of the seven-element set {(x), (y), (z), (x,y), (x,z), (y,z), (x,y,z)}. In other words, "x, y and / or z" means "one or more of x, y and z".

[0098] As used herein, the term “for example” commences a list of one or more non-limiting examples, cases, or illustrations.

[0099] As used herein, the terms "coupled," "coupled to," and "coupled with" mean a structural and / or electrical connection, whether it be attachment, bonding, joining, fastening, linking, and / or other fastening. As used herein, the term "attach" means to bond, connect, join, fasten, link, and / or otherwise fasten. As used herein, the term "connect" means to attach, bond, join, fasten, link, and / or otherwise fasten.

[0100] As used herein, the terms “circuit” and “circuit section” mean physical electronic components (i.e., hardware) and any software and / or firmware ("code") that can constitute the hardware, that the hardware can execute, and / or that can otherwise be associated with the hardware. As used herein, for example, a particular processor and memory may include a first “circuit” when executing one or more first lines of code, and a second “circuit” when executing one or more second lines of code. As used herein, whenever a circuit section includes hardware and / or code (if either is required) necessary to perform a certain function, the circuit section is “operable” and / or “configured” to perform that function, regardless of whether the performance of that function is disabled or not (e.g., by a user-configurable setting, factory trim, etc.).

[0101] As used herein, the term “processor” means a processing unit, device, program, circuit, component, system, and subsystem, whether implemented in hardware, in tangibly embodied software, or both, and whether programmable or not. As used herein, the term “processor” includes, but is not limited to, one or more computing devices, wired circuits, devices and systems for modifying signals, devices and machines for controlling systems, central processing units, programmable devices and systems, field-programmable gate arrays, application-specific integrated circuits, systems on a chip, systems comprising individual elements and / or circuits, state machines, virtual machines, data processors, processing equipment, and any combination thereof. A processor may be, for example, any type of general-purpose microprocessor or general-purpose microcontroller, a digital signal processing (DSP) processor, an application-specific integrated circuit (ASIC), a graphics processing unit (GPU), a reduced instruction set computer (RISC) processor with an advanced RISC machine (ARM) core, etc. A processor may be coupled to and / or integrated into a memory device.

[0102] As used herein, the terms “memory” and / or “memory device” mean computer hardware or circuitry that stores information for use by a processor and / or other digital device. Memory and / or memory devices may be any suitable type of computer memory or any other type of electronic storage medium, such as read-only memory (ROM), random access memory (RAM), cache memory, compact disk read-only memory (CDROM), electro-optical memory, magneto-optical memory, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), computer-readable media, etc. Examples of memory include non-temporary memory, non-temporary processor-readable media, non-temporary computer-readable media, non-volatile memory, dynamic RAM (DRAM), volatile memory, ferroelectric RAM (FRAM®), first-in, first-out (FIFO) memory, last-in, first-out (LIFO) memory, stack memory, non-volatile RAM (NVRAM), static RAM (SRAM), cache, buffer, semiconductor memory, magnetic memory, optical memory, flash memory, flash card, CompactFlash® card, memory card, secure digital memory card, microcard, minicard, expansion card, smart card, memory stick, multimedia card, picture card, flash storage, subscriber identification module (SIM) card, hard drive (HDD), solid state drive (SSD), etc. Memory can be configured to store code, instructions, applications, software, firmware and / or data, and can be external, internal, or both to the processor.

Claims

1. The first version of the file, The second version of the aforementioned file, Version control data indicating that the first version of the file is the active version of the file, and the second version of the file is the deprecated version of the file, Permission data, The first user is granted access or execution rights to the active version of the file, but is not granted modification rights to the active version of the file, and the first user is not granted access, modification, or execution rights to the deprecated version of the file. The second user has been granted access, modification, and execution permissions for the active version and the deprecated version of the file, The permission data, which indicates, When executed by the processing circuit, In response to receiving a return request from the second user via the user interface, the version control data is modified to indicate that the second version of the file is again the active version of the file, and the first version of the file is the deprecated version of the file. A machine-readable command that causes the processing circuit to perform the following: Non-temporary computer-readable media, including [specific examples of such media].

2. The non-temporary computer-readable medium according to claim 1, wherein the file includes a test file defining a test method, the test method including a method of performing a test on a sample subject using a material testing system, or a method of analyzing the test results of the test.

3. The aforementioned material testing system is A material testing machine comprising a testing machine sensor, a testing machine actuator, and a testing machine controller configured to control the testing machine actuator, A test workstation connected to the aforementioned material testing machine in a communication manner, A non-temporary computer-readable medium according to claim 2, comprising:

4. The non-temporary computer-readable medium according to claim 1, wherein the version control data includes a version history indicating that the second version of the file was the active version of the file before it was modified to indicate that the second version of the file was the deprecated version of the file.

5. When executed by the aforementioned processing circuit, Upon receiving the aforementioned revert request, determine, based on the permission data, whether a review of the revert request is required before the version control data is modified. The non-temporary computer-readable medium according to claim 1, further comprising a machine-readable instruction causing the processing circuit to perform the above.

6. When executed by the aforementioned processing circuit, In accordance with the determination that the aforementioned review is not required, the version control data is modified to indicate that the second version of the file is again the active version of the file, and the first version of the file is the deprecated version of the file. The non-temporary computer-readable medium according to claim 5, further comprising a machine-readable instruction causing the processing circuit to perform the above.

7. When executed by the aforementioned processing circuit, In accordance with the determination that the aforementioned review is necessary, Modify the version control data to indicate that the second version of the aforementioned file is pending review, To notify the third user that the second version of the aforementioned file is awaiting review by the third user, In response to receiving review approval input from the third user, the version control data is modified to indicate that the second version of the file is the active version of the file, and the first version of the file is the deprecated version of the file. The non-temporary computer-readable medium according to claim 5, further comprising a machine-readable instruction causing the processing circuit to perform the above.

8. A central data repository that communicates with a materials testing system, the central data repository is A first version of a test file, wherein the test file defines a test method, and the test method includes a method for performing a test on a sample subject using the material testing system, or a method for analyzing the test results of the test, The second version of the aforementioned test file, Version control data indicating that the first version of the test file is the active version of the test file, and the second version of the test file is the deprecated version of the test file, Permission data indicating that the first user is granted access or execution rights to the active version of the test file, but not permission to modify the active version of the test file, and that the first user is not granted access, modification, or execution rights to the deprecated version of the test file, Remember this, The permission data further indicates that the second user has been granted access, modification, and execution rights to the active version and the deprecated version of the test file, in a central data repository, A user interface configured to receive a return request from the second user, A central server that includes the aforementioned central data repository or communicates with the aforementioned central data repository, In response to the restoration request, the version control data is modified so that the second version of the test file is again the active version of the test file, and the first version of the test file is the deprecated version of the test file. A central server comprising a central server processing circuit section configured as follows, A system equipped with these features.

9. The system according to claim 8, wherein the central data repository communicates with a plurality of material testing systems, including the material testing system, and the test method defined by the test file can be implemented by each material testing system of two or more of the plurality of material testing systems.

10. The aforementioned material testing system is A material testing machine comprising a testing machine sensor, a testing machine actuator, and a testing machine controller configured to control the testing machine actuator, A test workstation connected to the aforementioned material testing machine in a communication manner, The system according to claim 8, comprising:

11. The system according to claim 11, wherein, in response to the user interface receiving an execution request from the first or second user to execute the active version of the test file, the test workstation is configured to communicate with the test machine controller that controls the material test machine and to perform the test method defined by the active version of the test file.

12. The system according to claim 1, wherein the central server processing circuit is further configured to determine, based on the authorization data, whether a review of the return request is required before the version control data is modified, in response to the receipt of the return request.

13. The system according to claim 12, wherein the central server processing circuit is configured to modify the version control data to indicate, upon determination that the review is not required, that the second version of the file is again the active version of the file and the first version of the file is the deprecated version of the file.

14. The central server processing circuit unit is In accordance with the determination that the aforementioned review is necessary, Modify the version control data to indicate that the second version of the aforementioned file is pending review, To notify the third user that the pending review version of the aforementioned file is awaiting review by the third user, In response to receiving review approval input from the third user, the version control data is modified to indicate that the second version of the file is the active version of the file, and the first version of the file is the deprecated version of the file. The system according to claim 12, configured to perform the following:

15. In the central data repository that communicates with the materials testing system, A first version of a test file, wherein the test file defines a test method, and the test method includes a method for performing a test on a sample subject using the material testing system, or a method for analyzing the test results of the test, The second version of the aforementioned test file, Version control data indicating that the first version of the test file is the active version of the test file, and the second version of the test file is the deprecated version of the test file, Permission data, The first user is granted access or execution rights to the active version of the test file, but is not granted modification rights to the active version of the test file, and the first user is not granted access, modification, or execution rights to the deprecated version of the test file. The second user has been granted access rights, modification rights, and execution rights to the active version and the deprecated version of the test file. The permission data that indicates this, and the storage of this data. Receiving a return request from the second user via the user interface, In response to receiving the recovery request from the second user, the version control data is modified via the central server processing circuit of the central server so that the second version of the test file is again the active version of the test file, and the first version of the test file is the deprecated version of the test file. Methods that include...

16. The method according to claim 15, wherein the central data repository communicates with a plurality of material testing systems, including the material testing system, and the test method defined by the test file can be implemented by each material testing system of two or more of the plurality of material testing systems.

17. The aforementioned material testing system is A material testing machine comprising a testing machine sensor, a testing machine actuator, and a testing machine controller configured to control the testing machine actuator, A test workstation connected to the aforementioned material testing machine in a communication manner, The method according to claim 15, comprising:

18. The method according to claim 17, further comprising: receiving an execution request from the first user or the second user via the user interface to execute the active version of the test file, and then performing the test method defined by the active version of the test file via the material testing machine.

19. Upon receiving the aforementioned recovery request, the central server processing circuit unit determines, based on the authorization data, whether a review of the recovery request is required before the version control data is modified. In accordance with the determination that the aforementioned review is not required, the version control data is modified to indicate that the second version of the file is again the active version of the file, and the first version of the file is the deprecated version of the file. The method according to claim 15, further comprising:

20. Upon receiving the aforementioned recovery request, the central server processing circuit unit determines, based on the authorization data, whether a review of the recovery request is required before the version control data is modified. In accordance with the determination that the aforementioned review is necessary, Modify the version control data via the central server processing to indicate that the second version of the aforementioned file is awaiting review, To notify the third user via the central server processing that the pending review version of the aforementioned file is awaiting review by the third user, In response to receiving review approval input from the third user, the version control data is modified via the central server processing to indicate that the second version of the file is the active version of the file and the first version of the file is the deprecated version of the file. The method according to claim 15, further comprising:

Images