Back to news

October 2, 2019 | International, Land

Pencils down: Bids are in to replace the US Army’s Bradley fighting vehicle

By: Jen Judson

WASHINGTON — The bids are in for a chance to build prototypes for the Army's Optionally Manned Fighting Vehicle that will replace its Bradley Infantry Fighting Vehicle.

Among them is a Raytheon and Rheinmetall team putting forward Rheinmetall's Lynx 41 Infantry Fighting Vehicle, and General Dynamics Land Systems, which showcased its Griffin III technology demonstrator equipped with a 50mm cannon a year ago at the Association of the U.S. Army's annual exposition.

It is currently unknown if any other teams submitted bids by the service's set deadline of Oct. 1. None have come forward publicly despite rumors of a dark horse or two.

Absent from the usual brood of combat vehicle manufacturers is BAE Systems. Defense News broke the news earlier this year that the company wouldn't compete in the OMFV competition.

Textron has joined the Raytheon and Rheinmetall team with plans to, if chosen to build the new vehicle, build Lynx here in the United States at its Slidell, Louisiana, manufacturing facility. Raytheon and Rheinmetall announced a joint venture Oct. 1 — calling it Raytheon Rheinmetall Land Systems LLC — to pursue the OMFV competition.

“General Dynamics Land Systems submitted our OMFV proposal and bid sample to the US Army on 27 September. GD's bid sample was purpose built to address the desired system lethality, survivability and mobility as substantiation of our response to the Army's request for proposal,” the company said in a statement sent to Defense News. The company did not provide details on the submission.

GDLS did note, however, that it is proposing a “purpose built vehicle” using technologies from other platforms and “years of investment in advanced capabilities to include a 50mm cannon,” according to the statement.

The Army released its request for proposals in March opening a competition to build prototypes. The service plans to choose from the pool of bidders up to two teams to build 14 prototypes each.

The service will choose a winner that will start replacing Bradleys in 2026 that is designed to better operate in future environments that would allow soldiers to maneuver to a position of advantage and “to engage in close combat and deliver decisive lethality during the execution of the combined arms maneuver,” according to an Army statement issued along with the RFP release.

Some of the threshold requirements for OMFV are a 30mm cannon and a second-generation, forward-looking infrared system, or FLIR. Objective requirements are a 50mm cannon and a third-generation FLIR.

Brig. Gen. Ross Coffman, who is in charge of Next-Generation Combat Vehicle (NGCV) modernization efforts, said at the Defense News Conference in September that he is confident the requirements set for OMFV are right and had no plans to change them.

The selected prototypes will go through “rigorous” operational testing and soldier assessments.

The Army plans to downselect to one vehicle for low-rate initial production following the assessments and testing.

https://www.defensenews.com/land/2019/10/01/pencils-down-bids-are-in-for-armys-bradley-fighting-vehicle-replacement

