Health & Consumers DG SANCO Unit A.4 Information systems TRACES New Technologies State of play Nov 18 2011 Nov 18, 2011 TRACES Workshop, Brussels

TRACES Workshop, Brussels Background TRACES is reaching a respectable age for an IT system TRACES scope foreseen to increase in the future Some aspects in TRACES are currently not optimal, or do not properly reflect reality: Organisations management (duplicates…) Transporters and vehicles Animal welfare module (GIS etc.) … TRACES should be designed to better match the business processes of All stakeholders TRACES is still based on J2EE, cutting edge in 2003… Conclusions: TRACES will need a fundamental redesign and technological update, and better start earlier than later Nov 18, 2011 TRACES Workshop, Brussels

TRACES Workshop, Brussels Strategy Gradually decrease evolution of current TRACES system In parallel, ramp up work on 2nd generation TRACES Gather requirements from stakeholders Investigate and select candidate technologies Start the technical design work Gradually involve the developers, shifting from TRACES to new TRACES - “TNT” Nov 18, 2011 TRACES Workshop, Brussels

Gathering requirements A number of MS visited: BE, DE, NL, DK… Meeting stakeholders at various levels (BIP, CCA, MSADM, LVU, EO, transitair) TNT questionnaire as basis for discussions In addition, internal “technical audit” of current TRACES system Nov 18, 2011 TRACES Workshop, Brussels

Key Points 1: User Experience Multi-platform, wide range browser support Current help feature of very limited use  new web technologies allow for context-based help and integrated user manual TRACES users should not have to re-learn too much  TRACES is, and will still be, based on legislation, so in this respect it can not fundamentally change Ergonomic aspects: Avoid excessive mouse usage  keyboard shortcuts Easy overview: Screens adapted per user profile Overview pane / certificate “preview” Nov 18, 2011 TRACES Workshop, Brussels

Key Points 2: General usability concerns LVU / BIP: wants to better use TRACES as planning tool  better search facilities CCA / RCA: wants to better use TRACES as a traceability tool Customised views for “peripheral users”: Roadside police inspection Customs … Nov 18, 2011 TRACES Workshop, Brussels

Key Points 3: Users and Organisations Take the Admin – User concept to multiple levels Flexible role assignment to same user Avoid duplicate organisations Still allow some flexibility: “Fuzzy search” (“Did you mean…” feedback) Allow for city name “aliases” (Cologne = Köln) … Transporters decoupled from vehicles Nov 18, 2011 TRACES Workshop, Brussels

Key Points 4: Interoperability – Current Situation Some systems are in place and operational However, double keying / parallel use is not eliminated: Users of national systems still need to access TRACES for some consignments Certain functionalities not available or in scope of national system (e.g. RASFF) Non-exploitation of labour-saving TRACES features (e.g. clone IMPORT to CVED) TRACES support burden grows linearly with number of connected national systems  current approach not sustainable in the long term Nov 18, 2011 TRACES Workshop, Brussels

Key Points 5: Interoperability - Solution Approach TRACES becomes the orchestrating system: TRACES always early part of the chain Avoid / reduce double keying to local systems: Allow national system to synchronise the data  Provide flexible, modular single window facilities (not only for customs, but for any purposes)  Base on international standards as much as possible Third country integration: IMPORT and EXPORT certificates based on UN/CEFACT Nov 18, 2011 TRACES Workshop, Brussels

Key points 6: Peripheral systems, annexed data AWF module: incorporate an external, professional GIS server Foresee closer integration to EC systems (RASFF, ADNS, …) Devise flexible way of annexing ancillary data, for example: Full 1/2005 journey log IUU certificate for fish catches Airway bill information … Nov 18, 2011 TRACES Workshop, Brussels

Thank you for your attention Nov 18, 2011 TRACES Workshop, Brussels