FInest Future Internet enabled Optimisation of Transport and Logistics (T&L) Business Networks FI PPP Use Case P

1. FInest Future Internet enabled Optimisation of Transport and Logistics (T&L) Business NetworksFI PPP Use Case Project Contact (Project Coordinator) Dr. J. Rod Franklin Kuehne + Nagel Management AGrod.franklin@kuehne-nagel.com Presenter: René Fleischhauer (SAP)

2. Agenda • Project Overview • Motivation & Solution Requirements • Platform Concept • Project Structure • Use cases & To-be scenarios • Conceptual Architecture • High-Level Architecture (incl. design decisions) • FInest Experimentation Environment • GEs for Platform-Level Technologies • GEs of Applications & Services Ecosystems Chapter • GEs of Security Chapter • GEs Used by FInest Modules • Business Collaboration Module (BCM) • Transport Planning Module (TPM) • Event Processing Module (EPM) • eContracting Module (EPM) • The End • Communication with FIWARE • Summary GE Usage of FInest

3. Part I : Project Overview

4. The Consortium

5. Motivation (1) Relevance of Transport & Logistics • Economical impact • 7% of the EU GDP • 5% of total EU employment • Ecological impact • ~15% of the global greenhouse gas caused by transportation • Transport-caused emissions • Increased by 50% in 2010 (compared with 1990) • Expected to double again by 2030

6. Motivation (2) Pressing problems • Limited visibility on T&L processes and critical events hampers business network efficiency and effectiveness • Closed logistic supply chains hinders agile inter-organizational information exchange and collaboration and access for SMEs • Highly manual processes, lack of standards, legal and governmental regulations(“tons of paper”)

7. Solution Requirements Requirement 1 Efficient support for inter-organizational collaboration and contracting in cooperative business networks Requirement 2 Seamless integration of information and data along with real-world data acquisition

8. Platform Concept

9. Project Structure WP Dependencies (refinement to DoW, cf. D3.1 p.14) WP 9 – FI PPP Alignment WP 10 – Management +

10. Use Case I Perishable Goods Shipments – Fish Transport

11. Use Case II Industrial Goods Shipment - Airfreight

12. Use Case III End-to-end Consumer Goods Shipment (Import/Export)

13. To-be Scenarios • Analysis of use case requirements and main challenges lead to consolidation • Clear similarities • Based on this: Development of to-be scenarios which target most of the challenges & requirements • To-be scenarios show examples for what shall be enabled by FInest

14. To-be scenario 1: Handling of Late Cancellation BEFORE AFTER

15. To-be scenario 2: Resource Coordination BEFORE AFTER

16. To-be scenario 3: Real time event handling BEFORE AFTER

17. To-be scenario 4: ePlanning (transport order mgt) BEFORE AFTER

18. To-be scenario 5: Automated shipment tracking BEFORE AFTER

19. Part II : Conceptual Architecture

20. Overview Conceptual Architecture • Architecture Model • Specification of interactions • Design of core modules • Design Decisions • Backend Integration • Data Interchange • Security • Publications • R. Franklin et al. “Future Internet technology for the future of transport and logistics (invited),” in ServiceWave 2011 • Metzger, A. et al. “Predictive monitoring of heterogeneous service-oriented business networks”, SRII Global Conference, 2012 • R. Franklin et al. “Cloud Based Collaboration Platform for T&L Business Networks, 6th Int’l Scientific Symposium on Logistics, 2012

21. Conceptual Architecture (1) Shipper Forwarder Carrier (e.g., Airline) Transport Planner … … Front EndLayer Multi-Channel Messaging (SMS, E-Mail, Social Networks) Customizable Web Portal (using Gadgets á la iGoogle) User-/Identity Mgt. & Access-Control Module Layer Back EndLayer Secure Storage & Backup Service-based System Integration IoS and IoTMonitoring Legacy Systems 3rd-party services Smart Items Legacy Systems 3rd Party Services Smart Items

22. Conceptual Architecture (2) Notifications and request for actions Module Layer Profiles of potential business partners Business CollaborationModule (BCM) Transport execution data Final status & data of completed transport process Transport execution plan Situationsto monitor / rules(e.g., ETA of transport leg) Detected situation(e.g., SLA violation /timing violation/proof of delivery) Events about transport process E-Contracting Module(ECM) Event Processing Module(EPM) (Re-)planning trigger Information aboutactual bookingsand changes List of matching contracts(long-/short-term) Offers and demands from spot-marketplaces Transport Planning Module(TPM) Events (from IoS& Legacy: EDI etc.) Events (from IoT) Transport bookings

