Corridor Information Systems Generic Concept Wout Hofman senior research scientist TNO technical support to EC DG Move/DTLF

Size: px

Start display at page:

Download "Corridor Information Systems Generic Concept Wout Hofman senior research scientist TNO technical support to EC DG Move/DTLF"

Rudolph Fields
5 years ago
Views:

Brussels, 26 April 2017 Please visit Sli.

1 Corridor Information Systems Generic Concept Wout Hofman senior research scientist TNO technical support to EC DG Move/DTLF Brussels, 26 April 2017 Please visit Sli.do and input the code #DTLF to interact with the presentation now!

2 This presentation Recapitulation Presenting the concept top down approach Discussion Recapitulation and overview of comments 2 Corridor Information Systems

3 Recapitulation activities so far regarding the concept Introducing the concept First version of the Discussion Paper An outline for a Generic concept for an innovative approach to interoperability in supply and logistics chains Discussion at SG2 meeting March Received comments 3 Corridor Information Systems

4 Recapitulation the problem Open standards: Implementation leads to closed systems Messaging replacing business documents Platforms and infrastructure Reflect the open standards approach (proprietary solutions) Various different systems and services: Difficult to compare Vendor lock-in Difficulty to expand Innovative (disruptive?) developments like blockchain - legacy of the future 4 Corridor Information Systems

5 Recapitulation why action? Policy Digital Single (Transport) Market Level playing field Inclusion of SMEs Private (and public) sector Short term: supply chain innovations Growing amounts of goods flows (ecommerce) Visibility, agility, resilience, security, safety, VAT Mid term: autonomous operating assets Autonomous barging, truck platooning, AGVs, drones, hyperloop, etc. New entrants Long term: Physical Internet Projects did not solve the problem 5 Corridor Information Systems

