Main Topic: The software crisis in critical infrastructure, particularly in the aviation and logistics sectors, and the need for modernization and collaboration between the public and private sectors.
Key Points:
Participants:
Takeaways:
Today’s critical infrastructure—air traffic, logistics, defense—is powered by legacy software. And that’s a problem.
In this episode, recorded live at the a16z American Dynamism Summit, a16z partner Leila Hay sits down with Phillip Buckendorf, CEO of Air Space Intelligence, and Lt. Gen. Leonard J. Kosinski (Ret.), ASI’s Chief Strategy Officer and former Director for Logistics on the Joint Staff for the Pentagon.
They explore why software is now a weapon system, how dual-use tech can harden both civilian and military infrastructure, and what happens if we don’t modernize fast enough.
Resources:
Find Phillip on LinkedIn: https://www.linkedin.com/in/phillipbuckendorf/?locale=en_US
Find Lieutenant General Leonard J Kosinsk on LinkedIn: https://www.linkedin.com/in/ljkosinski/
Find Leila on LinkedIn: https://www.linkedin.com/in/leilahay/
Stay Updated:
Let us know what you think: https://ratethispodcast.com/a16z
Find a16z on Twitter: https://twitter.com/a16z
Find a16z on LinkedIn: https://www.linkedin.com/company/a16z
Subscribe on your favorite podcast app: https://a16z.simplecast.com/
Follow our host: https://twitter.com/stephsmithio
Please note that the content here is for informational purposes only; should NOT be taken as legal, business, tax, or investment advice or be used to evaluate any investment or security; and is not directed at any investors or potential investors in any a16z fund. a16z and its affiliates may maintain investments in the companies discussed. For more details please see a16z.com/disclosures.
Stay Updated:
Find a16z on X
Find a16z on LinkedIn
Listen to the a16z Podcast on Spotify
Listen to the a16z Podcast on Apple Podcasts
Follow our host: https://twitter.com/eriktorenberg
Please note that the content here is for informational purposes only; should NOT be taken as legal, business, tax, or investment advice or be used to evaluate any investment or security; and is not directed at any investors or potential investors in any a16z fund. a16z and its affiliates may maintain investments in the companies discussed. For more details please see a16z.com/disclosures.
Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.
Host (Leila Hay)
We have a software crisis. There's just no time to wait. If you don't have that sense of urgency, we're not going to accomplish what we need to do.
Philip Buckendorf
You can build the most advanced equipment, you can produce it at the largest scale possible, but if you can't get it where it's needed, when it's needed, it doesn't exist.
Lt. Gen. Leonard J. Kaczynski
There's always been collective defense, but not necessarily collective logistics. Any one nation can't do it alone.
Philip Buckendorf
Whatever we're modernizing now, this is not going to be the last update. Software is never complete. Software is moving incredibly fast.
Lt. Gen. Leonard J. Kaczynski
The best type of war you fight is one that you don't have to fight at all.
Host (Leila Hay)
The largest companies in the world today are software companies. And many of these companies have become household names for developing fun software. Software that powers the games we play, the apps we scroll. Software that helps run our lives and manage our work.
But the world also needs serious software. The kind of software that runs the autonomous vehicles in San Francisco. The software that ensures planes take off and land safely. The software that ensures critical supplies make it to our shores and equally the front lines of our military, even in contested environments.
The challenge? Across the commercial sector and the public sector, much of this serious software is built on legacy technology. And with the world moving at the speed of software, our infrastructure gets more brittle with each passing year. When it breaks, it causes inconveniences at best and tragedies at worst.
But here is the good news. Software continues to eat the world, and the brightest minds are increasingly interested in solving these serious problems.
So in today's episode, recorded live at our American Dynamism Summit in the heart of Washington, D.C., we sit down with Philip Buckendorf and recently retired Lieutenant General Leonard J. Kaczynski. Philip is the co-founder and CEO of Airspace Intelligence, a company working to address the software crisis across some of the country's most critical public and private sector institutions, from air traffic to defense.
Lieutenant General Kaczynski is ASI's chief strategy officer and the former director of logistics for the joint staff, spending over three decades of leadership in air mobility and logistics, seeing firsthand what consequences we face if logistics are overlooked.
Lt. Gen. Leonard J. Kaczynski
It's just like oxygen. It's fine up until you don't have it and then it becomes a concern.
Host (Leila Hay)
Together with our very own Leila Hay, A16Z's go-to-market partner focused on American dynamism, the group explores the challenge of hardening America's logistical network, but also how the public and private sectors can join forces via dual-use software and the modernization and risk posture that we need from governing agencies.
So what's at stake if we don't get this right? Listen in to find out.
As a reminder, the content here is for informational purposes only, should not be taken as legal, business, tax, or investment advice, or be used to evaluate any investment or security, and is not directed at any investors or potential investors in any A16Z fund. Please note that A16Z and its affiliates may also maintain investments in the companies discussed in this podcast. For more details, including a link to our investments, please see A16Z.com slash disclosures.
The interview begins
Leila Hay
Philip, I'd love to start things off with your story. On your ASI company page, and I quote, it says, "12 years ago, you were frustrated by Germany's stagnant approach to national security and its economic degrowth mindset." Tell us about that moment in your life and why you came to America.
Philip Buckendorf
Grew up in Germany, spent some time in the UK, and then pretty much after college. So this is about 2011, 2012. I learned to figure out what I was going to do in my 20s. I knew I wanted to be in a fast-paced, demanding environment. But what I found in Europe was most of my friends just wanted to party. Germany just decided to pull out of nuclear energy to become fully dependent on cheap Russian gas. And then the top 5% in my friends and social network glorified consulting to go into consulting. At the same time, the government made it as hard as possible to build anything from starting a company to venture capital.
So while all that happened and I observed it and internalized it, I heard about Silicon Valley. I thought, that sounds like an interesting place. It sounds like everyone is just obsessed with building and technology. So a friend of mine and I traveled to Palo Alto, stayed in a hacker house. For the first three years, I slept on bunk beds and ate frozen food from Trader Joe's. But it was the most exciting environment to be in. Everyone was building in that hacker house. Everyone was thinking startups and technology.
Fast forward, I now probably spend nearly as much time or even more time in the US than I did in Germany. Our second daughter was just born here in DC last week. In many ways, I lived the American dream. Everything that I did, everything that I learned, none of this could have been built somewhere else. It was the ecosystem, the ethos, the energy, the people that enabled that. I'm very, very grateful, but also determined that it was very much the right decision on where to go.
Leila Hay
I love that. You actually started your career in the world of autonomy and autonomous vehicles. Can you talk about your career journey there and what brought you to ASI?
Philip Buckendorf
When KD, Lucas and I started ASI, we were the ultimate outsiders. We weren't pilots. We were not in defense before. We were not logisticians. We worked on autonomous driving. This was around 2017, 2018. Autonomous driving was very popular, very hot. While many liked that, we didn't. It felt overly crowded. We started this company with a simple question: what are other modes of transportation that require better software?
The first six months of ASI, we went to operation centers and wanted to understand the state of software, the state of technology, no matter if that is in maritime or in air operation centers. To some extent, we expected or hoped to see science fiction. What we saw was the most ancient software possible. That made it very, very obvious to start this company. It was a mission to enable the world's most critical operations and optimize the most valuable assets and infrastructure that we have as a country. That's how we got started.
Leila Hay
Fascinating. Leo, I'd love to hear about you. I know that recently in the Joint Chiefs serving as the Director of Logistics, Three Star General, you just retired. What brought you to ASI?
Lt. Gen. Leonard J. Kaczynski
I spent over 30 years of my career in the military, starting with air mobility operations, and then the last seven years, really logistics. After I retired, I got the advice to give yourself about six months to figure out what's next after doing something for that long. I knew what I was passionate about: national security, logistics, optimization type things. I had a chance over that six months to meet different companies, see different technologies, and see a lot of things going on.
But when I met Philip and the team at ASI, something was unique and compelling to me. Distribution platforms and planes and ships are all quite important, but it really comes down to the data. To be able to access that data, to be able to optimize and figure out what we need to do. That was something I struggled with in the Department of Defense — just being able to access, understand, and really optimize the things we need to do now and in the future. The combination of that piece being an exciting startup, not just supporting the military but also the whole commercial sector, which is hugely important for both.
Leila Hay
Absolutely. And can you tell us a little bit more about your career prior to ASI?
Lt. Gen. Leonard J. Kaczynski
I started off initially going to be an engineer. I went to graduate school for industrial engineering, optimization type things, neural networks back 30 plus years ago before we really had processing power to do that. Then quickly went into pilot training and flew mobility planes for many years.
My first real foray into broader logistics was about seven or eight years ago. I was a director of logistics for U.S. Africa Command out of Stuttgart, Germany. That was also during the pandemic. Working with Department of Defense logistics and infrastructure, trying to move around Africa — just the size and scope. Then you add on the pandemic. Then I went to Japan for a command assignment and came back to the joint staff as a director for logistics with Ukraine going on, support for Israel, everything else. I realized challenges with our defense industrial base, challenges with what we have. One of the main efforts was that data software piece, which we just weren't very good at. We were trying hard, but had a lot of catching up to do in the Department of Defense.
Leila Hay
Makes a lot of sense. So you've been all over the world and we're just seeing these common core challenges across everywhere you were. A lot of it is around data software.
Well, I'd love to kick off and first talk about the air domain. Obviously, ASI got its start in the aviation space. It's an area where we've seen a lot of challenges. On the one hand, we as consumers are told that flying is the safest mode of transport, and statistically, that's correct. On the other hand, we're seeing headlines every day. We're seeing news about air traffic control shortages, staffing challenges. Can you just help us paint a picture of the aviation industry and what the state of play is?
Philip Buckendorf
First of all, it is definitely by far still the safest domain and mode of transportation. But we're fundamentally looking at three different problems.
The first one is staffing. There's a significant staffing shortage right now in the industry. Why is that? You've seen a lot of retirements throughout the COVID pandemic. Training was not happening at the same speed during the COVID pandemic. More broadly beyond air traffic control, the industry might have also lost the ability to attract the very, very best talent. We can talk more about what that also meant for software.
So we have a staffing shortage on one hand. Then we equally have a software crisis. We have legacy software that is faltering, that is falling apart. Whenever it happens, you have these massive outages that are incredibly consequential to the entire industry. And then you have very outdated infrastructure.
What is not talked about enough is how they are actually all interconnected. Let me give you an example. Staffing and software go hand in hand. If you have better software that is much more intuitive, you can train people much faster. Even more, if you have software that is supporting the operator, that operator is a lot more productive. You're minimizing workload. If you don't have to do 10,000 clicks, but just a few, or you have AI that is assisting you in your decision-making, it can be much, much more productive.
That leads to second-order consequences. If you're increasing productivity, that means you can actually pay people more. That means more people want to operate or work in the field. What is not considered enough is how staffing and infrastructure are fundamentally software problems. You can't separate these three areas and look at them in an isolated way. Software is eating the world, and that is very much true for this domain. Internalizing that, as there's a mandate to modernize now and pull this sector forward, looking at it through the software lens is absolutely critical. Some of that is happening.
Leila Hay
It sounds like there are all of these challenges, but they're being looked at in silos. People are trying to say there's a people problem here, an infrastructure problem here, a tech problem here. But actually these things are all connected, and if we can modernize them, that's how we're going to be able to move faster.
Philip Buckendorf
Absolutely. You're training a new generation. If you're training a 25-year-old air traffic controller, that individual grew up with iPad, Snapchat, Google Maps when they drive a car. The generation that has retired or is about to retire grew up with IBM green screens. They are familiar with how to use that technology. They used that technology for the last 30 years. But the new generation being trained now is not familiar with those legacy tools. It's absolutely essential that software is modernized and brought up to speed with what people are used to using from a software quality perspective.
Leila Hay
I'd love to double click on that. We're here at the American Dynamism Summit in Washington, D.C. We all are grappling with the fact that there was a tragic accident here in our city just a couple of months ago. A commercial airline collided with a military copter. Philip, I believe you were at Reagan National Airport at the moment that that happened. People assume that good safety records equate with good technology, but it sounds like we're actually dealing with a lot of legacy technology. Can you help us understand what that looks like today?
Philip Buckendorf
The way I would frame it is it's very much a philosophy problem. The philosophy on what software should look like might be a bit broken. It boils down to three issues.
The first one is that software and compute are very much connected. If you have software systems that are deeply coupled with the compute power, it's very hard to modernize anything. Specifically, if you're dealing with an industry where you have facilities all over the country, you cannot just launch an update over the air and all the software is updated. That doesn't work. You would literally have to go from facility to facility to update the software or patch things. Every single time you're running at risk — can compute actually handle that new software update?
The first part that has to happen when we think about modernization is how do we separate software and compute? It's essential because whatever we're modernizing now, this is not going to be the last update. Software is never complete. Software is moving incredibly fast. The separation of software and compute is absolutely essential.
The second part is that historically, software in this domain has been built as if it would be hardware, while the entire world is moving towards a direction where even the hardware companies build hardware as if it would be software. It's in many ways the inverse. Whenever there's a modernization effort, no matter if this is with the government or on the commercial side in air operations, a program is started, it's funded. The first thing that happens is a thousand-page documentation is written. Already tens of millions of dollars are spent on just writing the documentation. No software built yet.
Nothing shipped. Nothing works yet. Just documentation. So we're already tens of millions of dollars into just documentation. Then over the next 10 years, for hundreds of millions of dollars, software is written from scratch for that particular problem area or against those requirements. Ten years later, all that is magically considered working and finished and rolled out. By that time, it's already out of date and antiquated because the state of technology has changed a lot over those 10 years. Then it's somewhat maintained for the next 20 years. We all know this is not how software is built given how fast it's changing and moving.
The third one is that the companies that historically participated in the space can no longer attract the very best software engineers. The very best software engineers do not want to work in that ecosystem with those structures. They want to build rapidly. They want to build close to the user. They don't want to be handed a list of 10,000 requirements and just write code against that.
The combination of all these things means you are in a setup that does not produce the software that should be produced. If you wrap all of that into an acquisition framework that is incentivizing those philosophies, you've got a really big problem at hand. That is where we are right now. But I think things are about to change.
Lt. Gen. Leonard J. Kaczynski
We may talk about this later, but when I think about the Department of Defense, the way you describe that ecosystem and our challenges is exactly the same, especially in the logistics business. Within each service — the Army, Marine Corps, Air Force — within each subunit, as you go down, legacy systems that were programmed by great people decades ago that weren't designed to be able to connect. We spend so much time trying to ad hoc systems together when we really should be thinking forward to have that clean sheet type of software that can be iterative.
There's just no time to wait. You have to move fast. Even moving fast, it still takes some time. But if you don't have that sense of urgency, we're not going to accomplish what we need to do.
Leila Hay
On that point around urgency, we have to fix the status quo. It's exciting that this administration seems very committed to moving fast. Would love your perspective on how fast we can solve some of these big challenges.
Philip Buckendorf
Things will only change if the momentum stays what it is right now. If there's a real urgency for change. President Trump and Secretary Duffy set the direction of the mandate. The next step is for Congress to fund the modernization efforts at the FAA. I would argue that in many ways, it's one of those areas where there's strong bipartisan support. It's very hard to argue why not to modernize air traffic control systems and why the U.S. should not have the very best software in that field. Everyone agrees that we should have the very best.
At the same time, it's important that the guidelines are put in place on how to spend that money and how to not repeat the same mistakes from the past. We don't need to spend 10 years on custom development if we can actually purchase software that already works in the private sector, that is already commercially deployed, that we can literally just purchase and use as is, maybe make a few modifications. That is a lot more efficient, allows for much faster modernization, and it's also the safest because it's already proven.
The next two steps are making sure the resources are there. It's fair to say the FAA has historically not had, or most recently has not had, the resources they need to modernize. But then making sure the structures are done the right way so we're not repeating the same mistakes over again.
Leila Hay
Absolutely. And when you say proven software, would love to understand what exactly you mean by that. How has ASI worked with the commercial sector and the DOD already to help provide some of these capabilities?
Philip Buckendorf
To give you some examples: when it comes to some of the modernization efforts that the FAA will pursue around air traffic management, a lot of that software that is needed, a lot of the capabilities, we already have commercially deployed with the airlines. In many ways, a lot of the airlines are advocating that they would love the FAA to use this type of software. Instead of building that capability from scratch for hundreds of millions of dollars — and that's historically been the idea — why not use something that is already deployed, that is already used by some of the largest airlines in the country? Because it already works.
The same has been true when we started working with the U.S. Air Force. The reason we were able to deploy within months and have seen our software being used in live operations was simply because it already worked in the commercial sector. It was already deployed there in a 24-7, 365 days a year type of fashion.
There are certain areas where dual use is a good idea and certain areas where dual use is not a good idea. But when it comes to some of these industries where the private sector and the public sector have to collaborate very closely together, dual use is a phenomenally good idea. Not just because it's more efficient, but it also enables more collaboration. When it comes to the national airspace system, it's a system that is managed by the government, but it's used by the private sector — the airlines.
Leila Hay
At the risk of bringing a Silicon Valley term to the table, there's a network effect here.
Philip Buckendorf
100%.
Leila Hay
You want everybody singing to the same tune. If you have a platform where everyone has access to the same data, then everything can be more efficient.
Philip Buckendorf
Yep.
Lt. Gen. Leonard J. Kaczynski
Just adding from my experience in the Department of Defense aspect, people may not realize that day-to-day, the U.S. military uses commercial transport — trucking, rail, air, sea. For any kind of contingent or disaster type of escalation, we would have to use even more. It's the same resources, the same need for that collaboration. We need to be able to really work well together on the same system and platforms.
Leila Hay
Absolutely. That brings me to the next thing I wanted to double click on: how ASI has been expanding into areas like logistics. Can you maybe walk us through what exactly that looks like with the DOD? It feels like a black box for many folks. And when we say "contested logistics," what does that exactly mean?
Lt. Gen. Leonard J. Kaczynski
"Contested logistics" is actually a military term. Every military term has definitions and doctrine and even secret stuff that we discuss. But just to understand the concept: most of us order things online. When you order it, you worry about the price, maybe when it might get there. But most people have no concern about where it's built or the supply chain when it gets there, unless it's going to be delayed or you realize there's some weather system.
Any given day, you have contested logistics. It's just that the consumer, and actually even the CEOs of some companies or even senior four-star generals, may not think about logistics day-to-day because it hasn't been a problem in the past. The idea of contested logistics is that whether it's weather, maintenance, or other situations, you're going to have challenges. How do you understand that, predict it, and optimize? That's what ASI's type of software does.
From the military perspective, contested logistics means adversaries will look for your vulnerabilities, which would be in our supply chain and logistics pieces. To outdo them and maintain what you need to do, you need to understand where your vulnerabilities might be, have that resiliency, and be predictive to go around.
Another example: we in the military move an aircraft carrier or a group of soldiers somewhere. You make that decision, but people don't often think about the whole supply chain — the tail — the food supply, munitions, everything else to get them there and get them back. That's hugely important because no matter what great weapon system you have, if you can't supply and sustain it and move it where you need to, it's not effective.
Logistics experts do think of it as a weapon system itself. It's your competitive advantage if you can leverage it. If you can't and you don't see it, it becomes your greatest weakness and vulnerability. We want it to be your competitive advantage by providing this capability.
Leila Hay
It's almost like electricity or water. You don't think about it working or not working until you flip the switch and your light doesn't come on or you turn the faucet and the water doesn't run. It's really the backbone of everything.
Lt. Gen. Leonard J. Kaczynski
We've seen that from day-to-day — the pandemic, when face masks or toilet paper were scarce. For the military, I saw that with support to Ukraine, where there were munitions and things we were moving, and just the resources to do that, the supply chain to be able to replenish those. As you start thinking through potential crises as things escalate, you want to be able to predict that and understand it better. It's just like oxygen. It's fine up until you don't have it, and then it becomes a concern.
Leila Hay
Philip, what's your perspective?
Philip Buckendorf
To echo what Leo shared, we talked about air traffic control and air operations before. Same there. You just assume things are working until they don't. That's why sometimes those sectors are a little harder to gather everyone's interest or to make sure the funding is there. It's very easy to spend money on the fancy weapon system, the autonomous drone, the new kind of high-tech equipment, because it's physical, it's visible. But when it comes to the silent software that runs in the background that enables all of this to work, that allows the most advanced equipment to go where it's needed, when it's needed, that's sometimes too much of an afterthought.
You could argue: you can build the most advanced equipment, you can produce it at the largest scale possible, but if you can't get it where it's needed, when it's needed, it doesn't exist.
Leila Hay
Why has that been such an underserved topic? To your exact point, when we think about defense and some of these new capabilities, we're talking about autonomous drones and counter-UAS capabilities and electronic warfare. We haven't been talking nearly enough about logistics. But we have just been through the pandemic. We've seen the disruption in our personal lives. Why do we still have this disconnect?
Lt. Gen. Leonard J. Kaczynski
Human nature wanting to go back to the status quo. You have all this stress and you just want to take a deep breath and go back to what seems comfortable. We've been able to be comfortable for the last few decades because we haven't had a global war, fortunately. It takes pressure points like the pandemic to really see where our vulnerabilities are. That's where there was a lot of investment taking place. But then that human nature of just easing back — same with air traffic control. Great people working on that, but they deserve a much better system, a software system at least from the 21st century. You hope it doesn't have to come to something where there's almost a crisis.
The other thing is we've been over the last several decades just accustomed to just-in-time logistics. Logistics has just been a cost area. You're worried about cost, reducing that. It's all well and good if there's nothing out there threatening that supply chain, but you realize that just-in-time isn't in time at all if you can't get that part or that supply in need. Companies that I talk to are realizing this — that their competitive advantage can be in that resilient understanding of the supply chain and logistics piece. Instead of thinking of the cost, it should be something that provides profit, or for the military, more deterrence and capability.
Leila Hay
We've been talking a lot about this. I love it. I want to go back to the dual use topic. That's an area where we spend a lot of time. We think about companies that have an existing commercial capability that is doing great work in the commercial sector. They can take that exact same capability to the DOD. Walk us through how ASI fits into that puzzle and some of the areas where you all are going to be able to lean in.
Philip Buckendorf
There are certain domains, certain capabilities where building something specific for one sector is absolutely the right way to go. A new missile or an aircraft carrier — there's not much commercial applicability for that. Logistics is one of those domains where I would argue it's the flagship example where you want to have dual use.
Why is that? Leo already alluded to it. From a defense perspective, a lot of the capacity resides in the private sector on the commercial side. That goes way beyond the civil reserve fleet. It's the same infrastructure that is used — the same ports. And guess what? Our adversaries are actually trying to deploy their software into allied ports. The Chinese are really good at making sure their software runs in ports. They're giving it away for free. And there's a reason why they do that.
And then from the other side, let's say the private sector, if you're providing mission-critical infrastructure like transportation, you want to make sure you're using military-grade software because the stakes are just so high. So you want these two sectors to be very close. Yes, there needs to be separation, but there's nothing better than actually running very similar—or the same—software stack on both sides so that these two sectors can communicate, collaborate, and share data when it's needed.
It shouldn't feel in the moment of crisis like, "Oh, now we need to understand what the software stack or data structures look like on the other side so we can coordinate." You don't want to figure that out in the moment of a crisis. You want to have that done before.
And that's very much what we're trying to do at ASI. We want to make sure that the very best logistics software—the very best software to operate critical operations—is deployed with the companies doing that in the private sector as well as with the government, and then enable these two sectors to collaborate. In many ways, I always say it's the truest form of dual use, because we're not only sharing technology, but we're also enabling collaboration and communication between these two sectors.
I think you can make the argument that you want to use similar ideas or a similar mental model when it comes to the collaboration between the U.S. and its allies. Specifically on the side of military logistics, it is always about integration with our allied partners. How can we tap their infrastructure? How can we use some of the capacity that they have? How can that all be coordinated? There are times where you want to have more separation, and there are times where you want to have tighter collaboration and more sharing, and you need to have the infrastructure in place that allows for that.
In my previous job, I was a U.S. rep for the NATO Logistics Committee. Over the last few years in NATO, there's always been collective defense, but not necessarily collective logistics. Logistics was left to each nation to do things. But the realization is that any one nation can't do it alone. So this idea of collective logistics across NATO—which the U.S. is a member of—is common sense. But they finally put it into not only a common understanding, but planning and other things to determine how best to utilize our collective logistics capabilities and plan for that in the future.
Leila Hay
If we talk about modernizing logistics for the DoD, what exactly needs to change? Is this a policy issue? Is it a culture issue? Is it an experimentation issue? What do we need to fix here?
Lt. Gen. Leonard J. Kaczynski
I think it's really thinking very differently about the software. And when I say software, in this case, I don't mean just the legacy software, but I think also what we deployed in recent years. Over the last five, ten years, a lot of the modernization that happened was just putting up new dashboards running in operation centers on bigger TVs. But we haven't really deployed software to the warfighter, to the operator.
David Yulovich put it very well when he said the world is getting a lot more spicy. It's much spicier now. And what that means is we actually need different software. When the world is stable, you can operate with near real-time displays. That means the human operator sees problems as they happen and then reacts to them. But that's not necessarily the world we're living in. The world is a lot more uncertain now. I think that means we need to have software that shows the operator what is about to happen in the operating domain and how they need to adjust. I would say anticipation, in many ways, is a new high ground.
When it comes to software, we've seen three evolution steps. The first evolution was compute. In the 1970s and 1980s, we had workstations. They were not connected. You input some data, there's some optimization process or form of processing happening, and then you have an output. The next evolution was when all those workstations became connected—the internet. So a lot more data came online. The next step from there was extending that to the internet of things. A lot more sensors came online. So the big challenge was how do we fuse all that data? How do we make sure we have a great common operating picture? I think that was very much the focus over the last 15 years or so—data fusion and displaying that data and making it accessible to these critical industries and the military.
I think now we're at the very beginning of a new revolution, which is prediction machines. How do we actually build interfaces that are predicting what is about to happen? What is the state of the operating domain, the state of the supply chain, the state of the assets we're operating—not just right now, but over the next hours, over the next days, over the next weeks? How can we forward simulate that? That is an enormous advantage for an organization if you have that capability. Now we need to make sure we're rolling that out and embedding it in our operations.
From an ASI perspective, we pioneered some of that work, very specifically in the air domain. But we need to do that more broadly now across all domains, across both sectors, private and public.
Philip Buckendorf
And then I think the second part is we need to enable much tighter collaboration between the two sectors. We talked about that already a little bit, but the key issue is going to be how do we get more capacity ASAP? Yes, we can think about how do we build more ships and all of that, and there are clear needs for that. But again, all those things take time. At the same time, there is already a lot of capacity within the Western Hemisphere between the U.S. and its partners and allies, as well as between the private and the public sector. How do we enable collaboration and communication to make sure that capacity can be used effectively and efficiently?
And then lastly, I think it's important that these sectors are not just an afterthought. How do we make sure these sectors get the funding, the care, and the attention—not just when things fall apart, because that means it's too late—but how do we make sure we invest in these sectors proactively before things fall apart?
Leila Hay
I think the last point about funding and prioritization is key. From policy, logistics is fundamental to everything we do, and we need to fund and prioritize it.
Lt. Gen. Leonard J. Kaczynski
The other thing—and this came from your air traffic controller explanation about the skill sets it took in the past to get proficient with older systems—I had a big challenge in the joint staff as a director for logistics in creating joint logisticians. In military terms, "joint" means you've got the Army, Air Force, Navy, Marines, and each of those have perspectives. If Air Force wants to move something, they think about doing it by air. Navy, by sea. Army, by ground. First, you have to be an expert in that kind of logistics—air logistics, for example. That takes several years, not a decade. Then opportunities to become a joint logistics expert, which means you have to understand all of those, takes a lot of time. We're challenged to do that.
Not that we shouldn't strive to do that, but when you have AI decision-making tools that can enable individuals to make decisions—to facilitate instead of taking 20 years to train someone to do this—you have software that you can be trained on and still learn, but can give you the option of multimodal: just send it by ship or air or whatever the best decision is. I think that's really an accelerator for what we need to do. We should be leveraging that technology as opposed to struggling to provide one person who can do everything. And if that person's not there, then you can't succeed.
Philip Buckendorf
Exactly. If I'm a developer, I don't need to go out and buy a bunch of servers and rack and stack them in my garage. I can swipe my credit card with one of the cloud providers and focus on higher level efforts—actually build the software. So it sounds like there's a similar opportunity here for acceleration.
Leila Hay
Philip, I'd love to ask you one more question because you started to touch on the intersection of AI and logistics. If we're doing all this right and we get in a time machine 10 years from now, what are some of the problems that we're going to be able to solve with getting that right?
Philip Buckendorf
One is we will be able to do a lot more with the capacity that we have available. Two is we will be able to harden our logistic networks in an uncertain world or uncertain state of the world. I think no matter how some of these crises are going to pan out, the probability is very high that the next few decades are going to be a bit more dynamic and uncertain than the last two decades were. That means that every form of supply chain, any piece of mission-critical infrastructure, will in one form or shape be disrupted. How do we have software that allows us to very quickly reroute stuff so that the impact of that uncertainty doesn't impact the warfighter, doesn't impact civilian infrastructure? Because we have the software systems in place that are able to balance that out and reroute things.
Again, the uncertainty comes from geopolitical tensions, but equally from sanctions and from a climate perspective. Increasingly more volatile weather has a huge implication, for example, to the national aerospace system and travel. How can we have logistic systems that are able to anticipate these challenges and then balance things out when needed because you have that predictive capability?
Lt. Gen. Leonard J. Kaczynski
No one I know wants to fight a war, but we want to be able to prevent that. Philip already alluded to it: no matter what ships, aircraft, and high-tech weapons you have, if you can't sustain them, if you can't move them where they need to be, the adversary knows that. Or even if you can move them where they need to be, but you can't keep them sustained for any given amount of time, that doesn't provide deterrence. That's something fundamental that we've maybe not had to think about as a nation for many decades.
Having that ability to provide deterrence based on understanding and really fully taking advantage of logistics capability allows us to be stronger. Hopefully, fast forward 10 years from now—I can't tell you everything that will happen—but we will still be able to deter and make sure this is a free and open world because of that. If we don't have that capability, it makes anything we do from a national security perspective that much harder. And I don't want it to be that much harder for our military men and women out there.
Leila Hay
What are the risks if we don't get this right? If we don't modernize, what's at stake?
Lt. Gen. Leonard J. Kaczynski
There should be a sense of urgency because there's no time. There's a book out there called *The 100-Year Marathon* by Michael Pillsbury. The premise of the book is that adversaries like China have been looking at our vulnerabilities and supply chains for quite some time. In a marathon, even if Philip's a much faster runner, but if I start running today and he doesn't start until tomorrow, I probably will win. This is the sense of urgency to catch up.
Our risks lie in our ports, lie within our supply chain. You see news releases about hacking into water supply systems in places in Texas. You wonder why that's all happening. If you look at Sun Tzu's ancient strategy, the best type of war you fight is one you don't have to fight at all. We as a nation have been able to power project and do things from everywhere around the world. It's been great for the United States. But in this age of contested logistics with hypersonic missiles and cyber and space threats, our ability not just to operate abroad, but to leave our own ports and move rail and everything uncontested no longer exists. It probably hasn't existed for a few years or more. That's really where the risk is.
That's why the risk of not taking action, not drastically updating your system to the way cutting-edge industry operates, is so high. The Department of Defense built its logistics system 40 years ago and has done minor updates to it. That's not the way we need to operate in the future.
Philip Buckendorf
And from a geography perspective, this stuff is so important. In many ways, the greatest asset for the U.S. is you've got a massive ocean to the west and a massive ocean to the east. It's very hard for any adversary to attack the U.S. on its homeland given you have the oceans. But at the same time, from a global power projection perspective, we need to be able to overcome these vast distances over the oceans. That requires logistics. Our adversaries know that. Their strategies are very much about how to cripple key logistic infrastructure—whether in the homeland or with allies and partners—to make sure the U.S. is limited in its capability to get equipment where it's needed, when it's needed. That requires software as much as physical infrastructure to allow us to maintain the ability to project power globally.
Lt. Gen. Leonard J. Kaczynski
Just some tangible examples. Look back to the Colonial Pipeline. Those on the East Coast couldn't get gas for quite some time. Look at the Suez Canal back in 2021. A ship got stuck there for six days. Billions of dollars of trade were affected. Those things had different reasons—no nefarious actions in particular—but you can just imagine those vulnerabilities. If we're in a crisis, you can't stop. You're going to have to be able to overcome that. That's why this predictive logistics capability, AI-enabled, is a way we would have to be able to look and think to come up with solutions.
Philip Buckendorf
And then how do we understand the threat profile for every single node in the system? How do we understand the threats that might impact key infrastructure? We see a lot how underwater sea cables are being attacked. Every key node in the system is a vulnerability. How do we make sure we have the technology in place to detect any threats, no matter what form or shape they come in? And then how do we quickly counter that by relying on other nodes more than particular nodes that are impacted in their capacity and efficiency?
Leila Hay
Now, if you made it this far, a reminder that this was recorded live at our third annual American Dynamism Summit in the heart of Washington, D.C. If you'd like to see more exclusive content from the summit, head on over to a16z.com/american-dynamism-summit, or you can click the link in our description.