WEBVTT

00:00:00.059 --> 00:00:03.599
Begin in New Call with a clearly named training exercise.

00:00:04.000 --> 00:00:08.220
Complete Name and Nature, then choose the department’s Priority and Type.

00:00:08.619 --> 00:00:13.020
Here, Urgent and Structure Fire match the prepared Academy Training Alarm.

00:00:13.449 --> 00:00:17.600
A run card is configured beforehand in Core administration; the dispatch

00:00:17.629 --> 00:00:19.329
app uses that configuration.

00:00:19.819 --> 00:00:24.389
Enter and check the incident’s Latitude and Longitude before comparing resources.

00:00:24.790 --> 00:00:28.270
These are fictional incident coordinates, not a device location.

00:00:28.709 --> 00:00:32.599
The first exercise stays unsent while we inspect its recommendation.

00:00:32.959 --> 00:00:37.459
This browser recording cannot establish native background GPS collection or

00:00:37.459 --> 00:00:39.750
delivery of an alert to a real device.

00:00:39.869 --> 00:00:43.550
Under Dispatch To, read the named card and its Decision.

00:00:44.050 --> 00:00:47.129
The rule asks whether an engine is within eight minutes.

00:00:47.570 --> 00:00:52.940
The first preview says Yes: Engine 51 has an estimated two-minute response.

00:00:53.310 --> 00:00:56.510
That does not mean the entire response package is complete.

00:00:56.979 --> 00:00:59.000
Ideal configuration not

00:00:59.000 --> 00:01:01.450
available and Could not fill explain that the

00:01:01.450 --> 00:01:03.819
incident-officer positions are too old.

00:01:04.319 --> 00:01:07.110
Read the explanation before accepting a proposal.

00:01:07.520 --> 00:01:11.520
An available vehicle and an eligible officer are separate requirements.

00:01:11.970 --> 00:01:15.549
The advice to send the initial response is guidance from this configured

00:01:15.549 --> 00:01:19.549
card; it is not proof that resources have already been dispatched.

00:01:19.680 --> 00:01:23.739
For the next preview, the three unchanged fictional officers received

00:01:23.739 --> 00:01:27.350
fresh simulated station fixes through the controlled training setup.

00:01:27.759 --> 00:01:32.680
Their statuses and earlier history were preserved; no device GPS was used.

00:01:33.129 --> 00:01:38.319
The refreshed proposal now lists Engine 51 under Recommended units and Christopher

00:01:38.319 --> 00:01:40.399
Herrmann under Recommended personnel.

00:01:40.850 --> 00:01:45.050
The Fills labels explain which package requirement each resource satisfies.

00:01:45.499 --> 00:01:49.610
Read both rows and their reasons, then choose Apply recommendation.

00:01:50.069 --> 00:01:52.099
The form changes to two selected.

00:01:52.560 --> 00:01:56.709
Applying the proposal prepares a selection; it does not create the call.

00:01:57.110 --> 00:02:01.310
Open that selection to inspect the actual people and units before proceeding.

00:02:01.469 --> 00:02:07.010
The Select Dispatch Recipients sheet offers Closest, Name and Available only.

00:02:07.429 --> 00:02:10.280
Closest follows the server’s location-aware board.

00:02:10.710 --> 00:02:14.460
Herrmann appears with Nearest number one and the Run card badge.

00:02:14.860 --> 00:02:20.149
Name changes the order; Blake Gallo then appears with Unavailable and No location.

00:02:20.579 --> 00:02:23.960
The absence of a location is useful information, not

00:02:23.960 --> 00:02:25.349
an invitation to guess one.

00:02:25.839 --> 00:02:29.950
Available only reduces this example from fourteen users to twelve.

00:02:30.399 --> 00:02:34.539
Previously selected recipients remain selected, so review the checkmarks

00:02:34.570 --> 00:02:36.300
and total as well as the filter.

00:02:36.690 --> 00:02:39.030
Everyone is a broader recipient choice.

00:02:39.469 --> 00:02:43.039
Leave it clear when this exercise needs only named resources.

00:02:43.239 --> 00:02:45.529
Search for Engine to narrow the sheet.

00:02:45.880 --> 00:02:49.719
The Groups entry called Engine 51 and the unit called Engine

00:02:49.719 --> 00:02:51.689
51 are separate choices.

00:02:52.090 --> 00:02:55.660
In this example the group is unchecked and the unit is checked.

