Pacific Defense wins Marine Corps EW prototype, signaling shift to open architecture

A 12-month contract award to a company most readers have never heard of just shifted the competitive terrain for who gets to build electronic warfare systems for the U.S. Marine Corps. Pacific Defense, an El Segundo-based defense contractor focused on signals intelligence and open-architecture mission systems, won the right to prototype next-generation EW capability for MARCORSYSCOM's Program Manager for Tactical Communications and Electronic Warfare on May 1, 2026. The contract does not have a disclosed dollar figure, rapid prototyping vehicles rarely do in their announcement phase, but it establishes Pacific Defense as the incumbent for what will almost certainly become a production contract worth significantly more. That matters because the USMC is finally adopting the same modular, software-defined approach to electronic warfare that the Army validated years ago. The Marine Corps has historically built its tactical systems around single-vendor solutions locked into specific hardware. That approach worked when threats moved slowly. It does not work now.

The competitive landscape for defense EW has split into two tiers: the legacy primes (Raytheon, Northrop, L3Harris) who built monolithic systems, and a new layer of companies like Pacific Defense that treat EW capability as a collection of interchangeable software modules running on open hardware standards. The Defense Department has been pushing this shift for five years through SOSA (Sensor Open Systems Architecture) and CMOSS (C5ISR Modular Open Suite of Standards), technical standards that let you swap out a signals processor or a radio without redesigning the entire vehicle. The Army's CMOSS Mounted Form Factor program proved it works. Now MARCORSYSCOM is asking the same question the Army already answered: can we build fighting vehicles where the electronic warfare brain can be upgraded without swapping out the whole platform? Pacific Defense's contract is the official yes. It also establishes a troubling pattern for competitors: Pacific Defense is now the incumbent on the Army's CMFF program, the USMC's next-gen EW prototype, and Australia's Land 555 program. That is not accident. It is the structural result of being first into an emerging standard.

The contract itself is narrowly scoped: Pacific Defense will deliver SOSA/CMOSS-aligned mission systems to enable vehicle-based experimentation by U.S. Marines over 12 months. Translation: build a working prototype, plug it into a test vehicle, run it through Marine Corps exercises, and collect data on whether the architecture holds up against jamming, latency, and the chaos of tactical radio environments. Frank Pietryka, VP of EW, SIGINT and Autonomy at Pacific Defense, characterized it correctly in a statement to Soldier Systems Daily: 'This effort reflects a pivotal shift toward software-defined, open architecture C5ISR/EW capabilities that can keep pace with the modern threat environment.' The operative word is 'shift.' This is not an incremental improvement to existing USMC EW systems. This is the service pivoting its acquisition model from 'build one thing, use it for 15 years' to 'build a chassis and swap capability modules.' That pivot is years behind the Army, which is exactly why MARCORSYSCOM needs data from an actual prototype rather than a PowerPoint.

Why did this happen right now? Three factors converged. First, the Army's CMFF program demonstrated that modular EW works at scale, Pacific Defense has been the incumbent there, which means the USMC could see real-world performance data before committing. Second, the National Defense Industrial Strategy and Biden-era acquisition reform directives made open standards a procurement preference, not a nice-to-have. MARCORSYSCOM's PM TCE literally cannot award a production contract without SOSA/CMOSS alignment anymore; that is doctrine now. Third, and most important, the threat environment moved faster than legacy EW systems can respond. Contested electronic warfare is not just about air defense anymore, it is about spectrum dominance in tactical networks where every vehicle is a node in a mesh. You cannot do that with a single-vendor black box. You need modular software that lets you insert new AI-driven signal detection, new jamming payloads, new radio protocols without redesigning the hardware. The Marine Corps finally understood that. This contract is evidence they understood it.

Pacific Defense wins the prototype award, but the real victory belongs to the SOSA/CMOSS industrial base as a whole. This contract signals to every other player in the space that the Marine Corps is moving toward open architecture, which means the 12-month prototype window is really a 12-month competitive data-collection period. L3Harris, Mercury Systems, and Curtiss-Wright will all be watching the results. They cannot win the incumbent slot, that goes to Pacific Defense, but they are already planning for the follow-on production RFP, which MARCORSYSCOM will almost certainly issue in FY2027 Q1 or Q2. That is where the real market prize sits. The prototype contract is the proof; the production contract is the scalable business. For Pacific Defense, the clock is ticking to generate data clean enough that MARCORSYSCOM leadership feels confident expanding this architecture across the entire EW modernization roadmap. Fail in the prototype phase and you lose the incumbent advantage. Succeed and you have locked in a cross-service foothold (Army, USMC, and Australia all running the same basic stack) that competitors cannot easily dislodge without proving an architectural advantage, not just a feature advantage.

Here is what the market actually sees happening: the USMC EW contract is not about Pacific Defense specifically, it is about the death of monolithic defense EW systems and the emergence of a modular, standards-based competitive terrain where a smaller contractor can win a critical capability slot if they build on the right architecture. Pacific Defense benefits from timing and incumbency, but the structural shift is larger. Once MARCORSYSCOM commits to SOSA/CMOSS for production (not just prototyping), every company bidding for the follow-on will have to build to those standards. That levels the field compared to the old model where Raytheon or L3Harris could lock in proprietary solutions through classification or integration complexity. Open standards are a forcing function toward real competition. The Marine Corps just signaled they are ready for that. Whether Pacific Defense can sustain the incumbent advantage through the prototype phase is a separate question, and one where the next 12 months of data collection becomes evidence in a larger competitive trial. The company has one year to prove that open architecture EW actually performs under tactical conditions. If it does, MARCORSYSCOM is positioned to become a model for how the rest of DoD modernizes electronics. If it does not, the whole SOSA/CMOSS EW narrative takes a credibility hit just when the Pentagon is betting on it.

Watch three specific milestones over the next 14 months. First, the Pacific Defense prototype system must be ready for field experimentation by Q1 2027; delays push back the MARCORSYSCOM follow-on RFP and give competitors more time to develop alternative architectures. Second, look for Pacific Defense systems to integrate with JIATF-401 counter-UAS infrastructure or appear in Marine Air-Ground Task Force exercises alongside Anduril Lattice C2 or similar common data fabrics by mid-2027, this is where you find out whether the open architecture actually works in the contested electromagnetic environment. Third, watch the follow-on RFP language in late 2026 or early 2027; if MARCORSYSCOM explicitly cites Army CMFF lessons learned and mandates SOSA/CMOSS compliance, the Marine Corps has fully committed to the modular stack and the competitive market for modular EW components becomes real. If the RFP waters down the standard or allows proprietary exceptions, the shift is weaker than the announcement suggests. The contract is real and the data requirement is real. Whether it converts to a durable market change depends on whether the prototype actually performs.