DTLF Plenary meeting 19 June 2019 Brussels Mobility and - - PowerPoint PPT Presentation

Mobility and Transport

Digital Transport and Logistics Forum

DTLF

• Plenary meeting
• 19 June 2019
• Brussels

Mobility and Transport

Agenda

MOVE

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

Mobility and Transport

DTLF II – SG1 Paperless Transport Proposal for Workplan June 2019

Mobility and Transport

DTLF SG1 by the numbers

Source: EC Online Survey (Feb 2019) In Subgroup 1 only Core SG1 members who have committed to dedicate their time

to SG1 exclusively.

44 39

In both Subgroups Over half of confirmed SG1 members are also willing to engage in SG2 activities. Subgroup 1 members Overall number of DTLF members willing to engage in SG1 activities.

83

MOVE

Mobility and Transport

Progress update

• 3+1 Subgroup meetings

 7 March 2019  11 April 2019 + working meeting  18 June 2019

• Achievements to date:

 Definition of the SG1 working areas (incl. eFTI proposal, documents for vehicles and personnel)  Drafting of the SG1 mandate and workplan

MOVE

Mobility and Transport

Areas of work endorsed at SG1 meeting

DTLF SG1 – Paperless transport

Goods Vehicles & Personnel

• eFTI Regulation

 Data modelling aspects  Functional aspects  Technical aspects  Platform and service provider requirements  Certification  Other aspects

• Road

 Access to data for regulatory purposes

• Air, Rail, Maritime, ILW

 No specific work – SPOCs designated for updates on developments MOVE

Mobility and Transport

eFTI Regulation - objectives

Main objectives:

• (1) ensure the establishment, in all EU Member States, of the
• bligation of acceptance of electronic freight transport

documents/information by all relevant public authorities;

• (2) ensure that the authorities implement the obligation of

acceptance in a uniform manner;

• (3) ensure the interoperability of the IT systems and

solutions used for the electronic exchange of freight transport information, and in particular for business-to-administration (B2A) regulatory information communication

Main benefits: If this is not dealt with on EU level,

• every single national/local

authority will take its own digitalisation initiative

• this would certainly lead to more

costs, further fragmentation and

• not necessarily trade

(facilitation) minded solutions 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 1) Data modelling aspects 2) Functional aspects 3) Technical aspects 4) Platform and service provider requirements 5) Certification 6) Other aspects 7) Where relevant; Transport means and personnel Characteristics of the

• rganisation
• Matrix organisation
• Phased approach
• Task-based with deadlines
• Input and feedback from all

DTLF Members is required and wanted

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,

existing standards and private sector models :

• List the legally required data, covered by the

annex as a starting point (if available). In other words; what are the minimum requirements

• Then see how this would match/fit with the

existing models like WCO and/or UN-CEFACT, but

• f course also the EUCDM
• Lastly, we can compare it to private sector

models/standards

• II. Analysis of the data
• elements. Find general overlap

and differences in:

• data elements (both main set and

metadata)

• definitions
• characteristics
• code lists
• cardinality and occurrence

DW

Mobility and Transport

Tasks 1 – Data model (2)

• III. Converge
• Define structure of the data model
• Determine quick wins/losses
• Determine where the most significant

differences are and what the best way forward would be

• IV. Finalisation
• Achieve consensus approval within DTLF
• Report results to DG Move
• Provide advice on next steps to be taken
• Provide advice on governance of the model
• cardinality and occurrence

DW

Mobility and Transport

Tasks 2 – Functional aspects (1)

• I. Analysis/Business Process

Modelling

• Establish per transport mode and

legislative area whether push or pull method is required

• Based on outcome of a), define high

level process overviews (happy flow)

• Define lower level process models
• Highlight specific challenges/choices.

Questions

• What does ‘making available’ mean?
• How/When will authorities check data?
• What happens if during a check information

turns out to be false or incomplete?

• In case there is feedback on a check, will this

be exchanged through the platforms?

• Will authorities “just” have access to a single

data set for a single transport operation or can they freely query databases?

DW

Mobility and Transport

Tasks 2 – Functional aspects (2)

• II. Converge
• Do comparison of BPMs per transport

mode and find overlaps and differences

• Align processes where possible
• Address challenges/formulate advice
• n possible choices
• III. Finalisation
• Establish business process documentation

(including descriptions)

• Review in line with data/technical and

governance

• Achieve consensus approval within DTLF
• Report results to DG Move
• Provide advice on next steps to be taken

