Skip to main content

Costs of doing BI the hard way

I am preparing a business case to justify the building of a data warehouse for the University.  This has some challenges.  While everyone acknowledges that our current BI reports need improved, it is far from obvious how to measure the benefits of improving our BI.  Suppose we our student satisfaction score increases in two year's time: how much of that would be due to which specific initiatives, and which of those would result from decisions made with better BI data?  It's a tenuous thread of causality.

Nonetheless, if we believe that the decisions made by staff have some impact on outcomes, and that by having better information available to them they will make better decisions, it follows that a successful data warehouse project will have a positive effect.  Even if the impact on University income is one tenth of one percent across the board, that would quickly repay the cost of developing and running the service.

Another approach is to look at the costs of not having an integrated source of BI data.  This is something we can measure more easily.  I've asked some of my colleagues to estimate how much time is spent constructing reports manually, downloading information from multiple systems and putting it together by hand, and they painstakingly revising it when changes are requested.  The costs soon mount up.

Without going into specific details on a public forum, each of our academic schools spends a considerable amount of administrator time pulling together this sort of report for the school finance reports, HR reports, and teaching office reports.  We have twenty schools, with varying degrees of support from the college offices.  Altogether, it is not unreasonable to estimate that the equivalent of 15 full-time equivalent staff (FTE) spend time creating these reports.  More time is spent in central support areas as well, easily reaching a total of 20 FTE.

Now, no IT system or process can make everything 100% efficient, certainly not at the first sweep.  For this business case, I assume we can make a 50% improvement.  That still frees up 10 FTE to do more productive work.  As the University is looking to expand, that sort of saving would pay for the data warehouse on its own, even before the advantages of better information kick in.

Comments

Popular posts from this blog

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…

A brief summary of our major initiatives

I notice that in 2016 I wrote 34 posts on this blog.  This is only my fifth post in 2017 and we're already three-quarters of the way through the year.  Either I've suddenly got lazier, or else I've had less time to spend writing here.  As I'm not inclined to think of myself as especially lazy, I'm plumping for the latter explanation.

There really is a lot going on.  The University has several major initiatives under way, many of which need input from the Enterprise Architecture section.

The Service Excellence programme is overhauling (the buzzword is "transforming") our administrative processes for HR, Finance, and Student Administration.  Linked to this is a programme to procure an integrated ERP system to replace the adminstrative IT systems. 

Enabling Digital Transformation is a programme to put the middleware and architecture in place so that we can make our processes "digital first".  We're implementing an API framework, a notification…

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-depth discussions about th…