This Community can only improve through your valued input - provide yours today!
                                                                                                            Click Here for SharePoint 2013 Migration Information and News
Click here   image of a classical greek architecture representing DAU's strength as a business university instructing in DoD Acquisition
HomeContactAbout ACCPrivacyTutorialDoD CertificateReport an Issue  
.

CRS - Marine Corps Amphibious Combat Vehicle (ACV) and Marine Personnel Carrier (MPC) Background and Issues for Congress

Learning Materials
0
Helpful Votes
File
Benefit/Value

by Andrew Feickert
Specialist in Military Ground Forces
Congressional Research Service (CRS)
December 3, 2015

Summary

On January 6, 2011, after spending approximately $3 billion in developmental funding, the Marine Corps cancelled the Expeditionary Fighting Vehicle (EFV) program due to poor reliability demonstrated during operational testing and excessive cost growth. Because the EFV was intended to replace the 40-year-old Amphibious Assault Vehicle (AAV), the Pentagon pledged to move quickly to develop a “more affordable and sustainable” vehicle to replace the EFV. The Amphibious Combat Vehicle (ACV) is intended to replace the AAV, incorporating some EFV capabilities but in a more practical and cost-efficient manner. In concert with the ACV, the Marines were developing the Marine Personnel Carrier (MPC) to serve as a survivable and mobile platform to transport Marines when ashore. The MPC was not intended to be amphibious like an AAV, EFV, or the ACV but instead would be required to have a swim capability for inland waterways such as rivers, lakes, and other water obstacles such as shore-to-shore operations in the littorals. Both vehicles are intended to play a central role in future Marine amphibious operations.

On June 14, 2013, Marine leadership put the MPC program “on ice” due to budgetary pressures but suggested the program might be resurrected some 10 years down the road when budgetary resources might be more favorable.

In what was described as a “drastic shift,” the Marines decided to “resurrect” the MPC in March 2014. The Marines designated the MPC as ACV Increment 1.1 and planned to acquire about 200 vehicles. The Marines also plan to develop ACV Increment 1.2, a tracked, fully amphibious version, and to acquire about 470 vehicles and fund an ongoing high water speed study. Although ACV Increment 1.1 will have a swim capability, a “connector” will be required to get the vehicles from ship to shore.

On November 5, 2014, it was reported the Marines released a draft Request for Proposal (RFP) for ACV Increment 1.1. The Marines are looking for information from industry regarding program milestones, delivery schedules, and where in the program cost savings can be achieved.

On November 24, 2015, the Marine Corps awarded BAE Systems and SAIC contracts to develop ACV 1.1 prototypes for evaluation. BAE’s contract was for $103.8 million and SAIC’s for $121.5 million, and each company is to build 16 prototypes to be tested over the next two years. Both vendors are expected to start delivering their prototypes in the fall of 2016 for testing, and the Marines expect to down select to a single vendor in 2018.

The Administration’s FY2016 Budget Request for the ACV was $219.1 million in Research, Development, Testing and Evaluation (RDT&E) funding. Congress approved the Administration’s FY2016 ACV budget request.

A potential issue for Congress is the Marines’ new MPC/ACV acquisition strategy and its associated challenges and risks. This report will be updated.

Popular Tags

Page Information

Popularity of this page:
#842 of 926 items
0 Helpful votes
At this page:
876 Page Views 0 Pages Emailed
0 Meta-card Views 80 Attachments Downloaded
0 Relationships and Highlights 0 Videos Downloaded
ID737314
Date CreatedWednesday, December 23, 2015 10:01 AM
Date ModifiedWednesday, December 23, 2015 10:01 AM
Version Comment:

REQUEST AN ACCOUNT Benefits of Membership I Forgot My Login Information
ACC Practice Center Version 3.2
  • Application Build 3.2.9
  • Database Version 3.2.9