23. Design Decisions (1) • Backend / Legacy • Coverage of actual execution of transport (e.g., handling of actual documents, e.g., eAWB) not part of the collaboration space • We will use existing systems (e.g., for creating AWBs / using EDI systems / marketplaces) as black-boxes and integrate them via back-end • FInest platform will observe events about the change of such documents and possibly link to those documents (but will NOT handle actual documents), i.e., similar to Cargo 2000 • Security, (Privacy) and Trustworthiness • Rely on FI-WARE GEs in “SPT” Chapter (incl. specific FInest feature requests) • Three dimensions of SPT: • Front-end (access-based) • Back-end (access-based) • Artifact-based (business entity-based) in the BCM

24. Design Decisions (2) Transport Chain Plan (TCP) • Data Interchange Format • Basis for interchange format: Common Framework • Defined by EU projects FreightWiseand eFreight and serves as the basis for ongoing standardization efforts within GS1 • Main modelling concepts • TCP = FInest addition • TSD will be mapped to USDL ( FI-WARE) Goods Item Itinerary (GII) 0..1 planned leg 1..* Transport Execution Status (TES) Transport Execution Plan (TEP) 0..* Transport Service Description (TSD) 1..1 0..1 1..1 TEP status booked TSD

25. Experimentation Environment

26. Part III : GEs used by FInest Platform

27. GEs for Platform-Level Technologies (1) • Relevant FIWARE chapters for FInest: • Architecture of Applications and Services Ecosystem and Delivery Framework • Security • Cloud Hosting • Interface to Networks and Devices (no specific GEs were identified so far)

28. GEs for Platform-Level Technologies (2) Architecture of Applications and Services Ecosystem and Delivery Framework: • FInest modules provide individual functionality and can be used independently • App/Eco GEs are used from the Customization Tools and Middleware Mgt. to provide the FInest modules as SaaS solutions • USDL • Repository • Marketplace • Registry • Mediator • Composition Editor • Composition Execution • Service description by USDL • Service provisioning and consumption through Repository, Registry • Service marketing via Marketplace • Customization through different service composition (Editor, Executor) • Orchestration and configuration by Mediator

29. GEs for Platform-Level Technologies (3) Security: • FInest has heavily relies on sophisticated security mechanisms • Logistics processes often entail a variety of different stakeholders • Sharing specific data while keeping confidential business data undisclosed • Needed Technologies • GEs for Security • Identity Management • Security Monitoring • Optional GEs for Security • Anti-Malware • Secure Storage FInest Security Framework • Additional required technologies • BYOD Security (security mechanisms for Bring-Your-Own-Device concept) • Document Right Management (Integrate access rights in documents before exporting [e.g. Invoice, contract]) • Network Security Solutions (Next Generation Firewall, IPS, Database + Application Firewall, VPN, DDOS Prevention)

30. FInest Security Framework Potential GEs from the initial FI-WARE architecture • Identity Management Generic Enabler • Security Monitoring Generic Enabler Requested Generic Enablers • Anti-Virus Malware Detection Optional Generic Enabler • Secure Storage Service Optional Generic Enabler • Security Access Control

31. GEs for Platform-Level Technologies (4) Cloud Hosting: • Hosting of FInest platform important and not trivial issue • Module deployment shall support different cloud infrastructures • How to enable a common platform deployed in heterogeneous cloud infrastructures? • Possible with provided GEs? • If yes, which GE(s) will be responsible? • Scope of provided GEs: • Deployment Mgt. by FIWARE? • What have to provide the use case project by their own?

32. Part IV : GEs used by FInest Modules

33. Business Collaboration Module – BCM (1) Overview & Aim • Design, specify and provide a conceptual prototype of the ‘Collaboration Manager’ • Envisioned Capabilities • Central management of all relevant information for the execution of multi-party logistics processes (enabling global view) • Facilitating consistent data management and information privacy throughout T&L business networks • Exploiting entity-centric modeling as new ‘approach’ for enabling this

34. Business Collaboration Module – BCM (2) Conceptual Architecture

35. Business Collaboration Module - BCM (3) Potential GEs from the initial FI-WARE architecture: • Data/Context Management Architecture • Big Data Analysis • SQL/Non-SQL Storages • Cloud Hosting Architecture • Object Storage Requested Generic Enablers • Multiple Source Analysis (Epic): Analysis of big data sets at near real-time • Analyze data of stored logistics processes and provide information to the user (statistics, crosscutting data quires) • Trusted Object Storage (GE): Extension of Object Storage to enable the trusted storage within an cloud-based infrastructure • Store highly confidential stakeholders information only in a trusted environment • Workflow Execution Engine (GE)

