Laserfiche WebLink
Attachment A - Joint Agreement for 800 MHz CCCS <br />Page 60 of 83 <br />word 'FAILSOFT' on the radio display and emit a short high-pitched tone every 10-15 seconds <br />to indicate to the user that normal trunked operation is unavailable. <br />Protocol/Standard <br />It is the policy of the Lead Agency to provide a failsoft assignment for every 'primary' talkgroup <br />on the System to prevent loss of communications for users. Failsoft channel assignments are <br />based on the needs of System users consistent with each user's mission and need for radio <br />communications. <br />The Lead Agency makes determinations concerning Failsoft channel assignments. <br />During a Failsoft condition, dispatchers may need to announce instructions to radio users and <br />remind them that operations may be combined among several agencies and to implement radio <br />discipline to reduce radio traffic. <br />Management <br />The Lead Agency is the responsible authority for failsoft assignments and management. <br />Agencies desiring additional information on failsoft assignments may request the information <br />from the Lead Agency. <br />5.10 Scanning <br />Purpose or Objective <br />Identifies operational procedures and responsible authorities governing scanning System <br />talkgroups. <br />Technical Background <br />The network infrastructure and subscriber units are configured to permit managed user <br />scanning of talkgroups. Including a talkgroup in a non -priority scan list does not necessarily <br />result in the user hearing traffic on that talkgroup. Talkgroups are only active if there is at least <br />one user affiliated who has the talkgroup of interest as their selected channel. <br />Subscriber units can scan a talkgroup, a talkgroup in another zone, or another trunked radio <br />system if compatible. An entire radio can be set up as receive only. <br />Operational Context <br />Scanning by multiple subscriber units can quickly overwhelm a trunked radio system creating <br />system busies. As a result, scanning on the System has been limited to the Fire Services as a <br />legacy feature allowing scanning of their Dispatch Talkgroup and primary tacticals. <br />Protocol/Standard <br />Before scanning and/or monitoring of System talkgroups is allowed, permission must be <br />obtained from the Lead Agency and the agency 'owning' the talkgroup. Scanning must also be <br />approved by the requestor's agency in their template design. <br />Scanning can only be enabled in the programming template by the Lead Agency. <br />