MM4618, Lesson 3
Lesson 3
PREPARE AND MAINTAIN WORLDWIDE
AMMUNITION REPORTING SYSTEM FEEDER
REPORTS
TASK
This lesson is based on the following task from STP 9-55B34-SM-TG: 093-406-3123,
Process Independent Mode Transactions.
OBJECTIVES
When you have completed this lesson, you should be able to describe the cycles and files
associated with the worldwide ammunition reporting system at the SAAS-3 level, how to
input data into the system, and how to output WARS feeder reports from the system.
CONDITIONS
You will have this subcourse book and will work without supervision.
STANDARD
You must score at least 75 on the end-of-subcourse examination that covers this lesson and
Lessons 1, 2, 4, and 5 (answer 23 of the 30 questions correctly).
SAAS-3 consolidates stock status reports from storage locations, computes authorized levels, and maintains
the status of munitions on hand and being throughput within the theater. The purpose of the SAAS-3 system is to
provide a standard worldwide method of providing management and stock control for Class V (less nuclear)
munitions by means of management information and stock control computer programs. SAAS-3 may operate
either as an independent corps or be supported by a SAAS level 1 organization. When operating independently,
SAAS-3 will interface directly with CONUS NICPs rather than with SAAS level 1.
Because of their criticality, high dollar value, length of procurement time, and high transportation costs,
munitions require intensive management. The worldwide ammunition reporting system (WARS) for conventional
ammunition and the guided missile and large rocket (GMLR) report for missiles and rockets were designed to
consolidate, evaluate, and manage US Army munitions stockpiles.
The WARS and GMLR reports are regulatory requirements and are submitted to US Army Armament
Materiel Readiness Command (ARRCOM) and US Army Missile Command (USAMICOM) periodically.
Automated preparation of these reports saves a significant amount of manual preparation and assures more
timely and accurate reports. The SAAS-3 system has the capability to produce WARS feeder reports for
submission directly to the NICP.
SYSTEM ORGANIZATION
Cycle Identification Codes
The SAAS-3 system is organized into functions defined as cycles. Each cycle is assigned a system
identification (ID) code, which consists of a six-character code. An example of how a six-character code is broken
down is listed below:
CYCLE AJCD80
CYCLE AJCR09
AJC = SAAS-3
AJC = SAAS-3
D80 = Daily Cycle
R09 = Document Status
Reports
39
Previous Page
