1 / 23

BOVEX Electronic Bovine Passport Exchange

BOVEX Electronic Bovine Passport Exchange. Technical presentation Rome/Teramo 11-12 June 2015 Amelio Francesco. The information in this presentation are based on the version 2.37 currently in production. Typical flow. Export MS authority issues a TRACES certificate

jacobg
Download Presentation

BOVEX Electronic Bovine Passport Exchange

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. BOVEXElectronic Bovine Passport Exchange Technical presentation Rome/Teramo 11-12 June 2015 Amelio Francesco The information in this presentation are based on the version 2.37 currently in production

  2. Typical flow • Export • MS authority issues a TRACES certificate • Receives a reference number (i.e. INTRA.FR.2015.00000123) • MS checks if the destination country is participating to BOVEX • Invoking the ListCountries method • MS authority submits the passports calling BOVEX WS (SubmitExchange) • Import (when the Bovines arrive) • Importing MS authority notifies the arrival (RetrievePassports and AcknowledgePassports) • Exporting MS authority gets notified of the acknowledge • currently by e-mail (can be disabled)

  3. Passport format • EARTag • (i.e. FR1234567890) • PassportNumber • (i.e. 278979879) • EARtagOrigin • BirthDate • BirthHolding • Sex (M/F) • BreedColorCode • BreedColorOrigin • MotherEarTag or OldEarTag • List of Movements

  4. Use cases

  5. Web Service methods • Set of operations • ListCountries • SubmitExchange • RecallPassports • RetrievePassports and AcknowledgePassports • QueryCertificates • QueryPassports

  6. ListCountries • Returns the list of participating countries • Should be invoked systematically to decide if a passport should be submitted to BOVEX

  7. SubmitExchange (1) • Notifies the export of animals to BOVEX • Is composed by a list of Passports and more • TracesReferenceNumber • i.e. INTRA.FR.2015.00000123 • ExchangeDate • OriginCountry • OriginHolding • DestinationCountry • List of Passports

  8. SubmitExchange (2)

  9. RecallPassports • Available only to sending country • Recalls a list of submitted passports • Used to • resubmit existing passports • correct mistakes

  10. RetrievePassports (1) • Gets the list of passports related to an import • Available only to importing country • Can be called multiple times for the same passports • Input • TRACES reference number (optional) • retrieves all the passports linked to the TRACES certificate at the moment of submission in BOVEX • and/or • EARTags / PassportNumber • Retrieves listed passports

  11. RetrievePassports (2)

  12. RetrievePassports (output)

  13. AcknowledgePassports • Notifies that • the passports are correctly stored in the importing country's DB • Same syntax as RetrievePassports • Mandatory operation • or done by the system • 10 days after the passports are retrieved • Marks the end the passport's lifecycle • after could eventually be submitted again to BOVEX

  14. QueryCertificates • Retrieves list of TRACES bovine certificates • basic set of information • Search parameters • Traces Reference Number • Origin country • Destination country • Status • Departure date (range) • Declaration date (range) • Last update (range)

  15. QueryCertificates (return) • Traces Reference Number • the reference can be used to retrieve the passports (using the QueryPassports method) • Origin and destination country • Place of origin and place of destination • Name, street, type, approval number • Status (VALID, REPLACED etc.) • Various dates • Departure date • Declaration date • Last update • Replaced certificate • with new TRACES reference

  16. QueryPassports (1) • Retrieves list of Passports related to a TRACES certificate • Input: TRACES reference number • Outputs two lists • EARTags submitted to BOVEX (linked during the submission to the specific TRACES certificate) • EARTags as in the field I.31 of the TRACES certificate

  17. QueryPassports (2) Passports submitted to BOVEX by the exporting country EARTags/Passport numbers declared in the TRACES certificate

  18. Passport lifecycle in BOVEX Retrieve Retrieve(importing country) Submit Passport Retrieved Submitted Automatic cancellation after 30 days Automatic after 10 days Acknowledge (receiving country) Recall(sending country) Cancelled Recalled Acknowledged In the red scope, the passports are de-facto deleted. A new passport with the same EarTag/PassportNumber can be submitted.

  19. How-To (1) • Analyze the business processes • where to collect information (passport, TRACES reference number, movements etc.) • what are the triggers for submission and retrieval • Read the documentation • How-to document • Data dictionary • BOVEX Bundle available on circabc.europa.eu • Section "Health and Food Safety"  TRACES Toolkit  Library  MANUALS  Bovine ID Exchange

  20. How-To (2) • Request credentials for acceptance environment • send a mail to SANTE-BOVEX@ec.europa.eu • Use the sample Soap-UI project to get familiar with the services • Generate the client • if using JAVA, could import and run the JaxWS sample client • otherwise import the WSDL file in your WS client generator tool

  21. Best practices (1) • Run the client automatically using a scheduler • Monitor the system • to make the service reliable and analyse errors • Use ListCountries • The birth is not considered as a movement • The EARTtag value must respect the format defined in the XSD • if a submission or retrieve contains a "dirty" passport, it should be removed from the list

  22. Best practices (2) • How many days to try a SubmitExchange • if for any reason (i.e. technical issue) a submission fails • should be tried for maximum 60 days (to be discussed) and then discarded • How many days to try a RetrievePassports • if a passport is not found • retry for maximum 60 days (to be discussed) after the date of the departure • Changes to the XSD that can break the client • announced 90 days before the deployment • Once your flow is drafted • send it to the EC-SANTE for feedback and comments

  23. Thank you! • References • SANTE-BOVEX@ec.europa.eu • BOVEX bundles on CIRCA-BC • Direct contact • francesco.amelio@ext.ec.europa.eu

More Related