WEBVTT

00:00:00.039 --> 00:00:04.389
Unit Alerts helps a coordination team find units that have remained in a timed

00:00:04.389 --> 00:00:06.860
status longer than the department expects.

00:00:07.269 --> 00:00:11.979
In Big Board, use the plus icon and choose Unit Alerts from Add Widget.

00:00:12.300 --> 00:00:13.699
Scroll to the new panel.

00:00:14.170 --> 00:00:17.729
This department initially shows No status timers configured.

00:00:18.180 --> 00:00:22.620
That message describes the missing timer configuration; it does not establish

00:00:22.620 --> 00:00:24.780
that every unit has reported promptly.

00:00:25.139 --> 00:00:28.579
The thresholds are department settings managed in the Core website.

00:00:28.829 --> 00:00:33.300
In Core, open Department Settings, choose Operations, then

00:00:33.370 --> 00:00:35.089
Mapping and BigBoard Settings.

00:00:35.479 --> 00:00:37.589
Scroll to Unit Status Timers.

00:00:37.999 --> 00:00:43.230
The table separates Status, Warn after in minutes, and Alert after in minutes.

00:00:43.579 --> 00:00:47.199
Each displayed status has its own row, including Dispatched,

00:00:47.369 --> 00:00:49.980
Responding, En Route and On Scene.

00:00:50.390 --> 00:00:53.800
Initially, both columns are zero throughout this training table.

00:00:54.179 --> 00:00:57.879
The helper text explains that leaving both at zero times nothing.

00:00:58.289 --> 00:01:01.209
Choose values that fit your department's reporting process.

00:01:01.419 --> 00:01:06.390
For this software exercise, enter two under Warn after and four under

00:01:06.419 --> 00:01:08.510
Alert after on the Responding row.

00:01:08.970 --> 00:01:10.679
Leave the other rows unchanged.

00:01:11.030 --> 00:01:14.839
These are demonstration values, not a recommended response standard.

00:01:15.280 --> 00:01:19.159
The two columns allow the department to distinguish a warning interval from a

00:01:19.159 --> 00:01:21.790
later alert interval for the same status.

00:01:22.220 --> 00:01:26.739
Review the row label and both minute values before saving, so the timer applies

00:01:26.739 --> 00:01:28.620
to the intended operational meaning.

00:01:28.870 --> 00:01:32.510
Below the table, set Reason when acknowledging to Required

00:01:32.510 --> 00:01:33.959
for warnings and alerts.

00:01:34.399 --> 00:01:37.610
The help explains that this policy applies when acknowledging

00:01:37.640 --> 00:01:39.600
or muting a status timer alert.

00:01:40.070 --> 00:01:41.129
Select Save.

00:01:41.600 --> 00:01:44.830
Reload Mapping and BigBoard Settings and return to the table:

00:01:45.240 --> 00:01:47.599
Responding still shows two and four.

00:01:48.029 --> 00:01:51.429
Scroll down again and verify the required-reason selection.

00:01:51.929 --> 00:01:55.699
Reading back both controls checks the saved configuration before you

00:01:55.699 --> 00:01:57.410
examine its effect in Big Board.

00:01:57.600 --> 00:01:58.720
Reload Big Board.

00:01:59.229 --> 00:02:04.400
Unit Alerts now shows Squad Three, its Responding state, Firehouse Fifty One

00:02:04.480 --> 00:02:06.339
and the elapsed time in that state.

00:02:06.759 --> 00:02:10.459
This fictional record is already more than one hundred eighty hours

00:02:10.459 --> 00:02:15.640
old, far beyond the four-minute alert threshold, so it appears red immediately.

00:02:16.089 --> 00:02:19.550
The elapsed value helps identify a status report needing review.

00:02:19.929 --> 00:02:22.210
It does not explain why the report is old.

00:02:22.649 --> 00:02:26.589
Use the unit's normal reporting and coordination process to investigate.

