Transferring test files in a distributed materials testing system

Abstract

This application describes an example of a distributed materials testing system that allows users to transfer files between groups (ie, teams) of users that use different data sets. In some examples, a distributed materials testing system uses a centralized data repository that is separated into separate data sets (and / or data partitions) so that a data set used by one team is not accessible by any other team. The ability for users to transfer files to other users in different teams provides a way for files to be shared and / or copied between team data partitions while still maintaining the integrity of the data partitions.

Description

[Technical Field]

[0001] [CROSS-REFERENCE TO RELATED APPLICATIONS] This application claims priority to and the benefit of U.S. Provisional Patent Application No. 63 / 687,390, filed August 27, 2024, entitled "TRANSFERRING TEST FILES IN DISTRIBUTED MATERIAL TESTING SYSTEMS," the entire contents of which are incorporated herein by reference.

[0002] This disclosure relates generally to distributed materials testing systems, and more particularly to transferring test files in distributed materials testing systems. [Background technology]

[0003] Materials testing machines are used to test various material specimens for attributes (e.g., tensile strength / compressive strength). The specific test method (also called test method) can vary from material specimen to material specimen. Test files can be used to store data related to the test method.

[0004] By comparing such a system with the present disclosure set forth in the remainder of this application with reference to the drawings, the limitations and disadvantages of the conventional and traditional approaches will become apparent to one skilled in the art. Summary of the Invention

[0005] The present disclosure relates to the transfer of test files in a distributed materials testing system substantially as illustrated in and / or described with respect to at least one of the figures and more fully set forth in the claims.

[0006] These and other advantages, aspects, and novel features of the present disclosure, as well as details of illustrated examples of the present disclosure, will be more fully understood from the following description and drawings. [Brief explanation of the drawings]

[0007] [Figure 1] FIG. 1 illustrates an exemplary materials testing system according to aspects of the present disclosure.

[0008] [Figure 2] FIG. 2 is a block diagram of the example materials testing system of FIG. 1 according to an embodiment of the present disclosure.

[0009] [Figure 3] FIG. 1 is a block diagram of an exemplary distributed materials testing system according to aspects of the present disclosure.

[0010] [Figure 4a] FIG. 4 illustrates an example of a central data repository of the example distributed materials testing system of FIG. 3 prior to file transfer, according to aspects of the present disclosure. [Figure 4b] FIG. 4 illustrates an example of a central data repository of the example distributed materials testing system of FIG. 3 after a file transfer, according to aspects of the present disclosure.

[0011] [Figure 5] 4 is a flowchart illustrating an exemplary file transfer process for the distributed materials testing system of FIG. 3 in accordance with an embodiment of the present disclosure.

[0012] [Figure 6a] 6 illustrates an example of a graphical user interface (GUI) that may be presented during the example file transfer process of FIG. 5, according to aspects of the present disclosure. [Figure 6b] 6 illustrates an example of a graphical user interface (GUI) that may be presented during the example file transfer process of FIG. 5, according to an aspect of the present disclosure. [Figure 6c] 6 illustrates an example of a graphical user interface (GUI) that may be presented during the example file transfer process of FIG. 5, according to an aspect of the present disclosure. [Figure 6d]6 illustrates an example of a graphical user interface (GUI) that may be presented during the example file transfer process of FIG. 5, according to an aspect of the present disclosure. [Figure 6e] 6 illustrates an example of a graphical user interface (GUI) that may be presented during the example file transfer process of FIG. 5, according to an aspect of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0013] The figures are not necessarily to scale. Where appropriate, the same or similar reference numbers are used in the figures to refer to similar or identical elements. For example, a reference number utilizing a letter (e.g., gripper 124a, gripper 124b) refers to the same reference number without the letter (e.g., gripper 124).

[0014] Disclosed herein are examples of distributed materials testing systems that allow users to send / transfer files between groups (i.e., teams) of users that use different data sets. In some examples, the distributed materials testing systems use a centralized data repository that is separated (logically and / or physically) into separate data sets (and / or data partitions) so that a data set used by one team cannot be accessed by any other team, but can be accessed by members of the same team on multiple materials testing systems. This can be useful, for example, when a particular team (e.g., research and development (R&D)) needs to modify and / or experiment with certain data / files without affecting data / files used by other teams (e.g., production and / or quality assurance teams).

[0015] However, teams may eventually desire to share at least some specific portions of their isolated data / files with other teams. For example, after an R&D team completes the development / update of a test file, the R&D team may want to distribute the completed test file to other teams (e.g., production and / or quality assurance) so that the other teams can perform tests using (and / or otherwise utilize) the completed file. The ability for users to send / forward files to other users in different teams provides a way for files to be shared and / or copied between team data partitions while still maintaining the integrity of the partitions.

[0016] Some examples of the present disclosure include a non-transitory computer-readable medium comprising: a file; and permission data indicating the file to which a particular user group has been granted access or execution permissions, the permission data indicating a first user group has been granted access or execution permissions for the file while a second user group has not been granted access or execution permissions for the file; and a program that, when executed by processing circuitry, creates a file copy of the file in response to receiving a file transfer request from a first user in the first user group to transfer the file to a second user in the second user group; and and updating the permission data to indicate that a first user group has been granted access to or execution of the file copy while a first user group has not been granted access to or execution of the file copy, or storing the file copy in a particular memory location of the non-transitory computer-readable medium such that the permission data indicates that a second user group has been granted access to the file stored in the particular memory location while the first user group has not been granted access to the file stored in the particular memory location; and providing notification of the file transfer to the second user via a user interface.

[0017] In some examples, the file is a test file defining a method for performing or analyzing a test on a sample specimen using the materials testing machine, and the file copy is a test file copy of the test file. In some examples, the machine-readable instructions, when executed by the processing circuitry, further cause the processing circuitry to control the materials testing machine to perform a test on the sample specimen according to the test method defined by the test file copy. In some examples, the materials testing machine is controlled to perform a test according to the test method defined by the test file copy in response to a second user selecting to execute the test file copy.

