Skip to main content

My MidWest tour (Wisconsin-Madison, Michigan and Miami)


I very much enjoyed my recent trip to visit the EA teams at three Universities in the American Midwest.  My hosts were generous with their time and gladly shared their knowledge and experience of establishing Enterprise Architecture practices.  I learnt a lot about EA techniques and even more about the soft skills required to establish an EA practice for a large and diverse institution with a limited budget.

The topics of our discussions reflected the different priorities that the three institutions have set for their EA teams.  The UM-W team focus on major initiatives rather than try to map the overall space.  They provide EA input to assess which aspects of the current state need most attention and then helping with the transition to the new processes.  This seems to reflect the steer I was given by a Gartner consultant, to show some immediate business outcomes.

The other two institutions are taking a more systematic approach in that they are attempting to define certain artefacts across all organisation units of their respective universities.  In the case of UMich, the EA team is helping organisational units across the university to define and clarify their (IT) strategies.  They have a common framework for presenting this information and this has proved especially useful for those units who are developing a strategy for the first time.  The resulting catalogue provides context for the prioritisation and implementation of projects.  

The team at Miami U is mapping the current state of five domains: business capabilities, applications, data entities, infrastructure, and security, in order to provide a context for decision making.  For example, their CIO wants to use this map of the “as-is” state to avoid (or at least discourage) the procurement of new systems that reproduce existing functionality.

Apart from showing me a variety of EA techniques, this diversity illustrated the importance of clear goals for the EA practice.  EA is an immensely flexible discipline, so we need to agree what we want to achieve, depending on the strategy of the institution.

For the University of Edinburgh, our goal is to emphasise the development of our data architecture.  To this end, I intend to produce conceptual data model, a business vocabulary, and high-level target architectures for both BI and operational data.  As data cannot exist in isolation, we will also look at the business processes that produce and consume data, and the applications that produce, store and consume data.

This runs alongside the development of EA processes themselves, of course.  A secondary goal of mine is to define a roadmap for achieving level 2 in the EA maturity model.

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 …