Mobile-Based Systems And Methods For Processing Fuel Orders

• US 20090070175A1
• Filed: 08/05/2005
• Published: 03/12/2009
• Est. Priority Date: 10/07/2004
• Status: Abandoned Application

• Current Assignee: Kenan Advantage Group Incorporated (Littlejohn & Company LLC)
• Original Assignee: Kenan Advantage Group Incorporated (Littlejohn & Company LLC)
• Inventors: Cundey, James Howard, Haidle, David Russell, Bauqhman, Thomas Jason
• Application Number:
  US11/631,208
• Publication Number:
  US 20090070175A1
• Time in Patent Office: Days
• US Class Current: 705/8
• CPC Class Codes: G06Q 10/0631 Resource planning, allocation, distributing or scheduling for enterprises or organisations
• CPC Class Codes: G06Q 10/08 Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
• CPC Class Codes: G06Q 10/083 Shipping
• CPC Class Codes: G06Q 10/087 Inventory or stock management, e.g. order filling, procurement or balancing against orders
• CPC Class Codes: G06Q 30/04 Billing or invoicing

Abstract

Systems and methods for handling fuel orders. A system can include application software that is configured for operation upon a vehicle operator'"'"'s communication device. The application software receives fuel order data and displays the received data to the fuel vehicle driver. The received fuel order data is for use in handling logistics related to picking up from a fuel source and delivering petrochemical fuel to a fuel destination.

Claims

1. A system for handling fuel orders, comprising:

application software configured for operation upon a vehicle operator'"'"'s communication device;

wherein the application software receives fuel order data and displays the received data to the fuel vehicle driver;

wherein the received fuel order data is for use in handling logistics related to picking up from a fuel source and delivering petrochemical fuel to a fuel destination;

wherein rules residing on the communication device are applied to information obtained from the fuel vehicle driver to determine whether the obtained information is valid with respect to at least one of the rules;

wherein rule application results are provided to a remote server system;

wherein sum of gross fuel quantity entered by the driver is provided to the remote server system for use in detecting a data mismatch that arises when the sum of the gross fuel quantity entered by the driver does not match gross fuel quantity specified by an order'"'"'s associated bill of lading.

2. The system of claim 1, wherein the vehicle driver accesses the fuel order data from the communication device which is located with the driver or with the driver'"'"'s fuel transportation vehicle and picks up fuel per the fuel order data.

3. The system of claim 2, wherein software operating on the communication device tracks exceptions that arise while the driver is fulfilling orders provided in the fuel order data;

wherein the driver provides reasons for the exceptions to the communication device.

4. The system of claim 2, wherein the communication device contains a human-machine display interface so that a driver can interact with the communication device.

5. The system of claim 2, wherein the rules allow for validating data received in real-time from the driver that relates to the pickup, transportation or delivery of ordered fuel.

6. The system of claim 2, wherein communication with the communication device occurs at least in part over one of the following:

a cellular communication network;

a satellite communication network;

or a wireless communication network.

7. The system of claim 2, wherein a communication device is a cellular phone or a device that keeps track of vehicle data in real-time in order to comply with department of transportation (DOT) governmental and legal requirements.

8. The system of claim 7, wherein different types of communications networks are used to communicate with the remote server;

wherein the tracking device is configured to communicate over a WIFI communications network or cellular communications network;

wherein fuel order data is provided to the tracking device that comprises a bulk of the fuel order data needed by a driver to complete the driver'"'"'s daily scheduled fuel orders;

wherein type of cellular phone is selected for the driver based upon whether the cellular phone'"'"'s company provider has coverage at the point where a vehicle is initially located before picking up loads.

9. The system of claim 1, wherein the communication device communicates over a network with a remote computer server;

wherein the server provides the fuel order data to the vehicle driver through the drivers'"'"' communication device;

wherein the server receives information that is generated based upon the interaction between the driver and the communication device.

10. The system of claim 9, wherein the communication device periodically polls the server to determine whether new fuel orders are to be completed by a driver or to determine whether an order has changed or to determine whether an order has been removed.

11. The system of claim 9, wherein the communication device receives from the server a viewing condition;

wherein the viewing condition is selected from the following group comprising;

a driver can only view one assigned order at a time;

a driver can view all assigned orders but cannot change sequence of the assigned orders; and

a driver can view all assigned orders and can change the sequence of the assigned orders.

12. The system of claim 9, wherein the information received by the server that is generated based upon the interaction between the driver and the communication device includes reasons for delay in the pickup/delivery process, fuel quantity loaded, fuel quantity delivered, customer information, supplier information, and accessorial information.

