The Preliminary Specification Part LXXIV (K&L Part V)
What is it that the people who work for a Joint Operating Committee know? Where does a person that has just been assigned to the property learn what is important about it in terms of how its run? Where is this history kept, who maintains it, and how is it accessed? We have discussed the knowledge area of the Knowledge & Learning module of the Preliminary Specification, I want to shift the discussion now to the learning area.
Lets first review Professor Langlois’ definition of Dynamic Transaction Costs.
"Over time, capabilities change as firms and markets learn, which implies a kind of information or knowledge cost - the cost of transferring the firms capabilities to the market or vice-verse. These "dynamic" governance costs are the costs of persuading, negotiating and coordinating with, and teaching others. They arise in the face of change, notably technological and organizational innovation. In effect, they are the costs of not having the capabilities you need when you need them." p. 99
Our efforts in the learning section of the Knowledge & Learning module must be to reduce the Dynamic Transaction Costs of the Joint Operating Committee. This objective may be contrary to the times that we find ourselves in. Change is the one constant, learning to adapt to that change is critical. Recognizing the high costs associated with Dynamic Transaction Costs therefore has to be handled from a strategic point of view. This post will initiate the discussion and begin documenting how the learning section of the module is configured to capture this data and information.
We now turn to a quotation from Professor Sidney Winter in his paper “Deliberate Learning and the Evolution of Dynamic Capabilities” to define some of the risks we face in the changing environment of the innovative oil and gas producer.
In a relatively static environment, a single learning episode may suffice to endow an organization with operating routines that are adequate, or even a source of advantage, for an extended period. Incremental improvements can be accomplished through the tacit accumulation of experience and sporadic acts of creativity. Dynamic capabilities are unnecessary, and if developed may prove too costly to maintain. But in a context where technological, regulatory, and competitive conditions are subject to rapid change, persistence in the same operating routines quickly becomes hazardous. Systematic change efforts are needed to track the environmental change; both superiority and viability will prove transient for an organization that has no dynamic capabilities. Such capabilities must themselves be developed through learning. If change is not only rapid but also unpredictable and variable in direction, dynamic capabilities and even the higher-order learning approaches will themselves need to be updated repeatedly. Failure to do so turns core competencies into core rigidities (Leonard Barton 1992).
We need to strike a fine balance between these two somewhat opposing goals. Strategically control the Dynamic Transaction Costs and maintain an environment of dynamic capability for change and organizational learning. Simple.
The first component of the learning module has to include a wiki styled information repository that contains the operational, policy and management of the property. This will be managed by the Security & Access Control module so that only those that are assigned to the property are able to access the wiki. In addition those that are not of senior levels within the property will have limited access to certain areas within the wiki. Within the wiki will be the entire life history of the property in terms of the information that has been collected. Well files, schematics, reports, agreements, etc. Everything and anything, indexed and referenced in electronic fashion. Recall too the Knowledge area contains the capabilities of the producer firms affiliated with the JOC.
Another section should be set out for “Lessons Learned” in which to document where decisions were made based on actions or activities that occurred of interest. These have a dramatic influence on everyone in terms of their learning and understanding about the property. These items should also be published to each person in the property as well as being posted in a central location. As with the Research & Capabilities module the ability to act on these items in terms of right clicking on them and generating an AFE, a Work Order, a Purchase Order or any of the other documents in the People, Ideas & Objects application modules should be possible based on the users needs. More will also be discussed about these lessons learned in the Compliance & Governance module.
Again it might be argued or asked, why is the ERP vendor so concerned about the operational concerns of the oil and gas producer? The simple answer is that its the business of the business of oil and gas that needs to be supported by the ERP system. And that is at the Joint Operating Committee level in the oil and gas business and the People, Ideas & Objects application. Its not just about debits and credits anymore, its about identifying and supporting the business of the innovative oil and gas producer.
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.