WEBVTT

00:00:00.000 --> 00:00:03.819
On Mapping, read the warehouse call label and open description

00:00:03.819 --> 00:00:05.539
before interpreting the marker.

00:00:05.940 --> 00:00:10.069
That popup identifies a fictional incident; it does not establish

00:00:10.069 --> 00:00:12.239
where a person or apparatus is now.

00:00:12.739 --> 00:00:16.469
This walkthrough reviews Core administration and recorded training data.

00:00:16.930 --> 00:00:20.590
Device permissions and field tracking need their own application checks.

00:00:20.959 --> 00:00:25.540
Keep that distinction visible when using location information for fire and EMS,

00:00:25.700 --> 00:00:28.360
community response, or industrial standby.

00:00:28.599 --> 00:00:33.869
In Department Settings, review Address and Default Map Center GPS Coordinates.

00:00:34.210 --> 00:00:37.830
The paired latitude and longitude inputs describe the starting map

00:00:37.830 --> 00:00:40.009
view, not a live vehicle fix.

00:00:40.360 --> 00:00:44.980
This example uses a fictional Chicago address and explicit decimal coordinates.

00:00:45.310 --> 00:00:50.840
Check Street, City, State/Province, Zip/Postal Code and Country

00:00:50.910 --> 00:00:52.580
before relying on the extent.

00:00:53.010 --> 00:00:57.299
Save and Cancel are visible; this demonstration reads existing values

00:00:57.330 --> 00:00:59.219
and leaves the department unchanged.

00:00:59.389 --> 00:01:04.579
On Edit Group, confirm Station Group and Group Name before reading Station Address.

00:01:05.059 --> 00:01:10.490
Firehouse 51 has a fictional Chicago address and Gps Coordinates; the lower

00:01:10.490 --> 00:01:13.250
what3words Address field is empty.

00:01:13.599 --> 00:01:17.599
These are alternative station-location inputs, not a live fix.

00:01:18.069 --> 00:01:21.079
Group Boundary is a separate response or service area.

00:01:21.450 --> 00:01:25.280
This demonstration reads the existing fields and preserves the station,

00:01:25.429 --> 00:01:27.870
boundary, apparatus assignment and crew.

00:01:28.109 --> 00:01:31.810
On Mapping, use Filter marker text to focus the display.

00:01:32.179 --> 00:01:35.699
The retained Truck 81 view leaves that named marker visible.

00:01:36.100 --> 00:01:40.800
Show calls, Show stations, Show units, Show personnel and Show

00:01:40.800 --> 00:01:43.439
POIs control displayed categories.

00:01:43.800 --> 00:01:48.379
In the comparison view, the text filter is empty and Show units is unchecked.

00:01:48.739 --> 00:01:52.559
A hidden category is not a released resource or deleted position.

00:01:52.940 --> 00:01:56.750
Inspect these controls before treating an expected resource as missing.

00:01:56.960 --> 00:02:01.720
From Mapping, Map Icon Legend explains type and priority conventions.

00:02:02.170 --> 00:02:06.039
Routine, Urgent and Emergency appear in separate columns.

00:02:06.499 --> 00:02:11.249
On Edit Call Type, the Structure Fire Preview shows a stored custom icon and

00:02:11.249 --> 00:02:13.800
says Showing the current custom icon.

00:02:14.240 --> 00:02:16.949
The warehouse popup supplies the incident description.

00:02:17.410 --> 00:02:19.349
These are visual identifiers.

00:02:19.570 --> 00:02:22.990
They do not establish a fresh position, response acceptance

00:02:23.140 --> 00:02:24.570
or notification receipt.

00:02:24.980 --> 00:02:28.109
Read the label and context rather than relying only on

00:02:28.109 --> 00:02:29.680
a flame or vehicle picture.

00:02:29.869 --> 00:02:32.830
On Mapping, the footer says Last update.

00:02:33.270 --> 00:02:36.749
It records when the client loaded or refreshed marker data, or

00:02:36.749 --> 00:02:40.749
handled a location update; it is not every resource’s fix time.

00:02:41.310 --> 00:02:45.690
In Units, Status and Timestamp belong to the latest unit status.

00:02:46.020 --> 00:02:48.569
That time is not a GPS measurement either.

00:02:48.940 --> 00:02:51.489
These screens show historical training states.

00:02:51.850 --> 00:02:55.190
Check the appropriate position source and age before treating a

00:02:55.190 --> 00:02:59.309
page refresh or status entry as evidence that an apparatus moved.

00:02:59.469 --> 00:03:04.070
In the recorded New Call position popup, Engine 51 explicitly says

00:03:04.070 --> 00:03:08.190
Station location and shows station coordinates beside the call location.

