Auxilus Mos · Emergency and operations
Local evacuation-center registration, occupancy, relief-batch receipt, and citizen QR workflows in active development.
What it is
PBB Salus is an in-progress local evacuation-center and relief-distribution module. Its implemented Laravel foundation covers multiple centers, express and regular registration, validation, opaque tags and QR codes, movement or aggregate occupancy tracking, relief batches, receipts, and correction workflows.
Person-level records remain local. Hotline may pull a bearer-protected, privacy-safe aggregate summary for SITREP use, while release packaging, Kit Setup installation, and full relief inventory remain outside the confirmed V1 implementation.
Problem it solves
Evacuation operations need one local record of active centers, registrations, current occupancy, relief schedules, and receipts even when internet access is unavailable and person-level data must remain within the node.
Core workflow
Operators open one or more evacuation-center activations and configure capacity, zones, and tracking mode.
Workers use express or regular lanes for individuals and families, then validate records and issue opaque tags or QR codes.
The operation records individual entry and exit or approved aggregate gate counts, with reconciliation when needed.
Workers manage scheduled relief batches, confirm receipts, and route corrections through controlled approval.
Hotline can request aggregate counts and freshness metadata without receiving person-level records.
Who uses it
Offline-first behavior
Deployment placement
Evacuation operations node; Barangay node
Hardware, connectivity, power, training, travel, and field logistics remain deployment-specific.Practical questions
Yes. Core evacuation-center work can continue on the local PBB network as long as the Salus node and its database are running.
No individual evacuee records are sent under the confirmed design. Hotline receives only approved totals and basic information showing how recent and complete those totals are.
No. V1 records planned relief batches, what people receive, and corrections. Full warehouse work such as receiving stock, storage, transfers, damaged or lost goods, purchasing, and accounting is not included yet.
The QR code contains a random, hard-to-guess identifier instead of personal information. Scanning it provides only a limited local view.
Not yet. Much of the application is built, but its release package, installer, data-preparation tools, and connection to Kit Setup are still incomplete.
No. V1 does not include map display, location-based boundaries, a native mobile app, or continuous tracking of people's locations.
Status and readiness
Operational routes and data models are implemented through the current milestones, but release packaging and field installation are not complete.
Connected platform
Local-node foundation
Briefing and pilot discussion
Explore how a local-node deployment could support practical service continuity in your community.
