Today we have a guest post from Sean Ryan.  Sean is a research analyst with IDC focused on mobile enterprise software.

Mobility as a Service (MaaS), may be another buzzword for the road, but there is a very real shift underway towards adoption of SaaS-based solutions for mobile devices. This includes SaaS-based solutions with mobile client add-ons, such as the case with Salesforce.com for the BlackBerry and the iPhone. It also includes SaaS-based mobile middleware platforms that extend multiple enterprise applications to mobile devices, as is the case with vendors like Antenna Software and Spring Wireless.

Many factors are contributing to the MaaS trend, but here are a few of the biggest drivers:

• The flexibility of enterprises to easily scale up and scale down users based on an on-demand subscription pricing model.
  
  
• The ability for enterprises to start small, in terms of number of users deployed and cash outlay, with certain apps and then grow them across the organization. This equates to being able to run a pilot on your own terms without time constraints or an obligation to purchase a set number of seats at a given time.
  
  
• A lightweight client can often be provisioned down to devices over-the-air (OTA).
  
  
• The challenges unique to mobile deployments -- e.g., limitations of wireless connectivity, limitations of small form factors, and the variety of smartphone Oses -- are a real headache for already overburdened IT departments to deal with, as they require different skill sets as well as different management and security tools. It is much easier to farm this out to a vendor that specializes in mobility.
  
  
• It is becoming very difficult for developers to keep up with the array of mobile OSes that are viable candidates for mobile workers -- i.e., BlackBerry OS, Windows Mobile, Symbian (Nokia 60, etc.), iPhone OS, Google Android, and Palm webOS. Combine this with the multiple versions for each OS along with different hardware reference designs, and the complexity is overwhelming unless the company takes a draconian approach to drastically limit the types of devices it will allow employees to use. Again, a vendor specializing in mobility can do a much better job of staying on top of a rapidly moving, complex space. In most cases, the near real-time updating of OS versions, bug fixes, etc., can be included in the service-level agreement (SLA).
  

While mobility as a service is not widely deployed today in large enterprises, it is expected to grow rapidly in the coming year.

A recent IDC survey of 309 IT and business professionals for large enterprises in the United States and the United Kingdom, responsible for enterprise mobility purchase decisions, found that only 9% of organizations have already embarked on a large-scale deployment of mobile SaaS-based solutions (see pie chart). However, the same respondents indicated a growing acceptance of this delivery model for extending enterprise applications to mobile devices. Almost 40% of organizations plan to deploy a SaaS-based mobile solution in the next 12-18 months. Another 19.7% have already done a pilot and plan to roll out a larger deployment in the next 12-18 months. Furthermore, 15.5% of organizations have no plans to roll out any aspect of mobile SaaS-based solutions in the next 12-18 months, with another 8.4% that did run a pilot but have no plans to roll the solution out to other employees.

Of course, this does not mean that all on-premises solutions will be displaced, as many organizations will likely run on-premises solutions for certain applications that may need to be more customized or strategic in nature, or deal with data that is very sensitive, particularly if it is in a highly regulated industry. But, overall, the advantages of a SaaS-based model for mobile deployments align well with the needs of mobile workers and the IT departments supporting them.