1. 1 st Review Meeting, Brussels 5/12/12 – Technical progress (P. Paganelli, Bluegreen) www.i-cargo.eu iCargo 1st Review Meeting Brussels 5/12/12 Technical Progress and discussion P. Paganelli (Bluegreen) 1

2. 1 st Review Meeting, Brussels 5/12/12 – Technical progress (P. Paganelli, Bluegreen) www.i-cargo.eu 1st Year results Key common results 2nd Year planned results Approach to cooperation Contents 2

3. 1 st Review Meeting, Brussels 5/12/12 – Technical progress (P. Paganelli, Bluegreen) www.i-cargo.eu First year results 3 Policy, Market and Technology survey D1.1 Consolidated high- level requirements D1.2 iCargo Vision D1.3 Common Framework Specific. D1.4 iCargo components design (version 1) D1.2 D2.1a iCargo components design (version 2) D1.2 D2.1b Orchestrated iCargo application objects D1.2 D3.1 Infrastructure archit. and design D1.2 D4.1a Business cases specification D1.2 D5.1 Pilot user requirements D1.2 D5.2 Market analysis D1.2 D7.1 Reference Business Models D1.2 D7.2 M3 M6 M12 ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔

4. 1 st Review Meeting, Brussels 5/12/12 – Technical progress (P. Paganelli, Bluegreen) www.i-cargo.eu WP1 – Deliverable D1.1 – Policy, Market and Technology Baseline Policies, practices and standards we will refer to – Deliverable D1.2 – Consolidated high-level requirements The overall business and functional requirements for iCargo – Deliverable D1.3 – iCargo Vision (White Paper) The Why, What and How of iCargo – Deliverable D1.4 – iCargo Common Framework Standardized processes and messages WP2 – Deliverable D2.1 – iCargo components design Overall technical architecture and components Available results (1/3) 4

5. 1 st Review Meeting, Brussels 5/12/12 – Technical progress (P. Paganelli, Bluegreen) www.i-cargo.eu WP3 – Deliverable D3.1 – Orchestrated iCargo application objects iCargo functions and how they are used WP4 – Deliverable D4.1 – Infrastructure architecture and design Putting together iCargo IT infrastructure (first version) WP5 – Deliverable D5.1 – Business Cases Specifications Business objectives of the Pilots – Deliverable D5.2 – Pilot user requirements What is requested to be implemented in the Pilots Available results (2/3) 5

6. 1 st Review Meeting, Brussels 5/12/12 – Technical progress (P. Paganelli, Bluegreen) www.i-cargo.eu WP7 – Deliverable D7.1 – Market Analysis Description of the available market (qualitative and quantitative) – Deliverable D7.2 – Reference Business Models What kind of companies will do business in the iCargo ecosystem Available results (3/3) 6

7. 1 st Review Meeting, Brussels 5/12/12 – Technical progress (P. Paganelli, Bluegreen) www.i-cargo.eu By 2020, efficient, low-carbon end-to-end transport and logistics services will be planned, executed and completed cooperatively in a global freight business ecosystem, based on fully interoperable cargo, vehicle, infrastructure and freight management systems, supporting optimal resources usage and real-time alignment of intermodal plans with on- going operations. The iCargo Vision 7

8. 1 st Review Meeting, Brussels 5/12/12 – Technical progress (P. Paganelli, Bluegreen) www.i-cargo.eu The iCargo approach Achieve the iCargo vision through an open freight management ecosystem. A business ecosystem is an “intentional community of economic actors” having in common protocols, interfaces and an overall business goal. In the case of iCargo this is the provision of door-to-door low-carbon logistic services, i.e., services that: – cover an entire supply chain or a significant portion of it, – produce less CO 2 than alternatives, – make use of the iCargo ecosystem to combine services through different transport modes and providers. 8

9. 1 st Review Meeting, Brussels 5/12/12 – Technical progress (P. Paganelli, Bluegreen) www.i-cargo.eu 9 Ecosystem -Inclusive -Decentralized -Based on shared rules Connected resources -Selected on the basis of the Virtual Resources Network Options -Integrated view based on common semantics -Support distributed monitoring and planning Door-to-door service Roles and resources assigned on demand Virtual Resources Network -Automated resource discovery The iCargo ecosystem 9

