Transcript MAGTF Expeditionary Family of Fighting Vehicles (MEFFV) Thomas H. Miller Program Manager MEFFV Marine Corps Systems Command 703-432-4032 [email protected] This presentation contains reference to the United States.

MAGTF Expeditionary Family
of Fighting Vehicles (MEFFV)
Thomas H. Miller
Program Manager MEFFV
Marine Corps Systems Command
703-432-4032
[email protected]
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.
1
Overview
• What is MEFFV?
• Future Combat System/MEFFV Joint
Program Office (JPO) plan
• PM MEFFV organization structure
• PM MEFFV charter
• Overview program schedule
2
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).
3
What is MEFFV?
FCS/MEFFV Common Technologies
Future Combat
Systems
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
MEFFV
Family of Vehicles
(light/medium/heavy)
Commonalities in Modular
Leap-Ahead Technology: Swim Capable (Riverine)
Transport Advantage
Power Trains
Direct and Indirect Fires
Weapon Systems
Survivable and
Survivability
Sustainable
Sensors
USMC Expeditionary:
System Integration
LCU, LCAC, CH-53, MV-22
IOC: ~2015+; ~2020+
4
FCS/MEFFV JPO Plan
Background
• 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.”
5
FCS/MEFFV JPO Plan
Key Tenets
Captured in the inter-service MOA on FCS / MEFFV Joint
Collaboration, signed Aug 2004.
• 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
6
FCS/MEFFV JPO Plan
Phasing
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
7
FCS/MEFFV JPO Plan
Network Integration Strategy
•
•
•
Future USMC Architecture
being developed by MCCDC will coordinate with TRADOC
and USJFCOM to ensure
MCCDC/
architectures are compatible
TRADOC
with the joint architecture of
land forces.
Future C2 Network being
developed by
C4I/FCS
MARCORSYSCOM – SE&I will NSI
establish cell at Ft. Monmouth
(SE&I
to coordinate interoperability
LNO)
with FCS networks.
MEFFV Product Team will
include representatives from
MEFFV/
MCCDC C2 Integration and
FCS
MARCORSYSCOM C4II to
JPO
ensure MEFFV will be well
(C4II)
integrated into the future
network consistent with the
future joint architecture
MEB-2015
UE/UA
Operational
Architecture
Army Battle
Command
Oper Arch
(Existing)
USMC Enterprise
Network/
FORCENet
(Existing)
FCS
Network
Army Tactical
Internet
(Existing)
Enterprise
Integrated
Product
FCS Vehicles
C4I
MEFFV C4I
Army Battle
Command
Systems
8
FCS/MEFFV JPO Plan
USMC C4II Coordination with PM UA
C4I members of the
MEFFV IPT integrate
systems into the MEFFV.
FCS
Vehicles
MEFFV
Vehicles
Existing
Existing
Emerging
USMC
Army
FCS
Unit of
MEFFV Tactical Data
Tactical
Vehicles
Vehicles
Action
Network
Internet
FCS
Network MEFFV
Network
Strategy
(TDN)
(FBCB2)
Vehicles Integration
Vehicles
FCS/MEFFV JPO Plan
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.
9
PM MEFFV
Organization Structure
Jointly chartered by MCCDC and MARCORSYSCOM, reflecting
close partnership in the JCIDS process.
CG MARCORSYSCOM
Dir, EFDC MCCDC
PM
T. Miller
JCIDS Team
IPT Lead
C. Yunker
MEFFV
PM
Team
IPT Lead Technology Team
H. Bayes
IPT Lead
E. Miller
Acquisition Planning Team
Will phase into the USMC component of the FCS/MEFFV JPO.
10
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).”
11
MEFFV Program Schedule
(Including Joint Activities)
FY02
FY04
FY06
FY08
FY10
FY12
FY14
FY16
FY18
FY20
FY22
JPO Phase II: Joint Development and Acquisition
- Design commonality to the maximum extent possible, in
JPO Phase I: Concept Refinement
MCCDC/TRADOC Officer Exchange
Joint Concept and Capabilities
Development, Joint Experimentation
FY24
FY26
systems, sub-systems, and software to reduce life cycle costs.
- Potential for shared design and production facilities
FCS INCR I
IPD#1
MEFFV
(INCR – M)
IOC
FOC (Range)
EOS LAV: 2015
EOS M1A1: 2020
JPO
MS A
MS B
IPD
IOC (Range)
FY04
FY04
FY05
FY05 FY05
FY05
FY06
FY06
FY06 FY06
FY07
FY07
FY07
FY07
FY08
FY08
QTR3
QTR4
QTR1
QTR2
QTR4
QTR1
QTR2
QTR3
QTR1
QTR2
QTR3
QTR4
QTR1
QTR2
FAA
Exp. Armored Forces FNA
QTR3
EAF FSA
QTR4
EAF ICD Approval
Analysis of Alternatives
Concept Development & AoA Study Plan Concept
Decision
Technology Assessment & Strategy Development
O&O, OMSMP Development MS A
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
•
•
•
•
INCR – Increment (Spiral Acquisition)
IPD – Initial Production Decision
CDD – Capability Development Document
SOS – System of Systems
IOC – Initial Operational Capability
MS – Milestone
-- Milestone Deliverable
OMMSP – Operational Mode Summary Mission Profile
12