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

Presentation: Putting IT all together

This is a presentation I gave to an audience of University staff: 

In this seminar, I invite you to consider what the University’s online services would be like, if we worked together to design them from the perspective of the student or member of staff who will use them, instead of designing them around the organisational units that provide them. I’ll start with how the services might appear to that student or member of staff, then work back from there to show what this implies for how we work, how we manage our data, and how we integrate our IT systems. It might even lead to changes in our organisational structure.

Our online services make a vital and valued contribution to the work of our students and staff. I argue that with better integration, more consistent user interfaces, and shared data, this contribution could be significantly enhanced.

This practice is called “Enterprise Architecture”. I’ll describe how it consults multiple organisational units and defines a framework …

Service Excellence, Digital Transformation and Enterprise Architecture

Our University Secretary has sponsored a major review of the University’s administrative processes, coining the banner “Service Excellence”.  The aim is to look at the services we provide to staff and students with a fresh eye, making them more effective, more efficient, and focussed on the user rather than administrative convenience.

Our CIO is sponsoring a similar programme called “Digital Transformation”. This will replace old paper-based processes, starting with the question of what would processes look like if we designed them afresh for the modern connected world.  The aim is to make processes that are more focussed on the user and hence more effective and efficient.

Both of these ambitious programmes will need an effective enterprise architecture, if they are to succeed.  Digital Transformation is intrinsically about using opportunities provided by new technology to improve services and, as such, it requires effective technology services to make data available when needed, to pro…

Not so simple...

A common approach to explaining the benefits of Enterprise Architecture is to draw two diagrams: one that shows a complicated mess of interconnections, and one that shows a nicely layered set of blocks. Something like this one, which came from some consultants:


I've never felt entirely happy with this approach.  Yes, we do want to remove as much of the needless complexity and ad-hoc design that litters the existing architecture.  Yes, we do want to simplify the architecture and make it more consistent and intelligible.  But the simplicity of the block diagram shown here is unobtainable in the vast majority of real enterprises.  We have a mixture of in-house development and different third-party systems, some hosted in-house, some on cloud infrastructure and some accessed as software-as-a-service.  For all the talk of standards, vendors use different authentication systems, different integration systems, and different user interfaces.

So the simple block diagram is, basically, a l…