02TML · Challenge 2

Dynamic information at stops

NEXTOP Smart Stop

The same device already installed at the stop for RF Mobility Mesh drives a very low-power e-paper display, powered by a small solar panel and connected via Wi-Fi or 4G to a central platform and the NEXTOP telematics platform.

Explore proposal
Core message
“The right information, at the right stop, at the right time.”
Bus stop with solar panel, compact device and e-paper arrival display at dusk
Illustrative image · solar-powered stop with e-paper display and shared device
The challenge in context
01

Static information

Printed timetables need manual updates across the network.

02

Frequent changes

Diversions, incidents and extra services must be communicated fast.

03

Not everyone uses apps

Information at the stop remains essential for many passengers.

Integrated vision

One infrastructure,
two challenges.

The same physical, connected stop infrastructure can support Smart Stop and RF Mobility Mesh, reducing duplication and creating a smart mobility network.

RF MESHCONNECTED STOPSMART STOP
One device, two challenges

The RF Mesh device
also drives the display.

The device installed for Challenge 1 already has power, connectivity and processing at the stop. Adding a low-power e-paper screen turns it into a Smart Stop — no second installation.

Anatomy of the smart stop

From the vehicle to the display

  1. BusGPS position of each vehicle via NEXTOP telematics.
  2. Central platformComputes arrival times, publishes messages and updates.
  3. Wi-Fi / 4GContent is sent to each stop in real time.
  4. Shared deviceReceives data and also runs the RF analysis.
  5. E-paperShows lines, minutes and notices to passengers.

Why e-paper + solar

Very low powerE-paper only consumes when the content changes.
Small solar panelEnough to power device and display at many stops.
No trenchingNo need to bring mains power to every stop.
Readable in sunlightPaper-like contrast, day and night with lighting.
Real-time remote updatesPer vehicle, per line or for the whole network.
Low cost per stopReuses the Challenge 1 device instead of new hardware.

Illustrative images · power and cost sizing to be validated in the pilot

01

Information that ages quickly

Timetables and physical information require manual updates. Changes, diversions and reinforcements need fast communication, without relying on smartphones alone.

02

The stop as a live channel

The platform receives location and telemetry from existing systems, links vehicle, route and upcoming stops, and estimates arrival time.

03

From the centre to the street

The stop displays upcoming services, minutes to arrival, changes, diversions, incidents, cancellations, reinforcements and operational messages.

04

One consistent source

Central management ensures information across the network is coherent, accessible and ready for open integration.

How it works

How it works, step by step.

  1. 1

    Receive telemetry

    Vehicle positions arrive from the operator's existing systems.

  2. 2

    Estimate arrivals

    The platform links vehicle, route and stop to compute ETAs.

  3. 3

    Publish messages

    Operators push incidents or changes to one stop or the whole network.

  4. 4

    Display at the stop

    A low-power connected display shows clear, accessible information.

System architecture

From the street to the dashboard.

L1

Data sources

AVL / telemetry, GTFS and operational messages.

L2

Integration

Open APIs and standard formats.

L3

Central platform

ETA estimation and content management.

L4

Connected stop

Shared RF Mesh device + low-power e-paper display, small solar panel, Wi-Fi / 4G.

L5

NEXTOP telematics

Vehicle positions per bus feed real-time arrival times.

Who benefits

Value for every stakeholder.

Transport authority

Consistent passenger information across the network.

Operator

Faster incident communication with less field work.

Passenger

Reliable, accessible information right where they wait.

Operational value

From physical perception to decisions.

01

Central updates across the network

02

Less manual intervention

03

Consistent, accessible information

04

Open integration with existing systems

PILOT
Validation in a real context

Validate with real information.

Use the same stops as challenge 1 to demonstrate the combined value of the infrastructure and avoid duplication from the start.

Integrate a real location source
Validate arrival estimates
Test messages and incidents
Evaluate operation at the same stops
Proposed pilot plan

Indicative timeline, to be agreed with the partner.

01 · Proposed · weeks 1–4

Integration

Connect to a real telemetry feed and define message types.

02 · Proposed · weeks 5–7

Deployment

Install connected displays at selected stops.

03 · Proposed · weeks 8–14

Operation

Run live information and test incident workflows.

04 · Proposed · weeks 15–16

Evaluation

Assess ETA quality, reliability and user feedback.

What we need from the partner

  • Access to a real telemetry feed
  • Selected stops with power or solar options
  • Operations team for message testing
  • Accessibility guidelines

Frequently asked questions

Proposal 2 / 3 ·