17 mars 2020 | International, Aérospatial

Air Force Acquisition Chief: Reaper Replacement Plan Should Come in FY ’22 Budget Request

The Air Force is conducting a study that will inform how the service will continue its critical intelligence, surveillance and reconnaissance (ISR) missions as it begins to phase out production of its MQ-9 Reaper unmanned aerial systems, acquisition chief Will Roper said March 10.

The service plans to reduce the General Atomics Aerospace Systems Inc.-developed MQ-9 Reaper combat lines from 70 to 60 by eliminating 10 contractor-operated lines while maintaining all MQ-9 aircraft in the fiscal year 2021 budget plan. House Armed Services Committee (HASC) member Rep. Filemon Vela (D-Texas) sought clarity on why the production line would be reduced in a Tuesday hearing on Capitol Hill.

“Why the major change in plans, and how will the Air Force address its ISR gap?” he asked.

Roper told the committee that the Air Force is planning to build the “next generation” of ISR drones with a mixture of options, including “more high-end, unique” systems that will require lots of money to ensure their survivability, as well as commercial platforms that can “push the price point down” and provide attritable systems for added capacity.

“We're doing studies now to see what our mix could be, and I anticipate that will be one of our major decisions in our FY '22 budget for the Air Force,” Roper said during the hearing.

The study is being led by the Air Force's Program Executive Office for ISR and Special Operations Forces at Wright-Patterson Air Force Base, Ohio, he told a small group of reporters after the hearing. He expects it to be complete before the end of the fiscal year to inform the service's FY '22 Program Objective Memorandum (POM), which is currently in development, he added.

“It's a really great time to give [PEO ISR & SOF] an innovative program because as their portfolio appears to be trending down ... it's important that they have something that's the new version of them that's innovative, that's indicative of their future,” he said.

The Air Force has to work on dropping the cost of the counter-violent extremism mission, both in manpower and unit price, Roper said.

He added that employing commercial drone services in the defense industry could help smaller, newer companies begin to scale their production while offering the service a “much lower, much cheaper” way to sustain cost.

“Working with the Defense Department, you don't need the kind of production capacity that the globe does, so we're a pretty good first stop,” he said. He also told the committee that while the Reaper had “undeniable overmatch in a low-end fight and has certainly saved many lives, ... as we look to the high-end fight, we just can't take them into the battlefield.”

Roper warned that if the Defense Department does not move quickly to engage builders of large UAS, the market could go the same way of small, hobbyist UAS and be saturated by Chinese products, as was seen with DJI's Phantom drone.

The service's ISR portfolio could look very different in FY '21 if Congress approves its proposed FY '21 presidential budget request, released Feb. 10 (Defense Daily.) It includes the retirement of 24 Block 20/30 RQ-4 Global Hawks, including three EQ-4B drones equipped with Northrop Grumman's Battlefield Airborne Communications Node (BACN) system, as well as reducing the MQ-9 lines.

In order to provide sufficient levels of ISR with the divestment of the Global Hawk 20/30 assets and reducing MQ-9 combat lines, the Air Force will maintain and modernize the U-2 [Dragon Lady ISR aircraft] and the Global Hawk Block 40 fleets and maintain 60 government-owned/government operated MQ-9 combat lines, the Air Force previously told Defense Daily.

The service also plans to procure one Bombardier E-11A BACN-enabled aircraft through the five-year future years defense plan (FYDP), with plans to bring the total fleet up to eight by FY '26. One E-11A aircraft suffered a fatal crash in Afghanistan last month, leaving the Air Force with three in its current inventory.

Vela also asked whether the Air Force's proposed MQ-9 retirements could affect other services operating the Reaper. Marine Lt. Gen. Steven Rudder, the service's deputy commandant for aviation, said during the hearing that while the Marines recently welcomed their first MQ-9 operators at Yuma Proving Ground, Arizona, he is also looking at the “wide-open” unmanned systems industry for the service's next generations of drones.

“We hope to be able to continue to operate with the Air Force,” he told Vela. However, “We're ready to step out on our own system,” he added.

https://www.defensedaily.com/air-force-acquisition-chief-reaper-replacement-plan-come-fy-22-budget-request/budget/

