INTRODUCTION • Getting the most out of your roadmap •
Selecting the degree of centralization
•
Getting a laser-focused plan
• Analyzing your solution’s degree of coupling
BUSINESS INTELLIGENCE FOR DUMMIES
3
WHAT A ROADMAP IS (AND ISN’T) Statement of overall business problem(s) and the specific scope of the solution. Business perspective of the solution — for example, what information needs your system will meet that it wasn’t meeting before. Initial financial analysis, including ROI projections. Current condition of the organization’s information infrastructure—including a discussion of where all the relevant data is being housed and what condition it’s in. High-level review of hardware requirements, emphasizing any new platforms you may need to implement. Discussion of existing and new software that will be utilized for the BI solution. General make-up of project team and division of responsibilities. A section on risks, constraints, and assumptions that lays out where things can go wrong, as well as the known limits of the BUSINESS INTELLIGENCE FOR DUMMIES BI implementation.
Organizational Structure BUSINESS INTELLIGENCE FOR DUMMIES
6
BI ARCHITECTURE ALTERNATIVES How and where will the data be maintained? What will the integration schedule be?
What tools will sit on which desktops — throughout the organization?
BUSINESS INTELLIGENCE FOR DUMMIES
7
ARCHITECTURE EVALUATION
Hardware
Data Management
End User Tools
BUSINESS INTELLIGENCE FOR DUMMIES
8
OTHER SOLUTION ELEMENTS Operating systems Network protocols
Server hardware Primary database vendor Data Warehouse and Extract, Transform, and Load (ETL) processes The kinds of front-end BI tools you absolutely must have The kinds of front-end BI tools that would be nice to have
BUSINESS INTELLIGENCE FOR DUMMIES
9
QUESTION ASKED DURING PLANNING PHASE Which solution components work well together? And which don’t? What infrastructure is currently in place and does it have spare capacity? Does the company have existing relationships with some of the target vendors?
THE SHORT LIST The goal is to produce a short list of architecture alternatives that satisfy all of your bare minimum requirements, and hopefully supply some nice-tohave features as well. BUSINESS INTELLIGENCE FOR DUMMIES
10
EXAMINING COSTS FOR EACH ALTERNATIVE
Keep your eyes for expenses such as
Software License
Hardware acquisition cost
Service and Training and maintenance support cost cost
BUSINESS INTELLIGENCE FOR DUMMIES
11
LOOKING AT TECHNOLOGICAL RISK Some examples of risk associated with IT implementation are
Software has unknown bugs that pupate and hatch at inopportune times. Software doesn’t perform as promised by the vendor Products don’t work together as well as projected.
BUSINESS INTELLIGENCE FOR DUMMIES
12
MAKING YOUR DECISION Verify Your Information
Revisit your criteria Get a new Perspectiv e
BUSINESS INTELLIGENCE FOR DUMMIES
13
DEVELOPING A PHASED, INCREMENTAL BI ROADMAP
Highest Value
Least Risky
Easy to deliver
Deciding Where to Start BUSINESS INTELLIGENCE FOR DUMMIES
14
DEVELOPING A PHASED, INCREMENTAL BI ROADMAP
Keeping Score
Deciding What Comes Next
• Prepare a score card with key variables • Rate them in order to decide your priorities
• Move ahead according to previously made decision • Review and refine the deliverables from the previous stage
• Planning • • For Contingen • cies
Cost Overflow Technological Risk High Human resource turnover Loss of project sponsor BUSINESS INTELLIGENCE FOR DUMMIES
15
DEVELOPING A PHASED, INCREMENTAL BI ROADMAP • Tiny changes in your scheme could impact your plan. • Insignificant updates can have big impact Dealing with moving targets on your project.
Leaving time for periodic “architectural tune-ups”
• A BI system is a constantly evolving organism • You need to updated or in easier term tune up the system from time to time.
Thank you for interesting in our services. We are a non-profit group that run this website to share documents. We need your help to maintenance this website.