Business Intelligence by

1
Business Intelligence by

• Greeshma Malgireddy

2
Introduction

• Business Intelligence (BI) systems facilitate the
  analysis of volumes of complex data by providing
  the ability to view data from multiple
  perspectives.
• An optimum business intelligence application
• Gives users access to data at various levels of
  detail.
• Allows users to request information and have it
  delivered to them accurately and quickly.

3
BI Architecture
The diagram above illustrates the common setup
for standardizing data from source systems and
transferring that data into Micro Strategy.
4

• Source Systems for data collection
• Source systems refer to any system or file that
  captures or holds data of interest.
• A bank is an example of business with source
  systems.
• A source system is usually an online Transaction
  processing (OLTP) system. These OLTP systems are
  the databases or mainframes that store real-time
  processing data.
• The ETL process consolidates data so that it can
  be stored in a data warehouse.

5
ETL Process

• The Extraction, Transformation and Loading (ETL)
  process involves the following steps
• 1.Data is gathered from various source systems.
• 2.The data is transformed and prepared to be
  loaded into the data warehouse.
• 3.The data is loaded into the data warehouse.

6
Data warehouse for data storage and
relational design

• A well designed and robust data warehouse is the
  source of data for the decision support system or
  business intelligence system.
• The data warehouse provides the foundation for a
  robust online analytical processing (OLAP)
  system.
• Data here is typically read-only and is rarely
  inserted, updated or deleted.

7
The Micro strategy platform
8
Components

• Metadata
• 1. Configuration objects
• 2. Schema objects, include
• a) Facts
• b) Attributes
• c) Hierarchies
• 3.Application objects
• Intelligence server
• Desktop
• Web and web universal
• Project

9
The project design process
10
(No Transcript)
11
(No Transcript)
12

• The above snapshots show the actual client (Micro
  Strategy Desktop). This is a thick client where
  most of the Micro strategy functionality can be
  managed for the Desktop. All the schema
  objects(attributes, facts, hierarchies etc.) must
  be built from this thick-client.
• Based on the proper user privileges various users
  get different access to this interface.

13
The below snapshot shows attributes built from a
customer table. Each of these columns in the
customer table architected into Micro Strategy
with proper joins and business rules.
14
Given below is a sample report generated with
region Category and Sub Category which shows
forecast and Revenue based on these. Various
front settings and thresholds can be used to
change the colors (like the above indicate the
green and red based on the forecast
expectations).
15

• The above snapshot shows a thin client (Micro
  Strategy Web universal) where most users will be
  seeing this interface. The users login through
  either micro strategy integrated corporate
  portals or directly launching the Web universal
  (Micro strategy deployed in a web server).
•  
• The users in this interface can be given access
  to built various run time objects like filters
  (used to filter a part of data), metrics(used for
  calculated columns like standard deviation,
  average etc.,) 
•  

16
References

• www.microstrategy.com/software
• www.intelligententerprise.com