WP5 – Open End-to-End Pilots Implementation

1. WP5 – Open End-to-End Pilots Implementation Jose Gato Luis – WP5 Leader Brussels 5th of December 1st Review

2. Agenda • WP5 plan of activities • Main results achieved in Task T5.1 • Deliverable D5.1, “Business Case Specification”, released • high-level description, in business terms, of the iCargo pilot cases • Deliverable D5.2, “Pilot user requirements”, released • User’s technical requirements for each pilot • Plan of the next activities and steps

3. M12 M18 M33 M3 M24 WP5 TimeLine • WP5 Business Cases Pilot’s Design Pilot’s Prototype Pilot user req. D5.2 D5.3 D5.6 D5.1 D5.4 D5.7 D5.5 D5.8 • WP5 T5.2 T5.1 T5.3 T5.4

4. Deliverable D5.1: objectives Main aim: to provide the high-level description, in business terms, of the iCargopilot cases: • Sea-City-Air-Rail door-to-door service (SCAR), • Green Corridor between Sweden and the European Continent, • LSP-Shipper Cooperation on the Continent, by identifying new low-carbon services, targeted customers, innovative elements introduced and related benefits expected.

5. Deliverable D5.1: approach • APPROACH • definition of: • business objective of the pilot; • main involved actors for each user role of the iCargo Reference Value Chain; • main activities, associated to user roles, to be supported by the iCargoecosystem; • features and barriers associated to these activities. • INPUTS • iCargoReference Value Chain, • definition of value-creation links between user roles of the iCargo Reference Value Chain (“job-to-be-done”). • OUTPUTS • definition and characterization of the value chain of the three business cases.

6. Deliverable D5.2: objectives Main aim: to provide user functional requirements for each pilot. It provides: • the description of the changes to be introduced on the users’ business processes to enable the new logistics services defined in Deliverable D5.1 “Business Cases Specifications”; • the requirements that the iCargo pilot implementation will have to fulfil, for the implementation to be successful from the user perspective. The outputs will be used: • to consolidate and validate the general requirements defined by iCargo; • as base for the detailed Pilot Cases Designs, to be delivered at month 24.

7. Deliverable D5.2: approach (1/2) • APPROACH • Definition of: • “As is” – “To be” scenario analysis: • Process description in the current situation • Process description in the desired situation • From scenario analysis to use case specification • From use cases to user requirements definition: • Common requirements • Pilot-specific requirements • User requirements consolidation and validation • OUTPUTS • Use Cases specification • User Requirements specification • Matching User Requirements with Initial High-level Requirements • INPUTS • Scenarios and objectives set by deliverable D5.1 • Detailed analysis of the three pilot cases • Initial high level requirements (D1.2) to verify the match between user requirements and general iCargo requirements 7

8. Deliverable T5.2: approach (2/2)

9. Deliverable D5.2: Business Innovations From “As is” into “to be”, links with iCargo Business Innovation • Sea-City-Air-Rail (SCAR) produces 6 uses cases. • Focused on Collaborative Planning and Replanning of logistic chains. • Integrating long-haul transport and last mille delivery (city of Bologna) • But also evaluating of both cargo emissions and logistic performances • The green corridor led by Stora Enso produces 4 use cases • Focused on Dinamyc replanning based on wagon movements collected in real time • But also monitoring the environmental footprint for a wider audience than the traditional inter costumers • Opening planning and booking • The logistic service provider (Shipper cooperation) produces 5 use cases • Focused on Optimization of the use of resources in the supply chain • Thanks to an advanced cross-docking service • But also about monitoring of emissions using sensors (onboard devices)

10. Deliverable D5.2: Business Innovations • Collaborative planning From “As is” into “to be”, links with iCargo Business Innovation • Sea-City-Air-Rail (SCAR) • The green corridor • The logistic service provider (Shipper cooperation) • Re-planning of logistic chains by the client • Dynamic replanning based on situational awareness • Optimization of the use of resources • Monitoring the environmental footprint • Monitoring the environmental footprint

11. Deliverable D5.2: outputs (1/3) Use case specification: • Process description in the current situation. It describes the current way of operation in the Pilot Case scenario. Limitations that should be addressed by iCargo are highlighted • Process description in the desired situation. It describes the to-be way of operation in the Pilot Case scenario. For each step the role of iCargo in achieving the Pilot Case objective is highlighted • Use case description

12. Deliverable D5.2: outputs (2/3) Users requirements definition: • Based on the specified Use Cases, requirements have been defined for the functionalities to be provided by, or through, the iCargo ecosystem IT infrastructure • The requirements have been reviewed and refined through dedicated conference calls and meetings with the users, leading to a final list for each Pilot Case

13. Deliverable D5.2: outputs (3/3) Users requirements consolidation and validation: • Consolidation: the collected User Requirements are analysed to rule out pilot-specific requirements that will be addressed entirely at the pilot level, since they do not affect the functionalities of the iCargo ecosystem infrastructure • Validation: user requirements are mapped onto the High-level Functional Requirements. The mapping indicates the relations between the functional requirements that will drive the implementation of the solutions provided by the technical packages, and the needs for the implementation of the pilot cases

