Back to news

February 18, 2022 | International, Aerospace, Naval, Land, C4ISR, Security

Un rapport parlementaire évoque l’idée de porter le budget de la Défense à 2,5% du PIB

DÉFENSE

Un rapport parlementaire évoque l'idée de porter le budget de la Défense à 2,5% du PIB

Dans un contexte où un conflit de haute intensité n'est plus considéré comme une hypothèse d'école, les députés Jean-Louis Thiériot et Patricia Mirallès estiment que la remontée en puissance des forces françaises doit se poursuivre et garantir la hausse annuelle prévue de +3 Md€ jusqu'en 2025. Et encore, il ne s'agit que du minimum. « Sous réserves de rester avec les mêmes ambitions, il y a un besoin complémentaire de 20 à 30 Md€ sur la prochaine LPM. Ce qui mène, grosso modo, à un effort de 2,5% du PIB (...) pour avoir notre modèle d'armée complet », a expliqué Jean-Louis Thiériot, lors de l'examen d'un rapport sur la préparation à la haute intensité, co-écrit avec Patricia Mirallès. Les deux députés ont livré quelques déficits capacitaires dont souffrent actuellement les forces françaises. S'agissant de l'Armée de l'Air et de l'Espace, le nombre de ses avions de combat est insuffisant ; ses capacités en matière de transport aérien médian devront être renouvelées (les C-235 n'étant pas éternels). Et la question des hélicoptères de transport lourd reste posée. Pour Jean-Louis Thiérot, porter le budget des armées à 2,5% du PIB aurait un réel bénéfice pour l'économie française : « un euro investi dans la défense rapporte davantage. (...) c'est un secteur industriel vital pour la France, réparti sur tout le territoire (...) permettant à la fois d'avoir l'outil de défense dont on a besoin mais aussi de développer des technologies qui nous servent sur d'autres marchés », a plaidé le député.

Opex360 du 16 février


