Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

CHOReVOLUTION SMT Use Case v1.3

276 views

Published on

Smart Mobility & Tourism Use Case (Version 1.3) of CHOReVOLUTION project by Marco Masetti, Softeco
First Year Project Review in Brussels
11 February 2016

Published in: Software
  • Be the first to comment

  • Be the first to like this

CHOReVOLUTION SMT Use Case v1.3

  1. 1. WP 5 Smart Mobility & Tourism Use Case Marco Masetti Softeco First Project Review Brussels, February 11, 2016
  2. 2. WP5 Overview Duration: M1 - M36 Effort: 43 PMs  T5.1: SMT Scenario investigation and requirements (Softeco, Thales, UDA, Tirasa)  T5.2: SMT Services Implementation and Choreography development (Softeco, Cefriel, Inria, Tirasa, UDA)  T5.3: SMT Choreography deployment and assessment (Softeco, Cefriel, Inria, Thales, Tirasa, UDA)  T5.4: SMT Business Model (Softeco)
  3. 3. WP5 Deliverables  D5.1: SMT Definition and Requirements ® [Released in M6]  D5.2: SMT Scenario simulation (O)  D5.3: SMT Demonstrator implementation (O)  D5.4: SMT Business Model (R)
  4. 4. Challenges in services for smart mobility and tourism  Growing diffusion of ICT services for tourists (and citizens) giving rise to new ways of enjoying the city  The provision of mobile applications is spreading, users can experience new ways to produce and consume information anywhere and anytime  An integrated approach toward a smart city model assume a strong cooperation and coordination among these services, but this is prevented by heterogeneous protocols and interfaces  A real challenge is the dynamic interaction and cooperation among these services in order to provide new added value services to citizens and tourists
  5. 5. Challenges with services and things Issues  Security: We want to have secure communication between services  Heterogeneity: No single choice on middleware protocols, depending on stakeholders  Interoperability: Different protocols need to be able to communicate with each other, critical in IoT Solutions Security filters Binding components Adapters
  6. 6. Services and Things in the FI domain Historical Historical Historical Historical Historical Historical Historical Historical Cultural Cultural Cultural Cultural Cultural Cultural Cultural Booking Booking BookingBooking Public Transport schedule Tourist blogs & news Traffic Info Traffic Info Parking Info Parking Info Parking Info Parking Parking Journey Planners Weather Station Emission sensor Weather Station Weather Station Mobility Services Environmental Services City Governance Services Smart Societal Services VR & Immersive Exp services Smart Tourism Parking Emission sensor Emission sensor All these services need to cooperate and coordinate one each other In a secured way in order to reach their goals! CHOReVOLUTION comes to resque!!
  7. 7. SMT Use Case description  The goal of the scenario taken into consideration for the validation of the first version of the platform is providing the tourist a detailed journey plan to visit a list of touristic places  To perform this task a set of basic services already available and realized in-house or by third-parties have to cooperate in order to reach the use case goal  A possible cooperation among the services is depicted in the following choreography  During this first project period the selected choreography has been continuously refined and adapted to the project needs.
  8. 8. Choreography of the implemented scenario
  9. 9. Demo (after lunch!)
  10. 10. First feedbacks in using the platform  A top-down systematic development process  Promotes the re-use and integration of already available services/Things  BPMN2 choreography diagrams provide a higher perspective and an efficient way to depict services/Things interactions  The integrated development environment facilitates the platform adoption by end users  Adapters and binding components to tackle service heterogeneity  Filters to seamlessly add security
  11. 11. Conclusion and next steps  WP5 main achievements in the period:  D5.1 delivered on time  First collection of choreographies  Set of services developed and deployed  First scenario demonstrator ready for the first review  Next Steps:  Start using the complete CHOReVOLUTION platform and provide feedbacks (T5.2)  Continuous refinement of the designed choreographies  Start the assessment, verification and validation of the CHOReVOLUTION platform (T5.3)
  12. 12. Q & A Thank You Marco Masetti (marco.masetti@softeco.it) Softeco

×