CWPC Contingency Wartime Planning CourseCWPC Contingency Wartime Planning Course


Force Planning

IP - 4120

INSTRUCTOR: MSgt Ricky Carter

DESCRIPTION: This period presents an introduction to force planning and the Time-Phased Force and Deployment Data as described by the Joint Operation Planning and Execution System, including an overview of the principle elements of the TPFDD, the purpose of each element, the source of its data, and how the elements interact with each other.

OBJECTIVES: The object of this instructional period is for each student to apply the TPFDD elements in relation to contingency wartime planning. To show an understanding of the JOPES programs and files used in TPFDD development, relate the data element sources, timing, and locations and to understand the purpose of TPFDD maintenance.

SAMPLES OF BEHAVIOR: Each student will:

  1. Know the definition and purpose of a TPFDD.
  2. Know the purpose of the TPFDD LOI
  3. Describe the difference between a plan-unique and a standard reference file
  4. Describe the JOPES software program used to create a TPFDD
  5. Describe each TPFDD data element category.
  6. Know the source (supported/supporting planner) of each TPFDD data element category.
  7. Relate the JOPES movement data elements with their locations.
  8. Demonstrate the ability to complete a TPFDD data element worksheet.
  9. Explain the benefits of TPFDD maintenance.
  10. Know the purpose of intensive management of the TPFDD.

 

 

 

 

REQUIRED READING:

  1. Refer to the Force List/Movement Requirements Working Paper (F11D) extract (4120-H-2) throughout this period.
  2. Review the CWPC Desktop Reference for definitions of the following:
  1. CINC
  2. Component Command
  3. Force Module
  4. Joint Operation Planning System (JOPES).
  5. JPEC
  6. PID
  7. SIPRNET
  8. Supported Command
  9. Supporting Command
  10. Transportation Component Command (TCC).
  11. Unit Type Code (UTC).
  12. WMP
  1. Complete the HOMEWORK ASSIGNMENT, Handout #1, of this lesson.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

TOPICAL OUTLINE:

INTRODUCTION: How do the National Command Authorities, the CINCS, and the Services identify the types of forces, locations of forces, and movement of forces required to achieve our National Security Objectives? (Answer: TPFDD).

  1. DEFINITION:
    1. A TPFDD is the computer-supported database of an OPLAN.
    2. It is a plan-unique JOPES database that lists the forces, beddown locations, and movement requirements for the forces of a particular plan.
    3. The data can be arrayed, sorted, and displayed to form meaningful computer lists (TPFDLs).
  1. PURPOSE:
  2. The TPFDD contains time-phased force data; non-unit related cargo and personnel data, and movement data for the operation plan. This automated data base allows planners to quickly and easily add, delete or modify force requirements, tasked units, locations and timing data.

  3. TPFDD Letter of Instruction (LOI)

