Digital Transport and Logistics Forum DTLF Plenary meeting • 19 June 2019 • Brussels • Mobility and Transport
Agenda INTRODUCTION 10.00 – 10.15 Welcome address and introductory remarks DTLF II WORK PROGRAMME (1) 10.15 – 12.30 DTLF Subgroup 1 (SG 1) Work Programme LUNCH BREAK DTLF II WORK PROGRAMME (2) 13.30 – 15.45 DTLF Subgroup 2 (SG 2) Work Programme COFFEE BREAK DTLF II HORIZONTAL MATTERS 16.00 – 17.00 DTLF organisation and operation 17.00 – 17.15 AOB 17.15 End of the meeting MOVE Mobility and Transport
DTLF II – SG1 Paperless Transport Proposal for Workplan June 2019 Mobility and Transport
DTLF SG1 by the numbers 83 39 Subgroup 1 members Overall number of In Subgroup 1 only DTLF members willing Core SG1 members to engage in SG1 who have committed activities. 44 to dedicate their time to SG1 exclusively. In both Subgroups Over half of confirmed SG1 members are also willing to engage in SG2 activities. Source: EC Online Survey (Feb 2019) MOVE Mobility and Transport
Progress update • 3+1 Subgroup meetings • Achievements to date: 7 March 2019 Definition of the SG1 working areas (incl. eFTI proposal, documents for vehicles and 11 April 2019 + personnel) working meeting Drafting of the SG1 mandate and 18 June 2019 workplan MOVE Mobility and Transport
Areas of work endorsed at SG1 meeting DTLF SG1 – Paperless transport Goods Vehicles & Personnel eFTI Regulation • Road • Data modelling aspects Access to data for regulatory Functional aspects purposes Technical aspects Platform and service provider Air, Rail, Maritime, ILW • requirements No specific work – SPOCs Certification designated for updates on Other aspects developments MOVE Mobility and Transport
eFTI Regulation - objectives Main objectives: Main benefits: If this is not dealt with on EU level, (1) ensure the establishment, in all EU Member States, of the • obligation of acceptance of electronic freight transport every single national/local • documents/information by all relevant public authorities ; authority will take its own digitalisation initiative (2) ensure that the authorities implement the obligation of • acceptance in a uniform manner ; this would certainly lead to more • costs, further fragmentation and (3) ensure the interoperability of the IT systems and • solutions used for the electronic exchange of freight transport not necessarily trade • information, and in particular for business-to-administration (B2A) (facilitation) minded solutions regulatory information communication DW Mobility and Transport
eFTI Regulation – principles Concerns B2A exchange of data for goods , possibly at a later stage vehicles and drivers, B2B is out of scope but can be taken into account Harmonised transport data model (similar to customs), based on international standards Harmonised/standardised interfaces (access points) “ Pull mechanism ” will be standard for exchange For that purpose IT used has to be certified , but existing systems can be used Certified systems will be called eFTI Platforms (can still be anything) Technological neutrality – important to prevent unnecessary IT changes (caused by hypes). Blockchain for example can be used, but is not mentioned DW Mobility and Transport
What DTLF SG1 is not doing Writing legislation - The DTLF is an expert group with a mandate to assist & advise COM. Nonetheless important opportunity to “steer” it in the right direction – we should use it Building, prescribing or endorsing systems for data exchange - It is up to every public and private sector party itself to find its most optimal solution – this includes the costs related to it Business to business exchange of information - Where we can find synergies or win-win results we should of course, but the main focus/scope is on B2A Re-inventing transport & logistics - There is always something to improve and it can be an entertaining topic for discussion, but it’s not a mandate for DTLF SG1 Creating world peace, saving the dolphins, curing cancer or stop hunger - It is of course good to achieve those things, but I am not sure we can achieve it through the DTLF SG1. Therefore we should not spend much time on it and focus on tangible result and the SG1 scope. DW Mobility and Transport
SG1 tasks relating to eFTI • common eFTI data set and subsets in relation to the respective regulatory information requirements, including corresponding definitions for each data element included in the common data set and subsets (article 7a) • common procedures and detailed rules, including common technical specifications, for competent authorities' access to eFTI platforms , including procedures for processing of regulatory information made available electronically by the economic operators concerned (article 7b) • Functional requirements for eFTI Platforms (article 8) and requirements for eFTI service providers (article 9) • Certification of eFTI Platforms (article 11) and eFTI Service Providers (article 12). DW Mobility and Transport
SG1 tasks relating to eFTI Grouping of activities Characteristics of the organisation 1) Data modelling aspects • Matrix organisation 2) Functional aspects • Phased approach 3) Technical aspects • Task-based with deadlines 4) Platform and service provider requirements • Input and feedback from all 5) Certification DTLF Members is required and wanted 6) Other aspects 7) Where relevant; Transport means and personnel DW Mobility and Transport
Means of transport and personnel • SG1’s work would not include a focus on documents related to the means of transport and personnel in the inland waterways , maritime and railway sector • Relating to road transport , it was concluded that access to data is lacking for certain regulatory purposes and that the DTLF could further explore what are the needs for work in this area. ITD agreed to propose a draft work plan • Relating to air transport , it was agreed that IATA and Airlines for Europe will explore the existing needs at a later stage. This will be included in the workplan of SG1 • Further, it was agreed that for each mode where no proactive work would be carried out by the DTLF, a single point of contact (SPOC) within the subgroup members would be appointed and in charge of updating the subgroup and Forum with any relevant developments in the given transport mode DW Mobility and Transport
Tasks 1 – Data model (1) I. Analysis (listing of) of the required data, II. Analysis of the data existing standards and private sector models : elements. Find general overlap and differences in: • List the legally required data, covered by the annex as a starting point (if available). In other • data elements (both main set and words; what are the minimum requirements metadata) • Then see how this would match/fit with the • definitions existing models like WCO and/or UN-CEFACT, but of course also the EUCDM • characteristics • Lastly, we can compare it to private sector • code lists models/standards • cardinality and occurrence DW Mobility and Transport
Tasks 1 – Data model (2) III. Converge IV. Finalisation • Define structure of the data model • Achieve consensus approval within DTLF • Determine quick wins/losses • Report results to DG Move • Determine where the most significant • Provide advice on next steps to be taken differences are and what the best • Provide advice on governance of the model way forward would be • cardinality and occurrence DW Mobility and Transport
Tasks 2 – Functional aspects (1) I. Analysis/Business Process Questions Modelling • What does ‘making available’ mean? • Establish per transport mode and • How/When will authorities check data? legislative area whether push or pull method is required • What happens if during a check information turns out to be false or incomplete? • Based on outcome of a), define high level process overviews (happy flow) • In case there is feedback on a check, will this be exchanged through the platforms? • Define lower level process models • Will authorities “just” have access to a single • Highlight specific challenges/choices. data set for a single transport operation or can they freely query databases? DW Mobility and Transport
Tasks 2 – Functional aspects (2) II. Converge III. Finalisation • Do comparison of BPMs per transport • Establish business process documentation mode and find overlaps and (including descriptions) differences • Review in line with data/technical and • Align processes where possible governance • Address challenges/formulate advice • Achieve consensus approval within DTLF on possible choices • Report results to DG Move • Provide advice on next steps to be taken DW Mobility and Transport
Recommend
More recommend
