The Five Hard Truths

EW/ISR systems live in a constant knife fight for priority and funding. They are essential but painful to resource in practice. When programs stall, it is rarely because the technology fails. It is because the system has run into one of five walls that define how the DoD actually buys and fields capability.

No Validated Requirement, No Money

Every successful program starts with a named requirement and a funded line in the Program Objective Memorandum (POM). Without it, even the most promising prototype dies in the Valley of Death between Research (BA 2-3) and Procurement (BA 4-5). EW/ISR suffers here because their effects are cross-domain, and nobody “owns” them.

Why it matters: No Joint Requirements Oversight Council (JROC) validation means no Key Performance Parameters (KPPs), no Program of Record, and no enduring funding.

What fixes it: Align your capability to a specific platform or enterprise requirement, tie it to measurable mission outcomes like detection probability (Pd) or time-to-detect, and secure a program sponsor who budgets the wedge two years ahead.

(Rooted in JCIDS and JROC policy; repeatedly flagged in GAO’s audits of ISR acquisition failures.)

The Wrong Color of Money

EW/ISR systems often straddle RDT&E, Procurement, and O&M, and teams try to buy integration work with the wrong appropriation. Contracts stall because color-of-money is not flexible.

Why it matters: You can’t field a prototype with RDT&E funds or maintain an operational fleet with Procurement dollars. The misalignment breaks the chain between technology maturity and fielding.

What fixes it: Build a clean work breakdown structure mapped to Budget Activity codes (BA 2–5) and O&M. Phase the transition intentionally instead of hoping for reprogramming.

(Grounded in PPBE practice and Defense Acquisition University funding rules.)

Spectrum Access and Certification

No spectrum approval, no test range, no mission. The NTIA’s Stage 1–4 certification process is slow, and every range operates under finite frequency coordination. ISR payloads that radiate or record outside assigned bands face immediate suspension.

Why it matters: EW and ISR operate where spectrum is most crowded. Delay in NTIA or range deconfliction can add 6–12 months.

What fixes it: Start frequency coordination at design kickoff. Treat spectrum engineering as a funded workstream. Bring your NTIA Stage 2/4 paperwork to every test readiness review.

(Defined in the NTIA Manual, Chapter 10; reinforced in DoD EMSO strategy and GAO reports on EMS congestion.)

Cyber and Crypto Bottlenecks

RMF accreditation and Encryption add months if not planned from day one. The Authority to Operate (ATO) process now spans Developmental Test (DT), Operational Test (OT), and sustainment.

Why it matters: Every payload that touches classified data must prove encryption, key management, and zero-trust compliance. A late cyber sprint can stop flight certification cold.

What fixes it: Treat cyber as a parallel engineering line. Deliver RMF artifacts as contract deliverables, and leverage already-accredited hosts or enclaves. Align crypto modernization (KGV/Type 1) with program milestones early.

(Driven by DoDI 8510.01 and DoD CIO zero-trust mandates.)

Platform Integration Risk

It’s easy to brief “modular payloads.” It’s hard to fit them into a jet. Size, weight, power, thermal load, EMI, airworthiness, and flight test all fall on the platform SPO. If your system isn’t in their baseline schedule, it’s a science project.

Why it matters: Every extra connector or rack slot affects airworthiness, cooling, and sustainment. SPOs protect their schedules first.

What fixes it: Earn a slot on the baseline integration plan. Deliver a signed integration schedule, configuration drawings, and a fully funded change request. Speak the platform’s language. Sortie rate, MTBF, mission data load time, not abstract capability metrics.

(Rooted in JCIDS deliverables and platform SPO budgeting authority.)

Takeaway

EW/ISR systems lose funding not because the technology fails, but because they misalign with the acquisition bloodstream. The key is to build systems that live inside the DoD’s structure, not outside it.

Validated requirement. Correct appropriation. Spectrum and cyber cleared. Platform integrated. Everything else is noise.