14. Next steps • Start: T5.2 (IPBO), T5.3(Stora Enso), T5.4 (Unilever/DHL) • Detailed design specification describing specific logistic objects and services to be implemented and integrated with iCargo. • One by each pilot: D5.3, D5.4, D5.5. M24 • Possible face to face meeting to start the pilots

15. THANK YOU! Jose Gato Luis AtoS Research & Innovation TechnicalCoordinator T +34 912064377 Jose.gato@atosresearch.eu www.atosresearch.eu

16. WP5 • AUXILLARY SLIDES

17. D5.1 Business Cases specif. • Released M3/M5 • Delivered in two parts (Feb 2012, Apr 2012) • Contributors • ATOS, BLUEGREEN, MARLO, IPBO, DHL, INTRANS, STORAENSO…. ????

18. D5.2 Pilot user requirements • Released M13 (expected for M12) • Slight deviation • Inputs: D5.1, D1.3 (vision to inspire user’s requirements, D1.2 (as high level req.) • Contributors • ATOS, BLUEGREEN, MARLO, IPBO, DHL, INTRANS….???

19. D5.1 Business Cases specif. • Outcomes • Business descriptions in each pilot • Who the users are, what are their objectives, how iCargo elements will help to achieve this objectives • To define from a strategic viewpoint what are the value-creating activities that iCargo will aim to support • iCargo Value Chain shows actors (roles) and how they interact to provide their services • Pilots depicted with this value chain • “Jobs to be done” by each role and pilot. With features and barriers • Input for D5.2 requirements

20. D5.2 Pilot user requirements • Outcomes • Specific user’s requirements regarding the pilot • “As is” and “to be” analysis • Changes to be done in the processes to achieve “jobs to be done” • Use cases • Modeling changes • Requirements: • Common: requested by pilots but considered as part of iCargo objectives • Specific: are particular of a specific pilot and are considered of no interest outside the pilot itself • Outcome for the pilots implementation • Outcome as requirements to be validated on D1.5 • Only common requirements • As continuation of the job done in this deliverable

21. D1.1 D1.2 D1.3 D1.4 iCargo Requirements (Linking) M12 M6 ✔ M3 iCargo Vision Common Framework Specific. ✔ Policy, Market and Technology survey ✔ D1.2 D2.1b iCargo components design (version 2) Consolidated high-level requirements ✔ ✔ D1.2 D3.1 Orchestrated iCargo application objects D2.1a D1.2 ✔ iCargo components design (version 1) D4.1a D1.2 ✔ Infrastructure archit. and design ✔ D1.2 D5.1 Business cases specification ✔ D1.2 D7.2 ✔ Reference Business Models D1.2 D5.2 Pilot user requirements ✔ D7.1 D1.2 Market analysis ✔

22. iCargo Requirements (Linking) • WP1 High Level Requirements • Global vision of iCargo regarding requirements, features, business innovation, etc • Collect, summarize and wrap req. • Guides to be followed by the entire project • WP2, WP3, WP4 Oriented to low-level technology • Technological requirements and tools/platforms/software • WP1 Compliance

23. iCargo Requirements (Linking) • WP5 Requirements focused on the pilots • Business and specific requirements detailed according to each pilot needs • Features provided by iCargo -> WP1’s compliance • Features to be developed only inside each pilot’s scope -> Specific Requirements not covered by iCargo

24. M18 M1 M12 iCargo Requirements (Linking) WP1 WP1 Final Consolidated Requirements WP1 High Level Req and Vision D1.2 D1.5 D1.3 Technicalvision WP2, WP3, WP4 WP5 WP5Pilots Implementation WP5Pilot user requirements WP5Business Cases Specifications D5.1 D5.2

25. M12 M18 M1 iCargo Requirements (Linking) WP1 WP1 Final Consolidated Requirements WP1 High Level Req and Vision D1.5 D1.2 D1.3 Technicalvision WP2, WP3, WP4 WP2 Components WP3 Apps WP4 Infrastructure D2.1b D3.1 D4.11 WP5 WP5Pilots Implementation WP5Pilot user requirements WP5Business Cases Specifications D5.1 D5.2

26. Value Chain For Pilot 3

27. Jobs to be done Pilot 3

28. Requirements example – Pilot 1

29. WP Efforts Distribution • Currently on M18

30. Partnert’s participation

31. Deliverable D5.1: outputs (1/3) Value chain of the Sea-City-Air-Rail door-to-door service (SCAR) pilot

32. Deliverable D5.1: outputs (2/3) Value chain of the Green Corridor between Sweden and the European Continent pilot

33. Deliverable D5.1: outputs (3/3) Value chain of the LSP-Shipper Cooperation on the Continent pilot