DW

Mobility and Transport

Tasks 3 – Technical aspects

• Depends on functional aspects
• Certain elements will be required in

any case

• Abundance of possible solutions
• Can already be analysed (SWOT)
• Existing solutions
• Take into account platform & service

provider requirements

Technical aspects to be considered

• Preferred interfacing options
• B2A and where relevant A2B & A2A, depending on

push or pull

• S2S and U2S
• (Where relevant) Database requirements
• Authentication, identification (related to platform

and service provider requirements)

• Confidentiality, integrity and availability (related to

platform and service provider requirements)

• Capacity requirements

DW

Mobility and Transport

Tasks 4 – Platform & SP requirements

Different elements

• Closely related to functional & technical aspects
• How regulatory transport information is made

available, in what cases, and by whom this can be accessed

• Correspondance to the common eFTI data set and

subsets

• Data safety & security (GDPR, commercial etc)

Subtasks deliverables

• Authentication & Identification
• Confidentiality, integrity and

availability

• Access rules, roles & governance

DW

Mobility and Transport

Tasks 5 – Certification

• 1. Certification requirements
• Harmonised, Specific requirements
• Known in advance
• Remain able to adapt
• Respect different actors and activities

Balance required

• sufficient clarity and harmonisation
• sufficient flexibility and ability to adapt to new

business concepts and technology

• 2. Certification procedure
• Same balance required
• Appeal procedure
• When to re-assess
• 3. Providing proof of certification
• How to provide proof
• In what cases can proof be required
• What to do if proof is refused

DW

Mobility and Transport

Tasks 6 – Other aspects

Implementation strategy & planning

• Deadlines set by legislation
• Will be discussion during trialogue
• Nonetheless, realistic and acceptable planning

required Communication, training and helpdesk facilities

• Common understanding of the purpose,

functioning, requirements and benefits is crucial

• Where to go with questions

Testing facilities

• Not just for (re)assessment
• Authorities and operators and

service providers must be able to test

• End-to-End
• Joint controlled environment

DW

Mobility and Transport

Planning & organisation of the work (1)

Phases

• Phase 0 - Q3 2019
• Phase 1 – Q4 2019
• Phase 2 – Q1 2020
• Phase 3 – Q2 – Q3 2020
• Phase 4 – Q4 2020

To be determined

• Agreement over organisation work plan
• Agreement over planning work plan
• Establishment of teams
• Appointment Team leads & co-team leads

DW

Mobility and Transport

Nr. Type of Activity

M1 M2 M3 M4 M5 M6 M7 M8 M9 M10 M11 M12 M13 M14 M15 M16 M17 M18

0. Coregroup 0.1 Finalise work plan and establishing of teams and team leads 1. Data modelling aspects 1.1 Listing of required and relevant data elements 1.2 Analysis of the data elements 1.3 Converging of analysis into conclusions 1.4 Finalisation & reporting 2. Functional aspects 2.1 Analysis / Business process modelling (per transport mode) 2.2 Comparison, alignment of processes & identification of issues 2.3 Finalisation & reporting 3. Technical aspects 3.1 Initial analysis on possible (existing) elements for interfaces 3.2 Next steps determined by functional aspects and partially data modelling 3.3 Finalisation and reporting 4. Platfrom requirements 4.1 Framework access rules, access governance, roles and delegation 4.2 Authentication, identification 4.3 Confidentiality, integrity and availability (including fall-back procedures) 4.4 Finalisation & reporting 5 Certification 5.1. Certification requirements 5.1. Certification procedure 5.1. Providing proof of certification 5.1. Finalisation & reporting 6 Implementation 6.1 Implementation strategy / planning 6.2 Testing and provision of testing facilities (where relevant) 6.3 Communication, training and helpdesk (where relevant)

Phase 4 – Q4 2020

DTLF - Subgroup 1- Paperless transport

Phase 0 - Q3 2019 Phase 1 – Q4 2019 Phase 2 – Q1 2020 Phase 3 – Q2 & Q3 2020

DW

Mobility and Transport

Next steps