On the same subject

  • Report slams Norwegian Navy for training, safety shortfalls in the run-up to frigate sinking

    November 13, 2019 | International, Naval

    Report slams Norwegian Navy for training, safety shortfalls in the run-up to frigate sinking

    By: David B. Larter WASHINGTON – The bridge watch team on the stricken Norwegian frigate Helge Ingstad was distracted, inadequately trained and failed to take adequate precautions while transiting close to land, according to an accident report released Friday by the Norwegian government. The watch standers on Helge Ingstad, which collided with the Maltese-flagged tanker Sola TS and subsequently sunk outside Sture Terminal near the mouth of the North Sea, were busy conducting a watch turnover and attempting to conduct training during the navigation in the channel, which it was conducting at 17-18 knots. “The Navy lacked competence requirements for instructors. The Navy had assigned the officer of the watch a role as instructor which the officer of the watch had limited competence and experience to fill,” the report reads. “Furthermore, the Navy had not given the officer of the watch assistant sufficient training and competence to operate important bridge systems while training the officer of the watch assistant trainee at the same time.” The Norwegian publication VG reported last December that the ship's captain, Capt. Preben Østheim, was asleep in his cabin during the transit through the strait near Sture, which is less than three miles across at its narrowest point. The report, which also faulted the tanker for failing to mitigate potential risks and the vessel traffic control service for inadequate monitoring, takes special aim at the Navy for a lack of qualified navigators, and for short-changing the training of junior officer, leaving bridge watch teams underqualified. “As a consequence of the clearance process, the career ladder for fleet officers in the Navy and the shortage of qualified navigators to man the frigates, officers of the watch had been granted clearance sooner, had a lower level of experience and had less time as officer of the watch than used to be the case,” the report found. “This had also resulted in inexperienced officers of the watch being assigned responsibility for training. The level of competence and experience required for the lean manning concept (LMC), was apparently not met.” The accident report shows that the bridge team confused the Sola TS for a stationary object on land, and because the watch standers were distracted with training, they were not fully engaged with monitoring the communications on the radio. “A more coordinated bridge team with more information sharing would have been more capable of detecting the tanker sooner,” the report said. “Achieving good teamwork is particularly challenging in the case of bridge teams whose members are constantly being replaced. “Furthermore, the bridge team was part of a culture characterized by great confidence in each other's skills, and this may have contributed to the perception of them being in full control of the situation and thus less vigilant and sensitive to weak signals of danger.” The report is part one of a two-part report and only encompasses the actions that led to the collision. Further findings about the actions after the collision will be released as part of a second report to be released later. ‘Not Particularly Demanding' According to the report, the transit through the body of water known as the Hjeltefjord “was not considered particularly demanding, as the fairway is open and offers a good view all around,” the report found, which likely contributed to a sense of complacence among the crew. That echoes the sentiments of the Capt. Østheim, who told VG he didn't think he needed to be on the bridge during that transit. “After 12 years at sea, I know the coast as my own pocket, so I know exactly when I need to be on the bridge and when I can rest,” Østheim told VG. There is generally little traffic through the channel and there is no traffic separation scheme. The Sola TS, which the report said was likely creating some visual confusion for Ingstad's watchstanders because of its illuminated deck lights at night, announced it was underway on the radio during the exact time that Ingstad's watchstanders were turning over, likely causing them to miss the transmission, the report reads. “At the same time as Sola TS notified of her departure from the Sture Terminal, the watch handover between the officers of the watch started on HNoMS Helge Ingstad, while the officer of the watch trainee continued to navigate the frigate,” the report reads. “During the watch handover, the officer of the watch being relieved and the relieving officer of the watch observed an object at the Sture Terminal, to starboard of the frigate's course line. The ‘object' was observed both visually and on the radar display in the form of a radar echo and AIS symbol. The two officers of the watch discussed, but did not clarify, what the ‘object' might be. “Both officers of the watch had formed the clear perception that the ‘object' was stationary near the shore and thus of no risk to the frigate's safe passage.” The situation was made even more perilous by the fact that Ingstad did not have its Automatic Identification System on, which would have notified traffic service and Sola TS of Ingstand's location. Traffic Service lost track of Ingstad because operators had their displays zoomed in too far, the report found. Collision As the Ingstad came closer to the terminal, the Sola TS, which the officer was convinced was a stationary object by the terminal, was appearing on radar to have made some distance between the pier and the water, but the officer was still not sure it wasn't a stationary object becoming more clear on the radar screen because Ingstad was closer to it. “A more experienced officer of the watch would probably have had greater capacity to pick up on weak signals of danger and be better equipped to suspect that his/her own situational awareness suffered from misconceptions,” the report read. “The officer of the watch thought, however, that the course had to be adjusted slightly to port to increase the passing distance to the ‘object'.” In the minutes before the collision, the Sola TS established contact with Ingstad's officer of the watch to get them to take an avoidance maneuver by turning to starboard. But the watch still thought that the Sola was a stationary object and that turning to starboard would run into it. “When HNoMS Helge Ingstad did not alter course, the master on Sola TS ordered ‘stop engines' and, shortly afterwards, the pilot ordered full speed astern on the engines,” the report read. “These two measures were carried out only short time before the collision, and were therefore without material effect. “When the officer of the watch on HNoMS Helge Ingstad understood that the ‘object' giving off light was moving and on direct course to collide, it was too late to avoid the collision.” ‘I don't feel shame' The decision of the captain to not be on the bridge or, at the very least, to have posted a special navigation detail with the ship so close to land is perplexing, said retired U.S. Navy cruiser skipper Capt. Rick Hoffman, a career surface warfare officer. “If I'm within five miles of land I'm going to have some kind of navigation detail posted,” which in the U.S. Navy means a team of more qualified watch standers, extra lookouts and more than likely either the Commanding Officer, Executive Officer or both, would be on the bridge overseeing the watch. It's further perplexing as to why the officer of the deck, or officer of the watch, was conducting training during a transit so close to land, Hoffman said. “[The officer of the deck should be] looking out the window and completely focused on the transit,” he said. “We would not use that as a training opportunity. The OOD and the Conning Officer has no other task.” However, Østheim told VG in December he has no regrets about his actions, though he accepts that he was overall responsible for the ship. “I don't feel any shame,” he said. “As the ship's chief, I of course have the overall responsibility for the ship and its crew. It's extremely sad that this happened. It's an accident that should not happen, but I don't feel any shame.” https://www.defensenews.com/naval/2019/11/12/safety-report-slams-the-norwegian-navy-for-training-safety-shortfalls-in-the-runup-to-frigate-sinking/

  • Contracts for April 6, 2021

    April 8, 2021 | International, Aerospace, Naval, Land, C4ISR, Security

    Contracts for April 6, 2021

    Today

  • Making the case for commercially successful tech

    October 6, 2020 | International, Aerospace, C4ISR, Security

    Making the case for commercially successful tech

    Peter Villano Despite the Pentagon's efforts to develop advanced technology to strengthen national security and stay competitive, barriers remain, keeping much of the most promising emerging technology out of the government. Pockets of success do exist; Air Force acquisition in particular evaluates dual-use technologies through AFWERX and investment arm AFVentures. To truly enhance our national security, however, more needs to be done to fund companies that have proven, viable emerging technologies. Most nontraditional companies with proven technologies that don't have national security experience already work with Fortune 500 companies and in highly regulated, complex industries. The problem is that most of these companies are still overlooked for collaboration with the government and the Pentagon. In an effort to leverage our nation's commercial innovators, the Small Business Innovation Research program requires federal agencies with large research and development budgets, like the Department of Defense, to set aside funds for small businesses. But the government's definitions for eligible small businesses can disadvantage tech companies that have already succeeded in the private sector. The SBIR program has been successful in many ways, but most awards go to companies already focused on the government. Robert Rozansky and Robert D. Atkinson wrote that nearly a fifth of all SBIR awards go to companies that have already won 50 or more times, evidencing failure to reach the most promising technology companies. A 2019 report from the Alliance for Digital Innovation claimed that the federal government's failure to adopt commercial technology has wasted $345 billion over the past 25 years. And a report from Govini noted that approximately 59 percent of DoD research and development funding is concentrated in the top 10 vendors, limiting innovation. As calls for public sector innovation remind us, the DoD needs the most advanced technology from the private sector. There are critical steps the DoD should take to fix this problem. First, the government should reform the SBIR program and dedicate new, flexible resources to find and utilize viable, commercially successful tech companies. The National Defense Authorization Act for fiscal 2020 provides additional SBIR flexibility for small businesses more than 50 percent owned by venture capital. But the DoD has yet to fully promulgate this new flexible authority and is missing an opportunity to work with proven, VC-backed companies. The Small Business Administration should adjust the eligibility standards for the SBIR program to incentivize growth and, more importantly, take advantage of companies with more venture funding and a proven record of past performance. The number of repeat winners indicates that the SBIR program is not casting a wide enough net. Second, the DoD should further streamline acquisitions, reward acquisition executives who move fast, and expand flexible programs such as AFWERX, SOFWERX and the Defense Innovation Unit. Mike Madsen, deputy director and director of strategic engagement of DIU, said: “What [DIU has] represented is a lowering of those barriers to entry, making it easier for those leading-edge technology companies to get their technology to the men and women in uniform.” In the National Defense Authorization Act that passed the House, there is a charter for the National Security Innovation Network, which will expand and coordinate these efforts within the DoD. I strongly encourage the Senate to adopt the NSIN charter as well, and ensure its effort remains fully funded. The DoD alone awarded over 179 contracts in 2018 to nontraditional companies leveraging the other transaction authority, a flexible prototype authority outside of federal acquisition regulations. These contracts represent another way to engage high-growth tech companies. The DoD should continue to leverage OTAs. Third, the DoD should seek out federally focused accelerators and VCs in the private sector to inform, source and evaluate high-growth tech companies to drive federal missions forward. Federally focused tech accelerators like Dcode, and its investment network Dcode Capital, source promising tech for the government and ensure commercial tech is fully vetted and equipped to succeed in the federal marketplace. The DoD is also establishing in-house, VC-like programs, with AFVentures as an example. “This has been a year in the making now, trying to make our investment arm, the Air Force Ventures, act like an investor, even if it's a government entity,” the assistant secretary of the Air Force for acquisition, technology and logistics, Dr. Will Roper, explained. Buy-in from Congress will also be crucial to the success of these initiatives, starting with the NSIN section of the NDAA. Working with the right private sector partners is vital, and organizations like Dcode reduce risk for the government. Defense organizations don't need to reinvent the wheel to work with commercially successful tech. Use what's available today to reduce barriers and risk, reform existing methods, and increase engagement with trustworthy resources to work with more viable commercial tech companies that can move our country forward. https://www.defensenews.com/opinion/commentary/2020/10/03/making-the-case-for-commercially-successful-tech/

All news