13. The system of claim 12, wherein the server integrates ordering, scheduling, and billing processes that are associated with the vehicle'"'"'s fuel delivery with the data that is supplied remotely by the communication device in the field in real-time or in near real-time.

14. The system of claim 13, wherein the server contains fuel order processing rules to identify data mismatches arising from data provided by the driver'"'"'s communication device.

16. The system of claim 14, wherein if a communication device does not have access to data necessary to validate a driver'"'"'s input to the communication device, then the server'"'"'s fuel order processing rules perform a validation of the driver'"'"'s input based upon order data stored in the server'"'"'s database.

17. The system of claim 16, wherein the communication device is configured to capture information from a driver such that a snapshot of the handling of the order by the driver is ascertainable when the communication device is not within a communication blind spot and can communicate the captured information to the server.

18. The system of claim 9, wherein the information provided to the communication device from the driver includes delivery confirmation information and load data that is sent to the server for use in performing order billing and payroll operations.

19. The system of claim 9, wherein the communication device collects actual logistics data for use by the server in determining whether the actual logistics data is in compliance with planned logistics data.

20. The system of claim 9, wherein the communication device is configured to access data from a global positioning satellite (GPS) location system in order to ascertain real-time position of the driver'"'"'s vehicle;

wherein the GPS accessed data is for use in determining whether the driver is in compliance with scheduling instructions based upon whether the current location of the vehicle matches or corresponds to the location expected in the scheduling instructions.

21. The system of claim 9, wherein fuel delivery orders are forwarded by the server to the communication device according to an order assignment determined by an order scheduling center;

wherein the driver utilizes the communication device to receive the fuel delivery orders so that the orders can be fulfilled in the manner specified by the scheduling center.

22. The system of claim 21, wherein based upon a driver receiving the fuel order-related data on the driver'"'"'s communication device, the driver proceeds to the one or more specified fuel loading facilities in order to fulfill fuel orders;

wherein bill of lading information is provided to the driver'"'"'s communication device, wherein the driver enters the actual delivered information into the communication device;

wherein the rules are configured to verify whether the driver entered information matches the bill of lading information.

23. The system of claim 22, wherein the driver entered information also includes delivery confirmation information and load data that is sent to the server for use in performing billing and payroll operations.

24. The system of claim 1, wherein a user interface screen is displayed on the communication device to the vehicle'"'"'s driver in order to determine identity of the driver;

wherein determination of the driver'"'"'s identity ensures that a driver can only access orders for which the driver is responsible.

25. The system of claim 1, wherein the communication device determines whether the previous driver of the vehicle had delivered previous orders associated with the vehicle;

wherein if a fuel retain amount exists from a previous shift, a user interface is displayed on the communication device and configured such that the driver can indicate an acknowledgement of the fuel retain amount;

wherein the user interface is configured such that if the driver disagrees with the fuel retain amount, the user interface provides information to the driver on how to handle the fuel retain amount.

26. The system of claim 1, wherein the communication device is configured to receive orders by compartment or aggregated by product;

wherein a user interface is configured so that a driver is asked to enter gross fuel quantity by compartment;

wherein the communication device performs a validation of the driver entered compartment data;

wherein the user interface is configured to display, to the driver, products expected to be placed in a compartment.

27. The system of claim 1, wherein a user interface screen is displayed on the communication device to the vehicle'"'"'s driver for use in entering gross fuel quantity that was loaded in a compartment;

wherein a bill of lading number is entered and is a loading rack'"'"'s unique number from a bill of lading.

28. The system of claim 27, wherein a tracking number is entered and is a unique bar-coded number adhered to the bill of lading;

wherein the tracking number is for use in linking an imaged physical bill of lading to the order being handled by the driver;

wherein a supplier number is entered and is indicative of supplier of the product;

wherein a purchase order number is entered through the user interface screen by the driver and is indicative of a customer reference number.

29. The system of claim 27, wherein if the entered gross fuel quantity associated with the bill of lading does not match the gross fuel quantity for the vehicle, then a discrepancy notification is generated on the display of the communication device;

wherein the communication device is configured to receive a reason from the driver regarding the discrepancy.

30. The system of claim 1, wherein a timer is started about when the vehicle has arrived at the fuel loading rack;

wherein about when the driver completes the fuel loading or entry of loading information into the communication device, the timer stops and the elapsed time is compared to an elapsed time criterion;

wherein if the elapsed time exceeds the criterion, then a notification is provided to the driver in order for a delay reason to be provided;

