Skip to Content
Author's profile photo Jim Spath

ASUG 2012 Day Zero, Mobile pre-con: baked, shipped, committed.

[ Sun | Mon | Tue | Wed ]

An early start to the day helped ensure that the facilities were functional and that support was available for this pre-conference day on SAP Mobile.  After literally months of preparation, it was time for the speakers and the audience to assemble.

Rather than the usual chronological tour through the day, I’ll leave that for the stories in pictures below and focus on some themes that resounded during the day. There were others, and Jon Reed captured one of the themes during his tweets, as well as other crowd reaction.


Repeatedly, customers wanted to know which moving parts are required, which are optional, and what of the existing built-out systems go into maintenance mode. This is especially critical to understand for parts that are new, may require new licenses, and for which little or no institutional knowledge exists. We saw several charts, including full spectrum business models, medium intensity connection diagrams, and something resembling entity relationship models. Based on what we’ve heard, we’ll expect to see refinements of these road maps later in the week.

Customer requirements

Early in the day, I asked for what customers were looking for in the sessions today. One specific issue stuck out, that might be beyond the typical developer focus in connecting back end data systems to mobile devices, and that’s calendar synchronization. That to me is one of those universal issues that mobile software should solve (get the times of meetings right), but whether that’s in SAP’s power, I don’t know. The question was not addressed later, nor did the pruning of contacts come up. Another related issue was governance – once a data model is built for who gets what data on their mobile device, who enforces or controls this?

That Mobile Guy

When I talked about the diversity of mobile devices, and the dearth of mobile infrastructure support, there was a common agreement in the audience that they recognize the same issue. Everyone wants the mobile devices to work, but few seem capable of bridging the gap between the business development requirements and the software development cycles required. Making Afaria work, managing the procurement, build-out, and demolition of devices seems left to a specialize cadre that is in short supply.

Event / Transportation Management

This trend may not have been universally absorbed by the audience, as the speaker spent a lot of time on general software trends, and not enough time on how mobile devices can track shipments, interface with existing carriers, and streamline logistics. The observation that trucking companies have more Androids than iPhones may be valid, but it wasn’t supported by any evidence presented. The example we saw, while a mock up perhaps, added new dimensions to the expansion of applications in this area. Reliance on the existence of an SAP backbone with transportation management seemed to be a prerequisite, and I’d have liked to have heard more specific examples. I’ll try to get this topic into an ASUG webcast soon.


It may not be fair to ask a technical presenter what the licensing terms of a specific software suite are, but the question came up multiple times. I would expect SAP to have some kind of standard price sheet, and at least let these people know what comes in a bundle and what doesn’t. My sense is that this is immediately directed to account representatives, and discerning all of the moving parts needed for a project (see Infrastructure, above) are going to be left for those closed door discussions.


As this “deal” as not closed, I did not expect to see or hear much about the impact. And while the presenters stayed away from revealing any confidential information, there was good discussion about possible scenarios, timing, and what may happen. And saying “names may change” seems obvious, but a welcome recognition of the rebranding (or spin) that happens post-merger.

Development style, and skill building

Jon Reed asked vital questions about what new skills or changes to current development management might be required as a result of shifting into an SUP landscape. The answers were valuable, but to me the more critical insight was into the data modeling process. Trimming the fat of an ERP system prior to caching and then distributing it to mobile devices seems like an obvious step, but the sense was this didn’t happen nearly as often as it should. And the skills of knowing the entire data catalog, understanding what needs to go, what needs to stay, and what needs to be filtered, is not easily acquired, nor,  I think, is it as well rewarded as it should be.

2012-05-13 09.06.05.jpg

Session 1 – John Polus

2012-05-13 11.25.08.jpg

Session 2 – Cam Patters

2012-05-13 12.20.01.jpg


2012-05-13 12.20.25.jpg

Another side of lunch

2012-05-13 13.55.35.jpg

Session 3 – Boris Magocsi

2012-05-13 14.11.48.jpg

Session 4


Transcription of portions of the above tweet stream – thanks Jon Reed for distilling some of the customer angst in the room.

1st time I’ve heard an SAP employee say publicly they don’t develop apps for RIM – only Android and iPhone #asug #sapphirenow
customer mobility questions rapidly moved into stew of SUP, Gateway, DOE, Syclo, MBOs, Odata – SAP has lots to simplify #asug #sapphirenow
RT @qmacro @jonerp wondering if “indirect access” phrase trumps all mobility stew keywords. #asug #sapphirenow #licensing -> big issue
@MartijnLinssen debate for another day maybe when I’m less distracted – but in this case I’d argue the complications deter investment
@MartijnLinssen SAP customer side, they want more clarity on tools/dev options etc.
[@Gurush_] @jonerp absolutely Sir.CRM mobility with DOE makes one go through more hoops to set up environment than on the ERP/ECC side.
SAP CRM mobile talk -“No, that’s not NetWeaver Gateway, that’s the Gateway within the NetWeaver Mobile DOE product” #sigh #sapphirenow

2012-05-13 14.39.18.jpg

Session 5 – Scott Steadman and Harleen Kaur

2012-05-13 15.55.45.jpg

Session 6 – Karsten Ruf and Viswanathan Ramakrishnan


Success, of a kind. Got one Mobile demo working on my iPad.  Boris said use itunes, not SAP store. Confused.

Bonus track

Mentor Birthday

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member

      Jim - thanks for this summary.  I heard great things about your pre-conf and mentioned it in my blog - Let me know if there's more I can read/share on this topic.  Great job!

      Author's profile photo Jon Reed
      Jon Reed

      Jim - thanks to you and ASUG for getting me into the mobility pre-con, I was able to attend about half of it. I always try to get in early to Sapphire/ASUG to attend these, for a couple reasons: 1. only chance to "deep dive" during a hectic week, and 2. get a real cut check from customers about the issues that they are facing. It's often different than what we hear from the main keynote stages.

      I thought you and your speakers did a terrific job on this session and I was able to fill in a lot of gaps. I got some pushback from SAP on the tweets I put out, and some of that pushback should be briefly addressed here. As you pointed out what I was trying to do was mirror/relay some of the customer confusion or "angst" around some of the fuzziness and complexity in SAP's mobility landscapes. Some at SAP didn't like that and seemed to think that the questions were mine. That's a "shoot the messenger" thing and the reality is that customers had questions and some of the answers raised more questions.

      However, SAP and RIM were right to push back on the tweet about forward development on RIM. That one's on me - though many in the room took his comment to mean SAP was not doing any forward mobile application development on RIM, only on Android and iOS, what I learned later was that such decisions are typically left to individual product teams, so I don't believe SAP has halted RIM mobile app development across the board.

      Having said that, the broader theme that RIM has its work cut out for them to remain relevant from an apps perspective is one that I think remains valid. To RIM's credit, I hear good things about what RIM is doing to engage developers, but it's not surprising to hear about RIM development being scaled back whether it's from SAP or elsewhere. But to be fair my tweet was misleading and I misunderstood the speaker on that point, who also could have been clearer.

      To SAP's credit, they reached out to me on these points beyond Twitter and there were some good conversations. Credit to Sanjay Poonen and Nick Brown for quickly responding and showing their passion for resolving this kind of confusion both in my reporting and more importantly for customers. We all know mobility is a moving target so this kind of diligence is clearly welcome and needed. I have suggested to RIM that they collaborate on a blog post with SAP to more clearly lay out the mobile app development strategy for RIM and SAP, that would be a positive to come out of this exchange.

      Author's profile photo Pushkar Ranjan
      Pushkar Ranjan

      Very progressive engagement all around. Love it. Thank you.