6 Integrated systems approach Objective to create an open infrastructure for controlled data sharing amongst logistic service providers and with their customers, meeting authority requirements Innovation in interoperability supported by an open infrastructure For any party involved (enterprise and authority) Register and connect once With a solution of choice (platform, local implementation (proprietary solution which can be based on COTS or open source) Build upon investments: Re-use of existing (open or de-facto) standards Re-use of available platforms and their functionality Technology independent the ability to incorporate innovative technology like blockchain technology and support e-documents Sli.do #DTLF Question: 1 What would be the best terminology? Infrastructure, Platform, Federated infrastructure, others. 6 Corridor Information Systems

7 Generic Concept for an innovative approach to interoperability in supply and logistics chains Elements: Architecture based on open standards with re-use of existing solutions Definition/description of core specifications for a set of services provided by a federative platform Criteria according to which specifications should be developed Data categorisation Principles of federated governance Business models for better collaboration Initiation of technical demonstrators 7 Corridor Information Systems

8 Functional requirements from a supply chain innovation perspective. Please prioritize. (spot) marketplace Open market trust and reputation Booking and ordering (transactions) Reference to a main modality A-modal booking based on Quality of Service of transport modalities and infrastructure (synchromodal) Multi-modal, different transactional relations (e.g. shipper-forwarder, forwarder-carrier, LSPrailway undertaking, forwarder-barge operator, ) Restrictions to bundling (shipments, capacity), based on competition, cargo properties, etc, Visibility delays, changes in planning, Resilience cope with accidents, incidents, maintenance, Agility last minute changes Re-planning, e.g. delays, incidents, last minute changes, Legal requirements safety, security, VAT,. 8 Corridor Information Systems

9 What should be the scope? subcontracting Bundling: business rules for subcontracting (multi-modal control tower) customer Service provider Transaction chain Registration service Market place service Booking and ordering visibility resilience Trust and reputation mgt Synchromodal Replanning Service provider Service provider agility Compliance Federated Platform Infrastructure The focus is on a bilateral collaboration between any customer and service provider. Customer goal(s) have to meet business services of service providers. Construction of a chain is based on business rules for subcontracting. These business specific rules are out of scope. Each bilateral collaboration utilizes specific platform services. 9 Corridor Information Systems Sli.do #DTLF Question: 2

10 What would be the domain? Sli.do #DTLF Question: 3 Logistics Infrastructure Compliance All modalities? All laws and regulations? 10 Corridor Information Systems

Platform services their relationship based on a choreography between customer and service provider Marketplace service Booking and ordering

Ordering delivery Visibility end LSP Adjust planning Cancel execution customer Cancel booking Agility - cancellation end Source: EU FP7 INFSO

11 Platform services their relationship based on a choreography between customer and service provider Marketplace service Booking and ordering service Agility service Visibility service end Adjust order (agility) customer Customer customer customer Start search Booking ordering Ordering delivery Visibility end LSP Adjust planning Cancel execution customer Cancel booking Agility - cancellation end Source: EU FP7 INFSO icargo Trust and reputation management 11 Corridor Information Systems The data semantics and structure is specified by logistics services (see further).

12 How can we specify these services? Example Customer Service provider booking Booking confirmation contract Booking order Plan Ordering Departed ETA update Visbility Arrival 12 Corridor Information Systems Sli.do #DTLF Question: 4

13 Extending to chains sub-contracting Customer 2 Customer 1 booking Service provider Subcontractor (carrier) Booking confirmation contract Booking Ordering order - 2 order - 1 Plan Ordering bundling order (order - 1, order - 2) Plan Ordering Visbility Visbility Departed ETA update ETA update Arrival Visbility Arrival Potential sub-contracting strategies during booking/ordering Certainty to deliver (risk reduction, inserted transactions) Certainty of availability (Framework contract with subcontractor, decoupling) 13 Corridor Information Systems

14 An example - visibility Customer perspective Shipment/consignment Actual pick up and delivery Interested in any changes of delivery (delay, damage, losses, etc.) Service provider perspective Synchromodal planning consideration of planned maintenance and accidents/incidents that may cause delays Individual shipments Actual pickup and delivery Any deviations from planning of a transport means ETA prediction Carrier perspective Location of a transport means: truck, barge, vessel, airplane or train Ability to generate many milestones including speed and direction of movement according to a route/voyage/trip/timetable Generic and mode specific milestones Considerations: Matching of customer perspective and available milestones Generic milestones for objects or scenario-based milestones, i.e. container has arrived versus container arrival 14 Corridor Information Systems

15 It all starts with registration and publication of logistics services Logistics Services Roles and services Carrier transport Stevedore transhipment DC - storage Logistics Services Logistics Service Registration Registration Services Role and name Carrier - companyxyz Transport service properties Cargo type Packaging type Cargo properties Corridor, region(s) Duration Packaging type Container Pallet.. 15 Corridor Information Systems Service properties Values Specify services Service Properties Transport Services Rhine Corridor Distribution services Rhine Corridor transport service Daily Containerized Containers Dangerous cargo 1 day (average) Registration also includes at conceptual level: Data policy controlled data access Supported (open) standards Required Identity and Authentication mechanisms (Certification Authority, policy properties, etc.) Which are the services and service providers? LSPs, carriers, etc. for all modalities and formalities Infrasrtructure Managers Sli.do #DTLF Question: 5

Relevant aspects of data governance for data

Privacy Laws and regulations Ownership and

Data processes - Data quality - Availability -

Accountability which data to share why share

16 Relevant aspects of data governance for data sharing. Privacy Laws and regulations Ownership and liability Economic sensitivity Organisation A - Data processes - Data quality - Availability - Security - Usability - Auditability - Accountability which data to share why share data security aspects technical aspects Organisation B - Data processes - Data quality - Availability - Security - Usability - Auditability - Accountability Sli.do #DTLF Question: 6 16 Corridor Information Systems

17 Will it be possible to further specify data governance by: Classification, e.g. Sli.do #DTLF Question: 7 Open data public available data Community data available to a community Transaction data shared between customer and service providers Process synchronisation data data shared between stakeholders that don t have a contract Compliance data data shared by business with authorities Internal data available to internal personeel Logistics services towards a classification Service specification open data Prices, performance, etc. transaction data Etc. Transaction data a customer is allowed to select those milestones relevant to a transactional relation with a unique identifier known to customer and 4PL For instance: consignment identification, container number Synchronisation of physical processes ETA prediction shared by carriers with terminals/hubs Commercial/customs release shared by for instance forwarder with stevedore and carrier 17 Corridor Information Systems

Logistics services and standards Logistics Services Registration Services Roles and services Carrier transport Stevedore transhipment DC - storage Logistics

region(s) Duration Packaging type Container Pallet.. Container Size and type Container number Tare weight.

agency Equipment identification Service properties Values Object types with properties (and associations) Representation by (open) standard(s) Specify services

18 Logistics services and standards Logistics Services Registration Services Roles and services Carrier transport Stevedore transhipment DC - storage Logistics Services Logistics Service Registration Role and name Carrier - companyxyz Transport service properties Cargo type Packaging type Cargo properties Corridor, region(s) Duration Packaging type Container Pallet.. Container Size and type Container number Tare weight.. UN/CEFACT WCO: Equipment Equipment qualifier Equipment size and type - Size and type - Code list - Code list resp. agency Equipment identification Service properties Values Object types with properties (and associations) Representation by (open) standard(s) Specify services Service Properties Object types (and associations) Choice for representation Transport Services Rhine Corridor Distribution services Rhine Corridor transport service Daily Containerized Containers Dangerous cargo 1 day (average) Data requirements 18 Corridor Information Systems

19 Choreography and standards The choreography consists of interactions Booking/booking confirmation/contract Order/plan Event (visibility) Cancelation request/confirmation (agility) These require a minimal data set Two approaches: Message structures common message structures leading to closed implementations (specific Implementation Guides) Per interaction a set of rules with minimal data requirements based on business services Examples Booking and confirmation refer to data requirements formulated by a logistics service (cargo type, packaging type, weight, volume, places, etc.) Order specifies details of cargo (e.g. container numbers, specific weights, expected times, vessel/flight number) Planning details on pickup and delivery (times, transport means, etc.) 19 Corridor Information Systems

20 The rules can be verified by processes of the choreography Booking request Booking confirmation customer instruction Booking Phase Cancel customer customer start Booking request Booking confirmation execution Service provider Service provider customer Conclude contract Service provider Booking request Booking confirmation Service provider instruction 20 Corridor Information Systems Source: EU FP7 INFSO icargo

21 Standards Implementation of standards leads to closed solutions Messaging paradigm replacing existing procedures and documents with electronic versions Private sector is not able to develop open systems and solutions on their own The previous slides propose a conceptual interoperability approach 21 Corridor Information Systems

22 Questions on standardization? What are requirements to standards: Open, duplicated for re-use free available to anyone in word Proprietary format like WCO data model Semi-structure in CSV (Excel) class diagram (XMI XSD) representing a model Open, by reference (ontology (OWL XSD) representing a model and rules) Others. A choice between two approaches: Message structures and implementation guides Interaction function and rules for minimal data requirements Others Standardisation of specific object types like container or generic ones like equipment. What needs to be done: Further development of logistics object types as core components Syntax independent specifications (e.g. XML, EDIFACT) Governance and development? 22 Corridor Information Systems

properties (and associations) Data requirements (view) Object types (and associations)

23 Returning back to our objectives infrastructure connection services For any party involved (enterprise and authority) Register and connect once Standards and models Object types with properties (and associations) Data requirements (view) Object types (and associations) Internal database structure(s) Representation by (open) standard(s) 23 Corridor Information Systems

24 This lead to the construction of the layered reference model Several application services are implemented by one application Federation requires a protocol between different providers 24 Corridor Information Systems Source: EU FP7 SEC CORE

25 Mapping of existing platform solutions Integration platforms (horizontal) Messaging based Transformation between various (open/de-facto) standards Publish/subscribe mechanisms Non-repudiation (especially ecmr platforms) Logistics service platforms (vertical) Logistics market places (generic or specific for cargo types like containers) Booking, ordering(, and visibility) Visibility (distributed) Registries Platform deployment providers Platform component providers Integration components - open source (e.g. FiWare, CEF building blocks) or Commercial Of The Shelve (COTS) Logistics components bundling, dynamic chain composition 25 Corridor Information Systems

26 What would be the way forward for the infrastructure? Big bang all existing platforms provide services Gradual upgrade of functionality Enrichment of the infrastructure with new components Gateways for federation Disruption by for instance blockchain technology Others, please specify Sli.do #DTLF Question: 8 26 Corridor Information Systems

27 Recapitulation First version of the Discussion Paper An outline for a Generic concept for an innovative approach to interoperability in supply and logistics chains Discussion at SG2 meeting March Received comments Re-use of existing (open or de-facto) standards Re-use of available platforms and their functionality Technology independent the ability to incorporate innovative technology like blockchain technology and support e-documents 27 Corridor Information Systems

28 Discussion points during the March meeting (see minutes): Potential conflicts between open data and controlled access to data Minimize standards DTLF should agree on data model and minimal standards Focus on facilitation of data sharing, choice of platforms by traders Decomposition of cargo flows into cargo and the transport system should be added to the model. Authority roles can be besides regulator and supervisor also facilitator Relation with existing projects Review of projects in other areas like the Industrial data space Blockchain as distributed, trusted facility to share documents without any central solution 28 Corridor Information Systems

29 Important comments on the document: Input of seven SG2 members Grouping of remarks (not all are listed) Scope of the document public and/or private sector, cargo/passengers (remark 7 (passengers), 20, 21, 28, 35, 42 The model (figure 1 remark 1, 19) Terminology (remark 6 (platform, system, infrastructure)) Innovative aspects (remark 15, 26, 27, 34, 40, 61, 62 (blockchain)) Scope of a specification (remark 2, 12, 43, 47, 48, 50, 56, 58) Governance and security (remark 10, 11, 13, 17, 18, 60) Activities (remark 32) Services, also relates to scope and how to specify (remark 38 (business services vs SOA), 51, 52, 53) (Re-use of) standards (remark 12, 14, 57, 59) Business case (remark 44) 29 Corridor Information Systems

30 Summary Integrated Systems Approach Open infrastructure meeting private (policy) and public requirements Prepared for the future Ingredients Conceptual interoperability: controlled data sharing for business requirements between any two stakeholders Infrastructure: standardized services increasing market potential of suppliers and prevent vendor lock-in 30 Corridor Information Systems

31 General remarks The approach is required! Agreed, to be able to cope with innovations No, there are sufficient solutions of an open infrastructure The approach is feasible Agreed Agreed, under specific conditions that need further specification No, while (please specify) Do not know The way forward Push by technology providers Pull from the logistics and supply chain stakeholders Push by authorities Push by the EC Joint collaboration of public and private sector Others (please specify) Requirement for a directive? Yes, if authorities drive the implementation No, there is no governance structure Others (please specify) 31 Corridor Information Systems Sli.do #DTLF Question: 9, 10, 11 & 12

Brussels, April 26th 2017

Electronic Transport Documents Team 2 a blueprint for a multimodal ewaybill Wout Hofman senior research scientist TNO (wout.hofman@tno.nl) technical support to EC DG Move/DTLF Brussels, April 26th 2017