AnBanjir: the last kilometre of a flood warning
Street-level flash-flood nowcasts, an offline-hardened response console and crowd-verified waterlines — sold one council at a time, to the authority that actually answers for the flooded underpass.
The state alert said “danger.” Your street said “which street?”
National radar knows the cloud is heavy. The council still has to know that the underpass floods in eleven minutes, that Bus 4 shouldn’t go that way tonight, and that the hall on Jalan Sepuh is at capacity — with or without signal.
- Residents · street-level warning
- Council control room
- Responders & shelters
Eleven minutes. That’s the whole product.
The street reports itself
Drain cameras, council water-level gauges and ten-second crowd photos of a rising kerb all resolve into one street-state feed. Residents report the way they already do — into a system that answers back with the map they helped draw.
Nowcast, not forecast
MetMalaysia radar and JPS hazard layers feed a per-catchment model that answers the only question that matters at 4pm: which streets, this hour, in which direction. Confidence published, thresholds set by the council, never by a vendor.
The council operates it
One console for the control room: alerts to every phone in the affected band, evacuee routing around the flooded underpass, shelter capacity, and the state engine that keeps mutating correctly when the tower goes dark — inherited from AnKampung.
One instance, four seats at it
Every consumer of a council’s AnBanjir is that council’s own operation — residents, control room, responders, and (under a separate licence) the state looking down. Same signatory, different hats.
Residents · street-level warning
Push and SMS alerts scoped to your actual road and your actual risk band — not a state-wide siren that trained everyone to ignore it.
Council control room
One instance per PBT: thresholds, alerts, shelter logistics and the post-event record the audit and the next budget submission are written from.
Responders & shelters
AnVerified-credentialed responders get routed assignments; shelters see incoming evacuees before the buses do — offline-capable, because the hall loses power first.
State agency overlay
Where a state or NADMA wants the picture across councils, they get a read-only overlay licensed separately — the aggregation is a product, never a join.
The doctrine made product
One council, one instance
Petaling Jaya signs with MPJ; Shah Alam with MBSA; Kuala Lumpur with DBKL. Nothing flows between them because nothing is allowed to — the fiefdom doctrine applied to the level where flood money is actually spent.
Offline is the design centre
The state engine — gates closed, routes forbidden, shelters full — mutates offline and resolves legally on reconnect. A flood product that needs four bars is a flood product that fails during the flood.
Crowd reports carry proof or carry weight-zero
A waterline photo is matched against hazard layers and neighbouring sightings before it moves a map state. Panic and fabrication both cost the reporter's confidence score; the map stays honest or the alert bell loses its meaning.
Questions, answered
Yes — and the doctrine is integrate-downstream, never-duplicate. JPS hazard maps and MetMalaysia radar are inputs the council already has rights to use. What no federal agency sells a PBT is the operating layer: their streets, their thresholds, their console, their record. The gap isn't the science; it's the last kilometre of authority and logistics.
Ready to build something intelligent?
Let's engineer your next product — from idea to launch.