CWPC Contingency Wartime Planning CourseCWPC Contingency Wartime Planning Course


Force Packaging

IP - 4200

INSTRUCTOR: Mr. Kenneth Hill

DESCRIPTION: This lesson introduces the student to force packaging and the force package codes, Unit Type Codes (UTCs).

OBJECTIVE: The object of this lesson is for each student to comprehend the structure of a force package and how force packages are used in wartime planning the process through which force packages are developed, and how the MEFPAK system works

SAMPLES OF BEHAVIOR: Each student will:

    1. Know the definition a force package.
    2. Know the main components of a force package.
    3. Explain how the MEFPAK system works
    4. Describe the benefits of Force Modules.
    1. Contrast the difference between a force module and a CORE UTC package.

REQUIRED READING:

1. Scan AFMAN 10-401, 2. Read AFMAN 10-401, "Force Modules, para 4.7.

2. Scan AFMAN 10-401, Chapter 5 And Chapter 6.

3. Review the CWPC Desktop Reference for definitions of the following:

a. Force Module (FM).

b. Logistics Detail (LOGDET).

c. Manpower and Equipment Force Packaging System (MEFPAK).

d. Manpower Force Element Listing (MFEL).

e. Mission Capability Statement (MISCAP).

 

OPTIONAL READING: None

 

 

 

 

 

 

 

 

TOPICAL OUTLINE:

1. Force package: A force package is a predefined standardized grouping of manpower and/ or equipment to provide a specific wartime capability. It is not unusual for a force package to be referred to as an UTC or an UTC package. In this lesson, force package and UTC package will be used interchangeably.

2. Main Components of a force package:

a. Unit Type Code (UTC). This is a 5-digit, alphanumeric computer code.

The assignment of an UTC categorizes each type organization into a class or kind of unit having common distinguishing characteristics. The first character of the code indicates its functional group. These are provided in Joint Pub 1-03.21, Table 6. Common Air Force designators for deployment capability are listed below.

1

Air Defense and Missiles

3

Mission Aircraft

3A

Airborne Cmd and Control Acft

3B

Bomber Aircraft

3C

Airborne Battlefield Cmd & Cntrl

3D

Electronic Combat Aircraft

3E

Air Defense

3F

Fighter Aircraft

3M

Military Airlift

3N

Tactical Airlift

3R

Reconnaissance Aircraft

3S

Special Ops Aircraft

3T

Search and Rescue

3W

Weather Aircraft

3Y

Refueling Aircraft

4F

Civil Engineering

6A

Special Ops Aircraft

6F

Command Information

6K

Comm and Info Systems

6S

Space/Nuclear

7E

Mobile Command and Control

7F

Theater Air Cont Sys

81

Special Tactics, Cmbt Cont

9

Unit Headquarters

9AA

Wing Headquarters

9AB

Group Headquarters

9AD

Air Refueling Hqs

9AL

Life Support

9AR

Rescue

CS

Manpower

CT

Majcom HQS

FF

Medical Services

H

Maint/Munitions

HE

Intermediate Maint

HF

Intermediate Maintenance

HFU

Battle Damage Repair

HG

Munitions and Maint

HR

Combat Search / Rescue Maint

JF

Supply/Fuels

LWR

Services

PF

Intelligence

QF

Security

RF

Personnel

UF

Transportation

X

All others (ops spt/weather)

XFB

Bare Base Support

XFFA

Comptroller

XFFC

Chaplain

XCFFG

Public Affairs

XFFJ

Legal

XFFK

Contracting

XFH

Combat Logistics

XFP

Operational Support SQ

XS

Safety

XW

Weather

       

 

b. Title. The package is further defined by a 31-character title.

c. Mission Capability (MISCAP) Statement. The MISCAP statement is a

short paragraph, which describes significant employment information and may or

may not be classified. The MISCAP contains:

(1). Brief explanation of mission capabilities.

(2). Statement concerning the types of bases to which the unit can be deployed (e.g., bare base, collocated operating base and main operating base etc.)

(3). List of the major functional areas included in the force element.

(4). Response Capability

(5). Other UTCs with which this UTC is used.

 

 

 

d. MFEL/LOGDET:

(1) Manpower Force Element listing (MFEL).

 

FAC-TITLE MANPOWER DETAIL

XFFS1 4635-TROOP ISSUE WHSEG

POSITION AFSC GRADE QUANTITY

