Back to news

November 4, 2019 | International, Land

U.S. Marine Corps Orders More Amphibious Combat Vehicles from BAE Systems

October 30, 2019 - BAE Systems has received a $120 million contract from the U.S. Marine Corps for additional Amphibious Combat Vehicles under a third order for Low Rate Initial Production (LRIP). This award is an important next step on the path to full rate production.

This press release features multimedia. View the full release here: https://www.businesswire.com/news/home/20191030005625/en/

This latest contract is for the ACV personnel carrier variant (ACV-P), an eight-wheeled amphibious assault vehicle capable of transporting Marines from open-ocean ship to shore and conducting land operations. Each vehicle embarks 13 Marines in addition to a crew of three.

“This award further validates the Marine Corps' confidence in the vehicle's proven capability in meeting their amphibious mission, and represents an important step toward fielding the vehicle in the Fleet Marine Force. The ACV is a highly mobile, survivable and adaptable platform designed for growth to meet future mission role requirements while bringing enhanced combat power to the battlefield,” said John Swift, director of amphibious programs at BAE Systems.

Current low-rate production is focused on the ACV-P variant. More variants will be added under full rate production to include the command and control (ACV-C), 30mm medium caliber turret (ACV-30) and recovery variants (ACV-R) under the ACV Family of Vehicles program. BAE Systems previously received the Lot 1 and Lot 2 awards.

The Marine Corps selected BAE Systems along with teammate Iveco Defence Vehicles for the ACV program in 2018 to replace its legacy fleet of Assault Amphibious Vehicles, which have been in service for decades and were also built by BAE Systems.

ACV production and support is taking place at BAE Systems locations in Stafford, Virginia; San Jose, California; Sterling Heights, Michigan; Aiken, South Carolina; and York, Pennsylvania.

View source version on businesswire.com: https://www.businesswire.com/news/home/20191030005625/en/

