Skip to Content

STARTER PACKS / MOBILITY

TRANSIT DATA PIPELINE

STARTER PACK

90 DAYS - 7.400€

FROM AVL TO NGSI-LD — WHEN YOU DON'T YET HAVE A GTFS-RT FEED.

problem

YOU OPERATE A TRANSIT NETWORK BUT YOUR DATA IS LOCKED IN A PROPRIETARY DISPATCH SYSTEM, BEHIND A FIREWALL, OR COUPLED TO OTHER CITY DOMAINS THAT VENDOR-LOCKED SAAS CAN'T SEE. THE ISSUE IS NOT MORE DASHBOARDS — IT'S BUILDING THE DATA LAYER UNDERNEATH.

When You Need This Pack (and not Vela Pulse)  

YOU DON'T HAVE 
GTFS-RT YET



Your AVL talks to a dispatch system. Nothing flows out as a public feed.

YOUR AVL IS 
PROPRIETARY OR 
LEGACY
 

Trapeze, INIT, IVU.cockpit, custom Siemens, in-house — Pulse can't read it directly.

YOU NEED ON-PREMISE 
OR DEDICATED 
INSTANCE

Data sovereignty, regulator-driven, defence-adjacent, or ministerial procurement. SaaS is not an option.

YOU NEED CROSS-
DOMAIN INTEGRATION
 


Connect transit to parking, air quality, weather, events, energy on one NGSI-LD context graph.

YOU PREFER ONE-TIME CAPEX OVER SUBSCRIPTION
  

Project-led procurement, grant-funded budget, or capital-account preference.

IF NONE OF THE ABOVE APPLIES → USE VELA PULSE. LIVE IN DAYS. A FRACTION OF THE PRICE. 

solution

HOW WE APPROACH THIS

(simple and a bit refreshing)

We build the data layer underneath your transit operations — from AVL or dispatch, to NGSI-LD context graph, to public GTFS-RT feed and dashboards.


We connect it using:

  • ETSI NGSI-LD Smart Data Models for public transport.
  • The Vela Context Data Hub — shared, dedicated, or on-premise.
  • Your existing AVL, dispatch, and scheduling systems — Trapeze, INIT, IVU.cockpit, Mentz, custom — via SIRI, NeTEx, MQTT, OPC-UA, or custom APIs.


No replacement of your scheduling system. No new dispatch software. No 'enterprise digitalisation committee'.

Once the pipeline is built → public GTFS-RT feed flows out, dashboards become available, and your data starts connecting to other city domains on one context graph.


Then we expand — adding cross-domain entities, additional modes, and regional federation.

What You Get (in 90 Days)
 
  • NGSI-LD context graph - your operations, modeled as a queryable graph on the vela context hub.
  • Avl → gtfs-rt pipeline - continuous conversion of your internal data into a standard public feed.
  • National access point submission - your gtfs static and gtfs-rt submitted to the relevant national mobility data point.
  • Cross-domain hooks - pre-configured links to weather, parking, air quality, and event datasets.
  • Operator dashboards - on-time performance, headway adherence, vehicle distribution.
  • Public live map widget - embeddable on your website. Same data, different surface.
  • Data ownership - your data, your context, your rules. No vendor lock-in.
THIS IS YOUR OPERATIONAL DATA LAYER, NOT A PILOT.

 

Who This Is For ​
 

Transit operators and authorities that:

  • Run 50–500 vehicles in scheduled service (bus, tram, trolleybus, light rail).
  • Have an AVL or dispatch system that doesn't expose GTFS-RT today.
  • Need on-premise or dedicated NGSI-LD for data sovereignty or regulatory reasons, OR
  • Need cross-domain integration with parking, weather, events, air quality on one context graph, OR
  • Prefer one-time CAPEX procurement over ongoing SaaS.


If you have GTFS-RT today and just want a live map → use Vela Pulse. 
It's a fraction of the price.

 

 We start with the Starter Pack (one operator, 50–500 vehicles, existing AVL system) because this gives you 80% of value in 90 days with minimal cost and no risk.

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

AVL / dispatch connector (SIRI, MQTT, REST, OPC-UA, vendor-specific APIs)

Database

NGSI-LD Context Broker

Operator / route / line / vehicle / stop hierarchy

Semantic model for public transport operations

Cross-domain hooks (weather, parking, events, air quality)

5–8 dashboards 

Alerts

 Cross-domain hooks (weather, parking, events, air quality)

GTFS-RT feed generation and hosting

GTFS Static validation and National Access Point submission

Data ownership

API for database access and direct Context broker access

 Optional dedicated or on-premise deployment


Installation

​

    Support

    E-mail support (Business hours)
    Instant setup, satisfied or reimbursed

(OPTIONAL) 12 MONTH SUPPORT EXTENSION

1.490€ per 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 routes / vehicles / cross-domain entities onboarded

    GTFS-RT feed monitoring and uptime SLA

    Support
     
    Priority email support​

Want the architecture walkthrough?

We’ll show:

  • How the data flows from your AVL into NGSI-LD and out as a public feed.
  • How cross-domain integration actually works in your context graph.
  • How on-premise / dedicated deployment differs from shared SaaS.

 BOOK A 30-MINUTE CALL

VELA CONTEXT DATA HUB · ONE SHARED DATA LANGUAGE FOR MOBILITY · EU OPEN STANDARDS (NGSI-LD) · YOUR INFRASTRUCTURE, YOUR RULES