Army chains three electronic warfare programs into one detect-and-jam loop

By the Army's own account of what comes next, the detect-and-jam chain that soldiers from the 11th Cyber Battalion worked with at Aberdeen still spans separate computers ^[3][14]. Its planned work includes a single interface so operators do not have to move between them, plus more soldier exercises and usability fixes ^[14].

Army officials described the test as a step toward a "develop once, deploy everywhere" framework for non-kinetic cyber and electromagnetic effects ^[11]. The idea is reusable software that runs across compatible hardware, so each new threat does not need a separate solution built for it ^[12].

In a simulated scenario of hostile forces talking while they prepared an attack ^[8], TRAC, a ruggedized open-architecture chassis built around the Army's CMOSS standard, detected the transmission and passed it on ^[5][8]. TDK takes a library of known adversary signals forward with it, built in part from the signals of interest listed by the US Cyber Command Arsenal ^[6]. For signals it does not recognise, it uses machine learning to work out frequency and waveform ^[6]. That analysis set the Warped Alloy response ^[8].

Warped Alloy is the piece that departs most from older kit, because it goes after protocols ^[7]. The Army says it can reconfigure compatible tactical radios on the fly to keep denying communications as an enemy moves through primary, alternate, contingency and emergency channels ^[17]. Once the underlying protocol changes, the chain starts again at detection ^[18].

The customer for this, in our view, is the radio maker. About seven months after the framework went to industry for integration into different software-defined radio architectures ^[13][16], the Aberdeen test delivered its effect through a radio hosted on TRAC ^[8]. A vendor pitching a stand-alone jammer built for one threat is now selling into a program that says it wants fewer of those ^[12].

The evidence for all of this is a four-day demonstration ^[15]. Interesting Engineering, which reported it, wrote that the event showed the systems' integration and was not evidence that a finished, fully automated battlefield capability is ready for deployment ^[10]. The report does not include a measured detection-to-jam time or a fielding date, though shortening that interval is the Army's stated goal ^[9].

For a vendor or a program office choosing what to build or buy next, we'd sort each component on two axes. The first is whether it sits on the shared CMOSS chassis standard or on its own hardware ^[5]. The second is whether it hands its output to the next step, as TRAC handed a signal to TDK, or keeps it on its own screen ^[8]. Shared standard plus handoff is what Aberdeen was assembled from; shared standard without handoff fits the chassis and still sends the operator to another computer. Own hardware with handoff is an integration project someone has to pay for, and own hardware without handoff is the stand-alone box. We'd build toward the first quadrant. The trade-off is committing engineering time to a program that has shown integration and has its usability work still ahead ^[10][14]. The simplest test at the next demonstration is to count the computers an operator touches between hearing a signal and jamming it. By the Army's account, that count is still more than one ^[14].