contact (project coordinator) dr. j. rod franklin kuehne + nagel management ag...

Contact (Project Coordinator) Dr. J. Rod Franklin Kuehne + Nagel Management [email protected]

Presenter: René Fleischhauer (SAP)

FInest Future Internet enabled Optimisation of Transport and Logistics (T&L) Business Networks

FI PPP Use Case Project

mailto:[email protected]

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

Part I : Project Overview

3

The Consortium

4

Motivation (1)

•

• 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

Relevance of Transport & Logistics

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”)

Solution Requirements

Efficient support for inter-organizational collaboration and contracting in cooperative business networks

Requirement 1

Requirement 2

Seamless integration of information and data along with real-world data acquisition

Platform Concept

8

Project Structure

9

WP Dependencies (refinement to DoW, cf. D3.1 p.14)

WP 9 – FI PPP

AlignmentWP 10 – Management

+

Use Case I

10

Perishable Goods Shipments – Fish Transport

Use Case II

11

Industrial Goods Shipment - Airfreight

Use Case III

12

End-to-end Consumer Goods Shipment (Import/Export)

• Analysis of use case requirements and main challenges lead to consolidationClear 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

To-be Scenarios

13

14

To-be scenario 1: Handling of Late Cancellation

BEFORE AFTER

Business Role Before AfterShipper Flexibility in booking More commitment to booking

Incentive for more accurate planning Possible last minute booking

Carrier Cancellations Low visibility of demand Late cancellations Late information Low environmental efficiency

Active search of customer (last minute) Improve use of capacity Higher income Higher environmental efficiency

Terminal Frequent changes in discharge/loading list

Less changes, less booking cancellations. Possibilities to book replacement cargo

15

To-be scenario 2: Resource Coordination

BEFORE AFTER

Business Role

Before After

Port Service info presented on website arrival & departure notified by AIS system Port call registered by port

Services accessible through a common portal for ports AIS information directly retrieved by the portal Port call registered automatically in back-end system

Captain / Ship agent

Port call registered in SSN, and notified to port Booking of services by email/phone/fax/radio No overview of capacity available

Port call centralised All booking online, with access to real time information

Terminal Some integration between terminal and port No overview of inventory available for carrier

Completed integration and info sharing about resource planning

General Multiple information sources One-to-one communication

Centralized information source EDI integration and automatic information sharing

16

To-be scenario 3: Real time event handling

BEFORE AFTER

Shipment execution Before AfterTrucking to Xiamen. Forwarder and Carrier are not always aware of

changes in booking, causing a lot of hick ups Forwarder and Carrier are immediately aware of changes and

can determine how to deal with these changes Handling of changes / replanning is facilitated and accelerated

Consolidating of shipments in to the carrier's warehouse

The forwarder receives different actual freight than originally booked. This is causing problems for efficient consolidation.

Gap between actual freight and booking, but early notification enabled the forwarder to update plan

Air transport, including handling by carrier

Surprises occurs at delivery to (more freight then planned)

No more/less surprises occur because both forwarder and airline are informed about the changes.

Pick up, custom declaration, deconsolidation

No information given to the forwarder at the airport of destinations, resulting in a gap between capacity reservation and actual need.

The forwarder was aware of the changes and adapted his number of pick-up trucks .

Forwarding to the consignee

The consignee doesn’t get his freight on time in full because freight capacity not available

Freight on time in full, because early communication between Shipper, Forwarder and Carrier, and correct replanning

17

To-be scenario 4: ePlanning (transport order mgt)

BEFORE AFTER

Business Role Before AfterShipper Manual process of data collection

Data is collected from many different sources which have different formats

Time delays in information input Hard to track updates Manual data processing for forming a cost

overview

Online service description connected to booking application Automated data gathering Automatic pre-cost estimation Visibility of historical usage on the time of purchasing Effective contract management Visibility on environmental impact Collaboration among partners who work on the same transport chain plan

18

To-be scenario 5: Automated shipment tracking

BEFORE AFTER

Business Role Before AfterShipper Manual input from LSPs about the status of the cargo

Time delays in information input Lack of automated alert system for deviations

Automated input from tracking systems Information is visible to the parties that have authorization

at the same time Timely notification of deviations

Part II : Conceptual Architecture

19

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

Module Layer

E-Contracting Module(ECM)

Event Processing Module(EPM)

Business CollaborationModule (BCM)

Transport Planning Module(TPM)

Front EndLayer

Back EndLayer

List of matching contracts(long-/short-term)

Detected situation(e.g., SLA violation /timing violation/proof of delivery)

Information aboutactual bookingsand changes

(Re-

)pla

nnin

g tr

igge

r

Tran

spor

t exe

cutio

n pl

an

Situationsto monitor / rules(e.g., ETA of transport leg)

Smart ItemsSmart ItemsLegacy SystemsLegacy Systems3rd-party services3rd Party Services

