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

Post a Comment

Popular posts from this blog

Webinar: Powering your business with Cloud Computing

On October 14th, I will be hosting a Grid Computing Now! web seminar on the topic of Cloud Computing. We have lined up two very interesting speakers who are using Cloud now to make businesses work. Ross Cooney had a good technological solution to sell but couldn't make it economic until Cloud Computing allowed him to pay for his computation only when he needed it. He will discuss the instant benefits and long term impact of cloud computing to the development, competitiveness and scalability of your application. Alan Williamson created the BlueDragon Java CFML runtime engine that powers MySpace.com. He advises several businesses and will give an overview of the different types of services available and how to avoid being locked-in to a single supplier. You can register for this event here .
Post a Comment
Read more

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-de...
2 comments
Read more

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...
1 comment
Read more