The Preliminary Specification Part XLVI (C&G Part I)
Ah Compliance & Governance, the module everyone loves to hate. It is my hypothesis that it is here, at compliance and governance, that everything went wrong. What I mean by that is in the 1960’s when the first computers were being introduced into oil and gas companies. The question was asked what will we do with them. And of course the answer was accounting. Then as they became ever more powerful and more capable they began to add more tasks to their duties and added the natural follow on concerns of tax, royalty and SEC compliance. Soon the culture became focused on those “compliance” requirements of the “firm” and the Joint Operating Committee became something that was used over there. Soon after this engineers and geologists began speaking a different language to the “business” types, as they began development of management science and other such nonsense. Divisions grew and the business of the business was focused on the corporation and its need to file the appropriate paper work to the appropriate agency in the appropriate time frame on the appropriate colored form.
Anyway the real business of the business, the Joint Operating Committee somehow survived and if we align its legal, financial, operational decision making, cultural, communication, strategic and innovation frameworks to the compliance and governance frameworks of the hierarchy everyone can start speaking the same language as the engineers and geologists and start to get some real business done. And as People, Ideas & Objects research has shown this would provide the oil and gas producer with greater speed, innovation and accountability.
Compliance & Governance is the eleventh module in the eleven module Preliminary Specification. Please note, the number of modules is not set as the user community may certainly add more modules if they feel the need to. It’s also no accident that I added Compliance & Governance last, as the question that should be asked is. How are we going to ensure compliance to all the regulations for all the module specifications that we have discussed so far? And I would assert that is why these are user based developments. But seriously, one thing governments seem to be fond of today is regulations on oil and gas companies. With Information Technology enabling various governments to issue technical business rules, technical specifications, XBRL syntax’s and other technological frameworks for these regulations. The ability to write these “frameworks” only seems to have encouraged them to write even more regulations. The larger point is that these frameworks do provide software developers with distinct advantages in enabling the regulations within the software.
As we had indicated in an earlier post about the user communities determination of the scope of the People, Ideas & Objects application. Part of that determination of scope will include which regulations it will need to be in compliance to. With so many jurisdictions requiring compliance, each transaction may need to be assured to be in compliance with multiple jurisdictions. Add to that the transaction may be generated through a Joint Operating Committee owned by a variety of producers. And those producers maybe composed from an international background and the Compliance & Governance module takes on enhanced importance.
From the point of view of a producer maintaining the database and applications for all of the compliance frameworks that you have to be concerned with is a difficult task. The number of people you need to have to keep your applications up to date is significant. However, People, Ideas & Objects as one software developer acting on behalf of the industry as a whole, the job becomes much more specialized and therefore manageable. Then again if we were building these applications with the purpose of serving an industry we could use the division of labor and specialization to manage these tasks in a way that would significantly lower the costs of compliance, and increase the quality of the producers compliance.
I foresee just the royalty compliance requirements of these applications potentially including many dozens of different jurisdictions. To approach that as a sole producer is not cost effective in the least. To consider these costs are replicated across each producer firm, then we begin to see the costs of compliance escalating to the levels that they are today. There is another way, and that is what is being proposed here in People, Ideas & Objects, along with the many other innovative ways we are proposing to deal with the issues in the oil and gas industry.
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.