VDC Research: Enterprise & Government Mobility Market Blog

Growth of Enterprise Apps Ecosystem to Drive Tablet Adoption in 2012

Although 2011 was a big year for tablets with notable large deployments (e.g., American Airlines, SAP, and the Department of Veterans Affairs), the perception of tablets as a complementary/companion device remains. The aforementioned deployments are early evidence of potential this device class may offer to transform today’s enterprise.   The extended battery life, portability, and large screen size of tablets enable enhanced computing capacity and usability over the smartphone, while preserving the portability, connectivity, and long battery life appreciated by many smartphone users.  While tablet use and adoption has currently centered on the consumer market, we believe that the growing ecosystem of enterprise-class applications will drive tablets into the enterprise in 2012. We project that the global market for tablets will exceed 100M units by 2014 – while this pales in comparison to laptop penetration in the enterprise, it is significant growth.

Alongside the anticipated advantages these devices will enable for enterprise customers (i.e. in sales, business intelligence, or communication), companies such as IBM have begun to recognize the generous profit potential for companies best able to access this growing software market. Earlier this month, IBM expanded its suite of mobile offerings with the announcement of seven new mobile applications targeted at enterprise users.  These social networking apps cater to users of iPad and Android devices, offering software to facilitate capabilities ranging from instant messaging and reduced calling costs to management and attendance of online meetings. Salesforce.com’s anticipated Touch.salesforce.com (a tablet-optimized HTML5 mobile app) will also be impactful, as it will seamlessly enable users to access their Salesforce applications across tablet and smartphone platforms.

We expect that the market for tablet-optimized enterprise applications will experience substantial growth in 2012, led primarily by large ISVs and by innovative startups. As enterprises and IT organizations become more comfortable with mobile devices and tools, we expect to see tablets expand across the enterprise. This growth will spur further innovation and technological advances in software applications, driving new uses for this device in the enterprise.

The Changing Face of Mobile Health Care

The increasing capabilities delivered by mobile solutions are causing health care organizations to evaluate the role of mobility in their organization and their interactions with medical professionals and patients. Organizations are not only aligning their mobile initiatives with their overall strategies but they are also evaluating whether they have the necessary resources to develop mobile health care solutions internally or whether they need to look for outside help. As the adoption of mobile health care solutions accelerates, some of the primary questions health care organizations must answer include who they would like to target with their mobile applications (i.e. health care professionals or the patients), what kind of capabilities they would like their solutions to have, and what types of problems they envision solving.

Based on our end-user questionnaire that we fielded in Q2 2011, the primary business initiatives that impact mobile computing solution investments include improvements in process efficiencies and customer service and satisfaction. Given the busy work schedules of physicians, clinicians and nurses, they not only would like to access the necessary information/ records anytime anywhere but they would also like to be able to have portable mobile devices that allow data input at the bedside. For the past couple of years CIOs and IT departments at health care organizations have been struggling with health care professionals bringing their preferred devices to work and asking for support. Demand for robust mobile security solutions continues to rise, and the numerous regulatory issues that impact the health care industry make ensuring the safety of patient records critical. While the BYOD trend has been picking up fast in other industries, more and more health care organizations are implementing mobile policies to gain visibility and control over costs, compliance, and the operational impact of their mobile assets.

Likewise, organizations see an opportunity in adopting next generation mobile solutions as they believe that they will offer them a competitive advantage in attracting the best physicians and nurses. Thus, the availability of patient-facing mobile applications is helping organizations to improve their customer service capabilities, as patients are eager to use tools that will allow them to enter and track their key health information and have their health care provider alerted should conditions that require immediate attention arise. Additionally, many health care organizations (such as Mayo Clinic and Beth Israel Deaconess Medical Center) are extending their existing web sites and/or newsletter to enhance communications among their patient community. The capabilities of mobile applications have grown from tracking closest ER locations and wait times into allowing remote access to patient care, recording vital health care information and providing access to reference information all of which are speeding care delivery to patients. We see evidence that solution providers such as WebMD, Allscripts, Epic Systems and Epocrates are gaining traction with their mobile solutions both among patients and medical professionals.

Health care organizations are hoping to reach more patients and consumers while building awareness for conditions that could affect their health with mobility solutions. By investing in mobility solutions to improve customer service and satisfaction, health care organizations are hoping to engender loyalty, increase efficiencies and realize bottom line improvements. VDC believes that the increase in patient-health care professional communication and collaboration among health care providers can help in reaching these goals since demand for timely and high quality health care is on the rise.

