The Preliminary Specification Part CXLII (K&L Part X)
In today’s post we want to talk about the publication of the specific Joint Operating Committee calculations of Revenue Per Employee, and particularly the trajectory that the factor is on. How this calculation could affect those that work within the property; and the use of the information contained within the Knowledge & Learning module of the Preliminary Specification.
First of all it is understood that not all people are necessarily assigned to work for one Joint Operating Committee. There are times when people might be assigned to dozens during the course of one month. Calculating the hours worked by the people within the Joint Operating Committee from the different companies is not going to be a difficulty for the People, Ideas & Objects software. With the Military Command & Control Metaphor the time and tasks that each individual will be doing is being recorded for these information purposes. Although most will only work part-time on a JOC, the factor will be converted on a full-time equivalent basis. Calculations of revenue for the property should be straight forward.
In previous posts we had discussed the calculation of a comparison of the factor of revenue per employee from one period of time to the other. These trajectories were the real key in determining where the factors were heading. Was the property accelerating its innovativeness, or decelerating. We also broke down the trajectory into three different types of variances. The volume variance, price variance, and employee # variance. Each of these variances reflecting the reason why the trajectory might have changed. All of these variables should be shown on their own “Revenue Per Employee” interface within the Joint Operating Committee. Each member that is assigned to the property should have access to this page and be able to contribute ideas and suggestions on how to improve the factor. An open collaboration focused on revenue per employee. In addition, this page could have a historical context of many time periods captured in a graphical format. Showing over the past many years how the revenue per employee at that Joint Operating Committee has performed.
A few days ago we also learned that revenue per employee reflects the asymmetry of the assets within the industry. That asymmetry would be very apparent in a comparison of Joint Operating Committees. We would see large variances in revenue per employee between Joint Operating Committees. And I am not suggesting that the comparisons are valid, just pointing out that the industry has a large asymmetry in their competitive makeup. The comparison of revenue per employee for the same property over time, I think, will have a significant impact on the people that work for that Joint Operating Committee.
One certain way to increase the factor of revenue per employee would be to fire all the employees. However, the best way to deal with the factor is described by Professor Giovanni Dosi when he 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.”
Members of the Joint Operating Committee would be able to turn to the “Capabilities Interface” which contains the capabilities of the producer firms that are part of the partnership. There the people would be able to see what the firms offered in terms of their earth science and engineering problem solving solutions. It may then be realized that applying some formerly unknown capability to the situation in the JOC will yield greater productivity... or something like that.
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.