Army Regulation 5–13

Management

Total Army
Munitions
Requirements
Process and
Prioritization
System

Headquarters
Department of the Army
Washington, DC
17 December 2009

UNCLASSIFIED
 SUMMARY of CHANGE
AR 5–13
Total Army Munitions Requirements Process and Prioritization System

This major revision, dated 17 December 2009--

o Changes the name of the regulation from Training Ammunition Management to

Total Army Munitions Requirements Process and Prioritization System (cover).

o Assigns Army Staff, Army Command, Army Service Component Command, and Direct
Reporting Unit responsibilities within the prioritization process (para 1-
5).

o Establishes policy related to the integration of Army munitions management

functions and the role of the DCS, G-3/5/7 munitions management office in
those processes (para 1-5i).

o Updates time lines and annual actions required by training ammunition

managers (paras 2-1d, 2-1h, 2-4o, 2-4p(1)(d), 2-4p(2)(c)).

o Establishes policy related to war reserve and operational munitions

requirements and test munitions (paras 2-2 and 2-3).

o Updates training ammunition management policy related requirements

determination, prioritization, and forecasts of training munitions (para 2-
4).

o Establishes policy for deployed, mobilized, and deploying unit training

requirements (para 2-4q).

o Outlines programming and budgeting actions governing training ammunition

(para 3-4).

o Revises the system description and characteristics of the Total Ammunition

Management Information System (para 3-5).

o Makes administrative changes (throughout).

Headquarters *Army Regulation 5–13
Department of the Army
Washington, DC
17 December 2009 Effective 17 January 2010

Management

Total Army Munitions Requirements Process and Prioritization System

Deputy Chief of Staff, G–3/5/7. The pro- Staff, G–3/5/7, 450 Army Pentagon
ponent has the authority to approve ex- (DAMO–TRA), Washington, DC
ceptions or waivers to this regulation that 20310–0450.
are consistent with controlling law and
regulations. The proponent may delegate Committee Continuance Approval.
this approval authority, in writing, to a The Department of the Army committee
division chief within the proponent management official concurs in the estab-
agency or its direct reporting unit or field lishment and/or continuance of the com-
operating agency, in the grade of colonel mittee(s) outlined herein in accordance
or the civilian equivalent. Activities may with AR 15–1. Army Regulation 15–1 re-
request a waiver to this regulation by pro- quires the proponent to justify establish-
viding justification that includes a full ing/continuing committee(s), coordinate
analysis of the expected benefits and must draft publications, and coordinate changes
include formal review by the activity’s in committee status with the Department
senior legal officer. All waiver requests of the Army Committee Management Of-
will be endorsed by the commander or
fice (AARP-ZA), 2511 Jefferson Davis
History. This publication is a major senior leader of the requesting activity
and forwarded through higher headquar- Highway, Taylor Building, 13th Floor,
revision. Arlington, VA 22202-3926. Further, if it
ters to the policy proponent. Refer to AR
Summary. This regulation prescribes 25-30 for specific guidance. is determined that an established “group”
policies governing war reserve, operation- identified within this regulation, later
al, training, and test munitions manage- Army management control process. takes on the characteristics of a commit-
ment and operating procedures for the This regulation contains management con- tee, the proponent will follow all AR
Total Ammunition Management Informa- trol provisions in accordance with AR
15–1 requirements for establishing and
tion System. 11–2, but it does not identify key manage-
ment controls that must be evaluated. continuing the group as a committee.
Applicability. This regulation applies to
the Active Army, the Army National Supplementation. Supplementation of Distribution. This regulation is available
Guard/Army National Guard of the United this regulation and establishment of com- in electronic media only and is intended
States, and the U.S. Army Reserve, unless mand and local forms are prohibited with- for command levels C, D, and E for the
otherwise stated. It also applies to the out prior approval from the Deputy Chief Active Army, Army National Guard/
U.S. Army Reserve Officer Training of Staff, G–3/5/7, 450 Army Pentagon Army National Guard of the United
Corps and the National Defense Cadet (DAMO–TRA), Washington, DC States, and the U.S. Army Reserve.
Corps. It applies during peacetime and 20310–0450.
during partial or full mobilization. Suggested improvements. Users are
Proponent and exception authority. invited to send comments and suggested
The proponent of this regulation is the improvements on DA Form 2028 (Recom-
mended Changes to Publications and
Blank Forms) directly to Deputy Chief of

Contents (Listed by paragraph and page number)

Chapter 1
Introduction, page 1
Purpose • 1–1, page 1
References • 1–2, page 1
Explanations of abbreviations and terms • 1–3, page 1
Key operational munitions management functions • 1–4, page 1

*This regulation supersedes AR 5–13, dated 1 March 2005.

AR 5–13 • 17 December 2009 i

UNCLASSIFIED
Contents—Continued

Responsibilities • 1–5, page 1

Chapter 2
Army Munitions Requirements Process, page 6
Overview • 2–1, page 6
War reserve and operational munitions requirements • 2–2, page 7
Test requirements • 2–3, page 9
Training requirements • 2–4, page 10
Stockage objectives • 2–5, page 12

Chapter 3
Prioritization and Synchronization of Support to Approved Requirements, page 13
Overview • 3–1, page 13
Prioritization of approved munitions requirements • 3–2, page 13
Integration and synchronization of Army munitions management • 3–3, page 14
Programming and budgeting • 3–4, page 15
Total Ammunition Management Information System • 3–5, page 15
Authorizations • 3–6, page 16
Forecasts • 3–7, page 17
Requesting munitions • 3–8, page 18
Expenditures • 3–9, page 19
Readiness Reports • 3–10, page 20

Appendix A. References, page 22

Glossary

ii AR 5–13 • 17 December 2009

Chapter 1
Introduction
1–1. Purpose
This regulation prescribes policy, procedures, and responsibilities for munitions management and the Total Army
Munitions Requirements (TAMR) and Prioritization System to include training, operational, new equipment training
(NET), and test munitions.

1–2. References
Required and related publications and prescribed and referenced forms are listed in appendix A.

1–3. Explanations of abbreviations and terms

Abbreviations and special terms used in this regulation are explained in the glossary.

1–4. Key operational munitions management functions

a. Requirement. Requirements are the types and quantities of munitions that the Army and its subordinate units must
have to execute their combat, operational, training, and testing missions.
b. Prioritization. Prioritization is establishing the relative importance of one requirement or resource over another
and is an operational function.
c. Authorization. An authorization is the quantity of munitions that a unit or organization may receive in support of
its DCS, G–3/5/7 validated requirements. The DCS, G–3/5/7 munitions management office ensures support for the
most critical requirements by publishing munitions authorizations in Total Ammunition Management Information
System (TAMIS).
d. Forecast. A forecast is a monthly estimate of munitions by Department of Defense identification code (DODIC),
quantity, and location that a unit or organization plans to draw in support of validated Army munitions requirements of
noncombat day-to-day operations, training, or testing.
e. Allocation. An allocation is the supply distributed to resource a requirement.
f. Expenditure. Expenditures are the quantities of munitions, by DODIC that a unit or organization fires in support
of operations, training, testing, or new equipment training (NET).
g. Request. A request is the quantity of munitions, by DODIC, that a unit asks to receive using an electronic DA
Form 581 (Request for Issue and Turn-in of Ammunition) in TAMIS or a manual DA Form 581 if electronic means are
not available.
h. Accountability. Accountability is the obligation of a person to keep records of property, documents, or funds.
These records show identification data, gains, losses, due-in, due-out, and balances on hand or in use, as defined in AR
735–5.

1–5. Responsibilities
a. The Under Secretary of Defense (USD) for Acquisition, Technology and Logistics (AT&L). The USD AT&L
directs all Services to develop their total munitions requirements according to DODI 3000.4 (DOD Munitions
Requirements Process) and USD implementation guidance. Services must submit their requirements to OUSD AT&L
no later than 1 January in alternating years to support near-term readiness assessments and long-term program objective
memorandum (POM) investments. The Land Warfare and Munitions Directorate is the lead Office of the Secretary of
Defense (OSD) agency for the development of Service munitions requirements.
b. Under Secretary of Defense for Policy. Provides formal policy guidance to the Services regarding scenarios and
other planning factors the Services must take into account when determining their respective munitions requirements.
c. The Secretary of Defense, Program, Analysis, and Evaluation (OSD PA&E). Maintains the approved Defense
Planning Scenarios for use in the munitions requirement process (MRP). The approved planning scenarios can be found
in the Analytical Agenda database managed by OSD PA&E.
d. The Joint Staff (J–8).
(1) Reviews and coordinates the Defense Intelligence Agency (DIA) threat report (TR).
(2) Reviews and coordinates combatant commanders’ (CCDRs) near-year (NY) phased threat distribution (PTD) for
all Services’ use.
(3) Develops the out-year (OY) PTDs for all Services’ use according to DODI 3000.4.
(4) Conducts a pre- and post-POM munitions sufficiency assessment (SA) based upon Service submissions and NY
and OY PTDs.
e. Combatant commander.
(1) Documents their Army Service Component Command (ASCC) war reserve and operational and training muni-
tions requirements.
(2) Develops their PTD according to DODI 3000.4 based on the threat equipment and personnel found in DIA threat

AR 5–13 • 17 December 2009 1

reports to provide Services with the threat targets that must be addressed by the individual Services in order for the
CCDR to successfully execute their operational plan (OPLAN).
f. Assistant Secretary of the Army for Acquisition, Logistics and Technology (ASA(ALT)). The Secretary of the
Army, as the single manager for conventional munitions (SMCA), has delegated the SMCA responsibilities to
ASA(ALT) (reference DODD 5160.65). ASA(ALT) does the following:
(1) Conducts all munitions acquisition and acquisition management functions for missiles and conventional muni-
tions for DOD.
(2) Procures nonstandard (U.S.-made and foreign-sourced) munitions for war reserves and operations, test, and
training requirements.
(3) Develops and maintains an Army acquisition strategy in support of the Army munitions strategy, and ensures
that the program executive office (PEO) maintains acquisition strategies for all Army munitions programs, demilitariza-
tion, and the industrial base.
(4) Assists with developing, managing, and defending munitions life cycle management (LCM) of which procure-
ment is one component. The principal agency for the LCM of conventional munitions acquisition is the PEO
ammunition (ammo). The principal agency for the LCM of missiles is the PEO missile and space (M&S).
(5) Assesses the feasibility of renovating Army munitions, and coordinates execution of renovation programs with
ARSTAF munitions managers (DCS, G–3/5/7; DCS, G–4; and DCS, G–8).
(6) Plans, develops, and manages requirements related to the munitions industrial base.
(7) Provides support for congressional testimony.
(8) Notifies the ARSTAF (DCS, G–3/5/7, DCS, G–4, and DCS, G–8) when procurement or production levels have
the potential to negatively impact Army readiness.
(9) Participates in a variety of Army-level forums designed to support Army munitions requirements, programming,
acquisition, and management.
(10) Programs for nonstandard and developmental munitions required to support research, development, test and
evaluation (RDT&E) of both munitions and platform development efforts.
(11) Integrates and synchronizes Army tests requiring munitions support to ensure the most effective and efficient
use of Army munitions provided for testing.
(12) Provides Army standard munitions test requirements for testing performed in support of all Army PEOs to the
Army Test and Evaluation Command (ATEC) for resourcing. Requirements support both POM and year-of-execution
resourcing processes.
(13) Maintains accurate procurement, production and delivery data for all munitions programs.
(14) Develops munitions, training devices, and simulators in support of DA-approved requirements.
(15) Develops NET plans for validation by the United States Army Training and Doctrine Command (TRADOC).
Programs and coordinates for all munitions to support NET unless support is formally coordinated in writing before-
hand with the DCS, G–3/5/7 munitions management office. Materiel developers will submit all requests for munitions
to support NET to the Army Material Command (AMC) munitions manager for resourcing.
(16) Serves as the proponent for the Web Ammunition Model (WAM)—the system of record for acquisition
modeling of Army munitions (conventional and missiles).
g. Assistant Secretary of the Army, Financial Management and Comptroller (ASA(FM&C)).
(1) Develops and publishes Army financial management, budget, and execution policy as it relates to Army
munitions.
(2) Serves as the Army liaison to the Office of the Under Secretary of Defense (Comptroller) (OUSD(C)).
(3) Prepares, reviews, approves, publishes, and submits to the OSD, Office of Management and Budget (OMB), and
Congress justification material and special exhibits in support of budget submissions.
(4) Provides support for congressional testimony.
(5) In coordination with ASA(ALT), develops continuing resolution authority (CRA) requirements related to
munitions.
(6) Validates CRA requirements related to munitions.
(7) Reviews and approves program/fund release documents.
(8) Provides information on financial execution of the Army munitions program. Performs execution reviews to
identify funding shortfalls and excesses.
(9) Coordinates staffing and submits prior approval reprogramming actions and new start notifications/prior approv-
als to congressional committees.
(10) Participates in a variety of Army-level forums designed to support Army munitions requirements, program-
ming, acquisition, and management.
h. Assistant Secretary of the Army for Installation and Environment (ASA(I&E)). The ASA(I&E) is responsible for
policy development, program oversight, and coordination of a wide variety of Army activities. These include, but are
not limited to: design, construction, operations, maintenance, and management of Army installations (including range
facilities).

