W2B - Digital Protocols &

Platforms for Interconnected

Logistics

28 May 2014 Tomasz Dowgielewicz and Giancarlo Tretola

Data structuration for PI: is EPCglobal enough or is the IoT the

solution?

Foreword Data structuration for PI

• The question: is EPCglobal enough or is the Internet

of Thing the solution?

• To answer this question it is important to consider two

points, in terms of collaboration between participant in

a PI scenario:

• The Interoperability needs a supporting ICT approach

for information exchange, which defines data

organization, access roles and covers security issues;

• It is important to consider all the objects and various

assets in the logistics processes (location, warehouse,

trucks, trailers, driver, etc.) it is no only a question of

goods to be shipped

2

Physical internet manifesto Internet of things is important for the Physical internet but is not enough

3

EPCIS EPC Information System

4

Supporting standards

Unique identification of all the elements of the logistics scenario, communication enabling

5

• XML and XSD

• EDI

• UBL

• UPU

Common Framework

OLI Model Matching the proposed approach with the OLI Model

7

Layer OSI model: Digital Internet TCP/IP model:

Digital Internet

OLI model:

Physical Internet CF

1 Physical Physical Physical TS

2 Data Link Data Link Link TPS

3 Network Network Network

4 Transport Transport Routing TEP

5 Session

Application

Shipping TS/TPS

6 Presentation Encapsulation

7 Application Logistics Web TSD

EPCIS: Supporting

T&T, units handling,

error corrections

e-Freight Common

frameworks support,

interoperapility, data

sharing, multimodal

waybill

e-Freigh the Common Framework The e-Freight Ontology and the conceptual Canonical Data Model EAI Pattern

8

P2Pm

P1

P5

P4

P3

P2Pm

P1

P5

P4

P3

e-freightontology

Modulushca Common Data Model The common data model and related roles

9

MBox

QR CodeRFIDGPS Positioning: Track the Truck(Russian Dolls approach)

MBox Data

UUIDSizeWeightFragilityPerishibilitySpecial environment(s)

Network flow

Public routing info:- GINC- destination address

Business flow

Reserved informationto be exchanged onlybetweensender andreceiver:ID_order- invoice- acknowledge- missing items- ETA

Shipment flow

Protected businessrelated info:- GSIN- sender identity- receiver identity- source address- description of goods- value- time-window

IT Systems

UUIDFederated DB

Examples of data declaration types

Business Data

Shipment Data

Network Data

Public Data

Manufacturer,Retailer

Shipper (4PL),Custom authorities

LSPs, Carriers(3PL)

MBox handlers,Warehouse

Modulushca proposed architecture

10

A potential reference architecture for interoperability leveraging EPCIS and eFreight

Conclusion

• So the answer to the original question is:

• We need both of them, EPCIS and IoT, furthermore

we also need more!

• We need conceptual framework for supporting the

interoperability and data exchange

• We need semantics for enabling scalable and

robust information exchange

11