
Variable message signs written from live traffic data
A variable message sign shows drivers text, pictograms and travel times that change with conditions. ROTA designs the message, decides which rule wins, writes it to the sign and reads back what is actually on screen.
What is a variable message sign?
A variable message sign (VMS) is a roadside LED display whose message changes with traffic conditions instead of being fixed. In SİNYAL systems the message is not typed by an operator but written by rule from live data — queue length, travel time, incidents — and every posting is reconciled against what the device actually shows.
Text, pictograms from a 134-piece library, multi-page messages and effects are composed in a device-independent designer. Rules draw on measured queue length per approach, travel time for a defined A→B route, and traffic incidents with their road and description. Sign faults are reported separately by type, and the LEDs the device reports as faulty are drawn on a bad-pixel map at the sign's own resolution.
- Message content
- Text, pictograms, multi-page, effects
- Pictogram library
- 134 pieces, plus operator uploads
- Automation inputs
- Queue length, travel time, incidents
- Arbitration
- Winner by priority, reason recorded
- Operator lock
- Automation never overwrites a manual message
- Fault types
- Offline, device, pixel, degraded automation
How a message reaches the sign
Five steps, from the rule that proposes a message to the read-back that confirms it.
- Rule — a condition, a message and a priority
- Candidate — every message whose condition currently holds
- Arbitration — the winner is picked by priority, and the reason is recorded with it
- Write — the message is sent to the device
- Reconcile — what is on screen is read back and verified against what was sent

What the sign can show
- Free text
- Pictograms from a 134-piece library
- Operator-uploaded regional pictograms
- Multi-page messages
- Display effects
- Travel time for a defined route
- Queue-length diversion
- Traffic incident notices
Travel time is the current measured time for a defined A→B route — "airport 18 min". Queue-length diversion posts once the per-approach queue crosses its threshold. A traffic incident carries the road and the description, whether it is an accident, a closure or roadworks.
The rules automation obeys
The operator lock wins
Automation never touches a message posted by hand, for any reason.
A stale source posts nothing
If the feeding data falls silent, "road closed" does not stay on the sign.
Arbitration records the reason
More than one rule can be right at the same moment — a queue warning on one side, an accident notice on the other. ROTA picks the winner by priority and records why, so "why was this message showing?" can always be answered.
Sign faults
The sign's alarms are kept separate: offline, device fault, pixel fault and degraded automation are never conflated. The LEDs the device reports as faulty are drawn on a bad-pixel map at the sign's own resolution.
- Offline
- Device fault
- Pixel fault
- Degraded automation
The sign
The screen and the software that writes to it.
LED display
The roadside screen itself, driven from the centre.
Central software
Designs the message, arbitrates the rules, writes to the device and reconciles what is on screen.
Frequently asked questions about variable message signs
What is a variable message sign?
A roadside LED display whose message changes with traffic conditions rather than being fixed. It can show text, pictograms, travel times and incident notices.
What can a variable message sign show?
Free text, pictograms from a 134-piece library plus operator uploads, multi-page messages and display effects, along with travel times, queue-length diversions and traffic incident notices.
Who decides what the sign says?
A rule does. Each rule carries a condition, a message and a priority; when the condition holds, the message becomes a candidate and arbitration picks the winner.
Can an operator post a message by hand?
Yes, and it takes precedence. Automation never touches a message posted by hand, for any reason.
What happens if two rules apply at the same time?
Arbitration picks the winner by priority and records the reason with it, so the question "why was this message showing?" can always be answered afterwards.
What happens if the data feeding a rule stops?
Nothing is posted. A stale source cannot leave an out-of-date message such as "road closed" standing on the sign.
Does the sign show travel times?
Yes. Travel time is the current measured time for a defined A→B route, shown in the form "airport 18 min".
How does queue length change the sign?
Once the measured queue on an approach crosses its threshold, the rule fires and drivers are sent another way.
How are sign faults reported?
By type, and never conflated: offline, device fault, pixel fault and degraded automation are separate alarms.
What is a bad-pixel map?
A drawing of the LEDs the sign reports as faulty, rendered at the sign's own resolution so the operator sees exactly which part of the display has failed.
Is the message verified after it is sent?
Yes. The final step of the chain reads back what is on screen and verifies it against what was sent.
Integration with ROTA
Sign automation is not a separate application: the rules draw on the same measured queue length, travel time and incident data that ROTA already holds, and the sign's alarms join the same fault lifecycle as the rest of the network.
Related solutions
Request a variable message sign demo
Send the sign locations, the routes you want travel times for and the data sources available.