This MARADMIN has been cancelled
Superseded by MARADMIN 316/06
USMC Procedures for Security Cooperation Training Teams
This MARADMIN establishes procedures for requesting, validating, executing, and reporting Security Cooperation (SC) training teams. It outlines different processes depending on whether teams are requested by Combatant Commands (under Title 10 or Title 22 authorities), regional Marine Component commands (MARFORs), or for Military-to-Military and Subject Matter Expert Exchange activities under the Joint Contact Team Program.
Issued: November 23, 2005
1. EXECUTIVE SUMMARY. THIS MARADMIN PROMULGATES THE PROCEDURES FOR REQUESTING, VALIDATING, EXECUTING, AND REPORTING SECURITY COOPERATION TEAMS PER REF A. 2. INFORMATION. THE INDIVIDUAL MARINE IS THE MOST SCARCE, YET MOST SOUGHT AFTER RESOURCE FOR ACCOMPLISHING USMC SECURITY COOPERATION (SC) OBJECTIVES WORLDWIDE. ALLIED AND PARTNER NATIONS RECOGNIZE THAT CAPITALIZING ON THE USMC ETHOS, TRAINING REGIMEN, AND PROFESSIONALISM IS ONE OF THE BEST WAYS TO TRANSFORM THEIR DEFENSE AND SECURITY ORGANIZATIONS. HOWEVER, SUPPLY RARELY MEETS DEMAND, AND A RIGOROUS PROCESS OF PLANNING, REQUESTING, VALIDATING, AND SOURCING MARINES FOR THESE IMPORTANT MISSIONS IS CRUCIAL. A. TEAMS REQUESTED BY THE COMBATANT COMMAND. (1) TEAMS DEPLOYING UNDER TITLE 10 AUTHORITIES. GENERALLY, TEAMS REQUESTED BY COMBATANT COMMANDS UNDER TITLE 10 AUTHORITY FOLLOW THE PROCESS ASSOCIATED WITH REQUESTS FOR FORCES (RFF). THE MARINE CORPS WILL STAFF AND FILL THESE TEAMS PER THE JOINT STAFF TASKING AND APPLY CMC GUIDANCE. HOWEVER, THE COMBATANT COMMANDER MAY DIRECT THE MARINE COMPONENT (MARFOR) TO EXECUTE SOME SPECIFIC TITLE 10 PROGRAMS (E.G., THE REGIONAL DEFENSE COUNTER TERRORISM FELLOWSHIP (RDTCF)) THAT DO NOT NECESSARILY USE THE FORMAL RFF PROCESS. IN THESE CASES, THE PROCEDURE OUTLINED IN PARAGRAPH 2.C APPLIES AS IF THE REQUEST ORIGINATED FROM THE REGIONAL MARFOR. (2) TEAMS DEPLOYING UNDER TITLE 22 AUTHORITIES. TEAMS REQUESTED BY COMBATANT COMMANDS DEPLOYING UNDER TITLE 22 AUTHORITIES NORMALLY ORIGINATE FROM THE SECURITY ASSISTANCE OFFICE (SAO) IN THE COUNTRY WHERE THE TEAM WILL OPERATE. PER SECNAVINST 4950.4A, A SAO MAKES REQUESTS DIRECTLY TO THE SERVICE HEADQUARTERS. CG MCCDC IS DESIGNATED AS THE "SUPPORTING COMMANDER" FOR TEAMS ASSEMBLED FROM THE SUPPORTING ESTABLISHMENT OR FROM HQMC. DEPENDING ON THE SITUATION, DEPLOYMENT OF THESE TEAMS MAY REQUIRE A DEPLOYMENT ORDER. (3) THE FOLLOWING IS THE GENERAL POLICY AND PROCEDURE FOR REQUESTING, STAFFING, AND DEPLOYING SC TEAMS UNDER TITLE 22 AUTHORITIES. (A) FOR TEAMS PLANNED DURING ANNUAL PLANNING SESSIONS (TPMRS, RWGS, ETC.), THE COMBATANT COMMANDER OR HIS SAO INITIATES A "CALL-UP" MESSAGE VIA OFFICIAL CORRESPONDENCE (DMS, OFFICIAL LETTER) NLT 120 DAYS BEFORE THE REQUESTED DEPLOYMENT DATE. FOR UNSCHEDULED, IMPROMPTU TEAMS THE COMBATANT COMMANDER OR HIS SAO INITIATES A "CALL-UP" MESSAGE VIA OFFICIAL CORRESPONDENCE (DMS, OFFICIAL LETTER) NLT 180 DAYS BEFORE THE REQUESTED DEPLOYMENT DATE. ALL CALL UP MESSAGES MUST USE THE INSTRUCTIONS AND FORMAT IN CHAPTER 13 OF REF D. (B) THE CALL-UP MUST BE ADDRESSED TO CG, TECOM (SCETC) OR CG, MCSC (INTERNATIONAL PROGRAMS), AS APPROPRIATE. CG, MCSC IS THE ACTION OFFICE FOR TEAMS FUNDED THROUGH AN FMS CASE WITH A TRAINING LINE ASSOCIATED WITH THE SALE OF A SYSTEM. CG, TECOM (SCETC) IS THE ACTION OFFICE FOR ALL OTHER REQUESTS. AT A MINIMUM, INFO COPIES MUST BE PROVIDED TO THE REGIONAL MARINE COMPONENT COMMANDER; COMMANDER, MARINE FORCES ATLANTIC (G3-5-7); DEPUTY COMMANDANT FOR PLANS, POLICIES, AND OPERATIONS (BOTH DIRECTOR, OPERATIONS (PO), AND DIRECTOR, STRATEGY AND PLANS (PL)); AND DIRECTOR, INTELLIGENCE (IO). (C) UPON RECEIPT OF THE REQUEST, SCETC (OR MCSC(IP)) WILL CONDUCT A MISSION ANALYSIS TO IDENTIFY DETAILED REQUIREMENTS INCLUDING THE POSSIBLE USE OF CONTRACTOR SUPPORT. SIMULTANEOUSLY, PP&O (PLU) WILL VALIDATE THE REQUEST WITH THE REGIONAL MARFOR TO ENSURE ACCEPTABILITY AND SUITABILITY. IF BOTH ACCEPTABLE AND SUITABLE, PLU WILL STAFF THE REQUEST AND THE RESULTS OF THE MISSION ANALYSIS TO THE APPROPRIATE USMC COMMANDS AND ORGANIZATIONS FOR FEASIBILITY AND PRESENT THE RESULTS TO DC PP&O FOR DECISION. AT A MINIMUM, PLU WILL CONSULT DC CD, DC M&RA (MPP), COMMARFORLANT (G3-5-7), AND DIRECTOR, OPERATIONS (PO). OTHER ORGANIZATIONS WITH EQUITY IN THE POTENTIAL MISSION ARE INCLUDED AS REQUIRED BY THE MISSION ANALYSIS. IF APPROVED BY DC PP&O, PLU WILL THEN ISSUE A CMC VALIDATION STATEMENT DIRECTING EXECUTION TO THE RELEVANT COMMANDS AND ACTIVITIES. (D) ONCE APPROVED THE SAO AND REGIONAL MARFOR WILL COORDINATE DIRECTLY WITH SCETC (OR MCSC(IP)) TO IDENTIFY TEAM COMPOSITION. TEAM MEMBERS NOT SOURCED BY THE REGIONAL MARFOR WILL BE GLOBALLY SOURCED BY DC M&RA USING INDIVIDUAL AUGMENTATION PROCEDURES. SCETC (OR MCSC(IP)) IS RESPONSIBLE FOR ENTERING THE REQUIREMENTS INTO THE MANPOWER REQUIREMENTS TRACKING MODULE (MRTM) OF THE MARINE CORPS MOBILIZATION PROCESSING SYSTEM (MCMPS), REFERENCING THE DC PP&O DECISION AS CMC ENDORSEMENT OF THE EVENT. NO ENTRIES WILL BE MADE INTO MRTM UNTIL A MISSION IS APPROVED BY DC PP&O. B. TEAMS REQUESTED BY THE REGIONAL MARINE COMPONENT (MARFOR). (1) THE PROCEDURES BELOW APPLY TO SC EVENTS AUTHORIZED AND FUNDED BY EITHER TITLE 22 OR TITLE 10. (2) REGIONAL MARFORS CONDUCT MANY SC EVENTS IN SUPPORT OF BOTH THE COMBATANT COMMANDER'S AND THEIR OWN TSCPS. WHEN A MARFOR EVENT INITIATED INTERNALLY, DIRECTED BY THE COMBATANT COMMANDER, OR REDIRECTED FROM THE SAO CANNOT BE ACCOMPLISHED USING ASSIGNED FORCES OR THROUGH THE RFF PROCESS, THE MARFOR SUBMITS A FEASIBILITY OF SUPPORT (FOS) MESSAGE VIA DMS TO EITHER MARINE FORCES ATLANTIC (MFL) OR MARINE FORCES PACIFIC (MFP), AS APPROPRIATE, DEPENDING ON THE SUPPORT REQUIRED FROM FORCES ASSIGNED TO THOSE COMMANDS. THIS MESSAGE SHALL INCLUDE, AT A MINIMUM, THE FOLLOWING INFO ADDRESSEES: CMC WASHINGTON DC PPO/PO/PL/PS/IO AND CG TECOM SCETC. (3) DIRECTOR PO OR DIRECTOR PL, AS APPROPRIATE, VALIDATES THE REQUEST. (4) MFL / MFP, AS APPROPRIATE, CONDUCTS STAFFING AND COORDINATES FOR SOURCING TO INCLUDE REQUESTING FEASIBILITY FROM THE SERVICE SUPPORTING ESTABLISHMENT, IF NECESSARY. IF THE MISSION IS FEASIBLE, MFL / MFP ASSEMBLES AND DEPLOYS THE TEAM USING TAD OR DEPLOYMENT ORDERS AS REQUIRED. IF SOURCING IS NOT FEASIBLE, THE REQUEST IS RETURNED TO THE REGIONAL MARFOR WHO CAN REENGAGE WITH THE COMBATANT COMMANDER FOR OTHER SOURCING OPTIONS. (5) SCETC AND / OR MCSC(IP) INVOLVEMENT IS CRITICAL IN THIS PROCESS IF THE EVENT IS TO BE EXECUTED UNDER TITLE 22 AUTHORITIES. SCETC (OR MCSC(IP)) HAS REPORTING, ACCOUNTING, BILLING, AND OTHER REQUIREMENTS TO PROPERLY ACCOUNT FOR, AND SUPPORT, TEAMS DEPLOYING UNDER TITLE 22. C. TEAMS SUPPORTING MIL-MIL AND SUBJECT MATTER EXPERT EXCHANGES (SMEE) ACTIVITIES AUTHORIZED BY 10 USC 168 (JOINT CONTACT TEAM PROGRAM (JCTP)). (1) SCETC IS ASSIGNED AS THE SERVICE LEAD FOR ALL MIL-MIL AND SMEE ACTIVITIES. THE PROCEDURES FOR THESE EVENTS ARE VERY SIMILAR TO MARFOR INITIATED SC TEAMS. THE MARINE OR MARINES CONDUCTING THE MISSION DEPLOY UNDER INDIVIDUAL TAD ORDERS. (2) IF THE MARFOR CANNOT ACCOMPLISH THE MIL-MIL OR SMEE MISSION WITH ASSIGNED FORCES AND DESIRES MARINES TO CONDUCT THE EVENT, THEY INITIATE A FOS MESSAGE TO THE MOST APPROPRIATE SOURCE: SCETC (FOR MCCDC/TECOM ASSETS), MCSC (FOR SYSTEMS AND LOGISTICS EXPERTS), MFL (FOR OPERATING FORCES), MFP (FOR OPERATING FORCES); MFR (FOR USMCR), OR A HQMC DEPARTMENT (FOR HQMC EXPERTS). 3. SCOPE. THIS MARADMIN IS APPLICABLE TO THE MARINE CORPS TOTAL FORCE.