[0018] In some examples, the materials testing machine is controlled to perform a test according to a test method defined by the test file copy in response to a selection by a third user of the second user group to perform the test file copy. In some examples, the machine-readable instructions, when executed by the processing circuitry, further cause the processing circuitry to: determine whether the second user group has been granted access or execution permissions for the different file version of the file; in response to determining that the second user group has been granted access or execution permissions for the different file version, prompt the second user via a user interface to select whether to rename the file copy, change the location of the file copy, or overwrite the different file version with the file copy; and in response to receiving a selection via the user interface to overwrite the different file version with the file copy, save the file copy as a more recent version of the different file version. In some examples, the machine-readable instructions, when executed by the processing circuitry, further cause the processing circuitry to: identify a user group to which the first user belongs; and, in response to receiving a file transfer setup request to set up a file transfer from the first user, identify one or more files that the first user has been granted permission to transfer based on the permission data and the user group to which the first user belongs; and identify potential users to which the one or more files can be transferred.

[0019] Some examples of the present disclosure include a materials testing machine including a testing machine sensor, a testing machine actuator, and a testing machine controller configured to control the testing machine actuator; a central data repository that stores a plurality of test files, a particular test file among the plurality of test files that defines a method for performing a test on a sample specimen using the materials testing machine or a method for analyzing test results of the test, and authorization data indicating which test files among the plurality of test files a particular user group has been granted access to or execution privileges for, the authorization data indicating that a first user group has been granted access to or execution privileges for the particular test file, while a second user group has not been granted access to or execution privileges for the particular test file; and a central server that allows a first user of a first user group to access or execute the particular test file to a second user. and a central server comprising server processing circuitry configured to: in response to a request from the first user group to transfer the test file to a second user of the first user group, create a test file copy of the test file; update the authorization data to indicate that the second user group has been granted access to or execution of the test file copy while the first user group has not been granted access to or execution of the test file copy; or store the file copy in a particular memory location of a central data repository such that the authorization data indicates that the second user group has been granted access to the file stored in the particular memory location while the first user group has not been granted access to the file stored in the particular memory location; and provide notification of the transfer of the test file to the second user via the user interface.

[0020] In some examples, the materials testing system further includes a computing system in communication with the materials testing machine and the central server, the computing system including a test workstation and a user interface, the user interface configured to receive a request from a first user to transfer a test file to a second user, the test workstation configured to send one or more transfer command signals to the central server in response to the user interface receiving the request to transfer the test file. In some examples, the user interface is further configured to receive a test file copy execution command from the second user, the test file copy execution command representing a command to perform test file copying. In some examples, the computing system further includes computer processing circuitry configured to control the materials testing machine via communication with the testing machine controller to perform testing of the sample specimen according to a test method defined by the test file copy in response to the user interface receiving the test file copy execution command.

[0021] In some examples, the user interface is further configured to receive a perform test file copy command from a third user of the second user group, the perform test file copy command representing a command to perform a test file copy. In some examples, the server processing circuitry is further configured to: determine whether the second user group has been granted access or execution permissions for the different file version of the file; in response to determining that the second user group has been granted access or execution permissions for the different test file version, prompt the second user via the user interface to select whether to rename the file copy, change the location of the file copy, or overwrite the different file version with the file copy; and in response to receiving a selection via the user interface to overwrite the different test file version with the file copy, save the test file copy as a more recent version of the different test file version. In some examples, the server processing circuitry is further configured to: identify a user group to which the first user belongs; and, in response to receiving a file transfer setup request from the first user via the user interface, identify one or more test files to which the first user has been granted transfer authority based on the permission data and the user group to which the first user belongs; and identify potential users to which the one or more test files can be transferred.

[0022] Some examples of the present disclosure include a method for storing, in a central data repository, a plurality of test files; a particular test file among the plurality of test files, the particular test file defining a method for performing a test on a sample specimen using a materials testing machine or a method for analyzing test results of the test; and authorization data indicating which test files among the plurality of test files a particular user group has been granted access to or execution privileges for, the authorization data indicating that a first user group has been granted access to or execution privileges for the particular test file, while a second user group has not been granted access to or execution privileges for the particular test file; and a method for transferring the particular test file to a second user in a second user group, the method comprising: creating, via the server processing circuitry, a test file copy of the test file; updating, via the server processing circuitry, the authorization data to indicate that a second user group has been granted permission to access or execute the test file copy while the first user group has not been granted permission to access or execute the test file copy; or storing the file copy in a particular memory location of a central data repository, wherein the authorization data indicates that the second user group has been granted permission to access the file stored in the particular memory location while the first user group has not been granted permission to access the file stored in the particular memory location; and providing notification of the transfer of the test file to the second user via the first user interface or the second user interface.

[0023] In some examples, the method further includes controlling, via the testing workstation, the materials testing machine to perform testing on the sample specimen according to the test method defined by the test file copy. In some examples, the materials testing machine is controlled to perform testing according to the test method defined by the test file copy in response to a selection by a second user to execute the test file copy. In some examples, the materials testing machine is controlled to perform testing according to the test method defined by the test file copy in response to a selection by a third user of the second user group to execute the test file copy.

[0024] In some examples, the method further includes determining, via the server processing circuitry, whether a second user group has been granted access or execution permissions for a different file version of the file; prompting the second user, via the first user interface or the second user interface, to select whether to rename the file copy, change the location of the file copy, or overwrite the different file version with the file copy in response to determining that the second user group has been granted access or execution permissions for the different file version; and saving the test file copy as a more recent version of the different test file version in response to receiving a selection via the user interface to overwrite the different test file version with the test file copy. In some examples, the method further includes identifying, via the server processing circuitry, a user group to which the first user belongs; and, in response to receiving a file transfer setup request from the first user to set up a file transfer, identifying one or more test files that the first user has been granted transfer permissions to and identifying potential users to which the one or more files can be transferred based on the permission data and the user group to which the first user belongs.

