SAP Mobile - Quo Vadis?

Before we start, maybe some background music by Dire Straits? Guess Where Do You Think You're Going is quite applicable ;-)
I got a bit confused last week and I wanted to share my confusion with you and hope that my SAP mobile life gets demystified.

So, SAP Mobile - Quo Vadis?


SAP's three pillars 

Now we all know SAP's 3 main pillars:
  • Cloud
  • Mobile
  • HANA

Needless to say that SAP shares a lot of PowerPoint slides and stories around these topics at events like SAPphire NOW and SAP TechEd, at local events like SAP Forum, press conferences and here on SDN and other sites.
Last week SAP held a very important press conference, the announcement of #SAPonHANA. And to be honest - it made me feel a bit jealous. Great story telling, together with customers and partners SAP shows the added value of running SAP on HANA. There is plenty of training material to be found in the HANA academy, a developer license, contact persons, … bottom line: SAP is supporting you in adapting this new technology into your own business.
Now this blog is not about HANA, but about mobile. So why jealous? There is with a specificSAP mobile platform area and the possibility for developer licenses. (Do you still remember how long it took SAP to provide these developer licenses? OK, OK forget about that, as it is there yet. Stop whining.)

Why this blog? Let me try to explain as I got disappointed by SAP Product Management last week.

Do we need a strategy?

Enterprise Mobility is not about the app. It is about mobilizing your business process, bring enterprise functionality to the end user so that he or she can access it via a user friendly interface, at the right time, with the right information and on the device of choice.
SAP is doing a good job in explaining its mobile roadmap, as you definitely need a strategy to be successful in the mobile area. Mobile is the new desktop, tablets and smart phones will outnumber PC's quicker than we think. Roadmap presentations at SAP TechEd were clear. Talks by Ian Thain are very understandable and sharing a lot of enthusiasm (E.g. The state of the mobile union). It is clear that we need a platform for integration, synchronization and providing back end functionality to mobile devices. And when SAP buys the two market leaders in that area, Sybase and Syclo, that proves that you have a strategy.

Again, why this blog? Because the long (define long in the mobile world ;-) time strategy is clear, but what if we want to start with mobility tomorrow?

So here's the customer case

With my current customer I am trying to lay out the solution architecture to bring service management functionality to service engineers. In order for the service engineer to focus, it is important to have the right user experience, not only for service management functionality but for all relevant functionality. Unfortunately our case is not really a regular service management mobility use case as the engineers face security issues (you can’t always bring your own equipment), process issues (besides service management, custom functionality is to be available as well), connectivity issues (sometimes you have, sometimes not, but you still need to do your job), …


Our challenges

  • Is SAP Work Manager (the app formerly known as Syclo SMART work manager) sufficient for our service engineers?
  • Can we offer custom functionality via Syclo?
  • As the user experience is so important, is Sybase the preferred platform? But what about integrating SAP Work Manager?
  • Hey, SAP is integrating the two platforms into SAP Mobile Platform. What are the consequences?
  • Are there any references, in a comparable environment, and how are these questions answered?

Thanks to SAP NL we got an appointment with SAP Product Management in Walldorf. Or at least that's what we thought. We planned to visit SAP in Walldorf last Friday, but unfortunately our visit got cancelled two days before, as "Our road map for integrating the two platforms is not clear yet, please come visit us in about 4 weeks"... (speechless) ...

OK, I can understand that the road map might not be 100% crystal clear, then show us some disclaimers as we are already used to that. But please start supporting us in making the right decisions.

Do you understand my disappointment now?

SAP, what about executing your strategy?

Again the big picture is clear. But please SAP there are customers that can't wait for 2 different platforms to be integrated. Or wait for future companies and solutions that SAP might buy. We want to start today and need some expert advice from SAP to prevent to make decisions that we regret later. "If only we knew that 3 months ago …"

Please SAP, don't leave customers and partners in the mobile darkness. Mobile is one of your three pillars. If you have a strategy built on three pillars and one collapses, what would be the impact on the other two?


Just my 2 cents

Allow me to make some final remarks, tips if I may say so:

  • SAP don't try to sell technology or licenses. Show the added value, sell solutions to real life customer cases.
  • At DKOM I learned about the new SAP by Jim Hagemann Snabe. An SAP that collaborates with customers and partners. Unfortunately on the mobile area SAP is not showing this off. Be open and partner with customers and system integrators.
  • The customer case as I described in this blog is not by itself. There are multiple stories about SAP leaving customers in the dark in executing the mobile strategy.
  • We all understand that integrating two different platforms and repositioning is a difficult thing to do. But please SAP get out of the ivory tower. Listen to customer use cases and take them into account. Don't just sell apps, provide solutions!

Still with me? Recognizable? Please share your experiences and, hopefully, prove me wrong. If so, please connect me to your personal Yoda for "Answers you get".


Popular posts from this blog

Professional Scrum Master \o/

SAP TechEd Top 10 (2010)