1. DENVER INTERNATIONAL AIRPORT FUEL IMPORT INTERFACE
FUEL IMPORT INTERFACE
MAXIMO TRANSPORTATION 6.3

2. EQUIPMENT TOTALS FUEL USED MULTI FORCE FUEL SYSTEM
DIA CURRENTLY OPERATES
1750 PIECES OF EQUIPMENT
1028 POWERED UNITS AND
FUELING OUT OF MULTI
FORCE FUEL SYSTEM.
FUEL USED 12/08 TO 12/09
458,195 GAL DIESEL
261,180 GAL UNLEADED
59,074 GAL CNG
FF SYSTEM TOTAL 2009
40,080 TRANSACTIONS
454 METER EDITS TOTAL
1.13 METER EDITS PER 1000
TRANSACTIONS
AVERAGE TRANSACTIONS
PER DAY = 110
2140 ACTIVE USERS

3. REASONS TO IMPORT METER READINGS INTO MAXIMO
METER DRIVEN PREVENTIVE MAINTENANCE
FUELING INFORMATION IN ONE DATA BASE (REPORTS, COSTS, USE HISTORY)

4. MULTI FORCE FUEL SYSTEM
TWO REMOTE ISLAND TERMINALS ARE USED TO CAPTURE DATA DURING THE DISPENSING OF FUEL.
A TOTAL OF 17 FUEL DISPENSERS ARE USED TO DISPENSE 3 TYPES OF FUEL. INCLUDING BULK FILLING OF MOBILE FUELING TRUCKS
UNLEADED
DIESEL
CNG
FUEL CAN BE DISPENSED 24 HOURS A DAY 7 DAY A WEEK.

5. MULTI FORCE FUEL SYSTEM
AT THE FUEL FORCE CONTROLLER THE VEHICLE OPERATOR MUST ENTER –
VEHICLE METER READING
DRIVER NUMBER
UNIT NUMBER
HOSE NUMBER
BEFORE THE SYSTEM AUTHORIZES FUEL TO BE DISPENSED.
CAPTURED DATA IS THEN UPLOADED BY MODEM AT PREDETERMINED TIME INTERVALS TO THE FUEL FORCE SERVER.

6. SOLUTION OVERVIEW
THE SOLUTION INTERFACE WAS DEVELOPED BY DENVER INTERNATIONAL
AIRPORT IT DEPARTMENT.
RAY SISNEROS - DEVELOPER
RAYNA BRANNON – DEVELOPER
THE FUEL FORCE SOLUTION CONSISTS OF
PERL SCRIPT (FUELFORCE.PL)
TWO FILE SHARES
A FOXPRO DATABASE (FUELFORCE.DBC)
A MICROSOFT 2008 SERVER
A BATCH SCRIPT (fuelforce.bat)
A FUEL FORCE LOGIN PASSWORD
A SERVER 2008 SCHEDULED TASK

7. USER INTERFACE FF PERL SCRIPT
THE USER INTERFACE FOR FUELFORCE PERL SCRIPT OUTPUTS A ROW AND ROWCOUNT OF THE SUCCESSFUL RECORDS PULLED FROM THE FOXPRO DATABASE. THE SCRIPT RUNS THE FOLLOWING QUERY:
MY $SQL = "SELECT * FROM FUEL LOG WHERE TXN_TM > {$YESTERDAY}";
THE QUERY PULLS ALL RECORDS WHICH ARE GREATER THAN YESTERDAY. SUBSEQUENTLY, ONLY RECORDS THAT ARE IN YESTERDAYS DATE RANGE ARE WRITTEN TO THE FUEL LOG FILE

8. OUTPUT FILE
THE BATCH SCRIPT RUNS EVERY MORNING AT 6:00 AM AND PLACES THE OUTPUT FILE IN A SHARED DRIVE FILE ON THE NETWORK FOR FLEET PERSONAL TO USE FOR IMPORT INTO MAXIMO.
THE OUTPUT FILE DISPLAYS THE MAXIMO VEHICLE ID, FUEL TYPE, FUEL QUANTITY, AND TRANSMIT DATE TIME STAMP.

