The Preliminary Specification Part CXLIII (K&L Part XI)
One of the advantages of writing the Preliminary Specification in the manner that we are is that you can aggregate the posts for one module by selecting its label. If you have an interest in working only on the Knowledge & Learning module then you can eliminate the other posts by just simply selecting the Knowledge-Learning label on this blog or from here. The disadvantage is that we are repeating ourselves in some cases so that the people who are focusing on one module are picking up all the pertinent information for that module. I would recommend that everyone read all the posts for all the modules as there is significant interactions between the modules, and we may not be able to catch all the pertinent detail that should be included in each module.
Today’s post discusses the risks of proprietary leakage of data or information as a result of the “Capabilities Interface” being populated with the capabilities information from each of the producers who are participants in the Joint Operating Committee.
We have all seen how information or secrets within the industry can travel from one firm to another at a rather rapid pace. No one should be surprised to learn that what they thought was confidential to the firm, was somehow leaked and became well known throughout the industry. It is some times more difficult to communicate information through the organization then it is to get information across the industry. The question therefore becomes how is proprietary information, and more importantly these proprietary capabilities that are available within the producer firms, deployed on an as needed basis within the various Joint Operating Committees.
Professor Dosi notes that although the free movement of information has occurred in industries for many years, yet has never been easily transferable to other companies within those industries. The ability to replicate a competitive advantage from one company to another is not as easy, and may indeed be not worthwhile doing. Dosi (1988) goes one step further and states, “even with technology license agreements, they do not stand as an all or nothing substitute for in house search.” A firm needs to develop “substantial in-house capacity in order to recognize, evaluate, negotiate and finally adapt the technology potentially available from others.”
Within the Knowledge & Learning module we are operating within the Joint Operating Committee. Populated with the capabilities from each of the participating producers through the “Capabilities Interface”. It may be a concern to some producers that the publication of these capabilities to other producers representatives in the Joint Operating Committee would lead to leakage of proprietary information or loss of knowledge or capabilities. That may be, however the nature of capabilities are such that they can’t be copied by a simple matter of recording the text. As we have discussed elsewhere, the development of capabilities is the results of research and application of the resources of the firm in a determined and purposeful manner to achieve an outcome. Copying the plans or instructions would not provide you with the means to achieve the objective.
If it is determined that the “Capabilities Interface” in the Knowledge & Learning module only provides a summary description of the capability, as opposed to publishing the entire capability in the Joint Operating Committee, then if selected it would be assumed that that producers staff would undertake to complete the task. That may be the ultimate solution to the concern for the loss of proprietary information, knowledge or capabilities. What we have to make sure that we don’t lose is the ability to deploy the right information, knowledge or capability at the right time and at the right place. Information’s shelf life expires faster each day. Knowledge, information and capabilities need to be employed and deployed when and where they are needed and required.
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.