The Preliminary Specification Part CXXIV (R&C Part XIX)
Today I want to take a look at Professor Giovanni Dosi’s “key factors” in the context of the scenario that we used recently during our review of the Partnership Accounting module. Recall that we had a number of producers who were joining together through the Work Order to participate in an engineering study. This was discussed in the Partnership Accounting module to highlight the manner in which it eliminated the logistical accounting difficulties that impede the development of these working groups. Today I want to discuss how the efforts of that working group are added to the capabilities of the producer and are managed in the Research & Capabilities module of the Preliminary Specification.
Upon completion of the working group the producer firm will have a unit of knowledge that has been developed from the efforts of the group. Professor Carliss Baldwin provides us with some clarity here with her “knowledge begets capabilities, and capabilities beget action” comment. What is needed is for the producer to have a central repository for the knowledge that is accumulated through the various working groups and other “key factors” in which they acquire that knowledge. This will be called the Capabilities Interface in the Research & Capabilities module and will detail the source of the knowledge, the key factor, how it was acquired, and what it involves will be captured within a wiki styled interface. This interface is also sorted by geological zone and populated to the Knowledge & Learning module for the Joint Operating Committee, based on what geological zones they produce from. Organizing a firms and Joint Operating Committees capabilities is the beginning of developing, deploying and effectively managing them.
Within any module of the People, Ideas & Objects application the user will be able to right click their mouse and select from a sub-menu of actions. These actions will include the ability to begin a Work Order, raise an AFE, prepare a Joint Venture Agreement etc. If the user can take action on the capabilities listed within the “Capabilities Interface” then we have achieved the process that Professor Baldwin states is necessary. Having this information centralized for the producer, and the specific information for the Joint Operating Committee helps to concentrate the knowledge within one location within the firm. There will be little confusion as to where to find the answer to a specific question. When the user finds what they are looking for, the detail of the knowledge or capability should be specific enough as to define a process as to how it is implemented. Understanding that knowledge is never static, the ability to update the information with lessons learned would be part of the users responsibility. Recall this update from lessons learned is also done for the Joint Operating Committee in the Knowledge & Learning module.
The ability to annotate and reference the material within the wiki would make this more usable. However, with the tools that are available today, such as search, make the information more valuable. What is truly valuable is the types of tools that will be available tomorrow. We are beginning to see some of these tools enter the consumer space with the iPhone’s SIRI virtual assistant. The first step however will be to acquire the data and make it actionable through the ERP system of People, Ideas & Objects. Then we will be able to add these tools easily as they become available in the future.
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.