[0025] 1 illustrates an example 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 through a cable 106. While the connection is illustrated as being physically connected, in some instances the connection may be wireless rather than wired.

[0026] 1, the materials testing machine 102 includes a frame 112. In some examples, the frame 112 provides rigid structural support to other components of the materials testing machine 102. As shown, the frame 112 includes a top plate 114 and a bottom base 116 connected by two posts 118. In some examples, the posts 118 of the frame 112 may house guide rails and / or a drive shaft 212 of the materials testing machine 102 (see, for example, FIG. 2).

[0027] 1, a movable crosshead 120 extends between the columns 118. In some examples, the movable crosshead 120 may be connected to guide rails and / or drive shafts 212 housed in the columns 118 and / or may be configured to move toward and / or away from the base 116 through actuation (e.g., motorized) of the drive shaft(s) 212. Although one movable crosshead 120 is shown in the example of FIG. 1, in some examples, the materials testing machine 102 may have multiple movable crossheads 120 and / or other moving members.

[0028] 1, fixtures 122 are attached to the bottom base 116 of the frame 112 and to the movable crosshead 120. As shown, the lower fixture 122a includes a gripper 124a, and the upper fixture 122b includes both a test sensor 126 and a gripper 124b. While one test sensor 126 and two grippers 124 are shown in the example of FIG. 1, in some examples, the test machine 102 may include more or fewer test sensors 126 and / or grippers 124.

[0029] In the example of FIG. 1 , grippers 124 hold test specimen 128. Test specimen 128 is shown as a (e.g., steel) rope / wire, but in some examples may be some other type of material and / or component. While grippers 124a and / or 124b are illustrated as rope holders, in some examples they may alternatively or additionally be configured as bolt holders, wedge-type grippers, side-acting grippers, manual grippers, roller grippers, capstan grippers, and / or syringe holders. In some examples, one or both of grippers 124 may be replaced by a compression platen configured to compress test specimen 128.

[0030] 1, the test sensor 126 is connected to the gripper 124 so as to measure the force acting on the gripper 124 (and / or the specimen 128, the 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.

[0031] In some examples, the materials testing machine 102 may be configured for static mechanical testing. For example, the materials testing machine 102 may be configured for compressive strength testing, tensile strength testing, shear strength testing, flexural strength testing, flexural strength testing, tear strength testing, peel strength testing (e.g., adhesive bond strength), torsional strength testing, and / or any other compressive and / or tensile testing. Additionally or alternatively, the materials testing machine 102 may be configured to perform dynamic testing.

[0032] In some examples, the materials testing machine 102 is configured to interface with a computing system 200 to implement the testing method. For example, the computing system 200 may communicate with a controller 214 (see, e.g., FIG. 2) of the materials testing machine 102 to implement the testing method.

[0033] 2 is a block diagram illustrating details of the computing system 200 and additional details of the materials testing machine 102. In the example of FIG. 2, the exemplary materials 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 and / or induce movement of the drive shafts 212. In some examples, the actuators 210 may include electric motors, pneumatic actuators, hydraulic actuators, piezoelectric actuators, relays, and / or switches.

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

[0035] The example materials testing machine 102 further includes a controller 214 in electrical communication with the actuator(s) 210. In some examples, the controller 214 may include processing circuitry and / or memory circuitry. In some examples, the controller 214 may be configured to control the materials 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 the computing system 200) into appropriate (e.g., electrical) signals that can be delivered to the actuator(s) 210, thereby controlling the operation of the materials testing machine 102 (e.g., via the actuator(s) 210). For example, the controller 214 may provide one or more signals instructing the actuator(s) 210 to provide more or less power, thereby increasing or decreasing the applied force.

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

[0037] The example controller 214 is also in electronic communication with a control panel 216 of the materials 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 materials testing machine 102. In some examples, the controller 214 may be configured to convert 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 gripper(s) 124 to control the materials testing machine 102.

[0038] The controller 214 is also shown in electronic communication with a network interface 218b of the materials testing machine 102. In some examples, the network interface 218b includes hardware, firmware, and / or software for connecting the materials testing machine 102 to a complementary workstation network 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 network interface 218 and / or send information (e.g., measurement data from the sensor(s) 126) to the computing system 200 through the workstation network interface 218.

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

[0040] In some examples, the 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, the one or more output devices 208 may include one or more displays / touchscreens, speakers, lights, tactile devices, and / or other output devices 208. In some examples, the output device(s) 208 (e.g., display screen) of the UI 204 may output one or more representations of a materials testing process 250 configured to enable a user to set up and / or execute a test method and / or analyze test results of the test method. In some examples, the input device(s) 206 of the UI 204 may receive input from a user and may send input data representing the user input to the testing workstation 202.

[0041] In the example of FIG. 2 , the example test workstation 202 includes a workstation network interface 218a. In some examples, the workstation network interface 218a includes hardware, firmware, and / or software configured to facilitate communication between the test workstation 202 and one or more external systems, networks, and / or devices. As shown, one workstation network interface 218a communicates with a network interface 218b of the materials testing machine 102 through cable 106. As shown, the test workstation 202 also includes a workstation network interface 218a that communicates with a network 220 (e.g., the Internet). In the example of FIG. 2 , the test workstation 202 communicates with a remote interface 230 through the network 220 and the workstation network interface 218a. In some examples, the test workstation 202 may communicate with one or more other test systems, servers, and / or other devices through the network and / or the workstation network interface(s) 218a. As shown, the workstation network interface 218 a is electrically connected to a common electrical bus 219 of the test workstation 202 .

