Best Practice to BI & Data Discovery Implementations
Download as PPTX, PDF0 likes675 views
The document outlines best practices for implementing BI tools, emphasizing the importance of understanding user business needs and pain points before implementation. It advocates for creating a coherent story during the implementation to engage prospects and demonstrate the tool's value, using overview and secondary workboards to provide insights. It also includes a checklist for ensuring a successful implementation, highlighting technical and relational aspects necessary for fostering trust and effective tool utilization.
Best Practice to BI & Data Discovery Implementations
- 1. Best practice for Implementation Presented by Efi Goldman, Head of Solution Experts Panorama Software
- 2. Implementation’s Successful Implementation’s Building Trust with Professionalism Know their problems Know their data Analysis That Brings Value Following the Implementati on deliveries WOW Build the Implementation vs. the current Competitors Sell a Solution
- 3. Understanding the Business Requirements for current tool. Before beginning a implementation it is very important to understand the users pains: What business problems is the BI tool expected to solve? What they need now and cannot do? Or think they cannot do? What they need? How they use the supplied data? What they do with it?
- 4. General Implementation issues Performance issues Model that is not planned well Server resources The tool is not used as it should Users that are abusing the system (big queries that are sent) Creating reports in an analysis tool Training Lack of information of how to work with the tool Users do things that are not according to best practice No training was done on new versions/ upgrades The users usually use the tool in a very basic level and do nt take it to the edge.. Lets take a look at some implementations…
- 5. Creating a Story Best Practices I
- 6. Create a Story Compile a story which describes an analysis path of a user. The analysis path should be translated to a series of Workboards that are connected to one another via a narrative. Avoid showing just a random set of Workboards that have no relation to one another. A story with business sense, will show the prospect that you understand its business and will hold the prospects interest during the implementation showcase. When working on the prospect’s data, try and find a real issue during the story. That will capture the prospect’s attention and will show that you understand the prospect’s business The best approach for a story is to have one main “Overview” Workboard that provides an overview of the business and holds links from its components to other Workboards;referred to as Secondary Workboards. These Secondary Workboards hold more detailed information on specific segment of the business
- 7. Example of an Overview Workboard This chart provides an Overview of sales over A year for the entire Business. Some or all of the components Will lead to a Workboard Component s with Value
- 8. The Overview Workboard A Secondary Workboard A Secondary Workboard A Secondary Workboard A Secondary Workboard
- 9. How to Preset a implementation Step by Step implementation Example
- 10. We always start with the home screen by reviewing the different available links. This allows us to survey BI tool’s unique Social and Contextual discovery capabilities, by reviewing the Recent Discussion, Recent Subscriptions and Relevant Workboards links
- 11. From the home screen, navigate to the Overview Workboard. Survey the Workboard and explain each of the components that are been viewed. Click on the show comments button.
- 12. Review the Social bar with its two Different user groups
- 13. Start the analysis on one of the components. Discover a business Insight. For further analysis click on The component title and drill through to one of the Secondary Workboards
- 14. Make sure the slicers in the Secondary Workboard are matching those of the Overview Workboard (There are couple of ways to achieve that). This Secondary Workboard should include either a BI 3.0 capability , a unique BI tool feature or deep insight on the prospect’s business. Otherwise There is no reason to create and show it
- 15. After reviewing the Secondary Workboard, go back to the Overview Workboard And continue to review the different components and drill through to the Secondary Workboards, each time showing different and unique capability and at least once showing OCI.
- 16. Don’t forget to navigate to one of the secondary Workboards (either from a Secondary or from the Overview Workboard) via the Advisor
- 17. Check List
- 18. Check List Understand customer business needs Make sure implementation document is signed by prospect Make sure BI tool implementation server meets HW requirements implementation Content: Capability BI tool Feature Enabling Best Practice Demonstrate understanding of prospect’s business Needs Workboards flow Building a Overview Workboards that allows drill through to other Secondary Workboards through a coherent business scenario 1 Social BI and advanced collaboration Social Bar, creating a discussion and comments Making BI tool Social ready by creating users and social activity 2 Contextual Discovery Relevant Workboards and Advisor Adding topics to users and Workboards, and visiting the Workboards with different users 3 Advanced Analysis OCI, Parameter analysis and Bubble up exception Creating Secondary Workboards with these unique features 4 Additional unique BI tool Capabilities Searching, advanced MDX, web data integration, etc. 5
Editor's Notes
- #3: Good Implementation is constructed of: Creating a great relationships with the customer Having an in-house Champion, that promotes the concept and creates a vibe This Champion has to be technologically strong. Giving a great business value during the sales cycle effects how well the implementation will be. Defining timeline and effort in a fix price, on the sales cycle, so the customer is happy with the solution we offer, and knows exactly what to expect and when. Planning the implementation carefully, with a Gantt worksheet, and following it on time and budget
- #5: 4 cores of CPU, and at least 4GB of RAM – It is Minimum. IF the implementation will contain more than 1 GB of Data and You are using the Modeling option, with SQL 2012 on the BI tool Server – You should have at least 6-8GB of RAM Create a Model – We prefer to create a Model, to show the benefits of using all BI tool Capabilities.