Added by Claudio Meza, edited by Claudio Meza on Aug 02, 2013

Labels

 
(None)

You are viewing an old version (v. 7) of this page.
The latest version is v. 8, last edited on Aug 02, 2013 (view differences | )
<< View previous version | view page history | view next version >>

Table of Content

1. Project purpose

The purpose of the project is to create Business Process Models and Business Class Diagrams to document business scenarios and business transactions involved in exchange of information about animal and animal products traceability.

This project updates Project P094: Livestock life record, submitted in april, 2008



Version: 1.0

2. 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: concerning 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 retrieving 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 of 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 includes data on breeding, transport, processing and selling farm animal production and/or their products and by-products (e.g. milk, meat, eggs, wool, etc.) and also similar data on 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 the second stage we will focus on the movements of animal products.
The outputs will be harmonized XML schemas to support the business process.

3. Project deliverables

The project deliverables are:

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.

4. Exit criteria

The exit criteria, indicating that 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.

5. Project Team membership and required functional expertise

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

6. HoD support (required for technical standards, business standards and UNECE recommendations)

List at least three Country heads of delegation who support this project, and include their written expression of support using the template in annex IV...
Heads of Delegation of France, The Netherlands and Canada are supporting this project.

7. Geographical Focus

The geographical focus is global, initial contribution is expected from European Union Member States, Canada and all other interested countries.

8. Initial contributions

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

9. Resource Requirements

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.

10. Project Leadership

Project Leader: Bruno PREPIN [ Bruno.PREPIN@agroedieurope.fr]
Editors: Gaëlle Cheruy Pottiau/Frans Van Diepen [ gcheruy@agroedieurope.fr]

Note to user: Each UN/CEFACT project proposal must specify the name and email address of at least one proposed Project Convener and at least one proposed Editor.

11. Milestones (repeat per deliverable)

ODP Step ODP Name Estimated Completion Date Comment
1 Project Inception 15.09.2013  
2 Requirements Gathering 31.10.2013  
3 Draft Development 31.12.2013  
4 Public Review 31.01.2014  
5 Project Exit 30.09.2014  
6 Publication 30.03.2014  
7 Maintenance 30.09.2014