Navy’s $10B IT Spend Is More Hardware Than You’d Think: A PSC-Level Look

Ask ten federal IT capture managers what “Navy IT spending” buys and nine will say application development labor, help-desk seats, cloud subscriptions billed under codes like DA01. That holds for the Air Force, the VA, and DHS. It breaks the moment you open Navy’s own FY2025 Product Service Code list, where $10.1B in total IT obligations splits in a direction almost nobody is positioned for.

Two of the Navy’s five largest PSC categories aren’t labor or software. They’re radios.

The Assumption Everyone Makes About DoD IT Money

Most DoD component IT spend is coded as labor, and Navy mostly follows that pattern too, except where it doesn’t. Across the dataset, Air Force, Army’s civilian-style accounts, VA, and DHS all lead their PSC lists with DA01 application-development labor, often trailed by DA10 software-as-a-service and 7A21 perpetual licenses. It’s a fair pattern to extrapolate from, which is exactly the problem.

Navy’s $10.1B FY2025 total, tracked the same way USAspending.gov tracks every other component, does lead with DA01 labor. But the next four codes tell a different story than the one capture teams have been building pipeline decks around.

What Navy’s Top PSC Codes Actually Reveal

Two of Navy’s top five PSCs in FY2025 are physical radio and network hardware, not labor or SaaS. DA01 still leads at $2.0B. But sitting right behind the expected 7A21 software-licensing line ($728.3M) are 5821, airborne radio and television communication equipment, and 7G20, analog voice network hardware.

Stack 5821 and 7G20 together and you get $1.26B in equipment riding inside what most market trackers would file as “Navy IT spend.” A PSC is a classification code, not a vendor type, so a hardware manufacturer and a labor shop both sit inside the same “IT” total without anyone flagging the split. That’s a market segment PSC-level commentary skips because it doesn’t fit the software-labor template written for Air Force, VA, and DHS. It’s not a one-year blip: Navy’s FY2024 top five also carried 5821, at $746.5M, alongside 5825 (radio navigation equipment, non-airborne) at $502.7M.

The NAICS Confirmation: Radio Manufacturing Rivals Systems Design

Navy’s NAICS list confirms the PSC pattern: a hardware-manufacturing code is its second-largest IT category, not a services or labor code. NAICS codes classify the industry of the company performing the work, which is a different lens than PSC’s “what was bought” view, and the two agree here.

334220 outranking two separate computer-services codes isn’t noise. Computer Systems Design Services still leads at $2.2B, but 334220 Radio/TV/Comms Equipment manufacturing pulled $1.57B, ahead of Engineering Services and Other Computer Related Services. It held the same rank at $1.40B in FY2024. A manufacturing NAICS beating two pure-services codes, two years running, is a fleet-and-platform story, not a back-office modernization story.

Why Navy Looks Different From Air Force, VA, and DHS

Navy’s IT dollars are entangled with communications and navigation gear embedded in ships and aircraft, which the other components don’t carry at scale. Air Force’s FY2025 NAICS list includes 334220 at $930.3M, but it ranks fourth, well behind three computer-services codes. VA’s top five, across two fiscal years, contain zero hardware-manufacturing codes. DHS carries one hardware-adjacent code, J063 alarm and security equipment, at $610.2M, which is physical security, not comms or navigation.

Navy is the outlier in degree, not kind. The likely mechanism: a destroyer’s radio suite and a carrier air wing’s avionics get bought through acquisition channels that overlap with IT procurement, because the equipment rides the same networks IT budgets fund. Nobody needs a classified program name to see that; the categories themselves, airborne equipment, radio navigation, analog voice hardware, say it plainly.

What This Means for Vendors Chasing Navy IT Work

Hardware OEMs and systems integrators in radio and navigation equipment have a real, named lane into Navy’s IT-coded budget that a software-only search strategy will never surface. A BD team that only tracks DA01, DA10, and 7A21 postings is, by construction, missing over a billion dollars of Navy’s top-line IT spend every year.

• Avionics and shipboard radio manufacturers already selling into defense primes have a coded, trackable Navy demand signal distinct from app-dev work.
• Integrators bidding Navy enterprise IT should budget for hardware-and-labor bundled solicitations, not pure labor SOWs.
• Competitive intelligence teams benchmarking DoD components need PSC and NAICS granularity, because department-wide IT totals erase this split entirely.

The practical research problem is separating hardware-coded IT spend from pure platform and weapons-system spend, which requires PSC and NAICS drill-down, not a department total. The Air Force’s own PSC and NAICS breakdown is a useful contrast case precisely because it doesn’t show this split, confirming Navy’s pattern is real rather than a dataset artifact. Resellers sizing Navy the way they’d size underserved contracts at other agencies need to run that comparison before building a Navy-specific pitch.

How to Track This Yourself

Pulling Navy’s PSC and NAICS mix requires component-level drill-down, not a department total, because the hardware signal disappears the moment you zoom out to “DoD.” A few steps make that tractable without rebuilding a USASpending.gov query from scratch every quarter.

1. Pull Navy-specific obligations by PSC and NAICS rather than a blended DoD figure, using FedSpend’s Award Data to break DoD out by component.
2. Flag hardware-coded categories (5821, 7G20, 5825, 334220, 334290) separately from labor and SaaS codes so pipeline models don’t collapse the split.
3. Trace those categories back to R-1/P-1/O-1 budget lines through Programs & Budget to see which program offices are funding the equipment buys.
4. Watch upcoming recompetes in those same hardware categories through Recompete Radar, since radio and navigation equipment contracts cycle on different timelines than labor IDIQs.

The Mental Model Capture Teams Need to Throw Out

Treating Navy like a smaller, saltier Air Force IT budget is a capture-strategy error, not a rounding error. The evidence is in Navy’s own codes: a hardware-manufacturing NAICS outranking two computer-services codes, two years running, isn’t a fluke. A pipeline that only tracks DA01, DA10, and 7A21 postings is structurally blind to over a billion dollars of annual demand sitting in plain sight under equipment codes. The fix isn’t a bigger total. It’s reading the PSC list like Navy actually wrote it.