Biden’s 2024 Budget Seeks $842B for Defense,  ‘21st Century’ Air Force

Biden’s 2024 Budget Seeks $842B for Defense, ‘21st Century’ Air Force

President Joe Biden’s $842 billion Defense budget request includes a 5.2 percent pay increase—the biggest in 22 years—“builds the Air Forces needed for the 21st century,” and “increases space resilience,” the administration said.

Topline budget figures released by the White House’s Office of Management and Budget offered scant details; the full budget is to be released March 13.

“The Budget funds the procurement of a mix of highly capable crewed aircraft while continuing to modernize fielded fighter, bomber, mobility, and training aircraft,” the OMB release said. “The Budget also accelerates the development and procurement of uncrewed combat aircraft and the relevant autonomy to augment crewed aircraft. Investing in this mix of aircraft provides an opportunity to increase the resiliency and flexibility of the fleet to meet future threats, while reducing operating costs.”  

Air Force Secretary Frank Kendall indicated earlier this week at the AFA Warfare Symposium that the Air Force will buy more F-35 Lighting II fighters than in fiscal 2023, new F-15EX fighters, and more KC-46 Pegasus tankers; it will also invest significantly in the B-21 bomber and Next-Generation Air Dominance systems.

The development and procurement of uncrewed combat aircraft—referred to by the Air Force as Collaborative Combat Aircraft—has been a well-known priority for the service. Kendall recently revealed notional plans to build 1,000 of the drones, which will fly alongside manned fighters. 

Air Force generals and civilian leaders have argued CCAs are necessary to build what they call “affordable mass,” giving the service enough aircraft to match an adversary like China while not costing as much as an entirely manned fleet. 

Space Force 

The White House budget document highlighted funding to improve “the resilience of U.S. space architectures, such as in-space sensing and communications, to bolster deterrence and increase survivability during hostilities.” 

Resilience or endurance of space operations under attack, whether by kinetic strikes or electronic jamming, is a defining aspect of Chief of Space Operations Gen. B. Chance Saltzman’s vision for the Space Force. He unveiled his theory of “Competitive Endurance” at the AFA Warfare Symposium, describing it as is a dis-incentivize to deter adversaries from striking first. 

The Space Development Agency has emerged as the most high-profile contributor to diversifying the national defense space architecture, developing plans to launch hundreds of satellites into low-Earth orbit in the coming years—including “layers” for sensing and tracking missile launches, as well as for communications, and transporting data. 

Budget Fights

The $842 billion topline for the Pentagon would be $26 billion more than the $817 billion appropriated for fiscal 2023—a 3.2 percent increase. Yet in an era of high inflation and increased threats, Congress may well up the ante, as it did in each of the past two years.

House and Senate Republicans will lead that charge. Sen. Roger Wicker (R-Miss.), ranking member on the Senate Armed Services Committee, and Rep. Mike Rogers (R-Ala.), chairman of the House Armed Services Committee, each released statements criticizing defense investment as insufficient. 

“The President’s defense budget is woefully inadequate and disappointing,” Wicker said. “It does not even resource his own National Defense Strategy to protect our country from growing threats around the world.”  

Rogers called the threats facing the United States “the most complex and challenging … in decades.” The president’s budget request “fails to take these threats seriously,” he added. “A budget that proposes to increase non-defense spending at more than twice the rate of defense is absurd. The President’s incredibly misplaced priorities send all the wrong messages to our adversaries.”  

But Biden will have supporters. Sen. Jack Reed (D-R.I.), chair of the Senate Armed Services Committee, praised Biden for crafting a “strong budget,” even as he left open the possibility for change. 

“Some will inevitably say the topline is too much, while others will claim it is not enough,” Reed said. “I say America’s defense budget should be guided by our values, needs, and national security strategy. This topline request serves as a useful starting point. I look forward to receiving the detailed budget request so we can get to work crafting a responsible, balanced National Defense Authorization Act.” 

Air Force Faces 10 Percent Recruiting Shortfall in 2023—And Long-Term ‘Headwinds’

Air Force Faces 10 Percent Recruiting Shortfall in 2023—And Long-Term ‘Headwinds’

AURORA, Colo.—The Active-duty Air Force is projected to miss its 2023 recruiting goal by 10 percent, amid a historic low unemployment rate and a growling lack of interest and eligibility to serve among young Americans, top service officials said earlier this week at the AFA Warfare Symposium.

“We are currently projecting about a 10 percent shortfall this year in the Active Air Force and more in the Guard and Reserve,” said Air Force Secretary Frank Kendall in his keynote address March 7. “We are swimming upstream against a reduced propensity to serve nationally across the board and a limited percentage of qualified candidates.”

The next day, Maj. Gen. Ed Thomas, the commander of the Air Force Recruiting Service, outlined some of the specific “headwinds” that his troops face as they try to sign up more recruits. These include a 3.4 percent unemployment rate, the lowest since 1969 according to the Department of Commerce. Only 23 percent of American youth are eligible to serve in the military, Thomas said, and only 9 percent say they are interested in serving.

The grim projections come in the wake of what was already shaping up to be a tough year for Air Force recruiting. The AFRS barely reached its fiscal 2022 goal for the Active-duty Air Force and missed its goals for the Reserve and Guard by about 1,500 to 2,000 recruits each. Last September, Thomas called the effort “a dead-stick landing” that would leave the service starting 2023 about 5,000 recruits short on the Active-duty side alone.

At the time, Thomas pointed to some of the challenges such as the lack of in-person recruiting due to the COVID-19 pandemic, low unemployment, and misperceptions about military service. Many of those long-term challenges persist.

“One area that I do want to highlight, which we believe is critical, is countering declining familiarity with the U.S. military,” said Thomas in a statement, citing research that 50 percent of American youth cannot name all of the military services, and 65 percent of young Americans said they would not join for fear of death or injury.

Thomas said the Air Force needs to counter misperceptions of military service by “increasing community outreach–getting out into the communities and re-introducing ourselves to America. I don’t just mean getting outside the gates of Lackland Air Force Base in San Antonio or Altus, Oklahoma. We must get out and provide meaningful exposure to our men and women in uniform across the nation, in the hard-to-recruit areas, and in all the places where Americans are not likely to know anyone in the military.”

In the meantime, the general said there is no “silver bullet or game-changing strategy” that will reverse the downward recruiting trends. Instead, AFRS has to pursue every small advantage it can, whether that is revising Air Force tattoo policies, updating body composition standards, changing bonus structures or other mechanisms to bring in more recruits.

“What we have concluded is that there are multiple areas where we need to adapt and improve performance by single or double-digit percentage points,” Thomas said. “We will continue to take a hard look at ourselves and leave no reasonable option off the table.”

There are bright spots for the recruiting service. For example, AFRS is on track to meet its Space Force goals and the Air Force in general enjoys strong retention levels.

“Retention numbers look very good,” Kendall said in his keynote speech. “We’re keeping the people that we get, but we need to get more people. People coming into the Air Force are staying with us, so please reach out to your communities and help us counter negative perceptions of our military service and share our positive and accurate messages.”

Ground-Penetrating Radar and AR Guide Airmen to Spark Tank Win

Ground-Penetrating Radar and AR Guide Airmen to Spark Tank Win

AURORA, Colo.—No one wants to stand up in front of the entire Department of Air Force leadership team and own up to being personally responsible for cutting vital communications lines in a war zone, but Tech. Sgt. Raymond Zgoda turned that error into an example of a much-needed, winning innovation March 8 in the 2023 Spark Tank Championship.

Zgoda and Master Sgt. Sarah Hubert (the originator of the winning idea), both of Yokota Air Base, Japan, won the competition before an audience of about 2,000 Airmen and Guardians with an idea for using ground-penetrating radar and augmented reality goggles to more precisely map underground pipes, wires, and fiber-optic lines on military bases to prevent accidental breaks caused by construction.

Spark Tank is an annual competition modeled after the “Shark Tank” TV program. Instead of entrepreneurs pitching investors for funding, Spark Tank enables DAF “intrapreneurs”—primarily Airmen and Guardians, but also including department civilians—to pitch innovative ideas and ask leaders to fund their projects. From an initial field of 235 ideas, or “sparks,” six finalists got to pitch their projects on the main stage at the 2023 AFA Warfare Symposium.

This year’s panel of judges included Secretary of the Air Force Frank Kendall; Air Force Chief of Staff Gen. Charles Q. Brown Jr.; Chief of Space Operations Gen. B. Chance Saltzman; Chief Master Sergeant of the Air Force JoAnne S. Bass; Chief Master Sergeant of the Space Force Roger A. Towberman; National Basketball Association Senior VP and Head of Referee Operations Michelle Johnson, a retired Air Force lieutenant general; and investor Michael Moe, founder of the merchant bank Global Silicon Valley.

Each of the six finalists were allowed a three-minute pitch explaining their ideas, their progress thus far, and the potential return on investment for the services. Panelists then had four minutes to question the presenters.

2023 spark tank
2023 Spark Tank Winners Master Sgt. Sarah Hubert and Tech. Sgt. Raymond Zgoda present their proposal to the Spark Tank panel. Photo by Mike Tsukamoto/Air & Space Forces Magazine

Hubert and Zgoda won the day with a straight-forward pitch.

“I’m a dirt boy,” Zgoda said. “I dig ditches. I’m good at my job, but without the proper tools and information, I can become a liability and insider threat. Unfortunately, I haven’t been issued X-ray vision. I am relying on inaccurate maps. I have personally seen our maps be off by as much as 75 feet from what is actually under the ground.”

Digging into underground storage tanks, wires, fuel lines, and other buried infrastructure is costly and all too common, they said. But by mapping areas using ground-penetrating radar and then fusing those findings with augmented reality, the solution the team presented can eliminate the risk of digging blindly—saving time, labor, money, and even lives.

For example, Hubert cited a sinkhole at Joint Base Lewis-McChord in 2020 that took two years and $77 million to repair. Ground-penetrating radar could potentially “detect these sinkholes at low costs before they turn into sunk costs.” Avoiding accidental damage to underground infrastructure could save up to $750,000 on wasted labor at every Air Force and Space Force base, the two said.

“Airmen and Guardians can die from hitting natural gas and electric lines,” Hubert said. “We cannot put a price on that loss.”

Their pitch won over Kendall, Saltzman, Bass, and Towberman, good enough to take home the prize. But all the projects earned the judges collective approval.

The “celebrity” judges reveal their votes for the Spark Tank 2023 champion at the AFA Warfare Symposium, March 8. Photo by Mike Tsukamoto.

The crowd favorite, indicated by electronic voting, was also Brown’s selection: “Project Kinetic Cargo Sustainment,” a system for accelerating airlift operations by implementing new digital processes for weighing and measuring pallets, vehicles, and other cargo before loading cargo craft. The idea was conceived by Master Sgt. Brandon Allensworth and Master Sgt. Peter Salinas, both from Kadena Air Base, Japan, who said the system can reduce cargo processing times from around 20 minutes per vehicle to a matter of seconds.

Both guest judges, Johnson and Moe, voted for “Accelerated Development of Multi-Capable Airmen and Guardians,” a Special Warfare training project touted to provide linkages between human systems and operational tasks. The concept was developed by a team of Airmen, including: Maj. Caitlin Harris, Chief Master Sgt Michael Rubio, Capt. Andrew Antonio, Tech. Sgt. Ty Hatcher, and Lt. Col. Peter Dyrud. Although still a prototype, the project is estimated to save an annual $3 million through graduation rates and has already received interest from multiple groups and across the DOD.

The remaining three “sparks” were all well-received by the judges, who praised the innovative solutions and encouraged their further development. They included:

  • DOD civilian Michael Dolan of Space Base Delta 3 at Los Angeles Air Force Base, for his “Real-time Asset Management System.” RAMS integrates the Air Force’s seven existing asset-management systems for tracking systems, people, and workspaces into a common interface, potentially saving 50,000 hours annually in wasted effort needed to track and map those assets.
  • Master Sgt. Aaron Cordroch, Hurlburt Field, Fla., for “Advanced Maintenance & Troubleshooting Suite,” a maintenance-troubleshooting dashboard and information database. Cordroch said AMATS can save the Air Force thousands of hours of equipment downtime by using predictive analytics to anticipate parts replacement.
  • Staff Sgt. Michael Sturtevant, Kadena Air Base, Japan, for Project Oregon Trail, a solution for lifting and moving pallets and equipment in all terrains without need of a forklift. Particularly relevant to agile combat employment scenarios, Sturtevant’s simple solution consists of four tripods for lifting the loads onto small wheeled platforms so they can be more easily moved by small teams. He envisioned equipping all expeditionary cargo craft with this gear in order to minimize the need for forklifts, which themselves make up a full plane load to get them into theater.

For more information on the six finalists in the 2023 Spark Tank, visit the Guardians and Airmen Innovation Network.

New Air Force Force Generation Model Will Stop ‘Crowdsourcing’ Deployments

New Air Force Force Generation Model Will Stop ‘Crowdsourcing’ Deployments

AURORA, Colo.—Looking to build stability and improve readiness, Air Force leaders said at the AFA Warfare Symposium they are planning a move in 2024 to what they call a more cohesive approach to deployments for Airmen.

That deadline to implement the service’s new force generation model—Air Force Force Generation, or AFFORGEN—is a self-imposed one, reflecting an urgency to shift focus to the Pacific and prepare for a more sophisticated fight, a panel of top generals said March 8.

“We’re changing fast enough now,” Lt. Gen. James C. “Jim” Slife, deputy chief of staff for operations said. “The reason we’re changing our force generation, force presentation models in the Air Force is because the strategic environment has changed.”

That changed environment means Airmen need to arrive at their deployed location prepared to work as a team without the luxury of time to work out the kinks—and AFFORGEN will emphasize that by grouping units together in new ways.

Instead of just bringing over squadrons, the Air Force will create XABs, or expeditionary air bases. That will replace the current model of air expeditionary wings. The goal is to bring more operations from a home base into a deployed location, including, for example, security forces personnel that previously may not have gone along with pilots and maintainers.

“It really goes back to what our National Defense Strategy says—we have to be ready for the high-end fight,” said Maj. Gen. Clark J. Quinn, deputy commander of Air Forces Central. “The AFFORGEN model is going to move away from the decades-long crowdsourcing—asking hundreds of Airmen to come from dozens of locations to arrive in their expeditionary wing, and then execute ops immediately as a high-performing team.”

Those teams of Airmen will cycle through four six-month phases in AFFORGEN—“available to commit,” “reset,” “prepare,” and “ready.” After twenty years of heavy demand for airpower during America’s fights in the Middle East that strained units and aircraft, AFFORGEN is supposed to provide predictability for Airmen and aircraft—and subsequently improve readiness.

“We’ve been able to get away with that in an operating environment where frankly, we have not been heavily pressured by our adversaries,” Slife said. “We’ve been able to get away with taking three Airmen from this base, five Airmen from this base and two Airmen from that base, deploy them and expecting them to come together on day one, be a team. But we don’t actually think that that’s the way the future operating environment is going to permit us to operate. We’re going to have to build and generate teams of Airmen at home station that train together, deploy together and then come home and reset together and go through that cycle.”

In addition to providing cohesion within the Air Force itself, leaders also expect AFFORGEN to make it easier to articulate what they actually have to combatant commanders and the rest of the joint force—and sometimes make sure they know requesting aircraft constantly will have long-term ramifications.

“It allows us to have what I would call a boundary on it to say ‘No.‘” Lt. Gen. Michael A. Loh, director of the Air National Guard, explained to Air & Space Forces Magazine. “You can’t just set up another location and more force elements—whether it be fighters, tankers, airlift—because we don’t have it.”

Loh explained that sometimes saying “No” to a commander’s request will ultimately benefit the rest of the U.S. military—if forces that are supposed to be in the training bin are deploying, then the Air Force may not be able to provide those forces in six months. Equipment may be overused, families will be strained, and retention will suffer, he said.

“When you gotta be all in, there’s a time to be all in, but for normal global force management, the natural tension between the combatant commanders and the service, this is how we’re presenting forces now,” Loh added. “That will build us a stronger Air Force over time.”

Watch, Read: ‘Transitioning to a Wartime Posture Against a Peer Competitor’

Watch, Read: ‘Transitioning to a Wartime Posture Against a Peer Competitor’

Maj. Gen. Heather Pringle, commander of the Air Force Research Laboratory, moderated a discussion with Andre McMillian, vice president of sustainment operations for military engines at Pratt & Whitney; Brian Morrison, vice president and general manager of cyber systems at General Dynamics; and David Tweedie, general manager of advanced products at GE Edison Works, on readiness ranging from technology to manufacturing to sustainment, on March 8, 2023 at the AFA Warfare Symposium. Watch the video or read the transcript below.

Maj. Gen. Heather Pringle:

Good morning. How are we doing today on day three of our symposium? Doing well? We have a great topic here today and we have great panelists. I want to say thanks for joining us today on an important topic, it’s transitioning to a wartime posture against a peer competitor. I’m really honored to be here with some of the thought leaders in industry on this critical topic. As we’ve all heard throughout the week, we are at a pivotal moment in history. The DOD is very clear-eyed about our peer adversary, our peer competition, and the multi-domain threats that it poses. Our nation has responded by advancing the concept of integrated deterrents in our national defense strategy, but should deterrence fail, then what?

Maj. Gen. Heather Pringle:

In this hour, or 40 minutes, more closely to the target, we’re going to talk about what it means for the Department of the Air Force to mobilize its forces at scale, to be ready with a wide range of information systems, facilities, and support, to deploy Airmen and Guardians to the fight, and most importantly, to win in air, in space, and in the cyber domains. In a word, this panel’s all about readiness, the seventh and essential operational imperatives. With me today, we have experts from industry up here on this stage. Thank you all for joining me. First up, we have Andre McMillan, who’s the Vice President of Sustainment Operations at Pratt & Whitney. Andre, if you would, please tell us a little more about you and your work.

Andre McMillian:

Thank you, General Pringle, and good morning, AFA. It’s great to be with all of you and certainly, it’s an honor to be on a panel. I lead all of our sustainment activities across all of our portfolio of military engines at Pratt & Whitney, so essentially, what that entails is that we’re responsible for activating all of the bases, the ships, the depots around the world. We’re also responsible for the customer support engineering to support all of our operators and maintainers in the field and in the depot. We also lead a team that’s responsible for the support equipment, for the movement of material around the world, and to industrialize the repair network. I’ll also share, I’ve been with Pratt & Whitney for 16 years, so I’m a 16-year industry partner, but also continue to serve as an Airman, 26 years as a mobilization assistant, and so it’s great to be with you this morning.

