Kevin Benedict Ponders the Future

SAP Mobility Challenge, Part 3

Systems Integrators represent a significant sales channel for SAP. Systems Integrators often have resources assigned to various SAP upgrades, integrations, customization and development projects onsite at a SAP customer's location. Often it is the systems integrators who first hear of upcoming sales opportunities and business requirements. SIs are very interested in SAP enterprise mobility (there is even a new Linkedin Group called SAP Enterprise Mobility) as it is seen as a major growth area. Here in lies the challenge.

Since as was discussed in Part 2 of this series, different groups within SAP are providing different mobile solution recommendations, the SI is going to be frustrated. They want to know specifically what mobile solution is recommended and where they can offer value by implementing it. The SI is not going to train on all possible SAP mobility solutions. They want to get trained on a mobile solution that has the maximum reusability across as many different SAP customers and business processes as possible to keep their costs as low as possible. They will not want to learn one mobile solution for EAM (enterprise asset management), another for workforce optimization and another for mobile CRM, etc.

Systems Integrators will want a MEAP (mobile enterprise application platform) that they can use broadly to design, develop, deploy and support mobile extensions to existing SAP business processes. In addition, once you start supporting field operations outside the four walls of the enterprise it is common that companies have unique business processes in place. Often these processes, methodologies and techniques provide competitive advantages. If the SAP customer wants to continue these practices then a customized mobile software application for field operations will be necessary. This necessitates a MEAP that can be used by the SI to develop powerful customized mobile applications.

Another challenge is that some of the mobile solutions recommended by various groups in SAP are focused on mobilizing the vendor's specific business applications and supported business processes, not necessarily SAP. You may have an architecture like the following, SAP=>Vertical Application=>Mobile Solution. This may be effective for the vertical application vendor, but does not help the system integrator that wants a MEAP that can be used widely across the entire SAP environment where there are a multitude of business processes and customization requirements.

***************************************************

Author Kevin Benedict

Mobility Consultant, Wireless Industry Analyst and Web 2.0 Marketing Expert

http://www.netcentric-strategies.com/

www.linkedin.com/in/kevinbenedict

http://twitter.com/krbenedict

***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.

**************************************************

New SAP Enterprise Mobility Group on Linkedin

For those of you active on Linkedin, there is a new group available called SAP Enterprise Mobility for professionals involved in SAP and SAP mobility projects. Here is the description:

This group is dedicated to the discussion of enterprise mobile applications in SAP environments and networking with other professionals engaged in SAP mobility strategy.

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

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.
**************************************************

SAP Mobility Challenge, Part 2

This article continues the discussion started in SAP Mobility Challenge, Part 1.

In the following excerpts from press releases issued by SAP's partners you can see that SAP understands and appreciates the significance of mobile applications in field service management. How does that appreciation translate into recommendations for SAP customers?

First let's look at an excerpt from a press release issued by SAP/ClickSoftware and a quote from the SAP Solution Management group. "There is growing demand in the market for more comprehensive field service management that incorporates decision support and optimization," said Tobias Dosch, senior vice president, Suite Solution Management, SAP AG. "Our relationship with ClickSoftware is a prime example of how SAP meets specific customer needs by leveraging our partner ecosystem to complement and extend SAP solution offerings."

SAP will resell ClickSoftware's ServiceOptimization Suite as the SAP® Workforce Scheduling and Optimization application by ClickSoftware, helping customers meet the challenge of optimizing the mobile service workforce. SAP Workforce Scheduling and Optimization helps customers to automate real-time proactive and reactive decision-making. Having the ability to act in real time on data from the field and produce optimal decisions for resource allocation and job scheduling can help SAP and ClickSoftware customers obtain the benefits of implementing a comprehensive service optimization solution.

Second, let's look at an excerpt from a press release issued by Syclo. "Syclo…announced an agreement centered around co-innovation with SAP AG to deliver mobile applications that enable maintenance and service technicians access to SAP® Business Suite software from a broad range of devices regardless of connectivity. They are designed for work order execution, operator rounds, time/attendance tracking and materials management.

"The cooperation with Syclo enables our customers to increase the productivity of maintenance and field service technicians by connecting them to SAP Business Suite for work order or service order execution, operator rounds and materials management," said Dieter Hässlein, vice president, Solution Management for EAM, Sustainability and Mobile.

