The aim of this document is to summarize all activities in individual demos but also the overall coordination that was needed among demos. As can be seen from the document, this coordination contained many follow-up steps. Therefore, it required close cooperation not only within the demo teams, but also at the WP5 level or across WPs. This coordination was also very important because some demos took place in both IP4MaaS and Ride2Rail projects (in particular in Athens and Padua) in parallel, so it took a lot effort to synchronize all activities between these projects and at the same time cooperation with CFM side, which was responsible for proper integration into the IP4 ecosystem. For this reason, this deliverable illustrates important phases of the demos life cycle, in particular:• demo preparation,• demo execution, • demo evaluation.This structure is used for each demo so that the reader is presented with the same content of the information, but at the same time can compare different approaches, e.g. within the user engagement strategy, number of demonstrated functionalities, number of testers, feedback from them, etc. All information is described in detail in individual reports. The last chapter then tries to summarize all the activities, but above all to emphasize the differences in the individual demos. Complete information is provided in individual report D5.2-5.7. These reports are published on the project website https://www.ip4maas.eu/