The Preliminary Specification Part CCXXXIII (R&C Part XLIII)
We continue on with our review of Professor Richard Langlois’ research in this our fourth pass through the Research & Capabilities module of the Preliminary Specification. The last few posts may have been a little confusing in that the focus might have appeared to be on the Knowledge & Learning module with the strong Joint Operating Committee focus. That is one of the possibilities with these specifications being so close in terms of their functionality. Recall too that the “Capabilities Interface” which is detailed in the Research & Capabilities module is populated into the Knowledge & Learning module for deployment purposes. This confusion between the modules will appear from time to time and is otherwise unavoidable and immaterial.
It is in the “Capabilities Interface” that we are seeking to document the “what” and “how” of the operation the Joint Operating Committee will undertake. It is very important to note at this point that the tacit knowledge that makes up that operation can not be documented. It will however be invoked through the orders in the Job Order system. The depth of “knowledge, skills and experience” that is documented in the “Capabilities Interface” includes the members of the Joint Operating Committee, their roles and responsibilities, and the field operations personnel. Detailing what and how they need to do their jobs in order to attain the objective of the operation. In a paper entitled “Transaction Costs in Real Time” Professor Langlois notes:
Although one can find versions of the idea in Smith, Marshall, and elsewhere, the modern discussion of the capabilities of organization probably begins with Edith Penrose (1959), who suggested viewing the firm as a 'pool of resources'. Among the writers who have used and developed this idea are G.B. Richardson (1972), Richard Nelson and Sidney Winter (1982), and David Teece (1980, 1982). To all these authors, the firm is a pool not of tangible but of intangible resources. Capabilities, in the end, are a matter of knowledge. Because of the nature of specialization and the limits to cognition, organizations as well as individuals are limited in what they know how to do effectively. Put the other way, organizations possess a pool of more-or-less embodied 'how to' knowledge useful for particular classes of activities. pp. 105 - 106.
That’s an effective way to state what it is that we are trying to achieve here. The “Capabilities Interface” is a how-to database of capabilities the firm has for getting things done. Or;
'Routines,' write Nelson and Winter (1982, p. 124), 'are the skills of an organization.' p. 106
Now here is the point where we need to pay attention. Both figuratively and literally. In this post as well as in any and all oil and gas field operations. The ability to do any of these tasks on auto-pilot doesn’t exist. And the implications of the next quotation is far reaching.
Such tacit knowledge is fundamentally empirical: it is gained through imitation and repetition not through conscious analysis or explicit instruction. This certainly does not mean that humans are incapable of innovation; but it does mean that there are limits to what conscious attention can accomplish. It is only because much of life is a matter of tacit knowledge and unconscious rules that conscious attention can produce as much as it does. p. 106
It will need to be the explicit instruction contained within the “Capabilities Interface” that guides the field operation. The conscious attention necessary to follow the program is a necessity. However, this is also about innovation. If there is an opportunity for further innovation. There is the Job Order system in which to invoke the request for a change in orders.
In a metaphoric sense, at least, the capabilities or the organization are more than the sum (whatever that means) of the 'skill' of the firms physical capital, there is also the matter of organization. How the firm is organized - how the routines of the humans and machines are linked together - is also part of a firm's capabilities. Indeed, 'skills, organization, and technology are intimately intertwined in a functioning routine, and it is difficult to say exactly where one aspect ends and another begins' (Nelson and Winter, 1982, p. 104). p. 106
One thing I can say for certainty is that the technology begins with People, Ideas & Objects. By developing the Preliminary Specification the producers will be able to attain the level of innovativeness and operational control that is described in these posts.
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 (private circle, accessible by members only) and begin building the community for the development of the Preliminary Specification.