Maj. Gen. Heather Pringle:

Thanks so much, Andre. Next up, to my left, we have Brian Morrison, Vice President/General Manager in Cyber Systems at General Dynamics Mission Systems. Brian, tell us about yourself.

Brian Morrison:

I’m delighted to be here. Thank you for having me, ma’am. I’m grateful to all of you for coming. I come to this from a little bit of a different perspective, I think, than many of you. I come here with a deep and abiding passion for security and how we can use security to render the fight against our adversaries unfair. I’m not interested in any fair fights and I know you all aren’t either. I lead a business focused on cryptography and keys and information security throughout the department, but with a very heavy focus on the Department of the Air Force, and I’m delighted to talk to you today about readiness.

Maj. Gen. Heather Pringle:

Thanks so much, Brian. Last, and certainly not least, we have David Tweedie, General Manager of Advanced Products at GE Edison Works. David.

David Tweedie:

Thank you, General. I’m just happy to be here to represent GE, who’s been a proud supplier of the US military for over 100 years now. From the first US jet engine in 1942 to the first three-stream adaptive cycle engine in 2022 and everything in the 80 years in between, just really proud with the partnership with the US military and the Air Force. Specifically within my portfolio, I have general manager responsibility for a variety of advanced fighter engine development programs at different phases that’s really focused on bringing state-of-the-art technology into our product portfolio, both today and in the coming years to bring that capability to the war fighter. Again, just excited to be here.

Maj. Gen. Heather Pringle:

Thanks so much. Appreciate you being here. Thank you all. Brian, I’m going to start with you, and let’s jump in. Talk about the context of readiness and really what it means, what does it mean to you, your company, or your technologies?

Brian Morrison:

I think through decades of the department, we’ve thought of readiness as are our Airmen trained, are our platforms maintained, do we have sufficient ordinance? Do we have sufficient JP-5? It was really a purely logistical question and that resonates, I think, with many of us, amateurs talk strategy, professionals talk logistics. But I think that in the world in which we live today, we need to think of readiness as maybe there’s a step before all of that. Readiness has to include the security of our information, the security of our plans, the security of our orders, the security of our comm systems, because as we know, our peer competitors are going at that soft underbelly, so that to me is the central principle of readiness.

Brian Morrison:

If I made aircraft engines or a sustained aircraft, I might feel differently about it, but from where I sit, the key issue in readiness is left of launch. It is can we secure our information before conflict arises and then keep the security of that information during conflict? It’s maybe a little bit of a different view of it than the logisticians in the room, than the engine manufacturers, than the maintainers in the room, but I think it is as essential as any other part of readiness I can think of. Does that answer the question, ma’am?

Maj. Gen. Heather Pringle:

Absolutely. As we’re facing multi-domain threats, we have to think about readiness in a multi-domain way, so I think that makes perfect sense. It leads into my next question, which really, I’m going to target at Andre. You mentioned that you’re a commissioned officer in the military and you’ve been in for a while, so times have changed, technologies have changed, and so can you tell us how has readiness changed from when you’ve started to maybe today?

Andre McMillian:

I think as you think about what’s changed is the fact that we’ve changed our way of thinking from an industrial age mindset to more of a informational age mindset. What I mean by that is if you were to take a look at and view readiness through the lens of a system, it’s not only the technology readiness levels, it’s the manufacturing readiness levels, but it’s also the digital readiness levels that I think is incredibly important. If you look at, iPhone is a great example. iPhone was launched in 2007, here, as we sit, they’ve launched, in 16 years, 16 versions of an iPhone. There’s been this desire to continue to have iterative technology insertion along the way. If you were to look at propulsion, we have done exactly that same in partnership with the Air Force, who really adopted this idea early on with the Engine Model Derivative Program.

Andre McMillian:

As we look at our history with the F100, that has had several iterations of improvements along the way, we’ve had the F119, likewise, that has done the same. Many people don’t realize that the 119 was nicknamed the maintainers engine, and so it was already looking at logistics under attack, it was already thinking about a contested environment, and it was already thinking about how is an Airman going to be able to utilize and work within a hazmat suit, be able to use six common hand tools, remove and replace a line replaceable unit within 15 minutes and do it in a austere environment?

Andre McMillian:

We’ve taken that type of iterative design and technology and we’ve built that forward even to the 135. From a digital perspective, I’ll share with you that the 135, in one single flight, will actually download usable and useful data than what an entire 119 was able to do in one year, and so as you think about how we accelerate change from that perspective, it’s significant. We continue to do that, we have an engine core upgrade that we’re working through now, and we’re making sure that it’s supportable across the sustainment network across the globe.

Maj. Gen. Heather Pringle:

Having that digital underpinning and adapting quickly to change is really what is making today’s readiness different than the past, and so that’s particularly important as we’re looking at the scale of a pure competition and transitioning there, so really great words there. Speaking of pure competition, David, if we can, let’s talk about China. They have this concept of military civil fusion, where industry looks and everything that they do, they bring those advantages to the military, including its readiness posture. Here in the United States we have a different model, open society, et cetera. Do you have any thoughts on how we might better benefit from what industry has to offer, even, as Andre just mentioned, those digital technologies that are out there?

David Tweedie:

When we look at what our competitors are doing with their system, I think we need to step back and look at what are the asymmetric advantages of our system? There’s a couple that I’ll bring up, one, the first one is competition. Our free market, private sector system, competition is a driver and it provides innovation, it provides affordability, and it provides responsiveness to the end user/customer. While the DOD is often the obtainer of bespoke capability and therefore has to often fund during the development phase, and so some of that upfront investment to ensure competition throughout the life cycle might be more upfront, downstream, time and time again, both in the commercial world and in the military world, the implementation of a competitive structure over the life cycle can bring those benefits of innovation, affordability, and responsiveness.

David Tweedie:

And then one step beyond that, I think with recent world events, both with COVID and the challenges in Ukraine, have highlighted resiliency in the supply chain. It’s one of those things you never know how valuable it is until you lose it and I think that’s something over the last three years, we’ve all collectively recognized how fragile we were in terms of supply chain resiliency. That’s another intrinsic benefit to competition that’s harder to quantify on a dollars and cents basis, but again, it’s invaluable once you realize you don’t have it. But then the second thing to bring up is our commercial aerospace industry in the United States. We’re blessed it is the best in the world and it’s actually the largest capital goods export market, which sets a very strong for the United States.

David Tweedie:

It sets a strong foundation for our economy, which is intrinsically beneficial to our country, but then that provides some technologies and capabilities that can be leveragable in, it provides an infrastructure, whether that’s unique manufacturing capabilities, as well as industrial capacity. The commercial aerospace market is larger than the military aerospace market, so tapping into that brings that industrial benefit, as well as the workforce. We heard from Secretary Kendall that the Airmen are critical to the success of the department, of the Air Force. Well, our skilled workforce, both our engineers, our salaried and hourly manufacturing workforce, it’s a tremendous asset to this country, so now how do you get more of those products into the Department of Defense space and how do you get more of those commercial players into the defense world? Just a couple thoughts, commercial off-the-shelf procurement is an obvious way to do that.

David Tweedie:

One thing we sometimes see is you start with something that’s almost what you want that’s commercially available. And then as you start applying unique requirements for our unique military needs, each of those individual requirement decisions in a vacuum might make sense, but in aggregate, you might have marched so far away from the original commercial off-the-shelf intent that you’re giving up the cost and the economies of scale and what you’re really after, and you drive more cost, higher qualification costs. Maybe just it doesn’t work in all cases, but adjust the lens a little bit from how do I tailor the commercial off-the-shelf product to my unique military requirements, to maybe flip the script a little bit is can I tailor my military requirements to align with what the commercial world is producing and maybe live with not perfect technical requirements, but good enough technical requirements, but then give you that affordability and scale that you’re looking for to provide readiness?

David Tweedie:

And then finally, IP. I think there’s a great structure for commercial items. There’s a great structure for bespoke items, but some of the players, if you’re a small business with a very narrow, but very valuable IP, and that’s the center of your business, when you put that at risk, you’re risking your whole company. And then if you’re a more large, commercial-oriented business wanting to get into the commercial world, how much of that are you willing to put at risk? In that in-between zone of pure commercial versus pure military, is there an IP structure that can get more players on the field? It’s not a insurmountable barrier, but it’s a speed bump that that might be preventing fully tapping into that asset we have.

Maj. Gen. Heather Pringle:

If I were to summarize what you were just helping us understand, intellectual property, the talent, the people that actually make it all happen, and then looking at the requirements in order to do it at scale, are there ways that we can get good enough, min viable product, if you will? I really like all of that discussion. You also mentioned something that’s near and dear to my heart, as a lab commander, we’re constantly focused on what if we don’t know what the threat is that’s out there and we have to adapt to the unknown? COVID was the absolute perfect example. You rely on the talent to converge in a multidisciplinary way and solve that in new and different ways than what you might not have thought, and so that makes readiness a whole different aspect. Andre, I’m going to come back to you and see, have you learned anything? What did your company employ throughout the pandemic and are there lessons learned that we might apply to our readiness posture?

Andre McMillian:

Thank you for the question. I think if you look back over the last couple years, we’ve learned a very valuable lesson because the pandemic, clearly, was the great equalizer that affected every city, every county, every country, every continent, but it was at the same time, the natural force and function, in many respects, that actually brought us together when we needed to be together the most. I’ll look at the lens of our partnership, specifically our public-private partnership, which we have down at Tinker Air Force Base. I’ll share with you that during the last couple years, despite the fact that we had workforce disruption, despite the fact that we had supply chain disruptions and everything else that was going on, that location, across three engine series, the F119 that powers the F22, the F135, obviously, as well as the C-17 engine, in two years, they were able to increase their output year-over-year and it was the highest they actually had ever done and they did it during a pandemic.

Andre McMillian:

And then you would say, “Well, why is that?” I think in many respects, we were able to develop the right level of partnership that was required, we were able to move at the speed of trust, and we actually brought that same focus as we increased our capacity across the international sector. We actually have 36, 26 spaces, 10 ships, that we stood up within a couple years, that’ll be 74. I had a team that actually built three test cells in three continents and still had to deal with quarantining for two weeks at a time in the countries that they were at, so it just shows you that despite the distractions and the disruptions that we have, that there’s still a way to be able to partner together.

Andre McMillian:

I’ll share one more that actually hits closer to home is obviously, General Pringle being the commander of the Air Force Research Lab, this year, we’ll actually sign a data sharing teaming agreement with them, and it’s in an effort to be able to support digital thread for sustainment. We decided to partner with them on how do we look at flight safety critical hardware and how do we actually utilize the data mesh that’s there and accelerate it in a way that we can actually not only be able to come up with advanced repairs, but also maybe potentially look at different types of materials? This is all in an effort to be able to leverage sustainment and then more so leverage the network that we have across the globe to support our products.

Maj. Gen. Heather Pringle:

Thank you, Andre. As we become more involved and/or dependent or integrated in a digital way, we’re going to have to start to think about, or well, hopefully we’ve thought in advance about securing that and our communication strategy and cybersecurity. Brian, this brings me to you and a question for you about what steps can we take to be better prepared, whether it’s with our cybersecurity or our communication strategy for Airmen and Guardians?

Brian Morrison:

I think as an initial matter, what I worry about, and I think many of you worry about, is that we’re coming off a couple of decades of conflict in which all of our comms were essentially secured, we were not competing with a peer, and I think most of us in the room believe the next conflict will be quite different from that. I worry that maybe we have lost some of the fire in the belly in worrying about how to keep those comms secure. Look, in every circumstance, whether it’s your laptop at home or the iPhone in your pocket or the IFF system in your aircraft, in every circumstance, the first question is always about updates and patches. We have seen over time that most of the penetrations we’ve had have not been unbelievably sophisticated attacks, they’ve been known exploits or exploits of known vulnerabilities that we had the means and the knowledge to remediate.

Brian Morrison:

The first thing I think we all have to think about all the time is are we doing our, what I would call cyber hygiene? It’s a funny turn of phrase, but I think it makes sense. Are we eating our vegetables, from an information security perspective? The second thing I think we need to keep in mind is that the United States Air Force and the United States Space Force has largely solved many of the most thorny problems of warfare for the past five centuries. We now can deliver a weapons system anywhere in the world within minutes with near 100% accuracy and near 100% lethality. That was unthinkable for most of human history and now, it’s thunk, we can do it and we know we can do it.

Brian Morrison:

Unfortunately, our peer adversaries know we can do it, so they will, by necessity, pursue those asymmetric attacks, which have to be attacks on our information systems. What that requires us in turn to do is think like the enemy. I know there are no doubt planners and red teamers, probably in this very room, who make their living thinking like the enemy. We’ve got hundreds of pen testers in my business who think every day, how can we break what we’re doing? We’ve got to think like the enemy and then we’ve got to devote the time, treasure, and attention to stay ahead of the obsolescence curve, particularly in my part of the world at General Dynamics Mission Systems, with codes and crypto.

Maj. Gen. Heather Pringle:

That’s not just a military issue, it would also be one in industry, as well. Do you have any thoughts on that?

Brian Morrison:

David said something I loved, he said, “Our asymmetric advantage is our competition.” I think that’s a wonderful response to the sort of unity of effort you can get in a totalitarian country. I totally agree. I think our competition will allow us to respond to that unity of effort. The challenge is that, again, our enemy knows that we are more innovative, that our technologies develop faster, so they’re stealing it left, right, and center, so that’s the industrial base threat is how do we keep them from stealing our mittens, so to speak? You know they’re trying, we know they’re trying, and we see it every day, OSI warns us all the time, our own internal security departments warn us all the time. While I totally agree with David that our innovation can get us out of this box, we’ve also got to protect our innovation.

David Tweedie:

100 percent agree with that.

Maj. Gen. Heather Pringle:

Jump in, please don’t be shy. It’s a great topic. David, let’s pull the thread a little bit more. How can industry be better prepared, whether it’s in this area or, as we’re talking about, this transitioning to a wartime posture? We are talking at scale and mass and speed, obviously, can’t get there soon enough, so do you have any thoughts on that?

David Tweedie:

A few things we’re working on at General Electric, we’ve been through a, as well as all of industry, a massive supply chain disruption through COVID. As we really try to get back to where we need to be to deliver for our customers, both commercial and military, we’re really trying to attack with lean principles, really trying to drive waste out of the system and focus on SQDC, safety, quality, delivery, cost, in that order, because you’ve got to attack them in that order if you want to get to the ultimate result, and also, driving a culture of continuous improvement, kaizen is the lean term for that. That’s both internally in our own shops, as well as in close partnership with a lot of our tier one suppliers, where we work collaboratively with them to go through week-long kaizen events and try to drive improvements. We’ve seen in our own shops up to a 70% improvement in turnaround time in our HPT blade manufacturing product lines, with some of our suppliers, we’ve seen a 30% improvement in throughput, and that’s just making better use of the assets that you already have.

David Tweedie:

Another approach for us is strong synergies between our commercial technologies and our military technologies. For GE specifically, that’s ceramic-based composites material systems that are lighter weight, more durable, higher performing, and additive manufacturing, 3D printing. We actually did a lot of pioneering technology work with the Air Force Research Laboratory on those technologies, but then our high-volume commercial products have industrialized those, gone through the regulatory hurdles, and are now flying millions of people every day on those technologies that then get fed back into our T901 turboshaft engine for the Army Future Attack Reconnaissance aircraft, as well as the XA100 that we worked in close partnership with the Air Force on, that that can revolutionize and maintain the air dominance function of the Air Force, so that’s as we think of things.

David Tweedie:

And then just one specific example that caught our attention yesterday was Secretary Kendall talking about 1,000 CCA, collaborative combat aircraft, and we need to collectively, industry and the government, think through the problem we’re being asked to solve is the Air Force can’t afford the exquisite capability of the manned platforms and the volume required, so CCA is the solution, but if we do nothing more than just take off the systems that are there to support the pilot, I don’t know that we’re going to break the cost curve enough to get to the volume we’d like,. How do we think through, again, the requirements process through design qualification and even the whole sustainment approach, how do we rethink that collectively, as industry and government, to get to a true low-cost solution, not just a slightly lower cost solution? I don’t have the answers, but that is some of the things we’re trying to think about and want to partner with the Air Force on.

Maj. Gen. Heather Pringle:

Well, and it even brings up the other question of the dual-use technologies that meet military or civilian needs. Do you have any thoughts on that? Would that be a way to better break the cost curve?

David Tweedie:

Absolutely. It speaks right at the heart of are there commercially available alternatives that are good enough or close to good enough that, again, when you think about the industrial cap… But first of all, products that might already be developed, as well as industrial capacity that might already exist, that can be quickly repurposed as different customers have shifting needs over time.

Maj. Gen. Heather Pringle:

Go ahead, please, Andre.

Andre McMillian:

I’ll add, and I think there’s some similarities there with a blended business of having commercial and military. Many folks don’t realize that 75% of our business is actually commercial, so we do think heavily about where do we leverage that technology to include the actual product? As you look at CCA, and the other topic that was brought up yesterday was this blended wing concept regarding the future tanker and what’s the staple of commercial off-the-shelf products that we actually have and they’re actually available, so it actually accelerates the time for insertion and then it also provides an opportunity to partner with their framers from an integration standpoint, so I think there’s great benefits there from an affordable readiness perspective.

Maj. Gen. Heather Pringle:

Any thoughts in the cyber world, is it different?

Brian Morrison:

It is. I’ll disagree with my friends just a tiny bit as it relates to my domain, which is different, admittedly, it’s a different world. In the cybersecurity domain, the notion of just good enough, or almost good enough, to me, is a recipe for mission failure. In the cybersecurity domain specifically, the notion that we can get almost there with commercial crypto is obviously a non-starter for our most critical missions. Of course, there are missions in which you can rely on some commercial crypto because you’ve got short lifetime for the… Data security. Maybe somebody doesn’t like what I’m saying, man.

Maj. Gen. Heather Pringle:

Well, or they really like it,

Brian Morrison:

Or they want me to get off the stage, I don’t know.

Maj. Gen. Heather Pringle:

We have seven minutes.

Brian Morrison:

For our most crucial missions, though, we have to be dealing with gear that only, only the US military and its closest allies have. It’s just our lives depend on it.

