Posted on

The End to End BI Concept

Considering the Full Landscape

Cornerstone Solutions® use an End to End BI approach and here’s why. When thinking about Business Intelligence architecture we need to consider the entirety of the component parts as a whole and not simply individually. In other words consideration is made of the full BI system as a whole and the individual components are not treated in exclusivity of each other. This is because the components will need to act interdependently regardless of whether they have been procured from a single or multiple software vendors.

In this respect the BI system is similar to the human body i.e. everything is so closely related that a felt symptom in one area (a pain in the arm) may be caused by an unseen symptom in another part of the body (a problem with an internal organ). To relieve the pain felt in the arm we treat the unseen causal effect in the internal organ. The same concept of unseen relationship and causal effect applies to the Business Intelligence system. Data flows from end to end through the Business Intelligence system in a similar way to blood circulating in the body and must not be blocked, lost or corrupted at any stage. The BI Architect must ensure this.

End to End BI
The components in the BI system are akin to a linked interdependent chain

Interdependency of the BI system

The early phases of a BI implementation can be usefully considered as akin to those of the Rational Unification Process (RUP) stages of Strategy, Inception, Elaboration, and Construction. A well defined BI strategy is very important. However, perhaps paradoxically the Construction phase is often delivered using an Agile delivery method.

Construction frequently commences with source system analysis, end user requirement gathering and the installation and configuration of the software components. If using SAP Business Information Warehouse, cubes and queries will be developed, or if a relational platform is used a dimensional modelling exercise is undertaken and then the physical tables are developed. The ETL system is designed and developed and reports and dashboards are built.

The relationship between these things is one of interdependency. It’s like a linked interdependent chain. This is why in the implementation methodology of BI System Builders we practice our philosophy of End to End BI. End to End BI takes the view that as each component in the BI system has interaction with and therefore dependency on its related components, BI Breakpoints can occur. BI System Builders take full consideration of the interdependencies in the landscape to ensure prevention rather than cure in their End to End BI project delivery method.

Posted on

Business Intelligence Architecture

Architecture that stands outCreating BI Architecture That Stands Out

In essence Business Intelligence is about taking raw data and turning it into information and then using that information to do intelligent business. The process of both transforming the data and consuming it as intelligence occurs in the BI system. The effectiveness of the BI system is dependent upon the quality of the overall BI architecture. Planning the BI system architecture occurs very early on and there is an art to getting it right. BI System Builders recognise that it takes wide and in-depth knowledge and experience to effectively make consideration of the full BI system in the early design stage of the Business Intelligence architecture. At this very early stage thinking may be embryonic and the components do not yet physically co-exist in the system. The skill set to visualise at this level can be sparse on the ground but the failure to do so can lead to consequent sub-optimal BI systems being developed. At their worse these BI systems run the risk of becoming expensive white elephants. They have taken a lot of effort and budget to implement but in the final analysis the end user community cannot access the critical information that it requires.

So what are the key areas at the macro level that constitute the Business Intelligence architecture and hold interdependencies?

Continue reading Business Intelligence Architecture

Posted on

Performance Tuning

It is both frustrating and unnecessary to endure an under-performing BI system. If you are on the BI DIY road you will find several articles and whitepapers on this website that may help you by pointing you in the right direction.Max Power

Performance optimised code for Web Intelligence is intrinsically tied into a relationship with the SAP BusinessObjects universe. There is a short article on this entitled: Increased Performance Through Optimised Universe Design. There are also various techniques that can be employed such as Improving Web Intelligence Deep Drilling Capabilities with Vertical Hierarchies.

However, for optimised performance the data warehouse design must be given serious thought, consider The Aggregate Advantage. Similar principles hold true if you are using the SAP Business Information Warehouse with Web Intelligence and need Cube and Query Design for Performance Boost.

It is always advisable to give consideration to Sizing, Hardware & Licensing Models before implementing your BI system, especially where the full SAP BusinessObjects Enterprise is to be deployed.

We will be adding many more whitepapers and helpful information as time progresses and you may also find our videos on this website and YouTube of some help. But, if you are experiencing issues that you cannot seem to rectify you can engage us via our Contact Page.