Animal traceability data exchange
other Linktoparent
Submitted date | Last Update Date | Version | Project Proposal Status | Project Page | |||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
|
| Animal traceability data exchange |
Project Purpose
Text Area | ||||
---|---|---|---|---|
| ||||
The purpose of the project is to create Business Process Models and Business Class Diagrams to document the business scenarios and business transactions involved in the exchange of information about animal and animal products traceability. |
Project Scope
Text Area | ||||
---|---|---|---|---|
| ||||
The project proposal has very broad scope. In this project we will start sub projects dedicated to a manageable scope. We will describe the different processes depending on the species concerned: - Traceability processes for individual animals - Traceability processes for groups of animals - Traceability processes for animal products Business cases supported by these processes are: - business to business : cooncerning animals / groups of animals/ animal products, events within a country or transborder events. - business to government :for example, regulatory requirements ( animal passport) The term “animal” designates the individual animal (e.g cow ) but also the group of animals (poultry, pigs, fish etc.). The definition of traceability is to retrieve information about locations and events, what happened to the animal or the group of animals or animal products. (OIE (World Organization for Animal Health): definition about animal traceability: Animal traceability is the ability to follow an animal or a group of animals during all the stages of its life.) The information exchanged concerns with breeding, transport, processing and selling farm animal production and/or their products and by-products (e.g. milk, meat, eggs, wool, etc.) and also the fish sector. The processes concerned are: - Breeding - Animal holding information - Health and sanitary issues (veterinary information, drugs, ) - Processing of the animal - Animal products and by –products At the first stage, we will focus on the movements of animals or groups of animals from one location to another and in a second stage we will focus on the movements of animal products. The outputs will be the harmonized XML schemas to support the business process. |
Project Deliverables
Text Area | ||||
---|---|---|---|---|
| ||||
The project deliverables include: a. A Business Requirements Specification (BRS) document containing Business Process Models covering electronic business processes b. A guide for users which assist them to select the model appropriate to their needs c. A Requirements Specification Mapping (RSM) document describing the message structures (as class diagrams) for the business transactions d. XML Schemas to implement the message structures for the business transactions |
Exit Criteria
Text Area | ||||
---|---|---|---|---|
| ||||
The exit criteria that when met will indicate the deliverable has been completed, are specified in the table below. a. A Business Requirements Specification (BRS) document containing Business Process Models covering electronic business processes · Completed BRS. · Public review and logs showing how comments have been addressed. b. A guide for users which assist them to select the model appropriate to their needs · Completed Guide. · Public review and logs showing how comments have been addressed. c. A Requirements Specification Mapping (RSM) document describing the message structures (as class diagrams) for the business transactions · Completed RSM. · Public review and logs showing how comments have been addressed. d. XML Schemas to implement the message structures for the business transactions · Completed XML Schemas. · Public review and logs showing how comments have been addressed. |
Project Team Membership and Required Functional Expertise
Text Area | ||||
---|---|---|---|---|
| ||||
Membership is open to experts with broad knowledge in the area of animal production within all countries, UN/CEFACT projects and the functions of UN/CEFACT, and its groups. In addition, Heads of Delegations may invite technical experts from their constituency to participate in the work. Experts are expected to contribute to the work based solely on their expertise and to comply with the UN/CEFACT Code of Conduct. Initially the project team is composed of: Niki DIECKMANN – The Netherlands Frans VAN DIEPEN – The Netherlands Gaëlle CHERUY POTTIAU – France Eric AUBIN - Canada |
Head of Delegation Support
Text Area | ||||
---|---|---|---|---|
| ||||
Heads of delegation of France, The Netherlands and Canada are supporting this project |
Geographical Focus
Text Area | ||||
---|---|---|---|---|
| ||||
The geographical focus covers the globe, initial contribution is expected from European Union Member States, Canada and all countries interested. |
Initial Contributions
Text Area | ||||
---|---|---|---|---|
| ||||
The following contributions are submitted as part of this proposal. It is understood that these contributions are only for consideration by the project team and that other participants may submit additional contributions in order to ensure that as much information as possible is obtained from those with expertise and a material interest in the project. · Cattle Registration Information exchange (CRIE) documentation – CCL10A · eLabs – CCL 12B · Previous work on Livestock Life Record draft data model · GS1 – ebMeat |
Resource Requirements
Text Area | ||||
---|---|---|---|---|
| ||||
Participants in the project shall provide resources for their own participation. The existence and functioning of the project shall not require any additional resources from the UNECE secretariat. |
Project Leadership
Text Area | ||||
---|---|---|---|---|
| ||||
Project Leader: Bruno PREPIN Editors: and other persons (to be decided) : Gaëlle CHERUY POTTIAU Frans VAN DIEPEN |
Milestones
DELIVERABLE NAME | Project Inception | Expected Completion Date | Requirements Gathering | Expected Completion Date | Draft Development | Expected Completion Date | Public Review | Expected Completion Date | Project Exit | Expected Completion Date | Publication | Expected Completion Date | Maintenance | Expected Completion Date | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Project Proposal Files
Attachments | ||
---|---|---|
|