SUBSIST OPNS SPEC 3K051 2

SUBSIST OPNS TECH 3K071 1

FUNCTIONAL TOTAL 3

XFFS1 RECAPITULATION OFFICERS AIRMEN CIVILIANS TOTAL

0 3 0 3

(2) Logistics Detail (LOGDET).

- Description

-- National Stock Number (NSN)

- Quantity

- Movement Characteristics

--Weight

--Size

 

3. Manpower and Equipment Force Packaging System (MEFPAK)

a. Definition. MEFPAK is the Air Force system for UTC package

management. It is the standard procedure for describing Air Force forces available for use in operation planning. It uses automated data systems to support contingency and general war planning with predefined and standardized manpower and equipment force packages.

b. Purpose. MEFPAK was established to provide standard descriptions of the force packages to be used to support contingency planning at all levels of command. MEFPAK is the source for identifying and communicating manpower and equipment planning data for all Air Force combat and support forces.

 

 

 

 

 

 

 

c. Subsystems:

    1. Manpower Force (MANFOR) Packaging System:

(a) MANFOR is a subsystem of both MEFPAK and the

Contingency Operation/Mobility Planning and Execution System

(COMPES). It contains the manpower detail for standard Air Force force packages.

(b) MANFOR provides

1. The standard Air Force means for timely identification

Of manpower requirements for mobility and operations

planning, requirements planning, program planning

documents, and readiness measurement.

2. The means to communicate wartime manpower

requirements to all levels of command.

(2) Logistics Force (LOGFOR) Packaging System:

(a) LOGFOR is a subsystem of both MEFPAK and COMPES

which contains the logistics detail for standard Air Force

packages.

(b) LOGFOR provides:

1. Passenger and detailed equipment planning data for use in

OPLANs and unit mobility plans.

2. A baseline for communication of logistics data.

 

4. Force Package Development:

a. Determine the need for a new force package:

(1) New equipment or organizations.

(2) Significant change in mission.

(3) Significant program changes.

b. Development Process:

(1) MEFPAK Responsible Command. (2) Functional Manager.

(3) AF/XOOW. (4) AF/ILXX.

(5) AFMRF (6) Other MAJCOMS

(7) Pilot/Non-Pilot Units.

 

5. Force Modules:

a. Definition: A grouping of combat and combat support force packages linked

together or uniquely identified so they may be extracted from or adjusted as an

entity in the time-phased force and deployment data file to enhance flexibility and

usefulness of the operation plan during a crisis.

b. Purpose. The primary purpose of a force module is to expedite

development of a TPFDD where there is no existing plan or to allow

modification of an OPLAN TPFDD in response to changes during execution.

c. There are two types of Force Modules:

(1) Service Modules.(unsourced)

(a) Mission orientated, not designed for a specific scenario

(b) Contains estimates of sustainment requiements

(2) OPLAN Dependent Modules.(sourced)

(a) Modified service modules

(b) Tailored for destination

1. Terrain

2. Weather

3. Expected conflice intensity

(c) Specific units

6. Core UTCS PACKAGES:

a. Description: Each Core UTC package is treated as an individual force module.

the concept links specific sourced UTCs to individual combat aviation

squadrons (or significant aviation deployment elements less than squadron size) to provide most of the support functions necessary to deploy and fight as a unit in a major regional conflict. (This is an Air Force only concept)

b. Concept Objectives:

    1. Improved command and control. They are sourced from the combat
    2. unit to the maximum extent possible. Remaining UTC requirements are sources from the nearest available source

    3. Improved transportation planning. Home station/regional sourcing
    4. allows close central location for APOE purposes.

    5. Improved planning process and reduced workload. Reduces amount
    6. of intra-conus movement requirements.

    7. Enhanced training. Unit can train with the same units they will deploy

and fight with.

 

c. Package Content:

(1) Combat Core: The combat core is specific to each individual

supported squadron. It contains specific aviation, maintenance,

wing/group headquarters and direct combat support UTCs that are

normally required by the type and number of aircraft in the linked aviation UTC (3----).

(2) Support Core: The support core normally consists of UTCs that are

oriented toward base population support, or functional area support that is

not necessarily dictated by the type or number of aircraft in the linked

aviation unit. Some UTCs are required to simply open the destination to

flight operations. Others are base operating support (BOS) UTCs

providing services necessary to "Fight the Base".