Ask for a change
How it behaves or how the screen looks — in your own words, in any language. You see exactly what would change before anything is saved.
Set the system up
Five steps, in this order. Each one is used by the ones after it.
4 of 4 complete
Store reference screenshots
4 storedScreenshots of the real console. They are read twice — once while your answers below are interpreted, and again when the console is built — so they come first.
Describe how it behaves
ApprovedTrack classes, identification, what the operator can do, the engagement envelope. Everything downstream is built from this — without it the model invents a system, and the exercises look right without being right.
Build the simulated console
ApprovedGenerated from the screenshots and the behaviour profile together, so it shows the right columns and the right controls — not just the right colours.
Fly it yourself
Do this nextTargets, real controls, the clock running. This is where you find out whether the detection range gives an operator any warning and whether your console holds up with a live picture in it. Nothing is recorded — run it as often as you like.
Teach it a scenario
1 approvedTalk a real operational scenario through, review the record extracted from it, correct it, approve it.
Scenarios on this system
What a trainee can be put through. Each holds the dilemmas you decided belong in it.
A scenario is a situation an operator can be put in, and it holds however many dilemmas — hard choices — you decide belong in it. An exercise is one concrete run of a scenario, laid out with real tracks and timings when a trainee asks for it; those collect in Exercises.