Consistently Optimised Resilient Secure Global Supply-Chains Intermodal transport of dangerous goods demonstrator IRU GEMD meeting, Geneva 21 September 2018

CONTEXT: needs/state-of-play of telematics in Dangerous goods Dangerous goods regulated transport Business stakeholders and authorities involved, with common needs of telematics: Monitor for law enforcement, safety, efficiency, risk assessment/minimization, accidents/impacts reduction, effective emergency and intervention operations Support inter-modal transport of dangerous goods - single digital document for transport across modes (road, rail, water) Data available thanks to tracking & tracing/telematics widely adopted in operations (mainly in road) Technology maturity (for road and for intermodal transport) Accuracy and reliability can be improved thanks to advanced technical solutions enabling robust and trusted position information/tracking & tracing data Introduction of digital transport document stimulated by the ability to support different use cases (e.g. e-CMR, law enforcement, eCall)

STATE OF PLAY: tracking devices Market-driven solutions adopted for different operational needs vs costs (e.g. type of transport, type of goods/sensors, certification for explosives, battery life/additional power source, installation constraints/accommodation, environmental conditions) Prototypes based on multi-GNSS developed through EU researches initiatives (e.g. SCUTUM, CONTAIN) now available as products thanks to technology evolution

STATE OF PLAY: authorities’ platforms Authorities’ platforms existing in some EU countries (e.g. Italy and France) for operations at national/regional and cross-border level

LEGAL and standardisation FRAMEWORK Main legal references: Inland transport of dangerous goods regulated by ADR (road), RID (rail), ADN (inland waterways) Endorsed by EC “DIRECTIVE 2008/68/EC of 24 September 2008 on the inland transport of dangerous goods” UNECE WP.15/AC.1 RID/ADR/ADN Joint Meeting UNECE WP.15/AC.1 RID/ADR/ADN Joint Meeting informal WG on Telematics Main standardisation references: e-CMR UN/CEFACT & IRU DATEX II, Technical Specification CEN/TS 16157 “data exchange specifications for traffic management and information”, www.datex2.eu TAF-TSI, European Union Agency for Railways Telematics Application for Freight - Technical Specifications for Interoperability, https://www.era.europa.eu/Document-Register/Pages/TAF-TSI.aspx CWA 16390 revision 2018, CEN Workshop Agreement for use of multi-GNSS (GPS/EGNOS/Galileo/GLONASS/BeiDou), https://www.cen.eu/work/areas/ICT/Pages/default.aspx

UNECE Informal WG on Telematics - TP1/TP2 architecture Third Parties: TP1 - public body TP2 - private entity Use cases (TP2/TP1 and TP1/TP1 transactions): Transport e-document compliant with ADR/RID/ADN for law enforcement/emergency management Risk assessment functions (combined with spatial information and real-time data) Advanced support to emergency/intervention operations Statistics Trusted Party 1 Management Server Trusted Party 2 Content Server Authorities Command & Control Centre (e.g. Emergency Responder) Transport [tracking device, if available] Casual observer Carrier

UNECE Informal WG on Telematics - TP1/TP2 data model e-DG Transport Document: XML/XSD schemas DATEX II format Mandatory classes and data (ADR/RID/ADN) Optional classes and data Interoperable with TAF-TSI

CORE: intermodal transport of dangerous goods demonstrator Enhancement/adaptation/evolution of existing tracking device and platforms Business stakeholders (transport operators, shippers) and authorities (ministries of transport, regional entities, emergency operators, law enforcement): Monitoring, localization, tracking and tracing eDocumentation Risk assessment Safety

CORE: intermodal transport of dangerous goods demonstrator Contribution to UNECE informal WG on Telematics: Architecture Proof of concept for TP1/TP2 Technical feasibility in cross-border operations (Italy and France) Data model Validation of GPS/EGNOS/Galileo/GLONASS Interoperability with TAF-TSI (rail) Analysis of interoperability with e-CMR (road) Analysis of interoperability with eCall (road) Contribution to standards Inputs to TAF-TSI and e-CMR Revision of CWA 16390 Possible inputs for future evolutions of DATEX II

CORE: intermodal transport of dangerous goods demonstrator Transport of Argon in tank container from Duisburg (Germany) to Terni (Italy) Intermodal road/rail (tank containers) Business stakeholders/transport operators Authorities/regulators Cross border operations Emergency activation Involved stakeholders: LINDE shipper HOYER tank container owner HOYER road and intermodal transport operator HUPAC rail transport operator and wagon keeper MIT, 5T (Italy) and MTES (France) national/regional authorities Running for about one year (mid of May 2017/beginning of April 2018)

Coherence with/contributions to legal and standardisation framework Contributions to UNECE WP.15/AC.1 RID/ADR/ADN Joint Meeting (through UNECE WP.15/AC.1 RID/ADR/ADN Joint Meeting informal WG on Telematics): Memorandum of Understanding for the use of 5.4.0.2 ADR/RID/ADN (endorsed by EC “DIRECTIVE 2008/68/EC of 24 September 2008 on the inland transport of dangerous goods”) eDG TD (Transport Document) data exchange Interoperability with EUAR TAF-TSI (multimodality) Analysis and partly implementation of interoperability with e-CMR Integration in C-ITS developments for Italy and France Coherence with EU proposal for regulation on eFTI (electronic Freight Transport Information) June 2018

Analysis of interoperability with e-CMR Dangerous goods part of today e-CMR not replacing the full ADR data Proposal: In e-CMR to include the mandatory classes/attributes of e-DG Transport Document Enabling e-CMR to be used as transport e-document compliant with ADR/RID/ADN for law enforcement/emergency management (TP1/TP2 operational) (*) In e-DG Transport Document to add a class for a link with e-CMR Enabling e-DG Transport Document to be interoperable with e-CMR use case e-DG Transport Document cannot be modified to create a link with e-CMR (the two descriptions of dangerous goods not completely equivalent, particularly for some cases - e.g. empty containers, nuclear/radioactive, explosives -) (*) Alternatively: the plate numbers of the truck and its trailers without any other information can be used to retrieve the dangerous goods description in line with ADR from TP2 for private actors or via TP1 for public bodies. e-CMR will automatically follow future evolutions of ADR

Analysis of interoperability with eCall HGV Today in eCall HGV message not all cases are considered - e.g. empty containers, 7 ADRType Proposal for modifications in eCall message: substituting the dangerous goods data with a Boolean indicating that DG are on board. VIN is already part of the eCall message and with the VIN PSAP acting as emergency services can retrieve the full dangerous goods description in line with ADR from TP1 (TP1/TP2 operational). - if dangerous goods yes, then dangerous goods description in line with ADR retrieved from TP1 (TP1/TP2 operational) eCall HGV message automatically following future evolutions of ADR

Antonella Di Fazio, Telespazio, demonstrator leader Questions ? Thank you! Antonella Di Fazio, Telespazio, demonstrator leader antonella.difazio@telespazio.com