On the same subject

  • OMFV: Army Wants Smaller Crew, More Automation

    July 20, 2020 | International, Land

    OMFV: Army Wants Smaller Crew, More Automation

    The draft RFP for the Bradley replacement, out today, also opens the possibility for a government design team to compete with private industry. By SYDNEY J. FREEDBERG JR.on July 17, 2020 at 1:51 PM WASHINGTON: The Army is giving industry a lot of freedom in their designs for its future armored troop transport, letting them pick the gun, weight, number of passengers and more. But there's one big exception. While the current M2 Bradley has three crew members – commander, gunner, and driver – a draft Request For Proposals released today says that its future replacement, the OMFV, must be able to fight with two. Fewer humans means more automation. It's an ambitious goal, especially for a program the Army already had to reboot and start over once. The other fascinating wrinkle in the RFP is that the Army reserves the right to form its own design team and let it compete against the private-sector contractors. This government design team would be independent of any Army command to avoid conflicts of interest. If the Army does submit its own design, that would be a major departure from longstanding Pentagon practice. But the Army has invested heavily in technologies from 50mm cannon to automated targeting algorithms to engines, so it's not impossible for a government team to put all that government intellectual property together into a complete design. The Army has embraced automation from the beginning of the Bradley replacement program, and that's been consistent before and after January's decision to reboot. OMFV's very name, Optionally Manned Fighting Vehicle, refers to the service's desire to have the option to operate the vehicle, in some situations, by remote control – eventually. But an unmanned mode remains an aspiration for future upgrades, not a hard-and-fast requirement for the initial version of the vehicle scheduled to enter service in 2028. By contrast, the two-person crew is one of the few hard-and-fast requirements in the draft RFP released this morning. It's all the more remarkable because there few such requirements in the RFP or its extensive technical annexes (which are not public). Instead, in most cases, the Army lays out the broad performance characteristics it desires and gives industry a lot of leeway in how to achieve them. That's a deliberate departure from traditional weapons programs, which lay out a long and detailed list of technical requirements. But the Army tried that prescriptive approach on OMFV and it didn't work. Last year, in its first attempt to build the OMFV, the Army insisted that industry build – at its own expense – a prototype light enough that you could fit two on an Air Force C-17 transport, yet it had to be tough enough to survive a fight with Russian mechanized units in Eastern Europe. Only one company, General Dynamics, even tried to deliver a vehicle built to that specification and the Army decided they didn't succeed. So the Army started over. It decided heavy armor was more important than air transportability, so it dropped the requirement to fit two OMFVs on a single C-17; now it'll be satisfied if a C-17 can carry one. In fact, it decided rigid technical requirements were a bad idea in general because it limited industry's opportunity to offer ingenious new solutions to the Army's problems, so the service replaced them wherever it could with broadly defined goals called characteristics. And yet the new draft RFP does include a strict and technologically ambitious requirement: the two-person crew. Now, since the OMFV is a transport, it'll have more people aboard much of the time, and when an infantry squad is embarked, one of them will have access to the vehicle's sensors and be able to assist the crew. But when the passengers get out to fight on foot, there'll just be two people left to operate the vehicle. A two-person crew isn't just a departure from the Bradley. This is a departure from best practice in armored vehicle design dating back to World War II. In 1940, when Germany invaded France, the French actually had more tanks, including some much better armed and armored than most German machines. But a lot of the French tanks had two-man crews. There was a driver, seated in the hull, and a single harried soldier in the turret who had to spot the enemy, aim the gun, and load the ammunition. By contrast, most German tanks split those tasks among three men – a commander, a gunner, and a loader – which meant they consistently outmaneuvered and outfought the overburdened French tankers. A lot of modern vehicles don't need a loader, because a mechanical feed reloads automatically. But in everything from the Bradley to Soviet tanks, the minimum crew is three: driver, gunner, and commander. That way the driver can focus on the terrain ahead, the gunner can focus on the target currently in his sights, and the commander can watch for danger in all directions. A two-person crew can't split tasks that way, risking cognitive overload – which means a greater risk that no one spots a threat until it's too late. So how do fighter jets and combat helicopters survive, since most of them have one or two crew at most? The answer is extensive training and expensive technology. If the Army wants a two-person crew in its OMFV, the crew compartment may have to look less like a Bradley and more like an Apache gunship, with weapons automatically pointing wherever the operator looks. The Army's even developing a robotic targeting assistant called ATLAS, which spots potential targets on its sensors, decides the biggest threat and automatically brings the gun to bear – but only fires if a human operator gives the order. Now, industry does not have to solve these problems right away. The current document is a draft Request For Proposals, meaning that the Army is seeking feedback from interested companies. If enough potential competitors say the two-man crew is too hard, the Army might drop that requirement. The current schedule gives the Army about nine months, until April 2021, to come out with the final RFP, and only then do companies have to submit their preliminary concepts for the vehicle. The Army will pick several companies to develop “initial digital designs” – detailed computer models of the proposed vehicle – and then refine those designs. Physical prototypes won't enter testing until 2025, with the winning design entering production in 2027 for delivery to combat units the next year. https://breakingdefense.com/2020/07/omfv-army-wants-smaller-crew-more-automation/

  • DoD ‘Office’ Functions Move To Cloud In Multi-Billion-Dollar Contract

    September 3, 2019 | International, C4ISR

    DoD ‘Office’ Functions Move To Cloud In Multi-Billion-Dollar Contract

    By BARRY ROSENBERG WASHINGTON: Overshadowed by the dispute with DoD's planned single-award JEDI cloud contract is another multi-billion-dollar single-award cloud contract awarded today that will actually determine the software that military personnel and civil servants use every day. Under the $7.6 billion 10-year Defense Enterprise Office Solutions (DEOS) cloud contract, the Pentagon will use Microsoft productivity tools such as word processing, spreadsheets, email, collaboration, file sharing, and storage — Office 365. Those applications presently reside mostly on legacy desktop computers, and will transition to a cloud-based solution across all military services. The result should be improved cybersecurity, for one thing. “The notion is that if you have it professionally and centrally managed it should be better patched and configured than having hundreds of individually managed servers,” said David Mihelcic, former chief technology officer at the Defense Information Systems Agency (DISA) and now a consultant with DMMI. “This seems reasonable, but I don't think there is any cyber magic in DEOS either.” The joint General Services Administration/Defense Department DEOS blanket purchase agreement was awarded to CSRA (acquired by General Dynamics in April 2018 for $9.7 billion) and its subcontractors Dell Marketing (a wholesale distributor of computers, peripherals, and software) and Minburn Technology (a value added reseller that specializes in Microsoft enterprise software agreements). The award includes a five-year base period with two two-year options and one one-year option. “DOD's cloud strategy includes both general purpose and fit-for-purpose clouds (and) DEOS is a great example of a fit-for-purpose cloud that supports our multi-cloud strategy,” said DOD Chief Information Officer Dana Deasy in a statement. “DEOS will streamline our use of cloud email and collaborative tools while enhancing cybersecurity and information sharing based on standardized needs and market offerings. “The journey to the cloud has been, and will continue to be, an iterative learning process. All lessons learned from pilot programs and the department's early cloud adopters have been rolled into this solution. DEOS takes advantage of technical, security and contractual lessons from these ongoing pilots, while military services are leveraging them to assess the readiness of their infrastructure to support migration to DEOS.” DEOS includes voice, video, and text collaboration capabilities, which the DoD already has with capabilities under enterprise services like: Defense Collaboration Services (DCS), which provides secure web conferencing and instant messaging services on the Non-secure Internet Protocol Router Network (NIPRNet) and Secure Internet Protocol Routing Network (SIPRNet), and Extensible Messaging and Presence Protocol (XMPP) chat. “Will it be an improvement over the current capabilities? I guess we will see,” said Mihalcic. “I can't say I found the collaborative capabilities of O365 better than what we had in DoD.” While DEOS on the surface appears to provide a back-office function, it can also be considered a weapon system given that it will provide common enterprise applications at local base, post, camp, and station levels — including deployed and afloat organizations — over the sensitive but unclassified NIPRNet and the secret SIPRNet, to include operations in Denied, Disconnected, Intermittent, and Limited Bandwidth (D-DIL) environments. “I would say almost certainly (DEOS is a warfighting capability), especially the SIPR instance,” said Mihelcic. “DoD uses email, chat, and DCS collaboration in support of warfighting today and this will now take on those needs. “As for DIL environments, DISA had threshold requirements for deployable instances in the draft RFP. The vendor most likely will satisfy with existing MS Exchange and Sharepoint software on deployable servers. To be honest, I think that most tactical units, including deployed Marines and Navy afloat, will stick with what they have.” https://breakingdefense.com/2019/08/dod-office-functions-move-to-cloud-in-multi-billion-dollar-contract/

  • Australia to manufacture Kongsberg cruise missiles

    August 21, 2024 | International, Land

    Australia to manufacture Kongsberg cruise missiles

All news