Wednesday, August 8, 2012

Sharing Resources between Projects & Operations

It is a common dilemma of IT project managers that for any project, they are provided with the resources who are already engaged in Operations.  No I am not talking about software development companies or consultants.  I am talking about in-house IT departments of different organizations.  These IT Departments work as support departments.  The main responsibility of the resources in such a department is to ensure continues and smooth operations.  However, when it comes to introducing any new Software Application or bringing in some new Infrastructure, same resources are provided to the Project Manager to work on the new project.  This situation creates two major challenges for a Project manager.
  1. Time management for a resource between Project and Operations.
  2. Loose control over resources since they report to their functional managers and not to project manager
I will cover point # 2 in another blog entry.  Right now I would focus on the issue mentioned in Point # 1.  This problem can be resolved by the 50/50 formula.  The resource needs to be scheduled based on only 50% of daily time.  Rest 50% of the time, he/she can spend in dealing with Operations issues.  Sounds simple... Does it?  Well things might go more complex..  I was once delivering a lecture in a Project management class when one of the students (Who was a professional DBA and a support resource of an in-house IT Department) asked about the same subject and I replied him the same.  But he said that there are some times operational issues which might take a couple of days or even weeks to get resolve. And usually they are on such a high level of priority that a resource really can not work on project and no alternate resource is available.  So what should a project manager do in this case?

My answer was to do the following:
  1. Prepare a change request for temporary release of the resource from project due to Operations requirements and get it approved from sponsor. 
  2. Add an entry in Project Issue Log regarding the resource un-availability due to Operations issue. Mention the Service Ticket number of the Operations issue (Usually most of the IT departments use a Help Desk or Service Desk software for operations which generates Service ticket numbers) and mention that change request#  as well.  
  3. Once the resource is available, adjust the project schedule if needed.  Raise another change request for resource addition to the project and schedule update and close the issue in the issue log after its approval."

Sunday, April 10, 2011

IT as a profit center

There has been a lot of debate on this topic and till some time back, i was also of the view that IT is better as a Cost center and it can never be and should never be taken as a profit center.  However, as i started digging into possibilities, i realized that how effective it can be in managing and improving the performance of an orgainization.

Wednesday, February 25, 2009

Part II: Difference Between BI & ERP Report

Welcome to the part II of Difference between BI and ERP reports. You can read the Part I of this post here. Before proceeding further, let me tell you that the target audience for this blog post is Business User. However, even if you are an IT professional, you are welcome to read it and give your comments (though you will find it a bit simple but that is because it is intended for Business users). I got a pretty encouraging response to my first post on this topic. The very first response I got after posting this thread's link in my LINKED IN profile was “what is the difference between BI and DW (read. Data warehouse)”.

In ordinary words “BI is the front end of your solution and DWH is backend”.

BI solution can only be based on the data warehouse. A data warehouse has a different data structure than a normalized entity relationship structure used in ERP applications. Some sophisticated tools such as Oracle Business Intelligence Enterprise Edition (OBIEE) provide you ability to create a virtual dimensional data model layer on top of a normalized physical database but doing that for enterprise reporting would have a severe hit on performance of the system.

Before continuing the discussion on BI vs ERP reports, first let me explain some of the concepts used in business intelligence, so you will be able to understand me in later sections.

What are Dimensions and measures?
In simple words, all the facts and figures are measures. Dimensions are the elements against which we see certain measures. Normally ERP and other OLTP systems generate two dimensional reports e.g. sales of certain products based on time. Here, product is a dimension. Time is also a dimension and sales amount is the measure. At the minimum, any report can contain two dimensions and one measure. BI reports make it possible to make multidimensional reports. You can refer to the report2 I displayed in my previous blog post. You can see that it contains three dimensions, i.e. Time, Product, location and there is one measure which is sales amount. You can even add several new dimensions in this report.