More information on the developments in mobile health care solutions can be found in our EMOB 2011 Health Care Vertical Market Report that will be published next week.

Mobile Operators, Systems Integrators, and ISVs Changing Channels for MEAPs

Our good friends in Stamford Connecticut did a great job in identifying and classifying the vendors who have brought a mix of solutions to the market that can be summarized as "mobile enterprise application platforms" or MEAPs - the core/primary capabilities that have been established are:

Rapid Application Development Tools: Drag-and-drop WYSIWYG design tools (including emulators/debuggers) with robust cross-platform/device support

Management and Security: Client-side security features with enterprise-grade encryption - along with management capabilities that include - application deployments, updates, reporting/analytics and mobile policies

Application Integration: The ability to integrate with a variety of "back-ends" referring to not only databases, but web services, proprietary/legacy systems as most importantly enterprise application suites such as SAP, Oracle, Microsoft etc.

The above are now table stakes for MEAPs - similar to other mobility categories or segments the MEAP space is maturing rapidly - not only has consolidation begun, but channels are evolving. MEAP vendors capabilities that allow for HTML, CSS and Javascript to native development tools are powerful, but the capabilities must expand in order to  remain relevant and have the ability participate in larger portions of the continually expanding "enterprise mobility value chain" (more on this concept later). Below are the areas we see MEAPs quickly moving towards:

HTML5: As ratification inches along, trends like Webkit standardization and a burgeoning developer community that is hungry to experiment and capitalize on the mobile "web app" market opportunity that HTML5 bringsare helping to move HTML5 apps forward. Our view is that HTML5 apps are elegant and service a purpose, however we don't see them usurping/replacing native applications. HTML5 apps are emerging as an important and complimentary element to MEAP vendor offerings as moving forward we see customers requiring both native and HTML5 apps and having a multi-pronged app strategy (more on this concept in future blog posts) - this is part of the "long tail" concept that we outlined in our research last year.

b2e App Stores: While businesses are still in the early stages of formulating mobile strategies, we believe that once they are fully formed, business-to-employee (B2E) app stores will naturally and quickly become a ‘must have’ feature on corporate intranets and as native apps on mobile devices for organizations of all sizes. SAP/Sybase plans to release a significant number of native mobile applications (~30) in the coming months and their strategy makes it clear that they see managing applications as a required element to provide to their customers along with their other platform capabilities - other MEAP vendors see the opportunity as well, and have either already built b2e app store functionlity into their platform, or are preparing (or looking to partner) to provide their customers with this capability.

Mobile Banking: Mobile commerce and banking have arrived - NFC capability will be featured every modern mobile OS by the end of 2012 - MEAPs like Kony Solutions have made significant headway and have caught up quickly to competitors like Sybase, Antenna and Pyxis who have long focused on the financial services vertical.

Vertical Market and Application Integration Expertise: Human capital has long been recognized as indispensible and a key differentiator to enter into specific vertical markets with a cogent and credible marketing  campaign. MEAPs have been hiring key personnel to spearhead specific vertical market initiatives - our view is that these investments are currently and will continue to bear fruit. Integration (implementation) and application consulting expertise in areas such as SOA and web services will also be key as legacy applications will continue to be modernized as IT budgets begin to open up.

The Channel and Partnerships are Critical

The channel opportunity for MEAP vendors is significant; with the solutions well positioned for white label arrangements with vendors with well established customer bases (i.e., systems integrators and mobile operators). We have recently seen AT&T move in this direction - the company currently works  with four prominent MEAP vendors (Antenna Software, Pyxis Mobile, Spring Wireless and Kony Solutions). Recently AT&T began offering Pyxis' solutions via a managed service - this is evidence not only of maturing channels, but is strong evidence supporting the point that MEAPs need to expand their range of capabilities.

Another important trend is the activities of ISVs - SAP (via Sybase), Oracle, Microsoft and MicroStrategy (and others) have mobile application platforms as well - moving forward they will try take more ownership of their customers (both for control and profit). Finaly, we see carriers and integrators moving in this direction as well (Infosys and SK C&C are prime examples).