2 AR 5–13 • 17 December 2009

 i. DCS, G–3/5/7. The DCS, G–3/5/7 is the ARSTAF focal point for integrating munitions management across the
Army. It has primary staff responsibility for developing Army munitions requirements, synchronizing policy, setting
priorities, overseeing the Army weapons training program, and monitoring munitions and industrial base readiness.
(1) Director, G–37/TR (Training).
(a) Chairs the Army Munitions General Officer Steering Committee (AMGOSC)—the primary senior-level forum in
which to discuss and resolve munitions issues that affect munitions readiness and management.
(b) Develops and synchronizes the Army munitions strategy, ensuring that acquisition, logistics, and programming
support approved Army munitions capabilities, requirements, and priorities.
(c) Develops and maintains the TAMR.
(d) Chairs the Army munitions strategy council of colonels (AMSCoC),
(e) Chairs the Army munitions requirements council of colonels (AMRCoC).
(f) Synchronizes Army munitions management policy and is the proponent for DA Pam 350–38 and AR 5–13,
which establish policy for developing, prioritizing, and managing Army munitions requirements.
(g) Develops, validates, and prioritizes Army munitions requirements for both standard and nonstandard munitions.
The only exceptions to this are Special Forces’ unique requirements and developmental munitions (and components)
required to support testing.
(h) Conducts risk analysis in coordination with the DCS, G–4 to determine resourcing solutions for all requirements
that decrement the Army munitions stockpile. This includes foreign military sales (FMS) diversions, loans to other
Services, and so forth.
(i) Assists the DCS, G–8 with defending munitions procurement programs and budgets.
(j) Validates and consolidates Army munitions stockage objectives (SO).
(k) Participates in a variety of Army-level forums designed to support Army munitions requirements, programming,
acquisition and management.
(l) Develops and publishes annual munitions authorizations in TAMIS—adjusting them as needed to ensure the
resourcing of validated requirements according to Army priorities.
(m) Co-chairs the Total Army Ammunition Authorization and Allocation Conference (TA4C) and Missile Distribu-
tion Plan (MIDP) Conference with the DCS, G–4 to ensure the authorization and distribution of Army munitions in
support of validated requirements and priorities.
(n) Serves as the DA proponent for TAMIS information requirements according to AR 25–1.
(o) Manages and administers TAMIS according to the Army Knowledge Management Implementation Plan.
(p) Calculate all munitions expenditures based upon issue and serviceable turn-in data received from any DCS, G–4-
approved system of record for munitions accountability.
(2) Director, G–37/FM (Force Management). This office is the Army lead agency for Army force structure and
provides the force structure used in the MRP—to include identifying the Standard Resource Code (SRC) apportioned in
support of each OSD-directed mission.
(3) Director, G–35/SS (Strategic Plans and Policy). This office is the Army lead agency for Army pre-positioned
stock (APS) policy and provides G–37/TR with APS personnel and equipment densities that require munitions.
(4) Director, G–37/CI (Capabilities Integration). This office is the Army lead agency for staffing and validating all
proposed capability requirements. The DCS, G–3/5/7 munitions management office incorporates only validated and
approved capabilities into Army munitions requirements.
j. DCS, G–4. This office has responsibility and oversight for policy, plans and resources for storage, surveillance,
allocations, distribution accountability, and demilitarization for all Army munitions. The DCS, G–4—
(1) Develops, synchronizes, and maintains munitions logistics support policy for Army munitions.
(2) Develops and administers munitions distribution plans in support of DCS, G–3/5/7 authorizations and priorities.
(3) Develops and maintains the Army logistics strategy in support of the Army munitions strategy.
(4) Participates in a variety of Army-level forums designed to support Army munitions requirements, programming,
acquisition, and management.
(5) Co-chairs the TA4C and MIDP Conference with the DCS, G–3/5/7 to ensure that the authorization and
distribution of Army munitions support validated Army requirements and priorities.
(6) Advises the DCS, G–3/5/7 on inventory and stockpile management matters that have the potential to affect
Army munitions readiness negatively. This includes providing assessments regarding the serviceability and reliability
of Army missiles and munitions.
(7) Provides information to support DCS, G–3/5/7 risk assessments and assists in determining resourcing solutions
for all requirements that decrement the Army munitions stockpile.
(8) Serves as the proponent for the Standard Army Ammunition System-Modernized (SAAS–MOD); the Worldwide
Ammunition Reporting System (WARS), the systems of record for accountability of all Army munitions; and the
National Level Ammunition Capability, which is the Joint Service tool for ammunition visibility.
(9) Maintains accurate on-hand, serviceability, and inventory data for all Army munitions.

AR 5–13 • 17 December 2009 3

 (10) Is the approval authority for all condition codes for munitions classification within the Army stockpile.
(11) Provides management, budgeting, and funding oversight for APS.
(12) Provides management, budgeting, and funding oversight for operational project (OPROJ) stocks.
(13) Coordinates OPROJ munitions requirements with the DCS, G–3/5/7 munitions management office for valida-
tion and resourcing.
k. DCS, G–6/Chief Information Officer (CIO). As the HQDA proponent responsible for information systems—
(1) Serves as the Army focal point for information systems.
(2) Provides oversight and direction for the Army Networthiness Program.
(3) Provides oversight of the Army Information Assurance Program (AIAP).
(4) Facilitates adoption of approved standards for information management and information system interoperability
with other Army systems.
l. DCS, G–8. As the principal military advisor to the Army munitions strategy/campaign plan (ASA(FM&C)) for
Army budget program development and justification, develops and defends Army munitions programs, resourcing, and
funding throughout the programming and budgeting phases of the planning, programming, budgeting and execution
(PPBE).
(1) Ensures that Army munitions funding requirements are accurately represented in the POM and presented in the
Future Year Defense Plan (FYDP).
(2) As part of the force integration process, synchronizes munitions funding requirements and programs with
weapon systems to achieve the maximum warfighting capability within technological and fiscal constraints.
(3) Develops and maintains an Army resource management strategy in support of the Army munitions strategy.
(4) Participates in a variety of Army-level forums designed to support Army munitions requirements, programming,
acquisition, and management.
(5) Conducts Army munitions program reviews.
(6) Advises the DCS, G–3/5/7 of shortfalls in munitions funding caused by program or budget decisions within the
Army, OSD, OMB, or the Congress.
(7) Ensures integration and coordination of munitions programming with other munitions management functions
(procurement, stockpile management, distribution, and demilitarization).
(8) Provides quantities of munitions planned for procurement in support of the requirements development process.
(9) Through its field operating agency, the Center for Army Analysis (CAA), supports the Army MRP by providing
detailed modeling and simulation of Army munitions requirements for combat operations, according to DCS, G–3/5/7
qualitative war reserve requirement for munitions (QWARRM) study directives.
m. Army Command, Army Service Component Command, and Direct Reporting Units. Commanders at all levels are
responsible for managing munitions within their respective organization. For the purpose of this regulation and in
TAMIS, ASCCs and DRUs are identified as Army Commands. This designation is not intended to convey any greater
authority or responsibility than an ASCC or DRU would ordinarily retain. Army Commands will—
(1) Participate in developing munitions requirements according to DCS, G–3/5/7 guidance.
(2) Validate, consolidate, and submit subordinate elements’ munitions requirements and annual stockage objectives
to DCS, G–3/5/7.
(3) Participate in HQDA-sponsored authorization and allocation conferences to ensure the proper resourcing of
Army Command requirements.
(4) Manage requirements and authorizations—to include subauthorizing munitions to subordinate elements.
(5) Manage requirements and authorizations for munitions supporting APS within the CCDR’s area of operations.
(6) Coordinate with the DCS, G–3/5/7 munitions management office and DCS, G–4 munitions managers prior to
receiving munitions support from another Service.
(7) Establish a program to monitor forecasting within the command, and ensure forecasting supports sound stockpile
management processes.
(8) Establish procedures to ensure the expenditure of only properly authorized munitions.
(9) Establish procedures to ensure accurate reporting of all expenditures.
(10) Publish internal operating procedures to ensure implementation of this policy and to minimize the effect of
personnel turnover on munitions management.
(11) Manage user access to TAMIS and ensure that proper user controls are in place throughout the command to
prevent untrained personnel from accessing the system.
n. Commanding General, U.S. Army Special Operations Command (USASOC). In addition to the responsibilities
common to all Army Commands, the CG, USASO supports the Army MRP by—
(1) Developing munitions combat load (CL) totals for special operations forces (SOF) weapons that are not in the
Army inventory but which use Army-common munitions and weapons that are in the Army inventory, but which are
configured to hold more ammunition than their Army-common counterpart.

4 AR 5–13 • 17 December 2009

 (2) Determining and providing the DCS, G–3/5/7 with USASOC’s requirements for Army-common munitions to
execute OSD/Joint staff-approved OPLANS or contingency plans (CONPLANs).
(3) Providing the DCS, G–3/5/7 and the DCS, G–4 with USASOC’s Title X requirements for which USASOC plans
to request Army munitions no later than the end of March and end of July annually to support authorizations and
allocations processes.
(4) Managing, programming, and budgeting for SOF-peculiar munitions.
(5) Approving authority for all Army requests for SOF-peculiar munitions.
(6) Managing, if desired, SOF-peculiar or SOF-procured nonstandard munitions in TAMIS.
o. Commanding General, U.S. Army Training and Doctrine Command (CG, TRADOC). In addition to the responsi-
bilities common to all Army Commands, the CG, TRADOC, supports the Army MRP by—
(1) Executing provisions in Munitions Combat Load Study (MCLS) directives, ensuring inputs are consistent with
NY and OY combat developments.
(2) Serving as the HQDA executive agent for the Standards in Training Commission (STRAC), established in
March 1982, according to guidance from the Vice Chief of Staff, U.S. Army.
(3) Proposing validated Army war reserve/operational and weapons training munitions resourcing strategies for
DCS, G–3/5/7 approval.
(4) Ensuring linkage between doctrine, warfighting requirements and training requirements.
(5) Ensuring linkage between institutional training requirements and home station/Combined Training Center (CTC)
sustainment training requirements.
(6) Maintaining DA Pam 350–38 (STRAC) and ensuring that it contains only DCS, G–3/5/7-approved munitions
resourcing strategies.
(7) Providing an annual updated estimate of TRADOC program of instruction (POI) requirements and requirements
for each POM period.
(8) Supporting the Army munitions strategy by providing information regarding the status and projected future of
Army capabilities requirements.
(9) Determining and coordinating mobile training team (MTT) requirements for Army units and providing annual
requirements and updates to the DCS, G–3/5/7.
(10) Analyzing weapons and tactical training needs to ensure the effective integration of subcaliber and dummy,
drill, and inert (DDI) munitions and training aids, devices, simulators, and simulations (TADSS) into Army weapons
training strategies.
(11) Tracking the progress of new programs and ensuring that materiel developers develop effective NET plans that
are synchronized with the POM process.
(12) Validating materiel developer NET plans involving munitions requirements in support of weapons training.
(13) Participating in Army-level forums designed to support Army munitions requirements, programming, acquisi-
tion and management.
p. Commanding General, U.S. Army Materiel Command (CG, AMC). In addition to the command-level munitions
management responsibilities common to all Army Commands, the CG, AMC—
(1) Manages the Army munitions stockpile, to include pre-positioned stocks and operational projects.
(2) Assists the DCS, G–4 with developing and maintaining the Army logistics strategy in support of the Army
munitions strategy.
(3) Provides the ARSTAF with accurate munitions inventory and production data.
(4) Compiles Army munitions readiness reports, and notifies the DCS, G–3/5/7 and the DCS, G–4 when conditions
affecting the stockpile may negatively impact Army munitions readiness or current or proposed distribution plans.
(5) Distributes munitions according to DCS, G–3/5/7 authorizations, forecasts in TAMIS, and DCS, G–4 distribution
plans.
(6) Designates a munitions manager to develop and coordinate command munitions requirements and resourcing,
which include munitions to support—
(a) AMC testing, such as Ammunition Stockpile Reliability Program (ASRP) testing and post-maintenance weapons
system testing and certification.
(b) NET in support of TRADOC-validated NET plans.
q. Commanding General, Army Test and Evaluation Command (CG, ATEC). The CG, ATEC is the single point of
contact (POC) for all Army test requirements for standard munitions. In addition to the command-level munitions
requirements responsibilities common to all Army Commands, the CG, ATEC—
(1) Is the lead agency for consolidating, reviewing, and submitting all Army RDT&E requirements for standard
munitions to the DCS, G–3/5/7 for validation and resourcing.
(2) Provides the DCS, G–3/5/7 updated requirements semiannually and for each POM period.
(3) Establishes a procedure to distinguish between RDT&E test requirements that receive DCS, G–3/5/7 validation
and those that do not.

