Power BI

Power BI is where many companies combine their business data: ERP, sales, finance. By bringing UpBlue production data into Power BI, you get the complete picture: production per order next to the order value, energy use next to the energy bill.

The best dataset for Power BI is Operations: one row per production run, with metadata (order, customer, article) and the KPIs from your aggregate rules. That is exactly the shape Power BI likes.

Power BI connects to UpBlue with its built-in OData feed connector. No code, no gateway. Read the Excel & Power BI page first for how feeds and OData users work.

Example: downtime per reason next to order data

Create the feeds

On the Excel & Power BI page, create two feeds:

Line1_Runs — Operations datasource, Get Data on the production-run operation tag. One row per run with order number, article and the KPIs from your aggregate rules.
Line1_Downtime_per_day — Operations datasource, Get Data on the downtime operation tag, then an Aggregate step: group by reason, metric Duration, interval 1 day. One row per day, one column per downtime reason, in seconds.

Set the default range to the period your report needs, for example 365 days.

Create an OData user

Create a user such as powerbi.production with access to both feeds, and copy the password.

Connect Power BI Desktop

Get Data → OData feed, paste the OData URL from the Excel & Power BI page. Choose Basic, sign in with the OData user, and select both tables in the Navigator.

Model

Relate Line1_Runs to your ERP order table on the order number. Divide the downtime columns by 3600 in Power Query to get hours, or unpivot them into a reason / seconds pair for a Pareto chart.

Publish and refresh

Publish the report. In the Power BI Service, open the semantic model settings, enter the OData username and password under Data source credentials (authentication method Basic) and turn on scheduled refresh.

💡

For years of timeseries data, use incremental refresh on the time column. Power BI then only asks UpBlue for the newest period on every refresh, which is fast and stays below the limit of 2 years per request.