50 DAF Battle Network Programs Rolled into Single, $4.5B ‘Megatron’ Contract Vehicle

The Department of the Air Force is consolidating more than 50 programs supporting its efforts to create a vast battle network into a single $4.5 billion contract vehicle to streamline software and technology integration.

The contract, dubbed “Megatron” in reference to the lead villain in the Transformers toy and movie franchise, is a multiple award, indefinite delivery, indefinite quantity vehicle to get technology now and in the future into the DAF Battle Network.

Brig. Gen. Joshua Williams, the department’s new portfolio acquisition executive for command, control, communications, and battle management, highlighted the Megatron program at AFA’s Air, Space, & Cyber conference in September.

“The DAF Battle Network depends on an industrial base that can innovate, integrate, and deliver at the speed of relevance, and we need to build business mechanisms to enable their ability to do that,” Williams told reporters at the conference.

The contract vehicle will cover software delivery, commercial solutions to Battle Network challenges, and other tech needs, Williams said.

The draft notice for Megatron was posted in August, with a final request for proposals expected to be released this quarter. Multiple contract awards are planned for fiscal 2027 under the new “master plan,” Megatron Contracting Officer Julianne Payne told Air & Space Forces Magazine, “which span from sensor integration and connectivity to applications and secure data processing.”

“Key efforts include maturing our digital architecture, fielding secure processing at the edge, and delivering applications that put the operator at the center,” Payne added.

Merging Efforts

Past contract vehicles often created multiyear contracts tied to fixed requirements and hardware delivery. That doesn’t work in a world of rapid software updates, new sensors, and modes of communication needed for the DAF Battle Network.

“When a specific mission need arises, we can quickly compete delivery or task orders within this pool, compressing our acquisition timeline from over a year to a matter of months to get critical capabilities to the field faster,” Payne said. “For years, our sensors, command and control nodes, and warfighters have operated in stovepipes, making it difficult to share information quickly.”

The C3BM office’s decision to take this new contract approach isn’t happening in a vacuum. Payne noted that adversaries such as China are already building highly sophisticated capabilities to disrupt U.S. military networks. The larger effort to connect all operational capabilities via the battle network and ultimately to the larger Combined Joint All Domain Command and Control network must happen faster.

Soliciting, buying, and implementing standalone platforms for a single aircraft or satellite, common practice for decades, won’t cut it.

“If our systems do not integrate, they do not fight. That realization is what led to the creation of C3BM in 2022 to bring all those fragmented authorities under one roof,” Payne said. “Ultimately, that’s what drove us to the DAF Battle Network concept, and Megatron is the vehicle that is going to deliver it.”

Megatron combines two current IDIQ contracts: the Advanced Battle Management System IDIQ and the Air Force Life Cycle Management Center’s architecture and integration directorate’s XA IDIQ.

The ABMS contract launched in 2020 and was planned for an initial five-year run, allowing the Air Force to award multiple contracts for ABMS work across the force. The Air Force used the ABMS IDIQ to conduct live operational demos for real-time hardware and software testing in field conditions. Contractors participating ranged from small software companies to large defense primes.

The XA IDIQ was a planned 10-year effort from 2022-2032 to bring together early-stage concepts for the network’s architecture and integration.

But even with two large IDIQs, the Air Force had a problem. A company might bring a great concept to AFLCMC via the XA IDIQ but not have a contract under the ABMS IDIQ, creating a bottleneck between capability growth and deployment.

A New Approach

PAE C3BM intends to use the new Megatron contract to find the “best-of-breed” option across six lines of effort for the Battle Network:

Digital Architecture & Standards
Sensor Integration
Secure Data Processing (including Cloud, AI, and Machine Learning)
Network Connectivity (Line-of-Sight, Beyond-Line-of-Sight, and anti-jamming)
Software Applications
Synthetic Environments (computer-simulated training and development)

Staying Relevant

With rapid upgrades across the tech industry, the Megatron contract, and larger C3BM efforts, the goal is to bring the best tech into the system while keeping it secure and standardized across the network.

The PAE’s secure processing strategy works across multiple security classification levels, Payne said.

“This capability applies to form factors ranging from enterprise data centers to tactical edge hardware,” Payne said. “The contract mandates that vendors deliver compatible, mission-tailorable solutions, utilizing bare metal, virtualization, or cloud-based services.”

Across the Department of Defense, information technology managers and decision-makers face the burden of maintaining legacy technology and software while merging old but sometimes linchpin systems with new software and hardware.

With Megatron, officials seek to prevent “technical debt,” or the continued use of legacy systems that can’t be upgraded, and avoid future “vendor lock,” which allows a single vendor to control vital software or hardware because of proprietary constraints.

“If a contractor’s solution becomes obsolete or creates technical debt, we can recompete future delivery orders or task orders among the other qualified vendors in our pool. This continuous competition at the order level incentivizes contractors to deliver open, modern, and cost-effective solutions,” Payne said.