DTLF Digital Transport and Logistics Forum - Plenary meeting 19 June 2019 Brussels - Clecat

DTLF Digital Transport and Logistics Forum - Plenary meeting 19 June 2019 Brussels - Clecat
Digital Transport and Logistics Forum

            •       Plenary meeting
                •    19 June 2019
                     •   Brussels
                          Mobility and
DTLF Digital Transport and Logistics Forum - Plenary meeting 19 June 2019 Brussels - Clecat
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          MOVE
 Paperless Transport
Proposal for Workplan
     June 2019

         Mobility and
DTLF SG1 by the numbers

83                                            39
        Subgroup 1 members
        Overall number of
        DTLF members willing                               In Subgroup 1 only
        to engage in SG1                                   Core SG1 members
        activities.                                        who have committed

                                                           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)

                               Mobility and                                          MOVE
Progress update

  • 3+1 Subgroup meetings              • Achievements to date:

       7 March 2019                        Definition of the SG1 working
                                             areas (incl. eFTI proposal,
       11 April 2019 +                      documents for vehicles and
        working meeting                      personnel)

       18 June 2019                        Drafting of the SG1 mandate and

                            Mobility and                                     MOVE
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

                                         Mobility and                                       MOVE
eFTI Regulation - objectives
Main objectives:                                                          Main benefits:

•   (1) ensure the establishment, in all EU Member States, of the         If this is not dealt with on EU level,
    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

                                                  Mobility and                                                  DW
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
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

                                          Mobility and                              DW
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.

                                               Mobility and                                         DW
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).

                                           Mobility and                                      DW
SG1 tasks relating to eFTI
Grouping of activities                                 Characteristics of the
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

                                        Mobility and                                   DW
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

                                           Mobility and                                     DW
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
• List the legally required data, covered by the           and differences in:
  annex as a starting point (if available). In other       • data elements (both main set and
  words; what are the minimum requirements
• Then see how this would match/fit with the
  existing models like WCO and/or UN-CEFACT, but           • definitions
  of course also the EUCDM
                                                           • characteristics
• Lastly, we can compare it to private sector
  models/standards                                         • code lists

                                                           • cardinality and occurrence

                                            Mobility and                                    DW
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
  way forward would be                           • Provide advice on governance of the model

                                                 • cardinality and occurrence

                                         Mobility and                                         DW
Tasks 2 – Functional aspects (1)
I. Analysis/Business Process                       Questions
                                                   • 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?

                                           Mobility and                                            DW
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)
                                                • 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

                                        Mobility and                                         DW
Tasks 3 – Technical aspects
• Depends on functional aspects          Technical aspects to be considered
                                         • Preferred interfacing options
• Certain elements will be required in
  any case                               • B2A and where relevant A2B & A2A, depending on
                                           push or pull
• Abundance of possible solutions
                                         • S2S and U2S
• Can already be analysed (SWOT)         • (Where relevant) Database requirements
• Existing solutions                     • Authentication, identification (related to platform
                                           and service provider requirements)
• Take into account platform & service   • Confidentiality, integrity and availability (related to
  provider requirements                    platform and service provider requirements)
                                         • Capacity requirements

                                         Mobility and                                            DW
Tasks 4 – Platform & SP requirements
Different elements                                        Subtasks deliverables

• Closely related to functional & technical aspects       • Authentication & Identification

• How regulatory transport information is made            • Confidentiality, integrity and
  available, in what cases, and by whom this can be         availability
                                                          • Access rules, roles & governance
• Correspondance to the common eFTI data set and

• Data safety & security (GDPR, commercial etc)

                                           Mobility and                                       DW
Tasks 5 – Certification
1. Certification requirements                               2. Certification procedure

• Harmonised, Specific requirements                         • Same balance required
• Known in advance                                          • Appeal procedure
• Remain able to adapt                                      • When to re-assess
• Respect different actors and activities                   3. Providing proof of certification
Balance required                                            • How to provide proof
• sufficient clarity and harmonisation                      • In what cases can proof be required
• sufficient flexibility and ability to adapt to new        • What to do if proof is refused
  business concepts and technology

                                             Mobility and                                         DW
Tasks 6 – Other aspects
Implementation strategy & planning                        Testing facilities
• Deadlines set by legislation                            • Not just for (re)assessment
• Will be discussion during trialogue                     • Authorities and operators and
• Nonetheless, realistic and acceptable planning            service providers must be able to
  required                                                  test

Communication, training and helpdesk facilities           • End-to-End

• Common understanding of the purpose,                    • Joint controlled environment
  functioning, requirements and benefits is crucial
• Where to go with questions

                                           Mobility and                                     DW
Planning & organisation of the work (1)
Phases                     To be determined

• Phase 0 - Q3 2019        • Agreement over organisation work plan

• Phase 1 – Q4 2019        • Agreement over planning work plan

• Phase 2 – Q1 2020        • Establishment of teams

• Phase 3 – Q2 – Q3 2020   • Appointment Team leads & co-team leads

• Phase 4 – Q4 2020

                                    Mobility and                      DW
Phase 0 - Phase 1 – Phase 2 –       Phase 3 –       Phase 4 –
                    DTLF - Subgroup 1- Paperless transport                            Q3 2019    Q4 2019   Q1 2020       Q2 & Q3 2020      Q4 2020
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)
                                                                   Mobility and                                                                        DW
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

                                  Mobility and                                MOVE
