UEA/EC911 Incident Alert System
UEA/EC911 Incident Alert System Chat
PM: Public
Top 10 Dispatchers
Dispatched
UEA03 405
UEA01 92
SWAT04 76
UEA09 70
T-AR12 66
UEA02 48
EC704 36
UEA07 29
NJ300 6
T-CT103 5
SWAT05 4
TX101 4
UEA-Test 2
NC805 2
UEA06 1
T-SC011 1
Co-Dispatched
T-AR12 85
EC704 75
PA02 55
@NYCFireWire 54
UEA07 34
#Tampa&Beyond 33
@EastCoast911IA 29
@NYScanner 26
NEFN 20
UEA01 16
NEID 13
UEA09 11
SWAT05 7
GA155 7
SWAT04 6
T-CT103 5
@DAVERY37 5
@DFWScanner 4
UEA02 4
NJ300 4
SCONFire 3
VAFireNet 3
UEA04 3
PA81 2
EALERTSPA 2
UEA03 2
@WichitaIncident 2
@CJFireBuffs 2
PA424 1
OHBN 1
UEA06 1
D2-USFG 1
@NatEmerAlerts 1
SNNJ 1
NY67 1

General Rules and Guidelines:


USEmergAlerts DISPATCH - Reporting & ALERT DISPATCHING CRITERIA

Please refer to this list of incident alert guidelines before sending your alerts. This list is only intended to assist in keeping alerts simplified and accurate. 

All information contained in UEA CAD alerts is to come from actual received radio transmissions, heard directly from their own radio / scanners, via an online broadcast, or verified reliable news media sources.  

UEA reserves the right to refuse, or ban any dispatcher or person that has / or is causing problems on our network in order to keep this a family friendly and user friendly system. 

USEmergAlerts does not condone taking and redistributing reports from paid/for profit notification services(Example, IPN, 1RWN, BNN Etc...). HOWEVER - We are not against users reporting through our system and then redistributing their posts onto other systems - AS LONG as it was something they heard or saw / owned. This is your own alert and not someone elses.

== MVA INCIDENT GUIDELINES ==
Alert on MVA's with one or more of the following conditions:

a. fatalities
b. serious or multiple injuries
c. entrapment
d. ejection
e. request for ALS medic unit
f. air medevac launched to LZ for patient transport
g. vehicle on fire
h. causing significant road closure
i. involving PD, FD and/or EMS Units
j. involving Major Transportation (e.g. Mass Transit Bus or Commuter Train)
k. vehicle vs. vehicle
l. vehicle vs. structure
m. vehicle vs. pedestrian

== FIRE INCIDENT GUIDELINES ==
Alert on Structure Fires with one or more of the following conditions:
(Alerts with units enroute but not on scene are not pagable)