Maj. Gen. Heather Pringle:

Well, great thoughts and apparently, it was enlightening. Dun, dun, dun. As we wind down our discussion, let’s finish with, so let’s we’ve assume we’ve transitioned to this wartime posture, we’ve collected our capabilities at scale, our Airmen and Guardians are prepared and ready, so how do we continue to adapt while we’re in the middle of fielding these challenges, addressing the threat, et cetera? That’ll be the last question, then we’ll go to closing comments. David, we’ll start with you.

David Tweedie:

I think in two work streams, I think in the cold conflict of ongoing, as our capabilities evolve, our understanding of our competitors capabilities evolve. I just think the continued close partnership between industry and the military and understanding where those emerging needs are is the way to address that. And then I think in more of the hot conflict, it’s about having the right products at the right time and that ability to surge capacity with very short notice, which I think we’ve all learned is harder than a lot of people anticipated. I think it’s about being prepared and perhaps thinking different from a just in time approach that a lot of us, in both commercial and the military side, have migrated to, to what does a just in case posture look like and how do you set up yourself for that?

Maj. Gen. Heather Pringle:

I think that’s a really good point, because we don’t want to just only plan for up to day one and then wing it after that, we’ve got to be prepared day 2 to day 200. Any thoughts, Andre?

Andre McMillian:

I go back to yesterday, the Chief shared the quote from Italian Air Marshall Giulio Douhet and it certainly resonated with me, and it’s a quote that I’ve shared with the team in previous times. Basically, it says, “Victory smiles upon those who anticipate the change in the character of war, not upon those who adapt themselves after the change occur.” I think what we bring to the fight is our ability and our approach to be able to solve problems with our customer.

Andre McMillian:

As I think back to Francis Pratt and Amos Whitney history, a lot of people don’t realize that they were integral in providing interchangeable parts during the Civil War, and so that’s where the history’s gone. And then in World War II, with the scale that was required for both the Navy and the Army Air Corps, we were able to provide that. Fast forward to even now, and much more, so we’re able to leverage the power of Raytheon Technologies, which is our parent company, and clearly, there is a portfolio of technologies, but then I would also say there’s 180,000 people that are working shoulder-to-shoulder with our customers. When you think about that and our ability to do things together and partner, I think it’s going to be critical as we go forward to be able to adapt in a pure competitive environment.

Maj. Gen. Heather Pringle:

Thanks, Andre. Brian?

Brian Morrison:

I love what you said about partnership. I’ll quibble with your premise a little bit, ma’am. The question was premised on the notion that we will one day move from a peacetime footing to a wartime footing. In my part of the world, ma’am, I believe we are there, and if there’s one thing that really keeps me up at night, I believe we are in hot conflict today in the cyber domain, and I know many of you agree with me. If we are in hot conflict today, I assure you that those two or three peer adversaries are working every day to break our codes, to get inside our sensors, to read our communications, to hear what we’re saying to each other.

Brian Morrison:

If in fact we are in that hot conflict, and I’ll ask you to believe me on that, what I worry about is that we are not having the urgency I think we need. Look, you can tell I’m a passionate person, you can tell that I jump out of bed every day to do what I do, but what I would love to see, from industry and government together, is that agility and urgency that we saw. There was a time, actually, when I was in Iraq, and I think you might have been there, too, at that moment, we were dealing with explosively formed projectile threats to the underbelly of the vehicles. Some of my people who would later be my colleagues at General Dynamics, I had never met them at the time, sat down with the two-star and the two-star said, “Look, soldiers are dying, we need an answer today.”

Brian Morrison:

They sketched out a design for a different hull for the vehicles and they went back to the plant and they started working on it. There was no question about how am I going to get paid for this? Are the requirements lying flat? Do we have all the contract terms? It was urgency to mission, and then we’ll let everything else sort out along the way. Everybody’s got lawyers, everybody’s got contracts, we’ve got to worry about them, but I would love for all of us together to get back to that moment of urgency, because I think we are in a hot war.

Maj. Gen. Heather Pringle:

There is no transition, is what you’re saying. That’s the whole title of this panel and I’m really glad you challenged that, because I think there’s a lot of what you say, there’s a lot of truth in that, and so the question is do we have our gloves off now or do we wait? Any final thoughts, David, closing remarks? We’ll just come down the line.

David Tweedie:

Just thanks for the opportunity. We at GE, we are not at the pointy end of the spear, but we’re really proud of what we do to support and bring in the most capable products to those men and women who are at the pointy end of the spear, because we don’t want them going into a fair fight, we want it to be an unfair fight in their odds. We just are really proud of the small piece we do to make that possible.

Andre McMillian:

Thank you again for the opportunity. I’ll really focus my comments on the folks that are given in uniform. Having come from the uniform and being in a position that served a customer I once was, I’ll share with you that you probably don’t realize that you need just as many people outside of uniform as you do inside a uniform to help you be successful. I would say I’ve taken that path and as I think about both David and Brian, on behalf of all of our industry partners out there, we truly are committed to one cause and one single mission. I think people need to understand it, they need to recognize it. Using the old African proverb, if you want to go fast, go alone, but if you want to go far, go together, and this pure competition will require us to go together.

Maj. Gen. Heather Pringle:

Long way to go. Brian?

Brian Morrison:

Again, thanks for having me. I think sometimes I tend towards scaring people with the vision of the cyber warfare that we’re in today. I guess I’ll leave you with some hopefulness, which is that I know the world is getting more dangerous. I’ve got a four-year-old at home, I worry about the world he’s going to grow up in. At the same time, I am 100% certain that when the chips are down, our soldiers, sailors, Airmen, Marines, and Guardians are invariably the kind of people that rise to the challenge. I want you to know that I get up every day to provide you the tools to meet that challenge and I’m grateful that you are out there meeting that challenge for us, so thank you to all of you. Thank you, ma’am.

Maj. Gen. Heather Pringle:

Thank you all for being here. I’m sure when you walked in and we started talking about transitioning to a wartime posture and you have a lab commander and three industry panelists, you wondered how is this going to be helpful to me? But I think the team has demonstrated that there are a lot of great ideas and that together, we can make it happen, so would you please join me in a round of applause for our great panelists?

Top Enlisted Service Member: We’re Competing with the PLA, Not the Chinese People

Top Enlisted Service Member: We’re Competing with the PLA, Not the Chinese People

The most senior enlisted service member shared a simple strategy for defeating China in a possible conflict March 8.

“Shoot them in the face,” Senior Enlisted Advisor to the Chairman of the Joint Chiefs of Staff Ramón Colón-López said at the AFA Warfare Symposium, when asked to describe in five words how to defeat the People’s Republic of China.

However, Colón-López cautioned that should a war break out, the U.S. military would target the People’s Liberation Army, not the Chinese people themselves.

“It’s the PLA that we’re actually going to go toe-to-toe with,” he said. “Are we going to go ahead and kill all Chinese, because we’re at war with them? Or are we going to go ahead and [follow] the rules of war and fight military-to-military? We start treading very dangerous ground when we generalize how we’re going to carry on the lethal means of military power, which is the national power, but we have to be disciplined in the execution of it.”

A pararescueman and combat veteran, Colón-López recalled several instances where his peers would say “‘we got to go out and kill all Muslims,’” he said. “Now think about that for a second. That is a pretty hateful statement when we’re fighting extremist organizations.”

If a war with China does occur, the hope would be for the U.S. military to fight the PLA until a diplomatic agreement could be reached that would allow both sides to “cohabitate the world,” he said.

China analysts have pointed out in the past that the People’s Liberation Army technically does not defend the Chinese people themselves. Rather, it is the armed wing of the Chinese Communist Party, the country’s governing body. 

“The People’s Liberation Army is not the army of China,” said Brendan Mulvaney, director of the Air Force’s China Aerospace Studies Institute, in an informational video last year. “This is a very important distinction. When the interests of the Chinese Communist Party align with the interest of the people’s republic, then the PLA will protect them. However, when those interests are not aligned, or when they’re in conflict with the party, then the party will use the party’s armed wing, the PLA, to protect the party’s interest.”

That conflict of interest is what led to the 1989 reprisal at Tiananmen Square, Mulvaney said. The Chinese students and citizens who gathered there did not seek to overthrow the Chinese government, the director said. Rather, they wanted a bigger voice in that government.

“They wanted more democracy and a hand in the governance of China,” he said. “This was in no way a threat to the government of the PRC, but it was a direct threat to the Chinese Communist Party because it threatened to weaken their grip on power.”

When the CCP deployed the PLA in response, it killed, injured, or jailed thousands of Chinese citizens, according to the State Department. In his comments at AFA, Colón-López seemed to make the same distinction between the PLA and Chinese people that Mulvaney made.

“We have to be very very careful about generalizing,” said the pararescueman, who received the Bronze Star with Valor for defending a damaged helicopter during a 2004 mission in Afghanistan.

“I said ‘shoot them in the face,’ which is necessary a lot of times in combat,” he said. “But remember that a warrior fights not because he or she hates what’s in front of him, but because he or she loves what they left behind. And I love every single one of you.”

Watch, Read: ‘Advancements in Collaborative Combat Aircraft CONOPs’

Watch, Read: ‘Advancements in Collaborative Combat Aircraft CONOPs’

Leaders from the Air Force and industry—Maj. Gen. R. Scott Jobe, director of plans, programs, and requirements for Air Combat Command; Brig. Gen. Dale R. White, program executive officer for fighters and advanced aircraft; David Alexander, president of the aircraft systems group for General Atomics Aeronautical Systems Inc.; and Mike Benitez, director of product for Shield AI—discussed the importance of capability, affordability and mass for the unmanned aircraft that will fly alongside manned platforms during the ‘Advancements in Collaborative Combat Aircraft CONOPs’ panel on March 8, 2023, at the AFA Warfare Symposium. Dr. Caitlin Lee, senior fellow for the Mitchell’s Institute’s Center for Unmanned and Autonomous Systems moderated the talk. Watch the video or read the transcript below.

Dr. Caitlin Lee:

All right. Hello, everyone. My name is Caitlin Lee. I lead the center for UAV and Autonomy Studies at the Mitchell Institute. We’ve got a great panel assembled here today to talk about the Air Force’s Collaborative Combat Aircraft Program or CCA. As many of you know, this is a program to rapidly field large numbers of autonomous aircraft to team with manned aircraft, and I think this program really has the potential to be a game changer.

If you think about the history of the Air Force, ever since the beginning, the service along with the other joint forces, have sought to seek overmatch over our adversaries. We started out in the early fifties during the Cold War looking to get overmatch over Soviet conventional forces with nuclear weapons. That was our first offset. Then we moved into the seventies and eighties, still looking to get that edge over the Soviets, and we built up some pretty breathtaking capabilities in terms of precision guide ammunitions and stealth, and then we employed them with devastating effect in the Desert Storm.

Now I think the question we have today is what does the third offset actually look like? And I would offer to you, it probably looks like affordable mass. If we can actually build large numbers of relatively low cost CCA, we can begin to offset over 30 years of decline in our capability and capacity in the United States Air Force, and begin to build a combat credible force to deter Russia and most importantly China.

I don’t think this is going to be easy. There’s a lot of technical challenges ahead, and how do we actually team all of our wonderful Airmen with these unmanned systems? These are huge challenges that lay ahead and that’s why I feel really proud and great to know that we have these gentlemen leading the charge and thinking about these problems every day. I think that’s going to be really good for our nation and I’m so glad we have them here today.

So I want to introduce them all to you. So first we have Major General R Scott Jobe who leads plans requirements at Air Combat Command. We have Brigadier General Dale White who leads program executive office for fighters in advanced aircraft at Air Force Lifecycle Management Command. We have Mr. David Alexander, the president of General Atomics Aeronautical Systems, and we have Mr. Mike Benitez, who is director of product at Shield AI.

Thank you gentlemen for being here today. This is going to be a great panel. There’s so much to cover with this DCA topic. It’s so new, and so I’m going to offer that we’ll just hop right into some questions and then we can come back and do some comments at the end, time permitting. So kick it off with General Jobe and General White. I’d like to ask you all about attrition.

So General Brown has said that a war with China could lead to combat losses on the order of World War II. We heard Secretary Kendall yesterday talk about fielding possibly up to 1,000 CCA or more. Could you tell us a little bit about the concept of building a CCA for affordable mass? What does that actually mean and what kind of trade-offs might we actually have to make to get there? Let’s go with General Jobe and then General White.

Maj. Gen. R. Scott Jobe:

Okay. Thanks, Dr. Lee. So first of all, appreciate you putting this panel together, all the work that went behind the scenes to set it all up. So it’s a great event for us, and appreciate all the rest of our panel members showing up this morning too, especially at 0730 hours on the last day of AFA, which is good. So as we embarked on this analysis of the capability gaps that we have looking at trying to provide mass to the battle space, there is going to be a lot of trade space that we work in and through.

I like to say affordable mass, because if we can get a price point that gets what Secretary Kendall talked about, maybe up to 1,000 air vehicles out there at a price point that gives us enough capability to provide effect on the battle space, it’s really a game-changing kind of concept. It doesn’t mean though that this is an attributable type of platform, and that’s been a common misconception. This is about affordable mass.

So as we look through this, we’ve got to make sure that everyone keeps an eye on that. We’re going to reuse these air vehicles, and that the decision for risk and the risk that we will take with these type of capabilities will be at the mission command or at the combined forces air component commander level. It’ll be at the point in time when you’re making a risk decision in combat, not at the industrial side of design, and not at the engineering level of detail. That is where a lot of trade space occurs when it comes to sensors, capabilities we’ll put on it with weaponry and communications and other types of those capabilities and technologies, but not at the risk level. That’s not at the mission command level.

That will be where that decision is made. So the affordable mass concept that in all of our analytics supported by multiple efforts across the Department of the Air Force partnered with other departments in the Department of Defense as well, specifically the Navy, show overwhelmingly that this provides us an overmatch capability and changes our loss exchange ratios dramatically in our favor. So that’s I think my first volley at that question and I’ll let General White pile in.

Brig. Gen. Dale R. White:

No, first of all, thanks as well, Dr. Lee, for putting this together and getting us all organized. This is really fantastic, and thanks for my industry partners being here and everyone getting up very early. And there was no coffee out there this morning, so it was a little rough walking through there. Hey, so first and foremost, I think when you talk overmatch, it’s an effects based discussion and you have to really start right there.

And so General Jobe and I did a panel with you recently and we really kind of refocused a lot of folks on the idea of simply this, right? Affordability is only as good as a capability you can deliver. No matter how cheap it is, if it doesn’t achieve the effect we need in the battle space, then it’s not going to do what we need it to do.

So affordable mass has to be based on affordability and capability and we got to keep that in mind all the time, and that is going to drive that trade. I’ve talked to Secretary Kendall about this and I’ve said it to my leadership, General Richardson, to Secretary Hunter. We have to start thinking through the lens of lethality for the dollar, and we measure what lethality we can achieve and then we look at the affordability aspects of that and we make those trades.

The second piece, and I really want to double down on what General Jobe said, when we started this journey together some time ago, we always knew the decision space was at the mission planning level. We could not force decisions in design that limited the flexibility of the war fighter or the commander for him or her to make that decision at the beginning of any and each mission.

So we will continue to make design decisions and approaches just like that, knowing that we got to provide that flexibility, because that affordable mass, that’s the challenge with it. You’ve got to unleash it, and we got to be able to build platforms and capabilities that allow us to have that flexibility for the commanders on the ground.

Dr. Caitlin Lee:

Got it. No, that makes a lot of sense. And just to dovetail on that discussion a little bit, I want to turn it over to Mr. Alexander. If anyone knows how to build lots of aircraft very quickly in wartime, it’s this man. So I’d like to, based on your experience with Predator and Reaper, can you tell us a little bit about the kinds of challenges we could expect to see if we want to ramp up the industrial base for CCA very quickly, and what we can do to plan for that prior to conflict?

David Alexander:

Thanks Caitlin, and thanks for that nice introduction. So it was really good to hear on the keynote from Secretary Kendall that we’ve heard a number of 1,000. I think that that went around the world twice within one minute, that number, but it’s a key number to have, because if you think about what would be your peak rate, and let’s just say we assume it’s like 200 aircraft a year, and that’s a considerable production rate.

So it’s going to be really important that we can tap into the commercial market that already has production lines that are set up to support this program. The light business jet, so propulsion. We need to make sure that we’ve got a propulsion set up so either they can support that kind of rate or even better maybe have where the airframe can take two different suppliers for propulsion going forward.

So propulsion would be super key and getting into a mature product line will be key, because if you have to redesign engines, we all know that’s billions of dollars that we can’t afford to spend or wait for. I think the second big area would be the airframe and tooling up for that. So there’s obviously the digital thread that everybody’s talking about that, but get into net parts so it’s enough investment in the tooling so that you’re not having a lot of labor coming out the back end. So eliminate the touch labor.

So that’s smart tools, additive manufacturing, thermoplastics. These kind of things will be in introduced. But again, I think the key here is to tap into the commercial market. There’s a lot of capacity out there that can be used and can be used quickly. For systems, those I think there’s pretty healthy production lines on that, and I think you could solve ramping up on that with a lot of long lead procurement, but it means you got to get your designs scored away from the beginning and know what you’re buying.

But things like navigators and radios and data links and things like that, I think pretty straightforward is scale up on those. But again, you got to have the time. So long lead procurement would be good there. General Atomics, we’re very vertically integrated, so we actually build a lot of the avionics ourselves. So for supply chain at the component level, we use vendor managed inventory, VMI, and that allows us to hire a company that buys for everybody, and they’re actually located inside our factory.

So we can buy at scale and we can avoid some of the issues you’ve seen here with supply chains on components like electrical components, connectors, wiring and such. Sensors and payloads, I think, are not a challenge right now. I think we’re still in that definition stage, and maybe some of that’ll come in phases on the program. So maybe that’s something we’re going to have to keep an eye on. But that will be a challenge depending on what sensors go with what platform, whether it’s a shooter or just a sensor or just doing ISR on these CCAs.

And then from day one, I mean you got to have the facilities in place for open production and then classified production, so closed areas for production. And then from day one we’re you’re going to need dedicated airports, dedicated airspace and dedicated areas to perform qualification testing. We can’t be waiting for those items when we’re going out. So I think just quick in summary would be tap into the commercial space and use that capacity that’s out there.

Dr. Caitlin Lee:

