Strategic consulting, technical professional and advisory services, to build and execute your mobility blueprint> read more
Mobility Management software automates BYOD and corporate liable programs for compliance, request management, and financial reconciliation> read more
Professionally managed scalable logistics, device imaging and end user activation support> read more
On demand user support for your mobile workforce, available globally 24/7> read more
Dedicated deep technical expertise in mobile security, MDM server setup, support and monitoring> read more
Expert audit and optimization service for total visibility and expense management> read more
The Court of Appeal in Cochran v. Schwan's Home Service stated:
"We hold that when employees must use their personal cellphones for work-related calls, Labor Code section 2802 requires the employer to reimburse them. Whether the employees have cellphone plans with unlimited minutes or limited minutes, the reimbursement owed is a reasonable percentage of their cellphone bills.” [Read the CIO article here]Despite my heavy consumption of Judge Judy and Law & Order (hotel room TBS), Vox’s legal counsel insisted I open with a disclaimer that I am in no way providing legal advice. K? That is out of the way… Here is how I view things: When I drive my car to work, I expect Vox to pay me for its use. Vox Mobile maintains a BYOD strategy and I expect them to pay me for using my device for business purposes. Conversely, they could always give me a car and a corporate phone (I’m open to discussing this car option further @KrisSnyder). What I feel happened here is that California told businesses to pay their employees a reasonable amount if they use their device for work. Not surprisingly, their mandate met with some resistance and it ended up in court. This isn’t complicated, I promise, but first I need to give you your new corporate BYOD plan. You’ve spent a year on it, but I can deliver it in 4 easy steps.
1) If you are using an MDM, employees have to agree to a full wipe of their personal device at any time.
2) Employees have to consent to the fact that their phone may be held for e-Discovery. This has not happened at your organization, ever, but if it does you will give them a “loaner” phone.
3) You will give them a stipend through payroll. If your finance team decides it is taxable, you will give them a higher amount to make up the difference. You will tier the amount: Voice Only, Data Only, Voice and Data.
4) Hourly Employees will not be given DataApply these rules and segment your user base. That’s it, your plan is complete! If you don’t want to take my advice, email me and I’ll come out and throw down all kinds of consulting for you and your CIO. Finally, buy Vox Choice, Now! [contact us] You’re undoubtedly skeptical so I’ll give you some reasons:
• When you try to run your BYOD stipend through T&E, you’re going to Fail. This strategy will add hundreds, or even thousands, of dollars’ worth of processing time, each month, to your program. Also, cost center managers and the finance team will begin cursing your name behind your back.
• You will invariably create a “simple form” for someone to sign and submit. I don’t have a lot of characters left so I will simply ask: Why did you stop doing that for laptops, licensing, pens, pencils and everything else you buy? (Answer: It doesn’t work).
• You will compile a really simple spreadsheet for finance, each month, detailing who to pay a stipend. EPIC Fail. I see so many organizations try this. So many problems: You are not informed when someone changes jobs and is no longer eligible. You forget who is allowed to have 1 connection, voice only, data only etc. and it turns into a management disaster. Some will even forget to check their MDM to see who is actually connected. Rita, that chic in marketing that always brings in doughnuts, will get paid every month for an iPad that hasn’t checked in on the MDM for over a year and a half!
• Time. This is simple. Your team has the time to do this. You already know that you don’t.This brings me back to Vox Choice. Vox Choice manages all of this for you, and more! It automates your corporate policy to prevent the request before it even starts. If the user is eligible, it routes for approval. Once approved, it will auto-provision into the MDM. Every month it checks who actually connected to the MDM and builds a payroll file. No longer eligible, no problem: it compiles a user feed every night. An employee exits? Boom – it wipes the device. “But I have a Hybrid environment!” No worries. Choice handles that too. Choice can accommodate split billing for features and rate plans. It slices, it dices and it can split hardware charges any way you can think of: upsize to bigger storage, ineligible replacement etc. In summary, California’s latest ruling on BYOD is not one of the 20,000 ways your everyday life could kill you. I over-simplified your plan, but you will inevitably fall into the traps I described if you choose to venture-forth alone. Implementing a BYOD strategy is a difficult journey and, without guidance, could fail miserably. However, once you have your strategy, Vox Choice can automate your regulatory adherence and compliance, including the details specified in this ruling.
1.) Outline a formal acceptable use policy. The first step organizations can take to reduce BYOD risks is to create an acceptable use policy, often referred to as a mobile policy. The policy should provide rules and protocols that govern BYOD deployment company-wide, setting standards for users. IT managers can take the lead by kicking off stakeholder discussions about BYOD rules now and into the future and designating a committee to promote and control mobile policy. It’s a good idea to require program participants to review the company’s mobile policy and acknowledge that they’ll abide by it via a signature.
2.) Identify users and create program participant segments. A crucial step in developing the organizational policy is to define BYOD users and identify various categories of program participants. This exercise gives the mobile policy committee the opportunity to think about any device type restrictions that may be needed, application restrictions and content issues. It also provides an opportunity for committee members to think through the financial implications of establishing a formal BYOD program, including user stipends or business expense rules applicable to employee devices.
3.) Select and deploy an enterprise mobility management platform. After the mobile policy is in place, committee members should assess their options and choose an enterprise mobility platform, keeping in mind their current technology and security needs and planning for future requirements. With technology evolving rapidly and employees choosing their own devices, it’s critical to think ahead and select a platform that can accommodate emerging technologies while keeping up with user demand and protecting corporate assets. The platform should feature strong network access controls.
4.) Plan to provide support for user-owned devices. Some company policy-makers mistakenly believe that BYOD means they no longer need to provide device support. This is a mistake that can lead to security breaches and decrease employee job satisfaction. Instead, companies should develop support protocols to manage all phases of BYOD, from device procurement and provisioning through decommissioning. By providing support and helping employees manage assets, technical professionals will gain valuable opportunities to ensure BYOD policies are followed, identify emerging vulnerabilities and help employees comply with safe practices.From an enterprise IT perspective, BYOD is one of the most significant workforce technology trends ever. That means it’s absolutely essential to manage it proactively. By establishing a formal acceptable use policy, identifying policy decision-makers and user groups, selecting a management platform and providing ongoing support, IT professionals can maximize the benefits of BYOD and minimize the risks.
- Best Practice: Short articles on best practices as gleaned from our consulting group, Vox Architect, and from our R&D teams working on various technologies.
- Webinar Abstracts: We produce a number of web events and recorded presentations, usually lasting between 30 and 60 minutes. The abstracts will give you a better sense of what is covered in the full event so you can decide whether it is the right resource for you.
- New Products: Overviews of new products that may be of interest to our clients, including hardware, systems, apps, and services
- Tutorials: Step-by-step instructions on technical or policy concerns that require some attention
- White paper Abstracts: We will provide some of the key take-aways and the most interesting info graphics from our research and reporting so you can find the right white papers more easily and so those with short attention spans can learn a few things
- Mobile Thought Leaders surveys and results: The Mobile Thought Leaders program (MTL) is helping hundreds of organizations fro around the globe to share their stories, insights and concerns about enterprise mobility. Throughout the year, MTL sponsors market and technology research projects. We will use the blog as one of the many places you can keep up with the opportunities to participate or access MTL research.
- Event recaps: Not everyone can attend all the industry events, like Mobile World Congress, AirWatch Connect, Gartner Symposium, to name a few. As our team members take part in these events, they will attempt to bring back some notes on the experience, the themes and the lessons learned.
As I said, the list of materials and information is extensive, but we see this kind of information sharing as a critical part of our mission:
We empower our clients to achieve their business vision through Complete Enterprise Mobility. [learn more]I look forward to sharing with you and welcome your thoughts and feedback.