Innovating Incident Command with Tablet Command Episode 10

WEBVTT
Kind: captions
Language: en
00:00:00.719 --> 00:00:03.110
You're listening to Catching Wildfire, a
00:00:03.120 --> 00:00:05.190
podcast by the Public Safety Broadband
00:00:05.200 --> 00:00:07.829
Technology Association. It's always my
00:00:07.839 --> 00:00:09.350
pleasure to introduce the National
00:00:09.360 --> 00:00:12.470
Treasurer, Chief Kim Zagaras, who as
00:00:12.480 --> 00:00:14.709
most folks knew that he was the top
00:00:14.719 --> 00:00:17.189
official at the or the office of
00:00:17.199 --> 00:00:19.429
California emergency services for 18
00:00:19.439 --> 00:00:21.910
years and truly a legend in the wildfire
00:00:21.920 --> 00:00:24.710
space. He now serves as a senior uh
00:00:24.720 --> 00:00:26.630
wildfire policy adviser for the Western
00:00:26.640 --> 00:00:29.269
Fire Chief. So, Chief Z, welcome. My
00:00:29.279 --> 00:00:31.669
name is Jeff Johnson and I am uh the
00:00:31.679 --> 00:00:33.350
retired executive director for the
00:00:33.360 --> 00:00:35.670
Western Fire Chiefs and retired out of
00:00:35.680 --> 00:00:37.510
Twallet Valley Fire and Rescue and it's
00:00:37.520 --> 00:00:40.069
my honor today to introduce our guest
00:00:40.079 --> 00:00:42.549
Will Pigeon and Will is the co-founder
00:00:42.559 --> 00:00:45.830
and CEO of Tablet Command. So Will,
00:00:45.840 --> 00:00:48.069
welcome. Uh we're so excited to have you
00:00:48.079 --> 00:00:50.869
here today and given how much Chief Z
00:00:50.879 --> 00:00:54.630
and I put into the uh LTE and technology
00:00:54.640 --> 00:00:57.270
space on behalf of FirstNet for public
00:00:57.280 --> 00:00:58.950
safety
00:00:58.960 --> 00:01:01.189
folks like you that are evolving the
00:01:01.199 --> 00:01:03.349
tools that our people use in the field.
00:01:03.359 --> 00:01:05.590
You're critical of the ecosystem. So
00:01:05.600 --> 00:01:07.990
welcome Will and why don't you start off
00:01:08.000 --> 00:01:09.670
telling us a little about yourself in
00:01:09.680 --> 00:01:10.710
tablet command.
00:01:10.720 --> 00:01:12.469
>> Awesome. Uh Chiefs, thank you so much
00:01:12.479 --> 00:01:14.469
for having us having me on Catching
00:01:14.479 --> 00:01:16.870
Wildfire. super happy to be here. Um,
00:01:16.880 --> 00:01:18.550
just a little bit about myself. I grew
00:01:18.560 --> 00:01:20.390
up in the Bay Area, went down to San
00:01:20.400 --> 00:01:22.310
Diego State, started uh, college there
00:01:22.320 --> 00:01:24.469
and had an interest in the fire service.
00:01:24.479 --> 00:01:26.310
Uh, so I had a parallel path while I was
00:01:26.320 --> 00:01:28.550
at college. Um, and while I was at
00:01:28.560 --> 00:01:30.230
college, I was a full-time firefighter.
00:01:30.240 --> 00:01:32.630
I was able to, the chief at the time let
00:01:32.640 --> 00:01:35.749
me go to, uh, San Diego State, downstaff
00:01:35.759 --> 00:01:38.149
the engine while I was actually, uh, on
00:01:38.159 --> 00:01:39.510
duty. They would just down staff the
00:01:39.520 --> 00:01:40.950
engine. So, that was that was awesome
00:01:40.960 --> 00:01:43.830
opportunity down in San Diego. fire uh
00:01:43.840 --> 00:01:46.389
firefighter, firefighter medic, uh fire
00:01:46.399 --> 00:01:48.389
dispatcher, flight rescue medic, and
00:01:48.399 --> 00:01:51.109
then in 2005, I got hired by Contraosta
00:01:51.119 --> 00:01:54.230
County Fire um to come back home, if you
00:01:54.240 --> 00:01:56.550
will, and work uh for an agency where I
00:01:56.560 --> 00:01:59.910
grew up in the county. And in 2005, um
00:01:59.920 --> 00:02:01.350
was in the academy, came out of the
00:02:01.360 --> 00:02:04.230
academy, and in 2007, Contraost County
00:02:04.240 --> 00:02:05.670
Fire for the first time in his history,
00:02:05.680 --> 00:02:07.910
had two line of duty deaths. Uh Matt and
00:02:07.920 --> 00:02:09.430
Scott both lost their lives tried to
00:02:09.440 --> 00:02:11.589
rescue an elderly couple in a thousand
00:02:11.599 --> 00:02:15.430
square foot home. Um so uh huge huge
00:02:15.440 --> 00:02:19.350
tragedy and around the time uh Andy my
00:02:19.360 --> 00:02:21.110
co-founder Andy Boto who came from
00:02:21.120 --> 00:02:24.070
Tacoma fire uh but was in the academy in
00:02:24.080 --> 00:02:25.670
Contraosta
00:02:25.680 --> 00:02:27.430
uh when we suffered that line of duty
00:02:27.440 --> 00:02:29.270
death uh he came out of the academy and
00:02:29.280 --> 00:02:31.030
of course the department any near miss
00:02:31.040 --> 00:02:32.630
or any line of duty death they're always
00:02:32.640 --> 00:02:34.470
interested in trying to figure out how
00:02:34.480 --> 00:02:37.910
to um avoid a tragedy like that in the
00:02:37.920 --> 00:02:39.830
future and improve the outcome. So I
00:02:39.840 --> 00:02:41.750
think there were 141 or 142
00:02:41.760 --> 00:02:43.830
recommendations that came out of that
00:02:43.840 --> 00:02:45.990
report and that finding. And so Andy
00:02:46.000 --> 00:02:47.350
after he came out of the academy was
00:02:47.360 --> 00:02:49.589
giving a class to uh the operations
00:02:49.599 --> 00:02:51.030
chief. And I'm getting in a little bit
00:02:51.040 --> 00:02:53.830
into tablet commands founding uh origin
00:02:53.840 --> 00:02:56.470
story but he was uh teaching the class
00:02:56.480 --> 00:02:58.630
to the operations chief what they did
00:02:58.640 --> 00:03:00.390
for accountability up in Tacoma fire. At
00:03:00.400 --> 00:03:01.910
the time the state of state-of-the-art
00:03:01.920 --> 00:03:03.350
solution and maybe they still do this
00:03:03.360 --> 00:03:05.990
today is the clip-on keychains. You clip
00:03:06.000 --> 00:03:08.390
two key chains on to your SCBA air pack,
00:03:08.400 --> 00:03:09.910
which I think we're all familiar with,
00:03:09.920 --> 00:03:12.550
and one gets commit clipped onto the
00:03:12.560 --> 00:03:14.309
command post and one gets click clicked
00:03:14.319 --> 00:03:16.710
into IDLH, whoever was maintaining that
00:03:16.720 --> 00:03:18.390
accountability. So, it got Andy thinking
00:03:18.400 --> 00:03:20.390
about incident command and
00:03:20.400 --> 00:03:22.869
accountability. And in parallel, the
00:03:22.879 --> 00:03:25.750
iPhone came out in 2007 and the iPad
00:03:25.760 --> 00:03:29.270
came out, I think, in 2009 or 2010. So
00:03:29.280 --> 00:03:31.110
that kind of marks the that draws a line
00:03:31.120 --> 00:03:32.550
in the sand where I I feel like
00:03:32.560 --> 00:03:34.789
technology truly was becoming mobile at
00:03:34.799 --> 00:03:36.550
the time for the fire service which is a
00:03:36.560 --> 00:03:39.350
mobile workforce. So Andy was playing
00:03:39.360 --> 00:03:41.509
Words with Friends uh with somebody in
00:03:41.519 --> 00:03:44.710
Texas off duty and uh he was dragging a
00:03:44.720 --> 00:03:46.470
letter out to the board. Imagine the
00:03:46.480 --> 00:03:48.390
letter E dragging it out and it has
00:03:48.400 --> 00:03:49.990
points associated with it and that could
00:03:50.000 --> 00:03:51.830
be the number of personnel. So, he had
00:03:51.840 --> 00:03:54.309
this he had this epiphany that why can't
00:03:54.319 --> 00:03:55.750
uh we drag, you know, an incident
00:03:55.760 --> 00:03:58.309
commander use a tool like an iPad to
00:03:58.319 --> 00:04:00.149
drag letters out to the board or those
00:04:00.159 --> 00:04:01.350
engine companies out to the board to
00:04:01.360 --> 00:04:02.949
give them assignments for a fire attack.
00:04:02.959 --> 00:04:04.229
And he was playing with in real time
00:04:04.239 --> 00:04:06.789
with somebody in Texas. Andy and I were
00:04:06.799 --> 00:04:08.470
working together on another project in
00:04:08.480 --> 00:04:09.589
the department. He knew I had a
00:04:09.599 --> 00:04:10.949
background in technology and that's when
00:04:10.959 --> 00:04:12.949
we founded Tablet Command. So,
00:04:12.959 --> 00:04:13.589
>> incredible
00:04:13.599 --> 00:04:15.670
>> in terms of the history. Yeah, thank
00:04:15.680 --> 00:04:18.069
you. Thank you very much. We started as
00:04:18.079 --> 00:04:20.469
a standalone application uh launched on
00:04:20.479 --> 00:04:23.510
the app store in early 2013 and it was
00:04:23.520 --> 00:04:25.189
really just an application to help
00:04:25.199 --> 00:04:27.350
incident commanders keep track of the
00:04:27.360 --> 00:04:28.870
resources that are assigned to the
00:04:28.880 --> 00:04:30.710
incident. When you first started you
00:04:30.720 --> 00:04:32.950
have to punch in the resources that you
00:04:32.960 --> 00:04:34.550
were assigned and whatever the alarm
00:04:34.560 --> 00:04:37.430
level was. Um and then we quickly got
00:04:37.440 --> 00:04:39.110
feedback from fire international
00:04:39.120 --> 00:04:40.629
association of fire chiefs. I think it
00:04:40.639 --> 00:04:43.030
was a connections event or a technology
00:04:43.040 --> 00:04:44.629
event at a fire chief's conference where
00:04:44.639 --> 00:04:46.710
they said you have to dial this in and
00:04:46.720 --> 00:04:48.629
integrate this with uh CAD,
00:04:48.639 --> 00:04:51.590
>> right? So we did that in 2014 and since
00:04:51.600 --> 00:04:53.909
then um you know some of the milestones
00:04:53.919 --> 00:04:55.670
that table commands had in terms of the
00:04:55.680 --> 00:04:58.469
feature and kind of revolutionary I
00:04:58.479 --> 00:04:59.990
think we've revolutionized the industry
00:05:00.000 --> 00:05:01.670
in terms of situation awareness and
00:05:01.680 --> 00:05:04.310
accountability and incident command is
00:05:04.320 --> 00:05:06.550
you know just to give you an example of
00:05:06.560 --> 00:05:08.870
the time savings one value proposition
00:05:08.880 --> 00:05:11.189
that tablet command has for an incident
00:05:11.199 --> 00:05:13.270
commander is if an incident commander is
00:05:13.280 --> 00:05:15.110
on the scene of a large incident second
00:05:15.120 --> 00:05:18.310
or third third alarm if they call for an
00:05:18.320 --> 00:05:19.830
inventory to the communication centers
00:05:19.840 --> 00:05:22.390
for a third alarm. That process alone
00:05:22.400 --> 00:05:25.029
takes 60 seconds on the radio versus
00:05:25.039 --> 00:05:26.790
tattlele command. As soon as the
00:05:26.800 --> 00:05:29.350
resources are assigned, they are
00:05:29.360 --> 00:05:31.189
populated in the application with just a
00:05:31.199 --> 00:05:32.550
quick drag and drop. So your
00:05:32.560 --> 00:05:35.029
whiteboard's automatically populated.
00:05:35.039 --> 00:05:36.790
And over time, we've had customers
00:05:36.800 --> 00:05:39.670
request uh integrations including MDT.
00:05:39.680 --> 00:05:42.629
So we do MDT replacement where we can
00:05:42.639 --> 00:05:45.110
now status back into the CAD and write
00:05:45.120 --> 00:05:47.510
comments back into the CAD. And then
00:05:47.520 --> 00:05:49.670
also just bringing everything including
00:05:49.680 --> 00:05:52.469
customized maps, uh staffing solutions,
00:05:52.479 --> 00:05:53.990
you name it. We try to bring everything
00:05:54.000 --> 00:05:56.310
into that single pane of glass for for
00:05:56.320 --> 00:05:59.270
responders in the field. Um some couple
00:05:59.280 --> 00:06:01.510
two two things I want to mention is the
00:06:01.520 --> 00:06:03.590
history of the tablet command. 2018 we
00:06:03.600 --> 00:06:06.390
launched shared AL
00:06:06.400 --> 00:06:08.790
which is allows you know of course when
00:06:08.800 --> 00:06:10.070
you're in a communication center you can
00:06:10.080 --> 00:06:12.150
see that your resources
00:06:12.160 --> 00:06:14.070
um and where the vehicle locations are
00:06:14.080 --> 00:06:16.950
in your CAD but you know recognizing
00:06:16.960 --> 00:06:19.590
that on these large campaign fires these
00:06:19.600 --> 00:06:21.430
wildfires or these large incidents or
00:06:21.440 --> 00:06:23.350
even just automatic aid incidents you're
00:06:23.360 --> 00:06:25.110
not able to see neighboring
00:06:25.120 --> 00:06:26.950
communication centers vehicle locations
00:06:26.960 --> 00:06:30.150
well in 2018 command changed that so if
00:06:30.160 --> 00:06:31.830
you're operating in tablet command
00:06:31.840 --> 00:06:34.790
you're able to see all resources of all
00:06:34.800 --> 00:06:36.550
tablet command customers whether you're
00:06:36.560 --> 00:06:38.390
in California, whether you're in Oregon,
00:06:38.400 --> 00:06:40.230
wherever you are in the country, you're
00:06:40.240 --> 00:06:42.309
able to see those resources. And then
00:06:42.319 --> 00:06:44.950
just more recently in u uh just about a
00:06:44.960 --> 00:06:46.710
year ago, we launched incident sharing.
00:06:46.720 --> 00:06:49.270
So now crews are able to see a mutual
00:06:49.280 --> 00:06:52.150
aid incident, the exact same data that
00:06:52.160 --> 00:06:54.150
the host agency is seeing in terms of
00:06:54.160 --> 00:06:57.430
the incident updates coming from uh
00:06:57.440 --> 00:06:58.870
coming from the CAD. So, for example,
00:06:58.880 --> 00:07:01.270
the Palisades fire, the Eaton fire, LA
00:07:01.280 --> 00:07:03.830
fires, uh, units were coming in from all
00:07:03.840 --> 00:07:05.589
over the state and they would see the
00:07:05.599 --> 00:07:07.990
exact same data that LA County would see
00:07:08.000 --> 00:07:09.670
in terms of their CAD data. So, it's
00:07:09.680 --> 00:07:10.629
really a game changer.
00:07:10.639 --> 00:07:12.550
>> That's incredible. And that's must be
00:07:12.560 --> 00:07:15.110
something that the user uh can turn off,
00:07:15.120 --> 00:07:16.150
right? If they didn't want to share
00:07:16.160 --> 00:07:18.150
their location, they could turn it off.
00:07:18.160 --> 00:07:19.830
>> Yeah, absolutely. Yeah, department could
00:07:19.840 --> 00:07:21.270
turn that off if they wanted to choose
00:07:21.280 --> 00:07:23.110
not to share with other agencies or even
00:07:23.120 --> 00:07:25.510
a user could share and turn off their
00:07:25.520 --> 00:07:27.589
location as well. Absolutely, too. I
00:07:27.599 --> 00:07:30.150
think uh you know we were chatting a
00:07:30.160 --> 00:07:32.550
little bit but uh I think the ability to
00:07:32.560 --> 00:07:35.749
share I think is u you know a great
00:07:35.759 --> 00:07:38.629
example is is that during the LA fires
00:07:38.639 --> 00:07:41.589
in 2025 you know resources out of Oregon
00:07:41.599 --> 00:07:44.309
were rolling uh down to Southern
00:07:44.319 --> 00:07:46.550
California where we're able to see the
00:07:46.560 --> 00:07:48.469
information as they were coming down and
00:07:48.479 --> 00:07:50.469
then you know the incident was actually
00:07:50.479 --> 00:07:52.469
able to see them and be able to sign
00:07:52.479 --> 00:07:54.309
them. So I think, you know, there's some
00:07:54.319 --> 00:07:55.909
things that are, you know, really
00:07:55.919 --> 00:07:58.070
remarkably moving where we're headed
00:07:58.080 --> 00:08:02.070
today. So h how does a typical customer
00:08:02.080 --> 00:08:04.230
use tablet command in today's day and
00:08:04.240 --> 00:08:06.469
age and uh as you're evolving?
00:08:06.479 --> 00:08:07.830
>> That's great. It's a great question,
00:08:07.840 --> 00:08:10.070
Chief. Yeah. So uh depends on who the
00:08:10.080 --> 00:08:11.510
user is, right? So if it's a
00:08:11.520 --> 00:08:13.430
firefighter, they're going to have uh TC
00:08:13.440 --> 00:08:15.670
Mobile in their pocket. So, if they're
00:08:15.680 --> 00:08:17.189
inside a fire department, they'll be on
00:08:17.199 --> 00:08:18.710
duty or off duty and they'll have TC
00:08:18.720 --> 00:08:20.869
Mobile and the user can subscribe to
00:08:20.879 --> 00:08:22.469
what kind of notifications they want to
00:08:22.479 --> 00:08:24.710
get. For example, if I'm a firefighter
00:08:24.720 --> 00:08:26.629
or captain, I may want to get structure
00:08:26.639 --> 00:08:29.110
fire or wildfire notifications anytime
00:08:29.120 --> 00:08:31.270
there's an incident that's in my CAD.
00:08:31.280 --> 00:08:32.469
And we're we're sending out
00:08:32.479 --> 00:08:34.310
notifications to firefighters sometimes
00:08:34.320 --> 00:08:37.350
30 to 60 or 90 seconds faster than
00:08:37.360 --> 00:08:39.589
traditional station alerting. The reason
00:08:39.599 --> 00:08:40.870
you may be wondering how is that
00:08:40.880 --> 00:08:42.469
possible is we're watching for the
00:08:42.479 --> 00:08:44.389
pending incident. So as soon as the
00:08:44.399 --> 00:08:46.070
address has been verified by the CAD and
00:08:46.080 --> 00:08:47.670
the call type has been defined by the
00:08:47.680 --> 00:08:49.269
dispatcher, we're sending out
00:08:49.279 --> 00:08:51.110
notifications. So before units are even
00:08:51.120 --> 00:08:52.630
assigned by a dispatcher in the
00:08:52.640 --> 00:08:53.829
communication center, we're sending
00:08:53.839 --> 00:08:57.350
those out. Um we replace uh users in the
00:08:57.360 --> 00:08:59.590
field are using it as an MDT. So while
00:08:59.600 --> 00:09:01.110
they're responding, engine company
00:09:01.120 --> 00:09:02.470
captains or battalion chiefs are
00:09:02.480 --> 00:09:04.070
utilizing our application to route to
00:09:04.080 --> 00:09:06.470
calls, see the customized maps, see the
00:09:06.480 --> 00:09:07.990
vehicle locations, and see all the
00:09:08.000 --> 00:09:10.150
updates coming from CAD. And then once
00:09:10.160 --> 00:09:11.910
the incident commander gets there or the
00:09:11.920 --> 00:09:13.990
battalion chief takes command, they're
00:09:14.000 --> 00:09:15.990
using our tool to manage and drag and
00:09:16.000 --> 00:09:17.590
drop those resources, have their
00:09:17.600 --> 00:09:19.590
checklists, be able to see what's going
00:09:19.600 --> 00:09:22.150
on in the incident, who's assigned with
00:09:22.160 --> 00:09:24.389
uh who's on the roster of what engine.
00:09:24.399 --> 00:09:25.910
We bring all that in together so that
00:09:25.920 --> 00:09:27.350
the incident commander and all the crews
00:09:27.360 --> 00:09:29.030
can see that and that information is
00:09:29.040 --> 00:09:31.910
shared with everybody in real time so
00:09:31.920 --> 00:09:33.509
everyone's on the same page. So, it's no
00:09:33.519 --> 00:09:34.870
longer the incident command board is
00:09:34.880 --> 00:09:36.949
just at the back of the command post or
00:09:36.959 --> 00:09:39.110
in the on the legal pad inside the
00:09:39.120 --> 00:09:41.110
chief's car. It's now available to
00:09:41.120 --> 00:09:44.870
everyone in real time. So,
00:09:44.880 --> 00:09:47.829
>> I you know, I know I I've chatted over
00:09:47.839 --> 00:09:49.670
time, but uh I think one of your
00:09:49.680 --> 00:09:51.750
challenging points has just been uh
00:09:51.760 --> 00:09:55.269
working to get all those AVL feeds uh uh
00:09:55.279 --> 00:09:57.829
in integrated into your proc into
00:09:57.839 --> 00:09:59.350
tablet. Yeah, it's definitely definitely
00:09:59.360 --> 00:10:01.110
a challenge and that's one of the strong
00:10:01.120 --> 00:10:02.550
points that we've done in terms of
00:10:02.560 --> 00:10:04.389
integrations and you know maybe I'll
00:10:04.399 --> 00:10:05.829
mention integrations a little bit later
00:10:05.839 --> 00:10:08.949
but um in terms of vehicle location data
00:10:08.959 --> 00:10:10.550
we started with CAD data we've got
00:10:10.560 --> 00:10:12.630
tablet command vehicle location data
00:10:12.640 --> 00:10:16.069
we've got uh solutions like Sam Sera
00:10:16.079 --> 00:10:18.710
Fleet Complete uh we have ADSB we're
00:10:18.720 --> 00:10:20.389
trying to bring all that location data
00:10:20.399 --> 00:10:22.470
because there's so many different
00:10:22.480 --> 00:10:24.069
sources for that because customers
00:10:24.079 --> 00:10:26.150
choose different solutions from cradle
00:10:26.160 --> 00:10:28.310
points to pep link whatever it might
00:10:28.320 --> 00:10:29.990
We want to be able to source that in our
00:10:30.000 --> 00:10:31.509
application because not every, you know,
00:10:31.519 --> 00:10:33.030
fire departments can't all agree in
00:10:33.040 --> 00:10:35.670
terms of what solution they choose. As
00:10:35.680 --> 00:10:37.190
chief knows,
00:10:37.200 --> 00:10:39.190
>> it's incredible when you think about how
00:10:39.200 --> 00:10:42.310
it applies at the street level. I uh was
00:10:42.320 --> 00:10:44.069
still working as a fire chief at Twit
00:10:44.079 --> 00:10:46.870
Valley Fire and it's uh it's uh
00:10:46.880 --> 00:10:49.829
Christmas Eve. I'm driving back from the
00:10:49.839 --> 00:10:51.430
office. I'm going home and of course I'm
00:10:51.440 --> 00:10:53.269
going home early because I'm the chief.
00:10:53.279 --> 00:10:55.030
So I was heading out. It's probably
00:10:55.040 --> 00:10:58.150
about 2:00 in the afternoon and you you
00:10:58.160 --> 00:11:01.030
hear a pre-alert for a structure fire, a
00:11:01.040 --> 00:11:03.190
commercial fire at Washington Square
00:11:03.200 --> 00:11:05.190
Mall. Now, Washington Square Mall inside
00:11:05.200 --> 00:11:08.230
TVF&R is the largest regional mall in
00:11:08.240 --> 00:11:10.790
the area and it's Christmas Eve, right?
00:11:10.800 --> 00:11:13.990
It's during the sprint mad rush part and
00:11:14.000 --> 00:11:16.150
I'm thinking, "Yeah, well, there's no
00:11:16.160 --> 00:11:19.590
way there's a fire at the mall at this
00:11:19.600 --> 00:11:22.630
time, right? It's just not." And um and
00:11:22.640 --> 00:11:24.949
I just could glance out my windshield in
00:11:24.959 --> 00:11:27.269
that general direction and there was a
00:11:27.279 --> 00:11:30.310
header that was you could see that
00:11:30.320 --> 00:11:31.590
thing. I don't know why I didn't notice
00:11:31.600 --> 00:11:34.470
it before, but there definitely was a
00:11:34.480 --> 00:11:37.350
fire and and that was bad news. The
00:11:37.360 --> 00:11:39.509
worst new news was I was going to be
00:11:39.519 --> 00:11:41.990
first due and that was bad news for
00:11:42.000 --> 00:11:45.190
everybody. And uh I pull into the
00:11:45.200 --> 00:11:47.269
parking lot and soon as I get eyes on
00:11:47.279 --> 00:11:48.710
this thing, it was a roof fire that
00:11:48.720 --> 00:11:51.430
started out of a restaurant. And soon as
00:11:51.440 --> 00:11:54.069
I get eyes on it, I pick up my radio and
00:11:54.079 --> 00:11:57.350
I go straight to three alarms. Now the
00:11:57.360 --> 00:11:58.790
problem with going straight to three
00:11:58.800 --> 00:12:01.990
alarms inside TVF&R is now you have what
00:12:02.000 --> 00:12:05.030
is that 18 inbound pieces of equipment
00:12:05.040 --> 00:12:07.190
and just trying to keep that straight in
00:12:07.200 --> 00:12:09.910
my head. And I don't do this every day
00:12:09.920 --> 00:12:11.670
anymore. I was good at it when I needed
00:12:11.680 --> 00:12:14.069
to be, but I don't have all the right
00:12:14.079 --> 00:12:17.110
tools and I'm just trying to scratch and
00:12:17.120 --> 00:12:19.430
write and make note and make assignment
00:12:19.440 --> 00:12:22.310
and try to have this sound like a cogent
00:12:22.320 --> 00:12:25.910
uh instant command presence. I I could
00:12:25.920 --> 00:12:28.310
have really used uh the kinds of tools
00:12:28.320 --> 00:12:30.230
that you're describing, Will. I mean,
00:12:30.240 --> 00:12:32.949
incredible. And when you think of that,
00:12:32.959 --> 00:12:35.509
h how does your product how did you
00:12:35.519 --> 00:12:37.430
design your product to lighten cognitive
00:12:37.440 --> 00:12:40.389
load? because it's pretty critical.
00:12:40.399 --> 00:12:41.910
>> Yeah, it's a great great question,
00:12:41.920 --> 00:12:44.310
Chief. And I I've had I've had responses
00:12:44.320 --> 00:12:46.550
like that as well. Uh being a chief
00:12:46.560 --> 00:12:47.750
officer and I was also a company
00:12:47.760 --> 00:12:51.190
officer. And so, you know, there's for
00:12:51.200 --> 00:12:52.949
me when I was a chief officer, the
00:12:52.959 --> 00:12:54.389
things or even a company officer if I
00:12:54.399 --> 00:12:56.310
was an incident commander, the things I
00:12:56.320 --> 00:12:58.870
was most concerned about was obviously
00:12:58.880 --> 00:13:00.550
figuring out the incident. Where's the
00:13:00.560 --> 00:13:02.470
fire? What's happening? Where am I going
00:13:02.480 --> 00:13:05.910
to assign resources? But but primarily
00:13:05.920 --> 00:13:07.990
even first to that is I want to make
00:13:08.000 --> 00:13:09.670
sure I don't lose my resources. I want
00:13:09.680 --> 00:13:10.870
to make sure I request the right
00:13:10.880 --> 00:13:13.269
resources and I want to make sure that
00:13:13.279 --> 00:13:16.150
um I also don't forget what to do. I
00:13:16.160 --> 00:13:17.590
mean that's a huge thing that we're
00:13:17.600 --> 00:13:19.829
constantly tested on but it's a huge
00:13:19.839 --> 00:13:22.470
stress I think for chief officers is you
00:13:22.480 --> 00:13:24.069
know they're trying to balance and
00:13:24.079 --> 00:13:26.230
manage all these things um when they're
00:13:26.240 --> 00:13:28.629
showing up to an incident. So we
00:13:28.639 --> 00:13:30.069
recognize that there's a lot of things
00:13:30.079 --> 00:13:32.790
that are coming at um you know chief
00:13:32.800 --> 00:13:34.310
officers or incident commanders or
00:13:34.320 --> 00:13:36.150
responders in the field include in you
00:13:36.160 --> 00:13:38.710
know the data and so what we wanted to
00:13:38.720 --> 00:13:40.870
do was provide a very simple user
00:13:40.880 --> 00:13:43.990
interface just drag and drop tiles and
00:13:44.000 --> 00:13:45.829
handle that for the user so that the
00:13:45.839 --> 00:13:47.670
units just show up there and then they
00:13:47.680 --> 00:13:50.230
just simply just drag and drop onto a
00:13:50.240 --> 00:13:52.389
template. So you don't have to memorize
00:13:52.399 --> 00:13:54.629
how to manage a, you know, large
00:13:54.639 --> 00:13:57.430
commercial mall fire like and you don't
00:13:57.440 --> 00:13:59.350
have to have that stress. You can use
00:13:59.360 --> 00:14:00.949
our application because it's built off
00:14:00.959 --> 00:14:02.870
your policies and procedures of how to
00:14:02.880 --> 00:14:04.949
manage the incident. And if you have
00:14:04.959 --> 00:14:07.110
time and you're not on the radio, you
00:14:07.120 --> 00:14:09.110
can pull open that checklist and open up
00:14:09.120 --> 00:14:11.030
that checklist and recognize, oh my
00:14:11.040 --> 00:14:13.910
gosh, I forgot to do a a 360. I forgot
00:14:13.920 --> 00:14:15.910
to assign staging. I forgot to, you
00:14:15.920 --> 00:14:18.389
know, assign or request law enforcement.
00:14:18.399 --> 00:14:20.230
Those are all the things that I think
00:14:20.240 --> 00:14:23.990
that we use when we're listening to
00:14:24.000 --> 00:14:25.670
incident commanders in the field and how
00:14:25.680 --> 00:14:27.110
they manage the incident. You're after
00:14:27.120 --> 00:14:29.350
the afteraction reviews. It's like, oh
00:14:29.360 --> 00:14:31.829
my gosh, Chief Johnson nailed it. He got
00:14:31.839 --> 00:14:33.750
he got all the resources accounted for.
00:14:33.760 --> 00:14:35.350
He assigned them all on the second and
00:14:35.360 --> 00:14:36.790
third alarm, broke out groups and
00:14:36.800 --> 00:14:38.710
divisions, never lost a resource,
00:14:38.720 --> 00:14:40.710
requested law enforcement, requested the
00:14:40.720 --> 00:14:42.629
building engineer. He remembered it all.
00:14:42.639 --> 00:14:44.870
He's an amazing chief. Well, you're
00:14:44.880 --> 00:14:47.509
having to you're having to memorize all
00:14:47.519 --> 00:14:49.269
that stuff basically or you're having
00:14:49.279 --> 00:14:51.030
use an incident template and we bring
00:14:51.040 --> 00:14:53.829
that all into the application so that
00:14:53.839 --> 00:14:57.590
>> um I I was I was riding along very early
00:14:57.600 --> 00:15:00.629
days back in 2014 with a a battalion
00:15:00.639 --> 00:15:03.030
chief and a major metro fire department.
00:15:03.040 --> 00:15:04.389
They were using table command at the
00:15:04.399 --> 00:15:06.790
time and I was riding in the jump seat
00:15:06.800 --> 00:15:07.990
with the battalion chief. We showed up.
00:15:08.000 --> 00:15:08.949
He was going to be the incident
00:15:08.959 --> 00:15:10.470
commander and they respond two battalion
00:15:10.480 --> 00:15:13.990
chiefs on the incident. And he he looks
00:15:14.000 --> 00:15:16.069
over to me after it was a it was a room
00:15:16.079 --> 00:15:18.310
in contents fire. So it was a it was you
00:15:18.320 --> 00:15:20.949
know bread and butter for them. But he
00:15:20.959 --> 00:15:23.509
looks over to me after he gave the first
00:15:23.519 --> 00:15:25.430
drags and drops and gets the first
00:15:25.440 --> 00:15:27.430
report from whoever the truck I think it
00:15:27.440 --> 00:15:29.269
was a truck company had the IC at the
00:15:29.279 --> 00:15:31.590
time and they transferred command. And
00:15:31.600 --> 00:15:33.350
after about 30 seconds he looks over at
00:15:33.360 --> 00:15:36.870
me. goes to be honest he's like uh tab
00:15:36.880 --> 00:15:40.150
of a command it's almost boring on a on
00:15:40.160 --> 00:15:42.310
a structure because everything's handled
00:15:42.320 --> 00:15:44.310
he's got everything tracked and I'm not
00:15:44.320 --> 00:15:47.430
going to say who it is but um you know
00:15:47.440 --> 00:15:50.310
it really opens up the cognitive load
00:15:50.320 --> 00:15:52.389
for the individual to focus on the
00:15:52.399 --> 00:15:54.310
incident and focus on what's important
00:15:54.320 --> 00:15:55.670
the resources and the crews that are
00:15:55.680 --> 00:15:57.749
assigned and have the less of that
00:15:57.759 --> 00:16:00.470
stress of what is the what are the 911
00:16:00.480 --> 00:16:02.790
call details what resources are assigned
00:16:02.800 --> 00:16:04.790
did somebody get diverted to a medical.
00:16:04.800 --> 00:16:06.069
Those are all stresses that we don't
00:16:06.079 --> 00:16:07.430
necessarily have to happen and table
00:16:07.440 --> 00:16:08.710
command alleviates a lot of that.
00:16:08.720 --> 00:16:10.550
>> Yeah, it's and it's so critical, right?
00:16:10.560 --> 00:16:12.870
Especially for an officer that jumps a
00:16:12.880 --> 00:16:15.189
call. Maybe maybe just the regular
00:16:15.199 --> 00:16:16.949
assigned battalion chief. I don't know
00:16:16.959 --> 00:16:18.550
if units are in position. I don't know
00:16:18.560 --> 00:16:20.150
if they started at their station. I can
00:16:20.160 --> 00:16:24.150
make no assumptions about 53s, 51, 67
00:16:24.160 --> 00:16:26.310
coming in order. That may not be the
00:16:26.320 --> 00:16:29.590
case, right? And and as as an incident
00:16:29.600 --> 00:16:31.670
commander would know, I want to start
00:16:31.680 --> 00:16:33.910
queuing people up. Truck model wants you
00:16:33.920 --> 00:16:35.509
to lad ladder the alpha side of the
00:16:35.519 --> 00:16:37.749
building, access the roof, right? You
00:16:37.759 --> 00:16:40.069
know, I want to start making those cues
00:16:40.079 --> 00:16:41.829
before someone sets an air brake because
00:16:41.839 --> 00:16:44.710
it matters for positioning. And I think,
00:16:44.720 --> 00:16:46.470
you know, this technology is so
00:16:46.480 --> 00:16:49.269
incredible at at helping you make those
00:16:49.279 --> 00:16:52.870
kind of decisions. Um I I just I'm
00:16:52.880 --> 00:16:55.189
impressed. And and you know, every fire
00:16:55.199 --> 00:16:57.030
we ever went on, every call we ever went
00:16:57.040 --> 00:16:59.990
on, they all have a memorable component.
00:17:00.000 --> 00:17:01.910
This particular fire, I was in the
00:17:01.920 --> 00:17:03.670
middle, I just had the truck set up on
00:17:03.680 --> 00:17:06.390
the alpha side. I just sent fire attack
00:17:06.400 --> 00:17:08.470
into the building and I am about as
00:17:08.480 --> 00:17:11.110
focused as you can be. And I get a tap
00:17:11.120 --> 00:17:13.350
on my window. Someone taps in my window
00:17:13.360 --> 00:17:16.470
with their wedding ring. And I roll it
00:17:16.480 --> 00:17:18.150
down and I'm quite certain this person
00:17:18.160 --> 00:17:19.669
is going to tell me some critical
00:17:19.679 --> 00:17:21.909
information about the incident. And I
00:17:21.919 --> 00:17:23.429
roll it down. And I said, "Could I help
00:17:23.439 --> 00:17:24.949
you?" And this lady says, "Yeah, I'm
00:17:24.959 --> 00:17:26.949
parked right there. Do you mind moving?"
00:17:26.959 --> 00:17:29.669
I said, "Yes, I do.
00:17:29.679 --> 00:17:31.590
You're just like, you can't make it up."
00:17:31.600 --> 00:17:32.070
>> Wow.
00:17:32.080 --> 00:17:32.950
>> That's fun.
00:17:32.960 --> 00:17:35.110
>> No, you can't. I used to work at a
00:17:35.120 --> 00:17:37.350
casino and we'd have a cardiac arrest in
00:17:37.360 --> 00:17:39.669
the casino as an EMT and you'd be doing
00:17:39.679 --> 00:17:41.350
compressions and somebody would say, "Is
00:17:41.360 --> 00:17:44.870
that machine open?"
00:17:44.880 --> 00:17:45.909
>> Yeah.
00:17:45.919 --> 00:17:48.710
>> Probably they're looking.
00:17:48.720 --> 00:17:49.830
>> Oh my god.
00:17:49.840 --> 00:17:52.310
>> They got a feel for it. Yeah. You know,
00:17:52.320 --> 00:17:53.990
it's kind of amazing when you talk about
00:17:54.000 --> 00:17:56.549
where we're at because I I go back to my
00:17:56.559 --> 00:17:59.830
days of, you know, as a as a young chief
00:17:59.840 --> 00:18:03.430
officer and I took the ICS 2011 form,
00:18:03.440 --> 00:18:07.669
which, you know, is actually uh uh 11 by
00:18:07.679 --> 00:18:12.070
11 11 by 16 or 14 x 16. Anyway, you you
00:18:12.080 --> 00:18:13.830
fold it together and it ends up being,
00:18:13.840 --> 00:18:17.430
you know, uh sheets and that thing was
00:18:17.440 --> 00:18:19.350
set up and on the back of it, you know,
00:18:19.360 --> 00:18:21.350
is where you write down the resources
00:18:21.360 --> 00:18:23.190
that were coming. And I got tired of
00:18:23.200 --> 00:18:25.270
doing that. And so, you know, a lot of
00:18:25.280 --> 00:18:27.430
the stuff I normally did, I I, you know,
00:18:27.440 --> 00:18:30.630
I typed in there and uh then on the on
00:18:30.640 --> 00:18:31.909
the other sheet, I put in there, you
00:18:31.919 --> 00:18:34.150
know, size up, put down the list, all
00:18:34.160 --> 00:18:35.590
things I could check, check, check, make
00:18:35.600 --> 00:18:37.510
it much easier. And I look where we're
00:18:37.520 --> 00:18:39.669
at today. I said, "Well, I kind of hard
00:18:39.679 --> 00:18:41.590
to fail to be a chief officer."
00:18:41.600 --> 00:18:43.510
>> No, there's still We'll find ways room.
00:18:43.520 --> 00:18:44.870
I think we'll find ways.
00:18:44.880 --> 00:18:45.270
>> Yeah,
00:18:45.280 --> 00:18:47.350
>> for sure. For sure.
00:18:47.360 --> 00:18:52.470
>> Yeah. Yeah. So, uh uh you know, what do
00:18:52.480 --> 00:18:55.590
you see coming for public safety uh with
00:18:55.600 --> 00:18:58.789
Tablet Command uh uh development cycle?
00:18:58.799 --> 00:19:00.789
Um, I mean, you you already talked about
00:19:00.799 --> 00:19:02.310
where you were in the last couple years,
00:19:02.320 --> 00:19:04.789
but things are moving so quickly and
00:19:04.799 --> 00:19:07.029
and, uh, there's, you know, so much
00:19:07.039 --> 00:19:09.190
competition in this space and, uh, you
00:19:09.200 --> 00:19:11.190
know, who's going to be ahead and who
00:19:11.200 --> 00:19:12.950
you working with and all that. I mean,
00:19:12.960 --> 00:19:14.150
where where do you see your
00:19:14.160 --> 00:19:14.710
developments?
00:19:14.720 --> 00:19:16.230
>> Yeah. No, it's a great great question.
00:19:16.240 --> 00:19:18.549
So, you know, there's things that I'll
00:19:18.559 --> 00:19:19.750
I'll be honest. There's things that
00:19:19.760 --> 00:19:21.669
we're thinking about that I'm not
00:19:21.679 --> 00:19:23.110
willing to share, of course, in terms
00:19:23.120 --> 00:19:24.710
of, you know,
00:19:24.720 --> 00:19:28.950
>> No, but I'll tell we won't tell anybody.
00:19:28.960 --> 00:19:31.110
That's right. Uh but I'll share I'll
00:19:31.120 --> 00:19:32.549
share what we're what we have coming.
00:19:32.559 --> 00:19:34.950
This is like a pre pre kind of
00:19:34.960 --> 00:19:37.270
announcement that we've got FDIC next
00:19:37.280 --> 00:19:39.669
week and so we'll be there of course and
00:19:39.679 --> 00:19:42.070
u our our team will be demoing a number
00:19:42.080 --> 00:19:43.830
of these things. But just at a high
00:19:43.840 --> 00:19:45.190
level some of the things that we've been
00:19:45.200 --> 00:19:48.310
working on is um uh we have we're we
00:19:48.320 --> 00:19:49.909
have the ability to support caller
00:19:49.919 --> 00:19:52.710
location. So if the communication center
00:19:52.720 --> 00:19:54.470
has an integration with something like
00:19:54.480 --> 00:19:56.950
uh rapid SOS or rapid deploy and the
00:19:56.960 --> 00:19:58.390
communication center has that caller
00:19:58.400 --> 00:20:00.150
location data, we can show that in our
00:20:00.160 --> 00:20:02.630
application. So if as that's updating uh
00:20:02.640 --> 00:20:03.909
working with the communication center,
00:20:03.919 --> 00:20:05.990
we can support that if the if the comm
00:20:06.000 --> 00:20:09.750
center has the data in their CAD.
00:20:09.760 --> 00:20:12.310
We've got personnel location. So we
00:20:12.320 --> 00:20:14.710
talked about vehicle location data and
00:20:14.720 --> 00:20:16.390
trying to track all that and that's been
00:20:16.400 --> 00:20:19.510
a huge value ad to the fire service. But
00:20:19.520 --> 00:20:21.909
there's a, as you know, there's a on the
00:20:21.919 --> 00:20:23.590
horizon, there's a lot of companies out
00:20:23.600 --> 00:20:27.029
there, and we've had the P25 location uh
00:20:27.039 --> 00:20:28.789
from the radios for a long time that our
00:20:28.799 --> 00:20:30.230
radios have been able to support, but
00:20:30.240 --> 00:20:32.070
the radio systems really haven't
00:20:32.080 --> 00:20:34.310
practically been able to support until
00:20:34.320 --> 00:20:36.870
recently, I would say, because you have
00:20:36.880 --> 00:20:39.590
um you know, solutions like uh Motorola
00:20:39.600 --> 00:20:42.310
has their P25 location through their API
00:20:42.320 --> 00:20:45.190
because they have uh a SIM card built
00:20:45.200 --> 00:20:46.710
into the radio. So, they're able to send
00:20:46.720 --> 00:20:48.310
that location data. So, we're doing that
00:20:48.320 --> 00:20:50.470
for a large customer in the Florida in
00:20:50.480 --> 00:20:52.470
the state of Florida um where we're
00:20:52.480 --> 00:20:54.470
sending officer location. They're
00:20:54.480 --> 00:20:56.310
utilizing that inside tablet command.
00:20:56.320 --> 00:20:57.430
So, that's one of the things that we're
00:20:57.440 --> 00:20:58.630
going to be announcing is that we're
00:20:58.640 --> 00:21:00.470
going to have a separate layer for
00:21:00.480 --> 00:21:02.230
personnel locations. So, you could turn
00:21:02.240 --> 00:21:04.710
that on and you can also search on those
00:21:04.720 --> 00:21:06.310
personnel as well. So, if you're looking
00:21:06.320 --> 00:21:08.789
for Chief Jeff Johnson and they're
00:21:08.799 --> 00:21:09.990
assigned to this incident, you could
00:21:10.000 --> 00:21:13.110
type JHN and you'd be able to see where
00:21:13.120 --> 00:21:15.190
that location is for that firefighter or
00:21:15.200 --> 00:21:16.950
that chief.
00:21:16.960 --> 00:21:19.270
Nerys is huge as we all know there's a
00:21:19.280 --> 00:21:21.350
lot of talk about nerys. So tablet
00:21:21.360 --> 00:21:23.190
command at the core of the application
00:21:23.200 --> 00:21:25.590
when we built it we have checklists so
00:21:25.600 --> 00:21:27.830
you're able to you know define what your
00:21:27.840 --> 00:21:29.350
checklist look like. Well what we're
00:21:29.360 --> 00:21:32.230
doing to support ner and to support all
00:21:32.240 --> 00:21:33.990
CADs and all incident reporting
00:21:34.000 --> 00:21:35.430
solutions that are out in the market. We
00:21:35.440 --> 00:21:37.909
find that this approach is the best hold
00:21:37.919 --> 00:21:40.230
CAD as the authority. And so what our
00:21:40.240 --> 00:21:42.470
checklist now can support is we can mark
00:21:42.480 --> 00:21:45.029
those as n nearest tactical benchmarks.
00:21:45.039 --> 00:21:46.870
There's about eight of them that Nerys
00:21:46.880 --> 00:21:49.590
has that you can you can tag a tablet
00:21:49.600 --> 00:21:51.190
command checklist item as a nearest
00:21:51.200 --> 00:21:53.110
checklist so that we can you can start
00:21:53.120 --> 00:21:55.510
mining that data but we'll also send it
00:21:55.520 --> 00:21:58.390
back to the CAD so that it'll come back
00:21:58.400 --> 00:22:00.710
into the CAD as the authority the record
00:22:00.720 --> 00:22:02.630
for the record management system whether
00:22:02.640 --> 00:22:04.870
you use you know image trend or ESO
00:22:04.880 --> 00:22:06.230
whoever is out there they're able to
00:22:06.240 --> 00:22:07.830
mine that data for those tactical
00:22:07.840 --> 00:22:09.110
benchmarks and bring that into the
00:22:09.120 --> 00:22:12.390
instant reporting um and then inapp
00:22:12.400 --> 00:22:16.230
navigation so we've We integrate with
00:22:16.240 --> 00:22:18.950
Apple Maps, Ways, Google Maps, forflight
00:22:18.960 --> 00:22:21.350
mobile for our aviation customers and
00:22:21.360 --> 00:22:23.270
Ezri Navigator, which is another third
00:22:23.280 --> 00:22:26.149
party application. We can send uh people
00:22:26.159 --> 00:22:27.909
out to those applications. We've had
00:22:27.919 --> 00:22:30.070
requests primarily from our larger
00:22:30.080 --> 00:22:32.310
wildland customers to be able to
00:22:32.320 --> 00:22:34.549
navigate directly to the incident so
00:22:34.559 --> 00:22:37.350
that they can still go through traffic,
00:22:37.360 --> 00:22:39.110
go through road road closures and those
00:22:39.120 --> 00:22:40.470
type of things or use their own
00:22:40.480 --> 00:22:42.390
customized streets. So, we're going to
00:22:42.400 --> 00:22:43.590
be able to support that in our
00:22:43.600 --> 00:22:45.110
application. So, our team will be able
00:22:45.120 --> 00:22:47.190
to demo that next week at FDIC and you
00:22:47.200 --> 00:22:49.110
can stop by and check that out. And one
00:22:49.120 --> 00:22:50.549
of the ones I'm really excited about
00:22:50.559 --> 00:22:53.350
relative to Wildfire is Watchd Duty. So,
00:22:53.360 --> 00:22:56.310
we partnered with Watchd Duty.
00:22:56.320 --> 00:22:58.310
And with Watchd Duty, there's three
00:22:58.320 --> 00:23:00.310
things we're working with them on which
00:23:00.320 --> 00:23:03.590
we're going to have in uh version 4.3.
00:23:03.600 --> 00:23:05.750
So, right uh we have 4.2 that's coming
00:23:05.760 --> 00:23:07.350
up for launch and 4.3 is going to
00:23:07.360 --> 00:23:09.909
support these watchduty features. First
00:23:09.919 --> 00:23:12.950
off, if the customer chooses, they can
00:23:12.960 --> 00:23:17.029
have us um based off rules send an
00:23:17.039 --> 00:23:18.870
update notification to watch duty
00:23:18.880 --> 00:23:20.470
including the latin long date and time
00:23:20.480 --> 00:23:22.789
and the call type uh and what agencies
00:23:22.799 --> 00:23:24.710
responding just to give them a highle
00:23:24.720 --> 00:23:26.549
notification that there's an incident.
00:23:26.559 --> 00:23:28.390
So watch duty calls that a signal. So
00:23:28.400 --> 00:23:30.390
they get notification that there's an
00:23:30.400 --> 00:23:32.310
incident going and we can work with our
00:23:32.320 --> 00:23:34.630
customers only if they opt to send it
00:23:34.640 --> 00:23:36.310
automatically send that to watch duty
00:23:36.320 --> 00:23:37.990
just highle location of incident in the
00:23:38.000 --> 00:23:40.549
call type inside the application as
00:23:40.559 --> 00:23:42.470
another feature what we're working on is
00:23:42.480 --> 00:23:45.029
being able to uh allow our users to see
00:23:45.039 --> 00:23:47.510
the watchd duty incidents because a lot
00:23:47.520 --> 00:23:49.350
of a lot of our users are utilizing
00:23:49.360 --> 00:23:51.750
watchd duty for you know uh situational
00:23:51.760 --> 00:23:53.350
awareness of what's going on on these
00:23:53.360 --> 00:23:54.789
large wildland fires and they're also
00:23:54.799 --> 00:23:56.950
using tablet command. So we want to be
00:23:56.960 --> 00:23:59.110
able to show watchd duty incidents in
00:23:59.120 --> 00:24:00.870
tablet command. So you can jump into the
00:24:00.880 --> 00:24:02.630
watchd duty app and get those updates.
00:24:02.640 --> 00:24:04.310
So we'll be able to have little icons or
00:24:04.320 --> 00:24:05.990
symbology for the watchd duty incidents
00:24:06.000 --> 00:24:08.149
in tablet command. And then the one I'm
00:24:08.159 --> 00:24:11.190
most excited about from an efficiency
00:24:11.200 --> 00:24:14.710
standpoint is the ability for a user a
00:24:14.720 --> 00:24:16.549
department can choose for example they
00:24:16.559 --> 00:24:18.870
could say hey chief zigaras is allowed
00:24:18.880 --> 00:24:20.549
to do this but chief Johnson's not
00:24:20.559 --> 00:24:23.350
allowed to do this is send updates to
00:24:23.360 --> 00:24:25.909
watchd duty. So today it's already
00:24:25.919 --> 00:24:27.110
having happen happening in common
00:24:27.120 --> 00:24:29.430
practice where PIOS, incident
00:24:29.440 --> 00:24:30.710
commanders, battalion chiefs or
00:24:30.720 --> 00:24:32.950
communication center or um you know
00:24:32.960 --> 00:24:34.950
staff are sending updates to watchd duty
00:24:34.960 --> 00:24:37.830
about acreage evacuations, whatever it
00:24:37.840 --> 00:24:39.510
might be. They're sending text messages
00:24:39.520 --> 00:24:41.909
and emails today. What we wanted to do
00:24:41.919 --> 00:24:44.070
was allow a user in tablet command, of
00:24:44.080 --> 00:24:46.230
course the user does this and chooses if
00:24:46.240 --> 00:24:47.510
they want to do it and the department
00:24:47.520 --> 00:24:49.750
chooses who has that ability. They can
00:24:49.760 --> 00:24:52.549
tap a comment in tablet command and then
00:24:52.559 --> 00:24:54.630
get it to edit and they can edit the
00:24:54.640 --> 00:24:55.909
comment before they're sending it to
00:24:55.919 --> 00:24:58.149
watchd duty and it asks like what's your
00:24:58.159 --> 00:24:59.430
phone number and some other things that
00:24:59.440 --> 00:25:02.710
watch watchd duty wants before um you
00:25:02.720 --> 00:25:04.230
know so they can vet it and follow up
00:25:04.240 --> 00:25:05.909
with any questions but it'll just
00:25:05.919 --> 00:25:08.070
immediately go to watchduty direct. So
00:25:08.080 --> 00:25:09.510
there's no more opening up a text
00:25:09.520 --> 00:25:10.950
message or an email. You can basically
00:25:10.960 --> 00:25:13.269
tap a comment. Maybe it's talking about
00:25:13.279 --> 00:25:15.669
evacuations or evacuation zones that are
00:25:15.679 --> 00:25:17.430
being activated. tap a comment in, tap a
00:25:17.440 --> 00:25:19.269
command coming from CAD or from the
00:25:19.279 --> 00:25:20.950
incident manager and immediately send
00:25:20.960 --> 00:25:22.230
that to watch duty. So, we're really
00:25:22.240 --> 00:25:23.430
excited about that in terms of the
00:25:23.440 --> 00:25:25.909
efficiency allowing users and
00:25:25.919 --> 00:25:27.750
departments to choose what they want to
00:25:27.760 --> 00:25:30.549
send and when to watch duty and it's
00:25:30.559 --> 00:25:32.149
essentially at no cost. There's no cost
00:25:32.159 --> 00:25:34.149
for the for the users. So, those are
00:25:34.159 --> 00:25:35.590
just a high level some of the things
00:25:35.600 --> 00:25:38.630
that are coming uh chief in terms of on
00:25:38.640 --> 00:25:40.789
the tablet command side. We're also
00:25:40.799 --> 00:25:44.310
looking at um ways that we can add AI or
00:25:44.320 --> 00:25:46.630
you know um artificial intelligence to
00:25:46.640 --> 00:25:49.029
help users maybe provide an
00:25:49.039 --> 00:25:51.430
autogenerated summary of the incident or
00:25:51.440 --> 00:25:53.190
report those type of things. We're
00:25:53.200 --> 00:25:54.470
looking and we're adding those features
00:25:54.480 --> 00:25:56.470
and that's kind of all high level I can
00:25:56.480 --> 00:25:58.710
talk about uh at this point but that's
00:25:58.720 --> 00:25:59.830
kind of what we're looking at on the
00:25:59.840 --> 00:26:02.390
road map and also the integrations we
00:26:02.400 --> 00:26:04.630
are constantly talking and I'll I think
00:26:04.640 --> 00:26:06.549
we might have a topic about integrations
00:26:06.559 --> 00:26:08.390
but we're always talking with partners
00:26:08.400 --> 00:26:10.230
about how to bring that data from other
00:26:10.240 --> 00:26:12.710
solutions into tablet command so that
00:26:12.720 --> 00:26:14.789
it's available to the users in the field
00:26:14.799 --> 00:26:18.630
to truly make a difference.
00:26:18.640 --> 00:26:22.149
So, uh, um, how's your cycle looking as
00:26:22.159 --> 00:26:23.590
you, as you're trying to move out of the
00:26:23.600 --> 00:26:25.029
west, heading more east? How's that
00:26:25.039 --> 00:26:25.830
working for you?
00:26:25.840 --> 00:26:28.470
>> It's, um, it's it's working well. It's
00:26:28.480 --> 00:26:30.070
working well, chief. To be completely
00:26:30.080 --> 00:26:33.669
honest, I I say that, um, you know, just
00:26:33.679 --> 00:26:35.269
like anything that's new to the fire
00:26:35.279 --> 00:26:37.510
service. I think certain certain states
00:26:37.520 --> 00:26:40.390
certain regions adopt uh solutions you
00:26:40.400 --> 00:26:42.950
know like if you think back to you know
00:26:42.960 --> 00:26:46.230
way back way ICS uh blue card or
00:26:46.240 --> 00:26:47.269
different things have been introduced
00:26:47.279 --> 00:26:49.269
across the United States that different
00:26:49.279 --> 00:26:50.789
pockets pick it up at different times
00:26:50.799 --> 00:26:52.710
and so we're seeing we're seeing that
00:26:52.720 --> 00:26:54.470
across the United States and some some
00:26:54.480 --> 00:26:57.190
regions are a little bit more
00:26:57.200 --> 00:26:58.870
uh
00:26:58.880 --> 00:27:00.710
further along down the path in terms of
00:27:00.720 --> 00:27:02.390
digital incident command than others but
00:27:02.400 --> 00:27:04.630
we uh you know it's predominantly I
00:27:04.640 --> 00:27:05.750
would
00:27:05.760 --> 00:27:08.149
western United States, Florida, Texas,
00:27:08.159 --> 00:27:09.750
and we have pockets of other states
00:27:09.760 --> 00:27:13.510
including like Ohio and um that are
00:27:13.520 --> 00:27:16.070
really adopting tablet command. So
00:27:16.080 --> 00:27:17.750
>> yeah, I don't think it's a secret like
00:27:17.760 --> 00:27:20.070
the Western Fire Chief crafted its
00:27:20.080 --> 00:27:22.870
mission around that, right? Our our
00:27:22.880 --> 00:27:24.470
mission at the Western Fire Chiefs is
00:27:24.480 --> 00:27:26.870
technology, wildfire, and the
00:27:26.880 --> 00:27:29.029
intersection of those two. And and
00:27:29.039 --> 00:27:31.029
that's because so much of the tech has
00:27:31.039 --> 00:27:32.870
started in the west and it tends to move
00:27:32.880 --> 00:27:35.590
east. uh the you know people work in the
00:27:35.600 --> 00:27:37.110
east coast they know things we don't
00:27:37.120 --> 00:27:39.750
know like I I I I don't know a thing
00:27:39.760 --> 00:27:41.909
about tornadoes and hurricanes I don't
00:27:41.919 --> 00:27:44.390
know other than the basics they're
00:27:44.400 --> 00:27:46.789
experts at them so every place has its
00:27:46.799 --> 00:27:49.990
thing but tech historically been a west
00:27:50.000 --> 00:27:52.549
thing and and the west because maybe
00:27:52.559 --> 00:27:55.190
we're younger as a profession here um
00:27:55.200 --> 00:27:57.430
maybe a little more willing to adapt to
00:27:57.440 --> 00:27:59.830
it but that doesn't make it better it
00:27:59.840 --> 00:28:02.470
just makes it an an observation so I'm
00:28:02.480 --> 00:28:04.230
I'm really glad to see that it's being
00:28:04.240 --> 00:28:06.549
accepted as you move across the country.
00:28:06.559 --> 00:28:08.230
I' I've been so proud of the fire
00:28:08.240 --> 00:28:10.710
service, fire and EMS that just how
00:28:10.720 --> 00:28:13.269
progressive they are. If you can show
00:28:13.279 --> 00:28:15.669
them that it makes the call better and
00:28:15.679 --> 00:28:18.470
and that's the key, right? Uh it's just
00:28:18.480 --> 00:28:22.389
making it better, you know. Um, when I
00:28:22.399 --> 00:28:24.230
when Chief Sagaras took me around the
00:28:24.240 --> 00:28:26.950
campfire in Paradise, California, one of
00:28:26.960 --> 00:28:28.710
the things as I talked to the first
00:28:28.720 --> 00:28:31.269
battalion chief about the challenges he
00:28:31.279 --> 00:28:34.230
faced, he was talking about uh going
00:28:34.240 --> 00:28:36.470
from evacuate this part of town, this
00:28:36.480 --> 00:28:40.070
section, to evacuate the whole town, and
00:28:40.080 --> 00:28:42.789
that happened in little to no time. And
00:28:42.799 --> 00:28:46.149
and he did that as we all did with
00:28:46.159 --> 00:28:48.310
virtually no situational awareness,
00:28:48.320 --> 00:28:51.430
right? that how nice would it have been
00:28:51.440 --> 00:28:54.470
for him to touch his tablet command and
00:28:54.480 --> 00:28:57.430
touch the map and see the impedance for
00:28:57.440 --> 00:29:00.310
traffic on every route out so that you
00:29:00.320 --> 00:29:01.909
could prioritize the routes that are
00:29:01.919 --> 00:29:04.950
green, not yellow or red. And and you
00:29:04.960 --> 00:29:07.350
know that those are these odd little
00:29:07.360 --> 00:29:10.070
components of a comprehensive common
00:29:10.080 --> 00:29:12.950
operating picture. one that integrates
00:29:12.960 --> 00:29:16.070
uh uh fire and EMS, but also law
00:29:16.080 --> 00:29:18.950
enforcement, emergency ma management,
00:29:18.960 --> 00:29:21.510
transportation functions that the county
00:29:21.520 --> 00:29:23.830
and state hold. You know, to have that
00:29:23.840 --> 00:29:26.710
two or three taps away helps us make
00:29:26.720 --> 00:29:28.470
better decisions. And to your point,
00:29:28.480 --> 00:29:31.110
it's a perfect execution of AI. It could
00:29:31.120 --> 00:29:33.190
be queuing up the one that it thinks you
00:29:33.200 --> 00:29:37.669
you should be using. Where are you on uh
00:29:37.679 --> 00:29:39.669
the creation of a common operating
00:29:39.679 --> 00:29:41.990
platform?
00:29:42.000 --> 00:29:43.430
Yeah, good, great question. Let me
00:29:43.440 --> 00:29:45.669
answer I'll answer that. Uh just you
00:29:45.679 --> 00:29:47.430
just got me thinking about we just at
00:29:47.440 --> 00:29:49.669
the Western Fire Chiefs at the Ignite
00:29:49.679 --> 00:29:52.710
conference. We demoed with um Earth, you
00:29:52.720 --> 00:29:53.590
know, because you're talking about the
00:29:53.600 --> 00:29:55.990
Paradise Fire, the campfire. Um you're t
00:29:56.000 --> 00:29:57.510
we demonstrated with Earth Fire
00:29:57.520 --> 00:29:59.430
Alliance, which has new technology on
00:29:59.440 --> 00:30:01.110
satellite
00:30:01.120 --> 00:30:04.310
and detection. We talked we did um a
00:30:04.320 --> 00:30:06.789
thing with XYOP plan where in terms of
00:30:06.799 --> 00:30:08.950
working with fire aside data in terms of
00:30:08.960 --> 00:30:11.190
structure structure hardening and then
00:30:11.200 --> 00:30:12.870
tablet command was every all the data
00:30:12.880 --> 00:30:14.789
was showing up in tablet command and
00:30:14.799 --> 00:30:17.350
they had the modeling with fireside
00:30:17.360 --> 00:30:20.070
structure protection data and then also
00:30:20.080 --> 00:30:22.470
you have the genesis evacuation zones
00:30:22.480 --> 00:30:24.389
all in one layer so you can see all this
00:30:24.399 --> 00:30:25.750
stuff and it just got me thinking when
00:30:25.760 --> 00:30:27.909
you were talking about the paradise fire
00:30:27.919 --> 00:30:29.990
of all the differences of the data that
00:30:30.000 --> 00:30:31.909
we have today in tablet command can
00:30:31.919 --> 00:30:34.310
truly make a difference. To answer your
00:30:34.320 --> 00:30:36.549
question on the common operating uh
00:30:36.559 --> 00:30:39.909
platform, we're there today as a common
00:30:39.919 --> 00:30:42.549
operating platform. Um for a lot of our
00:30:42.559 --> 00:30:44.149
a lot of our you know all our customers
00:30:44.159 --> 00:30:45.750
are utilizing it as a common operating
00:30:45.760 --> 00:30:48.149
platform. when you start to operate in a
00:30:48.159 --> 00:30:50.310
region or when you're like you mentioned
00:30:50.320 --> 00:30:52.870
with law enforcement and uh emergency
00:30:52.880 --> 00:30:55.510
management also events we're there as
00:30:55.520 --> 00:30:57.830
well and there's more adoption and it's
00:30:57.840 --> 00:30:59.750
becoming more and more the common opera
00:30:59.760 --> 00:31:02.470
operating platform for for our customers
00:31:02.480 --> 00:31:04.149
but just to give you some examples like
00:31:04.159 --> 00:31:07.269
we mentioned the LA fires in 2025 uh
00:31:07.279 --> 00:31:10.470
fire local government fire agencies OES
00:31:10.480 --> 00:31:12.630
Calire were all utilizing table command
00:31:12.640 --> 00:31:15.029
at some level to see location of
00:31:15.039 --> 00:31:17.029
resources is where people were assigned
00:31:17.039 --> 00:31:19.110
and what those incidents looked like.
00:31:19.120 --> 00:31:21.190
And just recently, we just demonstrated
00:31:21.200 --> 00:31:22.389
talked about a common operating
00:31:22.399 --> 00:31:24.870
platform. I can't share the video. I
00:31:24.880 --> 00:31:27.830
don't have the permission yet, but I the
00:31:27.840 --> 00:31:29.990
Tortuga Festival, which is I believe in
00:31:30.000 --> 00:31:33.590
Fort Lauderdale, Broward County area, uh
00:31:33.600 --> 00:31:38.549
they hosted a 100,000 person um uh not
00:31:38.559 --> 00:31:45.029
conference, um festival um and they um
00:31:45.039 --> 00:31:47.350
they had drone video, they had you know
00:31:47.360 --> 00:31:49.830
with Skyo, they had all their customized
00:31:49.840 --> 00:31:52.310
maps. So, everyone was operating on this
00:31:52.320 --> 00:31:55.029
platform to see everything. uh at the at
00:31:55.039 --> 00:31:57.110
the festival. So you have law
00:31:57.120 --> 00:31:58.870
enforcement with potentially with their
00:31:58.880 --> 00:32:00.870
drone video coming in with fire with
00:32:00.880 --> 00:32:03.269
their ICS board with all the customized
00:32:03.279 --> 00:32:05.430
maps. Um you could put anything you want
00:32:05.440 --> 00:32:08.549
in tablet command. So it is becoming
00:32:08.559 --> 00:32:10.389
depending on the region it is the common
00:32:10.399 --> 00:32:12.389
operating platform. Uh definitely for a
00:32:12.399 --> 00:32:14.470
lot of our customers uh and depending on
00:32:14.480 --> 00:32:16.310
the region it's becoming the comp common
00:32:16.320 --> 00:32:19.029
operating platform as well. Um, so we're
00:32:19.039 --> 00:32:21.110
definitely on the way to be the common
00:32:21.120 --> 00:32:23.269
operating platform hopefully for for
00:32:23.279 --> 00:32:24.950
public safety altogether.
00:32:24.960 --> 00:32:27.269
>> That'd be pretty critical. Chief Z and I
00:32:27.279 --> 00:32:28.630
remember when there were multiple
00:32:28.640 --> 00:32:31.509
incident command systems and and finally
00:32:31.519 --> 00:32:33.029
the country had enough and said we're
00:32:33.039 --> 00:32:35.590
doing one and that'll be a good day in
00:32:35.600 --> 00:32:37.750
public safety when we have one. Uh, so
00:32:37.760 --> 00:32:39.750
we appreciate your work there.
00:32:39.760 --> 00:32:41.430
>> Yeah.
00:32:41.440 --> 00:32:43.430
You know, kind of interesting. Um, you
00:32:43.440 --> 00:32:45.190
know, I not too long ago there was a
00:32:45.200 --> 00:32:48.789
CalFire video out uh and it actually has
00:32:48.799 --> 00:32:51.269
uh you know, one of the uh one of their
00:32:51.279 --> 00:32:53.669
Firehawks and it it was, you know,
00:32:53.679 --> 00:32:55.430
saying, "Hey, we use tablet command. We
00:32:55.440 --> 00:32:56.950
don't have to punch things in anymore.
00:32:56.960 --> 00:32:59.190
Now we've got it. We just get you know,
00:32:59.200 --> 00:33:01.350
get the alert, get get on board and go
00:33:01.360 --> 00:33:03.269
and takes us there," which I thought was
00:33:03.279 --> 00:33:05.509
uh speaks well. And I mean, uh, you
00:33:05.519 --> 00:33:07.750
know, you're talking one end and yet,
00:33:07.760 --> 00:33:10.870
uh, you know, um, um, you know, all the
00:33:10.880 --> 00:33:13.029
aviation feeds you've added are, you
00:33:13.039 --> 00:33:15.509
know, kind of J kind of like JJ, we put
00:33:15.519 --> 00:33:17.590
the aviation feeds on the Western Fire
00:33:17.600 --> 00:33:21.110
Map out there. So, you know, um, will
00:33:21.120 --> 00:33:22.870
uh, you know, you've got a lot of
00:33:22.880 --> 00:33:24.549
partners you're you're you've partnered
00:33:24.559 --> 00:33:27.190
up with to do this integration and, uh,
00:33:27.200 --> 00:33:28.389
you know, at the end of the day, it's
00:33:28.399 --> 00:33:30.870
for the boots on the ground. uh uh but
00:33:30.880 --> 00:33:32.710
you're also sharing you know boots on
00:33:32.720 --> 00:33:35.110
the ground to the IC's uh to the command
00:33:35.120 --> 00:33:37.509
staff and ultimately also pushing it to
00:33:37.519 --> 00:33:41.269
uh EOCC's so uh you know you've got a
00:33:41.279 --> 00:33:42.710
lot of partners out there
00:33:42.720 --> 00:33:46.149
>> yeah we do and you know over the years
00:33:46.159 --> 00:33:49.029
we have requests from integrating to CAD
00:33:49.039 --> 00:33:52.310
to building the MBT to AVL to staffing
00:33:52.320 --> 00:33:55.190
solutions and we've recognized that
00:33:55.200 --> 00:33:56.870
responders are utilizing or the incident
00:33:56.880 --> 00:33:59.110
commanders are utilizing our tablet or
00:33:59.120 --> 00:34:01.830
or our pane of glass as the solution
00:34:01.840 --> 00:34:03.190
that they're trying to manage incidents
00:34:03.200 --> 00:34:05.990
and respond on. And it only creates more
00:34:06.000 --> 00:34:08.389
value for both our partners, you know,
00:34:08.399 --> 00:34:10.149
other vendors in the industry, but also
00:34:10.159 --> 00:34:12.470
our customers to be able to see that
00:34:12.480 --> 00:34:15.109
valuable data as well. So, um, you know,
00:34:15.119 --> 00:34:16.950
you're looking at staffing solutions,
00:34:16.960 --> 00:34:18.710
customized mapping solutions, including
00:34:18.720 --> 00:34:22.389
like EZRI, uh, ADSB, which is, you know,
00:34:22.399 --> 00:34:24.310
uh, aircraft location. We're showcasing
00:34:24.320 --> 00:34:26.069
that in tablet command. So you can see
00:34:26.079 --> 00:34:27.990
government and military and fire
00:34:28.000 --> 00:34:29.750
aircraft as well operating on these
00:34:29.760 --> 00:34:31.430
incidents. You know I mentioned Watchd
00:34:31.440 --> 00:34:34.149
Duty Genesis which is you know formerly
00:34:34.159 --> 00:34:36.950
Zone Haven to see the evacuation zones.
00:34:36.960 --> 00:34:39.909
Um we've got a company called Firemapper
00:34:39.919 --> 00:34:42.230
where you can edit and annotate maps in
00:34:42.240 --> 00:34:43.589
real time with multiple people
00:34:43.599 --> 00:34:45.109
simultaneously.
00:34:45.119 --> 00:34:47.829
Drone video we've integrated with you
00:34:47.839 --> 00:34:50.149
know uh photokite drone sense aerody
00:34:50.159 --> 00:34:53.030
data skyio you name it we can show that
00:34:53.040 --> 00:34:55.190
in tablet command. So it really starts
00:34:55.200 --> 00:34:57.270
to kind of build out this ecosystem
00:34:57.280 --> 00:34:59.750
including all the staffing solutions and
00:34:59.760 --> 00:35:03.750
uh you know we're also talking pre-plans
00:35:03.760 --> 00:35:05.910
uh coming from CAD pre-plans coming from
00:35:05.920 --> 00:35:09.510
solutions like first do u or whatever it
00:35:09.520 --> 00:35:11.829
might be and personnel locations we
00:35:11.839 --> 00:35:13.510
recognize that all these integrations
00:35:13.520 --> 00:35:16.310
all these partners are so valuable to
00:35:16.320 --> 00:35:19.430
the to to the tablet command product we
00:35:19.440 --> 00:35:21.030
you know I went so far as hiring
00:35:21.040 --> 00:35:22.790
dedicated person just to manage our
00:35:22.800 --> 00:35:25.109
partnerships and our ecosystem with all
00:35:25.119 --> 00:35:27.109
of our different vendors. Um so if we
00:35:27.119 --> 00:35:28.870
have a customer that has something that
00:35:28.880 --> 00:35:31.030
we haven't integrated with uh please
00:35:31.040 --> 00:35:33.109
make that request to us um so that we
00:35:33.119 --> 00:35:34.790
can provide that value and we'll make
00:35:34.800 --> 00:35:36.550
that valuable and that integration to
00:35:36.560 --> 00:35:38.950
other customers as well because it's
00:35:38.960 --> 00:35:41.990
really you know it's you know Chief
00:35:42.000 --> 00:35:44.150
Johnson mentioned all the the single
00:35:44.160 --> 00:35:46.390
sign on the login and all these you know
00:35:46.400 --> 00:35:47.910
uh potentially in another another
00:35:47.920 --> 00:35:49.990
conversation we had but it tablet
00:35:50.000 --> 00:35:52.630
command brings all that data into one
00:35:52.640 --> 00:35:54.470
one pane of glass and that's that's
00:35:54.480 --> 00:35:56.470
where we really show show The value is
00:35:56.480 --> 00:35:57.990
is our partner is our partner.
00:35:58.000 --> 00:35:58.550
>> That's critical
00:35:58.560 --> 00:36:00.150
>> and that other data.
00:36:00.160 --> 00:36:01.829
>> I don't need to be remembering passwords
00:36:01.839 --> 00:36:03.750
in the middle of some lady tapping on my
00:36:03.760 --> 00:36:07.430
window. I you know I I want I just want
00:36:07.440 --> 00:36:10.069
to open the darn thing and touch it and
00:36:10.079 --> 00:36:11.910
have it move and get stuff done and
00:36:11.920 --> 00:36:14.950
lighten my load. Um, you know, as a
00:36:14.960 --> 00:36:16.710
couple of the guys, Chief Z and I
00:36:16.720 --> 00:36:18.710
working on a team of people trying to
00:36:18.720 --> 00:36:21.109
make sure that public safety always have
00:36:21.119 --> 00:36:25.109
tenacious uh LTE 5G soon to be 6G
00:36:25.119 --> 00:36:27.430
coverage. All this stuff requires
00:36:27.440 --> 00:36:30.790
connectivity, you know, and uh and and
00:36:30.800 --> 00:36:32.870
FirstNet has done such a remarkable job.
00:36:32.880 --> 00:36:34.950
They now have over a quarter million
00:36:34.960 --> 00:36:36.310
square miles of coverage, more than
00:36:36.320 --> 00:36:39.430
anyone else in the country. And this
00:36:39.440 --> 00:36:41.670
next year, the end of this year and next
00:36:41.680 --> 00:36:44.310
year, they're adding a satellite uh
00:36:44.320 --> 00:36:47.349
offering, which is satellite to device.
00:36:47.359 --> 00:36:50.230
So, no more sell over Wi-Fi. That your
00:36:50.240 --> 00:36:52.310
phone will see a satellite the same as
00:36:52.320 --> 00:36:55.190
it sees a tower just down the road. And
00:36:55.200 --> 00:36:57.750
that S2D capability is going to be a
00:36:57.760 --> 00:37:00.950
gamecher in uh the rural parts of the
00:37:00.960 --> 00:37:05.910
West. And um and it is so important that
00:37:05.920 --> 00:37:08.310
um technology such as yours and public
00:37:08.320 --> 00:37:11.270
safety that we have access to it. U
00:37:11.280 --> 00:37:13.190
Chuck Dow who's one of the four horsemen
00:37:13.200 --> 00:37:15.670
that founded First Nat, he always he
00:37:15.680 --> 00:37:18.790
he's fond of saying uh in public safety
00:37:18.800 --> 00:37:20.630
they won't work use it unless it works
00:37:20.640 --> 00:37:23.510
every time. Um and and that's right. I
00:37:23.520 --> 00:37:25.430
mean nobody has a gun that shoots every
00:37:25.440 --> 00:37:27.270
other time. They go get something more
00:37:27.280 --> 00:37:29.750
reliable. So, I think, you know, it's
00:37:29.760 --> 00:37:31.589
going to be critical that we continue to
00:37:31.599 --> 00:37:34.150
evolve. We continue to support companies
00:37:34.160 --> 00:37:36.630
like yours uh and FirstNet that are
00:37:36.640 --> 00:37:39.829
bringing this uh into our profession.
00:37:39.839 --> 00:37:41.990
And I just want to thank you on behalf
00:37:42.000 --> 00:37:45.190
of public safety for the risks you take
00:37:45.200 --> 00:37:47.510
uh the invest investment you're making
00:37:47.520 --> 00:37:50.710
because this really does uh touch
00:37:50.720 --> 00:37:52.790
firefighter safety. It touches the
00:37:52.800 --> 00:37:54.710
safety of the citizens we serve. and
00:37:54.720 --> 00:37:57.990
Chief Z, thank you as always uh for for
00:37:58.000 --> 00:38:00.390
your leadership and your guidance. Um I
00:38:00.400 --> 00:38:01.910
don't know what we'd do without you
00:38:01.920 --> 00:38:03.829
staying in this game. So, thank you.
00:38:03.839 --> 00:38:05.910
Well, thank you, Tablet Command. Thanks
00:38:05.920 --> 00:38:07.670
for joining us today on Catching
00:38:07.680 --> 00:38:10.680
Wildfire.