Showing posts with label Accting-Voucher. Show all posts
Showing posts with label Accting-Voucher. Show all posts

Thursday, September 15, 2011

The Preliminary Specification Part XXVI (AV Part IV)


Today I want to talk about the domain of the Joint Operating Committee. It is clear in the discussion of the Accounting Voucher that we are concerned about capturing and recording the business of the Joint Operating Committee. And clearing the costs and revenues of the property to the producers. What the Draft Specification talks about is Transaction Design which deals with the optimal location for a transaction to occur. The firm or the marketplace.

So much of what the Accounting Voucher aspires to do is to remove the user from the mundane aspects of dealing with transactions. With Information Technologies (IT) that are available today this is not only possible, but a competitive necessity. For instance you can buy an App for a phone that will take a picture of a receipt and code it to an accounting application. This is what I did in 1977 as my first job in oil and gas. The point of the Draft Specification is that users should be designing transactions as the key to building business value. This aspiration is what is so poorly discussed in the Draft Specification, but when your knee deep in papers, that’s the way the world looks.

Designing transactions, more or less from the point of view as to where the transaction will be conducted, in the firm or in the market, is part of the point of the exercise. What and How are two of the traditional questions of how to get things done. Now we need to answer the question, “where” will the transaction occur, and that is answered in the Accounting Voucher. The research and science on TCE that is referenced in the Draft Specification points to a means of determining where the transaction should occur. And that is what are called “thin crossing points”. However the first determination is the assessment of the capabilities of the group that is being assessed for the work that needs to be done. There is of course no sense in trying to determine the thinnest crossing points as the determining factor of who gets the deal.

It may seem intuitive to reduce the point of the transaction between two firms down to the thinnest point being the transfer of the invoice from one firm to the other. And that would score high on an exam but it would fail in terms of implementation of what the possibilities of Transaction Cost Economics could achieve. What if there were a system development, like People, Ideas & Objects Preliminary Specification, that was user community based that included the service industry as part of that user community? Would that provide an opportunity to define some service industry level systems integration that would be complementary to the Accounting Voucher of the People, Ideas & Objects application? Why couldn’t the service industry provider have their people populated into the Work Order system that we discussed earlier? Or, if the user community deemed that a Purchase Order system was worthwhile that this could also be used as means of direct communication between the producers represented in the Joint Operating Committee in the Accounting Voucher and the service industry providers.

There may ultimately be the thinnest of crossing points for the transaction being the invoice that crosses from the vendor to the joint account. Ultimately making the transaction the most efficient from the organizational point of view. However, with the use of IT we can also build on the information that is known and unknown in all of the producers and all the vendors that are party within a “transaction”.

What may not be clear is the need to design the transaction to ensure the business value is realized by the Joint Operating Committee. There is a general rule that whatever operation your conducting in the field, it is generally going to be conducted based on the understanding of the least experienced individual that is present in the field. It just seems to happen that way. Designing the transaction with these constraints in mind can help to mitigate the unknown factors from causing problems down the road. Also, because most of the “transactions” that occur in the marketplace are of such a large size, building of a compressor, building of a gathering system, drilling a well. The ability to apply further scientific strategic “game theory” type attributes in to the People, Ideas & Objects software is possible.

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.

Wednesday, September 14, 2011

The Preliminary Specification Part XXV (AV Part III)


Of particular interest to me is this is People, Ideas & Objects 1,000 blog post. Who would have thought that a simple idea of using the Joint Operating Committee could create so much discussion. We are well over 850,000 words and it feels like we are just beginning.

One of the implications of using the People, Ideas & Objects system is that each partner will have access to the Accounting Voucher during the time that the Voucher is either open or closed. Each of the producers involved in the JOC are therefore able to access the Accounting Voucher and have costs / revenues distributed to the other partners involved in the Joint Operating Committee. This is one of the key differences that we had discussed in the Petroleum Lease, and Resource Marketplace modules. Partners are all contributing to the joint account as equal participants with the role of “operator” being relegated to a thing of the past. (Note too of course, that each participant is able to charge their own account with their own 100% charges as well. These charges are to their private accounts and therefore not seen by any of the other participants.)

Cost control becomes an issue when everyone is able to charge freely to the joint account. A careful reading of the previous paragraph reflects that I didn’t state “charge freely”. Cost control comes about as a result of the traditional budgetary control of AFE and the Work Order system that we discussed earlier. Without pre-approval by the partnership nothing is able to be processed by the People, Ideas & Objects software applications. And as we will see in the upcoming discussion of the Security & Access Control module, few will have the authorization to “charge freely” to the joint account in any form or fashion.

