Project

A. General Information

1. Title

Electronic phytosanitary certification between Argentina and Chile

2. Status of the project
Operating
3. Implementation period of the project/service:
From
2020
To
Present
4. Website
https://www.ippc.int/en/news/argentina-and-chile-set-a-milestone-with-the-appli…
5. Geographical coverage
Bilateral
Participating countries: Argentina, Chile
6. Participating agencies/entities of the project/service:
a. Development stage
Lead agencies/entities
National plant protection organizations (NPPO) of Argentina and Chile
Other participating agencies/entities
--
b. Operational stage
Lead agencies/entities (op)
National plant protection organizations (NPPO) of Argentina and Chile
Other participating agencies/entities (op)
--
7. Main stakeholders/beneficiaries of the project
Traders (big enterprises)
Traders (SMEs)
Customs brokers
Customs
8. Business process category of the project
Regulatory/official control

B. Lessons Learned

9. Summary description of the project/service
Brief Summary

the NPPOs of Argentina and Chile have removed the use of paper for Phytosanitary Certificates by implementing the IPCC e-Phyto solution for the exchange of all their trade of plant commodities. It aims at facilitating safe trade in a more expeditious, transparent, reliable, and paperless manner.
 

a. Objective(s)

Beginning on 04 May 2020, Argentina and Chile have implemented electronic phytosanitary certification without paper for all their plant trade within the framework of the guidelines and development carried out by the International Plant Protection Convention (IPPC). The NPPOs of Argentina and Chile began the exchange of electronic phytosanitary certificates (PCs) through the Hub developed by the IPPC. The Hub allows both NPPOs to transfer PCs to each other electronically through their own national systems

b. Business need for the project (background)
--
c. Business process covered*

Exchange of electronic Phytosanitary Certificates.　 

d. Overall architecture and functionalities*

Use of the Hub is voluntary

The Hub is a single, multilateral system

The Hub will be available 24/7 (secure and monitored)

No information (messages, transactions) should be lost

There is a single exchange protocol

The IPPC determines the version of UN/CEFACT schema

Participating countries will require a National System to exchange ePhyto through the Hub or use the Generic system

e. Relevant document/figure
--
10. Documents and data exchanged via the project

Phytosanitary Certificates 

11. Data models/databases, proprietary solutions, hybrid approaches

Please refer to the link https://www.ephytoexchange.org/doc/HUB_Web_Service_API_EN.pdf

12. Main challenges faced during the project

Issues with regards to digital signature.

Resistance to fully remove paper.

13. Lessons learned from the project

Interactive work is required not only within the NPPO but between countries.

14. Main benefit(s) of the project
Enhanced regulatory compliance*
Transaction Cost savings*
Transaction Time savings
Simplified process
Increased trade flow
14A. Elaborations/detailed description on benefits gained

Reduction in trade time

Improved security

Simplification of information flow between traders and government

Better evaluation of risks

Ability to address certification problems in advance of commodity arrival

Expedited clearance of commodities

15. Technical/financial/capacity building/other assistance
--
16. Future plan for expansion of the project
--
17. Other information or relevant references on the project
--
18. Relevant document regarding the project
--

C. Relevant Standards

19. Name(s) of any international, national legal instrument underpinning the project
Bilateral agreement between Argentina and Chile
20. Electronic message standard
20A. Electronic message standard supporting the project
XML:
- UN/CEFACT BRS/RSM
20B. Type of standard for electronic message applied for the project
International standard
21. Technical communication standard
21A. Technical communication standard supporting the project
N/A
21B. Type of technical communication standard applied for the project
--
22. Security-related standards*
22A. Security-related standard supporting the project
--
22B. Type of security-related standard applied for the project
--
23. Other Technical Information
23A. Interface developed for data exchange with an internal system
--
23B. Other technical implementation information
--