Insights Page FAQ
What is the Insights Page?
The Insights Page on the SlateSafety Web App allows admins to analyze aggregated SlateSafety data for their organization. The page can provide metrics to demonstrate that your heat stress program is working, or it can reveal where there is room for improvement.
The Insights Page Summary provides a topline overview to help you evaluate how your heat stress program performed for any selected time period. Organization's will aim to have as few Heat Stress Events as possible, so this metric is at the top of the Insights Summary. But for many jobs, heat stress events are inevitable, so it is important to have a consistent and effective Heat Stress Intervention plan that results in an Intervention Rate near 100%. Lastly, the Heat Stress Timeliness Rate can show that not all interventions are happening in a timely manner. If an intervention does not occur until after 30 minutes, then it can lower your Heat Stress Timeliness Rate.
How do I use the Insights Page?
- Simply login the SlateSafety Web App
- Navigate to the page at the top labeled Insights
- Select the date range you are interested in from the date range picker
- Optional: filter to specific Groups or Users
- That's it! View the Summary tab to see an overview of your organization's data. Explore the other tabs to view other insights.
What questions does the Insights Page answer?
Heat Stress Events and Alerts
- How many heat stress events and BAND V2 alerts happened last month?
- Are alerts being responded to?
- How many alerts happened in July compared to June?
- How quickly are alerts being responded to?
- Are some groups responding to heat stress events better than others?
- Which groups experience the most heat stress events?
- Which type of alerts are occuring the most/the least?
- Which groups are wearing the BAND V2s the most/the least?
- Which groups have the highest core temperature/exertion/heart rate/HRLV?
- Which locations have the highest average heat index?
Can I print the Insights Page?
Yes. Follow the instructions below based on your operating system.
- Windows: Press Ctrl + P
- Mac OS: Press Cmd + P
What are Heat Stress Events and Heat Stress Interventions?
Heat Stress Event: occurs whenever an individual triggers a biometric alert or a series of biometric alerts. For example, if User 1 triggers a Core Temp alert.
Heat Stress Intervention: occurs whenever an individual successfully responds to a heat stress event by resting and reducing their core temperature, exertion, heart rate, etc.
How are Heat Stress Events (HSEs) determined?
To determine when a Heat Stress Event (HSE) has occurred, the system walks through triggered biometric alerts and groups them as one "event" if they occur within short enough time of each other (note that "feature" alerts like Tap and No-Movement are not considered). Specifically, alerts are considered to be part of the same HSE if, when ordered, they occur within ten minutes of the last alert in the sequence. For example, given this timeline of alerts:
|Alert #||Alert Type||Time|
|1||Heart Rate||1:00 PM|
|2||Core Temp||1:02 PM|
|4||Heart Rate||1:30 PM|
|5||Core Temp||1:38 PM|
|7||Heart Rate||2:15 PM|
The following HSEs are determined:
How are Heat Stress Interventions (HSIs) determined?
To determine when a Heat Stress Intervention (HSI) has occurred for a corresponding HSE, the system defines a sample period around when the alerts occur, and an observation period after the HSE during which an intervention is expected. The sample period is defined as the period ending with the last alert in the HSE, and starting with either 10 minutes before that last alert's timestamp, or the timestamp of the first alert in the HSE, whichever comes earlier. The observation period is defined as the hour after the last alert in the HSE. For each alert type in the HSE, a threshold is computed using the sample period, defined as:
threshold = avg(m)−stddev(m)
- avg(m) = the average of the metric over the sample period
- stddev(m) = one standard deviation of the metric over the sample period
Once the threshold(s) are computed, an HSI is considered to have occurred if one of the following is true:
- the system can find a period of 5 minutes with at least 1 minute's worth of data where the average for each relevant biometric falls below the specified thresholds, or
- a Return-To-Work (RTW) notification is triggered within the observation period
If neither condition is met, the HSI is considered to be a Missed Heat Stress Intervention.
How are Heat Stress Intervention Times determined?
Intervention times are computed depending on how the intervention was recognized:
- If an intervention was determined via finding biometrics under a calculated threshold, then the intervention time is then calculated by taking the difference in time between when the first alert is triggered in a Heat Stress Event (HSE) and the timestamp of the first biometric in the 5-minute period during which the user fell below the calculated thresholds.
- If an intervention was determined via observing a Return-To-Work, then the intervention time is calculated by taking the difference in time between when the first alert is triggered in a HSE and the timestamp of when the Return-To-Work occurred.
- If both of the above methods determine an intervention has occurred, then the earliest intervention is used for determining the intervention time.
Disclaimers and Caveats
The statistics contained with this insights report are not a substitute for the opinion of an industrial hygienist, occupational health specialist, or other such qualified professional. These individuals can provide a true assessment of the effectiveness of your organization's heat stress management, based on their own expertise and observations.
The statistics/observations provided in this Insights report are meant to help highlight and guide possible areas of improvement for your organization in heat stress risk management. Only you and your wearers, however, know the true nature of how the system is being used. In particular, the Heat Stress Event (HSE), Heat Stress Intervention (HSI) and Heat Stress Timeliness (HST) statistics all assume the following:
- a band is worn throughout the entirety of a heat stress event, and
- the alerts contained within a heat stress event are genuine.
If neither of these conditions are completely present, then the accuracy and subsequent usefulness of the statistics for a period may deteriorate. Given the above caveats, here are some examples of scenarios where noise may be introduced into the Heat Stress statistics:
- Your organization, as part of its Standard Operating Procedures (SOP), mandates that wearers remove all PPE as part of the cooldown process. In this scenario, HSEs with false missed HSIs will be recorded, as the band is unable to record the subsequent fall-off in user biometrics or a possible Return-To-Work event.
- You organization, as part of its SOP, allows wearers to continue their physical activity after an alert has triggered. In this scenario, the Heat Stress statistics may be misleading, as an alert and its subsequent thresholds may be treated more as just warnings rather than a strict "stop work" signal.
- Your organization does not ensure the proper wear and use of all BANDs. In this scenario, a false alert may be triggered, which will cause a false HSE to be recorded.
- Very rarely, the band's firmware may contain a bug or have a hardware malfunction that causes it to report a false alert, which will cause a HSE to be recorded when it shouldn't be.
It is up to your organization to decide to what extent its SOP should be adjusted according to the statistics presented in this report. Again, always consult the expertise of an industrial hygienist, occupational health specialist, or other such qualified professionals when making adjustments to your heat stress risk management policies and procedures.