CWPC Contingency Wartime Planning CourseCWPC Contingency Wartime Planning Course


PART IV Logistics Module (LOGMOD)

INSTRUCTOR: MSgt Ricky Carter

 

1. LOGMOD Definition. LOGMOD is a computer software program that runs on computers at both the MAJCOM and base level or through networked servers ("TG"). It is used to manage a database containing the logistics equipment and supplies for Air Force Unit Type Codes (UTCs).

2. Guidance on COMPES LOGMOD.

a. AFM 171-740 is the user's manual for LOGMOD.

b. AFMAN 10-401 describes the use of COMPES in support of the planning process.

c. OPRs for COMPES LOGMOD.

(1) LOGMOD Field Assistance Team DSN 596-5771.

(2) Standard Systems Group at Gunter AFB - DSN 596-4399.

3. Functional System Design and Capabilities. LOGMOD is composed of two program modules, MAJCOM and base level.

a. The MAJCOM module contains three subsystems LOGFOR, LOGPLAN and LOGFAC.

(1) The Logistics Force Packaging Subsystem (LOGFOR) provides the capability to create and maintain the standard database of logistics supplies and equipment for each UTC in the Air Force. This database is called the Logistics Detail (LOGDET). LOGFOR subsystem capabilities include:

(a) LOGDET reporting

(b) Standard UTC updates and distribution.

(c) Standard LOGDET microfiche.

(d) MEFPAK summary report.

(2) The Logistics Planning Subsystem (LOGPLAN) provides the capability to tailor or customize the plan unique UTC database of equipment and supplies for each USAF Operational or contingency plan. This database is called the Logistics Plan File (LPF). LOGPLAN subsystem capabilities include:

(a) Operation Taskings and Priorities (OT&P) TPFDD interface.

(b) LOGFOR interface.

(c) Separate OPLAN databases.

(d) Customizing or tailoring of OPLAN tasked UTCs.

(e) Printed products.

(3) The LOGFAC subsystem of LOGMOD supports the logistics feasibility assessment of operational plans. MAJCOM LOGFAC subsystem capabilities include:

(a) The War Consumables capability of the LOGFAC subsystem is used to generate the War Consumables Distribution Objective (WCDO). The WCDO is a printed report showing each base how much fuel, munitions and other consumables they will need to store for wartime use based on the aircraft activity identified in the WMP-4 for that base.

(b) The Force Supportability capability of the LOGFAC subsystem is used to "what if" the war. Using this capability a MAJCOM can decide if they have enough bombs, bullets, fuel and other consumables on hand to support a specific TPFDD force or OPLAN. For example: If we were planning an invasion of Panama, we could use this capability to see if we have enough consumables on hand to support the invasion.

(c) The Assets and Material Rating (AMR) capabilities of the LOGFAC subsystem provide asset visibility. These capabilities are used much like SORTS to provide information on the status of our consumables and bare base equipment. The AMR capability provides reports showing on-hand versus required quantities for war consumables and reports showing the in-commission status of bare base equipment such as HARVEST FALCON and HARVEST EAGLE.

(d) The Wartime Aircraft Activity Reporting capability is used to update the WMP-4 Wartime Aircraft Activity (WAA).

b. The base level module of LOGMOD contains three subsystems LOGFOR , LOGPLAN, and Deployment Schedule of Events (DSOE).

(1) The Logistics Force Packaging Subsystem (LOGFOR) manages the standard database (LOGDET) of logistics supplies and equipment for each UTC on the base. Base level LOGFOR subsystem capabilities include:

(a) Creating and updating standard UTCs.

(b) LOGDET reporting.

(c) Printed products.

(2) The Logistics Planning Subsystem (LOGPLAN) manages the plan unique database (LPF) of logistics supplies and equipment for each UTC the base is tasked for in USAF operational and contingency plans. Base level LOGPLAN subsystem capabilities include:

(a) Building an LPF from scratch.

(b) Tailoring or customizing of OPLAN tasked UTCs.

(c) Load and packing lists.

    1. Equipment listings by OPLAN.

(3) The Deployment Schedule of Events subsystem provides the information necessary to exercise command and control of deployment actions. DSOE is an on-line schedule of events to be used by the Deployment Control Center (DCC) personnel to monitor deployment processing status. DSOE receives information from Manpower and Personnel Module Base level (MANPER-B) to produce schedules and transfers data to the Computer Aided Load Manifesting (CALM) program to produce load plans

4. LOGMOD design and capabilities summary:

LOGMOD-MAJCOM LOGMOD-Base Level

LOGFOR : Dealing with standard UTCs or the databases containing them.

 

LOGPLAN: Deals with tailored UTCs or tailored databases (OPLAN specific). Used by planners to create OPLAN specific logistics planning file (LPF)

 

LOGFAC: Deals with the assessing the logistics feasibility of plans (WCDO, WMP-4 inputs etc).

 

 

 

 

LOGFOR: Dealing with standard UTCs or the databases containing them. Used by pilot units to develop standard UTC details and to report the details up channel for inclusion into JOPES.

 

LOGPLAN: Deals with tailored UTCs or tailored databases (OPLAN specific). Used by base planners to create OPLAN specific logistics planning file (LPF). Provides base planners with load and packing lists.

DSOE: Creates deployment schedule of events.

 

 

 

 

 

 

 

PART V Integrated Deployment System (IDS)

INSTRUCTOR: MSgt Ricky Carter

  1. Definition: IDS is a system of five independent stand alone data automation systems integrated to assist the installation level planners in managing their deployment requirements as well as providing in-transit visibility for these assets. These systems consist of: LOGMOD, MANPER, DeMS, CMOS, and CALM
    1. LOGMOD-B (Logistics Module) - Receives and maintains the cargo portion of UTCs and taskings. Maintains detailed records on cargo (i.e.. Nomenclature, NSN, weight, cube, dims, etc.) as well as a command and control capability through the Deployment Schedule of Events (DSOE) module.
    2. MANPER-B (Manpower and Personnel Module) - Receives and maintains the personnel data for UTCs and taskings.
    3. DeMS (Deployment Management System) - Is a unit level program that is the vehicle used to manage personnel and cargo data. Information is passed electronically between the units, LGX, PRU, & Trans. Provides units commanders with the ability to track information on shots, training, taskings, personnel and cargo details. Units can assign personnel to DRD line number, chalk C & P, PRU cut orders from info in DeMS
    4. CMOS (Cargo Movement Operating System) - Is a transportation system that automates manifesting movement of cargo and personnel. It also provides in-transit visibility. Roughly equivalent to Federal Express in tracking items from door to door. We can track deployment from location to the final destination. All actions can be monitored from base level or higher headquarters.
    5. CALM (Computer Aided Load planning and Manifesting) - Automated Load planning to ensure proper weight and balance of aircraft cargo load as well as optimal use of available cabin limits.
  2. Both LOGMOD and MANPER review deployment taskings at the wing.
    1. Equipment Flow: Equip taskings selected and tailored in LOGPLAN portion of LOGMOD, are then copied into LOGMOD DSOE for TCN creation, schedule of events development, and chalk assignment.
    1. Personnel Flow: MANPER requirements are provided as two separate processes. The manpower office through the MANPER-B interface provides the UTC/tasking requirements to DeMS. The Personnel Readiness Unit (PRU) provides the units personnel data to DeMS to allow unit planners to match personnel with requirements.
  1. Benefits of IDS provided over the old paper work shuffle:
    1. Streamlines and automates the wing-level deployment process. Features Include:

Automated DSOE in LOGMOD eliminates need for augmentees in DCC to post.