Skip to main content

Changing our integration mindset

Over the last few weeks, we've been working with some consultants to assess our approach to integrating business processes that involve multiple IT systems.  We have an ambition to replace many old point-to-point data transfers with more modern integration technology, enabling a more responsive user experience.  As we are consolidating many of our existing applications and gradually moving to more cloud-based services, we will need to replace many of our existing integrations and this provides an opportunity to transform our approach.

We're planning to support three types of integration:
  • Enterprise Application Integration (EAI) for message-based, inter-system processes
  • API Management for enabling portals and innovative user-facing apps
  • Extract-Transform-Load (ETL) for where we still need to move large amounts of data
On the technical front, the consultants recommend that we adopt one of a small number of cloud-based integration platforms.  The next step is to plan and execute the evaluation of candidate software, using short-term test licences of the cloud-based systems.

The more interesting challenges are the non-technical ones.  We are aiming to change the way people think about service integration.  We will explain why we’re changing things and what this will mean for the people concerned, including business colleagues and IT staff.  We need to establish governance to encourage re-use of components and to discourage ad-hoc solutions.  We may establish a new integration service.  None of this is straightforward, least of all in a University environment!

I found a useful article on the EDUCAUSE website in which a couple of American Universities summarise their experience of implementing such a change.  It make interesting reading and I recommend it.

Tying it All Together - Integration PaaS in the Next Generation Enterprise

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