Project control Construction, infrastructure and installation Planning and costs

Custom construction data analytics

On a construction project, reality runs ahead of the administration. The work is further along than what the system shows, subcontractor invoices arrive after the fact, and extra work is agreed on the scaffolding before it is recorded anywhere. Anyone looking at their dashboard is looking at the past. Appfront builds analytics systems that bring planning, work budget, hours, purchase commitments and invoicing onto a common footing, so a deviation becomes visible while there is still something you can do about it.

What it is and what this page covers

Construction data analytics brings together data that arises in separate systems during a project: estimating and work budget, planning, time registration, purchase orders and call-offs, subcontractor invoices and the payment schedule towards the client. Each system is right within its own boundaries. A usable picture only emerges when they share a common basis and the same reporting date.

If you mainly want data to flow between two systems, for example project administration to accounting, a Bouw7 integration is the shorter route. If you want to predict which work is at risk of running out of control, that belongs with a predictive analytics dashboard. Construction data analytics comes first: you have to establish what the situation is now, otherwise a forecast means nothing.

Intended for directors, project managers and controllers at main contractors, installers, infrastructure companies and developers running multiple projects at once.

Where does this project stand today?

Actual costs are known up to the last processed invoice, progress up to the last weekly report. Those reporting dates are weeks apart, and the margin everyone is arguing about sits in between.

Why did this project turn out better?

After completion, project A turns out to be more profitable than B. As long as the two classify their costs differently, the answer is a reconstruction from the memory of those involved.

Are our estimating norms still right?

An estimate rests on norms from earlier work. Without reliable post-calculation per building element, those norms get copied forward for years without ever being checked against what the work actually cost.

The administration lags behind the building site

A construction project does not produce today's administration today. Progress is recorded at the end of the week, timesheets are processed after that, and the subcontractor's purchase invoice follows once they report completion. Whoever reads the "actual" column is reading events from weeks or even months ago.

For financial reporting that is not a problem, because it only has to be right on the balance sheet date. For project control it is fatal: if in week 20 you are reading how the project stood in week 14, you can do nothing with it.

Execution runs ahead

The brickwork is finished and the installer has started, but the associated costs are not recorded anywhere yet. The reverse happens just as often: materials have been delivered, so the costs exist, but nothing has been built with them yet. As long as progress and costs are not measured in the same unit, every comparison is misleading. Progress deserves its own record, in quantities or percentage complete per building element.

The invoice tail of subcontracting

Subcontractors invoice once their part is complete, sometimes per instalment, sometimes only after a completion report has been approved, sometimes months later. Until then the cost column shows nothing, even though the commitment was entered into long ago. The answer is a commitments ledger: purchase orders, call-offs and subcontract sums appear in the project overview when the order is placed, not only when the invoice arrives.

Variations start verbally

This is where projects leak money. The client asks for a change on site, the site manager agrees, and the paperwork follows days later or never. Under Article 7:755 of the Dutch Civil Code, a contractor can only claim a price increase if they gave timely notice of the need for it, unless that need should have been obvious. Variations therefore deserve their own flow with their own statuses: executed but unapproved variations are risk, approved but uninvoiced variations are working capital.

Two truths about the same work

The planning knows phases, activities and dependencies. The financial administration knows cost types, cost objects and ledger accounts. The same week of work appears in one system as structural work on the ground floor in working days, and in the other as postings to labour, materials, equipment and subcontracting. A key shared by both structures almost never exists, so it has to be designed. That is where the value is created, and where the friction lies.

What such a system needs to do

This leads to a list of requirements that weighs more heavily than any visualisation. The most important: the system distinguishes between what has been invoiced, what is committed and what has been delivered. Three figures that are out of step.

The methodology resting on that distinction is called earned value management outside construction, and was formalised in 1998 as ANSI/EIA-748. The core is usable without the full apparatus: compare the actual costs not with the budget to date, but with the budgeted value of the work that is complete. A project that is behind schedule and therefore under budget looks healthy in an ordinary budget-versus-actual chart.

The second requirement is looking ahead. The forecast at completion, the expected cost to complete added to the actual costs, is the only figure that can still be steered. That forecast is partly calculation and partly judgement; keep both, so it becomes visible how earlier forecasts by the same project manager compared with the outcome. That is sensitive, and at the same time the most valuable reporting such a system delivers.

The data comes from a construction or ERP package such as Exact Bouw7, 4PS Construct or AFAS, from a planning package such as Asta Powerproject, Primavera P6 or KYP Project, and from a procurement flow that increasingly runs via the DICO Standard and Peppol. With BIM, quantities from the IFC model can serve as a measure of progress, provided the bill of quantities is included in the export.

  • Invoiced, committed and delivered shown separately
  • Commitments booked at order, not at invoice
  • Additional work as its own flow with its own status progression
  • Forecast at completion alongside the realised costs
  • Explicit key between planning and cost structure
  • Every figure traceable to its source record
