Deployment Planning and Execution - S-1 Procedural Page

Role and responsibility

The unit FDP&E coordinator runs deployment planning at the unit per MCO 3000.18BMCO 3000.18B Marine Corps Force Deployment Planning and Execution Manual. The S-1 officer supports personnel inputs to the TPFDD per CJCSM 3122.01A. The S-1 chief reconciles personnel readiness with the deployment requirement. MARFOR commands coordinate sourcing feasibility through HQMC PP&O (PLN). MAGTF commanders own the deployment execution. The unit commander signs the sourcing recommendation.

Source documents flow from the OPLAN tasking, the GFM tasking per MCO 3120.12AMCO 3120.12A, the unit DRRS readiness state per MCO 3000.13BMCO 3000.13B, the personnel readiness data from MCTFS, the equipment readiness reports, the T&R event status, and the TPFDD development in JOPES per CJCSM 3122.01A. Outputs include the developed TPFDD entries, the sourcing feasibility submission, the personnel deployment transactions, the deployment execution support record, the in-stride personnel tracking, the redeployment closeout, and the audit trail.

Per MCO 3000.18B, the FDP&E Manual sets the procedural framework for Marine Corps force deployment. Per CJCSM 3122.01A (JOPES), the Joint planning system supports OPLAN execution. Per MCO 3120.12A, GFM and Force Synchronization coordinate force allocation across MARFORs. The personnel S-1 supports the planning by validating personnel readiness against the sourcing requirement.

Trigger events

• New OPLAN tasking arrives at the unit.
• GFM tasking from MARFOR or HQMC PP&O.
• TPFDD development window opens for the planned deployment.
• Sourcing feasibility request from MARFOR.
• Deployment execution date approaches.
• Personnel deployment transactions required at execution.
• RIP/TOA with relieving unit.
• Redeployment and closeout cycle initiates.

Processing workflow

1. Receive the OPLAN tasking or sourcing requirement. The unit FDP&E coordinator receives from MARFOR or HQMC PP&O (PLN).
2. Coordinate TPFDD development. Per MCO 3000.18BMCO 3000.18B and CJCSM 3122.01A, the TPFDD identifies personnel and equipment time-phased into the operational area.
3. Validate personnel readiness against the sourcing requirement. Per MCO 3000.13BMCO 3000.13B, the unit DRRS state reflects personnel readiness. The S-1 reconciles with the sourcing requirement.
4. Interface with JOPES. Per CJCSM 3122.01A, JOPES is the Joint planning system. The unit submits inputs through the parent command.
5. Submit sourcing feasibility through MARFOR. Per MCO 3120.12AMCO 3120.12A, MARFOR coordinates GFM tasking. Sourcing feasibility surfaces gaps in personnel or equipment.
6. Coordinate deployment sequencing. The TPFDD time-phasing drives the sequence of personnel and equipment movement.
7. Process personnel deployment transactions. Per MCTP 3-30GMCTP 3-30G, the S-1 supports personnel transactions including individual augment fills, dependency separation actions, and pre-deployment certifications.
8. Support deployment execution at the unit. The unit S-1 coordinates with the deployed S-1 on personnel actions during the deployment.
9. Track personnel in-stride. The S-1 tracks casualties, replacements, and personnel transactions against the TPFDD timeline.
10. Support redeployment. Per MCO 3000.18B closeout procedures, redeployment processing and reset cycle complete the deployment.

Systems of record and forms

Systems

• Joint Operation Planning and Execution System (JOPES). Per CJCSM 3122.01A.
• Marine Corps Total Force System (MCTFS). Personnel readiness data feed.
• Defense Readiness Reporting System (DRRS). Per MCO 3000.13B.
• MARFOR command planning systems. Per MCO 3000.18B and 3120.12A.
• TPFDD development tools. Per JOPES.

Forms

• TPFDD Development Worksheet. Per MCO 3000.18B and JOPES.
• Sourcing Feasibility Memorandum. Per MCO 3120.12A.
• Personnel Deployment Tasking Order. Per MCO 3000.18B.
• Pre-Deployment Readiness Check List. Per the deployment cycle.
• Redeployment Closeout Memorandum. Per MCO 3000.18B.

Common pitfalls

• TPFDD inputs late. Per MCO 3000.18BMCO 3000.18B and CJCSM 3122.01A, the sourcing timeline drives the TPFDD development.
• Sourcing feasibility submitted without personnel readiness validation. Per MCO 3000.13BMCO 3000.13B, the DRRS state supports feasibility.
• Personnel deployment transactions missed. Per MCTP 3-30G, the S-1 supports transactions including individual augments and dependency separation.
• JOPES interface not coordinated. Per CJCSM 3122.01A, the JOPES inputs flow through the parent command.
• Redeployment closeout skipped. Per MCO 3000.18B, the closeout supports unit refit.
• Personnel in-stride tracking lagged. The S-1 maintains current personnel count against the TPFDD.

Decision points

• TPFDD sequence. Per MCO 3000.18B and JOPES, the OPLAN time-phasing drives the sequence.
• Sourcing feasibility recommendation. Per MCO 3120.12A, the unit's recommendation supports MARFOR sourcing.
• Personnel deployment versus individual augment. Unit deployment moves the unit. Individual augment fills route through OSCAR or joint tasking.
• Redeployment timing. Per MCO 3000.18B, the redeployment timing aligns with the relief in place.

Authority

This sub-page sits under MCO 3000.18BMCO 3000.18B Marine Corps Force Deployment Planning and Execution Manual. CJCSM 3122.01A sets Joint Operation Planning and Execution System procedures. MCO 3120.12AMCO 3120.12A covers Global Force Management. MCO 3000.13BMCO 3000.13B covers readiness reporting. MCTP 3-30GMCTP 3-30G covers Manpower and Personnel Administration doctrine. DoDD 7730.65 sets DoD readiness reporting framework.

Related references

• MCO 3000.18B. FDP&E Manual.
• CJCSM 3122.01A. JOPES.
• MCO 3120.12A. GFM.
• MCO 3000.13B. Readiness Reporting.
• MCTP 3-30G. Manpower and Personnel Administration.
• NAVMC 3500.3E. T-R event 0170-OPER-2003.