WEBVTT

00:00:00.029 --> 00:00:03.799
In the Chicago Fire demonstration department, we will compare Engine

00:00:03.799 --> 00:00:07.349
51, Truck 81 and Reserve Engine 51.

00:00:07.969 --> 00:00:10.100
These are fictional training resources.

00:00:10.569 --> 00:00:14.329
Before opening a call, inspect each unit's type, station

00:00:14.329 --> 00:00:16.139
assignment and current status.

00:00:16.590 --> 00:00:19.889
A nearby unit in maintenance is different from an available unit.

00:00:20.370 --> 00:00:23.280
Check that station coordinates are correct and that crews have

00:00:23.280 --> 00:00:24.969
usable current assignments.

00:00:25.350 --> 00:00:29.489
This preparation makes the nearest list an operational comparison instead of

00:00:29.489 --> 00:00:31.620
a collection of unexplained distances.

00:00:31.799 --> 00:00:34.000
Open New Call and enter a training

00:00:34.000 --> 00:00:34.819
name and nature.

00:00:35.309 --> 00:00:38.000
Choose the intended type and priority, then

00:00:38.000 --> 00:00:40.060
place a pin at the exercise location.

00:00:40.499 --> 00:00:45.989
You can enter latitude and longitude and use Set Pin On Map, or use the location

00:00:45.989 --> 00:00:47.659
tools your department makes visible.

00:00:48.139 --> 00:00:52.409
Confirm the pin represents the incident rather than a station or destination.

00:00:52.809 --> 00:00:57.530
Without a usable incident location, Resgrid cannot compare response distances.

00:00:57.989 --> 00:01:01.200
Wait for the lists to finish refreshing after the point changes.

00:01:01.399 --> 00:01:03.530
Scroll to the unit dispatch lists.

00:01:03.919 --> 00:01:06.829
The Units tab compares the units you may dispatch.

00:01:07.200 --> 00:01:10.530
The Firehouse 51 tab shows our station resources.

00:01:10.889 --> 00:01:14.519
This training department has all six units assigned to that station.

00:01:15.030 --> 00:01:18.390
Read the current status alongside ETA and position.

00:01:18.860 --> 00:01:22.839
Nearest badges identify the first available resources with measurable

00:01:22.839 --> 00:01:24.409
distance in the ranked result.

00:01:24.759 --> 00:01:28.290
They do not certify equipment readiness or crew capability.

00:01:28.659 --> 00:01:33.300
Compare the named unit and its situation before ticking a recipient, even when

00:01:33.300 --> 00:01:35.139
it carries the first nearest badge.

00:01:35.280 --> 00:01:38.740
The response comparison can include turnout as well as travel.

00:01:39.210 --> 00:01:44.280
In Call and Dispatch Settings, set In-quarters turnout to 120 seconds for

00:01:44.280 --> 00:01:47.000
this exercise, save, and

00:01:47.000 --> 00:01:47.599
reopen the page.

00:01:48.019 --> 00:01:49.750
Mobile turnout stays at zero.

00:01:50.250 --> 00:01:52.790
Return to New Call and set the training pin again.

00:01:53.280 --> 00:01:56.489
The unit rows now show an estimated two-minute response

00:01:56.560 --> 00:01:58.800
including 120 seconds of turnout.

00:01:59.280 --> 00:02:03.109
Here the origin is the station; this does not establish the

00:02:03.109 --> 00:02:04.599
unit's physical location.

00:02:04.999 --> 00:02:07.669
The distance measures separation from the incident.

00:02:08.059 --> 00:02:12.739
An estimated time uses an approximation, while a provider-derived drive time

00:02:12.739 --> 00:02:16.629
depends on the positions and route information available at that moment.

00:02:16.749 --> 00:02:20.309
Inspect Shift Coverage and Role Mix as well as response time.

00:02:20.739 --> 00:02:23.839
Initially, our unit rows show No crew assigned.

