Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
PD CEN/TS 16157 — Intelligent Transport Systems DATEX II Data Exchange Specifications (Parts 4-6: VMS, Measured and Elaborated Data, Parking Information)
CEN/TS 16157 Series — UK Implementation
🚦 PD CEN/TS 16157 (corresponding to the CEN/TS 16157 series) is the UK implementation of the DATEX II data exchange specifications in the European Intelligent Transport Systems (ITS) field, the responsibility of BSI Technical Committee EPL/278 (Intelligent transport systems). This article covers Parts 4-6: Variable Message Sign (VMS) publications, measured and elaborated data publications, and parking publications. Together with Parts 1-3 (context and framework, location referencing, situation publication), they form the complete DATEX II publication family for traffic management and information services.
💡 The value of DATEX II lies in “a unified model + standardised publication structures”: Parts 4-6 model VMS, measured traffic data, and parking information as exchangeable publications, enabling semantically consistent data interoperability between roadside devices, centre systems, and service providers.
1. Series Structure and Positioning 📌
| Part | Corresponding CEN/TS | Title | Publication Content |
|---|---|---|---|
| PD CEN/TS 16157-4:2014 | CEN/TS 16157-4:2014 | Part 4: Variable Message Sign (VMS) Publications | VMS content, status, and publication management |
| PD CEN/TS 16157-5:2014 | CEN/TS 16157-5:2014 | Part 5: Measured and elaborated data publications | Flow, speed, occupancy measurement data |
| PD CEN/TS 16157-6:2015 | CEN/TS 16157-6:2015 | Part 6: Parking information publications | Static/dynamic parking facility information |
The three specifications were approved by CEN for provisional application in 2014 (Parts 4 and 5) and 2015 (Part 6), with validity initially limited to three years; after two years members are asked whether they can be converted into EN standards.
2. Variable Message Sign Publications (Part 4) 🖥️
Part 4 specifies the DATEX II data exchange specification for VMS publications, used to:
- Describe the content, images, and text layout displayed on VMS;
- Publish VMS status and fault information, supporting device management;
- Link with location referencing and situation models, forming the complete “what is displayed, why” chain.
⚠️ VMS publications must not only describe “what is shown on screen” but also manage the publication lifecycle and status: stale information must be cancelled promptly, and faulty signs should be reported via status publication to avoid showing outdated or incorrect information to travellers.
3. Measured and Elaborated Data Publications (Part 5) 📊
Part 5 specifies the DATEX II data exchange specification for measured and elaborated data publications, used to:
- Publish measured data (flow, speed, occupancy) from detectors (inductive loops, radar, cameras, etc.);
- Publish elaborated (fused, predicted) traffic data;
- Support metadata such as data quality, timestamps, and station/spatial location.
4. Parking Information Publications (Part 6) 🅿️
Part 6 specifies the DATEX II data exchange specification for parking information publications, used to:
- Publish static information of parking facilities (car parks, on-street) — location, capacity, opening hours;
- Publish dynamic information (available spaces, status, charges);
- Support parking guidance and multimodal travel information services.
✅ Combining parking information with situation, VMS, and navigation services can form a complete “find a space — guide — arrive” travel chain, reducing the detours and congestion caused by cruising for parking.
5. Engineering Practice Essentials 🛠️
- 🔍 Model consistency: when implementing Parts 4-6, extend the unified UML model and reuse the location referencing and framework conventions of Parts 1-3.
- 🔧 Lifecycle management: manage create/update/cancel for VMS content, measured data, and parking status, clearing stale data promptly.
- 📊 Data quality: provide timestamps, stations, and quality metadata for measured data to support fusion and downstream service credibility.
- 📋 Version tracking: CEN/TS is provisional and regularly reviewed; track conversion to EN and the addition of new publication types.
6. Frequently Asked Questions ❓
❓ Q: How do Parts 4-6 relate to Parts 1-3?
A: Parts 1 and 2 define the framework and location referencing, Part 3 defines the situation model, and Parts 4-6 define dedicated publication models for VMS, measured data, and parking information on that basis.
A: Parts 1 and 2 define the framework and location referencing, Part 3 defines the situation model, and Parts 4-6 define dedicated publication models for VMS, measured data, and parking information on that basis.
❓ Q: Why does VMS publication manage status?
A: Sign faults or stale information affect travellers’ judgement; status publication and lifecycle management ensure displayed content and device status are monitorable and traceable.
A: Sign faults or stale information affect travellers’ judgement; status publication and lifecycle management ensure displayed content and device status are monitorable and traceable.
❓ Q: What should be considered in measured data publication?
A: Provide station, timestamp, and quality metadata, encode location per the unified model, and distinguish measured from elaborated data to avoid downstream misuse.
A: Provide station, timestamp, and quality metadata, encode location per the unified model, and distinguish measured from elaborated data to avoid downstream misuse.
🔍 Q: How does parking information publication help travel?
A: Standardised publication of static and dynamic parking data, integrated into navigation and parking-guidance services, helps drivers quickly find available spaces and reduces cruising detours.
A: Standardised publication of static and dynamic parking data, integrated into navigation and parking-guidance services, helps drivers quickly find available spaces and reduces cruising detours.