FUEL IMPORT INTERFACE MAXIMO TRANSPORTATION 6.3

FUEL IMPORT INTERFACE MAXIMO TRANSPORTATION 6.3

EQUIPMENT TOTALSEQUIPMENT TOTALSFUEL USEDFUEL USED

MULTI FORCE FUEL SYSTEMMULTI FORCE FUEL SYSTEMDIA 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

REASONS TO IMPORT METER REASONS TO IMPORT METER READINGS INTO MAXIMOREADINGS INTO MAXIMO

• METER DRIVEN PREVENTIVE MAINTENANCE• FUELING INFORMATION IN ONE DATA BASE (REPORTS, COSTS, USE HISTORY)

MULTI FORCE MULTI FORCE FUEL SYSTEMFUEL 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.

MULTI FORCE MULTI FORCE FUEL SYSTEMFUEL SYSTEM

AT THE FUEL FORCE CONTROLLER THE VEHICLE OPERATOR MUST ENTER –• VEHICLE METER READING• DRIVER NUMBER• UNIT NUMBER• HOSE NUMBERBEFORE THE SYSTEM AUTHORIZES FUEL TO BE DISPENSED.

CAPTURED DATA IS THEN UPLOADED BY MODEM AT PREDETERMINED TIME INTERVALS TO THE FUEL FORCE SERVER.

SOLUTION SOLUTION OVERVIEW OVERVIEW

THE SOLUTION INTERFACE WAS DEVELOPED BY DENVER INTERNATIONALAIRPORT IT DEPARTMENT.

RAY SISNEROS - DEVELOPERRAYNA 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

USER INTERFACE USER INTERFACE FF PERL SCRIPTFF 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

OUTPUT FILEOUTPUT FILETHE 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.

IMPORTING METER IMPORTING METER TRANSACTIONSTRANSACTIONS

IMPORTING OUTPUT FILE INTO MAXIMO

DUE DILIGENCE & RESPONSIBILITIES

IMPORTING OUTPUT FILE INTO MAXIMOIMPORTING OUTPUT FILE INTO MAXIMO

SELECT THE IMPORTED METER TAB


SELECT A DATA IMPORT TEMPLATE


SELECT SITE FOR IMPORTED TRANSACTIONS


SELECT CHECK BOX FOR IMPORT READINGS


CHECK SELECT FILE BOX TO CHOSE FILE TO IMPORT


CHECK BROWSE AND SELECT FILE TO IMPORT


SELECT FILE TO IMPORT


FILE PATH IS DISPLAYED NOW, CLICK THE OK BUTTON TO IMPORT


OUTPUT FILE CREATED FROM FUEL FORCE IS PUT THRU THE IMPORT TEMPLATE


COUNT OF METER RECORDS CREATED WILL DISPLAY


METER RECORDS HAVE NOW BEEN IMPORTED INTO THE METER TRANSACTION TABLE


TO CREATE METER READINGS CLICK ACTION MENU, IMPORTED METER READINGS, CREATE METER READINGS


SELECT CREATE READINGS


DEPENDING ON THE NUMBER OF RECORDS IMPORTED IT SHOULD TAKE BETWEEN 3 TO 7 MINUTES FOR ALL OF THE READINGS TO BE CREATED.


A DIALOG BOX WILL SHOW UP AND LIST THE NUMBER OF READINGS CREATED ALONG WITH THE NUMBER OF METER RECORDS WITH ERRORS


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


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.


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.


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.


DUPLICATE READING ERRORS SHOULD BE DELETED. BECAUSE THEY ARE DUPLICATES OF RECORDS ALREADY CREATED IN THE EQUIPMENT METER RECORDS

AND ARE NOT NEEDED.


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.


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.


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.

DUE DILIGENCEDUE DILIGENCE

KEYS USERS AT DIA

MAINTENANCE IN FUEL FORCE

MAINTENANCE IN MAXIMO

KEYS USERS AT DIAKEYS USERS AT DIA

FLEET MAINTENANCEFLEET MAINTENANCE MAINTAINS ALL VEHICLES

MONITORS ALL FUELING ACTIVITIES INCLUDING PURCHASE OF FUELSDISPENSING EQUIPMENT AND ENVIRONMENTAL ISSUES

MAINTENANCE CONTROL PRIMARY CONTACT FOR USERS

METER ISSUES, REPORT REQUESTS, SPILL CONTACTPRIMARY CONTACT FOR SUPPORT MULTI FORCE FUEL SYSTEMS

IT DEPARTMENTMAINTAINS FUEL FORCE SERVER

DATA BACK UP AND USER INTERFACE ISSUES

REASONABILITY’S IN REASONABILITY’S IN FUEL FORCEFUEL 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

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.

REASONABILITY’S IN REASONABILITY’S IN FUEL FORCEFUEL FORCE

RESPONSIBILITY'S RESPONSIBILITY'S IN MAXIMOIN 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 CAPTURECHANGES 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

Documents

FUEL IMPORT INTERFACE MAXIMO TRANSPORTATION 6.3