All projects

Emergency Services

Ambulance Corridor

A green corridor that opens just ahead of the ambulance, junction by junction, and gives the road back behind it.

An ambulance loses most of its time stopped at signals it had no way to clear in advance. This turns a dispatch into a route, the route into a per-junction preemption schedule, and drives that schedule against signal hardware on a control loop running four times a second — holding each junction for the window the pass actually needs, and no longer.

Line drawing of a road grid with one route held open through six junctions, an ambulance mid-corridor, and a staggered schedule of arm, green and release windows beside a chained audit record

Key Capabilities

Routing by A* over live link speeds, with signal delay modelled rather than ignored
Hospital chosen on clinical capability first, drive time only to break a tie
Arm, green and release windows sized by how long the queue takes to discharge
One clock shared by signal cycles, safety interlocks and corridor timing
Every signal command signed, carrying its own expiry inside the signature
An edge agent in the cabinet that enforces its own maximum hold
Vendor-neutral transport — ICCC HTTP, MQTT or Modbus behind one interface
Hash-chained audit log covering every state change the corridor makes
Live console: per-junction state, corridor telemetry and fleet health on one map

How It Works

1

Dispatch

A call becomes an origin, a patient and a destination

2

Hospital Chosen

Clinical capability first, drive time only to break a tie

3

Route Solved

Live speeds and modelled signal delay, not shortest distance

4

Junctions Scheduled

An arm, green and release window for each junction on the route

5

Corridor Runs

Greens held, the pass confirmed, the tail re-timed, the road released

Who It's For

108 Emergency Ambulance Services
City Traffic Police
ICCC & Municipal Corporations
District Hospitals & Emergency Departments
State Road Transport Authorities

Impact & Value

  • Time is saved at the junctions an ambulance never has to stop at
  • Each junction is held for the pass, then handed straight back to normal cycling
  • Green is granted on a schedule, never as a blanket override of a district
  • Crews stop negotiating junctions by phone, one call at a time
  • Every corridor can be reconstructed afterwards from the audit record

Safety & Assurance

  • Every command signed and expiring — a stale command cannot act on a junction
  • Safety interlocks evaluated on every command, including in simulation and in demos
  • Pedestrian clearance and conflicting movements are locks, not preferences
  • The cabinet enforces its own release; release from upstream is an optimisation, not the guarantee
  • Hash-chained audit record — an altered entry breaks the chain it sits in
Where this stands today

Simulation only. No signal hardware has been driven, no 108 or EMRI feed is connected, no hospital emergency department endpoint exists, and junction coordinates are approximate seeds. Nothing here should touch a live signal until the commissioning checklist has been completed for that junction. What is real is the control logic, the safety interlocks and the audit chain — and those run identically in simulation and in the field, because there is no separate offline implementation.

Deployment Models

On-Premise (ICCC)
Private Cloud
Hybrid (State Data Centres)
Edge at the Signal Cabinet

Ready to open a corridor?

Tell us which junctions sit on your busiest ambulance route and what controls them today. That conversation usually settles quickly whether a pilot is worth running.