Elvis Pereymer will introduce the key concepts of implementing a Data Warehouse, with a focus on data access for users like business analysts, product managers and other decision makers who need the insight that can be obtained from such a system.

1. PRESENTED BY: ELVIS PEREYMER Introduction to Data Warehousing 9/17/11

2. Data Warehousing Presentation Topics 9/17/11 What is a Data Warehouse? Why do I need a Data Warehouse? What are its goals? What are its objectives? Where does “Business Intelligence” fit here ? The software products that present the data warehouse data to users are sometimes called Business Intelligence Tools. Demo of “Pentaho” – an Open Source Business Intelligence tool connected to an already built Data warehouse. Q & A

3. Many names for the same thing 9/17/11

6. Executive Information System

8. Executive Information System

9. Management Information System

11. Executive Information System

12. Management Information System

13. Analytics Application

15. Executive Information System

16. Management Information System

17. Analytics Application

18. Reporting Systema system for helping companies get the information they want, when they want it, and how they want it - from one single source.

19. Purpose of a Data warehouse Establish the foundation for Decision Support Decision process of an organization will involve analysis, data mining, forecasting, decision modeling etc. By having a common point, which can provide consistent, quality data with high response time provides the core enabler for making fast and informed decisions. 9/17/11

20. Why do I need a Data Warehouse? Current way of getting data or reports is not ideal 9/17/11

21. Why do I need a Data Warehouse? Current way of getting data or reports is not ideal Dependent on a resource such as a developer 9/17/11

22. Why do I need a Data Warehouse? Current way of getting data or reports is not ideal Dependent on a resource such as a developer someone who knows your companies underlying database structure and is familiar with a query language such as SQL used to retrieve data. 9/17/11

23. Why do I need a Data Warehouse? Current way of getting data or reports is not ideal Dependent on a resource such as a developer someone who knows your companies underlying database structure and is familiar with a query language such as SQL used to retrieve data. Limited to Standard Reports built thereby limiting you do ad hoc reporting 9/17/11

24. Why do I need a Data Warehouse? Current way of getting data or reports is not ideal Dependent on a resource such as a developer someone who knows your companies underlying database structure and is familiar with a query language such as SQL used to retrieve data. Limited to Standard Reports built thereby limiting you do ad hoc reporting Performance reasons limit you to running reports during “off peak” hours 9/17/11

25. Why do I need a Data Warehouse? 9/17/11 Multiple source systems collecting similar or related information. CRM, ERP, Operational Databases, Spreadsheets Operational Databases may be archived and considered to be a separate source system

26. Why do I need a Data Warehouse? Summary of existing Reporting problems 9/17/11

27. Why do I need a Data Warehouse? Summary of existing Reporting problems Difficulty in accessing your data. 9/17/11

28. Why do I need a Data Warehouse? Summary of existing Reporting problems Difficulty in accessing your data. Unable to perform ad-hoc reporting 9/17/11

29. Why do I need a Data Warehouse? Summary of existing Reporting problems Difficulty in accessing your data. Unable to perform ad-hoc reporting Not aware of “All” the data that is tracked in your systems. 9/17/11

30. Why do I need a Data Warehouse? Summary of existing Reporting problems Difficulty in accessing your data. Unable to perform ad-hoc reporting Not aware of “All” the data that is tracked in your systems. Performance issues. Data is not optimized for reporting. 9/17/11

31. The Value of the Data Warehouse 9/17/11 Integrated Multiple Source Systems Common Terminology Consistently Updated

32. The Value of the Data Warehouse 9/17/11 Time Variant Data in the Warehouse is associated with a point in time Essential for time-series historical analysis and forecasting

33. The Value of the Data Warehouse 9/17/11 Non-volatile Once loaded, data does not change. The answer to a given historical question will not change based on the time the question is posed to the warehouse.

34. The Value of the Data Warehouse 9/17/11 Strategic Analysis Historical analysis Forecasting analysis Evaluation of performance to corporate strategic goals Discovery of revenue opportunities Cost reduction

35. The Value of the Data Warehouse 9/17/11 The Data Warehouse Defined: Integrated Time Variant Non-volatile Strategic Analysis Tool (Business Intelligence)

36. Demo Time! 9/17/11 Sample Data warehouse put together using Pentaho (an Open Source Business Intelligence solution)

37. I Want One! 9/17/11 Plan! Plan! Plan! Resources Experienced DW Architect Programmers Familiar with Legacy Systems Users Familiar with Legacy Data Thank you, Elvis Pereymer Elvis.pereymer@gmail.com (917)754-4638

38. I Want One! 9/17/11 How long will it take? On going project. Depends on the amount of data sources you have and the resources that understand the data sources. Suggestion is to start with the Agile methodology and build “data marts” per subject area.

39. I Want One! 9/17/11 End User Presentation Tools Business Objects Cognos (Powerplay, Impromptu) Microsoft Business Intelligence Suite Pentaho BI Solution – Open Source Many, many others!

40. Summary 9/17/11 DW are used for Decision support Analysis Not the same as your operational systems Designed badly, they are not useful