Sie sind auf Seite 1von 3

For DWHBI, it requires 4 components, namely:

 Data Integration, the ETL


 Data Design, Data Marts
 BI Layer
 Data Access.

Reports
C
Reports
BI
ETL Data Marts Layer Reports

Reports

Reports

A Typical BI System

Here are the descriptions of activities for each components

THE ETL

It’s otherwise known as Extract, Transform and Load. In order to build the Data marts, data from various
sources (Credit Risk Management, HR, ERP etc.) need to be extracted and brought to the FMBN BI
environment. After extraction, the data needs to be transformed. Data profiling and data cleansing are
core activities done at this stage.

Component Summary

1. Data Gathering
2. Gap Analysis
3. Data Extraction
4. Data Profiling
5. Data Cleansing
6. Oracle DBA activities.
7. Component Testing
8. UAT
9. Process Document and System Document are provided.

Duration: 2 - 3 weeks

DATA MARTS
A data mart is the access layer of the data warehouse environment that is used to get data out to the
users. The data mart is a subset of the data warehouse and is usually oriented to a specific business line
or team. For FMBN the following subject are scoped. Data are transform to model and loaded into data
marts using the Fintrak BI model for Credit Risk Management, HR and ERMS. The model comprises of
the following subjects:

1. Credit Risk
2. HR
3. ERMS

The BI model are of 2 types, logical and physical model.

Component Summary

1. Logical Model
2. Physical Model
3. Data Staging (ODS or PSA)
4. Data Marts - Credit Risk, HR, ERMS etc.
5. Security
6. Component Testing
7. UAT
8. Logical and Physical model documents.
9. Data Dictionary

Duration: 2 - 3 Months

BI LAYER

Different tools call this layer by different terms: project, universe, catalog, cube, framework, or semantic
layer. Depending on the tools used, this layer is either an abstraction of data stored within the
DWH/Data Marts, or a copy on disk or memory (often in a proprietary format) that allows easy, fast, and
consistent reporting. This data stores a pre-aggregated data hence enable trending and insights. The
purpose of this component is to store and retrieve data, NOT to accept input.

Component Summary

1. Build Cube or abstraction data layer.


2. Create Measures
3. Create Dimensions
4. Create Business rules
5. Create KPIs
6. Security
7. Component Testing
8. UAT
9. Cube Dictionary

Duration: 1 - 2 Months
DATA ACCESS

The Access Layer of the Business Intelligence component defines the functions and services to access BI
analytics with minimal effort. Access through thin client, widely available browsers, and portal solutions
that add value through filtering and organizing capabilities are presented as key strategies within this
section of the framework. The following type of reports will be rendered.

 Dashboard
 Standard Reports
 Ad-hoc Reports or Self Services
 Mobility
 KPI and Scorecards

Examples of Access Layer tools include:

a. Web Browser - OBIEE, SSRS


b. Portals - OBIEE, SharePoint, Power BI
c. Devices - Mobile Phones, Tabs
d. Web Services - as provided by Fintrak

Component Summary

1. Report design Specification.


2. Create Report portal
3. Build Standard Reports.
4. Build Dashboard.
5. Build KPI and Scorecards.
6. Enable Self Service
7. Security
8. Component Testing
9. UAT
10. Report design Specification Documents

Duration: 2 - 3 Months