00:02:26.790 --> 00:02:30.120
Select the Squad Three row to open Unit status alert.

00:02:30.489 --> 00:02:33.629
With Reason empty, the sheet explains the requirement and

00:02:33.629 --> 00:02:35.430
disables Acknowledge and Mute.

00:02:35.829 --> 00:02:39.720
Enter the clearly labeled training reason, then select Acknowledge.

00:02:40.100 --> 00:02:40.999
Reopen the row.

00:02:41.400 --> 00:02:46.289
The saved section now says Seen by Wallace Boden and retains the exercise note.

00:02:46.660 --> 00:02:51.039
Acknowledging records that review; the unit still has its Responding state.

00:02:51.410 --> 00:02:54.560
The sheet also offers Clear acknowledgement for removing

00:02:54.560 --> 00:02:55.709
the saved acknowledgement.

00:02:55.840 --> 00:02:59.419
If the small alert panel clips the saved note, open the gear

00:02:59.419 --> 00:03:01.700
settings and select Unit Alerts.

00:03:02.079 --> 00:03:07.129
Under Widget Size, this example uses width four and height three grid units.

00:03:07.489 --> 00:03:09.619
Select Save and return to the panel.

00:03:10.039 --> 00:03:14.430
The wider, taller result shows the unit, state, reviewer and

00:03:14.430 --> 00:03:16.049
complete training note together.

00:03:16.489 --> 00:03:20.540
Reopening these settings after a later reload still shows four by three.

00:03:20.919 --> 00:03:24.309
Check the rendered result as well as the values in the editing form.

00:03:24.509 --> 00:03:26.050
Open the same alert again.

00:03:26.470 --> 00:03:29.309
Under Mute for, select fifteen minutes.

00:03:29.690 --> 00:03:32.420
Replace the reason with the note describing this fictional

00:03:32.420 --> 00:03:34.940
mute exercise, then choose Mute.

00:03:35.389 --> 00:03:38.589
The panel now has a collapsed Muted, one, section.

00:03:38.990 --> 00:03:42.199
Expand it to see Squad Three and the saved mute reason.

00:03:42.520 --> 00:03:44.420
The unit still says Responding.

00:03:44.830 --> 00:03:49.520
Moving an alert into this section changes how the timer alert is presented; it does

00:03:49.520 --> 00:03:51.850
not resolve the underlying unit state.

00:03:52.070 --> 00:03:57.050
Reload Big Board, expand Muted, one, and reopen Squad Three.

00:03:57.559 --> 00:04:01.899
The sheet retains the reviewer and reason and displays a Muted until time.

00:04:02.350 --> 00:04:05.069
This checks that the saved mute survived a reload.

00:04:05.529 --> 00:04:08.420
For this exercise, choose Clear acknowledgement.

00:04:08.840 --> 00:04:11.879
The unit returns to the active red alert panel, because its

00:04:11.950 --> 00:04:15.600
unchanged Responding record is still beyond the configured threshold.

00:04:16.000 --> 00:04:20.120
The timer, saved acknowledgement or mute, and underlying unit status

00:04:20.170 --> 00:04:21.819
are separate things to verify.

00:04:22.029 --> 00:04:26.739
A security control room can use status timers to review a delayed patrol update.

00:04:27.190 --> 00:04:30.659
Search-and-rescue coordinators can follow a team's reporting interval.

00:04:31.119 --> 00:04:34.869
Community paramedicine and mental health response teams, wildland

00:04:34.869 --> 00:04:39.870
contractors, industrial response teams, and fire and E M S departments can

00:04:39.870 --> 00:04:43.860
apply the same review process with appropriate statuses and thresholds.

00:04:44.239 --> 00:04:48.120
Configure the timer, inspect the actual unit and elapsed time,

00:04:48.569 --> 00:04:52.280
document the review, and verify the saved result using fictional

00:04:52.280 --> 00:04:54.470
data before adopting the process.
