Nimbus Power BI Template Overview


KNOWN ISSUE Query Errors: Particularly on high data volume queries, we currently get issues reported that relate to the BI Data Privacy firewall. We continue to investigate this case to make further improvements to our query and templates as needed.

✅ Current workaround → If you encounter problems with your version of Power BI, please follow these steps.

Power BI Workaround - Privacy/Firewall Settings

Do not load the template file or data yet. Close any report files, but leave Power BI open.

Head to Power BI Options and Settings > Options > Global > Privacy 

  • Ensure "Always ignore Privacy Level settings" is selected

Next, head to Power BI Options and Settings > Options > Global > Security

  • Select "Allow any extention to load without validation or warning"

Finally, open your Nimbus Report file and provide the connection details, starting with a small time-range test query. 

💡 If everything works as required, continue to expand your query sizes. However, consider the known BI Performance Issues warning below in mind.

💡 If there still are issues: Head to Power BI Options and Settings > Options > Global > Security

  • Verify that "Ignore the Privacy Levels and potentially improve performance" is selected. If it is not, check the previous steps first, then and follow the linked Microsoft documentation for more details.


KNOWN ISSUE Performance Issues: On recent BI Versions – running on Windows 11 in particular – we have noticed considerable CPU and RAM usage spikes both during BI queries. The high frequency data access can lead to query errors (e.g. out of memory, connection forcibly closed) as your computer hits CPU and RAM boundaries.

KNOWN ISSUE Error “OData: Unable to read data from the transport connection. A existing connection was forcibly closed by the remote host”. 
This error can occur due to the Wifi network protocol. Microsoft advises that changing the network protocol as follows, solves the issue: 
1.    Go to Control Panel > Network and Internet > Network and Sharing Center > Change adapter settings 
2.    Double Click Wifi
3.    In General Tab, click properties
4.    Uncheck Internet Protocol Version 6 (TCP/IPv6)
5.    Click "OK"

💡 The Report parameters Unified Sessions and User States greatly increase the data load on Power BI and thus can increase the occurrence of query errors and connection aborts.

  • Even on a powerful PC with good internet connection you must still expect overall query and calculation times of ~10-15 minutes. → We recommend using a workstation equipped with Core i7 CPU or newer and at least 16 GB RAM to keep processing speeds acceptable.
  • Our BI template has been tested with up to 2 million call sessions. With additional data parameters (Unified Sessions, User States) enabled, we recommend querying your date range in smaller ranges and increments. This is especially applicable when you are running services with high call volumes  > 1 million monthly sessions.

✅ Recommended workarounds   
→ If you got a Nimbus .pbit template file successfully connected and used for queries, save it as a .pbix report file for continued work. We have noticed considerably lower resource usage on pbix file extensions.
→ Consider decreasing your reporting range and/or deactivate unneeded parameters to strike a balance between query times and data reported.



☝ Licensed BI features costs are outside of Luware scope and outside your Nimbus licensing.

💡 Most Power BI report designers who work on Business Intelligence projects use Power BI Desktop to manage the Power BI reports, then publish to a Power BI workspace service to collaborate and distribute the files.


Luware BI template files

✅ Luware provides the following Power BI Files. Contact Luware Support or your Customer Success Specialist to get the latest version.

Description Filenames
Power BI Template / Report

Nimbus.pbit / Nimbus.pbix

✅ When using a Template (.pbit), please add your connection parameters and credentials and perform a basic query. Afterwards, save it as a .pbix report, as it will use considerably lower RAM/CPU than a template.

Paginated Reports
  • Nimbus_ServicePerformanceOverview.rdl
  • Nimbus_UserPerformancePerMonth.rdl
  • Nimbus_LostCallDetails.rdl
Legacy Template


💡 A special variant to support users coming from our existing LUCS/TM products → As standalone "Nimbus" user you can refer to the "Power BI Template" instead.

Learn more...

Legacy Template Use cases

Legacy support is available for LUCS/TM versions 3.5+

DB versions:


You may need this template in 3 scenarios:

  1. Two active Systems - You have a working legacy system (LUCS/TM) and a new Nimbus tenant. You want see legacy and Nimbus reporting services side-by-side.
  2. Completed Migration - You've recently migrated all your services from legacy system to Nimbus tenant. You want see reporting collected by LUCS/TM and Nimbus side by side.
  3. Using just the Template - You have only Nimbus services, but you want to continue using the Nimbus Power BI template with Legacy adapters.

🔍 Refer to the → Parameters below for further notes on each scenario.

Example BI Template with both Nimbus and legacy data combined

💡 Note: Service names from legacy data sources have original GUIDs and "legacy_" prefix names, as shown highlighted here.

Report parameters

The legacy template contains a set of additional parameters for connecting to the LUCS or Team Manager SQL Server database.

