European Bovine Identification and Traceability within one European country.

Short description: 
Operations and actors to establish bovine traceability at the level one EU country.
Description: 

The use case is based on:
- At birth, application of two ear tags with animal identification number
- At birth, registration and notification of births
- Registration and notification of the arrivals and of the departures in and from the holdings.
- Notification of slaughter

Holdings are locations where the animals are kept permanently. They may be:
- farms,
- markets,
- collecting centres,
- abattoirs,
- ...

Holding identification and registration is a specific process which is out of the present use case as well as the management and the distribution of ear tags.

Other use cases deal with inra EU movement (see AgriXchange use case “Animal register”)

Relevance for European agri-sector: 

Bovine livestock farming, beef and dairy:
- herd management,
- advisory services for farmers,
- accounting offices for farmers,
- animal performance data recording and herd book keeping,
- bredding value caculation
- animal disease control,
- meat labelling to keep the consumers trust and to market meat at better prices,
- crisis management.

Relevant countries or regions: 

This use case is relevant for European Union and for European Economic Area.
This use case is generalisation of use cases which are specific per country and / or per region.
This use case has been implemented by other countries mainly in order to keep their access to the European market (Argentina, Australia...). Very often, the implementation is limited to a part of livestock.

Relevant parties: 

The actors that directly play a role are:
- Responsible of holdings: farmers, traders and abattoirs,
- Government bodies and their contractors acting as registration offices,
- Meat processors and retailers which have to ensure meat traceability.

Other stakeholders
- public authorities for their data bases for :
* crisis management of zoonosis and contamination by heavy metals or any other chemical products to ensure food
safety of the consumers,
* crisis management in case of epizootic to limit the financial consequences for livestock sector and for government,
control of animal movements to prevent the outbreak of diseases,
* disease monitoring.
- veterinarians:
* animal identification numbers for field operations (vaccinations, blood sample...),
* data bases to record vaccinations and blood sample analysis.
- farmers:
* animal identification numbers which may be used for herd management or to retrieve data from different service
providers (carcass results, health status, breeding values, milk analysis...),
* data bases for on farm management,
* data bases to market their animals according commercial label requirements,
* data bases for disease monitoring at farm level.

- breeding organisations such as milk recording, artificial insemination cooperatives or breed societies:
animal identification number for field operations and data bases for data performance recording or herd book keeping.

- meat processors as well as retailer with data for their calling back product system in case of non compliance.

- European consumers: minimum information about the origin of the meat.

Relevant conditions: 

a Relevant standards

a.1 Semantic level

The EU regulation for BIT provides sound basics for:
- data model
- data dictionary
- business rules,
- ...

The UNCEFACT Business Requirements Specification (BRS) for eCert provides a data model and a data dictionary.

The International committee for animal recording (ICAR) provides list of breed code and of colour coat code.

In most of the cases the syntax of the exchanged message depends on the countries. In some cases within country it may also depends on the region or on the type of notification; for example specific syntax for abattoirs.

a.2 Different types of standards are:
- Flat file.
- National or regional standards (In France, for instance, “VSE”)
- ADIS - ISO 11787
- EDIFACT
- XML

The UNCEFACT Mapping Requirements Specifications (MRS) provides XML schemes and data type definition through XSD files.

a.3 The major part of protocol transfer is asynchronous with different types of technologies:
- ISO X 400
- SMTP with attached an file to an e mail
- FTP or FTPS
- Socket
- Web services with SOAP files
- ...

a.4 The synchronous transfer may use:
- Client / server protocol,
- HTTP and Internet,
- SOAP and web services,
- ...

b Relevant legislation and regulations
- OIE recommendations.
- FAO recommendations.
- EU 1760 / 2000 regulation.
- Additionnal natinal regulations.

- Outside EU, several national regulations.

Definition of use case variants: 

Inside EU, BIT with animal passport.
Outside EU, some countries have to implement EU BIT in order to keep their access to the EU market: Australia, Argentina, Uruguay..

Description of the information exchange processes and exchanged data: 

For businness process model see the atached diagram.

The process starts a new animal in a holding because of either a birth or an arrival.

In case of birth
-Two ear tags should be applied to the animal (see task “Apply tags”)
-The birth should be:
* registered in the register of the holding (see task “Register birth”)
* notified to the registration office (see task “Notify birth”)
* registered by the registration office (see task “Register birth”)

