One of my hobbies is following the commercial aviation scene. My job requires me to fly around a lot, and that only sparks my curiosity further around how the commercial aviation business works. What better then, that to use this hobby as a motivation to test new features in SQL Server 2012? This hybrid interest, which I call Aviation BI, is the driver behind a series of blog posts, where I will take you through a typical lifecycle of a BI project:
In the first blog post of this series, I will take you through what I (as an end user) see as possible requirements. We will also review the datasets available for consumption.
There are some categories of requirements that we have, depending on the perspective we are talking about. A typical retail consumer would want to check some statistics:
As an airline executive, I might want to look at:
As an airport administrator, I might want to look at:
As an aviation analyst I may have the following queries:
And so on… these perspectives are imaginary, but I suppose they are very typical of what people in those roles would be asking to see.
There are some amazing datasets available in the public domain. For our purposes, we will be using the following:
1 A ‘market’ in DB1B terminology is a break in journey other than for changing planes.
2 The difference between ‘market’ and ‘segment’ in T-100 is explained at this link. The T-100 reporting guide is also useful to understand this dataset.
Over a series of blog posts, I will take you through how we:
All of this, towards answering the ‘customer’ requirements which we laid out earlier!
For those interested in reading further about airline statistics, here are some references:
So if you have some comments on the scope of this ‘project’, I would LOVE to hear from you! Do leave a comment below if you liked this idea and would like to see more.