Kick Off Meeting Island of San Servolo - Venice, Italy 11th to 13th February 2008

1. Kick Off MeetingIsland of San Servolo - Venice, Italy11th to 13th February 2008 P2 Pilot Applications Workplan Review Prof. Marco Mazzarino, Dr. Tatjana Bolic Venice International University – TLSU (Transport, Logistics and Supply chain management Unit) – Tedis Center

2. Agenda • Project 2 (P2) introduction • Work Package (WP) objectives, expected results, main activities and tasks • Common pilots methodology • Issues to address

3. P2 Introduction • P2 is targeted to the translation of Science/Technology (S/T) results into the benefits to the end users • P2 will focus on: • Obtaining requirements from end users, to be used as input in the P1, • Trials to tests and assess S/T results, that is, demonstrating through pilots the EURIDICE platform benefits for the various end-users • Pilots are to be designed by taking into account the requirements of different stakeholders: • Producers and distributors (WP23), • Intermodal operators (WP24), • Logistics operators (WP25), • Public authorities and logistics infrastrucuture managers (WP26) • Horizontal activities (common to all the pilots): • Consolidation of S/T results into a shared platform (WP21) • Planning, methodology and assessment of the pilots (WP22)

4. P2 Introduction P2 Pilot Applications WP21 Platform Integration WP22 Pilots Assessment WP23 Industry/Distribution Applications WP24 Intermodal Transport WP25 Logistics Operators WP26 Authorities and Infrastructure

5. WP 21 Platform Integraton • WP leader: INSIEL • Objectives and expected results: • Objective: to realize a common platform for the implementation of EURIDICE pilots • Platform will provide: • Integration of approaches, methodologies and tech components of P1 into a unified framework; • Reliable, accessible and effective ICT infrastructure for deployment of services and pilot user applications • Technical support and infrastructure maintenance • Expected results: • Integrated methodology for Intelligent Cargo (IC) applications, combining methods and solutions from S/T research • End-users applications, applicable to different pilots • Common test bed for pilot applications • WP21 will receive three kind of inputs: • From P1: approaches and prototypes made available by S/T activities; WP11 (architecture), WP12 (domain knowledge), WP13 (cargo intelligence), WP14 (SOA and mobile devices) • From P2: requirements and use cases specifications from pilot scenarios • From P3: issues and requirements derived from business models

6. WP21 Platform Integration 6 12 18 24 30 36 Months 21.1 Integrated Platform Specification and Methodology 21.2 End-user Applications 21.3 Integrated Platform Implementation 21.4 Integrated Platform Maintenance and Support

7. WP21 Platform Integration • 21.1 Integrated platform specification and methodology • Specification based on continuous updates of S/T results and pilot users requirements • Integration of: • Concepts and approaches into a unified methodological framework; • Applications by combining different software components and services • Identification, communication and information systems to realize a reference instantiation of the Euridice platform

8. WP21 Platform Integration • 21.2 End-user applications • Based on WP23-WP26 use cases specification a set of applications will be designed and develop • Criteria: relevance for pilot benefits demonstration, applications common to more pilot cases, innovation with respect to the state-of-the-art

9. WP21 Platform Integration • 21.3 Integrated platform implementation • EURIDICE platform to be used as a common test bed for different pilot cases (all pilot cases will use the shared platform)

10. WP21 Platform Integration • 21.4 Integrated platform maintenance and support • To ensure platform stability and accessibility according to pilot user needs • To support both users and pilot application developers in using a shared platform (central, dedicated structure for hosting and management services)

11. WP21 Platform Integration • Milestones: • M18 Euridice methodological framework • M24 Basic user applications and integrated platform first release • M30 Advanced user applications and integrated platform final release • M36 Integrated platform maintenance feedback

12. WP22 Pilots Management and Assessment • WP leader: ENICMA • Objectives and expected results: • Objective: to define and plan the most effective way to assess and validate EURIDICE results • Specific goals: • To accompany pilot innovation processes from early business needs assessment to validation and adoption of EURIDICE solutions • To facilitate information exchange among pilot cases and consolidate the pilots’ feedback to the S/T activities • Identify measurable criteria and instruments for measurements (questonnaires, etc.) • Background: • Each pilot will be focused on specific groups of users and a set of IC functions • WP22 aims at harmonizing requirements, planning and methodologies among pilots • Expected results:a common framework for pilot testing management and assessment

