UNITED24 - Make a charitable donation in support of Ukraine!

Military

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.

  2. 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.

    • Gives the name and description of the plan.
    • Defines Force Modules and nonstandard UTCs.
            1. Provides a place for planner’s remarks.

      1. Planning Factors File: Modified WMP-5. Shows planning factors specific to that theater.

      2. Personnel Working File: Personnel data created when nonstandard UTCs are used.
      3. Ports of Support File (POSF): Available theater ports
      4. Joint Flow Analysis System for Transportation (JFAST) control file: Contains information relating to the feasibility of inter-theater movement of planned forces.
      5. Medical Working File: Produced via the Medical Analysis Tool (MAT) subsystem. The MWF is used to compute patient numbers, lengths of hospital stay, death rates, and other losses. Assists medical planners in determining the medical feasibility of an OPLAN.

        1. Standard Reference Files. These files contain general information that is common to most plans, such as Locations, Unit Type Codes, etc. This data is accessed for reference or brought into plan unique files as a result of the planning process.
          1. Type Unit Data File (TUCHA). This file contains the movement characteristics of every approved unit type code.
          2. GEOFILE. The GEOFILE is a file created by JCS that provides a four letter identifier for every location used in planning. The file contains the name, geographic coordinates, identifier code, and type of facility listed.
          3. ASSETS/CHSTR: Contains information on the availability and planning factors for strategic lift assets
          4. GSORTS: Expresses unit readiness in terms of personnel and equipment
          5. TUDET: Descriptions and dimensions of specific wheeled or tracked equip, hazardous cargo, floating crafts, and non self-deploying aircraft, and items longer than 35 feet
          6. Characteristics of Transportation Resources (CHSTR). Standard planning factors for airlift and sealift available for deployment planning.
          7. Transportation Assets (ASSETS). Availability of strategic lift from JSCP.
          8. Port Characteristics (PORTS). Information on free-world seaports.
          9. Civil Engineering File (CEF). Standard engineering planning data used to develop the engineering force, and project material requirements for planning
    1. COMMON DATA ELEMENT CATEGORIES. To explain the meaning and use of the elements comprising a TPFDD, we will discuss them in three categories of information FORCE, UNIT, AND MOVEMENT data element categories.
      1. Force Data Elements
        2.
        1. Describes the TYPE of force required.
          1. Combat and support forces drawn from forces apportioned in USAF WMP-3.
          2. Non-unit records IAW WMP-5 Planning Factors.
        2. Usually entered into the TPFDD by the SUPPORTED CINC:
        3. Element examples:
          1. Unit Type Code (UTC). A five-character alphanumeric code associated with a particular type of unit. Designates a specific force package.
          2. Force Description. The 31 character field containing the name description of the force package
          3. AUTH (Authorized). The total number of personnel authorized for a (UTC)
          4. PAX. The number of passengers that will require transportation by a Transportation Component Command. This number may be less than the authorized (AUTH) number of personnel in the UTC, since some of the personnel may be traveling in unit-provided (organic) transportation (e.g., flying the F-16).
          5. Bulk cargo. The amount of cargo in an UTC that will fit on a standard Air Force cargo pallet (463L pallet).
      1. Over size cargo. The amount of cargo in the UTC that will fit on C-141 or

    C-130 aircraft, but exceed the size limits of the 463L pallet.

      1. Out size cargo. The amount of cargo that exceeds the size limitations of a C-141and C-130 aircraft, but will fit onto a C-17 or C-5.
      2. Not Air Transportable (NAT). The amount of cargo that cannot be moved by air due to size, weight, or hazard
      1. Unit Level Code (ULC). This states the operating level of the unit being tasked (e.g., team, flight, squadron, etc.).
      1. Unit Line Number (ULN). A code that uniquely describes a force entry (line entry) in a TPFDD. The ULN is made up of three elements: FRN, FRAG, and INSERT.
            • Force Requirement Number (FRN). A code used to uniquely identify force entries in a given OPLAN TPFDD.
            • FRAG. The FRAG provides additional data elements when the force requirement cannot be adequately
            • INSERT. When it is necessary to break down the description

    of a force requirement beyond the FRAG, the portions of the

    FRAG are assigned an INSERT identification.

      1. Cargo Increment Numbers (CINs) and Personnel Increment Numbers (PINs) CINs and PINs, like a ULN, are TPFDD records that project movement requirements for supplies and personnel that will result from unit requisitions, redeployment of unit unserviceable equipment, or repositioning of theater stocks.  They are often called non-unit moves
      2. Sequence Number. Every time a TPFDD is sorted, the first ULN will have

    the sequence number 00001, the next 00002, etc. The sequence number for

    any given ULN of a TPFDD will vary according to where that ULN falls in

    that particular sort.

      1. Unit Data Elements:
    1. Unit Data Elements of a TPFDD are the entries that describe the specific unit tasked to fill a force requirement.
    2. Usually provided by the SUPPORTING COMMAND.
          1. Determined at the WMP-3 beddown conference and published in the WMP 3-1 for COMBAT forces.
          2. Support force units are selected by the owning supporting commands at the TPFDD sourcing conference.
        1. Element examples:
          1. Unit Identification Code (UIC). Six-character code that identifies the specific unit tasked.
      1. Unit Name. The name of the tasked unit (e.g., 50th Airlift Squadron).
          1. Service. The military Service providing the force.

      1. Providing Organization. The command that provides the force requirement,

    such as AMC, ACC, etc.

      1. Movement Data Elements:
    1. Movement Data Elements of a TPFDD are the entries that provide the locations,

    dates, and methods of transportation.

    1. The data for these elements is provided by several sources, depending on the

      2. element

    2. Elements examples are:
          1. LOCATIONS. Location elements are the entries in the force data that provide the

    name and geographic locator code of any installation serving as Origin,

    Intermediate Location, Port of Embarkation, Port of Debarkation, or Destination

    for the deployment of forces. There are five Location Data Elements:

      1. DESTINATION. The station or location in an objective area where a unit will be employed.
      1. PORT OF EMBARKATION (POE). The geographic point in the routing scheme from which cargo or personnel depart on strategic transportation.
      2. PORT OF DEBARKATION (POD). The geographic point in the routing scheme at which cargo or personnel are discharged from strategic lift.
      3. INTERMEDIATE LOCATION. A point along a deployment routing scheme, other than origin, destination, POD or POE, at which a deploying unit will be scheduled to lay over for at least one day. Usually used for in-route training or equipping
      4. ORIGIN. The origin is the beginning point of a deployment. Usually the peacetime home of the deploying unit.
      1. DATES. TPFDD dates are stated in reference to the day that the contingency begins, the day is called C-Day. All other days are written into the plan in relation to that day (C010 is ten days after C-Day). There are five date elements in a TPFDD.
      1. Required Delivery Date (RDD). The latest date, relative to C-Day, that a force requirement must arrive at the DESTINATION to properly support the

    CONOPS.

      1. Latest Arrival Date (LAD). The latest date, relative to C-Day, that a force requirement must be at their Port of Debarkation (POD) in order to be at their OPLAN destination at the required time.
      1. Earliest Arrival Date (EAD). The date, relative to C-Day, that reflects the earliest date that a force requirement should arrive at a Port of Debarkation

    (POD).

      1. Available to Load Date (ALD). The date, relative to C-Day, that a force requirement must be prepared to load onto strategic transportation at the Port of Embarkation
      1. Ready to Load Date (RLD). The date, relative to C-Day, that a unit must be prepared to depart from their home station or ORIGIN.

    The dates and their corresponding locations are as follows:

     

     

      1. METHODS of movement. There are two TPFDD elements that deal with the

    method of deployment: MODE and SOURCE.

      1. MODE. The alphanumeric code for the type of transportation that a force requirement will use to deploy from one location to another (e.g., air, land, sea, optional, or not required).
      2. SOURCE. The alphanumeric code for the organization who will provide the transportation for a force requirement (e.g., AMC, MSC, MTMC, organic, or supported/supporting CINC).

    7. TPFDD MAINTENANCE

      1. DEFINITION. TPFDD maintenance is the process allowing a supported commander to incorporate changes to the TPFDD that have occurred since TPFDD refinement.
      2. PURPOSE: To systematically and effectively incorporate changes to the TPFDD files that may have occurred as a result of changes to unit sourcing, unit equipment changes, locations, etc.
      1. TWO TYPES:
        1. Periodic - Conducted as frequently as Supported CINC deems necessary.
        2. Rollover - Conducted in conjunction with JSCP cycle/JCS review.
      1. RESPONSIBILITIES:
        1. JPEC provides data to keep TPFDD current.
        2. USTRANSCOM hosts maintenance conferences and coordinates updates.
        3. Supported CINC is final authority for approving changes.
      1. INTENSIVE MANAGEMENT:
    1. Purpose - to keep initial stages of TPFDD current.
          1. Normally, first 7 days of air and first 30 days of sea movement.
          2. SUPPORTED CINC may specify different periods of Intensive Management.
    1. CAP - Execution Planning Update:
          1. Incremental updating accomplished during execution planning and execution.
          1. Ensures OPLAN data as current as possible for immediate execution.
        1. Practical considerations of Intensive Management:
          1. Large amounts of data can and will change as the operation unfolds. When the plan is being implemented, later portions of the plan will be incrementally updated as earlier portions ate being executed, to adjust to the actual results of the execution of earlier portions.
          1. Changes made to the early stages of the operation are likely to affect events taking place later on.
          2. Data must reflect even minor changes at execution.
          3. Changes to a plan require JCS approval prior to implementation, but the Supported Commander approves minor corrections or changes to a TPFDD.
        1. Benefits of Periodic Maintenance and Intensive Management:
          1. Reduces execution planning by decreasing the amount of changes that may have to be made at execution.
      1. By performing the periodic maintenance on the database, the JPEC maintains a pool of experienced, knowledgeable action officers.
      2. Expedites planning by starting with the most accurate data available at the time, rather than just what’s on the shelf.