The Preliminary Specification Part CCCXIV (PA Part XXXIV)
Staying on the topic of the Material Balance Report and the technical risk that is associated with that element of the Partnership Accounting module of the Preliminary Specification. We find that the access privileges to give the right people, the right information at the right time would be nightmarish in their scope. I agree, particularly from the point of view of having the participating producers who are members of the Joint Operating Committee reviewing the information contained in the Material Balance Reports. In addition with our zeal to have the industry operate more efficiently we have opened these interfaces to the production and royalty accounting service providers who need access to the Material Balance Report to do their job on behalf of the producers in the Joint Operating Committee. Why can’t we just print out a Statement of Operations for each producer and be done with it?
In answer to that last question, its automation. With so much of the production process subject to amendment, much time and effort is expended in making the corresponding changes in the subsystems that rely on the processes in the Material Balance Report. If the Material Balance Report reflect fact, although it would still be subject to multiple amendments, then the subsystems that operate off of the Material Balance Report could use its information to compile their data. Royalty volumes might change, and the royalty calculations would change as a result. All without user involvement, etc. As long as the Material Balance Report remained in system, partnership and material balance, everything that depends on that data can be relied upon from a volumetric point of view. Any of the volumetric amendments would be populated through the system immediately.
To address the access privileges issue we should turn to the People, Ideas & Objects Technical Vision. There are four technologies that make up the Technical Vision and they include Java, IPv6, Asynchronous Process Management and Wireless Networks. What these technologies provide, specifically Java and IPv6, is unlimited addressing of unique named spaces. So although the number of variables in terms of Joint Operating Committees and the number of people that will have access to them will grow to a tremendous size, all of the systems will be capable of handling the unique nature of each individual requirement. In other words the base capacity of the technologies can handle the demands.
What we have also learned is that the information contained within a Joint Operating Committee is not of the confidential nature to any one producer. The reserves, accounting, strategy formulation and internal discussions of the producer firm are held within the firm and are not party to the Joint Operating Committee. The only information that is held in the Joint Operating Committee is of a semi-private nature that is shared amongst the partnership. Information such as production, costs, well file and other data that is usually available from public sources as well. Therefore, having the producer firms, and the service providers accessing the Material Balance Report does not expose any one of the producers to any material risk of any highly confidential information.
Turning to the Oracle Fusion Middleware stack we look at the Business Process Management Suite to help us understand how the Material Balance Report can be built. How we can take a unit of production through the various gathering and functional units on to the ultimate point of sale. Having the balancing of each functional unit consider that unit of production and the activities associated with it. Noting for the producer or the owner of the gas plant the costs and revenues of processing and gathering, and the disposition of the product to the contract it is sold under. Each of these processes and activities triggering actions within the General Ledger and creating an invoice and sales records for both the producer, the plant owners and the holder of the gas contract. Automation of the process based on reliable volumetric facts.
For the industry to successfully provide for the consumers energy demands, it’s necessary to build the systems that identify and support the Joint Operating Committee. Building the Preliminary Specification is the focus of People, Ideas & Objects. Producers are encouraged to contact me in order to support our Revenue Model and begin their participation in these communities. Those individuals that are interested in joining People, Ideas & Objects can join me here and begin building the software necessary for the successful and innovative oil and gas industry.
Please note what Google+ provides us is the opportunity to prove that People, Ideas & Objects are committed to developing this community. That this is user developed software, not change that is driven from the top down. Join me on the People, Ideas & Objects Google+ Circle (private circle, accessible by members only) and begin building the community for the development of the Preliminary Specification.
The Preliminary Specification is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for People, Ideas & Objects products remains at the sole discretion of People, Ideas & Objects.