Ref. Ares(2019)933834 - 15/02/2019
Deliverable D3.2
CREL (Core Release) Synchronization Report
Project acronym: ATTRACkTIVE Starting date: 01/09/2016 Duration (in months): 28 Call (part) Identifier: H2020-S2RJU-CFM-2015-01-1 Grant agreement no: 730822 Due date of deliverable: 28/02/2018 Actual submission date: 21/01/2019 Responsible/Author: Sofie Käthe Agergaard Dissemination level: PU Status: Issued
Reviewed: yes
G A 730822 P a g e 1 | 1 1 8
Document history Revision Date Description 1 18/05/2018 Initial version 2 08/08/2018 Update with partners contribution 3 03/01/2019 Update main decisions 4 18/01/2019 Partner review 5 21/01/2019 Final release
G A 730822 P a g e 2 | 1 1 8
TABLE OF CONTENT
TABLE OF CONTENT ...... 3
EXECUTIVE SUMMARY ...... 5
LIST OF FIGURES ...... 6
1. INTRODUCTION ...... 7
1.1 List of acronyms ...... 7
1.2 Reference documents ...... 8
2. LIST OF SYNCHRONISATION MEETINGS ...... 9
3. MAIN DECISIONS ...... 11
3.1 Release Split – Discussions & Decision(s) ...... 11
3.2 Engineering Methodology (Capella/TFC Solutions) – Discussions & Decision(s) ...... 11
3.3 ATTRACkTIVE Dependencies on the ongoing CFM Projects – Discussions & Decision(s) ...... 12
3.4 Common Integration Environment Issue – Discussions & Decision(s)...... 12
3.5 Documentation and Source Codes Management – Discussions & Decision(s)...... 12
3.6 Glossary – Discussions & Decision(s) ...... 13
3.7 Use Case documents – Discussions & Decision(s) ...... 13
3.8 Configuration tools ...... 13
3.8.1 Mantis ...... 13
3.8.2 GitLab ...... 14
3.8.3 RACI Table ...... 15
4. APPENDICES ...... 16
4.1 TMT workshop – WPs 1, 2, 3 (29/03/2017 and 30/03/2017) ...... 16
4.2 Expert Group Meeting – WP3 Common LightHouse/CFM meeting with the Experts Group (26/04/2017 and 27/04/2017) ...... 23
4.3 Collaboration Workshop – IP4 meets IT2Rail & OCs GoF4R & ST4RT (03/05/2017 and 04/05/2017) ...... 24
G A 730822 P a g e 3 | 1 1 8
4.4 TMT Workshop – WPs 1, 2, 3 (07/06/2017) ...... 37
4.5 Capella Coaching Session – WPs 1, 2, 3 (06/09/2017) ...... 63
4.6 TMT Workshop – WPs 1, 2, 3 (26/09/2017) ...... 74
4.7 Collaboration Workshop – S2R COLA Info My- TRAC cooperation (09/11/2017)...... 81
4.8 TMT Workshop & Pre-Advisory Board (04/12/2017 and 05/12/2017) ...... 82
4.9 Collaboration Workshop – IP4 CFM meets IT2Rail (14/12/2017) ...... 93
4.10 Collaboration Workshop – IP4 CFM meets IP4 OCs (15/12/2017) ...... 100
4.11 T4C meetings ...... 109
G A 730822 P a g e 4 | 1 1 8
EXECUTIVE SUMMARY
This document has been prepared in order to report the synchronisation activities, within the CREL scope, between ATTRACkTIVE project and other calls, especially IT2Rail project and Co-Active (S2R-IP4-CFM-01-2015).
All synchronisation meetings have been listed in chapter 2, while the main decisions resulting from these meetings are described in chapter 3. These main decisions include for example the use of the same engineering methodology and tools (Capella, Gitlab, Mantis…) or agreements on technical questions and documentation. These main decisions were necessary in order to set a common ground for inter-project technical and management issues.
Furthermore, all meeting minutes of the synchronisation activities are available in the appendices.
G A 730822 P a g e 5 | 1 1 8
LIST OF FIGURES
Figure 1 : French interface of Mantis ...... 14 Figure 2 : Features the dedicated ATTRACkTIVE front end interface set up for the project...... 14
G A 730822 P a g e 6 | 1 1 8
1. INTRODUCTION
This deliverable will report the synchronisation activities, during the CREL, between this project and other calls.
1.1 List of acronyms
AMA Amadeus
BT Booking and Ticketing
CREL Core Release
DXT Diginext
EC European Commission
GA Grant Agreement
HAC HaCon
IND Indra
MAAP Multi Annual Action Plan
NR Network Rail
PCT Project Coordination Team
PSP Payment Service Provider
pTT partial Trip Tracker
SC Steering Committee
THA FR Thales France
THA PT Thales Portugal
TO Tracking Orchestrator
TMT Technical Management Team
VCC Virtual Credit Card
WP Work Package
G A 730822 P a g e 7 | 1 1 8
1.2 Reference documents
[R1] Co-Active Grant Agreement – N° 730846 08/08/2016
[R2] Co-Active Consortium Agreement version 1 28/07/2016
G A 730822 P a g e 8 | 1 1 8
2. LIST OF SYNCHRONISATION MEETINGS
Participants Meeting Linked WP / Date Location (beneficiaries short Category/Title Activity name)
29/03/2017 HaCon, THA, AMA, HAC, IND, TMT workshop WPs 1, 2, 3 and Brussels NR, ANS, DXT 30/03/2017
WP 3
Common 26/04/2017 Expert Group Indra, THA, AMA, HAC, IND, LightHouse/CFM and Meeting Madrid NR meeting with the 27/04/2017
Experts Group
Collaboration WPs 1, 2, 3 03/05/2017 Workshop – IP4 UNIFE, THA, AMA, HAC, IND, IP4 meets IT2Rail and meets IT2Rail & OCs Brussels NR, DXT & OCs 04/05/2017 (GoF4R & ST4RT)
THA, AMA, HAC, IND, TMT Workshop WPs 1, 2, 3 07/06/2017 Prague NR
Capella Coaching Thales, WPs 1, 2, 3 06/09/2017 THA, AMA, IND Session Paris
Indra, THA, AMA, HAC, IND, TMT Workshop WPs 1, 2, 3 26/09/2017 Madrid NR, ANS, DXT
Collaboration WPs 1, 2, 3
Workshop – S2R S2R COLA Info Diginext, 09/11/2017 HAC, IND COLA Info My- My-TRAC Paris
TRAC cooperation cooperation
G A 730822 P a g e 9 | 1 1 8
Participants Meeting Linked WP / Date Location (beneficiaries short Category/Title Activity name)
WPs 3 and 4 04/12/2017 Network TMT Workshop & Pre- Common CFM THA, AMA, HAC, IND, and Rail, Advisory Board projects pre-AB NR 05/12/2017 London was established
Collaboration WPs 1, 2, 3 UNIFE, THA, AMA, HAC, IND, Workshop – IP4 IP4 CFM meets 14/12/2017 Brussels NR, DXT CFM meets IT2Rail IT2Rail
Collaboration WPs 1, 2, 3 UNIFE, THA, AMA, HAC, IND, Workshop – IP4 IP4 CFM meets 15/12/2017 Brussels NR, DXT CFM meets IP4 OCs IP4 OCs
G A 730822 P a g e 10 | 118
3. MAIN DECISIONS
3.1 Release Split – Discussions & Decision(s)
This decision was discussed during TMT workshop – WPs 1, 2 and 3 (29/03/2017 and 30/03/2017)
C-REL will be spilt into two releases in order to meet with the dependencies with IT2Rail and with InnoTrans18.
C-REL: specification and implementation (Nov17 tbc) o 1st set of functionalities: Definition, Specification, Implementation, Testing, but method and algorithm oriented A-REL: Integration (Apr18)
Preparation for the integration in TD
This decision was acted during TMT Workshop – WPs 1, 2 and 3 (26/09/2017)
The official decision about pre-CREL/pre-FREL structure and the definition of the schedule attached were decided during this meeting. The main reason of this decision involved InnoTrans demonstration. In order to reach InnoTrans interesting demonstration, we added pre-CREL (to prepare the CREL) and pre-FREL = InnoTrans release.
Pre-CREL CREL CREL AREL Pre-FREL FREL FREL
3.2 Engineering Methodology (Capella/TFC Solutions) – Discussions & Decision(s)
This decision was done during TMT Workshop – WPs 1, 2 and 3 (26/09/2017)
The use of Capella is confirmed by all partners. There will be one Capella model for Shift2Rail, for all CFM projects. The version of Capella will be 1.1.2.
We decided to use Team for Capella, to allow the simultaneous time working on Capella. See §4.11 T4C meetings.
G A 730822 P a g e 11 | 118
During several meetings and conference calls it was decided how to work with Capella: training sessions, inputs from IT2Rail, timing, etc.
3.3 ATTRACkTIVE Dependencies on the ongoing CFM Projects – Discussions & Decision(s)
This subject was discussed during the TMT Workshop – WPs 1, 2 and 3 (04/12/2017)
For Work Package 2, Travel Companion, the Android Framework developed in IT2Rail can be taken over by ATTRACkTIVE. On the base of this framework each partner can develop their specific module which will then be integrated by DXT into the Android Application
Dependencies with IT2Rail and Co-Active: ATTRACkTIVE provides the TC, being the interface through which the user requests/launches the shopping and booking functionalities performed by Co-Active modules. The SNCF Source Code of the Travel Companion will be analysed by HaCon as soon as the code is available to proof which part(s) could be used in the ATT Travel Companion.
3.4 Common Integration Environment Issue – Discussions & Decision(s)
This subject was discussed during the TMT Workshop – WPs 1, 2 and 3 (04/12/2017)
ThalesPT will elaborate software solution which helps to test distributed systems.
Pending the setup of this software solution/environment, ThalesFR proposed using of a common integration environment (e.g. remote public cloud: Azure, OVH…), where each partners expose his results (services) in order to make COHESIVE mission easier (avoid partner’s availability problem, avoid partner’s network firewall & security constraints…).
3.5 Documentation and Source Codes Management – Discussions & Decision(s)
This subject was discussed during the TMT Workshop – WPs 1, 2 and 3 (04/12/2017)
G A 730822 P a g e 12 | 118
It was decided to create under COHESIVE space in the cooperation tool a section to host a common repository of IP4 documentation.
A similar folder will be created on COHESIVE private space in the cooperation tool covering information relevant to the OC (accessible by their coordinators).
The source code coming from IT2Rail will be transferred directly from the originator partner in IT2Rail to the destination partner in S2R/IP4 (in agreement with the JU). The same process will apply for source code transfer between consecutive and related CFM projects.
3.6 Glossary – Discussions & Decision(s)
This subject was discussed during the TMT Workshop – WPs 1, 2 and 3 (04/12/2017)
For the understanding of all Shift2Rail project, we decided to add a common glossary for all Shift2Rail projects. This document has been written from the IT2Rail one. This glossary is delivered in the CoopTool and linked to ontologies deliverables.
3.7 Use Case documents – Discussions & Decision(s)
This subject was discussed during the Collaboration Workshop – IP4 CFM meets IP4 OCs (15/12/2017)
For the understanding of ATTRACkTIVE and Co-Active projects, we decided to add a use case document. This document helps the definition of the use cases, in order to success the integration. This document is delivered in the CoopTool.
3.8 Configuration tools
This subject was discussed during the TMT workshop – WPs 1, 2 and 3 (29/03/2017 and 30/03/2017)
3.8.1 Mantis
The ticket management is important for a collaborative project like ATTRACkTIVE and Co-Active. Because of the context of these projects, it’s very useful to track changes and updates. It allows also defining responsible partners to work on a specific topic, to ensure the coherence of the entire project. That’s why, all partners agreed to use Mantis as ticket management software. HaCon provides the platform and manages all access needed.
G A 730822 P a g e 13 | 118
Figure 1 : French interface of Mantis
3.8.2 GitLab
In order to plan the successive integration windows with the available version of the modules, a specific versioning control system “GitHub” provided for the ATTRACkTIVE project was established. By having access to the GIT dedicated specially to the project, the partners import their modules when ready.
Figure 2 : Features the dedicated ATTRACkTIVE front end interface set up for the project.
G A 730822 P a g e 14 | 118
3.8.3 RACI Table
A RACI Table is used to define Roles for each partner. Our collaborative project required a table like that to ensure the communication between partners.
G A 730822 P a g e 15 | 118
4. APPENDICES
The aim of all this section is to get more information about all meetings for 2017. There is some extracts from the most important synchronisation meetings and highlight of the main decisions.
4.1 TMT workshop – WPs 1, 2, 3 (29/03/2017 and 30/03/2017)
Attendees List
Status Status Name Company TMT Day1 TMT Day2 Tom Jones (TJ) Amadeus A A
Emilio Garcia-Pozuelo (EGP) Amadeus A A
Fabrizio Cosso (FC) Ansaldo STS A A
Pascal Flauder (PF) Diginext A A
Rémi Courtel (RC) Diginext A A
Eric Velay (EV) Diginext A A
Daniel Schmidt (DS) HaCon A A
Achim von Der Embse (AVDE) HaCon A A
Leyre Merle (LM) Indra A A
Scott Heath (SH) Network Rail E A
Silvia Umiliacchi (SU) Network Rail E A
Edouard Carpentier de Changy (ECC) Thales FR A A
Marco Ferreira (MF) Thales PT A A
Elvino Monteiro (EM) Thales PT A A
A: Attended – E: Excused
G A 730822 P a g e 16 | 118
Minutes of Meeting (MoM)
Day 1: TMT
Time Topic Responsible
Opening Session HaCon
Antitrust: the Antitrust statement was presented
Round table: round table was made Edouard described that/ o He is participating in this meeting on behalf of Lionel LEVIEUX o For the time being, he will be the technical leader (system engineering manager) of Co-Active and the project coordinator (on behalf of Lionel LEVIEUX).
Agenda: the agenda was approved
Status of the projects – Co-Active Thales
WP1 – Travel Shopping (HaCon): Daniel explained the status of TS (see slides “CoA-TMT-WP1_00-01-00.pptx”)
WP2 – Booking & Ticketing (Thales): Edouard explained the status of BT (see slides “CoA-TMT-WP2_v0.pptx”)
WP3 – Business and Contractual management (Thales): Edouard explained the status of BCM (the SWIG communication strategy was presented, yet no declination has been done at the CFM project level)
Status of the projects – ATTRACkTIVE HaCon
WP1 – Trip Tracking (HaCon): Achim explained the status of TT (see slides “ATT WP1 status Tracking.pptx”) o Main work is spend on event sources and event generation o HaCon proposed a system architecture called “Distributed Trip Tracking” (DTT) . Each travel expert shall have its own Trip Tracker called “Partial Trip Tracker” (PTT) . A “Tracking Orchestrator” combines and processes the input generated by the PTT; it acts as CEP . The PTT will be fed by Event Sources; these sources are linked to one specific PTT
WP2 – Travel Companion (Diginext):
G A 730822 P a g e 17 | 118
Day 1: TMT
Time Topic Responsible
Presentation of the WP status o All tasks and nearly all subtasks are active. Most of the work of all tasks is about: . Analysing the output of IT2RAIL and how it can be reused . Investigation on how to architecture the software component . Research and state of the art on specific points/subtasks o There are no external outputs or deliverables o More details are available in the WP2 status of M7 document Next steps and Actions include: o Getting the IT2RAIL output: . reusability matrix . software components . cleaned up Capella model o Analysing these outputs o Writing the C-REL specifications Questions / Discussions o Partners who can should begin working on the implementation based on what was discussed during the TMT o The role of the “main” app versus the experiences: the “main” app should cover the whole travel and launch the experiences during specific travel episodes Definition of the C-REL and F-REL scopes discussed on second day 1st Report – ATTRACkTIVE HaCon
Technical: First Technical Report is delivered in time Table of Content according to a by the EU provided template Document can be downloaded from the EU-Project portal (not from the CoopTool)
Financial: Daniel shows the figures for the 1st period M1-M4 The figures are between 2% and 19% Action: All partners send their IKOP figures for M1-M4 to the coordinators. 1st Report – Co-Active Thales
Technical: Delivered 1month late (having well informed the Project Officer about the reasons) Document is the EU participant portal but not the cooperation tool (not ready yet)
Financial: Delivered one month late
G A 730822 P a g e 18 | 118
Day 1: TMT
Time Topic Responsible
Action: All partners send their IKOP figures for M1-M4 to the coordinators.
Dissemination Activities Thales
Project website: Published in time, will need updates when first newsletter will be published
Newsletter: Activity hasn’t started yet
TRA2018: Abstract for Co-Active is under review by the project officer
InnoTrans2018: Collection of Ideas: o JP for journey from booth to booth at the InnoTrans o Rally o Visit to “Südkreuz” to see indoor capabilities Tooling HaCon
Mantis: Mantis Bug-Tracking Tool will be used throughout the project Mantis is project oriented; following projects will be set up: o Bug-tracking o Capella o Open issues Achim will distribute a tutorial
RACI Table: A RACI Table is used to define Roles for each partner Table goes down from WP to subtask Thales shall enter the WP/Task/Subtask for Co-Active At least per WP and Task roles have to be defined Part of the table is a list of all members including o mail address o telephone number o definition for which Mantis project a member shall be activated if any
Cooperation Tool: Daniel explained the CoopTool briefly JU has access to all folders but PRV
G A 730822 P a g e 19 | 118
Day 1: TMT
Time Topic Responsible
The following sections will be used: o “Members” to see contact details of all members o “Documents” to share documents, e.g. agendas, minutes, specification documents, templates, deliverables etc. o “Meetings” to plan meetings o “Administrative” to help by the administrative management
GitLab GitLab is activated on HaCon servers It will be used (only) as repository (similar to SVN) GitLab works with a two factor authentication After receiving a token it can be accessed through a normal browser It works with Git software like “TortoiseGit” very similar to SVN / “TortoiseSVN”
Day 2: TMT
Time Topic Responsible
Opening Session HaCon
Antitrust: the Antitrust statement was presented
Round table: round table was made Reusability of Results from IT2Rail Thales
Process: 1. Commitment of IT2Rail how to deliver what and how: “Component Analysis” ( Mid-April) new columns needed: “copy-left inside?”, “Access to Background” 2. Analysis by S2R IP4 partners if this fits to the requirements / use cases for S2R IP4 ( End April) 3. Discussion between IT2Rail and Shift2Rail partic 4. ipants ( May)
Function Reusability (Specification + Model) : A undergoing study is led by IT2Rail to “qualify” better what functionalities could be reused exactly The reuse criteria aren’t well defined yet: document/model Quantity, Quality, Extensibility,
Component Analysis (Implementation): A first analysis has been conducted by IT2Rail (excel sheet containing a clear definition of the software
G A 730822 P a g e 20 | 118
Day 2: TMT
Time Topic Responsible
deliverables) This document has been delivered to Shift2Rail partners for feedback
Integration and final Demonstration in 2022: All use cases / function should be runnable / integrated in the final POC of S2R IP4, but not necessarily performed by the original components Release Planning HaCon
Dependencies: Daniel explained the dependencies to o IT2Rail as the S2R IP4 lighthouse project o TD4.7 project “COHESIVE” as the integration and demonstration project of S2R IP4 o Dissemination activities at TRA18 and InnoTrans18
Timing: Re-planning of the releases into three releases: o C-REL: 1st set of functionalities: Definition, Specification, Implementation and Testing o A-REL: preparation for integration o F-REL: 2nd set of functionalities; preparation for integration
Use Case – Co-Active Thales
G A 730822 P a g e 21 | 118
Day 2: TMT
Time Topic Responsible
1st ideas for the use cases / functionalities were collected (see slide 35) Action: (re)definition of the use case / functionalities for each release
Use Case – ATTRACkTIVE HaCon
1st ideas for the use case / functionalities were collected (see slide 36) Action: (re)definition of the use case / functionalities for each release
G A 730822 P a g e 22 | 118
4.2 Expert Group Meeting – WP3 Common LightHouse/CFM meeting with the Experts Group (26/04/2017 and 27/04/2017)
Attendees List
Please refer to Co-Active deliverable D5.4 – Recommendations and conclusions of the Experts Group. Minutes of Meeting (MoM)
Please refer to Co-Active deliverable D5.4 – Recommendations and conclusions of the Experts Group.
G A 730822 P a g e 23 | 118
4.3 Collaboration Workshop – IP4 meets IT2Rail & OCs GoF4R & ST4RT (03/05/2017 and 04/05/2017)
Day 1
Attendees List
Name Company Status1
Alessio Carenini (AC) CEFRIEL A
Achim von der Embse (AvdE) HaCon A
Daniel Schmidt (DS) HaCon A
Edouard Carpentier de Changy (ECdC) Thales E
Elvino Monteiro (EM) Thales Portugal A
Fabrice Setta (FS) UIC A
Florian Briy (FB) (partly) Amadeus A (via call)
Guido Di Pasquale (GdP) UITP A
Guido Mariotta (GM) Leonardo Company A
José Eugenio Bertolín Corisco (JB) Indra A
John Lutz (JL) UIC A
Marco Comerio (MC) CEFRIEL A
Marco Ferreira (MF) Thales Portugal A
Matteo Rossi (MR) Politecnico di Milano A
Nora Winninger (NW) SNCF E
Petr Buchníček (PB) Oltis Group A
Rémi Courtel (RC) Diginext A
1 A: Attended, E: Excused
G A 730822 P a g e 24 | 118
Name Company Status1
Riccardo Santoro (RS) Trenitalia A
Stefanos Gogos (SG) UNIFE A
Scott Heath (SH) Network Rail A
Stijn Lewyllie (SL) EPF E
Tom Jones (TJ) Amadeus A
Ugo Dell'Arciprete (UdA) Hit Rail A
Minutes of Meeting (MoM) Most of discussions and decisions held during this meeting were used for the drafting of the IT2Rail deliverable D8.5 – Intermediate report on the use of the results by S2R. Please refer to IT2Rail deliverable D8.5 – Intermediate report on the use of the results by S2R.
Time Topic Responsible
10:00 Opening Session John Lutz
SG welcomed the participants and explained that the ST4RT Advisory Board platform will be used for the collaboration workshops which will bring together all the WP leaders from the different IP4 projects. He added that numerous collaboration workshops will be needed, focusing on specific aspects and these will be organised by the relevant projects depending on the needs. The ST4RT Advisory Board will be used for the initial workshop, whose aim will be to go through the overview and needs of each project and define the collaboration procedures. Most likely another ST4RT Advisory Board will be organised in a year’s time, bringing together all the WP leaders again in order to have some concluding remarks of the collaboration that was established and to address any open points.
SG then explained that JL has been assigned as the moderator of the 2-day workshop. JL introduced himself and suggested roundtable introductions, in order to understand each participant’s role in the different projects and their expectations from the collaboration workshop.
The agenda of the meeting was approved.
G A 730822 P a g e 25 | 118
10:30 Overview IP4 Daniel Schmidt
DS gave a general overview of the S2R IP4 objectives and general timeline, whilst highlighting the different research areas being tackled in each IP4 project.
There was a debate on whether the S2R JU should be directly involved in this kind of collaboration workshops, but it was pointed out that the link should be established via the reporting to the IP4 Steering Committee. The S2R JU should not be directly involved in the technical discussions of the collaboration workshops.
10:45 Overview IP4 projects Project Coordinators
The project coordinators/technical leaders presented their respective projects, showing the general overview, scope, organisation, timeline, expected outcomes and current status, whilst highlighting the areas where collaboration would be needed.
SG presented IT2Rail.
JL presented GoF4R. It was highlighted that GoG4R needs to understand the use cases from each project in order to be able to establish appropriate governance rules. It was also added that GoF4R is looking into the W3C organisation in order to propose a similar environment.
RS presented ST4RT. He explained that the basis for the conversions in ST4RT will be TAP TSI and FSM, but in case that these are not used in other projects, then a new direction could potentially be sought. UdA elaborated that the idea is to start from UIC 918.1, which are binary messages that are then copied into the TAP TSI B.5. He then added that UIC has developed a new version of UIC 918.1 which is in XML, for which FSM has been based on.
DS presented Co-Active on behalf of Thales.
DS presented ATTRACkTIVE.
Please refer to the presentation attached to the minutes for more details on each project.
12:45 Lunch break
13:30 IT2Rail vs. Shift2Rail: Reusability + Enhanceability Daniel Schmidt / All
DS explained that the afternoon will focus on the level of Reusability and Enhanceability between IT2Rail and
G A 730822 P a g e 26 | 118
S2R IP4 projects, by looking into the maintenance aspects, the analysis of the IT2Rail outcomes and other related risks and issues. He then added that IT2Rail did a first component analysis, which will be used to find potential reusability and Enhanceability risks.
The exercise on reusability started by going through the Travel Shopping WP of Co-Active, in order to understand which IT2Rail functionalities could be enhanced and in what way.
General comments:
Adapt meta network so that there are not only stop points.
See how each of the components can handle additional preferences.
For Availability and Pricing Optimization, link to external components for Availability and Pricing are no longer planned within the IT2Rail model. Another possibility could be the model of an external “travel expert manager” to be applied instead.
The participants went through a spreadsheet with the list of functionalities that was created, which describes their relationship with IT2Rail and the possible open questions/issues on how these functionalities should be enhanced. As an exercise, the participants tried to take each functionality one by one, defining how to overcome the obstacles of reusability and Enhanceability and what the next steps could be. This will allow for a more concrete follow-up of actions and risk evaluation later on. The exercise was too time-consuming to finalize during the meeting, but please refer to the table enclosed below for more details on the work achieved so far:
Microsoft Excel Worksheet
RS commented that there is a need to establish how much time and effort will be associated to having a meaningful collaboration in terms of co-design between the different projects. One potential outcome of this workshop could be to come up with this high-level design estimate of the effort that will be needed.
Decision: A Travel Shopping workshop needs to take place between HaCon, Amadeus, INDRA, Leonardo and Thales France.
G A 730822 P a g e 27 | 118
The exercise on reusability continued with AvdE presenting the Trip Tracking WP of ATTRACkTIVE and analysing the different needs in connection to IT2Rail.
Decision: A Trip Tracking workshop needs to take place between HaCon, Diginext, Leonardo, Polimi, Oltis Group and Thales Portugal in order to understand better whether the architecture is compatible between ATTRACkTIVE and IT2Rail and to understand whether there are any potential reusability and Enhanceability risks.
The Travel companion WP of ATTRACkTIVE was then presented by RC.
Decision: Conference calls to be established at first between Leonardo, SNCF, HaCon, Diginext, Thales Portugal and Indra in order to understand the architecture and then have a dedicated workshop in order to go more into the details. This workshop should be combined with the Trip Tracking one.
The GoF4R and ST4RT reusability and Enhanceability analysis was moved to the next day and therefore the agenda for DAY 2 of the ST4RT AB- collaboration workshop was slightly modified as follows:
09:00-10:00 – GoF4R and ST4RT analysis of reusability and Enhanceability vs IT2Rail
10:00-13:00 – Collaboration Process (including Synchronisation of planning for all the projects)
14:00-15:30 – Next steps
15:30-16:00 – AOB
END of DAY 1 at 19:00
Day 2
Attendees List
Name Company Status2
Alessio Carenini (AC) CEFRIEL A
Achim von der Embse (AvdE) HaCon A
2 A: Attended, E: Excused
G A 730822 P a g e 28 | 118
Name Company Status2
Daniel Schmidt (DS HaCon A
Edouard Carpentier de Changy (ECdC) Thales E
Elvino Monteiro (EM) Thales Portugal A
Fabrice Setta (FS) UIC A
Florian Briy (FB) Amadeus E
Guido Di Pasquale (GdP) UITP A
Guido Mariotta (GM) Leonardo Company A
José Eugenio Bertolín Corisco (JB) Indra A
John Lutz (JL) UIC A
Marco Comerio (MC) CEFRIEL A
Marco Ferreira (MF) Thales Portugal A
Matteo Rossi (MR) Politecnico di Milano A (partly)
Nora Winninger (NW) SNCF A (partly)
Petr Buchníček (PB) Oltis Group A
Rémi Courtel (RC) Diginext A
Riccardo Santoro (RS) Trenitalia A
Stefanos Gogos (SG) UNIFE A
Scott Heath (SH) Network Rail E
Stijn Lewyllie (SL) EPF E
Tom Jones (TJ) Amadeus A
Ugo Dell'Arciprete (UdA) Hit Rail A
Minutes of Meeting (MoM)
Time Topic Responsible
G A 730822 P a g e 29 | 118
GoF4R and ST4RT analysis of reusability and Enhanceability vs John Lutz / Riccardo 09:00 IT2Rail Santoro
The exercise on reusability continued with JL mentioning that GoF4R will establish governance for the process, work flow, change management, synchronisation, credentials and procedures. Come up with rules that will be extensible for new components, assets, tools that are going to be developed in IP4. Therefore, looking at the timing of the different projects would be important. The identification of the Interoperability Framework assets is also important, but especially in terms of how these assets will be extended.
RS also highlighted that GoF4R will be looking at the governance of the technology. He added that the main principle is that the technology should be independent of what it is being used for, i.e. the point is not to establish governance on how you sell tickets. The ultimate goal is to encourage market uptake.
TJ pointed out that there is also a general reluctance from some operators in different sectors to share their data, so there needs to be a certain reassurance that by joining they will still be able to modify their commercial contracts. In terms of market place, RS explained that the idea is to encourage people to be part of it when it takes off, the same way it happened for the web, i.e. if you don’t have a website nowadays your market access will be reduced, but nobody will force you to establish a website.
Therefore, GoF4R’s main challenge is to design guidelines and apply them in order to discover whether they are too strict or whether they don’t actually work and modify them accordingly.
JL stressed that it will be important to have access to IT2Rail deliverables as they are in progress, especially regarding WP1 of IT2Rail. RS added that it would also be important to define how to facilitate the update of the assets.
RS continued by explaining reusability and Enhanceability challenges of ST4RT. He started by pointing out that if nobody from the companies or service providers participating in the other IP4 projects use the languages being analysed in ST4RT, then there is no particular need to analyse the specific languages. ST4RT could therefore possibly go down a different road. What should be discussed is the kind of converters the other projects need and consequently decide on whether another direction should be sought. This is especially relevant in relation to
G A 730822 P a g e 30 | 118
the demonstration activities being pushed by S2R. He added though that there is a lot of pressure to prove that FSM and TAP TSI can work, so if we are switching paths there needs to be a very good reason for it and an understanding from the S2R JU that some of the work that has already been carried out and the effort associated with it might be lost. If they want to bring more operators into S2R, this aspect has to be taken into consideration.
RS also pointed out that ST4RT focuses on aspects related to Booking and Ticketing, along with after sales and not on aspects related to Trip Tracking.
10:00 Collaboration Process John Lutz
Meetings:
The necessity for the following meetings has been identified:
TMT of IP4: Coordinators + Technical Leaders of all ongoing projects. These meetings should be combined with the IP4 Steering Committee if possible in order to be able to report directly to the S2R JU and inform/advise on possible outcomes/recommendations. Decision: The next TMT of IP4 will take place on the 15th June in Brussels (UNIFE premises).
Collaboration workshops with focus on dedicated topics. Decision: The need for the following workshops has been identified:
1) Combined workshop in May between TD4.2 (HaCon, Amadeus, Indra, and Leonardo) and TD4.3 (Thales France, Amadeus, Indra, HaCon) in order to discuss the co-design of some components. Action: DS to organise the workshop. 2) Combined workshop in May between TD4.4 (HaCon, Diginext, Leonardo, Polimi, Oltis Group, Thales Portugal) and TD4.5 (HaCon, Diginext, Leonardo, Thales Portugal, Indra, and SNCF). Action: DS to organise the workshop. 3) GoF4R workshop on the IF assets available in all the projects and how to manage them (e.g. update of the ontology etc.). Have a list of questions ready, since IT2Rail will be finished by end of October and therefore feedback to other projects will be difficult thereafter. Meeting to be scheduled around Sep/Oct, as a kick- off for the activities of WP5 in GoF4R. Action: GdP to organise the workshop in coordination with SG and DS. 4) Conference call for ST4RT: “Which Standards/Converters are needed for the other projects” (Trenitalia, Hit Rail, Polimi, UIC, Thales Portugal, Indra, Oltis Group, HaCon, Diginext, Cefriel). Action: RS to organise the conference call.
G A 730822 P a g e 31 | 118
Collaboration workshop (ST4RT Advisory Board) between WP leaders of all the projects (Sep/Oct) Decision: To be organised in conjunction with the GoF4R workshop which is planned in Sep/Oct (one day each).
Action: SG and DS to organise in cooperation with GdP regarding GoF4R workshop.
Decision workshop. Decision: The approval of the decisions/proposals of the Technicians should take place during the TMT/TMC or SC/SMC of each individual project, but decision workshops could be organised to validate any new proposals. It was highlighted that the S2R JU should be informed in cases where the collaboration cannot be achieved in specific cases or in cases where the efforts will have to be impacted significantly.
Tooling:
The necessity for the following tools has been identified:
RACI table Action: AvdE to send RACI table used in ATTRACkTIVE to RS and JL as a template to be filled in and which should then be shared in a common repository.
Mantis Action: AvdE to create a Mantis project for collaboration issues to be shared with all the IP4-related projects and then to harmonise the tutorial concerning the rules and distribute to all participants.
Capella The main question addressed was how to work with Capella in 4 parallel projects. RS pointed out that there should be a certain level of autonomy in each project, but stressed that there is a need to understand what each project is doing. This could be solved by assigning to some people ‘write’ capabilities and to others ‘read’ capabilities.
Action: Thales Portugal to look into how the appropriate rights could be assigned.
Action: Thales Portugal to look if S2R IP4 can use the professional version of Capella for free.
GitLab AvdE explained that GitLab is used as an SVN solution.
G A 730822 P a g e 32 | 118
Action: HaCon to create a GitLab for the collaboration purposes of all the IP4-related projects.
Access to outcomes:
Decision: The following outcomes should be shared:
Deliverables; Capella Model; Source / Runnable code (if applicable); Services.
Decision: The following versions should be shared:
Public outcomes; Confidential outcomes to be shared on a case by case basis and by request only; Intermediate versions to be shared upon request.
Action: HaCon to check whether a GitLab could be used as a common repository in order to share intermediate outcomes and documents that are work in progress between the projects. Once created, the list of deliverables for the different projects should be uploaded on the common repository.
Synchronisation of the planning for all the projects:
SG explained that the next important milestone for IT2Rail is the FREL which is due in month 28 (end of August).
DS shared the main milestones of Co-Active and ATTRACkTIVE, which are as follows:
CREL planned for Nov2017 AREL planned for Apr2018 FREL planned for Dec2018
RS pointed out that the review of the timetables should be done every three months or so, in order to check whether things are going according to schedule and to be able to identify potential inconsistencies.
Action: The S2R IP4 TMT has to perform this check quarterly.
For ST4RT there are some dependencies with IT2Rail, but there could also be a potential big impact depending
G A 730822 P a g e 33 | 118
on the outcomes of the workshop which will be planned about deciding on the converter language to be used in the project.
Action: Co-Active and ATTRACkTIVE to send a list of used standards to ST4RT (RS)
13:00 Lunch break
14:00 Next steps ALL
Collaboration Agreements:
AvdE explained that four collaboration agreements are being prepared for the moment. There will be collaboration agreements between each OC project (ST4RT and GoF4R) and each CFM project (Co-Active and ATTRACkTIVE).
He added that the core text will be the same for all the collaboration agreements and that only the annexes will be adjusted depending on the projects involved in the collaboration agreement.
He highlighted that there is an increasing pressure from the S2R JU to sign these collaboration agreements as soon as possible and that there are only a couple of issues left to be addressed in order to come to a final version for the core text. The plan is to circulate two versions (a clean version and one with track changes) by Monday 8th May, in order for them to be signed by all the partners within the following two weeks.
It was also stressed that the annexes have to be completed as soon as possible, because some inputs are required by each of the consortium partners involved in the collaboration agreements. AvdE continued by explaining the content that should be included in each of the Annexes.
InnoTrans 2018:
DS explained that there is the suggestion form the IP4 Steering Committee to use InnoTrans 2018 as a quick win opportunity in order to have a demonstration during that occasion. The implication is that some partners will have to spend extra effort to make this work.
RS pointed out that the main issue is to have the agreement of the potential operators which will be involved,
G A 730822 P a g e 34 | 118
and therefore use their systems and services in order to sell something and consequently decide on exceptions relevant to the use case. There is therefore a commercial risk to this approach, which is not related to the research perspective of whether it can be done.
Since the projects are not meant to develop a ‘real product’ and since companies have not adopted it yet, this will be challenging unless simulated. The ‘real product’ could be available for InnoTrans2020.
Decision: The InnoTrans demo will be discussed during the IP4 TMT meeting on the 15th June in order to provide a preliminary answer to the IP4 Steering Committee on the 20th June. A dedicated workshop should be organised later on in order to look at the details of what such a demonstration entails.
15:30 AOB ALL
There was a general agreement that the first main target of the collaboration workshop should be to have the agreed collaboration tools, like the common repository etc. operational by the 12th May.
Once the RACI tables are completed by all the projects, they will be used for setting up the GitLab etc.
END of DAY 2 at 15:30
Action List
N° Description Responsible Deadline
1 Organise TD4.2 and TD4.3 workshop in May DS 12/05/2017
2 Organise TD4.4 and TD4.5 workshop in May DS 12/05/2017
3 Organise GoF4R workshop in Sep/Oct GdP 31/05/2017
Organise WP Leaders collaboration workshop in coordination with 4 SG and DS 31/05/2017 GoF4R workshop in Sep/Oct
5 Organise ST4RT conference call for standards/converters to be used RS 12/05/2017
Send RACI table used in ATTRACkTIVE to RS and JL as a template to 6 AvdE 08/05/2017 be filled in
7 Create Mantis project for collaboration issues to be shared with all AvdE 12/05/2017
G A 730822 P a g e 35 | 118
N° Description Responsible Deadline
the IP4-related projects and harmonise the tutorial concerning the rules and distribute to all participants
Look into how the appropriate rights could be assigned for the Thales 8 19/05/2017 different projects that will be involved with Capella Portugal
HaCon to create a GitLab for the collaboration purposes of all the 9 AvdE 19/05/2017 IP4-related projects
HaCon to check whether a GitLab could be used as a common 10 AvdE 08/05/2017 repository
11 Upload list of deliverables on GitLab Coordinators 12/05/2017
Co-Active and ATTRACkTIVE to send a list of used standards to ST4RT CFM 12 19/05/2017 (RS) Coordinators
G A 730822 P a g e 36 | 118
4.4 TMT Workshop – WPs 1, 2, 3 (07/06/2017)
Agenda
Agenda items:
o Status of each WP (TS, BT, TT; TC), esp. the status of the specification @WP-Leaders: Please prepare slides for this
o Status of the Reusability / Enhanceability of IT2Rail outcomes --> Presentation of the result from the technCollWork per TD @WP-Leaders: Please prepare slides for this --> Preparation of a statement for IP4 SteCo6
o Processes for
. CoopTool
. Meetings
. official Documents
. Capella vs. Visio vs. PowerPoint
. GitLab
. Capella
. Code
. living documents
. Mantis
. Capella
. Open Issues
. Bugs
o Start of implementation activities
o Preparation of material for IP4 SteCo6
o Next steps & meetings
Attendees List
G A 730822 P a g e 37 | 118
Name Company Status
Tom Jones (TJ) Amadeus A
Leyre Merle Carrera (LM) Indra A
Elvino Monteiro (EM) ThalesPT A
Marco Ferreira (MF) ThalesPT A
Daniel Schmidt (DS) HaCon A
Achim Von Der Embse (AVE) HaCon A
Remi Courtel (RC) DigiNext A (per webex)
Pascal Flauder DigiNext A (per webex)
A (per Fabrizio Cosso (FC) Ansaldo webex)
Minutes of Meeting (MoM)
Time Topic Responsible
13:00 Opening Session ALL
. Round Table . Approval of the Agenda
13:15 Approval of the MoM of 1st TMT HaCon + Thales
13:30 Status of the Projects, esp Specification WP-Leader
. Co-Active – TD4.2 Travel Shopping (HaCon) . Co-Active – TD4.3 Booking & Ticketing (Thales) . ATTRACkTIVE – TD4.4 Trip Tracker (HaCon) . ATTRACkTIVE – TD4.5 Travel Companion (Diginext)
G A 730822 P a g e 38 | 118
Co-Active – TD4.2 Travel Shopping HaCon
G A 730822 P a g e 39 | 118
• Workshop at the 18th May
• HaCon
• AMADEUS
• INDRA
• Thales PT
• Leonardo
• Enriched Functionalities
• JP Orchestration
• New modes
• Influence of Preferences
• Itinerary Validation
• Co-modal Availability and Pricing Optimization
• Failure Cases
• Components
• Mobility Request Manager
• Shopping Orchestrator
• Location Resolver
• Meta Network Builder
• Meta Network Explorer
• Travel Expert Resolver
• Offer Builder
• Travel Expert Broker
G A 730822 P a g e 40 | 118
Co-Active – TD4.3 Booking & Ticketing Thales
AMA
• Meeting between AMA and INDRA
• Who wants to do what?
• How to collaborate.
• internal AMA-Meeting (IT2Rail S2R)
INDRA
• Spec: started
• Actors
• Use cases
• Funcitons
• Components
• TE – new ancillary services (also later booking)
• WIFI
• Lunch
• Others later
Questions
• Orchestrators
• Which are needed?
• Who will build them?
• Which has to been updated, enhanced, rebuild?
G A 730822 P a g e 41 | 118
ATTRACkTIVE – TD4.4 Trip Tracker HaCon
WP1 Planning
• CREL specifications: M-1
• CREL implementation: M-2
WP1 status
• Work focused on
• Analysis of IT2Rail components and Capella Model
• Identification of possible sources for events and analyse possible (generalized) interfaces to integrate events
• Elaborate the distributed Trip Tracker architecture
• Ongoing CREL specification
• 22/05: Technical Collaboration workshop
• Information from IT2Rail regarding TripTracking
• Check if systems or partly systems can be reused (e.g. Tools like ESPER-event correlation engine)
G A 730822 P a g e 42 | 118
• Discussion on proposed architecture including task breakdown
WP1 status - specification
• CREL specifications
• 24/05: Template CREL spec delivered to partners
• 31/05: WebEx CREL spec
• Actors, Use cases, Components, Functions
• CREL specification ongoing on base of WebEx discussion
• 30/06: Deadline for CREL specification
• All partners have contributed their first input to the specification
• Latest distributed version is dated 1st of June with comments from Elvino
• CREL specification is ongoing
• Next version is planned for the 16th June EOB
ATTRACkTIVE – TD4.5 Travel Companion Diginext
WP2 Planning
G A 730822 P a g e 43 | 118
• CREL specifications: M-1
• CREL implementation: M-6
• Software + 2 deliverables
WP2 status
• Work focused on
• Collaboration: analysis of reusability with IT2R partners
• CREL specifications
• 22/05: Technical Collaboration workshop
• Refined reusability from IT2R
• Rough architecture & components breakdown
• Answered many technical questions
• CREL specifications
• 06/06: Template initialised
• TBD: WebEx to refine components breakdown
• Breakdown prepared by each partner beforehand (Actors, Use cases, Components,
G A 730822 P a g e 44 | 118
Functions)
• Several calls? (because of planning incompatibilities)
• 30/06: Deadline
16:00 Technical Collaboration – status and risks WP - Leader
Co-Active – TD4.2 Travel Shopping HaCon
Travel Shopping Architecture
T1.1.1 JP Orchestration
G A 730822 P a g e 45 | 118
T1.1.2/3 new modes
T1.1.4 / T1.2.2 Influence of Preferences
G A 730822 P a g e 46 | 118
T1.1.5 Itinerary Validation
T1.2.2 Availability and Pricing Optimization
G A 730822 P a g e 47 | 118
T1.3.1 Failure Cases
Open points / risks
G A 730822 P a g e 48 | 118
• MRM
• What is inside?
• Can it handle Search Options and Preferences (as Search Options in the MR overrides Preferences from the cloud)?
• Can it handle each new of Preferences if them would follow the structure of IT2Rail?
• What is the structure of json-Format of the MRM-Request and -Response?
• MN
• How to integrate flexible Sharing system (free floating; flexible stations) definition of area
• How to introduce this area into MNB, MNE?
• OB
• Can we split the OB into subcomponents (and make them available)
1. Interface for Request and Response (from SO)
2. Analyse of the mobility request
3. Interface for Request and Response (to TE Broker)
4. (Customize / Pre-Filtering of the TEB results)
5. Building the itineraries
6. Building the offers
1 IO 6 Offer 2 Analysis 5 Itin.
3 IO 4
Co-Active – TD4.3 Booking & Ticketing Thales
G A 730822 P a g e 49 | 118
Quick overview and details were discussed in a later session. Please see below.
ATTRACkTIVE – TD4.4 Trip Tracker HaCon
T2.1 – Architecture
Task Structure (1)
G A 730822 P a g e 50 | 118
Task Structure (2)
G A 730822 P a g e 51 | 118
Next Steps
• Finish CREL specifications
• Specification will be general describing the principle structure
• Definition which functions, components etc. will be developed in CREL (approval of the List discussed on 31st May)
• Begin implementation
• About July after finishing the specification
CREl Content
Content of the CREL was discussed on 31st of May
INDRA :
• Partial Trip Tracker + Event Source: weather (only Madrid??)
• Partial Trip Tracker + Event Source: road (Madrid) -> for future releases, other modes will be added. For the F-REL, it will be a Partial Trip Tracker: Geography Madrid
HaCon:
• TT Orchestrator, but
• hardcoded pTT
• 1 pTT per Travel Episode
• pTT for VBB
• 1st Version AlternativeManager
THP:
• pTT for mobile device sources
G A 730822 P a g e 52 | 118
• Notification of delays based on device position changes validated with user interaction
ANS (tbc):
• 1st Component and Interfaces without algorithm
DXT:
• pTT for Brussels for Bus, Tram, Subway
• Interaction with TC
• Changed from Validation of Positioning Delays (…)
ATTRACkTIVE – TD4.5 Travel Companion Diginext
T2.1 – Architecture
• Extend the Android framework
• Share functionality through new libraries
• Preferences, Communication API, Positioning
• Modular background process
• Usable by all modules
• IT2R reusability mostly defined
• Integration strategy defined (led by HaCon)
• Architecture refinement still needed
• Background process
G A 730822 P a g e 53 | 118
• Communication API
• …
• iOS support
• Framework will follow Android’s architecture
• Some modules ported from Android
T2.2 – Experiences
• LBE Editor specified on its own
• Experiences are bound to specific Travel Episode conditions
• Geographic zone
• Current travel episode properties (length, type, …)
• Time
• Weather
• …
G A 730822 P a g e 54 | 118
• Backend
• Publish/List/Download experiences
T2.3 – Positioning
• Will be handled by libraries
• Shared across components
• Can run in background
• 3 parts
• Sensors data collection
• GNSS, Bluetooth, Wifi, NFC, IMU, …
• Positioning refinement
• Enrich positioning (places/stops detected…)
• Indoor positioning (NavVis…)
G A 730822 P a g e 55 | 118
• Logical Positioning
• Determine the Travel Episode
• Architecture refinement in progress
T4.2 – User Virtual Space
• INDRA will take charge of all cloud-based components
• (incl. IT2R SCNF modules)
• New shared library in PA
• Unified access to preferences
• Data persistence for offline use to some extent
• Work on cloud architecture in progress
• Compatible with commercial cloud offers
• No more VPN needed
• Scalability
G A 730822 P a g e 56 | 118
Next steps
• Finish CREL specifications
• Focus of June must be finished by the end of the month
• Several WebEx to be planned
• Begin implementation
• Share the framework, then each partner can begin on its own
• 6 months to CREL
WP2 technical collaboration
• IT2R only members concerned:
G A 730822 P a g e 57 | 118
• SNCF
• Agreed to give access to source code of modules
• Waiting for date for source code availability, and code documentation (architecture, conception…)
• Leonardo
• Agreed to give access to runnables
• Waiting for information on preferences module conception to know if it will handle new preferences
• Pending actions
• Renew requests to SNCF and Leonardo
• Analyse code & documentation when available
17:00 Process definition ALL
. Meetings o Internal o EUG o AB o S2R . Actions have to be put into MANTIS . Create the meeting at the CoopTool . All documents CoopTool Each „stable“ version Agenda All used / shown documents MoM . EUG, AB Find the audience Find the content / questions
G A 730822 P a g e 58 | 118
. Requirements gathering o Identify the sources o State of the art o Req validation o Req analysis o Cycle? o Specification
. Modelling / Specification / Ontology o Modelling usage of one Capella Model? . Branches . Same model o How to combine the different models from different projects (I2R, CFM, OC)? . Coordination: COHESIVE . Doing: COHESIVE vs. regularly by each project . THP costs of Capella++ o Specification . Analysis of the Reusability and Enhancebility of IT2Rail o Ontology . Define a Glossary . give it to CONNECTIVE for creating the „owl“
. Implementation . Bug tracking o Use MANTIS o Regularly CCB (Control change board) . weekly or biweekly or monthly o Status for Bugs . „resolved“ after bug fixing by anyone, assinging to the Reporter
G A 730822 P a g e 59 | 118
. “Closed” only by the Reporter of a bug o Closing for open issues preferable by consensus; entered by the relevant meeting leader at Mantis
. Test (Test case definition, perform Tests)
. Demonstration (Use Case, perform) o tbd . Deliverables . Dissemination o TRA18 Apr 2018 o InnoTrans2018 Sep 2018 o MidTerm? ??? Shift2Rail o EndTerm? ??? Shift2Rail o Updates for website . Additional content o Newsletter 1
. Collaboration Process (IT2Rail, CFM, OC) . Engineering guidelines COHESIVE
18:00 Next steps and meetings ALL
Next Deliverables
G A 730822 P a g e 60 | 118
Next steps / ToDos
Next meetings
G A 730822 P a g e 61 | 118
G A 730822 P a g e 62 | 118
4.5 Capella Coaching Session – WPs 1, 2, 3 (06/09/2017)
Attendees List
Name Company Status
Maximilien Riguidel (MR) Thales A
Charles Passeron (CP) Amadeus A
Javier Saralegui Sánchez (JSS) INDRA A
Julien Darrort (JD) Thales A
Stephane Bonnet (SB) Thales A
Aurélien Pinsonneau (AP) Thales A Minutes of Meeting (MoM)
After our training session about Capella, we get some feedbacks and actions. Here is a proposal of some points to investigate in order to improve:
Way of modeling with Capella; Clean-up of IT2Rail model to start Co-Active; Collaborative working process; Easy extract of Capella’s diagrams.
Global way of use Overview
Issue: Getting the overview window (after closing it accidentally). This window offers an easy way to navigate in the model.
1. Right click on the project “.aird” and click on ‘Open Capella Overview’
G A 730822 P a g e 63 | 118
Main rules Functions names
One feedback we got from the Capella training was about our description of Functions, names especially. These functions must be described by a verb. Here is an example:
Current Booking scenario
G A 730822 P a g e 64 | 118
Update booking scenario
In our example, which is only an example in order to describe our meaning, we see that the description of functions is improved. This is the “normal” way of using Capella.
Colour conventions:
- Functions: Green; - Components: Blue; - Interfaces: Red; - Implementation Components: Yellow. Use of [ES]
During our session, we discover (for our part) Exchange Scenario. These scenarios are much better than Functional Scenario in terms of system description. These are links from Component to function, with data exchange.
1. It’s possible to extract ES from FS automatically. Right click somewhere in the FS, then click on ‘FS to ES’.
G A 730822 P a g e 65 | 118
2. When it’s done, right click somewhere in the FS, then click on ‘Show in Capella explorer’.
G A 730822 P a g e 66 | 118
Here is our ES
3. Rename it: [FS]L Booking - B&T (ES) to [ES]L Booking - B&T 4. When it’s done, right click “[ES]L Booking - B&T”, then click on ‘New diagram/ES’.
5. Rename it like this
6. Now we get our ES
G A 730822 P a g e 67 | 118
7. The best interest about it is that now we can add our functions inside the ES. We have the link between Component/Functions/Data exchange.
G A 730822 P a g e 68 | 118
Tricks
Validation process
In Capella, it’s possible to check some rules with a kind of validation. It’s a static validation to check some rules defined before.
1. Click on Window/Preferences
2. Then, go to Model Validation/Constraints
Here you can find all rules, and add it to the validation process. But you first have to know what every rules
G A 730822 P a g e 69 | 118
means. See the Help content and see the figure below:
3. Right click somewhere in the FS, then click on ‘Validate model/Validate model’.
Semantic view
The semantic view allows, after clicking on an element + F9, to see all referenced elements related to the
G A 730822 P a g e 70 | 118
element clicked.
1. Open an FS for example
2. Click on an element like “Booking and Ticketing” and press F9
As you can see on the figure above, the semantic view is activated and we got all information related to the function Booking and Ticketing. Metrics
G A 730822 P a g e 71 | 118
When you need to see all metrics of the Capella Model, you can find at:
1. Right click on .aird file Progress Monitoring Metrics
In the figure above, we see all metrics related to our project.
G A 730822 P a g e 72 | 118
Extract from Capella to word
During our session, one aspect of the project was the extraction of information into a word document, like the specification. It’s possible to extract information with “M2Doc”. It will be interesting to use it to extract every diagram we need from the model instead of doing it by hands. Team for Capella
It’s a collaborative process to work in a simultaneous manner. It’s not free software which required a global acceptance by all partners.
This point will be discussed during the TMT Sept 2017. Open points
Version of Capella? o IT2Rail Capella model is working with 0.8.3. It will be interesting to move to the latest one 1.1.2 How to work with Git? Methodology? o EGit is recommended because it works with Eclipse and all the git work could be done in Capella. This point will be discussed during the TMC Sept 2017.
G A 730822 P a g e 73 | 118
4.6 TMT Workshop – WPs 1, 2, 3 (26/09/2017)
Attendees List
Name Company COA ATT
Tom Jones (TJ) Amadeus A
Leyre Merle Carrera (LM) Indra A A
Javier Saralegui Sánchez (JS) Indra A A
Agustín Rodriguez Gallego (AR) Indra A A
Luis Sánchez-Arévalo (LS) Indra A A
Scott Heath (SH) Network Rail A A
Maximilien Riguidel (MR) ThalesFR A (WEBEX)
Julien Darrort (JD) ThalesFR A
Elvino Monteiro (EM) ThalesPT A
Marco Ferreira (MF) ThalesPT A
Daniel Schmidt (DS) HaCon A A
Achim Von Der Embse (AVE) HaCon A A
Remi Courtel (RC) DigiNext A
Jean Claude Denat (JCD) DigiNext A
Fabrizio Cosso (FC) Ansaldo A
Minutes of Meeting (MoM)
Time Topic 10:00 Welcome / Opening Session
Round Table, antitrust statement presented and agenda approved.
10:30 Status of the Projects
G A 730822 P a g e 74 | 118
Time Topic Reminder of the releases name + planning.
There will be 2 major releases, as foreseen in the Grant Agreement of both COA and ATT.
CREL: end of February 2018, with WP3/4 integration activities going on up to end of April 2018.
FREL: end of September 2018, with WP3/4 integration activities finishing in December 2018.
We introduce an internal release (spec+implem) for November 2017, named preCREL, for settling some features in order to adjust (when possible) the CREL contents for better synchronization.
ATTRACkTIVE
WP1 – Trip Tracker
AVDE presented current status and progress of the WP
LM announced that pTT for Madrid will handle at CREL public transport only
ACTION: impact for demonstration at InnoTrans has to been analysed FC highlighted the need for real time data in order to train the prognosis algorithms
ACTION: FC will write an explanation for and description of the needed data.
TJ: Link between TT and TD 4.2 for re-Accomodation and alternatives calculation? Part of ATTRACkTIVE?
AVE: Disruption should be forwarded from 4.4 to 4.5, which will inform the user and may trigger some re- Accomodation.
ACTION for AVDE: Organize a technical workshop in order to finalize the interface definition between the Orchestration partial TripTracker Event Sources planned for the week of 23rd of Oct. (one day); an additional day will be reserved for Travel Companion
WP2 – Travel Companion
RC presented current status and progress of the WP
OPEN POINT: Do we want to have the source code for the application on a SVN / GIT Server?
DECISION: All open issues explicitly those mentioned in the specifications should be entered into Mantis (2017- 10-04: done for TT).
G A 730822 P a g e 75 | 118
Time Topic CoActive
WP1:
DS presented current status and progress of the WP
Question concerning interfaces TS-B&T / IF / TSPs :
- TSP should provide capabilities, exposed through the IF.
- Co-Active has to determine which capabilities are expected from a TSP for full compliance with the ecosystem. For TD 4.2 (& 4.3) to demonstrate the new features, Travel Experts (TSP) will be enhanced with those capabilities.
Question about need of IF between TDs (ex TD 4.5 / TD 4.2 / 4.3) Not within CoActive / Attracktive, but yes for further calls.
Travel Experts can be a Travel Expert Manager that offers “intermodal” itineraries. Could be difficult for them to produce GTFS data.
Concerning CMMP: This component is defined and implemented within TD4.2 (TS), but it will also be required for TD 4.3 (B&T).
OPEN POINT: Where in the ecosystem will be implemented rules that will allow the control of whether a TSP accepts to do business for a specific retailer (or travel agency), and vice versa? Would that be in the CMMP, in the IF?
WP2 :
MR presented work package status.
This WP suffered of a slow start, which is being revitalized since this summer. Preliminary work was done during last workshop in September in Velizy (France). “Task Description” document has been committed to the CoopTool in order to start the WP2 specification with all knowledge from partners.
13:00 Lunch Break
14:00 Technical Collaboration
G A 730822 P a g e 76 | 118
Time Topic Topics :
Release Planning Engineering activities - Capella (vs IT2Rail, upgrade, process…) Preparation for the Integration - Environment, Strategy, planning - Form of results Brainstorm on InnoTrans demonstration
Engineering activities - Capella
Decisions:
Usage of Capella as the engineering tool for COA and ATT system design is validated by both consortia.
There will be one common Capella S2R model for COA and ATT, based on IT2Rail outputs.
Since IT2Rail is still ongoing, and to avoid complicated merges, the following organization is agreed:
- Phase 1 : from now to end of 11/2017 COA and ATT system design activities will be done using temporary tools like VISIO /Power Point/Local Capella model, independently from the IT2Rail Capella model. (work done there will be reintegrated in Capella S2R during phase 3)
- Phase 2 : (12/2017) The IT2Rail Capella model will be retrieved and upgraded to release 1.1.2 Some consistency checks will be performed.
This work will be done by Thales FR => Model migration from 0.8.3 to 1.0, then 1.0 to 1.1.2
All partners will have to install the Capella Client version 1.1.2 (information: Should run on Apple iOS as well)
.
- Phase 3 : (01/2018)
G A 730822 P a g e 77 | 118
Time Topic All system design works done previously within COA/ATT will be reintegrated in the upgraded Capella Model (to be done by each partner, detailed process to be defined)
- Phase 4 : from Feb 2017 Business as usual.
OPEN POINT: Coaching for Capella 1.1.2 in Dec or Jan or both?
OPEN POINTS:
- Team for Capella is an extension from “Obeo” provided under licensed fees that allows simultaneous access and work on the Capella model. It consists of a centralized server that hosts the models and manages collaboration. All Capella clients will have to be connected to the server to retrieve the model and inform of ongoing changes. - Action: JD: explore further the possibilities (pricing, technical solutions), with the help of Thales PT
InnoTrans
Will be held in Berlin, mid-September 2018.
Is the opportunity to show IP4 work done so far, on top of IT2Rail?
The need (or interest) of having “end 2 end fully operational” demonstrations can be challenged. It might be more efficient to focus on key features, even with partial implementation.
The responsibility of COHESIVE toward the event coordination is discussed. This will have to be clearly defined after COHESIVE kick off.
In the meantime, next step actions taken by COA/ATT :
Action JD/DS: discuss with the JU the frame of the event for S2R/IP4 (space, format, timing, expectations). Define more precisely within each project the use cases that could demonstrate the projects outcomes and IP4 objectives (new functionalities on top of IT2Rail). Action JD: Schedule a synchronization call to share ideas (IP4 CFMs COA/ATT/CON/COH) by end of October
G A 730822 P a g e 78 | 118
Time Topic Integration
This topic aims at preparing the integration activities, expected to start end of the year for the CREL, and to define the needs in term of “environments” (platforms).
Discussions about the overall integration strategy, structured in 3 (+1 for Cohesive) layers, summarized in the slideware.
Concerning outcomes of the implementation, it is noted that sample data produced by components should be made available to components that may require them for their unit testing activities.
Discussion about the environments (which can be also called “Platform”) required by both projects : 3 levels of environments considered
- a/ Development environment, hosted and for use by each partner for the components they are implementing. This environment does not necessary have to be connected to the others, because it will be used for component level testing, and not for integration activities
- b/ Integration and maintenance environment: This environment will support integration activities at WP and project levels. The possibility of hosting all components under a same network (LAN) / Cloud infrastructure is discussed, but ruled out.
- “Production / Stable” environment: This environment corresponds to the environment that will host TDs components that have been successfully validated and integrated (at all levels, including COHESIVE’s). It addresses the need of a stabilized environment that can be used for IP4 demonstrations activities. That environment could be under the responsibility of COHESIVE (to be further discussed after project kick off).
All consortia agreed on the interest of having 2 platforms (a/ and b/) for each projects, but the feasibility will have to be instructed by each partner.
It is reminded that IT2Rail environment will most likely be kept “untouched” until the TRA 2018 event, in order to guarantee their demonstration.
G A 730822 P a g e 79 | 118
Time Topic Actions:
- All Partners : Each partner contributing to TD developments has to study the possibility of having an instance of their component in a dedicated environment for COA/ATT Integration & testing (independent of IT2Rail)
The environment c/ (production/stable) will be discussed later together with COHESIVE.
17h15 Next steps and meetings
Next Meetings
- Next TMT / SC : o TMT + preAB: 4th & 5th December in London, together with COA/ATT/CON/COH o TMT+SC: 6th, 7th & 8th March in Lisbon, TMT + SC for COA/ATT/CON/COH.
- Next Workshops: o COA WP1 & 2 : 15 & 16 November in Bruxelles o ATT WP1 & 2 : mid-October (16-18?) o Integration Workshop : to be clarified with COHESIVE
- IP4 Collaboration Workshop : not planned
18:00 AOB
19:00 The End
G A 730822 P a g e 80 | 118
4.7 Collaboration Workshop – S2R COLA Info My- TRAC cooperation (09/11/2017)
Attendees List
Due to internal issue, no attendees list was issued. Mainly, CoA, ATT and My-Trac partners assisted to this workshop Minutes of Meeting (MoM)
Due to internal issue, no MoM was written for this meeting.
The content of the meeting was a description of My-Trac Work Packages, and their initial ideas. Therefore, CoA and ATT partners described their activities.
Participants also discussed the possible overlaps of the projects and how these projects could be complementary in the future.
G A 730822 P a g e 81 | 118
4.8 TMT Workshop & Pre-Advisory Board (04/12/2017 and 05/12/2017)
Attendees List
Status Day Status Name Company 1 Day 2 Scott HEATH (SH) Network Rail A A
Colin BROWN (CB) Network Rail A
Robbie GENT (RG) Network Rail A A
Paul BOWDEN (PB) Rail Delivery Group - A
Leyre MERLE (LM) Indra A A
Tom JONES (TJ) Amadeus A A
Achim VON Der EMBSE (AVDE) HaCon A A
Daniel SCHMIDT (DS) HaCon A A
Maximilien RIGUIDEL (MR) ThalesFR A A
Nihad BAHRI (NB) ThalesFR A A
Stephane LORIN (SL) ThalesFR A A
Joao MIRA (JM) ThalesPT A A
Marco FERREIRA (MF) ThalesPT A A
Rémi COURTEL (RC) DigiNext A A
Eric VELAY (EV) DigiNext A A
... …
Connected via WebEx
Fabrizio COSSO (FC) ANSALDO
G A 730822 P a g e 82 | 118
Status Day Status Name Company 1 Day 2 Marcus DE PAZ (MdP) BOMBARDIER
… …
A: Attended – E: Excused Minutes of Meeting (MoM) – Day One: Technical Management Team Meetings
Nihad 10:00 Co-Active (ThalesFR)
After a brief presentation about Co-Active main aim & expected results, an update about project’s & deliverable’s status was shared.
Under Co-Active scope, a Capella Coaching Package was negotiated with about 5 sessions. Due to the S2R-IP4 projects common progress, Co-Active team proposed to offer S2R-IP4 partners the opportunity to attend these coaching sessions (proposal can be extended for OC partners). One session was already held during September 2017 and a second one (1 or 2 days) will be held by the end of January or the beginning of February (depending on Capella Trainers and S2R-IP4 Partners availabilities). Action (Co-Active): ThalesFR will propose some dates and partners will share their preferences. Indra suggested allowing WebEx remote attendance. ThalesFR will provide a WebEx remote connection and recommends a physical attendance especially for practical course in order to ensure efficient training.
Under Co-Active subtask 5.3.2 – Public sharing; Co-Active partners will write and publish three articles to communicate on the first outstanding results in specialized magazines. This subtask was identified as a common one with ATTRACkTIVE 4.3.2 subtask. Action (Co-Active): Thales FR proposed to identify projects sharing this common subtask and collaborate together on these subtasks in order to write common S2R-IP4 articles.
A potential collaboration was identified between Co-Active WP3 – Business and Contractual Management and the Co-Active WP1 section “Contractual Management Market Place” leaded by Indra. Action (Co-Active): The WP3 specification will be shared with Indra and interested partners.
During the discussion the following question occurs: How to manage the relationship between Travel Experts / Travel Service Operator and Resellers/Aggregators, meaning which Reseller/Aggregator is allowed to use/call which service and date from which
G A 730822 P a g e 83 | 118
TE.
A Co-Active WP1 brief technical presentation was shared and animated by DS.
A question was raised about Co-Active B&T orchestrators (Booking & Issuing) that were managed by Amadeus during IT2Rail project and should be redeveloped under Co-Active scope (Constraints inherited from IT2Rail and initially not a part of a Co- Active scope). The question was about the plan and the time needed to manage the development of these orchestrators and then new After-Sales orchestrator. Action (Co-Active): Partners that will potentially manage these tasks; HaCon (Booking orchestrator) and Indra (Issuing & After-Sales orchestrators) will share the details about the plan and the time needed to manage these tasks by the beginning of January.
11:00 ATTRACkTIVE Daniel (HaCon)
TD4.4 Trip Tracker Main issue has been to define the API between Tracking Orchestrator and partial Trip Tracker. It has been worked out that standard APIs like SIRI, TRIAS and OJP cannot be used for our purposes. Therefore it has been decided to develop a lean specific API that fits perfectly to our needs. Actions (ATTRACkTIVE): Finalize the API TO <-> pTT (most urgent) The architectural position of the Smart Device as an Event Source must be clarified Answers to the open questions of the specification must be entered into Mantis. Specification must be finalized within December Proceed development of TO, specific pTT and ES and Prognosis by all partners
TD4.5 Travel Companion Status: Android framework together with the specification of it is available to begin integration of modules that are being implemented separately by each partner. First version of the iOS framework and documentation is available to begin development of modules for FREL. The Cloud Wallet is also operational and the full API description was distributed. The new version of the specs is still pending and needs to be distributed ASAP.
Action (ATTRACkTIVE): Preparation and circulation of a new version of the specification.
General Main remaining open issue: There is a gap between ATT and CoA regarding the shopping and booking modules. HaCon proposes to study the source code from IT2Rail (SNCF) as soon as it is made available and see to what extent they can reuse it and how much effort this represents. Even source code from SNCF would be available it is not planned to generate real calculated itineraries. To test the system static
G A 730822 P a g e 84 | 118
values have to be used.
Action (ATTRACkTIVE:
HaCon is analysing the source code of SNCF and will decide if it can be reused for Shift2Rail
A corridor should be defined and aligned by all projects to demonstrate the system
Action (COHESIVE): Definition of the InnoTrans and FREL Corridor.
12:00 CONNECTIVE Leyre (INDRA)
Presentation of on-going works: in WP1, Indra is deploying IT2Rail-WP1 components in own servers and working in the proposal of the architecture. Planned to have them running by end of January, to start then the integration of new TSP and with other IP4 projects.
In BA, Indra and Thales are making contacts with potential collaborators that could provide data.
Action: Collaboration identified with ATT- mobile sensor, regarding GDPR
Action (CONNECTIVE): Workshop could be organized with Leonardo after next week workshop.
PPT available in CONNECTIVE Coop. tool with the name: S2R-CON-WP5-IND-01-00 slides TMT
14:00 COHESIVE Joao (ThalesPT)
The project setup and evolution status was presented. It was explained the transition process being followed between IT2Rail and COHESIVE that is being followed.
Actions (COHESIVE): A combined planning covering the CFM projects will be done to try to synchronize tasks and outcomes. The partners will need to complete the RACI table to guarantee the adequate access to the cooperation tool.
The deliverables planned have a slight delay. D7.1 and D7.2 will be shared with the partners on the next two weeks and D1.1 a little later, in the beginning of January. Action (COHESIVE): Target is to have the deliverables concluded by the end of January.
Interfacing between CFMs to guarantee consistency and alignment: The functional
G A 730822 P a g e 85 | 118
requirements will be based on the use cases defined.
Action (COHESIVE): TD leaders in the different CFM projects will update functional requirements to be later reviewed and consolidated in Cohesive.
Interfacing between CFM and OC: CFMs will interface directly with the corresponding OC. Cohesive will be kept updated for consistency and coherence checking.
Action (COHESIVE): Set up of the Cooperation Tool.
15:00 COMMON All
New Capella trainings/workshops will be organized by ThalesFR. Suggested to allow also WebEx connection.
The synchronization of common actors/roles between S2R-IP4 projects was discussed. S2R glossary definitions will be shared by all S2R-IP4 projects.
The macroscopic following cross-project (cross-TD) dependencies were identified:
Two questions were raised about cross-project dependencies: The first one regarding the availability of Co-Active orchestrators for ATTRACkTIVE results validation. The second one regarding the availability of CONNECTIVE interoperability framework for Co-Active results validation. Indra confirmed that CONNECTIVE interoperability framework will be available by the end of January or the beginning of February, for S2R-IP4 integration (communication with S2R-IP4 Travel Experts).
The options for the Capella Tool were explained. Decision to move for the “Team for Capella” version having server and virtual machines hosted in the same physical server in the premises of a partner.
Action (COHESIVE): Diginext and ThalesPT will analyse who could host Capella.
TRA2018 & Mid-Term Event potential communication plans were exposed as follow:
G A 730822 P a g e 86 | 118
TRA2018, April 16th – 19th: o IT2Rail (19th): Demonstration, Presentation + Workshops o ATTRACkTIVE: Speech o Co-Active: potentially Poster presentation Mid-Term Event, April 20th (Mainly Co-Active and ATTRACkTIVE) – 4h of presentation + 2h of networking workshops: o Plenary with presentation sharing the results o Workshops including interaction with stakeholders – possible parallel workshops running (per TD) The JU can help promoting the event (newsletter, other means) once the appropriate info is provided. Action (Co-Active and ATTRACKTIVE): fine planning of the Mid-Term Event (logistics, agenda, audience, …)
Description of the current status and composition of the task force working on the preparation of the demonstration in InnoTrans.
Action (COHESIVE): Rui LOURENCO (leader of the InnoTrans process) will send an updated version of the use cases under analysis. A WebEx meeting will be scheduled by Rui LOURENCO before the end of the year to discuss and approve the interactive live demos use case scenarios (and what technical new features to include), approve the project plan and discuss additional practical aspects that need to be taken into account during the InnoTrans exhibition. A workshop was planned to be held on January 15 at ThalesFR premises on Brussels, in order to work on InnoTrans use cases design.
Under IP4 Overall Implementation Plan; Thales FR proposed using of a common integration environment (e.g. remote public cloud: Azure, OVH… or local project cloud hosted by COHESIVE), where each partners expose his results (services) in order to make COHESIVE mission easier (avoid partner’s availability problem, avoid partner’s network firewall & security constraints…). Thales FR will expose the software components developed by them under a remote public cloud. Some partners are not agreeing with this proposal for their scope because of confidentiality and privacy concerns.
Interfacing between CFMs/TDs Actions:
TD leaders will update and complete the information about interfaces and relationships between TDs/components. DS will verify and consolidate the information
Action: It was decided to create under the space of Cohesive in the cooperation tool a space to host a common repository of documentation of IP4.
G A 730822 P a g e 87 | 118
A similar folder will be created on the private space of Cohesive on the cooperation tool covering information relevant to the OC (accessible by their coordinators). The source code coming from IT2Rail will be transferred directly from the originator partner in IT2Rail to the destination partner in S2R/IP4. The same process will apply for source code transfer between consecutive and related CFM projects.
Open issue: Still to be decided: where will be hosted executable code generated by partners that will leave a project after it ends (e.g. OLTIS, Leonardo)? Marco suggested creating a communication platform to facilitate and optimize cross TD integration.
Administration (all CFM)
Each coordinator should be informed about the consumption of real and H2020 budget.
All projects should use the “administrative” part of the Cooperation Tool and should add intermediate periods in order to ease the reporting.
Actions (all CFM):
Activation of the “administrative” part of the Cooperation Tool Set up of intermediate periods (with the help of CNC, contact: Paolo UMILIACCHI 16:00 Pre AB preparation Review agenda and contents AOB Review of 2017 activities in Co-Active and ATTRACkTIVE: the JU informed us informal, that the review meeting of the Co-Active and ATTRACkTIVE for 2017 will be (most probably) a remote meeting.
Action (Co-Active + ATTRACkTIVE): To inform all partners after an official announcement of the JU. Minutes of Meeting (MoM) – Day Two: Pre-AB Workshop
09:30 Capella Modelling Tool All The team discussed Capella, the licencing required, and server requirements.
It was agreed that both NR and Amadeus would have half licences for reviewing
purposes; all other partners would have full licences.
The means of hosting the Capella model could not be agreed, as there are multiple
G A 730822 P a g e 88 | 118
approaches. Thales PT agreed to provide options after further consultation with the necessary internal team.
Coaching sessions would be set up by Thales Fr
Survey Results Review 09:45 The team was invited to review the responses of BT and the RDG, and also assess the current format of the questions.
Q Comments about Survey
1 This question was viewed as being beneficial for introduction to the topic area
2 The team were happy with this question.
KBG highlight the need to discuss the interfaces, along with the distinction between ‘Open Data’ and ‘Open Services’.
3 It was queried how a person could filter by Transport Mode – would you use the element with the longest leg, for instance?
It was also noted that flexibility of tickets/legs may also be a factor missing.
We may want to enable filtering by flexible/open tickets.
4 Considerations around Brand Value are also missing in the question. Introductory text recommended.
5 CB raised questions about the influence of disability data and GDPR.
6 Comments were received about the value of augmented reality in the process of planning or taking a journey.
7 It was noted that advertisers were missing from this question.
9d It was discussed whether people would be automatically re- accommodated i.e. would they need to provide their consent for this?
10 The “as described above” element was viewed as being
G A 730822 P a g e 89 | 118
superfluous.
At the top of the survey, organisation needs to be added. There were comments about the need to consider finance.
GEN There was a discussion about making elements screen readable. AVDE responded that this is a normal element of the skins applied to front end of the system.
18 It was generally felt that much more information would be needed to make this question understandable. Recommended to remove.
19 Semantic approach should be clearly defined in the glossary.
21 Discussion around the need to understand 3rd party selection and the level of reward.
22d There were some queries raised about the aim of this question and whether it was providing value.
25a Rouge apostrophe.
General Observations:
Value of what we are doing was reaffirmed with the early questions in the survey;
With only 2 responses, it is hard to make clear decisions from the data set.
There was support from the RDG for the sharing of data across modes and outside of their realm of control, if it generates clearer business intelligence. We also had some answers that were unexpected and clarifying.
Advisory Board 13:00 A discussion about potential attendees too place. Suggestions included:
The Rail Delivery Group
GoEurope
IT2Rail AB members
G A 730822 P a g e 90 | 118
SilverRail
TrainLine
Operators and other IMs
European Passengers Forum
European Disability Forum
There was also discussion about the difference between technical input and business input, with the AB needing to have clarity around which ambition it has.
It was agreed that a sceencast / recorded WebEx would be a good piece of introductory material to share with the AB members. This would then reduce the amount of background information needed on the day.
Discussion with RDG 15:30 A Q&A type session was held with the Rail Delivery Group’s ticketing expert.
A highlight of the discussion points includes:
The Rail Settlement Plan is used to apportion rail fairs in Britain. This means that all revenue, irrespective of the initial retailer, is passed to a central repository where it is then distributed to the TSP (Rail).
There are non-UK retailers operating under these rules, but it a “painful process”. SeeTrip recently signed up, but it took a long time.
Certification (which is necessary to sell tickets) is performed by the RDG. They offer an in-house service but some organisations (e.g. TrainLine) have their own means of completing most of the work.
There are some examples of combined tickets. PlusBus was mentioned, which uses the same redistribution system as standard rail tickets. There is also a Great Western Railways example where flights are combined with air, but this is done from the air side and not railways.
Due to the redistributive nature of the RDGs system we may not need to integrate into the legacy system but instead emulate what they currently do.
Commission is currently a barrier to encouraging TSPs supporting retailers
G A 730822 P a g e 91 | 118
selling tickets, as they can charge 5% on any 3rd party sales.
MAAS is a goal for the RDG
We would have RDG support for an InnoTrans Demonstration in 2020.
Other Actions 16:30 SH: Asked to relaunch the survey with the amendments discussed. Look at creating a condensed version of the survey, with a focus on interesting areas for the AB.
DS: Asked to make preparations for the recorded WebEx – a scheduled meeting was put in the diary to do this (16th Jan)
Thales PT were asked to make the arrangements for the next TMT in March
Thales FR were asked to make the arrangements for Capella Training
G A 730822 P a g e 92 | 118
4.9 Collaboration Workshop – IP4 CFM meets IT2Rail (14/12/2017)
Attendees List
Name Company Status3
Achim von der Embse (AvdE) HaCon A
Catherine Bignotti (CB) Amadeus A
Catherine Minciotti (CM) Leonardo Company R
Daniel Schmidt (DS) HaCon A
Edouard Carpentier de Changy (ECdC) Thales A
Elvino Monteiro (EM) Thales Portugal A
Eric Volay (EV) Diginext R
Florian Briy (FB) Amadeus R
Gabriel.Virette (GV) SNCF A
Guido Mariotta (GM) Leonardo Company E
Habib Deriu (HD) Indra R
Houssem Chaabane (HC) SNCF A
Javier Saralegui (JS) Indra A
Joao Mira (JM) Thales Portugal E
John Lutz (JL) UIC A
Kamila Mestická (KM) Oltis Group A
Leyre Merle Indra E
Marco Ferreira (MF) Thales Portugal A
Matthieu Peteraux (MP) Diginext R
3 A: Attended, E: Excused, R: Remotely
G A 730822 P a g e 93 | 118
Name Company Status3
Maximilien Riguidel (MR) Thales A
Nihad Bahri (NB) Thales A
Nora Winninger (NW) SNCF A
Petr Buchníček (PB) Oltis Group E
Petra Juránková (PJ) Oltis Group A
Rémi Courtel (RC) Diginext A
Riccardo Santoro (RS) Trenitalia A
Stefanos Gogos (SG) UNIFE A
Stéphane Lorin (SL) Thales A
Scott Heath (SH) Network Rail E
Tom Jones (TJ) Amadeus A
Minutes of Meeting (MoM)
Time Topic Responsible
09:45 Opening Session Stefanos (UNIFE)
SG welcomed the participants to the 2nd IP4 Collaboration Workshop and explained that the ST4RT Advisory Board platform will be used, as it was done for the 1st IP4 collaboration workshop in May. He explained that the first day will focus on the outcomes of IT2Rail and the transferability to Shift2Rail; therefore that’s why only WP leaders of IT2Rail and coordinators of CFM projects were required. He then added that the second day of the workshop will focus more on the collaboration between CFM and Open Call projects.
The agenda was then introduced by SG, which was slightly modified to anticipate the discussions of TD4.4 and TD4.5, due to RC not being able to stay in the afternoon. The rest of the agenda was approved and SG suggested roundtable introductions so that everyone is aware of each participant’s role in the different projects.
10:15 TD4.3 IT2R WP3 Leader
G A 730822 P a g e 94 | 118
(THALES FR)
Nihad (TFR)
ECdC showed component analysis of WP3. He explained that a Service Level Agreement will be needed (pointing out what is available, who will be the contact point, explain if and how the service be maintained etc.). He then added that this is due to the fact that it would be expensive to have a server running 24/7 when it is only being called once a week.
Who is triggering booking orchestration? Does it need a certificate?
CB: Web services are available, but they need to link to Amadeus services.
Action: Amadeus to give procedure to be followed and provide the end point of the service.
DS: Different versions of ontologies will be used (until September)
TJ: publishing services could be possible, but tricky
NW: call to TSP will be available, but interchange can be updated though. Therefore, if there is an update in the API and services are not updated it could be a problem.
Action: NW to investigate possible cost of this and see whether a solution could be found in the future with S2R (possible funding etc.).
TJ: due to updates of APIs and services, this will have an impact on IP4 in terms of possible new annotations, new publications that need to be developed etc.
The participants then went through the TSP table and their reusability of the Travel Experts in IP4.
IT2R WP4 Leader 11:00 TD4.4 (Oltis Group) Achim (HaCon)
PJ presented the 6 components of trip tracking. She explained that there are currently some issues with “update patterns” of tracking activation and some other issues with the events listening, which will be solved asap.
She then explained that the API documentation of WP4 services will be provided. The source code will not be shared but will provide access rights according to GA and CA.
CM clarified that as long as someone can access Leonardo servers, it is not a problem to access the available
G A 730822 P a g e 95 | 118
services.
PJ continued by mentioning that if there is a bug in the system or change needed in the API, it is not clear at this time who will be responsible to make the update.
AvdE then showed how the IT2Rail trip tracker architecture was split into layers for IP4 purposes.
IT2R WP5 Leader 11:30 TD4.5 (SNCF) Rémi (Diginext)
RC presented what they want to do within ATTRACkTIVE in terms of the travel companion and went through the TC PA modules.
The participants then went through the IT2R components table for WP5 and what will be available to IP4.
It was clarified that the SNCF Tapping Module source code will not be shared. That being said, the Tapping Module Manager and Tapping Module Library will be shared.
Decision: As a general rule, the source codes for all WPs will be attached to the software components pack deliverables that will be submitted to the EC.
Action: NW to check within SNCF whether the TC cloud wallet will be shared.
RC wanted to know how configurable is the preference management of Leonardo, to which CM clarified that nothing is configurable.
Action: Guido Mariotta to clarify if at least the list of cities can be made configurable.
IT2R WP2 Leader 12:15 TD4.2 (Amadeus) Daniel (HaCon)
DS presented the Travel Shopping Architecture and JS showed a slide on the contractual management market place.
TJ suggested of having a generic contract to which TSPs could subscribe.
MR wanted to know which solution Amadeus will provide in terms of payment, since this was simulated in
G A 730822 P a g e 96 | 118
IT2Rail, to which TJ pointed out that Co-Active is not addressing customer payments.
IT2R WP1 Leader (Trenitalia) 14:00 TD4.1
Leyre (INDRA)
RS explained the architecture of the broker and how a new TSP comes online. He then explained that WP1 will share everything including source code. S2R should then be able to select which features need be used. He then highlighted though that smart services should be given by the companies that own the interface (jars owned by TSP providers).
RS then questioned whether the network statistics data is just an Amadeus specific requirement or a real IT2Rail requirement.
DS pointed out that a specific session has been scheduled to discuss on how this should be dealt with in Co- Active.
RS suggested that next time there is a new stop place; it would be preferable to include it in the graph as a global ID.
JS showed a slide from Connective point of view on IT2Rail components.
RS then mentioned that the events source resolver has been replaced by the Navizia decoder.
JS continued by showing a slide about the travel experts that have been updated.
Decision: A workshop at the beginning of 2018 would be beneficial for demonstrating how to integrate a new TSP.
IT2R WP6 Leader 14:45 TD4.6 (LEONARDO) Stephane (TFR)
CM explained the WP6 components.
She then clarified that the social network KPI is based on real data.
SL had a question about the data that has been used in IT2Rail, which will be reused in S2R to perform tests.
G A 730822 P a g e 97 | 118
CM explained that the TSPs did not give to WP6 any data, it had to be “invented” in order to make test strategies, send travellers around Europe and analyse something.
TJ wanted to know if the KPIs are static, to which CM pointed out that the queries are predefined and that the data is static.
TJ wondered which the TSP-inspired KPIs are and whether WP6 looked into that, to which CM clarified that it hadn’t.
RS mentioned it’s difficult to get this data from TSPs. Try to get the data out of the cloud, since it doesn’t belong to the TSP. TSP’s are not only reluctant to give this information, but they also have completely different interfaces.
TJ: if TSP’s get something from the KPIs like passenger flows, they would have an incentive to share their data.
IT2R WP7 Leader 15:30 TD4.7 (THALES PT) Joao (THP)
Regarding WP7, there is no direct re-use of components but re-use use cases, since Thales PT is continuing to be involved with the CFM projects.
EM stressed that the main goal is to identify the missing functionalities fast and take into account lessons learnt for the CFM projects.
Common things
Access to IT2Rail TSP services 16:30 ALL Capella: When the final clean IT2Rail model will be done?
…
MR mentioned that S2R will re-use the IT2Rail Capella model as a library and then create a new Capella model for S2R. He then wanted to know if the Capella model in line with specifications and, if not, he pointed out that there is time until the 8th January in order to fix it.
WP1 has finished with Capella updates
WP2 has finished with Capella updates
G A 730822 P a g e 98 | 118
WP3 has finished with Capella updates
WP4 needs to do some changes (before end of year).
WP5: EcdC: had to take the diagrams at some point to use in the specifications, so there will be some discrepancies, but these will be updated through ATTRACkTIVE and Co-Active.
WP6: Guido to confirm if the model reflects the F-REL specifications, but WP6 does not plan to do any further updates.
Action: EcdC to prepare a first draft for a Service Level Agreement template to be used for access to IT2Rail TSP services (to be included within software component packs of each WP delivering services).
Decision: Source Code handover within software component packs of each WP
DS highlighted that all mantis issues should be closed before the end of IT2Rail, and if not, need to check the implications this will have for S2R.
AOB
Synchronization of TRA18 (information about planning) 18:00 ALL IT2Rail: final event, including demo, pilot and video
S2R: midterm event, speech, poster
DS mentioned that on the 20th April there will be the mid-term event of Co-Active and ATTRACkTIVE (6 hours in total) and that there will be a common part with Connective and Cohesive.
SG thanked the participants for coming and closed the meeting.
END of DAY at 19:00
G A 730822 P a g e 99 | 118
4.10 Collaboration Workshop – IP4 CFM meets IP4 OCs (15/12/2017)
Attendees List
Name Company Status
Nihad BAHRI (NB) ThalesFR A
Achim VON Der EMBSE (AVDE) HaCon A
Javier SARALEGUI SANCHEZ (JS) Indra A
Stephane LORIN (SL) ThalesFR A
Elvino MONTEIRO (EM) ThalesPT A
John LUTZ (JL) UIC A
Ismini STROUMPOU (IS) AETHON A
SANTORO RICCARDO FSItaliane A
Kamila MESTICKA OltisGroup A
Connected via WebEx
Josep Lluís Larriba Pey – Larri (JLLP) UPC A
Daniel JOHNSON (DJ) UNIV LEEDS A
Rui LOURENCO (RL) ThalesPT A
Rémi COURTEL DigiNext A
A: Attended – E: Excused
G A 730822 P a g e 1 0 0 | 1 1 8
Minutes of Meeting (MoM)
Nihad 09:15 Co-Active (ThalesFR) . After a brief presentation about Co-Active main aim & expected results, an update about project’s & deliverable’s status was shared.
. Co-Active WP3 – Business and Contractual Management: Contractual Management/Terms and Conditions, was identified as a Key challenge to allow the go live of the Shift2Rail “one- stop-shop”. A potential collaboration was identified between this WP and the Co-Active WP1 section “Contractual Management Market Place” leaded by Indra. Some OC partners were, also, interested to hear more about these two tasks. Action (Co-Active): The WP3 specification will be shared with Indra and interested partners.
. The following macroscopic cross-project dependencies were shared:
Those cross-project dependencies lead to an inter-projects collaboration. - Availability of ATTRACkTIVE components for Co-Active results validation, and vice versa. If not a components emulation si possible. - Availability of CONNECTIVE components for Co-Active results validation. - Availability of Co-Active, ATTRACkTIVE and CONNECTIVE components for COHESIVE results validation. No Collaboration Agreements needed between CFM Projects.
PPT available in Co-Active Coop. Tool with the name: S2R-IP4-COA-WP4-THA-01- 0_Collaboration-Workshop_CFM-meets-OC
Achim 09:35 ATTRACkTIVE (HaCon)
G A 730822 P a g e 1 0 1 | 1 1 8
Javier 10:05 CONNECTIVE (INDRA) . After a brief presentation about Connective main aim & expected results, an update about project’s & deliverable’s status was shared.
. The following Complementarity with other Shift2Rail projects was shared:
. Connective WP1 – Interoperability Framework:
1.1.1 Ontologies and semantic model Analysing with IT2RAIL ontologies (Fraunhoffer repository) Analysing IT2RAIL DB graphs (Leonardo server) 1.1.2 Architectural principles and requirements Analysing IT2RAIL architecture Installing IT2RAIL-WP1 resolvers in own servers (Azure cloud) Proposing new paradigms: microservices, etc.
According to D8.5 all components and assets are non-proprietary and can be used in S2R.
. Connective WP2 – Business Analytics:
G A 730822 P a g e 1 0 2 | 1 1 8
2.1, 2.2, 2.3 & 2.4 Analysing IT2RAIL components and data produced, what to re-use 2.3 Understanding Business needs and use cases built inside IP4 ecosystem (CoActive & ATTRAkTIVE) 2.4 Identifying data sources / Stakeholders Treating data regarding GDPR (General data protection regulation) Cartography of data produced in IP4 Data typology x Use cases Which kind of anonymization Start with real data Generating “realistic data” based on existing and available data
INNOTRANS: As GDPR will be operational in May 2018, the plan is to propose for InnoTrans some demonstrator regarding how privacy will be treated
. The following macroscopic cross-project dependencies were shared:
PPT available in Connective Coop. Tool with the name: S2R_CON_WP4_IND-01- 00_Collaboration-Workshop_CFM-meets-OC (https://www.cooperationtool.eu/projects/goto.aspx?p=CONNECTIVE&doc=142288b8-c0a1-
G A 730822 P a g e 1 0 3 | 1 1 8
4d1f-85c2-73f4e71fbd1e)
Elvino 10:25 COHESIVE (ThalesPT)
John 10:35 GoF4R (UIC)
Ismini 10:50 My-TRAC (AETHON) My-TRAC project just started so the progress status is not advanced, hence the My-TRAC idea was presented and potential cooperation with other S2R projects was identified.
Key words:
Happiness Optimization
transport services platform
users and operators behavioural and transport analytics
artificial intelligence
pilots
G A 730822 P a g e 1 0 4 | 1 1 8
Progress status:
Introducing Travel Happiness as the objective of passengers’ choices
Scheduled and progressing on data acquisition through questionnaires (2000 questionnaires+60-80 in-depth interviews in 3 countries)
Continuous discussion with rail operators we want them involved from early on
NEXT STEPS
Questionnaire survey will be performed on January-February 2018
Data collection from other data sources (not related to user) starts November 2018
Programming of the application will start on February 2018
My-TRAC potential cooperation with ATTRACTIVE was mentioned
My-TRAC potential cooperation with GoF4R with exchanges of good practices and knowledge has already started (unofficially) by the participation of My-TRAC transport engineer experts in GoF4R workshop held in Brussels.
Daniel 11:10 SMARTE (UnivLEEDS)
Riccardo 11:25 ST4RT (FSItaliane)
G A 730822 P a g e 1 0 5 | 1 1 8
11:45 COMMON All
Collaboration Agreements (status and new ones): . For CFM projects, it was decided to create under COHESIVE cooperation tool space, a section to host a common repository of IP4 documentation. A similar folder will be created on Cohesive cooperation tool private space including information relevant for the OC projects (accessible by their coordinators).
. An excel sheet detailing most identified CFM/CFM, CFM/OC & OC/OC collaborations was drafted during the meeting. The excel file is managed by JL (UIC). Action (GoF4R): The excel file will be shared with all partners. Co-Active & ATTRACkTIVE will share their Ontologies documents with GoF4R project which is specifying the overall IP4 ontology.
. A potential collaboration plan was identified between Co-Active & ST4RT, in order to coordinate the conversion of technology and architecture.
Common Tooling: . Under Co-Active scope, a Capella Coaching Package was negotiated with about 5 sessions. Due to the S2R-IP4 projects common progress, Co-Active team proposed to offer S2R-IP4 partners (CFM & OC) the opportunity to attend those coaching sessions. One session was already held during September 2017. 2nd & 3rd sessions (2 days) are planned in week 4, 2018 (Madrid – Spain). WebEx remote attendance will be ensured, but physical attendance recommended especially for practical course in order to ensure efficient training. Next sessions, not yet scheduled. Action (Co-Active): ThalesFR will propose some dates and a program for the next Capella Coaching Sessions. Then, partners should share their preferences.
IP4 Communication Plan for TRA 2018 & Mid-Term Event: The TRA2018 & Mid-Term Event potential communication plans were exposed as follow: TRA2018, April 16th – 19th: o IT2Rail (19th): Demonstration, Presentation + Workshops o ATTRACkTIVE: Speech o Co-Active: potentially Poster presentation Mid-Term Event, April 20th (Mainly Co-Active and ATTRACkTIVE) – 4h of presentation +
G A 730822 P a g e 1 0 6 | 1 1 8
2h of networking workshops: o Plenary with presentation sharing the results o Workshops including interaction with stakeholders – possible parallel workshops running (per TD) The JU can help promoting the event (newsletter, other means) once the appropriate info is provided. Action (Co-Active and ATTRACKTIVE): fine planning of the Mid-Term Event (logistics, agenda, audience, …) Rui 14:30 InnoTrans18 Demonstration (ThalesPT) . Description of the current status of the work scheduled for InnoTrans Demo achievement: The InnoTrans will be focused on the three following topics: Live Interactive Demo Workshop(s) Presentation Material to be Rotated on Shared Screens, Flyers and Posters
Three different target audience were identified: Transport Service Providers Potential IP4 Ecosystem Operators Travellers
Two main use cases were identified, but still to be discussed, detailed, agreed and approved: Use Case 1: Starts in Brussels and finishes in Berlin, addressing as a target audience the European Commission representatives. Use Case 2: More complete, focused on the general Shift2Rail target audience.
A Task Force Team was identified to carry on, involving the following companies: Thales Portugal Thales France Hacon Indra Diginext Network Rail Bombardier Amadeus Communication Agency
A workshop planned to be held on January 15 at ThalesFR premises in Brussels, to discuss and approve the interactive live demos use cases (which technical functionalities will be included), approve the project plan and discuss additional practical aspects that need to be taken into account during the InnoTrans Exhibition..
G A 730822 P a g e 1 0 7 | 1 1 8
Action (COHESIVE): Rui LOURENCO (leader of the InnoTrans process) will send the need information required to update the use cases under analysis. 15:30 AOB – Next Steps ALL . A next S2R-IP4 collaboration workshop should be scheduled before the end of May 2018.
.
G A 730822 P a g e 1 0 8 | 1 1 8
4.11 T4C meetings
Attendees List
These “Team 4 Capella” meetings were held by conf-call. There were three meetings to discuss about the appropriate solution to follow. Minutes of Meeting (MoM)
Please see following screen shots.
G A 730822 P a g e 1 09 | 1 1 8
G A 730822 P a g e 1 1 0 | 1 1 8
G A 730822 P a g e 1 1 1 | 1 1 8
G A 730822 P a g e 1 1 2 | 1 1 8
G A 730822 P a g e 1 1 3 | 1 1 8
G A 730822 P a g e 1 1 4 | 1 1 8
G A 730822 P a g e 1 1 5 | 1 1 8
G A 730822 P a g e 1 1 6 | 1 1 8
G A 730822 P a g e 1 1 7 | 1 1 8
END-OF-DOCUMENT
G A 730822 P a g e 1 1 8 | 1 1 8