Skip to main content

A new architecture for the information landscape.

The next talk today was by Andy Youell of HEDIIP.  You may know that the University has to provide information about our students and staff to a number of statutory bodies, such as HESA, UCAS, SFC and a host of accreditation bodies for different professions (e.g. actuaries, social workers, nurses, etc). These data returns take a lot of time to produce each year.  From my point of view they are also quite disruptive because the statutory bodies keep changing their requirements, often at short notice, and we have to respond quickly when the latest set of changes comes through.
 
If you look at the whole higher education sector, the situation is more complicated still.  There are 523 separate HE data collections (i.e. institutions) providing information to over 93 different organisations. Each of these organisations has their own data definitions and requirements.  

In 2011 the government agreed a requirement to redesign the information landscape in order to reduce duplication and meet the  needs of a wider group of users.  HEDIIP is the organisation that we created to do this and they have been working towards a standard lexicon and ideally a standard set of definitions.  They have agreed the creation of a Unique Learner Number to identify each student and a Personal Learner Record with some basic fields.  There is far more to do but at least some steps are being made.

In Scotland, we already have a student identifier for the SFC, so HEDIIP are working with the SFC to try and define a mapping between the two.

HEDIIP are also working towards a revised set of subject codes, which will be based on a detailed requirements analysis which will be published this month.

In response to a question about ownership of data, Andy explained that HEDIIP are following the bottom-up, consultative model that was used by NHS Scotland in a previous exercise.  He contrasted this with the well-publicized problems of the top-down exercise attempted by the NHS in England

There is a long way to go because there is not yet any agreement between the various agencies regarding the data definitions that they use, even though there is a considerable overlap between the different agencies.  If HEDIIP can make this work, it would certainly simplify the work we have to do.  The scheme would require governance to manage data changes; apparently the FE world have similar governance structure in place.

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…

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…

A brief summary of our major initiatives

I notice that in 2016 I wrote 34 posts on this blog.  This is only my fifth post in 2017 and we're already three-quarters of the way through the year.  Either I've suddenly got lazier, or else I've had less time to spend writing here.  As I'm not inclined to think of myself as especially lazy, I'm plumping for the latter explanation.

There really is a lot going on.  The University has several major initiatives under way, many of which need input from the Enterprise Architecture section.

The Service Excellence programme is overhauling (the buzzword is "transforming") our administrative processes for HR, Finance, and Student Administration.  Linked to this is a programme to procure an integrated ERP system to replace the adminstrative IT systems. 

Enabling Digital Transformation is a programme to put the middleware and architecture in place so that we can make our processes "digital first".  We're implementing an API framework, a notification…