Built for the people whose decisions defend.
Four teams. Four pressures. One platform that survives all of them — the programme office picking the counter-UAS interceptor, the engineering team calibrating it, the operators rehearsing with it, and the researchers validating new capability against the golden baseline. Here is how each one uses UAVSimNet and what they walk out with.
Trade studies a scrutiny panel cannot dismantle.
Programme offices, capability-branch decision teams, and technical reviewers preparing an options analysis for a counter-UAS investment.
Build a trade-study scenario from validated presets. Sweep Monte Carlo across the threat classes you expect. Export a procurement-ready evidence pack. Every input carries its source. Every model touched carries its validity envelope. Every metric carries a regression comparison to the last blessed baseline.
A defensible options analysis and a transparent audit trail of every input that fed it. Related — the credibility framework.
Make the model match what the airframe actually did.
Systems-engineering teams with real telemetry (PX4 ULog, ArduPilot binary, MAVLink tlog, or CSV) who need to tune model parameters against field data.
Import the log (PX4 ULog, ArduPilot binary, MAVLink tlog, or CSV). Propose parameter deltas. Replay the engagement. Read the before/after side by side. Accepted deltas bump the model version. The audit trail records who signed off, on what evidence, and when.
An updated, version-bumped model in the registry — and a calibration session document any reviewer can re-open later. Related — the feature tour.
See the tails of the distribution before the range.
Operator cells preparing for a live-fire exercise or a contested-environment deployment.
Build mission scenarios that mirror the engagement envelope. Run thousands of Monte Carlo variants. Review the failure modes in a structured decision log — on the same console the analysts use. No separate training rig. No drift between training and production data.
A mission plan you have already seen survive the tails of the distribution, not just the nominal case. Related — verified intercept demonstrations.
A test bench someone else can re-run six months from now.
Defence-science teams and technology partners needing a reproducible counter-UAS test bench.
Register new interceptor or threat models. Publish their validity envelopes. Run the regression harness against the golden baseline. Ship the evidence as signed PDF and DOCX. Every run captures an immutable parameter-provenance snapshot a third party can re-validate independently.
A scientifically repeatable test record — not a folder of screenshots. Related — how the provenance chain works.
Decide which one is yours.
Every use case above maps onto concrete platform capabilities and a reviewer-signed evidence trail. Pick a thread and pull it.