It has been a while since I posted any information regarding the technical vision stated
here. Each of the four elements of this vision will be broken down and expanded upon individually in the next few weeks.
Today I want to start this review with the Asynchronous Process Management (APM). Asynchronous communications are like a letter where the reader has ample time to reflect and respond. Synchronous communications are like telephone conversations in that the communication itself engages its participants in real time. Asynchronous Process Management (APM) is the style of communication applied to the variety of oil and gas processes that require interaction through a number of different individuals, disciplines or producers. The Java Programming Language can engage in transactions that are asynchronous in nature and as a result reside as real objects with tasks and processes that may take many days, weeks or months to complete, based on the individual responses throughout the process.
The area that I foresee APM playing a strong role is in the joint venture billing, or as I have re-stated, the Partnership Accounting methods. Specifically how the reporting process is updated amongst the partners. We need to consider the number of ways that a producer may contribute to the joint account. I have limited these contributions to capital, leases, intellectual property, human resources and operational capabilities. There may be more types of contributions that can be discussed at a later date.
Each month an accounting of the property is required. I have suggested that this process should be accelerated and lets assume that we bring this up to a weekly process. The example will involve the drilling and day work for a well that was rig released 3 days ago. The example will start with the completion and distribution of the Daily Drilling Report, then the Vendors Invoice, comparison to the Drilling Contract, and finally distribution of the Joint Venture Billing to the partners and final resolution through payments.
You are the successful geologist in a productive well drilled just last week. You as Chairman of the Joint Operating committee have assumed operatorship of the property and are in receipt of the last information required for the Daily Drilling Report. Filing of the report in the file system (noted
here) populates the report to the authorized partners and authenticated users of the information. Due to the security of the information you know that none of the information about the tight hole will be leaked to any third party.
Completing that task the Drilling Contractor submits a finalized invoice based on the drilling contract. Comparisons are run between the current invoice and pre-paid invoices to the Drilling Contract. The system kick's out an anomaly in the mud and tubing used, and the invoice is approved subject to the holdback of the costs in the mud and tubing algorithm. This is then sent to the various partners through a weekly joint venture billing process.
For the purposes of the example, we should assume that there are only two other partners. One whom is the original P&NG lease holder, and geologist by training that promoted the deal based on his theory, the other providing the capital to drill the well where as the operator provided the operational expertise and drilling rig availability.
Based on the agreement that was put across by the geologist partner, the recognition of the lease, the capital, the capability and drilling contract are all assessed in determining the working interest distribution of the new well. The Chairman then sends the partners their agreed to share of the final drilling contract. As with all invoices there is a net 30 day payment requirement that would apply to both the drilling contractors invoice and the Statement of Expenditures.
Each partner peruses the invoice based on their agenda's availability. As the individuals time comes free the system offers the opportunity to review and approve the joint venture billing invoices of the operators that manage their properties. And on the 15th and 22nd days the two other partners approve the invoices for payment on the due date of the 30th.
On the 30th the invoices are paid with the automatic transfer of the funds from bank to bank based on the approval of each partner earlier that month. These payments are aggregated by the system and the operator then approves the payment of the invoice to the drilling contractor.
What we have in essence done is provided the cost justification and process management of one of the key processes of oil and gas. This is carried out in the paper based world industry wide with little variation. The process mentioned here is entirely electronic based on the Genesys Web Services provided. Each time the opportunity or need occurs the process is re-awaken to complete another element of the overall process, based on the relative criteria of each individuals decisions.
When the original invoice is approved by the operator it is automatically forwarded to the partners, who wait to peruse it on their time availability, upon review, which would include a comparison to the drilling contract in this case, would see that the tubing and mud reconciliations have some outstanding issues would accept them in to their Genesys Web Service and pay them at the appropriate time.
Each aspect of the process is being completed when it is convenient or required to be completed. Which ever is the latter. Java's asynchronous capability and exception handling are the most robust of any system. Their ability to conduct these types of operations asynchronously so that people are reduced to making the key decisions in their own time frames is the desire of the Genesys system.
I think that the ability to build on this concept requires that other elements of the technology vision to be brought about and discussed in the next week or two. As the asynchronous methods are able to build on the Java objects, Wifi and IPv6 component's of the vision. Until then we'll leave the discussion here.