AR 5–13 • 17 December 2009 5

 (4) Manages Army test munitions requirements, authorizations, forecasts, requests, and expenditures in TAMIS
(except for developmental munitions and munitions components used for testing, unless they choose to manage these
items in TAMIS).
(5) Participates in HQDA-sponsored authorization and allocation conferences, and assists the DCS, G–3/5/7 and
DCS, G–4 with developing resourcing solutions for test requirements.
(6) Distributes all TAMIS authorizations in support of Army test requirements according to DCS, G–3/5/7-validated
requirements and priorities.
(7) Establishes a program to monitor forecasting of test munitions, and ensures forecasting supports sound stockpile
management processes.
(8) Participates in a variety of Army-level forums designed to support Army munitions requirements, programming,
acquisition, and management.

Chapter 2
Army Munitions Requirements Process
2–1. Overview
a. DODI 3000.4 directs all Services to develop their munitions requirements biennially. The Army develops and
publishes its requirements annually in the TAMR document. The TAMR is a by-DODIC listing of Army NY and OY
munitions requirements for war reserves and operations, testing, and training. Army requirements identify the types and
quantities of munitions the Army must have to execute its warfighting and daily operational, test, and training missions.
The ARSTAF uses the Army’s NY and OY requirements to assist in managing the munitions stockpile.
b. The DCS, G–3/5/7 munitions management office is the lead Army agency for the development, validation, and
prioritization of all Army munitions requirements for both standard and nonstandard munitions. The only exceptions to
this are special forces’ unique requirements and developmental munitions (and components) required to support testing.
c. The DCS, G–3/5/7 submits draft unconstrained OY munitions requirements to OSD/Joint staff on 1 October in
odd-numbered years.
d. The DCS, G–3/5/7 submits final Army-approved unconstrained and constrained NY and OY requirements to
OSD/Joint staff on 1 January in even-numbered years.
e. Except in rare instances, war reserve and operational munitions requirements will have a supporting Army
weapons training strategy. Institutional weapons training strategies should also have a supporting home station weapons
training strategy to ensure that Soldiers do not lose perishable skills once they leave the institutional setting.
f. The DCS, G–3/5/7 conducts semiannual Army munitions requirements working groups (WGs) and councils of
colonels (CoCs) to formally analyze, approve, and synchronize proposed changes to Army munitions requirements.
Informal analysis and synchronization of Army munitions requirements are a continuous process that also occurs in
other forums, including the DCS, G–3/5/7 Army munitions strategy WGs/CoCs, the DCS, G–8 program reviews, and
the ASA(ALT) weapon systems reviews (WSRs).
g. Only test munitions requirements are exempt from the Army munitions requirements WG/CoC process. Test
requirements are developed according to AR 73–1. The ASA(ALT) integrates and synchronizes Army munitions test
requirements to ensure the most effective and efficient use of Army munitions prior to submitting requirements to the
Army Test and Evaluation Command (ATEC). The DCS, G–3/5/7, with ASA(ALT) support, approves Army test
munitions requirements in support of POM and year-of-execution resourcing.
h. The TAMIS is the DCS, G–3/5/7’s real-time, web-based application for managing munitions requirements,
authorizations, forecasts, requests and expenditures. Incorporated in TAMIS is an internal application that collects
HQDA-approved table of organization and equipment/table of distribution and allowances (TOE/TDA) weapons
density data for all unit identification codes (UIC). This data is a critical component of Army munitions requirements
calculations. Army Commands must validate the accuracy of their TOE/TDA weapons densities in Web-Based Total
Army Authorization Document System (WEBTAADS) and TAMIS and coordinate resolution of discrepancies with
Army Training Support Center (ATSC) not later than (NLT) 15 September annually.
i. Only munitions that have completed a milestone (MS) B (capability development document (CDD)) decision are
included in Army requirements. In years when QWARRM studies are conducted, munitions must reach MS B by 1
June to be included in the study.
j. New munitions are included in Army NY requirements only if they will be fielded by the end of the first year of
the POM period.
k. New munitions are included in Army OY requirements only if they will be fielded by the end of the last year of
the POM period.
l. Other Services and non-DOD agencies are responsible for providing the munitions necessary to support their
requirements. Army organizations that receive requests for Army munitions from other Services and non-DOD will
forward them to the DCS, G–3/5/7 munitions management office for coordination of resourcing solutions.

6 AR 5–13 • 17 December 2009

 m. The ASA(ALT)/PEOs will not provide Army-owned standard munitions to any organization (contract, military,
or civilian) without first obtaining DCS, G–3/5/7 validation of the requirement.
n. Key terms associated with war reserve and operational munitions requirements are—
(1) Combat load (CL). The standard quantity and type of munitions an individual weapon, crew-served weapon or a
weapons platform and its modified table of organization and equipment (MTOE)-designated munitions carriers are
designed to hold. Combat loads for bulk munitions (grenades, signals, and so forth) are not associated with a weapon
or weapons platform. Bulk munition CLs are assigned by SRC and reflect the quantity of munitions required to give
units capability and flexibility. Combat loads support the initiation of combat operations and are the basic building
blocks of Army war reserve requirements.
(2) Sustainment load (SL). SLs are the munitions needed to initiate and support a force’s operations until resupply
can be provided.
(a) Prior to the commencement of combat operations, a SL is calculated using a CL or multiples thereof and
includes the initial CL. Calculate SL requirements only for units that actually will be in the theater of operations prior
to establishment of a sea line of communications (SLOC), according to time lines in an ASCC’s most demanding OSD/
Joint staff-directed theater OPLAN or CONPLAN.
(b) Once operations commence, SL resupply is based on the munitions required to support forces until the next
scheduled resupply ship arrives. Taking into account that expenditures will vary from DODIC to DODIC during
operations, SL resupply quantities likely will be tailored to reflect variables such as planned missions and forces,
previous and planned expenditures, and on-hand supply.
(3) Operational project (OPROJ). OPROJs are munitions set aside for a specific unit or mission. OPROJs require
DCS, G–3/5/7 and DCS, G–4 written approval, according to AR 710–2.
(a) Once approved, an OPROJ remains at an ammunition supply point (ASP) or depot and is not issued unless the
unit for which the OPROJ is approved mobilizes or deploys, or the appropriate authority directs execution of the
mission for which the OPROJ has been designated.
(b) Munitions will not be requisitioned or stocked for an OPROJ unless it has a valid project code issued according
to AR 725–50.
(c) The DCS, G–3/5/7 munitions management office validates all munitions requirements in support of approved
OPROJs.
(4) Operational load (OPLOAD). OPLOADs are a commander’s daily operating requirements. They include muni-
tions that Army units require to support or conduct a broad range of day–to–day operational missions; for example,
installation EOD, SRT operations, ceremonies, and quarry operations, guard force missions, force protection, SOF,
predeployment site surveys, and so forth.
(5) OPLAN requirement. The total quantity of munitions required to execute an ASCC’s most demanding major
combat operation (MCO) in support of an OSD/Joint staff-directed theater OPLAN or CONPLAN. Generally speaking,
this consists of operations from D-day to the point at which OPLANs/CONPLANs project a transition to stability-type
operations.

2–2. War reserve and operational munitions requirements

a. In general, Army war reserve and operational munitions requirements include—
(1) Combat requirements in support of OSD/Joint staff-approved OPLANs or CONPLANs. Combat requirements
reflect the munitions needed to equip a specified force structure to perform its assigned military mission and to meet
CCDR objectives.
(2) Current operations/forward presence (CO/FP). The CO/FP requirements reflect the munitions needed to arm
forces to conduct current operations and meet forward presence obligations.
(3) Strategic readiness requirements. These requirements reflect the munitions needed to arm forces not committed
to support a combat operation and munitions needed to support those forces designated as a strategic reserve.
Additionally, it includes critical capabilities not explicitly addressed elsewhere.
b. War reserve and operational munitions may be live, practice, or DDI munitions.
c. Generating and validating war reserve/operational munitions requirements using the QWARRM process and
QWARRM studies.
(1) QWARRM process. The QWARRM process is the Army’s MRP for war reserve and operational munitions
requirements. The QWARRM process develops munitions requirements for—
(a) OSD/Joint staff-approved MCO/conventional campaigns (CCs)/irregular warfare (IW) operations.
(b) Current operations and forward presence commitments.
(c) Strategic readiness needs.
(2) QWARRM studies. The DCS, G–3/5/7 is the lead agency for QWARRM studies. The Chief, G–3/5/7 munitions
management office is the QWARRM study director. For each QWARRM study, the study director publishes detailed
directives to guide TRADOC MCLS and CAA modeling and simulation efforts. The Army reviews and updates its

AR 5–13 • 17 December 2009 7

requirements annually but conducts full-scale QWARRM studies biennially, in odd-numbered years. QWARRM
studies consist of three major components:
(a) TRADOC-developed CLs and add-on factors.
1. TRADOC is the lead agency for Army MCLS.
2. About 15 months prior to the Army’s suspense for submitting its final requirements to OSD and the Joint Staff,
the Director, G–37/TRA (training ammunition) publishes a study directive to TRADOC identifying the scope, objec-
tives, time lines, deliverables, and formats for the upcoming MCLS.
3. During each MCLS, TRADOC reviews and updates the quantities and types of munitions in Army munitions CL
for each weapons platform (tanks, artillery, rotary wing aircraft), Soldier weapons, (individual and crew-served), and
bulk munitions (hand grenades, shoulder-launched weapons, signal flares, mines, demolitions, and so forth) in a
QWARRM study. MLCS include weapons belonging to sustainment forces.
4. The Director, G–37/TRA, may request a review of NY CLs if necessary.
5. During each MCLS, TRADOC also reviews and updates add-on factors for use in the QWARRM study. Add-on
factors are a ratio of munitions in the CLs versus munitions fired in combat and is used solely as a modeling and
simulation tool. They reflect the fact that not all Army munitions demands are represented during modeling. Add-on
factors are used to generate munitions requirements for such things as shots fired at suspect targets and support targets;
onboard losses; zeroing, functions checks, and registration fire; munitions lost or destroyed in the supply chain; and
additional in-theater inventory to meet fluctuations in demand.
6. TRADOC presents recommended changes to Army CLs to the Army munitions requirements WG/CoC for
approval. TRADOC also presents recommended changes to add-on factors to the WGs/CoCs for information and
coordinates formal approval of proposed add-on factors directly with G–37/TRA.
7. Only G–37/TRA-approved CLs are posted in the TAMIS requirements module. Units will use them when
calculating their war reserve requirements. The TAMIS links the approved CLs to the line item number (LIN) and
personnel quantities assigned to a SRC to support development of unit-level CL requirements. The TAMIS extracts
unit LIN and personnel quantities from the G–37 Force Management WEBTAADS database semiannually.
(b) Center for Army Analysis-generated combat requirements.
1. The CAA is the lead agency for modeling Army MCO requirements.
2. Approximately 12 months prior to the Army’s suspense for submitting its final munitions requirements to OSD
and the Joint Staff, the Director, G–37/TRA, publishes a study directive to CAA identifying the scope and objectives of
the study, scenarios to be used, time lines, and deliverables for the planned QWARRM study. The study directive also
contains instructions regarding data needed from other organizations; for example, projected inventory data.
3. Through the use of modeling and simulation tools, CAA develops the munitions requirements for Army combat
missions based on OSD/Joint staff-approved scenarios. CAA also uses TRADOC-developed CLs and add-on factors to
identify requirements that are not modeled.
4. The CAA requirements include munitions to support actual consumption during combat, stocks for a theater
sustainment pipeline, and a residual capability to enable forces to fight in an unspecified operation at the end of a
combat operation.
5. To calculate consumption during a campaign, CAA categorizes munitions as—
a. Main munitions. These are munitions that CAA explicitly models or simulates, or are requirements based on a
factor of main munitions fired during modeling and simulation. Main munitions consist of primary “killing rounds”
such as high explosive (HE) munitions. CAA bases requirements for ancillary munitions such as smoke and illumina-
tion rounds on a ratio of main munitions in the CLs to main munitions fired in combat modeling, and TRADOC add-
on factors.
b. Small arms. These are .50-caliber and below munitions. Small-arms requirements are based on CLs associated
with a particular weapon type and unit.
c. Bulk munitions. These are munitions that are not associated with any particular weapon system. Bulk munitions
requirements are based on a CL associated with specific types of units. Bulk munitions include hand grenades,
shoulder-launched munitions, signals, flares, demolitions, and nonlethal munitions.
6. The CAA outputs include NY and OY constrained and unconstrained requirements and a 30-day requirement for
select OPLANS. The NY requirements reflect Army war reserve requirements for the first year of the POM period.
The OY requirements reflect Army war reserve requirements for the last year of the POM period.
a. Unconstrained requirements reflect the optimal mix of munitions needed to address OSD-approved OPLANs.
b. Constrained requirements reflect the reality of fiscal and industrial base constraints while still enabling CCDR to
execute OSD-approved OPLANs. Constrained requirements also reflect the types and quantities of nonprecision
munitions the Army must have on hand to compensate for a lack of all the precision munitions it requires.
7. Throughout the study, CAA analysts will coordinate with CCDR and ASCC planners to ensure CAA modeling
accurately replicates the CCDRs’ OPLANs and to address CCDR/ASCC-unique issues.
8. The CAA reviews and validates its study results prior to releasing them to the study sponsor. Validation will
consider such factors as whether recorded “kills” are realistic, whether the rounds-per-tube-per-day could be fired