That’s excellent. Thank you, Mr. Alexander. And it’s a great point about the commercial sector coming into this space more, companies that may not have even been associated with defense traditionally playing more of a role, especially on the artificial intelligence side, which is what we’re going to need to build these aircraft that are going to team up with their manned counterparts.

So the next question I want to do is to kick over with Mr. Benitez over here, talk about autonomy a little bit. So can you tell us a little bit about Shield AI? How do you guys think about autonomy as it relates to collaborative combat aircraft? What’s the art of the possible today with pairing and then what’s the technological readiness? How long is it going to take us to get to a world where we see the swarms we see in science fiction? No pressure.

Mike Benitez:

Oh it’s on now. Thanks. I’m the only one with the wired mic, which is why I’m the artificial intelligence company rep. I just want to point that out. Thanks for people who decided, I know there was a choice to make this morning. You can either sit here and listen to us or you could have gone to the NGAD conversation. So you’re here. Thank you. I think this is going to be a better engagement personally. I’m biased. So yeah, back to the beginning, before I answer that, I just want to highlight, we talked about affordable mass. I think there’s a word missing there, which is affordable, capable mass.

Dr. Caitlin Lee:

Yes, agree.

Mike Benitez:

Because we can have 1,000 drones and send them out, but if they’re not capable, it really doesn’t matter. And to get that capability at scale, you have to do something different. And that’s where the conversation about autonomy starts to come into play. Because as you know, the unmanned remotely piloted fleet that we have today is certainly manpower intensive. It’s not delivered on the promise of the past two and a half generations of promise. We’re going to take the man out of the cockpit, we’re going to save on manpower.

Turns out it’s about 4X to 5X more people to operate unmanned aircraft today. And we can’t do that with 1,000 CCAs. So how do we apply autonomy in the best use case possible? You asked about the state of autonomy. So to answer that, I’ll give you an analogy. So let’s talk about the state of AI. Who’s heard of generative pretext training? Has anyone ever heard of that? Okay, there’s a couple hands in there.

So here’s what it is. It’s you’re going to use basically stack types of artificial intelligence, so some unsupervised learning, which is a type of machine learning, which basically takes a whole bunch of data, tries to make sense of it, and then it applies that through a couple other filters. There’s supervised learning, which is another type of machine learning, and that basically applies some data labeling and then you apply some other stuff to it, some magic sauce, and at the end you’re getting some generative AI. Okay?

And I tell you that to ask you the next question. Who’s heard of ChatGPT? I just described what ChatGPT is. That is what the GPT stands for. It is generative pre-training transformer. So the history of ChatGPT, I think, draws a very, very clean parallel to the state of advancements of AI, because yes, it’s text, there’s some other stuff going on, but that is really, it marks with everything going on in the industry right now, whether it’s autonomy or applying AI from new for air or generating pictures that are funny, it’s all kind of advancing at the same rate.

It’s a common tech baseline. And there’s a few enablers for that we can talk about later. But if you go back to Open AI is the name of the company. So GPT, the first GPT came out in 2018, GPT1. That is when Shield AI deployed AI into combat on a quad copter. So we have TL9 AI deployed in combat since 2018 when GPT, the first GPT was created. One year later, GPT2 came out. It was 10 times the size of GPT1.

Two years after that, GPT3 came out, it was 10 times the size of GPT2. It has 175 billion parameters. That was modified and then turned into a chat bot. And that’s what you guys hear about ChatGPT. So 12 months ago, you probably never heard of GPT. Now everyone’s heard of GPT. GPT4 will come out in about 12 months. It has one trillion parameters. That is how fast the state of artificial intelligence is advancing.

So we talk about the clips of TRL advancement and industry is putting a ton of money. Our company is putting billions of dollars into advancing this because we believe it’s the right bet to make. And the reason is you go back to cost of attrition. Sorry kind of bouncing around. That’s okay. Cost at attrition is you do campaign analysis. Some guy named John Void back in the eighties, he did air campaign analysis and some of it still rings true today, which is 1%.

1% attrition is what you can sustain to continue an air campaign without prohibitive interference. And those two words matter because prohibitive interference is literally the definition of air superiority. So if we want to gain and maintain air superiority, we have to have a force that can absorb attrition at or below a 1% level, but, and this is the but, this is where the CCAs come in, is that attrition kind of comprises a few things.

It’s losses, it’s imposition and then it’s also reconstitution. So in World War II, the eighth Air Force, General Kelly, you’re a big fan of history. So the eighth Air Force absorbed 10% attrition a month for 24 straight months. How were they able to do that? Well, it’s because they were producing 1,000 bombers a month, so they had a reconstitution capacity.

And so when we talk about affordable mass at scale that’s capable, you have to have not only the means to produce them, but the means to continually and rapidly produce them. So that’s the part I wanted to answer from Dave, from General Thomas. As far as what we’re doing and what we could do, we talk about man to man teaming. Secretary Kendall had some ratios. We’ve heard three to one, two to one, five to one. I could do this, I could do that.

That’s not the problem. It’s not a technology problem. What we have to do is we need to do the analysis to make sure we’re solving the right problem. So what we don’t want to do in five years from now is sit here on a panel and talk about the should would’ve, could haves. Man, there is what we can do from the industry. There’s what we could do for policy potentially or budgeting. And then there’s what we will end up doing or maybe doing. We’ll see.

And so the analysis of that is extremely important. And when we back it up, we’re on the third day of this panel. And the theme of this thing is [inaudible 00:18:28] deter fight win? We like to talk about winning. We like to talk about fighting to win. There’s a lot of boost downstairs to talk about here are the things that help you fight the win or get you to the fight or sustain the fight. But I don’t want to fight. I don’t think anyone ultimately wants to go to war.

We want to prevent war and deterrence and how do you deter? And that gets in the conversation of what capabilities will I invest in with CCAs that induce or inject that fear, uncertainty and doubt calculus that can supercharge deterrents in the near term. And that’s really what we’re talking about with CCA’s autonomy. Again, it’s not a technology problem, there’s a lot of stuff we can do with it. We just got to make sure that we pick the right problem and we resource it and finally execute.

Dr. Caitlin Lee:

Thanks Mike. A theme that I’m hearing from this panel is, yes, affordable mass, but it’s got to be the right kind. You got to have the capability to, and it really is a balance, and I think that’ll be especially important when we think about deterrence in the Indo-Pacific Theater. So thanks for tying that together, Mike. General White, to pick up a little bit on the autonomy theme a little more, could you talk a bit about the Air Force’s approach to how we integrate autonomy into CCA? How it will look in the beginning and what the sort of end state you ultimately envision might be?

Brig. Gen. Dale R. White:

Well, certainly. First I’ll start by saying if ChatGPT were around when I was in college, I probably would’ve done a little better, for the record. Man, things have changed. So yeah, so I think first of all, in light of what Mike said, and he’s adding words to phrases, so I think I’m going to do that as well. Can’t be one-upped, right? I think when you think about autonomy, it’s got to be mission trusted autonomy. It’s missionizing trusted autonomy. That is what we have to do.

And it goes back to exactly what Mike said. We’ve got to bound the problem, because the technology is already there. It exists today. And in many cases I would submit to you that there are companies out there that have already started perfecting some of this delivering packages and things of that nature. So it is there. It’s how we bound that problem. And I will tell you how we’re going to do that.

We’re going to have a space where we build autonomy off of a basic architecture, a common architecture. And why that’s important is simply this. You used the term crawl, walk, run. I will tell you we’ve been crawling and almost standing for a while.

Dr. Caitlin Lee:

Good to hear.

Brig. Gen. Dale R. White:

I think that industry would-

Mike Benitez:

I agree.

Brig. Gen. Dale R. White:

Yeah, and I think I’ll go one further. We’ve been flying this with Skyborg and many other platforms. We still have XQ58s flying down in Eglin right now today. So I think having that common architecture, building on top of that architecture, and why that is important, that walk and run piece, is because then you have to bring in things from a mission perspective that most people don’t think about.

Interoperability, right, because we’re not doing this just for us. We’re doing this for a joint fight, our joint partners, our international partners, and so we have to have that common architecture. And so what the walk and run looks like is you take the autonomy that we have, you build it on top of a common architecture that is government owned. I think that’s critically important. We need that common architecture because that way we can make this a platform-agnostic discussion, because if you build autonomy each time you filled the new platform, we’ve gone about this all wrong.

And then the next piece is, is I think, and Mike and I think you and I have had this conversation, there’s also a culture aspect of this in the walk and run piece. And that culture aspect is simply this, and I couldn’t say it as well as General Kelly said at the last AFA, we need to get this capability in the hands of the captains and we need to let them lead us through this and we need to iterate as a function of time.

So we bound the problem early, we know how to build the architecture piece. We have the technology, we get it in the hands of the captains, let it iterate early and continue to build upon that. And I think where we’re going to have a challenge, and I think this is where General Jobe and I spend some time, and I’ll invite him to pile on here, is where you bound that problem.

What are those mission sets? How can we keep that problem low enough so that we can field something quickly and then we just continue to iterate. I don’t want anyone to gloss over the trusted autonomy piece. Trust is key. Trust is going to be key. And so the only way to break down probably that part of that culture piece is again to get it in the hands of the captains early and let them iterate on it.

Dr. Caitlin Lee:

You want to pile on there, sir?

Maj. Gen. R. Scott Jobe:

Just a couple of comments. I think that as we’ve been on this journey for a couple of years for these combat collaborative aircraft, we’re approaching this from a different perspective, and it gets after what General White talked about. We’re going to get prototypes rapidly to the field, but we’re also going to focus on that bounding condition problem. So we’re going to focus on very specific mission sets. We’re going to start with the air fight.

So we’re going to go do air-to-air kind of capabilities. Then we’re going to start working on surface targets, maritime and others. But we’re going to be very focused and we’re not going to take the very long developmental test, operational test approach to things. We’re going to be very iterative. We’re going to be really rapid and we’re going to do that by going prototyping and we’re going to iterate with both industry and the government side of things.

So we’re going to bound the mission set closely, but then we’re going to iterate rapidly through this, and we’re going to do that at places like Nellis where you get unique capabilities with unique Airmen and Guardians that can only do the kinds of things that they know how to do. And that’s how we’re going to go fast.

Brig. Gen. Dale R. White:

And I’ll add on it. I think that John Brown said yesterday, unleash the Airmen. That’s where this is going to happen. And if I were an adversary and I was watching this panel right now, I would be concerned because it’s not going to take us that long to figure this out. We’ve already come such a long way. And the mere fact that industry is sitting here with me saying, “Yeah, we’ve already kind of cracked the code on some of this,” it’s really just how we task organize and get after it. And we got a plan to do that knowing that we’re going at it in a different way. I don’t think, Caitlin, you’ve ever seen General Jobe and I not together talking about this.

Dr. Caitlin Lee:

Yeah, it’s true.

Brig. Gen. Dale R. White:

Because we are that closely aligned on getting this done.

Dr. Caitlin Lee:

Awesome. And I want to build on the point that General Jobe you just made where part of this is really define your problem carefully and bound that mission set. Could you drill down a little for us, sir, on the kinds of missions? When you look at air-to-air what do you actually see the CCA doing? What kind of payload sensors do they need? Are they missile trucks? Are they ISR? Where do we go first?

Maj. Gen. R. Scott Jobe:

Okay, so this is the big one. We’re going to focus on offensive counter air first. Both sweep and escort missions. Doctrinal, nothing new there, but we’re going to focus on that. But the unique thing that CCAs bring to the fight is the ability to do fire and maneuver in a different way. And you accept risk in a different way because you’re going to have different tactics, techniques and procedures. Traditionally when we do air-to-air and we’re walling up a four ship of fighters and we’re going at the enemy, you’re constrained by that mutual support. You’re constrained by your formations.

With the combat collaborative aircraft, you’re not necessarily constrained by that because you can make different risk decisions. As you enter a threat envelope, I can come in from a different axis or I can accept a different level of risk even though I’m in a threat envelope. So we’re going to focus on that first. Certainly kinetic effects are going to be one of our high priorities.

So we will have weaponry that can reach out and touch the enemy and provide lethal effects, but it’s not constrained by that only. It’s also going to include sensor packages so we can sense the environment from an air moving target indicator kind of perspective. Multi spectrum is going to be part of the play as well. And then in the electromagnetic spectrum, that’s also going to be capabilities.

If we built this architecture that General White talked about, we have the ability to now kind of plug and play, if you will, for what the mission needs and what the requirements of the day are. The behaviors of the autonomous capability that we have out there in the early days will be kind of fairly deliberate. It will be algorithmic, it won’t be like having a human in an airplane flying it. It’s not going to be that advanced, but it’s going to provide us the capabilities we need.

We’re going to be able to go to a cap, we’re going to be able to orbit, we’re going to be able to patrol an area, rooting, fuel calculations, all those kind of things, avoid areas where you don’t want to go, go to areas where you do need to go. Those are going to be very deliberate processes and we’re pretty confident in that. We’ve been looking at this for a very long time. We know the tech is there and we’re focused on those mission sets, if that got after. I don’t know if you had anything else you want?

Brig. Gen. Dale R. White:

No, I think you got it spot on. It’s spending the time early on, because we don’t have a technology problem like we’ve reiterated over and over again. And so the other part of this is in terms of coming at it differently, having industry with us every step of the way, that’s a critical piece. This isn’t one of those times where because of the challenges in trying to get the problem definition exactly right, this isn’t a time where you go in into a vault somewhere, write a requirement that goes over to the acquisition community and then creates an RFP and then we send it out and we wait for a response.

It’s not how we did it, and that’s not how we’re going to do it. This is an iterative journey with us and industry in the boat together rowing. And the reconstitution piece is critically important because I remind people often, right, it’s not militaries that go to war, it’s nations that go to war, and that reconstitution piece is going to be a critical part of that.

And so making sure we have that demand signal there and making sure industry is in that iterative circle with us all the time. And even talking about, hey, as we start bounding what the mission sets are, we’ve had those discussions about, “Well, did you think about this or did you think about this?” Because industry, they’ve got a lot of game here and they’ve been exercising that game quite a while in different spaces. I mean billions and billions of dollars across multiple AI companies. I mean it’s very clear that we have that piece cornered.

Maj. Gen. R. Scott Jobe:

Just one last point. As we’re iterating with industry and working on attributes and requirements that are not isolated and stove piped, we also started this journey with logistics and sustainment right at the forefront of everything that we’re doing, how we’re organizing, how we plan to sustain the fight in the field so we can mission generate and provide that mass. This is a right from the beginning, we bake this in for how we’re going to sustain this capability into the fight. So it’s pretty critical that we highlight that.

Dr. Caitlin Lee:

That’s awesome. It’s great to hear you say that, sir. Just one clarifying point, you and General White kind of alluded to this, in the beginning you talked about the Airmen and mission planning and how giving them options is really important, creating flexibility for the Airmen. And then you also mentioned thinking about the counter air mission. Sure, you need all kinds of payloads and sensors potentially to do that. Is modularity or dis-aggregating these capabilities across larger numbers of CCAs part of the plan here or do you see any one CCA having organic capability all the time? So if you could describe how much modularity.

Brig. Gen. Dale R. White:

Yeah, I think from my perspective we’ve given this a lot of thought. The modularity piece is absolutely critical because look, one of the things that I think I’ve recently told the secretary and we had this conversation, we could easily overreach here and make this a 15 or 20-year development program. We’re really good at that, right?

Dr. Caitlin Lee:

Yes.

Brig. Gen. Dale R. White:

And so we’ve given thoughtful approach to how we do this, making sure that, again, that flexibility for the commander, him or her on the ground at the time of mission planning is going to be key. And the only way we do that is have some form of modularity, because Gerald Jobe is right, we’re not building with attritability as the focal point. That should still be something that the commander that she or should have on the ground to say, “Okay, this is going to be a little more risky. We’re going to press this thing through and if it doesn’t come back, I got it. So I’m probably not going to put this sensor on there, I’m probably not going to do.” So again, it’s that flexibility piece. So yeah, we do see that as a key component.

Dr. Caitlin Lee:

Got it, got it. Okay. All right. Well was this is one more for you two here. And this is about operational experimentation. So everyone on the panel panel has talked about how important it is to get these CCA out there quickly. And so could you talk to us a little bit about what we need to do to shake out the CCA technology, get it into the hands of Airmen? What does that actually look like? How soon can we do it? Where can we do it? What dot mill PF, kind of, if you could walk us through that, General Jobe and General White.

Maj. Gen. R. Scott Jobe:

Yeah, that’s a great question. So we’ve been working on our concept of operations and concept of employment and how we plan on organized training and equip this capability. One of the best ways to figure out how to employ from a blue side of things, if you will, so having a CCA on our side is actually to go out and fight against one. So we’re going to do both of those because there’s five essential pillars of autonomous collaborative platforms that CCA is one of them.

So the combat collaborative aircraft is one of those pillars where we’re going to go out and we’re going to fight against these aircraft. So go take a Raptor, go fight against the CCA and then bring that CCA right back over onto the Raptor side as an example. F-35 is our cornerstone fighter. We know we’re going to partner with F-35s in mass. This is how we’re going to provide mass to the fight. It’s the most prolific fighter we’re going to have. It’s highly capable.

And so we’re going to go through those type of exercises. National airspace is going to be a challenge. So we’re going to need help from a policy perspective across the inter-agency. But places like Nellis where we have restricted airspace, we know we’re going to fly in areas like that early on as we kind of develop these tactics, techniques and procedures.

Brig. Gen. Dale R. White:

And I’ll pile a little bit there. One example I will give you, and I saw General [inaudible 00:31:51] come in earlier, there’s all kinds of aspects you have to address. I’ll give you an example I think is really interesting, because I had not really thought of this until the team had come to me. So we have a couple of XQ58s down at Eglin, and one of the things we’re doing is we’re practicing on how you would exercise these on a range. So we’re exercising the range to get ready for the type of tests we’re going to do in this environment, understanding how these would operate.

So we’re doing a lot of that right now. And so as we continue to go through the process that is prototyping and moving forward and things of that nature, we’ll be pushing more and more capabilities out, get into the hands of the Airmens and have them help us steer the outcome here. And so we’ve got a good speed to ramp on how we’re going to do that.

Dr. Caitlin Lee:

Awesome. Kind of building on that comment about needing that range space and needing to do this testing quickly and efficiently, I want to turn it over to Mr. Alexander and Mr. Benitez to talk a little bit about the industry perspective on what you guys actually need to go fast on developmental and operational testing. We’ll start with Mr. Alexander.

