← Back to context

Comment by ivanbakel

10 hours ago

Interesting that they settled on a standard model at all. The announcement implies that the university is responsible for phone maintenance and repair, which makes sense as a motivation, but is not something I would expect in itself from a cost/expertise standpoint. I would be curious to know if a Fairphone makes servicing cheap enough to warrant doing it in-house for an IT department.

It’s also tacit, but I assume it helps them to interface with a Dutch company. Did they get any financial incentive for it?

The university should push the maintainance to the holder of the phone? That seems unreasonable.

As mentioned in another comment. Universities already have in house it services. Being able to fix the phone right there with spare parts is likely very cost efficient.

  • I think the alternative was to contract it out to an IT company rather than push it to the holder. Same as company phones in corporate environments

If it is like my usual experience with European academia, it may be intended to more heavily push use of Microsoft 365 services, which tend to somewhat assume phone availability. I think that usually universities cannot force the use of personal devices for work, so providing mobile phones on request is one way of moving to a more purely Microsoft service infrastructure. It looks like Radboud is a Microsoft shop, so I would not be surprised.

My university, for example, is gradually removing all office phones (already voip) and replacing them with Teams voip as the only phone system for the university, encouraging personal phone use of Teams, but having computer-based use as the option for people who refuse. As they don't provide mobile phones, however, they can't require Microsoft Authenticator, and so at least officially will still give hardware keys on request (and fortunately still allow TOTP, even if they don't advertise it).

If they already have an IT department, they already have the staff to take care of this additional workload (after a bit of training). How much difference is there really in repairing a "repairable" phone and a computer? Not much really as "repairing" a computer is often just fiddling with the software and / or just about changing an easily available and "standardised" parts. (When was the last time any of us saw any IT department doing actual board level servicing to repair a computer?) It will be the same with the Fairphone too (Fairphone makes it easy to change the battery, the board and the display screen).

If the university didn't make phone repairs themselves they would have to send the phones off for repair, or contract with a local phone repair shop. Or the secret third option: telling your employees to get it fixed and send you the invoice. None of them are cheap, and some of them will make you very annoyed with your billing/procurement/finance people. After a certain scale doing it inhouse makes sense, and with the right phone it's not much more difficult than fixing a business laptop, which is also commonly done inhouse with available spare parts

If they want to use an MDM solution like Microsoft Intune to enforce some security compliance they are kind of forced to provide the device. People typically don't accept their private phone to be managed by their company IT.

  • Providing a device doesn't require picking a standard issue model of phone. IT departments often support an employee's choice of phone (or at least, choice of manufacturer) provided it's compatible with management software.

> The announcement implies that the university is responsible for phone maintenance and repair

It says "Do you require a (replacement) smartphone for your work at Radboud University?", so it's probably for a handful of board members and the like, not the actual faculty staff.