HomeMy WebLinkAboutR-2013-096 Executed a Regional Interlocal Agreement with BC for Cooperative Participation in a Regional Public Safety Intranet that can Support Closest Unit Response in Life Threatening Emergencies RESOLUTION NO. 2013-096
A RESOLUTION OF THE CITY COMMISSION OF THE CITY OF DANIA
BEACH, FLORIDA, AUTHORIZING THE PROPER CITY OFFICIALS TO
EXECUTE A REGIONAL INTERLOCAL AGREEMENT BETWEEN THE
CITY OF DANIA BEACH, FLORIDA AND BROWARD COUNTY,
PROVIDING FOR COOPERATIVE PARTICIPATION IN A REGIONAL
PUBLIC SAFETY INTRANET ("RPSI") THAT CAN SUPPORT CLOSEST
UNIT RESPONSE IN LIFE THREATENING EMERGENCIES; PROVIDING
FOR CONFLICTS; FURTHER,PROVIDING FOR AN EFFECTIVE DATE.
BE IT RESOLVED BY THE CITY COMMISSION OF THE CITY OF DANIA
BEACH, FLORIDA:
Section 1. That the proper City officials are authorized to execute a Regional Interlocal
Agreement between the City of Dania Beach, Florida and Broward County, to provide for a
County-wide interoperable public safety intranet that can support closest unit response in life
threatening emergencies. A copy of the Agreement is attached as Exhibit "A" and it is
incorporated into this Resolution by this reference.
Section 2. That all resolutions or parts of resolutions in conflict with this Resolution
are repealed to the extent of such conflict.
Section 3. That this Resolution shall be in full force and take effect immediately upon
its passage and adoption.
PASSED and ADOPTED on September 10, 2013.
ATTEST:
LOUISE STILSON, CMt WALTEk B. DUKE, III
CITY CLERK MAYOR
11 Is
APPROVED AST O CORRECTNESS:
THO S J ANSBRO 'AAl"Eo
CITY AT RNEY
REGIONAL INTERLOCAL AGREEMENT BETWEEN BROWARD COUNTY AND
THE CITY OF PROVIDING FOR COOPERATIVE PARTICIPATION
IN A REGIONAL PUBLIC SAFETY INTRANET
This Regional Interlocal Agreement ("Agreement') is made and entered into by and between
Broward County("County"), a political subdivision of the State of Florida, and City of ("City"), a
Florida municipal corporation (collectively City and County referred to as the "Parties") providing for
cooperative participation in a Regional Public Safety Intranet("RPSI").
WHEREAS, this Agreement is entered into pursuant to§163.01, Florida Statutes, also known as
the"Florida Interlocal Cooperation Act of 1969"; and
WHEREAS, County is to establish, with cooperation of Broward cities, a county-wide
interoperable public safety intranet that can support closest unit response in life-threatening emergencies
and regional specialty teams; and
WHEREAS, the Parties desire to satisfy the intentions of the Broward County Charter by insuring
that someone with a life-threatening emergency receive care from the closest available emergency
vehicle;and
WHEREAS, the City agrees to work towards insuring someone with a life-threatening emergency
receive care from the closest available emergency vehicle, including pursuing automatic aid agreements
with neighboring cities who utilize the county-wide CAD system; and
WHEREAS, the Parties desire to enhance radio interoperability by interconnecting County and
City public safety radio users and to enhance information sharing by interconnecting County and City
public safety data users; and
WHEREAS, County maintains a Trunked Radio System, Computer Aided Dispatching ("CAD")
System, Automated Vehicle Location ("AVL") System, a Law Records Management System ("LRMS"),
and a Fire Records Management System ("FRMS") as part of its public safety intranet that supports
county-wide police, fire, and emergency services; and
WHEREAS, the Parties desire to make the most efficient use of their technical resources to
enable the Parties to cooperate with each other to provide quality county-wide public safety
communication services;
NOW, THEREFORE, IN CONSIDERATION of the mutual covenants and promises, set forth, the
Parties agree as follows:
ARTICLE 1
DEFINITIONS
1.1 Advanced Tactical Mapping ("ATM"): A component of the RPSI that provides computer aided
dispatch mapping. In conjunction with AVL, these maps pinpoint the real time location,
availability, status, and routing of emergency vehicles which ultimately enhance response times.
1.2 Automated Vehicle Location ("AVL") System: A component of the RPSI that provides GPS-based
tracking of public safety vehicles. AVL facilitates closest unit response when coupled with a
common CAD platform.
1.3 Board of County Commissioners: The term "Board of County Commissioners" shall mean the
Board of County Commissioners of Broward County, Florida.
Page 1 of 99
1.4 Capital: The term "Capital"shall mean costs for machinery, equipment, vehicles or other tangible
assets that are used in operations and that have initial useful lives extending beyond a single
reporting period. The term shall exclude call-taking and dispatch equipment and other capital
items that are purchased by County pursuant to the provisions of Section 5.03A of the Charter of
Broward County.
1.5 Change Management Requests ("CMR"): The process used to specify the times and conditions
when designated tasks can be performed on all software and hardware affiliated with the RPSI
including but not limited to the Trunked Radio System, Public Safety Network, Computer Aided
Dispatch(CAD) System, E-911, etc. The CMR is more fully explained in Exhibit D.
1.6 Computer Aided Dispatch ("CAD") System: A component of the RPSI that has as one of its
functions, in conjunction with the AVL System,the ability to assist a radio dispatcher in identifying
and dispatching public safety vehicles and personnel closest to the scene of an incident.
1.7 Contract Administrator: County's Director of the Office of Communications Technology.
1.8 County: The term "COUNTY"shall mean the government of Broward County, acting through the
Board of County Commissioners or its designee.
1.9 Demarcation Points: A "Demarcation Point" or "Demarc" identifies a responsibility boundary
between City-responsible items and County-responsible items. Exhibit B further defines and
visually portrays the RPSI Demarcation Points and entity responsibilities on a portion-by-portion
basis.
1.10 Equipment: The County-owned and maintained items listed in Exhibit C and any other County-
provided items.
1.11 Fire Records Management System ("FRMS"): A component of the RPSI that archives fire-related
dispatch records and information.
1.12 Fire Rescue Frontline Vehicles: Vehicles that are typically dispatched in the initial stages of an
incident for the protection and preservation of life, property, and the environment. Vehicles
whose primary purpose is responding to emergencies where time is critical, i.e., Fire Engines
(Pumpers), Ladder Trucks, Medical Rescue Vehicles, and Shift Commanders. Frontline vehicles
are staffed and dispatched and do not include resources held in a reserve or staff capacity.
1.13 Fire Station Alerting: Allows regional and non-regional communication centers to efficiently
respond to emergencies by managing the assets of multiple fire stations. Public Safety Dispatch
Centers can dispatch an engine, ambulance, entire station, or multiple stations by selecting them
on their computer screen or by the push of a few buttons.
1.14 Hosted Master Site: The Hosted Master Site is the central hub for all analog and secure two-way
radio voice processing. The Motorola Hosted Master Site replaced the County owned SmartZone
Controller which was at end of life. The Hosted Master site uses Motorola's SmartX solution
inclusive of analog to digital site converters which will allow the existing SmartZone 3.0 Radio
Network to communicate to a P25 IP platform.
1.15 Law Records Management System ("LRMS"): A component of the RPSI that archives law
enforcement dispatch records and information.
1.16 NetMotion: A component of the RPSI that improves mobile data network performance,
encryption, communication stability, and roaming between disparate private and public wireless
networks.
Page 2 of 99
1.17 Network Mobility Zone ("NMZ"): A component of the RPSI which extends the public safety
network to multiple jurisdictions. The network mobility zone provides the mobile data and remote
facility user's access to the core of the Public Safety Intranet applications.
1.18 Non-Dispatch Facility: A City owned facility hosted by the infrastructure, applications, and
services of the RPSI. A non-dispatch facility does not receive E-911 calls nor does it provide
City-wide or county-wide dispatch services. A non-dispatch facility may require access to FRMS,
Read-Only CAD Services, and PMDC via their owned and operated Local Area Networks. The
City-County demarcation boundaries are outlined in Exhibit B.
1.19 Non-Regional Dispatch Center ("NRDC"): A cooperative dispatch center providing E911 call
taking and dispatch services for a municipality. A NRDC is also hosted by the infrastructure,
applications, and services of the RPSI. A NRDC supports the overall goals of closest unit
response, radio interoperability, and data sharing and utilizes the Regional CAD and County-
Wide Radio System. The County will be solely responsible for designating each qualifying
dispatch center as a NRDC based upon the dispatch center's participation in the regional system.
Upon such written designation by the County, the dispatch center will qualify as a NRDC under
this Agreement unless and until the County otherwise designates in writing or the Agreement is
otherwise terminated.
1.20 Peripheral Equipment: The City-owned and maintained items listed in Exhibit C and any other
City-provided items. Peripheral equipment includes but is not limited to Ethernet cabling, mouse,
keyboard, speakers, printers, etc.
1.21 Project: The integration of a regional public safety intranet comprised of radio and data systems,
benefiting public safety agencies within Broward County that choose to participate.
1.22 Project Charter: Outlines the requirements, direction, constraints, and collectively accepted
deliverables within a project. In addition, the charter will act as a guideline for the project
manager and project team members to establish scope, schedule, and cost pertaining to the
Project. The Project Charter template is further explained and listed in Exhibit E. Upon written
confirmation by both parties, the completed Project Charter(including any subsequent updates by
the parties) shall be automatically substituted and incorporated herein and shall operate as
Exhibit E to this Agreement.
1.23 Project Manager: An employee of the County who is assigned by the Contract Administrator to
provide day-today management of the Project from inception to completion.
1.24 Public Safety Network ("PSN"): A component of the RPSI which provides the communication
connectivity and network infrastructure for data portions of the RPSI.
1.25 Regional Dispatch Center ("RDC"): A cooperative and consolidated dispatch center providing
E911 call taking and dispatch services for multiple jurisdictions. A RDC is also hosted by the
infrastructure, applications, and services of the RPSI. A RDC supports the overall goals of
closest unit response, radio interoperability, and data sharing and utilizes the Regional CAD and
County-Wide Radio System. The County funds the personnel and operating expenses
associated to a regional dispatch center. The County will be solely responsible for designating
each qualifying dispatch center as a RDC based upon the dispatch center's participation in the
regional system. Upon such written designation by the County, the dispatch center will qualify as
a RDC under this Agreement unless and until the County otherwise designates in writing or the
Agreement is otherwise terminated.
1.26 Regional Public Safety Intranet ("RPSI"): The overall collection of Equipment — including but not
limited to County's Trunked Radio System, Public Safety Network, and Public Safety Applications
Page 3 of 99
— that constitutes the Regional Public Safety Intranet. City-owned equipment interfaces to the
County-owned RPSI.
1.27 Service Level Agreements ("SLA"): Defines an expected level of service segregated into various
categories: System performance, trouble resolution, operations, and administration. The Service
Level Agreements are further explained and listed in Exhibit F.
1.28 SmartZone: A component of the RPSI that interconnects disparate radio systems to provide
county-wide coverage for roaming, efficient use of channels, and voice communication
interoperability.
1.29 Subscriber Maintenance: Refers to City's responsibility to maintain the City owned users
equipment. Subscriber maintenance is further explained in Exhibit B.
1.30 System Maintenance: Refers to County's responsibility to maintain the regional public safety
intranet(RPSI) as described in Exhibit B.
1.31 Trunked Radio System: County's Trunked Radio Communications System, a major portion of
which is used by police and fire rescue personnel within Broward County. County currently owns
and operates a twenty-eight(28)channel 800 MHz trunked simulcast SmartZone radio system.
ARTICLE 2
SCOPE OF WORK
2.1 County and City agree to install the necessary Equipment and Peripheral Equipment and perform
their respective required tasks in accordance with the Statement of Work(Exhibit A).
2.2 The work to be done shall be referenced, for convenience, according to the project designations
and as further identified and detailed in the Exhibit A Statement of Work.
2.3 County agrees that the Trunked Radio System will meet appropriate coverage, functionality, and
availability parameters and accepted industry standard levels of performance as determined by
Federal Communications Commission (FCC), Telecommunications Industries Association (TIA),
and Association of Public Safety Communication Officials (APCO) standards together with
manufacturers' specifications.
2.4 County shall own all Equipment the County supplies to City pursuant to this Agreement.
2.5 City shall provide County access to the City's equipment rooms to the extent required for the
installation of the County-owned equipment and integration of any applicable City system into the
RPSI. City will exercise due care to ensure that the electrical, security, and environmental
requirements are maintained for such equipment rooms.
2.6 County agrees that the CAD, AVL, FRMS, LRMS, Mobility Zone, and Public Safety Network
functionalities supplied to City shall also meet appropriate performance levels as defined in
Exhibit F.
2.7 The Regional Public Safety Intranet will perform based on the specifications of any given
application being run on the system as defined in the Exhibit A (Statement of Work). The RPSI
shall allow for exchange of information amongst public safety users.
2.8 City shall be responsible for supplying County with needed unintenvptible power system (UPS)
electrical power, electrical wiring, heating ventilating and air conditioning (HVAC), and standby
power generation to meet manufacturer guidelines and operational standards established by
County for dispatch center Equipment.
Page 4 of 99
2.9 City agrees to allow County, with notice to City and monitoring by City personnel, to assist in
troubleshooting a City local area network (LAN) which adversely impacts the Regional Public
Safety Intranet. City agrees to correct any problems found in an expeditious manner.
2.10 City agrees to comply with the Demarcation Point division of responsibilities for the RPSI as
provided in Exhibit B.
2.11 County shall maintain all systems outlined as "County responsibility" in Exhibit B over the life of
this Agreement.
2.12 City shall maintain all systems outlined as "City responsibility" in Exhibit B over the life of this
Agreement.
2.13 County shall not be responsible for the payment of any taxes, insurance, and utilities for City
owned facilities.
2.14 Access to City's facilities for County personnel, or County's subcontractors, consistent with City
security practices and procedures, shall be unlimited as to time and day.
2.15 City shall be responsible for any and all maintenance and repairs to the existing City owned
facilities and any upgrades to such facilities. City shall maintain the structural and operational
integrity of all associated City owned facilities and supporting equipment including but not limited
to: batteries, buildings, cable plant, generators, roof, skylights, walls, foundations, sidewalks,
floors, windows, ceilings, sprinkler and hot water systems, elevators, heating systems, air
conditioning systems, plumbing, electrical and all other structural components.
2.16 Prior to the issuance of the Notice to Proceed from the County's Contract Administrator to the
contractor, the Parties shall develop a mutually acceptable Project Plan inclusive of Project
Charter (Exhibit E), project schedule, and communication plan set forth, among other things, (i)
selected tasks, deliverables, and activities required of each party, including all dates by which the
responsible party must complete such activity, (ii) the milestones and the agreed upon date for
completion of each milestone; and (iii) the date for System Acceptance. This development shall
constitute a Detailed Design Review. The Project Schedule shall be in the form of a progress
chart of suitable scale to appropriately indicate the percentage of work scheduled for completion
at any time. Each party represents that it will act in good faith to establish the Project Schedule
within thirty (30) days of a signed contract between the County's Contract Administrator and the
contractor and that the number of days established will be reasonable as to each activity.
2.17 Upon City's concurrence with, and County's acceptance of, the Detailed Design Review and
Project Schedule submitted to County, County will provide contractor with a Notice to Proceed.
2.18 Effective with the execution of this Agreement, City shall become a voting member of the
Regional Public Safety Communications Committee("RPSCC") (or equivalent committee that has
the authority to make technical decisions with regard to major upgrades and configuration
changes to the RPSI) and other applicable governance boards to the extent approved by County.
2.19 City shall follow all RPSI Trunked Radio System policies and standard operating procedures in
place at the time of this Agreement, a list of which are included in Exhibit G, as well as those
developed in the future and issued to City by County. City agrees to comply with any
enforcement actions required by these policies and procedures for misuse or abuse of the RPSI
Trunked Radio System.
2.20 County and City shall jointly be responsible for developing desired fleet mapping and
programming of all subscriber units and system parameters necessary to meet the operational
requirements.
Page 5 of 99
2.21 SmartZone operation shall be limited to public safety users only.
2.22 City acknowledges that the services to be performed under this Agreement, relative to County's
responsibilities, shall be performed by County and/or its contractors and shall be under the sole
supervision and direction of County. At City facilities, City may monitor installation work done by
the County, its employees, agents, and subcontractors. Likewise, County acknowledges that the
services to be performed under this Agreement relative to City's responsibilities shall be
performed by City and/or its contractor(s)and shall be under the sole supervision and direction of
City. County may monitor installation work done by the City, its employees, agents, and
subcontractors.
2.23 City is responsible for Subscriber Maintenance including repair and sub-fleet additions, moves,
and changes to City subscribers as provided in Exhibit B. City may utilize the services of a third
party to provide maintenance of City subscribers, or City may contract with County for a fee for a
combination of the aforementioned services or for all of the above services.
2.24 County shall reprogram all City subscriber radios and control stations for operation on the
County's Trunked Radio System.
2.25 City is responsible for all removals and installations of its subscriber equipment.
2.26 County agrees that it will not implement any changestenhancements to the RPSI that could
adversely affect the City system subscribers unless directed to do so by federal or state
mandates as stated in Section 3.3 of this Agreement or otherwise agreed to, in writing, between
the parties. Prior written notice as defined in Exhibit D shall be made by County to City for
proposed changes and their potential effect on City operations. Should City or County desire to
perform changes to the facility or the RPSI that may impact the Equipment or services provided
by the County, the Change Management Request(CMR)procedures(Exhibit D)will be followed.
2.27 The parties agree that any and all drawings, plans, specifications or other documents or materials
will be reviewed by City and County, or its sub-contractors to ensure that they are: (a) consistent
with the City and County requirements for the Project; (b) sufficiently fit and proper for the
purposes intended; and (c)comply with all applicable laws, statutes, building codes, and City and
County guidelines or regulations, which apply to or govem the Project. City's approval,
acceptance, use of or payment for all or any part of County's services under this Agreement or of
the Project itself shall in no way alter County's obligations or City's rights. Copies of all items
shall be provided to City and County. The Project Charter will be used to identify the
requirements and expectations set forth by City and County.
2.28 In the event that County or City believe that any aspect of a Project is not in compliance with
approved plans or applicable codes, or that work cannot be completed as designated, County or
City shall notify the appropriate other party within the next business day after discovery, in writing
or electronically, as to the reason(s)the proposed portion of the work is not in compliance or not
feasible to meet the scope of services to be provided in this Agreement.
2.29 City agrees to complete a joint Acceptance Test Plan (Exhibit A, Attachment 2) with County to
inspect County's or the contractor's performed work on the System to determine if it meets the
City's operational needs and County's requirements.
2.30 City public safety users shall have equal accessibility to County's RPSI similar to other public
safety agency subscribers.
2.31 City agrees to purchase all necessary City subscriber equipment as described in Exhibit B within
ninety(90)days of the City providing written notice to County exercising its option to participate in
a regional public safety intranet consisting of any one or combination of the following: Trunked
Radio System, CAD,ATM,AVL, FRMS, LRMS, or PSN.
Page 6 of 99
2.32 City agrees to provide County or County's contractor, for the term of the Agreement, with facility
space associated with the on-site maintenance, troubleshooting, and repair of all County
Equipment.
ARTICLE 3
TERM
3.1 The obligation of the Parties to perform under this Agreement shall commence upon the date of
the last party executing this Agreement("Effective Date").
3.2 The term of this Agreement shall be for five (5) years from the Effective Date. This Agreement
may be renewed every five (5) years with the written approval of both County and City, unless
terminated pursuant to Article 4.
3.3 The terms of this Agreement may be amended if a state or federal regulatory agency mandates
significant technological modifications of the system requiring a major reconfiguration or upgrade.
In such instances, the Parties shall meet to determine an appropriate solution and funding. In the
event the parties are unable to reach an agreement regarding state or federal mandates for
technological modifications and/or funding of said modifications, either party may terminate the
Agreement for cause pursuant to Article 4.
ARTICLE 4
TERMINATION
4.1 This Agreement may be terminated by the County or City for convenience upon providing written
notice to the other party at least 365 days prior to the effective date of such termination.
4.2 The failure of the City to perform its responsibilities as set forth herein for a period of thirty (30)
calendar days after written notice by County shall constitute a breach of this Agreement. In the
event the City fails to cure the breach within such thirty(30) day period, County may immediately
terminate this Agreement upon written notice to the City.
4.3 City recognizes that the Board of County Commissioners, Broward County, Florida is the
authority which establishes, allocates or otherwise provides for County's budget year funding. If
in any budget year, funding, for any reason, is not provided to cover the County's responsibilities
and obligations under this Agreement, this Agreement may be terminated by County without
penalty upon written notice to the City.
ARTICLE 6
COMPENSATION
5.1 Section 318.21(9), Florida Statutes, requires that Twelve dollars and fifty cents ($12.50) from
each moving traffic violation must be used by the County to fund the County's participation in an
intergovernmental radio communication program approved by the Department of Management
Services. City understands such revenue generated within its jurisdiction will be used by the
County to help fund the RPSI's operating costs.
ARTICLE 6
ADDITIONAL SERVICES
6.1 It is mutually acknowledged that during the term of this Agreement it may be desirable to change
the scope or extent of the maintenance services or to have County substitute items of Equipment
and/or provide new items of Equipment. The parties also recognize that during the term of this
Agreement, additions, changes, or modifications may be necessary or desirable to carry out the
intent or purpose of this'Agreement. The Parties agree that during the term of this Agreement
Page 7 of 99
they will negotiate in good faith any requested changes to the scope or extent of the maintenance
services or to substitution of items of Equipment and/or provision of new items of Equipment and
other services proposed by County. All requested changes to the scope or extent of the
maintenance services or to substitution of items of Equipment and/or provision of new items of
Equipment, upgrades and other proposed additional services are subject to funding availability.
6.2 Any and all modifications to the terms and conditions of this Agreement must be contained in a
written amendment executed by both parties with the same formalities as set forth herein. Should
City or County desire to perform changes to the facilities, the RPSI or PSN that may adversely
impact the Equipment provided by the County, the Change Management Request (CMR)
procedures(Exhibit D)will be followed.
ARTICLE 7
FREQUENCY USAGE
7.1 City agrees to authorize County, pursuant to state and federal regulations, to integrate City's 800
MHz frequencies into County's public safety intranet for the purpose of building a regional public
safety intranet benefiting public safety agencies within Broward County that choose to participate.
7.2 City agrees to authorize County, pursuant to state and federal regulations, to integrate City's
eligible 700 MHz frequencies into County's public safety intranet for the purpose of building a
regional public safety intranet benefiting public safety agencies within Broward County that
choose to participate.
7.3 City shall continue to maintain its radio frequency license ownership and, therefore, shall comply
with all applicable federal, state and local laws and regulations to maintain such licensure.
7.4 County shall assist City with filing appropriate documents to facilitate County's usage of the 800
MHz frequencies, including documents regarding Federal Aviation Administration (FAA) or FCC
licensure.
7.5 County shall assist City with filing appropriate documents to facilitate County's usage of the 700
MHz frequencies, including documents regarding Federal Aviation Administration (FAA) and/or
FCC licensure.
7.6 County understands and agrees to maintain City radio frequencies (direction and range)
integrated into the County Trunked Radio system(s).
ARTICLE 8
LIABILITY
8.1 City and County shall each individually defend any action or proceeding brought against their
respective agency pursuant to this Agreement and shall be individually responsible for all of their
respective costs, attorneys'fees, expenses and liabilities incurred as a result of any such claims,
demands suits actions damages and causes of action including the investigation or their
9 9 9
defense thereof, and from and against any orders, judgments or decrees which may be entered
as a result thereof.
8.2 City and County agree that no indemnification or hold harmless agreement shall be in effect
concerning any claims, demands, damages and causes of action which may be brought against
either party pursuant to this Agreement. This paragraph does not affect in any way any
indemnification or hold harmless obligations of any third party to City or County under any other
contract, agreement or obligation.
8.3 City and County are "state agencies or subdivisions" as defined in Section 768.28, Florida
Statutes, and agree to be fully responsible for acts and omissions of its agents or employees to
Page 8 of 99
the extent required by law. Nothing herein is intended to serve as a waiver of sovereign immunity
by any party to which sovereign immunity is applicable. Nothing herein shall be construed as
consent by a state agency or political subdivision of the State of Florida to be sued by third
parties in any matter, whether arising out of this Agreement or any other contract.
ARTICLE 9
INSURANCE
9.1 The Parties acknowledge that County is self-insured in accordance with the provisions set forth in
Section 768.28, Florida Statutes.
ARTICLE 10
PERFORMANCE
10.1 Operational Performance Metrics will be provided by County to City on a quarterly basis to
collectively evaluate system integrity. The operational performance metrics will be a part of the
service level agreement provided by County to City and further explained in Exhibit F.
ARTICLE 11
MISCELLANEOUS PROVISIONS
11.1 ASSIGNMENT: County shall perform the services provided for in this Agreement utilizing
County's employees, contractors, and subcontractors. Said services shall be performed
exclusively and solely for City which is a party to this Agreement. City and County shall not have
the right to assign this Agreement without the express written approval of both parties.
11.2 JOINT PREPARATION: The Parties acknowledge that they have sought and received whatever
competent advice and counsel as was necessary for them to form a full and complete
understanding of all rights and obligations herein and that the preparation of this Agreement has
been their joint effort. The language agreed to expresses their mutual intent and the resulting
document shall not, solely as a matter of judicial construction, be construed more severely
against one of the parties than the other.
11.3 SEVERABILITY: In the event any portion or provision of this Agreement is found to be
unenforceable by any court of competent jurisdiction, that provision or portion shall be deemed
severed from this Agreement and the balance of this Agreement shall remain in full force and
effect.
11.4 ENTIRE AGREEMENT AND MODIFICATION: This Agreement incorporates, supersedes and
includes all prior negotiations, correspondence, conversations, agreements or understandings
applicable to the matter contained herein. Specifically, this Agreement supersedes and replaces
in its entirety any prior Agreement Providing for Cooperative Participation in a Regional Public
Safety Intranet Between City and County (or between City and the Broward Sheriffs Office and
assigned by Broward Sheriff's Office to the County). It is further agreed that no change, alteration
or modification in the terms and conditions contained herein shall be effective unless contained in
a written document executed by both parties with the same formality and of equal dignity
herewith.
11.5 COMPLIANCE WITH LAWS: Each party shall comply with all federal, state, and local laws,
codes, ordinances, rules and regulations in performing its duties, responsibilities and obligations
pursuant to this Agreement.
11.6 BINDING EFFECT: This Agreement shall be binding upon and inure to the benefit of the parties
hereto and their respective successors.
11.7 FORCE MAJEURE: Neither party shall be obligated to perform any duty, requirement or
Page 9 of 99
obligation under this Agreement if such performance is prevented by fire, hurricane, earthquake,
explosion, wars, sabotage, accident, flood, acts of God, strikes, or other labor disputes, riot or
civil commotions, or by reason of any other matter or conditions beyond the control of either
party, and which cannot be overcome by reasonable diligence and without unusual expense
("Force Majeure").
11.8 AUTHORITY: The individuals executing this Agreement on behalf of any entity do hereby
represent and warrant that they are, on the date of this Agreement, duly authorized by all
necessary and appropriate action to execute this Agreement on behalf of their principal.
11.9 NOTICES: In order for a notice to a party to be effective under this Agreement, notice must be
sent via U.S. first-class mail with a contemporaneous copy via e-mail to the addresses listed
below, and shall be effective upon mailing. The addresses for notice shall remain as set forth
herein unless and until changed in writing in the manner provided in this section:
County:
Broward County
Director, Office of Communications Technology
115 S.Andrews Avenue, Room 325
Fort Lauderdale, Florida 33301
With a copy to:
Broward County Attorneys Office
Government Center
115 S.Andrews Avenue, Room 325
Fort Lauderdale, FL 33301
City:
City of
(Insert Address Here)
With a copy to:
City of General Counsel
City of
(Insert Address Here)
11.10 MATERIALITY AND WAIVER OF BREACH: The parties agree that each requirement, duty, and
obligation set forth herein is substantial and important to the formation of this Agreement and,
therefore, is a material term hereof. Either party's failure to enforce any provision of this
Agreement shall not be deemed a waiver of such provision or modification of this Agreement. A
waiver of any breach of a provision of this Agreement shall not be deemed a waiver of any
subsequent breach and shall not be construed to be a modification of the terms of this
Agreement.
11.11 INDEPENDENT CONTRACTORS: The parties agree that each party to this Agreement is an
independent contractor. In providing such services, neither of the Parties, nor their respective
agents shall act as officers, employees, or agents of the other party. This Agreement shall not
constitute or make the parties a partnership or joint venture.
11.12 RECORDING: This Agreement shall be recorded in accordance with the Florida Intedocal
Cooperation Act of 1969.
Page 10 of 99
11.13 PRIORITY OF PROVISIONS: If there is a conflict or inconsistency between any term, statement,
requirement, or provision of any exhibit attached hereto, any document incorporated into this
Agreement by reference and a term, statement, requirement, or provision of this Agreement, the
term, statement, requirement, or provision contained in Articles 1 through 11 of this Agreement
shall prevail and be given effect. Notwithstanding any other provision herein, if City and County
execute a Lease Agreement for a 911 Emergency Dispatch Center ("Lease Agreement"), then,
solely for the term of the Lease Agreement, to the extent any terms of the Lease Agreement
directly conflict with any provision(s) herein, the terms of the Lease Agreement shall supersede
and control as to any conflicting provision herein.
11.14 MULTIPLE ORIGINALS: This Agreement may be fully executed in five (5) copies by all parties,
each of which, bearing original signatures, shall be the force and effect of an original document.
11.15 NON-DISCRIMINATION: The parties shall not discriminate against any employee or participant in
the performance of the duties, responsibilities and obligations under this Agreement because of
race, age, religion, color, gender, disability, marital status, sexual orientation or national origin.
11.16 RECORDS: Each party shall maintain its own respective records and documents associated with
this Agreement in accordance with the records retention requirements applicable to public
records. Each party shall be responsible for compliance with any public documents requests
served upon it pursuant to Section 119.07, Florida Statutes, and any resultant award of attorney's
fees for noncompliance with that law.
11.17 CHOICE OF LAW,WAIVER OF JURY TRIAL: Any controversies or legal problems arising out of
this transaction and any action involving the enforcement or interpretation of any rights hereunder
shall be submitted exclusively to the jurisdiction of the federal or state courts of Broward County,
Florida, and shall be governed by the laws of the state of Florida and any applicable federal laws,
codes or regulations. To encourage prompt and equitable resolution of any litigation that may
arise hereunder, each party hereby waives any rights it may have to a trial by jury in any such
litigation.
11.18 OWNERSHIP OF EQUIPMENT: County retains ownership of all Equipment that the County
provides to the City pursuant to the terms and conditions of this Agreement. In the event this
Agreement is terminated by either party, the County shall remove and/or recover all equipment
within ninety(90)days of the effective date of termination.
11.19 ATTACHMENTS AND REFERENCES: The following named exhibits are made an integral part of
this Agreement:
Exhibit A: Statement of Work
Attachment 1: System Description
Attachment 2: Acceptance Test Plan
Exhibit B: System Demarcation Points
Attachment 1A: Regional Dispatch Center
Attachment 1 B: Non-Regional Dispatch Center
Attachment 1 C: Non-Dispatch Facility
Attachment 1 D: Mobile Data Law Enforcement
Attachment 1 E: Mobile Data Fire Rescue Frontline Vehicles
Attachment 2: Demarcation Drawings
Exhibit C: Equipment List
Exhibit D: Change Management Request
Exhibit E: Project Charter
Page 11 of 99
Exhibit F: Service Level Agreements
Attachment 1: Terms and Conditions
Attachment 2: Trouble Ticket Workflow
Exhibit G: RPSI Trunked Radio System SOP's
11.20 THIRD PARTY BENEFICIARIES: This Agreement is not intended to benefit any third party nor
shall it create a contractual relationship with any third party.
The remainder of this page is intentionally blank.
Page 12 of 99
REGIONAL INTERLOCAL AGREEMENT BETWEEN BROWARD COUNTY AND
THE CITY OF PROVIDING FOR COOPERATIVE PARTICIPATION
IN A REGIONAL PUBLIC SAFETY INTRANET
BROWARD COUNTY
WITNESS: BROWARD COUNTY, by and through
its Board of County Commissioners
By
(Signature) County Administrator
day of , 20_
(Print Name of Witness)
Approved as to form by
Joni Armstrong Coffey
(Signature) Broward County Attorney
Governmental Center, Suite 423
115 South Andrews Avenue
(Print Name of Witness) Fort Lauderdale, Florida 33301
Telephone: (954)357-7600
Telecopier. (954) 357-7641
By
(Signed) (Date)
Insurance requirements Assistant County Attorney
approved by Broward County
Risk Management Division
By
Signature (Date)
Print Name and Title above
Page 13 of 99
REGIONAL INTERLOCAL AGREEMENT BETWEEN BROWARD COUNTY AND
THE CITY OF PROVIDING FOR COOPERATIVE PARTICIPATION
IN A REGIONAL PUBLIC SAFETY INTRANET
CITY OF
ATTEST: CITY OF
By:
CITY CLERK CITY MAYOR
Print Name
day of , 20_
Approved as to form and legal
sufficiency subject to execution by the parties:
City Attorney
Page 14 of 99
Exhibit A
Statement of Work
Page 15 of 99
Exhibit A—ATTACHMENT 1
SYSTEM DESCRIPTION
To be provided at Detailed Design Review Phase of the project
Exhibit A—ATTACHMENT 2
Acceptance Test Plan
To be provided at Detailed Design Review Phase of the project
Page 16 of 99
EXHIBIT B—ATTACHMENT I
Regional Public Safety Intranet Demarcation Points
Regional Disoatch Center
RPSI Portion Demarc COUNTY CITY
Responsibility Responsibility
Trunked Radio GOLD ELITE Infrastructure and software All mobile and portable radio
System CONSOLE(S) up to and including the subscriber units including any
COUNTY-owned Gold software operating on the RPSI
Elite/P25 IP based Radio Trunked Radio System; and any
Console(s) located in the advanced features and other
Regional Dispatch Center. monitoring equipment, as
desired.
Hosted Master Site COUNTY OWNED Maintain COUNTY owned Maintain CITY owned radio
(HMS) SMARTX radio equipment in equipment in accordance to
CONVERTERS accordance to COUNTY CITY HMS User Agreement.
HMS User Agreement. The The HMS cost is the
HMS cost is the responsibility of the radio sub-
responsibility of the radio system owner.
sub-system owner.
Radio Talkgroup RECORDER AT Logging recorder CITY has no responsibility for
Recording REGIONAL equipment located at the talkgroup recording in a regional
DISPATCH CENTER Regional Dispatch Center. dispatch center
Any software playback at
the Regional Dispatch
Center.
Fire Station Alerting CITY FSA Fire station alerting Fire station alerting equipment
(FSA) EQUIPMENT equipment located in the located at the CITY fire stations.
LOCATED AT THE Regional Dispatch Center. CITY is responsible for any
FIRE STATION COUNTY will be communication medium other
responsible for COUNTY than COUNTY RF(ie: leased
RF connectivity from the lines). CITY is responsible for
Regional Dispatch Center the Fire Station Radio
to the CITY Fire Station. Frequency(RF)antenna to the
Zetron Model 6 to the
Audio/Video(AV)equipment
including the Public
Announcement(PA)system and
speakers. Any CITY LAN
requirements.
CAD System CITY LAN Infrastructure and software All extended CITY LAN
up to and including the equipment along with software,
CAD server, Regional client licenses, peripheral
dispatch console equipment to provide
workstations, Regional communications to City"read
Dispatch CAD client only" CAD workstations and all
licenses, and the needed existing interfaces. (Future
communications via the interfaces to the COUNTY-
Page 17 of 99
RPSI Portion Demarc COUNTY CITY
Responsibility Responsibility
RPSI. supplied systems do not apply.)
AVL System CITY LAN Infrastructure up to and All extended CITY LAN
including the AVL server, equipment along with software,
regional client desktop client licenses, peripheral
software licenses,and the equipment to provide
needed communications communications to City"read
via the RPSI. only"CAD workstations and all
existing interfaces. (Future
interfaces to the COUNTY-
supplied systems do not apply.)
Advanced Tactical CITY LAN Infrastructure up to and All extended CITY LAN
Mapping including the advanced equipment along with software,
tactical mapping servers, client licenses, peripheral
regional standard desktop equipment to provide
client software licenses, communications to City"read
and the needed only"CAD workstations and all
communications via the existing interfaces. (Future
RPSI. interfaces to the COUNTY-
supplied systems do not apply.)
Fire Records CITY LAN Infrastructure up to and Desktop hardware and all LANs
Management including the Fire Records connected to the FRMS; non-
System Management servers and standard or customized software
standard software site and desired by CITY.
client licensing for Fire
Records.
Law Records CITY LAN Infrastructure up to and Desktop hardware and all LANs
Management including the Law Records connected to the LRMS; non-
System Management servers. standard or customized software
desired by CITY and standard
software site and client licensing
for Law Records.
Page 18 of 99
EXHIBIT B—ATTACHMENT 1 B
Regional Public Safety Intranet Demarcation Points
Non-Regional Dispatch Center
RPSI Portion Demarc COUNTY CITY
Responsibility Responsibility
Trunked Radio Gold Elite Console(s) Infrastructure and software All mobile and portable radio
System up to and including the subscriber units including any
COUNTY-owned Gold software operating on the RPSI
Elite/P25 IP based Radio Trunked Radio System; and any
Console(s) located in the advanced features and other
Regional Dispatch Center. monitoring equipment, as
desired.
Hosted Master Site COUNTY OWNED Maintain COUNTY owned Maintain CITY owned radio
(HMS) SMARTX radio equipment in equipment in accordance to
CONVERTERS accordance to COUNTY CITY HMS User Agreement.
Or HMS User Agreement. The HMS cost is the
CITY OWNED The HMS cost is the responsibility of the radio sub-
SMARTX responsibility of the radio system owner.
CONVERTERS sub-system owner.
Radio Talkgroup N/A COUNTY is not responsible Logging recorder equipment
Recording for radio talkgroup located at the Non-Regional
recording at a Non- Dispatch Center.Any software
Regional Dispatch Center. playback at the Non-Regional
Dispatch Center.
Fire Station Alerting N/A COUNTY is not responsible All fire station alerting related
(FSA) for fire station alerting at a equipment and communication
Non-Regional Dispatch medium at the Non-Regional
Center. Dispatch Center and at the CITY
fire stations.
CAD System CITY LAN Infrastructure and software All extended CITY LAN
up to and including the equipment along with software,
CAD server, Regional client licenses, peripheral
dispatch console equipment to provide
workstations, Regional communications to City"read
Dispatch CAD client only"CAD workstations and all
licenses, and the needed existing interfaces. (Future
communications via the interfaces to the COUNTY-
RPSI. supplied systems do not apply.)
AVL System CITY LAN Infrastructure up to and All extended CITY LAN
including the AVL server, equipment along with software,
regional client desktop client licenses, peripheral
software licenses,and the equipment to provide
needed communications communications to City"read
Page 19 of 99
RPSI Portion Demarc COUNTY CITY
Responsibility Responsibility
via the RPSI. only"CAD workstations and all
existing interfaces. (Future
interfaces to the COUNTY-
supplied systems do not apply.)
Advanced Tactical CITY LAN Infrastructure up to and All extended CITY LAN
Mapping including the advanced equipment along with software,
tactical mapping servers, client licenses, peripheral
regional standard desktop equipment to provide
client software licenses, communications to City"read
and the needed only"CAD workstations and all
communications via the existing interfaces. (Future
RPSI. interfaces to the COUNTY-
supplied systems do not apply.)
Fire Records CITY LAN Infrastructure up to and Desktop hardware and all LANs
Management including the Fire Records connected to the FRMS; non-
System Management servers and standard or customized software
standard software site and desired by CITY.
client licensing for Fire
Records.
Law Records CITY LAN Infrastructure up to and Desktop hardware and all LANs
Management including the Law Records connected to the LRMS; non-
System Management servers. standard or customized software
desired by CITY and standard
software site and client licensing
for Law Records.
Page 20 of 99
EXHIBIT B—ATTACHMENT 1 C
Realonal Public Safety Intranet Demarcation Points
Non-Dispatch Facility
RPSI Portion Demarc COUNTY CITY
Responsibility Responsibility
CAD System CITY LAN All extended CITY LAN
Infrastructure up to and equipment along with software,
including physical network client licenses, desktop
connectivity from the RPSI workstations, peripheral
to a single pre-defined equipment to provide
CITY location. communications to City"read
only"CAD workstations and all
existing interfaces. (Future
interfaces to the COUNTY-
supplied systems do not apply.)
Advanced Tactical CITY LAN Infrastructure up to and All extended CITY LAN
Mapping including physical network equipment along with software,
connectivity from the RPSI client licenses, desktop
to a single pre-defined workstations, peripheral
CITY location. equipment to provide
communications to City ATM
workstations and all existing
interfaces. (Future interfaces to
the COUNTY-supplied systems
do not apply.)
Fire Records CITY LAN Infrastructure up to and Desktop hardware and all LANs
Management including physical network connected to the FRMS; non-
System connectivity from the RPSI standard or customized software
to a single pre-defined desired by CITY.
CITY location.
FRMS standard site and
client desktop software
licenses will be provided
from COUNTY to CITY.
Law Records CITY LAN Infrastructure up to and Desktop hardware and all LANs
Management including physical network connected to the LRMS; non-
System connectivity from the RPSI standard or customized software
to a single pre-defined desired by CITY and standard
CITY location. software site and client licensing
for Law Records.
Page 21 of 99
EXHIBIT B—ATTACHMENT I
Regional Public Safety Intranet Demarcation Points
Mobile Data—Law Enforcement
RPSI Portion Demarc COUNTY CITY
Responsibility Responsibility
Trunked Radio Gold Elite Console(s) Infrastructure up to the All mobile and portable radio
System COUNTY-owned Gold subscriber units including any
Elite/P25 IP Console(s) software required to operate
located in the Regional on the RPSI Trunked Radio
and/or Non-Regional System; and any advanced
Dispatch Center. features and other monitoring
equipment, as desired.
CAD System CITY MDT Infrastructure up to and All extended LAN equipment
including the CAD server along with software, client
and the needed licenses, peripheral equipment
communications via the to provide communications to
RPSI. City CAD MDTs and all
existing interfaces. (Future
interfaces to the COUNTY-
supplied systems do not
apply)
AVL System COUNTY's Infrastructure up to and All vehicle-related equipment
Infrastructure including the AVL server; and any remote monitoring
and the needed equipment and software
communications via the
RPSI.
Law Record COUNTY Infrastructure up to and All vehicle Equipment
Management System infrastructure including the Law Records including laptop, modem,
Management servers. cabling, associated mounting
hardware, antenna—and any
monitoring Equipment and
standard software site and
client licensing for Law
Records. Non-standard or
customized software is also
the responsibility of the CITY.
Page 22 of 99
EXHIBIT B—ATTACHMENT 1 E
Regional Public Safety Intranet Demarcation Points
Mobile Data-Fire Rescue Frontline Vehicles
RPSI Portion Demarc COUNTY CITY
Responsibility Responsibility
Trunked Radio Gold Elite Console(s) Infrastructure up to the All mobile and portable
System COUNTY-owned Gold radio subscriber units
Elite/P25 IP Console(s) including any software
located in the Regional required to operate on
and/or Non-Regional the RPSI Trunked Radio
Dispatch Center. System; and any
advanced features and
other monitoring
equipment, as desired.
CAD System CITY LAN Infrastructure and software All vehicle related
up to and including the peripheral equipment
CAD server, MDT and any monitoring
hardware, MDT regional
CAD client software equipment. Non-
licenses, and the needed Regional or customized
software desired by
communications via the
RPSI. CITY. (Future interfaces
to the COUNTY-
supplied systems do not
apply.)
AVL System Frontline Vehicle Infrastructure up to and All vehicle-related
including the AVL server, peripheral equipment
and GPS devices located in and any remote
Fire Rescue frontline monitoring equipment
vehicles. and software.
Mobile Data Frontline Vehicle COUNTY will assume All vehicle related
Terminals capital and lifecycle peripheral equipment
procurement of MDT's and and any monitoring
associated regional Equipment. CITY
standard software for Fire responsible for wireless
Rescue frontline vehicles. modems and recurring
operating costs. Non-
regional or customized
software desired by
CITY.
Fire Record COUNTY Acquisition of FRMS
Page 23 of 99
RPSI Portion Demarc COUNTY CITY
Responsibility Responsibility
Management infrastructure COUNTY infrastructure up standard site and client
System to and including the FIRMS mobile software licenses
Server and the needed will be the responsibility
communication interfaces of CITY. All vehicle
via the RPSI. related peripheral
equipment and any
monitoring Equipment.
Non-regional or
customized software
desired by CITY.
(Future interfaces to the
COUNTY-supplied
systems do not apply.)
Page 24 of 99
EXHIBIT B—ATTACHMENT 2(Drawinsis)
Page 25 of 99
k
. )
(
\ �
z
kk ® -
EE k�(
c _
�
7G !\ E
� / |kkkk �ty-!
: fkkkJ.5t
isa ; ES
■ - -
p f Cl) 2-2- /
J@ ---lis--- 27
q \ - - - - - - - (
\)�
L 2 \
J t a )
_ § § £
/{ �
— - k
a _
k k ƒ - - -
/ �J { \ .\{ ({
-
»
tm\ \)\§/k
■ O 13 z �
2 « § kk
U8 ] m
)
�\ -
§
\ ) -
� k2
2
&
� (#§
{|\
co . \/\
. �
i5
c ! 2�
� 142
/ / § IR133 �3\{\}
- - -
w�
§ ° w _ \{/ !
ET--------
J § q = - - - - - - - -
§ � 2rL
2 m a
0 uj \
)) �
co
f
c &.S:?
U f t -
- -
% O D
» p \ _ %
2 « K $§
IM Um ja
7
�
# \ 3 \k
a { / - /
-_ -
!
co ) 3K ƒ$\{i
/
■7(E
o # t /G2rJg{
§ f � �k\$ g
� )\{\{§)
`§ F)EE< \§f!
~&t;22a�/tea
} {
k \\
ƒ
■ _ &{»9! ƒ§
6m
LL _ \/)
#§« !$\4 !
2 CL ■ \ /-- �-k)/
-§
( § g■ IL \\\\\\\\\
tZ
Ix(L
0
� �
_ « .20. ■] *
o ! r ! )�■ u ®! (}
� _ -
0 % k 3 Q7 .j.2 2 ;
\#_ § #
� � ®t! | ■®
z � \
$ })} 2 __\
« 2\m \{{{«
_ d
i E u
N G
O T N N W
U y C C O] L
d a o
� p m U �n
W
Z t e o 0 o g
O
n 3 .63 0 0
u
c- E n a
o E¢
O
)An
O
L N
u y
n
w x w
C
d
E
d L.L r
In t v c=r g N 3 E Q
= v a
m o
c U L C C z fm E EE E A c c-.S
LL LL u�eac� owe 5 rm`Z` S
y J _
� GOOOEd c_ dQ aC
V d W
d LL o n> > >z Fi a H o E U E a a
SSZi o o¢a a o a' c a a L o
O L V m C C A A--- A N W C L G N
CCn.
ZE d y a�i E E
a N
J C c p y W
s �
R c
> p O 3 ccq�
Q O y V
U
C d O
�•+ � � �� a - is �. �' c 2��n
m t, O tiv c � r
Li.52
O L D U o] m'� a
y= y�[ -
U V = O c Q Z U U
p T T T T y
U V Occ
3 N a Z
m U.
u u u . C
R V Y
l0 U /0 LL0 na a a.E
0 p '�30 aaaa.3
m m` 0m
C
O
¢ m
O o c a u
uj
¢ m��� `• E u.�.�w o
2
m ° ° E
Z U d �j ° o
O u N - _a w r a
N� C °
c c c ij °c .°E
E a V
N 3 E E E.= d w
W a
d o 'to A N d
coV H C'O O C N .`16 O `O¢ C C m
-
\ O
O
U
_ov o 0 o.d E� cZ c c
y O
c� 3 v
u �
a, sA 0
.0
r0 c y U
`O
d
� n a
;f CL � c
E c
E
r 3 N w
4 Via'
O o o n
w � z
g X
C
J E g EU
d Y o Y O O
LE
�/ O L.G C C O
C zUz O-Z cc_T
W H di zo
U W �NONua=
J J O
O � ° a
io m O c asap a,c �«
0 Z o o o` _"
Gt O z 'rn z rn'rn t'a0
. E
Q = a a ;n"3czos �
o a0 0) y
tl NVAvg�
J +' 0 LU
�C c
LU
C1 m
a B
> ° O c
Q N O y V Z E w u
u = y o E
3 (A m Ln
O y� N mS AN�2 y O
S i a m � _�! u a
U =y d d G t E E H
V > c ° o a
0 2� C a >=.z>.s.m
2 O m z T u
u t0 ._a3aa
0 L 0 � �aoai�
m = m 0
[C
�
�
d \
� � \ j
o
} ( \ k
(
/ o
§
k\k/ -
kQ�!
w 7 §{
2 a 5.j\)�
(!\k#
(12
O
"i ZZla)' mow �
)
/\ `� /
$ n
o
${#
E 4k7E
`\\\ o
o
2\!$f
» \ / `*>\ƒ
f °o fE
o
G _ �
%
_ Q | - . j { !
$ e | - - - - - )/
Cog_ LU S
■ e r J2
_ = }
� E > � @
/ } ®
® tm: 2 0
f� # %
2f9 m §. e^
� of , �] . JI
� \)) / \� k} � � ){ \}/
o—%u q � � : ) u
is x-i j� ^ -
a
I
\
)
@ } \ )
& y & /
�■ / E � � 41
-�
�� -
e -
'
k ) }\\\
% CL
§ /
\
\
E E} {
❑ �� -\ � -
� ) eg
\ ) 20 §\ !
SE
. : . () �}/!
kcr
� \- 1.
E f$ t2c).
ƒ CLSF—
` /\}§ |\ � \wo
f2 ■ ;` !
■ § )k �
2 % e E}§& =
�
B VIoU 2 \ /
2 « e § - - - ® a
m � �
EL. ) f ] -
° ° ° ■. f //[ 2
�
§
0 2§\ 2
2 ) } 0 ® -
■ /fL) \ } kk )) k)/` E
m _ & \/ , \
\
!
IL
� !
10
JW
ca
a.
� |
. &
. . .
_ } !
�
§
k0 f ƒ \ )
.; IL
e - ) ■ k
r
LU �} �( /
co
§ Erg
�
�
E
q �)
\ \
.2 #
k �}
■ / Zo
2 p 3 . _ }
o E 2 $
}
> E � lw
) �mw} z ± f ; }
m 0 �7 $ co � ! !
#fir ° CO= &m .
ƒ soCD
\
� ) A�
;
J § k% / / > r
# , 0 � o i - - -
2 � ao . I �( -- -
� m \ } 2 - - -
M & -Oj3
EXHIBIT"C"
Equipment List
Model numbers are provided for reference only in this proposal and are subject to change.
Page 34 of 99
Exhibit D
Change Management Request Procedure
Introduction
This document defines the Change Management Reauest (CMR) process for any component(s)
that make up the Regional Public Safety Intranet providing delivery of services to end-users.
The CMR process will be used to specify the times and conditions when designated tasks can
be performed as maintenance on all software and equipment affiliated with the Regional Public
Safety Intranet including but not limited to the Public Safety Network (PSN), Trunked Radio
System, Computer Aided Dispatch (CAD) System, LRMS, FRMS, PMDC, UDT/DSS, E-911, etc.
Objective
The objective of the CMR process is to implement maintenance and expansion guidelines that
will assure system reliability; minimize the impact on end-users and prevent unintended outage
conditions.
Definition
The CMR process will be an ongoing activity involved with the scheduling, communication and
coordination of maintenance and construction activities impacting the RPSI. This process
includes a Request, Review and Approval process. All change and maintenance activities are
performed during predetermined and mutually acceptable Maintenance Windows.
Scope
The CMR process should be followed for any installation, equipment and software maintenance
activity or any construction activity which either directly or indirectly impacts the Regional Public
Safety Intranet.
CMR Process Reguirements
All scheduled change and maintenance activities will require completion of an electronic CMR
form and must conform to the following criteria:
• All work requests that impact directly or indirectly the end-users of Public Safety Mission
Critical applications must be thoroughly documented in the CMR forms and sent as an e-
mail attachment to: octchangemanagement(cD-broward.org.
• County's Office of Communication Technology (OCT) will review all requests and obtain
consensus from Operations and from all impacted end-users on scheduling the
Maintenance Window for the request.
• Activities will be scheduled and performed only during predefined or mutually acceptable
Maintenance Windows.
• The Requestor submitting the Method of Procedure (MOP) form must identify the scope of
the associated outage and a best estimate of the duration of the activities involved in the
Page 35 of 99
project. Stop times must take into account the time needed to restore the system to an
operational state.
• Following County OCT approval of the submitted Method of Procedure (MOP), a project
coordination meeting involving representatives of all involved or impacted parties will be
scheduled by the assigned OCT Program Manager prior to the start of the scheduled work.
MOP Requirements
• The MOP must clearly state the objective(s) of the work to be performed; the parties
performing the work; the parties impacted by the work and the steps to be completed by
each party.
• A Maintenance Window identifying a clear Start and Stop time and a work flow schedule
must be developed and included as part of the MOP.
• The scheduled work must follow the predetermined schedules identified in the MOP, and, as
previously noted, stop times must take into account the time needed to restore the system to
an operational state.
• The MOP must clearly identify the Program Managers responsible for coordination of the
activity and provide telephone numbers and any other relevant contact information.
• The MOP must include an escalation list with notification time frames should unforeseen
problems occur that would result in an outage extending beyond the scheduled Maintenance
Window.
• The MOP must include a fallback plan should the original plan not work.
Emergency Maintenance
Emergencies by their nature are not a part of the CMR process, but can seriously impact end-
users and any scheduled maintenance activities.
In the event of an emergency outage, both the affected end-user and first responder must notify
the designated on-call person for the Office of Communications Technology (OCT). An on-call
list will be provided to each 911/Dispatch Center Duty Officer and Manager. The OCT contact
will be responsible for the following actions:
• Identifying and assigning resources to work the emergency.
• Acting as a liaison between the maintenance provider and the 911/Dispatch Center Duty
Officer and Manager for the duration of the outage or service degradation.
• Documenting response times and actions taken, followed by generating an after-action
report.
The maintenance provider(s) responding to an outage or service affecting emergency must take
the following measures following notification:
Page 36 of 99
• Upon notification, use remote access to diagnose and repair the problem or arrive on site
within the contracted time frames of the responder's maintenance agreement.
• Assess the nature and scope of the problem.
• Notify the County OCT on-call person of all actions to be taken and provide the best
possible estimate of the duration of the outage or service degradation.
• Notify the County OCT on-call person of any break in maintenance activity prior to
completion of the repair for any reason.
• Provide periodic updates for extended outages.
• Document each step of the repair/troubleshooting process as it is performed.
• Within 24 hours of completion of a repair, provide a written summary of the problem and the
measures taken to repair the problem and (if relevant) prevent similar future outages.
• County OCT managers will review the submitted documentation and on a case by case
basis schedule a debriefing session to review the steps taken to resolve the problem and
suggest changes or improvements for responding to future unscheduled outages.
Maintenance Windows
• The standard weekday Maintenance Window for Public Safety Communications Operations
is 12:01 AM — 06:00 AM Sunday through Thursday or as otherwise specified by the
Operations managers.
• The standard weekend Maintenance Window for Public Safety Communications Operations
is 5:01 AM — 02:00 PM Saturday and Sunday or as otherwise specified by the Operations
managers.
• A CMR must include sufficient time to perform a back-out of the change within the Window
timeframe and restore systems to their normal operational state.
• A CMR that requires work to be performed outside the standard Maintenance Windows must
include justification for performing the work during a non-standard window and be approved
by County's OCT.
Page 37 of 99
Chanae Manaaement Request
Process Work Flow
Requestor OCT
Serbcriit Rw-Ww Rsgwst
Raqumist to Log in CUR
OCT
PsoW—
Rsais MOP
ftwwmi MOP No MOP yes
mint!R N
sdlmid"
Mpinomi
Wkdow WAlk Ai
Pmirimis
Amimiimi�r smind E-nwi
lWodt! MmiYomis to
NO CUR Peajact y (Ao cast Nfdfy End4je s
.�{i00 DOOIi�RI>tl! d
7 R
Page 38 of 99
T L Nd Acd i
WIN
FYI Non- Prep work activity Minimum No FYI as needed.
Service which has low risk to 2 days
Affecting end-users of Public
Safety Mission Critical
a lications.
Scheduled Potential Any activity that may Minimum Yes Notify all End-
-Service impact end-user access 5 days Users and
Affecting to Public Safety Support
Mission Critical Management
aDDlications.
Scheduled Service Includes any activity Minimum Yes Obtain written or
Affecting which will result in the 10 days e-mail approval
loss or degradation of from
accessibility to end- Management.
users of one or more Provide Written
Public Safety Mission Notification to all
Critical applications.
affected End-
Users.
Obtain Written
Approval of all
affected End-
Users.
Scheduled Outage Any work which will Minimum Yes Obtain written or
Required necessitate a total 10 days e-mail approval
outage of one or more from
of the Public Safety Management.
Mission Critical Provide Written
applications or the Notification to all
Public Safety Wide Area affected End-
Network, or any Users.
extremely high risk
activity which may Obtain Written
inadvertently cause an Approval of all
outage. affected End-
Users.
Emergency Service The unscheduled None No Requires
Affecting outage of one or more immediate
or Public Safety Mission management and
Outage Critical applications or End-User
Required the Public Safety Wide notification and a
Area Network. debriefing
meeting once the
problem has
been resolved.
Page 39 of 99
End-User Notification
Not less than ten (10) business days prior to an approved CMR project affecting the Regional
Public Safety Intranet, the County OCT project manager must notify all end-user management
by e-mail of the pending activity with all CMR and MOP documentation attached. The e-mail
should summarize the attached documentation but must include:
• A list of all affected end-users.
• A generic statement of nature of upgrade or maintenance procedure and the operational
need to make the change.
• The Maintenance Window, date and time the work will be performed including the projected
end time.
• A generic impact statement that identifies the nature of the work being performed; the
impact of the work on the end-user while the work is performed and the effect of the work on
the restored system or application.
• Telephone numbers of project managers and key staff involved in the activity.
Approval Authority
Any and all activities being performed must be supported by an approved CMR document.
Page 40 of 99
Broward County
Office of Communications Technology (OCT)
Change Request Form
Note: Complete and submit to the Broward County Office of Communications Technology at
OCTChangeManagementCcD-broward.org. All Change Requests submitted prior to Wednesday
are reviewed during the Thursday morning conference calls and either approved or returned
for modifications. Please allow a minimum of ten (10) business days from the date of
approval for your Maintenance Window to be scheduled. Any work performed on the Public
Safety Communications Network, its supporting infrastructure, or the application servers must
be documented and approved in a CMR.
Today's Date and Time:
Requestor Name:
Requestor Company Name or Agency:
Requestor E-Mail:
Office:
Requestor Phone Number:
Mobile:
Briefly describe the Work to Be Performed:
Identify End-Users & sites impacted by the
work to be performed:
Page 41 of 99
What is the expected and desired end
result of the Work to be Performed?
Identify any loss or degradation of
functionality and the impact on end-users
during the Maintenance Window:
Name & Contact Number:
Identify your On-Site Contact during the
scheduled Maintenance Window:
Start Date &Time:
Requested Maintenance Window for Work
to be Performed: Stop Date &Time:
Start Date &Time:
Approved Maintenance Window for Work to
be Performed:
Stop Date &Time:
Maintenance Window
Approved By: Date:
Page 42 of 99
Assigned MOP Tracking Number:
Method of Procedure —for Primary Contractor or Service Provider
Note: An MOP must be completed for each Contractor or Service Provider working on a
specific project. Use electronic attachments as needed.
Company or Agency Name:
Project Manager Name:
Project Manager Office Phone
Number:
Project Manager Mobile Phone
Number:
Project Manager E-Mail:
Detailed Project Description
Specify each step in the MOP Work
Process. Attach additional pages or
any supporting documents as needed:
Page 43 of 99
Describe back-out and restoration
plans if stated project goals are not
achieved within the allotted
Maintenance Window:
OCT to complete Items 1 through 10 Below:
(2) Name:
(1) OCT Contact for Project: (3) Mobile Phone Number:
(4) E-Mail:
(6) FYI —Non-Service Affecting: ❑
(7) Scheduled—Potential Service Affecting: ❑
(5) MOP Type: (g) Scheduled—Service Affecting: ❑
(9) Scheduled—Outage Required: ❑
(10) Emergency: ❑
Reviewer Comments:
Method of Procedure Approved By: Date Approved
Page 44 of 99
Exhibit E
Project Charter
PROJECT CHARTER
[Note:All fields in blue text must be filled in.]
1. General Proiect Information
Project Name:
Department/Agency Sponsor:
• What department is the primary proponent of this
project? (Enter one.)
• Who,within that department,is the Project Sponsor?(Note: This person must be a
decision-maker with the authority to commit department resources.)
• is this a Regional Project,i.e.does it have significant impact on regional applications or
resources(Y/N)?
Department Co-Sponsor:
Department/Agency Project
Rank:
If this project is mandated or is Mandated by
required for continued business whom?
operation:
Impact of not
meeting mandate?
Document History
Version Date Author Reason for Change
......................-.----..
..........._...._.......__ ._..__---1_..__.......—...---.--..____..._.__....... ______.__.____.._ ._......... ........__--____.____..______......._......
.
Page 45 of 99
2. Stakeholders
Name Department Telephone E-mail
Agency Lead:
Regional
Applications PSI
Manager:
...................................... ------
Project Lead:
Others: Key Players from the City
Agency Lead:
TechLead:
Tech Lead:
.......... ........... ............................................. ....... ..................
3. Vendor Contacts
Name Company/Role Telephone E-mail
........................... ......................... ........................
—-----—---------
............... 4—-——------------—-------—
........... ............................................
Project Purpose/Business Justification
ObjectiN es(in business terms)
Page 46 of 99
Project4. • •
Delis erables
Clear Statement of What This Project Will Not Include
Project Success
Project Milestones
Major Known Risks(including significant Assumptions)
Risk Rating(Hi, Med, Lo):
Constraints
Page 47 of 99
4. • • •
External Dependencies
Project Strategy
List of events that should take place in chronological order:
Resources Information
Funding Source Operating Budget,Capital Budget,Grant,Other.
Estimate of Implementation Cost
Return-on-Investment(ROI)Data
Estimate time required of Multi-Department Staff
Role Hours needed
Page 48 of 99
Resources . •
Estimate time required of other Organization Staff
Role Hours needed
6. Estimated Total Cost of Ownership (TCO) 5-Year — Provider (BC-OCT)
*The OPEX figures below only represent the provider capex and opex based on hardware,software,and
professional services.
Calendar Year(1,2,3)or Fiscal Year Capital($U.S.) Operational($U.S.)
(2012-13, 2013-14)
2012-13 0 0
2013-14 0 0
2014-15 0 0
2015-16 0 0
2016-2017 0 0
Totals $0 $0
Estimated7. Total Costof Ownership •
*The OPEX figures below only represent the monthly recurring cost for aircards and does not represent the annual
O&M expense for software and hardware devices.*
Calendar Year(1,2,3)or Fiscal Year Capital($U.S.) Operational($U.S.)
(2009-10,2010-11)
2012-13 $0.00 $0.00
2013-14 $0.00 $0.00
2014-15 $0.00 $0.00
2015-16 $0.00 $0.00
2016-17 $0.00 $0.00
Totals $0.00 $0.00
Page 49 of 99
8. Sourcing Strategy • • Strategy
Organization-Managed and Hosted Sole-Source/Amend Contract
Vendor-Managed and Hosted RFP/Competitive Bid
Organization-Managed,Vendor-Hosted In-House/Custom-Develop
Vendor-Managed,Organization-Hosted Other:
1 Types of • • Assistance
Turnkey Solution Supplemental Staffing(Time/Materials)
Vendor-Assisted(Fixed Price) Hardware/Software
Other: None/Not Applicable
11. Sign-off
Name Title Signature Date
(MM/DD/YYYY)
Business Sponsor
Business Sponsor
Program Manager
Agency Sponsor
Agency Sponsor
12. List of Addenda
Document Name Filename and Location
Page 50 of 99
12. List of Addenda
Document Name Filename and Location
13. • - Comments
Page 51 of 99
Exhibit F—ATTACHMENT 1
Service Level Agreements
Terms and Conditions
INTRODUCTION
This purpose of this Service Level Agreement (SLA) is to clarify the mutual expectations of the
City and the County with respect to the RPSI system ("System"). Changes in software and
hardware architecture make it imperative that all members understand their mutual
responsibilities.
1.0 MAINTENANCE SERVICE AND SUPPORT
1.1 Maintenance Service and Support being provided are based on the Severity Levels as
defined below. Each Severity Level defines the actions that will be taken by County for
Response Time (MTTR), Resolution Time, and Resolution Procedure for reported errors.
Response Times for Severity Levels 1 and 2 are based upon voice contact by City, as opposed
to written contact by e-mail, facsimile or letter. Should delays by City prevent scheduling of
downtime to resolve an issue, County will not be held responsible for Resolution time frames
listed below.
SEVERITY DEFINITION MTTR TARGET
LEVEL (Mean Time To RESOLUTION
Respond)
1 Failure/Outage occurs when the system is not :530 minutes of Resolve within 24
functioning which prohibits continuance of initial voice hours of initial
mission critical operations. notification* notification*
2 Failure occurs when an element in the system s 24 business Resolve within 5
is not functioning that does not prohibit hours of initial standard
continuance of normal daily operations. voice notification.* business days of
initial notification*
3 An Inconvenience occurs when software or 548 business Resolution
hardware causes a minor disruption in the hours of initial determined on a
way tasks are performed but does not stop notification case by case
workflow. basis.
*Does not apply to "READ-ONLY" CAD systems
1.2 The City Agency Administrator or IT Representative shall conduct a preliminary error
review to verify a problem, determine if such is the direct result of a defect in Hardware,
Software, or other and the direct conditions under which the problem occurred, identify the
applicable urgency rating scale by which errors, problems, and other issues are scheduled
("Severity Level'), and ascertain that errors are not due to an external system, data link between
systems, or network administration issue prior to contacting County.
1.3 City shall assign an initial Severity Level for each error reported, either verbally or in
writing, based upon the Severity Levels defined above. Severity Level 1 or 2 problems should
be reported verbally to the County by City IT Representative or Agency Administrator. County
Page 52 of 99
may modify the initial Severity Level (upgrade or downgrade), in which event County will notify
the City of the change in Severity Level of any City-reported problem.
1.4 County shall provide telephone support for maintenance issues 24 hours per day, 7 days
a week (24 x 7).
1.5 All requests for support for the products specified in this Exhibit will be logged with the
County Customer Support Center ("CSC") via telephone at 1-954-357-8686 or email at
selfheIDA-broward.om
1.6 County will provide City with a resolution within the appropriate Resolution Time and in
accordance with the assigned error Severity Level when County diagnostics indicate that the
error is present. Additionally, County will verify: (a) the hardware and software are being
operated in conformity to the System Specifications, (b) the hardware and software are being
used in a manner for which they was intended or designed, and (c) that the hardware and
Software are being used only with County approved hardware and software. Resolution Time
period shall not begin to run until such time as the verification procedures have been completed.
County will continue to provide service support under this Interlocal Agreement until final
resolution is determined.
1.7 Should County determine that it is unable to correct such reported error within the
specified Resolution Time, County will upgrade and escalate its procedure and assign such
personnel or designee to correct such error. This will include automatic problem call escalation
to appropriate levels of County management.
1.8 County will extend, to the extent permitted under applicable maintenance or service
agreements, any and all maintenance service provided to County by the maintenance or service
provider to City provided that:
a) Any third party hardware, software, and any other related supplies shall conform to any
and all applicable industry approved technical, functional, and performance
specifications;
b) The System is free of modifications and alterations which have not been pre-approved
by County.
c) The System has not been subject to any misuse and/or abuse, whether negligent,
intentional or otherwise.
1.9 Unless otherwise specified herein, any and all suspected errors will be investigated and
corrected at County facilities. County shall decide whether on-site correction of any hardware
and software error is required.
1.10 Any third party equipment supplied by County to City shall be subject, to the extent
permitted under applicable agreements, to the manufacturer's warranty for that equipment.
2.0 RECORD—KEEPING AND REPORTING RESPONSIBILITIES
2.1 County will provide verbal and written status reports on Severity Level 1 errors. Written
status reports on outstanding errors will be provided to City Agency Administrator or IT
Representative on a monthly basis upon request.
Page 53 of 99
2.2 County shall provide annual account reviews to include: a) service history of site; b)
downtime analysis; and c) service trend analysis.
2.3 County will prepare the following reports (for PremierCAD software only), to include:
a) System Analysis MEASURE: Evaluate disk and CPU load
PEEK: Evaluate memory availability and use
VIEWSYS: Evaluate use and availability of PCBs
EMSA/TMDS: Review logs for hardware reports
File Sizing: Review file sizing on changeable files
b) Pathway Analysis Evaluate effectiveness of system configuration for current
load.
Evaluate TCP/Server statistics.
Evaluate efficiency of server class maximum and minimum
settings.
c) Performance Analysis TMX Timings: Evaluate application response times
d) Printrak Technical Support Analyst. Based on an annual system performance review
and reports, the Printrak Technical Support Analyst will review findings and
recommend software or hardware changes to improve overall operations.
3.0 MISCELLANEOUS
3.1 When County performs service for the System at a City location, City agrees to provide
County, at no charge, a non-hazardous environment for work with shelter, heat, light, and power
and with full and free access to the System.
3.2 City will provide all requested information pertaining to the City-owned hardware and
software elements of any equipment with which the System is interfacing so as to enable
County to perform its obligations under this Service Agreement.
3.3 It is not required that parts furnished by County be newly manufactured, provided that
any furnished parts be equivalent to new in performance. County-owned parts replaced in the
course of repair shall remain County's property.
3.4 City will provide a qualified Agency Administrator for the Printrak system portion to
perform all functions as defined in the CAD Security Matrix or Printrak System Administrator's
guide(which has been made available to the City).
3.5 Upon the expiration or earlier termination of this Agreement, City and County shall
immediately deliver to the other party, as the disclosing party, all Confidential Information of the
other, including any and all copies thereof, which the other party previously provided to it in
furtherance of this Agreement. "Confidential Information" as used herein shall include: (a)
proprietary materials and information of the disclosing party regarding technical plans; (b) any
and all other technical information, whether in a softcopy or hardcopy medium, including but not
limited to data, developments, trade secrets and improvements that was disclosed in any form
by the disclosing party; (c) all GIS, address, telephone, or like records and data provided by the
disclosing party that is required by law to be held confidential.
Page 54 of 99
3.6 This Service Level Agreement does not grant directly, by implication, or otherwise, any
ownership right or license under any patent, copyright, trade secret, or other intellectual property
including any intellectual property created as a result of or related to the products sold or
services performed under this Service Level Agreement.
4.0 SOFTWARE UPDATES
County shall provide software updates, to the extent permitted under applicable license,
maintenance or services agreements, as defined below:
4.1 Supplemental Release is defined as a minor release that contains primarily error
corrections to an existing Standard Release. It may also contain limited improvements that do
not affect the overall structure of the Software. Supplemental Releases can be installed
remotely. Supplemental Releases are identified by the third digit of the three-digit release
number, shown here as underlined: "1.2.3".
4.2 Standard Release is defined as a major release of Software that contains product
enhancements and improvements such as new databases, modifications to databases, new
server/requesters, etc., and may involve file and database conversions, System configuration
changes, hardware changes, additional training, modifications of Software license terms, on-site
installation, and System downtime. Standard Releases are identified by the second digit of the
three-digit release number, shown here as underlined: "1.2.3".
4.3 Product Release is defined as a major release of Software considered the next
generation of an existing product or a new product offering. Product Releases are identified by
the first digit of the three-digit release number, shown here as underlined: "1.2.3".
4.4 The City will not be required to pay any additional fees for County provided software
releases.
4.5 At City's request, County will provide a current list of compatible hardware operating
system releases. A list of Software Supplemental or Standard Releases will also be made
available at no charge to City.
4.6 City must maintain all hardware and software connected to the County's network to the
latest compatible revisions.
6.0 ADDITIONS AND CHANGES
5.1 The City may request an enhancement to System functionality. Enhancement requests
should be submitted to County's Office of Communications Technology (OCT) for review. If
OCT accepts the enhancement request, the request will be referred to the Program
Management Team for possible inclusion in a future project. County OCT will provide a
response to the enhancement request within ninety (90) standard business days of written
receipt of initial request. If accepted, a proposed Project Plan will be furnished with any
applicable enhancement fee. The City may choose to pay for an enhancement request that has
been accepted by Program Management but is not viewed as a high enough priority to include
in a release.
Page 55 of 99
6.0 ACCESS
6.1 The City agrees to maintain any and all electrical and physical environments in
accordance with System manufacturer's specifications.
6.2 The City agrees to ensure System accessibility, which includes physical access to
building as well as remote access. Remote access is required and will not be substituted with
on-site visits if remote access is not allowed or available.
7.0 EXCLUSIONS
7.1 Maintenance services and support not expressly listed in this SLA are excluded, and
County shall not be liable under this Agreement for such services. Exclusions consist of, but
are not limited to:
a) Any service work required due to incorrect or faulty operational conditions, including
but not limited to equipment not connected directly to an electric surge protector,
equipment used in a non-office environment, and equipment not properly maintained
in accordance with guidelines set forth in the manufacturer's User's Guide;
b) The repair or replacement of parts resulting from failure of the City's facilities or
City's personal property and/or devices connected to the System (or interconnected
to devices)whether or not installed by County's representatives;
c) The repair or replacement of Equipment that has become defective or damaged due
to physical or chemical misuse or abuse from causes such as lightning, power
surges, or liquids;
d) The repair or replacement of any transmission medium, such as telephone lines,
computer networks, or the worldwide web, or for Equipment malfunction caused by
such transmission medium;
e) Accessories; custom or special products; office furniture which includes chair(s) and
workstation(s); modified units; or modified software;
f) The repair or replacement of parts resulting from the tampering by persons
unauthorized by County or the failure of the System due to extraordinary uses;
g) Operation and/or functionality of City's personal property, equipment, and/or
peripherals and any non-County provided application software including service of
any accessory, attachment, or component owned by City, whether or not installed by
County;
h) Removal, relocation, and/or reinstallation of System or any component thereof
without prior written consent by the County;
i) Services to diagnose technical issues caused by the installation of unauthorized
components or misuse of the System.
j) Operational supplies including, but not limited to, printer paper, printer ribbons, toner,
photographic paper, magnetic tapes, any supplies in addition to that delivered with
the System, and battery replacement for uninterruptible power supply(UPS).
Page 56 of 99
k) Unauthorized installation of any software or hardware modifying Printrak Software
and/or the System.
7.2 City shall be responsible for payment of any desired service and support not included
within the scope of this SIA and such service or support shall be performed at the rates set
forth below.
Billable rates are subject to a two(2) hour minimum:
$100 per hour 8 a.m. — 5 p.m. (local time) Monday — Friday (excluding County
established holidays)
$150 per hour After 5 p.m. Monday — Friday, and all day on Saturday, Sunday
and County established holidays
Travel Expense In addition to the above hourly labor rates, all other actual travel
related expenses may be charged to City.
Page 57 of 99
Exhibit F—ATTACHMENT 2
Service Level Agreements
Trouble Ticket Workflow
RPSL Interlocal Agreement Trouble Ticket Workflow
Broward County Office of Communications Technology-Public Safety Intranet
I.
mwll
.w-
Iltr ♦*T �. EAOli01 11nW �. Ma t.D/y. M T ti�
mills" rill WIN
der OiWlrtt.��
O.aRT Yoii"Pr Milli
Iwr rwb Milli
lww hyey
O A./r Tte.1^r W IIIY Yy'
w.wr
� b
twrwr ..YYb ..Y.b tr n.et. �ft
.wrrr w+.wl+ +...er wWri. � ttl.
r.0. rcf wrr tu+ ww.
1.
ttrtrt. +t'rl
to wary.
tu+
rpt:il9wAytTiwtar.a�em a�oweGY11140tt. BR'<.:WARD 'tunx�rm Mum cro corsmemu wntworaEr�rtr
. I I lhiab itiPrt.�tIlY m..raemrr.twieatr.a.m�ttororm. eao.trt.uetw2mwnntrtrat�mtn.rM.t,,otl
Nob J'cm w/Inw YlwrhMice mmrin ror.r.dertlnp.
Page 58 of 99
Exhibit G
Trunked Radio System
Standard Operating Procedures
Regional Public Safety
Communications —
Radio Sub-Committee
Standard Operating Procedures
For the Broward County Public Safety Intranet
RPSCC RADIO SUB-COMMITTEE
Page 59 of 99
STANDARD OPERATING PROCEDURES
FOR THE BROWARD COUNTY
PUBLIC SAFETY INTRANET
TABLE OF CONTENTS
SOP# PROCEDURE TITLE
1.1 Fleetmap Standards
1.2 Talk Group&Radio User Priority
1.3 Telephone Interconnect
1.4 Private Call
1.5 Radio Aliases
1.6 Radio Model and Features
1.7 Radio Auxiliary Equipment
1.8 Talk Group Names
1.9 Shared Use of Talk Groups
1.10 Scanning Talk Groups
1.11 Emergency Button
1.12 Encryption
1.13 Definitions&Acronyms
1.14 Console Naming
Page 60 of 99
STANDARD OPERATING PROCEDURES(SOP)
800 MHz Trunked Regional Public Safety Radio System
Standards, Protocols, Procedures
Document Section: 1.1 RPSCC Radio Sub-Committee
Sub-Section: Approved Date: 08/02/07
Procedure Title: Fleetmap Standards
Date Established: 12115/06
Replaces Documents Dated: N/A
Date Revised: N/A
1. Purpose or Objective:
The 800 MHz system will contain a large number of talk groups & multigroups to support the
various agencies that will be subscribing to the system.
The System has multiple administrating agencies that will be responsible for maintaining the
Fleetmaps and system programming for the agencies for which they are responsible.
Talk groups must be configured identically by name in the SmartZone Manager Terminal
database, Radio Consoles and the Subscriber Radio. The minimum characters are six (6)
and maximum is 14. The Talk Group number of characters will need to be based upon the
individual agency's subscriber radio model types used within their fleet.
For the effective management of the system a defined process needs to be used to
document the Fleetmap information that each agency is supporting. This information needs
to be in a format that is shared with the other administrators.
2. Technical Background:
• Capabilities:
The Fleetmap is parameter information programmed into the system infrastructure and into
the subscriber radios to control how the radios will behave on the 800 MHz system.
The Fleetmap itself contains the following information:
Page 61 of 99
Fleetmap Information Definition
Talkgroup Name of the talkgroup & multigroup as it is programmed
into the system
Talk group ID Numerical ID of the talkgroup&multigroup
Owner The actual"owning"agency of the talkgroup
Description General description of the talkgroup&multigroup
Multigroup If the talkgroup is part of a multigroup, this will identify the
multigroup
Priority Priority level of the talkgroup
Admin Agency The agency that is responsible for the system
administration for this talkgroup
Site#access Will be a listing of the RF sites individually, and if the
talkgroup is authorized
Media Access If media access is permitted for this talkgroup
Global Sharing The predefined global sharing authorizations
User Groups = The subscriber groups using the talk groups, this becomes a matrix for
programming.
The Fleetmap spreadsheet will become a documented matrix of the talk groups in the system
and the subscriber groups that are using/sharing these talk groups.
3. Operational Context:
The System Managers will be responsible for managing the Fleetmap information of the
users they are representing. This information is also shared with the other system
managers; the ID information also must be kept.
4. 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.
S. Recommended Procedures:
As individual System Managers make updates and changes to their spreadsheets, the
spreadsheet will be e-mailed to the Broward County County's Office of Communications
Technology Radio Communications Manager, the Administrator(for future reference this
person will be referred to as the "Primary Administrator") of the system. This will allow
the Primary Administrator to update the master spreadsheet information easily and
provide the information to the other System Managers for reference and integrity of the
Fleetmap planning process.
Talk groups that are shared between subscribers of different administrating agencies will
be reflected on all the spreadsheets having subscribers using these talk groups. The
portion of the System Manager's spreadsheet containing data on talk group ownership
will be considered the master reference for the Talk group.
The disclosure of the Fleetmap configuration information including Talk Group IDs, user
IDs, user privileges and other related system information would substantially jeopardize
the security of the system from tampering, sabotage, unauthorized use, jamming,
hacking, unauthorized access to the contents of confidential voice and data
Page 62 of 99
communications, etc. Therefore, the master Fleetmap spreadsheets shall be classified
as "Security Information" and "Non-Public Data." The System Managers may choose to
disclose some or all of their own information to their users; however, they shall not
disclose other Agencies' information without prior approval from the responsible System
Manager.
6. Manaciement:
The System Managers Group will manage the Fleetmap information and the details of the
process for communicating the information.
Page 63 of 99
Standard Operating Procedures(SOP)
800 MHz Trunked Regional Public Safety Radio System
Standards,Protocols, Procedures
Document Section: 1.2 RPSCC Radio Sub-Committee
Sub-Section: Approved Date: 08/02/07
Procedure Title: Talk Group&Radio
User Priority
Date Established: 12/15/06
Replaces Document Dated: N/A
Date Revised: N/A
1. Purpose or Objective:
The purpose of establishing varying priority levels for talk groups is to assure the most critical
talk groups on the system are granted a channel as quickly as possible when the system is
experiencing busy conditions.
2. Technical Backaround:
■ Capabilities
The system priorities can be managed at the user level and at the
Talk Group level.
■ Constraints
All User Priorities will be set at 10, as radio users change talk
groups,their effective priority will be set by the Talk Group that they are on.
3. Operational Context:
Priority levels in the system will be managed at the Talk Group level. The goal is to distribute
priorities across the systems talk groups in a way that maximizes the ability for critical groups to
communicate and minimizes the number of talk groups with high priority. All User Priorities will
be set to the lowest priority level, 10.
4. 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.
Priority 1 Definition — EMERGENCY: Only Emergency Alert calls, i.e. emergency button
pressed, will be given the Priority 1 status. Definition of an EMERGENCY means when a public
safety radio subscriber encounters a life-threatening situation and needs help by activating their
emergency button which then activates their designated dispatcher's radio console with an
emergency alert.
Priority 2 Definition—Unassigned
Priority 3 Definition—Unassigned.
Priority 4 Definition—Public Safety Talk Groups
Page 64 of 99
Priority 5 Definition—Low Priority Public Safety Talk Groups
Priority 6 Definition—Unassigned
Priority 7 Definition—Local Government Essential
Priority 8 Definition—Unassigned:
Priority 9 Definition—Local Government Non-Essential
Priority 10 Definition—PRIVATE&INTERCONNECT CALLS: Will be used for
Telephone Interconnect Calls, Private Calls as defined by direct point-to-point or radio-to-radio
communications that are not carried out within a talk group. This priority will also be used for talk
groups that are established for system testing.
5. Recommended Procedures:
N/A
6. Management:
The RPSCC Radio Sub-Committee is responsible for supervision and management of this
procedure.
Page 65 of 99
STANDARD OPERATING PROCEDURE(SOP)
800 MHz Trunked Regional Public Safety Radio System
Standards, Protocols, Procedures
Document Section: 1.3 RPSCC Radio Sub-Committee
Sub-Section: Approved Date: 08/02/07
Procedure Title: Telephone Interconnect
Date Established: 12/15/06
Replaces Document Dated: N/A
Date Revised: N/A
1. Purpose or Objective:
To manage the use of interconnect on the system. Although this is a useful feature and needed
by some users, it must be managed to an appropriate level to protect the primary radio
communications purpose of the system.
2. Technical Backaround:
■ Capabilities
Interconnect calls can be placed to individual users of the system, if they are configured
for interconnect functionality. Interconnect calls can be placed to talk groups of the
system, if the Talk Group is configured for interconnect functionality.
Interconnect is intended to be a BACKUP functionality to cellular
communications and used primarily on an emergency basis.
■ Constraints
o An interconnect call will consume an RF channel for the duration of the call.
o Interconnect calls are half duplex; only one end can talk at a time.
o A type 1 portable cannot initiate an interconnect call.
o A type 2 portable can only place calls to numbers that are pre-programmed into
the radio.
o A type 3 portable can place an interconnect call by dialing the number directly.
o The general public can easily monitor the interconnect calls and they are NOT
private or protected in any way.
o Interconnect shall NOT be utilized to conduct confidential business such as
discussing case strategy with the State Attorney's Office.
3. Operational Context:
If a radio user has a need for interconnect, it shall be granted, but the resources impact needs to
be carefully managed. Due to the risk of cutting off emergency/life safety communications, the
duration of interconnect calls shall be set to a time limit of two (2) minutes. Only one channel
within a radio system will be allowed the feature of Telephone Interconnect. The need to make a
Telephone Interconnect call must be restricted to emergency and business related use. The City
of Fort Lauderdale has two (2) channels available for the users that are allowed the Telephone
Interconnect feature; however, they do not permit other agencies to utilize their Interconnect
resources.
4. Recommended Protocol/Standard:
Interconnect usage shall only be programmed for the users of the system that have a need for the
Page 66 of 99
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.
5. Recommended Procedures:
The System Managers need to define and manage the interconnect properties of the RF
subsystem(s) that they are responsible for. Each RF subsystem can be configured individually
for the number of calls that they will be allowed to simultaneously carry.
6. Manacement:
The System Managers shall be responsible for following this procedure and monitoring the effect
and usage of this resource. If negative impact or excessive usage is determined, interconnect
permission will be reconsidered and possibly revoked. Definition of"negative impact or excessive
usage is defined as individuals who are reported for using this feature for non-emergency and/or
non-business related matters.
Page 67 of 99
STANDARD OPERATING PROCEDURE(SOP)
800 MHz Trunked Regional Public Safety Radio System
Standards,Protocols, Procedures
Document Section: 1.4 RPSCC Radio Sub-Committee
Sub-Section: Approved Date: 08/02/07
Procedure Title: Private Call
Date Established: 12/15/06
Replaces Document Dated: N/A
Date Revised: N/A
1. Purpose or Objective:
To manage the use of private call on the system, although this is a useful feature and needed by
some users, it must be managed to an appropriate level to protect the primary radio
communications purpose of the system.
2. Technical Backaround:
■ Capabilities
Private calls can be placed to individual users of the system, this communication is
outside of the Talk Group communications, and is a private communication between two
radio users. Console operators can place private calls to the radio users.
■ Constraints
o A private call will consume a RF channel for the duration of the conversation.
o Private calls are half-duplex, only one end can talk at a time.
o A type 1 portable cannot initiate a private call.
o A type 2 portable can only place private calls to numbers that are pre-
programmed into the radio.
o A type 3 portable can place a private call by dialing the number directly.
o Private calls are not recorded.
o For the duration that a radio user is involved in a private call,the user will not be
involved in dispatch/Talk Group communications.
o The system is not able to restrict the usage of private call on the system, unlike
interconnect calls,which can be managed.
3. Operational Context:
The private call resource should primarily be used as a supervisory function, if there is a business
need for a radio user to have this ability, it should be granted, but the resource overall needs to
be managed to protect the RF resources of the system. This is also a function that dispatch
consoles overall would be capable of. Due to the risk of cutting off emergency / life safety
communications, the duration of Private Calls must be set to a time limit of two (2) minutes. The
number of channels that allow the feature of Private Call will be determined by the individual
System Manager. The need to make a Private Call must be restricted to emergency and
business related use. Radio users of the Private Call feature must understand that when this
feature is being used,they cannot hear a Dispatcher call.
4. 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
Page 68 of 99
call is managed in the"Sites Profile Group"that the radio user belongs to.
5. Recommended Procedures:
System Managers shall work with the user groups they are responsible for to plan the appropriate
private call programming requirements for those users, in order to protect the RF resources of the
system.
6. Management:
The System Managers shall be responsible for following this procedure and monitoring the effect
and usage of this resource. If negative impact or excessive usage is determined, private call
permission will be reconsidered and possibly revoked. Definition of"negative impact or excessive
usage is defined as individuals who are reported for using this feature for emergency and/or non-
9 P 9 9 Y
business related matters.
Page 69 of 99
STANDARD OPERATING PROCEDURES(SOP)
800 MHz Trunked Regional Public Safety Radio System
Standards, Protocols, Procedures
Document Section: 1.5 RPSCC Radio Sub-Committee
Sub-Section: Approved Date: 08-02-07
Procedure Title: Radio Aliases
Date Established: 12/15/06
Replaces Document Dated: N/A
Date Revised: N/A
1. Purpose or Objective:
The purpose of this section is to set forth the principle by which all radio users in the regional
system will establish names for their radios in order to ensure that there are no duplicate names,
and also to facilitate intuitive understanding of the radio name.
2. Technical Backaround:
■ Constraints
Every Radio User ID in the system has to be unique; there can be no duplicate lDs. The Radio
User Alias field itself will hold up to 14 characters and the legal values that the system will accept
are: Upper Case Alpha, Numeric, Period, Dash, Forward slash, Number sign.
When agencies make additions, deletions and changes to the database for Radio Aliases the
modifications will not take effect until Motorola performs a database back-up that will occur every
Friday. The Dispatch consoles will not reflect these modifications until that step is taken.
3. Operational Context:
With the exception of the first three(3)characters users are technically free to choose any unique
name they wish for their radio aliases. However, since this is a shared system Radio User
Aliases that are programmed into the system must have naming conventions between agencies
that will not conflict with each other.
4. 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
refixes of at least two digits that would stand alone. Counties would be re-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.
Region 7 Operating Agencies and Broward County Region Agencies will have a naming prefix of
at least two(2) letters that would describe their area. The naming standard only governs the first
two characters; the characters following the first two are at the individual agency's discretion, for
example; the agency may opt to internally use more than two characters for the internal
identifications.
Page 70 of 99
The following are suggestions for the body of the subscriber alias name. The body of the alias
would contain an agency's identification for the individual or pool radio etc., possibly the radio
user's call sign as an example. The alias could be suffixed with identification for the radio itself,
such as a"-P"for portable for example to differentiate between a mobile&portable radio used by
the same person. This would allow Dispatchers & System Managers to readily identify radio
users and if the radio is a portable or a mobile.
Lost radios or radio IDs that are not associated with a radio user or console: A possibility for
locating unused radios in the system that are lost, or not assigned to subscribers would be to
temporarily prefix the radio serial number with a dash "-"at the time the radio is lost, or when the
radio user is assigned to another radio. A report of these radios can be created by the
SmartZone configuration reports tool and setting the radio selection criteria to "Radio Serial #,"
Start range-0, End range-999999.
A master list of Radio User Aliases will be created and maintained in the system. They will be
readily accessible through the data terminal for all who have rights on that part of the system. As
alias names are created and approved they will be placed on this master list so as to be available
for all appropriate parties for operations and planning.
REGIONAL SYSTEM NAMING PREFIXES
2-3 Character Prefix Name of the Agency using the Prefix
BC Broward County Local Government
BCP NPSPAC Mutual Aid
BCSB Broward County City
BSO Broward Count 's Office Police and Fire Rescue
CC Coconut Creek
CM Communications—Joint Operations
CS Coral Springs
DV Davie
DB Deerfield Beach Fire Rescue
DN Dania Beach Fire Rescue
FL Fort Lauderdale
FSO Motorola Field Service Operation FSO
HB Hallandale
HBB Hillsboro Beach
HW Hollywood Police, Fire Rescue and Local Government
LH Lauderhill
LP Lighthouse Point
MED Broward County MEDCOM
MG Mar ate
MM Miramar
OP Oakland Park
PB Pompano Beach Local Government
PB Pompano Beach Fire Rescue
PL Plantation
PP Pembroke Pines
SEM Seminole Tribe
SN Sunrise
WM Wilton Manors
5. Recommended Procedures:
N/A
Page 71 of 99
6. Manaeement:
The System Managers are responsible for seeing that the defined standard is followed and
maintained.
Page 72 of 99
STANDARD OPERATING PROCEDURES(SOP)
800 MHz Trunked Regional Public Safety Radio System
Standards, Protocols, Procedures
Document Section: 1.6 RPSCC Radio Sub-Committee
Sub-Section: Approved Date: 08/02/07
Procedure Title: Radio Model and Features
Date Established: 01/04/07
Replaces Document Dated: N/A
Date Revised: N/A
1. Purpose or Objective:
The purpose of this section is to set forth the recommended standards by which all 800 MHz
radio users in the regional system will agree to purchase subscriber radios that are defined in this
standard. This standard is to ensure that radios that are not in compliance do not affect the radio
system. This document will be revised after the RPSCC approves the purchase and
implementation of a new APCO P25 700 MHz radio system and the manufactured radio models
have been identified to work with the P25 system.
2. Technical Background:
■ Constraints
Radios must meet the recommended standards as set forth. These standards identify the proper
radio to be used in conjunction with the required features and auxiliary equipment (to be
described in Section 1.7) Each subscriber radio will be assigned it's unique Radio ID number,
Alias Name and programmed with a codeplug/template that has been approved by the user's
upper level management.
3. Operational Context:
All radios are programmed with the required Talk Groups, Mutual Aid (Local and Statewide) and
features to allow it to operate on the 800 MHz Trunked radio system. Codeplugs/templates are
created by the individual agencies radio shop or their contracted vendor.
4. Recommended Protocol/Standard:
In order to meet these requirements the following information describes the minimum standards
that must be considered when new radios are purchased. Radios of various manufacturers and
models are capable of operating on this network. The Network currently consists of a Motorola
SmartZone 3600 Baud Control Channel infrastructure. It is recommended that mobiles and
portables be capable of operation with SmartZone features to permit the automatic roaming
between sites as the users move out of range of their home system. SmartNet radios can be
utilized where there is no intention of providing the automatic roaming features. With an eye to
the future, where P25 and 700 MHz may be introduced, it is recommended that the subscriber
units with a life expectancy past 2009 be either upgradeable or be equipped to operate on 700
MHz using the P25 protocol. For Public Safety users it is strongly recommended that the current
Motorola products be utilized. System Managers can advise on the appropriate features,
functionality and options to purchase. As a minimum, all radios shall have the ability to be
assigned a unique individual ID number for system access, have the ability to be inhibited by
command from the System Management tools and have an adequate talkgroup/channel capacity
to permit the Local, Regional and National Mutual Aid talkgroups and channels to be programmed
along with local agency requirements. The radios shall be capable of operating both in
conventional mode and Motorola Trunking modes. There are other Trunking protocols that are
Page 73 of 99
not compatible, and radios utilizing these protocols shall not be authorized. These protocols
include, but may not be limited to, Privacy Plus, EDACS, LTR and TETRA.
Mobile Radios shall have their power set to the lowest possible value. The radio systems in
Broward County are designed to work in-building with portable radios. Constraints are placed
upon the acceptable mobile radio power levels that should be utilized by this in-building design
and the close spacing of the frequencies utilized by the network. Excessive power can cause
undesired interference to the other users on the network. Older model radios shall be set to the
lowest power permitted by their design, typically the half-power point. Non-Public Safety mobiles
shall utilize 1/4 wave antennas, not gain style antennas.
Any Public Safety user that desires to utilize a high power setting for a specific System's Talk
Groups shall obtain permission from the System Managers. The radios shall be programmed to
power up in the low power mode and require a positive action on the part of the user to increase
the power level. There shall be policies and procedures written to address the use of high power
only after communications are unsuccessful when using the low power setting, and when working
outside the primary coverage area of the network. If wide area talkgroups are involved, the
totality of the wide area coverage, and not that of a more restricted coverage system, shall
determine if high power usage is appropriate.
PORTABLE RADIO STANDARDS
Model XTS2500 XTS2500 XTS2500 XTS5000 XTS5000 XTS5000 XTS1500
Description Model I Model 11 Model III Model l Model 11 Model III Model I
Digital 0 0 0 O O O 0
SmartZone 0 0 0 O 0 0 0
Dual Mode S S S S S S S
800/700 MHz
capable
Project 25 0 0 0 0 0 0 0
9600 SW
RF Switch S S S S S S S
(764-806
MHz)
(808-870
MHz
Encryption 0 0 0 0 0 0
Software
Encryption 0 0 0 0 0 0
Hardware
Multi-Key 0 0 0 0 0 0
(Required only
if other
System Talk
Groups are
programmed
in the radio
Page 74 of 99
MOBILE RADIO STANDARDS
Model Description XTL1500 XTL2500 XTL5000
Digital O O
Dual Mode 800/700 S S S
MHz capable
SmartZone O O
P25 9600 Software O O O
ID Display O O
Encryption Software O O O
Encryption Hardware O O
Multi Key (Required O O
only if other System
Talk Groups are
programmed in the
radio
Remote Control Head O O
S=Standard Feature
O=Optional Feature
5. Recommended Procedures:
N/A
6. Manasiement:
The System Managers are responsible for seeing that the defined standard is followed
and maintained.
Page 75 of 99
STANDARD OPERATING PROCEDURES(SOP)
800 MHz Trunked Regional Public Safety Radio System
Standards, Protocols, Procedures
Document Section: 1.7 RPSCC Radio Sub-Committee
Sub-Section: Approved Date: 08/02/07 _
Procedure Title: Radio Auxiliary Equipment
Date Established: 01/04/07
Replaces Document Dated: N/A
Date Revised: N/A
1. Purpose or Objective:
The purpose of this section is to set forth the recommended standards by which all 800 MHz
radio users in the regional system will agree to purchase subscriber radios auxiliary equipment
that are defined in this standard. This standard is to ensure that radios that are not in compliance
do not affect the radio system. These standards will be revised once the RPSCC has purchased
and implemented a new APCO P25 700 MHz radio system and the radio model types have been
identified to work with the P25 radio system.
2. Technical Background:
■ Constraints
Radios must meet the recommended standards as set forth when auxiliary equipment is needed
by the individual radio subscriber to perform their job. These standards identify the proper radio
auxiliary equipment to be used in conjunction with the radio subscribers model type.
3. Operational Context:
All radios must meet these specific requirements for antennas and batteries when installed on a
subscriber's radio. Failure to utilize the manufacturer's recommended standards for the radio
auxiliary equipment may cause Law Enforcement and/or Fire Rescue field force personnel to
experience static, interference or audio communication breakdown with their assigned
Dispatchers. While it is recognized that it is desirable to utilize the accessories manufactured by
the radio manufacturer, there are alternative after-market accessories that provide performance
equivalent to the manufacture's items, or functionality not available from the Original Equipment
Manufacturer(OEM). The permissibility of these after-market items shall be determined by the
System Manager after performing a technical evaluation to insure a performance level equivalent
to the OEM items.
4. Recommended Protocol/Standard:
In order to meet these requirements the following information describes the minimum standards
that must be considered when new auxiliary radio equipment is purchased.
Antennas: Radio antennas shall be either the OEM part or an equivalent as determined by
the System Manager. No antenna shall be used that is not pre-approved. In no cases shall
"cellular" or shortened stubby designs be permitted unless technical testing confirms that the
radiated energy is within 1 dB of the OEM antenna radiation. Testing shall be performed under
the direction of the System Manager, not the end user.
Batteries: The battery is the life-blood for the radio and can have a major impact on the
radio performance over the course of a shift. It is encouraged that each Public Safety user will
have a spare charged battery available. In car charges are an option, either the OEM version or
Page 76 of 99
the AdvanceTec model as appropriate for the radio model in use. These shall only be utilized to
charge the spare battery. It is highly encouraged that OEM batteries be utilized as they have
proven to present fewer quality and performance issues then many of the after-market products.
After-market batteries shall be evaluated prior to implementing their use. Testing shall include fit
and finish, drop tests, vibration, cycle capacity, long-term capacity and self-discharge after the
battery has been in use for six (6) months. Testing shall be on a representative sample of the
after-market manufacturer's product.
Speaker/Microphones: Speaker/Microphones come in two basic styles; Public Safety—equipped
with an antenna; Standard — usually equipped with a coiled cord and does not have antenna.
The radio system coverage is predicated upon the use of a Public Safety microphone with the
appropriate antenna installed on the microphone. Use of Standard speaker/microphones for
users that ride in vehicles is discouraged due to the significant range reduction caused by having
the antenna below the vehicle glass level and shielded by the vehicle's construction. They may
be utilized by bicycle and motorcycle units with the understanding that when radio user is in a
vehicle, the coverage may be significantly reduced.
Surveillance kits such as the two or three wire kits, and ComPorts also utilize the antenna
mounted on the radio. The same in vehicle coverage issues apply to these units.
After-market microphones, surveillance kits, etc. require technical evaluation by the System
Manager before they are promoted to the end users.
The following are the manufacturer's recommend standard speck to radio models MTS2000
(antennas only),XTS3000 and XTS5000(batteries only) series.
Antenna:
• 806—870 MHz—'/"Wavelength Whip(MTS2000 only)
• 806—941 MHz—%"Wavelength Whip(MTS2000 only)
Public Safety Microphone(Models MTS2000.XTS3000 and XTS5000):
• Straight Cable 30 inches
• Straight Cable 24 inches
• Straight Cable 18 inches
• Command Shoulder Speaker(water-proof) microphone
Batteries for Portable Radios(Models MTS2000.XTS3000 and XTS5000):
• Nickel-Cadmium 7.5 volt Battery(MTS2000)
• Ultra-High Capacity Battery(MTS2000)
• High Capacity NiCD
• High Capacity NiCD FM
• High Capacity NiMH
• High Capacity NiMH FM
• High Capacity NiMH Rugged FM
• High Capacity Lithium Ion
• NiCAD(State approved)
5. Recommended Procedures:
All Antennas, Public Safety Shoulder Mics and Batteries must meet the specifications identified in
this standard, protocol and procedures. It is strongly recommended that all after-market vendors
Page 77 of 99
work through the System Managers to present their products for evaluation before they contact
the end users. End users shall refer all vendors to their System Manager before entertaining the
use of an after-market product that connects to, attaches to, or otherwise involves the subscriber
units and/or the radio system.
6. Manaaement:
The System Managers are responsible for seeing that the defined standard is followed and
maintained.
Page 78 of 99
STANDARD OPERATING PROCEDURES(SOP)
800 MHz Trunked Regional Public Safety Radio System
Standards, Protocols, Procedures
Document Section: 1.8 RPSCC Radio Sub-Committee
Sub-Section: Approved Date: 04/08/08
Procedure Title: Talk Group Names
Date Established: 01/04/07
Replaces Document Dated: 08/02/07
Date Revised: 04/08/08
1. Purpose or Objective:
The purpose of this section is to set forth the principals by which all radio users in the regional
system will establish names for Talk Groups (TG) and to facilitate intuitive understanding of the
TG name. The TG naming standard is also essential because, in keeping with the regional
interoperability concept, some TG's will be shared by multiple agencies.
2. Technical Background:
All TG names programmed in the County's 800MHz Trunked Radio System must be unique and
consistent from Zone Manager to subscriber. Due to the fact that the newer subscriber units will
have a maximum of twelve (12) characters on their display, TG length will be limited to a
maximum of twelve (12) characters. When possible, subscriber TG will be consistent with the
console database and zone controller. Any subscriber with less than eight (8) characters display
will be handled on a case by case basis.
3. Operational Context:
With the exception of the first four (4) characters (see Appendix A), the System Managers are
technically free to choose any unique name they wish for TG's assigned within their partition
(maximum of twelve(12) characters). The NPSPAC Mutual Aid conventional TG's are assigned a
name that is known nationwide. When possible, subscriber TG will be consistent with the console
database and zone controller. Any subscriber with less than eight (8) characters display will be
handled on a case by case basis.
4. 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.
Page 79 of 99
5. Recommended Procedures:
N/A
6. Manasiement:
The System Managers are responsible for seeing that the defined standard is followed and
maintained.
Page 80 of 99
Appendix A
Purpose:
The following is required in order to standardize and document talk group naming
convention for the Broward County SmartZone 800Mhz Trunked Radio System.
Description:
The first two characters of the talk group alias identifies the talk group governing
entity/municipality.The third character identifies the department/agency within the governing
entity/municipality.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 model,character display may be smaller or larger.Any subscriber displays that
are under eight(8)characters will be handled,by the Radio System Administrator,on a case by
case basis.See examples below.
Example 12 character display
P Pall
'-' ZZZZZZZZ
Talk group alias name
Dash separator
Ingle Letter Department Identifier(see Table 2).
T o Letter Identifier(see Table 1).
example: JiMIGO.M.1—ij D I I I S I P I - 14 1 A = PSB/BSO dispatch channel Disp4A
example: D I I I S I T - 11 = FTL dispatch channel"Dist-1
Note:Depending on the subscriber model,character display
may be smaller or larger.There is a max of twelve(12)
characters allowed for talk group alias names.
Example 8 character display
lC_'Xi Y,_ Z Z Z Z
1 Talk group alias name
Dash separator
Ingle Letter Department Identifier(see Table 2).
TVXO Letter Identifier(see Table 1).
example: a M D S I P 14 = PSB/BSO dispatch channel"Disp4A"
example: F I L,P - D�-Tn= FTL dispatch channel"Dist-1"
Note:Depending on the subscriber model,character display
may be smaller or larger.There is a max of twelve(12)
Page 81 of 99
Tables
Table 1 Table 2
BC Broward County A Aifport
BS Broward Sheriff Office B FUTURE USE
CC Cooper City C Communications
CK Coconut Creek D FUTURE USE
CS Coral Springs E Port Everglades
DN Dania F Fire Rescue
DR Deerfield G FUTURE USE
DV Dame H FUTURE USE
FL Fort Lauderdale I FUTURE USE
HA Hialeah, Miami Dade Ct . J FUTURE USE
HD Hallandale K FUTURE USE
HW Hollywood L Local Gorremment
LH Lauderhill M Mutual Aide
LL Lauderdale Lakes N FUTURE USE
LP Lighthouse Point
LS Lauderdale by the Sea P Police
LZ Lazy Lake Q FUTURE USE
MC City of Miami, Miami Dade Ct . R Parks&Rec
MB Miami Beach, Miami Dade Ct . S School
MD Miami-Dade County T FUTURE USE
MG Margate U FUTURE USE
MM Miramar V FUTURE USE
NIL North Lauderdale W FUTURE USE
OP Oakland Park X FUTURE USE
PC Palm Beach County Y FUTURE USE
PB Pom ano Beach Z FUTURE USE
PD Parkland
PK Pembroke Park
PL Plantation
PP Pembroke Pines
SF State of Florida
SM Seminole
SN Sunrise
SR Sea Ranch Lakes
SW Southwest Ranches
TM Tamarac
WM Wilton Manors
WP West Park
WS Weston
*To be used only by Broward Sheriffs Office
Page 82 of 99
STANDARD
S OPERATING PROCEDURES(SOP)
800 MHz Trunked Regional Public Safety Radio System
Standards, Protocols, Procedures
Document Section: 1.9 RPSCC Radio Sub-Committee
Sub-Section: Approved Date: 08/02/07
Procedure Title: Shared Use Of
Talk Groups
Date Established: 01/04/07
Replaces Document Dated: N/A
Date Revised: N/A
1. Purpose or Objective:
The intent of this standard is to provide an option to the users of the 800 MHz system, which will
allow the talk group owners to "at their discretion" predefine sharing authorizations for other
agencies.
2. Oaerational Context:
Talk Groups are considered to be "Owned" by the agency requesting the creation of the Talk
Group, similar to the ownership that applies to conventional RF resources. As the owner of the
Talk Group the owning agency has the authority and control to define who can and cannot use
the Talk Group and to what"degree. Traditionally this process has been primarily accomplished
with"letters of authorization."
The optional method to simplify this process is for the owning agency to predefine sharing
authorization, as diagrammed in the table example below.
The predefined authorizations would be kept in the Talk Group spreadsheet maintained by the
System Managers. These spreadsheets would be shared between the System Managers, and
would be a reference available for Talk Group planning. If an agency does not pre-define sharing
authorization for a particular talk group,the default will be a"P"as defined below.
3. 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 speck 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 3 Authorized to transmit and receive.
4. Recommended Procedures:
The System Managers, working with the user groups, would perform this task.
Page 83 of 99
5. Management:
The System Managers are responsible for the management of this procedure. The larger table
is also used to layout the Fleetmap information as described in this manual in Section 1.1,
Fleetmap Standards.
Talk Group Owning Agency Description Administrating Global Sharing
Agency Authorizations
P= Permission
letter required to
gain
authorization for
use
D=Defined Use
—Letter required
L=Like
agencies may
share"Fire,
Medical, Law,
Works"etc.
A=All agencies
RX=Are only
authorized to
receive
TX=Are
authorized to
receive&
transmit
Talk Group 1 D-TX
Talk Group 2 L-TX
Talk Group 3 A-TX
Talk Group 4 P-RX
Talk Group 5 P-TX
Talk Group 6 D-TX
Talk Group 7 L-TX
Talk Group 8 A-TX
Talk Group 9 P-RX
Talk Group 10 P-TX
Talk Group 11 D-TX
Talk Group 12 L-TX
Talk Group 13 A-RX
Talk Group 14 P-RX
Etc. P-RX
The "RX" option shown in the table is an authorization that permits receive only use, although the radio
would be technically capable of transmit(TX)operation on the talk group.
Page 84 of 99
STANDARD OPERATING PROCEDURES(SOP)
800 MHz Trunked Regional Public Safety Radio System
Standards, Protocols, Procedures
Document Section: 1.10 RPSCC Radio Sub-Committee
Sub-Section: Approved Date: 08/02/07
Procedure Title: Scanning Talk Groups
Date Established: 01/04/07
Replaces Document Dated: N/A
Date Revised: N/A
1. Purpose or Objective:
This procedure is to identify operational procedures and responsible authorities governing
Scanning activities as it relates to the Scan function in the individual subscriber radio.
2. Technical Background:
■ Capabilities
The network infrastructure and subscriber units need to be configured to permit managed
user Scanning of Talk Groups. Whether or not Scanning will be utilized in subscriber
radios, it is at the option of the user agency. Users also need to be trained that merely
including a Talk Group in a non-priority Scan list will not necessarily result in the user
hearing traffic on that Talk Group. The Talk Group must also be"active"at the site where
the user is affiliated. Talk Groups are active on a site if the Zone Controller is
programmed to allow the Talk Group to appear on that site and there is at least one user
affiliated at the site which has the Talk Group of interest as their selected channel.
■ Constraints
How the radio is programmed to handle wide area and local sub-system Talk Groups will
determine priority Scan capabilities. If the local sub-system Talk Groups is not
programmed to the same "system" in the radio, they cannot be included in the priority
monitor Scan list. In this case, only Talk Group Scan can be implemented. Priority Scan
requires System Infrastructure configuration in order to perform as expected. The Talk
Groups that are deemed to be Priority Monitor Groups need to be configured as such by
the System Managers. There are practical limitations on the overall number of Priority
Monitor Groups that can be enabled due to the amount of time required to distribute the
list of active Talk Groups to the radios in real-time. Talk Group Scan does not provide a
priority feature to direct the radio to the priority Talk Group. Talk Group Scan can Scan
Talk Groups from different systems (as defined in the radio internal programming) and
conventional channels. It is strongly recommended that "talkback Scan" not be used.
Talkback Scan would direct the user to transmit on the last active Talk Group the radio
heard traffic on. This will cause confusion as the radio user will not know what Talk
Group the radio will be transmitting on as it will constantly change based upon what the
radio last received. Scan is not recommended for those users that must hear critical
communications.
While Scanning will be available on the systems it will necessarily be limited and,
therefore, not be as robust as in conventional radio systems.
3. Operational Context:
The network infrastructure and subscriber units will be configured to balance the ability for users
Page 85 of 99
to achieve wide area coverage where necessary, and maintain an acceptable level of service for
all users. The use of"Critical User"and"Critical Site" in the system for the purpose of non-priority
Scanning is not permitted and Scanning between different sites will be accomplished by the use
of"requested sites."
Before priority Scanning is allowed on an individual subscriber's radio, it must be pre-approved by
the agency's management and/or command.
Additionally, priority Scanning of Talk Groups must be evaluated by the System Manager to make
sure the radio system is not affected by the use of this feature.
4. Recommended Protocol/Standard:
Limited Scanning/monitodng 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.
S. Recommended Procedures:
Permission:
If the Talk Group does not appear on the approved Scanning list, permission must be obtained in
writing from the Talk Group owner and the System Manager of the non-home site or sites being
"requested" if applicable.
Scanning Configuration:
If trunked Scanning is desired, it is recommended that Scanning should normally be limited to
owned trunked Talk Groups which are affiliated with their"always preferred site(s)".
It is further recommended that Scanning normally be disabled when the user leaves the system
and switches their radio to a conventional (non-trunked) channel. However, if mixed mode
Scanning (both trunked Talk Groups and conventional channel members) is required by some
users, it is also recommended that this Scan type only be available when the radio is selected to
a conventional channel. This is because mixed mode Scan does not provide priority reverts and
the user will typically miss substantial portions of conversations on the selected channel.
Talkback Scan is highly discouraged, as the user cannot control the Talk Group used to transmit.
Can lists can be either programmed into the radio with no user access for changes,or the list can
be made accessible for user modifications. It is preferred that the list is made user configurable
to allow those users that can handle Scan to determine what they want to listen to and make
changes"on the fly"as their requirements change.
Scanning of Non Home Site Talk Groups:
It is possible to monitor a non-home Talk Group by configuring the system to request the desired
non home Talk Group appears on your primary/home system or"always preferred site(s)". Doing
so however, will consume a repeater channel on your primary/home system or"always preferred
site(s)" and will carry the requested non-home Talk Group priority setting with it. Also, a call on
the requested non-home Talk Group will not be delayed (busy queued) if the home system or
Page 86 of 99
"always preferred site(s)" does not have a channel available. This however may cause
unacceptable conditions where the majority of users do not receive the call while the dispatcher
or calling party has no indication that a large segment of their users did not receive the call.
While this "requested site" is the recommended approach, it must be carefully controlled,
monitored and evaluated due to the potential to exhaust system resources. It must be approved
by the affected System Managers.
6. Management:
The System Managers will be the final authority for controlling the Scan feature and Scanning
issues. The agency's management and/or command will have the authority to
approve/disapprove this feature for their users.
Page 87 of 99
STANDARD OPERATING PROCEDURES(SOP)
800 MHz Trunked Regional Public Safety Radio System
Standards, Protocols, Procedures
Document Section: 1.11 RPSCC Radio Sub-Committee
Sub-Section: Approved Date: 08/02/07
Procedure Title: Emergency Button
Date Established: 01/04/07
Replaces Document Dated: N/A
Date Revised: N/A
1. Purpose or Objective:
There will be a large variety of users on the radio system with various Emergency Button needs.
The various ways the emergency key can be configured will allow for flexibility of use, however, it
is important to design the system in such a way that when an Emergency Button is pushed, it is
responded to quickly and appropriately.
2. Technical Backaround:
■ Capabilities
The "Emergency Button" feature, if it is programmed into the subscribing agency radios,
will allow a radio user to send an emergency notification by pressing the speck
Emergency Button on the radio. The notifications will audibly and visually alert all
dispatch console positions that have the talk group up that the emergency notification is
routed to. Other radios that have the talk group selected will also receive the emergency
notification, and display the radio ID of the radio generating the emergency. The display
of an ID is dependent upon radio model, firmware version, and purchased options. The
user activating the Emergency Button has the obligation to properly cancel the activation
by pushing—and holding the Emergency Button until a continuous tone sounds. Failure
to properly cancel the alarm on the originating radio will cause a new alarm activation
each time the user transmits.
Emergency calls are also automatically assigned the highest priority available and would
be the first available from the queue if the system is in a busy situation. Subscriber's
radios can optionally be configured to automatically activate the Push-to-Talk (PTT)for a
programmed period of time if the Emergency Button is pressed.
■ Constraints
Consider two situations a fire department engine company could be faced with,that show
different operational needs:
1. An engine company responds to a medical at a private home. Upon entering the
home,they are met by an out-of-control person who fires a handgun at them.
2. An engine company is conducting an interior fire attack when the floor collapses,
trapping them in the basement.
In the first example, a firefighter may push his Emergency Button as he is running out of
the home. He may want it to signal his dispatcher on the main talk group. The
dispatcher would immediately see the signal, assess the situation, and send the police to
assist.
Page 88 of 99
In the second example, a firefighter may push his Emergency Button, and have it send
the signal on his fire ground operations channel. The on-scene safety officer would
attend to this signal by immediately sending in a rescue crew comprised of people
already at the scene.
The design should also avoid the instance where an Emergency Button is pressed, and
nobody can identify the user, or the wrong people attend to the emergency. Such a
situation would occur if a police officer's Emergency Button were configured to signal on
a Main Channel talk group. In that case, pressing his Emergency Button would probably
signal every police dispatch console on the radio system.
Another example is that a public health official pushing the button when alone in a
dangerous situation. If the public health official's radio were configured to signal on the
County main dispatch talk group, but is unknown to the dispatcher, the dispatcher may be
confused by who is in distress, and may not know how to respond. This example shows
the importance of an agreement between the central monitoring agency and the radio
user agency.
Emergency Button programming cannot be configured on a talk group by talk group
basis. This function is defined within the radio personality consisting of a group of 15 talk
groups. The personality may be configured to direct the radio to a speck talk group or
to use the current selected talk group of the talk groups within the personality.
Emergency Button configuration requests shall be discussed with the System Manager of
the affected System as radio programming codeplugs are impacted.
It is recommended that non-Public safety, i.e. Public Service, or general government,
users not have the Emergency Button functionality unless appropriate training and
monitoring resources are available to respond to the alarms. Non-public safety
emergency alarms shall not be directed to a Public Safety Talk Group unless the Public
Safety Dispatch Center responsible for the Talk Group agrees to assume responsibility
for the alarms.
3. Operational Context:
An Agency may choose to utilize the Emergency Button functionality, or to disable its use. If an
Agency chooses to use the Emergency Button it shall be utilized as an indication of an immediate
threat to life or property. Use of the Emergency Button to advance a routine Talk Group call in
the priority cue is not an accepted usage. Agencies may choose to have the emergency
activations occur on a primary dispatch Talk Group, or be directed to a specific Talk Group set
aside to handle Emergency Activations. Agencies that may have access to the Talk Groups from
other Agencies in their consoles will receive the emergency activation notifications if that Talk
Group is active in a folder in the console operator position. Agencies shall NOT
acknowledge/silence/cancel emergency activations from another Agency without contacting that
agency before taking action. To do so may cause a valid emergency alarm to go unanswered.
Any Agency that acknowledges/silences/cancels emergency activations from another Agency
more than 3 times, without contacting that agency before taking action, shall remove the other
Agency Talk Groups from their consoles within 30 days of receiving notification from the Talk
Group owner or System Manager.
Subscriber units that send an excessive number of false emergency alarm activations shall be
located and corrected by the subscriber owner agency as expediently as possible. Excessive is
determined to be four(4) or more false alarm activations within a 24-hour period. The subscriber
owner agency shall take all steps necessary to locate and correct the false activations. There are
circumstances where it is not possible to stop the false activations by attempting to inhibit the
radio or by removing the radio authorization record from the system databases. In these cases
Page 89 of 99
the radio must and shall be located by the Owner Agency and brought to the servicing vendor for
repairs within 30 days of the first false activation. Dispatch Centers shall report all instances of
excessive false emergency alarm activation to their System Manager. The report shall include
the date, time and Talk Group the emergency occurred on, along with either the subscriber alias
or displayed radio ID#.
4. 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.
1. Agencies are not required to use this capability of the radio system.
2. No agency will be permitted to enable their emergency signal on a talk group designated
as"emergency restricted."
3. All agencies implementing the Emergency Button must have a plan in place to respond to
an Emergency Button activation.
4. All Emergency Button response plans must include, at minimum:
• A central radio monitoring point that can identify which radio user pushed the button,
the location and nature of the emergency and what the proper agency response
should be
• A central monitoring point must be available during any/all hours that personnel are
using the radio system.
• A policy for use of the Emergency Button by radio users.
• A response plan to assist the radio user in need.
• In the event the central radio monitoring point is not the same agency as the radio
user, an agreement on policy, monitoring, use and response must be in place among
the agencies.
• Where available the orange button should be used to program the Emergency
Button.
5. Recommended Procedures:
N/A
6. Manaaement:
Agencies wishing to use the Emergency Button function must coordinate which agency resources
that will be receiving the emergency calls, the receiving agencies must have an appropriate plan
in place, and documented as to the process that they will use to handle the emergency calls.
Page 90 of 99
STANDARD OPERATING PROCEDURES(SOP)
800 MHz Trunked Regional Public Safety Radio System
Standards, Protocols, Procedures
Document Section: 1.12 RPSCC Radio Sub-Committee
Sub-Section: Approved Date: 08/02/07
Procedure Title: Encryption
Date Established: 01/04/07
Replaces Document Dated: N/A
Date Revised: N/A
1. Purpose or Objective:
This procedure is to identify operational procedures and responsible authorities governing
Encryption activities.
2. Technical Backaround:
■ Capabilities
The network infrastructure and subscriber units need to be configured to permit
Encryption of selected Talk Groups. Whether or not Encryption will be utilized in
subscriber radios, it is at the option of the user agency. Users also need to be trained to
know how to activate the Encryption feature when needed on a specked talk group.
■ Constraints
It will be the subscriber radio user's responsibility to activate the Encryption feature when
needed. In most cases the use of Encryption will be decided once a talk group is
dedicated to the use by the personnel in the field that are involved in the operational
situation.
The Encryption feature blocks all non-approved/intruder radio users and scanners from
hearing the conversation of the talk group that is being used for the situation. At this
point in time (2007), only the City of Hollywood and County of Broward infrastructure
support Encryption capabilities. Encryption can only occur on a digital capable talk
group. Both the availability of digital Talk Groups and digital subscriber IDs is limited and
must be coordinated with the System Managers prior to any desired implementation.
Currently only DES-OFB and DES-XL Encryption algorithms are supported. Encryption
Talk Groups that must appear on a console will need to have Encryption key loaded into
the Console DIU. This has the potential to reduce the security of the talk group as others
may be able to access the clear audio via a console.
3. Operational Content:
The Encryption feature needs to be pre-approved by the agency's upper level management.
Police units that are approved to receive Encryption for their subscriber radios are designated as
SWAT, K-9, Homeland Security and Special Investigation Division, and any other unit as
determined by the Department. Other Departments and Divisions such as the Fire Department
may choose to encrypt some or all of their Talk Groups as needed to insure operational security.
4. Recommended Protocol/Standard:
Limited Encryption privileges may be pre-approved by the affected Talk Group owners and
System Managers.
Page 91 of 99
Before allowing Encryption as a feature of a subscriber radio user 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
5. Recommended Procedures:
A subscriber radio user that has the Encryption feature will be responsible for
activating/deactivating it as needed. Talk Groups may also be "strapped" secure in the
subscriber programming to permit only encrypted operation if desired.
Encryption Keys shall be maintained by the Agency utilizing the Encryption feature. Each agency
is responsible to insure that they do not duplicate Logical IN (LIDs). Logical IN for the keys
consist of a four-digit number entered as the last four digits of the Key. LIDs for Broward County
shall be in the 1000 series, Deerfield Beach shall use 2000, Hollywood shall use 3000, Fort
Lauderdale and Pompano Beach shall use 4000, and Hallandale Beach shall use 5000. As other
systems are brought into the Regional Public Safety Communications System, their LIDs shall
start with the site number for their infrastructure. This structure insures that there will not be
duplicated LIDs which will cause problems when utilizing Encryption in the integrated
environment that we share. The first 16 digits of the key are at the discretion of the Agency.
There are two shared Regional Special Investigations Joint Operations Talk Groups that utilize a
shared common key. These two Talk Groups may not be utilized on a permanent basis for any
one specific unit or agency. They are common, shared resources dedicated to interagency
operations. The talk group information and key are available to authorized personnel by
contacting either the System Managers of the Broward County's Office and Fort Lauderdale.
6. Management:
The System Managers group and the agencies upper level management will be the responsible
authority for Encryption issues.
Page 92 of 99
STANDARD OPERATING PROCEDURES(SOP)
800 MHz Trunked Regional Public Safety Radio System
Standards, Protocols, Procedures
Document Section: 1.13 RPSCC Radio Sub-Committee
Sub-Section: Approved Date: 08/02/07
Procedure Title: Definitions&Acronyms
Date Established: 06/28/07
Replaces Document Dated: N/A
Date Revised: N/A
1. Purpose or Objective:
To clarify terms used throughout the standards, protocols and procedures manual. All definitions
will be found in this section.
2. Mananement:
Should there be additions, deletions or changes to these procedures the Regional Public Safety
Communications Committee(RPSCC) members are responsible for revising this section.
3. Definitions(in alphabetical order)
APCO P25 Compliant: Public safety equipment that meets (Association of Public Safety
Communications Officials)APCO P25 standards.
Announcement Group: is a collection of Talk Groups.
Audit: An audit is defined as a one time, infrequent or occasional in depth analysis of
comprehensive elements. An audit may be annual or upon demand. An audit may be stimulated
by an event or complaint of monitoring outcome.
"Common" or"Pool"Talk Groups: Common/pooled talk groups (TG) are those that are set-
aside for communicating across multiple agencies. Agency radio users in appropriate service
areas who need to talk to one another for day to day business or for mutual aid will all put the
appropriate common or pool talk group in their radios to be available in time of need. Example:
Fire Departments will all have the common Statewide Fire Mutual Aid TG in their radios. "Pool" is
distinguished from "common" in that pool implies more than one, such as TAC 1 —4 is a pool of
common regional tactical TGs for law enforcement.
Failsoft Signaling: During normal system operation, the central controller supplies the base
station's Failsoft circuit with a Transmit Data (TDATA) signal. The TDATA signal consists of an
OSW followed by an LSHS signal, followed by a Disconnect Word signal. The TDATA signal
keeps the base stations in the trunking mode. If TDATA transmission stops because of failure of
the central controller, the base stations revert to the Failsoft mode.
• The base station unmutes and transmits a Failsoft data word
• Radios respond to the Failsoft word and unmute, allowing service to continue via
community repeater type operation.
• The base station sends out a 900 Hz tone for 280 milliseconds every 10 seconds to alert
the radio user that the system is in Failsoft mode.
Logging: Audio recording of a radio communication.
Mission Critical Operations: Those governmental, quasi-governmental and non-govemmental
Page 93 of 99
operations carried out by authorized users which are reliant upon a functioning two-way radio
communications system which unavailability, degradation, delay or failure, partial or complete,
would significantly impact or impair the successful delivery of a vital service or mission.
Operations would include, but are not limited to the categories below:
• Public Safety — Those functions of government that exist to protect the physical well-
being of the public as a whole from physical danger — continuous delivery of essential
public services. Included with this group are Legal Counsel and City's Special
Investigative Unit(SIU)and the Administration Site Operations.
• Transportation —Those functions of the government that exist to provide safe, effective
and efficient mufti-mode movement of the public commodities including public roads,
highways, waterways, railways, airways and public transportation systems. Included with
this section is the Broward City buses that may need to be used as a back-up to the
Broward County Mass Transit buses should a mass evacuation occur due to a major
incident.
• Environmental Protection — Those functions of the government that exist to protect the
environmental from changes that are detrimental to the existence and continuance of that
environment.
• Public Works — Those functions of the government that provide "first responders" that
may be necessary to clear streets and highways so that Public Safety operations can be
conducted after a major event like a hurricane.
Mobile Radio: A station in the mobile service, generally installed in a vehicle, intended to be
used while in motion or during hafts at unspecified points.
Mobile Service: A service of radio communication between mobile and base stations, or
between mobile stations.
Monitor: Monitoring is defined as the scheduled and routine inspection of operational practices
and facilities and/or the review of system reports and documents. Monitoring frequency would
generally be on a predetermined, scheduled basis
Non-Critical Operations: All other governmental, quasi-governmental and non-governmental
operations, which are reliant upon a functioning two-way, radio communications that do not meet
the above mission critical or department critical definitions.
Operational Fixed Station: A fixed station, not open to public correspondence, operated by,
and for the sole use of those agencies operating their own radio communication facilities in Public
Safety, Industrial, Land Transportation, Marine or Aviation Radio Services.
Patch:
Permanent (hard) Patch: A patch between two or more audio resources on a system,
which is fixed and cannot be controlled or edited by the dispatcher.
Manual (soft) Patch: A patch between two or more audio resources on the system,which
is setup and controlled by the dispatcher. The dispatcher owning the patch can add and delete
resources as needed.
Portable Radio: A radio that is completely freestanding and may be hand-carried or worn by the
radio user.
Preferred Site Assignment: A SmartZone system can also be configured with Preferred Site
Assignment operation. This feature allows radio users to maintain conversations on sites
Page 94 of 99
especially useful to operations and group requirements. In areas with overlapping coverage,
radios will work on their preferred site in order to efficiently utilize channel resources while
minimizing the number of channels necessary to complete a talkgroup call. Four types of
preference can be programmed into the radio personality:
• Always Preferred — The subscriber unit will always use this site if it has at least
acceptable signal strength, even if the site enters site trunking mode.
• Preferred - The subscriber unit will use this site if it has at least an acceptable signal
strength rating and is in wide-area trunking mode.
• No Preferred Site—This is the default setting for subscriber radios. The subscriber unit
will use the best signal according to the best Receive Signal Strength Indication (RSSI).
• Least Preferred —The subscriber unit will avoid this site unless no other sites with at
least acceptable signal strength are available for use.
Private Call: This allows one radio user to talk to and be heard by only one other radio user.
This feature allows a supervisor to discuss confidential matters with a particular member of a
talkgroup while other members of the same talkgroup remain squelched.
Public Safety: All Law Enforcement / County, Fire, Emergency Medical and related service
areas. These include badged and/or sworn ancillary personnel such as Park Rangers, Court
Security Officers, Community Corrections, and those who support public safety operations under
special circumstances.
Public Safety Answering Points(PSAPs):
Primary: The PSAP where a 9-1-1 call is originated and received by a call taker then
transferred to a dispatcher for dispatching police, fire or emergency medical assistance.
Secondary: The PSAP that receives transferred 9-1-1 call taker calls and is then
dispatched and monitored from this center.
Public Service: Public Service in this context refers to general government personnel such as
Public Works,Transportation, and other similar public service operations.
RF: Radio Frequencies
Regional Public Safety Communications Committee (RPSCC): The governing body of
municipal Police and Fire Chiefs, IT Management and decision-making staff that are empowered
to develop Standards, Protocols and Procedures regarding the intent to accomplish the Broward
County's Charter direction to achieve regional communication plans to establish Radio
Interoperability and Closest User Response objectives.
Region 7: State of Florida Homeland Security region that is made up of Broward, Dade, Monroe
and Palm Beach Counties.
Regional System: In this context of this manual this term is intended to represent the entire
Region-wide 800 MHz Public Safety Communication System.
SmartZone Trunked System: The 28 channel trunked radio system that serves public safety
communication users in a wide-area coverage network. This system allows for roaming from one
radio system to another trunked or conventional system seamlessly and provides
communications back to the municipality's home based dispatch center. This system can operate
in an analog or digital mode.
SmartZone Manager Terminal: The resource tool that is used by System Managers to
administer their radio system for maintenance issues and controls of how their radio subscriber
Page 95 of 99
and consoles are configured/programmed.
Subscriber Radio: A portable radio that is assigned to a specific individual or a mobile radio
that is shared by multiple staff that drives and operates the vehicle.
System: A countywide public safety radio communication system that consists of a shared
region-wide infrastructure, the elements of which are identified in the Regional Public Safety
Communications Plan and Subsystem integrated into or interconnected by the shared countywide
network.
System Manager/Administrator Positions:
• System Manager—individual in charge of the radio system of a participating agency.
• System Administrator — individual who is responsible for the day to day radio system
operations of a participating agency.
• Sub-System Administrator — individual who is responsible for the day to day radio sub-
system operations of a participating agency.
• Contract Manager—Director of Broward County Office of Communications Technology or
his appointed designee.
Talk Group: The Talk Group is the primary level of communication in a Trunked radio system.
This provides the effect of a private channel down to the talkgroup level and prevents members of
one talkgroup from hearing the talkgroup calls generated by radios in other talkgroups.
Telephone Interconnect: The use of a radio to make a two-way call between two radios
subscribers when privacy is needed to block other radio subscribers from hearing the
conversation. This feature must be programmed in the radio and activated on the system in order
for it to be functional.
Variance: An allowed divergence from full adherence of an adopted standard, protocol or
procedures
Waiver: A complete release from an adopted standard, protocol or procedure.
4. ACRONYMS(in alahabetical order)
ALS - Advanced Life Support
ATAC - All(user)Tactical talk group for 800 radios
AVL - Automatic Vehicle Locator
APCO - Associated Public Safety Communications Officials
BLS - Basic Life Support
CEB - Central Electronics Bank
CTCSS- Continuous Tone Coded Squelch System
DIU - Digital Interface Unit
DTMF - Dual Tone Multiple frequency
Page 96 of 99
EDICS - Emergency Deployable Interoperability
Communications System
EMS - Emergency Medical Services
EMIRS - Emergency Medical Radio System
FCC - Federal Communications Commission
ICALL - International 800 MHz Calling Channel
ITAC - International 800 MHz Tactical Channel
MHz - Megahertz
NAEMSD- National Association of State EMS Directors
NPSPAC National Public Safety Planning Advisory Committee
PSAP - Public Safety Answering Point
PSWAN- Public Safety Wide Area Network
PTT - Push to Talk, i.e.talk button
RF - Radio Frequency
RX - Receiver of radio communications
SMG - System Manager,the owner of the Regional Public
Radio System and Sub-Systems
RSS - Radio Service Software
TX - Transmission of radio communications
UHF - Ultra High Frequency
VHF - Very High Frequency
Page 97 of 99
STANDARD OPERATING PROCEDURES(SOP)
800 MHz Trunked Regional Public Safety Radio System
Standards, Protocols, Procedures
Document Section: 1.14 RPSCC Radio Sub-Committee
Sub-Section: Approved Date: 08/02/07
Procedure Title: Console Naming
Date Established: 06/28/07
Replaces Document Dated: N/A
Date Revised: N/A
1. Purpose or Objective:
The purpose of this section is to set forth the principle by which all System Managers /
Administrators of the regional system will establish names for the Radio IDs used to support
dispatch console positions. This is necessary because IDs are not associated with a Radio User
Alias.
2. Technical Background:
Constraints: The serial number field in Radio ID screens in 12 characters long. Every Talkgroup
per console position requires a Radio ID programmed for that position, for example a single
console position may have 50 radio ID programmed to support that position.
3. Operational Context: Every radio in the system represents a radio, but not every Radio ID in
the system is a radio, some are consoles. By planning an identification process, we can use the
radio serial number field in the radio entry screen in the system to categorize consoles so that
they can be easily identified.
4, 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.
4. Recommended Procedures:
N/A
Page 98 of 99
5. Management:
The System Managers/Administrators are responsible for ensuring compliance with the
standard.
Page 99 of 99