Showing posts with label meap. Show all posts
Showing posts with label meap. Show all posts

Notes from the Enterprise Mobility in Defense Conference

I spoke at my first military oriented mobility conference today.  It was located in Washington DC, and while attending the other sessions I was able to fill seven pages of notes.  I will refrain from posting all seven pages and just give you the highlights here.
  • Companies don't own brands any longer, their consumers do.  Their consumers can do whatever they want with your brand in the social media space - freedom of speech.  Companies need their consumers to protect and promote their brands since companies can't control the message any longer.  That means a completely different brand strategy.  I credit Fred McClimans, Managing Director, McClimans Group for this insight.
  • Generals today must learn about mobile technologies and social networking from their young enlisted men and women.  The younger generation has a more complete understanding of these technologies.
  • Americans, unlike many countries, raise soldiers accustomed to independent thought and action.  In many countries and cultures people won't think or act independently. They only follow commands.  This is a cultural and environmental competitive advantage for Americans.  Even in disconnected environments, the US Military can expect their warfighters to continue to act and follow through on a mission without additional communications or commands.
  • Our mobile capabilities and our country's competitive advantages are limited by the amount of frequency spectrum available.  We need to eliminate congestion and open up more spectrum to maintain our competitive advantages.  This is a long term problem and will take time to solve.
  • Military pilots are using more and more tablets.  These tablets must be small enough to be worn without injury during emergency ejections.  If the tablet is too big, it can break the pilot's leg during ejection (they are strapped to a pilot's right leg).
  • The army is currently using the following categories of mobile apps: training, inventory, medical, mapping, command and control and language translation.
  • Modern warfare, as conducted in Afghanistan, is more like gang warfare than wars of the past.  Mobile apps that help intelligence personnel diagram and understand human networks are important today.
  • The army divides mobility into four areas, 1) governance, 2) centralized app library, 3) development frameworks and 4) app certification.
  • Social networking on mobile devices causes problems for the military.  Facebook wants to use geo-location to reveal the location of soldiers in the field.  Military commanders might click a "Thumbs-Up" symbol to like a comment and suddenly they are being publicly quoted as supporting political parties and views that cause problems.
  • The Pentagon wants to support a BYOD strategy, however, this means the Pentagon can tell BYOD users when they must buy a new device to stay compliant.  Yikes!  There is still much work to be done before this becomes a reality.
  • The DoD (department of defense) believes they will save tens of millions of dollars by moving toward a BYOD strategy for non-classified use cases.
  • The DoD today has secure smartphones but they cost $8,000 USD each.  Ouch!  I see their motivation for wanting to support a secured BYOD environment.
  • Random information - the Pentagon receives 8 million emails per day, but only sends 1 million.  I am sure there is some sort of interesting insight here, but not from me.
  • The Pentagon believes Big Data is the next big wave.  As you can image, the volume of data coming into the Pentagon is mind boggling.  Only about one percent is analyzed today, and the other 99 percent is quickly scanned and archived.  However, Big Data promises to be able to help find additional trends and patterns in the 99 percent fast enough to be useful in the near future.
  • The Pentagon believes Big Data will force companies to re-engineer and rearchitect many of their systems in order to take advantage of it.
  • The Pentagon really only started to get serious with enterprise mobility in 2012.  Now many pilot projects are underway.
  • Securing the data is really the object not securing the mobile device.  This may require some kind of data tagging so the data can be protected for its entire life cycle.  Data may be tagged with different levels of security in the data properties so only the appropriate users can view it and apps integrate it.
  • The biggest enterprise mobility challenge in the military today is how to respond to the "consumerization of IT" trend in a secure environment.
  • There are two high level areas of mobility in the military, 1) garrison mobility (non-classifed, not warfighter oriented apps), and 2) tactical warfighter apps for the battlefield environment.
  • The Marines are wanting to drop BlackBerry support in favor of BYOD strategies for non-classified users and apps to reduce costs.
  • The Marines, for legal reasons, want a smartphone that has separate partitions for personal and military use.  The Marines want to control and own the apps and data in their portion, but not in the personal partition.  They are still looking for an ideal smartphone that meets these requirements.
There you go!  I saved you a trip and a long day listening to mobile secure lecture after security lecture.  You are welcome :-)
*************************************************************
Kevin Benedict, Head Analyst for SMAC, Cognizant
Read The Future of Work
Follow me on Twitter @krbenedict
Join the Linkedin Group Strategic Enterprise Mobility
Full Disclosure: These are my personal opinions. No company is silly enough to claim them. I am a mobility and SMAC analyst, consultant and writer. I work with and have worked with many of the companies mentioned in my articles.

Gartner's New 2012 Magic Quadrant for Field Services

Have you seen the new 2012 magic quadrant on field services from Gartner?  It is quite strange.  SAP is listed in the bottom left even after the Syclo acquisition?  I thought Syclo was all about mobile enterprise asset management which is very closely aligned with field services (think preventative maintenance and repairs).

ClickSoftware, however, is listed far above everyone else in the top right quadrant.  The strange part is that SAP resells ClickSoftware's solutions as the SAP Workforce Scheduling and Optimization solution and it utilizes the SAP Mobility Platform.  What a small world we all live in.  It seems the Gartner analysis is less about the technology, and more about how it is positioned in the market.  I say that because you can get the same solution from both companies yet they are far apart on the MQ.

My analysis is that field services is much more than just a mobile app platform.  It includes dynamic scheduling, rostering, forecasting, time sheets, planning, etc.   Mobility is simply extending and enhancing the power of those solutions.  Without those connected back-office solutions, mobility loses much of its value.  That is how I interpret the MQ.  What about you?

More pondering... This must present a real dilemma for SAP sales folks selling into field services opportunities.  Should they sell their prospects the SAP Workforce Scheduling and Optimization solution by ClickSoftware, which is on their price list and listed in the very top right Gartner MQ for Field Services and sits on top of the SAP Mobility Platform, or should they sell their prospects just SAP Mobility Platform which is listed in the bottom left.  Yikes!  That is going to require some strategy.

In a timely but coincidental note, I will be joining Stewart Hill from ClickSoftware at 11 AM EST on November 13th to present a webinar titled, "Using Mobile Technology to Drive Business Visibility and Real-time Decision Making."  What a fun subject!!!  I invite you to join the discussion by registering here.
*************************************************************
Kevin Benedict, Head Analyst for SMAC, Cognizant
Read The Future of Work
Follow me on Twitter @krbenedict
Join the Linkedin Group Strategic Enterprise Mobility
Full Disclosure: These are my personal opinions. No company is silly enough to claim them. I am a mobility and SMAC analyst, consultant and writer. I work with and have worked with many of the companies mentioned in my articles.

