USAF Wants One Software Integrator for KC-46 Fleet by Dec. 11

The Air Force gave industry a Dec. 11 deadline to propose a single software integrator for the KC-46 Pegasus tanker fleet, now past 100 aircraft and headed toward 263. The Air Force Life Cycle Management Center posted the request for information in late October. No contract value was disclosed. That omission matters.

The initiative carries a name: KC-46 Software Integration, Sustainment, and Support, or K-SWISS. An AFLCMC spokesman told Air & Space Forces Magazine the program office is exploring the effort "to consolidate these workstreams under a comprehensive, long-term enterprise software strategy."

What would the integrator actually do?

The contractor would manage software updates, upgrades, and coordination across the tanker's systems, some still under development. Work would run out of the Depot System Integration Electronics/Software Laboratory at Tinker Air Force Base, Oklahoma.

The stated objectives:

• Resolve software deficiency reports
• Adhere to Department of the Air Force risk management framework cybersecurity protocols
• Maintain continuous authority to operate across the fleet
• Synchronize multiple software certification cycles

The spokesman said the Tinker lab is already "scaled and postured" for current operations, upcoming deliveries, and future expansions. Scaled for what headcount or budget went unstated.

One requirement stands out for vendors: the RFI demands a comprehensive intellectual property and data rights framework. Boeing built the aircraft, and Boeing holds much of the code. Any integrator will need access. How that access gets priced is the question nobody has answered yet.

Has tanker software already failed?

The spokesman stressed no lapse has occurred. "Since the conclusion of Interim Contracted Support in June 2022, KC-46A software requirements have been continuously sustained without operational lapse through dedicated modernization and sustainment efforts," he said.

Read that closely. The denial covers the period after June 2022 only, and the RFI itself cites sustainment gaps in software management, testing, and modernization as the problem K-SWISS exists to fix. A gap in process is not a lapse in operations. But the Air Force is telling the market the current structure leaves holes.

The fleet's readiness record adds context. A Government Accountability Office report in June found the tanker missed its mission-capable rate goals every year from fiscal 2019 through 2025, scoring 62 percent in 2024. Software is one input among many. Still, the number frames why the service wants tighter control of the code base.

What else is in the upgrade pipeline?

The KC-46 is a heavily modified Boeing 767-200ER with probe-and-drogue refueling. A prototype first flew in 2014; Boeing won the contract in 2016.

Beyond software, the upgrade queue includes the Remote Vision System 2.0, which Boeing hopes to start retrofitting in 2028. The system moves the boom operator to the front of the aircraft, replacing the rear station with 4K Ultra HD cameras and a 3D display for distortion-free viewing in any lighting.

The legacy camera earned its replacement. It suffered poor lighting response, depth perception problems, and image washout, according to Air Force Research Laboratory documentation.

Other work in progress covers capability packages, additional software upgrades, and a redesign of the boom telescope actuator.

What is the open question?

The Air Force has defined the problem, the deadline, and the governance structure. It has not defined the money, the contract vehicle, or how a third-party integrator negotiates data rights with the airframe's original manufacturer. Proposals arrive Dec. 11. Until the Air Force answers those three questions, K-SWISS is a framework, not a program.