Enterprise Mobility Management

Transcription

1 Enterprise Mobility Management This is the second market overview report from 451 Research s Enterprise Mobility Management (EMM) Market Monitor service. We define EMM as a set of tools that include mobile device management, mobile application management, mobile application platforms, mobile containers, mobile back-end as a service and mobile virtualization. These tools can be used solo, in parallel or in a tiered fashion across a mobile environment. We see these as one of the most important toolsets adopted by the enterprise, and as critical enablers of future mobile computing. This report leverages 451 Research s deep knowledge of and relationships within the EMM market, resulting in a proprietary forecast based on a bottom-up analysis of 120 vendors current revenue and growth expectations through This analysis was developed and will be maintained with the support of our qualitative Enterprise Mobility analysts, primarily Chris Hazelton, Research Director, Chris Marsh, Principal Analyst and Raúl Castañón-Martínez, Senior Analyst. Included in the report is our EMM taxonomy, market-sector revenue estimates, growth forecasts and a view of the competitive landscape for each of the sectors outlined above. Greg Zwakman, Research Director, Quantitative Services Kathleen Frodyma, Research Associate, Quantitative Services

2 Table of Methodology Data Sources Enterprise Mobility Management Market Taxonomy Enterprise Mobility Management Sector Definitions Enterprise Mobility Management Sector Definitions EMM Vendor Participation by Sector (A-C) Vendor Revenue Distribution (Ownership) Vendor Revenue Distribution (Range) Vendor Revenue Distribution (Range Cont.) Vendor List by Total EMM Revenue Range Vendor List by Total EMM Revenue Range (cont.) EMM Vendor Distribution Summary EMM Vendor Participation by Sector (C-K) EMM Market Drivers (+) and Challenges (-) EMM Vendor Participation by Sector (K-P) EMM Vendor Participation by Sector (P-Z) Total EMM Market Revenue EMM Segment Revenue EMM Growth Expectations by Segment EMM: M&A Activity (3 Slides) Total Mobile Device Management Market MDM Vendor Distribution (Public/Private) MDM Vendor Distribution by Revenue Range MDM Vendor Distribution (Cont.) EMM Market Share Analysis

3 Table of Total Mobile Application Management Market MAM Vendor Distribution (Public/Private) MAM Vendor Distribution by Revenue Range MAM Vendor Distribution (Cont.) Total Mobile Application Platform (MAP) Market MAP Vendor Distribution (Public/Private) MAP Vendor Distribution by Revenue Range MAP Vendor Distribution (Cont.) Total Mobile Container (MEC) Market Total Mobile Back-end as a Service (MBaaS) Market MBaaS Vendor Distribution (Public/Private) MBaaS Vendor Distribution by Revenue Range MBaaS Vendor Distribution MV Market Highlights MV Vendor Distribution (Public/Private) MV Vendor Distribution by Revenue Range MV Vendor Distribution EMM Summary Data MEC Vendor Distribution (Public/Private) MEC Vendor Distribution by Revenue Range MEC Vendor Distribution (Cont.)

4 Methodology Market Monitor s Bottom-Up Approach 120 Vendors included in analysis are estimated and forecasted individually Our Enterprise Mobility Management database contains individual models on 120 vendors in the market. Each model contains intelligence specific to that company (i.e., customers, pricing, deal sizes and trends) with a forecast that incorporates the unique traits, strengths and weaknesses of the vendor. 100% Of market estimate and forecast based on individual vendor estimates, no blackbox other category A bottom-up analysis entails creating individual estimates and forecasts for each market participant in lieu of relying on historical or related data, applying broad assumptions or extrapolating market totals based on input from a handful of large vendors (a top-down approach). 8 out of 10 Vendors we have briefed directly to support our findings This analysis leverages our deep knowledge of and relationships within the enterprise mobility management marketplace, resulting in proprietary forecast of industry revenue based on a bottom-up analysis of each vendor s current revenue and growth expectations.

5 Market Monitor Data Sources 15, CXO Vendor briefings as a company annually Sector analysts support estimates Financial analysts contribute to MM Financial/banking clients provide insight Executive-level access across IT landscape 18 End-user surveys annually

6 Enterprise Mobility Management Market Taxonomy We define EMM as a set of tools that include mobile device management, mobile application management, secure container applications, mobile application platforms and mobile virtualization. These tools can be used solo, in parallel or in a tiered fashion across a mobile environment. We see these as one of the most important toolsets adopted by the enterprise, and as critical enablers of future mobile computing. Mobile Device Management Mobile Application Management EMM Mobile Application Platform Mobile Container Mobile Back-end-as-a-Service Mobile Virtualization

7 Enterprise Mobility Management Sector Definitions Mobile device management Mobile device management leverages an installed client on the device as well as APIs to provision, manage and de-provision mobile devices over the air. Helping to drive its adoption in the enterprise, MDM generally supports more than one mobile OS in order to be relevant to IT departments that are increasingly unable to prescribe or standardize on one mobile platform. MDM allows IT to on-board large populations of devices by pushing the client or a profile to the device via , SMS or a company website. Devices can also be shipped preconfigured for MDM. Mobile application management Mobile application management focuses on providing detailed control of enterprise applications. Basic levels of MAM functionality include app catalogs, provisioning and update management. Custom, in-house or third-party applications can be recompiled by the developer with a software development kit (SDK). An alternative approach is for an IT admin to wrap custom, in-house or third-party applications with a management layer. Mobile application platforms Mobile application platforms are used by businesses to develop, deploy and manage mobile applications. They typically provide access to an IDE and other development tools, connections to mobile-ready back-end services such as messaging, file sync and sharing, data storage, authentication and identity management, push notifications, and location-based services. They also typically offer dashboard reporting and some level of user and application analytics. MAPs may offer their own EMM capabilities, but are also increasingly interoperating with EMM providers offerings.

8 Enterprise Mobility Management Sector Definitions (cont.) Mobile containers Mobile back-end as a service (MBaaS) Mobile virtualization Container-based applications provide users with an encrypted app that offers a secure messaging and personal information management (PIM) service and in some cases, a separate environment for mobile apps. These secure containers can provide a third-party client that is encrypted and separate from the native client on the device, which can be provisioned and de-provisioned over the air by IT admins. MBaaS is defined in a way that closely mirrors 451 Research s definition of PaaS, except that it is designed for a mobile app developer s requirements. MBaaS provides the connection between an app and a data source, and provides the back-end services like push and storage to integrate into the app. Some of the common features provided by MBaaS vendors include push notifications, object upload and storage, Facebook/Twitter integration, geolocation, authentication and in-app payments. Mobile virtualization comes in two variants on smartphones and tablets either a Type 1 or Type 2 hypervisor can be used. Type 1 hypervisors, also known as bare-metal hypervisors, are integrated into a device s firmware. Type 2 hypervisors, also known as guest operating systems, are virtualized software stacks that reside on top of the device s OS. The market is tipping toward Type 2 hypervisors, but at this stage, there have been few major product launches that would point to one model winning out over the other. Similar to containers, mobile virtualization provides a second environment (also called a persona) that adds a separate software stack, which can also include a separate cellular voice application effectively mirroring the entire device using a guest mobile OS. All data and applications are siloed from the consumer side of the device, providing strong data-loss prevention. The challenge here lies in signing up device vendors to support the use of hypervisors on Android devices.

9 Greg Zwakman Tim Miller Yulitza Peraza Victoria Simons x x x x155 Kathleen Frodyma x168 Or