Server-based systems and methods for processing fuel orders

• US 20090299805A1
• Filed: 08/05/2005
• Published: 12/03/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: Haidle, David Russel, Baughman, Thomas Jason, Cundey, James Howard
• Application Number:
  US11/631,209
• Publication Number:
  US 20090299805A1
• Time in Patent Office: Days
• US Class Current: 705/70
• CPC Class Codes: G06Q 10/06311 Scheduling, planning or task assignment for a person or group
• CPC Class Codes: G06Q 10/06314 Calendaring for a resource
• CPC Class Codes: G06Q 10/06315 Needs-based resource requirements planning or analysis
• CPC Class Codes: G06Q 10/06316 Sequencing of tasks or work
• CPC Class Codes: G06Q 10/06375 Prediction of business process outcome or impact based on a proposed change
• CPC Class Codes: G06Q 10/08 Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
• CPC Class Codes: G06Q 10/087 Inventory or stock management, e.g. order filling, procurement or balancing against orders
• CPC Class Codes: G06Q 10/1097 Task assignment
• CPC Class Codes: G06Q 20/108 Remote banking, e.g. home banking
• CPC Class Codes: G06Q 30/04 Billing or invoicing
• CPC Class Codes: G06Q 30/0601 Electronic shopping [e-shopping]
• CPC Class Codes: G06Q 50/06 Energy or water supply

Abstract

Systems and methods for handling fuel orders. A system and method can include using a plurality of data interfaces, wherein a first data interface is operable to receive fuel order data from order senders. A database operating on a server is used for storing the fuel order data. Semantic fuel order business rules accessible through a server arc used for constructing groups of orders that comprise shifts so that drivers can fulfill orders specified in the stored fuel order data. A second data interface is operable to send fuel order data generated from the server database to a fuel vehicle operator'"'"'s communication device.

Claims

1. A processor-implemented system for processing fuel orders, comprising:

a plurality of data interfaces;

wherein a first data interface is operable to receive fuel order data from order senders;

wherein the fuel order data is in a first data format;

a database operating on a server for storing the fuel order data;

semantic fuel order business rules accessible through a server for constructing groups of orders that comprise shifts so that drivers can fulfill orders specified in the stored fuel order data;

wherein a second data interface is operable to send fuel order data generated from the server database to a fuel vehicle operator'"'"'s communication device;

wherein the fuel order data sent to the fuel vehicle operator'"'"'s communication device is in a second data format which is a different data format than the first data format;

fuel order processing rules configured to be operable upon a server to determine whether a discrepancy exists with respect to data received from the communication device and generated as a result of a fuel vehicle operator handling an order specified in the fuel order data or as a result of a fuel vehicle operator inputting information as specified in the fuel order data.

2. The system of claim 1, wherein the stored fuel order data is for use in handling logistics and data management associated with picking up from a fuel source and delivering petrochemical fuel to a fuel destination;

wherein the semantic fuel order business rules are used to construct the groups of orders;

wherein at least two orders in a constructed group are from two different customers;

wherein the semantic fuel order business rules are used to transform the received fuel order data into orders which fit within one or more drivers'"'"' work day or shift;

wherein the fuel order data from at least two of the order senders do not contain shift-related information as to which drivers handle which orders;

wherein the semantic fuel order business rules include rules directed to estimated time of arrival for the delivery, shift date and time, and number of hours a driver can work in a shift;

wherein semantic fuel order business rules are used to establish time window criteria within which drivers are to begin and complete the orders provided in the drivers'"'"' respective shifts, wherein the server logs an event if a criterion is not satisfied by a driver;

wherein the semantic fuel order business rules determine a time window criterion.

3. The system of claim 1, wherein the fuel order data is for use by a vehicle driver;

wherein a vehicle driver accesses the fuel order data from a communication device located with the driver or with the driver'"'"'s fuel transportation vehicle and picks up fuel per the fuel order data.

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

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

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

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

7. The system of claim 3, 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.

8. The system of claim 3, wherein a communication device is a cellular phone or on-board truck computer device or a device that keeps track of truck data in real-time for department of transportation (DOT) and other government and legal requirements.

9. The system of claim 8, wherein the communication device is selected because it has coverage at the point where a vehicle is initially located before picking up loads.

10. The system of claim 3, wherein the server and the server database comprise a middleware computer system that is placed between an order sender and fuel vehicle operator'"'"'s communication device.

