WEBVTT

00:00:00.029 --> 00:00:03.319
Open Call Settings in our fictional Chicago Fire department.

00:00:03.740 --> 00:00:06.610
Dispatch Import Email would show its all-call intake

00:00:06.610 --> 00:00:08.789
address; this example is blank.

00:00:09.180 --> 00:00:11.079
Email Type is set to Generic.

00:00:11.460 --> 00:00:15.069
Match the parser to the incoming format before using that channel.

00:00:15.529 --> 00:00:20.469
Prune (Auto Close) Calls is off and Minutes to keep call open is zero.

00:00:20.879 --> 00:00:23.950
The cleanup setting concerns eligible imported calls.

00:00:24.350 --> 00:00:27.309
We are reviewing the controls without sending an import or

00:00:27.309 --> 00:00:29.229
demonstrating an automatic close.

00:00:29.389 --> 00:00:30.940
Scroll to Call Numbering.

00:00:31.399 --> 00:00:39.889
The saved pattern is FD51-{YYYY}-{SEQ}, with four sequence digits.

00:00:40.339 --> 00:00:43.439
Next call number advanced after a separate training call.

00:00:43.849 --> 00:00:46.319
Existing calls keep their original numbers.

00:00:46.730 --> 00:00:50.150
The numbering lesson explains patterns and carry-forward values.

00:00:50.620 --> 00:00:54.360
An email-parser choice does not configure every phone or message

00:00:54.360 --> 00:00:58.849
channel; verify each supported intake route and recipient receipt separately.

00:00:59.039 --> 00:01:00.960
Open Call & Dispatch Settings.

00:01:01.489 --> 00:01:06.099
Use Shift for Group Dispatch selects the resolved on-duty roster; an

00:01:06.099 --> 00:01:09.590
empty roster falls back to group members for notification routing.

00:01:10.109 --> 00:01:14.079
Set Status for Shift Personnel On Dispatch is a separate switch.

00:01:14.499 --> 00:01:18.529
Automatic personnel dispatch and release statuses require both switches

00:01:18.779 --> 00:01:20.789
and use the resolved shift personnel.

00:01:21.279 --> 00:01:24.609
The two Person Call status controls choose those statuses.

00:01:24.939 --> 00:01:26.720
Both switches remain off here.

00:01:27.130 --> 00:01:31.119
Review the actual roster before changing them; an empty notification

00:01:31.119 --> 00:01:34.899
fallback does not create a shift or establish a status change.

00:01:35.130 --> 00:01:39.130
Group-Scoped Dispatch separates area scope from recipient selection.

00:01:39.599 --> 00:01:44.050
When Scope Dispatch to Group Areas is enabled, supported views and nearest

00:01:44.050 --> 00:01:47.810
comparisons follow the member’s group subtree and applicable calls.

00:01:48.159 --> 00:01:51.419
Department administrators and selected Department-Wide Dispatch

00:01:51.419 --> 00:01:53.099
Roles retain a wider view.

00:01:53.529 --> 00:01:57.160
Our scope switch and role exceptions remain off; the operator

00:01:57.160 --> 00:01:58.769
is a department administrator.

00:01:59.189 --> 00:02:01.949
Group Boundary defines response areas separately.

00:02:02.449 --> 00:02:06.240
A unit can remain listed without a nearest comparison, so review

00:02:06.240 --> 00:02:08.810
scope, status and position together.

00:02:09.019 --> 00:02:14.079
Also Dispatch To Assigned Personnel and Also Dispatch To Entire Group can

00:02:14.079 --> 00:02:16.420
expand a unit’s notification audience.

00:02:16.780 --> 00:02:17.869
Both are off here.

00:02:18.409 --> 00:02:22.359
Unit Call Dispatch Status and Unit Call Release Status are

00:02:22.359 --> 00:02:24.209
separate meaning-based choices.

00:02:24.560 --> 00:02:29.640
Defaults resolve within each unit’s own status set; built-in units use Responding

00:02:29.640 --> 00:02:32.189
on dispatch and Released on release.

00:02:32.580 --> 00:02:36.019
A missing matching custom status leaves the unit unchanged.

00:02:36.650 --> 00:02:40.169
Custom-status types can provide type-specific override rows.

00:02:40.529 --> 00:02:45.020
This Engine type uses Standard Actions, so this example has no such rows.

00:02:45.419 --> 00:02:48.619
Review crew assignments and status meanings before broadening

00:02:48.619 --> 00:02:50.660
recipients or changing targets.

00:02:50.799 --> 00:02:56.069
Personnel on Unit Set Unit Status controls linked crew context: a supported

00:02:56.069 --> 00:03:00.249
unit-status submission can place its submitted crew roles into On Unit.

00:03:00.629 --> 00:03:01.999
It remains off here.

00:03:02.459 --> 00:03:04.850
Hold to set status also remains off.

00:03:05.260 --> 00:03:09.449
When enabled in supported Unit and Responder apps, crews hold a status for

00:03:09.449 --> 00:03:14.549
two seconds; statuses requiring a note or destination still open that step.

00:03:15.009 --> 00:03:17.990
Verify that behavior in the app version crews use.

00:03:18.470 --> 00:03:21.689
These switches do not create crew assignments or establish

00:03:21.740 --> 00:03:23.079
anyone’s qualification.