00:02:56.069 --> 00:02:59.919
Read the unit’s Available status, Herrmann’s crew assignment and

00:03:00.079 --> 00:03:01.740
At station position source.

00:03:02.089 --> 00:03:05.230
Its Nearest number three badge is its place among the board’s

00:03:05.230 --> 00:03:09.169
available units; it does not say that three engines are selected.

00:03:09.560 --> 00:03:13.259
The row shows an estimated travel time, while the board can rank

00:03:13.259 --> 00:03:15.260
units using turnout plus travel.

00:03:15.630 --> 00:03:18.880
Confirm returns the selected recipients to the call form.

00:03:19.280 --> 00:03:22.299
It is still separate from creating or dispatching the call.

00:03:22.539 --> 00:03:25.730
Changing only the unsent incident’s coordinates creates

00:03:25.730 --> 00:03:27.110
the distant comparison.

00:03:27.539 --> 00:03:30.839
The same engine now fails the eight-minute condition, and the

00:03:30.839 --> 00:03:33.200
outcome becomes Review alternatives.

00:03:33.610 --> 00:03:36.879
The advice-only branch recommends no additional package.

00:03:37.200 --> 00:03:40.879
The recipient sheet shows about one hundred and one kilometres and roughly

00:03:40.879 --> 00:03:42.000
one hundred and

00:03:42.000 --> 00:03:44.600
ninety-eight minutes for both Herrmann and Engine 51.

00:03:45.119 --> 00:03:48.779
The run-card response estimate is slightly longer because its response

00:03:48.779 --> 00:03:50.490
calculation includes turnout.

00:03:50.879 --> 00:03:53.660
These are estimates, not a promise of arrival.

00:03:54.080 --> 00:03:58.070
Notice that the earlier two selected recipients remain in the form even

00:03:58.070 --> 00:03:59.730
when the recommendation changes.

00:04:00.090 --> 00:04:02.000
Restore the near coordinates and review

00:04:02.000 --> 00:04:04.270
both the new decision and your selection.

00:04:04.399 --> 00:04:08.970
For the saved example, a separate call named TRAINING ONLY, Dispatch

00:04:08.970 --> 00:04:12.229
allocation recording was created with those same two fictional

00:04:12.229 --> 00:04:14.469
recipients after checking every field.

00:04:15.019 --> 00:04:18.849
Open Dispatched to inspect what the application stored: Herrmann

00:04:18.849 --> 00:04:21.770
as a user and Engine 51 as a unit.

00:04:22.299 --> 00:04:26.369
Dispatch additional resources opens the existing call’s recommendation.

00:04:26.760 --> 00:04:30.000
Its banner says the decision was pinned from the dispatcher’s preview,

00:04:30.369 --> 00:04:33.910
and the explanation counts the engine and officer already on the call.

00:04:34.420 --> 00:04:37.269
Zero additional recommendations can mean the existing

00:04:37.269 --> 00:04:38.980
allocation covers the package.

00:04:39.339 --> 00:04:43.530
Strike alarm two is visible, but this training card has only one configured

00:04:43.530 --> 00:04:46.240
level, so no escalation is exercised here.

00:04:46.400 --> 00:04:49.120
Re-evaluate requests a current calculation.

00:04:49.570 --> 00:04:54.570
Here it returns No and Review alternatives after ordinary call creation

00:04:54.570 --> 00:04:56.420
changed the engine to Responding.

00:04:56.839 --> 00:05:00.960
Treat this as a fresh assessment, not another dispatch or evidence

00:05:00.960 --> 00:05:02.850
that the earlier recipients vanished.

00:05:03.260 --> 00:05:05.389
Cancel the picker without adding anyone.

00:05:05.910 --> 00:05:11.270
To finish this disposable exercise, Close Call uses Closed, a training note, and

00:05:11.270 --> 00:05:13.570
Notify everyone on the call switched off.

00:05:13.910 --> 00:05:15.690
Only this new call was closed.

00:05:16.160 --> 00:05:19.000
The console returned to the original three active

00:05:19.000 --> 00:05:23.559
calls, and Activity records the engine’s normal change from Responding to Released.

00:05:24.039 --> 00:05:28.080
Awaiting Resources is a separate queue for outstanding requirements; the

00:05:28.080 --> 00:05:32.390
captured queue is empty, so no requirement fulfilment or dismissal is claimed.