13. WP22 Pilots Management and Assessment 6 12 18 24 30 36 Months 22.1 Pilot Case Definition, Awareness Creation and Pilot Site Preparation 22.2 Definition of Business Drivers and Assessment Criteria 22.3 Preparation and Validation of Field Experiments 22.4 Pilot Case Analysis and Cross Pilot Analysis 22.5 Information Exchange Management

14. WP22 Pilots Management and Assessment • 22.1 Pilot case definition, awareness creation and pilot site preparation: • Plan all activities to be performed before and during pilot implementation (preparatory phase) • Training session for end-users involvement

15. WP22 Pilots Management and Assessment • 22.2 Definition of business drivers and assessment criteria: • Define the overall assessment methodology, in particular: • Assessment of the performance of the general platform requirements (technical) • Assessment of various requirements from pilots • How? Requirements (platform + pilots) will be broken down: • Into performance criteria • Efficiency, flexibility, usability, confidentiality, security, frequency, accuracy, etc • And consequently into specific (measurable) metrics • User perception, satisfaction index • Define tools needed for data gathering, and calculation of results • Questionnaires, interviews, observation, etc.

16. WP22 Pilots Management and Assessment • 22.3 Preparation and validation of field experiments • Preparation of the pilot cases assessment and collection of information data from various experiments

17. WP22 Pilots Management and Assessment • 22.4 Pilot case analysis and cross pilot analysis • Establishing assessment criteria for each pilot • Getting user satisfaction, system performance, level of improvement

18. WP22 Pilots Management and Assessment • 22.5 Information exchange management • Coordinating requirements, planning and methodologies among pilots to facilitate communication and information exchanges between WP21-26 and technical development WP11-14 • Regular feedback workshops • Planning of dissemination of methods and tools developed within Euridice to a higher number of users

19. WP22 Pilots Management and Assessment • Milestones: • M6 Consolidate plan of pilot experimentation and assessment • M12 Definition and approval of the pilots assessment methodology • M24 Initial assessment of the pilots experiments • M36 Pilots final assessment and validated methodologies and subsystems

20. WP23 Production and Distribution Applications • WP leader: VIU • Objectives and expected results: • Objective: to select and develop scenarios in which IC solutions and services will be tested and assessed according to the producers’ and distributors’ needs, while taking into account requirements of logistics and transport operators involved • Pilot main characteristics: • Buyer-supplier relationship • Industry-specific (Fast Moving Consumer Goods (FMCG) and eyewear) • Global scale • Focused on single items • Integration of different actors and strong SMEs involvement • Main goals: • Optimizing logistics planning and management systems • Optimizing logistics and transportation process control (monitoring, traceability, retrievals, work-in-progress, etc.) • Expected results: tested and validated Euridice applications within the stakeholder group

21. WP23 Production and Distribution Applications • Pilot scope: • Food industry (FMCG): • Specific sector: fresh fishing products • High value items (importance of quality control) • Sensitive items (perishability) • High turnover ratio • Various laws imposing control and information requirements on items and processes (transport, receiving, stocking, processing, etc.) • Necessity of better management of traceability codes • Global logistics and transportation network (including reverse logistics) • Items of interest for IC solutions: consumer unit (eg, single tuna slice), packaging unit (6-12 slices box), logistics unit (pallet or air container – ULD) • Fashion industry (eyewear): • Major producers (75% of world market share) and logistics operators involved • Capturing of all major Supply Chain (SC) relationships: leaders-SMEs, shipper-receiver • Global scenarios and networks • Global competition seriously put at risk due to a lack of suitable ICT solutions • Critical issue: moving toward global competition by redesigning logistics networks through IC solutions

22. WP23 Production and Distribution Applications 6 12 18 24 30 36 Months 23.1 Scenario Definition and New Challenges 23.2 Requirements Assessment 23.3 Logistics and Transport Planning, Management and Control System Design and Development 23.4 Integration and Deployment 23.5 Pilot Operation and Validation 23.6 Expected Results, Feedback and Benefits Assessment

23. WP23 Production and Distribution Applications • 23.1 Scenario definition and new challenges • Based on previous S/T results and critical needs defined by stakeholders

