Soil data in the exchange format From fieldwork via the lab to the report Checked before sending

Custom SIKB0101 integration development

Appfront builds integrations based on SIKB0101, the exchange format for data from environmental soil investigations. Boring descriptions, samples and analysis results travel as a file in line with the standard between consultancy, laboratory and competent authority. We connect your fieldwork, laboratory or reporting software to it, so data is not retyped and arrives without errors.

What is a SIKB0101 integration?

SIKB0101 is the exchange format for digital data from environmental soil investigations, maintained by SIKB. It is used between consultancies and laboratories, and between consultancies and the authorities that manage soil information. The latest version is 15.0, and SIKB0101 is listed as an open standard by the Forum Standaardisatie (the Dutch Standardisation Forum). For archaeological data there is a different format, SIKB0102.

In practice, samples are recorded in the fieldwork software, the analysis request is emailed to the lab, and the results are retyped from a PDF or spreadsheet into the report. When delivering to the municipality or regional environmental agency, a file is produced that does not always pass validation. Every manual step is a chance of an error in data on which a decision is based.

We build custom because parties differ: which software you use, which laboratories and authorities you exchange data with, and which versions of the format they support. The format is maintained by SIKB; we make sure your system works with it. Which data your investigation must include is determined by the protocols and guidelines that apply to it.

In line with the format

Borings, samples and results as a file in line with SIKB0101, from and to your own software.

From field via lab to report

Analysis requests to the lab, results back, without retyping.

Checked

Every file checked before it is sent, with errors returned to whoever can fix them.

How we build your SIKB0101 integration

We start with your exchange: which software, with which laboratories and authorities, which versions of the format, and where retyping happens. We follow an investigation from start to finish, from fieldwork to delivery, so we can see where data currently changes form. Versions often differ between partners. We map that out, so the integration can exchange data with everyone and a new version can later be supported without major changes.

1
Mapping the exchange

Your software, partners, versions and current way of working.

2
Building the files

Data converted to SIKB0101, with validation.

3
Lab and delivery

Requests to the lab, results back, delivery to the authority.

4
Go-live and maintenance

Go-live, monitoring, and maintenance when new versions arrive.

What a SIKB0101 integration actually does

The components below come up in almost every SIKB0101 integration. Which ones you need depends on your role.

Fieldwork

Boreholes and samples from your software.

Lab order

Analysis orders to the laboratory.

Results

Analysis results back, without retyping.

Delivery

Files to the competent authority.

Validation

Files checked before sending.

Log

Every file logged.

Who we build a SIKB0101 integration for

The integration is intended for parties that exchange soil data.

Consultancies

Many surveys and labs. No retyping is the core.

Laboratories

Orders from many consultancies. Getting results back matters most.

Competent authorities

A soil information system. Importing files is what you need.

Software suppliers

Your own product. The format is the core.

Technology and integrations

This page is about integrations based on SIKB0101. For projects under BRL SIKB 7000, see our page on SIKB software; for archaeological data, our page on a SIKB0102 integration; and for laboratories, our page on laboratory software. You can read about our approach on building custom software.

SIKB0101 Version 15.0 Boreholes and borehole descriptions Samples and composite samples Analysis orders Analysis results Soil information systems Validation against the format Multiple versions Log per file

Why Appfront for your SIKB0101 integration?

An analysis result that gets retyped can change a decision about a site. That is what we build around: data in line with the format, from field to lab to report, and checked before sending.

Error-free

No retyping of results.

Faster

Results straight into the report.

Right first time

Delivery that passes validation.

Security and privacy for a SIKB0101 integration

The integration processes data on locations, owners and soil quality. Connections are encrypted, access is set up per role, and every file is logged.

The integration runs in a European data centre or in your own environment, with encrypted storage and daily backups.

Frequently asked questions about a SIKB0101 integration

Questions soil sector parties ask before getting started.

The exchange format for digital data from environmental soil investigations, maintained by SIKB. It defines how projects, boreholes, samples and analysis results are described, so that parties can exchange them without errors. Because it is an open standard, any party and any software package can use it.

SIKB0102 is the format for archaeological data, such as finds and documentation for the repository. SIKB0101 covers environmental soil investigations. They share the same maintainer but have a different subject. If you work with both types of investigation, a single integration can support both formats.

The latest version is 15.0. Not all parties switch at the same time, so an integration sometimes has to handle several versions. We map out which versions your partners use in the first step.

Yes, if the laboratory supports SIKB0101. The order goes to the lab as a file, with the samples and the requested analyses, and the results come back into your software the same way. They then sit directly with the right samples and can be used in the assessment and the report without retyping.

As a SIKB0101 file, which the soil information system of the municipality, province or environmental agency can import. The integration validates the file first, so it is right the first time. Which data the competent authority wants to receive sometimes differs per authority; we record that per recipient.

The integration reports which data is missing or incorrect, with the reason. That way whoever holds the data can complete it before the file is sent. It is often a matter of fields that were not filled in on site; by making them mandatory in the fieldwork software, they will come through automatically from then on.

For consultancies and laboratories that exchange a lot of data, for public authorities with their own soil information system, and for suppliers of fieldwork and laboratory software who want to support SIKB0101.

Soil data without retyping?

Tell us which software you use, which laboratories and public authorities you exchange data with, and where you currently retype data. We'll show you what the integration would look like.

Edit content