Home
Home
Rota
Set standard rota via the websiteChange availability via the websiteGroup rota on the websiteTeam rota's on the websiteSet up and apply availability patternsSchedule amendments reportUnderstaffing due to schedule changesRed border in rotaWhen is a person counted as part of the crew that is operationally available?
Duties
Teams
Website
Dashboards
Regional management
Announcements
General
Maximum size of attachments24/7 SupportApp crashes/freezes regularlySupported browsersWhat data is audited?Our official appsOur new FAQ environment
Integrations
Application Programming Interface (API)Home AssistantHomeyiCalendar (iCal)
Hardware
How do I set up WiFi on the station monitor?Changing station monitor time zoneChange station monitor theme
Alerting & Alert Channels
Fair seat allocationRealerting in case of understaffingWhat are the added benefits of Primary Alerting?How to Create an Alerting Policy In FSRWhat happens if the Primary Alerting App is not sending heartbeats?
Smartphone app
Pagers
Geofencing & GPS
Contracts
Assign contract to userRequesting absence via the websiteHow does the Carryover mechanism work in Contracts?
User accounts & preferences
Activity Reports
Create a activity reportReview activity report
Station configuration
Add skills to stationModules
Working Time Directive
Where can we enable Working Time Directive Rules?Can I get a notification when I breach a Working Time Directive Rule? What types of Working Time Directive rules be created?How can I read the Working time directive report?
Payroll
How to download the payroll report fileCluster and Station payroll reportsWarnings in the Payroll Report

What happens if the Primary Alerting App is not sending heartbeats?

The Primary Alerting App performs a critical process, which is why it is configured to perform a heartbeat every 15 minutes to ensure that it is properly connected to our system.

What happens when FireServiceRota does not receive a heartbeat from a device after 15 minutes?

We now support the option to enable certain actions to take place when a heartbeat is missed. This actions need to be enabled per device. Currently we support the following actions:

  • The user becomes unavailable for 15 minutes: When a heartbeat is missed, and if the user is currently available (on call), the user will become unavailable for 15 minutes. A Priority 1 message will be sent to the user, and a comment will be left in the Group Rota. This ensures that, in case of a call-out to an incident, users that are not accessible through their mobile device are not called.
  • This feature will NOT remove the duty from a user who is on “duty” (Vagt).
  • If the user was not available at any station at the moment of the missed heartbeat, no change will take place to their availability.

This feature is not enabled by default. To get it enabled, contact us via helpdesk.

English
Powered by Product Fruits