11. The system of claim 10, wherein the middleware computer system serves as a conduit between order origination systems and drivers who perform fulfillment of the orders.

12. The system of claim 10, wherein the middleware computer system receives information that is generated based upon interaction between drivers and their communication devices;

wherein the information includes at least two types of information selected the group including;

reasons for vehicle delay in the pickup/delivery process;

fuel quantity loaded;

fuel quantity delivered;

customer information;

supplier information;

accessorial information;

fuel quantity loaded by component products;

fuel quantity delivered by component products;

shipment identification;

loading and pickup information;

mileage segment information;

bill of lading identification information;

document tracking information; and

combinations thereof.

13. The system of claim 11, wherein by using a vehicle delay reason provided by the driver, the server determines whether a bill can be sent to the customer for the delay based upon one or more provisions in a contract between the company and the customer;

wherein the middleware computer system contains rules based upon the contract to determine whether the customer can be billed for the delay.

14. The system of claim 11, wherein the middleware computer system interacts with ERP (enterprise resource planning) systems and a billing system;

wherein the middleware computer system integrates ordering, scheduling and billing ERP processes with the data that is supplied remotely through the driver in the field in real-time or in near real-time;

wherein the middleware computer system determines that quantity of delivered fuel corresponds to quantity of the ordered fuel;

wherein the middleware computer system validates billing information associated with the delivered fuel by using the fuel order processing rules and generates a customer bill in a third data format that is sent electronically to the customer.

15. The system of claim 14, wherein the middleware computer system stores in a third data format the received fuel order data and the information generated based upon the interaction between drivers and their communication devices;

wherein storage in the third data format of the fuel order data and of the information generated based upon the interaction allows a payroll system to use the stored fuel order data and the information to perform its payroll and fuel road tax operations.

16. The system of claim 15, wherein the third data format is a generic format relative to the first and second data formats.

17. The system of claim 15, wherein the third data format allows for data to be sent to another system in an Extensible Markup Language (XML) format.

18. The system of claim 15, wherein the use of a middleware computer system allows the server to interact with disparate other software systems;

wherein the disparate other software systems use different data formats;

wherein the middleware computer system acquires information from the disparate systems as well as acquires data from vehicle drivers via their communication devices;

wherein although the disparate systems and communication devices use different data formats, the middleware computer system acquires the disparate systems'"'"' and communication device'"'"'s information and processes it into a standardized format for access by the disparate systems and communication devices;

wherein the standardized format allows another software system to access the data from the middleware computer system without having to understand details of communicating with the other systems and communication devices.

19. The system of claim 1, wherein the fuel order processing rules are configured for use in identifying data mismatches that occur with respect to data provided to the server from the vehicle operator'"'"'s communication device.

20. The system of claim 19, wherein the fuel order processing rules are configured for use in identifying a data mismatch that occurs when sum of the gross fuel quantity entered by a driver does not correspond to gross fuel quantity specified by a bill of lading.

21. The system of claim 19, wherein the fuel order processing rules are configured for use in determining integrity of bills sent to customers for fulfillment of a fuel order by analyzing data provided by a driver via a communication device while fulfilling the fuel order.

22. The system of claim 19, wherein the fuel order processing rules are configured for use in verifying that a driver is handling the order in the manner prescribed by an order sender.

23. The system of claim 22, wherein an order sender includes a computer scheduling system.

24. The system of claim 23, wherein the computer scheduling system receives an order from a customer or from another source;

wherein the computer scheduling system uses optimization techniques to generate the fuel order data to handle, the customer'"'"'s order;

wherein the generated fuel order data is provided to the first data interface.

25. The system of claim 24, wherein instructions for execution upon the server are configured to determine which fuel order-related data is to be sent to which driver'"'"'s communication device;

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 fuel order processing rules are configured to verify whether the driver entered information matches the bill of lading information.

26. The system of claim 25, 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.

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

28. The system of claim 25, 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 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 the location expected in the scheduling instructions.

29. The system of claim 1, wherein the fuel order processing rules are configured to be dynamically updated to reflect changes in validation requirements.

30. The system of claim 29, wherein the fuel order processing rules are updated based upon a fuel order customer imposing a new billing validation requirement;

wherein the updated fuel order processing rules are used for reducing errors associated with the generation of bills sent to the fuel order customer.

31. The system of claim 1, wherein the communication device contains rules to validate a driver'"'"'s fuel order-related input.

32. The system of claim 31, 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 data stored in the database.

