RBRS Cognos Reporting

IT development departmentDWH&BI Unit

Belgrade, September 2011Marijana Tomašević

2

Agenda

� DWH, BI and Cognos in Raiffeisen Bank

� Data Modeling

� Cognos Applications in RBRS

� Specific Cognos Features In Use – Tips and Tricks

� Conclusion

3

DWH, BI and Cognos in Raiffeisen Bank

Source Source databasesdatabases

Data marts & Data marts & Analytical SystemsAnalytical Systems

Other Other sourcessources

FrameworkManager

FrameworkFrameworkManagerManager

DWHDWH

CBSCBS

DWHDWH

Data MartsData Marts

AnalyticalAnalyticalSystemsSystems

ReportingReporting

GDWH in Raiffeisen Banka is a Raiffeisen group wide Oracle solution with local extensionslive since December 2004.

4

For 3 Years in-house team of 2 - 3 developers doing both, DWH (mapping, ETL, operations, testing etc) and BI matters (metadata preparation, standard reporting, data mart preparations, etc).

IT DWH & BI Unit created with two teams: DWH (3) and BI (3) in 2008.

DWH, BI and Cognos in Raiffeisen Bank

Q2Q2

Cognos 8 BICognos 8 BICognos MR3Cognos MR3

20020055 20092009 20112011

Q2Q2 Q4Q4

Cognos 8.4Cognos 8.4

20072007

5

With increasing number of diverse reporting requirements our motivation was to:

� Create data marts and Cubes that would satisfy the majority of requirements, in order to facilitate development and raise data quality with one source for many reports/departments in the Bank.

� Educate Cognos power users to create ad-hoc queries and reports by themselves from prepared data marts.

DWH, BI and Cognos in Raiffeisen Bank

6

BI Initiative For IT & Business Users

Cognos training by our local Cognos partner in December of 2007:� Cognos 8 BI Reporting and Modelling� Cognos 8 BI Analysis and OLAP Modelling

Locally organized workshops introducing Reporting & OLAP and Data Mining tools’ capabilities and added value for daily user operations.Gap analysis and functional specification for Data Marts for different units performed.

7

Currently, there are three active Cognos servers:

� One with version of Cognos 8.2, test and production server at the same time.

� Two with version of Cognos 8.4, one test and one production server.

System Architecture

8.4 8.48.2

8

Framework Manager used by IT for preparing reporting metadata.

Query Studio is not used in RBRS as it turned out not to be acceptable choice with huge amounts of data they deal with.

Report Studio is used by Report Authors when creating Ad-Hoc and classic reports.

PowerPlay is used by certain departments for exploring data received from HO.

Analysis Studio was explored a little from our side, but is currently not used by business users.

Cognos Tools In Use

9

RBRS Bussiness Departments – Cognos Users

Users of Cognos portal and Cognos Applications are members of different departments within RB :

� Back Office Departments (Accounting...)

� Analysis Departments (Business Analysis...)

� Sales Departments (Retail Sales Finance...)

� Reporting Departments (Controlling...)

� Risk Departments (Market Risk...)

10

Satisfaction with Cognos tools can be seen through continually increasing number of active users.

Number of Users

N um b er O f D istinct Cognos Users

0

10

20

30

40

50

60

70

20

08

.06

20

08

.08

20

08

.10

20

08

.12

20

09

.02

20

09

.04

20

09

.06

20

09

.08

20

09

.10

20

09

.12

20

10

.02

20

10

.04

20

10

.06

20

10

.08

20

10

.10

20

10

.12

20

11

.02

20

11

.04

20

11

.06

20

11

.08

11

Agenda

� DWH, BI and Cognos in Raiffeisen Bank

� Data Modeling

� Cognos Applications in RBRS

� Specific Cognos Features In Use – Tips and Tricks

� Conclusion

12

Data modeling

First Cognos FM models were based on standard DWH model.

Experience with such models indicated that with quite huge amount of data that RBRS has, choosen approach was not good enough. Cognos had problems with calculating data required for reports.

Present practice is to create Data Mart for FM model.

So, we switched to generating Data Marts precalculated and suited to user needs. In that way, Cognos Applications are used to show prepared data rather than to calculate data.

13

Data Marts – Develop Once Use Many Times

� Created to fulfill requirements of different business segments.

� Created on monthly or daily basis.

DWHDWH

Daily Data MartsDaily Data MartsMonthly Data MartsMonthly Data Marts

14

Agenda

� DWH, BI and Cognos in Raiffeisen Bank

� Data Modeling

� Cognos Applications in RBRS

� Specific Cognos Features In Use – Tips and Tricks

� Conclusion

15

Cognos Applications

� Cognos as front-end for MIS System

� 5 major Cognos applications: KPI portal, RORWA Tool, Deposit DM, DQI Engine and Cost Accounting Application

� 7 Data Marts

� 5 Cubes

� > 200 locally developed reports, 80 centrally provided by HO.

16

Cognos Applications – RORWA Tool