00:03:23.309 --> 00:03:26.960
Run Cards & Automatic Dispatch shows Closest Unit Response

00:03:26.960 --> 00:03:28.689
with automatic dispatch off.

00:03:29.140 --> 00:03:33.609
Rest period deprioritizes recently dispatched resources; minimum

00:03:33.609 --> 00:03:37.830
staffing checks configured seats, and move-up checks station minimums.

00:03:38.330 --> 00:03:42.320
Our rest period is zero, staffing gate off and move-up off.

00:03:42.739 --> 00:03:48.019
Closest Unit Response Tuning has 1800-second location ages, a zero

00:03:48.019 --> 00:03:53.810
radius limit, meaning no maximum, stale locations excluded and routed ETA off.

00:03:54.189 --> 00:03:55.640
The shortlist is five.

00:03:56.000 --> 00:04:01.039
Station turnout is 120 seconds; mobile and personnel turnout are zero.

00:04:01.579 --> 00:04:05.779
Freed-unit automatic dispatch remains off; its limit bounds automatic

00:04:05.779 --> 00:04:07.550
sends while alerts still occur.

00:04:07.960 --> 00:04:12.539
Response codes is empty; its name, colour, retirement and crew-display

00:04:12.539 --> 00:04:14.640
controls apply when codes exist.

00:04:15.020 --> 00:04:17.739
Review New Call recommendations before sending.

00:04:18.079 --> 00:04:21.269
Auto-Enable Check-In Timers for New Calls is off.

00:04:21.670 --> 00:04:24.110
Default Timer Configurations is empty.

00:04:24.559 --> 00:04:29.270
The saved Investigation Personnel override is 60 minutes, warning five,

00:04:29.569 --> 00:04:32.140
enabled for all states and any priority.

00:04:32.579 --> 00:04:36.110
Matching overrides take precedence over defaults; the call’s

00:04:36.110 --> 00:04:37.930
own timer flag also matters.

00:04:38.350 --> 00:04:41.409
Our separately enabled training call shows Boden’s timer.

00:04:41.799 --> 00:04:43.790
No check-in receipt is established here.

00:04:44.250 --> 00:04:47.000
Timer forms use their own Add controls, and

00:04:47.000 --> 00:04:49.000
station coverage has a separate Save.

00:04:49.379 --> 00:04:53.340
Station Coverage Minimums currently has no saved requirements; its

00:04:53.340 --> 00:04:57.389
station, target, count and radius fields are a preparation form.

00:04:57.679 --> 00:05:01.399
New Call Form Fields has separate Visible and Required columns.

00:05:01.810 --> 00:05:05.950
Here the optional fields are visible and their required boxes are clear.

00:05:06.329 --> 00:05:10.549
Name, nature, priority and type always remain required.

00:05:10.950 --> 00:05:15.860
A missing required value can block a new call, archived-call entry or saved edit;

00:05:16.280 --> 00:05:18.479
hidden fields cannot remain mandatory.

00:05:18.960 --> 00:05:22.399
Plus Code is a location-finding aid and cannot be required;

00:05:22.800 --> 00:05:26.140
require GPS Coordinates when a saved point is necessary.

00:05:26.550 --> 00:05:29.000
Review both halves of the table, then the

00:05:29.000 --> 00:05:30.059
corresponding call form.

00:05:30.489 --> 00:05:33.140
This example preserves the current field policy.

00:05:33.309 --> 00:05:36.629
Use the existing training example 26-4.

00:05:37.069 --> 00:05:40.919
Its Dispatched tab stores Engine 51 and Christopher Herrmann.

00:05:41.220 --> 00:05:44.370
Stored assignment alone does not confirm device receipt.

00:05:44.800 --> 00:05:48.960
On its Close Call form, Completed Type is Closed, training notes are

00:05:48.960 --> 00:05:51.620
entered and Send Notification is off.

00:05:51.999 --> 00:05:55.870
The saved call then shows Closed with closing details and notes.

00:05:56.300 --> 00:05:59.579
Release policy moves only units still working that call.

00:05:59.950 --> 00:06:03.689
Units already back in service, unavailable, under maintenance,

00:06:03.790 --> 00:06:07.289
on break or working another open call can keep their status.

00:06:07.610 --> 00:06:11.120
Review status history separately when validating release behavior.

00:06:11.319 --> 00:06:14.829
Close call when last unit clears is off in this example.

00:06:15.280 --> 00:06:20.780
If enabled, every dispatched unit must report finished after dispatch; returning

00:06:20.780 --> 00:06:22.990
or transporting still keeps work open.

00:06:23.479 --> 00:06:28.280
Calls without dispatched units, future undispatched calls and active incident

00:06:28.280 --> 00:06:30.370
command retain their closeout guards.

00:06:30.780 --> 00:06:33.329
This training example uses manual closure.

00:06:33.739 --> 00:06:37.710
Chicago Fire can review station crews and notification audiences.

00:06:38.109 --> 00:06:42.439
Community care or mental health teams can review rosters; search and rescue

00:06:42.439 --> 00:06:46.989
teams availability and qualifications; security teams patrol coverage.

00:06:47.390 --> 00:06:52.070
Wildland contractors and industrial teams can check crew capability and access.

00:06:52.439 --> 00:06:56.739
Verify call state, status history and recipient receipt separately.