Mobile Expert Video Series: Michael King

This week I am in beautiful Silicon Valley in California where I met up with, and had the honor of interviewing Michael King, former Gartner mobility analyst and now Director of Mobile Strategies with up-and-coming mobility vendor Appcelerator.  In this segment of Mobile Expert Video Series, we discuss the concept of BYOA (bring your own apps), and the criteria he used when looking for a mobility vendor to join.


*************************************************************
Kevin Benedict, Head Analyst for SMAC (Social, MOBILE, Analytics and Cloud), Cognizant
Read The Future of Work
Follow me on Twitter @krbenedict
Join the Strategic Enterprise Mobility Linkedin Group
Full Disclosure: These are my personal opinions. No company is silly enough to claim them. I am a mobility analyst, consultant and writer. I work with and have worked with many of the companies mentioned in my articles.

Observations from the Enterprise Mobility Exchange in Rotterdam

Rotterdam
I enjoy the enterprise mobility exchange events.  This is my third time being the chairman at these events, and I keep coming back because I learn a great deal.  It is an event dominated by end users, rather than vendors.  I have nothing against vendors, as they sponsor the events and lead some sessions, but the event is organized to give end users an opportunity to discuss their needs, network and learn from other end users and their experiences.

In addition to the keynote presentations, there are case studies, think tanks and a CIO session.  The CIO session was very interesting.  CIOs bring a list of topics important to them and submit this list to the other CIOs for discussion.  The subjects are all related to enterprise mobility in the real world and addressing the challenges that come along with it.  I learned.

I saw several celebrity sightings yesterday including Nicholas McQuire, Research Director, IDC Research and Daniel Faulk, SAP Mobility Product Manager.

Today we hear from Coco Cola Bottling Company, IDC Research, National Grid, TNT Express, Philips Healthcare, EPAL, R. Hoffmann-La Roche and many others.

I also saw booths from mobility vendors Syclo, SAP, Antenna, ClickSoftware, Verivo and many others here.  You can follow events on the Twitter feed #emeeu.

I learned that many of the companies here struggle with change management and different cultures around the world.  It appears that in many places around the world service engineers are not happy with change, process improvement or accountability.  In fact, in many cases there is an ongoing battle between management wanting to optimize their operations and processes, and service technicians that want no such thing.  I heard from three different organizations yesterdaythat are constantly dealing with a workforce that tries to sabotage field force automation and mobility projects.  Wow!  Those are challenges that go way beyond an enterprise mobility discussion.  Those are political, cultural, legal, ethical and societal.  Yikes!  I will stick with the HTML5 vs. Native, Buy vs. Build, MDM, MEAP, MADP and other acronym discussions.

Join me on this webinar!
*************************************************************
Kevin Benedict, Mobile Industry Analyst, Mobile Strategy Consultant and SAP Mentor Alumnus
Follow me on Twitter @krbenedict
Full Disclosure: I am an independent mobility analyst, consultant and blogger. I work with and have worked with many of the companies mentioned in my articles.

Kevin Benedict's Video Comments: Mobile Development Models

In this segment of "Kevin Benedict's Video Comments" I share the six different models for enterprise mobility apps.  If there are more, please share so I can add them to the list.  These six take different levels of development, different designs and support models.




*************************************************************
Kevin Benedict, Independent Mobile Industry Analyst, Consultant and SAP Mentor Alumnus
Follow me on Twitter @krbenedict
Full Disclosure: I am an independent mobility analyst, consultant and blogger. I work with and have worked with many of the companies mentioned in my articles.

Enterprise Mobility, Re-usable Code and Private App Stores

Gil Bouhnick
A few years back when I was the CEO of a mobile enterprise application company, I spent a lot of time asking my PSO (professional services organization) the question, "Haven't we developed that before?"  The answer was nearly always, " Yes, but it won't work on this project."  That is not the answer a CEO wants to hear.

The dream I had was to own a library of reusable code or objects that I could build once, and leverage on hundreds of future mobile projects.  This week I read an article by my friend Gil Bouhnick, about ClickSoftware's new ClickAppStore.  This is the model I had always wanted.

It is not an app store for the public, it is a private app store for your internal developers and consultants.  Here is how ClickSoftware describes it, "The ClickAppStore is designed to allow IT people, system implementers and administrators do more with their ClickMobile product by downloading and embedding business apps inside one powerful mobile foundation called ClickMobile, and run them on any popular device out there from iPhones and Android smartphones to tablets, rugged PDA’s and laptops."

This isn't going to help IT departments that don't use ClickMobile, but it offers a huge efficiency for those that do.  ClickMobile is integrated with SUP (Sybase Unwired Platform) and plays nice with SAP.  The ClickAppStore solution that Gil is writing about and promoting in his article is designed to help companies develop the majority of their mobile apps by using visual configuration tools, wizards, drag & drop style editors etc, and downloading pre-build business apps front he ClickAppStore.

I am thinking through the requirements here...  This must have taken a lot of strategy sessions before this was built.  I love the notion!

The concept of a mobile app store for use internally is another important part of a complete mobile strategy.  Again, from a former technology CEO, it will drive you crazy if you have to rebuild and re-invest in the same tools over and over again across your global company.  It makes so much more sense to use a standard IDE (integrated development environment) and MEAP (mobile enterprise application platform) for your custom mobile applications, and then save the mobile business applications into a mobile app store so other internal parties can use them.

*************************************************************
Kevin Benedict, Independent Mobile Industry Analyst, Consultant and SAP Mentor Alumnus
Follow me on Twitter @krbenedict
Full Disclosure: I am an independent mobility analyst, consultant and blogger. I work with and have worked with many of the companies mentioned in my articles.

Coca Cola Consolidated and Enterprise Mobility

I just listened to an overview of a recent mobility project that Coca Cola Consolidated did using the system integrator Energy4U and the MEAP vendor Syclo.  The solution integrated with SAP.  It was basically a mobile shipping, inventory and warehouse application.

A few interesting points, 1)Coca Cola Consolidated are mobility veterans in some parts of their organization with over 25 years of mobility experience, but they outsourced this project to a mobility vendor and a system integrator, and 2) the project only took 8 weeks.

Coca Cola Consolidated selected Energy4U and Syclo as their mobility implementation team because mobility was not their core focus.  They wanted to outsource this effort to an experienced team with SAP expertise.

The success of the project was credited to productive on site visits where processes and requirements were accurately documented, trained experts and a good MEAP vendor.  It also helped that there was a very experienced Energy4U mobility team that were skilled veterans of developing on Syclo's Smart Mobile Suite.

Venky Govind of Coca Cola Consolidating said they wanted a mobility vendor that would be responsible for supporting all of the current and future mobile operating systems and devices, and keeping the MEAP (mobile enterprise application platform) updated.  They did not want that responsibility in-house.

