Posted on Leave a comment

Business Intelligence Competency Centres

Business Intelligence strategy is key to success.

Want to implement a BICC? Here’s an introduction.

Your Business Intelligence investment takes time, money and effort to realise and so should be properly looked after. Your Business Intelligence implementation should be designed to meet the strategic objectives of your BI strategy and these objectives should fulfil your vision. Your strategy will be realised through your tactics and BI operational model. A key component that will help you fulfil your vision is the Business Intelligence Competency Centre (BICC).

Business Intelligence strategy is key to success.Your BICC will act as your BI Centre of Excellence; it will help to ensure benchmark standards and formalised and documented BI process and the governance around it. As the BICC matures it becomes the stable BI mechanism for BI services and development and through which you can pilot and roll out new BI tools to the user community. It will also help you avoid the BI pitfalls such as BI silos.

To establish your BICC you will need to make decisions in several key areas. Here are some examples:

  • Who will be the overall sponsor?
  • What services will your BICC offer?
  • What are your BI processes? For example, what is the process that a key user should follow in order to realise self-service BI?
  • What governance surrounds your BICC process? For example, what should and should not key users do whilst practising Self-service BI?
  • What is the development process within the BICC?
  • How will your off-shore development model work?
  • How will your BICC organisational structure work and who and how will you recruit?
  • What is your communication strategy around the BICC?
  • How will your funding model look?
  • How will your training model look?

Your BICC should be scalable and will grow with you as your organisation grows. Your BICC should also be specifically designed to meet the needs of your organisation, and to this end it can be tailor made. That said there are often common themes and activities that occur within the BICC.

Here are some example activities that your BICC might manage and conduct:

  • New BI projects
  • Change requests
  • Encyclopaedia maintenance
  • Standard report library management
  • Universe maintenance
  • Business analysis
  • Dimensional modelling
  • ETL strategy and development
  • Report writing
  • Data extracts
  • Data mining and predictive algorithms
  • Lifecycle management

As the organisation grows, the BI system develops and more and more users want a piece of the action. This can place a great burden on the IT department. Therefore, one of your key strategic BI objectives should be to help your user community realise Self-service BI. This means that they will be competent to log on to the BI system and help themselves to pertinent data for their analysis and then share the information with other users. The benefits of realising self-service BI are numerous but without process and governance it can become chaotic. The BICC should be the genesis of BI process.

With a clear BI process and communication everyone should understand what is going on. When the process is well managed, order will be maintained and lead to success. The process should be monitored so that if it starts to deviate it can be corrected (refer to Six Sigma process management for more information). If the process continues to deviate unchecked it will become a process out of control. This can lead to inefficiency, unnecessary stress and fire fighting.

If you’re a small to medium sized company establish your BICC footprint as early as possible and plan for it to grow with you. If you’re a medium sized to large company you may already have many BI users in your community. Mistakes in BI process and governance can be painful because BI has high visibility and happens directly in front of and is felt by end users. If you’re experiencing end user grumblings, IT backlogs or high and increasing Total Cost of Ownership revisit your BICC management strategy.

Posted on Leave a comment

End To End BI 1

End to End BI Recommendations

This is the first in a series of short articles elaborating end to end BI philosophies and methods.

In the end to end BI philosophy (referred to as Cornerstone Solution® by BI System Builders) the BI component of the data warehouse is considered to consist of four layers.  The data warehouse is not regarded as simply a set of physical tables and views on a RDBMS.

The four layers are the Staging Layer, the Data Mart Layer, the Semantic Layer, and the Presentation Layer. Collectively these can be thought of as a Business Intelligence Data Warehouse (BIDW). This is an important principle because this way of thinking engenders the beginning of an end to end BI mindset.

Achieving a successful BIDW commences with modelling the data mart layer according to business user requirements. Committing to undertake this activity first becomes a catalyst to all other necessary requirements to create an end to end BI solution:

  • The Business Architecture is considered (‘as is’ and ‘to be’) and the Business Event Analysis and Modelling (BEAM) methodology is used to understand the business requirements. This will result in the development of a set of logical dimensional models that will later directly translate to physical data warehouse tables. These physical models form the ETL target tables in the data mart layer.
  • Data profiling of source data should now be carried out and fields mapped from source systems/ source files to staging tables. This activity will enable the commencement of ETL job development to populate the staging tables. Note that a source for BI may be among others a flat file, third party data, a legacy system, an ODS, or a 3NF data warehouse.
  • Fields are now mapped through from staging tables to data mart tables enabling further ETL jobs to be developed.
  • The semantic layer is configured as an abstraction of the data mart tables for business use and querying purposes. It’s a good practice to start this early as it often illuminates any flaws in the dimensional design, thus de-risking the programme.
  • BI reports can be developed in the presentation layer for information consumer purposes.

The next article will be a short introduction to sizing, hardware and BI Platform for the BIDW.

Posted on Leave a comment

ETL Data Services

A critical component in the BI system is the ability to take your source system data, clean it, and then load it into data your warehouse. It is this quality assured data that forms the backbone of your ‘single version of the truth’ in business intelligence. To achieve the timely loading of quality assured data a software program known generically as an ETL tool is used. We’ll take the SAP BusinessObjects suite as an example. The tool is based on an ETL program originally known as Data Integrator. Data Integrator is often used with another component tool known as Data Quality. As its name suggests Data Quality provides advanced data cleansing capabilities. Metadata Manager is a third component tool that can be used closely with Data Integrator to provide visibility into data lineage and data dependencies. There are several similar ETL tools in the market the best known of which are Informatica and Microsoft’s SQLServer Integration Serices (SSIS).