The Preliminary Specification Part CCXXX (R&C Part XL)
We have discussed modularity many times with respect to the Preliminary Specification. With eleven modules in the specification we have relied heavily on the principles of modularity to ensure that the user is provided with usable systems. In today’s post we are going to take modularity to a deeper level. In the past few days we have been discussing the unique organization that is created to complete a field operation. These organizations are derivative of the Joint Operating Committee and include members of the service industry. They are authorized, controlled and operated in the People, Ideas & Objects system through the “Capabilities Interface”, “Planning & Deployment Interface”, “AFE”, and “Job Order” systems to name a few. These make up a modular system that are part of the “modularity” benefits that we are seeking to achieve in this temporary organization and the Preliminary Specification.
Looking at the operation in the field through the lens of modularity can help us to deal with complexity and to simplify the interactions between the different situations and people. From Professor Richard Langlois paper “Modularity in Technology and Organization”.
Modularity is a very general set of principles for managing complexity. By breaking up a complex system into discrete pieces - which can then communicate with one another only through standardized interfaces within a standardized architecture - one can eliminate what would otherwise be an unmanageable spaghetti tangle of systemic interconnections. p. 1
Having difficult systems interconnections is a minor issue when compared to the real problems that people will have with systems that are too complex and too “different” each time they go to use them. As Professor Sidney Winter of the Wharton School of Business in his paper “Towards a Neo-Shumpterian Theory of the Firm” notes.
Carrying out a new plan and acting according to a customary one are things as different as making a road and walking along it. (p.85) p. 9
It is therefore imperative that we apply modularity theory to the design of the temporary organization that makes up these derivative organizations.
What is new is the application of the idea of modularity not only to technological design but also to organizational design. Sanchez and Mahoney (1996) go so far as to assert that modularity in the design of products leads to - or at least ought to lead to modularity in the design of the organizations that produce such products. p. 1
Remember we are spanning the oil and gas industry and the service industry. The marketplace and the firm. And suddenly the scope and budget of the Preliminary Specification doesn’t seem large enough. To achieve the efficiency and effectiveness of the interactions between the two industries will require this approach. Can it be done in an ad-hoc or other fashion? Are we dealing with Information Technologies that are in their infancy? Or are we dealing with the limited and self interested minds of the bureaucracy?
To incorporate elements of modularity into the systems that we build we have certain design considerations to include. In terms of the temporary organizations that we are creating here for these operations, I think the key focus will have to be on standards.
Recently, Baldwin and Clark (1997, p. 86) have drawn on similar ideas from computer science to formulate some general principles of modular systems design. The decomposition of a system into modules, they argue, should involve the partitioning of information into visible design rules and hidden design parameters. The visible design rules (or visible information consists of three parts.
• An architecture specifies what modules will be part of the system and what their function will be.
• Interfaces describe in detail how the modules will interact, including how they fit together and communicate.
• And standards test a modules conformity to design rules and measure the modules performance relative to other modules.
These visible pieces of information need to be widely shared and communicated. But contrast, the hidden design parameters are encapsulated within the modules, and they need not (indeed, should not) be communicated beyond the boundaries of the module. p. 7
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.