Tunas Akara
Back to Portfolio
Public Facility Emergency Button Network

Public Facility Emergency Button Network

Year: 2026Role: IT Consultant / Software Architectiot

Roughly 100 sites use connection checks, area-based alert routing, and a traceable history of button presses.

Technology

GoNext.jsMQTTPostgreSQLTelegram API

Public Facility Emergency Button Network

This emergency button system grew from a single-location proof of concept into a network at roughly 100 public facility sites. I designed and built it through full deployment. Operators can monitor device conditions and trace alert handling when a button is pressed.

Challenge

A healthy button and a dead button both look quiet when unused. Operators need to know their condition before an emergency. When a button is pressed, the alert must reach staff responsible for that area rather than wait in an unmonitored channel.

Solution

Each gateway sends a regular connection signal to the central system. Continuous checks monitor these signals. A location that stops reporting moves to warning, then offline, according to configured time thresholds.

Connection signals are separate from emergency alerts. Routine reports that a device is connected do not create incidents. Alerts route according to staff responsibilities and area. If not acknowledged, they escalate to a supervisor and then central operations on a timed sequence.

Every press, status change, and notification adds to history without overwriting previous records. Armed and disarmed modes let accidental presses be recorded without immediately calling responders.

Impact

Device conditions are continuously checked at roughly a hundred locations. A device that stops reporting appears as a warning within about a minute. False alerts can be recorded and closed without escalating an emergency call.

Separating connection reports from incidents keeps the alert channel useful for operators. The principles are discussed in designing emergency buttons for multiple locations.