Project Proposal: Animal traceability data exchange

other

Submitted dateLast Update DateVersionApproval StatusProject Page
2008-04-01 
2013-04-15 
1.0
Animal traceability data exchange

 

 

Project Purpose

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

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

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

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

 

Head of Delegation Support

 

Geographical Focus

 

Initial Contributions

 

Resource Requirements

 

Project Leadership

 

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

 
  • YES
  • NO
 
  • YES
  • NO
 
  • YES
  • NO
 
  • YES
  • NO
 
  • YES
  • NO
 
  • YES
  • NO
 
  • YES
  • NO
 
 
  • YES
  • NO
 
  • YES
  • NO
 
  • YES
  • NO
 
  • YES
  • NO
 
  • YES
  • NO
 
  • YES
  • NO
 
  • YES
  • NO
 
 
  • YES
  • NO
 
  • YES
  • NO
 
  • YES
  • NO
 
  • YES
  • NO
 
  • YES
  • NO
 
  • YES
  • NO
 
  • YES
  • NO
 

Project Proposal Files