What are Key Performance Indicators (KPIs)
KPIs are measures or metrics that help organizations to evaluate the progress towards organizational goals and objectives. KPIs can or can not be quantifiable in absolute numbers. Examples of some KPIs are:

  • Market Share
  • Market Growth
  • Customer Churn Rate
  • Customer Profitability
  • Advertising to sales ratio
  • Inventory Turnover
  • Net Sales to Net worth
  • Asset Turnover
There can be hundards of KPIs for any particular business sector.

Some of the concepts which I promised to explain in my earliar post are explained one by one here:

What is Single Version of Truth?
Realizing the limitations of ERP reporting, middle managers/analysts mostly use spreadsheets (mostly excel) to present information / analysis to business executives or to support their day to day functions. Usually these spreadsheets are shared with collegues and management as email attachments. Sometimes converted into PDF or word formats as well. These spreadsheets and documents are called “Unstructured data sources”. There are certain inherent limitation with this approach, one obviously being difficulty to apply version controlling if data gets updated. Analysts have to prepare a new spreadsheet every time by seeking help of IT to pull data from source systems (e.g. ERP, legacy applications) and apply aggregations and other statistical/mathematical functions manually. As a result sometimes, values for certain KPIs may be different in different spreadsheets prepared by different analysts. On the otherhand, having a BI solution for analytical reports, which gets all the data from a central data warehouse, eliminates the chances of multiple values for same KPI. This is why it is referred as Single Version of Truth.

Adhoc reporting
It is basically the same thing for which analysts use spreadsheets. Means those reports which are not present in your ERP or legacy applications. A Business intelligence solution offers the flexibility and powers of custom reports development to business analysts even if they don’t know about the structure of underlying data elements. The view of report writing tool that they see contains data elements in business terms like Sales, Profit, Year, Month etc. With drag and drop functionalities, they can quickly create reporting different measures against different dimensions

Slicing & Dicing
The concept of Slicing is much like filtering the data. This is used to view only that data which is necessary for our current analysis For Example suppose we are viewing a Quarter-on-Quarter revenue comparison report. Now we need to see the 3rd quarter revenues in detail so we slice the report to display only third quarter’s report. It depends on the system or user wether it is displaying an aggregate revenue report for full quarter or displaying it in Month-on-Month comparison. By the way, in accounting terms, these comparisons are called horizontal analysis.
Dicing stands for transposing the X and Y dimensions. Like pivoting or cross tabbing

There is a term in BI & DWH which is called Visualization. Visualiztion means representation of information in meaningful way like charts, graphs, tables etc. A dashboard is a place where you put all the visual representation of your information. Using charts, tables, gauges etc, you can display information (e.g. your KPIs) in a very eye-catching and to-the-point way. Here are some of the screenshots from some dashboards.

Figure 1: A Business Monitoring Help Desk System Dashboard

Figure 2: A Banking system Dashboard

Figure 3: A sample Airline executive Dashboard
Drill Down and Drill Across
Drill down means viewing information at a more detailed level for same dimension. For example, when you are viewing an annual report (time dimension), you can drill it down on time dimension for half year, quarter or month.
Drill across refers to drilling from one dimension to another on same hierarchal level.

In this topic, I have tried to present a business case that why business intelligence is necessary for organizations. It is not leisure. It is a must. People argue that it is expensive. Sounds familiar? Didn’t you hear it when ERPs came into market?
In my next post, i will explain about how this solution works. It will get a bit more technical but intended audience would be again business users. Feel free to send in your opinion or questions in the comments. After all i am writing all this to communicate with people like you out there.

Sunday, February 22, 2009

Horn Vs Headlights

After posting the blog titled Difference between BI and ERP reports couple of days ago, I got a lot of emails and messages. Some of them were appreciating, some were asking more details which i will cover in next posts. But one question which got more attention came from a marketing guy who asked me that shouldn't it be more reasonable for companies to spend in marketing/advertisement instead of business intelligence at this financial crisis time to get more business?