With the traditional ability to charge to an AFE or Cost Center, and possibly during the development of the People, Ideas & Objects Preliminary Specification, the user community determines the need to have a purchase order system, ensuring that an appropriate bidding and contracting process is in place, no unauthorized amount will be accepted in the system. There is also the fact that each voucher needs to be approved for payment before any money is expended and that approval would need to consider the authority of the joint account.

As one can envision these Joint Operating Committee - Accounting Vouchers can become large as they include all of the business of the property. Accountants would be pulling their hair out at month-end trying to get these Vouchers closed if they had to seek approvals and close each of the transactions within the appropriate small window of time of their month end. Needless to say that each transaction within the Accounting Voucher is a small subset of the larger Accounting Voucher and can be dealt with as a stand alone individual item. Seeking it’s own approvals and authorizations that deal with just the domain of the specific transaction.

What is different in People, Ideas & Objects Accounting Voucher system vs what exist today is the elimination of the designation of operator. The capabilities to house the state of the art necessary to run the property within one oil and gas firm is believed to be beyond what is possible in the very near future. This is primarily as a result of the further specialization of earth science and engineering skills needed to be attained by each individual within the industry. If each firm were to attain the full scope of these capabilities then they would not be a viable business due to the extreme overhead burden. And specialization is the only solution to deal with the limited resources. Therefore it is necessary for each producer in the Joint Operating Committee to contribute their unique capabilities. The objective is to enable the Joint Operating Committee to draw from the much larger pool of producers engineers and earth scientists in order to obtain the global capabilities necessary for the property to operate.

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.

Tuesday, September 13, 2011

The Preliminary Specification Part XXIV (AV Part II)


Reading the Draft Specification for the Accounting Voucher is a tortuous read. What I can glean from the material is what I recall from the research, however, I’m sure no one else has read the research. Making the reading particularly difficult for everyone else. I will, hopefully, make some sense, in the next week or so, of the material through this discussion. I certainly promise to do my best. Another assumption that I am operating from is that everyone has a high level of understanding of how the oil and gas industry operates, making this content difficult to read.

Yesterday we discussed the manner in which the Accounting Voucher was able to handle the material balance report. How it handles the balancing of the volumes, debits and credits, and cleared these amounts to the partnership represented in the Joint Operating Committee. Today we want to talk about the contracts that the products produced may have associated with that JOC. Contracts that would include marketing for gas, oil, natural gas liquids, or contracts for charges for gathering, processing etc.

I don’t know what the correct term that should be used, but stream seems to me to be the most intuitive. If a stream of product was flowing through a facility, then a contract for processing or sale could be attached to it. The ability to attach a contract to a stream would enable the Accounting Voucher to establish the billing of gathering or processing charges / sale for that stream. These charges (invoices) or sales (receipts) being generated in an automated fashion by the People, Ideas & Objects software. This point now brings up a point that is obtusely discussed in the Draft Specification.

The Accounting Voucher is a for lack of a better term a template that is built upon as time passes. Each month as the property changes, these changes are captured within each Accounting Voucher and the template is renewed each month with the new information. If a new contract was added for the production from a new well, then that contract stream and the new well would be represented in next months Accounting Vouchers. The Accounting Voucher documents the changes in the property over time.

So it is with my sincere apologies to any readers that may have tried to make sense of the Draft Specifications Accounting Voucher. One can clearly see the value in a six month sabbatical. I’m sure we’ll run into more bumps along the way and will have to share a laugh at those.

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.

Monday, September 12, 2011

The Preliminary Specification Part XXIII (AV Part I)


We now shift our attention to the Accounting Voucher module. This module introduces many new concepts that may appear to add a level of complexity to the oil and gas business. However, in reality these ideas help to alleviate the difficulties that are systemic in the industry today. For the purposes of clarity lets jump straight into the point that we have been deferring for a number of posts.

The point was raised initially during the discussion of the material balance report and then discussed further in the reporting of volumes to the many number of users of that information. Those posts deferred the discussion of a final solution of how People, Ideas & Objects resolves the volumetric reporting problems to the Accounting Voucher module itself. Now that we are reviewing the Accounting Voucher lets talk about this solution.

The concluding paragraph in the Draft Specification of the Accounting Voucher states:

The People, Ideas & Objects Accounting Voucher Module will provide the means for the application to manage the disparate inter-dependencies of modularity theory and Transaction Cost Economics. That is a summary application of Professor Baldwins comments. And therefore this Accounting Voucher is one of the key cross roads to all other modules in the application. What is necessary is for people to cease in processing transactions, by way of automation, and move toward the definition and design of transactions to optimize the business performance. The Accounting Voucher is also the most critical to the success of the application and hence the producers that use it. I am certain that in the hands of the user community it will achieve all that is possible.

