WEBVTT

00:00:00.059 --> 00:00:03.950
Reports brings several questions together: who is currently staffed,

00:00:04.219 --> 00:00:07.739
what happened on calls, and which timestamps have been recorded.

00:00:08.229 --> 00:00:12.310
In our fictional Chicago Fire department, begin with the Reporting catalog.

00:00:12.810 --> 00:00:15.979
Find Staffing Report and use its View Report button.

00:00:16.479 --> 00:00:19.770
The report groups people by their latest recorded staffing level

00:00:19.809 --> 00:00:21.489
and provides a count and chart.

00:00:21.850 --> 00:00:26.889
Truck 81 has people in Available, Unavailable and On Shift categories.

00:00:27.219 --> 00:00:30.459
This is a staffing summary; it does not establish who

00:00:30.459 --> 00:00:32.209
physically attended an incident.

00:00:32.399 --> 00:00:36.839
Below the summary, read Name, Group, Roles, Staffing and

00:00:36.839 --> 00:00:38.570
Staffing Timestamp together.

00:00:39.059 --> 00:00:43.790
Next Change and Next Staffing describe a scheduled change when one exists.

00:00:44.090 --> 00:00:47.030
A blank cell supplies no future staffing commitment.

00:00:47.519 --> 00:00:50.910
Wallace Boden’s row also carries an explicit training note.

00:00:51.399 --> 00:00:55.910
Farther down, Matthew Casey’s row shows Truck 81, Officer and the

00:00:55.910 --> 00:00:59.949
training Community Response Navigator role, with On Shift staffing.

00:01:00.399 --> 00:01:04.459
The report reads existing personnel information; running it does not

00:01:04.509 --> 00:01:06.509
edit those memberships or statuses.

00:01:06.640 --> 00:01:11.949
On the Call Summary Report parameter page, check Report Start Time, Report End

00:01:11.949 --> 00:01:14.869
Time and Group before using Run Report.

00:01:15.299 --> 00:01:18.610
This example starts October twenty-fifth, twenty twenty-six,

00:01:18.669 --> 00:01:22.440
at midnight and ends October twenty-ninth at twenty-three thirty.

00:01:22.859 --> 00:01:24.320
All Groups is selected.

00:01:24.779 --> 00:01:27.129
These are department-local report boundaries.

00:01:27.500 --> 00:01:32.680
Read the complete values before running: a different start, end or group changes

00:01:32.680 --> 00:01:34.369
the population being summarized.

00:01:34.560 --> 00:01:37.220
The resulting header repeats the selected period.

00:01:37.649 --> 00:01:42.130
This captured run contains fifteen calls, with four open, nine unit

00:01:42.130 --> 00:01:44.860
responses and four personnel responses.

00:01:45.249 --> 00:01:49.639
Response totals accumulate across calls; they are not a count of unique

00:01:49.639 --> 00:01:51.459
department members or vehicles.

00:01:51.859 --> 00:01:54.100
The tables provide a useful cross-check.

00:01:54.459 --> 00:01:59.100
Investigation, Structure Fire, Rescue and Medical counts total fifteen.

00:01:59.449 --> 00:02:03.060
Call States separates eleven Closed from four Active.

00:02:03.449 --> 00:02:06.430
Read the table labels and denominators before comparing

00:02:06.430 --> 00:02:08.159
percentages with another report.

00:02:08.370 --> 00:02:12.010
Calls by Group explains why a call belongs to a reporting group.

00:02:12.459 --> 00:02:14.010
Each call counts once.

00:02:14.410 --> 00:02:19.219
A containing group geofence is used first; otherwise the report uses the group

00:02:19.219 --> 00:02:21.870
associated with most dispatched resources.

00:02:22.269 --> 00:02:24.179
Some calls can remain unassigned.

00:02:24.600 --> 00:02:27.570
This is different from simply listing the current viewer’s group.

00:02:27.990 --> 00:02:32.180
Here, Firehouse 51 has seven calls and Command has five.

00:02:32.660 --> 00:02:36.649
Use the explanation when investigating a surprising group total instead

00:02:36.649 --> 00:02:40.010
of changing memberships to make a report match expectations.

00:02:40.210 --> 00:02:43.360
The Calls table lets you inspect the rows behind the summary.

00:02:43.769 --> 00:02:50.250
Read Number, Name, Type, Group, Logged On, Closed On and the duration columns.

00:02:50.710 --> 00:02:53.800
The original three DEMO calls are still Open in this result,

00:02:54.050 --> 00:02:56.050
and their OnScene Time is N/A.

00:02:57.020 --> 00:03:01.010
The lower rows include the native Unit response and deselection exercise,

00:03:01.299 --> 00:03:05.910
number ending zero zero zero eight, also Open at this report’s generation.

00:03:07.020 --> 00:03:11.299
N/A is missing usable timing information, not a zero-minute arrival.

00:03:11.649 --> 00:03:14.240
Preserve that distinction when explaining averages.

00:03:14.470 --> 00:03:18.880
Call Unit Times answers a more specific question: which dispatch

00:03:18.880 --> 00:03:22.450
and status timestamps exist for each unit on each call?

00:03:22.960 --> 00:03:26.599
Its parameter form has start and end times and Run Report.

00:03:27.019 --> 00:03:30.219
Here the range starts October twenty-fourth at twenty-three

00:03:30.219 --> 00:03:33.900
thirty and ends October twenty-ninth at twenty-three thirty.