MEAP vendors have oppporunities in front of them to partner with a broad range of complimentary mobility oriented ISVs - while this has already begun in a meaningful way, there are potential partnerships that have yet to be recognized that we see as beneficial for MEAPs to see the market traction that they have yet to see.

We are in the final stages of our research on MEAPs and plan on publishing a comprehensive report on this segment later this month. If you want to talk MEAPs, ping me! I'm @eakleiner on Twitter.

Survey Says: Mobile Managed Services have Arrived

We fielded an end-user survey to IT professionals, and line-of-business managers this past April and captured some very interesting market trends, perceptions, and attitudes surrounding deploying and maintaining a mobile workforce — end-users in organizations both large (65% of >$1B in annual revenue respondents) and small (52% of <$1B in annual revenue respondents) clearly stated that they were "very interested" in outsourcing a broad range of enterprise-grade mobility solutions.

Looking more closely at this "suite" of mobility solutions we saw that it ecompasses everything from device management and security, to application development, integration, billing / expense management etc. — in fact, we asked respondents to rate each of the items in the graphic below as to their level of priority for inclusion in a mobile service delivery platform — each rated >7 on a 10 point scale where 10= Most important.

 

Our data also clearly showed that the key drivers behind this receptivity were as follows:

• Device proliferation ("bring your own tech")
• Lack of in-house skills to support mobile applications and platforms
• Simplifying the end-user experience and ensuring adoption
• High expectations for costs savings

Considering these trends, we see enterprise environments as ripe for the adoption mobile solutions as managed service. However, we do see the increasingly complex channel relationships and the number of vendors “behind the scenes” participating on mobile solutions as a challenge for mobile focused vendors moving forward. 

The post summarizes several of the findings from our upcoming Mobile Managed Services Report

IT Organizations Lack Confidence in Mobility Expertise

Our most recent mobile survey* indicated that IT organizations possess some of the required skills and expertise required to develop, customize and maintain mobile applications and platforms in-house—however, they rate themselves the lowest on this specific category relative to 11 other IT related services we queried on:

 
Mobile Managed Services

Our survey also found that there was very strong interest (across all industries, regions, and by company size) in procuring a broad range of enterprise mobility solutions on a pay-as-you-go basis via a managed services model (57% of respondents overall indicated they were "very interested" in such an offering). In addition to the high level of interest in adopting mobile solutions organizations have indicated, we see the continuing trend of employees bringing their personal devices into the workplace also impacting the pace of adoption. These factors along with the growing complexity of mobile solutions provides fertile ground to a broad range of mobility vendors—particularly given the fact that IT organizations have expressed a lack of confidence on their mobile capabilities.

While pre-packaged enterprise class "off-the-shelf" mobile applications have recently emerged, the need for customization persists—so too does the complexity in managing a fragmented device and OS landscape for IT organizations (we see IT orgs. being forced to manage at least two, and more likely three OSes moving forward). In addition to the resources required to support a mobile workforce, successful deployment, adoption (usage), and maintenance of mobile applications/platforms is also very challenging and costly, even for the most seasoned and well staffed IT orgs. Recogizing these trends, vendors are positioning themselves to offer a very comprehensive managed mobility "solution stack" that continues to expand and now includes elements that extend far beyond device management and security to areas such as custom mobile application development and design, integration, and ongoing support and maintenance.

We will be publishing our Enterprise Mobility Managed Services and Hosted Applications Report (Track 3 / Volume 2) later this month which will examine in detail the current trends, vendor and solution range of mobile managed services solutions, specifically:

• How vendors are positioning / differentiating from one another
• Enterprise perceptions and primary areas of interest for these types of services
• The requisite elements of mobile managed service offerings
• The cost savings that organizations are expecting from adopting a managed service approach to mobility

* VDC's mobile and wireless team fielded a survey to 155 end-users in April of 2011—the respondents were IT and LOB decision makers, and worked for organizations headquartered in North America and in Europe.

No Such Thing as "Late" in this Fast Moving Mobile Ecosystem - But the Stakes are High

