STARTER PACKS / MOBILITY
TRAFFIC INCIDENTS AND ROADWORKS
STARTER PACK
90 DAYS - €7,400
DATEX II PUBLISHING FOR ROAD AUTHORITIES AND TRAFFIC MANAGEMENT CENTRES.
problem
YOU MANAGE A ROAD NETWORK AND CAPTURE INCIDENTS, ROADWORKS, AND DYNAMIC TRAFFIC EVENTS DAILY - BUT THE DATA STAYS IN YOUR TMS, REPORTED VIA SPREADSHEETS, AND NEVER REACHES JOURNEY PLANNERS, NEIGHBOURING REGIONS, OR THE EU NAP. THE ISSUE IS NOT MORE INCIDENT REPORTING - IT'S TURNING WHAT YOU ALREADY HAVE INTO STANDARD FEEDS.
INCIDENT DATA LIVES IN
YOUR TMS
Your control room sees it. Drivers don't. Journey planners can't.
ROADWORKS ARE
PLANNED IN A
CALENDAR, NOT A FEED
The schedule exists in Outlook or Excel. Nobody downstream knows.
CROSS-BORDER
COORDINATION IS BY
Incidents at the border don't propagate. Drivers find out at the queue.
DATEX II COMPLIANCE IS
A QUARTERLY REPORT,
NOT A LIVE FEED
EU regulations require continuous publishing. You publish quarterly.
ROAD AUTHORITIES DON'T NEED ANOTHER INCIDENT SYSTEM. THEY NEED THEIR EXISTING DATA TO FLOW AUTOMATICALLY AS DATEX II.
solution
We start with the Starter Pack (one authority, existing TMS, DATEX II publishing) because this gives you 80% of value in 90 days with minimal cost and no risk.
HOW WE APPROACH THIS
(simple and a bit refreshing)
We connect to your traffic management system and incident-reporting tools, generate DATEX II feeds continuously, and submit to the national access point - plus federate with neighbouring regions on NGSI-LD.
We connect it using:
- DATEX II as the EU traffic data standard.
- ETSI NGSI-LD Smart Data Models for traffic events.
- The Vela Context Data Hub.
- Your existing TMS, incident-reporting tools, and roadworks calendars - vendor-specific or in-house.
No replacement of your TMS. No new operations process. No 'enterprise digitalisation committee'.
Once the connection is built → DATEX II feeds publish continuously, journey planners and neighbouring regions consume your incidents in real time, and your data joins the wider mobility context graph.
Then we expand - adding cross-border federation, weather correlation, and predictive incident analytics.
What You Get (in 90 Days)
- DATEX II feed publishing - situations, SituationRecords, Roadworks, EnvironmentalObstructions, AbnormalTrafficSituations.
- NAP compliance - continuous submission to your national access point.
- NGSI-LD Context Bridge - traffic events join the wider mobility context graph.
- Live incident widget - embeddable on your authority website and partner sites.
- Cross-border federation hook - subscribe to neighbouring authorities' DATEX feeds. Publish to theirs.
- Operator dashboard - active incidents, scheduled roadworks, MTTR, frequency by road segment.
- Data ownership - your data, your context. Downstream partners consume; you control.
THIS IS YOUR TRAFfIC DATA PUBLISHING LAYER, NOT A PILOT.
Who This Is For
Road authorities and traffic management centres that:
- Manage a road network at municipal, regional, or national level.
- Operate a traffic management system that captures incidents and roadworks.
- Need DATEX II compliance for EU mobility data space participation or NAP submission.
- Want cross-border data sharing with neighbouring authorities.
Multi-region traffic data spaces → see Mobility Data Space STARTER pack.
pricing
STARTER PACK
€7,400
one time setup
(30 working hours included for consulting and developing)
-
- Fully managed shared hosted Vela Context Data Hub instance
-
The essentials
Metadata and data viewer / editor
Searchable metadata and data portal
Authentication and authorization
TMS connector (vendor-specific APIs, custom)
Roadworks calendar / planning system connector
Database
NGSI-LD Context Broker
Authority / road network / segment / event hierarchy
Semantic model for traffic events (NGSI-LD bridge to DATEX II)
DATEX II feed generator with validation
NAP submission automation
Cross-border federation hook
Live incident widget
Operator dashboards
Data ownership
API for database access and direct Context broker access
Optional dedicated or on-premise deployment
Installation
-
Support
Email support (Business hours)
(OPTIONAL) 12 MONTH SUPPORT EXTENSION
€1,490/month
12-month support extension,
hosting & support, billed monthly after 90 days period
(8 working hours per month included for consulting and developing)
Quarterly review session
New road segments / event types onboarded
Cross-border federation maintenance
DATEX II version evolution
Support
Email support
Want the architecture walkthrough?
We’ll show:
- How your TMS data flows into NGSI-LD and out as DATEX II.
- How NAP submission actually works.
- How cross-border federation with neighbouring authorities propagates incidents in real time.
VELA CONTEXT DATA HUB · ONE SHARED DATA LANGUAGE FOR MOBILITY · EU OPEN STANDARDS (NGSI-LD) · YOUR INFRASTRUCTURE, YOUR RULES