Skip to main content

BI advice from Southampton Solent University

We were fortunate to have a visit from Neil Randall of Southampton Solent University last month.  Neil and his colleague Paul Colbran gave an excellent presentation at this year’s UCISA conference about their experience of setting up an effective BI service.  I invited Neil to visit Edinburgh to explain their approach to our team and to review our proposed BI architecture.

We began the day with Neil reprising his part of the UCISA presentation and discussing several points arising.  We presented our draft architecture, and then we discussed topics including how to structure and manage a BI service, which ETL tools to use, how best to model data, and how to integrate a data warehouse with relationship management (CRM) software. 

We had a very information conversation about “Extract, Transform, Load” (ETL) tools, which load data from source systems into a data warehouse.  Neil recommended we look at file-based tools rather than database-oriented tools.  Without this advice, we probably would have made the opposite decision, just because we are used to working with database systems.  We will now pilot a file-based tool as part of our initial project, before using this experience to inform our tender for a full procurement.

Among all the topics we discussed, sometimes a really small idea stood out as simple and useful.  One such was that Southampton Solent’s team has a logo that they put on reports derived from the data warehouse, to show that these reports are based on trusted data.  Analysts can use the reporting tools on other data as well, but those reports don’t get the logo, so people reading the reports know they may be more speculative.

We all found Neil’s visit interesting and useful, and we are grateful to him for taking the time to visit Edinburgh.

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 …

A new EA Repository

One of my goals since starting this job two years ago has always been to create a repository for architecture documents.  The idea is to have a central store where people can find information about the University's applications, data sources, business processes, and other architectural information.  This store will make it easier for us to explain our plans, to show the current state of the University's information systems, and to explain what Enterprise Architecture is all about.

It's taken a long time to reach this goal, mainly because we're often had more pressing and immediate work to be done.  The creation of a repository is one of those tasks that is very important but never quite urgent.  So I'm now very happy to say that we are in the process of deploying a repository and modelling tool.


This is the culmination of a careful process to select the most appropriate tool for our needs.  We began by organising several workshops to gather requirements from a rang…