Well, every body has his/her own point of view on this but my opinion is that advertising is like a Car Horn which sounds loudly and draws the attention of people towards the car (or your business) whereas business intelligence is like a car's headlight which shows you that if you are on track or not and what is in front of you. (There are a lot of other things in a car which could be referred as BI, say, car's dashboard, windscreen etc but in this example, headlight fits appropriately :) ).

So what do you think. At the time of this economic & financial crisis when you are driving your business in dark and you don't exactly know what is going to happen, what do you need? Horn or Headlights ?

Wednesday, February 18, 2009

Difference between BI and ERP reports

Yesterday I had a meeting with a potential client in Abu Dhabi and a question popped up. What is the difference between reports/information obtained from an ERP and that of a BI solution?

I have seen this question on numerous discussion boards, forums and blogs and I felt that there are certain buzz words which are been repeatedly being told to audience without realizing that audience understand it or not. Some common phrases like

  • “ERP is for data input and BI is for data retrieval”.
  • “ERP is an OLTP system and BI is an OLAP System”
  • “You can do more analytical reporting in BI”.
  • “BI provides single version of truth”
  • “ERP reports are for day to day needs only” etc
These phrases still do not clear the concept in the mind of a non-IT business user that "why they need a BI solution when their existing ERP solution is already generating reports for them".

I will try to explain the difference for a non-IT business user giving some examples. Two phrases which I mentioned earlier were:

“ERP is for data input and BI is for data retrieval”…
“ERP is an OLTP system and BI is an OLAP System”…
That’s right. ERP software being an Online Transaction Processing (OLTP) system is used to record/edit transactions as and when these happen. The data architecture is designed in such a way that it provides maximum speed in recording a transaction keeping disk space utilization at a minimum. For those of you know who know about IT, this is the application of normalization in a database environment. BI on the other hand being an Online Analytical Processing (OLAP) system provides you robust access to different reports, dashboards and balanced scorecards. Now lets see how ERP reporting is different from BI reporting using a very simple case scenario.
Alpha Company, Inc is in the business of Food & Beverages. Mike is company’s Sales Director and wants to see the sales report for January 2009. A typical ERP system will generate a report like this:

Now what if Mike wants to analyze the report based on geographic region and compare it with last month’s sales. He doesn’t want to see the products appearing row wise. Instead he requires products to appear column wise and show the sales amount of respective geographic region in rows. Developer Buddies!! Remember cross tab / pivot table reports ??? But don’t think Mike’s expectations are going to end here. He also wants to compare these figures with previous months figures in the same report. Wait here. Still don’t think its end of the demands. Mike also wants to show the dropped sales figure in different color. So it needs to be like this

A typical ERP system doesn’t have enough capability to support this. Although there are cross tab / pivot table reports available in latest tools like ORACLE and Microsoft SQL Server 2005 (and above) but they are:
  1. Very Complicated,
  2. Very Slow
  3. Put a lot of burden on processor
So Mike might have to wait 10 minutes or more for the report shown in figure 2 using an OLTP system. But using an OLAP system, it will only take a few seconds. I have explained three concepts in the figure 2 that a BI system is capable of and those are:

  • Time series comparisons (between Jan 09 & Dec 08)
  • Drill Down (e.g. on regions)
  • Ability of OLAP to do cross tab/pivot table format
I will need at least 2 to 3 more posts to further explain/cover rest of the powers of BI solution like slice & Dice concepts, Dashboard Gauges and Scorecards, etc. Also I will explain about the single version of truth phenomenon. But developers!! please don't assume that you can accomplish the required results putting all data (including precalculated data) in one single table. This is a big misconception among developers and you will know it when i will explain the concept of dimensional data modeling in my next blogs i.e.what is the difference between a normalized relational database model (used in ERP) and a dimensional data model (or the data warehouse used for BI). That would be of much interest for those who are already in the field of ERP and want to know more about BI.

Watch out for my next post on this blog. Your comments/thoughts are always welcome.