00:03:34.309 --> 00:03:37.510
That begins thirty minutes earlier than our first Call Summary.

00:03:37.940 --> 00:03:41.029
Keep those periods distinct when reconciling the results.

00:03:41.190 --> 00:03:46.080
The generated report has Dispatched, En Route, On Scene, Staging,

00:03:46.279 --> 00:03:48.409
Cleared and Linked By columns.

00:03:48.859 --> 00:03:53.510
The original DEMO rows say Dispatch only and leave later status times blank.

00:03:53.890 --> 00:03:57.019
A dispatch entry alone does not establish an arrival.

00:03:57.460 --> 00:03:59.929
Other exercise rows say Unit status.

00:04:00.370 --> 00:04:04.460
Read the recorded timestamps as they stand; some are incomplete or out

00:04:04.460 --> 00:04:08.749
of order, so review the underlying history before calculating a duration.

00:04:09.150 --> 00:04:13.180
Some calls explicitly report no unit dispatch or status data.

00:04:13.610 --> 00:04:18.050
The native exercise shows Ambulance 61 with dispatch and en-route times,

00:04:18.219 --> 00:04:20.029
while its later cells remain blank.

00:04:20.430 --> 00:04:24.820
These are software records, not independent physical-arrival verification.

00:04:25.149 --> 00:04:30.179
Use Download CSV on this report to obtain its unit rows for the same parameters.

00:04:30.580 --> 00:04:35.510
The downloaded file includes call and unit identifiers, timestamps and Linked By.

00:04:36.140 --> 00:04:39.750
This exercise export contains thirteen unit rows for twelve

00:04:39.750 --> 00:04:44.370
distinct calls: a call with two units creates two rows, while a call

00:04:44.370 --> 00:04:46.380
with no unit rows contributes none.

00:04:46.790 --> 00:04:50.449
The file uses DispatchOnly and Explicit codes where the screen

00:04:50.449 --> 00:04:52.939
says Dispatch only and Unit status.

00:04:53.300 --> 00:04:57.120
Keep blank times blank, and retain the report period with your file.

00:04:57.280 --> 00:05:01.700
For a separate comparison, the parameters now show the default period spanning

00:05:01.700 --> 00:05:05.559
late December twenty twenty-five to late December twenty twenty-six.

00:05:05.939 --> 00:05:08.099
This is not the earlier October week.

00:05:08.590 --> 00:05:11.599
Select Command in Group and use Run Report.

00:05:12.059 --> 00:05:15.859
The result explicitly says Command, including the groups beneath it.

00:05:16.249 --> 00:05:18.659
It contains five calls and none open.

00:05:19.030 --> 00:05:23.859
Its detail table shows those five exercise rows with Command dispatch attribution.

00:05:24.189 --> 00:05:27.960
A group filter narrows the report; it does not move resources,

00:05:28.040 --> 00:05:29.750
reassign calls or close them.

00:05:29.979 --> 00:05:33.289
The longer period also produces Yearly Statistics.

00:05:33.739 --> 00:05:37.470
An asterisk marks a partial period; the note explains that

00:05:37.470 --> 00:05:39.319
the report covers only part of it.

00:05:39.789 --> 00:05:42.869
Do not describe that row as a complete calendar year.

00:05:43.350 --> 00:05:47.809
Quarterly Statistics adds YTD, the cumulative call count within the

00:05:47.809 --> 00:05:50.090
report’s included periods for that year.

00:05:50.600 --> 00:05:54.510
Monthly Statistics uses the same Calls and YTD distinction.

00:05:54.989 --> 00:05:56.999
October contains five calls.

00:05:57.370 --> 00:06:01.729
November and December show zero calls while YTD remains five.

00:06:02.169 --> 00:06:05.870
These are results from available records in the chosen range, not

00:06:05.870 --> 00:06:07.620
forecasts of future activity.

00:06:07.810 --> 00:06:12.029
Return to parameters for the same default period and choose All Groups.

00:06:12.450 --> 00:06:16.260
Keep both time boundaries unchanged, then Run Report.

00:06:16.780 --> 00:06:21.260
This result contains sixteen calls: four open and twelve closed.

00:06:21.659 --> 00:06:25.569
That can be compared with the five-call Command result because the periods match.

00:06:25.899 --> 00:06:29.530
It should not be treated as a new duplicate merely because the earlier

00:06:29.530 --> 00:06:31.290
October week contained fifteen.

00:06:31.729 --> 00:06:35.620
Establish the window and scope before interpreting a change in totals.

00:06:35.810 --> 00:06:39.950
Chicago Fire can review station call distribution; community care

00:06:39.979 --> 00:06:43.700
and mental-health teams can review operational workload without putting

00:06:43.700 --> 00:06:45.699
client histories into report notes.

00:06:46.079 --> 00:06:49.119
Search-and-rescue teams can compare mission-period groups.

00:06:49.510 --> 00:06:53.440
Security teams can inspect recorded staffing before a patrol review,

00:06:53.690 --> 00:06:57.260
while wildland coordinators can compare seasonal reporting windows.

00:06:57.610 --> 00:07:02.200
Industrial teams can examine unit status chronology during a software exercise.

00:07:02.630 --> 00:07:07.380
In each setting, choose the question, fix the period and scope, inspect the

00:07:07.380 --> 00:07:11.969
detail rows, and explain missing data before sharing an authorized result.
