Defense electronics and mission systems

This is the parent guide for defense electronics: radar and RF sensors, electro-optical and infrared systems, electronic warfare, military communications, weapons, battle management, simulators, ground vehicles, counter-UAS and hypersonics. Each has a guide of its own. What they share is the frame around the purchase, and for a tier-two or tier-three supplier that frame is now the hardest part of qualifying.

The list decides who may see the design

Military electronics are enumerated on the munitions list by capability, including systems not captured in the fire control and sensors category, and the enumeration reaches the technical data directly related to those articles and the defense services performed on them.¹ That last clause is what catches new entrants. The drawing package, the interface control document and the engineer on the video call are all inside the control. Ask a supplier for the classification of the exact item and its basis, ask who at the company owns export compliance, and ask how foreign national access is controlled on the shop floor and in the engineering system.

Cybersecurity is now a gate, not a clause

Defense contracts require contractors to safeguard covered defense information and to report cyber incidents, with security requirements drawn from the published federal standard and a defined process for variances.³ On top of that sits the certification programme, which establishes requirements for contractors and subcontractors to implement prescribed cybersecurity standards for federal contract information and controlled unclassified information, with levels ranging from self-assessment to third-party certification and government-led assessment.² Ask which level applies to the work, what the supplier's current status is, when it was assessed and by whom. Ask the same question about the supplier's own subcontractors, because the requirement flows down and the weakest link is usually two tiers below the prime.

Data rights decide the next twenty years

Rights in technical data are defined and negotiated, and the definitions matter more than the price. Unlimited rights allow the government to use and disclose data without restriction, government purpose rights run for five years or another negotiated period on data developed with mixed funding, and limited rights keep data inside the government, which may not use it for manufacture or release it without the asserting party's written permission.⁴ Ask which assertions accompany the proposal, item by item. A programme that accepts limited rights on a critical interface has chosen its supplier for the life of the system, and that is a decision worth making deliberately.

Where the public record can be checked

Federal award data is public and names who received contracts, for how much and when.⁵ For a small supplier that record is often the only third-party evidence available, and it is genuinely useful: it shows whether the company has performed on federal work and at what scale. It does not show technical performance, schedule adherence or whether the programme was restructured, and it does not show subcontract work except where it has been reported. Ask for programme references and call them.

Questions that sort suppliers

Ask for the export classification and the compliance owner's name. Ask for the certification level, the assessment date and the assessor. Ask for the data rights assertions in writing before award. Ask what the supplier's longest-running production programme is and who runs it now.