Nellis Air Force Base Renews UNIFY.C2 Contract Following Successful Year-Long Counter-UAS Evaluation

The most consequential counter-UAS decision at Nellis Air Force Base this year was not which drone-detection radar or jammer to buy. It was the decision to renew a command-and-control contract that deliberately refuses to privilege any single vendor's hardware. That distinction matters more than the renewal itself. After a year of operational evaluation, the Air Force has effectively certified that a unified common operating picture built on vendor-neutral sensor integration is not a science project but a fieldable capability. The renewal is the service putting money behind that judgment.

The mechanics here are worth unpacking, because they explain why this is harder than it sounds. Counter-UAS installations at a base like Nellis accumulate sensors over time: radars, RF direction-finders, EO-IR cameras, acoustic arrays, and increasingly passive RF detection grids. Each typically arrives with its own operator console, its own track format, and its own proprietary data model. The result is a fusion problem disguised as a hardware problem. Operators end up correlating tracks by voice or by eye, which is slow and error-prone precisely when seconds matter. A vendor-neutral C2 layer instead normalizes sensor outputs into a common track picture, applies correlation and classification logic, and presents one display. The hard engineering is in the interfaces, latency budgets, and track-quality management, not in any one sensor. That is why a successful year-long evaluation is a meaningful data point: it suggests the integration layer survived contact with real electromagnetic clutter, real false-alarm rates, and real operator workflows.