VMware And salesforce.com Join Forces To Push PaaS To Mainstream Adoption With vmforce
salesforce.com and VMware announced today the development of a joint product and service offering named vmforce. Forrester had a chance to talk to executives at both companies prior to the announcement, and I am quite impressed by the bold move of the two players. Most developers in corporate environments and ISVs perceive the two stacks as two totally different alternatives when selecting a software platform. While the VMware stack, with its Tomcat-based Spring framework, reached mainstream popularity among Java developers with its more lightweight standard Java approach, salesforce.com’s Force.com stack was mostly attractive to developers who liked to extend CRM packaged apps with individual business logic or to ISVs that created new applications from scratch. In some cases, the Java standard and the more proprietary APEX language at Force.com even appeared as competitive options.
Hi, I'd like to share part two of a recent discussion that I had with Martin Schindler, Editor of Silicon.de. See part one here in case you missed it.
Martin Schindler: You indicated earlier that interest in third-party maintenance has increased since SAP wanted to make its Enterprise Support basically mandatory. Is this just excitement or real demand?
Stefan Ried: Yes, interest has increased. We're also seeing that from the vendor side. In addition to Rimini Street, which already offers maintenance for SAP systems, there is also Aptech, netCustomer, the Spinnaker Management Group, and Versytec, which are today limited to PeopleSoft, JD Edwards, and Siebel. The vendor space has developed further, and the list of SAP-supporting vendors will soon become longer. Finally, it makes sense to ask the larger systems integrators, such as Wipro, Tata Consultancy Services, IBM Global Services, and Siemens (SIS), which are also the largest SAP integrators, to quote for offering SAP third-party maintenance.
Martin Schindler: This is interesting. We've read little about such offers.
Stefan Ried: These integrators naturally don't make a lot of noise about these things, as they also have a partner relationship with SAP, of course. At the end of the day, the demand will be balanced with the supply — and if more customers request SAP maintenance from their systems integrator, they will start to offer it.
Martin Schindler: Is this profitable for integrators?
I'd like to share a recent discussion that I had with Martin Schindler, Editor of Silicon.de
Martin Schindler: There are experts who talk of a non-existing market when it comes to SAP third party maintenance. Is that correct?
Stefan Ried: You could have the impression, especially for Germany, because companies remain very close to SAP and many have decided for a Single-Vendor-Strategy. But in other countries it is much less the case. However the price politics of SAP in the last year and now the slow innovation speed has raised the discussion of alternative maintenance model again.
Martin Schindler: Are there German users with real interest in obtaining maintenance for their SAP system through another company?
Stefan Ried: Yes, there is definitely interest.
We regularly make, and particularly in the last year, sample calculations for users (as well as for system integrators) if it is worth going for third-party maintenance. It depends on various factors, whether it is worth it.
Martin Schindler: What do these factors look like?
Stefan Ried: Companies must check, for example, how much "know-how" exists in-house. Third-party maintenance can work very well, if not everything from SAP-Maintenance is needed. This is for example the case, when parts of the SAP-System are regarded as frozen, small legal changes follow, or to repair a bug. With this technical problems, compatibility with operating system patches, performance problems within an established system can be addressed and the system can operate securely with very little change. So, third-party maintenance vendors can, especially for older SAP systems, work very well.