1

MAGTF Expeditionary Family of Fighting Vehicles (MEFFV)

Thomas H. MillerProgram Manager MEFFV

Marine Corps Systems Command703-432-4032

Millerth@mcsc.usmc.mil

This presentation contains reference to the United States Government military capabilities that may not be authorized for release or sale. Mention of these capabilities in no way implies that the United States Government will release or consider release of them or any associated classified or unclassified information pertaining to them.

2

Overview

• What is MEFFV?

• Future Combat System/MEFFV Joint Program Office (JPO) plan

• PM MEFFV organization structure

• PM MEFFV charter

• Overview program schedule

3

What is MEFFV?• Description from MEFFV Mission Need Statement (now

archived; to be replaced by a pending Initial Capabilities Document):– The MAGTF Expeditionary Family of Fighting Vehicles (MEFFV) is a

combat vehicle replacement project designed to provide the capabilities presently conferred by the Light Armored Vehicle family and the M1A1 Main Battle Tank.

– It is envisioned that this family of vehicles will facilitate and enhance the capabilities of Expeditionary Maneuver Warfare through use of technologies to significantly improve efficiency and lessen the impact of operational and tactical logistics.

– The family of vehicles will be designed to maximize deployability options while retaining the requisite combat capabilities (lethality, survivability, mobility, sustainability) to perform the roles of the vehicles replaced.

– MEFFV should replace the LAV and Tank fleets when they reach their respective End of Service dates (2015 and 2020 respectively).

4

What is MEFFV?FCS/MEFFV Common Technologies

Commonalities inCommonalities inLeap-Ahead Technology:Leap-Ahead Technology:

Power TrainsWeapon Systems

SurvivabilitySensors

System Integration

MEFFVMEFFV Family of Vehicles (light/medium/heavy) Modular

Swim Capable (Riverine)Transport Advantage Direct and Indirect Fires Survivable and Sustainable

USMC Expeditionary: LCU, LCAC, CH-53, MV-22IOC: ~2015+; ~2020+

Future Combat Future Combat SystemsSystems

Maximum 16-18 tons Net Fires = High Survivability Network Centric (Large UAV force)Large Robotic/Autonomous Force (Unmanned) New Conceptual Way to Fight Army Expeditionary: C-130, C-17, C-5

IOC: 2014

5

FCS/MEFFV JPO PlanBackground

• 20 Jun 02 Secretary Rumsfeld Memo“My impression is that the Marines and the Army are both looking at tanks and vehicles for the 2015 to 2020 period. Why shouldn’t we require that it be a common chassis and that they do it joint?”

• 2 Apr 03 JROCM 086-03 Gen Pace“The JROC request the Army and Marine Corps establish a FCV JPO to satisfy the program requirements of FCS and MEFFV. Request the services return to the JROC with a decision brief by Sep 03.”

• 13 May 03 JROCM 111-03 Gen Pace“The JROC assigned a Joint Potential Designator of “Joint” and recommended the formation of a Joint Program Office, assigning Army as the lead service and including US Marine Corps representation.”

• 01 Mar 04 JROCM 038-04 Gen Pace“The Joint Requirements Oversight Council (JROC) reviewed and accepted the Army and Marine Corps FCS/MEFFV JPO proposal. The JPO plan will meet both Services materiel requirements for future combat systems, reduce life cycle costs of these systems, and enhance interoperability between the services.”

6

FCS/MEFFV JPO PlanKey Tenets

• JPO Tenets:– Collaboration with development of the FCS Network

Services Integration will be accomplished under the Marine Corps’ participation in the Joint Battle Management Command and Control initiatives.

– Build from existing Marine Corps/Army relationships– Leverage Army investment in FCS (to include S&T)– Maximum commonality desired within the scope of

the requirements– Interoperability required

Captured in the inter-service MOA on FCS / MEFFV Joint Collaboration, signed Aug 2004.

7

FCS/MEFFV JPO PlanPhasing

1. JPO Phase I (FY04-08): Define Marine Corps / Joint capabilities/attributes

• Ramp up USMC manning (immediate infusion into FCS reqt’s process)• Assess common & unique attributes for Future Force and EMW • Evaluate trade-space of Increment I vehicles and related systems• Use Early Operational Evaluations to influence joint CDD • Recommend and resource technologies unique to Marine applications

(Joint MOA w/ DARPA)• Conduct joint experimentation• Identify areas of commonality between FCS/MEFFV

2. JPO Phase II (FY08 and beyond): Acquisition • Manage FCS systems development to meet Joint CDD for FCS and

“Increment-Marine” (Marine unique needs)• Utilize shared production facilities as much as practical• Manage acquisition of FCS/MEFFV systems• Manage life cycle of FCS/MEFFV systems with Army and Marine units

8

FCS/MEFFV JPO PlanNetwork Integration Strategy