33. The system of claim 32, wherein the server validates components in composite products delivered against standard component mix formulas;

wherein if order completion data does not pass validation, the server keeps it in suspense until it is manually corrected to satisfy validation.

34. The system of claim 33, wherein the server relaxes planned versus actual retain rules when dealing with a retain discrepancy situation and the retain discrepancy situation is caused by a customer.

35. The system of claim 32, wherein validation of driver input is performed by the communication device if the data necessary to perform the validation is available on the communication device;

wherein the validation of driver input allows validation to occur even though the communication device is within a communication blind spot and cannot communicate wirelessly with the server.

36. The system of claim 1, 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.

37. The system of claim 1, wherein the server uses the scheduled delivery times to calculate when a load should be completed and logs an event if a predetermined amount of time has elapsed without work having begun on the load.

38. The system of claim 1, wherein if there is more than a predetermined amount of variance between planned delivery times and actual delivery times, the server logs an event;

wherein the server is configured to log an event if a driver ends a shift without completing all loads assigned to the shift;

wherein a logged event indicates which loads are incomplete and need to be addressed.

39. The system of claim 1, wherein the server is configured to provide alerts for events specific to a communication device;

wherein events include;

a request to modify a load being rejected or a request to cancel a load being rejected;

a driver declining a load;

a driver finishing a shift before all loads were completed;

a driver not logging in by a predetermined time;

loads not being fulfilled on schedule;

grab bag loads not being serviced within a predetermined timeframe;

the server receiving completion data with a particular selected reason code.

40. The system of claim 39, wherein the server is configured to receive event criteria from a user which defines under which situations notification is to be issued that an event has occurred;

wherein at least a portion of the event criteria is on a per driver basis.

41. The system of claim 40, wherein notification through email is sent to the user when the user is logged into a computer system for receiving emails.

42. The system of claim 1, wherein the server validates one or more barcode fields received from downstream fuel fulfillment systems against the fuel order processing rules.

43. The system of claim 42, wherein a barcode field is used to identify documents associated with the fuel order fulfillment.

44. The system of claim 43, wherein the documents include a fuel order or bill of lading.

45. The system of claim 44, wherein images of the documents identified by the barcodes are stored in an image repository;

wherein instructions for execution upon a server are configured to retrieve the fuel order-related document images based upon a barcode identifier.

46. The system of claim 1, wherein the server is configured to provide notifications based upon pre-selected events occurring so as to be of use in a real-time decision making process.

47. The system of claim 46, wherein an entity within a fuel order logistics chain is allowed to configure what information is to be provided to the entity based upon the occurrence of a pre-selected event.

48. The system of claim 47, wherein the server calculates the new expected time of arrival by using established trip standards;

wherein the server compares the new expected time to the run out time that had been established in the fuel order data received from an order sender;

wherein if the run out time is earlier than the new expected time of arrival, the server is configured by the entity to send a message to a scheduling center;

wherein the scheduling center takes an action to avoid that run out by moving or rerouting loads.

49. The system of claim 1, wherein for split or multi-consignee loads, the server matches a station number for each consignee to identify the associated assigned delivery number;

wherein in the event that the same station occurs on more than one assigned delivery on a load, the server is configured to not automatically accept order completion data for the load;

wherein the server verifies whether each consignee identified in the order completion data corresponds to one and only one assigned delivery;

wherein if the verification fails, the order completion data for the load is placed in suspense for manual correction.

50. The system of claim 1, wherein the server is configured to receive odometer readings provided by the communication device and uses the readings to calculate the distance traveled for each load and the total distance traveled during a shift for the driver.

51. The system of claim 1, wherein the server is configured to store facility maps for transmission to the communication device;

wherein maps can be stored for unloading facility maps, loading facility maps, and truck domicile locations.

52. The system of claim 1, wherein the server is configured to store highway and other road-related maps.

53. The system of claim 1, wherein the server is configured to accept order completion data for assigned deliveries via automated interfaces from downstream carrier systems.

54. The system of claim 1, wherein the server is configured to validate order completion information, including checking for required fields and valid field types for information provided from the communication device.

55. The system of claim 1, wherein the server is configured to store reason codes for use by a communication device to identify a reason for occurrence of an event related to the driver'"'"'s fulfillment of a fuel order.

56. The system of claim 55, wherein a priority setting is associated with a stored reason code in order to establish a notification priority for when a reason is provided to the server by the communication device.