This solution was replacing a manual paper driven process.   The mobile app replaced the paper forms and simplified the entire process while automating the data collection and integrating it directly with SAP.

*************************************************************
Kevin Benedict, Independent Mobile Industry Analyst, Consultant and SAP Mentor Volunteer
Follow me on Twitter @krbenedict
Full Disclosure: I am an independent mobility analyst, consultant and blogger. I work with and have worked with many of the companies mentioned in my articles.

IBM to Acquire Mobility Vendor Worklight - An Analysis

IBM has jumped into the MEAP (mobile enterprise application platform) competition with yesterday’s announced intent to acquire MEAP vendor Worklight.   Worklight is headquartered in New York and was founded in 2006 by CEO Shahar Kaminitz.  Worklight's software supports HTML5, hybrid and native applications for smartphones and tablets with industry-standard technologies and tools.   Their solutions include an Eclipse-based software IDE (integrated development environment), mobile middleware, mobile solution management and analytics.

Worklight Studio competes with Appcelerator, Verivo (formerly Pyxis Mobile), Sybase Unwired Platform (SAP), Antenna, Syclo, ClickSoftware, Kony Solutions, Rhomobile (Motorola), Webalo and other mobility vendors that are experiencing rapid growth.

The deal size was not disclosed by IBM or Worklight, but the Israeli website Globes (www.globes.co.il) reported the acquisition to be $50-60 million.  Worklight raised $21 million in investment capital, from investors Genesis Partners, Pitango Venture Capital, Index Ventures, and Shlomo Kramer.  Globe also estimated 2011 revenues for Worklight at between $5-10 million (http://www.globes.co.il/serveen/globes/docview.asp?did=1000720723).


My analysis is that all ERP vendors need a standardized approach for supporting mobility.  Mobility, and MEAPs in particular, are far too strategic to leave up to partner ecosystems to deliver.  SAP acquired Sybase, IBM will acquire Worklight, and we are all awaiting Oracle’s expected 2012 move to acquire a MEAP vendor.

Interesting note, I cannot think of many situations where an ERP vendor bought a mobile apps company.  I am told that SAP's proposed acquisition of SuccessFactor will involve some mobile apps, but have yet to see them.  ERP vendors seem to want to buy the middleware, so they can standardize integration, syncing, security and management, and leave most apps to their partner ecosystem.

In a recent IBM study of more than 3,000 global CIOs, 75 percent of respondents identified mobility solutions as one of their top spending priorities.  Nearly all of the global analyst and research firms are also reporting enterprise mobility to be a top three priority.  In the Enterprise Mobility Survey 2011 that I conducted in September of 2011, 80% of survey respondents said enterprise mobility was "very important" to "critical" to their company's future success.

IBM officials said with this acquisition, IBM's mobile offerings will span mobile application development, integration, security and management.  Dow Jones Newswire reported on an internal memo from IBM’s senior vice president in charge of middleware software, Robert LeBlanc that highlighted their ambitions, “"Now is the time to make IBM essential in the era of mobile computing."

I had the privilege of interviewing Worklight’s COO Kurt Daniel about 15 months ago and published the interview on this site.  Here are some excerpts that you may find interesting given this week's news.


Worklight has developed a MEAP (mobile enterprise application platform) and a mobile SDK (software development kit), not for their own use, but rather for systems integrators and end customers to use to develop their own enterprise mobility solutions.  They want to be a technology company, not a mobile application company.

Kevin: What are your areas of responsibilities at WorkLight?
Kurt:  I look after our worldwide business channels, partnerships, sales and marketing.
Kevin:  Tell me about your solutions.
Kurt:  We have the WorkLight Studio, WorkLight Server and WorkLight console.  ISVs and OEM partners use these solutions to build their own packaged mobility applications.
Kevin:  How do you avoid competing with your partners in the mobility market?
Kurt:  We don't sell applications.  We are not experts on ERPS or other backend systems.  We focus on developing the best mobile technology possible, not services or mobile applications.
Kevin:  How do you fund your start-up business in the early years without generating revenue from services and mobile applications?
Kurt: We raised over $17 million.  That affords us the opportunity to invest in the technology without losing focus by delivering services and enduser solutions.
Kevin:  How do you keep your users loyal to your technology?
Kurt:  We provide them with a platform and SDK that supports the latest modern devices.  We provide them with great productivity tools that enable the same code base to be used across multiple devices and mobile operating systems.  We offer trial versions for 60 days.
Kevin:  Where do you see mobility going in the next 18-24 months?
Kurt: Enterprises are going to need to support a larger number of mobile devices and mobile operating systems.  They will need to support iPads, tablets of all kinds, Android and many more mobile apps.  Internally, companies will be launching large numbers of their own mobile applications that were developed in-house.
Kevin: Who do you compete with?
Kurt:  In-house development teams, Sybase and Antenna.
Kevin:  In conclusion, where does your company fit in the enterprise mobility ecosystem?
Kurt:  WorkLight is a 100 percent technology focused company.  We develop a horizontal MEAP.


It is fascinating to ponder Worklight's strategy.  They decided to build a new and powerful MEAP, but not to provide services or sell mobile apps to end users.  They chose to use their investment capital to focus exclusively on developing technology and developer support.   That is a rare strategy.  Sybase mostly followed that strategy with their embedded mobile database and synchronization business (iAnywhere and former Extended Systems) and was purchased by SAP, and now Worklight who followed a similar strategy will be acquired by IBM.  What does this tell us?  Perhaps ERP vendors don't want the burden of supporting a large MEAP or mobile app enduser base that does not fit their traditional customer profile.  They would rather just acquire the technology stack?  What do you think?

Most MEAP vendors depend on services and end user app sales to help cover expenses as they develop and mature their solutions and channels.  Worklight refused to follow that path.   It doesn't appear they had yet reached profitability, since it seems they took in another $4 million in investor funding in the past year, but they did accept IBM's offer as their exit strategy.  They committed to focus on the technology, rather than indulge the temptation (and distraction) to grab short term end user sales.

End user mobile app sales are sexy.  They get the press and show well, but ultimately I think the MEAPs themselves are the mobile market consolidation points.  Not just the mobile middleware, but the IDEs.  The integrated development environments that are used to design and develop the apps.  Some mobility vendors like ClickSoftware and Syclo actually support several choices of mobile middleware under their IDEs.  The customers often only see the IDE, but underneath the covers are middleware options.  SAP and the Sybase Unwired Platform also offer numerous choices (SUP, NetWeaver Gateway, Sybase 365, etc.) for middleware in their architecture.

If all the large ERP companies are going to ultimately acquire their own MEAP solution, that means MEAP market fragmentation will be hardened along ERP lines.  If that is the case, would mobility vendors that focus on mobile end user applications find it necessary to support all the major MEAPs if they want to sell into those markets?  That would be expensive!!!  If that is how the market evolves, then it seems cloud based ERP-to-mobile app integration hubs would be worth a consideration.  Mobile app developers would simply connect to one cloud based integration hub that integrates with all the ERPs.  Wow, this line of thinking reminds me of my early days working with EDI/B2B translators and EDI hubs.

It will be interesting to watch the choices companies will make that have a mix of different business solutions and ERPs across their IT landscape.

If I have any bad data or information in this article please correct me!

Please share your thoughts and ideas with us!!!


*************************************************************
Kevin Benedict, Independent Mobile Industry Analyst, Consultant and SAP Mentor Volunteer
Follow me on Twitter @krbenedict
Full Disclosure: I am an independent mobility analyst, consultant and blogger. I work with and have worked with many of the companies mentioned in my articles.

Flattening the Stack with Integrated App Development, MDM, and Hosted Solutions

Andre Guillemin
I want to thank my friend and mobility expert André Guillemin for writing this article and sharing it with all of us.

As the mobility needs of the enterprise continue to evolve, solutions providers are under increasing pressure to offer product suites that provide mobile device management, application development, and hosting capabilities all under one roof. Currently, solutions providers tend to specialize in one of the three, forcing most enterprise companies to purchase multiple solutions. Stacked on top of each other, an MDM, app development platform, and a hosting services package may provide the total functionality needed, but it’s not the most elegant solution.

So how are providers responding? The emerging trend among the major players in the mobile enterprise application platform (MEAP) space is to start piling on the features…and fast. Antenna Software just bumped up its MDM capabilities with the release of its Volt platform, which enables companies to publish and manage HTML5 apps with many common enterprise MDM features such as remote wipe. Another example is Pyxis Mobile, which recently rolled out a hosting solution that pairs nicely with its app development platform.

With the race on to expand their capabilities, you may wonder if these companies are biting off more than they can chew. It doesn’t seem so. For starters, most of the companies in this space built their business by developing specific solutions to specific problems. Only recently have they been pressured to expand beyond their core competencies in order to supply more comprehensive solutions that address multiple components of the enterprise mobility ecosystem. Secondly, many companies are filling those gaps not by trying to reinvent the wheel but by partnering with other specialists and rolling out white labeled products. The best example is hosting, where most providers have turned to dedicated hosting services companies to add that capability to their product portfolio because it’s faster, easier, and better for the customer than trying to build it themselves.

Where does all that leave us? As always, the devil is in the details. When shopping around for middleware solutions, make sure you’re prepared with a thoroughly vetted list of requirements and use that list to check it against the capabilities of the products you’re evaluating. Know what apps you’re going to build, who you’re going to build them for, and how they’re going to be used – not just today, but have a strategy that projects out at least three years. Think about the way mobility will grow and evolve within your company. You may be focused on employee apps today but what about customers and supply chain partners? How will your entire company be using mobility in three to five years?

Being able to paint the broad picture and then hone in on the details is critical because knowing exactly which capabilities, functions, and features you require in your development and management tools will help you avoid costly mistakes down the line.

Let us know what’s important to you. Take Kevin Benedict’s Enterprise Mobility Survey and receive a free copy of the results!

Today's Guest Columnist: André Guillemin has over ten years of experience in health care, financial services, and mobile technology. He spent the past three years focused on cross-industry solutions for mobile enterprise application development, including line of business uses in manufacturing, life sciences and wealth management. Mr. Guillemin frequently contributes to industry publications, panels, and events, and is available for consultation on the strategic and tactical use of mobile technologies in the enterprise.

*************************************************************
Kevin Benedict, Independent Mobile and M2M Industry Analyst, SAP Mentor Volunteer
Follow me on Twitter @krbenedict
Full Disclosure: I am an independent mobility analyst, consultant and blogger. I work with and have worked with many of the companies mentioned in my articles.

Mobile Expert Video Series: ClickSoftware's Uri Pintov

Uri Pintov is the Team Leader of the Solutions Group at ClickSoftware and he shares his views on HTML5 and device agnostic MEAPs, plus his predictions for Windows Phone 7.



Upcoming Events

Critical Requirements for Mobile App Development:  Agility and Speed Strategy, Process, and Tools to Accelerate Mobile Development, July 21, 2011
Mobile Tablet Trends in the Enterprise featuring Samsung Mobile - July 28, 2011

Whitepapers of Note

The Business Benefits of Mobile Adoption with SAP Systems
ClickSoftware Mobility Suite and Sybase Mobility Solution
Mobile Adoption Among Gas and Electric Utilities
Mobile Adoption in Life Sciences
Mobile Adoption in Oil and Gas
Networked Field Services

Recorded Webinars of Note

3 Critical Considerations for Embracing Mobile CRM
The Future of Enterprise Mobility
The Latest m-Business Trends and How the Onslaught of Mobile Devices Affects Development Strategies
The Real-Time Mobile Enterprise:  The Benefits of Rapid, Easy Access
Syclo and SAP Deliver Mobile Apps on Sybase Unwired Platform

You can follow me on Twitter @krbenedict.
*************************************************************
Kevin Benedict, Independent Mobile and M2M Industry Analyst, SAP Mentor Volunteer
Follow me on Twitter @krbenedict
Full Disclosure: I am an independent mobility analyst, consultant and blogger. I work with and have worked with many of the companies mentioned in my articles.

Mobile Expert Interview Series: SAP's Jack Chawla

SAP's Jack Chawla


I had the privilege to interview Jack Chawla, who is Senior Director, Technology Marketing with SAP's Mobile Business Unit last week via email.

Note:  This interview took place via email, so these are Jack Chawla's words with minor edits.

Kevin:  What mobile device(s) do you carry?
Jack:  I generally have the following devices in my vicinity. . . BlackBerry, iPad, iPhone, MBA and Lenovo.  While traveling, I try to carry not more than three devices. . . but sometimes I end up carrying more devices than pants!

Kevin:  What are your favorite mobile applications that you have on your mobile devices?
Jack:  I use Twitter, Bloomberg, Yelp, NYT, Pandora, Kindle, Google Maps, Google Search, Gmail and Camera apps the most.  I have more apps than I would like to admit on my devices.

Kevin:  Do you use your mobile device to buy things?
Jack:  Yes, I use the Amazon app to find and buy stuff cheaper than in retail stores!  I love the Amazon Remembers feature.

Mobile Expert Interview Series: Pyxis Mobile's EVP Christopher Willis

Pyxis Mobile is one of those companies that accomplishes great things, but moves under the radar.  Gartner recently highlighted Pyxis Mobile in their Magic Quadrant report so moving under the radar may be over.  Pyxis Mobile has over 500,000 mobile clients in the field.  Most of their traditional customers are in the financial services industry, but they have been rapidly expanding into higher education, manufacturing and pharmaceuticals. I had the opportunity recently to interview Chris Willis, Pyxis Mobile's EVP of Marketing and Strategy.

Chris joined Pyxis in 1998.  In 2001 the company became 100% focused on enterprise mobility. 

Chris what mobile device do you carry?
I carry two mobile devices, the iPhone for personal use, and the BlackBerry Bold for professional use.  I have always used BlackBerrys professionally and am just used to it.  I know how to get what I need from it.  I use the iPhone as a large iPod.

What is your favorite mobile application?
A CRM application built by Pyxis Mobile.  It is connected to our expense management system and enables me to complete my expense reports while on the road.  On the personal side I love MLB at Bat.  When you see MLB at Bat on an iPad it is amazing.  It is better than the programs you get at the game.

What industries do you see adopting mobility?
Financial services is big for us.  Seventy percent of our business is still in financial services.  We have developed complete trading systems on mobile devices for some customers.  Higher education is big for us.  We have developed all kinds of mobile applications for universities that show class schedules, grades, etc.  Emerging markets for us are in manufacturing and pharmaceuticals.

What business processes do you see companies mobilizing first?
Sales and field services to start, however, nowadays we are seeing a lot of B2C (business to consumer) application demand.  Companies want to give mobile applications to their customers for product sales, branding, marketing and customer support.

What are some of the most surprising trends that you saw in mobility over the past 12 months?
B2C is the biggest trend - "There's an App for that!"  Companies wanting to provide their customers with mobile applications.

What do you see happening in the near future, say 2010-2011?
Mobility vendors delivering on their promises and filling the missing "app gaps."  Companies are now educated on mobility.  They are now looking for complete solutions and mobility platforms to execute a full enterprise mobility strategy.

Tell me about some of the most interesting mobile applications you have seen in the market.
We have developed a mobile laundry application.  It is a M2M (machine-to-machine) application.  Laundry machines text students in the dorms when there is a machine available and when it is finished.  Another application I love is from Concur Mobile.  It helps you book travel, manage travel expenses, call taxis and have it all paid for by the credit card they have on file.  No cash needed.  You can also use it to photograph receipts and turn them in as well.  Nice!

What are some of the most unusual mobile applications you have seen?
There is an application that consists of a website and a mobile application. The website shows a 2D barcode on the screen, and your iPhone captures the barcode and activates various games that use the accelerometer on the iPhone to control various objects in races.  Very interesting!

When is a consumer oriented mobile device sufficient, and when do you need a ruggedized industrial grade device?
Consumer devices (smartphones) are capturing market share from industrial grade mobile handhelds.  There is less interest in expensive rugged devices, because the service technician is carrying a smartphone anyway.  If you buy expensive rugged devices, they will now have two devices to break.  Many companies are simply buying rugged cases for smartphones.

What is the most complex mobile application that you have seen?
We developed entire mobile trading systems for use by companies in the financial services industry.  Very complex!  We developed a very sophisticated mobile application for Thomas Reuters that pulled data from dozens of different sources.

What are some of the biggest challenges you see in the mobile industry today?
Rapid changes to mobile operating systems and new mobile devices.  Today Samsung announced a new mobile OS.  Today enterprises use the same mobile OS as consumer devices so we need to stay on top of all of them.

What do you see from ERP vendors in mobility?
All ERPs have to mobilize their solutions.  Pyxis Mobile is supporting all the majors, and we believe this is a competitive advantage.

What is still missing from MEAPs (mobile enterprise application platforms)?
I think MEAP vendors are simply taking different approaches.  Some try to be ERP agnostic.  Others focused on specific markets.  I think the differences will be how effective you are with partners.  Are you systems integrator friendly?  Pyxis Mobile provides tools for SIs to develop and support new mobile applications.  This is important!

How important is mobile device management to your customers?
It isn't.  Our customers don't ask for it.  Smartphones and online app stores seem to have resolved many of the earlier issues.  Perhaps in the future our customers will ask for it.

How is Pyxis Mobile positioned?
We are the one mobility platform that enables all of a company's mobility needs including B2B and B2C.  We cover mobile enterprise and consumer applications.

What are your thoughts on when thick/rich mobile clients are needed and when micro-apps or browser apps are needed?
We like rich native apps that optimize what you can do on each OS and mobile device.

Do your customers want to develop their own mobile applications using your Application Studio, or do they want you to develop it?
About 80% of our customers want us, or one of our systems integrator partners to develop the mobile application for them.  They are not experienced, but we are.

Thanks for your time Chris!!!

To read more interviews in the Mobile Expert Interview series, visit:
http://mobileenterprisestrategies.blogspot.com/p/mobile-expert-interview-series.html

To watch videos of mobile expert interviews, visit:
- http://mobileenterprisestrategies.blogspot.com/p/mobile-expert-video-series.html

For a weekly recap of mobility news, analysis and market numbers read:
- http://mobileenterprisestrategies.blogspot.com/p/kevins-mobility-news-weekly.html

***************************************************
Kevin Benedict, SAP Mentor, SAP Top Contributor, Mobile and M2M Industry Analyst
CEO/Principal Consultant, Netcentric Strategies LLC
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. I work with and have worked with many of the companies mentioned in my articles.
***************************************************

Mobile Solution Models, Part 1

It appears there are at least six unique mobile solution models.  This is a dynamic list, a work in progress, so please help me understand other models that need to be added.
  1. Mobile middleware - often includes a mobile database, a server database, synchronization, and basic database integration tools and general guidelines for using the middleware with your software development projects.  Typically, you develop in the programming environment of your choice (e.g. .NET, PowerBuilder, C++, Visual Basic) and integrate, the mobile middleware into your applications.
  2. Mobile browser applications - these are light weight browser based applications that often provide a mobile view into a back office business application or database.  They do not provide access to the data collection tools and functionality available on many devices.
  3. SEAP Infrastructure (I made this up) - smartphone enterprise application platforms - supports the testing, deployment, integration, and operations of mobile micro-applications often in cloud computing environments (although on premises versions are also available).  Mobile micro-applications may be developed for the iPhone, Android, and BlackBerry devices, etc., and downloaded from online application stores, but integrated to back-end ERPs via the SEAP Infrastructure.
  4. SEAP Infrastructure Plus - see number 2 and then add an SDK for rapidly developing mobile micro-applications that work with the SEAP infrastructure.
  5. MBA - mobilized business applications (made it up again) - shrink wrapped or off-the-shelf mobile clients for existing business applications.  The MBA can often be configured to match the basic customization of the integrated back-end business applications, but it is not designed for general purpose mobile applications.
  6. MEAPs - mobile enterprise application platforms - this is an enterprise class mobility platform used to support multiple mobile applications, disparate databases, different business processes, a wide range of mobile devices and operating systems, includes a comprehensive SDK for developing mobile applications and mobile device management.  It should be able to support mobile micro-applications and thick client mobile architectures.
There is a lot of noise around enterprise mobility today.  It is important to understand that a typical enterprise could realize solid ROIs by mobilizing dozens of different business processes.  IT departments may be receiving requests for mobile applications from the sales department today, but tomorrow it will be a dozen other departments all with different mobile device preferences and priority business processes.  The IT department needs to aggressively formulate a support and management plan that is flexible enough to satisfy a wide range of requests, requirements, and mobile devices before chaos reigns.

Many companies will be followers and simply want a "me too" mobile application that mobilizes common business processes, but others seek competitive advantages through mobile technologies.  These will seek to utilize mobile technologies in unique ways where shrink wrap applications do not exist.  These aggressive inventors and early adaptors want to control their own destinies and be able to develop mobilized business processes only they have conceived.  These inventors don't want to be reinventing the wheel. They want to spend their time developing visionary applications with massive ROIs.  They want a powerful MEAP to take care of all the mobile middleware infrastructure, integration, synchronization, security, and development infrastructure, but they want an SDK included that enables them to design, develop, test, deploy, and support a wide range of customized mobile applications and business processes.

Mobile "me-too" applications help you maintain the status quo.  Putting the power of a comprehensive MEAP in the hands of your brightest minds can be game changers. 

One of the key reasons SAP is following a partnership strategy for mobile applications, I believe, is that they realize they cannot develop all of the mobile applications that are being requested fast enough.  A partnership strategy enables dozens of SAP partners to fulfill the demand and enables the SAP ecosystem to compete with each other to make the most powerful and innovative mobile solutions possible.  However, just as SAP realizes they cannot solve all the mobility needs of the market themselves, neither can the mobility vendors. 

Mobility vendors must target the largest and most common business processes for mobilizing, as this is where the quickest and easiest sales revenue is located.  As a result, niche mobility applications that may provide a particular company with an enormous competitive advantage will be necessarily ignored.  The only way a company will realize the value of that competitive advantage is to implement it themselves.  That introduces another discussion which we will continue in Part 2.

***************************************************
Kevin Benedict
SAP Mentor, Mobile Industry Analyst, Founder/CEO Netcentric Strategies LLC
Author of the report Enterprise Mobile Data Solutions, 2009
Mobile Strategy Consultant and Web 2.0 Marketing Services
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. I work with and have worked with many of the companies mentioned in my articles. ***************************************************

MEAPs, Thick Clients and Mobile Chain of Custody Applications

For people with HIV/AIDS in developing countries like Ethiopia, Cote D’Ivoire, Kenya, and Ghana, receiving AIDS mediation in a cost effective, secure and reliable manner is critical to saving the lives of millions.  In addition to the health crisis, the geographical challenges of trying to care for patients that live in remote villages where access to medical facilities is minimal is a huge obstacle.

The challenge undertaken by global health organizations and companies funded by PEPFAR was to create a drug delivery system that would accomplish the following:
  1. Expedite the delivery process.
  2. Ensure the secure transfer of drugs.
  3. Provide visibility and transparency to participating agencies.
  4. Ensure accurate deliveries.
  5. Automate ARV drug processes that provide a rapid, regular, reliable supply of medications to patients.
  6. Provide a transactional record of the ARV drugs and test kits at every key point in the distribution chain.
The bottom line goal was to provide a truly mobile chain of custody system that could extend across a challenging geographical landscape with minimal technology infrastructure. How was this goal accomplished?  The answer - by implementing a MEAP solution that enabled delivery drivers to utilize a mobile application designed to work in a disconnected or connected model.  The application leveraged the power and flexibility of an enterprise quality mobile database in a thick mobile client that enabled the delivery drivers to maintain inventory counts, accept proof of delivery, and store key data on a consumer grade PDA until they could be connected with the internet at a later time.

Prior to implementing mobile solutions, agencies were only able to track drugs to a warehouse located in the larger cities in many countries.  Now delivery drivers are supplied with a mobile application that can track the delivery and re-ordering of ARV drugs from the warehouse, to regional distribution centers, to area regional centers and finally to the patient.  Every time the ARV medications change hands, a digital record is made of the transaction.  The information collected is synchronized back up the chain where program managers can actively manage the continual flow of mediations.

Since implementation this mobile solution has helped over 50,000 AIDS patients receive treatments in the Ivory Coast alone.  This, coupled with the fact that the mobile solutions decreased the delivery cycle from three months to as little as three weeks, has caught the attention of many other countries and relief organizations around the world.   These thick client mobile applications that operate in a connected and disconnected mode are critical to these kinds of environments.  Many organizations are looking at using MEAPs and thick client applications to offer better and more timely treatment to those afflicted with AIDS.

In the SAP ecosystem Sky Technologies, Sybase, and Syclo are the SAP mobility partners that seem to focus on supporting custom mobile applications with MEAPs that operate in both connected and disconnected modes using a thick client architectures.  By thick client I mean a mobile application that can operate with or without connectivity and that includes a mobile database for storing data on the device while waiting for synchronization.

In my opinion a good MEAP should have an SDK so that the IT department can utilize it to update and edit mobile applications and develop new ones.  Without a good SDK that the IT department can learn, the enterprise is hostage to the vendor.  The world of mobility is moving far too fast, and the IT department needs to be able to update and upgrade mobile applications on their schedule not the vendors.

Mobile micro-applications and mobile browser based applications are valuable and provide significant ROIs in many situations, but they cannot support the rugged environments described in this case study and would not have saved thousands of lives like the thick client mobile solution that was used.

***************************************************
Kevin Benedict
SAP Mentor, Mobile Industry Analyst, Founder/CEO Netcentric Strategies LLC
Author of the report Enterprise Mobile Data Solutions, 2009
Mobile Strategy Consultant and Web 2.0 Marketing Services
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. I work with and have worked with many of the companies mentioned in my articles. ***************************************************

Everyone Wants A Piece of SAP Enterprise Mobility!

I was surprised to read today that SAP's ECM (enterprise content management) partner Open Text Corp. now has a mobile applications strategy.  "This move is part of a strategy designed to help organizations harness the power of today’s mobile workforce in an effort to increase productivity."

The solution is called Open Text Everywhere and it is designed to make the entire Open Text ECM Suite available through mobile devices.  This move by Open Text highlights an interesting evolution in the mobile ecosystem around SAP.  A number of SAP's partners are producing mobile applications that only work if you buy their products.  There is nothing wrong with that strategy, but it does add confusion to companies interested in general SAP enterprise mobility.  Now there are at least four categories of mobile applications for SAP customers:
  1. MEAPs (mobile enterprise application platforms) - Enables the user to develop, customize and support many different mobile applications and mobile devices on one platform (e.g. Sybase, Sky Technologies, etc.).
  2. Mobile micro-applications - Lightweight mobile applications typically available from App stores that are specific to particular limited business processes in SAP (e.g. Vivido Labs, Leapfactor, etc.).
  3. Mobile solutions that are designed to work primarily with a specific vendor product (e.g. ClickSoftware, Syclo, Open Text, etc.).
  4. Out of the box mobile applications (email, calendars, etc.).
There may be more mobile application categories, so let me know which ones I missed.

I wonder how committed companies like Open Text are to mobility?  Are they serious, or are they just trying to excite an exciteable analyst?  Initially Open Text is only going to support BlackBerrys, but claims a long term commitment to supporting other mobile devices.  They plan to release applications that provide a comprehensive view of business processes, content and workplace social collaboration (as long as it involves their product).  Here is the list of mobile applications they are planning to develop:
  • Manage everywhere for documents and content.
  • Engage everywhere focusing on process workflows.
  • Collaboration everywhere using social media.
Although the product descriptions sound general, I expect they will only function with Open Text products.  That means SAP users who want these functions, that are not Open Text customers, will need to search for other mobile application vendors.

***************************************************
Kevin Benedict
Author of the report Enterprise Mobile Data Solutions, 2009
Mobile Strategy 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. I work with and have worked with many of the companies mentioned in my articles.
**************************************************

Mobile Expert Interview Series: EntryPoint’s Pete Martin

Pete Martin, the founder of EntryPoint Consulting worked for SAP for over five years. He managed field operations in his region which included sales and pre-sales. His consulting company, which was founded in 2003, resells SAP solutions to US based middle market companies and business units of the Fortune 1000. They focus on SAP CRM, an area where they have a lot of experience. Today mobility is a big issue for his customers.

Pete was involved in one of the first mobile SAP CRM implementations. It did not go well. Why?

  • SAP did not have a well defined interface for CRM at that time. There was about five different ways to interface with it and this caused confusion with all involved.
  • SAP did not have a strong mobility roadmap or good guidance at the time.
  • It was a case of you don't know what you don't know.
  • Broadband internet was not widely available and connection and synchronization speeds were slow.
  • The customer wanted to download huge price books and massive amounts of customer data which bogged down the system.
  • The client wanted to replicate their ERP on the mobile devices – not good.

After this first painful experience, Pete and his team stepped back and studied the mobility space for about three years. However, in 2009 they lost two SAP CRM sales because they did not have a strong mobile SAP CRM offering. This pain motivated them to jump back into researching good mobile solutions for SAP CRM. Pete says that now 100% of SAP CRM sales prospects are requesting mobile extensions. It is no longer an option. A mobilized version of SAP CRM is a requirement.

They looked at a lot of different MEAPs that worked with SAP. There were several things they wanted from a mobility partner:

  1. EntryPoint sells to medium and large companies. They need a solution that can scale from a few dozen users to a few thousand. They needed a partner that could support both of these markets and be priced to work in both.
  2. They looked for a mobile provider that had already successfully implemented mobile SAP CRM solutions at a large company. They wanted to see a full production environment already in place. The partner they chose already had a successful mobile SAP CRM implementation with one of the largest global CPG companies.
  3. They wanted a mobile provider that was not overly complex. They were looking for a simple and elegant architecture that was easy to implement and support.
  4. They wanted to partner with and learn one mobile solution that could be broadly implemented across many different business processes.
  5. They wanted a mobile provider that "partnered" well. Some mobile providers are large and small partners get overlooked. EntryPoint wanted a mobile partner that wanted them.

The end result was that EntryPoint Consulting selected SAP Partner, Sky Technologies as their mobile SAP CRM partner. They are now confident in telling customers they can have a mobilized CRM in 90 days.

Mobility is a big focus for EntryPoint Consulting in 2010. Why?

  • SAP customers are asking for mobile solutions and mobile extensions to their business processes.
  • Sales prospects are all asking for mobile extensions.
  • When EntryPoint Consulting promotes events around mobilizing SAP CRM they get BIG responses.
  • They lost two SAP CRM sales last year because they did not have a good mobile solution provider and plan in place.
  • SAP field sales is asking EntryPoint about their mobile solutions and plans. Pete wants a good answer.

I asked Pete what he thought about SAP's current mobility strategy and he said, "In markets where products and technologies are changing fast, it is hard for SAP to keep up. They are simply too big to be nimble. It is best for them to partner for mobile solutions today." In a follow up statement he added, "SAP's sales teams are still a bit confused by SAP's mobility strategy." It seems there is more to be done to evangelize SAP's mobility strategy and plans internally.

Pete also shared his thoughts on what SAP sales teams could learn from other CRM vendors. He said other vendors had learned how to sell to mid-level, line of business folks successfully. This according to Pete, is where CRM is sold. SAP sales teams are great at the C level sales process, but have historically been troubled when selling to the line of business. "If the VP of Sales can't connect to the CRM with his/her favorite mobile smartphone, the sale is lost," said Pete.

To read additional articles from the Mobile Expert Interview Series see below:

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

Kevin Benedict
Author of the report Enterprise Mobile Data Solutions, 2009
Mobile Strategy 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.utilizer.com/
http://mobileenterprisestrategies.blogspot.com/

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

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

Mobile Expert Interview Series: PriceWaterhouseCoopers' Ahmed El Adl, PhD

I had the privilege of interviewing PriceWaterhouseCoopers' Director of Enterprise Mobility Solutions, Dr. Ahmed El Adl a few days ago. He works out of PWC's Boston office and focuses on developing and expanding PWC's mobility practice. He is a big fan of this blog which instantly increased his credibility with me.

Ahmed worked for SAP in Waldorf from 1998-2002 and focused on SAP's CRM solutions. In fact he was involved in one of the very first mobility projects for SAP CRM. At that time SAP's architecture was simply not suited for mobility and it did not go well.

Ahmed said that a lesson learned from that first mobile SAP CRM experience was not to let sales and marketing completely drive design and engineering. The engineers developed everything that the marketing teams asked for, but the result was a mobile application that was far too big and heavy to work for customers.

Ahmed is a fan of SAP's current mobile strategy of working with many mobility partners. He believes SAP should slow down and focus on defining the mobile connectivity layer and open up their system for more nimble and innovative mobility partners to provide mobile applications. Mobility is evolving very fast and it is hard for a giant like SAP to effectively keep up. By opening up to mobility partners, SAP customers can get what they want now without waiting for SAP.Ahmed is the kind of consultant I would want to hire. He has experienced the good and bad of early mobility adoption and brings great wisdom to the table now.

Although Ahmed agrees with SAP's current strategy and likes what he sees from many of SAP's mobility partners, it doesn't mean he is satisfied. He believes Sybase, an SAP mobility partner, is good but complex, heavy and has too many different components and technology layers. He listed the numbers of technology layers that are involved in a Sybase/SAP integration and it was daunting.

He shared his thoughts on Sky Technologies, another SAP mobility partner. He thought their approach was interesting, but he was concerned that their "mobile SAP innerware" strategy would introduce challenges. He wondered how IT departments would accept a third party mobility solution being so closely embedded with SAP code? Would the benefits out weigh the risks for IT departments? Would they accept it, or avoid it?

He said he likes much of what he sees from SAP's mobility partners, however he is still cautious. In fact, he has recommended to some clients that they should go through a complete RFI process to determine for themselves which vendor has the best fit for them.

Ahmed believes that ultimately SAP customers will want a strong MEAP (mobile enterprise application platform) that they can standardize on, but for today mobile micro-apps can provide real value quickly. I was particularly interested in this statement as it aligns with many of the comments that other industry experts shared on the SAP Enterprise Mobility group on Linkedin.

Ahmed identified several areas of mobility that he finds particularly interesting:

  1. Telemedicine
  2. Medical diagnostics that feed data to iPhone applications (e.g. EKGs, x-rays)
  3. The Apple iTune model for app stores that allows small companies to compete against the big software companies.
  4. He loves the idea of unlimited innovation, on a level playing field, and that one person software companies can help large enterprises increase productivity.

I asked Ahmed what mobile device or smartphone does he carry. He said all of them. He carries a PWC issued Blackberry in his pocket, but he literally travels with a suitcase full of different mobile devices that he can show off and demonstrate to clients. What a nightmare for the TSA agents! Don't get in line behind him.

I want to again thank Dr. Ahmed El Adl for his time and willingness to share his insights.

This article was the third in the series called Mobile Expert Interviews. See related articles:

***************************************************
Kevin Benedict
Author of the report Enterprise Mobile Data Solutions, 2009
Mobile Strategy 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. I work with and have worked with many of the companies mentioned in my articles.
**************************************************

Scrutinizing SAP’s Mobile Strategy from Managing Automation

On the website Managing Automation, http://www.managingautomation.com/maonline/ they have an article this week by Stephanie Neil called Scrutinizing SAP's Mobility Strategy. Here is an excerpt, "... a quick search (on the SAP EcoHub) for ‘mobile infrastructure’ brings up Sybase, Antenna Software’s Concert development platform, and SkyConnect from Sky Technologies... I question whether or not SAP needs the same broad base of partners in mobility as it does in manufacturing. Most manufacturers are just starting to implement a wireless strategy, and since it is untapped terrain for them, they may just want a turnkey solution from SAP, not a menu of choices."

This is an interesting perspective. Neil seems to suggests that many SAP users (at least in manufacturing) would prefer just one designated turnkey SAP MEAP (mobile enterprise application platform) and that having a plethora of partner selections is not necessarily useful. The challenge I have with Stephanie's comments is that I believe she underestimates the number of mobile applications and their complexity. Different mobile applications and mobile business processes require different workflows and expertise that may not all be present in one mobile software vendor. It will take a number of years before mobile applications support many of the more niche business processes which is why there is a need today for many industry experts to supply mobile applications.

Neil concludes with the following, "...SAP’s next move should be to acquire a mobile infrastructure vendor upon which it can build a stable of wireless applications that fit into its — and its customers' — long-term mobile enterprise plan. The company can continue co-innovating, but it needs to lead the effort. SAP has a rare opportunity right now to shape an emerging market."

I will dodge the acquisition issue, but I agree with Neil that SAP should take the lead. I believe SAP users would ultimately benefit from a standardized methodology for connecting mobile devices to SAP and managing these connections.

Thanks Stephanie for a thought provoking article.

If you are one of the plethora of mobile application vendors supporting SAP users, please make sure you add your solution to the SAP Enterprise Mobility directory so others can learn about you.

***************************************************
Author Kevin Benedict
Mobile Strategy Consultant, Mobile 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. I work with and have worked with many of the companies mentioned in my articles.
**************************************************

SAP Mobility Challenge, Part 6

Would you use Linkedin if you had to make a phone call and ask each person individually if they were using Linkedin before connecting to them? What if you had to manually program each connection yourself according to the mobile operating system and version each friend or contact was using? What if the programming was different for every mobile device? What if you had to re-program the connection every time a friend changed smartphones or upgraded their OS? The system would quickly cease to be a benefit and start being a big burden wouldn't it?

The value of Linkedin is that it automates and standardizes most processes and connection related issues. Everyone connects in standardized ways and uses pre-built processes to manage all of their connections, security, settings, etc. It is easy to view all of your contacts and manage these contacts from one screen. Enterprise mobility and the support of mobile devices needs these same kinds of concepts in place.

Enterprise mobility, like most IT systems, need standards that include defined methodologies and processes in order to manage it effectively and efficiently. If your company or client has hundreds or thousands of smartphones, handheld computers or other mobile devices using mobile applications, thick and thin clients, MEAPs and micro-applications, there is an absolute requirement for mobile device management. If they don't, it will be a big challenge now that will only get bigger.

In the same way that the IT department needs to record and manage all desktops, laptops and servers and the software licenses and security on each, they will need to do the same for mobile devices that are used outside the four walls of the enterprise.

How is it done today? Many companies allow their employees to select their own smartphones and expense them each month. The company has no visibility to the specific mobile devices, operating system versions or downloaded mobile micro applications until they receive a request to connect it to the ERP or other back office applications. At that point it becomes an SAP challenge.

Is this a challenge that should be addressed in SAP, or is this a challenge that SAP's mobility partners like Sybase, Sky Technologies, Syclo or ClickSoftware should address outside of SAP? There are experts that specialize on mobile device management like B2M Solutions. They focus on the complete mobile project life cycle and provide management tools for each component of this life cycle.

IT asset management, the IT help desk, IT support, IT security, etc., must all embrace mobile devices and enterprise mobility and quickly set-up their internal systems and processes to support them.

On the subject of IT help desk, this is my favorite funny YouTube video on help desks.

I would like to hear your thoughts on how your company or your customers manage mobile devices.

Related Articles:

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


***************************************************
Author Kevin Benedict
Mobile Strategy 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. I work with and have worked with many of the companies mentioned in my articles.
**************************************************

Interviews with Kevin Benedict