WEBVTT

00:00:00.029 --> 00:00:03.450
Open the department menu and choose Stations and Groups.

00:00:03.829 --> 00:00:07.659
The table separates each group’s type, parent, and member count.

00:00:08.020 --> 00:00:11.510
Our fictional Chicago Fire department already has a station and

00:00:11.510 --> 00:00:13.119
organizational groups beneath it.

00:00:13.550 --> 00:00:16.469
We will add an empty coordination parent and a separate

00:00:16.469 --> 00:00:18.020
station beneath that parent.

00:00:18.399 --> 00:00:22.799
Read the existing rows first so the new exercise is easy to identify and

00:00:22.799 --> 00:00:24.959
the original memberships remain intact.

00:00:25.090 --> 00:00:27.000
Choose Add New Group and

00:00:27.000 --> 00:00:28.780
keep Organizational Group selected.

00:00:29.270 --> 00:00:32.889
Enter Training Only, Community Coordination, followed

00:00:32.889 --> 00:00:34.029
by the exercise date.

00:00:34.390 --> 00:00:37.619
Parent Group remains None, making this a top-level group.

00:00:38.090 --> 00:00:40.550
Group Admins and Group Users stay empty.

00:00:40.939 --> 00:00:44.730
These fields describe different membership responsibilities; choosing an

00:00:44.730 --> 00:00:46.859
administrator is a permission decision.

00:00:47.269 --> 00:00:50.999
We are preparing a structure, so we do not move a person from an existing

00:00:50.999 --> 00:00:53.040
group or assign an administrator.

00:00:53.229 --> 00:00:54.520
Use Save Group.

00:00:55.009 --> 00:00:59.930
The fresh Edit Group readback retains its full name and Parent None, and displays

00:00:59.930 --> 00:01:01.960
the Organizational type read-only.

00:01:02.389 --> 00:01:04.540
Both membership selectors remain empty.

00:01:04.929 --> 00:01:08.819
The page explains that a person can belong to only one group at a time.

00:01:09.210 --> 00:01:13.620
When maintaining a populated group, let its existing selections load before

00:01:13.620 --> 00:01:18.029
saving: the form submits the complete member and administrator selection.

00:01:18.240 --> 00:01:20.000
Create another group and

00:01:20.000 --> 00:01:21.029
select Station Group.

00:01:21.470 --> 00:01:26.410
Name it Training Only, Community Base, with the exercise date, and choose the

00:01:26.410 --> 00:01:28.510
new coordination group as its parent.

00:01:28.979 --> 00:01:31.760
A station requires a physical reference location.

00:01:32.189 --> 00:01:37.600
The form offers address fields, a coordinate pair, or a what3words address.

00:01:37.990 --> 00:01:41.449
We will use an explicitly illustrative Chicago coordinate pair.

00:01:41.910 --> 00:01:46.080
The parent describes the organizational relationship; it does not replace

00:01:46.080 --> 00:01:47.680
the station’s own location.

00:01:47.869 --> 00:01:53.289
In Gps Coordinates, enter latitude forty-one point eight five and longitude

00:01:53.320 --> 00:01:55.570
minus eighty-seven point six five.

00:01:55.970 --> 00:01:57.640
Enter both values together.

00:01:58.199 --> 00:02:02.619
The street fields are unused and what3words stays blank.

00:02:03.029 --> 00:02:06.909
This is a typed station reference, not a device-location reading or

00:02:06.909 --> 00:02:08.649
proof that anyone arrived there.

00:02:09.040 --> 00:02:12.219
Keep the member and administrator selectors empty and leave

00:02:12.219 --> 00:02:13.530
printing unconfigured.

00:02:13.989 --> 00:02:17.329
Use Save Group once after checking the prepared values.

00:02:17.559 --> 00:02:21.150
The returned catalog shows both new groups with zero members.

00:02:21.530 --> 00:02:24.750
The organizational root has no parent, while the station

00:02:24.750 --> 00:02:26.499
names that root as its parent.

00:02:26.910 --> 00:02:29.000
Use the station’s Edit control to check

00:02:29.000 --> 00:02:30.929
its full name and relationship again.

00:02:31.389 --> 00:02:36.050
Scroll to verify the saved coordinate pair, blank what3words field, and

00:02:36.050 --> 00:02:38.120
clear Print Calls to Printer option.

00:02:38.550 --> 00:02:42.159
This readback checks the particular fields we stored without changing the

00:02:42.159 --> 00:02:44.300
station type or configuring printing.

00:02:44.509 --> 00:02:46.890
Open Units and choose New Unit.

00:02:47.360 --> 00:02:52.280
The form separates Name, Type, Station, and the unit’s role positions.

00:02:52.679 --> 00:02:57.179
No Station is available, but our exercise will use the station we just created.

00:02:57.599 --> 00:03:02.490
A role position defines a seat; it does not select the person occupying that seat.

00:03:02.889 --> 00:03:06.779
Before completing this unit, use the type link to create a distinct

00:03:06.779 --> 00:03:10.189
training vehicle type that will be recognizable in the unit list.

00:03:10.320 --> 00:03:12.000
From the Unit Types section,

00:03:12.000 --> 00:03:13.760
choose New Unit Type.

00:03:14.250 --> 00:03:17.479
Enter Training Only, Community Response Vehicle.

00:03:17.919 --> 00:03:21.790
Set Class to Support; the help explains that class is used for

00:03:21.790 --> 00:03:25.870
reports, defaults, and integrations, separately from the display name.

00:03:26.299 --> 00:03:30.440
Keep Actions on Standard Actions and choose Van for Map Icon.

00:03:30.799 --> 00:03:33.500
The optional custom-icon file remains empty.

00:03:33.920 --> 00:03:37.309
These choices define the new type without changing an existing

