SAP Mobility Challenge, Part 5

I have heard much discussion lately on the subject of mobile micro applications in the SAP ecosystem. These are described as light weight mobile applications that do simple things like:

• Expense reports
• Alerts
• Approvals
• BI reports
• Etc.

There are literally hundreds of these micro-apps possible. The challenge is how does a SAP customer manage them? Does the mobile user really want 17 different little SAP micro-apps on their smartphone?

I see these mobile micro-apps as short term innovations that will quickly consolidate into a mobile enterprise application platform (MEAP). The SAP user ultimately wants one icon on their mobile dashboard not 17. This icon launches a menu system that can include 17 menu options with mobilized business processes. More options can be added through an opt-in function.

The MEAP vendors will rapidly create micro-apps and then quickly consolidate them on to their platforms. The big challenge for MEAP vendors is how to quickly create good MEAPs and get enough market exposure and success to be sustainable in the long run. MEAPs should include:

• Rapid application development environments with excellent visual design tools for customizing and creating new mobile enterprise applications.
• Powerful integration tools for connecting and synchronizing with a variety of backend database applications and environments.
• Mobile user and mobile device management dashboards and tools for the IT help desk.
• Support for all the major operating systems and popular mobile devices.
• Integrated workflow engines that enable business processes and workflows to be extended out to mobile environments.

Let's think about the IT decision making process. Mobile workers may be using mobile micro-applications from 9 different mobile software vendors. There will be much overlap in features and functionality. The IT department will eventually start standardizing, consolidating and simplifying. It won't be long before the IT department starts requiring all mobile micro-applications to come from one or two MEAPs that have good frameworks and offer solid enterprise quality features.

MEAP vendors face a number of challenges:

1. Developing solid MEAPs quickly.
2. Getting SAP approval and partnerships in place.
3. Developing many mobile micro-applications to cover the simple and niche requirements and preventing other companies from gaining a mobility foothold within the SAP ecosystem.
4. Gaining thought leadership, mindshare, influence and brand recognition quickly within the SAP customer base.
5. Educating the market on the requirements for a true enterprise quality MEAP.
6. Pricing their solutions to gain market share quickly - this is a viral marketing event.
7. Defending against a strategy of mobile chaos within the enterprise.
8. Providing a roadmap and strategy for an orderly and quickly expanding enterprise mobility strategy.
9. Arguing that any developer can develop a mobile micro-application, but only the experts can develop an enterprise quality MEAP.

The current strategy for most MEAPs seems to be to mobilize a vertical SAP business process quickly and then expanding in all directions. That means the current SAP MEAP partners are and will be colliding. Let the sparks and fun begin!

The companies that I view as SAP oriented MEAP vendors that are currently listed as SAP partners are:

• Sybase
• Sky Technologies
• ClickSoftware
• Syclo

There are a number of additional companies like Pyxis Mobile and Vivido that are moving into this space and many systems integrators with their own emerging mobile micro-apps and MEAP strategies. It will come down to enterprise quality MEAPs, thought leadership and mindshare.

If you are interested in discussing these topics in more detail or scheduling one of my in-depth two day workshops on these subjects please contact me.

Related Articles:

• SAP Mobility Challenge, Part 1
• SAP Mobility Challenge, Part 2
• SAP Mobility Challenge, Part 3
• SAP Mobility Challenge, Part 4

***************************************************
Author Kevin Benedict
Mobility Consultant, Mobile Industry Analyst and Web 2.0 Marketing Expert

http://www.netcentric-strategies.com/
www.linkedin.com/in/kevinbenedict
twitter: http://twitter.com/krbenedict
http://kevinbenedict.ulitzer.com/
http://mobileenterprisestrategies.blogspot.com/

***Full Disclosure: I am an independent mobility consultant and Web 2.0 marketing expert and as such I work with, and have worked with, many of the companies mentioned in my articles.
**************************************************

Mobile Enterprise Application Platforms, SAP and Marketing

Yesterday I was reading Gartner's Magic Quadrant for Mobile Enterprise Application Platforms. It was interesting to me that one of the points Gartner considers before including a MEAP vendor in their report is marketing. They consider the following:

1. Success at marketing (I am guessing it is measured by sales?)
2. Market awareness (name recognition within a target market)
3. Marketing strategy (if Gartner is convinced you have a good strategy)
4. Your ability to recruit a good partner ecosystem and support it through marketing

Think about it. You invest millions of dollars and tens of thousands of man/woman hours into your products, middleware, synchronization technologies, SAP integration methodologies, databases, device management dashboards, rapid application development environments and multi-channel support for dozens of mobile devices, but that is not enough. Gartner is going to evaluate your marketing before including you in their report.

Gartner understands what many smart engineers have not yet learned. A better mouse trap does not sell itself or pay the expenses - sales do. Unless a comprehensive marketing plan is designed, developed and successfully implemented you will not gain sufficient mind share and market share quick enough to remain viable in this fast changing market.

It almost seems like SAP is holding a marketing Olympics for their mobility partners. They have chosen to partner with a handful of companies like Sky Technologies, Syclo, Sybase, RIM and ClickSoftware. Many of these companies have overlapping mobility solutions, but SAP seems to want to invite their partners to compete on the marketing field and see which one comes out on top.

I enjoy a good game of strategy. Although, I can feel the pain that passionate software engineers must feel. They have dedicated their life to developing a progammer's MEAP masterpiece, but the winner is determined by the folks in the marketing department with the expense accounts and travel budgets.


***************************************************
Author Kevin Benedict
Mobility Consultant, Wireless Industry Analyst and Web 2.0 Marketing Expert

http://www.netcentric-strategies.com/
www.linkedin.com/in/kevinbenedict
twitter: http://twitter.com/krbenedict
http://kevinbenedict.ulitzer.com/
http://mobileenterprisestrategies.blogspot.com/

***Full Disclosure: I am a mobility consultant and Web 2.0 marketing expert and as such I work with, and have worked with, some of the companies mentioned in my articles.
**************************************************

Advice for Mobile Start-Ups: Working with SAP, Part 2

There are several different categories of mobile applications that work with or integrate with SAP.

1. Those that provide real-time mobile views of complete SAP applications
2. Those that provide mobile queries and reports on SAP data
3. Those that provide custom mobile forms for subsets of SAP business processes based upon roles and responsibilities
4. Complete, disconnected mobile applications (like work orders) that synchronize with a field force automation solution (e.g. Sky Technologies, Sybase, Syclo, ClickSoftware, etc) on the backend where it is integrated with SAP
5. Custom mobile applications for inspections, assessments, plant maintenance and other niche requirements that may be synchronized with custom databases that are integrated with SAP databases.

It is important to understand which category or categories your solutions fit, and how this impacts your ability to leverage the SAP sales and marketing organizations to help grow your business.

The different categories of mobile solutions and architectures listed above often have different users. A field service technician needs a connected/disconnected mobile application, while the administrator may simply need mobile access to the SAP ERP. You must recognize who your user is before you start marketing. What department's budget will pay for a white collar worker's mobile access? Who are the decision makers? What are their priorities? Is it saving money, making money or doing more with less?

Can you think of other mobile application categories that I missed?

Read Advice to Mobile Start-Ups: Working with SAP, Part 1 here, Part 3 here and Part 4.

***********************************************
Author Kevin Benedict
Independent Mobility Consultant, Wireless Industry Analyst and Marketing Consultant
www.linkedin.com/in/kevinbenedict
twitter: @krbenedict
http://kevinbenedict.ulitzer.com/
http://mobileenterprisestrategies.blogspot.com/
***********************************************