HomeMy WebLinkAboutCity of Tamarac Resolution R-2013-085Temp. Reso # 12384
August 28, 2013
Page 1
CITY OF TAMARAC, FLORIDA
RESOLUTION NO. R-2013PS.^
-
A RESOLUTION OF THE CITY COMMISSION OF THE CITY
OF TAMARAC, FLORIDA, APPROVING AN ASSIGNMENT,
DELEGATION AND RELEASE AGREEMENT MADE BY AND
AMONG SHERIFF OF BROWARD COUNTY, BROWARD
COUNTY AND THE CITY OF TAMARAC; PROVIDING FOR
CONFLICTS; PROVIDING FOR SEVERABILITY; AND
PROVIDING FOR AN EFFECTIVE DATE.
WHEREAS, on September 24, 2009, Sheriff entered into a Regional Interlocal
Agreement (RILA) with the City attached hereto as Exhibit 1 to establish acounty-wide
interoperable public safety intranet that can support closest unit response in life
threatening emergencies and regional specialty teams; and
WHEREAS, effective October 1, 2012 at 12:01 a.m., Broward County (County) has
undertaken the operation of the Regional Communication System ("System") and in order
that County may properly perform its functions as the operator of the System, it is
appropriate that the RILA between Sheriff of Broward County (Sheriff) and City be
assigned by Sheriff to County; and
WHEREAS, as of October 1, 2012 at 12:01 a.m., County has agreed to assume
Sheriff's rights, duties and obligations under the RILA; and
WHEREAS, Sheriff is willing to assign the RILA to County and County is willing to
accept the assignment of the RILA; and
WHEREAS, the existing RILA is set to expire on September 24, 2014 and in order
County to synchronize the
terms of the interlocal agreements
with all the
effected
municipalities throughout the
County, the assigned RILA will expire
September
30, 2015
and may be renewed commencing on October 1, 2015 in accordance with the remaining
Temp. Reso # 12384
August 28, 2013
Page 2
terms of the assigned RILA; and
I
WHEREAS, the City Manager and Fire Rescue Chief recommend approval of the
Assignment of the RILA from Sheriff to the County; and
WHEREAS, the City Commission of the City of Tamarac believes the assignment of
the RILA from Sheriff to the County is in the best interest of the City of Tamarac.
NOW, THEREFORE, BE IT RESOLVED BY THE CITY COMMISSION OF THE
CITY OF TAMARAC, FLORIDA:
SECTION L The foregoing "WHEREAS" clauses are hereby ratified and confirmed
as being true and correct and are hereby made a specific part of this Resolution upon
adoption hereof. All Exhibits attached hereto are hereby incorporated herein and made a
specific part of this resolution.
SECTION 2: The City Commission hereby approves the Assignment, Delegation
and Release Agreement attached hereto as Exhibit 2 between the Sheriff, County and the
City providing for assignment of the existing RILA from Sheriff to the County and
authorizes the appropriate City Officials to accept and execute the Assignment, Delegation
and Release Agreement.
SECTION 3: All Resolutions or parts of resolutions in conflict herewith are hereby
repealed to the extent of such conflict.
SECTION 4: If any clause, section, other part or application of this Resolution is
held by any court of competent jurisdiction to be unconstitutional or invalid, in part or
application, it shall not affect the validity of the remaining portions or applications of this
Resolution.
Temp. Reso # 12384
August 28, 2013
Page 3
SECTION 5: This Resolution shall become effective immediately upon its passage
and adoption.
PASSED, ADOPTED AND APPROVED this 9 o dad
MAYOR
ATTEST:
PATRICIA TEUFfL, CMC
CITY CLERK
RECORD OF COMMISSION VOTE:
MAYOR TALABISCO
DIST 1: COMM. BUSHNE L
DIST 2: COMM. ATKINS-GRAD dZA4z
DIST 3: COMM. GLASSER
DIST 4: V/M. DRESSLER A�
HEREBY CERTIFY THAT I HAVE
APPROVED THIS RESOLUTION
AS TO FORM
a
�dM U-EL S. GOREN
CITY ATTORNEY
r
TR11660
Page 1
August 12, 2009
CITY OF TAMARAC, FLORIDA
RESOLUTION NO. R-2009 - // 3
A RESOLUTION OF THE CITY COMMISSION OF THE CITY OF
TAMARAC, FLORIDA TO APPROVE THE REGIONAL
INTERLOCAL AGREEMENT (RILA) BETWEEN THE SHERIFF
OF BROWARD COUNTY AND THE CITY OF TAMARAC;
PROVIDING FOR CONFLICTS; PROVIDING FOR
SEVERABILITY; AND PROVIDING FOR AN EFFECTIVE DATE.
WHEREAS, the City of Tamarac (City) has provided high quality Fire Rescue
operations to the community since 1975; and
WHEREAS, Tamarac Fire Rescue desires to improve the quality of Fire and EMS
operations to the citizens and visitors of the City: and
WHEREAS, pursuant to §163.01 , Florida Statutes, also known as the Florida Interlocal
Cooperation Act of 1969, the City in cooperation with the Sheriff of Broward County (Sheriff)
wants to create an interoperable public safety system consisting of closest unit response to
emergency incidents; and
WHEREAS, the City desires to enhance radio interoperability by interconnecting to the
Sheriff of Broward County's public communication and Computer Aided Dispatching (CAD)
System as part of its public safety intranet that supports county -wide police, fire and
emergency services; and
WHEREAS, the City and Sheriff desire to enhance information sharing by
interconnecting public safety data users and records management systems that support fire
and emergency operations; and
WHEREAS, the City Manager and the Interim Fire Chief recommend acceptance of
this Regional Interlocal Agreement (attached hereto as Exhibit A); and
TR11660
Page 2
August 12, 2009
WHEREAS, the City Commission of the City of Tamarac, Florida deems it to be in the
best interest of the citizens and residents of the City of Tamarac to cooperate with the Sheriff
of Broward County to create an interoperable public safety system consisting of closest unit
response to emergency incidents.
NOW THEREFORE BE IT RESOLVED BY THE CITY COMMISSION OF THE CITY OF
TAMARAC, FLORIDA:
Section 1: The foregoing "WHEREAS" clauses are HEREBY ratified and confirmed as
being true and correct and are HEREBY made a specific part of this Resolution. All Exhibits
attached hereto are incorporated herein and made a specific part of this Resolution.
Section 2: The City Commission of the City of Tamarac HEREBY approves the
Regional Interlocal Agreement between the Sheriff of Broward County and the City of
Tamarac.
Section 3: The appropriate City Officials are HEREBY authorized to execute the
Regional Interlocal Agreement between the City of Tamarac and Sheriff of Broward County,
(attached hereto as Exhibit A).
Section 4: All Resolutions or parts of resolutions in conflict herewith are HEREBY
repealed to the extent of such conflict.
Section 5: If any clause, section, other part or application of this Resolution is held by
any court of competent jurisdiction to be unconstitutional or invalid, in part or in application,
it shall not affect the validity of the remaining portion or applications of this Resolution.
TR11660
Page 3
August 12, 2009
Section 6: This Resolution shall become effective immediately upon its passage and
adoption.
PASSED, ADOPTED AND APPROVED this C� day of � , 2009.
ATTEST:
-MARION SWENSON, CIVIC
CITY CLERK
I HEREBY CERTIFY that
I have approved this
RESOLUTION as to form.
A
SPIMUEL S. GOREN
fit, IN ATTORNEY
BETH FLANSBAUM-TALABISCO
MAYOR
RECORD OF COMMISSION `1^Tc8
MAYOR FLANSBAUM-TAI
DIST 1: COMM BUSHNEL
DIST 2: VM ATKI N S=G RAI
DIST 3: COMM GLASSER
DIST 4: COMM. DRESSLE
W
tr
Office of the General Counsel
2601 West Broward Boulevard
Fort Lauderdale, Florida 33312
(954) 831-8920 (Telephone)
(954) 321-4425 (Fax - General Counsel)
(954) 321-5040 (Fax - Legal)
(954) 797-0937 (Fax - Confiscations Unit)
www.sherifforg
September 29, 2009
Marion Swenson, City Clerk
City of Tamarac
7525 Northwest 88 Avenue
Tamarac, Florida 33321
RE: Regional Interlocai Agreement
Dear Ms. Swenson:
Please find enclosed one (1) original fully executed Agreement with the Broward
Sheriffs Office and the City of Tamarac for the Cooperative Participation in a Regional
Public Safety Intranet for your file.
Thank you for your time and attention to this matter.
Sincerely,
;;e�lr'esa S ds, Esq.
Senior Legal Counsel
TSlseh
Enclosure
cc: File
HATEREWLetters1200910ty of Tamarac ILA - Executed Contract.doc
:-=)
-' o
;
ti •��
co
TR11666 Exhibit A
Agreement
Broward County Sheriff s Office
Communications Technology Division
TR11660 - Exhibit A
Regional Interlocal
Agreement
Table of Contents
I. Agreement
II. Exhibit A — Statement of Work, System Description,
and Acceptance Test Plan
III. Exhibit B — Demarcation Points
IV. Exhibit C — Equipment List
V. Exhibit D — Change Management Request Procedure
VI. Exhibit E — Project Charter
VII. Exhibit F — Service Level Agreement
2
TR11660 - Exhibit A
AGREEMENT
BETWEEN
SHERIFF OF BROWARD COUNTY
.1•
Providing for
COOPERATIVE PARTICIPATION IN A
REGIONAL PUBLIC SAFETY INTRANET
This is an Interlocal Agreement, made and entered into by and between
Sheriff of Broward County (hereinafter referred to as "SHERIFF"), a political
subdivision of the State of Florida, and City of Tamarac, a Florida municipal
corporation, .(hereinafter referred to as "CITY"), collectively 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, SHERIFF 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. This includes 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 SHERIFF and CITY public safety radio users; and
WHEREAS, the Parties desire to enhance information sharing by
interconnecting SHERIFF and CITY public safety data users; and
3
TR11660 • Exhibit A
WHEREAS, SHERIFF maintains a Trunked Radio System as part of its
public safety intranet that supports county -wide police, fire, and emergency
services; and
WHEREAS, SHERIFF maintains a Computer Aided Dispatching ("CAD")
System as part of its public safety intranet that supports county -wide police, fire,
and emergency services; and
WHEREAS, SHERIFF maintains an Automated Vehicle Location
System as part of its public safety intranet that supports county -wide police, fire,
and emergency services; and
WHEREAS, SHERIFF
("FRMS") as part of its public
emergency services; and
maintains a Fire Records Management System
safety intranet that supports county -wide fire 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'T 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.
Automated Vehicle Location ("AVL") System: A component of
1.2 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 Change Management Requests CCMR" ): The CMR process
r�l.w_w.� ■ i ■� �rw
will be 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".
2
TR11660 - Exhibit A
Computer Aided Dispatch ("CAD") System: A component of the
RPSI that has as one of its functions, in conjunction with the
1.4 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.5 1Contract Administrator: SHERIFF's Contract Administrator of
ti- - r"% _ -_ _ - - 1 r%_ _L 1_- r%-t_L _ 1-L--- _1 I9rtiM^131 !- e%1 1r-n1f✓ r'!
Director of the Communications Technology Division.
1.6 Demarcation Points: A "Demarcation Point" or "Demarc"
identifies a responsibility boundary between CITY -responsible
items and SHERIFF -responsible items. EXHIBIT "B" further
defines and visually portrays the RPSI Demarcation Points and
entity -responsibilities on a portion by portion basis.
1.7 Equipment: The SHERIFF -owned and maintained items listed
in EXHIBIT "C" and any other SHERIFF -provided items.
1.8 Fire Records Management System ("FRM,S J: A component of
the RPSI that archives fire -related dispatch records and
information.
1.9 Fire, Rescue Frontline Vehicles: Refers to those vehicles
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 not in a reserve or staff capacity.
1.1 0 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 PC
screen or by the push of a few buttons.
NetMotion: A component of the RPSI that improves mobile
1.11 1 data network performance, encryption, communication stability,
and roaming between disparate private and public wireless
networks.
5
TR11660 - Exhibit A
1.12 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.13 Non -Dispatch, Facili 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 PM DC via their .owned and operated Local Area Networks.
The CITY -SHERIFF demarcation boundaries are outlined in
"Exhibit B".
Peripheral Equipment: The CITY -owned and maintained items
listed in Exhibit "C" and any other CITY -provided items.
1 1 Peripheral equipment includes but is not limited to Ethernet
net
cabling, mouse, keyboard, speakers, printers, etc.
Project: The integration of a regional public safety Intranet
comprised of radio and data systems, benefiting public safety
1.15 agencies within Broward County that choose to participate.
Proiect Charter: Outlines the requirements, direction,
1.16 constraints, and collective) d y accepted p deliverables
erables 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".
1.17 1 Proiect Ma An An employee of the SHERIFF who is
assigned by the Contract Administrator to provide day-to-day
management of the Project from inception to completion.
1.18 Public Safety Network_{`�P5: A component of the RPSI which
provides the communication connectivity and network
infrastructure for data portions of the RPSI.
1.19 1 Regional Dispatch Center (RDC): A cooperative 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 is directly connected and
utilizes the Regional CAD and County -Wide Radio System.
C1
2.1
TR11660 - Exhibit A
Regional Public Safety Intranet ("RPSI"): The overall collection
1.20
of Equipment — including but not limited to SHERIFF's Trunked
Radio System — Public Safety Network — Public Safety
Applications -- that constitutes the Regional Public Safety
Intranet. CITY -owned equipment interfaces to the SHERIFF -
owned RPSI.
1.21
Service Level Agreements ("SLA"): Defines an expected level
varlous categories: yslem
performance, trouble resolution, operations, and administration.
The Service Level Agreements are further explained and listed
in Exhibit "F".
1.22
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.23
Subscriber Maintenance: Refers to CITY's responsibility to
maintain the CITY owned user's equipment. Subscriber
maintenance is further explained in Exhibit "B".
Svstem Maintenance: Refers to SHERIFF Is responsibility to
1.24
maintain the regional public safety intranet (RPSI) as described
in Exhibit "B".
Trunked Radio Svstem: SHERIFF's Trunked Radio
1.25
Communications System, a major portion of which is used by
police and fire rescue personnel within Broward Sheriff's Office.
Today, SHERIFF owns and operates a twenty-eight (28)
channel 800 MHz trunked simulcast SmartZone radio system.
ARTICLE 2
SCOPE OF WORK
SHERIFF 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 SHERIFF 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
7
TR11660 - Exhibit A
Communications Commission (FCC), Telecommunications Industries
Association (TIA), and Association of Public Safety Communication
Officials (APCO) standards together with manufacturers' specifications.
2.4 SHERIFF shall own all Equipment the SHERIFF supplies to CITY
pursuant to this agreement.
2.5 CITY shall provide SHERIFF access to the CITY's equipment rooms to the
extent require or a installation o e s 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 SHERIFF agrees that the CAD, AVL, FRMS, Mobility Zone, and Public
Safety Network functionalities supplied to CITY shall also meet
appropriate performance levels as defined in EXHIBIT "A".
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 SHERIFF with needed
uninterruptible 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 SHERIFF for dispatch center Equipment.
2.9 CITY agrees to allow SHERIFF, with notice to CITY and monitoring by
CITY personnel, to troubleshoot a CITY local area network (LAN) which
adversely impacts the Regional Public Safety Intranet or the operation of
CITY's Public Safety Communications Dispatch Center. 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 SHERIFF shall maintain all systems outlined as "SHERIFF 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 SHERIFF
shall not
be
responsible
for the payment of any taxes,
insurance,
and
utilities
for
CITY
owned
facilities.
TR11660 - Exhibit A
2.14 Access to CITY's facilities for SHERIFF personnel, or SHERIFF'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
o: 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 SHERIFF's
Contract Administrator to the Contractor, the Parties shall develop a
mutually acceptable Project Plan inclusive of project charter ("Exhibit Ell
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 Sheriffs 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 SHERIFF's acceptance of, the
Detailed Design Review and Project Schedule submitted to SHERIFF,
SHERIFF 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.
2.19 CITY shall follow all RPSI Trunked Radio System policies and standard
operating procedures in place at the time of this Agreement, as well as,
those developed in the future and issued to CITY by SHERIFF. CITY
agrees to comply with any enforcement actions required by these policies
and procedures for misuse or abuse of the RPSI Trunked Radio System.
9
TR11666 a Exhibit A
2.26 SHERIFF and CITY shall jointly be responsible for developing
fleet mapping and programming of all subscriber units and
parameters necessary to meet the operational requirements.
2.21 SmartZone operation shall be limited to public safety users only.
desired
system
2.22 CITY acknowledges that the services to be performed under
Agreement, relative to SHERIFF's responsibilities, shall be performed
th is
OV49,
SHERIFF and/or its contractors and shall be under the sole supervision
and direction of SHERIFF. At CITY facilities, CITY may monitor
installation work done by the SHERIFF, its employees, agents, and
subcontractors. Likewise, SHERIFF 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. SHERIFF 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 SHERIFF for
a fee for a combination of the aforementioned services or for all of the
above services.
2.24 SHERIFF shall reprogram all CITY subscriber radios and control stations
for operation on the SHERIFF's Trunked Radio System.
2.25 CITY is responsible for all removals and installations of its subscriber
equipment.
2.26 SHERIFF agrees that it will not implement any changes/enhancements 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 SHERIFF to
CITY for proposed changes and their potential effect on CITY operations.
Should CITY or SHERIFF desire to perform changes to the facility or the
RPSI that may impact the Equipment or services provided by the
SHERIFF, the Change Management Request (CMR) procedures (Exhibit
"ID") 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 SHERIFF,
or its
sub -contractors to ensure that they are: (a) consistent with the CITY and
SHERIFF requirements for the Project; (b) sufficiently fit and proper for the
purposes intended; and (c) comply with all applicable laws, statutes,
10
TR11660 - Exhibit A
building codes, and CITY and SHERIFF guidelines or regulations, which
apply to or govern the Project. CITY's approval, acceptance, use of or
payment for all or any part of SHERIFF's services under this Agreement or
of the Project itself shall in no way alter SHERIFF's obligations or CITY's
rights. Copies of all items shall be provided to CITY and SHERIFF. The
Project Charter listed as Exhibit "E" will be used to identify the
requirements and expectations set forth by CITY and SHERIFF.
2.28 n the event that SHERIFF 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, SHERIFF 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 SHERIFF to inspect SHERIFF's or the Contractor's
performed work on the System to determine if it meets the CITY's
operational needs and SHERIFF's requirements.
2.30 CITY public safety users shall have equal accessibility to SHERIFF'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 SHERIFF 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, or PSN.
2.32 CITY agrees to provide SHERIFF or SHERIFF's Contractor, for the term
of the Agreement, with facility space associated with the on -site
maintenance, troubleshooting, and repair of all SHERIFF 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.
3.2 The term of this Agreement shall be for five (5) years from the
commencement date pursuant to Section 3.1 above. This Agreement may
be renewed every five (5) years with the approval of both SHERIFF and
CITY, unless terminated pursuant to Article 4.
TR11660 - Exhibit A
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 with thirty (30)
days notice to the other party.
ARTICLE 4
TERMINATION
4.1 Notwithstanding the provisions set forth in Section 3.3 and 4.4, this
Agreement may not be terminated by the SHERIFF or CITY for
convenience during the initial five (5) year term with the exception of the
circumstances set forth in Paragraph 4.3. Any subsequent renewal term
may be terminated for either cause or convenience by either party upon
providing written notice to the other party at least two (2) years 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 SHERIFF shall
constitute a breach of this Agreement. In the event the CITY fails to cure
the breach within such thirty (30) day period, SHERIFF may immediately
terminate this Agreement upon written notice to the CITY.
4.3 The failure of the SHERIFF to perform its responsibilities as set forth
herein or under a particular Project Charter, as same may be amended,
for a period of thirty (30) calendar days after written notice by CITY shall
constitute a breach of this Agreement. In the event the SHERIFF fails to
cure the breach within such thirty (30) day period, CITY may immediately
terminate this Agreement upon written notice to the SHERIFF.
4.4 CITY recognizes that the Board of County Commissioners, Broward
County, Florida is the authority which establishes, allocates or otherwise
provides for SHERIFF's budget year funding. If in any budget year,
funding, for any reason, is not provided to cover the SH ER I FF's
responsibilities and obligations under this Agreement, this Agreement may
be terminated by SHERIFF without penalty upon written notice to the
CITY.
12
5.1
TR11660 - Exhibit A
ARTICLE 5
COMPENSATION
Section 31821(9), Florida Statutes (2002), requires that Twelve dollars
and fifty cents ($12.50) from each moving traffic violation must be used by
e 0 fund the GOUNTY'Snarticination In 9n in arnnvPrnmanfa
radio communication program approved by the Department of
Management Services. CITY understands such revenue generated within
its jurisdiction will be used by the SHERIFF 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 SHERIFF 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 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 SHERIFF. 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 with the same
formalities as set forth herein. Should CITY or SHERIFF desire to perform
changes to the facilities, the RPSI or PSN that may adversely impact the
Equipment provided by the SHERIFF, the Change Management Request
(CMR) procedures (Exhibit "D") will be followed.
13
TR11660 = Exhibit A
ARTICLE 7
FREQUENCY USAGE
7.1 CITY agrees to authorize SHERIFF, pursuant to state and federal
regulations, to Integrate s eligible - - MHz-- frequencies into
SHERIFF'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 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.3 SHERIFF shall assist CITY with fling appropriate documents to facilitate
SHERIFF's usage of the 700 MHz frequencies, including documents
regarding Federal Aviation Administration (FAA) and/or FCC licensure.
7.4 SHERIFF understands and agrees to maintain CITY radio frequencies
(direction and range) integrated into the SHERIFF Trunked Radio
system(s).
ARTICLE 8
LIABILITY
8.1 CITY and SHERIFF 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 defense thereof, and from and against
any orders, judgments or decrees which may be entered as a result
thereof.
8.2 CITY and SHERIFF 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.
8.3 CITY and SHERIFF are state agencies or political 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 the extent required by
TR11660 - Exhibit A
law. Noting 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
9.1 The Parties acknowledge that SHERIFF 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 SHERIFF 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 SHERIFF to CITY and•further explained in "Exhibit F".
ARTICLE 11
MISCELLANEOUS PROVISIONS
11.1 ASSIGNMENT: SHERIFF shall perform the services provided for in this
Agreement utilizing SHERIFF's employees, contractors, and
subcontractors. Said services shall be performed exclusively and solely
for CITY which is a Party to this Agreement. CITY and SHERIFF 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: The invalidity of any provision of the Agreement shall in
no way affect the validity of any other provision.
15
TR11660 - Exhibit A
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. 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 with
the same formality and of equal dignity herewith.
� 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 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: With the exception of provisions of Paragraph 2.28, all notices
given or required under this Agreement shall be in writing and may be
delivered in person or by United States mail, postage prepaid, first class
and certified, return receipt requested, addressed as follows:
SHERIFF:
Broward Sheriffs Office
Director - Communications Technology Division
115 S. Andrews Avenue, Room 325
Fort Lauderdale, FL 33301
With a copy to: Office of the General Counsel
Broward Sheriffs Office
2601 W. Broward Blvd.
Ft, Lauderdale, FL 33312
16
TR11660 - EXhibit A
CITY:
Jeff Moral, Interim Fire Chief
City of Tamarac
6000 Hiatus Road
Tamarac, FL 33321
.lettrey L. Miller, City Manager
City of Tamarac
7525 NW 88th Avenue
Tamarac, FL 33321
Beth Flansbaum-Talabisco, Mayor
City of Tamarac
7525 NW 88th Avenue
Tamarac, FL 33321
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.1 1 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 Interlocal Cooperation Act of 1969.
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.
11.14 MULTIPLE ORIGINALS: This Agreement maybe 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.
17
TR11SS0 - Exhibit A
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 DRAFTING: This Agreement has been negotiated and drafted by all
Parties hereto and shall not be more strictly construed against any party
because of such party's preparation of this Agreement.
11.18 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 to
the -jurisdiction of the State courts of the Seventeenth Judicial Circuit of
Broward County, Florida, or the United States District Court, Southern
District, Broward County, Florida, the venue sites, 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.19 OWNERSHIP OF EQUIPMENT: SHERIFF retains ownership of all
Equipment that the SHERIFF provides to the CITY pursuant to the terms
and conditions of this Agreement. In the event this Agreement is
terminated by either party, the Sheriff shall remove and/or recover all
equipment within ninety (90) days of the effective date of termination.
11.20 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 1 A: Non -Dispatch Facility
Attachment 1 B: Mobile Data Fire Rescue
Attachment 2: Demarcation Drawings
HP
TR11666 - Exhibit A
EXHIBIT "C": Equipment List
EXHIBIT "D": Change Management Request
EXHIBIT "E": Project Charter
EXHIBIT "F": Service Level Agreements
Attachment 1: Terms and Conditions
men rouble Ticket Workflow
11.21 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 LEFT BLANK
19
TR11660 - Exhibit A
INTERLOCAL AGREEMENT BY AND BETWEEN SHERIFF OF BROWARD
COUNTY AND THE CITY OF TAMARAC FOR COOPERATIVE
PARTICIPATION IN A REGIONAL PUBLIC SAFETY INTRANET.
IN WITNESS WHEREOF, the parties execute this Agreement on the
date(s) set forth below:
AL LAMBERTI AS SHERIFF OF BROWARD COUNTY, FLORIDA
JOHWURRY, EXECUTga DIRECTOR
Department of Administration
Approved as to form and legal sufficiency
Subject to execution by the parties:
I y:
ral Counsel
ATTEST:
City Clerk
;7;
C
McInager
w
Date: R eft( Ct95'
Date: a�3
CITY OF TAMARAC
I HEREBY CERTIFY that I have approved this
AGREEMENT as to form and legal sufficiency
subject to execution by the parties:
uiv mayor
-.1' 1
•16,1w1, 1 ■vJ
TR11660 • Exhibit A
EXHIBIT "A"
Statement of Work
Statement of Work
BSO Communications Technology Division
Closest Unit Response Hardware and Software Package
r
g
City of Tamarac Fire Rescue Frontline Vehicles
April 23, 2009
This Statement of work (SOW) defines and facilitates the City of Tamarac Fire Rescue
Department ("TMFR") and Broward Sheriff's Office Communications Technology
Division's ("BSOCTD") regional involvement in the tasks and objectives required to
successfully implement and integrate the installation of Mobile Data Terminals, GPS
Receivers, PMDC Software, NetMotion Software, Mobile Mapping Software, and First
Look Pro Software for Fire Rescue Frontline Vehicles.
Overview:
The Broward Sheriffs Office Communications Technology Division will complete
installations for the Panasonic CF-30 Mobile Data Terminals. All installations are to be
completed in a vehicle mount configuration provided by BSOCTD. The products
involved are:
• Panasonic CF-30 with embedded commercial carrier aircard and GPS antenna
• CFX TuffDock Docking Station -- USB Dock with Dual Hi -Gain Antenna
(Department of Transportation Certified Mounts)
Garnber Johnson Adapter Plates -- Model 7160-0040
• Gamber-Johnson tilt -swivel attachment - Model DS/CLEVIS
Associated Mobile Application Software
o PMDC
o Mobile Mapping Software
o NetNIotion
o First Look Pro
This SOWprovides:
21
TR11660 ., Exhibit A
• A description of the responsibilities
Communications Technology Division
Department.
for both
the
Broward Sheriffs
Office
and
the
City
of Tamarac
Fire
Rescue
• The quanr cations and assumptions are
development of this statement of work.
taken into consideration during the
The Broward Sheriff's Office Communications Technology Division installation support and coordination services will be provided at
a level consistem v ith the complexity of this project, as well as, cooperation from the City of Tamarac Fire Rescue Department. In
general. these services include the following:
• Execution of the Regional Interlocal Agreement
• Project Initiation
• Order Entry and Processing
• Manufacturing and Shipping Coordination
• Equipment Installation
• Schedule Coordination
Responsibilities
A successful project requires responsibilities to be managed by both the Broward
Sheriff's Office Communications Technology Division and the City of Tamarac Fire
Rescue Department. These responsibilities are outlined throughout this statement of
work.
Broward Sheriffs Office Communications Technology Division Responsibilities:
• Supply and install eight (8) Panasonic CF-30 mobile data terminals with
Ledco mounts and associated power cables.
• Provide vehicle specific mounts for rescue, engine, squirt, and battalion
frontline vehicles. The aforementioned vehicles have been identified by the
municipality as Fire Rescue Frontline Vehicles -- total of 8.
• Configure and test embedded GPS receivers with Mobile Mapping Software.
• Configure and test embedded WWAN devices with PMDC, iV'etMotion, and
First Look Pro Software.
• Conduct functional ATP for CF-30 with embedded GPS receivers and
WWAN devices.
• Verify functionality and connectivity of embedded WWAN device (a.k.a.
Aircard) and its integration with the following RPSI systems:
1. Regional PMDC Message Switch
22
TR11666 - Exhibit A
2. Mobile :Mapping
3. NetMotion VP�,- Gateway Server
4. First Look Pro Software
• Configure, image, and test all CF-30 Mobile Data Terminals in a controlled
environment prior to field deployment.
1. Implement and integrate two (2) fully equipped City of Tamarac Fire
Rescue De artment Frontline vehicles with prototype closest unit _
response solution. Prototype solution will be tested for one week.
• Evaluate results from prototype solution.
• Implement any modifications required to facilitate proper PMDC, Mobile
Mapping, AVL, NetMotion, and First Look Pro configuration.
City of Tamarac Fire .Rescue Department Responsibilities:
• Review and accept the statement of work (SOW).
• Review and accept the installation schedule.
• Provide the necessary number of municipal frontline vehicles according to the
installation schedule.
• Provide a mutually agreeable location suitable for mass closest unit response
equipment installations. This location must have adequate working space
with HVAC, lights, electric, and shelter from the outside elements.
• Designate a single point of contact within the City of 'Tamarac Fire Rescue
Department that will be responsible for scheduling vehicles as required for
installation.
• Have a City of Tamarac Fire Rescue Department representative on site to
approve and accept the installations daily.
• Inspect each vehicle before it is delivered to the installation facility and ensure
that the vehicle is free from trash, weapons, and contraband.
• Arrange for all equipment removed from the vehicles to be accounted for and
picked up from the installation facility as necessary.
• Inventory all equipment prior to removal from the installation facility; any
discrepancies shall be resolved at that time.
• Identify a municipal agency single point of contact to approve the CF-30
mobile workstation application image prior to installation.
• Activate embedded WWAN devices by subscribing to the recurring monthly
service prior to installation. All WWAN devices and activations shall be
provisioned as unrestricted/public prior to start of installation.
23
TR11660 - Exhibit A
assumptions/Comments
• Standard Panasonic CF-30 mobile data terminal frontline vehicle installations
are assumed using standard Department of Transportation (DOT) certified
mounts and approved support arms as described in the SOW. (DOT certified
mounts are designed to operate with vehicle air bad systems and cannot be
altered_ or modified.
There will be no additional vehicle modifications or alterations done for this
installation.
• All vehicles are recommended to have shoreline power connected at all times.
After the frontline vehicle installation is complete, both the BSOCTD and
TMFR will assume that constant power will be supplied to the equipment.
• 12 Volt negative ground vehicle batteries are assumed for all equipment. The
installer will be responsible for verification of all facets related to each
installation.
• The Broward Sheriffs Office Communications Technology Division and its
selected installation subcontractors will perform all work and tasks required to
implement and optimize the new equipment and software supplied by this
Statement of work. All manufacturers' recommendations will be strictly
adhered to for the assembly of this equipment.
• The Broward Sheriff's Office Communications Technology Division has
identified in the Regional Interlocal Agreement equipment exhibit all
equipment required to implement the aforementioned closest unit response
system. If the City of Tamarac Fire Rescue Department desires to supply
substitute or additional equipment; said equipment must be approved by
BSOCTD as being compatible with the overall system design, and any
modifications must not compromise overall system integrity.
• The BSO Communications Technology Division will commence
programming, optimization, and installation work at the mutually agreed upon
installation facility when all equipment has been received and all connectivity,
interfacing, and integration work has been completed. The start of this work
will be coordinated with the City of Tamarac Fire Rescue Department point of
contact.
• Either party may request changes within the general scope of this SOW. If a
requested change causes an increase or decrease in the cost or time required to
perform within this SOW, the parties will agree to an equitable adjustment of
FM
TR1 1660 - Exhibit A
the price difference and installation schedule. Any requested chances to this
statement of work must be submitted in writing and a change order \vill reflect
the adjustment. Neither, the BSO Communications 'Technology Division or
the City of Tamarac Fire Rescue Department is obligated to perform requested
chan`Tes unless both parties execute a \Nritten change order.
• All work will be done at a mutually agreed location and time.
~--� r • This —project will be considered complete upon installation, configuration,
testing, and signoff by both parties.
Equipment Photos
T
Panasonic CF-30
Gatnber--Jt)hnsoii 'I'i1t-Sfvivel Attach mien i
25
Ledco Mount
Gainbei-4ohnson Adaptet- Flute
TR11660 - Exhibit A
HIBIT "All -
CHMENT 1
SYSTEM DESCRIPTION
To be provided at Detailed Design Review Phase of the project
HIBIT "A" -- ATTACHMENT
Acceptance Test Plan
To be provided at Detailed Design Review Phase of the project
26
CAD System
Advanced Tactical
Mapping
Fire Records
Management
System
TRI 1660 - Exhibit A
EXHIBIT "B" —ATTACHMENT 1A
Regional Public
CITY LAN
Intranet Demarcatic
Non -Dispatch Facility
Responsibility
Infrastructure up to and
including physical network
connectivity from the RPSI
to a single pre -defined
CITY location.
CITY LAN Infrastructure up to.and
including physical network
connectivity from the RPSI
to a single pre -defined
CITY location.
CITY LAN Infrastructure up to and
including physical network
connectivity from the RPSI
to a single pre -defined
CITY location.
FRMS. standard site and
client desktop software
licenses will be provided
from SHERIFF to CITY.
27
Points
Responsibility
All extended CITY LAN
equipment along with software,
client licenses, desktop
workstations, peripheral
equipment to provide
communications to City "read
only" CAD workstations and all
existing interfaces. (Future
interfaces to the SHERIFF -
supplied systems do not apply.)
All extended CITY LAN
equipment along with software,
client licenses, desktop
workstations, peripheral
equipment to provide
communications to City ATM
workstations and all existing
interfaces. (Future interfaces to
the SHERIFF -supplied systems
do not apply.)
Desktop hardware and all LANs
connected to the FRMS; non-
standard or customized software
desired by CITY
TR11SS0 - Exhibit A
EXHIBIT "B" —ATTACHMENT 1 B
Re_ Tonal Public Safety Intranet Demarcation Points
Mobile Data - Fire Rescue Frontline Vehicles
Part
___BPSI
Responsibility
Responsibility
Trunked Radio
Gold Elite Console(s)
Infrastructure up to the
All mobile and portable
System
SHERIFF -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
up to and including the
All vehicle related
CAD server, MDT
peripheral equipment
hardware, MDT regional
and any monitoring
CAD client software
equipment. Non -
licenses, and the needed
Regional or customized
communications via the
software desired by
RPSI.
CITY. (Future interfaces
to the SHERIFF -
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.
TR11660 - Exhibit A
RPSI Portion
Demarc
SHERIFF CITY
Responsibility Responsibility
Mobile Data
Frontline Vehicle
SHERIFF 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
SHERIFF
SHERIFF infrastructure up Acquisition of FIRMS
Management
infrastructure
to and including the FRMS standard site and client
System
Server and the needed mobile software licenses
communication interfaces will be the responsibility
via the RPSI. of CITY. All vehicle
related peripheral
equipment and any
monitoring Equipment.
Non -regional or
customized software
desired by CITY.
(Future interfaces to the
SHERIFF -supplied
systems do not apply.)
29
TRI 1660 w Exhibit A
EXHIBIT "B" - ATTACHMENT 2 (Drawings)
MM &A Raw an
mmum famm
LsOW nit W Oftip 0owolow Noo4>wpsftk Fwft
S#IERPFF RESnMSIBSUTIES
*Pam Iftm
onGnAq
as JV: si -r&m*W
ow
4
1 4;;;;* A&W 3." ftu.* Nopom
, 4.q INO ows Mae" - 4400%
V4mwGsm mot 'w A sink Sj" ow$kwm vwk pmbq s�m
WWr MPS#4'L:4p Lg"Apft %PMM6* ig d*n*pg#PWoa ps
Dab
Mmi Oft*' ftoft $ship &WMN
Lq*awoma fteop o"Wom "Ohdo Da w PRO ftegm
FONOMY66WO
sooleftft PI bw I
INERwFaffspOSSMANS
fw* k*Wwo r I . .- — . -
X" I &I I go Moll I
OR I
*ad P"dft
v
141.4,:= An - W.:Wt, oft; 4%4 J No
I "09;*k *-"34 evvpom
140000 visa udsv swoova Tftwww.,Gftwo
• 8=pAk 54* go* !;Toqw" Na&MM
PW& TPA% 0004 iaft tovoke L"Ja*
PVMU SOM *00" owrv*n sw►Am
I %plod& a" bw*wo PO ftusom ar"Pia" " ks*m -00WA 40 WSW%*'
I Amd"Po Aaftom aaftwo z"m �W" TAO Me &4L. P"
off a# P," 1*01 qp6mm wall ww"
W&qwd pm = 02
tip iliney f'aaaunoliaaam0elee 1/ ampiamm odk
sm"14 0 60 owns 4P mom Pa6v3*amksw*iamwww*"ooWdIFA jmwbe%&
go&- ktie "vwq6dlqdft.rry
30
v
141.4,:= An - W.:Wt, oft; 4%4 J No
I "09;*k *-"34 evvpom
140000 visa udsv swoova Tftwww.,Gftwo
• 8=pAk 54* go* !;Toqw" Na&MM
PW& TPA% 0004 iaft tovoke L"Ja*
PVMU SOM *00" owrv*n sw►Am
I %plod& a" bw*wo PO ftusom ar"Pia" " ks*m -00WA 40 WSW%*'
I Amd"Po Aaftom aaftwo z"m �W" TAO Me &4L. P"
off a# P," 1*01 qp6mm wall ww"
W&qwd pm = 02
tip iliney f'aaaunoliaaam0elee 1/ ampiamm odk
sm"14 0 60 owns 4P mom Pa6v3*amksw*iamwww*"ooWdIFA jmwbe%&
go&- ktie "vwq6dlqdft.rry
30
TRI 1660 a Exhibit A
ftftwo ftelp 0""*& offmad c*omv 43" sysaft
:@G&cw%"Wmft""
SMER" RESPONSISWTIES
A-1
islilR MP!F4r,
~
Vapor:*
weft
SPW*JAM ALdft
ME
4 a- 0- oromm &ftom low
L4
44 I'P%V saw* swo(c
Vw* IL
SWIMPF RESPCWSM&fflE-q
Raw wfwm
swwacuro"
Aml
srvnz&" ""
Swftb MWOM)
r9shwo
VV�WVO 10 MP.% TNAMW ftft IVMR
W.' -vw Paw :vuw R4pp%u :40mm
so;�N�Cvsm
t
31
'T7
jo
am k
wv 0 'PO
.44 i
aft*&
Lan
IL
TR11660 - Exhibit A
LOOM NNWM* Defies brr 11900014.Co" Red* sysa t
SNIFF RESldIHbLITIS
rpm„i
• .t�7fa
+
O
w�+ h � w.:M Nsli► s .�: •. =s• n �rtw oOC�li i
7
tU � •y'. «;. r.�1iiY
•.,hF
E«+SE
i
32
TRI 1660 - Exhibit A
EXHIBIT "C„
Equipment List
Model numbers are provided for reference only in this proposal and are subject to change.
Equipment list will be provided at detail design review phase of the project.
33
TRI 1660 = Exhibit A
EXHIBIT D
Change Management Request
ure
Broward County Sheriff's Office
Communications Technology
Division
34
TR11660 Exhibit A
Change Management Request Procedure
Introduction
This document defines the Change ,Manaae,m=, Request (CIVIR) 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, BI Query, PMDC, UDTIDSS,
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.
Sco e
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 Requirements
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:
changem�anagement SHERIFF=.org
• SHERIFF's Communication Technology Division (CTD). will review all
requests and obtain consensus from Operations and from all impacted end -
users on scheduling the Maintenance Window for the request.
35
TR11660 - Exhibit A
• 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 project. Stop times must take into account the time
needed to restore the system to an operational state.
• Following SHERIFF CTD 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 CTD Program
Manager prior to the start of the scheduled work.
MOP Reguireme is
• 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.
Emer-genev 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 Communications
Technology Division (CTD). An on -call list will be provided to each 911/Dispatch
36
TR11666 - Exhibit A
Center Duty Officer and Manager. The CTD 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:
Upon notification, use remote access to diagnose and repair the problem or
arrive on site within rthe contracted time frames of the responder's
maintenance agreement..
• Assess the nature and scope of the problem.
• Notify the SHERIFF CTD 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 SHERIFF CTD 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.
• SHERIFF CTD 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.
37
TR1 1 666 - Exhibit A
• The standard weekend Maintenance Window for
Communications Operations is 5:01 AM — 02:00 PM Saturday
as otherwise specified by the Operations managers.
Public Safety
and Sunday or
• 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 SHERIFF's CTD.
Progesra Work Flow
R,eq uesto r
Submit Review Request
' Request to_..._............................................................... Log in CMR E
CTD i Database
L
Assign
Program
Manager
_.. _,. Program Manager
_..__........_.._. ....... ... ......._... _..... ...
.
Reviews MOP
i
Revisw MOP
�____ _..._._ _ ...-................_.....__..N� � Yes......._.......- ..
' and Resubmit _.._ _.. _ .. _.._. ... `,Approved?
i
f Review Results,
i Notify End --Users
of Unsuccessful
Attempt
Now,/CMR Project
- S uccessfu l
.,Completion?_
V
1 __
— Schedule
Maintenance 1
Window With All ('
-- Parties
Send E-mail i
f Notices to
I End- Users
Yes Close CMR. Notify End -Users
- Document the of Successful 1
Results. f Completion
Cof mp
`0_ W O
a p
1,26
C'� � ? C C� � C � QW C.� � C RS C,�i y ���•�t �
eo �.. o� •� 0. o
u. c(CW c
Q .a L. O C Ca p ....• 'v L V� +� t
Z a.zu.a 00 O a`zw o�.4)*0
Q O 01 a, o
r
x
ul
0 E m tv E go .a E m c
�r-
rr
ce
M:3a to �zsN�O BOO=lo
� ,�.► �-H.Cw
.,.. 0
tv
cc 10
CL
CL
�°- • .O0 �i/?u 0L•��Q� Cie
god
•--
..— ` III •— *j .•..• [ 1 I/ w••. C •� r +ter � W
04. � a� smV
a. d a t--
as
z 0 4) 4) 't &
0 1
a a s d oc a Q ac
d
U. �.
co co W E
LU
E
TR11660 - Exhibit A
End -User Notification
Not less than ten (10) business days prior to an approved CMR project affecting the Regional Public Safety Intranet, the SHERIFF
CTD 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.
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
the impact of the work on the end -user while the work
the work on the restored system or application.
of the work being performed;
is performed and the effect of
• Telephone numbers of project managers and key staff involved in the activity.
AiDprova! Authority
Any and all activities being performed must be supported by an approved CIVIR document.
L-4 0
TR11660 - Exhibit A
Public Safety Communications
Communications Technology Division
Change Request Form
Note: Complete and submit to the Communications Technology Division at
Chanqe M-anagementasheritt.ora. 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:
Reguestor Name:
Requestor Company Name or
Agency:
Requestor E-Mail:
Reguestor Phone Number:
Office:
Mobile:
Briefly describe the Work to Be
Performed:
Identify End -Users & sites impacted
by the work to be performed:
C-41
TR11660 = Exhibit A
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:
Identify your On -Site Contact during
the scheduled Maintenance Window:
Requested Maintenance Window for
Work to be Performed:
Approved Maintenance Window for
Work to be Performed:
Maintenance Window
Approved By:
Assigned MOP Tracking Number:
Name & Contact Number:
Start Date & Time:
Stop Date & Time:
Start Date & Time -
Stop Date & Time:
Date:
C-42
TR11660 - Exhibit A
Method of Procedure —for Prim(,,
ontr
�tor or
ry ice 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:
Describe back -out and
restoration plans if stated project
goals are not achieved within the
allotted Maintenance Window:
C-43
TR11660 - Exhibit A
j CTD to complete Items 1 through 10 Below:
1
� (1) CTD COt1t8Ct for
Project:
(2) Name:
I (3) Mobile Phone Number:
(5) MOP Type:
(6)
FYI —Non-Service Affecting:
❑
(7) Scheduled —Potential Service Affecting:
❑
(8) Scheduled —Service Affecting:
❑
(9) Scheduled —Outage Required:
❑
(10) Emergency:
❑
Reviewer Comments:
Method of Procedure Approved By:
Date Approved
C-44
TR11660 - Exhibit A
EXHIBIT "E"
Proiect Charter
PROJECT CHARTER
General1. • • •
Project Name:
Department/Agency Sponsor:
• What department 1s the primary proponent of this
project? {Enter one.)
• Who, within that department, is the Project Sponsor?
• Is this a Regional Project, i.e. does it have significant impact on regional applications or
resources (YIN)?
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
i
s '
Name
Project Manager:
Tech Lead:
Agency Lead:
Department Telephone
Others (those with a significant interest in this project):
3
E-mail
C-45
TR11660 - Exhibit A
Project4. Description
Project Purpose / Business .Justification
Objectives
Deliverables
Clear Statement of What This Project Will Not include
Project Success
Project Milestones
Major Known Risks(including significant Assum tions
Risk Rating (Hi, Med, Lo):
List the most significant risks to the project:
I.
Constraints
C-46
TR11660 - Exhibit A
External Dependencies
5 Financial Resources Information
Funding Source Select one of ilie following: Operating Budget, Capital Budget, Grant, Other. (If Other, please provide a
description)
Estimate of Implementation Cost
Implementation Cost: $
Estimate time required of Multim'Department Staff (Add rows as needed
Role
Hours needed
Estimate time required of other Organization Staff(Add rows as needed
Rote
Hours needed
In the CalendarMscal Year column, change years as appror ate.
In the Capital and Op eradonal columns, dick on each entry once to select the full field (0. 00) completely before entering
the dollar figure.
In the Totals row, total the dollar figure in each column by placing the cursor on dollar figure field, clicking once to select it,
then licking the right mouse button and selecting Update Field.
Calendar Year (I -j 29 3) or Fiscal Year
(2004-59 2006-6)
Capital ($U.S.)
Operational ($U.S.)
2007-8 1 0.00 f 0.00
C-47
TR11660 - Exhibit A
2008-9
0.00
000
2009- 10
20010-11
O.00
0.00
0.00
0.00
20011-12
0.00
0.00
Totals
0.00
0.00
Place an X in the appropriate aciaaent boar:
Organization -Managed and Hosted
Vendor -Managed and Hosted
Organization -Managed, Vendor -Hosted
Vendor -Managed, Organization -Hosted
Place an X in the appropriate aafacent box:
Sole -Source / Amend Contract
RFP I Competitive Bid
In -House / Custom -Develop
Other:
8. Types of Vendor Assistance
Place an X in the appropriate adjacent box:
Tumkey Solution
Supplemental Staffing (Time/Materials)
Vendor -Assisted (Fixed Price)
Hardware l Software
Other:
None I Not Applicable
9. Sign -off
Name
Title
Signature Date
(MM/DD/YYYY)
Business Sponsor
Project Manager
Customer A
Customer B
Customer C
[Customer D
C-4 8
TR11660 - Exhibit A
10. List of Addenda
List all files supplemental to this Charter here.
Document Name
Rename and Location
C-49
TR11660 - Exhibit A
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 SHERIFF. 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 SHERIFF 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, SHERIFF will not be held responsible for
Resolution time frames listed below.
1
Failure/Outage occurs when the system is not
functioning which prohibits continuance of
mission critical operations.
s30 minutes of initial
voice notification`
Resolve within 24
hours of initial
notification'
2
Failure occurs when an element in the system is
s 24 business hours
Resolve within 5
not functioning that does not prohibit continuance
of initial voice
standard
of normal daily operations.
notification.*
business days of
initial notification*
3
An Inconvenience occurs when software or
s48 business hours
Resolution
hardware causes a minor disruption in the way
of initial notification
determined on a
tasks are performed but does not stop workflow.
case by case
basis.
*Does not apply to "READ-ONLY" CAD Systems
1.2 The CITY System Administrator 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 SHERIFF.
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 SHERIFF by CITY representative or System Administrator.
C-50
TR11660 • Exhibit A
SHERIFF will notify the CITY if SHERIFF makes any changes in Severity Level (upgrade or
downgrade) of any CITY -reported problem.
1.4 SHERIFF 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
SHERIFF Customer Support Center ("CSC") via telephone at 1-954-831-8301 or email at
bsosuoeortO_magic. com.
1.6 SHERIFF will provide CITY with a resolution within the appropriate Resolution Time and
in accordance with the assigned error Severity Level when SHERIFF diagnostics indicate that
the error is present. Additionally, SHERIFF will verify: (a) the Hardware and Software operates
in conformity to the System Specifications, (b) the Hardware and Software is being used in a
manner for which it was intended or designed, and (c) that the Hardware and Software is being
used only with SHERIFF approved Hardware or Software. Resolution Time period shall not
begin to run until such time as the verification procedures occur. SHERIFF will continue to
provide service support under this Inner Local Agreement until final resolution is determined.
1.7 Should SHERIFF determine that it is unable to correct such reported error within the
specified Resolution Time, SHERIFF 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 SHERIFF Management.
1.8 Any and all Maintenance Service provided for herein shall be warranted under the,
following terms and conditions:
a) 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 SHERIFF.
c) The System is free of any evidence of negligence, misuse and/or abuse, intentional or
otherwise.
1.9 Unless otherwise specified herein, any and all suspected errors will be investigated and
corrected at SHERIFF Facilities. SHERIFF shall decide whether on -site correction of any
Hardware and Software error is required.
1.10 Any third party equipment supplied by SHERIFF shall be guaranteed by the
manufacturer's warranty for that equipment.
2.0 RECORD —KEEPING AND REPORTING RESPONSIBILITIES
2.1 SHERIFF will provide verbal and written status reports on Severity Level 1 troubles.
Written status reports on outstanding errors will be provided to CITY System Administrator on a
monthly basis upon request.
2.2 SHERIFF shall provide annual account reviews to include: a) service history of site; b)
downtime analysis; and c) service trend analysis.
2.3 SHERIFF will prepare the following reports (for PremierCAD software only), to include:
C-51
a) System Analysis
55TIt
b) Pathway Analysis
TR11660 - Exhibit A
MEASURE: Evaluate disk and CPU load
PEEK: Evaluate memory availability and use
VIEWSYS: Evaluate use and availability of PCBs
EMSA/'fMDS: Review logs for hardware reports
File Sizing: Review file sizing on changeable files
Evaluate effectiveness of system configuration for current
va ua a erver 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 the 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 SHERIFF performs service at the System location, CITY agrees to provide
SHERIFF, 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 information pertaining to the CITY owned hardware and software
elements of any equipment with which the System is interfacing that enable SHERIFF to
perform its obligations under this Service Agreement.
3.3 It is
not required that parts furnished
by SHERIFF be newly manufactured.
SHERIFF
warrants such parts to be equivalent to new
in performance. Parts replaced in the
course of
repair shall,
at the close of maintenance, become SHERIFF's property.
3.3 CITY will provide a qualified System
Administrator for the Printrak System
Portion to
perform all
functions as defined in Printrak's
Systems Administrator's guide which
has been
provided to
the
CITY
under
separate cover.
3.4 Upon the expiration or earlier termination of this Agreement, CITY and SHERIFF 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 shall include: (a) Proprietary materials
and information regarding technical plans; (b) any and all other information, whether in a
softcopy or hardcopy medium, including but not limited to data, developments, trade secrets and
improvements that is disclosed in any form by SHERIFF to CITY; (c) all GIS, address,
telephone, or like records and data provided by CITY to SHERIFF that is required by law to be
held confidential.
3.5 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 SOFIWARE UPDATES
C-52
TR11660 - Exhibit A
SHERIFF shall provide software updates 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".
enhancements and improvements such as new databases, modifications to databases, new
serverlrequesters, 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 to be 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 license fees for SHERIFF provided
Software Releases.
4.5 At CITY's request, SHERIFF 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 SHERIFF's network to
the latest compatible revisions.
5.0 ADDITIONS AND CHANGES
5.1 The CITY may request an enhancement to System functionality. Enhancement requests
are submitted to SHERIFF Communications Technology Division (BSO CTD) for review. If BSO
CTD accepts the enhancement request, request will be referred to the Program Management
Team for possible inclusion in a future project. SHERIFF CTD will provide a response to the
enhancement request within ninety (90) standard business days upon 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.
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 access is not allowed or available.
7.0 EXCLUSIONS
C-5 3
TR11660 - Exhibit A
7.1 Maintenance Service and Support not listed in this SLA are excluded, and SHERIFF
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;
personal property and/or devices connected to the System (or interconnected to devices)
whether or not installed by SHERIFF$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;
fl The repair or replacement of parts resulting from the tampering by persons unauthorized
by SHERIFF 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 -SHERIFF provided application software including service of any
accessory, attachment, or component owned by CITY, whether or not installed by SHERIFF;
h) Removal, relocation, and/or reinstallation of System or any component thereof;
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).
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 SLA 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 8 a.m. — 5 p.m. (local time) Monday —Friday
hour
$150 per After 5 p.m. Monday —Friday, and all day on Saturday,
hour Sunday and SHERIFF established holidays
Travel In addition to the above hourly labor rates, all other actual
Expense travel related expenses may be charged to CITY.
C-54
TRI 1660,w Exhibit A
LIST OF HARDWARE and SOFTWARE
The following lists the System hardware and software items under the ILA
coverage/control of SHERIFFs area of responsibility:
Service Level Agreements
Trouble Ticket Workflow
87AIRT
< CAD C F R MOS (SIMPt> > > < W"
Ratia)CAO NO so AT&T NOto NO P NO MOUS ON* NO P49 4O0-<`SLM0MA" NCO- FKNY
ow
< <�=Sw < (30"Pro)
N,
NO
YES
V
Coo Mdorow
8004234949
SwMe
Number
7
cam
qW 00 /
YES
YES V
OMM M"'M
-YES Ticko'CAD YES...-- YES -
Cal AT&T
Tochruaw
.. . . .... ...
A� diVa4dod W
SLA
, 3A
4
NO
. YES . - - ...
YES
Open MIP&
Radio
V
Me andl EtcalMe to ISSM ow"�
E ZTrmjblba ons ot*dt
�scsiAa 10
11 aPP(WnM 4-NO-- tonor"Mand -_%ES-*,, few YES j and END
action eso CrD Omer
pion < >
NO
Troubis,
Esralift W
tasowed Pair
SLA
SLA?
"', I
I- N-MMAJ 3M* $Cam MtQt*MAW%dk BSOCID,
-55-
Lax 2
ASSIGNMENT, DELEGATION, AND RELEASE AGREEMENT
THIS ASSIGNMENT, DELEGATION, AND RELEASE AGREEMENT ("Assignment") is
made by and among SCOTT J. ISRAEL, AS SHERIFF OF BROWARD COUNTY, FLORIDA
("Sheriff'), BROWARD COUNTY, a political subdivision of the State of Florida ("County"), and
CITY OF TAMARAC ("City"), a Florida municipal corporation.
WHEREAS, on or about September 24, 2009, Sheriff and City entered into a Regional
Interlocal Agreement with the City to establish a county -wide interoperable public safety intranet
that can support closest unit response in life threatening emergencies and regional specialty
teams (herein referred to as the "Assigned Regional Interlocal Agreement");
WHEREAS, effective October 1, 2012 at 12:01 a.m. (the "Effective Date"), County has
undertaken the operation of the Regional Communication System ("System") and in order that
County may properly perform its functions as the operator of the System, it is appropriate that
the Assigned Regional Interlocal Agreement between Sheriff and City be assigned by Sheriff to
County;
WHEREAS, as of the Effective Date, County has agreed to assume Sheriff's rights,
duties and obligations under the Assigned Regional Interlocal Agreement;
WHEREAS, Sheriff is willing to assign the Assigned Regional Interlocal Agreement to
County and County is willing to accept the assignment of the Assigned Regional Interlocal
Agreement;
WHEREAS, on February 26, 2013, the Broward County Board of County Commissioners
("Board") authorized the County Administrator to, inter alia, enter into agreements necessary for
the assignment of contracts and agreements necessary to expedite the
implementation/facilitation of regional communications service delivery through the County's
Office of Communications Technology; and
WHEREAS, the parties desire to enter into this Assignment in order to formalize the
assignment to the County of all of the Sheriff's rights, obligations and responsibilities under the
Assigned Regional Interlocal Agreement.
NOW, THEREFORE, in consideration of the mutual terms, conditions, promises,
covenants, and payments hereinafter set forth, Sheriff, County, and City agree as follows:
ARTICLE 1
DEFINED TERMS; RATIFICATION; CONFLICTS
1.1 Defined Terms. All defined terms in this Assignment shall have the same meaning as in
the Assigned Regional Interlocal Agreement, except as otherwise noted.
1.2 Ratification. Except as amended and modified by this Assignment, all of the terms,
covenants, conditions, and agreements of the Assigned Regional Interlocal Agreement
are hereby ratified and shall remain in full force and effect. Specific amendments to the
Assigned Regional Interlocal Agreement made pursuant to this Assignment are indicated
herein with bold underlining used for additions and strikeout for deletions.
i
1.3 Conflicts. In the event of any conflict between the provisions of the Assigned Regional
Interlocal Agreement and the provisions of this Assignment, the provisions of this
Assignment shall control.
1.4 Term. Notwithstanding anything to the contrary in the Assigned Regional Interlocal
Agreement, the initial term of the Assigned Regional Interlocal Agreement shall conclude
on September 30, 2015, and may be renewed commencing October 1, 2015 in
accordance with the remaining terms of the Assigned Regional Interlocal Agreement.
ARTICLE 2
EFFECTIVENESS
The Effective Date of this Assignment shall be October 1, 2012 at 12:01 a.m. nunc pro
tunc. The Assignment is expressly subject to and contingent upon the approval and execution of
this Assignment by all parties. The County Administrator shall execute the Assignment on
behalf of the County under the authority granted by the Board with subsequent filing with the
Board.
ARTICLE 3
ESTOPPEL
The Sheriff and City represent the following:
3.1 The Assigned Regional Interlocal Agreement is the sole agreement pertaining to the
provision of establishing a cooperative participation in a Regional Public Safety Intranet
between City and the Sheriff, and the Assigned Regional Interlocal Agreement has not
been modified in any manner except as stated herein;
3.2 Neither Sheriff nor City has given a notice of default under the Assigned Regional
Interlocal Agreement to the other party, neither Sheriff nor City is in default of its
obligations under the Assigned Regional Interlocal Agreement, and no known
circumstances exist which, with the giving of notice or passage of time, would ripen into
a default under the Assigned Regional Interlocal Agreement; and
3.3 All obligations of the parties under the Assigned Regional Interlocal Agreement up to the
Effective Date of this Assignment have been fully performed and paid for by the
respective parties.
ARTICLE 4
ASSIGNMENT AND DELEGATION
4.1 As of the Effective Date, Sheriff does hereby assign and delegate to County, as
assignee, all of its right, title and interest in and to the Assigned Regional Interlocal
Agreement, including all right, title and interest in all reports, documents, or other data
prepared and/or provided by City thereunder in connection with or related to the
Assigned Regional Interlocal Agreement.
4.2 As of the Effective Date, County, as assignee, hereby accepts the assignment and
delegation of the Assigned Regional Interlocal Agreement and further agrees to assume
all of Sheriff's obligations thereafter under the Assigned Regional Interlocal Agreement
2
and agrees to perform and keep all of the terms, conditions, covenants, agreements,
liabilities and obligations to be performed thereunder from and after the Effective Date.
4.3 City hereby acknowledges and consents to the assignment and delegation by Sheriff to
County of the Assigned Regional Interlocal Agreement as set forth herein, and County
agrees to perform its obligations hereunder and be bound to City pursuant to the terms
of the Assigned Regional Interlocal Agreement.
4.4 The parties acknowledge and agree that in the event said assignment is not made within
sixty (60) days of the Broward County Board of County Commissioner's approval on
February 26, 2013 of the transfer of regional communication services from Sheriff to
County, the County shall provide services to City for a period not to exceed thirty (30)
days provided that the City provides a letter from its Manager, or equivalent position,
stating that City desires to receive Regional Communication Services from County and
will forthwith seek its Board's approval with an affirmative recommendation by the City
Manager, or equivalent position, to approve the assignment.
ARTICLE 5
RELEASE
Sheriff and City hereby release and forever discharge each other, and their respective
successors and assigns for all actions, causes of actions, suits, debts, damages, judgments,
claims, demands, agreements, promises and obligations whatsoever, in law or in equity, which
each party had, now has, or may have, or which any successor or assign of each party can,
shall or may have, against the other party arising out of, related to, or in connection with
actions or omissions under the Assigned Regional Interlocal Agreement prior to the Effective
Date.
ARTICLE 6
AMENDMENT OF TERMS AND CONDITIONS OF ORIGINAL AGREEMENT
6.1 As of the Effective Date, all references in the Assigned Regional Interlocal Agreement to
Is "Broward County Sheriff's Office," "BSO" shall be deemed to refer to "County"
and all references to the Sheriffs Communications Technology Division or "CTD" shall
be deemed to refer to the County's Office of Communications Technology unless
otherwise expressly stated herein.
6.2 The address for notices to County under the Assigned Regional Interlocal Agreement
and the agreements attached thereto are hereby amended such that any notice to
County after the Effective Date shall be made to the following:
TO COUNTY:
Director of Office of Communications Technology
Attention: Richard Carpani
115 S. Andrews Ave., Suite 325
Ft. Lauderdale, Florida 33301
The names, title, addresses for notices under the Assigned Regional Interlocal
Agreement can be changed using the notice procedures therein without the necessity of
an amendment.
6.3 Section 2.19 is amended as follows:
2.19-CITY shall follow all RPSI Trunked Radio System policies and standard
operating procedures in place at the time of this Agreement as set forth in Exhibit G
hereto, as well as, those developed in the future and issued to CITY by
COU NTYS#E-PJ4zF-... .
6.4 Exhibit G attached hereto is added as Exhibit G to the Assigned Regional Interlocal
Agreement.
6.5 The following exhibits to the Assigned Regional Interlocal Agreement are deleted in their
entirety and replaced, respectively, with the Exhibits attached hereto:
Exhibit B — Demarcation Points
Exhibit D — Change Management Request Procedure
Exhibit E — Project Charter
Exhibit F — Service Level Agreement
ARTICLE 7
MISCELLANEOUS
7.1 Severability. In the event any portion or provision of this Assignment is found to be
unenforceable by any court of competent jurisdiction, that portion or provision shall be
deemed severed from this Assignment and the balance of this Assignment shall remain
in full force and effect.
7.2 Joint Preparation. This Assignment has been jointly prepared by the parties hereto, and
shall not be construed more strictly against any party.
7.3 Applicable Law and Venue.
This Assignment and the Assigned Regional Interlocal Agreement shall be interpreted
and construed in accordance with, and governed by, the laws of the state of Florida.
The parties agree that the exclusive venue for any lawsuit arising from, related to, or in
connection with this Assignment or the Assigned Regional Interlocal Agreement shall be
in the state courts of the Seventeenth Judicial Circuit in and for Broward County, Florida.
BY ENTERING INTO THIS ASSIGNMENT, THE PARTIES EACH HEREBY
EXPRESSLY WAIVE ANY AND ALL RIGHTS THE PARTY MAY HAVE TO A TRIAL
BY JURY OF ANY CIVIL LITIGATION ARISING FROM, RELATED TO, OR IN
CONNECTION WITH THIS ASSIGNMENT OR THE ASSIGNED REGIONAL
INTERLOCAL AGREEMENT.
7.4. Third Party Rights. Nothing in this Assignment shall be construed to give any rights or
benefits to anyone other than Sheriff, County and City.
7.5 Successors and Assigns. This Assignment shall inure to and be binding upon the
authorized successors and assigns of the parties.
Ell
7.6 Recitals and Headings. The information contained in the Recitals set forth above is true
and correct and is incorporated into the body of this Assignment. The headings
contained herein are for reference purposes only and shall not affect in any way the
meaning or interpretation of this Assignment.
7.7. Multiple Copies. Multiple copies of this Assignment may be executed by all parties, each
of which, bearing original signatures, shall have the force and effect of an original
document.
[REMAINDER INTENTIONALLY LEFT BLANK]
5
IN WITNESS WHEREOF, the parties hereto have made and executed this Assignment
Agreement: BROWARD COUNTY SHERIFF, signing by and through himself in his official
capacity or his duly authorized representative, BROWARD COUNTY through its County
Administrator, authorized to execute same by the Broward County Board of Commissioners
action on the 26t" day of February, 2013, and CITY OF TAMARAC, FLORIDA, signing by and
through its , duly authorized to execute same.
By:
SHERIFF OF BROWARD COUNTY
SCOTT J. ISRAEL, As Sheriff of Broward County
Approved as to form and legal sufficiency
subject to the execution by the parties:
By:
Ronald M. Gunzburger, General Counsel
Office of the General Counsel
Date:
Date:
0
IN WITNESS WHEREOF, the parties hereto have made and executed this Assignment
Agreement: BROWARD COUNTY SHERIFF, signing by and through himself in his official
capacity or his duly authorized representative, BROWARD COUNTY through its County
Administrator, authorized to execute same by the Broward County Board of Commissioners
action on the 26th day of February, 2013, and CITY OF TAMARAC, FLORIDA, signing by and
through its , duly authorized to execute same.
SHERIFF OF BROWARD COUNTY
'S By: w/1A
SCOTT J. ISRAEL, As Sheriff of Broward County
Approved as to form and legal sufficiency
subject to the execy#ien-*4lle parties:
Rona . Gunzburger, General Counsel
Office of the General Counsel
Date: P61A0 13
Date: rvl &P
N
i
�
�
i
l
ASSIGNMENT, DELEGATION AND RELEASE AGREEMENT AMONG SCOTT J. ISRAEL,
AS SHERIFF OF BROWARD COUNTY, FLORIDA, BROWARD COUNTY, AND CITY OF
TAMARAC, FLORIDA.
WITNESS:
(Signatu
(Print Name of Witness)
ANDRt MORRUL
(Print Name of Witness)
Insurance requirements
approved by Broward County
Risk Management Division
y
Si
Risk Mana
BROWARD COUNTY
1//7//,3
Divisionate)
Print 1' W; Yr WTiIle a�'ove
Risk Insurance and
Contracts Manager
AS F/RDH
06/05/13
13-099.01
2013-06-05 Tamarac RILA Assignment Agreement
BROWARD COUNTY, by and thr ugh
its Count dministrator
By /V
Co Administrator,
�'�day of
C7V , 20 13
Approved as to form by
Joni Armstrong Coffey
Broward County Attorney
Governmental Center, Suite 423
115 South Andrews Avenue
Fort Lauderdale, Florida 33301
Telephone: (954) 357-7600
Telecopier: (954) 357-7641
By
Andrea S. Froome (Date)
Senior Assistant County Attorney
and
Bv A, A 411��
q I tpl
Rene' '*Aarrod (Date)
Assistant County Attorney
13)
N
ASSIGNMENT, DELEGATION AND RELEASE AGREEMENT AMONG SCOTT J. ISRAEL,
AS SHERIFF OF BROWARD COUNTY, FLORIDA, BROWARD COUNTY, AND CITY OF
TAMARAC, FLORIDA.
ATTEST:
CITY CLERK
CITY OF TAMARAC
CITY OF TAMARAC
By:
IOF
CITY MA
Print Name
day of 144019 , 20/3
I HEREBY CERTIFY that I have approved
This AGREEMENT as to form and legal
Suffic' ncy subject to execution by the parties:
n % . / /7 J
City !Attorney
EXHIBIT "B" - ATTACHMENT 1A
Regional Public Safety Intranet Demarcation Points
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 required to operate on
Elite/P25 IP based Radio
the RPSI Trunked Radio
Console(s) located in the
System; and any advanced
Regional Dispatch Center.
features and other monitoring
equipment, as desired.
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
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-
RPSI Portion
Demarc
COUNTY
Responsibility
CITY
Responsibility
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.
EXHIBIT "B" —ATTACHMENT 1B
Regional Public Safety Intranet Demarcation Points
Non -Dispatch Facility
RPSI Portion
Demarc
COUNTY
CITY
Responsibility
Responsibility
CADS stem
y
CITY LAN
Infrastructure up to and
All extended CITY LAN
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 "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
10
RPSI Portion
Demarc
COUNTY
Responsibility
CITY
Responsibility
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.
EXHIBIT "B" - ATTACHMENT 1 C
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/CITY MDT
Infrastructure up to and
including the CAD server
All extended LAN equipment
and the needed
along with software, client
communications via the
licenses, peripheral equipment
RPSI.
to provide communications to
CITY CAD M DT's and all
existing interfaces. (Future
interfaces to the COUNTY -
supplied systems do not
apply. )
AVL System
COUNTY's Server
Infrastructure up to and
All vehicle -related equipment
including the AVL server;
and any remote monitoring
11
RPSI Portion
Demarc
COUNTY
Responsibility
CITY
Responsibility
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.
EXHIBIT "B" —ATTACHMENT 1D
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.
CADS stem
y
CITY LAN
Infrastructure and software
up to and including the
All vehicle related
CAD server, MDT
peripheral equipment
hardware, MDT regional
and any monitoring
CAD client software
equipment. Non -
licenses, and the needed
Regional or customized
communications via the
software desired by
RPSI.
CITY. (Future interfaces
to the COUNTY -
supplied systems do not
apply.)
12
RPSI Portion
Demarc
COUNTY
CITY
Responsibility
Responsibility
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 Is 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
COUNTY infrastructure up
Acquisition of FIRMS
Management
infrastructure
to and including the FRMS
standard site and client
System
Server and the needed
mobile software licenses
communication interfaces
will be the responsibility
via the RPSI.
of CITY. All vehicle
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.)
13
EXHIBIT "B" - ATTACHMENT 2 (Drawin!
14
15
WOO
-:46
mmlmn=
COUNTY-RADIO-ILA:TrunlmdRsdb ftsim-Ind&*d8ubuwbm 6d
COUNTY - STATION ALERTMNI - NA Replaml Flm OlObn AlMblp — 7+1
17
EXHIBIT D
Change Management Request
Procedure
Broward County
Office of Communications
Technology
Introduction
This document defines the Change Management Request (_) process for any
component(s) that make up the Regional Public Safety Intranet providing delivery
of services to end -users. The ` 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,
U DT/DSS, E-911, etc.
Objective
The objective of the C_ MR 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.
Sco e
The C_MR, 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 Requirements
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:
o_ ctch,angemanageme t@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.
19
• 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 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.
Emergencv 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,
responder must notify the designated
Communications Technology (OCT). An
both the affected end -user and first
on -call person for the Office of
on -call list will be provided to each
20
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:
• 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
Communications Operations is 12:01 AM — 06:00 AM Sunday
Thursday or as otherwise specified by the Operations managers.
Safety
through
21
• 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.
Chan e Management Reaue,->L
Reguestor
Su!brrrit
eq uest tea
OCT
Process Work Flow
ocT
W14
M
N
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.
24
Broward County
Office of Communications Technology (OCT)
�'"► "�Ilk
Note: Complete and submit to the Broward County Office of Communications
Technology at OCTChangeManagement(cD-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:
Requestor Phone Number:
Office:
Mobile:
Briefly describe the Work to Be
Performed:
Identify End -Users & sites impacted
by the work to be performed:
25
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
Stop Date & Time:
Work to be Performed:
Start Date &Time:
Approved Maintenance Window for
Work to be Performed:
stop gate & time:
Maintenance Window
Approved By:
Date:
Assigned MOP Tracking Number:
26
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:
Describe back -out and
restoration plans if stated project
goals are not achieved within the
allotted Maintenance Window:
27
OCT to complete Items 1 through 10 Below:
(1) OCT Contact for
Project:
(2) Name:
(3) Mobile Phone Number:
(4) E-Mail:
(5) MOP Type:
(6)
FYI —Non-Service Affecting:
❑
(7) Scheduled —Potential Service Affecting:
❑
(g) Scheduled —Service Affecting:
❑
(9) Scheduled —Outage Required:
❑
(10) Emergency:
❑
Reviewer Comments:
Method of Procedure Approved By:
Date Approved
0
No Text
31
No Text
No Text
No Text
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. 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.
1
Failure/Outage occurs when the system is not
functioning which prohibits continuance of
mission critical operations.
<_30 minutes of initial
voice notification*
Resolve within 24
hours of initial
notification*
2
Failure occurs when an element in the system is
_< 24 business hours
Resolve within 5
not functioning that does not prohibit continuance
of initial voice
standard
of normal daily operations.
notification.*
business days of
initial notification`
3
An Inconvenience occurs when software or
<48 business hours
Resolution
hardware causes a minor disruption in the way
of initial notification
determined on a
tasks are performed but does not stop workflow.
case by case
basis.
*Does not apply to "READ-ONLY" CAD Systems
1.2 The CITY System Administrator 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 Representative or System Administrator.
35
COUNTY will notify the CITY if COUNTY makes any changes in Severity Level (upgrade or
downgrade) 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
selfhel broward.or
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 operates
in conformity to the System Specifications, (b) the Hardware and Software is being used in a
manner for which it was intended or designed, and (c) that the Hardware and Software is being
used only with COUNTY approved Hardware or Software. Resolution Time period shall not
begin to run until such time as the verification procedures occur. COUNTY will continue to
provide service support under this Inner Local 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 Any and all Maintenance Service provided for herein shall be warranted under the
following terms and conditions:
a) 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 is free of any evidence of negligence, misuse and/or abuse, 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 shall be guaranteed by 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 troubles.
Written status reports on outstanding errors will be provided to CITY System Administrator on a
monthly basis upon request.
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:
W
a) System Analysis
b) Pathway Analysis
MEASURE:
PEEK:
VI EWSYS:
EMSA/TMDS:
File Sizing:
c) Performance Analysis
Evaluate disk and CPU load
Evaluate memory availability and use
Evaluate use and availability of PCBs
Review logs for hardware reports
Review file sizing on changeable files
Evaluate effectiveness of system configuration for current
load.
Evaluate TCP/Server statistics.
Evaluate efficiency of server class maximum and minimum
settings.
TMX Timings: Evaluate application response times
d) Printrak Technical Support Analyst. Based on the 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 at the System 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 information pertaining to the CITY owned hardware and software
elements of any equipment with which the System is interfacing that enable COUNTY to
perform its obligations under this Service Agreement.
3.3 It is
not required that parts furnished
by COUNTY be newly manufactured.
COUNTY
warrants such parts to be equivalent to new
in performance. Parts replaced in the
course of
repair shall,
at the close of maintenance, become COUNTY's property.
3.3 CITY will provide a qualified System
Administrator for the Printrak System
Portion to
perform all
functions as defined in Printrak's
Systems Administrator's guide which
has been
provided
to
the
CITY
under
separate
cover.
3.4 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 shall include: (a) Proprietary materials
and information regarding technical plans; (b) any and all other information, whether in a
softcopy or hardcopy medium, including but not limited to data, developments, trade secrets and
improvements that is disclosed in any form by COUNTY to CITY; (c) all GIS, address,
telephone, or like records and data provided by CITY to COUNTY that is required by law to be
held confidential.
3.5 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.
37
4.0 SOFTWARE UPDATES
COUNTY shall provide software updates 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.
remotely. Supplemental Releases are identified
number, shown here as underlined: "1.2.311
.
Supplemental Releases can be installed
by the third digit of the three -digit release
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 to be 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.
5.0 ADDITIONS AND CHANGES
5.1 The CITY may request an enhancement to System functionality. Enhancement requests
are submitted to COUNTY Office of Communications Technology (OCT) for review. If OCT
accepts the enhancement request, 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 upon 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.
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 access is not allowed or available.
7.0 EXCLUSIONS
091
7.1 Maintenance Service and Support not 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;
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).
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 SLA and such service or support shall be performed at the rates set
forth below.
Billable rates are subiect to a two (2) hour minimum:
$100 per
8 a.m. — 5 p.m. (local time) Monday — Friday
hour
$150 per
After 5 p.m. Monday — Friday, and all day on Saturday,
hour
Sunday and COUNTY established holidays
Travel
In addition to the above hourly labor rates, all other actual
Expense
travel related expenses may be charged to CITY.
39
LIST OF HARDWARE and SOFTWARE
The following lists the System hardware and software items under the ILA coverage/control of
COUNTY's area of responsibility:
M
START
Radio
YES
Call Motorola
9003?33949
Service
Number
Provide
Customer $ite
10
YoOoeele
60 porWe /
nrnMr //
EXHIBIT "F" - ATTACHMENT 2
Service Level Agreements
Trouble Ticket Workflow
CUR- \
FroL(*W
CAWMDCI Fin Records Law Records ProOA CAD Paging 0 Station N Tower Facllny
AT&T VehiclHRetMotion (FRMS) (LRMS) NO Alerting
a
s
YE8
YES YES
YE8
Call County Helpdesk
Call AT3T Call Control 9a43S73fa6 YES YES YES YES
800 247-9020 Communications seirhe"broword.org
aervi°e 9"7914 040 YES
Number Service Number
ATBT Lo
proenb
wee
nueeer
Evaluate and EscaFaoe Escelata tD bsue Trouble and
notify
--
Communioate appropriate oontlrmed and YE neotvsd per YES u° ENO
action plan of
OCT owner owned? SLA9 resolution
Escalate par Trouble ar per
su neotwd
SLA? ,
)o, toes 1: All Severity 1 Cases are to be eacalded to Broolard County OCT.
➢ Note 2: Radio Support aswmes CITY has a current minisrumnce contract with Motorola.
No 3: CITY may have current maintenance contract for station alerting.
Open Magic
Ticket "CTD
Radio Shop"
#J f"'�
. BROWARD ListiN'iY C D CONFIDENTIAL AND PROPRIETARY
RADIO / PUBLIC SAFETY APPS TROUBLE REPORTING, WORT( FLOW
Qw Wby'DWWR"
Lutedbdby.DaWK.Rr*
F abet n of I
CPWW on $"a=?
FAWM n 0 Lom edbd m 10tV2012
41
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
42
RPSCC RADIO SUB -COMMITTEE
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
43
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: 12/15/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:
Fleetmap Information
Definition
Talkgroup
Name of the talkgroup & multigroup as it is
programmed into the system
Talkgroup ID
Numerical ID of the talkgroup & multigroup
Owner
The actual "ownin " 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 t
information of the users they
shared with the other system
kept.
e responsible for managing the Fleetmap
are representing. This information is also
managers; the ID information also must be
4. Recommended Protocol/Standard:
The detailed matrix will be maintained on
example of the matrix layout is shown in this
the matrix layout
the system database. An
manual. Need to develop
Each System Manager will maintain a master Fleetmap spreadsheet
containing data on the subscribers for whom they are responsible.
5. 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
Ely,
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 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. Management:
The System Managers Group will manage the Fleetmap information and
the details of the process for communicating the information.
Standard Operating Procedures (SOP)
800 MHz Trunked Regional Public Safety Radio System
Standards, Protocols, Procedures
Document Section:
Sub -Section:
Procedure Title:
1.2
Talk Group & Radio
User Priority
Date Established: 12/15/06
Replaces Document Dated: N/A
Date Revised: N/A
1. Purpose or Objective:
RPSCC Radio Sub -Committee
Approved Date: 08/02/07
The purpose of establishing varying priority levels for talk groups
assure the most critical talk groups on the system are granted a channel
quickly as possible when the system is experiencing busy conditions.
2. Technical Background:
■ 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:
is to
as
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.
47
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
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.
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 Background:
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
cellular communications and used
basis.
Constraints
BACKUP functionality to
primarily on an emergency
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 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 Isoverdialif
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. 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, 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.
50
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 Background:
■ 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.
51
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 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 -
business related matters.
52
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 Obiective:
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 Background:
■ Constraints
Every Radio User ID in the system has to be unique; there can be no duplicate
IDs. 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 affect 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
53
alphanumeric characters in length in order to avoid contention between agencies.
Regional Operating
Agencies
and all agencies
within the
County of Broward
would
have naming
prefixes
of
at
least
two
digits
that
would
stand
alone.
Counties would be pre -named with a two digit mnemonic, and the Cities and
Agencies of the Counties would be included under the prefix of the County they
are in.
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.
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 IN 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.
54
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 COUNTY'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
Margate
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
6. Management:
The System Managers are responsible for seeing that the defined standard is
followed and maintained.
�R
STANDARD OPERATING PROCEDURES (SOP)
800 MHz Trunked Regional Public Safety Radio System
Standards, Protocols, Procedures
Document Section: 1.6 RPSCC Radio Sub -
Sub -Section: Committee
Procedure Title: Radio Model and Features Approved Date: 08/02/07
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
cod eplug/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. Cod eplugs/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
56
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 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
Description
XTS2500
Modell
XTS2500
Modell)
XTS2500
Model III
XTS5000
Modell
XTS5000
Modell)
XTS5000
Model III
XTS1500
Modell
Digital
O
O
O
O
O
O
O
SmartZone
O
O
O
O
O
O
O
57
Dual Mode
S
S
S
S
S
S
S
800/700 MHz
capable
Project 25
O
O
O
O
O
O
O
9600 SW
RF Switch
S
S
S
S
S
S
S
(764-806
MHz)
(808-870
MHz
Encryption
O
O
O
O
O
O
Software
Encryption
O
O
O
O
O
O
Hardware
Multi -Key
O
O
O
O
O
O
(Required only
if other
System Talk
Groups are
programmed
in the radio
MOBILE RADIO STANDARDS
Model Description
XTL1500
XTL2500
XTL5000
Digital
O
O
Dual Mode 800/700
MHz ca able
S
S
S
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
only if other System
Talk Groups are
programmed in the
radio
O
O
Remote Control Head
O
O
S = Standard Feature
O = Optional Feature
5. Recommended Procedures:
N/A
6. Management:
The System Managers are responsible for seeing that the defined
standard is followed and maintained.
STANDARD OPERATING PROCEDURES (SOP)
800 MHz Trunked Regional Public Safety Radio System
Standards, Protocols, Procedures
Document Section: 1.7 RPSCC Radio Sub -
Sub -Section: Committee
Procedure Title: Radio Auxiliary Equipment Approved Date: 08/02/07
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 subscriber's 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.
59
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 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 specific to radio
models MTS2000 (antennas only), XTS3000 and XTS5000
series.
Antenna:
• 806 — 870 MHz -1/2"
Wavelength
Whip
(MTS2000
only)
• 806 — 941 MHz -1/4"
Wavelength
Whip
(MTS2000
only)
(batteries 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 XTS500:
•
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 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. Management:
The System Managers are responsible for seeing that the defined standard is
followed and maintained.
61
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
entity/municipality (see
department/agency within
fourth character will have
of the TG alias identify the talk group governing
Table 1). The third character identifies the
the governing entity/municipality (see Table 2). The
a dash (-) as a separator. The remaining available
62
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.
5. Recommended Procedures:
N/A
6. Management:
The System Managers are responsible for seeing that the defined standard is
followed and maintained.
63
Appendix A
Purpose:
The following is required in order to standardize and document talk group naming
convention for the Broward County SmartZone 80OMhz 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 departmentlagency 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
ZZZZZZZZ
Talk group alias name
Dash separator
Ingle Letter Department Identifier (see Table 2).
T o Letter Identifier (see Table 1).
example o «D I P - 4 1 A = PBBIBSC dispatch channel "Disp4A"
example:
OMMEMUSUMUME
= 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
ZZZZ
Talk group alias name
Dash separator
Ingle Letter Department Identifier (see Table 2).
T140 Letter Identifier (see Table 1).
example - D S P 4 = PSBIBSO dispatch channel "Disp4A"
example. D T 1 = 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)
Tables
Table I
BD
Broward Count
B S
B rows rd Sheriff Office
CC
Cooper City
CK
Coconut Creek
CS
Coral Springs
DN
Dania
DR
Deerfield
DV
Davie
FL
Fort Lauderdale
HA
Hialeah, Miami Dade Ct .
HD
Hallandale
HW
Hollywood
LH
Lauderhill
LL
Lauderdale Lakes
LP
Lighthouse Point
LS
Lauderdale by the Sea
LZ
Lazy Lake
MC
City of Miami, Miami Dade Ct .
MB
Miami Beach, Miami Dade Ct .
MD
Miami -Dade Count
MG
Margate
MM
Miramar
NL
Forth Lauderdale
OP
Oakland Park
PC
Palm Beach Count
PB
Pompano Beach
PD
Parkland
PK
Pembroke Park
PL
Plantation
PP
Pembroke Pines
SF
State of Florida
SM
Seminole
SN
Sunrise
SR
Sea Ranch Lakes
SDI
Southwest Ranches
TM
Tamarac
WIVI
Wilton Manors
W P
West Park
WS
Weston
* To be used only by B rowa rd Sheriffs Office
Table 2
A
Airport
B
FUTURE USE
O
Communications
D
FUTURE USE
E
Port Everglades
F
Fire Rescue
G
FUTURE USE
H
FUTURE USE
I
FUTURE USE
J
FUTURE USE
K
FUTURE USE
L
Local Government
ICI
Mutual Aide
N
IFUTURE USE
P
Police
Q
FUTURE
USE
R
P a rl+cs &
Fie c
S
School
T
FUTURE
USE
U
FUTURE
USE
FUTURE
USE
FUTURE
USE
FUTURE
USE
Y
FUTURE
USE
Z
IFUTURE
USE
65
STANDARD OPERATING PROCEDURES (SOP)
800 MHz Trunked Regional Public Safety Radio System
Standards, Protocols, Procedures
Document Section: 1.9
Sub -Section:
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:
RPSCC Radio Sub -Committee
Aaaroved Date: 08/02/07
The intent of this standard is to provide an option
system, which will allow the talk group owners to
sharing authorizations for other agencies.
2. Operational Context:
to the users of the 800 MHz
"at their discretion" predefine
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 T" 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 specific purpose talk groups, i.e., only
dispatch consoles, only neighboring cities, etc. The letter will be
on file with the appropriate System Managers.
L = Like agencies may share, "Fire, Medical, Law, Public Works, etc."
A = All agencies.
RX = Only authorized to receive.
TX = Authorized to transmit and receive.
4. Recommended Procedures:
The System Managers, working with the user groups, would perform this task.
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
67
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.
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 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/monitoring privileges may be pre approved by the affected Talk
Group owners and System Managers.
Before Scanning of owned Talk Groups, permission must be granted.
permission must come from:
■ The System Managers of the sites that are being requested for the Talk
Group
■ The jurisdiction/agency who is the "owner" of the requested Talk Group
Mutual aid, special roaming and other shared Talk Groups may be Scanned at
any time; however, "requested site" determinations will be made by the System
Managers of the affected sites.
5. Recommended Procedures:
70
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 sites)".
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 sites)". Doing so however, will consume a repeater channel
on your primary/home system or "always preferred site(s)11 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 "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.
S. 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.
71
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 Background:
■ 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 specific 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.
72
■ 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.
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 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 specific 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.
73
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 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
74
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. Management:
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.
75
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 Background:
■ 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 specified 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 IN 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 D I U .
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.
76
3. Operational Context:
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.
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.
77
6. Management:
The System Managers group and the agencies upper level management will be
the responsible authority for Encryption issues.
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. Management:
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 JG) 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 then 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 JDATA) signal.
The TDATA signal consists of an OSW followed by an LSHS signal, followed by
79
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 -governmental 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 multi -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 halts 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 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 Chief's, 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 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 alphabetical 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
EDICS Emergency Deployable Interoperability
Communications System
EMS - Emergency Medical Services
EMRS - 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
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 Skem
Managers /Administrators of the regional system will establish names for the
Radio IDs used to support dispatch console positions. This is necessary
because IN 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.
41 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
5. Management:
The System Managers / Administrators are responsible for ensuring compliance
with the standard.
No Text