Service-based System Integration

IoS and IoTMonitoring

Events(from IoT)

Multi-Channel Messaging (SMS, E-Mail, Social Networks)

Customizable Web Portal (using Gadgets á la iGoogle)

User-/Identity Mgt. & Access-Control

Notifications and request for actions Profiles of potential business partners

Events(from IoS& Legacy:EDI etc.)

Events about transport process

Secure Storage &Backup

Offers and demands

from spot-marketplaces

Final status & data of completed transport process

…Shipper Transport Planner Carrier (e.g., Airline)Forwarder

…

Transport bookings

Transportexecution data

Module Layer

Front EndLayer

Back EndLayer








…

Shipper Transport Planner Carrier (e.g., Airline)Forwarder

…

Conceptual Architecture (1)

Module Layer








(Re-

)pla

nnin

g tr

igge

r

Tran

spor

t exe

cutio

n pl

an


Events(from IoT)




Offers and demands



Transport bookings


Conceptual Architecture (2)

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

23

Design Decisions (2)

• Data Interchange Format• Basis for interchange format: Common Framework

• Defined by EU projects FreightWise and 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)

24

1..*

Transport Execution Plan(TEP)

Transport Service Description

(TSD)

Transport Execution Status(TES)

Goods Item Itinerary

(GII)

Transport Chain Plan(TCP)

0..1

1..1 0..*0..1 1..1

planned leg

booked TSD

TEP status

Experimentation Environment

25

FI-WARE

FInest test

Finest simulation environment

invokes

Test design workbench

Simulation engine

Test design workbenchtest

designtest

designtest

designtest

designtest

designtest

designtest

designtest

designtest

designtest

designtest

designtest

designtest

designtest

designtest

designtest

designtest

configuration

executionmanagement

accessmanagement

datamanagement

resourcemanagement

tests events resourcesparticipants, roles,

and access privileges

R

Test user interface

reporting

policies and regulations

sensor and operational

data

physical test sites

KPIs

FI-WARE

FInest test

Finest simulation environment

invokes

Test design workbench

Simulation engine

Test design workbenchtest

designtest

designtest

designtest

designtest

designtest

designtest

designtest

designtest

designtest

designtest

designtest

designtest

designtest

designtest

designtest

designtest

configuration

executionmanagement

accessmanagement

datamanagement

resourcemanagement

tests events resourcesparticipants, roles,

and access privileges

RRR

Test user interface

reporting

policies and regulations

sensor and operational

data

physical test sites

KPIs

Part III : GEs used by FInest Platform

26

• 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)

GEs for Platform-Level Technologies (1)

27

Architecture of Applications and Services Ecosystem and Delivery Framework:


28

• 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

Security:


29

• 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

• 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)

FInest Security Framework

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

Cloud Hosting:


31

• 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?

Part IV : GEs used by FInest Modules

32

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

Business Collaboration Module – BCM (1)

33

Conceptual Architecture

Business Collaboration Module – BCM (2)

34

Business Collaboration Module (BCM)

Notification & Action Trigger

Standard Process Repository

Process Engine

Collaboration ObjectManager

External Data

Importer

Secu

rity

& P

rivac

y M

anag

er

Notifications & Requests

Additionaltransport relevant

dataTransport plan

User Information & Profiles

BCO events Monitoring event types

Final Transport Status

CollaborationObject Storage

TransportEvents

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)

Business Collaboration Module - BCM (3)

35

Transport Planning Module – TPM (1)

36

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


InterfaceManager

Transport Planning Engine

TransportDemand

Replanning

Transport Search/

Optimization/Selection/

Configuration

TCP to BCM and ECM

(Re)-planning trigger from BCM

R

Transport Planning and Re-planning Module (TPM)

Contract and TSD/Marketplace searchContract and TSD/Marketplace details

TPM Storage

TransportBooking

TEP requests to Booking SystemsTEP response from Booking Systems

R

Transport Demand

R

Transport Demand Updates

LSCTSD, TEP and TCP

Maintenance

Frontend/Backend


38

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 and Execution: 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

Event Processing Module – EPM (1)

39

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)

…Running ProcessStatus