David Alexander:

Yeah, so just springboarding off what you were saying, doing a lot of iteration and a lot of development of AI and autonomy, this requires a lot of revisions going forward. So you can’t get hung up in a program that’s going to have to go through an airworthiness panel every time you want to release a new set of autonomy or a new algorithm. So I think what we had on our Skyborg program with the MQ20 is to create an airworthiness kind of checkpoint from the autonomy engine so that you don’t do dumb things basically.

And you can make it such that you don’t have to go through a whole process, and if you get a red risk, you got to run up to the head of acquisition and get it signed off. These are the types of things you have got to avoid. One, not to lose your asset, but just to be able to move quick. So you need that firewall. That firewall needs to say, “Nah, yeah, I hear what you just said, but I’m not going to do it, because we don’t fly upside down yet.” That kind of thing.

We don’t fly over LAX. So that geofencing and flight envelope checking, those kind of things I think are something new. And that’s what we’ve added the Skyborg. And it’ll allow you to go quick, allow you to iterate and move quicker. But we cannot get hung up every time we want a new algorithm to run it through and their worthiness panel, it’ll just slow us down way, way, way too much.

Dr. Caitlin Lee:

Got it. Mr. Benitez, you want to weigh in on this one?

Mike Benitez:

Sure. Well, we’re a software company so we don’t have airplanes, so that’s a problem. So we are dependent on a vehicle to actually do live fly experimentation. And in the CCA, if we say that CCA is your group five UASs in this conversation, they may not be, but let’s say they are, there’s really only a few people in the United States who even have group five vehicles that can host autonomy to do experimentation. You can count them on one hand, that’s it.

The X62, the Vista, the modified F-16, the Edwards, we flew on it in December. It’s a great aircraft. There’s only one in the whole world, one. So we’re kind of a slave to that platform. As we move to the Valkyrie in a few months, we’ll be flying autonomy on the Valkyrie down at Eglin as part of an Air Force program. That’s great but there’s only two of them. And in your launch and recovery reconstitution, we still have to flush out some of that to do what we call fly fix fly. So we want fly, iterate, fly again.

So we really have access problems to platforms, and to the point about dot mill PFP and logistics and how we bid this down, that’s not our problem as a company, but what I can tell you is that without the aircraft in the hands of the captains live flying it, it’s really just an academic exercise. You’re not really actually getting data and testing hypothesis because you don’t have anything to test it against.

So until we have different types of aircraft at different locations doing different things with different types of force compositions, it’s like the lead wing concept. For years the Air Force experimented with different constructs and different locations doing different things to see what those attributes might look like. So that’s where I think we’re going to learn a lot.

I can tell you we’ve done a lot of live fly of AI over the years on a lot of different platforms. And I can tell you that going from an R and D program that does some stuff in simulation and putting something and taking it into the air and flying with a human internet is orders of magnitude difference in difficulty. There is a lot of learning that is going to happen across industry. We learn something every time. It’s part of the process.

It’s why we have flight tests, we have a test community, we don’t just build it and give it to the operator. So I think that is going to be a really significant challenge. And the other part of that, just real quick then I’ll hand it off, is that there’s another step that autonomy actually injects into this entire process that everyone’s kind of ignoring right now.

We can experiment, we can do operational experimentation, it’s great, but we actually want to get something to the war fire. There is a process that that autonomy has to go through that is extremely nascent. And so it’s an internal validation verification process that AI companies do with their autonomy product. But there also has to be an independent validation verification, and that is a OSD requirement.

There is actually no requirements written for that, by the way. It’s just a requirement that we do it. So there’s not really a cross-functional team stood up or someone that we’ve actually spoken to in the Air Force, an OSD that can clearly articulate what a V and V process for autonomy for CCAs looks like. And that is going to be a huge problem.

Brig. Gen. Dale R. White:

So I want to pile onto that real quick for a second, because you said something that was important. I joked earlier about how long it takes us to do development. It’s obviously much, much less than that, but there’s a point here about development piece I think that we need to bring out, and you just said it, Mike. We have to fail forward here. We don’t want to go into an extended development pattern. Our EMD programs can be five to 70 years, whatever the number is. But in this particular case, it’s that iteration piece, it’s the idea of failing forward.

I think that is going to be a critical part of this process. And I think that you guys have already done a lot of that work. Some of the other companies I’ve worked with have seen, they’ve had the challenges, they’ve had the mistakes and so forth. If we learn how to fail forward, capture that and then immediately continue to move forward, what that allows us to do is trade off iteration for extended development timelines. There is a time and place for lengthy developments. I think this is one where iteration is going to be the one that’s going to serve us well.

Dr. Caitlin Lee:

Yeah, thank you.

Maj. Gen. R. Scott Jobe:

And I’m going to pile on one last bit. So much like the rest of the NGAD family of systems, next generation air dominant family of systems, the model-based system engineering, the digital threads that we’re baking in at the beginning have already enabled us to go into the virtual environment so that we can do iteration at scale in virtual environment, which you can do much, much faster in many cases than you can do in the live fly events.

And so our validation and verification process that we’re going to go through is going to have live fly events that we get data points off of and we’re going to take that data, we’re going to bring it back in, we’re going to adjust our algorithms, we’re going to adjust even the TTP and operational perspective. Then we’re going to stick it in the virtual environment and we’re going to go through that iteration process multiple times. So what you see flying on the range is not all the activity. There’s a lot that’s going on behind the scenes.

Dr. Caitlin Lee:

Got it. And I want to do one quick lightning round before we wrap up. And this is just going to be, Mike, you summed it up really well when you talked about why are we doing all this? Because we want to bolster our deterrence. And so if we look to the Indo-Pacific, what is the one thing I want each of you to say that we need to do to get these CCAs fielded rapidly west of the international dateline? General Jobe, go.

Maj. Gen. R. Scott Jobe:

Don’t give up.

Dr. Caitlin Lee:

All right.

Brig. Gen. Dale R. White:

Early user involvement.

David Alexander:

Agile combat employment.

Mike Benitez:

Fix two, four letter words, ITAR and MTCR.

Dr. Caitlin Lee:

Awesome. Yes, amen. All right. Thank you all so much for being here today. Thank you to this awesome panel. Really appreciate your time. Have a great aerospace power kind of day.

Watch, Read: ‘Global Strike’

Watch, Read: ‘Global Strike’

As the Air Force works to modernize its legs of the nuclear triad with the B-21 Raider and the Sentinel ICBM, industry experts including Willy Andersen, vice president of multi domain-special programs and capabilities at Boeing’s Phantom Works; Jon Norman, vice president of air power, requirements and capabilities at Raytheon; and Doug Young, vice president and general manager for strike programs for Northrop Grumman, talked about how they’re helping with the mammoth effort in a panel discussion on March 8, 2023. Retired Maj. Gen. Doug Raaberg, executive vice president of AFA moderated. Watch the video or read the transcript below.

Maj. Gen. Doug Raaberg, USAF (Ret.):

Well, good morning everyone. I’m Doug Raaberg, Executive Vice President of your Air and Space Forces’ Association. Definitely thank you for joining us this morning to discuss a very important operational imperative that is really near and dear to my heart, Global Strike. Please welcome to the stage and hold your applause till the end, my contestants. To my left, Mr. Willy Andersen, Vice President of Boeing’s Multi-Domain special programs and capabilities, Phantom Works, Major General Jon “Stormin” Norman, Vice President of Raytheon’s Air Power Requirements and Capabilities, and to my far left Mr. Doug Young, Vice President and General Manager of Northrop Grumman’s Strike Programs. Let’s give them a big round of applause, please

Let me help set the scene. Secretary Kendall described the Global Strike Initiative as being similar to the next generation air dominance, which identifies all of the components of the B-21 Raider family of systems, including the potential use of more affordable uncured autonomous combat aircraft. Of the technologies are there now to introduce uncured platforms in this systems of systems context, but the most cost-effective approach and the operational concepts for this compliment to crude Global Strike capabilities have to be analyzed and defined. If you go to the Air and Space Forces magazine, go right to the operational imperatives, that’s quoted right out of the magazine. Let’s remember that in the end, Global Strike is a human endeavor, yet the backbone of our nation’s success relies on the innovation and ingenuity of our industrial partners to deliver the transformational capabilities to the war fighters.

So on that note, Doug, let me fire away with a question. I know… And by the way, this is a spoiler alert, we will not be talking classified in this room. So Doug, set the scene for us. In his remarks at the B-21 rollout, and thank you for the invite. This last December, Secretary of Defense, Lloyd Austin commented that this is deterrence done right. He was in fact alluding to a model acquisition program that continues to adhere to cost, schedule and performance. Even last week, the House Armed Services Committee ranking member openly praised the B-21 program. Obviously you were at the rollout. So what has made Northrop Grumman’s B-21 program a success?

Doug Young:

Well, thanks for the question, Doug. And yeah, every day, it’s a big challenge, but so far, so good and a lot ahead of us and I’ll talk about that in a moment. First thing I wanted to do is kind of just step back for a moment, at the strike division at Northrop, we focus on systems and technologies that are dealing with the highly contested environment. So the two programs I can talk about today around that are for Global Strike and I’d like to just restate a quote from yesterday’s talk from General Bustier, which many of you I’m sure we’re at. But just to focus on these two programs, it’s about range, access, and payload to deliver disruptive effects in a contested environment with the mass and the lethality to win against a peer adversary. So with that, our focus on the B-2 first off, which is in this division and part of Northrop’s legacy around this kind of capability has been all around modernization and making that platform continue to be relevant and effective.

So we focus on comms and bombs if you will. So last year we were able to alter the architecture on that system in order to be able to segregate the mission systems from the flight systems to allow us to more rapidly upgrade and add mission capability, weapons and comms. We also have done a lot of work around low observables to continue to refine them, make them more maintainable and more effective for the mission. And on the weapons side, recently we qualified the [inaudible 00:04:42] last year for B2 and there are a number of other missiles or weapons in the pipeline. So that’s kind of the B2, which really until B-21 comes online in numbers is what we’ve got for this mission. So now switching over to B-21 and referencing back to the rollout, that was a great day for the company, for the country and for our war fighters, to really get out and have a visible symbol of what the country and what the industry is doing to support the mission for deterrence.

So team was very proud of that accomplishment, but we moved the airplane out of there that night and at five in the morning we were at it again starting to test the airplane. So no rest for the weary. So around B-21 we are testing that airplane, we’re doing ground test, we’re getting ready to go fly it sometime later this year and first flight’s going to be a big deal. But an even bigger deal really is to focus on the second flight because we want to make sure when we fly that airplane that it is not something we’re going to have to work on for another two months before we go fly it again. We want to get into a very productive flight test program. So part of that is all around making the trade-offs in the near term on schedule in order to implement things that we know we have to fix so that we can get through a good flight test program. So the second flight’s important too, and obviously the subsequent.

We’re also ramping up in production, getting ready for that. We rec recently received advanced procurement for the first lot. We’re focused on sustainment because when we get to the main operating base with that first aircraft, everything’s got to be in place, spares training, all the documentation, all the things required in order to allow the war fighter to support that aircraft and bring capability online quickly. So that’s another big focus of the program at the same time as production getting through AMD and into flight test. So with that, that’s kind of a summary of where we’re at. To finally answer your question, and I apologize for the segue, but I just thought a little background will be good. So what is working well? So it’s really starts with the partnership. The partnership we have on this program and it really is built on about 15 years of working closely with the RCO and developing that relationship, that relationship of trust, mutual accountability, transparency is really what provides the resilience for us to be able to get through the challenges that we see every day. I mean, these are hard programs.

We all know that we’ve all been there and this one is no different. So that elasticity has done us well and has allowed us to execute on a concept that we call active contract management. We don’t play by any different rules than anybody else. We work inside the DOD 5,000 system like everyone else. But the way in which we’ve applied resources to address risks early on the program through active contract mechanisms has allowed us to address those risks quickly and also address things that we see on the horizon that have newly presented themselves that if we address them early will help us have a better system, bring it online sooner and have it be more sustainable and operationally effective. So that’s a key element. We also have worked hard to make sure the first aircraft is very representative of the production aircraft. They’re essentially identical, so we have haven’t cut any corners on that first aircraft. I’ve read comments in the press about a prototype or whatever, it’s not what it is. We’re building the first aircraft, just like the first production aircraft, same processes, same people, same tools, same hardware.

So that’s been a challenge because oftentimes on a first article you like to be streamlined and do a lot of handwork and so on. We’ve avoided that in order to ensure that we’re really burning down the risk early. Again, it’s that moving risk left approach that we’ve used in order to be effective. Finally, on digital and open architectures, the program wasn’t born digital when it started eight years ago. It was not… I’ll call it digital in the way we talk about it today, but we moved quickly into that and that was with help with the RCO in many areas, but also just leveraging commercial tools that are now available. So the way I would describe digital is in three elements of physical, functional and operational. On the physical side, it’s all about the engineering models. An example there would be we just did a regional structural test of the airframe to ensure it was ready for flight and we were within 5 percent to the good of our models, of our predictions.

So the fidelity of that model was exceptional and it allowed us to really move quickly and address any risk that might have been there before we went to flight. As well in the physical area in the factory, the use of virtual reality, the VER use of hollow lenses to be able to see invisibly through the structure and be able to install elements for the mechanics and make it easier for them to perform their task as well as ultimately into sustainment, being able to use those same tools. Those are commercially available now we’ve adapted them into this SAP environment and now apply them in a production environment and ultimately sustainment. On the capability side, it’s about agile software and DevOps software. Many of you have heard about DevOps and it’s really about model-based systems engineering and implementing rapid cycles of software development in line with those models in order to bring capabilities online efficiently and quickly and make changes as required as you discover things.

Ultimately that will serve us well in the field because we’ll be able to make changes rapidly because we all know the threat is changing more rapidly every day and being able to alter software quickly is important. Finally, operationally, migrating to the cloud is a fundamental now part of the program in order to manage the amounts of data that are out there for not only sustainment but mission data that allows us to be more transportable around the globe as we deploy and go forward with B-21s in the operational context. So migration to a cloud, again another commercial thing that’s been around for a long time, but doing it a weapon system level, multi-level security is a challenge. Just like in DevOps, it’s again, it’s doing it a weapon system grade implementation has been the challenge we’ve overcome, which we’re very pleased with and software’s going very well on the program.

In the airplane world, sometimes you say, airplane’s waiting for the software. Well, in this case, the software’s going to be waiting for the airplane, so software’s going well. We’re really happy about that. Finally, OMS and all that in terms of what’s working is the requirements have been very stable. So from an acquisition perspective, we’ve been working to the same set of KPP since 2014, and in fact one of those KPPs was to have an open mission system architecture. So stable requirements has been a big reason why we’ve been successful. Thanks, Doug.

Maj. Gen. Doug Raaberg, USAF (Ret.):

That’s awesome. Especially as the B-2 commander, I wish the B-2 could have uploaded the software software like a Tesla in your garage and be the most capable going out to fight. And Willy, I’m going to turn to you because this is important. Yesterday, the Global Strike commander, General Bussiere really unveiled not only command perspectives, but he, he’s really bridging the full operational capability of current systems and about nine modernization programs to the future and getting them to FOC of the future. So let’s talk about that Systems. No doubt, modernizing the Global Strike enterprise is vital for our national security posture. So I’d like to take it from a vantage, your vantage point at the Boeing Phantom Works. What do you see as the most critical enablers to the long range strike mission?

Willy Andersen:

Thank you very much for the question and General thank you for hosting this. It’s an esteemed honored to be with you in these other two fine gentlemen. Well, first off, from a Phantom Work standpoint, the portfolio that I oversee is one of advanced materials, advanced mission systems, including self-protect, advanced command and control, and we’re applying those in very innovative ways for new platforms as well as upgrades to existing ones. In my past military career, I was a flight tester on a B-2. So B-2 is near and dear to my heart, congratulations to you and your team for B-21. I did a little work with them. It’s nice to see that platform out there. When we did the B-2, and the platforms of that generation, it was about this individual survivability of the platform, the employment of the platform. It was all about the singular mission aspects of that platform.

Now in the family of systems, we’re looking at essentially ecosystems, ecosystems of the gen-six fighter ecosystems of the B-21. And the ecosystem is it enhances your mission effectiveness, it enhances your survivability, and as the Secretary was saying in his opening remarks, it allows us to buy down our mission risk and provides a bunch of different levers. So in terms of critical enablers, it’s not trivial to build an airplane, but we know how to do that. Okay, we got a lot of success in history in doing that. The complexity now is okay, you’re not just building an airplane, you’re working with other partners, other industry partners and folks to create an ecosystem that works well together. It’s tightly coupled in a highly contested environment of maybe the employment for Global Strike. The coupling of capabilities of other platforms of support, if you will, has to be very, very tight. There can’t be a lot of margin for error.

The timing and so forth is very, very critical. So now you get into CCAs, you’re getting into common command and control. The work that General Cropsey is doing in JADC2 is going to be absolutely crucial if this is going to be successful, that element absolutely has to be successful. And now you’re coupling in capabilities from space in ways we haven’t done before. So that’s a key enabler. And then I think the last main key enabler is Global Strike, deep strike, long range, you need fuel. Okay, so in the secretary, it was real nice to hear in his opening remarks. We’ve been working closely with the Air Force on making sure we have a strong tanker backbone with the KC-46 and now we’re working with the Air Force in other to be able to add other functionality, mesh network backbone related to the KC-46 when the secretary announced the new initiative, the end gas.

You can envision if you will, a solid backbone of KC-46s that then are tied to maybe even refueling other tankers that have stronger survivability attributes to them conceptually maybe an MQ-25 lookalike kind of a thing that’s going back and forth in a yo-yo effect. I mean range is going to be a key element. I mean there’s no denying that to have range. The platforms are extending the range, but they still need fuel. So all of those elements are going to be key enablers related to that family of systems and Global Strike mission set.

Maj. Gen. Doug Raaberg, USAF (Ret.):

