Council on Foreign Relations on the e...
Technorati Tags: People's Economics Change Leadership
OUR PRELIMINARY SPECIFICATION MAKES SHALE COMMERCIAL. THROUGH AN INNOVATIVE BUSINESS MODEL SUPPORTING THE JOINT OPERATING COMMITTEE, WE PROVIDE OIL AND GAS ASSETS WITH THE MOST PROFITABLE MEANS OF OIL AND GAS OPERATIONS, EVERYWHERE AND ALWAYS. ENABLING THEM TO ACHIEVE ACCOUNTABLE AND PROFITABLE NORTH AMERICAN ENERGY INDEPENDENCE. OIL AND GAS’ VALUE PROPOSITION IS AT A MINIMUM, LEVERAGED TO THE POINT OF 10,000 MAN HOURS PER BOE. WE KNOW WE CAN, AND WE KNOW HOW TO MAKE MONEY IN THIS BUSINESS.
Posted by Paul Cox at 10:55 PM 0 comments
Labels: Change, Economics, Leadership
Former Mexican president Vicente Fox called for an energy "super-body" that goes beyond politics, ideologies and business interests to help create a unified global approach to the industry.
"(There are) too many interests, too many diverse positions, too many sources of information, What I would love to see is a leader . . . somebody should bring in some order into the conducting of the issue of energy in the future," he said in an interview before his speech. "I don't see that happening in energy."
According to Fox, assembling the talent of leaders, researchers, think-tanks and universities would help create a common purpose: "Getting energy to its optimum in the future so that energy fuels economies of the world, and so that economies of the world, being successful, fuel jobs and fuel opportunities for people."
Posted by Paul Cox at 5:58 PM 0 comments
Labels: Community, Economics, Energy, Leadership
With the release of Mac Chrome to the dev-channel, I wanted to talk about open source and expectations. What was the point of releasing at this stage, you might ask? It's clearly not finished. Clearly. It's missing a large number of features, some half implemented, others not at all. Why even bother? Doesn't it just make us look bad?
Open source projects aren't simply about a runnable binary, they're about the community of users, testers, and developers who devote their time and skills to working on a product they believe in. They go hand in hand: there's no binary without the community and there's no community without the binary. At some point in the life-cycle of a project, you have to stop thinking solely about your small band of developers and start growing the larger supporting community that will become your users, testers, localizers, documentation writers, and possibly even new coders.
In "The Cathedral and the Bazaar", Eric Raymond writes:
"When you start community-building, what you need to be able to present is a plausible promise. Your program doesn't have to work particularly well. It can be crude, buggy, incomplete, and poorly documented. What it must not fail to do is (a) run, and (b) convince potential co-developers that it can be evolved into something really neat in the foreseeable future."
We're not done yet, nor is it ready for the average user. It is, however, ready for those who want to live on the bleeding edge and help lend their talents towards completing it.
Another pillar of open source, along with releasing early, is releasing often. To that end, the dev channel will automatically receive weekly updates as development continues. You will be able to see the product improving from week to week and help immediately identify when things break. Getting feedback on new features as soon as they are completed helps the developers know if they hit the mark and helps close the feedback loop with the community. The community benefits by being more involved and connected and promoting further transparency in the development process. This wouldn't be possible if we only teased users with releases at widely-spaced intervals when most decisions had been set in stone (end-users who want that can use the beta or release channels).
Posted by Paul Cox at 8:04 PM 0 comments
Labels: development, Google, Open Source, User
Posted by Paul Cox at 10:09 PM 0 comments
McKinsey Consulting are providing a 14 minute video of Peter L. Bernstein talking about risk. This is a fascinating and valuable video that I promise you will learn one or two things about risk. It's unfortunate that the video marks the passing of Mr. Bernstein, but I have put his book "Against the Gods: The Remarkable Story of Risk" in my library.
Technorati Tags: People's McKinsey Algorithms Learning Video
Posted by Paul Cox at 9:16 PM 0 comments
Labels: Algorithms, Learning, McKinsey, Video
Posted by Paul Cox at 11:20 AM 0 comments
Labels: Community, development, Economics, Funding, Value-Proposition
On MasterResource, "a free market energy blog", the author Robert Bradley has a summary of the ExxonMobil Annual Meeting. First of all it is satisfying to see an energy company that doesn't indulge in the politics of climate change or the folly of alternative forms of energy. Those within the industry that are in the know, know that the exploration and development business has entered a more scientific level of complexity.
Petroleum as a primary energy source is the future, not only the recent past. (Comment: renewable energies once had a 100% market share, corresponding to mankind’s energy poverty era.)
Although renewables and alternatives are growing, their overall piece of the energy mix will remain small until they reach the massive scale at which fossil fuels are used. And Exxon won’t invest beyond research until renewables are profitable without subsidies, Tillerson said.
Posted by Paul Cox at 8:48 PM 0 comments
Labels: Energy, Innovation, Management, organization
With Google Wave I think we have a clear direction where the future of Information Technology is headed. There is an hour and twenty minute video of the Google Developers Conference announcement of their Wave product. Although it is early, I do not see to many hurdles to having the product shipping. Clearly the technology is not the key attribute of the value of the Wave product, its the implementation.
Lets quickly dispatch the techno speak with this one paragraph. Wave is open source, Java and uses the Google Web Toolkit. (Renders browser based code from Java.) All within the technology stack used by People, Ideas & Objects. The one technology that is not available is the W3C's HTML 5. I do not foresee HTML 5 having too much difficulty in being implemented quickly. HTML 5 provides some persistent data storage which is provided by the able Google Gears in the product demonstration.
So why is Google Wave an important technology for users and producers of People, Ideas & Objects. I will be augmenting the Draft Specification to include the video and this text. If we go back through this blog and the ideas that were used to build the Draft Specification. We focus on three key areas and some minor additional points. The three key areas in descending order of relevance are the Accounting Voucher Module, Military Command & Control Metaphor and Security & Access Control Module.
Recall in the Accounting Voucher we are capturing the changes in the business on a month to month basis. As "things" happen they are captured and recorded in the Accounting Voucher for future use. If this isn't making any sense then please review the Accounting Voucher part of the Draft Specification to better understand what it is that I am saying. The accounting changes that are captured in the Voucher are the discussions, documents and decisions that are made. The Accounting Voucher is capturing and recording the financial impact of these changes. It is the Google Wave infrastructure that we inherit, by using its open source code, and enhance it to incorporate the ability to capture these financial changes.
As the video reflects, we acquire these in a unique interface provided by Google. Representatives of the various producers on the Joint Operating Committee (JOC) interact on the topics of interest in the JOC. These are in documents, asynchronous communication, synchronous communications and in all the media available. The mode of these interactions are person to person, person to process, process to person and process to process as I noted in the Preliminary Research Report. A rich environment that provides the media, mode and method of communications that are necessary to support the innovative oil and gas producer.
The Military Command & Control Metaphor is used throughout the Draft Specification as the means to provide the dynamic resources provided by the producer members of the JOC. Much as the pooling of military resources is done by the NATO forces, the People, Ideas & Objects application is able to dynamically assign the corporate governance, authority, role and responsibility necessary to efficiently and innovatively manage the Joint Account. This Metaphor is used throughout the application, but most importantly one that controls the interaction of the communication and documentation contained within the Google Wave open sourced code.
Lastly I want to reiterate the importance of the Security & Access Control Modules use of Sun Microsystems Federated Identity software as the means to ensure these corporate governance needs are maintained in such a dynamic manner. I would encourage readers to spend some time in these elements of the People, Ideas & Objects application. It is an area that I think the innovation could and will prosper and is ripe for the users to exploit for their advantage; and please join us here.
Posted by Paul Cox at 11:00 PM 0 comments
Labels: development, Military Command, Specification
Oil giant Royal Dutch Shell on Wednesday announced a series of changes to senior management roles and responsibilities, which it said were aimed at creating a sharper focus on operating performance and technology.I interpret these changes as an admission that the engineering and earth sciences necessary for each barrel of oil produced are increasing. The Calgary Herald reported that Voser said:
"Organisationally, we are too complex, and our culture is still too consensus-oriented. Our costs are simply too high," Voser said in an email to staff, excerpts of which were seen by Reuters.Details of the changes include the consolidation of divisions into operating units around geographical locations. North America being one in which I would assume Houston will take the lead role in. It is also reported that many lay offs will occur throughout the company.
Exxon is renowned within the industry for its strict management practices and insisting employees do not deviate from standard operating procedures. BP, on the other hand, had a risk-taking culture that allowed considerable freedom to managers of units or fields, and Shell had a culture of making decisions by consensus.
Posted by Paul Cox at 3:10 PM 0 comments
Labels: Capabilities, Change, Engineering, Geology, Governance, Specification
Posted by Paul Cox at 12:19 PM 0 comments
Labels: Government, Leadership