8 AR 5–13 • 17 December 2009

without damaging the weapon or weapons platform, whether modeled munitions and munitions caps were properly
employed, and whether munitions stockage levels were sufficient for the campaign.
9. In accordance with DODI 3000.4, each Service must conduct a pre- and post-POM SA of its war reserve
munitions requirements. The pre-POM SA is an estimate of the Army’s NY and OY war reserve munitions require-
ments against projected inventory across the POM period. The post-POM SA is a comparison of Army OY require-
ments to the Army’s planned procurement across the POM period.
(c) Other war reserve and operational munitions requirements.
1. Concurrent with CAA modeling efforts, the DCS, G–3/5/7 munitions management office works with several
organizations to identify specific war reserve and operational requirements not addressed in CAA modeling. Once
validated, these requirements are added to CAA-generated requirements and form the remainder of the QWARRM
study.
2. These additional requirements include—
a. Conventional forces’ early-deployer requirements.
b. Army special forces operational requirements.
c. Mobilization requirements in support of OSD/Joint staff-approved scenarios.
d. A one-year strategic reserve of training munitions in outside the continental United States (OCONUS) theaters.
e. Munitions requirements in support of especially critical elements of the industrial base.
f. Munitions required to support approved OPROJs.
g. The OPLOAD munitions required to support Army daily operating requirements (for example, guard forces,
ceremonies, EOD mission support, SOF site surveys, and so forth).

2–3. Test requirements

a. The Army generates munitions requirements in support of Army testing on an annual basis.
b. The ATEC is the lead Army agency for consolidating RDT&E munitions requirements for all Army tests
involving standard Army munitions. ATEC will perform an administrative review of all submissions to ensure that they
comply with DCS, G–3/5/7 guidance prior to forwarding the requirements to the DCS, G–3/5/7 munitions management
office for validation and resourcing.
c. The ATEC also develops OPLOAD munitions requirements for mission support operations, such as range
clearing.
d. The ATEC submits Army’s NY and OY test requirements to the DCS, G–3/5/7 munitions management office for
validation and resourcing. These requirements will be reported separately by function (developmental, operational,
stockpile reliability, weapons rebuild, and OPLOAD, and so forth). The DCS, G–3/5/7 munitions management office,
in conjunction with ASA(ALT), reviews Army test requirements to determine resourcing solutions.
e. The DCS, G–3/5/7 munitions management office provides validated Army RDT&E munitions requirements for
inclusion into POM submissions to inform Army investment decisions.
f. All organizations requiring standard Army munitions for testing will maintain and manage their requirements in
the ATEC hierarchy in TAMIS. The TAMIS is the system of record for Army RDT&E requirements for standard
munitions.
g. Test munitions requirements development and validation.
(1) Test munitions requirements in support of RDT&E are developed in accordance with AR 73–1.
(2) The ATEC submits NY and OY Army RDT&E munitions requirements to the DCS, G–3/5/7 munitions
management office no later than 1 October each year in support of the POM process. This submission is a by-year, by-
DODIC and nomenclature projection of all validated RDT&E requirements for standard Army munitions needed during
the upcoming POM period.
(3) The ATEC submits the Army’s RDT&E munitions requirements for the upcoming fiscal year to the DCS, G–3/
5/7 munitions management office no later than 1 March and 15 July annually. The DCS, G–3/5/7 munitions manage-
ment office uses these requirements as the basis for distributing authorizations at Army annual munitions authorization
and allocation conferences. This ATEC submission is a by-DODIC and nomenclature projection of all Army RDT&E
requirements for standard Army munitions for the upcoming fiscal year.
h. It is imperative that organizations that require munitions for RDT&E coordinate support as far in advance as
possible. In the event unanticipated requirements occur outside of Army authorization and allocation processes,
RDT&E organizations will request support through ATEC using established processes. Such requests must be the
exception rather than the rule.
i. Organizations requesting munitions for RDT&E will request prime DODICs, unless a munition other than the
prime DODIC is required (such as for stockpile reliability testing). All organizations will inform ATEC munitions
managers if substitutes or less-than-fully serviceable munitions can be used to support an RDT&E requirement. ATEC
and DCS, G–3 and DCS, G–4 munitions managers will determine final resourcing solutions based upon this
information.
j. Materiel developers are responsible for providing all developmental and nonstandard munitions required for

AR 5–13 • 17 December 2009 9

RDT&E. If materiel developers require munitions for testing from another Service or non-DOD agency they must
coordinate with that Service or agency to obtain support.
k. Other Services and agencies are responsible for providing munitions necessary to support their RDT&E require-
ments and will submit them to the DCS, G–3/5/7 munitions management office for resourcing solutions.
l. Program managers who receive congressional adds or plus-ups to develop an item that is not a Joint Capabilities
Integration and Development System (JCIDS)-approved program are responsible for providing all munitions for
RDT&E of that item.

2–4. Training requirements

a. The Army develops munitions requirements in support of Army weapons training on an annual basis.
b. The DCS, G–3/5/7 munitions management office approves munitions requirements in support of Army weapons
training through the Army munitions requirements WG/CoC process.
c. The HQ TRADOC, ATSC, is the HQDA executive agent for the STRAC. DA Pam 350–38 contains all DCS,
G–3/5/7–approved individual and collective weapons training strategies that require Army munitions. These strategies
are also contained in TAMIS to facilitate management of training requirements.
d. The TRADOC proponent schools develop training strategies, including munitions requirements, for individual and
crew certification training on the individual and crew-served weapons for which they are the proponent.
e. The TRADOC proponent schools having collective training proponency for a crew-served weapon or weapons
platform will develop the collective training strategies, including munitions requirements, for the crew-served weapons
and weapons platforms involved in that training.
f. The TRADOC Combined Arms Center, with coordination and input from the owning command of that training
center, is responsible for developing all weapons training strategies to support collective training at all CTC. Strategies
must include resourcing for opposing forces’ training support requirements. TRADOC Combined Arms Center will use
standard Army munitions for this training
g. The TRADOC proponents also develop POI training strategies to support weapons training conducted in Army
schools and by MTTs.
h. The TRADOC proponent schools and the Combined Arms Center will base all Army weapons training strategies
upon approved Army doctrine.
i. Army Commands that have enduring (lasting 3 years or more) command-unique weapons training requirements
will present strategies for those training requirements to the Army munitions requirements WG/CoC for approval. An
example of a command-unique requirement is the third gunnery approved for Eighth U.S. Army. Army Commands
must coordinate command-unique strategies with the appropriate TRADOC proponent schools prior to presenting the
strategies in the WG/CoC for approval.
j. DA Pam 350–38 and TAMIS contains all DCS, G–3/5/7-approved individual and collective weapons training
strategies that require Army munitions. Only weapons training strategies approved through the Army munitions
requirements WG/CoC are in DA Pam 350–38, TAMIS, and TRADOC POIs.
k. Currently, DA Pam 350–38 is updated annually and officially published on 1 October in the year of execution.
Thus, the DA Pam for execution in fiscal year 20x1 is published on 1 October 20x0. The TRADOC POIs are updated
as needed.
l. All DCS, G–3/5/7-approved Army munitions resourcing strategies in STRAC and POIs are incorporated in
TAMIS so that DCS, G–3/5/7 can update as needed.
m. The standard lead time to program for, procure, produce, and distribute munitions in support of a CoC-approved
weapons training strategy is a minimum of 4 years, making it imperative for TRADOC proponents to identify weapons
training deficiencies proactively and develop training strategies to address them.
n. TRADOC proponents will incorporate TADSS into Army weapons training strategies.
o. Annually, no later than 1 November, ATSC will provide the DCS, G–3/5/7 munitions management office with a
by-year, by-DODIC, and nomenclature estimate of the Army’s total annual training requirements. In odd-numbered
years, this estimate will include requirements for the upcoming 6-year POM period. In even-numbered years, this
estimate will include requirements for the remaining 5 years of the current POM period. Once approved, the DCS,
G–3/5/7 munitions management office submits these requirements to the DCS, G–8, who uses them as a basis for
munitions funding decisions. Additionally, the DCS, G–3/5/7 uses these requirements as the basis for authorizing
munitions at Army munitions authorization and allocation conferences.
p. Army munitions requirements are calculated separately for home station training and TRADOC POI training.
(1) Home station training requirements.
(a) Home station training requirements are based on strategies in DA Pam 350–38 and G–37/Force Management-
approved weapons densities in official TOE/TDA documents.
(b) The TAMIS requirements module contains DCS, G–3/5/7 Force Management-approved TOE/TDA documents,
as well as the CoC-approved home station strategies. All units will use TAMIS to calculate their home station weapons
training requirements.

10 AR 5–13 • 17 December 2009

 (c) Occasionally, units may have TOE/TDA-authorized weapons that were not documented on the TOE/TDA when
TAMIS collected HQDA-approved TOE/TDA weapons density data for all UICs. These are valid STRAC require-
ments. Units also may have requirements that are considered “above-STRAC requirements.” These include require-
ments to support nonenduring (fewer than 3 years) Joint- and HQDA-directed exercises that are not in DA Pam 350–38
and do not appear in TAMIS and TRADOC POI requirements (discussed separately). Units will provide justification
for these requirements in TAMIS. Justifications must include the number of weapons and/or additional training events
to be resourced, as well as the impact of not conducting the training.
(d) Units that believe they have valid weapons-related STRAC and above-STRAC requirements will submit them
via TAMIS, through command channels, between 1 November and 28 February, to the DCS, G–3/5/7 munitions
management office for approval.
(e) The DCS, G–3/5/7 munitions management office will publish approved above-STRAC requirements in TAMIS.
(f) Above-STRAC requirements that will be enduring (3 years or more) will be presented through the Army
munitions requirements WG/CoC process for approval and inclusion in DA Pam 350–38. Commands must coordinate
strategies for all above-STRAC requirements with the appropriate TRADOC proponent schools prior to presenting
them in the WG/CoC process.
(g) Commands will generate CTC or exercise requirements using tables from DA Pam 350–38 in TAMIS.
(h) The total of an Army Command’s DA Pam 350–38 requirements and their DCS, G–3/5/7 munitions manage-
ment office-approved above-STRAC requirements represents the command’s total HQDA-validated annual training
munitions requirement.
(2) The TRADOC POI training requirements.
(a) The TRADOC POI requirements are based on Army munitions requirements WG/CoC-approved munitions
strategies for each course, multiplied by the number of times the course will be conducted each year.
(b) The TRADOC will calculate its POI requirements using the optimal class size, rather than the minimum or
maximum class size.
(c) Annually, no later than 1 September, TRADOC will provide ATSC with a by-year, by-DODIC estimate of
TRADOC POI training requirements. In odd-numbered years, this estimate will include requirements for the upcoming
6-year POM period. In even-numbered years, this estimate will include requirements for the remaining 5 years of the
current POM period. No later than 1 March and 15 July annually, TRADOC will submit its validated POI munitions
requirements for the upcoming fiscal year to ATSC. The DCS, G–3/5/7 munitions management office uses these
requirements as the basis for distributing authorizations at Army annual munitions authorization and allocation
conferences. This submission is a by-DODIC and nomenclature projection of all validated POI requirements for the
upcoming fiscal year.
q. Deployed, mobilized, and deploying unit training requirements.
(1) Active Army parent Army Commands are responsible for developing and validating munitions requirements for
Active Army deploying units prior to their deployment. Once the unit has deployed, the supported Army Command or
organization is responsible for the deployed unit’s munitions requirements.
(2) Active Army force providers are responsible for developing and validating munitions requirements for mobilized
Reserve Component (RC) units whose deployment location will be OCONUS, or in support of OCONUS missions;
such as “back filling” deploying Active Army units. Once the RC unit has deployed, the supported Army Command or
organization is responsible for the unit’s munitions requirements.
(3) The RC commands are responsible for post-mobilization munitions requirements for their RC units whose
deployment location will be in continental United States (CONUS); for example, for homeland defense missions. Once
the unit is at its deployment site, the supported Army Command or organization assumes responsibility for its
requirements.
(4) DA Pam 350–38 contains contingency tables to resource mission-specific training for deploying, mobilized, and
deployed units.
(5) DA Pam 350–38 contingency tables resource training munitions are based upon weapons densities rather than
specific events. This method simplifies the requirements determination process and allows units to account for
additional weapons that may be fielded to deployed, mobilized, or deploying units. It also takes into account that
deployed, mobilized, and deploying units may need to conduct mission-tailored training not supported by the event-
based weapons training strategies in DA Pam 350–38.
(6) Deployed units will use the contingency tables in DA Pam 350–38. Mobilized and deploying units may use the
contingency tables if they need to conduct mission-tailored training not resourced by DA Pam 350–38.
(a) If a unit will be deployed for part of a training year, the parent Army Command will only submit requirements
for munitions needed to support training during the portion of the year that the unit will be at home station.
(b) Upon redeployment to home station, units issued weapons in support of a contingency operation must add those
weapons to their unit’s official equipment authorization document or have HQDA-level approval to continue to retain
the weapons in order to continue receiving training munitions for those weapons.
(c) Army Commands will coordinate requirements for deployed, mobilized, and deploying units as far in advance as