The mobile ecosystem added more moving pieces this month with the release of two new OS platforms. Microsoft's long awaited Windows Phone 7 and HP's updated webOS 2.0 platforms have arrived. Both companies are actively expanding their carrier rosters/geographies. Whether Microsoft learned from its failure with its Kin, and if the Palm acquisition gives HP a vehicle to succeed in the Smartphone market remain to be seen–what is abundantly clear is that both of these heavyweights are deeply invested in the success of their new platform. While Apple, Google and RIM have captured significant market share, churn and competition between carriers (and the financial commitment) give both platforms an opportunity to not only participate, but to also gain new customers. The real "x-factor" is the applications–how important is the level of investment in applications a consumer has made on any given platform.

"Stickyness"

There has been a lot of discussion on app fatigue (meaning that an application's usage decreases over time). For example, while Foursquare, a popular application for "checking-in" to various venues continues to see it's user base ramp, the company must constantly be cautious of its users growing tired of the application. Today, in our view, the "stickyness" isn't there - particularly for the mobile applications aimed at consumers. So does the $50 I spent on mobile applications lock me in on a particular platform (as a consumer)? Maybe, for a certain amount of time, but it's a given that applications will continue to evolve and become more sophisticated and powerful devices will emerge and vie our attention / share of wallet–hence the opportunity for Microsoft and HP.

The Business Environment is Different

As the usage of mobile applications in enterprise environments continue to ramp and employees continue to bring their personal devices into the workplace, we see the equation around application "stickyness" being enitrely different in enterprise environments. When businesses make investments in mobile platforms, IT infrastructure, business process / workflow mapping and integration, they are making a commitment. By default, device management and security are mandatory in these environments, along with the ability to customize and upgrade applications. These investment levels and hardware (device) commitments translate into application "stickyness", as the pain involved in moving to new applications can be significant. Enterprises will always be challenged by application lifecycles, however growing tired/bored of the application isn't an option in these environments as the applications are integrated into corporate systems, and are required tools for conducting business.

The Challenge

So, while there is a window of opporuntity for both Microsoft and HP, the challenge will be to capitalize on the lack of app "stickyness" and to get software developers developing on thier respective platforms. Additionally, both will need to get carriers to promote their respective products. In aggregate, if I had to summarize all of the reviews/blogs I've read, I'd say that (generally) both platforms have received positive coverage. Indeed, both platforms are differentiated in terms of their UI, with very slick multi-tasking capability (Microsoft calls this "live tiles," HP calls it "stacking"). In terms of hardware, the current feature set for both platforms is comparable to the competition, and while both platforms seem to be off to a good start - many technology journalists are saying that Windows Phone 7 is Microsoft's "last chance" to be relevant and to compete against the likes of Google and Apple - they also knock both platforms for not having enough applications. While being "late" to a market can be a disadvantage, it definitely can work both ways - we'll be watching.

Do you agree/disagree? Please vote on our poll, we'd like to hear your comments on this topic as well!

Please select the response you mostly strongly agree with:

Let the Tablet Wars Begin...

RIM's much anticipated entry into the increasingly crowded tablet market was made official yesterday during the keynote at DevCon 2010, RIM's developer conference. The PlayBook aka "BlackPad" presents an interesting value proposition to core BlackBerry users - i.e. enterprise and government organizations - and delivers it in a package with some very compelling specifications. However, many questions and potential issues remain before the device is actually launched in Q1 2011. Let's explore a couple. 

The Device: The announced specs on this device speak for themselves. While I won't recast all of them I will touch on a couple of the more compelling. The 1Ghz dual-core processor (NVIDIA Tegra?) certainly packs a punch and should do well supporting some of the more processor intensive applications supported in the enterprise. While the decision NOT to offer a 3G/4G version at this juncture (more on that later) is interesting, the embedded WiFi radio will be very attractive for a variety of voice over WiFi and unified communications applications. At 7" RIM is making a statement - and perhaps taking on a bit of risk. Clearly other 7" devices have recently been introduced - most notably from Samsung - however, the tablet category (as it is currently defined) is centered around the 9.7" iPad. However, in the enterprise sector, VDC's research has indicated an opportunity/sweet spot at 7" - large and differentiated enough from smartphones and capable of supporting graphics-rich applications such as GIS while small enough to support a high degree of portability/mobility. A big question mark - given these robust features (Adobe Flash) - will clearly be battery life. 'Full shift' should be considered cost of entry. The lack of 3G/4G radio should help, however, it remains to be seen if that is attainable. 

The OS/platform: As widely speculated, the PlayBook OS will not be the recently released BlackBerry OS 6.0 but rather an OS (called BlackBerry Tablet OS) based on the recently acquired QNX (see comments about QNX from VDC's Embedded Practice here). The flexible application platform with support for WebKit/HTML-5, Adobe Flash Player 10.1, Adobe Mobile AIR, Adobe Reader, POSIX, OpenGL,
Java. For enterprise applications these will all be critical requirements. Lost amid the PlayBook fanfare was RIM's WebWorks announcements. With WebWorks, developers can build Web applications for BlackBerry leveraging HTML5, CSS, and JavaScipt. This could be a hugely critical differentiator for RIM, however, also potentially encroaches on some of the available cross-platform develop/compiler solutions. 

Connectivity: The lack of embedded 3G/4G options with the initial release (to be included in future versions) will not garner any favors with the carriers, however, will likely make the device more attractive from a management and security support perspective. The device OS can connect the the BlackBerry Enterprise Server (BES) software and will enable users to link - via Bluetooth - to users' BlackBerry smartphones. In this state the smartphone's content is viewable on the tablet, however, the content remains stored on the smartphone. According to RIM, this should address many enterprise IT department security concerns. However, this is not a smartphone companion device - nor should it be positioned primarily as one - and can also support standalone operation. 

The Timing: Initially expected in Q4 2010, the device will actually be first introduced in Q1 2011. There is two ways to look at this. In today's world of smartphones and tablets applications and the application eco-system are ultimately what distinguishes the 'haves' from the 'have nots'. To date, BlackBerry's application eco-system has left something to be desired. While BlackBerry's target market is not the broad consumer market and its litany of fart apps, VDC's recent mobile developer research has evidenced the broadening gap between Android and Apple's iOS and other mobile platforms. The PlayBook is a significant enough device - and the development platform and tools compelling enough - to shift much of the enterprise - and also broader mass market - development efforts back in BlackBerry's direction. In other words this provides sufficient enough time to seed the application market - RIM is working closely with partners IBM, SAP and Oracle on these efforts - so the device can hit the ground running once launched. On the flip side, the timing of the official ship date will likely coincide with the second generation iPad which could be a challenge to navigate. Moreover, does RIM really want to give its competitors over three months advance notice about its features and capabilities (and/or are they compelling enough for target users to wait several months before purchasing their tablet)?

The Target Market: With the iPad and other 'consumer' devices continuing to encroach RIM's core enterprise and government customer base, the PlayBook is designed to defend its turf. In other words road warriors, field workers, campus workers, etc. The browsing interface (along with Flash support) will also satisfy the mobile worker's appetite for a consumer-friendly experience (long absent from BlackBerry devices). Right now the target market is RIM's approximately 60M users. This is a good place to start. However, one issue that RIM has yet to effectively address - and is becoming an increasing issue - is that RIM does best in homogeneous environments. Outside of highly controlled/regulated industries this is increasingly NOT the norm. RIM needs to find a counter. 

With the PlayBook RIM has definitely hit the mark in terms of key features and capabilities. Clearly until the device is released and applications and user experiences can be evaluated much is left open to interpretation. However - and this perhaps cannot be said of other recent BlackBerry product announcements - with the PlayBook, and the accompanying services and development tools, RIM is committed to driving innovation and setting new standards when it comes to the enterprise and government mobility user experience. 

 

Cross Platform Compilers - Key Tools for Mobile Software Developers

A steady stream of smartphones have been released this summer, we've witnessed the release of several Android based phones (notably the HTC EVO, and Incredible), Apple's iPhone 4, Samsung's Wave, and expect RIM to release several new devices later this summer.  Meego, the merged effort of Intel's Moblin endeavor, and Nokia's Maemo operating system, and new devices based on HP's newly acquired WebOS will also be showing up on a broad range of hardware (tablets, smartphones, and printers in HP's case) later this summer or in late Q3 / early Q4 if things slip. Then of course, there is Microsoft (who can never be counted out), who failed with its Kin phone (a phone focused on "social", and targeted towards a young demographic), but whose long awaited Windows Phone 7 is rumored to be ahead of its scheduled October release date.  Even with this broad range of participants, there are many common demominators that these new devices share - the hardware feature sets are very similar, with variance happening on processor speeds, screen size, user interface, and megapixels to name a few.  Also par for the course for these releases, is updated OSes and SDKs (operating systems and software developer kits), and there's "the rub" ...

While mobility platform vendors such as Antenna Software, and Pyxis Mobile have been providing tools for their customers to seamlessly create native mobile applications (regardless of the mobile operating system(s) they use) - this capability is just a part of the broader solution sets they provide which include data synchronization and integration to enterprise applications.  However, a new class of vendors has emerged that focus solely on cross platform application development, and open the door to a massive population of web developers who may be interested in developing mobile applications, but are challenged by the fragmentation, and complexity of the smartphone market.

"Learning how to Play in Traffic" (Great line from the IBM's Mass Labs Launch back in June)

Only in the white hot mobility space can companies like startups Appcelerator ($6M in venture funding, and ~20 employees), and Rhomobile ($1M in funding, also with ~20 employees) have an impact, and appear on the radar of large mobility vendors as acquisition targets. These firms possess tools that enable traditional web developers to develop native applications using their "traditional" web development skills (HTML, CSS, and Javascript).  Mobile software developers must cope with the reality of an increasingly fragmented mobile device market, and "learn to play in traffic" - with cross platform compilers developers can reach a much broader audience of potential customers, and create native applications for the iPhone, BlackBerry, Windows Mobile, Symbian, and Android platforms (WebOS, Meego, and Windows Phone 7 support is in development).  While "write once, run many/everywhere" is possible, these vendors are also challenged with the steady releases of OS updates, SDKs, and screen size, UI and API variance - bottom line, these companies have made notable progress with their products, and have quickly become important players in the mobile ecosystem (incidentally, these aren't the only two).

Upcoming Research on Enterprise Mobility Applications & Mobile Software Development

VDC will be releasing two mobile software Reports later this month - the Reports will cover mobile application software/middleware, mobile software development, platform, and distribution trends.

Landscape Shift Looming

When the announcement of SAP's intent to acquire Sybase became public on May 12th, not only did the "Twitterverse" light up, a lot of participants in SAP's EcoHub (SAP’s online marketplace for vertical solutions) took notice.  SAP has achieved a "critical mass" of mobility partners with wide ranging technologies, industry expertise, and go-to-market strategies within their EcoHub — however, the acquisition of Sybase will inevitably lead to some changes.  Many of SAP's partners provide the marketplace with solutions that are very rich in functionality, and are adept at customizing applications for specific business cases; most importantly, many have deep expertise with specific vertical markets, and are focused on "established" mobile application areas such as sales and field force automation, and CRM (workflow oriented applications).  These companies are typically midsized, are expanding their geographical footprints, and are in the midst of a growth period.

EcoHub Flux?

There are mobility partners in SAP's EcoHub that have a limited number of customers, as they have recently launched their first apps (many of which are still in limited release).  This is a group to keep an eye on, as many of these companies are led by industry veterans with deep industry expertise and historic SAP connections.  To remain relevant, this group won't be able to rely on long-standing relations with SAP — they will have to possess the ability to deploy innovative applications that are complementary to SAP/Sybase.  They must be able to demonstrate that their solutions offer tangible ROI, a positive end-user experience, while solving their markets' mobility needs. Some will struggle to remain relevant if they are unable to get customer traction in the near term — others may see the need to adjust their strategy and offerings to better complement the new SAP/Sybase.

Mobile Developer?

There is major upside for mobile application developers — we are still in an early phases of extending enterprise applications to mobile devices; porting functionally rich, optimized, and customized applications that have been traditionally on desktops to mobile devices is next. Many disparate players are vying to be part of these solutions.

If you are involved in mobile software development and have not participated in our developer survey, please consider contributing to our research (link to survey).  If you have a colleague(s) that you feel would be qualified to take our survey we would welcome their participation as well.

Mobile Software Developer Perspectives Needed

VDC is conducting its annual survey of market trends in mobile software development.  If you are a mobile software developer we are asking for your help.  Please go to, or send others to, our end-user survey:

The research covers mobile OS, development platforms, tools, and environments. Your thoughts will improve our insights into the development community and help to influence next generation solutions.

Every respondent who completes the survey will receive:

• Entry into a prize drawing for one of five $100 Amazon.com gift certificates (drawing to be held June 7th, 2010)
• The executive summary of our survey findings once the data has been analyzed

Thank you in advance for your assistance.
 
Best Regards,
The VDC Enterprise Mobility Team