(grump mode on) I wish everybody who wants to hit submit on 'how hard can this be? I can do it over a weekend!' type of posts on HN would come off their high horse and apply Occam's Razor. If a problem exists, and probably thousands of people have already devoted substantial parts of their lives to it, how likely is it that some amateur on HN would come up with a better solution in 15 seconds after reading a cursory overview of it? Answer: negligibly likely. So what's the more likely explanation? That the reality is not as simple as the abstract overview makes one think. Which is exactly what is going on here.
There are few if any workable OS scheduling packages because it's boring and situation-specific. 'Scheduling' as an abstract problem is solved, all that is left are implementations, which are all site-specific. Exactly the type of situation in which OS has little chances of being a realistic solution.
Secondly, most places with computer programs should have enough competent people to choose from to collaborate on internal projects like this to avoid the need for everything to be an outside consultant or purchase. If a small team of graduate students can't handle some of these problems, I would consider that an indication that the programs aren't doing a good enough job. I understand not every "computer science" person is a naturally good programmer - there's a distinction, etc. But there still seems to be a waste of available talent on-campus that could be tapped for some problems.
Bitter, who, me?
This industry is beyond ripe for disruption. it's an institutional racket.
The software is crap, and hated by most who actually have to use it.
Take course scheduling for example. Are there any well known open-source course scheduling solutions out used by many universities? If not, why not? Every time we see an industry with a dearth of open source tools, we should be worried and be asking why.