Skip to main content

Episode IV: A New Hope


Since the beginning of this academic year, I have taken on the full-time role to establish an Enterprise Architecture capability at the University.   For the past few months, I have been working out roles and relationships, principles and processes.  I have given presentations to several groups, first within IS and now moving beyond.  I have recruited an experience contractor to help the University along this new path.  And as the new calendar year begins, we are in the position to start producing results that people can see.

A key part of this role is communication – explaining what EA is about, listening to people’s concerns, sharing knowledge of resources new and old, discussing what needs to be done, and disseminating decisions.   I am reviving this blog as one strand of this communication.  Over the years, I have been a pretty poor blogger.  I haven’t always had things to say, and sometimes I have lacked the time to write them.  With the importance of communication in this new role, I hope to do better.

There are other channels besides this blog.  I am arranging regular meetings with other sections of IS, with the colleges, and with other support units.  There will be an Architecture Repository with links to resources – including high-level documents such as principles and architecture overviews, as well as more technical artefacts such as data models, interface descriptions, technology life-cycles, and procurement standards.  And I welcome any questions from anyone who wishes to know more or to raise a concern.

Architecture is a subject dear to my heart.  During my time as Head of Development Services I did try to introduce some architecture ideas and practices, which is very difficult to achieve with basically no funding. My new role, to which I am seconded for the current academic year, gives me the opportunity to put proper foundations in place.

Comments

Popular posts from this blog

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…

Business Model Canvas

A Business Model Canvas is a tool for mapping the core functions and capabilities of an organisation.  Compared to the Core Diagrams that I described in an earlier post, the business model canvas attempts to present more aspects of the business, starting with the value proposition – a statement of what the organisation offers to its users (in the business world, to its customers).  It shows the activities and resources, as Core Diagrams do, but also shows user relationships & channels, and also benefits and costs.  I’m not aware of any universities that have used this tool but you can find examples from elsewhere on the web.

We are considering business model canvases as a tool for mapping the strategic capabilities of units at the University of Edinburgh.  Phil Taylor, our EA contractor, sketched an outline of what a business model canvas might begin to look like for HR:
This is only intended to be suggestive: the real canvas would need to result from in-depth discussions about th…