Overwatch takes everything the AWE Initiative already collects — community reports, verified events, identity matches, PSIM triggers, patrol coverage — and indexes it onto Uber's open-source H3 grid. The result: a live, explainable safety score for every square kilometre of every deployment, queryable from a map, a dashboard, a report, or an API call.
AWE was built from day one around fusion — identity, community signal, geospatial context and AI orchestration stacked into one Event schema. Overwatch is the missing abstraction layer that turns that fused schema into a single spatial number, everywhere.
WhatsApp Intel already classifies informal chatter into severity-scored, geolocated incidents in real time.
LIVE MODULEFaceMap and VOI Tracker resolve a face or plate into a persistent, searchable record with confidence scoring.
LIVE MODULECameras, alarms and perimeter sensors already feed straight into the same event pipeline.
LIVE MODULE4,392 wards, 3,591 facilities, 9 municipalities and custom geofences — already the platform's geographic spine.
LIVE MODULEPatrol compliance and response times are already measured — Overwatch gives that data somewhere spatial to live.
LIVE MODULEEvery stream already resolves to one Event/Location schema, already subscribed to by government and enterprise clients.
LIVE MODULEWards and geofences answer "whose jurisdiction is this?" Hexagons answer "how risky is this exact spot?" — at a resolution that's consistent everywhere, regardless of how a boundary happens to be drawn. Overwatch keeps both: official boundaries for governance, hexagons for scoring.
Two different distances between a cell and its neighbours (edge vs. corner) — distorts clustering, smoothing and "nearby" comparisons.
Exactly one distance to every neighbour, 16 hierarchical resolutions, and near-instant "is this point in this cluster?" lookups — the same properties Uber open-sourced H3 to solve for ride dispatch.
Overwatch sits as a new engine inside the Intelligence Hub, reading from every module that already exists and writing scores back out to every surface that needs them.
In line with AWE's Transparency pillar, a hex score is never a black box. Seven weighted layers compose it, and every layer is independently inspectable — availability-aware, so a missing signal redistributes its share instead of zeroing the score.
This is exactly what a client receives when they click a hex on the map or query it via the API — the score, the maths behind it, the underlying intelligence, and how the surrounding area pulled it up or down.
| Layer | Weight | Layer score | Contribution |
|---|---|---|---|
| Community Signal | 0.24 | 0.70 | 0.168 |
| Verified Events | 0.20 | 0.55 | 0.110 |
| User Engagement | 0.14 | 0.51 | 0.071 |
| Identity Matches | 0.13 | 0.30 | 0.039 |
| PSIM / Sensor State | 0.12 | 0.40 | 0.048 |
| Built Environment | 0.10 | 0.62 | 0.062 |
| Responder Context | 0.07 | 0.45 | 0.032 |
| Own-cell raw score | 0.53 |
No new dashboard to learn — Overwatch writes into the modules clients already use every day.
A togglable safe→severe hex overlay on the existing live map — the same visual language as ward and geofence layers.
Every incoming event shows the ambient score of the hex it landed in — plus how it compares to its immediate neighbours.
Entry/exit alert sensitivity adjusts automatically for zones sitting inside a high-scoring hex.
Patrol paths bias toward high-scoring hexes during coverage gaps, instead of a fixed loop.
Hex score over time becomes an exportable KPI for tenders, board packs and municipal reviews.
The same hex, scored differently for a retail footfall use case, an estate's night-patrol use case, or an insurer's underwriting use case.
Insurance prices with it. Logistics routes around it. Municipalities budget against it. Real estate discloses with it. Control rooms operate on it. Communities get alerted by it. Agents reason with it.
Overwatch extends the Intelligence Hub's existing subscriber model — Government, Enterprise and Private Sector clients already integrate the Unified Event API. Hex scores become one more queryable layer inside that same contract.
Municipal & national agencies integrate the fused hex feed into their own command-and-control or GIS systems, city- or region-wide.
Insurers, logistics and analytics platforms pull raw hex-scored streams to enrich underwriting, routing and risk models.
Security operators and multi-site PSIM clients subscribe at site or portfolio level to only the hexes covering their own footprint.
Overwatch is built on H3, Uber's open-source discrete global grid system. H3 doesn't stop at a country border — it's already projected across the entire Earth, on every icosahedron face, at every resolution. Drag the globe, or click a city, to see exactly how many H3 cells are already indexed there.
"Base cells" and "total cells" are two different numbers. H3 starts from just 122 resolution-0 base cells laid over an icosahedron — but each subsequent resolution divides every cell into 7 children, so by resolution 8 (our working resolution) that's 691,776,122 unique cells already indexed across the entire planet, with zero new geospatial infrastructure required to use any of them.
City counts below are computed live in your browser using the actual open-source h3-js library (v4) — h3.polygonToCellsExperimental() run against a circular approximation of each city's own municipal area, in "containmentOverlapping" mode so partially-covered edge cells are counted too. Not a static estimate, and not a lookup table — a real function call.
Overwatch is being built in phases directly on top of AWE's existing modules, so early phases go live without waiting on the later ones.
Already shipped, already earning its keep.
The current sprint. Pilot sites are already indexing live.
Turning the score into something operators act on, not just view.
Moving from "what happened here" to "what's likely next, and what's the safest way through."
Opening the engine outward as a standalone, monetisable data product.
Overwatch isn't a separate sale — it's a tier inside the subscription model AWE already runs. Figures below are a starting template; final scope and pricing are set per deployment.
Pricing tiers are illustrative and intended as a working template for commercial scoping — not final published rates.
Book a walkthrough and we'll run Overwatch against a real ward or site you already operate.