Parameter Data Type Description
Append_Legacy boolean if TRUE legacy data is appended, if False legacy data isn't appended
Legacy_MonthLimit integer Number of Month back from today to be imported from legacy database
Legacy_ServerName text SQL Server FQDN including instance
Legacy_DatabaseName text Database name

Please note in regards to the 3 scenarios above:

  • For Scenarios 1 and 2 (Legacy and Nimbus still active) your Power BI needs unrestricted access to the SQL Server database of a legacy system.
  • For Scenario 2 (DB access only) active communication services (ICH, PS, CIC etc.) can be stopped. Only the SQL Server is required. The Connection string to a legacy system is based on report parameters Legacy_ServerName and Legacy_Database. The Append_Legacy parameter should be TRUE.
  • For Scenario 3 (Nimbus only, but keeping the legacy Template) the Append_Legacy parameter should be to FALSE. Other parameters are not considered and can be left blank.
Parameter settings in Power BI


Template Overview

The Nimbus BI template consists several views/tabs:

  1. Service Overview - Session KPI per service
  2. User Overview - Session KPI per user
  3. Caller Overview - Incoming caller Sessions
  4. Session Details - KPI accross all sessions
  5. Tags-Codes - Session Tags and Codes as recorded in My Sessions view by users.
  6. Unified Sessions - Combined User and Service Sessions
  7. User States - The recorded change in User States 
  8. Info - Context on the data queried (Count of sessions, User used to query)

🔍 Each Tab is explained further below.


To switch between the tabs and views:

  1. Hold CTRL and left-click on the icons at the left hand sidebar   
  2. Use the tabs at the bottom of the report

Further points of Note:

  • In Power BI Desktop you must use CTRL + Click on buttons and links, otherwise you may just select fields in the template for editing.
  • CTRL is also used to multi-select filtering options and list entries.
  • On each view, Arrows indicate Drill-Through possibilities into further data. 
  • Data shown in the report is based on the Nimbus Reporting Model.
  • The Nimbus KPI Calculations are completely done in the product itself, the report does only query the results.

💡 Ensure to also read the "How to use" chapter below.


Service / User Overview

Service Overview and User Overview pages provide a general overview of your system. Here you may find:

  • ... total measures showing counts and time for all your Services and Users.
  • ... KPI such as as Reachability, Acceptance and Hangup SLA%. Call distribution in time.
  • ... performance comparisons in different time periods between services/users in your system.

💡 You can drill through into sessions for details as described in the “How to use” chapter below.

Service Overview
User Overview

Caller Overview / Session Details

Caller Overview and Session Details give a closer look on the distinct sessions accrued on the Service / distributed to the User.

💡 You can drill through into caller sessions for details as described in the “How to use” chapter below.

Caller Overview
Session Details

Tags and Codes

Tags and Codes specified by users during (via the My Sessions UI) are shown as a tag cloud in reporting. The bigger the tag shown, the more frequent it has been used.

For example you can click on tags to ...

  • ... narrow down data by call sessions that used these tags.
  • ... identify months where tags have been used more frequently.
Tag and Code Page example

Unified Sessions

Lists Caller (customer) data like PSTN or Name, the Caller path and connection times with the final session outcome.

Unified Sessions with various outcomes

💡 Click on a Session, then CTRL+Click the button on the bottom to show further details. Also see “How to use” chapter below .

User States


  • Licensing - please note that reporting on tracked User States is a Contact Center feature: 
    • The user refreshing the Power BI report must be a Nimbus User Supervisor (this role can only be assigned to a user with a Contact Center license). The User States tab in Power BI will not show any information unless you have this role assigned via the User Administration.
    • The Nimbus User Supervisor will see user states for all users in the supervised OUs irrespective of whether such users have a Contact Center license or not.
  • Organization Units:
    • The Nimbus User Supervisor will only see the user states for the users in the Organization Units they are explicitly assigned to as a Supervisor. 
  • To gather User State data, this feature needs to be enabled for your tenant. This is done via Tenant Administration > Data Privacy > "Show User Time in State" option.
  • Power BI parameters: 
    • In the Power BI template, the connection parameter “Load User States” must be set to “True” before refreshing the dataset.

LIMITATION BY DESIGN If a user has only Supervisor and not a Team Owner / Service Admin role, only the "UserStates" dataset in the report will be shown, consisting of: UserStates, StateTypes, ResponsibilityProfile, OU, Users. Other tabs and queries in the BI Report may appear blank.   
→ This is intended by design to prevent exposure of individual Service/User/Session data to the wrong audiences. To see a full dataset, the same user also needs a "Service/Team Owner" role assigned. 


What data is being tracked? What are user states?

User States

For its Reporting Model Nimbus distinguishes sessions by various user state factors (Teams Presence, Duty State, Task Selectability, Call Status). A change in either factor has influence on the others, either being a requirement or dependency.

Factor Definition / Conditions Nimbus-Tracked User State

Presence in MS Teams


