In businesses such as People, Ideas & Objects we have three main risk categories to deal with. We have financial, market and technical risks that must be addressed in order to succeed. This post is going to briefly address some of the technical risk that we face and how that risk impacts our budget needs. Embarking on a multi-billion dollar project without addressing these technical risks would be like bungee-jumping without the rope.
Firstly we should point out a decision that we made a few years ago that mitigates much of our technical risk. That is, the use of Oracle Fusion as the base ERP application at the core of People, Ideas & Objects (PI&O) applications. Our products will be built on Oracle's RDBMS, Java and Fusion Middleware which provide us with further ability to mitigate our technical risk by using best of breed in those product categories. The costs of these Oracle products are incremental to the software development budget we have been discussing in this and recent posts.
People, Ideas & Objects is based on a
Technical Vision that uses existing technologies in ways that the oil and gas industry will need to implement them. One that sees technology being ubiquitous, always on, secure, asynchronous and dynamic. An environment where the oil and gas industry is supported by a software development capability in addition to the People, Ideas & Objects applications that will be provided. This environment has to be purpose built and that is what PI&O is setting out to do. The technical risks of bringing this environment to the producers that subscribe to this community are mitigated through the ability of controlling the various technical, financial and market risks through the Intellectual Property that holds these disparate parts together.
At the same time we are not pushing the technical envelope. All of the technologies and their proposed deployment are proven time and again capable of the job that we are asking of them. There is a maturation of the technologies in the past ten years that provides an assurance that they are up to the task. I also expect that in the next ten years they will continue to provide greater levels of confidence and assurance of their capabilities.
What can only be described as a revolution in development tools and methodologies has occurred in the past decade. These tools and methodologies have reduced the time and budget requirements of software development projects, while at the same time increased the quality of the deliverables. People, Ideas & Objects have adopted these tools and methodologies and will implement them to reduce the time required for developments, the budget for developments and increase the quality of our developments. Ten years ago when compilers had to be purchased for several thousands of dollars per developer; have now been replaced by free IDE’s that exponentially accelerate the developers productivity. Methodologies who’s user focus is a religion. And build on frameworks and middleware (like Oracle Fusion Middleware) that provide an architecture and building block of work already done. Developers today are far more productive which reduces our risk.
Our approach to developments also mitigates much of the technical risks associated with a project of this size and type. The Draft Specifications use of the Joint Operating Committee imputes a scope of operations that involves the entire producer firm. Little of the unique characteristics of the applications
Marketplaces and
MCCM exist in current legacy systems. Therefore we are limiting the involvement of legacy system requirements to data only. As such we are unconstrained by existing requirements of systems limitations based on prior technologies. Ours is more of an engineering approach of identifying and resolving problems.
Transitions, accounting integrations, training, and the variety of tasks related to software’s use are not part of People, Ideas & Objects business model. We are focused on software development. We defer the remaining businesses and opportunities to the
Community of Independent Service Providers to fulfill the needs of the producers in these areas. This is the only reasonable means in which to approach the hands-on and large scale necessary to complete these activities.
It is these opportunities that I see mitigating the technical risks that we face in this software development project. Although our budget is large, it would have been impossible only a few short years ago. The technologies are sound and capable, ready to carry the load. We have only our imaginations holding us back in terms of how this industry could be managed more efficiently.
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.
Email me here if you need an invite.