Skip to content

Logistics dashboard in Power BI

We bring warehouse, transport and orders together in a single Power BI model, from order to delivery. For Port of Amsterdam, we measured berth usage.

We developed a tool for Port of Amsterdam that measures and visualises historical berth usage

This lets policymakers decide whether certain types of ships need more or fewer berths, based on figures rather than gut feeling alone. Built with Databricks, real-time data and Power BI.

Read the case study

Where in the supply chain do things go wrong when a delivery is late?

The warehouse sees its orders, the planner sees the delivery routes, and finance sees the costs. To find out whether the delay happened during picking, loading or the journey, you need to bring that data together in one model.

Book a conversation

From order line to delivered shipment in one model

Discuss your logistics figures

On time and in full

Delivery reliability by customer, site and carrier, including why a shipment was late or incomplete.

Time spent in the warehouse

From receipt of the order to ready for dispatch, broken down by step — picking, packing and loading — and by shift and hour.

Vehicle utilisation and cost per shipment

How full vehicles are and what each shipment costs, alongside that customer’s revenue from the ERP system.

Capacity use over time

Just as we measured historical berth use for Port of Amsterdam, we measure the use of loading bays and sites.

One definition of on time, and only then the first chart

  1. Supply chain and sources

    Which systems record each step, how an order moves through WMS, TMS and ERP, and which key links them.

  2. One flow recalculated

    Delivery reliability for one site or customer, calculated in the model and compared with what operations currently report.

  3. Expand and refresh

    More sites, costs and carriers, with a data load time that fits the rhythm of operations.

Do you need your own dashboard alongside WMS and TMS?

Talk it through with us

A good fit if

Warehouse and transport data sit in different systems, you want to track performance by customer or carrier, or someone currently pieces exports together every week.

Not a good fit if

Everything is in one system with good reporting, and no one needs to see warehouse, transport and costs side by side. In that case, that system is enough.

What determines the scope

The number of sites and systems, whether carriers provide their data, how often the model needs refreshing and who manages it.

Our data isn’t always accurate

That’s exactly what a single model reveals: a missing scan or an order with no transport trip. We make those gaps visible and agree who will fix them.

Reports by system, a shared Excel spreadsheet or one model for the entire supply chain?

Reports by system

Choose this if the warehouse and transport are managed separately. Each department sees its own figures, but not the full supply chain.

A shared Excel spreadsheet

Choose this if you discuss the key figures once a week. Whoever maintains the spreadsheet has to bring the data together manually each time, and that takes time.

One model for the entire supply chain

Choose this if you want to see where delays occur. Our advice: start with delivery reliability for your largest customers.

Across ports, rail and public transport, we turn operational data into decisions

We’ve worked with operational data for Port of Amsterdam, ProRail and GVB. Data Science Lab has been operating since 2016, is a Microsoft Partner and Databricks Partner, and shares knowledge at Techdays.

Book an introductory meeting

The delay you can’t explain yet is where we start

Stef Stoelwinder

Stef Stoelwinder

Business Development

Stef is your point of contact. In our first conversation, we’ll discuss your systems and which logistics metrics you’re missing.

Which stage of your supply chain would you like to quantify first?

Tell us which systems your warehouse and transport teams use. We’ll reply by email or arrange an initial conversation.

Enter a valid email address.

Let us know how we can help you.

Frequently asked questions

How orders move through your supply chain: from receipt and picking to loading, transport and delivery. For each step, you can see the time taken, the cost and where things went wrong.

For where to start with a dashboard, see Power BI dashboards.

Usually a WMS for the warehouse, a TMS or planning system for transport, the ERP for orders and invoices, and sometimes trip data from onboard computers or carriers.

We first map out which identifier links an order across those systems.

Often delivery reliability (on time and in full), lead time per step, order lines per hour, load utilisation, cost per shipment and the proportion of urgent orders.

Which ones matter depends on the decisions you make with them.

Yes, if the WMS records the time of each activity. You can then see how many order lines were picked per shift and per hour, and where delays occur.

If your main focus is stock, read about the stock dashboard.

Yes. If you use Transpas, read about the Transpas Power BI dashboard. We can also bring other systems into the same model, provided their data can be made accessible.

We check this for each system before building anything.

For reviewing performance after the fact, refreshing once a night is often enough. If operations teams need to check it during the day, we load data more frequently or work with real-time data, as we do for Port of Amsterdam.

More frequent loads place greater demands on the source systems, so we make that choice deliberately.

We define that in the model, by location, client or department. A team leader sees their shift, a site manager sees their location, and the management team sees the full picture.

You can also share data with clients or carriers, giving them access only to their own data.

Yes, once the foundations are in place. You can then predict busy periods or plan routes more efficiently. Read about route optimisation and the mobility and logistics sector.

We always start with figures you can trust.