CSG WInter 2013 – Policy Session on BYOD

Short Discussion – BYOD
Susan Metros (USC), Steve Sather (Princeton), Joseph Shebatello (sp?) (USC)

On university campuses we always brought the devices we wanted – this is not new to us. A successful BYOD program is about supporting a campus community and allow them to use the tools that they feel make them most comfortable and productive.

“Mobility is pervasive, and devices are prolific” – Educause study.

In survey found that 90% of USC students own a smart phone.
Philosophy shifting from device management to data management.

Big fundamental shift right now on the administrative side – we’re going to have to pedal fast or risk looking really silly – e.g. procurement systems that don’t work on smart phones.

We have to think about how to secure the data because we no longer control the devices.

Students coming with 3 devices – smartphone, laptop, tablet. They come knowing how to collaborate with their peers, and then wonder why the official environments don’t support that level of interaction. Students used to come to universities to get access to advanced technology, now they come with technology that the faculty don’t know how to user.

BYOD offers the possibility of getting out of the end point hardware business – like labs, leasing, etc.

Companies are starting to give employees vouchers to purchase their own devices, and getting out of the hardware business.

In many cases the issue is support from vendor products. To some degree we can try to mitigate, but often you have to wait for vendor support. Some campuses are looking at formally requiring mobility support when picking vendors.

We should concentrate on what are the gaps between where we are and supporting any device. In admin space that may be support for different Java versions, security issues, policy issues.

Some discussion about how to manage and secure devices – at Stanford you have to register devices MAC address – starting to look at making people install a management framework (they wrote a iOS one themselves). Several schools are using or looking at management platforms. How do we get users to accept the responsibility that comes with bringing their own devices into the workplace?

There are issues with the fringes of the lifecycle – brand new devices cause us to scramble, and on the tail end we struggle with compatibility issues that lead to uncomfortable conversations.

We should look at why people need to download sensitive information onto a device in the first place? What don’t our systems do that require that? Particularly a problem in the cloud – native apps for Google apps, for example, have a long authentication window, so anyone who grabs the phone can have access to the Google docs.

Students are still using computer labs, as a group study space. Some don’t want to carry their computers on campus, so use loaners in libraries. Will people be carrying tablets? USC Med School created big pockets in their lab coats to fit iPads.

If you’re using responsive design, then a large part of the problem becomes browser support rather than device support.

Consumer devices like Apple TV, Xboxes, etc are causing problems on campus because of their use of multicast on the wireless network.

How do we educate people what’s safe to use? And will they listen? We have responsibilities to protect the data – how do we do that?

Mobile application management tools might be more appropriate than mobile device management – you can remote wipe data from specific applications. The problem is that the tools are very expensive and aimed for the corporate marketplace. At Stanford they give users the option to either remotely wipe the device or just wipe the Stanford profiles and data.





CSG Winter 2013 – The Changing Nature of Support #3 – the Cloud and BYOD

Erik Lundberg (Washington), Bill Wrobleski (Michigan), Carol Craig (USC)

Cloud impact on support – our role is changing from provider to broker; support services need to react more quickly as the cloud enables speed to elivery; cloud introduces confusion around boundaries of authority.

Bill notes that they can tell users with issues “google just doesn’t do that”, but executives aren’t willing to hear that. 

Erik says that using cloud providers should save energy somewhere, perhaps in third tier engineering. 

We need people with the skills to program various APIs to integrate cloud and on-campus solutions together. 

User migration to cloud services can take a long time, and if you turn it into a user-run pattern it becomes a support burden. 

BYOD – Steven Sather (Princeton), Russ Kaurloto (USC), Marin Stanek (Colorado)

Embrace the drench!

ERP systems don’t support a lot of heterogeneous devices – how do we address that?

Within higher ed we’ve always embraced students bringing their own devices – unlike industry.

USC – ~2.5 wireless devices per person; number of wifi APs – 4,518; Number of simultaneous connections: 26,751; peak video streaming: 2.9 Gbps (on wireless only).

Devices (one typical day, just registered devices): 13 Roku; 79 Plastation 3; Apple TV 867; iPod 3,068; iPad 5,187

Network architecture considerations: wireless priority over wired – the new norm? should we still do end station wiring? multi-tiered segmented wireless networks? cellular DAS network overlays? SDN (software defined networks).

The time to delivery of support materials is shrinking and the number of devices people are using is huge. 

How do you structure the support organization to very high touch support for a set of VIPs and support BYOD for the masses, and how do you structure funding for that?

It’s now everyone in IT that has to do customer support. We’re consultants more than we are solution providers. 

Even if we can’t resolve the problem with cloud providers, if we communicate around it people understand and may be satisfied – at least for students. Not true for faculty and staff. 

Will the Knowledge Base of the future be forums where the crowd can contribute answers?