Skip to main content

Out and about

An important part of my role is to get out and meet people, to explain what enterprise architecture is about and how it will benefit the University.  I have regular meetings with a number of people across the University.  In addition, I am often invited (or put myself forward) to speak to particular groups.  Here follow a few examples.

The College of Science and Engineering IT Committee asked me to explain what my role was about and I was happy to do so.  I kept my presentation short and high level, to get across the main ideas rather than delve into technical details.  The Q&A turned into a really good discussion about the issues that staff face trying to get their jobs done and how a solution needs to address better integration of business processes as well as the supporting IT applications. As a result of this discussion, I will meet some of the admin staff in the School of Chemistry to hear first hand examples of where our current processes cause problems.

I also met the Deputy Directors of Finance to discuss how enterprise architecture could simplify their IT.  Finance is a core support function and hence the finance IT systems have to integrate with many other IT applications across the University.  Currently, this is mostly done using point-to-point integrations, which results in a large number of different connections that all need to be maintained and supported.  We could simplify this by building reusable interfaces, which would in turn reduce costs and improve reliability.

Another presentation was to my fellow Heads of Sections across Information Services.  We have a quarterly meeting at which we discuss a range of issues, and at which one or two Section Heads give an overview of their sections.  This quarter it was my turn.  Thanks to my practice at several other meetings, I managed to get my core message down to ten minutes, which is something I couldn't have managed a few months ago.  Some of my colleagues had heard me speak before but this was a good opportunity to spread the message more widely.

The Procurement Office have recruited a new member of staff to liaise with IS.  I have met her briefly and will be meeting her again tomorrow to explore how we can work most effectively with suppliers while still following procurement guidelines.  From our initial conversation, it seems that we can do better than our current practice.  This could be really useful and I'm looking forward to taking this conversation forward.

If anyone else in the University wants to hear more about enterprise architecture and the benefits it can bring, or if you want to bring particular issues to my attention, please do get in touch.

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 …

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…

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…