Thirdly, let's consider the SAP/Sybase announcements.

In March 2009, Sybase and SAP announced a strategic Co-Innovation Partnership to extend SAP to mobile workers on a wide array of mobile devices… "Our customers demand mobile access to proven business applications to stay connected to their customers, suppliers, partners and employees to drive innovation and productivity," said Bill McDermott, president, Global Field Operations, and member of the SAP executive board SAP AG. "SAP is committed to helping customers adapt to business change and optimize the value derived from our leading solutions and extensive partner ecosystem. Working together with Sybase, we will provide the modern mobile workforce with the tools they need on the device of their choice, which will enable faster time to value, through access to business functionality anytime, anywhere."

The three press release excerpts above show that three different SAP groups (SAP Suite Solution Management, Global Field Operation and SAP Solution Management for EAM, Sustainability and Mobile) are recommending three different mobile solutions for the mobile workforce. I can tell you from experience that many mobile business processes such as field services management are very similar across industries. The challenge here is which application does the SAP field sales team recommend to SAP customers? Should SAP customers buy different mobile solutions and different mobile clients for Asset Management, CRM and field services operations?

Last week I received a SAP EcoHub announcement of a webinar called, Defining Your Mobile Strategy. In it, SAP's Certified Partner Sky Technologies discussed the value of using one MEAP (mobile enterprise application platform) to organize and manage all mobile business processes from within an SAP environment. Here is yet a fourth mobility alternative promoted from within SAP's partner website.

I am still pondering the question I asked in Part 1 of this series - from a mobile technology and IT management perspective, does it make more sense for SAP to have one MEAP (mobile enterprise application platform) that best integrates and supports SAP's underlying architecture and product roadmap, rather than recommending the mobile applications from multiple partners? Can you image the challenges you would face if you were the IT manager of an SAP customer responsible for dozens of different mobile applications, using different mobile middleware, different security methodologies, different application development environments, etc., for each business process? Yikes!!

I would like to hear your thoughts and comments.

SAP’s Mobility Challenge, Part 1

I am very interested in watching SAP's emerging mobility strategy as it matures, evolves and morphs yet again. I am not critical; this is how all of mobility is these days. Four years ago we were all using the term Palm, Pocket PC and PDA. Now we are speaking of iPhone, Android, RIM and iPads. Within these different technologies are literally hundreds of different mobile applications and mobile extensions that can add value to SAP's ecosystem. I have been seeing a lot of activity in this space. I have seen SAP partnership announcements with RIM (Blackberry folks), Sybase, Sky Technologies, Syclo and ClickSoftware. I have seen SAP comments from many different industry and solution groups within SAP related to mobility.

What I believe is particularly challenging to SAP is trying to determine if mobility is an extension of an industry business process, or an integrated technology platform. Let me provide three examples of the challenge – work order management is both a back office solution and a mobile client (work orders are dispatched to mobile handheld computers in the field that are carried by the service technicians). Likewise, asset management involves both back office solutions and a mobile client (inspectors, facilities managers, plant maintenance teams and service technicians use mobile clients). Route/Sales management also involves back office solutions and mobile clients (route sales people track sales, inventory, delivery and promotions on mobile devices). So are the mobile applications/clients part of the work order management, asset management or route management categories or do they justify an integrated SAP mobility platform? What do you think?

I image this is a very complex and difficult discussion within SAP. SAP has selected specific partnerships within different industry verticals. These partners are often producing their own mobile applications to extend the capabilities of their solutions; however, these mobile solutions may in fact not align with SAP's overall mobile platform strategy.

From a purely technology perspective, it may make more sense for SAP to develop or select a MEAP (mobile enterprise application platform) that best integrates and supports SAP's underlying architecture and product roadmap, however, their vertical industry partners would not like this strategy at all as they see mobility as a major growth area for them. Very interesting times indeed!

Read SAP's Mobility Challenge, Part 2 here.

Advice for Mobile Start-ups: Working with SAP, Part 5

Part 4 of this series may have demoralized some mobile start-ups hoping to work closely with SAP, but Part 5 in this series provides solutions to many of the challenges identified in Part 4. Let's now take a closer look at some of the comments I made in Part 4.

The SAP customer is simplifying their IT infrastructure to reduce complexity and no non-SAP technology will be added unless it is approved by 17 business and IT committees. Who has the time to fight this battle?

