The information contained (vehicle registration number, fuel type, DoD activity address code/stock record account number [DoDAAC/SRAN]) on the VIL key and Serv-O-Plate is critical for the fuel-consumption data to flow to OLVIMS. One example of possible errors would be an incorrect registration number or lack thereof; in which case, OLVIMS simply disregards the record.
For bases without automated fuels service stations, the fuel data are manually entered into OLVIMS via an MZ transaction.
Fuel-consumption data for specific vehicle registration numbers can be retrieved by OLVIMS without any further action.
Fuel-consumption data from the coupons are gathered by vehicle operations and passed to vehicle maintenance for manual input into OLVIMS via an MZ transaction.
On all three flowcharts (Figures 5, 6, and 7), fuel-consumption data flow to DESC, except the data fed directly into OLVIMS. Prior to 1 October 2001, data flowed from SBSS to OLVIMS.
An interface requirement agreement between FAS and OLVIMS was established on 20 February 2001.
The OLVIMS query and download capability provides the Air Force visibility of fuels obligation data resident in the FAS Enterprise Server.
To access the Purple Hub, each OLVIMS user must establish a user identification and password by filling out Defense Logistics Agency Form 1811.
Base-level vehicle managers use the priority-buy module of OLVIMS to develop input to their MAJCOMs.
The priority recall field in the Automated Fleet Information System/MAJCOM Automated Fleet Information System programs and modernized OLVIMS could be relabeled to identify MEL vehicle authorizations.
Rename the priority recall field in the fleet management module of modernized OLVIMS to identify MEL authorizations.
Eventually, PECs should be added to OLVIMS as an independent field for sorting vehicles.