Digital Corridor Information Systems

          •   DTLF Plenary meeting
               •   19 June 2019
                   •   Brussels

                        Mobility and
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
    of 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

                                             Mobility and                                                 MOVE
Use case presentation

             Joost Naessens

European Chemical Industry Council - CEFIC

                   Mobility and              MOVE
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

                                   Mobility and                                    MOVE
Progress report (2)
DTLF SG2 in the EC Online Survey: February 2019

               Subgroup 2 members

               Overall number of DTLF
               members willing to                              In Subgroup 2 only
               engage in SG2 activities.                       Core SG2 members who
                                                               have committed to

                                                               dedicate their time to
                    In both Subgroups
                                                               SG2 exclusively.
                    Over half of confirmed
                    SG2 members are also
                    willing to engage in SG1

                                           Mobility and                                 MOVE
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

                                      Mobility and                                  MOVE
Progress report (4)
DTLF SG2 meeting: April 2019
• Building blocks of the federated platform

                                       Mobility and   MOVE
Progress report (5)

DTLF SG2 meeting: April 2019                                           Rapporteur: RISE
• Organisation of the DTLF SG2
                                           DTLF SG2

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

                     15 members     19 members          16 members          16 members

                                        Mobility and                                        MOVE
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

                                                 Mobility and                                   MOVE
Objective for this meeting

• Discussion and possible endorsement of the draft workprogramme
  (version 29052019)
• Mandate for continuing the work based on the draft workprogramme

                            Mobility and                             MOVE
Recap: Digital corridor information systems concept

Creation of a Federative Network of                         Design principles:
Platforms for data sharing with two                         •   Register and connect once
main features:
• one single entry point for organisations                  •   Interoperability by default
  (business and authorities)                                •   Open infrastructure with a solution of
• platform interoperability                                     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                                                MOVE
Federative Network of Platforms
                                              - mapping to the Building Blocks -
A          Enterprise (customer)
                                                                   FED                                   Enterprise (service provider)

    IT back-office                  Access                   Business-to-business                    Access                 IT back-office
       systems                       Point                                                            Point                    systems
                                                        Interoperability (peer-to-peer)

B      Enterprise (customer)
     IT back-
                                                                                                     Enterprise (service provider)
                                                                                                                         IT back-
      office               Access
                            Point                                Platform                            Access



        Enterprise (customer)                services                                     services            P&P
                                                                                                     Enterprise (service provider)

C    IT back-
      office                       Access
                                             TIS    Platform         FED       Platform              Access
                                                                                                                             IT back-

                                    Point                                                             Point
     systems                                                                                                                 systems

                                             Platform               Platform
       Enterprise (customer)                                                                         Enterprise (service provider)
                                             services           interoperability

    IT back-                       Access
                                                                                                                              IT back-
     office                         Point                                                             Point                    office
                                                                                   FED                                        systems

                                             Platform                           Platform
                                             services                       interoperability   Mobility and                                              ML
From building blocks to work plan

  Business process                        Federated Platform
   interoperability                          functionality

Guidelines, behaviour                       technology and
  and governance                               platforms

                           Mobility and                        ML
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

                                                Mobility and                                       ML
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

                                            Mobility and                                         ML
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

• 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

                                                 Mobility and                                              ML
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

                                                  Mobility and                                       ML
Feedback from the DTLF SG2 meeting

Endorsement of the draft SG2 work programme

                     Mobility and             MOVE
Open discussion

       Mobility and   MOVE
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?

                                       Mobility and             MOVE
Next steps

• Comments from the SG2 and plenary meetings

• The SG2 teams

• Input from CEF projects

• Second version of the workprogramme

                                Mobility and   MOVE
between DTLF SG1 and SG2

          Mobility and
Objectives & characteristics of S1 & SG2

SG1 – to de preparatory work for and to assist &                SG2 – to develop specifications and a governance
advice on eFTI regulation & implementation                      structure for a Federative Network of Platforms

                                                                • Main scope: B2B/B2G/G2B, including: infrastructure
• Main scope: B2G/G2B, exchange of regulatory                     management, traffic management, cross border
  information on goods,                                           management, trade facilitation, risk management,
                                                                  marketplace logistics services, booking, ordering,
• Scope and deadlines defined by legislation & Mandatory          tracing and tracking, supply chain visibility
  for authorities, Optional for private sector                  • At the moment not subject to any legislative initiative,
                                                                  no specific deadline
• Specifications for data model, common procedures &
  specs for access, requirements & certification                • Specifications for technology independent services,
                                                                  data models, access, registration, protocols for platform
                                                                  interoperability, open standards, governance

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

                                      29 Jan                              2019                                Q1 2020 –
     17 May                           2019                                                                    Q4 2023
     2018                                                                 • Start of EP-
                                      • First reading                       Council                           • Preparation &
     • Proposal                         adopted by                          discussions in                      adoption of
       adopted by                       European                            trialogue                           technical
       Commission                       Parliament                          format                              specifications

                    June 2018                           6 June                               End                                 Q1
                    • Start of                          2019                                 2019/Start                          2024/2026
                      consideration                     • Adoption of                        2020                                (tbc)
                      by European                         General
                      Parliament                                                             • Final text                        • Entry into
                                                          Approach by                          adoption by                         force
                      and Council                         Council                              EP & Council

                                                                        Mobility and                                                            MOVE
Possible elements that require alignment
    • Timing?
    • Data models/sets?
    • Access rules/registration?
    • Semantic models?
    • ……?

                                   Mobility and
Thank you for your attention

           Mobility and
You can also read
Next slide ... Cancel