It’s interesting, during this conference I’ve come to the realization that managing signatures of multiple stealth, let’s say like platforms of the future, especially when you’re talking about refueling to a strike platform, that’s going to require a lot of partnership with our industry teammates along the way. So thank you for that, Willy. Jon, I’m going to shift on you and [inaudible 00:17:05], and you have a unique background. Obviously each service is fielding its long range strike capabilities. So let’s, let’s be honest with ourselves, Navy’s got its strategic systems program, the SSP, the Army, it’s hypersonic program, the AHPO, and of course you over oversaw the Air Force’s Global Power programs in SAF/AQ. So I believe you really actually have a unique perspective and now an industry perspective at Raytheon regarding long-range strike. So it’s really a double whammy question. So let me hit you with one, first of all, how can digital technologies and modeling and simulation be used to advance long-range strike capabilities? And then follow up real quickly with what do you believe are the unique attributes of the Air Force LRS mission compared to those other service programs? No pressure.

Jon Norman:

Not the easy one. I guess you start with what’s the mission. Our mission is deterrence that that’s why we have a military. We don’t want to fight, but if we do have to fight, then we want to dominate. And that cornerstone of being able to dominate as a nation is to have a safe, secure, reliable capability, whether that’s nuclear or conventional and most importantly survivable. And that applies across the platforms and the weapons that we’re going to put in there. To your question on the digital engineering, so I think probably the best use case, and I know we’re doing this on Sentinel, I know we’re doing it on Radar, we’re absolutely doing it on LRS. So we have a digital model of the weapon. We have a digital model of all the threats of various threats through far into the future.

And we run this model every single night with our LRS program, 6 million miles, and we’ll change the threat lay down, we’ll change the threat capabilities. We’ll change attributes on that weapon system to ensure that is survivable into the future. It’s an incredible capability, something that we can never do before. We always had to do live tests and you’re testing the points and the edges of that capability. Because of model-based system engineering, because of our DevSecOps, we can do that near real time and that greatly accelerates the development timeline. It builds a lot of confidence for the war fighter because ultimately that’s who we’re all working for to ensure that they can execute this mission if called upon. We apply that same lesson learned with HACM. So it started out as HAWC with DARPA and now it’s evolved to a program of record with the Air Force on HACM and it’s a hypersonic missile.

It’s fast. It’s not that different from every other cruise missile that we’ve developed, but it’s that attribute of speed. It gives you a decreased target engagement cycle time. So it lets you hold more targets at risk in a shorter period of time. It lets us penetrate this A two environment from depth and hold those targets at risk to knock the door down. And I would say that long-range strike component of the Air Force is part and parcel to us being able to do that as a nation. The Navy program, the Army program, they’re important for their service. They’re all part of the joint campaign. We’re never going to do this as a single service. But as that critical element, I contend as that leading element of the triad, Global Strike Command has a fundamental impact on our ability to deter as a nation. Our submarine forces, incredibly capable. They’re facing a recap that’s going to be incredibly costly.

Certainly with Sentinel, incredibly expensive and we’re doing not just the weapon system to replace the [inaudible 00:21:00], but also the launch facilities. So they’re more survivable and quite frankly, more conducive to the crew environment. It requires the communication. So NC3, it requires ABMS the work. It requires, I’d say more than ever this replacement of the AGM-86 with LRSO so that we have that weapon in survivable and can deter an adversary. The reason that I think this is so important for our nation as that first step in a recap of the triad is it gives our national command authority a very flexible way to escalate to deescalate any tensions with any potential adversary. It’s fascinating having worked in different commands in [inaudible 00:21:48], certainly in INDOPACOM and CACOM. If you move a bomber into a theater, everybody notices, I mean everybody notices.

And so without ever firing a shot, just simply that bomber presence can change behavior because of the risk. And for that risk to be credible, we have to provide both a platform that’s survivable and we have to provide that weapon that’s survivable. And I think that this team is doing an incredible job with that. We’re partnered with North Grumman on HACM for the propulsion for that scramjet engine. I’d say what’s most critical, and Doug you touched on it’s starting in that design with a war fighter in mind, all the way from the weapons load crew to maintainer to the mission planners, to the air crew that are, or it can be an unscrewed plane that are going to be flying that aircraft in the harm’s way so that when they hit the weapons release button, it works the first time every time.

We’ve spent a lot of time with STRATCOM with Global Strike Command at the start and the design of these weapons, whether it’s HACM or LRSO, we design those just like you’ve done with the B-21 program through RCO, to have that first unit off the production line to be designed for manufacturing so we can produce at scale and to be operationally representative. So the first one off the line is the same as the last one off the line. And that’s good for the start. It makes the acquisition community happy because you’re meeting cost schedule performance. But more important I think to all of us is that total cost of ownership. So throughout the life cycle of whether it’s a platform or the weapon, making sure that it’s sustainable, that it’s upgradable through that open mission system architecture and whether it’s a weapon or the platform that is composable. So if we have a better navigation system, a better self-protect system, a better propulsion unit fielded in the future, we can easily integrate that into the weapon system.

I think Jason Bartolomei is doing a great job with that on the conventional side and certainly at our nuclear, they are absolutely doing that by ensuring that all of the weapons that we’re producing that they have that open mission system so there was the most compliant and that it is easy to integrate that with any new platform in the future and it’s easy to integrate that upgrade.

Maj. Gen. Doug Raaberg, USAF (Ret.):

Storman, that’s awesome. Let’s kind of touch on six generation attributes each and every one of you’ve done… And Doug, you laid it out pretty well. And that’s really the open mission systems architecture. We’re talking about advanced networks and we’re also talking about evolved stealth. The problem is the enemy’s doing the same thing, so they want to get ahead of us. So my real question to each and every one of you, starting with you Doug, is internally to be able to maintain and sustain first mover advantages, I call it with technologies, what demonstrations or what early successes each of your companies can you talk about that really help us and definitely the war fighters, stay ahead of the enemy?

Doug Young:

Okay, just two things on that. First off, in terms of being able to adapt to the threat, when we started this program, the requirements laid out in the 2014, 2015 timeframe. The threat looked very different to what it looks like today and to what’s being projected for the 2030s. So with some forethought, the architects of the program built into the requirements, this flexibility. So I’ve mentioned the open mission system architecture, but another key was having the size, weight, and power to be able to add things quickly and not have to completely redesign the internals of a platform. So right up front we had to build all that in so that we’d be flexible. And what we like to say is we’re in the process of future proofing the platform. So in addition to completing EMD, doing production and sustainment, we’re also working through a roadmap for modernization so that we can start to drop in capabilities as we bring the aircraft online that are going to deal with where we see the threat today.

So to that end, we’ve been doing a lot of work in terms of demonstrations. General Bustier referenced our OMS demonstration yesterday where we’ve integrated a third party sensor onto the platform that’s also enabled by the way DevOps process, which gives you that flexibility to be able to integrate those things on quickly in a very short period of time compared to former timelines. The second thing is that at the onset of the program collectively we invested in a flying test bed. That flying test bed has been flying since the beginning of the program, in fact, before the program started by the company where we initiated to basically fly the software and mission systems of the platform. So we’ve been flying the mission systems for the B-21 for a number of years and evolving it over time to the current state of where we want to be when we go and deploy the platform.

So we’ve exercised the entire kill chain with production hardware, production software, including things like the radar and the mission management systems and the systems. All those things are on that flying test bed. So we can actually go out to the range and fly it as if it was a B-21 and demonstrate that that kill chain is effective and do it for score. So that’s a big element of this concept of risk left so that when we get out into flight test, we’re only dealing with the unique integration challenges associated with being on the actual platform.

Maj. Gen. Doug Raaberg, USAF (Ret.):

It’s tough calculus. Willy, let me throw the question at you too. First, mover advantages out of Phantom Works demos, successes.

Willy Andersen:

Let me parlay off of his response because I think there’s an area… And I’ll get into the first mover in the demo piece as I go through, but OMS absolutely a hundred percent needs to be at the tier three level where you’re driving competition at the box level. Now you’re driving costs down, you’re driving competition at that level. But an area that I want to actually play out a little bit is in the software side of it. So first mover advantage is going to be how quickly we can get capabilities into the jet integrated test and fielded. That’s going to be a lot about software. We’ve had years, decades about doing software… I won’t say wrong because we thought we were doing it the right way, but clearly there’s all sorts of scars and bad lessons learned across the industry.

So what we’re doing in Boeing is a couple of things. So first off, we have our own software factory. We’ve been investing in DevSecOps and all the things that all the companies are essentially doing. But in the ecosystem now you’re looking at software for CCAs as well as the platforms. And we don’t hold the market on autonomy, MUM-T algorithm development and so forth. There’s a lot of other companies that have invested a lot more and we want to harness that innovation to be able to bring the change in the capability to the war fighter. So what we’re actually doing is we’re defining essentially the interfaces we have to protect safety critical elements. We have to be able to do the integration and essentially provide, I’m going to loosely call autonomy dev kit to those houses. So as long as they comply with those, now we can harness that innovation, we can partner up with the industry, we can get new cool capabilities that are out there integrated in a lot quicker.

And then the other element of it is you can envision needing to do a software update in flight. Now I know that sounds like crazy talk because you got to do integration and test and all that ahead of time, but as a B-21 is inbound long, long way to go before it gets in, it may need new threat file, it may need some new software. So just last week at Emerald Flag, we actually took software from our Boeing factory all DevSecOps compliant, and that whole thing, took it from the factory and we actually transferred over a SATCOM CommLink to an airborne platform and it uploaded inflight, everything went smoothly and so forth. So from a demonstration standpoint, it’s looking at those kind of key enablers software, multi-domain capability, common command and control. And quite honestly, it’s not going to be about a single company. It’s going to be about partnering across the industry, working together to be able to accelerate that innovation to the work life.

Maj. Gen. Doug Raaberg, USAF (Ret.):

Yeah, my experience, especially as an air component commander deputy is that’s a tactical imperative. The future means we have to upload inflight even inbound to the target. Storman.

Jon Norman:

Yeah, I think it’s more foundational than diving into the technical side of it. So it’s setting the requirements right from the start. You hit on it. RCO hasn’t changed the fundamental requirements of B-21. Global Strike Command, now under General Newberry, this is the third new weapon center PO, we have not changed the requirements for LRSO since we started this. So that helps industry, whether we’re still in a competition, early down select helps accelerate a program, but having those threshold requirements the first time, so leaning on the war fighters, get that right in thinking towards the future so that as we set those requirements, we’re designing a system that is upgradable and this is where we need to not be so bold to think that we’re the only ones with a good idea.

Now look to our adversaries. So let’s look at the Chinese, what they’ve done with the PL series of air-to-air missiles. They’re not that fundamentally different. They’re composable missiles. That’s how they’re able to iterate and change rapidly and test, fail fast, and field fast. That comes back to the next major point. So for us to be able to work fast as industry talked about the requirements, but for us to be able to field fast, we have got to be in a partnership with the SPO and we’ve gotten to be in a partnership with the PEO and that partnership has to extend out to the operational war fighters so that as we’re doing the design, as we’re doing the iterations, we’re not missing the mark and we are keeping that end user in thought and we’re delivering that capability right at IOC that they need to execute the mission.

It has got to be a partnership. It cannot be an evaluation, from the SPO. And I think that’s why these programs are so incredibly successful because we’ve kind of turned that whole acquisition program upside down. And then it goes back to how do we do this execution in that design phase. And this is where I think it’s real easy to jump on the platitudes of model-based system engineering, DevSecOps. And if I put myself back in uniform days, my eyes just roll in the back of my heads and I go, ah, I don’t care. Do your acquisition stuff, give me what I need. Stop with the prototypes, slap the table. We’ve taken enough strategic risk. I need weapons in the MUNs storage area. I need capacity. And we can deliver that for you and we absolutely will deliver that for you. I would suggest to you though that there is a significant benefit for the war fighter with what we’re doing with the model based system engineering and these models that we’re developing.

It’s not just going through the iterations and design. This is something that you take as a war fighter afterwards so that you can run these mission rehearsals in a campaign with very, very accurate models of every platform and every weapon and of every threat. And you can do this until you find that best combination, that best pairing of weapons and platforms to achieve the best success. And then that leads to your comment about that C2. So the AMBS… Yeah. In the future, here’s the panacea. I can sit back in my easy chair back in the [inaudible 00:34:02] 2000 miles away with my coffee, and I can watch this air war occurring in front of me. I can see every threat. I’ve got total SA and I can just pair the right platform to the right target set and the right weapon to that right threat coming in.

So I win the first time every time. I look at it a little bit differently, I want that war fighter, whether it’s an accrued or uncured platform at the tip of the spear that’s actually exposed to have that type of global assay. And I want that war fighter that’s at the tip of the spear to be able to receive that change of here’s the new target priority. I want them to see to receive that digitally so that it’s not a 12-hour mission planning process on jumps. It’s coming across as an ASCII file and it’s downloaded to the weapon. They got the new pairing and that weapon goes. For my C2, I want that C2 back there to be able to see what platforms at what location with what weapon so that I can make that smart decision, and I’m not dumping the situational awareness of the war fighter out at the tip of the spear. I think that this revolution that we’re going through both an industry and with our acquisition community is going to give the war fighter to that capability in the future.

Maj. Gen. Doug Raaberg, USAF (Ret.):

I started my remarks with. This is a human endeavor. We’re going to end on the human endeavor loop. Willy, I’m going to start with you and then I’m going to, Doug, you complete the loop here please. We’ve got about five minutes remaining. So quick thoughts, what about the human in the loop? We’re talking about collaborative combat aircraft, we’re talking about autonomous systems, we’re talking about hypersonic, blistering speed weapon systems and you’re in the cockpit or you’re on the ground. What from the Phantom Works, from the Boeing side, and let’s go Raytheon into Northrop Grumman. How do you account for this entirely new dynamic environment that you have to deal with? Let’s try to keep it to the weapons system level.

Willy Andersen:

Well, there’s a number of different areas that I could go down with that one honestly enough. But when we’re looking at again that Global Strike ecosystem, from a weapon, from a CCCA aspect of it, that command and control element of it gives the human in the loop the ability now to be able to make adjustments, real time, mission-based, that’s there. So you can envision long-range weapons being shot off an F-15EX, expanded the load out and so forth, and now they’re just on the edge and they’re just firing the heck out of them and shooting them into the area. Those weapons then are netted. And so through ABMS and your commanded control system, you’ve got your ABMers. Now they could be on a E-7, they could be in the back of a KC-46, they could be on the ground, but all the weapons now are all netted together and they’re talking, they’re communicating amongst themselves.

And if they get to a target and that target’s already been struck, they can roll to the next target. And so that’s going to be the ability to be able to provide mass, the fog and friction of war. I mean that’s an element of that ecosystem that increases survivability, that increases mission effectiveness across. That’s what I think when I think of your question.

Maj. Gen. Doug Raaberg, USAF (Ret.):

Awesome. Thank you Willy. Storman, human in the loop.

Jon Norman:

I think you have to keep it simple. So from the weapons, they need to be easy to mission plan, they need to be easy to employ. For the sustainability, it’s starting at the very beginning. So as you’re designing a weapon or you’re designing a platform, go up to Minot, go there in the middle of the winter. Don’t go there in the summer when the Airmen are out there in cold weather gear and they get these horrendous mitts on, hopefully we’ve got them equipped with the right gear and let them work on the platform or on the weapon. Can they do it? Put that weapon into the [inaudible 00:38:10], can you move it in and out easily? And then for our AMC team, can we transport it easily? And more importantly, can we integrate these very quickly onto the new platforms, whether they’re crude or uncrude? It starts with the Airmen it and it ends with the Airmen. If we’re doing this right, we’ve made their job easier and we’ve given them incredible capability that they can employ.

Maj. Gen. Doug Raaberg, USAF (Ret.):

You bring up a key point before I touch you, Doug, and that is the human in the loop also goes from ground to command and control. Obviously everything’s going to be rapid machine to machine in some cases to be able to make decisions. So bring us home. Human in the loop.

Doug Young:

Yes, sir. From a human in the loop perspective, I’ll come at it from two angles. First of all, one of the reasons the program is successful is because of the embedded nature of Global Strike in our program from day one. General Bustier, thank you for the amazing support that we get from Global Strike every day. They’re embedded throughout the program, certainly in the program office, but we have 12 pilots from Global Strike that have been working with us over the last few years on the pilot vehicle interface. So we’ve gotten a lot of great feedback from other stakeholders of the ease and simplicity by which the information is displayed and which enables rapid decision making, informed decision making.

And to the point of the fact we’re really in an information age, it’s the people that are coming through schools and some of them that are still playing video games are going to be flying this airplane. And so they need to have a vehicle interface that really represents the state-of-the-art as far as that ability to manage the flight, but also manage that mission, which will be complex. So that Global Strike engagement at the pilot vehicle interface spreads all across everything we do. Our Global Strike is involved in our maintainability and sustainability studies. We have people in our labs in Melbourne, Florida where they work with us on the software and then out in Palmdale, we have folks that are working with us on the flight line as we get ready to go fly this airplane.

So Global Strike is a big part of that and I think that’s really a big aspect of the human piece that needs to be involved right from the beginning. And then finally, from a human perspective, I just really want to acknowledge the 8,000 people around the country that wake up every day to deliver this radar capability online. Those are 400 suppliers in 40 states and Northrop employees across the country working with our government counterparts to bring this online as quickly as we know how. And we’re committed to that and we work at it every day. So thank you for the opportunity to speak today.

Maj. Gen. Doug Raaberg, USAF (Ret.):

So let’s wrap it up by going back and looking at what this is all about as we talk about the human endeavor of Global Strike. I think you three gentlemen just hit the home run of the day. And that is, let’s not forget the war fighters are actually in industry and they’re creating new approaches at Boeing and Raytheon, at Northrop Grumman and others. And this is a tough problem, but not one insurmountable. I guarantee you the Chinese are going to be watching this video over and over and over. So Willy, thank you. Storman, I appreciate it. And Doug, thank you very much. One shameless plug, please go to the shop AFA store. I’ve already bought my bomber T-shirt, it’s got the B-21 in the front and every aircraft that I’ve ever flown them on the backbone. So please and thank you. Let’s give these gentlemen a round of applause, please.

Watch, Read: ‘Operationalizing ABMS-JADC2’

Watch, Read: ‘Operationalizing ABMS-JADC2’

Chad Haferbier, vice president and division manager for multi-domain operations of Leidos; Lance Spencer, client executive vice president for AT&T Global Public Sector; and Joseph Sublousky, vice president for joint all domain command and control at SAIC, discussed ways the Department of the Air Force and industry can work together to deliver operational capabilities of Joint-All Domain Command and Control to Airmen and Guardians during a panel on ‘Operationalizing ABMS-JADC2’ on March 7, 2023, at the AFA Warfare Symposium. Watch the video or read the transcript below.

