Electromagnetic Warfare

A practical EW workflow starts with intercepted RF activity and ends with a confidence-rated assessment. The analyst asks: what was observed, which emitter could have produced it, where was it likely located, which platform or weapon system carries it, and what does that imply for the Electronic Order of Battle?

The core loop is collect -> describe -> cluster -> identify -> locate -> assess. Collection produces measurements such as frequency, pulse width, angle of arrival, and received power. Description normalizes those measurements into records a system can compare. Clustering groups measurements that appear to come from the same source. Identification compares a cluster against known emitter fingerprints. Location combines bearings, sensor positions, and timing evidence. Assessment records the confidence, source reliability, and operational meaning.

This is where Foundry-style analytics fits naturally. Ontology objects can represent emitters, platforms, weapon systems, units, intercept sessions, signal clusters, and assessment records. Links preserve the reasoning path: a signal cluster matched an emitter; the emitter is mounted on a platform; the platform is assigned to a unit; the unit belongs to an EOB hypothesis. That graph is more useful than a flat table because it lets analysts revisit assumptions when new evidence arrives.

A PDW is a compact measurement of a single pulse detected by a receiver. It usually captures when the pulse arrived, the measured frequency, pulse width, amplitude or RSSI, angle of arrival, and sometimes quality flags. A PDW is deliberately small: it is metadata about a pulse, not the full raw waveform.

A pulse train is a sequence of related PDWs over time. Looking at the gaps between pulses gives you PRI (Pulse Repetition Interval), while counting pulses per second gives you PRF (Pulse Repetition Frequency). These are two views of the same timing behavior: PRI is the interval, PRF is the rate. Radar modes often reveal themselves through timing regularity, stagger, jitter, dwell switching, and bursts.

PW or pulse width describes how long the transmitter stayed on for a pulse. Frequency describes where the pulse sits in the spectrum. Modulation describes how the pulse changes internally. I/Q samples are a deeper representation of the waveform itself: in-phase and quadrature components that preserve amplitude and phase detail for advanced analysis such as spectrograms, phase behavior, and modulation inspection.

An emitter is the RF source: radar, jammer, radio, datalink, interrogator, or navigation transmitter. A platform is the physical carrier: aircraft, ship, ground vehicle, site, satellite, or pod. A weapon system is the system-of-systems that groups launchers, sensors, command-and-control nodes, support vehicles, and sometimes jammers. An EOB is the assessed Electronic Order of Battle: what electronic systems are believed to exist, where they are, how they are organized, and how confident analysts are.

Good EW data models keep these concepts separate. A radar type can appear on many platforms. A platform can carry multiple emitters. A unit can operate several platforms. A specific deployment instance can differ from the generic family or variant. Separating those layers prevents a common analytics failure: treating one observation as if it proves the whole unit structure.

The EWSTT-style hierarchy is useful for learning: Platform -> Weapon System -> Emitter -> Radar Function -> Signal -> PDW. Read upward to understand operational meaning. Read downward to understand evidence.

EW terms can sound interchangeable until you map them to jobs. ES or Electronic Support is sensing and exploiting emissions for awareness and intelligence. EA or Electronic Attack is using electromagnetic energy or related techniques to create an effect against an adversary system. EP or Electronic Protection is protecting friendly systems from interference, exploitation, or attack. ELINT focuses on non-communications electronic intelligence, especially radar and signal characteristics. COMINT focuses on communications intelligence.

EMCON means emissions control: deliberate management of friendly transmissions to reduce detection, interference, or compromise. BDA means battle damage assessment, but in an EW context it often means effect assessment: did the target stop emitting, change mode, move, degrade, or recover?

Analytics supports these workflows by making uncertainty visible. A dashboard should not only say "matched emitter." It should show the evidence, confidence, reliability, freshness, alternate hypotheses, and what new collection would reduce uncertainty.

A useful EW analytics product usually has four layers. The first layer is measurement hygiene: normalize units, preserve collector identity, retain timestamps, and keep raw records traceable. The second is parametric comparison: compare frequency ranges, PRI behavior, pulse width, modulation family, scan mechanism, and band. The third is contextual linking: connect candidate emitters to platforms, platforms to units, units to locations, and locations to mission context. The fourth is assessment management: record confidence, source reliability, information credibility, and competing hypotheses.

Foundry can model this as an ontology-backed intelligence graph. Object Types represent PDWs, signal clusters, emitter candidates, emitters, platforms, weapon systems, units, and assessments. Link Types preserve reasoning paths. Actions let analysts promote, reject, or revise hypotheses with audit history. Functions can compute derived scores, freshness, conflicts, and missing-evidence prompts.

The smart design choice is to show the analyst both the conclusion and the evidence ladder. A good interface answers "what do we think?" and "why do we think it?" in the same view.

Use this as the first-pass decoder. The important habit is to ask whether a term describes a measurement, a signal behavior, a physical entity, an operation, or an assessment. That category usually tells you where it belongs in the data model.