Simple stuff. Critical to the “definition and design” of transactions is the fact that transactions are balancing themselves out. If the debits and credits were not in balance at the end of the day, then the automation of the systems and the accountants would not be doing their jobs. The same could be said for the volumetric reporting. If the material balance reports were out of balance (call this material balance), or were not balancing the inputs and outputs to other reports (call this system balance), or the internal accounting of those volumes to the partners, royalty holders and others were out of balance (call this partnership balance) the accountants and systems would not be doing their jobs.

What is proposed in People, Ideas & Objects is that for an Accounting Voucher to close it must balance the financial debits and credits, but must also from a volumetric perspective material balance, system balance and partnership balance. Each of these volumetric perspectives being accessed through a different “mode” within the voucher to make the necessary changes to correct any imbalances or errors.

The Joint Operating Committee is not a legal entity. It is a thing that exists in the minds of oil men and women. It therefore doesn’t own anything or incur any costs. All of the charges to the joint account must clear in the month they are incurred. Same for the volumetric information. The Joint Operating Committee "Accounting Voucher" balances to zero in terms of costs and volumes each month by clearing its charges to the ownership and royalty owners of the property.

Note that the clearing is done after the balance. That does not guarantee that the facility will remain in balance. Adjustments and amendments to the Accounting Voucher may occur. These may happen and they can be subsequently cleared to the partnership accounts.

The point of the exercise is that you have the business of the Joint Operating Committee being captured in the material balance report which is an integral part of the Accounting Voucher. Essentially all three are the same thing. (JOC, Accounting Voucher, material balance report.) An integrity of reporting that is embedded within the accounting systems that is as rigid as debits must equal credits.

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 and begin building the community for the development of the Preliminary Specification. Email me here if you need an invite.

Thursday, September 08, 2011

The Preliminary Specification Part XX (PA Part VI)


In Canada at least, there is the accounting month and production month to deal with the delay in reporting of production volumes. The logistics of reporting volumetric information creates a lag of one month in the data so that July’s production data will be reported in the August accounting month. And I’m sure that everyone is familiar with the much loved amendment process for that volumetric data. The adjustment process never seems to end, I wonder if we’ll ever find a solution to it.

I think we have an interesting solution in People, Ideas & Objects. We talked about the material balance report the other day. While we noted the need to balance each report, and each input and output with the input and output of other material balance reports. And that each material balance report essentially represented a Joint Operating Committee. We also noted that we were deferring some of the discussion of our solution to the Accounting Voucher module, which we are still doing. However, today we should note that there are some problems that need to be addressed in the Partnership Accounting module that are a result of the adjustments to the material balance reports. That is that these material balance reports do shift and amend volumes of products around as time goes by and things are found to be incorrect. When the physical world is found to be inconsistent with the reporting, the reporting must change.

As I said I don’t want to get into into the solution today, other then noting that containing the problem within the domain of a Joint Operating Committee helps significantly. I want to add to the discussion of the material balance report by detailing the scope of the engineering problem that we have to solve. The first area of concern is that there are both daily and monthly volumes defining a period of time. Some of these volumes are “spec” vs. raw, products and by-products. Volumes are processed and gathered based on ownership and non-ownership of the processing facilities. There are in North America two, units of measures vs. metric reporting standards. How gas is nominated (daily) and marketed (annually). Finally the royalty holders and the ownership of the properties expect to earn something for their efforts. And each of these variables could generate their own amendment processes.

The myriad combinations of possibilities that happen within oil and gas have to be captured and handled within the systems that are used in oil and gas. That has not happened as of this date. The first aspect of solving this problem is to engineer the solution. Many have tried and have found their budgets to be to small for the job. Approaching this from the one producer perspective may seem like adequate funding, however, no one today is declaring success. If, as we have proposed in People, Ideas & Objects, aggregate the resources of the industry towards engineering the solution, this scope can be scaled, the costs to each producer will be incidental, and the results that each producer will realize will reflect the full scale of that software development effort.

The second aspect of the solution of this issue is to limit the scope of it. That is what we have done in People, Ideas & Objects. First by using the Joint Operating Committee as the key organizational construct of the innovative oil and gas producer. What we are doing is adopting the material balance report as a function of the Joint Operating Committee. Which in reality it is. If however we separate it from other Joint Operating Committee’s from an accounting perspective then we can begin to deal within just that JOC as its own autonomous legal entity, which it is. This discussion may initially not make sense until we get into the Accounting Voucher module, and we get into the final aspect of this solution which is where we encapsulate all of this reporting within the accounting system itself.

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 and begin building the community for the development of the Preliminary Specification. Email me here if you need an invite.