Skip to content

L1NDA Power BI dashboard

We bring planned and actual hours and costs from L1NDA into Power BI, broken down by branch and scheduling level. For DutchSail, we’re developing a real-time dashboard.

With our real-time dashboard, DutchSail’s coaches track their sailors’ performance in the simulator

“The experts at Data Science Lab helped us streamline our dataflow by looking at the broader picture as well as solving the difficult IT issues we had, with their help we explored the possibilities of data analysis in sailing.” Dirk-Jan Korpershoek, DutchSail

Read the case study

Which branch consistently schedules more hours than are worked, and what does that cost?

L1NDA shows planned and actual figures by branch and period. To include freelancers, till takings and data from multiple years, you have to combine them again for each question. In Power BI, you set this up once, and the historical data remains available.

Book a call

Planned and actual hours and costs from L1NDA, side by side by branch, team and scheduling layer

Discuss your branch figures

Planned versus actual

Planned and actual working hours and costs by branch, scheduling layer and team, per day, as provided by the Open API Metrics calls.

Labour costs alongside revenue

Costs by branch alongside revenue by revenue category, if your point-of-sale integration sends that data to L1NDA. Otherwise, we read revenue directly from the point-of-sale system.

Your own staff and freelancers

Hours and costs for your own staff and freelancers via Temper or YoungOnes, shown separately or together by branch and period.

One view across all branches

Branch managers and the franchisor see the same figures, just as the coaches at DutchSail track their sailors’ performance in a single real-time dashboard.

Before loading, we establish which scheduling layer belongs to each branch and revenue group

  1. Branches and scheduling layers

    Which branches, scheduling layers, teams and revenue groups exist, and which hours and costs count as actuals.

  2. Open API and an initial overview

    After submitting the request, you create a token in the SSP. Then we compare planned and actual figures for one branch and check them against L1NDA.

  3. Loading and storing periods

    Retrieve and store each period yourself, then load only additional data. Responsibility for managing access rights and refreshes is defined.

Is L1NDA’s statistics page enough, or do you need your own model?

Talk it through with us

A good fit if

You work with multiple branches or a franchise, use freelancers alongside your own staff, or compare costs and hours over several years with revenue, budgets or salaries.

Not a good fit if

You have one location, and L1NDA’s Statistics page already gives you the answers you need by letting you break down the figures by branch or contract type. Managing your own Power BI model would then take more work than it’s worth.

What determines the scope

The number of branches and rota layers, whether revenue categories have the same names throughout, whether freelancers are included, which other sources are added, and whether your team will handle maintenance afterwards.

Does L1NDA’s Open API cost extra?

Yes. According to L1NDA’s help centre, the Open API has a separate charge per location, and you need to request it from their support team. That matters when you have many branches, so we’ll set out the costs in advance.

Statistics in L1NDA itself, the Open API, or everything together in a data warehouse?

Statistics in L1NDA

Choose this if one location is enough. You can select a period and interval, break down the figures by branch or contract type, and compare years side by side. But you start from scratch with each new question.

The Open API

Choose this if you compare multiple branches and adjust staffing costs each week. Our advice: retrieve the figures for each period in your own data-loading step, so you retain the historical data.

Together with till and payroll data

Choose this if you want to combine scheduling data with till, payroll and financial figures from other systems. Read about building a data warehouse.

We build dashboards that show you where you can make immediate adjustments

Since 2016, Data Science Lab has worked on applications of data and AI. We are also a Microsoft Partner for Fabric. For DutchSail, we are developing a real-time dashboard that shows coaches where their team can improve.

Book an introductory meeting

In our first conversation, we’ll go through your branches, your rota layers and the L1NDA statistics you currently export

Stef Stoelwinder

Stef Stoelwinder

Business Development

Stef is your first point of contact. In our first conversation, we’ll discuss your branches, your L1NDA environment and the reports you’re currently missing.

Which branches and scheduling layers do you want to compare in L1NDA?

Tell us how many branches you have and which point-of-sale and payroll systems you use alongside L1NDA. We’ll reply by email, or we can arrange an initial conversation.

Enter a valid email address.

Let us know how we can help you.

Frequently asked questions

Through L1NDA’s Open API. Its help centre describes it as a connection between L1NDA and another system, such as a BI tool. After requesting access from L1NDA support, you create a token under Office, SSP, Open API. We use that token to retrieve the figures in a data-loading step, then build the model on that data.

Read how we start a dashboard with the decision someone needs to make on our Power BI dashboards page.

L1NDA documents calls for branches, teams, schedule layers, roles, employees, contracts, allowances, shift types and revenue. The Metrics calls provide planned and actual costs and working hours by branch, schedule layer, revenue group or team, as well as by employee and day.

You can import clock-in and clock-out times into L1NDA through the API; the help centre does not document a call to retrieve them.

Every Metrics call requires a start and end date, and according to the help centre, the interval can be no longer than a month. To build up several years of history, we retrieve one period after another and store the data ourselves.

After that, we only load each new period. This turns L1NDA reporting into a trend spanning years, even if a branch later closes.

L1NDA uses revenue groups linked to schedule layers. Planned and actual revenue by revenue group enters L1NDA through a point-of-sale integration or the API, and we retrieve it from there. If the revenue is not in L1NDA, we read it directly from the point-of-sale or accounting system.

For an example involving a point-of-sale system, see Lightspeed Retail in Power BI.

In the Metrics calls, you select the platform: L1NDA, YoungOnes, Temper or a combination. If you leave it blank, L1NDA includes all three.

In the model, we keep employees and freelancers separate, so you can see how many hours and how much cost come from external workers by branch and period.

Through the Open API, you can retrieve each employee’s contracts, including contract type, contract location and salary, as well as contract types with any applicable conversion factor and collective labour agreement. L1NDA’s Statistics page can calculate figures based on either the schedule or the contract.

In the model, we compare scheduled hours with contracted hours by employee and branch. For HR figures independent of the scheduling system, see the HR dashboard.

Only if that has been agreed. Salaries from contracts can also be retrieved through the Open API, so we keep the token outside the report and load only what is needed. Row-level security in Power BI then ensures each manager sees only their own branch.

We cover workspaces and refreshes on our Power BI consultant page.

They are different scheduling systems, each with its own API and terminology. L1NDA uses branches, schedule layers and revenue groups; the model follows that structure. The questions are often the same.

Read how this works with Shiftbase and Dyflexis too.