OCI Research & Capabilities, Part IV
Key Factors in Innovation, a Scenario
Review of Professor Giovanni Dosi’s “key factors” of innovation in the context of a scenario we used recently during our review of the Partnership Accounting module. Recall that we had a number of producers who joined together through the Work Order system to participate in an engineering study. This Work Order system was discussed in the Partnership Accounting module to highlight the way it eliminated logistical accounting difficulties that impeded the development of these working groups. Working groups add to the producer's capabilities 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 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 all of the implicit knowledge of the producer. This knowledge is accumulated through the various working groups and other “key factors” in which they acquire knowledge. The “Dynamic Capabilities Interface” in the Research & Capabilities module will detail the source of the knowledge, the key factors, how it was acquired, and what it involves. This will be captured in a wiki-style interface. This interface will also be sorted by geological zone and other technical criteria. It will be populated into the Knowledge & Learning module for deployment to the appropriate or relevant Joint Operating Committees when required. The first step in developing, deploying, and effectively managing a company's and Joint Operating Committee capabilities is to organize them.
Within any module of the People, Ideas & Objects application the user will be able to right click their mouse and select from a contextual menu of actions. These actions will include the ability to create a Work Order, raise an AFE, prepare a Joint Venture Agreement etc. If the user can take action on the capabilities listed within the “Dynamic 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 in one location within the firm. There will be no confusion as to where to find the answer to a specific question. When the user finds what they are looking for, the details of the knowledge or capability should be detailed enough to define a process for how it is successfully implemented. Understanding that knowledge is never static, the ability to update the information with lessons learned would be part of the user's responsibility. Updates from the Lessons Learned Interface are also done for the Joint Operating Committee in the Knowledge & Learning module.
The ability to annotate and reference the material within the “Dynamic Capabilities Interface” would render this more usable. In addition, the tools available today, such as search, make the information more valuable. What is truly valuable are the types of tools available tomorrow. We are beginning to see some of these tools enter the consumer space with the iPhone’s SIRI virtual assistant or Chat GTP. The first step however will be to acquire knowledge and make it actionable through the ERP system of People, Ideas & Objects. We can add these tools as they become available in the future.
If documentation was all that we did with the capabilities aspect of the Research & Capabilities module of the Preliminary Specification, within the “Dynamic Capabilities Interface” then we would waste a lot of people’s time. The purpose of documenting capabilities is to deploy them. This brings in the “Planning & Deployment Interface” which is the topic of discussion here.
Ideally I see a firm's ability to deploy its capabilities as a key competitive advantage. The organization of that competitive advantage will be the focus of the firm's management. It should also be noted that there is a similar “Planning & Deployment Interface” in the Knowledge & Learning module for the Joint Operating Committee. The analogy that I would like to use and have developed in the Preliminary Specification is directly applicable to American football. Where the coach can call in a play and communicate that to the team to execute that play. This is based on their known capabilities, roles and skills on the team. I want to draw a direct analogy for the person who plans and calls upon the capabilities of the firm or Joint Operating Committee in the “Planning & Deployment Interface.”
The Industrial Command & Control method of organizing dynamic Joint Operating Committee resources in the Preliminary Specification. Understands that the role of the individual, as designated in that structure, becomes a critical part of the planning and deployment of the firm or Joint Operating Committee capabilities. There can only be one Quarterback on the team, and you need many Down Linemen. Filling the various roles to take the actions needed is as critical as the capabilities themselves. Industrial Command & Control (ICC) imposes a chain of command across the multiple producers represented in the Joint Operating Committee, or firm. This enables them to operate with the pooled resources and capabilities of these firms.
The “Planning & Deployment Interface'' will take the three critical aspects of the firm / Joint Operating Committee and arrange them within a web-like interface for the user to develop the actions they desire. Having the right people represented in the Industrial Command & Control, having the right capabilities, and having an appropriate time frame are all critical factors to consider. Having chosen the personnel to execute the action you envision, their available time becomes known to the interface from each individual's calendar. Selecting the capabilities from the Research & Capabilities, or Knowledge & Learning, module is then drawn into the interface. From there the user can “process” the information and based on the variables given determine when the work can be completed. Then they may select additional resources to fill deficiencies in areas where capabilities suggest they need more resources, conduct more studies to determine certain unknowns or proceed with the project.
Upon proceeding with the project the people who were selected by the user in the “Planning & Deployment Interface” are given the job to do. They are provided with an explicit understanding of what and how and who will be involved in completing the project. Not that it should be a simple matter of execution, but they should at this time have everything provided within the “package” they receive from the “Planning & Deployment Interface.” Application of their tacit knowledge and their "skills, knowledge, experience and ideas" to complete the program. That package should be comprehensive and detailed such that it is all that they need to focus on the successful completion of the task.
The quality of documentation of the capabilities will determine how successful the project will be. If the detail contained in the “Dynamic Capabilities Interface” is rich media-based, detailed and provides the user with a good understanding of what is required then the communication from what is expected and what is understood is not at variance. People will be able to see clearly what the project is about and how they are expected to complete the task.
The innovative and capable oil & gas producer needs the ability to document and deploy their capabilities efficiently and effectively. Here is a way in which the deployment is planned and executed with an understanding or “meeting of minds" based on the quality of the documentation in the “Dynamic Capabilities Interface.” It is not just a repository of data that might be used someday. But a living source of quality capabilities which the producer or Joint Operating Committee depends on to ensure the execution of their projects is successful.
Whoever implements the project through the “Planning & Deployment Interface” will select the various capabilities documents from the “Dynamic Capabilities Interface.” When they do this they can ensure that the capabilities they choose reflect the “final” status necessary for the project. If there is further documentation to be completed or more work is needed to advance the state of the capabilities selected, these attributes can be added. This would keep the documentation up to date with the state of capability within the firm or the Joint Operating Committee. Recipients of the information, once the “Planning & Deployment Interface” was processed, could compare the capabilities information they received with the previous version they viewed. They could also determine quickly how the capability has changed from that previous version. This could be done by way of differing colored text or some other means. Then they could assess what impact and consideration that change would have on their portion of the task. They could also assess if they had any issues as a result. Please review the Blockchain Module for implementation of the technical infrastructure necessary for this feature. Updates to the capability will be written to an additional "block" on the chain. Ensuring differentiation between updates, their authors, etc. can be determined.
As with the information regarding the different capabilities, the resource selection would include any updated information regarding the individual's capabilities. If the completion of a course or program, the successful implementation of other capabilities etc. Would be available to the user who initiates the “Planning & Deployment Interface.” This information could be incredibly detailed and include the contributions the individual made to the “Lessons Learned Interface” in both the Knowledge & Learning, and Research & Capabilities modules. Their performance reviews from previous tasks and any comments about their roles in previous assignments and projects. This information should be available for in-house staff, resources pooled through the various Joint Operating Committees that a firm participates in, and any other vendors or contractors that the firm or Joint Operating Committee may have hired to work on the task. This will be at the discretion of the producer firm.
The timing of the project and its completion are somewhat flexible based on the number of resources put into the project. This makes for a bit of a paradox, as if the team gets too large you lose the cohesiveness the team needs to rely upon. Understanding that the people resourced for these tasks are probably assigned to multiple projects, and their participation is constrained by these limits. Therefore, the timeline may exceed the target.
Lastly, the "Planning & Deployment Interface" has focused on the known unknowns. There are known unknowns and unknown unknowns. After the project interface has been processed and assigned, it is the responsibility of the team members to document these, if possible. Recall that Professor Dosi states
In very general terms, technological innovation involves or is the solution of problems." Dosi defines this as “In other words, an innovative solution to a certain problem involves “discovery” (of the problem) and “creation” since no general algorithm can be derived from the information about the problem automatically. Solutions to technological problems involve the use of information derived from experience and formal knowledge. p. 1125, 1126
Certainly, the "solution" of technological problems involves the use of information drawn from previous experience and formal knowledge (e.g. from the natural sciences); however, it also involves specific and uncodified capabilities on the part of the inventors. p. 1126
A section of the interface should be set aside where the team can collaborate on these points and provide innovative solutions for the producer or Joint Operating Committee.
It is therefore asked specifically, how can the knowledge, information and capability of oil & gas firms solve technical and scientific problems of the future? How can a firm more effectively employ its capability to solve problems and facilitate the discovery of new problems and creation of their solutions? I think the development of the “Planning & Deployment Interface” as described here would provide the producer and Joint Operating Committee with these sought-after abilities.