Twenty to three working days in advance Map of the excavation site Report deviating cable or pipe locations

Custom software for excavation notifications and KLIC information

An excavation notification has an expiry date and a schedule doesn't. You notify at least three working days before the start, the work slips a week because of rain or a permit, and the information the machine operator starts work with has expired. That isn't an administrative inconvenience but the moment damage happens.

Why the notification belongs tied to the schedule

The Dutch Information Exchange Act for Overhead and Underground Networks (WIBON) requires you to report mechanical excavation work. You file that excavation notification no earlier than twenty working days and no later than three working days before work begins. The Kadaster informs the network operators concerned, who are obliged to supply their location data.

For plans that are not yet fixed, there is the orientation request. It gives you an idea of what is in the ground without you having to dig, and it is explicitly not a substitute for the excavation notification. Anyone who breaks ground on the basis of an orientation request is not complying with the law.

In practice, the bottleneck is the time between notifying and digging. Work shifts, notifications expire, and by the time the machine operator starts, it is not always clear which data applies. On top of that, the excavator is obliged to report a deviating location if they find one, and that is something done in the trench, not in the office.

This page is about managing excavation data in the office system. What the excavation crew needs in the trench, even without a signal, is covered under the app for excavation data in the trench.

How we build this

The excavation site and its planning are the unit here. If the notification is tied to it, its validity moves with the work instead of expiring without anyone noticing.

1
Linking the planning and the notification

Which job belongs to which notification and which validity period. At most companies, those sit in two systems that don't know about each other.

2
Getting the data to the trench

The maps and the drawing package should be available at the excavation site. That means on a device that also works without a connection.

3
Building in deviating locations as an action

Finding and reporting is an obligation. We build it as an action of a few taps with a photo, because anything more than that simply doesn't get done in a wet trench.

4
Making it possible to look back

In the event of excavation damage, the question is about the day itself: which data applied, who was there, what was found. We design the recording around that question.

What the software actually does

The register of excavation sites with their notifications underpins everything. Which components you need depends on how many sites you have open at once.

Excavation sites with their notifications

For each site, which notification is in place, for which period and which network operators have supplied data. That way, the question of which data applied on a given day can be answered.

Validity monitored against the planning

If the work shifts, the system warns you that the notification is expiring before the machine starts. That is the most common cause of digging on outdated data.

Maps available at the excavation site

The supplied data is on the supervisor's device, even without a signal. In a trench outside built-up areas, that is the normal situation.

Reporting deviating locations from the field

Finding it, recording it with location and photo, and passing it on. This way, the obligation to report a deviating location reaches the right party instead of getting lost in a chat message.

Timestamped images of the trench

What was found and how it was positioned. In a dispute over excavation damage, that is the most convincing piece of evidence and the quickest to capture.

File kept per site

Notification, supplied data, checks and reports of deviations together. In the event of damage, the notification is not the evidence; the whole picture around it is.

Who we build for

How much this delivers depends on how much excavation work you have running at once. Four situations.

Civil engineering and groundworks

Many sites at once and shifting schedules. The gain here lies in monitoring validity; with dozens of open notifications, that can't be done from memory. The safety side of the work runs through your RI&E with action plan.

Installation and maintenance of connections

Short jobs at many addresses, often with a small crew. The notification per address is the job itself and must take just a few taps, otherwise it gets skipped.

Municipalities and managers of public space

You are both a client and the network operator of your own pipelines. That means the question applies on both sides: supplying what others request, and reporting on time yourself. There is a dedicated integration for exchanging data with the Kadaster.

Earthmoving and transport

You dig on behalf of someone else and are an excavator yourself. The responsibility then lies with you, even if the notification was made by the client; record who did what. If you work on a site covered by the Wwke, additional access rules apply.

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 →

Technology and integrations

Data is supplied via the Kadaster in a fixed format. We map out which integration options exist and how the files are structured for each situation before we promise anything.

Node.js / Python / .NET PostgreSQL Register of excavation sites and notifications Validity monitoring against the schedule Importing supplied data files Map view on the device, available offline Deviating location with photo and position Integration with your project administration File per location with history Reporting in the event of damage or inspection Roles per project and per location Version history on supplied data Audit logging Hosting in the EU

Why Appfront

A notification expires, a schedule shifts

We tie validity to the schedule and warn you before the machine starts. This is the most common cause of digging on outdated data.

The data belongs in the trench, not at the office

We make sure the maps are on the device and work without coverage, because that is where the decision is made.

Reporting a deviating location has to take just a few taps

Encountering and reporting is an obligation. Anything that takes more than a photo and a position simply doesn't happen in practice.

Your project administration already exists

Locations, schedules and contractors are already in there. We connect to them via integrations instead of letting a second schedule emerge.

Security and privacy

Location data for cables and pipelines is not public information. It is supplied to you for a specific excavation job, not to be stored or passed on. We therefore restrict access to the people on that project, link the data to the notification it was supplied for, and record who has viewed it.

On the retention side, there is a tension that you need to resolve explicitly. In the event of excavation damage, you need the data from the time to show what you based your work on, so discarding it afterwards is unwise. At the same time, you should not keep it indefinitely or reuse it for a next job, because then you are digging on old information again. We therefore store the supplied data linked to its notification, with a retention period and without it being usable as a current source. How we handle security ourselves is set out in our information security policy; reports from outside go through our CVD policy.

Frequently asked questions about WIBON and excavation notifications

At the earliest twenty working days and at the latest three working days before mechanical digging begins. That lower limit is where schedules fall apart: if you notify too early, you have outdated data at the start, and if you notify too late, you are not allowed to begin. That is why we tie the notification to the schedule rather than to a separate action.

No. An orientation request is meant for investigating an area when plans are not yet final. Before any actual digging takes place, an excavation notification is required. If you start digging on the basis of an orientation request, you are not complying with the law and are in a weak position if damage occurs.

The information about the location of the networks that you received with your notification must be available at the excavation site. In practice that means digitally, on a device that also works without coverage, because a printout that is three weeks old in a site cabin is not where the machine operator is standing.

Then you are required to report it. What helps is making that report as small as possible: a photo, the location and a short description, made from the trench. Anything that asks for more does not happen at the moment itself, and then it does not happen at all.

The excavator is the party doing the digging, and so carries the obligations that apply during the digging itself. The fact that someone else filed the notification does not release you from the duty to work with the correct data. That is why you should record per location who did what; in the event of damage, that is the first question.

Data is supplied via a fixed route and in a fixed format. What can be processed automatically changes over time and depends on your role. We map this out at the time of building, and we promise no integration before we have seen what is available.

In the event of damage, the discussion is about the day itself: which data applied, who was there, what was found and reported. A file per location containing the data supplied, the checks and the photos answers those questions without reconstruction. It does not determine whether you are liable; it does determine whether you can show what you did.

That depends on the number of simultaneous locations, whether the field side needs to be included, and whether it is integrated with your planning. The register with validity monitoring is usually usable quickly and removes the biggest risk; the map view on the device costs more. We give a well-founded estimate after the discovery phase.

Linking excavation notifications to the planning?

Look at how many open excavation notifications you have now and for how many of them the work has shifted. That number is your risk today. We build this both as a standalone application and as part of a broader custom software project.

Edit content