Excavation notification from your own planning Area information with the crew Deadlines and validity monitored

Custom development of an integration for KLIC notifications in the excavation process

Appfront builds integrations for companies that dig frequently and want to include the KLIC notification in their own process. The excavation notification goes from your planning or job preparation to the Kadaster, the area information comes back to the project, and the crew has that information on their phone before the first spade goes into the ground. The integration monitors whether the notification was made in time and whether it is still valid for the work.

What is a KLIC notification integration for the excavation process?

Anyone digging mechanically must first submit a KLIC notification to the Kadaster under the WIBON (the Dutch Underground Cables and Pipelines Information Exchange Act). The excavator then receives area information from the network operators: where cables and pipelines are located. The notification must be made within a statutory period before digging, and the area information must be available on site. An orientation request is intended only for preparation, not for digging.

In practice, a job planner submits the notification in the Kadaster's web application, saves the area information in a folder, and emails it to the site supervisor. With many small jobs, a notification occasionally gets lost, or a crew digs on a notification for a different address. Nobody knows whether the notification is still valid if the work overruns. And when excavation damage occurs, it becomes a search for what was available.

We build custom solutions because companies differ: how much excavation work they do, which software it is planned in, how the crews work, and which systems you use for work orders and projects. What the WIBON requires in your situation, you agree with your adviser or trade association; the integration makes sure the notification is there and that the crew has the information.

Notification from the planning

The excavation notification goes from your own planning to the Kadaster, using the data that is already there.

With the crew

The area information comes back to the project and is on the crew's phone.

Deadline and validity

Alerts when a job has no valid notification, or when a notification is about to expire.

How we build your KLIC notification integration for the excavation process

We start with your excavation work: how many notifications, who makes them, which software jobs are planned in, and how the information currently reaches the crew. We also look at what happens when a job overruns or is moved. That is where most situations arise in which a crew digs without a valid notification.

1
Mapping the excavation work

Your jobs, notifications, planning, crews and systems.

2
Notifying via the API

Excavation notifications from the planning to the Kadaster.

3
Information with the crew

Area information with the project and on the phone.

4
Monitoring and maintenance

Deadlines, validity, damage, and ongoing maintenance afterwards.

What a KLIC notification integration for the excavation process actually does

The components below come up at almost every company that digs. Which ones you need depends on your work.

Notify

Excavation notification from the planning.

Receiving

Area information with the project.

Crew

Information on phone or tablet.

Deadline

Notified in time before digging.

Validity

Alert when a notification expires.

Claims

Deviations and excavation damage recorded.

Who we build a KLIC notification integration for the excavation process for

The integration is intended for companies that dig frequently.

Infrastructure companies

Large jobs with many crews. Validity is the key issue.

Cable layers

Many notifications per week. Notifying from the planning matters most.

Landscape gardeners

Many small excavation jobs. Information with the crew is what is needed.

Network operators

Your own crews and faults. Speed is what matters.

Technology and integrations

This page is about the KLIC notification in the excavation process. For earthworks, see our page on an app for earthwork quantity estimation; for equipment, our page on an equipment planning app for earthmoving; and for soil that is being moved, our page on soil flow administration. You can read about our approach on building software.

If you want to exchange your own geo-information in line with NEN 3610, GML and OGC API, take a look at our geo standards integration.

KLIC Kadaster WIBON Excavation notification Orientation request Area information Kadaster API Deadline and validity Information on the phone Planning integration

Why Appfront for your KLIC notification integration in the excavation process?

A crew that digs on a notification for a different address, or without a valid notification, risks damage and fines. That is what we build around: notifying from the planning, information for the crew, and monitoring of deadline and validity.

Never forgotten

Every job with a notification.

The right information

The crew has the right map.

Demonstrable

What was available is on record.

Security and privacy for a KLIC notification integration in the excavation process

The integration works with data on projects, locations and the position of cables and pipes, which is confidential. Access is set up per role and per project, and a crew only sees the information for its own jobs.

The integration runs in a European data centre, with encrypted storage and daily backups. Area information is also available on the phone without coverage.

Frequently asked questions about a KLIC notification integration in the excavation process

Questions companies ask before getting started.

It submits excavation notifications from your planning to the Kadaster, retrieves the area information, adds it to the project and to the crew's phone, monitors deadline and validity, and records deviations and excavation damage.

For mechanical excavation, within the deadline the WIBON sets before digging starts. What applies in your situation, you should confirm with your adviser or trade association; the integration warns you if a job close to its start date has no notification yet.

An orientation request is for preparation, for example for a design or a quote. You may not dig on it. An excavation notification is always required for the digging itself. The integration can do both and keeps them separate.

It comes back to the project in your software and is available on the crew's phone or tablet, even without coverage. That way the crew has the right information for the right job.

The integration checks whether the notification is still valid for the new planning and gives a signal if it is not. A new notification can then be made in time.

Yes. A deviation between the area information and what the crew finds, or excavation damage, is recorded with photos against the job. What you must report, and to whom, follows from the rules and your agreements with the network operator.

Check that first. Some infrastructure and earthmoving packages have a KLIC integration, and that may be enough. Custom development makes sense if you have many small jobs, if notifications are currently made by hand, or if the information does not reliably reach the crew.

Never dig without a valid notification?

Tell us how many excavation jobs you have, where they are planned and how the information currently reaches the crew. We will show you what the integration looks like.

Edit content