AAO BI Portfolio


Published on

Numerous samples of the work that I did during the SetFocus BI Master's Program.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

AAO BI Portfolio

  1. 1. Al Ottley<br /><br />Business <br />Intelligence <br />Professional<br /><br />AAOttley@gmail.com<br />www.linkedin.com/in/aaottley<br /><br />Colorado Springs, CO<br />719 306 2495<br />Business Intelligence Portfolio<br />© Al Ottley 2009<br />
  2. 2. Table of Contents<br />3<br />5<br />9<br />11<br />16<br />20<br />23<br />27<br />29<br />32<br />36<br />41<br /><ul><li> Overview
  3. 3. Transact SQL (T-SQL)
  4. 4. Dimensional Data Modeling
  5. 5. SSIS (SQL Server Information Services)
  6. 6. SSAS (SQL Server Analysis Services)
  7. 7. MDX (Multi Dimensional eXpressions)
  8. 8. Calculated Members and KPIs
  9. 9. Excel 2007 and OLAP
  10. 10. SSRS (SQL Server Reporting Services)
  11. 11. Performance Point Services (PPS)
  12. 12. SharePoint (SP/MOSS) Services
  13. 13. Experience Summary</li></ul>2<br />© Al Ottley 2009<br />
  14. 14. Overview-Introduction<br />Introduction:This portfolio contains many examples of my developmental skills working with all aspects of the Microsoft Business Intelligence Toolset.<br />Core Technologies Covered:<br /><ul><li>Microsoft (MS) SQL Server 2005, T-SQL and MDX Queries
  15. 15. MS Office Visio 2007
  16. 16. MS SQL Server 2005 Integration Services (SSIS), Analysis Services (SSAS), Reporting Services (SSRS) and BIDS </li></ul> (Business Intelligence Development Studio)<br /><ul><li>MS Office Performance Point Server (PPS) and Dashboard Designer
  17. 17. MS Office SharePoint (SP) Server 2007 (MOSS)</li></ul>Audience:<br /><ul><li>Business Executives and Partners
  18. 18. IT Directors and Project Managers
  19. 19. IT Professionals, Colleagues and Peers
  20. 20. BI and DW Analysts, Designers and Implementers </li></ul>3<br />© Al Ottley 2009<br />
  21. 21. Overview-Project Goals<br />Project Goals:<br /><ul><li>Design a Star Schema data model using Visio, both fact and related dimension tables—based on requirements and RDBMS tables.
  22. 22. Create a Staging Database, using Visio and the DDL created.
  23. 23. Create an ETL solution with SSIS, to update and modify the SQL Server 2005 staging database—Excel spreadsheets, flat files and relational tables are the data sources.
  24. 24. Create a star schema Analysis Services Cube, with SSAS—the staging DB is the data source.
  25. 25. Write appropriate MDX queries, define Calculated Members and business KPIs, with SSAS, to support requirements and implementation best practices.
  26. 26. Use Excel Services 2007 to display cube measures, dimensions and KPIs, displaying various KPI statuses and trends.
  27. 27. Produce detail and summary reports using Excel Services and SSRS.
  28. 28. Create scorecards, reports and dashboards with MS Office Performance Point (MOSS).
  29. 29. Centralize dashboards, scorecards and reports using SharePoint Services.</li></ul>4<br />© Al Ottley 2009<br />
  30. 30. Transact-SQL (T-SQL)<br />This query joins several tables to show the total Order Amount for each Company, Product Category and Product.<br />5<br />© Al Ottley 2009<br />
  31. 31. T-SQL<br />This multi-join query joins the Item and Reservation tables, with the Title table.<br />The result set shows which books have less than 15 copies available and for which there have been more than 50 reservations made.<br />6<br />© Al Ottley 2009<br />
  32. 32. T-SQL<br />This query loads a Date Dimension table, containing keys for proper ordering, descriptions for display purposes. Initially, this data will be part of an SSIS Staging DB and later part of an OLAP Cube.<br />7<br />© Al Ottley 2009<br />
  33. 33. T-SQL<br />This T-SQL Query, after various Staging Dimension Tables have been loaded, determines the Primary Keys and two Date Attributes that are required for a related Fact Table. <br />To find the correct Fact Table PKs, Business Keys (BKs) are matched on the appropriate Dimension table. <br />BKs were used in this case, as integer comparisons are much quicker than string comparisons.<br />8<br />© Al Ottley 2009<br />
  34. 34. Dimensional Data Modeling<br />These two Databases are the source DBs used in the design process for the Fact and Dimensional tables, first used in the Staging area and ultimately the OLAP Cube. The final design, based on business requirements, is seen on the next slide. <br />These DB diagrams were created from SSMS; not all of the relationships were captured automatically. The PrimaryCategories table is actually related to the PrimarySubBridge table, via the PrimaryCategoryID and PrimaryCategoryKey fields.<br />9<br />© Al Ottley 2009<br />
  35. 35. Dimensional Data Modeling<br />This is the final DB design for the Fact and Dimension tables, based on the source DBs and Business Requirements. <br />DDL, created during the staging DB design process in Visio, will actually be used to create these tables in a Staging DB. <br />Once data is cleansed and loaded into the staging area, via SSIS, this staging area will become the basis for the SSAS OLAP Cube.<br />10<br />© Al Ottley 2009<br />
  36. 36. SSIS (SQL Server Integration Services)<br />This is a “Master Package”, executing all the other packages in the Project--each loads a portion of the staging DB, later used to create the SSAS OLAP Cube. <br />The following two slides (12 and 13) show additional packages in this project. A third slide (14) shows a script that keeps track of running totals of Employee time sheets processed and other statistics. <br />11<br />© Al Ottley 2009<br />
  37. 37. SSIS<br />12<br />© Al Ottley 2009<br />
  38. 38. SSIS<br />13<br />© Al Ottley 2009<br />
  39. 39. SSIS<br />14<br />© Al Ottley 2009<br />
  40. 40. SSIS<br />This is the Expression Editor and Properties page, which in this case, are used to compose and prepare an e-mail notification when all of the Employee Time Sheets have been successfully processed.<br />Parameters and variables help in automating the message notification process.<br />15<br />© Al Ottley 2009<br />
  41. 41. SSAS (SQL Server Analysis Services)<br />The resulting SSAS OLAP Cube created from a Staging DB source.<br />16<br />© Al Ottley 2009<br />
  42. 42. SSAS<br />Here, two Dimension Hierarchies are created, within this particular dimension. <br />With Hierarchies, access to various levels, at report time, is easily accomplished, drilling up and down at will.<br />17<br />© Al Ottley 2009<br />
  43. 43. SSAS<br />Using the Hierarchy Browser allows you to see the values of each level of a defined hierarchy made during design time, in this case the Division Hierarchy. <br />When defining the hierarchy, parameters are modified so that more descriptive “names” are used, rather than the keys, which are typically used for ordering. This allows for a more “natural” and meaningful way to see the data.<br />“Codes” in an OLAP cube will never be seen by anyone looking at reports, based on such a cube. All reporting values are descriptive and take on a definite meaning.<br />18<br />© Al Ottley 2009<br />
  44. 44. SSAS<br />Here, we are using the Cube Browser in BIDS to “look” into the Cube, with the defined Division Hierarchy on the rows and Year Quarters on the columns. <br />Drilling down to various levels is easily done, using Hierarchies, showing various Cube Measure values at each level, which will automatically aggregate as the hierarchies are drilled down and up. <br />This allows one to see data (measures), and the corresponding aggregations, at any level of detail that is important to them.<br />19<br />© Al Ottley 2009<br />
  45. 45. MDX (Multi-Dimensional eXpressions)<br />Defined Members are used to give additional “information” and “value” to the MDX query results.<br />They are also used to help simply MDX queries and allow the reuse of defined members in several places.<br />20<br />© Al Ottley 2009<br />
  46. 46. MDX<br />The IIF (Immediate IF) function is used here to check that the divisor is not equal to zero. If this is the case, the function will return, in this case, “N/A”.<br />21<br />© Al Ottley 2009<br />
  47. 47. MDX<br />This MDX query is more complex in that only where data values exist, should they show up in the result set. <br />The Filter function, in each defined member, ensures that data exists, before summing values in each defined member.<br />22<br />© Al Ottley 2009<br />
  48. 48. Calculated Members and KPIs<br />This is a Calculated Member, defined in <br />BIDS, that will later be used in a KPI.<br />Notice the use of the IIF function, again to check for divisors that may be zero.<br />23<br />© Al Ottley 2009<br />
  49. 49. Calculated Members and KPIs<br />This is a KPI that uses the Calculated Member, from the previous slide. As part of the KPI is a Goal and an Expression that will determine “how close” a value is to a specified goal and to show, in this case, which traffic light will show up, based on “rules” in the expression.<br />24<br />© Al Ottley 2009<br />
  50. 50. Calculated Members and KPIs<br />This is a second Calculated Member that defines the Percent Increase in Overhead.<br />Two IIF functions are used here. The first, based on a business rule, checks to see if the Previous Quarter % is zero; if it is, make the value 1 (100%). The second checks to see if the divisor is zero.<br />25<br />© Al Ottley 2009<br />
  51. 51. Calculated Members and KPIs<br />This is the corresponding KPI to the Calculated Member from the previous slide. This KPI will show, on a Dashboard, in a simple graphical format, the status of the Percentage Increase in Overhead Cost.<br />26<br />© Al Ottley 2009<br />
  52. 52. Excel 2007 and OLAP<br />Excel 2007 easily allows Pivot Tables to be created. This simple spreadsheet was created by using a SSAS OLAP Cube as a data source, easily allowing various measures and dimensions to be added and removed, to show values at many hierarchical levels.<br />27<br />© Al Ottley 2009<br />
  53. 53. Excel 2007 and OLAP<br />Once again, using an OLAP data source, it is very easy to create a Pivot Table in Excel 2007. Once the pivot table has been created, it is very simple to create an accompanying chart. The chart uses the data that is currently displayed in the table. <br />As the filters in the table are changed, reflected changes are seen immediately in the chart. Even though the chart is based on table data, only the chart needs to be deployed to Sharepoint, if desired (see slide 39).<br />28<br />© Al Ottley 2009<br />
  54. 54. SSRS (SQL Server Reporting Services)<br />An SSRS Report containing several report parameters, two of them nested. The MDX query, that drives the report, is shown below.<br />29<br />© Al Ottley 2009<br />
  55. 55. SSRS<br />This SSRS Report uses cascading parameters, so that selecting a given Employee, only week ending dates where that employee actually worked are available for subsequent selection. <br />This report also lists and sums the hours worked for each week and each job, for the selected employee.<br />30<br />© Al Ottley 2009<br />
  56. 56. SSRS<br />Performance Point Server can easily use KPIs. It is also possible to use “KPIs” in Reporting Services.<br />This is done by using KPI-like images and using conditional expressions, based on data values, as when to display each KPI indicator.<br />31<br />© Al Ottley 2009<br />
  57. 57. Performance Point Services (PPS)<br />This is the basic design template for a KPI scorecard, as is typically developed in PPS. <br />This simple template will later be used in a full-blown KPI scorecard, showing Product Categories on the Rows and Yearly Quarters on the Columns.<br />The template will replicate itself as many times as is necessary (slide 37).<br />32<br />© Al Ottley 2009<br />
  58. 58. PPS<br />This is one of two supporting charts for the scorecard, based on the KPI created in the previous slide. In the final Scorecard, there will be two “hot links” to bring up the appropriate chart.<br />33<br />© Al Ottley 2009<br />
  59. 59. PPS<br />Here is where all of the elements are brought together for the final scorecard, including the KPI template, the two supporting charts, parameters and filters.<br />34<br />© Al Ottley 2009<br />
  60. 60. PPS<br />This is an MDX query for another report, which is the primary driver for the resulting report. It also contains a employee parameter, which is selected at runtime.<br />This report will be seen in the SharePoint section of this portfolio (slide 38).<br />35<br />© Al Ottley 2009<br />
  61. 61. SharePoint Services (SP)<br />Share Point is a web based service that is most commonly used to store various types of business reports in a centralized location, for easy access by many employees. <br />Reports can be deployed to SP from a number of sources: SSRS, Excel and Performance Point. Many other types of collaborative documents may also be stored in SharePoint, including Word documents and Excel spreadsheets. Also, reports can be scheduled for delivery by a subscription process.<br />Access to items may be limited by the use of Roles, so that everyone that is using Reports and Documents in SharePoint only sees them on a need to know basis. <br />36<br />© Al Ottley 2009<br />
  62. 62. SP<br />The hotlink that brought up this supporting chart is on the left, the “Sales Growth %” row header.<br />The is the final Scorecard and one of the two Supporting Charts that were created in PPS (some of the elements were shown in earlier slides). It was then deployed to SharePoint.<br />37<br />© Al Ottley 2009<br />
  63. 63. SP<br />The chart above is the result of the MDX query that was shown in an earlier slide (slide 35), defined in PPS.<br />The entire Dashboard, the chart and a supporting table, was deployed from PPS to SharePoint.<br />38<br />© Al Ottley 2009<br />
  64. 64. SP<br />This chart, along with a related table, was originally created in Excel 2007 (slide 28), using an OLAP data source. <br />The Excel chart, but not the associated table, was deployed to SharePoint via Excel Services. The chart still functions as it did in Excel.<br />Parameters were set up in SP to use the same parameters as were originally used in the original Excel table and chart.<br />39<br />© Al Ottley 2009<br />
  65. 65. SP<br />This is an SSRS report (see slide 30) deployed directly into SharePoint, without any modification to the parameter dropdown lists. They still function as they did in SSRS.<br />Additional effort is required to use the SP-styled dropdowns. Even deploying Excel reports to SP and using SP-styled dropdowns is much easier.<br />40<br />© Al Ottley 2009<br />
  66. 66. Experience Summary<br /><ul><li>18 years of varied Information Technology experience.
  67. 67. Microsoft Business Intelligence: SQL Server 2005 Integration Services (SSIS), Visio, T-SQL Queries, Analysis Services (SSAS), MDX Queries, Reporting Services (SSRS), Excel with OLAP, Excel Services, Performance Point Server (PPS/MOSS) and SharePoint (SP) Server.
  68. 68. Experience with MS SQL Server 2008: SSIS, SSAS, SSRS, MDX, T-SQL.
  69. 69. Unified Data Modeling: from Logical/Physical to Star/Snowflake.
  70. 70. Experienced, insightful and results oriented Information Technology professional with many notable successes in the Telecommunications Business: Business Marketing and Call Traffic Settlement initiatives.
  71. 71. Extensive participation and contribution to the development and implementation of specific client based solutions: supporting various business objectives and requirements.
  72. 72. Hands-on experience in various stages of systems development: requirements gathering, analysis and design, architecture, testing and support.
  73. 73. Motivation and guidance to other team members, for consultation and to facilitate timely project completion.
  74. 74. Extensive IBM mainframe (Z/OS) and midrange (UNIX) experience, with a variety of DBMS back ends: DB2, Oracle, Sybase, Informix and MS-SQL Server.</li></ul>41<br />© Al Ottley 2009<br />