36. Transport Planning Module – TPM (1) Overview & Aim • Aim: Design, specify and provide a conceptual prototype of the ‘Transport Planning Module’ • Envisioned Capabilities • Describe how the TPM can contribute to the collaboration platform to achieve more efficient planning processes • Creation and maintenance of Transport Execution Plan (TEP) through usage of: • Updated Status Information • Updated Transport Services and Transport demand • Utilization of marketplace functionality including match making

37. Transport Planning Module – TPM (2) Conceptual Architecture

38. Transport Planning Module – TPM (3) Potential GEs from the initial FI-WARE architecture • Data/Context Management Architecture • Big Data Analysis • SQL/Non-SQL Storage • Cloud Hosting Architecture • Object Storage • DCRM Requested Generic Enablers • Optimization Models andExecution: Set up optimization models and execution of the models • GUI Platform:Create a graphical view of the workflow; give a picture of the process execution at certain points in time • APPS • Mediator • CompositionExecution • Repository

39. Event Processing Module – EPM (1) Overview & Aim • Collect events from various sources, and perform what is known as complex event processing (CEP) on them • by detecting situations of interest based on the logistic plan, and notify them to the business collaboration module (BCM) or FInest front-end. • Objective: Provide end-to-end visibility and monitoring of the logistic processes and the ability to respond to changes and deviations in a timely manner.

40. Event Processing Module – EPM (2) Conceptual Architecture Event Processing Module (EPM) Rules definition Monitoring requirements Rules Event Detected Situation Runtime engine (Source 1) … Running Process Status Event (Source n )

41. Event Processing Module – EPM (3) Potential GEs from the initial FI-WARE architecture • Publish/Subscribe Broker GE (Data/Context chapter) – addresses required capabilities #1-3 • Complex Event Processing (CEP) GE (Data/Context chapter) – addresses required capabilities #4 Requested Generic Enablers capabilities • IoT Event Subscription: Subscription mechanism to events or data produced by things such as devices or sensors • Capture andCollect Events:Collect data from various sources • DisseminateDerived Events:Allow distribution of events to consumers which are interested in that event. • Event Processing: Configurable event processing engine • Advanced Analytics: e.g. mining, predictive models, optimization engines, that can be linked to FInest proactive event-driven capabilities

42. eContracting Module – ECM (1) Overview & Aim • Support logistics stakeholders in semi-automatically establishing and managing contracts. Interpretation of contract information during execution because the contract itself is not available in an online form during its execution process Exact contract information UK Far East Leg 2: Vessel Leg 3: Truck Leg 1: Truck …

43. eContracting Module – ECM (2) Conceptual Architecture

44. eContracting Module – ECM (3) Potential GEs from the initial FI-WARE architecture • USDL Tooling for modeling of logistics contracts (Application/Services Ecosystem & Delivery) • Marketplace (Application/Services Ecosystem & Delivery) • (Repository) (Application/Services Ecosystem & Delivery) Requested Generic Enablers • SLA & Contracts Storage and Retrieval: Store SLAs and contracts and mechanisms to retrieve information from those SLAs and contracts

45. Part V : The End

46. Questions regarding GEs • How are GEs are hosted and how can they be accessed? • Distribution of GE-Software (Releases via Website, Access to Version-Control, …) • Installation and Setup (Manuals will be available?) • Assure quality and scalability • Access to GEs: Restricted by user, group, … • Details to the FIWARE Test Bed? • Details to FIWARE Tools? • How to use • When finished

47. Collaboration with FI-WARE • Short-term communication with FIWARE needed to enable efficient development based on GEs • Existing communication with FIWARE should be intensified • Use case projects are early customers of FIWARE • Our wish: More pro-active interaction highly desired • Our proposal: Establishing FIWARE User groups

50. FInest Usage Scenario I End-user Transport Planner Logistic Service Provider … Order Plan Shipment Front End User Management & Access Control Integrated User Interfaces Scenario 1 Core Modules trigger user action (during exec.) notification (for decision making) events (manual) parameters (for monitoring) Business Collaboration(BCM) Event Processing(EPM) status updates (during exec.) events (automated) transport plan (after planning) contract status (for updates) exec. status (for re- planning) contract data (manual) transport-relevant data Transport Planning(TPM) contract details (for planning) E-Contracting(ECM) contract usage (for updates) planning-relevant data contract data (automated) Back End Cloud Deployment & Management Service-based System Integration IoS and IoTMonitoring “Setup transport planfor customer-initiatedorder” Legacy Systems Smart Items Business Systems 3rd Party Services Smart Items ….