Col. Frederick “Trey” Coleman:

Good morning. Thanks for being here this morning. Thanks for choosing to attend this panel. We know there’s a lot of great topics out there, so we’re honored you chose to come and spend time with us. This topic today is on operationalizing ABMS and JADC2. It’s a great topic because, frankly, we’ve all been talking about this for quite a while. You probably didn’t attend a panel today. There’s probably not a panel out there that didn’t say the words ABMS or JADC2 or at least C2 at some point. It’s really exciting and it’s a great opportunity to talk about how we’re going to… Or how we are making it real, because I want to be clear that this isn’t a brief about tomorrow, or a panel about tomorrow, or the future necessarily. There will be a lot more to come.

But ABMS and JADC2 are being operationalized today. There’s a lot of great capabilities out there and a lot of great systems. That’s what we’re going to talk about. Before we get into that, what I’d like to do is lay some foundational groundwork a little bit and just talk some terminology, because I think that’s helpful before we get into a lot of the specifics. At the risk of sounding pejorative, I’ll just start with just defining JADC2 and ABMS. When we talk about JADC2, this is the Department of Defense’s Joint All-Domain Command and Control Program. The strategic document for it says, “The purpose of it’s to enable the joint force to use increasing volumes of data, employee automation, and AI, rely upon a secure and resilient infrastructure, and act inside an adversary’s decision cycle to sense, make sense, and act.”

In their report on JADC2, the Congressional Research Service described JADC2 as the DOD’s concepts to connect sensors from all the military services, Air Force, Army, Marine Corps, Navy, and Space Force into a single network. ABMS, the Advanced Battle Management System, is the Air Force’s contribution to JADC2. It’s part of the JADC2 solution. The name of the Air Force’s contribution is telling in itself, command and control. It can be a very broad thing. The President of the United States executes command and control, commanders execute command control. Just about anybody can execute command and control or touches command and control at some point. Battle management is a niche form of command and control. It’s the tactical level of command and control. It’s the employment, it’s the engagements, it’s the battle level of command and control. Just by naming the contribution Advanced Battle Management System, the Air Force has said that it’s focusing on the tactical level of C2. Not necessarily the operational level, not necessarily the strategic level, although there’s, of course, implications and tangential relationships, externalities, but battle management is tactical command and control.

Specifically, ABMS, is uniquely focused on the kill chain. The kill chain isn’t really a joint term. I’ll talk about that just for a second too. When we talk about the kill chain, we mean the F2T2EA process, finding, fixing, tracking, targeting, engaging and assessing. When we think about ABMS, we should think about it as ways the Air Force can advance its ability to execute F2T2EA faster, more resiliently, and at scale. That’s what this panel will focus on. Each of our panel members has been an important part of the ABMS community. Each of them and their companies have made and are making critical contributions towards our ability to operationalize ABMS to our ability to execute the kill chain faster, more resiliently, and at scale. Chad Haferbier serves as the vice president of Leidos’s multi-domain operations division.

In this role, he drives the corporate strategy that positions Leidos as a leader in the MDO paradigm with meticulous planning, technology disruption, and collaborative execution. Previously, Mr. Haferbier was a senior material leader at the Department of the Air Force Rapid Capabilities office. His team led the advanced panel management system to acquisition, delivering advanced all domain capabilities to Airmen and Guardians. The RCO’s done great work for us and continues to do great work. Lance Spencer is the client executive vice president of AT&T’s global public sector. He leads the AT&T business portfolios for the U.S. Department of Defense and Global Defense. In his capacity, he is responsible for identifying, aligning, and developing AT&T and partner capabilities to meet DOD joint and coalition global operating needs to improve operational availability, cybersecurity, resiliency, and cost. Mr. Spencer spent 26 years in the Air Force retiring as a colonel after serving in several key positions, including commander of an expeditionary group and two different squadron commands and serving as a joint task force J6 and on the half-staff.

Joseph Sublousky is the vice president of SAIC’s Joint All-Domain Command and Control campaign responsible for developing and implementing corporate JADC2 strategies. He works across all SAIC sectors and business units to ensure coherence and synergy around capabilities for Department of Defense imperatives. Digital engineering, artificial intelligence, machine learning, multi-level security networking, and cloud-based on-prem DevSecOps. He also has 28 years of active duty Air Force service, retiring as a colonel in 2014. As an airman, Mr. Sublousky commanded several C2 and communications organizations around the globe, including the 56th air communications squadron in Pacaf, the 1st combat communications squadron in USAFE, and the 609th air communications squadron, an AFCENT near and dear to my heart. He also served as the AFCENT A-6. Gentlemen, thanks for taking the time to be here on our panel. Over to you now for some opening comments and we look forward to having this discussion with you, Chad.

Chad Haferbier:

Thanks, Colonel Coleman. Super excited to be here with you all today to talk about two of my favorite topics, delivering operational capabilities to war fighters rapidly and then ABMS, and how we can mechanize the open architecture non-proprietary framework to drive best-of-breed solutions that will stay ahead of those threats. How do we expedite that kill chain? How do we make that kill chain more resilient? I think ABMS is laying the great framework to be able to do that under General Cropsey’s leadership. Very excited to help General Cropsey as a performer on the digital infrastructure consortium, as well as driving Leidos’ corporate strategy to help stay with that non-proprietary open architecture solution base that we can help work across the industry as well to bring the best-of-breed for war fighters around the globe.

Col. Frederick “Trey” Coleman:

Thanks, Chad. Lance.

Lance Spencer:

Yeah, thank you. Some of you may see my LinkedIn post yesterday. Yesterday was the 147th anniversary of Alexander Graham Bell receiving his patent for the telephone and birth of AT&T. Since then, AT&T lab scientists have gone on to invent some amazing things like the transistor, long distance phone calls, cellular phone system, invented the transistor, designed Unix, which was the basis for today’s modern internet. Even closer to the military, AT&T provided the first command and control network for General Pershing on the front lines of France during World War I. We invented AUTOVON and the precedent system. We’ve got a long history working with the military, over a century of working in the military, solving problems, and going right to the front lines with the military, when needed, to support our nation.

Connectivity is at the heart of everything we do and is at the heart of every communication network. What is an organization that cannot communicate, cannot access their data ubiquitously? How can they deliver on their mission without effective comms? That’s where AT&T comes in. There’ll be private-based, IP-based off of… Private access based off of use cases, but the underpinning is commercial networks. The fight won’t happen inside the gate. The fight will happen on commercial networks wherever you go. DOD simply can’t afford to build what we’ve already spent hundreds of billions of dollars on, and in most scenarios, they’ll need to operate on this commercial infrastructure, like I said, if not for all, some of the connection. Stove pipes just don’t work. 5G is a game changer in military operations. Low latency, seamless standards-based data access, and resilient edge operations provide connected platforms, interoperability, and the DOD decision superiority in JADC2.

By bringing the major network service providers like AT&T and for early planning and exercises, we can more effectively help the DOD during crisis and better align to the mission delivering standards-based solutions that meet the needs of the military. Working together is how we can deliver the right solutions. Thinking has matured and evolved with commercial 5G, private seller networking, securing those extensions of the enterprise, and how private networks interconnect for enterprise operations and scale. 5G use cases in hybrid of private and commercial 5G implementations will be critical and tailoring depending on what is needed for each use case. Delivering enterprise data access at scale will require partnering with network service providers to stitch this together, leveraging our significant investment solutions that already exists and can make this hybrid model work. 5G is the access, but it requires a massive fiber infrastructure, as well as a space layer, and service management and service assurance platforms to operate beyond niche solutions.

The DOD can’t recreate that. Like Space Systems Command says, “Exploit, buy, build.” DOD often gets that backwards. But to the success of a great power competition, it’s necessary to exploit and buy and leverage the innovation investment of the whole of nation. Just briefly, speaking of Space Systems Command, the next frontier space will be no different. The power of combining terrestrial and space-based mobile network solutions has the potential to provide end-to-end coverage never before available. Choosing the right trusted industry partners will be important in a national security imperative. That’s just the beginning. I can also talk about maritime and other domains. For example, AT&T and partnership with the Naval Postgraduate School is expanding 5G coverage into the Littorals with our commercial radio access network on ocean power buoys in Monterey Bay. The health communications industry is redefining networking, pushing the limits of mobile communication as we know them today. Our military needs to connect to an interoperable, seamless, unified data-driven network. Networks shouldn’t be different because they’re in space or at sea, and the same devices should be able to connect regardless of the network. That’s our plan.

AT&T is collaborating with AST SpaceMobile to deliver space-based mobility. The AST BlueWalker 3 satellite successfully launched in September 2022 and AST is completing initial vehicle and systems checkout. AT&T is working with AT&T SpaceMobile to test the integration of the AT&T mobile network with this AST solution. The satellite literally would operate as a cell tower in space and follow industry standards. We have conditional regulatory approval to use AT&T spectrum to test and this will bring the power of space-based mobile solutions, combined with terrestrial networks, to seamlessly provide interoperability in a single [inaudible 00:10:32] enterprise regardless of location. In our too distant future where DOD will be able to access space and terrestrial-based networks determined by best path with interconnects occurring as they do today in global peering and carrier-to-carrier handoffs, and with the same devices regardless of access to space systems or terrestrial mode. Just like our network and devices allow for roaming today, in the future, they’ll be roaming on space. This is another innovation in our long pedigree inventing the future and our century plus long relationship with the military providing cutting edge solutions. Over to you, Joe. Thanks.

Col. Frederick “Trey” Coleman:

Thanks, Lance. Joe.

Joseph Sublousky:

Fantastic. I can’t see you but you can see me. I’m going to tell you a lot of things, but I would love to have a follow-up with you after this. I want to talk to you, because the conversation’s how we’re going to get after JADC2 and ABMS. This is going to be a cooperative effort. What I’ll tell you about me is you heard my bio, a lot of acronyms. I’m an atypical communicator. I grew up under the likes of operators that taught me that it’s not about the links, it’s about the data, it’s about the mission. SAIC is a solutions provider. We are working in several areas across all of the services in order to provide each service’s contribution to JADC2 with capabilities, not products. JADC2 two won’t be a product. I tell everybody this, “You won’t buy a JADC2. What you’re going to buy is a capability and it’s going to be built upon an architecture that all are going to be able to share.”

A little bit about me, I’ve commanded, like you said, at the ACOMs, at the combat comm, and it as an A-6. I saw every non-interoperable system that you could probably see. We figured out a fix for it. But in tomorrow’s pacing threat, we’re not going to be able to figure it out. We’re not going to be able to get the data there fast enough once the person who needs it figures out what they need. We have to have a data repository that’s enabling us to allow algorithmic approaches to get the data at the places at the speed of need. We always say speed of need, but the reality of it needs to be there much like you’re getting your updates on your phone and you didn’t even ask it for anything. What I would tell you is I’m looking forward to this. Thanks for the opportunity to participate in this discussion as a one-way discussion, but more importantly, AFA, it’s been a fantastic symposium. Really have enjoyed time here.

Col. Frederick “Trey” Coleman:

Thanks, Joe. I appreciate it. Hey, I realized as you guys were introducing yourselves, I failed to introduce myself in the beginning, which was the first thing they told me to do when I walked in the door. I’m Trey Coleman from the 505th Command and Control Wing. We are the only command controlling in the Air Force. We work for the Air Warfare Force Center as part of ACC and directly for the CSAF to test, train, and develop TTPs for the war fighter. We’re really excited to be a part of this panel and work closely with the C3BM team and the CFT up at half to get ABMS across the finish line or continues to deliver it. I’m not sure there is a finish line. Okay. On to the questions. I’m going to ask each of you guys a question, a question or two, and what I’d like you to do is answer the question and then I’m going to ask the rest of the panel members if they’ve got something they’d like to add on.

This needs to be a conversation for it to be meaningful. I want this to be a meaningful conversation so that we all learn something so the audience walks away and we’re smarter and we’re a little bit more aligned. I’ll start with you, Chad. You’ve been working at ABMS for quite some time. As a matter of fact, I first met Chad when he was at the RCO and we were working CMCC together. I’d ask you, what do you think has been the greatest success of ABMS and what have we already accomplished or delivered or advanced as part of ABMS?

Chad Haferbier:

Yeah, It’s a great question. The pivot from the on-ramp exercises, which stimulated the imagination of what could be, to more of an acquisition-focused, delivering operational capability, I think, has been the best shift for ABMS. I think Congress agrees. They’ve actually appropriated a full budget, for the first time in ABMS, since Joint STARS was canceled. That’s good news for the Air Force as we’re on the right track. Under the leadership of Spaniard Valenzia and General Cropsey, that early prominent war fighter involvement in everything ABMS is doing is really where we need to go. That’s how you get operational capability fuel as rapidly as possible. You get that war fighter feedback, you apply DevSecOps principles to how we deliver capability, not just software. Those are great Ws for what ABMS is doing, which will manifest in great Ws for operational advantages for our war fighters.

Another great thing that ABMS has done a better job of, over the past few years, is getting Space Force more involved. General Olson’s far more dedicated in terms of bringing the Space Force along to have their story for how we, at the Department of the Air Force, delivers a joint across space and Air Force ABMS capability that is critical. We can’t stovepipe within our own department. How ironic would that be for JADC2 to be stovepiped within the Department of the Air Force? Those are some really big Ws. I’ll turn over these guys.

Col. Frederick “Trey” Coleman:

Lance, Joe, any pilots?

Lance Spencer:

Just a brief comment and I agree with what you said. Joe kind of touched on it in his opening comments, being in front of the pacing threat. I think it’s really important that, in the JADC2 and ABMS environment, that we start exercising together on what potential courses of action might have to be executed. If we wait till the balloon goes up, it’s too late. We got to do all that relationship building, getting to know each other, understanding the art of the possible together, pushing ourselves together. I think that’s really important in the construct.

Col. Frederick “Trey” Coleman:

Thanks.

Joseph Sublousky:

Recognizing we needed to do ABMS, I think, is a success. Absolutely. I would tell you that. When I took over at SAIC a year ago, I came from a cybersecurity company and I was doing a lot of the threat intelligence piece. It hearkened back to the days of tactical data links. How do you share threat intelligence across an environment so that you actually know the threat before it actually gets to you because you can see it in another domain? You can see it in another co comm. I navigated to the guiding principles of ABMS when I first started, because ABMS is a contribution to JADC2. I said, “What are the guiding principles?” Separable C2, that says a lot. How do you separate C2 in order to actually do it? That gets to a lot of the things that we need to work on within ABMS. I believe we’re starting to deliver those separable C2 constructs on how do you [inaudible 00:16:41] environment? How do you actually get the data to the locations that you need it? How do you operate within a cloud environment?that’s going to enable us to do that.

Distributed debt battle management, we’ve known that all along but how do you do it at speed and how do you do it where you’re actually doing a different kind of warfare? How do you reimagine the way we’re going to do battle management at the tactical level in the future? And then integration, we all know what integration means as a guiding principle. That’s the operational side. But you go to the technical side and it talks about DevSecOps in support of those operational guiding principles and open architecture. I think, most important, models-based systems engineering. We got to model what we want to do before we actually do it, because long gone are the days that we’re just going to buy it and see if it works and then we get into the integration challenges that we’ve faced in the past. I think those are some successes to date and what we’ve delivered. I’ll talk about in another question that you’re going to, I think, hopefully, open it up for us to say. What are we doing in cloud? I’ll stop there.

Col. Frederick “Trey” Coleman:

Okay. Thanks, Joe. I agree. One of the greatest benefits of JADC2 and ABMS has been this focus on C2 that I think we’ve led atrophy over the past few decades. That’s one of the greatest benefits. I said it before, no kidding, we, this room, we are delivering and there is capability out there, but that capability requires data. It requires connectivity. General Valenzia said it yesterday on a different panel, “Data is not C2. Data is not…” Or sorry, “Communications is not C2.” Command and control commands an authority and controls the communication of that authority, the expression of that authority. It’s a two-way conversation, but it requires some degree of connectivity and some degree of data in some way, shape, or form. We know our adversaries are working hard on their abilities to disrupt and degrade our ability to transfer data, to defeat our ability to communicate. Is the Air Force moving in the right direction? Lance, this question’s for you. Is the Air Force moving in the right direction and to ensure connectivity and access to our data, and are we thinking about connectivity the right way?

Lance Spencer:

The Air Force and Space Force is getting better at it. The conversation has changed and pivoted significantly in the last several years. I think the understanding of how to embrace commercial solutions and investment has been part of that. There’s a lot of opinions on enterprise IT as a service, but I’ll tell you, the network as a service, RRE that we’re doing at Buckley just down the street, we’re getting amazingly high marks. Buckley’s about to move to a secure internet gateway, which is a multi-generational leap from the current internet access points that the DOD is using today using commercial innovation. We did it in partnership with U.S. Cyber Command and National Security Agency. We’ve got all kinds of proof points off. It’s already migrated, it’s not going fast enough.

The pivot needs to happen faster. The DOD, and the Air Force, and Space Force are working on it, but they don’t quite know how to procure a commercial yet. I’ll give you a great example. Later today, we’re going over to Buckley to do a ribbon cutting on the 5G build that we just did there. It took five years just to get that done. Normally, it takes 18 months. There’s just all kinds of paperwork, all kinds of red tape, and 5G is going to be a major enabler for data ubiquity. You’re going to be using it inside and outside the gates, getting that infrastructure in place. Oh, by the way, the carriers pay for that. That’s not a bill, is going to be really important. Solving those problems are still really important and I think there needs to be more urgency and effort on that.

Col. Frederick “Trey” Coleman:

Any follow on thoughts, Chad, Joe?

Chad Haferbier:

Yeah. I’d pile on a little bit in terms of where I know the Air Force is going that is right. As you go to a detailed environment, you’re going to need to provision for that. You can’t expect to have comms all the time. How do we ensure that we have protocols and algorithms set up, whether it be at the far edge or at a operational C2 node, where we can understand the data, understand the latency of that data, and make sure we’re making the best decisions possible?

Col. Frederick “Trey” Coleman:

Yeah, thanks.

Joseph Sublousky:

I think the are we moving in the right direction? Yes, I think we are, but there’s a long way to go. The adversaries approaches to disrupt. Disrupting feeds and speeds is an easy thing to do. Isolate, locate, connect, disconnect. I think as we move towards a cloud, a cloud edge environment, and we start moving in that direction, that would be very important. We’re heavily dependent upon meshONE-T to come up with that answer to how are we going to actually connect and how are we going to be able to self-heal, self form those fancy words that we use that are very difficult to apply, but that’s going to be absolutely critical from a connectivity piece. But I would offer that connectivity is not the only way of operating within ABMS.

