Training at DCHSEMA #NatlPrep

Busy Monday morning instructing at the District of Columbia Homeland Security and Emergency Management.

I’m just glad to see so many partners in public safety participating.

csubtsmw8aefkdl

Trust me, I’m glad to be instructing in the Emergency Operations Center too.

csubtsnxgaa6a0x

So many resources here like a busy 9-1-1 call center, Watch Desk, 3-1-1 call center, and Fusion Center.

calltakergroundfloor

Training and education will help everyone work cohesively together in an emarrrrrrrrrrrrrgency.

Happy #TalkLikeAPirateDay too.

@rusnivek

 

This kind of parking is unacceptable #Chicago #Fire #Police

One thing that bothers me is idiots who park in front of a hydrant.

IMG_4810

Not like 30-seconds, but more like hours and hours and hours.

THIS IS A BLATANT DISREGARD FOR SAFETY!

IMG_4811

So I called my friends at Chicago Fire Engine-35, Truck-28, Ambulance-62, Battalion-17 who advised that I call Chicago Police and inform them.

IMG_4844

So I did. Chicago Police promptly showed up and ticketed the car. #booya

IMG_4847

Hey Jagoff – enjoy your $150 ticket #0964100A (Within 15′ of fire hydrant).

Then a tow truck (hook) showed up and made my night because….

IMG_4848

…I now have full hydrant access again.

Hey Jagoff! Now enjoy your $150 charge for towing your vehicle and $20 storage fee.

Expensive night out for your blatant disregard of public safety. Hope it was worth it.

Friendly reminder to anyone: Don’t park in front of fire hydrants. Ever.

@rusnivek

 

Technical jargon and giving actionable information Safety-PIO-SM-14-006

14-006: Technical jargon and giving actionable information
Agency: Chicago Fire Department Topic(s): Industry codes / Actionable info
Date: Fall 2014 Platform: Twitter

Industry speak or technical jargon is part of what we do every day. But using technical terms on a social media platform will be confusing to those who are NOT in the fire service. That’s what the Chicago Fire Department did yesterday at their big 3-alarm fire when they tweeted technical jargon.

imageaimage

The use of technical jargon is rampant in emergency services but when speaking to the media or the general public, we need to remember that everyone did not grow up with a VOX alarm or SCU tones. In this case, a “311” or 3-11 alarm means that there are 11 engines, 5 Trucks, 2 Tower Ladders, 6 Battalion Chiefs, 1 Rescue Squad, 2 Ambulances, 2 Paramedic Chiefs, Deputy District Chief, Deputy Fire Commissioner, and the 1st Deputy Fire Commissioner are onscene. There is no way to include all that information in a tweet, but using more simple terms will help your audience understand the scale of your ongoing incident.

Before you post images, make sure your pictures are rotated correctly. I know accuracy is sometimes overlooked in lieu of speed, but it takes less than 5 seconds to orientate/rotate a picture (In this case, it was going to be a long operation). And note, by just rotating a picture does not equate that you are “doctoring up” photos. But a correctly posted photo will help media repost and format your information quicker to the masses.

During an emergency situation, your constituents need the information pushes to be actionable and specific to your audience. Not only inform them of the danger, but tell them what they can do about it.

A more effective tweet could have read:

Chicago Fire: Large 3-alarm fire at Harrison St x Fifth Ave. Traffic delays-avoid the area. (insert two pictures)

By phrasing it this way:

  1. You cite the authority having jurisdiction and established incident command presence.
  2. You generally described the size/category of the ongoing incident and critical information to media.
  3. You identify the exact location of the incident.
  4. You describe the delays in the area and give actionable information to your constituents.
  5. You still have lots of room to push properly orientated pictures with your informational tweet.

 

Time is valuable, so tweet good stuff.

@rusnivek

***To download this as a single-page printable format, click this file:

TechnicalJargonAndGivingActionableInformation-Safety-PIO-SM-14-006