Smooth and dynamic data exchange between farms, milk recording organizations and the lab

machines.

A practical example

Harm-Jan van der BeekUNIFORM-Agri

Agenda1

Introduction of UNIFORM-Agri2

Introduction of the project3

Overview of the dataflow4

Validation of data5

A dynamic system6

Standardization of data exchange 7

What is next?..

Introduction UNIFORM-AgriThe Company (“UA”);International operating company specialised in Dairy Herd Management Software.Over 10.000 Farmers using it daily in over 50 countries.

Features; -

Over 100 national interfaces (incl.: DE, DK, NL, IT, UK, FR, BE, SW, AT, ES, PL, RU & others) -

Interface with parlor/robot systems (2-way)with: DeLaval, SAC, GEA, Lely, BouMatic, DairyMaster,

Fullwood, Afikim, Panazoo a.o. Other links: Heatime SCR, Nedap Velos, SmartBow, Engs, & TMR-tracker

-

User Friendly, Fast & Easy data entry, high quality analysis and solid data validation

Solutions for DHIA and Semen companies for:Milk Test Manager (MRO) , Conception (AI), M84U (semen)

Introduction of the ProjectThe Project;A milk recording organisation with just over 1000 members in the

Netherlands with it’s own lab wanted to have the complete solution for their service in house. And they wanted to have more flexibility is using extra information from the lab machine to give added value to their service.

Challenges; Smooth dataflow between the farms, the lab machine, their central database.Limited Budget, flexibility in adding new features, No real IT expertise with MRO.Web-based system, and ICAR approved milk recording status.

Partners in the project;

Overview of

the dataflow;

-

from farms

-

from 3e

party

-

from the Lab

and

-

to the farms

(depending on software)

Data flow back to the farmer

MRO

3e

party data

Server

Data flow from farm

What about validation of data?Validation of data for the MRO;Data from systems on farm can have quality issues;

-

Correct (validation of data at entrance)-

Up to date (validation of data at entrance)-

Complete (depending on situation)

Note; When data is used by the farmer for his own management it has a positive effect on the quality of data; -

no double entry, -

there is an intrinsic attitude to be correct,-

interfacing to on farm hardware stimulates correct data entry!

How can this be dynamicSuch a complex system, and still has to be dynamic, because;-New on farm sensors (milk meters, and processors)-New or up-dated on farm herd management software-New information from the lab machine (Delta Instruments has multiple)-New information to be send to the farmer (electronic and pdf)-New presentation of new information in on farm software.-Modern way of milk recording; not all cows every x weeks.

This MRO has chosen to play a role in on farm software as well with an experienced party who can handle interfaces on farm.And a good working relation with other partners for continues up-dates!

Standardization of data exchange

Standardization of data exchange is a challenge. Why?-There is a lot of well functioning data-exchange in use.

(many interfaces with parlor systems, including old ones)-In scope of a big project, just an exchange (1 to 1) is quicker.-“You need 2 to Tango”. If one can’t or does not want……

But what can we do?-Re-use existing protocols and data formats is a 1st step-Using standard (ICAR) Data-dictionary as much as possible-And we should do more

What is next?

-

2nd system will start later this year in Sweden, also with several exclusive interfaces and tools.

-

New info/data is coming from the Delta Instruments lab machine and needs to be implemented (central and for the farmer)

Thank you for your attention.

Screenshots:

MTM menu:

Farm specific settings:

Animal data (receive data button):

Sample form (send to farmer when sampling is scheduled):

Data input

• Manual• EMM• Robot file• Sample file

Progress bar

for required data. 4 steps.

Manual input

MPR Report:

MPR Report:

Farm specific sample settings:

Results in management system:

Questions?