It’s about not just the networking side, but it’s a data-centric approach put into a cloud architecture. That is absolutely, because once you get to that point, no matter where I go with this phone, or that iPad, or anything else I’ve got, I can get to all of my data. The data is what we need to get to. When you talk about redundant communications in the past, I would offer that, more importantly, it would be resilient communications to that data is what I’d focus on.

Col. Frederick “Trey” Coleman:

Yeah. That’s a great point, Joe. Somebody asked me recently what happens to the Takl or the Ford Edge when they’re disconnected? I think we’re at the point where degradation isn’t necessarily a binary thing where it’s you either have it or you don’t. I think, my assumption, and the way when we talk about this, I think there’s always going to be some degree of data that can get through. If there is, no kidding, you’re entirely disconnected, I think it’s a very short period of time when we can get reconnected. We’ve got the systems to do that in the multiple pathways to do that, but I don’t accept that it’s a binary thing, either you have it or you don’t have it. Because we do have multiple layers and very resilient comms, and you guys are helping us build those out.

A key part of this construct is, today, the Air Operations Center, and Joe, you mentioned that you’ve got some pretty good experience in our AOCs. Clearly, how we think of the AOCs today in the big monolithic buildings needs to change. I’d argue that there’s still, and in fact, there’s probably an increasing need for those operational level C2 decisions at resource management that decides where the assets need to be, and at what time they need to be there, and what they’re doing. We still need that, especially with our limited force. You still need that operational C2 function. But the question is what does it look like? How does it change in the future? Joe, in your opinion, what does the future of the AOC look like?

Joseph Sublousky:

That’s a big question.

Col. Frederick “Trey” Coleman:

You got to solve though. You can figure it out.

Joseph Sublousky:

I think there’s a lot of people in there that would know what the AOC is supposed to look like in the future. I’ve been out for a little while, but I can give you my opinion on and what I think it is. I’ve seen an example of it in SAIC. It’s cloud-based command and control. SAIC was selected to deliver a cloud-based command and control for customer number one, NORAD NORTHCOM. Nominally got started in November, December timeframe. The focus was on cloud and the focus was on data. It was not on the edge, it was not on the network connectivity or any of those things. In a DevSecOps environment, we’ve been able to deliver in two months an unclassified CUI level capability that connects all the air defense sectors and all of the radars that they’re looking at, unclassified-wise, to a single pane of glass using an application.

Now you would think that that’s critically important to have, which it is, but I think the most important thing that I would say for the AOC in the future is something that the commercial industry does today, which is a continuous update. It’s a continuous update to that app based upon the threats that you are actually getting into. Because we’ve all known it, your plan is just about as good as the first contact with the adversary and then it changes. How do we get continuous updates? Well, the way that you do that is through a DevSecOps environment. You can update that CBC2 app today and it actually is automatically available to everybody that’s connecting to it. I think it’s the first time in the Air Force that we’ve seen those feeds be connected into a cloud architecture that’s displayable, not only on a laptop but on your phone, because once we get the data and the access to the data in a cloud environment, the edge device is, I don’t want to say it’s simple, but it can be realized pretty quickly.

Col. Frederick “Trey” Coleman:

Chad, any thoughts on the AOC?

Chad Haferbier:

I’ll take a different angle. Some things that many probably assume already is that AOCs are on a common baseline. I think that’ll be in the future is, as Kessel Run, cloud hosts their applications will have a better ability to cross train across AOCs. Folks can come in and be familiar with the AOC as they sit down in whether they be in Hawaii or in Germany. That’s one thing, I think, in the CICD pipeline that Kessel Run’s leading is very important to realize that vision and be able to rapidly update. How do we break down the data between test, and training, and operations to quickly evolve our TTPs to stay ahead of threats? I think the AOC will be very involved in that as we break down those stovepipes of data and start to throw them black through the shotgun and other applications to work on those things in a more iterative process.

Col. Frederick “Trey” Coleman:

Yeah. That’s a great point. Systems like Kreios and CBC2 cloud-based systems allow you to distribute your control. That’s how you do it. We’re excited about these systems. Lance, any thoughts?

Lance Spencer:

Yeah. Just a couple thoughts and an open secret. Joe and I worked together once upon a time. I was the F4 A-6 for Europe in Africa for a few years, and I’ve slept on the AOC floor a few nights myself. When we’d finish the operational planning as a staff, the boss would say, “Oh, you all get on planning the next thing. Lance, you come with me to the AOC,” because they understood what comm meant and what the Sixth World looked like. A lot of people talk about cloud. I think what Joe talked about especially is a great prototype and proof of concept to innovate. The ability to scale it is really important, and it sounds like you’ve maybe solved some of the problems from what you’re describing. My experience and my observation, as I engage across the Air force, is the biggest stovepipe is the network.

Everybody goes and gets themselves some over their own network and it’s not ubiquitous. It doesn’t connect. There’s a myth that the DOD doesn’t write on commercial networks. Almost all of the DOD writes on commercial networks. It’s just not done the right way. Figuring out how to procure that. As you go to the cloud, how you going to get there? You got to connect. It doesn’t just magically hop in the cloud. Thinking through, that’s important, I think, when we’re thinking through, especially distributed AOCs, and distributed operations, and C2 that the AOCs will bring forward.

Joseph Sublousky:

That’s a great point. I mean you brought up PTSD for me back in Third Air Force. Lance would always decide where we were going and then I would go there and figure it out. But the plans are important, they’re absolutely critical. I mean, coming up with what you’re going to do is important. I guess what I would offer from the AOC’s perspective is, as a combat comm unit, we needed 17 pallets to take connectivity to the field, and then we needed 48 to 72 hours to connect that connectivity to some kind of a source where then we could start bringing up our servers and bringing up… That cannot happen in the future for an AOC.

It has got to be something where you can actually deploy a very light capability and sometimes use existing connectivity that’s available to you in order to get back into a cloud environment that has the data that you need to get access to. The Air Force is working in those realms, but that is going to be critical for the AOC in the future. The logistics trail that has to happen in order to actually establish some kind of a presence, even at the smallest of presence. We have a answer for that. The challenge is we just need to get through a policy discussion around how we do it. I think that’s going to lead into my next, hopefully, discussion. But I’ll stop there because we can go forever on policy.

Col. Frederick “Trey” Coleman:

Thanks, Joe. Hey, a great example of distribution is AFCENT, just a couple weeks ago, you may heard me say this in a panel yesterday morning, but they pushed their ATO from an apartment complex using sipper tablets, and the map team stayed in their apartments in Sumter, South Carolina and pushed the ATO out to the field. That’s distribution. That’s what it looks like. They did that because they’re using Kreios, and it’s a cloud-based system, and they don’t have to have the servers in their apartment complex. It’s a great example. Okay, question four. This is for each of you, and I’ll start with Chad, and we’ll go down the row here. As a senior corporate executive, what is one of the biggest challenges you see when working on the ABMS portfolio from the industry perspective? What one thing would you change in the Air Force bureaucracy, if you could, to help us operationalize ABMS?

Chad Haferbier:

The value proposition for ABMS JADC2 is China. There’s no secret there. The secretary’s talking about it, chief of space office is talking about it. With that comes, we’re going to be leveraging our most exquisite capabilities across the joint force. To me, one of the challenges that I understood, but now I really understand it on the industry side, is our ability to communicate, at a classified level, with the war fighters and with the acquisition entities so that we can better position our IRAD spends to skate where the puck is going, and be ready for them, and have capability ready for when they want to get there. To me, that’s one of the biggest challenges. It’s something I’m not just going to throw over the fence and hope somebody fixes it. I’m willing to help fix it. I’ve had many conversations this week about it actually. To me, that’s one thing that I would hope that the bureaucracy within the Pentagon can get together and solve.

Lance Spencer:

Thanks. Lance. I think that something to consider with that is how to better embrace the whole of nation. Because if a fight happens, the whole nation’s going to be involved. How do we bring all that to the table? I will echo what Joe finished with a minute ago about policy. One of the examples I used was building cellular networks on bases. It should be just as easy building outside the fences, inside the fence. The signal doesn’t stop at the fence line, but we have to do an 18-month spectrum study. By the way, for spectrum that we already own and are licensed to operate on. There’s a lot of things that put sand in the gears to keep that kind of stuff from happening. I was talking with Lauren Knausenberger last night for a while and I mentioned the secure internet gateway.

It’s an amazing capability, but it took her personally working for three years to get a temporary exception to policy to do it. She’s the CIO and it took that much to get that work through the building. I think being able to address policy, be nimble, and be able to take risk. I had an opportunity to talk with Secretary Kendall not long ago. He says, “What question would you pose to me?” I said, “You’ve accepted the risk of operating off department complex and people operating from their sofa on the same systems with the same data, but you can’t bring that on the base. Why is it harder to bring it on the base to do the exact same job?” That’s what my thoughts are.

Col. Frederick “Trey” Coleman:

Thanks, Lance.

Joseph Sublousky:

I would say the one thing, get rid of the word bureaucracy. I mean, it is not just a bureaucracy on one side. The bureaucracy is a two-way street. “You need to do it this way. No, I can’t do it that way. You need to change your mind. I can’t change my mind.” I think partnerships are important. Experimentations in partnerships between industry and the Air Force are critical. Just during this conference, I was asking a general officer I worked for about starting back in your day kind of approach. I can say that now, “Back in my day…” because I remember it. JFX was a great opportunity for us to experiment in how we were going to do joint task force operations. We do that in some terms today. But the challenge is I think there’s not enough partnership discussions because we’re bringing capability and technologies that may not necessarily meet the needs that you, the Air Force, has or the DOD has.

That’d be the first one. The second one is it is around test and certifications. It is around how do we get to the person that can say, “Yes, which I’m going to take that home with me, sir, and find that person”? It is about not trying to convince the people that say no all the time, but getting the person that can say yes, because when the nation goes to conflict, bureaucracy falls away. Because those folks that can say yes, come forward and say, “We’re going to do this.” I’ve been in that road before and we’ve been able to accomplish a lot of capabilities that we didn’t think we could in a very quick fashion, but we needed a conflict, the forcing function. I think, at this stage, partnerships and identifying clearly who can say yes to those challenging tests and certifications.

Secret releasable is a classic example. That takes a long time, but it’s not really a long time once you get to the right person and explain what you’re doing. There are technologies out there to allow us to do things in a different way. Today, in a more agile environment, you can’t apply hardware to a cloud environment. It just doesn’t scale. I would leave it at that. I got to mention, we talked about cloud. I just want to make sure everybody understands. Air Force Cloud One, it’s DOD Cloud One. SAIC is well-versed to support every Department of Defense entity into Cloud One. It’s not one service provider. It’s not just I have to go to one service provider. It’s a decision that says, “I need to move my on-prem or my capability sets into a cloud environment.”

It’s walking into that and saying, “Can you help me do it?” Number one. There’s a bureaucracy, I got it. But if you form a partnership, it can go very quickly. But more importantly, I think that when you start making that road to the cloud and you recognize it’s not one service provider, the next thing you’ll recognize is that it’s taken three plus years to put a zero trust environment in that cloud. I mean, why would you not want to go there? When you looked at solar winds, and Log4j, and all that, Cloud One was not impacted by any of those. The cost of moving to cloud may be expensive, but the cost to not move to cloud, I would say, would be something to take a look at because it’s very expensive to address those impacts, vulnerabilities that exist on a network-centric approach today.

Col. Frederick “Trey” Coleman:

As former A-6s and ACOMs commanders, how can the Air Force incentivize today’s ACOMs commanders to move their data to the cloud? Or the A-6s. The right person, the right air component. This is a surprise question. They weren’t expecting this one, but it’s a challenge we face because nobody wants to let go of their data. You got your data center, you want to hold onto it like it’s a teddy bear. How do we incentivize them?

Joseph Sublousky:

Incentivize them. You could say, “Do it,” because we do that. We do that. I mean, when it comes down to it, we get to the incentivizing way of just do it, but there’s a better approach to it as well. Today, when you want to move into a… Again, I’m going to take one minute to talk. But when we want to tell people to move to a cloud architecture, we don’t understand that… We don’t tell them the other part of that, which is, “Keep doing what you’re doing. I funded you to do what you’re doing, so keep doing that. But by the way, go find additional funds, additional resources, additional expertise, additional talent, and move.” And then operate it a period of time where you’ve got to keep both up and running for some semblance of a time before you’re assured that cloud architecture’s going to support you. I think that there’s an opportunity where the services can look to earmark or do some investments to get that data to the cloud to reduce vulnerabilities that exist in existing legacy systems today.

But I don’t think it’s going to happen if you’re asking the match comm A-6s, the NAF A-6s, to take it… “Go ask for an unfunded budget in order to move your architecture.” I would venture to say that there’s… I don’t want to be so pejorative to think that it is this, but I would say that if I were to express the benefits of cloud over the benefits of architectures living in a 19-inch rack, that there would be very few people that would say, “No, I want to stay here.” Now. There are some occasions where you have to stay there, but the benefits once you get into a cloud architecture with the reach, the capabilities, and then the security pieces behind it, what we’ve seen an industry, from a Cloud One perspective, primarily, the industry is moving into a cloud architecture for security reasons, because I can control the access to it, but more importantly, I have a configured environment that I can actually keep people in.

Col. Frederick “Trey” Coleman:

Nice. Lance.

Lance Spencer:

I think building on that, a couple thoughts. One is empowerment and having a solution available that does meet their interoperational needs and to allow that to happen. We reflected back on Ramstein and we did a lot of stuff people said, “You can’t do that.” But when things are happening, you can do a lot, but we can’t wait for that. I think there’s a workforce issue as well, and maybe a revisiting of roles. Companies like us up here on stage bring great things to the fight. What do we want our Airmen and Guardians doing?

Do we want them building servers under desks or solutions like that because they’ve got a need, and they’re very creative and they know a lot of things, but it becomes a solution under the desk? Or do we want them doing more cyber kind of missions and things like that? I think that we need to think through how do we realign the workforce so that they’re doing meaningful things to themselves that they feel is bringing the right contribution to the mission, and then how do we migrate what they had been doing under their desktop to companies like us so that you can get scalable standards-based solutions that talk together?

Col. Frederick “Trey” Coleman:

Thanks. Gentlemen, we’ve reached a couple minutes left. I’d like to just give you the opportunity for some closing comments. Chad.

Chad Haferbier:

Yeah. We talked a lot. You started off with we’re talking about battle management at the tactical level, and then we immediately fell back into operational. One thing that I really want to make sure we understand is that there’s never going to be a homogeneous compute environment. Cloud One’s not going to be on B-21. Sorry. But there will be operative advantages to connect to those operational C2 nodes and to have that data extraction for an operational C2 application in a cloud. Heterogeneous ecosystems for compute and how we communicate are going to be forever, just like ABMS, as you mentioned, will be forever. We need to make sure that we understand how do we drive advantages to the edge, to bare metal, as well as seize those advantages at operational level from that data extraction and redistribution and that decision layer?

My comments are really focused on, we want to work with industry, we want to work with all of you. We know it’s going to be hard, we know it’s going to be heterogeneous environment, but I think there’s tons of advantages for our war fighters. That is the national opportunity space. We’ve fallen away from our soul platform technological advantage, especially with China, but there is advantage in our ability to collaborate and seize those synergies from all domain JADC2.

Col. Frederick “Trey” Coleman:

Yeah. I appreciate your point that we started talking about battle management and the kill chain and we’re talking about data centers. We just got to keep reminding ourselves, I’m guilty of it, is anybody else? Data is not C2, but you need some kind of data. You need some kind of communications. But C2 can take the form of… It’s taking the form of smoke, drums, flags, and today, it’s taking the form of algorithms. Lance.

Lance Spencer:

Yeah. I’ve got to think that it’s probably just the job jar of trying to breathe this to life is fairly overwhelming. I’m sure there’s all kinds of people knocking at all kinds of doors saying, “Hey, take a look at what I’ve got. Take a look at me,” and sorting through that. Separating the wheat from the chaff, I’m sure, is a challenge. I remember being in uniform, coming to events like this, you don’t get a moment of peace. Actually I’m finding now in the role I’m in, a lot of the companies that are talking to the Air Force and Space Force are our suppliers also. I’m actually doing more industry meetings at these things now than I am doing government facing meetings, which has been enlightening.

But I think that a few things like the myth I mentioned that the DOD can’t use commercial. You’re using a ton of commercial, you’re just not doing it the right way. How do we work through the understandings and awareness of how to exploit and take advantage of that, I think, is really important. Working through and how do we develop that trust and that collaborative environment. I think exercises are one of the ways to do that. Call us, we’ll come participate in the war game. Let’s figure out how to come together as a community and do that, because there’s a lot of roles to be played and I think there’s the right people to play. We just got to sort that out.

Col. Frederick “Trey” Coleman:

Thanks, Lance. Joe.

Joseph Sublousky:

Thanks again for coming, and talking, and allowing us to see the light, I guess I’d say, because I can’t see anything else. SAIC is working towards, I would tell you, again, it sounds cliche, but it’s enabling decision dominance at the contested edge because it covers those guiding principles for ABMS. We are working hard to make that happen. We’re doing it in a number of areas, whether it’s a digital infrastructure, consortium membership, whether it’s cloud-based command and control for customer number one, NORAD NORTHCOM, or whether it’s modernizing the Air Operations Center, all of which SAIC is intimately involved in. If not the prime, we concerted efforts in doing work there. But there’s synergies around that.

I’ll share with you, my intro was I’m an atypical communicator. I met an individual here that was a three Delta, which is a enlisted communicator who then became a 17 Delta cyber officer who is now an ABM, which I believe, I’ve listened in a couple of these symposiums and conferences, that it’s going to take a different person in the future in order to operate in the battle spaces and the tactical areas that we’re going to operate in the future. We got to start building those. Industry is trying to build them as fast as possible to provide the capabilities, and SAIC is working those capabilities to support the architecture. Data, cloud, edge, and transport.

Col. Frederick “Trey” Coleman:

Thanks, Joe. Thanks to each of you guys, and your companies, and everybody in this room for getting after this, for trying to solve these really hard problems, and deliver operationally relevant ABMS and command and control. Thanks for being here.