Skip to content

No civil works, no tags

Locate your people where GPS can't reach

Metrosafe turns your stations' existing Wi-Fi and the smartphones your team already carries into real-time location. And when you need to know which train and which carriage an officer is in, that adds on without touching your infrastructure.

Book a demo How it works

ISO/IEC 27001 · ENS conformity · Aligned with NIS2 and CER

Esquema de un andén con puntos de acceso Wi-Fi midiendo la distancia a tres agentes y una trayectoria ajustada al plano de la estación ANDÉN ± 7 m · 2,1 s
accuracy in station
5-10 m

accuracy in station

publication latency
<5 s

publication latency

configurable refresh
15-30 s

configurable refresh

availability (SLA)
99.95 %

availability (SLA)

beacons in your infrastructure
0

beacons in your infrastructure

The starting point

Underground, knowing where your team is stops being trivial

Above ground, location has been a solved problem for twenty years. Forty metres below, surrounded by concrete, steel and curves, it is not. And that is precisely where it matters most.

GPS does not reach

No satellite signal, no position. The system the whole organisation relies on stops working at exactly the moment something happens on a platform.

Classic RTLS means building works

Anchors and beacons per zone mean cabling, power, permits and night-time work windows. On a network in service that adds up to months, and it is where most of these projects stall.

Tags have to be managed

Handing out, charging, replacing and auditing one device per officer per shift is a new daily process someone has to sustain. The day it is not sustained, the system lies.

How it works

Three pieces, none of them new to your infrastructure

The app runs on the terminals your officers already carry. The measurement relies on access points that are already mounted. The only thing added is software.

Wi-Fi RTT / FTM Cellular GPS where available EDGE Android terminal Ranging and filtering Publishes every 15-30 s Offline store and retry SERVER Fusion EKF / UKF filters Map matching NLOS detection OPERATIONS Portal Live map History and replay Roles, 2FA and audit trail REST API Webhooks CSV / JSON export

01 · Terminal

It measures, it does not guess

Wi-Fi RTT/FTM (IEEE 802.11mc) measures the round-trip time of the signal to each access point: an actual distance, not an estimate derived from received signal strength. The app dynamically picks the most reliable source between Wi-Fi, cellular and GPS, stores what it cannot send, and restarts itself.

02 · Fusion

It knows where walking is possible

Probabilistic filters combine the measurements and constrain them to the actual layout of platforms, concourses and tunnels. A position that would fall inside a wall is discarded before publication; multipath and non-line-of-sight measurements are detected and downgraded rather than allowed to contaminate the result.

03 · Portal

And it leaves a record

Live map, history and event replay. Two-factor, role-based access, an audit trail of who looked at what, and history export whenever you need the data outside the portal.

How it works in detail

On-board layer

And when the officer boards the train?

That is where station location runs out: the reference moves, the car is a metal box, and knowing somebody is seven metres from the platform edge does not tell you whether they are on the train that is pulling away. The on-board layer answers that with an identity instead of a coordinate.

ANDÉN TRAIN 4207 CAR 1 CAR 2 CAR 3 CAR 4 Car 3 · at station

One beacon per carriage, adhesive and battery-powered, fitted during a depot visit. The officer’s phone reads it and the system publishes the train, the car and the station it is at. No cabling, no power take-off from the vehicle, and not a metre of platform or tunnel touched: the beacons go in the rolling stock, not in your infrastructure.

  • An identity, not an estimate

    Car 3 of train 4207. No error radius and no room for doubt: either the phone sees that beacon or it does not.

  • You can go and meet the train

    Knowing which car the officer is in on the service arriving in two minutes turns a search into an appointment, at the right door.

  • And it saves you surveying the tunnels

    Between stations, car identity replaces the coordinate. The radio survey can be limited to whichever stations matter to you.

How the on-board layer works

It is optional. The base layer works on its own, and this is added when on-board service justifies it.

The difference

What you will not have to install

The comparison is not about accuracy: it is about what reaching that accuracy costs. An anchor-based system gives you centimetres in exchange for an infrastructure project. We give you metres in exchange for nothing.

Beacon and tag based RTLS Metrosafe
Hardware in the station Dedicated anchors per zone None: the Wi-Fi you already have
Hardware on the person An active tag to hand out and charge Their corporate smartphone
Civil works Cabling, power and mounting None
Upfront investment High and proportional to zones Minimal
Time to service Months, with night-time windows Weeks, without stopping service
Vendor lock-in Verticalised by the supplier Any FTM-capable access point
Scaling to another network A brand new infrastructure project A replication playbook