10. 1 st Review Meeting, Brussels 5/12/12 – Technical progress (P. Paganelli, Bluegreen) www.i-cargo.eu Collaborative planning, for pooling and sharing resources across the logistic chain. Logistic chain composition based on services, for integrating the different available transport and logistic services. Re-planning of logistic chains by (or on behalf of) the client, in case of goals changes or events happen during the execution time. Optimization of the use of resources of the logistic chain, allowing the Logistic Service Providers to be more situational aware and so to optimize the use of transport resources. Monitoring the environmental footprint, providing smart tools and shared methodologies for environmental data gathering and reporting. iCargo innovations 10

11. 1 st Review Meeting, Brussels 5/12/12 – Technical progress (P. Paganelli, Bluegreen) www.i-cargo.eu The iCargo ecosystem at work Execution Logistic Demand Logistic Service LSPLSC Cooperation X+Y Cargo Box-1234 C B Logistic network awareness Place B Trip C->A A Services BSD S x BSD D Y Transaction Order X-YYY Logistic chain composition Emission monitoring Organisation Truck 25-KGJ-8 Trip B->C 11

12. 1 st Review Meeting, Brussels 5/12/12 – Technical progress (P. Paganelli, Bluegreen) www.i-cargo.eu iCargo functions Logistic chain composition – Collaborative planning support (information services support to the “physical internet”, cooperation with the MODULUSHKA project). – Open logistic network based on common definition of transport and logistic services. – Taking into account 3 dimensions: cost, effectiveness, emissions. Logistic network awareness – Monitoring infrastructure based on Intelligent Cargo, vehicle and infrastructure connectivity. – Re-planning triggered by automated monitoring and deviations. – Dynamic alignment of individual service providers plans. Emissions monitoring – Monitoring infrastructure includes collection of energy consumption data. – Real-time calculation of emissions at shipment level. 12

13. 1 st Review Meeting, Brussels 5/12/12 – Technical progress (P. Paganelli, Bluegreen) www.i-cargo.eu iCargo reference value chain 13 Logistic Services Client (LSC) Low-carbon door-to door service Logistic resources and capabilities Freight Services Integrator (FSI) Logistic Services Provider (LSP) Needs goods delivered with lower emissions, good performance and no extra cost Needs to deliver door-to-door service by organizing logistic resources and capabilities Needs to make own resources and capabilities accessible and well utilised Needs to make own resources and capabilities accessible and well utilised Information Services Integrator (ISI) Information services infrastructure Transportation Network Manager(TNM) Transport infrastructure Regulatory Compliance Transport Regulator (TR) iCargo service providers/users iCargo jobs-to-be-done (12), with features/barriers Common high-level view for business-facing WPs (requirements, business models, assessment)

14. 1 st Review Meeting, Brussels 5/12/12 – Technical progress (P. Paganelli, Bluegreen) www.i-cargo.eu 2nd Year planned results 14 iCargo detailed requirements D1.5 Policy, Market and Tech. baseline upd. D1.6 Cloud resources, sematic … D1.2 D2.2 Infrastr. archit. and design (Final) D1.2 D4.1b M14M18M24 Exploitation Handbook D1.2 D7.5 Knowledge base infrastr. and tools D1.2 D2.3 Mobile infrastr., agents… D1.2 D2.4 Specification iCargo freight objects D1.2 D3.2 Specification iCargo traffic objects D1.2 D3.3 Specification iCargo plann. and CO2 obj. D1.2 D3.4 iCargo freight objects 1.0 D1.2 D3.5 iCargo traffic objects 1.0 D1.2 D3.6 iCargo plann. and CO2 obj. 1.0 D1.2 D3.7 Base IT Infrastructure D1.2 D4.2 SCAR Pilot design D1.2 D5.3 Green Corridor Pilot design D1.2 D5.4 LSP- LSC Cooper. Pilot design D1.2 D5.5 Initial Exploitation Plans D1.2 D7.6 Validation Approach & Metrics D1.2 D7.3 Initial status assessment D1.2 D7.4

15. 1 st Review Meeting, Brussels 5/12/12 – Technical progress (P. Paganelli, Bluegreen) www.i-cargo.eu Technical coordination approach 15 Shared high-level results (vision, requirements, value chain, functions, architecture) Involvement of technical coordinator for strategic planning of each new task/deliverable Consensus building on main decisions – WP leaders’ meeting every 3-4 months – Discussion of high-level results. Coordination actions planned for the 2 nd year: – Continue WP leaders’ meetings to refine interfaces and provide reciprocal input for next results – Align all partners through training on released results.