ENTERPRISE 11 - Mobiloitte Blog

3 Questions You Must Answer Before You Build Your Enterprise Mobility Strategy

Do you know that businesses of 1,000 employees estimate that a single hour of lost productivity due to a security breach could cost the company between $100,000 and $300,000 (Blackberry)? Does the ability to engage with your company through mobility create new opportunities for your business? If so, how can you capitalize on those opportunities.

The Enterprise Mobility (EM) environment is rapidly evolving, in terms of devices, operating systems, applications and content, which has seen EM capabilities develop in order to manage challenging boundaries between business and personal information. This is reflected in the incorporation of enterprise app stores, app wrapping and evolved MDM feature sets.

Subsequently there is an increased reliance on support and maintenance from EMM vendors and a focus on their ability to manage the full scope of business needs from basic MDM to fully regulated environments This resource intends to help your partner estimate the landscape and highlight the most important factors that will determine your selection of Enterprise mobility strategy and how to find the right vendor.

Which features can you get?

enterprise mobilityMake sure you make clear to your Enterprise mobility vendor about the feature scope you would require for your Enterprise mobility readiness. Are you searching for basic Mobile device management (MDM) features such as Device restrictions, require passcode, VPN, remote wipe, remote lock? Or instead you are interested in Enterprise Mobility Management rotating around all the basic  + Advanced Mobile Device Management (MDM) mobile application management and content management, versioning, rollback and containerization including:

  • Mobile device management (app white lists, black lists, policy setting)
  • Mobile application management app white lists, black lists, policy setting
  • Mobile email management (restricted access, disable forwarding options)
  • Mobile content management (FIPS-140 compliant 256-bit SSL encryption, location and time-based access, and printing restrictions)
  • Mobile secure workplace (VPNs wi-fi)

You may be needing Regulated-level EMM: EMM + compliance, control and advanced security (e.g. up to 100% lockdown) for government, defense agencies, financial services, healthcare, and other high security and regulated industries.

These feature sets can result in several Tiers of features, and one of them may be best choice for you at a particular point of time. To keep it simple we are going to present you 4 sample Tiers of features you can opt in from your Enterprise Mobility vendor (not all features are included in the sample Tiers):

  • Tier 1: Remote locking, remote wipe, VPN
  • Tier 2: Mobile Device Management, Workspace Container, App Catalogue
  • Tier 3: Mobile Device Management, Workspace Container, App Catalogue, Email Management
  • Tier 4: Mobile Device Management, Workspace Container, App Catalogue, Email Management, App Reputation Scanning, Secure Content Locker, Secure Browser

The scope of Enterprise Mobility management requirements is broad. It varies from basic mobility management needs, such as remote lock and wipe capabilities or password implementation, through to the complex integration requirements specified by regulated companies and government agencies that must adhere to the highest levels of compliance.

Making clear distinction between these various models will also ensure clearer financial landscape and ability to estimate costs easier.

What type of implementation you’d prefer?

We are talking about 2 main types of deployment models of Enterprise Mobility Management – On premise and on the Cloud. Answering this question will simultaneously give you a representation of the cost structure and the TCO (Total Cost of Ownership) and act accordingly. On premise or Self-Managed deployment would include hardware costs, software licenses and number of gateways.

Cloud based deployment will simplify the entire scope around implementation and cost estimation where you should only pay about the hosting charges impossed by your vendor.

Cloud based deployment model also imposes some concerns and manageability issues. For example, there may be a challenge with a company IT department’s ability to control and adapt the EMM offering for its users, and in the case of outages, IT is dependent on the vendor to repair the fault and reliant on the vendor’s support infrastructure.

What is the Number of devices and Operating systems you currently operate with?

Ensure that you have clear figures of the total number of devices which are going to be included in your Enterprise Mobility deployment because that will directly drive the hardware and the licensing costs and support and maintenance costs as well.

The proliferation of BYOD policy has imposed another concern regarding various mobile OS and various policies that need to be applied for each one of them which is especially a major concern with Android. Check your vendor’s rollout capabilities and ensure that platforms which are not supported by your vendors are highlighted in the model’s notes.

Why selecting a proper enterprise Mobility partner matters so much in the early stage of your enterprise Mobility transformation?  Because when there isn’t a consistent governance policy in place, the approach to mobility tends to become fragmented and siloed, with each department executing on its own strategy.

Mobiloitte has successfully established mobility roadmap and implemented Enterprise Mobility for Fortune 500 companies including Sandisk and Equinix. You could easily be the next enterprise to benefit from our model and experience in ensuring new mobile ways to empower your work team and delight your customers while securing sensitive data on the move.