• Finalisation of teams (SG1 members to confirm their involvement for

each task through an EU Survey.  The form will remain online until 28th June  https://ec.europa.eu/eusurvey/runner/DTLFSG1Teams

• Finalisation of the SG1 work plan following endorsement of main outline
• Launch of Phase 1 work (cf. Gantt chart)
• Next SG1 Meeting: September 2019

MOVE

Mobility and Transport

DTLF SG2 Digital Corridor Information Systems

• DTLF Plenary meeting
• 19 June 2019
• Brussels

Mobility and Transport

DTLF Subgroup 2:

• Objectives -
• DTLF SG2 aims to create a common understanding and solutions for data sharing in

supply and logistics through defining the parameters for establishing a federated network

• f platforms as a basis for innovation and cost reduction, and contribute to societal

challenges like safety, security, and sustainability.

• In the second mandate, DTLF SG2 will substantiate the concept in particular:
• through developing specifications for technology independent services, that support organisations in

sharing data without prior agreements, i.e. plug and play, and the protocols for platform interoperability, and

• through defining the required governance structure.
• The result will not restrict competition, should ease on-boarding of users to platforms,

enlarge the market for data sharing, and is expected to stimulate innovation similar to the introduction of the Internet

MOVE

Mobility and Transport

Use case presentation

Joost Naessens European Chemical Industry Council - CEFIC

MOVE

Mobility and Transport

Progress report (1)

DTLF plenary meeting: January 2019

• Development and implementation of digital corridor information systems (a

concept for a federated network of platforms) as one of the two main topics to be dealt with by DTLF II

• A dedicated Subgroup (SG2) to address this topic
• The DTLF Subgroups to be split into teams, if appropriate
• Definition of a workplan for Subgroups with clearly defined tasks and

deliverables

MOVE

Mobility and Transport

Progress report (2)

DTLF SG2 in the EC Online Survey: February 2019

In Subgroup 2 only Core SG2 members who have committed to dedicate their time to SG2 exclusively.

44 36

In both Subgroups Over half of confirmed SG2 members are also willing to engage in SG1 activities. Subgroup 2 members Overall number of DTLF members willing to engage in SG2 activities.

80

MOVE

Mobility and Transport

Progress report (3)

DTLF SG2 meeting: April 2019

• Working modalities, inter alia:
• Structure: teams, team leaders, rapporteur
• Project type approach: activities, time schedule, milestones, deliverables
• Communication: meetings, e-mails, teleconferences, sharepoint, website
• Coordination between teams: SG2 plenary, core team
• General oversight and coordination: DG MOVE

MOVE

Mobility and Transport

Progress report (4)

DTLF SG2 meeting: April 2019

• Building blocks of the federated platform

MOVE

Mobility and Transport

Progress report (5)

DTLF SG2 meeting: April 2019

• Organisation of the DTLF SG2

DTLF SG2

Plug & Play (P&P) Technology Independent Services (TIS) Federation of Platforms (FED) Trusted, Safe & Secure (GOV)

Rapporteur: RISE

15 members 19 members 16 members 16 members

MOVE

Mobility and Transport

Progress report (6)

DTLF SG2 meeting: April 2019

• Splitting into teams according to building blocks
• Interactive discussions on:
• Needs, Approaches, Benefits and Missed Opportunities
• Strategic Roadmap (objectives, deliverables, tasks, milestones, challenges, resources)
• Input for the work programme of the DTLF SG2

MOVE

Mobility and Transport

Objective for this meeting

• Discussion and possible endorsement of the draft workprogramme

(version 29052019)

• Mandate for continuing the work based on the draft workprogramme

MOVE

Mobility and Transport

Recap: Digital corridor information systems concept

Creation of a Federative Network of Platforms for data sharing with two main features:

• one single entry point for organisations

(business and authorities)

• platform interoperability

MOVE

Design principles:

• Register and connect once
• Interoperability by default
• Open infrastructure with a solution of

choice

• Trust and security
• Scope: B2A and B2B
• Transparency and level playing field
• Re-use of existing standards
• Technology independent
• No centralised solution

Mobility and Transport

Federative Network of Platforms

• mapping to the Building Blocks -

C D

• ffice

• ffice

Platform Platform

Platform interoperability Platform services

• ffice

• ffice

Platform

Platform interoperability Platform services

• ffice

• ffice

Platform

Platform services

Platform services

A B

P&P P&P FED FED FED

P&P TIS FED

ML TIS TIS

Mobility and Transport

From building blocks to work plan

ML

Business process interoperability Guidelines, behaviour and governance Federated Platform functionality Architecture, technology and platforms

Mobility and Transport

Tasks Building Block 1

– Plug & Play -

Objective: registration procedure and data sharing without specific implementation guides

• Business service specification – identification and (data requirements) specification of value

propositions of enterprises

• User stories – Registration of business services for Plug & Play
• Specification of Registration Services, including semantics
• Data requirements formulation – how to create myOntology
• Access Point Specification – integration with back office IT
• Implementation Guidelines – how to apply and implement the solution with your business partners and

in your organisation, compliant with regulations

ML

Mobility and Transport

Tasks Building Block 2

– Technology Independent Services -

Objective: basic principles for digital interoperability between actors

• Business and authority interoperability principles – basic design principles and concepts
• Business scenario’s – examples of use cases that have to be supported
• Business transaction choreography – specification of sequencing of data sharing and data

requirements for interactions between any two enterprises

• Semantic model – semantics of all data that can be shared in supply and logistics, utilising

knowledge gained by existing standardization bodies

• Platform Services – transforming the choreography into Platform Services for end-users
• Standards – support/inclusion of standards by semantic model

ML

Mobility and Transport

Tasks Building Block 3

• Federation, network of platforms -

Objective: interoperability between different platforms (technical and functional protocols), technological neutrality

• Architecture of Federative Network of Platforms – components, services, and interfaces. Different

technological solutions might fit different parts of the choreography (push/pull, pub/sub, …)

• Technical Protocols – how to technically interconnect platforms, p2p solutions and p2p solution with a

platform

• Functional Interoperability – functional data sharing between any two platforms or p2p solutions
• Payment, clearing and settlement – how to deal with business models of commercial solutions
• Configuration components – (high level) specification of components and their interfaces for distributed

development of Technology Independent Services and support of Plug & Play

ML

Mobility and Transport

Tasks Building Block 4

• Trusted, safe, and secure -

Objective: a neutral governance structure

• Analysis of best practices in other sectors – features of similar environments (e.g. Internet)
• Identify stakeholder groups and list their main drivers or barriers for adoption of the solution
• Governance structure and terms of reference, based on analysis of the previous tasks
• Procedures for distributed development and maintenance
• Identification and authentication – relevant mechanisms required to prevent unauthorised use
• Security requirements – additional rules for components and interfaces (see also eFTI)
• Adoption and implementation instruments

ML

Mobility and Transport

Feedback from the DTLF SG2 meeting Endorsement of the draft SG2 work programme

MOVE

Mobility and Transport

Open discussion

MOVE

Mobility and Transport

Discussion points

• Is the work programme structured correctly?
• Are the objectives specific enough and attainable?
• Are the /tasks/deliverables/milestones complete?
• Is the planning adequate and realistic?
• Are the interdependencies properly identified?
• Are the priorities for interdependent tasks set adequately?

MOVE

Mobility and Transport

Next steps

MOVE

• Comments from the SG2 and plenary meetings
• The SG2 teams
• Input from CEF projects
• Second version of the workprogramme

Mobility and Transport

DTLF II Interdependencies between DTLF SG1 and SG2

Mobility and Transport

Objectives & characteristics of S1 & SG2

SG1 – to de preparatory work for and to assist & advice on eFTI regulation & implementation

• Main scope: B2G/G2B, exchange of regulatory

information on goods,

• Scope and deadlines defined by legislation & Mandatory

for authorities, Optional for private sector

• Specifications for data model, common procedures &

specs for access, requirements & certification SG2 – to develop specifications and a governance structure for a Federative Network of Platforms

• Main scope: B2B/B2G/G2B, including: infrastructure

management, traffic management, cross border management, trade facilitation, risk management, marketplace logistics services, booking, ordering, tracing and tracking, supply chain visibility

• At the moment not subject to any legislative initiative,

no specific deadline

• Specifications for technology independent services,

data models, access, registration, protocols for platform interoperability, open standards, governance

Mobility and Transport

EFTI adoption and implementation timeline

17 May 2018

• Proposal

adopted by Commission

June 2018

• Start of

consideration by European Parliament and Council

29 Jan 2019

• First reading

adopted by European Parliament

6 June 2019

• Adoption of

General Approach by Council

Sept/Oct 2019

• Start of EP-

Council discussions in trialogue format

End 2019/Start 2020

• Final text

adoption by EP & Council

Q1 2020 – Q4 2023

• Preparation &

adoption of technical specifications

Q1 2024/2026 (tbc)

• Entry into

force

Application (Art. 17): 4 years – allow adoption of the implementing and delegated acts

MOVE

Mobility and Transport

Possible elements that require alignment

• Timing?
• Data models/sets?
• Access rules/registration?
• Semantic models?
• ……?

Mobility and Transport

Thank you for your attention