[Partnership accounting] [Java programming language]
I want to raise one of the major problems that Genesys needs to solve. This issue, I think is unique to the accounting for operations in the joint operating committee. The issue is the partnership or joint venture accounting, as discussed here and here, and focuses on the way the functionality and process is written. The way the system needs to be designed will use concepts that are not present in oil and gas accounting systems available today. I would also assert that these issues could not be addressed in prior programming languages. Java opens up many opportunities to handle and solve these types of problems, and I can see how it would be very effective in solving this issue.
The current systems, SAP in particular, focus almost exclusively on the accounting of the company of interest. The joint account is cleared monthly to the appropriate working interest owners, and from that point, little if anything is done other then from an internal perspective. With the change in organizational focus to the joint operating committee, this internal focus is maintained, and from an accountability point of view increased, however the partnership focus begins to take on a more substantial component of the interests of the collective organizations as represented by the joint operating committee.
I have discussed that many of the participants of the JOC will be more active in the day to day of each JOC. Micro Specialization is something that will have to come about as a result of the demands for so much work to be done by the existing and possibly declining population of oil and gas workers. I have also detailed here the use of personnel from various participants will be called upon to conduct activities, whereas currently, the operator and chairman undertook most of these tasks.
This point will help to mitigate the redundant and unproductive duplication of capabilities of the competitive oil and gas marketplace today. As Dr. Giovanni Dosi has suggested, the capabilities and qualities of each individual producer are currently being mirrored and this mirroring is constraining the understanding of the advancement of the sciences and engineering and their application in innovative ways. A more cooperative mindset is required to fulfill the markets demand for energy.
Currently the direction of data and information is from the operator to the non-operators. This by nature was a simple programming issue to overcome, and there will be some elements of this simple method in the Genesys system. The difficulty comes when all participants of the joint operating committee have each been contributing people, financial and technical resources, and direct costs on behalf of themselves, and / or, other members of the joint account. All the producers collective resources are pooled to attain the highest level of technical capability, management and tactical deployment available.
These costs and resources are being incurred on each producers behalf, or, their own behalf and not initially shared, but may be eligible to offset their obligations to other partners or need to be recognized irrespective. This is further complicated by the fact that many of the internal charges and overhead allowances that have been traditionally charged to the joint account also become redundant. These overhead style of costs are replaced by the specific costs and attributes that were directly incurred by each producer represented in the joint operating committee. The Genesys system will capture these components as they are incurred by the employee / worker / investor / consultant in an active job costing state as the user / worker is logged on.
What is therefore required in order to determine the 100% costs attributable to the JOC is a "pooling" of all the eligible associated costs and revenues involved in the property. Once these costs have been aggregated from each producer, then and only then, can the appropriate costs of each producer be determined, recognized and billed.
To only make things more complicated for the developers, this cost data should be compiled into its usable form at least daily and ideally on a live basis. The elimination of the month end process is one of the objectives of this system, and things need to be dealt with on a more current basis. Cash redistribution based on contributions would remain on a clearing basis at the end of the month or when reasonable.
When a cost is incurred, the system is required to be able to denote that transaction as an operated or non-operated cost and if it is eligible. These two attributes are telling the system that these costs are incurred on behalf of all of the participants of the joint operating committee, on behalf of the producer itself and if it should be recognized in the joint account or not. Therefore reflecting that their may be unique costing components of each producer represented by the joint operating committee.
Technorati Tags: Energy, Genesys, Partnership-Accounting, Technical Vision