a. confirmed working fire
b. structure fire with multiple calls(after being confirmed by unit's o/s)
c. structure fire with smoke showing
d. multiple alarms
e. occupant entrapment
f. exposure risk to other nearby structures
g. collapse/partial collapse
h. mutual aid companies requested to the scene (not put on standby, and cannot be paged soley as an update. must have additional fire info for paging also.) 
i. burn/smoke inhalation victim(s) 
j. hazmat involvement 
k. significant sized field or brush fires(Normally 1 acre or more)
l. brush fires endangering vehicle(s) and or structure(s)
m. aircraft or other large vehicle crash with fire
n. search and rescue ops

== POLICE INCIDENT GUIDELINES ==
Alert on Police Incidents with one or more of the following conditions:

a. shooting w/ victim(s)
b. shots fired (Confirmed with shell casings, or Witnesses giving firsthand information on the shots fired)
c. stabbing w/ victim(s)
d. armed robbery
e. violent assault(WE DO NOT SEND SEXUAL ASSAULTS!!!!!!!!)
f. civil disturbance of a large or serious nature 
g. bomb incidents (non-explosion situations should have evac in progress & bomb squad activation)
h. SWAT team deployed(DO NOT PAGE W/ADDRESS)
i. armed hostage or barricade situations(DO NOT PAGE W/ADDRESS)
j. officer shooting/officer needs help(DO NOT USE COMPLETE ADDRESS)
k. foot or vehicle pursuit (give reason why suspect is wanted if known) 
l. larger scale search and rescue efforts (give reason for search if known) 
m. police helo deployed
n. search and rescue ops
o. amber alerts(NOT A MISSING PERSON REPORT. AMBER ALERT MUST BE ISSUED)
p. never post any victim's names or any other personal information involved in an incident (please, no known suicides)
q. do not post any information that would compromise officer safety in any way

== ADDITIONAL NOTES ==

1. Do Not Post Automatic Fire Alarms

2. No known 'pot of food on stove' or 'bad cook' calls unless later declared a working fire by command o/s W / Extentionto the house, or walls.

3. Do not attempt to list every piece of equipment responding to an alarm, as it consumes the limited character count of the alert message.  (Use Units, Srvs, FD / PD etc...)

4. No routine EMS calls, i.e. Cardiac Arrest, Difficulty Breathing, General Sickness, Lift Assists or Transfers, etc. 

5. Remember character count is limited so please (clearly!) abbreviate whenever possible.  Keep to the 3 Line rule when it comes to the indicent DETAILS.  If the detail area is more then 3 lines in CAD, your alert will most likely be cutt off.

6. Do not post delayed or old alerts greater then 20 mins. (in progress, occurring incidents only if possible)

7. No Test Alerts unless auth. by an admin to do so.

8. Major weather alerts will be permitted, however not repeated updates. Please use common sense in judging which alerts should be posted and how. They should be interesting, newsworthy and/or priority type events, not routine occurrences. 

9. Zello Communications:  It is not Manditory, but well Advised for all Dispatchers to Download Zello, which can be found in the Google, Blackberry, ITune App Store, as well as Zello.com.  There are however certain rules in regards to Zello Use within USEmergAlerts(UEA).
- All Communications on Official Chanels of UEA must be 100%Confirmed, Acurate Information.
- When Requesting an Incident to be Paged, Dispatcher must Key Up Stating "(Disp ID) to any availible dispatcher to page out a Call"  If a Dispatcher is availible to page, they will Acknolege you, and take your information.
- If you as a Dispatcher, hear a Dispatcher requesting an incident to be paged, and You are availible to page out the call, and you acccept it,  It is now Manditory that you Page out that Call.  If you do not, It is grounds for disciplinary actions up to suspension, and possibly removal from UEA for multiple repeat issues.
- All Information recieved over Zello from Trainees, and or affiliates, Must be Confirmed prior to paging.

If you have any questions about sending incident alerts, please contact the UEA Support Team @ Support@USEmergAlerts.net

============================================================================
CAUTIONS:

1) Per USEmergAlerts rules, we do not permit any information other than actively occurring public safety alerts from our coverage areas to be sent via our dispatch system.

2) The dispatch system is to be used exclusively for in-progress public safety incident alert information.

3) Use the "UPDATE" link in UPDATE INCIDENT tab to add any new updated information to the existing alert. Only important updates should be added. 

4) Absolutely NO SPAMMING will be tolerated. All alerts must be active incident related. Do not post URL web links(unless scene picture, or radio feed) or email addresses in alerts. All alerts are monitored and recorded. Any dispatchers who are found to have sent SPAM using the USEmergAlerts Dispatch system will have their membership immediately revoked, and will be permanently BANNED from the UEA System. 

We hope you find these guidelines helpful in making the USEmergAlerts incident alert system an easy to use and fun way to share your active incidents with other Scanning Hobbyist and online listeners. 

Thank you! for being part of the UEA Dispatch team.
Incoming Tips

Rest In Peace

Ed Senkbeil - UEA08 / SWAT06

USEmergAlerts Administrator

 

 

UEA 24HR TIP HOTLINE

(262) 208-4911

IF YOU ARE A DISPATCHER,

JOIN THE UEA DISP GROUP

CLICK HERE

UEA Dispatcher E-Mail
Sign up/in for Dispatcher E-Mail Accounts @usemergalerts.net