Wednesday, 20 March 2013

How to Save on BYOD Implementation

By Joseph B. Kappernick


There is no question that BYOD (bring your own device) has many benefits for businesses, especially if this is the only policy in place. Unfortunately, most organizations still provide company owned devices in addition to allowing individually owned devices. This mix of device ownership opens up the door for some big cost risks when you consider how BYOD will affect carrier contracts.

If you are in the majority, your business probably has both a BYOD policy and provides company-owned devices to certain employees. You can still benefit from BYOD cost savings if you fully understand you contractual agreements and know which aspects may negate any of these savings. Here are three common ways you can plan ahead and decrease your cost risks:

1. Don't give up your volume discounts

Most carriers will allow individual responsible users (IRUs) to sign up on your corporate rate plan and count towards the number of plan users. Simply tell any employees that use their own devices to use a corporate referral code when signing up for service. If you can get enough people to do this, the discounts could even exceed your current ones.

2. The effects of termination fees can be minimized

Most carrier contracts contain termination fees to keep companies from switching carriers. These fees can be highly detrimental to any potential BYOD cost savings when you decide to move large numbers of corporate responsible users (CRUs) to IRUs. Always plan ahead you can choose the best time to make your move and be prepared to counter any financial losses.

3. Be prepared for security costs

Unfortunately, individually owned devices require more security measures and governance to keep company information safe and monitor usage effectively. The costs associated with implementing these measures are often high, but also necessary. Be prepared to manage the additional costs by having a plan in place before you begin BYOD implementation.




About the Author:



No comments:

Post a Comment