The on-board layer does fit one beacon per carriage, but inside the rolling stock: adhesive, battery-powered and fitted in the depot. No platform and no tunnel is touched, and people still carry no tag of any kind.

Security and compliance

Built to get through your security committee

In critical infrastructure the final technical call is not made by the person who needs the system, but by the person accountable for the network. This is the part that matters to them.

  • TLS encryption in transit and at rest
  • Two-factor authentication (2FA)
  • Role-based access control (RBAC)
  • Network microsegmentation
  • Rate limiting and OWASP API protection
  • Audit trail of access and actions
  • Continuous SAST and DAST in CI/CD
  • External cybersecurity audit
  • Configurable data retention
  • Anonymisation where the use case allows it

Regulatory framework

  • Spanish National Security Framework (ENS) and CCN-STIC guidance
  • ISO/IEC 27001 · ISO 9001 · UNE 166002
  • Aligned with NIS2 and CER, the two European directives raising the bar on cybersecurity and resilience in transport.
  • ISO 9001
  • ISO/IEC 27001
  • UNE 166002
  • ENS conformity
  • Innovative SME

Locating people is personal data. Metrosafe is deployed with a legal basis, prior information to the worker, bounded retention and anonymisation where the use case allows it.

How worker data is handled

Where it fits

Wherever Wi-Fi is dense and GPS is absent

Metro is the anchor case, but nothing about the pattern is rail-specific: as soon as Wi-Fi coverage is in place and satellites cannot reach, the answer is the same.

Metro and urban rail

Platforms, concourses, interchange corridors and tunnel sections, with teams spread across shifts.
Learn more

Tunnels and interchange hubs

Linear infrastructure and interchange nodes where satellite coverage is intermittent or absent.
Learn more

Airports and hospitals

Large indoor footprints with dense Wi-Fi, mobile staff and traceability requirements.
Learn more

Facility management and logistics

Extensive sites where knowing where the service team is changes the response time.
Learn more

Getting started

Start with one line, not the whole network

A scoped pilot of 8 to 16 weeks over one line or a set of stations. With numeric acceptance criteria agreed in writing before it starts, so there is no argument at the end about whether it worked.

  1. 01

    Survey

    Inventory of FTM-capable access points, station layouts and a map of constraints.

  2. 02

    Go live

    App on the terminals, server and portal in service, telemetry and security active.

  3. 03

    Measurement

    Accuracy and latency campaigns per station, against the acceptance criteria agreed upfront.

  4. 04

    Decision

    A report with real metrics your committee can use directly in the procurement file.

See the full process

Frequently asked

What people ask before the demo

How do you locate personnel where there is no GPS?
By measuring the round-trip time of the signal (Wi-Fi RTT / FTM, IEEE 802.11mc) to the access points that already exist in the station, fusing that measurement with cellular and with GPS where it becomes available, and constraining the result to the actual layout of platforms and tunnels.
Do we need to install beacons or hand out tags?
No. It uses the corporate smartphone the officer already carries and the Wi-Fi network already installed across stations. No new hardware and no civil works.
Can you tell which train and which carriage an officer is in?
Yes, with the on-board layer. It is an optional layer that fits one BLE beacon per carriage: adhesive, battery-powered, no cabling, fitted during a depot visit. The officer’s corporate phone reads it and the system publishes the train, the car and the station it is at. It is not a coordinate with an error margin, it is an identification: car 3 of train 4207. And because the beacons sit in the rolling stock, the network infrastructure is not touched.
What accuracy do you get?
Between 5 and 10 metres in station, with publication latency under 5 seconds and a refresh rate configurable between 15 and 30 seconds. It is worth saying why that figure and not a smaller one: the Wi-Fi RTT literature reports 1-2 metres under direct line-of-sight conditions, and a platform full of concrete, columns and trains is not that condition. In real operation, 5-10 metres is the difference between platform and concourse, or between directions of travel: enough to know where to send support and which entrance to use.
Does it meet European security requirements?
It is designed in line with the Spanish National Security Framework (ENS) and CCN-STIC guidance, with TLS encryption, two-factor authentication, role-based access control and an audit trail, aligned with NIS2 and CER, and verified by an external, independent cybersecurity audit.
How long does a deployment take?
A scoped pilot over one line or a set of stations goes live in 8 to 16 weeks, without interrupting service and without works windows.

Tell us about your network

Let us know how many stations you run, how many terminals are in service and what you need to solve. You get a concrete pilot proposal back, not a brochure.

We reply within one business day.