The Preliminary Specification Part CXXXIII (R&C Part XXVIII

In today’s post I want to continue on with yesterday’s discussion of the “Research Budget Allocation Interface” and the two “pages” format. Recall that one page would be for the endogenous developed capabilities and the other for the exogenous scientific findings. What I want to discuss today is the process that the user of this interface will be involved in in documenting the capabilities from the research that is being conducted within the firm and the greater scientific community. By way of the football analogy that we raised a few weeks ago, I want to show how this documentation would be done.

Ultimately the objective of the “Research Budget Allocation Interface” is to augment the firms “Capabilities Interface” or to enhance the firms overall capabilities. The Capabilities Interface documents what the firm is capable of and is in turn populated, through the Knowledge & Learning module, to the various Joint Operating Committees. And then based on geological zones and other criteria that are applicable to the property. The user select the pertinent capabilities that are needed. At which time the people that are assigned the work at the Joint Operating Committee are able to determine the state of the capabilities of the firm, and apply them to their work. The football analogy would come into play here in that the design of a play is committed to writing in which the team studies it, and each team member learns their role, and then executes the play in the manner in which it was designed.

As the firm continues on over time, research from the endogenous and exogenous areas become innovations that populate the “Capabilities Interface” which in turn populate the various Joint Operating Committees. This is the process of how I see the innovations developed within the firm and elsewhere are implemented in the innovative oil and gas firm. Professor Dosi (1988) continues on to assert that much of the innovativeness of a firm is dependent on technology more than science, and is based on several implications. The first implication being the net benefactor of the cumulativeness, tacitness and technological knowledge implies that “innovation and the capabilities for pursuing them are to an extent local and firm specific.” Secondly, the “opportunity for technological advances in any one economic activity can also be expected to, and constrained by, the characteristics of each technological paradigm and its degree of maturity”. This is further defined by the technological and scientific capabilities, and “the advances made by suppliers and customers.” (p. 1137) We documented in yesterday’s post that we have three processes that deal with these variables under management in the Research & Capabilities module.

Recently we learned of the difficulty for a firm to copy another firms ideas or capability provides little to no value. On the contrary the effort to copy the capabilities is as potentially difficult as building their own unique capabilities. Today we learn that innovation is dependent on the technology that supports the firm. That is the technology both enables and / or constrains the capabilities of the producer.

Professor Dosi notes “New technology paradigms reshape the patterns of opportunities of technical progress in terms of both the scope of potential innovations and ease with which they are achieved.” p. 1138. The technology that a producer has includes the ERP systems used within the organization.  When the business is a science, as it is in oil and gas, it would be in the producers interest to remain open and flexible in both its scientific and business approach. This is the strategic position that a producer would be capable of maintaining with People, Ideas & Objects software applications, based on the Preliminary Specification.

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.

The Preliminary Specification Part CXXXII (R&C Part XXVII)

Yesterday’s discussion of the Research & Capabilities “Research Budget Allocation Interface” offered the innovative oil and gas producer the opportunity to control the costs of the research and innovation conducted within their firm. We know from Professor Giovanni Dosi that businesses commit to innovation as a result of both the exogenous scientific factors and endogenous accumulated capabilities developed by their firms. We have discussed in fairly good detail how the capabilities are handled in the Research & Capabilities module of the Preliminary Specification. Today I want to continue to discuss how the research end of the module is managed.

With the “Research Budget Allocation Interface” we are able to provide a global view of the capabilities that the firm have under development. As was mentioned yesterday, this interface will provide the user with the ability to see areas that might otherwise fall through the cracks, so to speak. What is needed now is a similar interface that would give a view of the research that is being undertaken in the scientific arenas that enable the producer to “commit to innovation as a result of exogenous scientific factors”.

It might be important to quickly recall the major processes that are being managed in the Research & Capabilities module. We have the “Ideas Marketplace Blog” providing the environment where the service industry is actively developing new and innovative products and services with input from the producers. We have the “Capabilities Interface” where the firm is documenting what it is capable of and can achieve. These capabilities are deployed through the “Planning & Deployment Interface” in the Research & Capabilities or Knowledge & Learning modules and lastly we have the “Research Budget Allocation Interface” we discussed yesterday. There are more processes under management in the Research & Capabilities module, I only wanted to highlight the pertinent ones for the discussion that follows here on the scientific nature of the business.

Professor Dosi concludes that scientific input into the innovation process is evidence of the importance of factors exogenous to competitive forces among private economically motivated actors. This is subject to two important qualifications.

• Science and Technology are self-fulfilling in their developments.
• Scientific advances play a major direct role, especially at an early phase of development of new technological paradigms. p. 1136

These points support Dosi’s (1988) assertion that “general scientific knowledge yields a widening pool of potential technological paradigms,” where the greatest value is attained in the earlier stages. Professor Dosi analyzes the specific mechanisms through which a few of these potential paradigms are actually developed economically, subsequently applied, and that often have become dominant in their industry. The process of selection depends on the following factors.

• The nature and interests of the bridging institutions between pure research and economic applications. (p. 1136)
• Institutional factors that drive the technology or science, such as (the military) (p. 1137)
• The selection criteria of markets and or techno-economic requirements of early users. (p. 1137) (NASA, Pentagon the FDA and Nuclear Reactors for the Navy.)
• Trial and error associated with the Schumpterian entrepreneurship. 

There is little doubt in my mind that we need an interface here. An interface that is similar to the “Research Budget Allocation Interface” would be appropriate. And maybe we only need to establish a second “page” within that interface. One for the internal or endogenous budget items and one for the exogenous budget items. The key here is to note that the greatest value is attained in the earlier stages. And that seems somewhat intuitive doesn’t it.

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.

2012 Fees Are Now Due

People, Ideas & Objects 2012 software development fees are now due. These fees were set in a November 1, 2011 blog post at $1.00 per barrel of oil equivalent per day production. (Producers with production of 50,000 barrels per day would pay $50,000.00 U.S. for software development fees for the 2012 calendar year.) Penalties of 300% of the 2012 fees will be assessed on any outstanding fees after March 31, 2012. All fees for 2010 onward must be paid in full by the producer before their participation can begin in the user community. 2010 and 2011 fees and penalties were set at $1.00 per barrel of oil equivalent per day production and 300%. All fees for 2010, 2011 and 2012 total $9.00 per barrel of oil equivalent.

Fees are used to support the developments of the Preliminary Specification. Please review our revenue model for more information on our fee structure and policies.

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.

The Preliminary Specification Part CXXXI (R&C Part XXVI)

We now turn to the research area of the Research & Capabilities module in the Preliminary Specification. What we are particularly interested in today is to take control of the financial costs of the innovative activities that are being conducted within the producer firm. A firm of any size would have a variety of projects being conducted. With the volume becoming unmanageable quite quickly if there was no control over the amount spent and the type of activity. There are cost controls that are set in place in the People, Ideas & Objects systems like AFE’s and Work Orders, and these will sponsor most of the research undertaken in the firm. The interface that we are talking about today does not replace those, it only centralizes the information for a clearer understanding of the activity and its funding.

Your firm may become involved in many projects that seek to find new knowledge and information regarding the oil and gas business. Some of these activities may be rather large and will certainly be the focus and will have no difficulty in attracting the attention of the firm. Some however may be small and will be important from the perspective that the information is just as pertinent to the firm, but don’t attract the attention. Nonetheless, this information needs to be included in the day to day of each and every operation of your firm, and as such needs to be documented in the “Capabilities Interface”. How does the firm manage the various projects within a firm to ensure that the money spent and all of the projects are documented within the capabilities of the firm?

Within the Research & Capabilities module we will have the “Research Budget Allocation Interface” that will assist in dealing with the costs of innovation and the volumes of projects the firm is involved in. If an AFE is raised with some element of the costs including the partnership doing some joint research or innovative activity, this activity should be populated in the “Research Budget Allocation Interface”. Or, if a Work Order is raised to conduct some study, that too should be populated into the “Research Budget Allocation Interface”. The purpose of this interface is to ensure that there is no duplication of the research undertaken, if there is then the costs could be saved. It is also to document the ongoing status of the project. And ensure that the results of the project are documented within the “Capabilities Interface” of the Research & Capabilities module.

In general, each organizational arrangement of a firm embodies procedures for resource allocation to particular activities (in our case, innovative activities), and for the efficient use of these resources in the search for new products, new processes, and procedures for improvements in existing routines; however, the specific nature of these procedures differs across firms and sectors. For example, the typical degrees of commitment of resources vary by industry and so do the rates at which learning occurs. I now turn to the interpretation of these phenomena. p. 1135

Although this may appear like a simple interface, in the proper hands it would be a very powerful tool. It would provide a global view of the firms activities in the area of innovation and show the overall progress that the firm was making. It would also show where unrelated innovations might occur. Lastly, and here’s the real kicker, it might show where some opportunities lay. Professor Dosi (1988) states that profit motivated agents must involve both “the perception of some sort of opportunity and an effective set of incentives.” (p. 1135) Professor Dosi introduces the theory of Schmookler (1966) and asked “are the observed inter-sectoral differences in innovative investment the outcome of different incentive structures, different opportunities or both”? (p. 1135) Schmookler believed in differing degrees of economic activity derived from the same innovate inputs.

The “Research Budget Allocation Interface” would provide a window on both the “different incentive structures and different opportunities within the producer firm. Making for a powerful tool in terms of guiding the innovative oil and gas producer.

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. 

The Preliminary Specification Part CXXX (R&C Part XXV)

Continuing on with our innovation review of the Research & Capabilities module of the Preliminary Specification. We note that yesterdays post enabled the innovative oil and gas producer to isolate the innovation activities within one area in their firm. This enabled the various Joint Operating Committees to focus on execution of what was known, which of course included what was proven new and innovative. Today we want to talk about the uncertainty and risk associated with innovative search. Something that I think that most producers are familiar with, however, something that will become more commonplace as the demand for innovation by the producer increases.

What is clear to me is the role that software will play in the enabling of innovation within the oil and gas firm. Throughout the series of these blog posts on the Preliminary Specification it is evident that software plays a critical role in the future oil and gas firm. Software is able to define and support the quantifiable and replicable processes of innovation. For the oil and gas industry to conduct any level of innovation without having the software, as defined here by People, Ideas & Objects, will be leaving the innovations outcome to chance. Such is the nature of software in the 21st century.

Whether it is geological or engineering in nature, the pursuit of these sciences bring to the oil and gas business certain elements of risk and uncertainty. Add to this the commercial nature of the oil and gas business and you have an atmosphere where innovation is for those who can take the heat. Professor Dosi suggest this is the appropriate environment for innovation.

I suggest that, in general, innovative search is characterized by strong uncertainty. This applies, in primis to those phases of technical change that could be called pre-paradigmatic: During these highly exploratory periods one faces a double uncertainty regarding both the practical outcomes of the innovative search and also the scientific and technological principles and the problem-solving procedures on which technological advances could be based. When a technological paradigm is established, it brings with it a reduction of uncertainty, in the sense that it focuses the directions of search and forms the grounds for formatting technological and market expectations more surely. (In this respect, technological trajectories are not only the ex post description of the patterns of technical change, but also, as mentioned, the basis of heuristics asking “where do we go from here?”) p. 1134

Lets be clear, the uncertainty resides in both the scientific and business realms. I am not of the opinion that the two can be separated, as is done in other systems such as SAP. This is maybe why the industry has been poorly served, in my opinion, by the business systems that operate today. They don’t recognize the innovative and science basis of the business and therefore are unable to support an innovative oil and gas industry. If the commodity prices are reallocating the financial resources to fuel innovation. The industry will need to have the systems and procedures installed in order to manage the innovation. Systems such as described here. With the low costs of knowledge and collaboration being the two elements that affect the technological trajectories, having interfaces such as the “Planning & Deployment Interface” of the Research & Capabilities module will be a necessity.

However, even in the case of “normal” technical search (as opposed to the “extraordinary” exploration associated with the quest for new paradigms) strong uncertainty is present. Even when the fundamental knowledge base  and the expected directions of advance are fairly well known, it is still often the case that one must first engage in exploratory research, development, and design before knowing what the outcome will be (what the properties of a new chemical compound will be, what an effective design will look like, etc.) and what some manageable results will cost, or, indeed, whether very useful results will emerge. p. 1135

It is this paragraph that prompted me to start the process of writing the Preliminary Specification series. “Engaging in the exploratory research, development and design of the system before knowing what the outcome will be and what some manageable results will cost, or, indeed, whether very useful results will emerge.” At part 130 we have come a long way and I think we have built some value for the innovative oil and gas producer. It seems we have a long way yet to travel.

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. 

The Preliminary Specification Part CXXIX (R&C Part XXIV)

Every organization has to deal with the two distinct and differing types of work that need to be done. Simply the two types of work are the need to execute and the need to develop the firms capabilities for the future. These two roles have been separated in the Preliminary Specification with the Knowledge & Learning module, or Joint Operating Committee, concerning itself with execution. And the Research & Capabilities module, or producer firm concerned with developing its capabilities. This division of labor and specialization regarding these two types of work is the topic of discussion in today’s blog post.

Yesterday we noted that innovation was in many ways an engineering approach to problem identification and resolution. We however want to focus these innovation efforts in one area of the firm. Making sure that they are concentrated where they are most useful and the least harmful. And that is the “Planning & Deployment Interface” of the Research & Capabilities module. It is at that location that the focus can be on innovation without the impact affecting the day to day operations of the Joint Operating Committees. Only when an innovation is proven to be worthwhile should it be written up as a new capability in the Capabilities Interface, and therefore populated into the Knowledge & Learning module for use in the day to day of the Joint Operating Committees. Professor Giovanni Dosi notes;

Organizational routines and higher level procedures to alter them in response to environmental changes and / or to failures in performance embody a continuous tension between efforts to improve the capabilities of doing existing things, monitor existing contracts, allocate given resources, on the one hand, and the development of capabilities for doing new things or old things in new ways. This tension is complicated by the intrinsically uncertain nature of innovative activities, notwithstanding their increasing institutionalization within business firms. p. 1133

These support the “how to do things” (the JOC) and “how to improve them” (the producer firm). This dichotomy reflects the challenge of improving the processes and products through trial and error, with heavy emphasis on the error. The ability to accurately predict the success or failure of a new idea contains inherent high risks and hence high rewards. This is one of the constraining factors in implementing innovative thinking, in that no one wants to be proven wrong. Whereas, even if the idea fails to test the theory, the failure may ultimately lead to and may be one of the keys to discovery.

By containing the innovation within the producer firm in the manner that the Research & Capabilities “Planning & Deployment Interface” does. Limits the contamination that might occur if innovation were attempted in the areas where execution is expected. This division of labor is necessary within the oil and gas firm. As we know there are two types of people, those who are able to function best in either of these two environments. Any time these people are asked to operate in the environment that they are not oriented to, they feel uncomfortable and perform poorly.

This maybe shows a contradiction in the People, Ideas & Objects software. We assert that the software aligns the Joint Operating Committees legal, financial, operational decision making, cultural, communication, strategic and innovation frameworks. This claim that the innovation framework is part of the Joint Operating Committee is consistent with the fact that once the producer has proven the innovation is valid, then the Joint Operating Committee is the means in which it is implemented and executed through the “Capabilities Interface”.

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. 

The Preliminary Specification Part CXXVIII (R&C Part XXIII)

In today’s post I want to reinforce the point that innovation will develop from the interactions and collaborations in the “Planning & Deployment Interface”. We noted that the people assigned to the project would discuss the project and raise any issues that they may have and innovation would stem from these interactions. This process that is captured in the “Planning & Deployment Interface” is how the Preliminary Specification reduces innovation to a defined and replicable process.

Professor Dosi notes that innovation is developed through the interactions between the “capabilities and stimuli” and “broader causes external to the individual industries such as the state of science”. These are captured in the “Planning & Deployment Interface” (capabilities and stimuli) and the Work Order system (state of science) of the Preliminary Specification. As time passes the producer augments their capabilities with the findings from their research undertaken in the various Work Orders that are issued. Capabilities are implemented in the day to day activities that the firm is involved in. It is the interaction within the firm and JOC, and the broader causes that create the innovations. But there’s more.

In today’s post we take the concept of a trajectory, define it, and apply it to oil and gas. The definition of a technological trajectory is the activity of technological process along the economic and technological trade offs defined by a paradigm. Dosi (1988) states “Trade-offs being defined as the compromise, and the technical capabilities that define horsepower, gross takeoff weight, cruise speed, wing load and cruise range in civilian and military aircraft.” People, Ideas & Objects assumes the technical trade-off in oil and gas is accurately reflected in the commodity pricing. Higher commodity prices finance enhanced innovation. These “trade-offs” are very much an engineering approach and therefore I want to reiterate the point that they are “defined as the compromise, and the technical capabilities”.

These trade-offs facilitate the ability for industries to innovate on the changing technical and scientific paradigms. Crucial to the facilitation of these trade-offs is a fundamental component that spurs the change and is usually abundant and available at low costs. For innovation to occur in oil and gas, People, Ideas & Objects would assert that the ability to seek and find knowledge, and to collaborate are two “commodities” that are abundant today. With their inherent low direct costs, knowledge and collaboration are the triggers for a number of technical paradigms which will provide companies with fundamental innovations.

Therefore the ability to collaborate in the “Planning & Deployment Interface” of the Research & Capabilities module is critical to the innovativeness of the producer firm. And by extension, this would also apply to the Joint Operating Committee through the “Planning & Deployment Interface” in the Knowledge & Learning module. Innovation, as it appears in this post, is as much an engineering discipline as it is anything else. That is how we can reduce it to a defined and replicable process.

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.

The Preliminary Specification Part CXXVII (R&C Part XXII)

People, Ideas & Objects software application modules enable the producer firms and Joint Operating Committees to focus on their core competitive advantages. These being the land & asset base, and the earth science and engineering capabilities of the innovative oil and gas producer. The Research & Capabilities module of the Preliminary Specification is the key module for the innovative producer to focus on their core competitive advantages. We have been discussing the “Planning & Deployment Interface” of the module and today we want to discuss how the producer maintains the pace of change in the underlying sciences and technologies.

The simple answer to this question is that the producer and particularly the Joint Operating Committee will not have the distraction of the long term acquisition of scientific and engineering research affect the day to day implementation of the knowledge of the firm or Joint Operating Committee. Recall at the beginning of this modules review we defined the time horizons for the Research & Capabilities module, and the Knowledge & Learning module, as the long term and short term respectively. The Research & Capabilities is about the acquisition of capabilities and their documentation, and the Knowledge & Learning is about their implementation. The fact that there is a “Planning & Deployment Interface” in the Research & Capabilities module may lead to some confusion, however, it is there as there are times in which the producer firm needs to implement the capabilities that it has for its sole benefit.

This separation of the time horizon for the Research & Capabilities to take the long term perspective, provides the appropriate mindset for it to focus on the overall development of the earth science and engineering disciplines. The ability of the producer to match the pace of change in the underlying sciences and mapping the necessary changes within the “Capabilities Interface” will communicate the changes through to the organization to the various Joint Operating Committees that need that information on those capabilities. These changes and the communication of the changes to the appropriate people in a timely fashion will provide a means of increased performance for the producer and JOC. Providing a foundation for the producer to further build and implement their competitive advantages of earth science and engineering capabilities.

Restating for clarity purposes. That is how the Research & Capabilities module enables the producers to develop, implement and integrate advanced capabilities within their organization. The research undertaken by the firm should not interrupt the day to day of the operation. However, when the research augments the firms capabilities the “Capabilities Interface” is updated for that information. The capabilities as they are listed in the“Capabilities Interface” will be selected in the “Planning & Deployment Interface”. With these newly augmented capabilities, they will be deployed through to the Knowledge & Learning module, or in the case of work being done by the sole producer the Research & Capabilities module where they can be used and reused by the organization. If the research conducted by the firm is unresolved or undetermined in its conclusion then it would not belong in the “Capabilities Interface”. If it remained unresolved or undetermined then it would indicate that further work was required and therefore remain open in a Work Order for completion or resolution.

Today’s post attempts to clarify the role that Research takes in the Research & Capabilities module and how these advanced capabilities are updated and communicated through to the rest of the organization, which is predominately the Joint Operating Committee. Essentially there are perspectives of the information that need to be enforced. The Research & Capabilities take the long term perspective. The Knowledge & Learning takes the current perspective. Research that is incomplete remains open in a Work Order until resolution. Completed research augments the “Capabilities Interface” which ultimately updates the “Planning & Deployment Interface” in both the producer firm and Joint Operating Committee.

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. 

The Preliminary Specification Part CXXVI (R&C Part XXI)

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. 

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.