Electronic run ticket

• US 10,108,936 B1
• Filed: 03/24/2015
• Issued: 10/23/2018
• Est. Priority Date: 12/13/2013
• Status: Active Grant

• Current Assignee: Robert P. Garner
• Original Assignee: Robert P. Garner
• Inventors: Garner, Robert P.
• Primary Examiner(s): Ade, Garcia
• Application Number:
  US14/667,589
• Time in Patent Office: 1,309 Days
• Field of Search: 705 22
• CPC Class Codes: G06F 40/174 Form filling; Merging
• CPC Class Codes: G06Q 20/047 using payment protocols involving electronic receipts
• CPC Class Codes: G06Q 50/06 Energy or water supply

Abstract

Technology for managing electronic run ticket data is provided. In an example method, electronic run ticket data representing a transaction is received from a client device. The electronic run ticket data may be stored in an exchange data store. A participant to the transaction may be identified and the identity of the participant may be stored with the electronic run ticket data in the exchange data store. A request may be received from the participant to the transaction to access the electronic run ticket data and access to the electronic run ticket data may be provided to the participant.

Claims

1. A computing device that is configured to implement a run ticket exchange, comprising:

a processor;

a memory in electronic communication with the processor;

instructions stored in the memory, the instructions being executable by the processor to;

receive electronic run ticket data from a plurality of client devices, wherein the electronic run ticket data represents one or more transactions in one or more purchases or sales of crude oil and includes a plurality of data points;

store the electronic run ticket data in an exchange data store accessible by a plurality of participants to the one or more transactions;

store an identifier of an oil tank received from the client device as part of the electronic run ticket data and associate a plurality of electronic run tickets together when the plurality of electronic run tickets are part of a single transaction involving identifiers for a plurality of oil tanks;

assign data access permissions to different ones of the plurality of data points;

compare and correlate individual transaction data received from the plurality of client devices for an individual transaction of the one or more transactions as correlated data;

determine whether a discrepancy is present in the correlated data and notify at least one of the plurality of participants when the discrepancy is present;

receive a request to access the correlated data from a participant of the plurality of participants, wherein the participant is a crude oil producer, a crude oil marketer, a crude oil purchaser or a crude oil transporter and is assigned a role as the crude oil producer, the crude oil marketer, the crude oil purchaser or the crude oil transporter;

restrict access by the participant to at least one of the plurality of data points included in the correlated data based on the data access permissions and an identity of the participant, including an identification of the role assigned to the participant where different roles have different of the data access permissions, wherein restricting the access limits the at least one of the plurality of data points accessible by the participant to data points within a defined geographic region, wherein restricting the access enhances security of the plurality of data points and use of the run ticket exchange increases availability of the plurality of data points and enables sharing of the plurality of data points while reducing errors in the plurality of data points; and

receiving and storing a path of the client device between the tank and a road near the tank, reversing the path when the path is from the tank to the road, and transmitting the reversed path as navigation instructions from the road to the tank for use with a second client device.

2. The computing device of claim 1, wherein the plurality of data points comprises:

identification of the crude oil producer, identification of the crude oil transporter, identification of the crude oil marketer, identification of a delivery location and receiving party, identification of an oil tank, identification of a lease of the oil tank, user credentials for the client device, a transaction time stamp, a temperature of oil in the oil tank at the time of the one or more transactions, an API (American Petroleum Institute) gravity of the oil, and a valve seal identifier.

3. The computing device of claim 1, wherein the plurality of data points comprises a location history of the crude oil involved in the one or more transactions based on a location history of the client device.

4. The computing device of claim 1 implemented as an independent third party computing device of a non-participant third-party to the one or more transactions.

5. The computing device of claim 1, further configured to sort the plurality of data points based on input from the participant and further based on the permissions.

6. The computing device of claim 1, further configured to generate audit reports based on the electronic run ticket data for a plurality of electronic run tickets over a defined time period.

7. The computing device of claim 1, further configured to manipulate the plurality of data points to obtain derivation data points representing forecast data or historical data derived from the plurality of data points.

8. The computing device of claim 1, further configured to identify the participant and other participants based on a combination of the electronic run ticket data and additional data present in the exchange data store prior to receipt of the electronic run ticket data.

18. The computing device of claim 1, wherein the identifier comprises a barcode, an identifier obtained from a barcode, or data from a low-power wireless tag associated with the oil tank and obtained by the client device.

9. A computer implemented method, comprising:

receiving electronic run ticket data from a plurality of client devices, wherein the electronic run ticket data represents one or more transactions in one or more purchases or sales of crude oil;