00:02:24.279 --> 00:02:26.669
Open Units, then Unit Staffing.

00:02:27.119 --> 00:02:31.909
In this exercise, choose Christopher Herrmann for Engine 51's Officer or Team

00:02:31.909 --> 00:02:34.000
Lead seat, save, and

00:02:34.000 --> 00:02:34.830
reopen the page.

00:02:35.260 --> 00:02:39.949
Engine 51 now says Fully Staffed because its one configured seat is filled.

00:02:40.400 --> 00:02:43.500
That is not proof of a complete operational engine crew.

00:02:43.859 --> 00:02:46.209
Define the seats and qualification requirements

00:02:46.209 --> 00:02:47.939
your department actually needs.

00:02:48.330 --> 00:02:51.379
Return to New Call and refresh the incident comparison.

00:02:51.780 --> 00:02:55.030
Read the resulting crew and role mix rather than inferring them

00:02:55.030 --> 00:02:58.609
from group membership, a vehicle's seats or its nearest badge.

00:02:58.720 --> 00:03:01.249
Click Station location for Engine 51.

00:03:01.700 --> 00:03:05.040
The position panel compares its response origin with the call.

00:03:05.430 --> 00:03:07.909
Here Resgrid uses the station origin.

00:03:08.310 --> 00:03:12.530
That can happen for an In Quarters unit or when no usable GPS fix

00:03:12.530 --> 00:03:16.400
is available; it does not confirm the unit's physical whereabouts.

00:03:16.840 --> 00:03:19.539
Check the displayed source and any stale warning.

00:03:20.000 --> 00:03:24.299
If a location is hidden from you, distance and ETA can also be withheld.

00:03:24.689 --> 00:03:28.410
Do not fill that gap by assuming the unit is somewhere else on the map.

00:03:28.639 --> 00:03:32.339
Open Personnel and inspect the same response context for Christopher

00:03:32.339 --> 00:03:34.239
Herrmann, our fictional officer.

00:03:34.770 --> 00:03:37.770
Personnel have their own status and staffing information.

00:03:38.249 --> 00:03:41.759
The positions in this exercise are simulated training fixes.

00:03:42.099 --> 00:03:45.109
Read any stale label before relying on an estimate.

00:03:45.600 --> 00:03:48.619
A person can be close to the incident without being available

00:03:48.619 --> 00:03:52.840
for assignment, and an available person may have no usable position.

00:03:53.330 --> 00:03:57.660
A unit assignment gives useful crew context, but it does not establish that

00:03:57.699 --> 00:03:59.889
this person shares the unit's position.

00:04:00.299 --> 00:04:03.900
Read the actual row rather than transferring a unit's ranking to

00:04:03.969 --> 00:04:08.249
every crew member or assuming a role name proves current qualification.

00:04:08.630 --> 00:04:12.610
Open Call and Dispatch Settings and review Group-Scoped Dispatch.

00:04:13.040 --> 00:04:16.799
Response area boundaries describe which area contains an incident.

00:04:17.200 --> 00:04:21.570
The Group Boundary editor under Stations and Groups is where those areas are drawn.

00:04:22.070 --> 00:04:26.869
Our New Call comparison reports that the incident is not inside any group boundary.

00:04:27.199 --> 00:04:29.879
We will inspect the controls without saving a boundary.

00:04:30.369 --> 00:04:34.049
Dispatch scope controls the candidates used for nearest comparisons.

00:04:34.410 --> 00:04:35.879
These are separate settings.

00:04:36.250 --> 00:04:40.439
This demonstration uses a department administrator with department-wide scope.

00:04:40.949 --> 00:04:44.620
A unit can remain in the dispatch list without a nearest comparison,

00:04:44.870 --> 00:04:48.650
so a missing estimate does not establish that the unit is unavailable.

00:04:49.050 --> 00:04:53.140
When a comparison is missing, check the permitted scope, current status,