24. WP23 Production and Distribution Applications • 23.2 Requirements assessment • Analysis of the state-of-the-art situation (ICT tools) and definition of critical needs that are suitable for IC solutions • Poor integration among actors and poor tech standard, not suitable for global competition • Identification and analysis of lacking applications, infrastructures (especially for SMEs) and “tech culture” • Collection and analysis of requirements for EURIDICE applications from users (cyclical process)

25. WP23 Production and Distribution Applications • 23.3 Logistics and transport planning, management and control system design and deployment • Design an integrated logistics and transportation planning, management system based on scenarios and requirements • Identify specific user objectives, data requirements identification • Employ EURIDICE prototypes

26. WP23 Production and Distribution Applications • 23.4 Integration and deployment • Integrate applications into the existing ICT systems of users • Deploy EURIDICE prototypes into a functioning demonstrator environment suitable for testing, assessing and piloting • Architecture specifications (WP11) and platform (WP21) will be adopted

27. WP23 Production and Distribution Applications • 23.5 Pilot operation and validation • Actual implementation in the end users’ environment (trial as-close-as possible to real life) • Collection of end users’ assessment of EURIDICE solutions for validation purposes • Activities: • Fine-tuning selection of users, • Real data usage, • Test cases, • Benefit assessment • Dissemination of results

28. WP23 Production and Distribution Applications • 23.6 Expected results, feedback • Collection of feedback information: • On EURIDICE platform performance and • On main benefits for end users • Benefits assessment, their communication to WP33 for further dissemination • Feedback to S/T results (requirements, potential new features)

29. WP23 Production and Distribution Applications • Milestones: • M12 Production / distribution logistics pilots requirements • M24 Production / distribution logistics pilot prototype • M36 Production / distribution pilots operation, feedback and evaluation

30. WP24 Intermodal Operator Management Pilot • WP leader: VTT • Objectives and expected results: • Objective:develop a management and operation information system for intermodal operations and demonstrate results • The system will enable efficient planning, monitoring and management of intermodal operations • Sub-goals: • Create an intermodal operation management system (information collection to support Key Performance Indicators (KPIs) calculation) • Realize a pilot prototype system • Real case based evaluation of developed solutions • WP in close relationships with WP12, WP13, WP21, WP22 • Expected results: operation and validation of developed system

31. WP24 Intermodal Operator Management Pilot • Pilot scope: • Intermodal transportation in Europe very low • Complex processes with many independent players (railway companies, other operators) • Need for continuous access to and reliability of real-time tracking and tracing information of the transport/goods • Features to be demonstrated: • Vision of future tracking: Global, real-time tracking and tracing providing relevant status info • Technical innovation: Management system supporting planning and operation of efficient transportation • Business innovation: User interface

32. WP24 Intermodal Operator Management Pilot 6 12 18 24 30 36 Months 24.1 Definition of Case Scenarios and Inputs to S/T Research 24.2 Design and Development of the Management and Information System 24.3 Design and Development of an ICT-Platform 24.4 Integration & Prototype Realization 24.5 Prototype Evaluation and Enhancement

33. WP24 Intermodal Operator Management Pilot • 24.1 Definitions of case scenarios and inputs to S/T research • Input and requirements from partners (intermodal operators) regarding regulations, management principles and approaches, KPIs features, interoperability and integration of partner’s information systems

34. WP24 Intermodal Operator Management Pilot • 24.2 Design and development of the management and information system • Based on previous requirements, the task will address issues such as: data collection and warehousing, solutions for communication among actors, operations support systems (simulation, anomaly and alerting systems, etc.), interfaces

35. WP24 Intermodal Operator Management Pilot • 24.3 Design and development of an ICT platform • Platform development will be based on the WP11 framework and will apply WP11 solutions for: • Communication, • Identification, • Positioning, • Security, • Interfaces

36. WP24 Intermodal Operator Management Pilot • 24.4 Integration and prototype realization: • Design and implement the prototype system into a pilot • Prototype will use the ICT platform and IC framework of P1 • Minimum scope: GPS/GPRS module installed in a rail wagon (transmitting a location signal during a trip that is transmitted to the pilot database) • Pilot prototype having interfaces to transform data into suitable information format for different end users

37. WP24 Intermodal Operator Management Pilot • 24.5 Prototype evaluation and enhancement • Close collaboration between end users is envisioned in evaluation and testing • Develop a mechanism for continuous evaluation and improvement – a sort of spyral development

