IP-322 Force Sourcing We Produce the Future Mr. Jason Benton
Who? WHAT WHO HOW WHERE WHEN ULN UTC UIC MODE & SOURCE DEST. RDD
Overview Force Sourcing Sourcing Methodologies Joint Force Providers (JFP) Joint Capabilities Requirements Manager (JCRM) Sourcing for Contingency and execution AF Sourcing Processes
JP 5-0, Joint Operation Planning References CJCSM 3122.01A, JOPES Volume I, Planning Policies and Procedures AFI 10-401, AF Operations Planning and Execution CJCSM 3130.06, GFM Allocation Policies and Procedures (classified so not used in lesson) New RFF Template Updated JS duties and responsibilities Updated risks per CJCS Risk Matrix
Assignment, Apportionment, and Allocation Assignment: Forces and resources placed under combat commander by direction of the SECDEF in his Forces for Unified Commands Memo 2009 Forces AC AC RC RC Total Total SERVICE Units Equip Units Equip Units Equip HD A Bin B Bin USPACOM USELEMNORAD USNORTHCOM Forces not available for planning Forces for planning that are "not readily available" Forces for planning that are "readily available" Units Equip Units Equip Units Equip Units Equip Units Equip Units Equip Capability "A" 11 26 37 0 1 8 23 5 0 Capability "B" 14 3 17 108 3 14 79 96 12 1 2 26 Capability "C" 16 118 16 118 5 6 9 91 2 2 16 3 Capability "D" 12 140 6 80 4 36 12 140 2 24 Apportionment: Quantities of specific force types (force elements) reasonably expected to be available to respond globally Allocation: Forces provided to a Unified commander for execution Rotational or Emergent
Force Sourcing Defined GFMIG Force sourcing covers a range of sourcing methodology providing CCDRs with requested capabilities for planning, assessment, and execution JP 5-0 A range of methodologies that identify units to meet a force requirement during planning, plan assessment, or execution AFI 10-401 The comprehensive and collaborative process of assigning actual units to force requirements
Sourcing Methodologies Preferred Force Identification: Forces identified by supported Combatant Commander/Service Component to continue employment, sustainment, and transportation planning; forces are planning assumptions only Contingency Sourcing: Specific forces identified by Joint Force Providers (JFPs), assisted by their Service components, that meet Contingency planning requirements at a specified point in planning process Execution Sourcing: Forces recommended and identified by Joint Force Providers (JFPs) via their Service components and allocated by SecDef to meet Combatant Commander execution planning needs
Joint Force Providers (JFPs) Provide trained/ready capabilities and forces Joint Staff, J35 South, performs role of JFP for conventional forces USTRANSCOM is JFP for mobility forces USSOCCOM is JFP for special operations forces USSTRATCOM is Joint Functional Manager for missile defense (per GFMIG) JOINT FORCE PROVIDERS (JFPs) USTRANSCOM J35 CONVENTIONAL FORCES USSOCOM
AF Service Force Providers (FPs) Combatant Commander (CCDR) force request JS DJ3 US Strategic Command (Joint Force Manager) US Transportation Command JS DJ3 (J35S) US Special Operations Command Air Force Global Strike Command Air Mobility Command Headquarters Air Force And Air Combat Command Air Force Special Operations Command Missile Defense Mobility Forces Conventional Forces Special Operations Forces
Joint Capabilities Requirements Manager (JCRM) Web-enabled tool which facilitates GFM policy, processes and tools Automated requirements generation and validation Processes include: - Standardizes Request for Forces (RFF) Account for forces/capabilities committed to ongoing operations and constantly changing unit availability Identifies force/capability to best meet Combatant Commander needs - Force Tracking Number (FTN) created Request for Forces (RFF):the means to obtain not already assigned or allocated forces.
JCRM Systems Connectivity Execution Interface JOPES Capability/Task Interface Search Engine Interface JCAs JDEIS UJTL Service Tasks JCRM FMSWEB TFSMS GEO-FILE TUCHA DCAPES Requirements Interface FMTS JTIMS FRED JOPES
FORCE SOURCING PROCESSES JOPES DATABASE Requirements Validation Movement
CONTINGENCY PLANNING JOPES DATABASE Requirements Mainly sourced with GFMIG and WMP Forces. Transportation Validation
Contingency Planning 1. Service Components create TPFDD with force requirements and preferred force identification - Use assigned forces first, then apportioned 2. Combatant Command forwards to Joint Staff, J5 with preferred force ID and requests Contingency sourcing Normally top-priority plans 3. Joint Force provider (JFP) and Joint Force commander (JFC) to Contingency source specific plans per GFM Board approved schedule 4. JFPs request appropriate Service Force Providers (FPs) create sourcing solution
Contingency Planning 5. Service FPs identify units to fill TPFDD requirements 6. FPs return solution to Joint Force Providers 7. Joint Force Providers provide TPFDD with sourcing solution to Joint Staff, J5 8. JSCP Top Priority plan sourcing approved during IPR F 9. Sourced TPFDD goes back to Supported CCMD
TPFDD, Force Apportionment, & Contingency Sourcing 8. Approve SECDEF Disapprove If necessary, will occur during IPR F after Plan Development Supported Combatant CDR 1. OPlan TPFDD with Force Requirements & Preferred Force ID Service Components 9. Sourcing Solution 2. Request for Contingency Sourcing i.e. AFCENT, AFNORTH, AFSOUTH, PACAF, USAFE, 7AF for AF JS J5 7. Sourcing Solution 3. Validates & requests sourcing solution TRANS 4. Requests sourcing solution Joint Force Providers 5. Each Service Force Provider performs Sourcing Solution and/or Participates in Forces Conferences J35 Navy FPs Army FPs Marines FPs Air Force FPs SOC 6. TPFDD with Unit Data Elements
EXECUTION PLANNING JOPES DATABASE Requirements Movement Validation
Rotational-Annual Baseline - CCDR Submits FY forces requirements - Vehicle is RFF in JCRM - Global Force Management Allocation Plan (GFMAP) outlines forces for year RFF Joint Staff JOINT FORCE PROVIDERS (JFPs) Emergent - Requirements not met by assigned or allocated forces -Vehicle is RFF in JCRM and MSG -SDOB is the process by which ALL orders are taken to the SECDEF for decision (GFMAP Mod) USTRANSCOM J35 CONVENTIONAL FORCES USSOCOM
EXECUTION PLANNING JOPES DATABASE Requirements Movement Validation
Execution Rotational Process 1. Supported Service Component planners determine forces required for ongoing operations Validate continuing need for forces in coming FY Considers shaping, engagement, and stabilization 2. Combatant Command consolidates RFF for FY RFF processed via JCRM, submitted to the JS 3. Joint Staff J3 validates and assigns to JFPs 4. & 5. JFPs and their Service FPs create sourcing solution 6. & 7. Force nominations go back to Joint Staff 8. Joint Staff approved solution goes in GFM Allocation Plan (GFMAP) and GFMAP mods
EXECUTION PLANNING JOPES DATABASE Requirements Movement Validation
Execution Emergent Process 1. & 2. Supported planners determine forces required Review assigned & previously allocated in-place/inbounds for mission adequacy If additional forces required, submit RFF for adds RFF processed using JCRM and message 3. Joint Staff J3 validates and assigns to JFPs 4. & 5. JFPs task and their Service FPs create sourcing solution 6. & 7. Force Nomination goes back to Joint Staff 8. Joint Staff approved solution goes into GFMAP modification; SecDef Approves/Disapproves
Supported Combatant CDR Joint Task Force Service Components 9. Approved Allocation 2. RFF / RFC RFF, Force Allocation, & Execution Sourcing 8. Approve 1. RFF for FY in JCRM (rotational) SECDEF JS J3 1. RFF for adds in JCRM & MSG (emergent) i.e. AFCENT, AFNORTH, AFSOUTH, PACAF, USAFE, 7AF for AF Disapprove GFMAP 7. Sourcing Recommendation 3.Validates & assigns to a JFP TRANS 4. Force Request Tasker Joint Force Providers Navy FPs Army FPs Marines FPs Air Force FPs J35 6. Force Nomination 5. Each Service Force Provider performs Sourcing Solution and Force Nomination SOC
Contingency vs Execution 1. JOPES Contingency 1. JCRM Execution 2. J5 Validates 3. Apportionment 4. IPR per GFMB schedule 5. JFPs & Service FPs devise Contingency sourcing solution 6. Level 3 and 4 Contingency plans with TPFDDs 2. J3 Validates 3. Allocation 4. GFMAP 5. JFPs & Service FPs devise execution sourcing solution 6. Emergent & Rotational requirements for actual operations
Execution Sourcing Solutions Standard Force Solution: Ready, joint capable force executing its core mission Joint Force/Capability Solution: Force executing core mission in place of another Service In Lieu Of: Alternative force executing missions/tasks outside of its core competencies Ad Hoc: Personnel and equip from multiple commands/services Joint Individual Augmentation: Fill JTF Staff Headquarters per Joint Manning Document
AF Sourcing Joint Force Providers (JFPs) J35 South AF Service Force Providers (FPs) (Force Management Responsibility) HAF&ACC AFSOC (SOF) Personnel Mgmt & AF Svc Component Policy TRANSCOM AMC CSAF A1 & A3OD SOCOM AFSOC STRATCOM AFGSC AFPC/ DP2
AF Contingency Planning 1. 2. 3. 4. No change from previous joint process 5. For unavailable aviation and associated maint/muns ACC/A3 provides substitutes 5. After in-theater assets and Aviation forces are sourced, AF/A3OD receives for Combat Support force sourcing Case 1: Uses automated sourcing application Case 2: Has conference with MAJCOMs and AFPC/DP2 6. Returns sourced TPFDD to JFP & supported AFFOR
TPFDD, Force Apportionment, & AF Contingency Sourcing Approve SECDEF Disapprove If necessary, will occur during IPR F after Plan Development Supported Combatant CDR Sourcing Solution 2. Request for Contingency Sourcing 1. OPlan TPFDD with Force Requirements & Preferred Force ID AFFOR Component ing JS J5 Sourcing Solution 3. Validates & requests sourcing solution 5. Aviation sourcing ACC/A3X 4. Requests sourcing solution TRANS Joint Force Providers Navy Army Marines J35 HQ Air Force A3OD SOC 6. TPFDD with Unit Data Elements AFFOR Component ed 6. TPFDD with Unit Data Elements 5. Combat Support sourcing solution Other MAJCOM ings
AF Contingency Planning Sourcing logic normally follows these rules: I Source active duty aviation first II Air Reserve Component (ARC) aviation III Close Proximity to Aviation Origins. Support as close to aviation as possible. IV Maximum teaming. Source forces going to one destination from one location. V Residual requirements. Based on best fit to minimize number of origins for each destination.
AF Execution Planning 1. Supported AFFOR component planners determine aviation and CS force requirements Source from existing assigned forces & previously allocated in-place/inbounds (should not use forces already outbound to another theater in current FY GFMAP) If forces not available, submit RFF using JCRM & MSG 2.,3. and 4. No change 5. AF GFM Cells work with HAF & MAJCOM FAMs and AFPC/DP2 to develop sourcing solution 6. Solutions, or non-concurs (a.k.a. reclama), go back to JFPs - JFPs may give AF reclama to another service to fill 7. And 8. No Change 9.,10. Approved GMAP modification is forwarded to supporting Combatant CDRs and Services who produce DEPORDs (ACC does this for unassigned forces)
RFF, Force Allocation, & AF Execution Sourcing Solution SECDEF 8. Approve Disapprove GFMAP Supported Combatant CDR JTF 1. RFF 2.RFF in JCRM AFFOR Component ing AFFOR Component ed (*JFM) JS J3 TRANS 3. Validates & assigns to a JFP AFPC 7. Sourcing Recommendation 4. Force Request Tasker Joint Force Providers MAJCOM FAMs J35 Navy Army Marines GFM Cells & HAF FAMs SOC 6. Force Nomination 5. Use posture /coding, ART status, AEF scheduling, SECDEF 1:1 redline to develop solution
AFMED Force Requirement UTC UTC Title Auth Pers Pax Bulk Over- Sized Out- Sized Total Stons DEP ID C Day UIC Unit Origin RFL01 PFS COMMAND & CONTROL 4 4 0.0 0.0 0.0 0.0 P C001 RFL03 PFS FORCE SUPPORT BEDDOWN 13 13 0.0 0.0 0.0 0.0 P C004 RFL05 PFS BASE LEVEL CGO 1 1 0.0 0.0 0.0 0.0 P C004 RFL09 PFS STAFF AUG 4 4 0.0 0.0 0.0 0.0 P C004 RFL03 PFS FORCE SUPPORT BEDDOWN 13 13 0.0 0.0 0.0 0.0 P C012 Rotational AEF period 4 and RCP5
UTA, ART Status & AEF UTC UTC Description UIC Unit Origin State CMD Comp P- CODE ART AEF AEF PERIODS RFL01 PFS COMMAND & CONTROL FFYRX0 358 FSS JONAS SALK LUNA AFMED Active DX GRN ACS01 1&4 RFL01 PFS COMMAND & CONTROL FFD9X0 72 FSS TINKER AFB OKLA AFMC Active DW GRN ACS12 3&6 RFL01 PFS COMMAND & CONTROL FFYRZ0 20 FSS SHAW SC ACC Active DW GRN ACS07 2&5 RFL01 PFS COMMAND & CONTROL FFD7X0 28 FSS ELLSWORTH SD ACC Active DW YEL ACS12 3&6 RFL01 PFS COMMAND & CONTROL FFY6X0 60 FSS TRAVIS CA AMC Active DW RED ACS03 1&4
Force Requirement UTC UTC Title Auth Pers Pax Bulk Over- Sized Out- Sized Total Stons DEP ID C Day UIC Unit Origin RFL01 PFS COMMAND & CONTROL 4 4 0.0 0.0 0.0 0.0 P C001 RFL03 PFS FORCE SUPPORT BEDDOWN 13 13 0.0 0.0 0.0 0.0 P C004 RFL05 PFS BASE LEVEL CGO 1 1 0.0 0.0 0.0 0.0 P C004 RFL09 PFS STAFF AUG 4 4 0.0 0.0 0.0 0.0 P C004 RFL03 PFS FORCE SUPPORT BEDDOWN 13 13 0.0 0.0 0.0 0.0 P C012
UTA, ART Status & AEF UTC UTC Description UIC Unit Origin State CMD Comp P-CODE ART AEF AEF PERIODS RFL03 PFS FORCE SUPPORT BEDDOWN FFD5X0 358 FSS JONAS SALK LUNA AFMED Active DW GRN ACS01 1&4 RFL03 PFS FORCE SUPPORT BEDDOWN FFY4X0 72 FSS TINKER AFB OKLA AFMC Active DW YEL ACS12 3&6 RFL03 PFS FORCE SUPPORT BEDDOWN FF2W90 20 FSS SHAW SC SC ACC Active DW YEL ACS07 2&5 RFL03 PFS FORCE SUPPORT BEDDOWN FFC730 435 FSS RAMSTEIN AB GE USAFE Res DW GRN RCP 5 1&4 RFL03 PFS FORCE SUPPORT BEDDOWN FF2W70 49 FSS HOLLOMAN AFB NM ACC Active DW GRN ACS12 3&6 RFL03 PFS FORCE SUPPORT BEDDOWN FFC9K0 2 FSS BARKSDALE AFB LA AFSGC Active DW GRN ACS05 2&5
Sourced UTC UTC Title Auth Pers Pax Bulk Over- Sized Out- Sized Total Stons C Day UIC Unit Origin RFL01 PFS COMMAND & CONTROL 4 4 0.0 0.0 0.0 0.0 C001 FFYRX0 358 FSS JONAS SALK RFL03 PFS FORCE SUPPORT BEDDOWN 13 13 0.0 0.0 0.0 0.0 C004 358 FSS 358 FSS JONAS SALK RFL05 PFS BASE LEVEL CGO 1 1 0.0 0.0 0.0 0.0 C004 RFL09 PFS STAFF AUG 4 4 0.0 0.0 0.0 0.0 C004 RFL03 PFS FORCE SUPPORT BEDDOWN 13 13 0.0 0.0 0.0 0.0 C012 435 FSS USAFE RAMSTEIN AB
AF Crisis Planning 11. AFPC/DP2 (and some HAF FAMs) puts UICs against ULNs in DCAPES 12. Force providers verify availability of forces to include ability to meet TPFDD timelines MAJCOM FAMs use DCAPES AF Verification Capability (AFVC) to notify bases who accept or reclama Per JOPES Volume I, The sourcing process is complete once verification is accomplished. 13. Supported AFFOR component verifies sourcing to combatant commander who in turn validates Validation can then be forwarded to TRANSCOM
Validates & sends to TRANSCOM Force Allocation, & AF Execution Sourcing Verification Approve SECDEF Disapprove GFMAP Supported CCDR JTF AFFOR Component ing AFFOR Component ed JS J3 TRANS 9. SecDef approved GFMAP / SDOB 10. DEPORD Tasking 11. Loads solution into DCAPES AFPC Joint Force Providers J35 Navy Army Marines GFM Cells & HAF FAMs SOC 13. Verifies force availability NLT 24 hrs of DEPORD release 12. MAJCOM FAMs Base Notification
Air Force Sourcing Priorities (Emergent and Rotational) A. Validated CCDR and deployed commander s real-world contingencies B. JCS exercises C. Air Force exercises D. MAJCOM exercises and inspections E. Numbered Air Force (NAF) exercises F. Supporting wing and group exercises and events G. Manning assistance
Summary Force Sourcing Sourcing Methodologies Joint Force Providers (JFPs) Joint Capabilities Requirements Manager (JCRM) Sourcing for Contingency and execution AF Sourcing Process
Questions?