1. 1 © EURIDICE Consortium 2008 Kick Off Meeting Island of San Servolo - Venice, Italy 11th to 13th February 2008 Euridice Project Overview Paolo Paganelli Insiel

2. 2 © EURIDICE Consortium 2008 P. Paganelli, Insiel -11/2/2008 Agenda ● Vision ● Objectives ● Approach ● Workplan overview

3. 3 © EURIDICE Consortium 2008 P. Paganelli, Insiel -11/2/2008 Some words about the acronym ● It has not been chosen for its mythological meaning or appeal ● or lack of appeal. At the proposal beginning a potential partner said: “it has a nice sound, but a sinister meaning for a transport project”. ●..they stayed potential. ● It as been chosen because of I.D. and the I.C. ● I nter- D isciplinary research ● on I ntelligent C argo ● We started from two basic considerations: ● There are technology developments out there that could bring about a paradigm reversal in logistics: making the cargo itself an active part of the information flow. ● To bring about this change, different disciplines must be involved: various branches of ICT, logistics, economics and business modelling.

4. 4 © EURIDICE Consortium 2008 P. Paganelli, Insiel -11/2/2008 The Intelligent Cargo vision “In five years time, most of the goods flowing through European freight corridors will be ‘intelligent’, i.e.: self-aware, context-aware and connected through a global telecommunication network to support a wide range of information services for logistic operators, industrial users and public authorities.” ● Self-awareness means the ability of cargo to interact with the surrounding environment to actively notify its presence, identity and requirements. An intelligent cargo item will be an active provider of information services, notifying to the interested users and systems its details, position and related events as they occur. ● Context-awareness means intelligent ad hoc combination of information from all the involved stakeholders (shippers, logistic services providers, infrastructures and authorities), based on the current cargo position and status. An intelligent cargo item will “understand” its context in terms of interacting entities (vehicle, user, infrastructure), related information services and available combinations of services to solve specific user needs. ● Connectivity of moving goods means their constant availability as service consumers or providers by exploiting at need the mobile and fixed network infrastructures available along the route. Integration of intelligent cargo into service oriented architectures including mobile user and vehicle devices will make freight control virtually ubiquitous.

5. 5 © EURIDICE Consortium 2008 P. Paganelli, Insiel -11/2/2008 How it should work

6. 6 © EURIDICE Consortium 2008 P. Paganelli, Insiel -11/2/2008 How it is done ● Cargo Connectivity is realized by adapting and integrating state-of-the-art identification, communication and networking technology into an Intelligent Cargo Integration Framework (ICIF), including: ● Identification through RFID tags readers/writers or barcode readers. ● Positioning through GNSS (GPS or Galileo) devices, as well as GPRS-based localization. ● Mobile devices embedded into a network infrastructure that host local services for identification, data observation and manipulation. ● Middleware architecture including proxy functionality for information system backbone and data interchange. ● Security infrastructure. ● Flexible mobile radio transceiver by means of software defined radio technologies. ● Cargo Intelligence (CI) services and technologies for gathering, storing, analyzing, and providing access to cargo data to help users make better decisions. CI applications support the activities of centralized and distributed decision support based on: ● Semantic web and domain ontologies, for automated knowledge discovery and identification of services associated to any specific cargo item, context and user request. ● Advanced context technologies, for combination of item, vehicle and user IDs with automatically-detected conditions like, e.g., position and status of cargo. ● Distributed intelligent agents, for optimisation, anomaly and threats detection (alerting) and distributed real-time decisions support. ● Analysis of collected cargo data based on deep and shallow reasoning methods, query and reporting, online analytical processing (OLAP), statistical analysis, data, text and web mining, time series analysis for forecasting and trend detection, complex visualisation and reporting. ● Cargo Services Infrastructure is realized by adapting current SOA standards to the specific needs of moving goods and cargo communities, including: ● Mobile and fixed services support, allowing hybrid setup of mobile (field user) and fixed (back-office, 3rd party) use cases, ● Infrastructure services, supporting scalability, for infrastructure setups of different shapes and sizes, and wireless connectivity, for virtual omnipresence of cargo identification, context information and the related information services. ● Orchestration, supporting the combination of services for specific cargo management scenarios.

7. 7 © EURIDICE Consortium 2008 P. Paganelli, Insiel -11/2/2008 Architecture starting point

8. 8 © EURIDICE Consortium 2008 P. Paganelli, Insiel -11/2/2008 Euridice Impact Objectives ● Enhanced and widespread capability to monitor, trace and safely handle moving goods at the required level of detail, from full shipments to individual packages or items. ● Increased efficiency of transportation networks, by improving synchronization between logistic users, operators and control authorities. ● Improved sustainability of logistic systems, by reducing their impact on local communities in terms of traffic congestion and pollution.