AR 5–13 • 17 December 2009 11

possible. If sufficient notice of a contingency mission has been provided, Army Commands will submit requirements
for resourcing at Army munitions authorization and allocation conferences.
(7) Deploying units have priority of support. Army Commands will resource predeployment, mobilized, and deploy-
ing unit training with internal assets to the maximum extent possible and request additional munitions authorizations
only if internal assets are insufficient.
(8) At least once every 3 years, ATSC will coordinate the DA Pam 350–38 contingency tables with TRADOC
proponents and Army force providers to ensure the tables remain relevant and useful for assisting deploying, mobilized,
and deployed units in developing their training requirements. Present all recommended changes to the contingency
tables to the Army munitions requirements WG/CoC for approval. The DCS, G–3/5/7 munitions management office
will not include contingency training requirements in POM submissions but will use them as a basis for distributing
TAMIS authorizations in support of valid, priority requirements.
r. NET requirements.
(1) Materiel developers are responsible for developing and resourcing all munitions required to support TRADOC-
approved NET plans for materiel to be fielded to Army units. Materiel developers will program for all munitions
required to support NET.
(2) In some instances, it may be possible to leverage a unit’s planned training to accomplish approved NET, but
materiel developers must formally request, in writing, that NET be conducted in conjunction with a unit’s planned
training.
(3) Materiel developers will submit all requirements for NET ammunition to the AMC munitions manager. The
AMC munitions manager will perform an administrative review of all requests to ensure they comply with DCS, G–3/
5/7 guidance prior to forwarding them to the DCS, G–3/5/7 munitions management office for consideration. Requests
must contain—
(a) A description of the NET to be conducted, according to the TRADOC-approved NET plan.
(b) The NET schedule (including units to undergo NET) and dates and locations of the planned NET.
(c) A by-DODIC and nomenclature listing of the quantities of munitions required for each fiscal year the NET will
be conducted.
(d) A POC through which support can be coordinated and contact information for the POC.
(4) Upon receiving written concurrence from the DCS, G–3/5/7 munitions management office, the materiel
developer will work with the appropriate Army Command ammunition manager to coordinate the NET.
(5) If DCS, G–3/5/7 munitions managers nonconcur with the materiel developer’s proposal, the materiel developer
is responsible for providing all munitions needed to fully resource the TRADOC-approved NET plan.
(6) Materiel developers who fail to plan for NET may be required to transfer funds to the Joint Munitions Command
(JMC) to pay for required munitions.
s. Nonstandard ammunition.
(1) Nonstandard munitions are those munitions and explosives that—
(a) Have not completed safety type classification and may pose unacceptable risks to personnel or equipment.
(b) Do not have a National Stock Number (NSN) or DODIC.
(c) Are not managed by the JMC or the Army Missile Command (AMCOM).
(2) The ACOMs that require nonstandard ammunition for training will request the required munitions through the
DCS, G–3/5/7 munitions management office. The DCS, G–3 will forward approved requests to ASA(ALT) PEOs for
execution.
(3) All requests for nonstandard ammunition will include the following information:
(a) Nomenclature (type and caliber).
(b) Quantity.
(c) Manufacturer, source, and vendor information.
(d) Explanation of why the requirement cannot be satisfied with standard Army ammunition.
(e) The ACOM POC and phone number.
(f) Unit POC and phone number.
(g) Installation POC and phone number.
(4) In accordance with AR 710–2, ACOMs will ensure proper accountability of all nonstandard training munitions—
whether contained in sets or issued as individual items.
(5) DA Pam 385–64 contains procedures for obtaining approval to actually possess and use nonstandard munitions
on military installations.

2–5. Stockage objectives

a. The DCS, G–3/5/7 munitions management office validates all proposed SOs. The DCS, G–4 fills SOs based on
DCS, G–3/5/7 priorities and supply availability. The Army’s goal is to maintain theater supply levels as close to the
validated SO as possible in order to avoid both significant shortfalls and overages.
b. In the case of preferred munitions (for example, missiles and other precision munitions) and low-density

12 AR 5–13 • 17 December 2009

specialized items for which the Army needs a capability less than a full CL for every unit, the Army may retain those
stocks in CONUS depots to preserve maximum operational flexibility to meet emerging requirements worldwide.
During deployment planning, ASCCs, in coordination with United States Army Forces Command (FORSCOM), AMC,
or other applicable organizations, must plan transportation of such munitions in support of their deploying forces.
c. A stockage objective is the quantity of munitions required to ensure all training and operations can be conducted
until resupply occurs. Stockage objectives consist of—
(1) The SL requirements.
(2) The OPLOAD requirements.
(3) The OPROJ requirements.
(4) Twenty-four months of training munitions (OCONUS theater-level only), according to DCS, G–3/5/7 munitions
management office-approved training requirements.
(5) The APS requirements for munitions to support TOE equipment in Army-approved APS sets.
d. Determining APS requirements.
(1) APS–2, –4, and –5. ASCCs calculate requirements for all TOE-authorized units in forward-positioned, land-
based sets (APS–2, –4, and –5). This requirement will consist of one CL for initiation of operations, plus an SL equal
to one-half CL for all unit sets. This planning factor assumes land-based sets will be able to quickly obtain resupply
from munitions within the theater of operations.
(2) APS–3.
(a) Brigade sets. Because APS–3 is multiapportioned, the DCS, G–3/5/7 munitions management office will develop
requirements for the TOE-authorized equipment sets, in coordination with the ASCCs. Requirements for these sets will
include one CL for initiation of operations, plus an SL equal to one additional CL for all unit sets in APS–3. This
planning factor assumes that sea-based sets may not be able to obtain resupply quickly once deployed.
(b) Army strategic flotilla (ASF) ships. DCS, G–3/5/7 munitions management office will base APS–3 ASF muni-
tions requirements on a total of 30 days of supply (DOS) required to support the Army’s most stressful major combat
operation. Each ASF ship also will contain a munitions package to support stability operations.
(c) The DCS, G–3/5/7 munitions management office will provide APS–3 munitions requirements to AMC annually,
not later than the end of March to support the annual TA4C.
(3) APS–1. These are CONUS-based munitions and consist of—
(a) DCS, G–3/G–4-approved OPROJs for CONUS units.
(b) DCS, G–3/5/7-approved OPLOADs for CONUS units.
(c) One CL and one SL equal to one CL for each of two infantry brigade combat teams to provide a conventional
force early-deployer capability. In CONUS, 150 days of Army training stocks on hand.

Chapter 3
Prioritization and Synchronization of Support to Approved Requirements
3–1. Overview
a. This chapter provides policy for how the DCS, G–3/5/7 prioritizes and synchronizes support of approved
requirements.
b. It includes discussions of key forums where prioritization and synchronization decisions are made, the DCS, G–3/
5/7 munitions management office’s role, user responsibilities, readiness reporting, use of TAMIS, and the Army
munitions management battle rhythm.

3–2. Prioritization of approved munitions requirements

a. As noted in chapter 1 of this regulation, prioritization involves establishing the relative importance of one
validated requirement over another. Prioritization is a key element of the munitions management process because it
specifies which requirements must be resourced first or to a higher level than other requirements. At times, the DCS,
G–3/5/7 may deem a requirement to be so important that it must be resourced above all others. At other times, the
DCS, G–3/5/7 may deem a requirement to be valid but not a priority that must be resourced above any others.
b. Many factors influence Army priorities. These factors range from current and projected readiness and changes in
Army missions and force structure to available resources. Like requirements, priorities are subject to change, some-
times frequently and with little notice.
c. Policy regarding prioritization of actual munitions is discussed in the paragraph 3–6 (Authorizations) of this
regulation.
d. Concurrent with the publication of NY and OY TAMR, the DCS, G–3/5/7 will publish its general munitions
funding priorities to assist Army programmers and ASA(ALT) with determining which types and quantities of
munitions to fund and procure first.

AR 5–13 • 17 December 2009 13

 e. ARSTAF or other munitions managers who have questions regarding prioritization of specific munitions or
munitions funding priorities should contact G–37/TRA for additional guidance.

3–3. Integration and synchronization of Army munitions management

a. The DCS, G–3/5/7 is responsible for integrating all aspects of Army munitions management. The DCS, G–3/5/7
munitions management office serves as the Army lead in that effort.
b. Army munitions strategy and campaign plan (AMS/CP). The AMS/CP is the DCS, G–3/5/7’s tool for integrating
Army munitions management. The AMS/CP provides a holistic, strategic-level approach to managing Army conven-
tional and missile munitions in the context of a Joint, capabilities-based force.
(1) The AMS/CP addresses—
(a) Programs (including capability and resource gaps), excessive duplication of capabilities, and issues related to the
life-cycle management of Army munitions.
(b) Processes for managing requirements, prioritization, decisionmaking, and use of resources.
(2) Primary objectives of the AMS/CP are to—
(a) Ensure that the Army munitions stockpile supports DOD, Joint, and Army warfighting requirements and
priorities at all times.
(b) Ensure that munitions-related programs are transparent, defendable, and support approved Joint and Army
capability-based requirements and priorities.
(c) Prevent capability gaps and excessive duplication of capabilities.
(d) Generate steady-state warfighter training and operational capability while maintaining the ability to surge.
(e) Ensure proactive, strategic management of Army munitions by focusing on munitions readiness at the end of
each POM cycle, rather than on current or near-term readiness.
(f) Force difficult and systemic problems to the forefront, assign a way ahead and responsibility for addressing them,
and track progress toward their resolution.
(g) Ensure munitions managers at all levels take a life-cycle management approach to addressing munitions
readiness.
(h) Improve the processes that support Army munitions management.
c. The AMSCoC is a chartered DA steering committee for reviewing, analyzing, and updating the Army munitions
strategy and overseeing execution and resourcing of the approved strategy.
(1) The Director, G–37/TRA munitions management office chairs the AMSCoC. All organizations with a role in the
key functions associated with Army munitions management—requirements and priorities, acquisition, logistics and
resource management—will participate in the AMS/CP process.
(2) The AMSCoC and its supporting WGs are held semiannually.
(3) Key duties of the AMSCoC are to—
(a) Approve and oversee execution and resourcing of the Army munitions strategy.
(b) Identify issues that require general officer decisionmaking authority and present them to the AMGOSC or other
appropriate committee or office. Examples include actions that would establish new program requirements, sig-
nificantly increase the costs of a program, or increase risk to Army munitions readiness or the warfighting capability of
the combatant commands.
(c) Publish the Army munitions strategy biennially in odd-numbered years to support the POM process.
(d) Develop and maintain an up-to-date campaign plan to actively manage, synchronize, and track execution of the
approved Army munitions strategy.
(e) Present the AMS/CP as an annex to the Army Campaign Plan (ACP).
d. The AMS WGs and CoCs are not forums in which to present year-of-execution unfunded requirements. Rather,
their focus is on long-term issues that should be across the POM cycle.
e. The key components of all munitions strategies are—
(1) The strategy identifies the plan and key milestones associated with developing and implementing munitions-
related programs that support approved Joint and Army requirements and priorities.
(2) Baseline assessment. The baseline assessment reflects the current status of a program or management process
(such as, requirements and priorities, acquisition, logistics and resource management). It is the basis for all CPs, as it
allows munitions managers to identify problems that impact their ability to implement a proposed strategy.
(3) Campaign plan. The CP is the action plan for correcting issues that will inhibit successful execution of a
strategy. It must provide decisionmakers with key facts, operational impacts, and actions needed to resolve the issue.
f. The AMS/CP is not intended to replace ASA(ALT) WSR or the DCS, G–8 program reviews. The strategy should
inform WSRs and program reviews, but it is focused more broadly on all aspects of munitions management, to include
management processes.
g. Army Munitions General Officer Steering Committee (AMGOSC).
(1) The AMGOSC is the DCS, G–3/5/7’s primary senior-level forum in which to discuss and resolve munitions
issues that affect Army munitions readiness and that require general officer decisionmaking authority. It also ensures a

