Submission of Individual Augmentation Request
This MARADMIN establishes the requirement for USMC organizations to submit Individual Augmentation (IA) requests through the Manpower Requirements Tracking Module (MRTM) of the Marine Corps Mobilization Processing System (MCMPS) effective 15 March 2004. The new automated system replaces the previous message-based submission process to improve tracking and reduce errors. Organizations without web access may continue to submit requests via message traffic.
Issued: February 27, 2004
1. REF A PROVIDES BROAD GUIDANCE ON JOINT POLICIES AND PROCEDURES FOR INDIVIDUAL AUGMENTATION. LACK OF A FULLY AUTOMATED REQUIREMENTS TRACKING SYSTEM HAS MADE THE SUBMISSION AND TRACKING OF REQUIREMENTS DIFFICULT AND PRONE TO ERROR. THE MARINE CORPS INITIATED A "QUICK WIN" EFFORT TO DEVELOP AN AUTOMATED SYSTEM TO SOLVE THIS PROBLEM. 2. EFFECTIVE 15 MAR 04, USMC ORGANIZATIONS REQUESTING INDIVIDUAL AUGMENTATION WILL SUBMIT THEIR REQUESTS TO CMC (MPP-60) VIA THE MANPOWER REQUIREMENTS TRACKING MODULE (MRTM) OF THE MARINE CORPS MOBILIZATION PROCESSING SYSTEM (MCMPS). THE MRTM MCMPS WILL BE USED TO REQUEST, VALIDATE, APPROVE, AND MANAGE ALL IA REQUIREMENTS. USMC ORGANIZATIONS WILL BE EXPECTED TO HAVE ALL CURRENT INDIVIDUAL AUGMENT REQUIREMENTS ENTERED INTO THE SYSTEM BY THIS DATE. THIS WILL ALLOW TIME TO EFFECT TRANSITION FROM MESSAGE TRAFFIC TO PERMANENT USE OF THE MRTM. 3. THE MRTM MCMPS IS LOCATED AT URL HTTPS:WWW.US-MARINE- CORPS.NET/MCMPS/. TRAINING TEAMS VISITED MARFORPAC, MARCENT, MARFORSOUTH, MARFORLANT, MARFORRES, I, II AND III MEF AND SELECTED ORGANIZATIONS DURING JAN/FEB. A TRAINING MODULE IS PROVIDED AT URL HTTPS:WWW.US-MARINE-CORPS.NET/BETA/MCMPS/. 4. MARFORS WILL IDENTIFY ALL LEVEL 1 AND LEVEL 2 (MARFOR) ADMINISTRATORS, USERS AND ASSOCIATED ROLES WITHIN MRTM TO CMC (MPP-60) IN THE FOLLOWING FORMAT: SSN, RANK, FULL NAME, E-MAIL ADDRESS, MCC, MRTM ROLE. E-MAIL SUBMISSION IS ACCEPTABLE. 5. OUTSIDE AGENCIES OR THOSE ORGANIZATIONS WITHOUT WEB ACCESS MAY CONTINUE TO USE MESSAGES TO SUBMIT REQUIREMENTS PER GUIDANCE CONTAINED IN REFS B AND C. AS THE REQUIREMENT IS VALIDATED AND TASKED, THE FIRST COMMAND WITH ACCESS TO THE MRTM WILL INPUT THE REQUIREMENT AND NOTE DATE TIME GROUP OF THE ORIGINATOR. 6. REPLACEMENTS. MRTM DOES NOT RELIEVE COMMANDS OF THE NECESSITY TO DEVELOP CASUALTY ESTIMATES WITH THE APPROVED CASUALTY ESTIMATION (CASEST) MODEL IN ORDER TO PREDICT CASUALTY REPLACEMENT REQUIREMENTS. CASUALTY REPLACEMENTS WILL NOT BE LOADED IN THE MRTM BELOW HQMC LEVEL 3. REQUEST FOR CASUALTY REPLACEMENTS WILL BE MADE VIA SEPARATE CORRESPONDENCE. 7. MRTM DOES NOT REPLACE CURRENT GUIDANCE CONTAINED IN REFS D AND E PERTAINING TO SUBMISSION OF T/O CHANGE REQUESTS, WHICH IS ENCOURAGED. 8. MCMPS WILL CONTINUE TO BE USED TO PROCESS AND TRACK IA'S AT THE DEPLOYMENT PROCESSING COMMANDS (DPC) AND INITIAL DEPLOYMENT PROCESSING CENTERS (I-DPC). 9. THIS MARADMIN CANCELS REF D. 10. POLICIES AND PROCEDURES ASSOCIATED WITH MRTM WILL BE INCORPORATED INTO AN UPCOMING REVISION OF REF B. 11. THIS MARADMIN IS CANCELLED WHEN INCORPORATED IN REF B, AND FOR RECORD PURPOSES 19 FEB 2005.