May 28, 2020 | International, C4ISR, Security
By SYDNEY J. FREEDBERG JR.on May 27, 2020 at 2:25 PM
WASHINGTON: The legal battle over the JEDI cloud-computing contract has slowed down the Pentagon's AI program, the director of the Joint Artificial Intelligence Center acknowledges. In the meantime, Lt. Gen. Jack Shanahan told an AFCEA webcast last week, JAIC will turn to a new Air Force program our longtime readers are already familiar with: cloudONE.
Cloud computing matters for AI because machine-learning algorithms need lots of data and lots of processing power. A shared cloud can offer both with far greater efficiencies of scale than any single organization's in-house network. JEDI was meant to provide a single “general purpose” cloud to all users across the Defense Department, including Shanahan's Joint AI Center. But it has been mired for months in legal battles over which company should have won the contract, Microsoft Azure or Amazon Web Services.
“It slowed us down, no question about it,” Shanahan told the AFCEA audience.
“Azure, AWS, I will never get into a company discussion. I'm agnostic,” he said. “[But] if we want to make worldwide updates to all these algorithms in the space of minutes, not in the space of months running around gold disks, we've got to have an enterprise cloud solution.”
JEDI can't be that solution today, Shanahan acknowledged, but “we now have a good plan to account for the fact that it will be delayed potentially many more months.”
For instance, as the COVID-19 pandemic spread, the Joint AI Center urgently stood up what they call Project Salus – named for the Roman goddess of health and safety – to pull data from 70 different sources, find patterns, and predict trends for US Northern Command and the National Guard. Salus went from a sketch on a “bar napkin” to a functional bare-bones system (what's called a Minimum Viable Product) in 29 days, Shanahan said. With JEDI unavailable, he turned to an existing Air Force cloud run out of Hanscom Air Force Base, which he'd previously used as head of Project Maven.
But the Hanscom-based cloud is “an interim solution that will end ... here later in the fall,” Shanahan said. “Because of that, we are pivoting to the cloudONE environment.”
CloudONE & Beyond
So what's cloudONE? Like JEDI, it's a new cloud-computing capability that the Air Force hopes will be available to a wide range of users from across the Department of Defense. Unlike JEDI, it's not a joint program run by the Office of the Secretary of Defense, but a service program, run by the Air Force.
In fact, cloudOne is part of a whole package of computing initiatives – deviceONE, dataONE, et al – that the Air Force acquisition chief, Will Roper, began pushing (and branding) aggressively last year. Further, while JEDI is meant as the Defense Department's “general purpose” cloud, Roper's many ONEs are all intended to serve a single purpose, albeit a broad one: military command and control.
Together, Roper's projects will make up what the Air Force is calling its Advanced Battle Management System. ABMS, in turn, will be an Air Force component of the future Joint All-Domain Command and Control (JADC2) meta-network to share battle data between all the armed services across all five “domains” of warfare: land, sea, air, space, and cyberspace.
Artificial intelligence is essential for JADC2, since human analysts can't pull together that much data from that many sources fast enough to make a difference in combat. The JAIC is far too small to build the whole JADC2 network – that's up to the far better-resourced services – but it can help.
“We're not here to build JADC2,” he said. “We're here to find AI-enabled solutions that stitch seams together from all the services, who're [each] developing some version of JADC2.”
The objective is to automate and accelerate the often-laborious process of bringing American firepower to bear. That “kill chain” includes everything from spotting a potential target with some kind of sensor, confirming what it is with other sensors, deciding to strike it, picking an aircraft, warship, or artillery battery to execute the strike, and then giving that shooter precise targeting data. Currently most of that requires human beings relaying coordinates and orders over the radio, typing them into terminals by hand, or even scrawling them on sticky notes because one network can't transfer data to another.
“Accelerated sensor-to-shooter timelines are so important – to me, this is what the next couple of years will be about, and each of the services has a really strong programs in sensor-to-shooter,” Shanahan said. “What we're trying to bring is the AI/ML solutions.”
To do that job, however, the JAIC needs more people and more legal authorities to conduct acquisitions on its own – although it will never be the size of the services' acquisition bureaucracies.
For example, while Shanahan initially focused on lower-risk, non-combat applications of AI like maintenance, on May 18 the JAIC awarded Booz Allen Hamilton a landmark contract worth up to $800 million for AI “to support warfighting operations [and] decision-making and analysis at all tiers of DoD operations.” But JAIC did so in partnership with the civilian General Services Administration (using GSA's Alliant 2 contract vehicle), just as it's done past contracts through the Defense Information Systems Agency and other established organizations, because it doesn't have the necessary authorities and personnel in-house – yet.
“I couldn't ask for better support,” Shanahan said, “but it's not going to be fast enough as we start putting more and more money into this capability development. We need our own acquisition authority.” In particular, he sees JAIC as a potential early adopter of the new streamlined process for software development and acquisition recently rolled out by the Pentagon's acquisition chief, Ellen Lord.
The JAIC also needs to get bigger. Founded in summer 2018 with just four staff, JAIC has now grown to 175 personnel (counting contractors) and must keep growing, Shanahan said. But that larger staff won't include Shanahan: JAIC's founding director retires from the Air Force next month.
https://breakingdefense.com/2020/05/joint-ai-center-turns-to-air-force-cloudone-as-jedi-stalls/
May 20, 2022 | International, Aerospace, Security
Pushing back initial operational capability of the CC-295 will disrupt SAR pilots and maintenance technicians preparing to transition to the new aircraft.
September 26, 2018 | International, Naval, C4ISR
By: David B. Larter The Navy has to get software updates and patches to the fleet within days if it's going to win in the future, the Department of the Navy's acquisition boss said Sept. 25 at Modern Day Marine. James Geurts, assistant secretary of the Navy for research, acquisition and development, said the fleet has been working on the rapid development of software to get needed upgrades to the ships ahead of pier-side availabilities, a pace he said was too slow for the modern battlefield. “We recently did one of our proof-of-principles to say: ‘How do you take ... software, get it system certified, get it cyber certified then get it out over the airwaves, uploaded on to a ship and into the combat system in 24 hours,” Geurts said. “My view is unless we get to the point where I can identify a software requirement, whether it's an [artificial intelligence] algorithm or something, find the solution, get it checked out on the network, give it whatever cyber-proofing it needs and get it into the fight in less than a week, we are not going to be successful in the long run.” The Navy has increasingly found that its current systems are capable of adjusting to new threats through software upgrades rather than buying new systems and installing them, a time-consuming and cripplingly expensive process that has been the norm in years past. Geurts said the Navy had to have a software architecture that was amenable to rapid upgrades so that developers would not need to re-test the underlying architecture each time a patch or fix is uploaded. Furthermore, the service also has to develop cyber security standards that don't just weigh whether or not something can be compromised but begin to think of it more in terms of risks associated. “The answer isn't yes or no, it's ‘Commander here is your risk.' And then weigh the risk of doing that [upgrade] versus a potential cyber impact so that commanders can make reasonable command decisions. Because there is always a risk to not doing something. We often talk about the risk of doing something, we don't often talk about the risk of not doing it.” Geurts told a gaggle with reporters after the talk that he was not talking about uploading whole new programs that sailors might be unfamiliar with but more iterative upgrades. "Don't take that to an extreme to where we will load on something that nobody has ever seen before, but it could be that there is a particular issue or new need, and you can envision us testing and training that shore-side, making sure it's right – we don't want to wait for the ship to come home we could potentially blast that out [to the fleet.]" The Navy is also working more with having digital doppelgangers of its combat system on board its ships so that new technologies can be tested by the crew and commanders before its uploaded into the main combat system, a hedge against reaping unintended consequences by uploading a feature or patch without knowing exactly how it will fit into the ship's systems. "The other thing we are doing a lot with is digital twins, where [the ship] might have the combat system that it's fighting with as well as a digital twin,” Geurts explained. “So you might be able to upload that new feature in the digital twin so you could have both, then it's up to the commander whether it's something you adopt or not.” https://www.c4isrnet.com/digital-show-dailies/modern-day-marine/2018/09/25/on-the-new-battlefield-the-navy-has-to-get-software-updates-to-the-fleet-within-days-acquisition-boss-says
October 2, 2023 | International, Naval
The Ministry of Defence has awarded £3.95 billion of funding to BAE Systems for the next phase of the UK's next-generation nuclear-powered attack submarine programme, known as SSN-AUKUS.