The Preliminary Specification Part CXXV (R&C Part XX)
If all that we were to do with the capabilities aspect of the Research & Capabilities module of the Preliminary Specification. Was to document the capabilities as in the “Capabilities Interface” then we would be wasting a lot of people’s time. The purpose in documenting the capabilities is so that we can deploy them, and that brings in the “Planning & Deployment Interface” which is the topic of discussion in today’s post.
Ideally I see the ability of a firm to deploy their capabilities as a key competitive advantage. The organization of that competitive advantage will be the focus of the management of the firm. 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 develop is directly applicable to the game of American football. Where the coach can call in a play and the team is able to execute that play based on their known capabilities, roll and skills on the team. I want to draw a direct analogy for the person who plans and calls on the capabilities of the firm or JOC in the “Planning & Deployment Interface”.
First we need to bring in the Military Command & Control Metaphor and understand that the role of the individual, as designated in that structure becomes a critical part of the planning and deployment of the firm or JOC’s capabilities. There can be only one Quarter Back and you need many Down Lineman. The filling of the various roles in order to take the actions that are needed is as important as the capabilities themselves. Please review the Military Command & Control Metaphor if you have recently started reading this blog. The MCCM imposes a chain of command across the multiple producers represented in the JOC, or firm and enables them to operate the pooled resources of these firms.
The “Planning & Deployment Interface” will take the three critical aspects of the firm / JOC and arrange them within a web like interface for the user to develop the actions they desire. The three critical aspects are the people represented in the MCCM, the capabilities and the time frame. Having selected the personnel that you want to execute the action that you have in mind, their available time becomes known to the interface from each individuals calendar. Selecting the capabilities from the Research & Capabilities, or Knowledge & Learning, module is then drawn into the interface. From there the user is able to “process” the information and based on the variables given determine when the work would be able to be completed. Then they may select additional resources to fill deficiencies in areas where the 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 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”. That package should be comprehensive and detailed such that it is all that they need to be able to focus on the successful completion of the task. This is how I see the interface operating in the Research & Capabilities module.
The quality of the documentation of the capabilities will be the determining factor in how successful the project will be. If the detail contained in the “Capabilities Interface” is of rich media, 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. The people will be able to see clearly what it is that the project is about and how they are expected to complete the task.
The innovative and capable oil and gas producer is in need of the ability to document and deploy their capabilities in an efficient and effective manner. Here is a way in which the deployment is planned and executed with an understanding or “meeting of the minds” based on the quality of the documentation in the “Capabilities Interface”. It being not just a repository of data that might be used some day by some one. But a living source of quality information in which the producer or JOC depends on to make sure that the execution of their projects are successful.
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.