We continue on with the “Planning & Deployment Interface” in the
Research & Capabilities module of the
Preliminary Specification. This interface would also be available to the Joint Operating Committee through the
Knowledge & Learning module. Today I want to discuss the general operation of the interface and how users will interact with the information contained within it.
Who ever it is that implements the project through the “Planning & Deployment Interface” will be selecting the various capabilities documents from the “Capabilities Interface”. When they do this they will be able to ensure that the capabilities they select reflect the “final” status necessary for the project. If there is further documentation that needs to take place or more work is needed to advance the state of the capabilities that are selected, these attributes can be added. This would have the effect of keeping the documentation up to the state of the capability within the firm or the Joint Operating Committee. Recipients of the information, once the “Planning & Deployment Interface” was processed, would be able to compare the capabilities information they received with the previous version they viewed, and determine quickly how the capability has changed from that previous version. Then they could assess what impact and consideration that change would have on their portion of the task and if they were to have any issues as a result.
Just as with the selection of the various capabilities the resource selection would have any updated information regarding the capabilities of each individual. 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 that 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 the role they undertook in previous assignments. This information should be available for in-house staff, resources that are pooled through the various Joint Operating Committees that a firm participates with, any suppliers and vendors or contractors that the firm or JOC may have hired to work on the task.
The timing of the project and its completion are somewhat flexible based on the number of resources that are put on the project. This makes for a bit of a paradox, as if the team gets too large you lose the cohesiveness that the team needs to rely upon. Understanding that the people that are resourced into these tasks are probably assigned to multiple projects, and their participation is somewhat constrained by these limits, the time line may reach beyond what is initially the target.
Lastly the “Planning & Deployment Interface” has been about the known knowns to this point. There are a variety of known unknowns and unknown unknowns. To document these, if possible, is the role of the team members once the project interface has been processed and assigned. Recall that Professor Dosi states “In very general terms, technological innovation involves or is the solution to problems.” Dosi goes on to further define 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 problems. Solutions to technological problems involve the use of information derived from experience and formal knowledge.
It is the specific and un-codified capabilities, or tacit-ness” as Professor Dosi describes “on the part of the inventors who discover the creative solution.” A section of the interface should be set aside where the team can collaborate on these points and provide some innovative solutions for the producer or JOC.
It is therefore asked specifically, how can the knowledge, information and capability of oil and gas firms solve the 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.
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.