and here's why...
It's too much of a cult thing. I've worked at dozens of implementation sites (Oracle, SAP and others). When you implement SAP it is all about fitting your business in to SAP, not making SAP work for your business. Don't jump all over me because it is an honest comment. I've nothing against SAP, and it is not too complex, simply badly communicated and too rigidly designed. they need to do something pronto because in a recessionary economy I don't think anyone would touch a major SAP implementation.
Good luck to all.
Your post confirms my point. The arrogance of those working in this industry knows no bounds. It is nothing against you personally. That is simply the culture of the software industry. "We know what is best for your industry, by God, and if you don't believe it, you are an idiot." This mindset is commonplace.
If a software company can truly focus on customization to meet the needs of a specific customer or even an industry and not be so content on the take it or leave it, one size fits all cookie cutter approach, they will truly rule the world. Someone will do it does it hurt. Not a matter of if. A matter of when.
<One of these days a software company will figure out they must meet the needs of their customer...>
Balls - I think you are just the man for the job. Let me give you some advice on how to get started:
1) The first thing you need to do is determine all of the needs of the 'customers'. I suggest doing this on an industry-by-industry basis. You'll need to identify all of the the different business processes that occur within each industry, and since no single customer should ever have to change the way they are doing things (even if they are doing them completely wrong) you'll need to identify all of the nuances within each process. You'll also need to identify all of the country-specific and legal requirements so that software solution does not land one of your customers in jail (and you in court)
2) Now that you know what the customer wants in every possible scenario, you'll need to design a software system that ties all of this together. Make sure that you use only the latest technology with the understanding that this technology will change every couple of years
3) No time for rest yet, Balls. Now that you've got your awesome software package that meets the needs of every company, you need to continuously validate your solution against the ever-changing market and changes in tax laws. Your software must be in a constant state of upgrade, otherwise you will have big-mouthed jerks on the internet calling your software archaic and outdated.
Of course, you'll still need to find customers who are willing to buy, and people who know how to implement. But your sofware will sell itself and implement at the push of a button, right Balls. Because it's all so easy - almost as easy as sitting back and making generic statements about an industry you obviously don't understand.
This is your calling, Balls. Time for you to rule the world.
The product you represent and that I'm sure that is your livelihood is archaic and outdated. Companies must completely change their business practices, including the ones that are highly successful, to conform to SAP. One of these days a software company will figure out they must meet the needs of their customer. The company that does will rule the world. And I188188, SAP is not that company. You might as well be selling Edsels. SAP is old, outdated technology. You can hype it and pump it up all you want, but it is what it is.
You might be correct about the rigid software design (3 decimaal places???) but we just had a smooth go-live along with our first phase smooth go-live a year ago, and we were LOOKING for the discipline that SAP forces into a business. SAP is not so much "ERP software" as it is a development environment these days. And I personally know of many large SAP projects that are in the middle or just beginning. I am jumping in today.
I think you need to take this on an industry by industry basis. Some industries are addressed by SAP solutions more so than others.
It's also a safe bet that many companies have business processes that are decades old that should redesigned rather than simply replicated in newer enabling technologies, be it SAP, Oracle or others. I've been on many implementations where the customer has some round-about way of doing things because that's how it has always been done. The companies that tend to have the most successful implementations are the ones that are flexible when it comes to process change. This involves more change management, but ultimately it's worth it.
Would love to hear other views on this topic.
I agree, I had developed software for our place that was in some cases 20 years old, and we consciously were looking to throw out the old manual methods that I duplicated in software and have SAP "force" us into more streamlined processes. And that is exactly what happened. I will say that during our selection process, we did not pick SAP so much as we picked the implementation company that helped us install... any major ERP software could do the things we needed.
Hello Old Buddy,
"SAP Solutions". Those two words together still give me a chuckle. And for the record, it is SAP that is old and antiquated and needs to be updated. They bring nothing new from a technology standpoint to the table.
Your post pretty much confirms the original posters comments. You basically said that in many implementations that the customers way of doing things is wrong and SAP is right. And companies that are "flexible" and will to conform their businesses to SAP are the ones that are successful. Once again, it is the extreme arrogance in this way of thinking that will ultimately lead to SAP's demise.
One of these ERP outfits will one day create a system that conforms to the customer's business, is user friendly, and streamlines tasks and saves time of the individuals using it. The first one to figure this out will rule the world.