Skip to main content

Meetings: Data Governance and Information Security

This week saw a meeting of the University’s Data Governance Group.  I gave a presentation about enterprise architecture, including my draft principles for data architecture and the need for governance of the data architecture as it evolves.

I requested that we produce a list of core data sets, with the data steward identified for each, and a standard process for requesting and recording access to data.  Some of our data stewards already have reasonably mature processes in place, but others do not and the lack of standardisation makes it difficult for people to access the data they need.

We had a useful discussion about this and other issues. One key piece of feedback I took away was that my draft principles are focussed on centrally managed datasets, and I also need to consider how locally managed data fits into the architecture. The view of the group is that we need to ensure that this data can be managed without undue overhead.  I think the tools we develop for documenting central data sets will also be useful for local data stewards, should they choose to use them, but we may require a level of governance for central data that would be optional for at least some local data. 

I'm reminded of the "big blue ring" diagram that Nikki Rogers used to such good effect at the University of Bristol.  I may well recast our informal high-level architecture diagram in a similar way.  The following is the Bristol version:


The next meeting of the Data Governance Group will look into how the group should engage with various operational processes to better oversee the governance of data within the university.  This should be a very interesting discussion.

I also had a meeting with our new Chief Information Security Officer, Alistair Fenemore.  As Alistair has been in post for only a couple of weeks, this was very much an introductory meeting to explore our concerns and see where they overlapped.   We agreed to meet regularly in order to coordinate our efforts and I look forward to working with Alistair.  


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…