[0042] In some examples, the test workstation may be a computing device. In the example of FIG. 2, the test workstation 202 includes workstation processing circuitry 224 connected to the common electrical bus 219. In some examples, the workstation processing circuitry 224 may include one or more processors. In some examples, the workstation processing circuitry 224 is configured to process information received from the UI 204, the data import device(s) 108, and / or the materials testing machine 102.

[0043] In some examples, the workstation processing circuitry 224 is configured to send commands and / or test parameters to the materials testing machine 102 (e.g., via the network interface(s) 218a). In some examples, the workstation processing circuitry 224 is configured to output information to an operator through the UI 204. In some examples, the workstation processing circuitry 224 is configured to execute machine-readable instructions stored in the workstation memory circuitry 226.

[0044] 2, the testing workstation 202 further includes a workstation memory circuitry 226 connected to the common electrical bus 219. As shown, the workstation memory circuitry 226 includes a materials testing process 250. In some examples, the materials testing process 250 includes machine-readable instructions. In some examples, the workstation processing circuitry 224 is configured to execute the machine-readable instructions of the materials testing process 250 to communicate with the materials testing machine 102 (e.g., the controller 214 of the materials testing machine 102) and perform tests on the materials specimens 128.

[0045] In some examples, testing of material specimens 128 is performed (and / or the test results analyzed) according to a particular test method. In some examples, the test method is defined by parameters in a test file 450 (see, e.g., FIGS. 4a and 4b). Test file 450, as used herein, refers to a collection of data (e.g., stored data) representing one or more parameters (e.g., test, sample / specimen, analysis, etc.) that define (at least in part) a test method.

[0046] For example, the test parameters in the test file 450 may include the date the test is to be performed, the test's identification (e.g., number, name, type, description, etc.), the target start / end positions of the gripper(s) 124, the target start / end positions of the crosshead 120, the target distance / direction traveled by the crosshead 120, the target speed of travel of the crosshead 120, the expected result(s) of the test (e.g., location / type of failure, distance traveled before failure, force applied before failure, post-test properties of the specimen, etc.), the time(s) at which the sensor(s) 126 should take the measurement(s), and / or other matters relevant to the particular test method.

[0047] As another example, the test subject parameters may include the date the test subject 128 was manufactured / shipped / packaged, the identification of the test subject 128 (e.g., number, name, description, etc.), the pre-test characteristics of the test subject 128 (e.g., actual size / dimensions, material type, weight, color, shape, modulus, ultimate tensile strength, etc.), and / or other information related to the particular test subject 128. As another example, 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., that may adjudicate the test results to determine whether the test subject 128 passed or failed the test). In some examples, the parameters represented by the test file 450 may be used to set up and / or run a test method and / or analyze subsequent test results of the test method.

[0048] 3 shows an example of a distributed materials testing system 300 having a central data repository 400 that stores multiple test files 450 (see FIGS. 4a and 4b) that may be used by multiple materials testing systems 100. In some examples, storing the test files 450 in the central data repository 400 can be useful when there are several materials testing systems 100 that need to use the same test file 450, as a single copy of the test file 450 can be stored rather than each materials testing system 100 having its own copy. Having a single, central copy of the test file 450 not only saves memory space, but also helps ensure that each materials testing system 100 is using the same test file 450 (and thereby performing the same test methodology), which may be important for documentation and / or compliance with certain regulations.

[0049] 3, the central data repository 400 is illustrated as part of the server memory circuitry 304 of the central server 302. Several materials testing systems 100 are illustrated as connected to (and / or in communication with) the central server 302 through the server communication interface 308 of the central server 302 and the network 220 (and / or the communication interface(s) 218 ​​of the test workstations 202). Through their connection to the central server 302, the materials testing systems 100 are connected to (and / or in communication with) the central data repository 400.

[0050] While a certain number of materials testing systems 100 are shown in the example of Figure 3, in some examples, more or fewer materials testing systems 100 may be connected to the central server 302 and / or central data repository 400. The central data repository 400 is shown in the example of Figure 3 as part of the server memory circuitry 304 of the central server 302, but in some examples, it may alternatively or additionally be separate from the central server 302. In such examples, the server network interface(s) 308 may further communicate with the central data repository 400.

[0051] 3, central server 302 further includes server processing circuitry 306. In some examples, server processing circuitry 306 may comprise one or more processors. In some examples, server processing circuitry 224 is configured to execute machine-readable instructions stored on server memory circuitry 304 and / or query central data repository 400.

[0052] 4a and 4b show an example of a central data repository 400. In some examples, the central data repository 400 may include one or more different data structures (e.g., a database, a file system, a lookup table, etc.).

[0053] 4a and 4b, the central data repository 400 is separated into several different data partitions 402, with data in one data partition 402 being isolated and / or separated (logically and / or physically) from data in another data partition 402. Data partitions 402 can be useful, for example, in situations where a particular group of users uses a particular set of data that is not relevant to other user groups.

[0054] For example, it may be prudent for all users of a particular production team (or other user group) to exclusively use empirically validated test file(s) 450 and / or test method(s) when testing products coming off the production line. Thus, team members of a particular production team may exclusively access data / files within the same data partition 402, and their ability to modify those data / files may be restricted (e.g., to the team leader). As another example, different production teams may test different products and / or have access to different types of materials testing machines 102. In such situations, different production teams may access different data partitions 402 (and / or different data / files) related to the particular products they test and / or the types of materials testing machine(s) 100 they use.

[0055] As another example, an R&D team may be responsible for research on new and / or existing products and / or test methods, and may consequently develop new test files (and / or update existing test files). On the other hand, the R&D team may want to create, modify, and / or otherwise experiment with certain data / files without affecting data / files used by other users (e.g., the production team). In such an example, the R&D team may access its own data partition 402, which is separate from the production data partition 402.