57. The system of claim 1, wherein access to at least a portion of the fuel-related data stored on the server is based upon data filtering and functionality security assignment;

wherein the data records in the server database are separated using security wrappers established by the data filtering and the functionality security assignment so that only administrative personnel can modify the customer order information.

58. The system of claim 57, wherein the data filtering provides a mechanism with which to permit users to see only the data they are authorized to view;

wherein each time the server data is queried, the resulting data is passed through a filter created for a user prior to being rendered on a display screen or in a report form;

wherein the functionality security assignment provides or restricts access to data on the server by assigning one or more roles to users that indicate one or more permissions in accessing data from the server.

59. The system of claim 1, wherein the server is configured to use a petroleum industry standard to accommodate importing of assigned delivery and supporting data from XML files without reliance on a direct interface into an order scheduling system.

60. The system of claim 1, wherein the server indicates to the communication device a viewing condition;

wherein the viewing condition is at least one viewing condition selected from the following group;

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 an assigned order.

61. The system of claim 1, wherein a memory storage unit is configured to store a data structure;

wherein the data structure is configured to identify groups of orders constructed through use of the semantic fuel order business rules;

wherein the data structure is configured to associate which drivers have been assigned to which shifts and what orders are contained within a shift;

wherein the identification of groups of orders allows the data structure to be used to determine which shifts and drivers are impacted if an order is changed.

62. The system of claim 1, wherein a memory storage unit is configured to store a data structure;

wherein the data structure is configured to store;

information on fuel loading stops;

information on customer delivery stops;

information on order of deliveries;

information on trailer fuel capacities;

wherein the information stored in the data structure is based upon data collected via interfaces that are operable to receive data from the order senders and data from the communication device;

wherein the data structure stores the collected data in a format different than the format of the data received from the order senders and different than the format of the data sent from the fuel vehicle operator'"'"'s communication device.

63. A signal embodied on a carrier wave sent to the communication device that contains the fuel order data of claim 1.

64. A processor-implemented method for fuel order processing, comprising:

receiving a plurality of customer orders;

wherein customer orders are in different data formats;

converting each customer order into a generic data format;

sending customer orders to one or more delivery trucks in a data format for handling by a communication device located with a fuel delivery vehicle;

wherein the sent customer order information is for display to a fuel truck driver;

wherein the generic format is a format that is different than the format in which customer orders are received and different than the format in which data is sent to and received from the communication device;

using fuel order processing rules to determine whether a discrepancy exists with respect to data received from the communication device and generated as a result of a fuel vehicle operator handling an order specified in the fuel order data.

65. Computer-readable medium capable of causing a computing device to perform the method of claim 64.

66. The method of claim 64, wherein an order scheduling system provides an electronic message in a first data format that modifies a previously sent fuel order;

converting the received electronic message into a generic data format and storing the converted data in a database;

determining fuel delivery status of the present order;

generating a data message for transmission to the communication device located with a fuel delivery truck;

wherein the data sent to the communication device is in a format that is different than the data format associated with the order scheduling system;

receiving confirmation of the order cancellation from the communication device.

67. The method of claim 66, wherein the electronic message modifying the fuel order is a message to cancel the fuel order.

68. A signal embodied on a carrier wave containing a customer order for receipt by a communication device, wherein the customer order is generated according to a method comprising:

receiving a plurality of customer orders;

wherein customer orders are in different data formats;

converting each customer order into a generic data format;

sending customer orders to one or more delivery trucks in a data format for handling by a communication device located with a fuel delivery vehicle;

wherein the sent customer order information is for display to a fuel truck driver;

wherein the generic format is a format that is different than the format in which customer orders are received and different than the format in which data is sent to and received from the communication device;

using fuel order processing rules to determine whether a discrepancy exists with respect to data received from the communication device and generated as a result of a fuel vehicle operator handling an order specified in the fuel order data.

69. A processor-implemented system for fuel order processing, comprising:

means for receiving a plurality of customer orders;

wherein customer orders are in different data formats;

means for converting each customer order into a generic data format;

means for sending customer orders to one or more delivery trucks in a data format for handling by a communication device located with a fuel delivery vehicle;

wherein the sent customer order information is for display to a fuel truck driver;

wherein the generic format is a format that is different than the format in which customer orders are received and different than the format in which data is sent to and received from the communication device;

means for using fuel order processing rules to determine whether a discrepancy exists with respect to data received from the communication device and generated as a result of a fuel vehicle operator handling an order specified in the fuel order data.