Micah Choquette:
Stupid question time: someone please explain to me what the tfdd.co app actually does. I see a dispatch log, but I understand that it also sends a text message if you register? Is it more beneficial for the guys out at the firehouse or the guys in the newsroom? I don't mean to sound cynical, as I actually think it's a cool thing, but I'm having a hard time coming up with a way to explain it to someone who's never seen it before and wasn't at the presentation.
John Whitlock:
Definitely needs an about page. Here's how I understand the current situation:
Like many communities, Tulsa has central emergency dispatching. When someone calls 911, the operator gets the details of the incident, including name and address, and enters it into the system. There is a Tulsa Fire Department dispatcher listening in on the call, as well as a Police and EMS dispatcher. If it sounds like it is in the TFD's wheelhouse, the dispatcher may make initial radio contact with the likely station, while entering data into their own system. When they do decide to dispatch the call, the details are sent over a radio modem, and then they repeat the dispatch by voice.
Often, the fire fighting crew is already in motion from the initial voice contact. The data dispatch will print the details to an attached printer, as well as turn on the station lights and alarm and open the garage door. The details include a map page, which directs them to a specific section of a printed binder with streets and hydrant locations (curated by the city).
Sometimes, they don't wait for the printout, but get the details read over the radio. One of the fire fighters scanned the map book as a set of PDFs and put it on his iPad, so he could more easily access the map. This gave one of the chiefs the idea for the project - what if the fire fighters and others in the TFD could get the dispatches on their mobile devices? What if it was easy to get dispatch data to the reporter that just called about the truck zooming by?
Our project uses a RaspberryPi to get this dispatch data onto the web. The printer was disconnected, and the device connected in its place. Every station gets and prints the same dispatches - we used a radio at a training facility where the printer was usually turned off anyway. Once we have the data, we send it over the center's wifi to the tfdd.co server. We parse out the unit w/o interpreting them - TFD insiders know that E21 is station 21's EMSA unit, L21 is their ladder truck, SQ21 is usually a truck, and C641 is one of the chiefs. We send an SMS and email for the incident, and update the website.
The RaspberryPi, wifi equipment, and cables are donated by devs. http://tfdd.co is hosted in Isocentric, which is donating the hosting and bandwidth. Google is sending the emails, and Luke Crouch's Twillio account (topped up with some donated credits) is sending the SMS.
From TulsaWebDevs FB conversation:
Micah Choquette: Stupid question time: someone please explain to me what the tfdd.co app actually does. I see a dispatch log, but I understand that it also sends a text message if you register? Is it more beneficial for the guys out at the firehouse or the guys in the newsroom? I don't mean to sound cynical, as I actually think it's a cool thing, but I'm having a hard time coming up with a way to explain it to someone who's never seen it before and wasn't at the presentation.
John Whitlock:
Definitely needs an about page. Here's how I understand the current situation:
Like many communities, Tulsa has central emergency dispatching. When someone calls 911, the operator gets the details of the incident, including name and address, and enters it into the system. There is a Tulsa Fire Department dispatcher listening in on the call, as well as a Police and EMS dispatcher. If it sounds like it is in the TFD's wheelhouse, the dispatcher may make initial radio contact with the likely station, while entering data into their own system. When they do decide to dispatch the call, the details are sent over a radio modem, and then they repeat the dispatch by voice.
Often, the fire fighting crew is already in motion from the initial voice contact. The data dispatch will print the details to an attached printer, as well as turn on the station lights and alarm and open the garage door. The details include a map page, which directs them to a specific section of a printed binder with streets and hydrant locations (curated by the city).
Sometimes, they don't wait for the printout, but get the details read over the radio. One of the fire fighters scanned the map book as a set of PDFs and put it on his iPad, so he could more easily access the map. This gave one of the chiefs the idea for the project - what if the fire fighters and others in the TFD could get the dispatches on their mobile devices? What if it was easy to get dispatch data to the reporter that just called about the truck zooming by?
Our project uses a RaspberryPi to get this dispatch data onto the web. The printer was disconnected, and the device connected in its place. Every station gets and prints the same dispatches - we used a radio at a training facility where the printer was usually turned off anyway. Once we have the data, we send it over the center's wifi to the tfdd.co server. We parse out the unit w/o interpreting them - TFD insiders know that E21 is station 21's EMSA unit, L21 is their ladder truck, SQ21 is usually a truck, and C641 is one of the chiefs. We send an SMS and email for the incident, and update the website.
The RaspberryPi, wifi equipment, and cables are donated by devs. http://tfdd.co is hosted in Isocentric, which is donating the hosting and bandwidth. Google is sending the emails, and Luke Crouch's Twillio account (topped up with some donated credits) is sending the SMS.