wherein depending upon the delay reason and an arrangement with the customer regarding a delay, a computer system is configured to bill the customer for the delay.

31. The system of claim 1, the communication device is configured for entry, by product or by tank, of a stick reading for a fuel product;

wherein the communication device is configured to determine whether the starting stick reading is below a predetermined value;

wherein if the starting stick reading is not below the value, then the communication device is used to handle a fuel retain situation and communicate to the driver how to handle the retain situation.

32. The system of claim 31, wherein handling the fuel retain situation through use of the communication device includes using the communication device to select compartments that were not delivered in full;

wherein the communication device is configured to display fuel quantity that was loaded in those compartments;

wherein if the compartments are unbroken, the communication device is configured to receive a reason for the fuel retain;

wherein if the compartments are broken, the communication device is configured to prompt the driver for an estimated fuel quantity still onboard which can be delivered through an ad hoc delivery.

33. The system of claim 32, wherein the communication device is configured to store a record for each compartment so that the compartment can be delivered before returning to the rack or the compartment can be top-loaded and delivered with the next order or a successive order;

wherein when the retain is delivered, the corresponding record stored on the communication device is amended to include the order number with which it was delivered.

34. The system of claim 33, wherein when the retain is delivered, the corresponding record stored on the communication device is amended to include a second bill of lading associated with the delivery.

35. The system of claim 1, wherein the communication device is configured to allow entry by a driver of a stick before reading value, a stick after reading value, and a water before reading related to a fuel product;

wherein if the driver was unable to perform a full drop for a particular delivery, then the communication device is configured such that the driver must indicate, to the communication device, data regarding the retain situation;

wherein the retain situation data includes amount of fuel that has been retained in a trailer;

wherein a full drop includes all or substantially all of the fuel is delivered for a particular delivery.

36. The system of claim 35, wherein the communication device is configured to perform in real-time mathematical calculations based upon the stick before and after reading values to determine if the stick reading values correspond to the received fuel order data with respect to amount that the communication device expects that a tank should have;

wherein a notification is generated if there is a discrepancy in the values corresponding to the received fuel order data;

wherein the driver enters in real-time a reason for the discrepancy.

37. The system of claim 1, wherein the communication device is configured to allow entry of a bill of lading identifier and a corresponding carrier specific tracking number;

wherein source of a carrier specific tracking number is identified by using a sheet of pre-printed decals that is provided to a driver by dispatch;

wherein a carrier specific tracking number is identified through a bar code associated with a decal;

wherein a bar code scanning device is used by a driver to scan in the bar code from the decal in order to specify to the communication device a carrier specific tracking number;

wherein a decal is placed onto a bill of lading form in order to associate the bill of lading form with a carrier specific tracking number.

38. The system of claim 37, wherein the communication device is configured to allow entry by a driver of gross fuel quantity loaded for a fuel product and delivery stop;

wherein a fuel gross amount field is displayed to a driver and whose value is automatically determined based upon order data received from a remote server over a wireless communication network.

39. The system of claim 38, wherein the communication device is configured to allow entry by a driver of gross fuel quantity loaded for an order and the net fuel quantity loaded for the specified fuel component based upon information provided in an associated bill of lading form having a specified bill of lading identifier;

wherein if a driver is issued multiple bills of lading at a fuel rack, then the communication device is configured to display fuel quantity entry screens to the driver for each bill of lading.

40. The system of claim 37, wherein the communication device is configured to provide entry by a driver of multiple fuel components if an order includes a fuel product that is created through a splash blend at load time.

41. The system of claim 37, wherein the communication device is configured to provide entry by a driver of accessorial condition data related to a fuel order delivery.

42. The system of claim 37, wherein the communication device is configured to provide to a driver an interface by which a fuel component can be added to a fuel product that was not specified in the fuel order data originally provided to the communication device.

43. The system of claim 42, wherein the communication device is configured not to permit the driver to remove a fuel component from a fuel product that has only one component defined.

44. The system of claim 37, wherein the communication device is configured to interact with a driver to handle an unplanned pickup or an unplanned delivery;

wherein the pickup or delivery is unplanned because the pickup or delivery was not provided in the fuel order data originally received by the communication device.

45. The system of claim 44, wherein the communication device is configured to receive fuel data related to the unplanned pickup or delivery from the driver;

wherein the received fuel data includes what fuel product was loaded.

46. The system of claim 1, wherein the communication device is configured for interaction with a driver if amount of fuel loaded exceeds an order amount specified by the fuel order data or is below the order amount by a pre-specified amount;