Embed your solution in SAP so it becomes a part of SAP and avoids these issues (Sky Technologies, a Certified SAP Partner embeds their mobile solutions in SAP)
Simply provide a mobile application or iPhone view of SAP's current applications (Mobile micro-apps)

The IT Managers only want to learn mobile technology that will add to their resume and help them get their next assignment. The cool mobile technology that they just witnessed does not have its own category on the IT recruiters' websites. They want NAME power on their resume.

Show IT managers how to extend their current SAP infrastructure and code to mobile applications. This will accomplish their purposes.
Show IT managers that your solution is from a Certified SAP Partner

The SAP system integrator does not support the mobile technology, so recommends some other mobile solution that they support and have trained experts on.

Go directly to the end user with your message and evangelize and educate them. Build support internally for the "best" mobile technology. Close the deal first, then motivate the system integrator to be trained on your mobile technology and play a role in the implementation.

The SAP sales team does not get quota credit on it, but they do on another mobile solution. If the sales person does not make their numbers they are fired, so they do not care which mobile technology is better if it does not help keep their job.

Find a way for your mobile technology to sell more SAP licenses and products. Perhaps the mobile workforce that is not currently using SAP licenses will need them if they are connected via mobile devices. This would encourage the SAP sales force to work with you to sell more SAP licenses. Think in terms of the SAP AE's interests as well as the customers.

SAP's Industry Principals and Solutions Managers also must be very selective as to the mobile technology they recommend. They would not want to recommend a product that was not on the SAP price list or Certified Partner list, unless there was no other viable choice or this product helped sell other SAP licenses that benefited the SAP sales team.

SAP has only identified a few mobile categories for partnerships; field service automation, route/delivery and mobile CRM. I can tell you from personal experience that hundreds of mobile applications are needed in most large enterprises. Mobile applications that deal with security, asset management, inspections, compliance, job estimating, fleet management, engineering, construction, logistics, etc. There are massive opportunities to mobilize these business processes.
Show the SAP user and the SAP sales team how you can help them.

SAP customers are often on 5 year plans. These plans include upgrades, roll-outs, add-ons, customization, old product sun setting, mergers and acquisitions, etc. What does this mean to the mobile entrepreneur? It means your product needs a 5 year road map that aligns with SAP and the SAP customer's. If it does not, you are unlikely to survive the first round.

Be the thought leader and explain where mobility is going to be in 5 years. Tell them why your solution is better aligned with the direction of mobility than any.

The biggest project and highest priority in the company is around route delivery improvement, and your project is mobile SAP CRM. The route delivery mobility vendor agrees to extend their mobile solution into mobile CRM and since it is a higher priority, you lose.

Understand the decision making process, organizational chart and budget limits within IT and the department you are targeting. Can you keep the project cost below the threshold that requires additional management approvals? Can you break down your project so that yearly costs keep it below the approval thresholds so you can simply focus on this one department until it is firmly established?

The CIO will never get invited to speak in front of thousands at Sapphire if they choose your solution. Your user conferences could be held at Denny's.

Become a Certified SAP partner and attend Sapphire yourself. Be a mobile solution provider in a different category than other larger mobility vendors. Be the mobile application provider for; food processors, engineers, bridge inspections, healthcare, quality assurance, sustainability, etc., and then expand your mobile offerings. That is exactly what all the other mobile partners of SAP are doing.

If you would like to discuss these strategies and/or my consulting practice please contact me.

____________________________

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

http://www.netcentric-strategies.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.

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

SAP can be like a giant aircraft carrier moving powerfully across the ocean. It is huge and heavy and if you are a swimmer in the ocean trying to make it change directions to suite your purposes, good luck. A more successful approach is to understand the direction the ship is going and jump on board. Sign on, offer them a hand and help them get there. Perhaps as you gain their confidence they will let you into the wheelhouse where you can learn about their intended strategies and influence future directions.

Mobile software companies and their entrepreneurs often feel their mobile technology and strategy is better than all others. They often feel driven by a messianic mission to carry their mobile technology message to the world, and then scream in frustration when others don't seem to "get it." I understand. I have screamed.

