Experiment Data Sheet.docx

CUI Once Complete

AFRL/RVBN Payload Intake Form (optional)

Submit UNCLASSIFIED / CUI completed sheet to:

DoD SAFE Request Link Via NEUTRON STAR Org Mailbox:

For form questions, please contact:

Email: afrl.rvkb.afrlneutronstardms@us.af.mil

DO NOT SUBMIT FORM TO ORG BOX

Experiment Requester Information

Name

Organization

Phone Number

Unclassified Email

Classified Email (e.g., SIPR)

Classified Mailing Address

Experiment Description

What is the name of experiment?

What are the estimated ranges for Technology Readiness Level (TRL) of the experiment, including before and after flight?

Is the experiment internally or externally mounted?

What is the experiment orientation? What are the axial and radial placement limitations?

What acceleration level will the payload be designed/qualified to? (In units of Gs.)

What temperature range will the payload be designed/qualified to?

Does the experiment contribute to drag on the vehicle?

If applicable, is data required to be stored and what are the estimated disk space needs?

What does the sponsoring organization hope to gain from this experiment? Please be comprehensive.

Size, Weight, and Power (SWaP)

Dimensions (if known) or Order of Magnitude (e.g., Matchbox, Breadbox, etc.).

Experiment Weight (or estimated WITH margin).

If power is required for this experiment, what is required power (Watts, Amps, Volts)?

Please select the requested power duty cycle below.

☐Whole Flight – Power must be applied for the entire flight, including during pre-flight countdown.

☐Phase of Flight – Power must be applied during a particular Phase of Flight. Conditions must be specified.

☐On Test Condition – Power must be applied when the flight is on the test condition. The amount of power-on time before and after the Test Condition must be specified.

☐Duration – Power must be applied for a specified duration at a specified flight time.

Explanation (if necessary):

Interface(s)

Briefly describe the logical and physical interfaces required to integrate the Test Article. At minimum, must address mounting, power, data collection, and experiment inputs.

List restrictions (e.g., no-spinning, aft facing, etc.).

Acceptance Testing

Please select all testing capabilities accessible to the payload team for acceptance testing.

☐ Vibration: Low-level sine sweep ☐ Vibration: Random vibe ☐ Vibration: Sine burst ☐ Thermal: Thermal vacuum ☐ Thermal: Thermal cycling (non-vacuum) ☐ EMI/EMC: Radiated emissions ☐ EMI/EMC: Conducted emissions ☐ EMI/EMC: Radiated susceptibility ☐ EMI/EMC: Conducted susceptibility ☐ Other: Shock ☐ Other: Acoustics ☐ Other: Radiation ☐ Other: Pressure ☐ Other: Antenna feed interface (if applicable) ☐ TPS (if applicable): Density ☐ TPS (if applicable): Char yield ☐ TPS (if applicable): Thermal conductivity ☐ TPS (if applicable): Tensile properties ☐ TPS (if applicable): Thermal expansion coefficient

System Hazards (if applicable)

List all hazardous systems, including electrical, chemical, pressure, etc. Hazardous system is one that, by the expenditure of its own energy or because it initiates a chain of events, may result in a catastrophic, critical, or marginal hazard.

System Hazards (cont.)

Please select the category of the hazard below.

☐Category 1 – A hazardous system whose consequence of inadvertent initiation cannot be physically contained. Reducing the likelihood of inadvertent initiation of a Category 1 system does not change the consequence of the associated hazard.

Examples: Rocket Motor, FTS Ordnance, hazardous chemical release systems, etc.

Please list hazards in this category below.

1.

2.

3.

4.

5.

6.

7.

8.

9.

10.

☐Category 2 – A hazardous system whose consequence of inadvertent initiation is physically contained when personnel would be exposed to the hazard. Containment of the hazard mitigates the safety consequence of the hazard effects to a negligible level.

Examples: Guillotine pyros for De-spin or Boom Release System, Stage Separation System with a mechanical restraint (i.e., V-Band Safety), etc.

Please list hazards in this category below.

1.

2.

3.

4.

5.

6.

7.

8.

9.

10.

Financial Information

Please select the funding status for payload development below.

☐Unfunded – An Unfunded Project is planned or proposed, but funding has not been committed.

☐Funded – A funded project has had funding committed but has not been awarded funding.

☐Executing – An executing project has had awarded funds and is expending them to complete its objectives.

☐Complete – The project has completed executing.

☐Terminated – The project has stopped without being completed.

Development Status

What is the proposed date for when experiment testing must be completed to support the project schedule?

What is the estimated date by when experiment hardware will be available to begin integration?

Development Status (cont.)

Please select the level of schedule flexibility for flight testing below.

☐High – Testing schedule can easily be adjusted with low risk for the project.

☐Medium – Testing schedule can be adjusted but with some risk to the project.

☐Low – Testing schedule cannot be adjusted without high risk to the project.

Please select confidence level that hardware will be completed by the estimated date.

☐High – Delivery on the specified date is as certain as possible. There are no cost, schedule or technical risk items likely to cause delay

☐Medium – Delivery on the specified date is at a moderate amount of risk. There are cost, schedule or technical risk items likely to cause delays, but they are being addressed by the project.

☐Low – The Test Article is likely to be delivered after the expected delivery date or the likelihood it has not been assessed. Cost, schedule, or technical risk items that are likely to cause delays have been identified and accepted or no assessment has been made.

Are there other projects that this experiment either depends upon or is depended upon?

If applicable, what scientific and/or technological potential do you envision for the proposed experiment?

Appendix A: TRL Reference

CUI

image1.png