1 / 32

You Can Get Fries and Coleslaw With The BI/DW Combo!

You Can Get Fries and Coleslaw With The BI/DW Combo!. Steve Bond, Consulting Director. BI Today BI Purpose Why BI Business Reflection The Roadmap The Framework The Business Design Development Implementation Project BI Successes. Agenda. Business Intelligence. Business Intelligence.

hestia
Télécharger la présentation

You Can Get Fries and Coleslaw With The BI/DW Combo!

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. You Can Get Fries and Coleslaw With The BI/DW Combo! Steve Bond, Consulting Director

  2. BI Today BI Purpose Why BI Business Reflection The Roadmap The Framework The Business Design Development Implementation Project BI Successes Agenda

  3. Business Intelligence Business Intelligence CPM – Corporate Performance Management Organizational Understanding Data Warehouse Performance Management Enterprise Efficiency Self Sufficiency Optimization ODS Single Source of Truth

  4. The Purpose of BI To help organizations meet their objectives by providing: • Relevant information • Accurate information • Timely information . . . .to support critical business strategies & processes Successful BI is achieved by: • Consolidation multiple disparate data sources • Cleansing and transforming • Creating a single source of information • Accessible by business users using their language

  5. Why BI? • Business Need • Data rich • Information poor • Technical Limitations • Multiple sources of data • Built to purpose • Inconsistent data • Transactional systems vs.analytical solutions

  6. BI Reflects the Business Objectives Actions Objective 1 Action to support objective Objective 2 Action to support objective Objective 3 Action to support objective Strategy Business Plan Strategic Objective 1A textual description of the objective Strategic Objective 2A textual description of the objective Strategic Objective 3A textual description of the objective Executive Management Management Measures Workforce

  7. BI Roadmap • Successful BI solutions are based on communicating and measuring the strategy of the organization • Think Big, Implement Small • BI Roadmap service identifies strategy, creates a prioritized roadmap through collaboration with business stakeholders and IT • Incremental process minimizes development and releases BI content to the business quickly • Change Management and Project Management reduce risk and increase success

  8. BI Roadmap • Stakeholder Interviews • Reporting and analysis reviews • Subject area identification and prioritization exercise • Source systems reviews • Technical complexity assessment • Toolset selection

  9. BI Roadmap • Deliverables • Prioritized subject areas linked to organizational strategy • Information delivery framework • Enterprise information architecture • Toolset recommendation, RFP, proof of concepts • High level logical model • Project Plan • Cost estimates (hardware, software, consulting services, internal resource time) • High level change management plan • High level education plan

  10. BI Roadmap

  11. BI Framework – The Business:Identify Business Pillars & Drivers • Strategy • ‘Enabling Pillars’ • Business Drivers • Key Performance Indicators • Keep it high level

  12. BI Framework – The Business:Information Consistency & Presentation • Consistent KPI Development • Cascade throughout the organization • Process for change • Presentation Layer • User classes require different information displays • Right information, right level at the right time • End state scenarios

  13. BI Framework – The Business:Prioritize the Business Requirements • Determine • Capture • Agree • Prioritize • Map • Business value vs. urgency • Preliminary mapping • Include organizational cultural aspects • Drill into 1 area

  14. BI Framework – The Business:Go Into Detail • Determine KPI Measures • In detail • By user classification • reports, etc. • Frequency • Drill path • Common Vocabulary • Source Systems • Extraction complexity • Data quality

  15. Establish high level business sponsorship Let the business lead Deliver to business objectives Ensure common business language Ignore business culture Deliver volumes of technical documentation Identify all KPI’s for all requirements in detail BI Framework – The Business Do's Dont's

  16. OLAP Denormalized Constrained dimensions Constrained facts Write back and other requirements Business support Metadata Business Technical History Years available Data Quality Audit Correction process ETL Batch schedules Error correction Availability Update requirements Business requirements User locations Data quantities BI Framework: The Design

  17. BI Framework: The Design Only when you understand: • Business requirements • Data requirements • Usage • Data quality • History • Metadata • Can you determine the overall architecture • ROLAP, MOLAP, HOLAP • Federated, Centralized • Start to consider your front-end, back-end and ETL tools!!!

  18. BI Framework: Architecture Design • Envision the Grand Design

  19. BI Framework: Architecture Design • Implement Incrementally

  20. Aggressively define data model - incrementally Have a data owner Develop & maintain metadata, dictionary and repository Use DW specific experience Make sure architecture is cohesive, open, scalable & flexible Compromise the model Assume ‘one size fits all’ Purchase tools before you know your requirements Assume existing skills are sufficient BI Framework: The Design Do's Dont's

  21. BI Framework: Development • Proof of Concept • Proves technical tit • Proves business fit • Tool Evaluations • Consider multiple tools • Allow users to evaluate front-end tools • Follow a consistent framework • Consider costs up front if necessary

  22. BI Framework: Development • BI projects are extremely successful when iterative (agile) development processes are followed • Business testing is critical • Data reconciliation is critical • Expect issues with data quality, ETL processes & procedures and presentation layer re-work • Experienced teams should deliver in 3 month cycles • First implementation cycle may take up to 6 months Iteration 1 Iteration 2 Iteration 3

  23. Undertake a proof of concept Use a tested BI implementation methodology Develop incrementally Expect some re-work ETL Report development Include users Report development Big-bang approach Keep the business in the dark Shoe horn the project to your standard methodology Exclude the business from the front-end tool selection Avoid implementing ETL error handling and production monitoring BI Framework: Development Do's Dont's

  24. BI Framework: Implementation • User Training • Tool usage • Integration into role • Business As Usual Training • Technology & tools • Error handling • Batch schedule • Data lineage • Release to users in small, manageable batches • Floor walks

  25. BI Framework: Implementation • Performance Monitoring • Monitor usage daily & adjust to reality • Identify top and bottom reports • Assess user satisfaction • Communications Planning • Multi-channel communications to target users & business • Identify ‘win’ stories and communicate to management • Clearly communicate success criteria

  26. BI Framework: Implementation • Hand Over to Business As Usual • Establish support structure early • Ensure all teams know about ‘batch windows’ • Maintenance for source systems may require additional planning • Provide development team support for a defined period

  27. Establish: Training Hand over Success criteria Communications plans early in the process Have a robust performance management plan Use vendor only training Expect BAU to quickly ‘pick up’ the system Allow ‘wins’ to go unnoticed Roll out in 1 go BI Framework: Implementation Do's Dont's

  28. BI Framework: Project • Use a phased approach • Business requirements • Discovery period(3 to 8 week time frame) • Define phases by business delivery • Strong BI Project Manager • Organizational change management • Communications management

  29. BI Framework: Project • Establish clear resource plan & don’t remove resources • Use ‘seasoned’ internal resources • Ensure contingency is built-in throughout the plan, especially during the ETL phases • Allow for support, tuning and hand-over time well after the project has ‘delivered’ • Plan for the sake of planning. Keep it reasonable, detailed BI plans go off-track.

  30. Strong subject matter expertise Experienced BI project management Follow issue, risk, status, governance structures Communicate, Communicate, Communicate!! Not plan or update plan Hide plan results Ignore the business Communicate to business in tech speak – translate to English Wait for a 100% solution before release BI Framework: Project Do's Dont's

  31. BC Public Safety and Solicitor General BC Attorney General Various WA State Agencies BC Ministry of Provincial Revenue State of Connecticut Los Angeles Police Department BC Ministry of Management Services BC Ministry of Employment & Income Assistance City of Surrey A & W Boston Pizza International Dimensional Fund Advisors North Shore Credit Union Tolko Industries Vancouver Island Health Authority BI Successes

  32. Questions?

More Related