In short
A railway control room video wall sits beside the certified dispatch and signalling systems. Its job is to give supervisors and adjacent teams a common operating picture: train movement summaries, CCTV, incidents, weather, passenger flow, traction power, station status, field crews, and public-information state.
Rail OCC and metro dispatch are not the same wall
A mainline rail operations center watches network topology, timetable recovery, freight and passenger priority, weather, traction power, and major incidents across long distances. A metro OCC is denser: station CCTV, escalators, passenger flow, platform safety, traction segments, and very short incident-response windows.
Depots and freight operations add another mix: yard state, shunting plans, rolling-stock readiness, loading windows, repair status, and gate or perimeter cameras. One generic transport wall rarely fits all of these without named layouts for each operating mode.
Keep signalling and dispatch control primary
Interlocking, signalling, train-control, certified dispatcher HMIs, and safety procedures remain in the primary system. A software-defined wall should render read-only summaries and shared context around that chain. This keeps the wall useful without pretending to satisfy EN 50716 (formerly EN 50128) / EN 50129 or railway safety certification.
For the broader transport-control-room map, use the companion guide: video wall for transport control rooms.
Source mix for rail and metro walls
- Network state, train graph, timetable recovery, and incident boards.
- Read-only dispatch summaries, traction power, station state, and crew location.
- Station, platform, depot, yard, and perimeter CCTV.
- Passenger information, public announcements, service disruption status, and social signals.
- Weather, flooding, heat, fire, and security overlays.
- Maintenance windows, rolling-stock readiness, freight loading, and gate events.
Specification checklist
- Browser dashboards and RTSP / NDI camera feeds as first-class sources.
- Named layouts for normal operations, disruption, weather event, security incident, depot, and executive briefing.
- Operator-controlled source promotion with audit and source-health status.
- Local operation by default for restricted transport environments.
- Clear procurement wording: secondary visualization layer, not certified signalling or train-control equipment.
Build the wall around a handover and an incident
Walk through a representative shift handover with the people who use the room. Identify the network view, open incidents, maintenance restrictions and supporting cameras they need to discuss. Keep the shared view organised around decisions the team actually makes.
Then review a disruption scenario. Identify which sources must remain visible, which become useful only during that event and who may change the layout. This produces a source priority list that can guide both scene design and hardware sizing.
Check source access before sizing the controller
For each dashboard or camera, record its connection method, resolution, frame rate and access owner. Identify whether it is a web page, remote desktop, network video stream or captured output. Include the authentication and network dependencies in the configuration review.
Review a representative set of simultaneous sources with an engineer. A list of all stations is not the same as the workload rendered on the wall at one moment. Record normal, disruption and briefing workloads separately.
Test visibility from the room's working positions
Use actual map labels, timetable summaries and camera images when reviewing the display arrangement. Ask operators to assess them from their usual seats. Check panel boundaries, source window sizes and the information hidden when another window is promoted.
Prepare named scenes for the agreed tasks and document who may change them. Review the transition back to routine monitoring as an acceptance question. Record the observed behaviour on the project configuration without assuming an untested recovery time.
Keep recovery and maintenance in the acceptance plan
Agree checks for source interruption, expired authentication, controller maintenance and network unavailability. Identify the team that owns each dependency and the communication route between teams. A clear escalation process helps operators report the right context when a display looks wrong.
Preserve the role of the primary railway operating systems throughout those checks. The wall's acceptance record should describe shared visualisation, operator access and source presentation; it should not imply certification of signalling, interlocking or train-control functions.
Hand over a configuration that the next shift can understand
Keep the source register, scene list, permissions and support contacts with the installation documentation. Train operators using the room's actual scenarios. Include the process for requesting changes so a new source or layout receives the same visibility and access review.