Military

6-1. In the early 1970s, SAAS was developed to provide automated status of ammunition assets for the theater or MACOM (i.e., SAAS level 1). In 1982, SAAS level 3 added Class V management capability and other stock control activities to the corps support command. The two baselines were merged as SAAS 1/3 in 1986. As this system evolved, the requirement to maintain visibility and accountability became more demanding. During Operation Desert Storm, the system was not able to meet wartime requirements. In 1994, SAAS was placed in limited moratorium, and resources were redirected toward developing a modernized system, SAAS-MOD.

6-2. SAAS-MOD replaces and combines SAAS-1/3, SAAS-4, and SAAS-DAO in a modular design concept. It is the approved STAMIS for all Class V conventional retail ammunition inventory control or management. SAAS-MOD automates and integrates ammunition management functions among users, storage sites, and theater managers. It operates on deployable NDI hardware in both tactical and nontactical environments at the theater, corps, ASP, division, and installation levels.

6-3. SAAS-MOD provides total functional integration of existing and future retail level Class V information management systems. SAAS-MOD operates on IBM-compatible PCs using COTS software whenever possible. SAAS-MOD application software handles the unique requirements involved in maintaining ammunition data.

6-4. SAAS-MOD gives commanders and ammunition managers the capability for producing accurate, timely, and near real-time Class V information during peacetime and contingency operations, as well as wartime operations on a highly mobile battlefield. It provides management and stock control for conventional ammunition, GMLR, and C&P materials. SAAS-MOD operates at all of the following functional levels in the theater of operations:

• Corps and theater MMCs or MACOM-equivalent.
• DAO and ATP.
• ASA (TSA, CSA or ASP).
• Installation ASA.

6-5. SAAS-MOD supports ammunition managers at three functional levels in a theater of operations (MMC, ASP, and DAO) by providing the capability to pass and receive near real-time data. System functions are divided into the following ammunition management areas:

• General core operations.
• Materiel management.
• Requirements management.
• Primary operations.
• Ammunition surveillance management.
• SAAS interface.

These SAAS software areas incorporate distinct functions and processes. Below is an overview of the types of products that can be produced and the types of information that can be processed.

6-6. General core operations are performed at the three functional levels of SAAS for the system to produce accurate and timely information. They cover establishment and maintenance of the military organizational structure; facility resources; reference data; and ammunition requirements, authorizations, and assets for all functional levels within a theater or corps. These operations are discussed below.

6-7. Organization management incorporates the processes used to identify all activities receiving or providing ammunition support by name, UIC, organization address, DODAAC, and RIC (where applicable). Command and ammunition logistic support structures are also shown.

6-8. Security management functions identify valid user(s) by maintaining profiles for each user. These functions are accessed through the Maintain User menu and the User Manager for Domains menu.

6-9. Information support procedures provide access to facilities to establish and maintain complete, accurate, and current logistics records. These records facilitate requisition, inventory control, and shipping.

6-10. System administrative functions include archiving and restoring data, other file maintenance as needed, maintaining site defaults for MILSTRIP documents, and domain administration.

6-11. Maintenance resource functions include identifying resources needed in the theater to manage ammunition assets. Resource functions also include maintaining the location of all assets, the movement of assets, inventory statistics, and mass transfers.

6-12. Accounting functions enable SAAS-MMC managers to establish and maintain the management account structure in the theater. The structure contains recording account codes (detailed accounts), summary account codes, and WARS purpose codes.

6-13. The recording account identifies stockage requirements by DODIC at the ASP for a specific purpose (for instance, a unit, project, or operation). The summary account codes, which are roll-ups of the applicable recording accounts, identify requirements at both the corps and theater levels and relate to a more general purpose. The WARS purpose codes (i.e., war reserve, training, operational projects, and ammunition basic load) identify the total requirements for the theater. The accounting function is used to report requirements for training and ammunition.

6-14. Ammunition materiel management functions are performed only at theater and corps MMCs. These functions relate to the overall management of authorizations, requirements, and redistribution of ammunition assets within the theater. They may be performed at a lower level only when authorized. Material management functions are outlined below.

6-15. The processes available for identifying excesses and shortages compare specified theater and corps requirements to available assets (on-hand/in-transit) and display excess and shortage conditions. This function allows direct access requisition or directives processes to order, redistribute, or report excess.

6-16. The available selections allow managers to establish a requisition, create a follow-up transaction, and generate a request for cancellation and/or request modification of a requisition. When a requisition is initiated or modified, the system updates due-in and due-out status.

6-17. The directives process maintains current due-in and due-out status in the background and contains selections for the following functions:

• Procedures to prepare, view, and update MROs.
• Procedures to prepare, view, and update local shipment directives.
• Procedures to maintain shipment notifications for shipments within or coming into the theater or corps.
• Procedures to initiate and maintain MILSTRIP excess reports and generate shipment directives for the ASP when shipping instructions are received from the CCSS.

6-18. This batch process handles all transactions coming in through the communications process from DAAS, SPBS-R, and any SAAS activity. It routes and processes all MILSTRIP, SAAS, and SPBS-R transactions. Besides updating the SAAS tables, the process creates output for WARS and other SAAS activities.

6-19. The functions of managing ammunition requirements are performed at the DAO and ATP. They include maintaining ammunition requirements and visibility and distribution within the division. The DAO is responsible for distributing ammunition, verifying unit requirements, and tracking ammunition coming into the division. Requirements management functions are described below.

6-20. Task force support processes allow the manager to create and update task force data for a military organization. These processes also identify ATPs providing support.

6-21. Management processes in wartime allow the manager to update, submit, and monitor ammunition requirements and to facilitate distribution within the division.

