Why EW effects look different in a targeting cycle
The deliberate joint targeting methodology—find, fix, track, target, engage, assess—was developed primarily around kinetic effects. A target is identified and nominated, approved through an engagement authority process, assigned to an effector, engaged, and assessed. The cycle was designed around physical events with observable indicators: a destroyed vehicle, a damaged runway, an asset that stops appearing in subsequent ISR collection. [JP 3-60, Joint Targeting, Joint Chiefs of Staff, available through jcs.mil, establishes the current joint targeting methodology and its component processes.]
Electronic warfare operates differently in three specific ways.
EW effects are temporary by nature. A jamming effect suppresses an adversary radar for the duration of the emission from a platform maintaining its position and power output. An electronic deception redirects an adversary sensor during the active engagement window. The effect ends when the platform repositions, when the adversary adapts, or when the EW resource is committed to a different task. There is no physical residue. This is not a deficiency; it is how EW works. But it means the F2T2EA cycle's assessment phase—which assumes a persistent, observable change in target state—does not directly map onto EW effects.
EW effect confirmation is probabilistic. With a kinetic strike, battle damage assessment works from observable indicators. With an EW effect, the adversary radar or communication link may have simply stopped emitting for another reason, or may have been suppressed only partially. Confirming that the effect was achieved requires either direct intelligence collection on the adversary's behavior or inference from correlated observations. That confirmation uncertainty is a design requirement for the targeting support systems representing the effect.
EW deconfliction is combinatorial, not exclusive. Kinetic fires targeting assumes mutual exclusivity: once a target is destroyed, it cannot be assigned again. EW effects are not mutually exclusive. Multiple EW platforms can simultaneously contribute to suppressing the same adversary emitter; a kinetic effector can strike a target that an EW effect has already suppressed; an EW effect on one frequency band may not address the adversary's backup emitter on another. The deconfliction logic for a mixed-effects engagement is fundamentally different from kinetic-only deconfliction, and commercially available targeting support tools built around the kinetic model were not designed to represent it.
The classification constraint
The more significant structural obstacle is classification. Most EW operations—particularly those involving specific waveforms, frequencies, electronic order of battle data, and exploitation techniques—are classified at levels that prevent their inclusion in common operational picture systems accessible to the full joint force.
The practical consequence: a fires coordinator working from a joint operations center may have full visibility on planned kinetic fires that have gone through the targeting cycle but no visibility on EW effects simultaneously planned or active in the same target area. From their picture, those effects are invisible. This creates real deconfliction risk. A kinetic strike planned without knowledge of an active EW operation may be timed in ways that complicate the EW platform's mission, or an EW effect may be terminated because the fires coordinator asked for something that the EW system's operator—in a separate classified channel—knows creates a conflict.
Joint doctrine on electromagnetic spectrum operations (current joint publications available through jcs.mil, including JP 3-85 on Joint Electromagnetic Spectrum Operations) establishes the requirement for integrating EMS operations with joint fires and other warfighting functions. The practical implementation—how EW effects actually appear in systems accessible to fires coordinators without exposing classified technique information—is an active architecture problem that doctrine establishes the need for but does not resolve at the system design level.
The information a fires coordinator actually needs is separable from the classified technique details. Knowing that an EW effect is active in a target area, its planned temporal window, its spatial footprint, and which platform owns it does not require revealing waveform parameters or exploitation methods. Designing that separation requires deliberate architecture decisions about what information lives at what classification level. Those decisions belong in the system architecture document, not in the judgment calls of individual operators managing two classification domains simultaneously at operational tempo.
Timescale mismatch
Deliberate targeting operates on hours. An air tasking order is typically built 72 hours ahead of the execution window; time-sensitive targeting compresses that cycle to minutes in specific contexts, but the process still involves staff coordination across multiple nodes. The authorization chain for effects—engagement authority confirmation, rules of engagement check, collateral damage estimation—was designed around a deliberate tempo.
Most EW effects do not operate on deliberate timescales. An EA-18G Growler crew adapts emissions in response to radar threats on a timescale of seconds. A ground-based jamming system countering an inbound UAS swarm may need to shift frequencies in under a minute. These adaptation decisions happen at the platform level because the threat does not wait for staff process. That is the right design. The problem is not making EW effects slower. The problem is representing those effects in the joint fires picture in a way that enables coordination without requiring the EW execution cycle to pause for staff authorization.
That requires a data model for effects that handles two things the kinetic model does not: temporal states (planned, active, suspended, concluded) that update continuously at platform tempo without requiring a new authorization action for each update, and a representation of resource availability that tells a fires coordinator whether a given EW asset is committed elsewhere, without exposing the details of that commitment. The architecture that satisfies both requirements is solvable but requires explicit design. It has not appeared as an explicit requirement in program specifications reviewed, based on available program documentation.
Where programs are working on this
The Air Force's Advanced Battle Management System program, which contributed to the broader DoD JADC2 framework, specifically addressed multi-domain effects coordination including non-kinetic effects in its operational demonstrations from 2020 onward. ABMS demonstration scenarios included representations of EW effects alongside kinetic fires in a multi-domain operations center context. [DoD ABMS program reporting available through af.mil; ABMS demonstration press releases describe multi-domain operational scenarios.] The demonstrations produced lessons about what a joint effects representation actually needs to contain, even if the resulting data standards were not fully operationalized before the program evolved into current JADC2 implementation efforts.
Bold Quest, the coalition interoperability exercise for cross-domain fire control, has addressed joint fires and EW integration in a multinational context, where the classification constraints are more acute—allied partners have different classification frameworks and cannot receive technique details that U.S. forces can access on a need-to-know basis. Bold Quest scenarios have tested what information actually needs to be shared at what classification level for effective EW-fires coordination, producing operational lessons about the practical minimum for coordination without technique exposure. [Bold Quest exercise reporting is available through DVIDS and defense press releases.]
The Army's Multi-Domain Task Force construct includes an organic EW element specifically intended to integrate EW effects with joint fires at the operational level. The data systems connecting MDTF EW capabilities to joint fires networks are in development and represent one of the more direct attempts to solve the integration problem at the unit level rather than at the enterprise architecture level.
What program offices need to specify
Programs that describe EW integration as a future increment are deferring three design problems that are harder to retrofit than to build in from the start.
An effects representation model for temporary, probabilistic effects. Targeting support systems represent effects as scheduled events with binary outcomes. An EW effects model needs to represent temporal duration, update continuously as platform state changes, and communicate confidence in whether the effect is being achieved—particularly against an adaptive adversary that may be responding. That model is a data architecture decision affecting every system component that represents effects. It cannot be added to an existing targeting system without touching the data layer those components share.
A classification separation architecture. The information a fires coordinator needs—effect active, temporal window, area, owning platform—is separable from the technique details that must remain in classified channels. Designing that separation requires explicit decisions about which attributes live in a joint effects layer versus service-specific command channels. Those decisions belong in the architecture document, and they need to be made early enough that both the fires coordination system and the EW command channel are built to exchange the same structured data. Ad hoc coordination procedures between separate systems produce the kind of friction that kills combined-arms timing under operational stress.
Training scenarios that include EW effects as inputs to fires coordination decisions. Operations center training that presents only kinetic fires coordination produces operators who understand kinetic fires coordination. If EW effects are part of the operational picture, the operations center needs people trained on scenarios where EW asset availability, timing, and effectiveness are variables in the fires decision—including the cases where the EW effect is terminated early, where the adversary adapts, and where the planned EW window does not cover the kinetic strike window. This is an exercise design requirement, not a live-system requirement, and it is cheap to address early.
What changes this assessment
These requirements apply in full to programs operating in contested, multi-domain environments where EW is part of a coordinated joint effects plan.
A program explicitly scoped to kinetic fires only, with EW handled through separate command channels and no requirement to present EW effects in the fires coordinator's picture, does not need the effects representation or classification architecture described here. It does need documented coordination procedures between its operators and the parallel EW command channel. That is a workable design choice if it is deliberate—it is not workable if it is the product of an assumption that someone else will solve the integration problem.
A program operating in a permissive environment where EW is primarily platform self-protection rather than an active joint targeting effect faces a simpler integration requirement. The timescale and classification constraints described here are significant when EW is part of the deliberate fires plan; they are much smaller when the EW element is only protecting the platforms executing the kinetic strike.
Sources and further reading
- JP 3-60, Joint Targeting — Joint Chiefs of Staff; establishes the joint targeting methodology (F2T2EA) and engagement authority processes; available through jcs.mil
- JP 3-85, Joint Electromagnetic Spectrum Operations — Joint Chiefs of Staff; establishes the doctrinal basis for JEMSO and EMS operations integration with other joint functions; available through jcs.mil
- DoD Electromagnetic Spectrum Superiority Strategy (October 2020) — establishes the DoD framework for competitive EMS operations and cognitive EW development; available through defense.gov
- ABMS program reporting — af.mil; covers multi-domain operations center demonstrations including non-kinetic effects representation across service and coalition boundaries
- Bold Quest exercise reporting — DVIDS; covers coalition EW-fires integration scenarios; relevant for the classification-separation lessons from multinational interoperability exercises
- GAO reports on JADC2 and EW modernization programs — GAO tracks both JADC2 program progress and service EW modernization investments; search "JADC2" and "electronic warfare" within the GAO reports database
Spartan X works on AI systems designed for contested, DDIL environments—the conditions where EW integration matters most. The architecture problems the EW-JADC2 gap represents—effects data models that handle uncertainty and continuous state updates, multi-layer systems that operate across classification boundaries, and AI infrastructure that maintains useful output when network conditions degrade—are the same problems Spartan X addresses for edge AI, C2 infrastructure, and multi-model verification. The fires coordination problem and the AI assurance problem share an underlying structure: both require systems that remain operationally useful when conditions do not match the nominal design case.