• Future USMC Architecture being developed by MCCDC - will coordinate with TRADOC and USJFCOM to ensure architectures are compatible with the joint architecture of land forces.

• Future C2 Network being developed by MARCORSYSCOM – SE&I will establish cell at Ft. Monmouth to coordinate interoperability with FCS networks.

• MEFFV Product Team will include representatives from MCCDC C2 Integration and MARCORSYSCOM C4II to ensure MEFFV will be well integrated into the future network consistent with the future joint architecture

UE/UA OperationalArchitecture

Army Battle CommandOper Arch(Existing)

FCS Network

Army TacticalInternet

(Existing)

FCS VehiclesC4I

MEFFV C4I

Army BattleCommandSystems

MEB-2015

USMC EnterpriseNetwork/

FORCENet(Existing)

EnterpriseIntegratedProduct

MEFFV/FCS JPO(C4II)

C4I/FCSNSI (SE&I LNO)

MCCDC/TRADOC

9

FCS/MEFFV JPO PlanNetwork Integration Strategy

FCS/MEFFV JPO PlanUSMC C4II Coordination with PM UA

USMC LNO to PM UA NSI ensures that UA Wireless Network will support integration with the USMC Tactical Data Network. Operates under MCSC SE&I Joint, Naval, and Coalition Integration Section.

Emerging Unit of Action

Network

Existing USMC

Tactical Data Network (TDN)

FCSVehicles

FCSVehicles

FCSVehiclesExisting

ArmyTacticalInternet (FBCB2)

MEFFVVehicles

MEFFVVehicles

MEFFVVehicles

C4I members of the MEFFV IPT integrate systems into the MEFFV.

10

PM MEFFV Organization Structure

MEFFVPM

Team

Dir, EFDC MCCDC CG MARCORSYSCOM

JCIDS Team

Acquisition Planning Team

Technology Team

PMT. Miller

IPT LeadC. Yunker

IPT LeadH. Bayes

IPT LeadE. Miller

Jointly chartered by MCCDC and MARCORSYSCOM, reflectingclose partnership in the JCIDS process.

Will phase into the USMC component of the FCS/MEFFV JPO.

11

PM MEFFV Team Charter

• Independent PM office reporting to CG MARCORSYSCOM (BGen William Catto)

• Teaming with MCCDC Expeditionary Force Development Center to support JCIDS

• Team Mission: “The MEFFV Team is the Marine Corps’ focal point for conducting concept development and capabilities refinement of mounted and armor units of the MAGTF conducting Expeditionary Maneuver Warfare (EMW) in support of the Joint Warfighting Commander consistent with MAGTF Command and Control Architectures. In conducting these activities, the Team shall consider opportunities to equip MAGTF units conducting combat support, combat service support, and special operations. The team shall conduct acquisition planning in anticipation of initiation of a MEFFV acquisition program. Additionally, the team will be the Command’s focal point for information on the Army’s Unit of Action (UA)/Future Combat Systems (FCS).”

12

MEFFV Program Schedule(Including Joint Activities)

FY24FY04 FY06 FY08 FY10 FY12 FY14 FY16 FY18 FY20 FY22 FY26

MS B IPD

FY02

IOC (Range)

MEFFV(INCR – M)

MS A

JPO Phase I: Concept Refinement MCCDC/TRADOC Officer Exchange

Joint Concept and Capabilities

Development, Joint Experimentation

IOCFCS INCR I

IPD#1

JPO Phase II: Joint Development and Acquisition - Design commonality to the maximum extent possible, in

systems, sub-systems, and software to reduce life cycle costs.- Potential for shared design and production facilities

FY04 QTR3

FY04 QTR4

FY05 QTR1

FY05 QTR2

FY05 QTR3

FY06 QTR4

FY07 QTR1

FY07QTR2

FY07 QTR3

FY05 QTR4

FY06 QTR1

FY06 QTR2

FY06 QTR3

FY07 QTR4

FY08 QTR1

FY08QTR2

Exp. Armored Forces FNA EAF FSA EAF ICD Approval Analysis of AlternativesFAA

Technology Assessment & Strategy Development

Concept Development & AoA Study Plan O&O, OMSMP Development

• INCR – Increment (Spiral Acquisition) IOC – Initial Operational Capability• IPD – Initial Production Decision MS – Milestone• CDD – Capability Development Document -- Milestone Deliverable• SOS – System of Systems OMMSP – Operational Mode Summary Mission Profile

MS AConceptDecision

C2 Integration (OVs, SVs, TVs, and Network Integration)

FCS Coordination and JPO Planning

Systems Engineering Management/Integration Planning

Test and Evaluation Planning/Strategy

Supportability Concept Planning/Strategy

FOC (Range)

EOS LAV: 2015 EOS M1A1: 2020JPO