SalientCharacteristics_DigitalTest (Rev 7_14_2025).pdf

The Air Force Research Lab, In-Space Propulsion Branch (RQRS) is looking to digitize the generation, approval, execution, and archiving test procedures. To accomplish this RQRS will purchase approximately 10 licenses for commercial off the shelf software (COTS) that meets the goals listed below. To increase collaboration, a cloud-based application is the preferred platform but is not required.

The overall goal is to increase the reliability while decrease the time required to generate & approve test procedures, provide real time tracking of test execution, provide a searchable archive of past tests, and link tests with their products (data, reports, …).

Additional background on the RQRS test environment:

• The generation of test procedures is done on standard Air Force computer systems.

• Tests are performed on isolated systems that do not have access to outside networks.

• The test procedures and associated test data will include Controlled Unclassified

Information (CUI) as well as export controlled and ITAR data.

• We also perform tests for commercial clients, as such those test procedures and data may be proprietary and must have further access controls.

• We expect low hundreds of tests per year.

As digital test procedure software is not a mature field, not all software may meet all our needs. To better prioritize our goals, we will mark them as core goals (CORE) which are necessary for minimal technical acceptability or extension goals (EXT) that will add benefit but are not necessary to be determined as minimally technically acceptable.

Specific goals:

• [EXT] Transfer test procedure between cloud and isolated systems

• [CORE] For cloud solutions, the software must be compliant with ITAR regulations and minimum of DoD IL4, IL5 preferred.

• [CORE] Assign restrictions to test templates and entire tests, to protect proprietary and sensitive data

• Ease the generation and approval of test procedures:

o [EXT] Convert existing paper-based test procedures and to digital form o [CORE] Build up test procedures from existing templates o [CORE] Save portions of a test procedure as a template for reuse o [EXT] Have version control on templates and full procedures o [EXT] Identify new and changed portions of a test procedure o [EXT] Allow multiple users to edit test procedures o [EXT] Allow for multiple people to approve steps in a test procedure o [EXT] Generate timeline for preapprovals, e.g. need safety approval 1 week prior to test

• Hardware and consumables:

o [EXT] Track hardware assembly and calibration instructions o [EXT] Maintain a list of available hardware and consumables o [EXT] Identify which hardware and consumables are scheduled to be used for test

• Running a Test:

o [CORE] Export test procedure as PDF o [CORE] Allow “red lines” through portions of the test o [CORE] Allow for the option to approve deviations from test procedure o [EXT] Link test procedure with data from test, e.g. LabView, to provide real time monitoring of test conditions

• Post Processing o [EXT] Run post processing scripts on collected data

• Archiving o [CORE] A searchable record of “as run” experiments approved changes o [EXT] Link data, post processing scripts, and reports to a test or tests o [EXT] Track which hardware was used on which tests o [EXT] Track test anomalies, failures, and observations