9. IMPORTING METER TRANSACTIONS
IMPORTING OUTPUT FILE INTO MAXIMO
DUE DILIGENCE & RESPONSIBILITIES

10. IMPORTING OUTPUT FILE INTO MAXIMO
SELECT THE IMPORTED METER TAB

11. IMPORTING OUTPUT FILE INTO MAXIMO
SELECT A DATA IMPORT TEMPLATE

12. IMPORTING OUTPUT FILE INTO MAXIMO
SELECT SITE FOR IMPORTED TRANSACTIONS

13. IMPORTING OUTPUT FILE INTO MAXIMO
SELECT CHECK BOX FOR IMPORT READINGS

14. IMPORTING OUTPUT FILE INTO MAXIMO
CHECK SELECT FILE BOX TO CHOSE FILE TO IMPORT

15. IMPORTING OUTPUT FILE INTO MAXIMO
CHECK BROWSE AND SELECT FILE TO IMPORT

16. IMPORTING OUTPUT FILE INTO MAXIMO
SELECT FILE TO IMPORT

17. IMPORTING OUTPUT FILE INTO MAXIMO
FILE PATH IS DISPLAYED NOW, CLICK THE OK BUTTON TO IMPORT

18. IMPORTING OUTPUT FILE INTO MAXIMO
OUTPUT FILE CREATED FROM FUEL FORCE IS PUT THRU THE IMPORT TEMPLATE

19. IMPORTING OUTPUT FILE INTO MAXIMO
COUNT OF METER RECORDS CREATED WILL DISPLAY

20. IMPORTING OUTPUT FILE INTO MAXIMO
METER RECORDS HAVE NOW BEEN IMPORTED INTO THE METER TRANSACTION TABLE

21. IMPORTING OUTPUT FILE INTO MAXIMO
TO CREATE METER READINGS CLICK ACTION MENU, IMPORTED METER READINGS, CREATE METER READINGS

22. IMPORTING OUTPUT FILE INTO MAXIMO
SELECT CREATE READINGS

23. IMPORTING OUTPUT FILE INTO MAXIMO
DEPENDING ON THE NUMBER OF RECORDS IMPORTED IT SHOULD TAKE BETWEEN 3 TO 7 MINUTES FOR ALL OF THE READINGS TO BE CREATED.

24. IMPORTING OUTPUT FILE INTO MAXIMO
A DIALOG BOX WILL SHOW UP AND LIST THE NUMBER OF READINGS CREATED ALONG WITH THE NUMBER OF METER RECORDS WITH ERRORS

25. IMPORTING OUTPUT FILE INTO MAXIMO
NOW THAT READINGS HAVE BEEN CREATED YOU NEED TO CLEAR THE METER TRANSACTION TABLE AND YOU DO THIS BY CLICKING ON THE ACTION MENU, IMPORTED METER READINGS, DELETE ALL CREATE METER READINGS

26. IMPORTING OUTPUT FILE INTO MAXIMO
A WARNING BOX WILL COME UP WARNING YOU THAT ALL READING-CREATED RECORDS WILL BE DELETED. IT IS OK TO DELETE THESE READINGS BECAUSE THEY HAVE ALREADY BEEN WRITTEN TO THEIR DESIGNATED EQUIPMENT METER TABLES.

27. IMPORTING OUTPUT FILE INTO MAXIMO
NOW THAT ALL READING-CREATED RECORDS HAVE BEEN CLEARED FROM THE TRANSACTION TABLE YOU ARE LEFT WITH THE RECORDS THAT COULD NOT HAVE READINGS CREATED FROM THEM BECAUSE OF VARIOUS ERRORS.

28. IMPORTING OUTPUT FILE INTO MAXIMO
DUPLICATE READING ERRORS ARE CREATED WHEN FUELING FOR ONE REASON OR ANOTHER THE OPERATOR HAS MADE MULTIPLE ENTRIES INTO FUEL FORCE. EXAMPLES ARE, THE LEVER BOUNCED DOWN AND BACK UP, LONG HOOK TIMED OUT, SHORT HOOK TIMED OUT.

