Skip to main content

Service Management and Enterprise Architecture



We are currently reviewing our catalogue of IT & Library services.  In this, we follow ITIL, the widely used framework for service management.  This has stimulated some discussion about how enterprise architecture can support service management, and also how the two approaches fit together.

In my opinion, EA best supports service management by providing context and describing how the various services inter-relate.  An ITIL service catalogue is simply a list of services (in much the same way that an EA interface catalogue is just a list of APIs).  The catalogue does not show how the services fit together, or which business capabilities they support, or which group of users uses each service.  ITIL classifies services along one axis as “business services” or “IT services”, and along another axis as “customer-facing services” or “supporting services”, but these are broad-brush terms and open to interpretation.


An architecture diagram can show, for example, that one IT service is “customer-facing” from the point of view of the IT department because it supports “customers” in the Finance department, and that from the Finance department’s point of view the same service is a supporting service that underpins some aspects of one or more of their business services. The notion of “customer” changes depends on who is looking (in architecture, this is called the “viewpoint”).  To continue the example, the finance services may have different customers – one may help students manage their accounts, while another may be for school administrators to manage their internal budgets.

The picture is a conjecture of how we could model this interrelationship for a subset of services.  It shows, in the lower layer, two services provided by a production management group.  These keep the IT applications running.  One thing to note is that individual applications are not services; they only become services when grouped and managed.

The upper layer shows two groups that use these IT services to provide services to various groups of users.  At Edinburgh, the Digital Learning section is part of Information Systems, as is Production Management, while the Finance section is in a different support group.  EA shows that we can use the same model for internal and external customers, and provides a level of clarity that a simple catalogue cannot achieve.

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…