My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Res 2005-123
San-Marcos
>
City Clerk
>
03 Resolutions
>
2000 s
>
2005
>
Res 2005-123
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
5/23/2006 11:21:40 AM
Creation date
5/23/2006 9:47:44 AM
Metadata
Fields
Template:
City Clerk
City Clerk - Document
Resolutions
City Clerk - Type
Agreement
Number
2005-123
Date
9/6/2005
Volume Book
163
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
36
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Show annotations
View images
View plain text
<br />· Use of the interoperability channels shall be limited to their designated purpose of <br />coordination between emergency response agencies and resources. Such coordination <br />may occur during routine operations, en-route travel, or on-incident. <br /> <br />· The interoperability channels should not be used for routine dispatch operations, but may be <br />used for routine and en-route communications in accordance with local and regional policies <br />and procedures. <br /> <br />. Use of the interoperability channels shall be prioritized: <br /> <br />1. Emergency or urgent operation involving imminent danger to life or property <br /> <br />2. Disaster or extreme emergency operation requiring extensive interoperability and <br />inter-agency communications <br /> <br />3. Special event, generally of a pre-planned nature <br /> <br />4. Joint training exercises <br /> <br />5. Inter-agency and en-i"oute communications in accordance with local and regional <br />policies and procedures. <br /> <br />· Use of the interoperability channels for on-incident communications shall be in accordance <br />with an Incident Communications Plan established by the on-scene incident commander. <br />The controlling agency for an incident shall, through its incident commander, assign and\or <br />reassign interoperability channels for each operational period as required to support incident <br />operations. <br /> <br />· Radio communications procedures consistent with the National Incident Management <br />System (NIMS) and Incident Command System (ICS) shall be implemented, including: <br /> <br />o Use "plain language" without 10-codes or agency-specific codes/jargon <br /> <br />o Use the calling order, "Agency-Unit #, this is Agency-Unit #" calling order, rather <br />than "Unit # to Unit #" <br /> <br />Example: "Bryan 1605 this is Tyler 2102" or "Incident Command this is DPS 505 <br /> <br />· Interoperability channels shall be used only for voice traffic. Paging, DTMF signaling and <br />SCADA operations are not permitted on interoperability calling or tactical channels. The <br />transmitters arrdtorreceivers in tempurary base stations and repeaters/mobtle reiays shatl <br />not be enabled, disabled or muted by any over-the-air signaling device (selective or DTMF <br />signaling, etc). <br /> <br />· To alleviate confusion, the standard channel names listed in this plan should be used in all <br />equipment to refer to individual channels. Radios not capable of displaying alphanumeric <br />channel labels should be placarded to indicate the channel names and their corresponding <br />positions on the radio's channel selector switch. <br /> <br />· All mobile and portable radio equipment should employ a time-out timer set to limit <br />transmission duration to a period of no greater than 120 seconds (2 minute). <br /> <br />· User-initiated telephone interconnect, e.g. phone patch, on the interoperability channels is <br />not permitted. <br /> <br />Co-Channel and Adjacent Channel Interference <br /> <br />The statewide interoperability channels and CTCSS tones are designated statewide under this plan <br />and thus co-channel interference is possible. Given adequate geographic separation, coordinated <br /> <br />5 <br />
The URL can be used to link to this page
Your browser does not support the video tag.