Laserfiche WebLink
Attachment A - Joint Agreement for 800 MHz CCCS <br />Page 39 of 83 <br />Establishes the policy to ensure the System's operational integrity and security by providing <br />users with a procedure for reacting to incidents of missing, lost or stolen radio units. <br />Each agency shall develop internal guidelines for dealing with incidents of lost, stolen or missing <br />radio equipment, to include notification to the Lead Agency. <br />Technical Background <br />The System's controller provides individual access to the System for each assigned radio. The <br />controller prlides the ability to disable the radio altogether with the inhibit' feature. <br />The target radio must be turned on and affiliated with the System for the actions to be <br />processed. If the target radio is not active, the requested action can be put into the passive <br />mode. When the target radio does attempt to affiliate with the System, the pending action is <br />initiated. <br />Operational Context <br />All agencies are required to make immediate notification to the Lead Agency upon receiving <br />information, notification, or recognition that an assigned radio is misplaced, lost or stolen. Delay <br />in providing notification could result in unauthorized persons causing interference and/or <br />receiving confidential information. <br />Protocol/Standard <br />The Lead Agency shall be immediately notified of the situation by a phone call and submission <br />qfa Lost/Stolen Radio Report Form. <br />The request to inhibit a lost/stolen radio must be specified on the Lost/Stolen Radio Report and <br />must be accompanied by a copy of the Police report. <br />Lost and stolen radio information will be passed on to user agencies and local radio shops in <br />case the radio is located or turned in. <br />The Lead Agency will invoice the agency for the replacement cost of the radio if owned by the <br />Lead Agency (ie., a loan pool radio). <br />Management <br />The Lead Agency is responsible for managing this policy. <br />4.8 System Management Access <br />Purpose or Objective <br />Defines the types and areas of individual access to the management functions of the System. <br />Technical Background <br />Every login user of the System has a minimum of one login account and possibly more if <br />multiple levels of access rights are needed for different purposes, such as administrative or <br />general use. Every account can be individually set with the security and application rights <br />needed to meet the needs of each user. All user account IDs shall be unique as the System's <br />