[0056] In the example of Figures 4a and 4b, the central data repository 400 includes three data partitions 402: an R&D data partition 402a, a first production team partition 402b, and a second production team partition 402c. Although three data partitions 402 are illustrated in the central data repository 400 of Figure 4, in some examples, the central data repository 400 may have more or fewer partitions 402. Two of the partitions 402 are labeled as being for two different production teams, while the third partition 402 is labeled for the R&D team; however, in some examples, the partitions 402 may be differently labeled and / or designated for use by different teams. While each partition 402 is illustrated as storing a particular test file 450, in some examples, the partitions 402 may additionally or alternatively store different test files 450 and / or other data / files (e.g., other than test files 450).

[0057] In the examples of FIGS. 4a and 4b, both the R&D data partition 402a and the second production team data partition 402c are illustrated as including multiple versions 499 of a test file 450. In some examples, the central data repository 400 may store different versions 499 of a test file 450 (and / or other files). For example, if a first version 499 of a file is changed and then saved, the central data repository 400 may save a second version 499 of the file with the changes rather than overwriting the first version 499 of the file. In some examples, this may allow a user to continue to access a previous version 499a of a test file 450. This may be useful for comparison with a newer version 499 (e.g., if the newer version 499 begins to cause errors, malfunctions, anomalous results, etc.). In some examples, each version 499 of a file may be associated with one or more timestamps and / or other data (e.g., the team / user that last modified / saved it, etc.).

[0058] 4a and 4b, the central data repository 400 further stores permission data 404 and team data 406. In some examples, the team data 406 indicates which users belong to which teams. In some examples, the permission data 404 indicates which teams are authorized to access, modify, and / or execute data / files in a particular data partition 402. In some examples, the permission data 404 may additionally or alternatively implement the data partitions 402, such as by indicating that files in a particular data partition 402 are accessible, editable, and / or executable only by specific user(s) / team(s) that have access to the particular data partition 402. In some examples, the data partitions 402 may alternatively or additionally be implemented by storing files of a particular data partition 402 in a memory location (and / or on a physical hard drive) separate from other data partitions 402.

[0059] In some examples, the permission data 404 may indicate which users are authorized to transfer files from one team to another and / or receive file transfers. In some examples, the distributed materials testing system 300 may allow certain users to transfer files from one team (and / or one team's data partition 402) to another team (and / or another team's data partition 402). This may be useful, for example, when an R&D team completes the development / update of a test file 450 and the R&D team wants to distribute the completed test file 450 to a production team(s) so that the production team(s) can perform tests using (and / or otherwise utilize) the completed test file 450. In some examples, being able to transfer files from one team to another may also be useful for transferring result data between production teams, to an R&D team, and / or to a third-party team for analysis.

[0060] In some examples, only certain users may be authorized to actually transfer files from one team to another and / or receive file transfers from other users. For example, team data 406 may identify a team leader for each team, and permission data 404 may specify that any team leader may be authorized to make and / or receive file transfers. As another example, permission data 404 may individually identify users authorized to make and / or receive file transfers. While only certain team members may be authorized to receive file transfers, and file transfers are made individually from one user to another, in some examples, once a file transfer is approved, the transferred file may be available to (and / or accessible by) all team members.

[0061] 3, server memory circuitry 304 stores file transfer process 500. While file transfer process 500 is illustrated as part of server memory circuitry 304 in the example of FIG. 3, in some examples it may be implemented using discrete circuitry (e.g., in server processing circuitry 306). In some examples, file transfer process 500 is implemented using non-transitory machine-readable instructions stored in server memory circuitry 304 and / or executed by server processing circuitry 306. In some examples, portions of file transfer process 500 may additionally or alternatively be stored in workstation memory circuitry 226 of one or more materials testing systems 100 and / or executed (and / or implemented) by workstation processing circuitry 224 of one or more materials testing systems 100.

[0062] In some examples, server processing circuitry 306 is configured to execute machine-readable instructions of file transfer process 500 to transfer files from one team to another. In some examples, file transfers may occur at the request of a particular team member. In some examples, a "transfer" of a file is performed by copying the file from one data partition 402 to another data partition 402 so that any team member of the receiving team can access the file after the transfer and any changes made by one team to the transferred file are invisible to another team (unless there is another transfer).

[0063] 5 is a flow diagram illustrating an example operation of file transfer process 500. In some examples, a user may be required to log in and / or be authenticated (e.g., using a user certificate, biometrics, RFID / NFC / Bluetooth / barcode device, etc.) before using and / or proceeding through file transfer process 500. For purposes of understanding and convenience, file transfer process 500 may be described below as performing certain operations, although one or more of the above-described components of distributed materials testing system 300 (e.g., server processing circuitry 306, remote interface(s) 230, materials testing system(s) 100, etc.) may undertake these operations on behalf of (and / or in accordance with) file transfer process 500.

[0064] In the example of FIG. 5, file transfer process 500 begins at block 502, where file transfer process 500 determines whether there is a file to transfer. In some examples, the determination at block 502 may be based on whether a file transfer request has been made. In some examples, the file transfer request may be made by a user, such as through appropriate input using UI 204 and / or remote interface 230. In some examples, only certain users may be authorized to make file transfer requests (e.g., as indicated by permission data 404). Block 502 is included in the example of FIG. 5 for purposes of understanding and completeness, but in some examples, it may actually occur prior to the start of file transfer process 500.

[0065] After the file transfer process 500 determines at block 502 that there is a file to transfer, the file transfer process 500 proceeds to block 504, where the file transfer process 500 identifies one or more different teams to which the file can be transferred. For example, a user may not be able to transfer a file to their own team or team members, but may be able to transfer the file to some other team in the distributed materials testing system 300. In some examples, the identifying operation at block 504 may involve an analysis of the team data 406, the permission data 404, and / or the user identification information (e.g., established at login). After the one or more different teams to which the file can be transferred are identified at block 504, the identified one or more different teams may be presented to the user via the UI 204 and / or the remote interface 230, etc.