Online – including status "Busy" or "Away" –  if defined per Service-individual Distribution Service Settings. Offline Online 
MS-Teams based services will distribute when "Active".
Online and set "Active"
MS-Teams based services will distribute.

Online and "Active" but Busy/Away
Can either be selectable or not ⬇️ (determined per each Service's Distribution Service Settings)

Duty State

Contact Center

User is online and has any "On Duty" responsibility profile selected.

User is assigned to the Service as "Agent" via Agent Service Settings.

An "OffDuty" responsibility profile prevents any Contact Center participation.
On Duty
Any "Duty" type responsibility profile allows Contact Center participation. Skills and Responsibilities in that profile must match the service to be "Selectable". This is determined by the individual Distribution Policies assigned to the respective services.
Task selectability

"In Time" available to perform tasks in Nimbus:

Online in MS Teams.

Set to "Active"  in any Teams-Based  Nimbus service or

In a "On Duty" profile for Contact Center services.

  🌟 "Selectable" state
This includes Busy/Selectable and Away/Selectable
"Non-Selectable" State, either because:
⬆️ User is not available either due to the Presence state in MS Teams or set "inactive" for all Nimbus teams or
⬇️ ... any existing or previous Call Status marks the user as "Not Selectable

Call status


Reserved and blocked for a Nimbus task.

Any of these status flags occur during or after a call and prevent selection for further tasks until resolved.

      Not Available Reason
Requested as the user changes MS Teams presence (manually or from idle).
RONA (Redirect on No Answer)
User flag after not responding to a task, blocked for the next tasks.
User reserved for new task, but has not accepted yet
User accepted task, is blocked by 
ACW (After Call Work)
User has a fixed (optionally extensible) timespan to complete work after a call.


💡 It is important to note that these user state factors depend on each other. Reading the table vertically from "top to bottom" here are some examples:

  • Offline users are not considered to be in any duty state. Nimbus will not distribute tasks.
  • While "Online" ...
  • For any service: While "online", "active" and "on duty" a user is selectable for tasks. Users can participate types of service simultaneously via their "Active" toggle and Profile selection accordingly.
  • Any Call status (e.g being Not Available, already busy in a task, in ACW or flagged by RONA) will flag the user as "Not selectable"

🔍 Learning: Users have one deterministic state at a time. Combined factors listed above and their change over time form a "User Session" which is tracked as part of the Nimbus Reporting Model. Detailed user states are tracked with timestamps for later evaluation analysis, e.g. in BI. This is enabled via Tenant Administration > Data Privacy, and included in Power BI historic reporting.


This tab lists User States, also referred to as "Team Enability" (e.g. the On/Off Service participation toggle in the Frontend UIs during daily use of Nimbus).

Example showing accumulated time spend in various states

The DataWareHouse distinguishes by the following user states:

  • After Call Work
  • Connected
  • Not Selectable
  • Off Duty
  • Offline
  • Ringing
  • Selectable

🔍 Also see Nimbus Reporting Model→ User States table


Allows to inspect where sessions are transferred to and to which result, so involved services can be optimized accordingly.

Transfer Report

Can be filtered by: 

  • Start Date Time
  • Service From
  • Service To

Provides the following Visuals:

  • Pie Chart "Transfer by"
  • Pie Chart "Transfer by Result"
  • Transfer Flow Diagram by Service 
  • Source Service
  • Destination
    • Service by Name
    • External
    • User
  • Grid “Transfer Overview”
  • For related OData Tables on static dimensions and facts see Nimbus Reporting Model→ “Transfer Sessions”
  • If there was more than one transfer session occurring during a single service session, it is stored in the Transfer Sessions table. However:
    • If the last logical Workflow Activity of a service session was a transfer, then the "transfer" fields in service sessions table will be populated.
    • if the last logical Workflow Activity was not a transfer (e.g. Transfer > Queue in new Service), then "transfer" fields in service sessions table will be left empty.

How to use…

Drill Through

Drill Through buttons provide a convenient way to navigate between entry overviews and detail pages. The drill through possibility is signaled with an arrow:



  1. Select a Service entry (row) on the Service Overview page.
  2. Use the Drill Through button (don't forget: CTRL+ Left-click) → The Caller Overview page with a full list of Service Sessions for this particular service is shown
  3. Pick one session (row) on the Caller Overview page and CTRL + Left-click "See Session Details" → The Session Details page for that user is shown.
  4. Use the "Back" buttons/arrows to get back to the previous pages.
Drill down into sessions of a particular user
Example of multiple drill-through steps

Data Slicers

From within any tab you can narrow down the data with predefined slicers (filters).

  1. Navigate to any tab that has a slicer symbol shown in the menu.   
  2. CTRL + Left-click the Slicer Symbol at the bottom left → The Slicer Menu opens
  3. Select your filters and time range slicers as needed 💡 Don't forget to hold down CTRL while handling UI elements.   
    → The BI Template automatically refreshes the data based on your selection.
Slicer Menu

Table of Contents