Operational summary
When an SOS alarm fires, the operations center must act in seconds: locate the operator, dispatch a response mission, and notify the team through the agreed channels.
In the web hub, the map can focus the unit and the detail panel shows recent context. The tactical log records the incident for later review.
Deep dive
Picture the scene: Tuesday 22:14, a private security operator on an isolated patrol triggers SOS from his Sentinel node. The alert crosses LoRa, hits the gateway, climbs to backend, and shows up on the operations center dashboard in seconds. The center operator has a clear protocol and integrated tools to respond.
Step 1, see: the central panel raises the high-priority alert, the map auto-focuses on the last known position, and the node marker turns orange with accelerated pulse. The center operator opens the unit detail panel: name of the field operator, last heartbeat, current geofence, exact SOS time. All on screen in less than five seconds since the alert arrived.
Step 2, dispatch: with the situation confirmed, the center operator generates a response mission for a nearby unit (or backup team) from the missions drawer. The mission appears immediately in the receiver's mobile app with all the details. The center can also use fleet chat for parallel textual coordination while radio stays for critical voice.
Step 3, notify and close: in parallel to tactical coordination, the center operator follows the organization's SOP (notify supervisor, contact family if applicable, escalate to external forces if severity warrants). The tactical log records each action for audit. Once the incident is operationally resolved—not before—the SOS is closed in the panel and the complete incident remains in history for review and continuous process improvement.
Key takeaways
- See: open the map and unit sheet; confirm identity and last position.
- Dispatch mission: from Missions assign a task to the node or a response crew.
- Notify: use fleet chat or voice protocol per your SOP; do not close the incident in software without operational sign-off.
Flow diagram
+-------------+ +-----------------+ +------------------+
| SOS triggers| --> | Map + unit card | --> | Mission + alerts |
| (app/node) | | View / focus | | Chat / protocol |
+-------------+ +-----------------+ +------------------+
| |
+-----------+-----------+
v
Tactical log (audit)Open in product