recommended dgt system architecture by the unece joint...

Recommended DGT System Architecture by the

UNECE Joint Meeting and the availability of the entire

electronic transport document in case of accidents

Christian Lüpges

AlbrechtConsult GmbH

eCall implementation for Heavy Goods Vehicles

Rotterdam, 5th July 2017

2017/07/05 AlbrechtConsult GmbH 1

Background

The UNECE Joint Meeting*) has mandated an informal WG on Telematics – this group has created a tabular description of relevant Dangerous Goods data, including references to stakeholder roles and use cases

Germany has launched a study in 2010 to consider the role that Telematics could potentially play in Dangerous Goods Transport –further national projects in DE and FR have validated the conclusions and elaborated a system architecture for a Telematics system supporting the transport of dangerous goods

The results of these studies have been reported to WG Telematics

The principle approach was to start with a system that deals with the data that is already covered by the regulatory frameworks, i.e. the data currently contained in the transport documents (e.g. ADR 5.4) –the system architecture is designed in a way that allows future extensions

In September 2013 the proposed system architecture has been recommended by the UNECE Joint Meeting. The electronic transport document and the availability in case of accidents should be the main aspects.

*) UNECE, Joint Meeting of the RID Committee of Experts and the Working Party on the Transport of Dangerous Goods

AlbrechtConsult GmbH 42017/07/05

Telematics System – Overview and Basic Considerations


Service Provider

Internet

InteroperabilityInterface PSAP / Command & Control centreIn-House System

Trigger

External characteristics (e.g. number plate)

Complex standardisation / certificationof OBUs and devices to be avoided

Central

Management

Service

Trigger (e.g. eCall HGV)

TP2TP1

General system concept

Replace access to paper documents with (electronic, machine-to-machine) access to a back-office system (TP2). TP2…

▪ is web service

▪ can be provided by the carrier or by a service provider ( many instances of this service – needs addressing)

▪ (interface) should fit into the existing landscape of Freight & Logistics IT services use of widely accepted IT standards (e.g. web services & XML)

Provide central management service (TP1) that manages the whole information exchange between all participants (economy and authorities / emergency responders). TP1…

▪ is a central web service

▪ manages the access rights of the public bodies usage of existing Public Key Infrastructure

▪ stores temporarily characteristics of a transport e.g. VINs (tractor + trailer) / number plates / BIC-Codes

▪ forwards in case of accidents or enforcements requests of emergency responders or enforcement bodies to the appropriate TP2

▪ Access credentials can be carried by today’s / future standards for vehicle initiated emergency notification (e.g. eCall HGV)


Telematics system high-level architecture


Trusted Party 1

Management

Server

Trusted Party 2

Content Server

Authorities

PSAP / Command

& Control Centre

(e.g. Emergency

Responder)

Transport

[OBU, if available]Casual observer

Carrier

eCall HGV

Data exchange via single TP1 instance


Trusted Party 1

Management

Server

Trusted Party 2

Content Server

Authorities

Command &

Control Centre

(e.g. Emergency

Responder)

Carrier

Registered company notifies…

• Start of transport (incl. characteristics like

e.g. VINs, number plates, BIC codes),

• Access to the full transport document

• End of transport

Enforcement bodies and emergency

responders…

• are registered at TP1

• request data, when needed

(e.g. triggered by eCall)

eCall HGV

Current Status

Discussions with the EC and other international institutions (e.g.

UNECE) to operate a single TP1 haven't been successful

In 2016 Germany allowed the electronic transport document provided

by mobile device and a stationary server. Request ensured via

telephone as an initial step due to the lack of a TP1

National projects in IT (CORE) and FR (GEOTRANCEMD) have

implemented and approved the system architecture. Additionally, the

decentralised cross border data exchange between those projects

has been validated.

In May 2017 DE, IT, FR and NL discussed in a WG the requirements

for federated TP1

Private companies from DE, IT, FR will further elaborate the cross

border exchange via private TP1s

In October 2017, a further WG meeting will prepare a

recommendation for the Joint Meeting in order to harmonise the

usage of the electronic transport document.AlbrechtConsult GmbH 92017/07/05

International data exchange


Trusted Party 1

Management

Server B

Trusted Party 1

Management

Server B

Trusted Party 1

Management

Server B,C, …

Trusted Party 2

Content Server

Carrier

Trusted Party 1

Management

Server A

Authorities

Command &

Control Centre

(e.g. Emergency

Responder)

Co

un

try B

, C

, …

Co

un

try A

TP1 Country A …

• Doesn‘t know the transport.

It’s registered in the TP1 of other

countries

• Applies to the other countries‘ TP1 if

needed

?

eCall HGV

Federated management

TP1 entities know each other


Trusted Party 2.2

Content ServerTrusted Party 2.n

Content ServerTrusted Party 1.1

Management

Server

Trusted Party 2.2



Management

Server

Trusted Party 2.2



Management

Server

Trusted Party 2.2



Management

Server

Request

Cross-border data exchange via federated TP1s


TP1 Private

TP2

TP2

TP2

TP2

TP2

TP2

TP2

TP2

TP2

Emergency

ResponderEmergency

ResponderEmergency

Responder

Emergency

ResponderEmergency

ResponderEmergency

Responder

AuthoritiesAuthorities

Authorities

TP2

TP2TP2

Emergency

ResponderEmergency

ResponderEmergency

Responder

Emergency

ResponderEmergency

ResponderEmergency

Responder





Authorities

TP1 Private

TP2

TP2

TP2

TP2

TP2

TP2

TP2

TP2TP2

TP1 Private

TP1 PrivateTP1 Private

TP1 Private

Country C Region B

Country BCountry A

TP1 Public

TP2TP2

TP2

TP2TP2

TP2

Emergency

ResponderEmergency

ResponderEmergency

Responder

TP2

TP2

Emergency

ResponderEmergency

ResponderEmergency

Responder

Emergency

ResponderEmergency

ResponderEmergency

Responder


Authorities


Authorities


Authorities

TP1 Public

TP1 Public

Country C Region A

TP2TP2

TP2

Emergency

ResponderEmergency

ResponderEmergency

Responder


Authorities

TP1 Public

TP2

TP2

TP2

TP2

Federated TP1 driven by public

bodies

Federated TP1 driven by private

companies

Documentation available

Final Report

▪ Entire description of the system

architecture and trigger modes

(German)

▪ Interface specification (English)

▪ Brief system overview and design

decisions

▪ Explanation of TP1 and TP2 web

services

▪ Corresponding WSDL and XML-Schema

files

▪ Presentations (Dangerous Goods

Data Model, System Architecture)

held on the BMVBS Workshop on

transport logistic fair Munich,

5th June 2013


Update needed according to latest

discussions and results

Thank you for listening!!

Christian Lüpges

AlbrechtConsult GmbH

direct contact

Tel: +49 241 466 89 708

Mobile : +49 173 95 49 026

Fax: +49 241 500 718

[email protected]

2017/07/05 AlbrechtConsult GmbH 14

recommended dgt system architecture by the unece joint...

Documents