storing the electronic run ticket data in an exchange data store accessible by a plurality of participants to the one or more transactions;

storing an identifier of an oil tank received from the client device as part of the electronic run ticket data and associating a plurality of electronic run tickets together when the plurality of electronic run tickets are part of a single transaction involving identifiers for a plurality of oil tanks;

comparing and correlating individual transaction data received from the plurality of client devices for an individual transaction of the one or more transactions as correlated data;

determining whether a discrepancy is present in the correlated data and notifying at least one of the plurality of participants when the discrepancy is present;

identifying participants to the transaction and storing an identity of the participants with the electronic run ticket data in the exchange data store, wherein each participant is associated with a crude oil producer, a crude oil marketer, a crude oil purchaser or a crude oil transporter and is assigned a role as the crude oil producer, the crude oil marketer, the crude oil purchaser or the crude oil transporter;

receiving a request from the participant to the correlated data at a run ticket exchange to access the electronic run ticket data;

providing access by the participants to the correlated data based at least in part on the respective roles of the participants, wherein providing the access based in part on the roles of the participants enhances security of the electronic run ticket data and the use of the run ticket exchange increases availability of the electronic run ticket data to the participants while reducing errors and personnel;

receiving and storing a path of the client device between the tank and a road near the tank, reversing the path when the path is from the tank to the road, and transmitting the reversed path as navigation instructions from the road to the tank for use with a second client device.

10. The method of claim 9, wherein the electronic run ticket data represents a transaction and includes a plurality of data points, the method further comprising assigning data access permissions to different ones of the plurality of data points, and restricting access by at least one of the participants to at least one of the plurality of data points based on the data access permissions and the identity of the at least one of the participants, where different participants are granted different data access permissions based in part on the role assigned.

11. The method of claim 9, further comprising calculating a time period for completion of the transaction by tracking time stamping at multiple times during the transaction, and reporting the time period for completion to at least one of the participants.

12. The method of claim 9, further comprising deriving or calculating additional data points based on a plurality of data points in the electronic run ticket data and determining whether to display the additional data points to the participants based on the identity of the participants.

13. The method of claim 9, further comprising calculating a volume of oil in an oil tank involved in the transaction based on a temperature and an API (American Petroleum Institute) gravity of the oil.

14. The method of claim 9, further comprising restricting access to the electronic run ticket data based on credentials of the participants, permissions associated with the credentials, and at least one of a relationship to other participants to the transaction or involvement by the participants with portions of the transaction.

15. The method of claim 9, further comprising maintaining an oil lease data store identifying oil lease candidates for transactions and locations of the oil lease candidates, and responding to requests for oil lease candidate identification based on Global Positioning System coordinates of the client device.

16. The method of claim 9, further comprising associating run tickets for a plurality of oil tanks when a truck picks up lease oil from the plurality of oil tanks.

17. An electronic run ticket system, comprising:

a computing device;

an exchange data store in communication with the computing device and configured to store electronic run ticket data received from a plurality of client devices, wherein the electronic run ticket data represents one or more transactions in one or more purchases or sales of crude oil and includes a plurality of data points, and wherein the run ticket data includes an identifier of an oil tank received from the client device as part of the electronic run ticket data and also includes a path of one of the client devices between the tank and a road near the tank;

a rules data store in communication with the computing device and configured to store rules for manipulating the plurality of data points, the rules including rules for;

comparing and correlating individual transaction data received from the plurality of client devices for an individual transaction of the one or more transactions as correlated data;

determining whether a discrepancy is present in the correlated data and notifying at least one of the plurality of participants when the discrepancy is present;

associating a plurality of electronic run tickets together when the plurality of electronic run tickets are part of a single transaction involving identifiers for a plurality of oil tanks; and

reversing the path when the path is from the tank to the road, and transmitting the reversed path as navigation instructions from the road to the tank for use with another one of the client devices;

a derivation module executed by the computing device and configured to derive derivation data points from the plurality of data points; and

a permissions module executed by the computing device and configured to assign data access permissions to different ones of the plurality of data points and derivation data points, the permissions module being further configured to receive a request from a participant to the transaction to access the electronic run ticket data, and to restrict access by the participant to at least one of the plurality of data points or derivation data points based on the data access permissions and an identity of the participant, the participant being associated with a crude oil producer, a crude oil marketer, a crude oil purchaser or a crude oil transporter;

wherein the electronic run ticket system increases availability of the electronic run ticket data while reducing errors.