A common theme is limited or no budget for updating or expanding systems such that the go from "nice" to "acceptable" to "clunky" and then worse.
Politics also becomes an issue. That aged home rolled service might have a palpable price tag to fund a major update for, but once you do discovery and scope every specialized integration made for every department and reality sets in. Whatever path is chosen is going to burn a number of parties, and using a vendor provides a baseline for functionality and a convenient scapegoat
2 - see federated auth via shibboleth, or any number of incommon tech. Or even Kerberos
This stuff exists and often works well, but brings it's own operational maintenance challenges and required specialized skill sets.
3 - only a subset of these processes were handled on paper. expectations on both the timelines and breadth of services have gone up significantly since this was all on paper
This reminds me of how a small team of U.S. seniors provided WiFi to basically the entire D1 football stadium for our college (at a time this hadn’t been done before), for < $10k (we used the grant to buy whatever we couldn’t get used from various departments), had it working in what may have been a first for a college stadium of that size, only for it to be completely scrapped and the university spending tens of millions to replace it with a new commercial system that didn’t even work as well and had a higher per game support fee than the cost of running our entire system for the whole season.
Unrelated to this (but maybe still explaining why), the college president was suspected of having sent contracts to “friends” who had significantly overcharged the university for years.
2) See (1) and also because AI can't do it, so they can't handle.
3) Because paper kills trees, and brawndo contains electrolytes, duh.
> Washington University's Executive MBA (EMBA) program provides a holistic approach to managing people, projects, and budgets. It is designed to meet the needs of middle- and senior-level professionals who seek to exercise true organizational leadership in dynamic and changing business environments
Sounds like the perfect people to manage your software projects. Not sure if you'd get a professor, hire phds or make it a student-run program, but surely something can be arranged. Maybe they can even rope in the people from the Information Systems Management courses
I guess we could also flip it and ask why don't we offer PhDs in developing software for public administration?
I think it might also be something else.
WUSTL has 20,000 students and faculty. This is not a big organization. To manage that, they have over 17,000 administrators. Meanwhile, the Pentagon in 1941, at the start of US involvement in WWII, had only 24,000 civilian employees to manage over a million soldiers.
Some universities will also claim that the average financial contribution for students and families has not increased, in spite of tuition and fees outpacing inflation for half a century or more and student loan debt reaching $1.6T.
But any large bureaucratic organization tends to seek expansion of its staff, budget, and influence, and that is likely a core reason for the dramatic increase in non-teaching university staff.
1. They exist. However, writing a piece of software is not the same thing as supporting them, especially when it comes to dealing with core HR system. This is where SaaSs and similar platform offers lot of appeal.
2. Also difficult because everyone has different needs and at some point certain features get prioritized over others. I support a platform that was built in house before I was born. The guy who wrote it is no longer with us and it is cludgy. Any product decisions evolve years of committee meetings before any decision gets made (by which the it may be incorrect or not relevant.)
Every single time I worked for a company that said let’s hiring an engineering team to build a software that is already solved by a market offering, it has never gone well. The in house product never had the same capabilities or had the same sheen.
3. Can’t answer this one other than digitization efforts.
For transparency, a single software engineer budget is $670K+.
Are you saying that the costs to employ a single software engineer is $670K+? If you mean something else then nvm.
Otherwise that's a ridiculous number to use unless you are specifically talking about places with the highest cost of living in the country where a mid-level dev starts at over $200K.
I find this 4X of base salary implausibly high. 2X strikes me as closer to my reality at a large academic medical center.
Heck of a lot of "support cost" to get to $670k
Whether the numbers are either wrong or if that is truly what support costs look like at a university would be interesting to know.
Federal taxpayers underwrite unlimited amounts of money to the university’s customers. Why would the university’s leaders not take advantage of this and enlarge their kingdoms as much as possible? The bigger the budget, the bigger the university employees’ cut (incl the board).
I mean students on their own go rogue and make tools for their peers to make it less painful to much fist shaking by the administration.
the kickbacks are too good.
I don't remember all the details, but this is what they used up til the mid-90s. By then, I could probably run something on my 486 home computer that would complete in half an hour. But there were decades of process and customization embedded in these systems.
When modernization happened, it was swift. My dad was lucky with the timing as he was retiring during the transition so even made bonus money coming back as a consultant. But you can imagine that even if the new software was pricey and not as customizable, the speed improvements and reduction in staff made sense.
Once the old staff was cleared out, there was no department of staff being paid to build computer services, only the lesser staff needed to maintain and use it. The issue was that hardware/Internet usage expanded too fast, the importance and reliance on tech grew and it became a selling point for unis to have the newest systems in place.
It makes sense now for the pendulum to swing in the other direction, as customization and cost are wildly out of balance with AI and the latent tech workforce available at every college.
I would say the blocker now is the same as what allowed creaky old systems to persist into the 90s - administration doesn't give a shit about any of this and it is only viewed as a cost center. Until differentiating through customization provides an obvious and immediate fiscal benefit to the admins themselves, most unis won't look at changing off their shitty landlord systems until they are basically forced to by the market.
1) What happened to the days when universities published their own software, like pine from UW? It seems like Washington of St Louis, which offers a PhD in computer science, should have some students capable of writing a database to run the university.
2) Why have universities not collaborated to develop a modular, expandable system for running a university, instead of putting themselves at the mercy of Workforce, SAS, etc?
3) These same processes were at some point in the past handled on paper, for far less than $16k/student. At what point did the university so lose its organizational competence that the filing system (that's what a database is) ate the budget?