Introduction to Compliance & Governance
Anyway the real business of the business, the Joint Operating Committee somehow survived. When we align the compliance and governance frameworks of the hierarchy to the Joint Operating Committees legal, financial, operational decision making, cultural, communication, strategic and innovation frameworks 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, accountability and profitability.
Compliance & Governance is the eleventh module in the eleven module Preliminary Specification. 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. 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 governments 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 earlier regarding 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 too. 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. Who may be composed from an international background and the Compliance & Governance module takes on an 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 will 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 including dozens of different jurisdictions. To approach this from a software engineering point of view as a sole producer is not cost effective. To consider these costs are replicated within 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 we move away from the individual producer compliance and governance capabilities and rely on an industry wide capability. 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 of the oil and gas industry.
The Preliminary Specification provides the oil and gas producer with the most profitable means of oil and gas operations. People, Ideas & Objects Revenue Model specifies the means in which investors can participate in these user defined software developments. Users are welcome to join me here. Together we can begin to meet the future demands for energy.