Clark said one potential drawback to the software-sold-separately approach is that vendors’ programming will need to be designed to work with multiple systems, and, as a result, could lose some of the performance that more tailor-made software might provide.
“When you’re writing the software for a radar, if you knew what the vehicle was going to be on every time, then you would write the software in a way that is tailored to the vehicle design, and also leverages what the vehicle’s other capabilities,” Clark said. “If it’s a highly modular system where you’re mixing and matching different sensors, or different electronic warfare jammers or different weapons payloads, that mixing and matching means you’ve got to genericize the software to a degree. That means you’re not going to be able to leverage all the functionality of the payloads every time.”
For that reason, Clark said, a software-sold-separately approach may not be right for the F-47, which is focused on delivering high performance. But other systems that wouldn’t require such high performance, such as next-generation mobility or refueling aircraft, may benefit from this strategy, Clark said.