6-22. Management processes in peacetime allow the DAO to manage requirements and basic load, operational load, and training ammunition for the division.

6-23. Primary operations functions, also called ammunition asset management, are normally performed at the ASP. They are used to receive, store, issue, and account for ammunition in a retail ammunition stock record account. The account may be located at an ammunition DS/GS company or the responsible installation organization. Functions are described below.

6-24. Stock control processes cover all transactions used to maintain and update the stock records and supporting documents of a formal stock record account. The processes available are as follows:

• Stock control monitoring (supply studies, due-in/due-out analysis, and excess).
• Stock control operations (receipts, issues, turn-ins, shipments, inventories, and ammunition maintenance transactions).

6-25. Storage management processes include maintenance of storage site (warehouse) profiles, explosive safety profiles, and compatibility information.

6-26. The on-site ammunition inspectors perform ammunition surveillance management functions. These tasks are associated with acquiring and maintaining the records of ammunition quality and safety at ATPs or ASPs.

6-27. SAAS-MOD receives and transmits data from/to several systems at each functional level. SAAS-MOD uses magnetic media, mail, and communications networks to accomplish all interfaces.

6-28. SAAS-MOD provides a standard ammunition management tool that is capable of the following:

• Maintaining current status of all ammunition within the command ASAs and ATPs.
• Computing complete rounds, days of supply, configured loads, and authorized stockage levels.
• Providing data used by the manager to determine redistribution of assets.
• Supporting Class V logistic estimates based on weapon systems.
• Maintaining data on US and foreign munitions for use in determining Q-D and NEW computations and weapon systems interoperability.
• Supporting surveillance stockpile management.
• Supporting ad hoc query, including data imported and exported to other systems.
• Evaluating and providing distribution history and distribution plan.
• Requisitioning from the NICP if acting as a TAMMC or from a higher node if acting as a CMMC.
• Maintaining and calculating the status of CSR.
• Planning, determining, and forecasting future requirements.
• Maintaining and evaluating consumption of ammunition historical data.
• Computing and determining transportation requirements for movement by type and number of carriers.
• Maintaining asset visibility aboard transport vehicles passing through the system including due-ins and due-outs.

6-29. SAAS-MOD receives and sends data to several systems. When the communications link is down, operators can input data manually if it is received off-line. All data received by communications is normally batch-processed after the communications portion of the interface is complete. All SAAS activities within a theater provide data for each other. SAAS-MOD contains the following interfaces:

• WARS receives daily SAAS transactions that affect assets.
• MILSTRIP data received and sent to the CCSS.
• MILSTRIP and MILSTAMP data sent and received through the DAAS.
• FEDLOG provides up-to-date catalog information.
• TAMIS-R provides allocation and authorization data for training ammunition.
• CSSCS interface keeps tactical commanders informed on status of selected ammunition.
• DAMMS-R (TC-AIMS-II) allows the MMCs and ASPs to receive information on in-transit shipments.
• SPBS-R provides on-hand quantities at the unit.
• Corps SAAS interfaces with corps DAMMS-R (TC-AIMS-II) and CSSCS activities.
• ASPs, TSAs, and CSAs providing training ammunition support send training expenditure information to TAMIS-R.
• SAAS-DAO uses SPBS-R and ULLS-S4 to track weapon densities, basic load requirements, and training ammunition support.

6-30. The NDI hardware required to operate SAAS is purchased through a DOD computer contract that provides complete systems. The user gets the most modern equipment available on the contract at the time of purchase and installation. The equipment is tailored for each of the three functional levels and to the site that operates it. Quantities of hardware at each location are based on unit missions and are outlined in the BOIP for SAAS. The equipment described in this paragraph is subject to change because of improvements in technology.

6-31. The computer hardware at the theater and corps MMC level consists of a network file server, 1 to 14 PCs for user terminals, 1 to 8 laser printers, a UPS, surge suppressor, LAN equipment, and modems.

6-32. The computer hardware at the DAO and ATP levels consists of a network file server, a printer, surge suppressor, laptop for each ATP, LAN equipment, modems, and AIT equipment. AIT equipment includes the following:

• RF interrogator/laser scanner and docking stations.
• Portable printer.
• Thermal printer.

6-33. The hardware for the ASP consists of a network file server, a printer, surge suppressor, 3terminals (PCs or laptops with monitor), LAN equipment, modems, and AIT equipment. AIT equipment is the same as listed above.

6-34. The SAAS System Administrator Manual can be viewed and downloaded at http://www.gcss-army.lee.army.mil/saashdbk/default.htm. This manual identifies all software required to operate or continue operations in an emergency. See Appendix B of the End User Manual for more information.

6-35. Several circumstances can disrupt the normal operations of an automated system. The SAAS End User Manual provides courses of action to be considered and/or included in the development of contingency plans. Table 6-1 lists those SAAS-MOD critical functions that must continue to be performed manually in the event of system failure.

6-36. All SAAS-MOD users are responsible for identifying and reporting problems and submitting recommended changes on an ECP-S for software enhancements. Control logs (automated or manual) are maintained by all units submitting problem reports and ECP-S. Submit problem reports using DA Form 5005-R.

6-37. SAAS-MOD corrected shortcomings of the legacy system and incorporated lessons learned from Operation Desert Storm. The system was developed in incremental blocks: Block 1-A (MMC) and Block 1-B (ASP and DAO). Full system fielding has resulted in the removal of the DAS-3 and TACCS from the SAAS inventory. It is anticipated that all functional applications currently in SAAS-MOD will evolve into the Global Combat Support System-Army.