Ammunition is Class V supply — the category that most directly determines combat capability. A unit with fuel and food but no ammunition cannot fight. A unit with ammunition but without accurate accountability cannot be resupplied efficiently, because the supply system does not know what was expended. Ammunition management software serves both functions: tracking current on-hand quantities to inform commanders, and recording expenditures to drive resupply calculations.
Ammunition is also the most regulated category of military supply. Explosive ordnance is subject to strict hazardous material (hazmat) storage regulations that govern compatibility between ammunition types, net explosive weight (NEW) limits per storage site, minimum separation distances, and transportation constraints. Software that manages ammunition must enforce these regulations as data constraints, not as manual checklist items.
Lot Number Tracking and Ammunition Safety
Every ammunition item is assigned a lot number at the point of manufacture. The lot number encodes the manufacturer, production line, date of manufacture, and any quality or safety notes associated with that production batch. Lot tracking in ammunition management software is mandatory, not optional: when a safety defect is identified in a lot (a common occurrence as ammunition ages or quality control issues are discovered), the lot must be immediately located across all storage sites and either recalled or placed on restricted use pending investigation.
The software maintains a lot master record for each lot number, linked to all inventory records that reference that lot. A lot recall — triggered by a Ammunition Restricted Use message from the ammunition authority — propagates through the system as a constraint on the inventory records: any issue transaction for items of that lot is blocked until the recall is resolved. The lot master record also tracks the inspection and test dates, shelf life remaining, and storage condition requirements for the lot.
Ammunition condition codes reflect the serviceability of the ammunition. Code A is serviceable, ready for issue. Code F is unserviceable but reparable. Code H is condemned, awaiting disposal. The condition code of each lot determines whether it can be issued, and the software enforces FIFO (first in, first out) issue of same-condition-code ammunition to manage shelf life.
Basic Load Calculations
The basic load is the quantity of ammunition that a unit carries on its organic vehicles and weapons as its initial combat load — the ammunition it has available before any resupply. Basic loads are defined by unit type and weapon system: an infantry company has a defined basic load of 5.56mm rounds per soldier, 40mm grenades per grenadier, and anti-tank missiles per launcher team. Commanders need to know how close each unit's current on-hand quantity is to its prescribed basic load.
Ammunition management software calculates basic load status by comparing current on-hand quantities by NSN against the unit's authorized basic load table — a configuration table that defines the authorized quantities of each ammunition type for that unit type. The output is a basic load percentage by ammunition type: 85% of basic load for 5.56mm, 60% for 40mm, 100% for Javelin missiles. Units below a threshold (typically 70%) are flagged for priority resupply.
During operations, basic load status is updated in near-real-time as expenditures are recorded. The software projects how long current stocks will last at the observed expenditure rate — a Days of Supply (DOS) calculation that drives resupply timing. If the expenditure rate increases (as it does during contact), the DOS calculation updates accordingly, triggering resupply requests before the unit reaches a critically low state.
Hazardous Material Storage Constraints
Ammunition storage is governed by DOD 4145.26-M (Contractors' Safety Manual for Ammunition and Explosives) and equivalent national regulations in NATO countries. The key storage constraint enforced by the software is net explosive weight (NEW) per storage site. Each ammunition type has a defined NEW per round, and the total NEW stored at a single site is capped at limits that vary by site type (permanent magazine, temporary field storage, vehicle-borne).
The software maintains a storage site master record that includes the site's maximum NEW capacity, current stored NEW (computed by summing the NEW contribution of each lot stored at that site), and compatibility constraints between ammunition types stored together. Certain ammunition types cannot be stored together due to sympathetic detonation risk — the software enforces these constraints as hard blocks on storage assignment.
Transportation constraints are similarly enforced: the software validates that convoy loads do not exceed the vehicle's rated NEW capacity and that incompatible ammunition types are not mixed on the same vehicle. These validations run at the transaction level — any move transaction that would violate a storage or transportation constraint is rejected with an explanation before the physical movement occurs.
Consumption Reporting and Resupply Triggers
Expenditure recording — logging the quantities of each ammunition type expended during training or operations — is the data entry point that drives resupply calculations. In a deployed environment, ammunition expenditure is recorded by the unit ammunition NCO on a mobile device application, entering the NSN, lot number, quantity expended, and the date/time of expenditure. The expenditure record is transmitted to the ammunition management server, which updates the on-hand balance and recalculates DOS.
When DOS for any ammunition type falls below the commander's threshold, the system generates a resupply request — a DODIC (Department of Defense Identification Code) request in the standard format — that is submitted to the supporting ammunition supply point. The supply point software receives the request, checks its on-hand stock, and generates a materiel release order for the requested quantities. The resulting convoy load is computed and a shipping manifest is generated for the ammunition handlers.
Key insight: Ammunition data quality directly affects combat capability assessments. Commanders making decisions about the duration of operations, the intensity of fires, and the need to conserve ammunition are relying on the on-hand figures the system reports. If the data is stale, incomplete, or inaccurate — due to missed expenditure recordings, unsynchronized databases, or data entry errors — commanders are making those decisions on wrong information. The system must make expenditure recording fast and simple enough that it happens in real time, not as a batch update hours later.