Rebecca LeeNAPPO Technical DirectorePhyto Steering Committee memberNovember, 2012

www.nappo.org

Ottawa, Canada

Electronic certification- status of IPPC ePhyto

developments

Steps in the development of ePhytos

• Netherlands (2007), Ottawa (2009), Korea (2011), Paris (2012) meetings•Steering committee in place•Working Groups:

1 - XML schema2 - Code lists3 - Communication protocols

•Brazil training workshop, November, 2012

Steps in the development of ePhytos (cont.)

• July 1 – October 20, 2012IPPC 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 elementse.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.

ePhyto EWG Achievements

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.

• <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>

XML message

<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>

Example of XML SchemaISPM 12 Element

E-Phyto Schema Element Paper Example Schema example

Certificate name/model

SPSExchangedDocument_TypeCode Export format <SPSExchangedDocument> <TypeCode>851</TypeCode>

SPSExchangedDocument_Name Phytosanitary Certificate

<SPSExchangedDocument> <Name>Phytosanitary Certificate</Name>

Unique identification number

SPSExchangedDocument_ID 123456 <SPSExchangedDocument> <ID>123456</ID>

Name of the country issuing

SPSConsignment_ExportSPSCountry_Name China <SPSConsignment> <ExportSPSCountry> <Name>China</Name>

SPSConsignment_ExportSPSCountry_ID N/A <SPSConsignment> <ExportSPSCountry> <ID>CN</ID>

Name of the state / province etc. within a country

SPSConsignment_ExportSPSCountry_ SubordinateSPSCountrySubDivision_Name

Jiangxi Province <SPSConsignment> <ExportSPSCountry> <SubordinateSPSCountrySubDivision> <Name>Jiangxi</Name>

SPSConsignment_ExportSPSCountry_ SubordinateSPSCountrySubDivision_ID

N/A <SPSConsignment> <ExportSPSCountry> <SubordinateSPSCountrySubDivision> <ID>CN-36</ID>

Name of the NPPO

SPSExchangedDocument_IssuerSPSPartyName General Administration of Quality Supervision, Inspection and Quarantine

<SPSExchangedDocument> <IssuerSPSParty> <Name>General Administration of Quality Supervision, Inspection and Quarantine</Name>

SPSExchangedDocument_IssuerSPSPartyID N/A <SPSExchangedDocument> <IssuerSPSParty> <ID>AQSIQ</ID>

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

<?namespace:rsm=urn:un:unece:uncefact:data:standard:SPSCertificate:4?> <?namespace:ram=urn:un:unece:uncefact:data:standard:ReusableAggregateBusinessInformationEntity:8?>

PRINT of an electronic phytosanitary certificate This print is a certified copy of the original phytosanitary certificate according to IPSM 12 when validated (stamped, dated and countersigned) by the NPPO indicating it is a true representative of the original phytosanitary certificate Document type Type PH Cert E <Phytosanitary certificate for export> Type PH Cert E Type PH Cert R <Phytosanitary certificate for re-export> Type PH Cert R No. Ref no PH cert Plant Protection Organization of NPPO Export - NPPO Export short Type PH Cert E < ExportCountry Name - ExportCountry Code > Type PH Cert E Type PH Cert R < ReExportCountry Name - ReExportCountry Code > Type PH Cert R TO: Plant Protection Organization(s) of NPPO Import - NPPO Import short Type PH Cert I < ExportCountry Name - ImportCountry Code > Type PH Cert I I. Description of Consignment Name and address of exporter: Exporter name

Exporter line one Exporter line two Exporter city name Exporter country

Declared name and address of consignee: Importer name Importer line one Importer line two Importer city name Importer country

Declared means of conveyance: Conveyance Declared point of entry: PoE country name - PoE ISO-code

PoE city <?for-each: ram:IncludedSPSTradeLineItem?> Reference no of trade line item: Ref no trade line item Number and description of packages: QuantityType of package <XJ> Distinguishing marks: Marks Place of origin: Origin country name - Origin ISO-code Name of produce and quantity declared: Common name: Common name

Commodity type: Commodity type Quantity: Quantity units pieces / gram / kilogram

Botanical name of plants: Botanical name <?end for-each?> Type PH Cert E < This is to certify that the plants, plant products or other regulated articles described herein have been inspected and/or tested according to appropriate official procedures and are considered to be free from the quarantine pests specified by the importing contracting party and to conform with the current phytosanitary requirements of the importing contracting party, including those for regulated nonquarantine pests. They are deemed to be practically free from other pests.*

• <?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>

WG2 – example of code lists

EPPO codes: a few general principles

For plant pests and pathogens: For plant pests and pathogens: 6 letters = 4 (genus) + 2 (species)6 letters = 4 (genus) + 2 (species)

B E M I T AB E M I T A

The species Bemisia tabaci: BEMITA

An unspecified species of the genus Bemisia: BEMISPSP

Genus Bemisia: 11BEMIGG

Aleyrodidae Family: 11ALEYFF

Sternorrhyncha Suborder: 11STERSS

Hemiptera Order: 11HEMIOO

Insecta Class: 11INSECC

Animal Kingdom: 11ANIMKKCourtesy: EPPO, 2012

For cultivated and wild species (including weeds)For cultivated and wild species (including weeds)

5 letters = 3 (genus) + 2 (species)5 letters = 3 (genus) + 2 (species)

S O L T US O L T USolanum tuberosum: SOLTU

An unspecified species of Solanum: SOLSSSS

Genus Solanum: 11SOLGG

Solanaceae Family: 11SOLFF

Polemoniales Order: 11POMOO

Dicotyledons Group: 11DICSS

Magnoliophyta Division : 11MAGPP

Plant Kingdom: 11PLAKK

EPPO codes: a few general principles (cont.)

Courtesy: EPPO, 2012

1 biological entity = 1 unique code1 biological entity = 1 unique code

Change of preferred scientific name:Change of preferred scientific name:Gnorimoschema absoluta = Tuta absoluta => The code GNORABGNORAB remains the same

Newly described species:Newly described species:Phytophthora pinifolia => PHYTPFPHYTPF is newly created

New subspecies: additional codesNew subspecies: additional codesXylella fastidiosa = XYLEFAXylella fastidiosa subsp. multiplex => XYLEFMXYLEFMXylella fastidiosa subsp. pauca => XYLEFPXYLEFPXylella fastidiosa subsp. sandyi => XYLEFSXYLEFS

EPPO codes: a few general principles (cont.)

Courtesy: EPPO, 2012

Special form 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

28

Electronic certificates issued in Exporting country

Exchange mechanism

Electronic certificates received in Importing country

Example of Communication Protocol

Action Service Description

2.1 Find a list of certificates Find_certificate Put the request to the NECS to return all certificate numbers that meet the input criteria. Immediately after this Request the NECS returns the list of numbers

2.2 Download a list of certificates get_certificate Put the request to the NECS to return all certificates s that meet the input criteria. Immediately after this request the NECS returns all the certificates

2.3 Change the status of a certificate

Put_certificate_status Put the request to the NECS to change the status of a list of certificatesto the specified value. Immediately after this request the NECS returns the process result for every individual certificate (Succes or Failed with reason)

2.4 Show the status of a certificate Show_certificate_status Put the request to the NECS to show the status of a list of. Immediately after this request the NECS returns the status for every individual certificate (Succes or Failed with reason)

2.5 Show status of the NECA Hart_beat Put the request to the NECS to confirm that the NECS and the network between the NECS and NICS are operational. Immediately after this Request the NECS returns the message OK

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?