The supported commander publishes a LOI at the beginning of the plan development phase of deliberate planning. The purpose of the LOI is to give the CINCs component commanders and supporting commands and agencies specific guidance on how the plan is to be developed. The supported commanderís staff will coordinate with affected commands such as USTRANSCOM and its components before publication to ensure that the guidance given in the LOI is current. The LOI must furnish specific guidance concerning these items:

    1. Priority of air movement for major units
    2. Apportionment of airlift capability between Service components and resupply
    3. Standard time windows for resupply defined by earliest arrival date (EAD) and latest arrival date (LAD)
    4. Resupply and non-unit personnel replacement planning factors
    5. Attrition planning factors
    6. Standard ports of embarkation (POEs) and ports of debarkations (PODs) for forces and channels of resupply
    7. Instructions on the use of JOPES identifiers like unit line numbers (ULNs), cargo increments numbers (CINs), personnel increment numbers (PINs), and force record numbers (FRNs)
    8. The CINCís required delivery dates (RDDs) and TPFDD points of contact for the supported and supporting CINCsí staff.
    9. Retrograde, chemical, and nuclear TPFDD procedures
  1. JOPES Software Programs used for TPFDD creation and modification.
    1. Requirements Development and Analysis (RDA). RDA is the primary program that provides the capability to create, add, modify, delete, and generate output on deployment-related information contained in an OPLAN TPFDD. RDA provides numerous functions to the Joint Planning and Execution Community (JPEC).
      1. Plan Population. Once the plan identification (PID) is initialized and available in RDA, requirements can be added through various activities. For example, new TPFDDs can be created quickly from existing TPFDDs. By accessing two TPFDDs simultaneously, you can copy part or all of one TPFDD to another.
      2. Requirements Generation. TPFDDs can be created by building basic movement requirements, individually or in groups, based on UTC and starting unit line number (ULN). Predetermined force modules (FMs) can also be used to quickly build a tailored TPFDD.
      3. TPFDD Maintenance. RDA offers planners and operators various options to manipulate the requirement elements of a TPFDD. Planners and operators can employ functions that edit graphic displays that directly change the data structure within a TPFDD. These capabilities are useful during both deliberate and crisis action situations. You may add new requirement records or delete already existing records. You may also modify requirement records. This includes timing, locations, and cargo detail.
      4. Availability of Deployment Information. You can display, view, and edit one or more of the various attributes of the movement requirements. The attributes include characteristics of the units, properties of their cargo (to Level 4 data), and the routing or itinerary data for planned movement. Individual or groups of requirements can be created, either from scratch or by copying others.
      5. Force Module Development and Maintenance. Force Modules can be used to edit, track, and analyze groups of requirements based on any number of factors. Force Module packages are as easy to construct and maintain as individual requirements.
      6. Availability of Reference File Information. RDA allows you access to standard reference files such as the Geographic Location File (GEOFILE), the Type Unit Characteristics Data File (TUCHA), and the Port Characteristics File (PORTS).
      7. Predefined Reports/Retrieval Generation. Many reports are included to identify such information as logical errors. Additionally, RDA offers a select function that allows you to query the requirements database for information of interest to assist in analysis.
      8. Map Displays. In the future, Map displays will allow you to view movement requirements in a geographic format.
      9. Relationship to the JOPES Core Database (External Integration). RDA operates directly off the JOPES Core database, thus it is connected to all systems using the database. Through the sharing of functional applications via the core relational database across different computer system platforms, RDA is able to support the many functions needed by the joint community. RDA is the only TPFDD building capability available providing network linkage.
    1. Other TPFDD Builders. There are other TPFDD building tools available at various sites and/or Services. RDA TPFDDs, however, are the only ones that can be networked across the SIPRNET.
      1. MAGTF II. The Marine Air/Ground Tactical Forces II (MAGTF II) application is referred to by the Marines as a "deployable JOPES" system. It is a laptop based planning system able to respond to a wide variety of operational requirements and is capable of calculating both sustainment and force lift requirements.
      2. JFRG. The Joint Force Requirements Generator (JFRG) was designed to support remote and forward deployed users with a PC based application. It is very similar to the Marine Corps program, MAGTF II.
      3. TARGET. The Theater Analysis and Replanning Graphical Execution Toolkit (TARGET) application is an operational planning set of tools that does more than just build TPFDDs. It supports situation assessment and development, COA development and selection, execution planning, and execution. Planners and operators can accomplish their tasks faster through rapid access to the required documents, information sources, analysis tools, and teleconferencing tools.
  1. JOPES ADP files used in TPFDD Development:
    1. Two kinds of data files: Plan Unique Files and Standard Reference Files:
      1. Plan Unique Files contain data that applies to only one plan or a specific area. Examples of Plan Unique Files are:
        1. TPFDD: This database lists the forces for one plan only.
    1. Summary Reference File: Includes all the added data for the TPFDD and is

created by the planner at the same time as the TPFDD.