In case of arrival
- When the animal is arriving from a holding located in another EU member state (exchanged animal), the passport of
the member state of origin should be sent to the registration office (see task “Notify passport”) which registers the
arrival of an exchanged animal (see task ‘Register an exchanged animal”).
- The arrival should be:
* registered in the register of the holding (see task “Register arrival”)
* notified to the registration office (see task “Notify arrival”)
* registered by the registration office (see task ‘Register arrival’)

The registration office registers the arrival (see task “Register arrival”) provided that :
- When the animal is coming from an other EU country, the animal has been already registered
- When the animal is coming from the same country, a departure consistent with the arrival has been already
registered.

In case of departure
- The departure should be:
* registered in the register of the holding (see task “Register departure”).
* notified to the registration office (see task “Notify departure”).

The registration office registers the departure (see task “Register departure”) provided that:
- When the animal is leaving the holding where he was born, a birth consistent with the departure has been
already registered.
- When the animal is not leaving the holding where he was born, an arrival consistent with the departure
has been already registered.

At abattoir
- The process starts when a new animal is entering the abattoir.
- The abattoir should check the visual ear tags as well as the already registered data against the visual
characteristics of the animal (see task “Check animal”).
- The animal is slaughtered (see task “Slaughter”) and the slaughter is notified to the registration office
(see task “Notify slaughter”).
- The registration office registers the slaughter provided that a departure consistent with the slaughter has been
already registered (see task “Register slaughter”).

After slaughtering, the animal is transformed into carcasses ( see task ‘Transform into carcass’)

According the results of the veterinary inspection, carcasses are totally or partially delivered to meat
processors (see tasks “Deliver to rendering plan” or “Deliver to meat processors”).

At meat processors and retailers
Meat processors and retailers should ensure meat traceability (see task ‘Meat processing’) in order to provide
consumers with information dealing with :
* Country of birth.
* Country for rearing.
* Country for slaughtering.

Business model (see www.bizagi.com): 
Information model: 
BPM reference Description Attributes/Data
A Birth
Holding identification number
Animal identification number
Dam identification number
Birth date
Sex
Breed code
Colour code
B Passport
Authortity which has issued passport
Holding identification numbers where the animal was reared
Animal identification number
Dam identification number
Breed code
Colour code
Birth date
Sex
B Passport Holding where the animals was reared
B Passport Breed code
B Passport Birth date
C Arrival
C.Holding identification number
C.Animal identification number
C.Date of arrival
C.Reason of arrival
Known issues and bottlenecks for harmonization: 

Holding and animal identification number

Holding and animal identification numbers are pre requisites of any sound identification systems. Many issues are dealing with these numbers. At the EU level, the reliability of these numbers is rather good for a manual use. But the lack of uniform and detailed recommendations for their implementation for electronic data exchange results in a lot of errors and as consequences a decrease in reliability and an increase in costs which prevent a full development of electronic data exchange within one country or between countries.

Intra EU data exchange.

Several millions of bovine are exchanged every years between EU countries. The lack of well accepted recommendation for data exchange prevents the development of electronic data exchange. Animal passports of different types and in different languages remain the only mean to transmit data by paper. It results in a decrease of the reliability of the animal traceability when an animal is crossing a border and difficulties to exchange data which may be useful for all the stakeholders.
The existing BIT systems are aging. Most of them were built at the end of nineties. They have to be deeply renewed in most of the countries. If some recommendations would exist, it could be a good opportunity to get more harmonized and interoperable systems.

Proposed recommendations and solutions for harmonization: 

The cost / benefit of :
- Better harmonised AIT systems between the EU countries
- Interoperable AIT systems between the EU countries
is not precisely known. Some research about that would be necessary to help the responsible of AIT at the EU level and the country level to make appropriate decisions for better harmonized AIT systems.

Establish or to appoint and find the way of financing a body, accepted body by the stakeholders and able in a reactive way, for at least BIT, to:
- analyse the needs for harmonisation and interoperability,
- publish and maintain the relevant technical standards,
- improve permanently the standards according the problems met at implementation,
- provide tools to help actors in the implementation of the standards.

Start electronic data exchanges between EU countries which is one of the changes of the current regulation which is in discussion. It would be necessary and urgent to define at least a unique standard for the message by:
- analysing how the existing UNCEFACT standards could be the starting point of a unique EU standard;
- organising the maintenance and the development of these standards.

State of Implementation: 
Implemented in all EU countries
Source: 
agriXchange project team

Comments

Test of Axtool

Completed for the page Create content