AllSolutions Power BI dashboard
We bring hours, projects and billing data from AllSolutions together in a single Power BI model. For GVB, we made discrepancies in hours visible by project.
For GVB, our model provided project-level insight into productivity, whether all hours were recorded, and overtime
The Rail Materiaal department wanted to identify which logged hours were unusual. With that insight, GVB can plan more effectively for each project. No AllSolutions, but the same question: are the hours recorded for each project accurate?
Why do we only find out a project went over budget when the invoice arrives?
AllSolutions brings together time entries, planning and invoicing. If you want to compare by department, client or month, or track work in progress, you need to put that data into your own model.
Hours, budget and invoices for each project at a glance
Billable hours by employee
Logged hours by type, employee and department, alongside the hours available on the rota.
Budget versus actuals
Budgeted hours and costs alongside what has been logged for each project, so you can spot overruns early.
Work in progress and invoicing
Work completed but not yet invoiced, by client and month.
Hours that don’t add up
As we did for GVB by making missing hours and overtime visible for each project, the model flags hours that don’t add up.
We define the hour categories before building a single chart
-
Configuration and API
Which browsers, fields and companies are needed, plus a dedicated API user with only the necessary permissions.
-
One period cross-checked
Hours and revenue for one month in the model, compared with the figures the finance team currently uses.
-
Expansion and management
Historical data, planning, multiple companies, permissions by department and a fixed data refresh time.
Does an organisation using AllSolutions need its own dashboard?
A good fit if
You want to compare projects, departments or years, combine AllSolutions with other sources, or someone currently puts together an Excel spreadsheet for management every month.
Not a good fit if
The reports in AllSolutions answer your questions and no one combines them with other systems. In that case, an additional model adds little value.
What determines the scope
How many companies or departments you have, which modules you use, how many custom fields there are and whether other sources will be added.
Do we lose control of our data?
No. You decide in AllSolutions which data is made available through the API, and the API user's permissions apply in full.
Standard reports, an Excel export or your own model built on AllSolutions?
Reports in AllSolutions
Choose this if project managers mainly want to see the status of their own projects. Everything stays in the system where they log their hours.
An Excel export
Choose this if you produce a report once a month. Whoever prepares it has to combine the data again each time, and the definitions can shift too.
Your own Power BI model
Choose this if you want to compare results over time or bring in other sources. Our advice: start with billable utilisation by department.
We've turned time tracking into project-level management insights before
For GVB, we made variances in hours visible by project; for Fokker, we built a planning tool for work orders and capacity. Data Science Lab has been operating since 2016, is a Microsoft Partner and Databricks Partner, and shares knowledge at Techdays.

Our first conversation starts with the project question you’ve had to put on hold
Stef Stoelwinder
Business DevelopmentStef is your point of contact. In our first conversation, we’ll discuss how AllSolutions is working in your organisation and which figures you’re missing.
E-mail info@datasciencelab.nl
Phone +31 (0)20 3636 724
Hours or projects: what would you like an answer to first?
Tell us which modules you use and what else you use alongside them. We’ll reply by email or arrange an initial conversation.
Message sent
Thanks for your message. We’ll be in touch as soon as possible.
Frequently asked questions
Through the AllSolutions REST API. A data-loading step retrieves the data at set times and prepares it for the model, so Power BI does not run queries directly against AllSolutions.
To see where a dashboard starts, read about Power BI dashboards.
Yes. The REST API is a module that your AllSolutions consultant can activate. You will then receive an interface code and a Secret ID, which the data-loading step needs to log in.
AllSolutions notes that using the API may incur costs. You can confirm this with them.
Whatever your team makes available. In AllSolutions, you configure a view and API settings for each browser, such as projects or contacts. Custom fields can be included too.
Together, we make a list of what the model needs—and nothing more.
Billable utilisation by employee and department, budget versus actual spend by project, work in progress, invoicing by client, and capacity based on the schedule.
For projects more generally, read about the project dashboard.
The API uses the permissions of the user account it logs in with. AllSolutions recommends a separate API user for a reporting tool, with only the permissions it needs.
In Power BI, we also define who can see each department or project.
You authorise the API user to access the companies that need to be included. In the model, we can show them side by side or combine their figures, using a consistent structure for departments and types of hours.
For the financial side, read about the financial dashboard.
Yes. You can set up the API configuration in the acceptance environment and then export it to production. That lets us test the model on a copy before it runs on live figures.
We plan this together with your application administrator.
If the reports in AllSolutions already answer your questions. Or if hours and projects are not recorded consistently: in that case, data quality comes first.
We will tell you that upfront.