US2019050830A1PendingUtilityA1

Electronic Run Ticket

Individually held — no corporate assignee on recordPriority: Dec 13, 2013Filed: Oct 11, 2018Published: Feb 14, 2019
Est. expiryDec 13, 2033(~7.4 yrs left)· nominal 20-yr term from priority
G06Q 20/047G06F 40/174G06Q 50/06G06F 17/243G06Q 20/0453
65
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

Technology for managing electronic run ticket data is provided. In an example method, a fluid tank is electronically identified using a client device. Fields of the electronic run ticket are populated based on the electronically identifying the fluid tank and further based on variable data. The electronic run ticket is transmitted as an encrypted electronic run ticket to a management server, the encrypted electronic run ticket being encrypted using a unique key. The electronic run ticket is marked as complete and at least a portion of the electronic run ticket is locked from editing to create an original document which exists as a fixed and accurate record of the fluid transaction.

Claims

exact text as granted — not AI-modified
1 . A method for completing an electronic run ticket in a fluid transaction, comprising:
 electronically identifying a fluid tank using a client device;   populating fields of the electronic run ticket based on the electronically identifying the fluid tank and further based on variable data, using the client device;   transmitting the electronic run ticket as an encrypted electronic run ticket to a management server, the encrypted electronic run ticket being encrypted using a unique key;   marking the electronic run ticket as complete; and   locking at least a portion of the electronic run ticket from editing to create an original document which exists as a fixed and accurate record of the fluid transaction.   
     
     
         2 . The method of  claim 1 , wherein the at least a portion of the electronic run ticket is locked from editing prior to marking the electronic run ticket as complete. 
     
     
         3 . The method of  claim 1 , wherein the at least a portion of the electronic run ticket is not locked from editing prior to marking the electronic run ticket as complete. 
     
     
         4 . The method of  claim 1 , further comprising generating a separate corrections ticket when edits are made to data of the electronic run ticket without modifying the original document. 
     
     
         5 . The method of  claim 1 , enabling editing of comments on the electronic run ticket and of a destination of fluid extracted from the fluid tank after marking the electronic run ticket as complete. 
     
     
         6 . The method of  claim 1 , further comprising storing a time of the fluid transaction with the electronic run ticket to enable storage of the electronic run ticket for a predefined period of years following the fluid transaction. 
     
     
         7 . The method of  claim 1 , wherein the fluid transaction comprises a plurality of fluid transactions completed over time, the method further comprising generating audit documents for a participant to the plurality of fluid transactions based on data of the plurality of fluid transactions. 
     
     
         8 . The method of  claim 1 , wherein populating fields of the electronic run ticket further comprises identifying a valve seal identifier and entering the valve seal identifier in one of the fields. 
     
     
         9 . The method of  claim 1 , wherein populating fields of the electronic run ticket further comprises identifying a plurality of identifiers associated with a location of the fluid transaction and entering the plurality of identifiers in the fields. 
     
     
         10 . The method of  claim 9 , wherein the plurality of identifiers are selected from a group consisting of: a sales valve identifier, a production valve identifier, an equalizing valve identifier, a tank identifier, and a lease identifier. 
     
     
         11 . The method of  claim 9 , further comprising populating a plurality of fields for each of the plurality of identifiers, the plurality of identifiers being associated with seals, one of the plurality of fields being populated for one of the seals to be broken and other one of the plurality of fields being populated for one of the seals for re-sealing after the one of the seals to be broken is broken. 
     
     
         12 . The method of  claim 9 , wherein each one of the plurality of identifiers is a unique identifier associated with a specific item of equipment associated with the location of the fluid transaction. 
     
     
         13 . The method of  claim 9 , wherein at least one of the identifiers is a unique identifier identifying the location of the fluid transaction. 
     
     
         14 . The method of  claim 1 , wherein the fluid tank is a water tank. 
     
     
         15 . The method of  claim 1 , wherein the fluid tank is an oil tank. 
     
     
         16 . An electronic run ticket system for recording data of a fluid transaction, comprising:
 a client computing device;   detection hardware associated with the client computing device for electronically identifying identifiers uniquely identifying a location of the fluid transaction and of valve seals involved in the fluid transaction;   a memory on the client computing to store the identifiers;   a clock on the client computing device to identify time stamp data;   a population module to populate an electronic run ticket based on the identifiers and the time stamp data;   a submission module for submitting the electronic run ticket as an encrypted electronic run ticket to a management server using a unique encryption key; and   a locking module to lock at least a portion of the electronic run ticket during or after completion of the fluid transaction to render the electronic run ticket an original document which exists as a fixed and accurate record of the fluid transaction.   
     
     
         17 . The system of  claim 16 , wherein the detection hardware comprises a Global Positioning Satellite (GPS) unit to identify a location of the client computing device, the client computing device being further configured to present one or more fluid tanks for selection by a user based on the location of the client computing device, each of the one or more fluid tanks being associated with one of the identifiers for uniquely identifying the location. 
     
     
         18 . The system of  claim 16 , further comprising a recognition module to recognize handwritten data, the population module being further configured to populate the electronic run ticket based on recognition of the handwritten data by the recognition module. 
     
     
         19 . The system of  claim 16 , wherein the detection hardware comprises at least one of: a camera, a scanner or a radio communication device. 
     
     
         20 . A method for completing an electronic run ticket in a fluid transaction, comprising:
 electronically identifying a fluid tank using a client device;   populating fields of the electronic run ticket based on the electronically identifying the fluid tank, using the client device, including creating a record in the electronic run ticket of identifiers uniquely identifying a location of the fluid transaction and of valve seals involved in the fluid transaction;   marking the electronic run ticket as complete using the client device;   transmitting the electronic run ticket as an encrypted electronic run ticket to a management server for secure storage and accessibility of data of the electronic run ticket by participants to the fluid transaction based on permissions associated with each of the participants, the encrypted electronic run ticket being encrypted using a unique key; and   locking the electronic run ticket from editing to create an original document which exists as a fixed and accurate record of the fluid transaction, the electronic run ticket being locked from editing both at the client device and at the management server.   
     
     
         21 . A computer implemented method, comprising:
 receiving electronic run ticket data from a first client device, wherein the electronic run ticket data represents a fluid transaction involving a tank and a valve on the tank, the electronic run ticket data including a first unique valve seal number for when the valve was opened and a second unique valve seal number from when the valve was closed;   receiving electronic run ticket data from a second client device;   storing the electronic run ticket data from the first and second client devices in an exchange data store;   comparing the electronic run ticket data from the first client device with the electronic run ticket data from the second client device; and   providing a notification when the electronic run ticket data from the first client device does not correspond with the electronic run ticket data from the second client device within a predetermined threshold.   
     
     
         22 . A computer implemented method, comprising:
 receiving electronic run ticket data from a first client device, wherein the electronic run ticket data represents a fluid transaction involving a tank, the electronic run ticket data including an identifier identifying the tank and further including fluid levels of the fluid tank before and after the fluid transaction;   identifying a strapping table the corresponds to the fluid tank based on the identifier;   calculating a measurement of the change in fluid levels in the fluid tank based on the fluid levels;   converting the measurement into a run volume expressed in barrels;   receiving electronic run ticket data from a second client device;   storing the electronic run ticket data from the first and second client devices in an exchange data store;   comparing the electronic run ticket data from the first client device with the electronic run ticket data from the second client device; and   providing a notification when the electronic run ticket data from the first client device does not correspond with the electronic run ticket data from the second client device within a predetermined threshold.

Join the waitlist — get patent alerts

Track US2019050830A1 — get alerts on status changes and closely related new filings.

We store only your email — no account needed. See our privacy policy.