department of the navy oepartment of the … 4000.1_1.pdf · oepartment of the navy headquarters...

OEPARTMENT OF THE NAVYHEADQUARTERS UNITED STATES MARINE CORPS

3000 MARINE CORPS PENTAGONWASHINGTON, DC 20350-3000

NAVMC 4000.1LPO3 Feb 11

NAVMC 4000.1 War Reserve Materiel (WRM) Program Handbook

From: Director, Logistics Plans, Policies, and StrategicMobility Division

To: Distribution List

Subj: WAR RESERVE MATERIEL (WRM) PROGRAM HANDBOOK

Ref: (a) MCO 4400.39, War Reserve Materiel (WRM) Policy

Purpose. The WRM Program Handbook provides guidance to MarineForces on the execution of MCO 4400.39, WRM Policy.

Background. The WRM Program provides guidance for thecomputation, acquisition and management of ground materielrequired to sustain operating forces across a spectrum ofmissions and contingencies. This Handbook provides detailedguidance on actions associated with the roles andresponsibilities of the WRM Program in accordance with MCO4400.39.

Exceptions. This Handbook pnly addresses Class I, II, III(P),IV, VI, VII, VIII, and IX ground materiel. Further informationon Class V can be found in MCO 4400.39.

Action. Utilize the WRM Program Handbook to execute MCO 4400.39in alignment with the WRM Functions: Selection Criteria,Requirements Determination, Sourcing, Positioning, Acquisition,Distribution, and Management. The WRM Functions are the means bywhich the Marine Corps provides for sufficient materiel, withinthe limits of acceptable risk, to sustain operating forces- frominception to the establishment of the theater supportcapability.

DISTRIEUTION STATEMENT A: Approved for public release;

distribution is unlimited.

DEPARTMENT OF THE NAVYHEADQUARTERS UNITED STATES MARINE CORPS

3000 MARINE CORPS PENTAGONWASHINGTON. OC 20350.3000


NlWMC 4000.1 War Reserve Materiel (WRH) Program Handbook

From: Director, Logistics Plans, Policies, and StrategicMobility Division

To: Distribution List


Ref: (a) MCO 4400.39, War Reserve Materiel (WRM) Policy

Purpose. The WRM Program Handbook provides guidance to MarineForces on the execution of Mea 4400.39, WRM Policy.

Background. The vJRM Program provides guidance for thecomputation, acquisition and management of ground materielrequired to sustain operating forces across a spectrum ofmiisions and contingencies. This Handbook provides detailedguidance on actions associated with the roles andresponsibilities of the WRM Program in accordance with MCO4400.39.

§~~~12.~~Ens. This Handbook only addresses Class I, II, III (P) ,IV, VI, VII, VIII, and IX ground materiel. Further informationon Class V can be found in MCO 4400.39.

Accion. Utilize the WRM Program Handbook to execute MeO 4400.39in alignment with the WRM Functions: Selection Criteria,Requirements Determination, Sourcing, Positioning, Acquisition,Distribution, and Management. The WRM Functions are the means bywhich the Marine Corps provides for sufficient materiel, withinthe limits of acceptable risk, to sustain operating forces frominception to the establishment of the theater supportcapability.

DISTRIBUTION STATEMENT A: Approved for public release;distribution is unlimited.

l



Reserve Applicability. This NAVMC applies to the Marine CorpsTotal Force.

ff:IS4V72444e. K. HAVILAND

By direction

DISTRIBUTION: 10204830000Copy to: 7000110 (15)

7000153 (12)7000046 (40)7000012, 034, 154 (2)

7000144/8145001 (1)

ii



Reserve Applicability. This NAVMC applies to the Marine CorpsTotal Force.

2K~. K. HAVILANDBy direction

DISTRIBUTION:Copy to:

102048300007000110 (15)7000153 (12 )7000046 (40)7000012, 034, 154 (2)7000144/8145001 (1)

ii

NAVMC 4000.1

War Reserve Materiel (WRM)

Program Handbook

iii

NAVMC 4000.1

War Reserve Materiel (WRM)Program Handbook

III

Table of Contents

Selection Criteria l-1

Requirements Determination, Sourcing, Positioning 2-1Acquisition 3-1

Distribution 4-1

Management 5-1War Reserve System (WRS) Training: MEF Level Users Guide 6-1

War Reserve System (WRS) Training: Plan Level Users Guide 7-I

Class VIII Management 8-1Systems Descriptions 4-1

Terms of Reference 10-1

Governance ll-I

iv

Table of Contents

Selection criteria 1-1Requirements Determination, Sourcing, positioning 2-1Acquisi tion 3-1Distribution " 4-1Management 5-1War Reserve System (WRS) Training: MEF Level Users Guide 6-1War Reserve System (WRS) Training: Plan Level Users Guide 7-1Class VIII Management 8-1Systems Descriptions 9-1Terms of Reference 10-1Governance 11-1

iv

Selection Criteria

NAVMC 4000.1lAlar Reserve Materiel Program Handbook

Selection Criteria

rChapter 1

Selection criteria

NAVMC 4000.1War Reserve Materiel Program Handbook

.Selection Criteria

Chapter 1

1-1

Selection C 'teria

Table of Contents

A. War Reserve Materiel OW FunctionsB. Criteria for Selection of WRMC. Planning FactorsD. Combat Active Replacement Factors (CARFs)E. CARF Methodology

1-31-41-51-51-8

1. CARF Low Intensity Sustainment Phase (CARFLS) 1-9

a. Derivation 1-9

b. Formula 1-92. CARF Low Intensity Assault Phase (CARFLA) 1-9

a. Derivation 1-9

b. Formula 1-9

3. CARF Medium Intensity Sustainment Phase (CARFMS) 1-104. CARF Medium intensity Assault Phase (CARFMA) 1-105. CARF High Intensity Assault Phase/Sustainment Phase

(CARFHA/CARFHS) 1-10

Select

Table of Contents

A. War Reserve Materiel (WRM) Functions 1-3B. Criteria for Selection of WRM 1-4C. Planning Factors 1-5D. Combat Active Replacement Factors (CARFs) 1-5E. CARF Methodology 1-8

1. CARF Low Intensity - sustainment Phase (CARFLS) 1-9a. Derivation 1-9b. Formula 1-9

2. CARF Low Intensity - Assault Phase (CARFLA) 1-9a. Derivation 1-9b. Formula 1-9

3. CARF Medium Intensity - sustainment Phase (CARFMS) 1-104. CARF Medium Intensity - Assault Phase (CARFMA) 1-105. CARF High Intensity - Assault Phase/Sustainment Phase

(CARFHA/CARFHS) 1-10

1,.,

-.!.

iuu 'ciea

The WRM Functions are the means by which the Marine Corps provides forsufficient materiel, within the limits of acceptable risk, to sustainoperating forces from inception to the establishment of the theatersupport capability. This Handbook only addresses Class I, II, ZII(P),IV, VI, VII, VIII, and IX ground materiel. Further information onClasses V can be found in MCO 4408,39.

äItbuugb the WRM Functions are executed separately, they are mutuallysupporting activities. This Handbook defines the specific roles andresponsibilities for the participants associated with each function.Additional stakeholders may support these activities as appropriate.This chapter addresses the execution of the Selection Criteriafunction as it relates to the program.

Selection RequirementsCriteria Determination

Sourcing )Pooúion|ng )Acquiwitiuw > Distribution

Management

Figure 1.1: WRM Functions

1. Selection CriteriaSelection Criteria is the identification of ground equipment materieldeemed essential for the operational effectiveness of combat andcontingency operations, for which the Marine Corps computes asustainment requirement. (See Figure 1,2 below for descriptions ofeach class of supply.)

Class DescriptionClass I Subsistence (Food, rations, and water)Class II Clothing and Individual Items

CIass IIIPetroleum, Oils, and Lubricants; IncludingBulk Ground Fuel

Class IVLumber, Field Fortification andConstruction Materiel

Class V AmmunitionClass VI Personal Demand ItemsClass VII End ItemsClass VIII Medical suppliesClass IX Repair Parts

CIass XMateriel to support nonstandard militaryoperations

Figure 1'2: Classes of Supply

iter

A. War Reserve Materiel (WRM) Functions

The WPM Functions are the means by which the Marine Corps provides forsufficient materiel, within the limits of acceptable risk, to sustainoperating forces from inception to the establishment of the theatersupport capability. This Handbook only addresses Class I, II, III(P),IV, VI, VII, VIII, and IX ground materiel. Further information onClasses V can be found in MCO 4400.39.

Althou9h the WRM Functions are executed separately, they are mutuallysupporting activities. This Handbook defines the specific roles andresponsibilities for the participants associated with each function.Additional stakeholders may support these activities as appropriate.This chapter addresses the execution of the Selection Criteriafunction as it relates to the program.


1. Selection Criteria

Selection Criteria is the identification of ground equipment materieldeemed essential for the operational effectiveness of combat andcontingency operations, for which the Marine Corps computes asustainment requirement. (See Figure 1.2 below for descriptions ofeach class of supply.)

Class IClass II

Class III

Class IV

Class VClass VIClass VII

Class VII IClass IX

Class X

Subsistence (Food, rations, and water)Clothing and Individual ItemsPetroleum, Oils, and Lubricants; IncludingBulk Ground FuelLumber, Field Fortification andConstruction MaterielAmmunitionPersonal Demand ItemsEnd ItemsMedical suppliesRepair PartsMateriel to support nonstandard militaryoperations

Figure 1.2: Classes of Supply

1-3

lc,ction Criteria

B. Criteria for Selection of WRM

As a subset of the DODI 3010.06 War Materiel Requirement, the currentMarine Corps guidelines for selection of WRM for each Class of Supplyare provided in Figure 1.3, below.

Class'include& in WRM - -:. Important Note

I

