Driven by PeopleSft Motivated by MicroSft
This post of mine is to motivate myself to build the ERP which will change the Face of the existing ERP's. I've just started visualizing how an ERP should be designed in the future, before I start describing how MY ERP will be, I'll give you the reasons which led me to this road;)
I started my career as a PeopleSft Consultant. Looking at this product I thought nothing better can ever be built. Amazing!!! finally it is "I" who came up with this idea to revolutionize ERP's future. I would like to accept that this Idea of mine is totally motivated by Microsft.
I start my story here, Windows is a product which removes the requirement of spending time to understand the USE of it from the end user perspective. I want to use Windows for a specific application, say I wanna watch a movie using Windows. They provide me with the Windows Media Player. I being the end user who is not satisfied with the performance of Media Player can download similiar applications which will suit my requirement and simplify my process. This application although obtained from a third party is not very difficult to Install into the product (Windows). Will YOU be interseted to INSTALL this application ( say Real Player or QuickTime ), if you had to hire a third party CONSULTANT and ask him to Customize your existing Windows Application?
I think you can see where I'm getting to: ERP's in the future should allow third parties to provide the Business Logics which a customer will require. These Business Logics should be available to the Customer as Modules which can be installed directly to his production environment. This will remove the requirement for the customer to apply customizations to the product which he purchases. Now he'll be buying from other third parties which you think would increase the cost for the customer. But with the increase in the number of third party vendors the cost of each module will definitely COME DOWN. The ERP companies can themselves test and certify each of these third party modules. This certifying process will give a lot of comfort to the customer.
In summary I would like to see an ERP that can be bought for 2000$, but will still have all the Gloss of PeopleSft. The ERP should work on all databases starting from MYSQL to ORCL this would allow users of any scale to use it.
The previous products that I've built are for the use of PeoplSft consultants. They can be downloaded from the links given below.
This product is called a Customization Analyzer, which will give you the results of Peoplesoft Compares. This is just a demo version which will only give you a report for Records, Fields, Record Fields.
Sorry I've temporarily removed the links
The following product has been named as Reapply Customizations. This is too a demo version which can be used only for record fields. As the documentation will not be provided for these demo versions use the Tool Tip Text.
Sorry I've temporarily removed the links
I would appreciate your valuable comments. If you wish to purchase the above listed products you can mail me at: nextrevolutioninerp@yahoo.com.
The products come with support.
2 comments:
If I understand you correctly, you are suggesting building a framework that then third parties could build applications on. For this, I would assume that you would need to define the data dictionary (so that everybody is speaking the same language) and some common services (workflow, communication, etc) so that you don't have a bunch of fragmented approaches. It sounds a lot like what Oracle is planning on doing with Fusion. They are defining a common data structure and then tying it all together with standard protocals. Your application becomes a series of web services tied together with BPEL. In therory, anybody could create new services and or BPEL processes (all open standards). If you want to support all databases (as mentioned), you will end up in the same predicament as PS. I have always thought that the biggest weakness to PeopleSoft is that they try to be everything to everybody. Supporting multiple databases means that you have to 'dumb it down' to the least common denominator. Sure, ORACLE is a very powerful and scalable database, but that doesn't do a lot of good when PS only uses unique constraints (no PL/SQL, no hints, no more advance indexing). If Oracle was smart, they would support only Oracle (although that would piss off many customers). My guess is that they will eventually announce support for Oracle and DB2... no way I can see them supporting SQL Server in the future.
Anonymous, you r right with the fact that this is what ORACLE is planning to do currently. But the other fact is that I've been thinking about this, even before ORACLEs roadmap for FUSION. May be you were thinking that I can only COPY ideas, but as a matter of fact I read the SOA (Service Oriented Architechture), from Customer Connection only recently. Moving to the Database side of it, my target are only small and mid-sized companies to start with. They will not be able to invest millions of dollars in implementation or infrastructure procurement. Hence it is very essential that I cater to the needs of the overall market requirement. My customer should be able to afford a product when he needs it. I should not put constraints on him for his infrastructure. He should be able to install the application on top of MYSQL(this is the only free database name that I know, I heard that they ve been closed, but I'm not sure.). I'm targetting the millions of small sized businesses which could be a Bookstall for example, they must be having a product already installed, hence their movement to MY ERP should be seemless. Moving to the next aspect os it, Am I going to provide only a framework? NO, certainly not, cause then I cannot call it an ERP (it is just an application). An application becomes an ERP only when my product is stable over the industry that I wish to cover. But remember that I'm still going to provide a framework, this is to facilitate the other capable industry experts to build modules out of my framework and install it in my product. They should also be able to sell their modules, I'm actually making an entrepreneur out of a nobody. But as stated in the BLOG I'll continue to make money by certifying these third party Modules.
Post a Comment