14 AR 5–13 • 17 December 2009

common understanding of Army requirements and priorities as well as the constraints associated with implementing
them.
(2) The Director, G–37/TR chairs the AMGOSC.
(3) The AMGOSC is held semiannually.

3–4. Programming and budgeting

a. The DCS, G–3/5/7 munitions management office provides Army war reserve/operational, test, and training
munitions requirements to the DCS, G–8 for inclusion in programming and budgeting processes.
b. Title 10, U.S. Code (USC), Title 31 USC, and Defense Finance and Accounting Service–Indiana Manual 37–100
(DFAS-IN 37–100) prohibit Army units from using funds for other than their intended purpose and specify that
munitions may be purchased only with procurement ammunition, Army (PAA) funds or missile procurement, Army
(MIPA) funds, which are controlled at HQDA. It is a Federal offense for units to procure munitions using anything
other than PAA or MIPA funds.
c. Munitions and explosives include but are not limited to, all items of ammunition; guided missiles; warheads;
liquid and solid propellants; high and low explosives; chemical agents; pyrotechnics; cartridge and propellant-actuated
devices; and associated components and substances that present real or potential hazards to life or property. These
restrictions are designed to protect Army personnel from injury or death, to ensure inventory control and accountability,
and to comply with the intent of existing laws and regulations.
d. The only authorized exceptions to this procurement policy are when—
(1) USASOC has procured nonstandard ammunition and explosives under United States Special Operations Com-
mand (USSOCOM) authority.
(2) TRADOC has procured nonstandard munitions under an agreement with the Federal Bureau of Investigation
(FBI) to operate the hazardous devices range.
(3) ATEC has procured ammunition to support RDT&E requirements for which standard items are unavailable or
unsatisfactory.

3–5. Total Ammunition Management Information System

a. The TAMIS is the DCS, G–3/5/7’s automated tool for managing munitions requirements, priorities, and forecasts.
TAMIS also contains a reports application for HQDA and subordinate organizations’ use to assist with determining
operational readiness and to support the management of Army munitions. The DCS, G–3/5/7 munitions management
office uses TAMIS to—
(1) Generate training requirements.
(2) Generate CL and SL requirements for operational forces.
(3) Generate ACOM stockage objectives.
(4) Manage authorizations, forecasts, and requests of Army munitions in support of valid requirements.
(5) Capture transactional data from the Standard Army Ammunition System-Modernized (SAAS–MOD) or any
other DCS, G–4 approved system of record for munitions accounting in order to calculate munitions expenditures.
b. Provides Army leaders with reports portraying the status of munitions requirements, authorizations, forecasts, and
expenditures by, for example, event, weapon system, munitions family, DODIC, location, command, and dollar values.
(1) TAMIS contains four distinct types of accounts, which are discussed more in-depth throughout this chapter:
(a) Training (includes STRAC and POI training).
(b) Operational.
(c) Test.
(d) NET.
(2) The TAMIS is a hierarchical based, Internet-accessible system available from anywhere in the world. The
TAMIS live site is located at https://tamis.army.mil. The TAMIS training site is located at https://www.tamis.org. Users
require an Army Knowledge On-line (AKO)/Defense Knowledge On-line (DKO) password or common access card
(CAC) to log into TAMIS.
c. The TAMIS is centrally administered by the DCS, G–3/5/7 munitions management office, but each command-
level organization that has munitions requirements must have a TAMIS account and manager for its organization. Each
Army Command-level organization administers and manages its segment of the TAMIS hierarchy.
d. The TAMIS managers should be knowledgeable of their organization’s munitions requirements and priorities.
This knowledge will be critical in the event authorized quantities of munitions are insufficient to resource all of the
unit’s or organization’s requirements, or in the event the Army authorizes a substitute DODIC to resource a
requirement.
e. The DCS, G–3/5/7 munitions management office strongly encourages commanders and munitions managers at all
levels to use the wide variety of reports tools in TAMIS to monitor their requirements, authorizations, forecasts, and
expenditures. Large differences between authorizations and forecasts or expenditures may be indicators of readiness
shortfalls, particularly late in a FY.

AR 5–13 • 17 December 2009 15

 f. For additional TAMIS assistance, users may contact TAMIS customer support.

3–6. Authorizations
a. An authorization is the quantity of munitions that a unit or organization may receive in support of its DCS, G–3/
5/7 munitions management office-validated requirements. The DCS, G–3/5/7 munitions management office ensures
support for the most critical requirements by publishing munitions authorizations in TAMIS.
b. Command ammunition managers must distribute munitions authorizations in a timely manner because units that
do not have an authorization cannot forecast or receive munitions in support of their validated requirements.
c. All issues of Army munitions to Army organizations in support of war reserve and operations, testing, training,
NET, and Title X requirements must be based upon a munitions authorization in TAMIS (except for special forces’
nonstandard ammunition, unless they choose to manage it in TAMIS, and developmental munitions and munitions
components used for testing).
d. TAMIS authorizations must be distributed to the UIC level in the TAMIS hierarchy in order for a unit to forecast,
request, and receive munitions.
e. Units or organizations in the TAMIS hierarchy may or may not receive authorizations in each account. Authoriza-
tions cannot be moved between any of the TAMIS accounts without DCS, G–3/5/7 munitions management office and
DCS, G–4 approval.
(1) Training account. This account allows units to manage authorizations issued to support validated training
requirements. These requirements consist of—
(a) Individual, collective, and CTC weapons training requirements based on DA Pam 350–38.
(b) Institutional POI training for both Army schools and mobile training teams.
(2) Operational account. This account allows units to manage authorizations issued to support validated operational
requirements. These requirements consist of—
(a) Combat load.
(b) Sustainment load.
(c) OPLOADs.
(d) OPROJs.
(3) Test account. This account is for munitions authorized to support all Army test requirements for standard Army
munitions.
(4) NET account. This account is for munitions authorized to support NET associated with the fielding of new
equipment or munitions, in accordance with a TRADOC-approved NET plan.
f. Authorizations for serviceable, unused munitions are credited back to the user’s UIC account in TAMIS upon
reconciliation of the request (e581) document as long as the fiscal year remains unchanged.
g. Unused munitions authorizations will not be carried over from one fiscal year to the next fiscal year for training,
test, NET or OPLOAD. Authorizations for CL, SL, and OPROJs remain in a unit’s account continuously from one
fiscal year to another until the requirement changes.
h. Authorizations for OPROJs. During hostilities, once a unit has consumed all of its operational authorizations,
additional authorizations are automatically posted to the requesting unit’s operational account so that the lack of an
authorization does not prevent a unit from receiving munitions. Units must have had at least one authorization in their
operational account in order for the automatic replenishment of authorizations to occur. The intent of this rule is not to
deny units in hostilities the receipt of required munitions support.
i. The primary forums through which the DCS, G–3/5/7 munitions management office distributes munitions authori-
zations are the TA4C and the MIDP conference.
(1) The primary responsibilities of the TA4C and MIDP conference are to—
(a) Authorize the use of Army munitions and prioritize munitions allocations in support of validated requirements.
(b) Direct the positioning of Army munitions in order to support Army readiness and sound stockpile management.
(c) Serve as a venue for informing munitions managers about munitions management policy, trends, requirements,
and logistics issues.
(2) The TA4C generally is held in April and August of each year. The TA4C distributes initial authorizations in
TAMIS for all conventional ammunition requirements at the April TA4C and adjusts them as needed at the August
conference.
(3) The MIDP conference is held just prior to or after the April TA4C and distributes authorizations and allocations
for Army missiles.
(4) The DCS, G–3/5/7 and the DCS, G–4 munitions managers co-chair the TA4C and MIDP conference. A
representative from all Army Command-level organizations having conventional ammunition requirements must attend
TA4Cs. A representative from all Army Command-level organizations having missile requirements must attend MIDP
conferences. Attendees must be knowledgeable of the command’s requirements and priorities and be prepared to make
decisions for their commands.

16 AR 5–13 • 17 December 2009

 (5) Authorizations distributed at the TA4C and MIDP conference support the upcoming fiscal year’s (FY) ammuni-
tion and missile requirements. In the event emergency requirements occur outside of the TA4C and MIDP conference,
command-level organizations may submit via email to DCS, G–3/5/7 munitions management office a by-DODIC and
nomenclature list of the required munitions and quantities, justification, and an assessment of the operational impact of
not receiving them. Such requests must be the exception rather than the rule.
(6) Guidance specific to MIDP conferences:
(a) Missiles are high-demand, low-density munitions that require intensive management at all levels.
(b) The Army does not procure live missiles for training. Units receive live missiles for training only if they are
available through shelf-life management.
(c) Inventory data at the MIDP conference must include—
1. By-DODIC quantities of serviceable missiles that will be available to support operational requirements.
2. By-DODIC and location, quantities of serviceable, shootable missiles that are expected to reach their shelf life
within 3 years and which are not expected to receive any further shelf-life extensions. The DCS, G–3/5/7 munitions
managers will give priority to using these missiles to support valid training and test requirements.
3. Supply points will issue only the DODICs and quantities of missiles authorized in TAMIS to a unit or
organization.
4. Units must request an authorization change through command channels if a missile DODIC other than the one
authorized is to be issued.
j. The DCS, G–3/5/7 and G–4 munitions managers’ goal is to fully resource all valid requirements. When supply
constraints exist, command-level munitions managers must be able to identify their critical requirements and the
operational impact of receiving authorizations that are less than their full requirement.
k. The DCS, G–3/5/7 munitions managers will ensure that authorized quantities are closely aligned with available
supply, thereby giving units a reasonable expectation that munitions will be available to support their requirements
when needed.
l. Supply on hand is not justification for an authorization.
m. When possible, the DCS, G–3/5/7 munitions managers will authorize older-model and substitute ammunition for
training and tests in order to facilitate sound stockpile management and prevent the accumulation of aging stocks in the
stockpile. The DCS, G–4 munitions managers will make every effort to issue the specific DODICs and quantities
authorized to a unit or organization.
n. No later than the end of the second quarter annually, Army Commands may turn back ammunition and missile
authorizations they do not intend to use during the remainder of the current fiscal year. The DCS, G–3/5/7 munitions
managers may redistribute these authorizations to support other requirements, if necessary.

3–7. Forecasts
a. Munitions forecasts are monthly estimates of munitions by DODIC, quantity, and location that a unit or
organization plans to draw in support of validated noncombat day-to-day operations, training, or testing.
b. Units and organizations will forecast valid training, test, and NET munitions requirements. Units will forecast
OPLOAD munitions requirements unless operational conditions prohibit meeting the forecasting time line. Units should
forecast CL or SL munitions if time permits but are not required to do so.
c. Materiel developers will forecast all NET munitions requirements in TAMIS unless the DCS, G–3/5/7 has agreed
to support the NET using a unit’s annual training resources, in which case, the unit undergoing NET is responsible for
forecasting the munitions to support NET.
d. Program managers will forecast all test munitions requirements in TAMIS.
e. Accurate forecasts are critical. Inaccurate forecasts are a leading cause of munitions shortage caused by mal-
distribution of Army munitions. Leaders at all levels will monitor and validate their unit forecasts for accuracy.
(1) Units and organizations will not “front load” their forecast to receive more than fifty percent of their annual
authorizations in the first 120 days of a fiscal year without approval from their Army-level command munitions
manager.
(2) Units and organizations will not submit “cookie-cutter” forecasts, wherein authorized quantities are divided by
twelve, with one-twelfth of a unit’s authorizations forecasted monthly, or like quantities submitted across several
months.
f. The TAMIS monitors each organization’s forecasting accuracy by comparing a unit’s expenditures to its forecasts.
TAMIS automatically reports all units’ forecasting effectiveness to their respective Army Command-level munitions
managers.
g. A TAMIS forecast is not essential for an ammunition supply point to issue munitions, but a supply point may
reject any request for issue if the request was not properly forecasted, or if the assets are not available. Unforecasted
requirements may also result in the requesting unit or organization being charged premium transportation fees to cover
the cost of short-notice, unplanned shipments.
h. Prior to the start of a fiscal year, units may forecast in TAMIS but those forecasts are “unapproved” until Army

AR 5–13 • 17 December 2009 17

