Our approach for implementations

Whether you are starting from scratch, moving past spreadsheets, or looking to migrate them to Power BI in place, an implementation strategy and roadmap has always to be scheduled. 


So, for every single project we previously discuss with the Project sponsors and other stakeholders the Goals and Objectives in terms of priority-feasibility and hence the steps to be taken. 


Roadmap

 


Planning

Performed by

BI4U and Client's Project Sponsors (onsite/remote)


Input

  • Client's Project Sponsors needs
  • Requirements, pain points, GAPs


Output 

  • Scope of delivery
  • Implementation roadmap
  • Business requirements document

Workflow

Everything begins by initiating a meeting with the stakeholders to outline key areas of the requirements with a business requirements specifications. 

The business requirement specification includes the analytical needs, data dependencies, Independent teams/leads and considering potential obstacles. 

Once the requirements have been documented into the Scope of Delivery that includes functional and non-functional requirements, it will be used to prepare the strategy. In collaboration with the independent teams/leads the key milestones defined and planned into a roadmap of delivery. 


 


Functional Requirements

Performed by

BI4U and Client's Project Sponsors (onsite/remote)


Input

  • Business Process Workflow, taxonomy, data sources scope, latency/refresh/updating terms
  • Required Metrics/Calculations breakdown


Output

Functional requirements document

Workflow

As we kick off, it is time to gather functional and non-functional requirements and to assemble first business rules, and the pain points of the project. 


We identify together with you the KPIs that are relevant to your business, your industry, and more specifically the KPIs involved in the final model. These and other questions allows us to get to know your needs and help you determine or perhaps discover how we can help you and finally answer to your business questions in just a few clicks as soon as you power up your computer every morning.  

 


Development

  • Functional design
  • Technical design
  • Semantic layer ETL and Data model settings
  • Reporting layer- Mockuping and  Prototyping

Performed by

BI4U 


Input

Functional requirements document


Output

  • Functional and technical design documents
  • Prototype, pre alpha, alpha and beta versions

Workflow

We will in this phase be doing (and undoing) at our offices “for a while”: first collecting everything, analyzing it, and finally going into the model architecture development. Duration of this phase rests on the functional constrains and features struggles, but use to take no fewer than 6 weeks, commonly 8-10.


Status and progress meetings are held in regularly scheduled meetings with the involved project team. But also communication at a more detailed technical level. This way the people taking over the project at our clients side also grow in the newly build Power BI solution. We also foresee time for the technical solution training, which explaining why the implementation is done in a specific manner so people understand why certain choices are made.

 





Delivery & Users integration 

  • QA testing
  • UX testing

Performed by

BI4U interacting with Client's Project Sponsors and end-users (onsite/remote)


Input

Beta version


Output

Stable tested release version

Workflow

Our deployments encompasses all the processes involved making sure Power BI solution is running properly in its environment, including installation, configuration, running, and, over all, testing solution with end-users. 


In the testing stage, users can help to detect misunderstandings in the interface’s design that deter usability, such as misleading labels, misplaced buttons, or menu structures that are difficult to understand. 

 


Training post-deployment and ongoing Support

Performed by

BI4U interacting with Client's Project Sponsors and End-users (onsite/remote)


Workflow

After delivery and once the users integration is concluded (including those who remain reluctant or reactive to the project) you will not be alone: our BI4U coaching services will help you set up and acquaint yourself both with the software and the very own prototype features.  You will also be able to lead your team and keep on delivering value on your Power BI project.



Most common deployments depending on scenario usages

Based on how Power BI is intended to be used, we help our clients to deploy the Power BI solutions in different ways. The following outlines* illustrate the most common implementations depending on usage scenarios we find, although these options are very often mixed and matched (click on images to enlarge): 


Team Collaboration

Team Collaboration

Most common deployment, typical for a group of users within a global business or regional area who all interact regularly sharing reports and dashboards. Collaboration and distribution could be handled directly within an App Workspace at the Power BI Service. All users require a Pro license even if they are only consuming reports.

Power BI Desktop. Power BI Desktop is the tool for queries, datasets, and reports. For team-based scenarios, storing the original Power BI Desktop file in a share location such as OneDrive for Business easily accessible to team members so one person can work on the dataset and another on the reports.

Power BI and Analyze in Excel. These features permit a live connection, from Power BI Desktop and Excel, respectively and allows the user to utilize all slice, dice, and pivoting capabilities within Excel while remaining pointed to the original data which resides in the Power BI Service

Workflow Automation + Updating Data

Workflow Automation + Updating Data

The family of tools that is comprised of Power BI, Power Automate, and PowerApps allows for many interesting use cases that involve integration between these three business applications.

Power BI Desktop. Creation of queries, calculations, datasets and reports

Power Automate. Power Automate is a Microsoft 365 service for workflow automation between services. Used in conjunction with alerts in Power BI, Flow can be utilized for many types of workflow automation, such as sending customized e-mail alerts or text messages, post a message on Teams or request an approval

PowerApps. PowerApps is a Microsoft 365 service for creating small line of business applications and user interfaces in a low-code/no-code way. PowerApps can be used for many things, such as task and issue tracking, Surveys, etc.

Enterprise Level Collaboration

Enterprise Level Collaboration

Enterprise-Level BI environments often employ a “top-down” approach because it is common for the Power BI content to be largely created and maintained by IT and/or a BI team. Enterprise-Level reporting scenarios commonly have a significantly larger number of read-only users compared to a much smaller number of authors. A common way to cost-effectively support organizational/enterprise level reporting is via the use of Power BI Premium.

Premium Capacity in Power BI Service. Some larger implementations (>500 users) may justify the use of dedicated Premium capacity in the Power BI Service. When there are a large number of readers or view-only consumers of reports and dashboards, the use of Free licenses afforded by Power BI Premium is a cost-effective alternative to purchasing Pro licenses for all users. Larger implementations may also find advantages from the larger storage limits, larger dataset sizes, higher refresh rates, and incremental data refresh.

*Authorship contributions: Melissa Coates (Coates Data Strategies) and Chris Webb (Microsoft) / Microsoft® Whitepaper Planning a Power BI Enterprise Deployment 


To learn more about our Power BI Implementation services, make inquiries or arrange an initial discussion, do not hesitate to contact us, we are glad to assist you in any matter.