Skip to main content

Enterprise Architecture at the University of Edinburgh


So, what is Enterprise Architecture (EA) and why are we bringing it to the University?  Let me set aside formal definitions and detailed explanations - after all, there is plenty of background information on the web, which you can read should you wish.  Instead, let’s keep this informal and look at what it can do for our university.

Essentially, the goal of EA is to link all IT and administrative services together to provide a joined-up, easy-to-use suite of services.  Times have changed from when students dealt with IT systems separately -  logging in to the back-office finance system for one task, the timetabling system for another, teaching systems during the day, and so forth.  Instead, people do everything online, using smartphones or laptops or desktops.  We rarely think about the ”IT” systems underpinning these services, we just do the processes online without really thinking about the IT.  Enterprise Architecture is about making the “business processes”, the data, the applications and the underlying technology all line up to provide this modern, integrated service.

We need to design processes to prioritise the user’s point of view, rather than the administration staff  (including IT staff).  We may need to change the way we do things, and we need to align the underlying IT so that we can make these changes as easy as possible.

We also need agreed data models and data definitions, so that anyone accessing data via any of our systems see the same information and understand the information presented to them.  We need management information (MI) so that the University makes decisions based on accurate and timely information.

Enterprise Architecture provides a range of techniques to aid all this.  An EA practice brings people together to achieve shared understanding and common goals.  It creates templates so that we can define standards, processes and data models using common approaches.  It produces reusable data schemas and APIs so that IT systems can integrate with each other more simply, and so that projects don’t replicate similar work.

This gives me plenty of scope for future blogs posts.  I can write about particular techniques and what they can do for us.  I can give examples of the work we do as we do it.  I can discuss some of the challengers we face as an institution.  First of all, I’ll be writing about enterprise architecture experiences from other universities, which may give us some guidance of what can be achieved in our sector.

Comments

Popular posts from this blog

2016 has been a good year

So much has happened over the last year with our Enterprise Architecture practice that it's hard to write a succinct summary.  For my day-to-day experience as enterprise architect, the biggest change is that I now have a team to work with.  This time last year, I was in the middle of a 12-month secondment to create the EA practice, working mainly on my own.  Now my post has been made permanent and I have recruited two members of staff to help meet the University's architectural needs.

I have spent a lot of the year meeting people, listening to their concerns and explaining how architecture can help them.  This communication remains vital, the absolute core of what we do and we will continue to meet people in this way.  We also talk to people in other Universities in order to learn from what they are doing and to share our own experience back.  A highlight in this regard was my trip to the USA last January.

Our biggest deliverable for the past year was the design of the data wa…

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…