Command-level munitions managers distribute authorizations for that fiscal year. Commands must distribute authoriza-
tions to their subordinate units to avoid invalidating subordinate unit forecasts.
i. In the execution year (current year), TAMIS will not accept a forecast that will cause the total forecasted quantity
to exceed a unit’s available authorizations.
j. To forecast munitions in TAMIS, each unit must possess an authorization for the DODIC that is required and also
establish an association with an ammunition supply point in TAMIS.
k. Forecast lockout period.
(1) Most ammunition supply points have a forecast lockout period. The lockout period allows logistics organizations
time to configure shipments, arrange transportation, and move munitions to the forecasted location. In CONUS, the
TAMIS lockout period is the 2-month period following the last day of the current month. For example, if the current
date were any day in the month of July, the lockout period would extend through all of August and September, and the
last day of July would be the final date units could increase a forecast for October.
(2) Prior to entering the forecast lockout period, TAMIS automatically reduces each unit or organization’s training,
POI, test, NET or OPLOAD forecast to its available authorizations.
(3) During the lockout period, units cannot increase their forecasted quantities. Any increases to forecasts during the
lockout period require the unit’s command-level munitions manager to coordinate approval with the DCS, G–3/5/7 and
DCS, G–4 munitions managers to ensure they are supportable.
(4) Units may reduce their forecast quantities during the lockout period.
(5) By using the TAMIS forecast move tool, munitions managers at all levels may cross-level forecasts to another
unit any time prior to submitting an electronic DA Form 581 (e581) to request munitions as long as the forecast
quantity, month, and supply point remain the same.
(6) The OCONUS lockout periods vary, depending on a variety of logistical and operational factors. TAMIS
manages OCONUS lockout periods based on each OCONUS command’s preference.
(7) There is no lockout period for CL or SL forecasts. The TAMIS simply treats forecasts for these requirements as
shortages against a valid authorization.
(8) At contractor-operated or other special-purpose munitions sites, the munitions requestor or user arranges trans-
portation and controls the lockout period. Regardless of the transport method or the lockout period, the requesting
organization will forecast its requirements in the ATEC hierarchy in TAMIS before the DCS, G–4 munitions managers
release munitions.

3–8. Requesting munitions

a. The TAMIS enables units and organizations to request munitions (standard and nonstandard) using an electronic
DA Form 581 (e581). Each unit or organization requesting munitions must have an account in TAMIS and must have
an authorization in the account to prepare and submit an e581 to an ammunition supply point.
b. Authorized users complete the e581 in TAMIS and transmit it electronically through command channels to the
ammunition supply point from which forecasted support is requested. Only when TAMIS is unavailable may units
request training, test, and NET or OPLOAD munitions using a paper DA Form 581. Installation munitions managers
are still required to validate the manual DA Form 581 by using TAMIS to ensure that the unit is authorized the
munitions and that the supply is available to support the request. Ammunition supply points may reject manual
munitions requests if they have not been properly validated.
c. Requests for all training munitions will include the DA Pam 350–38 STRAC event(s) and the range designation
where the munitions will be expended. Test and NET e581 munitions requests will include the range designation. The
STRAC event(s) and range selection are listed in the remarks block on the e581 when printed.
d. Training events not listed in STRAC tables will be entered in the non-STRAC event field in TAMIS during
completion of the e581.
e. Electronic routing (requestor, approver, and validater) of the e581 is based on each unit’s individual routing
instructions contained in TAMIS for each munitions account type.
f. Electronic requests for CL or SL follow ordinary TAMIS submission and approval rules, with the exception of
entries for the STRAC event, range selection, and allocation period. These entries are not required for approval or
acceptance at an ammunition supply point.
g. The OPLOAD requests do not require a STRAC event or range entry.
h. Units may create and save contingency e581s in TAMIS for recall and submission when needed. CL and SL
requests for contingency operations do not require a pickup date, ammunition supply point, or allocation period.
i. Units that are supporting a valid test requirement will charge this requirement to the ATEC UIC that has the
authorizations to support the test. By validating the request, ATEC permits the use of its authorizations to support the
test.
j. Units that are going through an approved NET will charge this requirement to the AMC UIC that has the
authorizations to support the NET. By validating the request, AMC permits use of its authorizations to support the
NET.

18 AR 5–13 • 17 December 2009

 k. To request munitions in TAMIS, users must have a TAMIS user ID and password and a CAC. The digital
certificate on the CAC is used to sign the e581 electronically. TAMIS users without a CAC should contact their
munitions manager to obtain a digital signature application from the TAMIS help desk. Digital signature applications
are processed through the TAMIS help desk. A TAMIS-issued ePersona signature may be used in lieu of a CAC to
sign the e581 officially.
l. Signing the e581 in TAMIS requires the DOD private key infrastructure (PKI) to be installed on your computer.
Contact your Director of Information Management (DOIM) or network administrator to ensure that your computer is
configured for electronic signatures prior to attempting an e581. Signed e581 forms are retained in TAMIS for 5 years.
m. In accordance with DA Pam 710–2–1, munitions managers will ensure that appropriate signature card(s) (DA
Form 1687 (Notice of Delegation of Authority-Receipt for Supplies)) and delegation of authority letters are on file at
the supporting ammunition supply point before submitting a munitions request. Requests without a DA Form 1687 on
file at the ammunition supply point or stored electronically in TAMIS will be rejected by the ammunition supply point.
n. The ammunition supply point may use the TAMIS munitions request to print a final DA Form 581 or import it
into SAAS–MOD, Standard Depot System, or other approved DCS, G–4-approved munitions accountability system.
o. Units may use TAMIS to prepare the turn-in DA Form 581, but they will submit these turn-in documents
manually to the ammunition supply point.
p. Units will reconcile training ammunition issues with the ammunition supply point according to DA Pam 710–2–1.

3–9. Expenditures
a. Expenditures are the quantities of munitions per DODIC that a unit or organization fires in support of operations,
training, testing, or NET. Units or organizations will expend only those munitions necessary to achieve their approved
objectives.
b. The TAMIS estimates Army munitions expenditures to assist the DCS, G–3/5/7 munitions management office
with—
(1) Assessing Army weapons training execution and readiness.
(2) Developing critical munitions requirements.
(3) Making programming recommendations during the POM process.
(4) Distributing munitions authorizations in support of valid requirements.
c. To estimate expenditures, TAMIS subtracts a unit’s or organization’s serviceable turn-in quantities from the
quantity issued.
d. For all munitions issued in support of an e581 request, the issuing facility (unit, retail, or wholesale), using
SAAS–MOD or another DCS, G–4 approved system of record for munitions accounting, will electronically transmit all
issue and serviceable turn-in quantities to TAMIS daily if these transactions occurred. If an electronic interface is not
available or functioning between TAMIS and the system of record, the operator of that system will manually transfer
issue and turn-in data to TAMIS each day an issue or turn-in occurred.
e. Upon deployment, units will commence reporting of operational expenditures under the appropriate combatant
command. according to Chairman of the Joint Chiefs of Staff Manual (CJCSM) 3150.14B.
f. Turn-in transactions for issues occurring during a fiscal year must be completed NLT 31 October of that calendar
year. Turn-in transactions occurring more than 31 days past the end of the fiscal year in which the munitions were
authorized must be forwarded to the TAMIS help desk to be recorded in TAMIS.
g. Final expenditure data for all training, NET, OPLOAD, and test expenditures must be in TAMIS NLT 30
November annually. There is no suspense for recording operational expenditures (except OPLOAD), as they are
considered permanent transfers to a unit until cleared from the unit’s property accountability records, according to
applicable Army supply policy.
h. TAMIS credits a unit’s expenditures to the fiscal year in which the authorizations are granted. The only exception
to this is when the turn-in crosses two fiscal years, in which case TAMIS credits the unit’s expenditures to the fiscal
year in which the issue occurred. Events that cross two fiscal years may require separate issue and turn-in documents to
reflect munitions issued in one fiscal year and turned in in another.
i. To the maximum extent possible, ammunition supply points will only issue munitions actually authorized in
TAMIS. In those instances when a supply point must issue a DODIC other than the one authorized and requested, the
following TAMIS expenditure recording rules apply:
(1) Prime and substitute DODICs are mapped to each other in TAMIS. When a substitute is not identified with a
prime DODIC in TAMIS, the DCS, G–3/5/7 munitions management office, in coordination with the affected command
and the DCS, G–4 must approve issue and use of the proposed substitute.
(2) When a prime DODIC is authorized and requested but a valid substitute DODIC is issued and expended, TAMIS
posts the expenditure against the authorized, requested prime DODIC as long as the unit does not have an authorization
for the substitute DODIC. If a unit has an authorization for the substitute item, TAMIS posts the expenditure against
the substitute DODIC. Ammunition supply points may reject munitions requests if they are not properly validated by
the installation ammunition manager.

AR 5–13 • 17 December 2009 19

 (3) When a substitute is authorized, requested, and expended, TAMIS posts the expenditure against the authorized,
requested DODIC rather than against the prime DODIC.
(4) When time constraints prevent a command from obtaining DCS, G–3/5/7 munitions management office approval
of the use of a proposed substitute not identified in TAMIS, Army Command-level munitions managers must
coordinate changes to authorizations within 5 working days following the issue.
(5) Test munitions that will be disassembled and not reassembled into a standard, serviceable configuration are
considered to be expended upon issue, and the issue document for those munitions should be closed out upon issue.
Issue documents for all other munitions will be processed in accordance with all applicable munitions management
policy and regulations.
j. To support range management, users will submit information in TAMIS to report the occurrence of duds and
unexploded ordnance during any training, NET, or testing event. TAMIS alerts users that a dud or unexploded
ordnance report is required. Negative reports are required when dud-producing ordnance is used at any Army
installation. Additional reporting requirements are contained in AR 75–1.

3–10. Readiness Reports

a. The DCS, G–3/5/7 munitions management office is responsible for conducting munitions readiness assessments
and developing reports that enable Army senior leaders to quickly understand the near- and long-term readiness of the
Army munitions program. These reports identify areas where the Army may be incurring operational risk and provide
recommendations for risk mitigation.
b. The Army’s specific metrics for assessing munitions readiness are sensitive and, in some cases, classified. At a
minimum, unclassified metrics should be treated as “For Official Use Only” information and distributed strictly on a
need-to-know basis.
c. Senior leaders routinely receive munitions readiness updates, the most important of which are discussed below.
(1) Munitions readiness review (MRR).
(a) The basis for Army worldwide munitions readiness assessments is the monthly JMC MRR.
(b) The MRR is a web-based readiness assessment tool with drill-down capability that measures the quality and
quantity of Army war reserve and operational (including test) and training munitions for a 24-month period. Army NY
munitions requirements are the yardstick for MRR readiness assessments, which take substitute munitions into account
but only include stocks in select condition codes.
(c) The MRR reflects the integration of munitions information (requirements, inventory, planned production, and so
forth) from several sources and provides the status of each individual DODIC as well as roll-up assessments of
subgroups (such as, .50-caliber armor piercing), groups (such as, .50-caliber), and families (such as, small caliber) of
munitions.
(d) MRR metrics are requirements-based S-ratings (S–1, S–2, S–3) intended to quickly and clearly portray opera-
tional risks and readiness.
(2) Army operations center (AOC) briefings. This assessment, commonly referred to as the “balcony briefing,”
provides the current munitions readiness status for ongoing major operations as well as for war reserve and operational
(including test) and training munitions readiness. The DCS, G–3/5/7 munitions management office works with the
DCS, G–4, the DCS, G–8, and the ASA(ALT) to conduct the required analysis and reports showing the current status
of the worldwide munitions stockpile and the current status of munitions stocks in any ongoing operations for which
senior leaders request updates.
(a) The source of data for the current status of munitions in a theater of operations in which contingency operations
are ongoing is the theater’s munitions managers. The sources of data for the current worldwide munitions status reports
are the DCS, G–3, the DCS, G–4, the DCS, G–8, and the ASA(ALT) munitions managers.
(b) Munitions managers for contingency operations have latitude regarding how they portray their munitions
readiness, but their reports must be requirements-based, incorporate on-hand substitute munitions at the retail and
wholesale levels and in the hands of troops, and mirror the JMC MRR format as closely as possible.
(c) Current worldwide war reserve and operational and training munitions readiness updates and supporting docu-
mentation are based upon munitions information in the JMC MRR.
(d) The Army’s specific metrics for assessing munitions readiness are sensitive and can be obtained from the DCS,
G–3/5/7 munitions management office on a need-to-know basis. In general, however, the metrics are requirements-
based S-ratings (S–1, S–2, S–3) intended to clearly portray operational risks and readiness.
(e) Using MRR data, the DCS, G–3/5/7 munitions management office coordinates the development of detailed
backup reports and charts that ensure munitions managers share a common understanding of munitions readiness issues
during the monthly updates. In support of this effort, the ASA(ALT) provides up-to-date acquisition, production, and
delivery information; the DCS, G–8 provides updated programming and funding information; and the DCS, G–4
provides updated inventory and stockpile management information.
(f) Based upon the detailed backup reports and charts, the DCS, G–3/5/7 munitions management office also
develops a condensed readiness assessment that specifically addresses requirements, funding, bottom-line issues, get-
well assessments, and key comments for any munitions group that is not S–1.

20 AR 5–13 • 17 December 2009

 (3) POM readiness review (PRR). An MRR-like readiness assessment that measures the quality and quantity of
