Custom SIKB0101 integration development
Appfront builds integrations to the SIKB0101 standard, the exchange format for data from soil quality investigations. Borehole descriptions, samples and analysis results travel as a file under 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 most recent version is 15.0, and SIKB0101 is listed as an open standard by the Forum Standaardisatie. For archaeological data there is a different format, SIKB0102.
In practice, samples are recorded in fieldwork software, the analysis request is emailed to the laboratory, and the results are retyped from a PDF or spreadsheet into the report. When delivering to the municipality or environmental service, a file is produced that does not always pass validation. Every manual step is a chance for an error in data on which a decision is based.
We build custom solutions because every party is different: which software you use, which laboratories and authorities you exchange 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 the investigation.
Following the format
Boreholes, samples and results as a file in SIKB0101, to and from your own software.
From field through lab to report
Analysis orders to the lab, results back, without retyping.
Checked
Every file validated before it is sent, with errors returned to whoever can fix them.
How we build your SIKB0101 integration
We start with your data exchange: which software, with which laboratories and authorities, which versions of the format, and where retyping happens. We work alongside you on an investigation from start to finish, from fieldwork to delivery, so we can see where data changes hands today. Versions often differ between partners. We map that out so the integration can exchange with everyone and support a new version later without major rework.
Your software, partners, versions and current way of working.
Data converted to SIKB0101, with validation.
Orders to the lab, results back, delivery to the authority.
Go-live, monitoring, and maintenance when new versions are released.
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.
Laboratory order
Analysis orders to the laboratory.
Results
Analysis results back, without retyping.
Delivery
Files to the competent authority.
Validation
Files checked before submission.
Audit log
Every file recorded.
Who we build SIKB0101 integrations for
The integration is intended for parties that exchange soil data.
Consultancies
Many investigations and laboratories. Eliminating retyping is the core benefit.
Laboratories
Orders from many consultancies. Returning results matters most.
Competent authorities
A soil information system. Import is what matters here.
Software suppliers
A product of your own. The format is the core.
Technology and integrations
This page covers integrations to 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 way of working under building software.
Why Appfront for your SIKB0101 integration?
A laboratory result that gets retyped can change a decision about a site. We build around that: data that conforms to the format, from field through lab to report, and validated before it is sent.
Error-free
No retyping of results.
Faster
Results go straight into the report.
Right first time
Deliveries that pass 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 parties ask before getting started.
The exchange format for digital data from environmental soil investigation, 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 soil quality investigation. They share the same custodian but cover different subjects. If you work with both types of investigation, one integration can support both formats.
The most recent version is 15.0. Not all parties switch over at the same time, so an integration sometimes has to handle multiple versions. We map out which versions your partners use in the first step.
Yes, provided 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 the same way into your software. They are attached straight to the correct samples and can be used in the assessment and the report without retyping.
As a file under SIKB0101, which the municipality's, province's or environmental service's soil information system can import. The integration validates the file first, so it is right the first time. The data the competent authority wants to receive sometimes varies by government body; we record that for each recipient.
The integration reports which data is missing or incorrect, along with the reason. That lets whoever holds the data complete it before the file is sent. Often these are fields left blank in the field; by making them mandatory in the fieldwork software, they will be captured automatically from now on.
For consultancies and laboratories that exchange a lot of data, for authorities with their own soil information system, and for suppliers of fieldwork and laboratory software that want to support SIKB0101.
Soil data without retyping?
Tell us which software you use, which laboratories and authorities you exchange data with, and where data is still being retyped. We'll show you what the integration would look like.