[0066] 6a illustrates an example of a graphical user interface (GUI) 600a that may be presented to a user in block 504. As shown, GUI 600 includes a team drop-down dialog box that provides the user with the option to select a first production team or a second production team as the recipient for the file transfer. Notably, because the user is part of the R&D team, the user is not provided with the option to transfer the file to the R&D team. As shown, the user has selected Production Team 1 as the team recipient.

[0067] In the example of FIG. 5 , the file transfer process 500 receives a team selection at block 504 and then proceeds to block 506, where the file transfer process 500 identifies one or more different team members of the selected team to which the file can be transferred. In some examples, the identifying operation(s) at block 506 may involve analyzing the team data 406 and / or the permission data 404. For example, the permission data 404 may indicate that only certain members of a particular team (e.g., a team leader) may be authorized to receive file transfers, while other members of the team are not. Alternatively, or additionally, the permission data 404 may indicate that any member of a particular team is authorized to receive file transfers. After the one or more different team members to which the file can be transferred are identified at block 506, the identified one or more different team members may be presented to the user via the UI 204 and / or the remote interface 230, etc.

[0068] 6b illustrates an example GUI 600b in which a team has been selected and authorized team member recipients for the team have been identified. As shown, the authorized team member recipients for the selected team are presented to the user via a team member drop-down dialog, and the user has selected John Doe to receive the file transfer.

[0069] 5, the file transfer process 500 receives a team member selection at block 506. In some examples, multiple team members and / or groups of team members may be selected at block 506. For example, a user may select to send to all team leaders of a selected team.

