Skip to main content

EA Community of Practice

Today, I attended a meeting of the UCISA EA Community of Practice, at Manchester Metropolitan University (MMU).  The focus of today's meeting was on data architecture, and I contributed with a talk about our data warehouse plans at the University of Edinburgh.

The first presentation of the day was from the University of Birmingham, who are using data architecture techniques to support the upgrade of their Finance and HR systems to a new ERP system.  This was a good example of the benefits that enterprise architecture can contribute to service transformation projects.

Next was a talk about the HEDIIP Data Capability Toolkit for the HE sector.  This sets out the case  that we can make data a tangible asset, capable of adding value to our universities.  The programme is effectively taking an EA approach, mapping the as-is state and defining the target to attain, all mapped to a data strategy.  From the talk, it sounds like the toolkit has some elements which will be very helpful and I will take a look to see which ones I can use in my own work.

My talk seemed to go well and I got some useful feedback from the questions.  That is one of the benefits of giving a presentation to a group that includes several experienced architects; it's a cheap way of getting consultancy!

The final presentation of the day was from the team at the host University (MMU), who are preparing to replace the interfaces from their student record system.  They are planning to use Azure API Management to present all their APIs, which looks to be a useful system (if your data is on Azure, that is).  It provides a browsable catalogue for users, a request process that lets owners approve or deny requests, and management information about which systems are using which APIs.  It basically fulfills all the functions of a traditional Enterprise Service Bus.

UCISA, for those readers who don't know, is the organisation for supporting & representing University & College IT departments.  The EA Community of Practice, as the name suggests, is formed of enterprise architects (and data architects, business analysts, solution architects) from approximately 80 universities.  In addition to the data architecture sessions, we spent some time reflecting on how to better support each other and build our community.  Several ideas surfaced and I hope to see them taken forward.  One idea was for local meetups and I'd be open to organising some meetups in Scotland.


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…