New: the AI firewall watches the whole platform and explains each incident in plain words. See how it works

Level crossing and traffic signal monitoring

A blueprint for watching level crossings and signalled junctions through their controllers' status outputs: faults, lamp failures, barriers held down, mains and battery, alarms and rollout.

Without data vs with Hermetry

Barriers come down at 07:52 and stay down. Who knows first?

The same morning at one tram crossing, twice: once with nobody watching the crossing, once with Hermetry watching it.

Without data

until someone knows

48 min

The maintainer hears of it from the street, through the control room.

Thu 07:52

The barriers at Crossing 3 come down and stay down

No tram is coming. Cars queue on both sides.

Thu 08:10

The queue reaches the next junction

Buses on two routes are held in it.

Thu 08:25

A driver calls the city

The call is passed on to the traffic control room.

Thu 08:40

The crossing maintainer is called

Forty-eight minutes after the barriers came down.

With Hermetry

to the first alarm

10 min

A Rules card on the corridor raises "Barriers held down" when a crossing’s barriers stay down for 10 minutes.

Thu 07:52

The barriers at Crossing 3 come down and stay down

The crossing controller reports barriers down.

Thu 08:02

Major alarm: Barriers held down

The barriers have stayed down for 10 minutes. This is what the control room sees:

Crossing 3, Mill Road

Thu 08:03

The control room and the crossing maintainer get a push

It repeats every 15 minutes until someone acknowledges it.

Thu 08:20

The maintainer is on site

The alarm is acknowledged with a note and resolves when the barriers rise. Its history is kept.

At a glance

ItemTypical answer
ProblemA crossing controller or a signal controller records a fault in its own cabinet, but the street finds out first: a lamp out, barriers stuck down, or a junction on flashing amber in the morning peak.
What is connectedThe status outputs of each level crossing controller (healthy, fault, barriers down, lamp failure), mains and battery at the crossing, and the fault, lamp and power states of each traffic signal controller.
Who uses itThe traffic control room, the signals maintenance contractor, the crossing maintainers of the tramway or railway, and the road authority's duty officer.
Typical first scopeFive to ten crossings or junctions of two controller types, usually along one corridor.
Time to first screenTypically a few days after the first cabinet is wired, because the signals are contacts and a battery voltage. Allow four to six weeks before maintainers rely on the alarms instead of patrols.
Estimates; access to the cabinets and the controller owner's approval of the wiring usually set the pace.

The situation

A city has signalled junctions on its main roads and, where trams or a railway cross the street, level crossings with barriers, warning lights and a crossing controller. Each controller checks its own lamps and equipment and records faults in its cabinet. Some report to a central system of their own; many older ones report to nobody.

So faults are found from the street. A red lamp fails and a driver reports it. Barriers stay down after a fault and traffic queues before anyone is sent. A junction drops to flashing amber at 08:00 and the contractor hears of it from the police. A crossing on standby battery after a mains failure runs until the battery is flat, and nobody saw the voltage fall.

This blueprint reads the status that controllers already provide for remote monitoring, adds mains and battery, and puts every crossing and junction on one map with alarms to the right maintainer. It reads. It never takes part in the controllers' safety logic.

What gets connected

Signals are status outputs the controller provides for monitoring, read on gateway inputs, or registers where a controller offers Modbus. Their names and meanings vary by controller type; agree them with the owner.

PointTelemetry keyUnitSourceIntervalNotes
Crossing healthyxing_okboolController status outputon changeThe controller's own summary.
Crossing faultxing_faultboolController fault outputon change
Barriers downbarrier_down0/1Controller monitoring outputon changeUsed by the held-down rule.
Warning lights activelights_active0/1Controller monitoring outputon change
Crossing lamp failurelamp_failboolLamp-proving output of the controlleron changeWarning light or road signal lamp.
Mains presentmains_okboolPhase relay on a gateway inputon changeAt crossings and junctions.
Standby battery voltagebattery_vVGateway analog input through a transducer5 minCrossing standby supply.
Cabinet door opendoor_openboolReed contacton changeExplains visits on the timeline.
Signal controller faulttsc_faultboolController fault output, or Modbuson change
Junction modetsc_modecodeController mode outputson change0 normal, 1 flashing, 2 dark.
Signal lamp failureslamp_fail_countcountController, where it reports a count; else a lamp-fail contacton change
Vehicles per hourveh_per_hveh/hController detector counts, where offered15 minOptional.

How it is set up

  • Gateways: a 4G gateway in each crossing and junction cabinet, or an industrial gateway running Hermetry Edge where a cabinet has a network link, reads the status outputs on its digital inputs, the battery voltage on an analog input and, where a controller offers it, registers over Modbus RTU. It sends them over MQTT over TLS on one outbound connection; nothing on the street accepts connections from the internet.
  • Wiring: only to outputs the controller provides for remote monitoring, through isolated contacts, and approved by the controller's owner. Nothing is wired into the crossing's or the junction's safety circuits.
  • Buffering: readings are kept on the gateway while the link is down and arrive later with their original time stamps; capacity depends on the model.
ComponentRoleNotes
Crossing controllerKeeps control of barriers, lights and the crossing sequenceRead-only from Hermetry, through its monitoring outputs.
Traffic signal controllerKeeps control of the junctionRead-only from Hermetry.
4G gatewayReads contacts and battery voltage in the cabinetOne per cabinet; claimed into your organisation.
Industrial gateway with EdgeThe same, where a cabinet has a network link or a controller offers ModbusEach controller can report as a child device.
HermetryStorage, alarms, map, boardsEU, US or Türkiye region, or on your own servers with the Enterprise plan.

