Skip to main content

Upgrades & integrating vendor software

The last month we seem to have spent a lot of time dealing with projects to upgrade various  systems.  We run a large number of such systems, covering everything from virtual learning environments and wikis to student record systems and timetabling, and also encompassing underlying middleware software.  I say "vendor systems" but some of these are open-source projects maintained by a global community.  Others are traditional vendors, ranging from large multi-national corporations to niche vendors of HE products.

We have encountered problems with a number of systems, from various sources.    Some of these have been bugs in the third-party software.  I won't name the systems, nor even say what functions they perform, as I don't want to bring any particular vendor into disrepute.  Other issues have turned out to be caused by mistakes in our own systems.  In one failed upgrade, we kept the existing system running on one site while we upgraded the system on the backup site, only for the tests to fail; it turned out that the problem was a setting in the load balancer that we were using to separate traffic between the two sites.

Upgrade failures are very frustrating for everyone involved.  We have responded quickly in all cases.  Usually we have brought an external consultant on site for a couple of days, as a new pair of eyes can help to diagnose problems.  The consultants don't always find the underlying problem but sometimes they do, and at least they can confirm that we aren't missing anything obvious.

In most cases we have resolved the issues and the upgrades have either proceeded or are due to proceed shortly. One or two do remain and we are working with the vendors to find a way forward.




Comments

Popular posts from this blog

Changing Principles

In EA, architecture principles set a framework for making architectural decisions.  They help to establish a common understanding across different groups of stakeholders, and provide guidance for portfolios and projects.  Michael Durso of the LSE gave a good introduction to the idea in a webinar last week for the UCISA EA community.

Many organisations take the TOGAF architecture principles as a starting point.  These are based on the four architectural domains of TOGAF: business, information/data, applications, technology/infrastructure.  These principles tend to describe what should be done, e.g. re-use applications, buy in software rather than build it, keep data secure.  See for example the principles adopted at Plymouth University and the University of Birmingham.

Recently though, I encountered a different way of looking at principles.  The user experience design community tend to focus more on how we should do things.  E.g. we should start with user needs, use iterative developm…

Why the UCISA Capability Model is useful

What do Universities do?

This may seem a strange question to ask and the answer may seem obvious.  Universities educate students and undertake research.  And perhaps they work with industrial partners and create spin-off companies of their worn.  And they may work with local communities, and affiliation bodies for certain degress, and they definitely report on their activities to government bodies such as HEFCE.  They provide student services and support.  The longeryou think about it, the more things you can think of that a University does.

In business, the things that an organisation does are called "capabilities", which is a slightly strange term.  I think it is linked to the HR idea of a combination of the CAPacity and ABILITY to do a task.  Whatever the name, it is a useful concept.  A capability is more basic than a process: a University may change the way it educates students but as long as it remains a University it will educate them one way or another.

A capability …

"No more us & them"

WonkHE recently posted an interesting opinion piece with the title Academics and Administrators: No more ‘us and them’. In that post, Paul Greatrix rebutted criticisms of professional services (administrative) staff in Universites from some academics. To illustrate his point, he quoted recent articles in which administrators were portrayed as a useless overhead on the key tasks at hand (teaching and research).

This flows both ways, as Greatrix himself points out. As Enterprise Architect, I work with Professional Services colleagues and I have heard some of them express opinions that clearly fail to understand the nature of academic work. Academics cannot be treated as if they were factory workers, churning out lectures on a treadmill.

I think these comments reveal a fundamental clash of ideas about how a University should work. Some people who come into management positions for other sectors tend to frame the University as a business, with students and research funders as customers t…