My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Item 11 - Joint Agreement with OC for the 800MHz Countywide Coordinated Communications System (CCCS)
Clerk
>
Agenda Packets / Staff Reports
>
City Council (2004 - Present)
>
2022
>
02/01/2022 Special and Regular & HA
>
Item 11 - Joint Agreement with OC for the 800MHz Countywide Coordinated Communications System (CCCS)
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
4/3/2024 4:17:52 PM
Creation date
8/16/2023 12:06:32 PM
Metadata
Fields
Template:
City Clerk
Doc Type
Agenda Packet
Agency
Clerk of the Council
Item #
11
Date
2/1/2022
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
88
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).
View images
View plain text
Attachment A - Joint Agreement for 800 MHz CCCS Page 55 of 83 <br />Technical Background <br />The Fleetmap is parameter information programmed into the System infrastructure and into the <br />subscriber radios to control how those radios perform on the System. <br />The Fleetmap spreadsheet is a documented matrix of the talkgroups in the System and the <br />departments or agencies that use and control user access to these talkgroups. The Fleetmap <br />contains the following information: <br />• Talkgroup Name — Name of the talkgroup as it is programmed into tho System. <br />• Talkgroup Alias — Abbreviated naming of the talkgroup to fit within thl 8 or 14 character <br />radio display. <br />• Talkgroup ID — Numerical designation of the talkgroup in decimal and/or hexadecimal. <br />• Failsoft Channel — The System channel designated for the talkgroup when in the failsoft <br />mode. <br />• Owner — The primary user agency with access control of the talkgroup. <br />• Priority — Priority level of the talkgroup. <br />• On Console — If the talkgroup is available as a console resource. <br />• Trunked Alternate — A talkgroup to be used when the user's primary system is <br />unavailable. <br />Operational Context <br />The Lead Agency will establish and manage the Fleetmap database information for all users of <br />the System. <br />Protocol/Standard . <br />A detailed matrix is maintained by the Lead Agency on the System database. Each agency's <br />radio representative maintains a Fleetmap spreadsheet containing data on their talkgroups and <br />the users for whom they are responsible. <br />Procedure <br />If an individual agency desires to make updates and changes to their Fleetmap standards, the <br />changes shall be requested through the Lead Agency. <br />• The Lead Agency will evaluate any requests for changes and conduct an analysis to <br />determine its feasibility and impact on the System. <br />• The Lead Agency will decide if the request will be approved or denied and proceed <br />accordingly with notification to the requesting agency. <br />The disclosure of the Fleetmap configuration information, including talkgroup IDs, user IDs, <br />user privileges and other related System information could substantially jeopardize the security <br />of the System. This disclosure makes it more susceptible to sabotage and unauthorized access <br />to the contents of confidential voice and data communications. Therefore, the master Fleetmap <br />data shall be classified as `Restricted Information' and is not available to the general public <br />except by formal written request to the 800 MHz CCCS Governance Committee. <br />Management <br />
The URL can be used to link to this page
Your browser does not support the video tag.