Sur le même sujet

  • Indra brings the latest NATO standards for the protection of military vessels to the international market

    3 juin 2024 | International, Naval

    Indra brings the latest NATO standards for the protection of military vessels to the international market

    The company has teamed up with Navantia to implement them in a first ship destined for the export market and is moving forward with their installation in the entire Spanish...

  • MBDA place son Meteor sur le futur avion de combat KF-X

    25 novembre 2019 | International, Aérospatial

    MBDA place son Meteor sur le futur avion de combat KF-X

    MBDA est retenu par la Korea Aerospace Industries pour réaliser l'intégration de son missile air-air longue portée Meteor sur le futur avion de combat sud-coréen KF-X. La Korea Aerospace Industries (KAI), maître d'oeuvre du programme d'avion de combat multirôle KF-X, notifie à MBDA un contrat pour réaliser l'intégration du missile air-air longue portée Meteor sur le KF-X. Le contrat comprend le soutien technique des équipes de MBDA, la réalisation des différents équipements d'essai nécessaires (aéromécaniques, séparation, intégration,...) et la participation aux différentes campagnes de tests associant Meteor et KF-X. Le missile Meteor de MBDA équipe d'ores et déjà plusieurs avions de combat : Dassault Aviation Rafale, Airbus Typhoon et Saab Gripen. https://www.air-cosmos.com/article/mbda-place-son-meteor-sur-le-futur-avion-de-combat-kf-x-22081

  • 4 big problems the intelligence community faces moving to a new data system

    21 août 2019 | International, C4ISR

    4 big problems the intelligence community faces moving to a new data system

    By: Nathan Strout The Defense Intelligence Agency wants to move quickly in developing the Machine-assisted Analytic Rapid-repository System, but the massive project, which will transform how the intelligence community uses data, faces some hard problems. The Defense Intelligence Agency is responsible for informing war fighters and policy makers on the military capabilities of foreign nations. Currently, the agency relies on the Modernized Integrated Database to house foundational military intelligence, but the 20-year old database wasn't built for the 21st century data landscape. The DIA wants to replace MIDB with MARS, a comprehensive, adaptable, scalable and rigorous data environment. With more data that is better labeled and organized, MARS will allow analysts to use applications to sort and process that data to make connections they couldn't otherwise. Last year, the DIA issued a broad agency announcement to solicit industry feedback from MARS. They've spent the year going over that information and are now preparing to actually build it. “2019 was about learning,” said Terry Busch, chief of DIA's integrated analysis and methodologies division. “This was the year of prepping to get started. In 2020 we get started ... We're going to move from designing to building very very quickly." Irving Townsend, also of the DIA, added that the agency was working to make some components of MARS available to the United States' closest allies in 2020 so leaders in those countries can begin looking at how they can use that data. In summer 2020, the MARS application programming interface will be released to the public, Busch said. But even as the DIA gears up to begin building MARS, the agency has four big problems left to solve. Resolving data inconsistency Perhaps the most pressing problem with creating a unified resource such as MARS is ensuring that the data fed into the system has been labeled and handled in a uniform way. That's easier said than done. According to Busch, there are 1,300 different data standards in the Department of Defense. “I work a lot with (the National Geospatial-Intelligence Agency) and DIA because we have a very similar path for our data,” said Busch. “The NGA has done some wonderful work with some of their data standardization and modeling (...) because NGA's been in the data making business for a long time.” Making the data collected by the various agencies and services interoperable is essential for the MARS enterprise. Data storage The amount of data collected by the intelligence community that MARS needs to encompass is staggering. Hosting images and videos, like those collected by the National Reconnaissance Office, for instance, takes up a lot of space. Because of this, MARS will not actually host all of the data itself. Instead, MARS will refer to intelligence hosted by other agencies. Instead, MARS needs to be able to index that intelligence. Theoretically, users will be able to click a link to access that data hosted on other servers. The DIA will have to figure out how this solution for MARS to operate effectively. The black box problem In developing a massive dataset of intelligence, the DIA wants all intelligence to be explainable, meaning that analysts need to be able to see how the intelligence was arrived at. In other words, can analysts and systems show their work? “It's really, really important to understand that we're not going to accept a black box,” said Townsend. “Our analysts are not going to accept that.” This is a problem for intelligence agencies and contractors who don't want to reveal their methods or proprietary information. Townsend noted that companies are going to have to figure out how to explain their intelligence without giving away that information. Legacy systems Another problem with moving to MARS? Many legacy systems will not be able to move to the MARS framework. While MARS will incorporate all of the MIDB data, some legacy systems will not be able to use the new system and will instead remain reliant on MIDB. “The transition is difficult. Many of our war fighters are impinged by legacy technology,” said Busch. “There is not turning MIDB off. Not for the foreseeable future.” Busch noted that while Congress may not like funding both programs simultaneously, it is necessary until those legacy systems can be replaced or upgraded. The DIA will discuss these problems at a MARS industry day Sept. 10, where they are expected to explain what the agency wants from industry. https://www.c4isrnet.com/intel-geoint/2019/08/19/4-big-problems-the-intelligence-community-faces-moving-to-a-new-data-system/

Toutes les nouvelles