Custom integration with the KringloopWijzer
Appfront builds integrations with the KringloopWijzer, the tool that maps the mineral cycle on a dairy farm. Dairy farmers who supply a dairy company affiliated with NZO complete it every year. Suppliers of feed, fertiliser and analyses, and 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 fill in and the data is accurate.
What is a KringloopWijzer integration?
The KringloopWijzer is a management tool that maps the nutrient cycle on a dairy farm: what nitrogen and phosphate come in through feed and fertiliser, what leaves through milk and animals, and what remains on the farm. Dairy farmers supplying a dairy company affiliated with NZO must complete it every year, by 15 May for the previous year. It builds on the farm-specific excretion, the BEX.
Much of the data that belongs in the KringloopWijzer sits with others: the feed supplier knows what has been delivered, the laboratory holds the silage analyses, and the dairy company has the milk deliveries. With the dairy farmer's authorisation, those parties can link their data directly to the central database, rather than the farmer retyping it. Without an integration, a supplier sends a summary, and the farmer or adviser enters it by hand.
We build custom solutions because every party is different: which data you hold, which system it lives in, and how many dairy farmers you supply. The rules for data-supplying parties, and how to connect, are set by the KringloopWijzer administrators; we take that into account in the first step.
Supplied automatically
Your deliveries or analyses go straight into the central database, without the farmer retyping them.
With authorisation
Only for dairy farmers who authorise you to do so, with authorisations tracked per client.
Data that adds up
Checks for missing or inconsistent data, so the farmer's outcome is accurate.
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 things work today. Then we assess what is needed to connect as a data supplier. The aim is for a farmer to see in the KringloopWijzer that your data is already there.
Your data, systems, clients and current way of working.
Agreements as a data supplier, and authorisations.
Data to the central database, with checks.
Go-live ahead of the season, and maintenance as things change.
What a KringloopWijzer integration actually does
The components below come up 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 inconsistent data.
Audit log
Every submission logged.
Who we build KringloopWijzer integrations for
The integration is intended for parties that hold data for dairy farmers.
Feed suppliers
Deliveries to many businesses. Delivery data is the core.
Laboratories
Silage and soil analyses. Verification matters most.
Advisers
Help with completing forms. Less manual re-entry is what's needed.
Software suppliers
Software for dairy farms. The integration is the core.
Technology and integrations
This page covers integrations with the KringloopWijzer. For sharing farm data with consent, see our page on a JoinData integration; for the agri and food supply chain, see our page on agri-food software; and for fields, see our page on field registration. You can read about our approach under software development.
Why choose Appfront for your KringloopWijzer integration?
Data a farmer retypes by hand from supplier statements introduces errors into an outcome that matters. We build around that: automatically submitted, with authorisation, and data that is correct.
Less data entry
The farmer doesn't have to retype.
Reliable
Data comes from the source.
On time
Ready for the annual deadline.
Security and privacy in a KringloopWijzer integration
The integration processes business 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 suppliers and advisers ask before getting started.
A management tool that maps the nutrient cycle on a dairy farm. Dairy farmers who supply a dairy company affiliated with the NZO complete the KringloopWijzer every year. The outcome helps the farmer manage nutrients and is used in agreements within the supply chain.
The KringloopWijzer for the previous year must be submitted by 15 May at the latest. Data submitted automatically is already in place by then, so the farmer and adviser have less work in spring.
The dairy farmer authorises you to submit data to the central database. The integration only submits for farms that have given authorisation, and tracks the status for each client. You can see clients without authorisation 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. We look at which data you can submit, and under which agreements, in the first step. We often start with the data that takes farmers the most work to take over.
The KringloopWijzer builds on the farm-specific excretion, the BEX, which allows manure production to be determined from farm data. What the outcome means for a farm is discussed by the farmer with their own adviser.
The integration validates data before submission and handles error feedback. An error goes to whoever can resolve 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 prevent farmers from retyping it.
Your data directly into the KringloopWijzer?
Tell us what data you hold for dairy farmers, which system it sits in and how many farms are involved. We'll show you what the integration would look like.