Packaged Operational Rations(Meals Ready To Eat (MRE)Operational Rations(Unitized Group Rations (UGRs)/Unitized Group Rations-B (UGR-B)

Requirements calculated forplanning of anticipated demand;not actually held as WRMExcludes all other SubsistenceItems

II

Combat Essential End ItemsType 1 End Items TAMCN beginningwith A, B, C, D, or EType 2 End Items TAMCN beginningwith H, J, K, M, & NType 3 End Items TAMCN beginningwith T, U, V, W, & X

Must have CARFs AssignedMust have a Combat EssentialityCode (CEC)designating it as"Combat Essential"Excludes items that arecontractor/vendor-supportedduring the development phase

III

Oils, Petroleum, and LubricantsEssential for the OperationalReadiness of Equipment utilized inCombat

Requirements calculated forplanning of anticipated demand;not actually held as WRMExcludes Bulk Fuel Items

IV

Items Essential to the Establishmentand Protection of Base, Post, andStation in support of a CombatEnvironment such as Barriers,Construction Materiel, and Lumber

Requirements calculated forplanning of anticipated demand;not actually held as WRM

V Ammunition See MCO 4400.39

VI Health and Comfort Packs

Requirements calculated forplanning of anticipated demand;not actually held as WRMExcludes items required solelyfor comfort, convenience, ormorale

VIICombat Essential Major End Items

Type 1 End Items with TAMCNsbeginning with A, B, C, D, or E

Must have CARFs AssignedMust have a Combat EssentialityCode (CEC)designating it as"Combat Essential"Excludes items that arecontractor/vendor-supportedduring the development phase

VIII Medical Assets See MCO 4400.39

IX

Critical Repair Parts for CombatEssential End Items by which theirfailure will render the End Iteminoperable or incapable of fulfillingits mission

Must be designated as "CombatEssential" for the End Item.Excludes Items that arefabricated

X N/A Excluded from WRMFigure 1.3 WRM Selection Criteria

Once assets are selected as WRM, a requirement is computed for eachTable of Authorized Materiel Control Number (TAMCN) applied to eitheran associated planning factor or Combat Active Replacement Factor(CARF) . Planning factors are applied to TAMCNs associated with Class

1-4

Selection

B. Criteria for Selection of WRM

As a subset of the 0001 3010.06 War Materiel Requirement, the currentMarine Corps guidelines for selection of WRM for each Class of Supplyare provided in Figure 1.3, below.

Note

I

II

III

IV

V

VI

VII

VIII

IX

X

- Packaged operational Rations(Meals Ready To Eat (MRE)

- operational Rations(Unitized Group Rations (UGRs)/unitized Group Rations-B (UGR-B)

Combat Essential End Items- Type 1 End Items - TAMCN beginning

with A, B, C, 0, or E- Type 2 End Items - TAMCN beginning

with H, J, K, M, & N- Type 3 End Items - TAMCN beginning

with T, U, V, W, & Xoils, Petroleum, and LUbricantsEssential for the operationalReadiness of Equipment utilized inCombatItems Essential to the Establishmentand Protection of Base, Post, andstation in support of a CombatEnvironment such as Barriers,Construction Materiel, and LumberAmmunition

Health and Comfort Packs

Combat Essential Major End Items- Type 1 End Items with TAMCNs

beginning with A, B, C, 0, or E

Medical AssetsCritical Repair Parts for CombatEssential End Items by which theirfailure will render the End Iteminoperable or incapable of fUlfillingits missionN/A

- Requirements calculated forplanning of anticipated demand;not actually held as WRM

- Excludes all other SubsistenceItems

- Must have CARFs Assigned- Must have a Combat Essentiality

Code (CEC)designating it as"Combat Essential"

- Excludes items that arecontractor/vendor-supportedduring the develo ment phase


- Excludes Bulk Fuel Items


See MCO 4400.39- Requirements calculated for

planning of anticipated demand;not actually held as WRM

- Excludes items required solelyfor comfort, convenience, ormorale

- Must have CARFs Assigned- Must have a Combat Essentiality

Code (CEC)designating it as"Combat Essential"

- Excludes items that arecontractor/vendor-supportedduring the development phase

See MCO 4400.39

- Must be designated as "CombatEssential" for the End Item.

- Excludes Items that arefabricated

Excluded from WRMFigure 1.3 WRM Selection Criteria

Once assets are selected as WRM, a requirement is computed for eachTable of Authorized Materiel Control Number (TAMCN) applied to eitheran associated planning factor or combat Active Replacement Factor(CARF). Planning factors are applied to TAMCNs associated with Class

1-4

I, II secondary items, III, IV, and IX. CARFs are applied to TAMCNsassociated with Type 1 End Items designated as Combat Essential furClass II and Class VII.

C. Planning Factors

The planning factors for requirements determination, in Figure 1.4below, are established through a coordinated effort between allMARFOR/MEF Planners associated with WRM computations, except forhistorical usage data. Historical usage data is pulled from theauthoritative systems (SASSY and MIMMS or GCS3-MC+).

Class Planning Factors Used within the WRS

I

Approved force list, feeding plan, Days of Supply (D0S),Prisoner of War (EPW) factor, Safety Level Factor,environmental conditions

Enemy

IZFor secondary items - shelf-life attrition, environmentalfactors, DOS, approved force list

III Safety Level Factor and Demand FactorIl/ DOS, Safety Level Factor and usageIX Historical usage and deployment data, as required

Figure 1'4: Planning Factors

Additionally, see Chapter 2 for details on how planning factors areused to support requirements determination, Chapters 6 & 7 fortraining on how to input planning factors into the WRS, and Chapter 10for definitions of each planning factor listed.

D. Combat Active Replacement Factors (CARFs)

CABFa are established as a part of an Enterprise process (see SectionD of this chapter) and is a tool specific to WRM that determines therequirement quantity needed to keep the forces up to their Table ofEquipment (T/E} level in the event assets are destroyed or lost in acontingency operation. CARFs are established for Type l End Itemsdesignated as Combat Essential for Class II and Class VII.

CARFs are critical elements in the requirement determination due totheir effect on Marine Corps Acquisition. A minor change in a CARF foreither a high-density or high dollar value item can result in asignificant change in funding requirements. These factors also have adirect impact on the strategic lift and sustainment requirements for adoployiog Marine Air-Ground Task Force (MAGTF).

CARFs are established for combat essential materiel following PP&O'spublication of the essential equipment list (See Criteria forSelection of WRM, abone).

I, II secondary items, III, IV, and IX. CARFs are applied to TAMCNsassociated with Type 1 End Items designated as Combat Essential forClass II and Class VII.

C. Planning Factors

The planning factors for requirements determination, in Figure 1.4below, are established through a coordinated effort between allMARFOR/MEF Planners associated with WRM computations, except forhistorical usage data. Historical usage data is pulled from theauthoritative systems (SASSY and MIMMS or GCSS-MC*) .~ As applicable with C~SS-MC roll-out

I

II

IIIIVIX

Approved force list, feeding plan, Days of Supply (DOS), EnemyPrisoner of War (EPW) factor, Safety Level Factor,environmental conditionsFor secondary items - shelf-life attrition, environmentalfactors, DOS, approved force listSafety Level Factor and Demand FactorDOS, Safety Level Factor and usageHistorical usage and deployment data, as required

Figure 1.4: Planning Factors

Additionally, see Chapter 2 for details on how planning factors areused to support requirements determination, Chapters 6 & 7 fortraining on how to input planning factors into the WRS, and Chapter 10for definitions of each planning factor listed.

D. Combat Active Replacement Factors (CARFs)

CARFs are established as a part of an Enterprise process (see Sectiono of this chapter) and is a tool specific to WFM that determines therequirement quantity needed to keep the forces up to their Table ofEquipment (T/E) level in the event assets are destroyed or lost in acontingency operation. CARFs are established for Type 1 End Itemsdesignated as Combat Essential for Class II and Class VII.

CARFs are critical elements in the requirement determination due totheir effect on Marine Corps Acquisi\ion. A minor change in a CARF foreither a high-density or high dollar value item can result in asignificant change in funding requirements. These factors also have adirect impact on the strategic lift and sustainment requirements for adeploying Marine Air-Ground Task Force (MlI.GTF).

CARFs are established for combat essential materiel following PP&O'Spublication of the essential equipment list (See Criteria forSelection of WRN, above).

1-5

Selection Criteria

1. Process Flow Map

Ltter';.i.:' , t ' k ., x , 441::t*#,.. , 4#,.- Pit - -

rB Fenn i ra. I CARF InitiatIO41' 4` 1 l'4,0,

'

1.,- ,,,, ,PYL,' ,:,

040-T '.%S'S

lalki 'St

1' - #T .. t ,- ' ';NW Previolt bet - NextAO, Phastit AP:' P - yst.. t.;,,I.A

006a_Cl.

0O

-.---#..

- .4'''..r-

seni4

Ceii3(..)

o0

PMF",° `in

4, ,

' ,4,

e4

In ..8.Pt915

r ,

--,J*IS

0 'km

6 0I CO0 (44)M M

mo.

.

1

T

.4

7

i

. 4

Systétil*."

^-7--"TilPOP..--IL Z7INd

, -""0411M"l. ---% A,....N,

Figure 1.5: Biennial CARF Initiative Process Flow Map

1. Process Flow Map

Figure 1.5: Biennial CARF Initiative - Process Flow Map

1-6

2. Process Step Descriptions

Publish list of essential equipment

Description: In the second quarter of the odd (planning) year ofthe POM cycle, PP&O initiate the selection .criteria process byrequesting equipment recommendations from the MARFORs. Based onthe MARFORs input, PP&O publish by April a list of essentialequipment, including newly fielded/initial provisioning items forwhich a sustainment requirement will be computed.Input: MARFOR input

Output: List of essential equipment

2. CQr0iict CARF review/Mordification initiative

Description: CD&I leverage the PP&O list of essential equipmentand lead an initiative to review/modify the CARFs. This effort issupported by PP&O, I&L, MCLC, and MCSC.Input: List of essential equipmentOutput: Draft CARFs

3 . Approve 9ARF methodology

Description: I&L review and provide input on CD&I's draft CARFsuntil an approved methodology is reached.Input: Draft CARFs

Output: Approved CARFs

4. Input factors into TFSMS

Description: CD&I input approved CARFs into TFSMS by August andprovide data file to MCLC/MCSC via secure File Transfer Protocol(FTP).

Input: Approved CARFs

Output: TFSMS CARF file, Item Data File

5. Import factors into WRS

Description: MCLC/MCSC import factors into WRS in support of theEnterprise requirements determination process (see Chapter 2,Requirements Determination, MEF Level Recomputation Conference).

Input: Item Data File delivered via secure FTPOutput: WRS Item Data File

Figure 1.6: Biennial CARF Initiative Process Step Descriptions

2. Process step Descriptions

• Description: In the second quarter of the odd (planning) year ofthe POM cycle, PP&O initiate the selection criteria process byrequesting equipment recorrunendations from the MARFORs. Based onthe M}\B.FORs input, PP&O publish by April a list of essentialequipment, including newly fielded/initial provisioning items forwhich a sustainment requirement will be computed.

• Input: M}\RFOR input• Output: List of essential equipment

2. Coil.duct C

• Description: CD&I leverage the PP&O list of essential equipmentand lead an initiative to review/modify the CARFs. This effort issupported by PP&O, I&L, MCLC, and MCSC.

• Input: List of essential equipment• Output: Draft CARFs

• Description: I&L review and provide input on CD&I's draft CARFsuntil an approved methodology is reached.

• Input: Draft CARFs• Output: Approved CARFs

4.

• Description: CD&I input approved CARFs into TFSMS by August andprovide data file to MCLC/MCSC via secure File Transfer Protocol(FTP) .

• Input: Approved CARFs• Output: TFSMS CARF file, Item Data File

5. ImI>0rt factors,

• Description: MCLC/MCSC import factors into WRS in support of theEnterprise requirements determination process (see Chapter 2,Requirements Determination, MEF Level Recomputation COl1ferfE:l1ce).

• Input: Item Data File delivered via secure FTP• Output: WRS Item Data FileFigure 1.6: Biennial CARF Initiative - Process Step Descriptions

1-7

Selection Criteria

E. CARF Me th o do 1 ogy

CARFs are derived based on a methodology utilizing historicaldeployment and usage data to project an average daily loss rate over a30-day period. In order to estimate loss rates for a given conflictlevel over a 30-day time period, three essential pieces of data arerequired per Table of Authorized Materiel Control Number (TAMC0): time(duration of deploymemt), total number of items deployed to theater,total number of items destroyed by date. In cases where data does notexist (i.e. High Intensity Conflicts), combat modeling data is uaed.CARFs are categorized into two combat phases and three levels ofintensity.

Two phases of combat:

Assault (lst 30 days of combat)Sustainment (Every subsequent 30 day period)

Three intensities of combat:

Low Intensity Conflict (LIC): Political-military confrontationbetween contending states or groups below conventional war andabove the routine, peaceful competition among states. Itfrequently involves protracted struggles of competing principlesand ideologies. LIC ranges from subversion to the use of meansemploying political, economic, informational, and militaryinstruments to include irregular warfare scenarios. LICs areoften localized, generally in the third-world, but containedregional and global security implications.Medium Intensity Conflict (MIC): A Medium Intensity Conflict ischaracterized by the protracted employment of regular armedforces in combat as a major manifestation of power by the threatand responding nations, and the designation of militaryobjectives to achieve political and economic goals. It mayinclude some or all of the techniques and characteristics of lowintensity conflict.

m High Intensity Conflict (8ZC): The relatively unconstrained useof power by one or more nations to gain or protect territory andinterests that directly affects the survival of the nation. Theform of conflict is characterized by extreme levels of violence.The employment of the full range of military force sustained bythe preponderance of other national resources to achieve militaryand political victory is the primary use of nuclear weapons andmay include some or all of the characteristics of LIC and MIC.

lon C

E . eARF Methodology

CARFs are derived based on a methodology utilizing historicaldeployment and usage data to project an average daily loss rate over a30-day period. In order to estimate loss rates for a given conflictlevel over a 30-day time period, three essential pieces of data arerequired per Table of Authorized Materiel Control Number (TAMCN): time(duration of deployment), total number of items deployed to theater,total number of items destroyed by date. In cases where data does notexist (i.e. High Intensity Conflicts), combat modeling data is used.CARFs are categorized into two combat phases and three levels ofintensity.

Two phases of combat:

• Assault (1st 30 days of combat)• Sustainment (Every subsequent 30 day period)

Three intensities of combat:

• Low Intensity Conflict (LIC): Political-military confrontationbetween contending states or groups below conventional war andabove the routine, peaceful competition among states. Itfrequently involves protracted struggles of competing principlesand ideologies. LIC ranges from subversion to the use of meansemploying political, economic, informational, and militaryinstruments to include irregular warfare scenarios. LICs areoften localized, generally in the third-world, but containedregional and global security implications.

• Medium Intensity Conflict (MIC): A Medium Intensity Conflict ischaracterized by the protracted employment of regular armedforces in combat as a major manifestation of power by the threatand responding nations, and the designation of militaryobjectives to achieve political and economic goals. It mayinclude some or all of the techniques and characteristics of lowintensity conflict.

• High Intensity Conflict (HIC): The relatively unconstrained useof power by one or more nations to gain or protect territory andinterests that directly affects the survival of the nation. Theform of conflict is characterized by extreme levels of violence.The employment of the full range of military force sustained bythe preponderance of other national resources to achieve militaryand political victory is the primary use of nuclear weapons andmay include some or all of the characteristics of LIC and MIC.

1-8

tler

1.CARF Low Intensity Sustainment Phase (CARFLS)

4. Derivation4;:1, 4

The CARFLS is the CARF rate associated with a low intensity ofconflict for subsequent 30-day periods after the initial 30-dayassault period. In .contrast to the CARFLA, the subsequent periods donot include the maintenance deadline factor.

b. Formula

CARFLS=KIN

x 30davs

Where:N = Total number of items deployedK = Total number permanently lostT = Total number of days TAMCN was deployed to OIF/OEF (excludingPhantom Fury, Vigilant Resolve and OIF I)

Figure 1.7: CARFLS

2. CARF Low Intensity Assault Phase (CARFLA)

a. Derivation

CARF rate associated with a low intensity of conflict for the initial30 days of combat operations, the expected loss for the initial 30days of combat, plus a maintenance factor. The maintenance factor isincluded in order to account for a certain percentage of TAMCNs thatare inoperable due to maintenance issues.This maintenance factor is derived by calculating the arithmetic meanof maintenance deadlines of the individual TAMCN within deployedunits to Operation Iraqi Freedom (0IF) and Operation Enduring Freedom(OEF).

Formula

CARFLA. (KI N

30days)+Median Maint Deadline

Where:N = Total number of items deployedK = Total number permanently lostT = Total number of days TAMCN was deployed to OIF/OEF (excludingPhantom Fury, Vigilant Resolve, and OIF I)

Figure 1.8: CARFLA

!.~;c riter

1. CARF Low Intensity - Sustainment Phase (CARFLS)

The CARFLS is the CARF rate associated with a low intensity ofconflict for subsequent 3D-day periods after the initial 3D-dayassault period. In 'contrast to the CARFLA, the subsequent periods donot include the maintenance deadline factor.

b. Form:

KINCARFLS= --x 30davsT .

Where:N Total number of items deployedK = Total number permanently lostT = Total number of days TAMCN was deployed to OIF/OEF (excludingPhantom Fury, Vigilant Resolve and OIF I)

Figure 1.7: CARFLS

2. CARF Low Intensity - Assault Phase (CARFLA)

a. Deri

CARF rate associated with a low intensity of conflict tor the initial30 days of combat operations, the expected loss for the initial 30days of combat, plus a maintenance factor. The maintenance factor isincluded in order to account for a certain percentage of TAMCNs thatare inoperable due to maintenance issues.This maintenance factor is derived by calculating the arithmetic meanof maintenance deadlines of the individual TAMCN within deployedunits to Operation Iraqi Freedom (OIF) and Operation Enduring Freedom(OEF) .

b.

CARFLA= (K;N :< 30days) + Median Maint Deadline

Where:N Total number of items deployedK = Total number permanently lostT = Total number of days TAMCN was deployed to OIF/OEF (excludingPhantom F~ry, Vigilant Resolve, and OIF I)

Figure 1.8: CARFLA

1-9

Selection Criteria

3.CARF Medium Intensity Sustainment Phase (CARFMS)

a. Derivation

Like the low intensity sustainment CARF, the CARFMS is the CARF rateassociated with a medium intensity of conflict for subsequent 30-dayperiods after the initial 30-day assault period. The sustainmentCARFs do not include the maintenance deadline factor.

b. Formula

CARFMS=KINx 30days

Where:N = Total number of items deployedK = Total number permanently lostT = Total number of days TAMCN was deployed to Operations PhantomFury, Vigilant Resolve and OIF I

Figure 1.9: CARFMS

4.CARF Medium Intensity Assault Phase (CARFMA)

'a. 'Derivation

The CARFMA is the CARF rate associated with a medium intensityconflict for the initial 30 days of combat operations plus amaintenance factor. This maintenance factor, which was applied to theCARFLA formula, is not included for subsequent 30-day periods.

b. Formula

CARFMA= (KN

x 3 Odays) + Median Maint Deadline

Where:N = Total number of items deployedK = Total number permanently lostT = Total number of days TAMCN was deployed to Operations PhantomFury, Vigilant Resolve, and OIF I

Figure 1.10: CARFMA

5.CARF High Intensity Assault Phase/Sustainment Phase(CARFHA/CARFHS)

'a. Derivation

The Marine Corps has not been involved in a High Intensity Conflict(HIC) in over 50 years. Since historical data is outdated, therecurrently is no methodology determined for this factor.

Figure 1.11: CARFHA/CARFHS

Selection

3. CARF Medium Intensity - Sustainment Phase (CARFMS)

Like the low intensity sustainment CARF, the CARFMS is the CARF rateassociated with a medium intensity of conflict for subsequent 30-dayperiods after the initial 30-day assault period. The sustainmentCARFs do not include the maintenance deadline factor.

KINC4RFMS=--x 30davsT .

Where:N Total number of items deployedK = Total number permanently lostT = Total number of days TAMCN was deployed to Operations PhantomFury, Vigilant Resolve and OIF I

Figure 1.9: CARFMS

4. CARF Medium Intensity - Assault Phase (CARFMA)

The CARFMA is the CARF rate associated with a medium intensityconflict for the initial 30 days of combat operations plus amaintenance factor. This maintenance factor, which was applied to theCARFLA formula, is not included for subsequent 30-day periods.

CARFM4=CK

I N x30davs) + Median Maint DeadlineT o·

Where:N Total number of items deployedK = Total number permanently lostT = Total number of days TAMCN was deployed to Operations PhantomFury, Vigilant Resolve, and OIF I

Figure 1.10: CARFMA

5. CARF High Intensity - Assault Phase/Sustainment Phase(CARFHA/CARFHS)

The Marine Corps has not been involved in a High Intensity Conflict(HIC) in over 50 years. Since historical data is outdated, therecurrently is no methodology determined for this factor.

Figure 1.11: CARFHA/CARFHS

1-10

Recfuirements Determination, Sourcing, Positioning

JAVMC 4000.1War Reserve Materiel Program Handbook

Requirements Determination,Sourcing, Positioning

Chapter 2

lrements Determination, Sourcing, Positioning


Requirements Determination,Sourcing, Positioning

Chapte;c 2

2-1

Requirements Determination, Sourcing, Positioning

Table of ContentsA. WRM Functions

1. Requirements Determination2. Sourcing3. Positioning

2-32-32-3

2-4B. MEF Level Annual Recomputation Conference 2-5

1. Description2. Pre-Conference Activities 2-63. MEF Level Conference 2-104. Retail Activities 2-135. Wholesale Activities 2-156. MEF Level Prerequisite Data Checklist 2-187. EXAMPLE GUIDANCE MESSAGE FOR WAR RESERVE MATERIEL

REQUIREMENTS (WRMR) ANNUAL RECOMPUTATION CONFERENCE 2-20C. Plan Level Conference 2-22

1. Description 2-99

2. Pre-RECOMP Activities 9-23

3. Plan Level Conference 2-264. Post-RECOMP Activities 9-295. Plan Level Prerequisite Data Checklist 2-346. EXAMPLE GUIDANCE MESSAGE WAR RESERVE WITHRAWAL PLAN (WRWP)

CONFERENCE 2-357. Example of War Reserve Withdrawal Plans (WRWP)

Registration 9-37


Table of Contents

A. WRM Functions 2-31. Requirements Determination 2-32. Sourcing 2-33. positioning 2-4

B. MEF Level Annual Recomputation Conference 2-51. Description 2-52. Pre-Conference Activities 2-63. MEF Level Conference 2-1 04. Retail Activities 2-135. Wholesale Activities 2-156. MEF Level Prerequisite Data Checklist 2-187. EXAMPLE GUIDANCE MESSAGE FOR WAR RESERVE MATERIEL

REQUIREMENTS (WRMR) ANNUAL RECOMPUTATION CONFERENCE 2-20C. Plan Level Conference 2-22

1. Description 2-222. Pre-RECOMP Activities , 2-233. Plan Level Conference 2-264. Post-RECOMP Activities 2-295. Plan Level Prerequisite Data Checklist 2-346. EXAMPLE GUIDANCE MESSAGE WAR RESERVE WITHRAWAL PLAN (WRWP)

CONFERENCE 2- 357. Example of War Reserve withdrawal Plans (WRWP)

Registration 2-37

2-2

Deter mi nation,

A. WRM Functions

urc ng, °Jos t ionang

The WRM Functions are the Means by which the Marine Corps provides forsufficient materiel, within the limits of acceptable risk, to sustainoperating forces from inception to the establishment of the theatersupport capability. This Handbook only addresses Class I, II, III (P),

IV, VI, VII, VIII, and IX ground materiel. Further information onClasses V can be found in MCO 4400.39.

Although the WRM Functions are executed separately, they are mutuallysupporting activities. This Handbook defines the specific roles andresponsibilities for the participants associated with each function.Additional stakeholders may support these activities as appropriate.This chapter addresses the execution of Requirements Determination,Sourcing, and Positioning functions as they relate to the program.


Requirements,Determination Posffioning Aoquisition

Management

1. Requirements Determination

Requirements determination is the computation of actual quantities ofmateriel by class of supply that result in War Reserve MaterielRequirements (WRMR) budgeting and programming to resource the WRMProgram. WRMR quantities are computed based on equipment selected andassociated CARF/planning factors defined in Chapter 1 of thisHandbook.

There are currently two events within the WRM Program that accomplishthis task. The MEF Level Annual Recomputation Conference determinesbaseline WRMR for each MEF and MARFORRES to support fundinginitiatives. The conference also determines the MARFORRES Initial.Issue and, as required, the Active Force Initial Issue (SpecialTraining Allowance Pool (STAP)). The Plan Level Conference determinesthe WRMR tied to specific Operational Plans (OPLANs) or ContingencyPlans (CONPLANs) for the development of War Reserve Withdrawal Plans(WRWP).

2 . Sourcing

Sourcing is the registration of WRMR with the appropriate Marine Corpsor Department of Defense (DoD) agencies or the alignment of MarineCorps wide on-hand stocks to fulfill or satisfy the WRMR. This enablesthe WRM Program to effectively deliver materiel to support therequirements of the Combatant Commander. Type 1 End Item requirementsare registered with DC CD&I to support acquisition initiatives

2-3

L: ,~j r (:'nEon t::; [)(:::termination, scurci ,P05 10n1n9

A. WRM Functions

The WBM Functions are the means by which the Marine Corps provides forsufficient materiel, within the limits of acceptable risk, to sustainoperating forces from inception to the establishment of the theatersupport capability. This Handbook only addresses Class I, II, III (P),IV, VI, VII, VIII, and IX ground materiel. Further information onClasses V can be found in MCO 4400.39.

Although the WBM Functions are executed separately, they are mutuallysupporting activities. This Handbook defines the specific roles andresponsibilities for the participants associated with each function.Additional stakeholders may support these activities as appropriate.This chapter addresses the execution of Requirements Determination,Sourcing, and Positioning functions as they relate to the program.

Figure 2.1: WBM Functions

1. Requirements Determination

Requirements determination is the computation of actual quantities ofmateriel by class of supply that result in War Reserve MaterielRequirements (WBMR) budgeting and prograrruning to resource the WBMProgram. WBMR quantities are computed based on equipment selected andassociated CARF/planning factors defined in Chapter 1 of thisHandbook.

There are currently two events within the WBM Program that accomplishthis task. The MEF Level Annual Recomputation Conference determinesbaseline WBMR for each MEF and MARFORRES to support fundinginitiatives. The conference also determines the MARFORRES Initial'Issue and, as required, the Active Force Initial Issue (SpecialTraining Allowance Pool (STAP)). The P~an Level Conference determinesthe WBMR tied to specific Operational Plans (OPLANs) or ContingencyPlan::; (CONPLANs) for the development of War Reserve Withdrawal Plans(WRWP) .

2. Sourcing

Sourcing is the registration of WBMR with the appropriate Marine Corpsor Department of Defense (000) agencies or the alignment of MarineCorps wide on-hand stocks to fulfill or satisfy the WRMR. This enablesthe WBM Program to effectively deliver materiel to support therequirements of the Combatant Corrunander. Type 1 End Item requirementsare registered with DC CD&I to support acquisition initiatives

2-3


associated with resourcing the WRMR portion of the Marine Corps totalrequirement. Consumables and reparables are registered with theappropriate DoD or Marine Corps Integrated Materiel Manager (IMM) tocontract and budget for the acquisition of required materiel.

The MEF Level Annual Recomputation Conference and Plan LevelConference also include sourcing activities. The sourcing actions forWRMRF are the responsibility of each MEF at the conclusion of the MEFLevel Annual Recomputation Conference and Plan Level Conference as apart of their Retail actions. The sourcing actions that occur withinthe MEF Level Annual Recomputation Conference support subsequentfunding initiatives in the Program Objective Memorandum (POM) Cycle.The Plan Level sourcing actions support the alignment of tailoredrequirements to sustainment blocks that are parsed and sequenced tosupport a given numbered OPLAN/CONPLAN via the TPFDD. The liftrequirements generated by the sequenced requirements are assigned UnitLine Numbers (ULNs) that are registered with USTRANSCOM to ensureappropriate lift is available to support sustainment stock movement.

The sourcing actions for WRMRI are the responsibility of Marine CorpsLogistics Command (MCLC) , War Reserve Planning Branch (WRPB) . In orderto source WRMRI, WRPB initiates actions internal to the Marine Corpsto register Wholesale requirements with respective Integrated MaterielManagers (IMMs). Remaining requirement shortfalls are sourced externalto the Marine Corps through DoD IMMs. WRPB conducts these sourcingactivities during both conferences to ensure that all requirements areregistered.

3 . Positioning

Positioning is the physical and geographical locating of War ReserveMateriel Stocks (WRMS) in order to minimize lead times in support ofthe OPFOR and to effectively manage investments in equipment stocks.

Positioning activities are directly tied to sourcing activities.During the MEF Level Annual Recomputation Conference, WRPB providesrequirements to the IMMs for sourcing. At this point the IMMs gaincontrol over positioning and determine the most suitable location forthe purchased stocks.

During the Plan Level Conference, positioning is determined within theWRS designates geographical location codes per National Stock Number(NSN).

MCLC utilize WRMSI as a source of supply to satisfy the WRMR insupport of the execution of these objectives. When specified within anOPLAN/CONPLAN, MPF can be used to offset the WRMR.

Requirements Determination, Sou ng, Positioninq

associated with resourcing the WRMR portion of the Marine Corps totalrequirement. Consumables and reparables are registered with theappropriate 000 or Marine Corps Integrated Materiel Manager (IMM) tocontract and budget for the acquisition of required materiel.

The MEF Level Annual Recomputation Conference and Plan LevelConference also include sourcing activities. The sourcing actions forWRMRF are the responsibility of each MEF at the conclusion of the MEFLevel Annual Recomputation Conference and Plan Level Conference as apart of their Retail actions. The sourcing actions that occur withinthe MEF Level Annual Recomputation Conference support subsequentfunding initiatives in the Program Objective Memorandum (POM) Cycle.The Plan Level sourcing actions support the alignment of tailoredrequirements to sustainment blocks that are parsed and sequenced tosupport a given numbered OPLAN/CONPLAN via the TPFDD. The liftrequirements generated by the sequenced requirements are assigned UnitLine Numbers (ULNs) that are registered with USTRANSCOM to ensureappropriate lift is available to support sustainment stock movement.

The sourcing actions for WRMRI are the responsibility of Marine CorpsLogistics Command (MCLC), War Reserve Planning Branch (WRPB). In orderto source WRMRI, WRPB initiates actions internal to the Marine Corpsto register Wholesale requirements with respective Integrated MaterielManagers (IMMs). Remaining requirement shortfalls are sourced externalto the Marine Corps through 000 IMMs. WRPB conducts these sourcingactivities during both conferences to ensure that all requirements areregistered.

3. Positioning

Positioning is the physical and geographical locating of War ReserveMateriel Stocks (WRMS) in order to minimize lead times in support ofthe OPFOR and to effectively manage investments in equipment stocks.

Positioning activities are directly tied to sourcing activities.During the MEF Level Annual Recomputation Conference, WRPB providesrequirements to the IMMs for sourcing. At this point the IMMs gaincontrol over positioning and determine the most suitable location forthe purchased stocks.

During the Plan Level Conference, positioning is determined within theWRS designates geographical location codes per National Stock Number(NSN) .

MCLC utilize WRMSI as a source of supply to satisfy the WRMR insupport of the execution of these objectives. When specified within anOPLAN/CONPLAN, MPF can be used to offset the WRMR.

2-4

errInts Determination, Sourcino, Positioning

'.ClassOffSétg0SuPpIy.SottrOWS sdeeOrt

*:15.141,74'7 -d-WRM Pos?.,&loning,Upiv;itses

I LFORM, MPFII Initial Provisioning, MPF, In-storesIII LFORM, MPF, In-storesIV LFORM, MPF, In-storesVII Initial Provisioning, MPF, In-StoresIX, Initial provisioning, MPF, In-stores

Figure 2.2: Offset/Supply Sources Supporting WRM

B. MEF Level Annual Recomputation Conference

1. Description

The MEF Level Annual Recomputation Conference, which occurs the firstquarter of each fiscal year, develops the WRMR for each MEF andMARFORRES. The process is internal to the Marine Corps and determinesprimary sustainment to include materiel held by the MEFs (designatedas WRMRF), materiel held by MCLC or Marine Corps/DoD IMMs (designatedas WRMRI), and Initial Issue. The MEF Level Annual RecomputationConference provides baseline data to be used in the development of thePOM or to be used during the following budget cycle. The baseline dataalso supports tailoring of the requirements to OPLANs/CONPLANs in thecreation of WRWPs, during the Plan Level Conference.

The desired end state for the MEF Level Annual RecomputationConference is:

Generation of requirements data and submission of Type 1 EndItems for Class II and Class VII, designated combat essential(WRMR) to Deputy Commandant Combat Development and Integration(DC CD&I)

Generation of requirements data of Class I, III, IV and VI tosupport planning purposes (important note: these requirements arebased on anticipated demand, but will not be procured and held asWRM stocks)

Generation of requirements data and submission of Class IIsecondary items and Class IX consumable/reparablesCreation of a Posture Report and submission to Deputy CommandantInstallations and Logistics (DC I&L)

Registration of WRMR with Marine Corps/DOD IMMsDetermination of WRMRF for procurement by MEFsDetermination of Initial Issue for MARFORRES &Active Forces (as applicable based on STAP)

Determination of sustainment for MARFORRES

;'.' ;:c'm'211+':'s Determination, Sourcinq, PO:::iitioning

IIIIIIIV

VIIIX.

Figure

LFORM, MPFInitial Provisioning, MPF, In-storesLFORM, MPF, In-storesLFORM, MPF, In-storesInitial Provisioning, MPF, In-StoresInitial provisioning, MPF, In-stores

2.2: Offset/Supply Sources Supporting WRM

B. MEF Level Annual Recomputation Conference

1. Description

The MEF Level Annual Recomputation Conference, which occurs the firstquarter of each fiscal year, develops the WRMR for each MEF andMARFORRES. The process is internal to the Marine Corps and determinesprimary sustainment to include materiel held by the MEFs (designatedas WRMRF), materiel held by MCLC or Marine Corps/DoD IMMs (designatedas WRMRI), and Initial Issue. The MEF Level Annual RecomputationConference provides baseline data to be used in the development of thePOM or to be used during the following budget cycle. The baseline dataalso supports tailoring of the requirements to OPLANs/CONPLANs in thecreation of WRWPs, during the Plan Level Conference.

The desired end state for the MEF Level Annual RecomputationConference is:

• Generation of requirements data and submission of Type 1 EndItems for Class II and Class VII, designated combat essential(WRMR) to Deputy Commandant Combat Development and Integration(DC CD&I)

• Generation of requirements data of Class I, III, IV and VI tosupport planning purposes (important note: these requirements arebased on anticipated demand, but tvill not be procured and held asWRlvJ stocks)

• Generation of requirements data and submission of Class IIsecondary items and Class IX consumable/reparables

• Creation of a Posture Report and submission to Deputy CommandantInstallations and Logistics (DC I&L)

• Registration of WRMR with Marine Corps/DoD IMMs• Determination of WRMRF for procurement by MEFs• Determination of Initial Issue for MARFORRES &

Active Forces (as applicable based on STAP)• Determination of sustainment for MARFORRES

2-5

Pequirem Its Determination, Sourcing, Positioning

There are four phases that make up the MEF Level Annual RecomputationConference: Pre-Conference Activities, MEF Level Conference, RetailActivities, and Wholesale Activities.

oierecAttVibes

2. llAEF LevelConference

3

4401I. Wbolesa eActivities

Figure 2.3: MEF Level Annual Recomputation Conference Phases

2. Pre-Conference Activities

Pre-Conference Activities are conducted one to two months prior to theactual MEF Level Conference.

Participants in this phase are (See MCO 4400.39 for overall roles andresponsibilities):

Deputy Commandant Installations and Logistics (DC I&L) LogisticsPlans and Operations Branch (LPO)

Marine Corps Logistics Command (MCLC)

War Reserve Planning Branch (WRPB)

Marine Forces (MARFORs)

Marine Expeditionary Forces (MEFs)

Marine Forces Reserve (MARFORRES)

Systems used in this phase are (See Chapter 9 for SystemsDescriptions):

Marine Corps Action Tracking System (MCATS)Mainframe Systems (See Figure 9.1 for complete listing)

War Reserve System (WRS)

Requil:ement.s Determination I 5l1 urcing, PO:3i tioning

There are four phases that make up the MEF Level Annual RecomputationConference: Pre-Conference Activities, MEF Level Conference, RetailActivities, and Wholesale Activities.

Figure 2.3: MEF Level Annual Recomputation Conference Phases


Pre-Conference Activities are conducted one to two months prior to theactual MEF Level Conference.

Participants in this phase are (See Mca 4400.39 for overall roles andresponsibilities) :

• Deputy Commandant Installations and Logistics (DC I&L) LogisticsPlans and Operations Branch (LPO)

• Marine Corps Logistics Command (MCLC)• War Reserve Planning Branch (WRPB)• Marine Forces (MARFORs)• Marine Expeditionary Forces (MEFs)• Marine Forces Reserve (MARFORRES)

Systems used in this phase are (See Chapter 9 for SystemsDescriptions) :

• Marine Corps Action Tracking System (MCATS)• Mainframe Systems (See Figure 9.1 for complete listing)

• War Reserve System (WRS)

2-6

ments Determination, Sourcing, Positionìng

b. Process Flow Map

MEF Level Recomputation Conference wEipmz. (Doa-curneo 7t1 Pre'4°U3 0 4i= - System

Pre-Conference Activities

_I

15. 2o -,0

....u. T.

2 E lit

ce0

*2

Ti

Li.

2

Sy_s_!!!!!-...mmillibli"._-_-____14:"464° ., ,-,.....- ,,a..... , itar---., ., t.

Figure 2.4: Pre-Conference Activities Process Flow Map

c. Process Step Descriptions)rik ,...... 4 . ...b.

1. Initiate còördinatión forRecomputation ConAevence9z-

Description: LPO initiate coordination prior to estimated MEFLevel Annual Recomputation Conference message release.Input: POC information for Stakeholders

Output: Email/phone call

2. Cooidinate fOrChédule of RecoinputatIblit

Description: WRPB coordinate with LPO for scheduling of MEF LevelAnnual Recomputation Conference (taking into account upcomingconferences, exercises, etc. that may present conflicts forparticipants) . WRPB also provide LPO prerequisites for conferenceparticipants and coordinating instructions.Input: Email/phone call

Output: Prerequisites for conference; Coordinating instructions

9-7

ir0ments Determination, sourcing, Positioning

b. Process Flow Map

•........ '/F··..· ..... ... Key:MEF Level RecomputatIQn~o~ference m~~1loc:urenI

Pre-Conference Activities

0::ou.~~

u.w~

System

Figure 2.4: Pre-Conference Activities - Process Flow Map

c. Process Step Descriptions

1. Initiate

• Description: LPO initiate coordination prior to estimated MEFLevel Annual Recomputation Conference message release.

• Input: POC information for Stakeholders

• Output: Email/phone call

2. Coor$.:• Description: WRPB coordinate with LPG for scheduling of MEF Level

Annual Recomputation Conference (taking into account upcomingconferences, exercises, etc. that may present conflicts forparticipants). WRPB also provide LPG prerequisites for conferenceparticipants and coordinating instructions.

• Input: Email/phone call• Output: Prerequisites for conference; Coordinating instructions

2-7

zicemeots Detmzmioatioo, Sourcing, Pooitioniog

3. Release Recomputation guidance message

Description: LPO release the Guidance for FYXX War ReserveMateriel Requirements (WRMR) and Annual Recomputation Conferencevia Naval Message, announcing the conference NLT 30 days prior tothe conference. The message provides initial guidance relative tothe CARFs/logistics planning factors for each MEF and MARFORRES.It sets the dates for the conference, defines prerequisites forconference participants, sets parameters to be used forWRMR/Recomputation, and provides coordinating instructions.Participants confirm attendance at this point by filling out andreturning to MCLC the Conference Attendee Contact Informationform.

Input: List of prerequisites for conference; Coordinatinginstructions; Parameter data

Output: Naval Message

Document: Guidance for FYXX War Reserve Materiel Requirements(WRMR) and Annual Recomputation Conference; Conference AttendeeContact Information template

' -4. Task NEF to complete MPS training and provide guidance

Description: MADFURa task MEF participants in the MEF LevelAnnual Recomputation Conference to complete the training packagefound in NAVMC 4000.I and provide guidance accordingly.Input: Guidance for FYXX War Reserve Materiel Requirements (WRMR)and Annual Becompotatioo ConferenceOutput: Email (Attendance Confirmation)

Document: NAVMC 4800.1 - Chapter 6, Certificate of trainingcompletion

5. Complete WRS training

Description: MEFs ensure all attendees complete the War ReserveSystem (WRS) Training: MEF Level Users Guide and submitcertificate of training completion to WRPB via email prior toevent participation.Input: Guidance for FYXX War Reserve Materiel Requirements (WRMR)and Annual Recomputation Conference; NAVMC 4000'I - Chapter 6Output: Certificate of training completion submission


rements , sourcing, Pos

• Description: LPO release the Guidance for FYXX War ReserveMateriel Requirements (WRMR) and Annual Recomputation Conferencevia Naval Message, announcing the conference NLT 30 days prior tothe conference. The message provides initial guidance relative tothe CARFs/logistics planning factors for each MEF and MARFORRES.It sets the dates for the conference, defines prerequisites forconference participants, sets parameters to be used forWRMR/Recomputation, and provides coordinating instructions.Participants confirm attendanGe at this point by filling out andreturning to MCLC the Conference Attendee Contact Informationform.

• Input: List of prerequisites for conference; Coordinatinginstructions; Parameter data

• Output: Naval Message• Document: Guidance for FYXX War Reserve Materiel Requirements

(WRMR) and Annual Recomputation Conference; Conference AttendeeContact Information template

·ldance

• Description: MARFORs task MEF participants in the MEF LevelAnnual Recomputation Conference to complete the training packagefound in NAVMC 4000.1 and provide guidance accordingly.

• Input: Guidance for FYXX War Reserve Materiel Requirements (WRMR)and Annual Recomputation Conference

• Output: Email (Attendance Confirmation)• Document: NAVMC 4000.1 - Chapter 6, Certificate of training

completion

• Description: MEFs ensure all attendees complete the War ReserveSystem (WRS) Training: MEF Level Users Guide and submitcertificate of training completion to WRPB via email prior toevent participation.

• Input: Guidance for FYXX War Reserve Materiel Requirements (WRMR)and Annual Recomputation Conference; NAVMC 4000.1 - Chapter 6

• Output: Certificate of training completion submission• Document: NAVMC 4000.1 - Chapter 6, Certificate of training

completion

2-8

'Dents Determination, Sourcinc, Positioning

2 VZFL4ova1 3 Rota 4 Whot4441.Contemn.] 44844las belle*.

Gather materiel inlientory data.

Description: MEFs gather required data per instruction in LPO'sguidance message and the MEF Level Data Gathering Checklist andsubmit to WRPB.

Input: Guidance for FYXX War Reserve Materiel Requirements (WRMR)and Annual Recomputation Conference; NAVMC 4000.1 Chapter 2Output: Materiel inventory data submission

Document: NAVMC 4000.1 Chapter 2, MEF Level Data GatheringChecklist

Import 1og1s'ti4144,4

Description: WRPB import data into WRS via systems interface withinventory systems to include: SASSY, MIMMS, GCSS-MC*, DoDAAD,Provisioning, Item Apps, SCS and TDMS; and requirement systems toinclude TFSMS.

Input: Interface with inventory systems

Output: Wholesale data' Az applicabre vich GCSS-MC roll-out

8. Import Retail,data

Description: WRPB import materiel inventory data submitted byMEFs into WRS. Imported data becomes Retail data used in WRMRFdetermination.Input: Materiel inventory dataOutput: Retail data

Figure 2.5: Pre-Conference Activities Process Step Descriptions

;,-"> ~ C(':m':'llt::; Deterrnination, sourcing, PO:3itioning

6. Gather

• Description: MEFs gather required data per instruction in LPO'sguidance message and the MEF Level Data Gathering Checklist andsubmit to WRPB.

• Input: Guidance for FYXX War Reserve Materiel Requirements (WRMR)and Annual Recomputation Conference; NAVMC 4000.1 - Chapter 2

• Output: Materiel inventory data submission• Document: NAVMC 4000.1 - Chapter 2, MEF Level Data Gathering

Checklist

7 . IIllP()J:.'t

• Description: WRPB import data into WRS via systems interface withinventory systems to include: SASSY, MIMMS, GCSS-MC*, DoDAAD,Provisioning, Item Apps, SCS and TOMS; and requirement systems toinclude TFSMS.

• Input: Interface with inventory systems• Output: Wholesale data~ As dpplicdbl~ vich GCS$-MC roll-out

8. Import

• Description: WRPB import materiel inventory data submitted byMEFs into WRS. Imported data becomes Retail data used in WRMRFdetermination.

• Input: Materiel inventory data• Output: Retail dataFigure 2.5: Pre-Conference Activities - Process Step Descriptions

2-9

airements Determination, Sourcing, Pos itioning

3.MEF Level Conference

MEF-Level Conference Activities describe the procedures conductedduring the actual MEF Level Annual Recomputation Conference. Theconference duration may vary from year to year, depending on the needsof the Marine Corps, but all steps depicted are required to becompleted prior to conference conclusion.


Marine Corps Logistics Command (MCLC) War Reserve Planning Branch(WRPB)

Marine Expeditionary Forces (MEFs)(Note: Respective Marine Forces Command (MARFORCOM/MARFORPAC) provide oversight to their subordinate

MEF during this phase)



a. Process Flow Map

MEF 1140 ReOrnpútation Conference

MEF Level Conference

itati:g1

...grt"

Figure 2.6: MEF Level Conference Process Flow Map

Pas

3. MEFLevel Conference

MEF-Level Conference Activities describe the procedures conductedduring the actual MEF Level Annual Recomputation Conference. Theconference duration may vary from year to year, depending on the needsof the Marine Corps, but all steps depicted are required to becompleted prior to conference conclusion.

Participants in this phase are (See Mca 4400.39 for overall roles andresponsibili ties) :

• Marine Corps Logistics Command (MCLC) War Reserve Planning Branch(WRPB)

• Marine Expeditionary Forces (MEFs)(Note: Respective Mdrine Forces COIl'Jrldnd 01A.RFORCOM/MARFORPACj provide ot-"ersight to their subordln.~te



• War Reserve System (WRS)

a. Process Flow Map

Figure 2.6: MEF Level Conference - Process Flow Map

2-10

Determination, Soul:ell 'Positioning

b. Process Step Descriptions

Perform Wholesale file maintenance

Description: WRPB validate Wholesale data in WRS in preparationfor the MEF Level Annual Recomputation Conference, providing asnapshot of Marine Corps IMM inventory.Input: Wholesale data

10. Input parameter data

Description: MEFs input parameter data into the WRS in accordancewith LPO's guidance message in preparation for the computation.

Input: CARF guidance for the Recomputation; Navy Additive; MAGTFUnit Data; Plan Data; Days Of Supply (DOS) Data; Item DesignatorNumber (IDN) Data

Output: WRS database update

ïl Execute computation process

Description: WRPB run the WRS with complete parameter data set togenerate the WRMR.

Input: WRS database updateOutput: WRMR; Initial Issue

19. Review and modify requirements

Description: MEFs/MARFORRES have the opportunity to modify theirRetail quantities within the WRS.Input: WRMR; Initial Issue

Output: Modified WRMRF; Modified WRMRI; Modified T/A and STAP*(- = as applicable)

13. Send modified requirements to SRMO/CSP

Description: WRPB retrieve WRMR from the WRS and send Class IXdata to Secondary Repairable Management Office (SRMO) forvalidation IAW Repair Issue Point (RIP) Additionally, WRPB sendClass Type 1 End Items for Class II and Class VII CBRN materielto CSP. This.is the last opportunity to make adjustments toRetail quantities.

Input: Modified WRMRF; Modified WRMRI

Output: Validated WRMRF; Validated WRMRI

nat f S()tl


• Description: WRPB validate Wholesale data in WRS in preparationfor the MEF Level Annual Recomputation Conference, providing asnapshot of Marine Corps IMMinventory.

• Input: Wholesale data

• Description: MEFs input parameter data into the WRS in accordancewith LPO's guidance message in preparation for the computation.

• Input: CARF guidance for the Recomputationi Navy Additive; MAGTFUnit Data; Plan Datai Days Of Supply (DOS) Data; Item DesignatorNumber (IDN) Data

• Output: WRS database update

• Description: WRPB run the WRS with complete parameter data set togenerate the WRMR.

• Input: WRS database update• Output: WRMR; Initial Issue

• Description: MEFs/MARFORRES have the opportunity to modify theirRetail quantities within the WRS.

• Input: WRMRi Initial Issue• Output: Modified WRMRF; Modified WBMRIi Modified T/A and STAP*

(~ = as applicable)

• Description: WRPB retrieve WRMR from the WRS and send Class IXdata to Secondary Repairable Management Office (SRMO) forvalidation lAW Repair Issue Point (RIP). Additionally, WRPB sendClass Type 1 End Items for Class II and Class VII CBRN materielto CSP. This.is the last opportunity to make adjustments toRetail quantities.

• Input: Modified WRMRF; Modified WRMRI• Output: Validated WRMRF; Validated WRMRI

2-11


14. Load final computation requirements

Description: Once requirements are validated for each class ofsupply they are loaded in the WRS.by WRPB as the final activitywithin the WRS.

Important Note: Any subsequent changes to the retail requirementsbeyond the MEF Level Conference must be coordinated with WRPB.Input: Validated WRMRF; Validated WRMRI, Modified T/A and STAP*

Output: Loaded WRMRF; Loaded WRMRI; Loaded Initial Issue(* = as applicable)

15. ;Create & Sen&Retail sustainmentlata set

Description: WRPB create the Retail sustainment data set by pullthe Retail (WRMRF) component of the WRS database file (YCC dataset) from the system and provide via email to the MEFs/SMUs alongwith accompanying spreadsheet containing the same data set in aMicrosoft compatible format. The requirements become theresponsibility of the MEFs/SMUs to load in their retail inventorysystem and to procure.

Important Note: The Retail sustainment data set is also providedto the SRMO.

Input: WRMRF

Output: YCC data set; Spreadsheet

Figure 2.7: MEF Level Conference Process Step Descriptions


~i:j,:n:Cllqgll1Ptitationre~

• Description: Once requirements are validated for each class ofsupply they are loaded in the WRS·by WRPB as the final activitywithin the WRS.

• Important Note: Any subsequent changes to the retail requirementsbeyond the MEF Level Conference must be coordinated with WRPB.

• Input: Validated WRMRF; Validated WRMRI, Modified T/A and STAP*• Output: Loaded WRMRF; Loaded WRMRI; Loaded Initial Issue

(* = as applicable)

• Description: WRPB create the Retail sustainment data set by pullthe Retail (WRMRF) component of the WRS database file (YCC dataset) from the system and provide via email to the MEFs/SMUs alongwith accompanying spreadsheet containing the same data set in aMicrosoft compatible format. The requirements become theresponsibility of the MEFs/SMUs to load in their retail inventorysystem and to procure.

• Important Note: The Retail sustainment data set is also providedto the SRMO.

• Input: WRMRF• Output: YCC data set; Spreadsheet

Figure 2.7: MEF Level Conference - Process Step Descriptions

2-12

ination, Sourcing, Positioning

4. Retail Activities

Retail Activities describe the procedures conducted by the MEFs toprocure, hold and maintain Retail requirements after the completion ofthe MEF Level Annual Recomputation Conference.



Deputy Commandant Installations and Logistics (DC I&L) LogisticsPlans and Operations Branch (LPO)Marine Expeditionary Forces (MEFs)(Note: Respective Marine Forces Command (MMSFORCOM/MARFORPAC) provide oversight to their subordinate




Supported Activities Supply System (SASSY)

Global Command Supply System Marine Corps (GCSS-MC)*An applicable with GCSS-MC roil-out

a. Process Flow Map

,

MEF Level Recomputation ConferenceKey2Process [iADoctiment us W Ned

Step Phase 'tt SYstem

Retail Activities

0 W2

,Fo.pon

II_Lu . 16-1-

_

,

--"IF.-

Figure 2.8: Retail Activities Process Flow Map

Sou Posit

4. Retail Activities

Retail Activities describe the procedures conducted by the MEFs to.procure, hold and maintain Retail requirements after the completion ofthe MEF Level Annual Recomputation Conference.

Participants in this phase are (See MCG 4400.39 for overall roles andreSIJOl1sibili ties) :



• Marine Expeditionary Forces (MEFs){Note: Respec:til,'e Mdrine Forces Cotr'.mdnd (MARFORCOM!MARFORPACj pro'f,>~ide oversight to their subordinate

MEF during this phdse)


• War Reserve System (WRS)• Supported Activities Supply System (SASSY)

• Global Command Supply System - Marine Corps (GCSS-MC)*~. As applicable with GCSS-MC roll-out

a. Process Flow Map

Retail Activities

Figure 2.8: Retail Activities - Process Flow Map

2-13



16. Register Retail requirement

Description: MEFs load the YCC data set in SASSY or GCSS-MC*,registering the Retail requirement.

As applicable with GCSS-MC roll-out

Input: YCC data set; Spreadsheet

17. Send notification of status changes in Retail requirement

Description: MEFs notify WRPB of any changes in Retailrequirement outside the WRS via Naval Message.

Important Note: If MEFs DO NOT report any changes to WRMRF by 01Dec following the MEF Level Conference, then it is assumed thatthe MEFs will procure their full shortfall quantity.Output: WRMRF changes

18. Input changes to WRMRF

Description: WRPB input WRMRF changes, provided by the MEFs, intothe WRS.

Input: WRMRF changes

Output: Adjusted WRMRF

19. Create & send Retail Risk Analysis Report

Description: WRPB create the Retail Risk Assessment Report toinclude the retail requirement: Class, NSN, Quantity, andExtended Dollar Value. WRPB provide this report to LPO.Input: Adjusted WRMRF

Output: Retail Risk Analysis Report

26. Adjust WRMRI

Description: WRPB make adjustments to WRMRI, which utilizedthroughout the Wholesale activities.Input: Adjusted WRMRF

Output: Adjusted WRMRI

nGUU~rement:3


• Description: MEFs load the YCC data set in SASSY or GCSS-MC*,registering the Retail requirement .

• As applicable with GCSS-MC roll-out

• Input: YCC data set; Spreadsheet

requirem~nt

• Description: MEFs notify WRPB of any changes in Retailrequirement outside the WRS via Naval Message.

• Important Note: If MEFs DO NOT report any changes to WRMRF by 01Dec following the MEF Level Conference, then it is assumed thatthe MEFs will procure their full shortfall quantity.

• Output: WRMRF changes

• Description: WRPB input WRMRF changes, provided by the MEFs, intothe WRS.

• Input: WRMRF changes• Output: Adjusted WRMRF

• Description: WRPB create the Retail Risk Assessment Report toinclude the retail requirement: Class, NSN, Quantity, andExtended Dollar Value. WRPB provide this report to LPO.

• Input: Adjusted WRMRF• Output: Retail Risk Analysis Report

• Description: WRPB make adjustments to WRMRI, which utilizedthroughout the Wholesale activities.

• Input: Adjusted WRMRF• Output: Adjusted WRMRI

2-14

Determination, Sourcing, ning

21. 'Rrocure Retail requirement

Description: The MEFs procure WRMRF shortfall quantities to bringWRMSF up to the DOS quantity designated during the MEF LevelRecomputation Conference.

Input: MEF Funding

Output: Inventory

22. Hold inventory until reqUired

Description: MEFs stock and maintain WRMRF until assets aredesignated for use. MEFs can rotate assets as necessary if theyplan to replenish the following year.

Figure 2.9: Retail Activities Process Step Descriptions

5. Wholesale Activities

Wholesale Activities describe the procedures conducted by WRPB tocoordinate for procurement and storage of Wholesale requirements withMarine Corps and/or DoD IMMs.



Deputy Commandant Installations and Logistics (DC I&L) LogisticsPlans and Operations Branch (LPO)Deputy Commandant Combat Development & Integration (DC CD&I)

DC CD&I Combat Development Division (CDD)

DC CD&I MAGTF Integration Division (MID)DC CD&I Integration Division (ID)

Systems used.in this phase are (See Chapter 9 for SystemsDescriptions):

Stock Control System (SCS)War Reserve System (WRS)

Component Systems (See Figure 9.1 for complete listing ofcomponent systems)Total Force Structure Management System (TFSMS)

Supported Activities Supply System (SASSY)

Global Command Supply System Marine Corps (GCSS-MC)*As applicable with GCSS-MC roll-out

21.

nts Determination, Sourcing, Positioning

• Description: The MEFs procure WRMRF shortfall quantities to bringWRMSF up to the DOS quantity designated during the MEF LevelRecomputation Conference.

• Input: HEF Funding

• Output: Inventory

22. Hold required

• Description: HEFs stock and maintain WRMRF until assets aredesignated for use. HEFs can rotate assets as necessary if theyplan to replenish the following year.

Figure 2.9: Retail Activities - Process Step Descriptions

5. Wholesale Activities

Wholesale Activities describe the procedures conducted by WRPB tocoordinate for procurement and storage of Wholesale requirements withMarine Corps and/or DoD I!'1!'1s.




• Deputy Commandant Combat Development & Integration (DC CD&I)

• DC CD&I Combat Development Division (CDD)• DC CD&I MAGTF Integration Division (MID)• DC CD&I Integration Division (ID)

Systems used.in this phase are (See Chapter 9 for SystemsDescriptions) :

• Stock Control System (SCS)• War Reserve System (WRS)• Component Systems (See Figure 9.1 for complete listing of

component systems)• Total Force Structure Management System (TFSHS)

• Supported Activities Supply System (SASSY)• Global Command Supply System - Marine Corps (GCSS-MC)*

~ As dpplicdbl~ vich GCSS-MC roll-out

2-15


a. Process Flow Map

MEF Level Recomputation ConferenceKwro44

Previous Maxi F.*SystemPhase

> Wholesale Activities

M.J O.o WM '

,

Pravid Pew.

wi. .

: , ,

:

__

1

V

4

.

1.1

7 , '

0. ..]:

_.

t.!'

Figure 2.10: Wholesale Activities Process Flow Map


23. Source Wholesale data set

Description: WRPB update Wholesale Inventory Requirement toreflect assets already available to source shortfalls (i.e.,Maritime Prepositioning System (MPS) data) . This is the lastopportunity for WRPB to make adjustments to Wholesale quantity.Input: Adjusted WRMRI; MPS data

Output: Wholesale Inventory Requirements

24. Create Wholesale data set

Description: WRPB retrieve the Wholesale component of the fullWRMR database file from the WRS.Input: Wholesale Inventory Requirements, Initial IssueOutput: Wholesale data set (ZOA and DMA/DME transactions)

irements , Sourcin~l! Posi tL'jl'.L'F-1

a. Process Flow Map

Wholesale Activities

Figure 2.10: Wholesale Activities - Process Flow Map


• Description: WRPB update Wholesale Inventory Requirement toreflect assets already available to source shortfalls (i.e.,Maritime Prepositioning System (MPS) data). This is the lastopportunity for WRPB to make adjustments to Wholesale quantity.

• Input: Adjusted WRMRI; MPS data• Output: Wholesale Inventory Requirements

• Description: WRPB retrieve the Wholesale component of the fullWRMR datqbase file from the WRS.

• Input: Wholesale Inventory Requirements, Initial Issue• Output: Wholesale data set (ZOA and DMA/DME transactions)

2-16

umiDat¡ÓD, SOUrCigg, POSit¡OniDg

Register Wholesale requirements w/ IMMs

Description: WRPB register the Wholesale requirement in componentsystems (specific to selected ZMM) and the SCS. MCLC becomesresponsible for the procurement of the Class II secondary items,III (P), IV, and IX Wholesale Inventory Requirements andcoordinate with DC CD&I PMs for the procurement of WRMR for Typei End Items of Class II/CIass VII, deemed combat essential.

Input: Wholesale data set (ZOA and DMA/DME transactions)

Output: Registered Class II secondary items, III (P), Z\7, and IX

Wholesale Inventory Requirements; Registered Initial Issue

26. Provide Posture Report to LPO

Description: MCLC provide a Posture Report to LPO definingWholesale percent attainment, shortfalls, and associated dollarvalue WRPB is responsible to procure; and Initial Zssue.

Input: Registered Class II a*coudary items, III (P), IV, and IXWholesale Inventory Requirements; Wholesale InventoryRequirements of Type l End Items for Class II and Class VIIRegistered Initial Issue

27' Provide Type 1 End Items for Class II/ Class VII datato CD&I

Description: WRPB provide data to CC0 detailing the requirementquantities for each Table of Authorized Material Control Number(TAMCN) to be input into the TFSMS. CDD coordinates theinformation with the MID and the Integration Divisions (IDs) tofacilitate the input of WRMR quantities into TFSM3.Input: Wholesale Inventory Requirements of Type i End Items forClass II and Class VII (WBMB)Output: Registered Type l End Items for Class II and Class VII

Figure 2.11: Wholesale Activities - Process Step Descriptions

nat

• Description: WRPB register the Wholesale requirement in componentsystems (specific to selected IMM) and the SCS. MCLC becomesresponsible for the procurement of the Class II secondary items,III (P), IV, and IX Wholesale Inventory Requirements andcoordinate with DC CD&I PMs for the procurement of WPMR for Type1 End Items of Class II/Class VII, deemed combat essential.

• Input: Wholesale data set (ZOA and DMA/DME transactions)• Output: Registered Class II secondary items, III (P), IV, and IX

Wholesale Inventory Requirements; Registered Initial Issue

• Description: MCLC provide a Posture Report to LPO definingWholesale percent attainment, shortfalls, and associated dollarvalue WRPB is responsible to procure; and Initial Issue.

• Input: Registered Class II secondary. items, III (P), IV, and IXWholesale Inventory Requirements; Wholesale InventoryRequirements of Type 1 End Items for Class II and Class VIIRegistered Initial Issue

• Output: Posture Report

• Description: WRPB provide data to COO detailing the requirementquantitie::; for each Table of Authorized Material Control Number(TAMCN) to be input into the TFSMS. COO coordinates theinformation with the MID and the Integration Divisions (10::;) tofacilitate the input of WRMR quantitie::; into TFSMS.

• Input: Wholesale Inventory Requirements of Type 1 End Items forClas::; II and Class VII (WRMR)

• Output: Registered Type 1 End Items for Class II and Class VIIFigure 2.11: Wholesale Activities - Process Step Descriptions

2-17


6.MEF Level Prerequisite Data Checklist

Participants in this effort are (See MCO 4400.39 for overall roles andresponsibilities):




Review and update the Class III War Reserve System (WRS) Demand -

Based File

How to Complete:

Update should be a coordinated effort with MARFOR/MEFPlanners and Motor Transportation

Class III WRS Demand Based File must be updated andsubmitted to WRPB in the following format:

NSN NOMEN QTY

Date must becompleted by:

Provide updates to WRPB no later than 15 businessdays prior to MEF Level Annual RecomputationConference

Review and update the Class rv Constructionldateriel File

How to Complete:

'Update should be a coordinated effort betweenMARFOR/MEF Planners and Engineer Support Personnel

Class IV construction materiel file must be updatedand submitted to WRPB in the following format:

NSN NOMEN QTY



Validate items currently in the Combat Ready Storage ProgrAM(CURSP) and items administratively deadlined

How to Complete:

Update should be a coordinated effort with MARFOR/MEFPlanners, Supply Support and Maintenance Management

Update Item Designation Numbers (IDNs) and quantitiesfor special items needing repair parts that are notaccumulating usage reports and for itemsadministratively deadlined



s , sourcing, positioni

6. MEF Level Prerequisite Data Checklist

Participants in this effort are (See MCO 4400.39 for overall roles andresponsibilities) :

• Marine Forces (MARFORs)• Marine Expeditionary Forces (MEFs)• Marine Corps Logistics Command (MCLC) War Reserve Planning Branch

(WRPB)

Update should be a coordinated effort with MARFOR/MEFPlanners and Motor Transportation

How to Complete: Class III WRS Demand Based File must be updated andsubmitted to WRPB in the following format:

NSN NOMEN QTY



Update should be a coordinated effort betweenMARFOR/MEF Planners and Engineer Support Personnel

How to Complete: Class IV construction materiel file must be updatedand submitted to WRPB in the following format:

NSN NOMEN QTY



oqram

How to Complete:


Update should be a coordinated effort with MARFOR/MEFPlanners, Supply Support and Maintenance Management

Update Item Designation Numbers (IDNs) and quantitiesfor special items needing repair parts that are notaccumulating usage reports and for itemsadministratively deadlined


2-18

J.,:cing, Positioning'

Determine Class I & IV Landing Force Operational ReserveMaterial (LFORM) quantities to be used during the conference

How to Complete:

Update should be a coordinated effort with MARFOR/MEFPlanners

Determine and submit available Class I ..& IV LFORMquantities to WRPB. Class I MRE quantities per boxshould be specified



,

Provide the names of individuals attending the conference toWRPB

How to Complete:Provide Attendee Contact Information via email toMCLC


Return Form to WRPB no later than 15 business daysprior to MEF Level Annual Recomputation Conference

Ensure designated user representatives have verified currentaccess to the WRS and INFOPAC

How to Complete: Contact WRPB to request access


Appropriate access must be requested/ obtained fornew users a minimum of 15 business days prior to MEFLevel Annual Recomputation Conference

Determine force held sustaining supply period (10-60 days)

How to Complete:Personnel provide supply period days to be force held.(WRMRF) on behalf of their respective MEF Commander.Proper coordination is required.


Provide supply period days to be force held (WRMRF)to WRPB no later than 15 business days Prior to MEFLevel Annual Recomputation Conference

Gather Retail filesI

How to Complete:Gather any other Retail files to support MEF planningsuch as Equipment Density Lists (EDLs) andConsolidated Allowance Lists (CALs)

Date must becompleted by

Bring to MEE Level Annual Recomputation Conference

Figure 2.12: MEF Level Data Gathering Checklist

2-19

! SC)\J F'c'::;.Lt 1

Update should be a coordinated effort with MARFOR!MEFPlanners

How to Complete:


Determine and submit available Class 1& IV LFORMquantities to WRPB. Class I MRE quantities per boxshould be specified


ProWRPB

How to Complete:


Provide Attendee Contact Information via email toMCLC

Return Form to WRPB no later than 15 business daysprior to MEF Level Annual Recomputation Conference

How to Complete:


Contact WRPB to request access

Appropriate access must be requested! obtained fornew users a minimum of 15 business days prior to MEFLevel Annual Recomputation Conference

How to Complete:


Personnel provide supply period days to be force held(WRMRF) on behalf of their respective MEF Commander.Proper coordination is required.

Provide supply period days to be force held (WRMRF)to WRPB no later than 15 business days prior to MEFLevel Annual Recomputation Conference

Gather any other Retail files to support MEF planningHow to Complete: such as Equipment Density Lists (EDLs) and

Consolidated Allowance Lists (CALs)

Date mustcompleted

beby:' Bring to MEF Level Annual Recomputation Conference

Figure 2.12: MEF Level Data Gathering Checklist

2-19

Requirements Det rmination, Sourcing, Positioning

EXAMPLE GUIDANCE MESSAGE FOR WAR RESERVE MATERIELREQUIREMENTS (CRMR) ANNUAL RECOMPUTATION CONFERENCE

NOTE: Content in brackets E ] will be populated by LPO when message isreleased.

UNCLASFM CMC WASHINGTON DC LP LPOTO COMMARCORLOGCOM ALBANY GA

COMMARFORRESCOMMARFORRES (G- 3/4)COMMARFORPACCOMMARFORPAC (G-3/4)COMMARFORCOMCOMMARFORCOM (G-3/4/5/7)CC CG III MEFCG III MEF (G-3/4)CG I MEFCG I MEF (G-3/4)CMC WASHINGTON DC P&RCG II MEFCG II MEF (G-4)COMMARCORSYSCOM ALBANY GACG MCCDC QUANTICO VACMC WASHINGTON DC PP&OCMC WASHINGTON DC PLCMC WASHINGTON DC POCMC WASHINGTON DC LCMC WASHINGTON DC L LPCCMC WASHINGTON DC PLNCMC WASHINGTON DC POECMC WASHINGTON DC POCCG 1ST MLGCG 2ND MLGCG 3RD MLGCOMUSMARCENTCOMUSMARSOCLOGMODTM WESTPACLOGMODTM WESTFSMAO EAST

MSGID/GENADMIN/CMC WASHINGTON DC LP0//SUBJ/GUIDANCE FOR FYXX WAR RESERVE MATERIEL REQUIREMENTS (WRMR) AND ANNUALRECOMPUTATION CONFERENCE//REF/A/DOC/MCO 4400.39/-//AMPN/REF A IS THE MARINE CORPS WAR RESERVE MATERIEL POLICY.//POC/[NAME]/[RANKMOFFICE]/-/TEL:[COMM]/ TEL:[DSN]/EMAIL: //GENTEXT/REMARKS/1. THIS IS A COORDINATED HQMC AND COMMARCORLOGCOM MSG.2. THE FYXX ANNUAL WAR RESERVE MATERIEL REQUIREMENTS (WRMR) RECOMPUTATIONCONFERENCE WILL BE HOSTED BY MCLC XX-XX OCT FYXX, AT MCLC, ALBANY GA.REPRESENTATIVES FROM [LIST OF OFFICE SYMBOLS] ARE REQUESTEDATTENDEES.3. PURPOSE.3.A. TO ESTABLISH MARINE CORPS WRMR FOR PROGRAM OBJECTIVE MEMORANDUM (POM)XX.3.B. TO PROVIDE MEF WAR RESERVE SYSTEM (WRS) USERS A CENTRALIZED SITE FORCONCURRENT WRMR RECOMPUTATION REQUIREMENTS TO INCLUDE COMPLETION OFREQUIREMENTS DETERMINATION, REVIEW/MODIFY MEF-LEVEL WITHDRAWAL PLANS, AND

7-20

rements Determination, Sourcing, Positioning

7. EXAMPLE GUIDANCE MESSAGE FOR WAR RESERVE MATERIELREQUIREMENTS (WRMR) ANNUAL RECOMPUTATION CONFERENCE

NOTE: Content in brackets [ 1 will be populated by LPG when message isreleased.

UNCLASFM CMC WASHINGTON DC LP LPOTO COMMARCORLOGCOM ALBANY GA

COMMARFORRESCOMMARFORRES (G- 3/4)COMMARFORPACCOMMARFORPAC (G-3/4)COMMARFORCOMCOMMARFORCOM (G-3/4/5/7)CC CG III MEFCG III MEF (G-3/4)CG I MEFCG I MEF (G-3/4)CMC WASHINGTON DC P&RCG II MEFCG II MEF (G-4)COMMARCORSYSCOM ALBANY GACG MCecC QUANTICO VACMC WASHINGTON DC PP&OCMC WASHINGTON DC PLCMC WASHINGTON DC POCMC WASHINGTON DC LCMC WASHINGTON DC L LPCCMC WASHINGTON DC PLNCMC WASHINGTON DC POECMC WASHINGTON DC POeCG 1ST MLGCG 2ND MLGCG 3RD MLGCOMUSMARCENTCOMUSMARSOCLOGMODTM WESTPACLOGMODTM WESTFSMAO EAST

MSGID/GENADMIN/CMC WASHINGTON DC LPO//SUBJ/GUIDANCE FOR FYXX WAR RESERVE MATERIEL REQUIREMENTS (WRMR) AND ANNUALRECOMPUTATION CONFERENCE//REF/A/DOC/MCO 4400.39/-//AMPN/REF A IS THE MARINE CORPS WAR RESERVE MATERIEL POLICY. / /POC/[NAME)/[RANK)/[OFFICE)/-/TEL: [COMM)/ TEL: [DSN)/EMAIL: //GENTEXT/REMARKS/1. THIS IS A COORDINATED HQMC AND COMMARCORLOGCOM MSG.2. THE FYXX ANNUAL WAR RESERVE MATERIEL REQUIREMENTS (WRMR) RECOMPUTATIONCONFERENCE WILL BE HOSTED BY MCLC xx-xx OCT FYXX, AT MCLC, ALBANY GA.REPRESENTATIVES FROM [LIST OF OFFICE SYMBOLS) ARE REQUESTEDATTENDEES.3. PURPOSE.3.A. TO ESTABLISH MARINE CORPS WRMR FOR PROGRAM OBJECTIVE MEMORANDUM (POM)xx.3.B. TO PROVIDE MEF WAR RESERVE SYSTEM (WRS) USERS A CENTRALIZED SITE FORCONCURRENT WRMR RECOMPUTATION REQUIREMENTS TO INCLUDE COMPLETION OFREQUIREMENTS DETERMINATION, REVIEW/MODIFY MEF-LEVEL WITHDRAWAL PLANS, AND

2-20

acnts Determination, Sourcing, Positioning

SASSY/GCSS-MC INTERFACE PROCESSES. INTENT IS TO ACHIEVE THE FOLLOWINGRESULTS: WHOLESALE ACTIONS, TO INCLUDE REVIEW AND REGISTRATION OF IN-STORES REQUIREMENTS, REGISTRATION OF REQUIREMENTS WITH DLA AND OTHER DODINTEGRATED MATERIEL MANAGERS, AND GENERATION OF POSTURE REPORTS TO BECOMPLETED BY THE WAR PLANNING BRANCH WITH AN ESTIMATED COMPLETION DATE OFDATE]

4. BACKGROUND.4.A. PER DODI 3110.06, COMPONENTS SHALL ACQUIRE AND MAINTAIN IN PEACETIMEWAR MATERIEL INVENTORIES SUFFICIENT TO ATTAIN AND SUSTAIN OPERATIONALOBJECTIVES AS PRESCRIBED IN SECDEF DEFENSE PLANNING AND PROGRAMMINGGUIDANCE (DPPG) AND JOINT STRATEGIC CAPABILITIES PLAN SCENARIOS FORCOMMITTED FORCES. TO MEET THIS REQUIREMENT, THE MARINE CORPS CONDUCTS ANANNUAL RECOMPUTATION OF ITS WARTIME REQUIRMENT BY COMPLETING THE MEF-LEVELRECOMPUTATION PROCESS THAT VALIDATES WHOLESALE ACTIONS, SOURCESREQUIREMENTS, REGISTERS IN-STORES REQUIREMENTS WITH DLA AND OTHER DOD ITEMMATERIEL MANAGERS (IMM), GENERATES A WAR RESERVE MATERIEL POSTURE REPORTAND REGISTERS WRMR FOR POM INCLUSION.5. ACTION.5.A. THE FOLLOWING PROCEDURAL STEPS ARE REQUIRED BY EACH MARFOR PRIOR TOTHE RECOMPUTATION CONFERENCE.5.A.1. ENSURE DESIGNATED USER REPRESENTATIVES RAVE VERIFIED CURRENT ACCESSTO THE WAR RESERVE SYSTEM (WRS) AND INFOPAC. APPROPRIATE ACCESS MUST BEREQUESTED/OBTAINED FOR NEW USERS NLT [DATE] .POINTS OF CONTACT FOR WRSACCESS ARE: [POC NAME, TEL, EMAIL]5.A.2. ENSURE DESIGNATED USER REPRESENTATIVES HAVE COMPLETED WAR RESERVESYSTEM TRAINING HAVE SUBMITTED CERTIFICATE OF COMPLETION PRIOR TOCONFERENCE INITATION.5.A.3. ENSURE DESIGNATED USER REPRESENTATIVES HAVE GATHERED REQUIREDINFORMATION IAW MEF LEVEL PREREQUISITE DATA CHECKLIST, NAVMC 4000.1,CHAPTER 2.5.A.4. PROVIDE THE NAMES OF INDIVIDUALS ATTENDING THE CONFERENCE TO THISHQS NLT [DATE].5.A.5. THUMB DRIVES ARE STRICTLY PROHIBITED. MEF REPRESENTATIVES SHOULDULTILIZE EXTERNAL HARD DRIVES, CDS OR OTHER ACCEPTABLE MARINE CORPSSTORAGE DEVICES.6. THE FOLLOWING PARAMETERS SHALL BE USED FOR WRMR/RECOMPUTATION PROCESS:6.A. COMBAT ACTIVE REPLACEMENT FACTORS (CARFS):6.B. [NAVY ADDITIVE]6.C. PERSONNEL STRENGTH FOR MARINE CORPS REQUIREMENTS:6.C.1 MIC (P)6.C.2 MIC (Z)6.D. HEALTH & COMFORT PACKAGE (HCP) PERCENTAGE:6.D.1 MALE6.D.2 FEMALE7. COORDINATED INSTRUCTIONS.7.A. [CONFERENCE LOCATION]7.B. [AGENDA]7.C. TAD FUNDING IS A UNIT RESPONSIBILITY.7.D. ATTENDANCE AND CLEARANCE VERIFICATION REQUIRED. [PROCEDURES FORSENDING CLEARANCE IDENTIFICATION/VERIFICATION] . INCLUDE THE FOLLOWINGINFORMATION: NAME, GRADE/RANK, SSN, CLEARANCE WITH EFFECTIVE DATE, UNIT,OFFICE SYMBOL, DUTY PHONE.7.E. [MARINE UNIFORM]. [CONFERENCE ATTIRE]7.F. [HOTEL INFORMATION]7.G. CONFERENCE AGENDA WILL BE PROVIDED UNDER SEPCOR.BT

2-21

~ ~irements Determination, sourcing, positioning

SASSY!GCSS-MC INTERFACE PROCESSES. INTENT IS TO ACHIEVE THE FOLLOWINGRESULTS: WHOLESALE ACTIONS, TO INCLUDE REVIEW AND REGISTRATION OF INSTORES REQUIREMENTS, REGISTRATION OF REQUIREMENTS WITH DLA AND OTHER DODINTEGRATED MATERIEL MANAGERS, AND GENERATION OF POSTURE REPORTS TO BECOMPLETED BY THE WAR PLANNING BRANCH WITH AN ESTIMATED COMPLETION DATE OF[DATE] .4. BACKGROUND.4.A. PER DODI 3110.06, COMPONENTS SHALL ACQUIRE AND MAINTAIN IN PEACETIMEWAR MATERIEL INVENTORIES SUFFICIENT TO ATTAIN AND SUSTAIN OPERATIONALOBJECTIVES AS PRESCRIBED IN SECDEF DEFENSE PLANNING AND PROGRAMMINGGUIDANCE (DPPG) AND JOINT STRATEGIC CAPABILITIES PLAN SCENARIOS FORCOMMITTED FORCES. TO MEET THIS REQUIREMENT, THE MARINE CORPS CONDUCTS ANANNUAL RECOMPUTATION OF ITS WARTIME REQUIRMENT BY COMPLETING THE MEF-LEVELRECOMPUTATION PROCESS THAT VALIDATES WHOLESALE ACTIONS, SOURCESREQUIREMENTS, REGISTERS IN-STORES REQUIREMENTS WITH DLA AND OTHER DOD ITEMMATERIEL MANAGERS (IMM) , GENERATES A WAR RESERVE MATERIEL POSTURE REPORTAND REGISTERS WRMR FOR POM INCLUSION.S. ACTION.S.A. THE FOLLOWING PROCEDURAL STEPS ARE REQUIRED BY EACH MARFOR PRIOR TOTHE RECOMPUTATION CONFERENCE.S.A.1. ENSURE DESIGNATED USER REPRESENTATIVES HAVE VERIFIED CURRENT ACCESSTO THE WAR RESERVE SYSTEM (WRS) AND INFOPAC. APPROPRIATE ACCESS MUST BEREQUESTED/OBTAINED FOR NEW USERS NLT [DATE] . POINTS OF CONTACT FOR WRSACCESS ARE: [POC NAME, TEL, EMAIL]S.A.2. ENSURE DESIGNATED USER REPRESENTATIVES HAVE COMPLETED WAR RESERVESYSTEM TRAINING HAVE SUBMITTED CERTIFICATE OF COMPLETION PRIOR TOCONFERENCE INITATION.S.A.3. ENSURE DESIGNATED USER REPRESENTATIVES HAVE GATHERED REQUIREDINFORMATION lAW MEF LEVEL PREREQUISITE DATA CHECKLIST, NAVMC 4000.1,CHAPTER 2.S.A.4. PROVIDE THE NAMES OF INDIVIDUALS ATTENDING THE CONFERENCE TO THISHQS NLT [DATE].S.A.S. THUMB DRIVES ARE STRICTLY PROHIBITED. MEF REPRESENTATIVES SHOULDULTILIZE EXTERNAL HARD DRIVES, CDS OR OTHER ACCEPTABLE MARINE CORPSSTORAGE DEVICES.6. THE FOLLOWING PARAMETERS SHALL BE USED FOR WRMR/RECOMPUTATION PROCESS:6.A. COMBAT ACTIVE REPLACEMENT FACTORS (CARFS):6.B. [NAVY ADDITIVE]6.C. PERSONNEL STRENGTH FOR MARINE CORPS REQUIREMENTS:6.C.1 MIC (P)6.C.2 MIC (Z)6.0. HEALTH & COMFORT PACKAGE (HCP) PERCENTAGE:6.0.1 MALE6.0.2 FEMALE7. COORDINATED INSTRUCTIONS.7.A. [CONFERENCE LOCATION]7 . B. [AGENDA]7.C. TAD FUNDING IS A UNIT RESPONSIBILITY.7.0. ATTENDANCE AND CLEARANCE VERIFICATION REQUIRED. [PROCEDURES FORSENDING CLEARANCE IDENTIFICATION/VE.RIFICATION]. INCLUDE THE FOLLOWINGINFORMATION: NAME, GRADE/RANK, SSN, CLEARANCE WITH EFFECTIVE DATE, UNIT,OFFICE SYMBOL, DUTY PHONE.7.E. [MARINE UNIFORM]. [CONFERENCE ATTIRE]7.F. [HOTEL INFORMATION]7 . G. CONFE.RENCE AGENDA WILL BE PROVIDED UNDER SEPCOR.

BT

2-21


C. Plan Level Conference

1. Description

MAGTFs deploy combat ready and have enough inherent sustainability tobe basically self-sufficient for a preplanned period. Prior planningis required to ensure ground supplieS and equipment are identified torapidly withdraw stocks held by the force (WRMRF), by the Marine CorpsIMMs (WRMRI), or by DoD IMMs. This planning is accomplished at thePlan Level Conference, which occurs annually or as required by theMarine Corps.

During the Plan Level Conference, MARFORs, MEFs and WRPB coordinate totailor the WRMR to OPLAN/CONPLAN task organization, phasing, andtiming in the creation of War Reserve Withdrawal Plans (WRWPs) forClass I, II, III(P), IV, VI, VII and IX. Once shortfalls have beenidentified and sourcing actions are completed, based on the WholesaleDollar Value Report provided by MCLC, the associated operationalcapability and funding risks are assessed by DC P&R (PA&E) , DC PP&O(PO/PL), and DC I&L (LPO) to determine the associated impacts on theEnterprise. This is accomplished during the annual WRWP RiskAssessment Working Group. The WRWP Risk Assessment is utilized byPA&E in the next Fiscal Year (FY) POM baseline reviews. Additionally,PO/PL incorporates the WRWP Risk Assessment into the comprehensivejoint risk assessment of MARFORs' ability to support OPLANs/CONPLANsused to inform Congress.

The desired end state is a series of sourced sustainment ULNs in theOPLAN/CONPLAN TPFDD that represent Class I, II, III(P), IV, VI, VIIand IX sustainment necessary to support each MAGTF. Each individualgrouping of sustainment has a unique number associated with a WRWP andthe OPLAN/CONPLAN it supports.

There are three phases that make up the Plan Level Process: Pre-Conference Activities, Plan Level Conference and Post-Conference.

1. Pre-

ConferenceActivitiee

2. Plan LevelConference

3. Post-Conference

Figure 2.13: Plan Level Conference Phases

Requirements Determination, Sourcing, positioning

C. Plan Level Conference

1. Description

MAGTFs deploy combat ready and have enough inherent sustainability tobe basically self-sufficient for a preplanned period. Prior planningis required to ensure ground supplies and equipment are identified torapidly withdraw stocks held by the force (WRMRF), by the Marine CorpsIMMs (WRMRI), or by DoD IMMs. This planning is accomplished at thePlan Level Conference, which occurs annually or as required by theMarine Corps.

During the Plan Level Conference, MARFORs, MEFs and WRPB coordinate totailor the WRMR to OPLAN/CONPLAN task organization, phasing, andtiming in the creation of War Reserve Withdrawal Plans (WRWPs) forClass I, II, III(P), IV, VI, VII and IX. Once shortfalls have beenidentified and sourcing actions are completed, based on the WholesaleDollar Value Report provided by MCLC, the associated operationalcapability and funding risks are assessed by DC P&R (PA&E), DC PP&O(PO/PL), and DC I&L (LPO) to determine the associated impacts on theEnterprise. This is accomplished during the annual WRWP RiskAssessment Working Group. The WRWP Risk Assessment is utilized byPA&E in the next Fiscal Year (FY) POM baseline reviews. Additionally,PO/PL incorporates the WRWP Risk Assessment into the comprehensivejoint risk assessment of MARFORs' ability to support OPLANs/CONPLANsused to inform Congress.

The desired end state is a series of sourced sustainment ULNs in theOPLAN/CONPLAN TPFDD that represent Class I, II, III(P), IV, VI, VIIand IX sustainment necessary to support each MAGTF. Each individualgrouping of sustainment has a unique number associated with a WRWP andthe OPLAN/CONPLAN it supports.

There are three phases that make up the Plan Level Process: PreConference Activities, Plan Level Conference and Post-Conference.

Figure 2.13: Plan Level Conference Phases

2-22

liements Determination, Sourcinq, Positioning


The Pre-Recomputation Activities describe the procedures conducted bythe various organizations that participate in the Plan LeVelConference. The actions are required to determine the time andlocation for the Conference as well as to support data gatheringrequired to build the WRWPs.






a. Process Flow Map

Plan Level Pre-ConferenceKey:

[..3

, .

It tr, -Pre-Conference Activities

°15 -,--

(..) .-J0

S.T,Ist.Z',i

1 i

q,

o a-J a.o Ce

CC0U-ir<2

Iii 46..111

U..L11

2m.P. -

OZ.% 4

- __--....1MMMImmi.-___ .7%,_

System _.......4,41,44

, .

Figure 2.14: Pre-Conference Activities Process Flow Map

2-23

uire~0nt3 Determination, Sourcing, positioning


The Pre-Recomputation Activities describe the procedures conducted bythe various organizations that participate in the Plan LevelConference. The actions are required to determine the time andlocation for the Conference as well as to support data gatheringrequired to build the WRWPs.

Participants in this phase are (See Mea 4400.39 for overall roles andresponsibilities) :



• Marine Forces (MARFORs)• Marine Expeditionary Forces (MEFs)

a. Process Flow Map

Plan Level

UiD...J Q.

UO::~~

a:::oLLa:::«~

LLW~

Figure 2.14: Pre-Conference Activities - Process Flow Map

2-23

Requiremen s Determination, Sourci g, Positioning


--,InItiate coordination for Plan Lev41 Conference1.

Description: LPO initiate coordination prior to estimated PlanLevel Conference message release. During this coordination, LPOcoordinate with PP&O to gather current Programming Scenarios forincorporation into the Plan Level Guidance Message.

Input: POC information for Stakeholders


;Coorainate fOr schedule of PlänlIfvel Conference

Description: WRPB coordinate with LPO for scheduling of PlanLevel Conference (taking into account upcoming conferences,exercises, etc. that may present conflicts for participants).WRPB also provide LPO prerequisites for conference participantsand coordinating instructions.

Input: Email/phone call

Output: Prerequisites for conference; Coordinating instructions

3. Publish Plan Lexi.el guidance to simporting MÁRFORs

Description: LPO release the Guidance for FYXX War ReserveWithdrawal Plan (WRWP) Conference via Naval Message prior toscheduled conference. Programming Scenarios and Parameter dataare contained in the Naval Message to support the development ofplans. Parameter data included in the message are: Temperaturefactors, Apply Maritime Prepositioning System (MPS), EnemyPrisoner of War (EPW) factors, Maximum sustaining supply period,Sustainment intensity rates, Feed plan, Personnel to be fed, andHealth & Comfort Package (HCP) Percentage. The guidance messagewill also include a list of prerequisites for the conference andall coordinating instructions. Participants confirm attendance atthis point by filling out and returning to WRPB the ConferenceAttendee Contact Information form.Input: Prerequisites for conference participants; CoordinatinginstructionsOutput: Naval MessageDocument: Guidance for FYXX War Reserve Withdrawal Plan (WRWP)and Development Conference; Conference Attendee ContactInformation template



oriference

• Description: LPO initiate coordination prior to estimated PlanLevel Conference message release. During this coordination, LPOcoordinate with PP&O to gather current Programming Scenarios forincorporation into the Plan Level Guidance Message.

• Input: POC information for Stakeholders• Output: Email/phone call

ce

• Description: WRPB coordinate with LPO for scheduling of PlanLevel Conference (taking into account upcoming conferences,exercises, etc. that may present conflicts for participants) .WRPB also provide LPO prerequisites for conference participantsand coordinating instructions.

• Input: Email/phone call• Output: Prerequisites for conference; Coordinating instructions

fig HARPORs

• Description: LPO release the Guidance for FYXX War ReserveWithdrawal Plan (WRWP) Conference via Naval Message prior toscheduled conference. Programming Scenarios and Parameter dataare contained in the Naval Message to support the development ofplans. Parameter data included in the message are: Temperaturefactors, Apply Maritime Prepositioning System (MPS), EnemyPrisoner of War (EPW) factors, Maximum sustaining supply period,Sustainment intensity rates, Feed plan, Personnel to be fed, andHealth & Comfort Package (HCP) Percentage. The guidance messagewill also include a list of prerequisites for the conference andall coordinating instructions. Participants confirm attendance atthis point by filling out and returning to WRPB the ConferenceAttendee Contact Information form.

• Input: Prerequisites for conference participants; Coordinatinginstructions

• Output: Naval Message• Document: Guidance for FYXX War Reserve Withdrawal Plan (WRWP)

and Development Conference; Conference Attendee ContactInformation template

2-24

.e 10IDa LjDD, SVuICiog, PDsitiOniDa

m".

yrask MEF to complete WRS training and provide guidance

Description: MARFORs task MEF participants in the êlao LevelConference to complete the training package found in NAVMC 4000.1and provide guidance accordingly.

Input: NAVMC 4000,1 - Chapter 7


Document: NAVMC 4000.I - Chapter 7, Certificate of trainingcompletioo

5. Complete WRS training

Description: MEFs ensure all attendees conduct the War ReserveSystem (WRS) Training: Plan Level Users Guide and submitcertificate of training completion to WRPB prior to eventparticipation.Input: Guidance for FYXX War Reserve Withdrawal Plan (WRWP)Conference; NAVMC 4000.1-Cbapter 7Output: Certificate of training completion submission


Gather data to support Plan Level

Description: MEFa gather required data ZAW LPO's guidance messageand aubmit to WRPB ZAW the timeline designated in the Plan LevelData Gathering Checklist.Input: Guidance for FYXX War Reserve Withdrawal Plan (WRWP)Coofereuco/' NAVMC 4080.1-Cbaptez 7

Output: MIC data; Commodity code data; TE/T0 data; Reserve data;RBE readiness factorDocument:NAVMC 4000.1 - Chapter 2, Plan Level DataGatberiogChecklist

Figure 2.15: Pre-Conference Activities Process Step Descriptions

IJe t.e lon, p():sit

• Description: MARFORs task MEF participants in the Plan LevelConference to complete the training package found in NAVMC 4000.1and provide guidance accordingly.

• Input: NAVMC 4000.1 - Chapter 7• Output: Email/phone call• Document: NAVMC 4000.1 - Chapter 7, Certificate of training

completion

• Description: MEFs ensure all attendees conduct the War ReserveSystem (WRS) Training: Plan Level Users Guide and submitcertificate of training completion to WRPB prior to eventparticipation.

• Input: Guidance for FYXX War Reserve Withdrawal Plan (WRWP)Conference; NAVMC 4000.1-Chapter 7

• Output: Certificate of training completion submission• Document: NAVMC 4000.1 - Chapter 7, Certificate of training

completion

• Description: MEFs gather required data lAW LPO's guidance messageand submit to WRPB lAW the timeline designated in the Plan LevelData Gathering Checklist.

• Input: Guidance for FYXX War Reserve Withdrawal Plan (WRWP)Conference; NAVMC 4000.1-Chapter 7

• Output: MlC data; Commodity code data; TE/TO data; Reserve data;RBE readiness factor

• Document: NAVMC 4000.1 - Chapter 2, Plan Level Data GatheringChecklist

Figure 2.15: Pre-Conference Activities - Process Step Descriptions

2-25

ements Determination, sourcing, Positioning

3 . Plan Level Conference

The Plan Level Conference Activities describe the procedures conductedduring the actual Conference. The Plan Level Conference occursannually or as needed, depending on the needs of the Marine Corps, butall steps depicted are required to be completed prior to theconference conclusion.




Marine Expeditionary Forces (MEFs)Systems used in this phase are (See Chapter 9 for SystemsDescriptions):


Stock Control System (SCS)

a. Process Flow Map

.ii ,

Plan Level ConferenceKey:

ar:7 ,ii Phase, System

Plan Level Conference. a ._

..:

CL0U.;C< .

t,o,

-

- .. [

-,

.... . .

....-

.

,

,

1

,..ii,..-i

Systeml A

T 41.114W'

Figure 2.16: Plan Level Conference Process Flow Map

rements on, Sourcing, Posit

3. Plan Level Conference

The Plan Level Conference Activities describe the procedures conductedduring the actual Conference. The Plan Level Conference occursannually or as needed, depending on the needs of the Marine Corps, butall steps depicted are required to be completed prior to theconference conclusion.





• War Reserve System (WRS)• Stock Control System (S\S)

a. Process Flow Map

0::ou.0::

~

u.w:e

Figure 2.16: Plan Level Conference - Process Flow Map

2-26

eme _s Determination, Sourcincl, Positioning


7. Establish Bae EórListpe'r OPLiN/004kkinTi

Description: MARFORs establish Base Force List per theOPLAN/CONPLAN in the WRS to initiate the tailoring of Enterpriserequirements to specific plans.

Input: OPLAN/CONPLAN Base Force List

Output: Unit Identification Code (UIC); Unit Name; Number ofpersonnel; Earliest Arrival Date (EAD); Latest Arrival Date(LAD); Owning MEF

8. Provide parameter data

Description: MEF provide WRPB with parameter data, which isloaded into the WRS.

Input: Guidance Message

Output: Temperature Factors; Maritime Prepositioning System(MPS); Enemy Prisoner of War (EPW) Factors; Maximum SustainingSupply Period; Sustainment Intensity Rates; Feed Plan; Personnelto be Fed; Health & Comfort Package Percentage

9. Review and update perametérldata'fór-eAchc.r. egui440#1*1

Description: MEFs refine parameter data entered into the WRS byWRPB in support of specific missions and contingency plans.Input: Temperature Factors; Maritime Prepositioning 'System (MPS);Enemy Prisoner of War (EPW) Factors; Maximum Sustaining SupplyPeriod; Sustainment Intensity Rates; Feed Plan; Personnel to beFed; HCP Percentage

10. InpUtaddiional pe,rameter data

Description: MARFOR/MEF enter additional data into the WRS tocomplete preparation for Plan Level requirements determination.Input: MIC Data Entry; Commodity Code Data Entry; TE/TO DataEntry; Reserve Unit Data Entry; RBE Readiness FactorOutput: Parameter data set

11.tkje

Execute comPutatiorkr,

Description: WRPB run the WRS with all required data inputs togenerate the WRMRF/WRMRI, modified from Enterprise requirements,specific to each OPLAN/CONPLAN.Input: Parameter data set

Output: Modified WRMRF; Modified WRMRI; Modified Initial Issue

2-27

irements Determination, Sourcing, Positioning


7 . EstablJ;i

• Description: MARFORs establish Base Force List per theOPLAN/CONPLAN in the WRS to initiate the tailoring of Enterpriserequirements to specific plans.

• Input: OPLAN/CONPLAN Base Force List

• Output: Unit Identification Code (UIC); Unit Name; Number ofpersonnel; Earliest Arrival Date (EAD); Latest Arrival Date(LAD); Owning MEF

8 . Proviq~,l, ,t

• Description: MEF provide WRPB with parameter data, which isloaded into the WRS.

• Input: Guidance Message

• Output: Temperature Factors; Maritime Prepositioning System(MPS); Enemy Prisoner of War (EPW) Factors; Maximum SustainingSupply Period; Sustainment Intensity Rates; Feed Plan; Personnelto be Fed; Health & Comfort Package Percentage

9.

• Description: MEFs refine parameter data entered into the WRS byWRPB in support of specific missions and contingency plans.

• Input: Temperature Factors; Maritime Prepositioning 'System (MPS);Enemy Prisoner of War (EPW) Factors; Maximum Sustaining SupplyPeriod; Sustainment Intensity Rates; Feed Plan; Personnel to beFed; HCP Percentage

10. InpuE~~~

• Description: MARFOR/MEF enter additional data into the WRS tocomplete preparation for Plan Level requirements determination.

• Input: MIC Data Entry; Commodity Code Data Entry; TE/TO DataEntry; Reserve Unit Data Entry; RBE Readiness Factor

• Output: Parameter data set

11 . Execute] ,

• Description: WRPB run the WRS with all required data inputs togenerate the WRMRF/WRMRI, modified from Enterprise requirements,specific to each OPLAN/CONPLAN.

• Input: Parameter data set• Output: Modified WRMRF; Modified WRMRI; Modified Initial Issue

2-27

Requirements Determination, Sourcing, Positioninq

12. 4,ReviewItodify computation outguts

Description: MEFs have opportunity to modify the sustainingsupply period during the review/modify portion of plandevelopment.

Input: Updates to sustaining supply period

Output: Tailored WRMR; Tailored Initial Issue

13. Eic46,iiiteilaoad,to plan file

Description: WRPB load tailored requirements and initial issuebased off the OPLAN/CONPLAN Base Force Lists into the WRS planfile.

Input: Tailored WRMR; Tailored Initial Issue

Output: Validated WRWP plan file

4E444 thiWP,scenarios

Description: MEFs assign a name for each WRWP scenario andprovide precedence based on period of support. MEFs run theprocess withi,n the WRS to build the scenario. The process ofbuilding a scenario assigns Retail and Wholesale requirementsdepicting the expected flow of equipment for each specificsituation. It is important to note that the scenarios may cover agroup of plans in support of OPLANs/CONPLANs.Input: Validated WRMR plan file

Output: WRWP

15.,A

eqsuppqit tests on WROO nariostit

Description: MEFs conduct support tests, within the WRS, todetermine materiel available to support each scenario andremaining shortfalls. This provides a snapshot of availableassets to support a specific WRWP scenario. The process testsagainst Marine Corps internal stocks only.Important Note: This test can be conducted within the WRS at anytime to provide a current status of available stocks as needed toupdate Force Commanders.Input: WRWPOutput: Marine Corps IMM Shortfalls

Figure 2.17: Plan Level Conference Process Step Descriptions

Requirements Determination, sourcing, positioning

• Description: MEFs have opportunity to modify the sustainingsupply period during the review/modify portion of plandevelopment.

• Input: Updates to sustaining supply period• Output: Tailored WRMRi Tailored Initial Issue

• Description: WRPB load tailored requirements and initial issuebased off the OPLAN/CONPLAN Base Force Lists into the WRS planfile.

• Input: Tailored WRMRi Tailored Initial Issue• Output: Validated WRWP plan file

• Description: MEFs assign a name for each WRWP scenario andprovide precedence based on period of support. MEFs run theprocess within the WRS to build the scenario. The process ofbuilding a scenario assigns Retail and Wholesale requirementsdepicting the expected flow of equipment for each specificsituation. It is important to note that the scenarios may cover agroup of plans in support of OPLANs/CONPLANs.

• Input: Validated WRMR plan file• Output: WRWP

• Description: MEFs conduct support tests, within the WRS, todetermine materiel available to support each scenario andremaining shortfalls. This provides a snapshot of availableassets to support a specific WRWP scenario. The process testsagainst Marine Corps internal stocks only.

• Important Note: This test can be conducted within the WRS at anytime to provide a current status of available stocks as needed toupdate Force Commanders.

• Input: WRWP• Output: Marine Corps IMM Shortfalls

Figure 2.17: Plan Level Conference - Process Step Descriptions

2-28

"- Determination, Sourcir- itioring

4. Post-Conference Activities

Post-Conference Activities describe the procedures conducted to notifyappropriate HQMC elements in preparation for plan execution.

Participants in this phase are (See MCO 4400.39 for overall roles andresponsibilities) :

Deputy Commandant Installations and Logistics (DC I&L) LogisticsPlans, Policies, Strategic Mobility Division (LP) Marine Forces(MARFORs)


MCLC Supply Management Center (SMC)

Department of Defense (DoD) Integrated Materiel Managers (IMMs)

Deputy Commandant Programs & Resources (P&R) Program Assessmentand Evaluation Division (PA&E)

Deputy Commandant Plans, Policies & Operations (PP&O) OperationsDivision (PO)


Component Systems (See Figure 9.1 for complete listing ofcomponent systems)


MAGTF Deployment Support System II (MDSS II)

Marine Air-Ground Task Force War Planning System II(MAGTF II)

Joint Force Requirements Generator II (JFRG II)Joint Operation Planning and Execution System (JOPES)

cements Determination, Sou

4. Post-Conference Activities

ng, posi.tioning

Post-Conference Activities describe the procedures conducted to notifyappropriate HQMC elements in preparation for plan execution.


• Deputy Commandant Installations and Logistics (DC 1&L) LogisticsPlans, Policies, Strategic Mobility Division (LP) Marine Forces(MARFORs)


• MCLC Supply Management Center (SMC)• Department of Defense (000) Integrated Materiel Managers (IMMs)• Deputy Commandant Programs & Resources (P&R) Program Assessment

and Evaluation Division (PA&E)

• Deputy Commandant Plans, Policies & Operations (PP&O) OperationsDivision (PO)


• Component Systems (See Figure 9.1 for complete listing ofcomponent systems)

• War Reserve System (WRS)• MAGTF Deployment Support System II (MOSS II)• Marine Air-Ground Task Force War Planning System II (MAGTF II)• Joint Force Requirements Generator II (JFRG II)• Joint Operation Planning and Execution System (JOPES)

2-29

Requirements Determi ation, Sourcing, Positioning

a. Process Flow Map

Plan LeveTost-Conference '<#9)

la m... 1P:= Syten

> Post-Conference Activities

0a.o -40

It ,'4114

w0 aCI 10 eL0

008 ata.

0. 00o a.0

Pr Flury

wow<2

0 w2

-----al.4

,w4r. v1,

_

0-J 0cy gm olv t

040104 iiii.....r ,

,

0 Mo m

,

1

1

1

1

1

40111t 1,11e1T.aLl4L04 rilles'omtl ,L lini , ,__,__' , -terilrlomei2 ,., 4- 4

..,--__.,,.......1.2,.____....._

,vvror10100,...._ i'verrw ,,_.1411 =Figure 2.18: Post-Conference Activities Process Flow Map

2-30

Pos

a. Process Flow Map

Figure 2.18: Post-Conference Activities - Process Flow Map

2-30

E:mination, Sourcing, Ptiniric


16. Assign ULNs to Wholesale/Retail requirements

Description: WRPB coordinates with DMC to assign ULNs toWholesale sustainment data.Input: Tailored WRMRI

Output: DoD IMM Shortfalls

17 Register Plans w/HQMC

Description: Once the MARFOR has validated all WRS sustainmentdata associated with the separate WRWPs, MARFOR register planswith HQMC via Naval Message.Input: WRWP

Output: Registered WRWP

Document: NAVMC 4000.1 Chapter 2, War Reserve Withdrawal PlansRegistration

Create Withdrawal Plan DolTar Report

Description: WRPB create a Withdrawal Plan Dollar Report toinclude force held, in-stores, and IMM attainment for each WRWPand associated scenario.Input: WRWP

Output: Withdrawal Plan Dollar Report

19. Provide Withdrawal Plan Dollar Report

Description: WRPB submit the Withdrawal Plan Dollar Report statusupon completion of the WRWP development to LP via Naval Message.Copy MARFORs, PO, PL, PA&E.Input: Withdrawal Plan Dollar Report

Output: Naval Message

20. Participate in WRWP Risk Assessment Working 9roup

Description: PA&E, LP, PO and PL participate in the annual WRWPRisk Assessment Working Group to develop a risk assessment ofeach WRWP shortfall impact on the Enterprise. PA&E providefunding analysis and PO/PL provide operational capabilityanalysis to support the development of this risk assessment.Upon completion, PO inform the Combatant Commanders (COCOMs) ofrisk such that they accept or modify plans. LPO disseminate toWRPB and MARFORs, accordingly.Input: Withdrawal Plan Dollar ReportOutput: WRWP Risk Assessment Report

2-31


• Description: WRPB coordinates with DMC to assign ULNs toWholesale sustainment data.

• Input: Tailored WRMRI

• Output: DoD IMM Shortfalls

• Description: Once the MARFOR has validated all WRS sustainmentdata associated with the separate WRWPs, MARFOR register planswith HQMC via Naval Message.

• Input: WRWP• Output: Registered WRWP• Document: NAVMC 4000.1 - Chapter 2, War Reserve Withdrawal Plans

Registration

• Description: WRPB create a Withdrawal Plan Dollar Report toinclude force held, in-stores, and IMM attainment for each WRWPand associated scenario.

• Input: WRWP• Output: Withdrawal Plan Dollar Report

• Description: WRPB submit the Withdrawal Plan Dollar Report statusupon completion of the WRWP development to LP via Naval Message.Copy MARFORs, PO, PL, PA&E.

• Input: Withdrawal Plan Dollar Report• Output: Naval Message

• Description: PA&E, LP, PO and PL participate in the annual WRWPRisk Assessment Working Group to develop a risk assessment ofeach WRWP shortfall impact on the Enterprise. PA&E providefunding analysis and PO/PL provide operational capabilityanalysis to support the development of this risk assessment.Upon completion, PO inform the Combatant Commanders (COCOMs) ofrisk such that they accept or modify plans. LPO disseminate toWRPB and MARFORs, accordingly.

• Input: Withdrawal Plan Dollar Report• Output: WRWP Risk Assessment Report

2-31

(c¡remeots DeteImiD8tion, Souro¡ng, PositiOoiug

21' Request disposition of unsourced requirements

Description: WRPB receive input on Wholesale shortfallsdetermined during scenario support tests. WRPB source shortfallswith Marine Corps IMMs and submit all unsourced requirements tothe DoD ZMM for support. These external agencies will sourcerequirements and report back to WRPB for updating OPLAN/CONPLANsustainment data.

Input: DoD IMM Shortfalls

Output: In-stores requirement

22..

Provide Sourcing Availability

Description: DoD ZMMo determine the assets they and/or theIndustrial Base can source and provide WRPB an account of allshortfalls they are currently capable of fulfilling.Input: Remaining Shortfalls

~ `.

Description: WRPB update the TPFDD in WRS to reflect all sourcingfrom internal/external agencies.Input: WRMRI Shortfalls

24..

¡BuiId WRS Containerization and coNOlata assïgozmeot'

Description: Based on the TPFDD and particular WRWP, DMCsupported by WRPB determines the associated containerizationrequirements (number of 20' ooutaioera needed to supportrequirements) and generate ULN data to ensure all appropriateinformation is associated with the specific WRWP within WRS. WRPBprovide WRS data to Mc.Input: Scenario data

Output: Final WRS TPFDD; MAGTF II / JFRG II compatible file

25. Upload WRS sustainment data

Description: DMC receive sustainment data ULNs from WRPB andrefine for JOPES upload.Input: MAGTF II / JFRG II compatible file

irements I SClU , PO::il t

• Description: WRPB receive input on Wholesale shortfallsdetermined during scenario support tests. WRPB source shortfallswith Marine Corps IMMs and submit all unsourced requirements tothe DoD IMM for support. These external agencies will sourcerequirements and report back to WRPB for updating OPLAN/CONPLANsustainment data.

• Input: DoD IMM Shortfalls• Output: In-stores requirement

• Description: DoD IMMs determine the assets they and/or theIndustrial Base can source and provide WRPB an account of allshortfalls they are currently capable of fulfilling.

• Input: Remaining Shortfalls• Output: DoD IMM registered assets

• Description: WRPB update the TPFDD in .WRS to reflect all sourcingfrom internal/external agencies.

• Input: WRMRI Shortfalls• output: Updated WRS Wholesale TPFDD

• Description: Based on the TPFDD and particular WRWP, DMCsupported by WRPB determines the associated containerizationrequirements (number of 20' containers needed to supportrequirements) and generate ULN data to ensure all appropriateinformation is associated with the specific WRWP within WRS. WRPBprovide WRS data to DMC.

• Input: Scenario data• output: Final WRS TPFDD; MAGTF II / JFRG II compatible file

• Description: DMC receive sustainment data ULNs from WRPB andrefine for JOPES upload.

• Input: MAGTF II / JFRG II compatible file• Output: JOPES sustainment data

2-32

ents Determination, Sourcing, Positioning

k:gmaloyjmittZ,

26. Submit OPLANi6iNiSak ULN verification

Description: At the conclusion of the Plan Level conference, DMCnotify Supported MARFOR, via NEWSGROUP, that ULN data isavailable for transportation and feasibility analysis.Input: JOPES sustainment data

Output: NEWSGROUP

Figure 2.19: Post-Conference Activities Process Step Descriptions

irE-wene::; Determination, Sourcing, Positioning

26. sUbmit

• Description: At the conclusion of the Plan Level conference, DMCnotify Supported MARFOR , via NEWSGROUP, that ULN data isavailable for transportation and feasibility analysis.

• Input: JOPES sustainment data• Output: NEWSGROUPFigure 2.19: Post-Conference Activities - Process Step Descriptions

2-33


5. Plan Level Prerequisite Data Checklist

Participants in this effort are (See MCO 4400.39 for overall roles andresponsibilities):




Plan LevOlprerequdisite Data Checklist

Description. The following procedural steps are required by each MARFORprior to the Plan Level Conference.

Earliest0Acival.Date (EAD)

How to Complete:

Update should be a coordinated effort withMARFOR/MEF Planners

Provide in Sustaining Period of Support (POS)


Provide updates to WRPB no later than the start ofthe Plan Level Conference

LatelAriti 11444y(LAD5,

How to Complete:




Provide updates to WRPB no later than the startthe Plan Level Conference

of

Figure 2.20: Plan Level Prerequisite Data Checklist


5. Plan Level Prerequisite Data Checklist

Participants in this effort are (See MCO 4400.39 for overall roles andresponsibilities) :

• Marine Forces (MARFORs)• Marine Expeditionary Forces (MEFs)• Marine Corps Logistics Command (MCLC) War Reserve Planning Branch

(WRPB)

The following procedural steps are required by each MARFORPlan Level Conference.

How to Complete:





How to Complete:


Figure




2.20: Plan Level Prerequisite Data Checklist

2-34

rf-!xtents Determination, Sourcino, Positioning

6. EXAMPLE GUIDANCE MESSAGE WAR RESERVE WITHRAWAL PLAN(WRWP) CONFERENCE.

NOTE: Content in brackets [ ] will be populated by LPO when message isreleased.

UNCLASSIFIED//FM CMC WASHINGTON DC LP LPOTO COMMARCORLOGCOM ALBANY GA

COMMARFORRESCOMMARFORRES (G-5/4)COMMARFORPACCOMMARFORPAC (G-5/4)COMMARFORCOMCOMMARFORCOM (G-3/4/5/7)

CC CG III MEFCG III MEF (G-3/4)CG I MEFCG I MEF (G-3/4)CG II MEFCG II MEF (G-4)COMMARCORSYSCOM QUANTICO VACG MCCDC QUANTICO VACMC WASHINGTON DC P&RCMC WASHINGTON DC L LPCCMC WASHINGTON DC PP&OCMC WASHINGTON DC LCMC WASHINGTON DC PLNCMC WASHINGTON DC POCCOMUSMARCENT (G-4)COMUSMARSOCLOGMODTM WESTPACLOGMODTM WESTFSMAO EAST

[THIS DOCUMENT MAY BECOME CLASSIFIED WHEN COMPLETELY FILLED IN]MSGID/GENADMIN/LPO/SUBJ/ GUIDANCE FOR FYXX WAR RESERVE WITHRAWAL PLAN (WRWP) CONFERENCE//1. REF/A/DOC/MCO 4400.39/-// REF/B/DOC/NAVMC 4000.1/-// REF/C/DOC/MCOP3000.18/-// NARR/REF A IS THE WAR RESERVE MATERIEL POLICY. REF B ISTHE WRM PROGRAM HANDBOOK. REF c IS THE MARINE CORPS PLANNERS MANUAL.//POC/XX/LP0/-/TEL:703-695-8870/TEL:DSN 225-8870/EMAIL:XX////GENTEXT/ REMARKS/ THIS IS A COORDINATED HQMC AND COMMARCORLOGCOMMSG.2. THE FYXX ANNUAL WAR RESERVE WITHDRAWAL PLAN DEVELOPMENT CONFERENCEWILL BE HOSTED BY MCLC 1DATE], AT MCLC, ALBANY GA. REPRESENTATIVESFROM.[LIST OF OFFICE SYMBOLS] ARE REQUESTED ATTENDEES.3. PURPOSE.4. ACTION.4.A. THE FOLLOWING PROCEDURAL STEPS ARE REQUIRED BY EACH MARFOR PRIORTO THE WRWP CONFERENCE.

.-, :~ r f-!menrs Determination I Sourcinq, Posi tioning

6. EXAMPLE GUIDANCE MESSAGE WAR RESERVE WITHRAWAL PLAN(WRWP) CONFERENCE

NOTE: Content in brackets [ ] will be populated by LPO when message isreleased.

UNCLASSIFIED//FM CMC WASHINGTON DC LP LPOTO COMMARCORLOGCOM ALBANY GA

COMMARFORRESCOMMARFORRES (G-5/4)COMM.r..RFORPACCOt1MARFORPAC (G-5/4)COl'1MARFORCOMCOMMARFORCOM (G-3/4/5/7)

CC CG III MEFCG III MEF (G-3/4)CG I MEFCG I MEF (G-3/4)CG II MEFCG II MEF (G-4)COMMARCORSYSCOM QUANTICO VACG MCCDC QUANTICO VACMC WASHINGTON DC P&RCMC WASHINGTON DC L LPCCMC WASHINGTON DC PP&OCMC WASHINGTON DC LCMC WASHINGTON DC PLNCMC WASHINGTON DC POCCOMUSMARCENT (G-4)COMUSMARSOCLOGMODTM WESTPACLOGMODTM WESTFSMAO EAST

[THIS DOCUMENT MAy BECOME CLASSIFIED WHEN COMPLETELY FILLED IN]MSGID/GENADMIN/LPO/SUBJ/ GUIDANCE FOR FYXX WAR RESERVE WITHKr..WAL PLAN (WRWP) CONFERENCE//1. REF/A/DOC/MCO 4400.39/-// REF/B/DOC/NAVMC 4000.1/-// REF/C/DOC/MCOP3000.18/-// NARR/REF A IS THE WAR RESERVE MATERIEL POLICY. REF B ISTHE WRM PROGRAM HANDBOOK. REF c IS THE MARINE CORPS PLANNERS MANUAL.//POC/XX/LPO/-/TEL:703-695-8870/TEL:DSN 225-8870/EMAIL:XX////GENTEXT/ REMARKS/ THIS IS A COORDINATED HQMC AND COMMARCORLOGCOMMSG.2. THE FYXX ANNUAL WAR RESERVE WITHDRAWAL PLAN DEVELOPMENT CONFERENCEWILL BE HOSTED BY MCLC ,[DATE], AT MCLC, ALBANY GA. REPRESENTATIVESFROM [LIST OF OFFICE SYMBOLS] ARE REQUESTED ATTENDEES.3. PURPOSE.4. ACTION.4.A. THE FOLLOWING PROCEDURAL STEPS ARE REQUIRED BY EACH MARFOR PRIORTO THE WRWP CONFERENCE.

2-35

Requirements Determination, Sourcing, Positi ning

4.A.1. DESIGNATED USER REPRESENTATIVES HAVE COMPLETED WAR RESERVESYSTEM TRAINING HAVE SUBMITTED CERTIFICATE OF COMPLETION PRIOR TOCONFERENCE INITATION.4.A.2. ENSURE DESIGNATED USER REPRESENTATIVES HAVE GATHERED REQUIREDINFORMATION IAW PLAN LEVEL PREREQUISITE DATA CHECKLIST, NAVMC 4000.1,CHAPTER 2.4.A.3. PROVIDE THE NAMES OF INDIVIDUALS ATTENDING THE CONFERENCE TOTHIS HQS NLT [DATE].4.A.4 ENSURE DESIGNATED USER REPRESENTATIVES HAVE VERIFIED SECURITYCLEARANCE. [PROCEDURES FOR SENDING CLEARANCE IDENTIFICATION/VERIFICATION] . INCLUDE THE FOLLOWING INFORMATION: NAME,GRADE/RANK,SSN, CLEARANCE WITH EFFECTIVE DATE, UNIT, OFFICE SYMBOL, DUTY PHONE.4.B. HEALTH & COMFORT PACK (HCP) PERCENTAGE4.B.1. MALE4.B.2. FEMALE5. ADMIN AND LOGISTICS.5.A. MEF PLANNERS HAVE THE CURRENT FORCE LIST FOR OPLANS.5.B. PLAN DEVELOPERS ARE REQUIRED TO BUILD SEPARATE PLANS FOR ACTIVEAND RESERVE FORCES IN SUPPORT OF. EACH OPLAN/CONPLAN.5.C. THE FOLLOWING PROGRAMMING SCENARIOS WILL BE USED FOR DEVELOPINGAND UPDATING PLANS.5.D. THE FOLLOWING PARAMETER DATA WILL BE USED FOR DEVELOPING ANDUPDATING PLANS.5.E. NEW PLANS.5.E.1 TEMP FACTORS: XX.5.E.2 APPLY MPS: XX.5.E.3 EPW FACTORS: XX.5.E.4 MAXIMUM SUSTAINING SUPPLY PERIOD IS 90 DAYS IN THREE PERIODS OFSUPPORT (POS) : XX.

5.E.5 SUSTAINMENT INTENSITY RATES.5.E.6 FEED PLAN.5.E.7 PERSONNEL TO BE FED.5.E.8 REQUEST G5 PLANS PERSONNEL WORK WITH PLAN DEVELOPERS WHEN ADDINGFORCES TO THE WRWD PLANS.6. COORDINATING INSTRUCTIONS.6.A. [CONFERENCE LOCATION]6.B. [AGENDA]6.C. TAD FUNDING IS A UNIT RESPONSIBILITY.6.E. [MARINE UNIFORM]. [CONFERENCE ATTIRE]6.F. [HOTEL INFORMATION]BT


4.A.1. DESIGNATED USER REPRESENTATIVES HAVE COMPLETED WAR RESERVESYSTEM TRAINING HAVE SUBMITTED CERTIFICATE OF COMPLETION PRIOR TOCONFERENCE INITATION.4.A.2. ENSURE DESIGNATED USER REPRESENTATIVES HAVE GATHERED REQUIREDINFORMATION lAW PLAN LEVEL PREREQUISITE DATA CHECKLIST, NAVMC 4000.1,CHAPTER 2.4.A.3. PROVIDE THE NAMES OF INDIVIDUALS ATTENDING THE CONFERENCE TOTHIS HQS NLT [DATE].4.A.4 ENSURE DESIGNATED USER REPRESENTATIVES HAVE VERIFIED SECURITYCLEARANCE. [PROCEDURES FOR SENDING CLEARANCE IDENTIFICATION!VERIFICATION]. INCLUDE THE FOLLOWING INFORMATION: NAME,GRADE!RANK,SSN, CLEARANCE WITH EFFECTIVE DATE, UNIT, OFFICE SYMBOL, DUTY PHONE.4.B. HEALTH & COMFORT PACK (HCP) PERCENTAGE4.B.1. MALE4.B.2. FEMALE5. ADMIN AND LOGISTICS.5.A. MEF PLANNERS HAVE THE CURRENT FORCE LIST FOR OPLANS.5.B. PLAN DEVELOPERS ARE REQUIR~D TO BUILD SEPARATE PLANS FOR ACTIVEAND RESERVE FORCES IN SUPPORT OF EACH OPLAN!CONPLAN.S.C. THE FOLLOWING PROGRAMMING SCENARIOS WILL BE USED FOR DEVELOPINGAND UPDATING PLANS.5.0. THE FOLLOWING PARAMETER DATA WILL BE USED FOR DEVELOPING ANDUPDATING PLANS.5.E. NEW PLANS.5.E.1 TEMP FACTORS: XX.5.E.2 APPLY MPS: XX.5.E.3 EPW FACTORS: XX.5.E.4 MAXIMUM SUSTAINING SUPPLY PERIOD IS 90 DAYS IN THREE PERIODS OFSUPPORT (POS): XX.5.E.5 SUSTAINMENT INTENSITY RATES.5.E.6 FEED PLAN.5.E.7 PERSONNEL TO BE FED.5.E.8 REQUEST G5 PLANS PERSONNEL WORK WITH PLAN DEVELOPERS WHEN ADDINGFORCES TO THE WRWD PLANS.6. COORDINATING INSTRUCTIONS.6.A. [CONFERENCE LOCATION]6.B. [AGENDA]6.e. TAD FUNDING IS A UNIT RESPONSIBILITY.6.E. [MARINE UNIFORM]. [CONFERENCE ATTIRE]6.F. [HOTEL INFORMATION]BT

2-36

reme-- Determination, Sourc ng, Poítioning

7.Example of War Reserve Withdrawal Plans (WRWP)Registration

The example below is fOr the registration of withdrawal plans withinthe WRS. Information provided is an example only, actual input isclassified accordingly. NOTE: Content in brackets [ ] will bepopulated by Supported MARFOR when message is released.

FM MARFOR MAKING THE REGISTRATIONTO CMC WASHINGTON DC L LPOCC COMMARCORLOGCOM ALBANY GA//M400//

COMMARCORSYSCOM QUANTICO VA//AM//CMC WASHINGTON DC PP&OCMC WASHINGTON DC LCMC WASHINGTON DC PLNCMC WASHINGTON DC POCCMC QUANTICO CD&ICOMUSMARCENT (G-4)COMUSMARSOCCOMMARFORCOW/G-41G-5/1CG III MEFCG III MEF (G-3/4)CG I MEFCG I MEF (G-3/4)CG II MEFCG II MEF (G-4)SUPPORTING FORCE COMMANDER//G-4/G-5//SUPPORTED MAGTF COMMANDER//G-4/G-5//FMF MSC'S (as appropriate)CG MARFORRES//G-4/FSO/G-5//(as appropriate)MARFORRES MSC'S (as appropriate)COMMARCORSYSCOM QUANTICO VA//PS//SUPPORTING ESTABLISHMENT MSC'S (as appropriate)

[THIS DOCUMENT WILL BECOME CLASSIFIED WHEN COMPLETELY FILLED IN]CLASSIFICATION //N04000//SUBJ/WAR RESERVE WITHDRAWAL PLANS REGISTRATION FOR [COCOM OPLAN/XXXX-XX or OPERATION/EXERCISE TITLE] (U)//A. COCOM/CJCS AUTHORIZING DIRECTIVEB. MCO 4400.39C. MCO P3000.18RMKS/1. (S) FOLLOWING DATA PROVIDED TO REGISTER WITHDRAWAL PLANS:A. (U) WITHDRAWAL PLANS: [WRWP NUMBERS].B. (U) TITLE: [XX]

C. (S) OPLAN SUPPORTED: [XXXX-XX]D. (U) PERIOD OF SUPPORT: [XX]

E. (U) TPFDD DATA LOCATED IN PLAN IDENTIFICATION (PID) NUMBER [INSERTPID NUMBER].2. (U) POC IS [NAME, RANK, DSN/SVOIP].

2-37

1 rem!",!; t::.: Detel'mina t ion, sourcing, 205i tioning

7. Example of War Reserve Withdrawal Plans (WRWP)Registration

The example below is for the registration of withdrawal plans withinthe WRS. Information provided is an example only, actual input isclassified accordingly. NOTE: Content in brackets [ ] will bepopulated by Supported MARFOR when message is released.

FM MARFOR MAKING THE REGISTRATIONTO CMC WASHINGTON DC L LPOCC CO~~RCORLOGCOM ALBANY GA//M400//

COMMARCORSYSCOM QUANTICO VA//AM//CMC WASHINGTON DC PP&OCMC WASHINGTON DC LCMC WASHINGTON DC PLNCMC WASHINGTON DC POCCMC QUANTICO CD&ICOMUSMARCENT (G-4)COMUSMARSOCCOMMARFORCOM//G-4/G-5//CG III MEFCG III MEF (G-3/4)CG I MEFCG I MEF (G-3/4)CG II MEFCG II MEF (G-4)SUPPORTING FORCE COMMANDER//G-4/G-5//SUPPORTED ~~GTF COMMANDER//G-4/G-5//FMF MSC'S (as appropriate)CG MARFORRES//G-4/FSO/G-5//(as appropriate)MARFORRES MSC'S (as appropriate)COMMARCORSYSCOM QUANTICO VA//PS//SUPPORTING ESTABLISHMENT MSC'S (as appropriate)

[THIS DOCUMENT WILL BECOME CLASSIFIED WHEN COMPLETELY FILLED IN]CLASSIFICATION //N04000//SUBJ/WAR RESERVE WITHDRAWAL PLANS REGISTR~TION FOR [COCOM OPLAN/XXXX-XX or OPERATION/EXERCISE TITLE] (U) / /A. COCOM/CJCS AUTHORIZING DIRECTIVEB. MCO 4400.39C. I'1CO P3000.18RMKS/1. (S) FOLLOWING DATA PROVIDED TO REGISTER WITHDRAWAL PLANS:A. (U) WITHDRAWAL PLANS: [WRWP NUMBERS] .B. (U) TITLE: [XX]C. (S) OPLAN SUPPORTED: (XXXX-XX]D. (U) PERIOD OF SUPPORT: [XX]E. (U) TPFDD DATA LOCATED IN PLAN IDENTIFICATION (PID) NUMBER [INSERTPID NUMBER].2. (U) POC IS [NAME, RANK, DSN/SVOIPj.

2-37

'NAVMC 4000.1War Reserve Materiel Program Handbook

Acquisition

Chapter 3

isit

~~P~l

INAVMC 4000.1IWar Reserve Materiel Program HandbookII1'1

~I

IAcquisitioni

Chapter 3

Ii

3-1

Table of Contents

A. WRM Functions1. Acquisition2. POM Process

3-3

3-33-3

B. Warfighting PEB 3-4

1. Description 3-4

2. Process Flow Map 3-5

3. Process Step Descriptions 3-6C. Sustainment PEB 3-8

1. Description 3-8

2. Process Flow Map 3-93. Process Step Descriptions 3-9

·L::~iti)n

Table of Contents

A. WRM Functions 3-31 . Acquisition 3-32. POM Process 3-3

B. Warfighting PEB 3-41. Description 3-42. Process Flow Map 3-53. Process step Descriptions ; 3-6

c. Sustairunent PEB 3-81. Description 3-82. Pr()cess Flow Map 3- 93. Process step Descriptions 3-9

3-2

Acquisition

A. WRM Functions

The WRM Functions are the means by which the Marine Corps provides forsufficient materiel, within the limits of acceptable risk, to sustainoperating forces from inception to the establishment of the theatersupport capability. This Handbook only addresses Class I, II, III(P),IV, VI, VII, VIII, and IX ground materiel. Further information onClasses V can be found in MCO 4400.39.

Although the WRM Functions are executed separately, they are mutuallysupporting activities. This Handbook defines the specific roles andresponsibilities for the participants associated with each function.Additional stakeholders may support these activities as appropriate.This chapter addresses the execution of the Acquisition function as itrelates to the program.

sere4n1,1v .4g

(lire

''

RectOremeNts

RkeriminatiokSourcing ) Posititini* cgipsition....,,., ,

.. v !

Distribu ion

Manage ent


1. Acquisition

Acquisition consists of the procurement activities completed toresource the Marine Corps War Reserve Materiel Requirement (WRMR)determined during the MEF Level Annual Recomputation Conference (SeeChapter 2 for Requirements Determination) . WRMR is an Enterpriserequirement supported by various funding and procurement activitiesaccomplished through the Program Objective Memorandum (POM) . MarineCorps Systems Command (MCSC) procures Type 1 End Items for Class IIand Class VII, designated as combat essential; Class V; and initialprovisioning of Class IX through the Warfighting Program EvaluationBoard (PEB) . Marine Corps Logistics Command (MCLC) procures Class II,111(P), IV, and IX through the Sustainment PEB. DC Installations andLogistics (I&L) (LFS) funds Class I for MARFOR procurement through theManning PEB. MARFORs procure War Reserve Materiel Requirement Force-held (WRMRF) and Class VIII Authorized Medical AllowanceLists/Authorized Dental Allowance Lists (AMALs/ADALs) through normalunit funding processes. Consumables and reparables are procured byMCLC and MARFORs for a combined total of at least 60 Days of Supply(DOS).

2 . POM Process

The POM provides a detailed and comprehensive six-year projection ofthe proposed programs. Programming begins with the development of aPOM by each DoD component.

3-3

Acquisition

A. WRM Functions


Although the WRM Functions are executed separately, they are mutuallysupporting activities. This Handbook defines the specific roles andresponsibilities for the participants associated with each function.Additional stakeholders may support these activities as appropriate.This chapter addresses the execution of the Acquisition function as itrelates to the program.


1. Acquisition

Acquisition consists of the procurement activities completed toresource the Marine Corps War Reserve Materiel Requirement (WRMR)determined during the MEF Level Annual Recomputation Conference (SeeChapter 2 for Requirements Determination). WRMR is an Enterpriserequirement supported by various funding and procurement activitiesaccomplished through the Program Objective Memorandum (PaM). MarineCorps Systems Command (MCSC) procures Type 1 End Items for Class IIand Class VII, designated as combat essential; Class V; and initialprovisioning of Class IX through the Warfighting Program EvaluationBoard (PEB). Marine Corps Logistics Command (MCLC) procures Class II,III(P), IV, and IX through the Sustainment PEB. DC Installations andLogistics (I&L) (LFS) funds Class I for MARFOR procurement through theManning PEB. MARFORs procure War Reserve Materiel Requirement Forceheld (WRMRF) and Class VIII Authorized Medical AllowanceLists/Authorized Dental Allowance Lists (AMALs/ADALs) through normalunit funding processes. Consumables and reparables are procured byMCLC and MARFORs for a combined total of at least 60 Days of Supply(DOS) .

2. POM Process

The POM provides a detailed and comprehensive six-year projection ofthe proposed programs. Programming begins with the development of aPOM by each 000 component.

3-3

It is crucial that program sponsors/advocates clearly articulate thevalue/benefit of program resources in order to receive funding.

Program sponsors determine what requirements are needed for theirprogram and submit initiatives to HQMC for review by the appropriatePEBs. The PEB process relies on subject matter experts to reviewinitiatives and assess the relative value of each initiative. The PEBsreceive briefs on initiatives, review all guidance, and deliver aprioritized list of initiatives with assigned benefit values.

Although DC I&L is the overall advocate for WRM Program, MCLC is thelead for WRM funding and procurement. MCLC supports funding initiativedevelopment and validation of Type 1 End Items for Class II and ClassVII in the Warfighting PEB through collaboration with CD&I and MCSC.In addition, MCLC is responsible for submitting initiatives andbriefing the Sustainment PEB on Class II secondary items, III, IV andIX WRM requirements. These MCLC activities are supported by DC I&L.This chapter examines the procedures conducted to submit and justifyfunding requirements in both PEBs, respectively.

B. Warfighting PEB

1. Description

The Warfighting PEB, or WIPEB, is the procurement or investment PEB.The WRM Program competes for funding of Type i End Items for Class IIand VII requirements, designated as combat essential on theWarfighting PEB.



Deputy Commandant Combat Development and Integration (DC CD&I)Capability Integration Officers (CI0s)

DC CD&I Total Force Structure Division (TFSD)

DC CD&I Combat Development Directorate (CDD)DC CD&I Integration Division (ID)


Marine Corps Systems Command (MCSC) Program Managers (PMs)


Total Force Structure Management System (TFSMS)Program and Budgeting Documentation Database (PBDD)

U ->.• :~; .i t (;11

It is crucial that program sponsors/advocates clearly articulate thevalue/benefit of program resources in order to receive funding.

Program sponsors determine what requirements are needed for theirprogram and submit initiatives to HQMC for review by the appropriatePEBs. The PEB process relies on subject matter experts to reviewinitiatives and assess the relative value of each initiative. The PEBsreceive briefs on initiatives, review all guidance, and deliver aprioritized list of initiatives with assigned benefit values.

Although DC I&L is the overall advocate for WRM Program, MCLC is thelead for WRM funding and procurement. MCLC supports funding initiativedevelopment and validation of Type 1 End Items for Class II and ClassVII in the Warfighting PEB through collaboration with CD&I and MCSC.In addition, MCLC is responsible for submitting initiatives andbriefing the Sustainment PEB on Class II secondary items, III, IV andIX WRM requirements. These MCLC activities are supported by DC I&L.This chapter examines the procedures conducted to submit and justifyfunding requirements in both PEBs, respectively.

B. Warfiqhtinq PEB

1. Description

The Warfighting PEB, or WIPEB, is the procurement or investment PEB.The WRM Program competes for funding of Type 1 End Items for Class IIand VII requirements, designated as combat essential on theWarfighting PEB.

Participants in this phase are (See Mca 4400.39 for overall roles andresponsibili ties) :


• Deputy Commandant Combat Development and Integration (DC CD&I)Capability Integration Officers (CIOs)

• DC CD&I Total Force Structure Division (TFSD)

• DC CD&I Combat Development Directorate (COD)• DC CD&I Integration Division (ID)• Marine Corps Logistics Command (MCLC) War Reserve Planning Branch

(WRPB)• Marine Corps Systems Command (MCSC) Program Managers (PMs)


• Total Force Structure Management System (TFSMS)• Program and Budgeting Documentation Database (PBDD)

3-4

Acquisition

2 . Process Flow Map

Figure 3.2: Warfighting PEB Process Flow Map

3-5

2. Process Flow Map

Figure 3.2: Warfighting PEB - Process Flow Map

3-5

Acc.,L


1. Submit,WRMRfor Type 1 End Items for Class IÍ & viI

Description: At the completion of the Recomputation, WRPB providedata to CDD detailing the requirement quantities for Type i EndItems for Class II and Class VII.Input: WRMR (NAVMC 4000.1 Chapter 2, MEF Level Conference)

Output: Wholesale Inventory Requirements of Type 1 End Items forClass II and Class VII (WRMR)

Document: WRMR data

.2, Receive WRMR data and validate w/ID

Description: CDD receives the WRMR data; reviews and coordinatesthe data with the ID.

Input: Wholesale Inventory Requirements of Type 1 End Items forClass II and Class VII (WRMR)Output: Verified WRMR

3. CootdinAte to establ*Ohkequirament's validation

Description: CDD engage with CIOs, ID, LPO, WRPB, and PMs todetermine availability for the requirements validation.


4. 4AsseSs program and Validate regUirements

Description: CDD, CIOs, ID, LPO, WRPB and PMs align requirementsdetermined during MEF Level Annual Recomputation Process withprogram functional and Total Life Cycle Management (TLCM)analysis.

Input: WRMR data; Functional Analysis; TLCM Analysis

Output: Final WRMR

Submit TOECR to adjust WRMR in TFSMS

Description: Once the WRMR are validated, the appropriate IDsubmits a T/O&E Change Request (TOECR) to adjust the WRMRregistered in TFSMS, accordingly.Input: Verified WRMROutput: TFSMS data


1.

• Description: At the completion of the Recomputation, WRPB providedata to COO detailing the requirement quantities for Type 1 EndItems for Class II and Class VII.

• Input: WRMR (NAVMC 4000.1 - Chapter 2, MEF Level Conference)

• Output: Wholesale Inventory Requirements of Type 1 End Items forClass II and Class VII (WRMR)

• Document: WRMR data

2.

• Description: COO receives the WRMR data; reviews and coordinatesthe data with the 10.

• Input: Wholesale Inventory Requirements of Type 1 End Items forClass II and Class VII (WRMR)

• Output: Verified WRMR

3. Coordi.nate to

• Description: COO engage with CIOs, 10, LPO, WRPB, and PMs todetermine availability for the requirements validation.

• Output: Email/phone call

4. Assessprogram:afi equirements

• Description: COD, CIOs, 10, LPO, WRPB and PMs align requirementsdetermined during MEF Level Annual Recomputation Process withprogram functional and Total Life Cycle Management (TLCM)analysis.

• Input: WRMR data; Functional Analysis; TLCM Analysis• Output: Final WRMR

• Description: Once the WRMR are validated, the appropriate 10submits a T/O&E Change Request (TOECR) to adjust the WRMRregistered in TFSMS, accordingly.

• Input: Verified WRMR• Output: TFSMS data

3-6

Acquisition

6. ApripOelECR subialssion

Description: TFSD approve TOECR submitted by the appropriate ID

Input: TFSMS data

Output: Approved TFSMS data

7. Generate requirements documents; tailorto CD&I Functional Groups

Description: CIOs incorporate WRMR into PBDD and alignrequirements to one of the 5 Warfighting Functions: ForceProtection, Logistics, Fires & Maneuver, Intelligence, Command &Control. The Functional Groups divide up programs by theirfunctional support and conduct analysis on the program in orderto justify program requirements.

Input: Approved TFSMS data

8. Génate 5.nitiatives briefs and imp*

Description: CIOs update the validated WRMR in the PBDD and workwith CD&I Programmers to substantiate requirements.

Input: Final WRMR

Output: PBDD Updates

Figure 3.3: Warfighting PEB Process Step Descriptions

Acquisition

• Description: TFSD approve TOECR submitted by the appropriate 10• Input: TFSMS data• Output: Approved TFSMS data

Fun.ctional Groups

• Description: CIOs incorporate WRMR into PBDD and alignrequirements to one of the 5 Warfighting Functions: ForceProtection, Logistics, Fires & Maneuver, Intelligence, Command &Control. The Functional Groups divide up programs by theirfunctional support and conduct analysis on the program in orderto justify program requirements.

• Input: Approved TFSMS data

• Description: CIOs update the validated WRMR in the PBDD and workwith CD&I Programmers to substantiate requirements.

• Input: Final WRMR• Output: PBDD Updates

Figure 3.3: Warfighting PEB - Process Step Descriptions

3-7

C. Sustainment PEE

1. Description

The Sustainment PEB is the Operations & Maintenance PEB. The WRMProgram competes for funding of Class II secondary items, III (P), IV,

and IX requirements on the' Sustaining PEB.

Participants in this phase are (See MCO 4400.39 for overall roles andresponsibilities) :

Deputy Commandant Installations and Logistics (DC I&L)

Commanding General (CG) Marine Corps Logistics Command (MCLC)

DC I&L Logistics Plans and Operations Branch (LPO)

MCLC War Reserve Planning Branch (WRPB)


Program and Budgeting Documentation Database (PBDD)

C. sustainment PEB

1. Description

The Sustainment PEB is the Operations & Maintenance PEB. The WRMProgram competes for funding of Class II secondary items, III (P), IV,and IX requirements on the' Sustaining PEB.


• Deputy Commandant Installations and Logistics (DC I&L)• Commanding General (CG) Marine Corps Logistics Command (MCLC)

• DC I&L Logistics Plans and Operations Branch (LPO)• MCLC War Reserve Planning Branch (WRPB)


• Program and Budgeting Documentation Database (PBDD)

3-8

Acqui3ition

2. Process Flow Map

AC Ci Fi i

IA , .4 kW.

...I00

00LOZCL"rikAil

200

..,

ati 6

0-

2 ,i-e.,awl

s Eo2

,

1

1

i

'3 ,- 7 . I 7 '

'''!_tttILL-wilimilliiiiiiW22-112--7-SyMer ...i._ .........m...,_

Figure 3.4: Sustainment PEB Process Flow Map


Provide- L

VIRMAkAA Iglare IIIAP), IV, & IX

Description: WRPB provide P&R with WRMR attainment, shortfalls,associate dollar value and risk assessment associated with ClassII secondary items, III (P), IV, and IX to support P&R'sdevelopment of a brief to CG MCLC.Output: Posture Report (See NAVMC 4000.1 Chapter 2, MEF LevelConference)

l\cqui.3ition

2. Process Flow Map

od~

<:>o

Figure 3.4: Sustainment PEB - Process Flow Map


&IX

• Description: WRPB provide P&R with WRMR attainment, shortfalls,associate dollar value and risk assessment associated with ClassII secondary items, III (P), I~ and IX to support P&R'sdevelopment of a brief to CG MCLC .

• Output: Posture Report (See NAVMC 4000.1 - Chapter 2, MEF LevelConference)

3-9

2. Brief CG MCLC on WRMRtand?Attaihment Ana1YsiS1,p/C rryl

Description: P&R brief CG MCLC on the results of the requirementsdetermination activities. This briefing will include percent WRMRattainment, shortfalls, associate dollar value and riskassessment.

Input: Posture Report (See NAVMC 4000.1 Chapter 2, MEF LevelConference)

Output: Draft briefing

3. Provide gUidance onkthiOMand Attainment Analysis

Description: CG MCLC provide guidance to WRPB based on determinedpriorities, budgetary constraints, and acceptable risk.

4. Modify brief per CGACLC" guidance and ,právide to:

Description: P&R incorporate guidance of CG MCLC and finalizebriefing. This briefing will facilitate the creation of the WRMProgram Prioritization Briefing.Input: Draft briefingOutput: Final briefing

5. Create PEB prioiitliatkón ljustification briefing

Description: LPO create a prioritization justification briefingto DC I&L. Since DC I&L is the authority for setting theSustainment PEB priorities for each cycle, this effort serves toprovide DC I&L with the WRM Program value/benefit and risksassociated with shortfalls prior to prioritization.Input: WRPB reportOutput: WRM Program Prioritization Briefing

6. Brief DC I&L

Description: LPO brief DC I&L on WRM Program PrioritizationBriefing to support modifications in the program priority.Input: WRM Program Prioritization Briefing

Output: DC I&L guidance/feedback

7. Provide guidance onopr;:prities

Description: DC I&L establish priorities for the Sustainment PEBto support their initiative prioritization.Input: Various Program Prioritization Briefings

Output: DC I&L Sustainment PEB Priorities

2. Brief

• Description: P&R brief CG MCLC on the results of the requirementsdetermination activities. This briefing will include percent WRMRattainment, shortfalls, associate dollar value and riskassessment.

• Input: Posture Report (See NAVMC 4000.1 - Chapter 2, MEF LevelConference)

• Output: Draft briefing

• Description: CG MCLC provide guidance to WRPB based on determinedpriorities, budgetary constraints, and acceptable risk.

3. Provide guidance

4. Modify"pri'

• Description: P&R incorporate guidance of CG MCLC and finalizebriefing. This briefing will facilitate the creation of the WRMProgram Prioritization Briefing.

• Input: Draft briefing• output: Final briefing

• Description: LPG create a prioritization justification briefingto DC I&L. Since DC I&L is the authority for setting theSustainment PEB priorities for each cycle, this effort serves toprovide DC I&L with the WRM Program value/benefit and risksassociated with shortfalls prior to prioritization.

• Input: WRPB report• Output: WRM Program Prioritization Briefing

6. Brief DC','

• Description: LPG brief DC I&L on WRM Program PrioritizationBriefing to support modifications in the program priority.

• Input: WRM Program Prioritization Briefing• Output: DC I&L gUidance/feedback

7. Provide,;' ",

• Description: DC I&L establish priorities for the Sustainment PEBto support their initiative prioritization.

• Input: Various Program Prioritization Briefings• Output: DC I&L Sustainment PEB Priorities

3-10

Support the creation of WRM initiative/briefing

Description: LPO gather/incorporate any feedback and provide toP&R to support generation of WRM Program initiatives.Additionally, WRPB provide subject matter expertise and reachback support to MCLC P&R in their development of WRM initiatives.

Input: DC I&L Sustainment PEB Priorities

Output: LPO guidance/feedback

9.:Create initiative and support brief for PEB review

Description: MCLC P&R, supported by LPO/WRPB, create WRM Programinitiative and briefing in PBDD depicting the value/benefit ofprogram resources and the risk associated with programshortfalls.Input: DC I&L Sustainment PEB Priorities; LPO guidance/feedback

Output: Initial WRM Program Initiative; Initial WRM Program Brief

10 Submit initiative/briefing to Sustainment PEB Chair

Description. MCLC P&R, supported by LPO/WRPB, refine programinitiative/brief until it is ready for submission. Upon completionor within the prescribed timeframe, WRPB submit finalinitiative/briefing to the Sustainment PEB Chair.Input: Initial WRM Program Initiative; Initial WRM Program Brief

Output: Final WRM Program Initiative; Final WRM Program Brief

11. Present briefing to PEB and make case, for programrequirements

Description. MCLC P&R, supported by LPO/WRPB, present WRM Programbrief to the Sustainment PEB to support program resources.Note: This presentation may be consolidated into the overall MCLCrequirements briefing.

Input: Final WRM Program BriefFigure 3.5: Sustainment PEB Process Step Descriptions

F"I.-U ","_3 lOn

e creation of WRM initia briefing

• Description: LPO gather/incorporate any feedback and provide toP&R to support generation of WRM Program initiatives.Additionally, WRPB provide subject matter expertise and reachback support to MCLC P&R in their development of WRM initiatives.

• Input: DC I&L Sustainment PEB Priorities• Output: LPO guidance/feedback

9. and support brie review

• Description: MCLC P&R, supported by LPO/WRPB, create WRM Programinitiative and briefing in PBDD depicting the value/benefit ofprogram resources and the risk associated with programshortfalls.

• Input: DC I&L Sustainment PEB Priorities; LPO guidance/feedback• Output: Initial WRM Program Initiative; Initial WRM Program Brief

10. Submit initiative/briefing to S an.t PEB Chair

• Description. MCLC P&R, supported by LPO/WRPB, refine programinitiative/brief until it is ready for submission. Upon completionor within the prescribed timeframe, WRPB submit finalinitiative/briefing to the Sustainment PEB Chair.

• Input: Initial WRM Program Initiative; Initial WRM Program Brief• Output: Final WRM Program Initiative; Final WRM Program Brief

lrieofing to PEB and mabJ(,€!c::a:S8' for program

• Description. MCLC P&R, supported by LPO/WRPB, present WRM Programbrief to the Sustainment PEB to support program resources.

• Note: This presentation may be consolidated into the overall MCLCrequirements briefing.

• Input: Final WRM Program BriefFigure 3.5: Sustainment PEE - Process Step Descriptions

3-11

:NAVMC 4000.1War Reserve Materiel Program Handbook

Distribution

Chapter 4

4-1

.L, () (J n


Distribution

Chapter 4

4-1

Distribution

TAble of Contents

A. WRM Functions 4-2B. Withdrawal Release Message Activities 4-6C. Execution Authorization Message Activities 4-9D. MCLC Funding Alignment Activities 4-12E. Withdrawal Execution Prerequisite Activities 4-15F. Withdrawal Execution Activities 4-19G. Example Request for Withdrawal of Registered WRWP Message 4-26

Distribution

Table of Contents

A. WRM Functions 4-2B. Withdrawal Release Message Activities 4-6C. Execution Authorization Message Activities 4-9D. MCLC Funding Alignment Activities 4-12E. Withdrawal Execution Prerequisite Activities 4-15F. Withdrawal Execution Activities 4-19G. Example Request for Withdrawal of Registered WRWP Message 4-26

4-2

)

WRM Functions


Although the WRM Functions are executed separately, they are mutuallysupporting activities. This Handbook defines the specific roles andresponsibilities for the participants associated with each function.Additional stakeholders may support these activities as appropriate.This chapter addresses the execution of the Distribution function asit relates to the program.

Selection Requirements-/ Criteria DeterminationSourcing Positioning Acquisition Distribution

Management


1. Distribution

Distribution is the authorization, release, and movement of WRM assetsto a desired Sea/Aerial Port of Debarkation (S/APOD) upon request fromthe lead MARFOR and approval of HQMC in support of a specificOPLAN/CONPLAN. WRM distribution activities are initiated upon receiptof HQMC approval.

2 . Withdrawal Process

Once the order is released and the MARFORs receive authorization, theyare responsible for the movement of WRMSF IAW the OPLAN/CONPLAN TPFDD.The supported MARFOR is also responsible for submitting a WithdrawalRelease Message for WRMSI. DC I&L (LP) approves the request with anExecution Authorization Message.

Upon approval of the execution of the War Reserve Withdrawal Plan(WRWP) , Marine Corps Logistics Command (MCLC) is responsible for thephysical movement of WRM from In-stores locations, as well as thephysical preparation and movement of assets to the designated S/APODIAW the OPLAN/CONPLAN TPFDD. If WRMSI are not on-hand at thecommencement of Withdrawal, they are considered shortfalls insustainment.

Requisitions will be released by MCLC to fill WRMR shortfalls. Assetsimmediately available will be released by MCLC for containerizationand shipment via the TPFDD process. Upon receipt of Procurementdocumentation, remaining shortfalls will be delivered by the DoD IMM

4-3

WRM Functions


Although the WRM Functions are executed separately, they are mutuallysupport.ing activi ties. This Handbook defines the specific roles andresponsibilities for the participants associated with each function.Additional stakeholders may support these activities as appropriate.This chapter addresses the execution of the Distribution function asit relates to the program.


1. Distribution

Distribution is the authorization, release, and movement of WRM assetsto a desired Sea/Aerial Port of Debarkation (S/APOD) upon request fromthe lead M.ll.RFOR and approval of HQMC in support of a specificOPLAN/CONPLAN. WRM distribution activities are initiated upon receiptof HQMC approval.

2. Wi thdrawal Process

Once the order is released and the MARFORs receive authorization, t.heyare responsible for the movement of WRMSF lAW the OPLAN/CONPLAN TPFDD.The supported MARFOR is also responsible for submitting a Wi thdraTdalRelease Message for WRMSI. DC I&L (LP) approves the request with anExecution Authorization Message.

Upon approval of the execution of the War Reserve Withdrawal Plan(WRWP), Marine Corps Logistics Command (MCLC) is responsible for thephysical movement of WRM from In-stores locations, as well as thephysical preparation and movement of assets to the designated S/APODlAW the OPLAN/CONPLAN TPFDD. If WRMSI are not on-hand at thecommencement of Withdrawal, they are considered shortfalls insustainment.

Requi::;itions will be released by MCLC to fill WRMR shortfalls. Assetsimmediately available will be released by MCLC for containerizationand shipment via the TPFDD process. Upon receipt of Procurementdocumentation, remaining shortfalls will be delivered by the DoD IMM

4-3

Distribution

or vendor directly to the designated S/APOD or DoD Activity AddressCode (AAC) via commercial or channel lift and not via the TPFDDprocess. Distribution Management Center (DMC) maintains visibilityover all assets based on the assigned Joint Chief of Staff (JCS)special project code and other tracking information.

3.Remain Behind Equipment (RBE)

RBE is the defined by the Joint Publication 1-02 (JP 1-02) Departmentof Defense Dictionary of Military and Associated Terms, as "unitequipment left by deploying forces at their bases when they deploy."

MEF Commanders, supported by the MARFOR*, are responsible for thereporting and management of RBE for the first 30 days after thedeployment of forces. The MEF Commander may coordinate with Bases,Posts, and Stations to support the management and maintenance duringthe 30 day period.

No later than 30 days following the first deployment of forces, MEF

Commanders are required to report RBE as excess to MCLC for

determination as to disposition, in accordance with policies and

procedures outlined in DoDD 4140.1, Supply Chain Materiel Management

Policy.

MCLC, according to procedures outline in DoDD 4140.1, will advise the

respective MEF Commander to: return the reported assets to wholesale

stocks, laterally redistribute the reported assets, temporarily retainthe assets in-place, and/or not return the reported assets as they are

not authorized to be returned.

' These actions DO NOT apply to Marine Forces Reserved (MARFORRES).

Distribution

or vendor directly to the designated S/APOD or 000 Activity AddressCode (AAC) via corrunercial or channel lift and not via the TPFDDprocess. Distribution Management Center (DMC) maintains visibilityover all assets based on the assigned Joint Chief of Staff (JCS)special project code and other tracking information.

3. Remain Behind Equipment (RBE)

RBE is the defined by the Joint Publication 1-02 (JP 1-02) Departmentof Defense Dictionary of Military and Associated Terms, as "unitequipment left by deploying forces at their bases when they deploy."

MEF Corrunanders, supported by the MARFOR*, are responsible for thereporting and management of RBE for the first 30 days after thedeployment of forces. The MEF Corrunander may coordinate with Bases,Posts, and Stations to support the management and maintenance duringthe 30 day period.

No later than 30 days following the first deployment of forces, MEFCorrunanders are required to report RBE as excess to MCLC fordetermination as to disposition, in accordance with policies andprocedures outlined in 0000 4140.1, Supply Chain Materiel ManagementPolicy.

MCLC, according to procedures outline in 0000 4140.1, will advise therespective MEF Corrunander to: return the reported assets to wholesalestocks, laterally redistribute the reported assets, temporarily retainthe assets in-place, and/or not return the reported assets as they arenot authorized to be returned.>I- Theslf' actions 00 NOT dpply to Marine Forces Re.served (MARFORRES).

4-4

4.Estimated timeline for Withdrawal

The notional example of the timeline for the flow of sustainment todeployed forces is depicted below by major milestones. This timelineis intended to support planning purposes only.

Actions associated with the WRM Distribution Function Actions outside the WRM Distribution Function

Release ofWARNO/EXORD

Request MCLCContainers Receives

HO ID & ContainersAdmIN CoordinateFunding LiftActions Requirements

Complete

Last Container Surface Requesting unitLoaded/ Surface Transport initiates asset

Transportation Transport Latest Transport toCoordinated initiates Arrival Forward location

CompleteEmbarkmentAt A/SPOE

CompleteDebarkationAt A/SPOD

3 12112 Days Days Days 15 Days 20 Days

Days 0 12 1517 35

30 Days

55 85

21 Days 16 Days

106 1221

Figure 4.2: Withdrawal Timeline (Notional Example)

In order to support uninterrupted flow of sustainment to deployedforces, commanders and planners must be aware of the assumptions andconstraints associated with Withdrawal process.

(--Planning is for a single MEF's worth of equipmentwith only 10% of the total requirement purchasedand on-hand at Albany/Barstow

o All administrative actionsare conducted in theminimum amount of time required (e.g. WRWPRelease Request, Execution AuthorizationMessage, etc.)

o Funding codesare available and fundingtransactions progress efficiently

o FSD's QA/QC does not find any deficiencies inthe equipment for shipment

MEFs have entire WRMRF on-hand

Program Assumptions

WRM is transported via Military Sealift Command(MSC) Shipping

o Containerization process assumes 45day

...,___

timeline with 20 trucks / 40 containers loaded perday, an augmented team, and two loaders

Program Constraints

Sustainment requirements may not meetoperational timelines due to:

- Priority amongst other DoD requirements/availability of assets

- Military Sealift Command (MSC) vs.commercial shipping

COCOM sailing times

The geographic location of destinationfrom Sea Port of Debarkation (SPOD)

- Host Nation support limitations (e.g.holidays, etc.)

Marine Corps visibility of all assets is dependentupon MCLC receipt of WRM Materiel RequestOrders (MR0s) to build Transportation ControlNumbers (TCNs)inJOPES

Figure 4.3: Withdrawal Assumptions and Constraints

4-5

4. Estimated timeline for Withdrawal

The notional example of the timeline for the flow of sustainment todeployed forces is depicted below by major milestones. This timelineis intended to support planning purposes only.

Actions associated with the WRM Distribution Function Actions outside the WRM Distribution FunctionII E II

CompleteDebarl<allonAtA/SPOD

16 Days

Surface Requesting unllTransport initiates assel

Latest Transport 10Arrlval Forward location

21 Days

SurfaceTransportInlllJ1tas

CompleteEmbarkmentAt AlSPOE

30 Days

Lasl ContainerLoaded!

TransportationCoordinated

20 Days

ContainersMCLC

ReceivesHQ 10 & Containers

Admin! CoordJnateFunding LIIIActions Raqu:lromonta

Complete

H-3h1t-------------------------------

12 Days Days Days 15 Days

~ •.

Release ofWARNOIEXORD

Days 0 12 1517 35 55 85 106 122

Figure 4.2: Withdrawal Timeline (Notional Example)

In order to support uninterrupted flow of sustainment to deployedforces, commanders and planners must be aware of the assumptions andconstraints associated with Withdrawal process.

• Sustainment requirements may not meetoperational timelines due to:

• Marine Corps visibility of all assets is dependentupon MCLC receiptofWRM Materiel RequestOrders (MROs) to build Transportation ControlNumbers (TCNS) in JOPES

- Priority amongstotherDoD requirements!availability of assets

Military Sealift Command (MSC) vs.commercial shipping

COCOM sailing times

The geographic location ofdestinationfrom Sea Port of Debarkation (SPOD)

Host Nation support limitations (e.g.holidays, etc.)

t::lannin~ i~ f~r ~ sin~le MEF':W:rth of equipmentwith only 10% of the total requirement purchasedand on-hand atAlbany/Barstow

• All administrative actions are conducted in theminimum amountoftime required (e.g. WRWPRelease Request, Execution AuthorizationMessage, etc.)

• Funding codes are available and fundingtransactions progress efficiently

FSD's QA/QC does notfind any deficiencies inthe equipmentforshipment

MEFs have entire WRMRF on-hand

• WRM is transported via Military Sealift Command(MSC) Shipping

• Containerization process assumes 45day\ timeline with 20 trucks I 40 containers loaded per~ay,an augmented tea m, and two loaders

Figure 4.3: Withdrawal Assumptions and Constraints

4-5

Distribution

The five phases that make up the Withdrawal process are: WithdrawalRelease Message Activities, Execution Authorization MessageActivities, MCLC Funding Alignment Activities, Withdrawal ExecutionPrerequisite Activities, and Withdrawal Execution Activities.

3. MCLCFunding

ArignmentActivItks

draws! I

cutionMoo

Figure 4.4: Withdrawal Process Phases

D. Withdrawal Release Message Activities

1. Description

The Withdrawal Release Message Activities phase describes theprocedures conducted to submit a request to HQMC for the release ofClass I, II, III(P), IV, VI, VII and IX WRM. Upon receipt of a WarningOrder, released by the Chairman of the Joint Chiefs of Staff (CJCS),Withdrawal execution planning is initiated. During the initialplanning stages, the CJCS releases the Execute Order grantingsupporting units the authority to execute the planned operation.Planning actions culminate in the issuance of the Withdrawal Messagefrom the supported MARFOR.

Participants in this phase are (See MCD 4400.39 for overall roles andresponsibilities) :





Department of Defense Activity Address Code Directory (DoDAAD)

Distribution

The five phases that make up the Withdrawal process are: WithdrawalRelease Message Activities, Execution Authorization MessageActivities, MCLC Funding Alignment Activities, Withdrawal ExecutionPrerequisite Activities, and Withdrawal Execution Activities.

\ ,

Figure 4.4: Withdrawal Process Phases

D. withdrawal Release Message Activities

1. Description

The Withdrawal Release Message Activities phase describes theprocedures conducted to submit a request to HQMC for the release ofClass I, II, III(P), IV, VI, VII and IX WRM. Upon receipt of a WarningOrder, released by the Chairman of the Joint Chiefs of Staff (CJCS),Withdrawal execution planning is initiated. During the initialplanning stages, the CJCS releases the Execute Order grantingsupporting units the authority to execute the planned operation.Planning actions culminate in the issuance of the Withdrawal Messagefrom the supported MARFOR.





• Department of Defense Activity Address Code Directory (DoDAAD)

4-6

:t ihut


Withdrawal ProcessKey:

Process _,Step Document

, .

Previous rn Next temN,,,i0P7," Phase

Withdrawal Release Message Activities

ors 6-(1.

c) ...1a

,.

rx0U...

ce<2

0.¡Pte.,*

OWr7r7r

!..

.

Li.tu2 s

_

4

(..) aJ cL(..) X2 1

-.System _ ,

tte;.

mr--.16.

Figure 4.5: Withdrawal Release Message Activities Process Flow Map

2. Process Flow Map

Withdrawal Process

Withdrawal Release Message Activities

l.LW~

Om....In.00::~~

System

Figure 4.5: Withdrawal Release Message Activities - Process Flow Map

4-7

Distribution


rnar.wor-

Acmttlas ¡

Receive Warning/Execute Order from JCS

Description: LPO receive the Warning/Execute Order from CJCS. TheExecute Order directs execution of an Operation Order (OPORD) orother military operation to implement a National CommandAuthority (NCA) decision. The Warning/Execute Order will beissued by authority and direction of the Secretary of Defense(SECDEF) and provides essential guidance such as the date andtime for execution, course of action, major combat forcesapproved for the operation, strategic movement planning guidance,and known logistics constraints. In a particularly time-sensitivesituation requiring an immediate response, an Execute Order maybe issued without prior formal crisis planning.

Input: Warning/Execute Order

2. Request WRWP Release Message prerequisites

Description: MARFOR (Supported) request, via Naval Message, theMEF provide critical data required for inclusion in the WRWPrelease message to ensure assets arrive at designated locationand time. This data includes Activity Address Codes (AACs), whichcontain associated SPOD and Electronic Key Management System(EKMS) account activation.

Input: Execute Order

Output: WRWP Release Message Prerequisites Request Naval Message

3. Gather Message prerequisites

Description: MEFs confirm AAC upload from the DoDAAD system, EKMSaccount activation, and identification of EKMS ResponsibleOfficer (RO).

Important Note: The SMUs must ensure the most currentTransportation Address Codes .(TAC1/TAC2) are disseminated to theIntegrated Materiel Managers (IMMs), since IMMs ship to the lastknown address.Input: WRWP Release Message Prerequisites Request Naval Message

4. Develop Withdrawal request

Description: MARFOR (Supported) create initial draft of WRWPRelease Message, pending critical input from the MEF.

Input: Execute OrderOutput: Draft WRWP Release Message

4-8

Distribution


1 . va .WarI)~rtgf,Execute Qrq

• Description: LPO receive the Warning/Execute Order from CJCS. TheExecute Order directs execution of an Operation Order (OPORD) orother military operation to implement a National CommandAuthority (NCA) decision. The Warning/Execute Order will beissued by authority and direction of the Secretary of Defense(SECDEF) and provides essential guidance such as the date andtime for execution, course of action, major combat forcesapproved for the operation, strategic movement planning guidance,and known logistics constraints. In a particularly time-sensitivesituation requiring an immediate response, an Execute Order maybe issued without prior formal crisis planning.

• Input: Warning/Execute Order

• Description: MARFOR (Supported) request, via Naval Message, theMEF provide critical data required for inclusion in the WRWPrelease message to ensure assets arrive at designated locationand time. This data includes Activity Address Codes (AACs) , whichcontain associated SPOD and Electronic Key Management System(EKMS) account activation.

• Input: Execute Order• Output: WRWP Release Message Prerequisites Request Naval Message

prereClUisites

• Description: MEFs confirm AAC upload from the DoDAAD system, EKMSaccount activation, and identification of EKMS ResponsibleOfficer (RO).

• Important Note: The SMUs must ensure the most currentTransportation Address Codes .(TACl/TAC2) are disseminated to theIntegrated Materiel Managers (IMMs) , since IMMs ship to the lastknown address.

• Input: WRWP Release Message Prerequisites Request Naval Message

··h<lz:awa1{· reques t

• Description: MARFOR (Supported) create initial draft of WRWPRelease Message, pending critical input from the MEF.

• Input: Execute Order• Output: Draft WRWP Release Message

4-8

,

5. Submit prereguisites

Description: MEF coordinate requested prerequisite informationand provide back to the MARFOR to incorporate in the WRWP ReleaseMessage.

Output: AAC; EKMS Account Activation; EKMS RO

6. Publish WRWP ReleaS!, essage.!

Description: MARFOR (Supported) incorporate prerequisiteinformation from the MEF in order to complete final WRWP ReleaseMessage and submit to LPO via Naval Message.

Input: Draft WRWP Release Message; AAC; EKMS Account ActivationOutput: WRWP Release Naval Message

Document: 'NAVMC 4000.1 Chapter 4, Example Release of WarReserve Withdrawal Plans in Support of OPLAN XXXX-XX

Figure 4.6: Withdrawal Release Message Activities Process StepDescriptions

E. Execution Authorization Message Activities

1. Description

The Execution Authorization Message Activities describe the.proceduresconducted at the HQMC level to realign funding for the release andmovement of Class I, II, III(P), IV, VI, VII and IX WRM.


Deputy Commandant Programs & Resources (P&R) Program Assessmentand Evaluation (PA&E)


Marine Corps Logistics Command (MCLC) War Reserve Planning Branch(P&R)


5. Submit prere. .. :' . '" ,':~: " ,- ~

• Description: MEF coordinate requested prerequisite informationand provide back to the MARFOR to incorporate in the WRWP ReleaseMessage.

• Output: MC; EKMS Account Activation; EKMS RO

6. Publi~B!

• Description: MARFOR (Supported) incorporate prerequisiteinformation from the MEF in order to complete final WRWP ReleaseMessage and submit to LPO via Naval Message.

• Input: Draft WRWP Release Message; MC; EKMS Account Activation• Output: WRWP Release Naval Message

,. Document:NAVMC 4000.1 - Chapter 4, Example Release of WarReserve Withdrawal Plans in Support of OPLAN xxxx-xx

Figure 4.6: Withdrawal Release Message Activities - Process StepDescript,ions

E. Execution Authorization Message Activities

1. Description

The Execution Authorization Message Activities describe the proceduresconducted at the HQMC level to realign funding for the release andmovement of Class I, II, III(P), IV, VI, VII and IX WRM.

Participants in this phase are (See Mea 4400.39 for overall roles andresponsibilities) :

• Deput.y Commandant Programs & Resources (P&R) Program Assessmentand Evaluat.ion (PA&E)


• Marine Corps Logistics Command (MCLC) War Reserve Planning Branch(P&R)

• Marine Forces (MARFORs)

4-9

Distribution

2. Process Flow Map

INiiht) w rititogessq, 1 WO ,

JAYmciii

Previ°us 9 irip ,rit UÌ Phass . System

Execution Authorization Message Activities >

oa.

en

g3p-qp,,i

_16-oes

a0 -4,10

igifiti44

,

..,.

Yes

41NX4M

C.)

-J E0 12

u.

...J.,

syae

,..L.,e..A..,

Figure 4.7: Execution Authorization Message Activities Process FlowMap


Receive WIthdrawe 4441 toplocva

Description: LPO receive WRWP Release Message from the MARFOR(Supported) which contains information essential to support therelease and movement of assets to a particular geographiclocation based on the Combatant Commander (COCOM)'sOPLAN/CONPLAN, per MCO 4400.39.

Input: WRWP Release Naval Message; MCO 4400.39

4-10

Distribution

2. Process Flow Map

Execution Authorization Message Activities

....J~o

a.Udo

Yes

Figure 4.7: Execution Authorization Message Activities - Process FlowMap


• Description: LPO receive WRWP Release Message from the MARFOR(Supported) which contains information essential to support therelease and movement of assets to a particular geographiclocation based on the Combatant Commander (COCOM)'sOPLAN/CONPLAN, per MCO 4400.39.

• Input: WRWP Release Naval Message; MCO 4400.39

4-10

1

8. Approve request?

\ 1 Mutrowal rikérikas"" f XLC\ Isms Atïffit.0.4ion Pulsar*/ ifiesse,

Ac1.112e.

Description: LPO determine whether or not to approve the WRWPrelease request.

9. PUblisb guidance to MARFORs

Description. If LPO reject the WRWP Release Message, LPO providedetailed guidance to MARFOR (Supported) on actions required priorto resubmitting in order to receive approval.

Output: Withdrawal Release Request Guidance

10. Coordinate Cla'& Class VI funding.,,

Description: LP compare the approved WRWP Release Message withWithdrawal Plan Dollar Report (See Chapter 2, Plan LevelRecomputation) . LP utilize this information to coordinate with LFto adjust and align funding for Class I WRM.Input: WRWP Release Naval Message Class I Requirement;Withdrawal Plan Dollar Report (NAVMC 4000.1 Chapter 2, PlanLevel conference)

Output: Class I Funding

"

11. Coordinate WRWR;.1Unding less Class i &

Description: LPO compare the approved WRWP Release Message withWithdrawal Plan Dollar Report (See Chapter 2, Plan LevelJRecomputation). LPO utilize this information to coordinate withPA&E to adjust and align funding for Class II, III(P), IV, VII,VIII and IX WRM.

Input: WRWP Release Naval Message Class II, III(P), IV, VII, IXRequirement; Withdrawal Plan Dollar Report (NAVMC 40_00.1Chapter 2, Plan Level Oonference); Class VIII Medical ContingencyFile (MCF) (NAVMC 4000.1- Chapter 8, Requirements Determination)Output: Class II, III(P), IV, VII, VIII and IX Funding

12. .ReceiVe WRVIP4'UO044;information códas

Description: LPO incorporate funding codes into ExecutionAuthorization Message.Input: Class I Funding; Class II, III(P), IV, VII and IX FundingOutput: Draft Execution Authorization Message

L, , ~ 1

B. Approve

• Description: LPO determine whether or not to approve the WRWPrelease request.

9. Publish guidan<::¢, ., .~;

• Description. If LPO reject the WRWP Release Message, LPO providedetailed guidance to MARFOR (Supported) on actions required priorto resubmitting in order to receive approval.

• Output: Withdrawal Release Request Guidance

10.

• Description: LP compare the approved WRWP Release Message withWithdrawal Plan Dollar Report (See Chapter 2, Plan LevelRecomputation). LP utilize this information to coordinate with LFto adjust and align funding for Class I WRM.

• Input: WRWP Release Naval Message - Class I Requirement;Withdrawal Plan Dollar Report (NAVMC 4000.1 - Chapter 2, PlanLevel conference)

• Output: Class I Funding

11. coo:tciihci

• Description: LPO compare the approved WRWP Release Message withWithdrawal Plan Dollar Report (See Chapter 2, Plan Level,Recomputation). LPO utilize this information to coordinate withPA&E to adjust and align funding for Class II, III(P), IV, VII,VIII and IX WRM.

• Input: WRWP Release Naval Message - Class II, III(P), IV, VII, IXRequirement; Withdrawal Plan Dollar Report (NAVMC 40,00.1 Chapter 2, Plan Level ~onference); Class VIII Medical ContingencyFile (MCF) (NAVMC 4000.1- Chapter 8, Requirements Determination)

• Output: Class II, III(P), IV, VII, VIII and IX Funding

12 . ' Receive

• Description: LPO incorporate funding codes into ExecutionAuthorization Message.

• Input: Class I Funding; Class II, II I (P), IV, VII and IX Funding• Output: Draft Execution Authorization Message

4-11

Distribution

\ WA:Mr.vosi Wknorawan\ UtImatsalfso

tkesaapAdMdka hitiVaests A

.,

13. Publish Withdrawal Execution Authorization Message

Description: LPO publish the Execution Authorization Message,granting the authority to release and move Class I, II, III(P),IV, VII, and IX WRM, via Naval Message.

Input: Draft Execution Authorization Message

Output: Execution Authorization Naval Message

Figure 4.8: Execution Authorization Message ActivitiesDescriptions

F. MCLC Funding Alignment Activities

1. Description

Process Step

The MCLC Funding Alignment Activities describe the proceduresconducted at MCLC to support funding alignment for the release andmovement of Class I, II, III (P),.VII and IX WRM.




MCLC Programs and Resources (P&R)MCLC Supply Management Center (SMC)



Standard Accounting, Budget and Reporting System (SABRS)

r

• Description: LPO publish the Execution Authorization Message,granting the authority to release and move Class I, II, III(P),IV, VII, and IX WRM, via Naval Message.

• Input: Draft Execution Authorization Message• Output: Execution Authorization Naval Message

Figure 4.8: Execution Authorization Message Activities - Process StepDescriptions

F. MCLC Funding Alignment Activities

1. Description

The MCLC Funding Alignment Activities describe the proceduresconducted at MCLC to support funding alignment for the release andmovement of Class I, II, III (P),VII and IX WRM.




• MCLC Programs and Resources (P&R)• MCLC Supply Management Center (SMC)


• Stock Control System (SCS)• Standard Accounting, Budget and Reporting System (SABRS)

4-12

2. Process Flow Map


P Step 1-4;6-4D°eunvent tA Ph .°us Phase

MCLC Funding Afignment Activities

06 6-() a

--,o,

o EE'l_1 a_

o ce2

w, ,

,_

o__, E0 *52 a'

1-110- a mo 101L

f...1a

0o g

.

v d..

1¢

-......

System .......... -..1,..4,,--

Figure 4.9: MCLC Funding Alignment Activities Process Flow Map


14. Coordinate for funding to support Withdrawal ekecution

Description: MCLC P&R coordinate the submission of fundingrequests required to ensure WRWP requirements are met.Input: Execution Authorization Naval Message

Output: Class II, III(P), IV, and IX Funding

4 -13

2. Process Flow Map


MCLC Funding Alignment Activities

System·

Figure 4.9: MCLC Funding Alignment Activities - Process Flow Map


14 . coo~dinlt"

\ I.""""",,",", n~.

J '*""UlQ-L0< k#ir.ki

• Description: MCLC P&R coordinate the submission of fundingrequests required to ensure WRWP requirements are met.

• Input: Execution Authorization Naval Message• Output: Class II, III(P), IV, and IX Funding

4-13

Distribution

Ny MIX = * Vitt.a.ral \n % ntreelltv %, tracuten 'Exr.ionAxamisonti Pini,11t, a t. ,

t ACUtitit60 A,P.,.. i-,

15. Notify MCSC of available funds

Description: WRPB notify MCSC of funds available in the SCS tosupport release and movement of Class VII WRM.

Input: Execution Authorization Naval Message

Output: Class VII Funding

16. Request funding for buy items ISO WRWP

Description: MCLC P&R coordinate with the Department of the Navy(DoN) Navy Working Capital Funds (NWCF) to request direct buy ofClass I, II, II.I (P), and IX WRM to fulfill the WRWPrequirements.Input: Class II, III(P), IV, and IX Funding

Output: Direct Buy Request

17. Receive funding & load

Description: MCLC P&R receive funding approval for procurementand load into SABRS.

Input: Approved Direct Buy Request

18. Provide notice to SMC of available funding

Description: MCLC P&R notify SMC of approved funding loaded intoSABRS is complete.

Output: Loaded Funding

19. Validate funds are available

Description: SMC confirm funds are available in the loan accountused to procure assets not in the Marine Corps inventory based onthe associated Memorandum of Record.Input: Loaded Funding

Output: Memorandum of Record

Figure 4.10: MCLC Funding Alignment Activities Process StepDescriptions

4-14

ibution

• Description: WRPB notify MCSC of funds available in the SCS tosupport release and movement of Class VII WRM.

• Input: Execution Authorization Naval Message• Output: Class VII Funding

• Description: MCLC P&R coordinate with the Department of the Navy(DoN) Navy Working Capital Funds (NWCF) to request direct buy ofClass I, II, III (P), and IX WRM to fulfill the WRWPrequirements.

• Input: Class II, III(P), IV, and IX Funding• Output: Direct Buy Request

• Description: MCLC P&R receive funding approval for procurementand load into SABRS.

• Input: Approved Direct Buy Request

• Description: MCLC P&R notify SMC of approved funding loaded intoSABRS is complete.

• Output: Loaded Funding

• Description: SMC confirm funds,are available in the loan accountused to procure assets not in the Marine Corps inventory based onthe associated Memorandum of Record.

• Input: Loaded Funding• Output: Memorandum of Record

Figure 4.10: MCLC Funding Alignment Activities - Process StepDescriptions

4-14

utin

G. Withdrawal Execution Prerequisite Activities

1. Description

The Withdrawal Execution Prerequisite Activities depict the proceduresconducted by MCLC to validate data for Wholesale WRM release.



MCLC Supply Management Center (SMC)

MCLC Fleet Support Division (FSD)

Other Storage DepotsIntegrated Materiel Managers(IMMs)




G. Withdrawal Execution Prerequisite Activities

1. Description

The Withdrawal Execution Prerequisite Activities depict the proceduresconducted by MCLC to validate data for Wholesale WRM release.

Participants in this phase are (See MCG 4400.39 for overall roles andresponsibilities) :


• MCLC Supply Management Center (SMC)• MCLC Fleet Support Division (FSD)

• Other Storage Depots• Integrated Materiel Managers (IMMs)


• War Reserve System (WRS)• Stock Control System (SCS)

4-15

Distribution

2. Process Flow Map

WithdráAl Ilroce:gsKElyS P7:70 Perricess Next rs.

Rose 9 Pease e;.ti, S 'Withdrawal Execution Prerequisite Activities >

2. eo

+4

Jo :ioxm

.gtiff

o -°

).

i\l' ,:,t'stil

,

aggia

* IAAlki

r'-',0

R(3 a-

,

i

,

1

1

1

T

1

1

0 2020

1

Y *teNo

1

I

1

I

I

I

1

1

+

I

1

1>

'IMMmft.

Figure 4.11: Withdrawal Execution Prerequisite Activities ProcessFlow Map

Distribution

2. Process Flow Map

No

Figure 4.11: Withdrawal Execution Prerequisite Activities - ProcessFlow Map

4-16

3.Process Step Descriptions

20. Z$ecute Wholesale,111RM Requirements

Description: WRPB release transactions via the WRS into the StockControl System (SCS), containing Wholesale Requirement data set,to SMC.

Input: Wholesale requirement (NAVMC 4000.1 Chapter 2, PlanLevel Conference)

Output: Zli Transactions

21. .Send ration/144i.sition Naval Mes0qe::tótip04,

Description: SMC send the Class I ration and Class VI HCPrequisition message to DLA via Naval Message via the (SCS).

Important Note: This represents an automated process within theSCS that does not require manual input.Input: Wholesale requirement (NAVMC 4000.1 Chapter 2, PlanLevel Conference)output: zll Transactions

' 3 ,A Jr ^+, ,tr1. elNk, ,fre, hp14,22. Determine-Marine4CoiPs IMM assets onrhand R-vallidae4A

,4sotrcing -A4T'

Description: SMC identify quantities on-hand at Marine Corps IMMsand utilize approved funding to support release of Class I, II,

III(P), IV, VII and IX WRM.Input: Zll Transactions

23. Determine location of Marine Corps assets to send MRO

Description:.SMC determine the location of on-hand Marine CorpsIMM assets (per Chapter 2, Plan Level Recomputation) and provideto WRPB to support Materiel Request Order (MR0) creation.Output: Marine Corps IMM on-hand assets; Marine Corps IMMshortfalls

24. Create MRO

Description: SMC create an MRO directing a MCLC FSD or otherstorage depots to release and ship materiel. An MRO contains aProject Code, shipping instructions, Activity Address Code (AAC),National Stock Number (NSN), Serial #, and quantity associatedwith every requisition. Once created, FSD or other storage depotsare directed to release and ship materiel via the SCS.Input: Marine Corps IMM on-hand assetsOutput: MRO

4-17


20.:,i!;

• Description: WRPB release transactions via the WRS into the StockControl System (SCS), containing Wholesale Requirement data set,to SMC.

• Input: Wholesale requirement (NAVMC 4000.1 - Chapter 2, PlanLevel Conference)

• Output: 211 Transactions

21. Se~a ra

• Description: SMC send the Class I ration and Class VI HCPrequisition message to DLA via Naval Message via the (SCS).

• Important Note: This represents an automated process within theSCS that does not require manual input.

• Input: Wholesale requirement (NAVMC 4000.1 - Chapter 2, PlanLevel Conference)

• output: 211 Transactions

• Description: SMC identify quantities on-hand at Marine Corps IMMsand utilize approved funding to support release of Class I, II,III(P), IV, VII and IX WRM.

• Input: 211 Transactions

23.

• Description:SMC determine the location of on-hand Marine CorpsIMM assets (per Chapter 2, Plan Level Recomputation) and provideto WRPB to support Materiel Request Order (MRO) creation.

• Output: Marine Corps IMM on-hand assets; Marine Corps IMMshortfalls

• Description: SMC create an MRO directing a MCLC FSD or otherstorage depots to release and ship materiel. An MRO contains aProject Code, shipping instructions, Activity Address Code (AAC),National Stock Number (NSN), Serial i, and quantity associatedwith every requisition. Once created, FSD or other storage depotsare directed to release and ship materiel via the SCS.

• Input: Marine Corps IMM on-hand assets• Output: MRO

4-17

Distribution

MOot. , I kftdrancsi

Lc. t..f4 Aommo

OttomptOto

, 25. Generate Buy Document & send requisitions to DoD IMM

Description: SMC generate procurement documents for wholesaleshortfalls which are provided to the appropriate DoD IMMs.

Important Note: Funding validation in the MCLC Funding AlignmentActivities is required before this document can be generated. SMCmust annotate requisitions with a DoD Assigned project codeassociated with the contingency to ensure FSD provide back to DMCprior to sending to DLA to ensure they are updated in the TPFDD.

Input: Marine Corps IMM shortfalls

Output: Buy Document

26. , Can requisitions be filled?

Description: DoD IMMs determine whether or not they canimmediately fill requisitions.

Input: Buy Document

Output: DoD IMM on-hand assets; DoD IMM shortfalls

27. Process requisitions for shipment

Description: DoD IMMs utilize approved funding provided in BuyDocument to process -requisitions for shipment to MCLC FSD orother storage depots.Input: DoD IMM on-hand assets

28. 'Reject and send back to SMC

Description: DoD IMMs reject requisitions which the IndustrialBase cannot support and sent back to SMC for action.Input: DoD IMM shortfalls

Output: Industrial Base shortfalls

29. Determine disposition of asset

Description: SMC determine alternative sourcing for all remainingWRM shortfalls to ensure WRWP requirements are filled.Important Note: This represents an automated process within theSCS that does not require manual input.Input: Industrial Base shortfalls

Figure 4.12: Execution Prerequisite Activities Process StepDescriptions

on

• Description: SMC generate procurement documents for wholesaleshortfalls which are provided to the appropriate 000 IMMs.

• Important Note: Funding validation in the MCLC Funding AlignmentActivities is required before this document can be generated. SMCmust annotate requisitions with a 000 Assigned project codeassociated with the contingency to ensure FSD provide back to DMCprior to sending to DLA to ensure they are updated in the TPFDD.

• Input: Marine Corps IMM shortfalls• Output: Buy Document

• Description: 000 IMMs determine whether or not they canimmediately fill requisitions.

• Input: Buy Document• Output: 000 IMM on-hand assets; 000 IMM shortfalls

• Description: 000 IMMs utilize approved funding provided in BuyDocument to process ~equisitions for shipment to MCLC FSD orother storage depots.

• Input: 000 IMM on-hand assets

• Description: 000 IMMs reject requisitions which the IndustrialBase cannot support and sent back to SMC for action.

• Input: 000 IMM shortfalls• OUtput: Industrial Base shortfalls

• Description: SMC determine alternative sourcing for all remainingWRM shortfalls to ensure WRWP requirements are filled.

• Important Note: This represents an automated process within theSCS that does not require manual input.

• Input: Industrial Base shortfallsFigure 4.12: Execution Prerequisite Activities - Process Step

Descriptions

4-18

Ili

H. Withdrawal Execution Activities

1. Description

Withdrawal Execution Activities describe the procedures Conducted byMCLC to prepare, load and package assets for shipment to therequesting unit while maintaining the Supported Commander's visibilityof assets throughout transportation.



Marine Corps Logistics Command (MCLC) Fleet Support Division(FSD)

Other Storage Depots

MCLC Distribution Management Center (DMC)Defense Logistics Agency (DLA) Storage Sites

Department of Defense (DoD) Integrated Materiel Managers (IMMs)


Marine Air-Ground Task Force War Planning System II (MAGTF II)

MAGTF Deployment Support System II (MDSS II)Joint Force Requirements Generator II (JFRG II)

Joint ,Operation Planning and Execution System (JOPES)

Integrated Booking System (IBS)

Radio Frequency Identification Tracking and Visibility (RFITV)

Global Transportation Network (GTN)

Single Mobility System (SMS)

Distribution .Standard System (DSS) MRO Shipping Tracking

H. Withdrawal Execution Activities

1. Description

Withdrawal Execution Activities describe the procedures conducted byMCLC to prepare, load and package assets for shipment to therequesting unit while maintaining the Supported Commander's visibilityof assets throughout transportation.


• Marine Forces (MARFORs)• Marine Corps Logistics Command (MCLC) Fleet Support Division

(FSD)

• Other Storage Depots• MCLC Distribution Management Center (DMC)• Defense Logistics Agency (DLA) Storage Sites• Department of Defense (000) Integrated Materiel Managers (IMMs)


• Marine Air-Ground Task Force War Planning System II (MAGTF II)

• MAGTF Deployment Support System II (MOSS II)• Joint Force Requirements Generator II (JFRG II)

• Joint Operation Planning and Execution System (JOPES)• Integrated Booking System (IBS)• Radio Frequency Identification Tracking and Visibility (RFITV)

• Global Transportation Network (GTN)• Single Mobility System (SMS)• Distribution ~tandard System (DSS) - MRO Shipping Tracking

4-19

Distribution


wmwrawali!rm

Withdrawat Execution Activities

W0u.

t got8 A 8 i

o

d 02

0^g

id4,4

S441

4--A

MO

- ...

, 'AA i,.....----,,

2_

1

,

System

=

. f.fv.a

Figure 4.13: Withdrawal Execution Activities Process Flow Map

Distribution

2. Process Flow Map

a::o

~

~"'-"ijl1':;;:~;::' tlJll-Withdrawal Execution Activities

-.'

Figure 4.13: Withdrawal Execution Activities - Process Flow Map

4-20

-ctribution


30. Conduct QC &-prepare eguipMent

Description: Based on the MRO, other storage depots conductQuality Control (QC) measures of equipment to include maintenanceinspections, warranty maintenance, and asset configuration, asrequired, to prepare equipment for shipment.Input: WRM assets

Output: QC WRM assets

Generate TINS

Description: Other storage depots generate a TransportationControl Number (TCN) for each asset. Other storage depots useDSS-MRO Shipping Tracking to assign TLNs and ship equipment.

Important Note: These TLNs do not utilize the TPFDD process.Input: QC WRM assets

Output: TLNs

32. Generate RFID Military ShIPITAblElbéVS

Description: Other storage depots generate a Radio FrequencyIdentification (RFID) shipping label and upload onto the RFITV totrack the last known location of their assets.Important Note: Since these TLNs do not utilize the TPFDDprocess, the Marine Corps does not have visibility on theseassets.

Input: TLNs

Output: RFID Tags / Military Shipment Labels

3 Register Transpokta4ion

Description: Other storage depots register assets intransportation systems. Surface transportation is registered inIBS.

Input: RFID Tags / Military Shipment LabelsOutput: Prepared & Registered Assets

[,is t bution


30. Conduct,

• Description: Based on the MRO, other storage depots conductQuality Control (QC) measures of equipment to include maintenanceinspections, warranty maintenance, and asset configuration, asrequired, to prepare equipment for shipment.

• Input: WRM assets• Output: QC WRM assets

31. Generat.

• Description: Other storage depots generate a TransportationControl Number (TCN) for each asset. Other .storage depots useDSS-MRO Shipping Tracking to assign TLNs and ship equipment.

• Important Note: These TLNs do not utilize the TPFDD process.• Input: QC WRM assets• Output: TLNs

32 . Generate

• Description: Other storage depots generate a Radio FrequencyIdentification (RFID) shipping label and upload onto the RFITV totrack the last known location of their assets.

• Important Note: Since these TLNs do not utilize the TPFDDprocess, the Marine Corps does not have visibility on theseassets.

• Input: TLNs• Output: RFID Tags / Military Shipment Labels

• Description: Other storage depots register assets intransportation systems. Surface transportation is registered inIBS.

• Input: RFID Tags / Military Shipment Labels• Output: Prepared & Registered Assets

4-21

Dilztribution

bie{x \:k Velst, Funding Esstution

Alignmsn't IAcaMtless MIN*.

34. '1Ship Containers

Description: Other storage depots ship containers.

Important Note: Containers are shipped in accordance with storgedepots process/procedures. Therefore, the assets may arrive in atheater of operations but not necessarily at the COCOM designatedSPOD/APOD.

Input: Prepared & Registered Assets

35. Receive Assets and Conduct QC

Description: FSD receive all assets required for transport andconduct Quality Control (QC) measures to ready equipment prior toshipment to include conducting maintenance inspections, warrantymaintenance, and asset configuration as required.

Important Note: All requisitions are annotated with the DoDAssigned project code by SMC to ensure FSD provide to DMC forincorporation into TPFDD prior to sending to DLA Storage Sites.Input: WRM assets

Output: QC WRM assets

keceive QC assets

Description: DLA Albany/Barstow receive QC WRM assets and preparefor containerization, loading in 20' containers.

Important Note: This step is part of a continuous cycle thatreplicates until all assets have been received and shipped(except for those assets shipped directly from vendor or DoD IMMinto the theater of operations).

Input: QC WRM assets

37. Load containers with received assets

Description: DLA Albany/Barstow load assets into 20' containersas they arrive.


Input: 20' Containers

Distribution

• Description: Other storage depots ship containers.• Important Note: Containers are shipped in accordance with storage

depots process/procedures. Therefore, the assets may arrive in atheater of operations but not necessarily at the COCOM designatedSPOD/APOD.

• Input: Prepared & Registered Assets

~;p. ~~1::$~'{l'fl Cond,u.¢t.

• Description: FSD receive all assets required for transport andconduct Quality Control (QC) measures to ready equipment prior toshipment to include conducting maintenance inspections, warrantymaintenance, and asset configuration as required.

• Important Note: All requisitions are annotated with the DoDAssigned project code by SMC to ensure FSD provide to DMC forincorporation into TPFDD prior to sending to DLA Storage Sites.

• Input: WRM assets• Output: QC WRM assets

• Description: DLA Albany/Barstow receive QC WRM assets and preparefor containerization, loading in 20' containers.

• Important Note: This step is part of a continuous cycle thatreplicates until all assets have been received and shipped(except for those assets shipped directly from vendor or DoD IMMinto the theater of operations) .

• Input: QC WRM assets

• Description: DLA Albany/Barstow load assets into 20' containersas they arrive.

• Important Note: This step is part of a continuous cycle thatreplicates until all assets have been received and shipped(except for those assets shipped directly from vendor or DoD IMMinto the theater of operations) .

• Input: 20' Containers

4-22

u t

6 V, 1116dima

WecteWA60.06,4

313. Provide Container Load Lists

Description: DLA Albany/Barstow provide the Container Load Liststo DMC


Output: Container Load Lists

39. Update MDSS II filé:

Description: DMC update MDSS II file associating each asset witha designated container from Container Load Lists to supporttracking.

Important Note: This step is part of a continuous cycle thatreplicates until all assets have been received and shipped(except for those assets shipped directly from vendor or DoD IMMinto the theater of operations).Input: container Load Lists

40. Generate T

Description: DMC generate a Transportation Control Number (TCN)for each available asset. DMC enters anticipated movement data tothe MDSS II Embarkation Workbench.Input: Container Load List

Output: TCN

Generategseend,,Militáry Shipme LakeTs_

. ,..

Description: DMC generate a Radio Frequency Identification (RFID)shipping label and upload via MDSS II onto the RFITV server andGTN which provide commanders the ability to track the last knownlocation of assets.Input: TCNOutput: RFID Tags / Military Shipment Labels

42. Affix RFID tag Libels to containers

Description: DLA Albany/Barstow affix RFID tags/labels torespective containers and/or Type 1 End Items to facilitatetracking and prepare for shipment.Input: RFID Tags / Military Shipment Labels

38.

• Description: DLA Albany/Barstow provide the Container Load Liststo DMC.

• Inportant Note: This step is part of a continuous cycle thatreplicates until all assets have been received and shipped(except for those assets shipped directly from vendor or 000 IMMinto the theater of operations) .

• Output: Container Load Lists

39. Updat~

• Description: DMC update MOSS II file associating each asset witha designated container from Container Load Lists to supporttracking.

• Important Note: This step is part of a continuous cycle thatreplicates until all assets have been received and shipped(except for those assets shipped directly from vendor or 000 IMMinto the theater of operations) .

• Input: Container Load Lists

40 . Generat.e'

• Description: DMC generate a Transportation Control Number (TCN)for each available asset. DMC enters anticipated movement data tothe MOSS II Embarkation Workbench.

• Input: Container Load List

• Output: TCN

4:1. : GenerA

• Description: DMC generate a Radio Frequency Identification (RFID)shipping label and upload via MOSS II onto the RFITV server andGTN which provide commanders the ability to track the last knownlocation of assets.

• Input: TCN• Output: RFID Tags / Military Shipment Labels

42. Affix RF

• Description: DLA Albany/Barstow affix RFID tags/labels torespective containers and/or Type 1 End Items to facilitatetracking and prepare for shipment.

• Input: RFID Tags / Military Shipment Labels

4-23

1.,#4117ArtmeralRah*.

%XIX ORtivamaal

Vann. Messaps PTo,.stftmFtotchno tlArcullorv

Maw

43. inJ6PES

Description: DMC upload MDSS II TCN files into JOPES via MAGTFII/JFRG II to provide commanders visibility of all assets andsupport tracking. The upload includes the Unit Line Number (ULN)which contains the Ready to Load for transport Date (RLD),Required Delivery Date (RDD) validated by MARFOR (Supported) andCombatant Commander (COCOM), Earliest Arrival Date (EAD) , LatestArrival Date (LAD) or latest date at destination (EAD + 6 days).

Input: MDSS II Build

Output: JOPES Upload

44. Register Surface Transport

Description: DMC registers surface transportation booking requestin IBS and coordinates with the Military Surface Deployment andDistribution Center (SDDC) to confirm booking and receive bookingnumber.

Input: MDSS II Build

Output: Surface Transport Booking #

45. 4kiAtsf7y; Supported. MARFOR

Description: DMC notify MARFOR (Supported) of assets availablefor shipment.Input: JOPES Upload; Surface Transport Booking #Output: Final Transportation Lift Request (ULN Validation)

46. 0o*44nate with COCOM for transportation and lift

Description: MARFOR (Supported) coordinate with respective COCOMfor prioritized transportation lift requirement and finalsubmission to US Transportation Command (TRANSCOM) . Uponreceiving confirmation from TRANSCOM of lift and associatedtimeline, MARFOR (Supported) coordinates with DLA to ensureassets are at SPOE at designated time/date.Input: Final Transportation Lift RequestOutput: SPOE; Date/Time

Distributir,n

• Description: DMC upload MOSS II TCN files into JOPES via MAGTFII/JFRG II to provide commanders visibility of all assets andsupport tracking. The upload includes the Unit Line Number (ULN)which contains the Ready to Load for transport Date (RLD) ,Required Delivery Date (ROD) validated by MARFOR (Supported) andCombatant Commander (COCOM), Earliest Arrival Date (EAD) , LatestArrival Date (LAD) or latest date at destination (EAD + 6 days) .

• Input: MOSS II Build• Output: JOPES Upload

44.

• Description: DMC registers surface transportation booking requestin IBS and coordinates with the Military Surface Deployment andDistribution Center (SDDC) to confirm booking and receive bookingnumber.

• Input: MOSS II Build• Output: Surface Transport Booking #

• Description: DMC notify MARFOR (Supported) of assets availab~e

for shipment.• Input: JOPES Upload; Surface Transport Booking #• Output: Final Transportation Lift Request (ULN Validation)

nd lift

• Description: MARFOR (Supported) coordinate with respective COCOMfor prioritized transportation lift requirement and finalsubmission to US Transportation Command (TRANSCOM). Uponreceiving confirmation from TRANSCOM of lift and associatedtimeline, MARFOR (Supported) coordinates with DLA to ensureassets are at SPOE at designated time/date.

• Input: Final Transportation Lift Request• Output: SPOE; Date/Time

4-24

1..WWnles; / 4 Wahlb-earalRatoom. Aataleeszathm ksecirttonklmes.ga !Assuage &ligament ) Prannazflaa.Actialifs. Act.lat. AtitAti.4 Act..

47. Ship containers

Description: DLA Albany/Barstow ship containers to SPOE by thedesignated time and date and release assets to Maritime SealiftCommand(MSC)/Commercial Shipping. Containers are shipped inaccordance with the COCOM's prescribed sailing times.

Important Note: Sailing times are dependent on geographiclocation of destination. Planning factors must be adjusted toaccount for in-transit stops for commercial shipping or if MSC isnot dedicated for WRM assets (See Estimated Timeline forWithdrawal in this chapter).Input: SPOE; Date/Time

Figure 4.14: Withdrawal Execution Activities Process StepDescriptions

• Description: DLA Albany/Barstow ship containers to SPOE by thedesignated time and date and release assets to Maritime SealiftCommand(MSC)/Commercial Shipping. Containers are shipped inaccordance with the COCOM's prescribed sailing times.

• Important Note: Sailing times are dependent on geographiclocation of destination. Planning factors must be adjusted toaccount for in-transit stops for commercial shipping or if MSC isnot dedicated for WRM assets (See Estimated Timeline forf"1i thdrml1al in this chapter) .

• Input: SPOEi Date/Time

Figure 4.14: Withdrawal Execution Activities - Process StepDescriptions

4-25

Distribution

I. Example Request for Withdrawal of Registered WRWPMessage

Provided below is an example of the message request for withdrawal ofpreviously registered WRWPs. Upon receipt, the Commandant Marine Corps(CMC) readdresses the message to the MCLC and MCSC for action. The CMCmessage provides additional guidance/funding data as required. NOTE:Content in brackets [ ] will be populated by the MARFOR when messageis released.

FM COMMARFOR[]TO CMC WASHINGTON DC/L/LP/LRCC/PR//CC USCENTCOM OR USPACOM J4 (as appropriate)

COMMARFORCOM//G-4/G-5/G-3//SUPPORTING MAGTF COMMANDERS//G-4/G-5// (as appropriate)COMMARCORLOCGCOW/M400//FMF MSC'S (as appropriate)COMMARFORRES MSC'S (as appropriate)COMMARCORSYSCOM QUANTICO VA//PS/AM//

[THIS DOCUMENT MAY BECOME CLASSIFIED WHEN COMPLETELY FILLED IN]CLASSIFICATION //[XX1//SUBJ/RELEASE OF WAR RESERVE WITHDRAWAL PLANS IN SUPPORT OF COCOMOPLAN [XXXX-XX] (as appropriate)//A. CJCS RMG [XXXXXX]B. PREVIOUS REGISTRATION MESSAGESC. [additional as appropriate]NARR/ [as necessary and may also be classified]RMKS/I. (S) IN SUPPORT OF REF A, REQUEST RELEASE OF WAR MATERIEL PREVIOUSLYREGISTERED.2. (S) REQUEST RELEASE OF WRWP IN SUPPORT OF OPLAN [XXXX] . FORPURPOSES OF RDD DEVELOPMENT, C-DAY EQUALS [XXX].3. FOLLOWING DATA PROVIDED TO EXPEDITE RELEASE OF WAR RESERVEWITHDRAWAL PLANS REGISTERED DURING DELIBERATE PLANNING CYCLE.A. PRIORITY: [XX].B. WITHDRAWAL PLANS:PLAN NR.[XXXX][Xxxx]C. TAC 2 ADDRESS (READ IN TWO COLUMNS)D. (U) SMU AAC: [XXXXXX]E. (s) EKMS: [INSERT].F. MATERIEL REQUESTED: (READ IN 7 COLUMNS)PLAN NR POS MIC COS RDD POE POD JULIAN DATEG. PER REF A ASSIGN FOLLOWING PROJECT CODE TO ALL SUPPLYTRANSACTIONS: [XX] (AS APPROPRIATE)4. REQUEST CONFIRM RECEIPT AND NOTIFY THIS HQ'S ON SHORTFALLS.5. ADDITIONAL DATA REQUIRED FOR PROCESSING TRANSACTIONS: [INPUT BYSUPPORTED MAGTF COMMANDER OR CMC]6. (U) POC IS [NAME, RANK, POSITION, DSN/SVOIP].//

4-26

Distribution

I. Example Request for Withdrawal of Registered WRWPMessage

Provided below is an example of the message request for withdrawal ofpreviously registered WRWPs. Upon receipt, the Commandant Marine Corps(CMC) readdresses the message to the MCLC and MCSC for action. The CMCmessage provides additional guidance/funding data as required. NOTE:Content in brackets [ ] will be populated by the MARFOR when messageis released.

FM COMMARFOR [ ]TO CMC WASHINGTON DC/L/LP/LRCC/PR//CC USCENTCOM OR USPACOM J4 (as appropriate)

COMMARFORCOM//G-4/G-5/G-3//SUPPORTING MAGTF COMMANDERS/IG-4/G-51/ (as appropriate)COMMARCORLOCGCOM//M40011FMF MSC'S (as appropriate)COMMARFORRES MSC'S (as appropriate)COMMARCORSYSCOM QUANTICO VAI/PS/AM//

[THIS DOCUMENT MAY BECOME CLASSIFIED WHEN COMPLETELY FILLED IN]CLASSIFICATION II[XX]//SUBJ/RELEASE OF WAR RESERVE WITHDRAWAL PLANS IN SUPPORT OF COCOMOPLAN [XXXX-XX] (as appropriate) 1/A. CJCS RMG [XXXXXX]B. PREVIOUS REGISTRATION MESSAGESC. [addi tional as appropriate]NARRI [as necessary and may also be classified]RMKSI1. (S) IN SUPPORT OF REF A, REQUEST RELEASE OF WAR MATERIEL PREVIOUSLYREGISTERED.2. (S) REQUEST RELEASE OF WRWP IN SUPPORT OF OPLAN [XXXX]. FORPURPOSES OF ROD DEVELOPMENT, C-DAY EQUALS [XXX].3. FOLLOWING DATA PROVIDED TO EXPEDITE RELEASE OF WAR RESERVEWITHDRAWAL PLANS REGISTERED DURING DELIBERATE PLANNING CYCLE.A. PRIORITY: [XX].B. WITHDRAWAL PLANS:PLAN NR.[XXXX][XXXX]C. TAC 2 ADDRESS (READ IN TWO COLUMNS)D. (U) SMU AAC: [XXXXXX]E. (s) EKMS: [INSERT].F. MATERIEL REQUESTED: (READ IN 7 COLUMNS)PLAN NR POS MIC COS ROD POE POD JULIAN DATEG. PER REF A ASSIGN FOLLOWING PROJECT CODE TO ALL SUPPLYTRANSACTIONS: [XX] (AS APPROPRIATE)4. REQUEST CONFIRM RECEIPT AND NOTIFY THIS HQ'S ON SHORTFALLS.5. ADDITIONAL DATA REQUIRED FOR PROCESSING TRANSACTIONS: [INPUT BYSUPPORTED MAGTF COMMANDER OR CMC]6. (U) POC IS [NAME, RANK, POSITION, DSN/SVOIP] .11

4-26


Management

Chapter 5


Management

Chapter 5

5-1

Management

Table of ContentsA. WRM Functions 5-3B. File Maintenance 5-4C. System Maintenance Support 5-4D. Training 5-5E. NAVMC Governance 5-5

F. CARF Updates 5-6G. CBRN Asset Reporting 5-6H. Exercise Support 5-6I. Study Support 5-6J. Change Request (CR) Form 5-7K. Quarterly Report on CBRN Assets 5-9

Table of Contents

A. WRM Functions 5-3B. File Maintenance 5-4C. System Maintenance Support 5-4D. Training 5-5E. NAVMC Governance 5-5F. CARFUpdates 5-6G. CBRN Asset Reporting 5-6H. Exercise Support 5-6I. Study support 5-6J. Change Request (CR) Form 5-7K. Quarterly Report on CBRN Assets , 5-9

5-2

A. WRM Functions

The WRM Functions are the means by which the Marine Corps provides forsufficient materiel, within the limits of acceptable risk, to sustainoperating forces from inception to the establishment of the theatersupport capability. This Handbook only addresses Class I, II, III(P),IV (lumber), VI, VII, VIII, and IX ground materiel. Furtherinformation on Classes V can be found in MCO 4400.39.

Although the WRM Functions are executed separately, they are Mutuallysupporting activities. This Handbook defines the specific roles andresponsibilities for the participants associated with each function.Additional stakeholders may support these activities as appropriate.This chapter addresses execution of the Management function as itrelates to the program.

Selection RequirementsCriteria Determination

Squrcing Positioning

;Management

Acquisition Dis riAtiltion


1. Management

Management is comprised of activities required to support.the WRMProgram outside of the program's main events. Although Marine CorpsLogistics Command is has the primary responsibility these activities,all efforts are a collaborative effort with Deputy Commandant,Installations and Logistics (DC I&L), Logistics Plans and Operations(LPO).

Participants in this function are (See MCO 4400.39 for overall rolesand responsibilities):


Marine Corps Systems Command (MCSC) Logistics Information Systems(LIS)



Technical Data Management System (TDMS)

ApplicationsProvisioning

Marine Corps Integrated Maintenance Management System (MIMMS)

Total Force Structure Management System (TFSMS)Supported Activities Supply System (SASSY)

A. WRM Functions

The WPM Functions are the means by which the Marine Corps provides forsufficient materiel, within the limits of acceptable risk, to sustainoperating forces from inception to the establishment of the theatersupport capability. This Handbook only addresses Class I, II, III (P),IV (lumber), VI, VII, VIII, and IX ground materiel. Furtherinformation on Classes V can be found in MCO 4400.39.

Although the WPM Functions are executed separately, they are mutuallysupporting activities. This Handbook defines the specific roles andresponsibilities for the participants associated with each function.Additional stakeholders may support these activities as appropriate.This chapter addresses execution of the Management function as itrelates to the program.


1 . Management

Management is comprised of activities required to support the WPMProgram outside of the program's main events. Although Marine CorpsLogistics Command is has the primary responsibility these activities,all efforts are a collaborative effort with Deputy Commandant,Installations and Logistics (DC I&L), Logistics Plans and Operations(LPO) .

Participants in this function are (See Mca 4400.39 for overall rolesand responsibilities) :


• Marine Corps Systems Command (MCSC) Logistics Information Systems(LIS)


• War Reserve System (WRS)• Technical Data Management System (TOMS)

• Applications• Provisioning• Marine Corps Integrated Maintenance Management System (MIMMS)• Total Force Structure Management System (TFSMS)• Supported Activities Supply System (SASSY)

5-3

Maoagement


Logistics Data Repository (LDR)

Global Command Supply System - Marine Corps (GCGS-MC)*

B. File Maintenance

. w `

^

Description. WRPB enable routine pulling of data from three mainframeapplications (TDMS, Provisioning and MIyMB) and one server based system(TF3GS), Note: these are run on a scheduled basis, but may be run on anas-required basis. TDMS changes are reflected in reports. These changesmay include: obsolete, replaced or substitutable National Stock Number(030s), Activity Address Code (AAC) obanges, and catalogue i000es. Thesystem generates reports which WRPB reviews for changes to criticalparts that may require analysis. Data from TFSMS is received via securefile transfer protocol (FÍP).

Description. During WRPB's analysis, WRPB may work with severalexternal organizations to support their efforts. External organizationsthat work with WRPB to determine the best solution or decisionregarding any change include: Program Managers (PMs), Item MaterielManagers (IMMs), Total Force Structure Division (TFSD), and DataMaoagemeot, Additionally, WRPB may pull sustainment/on-hand inventorydata from SASSY or GCSû-MC* and SCS, or usage data from MZMMS or GCSS-MC+ to support their analysis. If the analysis reveals that a change isrequired then WRPB generate a Change Request (CR) to LIS. Seedescription under System Maintenance Support.^ ^° appl/=°ale with GCSS-MC `°o'""^

Figure 5.2: File Maintenance

C. System Maintenance Support

Chan44

Description. WRPB initiate a CR based on a trigger, such as findingsfrom data analysis (see description under File Maintenance), changes toan interfacing system, code edits, user requests, policy changes, orConfiguration Control Board (COB) assessments. See Section G for ChangeRequest Form. Changes to the code may also be performed without COBinput by LIS on a routine basis to comply with new regulations or toimprove the systems overall performance.

• Stock Control System (SCS)• Logistics Data Repository (LDR)• Global Command Supply System - Marine Corps (GCSS-MC)*

* As applicable vith GCSS-MC roll-out

B. File Maintenance

Description. WRPB enable routine pulling of data from three mainframeapplications (TDMS, Provisioning and MIMMS) and one server based system(TFSMS). Note: these are run on a scheduled basis, but may be run on anas-required basis. TDMS changes are reflected in reports. These changesmay include: obsolete, replaced or substitutable National Stock Number(NSNs), Activity Address Code (AAC) chapges, and catalogue issues. Thesystem generates reports which WRPB reviews for changes to criticalparts that may require analysis. Data from TFSMS is received via securefile transfer protocol (FTP).

Description. During WRPB's analysis, WRPB may work with severalexternal organizations to support their efforts. External organizationsthat work with WRPB to determine the best solution or decisionregarding any change include: Program Managers (PMs), Item MaterielManagers (IMMs), Total Force Structure Division (TFSD), and DataManagement. Additionally, WRPB may pull sustainment/on-hand inventorydata from SASSY or GCSS-MC* and SCS, or usage data from MIMMS or GCSSMC* to support their analysis. If the analysis reveals that a change isrequired then WRPB generate a Change Request (CR) to LIS. Seedescription under System Maintenance Support.t As applicable with GCSS-MC roll-out

Figure 5.2: File Maintenance

C. System Maintenance Support

Description. WRPB initiate a CR based on a trigger, such as findingsfrom data analysis (see description under File Maintenance), changes toan interfacing system, code edits, user requests, policy changes, orConfiguration Control Board (CCB) assessments. See Section G for ChangeRequest Form. Changes to the code may also be performed without CCBinput by LIS on a routine basis to comply with new regulations or toimprove the systems overall performance.

5-4

"\'

System Change Test & Approval

Description. Upon receipt of CR, LIS assigns a Change ControlIdentification Number (CCID #) and priority status. LIS makes changesin the development phase. Once complete the changes will undergoiterations of testing by LIS and then by WRPB before final jointapproval and move to production.Important Note: MCSC is the system owner and responsible formaintaining the code.

Quarterly ConfigurationControl Board (CCB)

Description. During the quarterly LIS-hosted CCBs, MCSC and WRPBprovide input on CRs under review, reassessments of request priorities,and CRs transitioning into testing. Changes may be approved or rejectedbased on the CCB review.

PreserVation of-Archives

Description. MCSC archive Withdrawal data in the Logistics DataRepository (LDR) for a minimum of 7 years.

Figure 5.3: Systems Maintenance.

D. Training

Maintenance of Training:Materai41s

Description. WRPB conduct an annual review of WRS Training (MEF Leveland Plan Level Users Guides) and update as applicable.

PerSonnel Training ,

Description. WPRB serves as Point of Contact (POC) for collectedCertificates of Training Completion submitted in advance of the MEFLevel Annual Recomputation Conference and the Plan Level Conference.

Figure 5.4: Training

E. NAVMC Governance

Ongoing Governance of NAVMC 4000:1

Description. WRPB ensures that any programmatic changes affecting thisNAVMC for (e.g., updates to processes, forms or templates) arereflected in updates to NAVMC content. Additionally, WRPB recordssuggestions for process improvements proposed by end users andevaluates them for accuracy and validity. Major changes to processflows will be addressed at the Annual Review Meeting.

Description. Upon receipt of CR, LIS assigns a Change ControlIdentification Number (CCID #) and priority status. LIS makes changesin the development phase. Once complete the changes will undergoiterations of testing by LIS and then by WRPB before final jointapproval and move to production.nnportant Note: MCSC is the system owner and responsible formaintaining the code.

Quarte!t:1.y con~'

Description. During the quarterly LIS-hosted CCBs, MCSC and WRPBprovide input on eRs under review, reassessments of request priorities,and CRs transitioning into testing. Changes may be approved or rejectedbased on the CCB review.

Preservation of ..... Ai:Description. MCSC archive Withdrawal data in the Logistics DataRepository (LOR) for a minimum of 7 years.

Figure 5.3: Systems Maintenance

D. Training

Maintenance of

Description. WRPB conduct an annual review of WRS Training (MEF Leveland Plan Level Users Guides) and update as applicable.

Personnel TraiDescription. WPRB serves as Point of Contact (POC) for collectedCertificates of Training Completion submitted in advance of the MEFLevel Annual Recomputation Conference and the Plan Level Conference.

Figure 5.4: Training

E. NAVMC Governance

On-going GOvernan9~ 4000.1====--====~===--'"

Description. WRPB ensures that any programmatic changes affecting thisNAVMC for (e.g., updates to processes, forms or templates) arereflected in updates to NAVMC content. Additionally, WRPB recordssuggestions for process improvements proposed by end users andevaluates them for accuracy and validity. Major changes to processflows will be addressed at the Annual Review Meeting.

5-5

gE,ment

Eupport APhual Review of NAVMC 4000.1

Description. WRPB supports LPO's annual review of NAVMC 4000.1 byconducting a review of relevant portions of the NAVMC and participatingin the Annual Review Meeting, per Chapter 10.

Figure 5.5: NAVMC Governance

F. CARF Updates

New Item cpt.F Deteimination

Description. As new items are introduced into the inventory, MCLCProgram Support Center (PSC) coordinate with Marine Corps SystemsCommand (MSCS) to ensure that CARF rates are calculated and admittedinto the WRS.

Figure 5.6: CARF Updates

G. CBRN Asset Reporting

AssetQuarterly¡Aepoiting

Description. Provide PM-CSE with quarterly reports of CBRN assetmateriel status (1-AW Section K report format, Figure 5.11) to supportthe DoD requirement for quarterly reports to Congress on Chemical andBiological Defense (CBD) Equipment.


H. Exercise Support

-

Mock Withdrawal ip Test Environment

Description. Once all database files have been copied into a testenvironment, WRPB execute the Withdrawal plans. Appropriatetransactions are released to SCS, SASSY or GCSS-MC* and other systems.WRPB and the MARFORs, as required, simulate capabilities of thesystem(s) to support operational planning for up to 99 plans per MAGTF-UNIT.

' As applicable with GCSS-MC roll-out

Figure 5.8:

I. Study Support

Exercise Support

Review & Validation

Description. WPRB is responsible for supporting ongoing LPO studies andserving as subject matter experts in the review and validation of finalproducts.

Figure 5.9: Study Support

5-6

Description. WRPB supports LPO's annual review of NAVMC 4000.1 byconducting a review of relevant portions of the NAVMC and participatingin the Annual Review Meeting, per Chapter 10.

Figure 5.5: NAVMC Governance

F. CARF Updates

D~scription. As new items are introduced into the inventory, MCLCProgram Support Center (PSC) coordinate with Marine Corps SystemsCommand (MSCS) to ensure that CARF rates are calculated and admittedinto the WRS.


G. CBRN Asset Reporting

Description. Provide PM-CSE with quarterly reports of CBRN assetmateriel status (JAW Section K report format, Figure 5.11) to supportthe DoD requirement for quarterly reports to Congress on Chemical andBiological Defense (CBD) Equipment.


H. Exercise support

Description. Once all database files have been copied into a testenvironment, WRPB execute the Withdrawal plans. Appropriatetransactions are released to SCS, SASSY or GCSS-MC* and other systems.WRPB and the MARFORs, as required, simulate capabilities of thesystem(s) to support operational planning for up to 99 plans per MAGTFUNIT.

~. As dpplicable with GCSS-MC roll-out

Figure 5.8: Exercise Support

I. study Support

Description. WPRB is responsible for supporting ongoing LPO studies andserving as subject matter experts in the review and validation of finalproducts.

Figure 5.9: Study Support

5-6

Mailagement.

J. Change Request (CR) Form

Chan e Request Number: XXXX-S-YYMMDD-AProject (System) name: <SYSTEM>Date Raised: <dd-mmm-yy>Date Resolution Required: <dd-mmm-yy>Functional Area: <Block 1, Bridge, Legacy,etc.>

Change Type:III Perfective Adaptive Corrective

Change Affects: (Check all that apply)E Software E Documentation0 Other:

Customer Request? (Check one) :Yes M No

Requested by (Customer): <POC info>Prepared by (Implementer): <POC info>

.

Priority: (Chek one)M 1 2 III 3 III 4 5

c A

u.9m

Category: (Check one)A MB c

Risk Level: (Check one)

ElmoED Madura

Elto..

High M Medium II Low

Details of Change: <State the details as to what specifically is required to bedone/implemented regarding the/these proposed change(s)>

Justification for Change: <State the current justification and gap that is requiringthis/these proposed change(s)>

Scope of Work: <State if approval, what will affect work products are affected, whatresource assignments, requirements, and schedule impacts will occur due to this scope ofwork>

Impact of Change: <State the Impact to cost (total LOE for this complete change request andall associated work identified by the impact analysis, schedule (total LOE for thiscomplete change request (all line items broken out) & resources (resource loading ofschedule to gauge impact) , and associated work>

4

Impact if Not Approved: <State the impact if change not approved. Any alternatives forfulfilling requirement? >

Technical Risks: <State any technical or functional risks associated with the change>

Investigation and Findings: <State the current investigation and finding notes related tothis/these proposed change(s)>

Ivl2n2qernent

J. Change Request (CR) Form

Chanqe Request Number: XXXX-S-YYMMDD-AProject (System) name: <SYSTEM> Customer Request? (Check one) :

:~Date Raised: <dd-mmm-yy> 0 Yes 0 NoDate Resolution Required: <dd-mmm-yy> Requested by (Customer) : <POC info>

':1=Functional Area: <Block I, Bridge, Legacy, Prepared by (Implementer) : <POC info>etc.>

Priority: (Check one) - -c ..

Change Type: 0 1 0 ~ 0 3 0 4 0 5 "-'-0 Perfective 0 Adaptive 0 Corrective Category: (Check one)

EJ0 A 0 B 0 C 0 .........Change Affects: (Check all that apply) Risk Level: (Check one) lEI .....

0 Software 0 Documentation 0 High 0 Medium 0 Low0 Other:Details of Change: <State the details as to what specifically is required to bedone/implemented regarding the/these proposed change(s»

Justification for Change: <State the current justification and gap that is requiringthis/these proposed change(s)>

Scope of Work: <State if approval, what will affect work products are affected, whatresource assignments, requirements, and schedule impacts will occur due to this scope ofwork>

Impact of Change: <State the impact to cost (tota~ LOE for thi.s comp~ete change request andall associated work identified by the impact analysis, schedule (total LeE for thiscomplete change request (all line items broken out) & resources (resource loading ofschedule to gauge impact) , and associated work>

Impact if Not Approved: <State the impact if change not approved. Any alternatives forfulfilling requirement? >

Technical Risks: <State any technical or functional risks associated with the change>

Investigation and Findings: <State the current investigation and finding notes related tothis/these proposed change(s»

5-7

Management

CCB <Board Name> Recommendation:

0 Agreed - Approved with specific changes - services associated with the change will notcommence until all specified changes have been accomplished

1)

2)

0 Agreed - Approved as Stated

0 Agreed - Reviewed by GCSS-MC IA and contains no impacts to Security Architecture orAccreditation noted.

0 Deferred - (Next Review Date:) <dd-mm-yy>

E Rejected - Disapproved for following reasons

1)

2)

Recommendation acknowledged by: (CCB <Board Name>)(Date)

Figure 5.10: CR Form

Management

CCB <Board Name> Reoommendation:

[] Agreed - Approved with speoifio changes - servioes associated with the change will notcommence until all specified changes have been acoomplished

1)

2)

[] Agreed - Approved as Stated

[] Agreed - Reviewed by GCSS-MC IA and contains no impacts to Security Arohitecture orAccreditation noted.

[] Deferred - (Next Review Date: ) <dd-mm-yy>

[] Rejeoted - Disapproved for following reasons

1)

2)

Recommendation acknowledged by: (CCB <Board Name»(Date)

Flgure 5.10: CR Form

5-8

M.,

K. Quarterly Report on CBRN Assets

The following data required for inclusion in the MCLC quarterly reportto PM-CSE is based on the Joint Total Asset Visibility Reporting

Warehouse (JTAVRW) Roll-up File Layout.

Column Name- ,

Desoription,

QThe letter 'Q' indicating it's an authorizedquantity record

NSN National Stock Number of the asset

Quantity Authorized quantity for the NSN

S The letter 'S' indicating it's a Stock record

Lot Number Lot number of the asset

Contract Number Contract number of the asset

DOM Date of Manufacture (in format yyyymmdd)

DOE Expiration Date (in format yyyymmdd)

Total Quantity Total count of these type of assets

Issued Quantity Count of these type of assets that are issued

Unserviceable Reason

MICAS allows the user to specify a reason whyan asset is unserviceable if the DOM, lot,and contract number all indicate it'ssupposed to be good (such as Damaged)

Condition Code The standard DoD condition code of the asset

Location Type'D' if the location is deployed, '0' if thelocation is on-station. If left blank, willbe loaded to the 'NOT APPLICABLE' location

Figure 5.11 Quarterly Report on CBRN Assets

Additional infOrmation on data entry format and codes is located athttps://jtavrw.ria.army.mil.

K. Quarterly Report on CBRN Assets

The following data required for inclusion in the MCLC quarterly reportto PM-CSE is based on the Joint Total Asset Visibility ReportingWarehouse (JTAVRW) Roll-up File Layout.

Q

NSN

Quantity

S

Lot Number

Contract Number

DOM

DOE

Total Quantity

Issued Quantity

Unserviceable Reason

Condition Code

Location Type

Figure 5.11

The letter 'Q' indicating it's an authorizedquantity record

National Stock Number of the asset

Authorized quantity for the NSN

The letter '5' indicating it's a Stock record

Lot number of the asset

Contract nlmmer of the asset

Date of Manufacture (in format yyyymmdd)

Expiration Date (in format yyyymmdd)

Total count of these type of assets

Count of these type of assets that are issued

MICAS allows the user to specify a reason whyan asset is unserviceable if the DOM, lot,and contract number all indicate it'ssupposed to be good (such as Damaged)

The standard DoD condition code of the asset

'0' if the location is deployed, '0' if thelocation is on-station. If left blank, willbe loaded to the 'NOT APPLICABLE' location

Quarterly Report on CBRN Assets

Additional information on data entry format and codes is located athttps://jtavrw.ria.army.mil.

5-9

MEF Level Users Guide


WRS Training:MEF Level Users Guide

Chapter 6

1'1EF Level Users r';uide


WRS Training:MEF Level Users Guide

Chapter 6

6-1

NPF u s Guide

Table of Contents

General information 6-3A. Helpful Hints 6-3B. MEF Level Processing Menu 6-4C. MEF Level Data Entry Menu 6-6D. MAGTF Unit Data Entry 6-6E. MEF Data Entry Menu Plan Data Entry 6-8F. Days of Supply Data MEF Level 6-10G. Item Designator Number Data Entry 6-12H. Certificate of Training Completion 6-13

Table of Contents

General information 6-3A. Helpful Hints 6-3B. MEF Level Processing Menu 6-4C. MEF Level Data Entry Menu 6-6D. MAGTF Unit Data Entry 6-6E. MEF Data Entry Menu - Plan Data Entry 6-8F. Days of Supply Data - MEF Level 6-10G. Item Designator Number Data Entry 6-12H. Certificate of Training Completion 6-13

6-2


A. General information

1. Training Overview

There are three training requirements for the War Reserve Materiel(WRM) Program users. The first training requirement is on the use ofthe War Reserve System (WRS) . The resource for this training can befound in UM 4400-185 WRS Users Manual.

The second training requirement is for users participating in the MEFLevel Conference. This chapter provides step by step guidance on theprocedures to enter MEF Level parameter data in the WRS in order todetermine the War Reserve Materiel Requirement (WRMR).

The third training requirement is for users participating in the PlanLevel Conference. The resource for this training is the NAVMC 4000.1Chapter 7 WRS Training: WRS Plan Level Users Guide. Chapter 7provides step by step procedures to assist MEFs in entering planparameter data for the development or updating of War ReserveWithdrawal Plans (WRWP) in support of specific missions andcontingency plans.

B. Helpful Hints

On-line User'Mailual FI

Fl will access the on-line user's manual. Press Fl to automaticallyenter that portion of the user's manual that addresses the currentscreen or portion of the system currently being accessed.

A430,0,16

iS:43:48

ASPICAMPS

mAn RESERvE smWE LEW+. PROCESST

1. AI LEAEL ZATA2 41 *AfAtATE3. 4EY:Tii AtEtrY scr 4E

4 L i-C444441 4i,44

S %ASV* PA TFArACE 41E6ko

6. :41.1"E tiEft 0101c,t1

1. 4E!A:L 41,E4

S!!'l WSW1042

'..7.4,11 AIWA

Figure 6.1: Online Users Manual WRS Screen Capture


A. General information

1. Training Overview

There are three training requirements for the War Reserve Materiel(WRM) Program users. The first training requirement is on the use ofthe War Reserve System (WRS). The resource for this training can befound in UM 4400-185 WRS Users Manual.

The second training requirement is for users participating in the MEFLevel Conference. This chapter provides step by step guidance on theprocedures to enter MEF Level parameter data in the WRS in order todetermine the War Reserve Materiel Requirement (WRMR).

The third training requirement is for users participating in the PlanLevel Conference. The resource for this training is the NAVMC 4000.1Chapter 7 - WRS Training: WRS Plan Level Users Guide. Chapter 7provides step by step procedures to assist MEFs in entering planparameter data for the development or updating of War ReserveWithdrawal Plans (WRWP) in support of specific missions andcontingency plans.

B. Helpful Hints

F1 will access the on-line user's manual. Press F1 to automaticallyenter that portion of the user's manual that addresses the currentscreen or portion of the system currently being accessed.

Figure 6.1: Online Users Manual - WRS Screen Capture

6-3

s Guid

Question Mark (?) Help<

Tab to the beginning of a field, type "?" and press "ENTER". A "HelpScreen" will appear explaining the field and/or the valid values youcan choose from the selected field..Anytime a value is entered that thesystem considers incorrect, the system provides an error number andmessage at the top of the screen.

Figure 6.2: Helpful Hints Descriptions

R43GOR2.e WAR RESERVE SYSTEM SI. ROW(17:14:12 NAN mEWU 01122Y,RONEWS «c(cmciRESTRICTED USEm/I)I>)) USER ID. D0G444

DIRECTIONS. Entr aptFriTer-PEiPEZ--

NUR IT

1, MEE LEVEL P MESSING MENU

2. PLAN LEVEL PROCESSING REM3. ANOLESALE PROCESSING NENo

4. DEPLOYMENT OPT PEG GENERATOR Kitt.

5. SYSTEM MAINTENANCE MENU

. CONTINUE RAEVIODS PROCESSING

OP-314

proms ENTER or antes appropriate PF-Wi

Figure 6.3: Question Mark (?) Help WRS Screen Capture

C. MEF Level Processing Menu

F9 Unit

Use F9 to ensure the Unit and Plan Number of the plan intended to beupdated is in the Unit/Plan fields on the lower portion of the screen.

Select the unit by pressing the F9 key and entering an "X" beside theappropriate unit.

ME Leve Users Guide

Questiori.·Mar

Tab to the beginning of a field, type "?U and press "ENTERu• A "Help

Screen u will appear explaining the field and/or the valid values youcan choose from the selected field."Anytime a value is entered that thesystem considers incorrect, the system provides an error number andmessage at the top of the screen.

Figure 6.2: Helpful Hints Descriptions

Figure 6.3: Question Mark (?) Help - WRS Screen Capture

C. MEF Level Processing Menu

F9 - Unit .' . '.

Use F9 to ensure the Unit and Planupdated is in the Unit/Plan fields

Number of the plan intended to beon the lower portion of the screen.

Select the unit by pressing the F9 key and entering an "XU beside theappropriate unit.

6-4

MFF Level Users Guide

A43OOPiOtS:445:r5

AORCSNRS

i4AA Alli.LAiE MIER

mEr LEVEL PROCESSING RENG..4,4.4c.4.AESTAIOTEO ViEsssolo..s3,*

4, 4430MMO.

0942,0'USER ID- AOAN04

1. OTT tIVEL DATA ENTNT MONV

2. ItiOV/AtIMITIN COMPUTATION (MATCMI

3. At31141;MODITY REF REQUIREMENT%

O. W:tmONANAL PION IRATCNi..... ......... ............. ............ s

MID ALtas ro4 man uNIT Di 10102

MAOTT V 22

O3 4II ft*f

1410100,,tlirrPf. Soltet vajp, PV4 rue oR Pf.it TO EXIT PH,

oftt 4. ....... .... , .. . . SW.CO

Figure 6.4: MEF Level Processing Menu WRS Screen Capture

Selection Option 1 from the menu and press the enter key to gain entryinto the WRS for the MEF Level Data Entry Screen.Important Note: Press "enter" at the end of every screen where data isinput or changed to ensure data is saved.

Figure 6.5: MEF Level Processing Menu Descriptions

M3C3,'1)

*5-441;it

MACAWS

NAM ki 1,v , ,

MAIN MENUt.t.o.4*.ur.401STAICTIO

1 r N1 rY'. Ir Y.rg

2 , .AN

W4(4BIA,..-4 UTPIOVAINT 4 4V4t44100 MTAV

5 SvIritt RATATINAR4t. 0(NQ

A CONTINUE Pefil5U5 MUMitili!a4

orr:csa

4434400,

0111/22n1.

U144 le- A0A0104

leFCTIONS tot r **tie* press ENTER or pre*. appropriate PIFArryRter P11.--P42 Pr3 PF4 rfv, +90 PH 10 Pf0 0 Prit prI2

HtLP rtit eMICH

Figure 6.6: Main Menu WRS Screen Capture


Figure 6.4: MEF Level Processing Menu - WRS Screen Capture

Selection Option 1 from the menu and press the enter key to gain entryinto the WRS for the MEF Level Data Entry Screen.Important Note: Press "enter" at the end of every screen where data i~;

input or changed to ensure data is saved.Figure 6.5: MEF Level Processing Menu Descriptions

Figure 6.6: Main Menu - WRS Screen Capture

6-5

MEJ Gu de

D. MEF Level Data Entry Menu

Option 1

Select Option 1 from the menu and press the enter key

Figure 6.7: MEF Level Data Entry Menu Descriptions

MA MERV( MOmu LEVU PROCUMMO Ntwu

USTRICTIED USE7.24.1.44,.*10,

1. Vt rn i* r

2 PtOolArmAN tV CIMTOM (Sortp)1 Pfv:CMAOSTro MU 'IMUCtSTS4 LOA0 rifIM20A0A1. PLAM MATCH)S. SASSY IMIrPTACr MfS. DE:Utt Ork P.AA ISATCm1

ITTTAlt, 414' tfq, ACPCIA*S 41344

MAOrt SA:- ,1 'AU

A43044

490,2v;,

430% :17z ADANNI

F1A14 C12; rv 12 AfCar.

ENTEA or press oopropriACA Pr PAPPrS PF6 Prr Pve rito 1117

siec,

Figure 6.8: MEF Level Data Entry Menu WRS Screen Capture

E. MAGTF Unit Data Entry

Option 1

Selection Option 1 from the menu and press the enter key. Update theParameter Data as required and press "enter" to save the data andadvance to the next screen.Important Note: MAGTF Unit, Plan Number'and Description of Plan cannotbe changed on this screen. MAGTF Unit defaults to the respective MEF.Plan Number defaults to the Plan Number,of the respective MEF (i.e.0100 for I MEF).

NEF Level sers Gu

D. MEF Level Data Entry Menu

Option 1

Select Option 1 from the menu and press the enter key

Figure 6.7: MEF Level Data Entry Menu Descriptions

Figure 6.8: MEF Level Data Entry Menu - WRS Screen Capture

E. MAGTF Unit Data Entry

press the enter key. Update the"enter" to save the data and

I

Number'and Description of Plan cannotUnit defaults to the respective MEF.Number,of the respective MEF (i.e.

I

Option 1

Selection Option 1 from the menu andParameter Data as required and pressadvance to the next screen.Important Note: MAGTF Unit, Planbe changed on this screen. MAGTFPlan Number defaults to the Plan0100 for I MEF).

6-6


R43004517:1200A-0140NRS

wola RESERVE SYSTEM

MAG1F UNIT DATA ENTRY

44(MEE:t<RESTRICTED USE>>>>>>>2)2

SI, R430011-

01/22/0

USER ID, 00G444

HAr,TF CN:1 02 It REF

PLAN C200 PLAN 13 rY G4

PAC

RAC MAINTENANCE.-- , .....RFPRIA ISSUE POINT.PESUPPLY DELAY TIME.-- . .

DEmAND FACT04......... .....SAvErf LEVEL FACTOR. :

ORDER SNIP TIME rACTOA

HAvIIMAt SUSTAINING SUPOLv PERIOD:

EARAZT FAISTINC DATA 4DA THIS NAGTF UNIT AS REOUIREG

DIRECTIONS: Entor doto end pr.** ENTER or pros* opproprist PF-komErt,,,-PF1,---PE2-.443---PV4---PFS.--Afe---Pfl---Pf8---Pf9.--PPIGAVIIOf12--

WELP MAIO MT MENU CURR OLD SOTEN

09/,

Figure 6.9: MAGTF Unit Data Entry WRS Screen Capture

Regional Activity (RAC) Inirentory ,

WRS uses this code to determine which SASSY or GCSS-MC* (SMU RUC)information is applicable to the respective MEF.

. As applicable with GCSS-MC roll-out

Regional' ACtivity (RAC) Maintenance

WRS uses this code to determine which MIMMS information is applicableto the respective MEF.

Repair Issue Point (RIP)

The Activity Code used by the WRS to determine which RIP is applicableto the respective MEF.

Resnpply Delay Tite

The input data used to indicate the time between when a MAGTF lands inthe objective area and when the first resupply requisitions aresubmitted or when the first repair action begins. The time generallybegins on the 46th day of the operation.Important Note: The field defaults to 45 days.

Demand Factor

A factor used to increase the percentage of the peacetime demand to theexpected tempo of combat. The peacetime demand factor is set by SASSYor GCSS-MC*.' As applicable with GCSS-MC roll-out

Important Note: The system default is 100% (1.0000). A 1.5000 DemandFactor represents 150% of the peacetime usage.

6-7


Figure 6.9: MAGTF Unit Data Entry - WRS Screen Capture

WRS uses this code to determine which SASSY or GCSS-MC* (SMU RUC)information is applicable to the respective MEF .

• As dpplicdble with GCSS-MC roll-out

WRS uses this code to determineto the respective MEF.

applicable

R.~I?~:l-The Activity Code used by the WRS to determine which RIP is applicableto the respective MEF.

The input data used to indicate the time between when a MAGTF lands inthe objective area and when the first resupply requisitions aresubmitted or when the first repair action begins. The time generallybegins on the 46 th day of the operation.Important Note: The field defaults to 45 days.

A factor used to increase the percentage of the peacetime demand to theexpected tempo of combat. The peacetime demand factor is set by SASSYor GCSS-MC*., As dpplicdble with GCSS-MC roll-out

Important Note: The system default is 100% (1.0000). A 1.5000 DemandFactor represents 150% of the peacetime usage.

6-7

Useit's Guide

Factor

1.' 17 77E' c't t 07- 7

rA a:- eat er nitt tnir't y A e v e " ir

,nyntem ielait r. i, A 1..',1'0U Safety

Let-, '.-¡" Inctea.se .7atety Iew,n,_ an asdtiatlunal

_ t

7:2r Ship Factor

I. -r1 (.,-a.et reu,s'e t 01_ lett <an h IN rri t trte

I.: ftnnt,Altlen in the tetrint Tblt. Tnn in'tattettme Uemlnit'ns t tn,'AzSY IWA:3S-M74

Tne nyt trn cktu1t is Int-t :. A ctt,ier

F.Infcr wid inclase the 1"eanetime fiftety ;.evel an aci(tf

Maximum Sustaining Surply Period

7te :n.mtnei t, th1,- t:e r cart-lent syl7t: f.nm Hie b,:evitus -ntIneeti

t 1 nThel- -1 lay: Ini-endel "

: MAta`rE Cat a Ent. ittn' t"

F. MEF Data Entry Menu - Plan Data Entry

MAGTF Unit

L' , I''flIIti the MEF as t':,:a.uted with , '2.7npn-!fl.ve

r d.17 sy:tem aatùmattnally detaul tu the nhmL.er ni tnele MEF.

Plan

7nn !:-.¡la,n-. the Plan n(ur.Let ign,,,a 7, tne :;:tenlf 2, .7 Y.EF In

t_nn ne i . tne (.1",p(t_t tuna_tv t,, ):" 4C1=ST

FA,IN le: f-EnA)MP

Tt may be n,erul tu in,:"Iin:e the :late in theif.

Temperature Zone

.rne fin( t I ehete ;nu iaentlfy the ent"11:,nmen;--11 cen,nitrone ( t tnnIn. ln » p: It: . efte,:tt hnw ttir y,Jfem nnnmpute:n

nn'Ll 17' ." an '1 s-'1,,iSZ 1 i t r ;rt17, I= 7'1 11 -)1

Y3:7!7. At tlet- MEF Le-el thi_ ma::

Users CD

F.

6-8

department of the navy oepartment of the … 4000.1_1.pdf · oepartment of the navy headquarters...

Documents