Skip to content
Use case 023

Metro Platform Screen Door Controllers

A deployment concept for metro operators, station-system integrators and public transport authorities.

Proposed deployment · Compatibility assessment required
Rail, Aviation, Maritime and Logistics

Why this environment matters

The trust boundary for metro platform screen door controllers matters because the system synchronises platform barriers with train arrival and door opening. The operational threat is specific: false commands, sensor spoofing or remote compromise could create passenger entrapment, falls or prolonged station shutdowns. A NØNOS-based design could reduce ambient authority and make the system easier to reset, inspect and attest.

The security challenge

Transport systems often operate continuously, depend on specialised protocols and must preserve safe fallback behaviour while interacting with many operators, contractors and external data sources. For this system, the primary attack path is that false commands, sensor spoofing or remote compromise could create passenger entrapment, falls or prolonged station shutdowns. Conventional general-purpose hosts often place parsers, management tools, network services and privileged drivers in one broad trust domain, allowing a flaw in a low-value feature to reach a high-consequence function.

How the capsule model could help

NØNOS could be placed at the operator, gateway, edge or application-compute layer and configured to separate train-detection, door actuation, obstacle sensing and remote maintenance services with tightly scoped hardware capabilities. The most relevant controls are rapid recovery to a known state, signed operational software, compartmentalised protocol handlers and attested operator sessions. This would make privileges explicit: a service that reads a sensor, displays data or contacts a cloud API would not automatically be able to issue a physical command or use a signing key.

Separate address spaces and capability checks can limit cross-process reach. They cannot stop harmful use of legitimate permissions, prove AI decisions correct or substitute for domain-specific safety controls.

Deployment requirements

NØNOS would need to sit beside, or be engineered into, existing certified systems without weakening deterministic behaviour, fail-safe modes, independent protection or operator procedures.

Current public-beta limitations, hardware support and application availability must be assessed before any pilot. Neither this use case nor an industry source establishes NONOS certification or a current customer deployment.

Who could buy or integrate it?

  • Metro authorities commissioning platform barrier systems
  • Platform-door manufacturers embedding controller software
  • Station systems integrators coordinating doors and signalling

Industry examples: Knorr-Bremse, Wabtec. Organisations shown illustrate the industry. No NONOS customer, partner or endorsement relationship is implied.

Market opportunity

Market benchmarks and device scenarios.

Published industry benchmark
US$1.42 billion

Subway platform screen doors

Global · 2025 · annual market estimate

Manufacture, installation and maintenance of platform door systems, including panels and controls.

Modelled global devices
10K–160K

Candidate OS endpoints

Hypothetical planning range · 2025

Low confidence: planning assumptions. Hardware compatibility, procurement and adoption have not been validated.

Illustrative annual licensing
$300K–$28.8M

USD / year at full model coverage

Device scenario × assumed US$30–$180 per device / year.

Not a revenue forecast, announced price or measured serviceable market.

Device calculation

Hypothetical global planning range, 2025 scenario: assume 5,000–20,000 metro stations equipped with platform screen doors × 2–8 candidate OS endpoints per site/asset = 10,000–160,000 endpoints. Counting unit: platform control computers; individual door motors excluded. Site and asset counts, and devices per site, are planning assumptions. The installed base has not been measured. Coverage is limited to the defined equipped subset; includes all candidate endpoints within that assumed subset. Hardware eligibility, certification, adoption and achievable NØNOS share are unverified; overlaps other cases.

Subway platform screen doors market report ↗

Market context only; separate from device and site population estimates. Original monetary-market scope and geography are preserved in benchmark. This source does not establish the assumed worldwide site count or endpoint density.

How to interpret the figures

Adjacent or broader commercial market benchmark; not the NØNOS OS market, licensable-device count or revenue forecast.

Modelled candidate endpoints multiplied by an assumed annual USD price per endpoint. Pricing is a planning assumption, not a vendor quote. This illustrates the full scenario range, not revenue or total addressable market. It excludes adoption timing, procurement, certification, support costs, channel economics and achievable market share. Use cases can overlap, so their totals do not represent unique devices.

Research from 2026. Publisher estimates have not been independently audited.

Read the full methodology

Explore NONOS

Choose your
NONOS experience.

Discover the platform for your organisation or explore the software.

You can reopen this chooser from the footer at any time.