A picture is worth 1000 words, so check out this video for how we have arrested cost for other users:
The Bill Police: Protecting Your Wireless Rights since 2003
Corporate Wireless is a headache to manage. We fix that.
A picture is worth 1000 words, so check out this video for how we have arrested cost for other users:
Protect your wireless devices from HIGH OVERAGES! Remember to set up your Alert Notifications from your Carrier’s websites!
A recent Bill Police study has uncovered that we saved an average of $1500 per alert notification for our customers!
Carriers websites allow you to receive notifications for users that are spending $200 over their limit for data. These alerts include notification for:
Think of the cash you could pocket –you’ll have to put on a cape of your own!
STILL protecting your rights……..
So now that we have defined what Mobile Device Management (MDM) IS, let’s define what it IS NOT.
MDM is…..
While all are key factors, I will discuss the first two in detail as they are the most important key factors in my mind and they are the most often misunderstood.
The Enterprise needs a Mobility Policy, that is an Operational statement of what can be done with a mobile device, who should be able to conduct certain procedures and how these procedures will occur. All users need to be set up and rules for which applications will be allowed need to be determined. For example if you don’t want users to have Facebook on their corporate device, this needs to be delineated and then managed as part of MDM user protocols.
The following are just a few of the things needing to be considered for MDM management profiles and user policies:
None of this is just done by MDM, MDM simply implements what you tell it to do after you set up the process for it to do it.
Fie on those MDM providers touting they are a WEM solution. Let’s review: MDM costs you money to implement, WEM saves you money to implement.
Although these two solutions can be combined to help enterprises in the long run avoid costs, MDM on its own does NOT help reduce your wireless expense. WEM, on the other hand, as a fully managed solution reduces your bills without the enterprise having to do anything except approve changes.
Let’s take one example of what happens with MDM when changes need to happen:
Now lets take a look at the same example when done with a WEM provider:
You can get all the alerts necessary to make the enterprise AWARE of potential issues, but if no one in the organization actually makes the change, the result is not a good one (also, again, back to point 1, MDM is NOT a MANAGED SOLUTION).
On the other hand, WEM is a managed solution and inherently takes the additional steps required in order to save money. MDM providers can tout money savings all they want, but unless someone is managing the plans, the enterprise will end up paying more.
Craig Mathias writes several great points on MDM and expense management in his November 2011 Information week article. He says:
“…tracking of how money is being spent on network access is vital. It’s important that this be as close to real-time as possible in order to spot negative trends before they become a big hit to the bottom line. And policy enforcement via software would also be nice–there’s no point in racking up cellular minutes when, for example, a lower-cost Wi-Fi option is available.”
I’ve proposed the term Mobile Operations Management (MOM) as the all-inclusive catch-phrase for describing all of the elements required for a successful enterprise mobility implementation–successful being defined as secure, cost-effective, appropriate, visible, enabling, and manageable. But no matter what we call all of this, enterprises everywhere need to think about strategy, and not just assume that an MDM solution (again, whatever that is) is all that’s required”.
Gartner when referring to what MDM is NOT says, “While IT organizations vary in their approaches to implementing and owning the tools that manage mobile devices (e.g., the messaging group, some other mobile group, the desktop group, etc.), there are still very few that are managing the full life cycle across multiple device platforms.
This idea of wireless management is key. MDM is piece of the pie, and it could be a very helpful piece, but it is only a piece; don’t be misled by trying to keep up with the joneses on the latest and greatest. It is likely not the right plan, right price nor right result.
In order to fully grasp what MDM actually does, it’s helpful to understand exactly what MDM is.
Mobile device management allows administrators to oversee the function of wireless devices via software downloaded to the device Over The Air (OTA). This means that MDM providers have mobile devices secure their software over the air (OTA) from an application that is downloaded to the device.
The software then can add certain allowable softwares (like allow windows, don’t allow Facebook) and
then provides information about that device (NOTE: not about its billing nor about how best to allocate
or spend cost, but about the device itself: it is on, what is the battery life, security, etc.)
Wikipedia states, “The ideal mobile device management tool:
Below are some of the functionalities of MDM:
Gartner, in their most recent “Magic Quandrant” rating on MDM included the following criteria to select
their top MDM providers:
Security management, with at least these features:
Software distribution, with at least these capabilities supported:
Inventory management, with at least these capabilities supported:
Given the large number of players in this market and the complexity of the products, we have chosen to restrict this analysis to a subset of vendors whose offerings get the most interest and highest level of inquiries from Gartner’s clients.
What you get for your money – an important factor to consider.
One major area of differentiation among MDM offerings is the technical approach to management. The industry is divided into 3 delivery modalities:
While many products are on-premises, a growing number of cloud services offerings are starting to appeal to users because they are more economical. The option provides fewer up- front costs due to no purchases of software and allows more flexibility to scale up services with growing mobility adoption or needs. However, many providers do require both an activation fee, potential maintenance fee and set-up fees. Make sure you understand what you are paying and what it gets you and the organization!
Gartner also adds the following about server vs client-side offerings:
Server-side product or service offerings These offerings may have a small mobile agent running on the device, and/or call native APIs provided by the mobile OS platform (e.g., iOS 4), but do not have a complete mobile management client. They can enforce policies on the server side, but cannot control the device and mobile user behavior in depth. They are used in combination with native mobile support in corporate email servers (e.g., Microsoft Exchange ActiveSync [EAS] in Microsoft Exchange Server or Notes Traveler in Lotus Notes/Domino) to enforce complementary policies to those provided by the server. Thus, they can preserve the native email client experience on iPhones and iPads, which are favorite choices for users.
Client-side offerings Management software is available for every relevant mobile OS platform (either stand-alone or blended with a proprietary email client). The management client can enforce strong IT control on the device (e.g., local data encryption, selective wipe and containerization). Actually, it replaces it, and it does not work with the device’s native email client, but requires its own client, which can only connect to a corporate email server. Good Technology’s approach prioritizes on IT control, limiting the user’s choice and experience with the email client.
The following vendors have been examined when reviewing the marketplace:
AirWatch, BoxTone, Excitor, Fiberlink, FancyFon, Good Technology, Mobile Active Defense, McAfee, MobileIron,Sybase, Symantec, Tangoe and Zenprise. Vendors not included in this research are still valid options for consideration (see “Magic Quadrant for Mobile Device Management Software” for details), including: Capricode, Fixmo, IBELEM, Fromdistance, Motorola, Odyssey Software, Smith Micro Software, SOTI, The Institution and Ubitexx (acquired by RIM).
While most vendors specialize in management for smartphones and tablets, a subset provides specific capabilities to manage fleets of ruggedized devices (on Windows CE or Windows Mobile), including SOTI, Odyssey Software and Motorola. We do not consider these vendors in a separate use case because specialized management tools for ruggedized devices generate limited Gartner client inquiries.
You can find the entire Gartner study by clicking here.
First, take a look at PART II – MDM: What it is NOT (COMING SOON). This will help shed some light on what to expect and how YOU will really need to heavily interact with these programs and solutions to indeed see concrete results.
Second, make sure you know and identify IT policies required to control deployments, manage risks and support users.
Third, make sure you understand how to marry the product and your needs to make any of these products useful to your organization and that it will indeed produce RESULTS, not just more work for you at increased rates.
Here’s a great article by Phillip Redman posted on Gartner Inc’s blog, in which he explains that it’s a good idea for enterprises to support multiple devices and operating systems, since as he puts, “…in reality, there is no alternative.” Here’s the entire article (or click the link in the previous sentence to view the original). Great insight Phillip!
by Phillip Redman – June 14, 2010
Last week I spent a lot of time with user clients going over some of their main business issues relating to mobile networks and the enterprise. At each meeting, the most burning question was not related specifically to technology, but how to manage the ever expanding number of mobile and wireless platforms and services. In the past year, in North America, U.S. businesses have seen an influx of devices, especially the iPhone. iPhone, though not a corporate standard is a mile wide, but an inch deep at U.S. companies. But adoption is growing and iOS4, and the ability to manage it better will only increase the pressure CIOs feel to support this platform. BlackBerry, the ultimate managed device, is under attack from at least two fronts–iPhone and later this year Android platforms. And decreasing BlackBerry marketshare in smartphones only proves the point (see: Market Share: Mobile Devices and Smartphones by Region and Country, 1Q10). Though the vast majority of companies want to support multiple platforms and service adoption strategies, they are struggling with policy and best practices.
I believe it makes sense for most companies to support a diversity of devices, since in reality, there is no alternative. No standard OS means no standard device. But it is key to create a framework of support and define the IT and user requirements for devices and platforms. Companies should review our managed diversity framework for guidance on this (see: Use Managed Diversity to Support Endpoint Devices, May 2010). Most companies should continue to support corporate liability in order to retain control over security, costs and the future direction of mobility in the enterprise (see: Companies Should Keep Control of Cellular Users Through Corporate Liability, January 2010) and develop policy that helps guide users and the company in supporting mobility.
The good news, there is an ever expanding set of enterprise tools and services to help companies manage mobility. As service price continues to decline, as device and network capability continues to increase–it is inevitable that for many business users, the mobile device will become the primary communications tool, if it hasn’t already. Now is the time to acknowledge and manage it.
U.S. Patent Numbers 7,486,944 & 7,986,936, Confidential and Proprietary, ©Copyright 2024 The Bill Police Inc., All rights reserved