Army war reserve and operational (including test) and training munitions for a 6-year POM period (to be developed).
(4) Munitions positioning review (MPR).
(a) The MPR is a JMC assessment tool that measures the distribution of munitions relative to requirements by
geographical region.
(b) DCS, G–3/5/7 munitions management office-approved stockage objectives provide the yardstick for MPR
assessments.
(c) The MPR integrates information about stockage objectives and on-hand prime munitions, and substitutes
munitions in order to make positioning recommendations to the DCS, G–4 in support of Army and combatant
commander objectives.
(d) Stockage objectives are updated annually. The MPR is updated semiannually to support the semiannual TA4C
and annual MIDP.
(e) MPR metrics are requirements-based S-ratings intended to quickly and clearly portray the effect of munitions
distribution upon Army munitions readiness by geographic region.
(f) The MPR uses the same DODICs, subgroups, groups, and families of munitions as the MRR.
(5) Strategic readiness update (SRU).
(a) The DCS, G–3/5/7 Training Directorate provides a monthly training readiness update as part of the SRU chaired
by the Vice Chief of Staff of the Army (VCSA). The DCS, G–3/5/7 munitions management office includes a training
munitions readiness assessment in this monthly update.
(b) The DCS, G–3/5/7 munitions management office uses munitions expenditures and unit forecast data from
TAMIS to conduct the training munitions readiness assessment. The analysis compares each component’s forecasts and
actual expenditures to their approved Army weapons training strategies in DA Pam 350–38.
(c) The SRU addresses only home station training. It does not address TRADOC institutional weapons training or
mobilization weapons training.
(6) Force validation committee (FVC) update.
(a) The DCS, G–3/5/7 Training Directorate provides a training readiness update for individual units identified by the
FVC. As part of the assessments, the DCS, G–3/5/7 munitions management office presents a training munitions
readiness assessment as part of the overall training readiness update for each unit.
(b) The DCS, G–3/5/7 munitions management office assessment compares each unit’s DA Pam 350–38 training
munitions requirements to their current munitions authorizations and provides the DCS, G–3/5/7 Director of Training
with an analysis by munitions family of each unit’s training munitions resourcing status.
d. The DCS, G–4 is responsible for the Quarterly Readiness Report to Congress and for providing input as required
to the Joint Forces Readiness Review. This report will be coordinated with the DCS, G–3/5/7 munitions management
office prior to submission.

AR 5–13 • 17 December 2009 21

Appendix A
References

Section I
Required Publications

AR 73–1
Test and Evaluation Policy (Cited in paras 2–1g, 2–3g(1).)

AR 710–2
Supply Policy Below the National Level (Cited in para 2–1n(3).)

AR 735–5
Policies and Procedures for Property Accountably (Cited in para 1–4h.)

DA Pam 385–64
Ammunition and Explosives Safety Standards (Cited in para 2–4s(5).)

DA Pam 710–2–1
Using Unit Supply System (Manual Procedures) (Cited in para 3–8m.)

DA Pam 350–38
Standards in Training Commission (Cited in para 1–5i(1)(f).)

DODI 3000.4
DOD Munitions Requirements Process (Cited in para 1–5a.)

Section II
Related Publications
A related publication is a source of additional information. The user does not have to read it to understand this
publication.

AR 25–1
Army Knowledge Management and Information Technology

AR 75–1
Malfunctions Involving Ammunition and Explosives

AR 350–1
Army Training and Leader Development

AR 700–19
U.S. Army Munitions Reporting Systems

AR 700–28
Committee for Ammunition Logistic Support

AR 710–1
Centralized Inventory Management of the Army Supply System

AR 725–50
Requisition, Receipt, and Issue System

CJCSM 3150.14B
Chairman of the Joint Chiefs of Staff Manual (Available at www.dtic.mil)

DA Pam 700–19
U.S. Army Munitions Reporting System

22 AR 5–13 • 17 December 2009

DFAS–IN 37–100 Manual
Disbursing Operations

DODD 5160.65
Single Manager for Conventional Ammunition (SMCA)

FM 7–0
Training for Full Spectrum Operations

Section III
Prescribed Forms
This section contains no entries.

Section IV
Referenced Forms

DA Form 581
Request for Issue and Turn-in of Ammunition

DA Form 1687
Notice of Delegation of Authority-Receipt for Supplies

DA Form 2028
Recommended Changes to Publications and Blank Forms

AR 5–13 • 17 December 2009 23

Glossary
Section I
Abbreviations

ACOM
Army Command

AMC
Army Materiel Command

AMGOSC
Army munitions general officer steering committee

AMRCoC
Army munitions requirements council of colonels

AMSCoC
Army munitions strategy council of colonels

AMS/CP
Army munitions strategy/campaign plan

APS
Army pre-positioned stocks

ARSTAF
Army Staff

ASA(ALT)
Assistant Secretary of the Army for Acquisition, Logistics and Technology

ASA(I&E)
Assistant Secretary of the Army for Installations and Environment

ASCC
Army Service Component Command

ASF
Army strategy flotilla

ASP
Ammunition supply point

ATEC
Army Test and Evaluation Command

ATSC
Army Training Support Center

CAA
Center for Army Analysis

CAC
common access card

CCDR
combatant commander

CL
combat load

24 AR 5–13 • 17 December 2009

CoC
council of colonels

CONPLAN
contingency plan

CONUS
continental United States

CP
campaign plan

CRA
Continuing Resolution Authority

CTC
Combined Training Center

DA
Department of the Army

DCS, G–3/5/7
Deputy Chief of Staff for Operations and Plans

DCS, G–4
Deputy Chief of Staff for Logistics

DCS, G–8
Deputy Chief of Staff for Programs

DDI
dummy, drill, and inert

DOD
Department of Defense

DODIC
Department of Defense identification code

DRU
Direct Reporting Unit

EOD
explosive ordnance disposal

FVC
force validation committee

FY
fiscal year

G-35
Strategic Plans and Policy

G-37
Force Management/Training

HQDA
Headquarters, Department of the Army

AR 5–13 • 17 December 2009 25

JMC
Joint Munitions Command

LIN
line item number

MCLS
munitions combat load study

MCO
major combat operation

MIDP
missile distribution plan

MIPA
missile procurement, Army

MPR
munitions positioning review

MRP
munitions requirements process

MRR
munitions readiness review

MS
milestone

MS A
milestone A (initial capability document)

MS B
milestone B (capability development document)

MTOE
modified table of organization and equipment

MTT
mobile training team

NET
new equipment training

NLT
not later than

NY
near year

OCONUS
outside continental United States

OMB
Office of Management and Budget

OPLAN
operational plan

26 AR 5–13 • 17 December 2009

OPLOAD
operational load

OPROJ
operational project

OSD
Office of the Secretary of Defense

OUSD
Office of the Under Secretary of Defense

OUSD(AT&L)
Office of the Under Secretary of Defense (Acquisition, Technology and Logistics)

OUSD(C)
Office of the Under Secretary of Defense (Comptroller)

OY
out year

PAA
procurement ammunition Army

PA&E
program, analysis, and evaluation

PEO
program executive office

POI
program of instruction

POM
program objective memorandum

PTD
phased threat distribution

QWARRM
qualitative war reserve requirement for munitions

RC
Reserve Component

RDT&E
research, development, test, and evaluation

SA
sufficiency assessment

SAAS–MOD
Standard Army Ammunition System-Modernized

SL
sustainment load

SMCA
single manager for conventional ammunition

AR 5–13 • 17 December 2009 27

SO
stockage objectives

SOF
special operations forces

SRC
standard resource code

SRT
special reaction team

SRU
strategic readiness update

STRAC
Standards in Training Commission

TADSS
training aids, devices, simulators, and simulations

TA4C
Total Army Ammunition Authorization and Allocation Conference

TAMIS
Total Ammunition Management Information System

TAMR
total Army munitions requirement

TDA
tables of distribution and allowances

TOE
table of organization and equipment

TR
threat report

TRADOC
Training and Doctrine Command

UIC
unit identification code

USASOC
United States Army Special Operations Command

WEBTAADS
Web-Based Total Army Authorization Document System

WG
working group

WSR
weapons system review

28 AR 5–13 • 17 December 2009

Section II
Terms

Allocation
An allocation is the supply distributed to resource a requirement.

Army Command
A command directly subordinate to HQDA as specified in AR 10–5. All commands are referred to as ACOMs in this
regulation.

Authorization
An authorization is the quantity of munitions that a unit or organization may receive in support of its DCS, G–3/5/7-
validated requirements. The DCS, G–3/5/7 munitions management office ensures support for the most critical require-
ments by publishing munitions authorizations in Total Ammunition Management Information System (TAMIS).

Combat load (CL)

A CL is the standard quantity and type of munitions an individual weapon, crew-served weapon, or a weapons platform
and its MTOE-designated munitions carriers are designed to hold. Combat loads for bulk munitions (for example,
grenades, signals, and so forth) are not associated with a weapon or weapon platform. Bulk munitions CLs are assigned
by standard resource code (SRC) and reflect the quantity of munitions required to give units a realistic level of
capability and flexibility.

D-day
Unnamed day on which operations commence or are schedule to commence.

Dummy, drill, and inert ammunition

Ammunition on that has the appearance of actual service munitions but does not contain any explosives components.

E–Date (effective date)

A six-position numeric code that signifies the actual date that an authorization document is effective; for example,
041001. The first two digits are the calendar year, the third and fourth are the month, and the fifth and sixth are the
day.

Electronic signature
An electronic representation of a person’s signature. The electronic signature is most often contained in a computer file
or on a common access card (CAC). TAMIS uses electronic signature software to digitally sign the e581 used in Total
Ammunition Management Information System (TAMIS). By combining the electronic signature with an e581, a
request for munitions may be routed through munitions managers to the ammunition supply point (ASP) using
computers. Like a written signature, the purpose of an electronic signature is to authenticate a person’s identity.

Expenditure
Expenditures are the quantities of munitions, by Department of Defense identification code (DODIC), that a unit or
organization fires in support of operations, training, testing, or new equipment training (NET).

Forecast
A forecast is a monthly estimate of munitions by Department of Defense identification code (DODIC), quantity, and
location that a unit or organization plans to draw in support of validated noncombat day-to-day operations, training, or
testing.

Mobilization
The act of preparing for war or other emergencies through assembling and organizing national resources. It is the
process by which the Armed Forces, or part of them, are brought to a state of readiness for war or other national
emergency. This includes assembling and organizing personnel, supplies, and materiel for active military service,
federalizing the Reserve components, extending military terms of service, and taking other actions necessary to convert
to a wartime posture.

Nonstandard ammunition
Nonstandard munitions are those munitions that have not completed safety-type classification and may pose unaccep-
table risks to personnel or equipment. They do not have a National Stock Number (NSN) or Department of Defense

AR 5–13 • 17 December 2009 29

identification code (DODIC) and are not managed by the Joint Munitions Command (JMC) or the Army Missile
Command (AMCOM).

Operational Load (OPLOAD)

The munitions that Army units require to support or conduct a broad range of day-to-day operational missions; for
example, installation explosive ordnance disposal (EOD), special reaction team (SRT) operations, ceremonies, quarry
operations, guard missions, force protection, special operations forces (SOF) predeployment site surveys, and so forth.

Operational Project (OPROJ)

Operational projects are munitions set aside for a specific unit or mission according to AR 710–2.

Prioritization
Prioritization is establishing the relative importance of one requirement or resource over another and is an operational
function.

Requirement
A munitions requirement is the type and quantity of munitions the Army must have to successfully execute its war
fight, daily operational, test and training missions successfully.

Stockage objectives (SO)

SO is the quantity of munitions (sustainment load, operational load (OPLOAD), operational project (OPRO)), Army
pre-positioned stocks (APS), and training) required to ensure that all training and operations in a theater can be
conducted until resupply occurs.

STRAC Standard
The total types and quantities of all munitions required to execute individual qualification and crew certification tasks
and a live-fire exercise event (Active Army) and a field training exercise (Reserve Component) each year, as defined in
DA Pam 350–38. The standard is the minimum quantity of ammunition that the Army requires for a given year for
home station training. Program of instruction (POI) and Combined Training Center (CTC) requirements are additive to
the STRAC standard.

STRAC strategy
The total of all types and quantities of all munitions required to execute 100 percent of the Army’s home station
training strategy each year, as defined in DA Pam 350–38. The strategy reflects the Army’s maximum home station
training ammunition requirement for a given year. Program of instruction (POI) and Combined Training Center (CTC)
requirements are additive to the STRAC strategy.

Sustainment Load (SL)

SL is the munitions needed to initiate and support a force’s operations until resupply can be provided.

Training Ammunition
All Class V items to be consumed during training.

Unit identification code (UIC)

A six-character code assigned to a specific unit that can be used to identify that unit.

Section III
Special Abbreviations and Terms
This section contains no entries.

30 AR 5–13 • 17 December 2009

UNCLASSIFIED PIN 999999–999