The first step in this initial development phase is therefore to implement the model that is the Preliminary Specification. This vision provides the broad outline of what and how the applications need in order to operate. The details of how each individual's work needs to be handled is the work of the user community to fill in, define and ensure that our developers provide you with the systems that you want and need. For example, if you are working in an area where the Material Balance Report is part of the domain of your work. You will collaborate with others to determine what is required, ensure that it is correct and iteratively develop the functions and processes that will be managed by the software and the service providers. In many ways we are capturing the manner in which the industry operates today from an operational, administrative and accounting manner and redefining it around the Joint Operating Committee and the vision of the Preliminary Specification.
What we don’t need in this first iteration is to have any innovation completed by the user community on the business models contained within the Preliminary Specification. What exists today in the vision works in terms of its global perspective. It may appear that in some small area it might be better to change an element of the model to accommodate some other condition. What we will not know is if this change will upset the global perspective and put the overall vision out of sync in terms of its operational capabilities. The first iteration is not a time in which to innovate on the business models of the Preliminary Specification.
What we can do, and what brings about the greatest value from the model is exploring and implementing the interactions and implications of our model. When we move to the Joint Operating Committee as the key organizational construct of the producer. We are changing every aspect of the oil and gas producer, the industry and service industry. Not much is unchanged in terms of the effects of implementing the Preliminary Specification. The interactions and implications are where the dramatic value is generated for the various stakeholders in our targeted market. It is here that I expect to see the value of the model to be in the forefront of the user communities search for delivering on that value in the first iteration of the development.
Once we have the software fully operational in the marketplace then we will be able to innovate on the model, and determine further interactions and implications within the various domains of our operation. We are focused on providing the oil and gas industry with a dynamic, innovative, accountable and profitable oil and gas producer. This requires that constant change be part of the user community and service providers. People, Ideas & Objects Revenue Model is structured to generate revenues based on changes within the industry. That is the dynamic that keeps this community moving forward. Software has the effect of becoming concrete to an organization. Turning it into an unchangeable beast. If an organization needs to change, it is the software that needs to change first. And in order for the software to change, the user community has to be the ones that make the changes through the mechanisms they have to affect that change. And in People, Ideas & Objects that is our user community vision.
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.