29. IMPORTING OUTPUT FILE INTO MAXIMO
DUPLICATE READING ERRORS SHOULD BE DELETED. BECAUSE THEY ARE DUPLICATES OF RECORDS ALREADY CREATED IN THE EQUIPMENT METER RECORDS AND ARE NOT NEEDED.

30. IMPORTING OUTPUT FILE INTO MAXIMO
OUT OF SEQUENCE ERRORS NORMAL OCCUR WHEN THE TRANSACTION METER READING IS GREATER THAN METER READING OF THE LAST METER UPDATE ALREADY IN THE DESIGNATED EQUIPMENT METER IN MAXIMO. A COMMON EXAMPLE IS A FLEET TECH HAS UPDATED THE RECORD BEFORE THE METER IMPORT IS COMPLETED.

31. IMPORTING OUTPUT FILE INTO MAXIMO
APPARENT ROLLOVER ERRORS NORMAL OCCUR WHEN THE TRANSACTION METER READING IS LESS THAN METER READING OF THE LAST METER UPDATE ALREADY IN THE DESIGNATED EQUIPMENT METER IN MAXIMO. A COMMON EXAMPLE IS A OPERATOR OR FLEET TECH ENTERED THE WRONG METER READING OR A READING FROM THE WRONG METER.

32. IMPORTING OUTPUT FILE INTO MAXIMO
APPARENT ROLLOVER AND OUT OF SEQUENCE ERRORS ARE RESEARCHED IN METER HISTORY IN MAXIMO AND IN FUEL FORCE AND CORRECTED IF POSSIBLE. AFTER CORRECTING EITHER THE DATE OR METER READING IN THE EQUIPMENT METER HISTORY THE CREATE METER READING PROCESS CAN BE RUN AGAIN. OCCASIONALLY YOU WILL NOT BE ABLE TO CORRECT A METER AND THEN THE RECORD IS JUST DELETED.

33. KEYS USERS AT DIA MAINTENANCE IN FUEL FORCE MAINTENANCE IN MAXIMO
DUE DILIGENCE
KEYS USERS AT DIA
MAINTENANCE IN FUEL FORCE
MAINTENANCE IN MAXIMO

34. KEYS USERS AT DIA FLEET MAINTENANCE MAINTENANCE CONTROL IT DEPARTMENT
FLEET MAINTENANCE MAINTAINS ALL VEHICLES
MONITORS ALL FUELING ACTIVITIES INCLUDING PURCHASE OF FUELS
DISPENSING EQUIPMENT AND ENVIRONMENTAL ISSUES
MAINTENANCE CONTROL
PRIMARY CONTACT FOR USERS
METER ISSUES, REPORT REQUESTS, SPILL CONTACT
PRIMARY CONTACT FOR SUPPORT MULTI FORCE FUEL SYSTEMS
IT DEPARTMENT
MAINTAINS FUEL FORCE SERVER
DATA BACK UP AND USER INTERFACE ISSUES

35. Reasonability’s in Fuel force
Fleet will be responsible for entering and updating vehicle records and equipment Alias numbers in Fuel Force.
Changes to vehicle records other than meter readings should be routed thru Fleet.
MCC will maintain and update user records.
MCC will run reports on user activity and move users who have not generated a transaction in the last 18 months into inactive

36. Reasonability’s in Fuel force
MCC will continue to maintain remote island terminals and be the first point of contact for trouble calls at the remote island terminals.
IT and MCC will maintain the Fuel Force server and security access for Key users of database interface.
MCC will continue to be the main contact for reports for other groups.

37. Responsibility's in maximo
WHEN METERS ARE ENTERED INTO THE WORK ORDER BY FLEET TECHS SOMETIMES THEY COME ACROSS METER ENTRIE’S THAT ARE INCORRECT.
A FORM WAS CREATED TO CAPTURE
CHANGES NEEDED IN MAXIMO
METERS
VRMS (COMPONENT CODES)
PM FREQUENCY
PM JOB PLAN CHANGES.
FLEET PLANER IS RESPONSIBLE FOR
CORRECTING METERS
RUNNING IMPORT FUNCTION
MONITORING INTEGRITY OF METER
IMPORTS