Use one profile for crossings and one for junctions, duplicated per controller type, because rules address devices one by one or by profile. In the asset tree, a corridor is an area and each crossing or junction a site beneath it, with its location, controller type, maintainer and battery limit as attributes.

Heartbeats. Contacts report on change, so without a heartbeat a quiet crossing and a dead link look the same. Have each gateway report every few minutes and use the Recent message online rule with that interval.

Testing at the cabinet. With the maintainer, force a fault, a lamp failure and barriers down from the controller's own test function where it has one, and check that each state changes in Hermetry within a minute and that the alarm reaches the right person.

Alarms

AlarmConditionDelay and hysteresisSeverityNotifiedEscalation
Crossing faultxing_fault == trueDebounce 10 sCriticalCrossing maintainer on call and control room, SMS and pushReminder every 10 min until acknowledged
Barriers held downRules card on the corridor: barrier_down = 1Stays so for 10 minMajor (raised by the rule)Control room and crossing maintainer, pushReminder every 15 min
Crossing lamp failurelamp_fail == true on the crossing profileDebounce 30 sMajorCrossing maintainer, push and SMSReminder every 30 min
Crossing on batterymains_ok == false on the crossing profileDebounce 60 s raise, 120 s clearWarningControl room, in-appCovered by the battery alarm
Crossing battery lowbattery_v < attribute battery_low_vDebounce 3 readings; hysteresis 0.5 VMajorCrossing maintainer, SMSReminder every 30 min
Junction dark or flashingtsc_mode > 0Debounce 30 sCriticalSignals contractor on call and control room, SMSReminder every 10 min
Signal controller faulttsc_fault == trueDebounce 30 sMajorSignals contractor, pushReminder every 30 min
Signal lamp failurelamp_fail_count > 0Debounce 2 readingsMinorSignals contractor, e-mailReminder daily
Junction mains lostmains_ok == false on the junction profileDebounce 60 sMajorSignals contractor and control room, pushReminder every 30 min
Gateway offlineInactivity rule, no message for 10 minMajorControl room, pushReminder every 30 min

Consequences, not dips. A mains failure at a crossing is a Warning, because the standby battery carries it. What pages people is the battery falling. Put limits that differ by site, such as battery_low_v, in attributes so one rule fits every crossing.

Held down. A busy tram line can keep barriers down for minutes at the peak. Agree the held-down time with the crossing owner, and use a Rules card, whose timer runs even when no new reading arrives.

Maintenance. Mute a crossing or junction while the maintainer works in the cabinet. Its alarms are recorded but nobody is paged, and the mute ends by itself. Limits and times here are starting values; take them from the controller owner and the maintenance contract.

Dashboards and screens

BoardAudienceWidgets and what they show
Corridor mapControl roomMap of crossings and junctions coloured by status; table with mode, faults, mains and battery; alarm table filtered to Major and Critical.
Crossing pageCrossing maintainerState cards for healthy, barriers and warning lights; gauge for battery voltage; line chart of battery voltage over 7 days; the crossing's alarms with their notes.
Junction pageSignals contractorState cards for mode, fault and mains; lamp failures; mode changes over 24 hours; vehicles per hour where counted.
Maintenance reviewContractor managerFaults per site and month; time to acknowledge from the alarm timeline; tables downloaded as spreadsheets.

Entity parameters let one Crossing page serve every crossing and one Junction page every junction, opened from a map marker or a table row.

A SCADA drawing of a corridor places the level crossing and traffic light symbols of the city family where they stand, with the controller beside each. Colour rules show a fault in red, a flashing junction in amber and a low battery as a second reading. Leave every command out of these drawings: barriers, lights and signal plans stay with their controllers.

Rollout

PhaseWeeksWorkExit criteria
0. Survey1-3List controllers and their monitoring outputs; agree meanings and wiring with each owner; check cellular coverage at the cabinets.Approved wiring list per controller type.
1. Pilot4-7Two crossings and three junctions; profiles; alarms to the control room only; corridor map.Every output tested at the cabinet with the maintainer; alarms seen within a minute.
2. Corridor8-12All sites of the corridor; routing to maintainers and the contractor; battery limits per site.Two weeks in parallel with patrols; no fault found in the street first.
3. City13 onRemaining corridors in turn; maintenance review board; signed webhooks to the contractor's job system.Every site reporting; faults acknowledged within the agreed time.

Pitfalls

  • Wiring into safety circuits. Use only outputs the controller provides for monitoring, through isolated contacts, with the owner's approval.
  • Paging on every mains dip. Crossings carry standby batteries. Page on the battery, not on the dip.
  • One profile for every controller type. Output meanings differ. Duplicate the profile per type and map each to the same keys.
  • A gateway on the cabinet's own supply. At a junction without standby power, a mains failure takes the gateway with it and shows as “Gateway offline”. Give the gateway a small backup supply, or read offline as power lost.
  • A silent cabinet that looks healthy. A gateway without a link shows its last good state. Keep an inactivity alarm on every gateway.

What Hermetry does not do

Hermetry measures and alarms; it does not control level crossings, barriers, warning lights, traffic signals or trains. The crossing controller, the signal controller and the railway's or tramway's signalling keep full control and every safety function, and must work without Hermetry or its link. An alarm in Hermetry tells people; it is no part of the crossing's protection. Signal timings, crossing sequences and maintenance stay with their owners.

See your field data live this week

Start a trial in your region with your first devices, or book a demo and bring your own use case.