38. WP24 Intermodal Operator Management Pilot • Milestones: • M6 Intermodal transport scenario and preliminary requirements • M18 Intermodal transport requirements • M24 Intermodal pilot design • M30 Intermodal pilot demonstration • M36 Feedback and evaluation of intermodal pilot

39. WP25 Logistics Operators Pilot • WP leader: TREDIT • Objectives and expected results: • Objectives: • Bring logistics operators into the project by exploiting components and technologies of Euridice platform, according to WP22 approach • Support real-time functions (monitoring, tracking, dynamic re-planning) and off-line ones (accounting and invoicing) • Key challenges: • Integration with existing ICT solutions of users • Re-engineering of business process and workflow • Data requirements • Expected results: operation and validation of pilot applications that use real-time data transfer and collection, their integration into the existing systems

40. WP25 Logistics Operators Pilot • Pilot scope: • PRODOS (Kuehne-Nagel): to develop synergies with existing ICT solutions and platforms (monitoring of rail network, GPS/GPRS units, etc.) • AKARPORT: integrating IC solutions into the existing ERP system for bulk cargo • OMEGA: to enhance monitoring deliveries to/from Romania by using EURIDICE platform solutions (tracking, tracing, etc.) integrated into its ERP system • Gebruder Weiss: continuous GSM tracking&tracing system to be integrated into the EURIDICE platform by means of two pilots • Pilot scenarios: • Automated proof of delivery of itemized/unitized cargo • Monitoring bulk cargo • Online monitoring of transportation process and reporting

41. WP25 Logistics Operators Pilot 6 12 18 24 30 36 Months 25.1 Requirements and Inputs to S/T Research 25.2 Pilot Applications Design and Development 25.3 Integration and Deployment 25.4 Pilot Operation and Validation 25.5 Formalization of Feedback

42. WP25 Logistics Operators Pilot • 25.1 Requirements and inputs to S/T research • Logistics operators and ICT experts will provide input to P1 reflecting industry needs • Euridice solutions should accomodate existing ICT solutions

43. WP25 Logistics Operators Pilot • 25.2 Pilot applications design and development • Develop pilot applications to support logistics operators’ needs, based on technologies developed within P1 and the EURIDICE platform • Emphasis on: integration of existing systems into the EURIDICE platform by customization

44. WP25 Logistics Operators Pilot • 25.3 Integration and deployment • EURIDICE components to be integrated into the workflow of logistics operators and prototypes to be assessed by WP25 partners

45. WP25 Logistics Operators Pilot • 25.4 Pilot operation and validation • From integration to operation and validation • Aim: extracting constructive feedback

46. WP25 Logistics Operators Pilot • 25.5 Formalization of feedback • Collection and formalization of feedback at the end of the project

47. WP25 Logistics Operators Pilot • Milestones: • M6 Logistics operators’ scenario and preliminary requirements • M18 Logistics operators’ pilot requirements • M24 Logistics operators’ pilot application design • M30 Logistics operators’ pilots demonstrator systems • M36 Logistics operators’ pilots feedback and evaluation

48. WP26 Authorities and Infrastructure Pilots • WP26 leader: INSIEL • Objectives and expected results: • Objective: design, implement and assess pilot applications of the EURIDICE approach and technologies for public authorities and logistics infrastructures • Expected benefits: • Efficiency of cargo verification and document processing activities (border-crossing operations), in particular the assessment of automated verification of container (port of Trieste) and trailers (SDAG) • Efficient infrastructure usage and traffic reduction spatially (real-time synchronization of terminal access by communication with vehicle drivers) • Key challenges: • Integration with existing ICT solutions • Minimal impact on users in terms of additional information and familiarization with new solutions • Security concerns (sharing sensitive data with other entities) • Expected results: authorities and infrastructure pilot demonstrator system operation, validation and assessment

49. WP26 Authorities and Infrastructure Pilots • Pilot scope: • Port of Trieste • SDAG of Gorizia (two main nodes of the Friuli Venezia Giulia logistics system) • Aiming at assessing how the Euridice technology can improve their internal and combined operations, and the corresponding impact on the overall regional system

50. WP26 Authorities and Infrastructure Pilots 6 12 18 24 30 36 Months 26.1 Requirements and Inputs to S/T Research 26.2 Pilot Applications Design and Development 26.3 Integration and Deployment 26.4 Pilot Operation and Validation 26.5 Formalization of Feedback