This post is about the technological competitive advantages of People, Ideas & Objects. The unique advantages that technological developments bring to our approach to ERP systems development. It's important that users and producers understand how our advantages can deliver the systems as defined in the Draft Specification. If people are not sure if what we are doing is even technically possible. Then it is difficult for them to see how a start-up can take such an opportunity and deliver on it. In a nutshell, yes we can. The proof has been written about elsewhere and I will refer to these so the individual can do their own research. This is important, as I do not expect anyone to have to take a leap of faith that this risk is not being identified and addressed.
I want to also stress that the identification of yourselves to any producer as being affiliated with this project is not advisable. The management of the oil and gas companies are not constructively approaching the systems or organizational needs of the innovative oil and gas producer. Secondly, to suggest that the individual give up their current career for this opportunity would be too much to ask. I would only expect that people would be involved with this project on a part time basis to begin with.
Contrast the competitive advantages that are being developed in People, Ideas & Objects to the competition. Oracle has spent $39. billion to bring out their Oracle Fusion product. How has this product been built to deal with the issues of the innovative oil and gas producer? SAP has a checkered past in the industry and they too have what I would consider critical faults in their offerings.
The first thing is to define the priority of the development. In systems you can have any two of three priorities. Either 1) the speed of development, 2) the quality of the development or the accuracy of meeting the users requirements, or 3) effective cost control. Making this decision is academic when we consider the scope of the application, the financial resources of the oil and gas industry and our fundamental value proposition and business model. The speed and quality can be attained in a start-up, I'm not certain that it can be built into a large organization such as SAP or Oracle. Our speed and accuracy are something that have been available to SAP and Oracle in the past. Asking them to overcome the speed and focus I know is too much.
The key technological advancements that make People, Ideas & Objects the most competitive in the oil and gas marketplace are as follow.
Java
By for the most powerful of programming environments. And blah, blah, blah techno talk. Needless to say this is an easy and unanimous choice.
Frameworks
Employing the re-usability of Java. Rebuilding everything from scratch is just not necessary. So much infrastructure and capabilities have been built into open source and other frameworks. Providing infrastructure and capabilities at a level that enables flexibility without the constraints.
Open Source
In combination with Agile / Scrum, Frameworks and Java, Open Source brings so many of the qualities that it is hard to document them all. Realizing the value in software development is in the journey, not the destination.
Data Model
Maybe one of the more difficult decisions, but this is what we have so far. We will be using the Professional Petroleum Data Model (PPDM) data model. And in answer to the technical question are we relational or object relational, I'll need to be convinced that an object relational model would work in a complex application such as People, Ideas & Objects. Until then we are relational. Performance may not be as fast, however, accuracy will be predictable.
The PPDM data model has the combined efforts of the industry in defining a data model for use by members of the petroleum industry. Our use of this work, which is substantial, eliminates a difficult area of concern. PPDM increases the quality of the subsequent developments. At the same time I think PPDM's data model has not been rigorously tested in the marketplace. And therefore we will be looking critically at the data model to see if it can be enhanced through a more strict interpretation of
Relational Theory. And if it can be optimized for the innovative oil and gas producer.
Modular Specification
The Draft Specification is modular for a reason. Modularity is a key attribute of simplifying systems development. Interactions between modules are easily handled and the overall system design can be accommodated. In total we will be employing fifteen development teams in the agile / scrum development methodology.
Agile / Scrum
This is a method that has simplified development to its most efficient.
Scrum increases the performance of a development team from two to ten times the standard. That's correct, a two to ten fold increase in productivity. This doesn't sound at all believable but I can assure you it is true. Although it is open and available to anyone that wants to strive to achieve these multiples of development efficiency, it is difficult to implement retroactively in teams that have been together for a long period of time. Many developers are unable to transition.
One of the key attributes of Agile Scrum teams is the focus and role of the user. It is critical and the methodology makes itself accountable to those users in quick, short, intense development periods. I'll talk more about this methodology in the future, one of its key advantages is that the team can be distributed as far, and as wide as is required. Enabling the best of the best developers to be recruited and involved in this development. The key mode of communication between users and developers is the
User story.
User Driven
You can not expect the user to be satisfied with systems that do not involve them. Users can not expect worthwhile systems that they did not have a hand in. The difficult and time consuming aspect of building systems to the users specification is the development of the community. People have had time to be able to codify these ideas and think of new and innovative ways for the system to be built to deal with a nuance of their day to day activities in their jobs. This will be the real key competitive advantage of this community.
User Interface
I don't use Windows systems. Two hours with one of those machines and I get frustrated either at the slow pace of my work or the fact they seem to break every time I push them. Using Mac's as machines and Unix / Linux are the only ways in order to deal with computers.
I have a wonderful ability with computers. When I started in oil and gas in 1977 I was introduced to them and they have been my friends since. In fact all my best friends are computers. The way we interact with them is critical to the productivity of the user. To ignore the user interface is to miss out on much of the computers value.
Users need to see the approach we are taking is going to be successful. Committing to a losing cause is in no one's best interest. How their involvement in the quality of systems is clear. What is not clear is how an application of such scope and functionality can be approached and built. The performance of technology, its reliability and maturity are providing productivity gains that are surprising to everyone. I'm seeing a distinct move away from the Oracle and SAP style of application offering. The need for fast, innovative firms is being demanded throughout the world. This can only be provided by a software development capability dedicated to the innovative firms. Please join me here.
Technorati Tags:
People's Development User Capabilities Community