best practices | video Youtube channel | business intelligence | datavisualization | dataviz | digital transformation | Iver van de Zand
the BI Component Selection Tool
what technical component best suites your users
As an analytics professional you already figured out that users prefer to have as many tools available when you discuss with them what they need for their job when it comes to getting insights. They want everything for the reason of ".. just to be sure; imagine I'd miss something ..". They care less about maintaining and deploying software, but you do!
So how do you decide what user should have what analytical component?My Business Intelligence Component Selection Tool will help you.
As part of your BI Strategy Roadmap, you may consider to discuss your users logical - functional requirements. It is my experience that these requirements always come down to a list of 40 - 50 generic ones. It are these that guide you in your decision on what technical component to offer to what type of user.
Specifically on dashboards some important decisions are to be taking when you opt for one. Tap the button on the right to found out more.
If you are interested in the latest roadmaps, convergence programs, vison and strategy on all SAP analytics BI products, have a look at this tremendous deck.
Passion is walking the tricky path of unknown, but exciting future
Prior to start thinking about the BI functionality we want to provide, we need to categorize our types of users. Our beloved Internet has tons of blogs on this topic, but at least we can derive following basic categories of BI users:
IT specialists maintaining the BI environment. Specialists maintaining the technical BI environment, ensuring governance, security and authorizations, backups, population routines and up-time
Developers, architects and members of the BI Competence Centers. BI specialists deploying the BI environment. Content creators for semantic layers, managed dashboards and reports, datasets and metadata
Data analysts and/or scientists. Users of the BI information, deeply exploring and analyzing the BI data and information. Also embed (un-)structured data from outside the BI environment
BI consumers. Employees consuming the offered BI structures like datasets, storybooks, reports, cubes and dashboards
Deciding on providing what kind of specific BI functionality to your users, is based on considerations that vary in abstraction-level. On a higher level core considerations like indicated below will impact your choice. These considerations have to be taken into account first before deciding on what functionality you offer to users. They should be part of your company’s business intelligence roadmap. This roadmap typically covers max. 3 – 5 years ahead, and describes how business drivers delegate BI content and functionality.
The next abstraction level should be to define specific logical BI functionality your users require, and match these requirements against the BI components you have available. The definition of the logical functionality can be drafted upfront by the BICC, but needs to be thoroughly verified with users based on use cases. Short workshops with BI users, going through day to day practices, will quickly generate these functionalities. Examples are the ability to work with hierarchies, or to create custom reporting groupings.
Your business intelligence roadmap is the ultimate place to where you should store and secure the logical functionalities required. This should be done per BI component you have available to offer your users. Components are the likes as managed reporting tools, OLAP tools, self-service tools and managed dashboard tools. The example is based on the SAP BI Suite components and the SAP Cloud For Analytics product, and lists the logical functionalities your users will ask for. Ah, and by the way, I use SAP Lumira to all visualize it
PASSION IS PUZZLING
Passion is sleepless nights doubting, weighting and considering that single detail
Get the BI Component Selection Tool
Learn how to set up the tool
If you like to use the BI Components selection tool, following procedure applies:
ensure you have SAP Lumira Desktop running at least as of version 1.27 or higher.
If you don't have Lumira available, contact you local SAP ofice and request a test-license
Tick the button "Download Now" on the right and save the file with it's existing LUMS extension
Start Lumira Desktop
Click File->Import ... and import the downloaded LUMS file
Click the compose-tab
An overview video of the BI Component Selection tool is below.
The ratings and weight-factors in the tool are my own and based upon 21 years experience. I'll regurlarly update the tool according to the latest sofwtare releases
PASSION IS DEEP DIVING
Passion is about preparing to deep dive the era that touches and intrigues your mind
Dashboards and Dashboards
What to choose from a dashboard
The SAP BI Suite currently holds the Dashboard as the Design Studio components to be used for enterprise dashboarding. Below is a very comprehensive overview comparing both components. A must read if you are opting to use enterprise dashboarding in your company.