On the same subject

  • For the Navy’s hospital ships, networking is yet another challenge

    April 22, 2020 | International, Naval, C4ISR

    For the Navy’s hospital ships, networking is yet another challenge

    Andrew Eversden When the Navy hospital ship Comfort deployed to Haiti in 2010 following devastating earthquakes, media organizations broadcasting in the area ate up so much satellite bandwidth that the ship had to revert to paper processes and adjust its satellite communications for some ship-to-shore messaging. While the outages weren't a widespread issue, said Sean Kelley, who served as the ship's top IT officer at the time, the problem highlighted a challenge these ships face: broadband. Now, the hospital ships Mercy and Comfort are deployed to Los Angeles and New York, respectively, and are in the national spotlight as symbols of the coronavirus pandemic relief effort. But security and IT experts say the ships' mission presents the Navy with distinct networking problems, from cybersecurity to network connection for patients. Onboard devices When disaster strikes, the Navy's hospital ships deploy in a matter of days, mobilizing with a crew of about 100-1,200 personnel. But the influx of staff also leads to an incursion of devices, all of which must be secure and require bandwidth. “You have a lot of different people going to a lot of different places that now have to be acclimated to this environment,” said Kelley, now executive vice president at Unissant, an IT and cybersecurity company. “So that's really one of the biggest challenges, is getting all those things turned on, all those things activated, making sure that they are all compliant with the latest patches and fixes, and making sure they're good.” This process can be a “nightmare,” said retired Rear Adm. Danelle Barrett, former deputy chief information officer of the Navy and cybersecurity division director. “The challenging part is always in the first couple days whenever this happens,” said Barrett, who oversaw communications and cyberspace for Operation Unified Response, the U.S. military's mission in Haiti following the 2010 earthquake. “The team is coalescing about how they want to operate, and they're getting their feet wet, getting new accounts on networks ... [getting] their logins.” Cybersecurity aboard the ships is also complex. Both ships have 1,000 beds, 12 operating rooms, blood banks, labs, medical devices and a multitude of other “internet of things” devices connected to hospital beds. According to a 2018 survey by health care IoT security company Zingbox, each bed can have as many as 10-15 IoT devices. “They have to be cyber-ready, or the mission of the Mercy is considered [degraded],” said Dean Hullings, global defense solutions strategist at Forescout, which handles Comply to Connect — a Defense Department framework created to ensure the cybersecurity of new devices — for the USNS Mercy. Ensuring connectivity For the devices to function, they need connectivity. When the ships arrived in ports in late March, technology firm CenturyLink “donated” connectivity to the Mercy, while Verizon provided connectivity to the Comfort. Former and current Navy officials told C4ISRNET that adequate broadband is the most challenging IT consideration faced by these ships. “Obviously you're going to be transferring imagery of X-rays or things like that that are more dense and require a ... higher data rate, so that bandwidth in port is important,” Barrett said. And with the introduction of patients, bandwidth needs become more complex. “The greatest communications challenge we are going to face during this deployment is the increased need for patients to communicate off the ship during their stay,” Tom Van Leunen, a spokesman for Military Sealift Command, told C4ISRNET. “Our hospital ships are designed to support official communication for the ship's crew and embarked medical community to complete their job. Adding a capability for patients to reach loved ones increases the risk of saturating the bandwidth off the ship.” Aboard both ships, the Navy doubled the bandwidth, he said, adding that Navy personnel also set up separate networks for patients' communications. While this solves one networking problem, it can also create an increased cybersecurity risk. Securing the ships Cybersecurity on the hospital ships follows the same standard practices as the rest of the Navy fleet. Since those aboard are largely Navy medical staff and personnel, they know what activities are acceptable on the network, Barrett said. “You can't just go and plug anything into that network because of potential vulnerabilities that that system may bring that could affect not just the ship, but remember, the ship is then connected to the rest of the [Department of Defense Information Network],” Barrett said. “So risk by one is shared by all.” ForeScout's Hullings said a hospital environment “epitomizes” why the Comply to Connect program is necessary. The ship has desktops, servers, routers, printers and other networks equipment, as well as mobile devices, such as tablets, that health care providers use to track patient care. “The truly unique stuff is the mission systems of the hospital, like X-ray machines, MRI machines, the beds themselves in the post-operative recovery rooms, that are all sensors. And they are all passing data. They have to be protected,” Hullings said. A spokesperson for the Navy told C4ISRNET that the ships are prepared for the cybersecurity challenges associated with their missions, but declined to address what additional cybersecurity challenges are introduced with the addition of private citizens. “These ships have routinely deployed in humanitarian assistance missions such as Pacific Partnership (USNS Mercy) and Continuing Promise (USNS Comfort) that required them to operate in partner nation ports, with foreign national patients being brought to and from the ship,” said Cmdr. Dave Benham, a spokesman for the Navy's 10th Fleet. “In all operating locations, we take appropriate precautions to keep our networks secure, and we do not discuss specific measures in order to protect operational security.” Cybersecurity on the hospital ships follow the same protocols as any other Military Sealift Command ship, said Benham. “Protecting our networks is a continuous challenge, and the overarching concern is to ensure that the right information gets to the right place at the right time with the right level of protection,” he explained. Cybersecurity aboard the hospital ships follow similar efforts to those recommendations made by the Centers for Disease Control and Prevention: Wash your hands. “It's ‘wash your hands' with your computer, too,” Barrett said. “Do good hygiene with your computer.” https://www.c4isrnet.com/it-networks/2020/04/21/for-the-navys-hospital-ships-networking-is-yet-another-challenge/

  • Breakthrough for Skyranger 30 air defence system: Rheinmetall awarded development contract for Skyranger variant of Lynx in Hungary

    December 20, 2023 | International, Land

    Breakthrough for Skyranger 30 air defence system: Rheinmetall awarded development contract for Skyranger variant of Lynx in Hungary

    The customisation development of the Skyranger 30 turret for the Lynx tracked armoured vehicle and the integration of additional effectors responds to Hungary’s need to address the current threat situation,...

  • Two companies to square off for Australia’s $10 billion infantry fighting vehicle program

    September 18, 2019 | International, Land

    Two companies to square off for Australia’s $10 billion infantry fighting vehicle program

    By: Nigel Pittaway MELBOURNE, Australia – The Australian government has selected Hanwha and Rheinmetall to participate in the next phase of its A$15 billion (U.S. $10.3 billion) infantry fighting vehicle program, being delivered under Project Land 400 Phase 3. Hanwha's AS21 Redback IFV, a variant of the South Korean Army's K21 vehicle, and Rheinmetall's Lynx KF41 will now progress to a 12-month risk mitigation activity program later this year, which will test the vehicles under operational conditions. Land 400 Phase 3 (Mounted Close Combat Capability) will acquire up to 450 tracked IFVs to replace the Australian Army's ageing M113AS4 armoured personnel carriers. A decision on which tenderer will progress to the acquisition phase of the program will be presented to government for consideration in 2022. “The two companies have been assessed as offering vehicles that are best able to meet the requirements of the Army while offering value for money for defense,” Minister for Defence Industry Melissa Price said at the Sept. 16 announcement. The announcement reduces the field from four to two, with BAE Systems (CV90) and General Dynamics Land Systems (Ajax) now eliminated from the competition. Phase 3 of the overarching Land 400 program follows on from the A$5.2 billion (U.S. $3.6 billion) Phase 2, under which Rheinmetall is delivering 211 Boxer wheeled 8x8 combat reconnaissance vehicles to replace the Australian Army's light armored vehicles. Rheinmetall is assembling all but the first 25 Boxers at its recently established Military Vehicle Centre of Excellence at Ipswich, west of Brisbane. Local industry participation will be a key requirement for Land 400 Phase 3. “Australian industry involvement and Australian workers are vital to this project,” Price said. “Phase 3 is another important opportunity for Australian industry to deliver leading edge technology for the ADF.” Rheinmetall has indicated it will assemble the Lynx in its Ipswich facility and Hanwha announced on May 23 that it had teamed with EOS Group and Elbit Systems to develop the AS21 and build it in Geelong, south of Melbourne. Hanwha and Rheinmetall are also the prime contenders for the Australian Army's recently revitalized Land 8116 program, which will acquire 30 self-propelled howitzers, together with support vehicles and systems. Hanwha is proposing a local version of its K9 Thunder 155mm SPH, dubbed Aussie Thunder, which the company said in May would be assembled in Geelong irrespective of the Land 400 Phase 3 outcome. Rheinmetall is expected to offer a solution based on its PzH 2000 vehicle. https://www.defensenews.com/global/asia-pacific/2019/09/17/two-companies-to-square-off-for-australias-10-billion-fighting-vehicle-program/

All news