General Rules and Guidelines:

*** New with IA Dispatching: Feed Links *** With the new IA system release a dispatcher can now add a link to where a feed is broadacsting the incident online. The following rules apply:

a. Feed can be with any system or service.
b. Link added must go to the feed directly or to information on how to access the feed.
c. Any advertisements posted for sake of - users will be banned from entire IBN system and RH servers.
d. Any links posted that direct to a file other than .mp3 will be banned from the entire IBN system and RH servers.
e. If you post Icecast or TS3, TS2 it the link will go to a page describing how to get to IBN services

IBN DISPATCH - INCIDENT 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 Incident Alerts CAD alerts is to come from actual received radio transmissions, heard directly or via IBN TeamSpeak.** IBN / IA 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 freindly and user freindly system

== 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 OK)

a. confirmed working fire
b. reported structure fire with multiple calls
c. reported structure fire with smoke showing
d. multiple alarms
e. occupant entrapment
f. exposure risk to other nearby structures
g. collapse
h. mutual aid companies requested to the scene (not put on standby)
i. burn/smoke inhalation victim(s)
j. hazmat involvement
k. significant sized field or brush fires
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
c. stabbing w/ victim(s)
d. armed robbery
e. violent assault
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
i. armed hostage or barricade situations
j. officer shooting/officer needs help
k. foot or vehicle pursuit (give reason why actor 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
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
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
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
6. NO ALERTS IN ALL CAPS PLEASE
7. Do not post delayed or old alerts (in progress, occurring incidents only)
8. No Test Alerts.

9. Major weather alerts will be permited, 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. If you have any questions about sending incident alerts, please contact the IBN / IA Support Team by using the "Submit Support Ticket" link under 'HELP', and select "Submit an IA Support Ticket". We will be happy to answer any questions you may have.

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

1) Per IBN 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) Do not send multiple alerts on the same incident. Use the "EDIT" link in Manage My Notifications to add any new updated information to the existing alert. Only important updates should be added.
4) Please be sure to remove your alert(s) from the system once it is obvious that they have expired with regard to the incident. Click the 'ARCHIVE' link under the alert that you wish to remove. This takes the notification off of the active list and moves it into the searchable alert database.
5) Absolutely NO SPAMMING will be tolerated. All alerts must be active incident related. Do not post URL web links or email addresses in alerts. All alerts are monitored and recorded. Any dispatchers who are found to have sent SPAM using the IBN Dispatch system will have their subscriptions immediately revoked, and will be permanently BANNED from the IBN System.

We hope you find these guidelines helpful in making the IBN DISPATCH incident alert system an easy to use and fun way to share your active incidents with other IBN Members and IBN TeamSpeak listeners.

Thank you! for being part of the IA Dispatch team.