Recommended Protocol/Standard. The detailed matrix will be maintained on the system database. An example of the matrix layout is shown in this manual. Need to develop the matrix layout. Each System Manager will maintain a master Fleetmap spreadsheet containing data on the subscribers for whom they are responsible.
Recommended Protocol/Standard. The Talk Group owner, or the applicable subsystem owner, shall assign Talk Group priority levels not exceeding the level defined by the criteria below. Talk Group priorities that are assigned to level five or above are subject to the review and audit of the RPSCC Radio Sub-Committee.
Recommended Protocol/Standard. Interconnect usage shall only be programmed for the users of the system that have a need for the function, the primary purpose of the system is for radio communications, but there may be some users that may require a backup ability to cellular communications. The priority level for interconnect calls is “10,” this is defined under the priorities standards documents. The interconnect equipment of the system will be configured to use the “overdial” method of operation, where the incoming calls come into a generic phone number, and then the interconnect ID of the radio is entered to complete the call. The Fort Lauderdale radio system does not support inbound interconnection.
Recommended Protocol/Standard. Private call usage will only be programmed for the users of the system that have a need for the function the primary purpose of the system is for radio communications. Site access for private call is managed in the “Sites Profile Group” that the radio user belongs to.
Recommended Protocol/Standard. In order to meet this need the Radio User aliases would be prefixed with an agency identification that would be unique to that agency and would preferably readily identify the agency the Radio User is associated with. Because of the number of agencies using the system the prefix would be a minimum of two alphanumeric characters in length in order to avoid contention between agencies. Regional Operating Agencies and all agencies within the County of Broward would have naming prefixes of at least two digits that would stand alone. Counties would be pre-named with a two digit mnemonic, and the Cities and Agencies of the Counties would be included under the prefix of the County they are in.
Recommended Protocol/Standard. The first two characters of the TG alias identify the talk group governing entity/municipality (see Table 1). The third character identifies the department/agency within the governing entity/municipality (see Table 2). The fourth character will have a dash (-) as a separator. The remaining available characters will be used to complete the talk group alias. It is important to note, depending on the subscriber type and/or model, character display may be smaller or larger. Subscribers units with displays smaller than twelve (12) characters will require condensing the TG name to fit within the display. Any subscriber displays that are under eight (8) characters will be handled, by the Radio System Administrator, on a case by case basis. It is understood that there is currently a wide variety of subscribers out in the field. In addition to this, there are many agencies who still wish to continue to identify zone and channel assignments prior to the TG in the subscriber unit. Even though the concept that the TG’s are to remain consistent from zone controller up to the subscriber is fully supported by Broward County Office of Communications Technology, this may be too big of a challenge to overcome at this time. We have come to the understanding that if the agency wishes to continue to identify zone and channel assignment prior to the TG name in the subscriber, they have this ability if they can leave the TG name consistent, as it appears in the zone controller, as much as possible.
Recommended Protocol/Standard. Use of the Emergency Button as an emergency signaling option should be available to any agency on the radio system, subject to certain conditions and provisions.
Recommended Protocol/Standard. The use of the following codes, which are combined to define the intended pre-authorizations… P = Permission is required to gain authorization for use. A letter of permission must be generated from the System Manager of that agency that wishes to use another agency's Talk Groups for their radio subscribers and/or their Dispatch consoles and this written request must be sent to the System Manager of the system that has ownership of those Talk Groups for their system. D = Defined agencies may share, to be defined in a separate letter. The letter would outline specific purpose talk groups, i.e., only dispatch consoles, only neighboring cities, etc. The letter will be on file with the appropriate System Managers. L = Like agencies may share, “Fire, Medical, Law, Public Works, etc.” A = All agencies. RX = Only authorized to receive. TX = Authorized to transmit and receive.
Recommended Protocol/Standard. Limited Scanning/monitoring privileges may be pre-approved by the affected Talk Group owners and System Managers. Before Scanning of owned Talk Groups, permission must be granted. permission must come from: The System Managers of the sites that are being requested for the Talk Group The jurisdiction/agency who is the “owner” of the requested Talk Group Mutual aid, special roaming and other shared Talk Groups may be Scanned at any time; however, “requested site” determinations will be made by the System Managers of the affected sites.
Recommended Protocol/Standard. The Serial Numbers used in the records for console Operator positions will be formatted according to the following: OPTION 1 Regional Operating Agencies would have naming prefixes of at least two characters that would stand alone. Counties would be pre-named with a two character identifying mnemonic, and the Cities and Agencies of the Counties would be included under prefix of the County they are in. The next three characters would be the letters “con” for console, so as to easily distinguish this identifier from other radio aliases. The characters following these first five are at the individual agency’s discretion. OPTION 2 Starting with a 2 – digit prefix to identify the Console location “for example FL, PB, HL, etc. The next 2 digits represent the CEB number. The following 2 digits indicate the TDM slot on that CEB The last four characters are to be unique, at the individual agency discretion.
