Getting Started

A short setup path from empty database to a verified end-to-end fire drill.

Response process · Koronadal City

Setup path

Six steps from an empty database to a verified end-to-end drill.

1
Confirm both services are online
The status dots in the top bar must be green. If not, run npm run dev from the project root and check the URLs in Settings.
Open Settings →
2
Register a building
Add the name, address, coordinates, occupancy type, and number of storeys. One floor is created per storey automatically.
Register a building →
3
Add rooms and devices
Add rooms to each floor, then attach cameras and sensors. Camera codes are what the AI uses to name the room on fire.
Open the building registry →
4
Add stations and hydrants
The nearest active station is chosen by coordinates when an incident escalates, and hydrant distance rides along with the dispatch.
Manage stations →
5
Run a simulated detection
From the Guard Console, trigger a detection to see the confirmation countdown, then confirm, dismiss, or let it time out.
Open Guard Console →
6
Inspect the spatial views
Open the 3D twin to see the fire room, the city heatmap for risk intensity, and the route map for station-to-fire paths with hydrants.
Open 3D twin →
7
Review the record
Open the incident to read the AI reasoning, the dispatch package, and the audit trail of who did what and when.
View incidents →

Created by php artisan db:seed. Password for all of them is 'password'.

Detect → Confirm → Analyze → Notify BFP → Dispatch. Units are never auto-committed.

1Detect — AI cameras and sensors flag smoke, flame, and heat in a room.
2Confirm — Guard verifies with live feed, countdown, Confirm / False alarm / Call BFP.
3Analyze — Locate the room in the 3D twin (floors, 3D/2D/thermal) and plan routes on the map.
4Notify BFP — Confirmed package (feeds, victims, ETA) reaches Station Command.
5Dispatch — Commander presses Dispatch units to commit crews, then tracks on-scene progress.