00:04:53.219 --> 00:04:56.990
and usable position before deciding what resources are available.

00:04:57.379 --> 00:05:00.170
We will return to New Call without changing permissions.

00:05:00.349 --> 00:05:03.849
Move the incident pin to a second training location and wait for

00:05:03.849 --> 00:05:05.490
the refreshed response values.

00:05:06.010 --> 00:05:09.899
Compare the same named units and personnel before and after the move.

00:05:10.469 --> 00:05:15.000
Engine 51's distance changes from less than a tenth of a kilometer to

00:05:15.000 --> 00:05:15.639
98.8

00:05:15.639 --> 00:05:20.479
kilometers, while its estimate rises from two to 195 minutes.

00:05:20.889 --> 00:05:23.969
These are straight-line estimates, not a routed drive time.

00:05:24.430 --> 00:05:28.049
A change in distance or turnout-adjusted time may change the order.

00:05:28.510 --> 00:05:31.979
Check that the labels and pin still describe the intended exercise.

00:05:32.430 --> 00:05:36.220
The system can retain the view you manually chose, so use the visible

00:05:36.220 --> 00:05:40.340
coordinates and final list values as evidence instead of expecting every

00:05:40.340 --> 00:05:42.489
refresh to zoom the map automatically.

00:05:42.959 --> 00:05:46.849
In this station-based example, several units share an origin, so

00:05:46.849 --> 00:05:50.169
their distances can change together without changing their order.

00:05:50.370 --> 00:05:53.669
Return the incident pin to the original near training location

00:05:53.909 --> 00:05:55.689
and wait for the values to refresh.

00:05:56.189 --> 00:05:58.639
Select the resources that fit the exercise.

00:05:59.030 --> 00:06:03.000
Here we choose Christopher Herrmann, the first nearby officer, and

00:06:03.000 --> 00:06:03.780
Engine 51.

00:06:04.340 --> 00:06:08.840
Engine 51 is third in the overall list, but it is the available engine;

00:06:09.160 --> 00:06:11.000
the reserve engine is out of service.

00:06:11.479 --> 00:06:15.500
Check that the unit selection agrees across its station and Units tabs.

00:06:15.889 --> 00:06:19.789
If a run card also suggests resources, inspect that panel and

00:06:19.789 --> 00:06:21.459
the final checkboxes together.

00:06:21.860 --> 00:06:24.470
Ranking does not send anyone by itself.

00:06:24.910 --> 00:06:29.320
Before saving, review the call, recipients and notification arrangements.

00:06:29.739 --> 00:06:34.320
After the training save, open the resulting call, 26-4 in this

00:06:34.320 --> 00:06:36.779
example, and its Dispatched tab.

00:06:37.239 --> 00:06:41.340
Check Engine 51 and Christopher Herrmann against the intended recipients.

00:06:41.750 --> 00:06:45.150
This proves the saved assignment; it does not establish that

00:06:45.150 --> 00:06:46.680
a device received an alert.

00:06:47.119 --> 00:06:48.970
Confirm member receipt separately.

00:06:49.450 --> 00:06:52.970
Finish by closing only the training call with Send Notification

00:06:53.020 --> 00:06:54.000
off, and

00:06:54.000 --> 00:06:54.699
keep its history.

00:06:55.150 --> 00:06:59.059
Keep the location source, freshness and estimated-time limits in

00:06:59.059 --> 00:07:02.690
your decision, even when the first-ranked choice appears obvious.

00:07:03.120 --> 00:07:06.309
The same review helps a mobile crisis team choose an available

00:07:06.309 --> 00:07:11.019
clinician, a search and rescue team find a nearby qualified member, or a

00:07:11.019 --> 00:07:13.269
security supervisor compare patrols.

00:07:13.699 --> 00:07:18.129
Wildland contractors and industrial teams should also compare crew capability

00:07:18.360 --> 00:07:22.129
and access to the incident before choosing the first-ranked resource.
