03 · Respond — For LGUs, DRRM offices, and the teams that move first
Haribon
One live map, instead of forty group chats.
Haribon puts incidents, sensor readings, hazard scores, stock and vehicles on one live map — so the people dispatching are reading a situation instead of reassembling it from messages.
- map for every screen
- 1
- no polling, no stale tabs
- Live
- products feeding it
- 3
- early access
- LGU-first
The problem
Nobody has the whole picture, and everybody has part of it.
During a response, the information exists. It is just scattered across a dozen group chats, three spreadsheets, a radio net, and several people’s heads. The barangay knows which road went under. The warehouse knows what is left on the pallet. The rescue team knows where it actually is. None of them can see the other two.
So the coordinator spends the first hours of an emergency doing data entry — reconciling messages into a picture that is already out of date by the time it is complete. Relief arrives where it was needed an hour ago. A truck takes a road that closed at noon.
Haribon is the shared picture. Incidents, hazard zones, live sensor readings, team positions, inventory and vehicles on one map that every screen is looking at simultaneously. The backend is reactive by design: when a road closes, it closes on everyone’s map at once. Nobody should be hitting refresh during a disaster.
Before landfall, the same map is a pre-positioning tool — Bedrock says who is exposed, so goods move before the roads go. After landfall, Stormwatch stations report what the water is doing, so routing is based on a reading rather than a guess. That is the loop closing.
How it works
Four moves, end to end.
- 01
Take in
Incidents, Stormwatch readings and Bedrock exposure land on one map.
- 02
Decide
Coordinators see who is cut off and what is still reachable, right now.
- 03
Dispatch
Teams, vehicles and stock go out on routes that avoid closed roads.
- 04
Sync
Every change reaches every screen at once. Nobody hits refresh.
Live operational map
Everyone works from the same map.
Incidents, sensor readings, hazard zones, and team positions on a single GIS picture — the one thing every responder, coordinator and executive is looking at. Shared situational awareness is not a feature of the response; it is the precondition for one.
| Unit | Task | Route | ETA |
|---|---|---|---|
| Boat 2 | Rooftop rescue · 6 pax | via Panganiban | 6 min |
| Team B | Evacuation · 11 pax | rerouted · road closed | 11 min |
| Truck 4 | Relief · 40 packs | via Diversion Rd | 9 min |
| Team D | Medical | on foot · flooded | 14 min |
Logistics and dispatch
Inventory, vehicles, routes.
Track relief stock, vehicles and teams; route around roads that are impassable right now rather than roads that were passable this morning; get the right load to the right barangay. The dispatch board and the situation map are the same object, so they cannot fall out of sync.
Fed by the other two
It starts from a reading, not a guess.
Stormwatch stations send live flood measurements from the ground. Bedrock supplies who is exposed at address level. Response planning begins from evidence that was already collected before anyone picked up a radio.
Coordinator
Field team
Mayor’s office
Real-time by architecture
The map updates itself.
A reactive backend pushes every change to every connected screen as it happens. No polling, no stale tab, no coordinator wondering whether the version they are looking at is the current one.
Where this stands
Platform build, and our flagship. Early access is going to a small number of LGUs first, because a response tool that has not been used in a response is a prototype.
Built on
Push on Haribon. We answer the hard ones ourselves.
Questions go to the engineer who built the part you’re asking about — not a sales sequence.