Some Operational Concerns
We’ve had a lot of fun this past week highlighting the conflict and contradictions that we find ourselves in. Bureaucrats are bureaucrats whether they exist within the producer firm or in the firms that invest in the oil and gas producer. And those investors continue to invest in the oil and gas producers. My argument about investors subsidizing consumers for their costs of energy doesn’t seem to have been made. Maybe the oil and gas investors should just buy the commodities instead of the producers. They’ll get the same performance but with no risk of the firm defaulting. Which brings into question what is it that the bureaucrats are doing if they’re just mirroring the commodities moves. I thought I read somewhere at sometime that the point of management was to eliminate the downside risk of investing in the commodity.
One area that the bureaucrats criticize me for is the broad scope and scale of the Preliminary Specification. Applying this across the industry would be difficult and doesn’t seem, to them, to be a viable solution to the issues facing the industry. I agree with the scope and scale point of view. It is very broad and includes the accounting, administration and operations of an oil and gas producer. Which raises the question how is it that the bureaucrat is able to cobble this solution together within their own shop, but feels it would be impossible on a broader scale? I will have a much more efficient budget where the costs of operations will be covered on a greater percentage basis than they can achieve. For example, the costs of managing an email server takes 30% of one individual's time within the producer. Whereas it may take ten fully committed specialized team members at People, Ideas & Objects. Yet these ten team members costs when allocated over the production profile of the industry will be mere pennies on the dollar compared to the individual producer's costs. We also have the advantage of specialization and the division of labor to expand the industries capacities and throughput when and where it is necessary. These traditional economic tools are not available to the bureaucrats small internal technical teams with their limited capabilities when applied against this broad scope and scale. We also have the budget in terms of our ability to research and develop new initiatives and capabilities that will provide value to the producers in the future. Something that the producers don’t appear to have today.
If we were to commence developments without the full budget secured. Then we would be at risk of having the bureaucrats cancel our project each time the price of oil went up by more than $2.00. Their attention spans do not breach the next quarterly report. Therefore we need to have these resources secured to ensure that the outcome of the project is viable, but there is a far more important issue here. The bureaucrats are vindictive and will take the baseball bats to those that are involved in this project. If those people find that their opportunities in this initiative are suddenly cut off, then they’ll only have the angry, vindictive bureaucrats to deal with to save their careers. No one should have to commit career suicide in order to save the industry from these most lovely people.
I want to point out why Exxon, BP, Shell and Chevron can’t go it alone in terms of their own systems development and why we need them in the user community. The big guys like to do things their own way and we can all understand their reasoning for that. But we need them. It is their production profile that will be responsible for offsetting much of our costs. Or in other words they’ll be paying most of the freight. They’ll be doing that anyways with their own systems development, and once their system is built there will be no one else that’ll touch it. Is Devon going to want to use a system that was developed by Exxon? People, Ideas & Objects independence from any individual producer, working on behalf of the best interests of the producers, providing producers with the most profitable means of oil and gas operations, is the objective way in which all producers, large and small can willingly use a system that was designed and developed by a user community.
I’d also like to point out the recent discussion we had regarding IBM and Oracle’s participation in the oil and gas ERP marketspace. After many years of trying to secure support from the producers they were wholly unsuccessful and left the market. All of the producers stood united together expecting that the Information Technology vendors would be the ones that “invested” in the producers ERP applications. IBM and Oracle could see the devastation that had been created in the oil and gas ERP space over the years. For more on that read our Revenue Model. Now, outside of the existing SAP and P2 installs which have no further development plans, there is only People, Ideas & Objects who have a value proposition in the trillions of dollars, which coincidentally has been determined to be not a good enough effort by the producers and their investors. The fact of the matter is they wouldn’t do anything then, and they don’t do anything now. The only difference today is that I have provided them with a comprehensive vision of how and what the producer and industry would need to operate in order to earn our multi trillion dollar value proposition. Creative destruction is about the old being washed away by the new. We obviously don’t know who will be the ones who step up to earn those trillions of dollars. What we do know is it's not the existing bureaucrats.
The Preliminary Specification and user community provides the oil and gas producer with the most dynamic, innovative, profitable and successful means of oil and gas operations. People, Ideas & Objects Revenue Model specifies the means in which investors can participate in these user defined software developments. Users are welcome to join me here. Together we can begin to meet the future demands for energy. And don’t forget to join our network on Twitter @piobiz anyone can contact me at 403-200-2302 or email here.