Exact Bouw7 4PS Construct AFAS Profit Asta Powerproject Primavera P6 IFC quantities DICO Standard Peppol Power BI / Qlik

Comparability is an organisational issue

Benchmarking between projects is the question management teams ask most often and the hardest one to answer. Not because the technology falls short, but because project A categorises its costs differently from project B. If one estimator books the crane under equipment and another under general site costs, even the best dashboard ends up comparing unlike quantities.

Standards exist for this. NEN 2699:2017 sets out the classification of investment and operating costs of real estate and replaced the older NEN 2631, NEN 2632 and NEN 2634. For classification by building element, NL/SfB is the common element classification, maintained by Ketenstandaard Bouw en Techniek. In addition, commercial building uses the STABU system, and civil engineering uses CROW's RAW system, in which specification items are described as cost-homogeneous and measurable, and adjustable quantities have their own settlement regime.

Choosing a standard is the easy part. The work lies in agreeing that everyone actually sticks to that coding, in estimating, in procurement and on the timesheet, and in accepting that estimators and work planners have to show discipline for something that gives them little in return. We can support this with mandatory fields and validations, but part of this process is about consultation rather than building software. If you skip that, you end up with a dashboard that places figures side by side that don't belong together.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

When standard reporting is enough

Many construction companies get a long way with what is already there. Exact Bouw7, 4PS Construct and AFAS offer project monitoring with a working budget, and putting a standard BI tool on top of that delivers usable reporting for much less effort. If your project administration mostly runs in one package, and your questions are essentially budget versus actuals per cost type, then custom software is the more expensive route to the same answer. For some readers of this page, that is the honest conclusion.

Custom software starts to pay off when data has to come from systems that don't know each other. A schedule in Powerproject, an estimate in a separate package, hours via an app on site, procurement in the ERP and a client who demands their own reporting format: combining all that requires a layer that none of those vendors supplies. The same applies when your way of steering projects is itself a differentiator, for example because you work in building teams or with two-phase contracts and standard reporting doesn't recognise that contract form.

The third reason is the most common: you're stuck on a vendor's roadmap. The report you need has been on the wish list for two releases. Bear in mind that custom software shifts maintenance: documentation, keeping integrations up to date when a vendor changes its API, and revalidating figures after every release become your responsibility or that of the party you contract. That belongs in the trade-off.

  • Project data sits in systems that don't know each other
  • Planning and financial administration need to line up
  • You work with construction teams, two-phase contracts or UAV-GC
  • Clients demand their own reporting format
  • Estimating norms need to come from your own post-calculation

Frequently asked questions about construction data analytics

The questions clients ask just before they decide.

For many companies, that is the right choice. If your project administration mainly runs in a package such as Exact Bouw7, 4PS Construct or AFAS, and your questions are essentially budget versus actuals per cost type, a standard BI tool on top will do. Custom work only becomes interesting when data has to come together from systems that don't know each other.

This is a contractual question and it should be answered before the build starts. Record who owns the source code, the data models and the transformation logic, and where the repository is hosted. For each integration, ask for a description of which field comes from which source system. A system in which nobody can explain how a figure comes about is worth little once the developer leaves.

By agreeing up front which figure is meant for what. The accounting for projects in progress follows RJ 221 and generally uses the percentage-of-completion method, with its own rhythm and valuation principles. A management dashboard wants a usable indication rather than an audited figure. The two may differ, provided the difference can be explained.

Yes, but not with benchmarking as the first goal. Start with the projects that are comparable, or with analyses that don't need uniform coding, such as the lead time of additional work. In parallel, agree a coding convention based on NEN 2699 or NL/SfB. Recoding old projects is possible, provided the records were detailed enough.

Usually yes, because these packages offer APIs or exports that are sufficient for this purpose. The limitations lie elsewhere: which fields are available, how often you may retrieve data, and what happens when the supplier releases an update. We build the integration so that a change on the source side becomes visible rather than quietly producing wrong figures. See also our page on Bouw7 integration.

More than companies expect up front, and that is the biggest risk factor. Recording progress in quantities or percentage complete, reporting additional work immediately and registering commitments at the time of order all happen on site. If that can't be done in a few taps on a phone, it won't happen and the dashboard will be empty or wrong. That is why we design the input side first.

Related services

Build a Bouw7 integration

If your main concern is data that has to flow between two systems, for example project administration to bookkeeping, an integration is the shorter route.

Predictive analytics dashboard

If you want to predict which job is at risk of getting out of hand, that is the next step. The prerequisite is historical records that are consistent enough to train on, and that is what construction data analytics sorts out first.

Shall we first check whether you need this?

Tell us which systems your project data sits in, how you determine the status of a running project today and at what point you feel you find out too late. Based on that, we'll tell you whether reporting on top of your existing package will do, or whether custom development is justified.

Edit content