Mobility entrepreneurs are often focused on their specific mobile technology. Many have engineering backgrounds and believe they have solved a significant problem. The challenge they often face is not understanding the business of their potential partners, resellers and target customers. Let me provide the following scenario to demonstrate my point:

There is a large conference room with a long table. There are 2 mobility entrepreneurs, 12 IT managers for a large SAP customer, 4 sales and pre-sales folks from SAP, and 3 representatives from a large system integrator with a focused SAP practice in attendance. The mobility entrepreneurs stand up and present the "world's best" enterprise mobility technology to the attendees. When they are done presenting, lots of questions are asked; the entrepreneurs cover them all and leave to catch their flight home expecting a PO on the fax machine when they arrive. The PO never arrives. Why?

Here are some possible reasons:

The SAP customer has a $14 million problem, and the mobile technology presented will solve only $675,000 of that problem. They need a complete solution, not a partial.

The $14 million problem requires a full range of systems integration, business process design and SAP customization to fix. They want to fix this problem with one overall integrated solution, not many small solutions linked together. Complexity can kill.

The SAP customer has three preferred SAP systems integrators – none have a practice around this particular mobile technology.

The SAP customer is simplifying their IT infrastructure to reduce complexity and no non-SAP technology will be added unless it is approved by 17 business and IT committees. Who has the time to fight this battle?

The IT Managers only want to learn mobile technology that will add to their resume and help them get their next assignment. The cool mobile technology that they just witnessed does not have its own category on the IT recruiters' websites. They want NAME power on their resume.

The SAP system integrator does not support the mobile technology, so recommends some other mobile solution that they support and have trained experts on.

The SAP sales team does not get quota credit on it, but they do on another mobile solution. If the sales person does not make their numbers they are fired, so they do not care which mobile technology is better if it does not help keep their job.

