330 likes | 598 Views
Electronic certification - status of IPPC ePhyto developments. Rebecca Lee NAPPO Technical Director ePhyto Steering Committee member November, 2012. www.nappo.org Ottawa, Canada. Steps in the development of ePhytos. Netherlands (2007), Ottawa (2009), Korea (2011), Paris (2012) meetings
E N D
Electronic certification- status of IPPC ePhyto developments Rebecca Lee NAPPO Technical Director ePhyto Steering Committee member November, 2012 www.nappo.org Ottawa, Canada
Steps in the development of ePhytos • Netherlands (2007), Ottawa (2009), Korea (2011), Paris (2012) meetings • Steering committee in place • Working Groups: • 1 - XML schema • 2 - Code lists • 3 - Communication protocols • Brazil training workshop, November, 2012
Steps in the development of ePhytos (cont.) • July 1 – October 20, 2012 • IPPC member consultation: • “Draft Appendix to ISPM 12: Electronic certification, information on standard XML schemes and exchange mechanisms” • Meeting of WGs 2 and 3 held Sept 10 to 13, 2012, in Paris
Steps in the development of ePhytos (cont.) • Current schedule: • Country comments received until October 20 • Revision of country comments and Appendix 1 at spring 2013 IPPC Standards Committee meeting • Substantial concerns commenting process – to end of Sept 2013 and new draft to SC in Nov 2013 • Included in agenda for approval during CPM 2014
ePhyto WG1: Issues to consider The structure of the XML message What elements are in the schema What are the names of the elements e.g. Country,issuing party name Coverage of all ISPM12 elements
UN/CEFACT Schema • UN/CEFACT: Centre for Trade Facilitation and e-business • UN/CEFACT standard schema • Covers Sanitary and Phytosanitary issues • This schema was adapted for the phytosanitary context (ISPM 12) • Agreement needed on use of fields
How does it work? • XML language, communication between computer systems • All certificate elements in the XML message • Secure transmission between NPPOs
What is XML • Sheryn to provide
Issues for WG 1(con’t) • Data mapping, e.g. treatments, import permit etc. • Mixed consignments, e.g. containing roses and chrysanthemum cut flowers; mixed products, e.g. bouquets that consist of roses and gypsophila cut flowers. • Data mapping of elements that are specific for a re-export certificate and for a replacement certificate.
ePhyto WG 2: Harmonisation of contents: Codes Why codes? Fullest use of electronic system possible Avoids mismatches by typing errors Unambiguous spelling of names, etc. Language independent Makes digital checks possible More efficient Flexibility to update
Codes • Botanical names – plants: will use EPPO list • Scientific names – pests (EPPO list) • Commodity classes • Treatments • Additional declarations Note: any codes already used, eg ISO codes for country and points of entry, will be used here as well, as per UN/CEFACT
ePhyto WG3 Exchange mechanism Objective is to complete the methods for transfer, security measures and validation for Appendix 1 of ISPM 12 for the exchange of information between countries.
WG1 • Version 1.0 of a global data map for electronic phytosanitary certification • Solutions for consignments consisting of: - a single lot containing only a single product - different lots, each of them containing only a single product • a lot containing different plant species or plant products • UNCEFACT will be approached to request an additional certificate type, for re-export situations • there is no electronic equivalent for alteration, but in these cases a replacement certificate is issued.
XML message • <SPSExchangedDocument> • <Name>Phytosanitary Certificate</ Name> • <ID>KEPHIS/677636/2010</ID> • <IssuerSPSParty> • <Name>Kenya Plant Health Inspectorate Service (KEPHIS)</Name> • <TypeCode>National Plant Protection Organisation</TypeCode> • </IssuerSPSParty> • <RecipientSPSParty> • <Name>Ministry of Economic Affairs, Agriculture and Innovation</Name> • <TypeCode>Ministry</TypeCode> • </RecipientSPSParty> • <RecipientSPSParty> • <Name>Food and Consumer Product Safety Authority (VWA)</Name> • <TypeCode>National Plant Protection Organisation</TypeCode> • </RecipientSPSParty> • <Description>Cut flowers</Description> • <CommonName>Rose</CommonName> • <ScientificName>Rosa spp.</ScientificName> • <NetWeightMeasure unitCode="NA">109,460</NetWeightMeasure> • <ApplicableSPSClassification> • <SystemName>Commodity Class of the product</SystemName> • <ClassName>120: Other living plants: Cutflower and branches with foliage</ClassName> • </ApplicableSPSClassification> • <ApplicableSPSClassification> • <SystemName>Intended end use of the product</SystemName> • <ClassName>Consumption</ClassName>
<Name>Phytosanitary certificate<Name> <ID>EC/NL/04026805<ID> <IssueDateTime>2011-07-20<IssueDate Time> <IssuerSPSparty> <Name>Plant Protection Organization of the Netherlands<Name> <RecipientSPSparty> <Name>APHIS<Name> <Description>Cut flowers<Description> <ScientificName>Rosa spp.<ScientificName>
Electronic equivalent of a certified copy • It is the responsibility of trade to store and provide certified copies for re-export certification. • A certified copy can be: • a decrypted version of the original certificate: contents or the authenticity of the certificate cannot be changed. • a print out of the certificate data which is stamped, dated and countersigned by an NPPO • either in a format similar to phytosanitary certificates • or as a straight print out of a XML message
<?xml version="1.0" encoding="utf-8" ?> • <SPSExchangedDocument> • <Name>Phytosanitary Certificate</ Name> • <ID>KEPHIS/677636/2010</ID> • <TypeCod>851</TypeCode> • <StatusCode>39</StatusCode> • <IssueDateTime>2010-10-30T16:59:06.69</ IssueDateTime> • <SignatorySPSAuthentication> • <ActualDateTime>2010-10-30T16:59:06.69</ActualDateTime> • </SignatorySPSAuthentication> • <IssuerSPSParty> • <Name>Ministry of Agriculture & Rural Development</Name> • <TypeCode>Ministry</TypeCode> • </IssuerSPSParty> • <IssuerSPSParty> • <Name>Kenya Plant Health Inspectorate Service (KEPHIS)</Name> • <TypeCode>National Plant Protection Organisation</TypeCode> • </IssuerSPSParty> • <RecipientSPSParty> • <Name>Ministry of Economic Affairs, Agriculture and Innovation</Name> • <TypeCode>Ministry</TypeCode> • </RecipientSPSParty> • <RecipientSPSParty> • <Name>Food and Consumer Product Safety Authority (VWA)</Name> • <TypeCode>National Plant Protection Organisation</TypeCode> • </RecipientSPSParty> • <SignatorySPSAuthentication> • <IssueSPSLocation> • <ID>KE-NBO</ID> • <Name>Nairobi, Kenya</Name> • </IssueSPSLocation> • <ProviderSPSParty> • <name>Ministry of Agriculture & Rural Development</name> • <rolecode>Ministry</rolecode> • <SpecifiedSPSPerson> • <Name>Dorothy Olubayo</Name>
EPPO codes: a few general principles • For plant pests and pathogens: • 6 letters = 4 (genus) + 2 (species) • B E M I T A • The species Bemisia tabaci: BEMITA • An unspecified species of the genus Bemisia: BEMISP • Genus Bemisia: 1BEMIG • Aleyrodidae Family: 1ALEYF • Sternorrhyncha Suborder: 1STERS • Hemiptera Order: 1HEMIO • Insecta Class: 1INSEC • Animal Kingdom: 1ANIMK Courtesy: EPPO, 2012
EPPO codes: a few general principles (cont.) • For cultivated and wild species (including weeds) • 5 letters = 3 (genus) + 2 (species) • S O L T U • Solanum tuberosum: SOLTU • An unspecified species of Solanum: SOLSS • Genus Solanum: 1SOLG • Solanaceae Family: 1SOLF • Polemoniales Order: 1POMO • Dicotyledons Group: 1DICS • Magnoliophyta Division : 1MAGP • Plant Kingdom: 1PLAK Courtesy: EPPO, 2012
EPPO codes: a few general principles (cont.) 1 biological entity = 1 unique code • Change of preferred scientific name: • Gnorimoschema absoluta = Tuta absoluta • => The code GNORAB remains the same • Newly described species: • Phytophthora pinifolia => PHYTPF is newly created • New subspecies: additional codes • Xylella fastidiosa = XYLEFA • Xylellafastidiosa subsp. multiplex => XYLEFM • Xylella fastidiosa subsp. pauca => XYLEFP • Xylellafastidiosa subsp. sandyi => XYLEFS Courtesy: EPPO, 2012
Specialform on the web to request new codes Courtesy: EPPO, 2012
WG3 (transmission protocol) • Message transmission is between two NPPOs. • To authenticate security SSL certificate • use X509 certificate (provides secure method for recognition of two parties) • it’s part of the envelope and will go with each message, like a fingerprint. • So, no user name or password; no certifying officer • XMLDSIG exists for digital signatures. • Discussion on Web Service Definition Language (WSDL) • Definition: it’s the language you can use to talk to the exporting country, what questions to ask to get the answer you want.
Observations Existing bilateral exchanges are based on Web services Functionality more or less the same Implementation differs (slightly) Standardisation of the implementation will reduce cost of IT solutions Conclusion : Create a best practice WSDL that can be used by newcomers Existing applications can migrate in their own timeline Courtesy: A.J.Moret, 2012
Functionality Find certificates issued by the exporting NPPO Get (Download) certificates from the exporting NPPO Report the status of a downloaded certificate to the exporting NPPO Monitor the status of a certificate Detect if the network and services at the exporting country are available (Hart beat) Courtesy: A.J.Moret, 2012
Exchange mechanism Electronic certificates issued in Exporting country 28
Example of Communication Protocol Courtesy: A.J.Moret, 2012
Communication Diagram Courtesy: A.J.Moret, 2012
Steps in the development of ePhytos (reminder) • Current schedule: • Country comments received until October 20 • Revision of country comments and Appendix 1 at spring 2013 IPPC Standards Committee meeting • Substantial concerns commenting process – to end of Sept 2013 and new draft to SC in Nov 2013 • Included in agenda for approval during CPM 2014
Questions? Suggestions?