The approach taken by Microsoft is fairly unusual.
Leave the BI Design to End-Users (or designated Power End Users) and simultaneously build EDW (Enterprise Data Warehouse). Once the design & EDW is ready, use following tools to achieve this CBI Model:
Microsoft Office, SharePoint 2010, SQL Server 2008 R2, Silverlight Technology.
CBI basically means one Single Enterprise Report Catalog. It’s then delivered as a SharePoint based BI Portal. Microsoft IT hosts BI with Reporting Services, PPS, etc, BUT Power End Users design and publish Reports on to this Portal. There are certain restrictions in terms of how many users being allowed to publish these reports for their own Team/Department/Division.
Top 10 Questions which Microsoft asked themselves before CBI (and of course everyone of us to ask ourselves as well):
1. IT Cost too much to implement this BI Catalog. What to do first? EDW or BI Reporting Catalog?
1.1. Allow End Users to publish all their ideas on a Not-So-Clean EDW Data.
1.2. Clean EDW and keep EDW ready.
2. How do you get the First Sponsorship?
2.1. Push and Pull Approach
2.2. Create a Cool Demo
3. How do you architect with big Holistic Enterprise Vision?
4. How do we implement seamless security across layers?
5. Who should create BI and show we actually give control of the report catalog to business and enable self-serviced BI?
6. Can we implement ZERO footprint deployment for masses using SharePoint?
7. What about regional deployment and scalability?
8. What front end tools to BI publishers use and how do you integrate various tools?
9. How do you evangelize and achieve enterprise adoption?
10. How do you achieve high Customer Satisfaction?
10.1. Customer Empathy
10.2. Maintain Customer Relationship
10.3. Improve, Improve & just Improve
Until next post on Tech-Ed from me.
VAIDY
Dynamics GP - Learn & Discuss 