SAP's Industry Principals and Solutions Managers also must be very selective as to the mobile technology they recommend. They would not want to recommend a product that was not on the SAP price list or Certified Partner list, unless there was no other viable choice or this product helped sell other SAP licenses that benefited the SAP sales team. Their priorities would be:
1. SAP solution
2. SAP price list solution (could be a partner's solution on the price list)
3. SAP Certified or Innovation Partner
4. Only in desperate times would a non-partner be recommended and then only if it helped sell more SAP products

SAP pre-sales teams learn about many different technologies, but if it does not help their Account Executive make his/her quarterly numbers, it is unlikely to be introduced to the customer. However, there is an exception; if the solution, combined with an SAP solution helps close more revenue for the SAP Account Executive, then you have a winner.

SAP customers are often on 5 year plans. These plans include upgrades, roll-outs, add-ons, customization, old product sun setting, mergers and acquisitions, etc. What does this mean to the mobile entrepreneur? It means your product needs a 5 year road map that aligns with SAP and the SAP customer's. If it does not, you are unlikely to survive the first round.

Large software companies like SAP often consider potential partners as possible acquisition targets. Issues like are you private or public, customer base size, intellectual property ownership, market presence, etc, play into these considerations. If two partners have similar technologies, the one that is a better future acquisition target may be chosen for strategic reasons.
The SAP customer may have outsourced their IT to a large service provider with their own recommended mobile solution.
The SAP customer may have a large server deal with IBM, and IBM agrees to throw in a software solution for free if the annual support contracts are renewed...it happened to me :-(
The biggest project and highest priority in the company is around route delivery improvement, and your project is mobile SAP CRM. The route delivery mobility vendor agrees to extend their mobile solution into mobile CRM and since it is a higher priority, you lose.
The CIO will never get invited to speak in front of thousands at Sapphire if they choose your solution.
Your user conferences could be held at Denny's.

In summary, a mobile solution needs to be viewed favorably by the SAP customer, SAP sales team and the SAP system integrator. Not always all of them, but most of them. It needs to align with most of their strategic visions, personal interests and compensation structures. The frustrating part of this list for many mobility entrepreneurs is that none of it has to do with "best" mobile technology. These are primarily business issues that relate to alliances, partnerships, self-interests, marketing, strategic directions and business models.

Since we live in the real world, not all of the players' motivations will be clear or have the same level of priority. Sometimes new technologies appear that do not fit these molds, but once you understand these underlying motivations it becomes more clear.

If you are interested in discussing these issues in more detail and/or learning more about my consulting practice please contact me.

Watch for Part 5 in this series - it gives hope back to the Mobile Start-Ups. You can follow-me on Twitter (see right sidebar) and by RSS.

***************************************************

Author Kevin Benedict

Mobility Consultant, Wireless Industry Analyst and Web 2.0 Marketing Expert

http://www.netcentric-strategies.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 SAP CRM

In a recent analysis from Frost & Sullivan called, European Mobile Sales Force Automation (CRM/SFA) Markets, it is stated that mobile SFA is the largest application segment after wireless email, and this segment will grow close to 300% between now and 2013.

SAP seems to be making a big push in this area with mobile CRM partnerships with Sky Technologies (Certified SAP Partner, Certified SAP NetWeaver Partner) Sybase and RIM (Innovation Partners) in this area. What are the key areas covered by mobile CRM?

Activity management – Phone call, email, cold calls, what to do each day
Lead management – receive leads, contact, qualify
Opportunity Management – define, document and manage specific sales opportunities
Account Management – organizational charts, people, budgets, plans, needs

To me these are obvious needs for the mobile sales force. They work and travel in mobile environments so provide mobile tools that let them sell more product and make customers happier.

The future of mobile SAP CRM in my opinion is the combination of mobile SAP CRM and business intelligence. The ability to fully brief a traveling sales person on a customer’s account status, order history, shipments, credit status, financials, latest news and potential opportunities using text and audio files is very useful. Audio because many times a sales person is flying or driving and would benefit from having this information in audio format so they could listen to it.

In addition to the obvious account information, what additional kinds of mobile information do you think would be useful to integrate within a mobile SAP CRM?

For related articles please read:

The Future of Mobile and Route Sales Applications for Smart Phones, Part 1
The Future of Mobile and Route Sales Applications for Smart Phones, Part 2

***************************************************
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 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.
**************************************************

Body Weight, Twitter, M2M and Mobile Applications

In the past I have written articles about M2M and mobile applications. These have been in the context of machines sending wireless data to other machines. I believe the value of these applications have not been fully realized, and am excited about seeing more of them. If readers of this blog have interesting M2M solutions please share them with me.

My wife sent me an article on one of the most interesting (read disturbing) examples of M2M. Seems there is a home scale, for $159, that is wirelessly enabled and sends Twitter messages with your weight to anyone following you. Let me ask by a show of hands how many of you want to see my daily weight tweeted to you? All of you with hands up will be deleted.

I have seen and heard numerous examples of great M2M use cases. An article I wrote yesterday discussed street parking sensors that automatically send messages to a mobile service that notifies subscribers of available parking spots. I have seen electrical utility companies install wireless monitors at remote substations. I have heard of mobile wireless sensors in green houses and chicken houses that monitor, report and adjust temperatures.

The ability to automatically collect data, wirelessly transmit the data and accept electronic instructions from a distant mobile supervisor is a very interesting concept. The military is using more and more of these sensors in their Network-Centric Warfare strategies. I wrote about this strategy in terms of field force automation in this article.

Please send me interesting use cases for M2M and I will the best examples here.

If any of you are tempted to automatically send me messages concerning your body weight, or other information of a VERY personal nature, please resist.

***************************************************
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 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.
**************************************************

Street Parking and Mobile Data Solutions

I had several very interesting calls yesterday with various mobile industry dignitaries. We shared ideas, concepts and experiences around mobility. One of the mobile use cases that really stands out to me is the use of wireless parking sensors used in 25,000 on-street parking spots in San Francisco.

It seems the parking sensors can detect the presence of a vehicle. When no vehicle is in the parking spot, it can transmit an "availability" message to a central server that broadcasts the location to mobile devices of drivers. Drivers can simply open the application and view the location of all available on-street parking locations.

This use case for a mobile application is AWESOME! I applaud the imagination and creativity of the entrepreneurial team that put that together. A common pain point, that bright minds have addressed. I am inspired.

Another person I spoke to yesterday was in Kenya, Africa working at a large cement manufacturing plant. They have been implementing many new SAP processes to better track inbound materials from suppliers, and are now preparing to implement various delivery and scheduling applications using SAP partner Sky Technologies' SkyMobile application to extend business processes out to the mobile workforce.

This cement company estimates they have already saved over $1 million in materials tracking improvements, and now expect to add to their ROI by mobilizing more SAP business processes.

***************************************************
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 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.
**************************************************

SAP Mobility – Is Change Coming?

I read a very interesting article in BusinessWeek (February 9, 2010 edition) today called "What SAP Needs After Apotheker" by Aaron Ricadela. Last week, as many of you know, Leo Apotheker was replaced as CEO of SAP by both Bill McDermott and Jim Hagemann Snabe who were announced as Co-CEOs. In the article SAP mobility is raised again and again as an area where improvements are needed. Here is an excerpt, "In order to fix SAP, former North American sales boss McDermott and Snabe, head of product development, need to stock its pipeline with products that companies are more interested in buying… SAP must develop versions of its complicated software that can be delivered over the Internet and run on new classes of mobile computing devices."

In December of 2009, SAP unfolded their 5-year strategic plan that emphasized the following five points: on-demand computing, cloud architectures, flexible pricing, mobile and in-memory computing. This event was covered well by InformationWeek in an article called SAP Outlines 5-Year Enterprise Software Plan. I assume this 5 year plan announced in December was developed by Snabe and his team, so Apotheker's departure is unlikely to change this emphasis.

Don Bulmer, SAP VP of industry relations is also quoted at a recent Influencer Summit in Boston saying, "Sixty to seventy percent of the population has mobile devices… There are lots of opportunities for SAP." This seems to back repeated comments from SAP executives that they recognize the importance of mobility.

Here is another excerpt from BusinessWeek, "SAP needs to articulate to customers a clearer plan for delivering new technologies that can save money and make workers more productive, says Forrester analyst Hamerman." He goes on to add, "the company (SAP) must deliver more software over the Web and let users interact more capably with it through smartphones and tablets...Those are on the road map but they don't seem to be a priority...We haven't seen from them (SAP) a comprehensive technology strategy."

Hamerman does not seem to feel a listing in the 5 year enterprise software plan is sufficient. He wants to see a comprehensive technology strategy and a demonstration that mobility is a priority.

More from BusinessWeek, "Additional announcements of SAP software for cloud computing and mobile devices will come later this year, according to a person close to SAP. To get the message across, Plattner (Hasso Plattner, SAP co-founder) even plans to deliver his keynote address in Orlando with the help of an Apple iPad."

McDermott also tried to communicate that mobility was a SAP priority with the following announcement, "SAP plans to announce new online software under the Business By Design brand name for customer management, human resources, and procurement. Once it arrives in the second half of this year, customers will be able to run the software on their own servers, access it through the Web, and run portions of it on mobile devices."

In summary, SAP says mobility is one of the 5 key points in their strategic 5-Year Enterprise Software Plan. SAP's new Co-CEOs have reiterated that mobility is a high priority. Don Bulmer, SAP VP of industry relations agrees that there are lots of opportunities for SAP in mobility. Forrester analyst Hamerman says that it is not enough to say it, "Show me the money!" SAP Co-Founder Hasso Plattner says, "OK, watch me do a Sapphire power point on an iPad."

Here is another challenge – SAP has announced multiple reseller and co-innovation agreements with mobile solutions companies like Sky Technologies, RIM, Sybase, Syclo and ClickSoftware. So a customer looking for mobile solutions on SAP's EcoHub will find a plethora of mobile software solutions. In fact, mobile solutions for just about any need.

If I am looking for a good mobile enterprise application platform to work with SAP, I will find the following; Sybase for mobile Field Sales (except RIM users who can use RIM's mobile SAP CRM or Sky Technologies customers who can use their mobile version of SAP CRM?), Syclo for mobile field services, ClickSoftware for mobile route optimization, Sky Technologies for companies wanting to standardize on SAP embedded code? Is that clear to you? No, me neither.

Gartner analysts are suggesting that large enterprises should reduce the number of mobile application vendors. Read the following excerpt from Gartner's Magic Quadrant for Mobile Enterprise Application Platforms published December 16, 2009. "Enterprises are increasingly mixing solutions from multiple vendors, each with separate software stacks for data transport (which results in poor battery life). This also leads to conflicts with managing network connections on mobile devices, an inability to administer security and devices, complexities with testing, an increase in software defects, and higher service and support costs."

It will be very interesting to watch how SAP maneuvers the mobility landscape in 2010. Will SAP leave the task of bringing order out of chaos to third-party MEAP vendors, or will they?