Trafficure · Capabilities
Monitoring, alerts, analytics and reports, for the whole network
Trafficure turns Google Maps Roads Management Insights data into four working capabilities a city operations team uses every day: monitor every road, get alerted as congestion forms, read road-level analytics, and ship reports automatically. No cameras, no sensors, no construction.
Get a demo →The shape of the platform
Four capabilities, one road graph
Trafficure is built on Google Maps Roads Management Insights, which delivers anonymized speed and movement signals aggregated per road segment from the more than one billion smartphones running Google Maps and Waze. RMI is the data layer. Trafficure is the activation layer that turns it into something an operations team can run a city on.
That activation layer resolves into four capabilities. Each one works off the same normalized road graph, so monitoring, alerting, analytics and reporting all speak about the same roads, the same segments and the same baselines. This page walks through what each does and what an agency does with it.
Capability 1
Monitor every road, not just the junctions with cameras
Trafficure monitors the whole network, arterials, residential streets and service lanes alike, normalized into more than 15,000 road segments per city against the road graph. The network refreshes on a two-minute cycle, so the operations picture is current rather than a snapshot from hours ago.
- 01
Coverage · The full network is in view
100% road coverage rather than the few hundred junctions a camera system can reach. The roads that never had a sensor are now monitored alongside the ones that did.
- 02
Refresh · A two-minute cycle
The whole network re-reads every two minutes, so what the command centre sees reflects the road now, not a stale reading.
- 03
Resilience · No hardware to fail
Probe data is unaffected by fog, rain, dust or darkness, and there are no cameras to decay. Coverage does not erode as equipment ages.
Capability 2
Be alerted as congestion forms, not after the complaints
Trafficure compares each road against its own baseline, a normal speed profile computed from roughly ninety days of history, and fires a predictive alert when a corridor begins to deviate. The alert lands while congestion is forming, which is the window in which an agency can still act on it. Alerts go out across the channels a team already uses.
Fires as congestion forms
Machine-learning alerts trigger on deviation from baseline, before a corridor is fully jammed, so a response is proactive rather than reactive.
Reaches the team where they are
Command centre dashboard, WhatsApp and SMS, email, Slack, webhook and X. Thresholds, priority levels and auto-resolve are configurable per agency.
Surfaced and closed
An alert is not just raised. Build-ups are tracked through to clearance, so the operations team sees the event from formation to resolution.
One road graph
Congestion, caught as it forms.
The same road graph that monitors the whole city is the one the alert reads from. A build-up is scored against that corridor's own baseline the moment it starts to deviate, and the alert reaches the team across every channel they already use.
Capability 3
Read the road at street level, with analytics you can act on
Trafficure normalizes more than 15,000 segments per city against the road graph and runs the full analytics cycle in under 120 seconds. The output is road-level, not a city-wide average: a CityPulse traffic-health score per corridor, a congestion ratio of free-flow speed to actual speed, and baselines built from roughly ninety days of history. That is the layer a planner uses to find a chronic bottleneck and prove an intervention worked.
- 01
CityPulse · A traffic-health score per road
A composite metric that turns raw speed into a readable health signal for each corridor, used directly in reports.
- 02
Congestion ratio · Free-flow against actual
The ratio of a road's free-flow speed to its current speed, so severity is comparable across very different roads.
- 03
Baselines · Normal, learned from history
Per-road baselines computed from roughly ninety days of history. Deviation from normal is what drives both the analytics and the alerts.
Speed along chainage AM peak 08:00 to 10:00 vs free-flow
Segments eastbound · mean speed includes junction approach delay
| Seg | Link | Length | Free-flow | AM peak | Ratio | Travel time | Delay |
|---|---|---|---|---|---|---|---|
| S1 | J01 → J02 | 1.2 km | 48 | 34 km/h | 71% | 2.1 min | 0.6 |
| S2 | J02 → J03 | 0.9 km | 46 | 27 km/h | 59% | 2.0 min | 0.8 |
| S3 | J03 → J04 | 1.1 km | 46 | 14 km/h | 30% | 4.7 min | 3.3 |
| S4 | J04 → J05 | 0.8 km | 40 | 11 km/h | 28% | 4.4 min | 3.2 |
| S5 | J05 → J06 | 1.3 km | 48 | 29 km/h | 60% | 2.7 min | 1.1 |
| S6 | J06 → J07 | 1.1 km | 44 | 33 km/h | 75% | 2.0 min | 0.5 |
| corridor | 6.4 km | 45.7 | 21.5 km/h | 47% | 17.9 min | 9.5 min |
Junction diagnostics worst approach, AM peak
| Jn | Name | Control | Cycle | v/c | Delay | LOS |
|---|---|---|---|---|---|---|
| J02 | Mill Gate | signal | 120 s | 0.82 | 38 s | D |
| J03 | Old Bridge | signal | 140 s | 0.94 | 74 s | E |
| J04 | Clock Tower | signal | 180 s | 1.08 | 178 s | F |
| J05 | Depot Cross | signal | 160 s | 1.02 | 151 s | F |
| J06 | Lakeview | roundabout | · | 0.71 | 22 s | C |
Corridor mean speed by hour peak spreading, quarter on quarter
Capability 4
Ship reports automatically, in standard formats
The analytics do not stop at a dashboard. Trafficure generates PDF reports built on the CityPulse scores and exports standard formats, so a weekly operations brief or a before-and-after intervention study is produced from the same live record rather than rebuilt by hand. Exports are standard formats, which means no vendor lock-in on the data an agency owns.
- 01
Automated · PDF reports, generated
Operations and planning reports are produced from live data, so the brief reflects the road graph as it stands rather than a hand-assembled snapshot.
- 02
Portable · Standard-format exports
Data exports in standard formats keep the agency's record portable, with no vendor lock-in on what the city owns.
- 03
Evidence · Before and after, on record
Because baselines persist, an intervention can be measured against the corridor's own history and the result written into a report.
Where the line is
What Trafficure is, and what it is not
These four capabilities are monitoring, alerting, analytics and reporting. Trafficure is not built for sub-second adaptive signal control, and it does not claim to be: that is where sensors and junction-level systems belong.
It runs on aggregated, anonymized movement with k-anonymity at the source, which means very sparse roads can drop out and there is no commercial-fleet-only or individual-level view. It is complementary to a camera ITMS, which keeps enforcement and number-plate recognition, while Trafficure covers the monitoring gap across the rest of the network.
Proof
Running in production, across cities
The four capabilities are not a roadmap. They run today in Pune, where Pune City Traffic Police became the first Indian city with software-only city-wide traffic management, and across the Kolkata region. In Pune the platform surfaced and closed 39,734 congestion build-ups with a median clearance of 26 minutes.
- Pune City Traffic Police
- Pune Municipal Corporation
- Kolkata Police
- Howrah Police
- Bidhannagar
- Barrackpore
See all four capabilities on your own road network.
Bring your city's corridors. We will show you live monitoring, predictive alerts, analytics and reports running on Trafficure.
Get a demo →