Discussion on:
View:
Show:
It is generally considered bad practice to use an acronym without spelling it out on first reference. It is fine in the headline for brevity, but every communications professional I know says to always spell it out on first reference. The fact that I know BYOD means Bring Your Own Device is irrelevant if I have to think about it for a second or if I'm new to the industry and don't know the jargon. If I happen across your website as a curious outsider I shouldn't have to use context clues or search for an acronym to figure out what it means. You guys seem to do this a lot, and it would be incredibly helpful if you would just spell it out. Thanks!
I love the term 'wireless WiFi'. Is WiFi not wireless enough? What's next, ether-ethernet (transmitting network signals through a sweet, volitile liquid. needs Cat6 copper cabling, sulfuric acid and ethanol) 
Yep - I'm in that sort of mood again today
Yep - I'm in that sort of mood again today
Judging from the article, companies are providing employees with mobile devices on the job. This practice isn't any different than what one of my former employers did when providing us laptops. The same issues we faced then---security, access, etc.---apply to the mobile devices today. Good information for those unfamiliar with the subject matter, but nothing new here for this old timer.
It is not "BYOD". If Lowe's is rolling out 42,000 tablets, it has a major mobility project not a "BYOD" project and shouldn't be mentioned in such a short, hopefully focused report. Although both company-provided and employee-provided hardware have many of the same issues, much better control and security can be obtained by company-owned equipment. Employees always feel that if they own the equipment, they have the "right" to put games, porn, and anything else they want on "their" device. The company can have policies, but enforcement becomes an issue.
why so much discussion on the company monitoring the charges, rates, and fees? Are companies footing the connectivity bill for employees' personal devices?
Because you know that a lot of employees will say, "Hey, I'm using this to do work, so you should pay for my data plan." But -- rightly so -- the company has the right to come back and say, "Sure, we'll pay... for the portion you used to do work, not to watch episodes of Bones or CSI on Hulu Plus, or the Facebook/Twitter updates about how dry & brown your grass was...".
There's a big difference between corporate managing business-provided/sanctioned mobile devices, hence the Bring your own Business Device (BYOBD), verses attempting to manage a private individual mobile device (Bring Your Own Device, BYOD). Security, privacy, expense, and availability, need consideration for both the individual and the business sides and are all factors in how and what is allowed and who is responsible.
If you're the one that buys the device, brings it into work, & use it to do your work, it's BYOD (Bring Your Own Device).
If your employer providese you with the device to perform your work -- whether it's a traditional desktop PC or a mobile PC (laptop, tablet, smartphone, whatever) -- then it's a CPD (Corporate-Provided Device).
For the latter, it belongs to the employer, so the existing data/Internet policies (& the associated software controls) already apply to it, plus they're the ones paying for the data plan.
For the former, there's the dual expectation that a) what you do in your free time (i.e. "off the clock") is up to you, but b) what you do during work time ("on the clock") is subject to monitoring & control by the employer. If that means your smartphone has a constantly-running app that logs when you access non-work-related apps and websites, & reports when you're doing it while on the clock... then that's fine, because your employer is paying you to work, not to do non-work-related items. And it's no more invasive than, say, tracking a delivery driver's truck to make sure he's working his route & not "taking an extra long break" at the mall; or, for example, requiring a sales rep in the field to call into the office every time he finishes one client meeting & is leaving for the next. You're on the clock, so your time is your employer's money. You'd be upset if a contractor was billing you by the hour to replace a damaged roof, & you found him taking a 30-minute "smoke break" every hour to pad his chargeable time; don't expect employers to be any more lenient when it comes to employees and their "work".
If your employer providese you with the device to perform your work -- whether it's a traditional desktop PC or a mobile PC (laptop, tablet, smartphone, whatever) -- then it's a CPD (Corporate-Provided Device).
For the latter, it belongs to the employer, so the existing data/Internet policies (& the associated software controls) already apply to it, plus they're the ones paying for the data plan.
For the former, there's the dual expectation that a) what you do in your free time (i.e. "off the clock") is up to you, but b) what you do during work time ("on the clock") is subject to monitoring & control by the employer. If that means your smartphone has a constantly-running app that logs when you access non-work-related apps and websites, & reports when you're doing it while on the clock... then that's fine, because your employer is paying you to work, not to do non-work-related items. And it's no more invasive than, say, tracking a delivery driver's truck to make sure he's working his route & not "taking an extra long break" at the mall; or, for example, requiring a sales rep in the field to call into the office every time he finishes one client meeting & is leaving for the next. You're on the clock, so your time is your employer's money. You'd be upset if a contractor was billing you by the hour to replace a damaged roof, & you found him taking a 30-minute "smoke break" every hour to pad his chargeable time; don't expect employers to be any more lenient when it comes to employees and their "work".
BYOD may be ???Bring Your Own Device???, but the implication of the article is that this does not include ???Bring Your Own Network Service???. Remembering the difficulties we experienced even trying to hold a sensible conversation with the service provider of mobile phones, quite apart from achieving any sort of sensible outcome, I dread to think what joys will be in store when trying to achieve a satisfactory service and charging regime for the mix of facilities now being considered. Beware the standard telecomm provider strategy of charge a fortune for ill defined services and act stupid when challenged.
Isn't the point of BYOD to avoid having to provide mobile devices and plans to your user community? It would seem a successful BYOD program would be able to provide access to information and applications in a secured manner without having to manage the end device.
...already being commented upon, you can count on C-series' everywhere to fail to account for costs (time and labor) associated with:
1) completion of provisioning devices to corporate standards - it'll always be point and click, right?
2) Increased number of incidents and time of investigation surrounding those incidents (security and otherwise) as IT will not be able to count on standard configurations - at least until a body of knowledge is built up (which in turn relies on staff stability - I won't go there in this response).
Note that this is likely to have a nefarious impact on projects large and small and will likely be simply another source of project time and cost overruns.
In other words it is very likely that yet another impact to IT cost and time efficiencies will be overlooked and unaccounted-for by those in charge - and become another club to beat already-overloaded staff with.
1) completion of provisioning devices to corporate standards - it'll always be point and click, right?
2) Increased number of incidents and time of investigation surrounding those incidents (security and otherwise) as IT will not be able to count on standard configurations - at least until a body of knowledge is built up (which in turn relies on staff stability - I won't go there in this response).
Note that this is likely to have a nefarious impact on projects large and small and will likely be simply another source of project time and cost overruns.
In other words it is very likely that yet another impact to IT cost and time efficiencies will be overlooked and unaccounted-for by those in charge - and become another club to beat already-overloaded staff with.
"...IT will not be able to count on standard configurations - at least until a body of knowledge is built up (which in turn relies on staff stability..."
It also relies on hardware configuration stability. That's tough to maintain when individual users are changing devices every 18 - 24 months, when the hardware fleet as a whole isn't turning over on a regular or controlled schedule, and when IT doesn't know what models are coming in next.
It also relies on hardware configuration stability. That's tough to maintain when individual users are changing devices every 18 - 24 months, when the hardware fleet as a whole isn't turning over on a regular or controlled schedule, and when IT doesn't know what models are coming in next.
Any suggested words for such policies, perhaps couched along the lines of the ISO 27001 frame work, regarding use of BYOD in a corporate setting?
Thanks.
Thanks.
- Keyboard Shortcuts:
- Prev
- Next
- Toggle
