Data automatically to the KringloopWijzer With the dairy farmer's authorisation Less data entry for the farmer

Custom integration with the KringloopWijzer

Appfront builds integrations with the KringloopWijzer, the tool that maps the nutrient cycle on a dairy farm. Dairy farmers who supply a dairy company affiliated with the NZO fill it in every year. Suppliers of feed, fertiliser and analyses, as well as other parties, can link their data to the central database with the dairy farmer's authorisation. We build that integration, so the farmer has less to enter and the data is correct.

What is a KringloopWijzer integration?

The KringloopWijzer is a management tool that maps the nutrient cycle on a dairy farm: the nitrogen and phosphate coming in through feed and fertiliser, what leaves again through milk and animals, and what remains on the farm. Dairy farmers who supply a dairy company affiliated with the NZO must fill it in every year, by 15 May at the latest for the previous year. It builds on the farm-specific excretion figures, the BEX.

Much of the data that belongs in the KringloopWijzer is held by others: the feed supplier knows what was delivered, the laboratory has the silage analyses, and the dairy company has the milk deliveries. With the dairy farmer's authorisation, these parties can link their data directly to the central database, instead of the farmer retyping it. Without an integration, a supplier sends an overview, and the farmer or adviser enters it by hand.

We build custom integrations because parties differ: which data you hold, which system it sits in, and how many dairy farmers you supply. The rules that apply to parties supplying data, and how to connect, are set by the administrators of the KringloopWijzer; we take that into account in the first step.

Delivered automatically

Your deliveries or analyses go straight into the central database, with no retyping by the farmer.

With authorisation

Only for dairy farmers who authorise you to do so, with authorisations tracked per customer.

Data that is correct

Checks for missing or deviating data, so the farmer's results are correct.

How we build your KringloopWijzer integration

We start with your data: which data you supply to dairy farmers, which system it sits in, for how many farms, and how it works now. Then we look at what is needed to connect as a data supplier. The goal is that a farmer sees in the KringloopWijzer that your data is already there.

1
Mapping your data

Your data, systems, customers and current way of working.

2
Connect

Agreements as a data supplier, and authorisations.

3
Building the integration

Data to the central database, with checks.

4
Go-live and maintenance

Go-live before the season, and maintenance when things change.

What a KringloopWijzer integration does in practice

The components below feature in almost every KringloopWijzer integration. Which ones you need depends on your data.

Deliveries

Feed and fertiliser per farm.

Analyses

Silage and soil analyses.

Authorisations

Tracked per dairy farmer.

Submitting

To the central database.

Validation

Missing or deviating data.

Log

Every submission recorded.

Who we build a KringloopWijzer integration for

The integration is intended for parties that hold data for dairy farmers.

Feed suppliers

Deliveries to many farms. Supplying the data is the core.

Laboratories

Silage and soil analyses. The checks matter most.

Advisers

Help with filling it in. Less retyping is what is needed.

Software suppliers

Software for dairy farms. The integration is the core.

Technology and integrations

This page is about integrations with the KringloopWijzer. For sharing farm data with consent, see our page on a JoinData integration, for the agri and food chain our page on agri-food software, and for parcels our page on parcel registration. You can read about our approach on building software.

If you also want data on animals, feed and milk production from AgroVision Cows in your own system, read more about our AgroVision Cows integration.

If your farm's production and feed data comes from Lely Horizon and you want to use it without retyping, read more about our Lely Horizon integration.

KringloopWijzer Central database Dairy farmer's authorisation Feed and fertiliser deliveries Silage analyses BEX Data validation Error feedback Results for advice Log

Why Appfront for your KringloopWijzer integration?

Data that a farmer retypes by hand from supplier statements introduces errors into a result that matters. We build on that: data delivered automatically, with authorisation, and data that is correct.

Less data entry

The farmer doesn't retype anything.

Reliable

Data comes straight from the source.

In time

Ready for the annual deadline.

Security and privacy in a KringloopWijzer integration

The integration processes farm data from dairy farmers, which may only be shared with their authorisation. Access credentials are stored encrypted, and every submission 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 KringloopWijzer integration

Questions that suppliers and advisers ask before they get started.

A management tool that maps the mineral cycle on a dairy farm. Dairy farmers who supply a dairy company affiliated with the NZO complete the KringloopWijzer every year. The result helps the farmer manage minerals and is used in agreements across the supply chain.

The KringloopWijzer for the previous year must be submitted by 15 May at the latest. Data that has been delivered automatically is already in place by then, so the farmer and the adviser have less work to do in the spring.

The dairy farmer authorises you to deliver data to the central database. The integration only delivers data for farms that have given authorisation, and keeps track of the status for each customer. Customers without authorisation are shown separately, so you can ask them to provide one.

For example, deliveries of feed and fertiliser, silage analyses and other data that belongs in the KringloopWijzer. Which data you can deliver and under which agreements is something we look at in the first step. We often start with the data that costs farmers the most effort to copy over.

The KringloopWijzer builds on farm-specific excretion, the BEX, which makes it possible to determine manure production based on farm data. The farmer discusses what the result means for a farm with their own adviser.

The integration validates data before submission and processes error feedback. An error goes to whoever can fix it, so the farmer's data is correct before the KringloopWijzer is submitted.

For feed and fertiliser suppliers, laboratories, advisers and software vendors who hold data for many dairy farmers and want to spare the farmer from retyping it.

Your data straight into the KringloopWijzer?

Tell us what data you hold for dairy farmers, which system it is in and for how many farms. We'll show you what the integration would look like.

Edit content