Skip to content
45:00
← Mission Design Library
Problem 04 T&E RDT&E Medium Concept preview

Design the data pipeline for an operational test event

Collect sensor, operator and white-team data at a remote range so every measure in the test plan holds up afterward.

  • Disconnected ops
  • CUI marking
  • Human in the loop

IllustrativeA composite built from public information. It does not describe a specific OCEANS engagement, customer system or solicitation, and every figure on this page is an assumption for the exercise.

Practice mode

45:00

Starts a 45-minute clock on the prompt. Built for rehearsing an orals technical challenge.

01 · The prompt

“A two-week operational test runs at a remote range with patchy connectivity. Sensors, operator logs and white-team observers all generate data. Design the collection pipeline so every measure in the test plan can be computed afterward, the chain of custody holds up, and nothing depends on the network being up.”

02 · Ask these first

Each of these changes the design. Ask them before drawing a single box.

  1. Q1 Is the analysis plan locked before the event, and who signs it?
  2. Q2 Which clocks do we trust, and how do we sync them without a network?
  3. Q3 What counts as a valid trial, and who rules on the disputed ones?
  4. Q4 How do observer notes get structured enough to compute against?
  5. Q5 Where does the data go at the end, and under what marking?

Practice prompt

Your turn. Requirements, sizing, architecture, trade-offs.

Work it on a whiteboard. Our write-up for this one is still being drafted, so compare your structure against problem 01.

Write-up in progress

The prompt and the opening questions are live. Our full write-up is still being drafted.

You can practice it now. For the finished format, read problem 01.