[0070] After selecting the team member(s) at block 506, the file transfer process 500 then proceeds to block 508, where the file transfer process 500 identifies one or more files (and / or one or more file versions 499) that the user is authorized to transfer. In some examples, the identifying operation(s) at block 508 may involve analyzing the team data 406 and / or the permission data 404. For example, the permission data 404 may indicate that the user (and / or the user's team) can transfer any file (and / or file version 499) in the data partition(s) 402 to which they are authorized to access. Alternatively, the permission data 404 may indicate that only certain files (and / or file versions 499) may be transferable (e.g., as indicated by the permission data 402) even in the data partition(s) 402 to which they are authorized to access. After one or more different files (and / or file versions 499) available for transfer are identified in block 508, those files (and / or file versions 499) may be presented to the user via UI 204 and / or remote interface 230, etc.

[0071] 6c shows an example GUI 600c in which a team and team members have been selected. As shown, two test files 450 have also been selected for transfer. Specifically, a bolt test file 450a and a screw test file 450b have been selected for transfer. The file paths for both test files 450 are shown next to the file folder icons.

[0072] In some examples, the file path for the file to be transferred may be entered manually. In some examples, the file path may be filled in automatically by the file transfer process 500, such as upon selection of the file via a file explorer window (not shown). In some examples, the file explorer window may be opened via selection of a file folder icon next to the file path. The file explorer window may show the files available for transfer and may allow the user to navigate and select one or more of the available files.

[0073] In the example of FIG. 6c, the GUI 600c also indicates which version 499 of each test file 450 has been selected for transfer. More specifically, the third version 499c of the bolt test file 450a and the first version 499a of the screw test file 450b have been selected for transfer. In the example of FIG. 6c, a clock icon is shown next to the selected version number. Also shown is a file version drop-down dialog listing the versions 499 available for selection for the bolt test file 450a. In some examples, the file version drop-down dialog may display a list of available versions 499 in response to a user selection of the clock icon.

[0074] 5, once the team, team members, and files are selected (and any messages added), the file transfer process 500 proceeds to block 510, where the file transfer process 500 determines whether the selected file(s) should be transferred to the selected team members. In some examples, the determination at block 510 may involve determining whether a transfer signal has been received from the UI 204 and / or the remote interface 230, such as may occur after a user selects a "Send" button in the GUI 600c. If the file transfer process 500 determines at block 510 that the selected file(s) should be transferred, the file transfer process 500 proceeds to block 512.

[0075] 6d shows an example of a GUI 600d after a user selects to send the test file 450 in block 510. As shown, the GUI 600 displays a message indicating that the test file 450 is being sent. In some examples, the GUI 600d may close after displaying this message. In some examples, after the file transfer process 500 proceeds from block 510 to block 512, the file transfer process 500 may appear to be finished from the sending user's perspective.

[0076] In some examples, the recipient user is notified that someone has sent one or more files at block 510. Then, at block 512, the file transfer process 500 determines whether there is an indication from the recipient that the file transfer was accepted or rejected by the recipient. If the file is accepted, the file transfer process 500 copies the transferred file from the sender's data partition 402 to the recipient's data partition 402 at block 514. To the extent that the file already exists in the recipient's data partition 402, the file transfer process 500 may append the sent file as a new version 499 of the existing file. If the file is rejected by the recipient user, the file transfer process 500 repeats blocks 512-516 for each additional file or ends if there are no more files.

[0077] 6e shows an example of a GUI 600e from the perspective of a recipient user at block 512. As shown, the recipient user is presented with an inbox showing a chronological list of sent files along with information about the sender and any attached messages. GUI 600e further shows that the inbox entry for vault test file 450a has been selected.

[0078] The example of Figure 6e also shows a file review window 602 with information entered for the selected inbox entry. For example, the file review window 602 indicates the file path where the transferred test file 450 will be stored (e.g., by selecting "Save") if the transferred test file 450 is accepted. In the example of Figure 6e, the file review window 602 also shows a warning that an identical version of the test file 450 already exists at the specified file path. The recipient user is given the option to either change the file path or "overwrite" the existing test file 450 by appending the transferred test file 450 as a new version 499 of the existing test file 450.

[0079] 4b illustrates an example of the central data repository 400 after a recipient user has selected to “overwrite” an existing test file 450 by appending the transferred test file 450 as a new version 499 of the existing test file 450. As shown, the first production team data partition 402b now includes a second version 499b of the bolt test file 450a and a first version 499a of the screw test file 450b. Note that such test file 450 and / or version 499 did not previously exist (e.g., in the example of FIG. 4a). Once these test files are available in the first production team data partition 402b, any team member of the first production team may be able to access, edit, and / or run the test file 450.

[0080] The disclosed distributed materials testing system 300 and file transfer process 500 allows users to send / transfer files between groups of users (i.e., teams) that use different data partitions 402. The ability for users to transfer files to other users on different teams provides a way for files to be shared and / or copied between team data partitions 402 while still maintaining the integrity of the data partitions 402. This can be useful, for example, when a particular team (e.g., an R&D team) completes the development and / or update of a test file 450 and wants to allow another team (e.g., a production team) to utilize the completed test file 450. Once the test file is transferred, any team member on the recipient team can use the transferred test file 450 to conduct tests via the materials testing system 100.

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

[0082] While the present method and / or system has been described with reference to certain specific embodiments, those skilled in the art will recognize that various modifications can be made and equivalents can be substituted without departing from the scope of the present method and / or system. In addition, many modifications can be made to adapt a particular situation or material to the teachings of the disclosure without departing from the scope of the disclosure. Therefore, the present method and / or system is not limited to the particular embodiments disclosed, but it is intended that the present method and / or system include all embodiments falling within the scope of the appended claims.

[0083] As used herein, "and / or" means any one or more of the items in the list connected by "and / or." As an 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."

[0084] As used herein, the term "for example" begins a list of one or more non-limiting examples, instances, or illustrations.

[0085] As used herein, the terms "coupled," "coupled to," and "coupled with" mean a structural and / or electrical connection, whether attached, adhered, connected, joined, fastened, coupled, and / or otherwise secured. As used herein, the term "attach" means attached, adhered, connected, joined, fastened, coupled, and / or otherwise secured. As used herein, the term "connect" means attached, adhered, connected, joined, fastened, coupled, and / or otherwise secured.

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

[0087] As used herein, control circuitry can include digital and / or analog circuitry, discrete and / or integrated circuitry, microprocessors, DSPs, etc., software, hardware, and / or firmware located on one or more boards that form part or all of a controller and / or are used to control the welding process and / or equipment such as a power supply or wire feeder.

[0088] As used herein, the term "processor" refers to processing units, devices, programs, circuits, components, systems, and subsystems, whether implemented in hardware, 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, hardwired circuits, devices and systems that modify signals, devices and machines for controlling systems, central processing units, programmable devices and systems, field programmable gate arrays, application specific integrated circuits, systems-on-chips, systems comprising discrete elements and / or circuits, state machines, virtual machines, data processors, processing facilities, and any combination of the above. 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.

[0089] As used herein, the terms "memory" and / or "memory device" refer to computer hardware or circuitry that stores information for use by a processor and / or other digital device. The memory and / or memory device can 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 disc 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 medium, etc. Memory may include, for example, non-transitory memory, non-transitory processor-readable medium, non-transitory computer-readable medium, non-volatile memory, dynamic RAM (DRAM), volatile memory, ferroelectric RAM (FRAM®), first-in-first-out (FIFO) memory, last-in-first-out (LIFO) memory, stacked 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, micro card, mini card, expansion card, smart card, memory stick, multimedia card, picture card, flash storage, subscriber identity module (SIM) card, hard drive (HDD), solid state drive (SSD), etc. Memory may be configured to store code, instructions, applications, software, firmware, and / or data and may be external, internal, or both to the processor.

Claims

1. A non-transitory computer-readable medium, comprising: Files and permission data indicating files to which particular user groups have been granted access or execution permissions, the permission data indicating that a first user group has been granted access or execution permissions to the files, while a second user group has not been granted access or execution permissions to the files; When executed by the processing circuitry: in response to receiving a file transfer request from a first user in the first user group to transfer the file to a second user in the second user group; making a file copy of said file; updating the permission data to indicate that the second user group has been granted permission to access or execute the file copy, while the first user group has not been granted permission to access or execute the file copy, or storing the file copy in a specific memory location on the non-transitory computer-readable medium, such that the permission data indicates that the second user group has been granted permission to access the file stored in the specific memory location, while the first user group has not been granted permission to access the file stored in the specific memory location; providing notification of the transfer of the file to the second user via a user interface; machine-readable instructions that cause the processing circuitry to:

1. A non-transitory computer-readable medium comprising:

2. 10. The non-transitory computer-readable medium of claim 1, wherein the file is a test file that defines how to perform or analyze a test on a sample specimen using a materials testing machine, and the file copy is a test file copy of the test file.

3. 3. The non-transitory computer-readable medium of claim 2, wherein the machine-readable instructions, when executed by the processing circuitry, further cause the processing circuitry to control the materials testing machine to perform the test on the sample specimen according to the test method defined by the test file copy.

4. 4. The non-transitory computer-readable medium of claim 3, wherein the materials testing machine is controlled to perform the test according to the test method defined by the test file copy in response to a selection by the second user to execute the test file copy.

5. 4. The non-transitory computer-readable medium of claim 3, wherein the materials testing machine is controlled to perform the test according to the test method defined by the test file copy in response to a selection by a third user of the second user group to execute the test file copy.

6. The machine-readable instructions, when executed by the processing circuitry, determining whether the second user group has been granted access or execution rights to a different file version of the file; prompting the second user via the user interface to select whether to rename the file copy, change the location of the file copy, or overwrite the different file version with the file copy in response to determining that the second user group has been granted access or execution permissions for the different file version; In response to receiving a selection via the user interface to overwrite the different file version with the file copy, saving the file copy as a more recent version of the different file version; The non-transitory computer-readable medium of claim 1 , further causing the processing circuitry to perform:

7. The machine-readable instructions, when executed by the processing circuitry, Identifying a user group to which the first user belongs; In response to receiving a file transfer setup request from the first user to set up a file transfer, Identifying one or more files that the first user is authorized to transfer based on the permission data and the user group to which the first user belongs; identifying potential users to whom the one or more files can be transferred; The non-transitory computer-readable medium of claim 1 , further causing the processing circuitry to perform:

8. a materials testing machine comprising a testing machine sensor, a testing machine actuator, and a testing machine controller configured to control the testing machine actuator; a central data repository, Multiple test files, a specific test file from the plurality of test files that defines a method for performing a test on a sample specimen using the materials testing machine or a method for analyzing test results from the test; authorization data indicating which test files of the plurality of test files a particular user group is authorized to access or execute, the authorization data indicating that a first user group is authorized to access or execute the particular test file, while a second user group is not authorized to access or execute the particular test file; a central data repository storing the a central server, In response to a first user in the first user group requesting that the particular test file be transferred to a second user in the second user group, creating a test file copy of said test file; updating the permission data to indicate that the second user group has been granted permission to access or execute the test file copy, while the first user group has not been granted permission to access or execute the test file copy, or storing the file copy in a specific memory location in the central data repository, such that the permission data indicates that the second user group has been granted permission to access the file stored in the specific memory location, while the first user group has not been granted permission to access the file stored in the specific memory location; providing notification of the transfer of the test file to the second user via a user interface; a central server comprising server processing circuitry configured to: A materials testing system comprising:

9. a computing system in communication with the materials testing machine and the central server; 9. The materials testing system of claim 8, wherein the computing system comprises a test workstation and the user interface, the user interface configured to receive a request from the first user to transfer the test file to the second user, and the test workstation configured to send one or more transfer command signals to the central server in response to the user interface receiving the request to transfer the test file.

10. 10. The materials testing system of claim 9, wherein the user interface is further configured to receive a test file copy execution command from the second user, the test file copy execution command representing a command to execute the test file copy.

11. the computing system further comprising computer processing circuitry; The computer processing circuitry includes: responsive to the user interface receiving the execute test file copy command, controlling the materials testing machine via communication with the testing machine controller to perform the test on the sample specimen according to the test method defined by the test file copy; The materials testing system of claim 10 configured to:

12. 10. The materials testing system of claim 9, wherein the user interface is further configured to receive a test file copy execution command from a third user of the second user group, the test file copy execution command representing a command to execute the test file copy.

13. The server processing circuit unit determining whether the second user group has been granted access or execution rights to a different file version of the file; prompting the second user via the user interface to select whether to rename the file copy, change the location of the file copy, or overwrite the different file version with the file copy in response to determining that the second user group has been granted access or execution privileges for the different file version; saving the test file copy as a more recent version of the different test file version in response to receiving a selection via the user interface to overwrite the different test file version with the file copy; 10. The materials testing system of claim 8, further configured to:

14. The server processing circuit unit Identifying a user group to which the first user belongs; in response to receiving a file transfer setup request from the first user via the user interface; Identifying one or more test files that the first user is authorized to transfer based on the authorization data and the user group to which the first user belongs; identifying potential users to whom the one or more test files can be transferred; 10. The materials testing system of claim 8, further configured to:

15. In a central data repository, Multiple test files, a specific test file from the plurality of test files that defines a method for performing a test on a sample specimen using the materials testing machine or a method for analyzing test results from the test; authorization data indicating which test files of the plurality of test files a particular user group is authorized to access or execute, the authorization data indicating that a first user group is authorized to access or execute the particular test file, while a second user group is not authorized to access or execute the particular test file; Remembering the in response to a first user in the first user group requesting, via a first user interface, that the particular test file be transferred to a second user in the second user group; creating a test file copy of said test file via server processing circuitry of a central server; updating, via the server processing circuitry, the permission data to indicate that the second user group has been granted permission to access or execute the test file copy, while the first user group has not been granted permission to access or execute the test file copy, or storing the file copy in a specific memory location in the central data repository, such that the permission data indicates that the second user group has been granted permission to access the file stored in the specific memory location, while the first user group has not been granted permission to access the file stored in the specific memory location; providing notification of the transfer of the test file to the second user via the first user interface or a second user interface; A method comprising:

16. 16. The method of claim 15, further comprising controlling, via a test workstation, the materials testing machine to perform the test on the sample specimen according to the test method defined by the test file copy.

17. 17. The method of claim 16, wherein the materials testing machine is controlled to perform the test in accordance with the test method defined by the test file copy in response to a selection by the second user to execute the test file copy.

18. 17. The method of claim 16, wherein the materials testing machine is controlled to perform the test according to the test method defined by the test file copy in response to a selection by a third user of the second user group to execute the test file copy.

19. determining, via the server processing circuitry, whether the second user group has been granted access or execution rights to a different file version of the file; prompting the second user via the first user interface or the second user interface to select whether to rename the file copy, change the location of the file copy, or overwrite the different file version with the file copy in response to determining that the second user group has been granted access or execution permissions for the different file version; In response to receiving a selection via the user interface to overwrite the different test file version with the test file copy, saving the test file copy as a more recent version of the different test file version; 16. The method of claim 15, further comprising:

20. Identifying, via the server processing circuitry, a user group to which the first user belongs; In response to receiving a file transfer setup request from the first user to set up a file transfer, Identifying one or more test files that the first user is authorized to transfer based on the authorization data and the user group to which the first user belongs; identifying potential users to whom the one or more files can be transferred; 16. The method of claim 15, further comprising:

Images