Lone worker dashboard

corinna.hammerstingl@f24.com Updated by corinna.hammerstingl@f24.com

Please note that visibility of this functionality depends on your product edition.

The Lone worker dashboard is used to display monitoring and alarms of loneworkers and accessible via the operating cockpit.

Monitor

The "Status Monitoring" selector can be used to select for which status the participants are to be displayed:

  • All: The monitored participants and the participants who have an alarm are displayed.
  • Alarms: Only participants who have had an active alarm within the last 60 minutes are displayed.
  • Monitoring: All participants who are currently or have been in active lone working monitoring within the last 60 minutes are displayed.

In the overview on the right side is a summary of all current open lone worker monitorings:

  • Number of monitoring sessions: Here the sum of all active single monitors is displayed.
  • Number of alarms: Is the sum of all open alarms in the system. An incident must be edited and closed so that it is no longer visible in the lone worker dashboard.
  • Unprocessed alarms: This displays all current alarms that have not yet been as-signed to a user for processing.

Table fields:

  • Assignee: An incident can be assigned to a Web user; this user is displayed in this field.
  • Status: Display of the current status of the person.

    Registered

    The person is actively logged into the system and is working alone.

    Left

    The person has finished working alone within the last 60 minutes.

    Manual

    There is an active deliberate alarm which has been Launched within the last 60 minutes.

    Man-down

    There is an active situation alarm which has been Launched within the last 60 minutes.

    NO_MOVEMENT

    There is an active quiescent alarm which has been Launched within the last 60 minutes.

    Timeout

    The solo work was not finished regularly. There is a time alarm within the last 60 minutes.

    Panic

    There is an alarm, which has been caused by pull-ing the pull line (loss alarm). This alarm was Laun-ched within the last 60 minutes.

    Technical

    There is a technical malfunction on the end device. This means, for example, that the battery level has fallen below the defined threshold value or that there is a loss of connection to the terminal device.

  • Start time: Here you can see when the loneworking was started.
  • End time: Here you can see when the loneworking will be or has been finished.
  • Employee ID: A defined ID of the employee.
  • Surname: The last name entered for the employee.
  • First name: The first name entered for the employee.
  • Place: The localization information. Depending on the status, this can be the information of an NFC tag, a Bluetooth beacon or the GPS information.
  • Alarm: Here is the information which alarm is launched or was launched. This can vary depending on the configuration, for example if different alarm scenarios are defined for each localization point.

In the event of an alarm, the affected event flashes red in the display and a notification tone is played. As soon as a user accepts the incident, the red display is deactivated, and the sound is stopped.

In the detailed view, additional information about the respective event is displayed. If GPS data has been transmitted in the event of an alarm, it is visualised using Google Maps. In addition to the GPS data, a building plan for a positioning object (NFC, BLE Beacon, Gateway, WLAN) can be stored in the location profile and then be displayed.

React

The following steps are necessary to react to an incident:

  1. Accept the incident (only possible for web users)
  2. Click on the summary of the incident
  3. Execute the individually defined steps in case of an alarm. These are the organizational measures in case of a single workstation alarm. After the measures have been carried out accordingly, the web user must click on the button «External alarm carried out». The hook for the alarm is set. A system entry is also created as logbook information.
  4. Create a logbook entry to complete the process. After the entry has been made, the process can be completely terminated by clicking the «Complete Incident» button. The entry will be saved in the reports of the loneworker.

How did we do?

Profile Settings for Loneworking

Contact