InnerWeb
Skip to main content

Alarm simulation on the hall map: a demo case

A plant director watched during a demo how an SOS and a stillness alert appeared on the isometric hall map, together with a sound signal, within a few seconds. This describes a demo scenario on a demonstration instance, not a production deployment. We show what happens on screen and in the background, so that a similar demo can be repeated.

3 s
SOS countdown with the option to cancel
5.3 s
duration of the SOS siren
Source: IsoMap SOS function documentation
3 s
polling interval of the work feed by the map
Source: IsoMap SOS function documentation

Starting point: the director wants to see the reaction, not a description

The plant director had already heard about employee location systems. He wanted to see one thing: what happens on the dispatcher's screen when an employee calls for help or stops moving. Feature descriptions did not convince him, because every vendor gives similar claims.

The demo was therefore prepared as a simulation of events on the isometric hall map. It ran on a demonstration instance with the plant's data, and the participants in the events were demonstration accounts in a domain reserved for testing. No one outside the demo received a notification.

Scene one: SOS from a watch and a siren on the map

An SOS alarm from a watch starts with a triple click or a long press of the button. A three-second countdown follows, which allows an accidental call to be cancelled. During the demo this element drew the most attention, because the director immediately asked about false alarms.

The map plays a siren when a new work appears in the work feed and it comes from a template with map sound enabled. A silent report is a template without this option. The siren lasts 5.3 s and repeats twice, and a second work arriving during the signal does not play a second sound.

The work feed is polled every 3 s, so a few seconds pass from creating the event to its appearance on the map. This is the time the director was watching.

Timing parameters of the alarm in the demo

Timing parameters of the alarm in the demoBar chart: SOS countdown 3 s, feed polling 3 s, siren 5.3 s0246sSOS countdown: 3 s3 sSOS countdownFeed polling: 3 s3 sFeed pollingOne siren: 5.3 s5.3 sOne siren
Source: Function and IsoMap SOS Alarm Sound function documentation

Scene two: stillness and a two-sided alarm

Stillness detection is two-sided. The application analyzes the device sensors, while the server independently measures the time. A full alarm is triggered only when both measurements agree, which limits false reports, the very issue the director had raised.

After the stillness threshold is exceeded, the system sends a push and an e-mail notification, creates an alarm permit from the ALARM template, marks the alarm on the map, and may trigger an external webhook. During the demo the last of these effects was visible: a red marker at the employee's location.

A technical condition worth remembering: stillness is drawn on the map only for a permit from a template named ALARM, and SOS for a template named SOS. Without attaching the location to the template, the alarm exists only in the cache and is not visible.

What went well and what needed attention

What worked well was that the director could trigger the event himself on a demonstration account and see it on the map. Active participation builds more trust than watching a recording.

Two technical details are worth keeping in mind. Browsers block sound without a user gesture, so after opening the map one click on it is needed, otherwise the siren will not play. After the first load of a hall the map only remembers the existing works and does not ring, the sound is triggered only by new works.

  • a click on the map after opening it, to unlock the sound,
  • first load of the hall without sound, alarms only for new works,
  • SOS and ALARM templates with the location attached,
  • demonstration accounts instead of real employees.

Conclusions from the case

An alarm simulation on the map is the shortest route to showing the value of the system to the person responsible for the safety of the whole plant. It shortens the distance between a claim and proof to a few seconds.

The key is preparation: correct templates, attached locations and the click that unlocks the sound. Without them, the best scenario ends in silence on the map.

Video

Frequently asked questions

How do you avoid a false SOS?

An SOS from a watch has a three-second countdown during which the alarm can be cancelled. Stillness additionally requires the app and server measurements to agree.

Why did the siren not sound during the demo?

Most often the browser blocked the sound without a user gesture. One click on the map after opening it is enough. Another cause may be a template without the option to play sound on the map.

Does the demo send notifications to real people?

No. Demonstration accounts use addresses in a domain reserved for testing, so messages do not reach anyone.

See the alarm on the map of your hall

Book a demo on your plant's data. We will prepare the SOS and stillness scenario for your roles.

Let's talk