Reporting Formalities Directive

Size: px
Start display at page:

Download "Reporting Formalities Directive"

Transcription

1 Reporting Formalities Directive and Trade facilitation ESPO joint committees meeting Lisbon, 21 March, 2015 Jukka Savo European Commission DG Mobility and Transport Unit D1 Maritime Transport and Logistics

2 The RFD in short RFD is a horizontal facilitation directive does not introduce new reporting obligations but aims to reduce burden deriving from the existing information requirements. Two principal objectives or requirements: 1. Simplification and harmonization of reporting formalities On national level harmonised procedures for ports calls mandatory On EU level obligation to work towards harmonization 2. Electronic reporting through National Single Window

3 The RFD National Single Window National SW establishes nationally harmonized reporting and increases EU level harmonization The platform for sharing of information on national level and through SSN with other EU Member States Tools: Guidelines for implementing National Single Windows Including harmonised Business Rules for the reporting obligations deriving from the EU legal acts, and Data map with about 170 data elements

4 The RFD Evaluation and possible revision Evaluation during 2016, likely followed by an Impact Assessment exercise taking place 2017 Reason: Based on the industry feedback the directive fails to introduce the expected level of harmonization and needs: Binding technical specifications? Better harmonization on national requirements? Also true submit only once by better re-use of data EU Maritime Single Window?

5 emanifest The European Maritime Transport Space without Barriers (recommends to simplify customs procedures for SSS) Blue Belt pilot 2011 (tracking of vessel movements) Reporting Formalities Directive Includes vessel related customs declarations (ENS and FAL 2) Blue Belt Communication 2013 (RSS and emanifest) Implementation of the NSWs harmonised data set w/o cargo information The EU (Enhanced) National Single Window prototype project = > emanifest pilot project

6 emanifest Pilot project Demonstrator project (no legislative support actions, historic data) Strong interest: 17 Member States (maritime and customs) plus industry Activity Scope, objectives and business rules Definition of project specifications Design and development of the prototype Operational testing Evaluation Time March April April May June September October December January - February

7 IMO Single Window Prototype The amended FAL Convention will require public authorities to establish systems for the electronic exchange of information to assist ship clearance processes, no later than three years after adoption. IMO secretariat is proposing three options: 1) develop a prototype by re-using one of the existing systems; 2) develop a completely new prototype based on experience gathered; 3) recommend using one or various existing systems which are made available to the IMO members The Commission together with EMSA has been supporting the work of IMO in this matter (one of the three evaluated systems)

8 Digital Transport and Logistics Forum (DTLF) edocument subgroup Objective 1: To ensure the acceptance of electronic transport documents by national authorities. Objective 2: To reach better harmonisation of transport documents across modes. Objective 3: To widen the analysis to other transport-related documents (e.g. on vehicles or drivers). Corridor cargo flow optimisation subgroup Objective of the subgroup will be to facilitate exchange of information along transport corridors in order to increase efficiency of cargo flows. - As-is Survey going on on Scan-Med corridor. After the survey concrete business cases will be identified. Analysis of these business cases will lead to recommendations on potential measures to improve and optimise cargo flows along the corridors as well as possible pilot projects.

9 Thank you! More information: