ENERGY COLLABORATION PLATFORM WITH MULTIPLE INFORMATION LEVEL MATCHING

• US 20170039658A1
• Filed: 08/02/2016
• Published: 02/09/2017
• Est. Priority Date: 08/03/2015
• Status: Active Application

• Current Assignee: Aquilon Energy Services, Inc.
• Original Assignee: Aquilon Energy Services, Inc.
• Inventors: Egan, MIchael E., Wagner, Jeffrey K.
• Application Number:
  US15/226,152
• Publication Number:
  US 20170039658A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06Q 50/06 Energy or water supply

Abstract

Methods and systems for automatically matching energy transactions between two or more counterparties. One embodiment provides receiving, with a server, first transaction type data from a first counterparty involved in an energy transaction. Embodiments can also provide establishing, with the server, a sequence of concatenated data fields based on the first transaction type data for a first data level. The sequence of concatenated data fields to a second transaction type data associated with a second counterparty involved in the energy transaction are compared. One or more variances between the sequence of concatenated data fields and the second transaction type data are identified. Additional information for a second data level from at least one counterparty involved in the energy transaction is requested to address the one or more variances.

Claims

1. A method of automatically matching energy transactions between two or more counterparties, the method comprising:

receiving, with a server, first transaction type data from a first counterparty involved in an energy transaction;

establishing, with the server, a sequence of concatenated data fields based on the first transaction type data for a first data level;

comparing, with the server, the sequence of concatenated data fields to a second transaction type data associated with a second counterparty involved in the energy transaction;

identifying, with the server, one or more variances between the sequence of concatenated data fields and the second transaction type data; and

requesting, with the server, additional information for a second data level from at least one counterparty involved in the energy transaction to address the one or more variances.

2. The method of claim 1, wherein requesting the additional information includes automatically generating at least one of an email and an electronic notification provided to a representative of the at least one counterparty.

3. The method of claim 1,wherein requesting additional information includes automatically accessing stored information previously submitted to the server by the at least one counterparty and notifying a representative of the at least one counterparty of the access.

4. The method of claim 1, wherein receiving the first transaction type data includes receiving at least one selected from a group consisting of invoice level data, product level data, deal level data, transport level data, delivery level data, and detailed transaction level data.

5. The method of claim 4, wherein receiving the invoice level data includes receiving at least one of volumetric data and financial data.

6. The method of claim 4, wherein receiving the detailed transaction level data includes receiving at least one of volumetric data and financial data.

7. The method of claim 4, wherein receiving the transport level data is selected includes receiving data selected from the group consisting of pipeline data, transmission grid data, location data, delivery point data, and meter data.

8. The method of claim 1, wherein receiving the transaction type data includes receiving data from a prior tie-out period.

9. The method of claim 1, further comprising:

establishing, with the server, a second sequence of concatenated data fields based on the additional information for the second data level, wherein the second sequence of concatenated data fields includes a sequence of data fields different than a sequence of data fields included in the first sequence of concatenated data fields;

comparing, with the server, the second sequence of concatenated data fields to the transaction type data associated with the second counterparty;

identifying, with the server, any variances between the unique sequence of concatenated data fields and the second transaction type data; and

requesting, by the server, additional information at different data levels until no variances remain.

10. A system for matching energy transactions, the system comprising:

at least one computing device comprising memory and at least one processor executing computer-readable instructions that cause the at least one computing device to;

receive a first transaction type data from a first counterparty involved in an energy transaction;

establish a sequence of concatenated data fields based on the first transaction type data for a first data level;

compare the sequence of concatenated data fields to a second transaction type data associated with a second counterparty involved in the energy transaction;

identify one or more variances between the sequence of concatenated data fields and the second transaction type data; and

request additional information for a second data level from at least one counterparty involved in the energy transaction to address the one or more variances.

11. The system of claim 10, wherein the at least one computing device automatically generates at least one of an email and an electronic notification provided to a representative of the at least one counterparty.

12. The system of claim 10, wherein the at least one computing device automatically accesses stored information previously submitted to the server by the at least one counterparty and notifying a representative of the at least one counterparty of the access.

13. The system of claim 10, wherein the first transaction type data includes at least one selected from a group consisting of invoice level data, product level data, deal level data, transport level data, delivery level data, and detailed transaction level data.

14. The system of claim 13, wherein the detailed transaction level data includes at least one of volumetric data and financial data.

15. The system of claim 13, wherein the transport level data is selected from the group consisting of pipeline data, transmission grid data, location data, delivery point data, and meter data.

16. The system of claim 12, wherein the first transaction type data includes data from a prior tie-out period.

17. A method of performing a tie-out process between information systems associated with a first counterparty and a second counterparty, the method comprising:

requesting, with a server, a first level information from each of the information system of the first counterparty and the second counterparty;

determining, with the server, whether a variance exists between the first level information of the first counterparty and the first level information of the second counterparty; and

requesting, with the server, additional level of information from at least one of the information system of the first counterparty and the second counterparty until no variance remains in the tie-out process between the first counterparty and the second counterparty.

18. The method of claim 17, further comprising:

requesting additional level information from at least one of the information system of the first counterparty and the second counterparty when at least one of information system of the first counterparty and the second counterparty has not provided the additional level information.

19. The method of claim 17, wherein requesting the additional level information from at least one of the information system of the first counterparty and the second counterparty includes automatically requesting and receiving additional information from the information system associated with at least one of the first counterparty and the second counterparty.

20. The method of claim 19, wherein the requesting the additional level information from at least one of the information system of the first counterparty and the second counterparty includes sending a request for access to additional level information based on a pre-determined hierarchy.