Integrate mobile device management and UC system and functions

Most enterprises want to create a unified communication UC system to replace a variety of voice, email, video, instant messaging IM), Short Message Service SMS) and their employees are using social networks. However, the goal of this unified communication and collaboration UC/UCC seems to be in conflict with BYOD mobile device management.

Most enterprises cannot standardize mobile devices. Employees are used to using their own personal devices and always switch back and forth between the devices provided by the company and their own devices. In addition to practicality, BYOD also brings personal support, compliance, and security issues to the IT department.

Now the question is, can mobile devices have a wide variety of unique communication services and interfaces that can be integrated into a unified enterprise communication system that requires consistency? How can enterprises achieve this?

Create a mobile device matrix to coordinate the UC system and BYOD policy

The first step for an enterprise to deploy a unified communication policy is to determine what mobile devices the UC supplier currently supports, what UC functions are supported, and how they are supported. Not only are communication tools on tablets and smartphones different, but the functions available on the software platform may also be different. In practical applications, most large enterprises need to use Apple, Android, and RIM Blackberry products. Some employees even use other devices.

Next, IT enterprises need to create a matrix to classify their currently supported mobile devices, comment on the support of each device for voice, video, email, IM/SMS, and other special collaboration tools such as online whiteboards.

Most enterprises find that some UC functions in their existing UC products cannot be used on users' mobile devices. For example, if there are no special software or accessories, it is difficult for a tablet to use for voice calls. Although most devices can use key functions of the UC system through appropriate accessories or applications, there will always be speech and video tools not supported by mainstream UC products.

Enterprises need to be able to require BYOD users to add components to their devices so that they comply with the company's communication standards, just as they want them to meet security and compliance requirements. In turn, employees need to make some choices if the component is unavailable.

Build a BYOD compatibility and UC Function Matrix from scratch

When the conflict between the BYOD policy and the current UC system cannot be resolved, or if the company does not have a UC policy, you can create a matrix of identical devices and UC functions for each UC platform under consideration, this will help the company select the right product. In general, it is best to avoid setting specific mobile device guidance. The simplest way is to use standard interfaces and protocols to ensure compatibility.

In the UC selection Matrix, the impact of BYOD compatibility on it depends on how many employees carry their own devices and whether the enterprise can limit the growth of such devices.

If BYOD is limited to a relatively small number of employees, IT can control its growth rate. If a large number of employees bring their own devices to the company, enterprises must take necessary measures to ensure that the development of the mobile device market will not bring more trouble to enterprises.

In enterprises driven by BYOD requirements, UC needs to be integrated into mobile device functions. In this case, enterprises need to consider accessing the hosted UC system through a browser, rather than relying on software installed on the device for access. Browser-based systems can be well used for collaborative whiteboards, e-mails, and instant messaging tools. However, for voice and video, plug-ins or tools will need to be installed, this may cause problems to some devices. Because smartphones generally use standard mobile voice services, they can generally be integrated into a speech UC system that supports any PSTN device. However, tablets often require a compatible VoIP client, even for browser-based UC systems.

Participation of mobile users

The last question to consider when integrating UC and BYOD policies is to what extent mobile device users really want to participate in UC. Although companies generally want UC support on any mobile device, they also believe that the drive to extend UC to BYOD comes from future use, rather than the current demand. UC vendors are developing their own BYOD support functions. So, if there is no demand at present, it is best to wait for a better BYOD-UC integration solution.