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

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…

New staff for the EA team

I'm delighted to welcome Jason Murphy, who joins us as our CRM Architect, and Wilbert Kraan, our new Data Architect.  Both Jason and Wilbert have worked as consultants for several years and bring new skills and considerable experience to IS.  They both know more than I do about their respective fields, which is how I like to hire people.

So the Enterprise Architecture practice now comprises the three of us, instead of me working on my won, which means we have more capacty to guide the University's IT architecture.  We can offer a greater range of skills and can bring a wider range of experience to bear.  I'm really excited about the opportunities this presents.

As his job title implies, Jason will focus on contact relationship management, working to build a user community and to create a strategy for managing and improving the University's relationships with prospective students, research partners, community organisations, and other parties - to give them all a better …