00:03:08.650 --> 00:03:11.169
That comparison uses a stored origin.

00:03:11.610 --> 00:03:15.589
A unit in quarters, or one without an available live position, can

00:03:15.589 --> 00:03:18.790
be measured from its station under the response-origin rules.

00:03:19.230 --> 00:03:21.450
Read the source before using the estimate.

00:03:21.849 --> 00:03:26.149
The displayed distance and time do not prove physical presence, arrival,

00:03:26.239 --> 00:03:28.040
or an active navigation route.

00:03:28.160 --> 00:03:30.719
On New Call, compare the Personnel rows.

00:03:31.060 --> 00:03:35.920
One historical training view shows Live GPS with a stale badge; the separately

00:03:35.920 --> 00:03:38.399
simulated newer view omits that badge.

00:03:38.859 --> 00:03:42.189
Live GPS names the application’s data-source category.

00:03:42.510 --> 00:03:46.039
No real device permission or physical movement was exercised.

00:03:46.410 --> 00:03:50.850
Status, Staffing, ETA and Position are separate columns.

00:03:51.180 --> 00:03:55.879
Treat No position as missing information, and review the source and configuration

00:03:55.879 --> 00:03:59.809
before using the first ranked candidate as an operational recommendation.

00:04:00.029 --> 00:04:04.659
In Mapping and BigBoard Settings, review personnel and unit controls separately.

00:04:05.159 --> 00:04:08.000
TTL In Minutes for Personnel Locations

00:04:08.000 --> 00:04:10.210
and TTL In Minutes for Unit Locations

00:04:10.449 --> 00:04:12.439
both show zero in these views.

00:04:12.859 --> 00:04:18.969
Zero disables ping expiry; the help text’s sixty-minute example is not a saved sixty.

00:04:19.379 --> 00:04:23.450
A location-bearing status can remain a fallback after a ping expires.

00:04:23.840 --> 00:04:28.100
The separate no-location-status checkboxes affect replacement behavior.

00:04:28.559 --> 00:04:31.620
Check the policy and position source before promising that

00:04:31.620 --> 00:04:32.930
a marker will disappear.

00:04:33.069 --> 00:04:37.809
In dispatch settings, Closest Unit Response Tuning has separate age controls.

00:04:38.210 --> 00:04:43.060
Maximum unit location age and Maximum personnel location age are in seconds;

00:04:43.369 --> 00:04:45.630
both recorded values are eighteen hundred.

00:04:46.019 --> 00:04:48.850
They differ from map TTL measured in minutes.

00:04:49.259 --> 00:04:51.640
Include stale locations is unchecked.

00:04:52.060 --> 00:04:56.609
Maximum response radius is zero, meaning no configured maximum radius.

00:04:57.050 --> 00:04:59.660
These controls influence candidate evaluation.

00:05:00.050 --> 00:05:03.849
They do not certify a fresh fix, prove service-area coverage,

00:05:04.109 --> 00:05:07.100
or change a resource position because the map refreshed.

00:05:07.319 --> 00:05:12.200
In the same Closest Unit Response Tuning section, Order by driving ETA is

00:05:12.269 --> 00:05:15.679
unchecked and ETA shortlist size is five.

00:05:16.090 --> 00:05:21.059
Turnout is one hundred twenty seconds in quarters, zero mobile and zero personnel.

00:05:21.540 --> 00:05:25.989
The matching Engine 51 station popup shows a two-minute estimate including

00:05:25.989 --> 00:05:27.669
one hundred twenty seconds of turnout.

00:05:28.179 --> 00:05:31.460
Response combines applicable turnout with estimated travel.

00:05:31.849 --> 00:05:33.400
Routed drive time is separate.

00:05:33.849 --> 00:05:37.560
This is no tested drive, confirmed dispatch receipt, physical

00:05:37.560 --> 00:05:39.419
movement or arrival commitment.

00:05:39.670 --> 00:05:42.000
From Mapping, Manage POIs

00:05:42.000 --> 00:05:44.350
opens the empty POI-type list.

00:05:44.739 --> 00:05:49.770
In Weather Alerts, Monitoring Zones offers Center Location, Radius in miles

00:05:49.889 --> 00:05:52.520
and Save Zone; no zone is saved here.

00:05:52.919 --> 00:05:57.030
Hospitals, layers, floor plans and patrol routes still require

00:05:57.030 --> 00:05:58.880
their own saved-workflow checks.

00:05:59.290 --> 00:06:03.200
For search and rescue, security, wildland or community teams,

00:06:03.460 --> 00:06:07.050
apply the same source-and-age checks before operational use.

00:06:07.390 --> 00:06:10.860
Keep missing reference data on the follow-up list until its placement

00:06:10.890 --> 00:06:12.690
and limits are actually reviewed.
