08.11.2014 Views

2454 final report.pdf - Agra CEAS Consulting

2454 final report.pdf - Agra CEAS Consulting

2454 final report.pdf - Agra CEAS Consulting

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Evaluation of the Community Plant Health Regime: Final Report<br />

DG SANCO Evaluation Framework Contract Lot 3 (Food Chain)<br />

Plant Passport system: preliminary analysis of each option<br />

Option: Description Impact Advantages Disadvantages<br />

document template);<br />

Partial (common<br />

fields in free<br />

document template);<br />

Some distinction may be needed<br />

between categories of plants, and<br />

harmonisation pursued within<br />

each category (rather than across<br />

categories), but the number of<br />

categories would be limited (e.g.<br />

young plants versus others).<br />

plant health document;<br />

Easier to find information; could<br />

result in reduced administrative<br />

burden for private operators and<br />

for NPPOs;<br />

Facilitates inspections<br />

Improve coordination between<br />

NPPOs<br />

in the case of full harmonisation;<br />

In case of PP information is<br />

included in trade documents,<br />

redefinition of trade documents<br />

May lose flexibility for specific<br />

sectors with specific<br />

requirements.<br />

iii variant<br />

iv. Setting up an EU<br />

wide electronic<br />

database<br />

A variant to option iii<br />

would be to replace PP<br />

document by a health<br />

mark or logo, with all the<br />

necessary information<br />

and details stored in an<br />

electronic database.<br />

To store electronically<br />

plant passport related<br />

information. Database<br />

accessible only to CAs<br />

and registered operators<br />

(different access levels<br />

and options could be<br />

considered, as under<br />

EUROPHYT or under<br />

TRACES systems).<br />

High.<br />

Pre-requisite is full development<br />

of electronic database to ensure<br />

traceability (option iv).<br />

High.<br />

Actual costs to depend on<br />

implementation.<br />

Can result in potential savings if<br />

used in conjunction with option<br />

iii, to replace rather than add to<br />

detailed information provided in<br />

PP document, particularly with<br />

variant to option iii) (logo/mark).<br />

Full harmonisation;<br />

Improves visibility (further than<br />

PP), thus further product<br />

traceability;<br />

Simplification/modernisation of<br />

current system;<br />

Can draw from experience of<br />

similar system used in animal<br />

health (veterinary health mark +<br />

TRACES)<br />

Improves degree of transparency<br />

between MS;<br />

Improves traceability, especially<br />

when combined with option iii);<br />

Can contribute to simplification<br />

of used in conjunction with<br />

option iii, particularly its variant;<br />

Facilitates updating, referencing<br />

and exchanging information<br />

between relevant parties;<br />

Can draw from experience of<br />

similar system used in animal<br />

health (TRACES);<br />

Costs of setting up and running<br />

(option iv) can be very<br />

substantial;<br />

Only feasible in conjunction<br />

with option iv)<br />

Can carry significant costs<br />

(depending on implementation);<br />

Need to identify appropriate<br />

body and resources (COM/MS)<br />

for managing database<br />

development, maintenance and<br />

running;<br />

Feasibility, given the large scope<br />

of products/pests (compared to<br />

animal health sector) is an issue.<br />

Food Chain Evaluation Consortium 356

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!