The Preliminary Specification Part CCLXV (K&L Part XXXIII)
This will be the last post of our fourth or capabilities pass through the Knowledge & Learning module. It has been in the Research & Capabilities and the Knowledge & Learning modules that Professor Richard Langlois work has been of most value. We will continue on with the review of Professor Langlois in the Performance Evaluation, Analytics & Statistics and Compliance & Governance modules and then in the fifth pass we will be taking a different perspective on the Preliminary Specification. The fifth pass will combine two elements during its review. The first will be the application of Oracle’s Fusion technologies which are the base technologies of the Preliminary Specification. The second element is some of the more common components of an ERP system. We have covered off what an innovative ERP system looks like, we need to include how that innovation interacts with the day-to-day of an ERP system. So those will be the focus of the fifth pass through the specification. I am tentatively scheduling the sixth pass to be a deeper dive into the same elements as we may not be able to make sense of everything in the first pass and will need two runs through to be coherent.
If we go back to the previous modules we recall the discussion around moving from the “high throughput production” model to the “decentralized production” model that was being conducted in the Preliminary Specification. Essentially the “decentralized production” model has all of the costs, production and overhead, match the revenues. So when there was no production, there would be no costs associated with any shut-in production. The “high throughput production” model is something that the bureaucracy can do. It is their means of managing and is how they are able to provide value in the organization. That “high throughput production” is incapable of providing value today is a matter of the time and place that we find ourselves in. Using the “high throughput production” model requires the bureaucracy to summarily ignore the Joint Operating Committee as the key organizational construct of the oil and gas industry. It can not do both, “high throughput production” requires the designation of operatorship be granted to one partner for control over the property.
Industrial structure is really about two interrelated but conceptually distinct systems: the technology of production and the organizational structure that directs production. These systems jointly must solve the problem of value: how to deliver the most utility to ultimate consumers at the lowest cost. Industrial structure is an evolutionary design problem. It is also a continually changing problem, one continually posed in new ways by factors like population, real income, and the changing technology of production and transaction. It was one of the founding insights of transaction-cost economics that the technological system does not fully determine the organizational system (Williamson 1975). Organizations — governance structures — bring with them their own costs, which need to be taken into account. But technology clearly affects organization. This is essentially Chandler’s claim. The large-scale, high-throughput technology of the nineteenth century “required” vertical integration and conscious managerial attention. In order to explicate this claim, we need to explore the nature of the evolutionary design problem that industrial structure must solve. p. 50
With the Preliminary Specifications adoption of the “decentralized production” model and the recognition of, and technical support of the Joint Operating Committee. The elements of change are in place. It is the culture of the industry to use the Joint Operating Committee, it is an industry that is based on partnerships and the closer we move to that culture the greater alignment (speed, innovation, and accountability) we will achieve. This next quote should be read twice with either the hierarchy or the Joint Operating Committee in mind.
And there are certainly examples of this. But it is also possible that a structure of organization can persist because of “path dependence.” A structure can be self-reinforcing in ways that make it difficult to switch to other structures. For example, the nature of learning within a vertically integrated structure may reinforce integration, since learning about how to make that structure work may be favored over learning about alternative structures. A structure may also persist simply because the environment in which it operates is not rigorous enough to demand change. And organizations can sometimes influence their environments — by soliciting government regulation, for instance — in ways that reduce competitive rigors. p. 58
This discussion elevates the importance of the Research & Capabilities and Knowledge & Learning modules in defining how the industry operates. These modules remove the task of how the industry is operated from the hands of the bureaucracy and moves the operations to the Joint Operating Committee. It is therefore a critical module.
Over time, two things happen: (a) markets get thicker and (b) the urgency of buffering levels off and then begins to decline. In part, urgency of buffering declines because technological change begins to lower the minimum efficient scale of production. But it also declines because improvements in coordination technology — whether applied within a firm or across firms — lower the cost (and therefore the urgency) of buffering. p. 78
As a point of interest when I read that last quote I became concerned for the Natural Gas business in North America. The size of the Natural Gas storage business has become so large as to dwarf any real purpose for its existence. The other aspect is, the storage business is no longer in the hands of the producers. How in a market economy will the producers ever get market prices for their product again?
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.
