61
3. FMU hose configuration in the software was updated with correct AIM2™ nozzle IDs
(ANIDs), and ANIDs are configured in ascending order. “Grade Positions – XXX” window
should contain column for “ANID”, and ANIDs must be numbered in ascending order.
4. Vehicle records could be modified for proper AIM2™ configuration. Vehicle record
“Fuelmaster Plus” window contains “Passive Status” box, “Authorized” status for
“AIM”, and tab for “AIM II”.
5. User logon privileges allow the encoding of AIM2™ programming keys. “Operator Name:
XXXX” window has AIM2 tab. Under AIM2 tab, options for “AIM2 Programmer” and
“Prokee” are enabled.
6. Authorization list with new AIM2™ records was successfully sent. Go to “Go Online with
FMUs” window, and “Send Auth
. Lists”.
7. AIM2™ transactions were successfully downloaded with correct quantity, odometer and, if
applicable, chronometer data. View information in “Polling Report”.
AIM2™ FMU
CONFIGURATION
8. AIM2™ nozzle tags were installed on the desired hoses with the correct AIM2™ nozzle ID
(ANID) configured to match the FMU hose configuration in the software. Self-explanatory.
9. The FMU Supervisor Prokee
®
/Smartcard, and AIM2™ Programming Prokee
®
/Smartcard
function correctly. Test both keys to ensure the access the appropriate menus.
10. AIM2™ installed vehicles can be successfully programmed from a FMU configured for
AIM2™ programming. As needed, modify an AIM2 vehicle record, send to the FMU, then
program the AIM2 module from the FMU with a Programmer Key.
11. Each hose configured for AIM2™ operation can successfully start, record and terminate an
AIM2™ transaction with an authorized and programmed AIM2™ vehicle. Perform a test
transaction on each hose with a nozzle tag in an AIM2™ equipped vehicle using the
same product.
TRAINING The customer or his/her representative(s) were trained on the following:
12. New features or changes in FuelMaster
®
software. (for upgrade sites) Explain the
differences between the old and new systems.
13. AIM2™ vehicle configuration operations. Vehicle setup in software.
14. Site configuration changes for AIM2™ sites. Site setup in software.
15. Online operations for AIM2™ data. Sending AIM2™ vehicle records to FMU.
16. Reports providing AIM2™ transaction and vehicle data. Show software report options for
AIM2™ transaction and vehicle data.
17. Overview of all AIM2™ hardware, hardware connections and hardware operations. Provide
description of AIM2™ hardware and relationships.
18. Installation process using the AIM2™ Installation Manual. Provide overview of installation
as described in AIM2™ Installation Manual.