17

Date, analytical and instance selection

Top 4 employees by difference from

benchmark value

Top 4 empoyees by improvement from last month value

KPI Portal Page - Details

18

Historical KPI

KPI Portal Page – History Overview

19

� DWH, BI and Cognos in Raiffeisen Bank

� Data Modeling

� Cognos Applications in RBRS

� Specific Cognos Features In Use – Tips and Tricks

� Conclusion

Agenda

20

FM defined data security concept. Data is filtered by membership of Cognos users groups within defined Cognos roles created based on customer segmentation.

Implementation Of Data Protection

21

When using query items from secured query subject in creating a report, where clause contains security check that returns only data allowed for user running or creating a report to see.

Implementation Of Data Protection

22

Example Of Visibility Of Report Navigator

Simmilar security approach implemented in regular reports is used to show different links to different reports, so depending on user logged, Deposit Navigator interactively changes.

23

Example Of Report Pages Rendering

The same report renders differently depending on user logged, and parameters supplied.

24

Cognos Features In Use – Drilling

Detail records are exported to excel files for further analysis

Life before Cognos: complex gigantic excels or access databases with all data for analysis/troubleshooting. With Cognos: targeted reports with drill through capabilities for narrow search results and faster analysis.

25

Native cube vs user expected drilling

Cube report shows summaries accross different dimensions. Cognos enables drilling up and down within a cube.

For user convenience and targeted analysis, detail records are exported to excel files.

26

When distributing report results via email, few scenarios exist:

� Internal DQ reports scheduled to be run after daily DWH load. Excel files sent via email.

� Bursted daily reports with details of products for customers are mailed to relationship mangers in charge. Their superiors receive same reports with the data of all RELMs they are responsible for.

� Some users receive only notifications that reports are run, results are saved on Cognos server, and can be downloaded via link indicated in email.

Distribution Of Reports

27

Scheduling of a single report

� Start by using triggers� Check every few hours whether certain conditions are met and

then start (conditions ranging from finishing the creation of the data mart to finishing the import of external files recieved through file transfer software).

Run a set of reports (business request)

� Jobs and events are used to runset of reports every working day bytrigger after certain conditions are met.

Cognos Features In Use – Scheduling Of Reports

28

Example of a daily reconciliation report.

Scheduling Of a Single Report

29

Trigger Implementation

DWHDWH

Data Stage job calls NRPE script located on Data Stage Server.Script contains address of Cognos Server and name of the Cognos trigger.

30

Trigger Implementation

When scheduling a report, user should only specify the name of the trigger.

Trigger is located in a predefined folder on the Cognos server.

31

Cognos Features In Use – Bursting of Reports

32

� DWH, BI and Cognos in Raiffeisen Bank

� Data Modeling

� Cognos Applications in RBRS

� Specific Cognos Features In Use – Tips and Tricks

� Conclusion

Agenda

33

Cognos enables us to use one well defined single-point-of-truth data source to:

� Secure and protect our data

� Analyze data with ease

� Create personalized reports without IT resources

� Receive results in most convenient and timely manner

Benefits

TRERWA

34

Questions

35

Appendix

36

Modeling Approach

Best practice relational model is made up of few layers, for instance:

� A “Database View ”, where the database objects (tables, views) and their relationships are mapped in an almost one-to-one direct manner to the ReportNet model.� A “Business View ”, where query elements are structured and named in a more business oriented manner, hiding the database structures (tables, views) and their relationships from the user.

Database View is used as the basis for the Business View.

Relationships are always modeled in FM when models are used by power users.

37

Cognos Authors who use DWH based FM model sometimes (from their own words, 1-2 times a month) expirience prolonging of run time of Ad-Hoc reports, which is usually resolved by analysing Cognos generated SQL, and reconstructing the report with our help.

This is probably due to refreshed statistics on some of the DWH tables, but we have never investigated the reasons for such a behaviour.

Performance Issues Cognos 8.2

38

When in process of creating Cognos Cube, Cognos can run out of temporary space.

While calculating data for cube, temporary working file can require up to 100GB, although cube ends up with size of less than 2GB. Thisdepends on number of categories and on number of values within categories. Error thrown hascode TR0114*. IBM advises: To estimatehow much disk space you need to createa cube, multiply the size of all data sourcesby 3.5. To locate the temporary work files,check the Directories tab of the Preferencesproperty sheet.

Performance Issues Cognos 8.2

*Transformer cannot write in the model temporary file.Please check if there is enough free disk space in the temporary directory.

39

Problems with local proccessing that occures on Cognos Server.Cognos is creating temporary file in folder which can be located on the path C:\Program Files\cognos\c8\temp.

When testing report which was combining data from two different databases, temporary file created has reached size of 10GB, and the error UDA-TBL-0004* was thrown.

Resolved by optimizing queries to deal with onlynecessary rows and columns, thus reducingnumber of rows processed.

Performance Issues Cognos 8.4 Test Server

*There was a Write error while processing a temporary file.