Two S-Curves and the Counter-UAS Challenge: How Halo_Shield Was Built on the MAYA Concept
By Paul Webber, Director, Strategic Initiatives, Advanced Defense Solutions, AV
U.S. and allied partners have a problem: new and very real threats from a class of low-cost, autonomous, or semi-autonomous weapons that have disrupted traditional military advantages by imposing exponential costs on legacy Western defense systems. Recent media reports of Iranian Shahed-type attacks on U.S. radar facilities in the Arabian Gulf are but one example. Shaheds cost tens of thousands of dollars, cheap enough to field at scale by most of adversary nations, and capable of delivering deadly effects. And the threat is worldwide; Russia has launched tens of thousands of long-range drones into Ukraine and are producing hundreds per day.
I’ve spent most of my career working with people whose job is to keep bad things from happening to Americans. For the past several years, I’ve architected counter-drone (C-UAS) solutions at AV. I’m paying attention to the technology paradigm shift in real time, where an S-curve that moves faster and scales wider is putting unprecedented strain on defenses built for a different era.
A useful way to understand this paradigm shift is to view the evolution of air defense as two separate S-curves (measurable growth over time) and recognize that today’s challenge is the growing mismatch between them.
S-curve #1: Traditional Air Defense
This model was designed to protect high-value assets from a limited number of high-end threats. It assumes centralized sensing and command and control (C2), time to build clean tracks, human decision management, and hard-kill interceptors to finish. Inside those assumptions, the traditional model works extremely well. The challenge is that its design assumptions don’t translate cleanly to the problem of mass adversary drones. A radar built to see large, predictable signatures at range is not optimized to find masses of drones with small radar cross sections hugging terrain as they approach our defenses.
The issue is not that the model failed. It did exactly what it was designed to do.
S-curve #2: The UAS Era and Distributed C-UAS
The UAS era flips the math, because low-cost platforms have been fielded at scale, with widely varying signatures, dynamic tactics, and coordinated deployment from saturation to swarming. The shift is not just in complexity, but in volume and velocity. The limiting factor is the speed with which a defense can detect, correlate, decide, and assign effects to mitigate those threats.
Which is where defenses break down.
Defenses don’t fail because they can’t defeat a drone. They fail because they lack counter drone capacity, because operators are saturated, decision timelines stretch, and expensive effects get consumed faster than they can be replenished.
It’s an architectural gap, not a technology gap.
From Problem to Architecture
America’s answer to mass cheap drones can’t be to stretch legacy systems further, which will be neither effector nor affordable. It has to be a rethinking of how we scale and build CUAS capacity.
At AV, that shift is taking shape in Halo_Shield™: a modular, tile-based, distributed C-UAS architecture designed for high-volume environments. Instead of concentrating sensors, decisions, and effectors at a single point, Halo_Shield distributes them across the battlespace. Each Halo_Shield “Tile” functions as a self-contained node, combining sensing, processing, and engagement capabilities at the edge, while contributing to a shared operational picture through AV_Halo, our AI-driven command platform delivering unified, real-time battlespace awareness and control.
This is a fundamental change in how defense is constructed.
Point defense concentrates capability, and it inherits limits. Distributed defense multiplies capability.
By dispersing sensors and effectors, Halo_Shield extends detection timelines, increases engagement opportunities, and builds depth into the fight, enabling attrition before threats ever reach a final engagement window. Just as importantly, it scales without creating new bottlenecks. Each Tile adds capacity, but not complexity.
Where Good Ideas Break Down
There is a hard truth in C-UAS.
Many capable solutions work in demonstration events but fail in deployment because their interfaces are too complex, integration with command-and-control architectures is too fragile, and data overloads operators and slows decisions.
Implementing MAYA: Most Advanced Yet Acceptable
As I continue to watch the S-curve paradigm shift, I keep coming back to a design principle of product innovation: MAYA, Most Advanced Yet Acceptable.
MAYA reminds us that having exquisite technology does not necessarily mean having efficient, effective fieldable systems. Especially in defense, the best solution is the one that can be trusted, trained, integrated, and fielded quickly and repeatedly.
Applied to C-UAS, MAYA means being advanced enough to compress the OODA loop (Observe, Orient, Decide, Act) against scale and speed, while still acceptable enough to fit real operator workflows, rules of engagement constraints, and integration realities.
We’ve all seen the brilliant concept and working demonstration. And then reality shows up: the user experience looks like a cockpit built by committee, the integration requires sequential miracles, the sustainment plan is basically “good luck.” The operator does not trust it, and the system never scales past the pilot.
MAYA forces discipline: innovation must scale operationally, not just technically. And in C-UAS, MAYA is not just philosophy. It is survival.
We developed Halo_Shield around this philosophy.
What MAYA Looks Like in Practice
MAYA isn’t a slogan. It shows up in how systems are built, deployed, and actually used in the field. And the MAYA approach tends to share a few traits.
It starts with progress that can be measured, or stepwise capability growth. Real phases, real metrics, real learning, real measurable outcomes.
It requires clear human-in-the-loop boundaries. Automation should remove friction and compress decision time, not create mystery behavior. Trust is earned one engagement at a time.
It demands simplicity in the form of clean workflows that reduce screens and cognitive load. If the system requires a new operator for every new sensor, you did not scale the system. You scaled the staffing problem.
It depends on architecture that assumes change or what we call “Integration-first Architecture.” Sensors and effectors will evolve faster than legacy C2 cycles. The architecture assumes change as a feature, not a surprise.
Tiles Versus Point Defense: The Distributed Path to Scale
This is where the distributed concept comes in, and it is not as exotic as it sounds.
A traditional point defense site has multiple sensors and effectors applied from a single geographic location. It is usually governed by the sensor with the biggest sensing range and the effector with the longest effective range. This is a valid construct, but it also has a hard limit: finite weapons before reload, finite operator bandwidth, and a tendency to centralize decisions until the system itself becomes the bottleneck.
Distributed defense does not concentrate capacity. It multiplies it.
Halo_Shield’s distributed approach adapts a proven doctrinal idea, area air defense, to the UAS scale problem. We call a geographic area where sensors and effectors are dispersed and not co-located a “Tile.”
Each Tile has edge processing and a C2 interface to manage the mitigation cycle locally while still contributing to a broader operational picture. Tiles are modular by design, combining AV-recommended components with Government-furnished and third-party sensors and effectors, so customers can leverage what they have today and integrate new capabilities as needs evolve.
The practical takeaway is simple: distribution helps elongate detect, track, identify, and defeat to accelerate situational awareness and enable attrition in depth instead of only at the last second. You build Tiles around limited first S-curve air defense sites and increase total system carrying capacity without pretending one point defense site can do it all.
Passive Versus Active: Right Sensor, Right Time, Right Place
Active radar has a place in the mitigation cycle as well. But in a transparent battlefield with long-range precision weapons and shrinking sensor-to-shooter timelines, “radiate all the time everywhere” is not a survivability plan.
A distributed approach like Halo_Shield enables more low- or no-signature, multi-phenomenology sensing such as passive radar, acoustics, and distributable Electro-Optical/Infra-Red (EO/IR), paired with edge computation that limits what must be transmitted to higher echelons.
That reduces bandwidth demand and lowers the risk that central nodes become both overloaded and targetable. It also aligns with first principles. A threat UAS must disturb air to generate lift and move. It must have physical form to carry the technologies that make it a threat. Radio Frequency (RF) detection is valuable when it provides high information value and can support pairing and scheduling, but it is not the only foundation. A signature-centric detection strategy creates an on-ramp for advanced processing and helps reduce latency in high-density environments.
The Bottom Line
This shift in air defense is not just about a new threat. It’s about new requirements: throughput, adaptability, and trust at scale.
MAYA is the discipline that keeps us honest. It forces a simple question: will this be fielded, used, and trusted when the sky gets busy, not just when the demo is clean?
Halo_Shield is the architecture that puts that discipline into practice: not a brittle, centralized stack that collapses under its own weight, but a distributed approach that can grow, integrate, and keep pace.
Together, they move us away from point solutions and toward something more durable: a distributed, scalable, operationally viable defense that delivers value on day one and stays relevant as the fight evolves.
And to be clear, Halo_Shield is not just an upgrade. It’s a shift in how we build defense in the first place, designed for the new S-curve and built to scale with it.
WHAT’S NEXT IN THIS SERIES?
In Part 2, Paul will unpack solutions to the modern C-UAS challenge, including phased introduction of an effective and efficient distributed sensing and effecting architecture, and how leaders can measure C-UAS capacity, and how to move quickly from demo to scale.
ABOUT THE AUTHOR
Paul Webber is a retired Marine Raider and strategic advisor with two decades of leadership, special operations, and systems analysis experience. He blends operational insight with design thinking to tackle complex defense challenges, particularly in emerging domains like C-UAS. Paul holds an MBA from the University of Georgia, an MS from the Naval Postgraduate School, maintains a Top Secret-SCI clearance, and applies a human-centered lens to technology adoption and workflow design in defense environments.
——
ABOUT AV — JOINING THE MISSION
AeroVironment (AV) is a defense technology company with a mission to invent and deliver advantage to U.S. and allied militaries. AV isn’t for everyone. We hire the curious, the relentless, the mission-obsessed.
AV doesn’t just build defense technology; we redefine what’s possible. As the premier autonomous systems company in the U.S., we deliver breakthrough capabilities across air, land, sea, space, and cyber. From autonomy-enabled drones and loitering munitions to integrated autonomy and space resilience, our technologies shape the future of warfare and protect those who serve.
Founded by legendary innovator Dr. Paul MacCready, AV has spent over 50 years pushing the boundaries of what unmanned systems can do. Our heritage includes seven platforms in the Smithsonian—but we’re not building history, we’re building what’s next.
If you’re ready to build technology that matters – with speed, scale, and purpose – come find your people.
EXPLORE OPPORTUNITIES
