Intellectual Property
Back in the late 1990s I was trying to determine what asset would be the most valuable in the future. I’d always put my efforts into software and was asking if that was adequate for the future or was there something more. While contemplating the next stage of this adventure I realized that Intellectual Property was the only real asset that would exist in the 21st century and the only real asset that would provide owners of any asset with any value. Today the economic environment that exists doesn’t offer anything of the type of reward that Intellectual Property does, in my opinion, and most particularly one that is inflation and or interest rate desensitized. In the future all business will be based on some form of Intellectual Property.
At People, Ideas & Objects we believe that in order to obtain gainful employment people will need to have some form of Intellectual Property in order to do their work, or to better define this, have the right to do their work. This can begin to be acquired through the education and experience one obtains, however they’ll also have to have one of three levels of access to IP. The first is the outright ownership of their own Intellectual Property which are commonly known as copyrights, trademarks, patents and to a lesser extent trade secrets. The second is a contractual arrangement where access to others Intellectual Property is licensed to the individual or firm they’re responsible for. And the last will be as an employee of a firm that either has the IP or is licensed to use the IP. These three tiers of IP are distributed throughout People, Ideas & Objects, our user community and their service providers in the following ways.
I myself am the beneficial owner of the underlying copyright of the Preliminary Specification and its derivative works. I have licensed People, Ideas & Objects to commercially develop the ERP application, communities and all its associated needs. Our user community members are direct license holders from People, Ideas & Objects, as either individuals or as representatives of their service providers and are licensed to prepare derivative works. They also sub-license on a run-time, read only basis the Intellectual Property that our user community member has licensed access to, which is unencumbered, to the staff they employ in their service provider organization.
In order to ensure that this IP is held and developed in pristine condition. Our user community members are paid by People, Ideas & Objects for their contributions in the development of the Preliminary Specification and other derivative works such as the software code and binaries. It is in the process of this payment that we are purchasing the IP from each of our user community members in order to ensure that the entirety of it remains whole, and most importantly, available to our user community to prepare derivative works. If this was not done we would end up with an unworkable model due to the claims of individuals and trolls who would hold up the profitability of the oil & gas producers for their own monetary purposes. If it is that you have your own Intellectual Property and feel that it should be recognized then the market is available for you to do so.
There are a number of conditions that will need to be met in order to participate in People, Ideas & Objects user community. First we are seeking to provide the North American oil & gas producers with the most profitable means of oil & gas operations everywhere and always. A task that enables others in the rebuilding of the industry and sub-industries themselves. That is our objective. We are not in any way providing producers with anything to do with clean energy. The revenues of our user community and their service providers are derived from the oil & gas production. Therefore the license precludes user community members and their service providers from operations outside of the oil & gas realm. It will also preclude them from working in any area other than the domain of oil & gas ERP systems of People, Ideas & Objects, our user community and their service provider organizations. Our user community is our primary competitive advantage and is therefore not accessible to our competitors or others in the greater oil & gas, software industries or elsewhere. Our focus is exclusively on the ERP product licensed for the oil & gas producers to maximize profitability. Maximizing producer profitability is seen as an unending task.
We need to consider the possible contamination of this IP in a scenario that would disrupt this community. If a user community member or its service provider was using this IP, or augmenting their efforts with other software providers or vendors products from outside of our community. This would be a can of worms that would demand People, Ideas & Objects terminate our user community license in order to protect ourselves from any allegation or potential claim of contamination. In a world where Intellectual Property is the domain where all value is generated. In situations such as we have, where it’s not enough to own the oil & gas asset anymore, it’s also necessary to have access to the software and services that make the oil & gas asset profitable. The basis of this industry wide profitability is sourced from the Intellectual Property that is produced through this community. Value of this magnitude needs to be protected from the potential of incidental and minor actions that would appear to be non-consequential. However could be based on the actions of others outside the community who were looking to leverage the work of the community in a manner that was unproductive. Our safeguard here is to state the risk to the community of a participant that may innocently fall prey to these actions by advising them of the consequences in advance. That the loss of the license is something that could be communicated to our user community members staff within their service provider organization and those within that organization would be wise to the risk and consequences and ensure they and their service provider did not fall down that path. Sabotage by an employee is a different, criminal act that has its own remedies and would not fall under these provisions.
Membership in our user community will be maintained in the initial development period on the basis that it’s a privilege and not a right. We need to have an environment within the community where the performance of the community is maintained at the highest levels. If we have the solution for the greater oil & gas economy, a matter of opinion, then we have a commensurate obligation and hence the need to build a highly performative community. We therefore need to start by establishing the means in which our user community's performance is the overriding requirement. Methods will therefore be implemented to ensure that the lack of contributions, free riding, trolling etc are to be dealt with effectively. What I am suggesting is, that in either of these or other possible scenarios the licensing and management of the IP in the structure of our user community ensures that the community’s leadership can manage who contributes. If the community member is not able, free riding or implementing a value proposition inconsistent with the overall objective, our user community leadership, under the license provisions will have the means in which to terminate the license. The right to cull the herd will be a method that our user community will be able to ensure that quality and performance is achieved and obtained in each and every corner of the work they’re doing. Vetting is not always able to determine the best candidates. A successful implementation of the IP and software in the industry is necessary in order for our user community and their service provider organizations to succeed as organizations.
Those that contribute are compensated appropriately and will need to perform to ensure producers are able to rely on quality ERP systems. Members of the community themselves will be able to know reliably they will not have to tolerate the inappropriate behaviors and antics of those that haven’t fully participated. They’ll also not have to carry any “dead weight” with them. If you want to belong to a high performance community, these are the methods that have been used to establish other high performing organizations. Success must be obtained when the stakes are this high and the dependence is wholly upon our user community's performance. The mitigating strategy for our user community members is its part time participation during initial development and prior to the initiation of their service provider organizations. We are building upon the depth of industry knowledge necessary to ensure the full scope and scale of the application is conducted correctly and in innovative ways. There is an opportunity to determine if you qualify, can participate, if this arena is your calling where you're able to make a contribution and a difference. There are risks, and I have worked to ensure that none of these are incurred unnecessarily, however we should all agree the responsibility we have is substantial and the role our user community members have in this task is critical.
This is a challenging and difficult environment where the task appears to be impossible for many. And then it will attract exactly the kind of people that will perform in an environment such as this. One of People, Ideas & Objects first tasks is to establish the leadership group, which are full time positions. Then they’ll be able to take our user community members we have and recruit the many, many more that will be needed to cover the full needs of the applications scope and scale.
Our User Community Tasks
As a group, our user community has specific tasks that need to be completed in the first iteration of our development. These only apply to our initial development and will change once the software is operational in the marketplace. If we look at these tasks from a global perspective we are taking Oracle Cloud ERP, applying the vision of the Preliminary Specification, developing, integrating, servicing and supporting that across North American oil & gas. In terms of technical risk, I assess the project as moderate, we are using proven technologies on a large scope and scale. In terms of business risk we see the North American producers failing in their primary objective of supplying abundant supplies of affordable energy to the consumer. A failure on many levels and therefore our level of business risk has to be none. We must have this completed successfully, in my opinion. Ditto for the market risk. Our vision within the Preliminary Specification is comprehensive and has the benefit of unifying our user community in the appropriate direction for successful implementation. And most importantly we are user community driven and therefore quality software.
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 our 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’s correct and iteratively, and innovatively develop the functions and processes in ways that meet the overall vision that will be managed by the software and your service provider organization. We are capturing the manner in which the industry needs to operate profitably everywhere and always which includes everything that is on the table, exception noted below. Ensuring it is the operational, administrative and accounting manner for the future we’ll need and redefining it around the Joint Operating Committee, the other five Organizational Constructs and the vision of the Preliminary Specification.
What we don’t need in this first iteration of the Preliminary Specifications software is to have any innovation on its business model completed by our user community. What exists today in the vision works in terms of its global perspective. It may appear that in some small areas it might be better to change an element of the business model to accommodate some other condition. What we will not know is if this change upsets the global perspective and puts the overall vision out of sync in terms of its operational capabilities in other areas. The first iteration is not a time in which to innovate on the business models contained within the Preliminary Specification. This may be introduced in the second phase of the developments, when the software is operational in the market. There will be substantially more that needs to be done that is incremental to the traditional software development process that we need to ensure we don’t bite off too much of a task to begin with. I would point out that our initial needs will include such one time events as a familiarity with Oracle Cloud ERP and the other people involved in our user community and initiative which would be demanding much of our time and energy. Focusing on what works from a business model point of view would provide a consistency in terms of the understanding throughout the industry.
Once we have the software fully operational in the marketplace then we’ll 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 & gas industry with a dynamic, innovative, accountable and profitable oil & gas producer everywhere and always. This requires that constant change will be part of our developers, user community and service providers operations. People, Ideas & Objects Revenue Model is structured to generate revenues based on changes in the software which we’ll provide to oil & gas. Services revenues fall under the domain of the service provider organizations individually which are managed by our user community members who own and operate those concerns. That is the dynamic that keeps this community moving forward. Otherwise software has the effect of becoming concrete to an organization as it is the case today. 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, our user community or producer firms have to initiate the changes through these mechanisms we provide to affect that change. And in People, Ideas & Objects our user community has obtained that power through this user community vision.
What we can do, and what brings about the greatest value from the model is exploring, innovating and implementing on the interactions and implications of our model. When we move to the Joint Operating Committee and the other Organizational Constructs of the producer and industry we are changing every aspect of their operation, administration and accounting. Including within the service industry. Not much will be left unchanged in terms of the effects of implementing the Preliminary Specification. The interactions and implications are where the dramatic value will be generated for the various stakeholders in our targeted market. It is here that I expect to see the value of the model be in the forefront of our user community's search for delivering tangible value. Upon commercial release we’ll have a solid foundation in which to innovate on a known - known in terms of the Preliminary Specifications business models.
Who Will Work Within Our User Community
It's true that not everyone qualifies to work within our user community. This applies to both their leadership team and the general community. We’ll be looking for certain individuals that are unique in their skills and knowledge of the oil & gas industry. That is a given. And the diversity of those skills will make up the entire scope of the oil & gas industries administrative and accounting needs. It is these skills and understanding that are the primary concern that need to be addressed in the work that is done by our user community. The ability to analytically break down the processes and design new innovative and effective ones that are consistent with the Preliminary Specification is not something that will be easily done. That is why we have costed this work in our budget at the $345 / hour rate for our user communities participants. We are looking for people of that caliber. Recently Mr. Tom Hood, CEO, Maryland Association of CPA's published a list of 7 skills that clearly identify what is required.
As I noted the primary concern is that our user community participants be trained and experienced in the disciplines that fall within the administrative and accounting areas and their work experience fall under the greater oil & gas economy. However, we expect that there will be a strong element of Information Technology aptitude that will be inherent in their skill set. Particularly in the two areas we have mentioned before of relational databases and Java. Having a good working knowledge of these two specific technologies, on top of your current skills, will make the design and development of the software, which will be your job as a user community member and service provider, that much easier and better. The importance of this IT aptitude will make a significant difference in the quality of the People, Ideas & Objects Preliminary Specification in many different ways. Today Oracle provides an "Always Free" tier of their Oracle Cloud Infrastructure (OCI). This is available to everyone and anyone and I would encourage user community members and prospective members to sign up to be familiar with the basic structure of our systems offering.
First it will permit you to better understand the issues and opportunities that the technology provides. What is possible to you as a result of the Oracle database, its deployment in a cloud computing environment and Java, which now includes Oracle Fusion Applications the base of the Preliminary Specification, from a conceptual level offer interesting new perspectives and dimensions in ERP software. To add these to your tool kit and be able to employ them, either to use them as a service provider, or to ensure that the producers who use them are provided with the most dynamic, innovative, accountable and profitable means of oil & gas operations, should be of concern to all within the community. There is no demand here to write code at any time, that is not what we are specifying. It is the conceptual framework of these technologies that need to be addressed.
Secondly your ability to communicate with the People, Ideas & Objects developers in their primary skill set will be necessary to enhance the communications between yourself and them. It is easier for you to understand the basic elements of these concepts in relational theory and Java than it is for them to comprehend the understanding of the oil & gas industry as represented in the entire user community. Therefore to enhance the communications between the developers and our user community it is by far the easiest for our user community to speak an elementary level of the language of the developers. As there is no way in which each developer is ever going to fully comprehend the scope and scale of the oil & gas industry contained in our user community. Particularly since no one else carries that body of knowledge around individually.
This understanding of the technology may take four or five university level courses in order to acquire the type of understanding that I think is necessary. We are seeking to communicate effectively with developers. Think of it as an investment in order to earn those handsome hourly rates and resolve industry issues. The thing about providing the oil & gas producers with the most dynamic, innovative, accountable and profitable means of oil & gas operations. Is that you are able to prove substantial value propositions such as what we have. And therefore, as a result everyone benefits monetarily.
Some Technical Points of Interest
Now for the relational database geek in all of us, I provide the videos of the last number of keynote presentations by Larry Ellison founder of Oracle Corporation. These are technical. Understanding the basis of relational databases and the Java Programming Language from a high level will provide any participant in our user community with a better knowledge and understanding of how the system is put together. And the best place to get that understanding is from C. J. Date, An Introduction to Database Systems
Here are Larry Ellison’s last number of keynote addresses, all are must see viewing for members of our user community.