9. 9 © EURIDICE Consortium 2008 P. Paganelli, Insiel -11/2/2008 Euridice Scientific and Technological Objectives ● Obj 1.1:To provide a pan-European ICT infrastructure for intelligent cargo items and mobile users to be identified, localized and connected through local and distributed communication facilities. ● Obj 1.2:To provide a fixed and mobile web services infrastructure for public and private stakeholders to access and use the information they need on a cargo item at any point along its route across European corridors, connecting the cargo with back-office and field staff. ● Obj 1.3:To provide for “on the fly” combination of services to address specific user/cargo/context interactions based on the concept of service oriented architectures. ● Obj 1.4:To provide for intelligent cargo solutions based on distributed and centralized data gathering, detection, analysis and prediction tools. ● Obj 1.5:To provide for an interoperability platform allowing the main actors on the field to expose and use intelligent cargo information services by linking these to their information systems.

10. 10 © EURIDICE Consortium 2008 P. Paganelli, Insiel -11/2/2008 Euridice Business and Societal Objectives ● Obj 2.1: To realize more flexible and efficient supply chains through the integration of intelligent cargo concepts into leading logistic operators and industrial organizations. ● Obj 2.2:To increase the efficiency, transparency and cost- effectiveness of intermodal transport. ● Obj 3.1:To provide the necessary business models for an intelligent cargo infrastructure to be established, sustained and fed with appropriate information. ● Obj 3.2:To realize more secure and environment friendly transport chains through the adoption of intelligent cargo to support modal shift and door-to-door intermodal services.

11. 11 © EURIDICE Consortium 2008 P. Paganelli, Insiel -11/2/2008 Project Structure

12. 12 © EURIDICE Consortium 2008 P. Paganelli, Insiel -11/2/2008 Concurrent development approach between P1 and P2

13. 13 © EURIDICE Consortium 2008 P. Paganelli, Insiel -11/2/2008 Milestones and results (months 1 to 18) Mile-stone No. Milestone Name Workpa-ckage(s) Involved Lead benefi- ciary Delivery date Means of verification M6Project foundations WP11, WP12, WP22, WP23, WP24, WP25, WP26 Insiel Month 6 Availability and evaluation of: -High level architecture overview. -Knowledge sources in the transportation and connected logistics domains. -Plan of pilot experimentation and assessment -Pilot Scenarios descriptions. M12 Technical and business context characterization WP12, WP13, WP14, WP22, WP31 SingularLogicMonth 12 Availability and evaluation of: -Data sources definition. -Wireless Connectivity Characterisation. -EURIDICE Context Model. -Pilots assessment methodology. -Analysis of pilot business models. M18 Architectural and methodological framework. WP11, WP12, WP13, WP14, WP21, WP22, WP23, WP24, WP25, WP26 Logica CMG Month 18 Availability and evaluation of: -detailed architecture and platform integration guidelines. -Data gathering, cleaning, fusion and pre-processing prototypes. -Mobile, Fixed, System and Communication Services Definition. -EURIDICE Methodological Framework. -Formalised Domain Knowledge. -Pilots assessment and final requirements.

14. 14 © EURIDICE Consortium 2008 P. Paganelli, Insiel -11/2/2008 Milestones and results (months 19 to 36) Mile-stone No. Milestone Name Workpa-ckage(s) Involved Lead benefi- ciary Delivery date Means of verification M24 Framework components release WP11, WP12, WP13, WP14, WP21, WP23, WP24, WP25, WP26, WP31, WP32 InsielMonth 24 Availability and evaluation of: -Intelligent Cargo conceptual framework and interoperability platform. -Data-mining, web-mining, text-mining and offline anomalies detection prototypes. -Technologies for Wireless Connectivity, Services and Orchestration. -Basic user applications and integrated platform first release. -EURIDICE Data Models. -Pilot applications design. -Reference business models. -Training modules and internal training workshops. M30Demonstrators WP13, WP21, WP23, WP24, WP25, WP26, WP32, WP34 InsielMonth 30 Availability and evaluation of: -Advanced user applications and integrated platform final release. -Pilot demonstrator systems. -Public training workshops. -EURIDICE Exploitation Workshops. M36 Validated results and way forward WP22, WP23, WP24, WP25, WP26, WP31, WP32, WP33, WP34 CeTIMMonth 36 Availability and evaluation of: -Pilots final assessment and validated methodologies and subsystems. -Pilot feedback and evaluation. -Business models validation results. -Training evaluation. -EURIDICE closing event at international conference. -Joint and Single Exploitation Plans.

15. 15 © EURIDICE Consortium 2008 P. Paganelli, Insiel -11/2/2008 Project GANTT (1/2)

16. 16 © EURIDICE Consortium 2008 P. Paganelli, Insiel -11/2/2008 Project GANTT (2/2)

17. 17 © EURIDICE Consortium 2008 P. Paganelli, Insiel -11/2/2008 Conclusions ● Strengths ● Strong competencies in the consortium, including technology leaders. ● Multi-disciplinary approach. ● Weaknesses ● Complex workplan. ● Challenging objectives. ● Opportunities ● Key technology progresses in areas related to EURIDICE. ● Attention paid by important business and government players. ● Threats ● Mismatch between different visions of the project: our success depends on both user value and technology innovation. “ Value without innovation works on an incremental scale.. not sufficient to make you stand out in the marketplace. Innovation without value tends to be technology-driven.. often shooting beyond what buyers are ready to accept and pay for.” Kim, W. Chan, Mauborgne, R., « Blue Ocean Strategy », Harward Business School Press, 2005