Event)Source 1(

Event)Source n(

Detected Situation

Monitoring requirements

Runtime engine

Rules Rules definition



41

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 capabilities1. IoT Event Subscription: Subscription mechanism to events or data produced by things

such as devices or sensors2. Capture and Collect Events: Collect data from various sources 3. Disseminate Derived Events: Allow distribution of events to consumers which are

interested in that event. 4. Event Processing: Configurable event processing engine 5. Advanced Analytics: e.g. mining, predictive models, optimization engines, that can be

linked to FInest proactive event-driven capabilities

eContracting Module – ECM (1)

42

Overview & Aim Support logistics stakeholders in semi-automatically establishing and managing

contracts.

Leg 1: Truck Leg 2: Vessel Leg 3: Truck

…

Exact contract information

Interpretation of contract information during execution because the contract itself is not available in an online form during its execution process

Far East UK


43



44

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

Part V : The End

45

1. 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, …

2. Details to the FIWARE Test Bed?3. Details to FIWARE Tools?

How to use When finished

Questions regarding GEs

46

• 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

Collaboration with FI-WARE

47

THANK YOU!

48

Appendix

49

FInest Usage Scenario I

“Setup transport planfor customer-initiatedorder”

Core Modules

Front End

Back End

…

End-user Transport Planner Logistic Service Provider

Order Plan Shipment

Smart ItemsSmart ItemsLegacy SystemsBusiness Systems 3rd Party Services



….

Integrated User Interfaces

User Management & Access Control

Cloud Deployment & Management

transport plan (after planning)

exec. status (for replanning)

parameters (for monitoring)

status updates (during exec.)

contract details (for planning)

contract usage (for updates)

contract status (for updates)

E-Contracting(ECM)

Event Processing

(EPM)

Business Collaboration

(BCM)

Transport Planning(TPM)

trigger user action (during exec.)

notification (for decision making)

events (manual)

events (automated)

contract data (manual)

contract data (automated)planning-relevant data

tran

spor

t-re

leva

nt d

ata

Scenario 1

FInest Usage Scenario II

“Monitor cargoand respondto deviations”

Core Modules

Front End

Back End

…


Order Plan Shipment




….











E-Contracting(ECM)

Event Processing

(EPM)


(BCM)




events (manual)

events (automated)



tran

spor

t-re

leva

nt d

ata

Scenario 2

FInest Usage Scenario III

“Establishnew blanketcontract withtransport provider”

Core Modules

Front End

Back End

…


Order Plan Shipment




….











E-Contracting(ECM)

Event Processing

(EPM)


(BCM)




events (manual)

events (automated)



tran

spor

t-re

leva

nt d

ata

Scenario 3

SummaryUsage of GEs by FInest

Core Modules

Front End

Back End

…


Order Plan Shipment




….











E-Contracting(ECM)

Event Processing

(EPM)


(BCM)




events (manual)

events (automated)



tran

spor

t-re

leva

nt d

ata

Premise (Charging, Billing, Payment, …) + Revenue Sharing

Aggregator (composition & mashup)

USDL to describe „real-world“ T&L services (business value, legal, financial, …)

Channel maker (devices & channels) & Aggregator (UI mashup)

Broker (T&L service marketplaces)

SLA management

Outdated!

FInest Collaboration Space (1)

Future Internet Core Platform

NoF IoT IoC IoS

Real World Integration

Service Provisioning & Consumption

Ubiquitous Broadband

Connectivity

Information Integration & Processing

SPT

Security & Reliability

Generic Enablers

…

…

T&L Stakeholders

…

FInest Transport and Logistics

Collaboration SpaceDeployed in

the Cloud

55

K&N joined the FInest platform

Kühne & Nagel, one of the worlds largest

logistic service providers, adopted the

FInest

platform

AFKLM joined the FInest platform

Air France KLM Cargo joined the user

group for the FInest collaboration services

Paluno to offer eContracing App

Paluno (the Ruhr Institute for Software

Technology) offers a novel eContracting

app and gadget for the FInest platform…

SAP to deploy first FInest instance

SAP is to offer the FInest platform

services as part of their business by design

portfolio

e.g., eContracting Gadget: Search for offers (contracts) matching empty capacity

FInest Collaboration Space (2)

High-level Architecture

56

Module Layer





Front EndLayer

Back EndLayer




(Re-

)pla

nnin

g tr

igge

r

Tran

spor

t exe

cutio

n pl

an





Events(from IoT)








Offers and demands



…

Shipper Transport Planner Carrier (e.g., Airline)Forwarder

…

Transport bookings


The information in this document is proprietary to the following FInest consortium members funded by means of European Union within the 7th Framework Program: SAP AG, IBM Israel – Science and Technology Ltd, Kuehne + Nagel Management AG, Norsk Marinteknisk Forskningsinstitutt AS, Universität Duisburg-Essen, Ålesund Kommune, Tyrholm & Farstad AS, Arcelik A.S., KocSistem Bilgi Ve Iletisim Hizmetleri A.S., North Sea Container Line AS, Koninklijke Luchtvaart Maatschappijnv. The information in this document is provided "as is", and no guarantee or warranty is given that the information is fit for any particular purpose. The above referenced consortium members shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials subject to any liability which is mandatory due to applicable law.

57

contact (project coordinator) dr. j. rod franklin kuehne + nagel management ag...

Documents

management slide

replacement cargo slide

booking cancellations

business network efficiency

transportation transport

challenges requirements

contact project coordinator

tl processes