Unlike the Army (centralized via AFC) or Air Force (distributed across MAJCOMs), the Marine Corps blends doctrine-led concept development with operational demand, coordinated through a compact but powerful requirements ecosystem.
Formal Requirements Process
MCCDC Requirements Oversight Council (ROC)
Role: Internal council that reviews and validates USMC requirements before they go up to the Joint level.
Notes: Chaired by DC CD&I. Final Marine approval before JCIDS gates.
Marine Corps Capabilities Development Process (MCCDP)
Role: USMC's internal version of JCIDS. Streamlined and warfighter-focused.
Notes: Efficient, but rigid—once a requirement is validated, it's hard to change.
Integration with PPBE
Role: CD&I works closely with PP&O and Programs Division to push validated requirements into the budget.
Notes: Nob funding = no fielding. Alignment here is critical.
Upstream – Warfighting Concept & Capability Drivers
These actors influence the "what" and "why" before a formal requirement is written:
Marine Corps Combat Development Command (MCCDC)
Role: Central architect of Marine Corps future force design. Based at Quantico.
Notes: Owns the Marine Corps Capabilities-Based Assessment (MC-CBA) process. This is where requirements start.
Deputy Commandant for Combat Development & Integration (DC CD&I)
Role: 3-star general responsible for all USMC force design, requirements, and modernization.
Notes: Sets the strategic direction via Force Design 2030 and ongoing refinement.
Capabilities Development Directorate (CDD) under CD&I
Role: Writes and validates formal requirement documents (ICDs, CDDs, CPDs).
Notes: Core authors of everything that turns into a program or fielded capability. Engage these early.
Marine Corps Warfighting Lab (MCWL)
Role: Rapid experimentation, operational prototypes, CONOPS testing.
Notes: If you're an emerging tech player, MCWL is your wedge. They trial capabilities and feed insights back into CDD.
Operating Forces (I MEF, II MEF, III MEF, MARFORPAC, MARFORSOC)
Role: Deliver bottom-up demand signals via urgent needs, JUONs, or experimentation feedback.
Notes: Real-world usage and operator input is key—especially in INDOPACOM.
Downstream – Acquisition & Fielding
These actors turn requirements into funded programs and fielded capabilities:
Marine Corps Systems Command (MCSC)
Role: Primary acquisition arm. Manages portfolios including unmanned systems, C4ISR, force protection, and logistics.
Notes: Where your requirement becomes a contract. Not the right entry point for shaping—too late—but essential for execution.
Program Managers (e.g., PM-UES, PM-GCES)
Role: Oversee specific programs like unmanned ground systems, expeditionary power, or command & control.
Notes: Key targets once a requirement is validated or you're entering Phase III SBIR/OTA.
Rapid Capabilities Office (RCO-USMC)
Role: Handles urgent or emerging operational needs via accelerated pathways.
Notes: A growing tool for experimentation and early fielding.
T&E and Fleet Input
Role: Marine Corps Operational Test & Evaluation Activity (MCOTEA) + Fleet Marine Forces
Notes: Final gate for operational effectiveness. Also influence iterative requirement updates post-deployment.
BD & GTM Implications
Shape at the concept level: CD&I, MCWL, and MCCDC are where real shaping happens—not MCSC.
MCWL = entry point for demos and prototypes: Especially if you're pushing autonomy, robotics, ISR, or logistics edge tech.
Tie to Force Design 2030: Aligning your pitch to distributed ops, expeditionary sustainment, or littoral maneuver will resonate.
Get theater demand: MARFORPAC and III MEF are driving needs in the INDOPACOM theater. Field input from them adds urgency and operational credibility.
Build dual advocacy: Top-down (CD&I/CDD) + bottom-up (MEF or MARFOR) is your winning combo.
Marine Corps Requirements-101