Skip to main content


The annual EDUCAUSE conference attracted 8,000 people to the Philadelphia convention centre, including four of us from the University of Edinburgh.  My colleagues were giving presentations, while my main reason for attending was the pre-conference workshop on Enterprise Architecture and Digital Transformation, which I blogged about last week.

The conference itself offered a smorgasbord of options.  I mainly attended sessions about new technologies, which I blogged about on the Applications Directorate blog, and a few others which consolidated my existing interests.  If these topics weren't to your taste, there were also sessions about research, learning technologies, enterprise systems, leadership development, equality and diversity, and many other aspects of IT in higher education.

The exhibit hall gave opportunities to talk to many vendors, from the large established corporations to the newcomers in "startup alley". I chatted to several CRM vendors, and looked at other technologies such as cloud authentication services.

Of course, there were also informal conversations, which are always interesting to find out what other institutions are doing and which challenges they face.

Overall, I found EDUCAUSE 2017 a very useful experience.  

My blog posts:
Artificial Intelligence, Clouds and Prediction: Day 1 of Educause 2017/

Nudged Users, Distributed Security and Voice Control: Days 2 & 3 of Educause 2017/

My colleagues' presentations:
Research Data Management International and Institutional Intersections

Discover the Treasures of Benefits Mapping


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…