Alignment and harmonization
of data exchange standards
WG4 – Sylvain Belloche
Mobility Data Days
09.11.2023
Introduction and objectives
Transmodel
SIRI
Introduction and objectives
Context of the finalization of a roadmap for alignment and harmonization
of data exchange standards (NAPCORE WG4)
Today’s session:
● Presentation of the current content of the roadmap
● Topics for alignment and harmonization
● Alignment and harmonization methodology
● Actions and assessment
● Do not hesitate to interact!
Agenda
● General presentation of each standards
● DATEX II
● TN-ITS
● Multimodal data exchange standards
● Metadata
● Presentation of the roadmap:
● Objectives, identified topics, actions and tasks
● Methodology to ensure alignment / harmonization
● Presentation of 2 topics: parking and real-time traffic information
● Discussion with the audience
I. Presentation of the standards
Alignment and harmonization of data exchange standards
Mobility Data Days
09.11.2023
ITS enabled by
[presenter name]
[presenter title/role]
Information challenge
About
• E-language for road-traffic and travel related information
• For all road-networks (motorway, trunkroads and urban/local
roads)
• Maintained by stakeholder community
• Standardized stepwise in CEN TC278 WG8 (16157 series) and
ISO TV204 WG9 (for Exchange).
• Local additions are facilitated
• Like a natural language: grammar and dictionary
Standardisation? The will to cooperate
Lost
?
Each actor has to
maintain receiving
asynchronous different
interfaces in terms of:
• Information model
• Location referencing
standards
Local adaptations
Examples:
• Netherlands expanded road works (hindrance category).
• OpenLR support started as a local need in Sweden
• Germany: real time fuel price information -> Energy
Publication
• Cross border TMP between Spain and France (being
standardized right now)
If DATEX is the letter…
• DATEX II = language and paper
• DATEX II profile = predefined form for specific purpose
• Postal system: uses standard IT
• Two envelope types are developed (XML; json)
• One transport type is defined in two flavours
• Pull (webservices and simple http)
• Push
• Content is independent from postal system
• Support for other delivery methods are being developed
The Evolution of
0 1
TCC TCC BSP
Big Service Provider
2
SSP
0. Original interface 4 5 Small Service
Provider
1. DATEX XML full model/ profiles
2. DATEX II Profiles 3
3. DATEX II Profiles • Phone APP
4. Message protocol C-ITS APP
•
•
Navigation APP
Navigation system
5. Message protocol Road side Units • OBU Info system
• OBU ADAS
The ITS value chain
service service content access
aggregator point traffic centre
access point provider
vehicle
roadside
station
The content part of
• Traffic situations • Electromobility infrastructure
• Traffic status • Management of electronic
• Traffic management traffic regulations
• Messages displayed on VMS • Urban vehicle access regulations
• Service information
• Parking • Map updates*
• Urban traffic specifics
What is about?
• Toolbox
ready to support:
• Traffic management
• Urban mobility
• Electric mobility charging infrastructure
• Logistics
• Electronic traffic regulations
• Cooperative, connected, and automated mobility
• Functional packages instead of one big model
• Exchange completely separated (now also JSON and ASN.1)
• Profiles per use-case
in the NAP ecosystem
EU Regulations
- Comission Delegated Regulation (EU) 2015/962 – RTTI
- Comission Delegated Regulation (EU) 2017/1926 – MMTIS
- …
FACILITATE
??? PARKING
LOCATION
Components
High Precision Location TPEG RDS ISO Open
Referencing GNSS
2 GML
7 LOC TMC Linear LR
Management Data Dictionary
Common: Reusable Data Location: Referencing
Road Information and
3 5 4 6 Subdomains
CEN
Variable Traffic Traffic
Road Road Status & TN-ITS
Message Parking TMPlan Signal Energy Regulati Facilities
Fault
Situation Data Signs Status ons
8 9 10 11 12 13 14
1 DATEX II Methodology – Object Oriented UML 16157 – (N)
CEN
Communication Protocol Specification / Exchange 19468 / 14827- (N)
ISO
I. Presentation of the standards
TN-ITS
Alignment and harmonization of data exchange standards
Mobility Data Days
09.11.2023
Multimodal data standard presentation
09/11/2023
Multimodal data standards – Scope
Multimodal data standards – Ecosystem
BIPEx
Multimodal data standards – Functional Areas
Transmodel
NeTEx
SIRI
OpRa
mobilityDCAT-AP
NAPCORE Mobility Data Days – WG 4 Session
November 9th, 2023
Context
● Metadata for search function in NAPs
How to describe mobility data?
Geographical
Data format
Coverage
Temporal Info Conditions for use
Access Info
Content Info
Ownership
Mobility Quality Info
Data
Metadata subWG 27
DCAT-AP framework
• Idea: a DCAT-AP extension for mobility data
DCAT-AP
Extension Extension Extension
“DCAT- „GeoDCAT- … „mobilityDCAT-
[Link]“ AP“ AP“
Metadata subWG 28
A new Metadata specification
Metadata subWG 29
A new Metadata specification
Metadata subWG 30
Work done so far
● Preparatory actions : Requirement Analysis, RoadMap,
Conceptual Model, Mapping to DCAT-AP elements
● [Link]
● Draft and review of mobilityDCAT-AP
● Intensified exchange with DCAT-AP/SEMIC group
Metadata subWG 31
The final product
● October 16th 2023: official release of mobilityDCAT-AP
v1.0 specification
● A set of documentation and technical artefacts
● [Link]
Metadata subWG 32
mobilityDCAT-AP: UML model
Metadata subWG 33
Upcoming tasks
● mobilityDCAT-AP governance & maintenance concept
December 2023
● Accompanying Guidelines as additional user support
January 2024
● WG 2 Metadata demonstrator as Proof-of-concept for
mobilityDCAT-AP April 2024
Metadata subWG 34
Thank you!
Peter Lubrich
Department Connected Mobility
Federal Highway Research Institute
Brüderstraße 53
51427 Bergisch Gladbach, Germany
lubrich@[Link]
[Link] + LinkedIn + Instagram + YouTube
II. Presentation of the roadmap
Alignment and harmonization of data exchange standards
Mobility Data Days
09.11.2023
Roadmap for alignment and harmonization
of data exchange standards
● Finalisation of the roadmap underway inside NAPCORE WG4
● Roadmap to help to ensure harmonization between standards: how?
Methodology to ensure alignment and
harmonization
09/11/2023
Alignment methodology – Overview
Alignment
Three
main Harmonization
scenarios
Mapping
Alignment methodology – Alignment
1. Alignment:
● applied (new) standardisation topics
● supported by one or more of the NAPCORE core
standards, avoiding parallel/competing initiatives.
● identifying existing semantical equivalent concepts that
can be subject of alignment in this context
Alignment methodology – Harmonization
2. Harmonization:
● The process to ensure that semantical equivalences
between standards are interoperable:
● unifying overlaps
● merging standards
Alignment methodology – Mapping
3. Mapping:
● Process that allows representation of a reference
standard to a different one.
● when overlapped standards exist and cannot be aligned
nor harmonized:
● Legacy
● Wide implementation
● Mappings require regular updates and maintenance.
II. Presentation of the roadmap
Alignment and harmonization of data exchange standards
Mobility Data Days
09.11.2023
Roadmap for alignment and harmonization
of data exchange standards
● Finalisation of the roadmap underway inside NAPCORE WG4
● Roadmap to help to ensure harmonization between standards
● To achieve harmonization:
● Identification of common grounds, such as
● Real-time traffic information / real-time multimodal traffic information
● Parking data
● Infrastructure changes, conditions of use of the infrastructure, availability of the infrastructure
● Search for alignment or harmonization of the standards for these common grounds
● Alignment: management of the distribution of new standardisation topics, to avoid
parallel/competing initiatives
● Harmonization: interoperability of semantical equivalences between standards
● If alignment or harmonization is not possible (legacy…), elaboration of a mapping
● Mapping and convertor tools needed
● Requires maintenance and updates
Roadmap for alignment and harmonization
of data exchange standards
Main action foreseen:
● Elaboration of a governance process to enable alignment and harmonization
between data exchange standards
● This process may include:
● Communication agreement to share change requests
● Assessment of the relevance of a task / work item
● If relevant, assignement of a host and definition of resources for the work item
● Joint solution to be found. This may lead to prior definition of priorities to select
one proposal from a range of conflicting solutions
Communication and cooperation are keys!
Roadmap for alignment and harmonization
of data exchange standards
● Case of metadata: potential interaction points between domain data
standards and metadata includes
● Equivalent information provided by both standards (e.g data provider details)
● Automated creation of metadata from content data (such as via a GUI - graphical
user interface)
● Pending question about the role of standardization organization, such as
CEN
● Illustration with 2 topics
● Parking
● Real-time traffic information
Focus – Parking data
09/11/2023
Parking
DATEX II Transmodel
APDS Park-and-ride
Safe and secure truck Park-and-drive
Storage due to crisis Scooter parking
Parking Tariffs
Parking
● National NeTEx parking profile (France)
([Link]
[Link])
● The column “DATEX II CONCEPT” is extracted from: drafted version parking profile
Focus
● Parking data
● Real-time traffic information
RTTI and Public Transport
NAPCORE Mobility Data Days 09-11-2023
Martin van Ekelenburg
NDW, The Netherlands
RTTI related data standards WG4
• DATEX II – Real Time Traffic Information
• Disturbances on the road network
• Transmodel NeTEx / SIRI – Public Transport Information
• Timetables
• Real Time Information
Planned roadworks / events
DATEX II contains:
• Road closures
• Possible rerouting
Public transport impact:
• Delays on the route
• Changes of a stop
• Cancellations of a stop
Unplanned disturbances
DATEX II contains
• Accidents
• Traffic jams
• Weather impact on road
• Road closures
Public transport impact:
• Delays on the route
• Unplanned changes/ cancellation of a route
Unplanned disturbances
Public transport events:
• Queuing times near ferries
Traffic Management impact
• Slow down traffic route
Harmonisation/ alignment
• More than traveller information data
• Relevance for incident management and the response
•,
• Support the data concepts in the involved standards in harmonized way
• Not driven by the Delegated Regulations
• Intermodal RealTime Incident Management Process
Thank you for your attention!
What’s next?
● Roadmap to be enhanced and finalized
● WG4 workshop 29-30 November
Contact:
Sylvain Belloche – French Ministry in charge of transport
WG4 leader
[Link]@[Link]