wherein the interaction includes obtaining from the driver a reason for the amount of fuel loaded exceeding or being below the order amount.

47. The system of claim 1, wherein the communication device receives, over a wireless communication network, software updates for use on the communication device;

wherein a micro edition virtual machine operates on the communication device that handles software operations on the communication device.

48. The system of claim 1, wherein the communication device is configured to communicate with a remote server and with a rack automation system over one or more networks that includes a wireless communications system;

wherein a rack automation system is located at a fuel loading facility and monitors dispensing of fuel from storage into a vehicle;

wherein operative to notification from the communication device that the driver'"'"'s vehicle is within a pre-specified distance from the fuel loading facility, the server determines which order the vehicle is fulfilling;

wherein the server provides order data and driver or vehicle identification to the rack automation system;

wherein when the driver arrives at the fuel loading facility, the rack automation system handles the driver'"'"'s order based upon the provided order data and driver or vehicle identification, thereby decreasing delay between when the driver arrives at the fuel pickup location and when the driver can begin loading fuel onto the vehicle.

49. The system of claim 48, wherein the server providing order data and driver or vehicle identification to the rack automation system comprises early notification of a pickup;

wherein the early notification results in reserving fuel required to fulfill the order against a supplier'"'"'s allocation;

wherein the reserving ensures that an adequate amount of fuel is available to fulfill the driver'"'"'s order.

50. The system of claim 1, wherein the communication device is configured to communicate with a remote server and with a rack automation system over one or more networks that includes a wireless communications system;

wherein a rack automation system is located at a fuel loading facility and monitors dispensing of fuel from storage into a vehicle;

wherein the communication device is configured for accessing data from a global positioning satellite (GPS) location system in order to ascertain real-time position of the driver'"'"'s vehicle;

wherein the communication device uses the GPS data to determine whether a driver'"'"'s vehicle is within a pre-specified distance from the fuel loading facility;

wherein operative to the GPS data indicating that the driver'"'"'s vehicle is within a pre-specified distance from the fuel loading facility, the communication device sends a notification to the server that the vehicle is nearing the pickup location;

wherein operative to the notification from the communication device, the server determines which order the vehicle is fulfilling;

wherein the server provides order data and driver or vehicle identification to the rack automation system;

wherein when the driver arrives at the fuel loading facility, the rack automation system handles the driver'"'"'s order based upon the provided order data and driver or vehicle identification, thereby decreasing delay between when the driver arrives at the fuel pickup location and when the driver can begin loading fuel onto the vehicle.

51. The system of claim 50, wherein the server receives from the rack automation system whether any problems exist with respect to fulfilling the order;

wherein the server is configured to process data from the rack automation system regarding a problem that a destination location does not have sufficient product in inventory to fulfill the order and that an alternate load terminal should be used;

wherein the server receives from the rack automation system bill of lading information related to a fuel order;

wherein the server transmits information received from the rack automation system in order to pre-populate information in data fields that a driver would have to manually enter through the communication device, thereby decreasing amount of manual entry by the driver;

wherein the transmitted information includes bill of lading information provided by the rack automation system.

52. The system of claim 51, wherein use of order-related information from the rack automation system by the server and the communication device decreases order billing errors.

53. The system of claim 51, wherein the server uses information provided by the rack automation system is used to verify information provided by the communication device related to an order.

54. The system of claim 53, wherein use of order-related information from the rack automation system by the server and the communication device decreases order billing errors.

15. (canceled)

55. A system for handling fuel orders, comprising:

application software configured for operation upon a vehicle operator'"'"'s communication device;

wherein the communication device is a fuel vehicle'"'"'s device that was originally programmed to collect vehicle safety-related and fuel tax-related data and is configured to include additional processor-implemented instructions to communicate and process fuel order data sent from a remote server;

wherein the application software receives fuel order data and displays the received data to the fuel vehicle driver;

wherein rules residing on the communication device are applied to information obtained from the fuel vehicle driver to determine whether the obtained information is valid with respect to at least one of the rules;

wherein rule application results are provided to a remote server system for fuel order reporting purposes;

wherein sum of gross fuel quantity entered by the driver is provided to the remote server system for use in detecting a data mismatch that arises when the sum of the gross fuel quantity entered by the driver does not match gross fuel quantity specified by an order'"'"'s associated bill of lading.

56. The system of claim 55, wherein the application software is configured such that operation of the application software minimizes or eliminates interfering with the safety-related operations of the communication device.

57. The system of claim 56, wherein the application software includes a software application programming interface (API) that maintains priority of safety-related operation of the communication device.