00:03:37.309 --> 00:03:39.360
type or a department status set.

00:03:39.490 --> 00:03:43.259
The preview now shows the built-in green Van symbol on light and

00:03:43.259 --> 00:03:45.209
dark backgrounds and in a list.

00:03:45.610 --> 00:03:47.490
No custom image has been uploaded.

00:03:47.879 --> 00:03:49.000
Save, then

00:03:49.000 --> 00:03:50.790
read the new type row in the catalog.

00:03:51.219 --> 00:03:54.750
It shows the full name, Default Unit Actions, and Van.

00:03:55.210 --> 00:03:57.000
Open Edit to verify

00:03:57.000 --> 00:03:59.640
Support, Standard Actions, and the Van choice again.

00:03:59.999 --> 00:04:03.849
This confirms the type configuration; it is not a demonstration of

00:04:03.849 --> 00:04:05.630
a vehicle’s live map location.

00:04:05.869 --> 00:04:07.000
Return to New

00:04:07.000 --> 00:04:10.079
Unit and name the vehicle Training Only, Community

00:04:10.079 --> 00:04:11.780
Van, with the exercise date.

00:04:12.169 --> 00:04:14.090
Select the new type and station.

00:04:14.489 --> 00:04:16.590
Add two positions with different names.

00:04:16.940 --> 00:04:21.350
Coordination Seat requires the existing Community Response Navigator personnel

00:04:21.350 --> 00:04:23.700
role, and its Required box is checked.

00:04:24.120 --> 00:04:27.260
Optional Support Seat has no personnel-role restriction

00:04:27.479 --> 00:04:29.229
and its Required box is clear.

00:04:29.639 --> 00:04:31.590
These are the unit’s seat definitions.

00:04:31.919 --> 00:04:34.620
No person is assigned by creating either row.

00:04:34.850 --> 00:04:37.960
Browse Templates opens reusable starting layouts.

00:04:38.349 --> 00:04:42.419
Here the Security Companies cards show examples such as Security

00:04:42.419 --> 00:04:44.550
Patrol and Alarm Response Team.

00:04:45.050 --> 00:04:47.730
Use These Roles would add a template’s positions to the

00:04:47.730 --> 00:04:49.749
form for review before saving.

00:04:50.190 --> 00:04:52.769
For this exercise, choose Close instead.

00:04:53.259 --> 00:04:56.910
The settled unit form still contains our two prepared positions.

00:04:57.340 --> 00:05:00.660
Inspect a template’s suggested roles deliberately rather than

00:05:00.660 --> 00:05:04.429
assuming its names or suggested qualifications match your department.

00:05:04.669 --> 00:05:06.519
Use Save on the prepared unit.

00:05:07.020 --> 00:05:10.339
The returned list shows its full name and training vehicle type.

00:05:10.779 --> 00:05:12.000
Open Edit and check

00:05:12.000 --> 00:05:14.929
that both positions and their Required choices remain.

00:05:15.350 --> 00:05:17.000
Open the Station dropdown to

00:05:17.000 --> 00:05:19.079
read the complete selected Community Base

00:05:19.079 --> 00:05:21.240
name; the closed field truncates it.

00:05:21.629 --> 00:05:24.849
We are verifying the stored definition without pressing Update.

00:05:25.199 --> 00:05:29.459
The list’s Available display alone does not establish crew readiness or

00:05:29.459 --> 00:05:31.580
prove a newly recorded status event.

00:05:31.719 --> 00:05:35.439
Open Unit Staffing to distinguish positions from assigned people.

00:05:35.989 --> 00:05:39.540
Engine fifty-one retains Herrmann in its one configured seat.

00:05:39.919 --> 00:05:43.950
The new van is Not Staffed, and both positions are Not Occupied.

00:05:44.490 --> 00:05:48.050
Opening a person selector does not itself prove that the listed

00:05:48.050 --> 00:05:49.780
people hold the required role.

00:05:50.180 --> 00:05:52.169
We close it without selecting anyone.

00:05:52.759 --> 00:05:56.589
Save on this page replaces staffing selections across the department,

00:05:56.880 --> 00:06:00.290
so we leave it untouched and preserve every existing assignment.

00:06:00.400 --> 00:06:02.489
Finish with the group tree on Units.

00:06:02.989 --> 00:06:06.010
Expand and select the Community Coordination parent.

00:06:06.400 --> 00:06:10.250
Its view includes the vehicle assigned to the child Community Base station.

00:06:10.670 --> 00:06:13.790
Select that station directly and the same unit appears.

00:06:14.210 --> 00:06:17.260
This demonstrates the saved relationship from organizational

00:06:17.260 --> 00:06:19.410
parent to station to unit.

00:06:19.820 --> 00:06:23.830
These tree choices filter the view; they do not move a unit, assign a

00:06:23.830 --> 00:06:26.020
crew member, or change its status.

00:06:26.210 --> 00:06:30.960
Chicago Fire can separate a coordination structure from a station and its vehicles.

00:06:31.359 --> 00:06:35.220
Community care and mental health teams can organize operational teams

00:06:35.220 --> 00:06:37.330
and bases without patient detail.

00:06:37.739 --> 00:06:41.489
Search and rescue can distinguish coordination groups, staging bases,

00:06:41.489 --> 00:06:46.399
and resources; security teams can structure patrol resources; wildland

00:06:46.399 --> 00:06:50.959
teams can organize seasonal bases; and industrial response teams can separate

00:06:50.959 --> 00:06:53.200
facility groups from response vehicles.

00:06:53.610 --> 00:06:57.559
In each setting, verify saved relationships and seat requirements,

00:06:57.889 --> 00:07:01.799
then manage actual staffing as a separate, deliberate operation.
