HomeMy WebLinkAboutContract 44646-A1CITY SECRETARY CONTRACT NO. �a�i-� ' A I
AMENDMENT NO. 1 TO
CITY SECRETARY CONTRACT NO. 44646
SYSTEM PURCHASE AGREEMENT
BETWEEN CITY OF FORT WORTH AND
MOTOROLA SOLUTIONS INC.
This Amendment No. 1("Amendment") to City Secretary Contract No. 44646 System Purchase
Agreement ("Agreement"), is made and entered into by and between the City of Fort Worth (the
"City"), a home rule municipal corporation situated in portions of Tarrant, Denton, and Wise
Counties, Texas acting by and through Susan Alanis, its duly authorized Assistant City
Manager, and Motorola Solutions, Inc., ("Consultant"), acting by and through Michael Duke its
duly authorized Territory Services Director, collectively referred to as the "Parties."
RECITALS
The following provisions are true and correct and form the basis of this Amendment:
WHEREAS, on or about July 24, 2013, the parties entered into a System Purchase Agreement
("Agreement") to purchase radio communications equipment and services. The Agreement is a
public document on file in the City's Secretary Office and referenced as City Secretary Contract
No. ("CSC") 44646; and
WHEREAS, the Parties wish to amend the agreement to incorporate changes agreed to during
the Design Review and in accordance with the Agreement, to modify the system description,
statement of work, project schedule, and other items as deemed necessary and agreed to by
the Parties.
NOW, THEREFORE, for good and valuable consideration, the receipt and adequacy of which
are hereby acknowledged, the City and Consultant agree as follows:
1.
The agreement shall be modified to incorporate changes agreed by the Parties during
the design Review set forth herein and in the following Change Order 1, which is attached
hereto or incorporated by reference and hereby made a part of this Agreement. The agreed
changes include replacing in their entirety the original System Description, Statement of Work,
and Project Schedule with the following documents:
1. Change Order 1 Section 1 System Description
2. Change Order 1 Section 2 System Drawings
3. Change Order 1 Section 3 Equipment List
4. Change Order 1 Section 4 Acceptance Test Plan
5. Change Order 1 Section 5 Statement of Work
CFW / MOTOROLA
Amendment No.1 to CSC No. 44646
Page 1
I�E.C�I�l�� .l�N � 3 �C11�
;; ° �-�-�=
,
� �P�ICI��. RECOidD
G �0'TY ��CR�T��tV
� f�i'. �111"�R'6"6�N, '�"�(
�
6. Change Order 1 Section 6 Project Schedule
The agreed changes also include the addition of the following new document:
7. Change Order 1 Section 6, Addendum A— BGA Questions and Answers
2.
All other provisions of the Agreement that are not expressly amended herein shall
remain in full force and effect.
Executed on this the � day of �, , 2014.
/ �
CITY OF FORT WORTH:
- -� _� �
B: � ;�:�C
y ��.
Susa) Alanis
�A�s�ant City Manager
Date: , ' vl
ATTEST:
:
Mar
City
APPROVED AS TO FORM AND LE
MOTOROLA SOLUTIONS, INC.:
By: _'��l'1 t ��. t',��; .r' ;�,`�� G �-�
r 11�1i hael Duke
Territory Services Director
Date: �� � � � ��= �' �i
`Y� te��6� � � �
�� b
�g ��
�� ��
° � k
�X �'°�o�o�o°"� ,� �
_ �`�-� ��� ���('�a`�'�zr,���
'�Y� --
aleshi -Farmer - --
Senior Assistant City Attorney
Contract Authorization:
M&C G26278
Date Approved: June 4, 2013
CFW / MOTOROLA
Amendment No.1 to CSC No. 44646
Page 2
; _ _ _ _ __ _�
c ,%�@���4L �E�ORD
� ���'6'lf �E�I�ET,ARV
��i; �i". bVC�R1f�#� �X
2-
QMCiTOR��A S��LI�I�IVS
�hange �Pdep Plo. 1
� �' '; � _-: ''
�ate: October 25, 2013
�Poj�ct NaPne: Fort Worih DSft Project - TX-131109�
Custorrr�r IVaene: City of Fort Wor#h
CustameP �Pojeet Wlgp: Alan Girton
ihe purpase of this Change Ordee is to:
7he purpose is to update specific sections of ihe project documenfis after the Design Review. Updated
documents replace, in their en4ire4y, Qhe following sections of the contract (dated Ociober 25, 2013 in the
fiooter of the aftached combined F'DF document):
1. Section 1 System Description
2. Section 2 Sysfem Drawings
3. Section 3 Equipment List
4. Section 4 Acceptanc� iest Plan
5. Section 5 Statement of Work — removed references to staging, removed certain �ori Worth
responsibilities, etc.
6. Section 6 Project Schedul�
The following is also added with this Change Order:
1. Addendum A—�GA Quesfions and Answers _
Contract # Citv of Fort Worth: ^�� c5 C y�j � y L Contract Date: 7/24/2013
Nlotorola Solutions Contract: 88741
In accordance with the terms and conditions of the contract identified above between ihe City of Forf
Worth and Motorola Solutions, Inc., the following changes are approved:
Contract Price Adiusiments
Original Contrac4 Value: � $9�2,254
Previous Change Order amounts for Change Order numbers
� �, � through � N/A
L"
This Change Order: No pricing adjustment
New ConiracY Value: $952,254
Original Completion Daie: � 11/4/2013
Current Comple4ion �ate prior to this Change Order: 11/4/2013
New Complefion Date; NIA
Chan�es to Sys�ern Purehase Agreement (SPA) Provisions:
'There are no change� to the System Purchase Agreemeni (SPA) Provisions with this change order.
Chang�s bn �quiprv�eni:
The equipment changes are
in the new Section 3 Equipment Lis4
Fort Worth DSR PrOj�Ct Page 1 of 2
QMOTOROLA SOLUTIONS
Changes in Services:
Services changes are identified in the
Order.
le
are
Pricing Changes:
The Price of the contract is not altered
Order.
There are no Warranty changes with this Change Order.
Customer Responsibilities:
Customer Responsibility changes are identifled in
Change Order.
Payment Schedule Changes:
There are no Payment Schedule Changes with this Cha
5 Statement of Work provided with this
Unless amended above, all other terms and conditions of the Contract shall remain in full force. If there
are any inconsistencies between the provisions of this Change Order and the provisions of the Contract,
the provisions of the Change Order will prevail.
Reviewed by: Date: �` ��
M to la S G' ect M ager
Reviewed by: ^ Date: � /7 1 '`�
City of Fo o Project Manager
CHANGE ORDER
Statement of Work provided with this
updated Section 6 Project Schedule provided with
FOtt Worth DSR ProjeCt Page 2 of 2
SE'CTION 1
' • • ,
1l�I
1.1.1
SCOPE OF DESIGN
The pui•pose of this design is to add Dynamic System Resiliency to the City of Fort Worth System,
for City of Fort Worth users.
The Dynamic System Resilience (DSR) featul•e will automatically maintain critical radio system
communications in the event of a catastrophic failure of a master site. Using DSR assures that the
City of Forth Woi�th system will remain active, with no loss of features at your most critical time of
need, thus maintaining strategic communications throughout your organization and preserving the
safety of the members of your organization. During such a failure, DSR maintains full system
functionality including network management features and core component redundancy.
The City of Fort Worth system with this DSR offering would consist of two geographically separated
master control sites. These two sites would be: 1) The existing City of Foi�t Worth Master Site located
at Eagle Mountain; and 2) A City of Foi�t Wot�th DSR Master Site located at the Irving Criminal
Justice Center (CJC) building. This would allow all City of Foi�t Worth Radio Frequency (RF) and
remote dispatch sites to have communications capability to both master sites. The two master sites
communicate with each other, exchanging voice and cont�•ol h•affic, and health and management
information. Each site contains a redundant pair of zone controllers, their associated management
servers, and redundant paiis of networking equipment.
Shared DSR Equipment
The Foi�t Woi�th DSR Master Site at Irving CJC leverages cei�tain City of Irving Master Site
components including Core and CEN equipment. However, the sharing also occurs in Foi�t Wot•th
where the City of Iiving is leveraging the same components at the Fort Woi�th Eagle Mountain Master
Site. Shared equipment elements are listed below:
• The Gateway Routers
• The Core LAN Switches
• The User Configuration Server (UCS). In an Interzone System with two zones like Fort
Worth and Irving, both zones have UCS' that will be used. There is a UCS at the CFW Eagle
Mountain site and a UCS at the Irving CJC site. Only one UCS will be used at any given
time, but each will back up the other in the case of a failure. This is not automatic and would
requii•e user intei•vention to perform the switch.
• The GGSN
• The Customer Enterprise Netwol•k (CEN) Firewall, DMZ and PN Router
City of Fort Worth
Dynamic System Resiliency (DSR)
October 25, 2013
Use or disciosure of this proposal is subject
to the restrictions on the cover page.
Motorola Solutions Confidential Restricted System Decription 1-1
1.1.2
DSR Operation
In oi•der for an RF site, simulcast pi•ime site or dispatch site to take advantage of DSR opei•ation, the
site must be equipped with dual (redundant) site links. One site link would connect to the main Fort
Woi�th master site and the second site link would connect to the DSR master site.
ISSI Operation
Note that the City of Fort Worth's Inter-Subsystem Interface (ISSI) gateway will not be functional
when operating on the DSR master site. This is because the City of Fort Worth's ISSL 1 gateway does
not support DSR operation. The City's current ISSI.1 gateway will continue to operate normally as
long as the City is on the main master site at Eagle Mountain and operating off of either Zone
Controller (ZC 1 or ZC2). In the unlikely event the City would need to switch to the DSR master site,
using Zone Controllers at the Irving site (ZC3 or ZC4); the ISSI.1 gateway will not be functional
while operating on the DSR master site.
Should the City determine ISSI functionality is required when operating on the DSR mastei• site, the
ISSI.1 gateway can be upgraded to the ISSI 8000 gateway? The ISSI 8000 gateway suppoi�ts DSR
operation for system releases 7.13 or higher. Additionally, an ISSI 8000 gateway would also be
required at the DSR master site location. This proposal does not include an upgrade to the City's
current ISSL 1 gateway.
Dual Site Links
Fort Worth System users will require dual link equipment to share in the benefit of DSR It is not a
requir•ement to implement dual links on all sites to use DSR on a system. However sites not using
dual links will be in site trunking should the main Master Site fail as they are today.
Sites with single links will be activated as DSR capable but not equipped sites. This will
allow for rolling system controllers to the DSR Master Site during system upgrades and
updates. These sites will continue to operate not•mally under these conditions.
Sites with single links will not have access to DSR Master Site therefore:
— RF Sites will go into Site Trunking under conditions of a catastrophic failure of the main
Master Site.
— MCC 7500 Sites with Single Site links would be required to dispatch on the P25 system
via a secondary means such as control stations during conditions with a catastrophic
failure of the main Master Site.
— The P25 system in use today has some users with single site links, and MCC 7500 sites
with single links, an example of this would be Johnson County. These users need to
upgrade to dual site links to gain benefit fi•om DSR.
All non-Fort Woi�th users having dual links for their sites and dispatch locations must re-route
one of the two links to the DSR Mastei• Site to gain benefit of DSR operation.
These other system useis if they desired could direct both dual links from an RF or dispatch
site to the Foi�t Woi•th Master only. If this wei•e done however they would lose the DSR
functionality on these sites and dispatch centei•s.
Network Management
Soine City of Fort Worth features on the main Master Site will not function during the time the
system is switched to the DSR Master site. For instance, the DSR only has CEN back up links to the
downtown Data Center so this is the only site that will be able to do CEN functions when on the
DSR Master. Also there is no back up PN Server, and you will not get other functions down that
pipe if thei•e is no server associated with them in the DSR CEN. So, things like ATIA stream etc.
City of Fort Worth
Dynamic System Resiliency (DSR)
October 25, 2013
Use or disclosure of this proposal is subject
to the restrictions on the cover page.
Motorola Solutions Confidential Restricted System Decription 1-2
will not work so even though the data pipe is available the only DSR function that will function fi•om
the DSR would be the ICMF Server and KMF Client at the Data Center.
• The City of Foi�t Woi�th has a Network Management site and a MCC 7500 site at the Radio
Shop. These will function normally as long as the system is using the Eagle Mountain Master
Site. In the case of a catastrophic failure of the Eagle Mountain Mastei• the MCC 7500
Console and NM terminal at this site will cease to operate at this location.
• The Network Management terminals located at Eagle Mountain will cease to function in the
case of a catasti•ophic failure of the Eagle Mountain Master.
• Any Network Management terminal co-located with a dispatch center will operate normally.
— The Network Management terminal located at the Data Center is technically connected to
the dispatch routers at the Alternate PSAP location and therefore will opei•ate noi•mally,
once the Network Management Services however would not operate until these services
are activated through manual enhy to activate on the DSR Master.
— The Network Management terminals at all other locations in the City would cease to
operate.
CEN and Data operation
• Since all CEN connectivity is thi•ough the Master Site, all CEN activity such as OTAP—
Inform etc, will not be available through the system during times of catastrophic failure of
Eagle Mountain.
• OTAP will continue to work as long as 1) PN Server is alive; 2) As connectivity is still
available to the DSR site. However in the case of catastrophic failure of the main master site
only the KMF will work on the DSR Master — therefore OTAP will not work.
• OTAR is a KMF function and therefore will work with the DSR Master. Note the ICMF
server and one Client will be located at the City Data Center. Therefore the only access to
KMF (OTAR) functions in DSR conditions will be available through the KMF Client located
at the Data Center.
• The City of Fort Woi�th will supply Fii•ewall poi�ts on their Firewall located at the City of Fort
Worth Alternate PSAP/Data Center location. The CEN connection for the ICMF Server and
Client that comes fi•om the City of Irving CJC CEN will pass through this Firewall to provide
protection for the City of Foi�t Wot�th network.
• The CEN OTAP terminal could be used at the Data Center only if the conditions below were
satisfied
— This would require that the person using that terminal knew the radio IP to reprogram the
radio in the field—this is because the PN server is located at Eagle Mountain.
— OTAP at Data Center both client and server would continue to operate—may require some
manual keyboard intei•vention to do this.
— This would require a router for this functionality be placed at both Irving DSR site and at
Data Center and interconnected via either T1 or LAN connectivity. The new i•outer would
be plugged into the CEN switch at the datacenter so that site would have connectivity to
both Mastei• sites.
City of Fort Worth
Dynamic System Resiliency (DSR)
October 25, 2013
Use or disciosure of this proposai is subject
to the restrictions on the cover page.
Motorola Solutions Confidential Resfricted System Decription 1-3
Design Assumptions
1.2
1.2.1
The following design assumptions wei•e considei•ed when determining the equipment for this project:
• The City of Irving will establish their Master Site, in Irving and their DSR Mastei• Site at the
Fort Worth Eagle Mountain location before this equipment is installed.
• The City of Foi�t Woi�th and Ii•ving systems will be at the same system release and connected
with an inter-zone tink when DSR for the City of Foi�t Worth is purchased and implemented.
• Complete DSR functionality depends on Dual link sites.
• The City of Fort Worth 6-site two layer system, the two MCC 7500 dispatch locations and the
ASR site in Roanoke have dual links.
• The City of Foi�t Woi�th will be responsible for providing a single T I connectivity to the City
of Irving master site location fi•om each prime site, each ASR site and fi•om each MCC 7500
dispatch location.
• One of the two dual links will fi•om each prime site, MCC 7500 dispatch site, and the ASR
site will be disconnected fi•om the cur•rent master site and rerouted thi•ough T1 connectivity to
the Foi�t Worth DSR master site (in Irving).
• These sites will continue to operate normally should the system be forced to switch to the
DSR Master Site.
• The City of Fort Worth is in the process of implementing MCC 7500 equipment for all of its
dispatch. This project assumes that this process has been completed.
• Gold Elite sites remaining on the Fort Worth Zone will not have DSR capability. Gold Elite
Console connectivity is through an AEB located at Eagle Mountain and is not available
through DSR.
• This implementation will take place after the City of Fort Worth and its Customers have
migrated fi�om the Gold Elite dispatch console platform to the MCC 7500 dispatch console
platform. Motorola understands that Medstar may be a possible exception. In the event that
Medstar has not upgraded to MCC 7500 dispatch consoles then direct wireline console
connectivity will not be available for Medstar when the system is operating on the DSR
master site. In which case, Medstar would have to revert to control station dispatch or other
means when the DSR master site is activated.
DESIGN REQUIREMENTS
City of Fort Worth and its Customers
DSR implementation for the City of Fort Worth would require the rerouting of some of the T1 links
fi•om the Eagle Mountain master site to the City of Irving master site. These links will be connected to
the City of Fort Wol•th i•elay panel located thei•e. Essentially this means that all cui•rent dual links foi•
the City of Fort Worth System will be split in hal£ One half remaining at Eagle Mountain and the
other half going to the DSR master located in Irving.
city of Fort wortn
Dynamic System Resiliency (DSR)
October 25, 2013
Use or disclosure of this proposal is subject
to the restrictions on the cover page.
Motorola Solutions Confidential Restricted System Decription 1-4
��_
� I ���r
I � �,
�) I
�— — —
m���c�
�
�
�)
�)
�)
� (I
���)
— JI
m vw u�u srz
m cnr ou �u.mx �
pt an ar nv�Na)
Figure 1-1: Typical Dual Link Site Biock Diagram
The typical dual link site is shown in Figure 1-1. As configured today both links mai•ked "To CFW
Master Site" and "To CFW DSR Master Site (At City of Irving) go to the Master Site at Eagle
Mountain. As pat�t of the implementation of DSR, the redundant link will be sevei•ed fi•om the master
site at Eagle Mountain and redirected to the DSR master. This means that the current core routers and
their associated ports on the relay panels will need to be remapped to single links, requiring
reprogramming of the core routers at Eagle Mountain for the new operation. Motorola Solutions will
work with the City to carefully plan this reprogramming at Eagle Mountain during the
implementation process.
This move of links will require that the City of Fort Worth and its customers with dual links retask
the redundant Tls and change their final demarcation point fi•om the RF site, RF simulcast prime site,
or Dispatch location to the Irving location containing the DSR master.
Both links are logically tied to the active zone controller during noi7nal operation. The primaiy link
travels through the link directly connected to the active core and the backup link routes through the
inactive core network and through the interzone link back to the active core. Upon a primaiy link
failure, connectivity will be maintained through the backup link, though physically connected to the
inactive core, as it will be logically connected to the active core through the network.
For the City of Fort Worth sites this would mean that:
A redundant site link fi•om the Eagle Mountain Prime site woulcl have to redirected to
terminate at the DSR Master site. It would be the i•esponsibility of the City of Foi•t Wol•th to
i•econfigure theii• T1 plan foi• the microwave, and oi• provide a physical T1 to make the
connection fi•om Eagle Mountain Pi•itne site to the DSR site.
A redundant site link fi•om the Rolling Hills Prime site would have to redirected to terminate
at the DSR Master site. It would be the responsibility of the City of Foi•t Woi•th to reconiigure
their T1 plan for the microwave, and ol• pl•ovide a physical T1 to malce the connection fi•oln
Rolling Hills Prime site to the DSR site.
City of Fort Worth
Dynamic System Resiliency (DSR)
October 25, 2013
Use or disciosure of this proposal is subject
to the restrictions on the cover page.
Moforola Solutions Confidential Restricted System Decription 1-5
� ROLLING FiILLS PRIME SITE
� SIMULCAST SUBSYSTEM
• A redundant site link fi•om the ASR site at Roanoke would have to redirected to terminate at
the DSR Master site. It would be the responsibility of the City of Fort Worth to provide a
physical T1 to make the connection fi•om Roanoke site to the DSR site.
• Two redundant site links fi•om the Bolt Street Dispatch site would have to redirected to
terminate at the DSR Mastei• site. It would be the responsibility of the City of Fort Worth to
reconfigure their T 1 plan for the microwave, and or provide a physical T 1 s to make the
connection fi•om the Bolt Sn•eet Dispatch site to the DSR site.
• Two redundant site links fi•om the Alternate PSAP Dispatch site would have to redirected to
terminate at the DSR Master site. It would be the responsibility of the City of Fort Worth to
reconfigure their T 1 plan for the microwave, and or provide a physical T 1 s to make the
connection fi•om the Alternate PSAP Dispatch site to the DSR site.
• The console site at the Radio Shop and the Network Management terminals curi•ently
connected to the Eagle Mountain site would i•emain on their current links. These ar•e single
site links and will cease to function in the case of a catastrophic failure of the Eagle Mountain
site.
• The prime site at Eagle Mountain would no longer operate in the case of a catastrophic failure
at that site since it is co-located with the Master Site. However if just the Master Site at that
physical location is no longer available the Prime Site will be redirected to the redundant link
and continue to operate when the DSR master is in control of the system.
• In cases where there are dual links to a RF site or dispatch center and the main link is dit•ected
to the Eagle Mountain Main Master Site, and the redundant link is directed to the DSR
Master Site located at Irving CJC: Both links are logically tied to the active zone controller
during normal operation. The primary link travels through the link directly connected to the
active core and the backup link routes through the inactive core network and through the
interzone link back to the active core. Upon a primaty link failure, connectivity will be
maintained through the backup link, though physically connected to the inactive core, as it
will be logically connected to the active core through the network.
• Since the design does provide redundant CEN operation for the Data Center location, the City
of Foi�t Woi�th will be responsible for providing one T1 link between the Data Center and the
DSR Master Site.
• Other system users such as NETCO and Mansfield that have dual links to their console, and
RF sites would need to redirect the redundant T1 links to the DSR Master Site. The City of
Fort Worth will need to work with these agencies for the provision of the i•equired TI linlcs to
the DSR Master Site.
• All single link sites are only connected to the Master Site at Eagle Mountain, should a
catastrophic failure take place at the Eagle Mountain Mastei• Site theii• site links would be
severed and they would revert to site trunking for those RF sites, and would need to use
backup consolettes or other means for dispatch. At all dispatch, Prime Site, and RF site
locations where Tls have been redirected, the City of Fort Worth and its customers are
responsible for providing proper T 1 surge suppression at the entrance of the building.
• Fui•ther at the DSR location the physical T1 s redirected to this location require TI surge
suppression at the entrance of the building, and this surge suppression must be provided by
the City of Fort Woi�th and its customers.
• All Tls pi•ovided by the City of Fort Woi•th and its customers must meet the T1 link
specifications. These specifications are provided later in this document.
City of Fort Worth
Dynamic System Resiliency (DSR)
October 25, 2013
Use or disclosure of this proposal is subject
to the restrictions on the cover page.
Motorola Solutions Confidential Restricted System Decription 1-6
1.2.2
1.2.3
Motorola Solutions Requirements
Motoi•ola Solutions will be responsible for the installation of the additional hai•dware and softwai•e
i•equired at both the newly established DSR location, and softwai•e and configuration changes and
upgrades at the existing Eagle Mountain Master site.
• Motorola Solutions will test all links provided by the City of Fort Worth and its customers.
• Motorola Solutions will make the necessaiy cross-connects between the City of Foi�t Worth
and its customers routers and switches to the T1 s provided by the City and its customers at
the demarcation location at each site.
• Motorola Solutions will coordinate with the City of Fort Worth and its customeis to insure
that any downtime or system outage necessary due to reprogramming of the Master Site will
be kept at a minimum, and that back up procedures, and mitigations of risks are understood
by all customei•s and the system cutovers are planned.
■ It should be noted that during the cut-over process: The reconfiguration requires the "rolling
over" of the system controllei•s at Eagle Mountain. The system will complete a full switch within
a minute for a fully configured system. In smallet• systems, this time will be closer to 15 to 20
seconds. During this time, the RF sites will enter site ttvnking and data functionality will be
down. Field users will be able to communicate normally during this time in the site trunking
mode, and dispatch positions will need to use backup procedures for communicating with field
units.
■ Further the DSR implementation involves reloading the existing GAS servers with DSR flag
enabled. This can be done a server at a time but it will involve switching zone controllers as well.
So site trunking impact would occur during a ZC switch. Network Mangement impact (Zone
Watch etc) will be the time it takes to reload the servers over a period of 4-Shrs each. So network
management functions associated with each GAS server will be down for that 4-5 hr period the
server is being loaded. This system will continue operate normally.
■ Also the new network configuration files need to be deployed, and dual site links need to be
configured. This coniiguration upload may also cause a site to enter site trunking for less than a
minute.
■ Lastly the CEN functions will not be available during CEN router and switch reconfiguration.
• Motorola Solutions will provide modifications to any required system drawings for this
modification.
• Motorola Solutions in conjunction with the City of Foi�t Worth will develop a site by site
cutover plan and system upgrade plan for the City of Foi�t Worth Master Site.
• Motorola Solutions will provide interconnection fi•om the Star-line powei• system at the Irving
Master Site location to the OP820 power strips located in the cabinets.
• Motorola Solutions will be responsible for the racking and stacking of equipment and for the
provision of inner-cabinet cabling at the DSR prime site.
• Functional ATP in the field will provide demonstration the demonstration of DSR
functionality foi• acceptance purposes.
• Possible ATP tests on DSR will be reviewed and modified at the Customer Design Review
post contract to detei•mine which tests will be perfol•med since this modification is taking
place on a live system.
Power Requirements
The City of Foii Woi•th DSR will be located at the City of Irving Mastet• Site location. It is assumed
that the City of Ii•ving and the City of Fort Worth have come to agreement that the City of Irving will
supply the additional rack space and UPS power requirements for the City of Fort Worth DSR at that
City of Fort Worth
Dynamic System Resiliency (DSR)
October 25, 2013
Use or disclosure of this proposal is subject
to the restrictions on the cover page.
Motorola So/utions Confidential Restricted System Decription 1-7
location. Therefore this pi•oposal includes no additional equipment for Generatoi• oi• UPS backup at
the City of Ii•ving location and that the two cabinets requii•ed for the DSR for Fort Worth will have
dedicated floor space and environmental considerations at the City of Irving site.
Table 1-1 outlines the additional powel• i•equii•ements for the DSR Master foi• Fort Worth at the Irving
location.
Table 1-1: DSR Power Requirements
� � e . .
• •. �•
Core Backhaul Switches 2 1 2 41 82 142 284
CEN LAN Switch 1 1 1 41 41 142 142
Border Router 1 1 1 60 60 273 273
Packet Data Gateway 1 2 2 325 325 1110 1110
Core Router 6 1 2 60 120 273 546
Zone/System Server 3 2 8 650 2600 2218 8872
NAS 1 2 2 145 145 501 501
Virtual Server 2 2 2 325 325 1110 1110
NM Client 1 1 1 134 134 456 456
KVM W/Pull Out Monitor 1 2 2 72 72 246 246
SDM3000 1 1 1 20 20 68 68
City of Fort Worth
Dynamic System Resiliency (DSR)
October 25, 2013
Use or disclosure of this proposal is subject
to the restrictions on the cover page.
Motorola Solutions Confidential Restricfed System Decription 1-8
1.2.4 T1 Specifications and Requirements
City of Fort Worth and its customers Responsibilities
Provide minimum requirements for T1 site links. Requirements are listed in Table 1-2.
Table 1-2: Requirements
Bit Error Rate—BER 1 x 10 �
Stratum Level 2 or Better
Max. Delay 5 milliseconds (ms)
Availability 99.999 %
Line Coding B8ZS (bit 8 zero substitution)
Signaling Clear Channel
Compression None
Framing ESF (extended super frame)
Pulse Amplitude 0 dBdsx (3.OV +/- 0.3V or 6V P-P)
Dry or Wet Dry, No voltage (-48 VDC or other) Present
City of Fort Worth Responsibilities
The City of Fort Worth is responsible for providing the numbers of T1 links that meet Motorola site
link specifications as described in Table 1-2.
Table 1-2: Required T1 links to be provided by the City of Fort Worth
Motorola Solutions has assumed that the City of Fort Worth system customers will want to
have DSR backup if they have dual link site, and console links. The City of Fort Worth must
work with its customers to determine if this is the case. The following section assumes that
this is ti•ue, and that the site links discussed below is complete. Should additional systems be
added to the Fort Worth system befoi•e the implementation of this project revision of the
proposal, and the following information will be needed.
The City of Fort Worth Customer ai•e responsible for providing the nuinbers of T1 links that
meet Motoi•ola site link specifications as described in Table 1-3.
City of Fort Worth
Dynamic System Resiliency (DSR)
October 25, 2013
Use or disclosure of this proposal is subject
to the restrictions on the cover page.
Motorola Solutions Confidential Restricted System Decription 1-9
City of Fort Worth Customers Responsibilities
Table 1-3: Required T1 links to be provided by the City of Fort Worth Customers
-� '• •• e
Colleyville (NETCO PRIME) CFW DSR Master 1
Dispatch Location 1(NETCO) CFW DSR Master 1
Dispatch Location 2(NETCO) CFW DSR Master 1
Dispatch Location 3(NETCO) CFW DSR Master 1
Dispatch Location 4 CFW DSR Master 1
Alternate PSAP CFW DSR Master 1
Heritage RF Site (Mansfield) CFW DSR Master 1
Heritage Dispatch Site CFW DSR Master 1
(Mansfield)
Tarrant County SO Dispatch CFW DSR Master 1
Tarrant County College CFW DSR Master 1
Dispatch
North Richiand Hills Dispatch CFW DSR Master 1
Ft Worth "T" Dispatch CFW DSR Master 1
Tota I 12
City of Fort Worth and other customer non-redundant links
• As noted earlier the City of Fort Worth has one CEN location that will be backed up by a
redundant CEN link to the DSR Master. This is the Data Center Location. All other City of
Fort Worth links other than the ones mentioned in Table 1-2 will cease to function during a
catastrophic failure of the Eagle Mountain Master site.
• The City of Forest Hills is a single link dispatch system and this site will not be available
through DSR.
• The City of Mansfield CEN network has a single link to the Eagle Mountain site; it will cease
to function during catastrophic failure of the Eagle Mountain Master site.
• Although MedStar has dual links to their dispatch locations—currently their dispatch will be
done initially through Gold Elite connectivity, this connectivity does not connect to the DSR
and these consoles would have to revert to back-up consolette operation in the case of a
catastrophic failure of the Eagle Mountain site.
• All of the site links, and dispatch links in the Johnson county system are single site links, and
these sites would revert to site trunking and backup consolette dispatch during a catastrophic
failure ofthe Eagle Mountain Master Site.
The Customer Design Review and further discussions of scope will help determine the exact number
and type of T 1 s needed for this system. The bandwidth i•equired to the two dispatch centers has not
been calculated and will depend on the total number of talkgroups, amount of audio traffic to be
recorded by the MCE system, and system usage questions that will be resolved during the Design
Review. The above values are estimation. The site link for Aledo will be discussed with the City to
determine how it will be intei•connected. The City of Foi�t Woi�th is responsible foi• pi•ovision of T 1 s
and bandwidth necessary at these sites.
City of Fort Worth
Dynamic System Resiliency (DSR)
October 25, 2013
Use or disciosure of this proposal is subject
to the restrictions on the cover page.
Motorola Solutions Confidential Restricted System Decripfion 1-10
�� ��
Motoi•ola Solutions is pleased to present this Firm Fixed Proposal to the City of Fort Worth for DSR.
The design is based on assumptions. Any changes in these assurnptions and additional requirements
for DSR functionality would i•equire additional discussions.
City of Fort Worth
Dynamic System Resiliency (DSR)
October 25, 2013
Use or disclosure of this proposal is subject
to the restrictions on the cover page.
Moto�ola Solutions Confidential Resfricted System Decription 1-11
SECTION 2
The System drawings are included on the following pages.
City of Fort Worth
Dynamic System Resiliency (DSR)
October 25, 2013
Use or disclosure of this proposal is subject
to the restrictions on the cover page.
Motorola Solutions Confidential Restricted System Drawings 2-1
City of Fort Worih
Dynamic System Resiliency (DSR)
October 25, 2013
Use or disclosure of this proposal is subject
to the restnctions on the cover page.
� Molorola Solutions Confidential Restncted System Diawings 2-1
�n� �.�,:�n�� ; .�.,
�--------------------- ----.--- ---. — ,-----------------
co,� :c.""i ia�r.'�� �. ni.`±'ao �o"�, � ASTRO. l5_ \l1STP:l2...SITF
. i
�, .u,. �,E. x w e*i �n w� i
i
�i
i
i
------�
i
i
i
�w i
i
i
i
uuu� �uUul-�� '
_ t
i
i
i
i__--________�_�______�___��_�__�������_���________________________J
� �________________________________________�_--__�__--_-_-_-_-__--__1
h5TR0 25 BACKLIP 1fASTER SITE
i
'i � �I �iM
i m.d �. ,
i K�n a� os,
i ■ uvrz
_ i rma ze.� sr.wa __..'!.''.°�.
'urOo�u� wff'° t�t sw.w Y�
I
i :pM1r "'
� -- , T_ - � . ..::.._ " .. � ... ..
�U���� U����
i
i
i
�
i
i
Cily of Fort Worth October 25, 2013
Dynamic System Resiliency (DSR) Use or disclosure of this proposal is subject
to the restrictions on the cover page.
� Motorola Solutions Con�dential Restnc�ed System Drawings 2-2
SECTION 3
, " �
!� • ! - � •
1 SQM01SUM0201 DYNAMIC SYSTEM RESILIENCE A7.9
1 CA01511AA ADD: DSR VOICE
1 CA01512AA ADD: DSR DATA
1 CA01723AA ADD: BASELINE BACK UP
1 CA01414AD ADD: 7.11 ZC/NM HW 25-100 SITES
1 CA01720AA ADD: ANTI-VIRUS SERVICE SERVERS
99 CA01588AA ADD: ANTI-VIRUS SERVICE
1 CA01784AA ADD: STORAGE DEVICE
1 CA01771AA ADD: DUAL COMMON PLATFORM HARDWARE
1 CA01471AA ADD: WINDOWS SUPPLEMENTAL TRANS CON
1 DLN6692 HP LASERJET PRINTER CP3525DN 110V
1 TT2565 NM Z420 HIGH TIER WIN7-IE9 64BIT
1 T7702 ASTRO 7.11 CLIENT APPLICATION SOFTW
1 DDN8325 17" LCD DRAWER W/ KEYBOARD & MOUSE,
6 DQKVMCABLE15FT 15 FT KVM CABLE - 26-15-51213
1 DDN9748 19 INCH BLACK SHELF
1 TT04523AA RAS ACE SERVER
5 DDN8653 RSA 5 YEAR HARD TOKEN SOLD ONLY IN
1 T7449 WINDOWS SUPPLEMENTAL TRANS CONFIG
1 CLN1856 2610-24 ETHERNET SWITCH
1 ST6000 S6000 MNR MULTI-PROTOCOL ROUTER
1 ST6017B S6000 4 PORT ULTRAWAN II MODULE
1 ST6000 S6000 MNR MULTI-PROTOCOL ROUTER
1 ST6017B S6000 4 PORT ULTRAWAN II MODULE
1 SQM01SUM0197 PACKET DATA GATEWAY RACKMOUNT SERV
1 CA01494AA ADD: PDG DSR SOFTWARE IV&D
3 ST6202 SRC 24 PORT T1/E1 EXP II
2 DQTG1153242 84" 600 X 900 FULLY ADJUSTABLE EIA-
4 DSOP820B PDU, 120V HARDWIRE 8 20A OUT�ET P
4 DS1101378 RACK MT ADAPTER PLATE, 19 IN FOR DS
1 DSCPX1101986 SPD, RJ-45 CONNECTED 16 LINE T1/E
1 SQM01SUM0211 MOSCAD NFM VIRTUALAPPLIANCE
1 F4528 GMC PER DEVICE SW LICENSES
1 VA00363 GMC SW LIC PER GMC IN DSR ZONE
City of Fort Worth
Dynamic System Resiliency (DSR)
October 25, 2013
Use or disclosure of this proposal is subject
to the restrictions on the cover page.
Motorola Solutions Confidential Restricted Equipment List 3-1
City of Fort Worth
Dynamic System Resiliency (DSR)
October 25, 2013
Use or disclosure of this proposal is subject
to the restrictions on the cover page.
Motorola Solutions Confidential Restricied Equipment List 3-2
SE�TION 4
ACCEPTANCE TEST PLAN
Dynamic System Resilience
Automatic Registration Server (Presence
Notifier) Registration
1. DESCRIPTION
This test shows that in the event of a Primary Core
Packet Data Gateway failure, the (ARS) will continue
to operate using the backup mechanism available
with Dynamic System Resilience (DSR) to reach its
Presence clients.
Note: This test applies to IV&D only.
SETUP
RADIO-1 - TALKGROUP 1
RADIO-1 - SITE - SITE 1
Packet Data Gateway 1: Active
Packet Data Gateway 2: Standby
2. TEST
Step 1. Register with Automatic Registration Server
(ARS).
Step 2. Disconnect the Ethernet links of the Packet
Data Router and Radio Network Gateway in
the Primary Core.
Step 3. Observe that both the Unified Event
Managers lost communication with Packet
Data Gateway 1.
Step 4. Observe, in both the Unified Event
Managers, that Packet Data Gateway 2's
Redundancy state becomes `Active'.
Step 5. Observe, in both the Unified Event
Managers, the Link Status of the Packet
Data Gateway's common managed links
transition through various states to `Up'.
Step 6. Observe that RADIO-1 automatically context
activates.
Step 7. Verify that RADIO-1 re-registers with the
ARS.
VERSION #1.010
Pass Fail
City of Fort Worth
Dynamic System Resiliency (DSR)
QMotorola Solutions Confidential Restricted
October 25, 2013
Use or disclosure of this proposal is subject
to the restrictions on the cover page.
Acceptance Test Plan 4-1
D'ynamic System Resilience
Dual T1/E1 Link Console Site Router Failure
1. DESCRIPTION
This test will demonstrate that in the event of a
failure of the Console Site Router which has a
physical T1/E1 link to the Primary Core, in a dual
site router configuration, the other Console Site
Router takes over by routing packets through the
Backup Core to the Primary Core. The Site Control
Paths are unaffected by the failure.
SETUP
RADIO-1 - TALKGROUP 1
CONSOLE-1 - CONSITE-1 - TALKGROUP 1
CONSOLE-2 — CONSITE-1 - TALKGROUP 1
Zone Controller 1: Active
Zone Controller 2: Standby
Zone Controller 3 : Standby
Zone Controller 4 : Standby
VERSION #1.020
2. TEST
Step 1. Initiate a Talkgroup call from CONSOLE-1
Verify the call is received by CONSOLE-2
and RADIO-1.
Step 2
Step 3
Pull the power cord to Console Site Router
1.
Observe, in both Unified Event Managers,
that Console Site Router 1 has failed.
Step 4. Verify, via the Unified Event Manager (e.g.
in the Primary Core), that Zone Controllers 1
and 2, and the Consoles in the site are
unaffected by the Console Site Router
outage.
Step 5. Initiate a Talkgroup call from CONSOLE-1
on TALKGROUP 1. Verify the call is
received by CONSOLE-2 and RADIO-1.
Step 6
Step 7
Plug the power cord back in to Console Site
Router 1.
Verify Console Site Router 1 returns to
service in both Unified Event Managers.
Pass Fail
City of Fort Worth
Dynamic System Resiliency (DSR)
October 25, 2013
Use or disclosure of this proposal is subject
to the restrictions on the cover page.
QMotorola Solutions Confidential Restricted Acceptance Test Plan 4-2
Dynamic System Resilience
Dual T1/E1 Link RF Site Router Failure
1. DESCRIPTION
This test will demonstrate that in the event of a
failure of the RF Site Router which has a physical
T1/E1 link to the Primary Core, in a dual site router
configuration, the other RF Site Router takes over by
routing packets through the Backup Core to the
Primary Core. The Site Control Paths are unaffected
by the failure.
SETUP
RADIO-1 - TALKGROUP 1
RADIO-1 - SITE - SITE 1
RADIO-2 - TALKGROUP 1
RADIO-2 - SITE — SITE 2
Zone Controller 1: Active
Zone Controller 2: Standby
Zone Controller 3 : Standby
Zone Controller 4 : Standby
VERSION #1.030
City of Fort Worth
Dynamic System Resiliency (DSR)
Q Motorola Solutions Confidential Restricted
2. TEST
Step 1. Initiate a Talkgroup call from RADIO-1.
Verify RADIO-2 receives the call.
Step 2. Pull the power cord to RF Site Router 1.
Step 3. Observe, in both Unified Event Managers,
that RF Site Router 1 has failed.
Step 4. Verify, via the Unified Event Manager (e.g.
in the Primary Core), that Zone Controllers 1
and 2, Packet Data Gateway1 and the RF
sites are unaffected by the RF site router
outage.
Step 5. Initiate a Talkgroup call from RADIO-1.
Verify RADIO-2 receives the call.
Step 6. Plug the power cord in to RF Site Router 1.
Step 7. Verify in both Unified Event Managers, that
RF Site Router 1 returns to service.
Pass Fail
October 25, 2013
Use or disclosure of this proposal is subject
to the restrictions on the cover page.
Acceptance Test Plan 4-3
Dynamic System Resilience
Manual Synchronization of User
Configuration Manager/Unified Network
Configurator
1. DESCRIPTION
This test demonstrates that the standby User
Configuration Manager and the standby Unified
Network Configurator can be manually synchronized
to their active counterparts, for upgrade scenarios.
SETUP
User Configuration Manager 1: Active
User Configuration Manager 2: Standby
Unified Network Configurator 1: Active
Unified Network Configurator 2: Standby
Default automatic synchronization interval is 24
hours
VERSION #1.010
City of Fort Worth
Dynamic System Resiliency (DSR)
2. TEST
Step 1. Before the automatic synchronization is due
to occur, perform a manual synchronization.
Step 2. Verify from the administration menu of both
the Unified Network Configurator and User
Configuration Manager that the manual
synchronization was successful.
Step 3. Before the automatic synchronization is due
to occur, perForm manual switchover of the
User Configuration Manager and Unified
Network Configurator to make both User
Configuration Manager 2 and Unified
Network Configurator 2 go active.
Step 4. Perform manual switchover of the User
Configuration Manager and Unified Network
Configurator to make both User
Configuration Manager 1 and Unified
Network Configurator 1 go active.
October 25, 2013
Use or disclosure of this proposal is subject
to the restrictions on the cover page.
QMotorola Solutions Confidential Restricted Acceptance Test Plan 4-4
Dynamic System Resilience
MOSCAD Failure
1. DESCRIPTION
In a system with DSR, MOSCAD components in a
master site primary core are duplicated in the
backup core. This includes the SDM3000 Network
Translator (SNT) server and the Graphical Master
Computer (GMC) server.
This test demonstrates that when a MOSCAD device
in the Primary Core fails, an alarm is reported to
both the Primary Core and Backup Core Unified
Event Managers.
SETUP
No prior setup is required.
VERSION #1.010
2. TEST
Step 1. Disconnect MOSCAD RTU 1's link from the
network.
Step 2. Verify, on both Unified Event Managers, that
MOSCAD RTU 1 has lost communication
with the Unified Event Manager.
Step 3. Verify, on MOSCAD GMC #1, that the
MOSCAD RTU #1 has lost communication
with the GMC
Step 4. Connect MOSCAD RTU 1's link to the
network.
Step 5. Verify, on both Unified Event Managers, that
MOSCAD RTU 1 has returned to service.
Step 6. Verify, on both the MOSCAD GMCs, that the
MOSCAD RTU now has communication with
the GMC
Pass Fail
City of Fort Worth
Dynamic System Resiliency (DSR)
QMotorola Solufions Confidential Restricted
October 25, 2013
Use or disclosure of this proposal is subject
to the restrictions on the cover page.
Acceptance Test Plan 4-5
Dynamic System Resilience
OTAR Registration on Packet Data Gateway
Failure
1. DESCRIPTION
In a system with DSR, each zone has two Packet
Data Gateways (PDG) for each Integrated Voice &
Data (IV&D) and/or High Performance Data (HPD)
data service; one PDG in the primary core, and one
PDG in the backup core. The PDGs securely
communicate to automatically select one active
PDG. The selection algorithm is weighted to give
preference to the PDG serving the most number of
sites or the PDG in the primary core if the number of
serving sites is equal. The standby PDG does not
synchronize any context databases with the active
PDG.
This test will show that in the event of a Primary
Core Packet Data Gateway failure, the Key
Management Facility will continue to operate using
the backup mechanism available with Dynamic
System Resilience (DSR) to reach its Over the Air
Rekeying (OTAR) clients.
Note: This test applies to IV&D only.
SETUP
RADIO-1 - TALKGROUP 1
RADIO-1 - SITE - SITE 1
Packet Data Gateway 1: Active
Packet Data Gateway 2: Standby
VERSION #1.010
City of Fort Worth
Dynamic System Resiliency (DSR)
2. TEST
Step 1. Register RADIO-1 with the Key
Management Facility.
Step 2. Disconnect the Ethernet links for the Packet
Data Router and Radio Network Gateway in
the Primary Core.
Step 3. Verify in the Primary Core Unified Event
Manager and Backup Core Unified Event
Manager an event is received for Comm
Loss for Packet Data Gateway 1.
Step 4. Verify Packet Data Gateway 2's
Redundancy state is 'Active' using the
Unified Network Configurator (UNC) "Quick
Commands" or the Unified Event Manager
in the Primary and Backup Core.
Step 5. Observe, in both Unified Event Managers,
the Link Status of the Packet Data
Gateway's managed links transition through
various states to `Up'.
Step 6.
Step 7
After a short period, verify that the radio
automatically context activates.
Verify that RADIO-1 re-registers with the
Key Management Facility.
Pass Fail
October 25, 2013
Use or disclosure of this proposal is subject
to the restrictions on the cover page.
QMotorola Solutions Confidential Restricted Acceptance Test Plan 4-6
Djrnamic System Resilience
Primary Core Customer Network Interface
Failure - Over the Ethernet Keying (OTEK)
Clients
1. DESCRIPTION
In a system with DSR, each Customer Enterprise
Network (CEN), which requires full data redundancy,
has two CNI connections to the system. These
connections must be made to a master site pair.
This test will show that when the communication
path between the Customer Enterprise Network and
the Primary Core fails, e.g. Border Router 1, the Key
Management Facility will continue to operate using
the standby path available with Dynamic System
Resilience (DSR) to reach its OTEK clients.
Note: The OTEK client has to re-establish the
communication path with the Key Management
Facility.
SETUP
CONSOLE-1 with OTEK
CONSOLE-1 - SITE - CONSOLE SITE 1
VERSION #1.050
2. TEST
Step 1. From the KMF Client verify that the
CONSOLE-1 has registered. Perform a full
update on CONSOLE-1. Verify that the Full
Update is successful.
Step 2. Pull the power cord to Border Router 1
Step 3. Observe, in both the Unified Event
Managers, the GGSN reports that the
GGSN connection to the Customer
Enterprise Network is down.
Step 4. Verify that the Key Management Facility can
no longer reach CONSOLE-1, by attempting
to send a clear `Hello'.
Step 5
Step 6
Re-start CONSOLE-1.
Observe that CONSOLE-1 registers with the
Key Management Facility.
Step 7. Verify that the Key Management Facility can
now reach CONSOLE-1, by sending a clear
'Hello'. Perform a full update on the
CONSOLE-1. Verify that the Full Update is
successful.
Step 8. Plug the power cord in to Border Router 1.
Pass Fail
City of Fort Worth
Dynamic System Resiliency (DSR)
October 25, 2013
Use or disclosure of this proposal is subject
to the restrictions on the cover page.
QMotorola Solutions Confidential Restricted Accepfance Tesf Plan 4-7
Dynamic System Resilience
User Configuration Manager and Unified
Network Configurator Switchover
1. DESCRIPTION
Configuration management is performed through the
User Configuration Manager (UCM) and Unified
Network Configurator (UNC) applications. In the City
of Fort Worth System, since it is tied to the City of
Irving core through SmartZone, and the DSR core is
co-located with the Irving Master site, both UCSs will
be used. There is UCS at Eagle Moutain and there
is UCS at Irving CJC. Only one UCS will be used at
any given time, but each will back up the other in the
case of a Master Site failure. This is not automatic
and would require user intervention to perform the
switch. This test will show that in the event of a
failure of the User Configuration Manager or the
Unified Network Configurator in the Primary Core,
the Backup Core counterparts can take over in order
to continue providing configuration services. This
switchover requires the user to de-activate the
Unified Network Configurator and User
Configuration Manager, and activate both the User
Configuration Manager and Unified Network
Configurator in the Backup Core.
SETUP
User Configuration Manager 1: Active
User Configuration Manager 2: Standby
Unified Network Configurator 1: Active
Unified Network Configurator 2: Standby
VERSION #1.050
2. TEST
Step 1. Log into the primary and secondary User
Configuration Server's Administration Menu.
Verify from the Administration Menu that the
primary server is "Enabled" and the backup is
"Disabled".
Step 2. Log into the primary and secondary Unified
Network Configurator's Administration Menu.
Verify from the Administration Menu that the
primary server is "Enabled" and the backup is
"Disabled".
Step 3. On the primary User Configuration Server's
Administration Menu select the option to disable
the application. Verify that the server disables
from the menu.
Step 4. On the primary Unified Network Configurator
Administration Menu, select the option to disable
the application. Verify that the server disables
from the menu.
Step 5. Verify that the current Unified Network
Configurator and User Configuration
Management applications are no longer available
on a Network Management client.
Step 6. On the secondary (DSR) User Configuration
Server's Administration Menu select the option to
enable the application. Verify that the server
enables from the menu.
Step 7. On the secondary (DSR) Unified Network
Configurator Administration Menu, select the
option to enable the application. Verify that the
server enables from the menu.
Step 8. Verify from a Network Management client that the
Unified Network Configurator and User
Configuration Management applications are now
available, running on the backup servers. (The
Motorola application may need to be restarted.)
Step 9. Return the system to normal operation.
Pass Fail
City of Fort Worth
Dynamic System Resiliency (DSR)
October 25, 2013
Use or disclosure of this proposal is subject
to the restrictions on the cover page.
QMotorola Solufions Confidential Restricted Acceptance Test Plan 4-8
D'ynamic System Resilience
Zone Controller 1 and 2 Failure (Intra-zone
wide area trunking)
1. DESCRIPTION
The purpose of this test is to show that, in the event
of the Primary Core Zone Controllers failing, a
Backup Core Zone Controller will take over in order
to return the zone back to wide area trunking.
The Zone Controller 1 failure, Zone Controller 2
failure, Zone Controller 3 becoming active and
resetting of Site Control Paths and InterZone Control
Paths are all reported in BOTH the Unified Event
Managers.
SETUP
RADIO-1 - TALKGROUP 1
RADIO-1 - SITE - SITE 1
RADIO-2 - TALKGROUP 1
RADIO-2 - SITE — SITE 2
Zone Controller 1: Active
Zone Controller 2: Standby
Zone Controller 3: Standby
Zone Controller 4: Standby
VERSION #1.050
City of Fort Worth
Dynamic System Resiliency (DSR)
2. TEST
Step 1. Initiate a Talkgroup call from RADIO-1.
Verify that RADIO-2 receives the audio.
Step 2. In the Unified Network Configurator, select
Zone Controllers 1 through 4 and check the
redundancy state using the Quick Command
feature.
Step 3. Verify that Zone Controller 1 is Active.
Step 4. Reset the Application state of both Zone
Controller 1 and Zone Controller 2 in Zone
1, via Zone 1's Primary Core Unified Event
Manager.
Step 5. In the Unified Network Configurator, select
Zone Controllers 1 through 4 and check the
redundancy state using the Quick Command
feature.
Step 6. Verify that Zone Controller 3 is Active.
Step 7. Initiate a Talkgroup call from Radio-1. Verify
that RADIO-2 receives the audio.
Pass Fail
October 25, 2013
Use or disclosure of this proposal is subject
to the restrictions on the cover page.
QMotorola Solutions Confidenfial Restricted Acceptance Test Plan 4-9
Signoff Certificate
By their signatures below, the following witnesses certify they have observed the system Acceptance Test
Procedures.
Signatures
WITNESS:
Please Print Name:
Piease Print Title: C a�uN � c5,"�"►i.vs �,N�►c �
�-�'��y
Initials: �
WITNESS: �'����^�Qo Date:
Please Print Name: �JD/1 Yl C, •�1.�Y1��''�% Initials:
Please Print Title: � v�Ot�DI"G/Qt �% �l\�c.� �' Y tQ �� � e%�
WI7NESS:
Please Print Name:
Please Print Title:
City of Fort Worth
Dynamic System Resiliency (DSR)
Initials:
October 25, 2013
Use or disclosure of this proposal is subject
to the restr(ctions on the cover page.
Q Motorola Solutions Confidential Restricted Acceptance Test Plan 4-10
SEi;TION 5
�i
�+r�•
ovERviEw
This Statement of Work (SOW) describes the deliverables to be furnished to the City of Fort Worth.
The tasks described herein will be performed by Motorola, its subcontractors, and the City of Fort
Worth to implement the solution described in the System Description. It describes the actual work
involved in installation, identifies the installation standards to be followed, and clarifies the
responsibilities for both Motorola and City of Foi�t Woi-�h during the project implementation.
Specifically, this SOW provides:
• A summary of the phases and tasks to be completed within the project lifecycle.
• A list of the deliverables associated with the project.
• A description of the responsibilities for both Motorola and City of Fot�t Worth.
• The qualifications and assumptions taken into consideration dui•ing the development of this
proj ect.
This SOW provides the most current understanding of the work required by both parties to ensure a
successful project implementation. In pat�ticular, Motorola has made assumptions of the sites to be
used for the new system. Should any of the sites change, a revision to the SOW and associated pricing
will be required. It is understood that this SOW is a working document, and that it will be revised as
needed to incorporate any changes associated with contract negotiations, Contract Design Review
(CDR), and any other Change Orders that may occur during the execution of the project.
The scope of this project is to to add Dynamic System Resiliency (DSR) to the City of Fort Worth
System. This includes installing backup Master Site equipment on for the City of Fort Woi�th at the
City of Irving Criminal Justice Center (CJC). The equipment will include the zone cont�•oller, system
and zone level database servers, network monitoring equipment and MOSCAD equipment. This
equipment will be connected to the common zone core networking equipment currently installed at
the Irving CJC site. Once implemented, The City of Fort Woi�th system would consist of two
geographically separated Master sites, one at Eagle Mountain and the other at the Irving Master site at
CJC.
► � �
Motorola has based the system design on information provided by the City of Fort Worth and an
analysis of their system requirements. All assumptions have been listed below for review. Should
Motorola's assumptions be deemed incorrect or not agreeable to the City of Fort Wot�th, a revised
pi•oposal with the necessaly changes and adjusted costs may be i•equired. Changes to the equipment or
scope of the project after contract may require a Change Order.
City of Fort Worth
Dynamic System Resiliency (DSR)
October 25, 2013
Use or disclosure of this proposal is subject
to the restrictions on the cover page.
Motorola Solutions Confidential Restricted Statement Of Work 5-1
• It is assumed that the City of Irving will have established theii• DSR Mastei• site at the Fort Worth
Eagle Mountain site.
• Both the City of Fort Worth and the City of Iiving RF systeins will be at the same System
Release, SR7.11 when the City of Fot•t Worth DSR Master is implemented.
• City of Fort Worth will supply the dual site links required for the DSR functionality.
— The City of Fort Woi�th will be i•esponsible for providing single T1 connectivity to the City of
Irving Master site location fi•om each prime site, each ASR site and fi•om each MCC 7500
dispatch location.
5.3
5.3.1
5.3.2
— One of the two T1 links fi•om each prime site, MCC 7500 dispatch site, and the ASR site will
be disconnected from the current Master and rerouted through T1 connectivity to the Fort
Worth DSR Master (in Irving).
— These sites will continue to opei•ate normally should the system be forced to switch to the
DSR Master Site.
• This proposal assumes the implementation of the Fort Worth MCC7500 equipment will be
completed prior to the implementation of the DSR Master.
• Any Gold Elite dispatch sites on the Fort Wot�h system will not have the DSR capability.
• Any RF site the does not utilize dual links will go into site trunking under the condition of the
Master site failure.
• Any Dispatch site that does not utilize dual links will have to dispatch with secondary means,
such as control stations, under the condition of the Master site failure.
• All non-Fort Worth users on the system with dual links to the Fort Worth Master will require one
of the two links to be re-routed to the DSR Master to benefit from the DSR operation. Any re-
routed T 1 s must be sut•ge protected at both ends.
• This design is based on the City of Irving supplying the required rack space and UPS power foi•
the Fort Worth DSR Master site equipment to be located at the CJC.
• There is no Site Development work quoted as part of this proposal. If required for any of the
designated sites, all site development is the responsibility of the City of Fort Worth.
• All work is to be performed during normal work hours, Monday through Friday 8:00 a.m. to 5:00
p.m.
� ,�
Cont�act Award (Milestone)
• The City of Foi�t Woi�th and Motorola execute the contract and both parties receive all the
necessaiy documentation.
Contract Administration
Motorola Responsibilities:
• Assign a Project Manager, as the single point of contact with authority to make project decisions.
• Assign resources necessary for project implementation.
• Set up the project in the Motorola info�•mation system.
• Schedule the project kickoff ineeting with the City of Fort Worth.
City of Fort Worth
Dynamic System Resiliency (DSR)
October 25, 2013
Use or disclosure of this proposal is subject
to the restrictions on the cover page.
Motorola Solutions Confidential Restricted Statement Of Work 5-2
City of Fort Worth Responsibilities:
• Assign a Pi•oject Manager, as the single point of contact responsible for City of Fort Worth-signed
approvals.
• Assign other resources necessaiy to ensui•e completion of project tasks for which the City of Fort
Worth is i•esponsible.
5.3.3
��:;
�"��il
Completion Criteria:
• Motorola internal processes are set up for project management.
• Both Motorola and the City of Fort Worth assign all required resources.
• Project kickoff ineeting is scheduled.
Project Kickoff
Motorola Responsibilities:
• Conduct a project kickoff ineeting.
• Ensui•e key project team participants attend the meeting.
• Introduce all project participants attending the meeting.
• Review the i•oles of the project pal�ticipants to identify communication flows and decision-making
authority between project pat�ticipants.
• Review the overall project scope and objectives with the City of Fot�t Worth.
• Review the resource and scheduling requirements with the City of Fort Worth.
• Review the Project Schedule with the City of Fort Wot•th to address upcoming milestones and/or
events.
• Review the teams' interactions Motorola and the City of Fort Worth, meetings, reports, milestone
acceptance, and the City of Foi�t Worth's participation in pa��ticular phases.
City of Fort Worth Responsibilities:
• The City of Foi�t Wot�th's key project team pai�ticipants attend the meeting.
• The City of Fort Worth facilitate coordination between Fort Woi�th and the City of Irving where
needed.
• Review Motorola and City of Fort Woi•th responsibilities.
Completion Criteria:
• Project kickoff ineeting completed.
• Meeting notes identify the neYt action items.
, � � , �
Review Contract Design
Motorola Responsibilities:
• Meet with the City of Fort Worth project team.
• Review the operational requirements and the impact of those requirements on various equipment
configurations.
• Establish a defined baseline for the system design and identify any special product requirements
and their impact on system implementation.
City of Fort Worth
Dynamic System Resiliency (DSR)
October 25, 2013
Use or disclosure of this proposal is subject
to the restrictions on the cover page.
Motorola Solutions Confidential Restricted Statement Of Work �3
• Review the System Design, Statement of Work, Project Schedule, and Acceptance Test Plans,
and update the conti•act documents accordingly.
• Discuss the proposed Cutover Plan and methods to document a detailed procedure.
• Submit design documents to the City of Fort Woi�th for approval. These documents form the basis
of the system, which Motorola will manufacture, assemble, stage, and install.
• Pi•epare ec�uipment layout plans for staging.
• Provide minimum acceptable pei•formance specifications for microwave, fibei•, oi• copper links.
• Establish demarcation point (supplied by the Motorola system engineer) to define the connection
point between the Motorola-supplied equipment and the City of Foi�t Worth-supplied link(s) and
external interfaces.
• Finalize any site evaluations to capture site details of the system design and to determine site
readiness if necessary.
— Determine each site's ability to accommodate proposed equipment based upon physical
capacity.
— If applicable, test existing equipment with which Motorola equipment will interface.
Restrictions:
• Motorola assumes no liability or responsibility for inadequate fi•equency availability or fi•equency
licensing issues.
• Motorola is not responsible for issues outside of its immediate conh•ol. Such issues include, but
are not restricted to, improper fi•equency coordination by others and non-compliant operation of
other radios.
• Motorola is not responsible for co-channel interference due to errors in fi•equency coordination by
APCO or any other unlisted fi�equencies, or the improper design, installation, or operation of
systems installed or operated by others
• If, for any reason, any of the proposed sites cannot be utilized due to reasons beyond Motorola's
control, the costs associated with site changes oi• delays including, but not limited to, re-
engineering, fi•equency re-licensing, site zoning, site permitting, schedule delays, site
abnot•malities, re-mobilization, etc., will be paid for by the City of Fort Woi�th and documented
through the Change Order process.
City of Fort Worth Responsibilities:
The City of Foi�t Woi�th's key project team participants attend the meeting.
Make timely decisions, according to the Project Schedule.
Frequency Licensing and Interference:
— As mandated by FCC, the City of Foi�t Worth, as the licensee, has the ultimate responsibility
for providing all required radio licensing or licensing modifications for the system prior to
system staging. This i•esponsibility includes paying for FCC licensing and fi•equency
coordination fees (if required).
Completion Criteria:
• Complete Design Documentation, which may include updated System Description, Equipment
List, system drawings, or other documents applicable to the project.
• Incorpoi•ate any deviations fi•om the pi•oposed system into the contract documents accordingly.
• The system design is "fi•ozen" in preparation for subsequent project phases such as Order
Processing and Manufacturing.
e A Change Order is executed in accordance with all material changes resulting from the Design
Review to the conti•act.
City of Fort Worth
Dynamic System Resiliency (DSR)
October 25, 2013
Use or disclosure of this proposal is subject
to the restrictions on the cover page.
Motorola Solutions Confidential Restricted Statement Of Work 5-4
5.4.2
�
5.5.1
��'J
5.6.1
Design Approvai (Milestone)
• The City of Fort Worth executes a Design Approval milestone document.
���' � ���
Process Equipment List
Motorola Responsibilities:
• Validate Equipment List by checking for valid model numbers, versions, compatible options to
main equipment, and delivery data.
• Enter order into Motorola's Customer Order Fulfillment (COF) system.
• Create Ship Views, to confirm with the City of Foi�t Worth the secure storage location(s) to which
the equipment will ship, if the designated site(s) are not ready for receipt of the proposed
equipment. Ship Views are the mailing labels that carry coinplete equipment shipping
information, which direct the timing, method of shipment, and ship path for ultimate destination
receipt.
• Create equipment orders.
• Reconcile the equipment list(s) to the Contract.
• Procure third-party equipment if applicable.
City of Fort Worth Responsibilities:
• Approve shipping location(s).
Completion Criteria:
• Verify that the Equipment List contains the correct model numbeis, veision, options, and delivery
data.
• Trial validation completed.
• Bridge the equipment order to the manufacturing facility.
� � • ► � �
Manufacture Motorola Fixed Network Equipment
Motorola Responsibilities:
• Manufacture the Fixed Network Equipment (FNE) necessai•y for the system based on equipment
order.
City of Fort Worth Responsibilities:
• None.
Completion Criteria:
• FNE shipped to eithel• the field or the staging facility.
City of Fort Worth
Dynamic System Resiliency (DSR)
October 25, 2013
Use or disclosure of this proposal is subject
to the restrictions on the cover page.
Motorola Solutions Confidential Restricted Statement Of Work 5-5
5.6.2
�J
!��[ ;
5.8.1
Manufacture Non-Motorola Equipment
Motorola Responsibilities:
• Pi•ocure non-Motor•ola equipment necessary foi• the system based on equipment ordei•.
City of Fort Worth Responsibilities:
• None.
Completion Criteria:
• Ship non-Motorola manufactured equipment to the field and/or the staging facility.
CIVIL WORK FOR THE CITY OF FORT WORTH/IRVING
PROVIDED FACILITIES
Motorola Responsibilities:
• Provide electrical requirements for each equipment rack to be installed in the City of Fo��t Worth-
provided and Irving facilities.
• Provide heat load for each equipment rack to be installed in the City of Fort Woi�th-provided
facilities.
• Install4 OP820s (2 per cabinet) in the two cabinets at the Irving CJC site.
• Supply and install 4 circuit modules with 20 AMP breakers (panel with 32 circuits) into the City
of Irving Star-line electrical system in slots above the two cabinets.
• Install 10-T1 CAT SE oi• better T1 jumper cables fi•om the Switching and Routing center (SRC)
interface panels to the City of Fort Worth provided T1 interface demark point.
City of Fort Worth Responsibilities:
• Complete any agreements necessaiy with the City of Irving to allow installation of the Fort Worth
equipment, use of City of Irving equipment required to complete DSR, and use of Irving
facilities, including power backup systems.
Completion Criteria:
• All sites are ready for equipment installations in compliance with Motorola's R56 standards.
� 1 / ,
Install Fixed Network Equipment
Motorola Responsibilities:
Motorola will be responsible for the instailation of all the proposed fixed equipment
contained in the Equipment List and outiined in the System Description based upon the
agreed to floor plans, at the sites where the physical facility improvement is complete and
the site is ready for installation. All equipment will be propel•ly secti�red to the floos• and
installed in a neat and pl•ofessional manner, employing a standard of workmanship
consistent with its own R-56 instaliation standards and in compliance with applicable
Naiional Electrical Code (NEC), EIA, Federal Aviation Administration (FAA), and FCC
standards and regulations. Motorola will furnish all cables for power, control, and radio
transmission to connect the Motorola supplied equipment to the power panels or
City of Fort Worth
Dynamic System Resiliency (DSR)
October 25, 2013
Use or disclosure of this proposal is subject
to the restrictions on the cover page.
Motorola Solutions Confidential Restricted Statement Of Work 5-6
receptacles and the audio/conti•ol line connection point.
5.8.2
5.8.3
�
5.9.1
• Install 1 Firewall provided by the City of Fort Worth in one of the two above cabinets and supply
and install LAN cable for this firewall to Networking equipment.
• At City Hall, Install 56000 CEN router and any cable required fi•om the City of Fort Worth T1
demarcation.
• Program and Test the S6000 CEN router.
• Install cross-connects between the DSR Master Site located at the City of Irving CJC and the City
of Fort Worth provided Tls between the supplied DSR Relay Panels and the T1 demarcation
location.
• Install cross-connects between the City of Fort Worth, and its customers site routers at various
locations throughout North Texas, and City of Fort Worth customer's supplied T I s demarcation
locations.
• During field installation of the equipment, any required changes to the installation will be
noted and assembled with the final `as-built' documentation of the system.
• Receive and inventory all equipment.
• Bond the supplied equipment to the site ground system in accordance with Motorola's R56
standards.
• Will interface with the following network connections: Tl.
• Removal of existing equipment is not included in this proposal.
• Relocation of existing equipment to a location designated by the City of For�t Worth is not
included in this proposal.
• Disposal of existing equipment is not included in this proposal.
City of Fort Worth Responsibilities:
• Provide a Firewall to be installed at the Fort Worth DSR Backup site located at the Itving
Criminal Justice Center site
• Provide access to the sites, as necessary.
• Provide the numbers of T1 links that meet the site link specifcations as described in the System
Description T1 table.
Completion Criteria:
• Fixed Network Equipment installation completed and ready for optimization.
Fixed Network Equipment Installation Complete
• All fixed network equipment installed and accepted by the City of Foi�t Woi�th.
System Installation Acceptance (Milestone)
• All equipment installations are completed and accepted by the City of Fort Worth.
� � ; / �
Optimize System FNE
Motorola Responsibilities:
• Motorola and its subcontractors optimize the DSR subsystem.
City of Fort Worth
Dynamic System Resiliency (DSR)
October 25, 2013
Use or disclosure of this proposal is subject
to the restrictions on the cover page.
Motorola Solutions Confidential Restricted Statement Of Work �7
• Verify that all equipment is operating properly and that all electrical and signal levels are set
accui•ately.
• Verify communication interfaces between devices for proper operation.
• Test features and functionality are in accordance with manufacturers' specifications and that they
comply with the final configuration established during the CDR/system staging.
City of Fort Worth Responsibilities:
• Provide access/escort to the sites as necessaiy.
5.9.2
5.9.3
5.9.4
Completion Criteria:
• System FNE optimization is complete.
Link Verification
Motorola Responsibilities:
• Perform test to verify site link performance, prior to the interconnection of the Motorola-supplied
equipment to the link equipment.
City of Fort Worth Responsibilities:
• Make available the required links which meet the specifications supplied by Motorola at the
CDR.
Completion Criteria:
• Link verification successfully completed.
Optimization Complete
o System optimization is completed. Motorola and the City of Fot-t Worth agree that the equipment
is ready for acceptance testing.
� ��
�
5.11.1
Training is not included in this proposal
ACCEPTANCE TESTING
Perform Equipment Testing
Motorola Responsibilities:
• Test individual components of the system to vei•ify compliance to the equipment specifications.
• Repeat any failed test(s) once Motoi•ola (or the City of Foi�t Worth) has completed the corrective
action(s).
• Prepare documentation of component tests to be delivered as part of the fnal documentation
package.
City of Fort Worth Responsibilities:
• Witness tests if desii•ed.
City of Fort Worth
Dynamic System Resiliency (DSR)
October 25, 2013
Use or disclosure of this proposal is subject
to the restrictions on the cover page.
Motorola Soluiions Confidential Restricted Statement Of Worlc 5-8
Completion Criteria:
• Successful coinpletion of equipment testing.
5.11.2
Perform Functional Testing
Motorola Responsibilities:
• Verify the operational functionality and featu►•es of the individual subsystems and the system
supplied by Motorola, as contracted.
• If any major task as contractually described fails, repeat that pai�ticular task after Motorola
determines that corrective action has been taken.
• Document all issues that arise during the acceptance tests.
• Document the results of the acceptance tests and present to the City of Foi�t Worth for review.
• Resolve any minor task failures before Final System Acceptance.
City of Fort Worth Responsibilities:
• Witness the functional testing.
Completion Criteria:
• Successful completion of the functional testing.
• City of Fort Wor�th approval of the functional testing.
5.11.3 System Acceptance Test Procedures (Milestone)
• City of Fort Worth approves the completion of all the required tests.
5.12 FINALIZE
5.12.1 Cutover
Motorola Responsibilities:
• Motorola and the City of Fort Woi�th develop a mutually agreed upon cutover plan based upon
discussions held during the CDR.
• During cutover, follow the written plan and implement the defined contingencies, as i•equired.
• Conduct cutover meeting(s) with user group representatives to address both how to mitigate
technical and communication problem impact to the users during cutover and during the general
operation of the system.
City of Fort Worth Responsibilities:
• Attend cutover meetings and approve the cutover plan.
• Notify the user group(s) affected by the cutover (date and time).
• Conduct a roll call of all users working during the cutover, in an organized and methodical
manner.
Completion Criteria:
• Successful integration ofthe DSR Master site into system.
City of Fort Worth
Dynamic System Resiliency (DSR)
October 25, 2013
Use or disclosure of this proposal is subject
to the restrictions on the cover page.
Motorola Solutions Confidential Restricted Statement Of Wor{c �9
5.�12.2 Resolve Punchlist
Motorola Responsibilities:
• Work with the City of Fort Worth to resolve punchlist items, documented dui•ing the Acceptance
Testing phase, in order to meet all the criteria for final system acceptance.
City of Fort Worth Responsibilities:
• Assist Motorola with resolution of identified punchlist items by providing support, such as access
to the sites, equipment and system, and approval of the i•esolved punchlist item(s).
Completion Criteria:
• All punchlist items resolved and approved by the City of Foi�t Worth.
5.12.3 Transition to Service/Project Transition Certificate
Motorola Responsibilities:
• Review the iteins necessaty for transitioning the project to warranty support and service.
• Provide a City of Fort Worth Support Plan detailing the wari•anty and post-wai•ranty suppoi�t, if
applicable, associated with the Contract equipment.
City of Fort Worth Responsibilities:
• Pat�ticipate in the Transition Service/Project Transition Certificate (PTC) process.
Completion Criteria:
• All service information has been delivered and approved by the City of Fort Worth.
5.12.4 Finalize Documentation
Motorola Responsibilities:
Provide an electronic as-built system manual on a Compact Disc (CD).
include the following:
— System Block Diagram.
— Site Block Diagram.
— Site Network Diagram.
— Site Floor Plan.
— Site Equipment Rack Configurations.
— ATP Test Checklists.
— Functional Acceptance Test Plan Test Sheets and Results.
The documentation will
— Equipinent Inventory List.
— Maintenance Manuals (where applicable).
— Technical Service Manuals (where applicable).
Drawings are created utilizing AutoCAD design software and will be delivered in Adobe PDF
fo�•mat. All other system manual documents converted fi•om native format to Adobe PDF format
to be included on the System Manual CD.
DSR System Drawings will be integrated into the overall P25 System Manual and where
applicable throughout the System Drawings.
City of Fort Worth Responsibilities:
City of Fort Worth
Dynamic System Resiliency (DSR)
October 25, 2013
Use or disclosure of this proposal is subject
to the restrictions on the cover page.
Motorola Solutions Confidential Restricted Statement Of Work 5-i0
• Receive and approve all documentation provided by Motorola.
5.12.5
5.13
5.13.1
5.13.2
Completion Criteria:
• All required documentation is provided and approved by the City of Fort Woi�th.
Final Acceptance (Milestone)
• All deliverables completed, as contractually required.
• Final System Acceptance i•eceived fi�om the City of Fort Woi�th.
�r, ��, �1 ,
Project Status Meetings
Motorola Responsibilities:
• At a mutually agreed upon occurrence, the Motorola Project Manager, or designee, will attend all
project status meetings with the City of Fort Worth, as determined during the CDR.
• Record the meeting minutes and supply the report.
• The agenda will include the following:
— Overall project status compared to the Project Schedule.
— Product or service related issues that may affect the Project Schedule.
— Status of the action items and the responsibilities associated with them, in accordance with
the Project Schedule.
— Any miscellaneous concerns of either the City of Fort Worth or Motorola.
City of Fort Worth Responsibilities:
• Attend meetings.
• Respond to issues in a timely manner.
Completion Criteria:
• Completion of the meetings and submission of ineeting minutes.
Progress Milestone Submittal
Motorola Responsibilities:
• Submit progress (non-payment) milestone completion cei�tificate/documentation.
City of Fort Worth Responsibilities:
• Approve milestone, which will signify confirmation of completion of the work associated with
the scheduled task.
Completion Criteria:
• The City of Fort Worth approval of the Milestone Completion document(s).
City of Fort Worth
Dynamic System Resiliency (DSR)
October 25, 2013
Use or disclosure of this proposal is subject
to the restrictions on the cover page.
Motorola Solutions Confidential Restricted Sfatement Of Work 5-11
5:13.3 Change Order Process
Either Party may request changes within the general scope of this Agreement. If a requested
change causes an increase or decrease in the cost, change in system configuration or adds time to
the project's timeline 1•equired to perform this Agi•eeinent, the Pal•ties will agree to an equitable
adjustment of the Contract Price, Performance Schedule, or both, and will reflect the adjustment
in a Change Ordei•. Neithei• Pai�ty is obligated to perform i•equested changes unless both Parties
execute a written Change Order.
An example of a Change Order Form is included in the following pages.
City of Fort Worth
Dynamic System Resiliency (DSR)
October 25, 2013
Use or disclosure of this proposal is subject
to the restrictions on the cover page.
Motorola Solutions Confidential Restricted Statement Of Work 5-12
l�+�t'�"�t,�i�lLA SC3LUTl�NS �HAN�E t3RDER
Change Order No. 1
Dake: September 22 2013
Project Name: FortV�+orth DSR Project- T)f-1311098
Customer Name: Cfty af Fort Wotth
Castomer Project Mgr: Alan Girton
The purpose of this Change Order isto:
The purpo�e isto updatethe E�roject ciocurtients afterthe Desiyn Review. Updated documents replace, in
tf��eir entirety, the folldwing sections of the contract. ��eciFically, upd�ites are macie in the following sections
(dated Se�rt 22, 2093 in tl7e footer cd the attached corriaine�! PdF document):
1. System Descri�tian —descriptions, drawinys, ec�uipment lis�t, etc., 9r� updatec�
2. Statemerit af Work— remon�e refer�nces to sta3iny, remove certain Fort Watth responsibilities, etc.
3. Praject 5�hetlule- u��dated
The following is al� added to witf7 thi$ Chanye Order:
1. Addendur-nA-6GAQuestionsandAnsva�rs
Contrad # Citv af Fort Worth: C-262�8
tulotorc�la Sal�rtions Cantract: 887�9
Contract Dat� 7124i20�13
In accord�nce with the terrns anc! conditions of the cantract identified abaae hetween the City of Fort
Warth and tu1 otorola Soi�rtions, Inc., the follavving chanyes are ap�roveci:
ce Adiustments
Origin�l Contr�rctValue: � $982,2�4
Pre�ious Change dreler amounts for Ch�nge Order numbers
( � � througt7 (—�� NtA
I " I�
This Change Order: No pricing acfjustment
NewContractValue: $982,254
i Date Ad-ustme�ts
Original C+�mpletion Date: 1114l2413
Current Completian Date prior to this Ch�nye Order: 1 1/412 01 3
NewCompletion Date: NJ.4
Chan esto skemPurdiaseA reement SPA Provision�
There are no chanyes to the Systern Purcha:� A,yreemer�t (SPAJ Provi�ions with this chanye arcler.
Chanqes in Equipment:
The ec�uipment chanyes are identiFiec! in the ne�+ equiFSrnent liUt within the upcl�,tPd System Deseription
prouicied with this Chancte O rder
Chan esinSe�vices:
Fort lNatth DSR Pr�ojEct
City of Fort Worth
Dynamic System Resiliency (DSR)
Page1 c,f2
October 25, 2013
Use or disclosure of this proposal is subject
to the restrictions on the cover page.
Motorola Solutions Confidential Restricted Statement Of Work 5-13
!1�'/�'��A�i'�7lLA SOLUTI�NS
Services chanaes ar�
�HAN�E t�RDER
�f Work prwided with this Cfianye Order.
�diedule Chan e�
Schedule efianyes are ident�ecl in the updated Project Schedule prcNided with this Chanye Order
The Price of the cor�tract is not a
Cus#omer Responsibilitie�
Customer Responsibiliiy chang�s are id
Ortier.
Order.
upciated Statement of Work prwicled with this
Payment Schedule Change� '
There are no P�rnent �chedule Chanyeswith this Chanye Order.
Unless arriende�i abwe, alI other terms and conditions oftt7e Coritract shall rsmain in full force. If there
are ary inconsistencies betw�en the provisions of this Change Or�der anci the prwisions ofthe Cordract,
theprcNi�iansofthe Change drr�erwill prc�v�iil.
Review�ed by: Date:
M otorola Solutions Prnject 6,1 t�nayer
Revievv�d by: Date:
City of Fort Worth Project M anager
Fort Wotth 6SR Project
City of Fort Worth
Dynamic System Resiliency (DSR)
Motorola Solutions Confidential Restricted
Page 2 of G
October 25, 2013
Use or disciosure of this proposal is subject
to the restrictions on the cover page.
Statement Of Work 5-14
S�CTION 6
JECT S
The following is the estimated Project Schedule cotnpleted after the Design Review
_ _ ,
% Comp iTask Name ,Duration Start Finish
26% ;DSR Project ',86 days Mon 7/29/13 �Mon 11/25/13
100% ; Contract Award �1 day 'Mon 7/29/13 ',Mon 7/29/13
_
100% Contract Design Review ;1 day IWed 7/31/13 ,Wed 7/31/13 ,
, ,
100% Design Approval '1 day 'Thu 8/1/13 Thu 8/1/13
,
100% Notice to Proceed (30% billing) �'1 day !Thu 8/1/13 Thu 8/1/13
,
100% , Generate Subcontracts '3 days 'Fri 8/2/13 'Tue 8/6/13
100% Order Processing �1 day �Fri 8/2/13 Fri 8/2/13
100% Motorola Manufacture Fixed Network Equipment 1 day Mon 8/5/13 iMon 8/5/13
100% Ship Equipment to Field �5 days Tue 8/6/13 'Mon 8/12/13
80% � Inventory (40% billing) ,15 days 'Tue 8/13/13 Mon 9/2/13
_
0% ' Irving Criminal Just Center Civil Wori< (electrical) 2 days 'Fri 8/30/13 ;Mon 9/2/13
0% System Installation ,10 days ,Fri 8/30/13 Thu 9/12/13
0% � System Installation Acceptance (15% billing) �1 day ,Fri 9/13/13 Fri 9/13/13
0% Link Verification 3 days Mon 9/16/13 ��Wed 9/18/13
0% Upgrade to DSR �10 days Mon 9/30/13 Fri 10/11/13
0% i System Optimization �10 days iMon 9/30/13 Fri 10/11/13
0% � Perform Functional Testing 2 days Thu 10/10/13 IFri 10/11/13
0% !, R56 Audit '�3 days Thu 10/10/13 Mon 10/14/13
0% , System Acceptance (10%) 1 day �Mon 10/14/13'���Mon 10/14/13
_
0% Cut Over ,0 days Mon 10/14/13 �Mon 10/14/13
0% Fina) Inspection �0 days 'Mon 10/14/13 iMon 10/14/13
,
0% Punch List Resolution 5 days Tue 10/15/13 �Mon 10/21/13
�;0% , Transition to Service ,0 days �Mon 10/14/13 �Mon 10/14/13
0% �I Fina) Documentation �20 days Tue 10/22/13 'Mon 11/18/13
!0% Final Acceptance (5% Billing Milestone) '�5 days Tue 11/19/13 Mon 11/25/13
City of Fort Worth October 25, 2013
Dynamic System Resiliency (DSR) Use or disclosure of this proposal is subject
to the restrictions on the cover page.
Motorola Solutions Confidential Restricted Project Schedule 6-1
�11 / � : �
� � . � 1 '
.
:, � � � : � � • •
Dynamic System Resilience (DSR) Proposal Review Report
A. DSR PROPOSAL BACKGROUND
The City places great emphasis and importance on the redundancy and fault tolerance of the P25
radio communications system and as such requested a fixed firm proposal for DSR from
Motorola to further enhance the resiliency of the network. Buford Goff & Associates, Inc.
(BGA) reviewed the proposal and has compiled comments, questions and recommendations for
the City's evaluation.
B. REQUEST FOR INFORMATION
BGA recommends that the City request additional information and clarification from Motorola to
address the items detailed below.
1. Section 1.1 describes "...automatic with only momentaiy interruption to radio system users
as the DSR master site is activated." Section 1.2.2 also discusses the cool•dination required to
mitigate downtime when the Master site is reprogrammed for DSR operation.
a. What is the expected switching time between DSR Master sites once implemented on
the live system? Is there any downtime during switchover? If so, what components?
— The system �vill complete a fi�ll switch within a minute for a fi�lly configured
system. In smallei• systems, this time will be closer to 15 to 20 seconds. Du►•ing this
time, the RF sites �vill entec site trunlcing and data fiinctionality will be down.
b. What is ihe estimated downtime involved in reprogramming the Master Site for DSR?
— The eapansion involves reloading the existing GAS servecs with DSR flag enabled.
This can be doue server at a time b�lt it would involve switching zone controllers as
well. So site trlu�lcing ilnpact wol�ld be a ZC switch. NM impact (zone watch,
voyence etc) will be the time it takes to reload the serveis �4-Shrs each.
City of Fort Worth
Dynamic System Resiliency (DSR)
October 25, 2013
Use or disclosure of this proposal is subject
to the restrictions on the cover page.
Motorola Solutions Confidenfial Restricted Addendum A— BGA Questions and Answers 6-1
So networl< management fi�nctions associated with each GAS server will be down for
that 4-5 hr period t}1e servei• is being loaded. This systein will continne operate
normally.
Thei•e are a few thoughts that arose in the discussion that cc�uld add to the downtime:
We believe new network configs need to be deployed, and dual site links need to be
configured (if they ai•e not alr•eady), so they could talce a hit hei•e.
There may be CEN do�vntime if they are re-configuring.
c. Please provide switching times of live systems currently implementing DSR It is
understood that times may vary based on system and site topology. — Recent
experience tells us on a 9 site simulcast with 3 dispatch centers at 23 ops total —
appeoaimately 15-20 seconds. However the specification is up to a minute
2. Section l.l states that "All non-Fort Worth users having dual links foT• their sites and dispatch
locations will require that one of the two links be routed to the DSR Master Site to gain
benefit of DSR operation."
a. Is this a requirement? — This is a requirement to 1•l�n the site as a DSR site. Can
agencies decide to retain redundant links to Fort Worth if their primary focus is on
preventing site link disruption, or if they do not desire to obtain site linlcs to Irving, or
because they are fine with operating in site trunking in an emergency scenario? — Yes.
In the case in which a DSR switch would occur, the site would enter site trunking.
3. Are there any Irving Customer's that plan to connect links to the Irving DSR Backup in Fort
Worth? — At this time, the City of [rving 4 site simulcast cell is the only site connecting to the
Irving DSR. No other customet• sites have been proposed that will tie into the City of It•ving
mastet• site.
4. Section 1.1 page 1-2 states "Some City of Fort Woi•th features on the main Master Site would
not function during the time the system is switched to the DSR Master site." Please detail
specifically which features would not fiinction. Are there features in addition to the IV&D
discussion that follows?
The DSR only has CEN back up links to the downtown Data Center so this is the only site
that will be able to do CEN fi�netions when on the DSR Master. There is no back �ip PN
Server, and you will not get other fiinctions down that pipe if there is no server associated
with them in the DSR CEN — so things like ATIA stream eic. �vill not worl< so even though
the data pipe is available the only DSR function that will fi►nctioi� fi•om the DSR would be
the KMF Server and KMF Client at the Data Centec,
5. Section 1.1 page 1-3 and Section 23 state the assumption that "Irving will supply the
required i•acic space and UPS powel• for the DSR Master site equipment". While this
assumption is logical considering Foi-t Worth is doing the satne with Irving as stated in the
proposal, it must be verified.
City of Fort Worth
Dynamic System Resiliency (DSR)
October 25, 2013
Use or disclosure of this proposal is subject
to the restrictions on the cover page.
Motorola Solutions Confidential Restricted Addendum A— BGA Questions and Answers 6-2
a. Has Motorola verified that adequate power and rack space eYists? HVAC? - Racic
space has been designated foi• the CFW DSR equipment. HVAC shot�ld be sufficient,
but �vill need to be verified with tlle City of Irving.
b. Section 5.7 and the equipment list refer to two new cabinets, two DSOPs, 4 circuits
and a new 32 breaker panel. Where has space been designated for this equipment? -
Space has been assigt�ed within the City of I1•ving CJC equipmet�t i•oom for the
instaflation of two cabinets foc the CFW DSR ec�uipment.
c. Is there an existing UPS to utilize or should Fort Worth provide one? — Will need
to verify if the eYisting UPS wili handle the load.
6. Section 1.2 page 1-8 states that the bandwidth to the two dispatch centers has not been
calculated and is based on audio loggintc. Is there a potentiai for more than the two Tls
listed in table 1-2 to be required? — These should be okay — logging is not included with the
DSR core so the IP logging recorder will not be available when you are switched to the DSR
master. The note in section 1.2 is a bit confiising in the proposal because the links were
calculated to the Foi�t Worth Master for the two dispatch centeis - and there is not any IP
logging fiinctions at the Fort Worth dispatch centeis they are in the core at the Master site.
7. Section 1.3 refers to the proposal as firm fixed but the last sentence states it's a budgetary
quotation that will require updates if necessary. It is assumed that this is a typo but please
confirm. — Yes it was a typo.
8. Section 2, System Drawing labeled "ASTRO 25 Backup Master Site" has ct•oss-hatched
items with a note that these components exist in the City of Fort Worth System. These
crosshatched items rept•esented existing i•eused items (i.e. CFW alt�eady had core LAN
s�vitches which oui• stuff was going to plug into).
a. Does this mean the LAN Switch, Firewall/DMZ and Gateway Routers at Eagle
Mountain? The additional Firewall at CJC is lised to filter data for the KMF server
and I<MF client at the Data Center. Therefore the Fire�vall/DMZ for Fot�t Worth
would remain as designed 1•ecently at Eagle Mountain for conditions �vhere noi•Inal
operation talces place. Note other agencies and some fi►nctions of the ctu�rent DMZ
�vi(I not be available when opel•ating on the back up Master. Note also Irving will
share soule of the Coce equipment at Fort Wo►•th for theii• DSR and viee versa for Fort
Wot•th and their DSR at CJC. There is a reference to another Fort Worth provided
Firewall to be installed at Irving CJC in the SOW. That is correct — this was wcitten
and designed before the CEN �vas completely designed for Fort Worth it was our
assunlption at the ti�ne that �ve could use one of the two fii•ewalls previously
purchased by Foct Worth at Irving CJC — however this is not the case — the proposal
does not include an additional Motoi•ola Solutions fre�vall and therefot�e the City
woltld be requit•ed to purchase an additional one at CJC.
b. Does the CEN design remain the same in the DSR configuration?
Again, the CEN design for the n�ain Core remains the sa�ne — when using the DSR
located at CJC in Irving the only fu�lctions that will be reproduced fi•om the CEN are
City of Fort Worth
Dynamic System Resiliency (DSR)
October 25, 2013
Use or disclosure of this proposal is subject
to the restrictions on the cover page.
Motorola Solutions Confidential Restricted Addendum A— BGA Questions and Answers 6-3
the KMF functions through the Data Centei• — the CEN at that location is ne�v foi• this
pi•oject. The CEN at FTW Eagle Mtn. remains the saine.
Section 1.1 Page 1-2 CEN operation discusses loss ofCEN fiinctionality specifically KMF-
OTAP-Inform etc. during failure of Eagle Mountain. The bullets then describe continued
availability of the OTAP terminal at the data center and the need for additional routers. See
note above about tlle same c�uestion.
a. Please further detail what functionality will be available and what eq�iipment is
necessaly?
b. Section 4.6 ATP has a test for KMF-OTAR funetionality during DSR but it appears
to only validate PDG switchover and registration with the KMF server. Will OTAR
functions be available as well?
10. Section 4-8 ATP involves a primary and secondary UCS but the drawing has the secondary
drawing cross-hatched out. Is a secondary UCS necessary? Please clarify. — Both UCS's will
be used. Tl�ere is a UCS at the CFW Eagle Moi�ntain site and a UCS at the Irving CJC site.
Only one UCS will be used at any given time, but each will bacic up the other in the case of a
failuce. This is not automatic and would require user intervention to pecfol•m the switch.
11. Are there tests that prove continued operation of Network Management features during DSR
switchover? — Yes
12. Formal training is not proposed as stated in the SOW section 5.10. Has SI time been
allocated in the proposal to provide informal training on DSR switchover for Fort Worth
personnel? What about external customers whose sites and consoles would be affected?
No formal training is included or thought to be necessary, however we can provide
infor►nation about DSR opel•ation and potential impaets in the event of Mastei• site transitions
that can be presented and/oc disti•ibuted to all custoiners that wolilcl have a need to lcnow.
13. Section 5.12.4 of the SOW lists the documentation set proposed for DSR Is this a
standalone documentation set or have costs been included for DSR to be integrated in the
overall P25 project's documentation set?
The documentation will be integrated with the overali project documentation foi• Phases 1
through 4.
14. Section 6 Project Scheduie is 107 days or just over five months concluding in early
December. Cutover activities would likely be postponed around Thanlcsgiving, which would
result in DSR project completion after the current Phase 3 cutover date.
a. If necessary, pending Burnett Plaza site wo1�k completion and final schedule, would it
be possible to compress this schedule? If so, how?
b. Are there any potential savings in cost and time if DSR is incorporated into the P25
schedule and run as one project (change order vs. standalone pt•oject).
City of Fort Worth October 25, 2013
Dynamic System Resiliency (DSR) Use or disclosure of this proposal is subject
to the restrictions on the cover page.
Motorola Solutions Confidential Restricted Addendum A— BGA Questions and Answers 6-4
We have currently schedu(ed with Motorola Upgrade Operations (UO) to do this
upgrade beginning Septe�nbet� 30 thi•ough October 11, 2013. This was not taken into
account in t11e schedule provided �vith the proposal, but it is inlportant to point out
that ordeTs should be placed no later than nlid-July (hopefiilly earliei•) in oi•del• to
maintain this upgrade schedule. A new/updated schedule will be provided in Design
Review.
15. In reference to section 7.3 Warranty Summary, please provide a quote for post-warranty
sei•vices for DSR to match the post-warranty discussions for the P25 project. — The wai•i•anty
pel•iod included in this pi•oposal will cun thi•ough December 31, 2014 to align with the cul•i•ent
Fort Wortl� P25 Pi•oject warranty period. Kevin Lamb �vill be compiling and presenting the
2015 Post Wacranty numbers to Fort Worth prior to June 15, 2013.
16. System Pricing section 8 is a lump sum amount. Please provide a cost breakdown of
equipment, civil and electt•ical work, system integl•ation, warranty, post-warranty, SUA and
any applied discounts in the same format as the P25 proposal.
Round 2 Questions
Questions and answers labeled "Round 2" from email dated May 16, 2013
1. If the primary Prime site link from Rolling Hills to the Eagle Mountain Main Master site were to
fail, will the secondary linl< to the CJC Backup DSR Foi�t Worth Master allow re-routing back to
the local Eagle Mountain Master Site without requiring a DSR switchover? We would like to
understand how the DSR architecture protects the P25 system and Prime Sites against site link
failures.
Both links are logically tied to the active zone controller dur•ing normal operation. The primary
link travels through the link directly connected to the active core and the backup link rotrtes
through the inactive core networlc and tllrough the intei•zone link back to the active core. Upon a
primary link failure, connectivity �vill be maintained through the bacicttp link, though physically
connected to the inactive core, as it will be logically connected to the active core through the
network.
2. Please provide a regional ISSI map (who is connected to whom) to evaluate communications
flows and evaluate disruptions in service that tnay occur in a DSR scenario. Will the Interzone
link between Fort Worth and Irving allow access to other agencies connected to either entity via
ISSI? If so, how?
There ace two ISSI links that are ��sed in the system fi•om ISSI boxes —
l. Dallas to the Airpol•t ISSI system
2. Fort Worth to the Dallas ISSI system
City of Fort Worth
Dynamic System Resiliency (DSR)
October 25, 2013
Use or disclosure of this proposal is subject
to the restrictions on the cover page.
Motorola Solutions Confidential Restricted Addendum A— BGA Questions and Answers 6-5
3. A(1 ISSI sites connect to one of these two sites
The following pacagraphs come fi•om the Systetn Description for Fort Wo1•th DSR — it notes that
the ISSI linl< fi•om Fort Worth will not be fiulctional when a catasti•ophic fail takes place at Eagle
Mountain.
"Note that the City of Fort Wol•th's Inter-SubSystem Interface (ISSI) gateway will not be
functional when operati►Zg on the DSR tnastet• site. This is because the City of Fort Worth's
ISSI.1 gateway does not support DSR operation. The City's current ISSI.1 gateway will
continue to opei•ate no►•mally as long as the City is on the tnain tnaster site at Eagle Mo�mtain and
opei•ating off of eithec Zone Controllei• (ZC 1 or ZC2). In the �mlikely event the City would need
to switch to the DSR master site, using Zone Contl•ollers at the Irving site (ZC3 oi• ZC�4), the
ISSI.1 gateway will not be functional while operating on the DSR master site."
"Should the City determine ISSI fiinctionality is required when operating on the DSR master
site, the ISSI.I gateway can be upgraded to the ISSI 8000 gateway. The ISSI 8000 gateway
sllpports DSR operation for system releases 7.13 or higher."
"Additionally, an ISSI 8000 gateway would also be rec�uired at the DSR master site location.
This proposal does not include an upgrade to the City's c�irrent ISSLl gateway."
As far as the question concerning the use by a Fort Worth unit of the Fort Worth ISSI when in
the capture of an Irving site by a Fort Wocth unit or the use an Irving unit of the Irving ISSI
when in the capture of the Fort Worth system. I would note two things:
1. W11ile Irving has purchasecl ISSI they have not determined wl�ece these links will connect as
of this time.
2. Since the ISSI function is mecely a mapping of particula�• talkgroups on a system through the
ISSI boY to another system it would be possible to i�se an ISSI tallcgi•oup authorized on the
Fort Worth system that is mapped to the ISSI fi•om an Icving site if the talkgi•oup wei•e
authorized to transvei•se the Interzone linl<. It would tie up r•esources on both systems
however.
Note this would also be true of an Ii•ving unit using an Irving talkgroup mapped to ISSI
through the ISSI bo� at Irving if the salne conditions �vere tr��e, and with the same caveats as
above.
Note also that in no case wo�ild a Foi•t Wortl� unit be able to access the Fort Worth ISSI
tallcgro�ips �vhen in tlle DSR scenacio.
Since this is so eesource intensive and ISSI access is cal•e we would not recon�nlend this
operation.
ciry of Fort worth
Dynamic System Resiiiency (DSR)
October 25, 2013
Use or disclosure of this proposal is subject
to the restrictions on the cover page.
Motorola Solutions Confidential Restricted Addendum A— BGA Questions and Answers 6-6
3. Is there one additionai pair of Core Routers added at both Master sites for the DSR design?
How tnuch core router capacity will be utilized if the City and ail eYternal agencies
implement dual linlcs with secondaty links routed to the DSR backUp at CJC?
Once NETCO goes on the air thei•e will be thl•ee sets of core cottters at the Eagle Mountain
Master Site. There will also be three paics of core routers at the CJC site for DSR.
4. All of the items in the SOW section 5.7 page 5-8 "Foi•t Worth Responsibilities" relate to the
environmental, permitting, space, electt•ical, HVAC and grounding readiness of the Irving
CJC DSR Baclaip site location. We request that Motorola to confirm that all of these
requirements and facilities exist at CJC.
Motorola as confirt�led that the City of Irving CJC faciliry will accolnmodate the City of Fort
Worth DSR Backup site in all these areas. Cabinet space has already been allocated within
the CJC equipment room. Electrical woi•k and grounding have been incllided as pat•t of this
pi•oject. UPS capacity and HVAC cequirements have been verified to be sufficient for the
additional load.
(Low priority) Please provide a high level technical description of Motorola's geographically
redundant Pr•ime Site Simulcast architecture and a conceptual design to address a Prime site
failure at Eagle Mountain. The concern is regarding catastrophic failure of the Eagle
Mountain site disrupting one Simulcast layer which DSR would not protect against. The
City requests Motorola provide a ROM level quote for the conceptual solution as well as a
comparison ROM quote to geographically relocate the Eagie Mountain Prime Site to another
location.
Actually what Motorola Solutions has pt•ovided in the Fort Worth Syste�n is Layer•
Redundancy at geographically separate prime sites. Shouid a layer become inactive because
of catastrophic failure of a prime site in Layer 02 for example users on that layer would need
to switch to a backup Yalkgroup on Layer O1 which is still active, and vice vel•sa. Half of the
system resources for channels would no longer be available so instead of operating on two 20
cha�lnel layers all users oti the City of Foi•t Wocth system would have only 1 layer of 20
channels to operate on until the disabled layer is restoced.
The second question about relocation of the pritne site at Eagle Mountain has a some�vhat
complex answer. Howevec the basic answet• is yes it could be relocated. However, here are
some of the issues i•aised with that scenario:
A site would have to be chose with adec�u�te power and space and T1 capacity —
a. The Rolling Hills site which has the Layer 02 prime requires three cacic spaces for
additional equipmei�t for the prime site. The new prime �vould require minimum
of 3 rack spaces for the new prime.
b. The Rolling Nills site �vhich has the Layer 02 prime requires an additional UPS in
the building because of the Prin�e site — the building in which the relocated prime
site would be located wot�ld lilcely requii•e additional UPS capacity.
c. All of the T1 s going to the Eagle Mountain prime site would need to be celocated
to the new priine site (Note ilot the Mastel• site links) Also two additional linlcs
City of Fort Worth
Dynamic System Resiliency (DSR)
October 25, 2013
Use or disciosure of this proposal is subject
to the restrictions on the cover page.
Motorola Solutions Confidential Restricfed Addendum A— BGA Questions and Answers 6-7
fi�om the Eagle Mountain Layer O1 RF site would neecl to be routed to the new
site.
2. Today if Eagle Mountain �vere to be completely taken off-line you would have the
following conditions:
a. Layer Ol would be unavailable
b. Layer 02 wot�ld be in site trunlcing — no direct connect to the dispatch centel•s
eacept through bacicup consolettes or through control station dispatch.
c. Network Management functions would be down.
d. Layer 02 would be dirninished in coverage by one site Eagle Mountain.
e. The City would still be opel•ational on one layer in site t►•unlcing — �vhen and if
DSR was in place Layer 02 �vould be operational wide-at•ea off the DSR site — the
NM filnctions would be available fi•om the DSR Master but Layer O1 would be off
line.
f. Note if just the Master site equipment was da►naged Layer O l would be in site
trunlcing or if DSR is purchased would continue to work wide area through DSR.
3. If the prime site was moved —
a. Iftl�at site were failed — Layer 02 would still be the active layer and Mastei• Site
activity wou�d continue through Eagle Mountain.
b. If the prime site was co-located at one of the eYisting RF sites and that site went
off you would still lose that layer and the RF coverage foc both layers ofFthat site.
c. Layec O l �vould have to be disabled during the reconfiguration of prime site
equipment to a new site.
4. None of this deals �vith the cost involved in moving the prime site — just the steps
required to make it happen. Please let us know what your.desire is here so that we can
appropriately respond if it is desired to move the prime.
City of Fort Worth
Dynamic System Resiliency (DSR)
October 25, 2013
Use or disclosure of this proposal is subject
to the restrictions on the cover page.
Motorola Solutions Confidential Restricted Addendum A— BGA Questions and Answers 6-8
Round 3 Questions
Questions and answers labeled "Round 3" from email dated June 10, 2013
Clarification to Question 5- Round 1
The response above indicates further evaluation of the HVAC and UPS is necessary however the
response to Round 2 Questions #4 states that the UPS and HVAC will be sufficient. Please clarify.
Also indicate if the City would be required to provide the HVAC and UPS if necessaiy or also install.
The bottom line answer to this question is the latest response fi�om the Ii•vit�g pcoject team is that HVAC
and UPS are sufficient to handle the additional load and BTUs pi�ovided by installing the CFW DSR at
their location.
Therefot•e there is no need for• Fort Worth to supply or instali additional UPS or HVAC resources at this
time.
Follow-up to Ouestion 8- Round 1
The response indicates that core equipment is shared for Irving and Fort Worth. Specifically what
equipment wili be shared at both cores? How will network management and warranty be handied for
shared equipment?
Gate�vay Routers
Core LANSW
GGSN
Firewall (ICMF)
Clarifcation to Question 9- Round 1
a. Motorola's response to question 4 indicates that only KMF will be available in a DSR scenat•io
via the backup CEN links to the data center. So in response to question 9 are we to assume that
OTAP at the data center will also work or not function (no backup PN)?
OTAP will continue to worlc as long as 1) PN Server is alive; 2) As connectivity is still available
to the DSR site. However in the case of catastrophic failure of the main master site only the
KMF will wol•k on the DSR Master — therefore OTAP will not woi•k.
b. Also with respect to 9b, at�e OTAR functions available in conjunction with KMF?
OTAR is a KMF function and therefot•e will work with the DSR Master. Note the KMF server
and 1 Client will be located at the City Data Center. Therefore the only access to KMF (OTAR)
fiinctions in DSR conditions wiil be available thl•oug11 the I�MF Client located at the Data
Center.
Clat•ification to Question 16 - Round 1
Does line item 2 include all electrical work necessary to install the DSR bacicup equipment for Fort
Woi�th at CJC? What about the UPS or enhanced HVAC if necessary? Is there anything that is a City
responsibility with respect to this category?
City of Fort Worth
Dynamic System Resiliency (DSR)
October 25, 2013
Use or disclosure of this proposal is subject
to the restrictions on the cover page.
Motorola Solutions Confidential Restricted Addendum A— BGA Questions and Answers 6-9
Yes installation is included for CFW DSR — again at this time there is no enhancement of the HVAC oi•
UPS t•equired. CFW is not responsible for this categoly of service.
Clarification to Question 2- Round 2
We understand that ISSI wili not filnction in a DSR scenario without an upgrade. The question
requested a regional ISSI map or biock diagram so the City couid evaluate interopeT•ability scenarios.
Will communications be available through the ISSI link to Dallas and Irving to other agencies that ai•e
not currently possible? From our understanding there are other agencies connected to Dailas' ISSI
(Austin etc.) We understand that this would be resource intensive scenario per your response above, but
would be a consideration for emergency scenarios only.
Cut•rei�tly the Fort Worth system is connected to the Dallas System with ISSi connectivity
The Dallas System is tied to Fort Worth and the Aii• Port System via lSSi
Fort Worth is connected to Irving via Smai•tZone
Irving has an ISSi Networl< but its connections have yet to be defined.
ISSi is designed to woi•I< between diffei•ent systems via a one-on-one connection. These paths pi•ovide
Talkgroup connectivity via mapping a talkgrot�p on one system to a talkgroup on the other system.
Since Dallas has ISSi's to both Fort Worth and to the Airport system you could rnap both ISSi's to pass
the same tallcgroup aiid therefore talk tolfi•om a talkgroup on Fort Worth to an Airport tallcgrolip. Since
Irving is connected to Fort Worth via Smart Zone ISSi traffic from the systems that will connect to the
Irving ISSi could be mapped to tallc on Fort Worth, Dallas (via lSSi linlc to Dallas) and to the Airport
System (via the ISSi linlc at Irving, Smart Zone to Foi�t Wot�th, via Dallas ISSi link to Fort Worth, and to
an Airport tallcgroup via the ISSi link to the airport)
Thei•e are no other ISSi linlcs on these systems at this tinle, for exanlple there is none to Alistin.
There are two points I think I should make concerning these cross-system ISSi links with multi-links
needing to be set-up with each call:
l. The system administrators on each system will have to set up the mapping to allow a call to
traverse the various systems.
2. Since with a talkgroup call on System A you would be creating a call on System B, and through
System B a call on System C it will require longer than normal tin�e to pass audio. I have to set
up the call on system A then on B and then o�1 C the delay fot• a call will be longer than 500 msec
before I can pass audio on that call. If each system ISSi and System toolc 500 msec it could take
up to 1.5 seconds in the exalnple where you are going through 3 systems.
Clarification to Question 4- Round 2
While the response is satisfactory we request that Motorola remove these responsibilities as "Fort
Worth" in the SOW as part of the Design Review pr•ocess.
We'll address during Design Review.
Clarification to Question 5- Round 2
Please provide an amended response to address the ciarifications below.
City of Fort Worth October 25, 2013
Dynamic System Resiliency (DSR) Use or disclosure of this proposal is subject
to the restrictions on the cover page.
Motorola Solutions Confidential Resfricted Addendum A— BGA Questions and Answers 6-10
y� a. To clarify the ot�iginal question, we wei•e asking about a conceptual design and discussion foi• a
true Prime Simulcast Site backup for Eagle Mountain Layer O1 layer only. That is, equipment
that would be geographically located at another location and activate should the Prime Site only
fail at Eagle Mountain. The thought behind this request wouid be to protect against a
catastrophic failure at Eagle Mountain disrupting Wide Area communications but also site
trunking of Layer O1.
There are two approaches that can be taken to achieve redundant geographically sepacate pcime
sites. Only the tirst of these is available until October of 2014. This date is when the City of
Foi•t Worth/City of Irving infrasti•ucture is upgraded to 7.14.
Option 1
Several yeals ago because of rec�uests in this region, local engineel•ing teams developed a means
of providing a geographically separate prime site location.
This redundancy requires the fol(owing:
o Additional system T1 s are needed — two T 1 fi•om each ren�ote site will be routed to the
new pcime site.
e One new Tl from the new priine site to CJC Irving CFW DSR site.
• Additional Moscad equipment with ne�v programming to be installed at Eagle Mtn. prime
and the new pt•ime site for layer O1. This programming is done by a third party vendor.
• Radios at each prime site to indicate the condition of that layer
o Radio foi• wide area detection
o Radio for site trunlcing detection
o Radio for failsoft detection
o Radio foi• laye►• failure detection
o A special switch is installed at the output of these radios to create relay clos�ires at
the pi•ime site based on layer condition.
o Moscad is programmed to interpret these conditions to al(ow for switching the
prime site it is located at to the proper mode and to coute T1 s t�vo and fi�om that
site.
• The output of the MOSCAD is connected to a switch module to switch T 1 s at the prime
site —►�emote sites to prime and prime to Master site.
• Typically this logic is used to switch the bacicup prime site into the opecational mode
upon failiu•e of the main pi•ime site, automatically depending on layer condition.
• The switch bacic to the main prime is typically a manual switch done through either a
Moscad relay closu►•e at the sites, or an E lead fiinction via the microwave system. The
coiitrol for this could be located at the radio shop oc other City of Fort Worth location.
• The �nain idea of ihis configuration was to aflow the logic to switch to the bacicup prime
upon failure of the main prime — but not in the other direction to allo�v for analysis for the
repairs needed, the repairs to be peeformed and tested co�npletely before teying to restore
normal operation. Human intervention in this step of the restoration was seen as
necessary.
Aciditional equipment requii•ed to implement this type of solution:
City of Fort Worth
Dynamic System Resiliency (DSR)
October 25, 2013
Use or disclosure of this proposal is subject
to the restrictions on the cover page.
Motorola Solutions Confidential Restricted Addendum A— BGA Questions and Answers 6-11
e Complete set of standat•d pi•ime site equip�ilent at new pi•ime site (layei• O l)
• New Coci7ett switches at each prime site (layer O1)
• Raven Audio switches for detection of radio system layer condition at each prime site for
layer 01
• Four each P25 mobile radios with po�ver supply and antenna system for radio system
layer condition at each prime site for layer O1
• New MOSCAD RTU with special systetn programming.
• Additional equipulent for "manual" switching at both prime sites and possibly at the
Radio Shop
Option 2(only available iu October of 2014 on 7.14 t�pgrade)
The geo-redundant prime site can be considei•ed to a lai•ge eYtent to be simply a redundant
comparatoc prime site with redundant site gateways in which the 1•ed�mdant components a►•e
installed at t�vo geogi•aphic locations. Additional itenls that are added to this al•e a thii•d site
controller and a site reference, so either site �vill sLipport the same filll channel capacity of the
subsystem.
Oul� ASTRO 25 system "sees" this configuration as a single simulcast prime site or subsystem.
In presentations to customers it should be shown as a pair of redundant prime sites, a primacy
prime site and a secondary prime site. In general active resources "prefer" the primaiy prime
site, but this is and operational and not an ordering consideration.
Geo-redundant prime sites are only available with IP sim�llcast subsystenls. IP simulcast sub-
sites may be either ESS or stand-alone repeater based. Only Ethernet connectivity is supported
for this solution, both to the master site(s) and sub-sites.
A simple block diagram of this configuration is shown below:
City of Fort Worth
Dynamic System Resiliency (DSR)
October 25, 2013
Use or disclosure of this proposal is subject
to the restrictions on the cover page.
Motorola Solutions Confidential Restricted Addendum A— BGA Questions and Answers 6-12
The following equipment is needed foi• both prime locations (main and redimdant):
o Two HP 2620-48 switch this replaces the e�isting site switches fol• the cul•cent pritne site
location. One of the new switches is located at the eYisting location and one would be
located at the new prime location.
• Two Backhattl switches are needed. One would be located at the elisting prime location and
one would be located at the new prime location. (These ai•e requiced because the eYisting site
links will need to be replaced with IP based links to each of the remotes, it is assumed that
Fort Worth would provide this throi�gh the MPLS capability of their microwave system).
The following additional eqiiipment would be requil•ed at the new pi•ime site only:
• One site controllei•
Ten new comparator bo�es with twenty total comparators.
New TRAK GPS cards at new site (Note if not co-located with an eaisting RF site will
reqt�il•e a new TRAI� GPS with antenna systems)
The following new links are required between the split prime sites. These links milst be
redundant, diversely routed "LAN eatensions" between prime sites; the following specifications
are CRITICAL:
Transparent, dedicated 10 or 100 Mbps Ethernet links
Linlc speed depends on subsystem size: if the total of the numbec of tallc-paths, sub-sites,
and CCGW's & HPD ovei•(ay sites > 42, 100 Mbps must be pl•ovided.
One-way latency < Sms
The reconfigtu•ed and site liiiks betweeu the remote sites and the two pri�ne loeations will
consunle much less than the existing Tls they are replacing. The prime site linl<s to the Master
City of Fort Worth
Dynamic System Resiliency (DSR)
October 25, 2013
Use or disclosure of this proposal is subject
to the restrictions on the cover page.
Motorola Solutions Confidential Restricted Addendum A— BGA Questions and Answers 6-13
site fi•on� each of the prime locations will a(so cequil•e n�uch less bandwidth than the e�isting T1
links. This is because the City wiil now have to have IP links between each prime and each
i•emote, and IP linlcs between each pi•ime and the Eagle and CJC DSR Master sites. The eapacity
of these links has not been calculated at this time but is foreseen as being the equivalent to 6 or 7
DSOs at this moment.
b. The second part of the original question discusses relocation of the Eagle Mountain Prime
Simulcast Site in order to maintain site tr�inking of Layer 01 cathec than losing it completely
should a catastrophic failu�•e of Eagle Moimtain occur.
Before the implementation of DSR the following would happen if Eagle Mountain were to have
a catastrophic failure:
1. Wide-Area tr�ullcing would no longer be availab�e on either layer.
2. Layer O1 would cease to operate.
3. Eagle Mountain would no longer available therefore the RF site would cease for both layers.
4. Layer 02 wol�ld still operate in a Site Trunlcing scenario,
After the impiementation of DSR the following would happen if Eagle Mountain were to have
catastrophic failure
l. Wide-Area trunlcing would be available through the DSR for which ever prime sites are up.
2. Layer O l would cease to operate —(if prime site is affected by catastrophic failure of the
whole site).
3. Eagle Mo��ntain RF site for both layecs �vould be off-line (if entire site fails due to
catastrophic failure).
4. Layer 02 wouid continue to operate in the wide area trunking mode thcough the DSR.
Situation after DSR if Prime site for Layer Ol were moved to another location (and Eagle
Mountain Master site failed).
1. If eatastrophic failut�e is on the Eagle Mountain site (affecting all elements at that location):
a. Both layers would still be in wide-area trunking working off the DSR mastec.
b. The RF sites (Eagle Mountain) would be off-line for both layers because of site
fai(u1•e, and therefore have reduced coverage,
2. If catastrophic failure happens at a different site with the relocated prime for layer O1:
a. Layer O1 would cease to opei•ate.
b. Layer 02 wot�ld continue to operate �vide-area thcottgh either the main Eagle
Mountain DSR oi• the CJC (CFW) DSR Master depending on whether Eagle is still on
line (Note if Layer O1 peime were tnoved to Rolling Hills and this site had
catast�•ophic failure — both layei•s would no longer fiinction si�lce both primes would
be at this location.).
c. If located at a current RF site location (6-sites) that have both layers on P25 atld
catastrophic fail��re occurred the layer O1 and layei• 02 RF sites at that location would
no longer function.
City of Fort Worth
Dynamic System Resiliency (DSR)
October 25, 2013
Use or disclosure of this proposal is subject
to the restrictions on the cover page.
Motorola Solutions Confidential Restricted Addendum A— BGA Questions and Answers 6-14
d. If Rolling Hills ��vel•e to have catasti•ophic failiu�e Layei• 02 would cease to ope�•ate
under the conditions of all of the above scenarios.
Any relocation of the pcime at Eagle will cause a cucrent system outage of Layer O 1 during
the move. Also:
a. Site moved to would have to have �dequate space power and air conditioning.
b. Tl ►napping of eveiy RF site and the new prime site would be requiced.
c. Two additional Tls would have to be added to the c�n•cent TI plan for the new links
that would have to be established between Eagle and new prime and between CJC
DSR and new prime.
City of Fort Worth
Dynamic System Resiliency (DSR)
October 25, 2013
Use or disclosure of this proposal is subject
to the restrictions on the cover page.
Motorola Solutions Confidential Restricted Addendum A— BGA Questions and Answers 6-15
i1�I&C Review
�� � � '� � �
Page 1 of 2
Official site of the City of Fort Worth, Texas
FORT�ORTI�
a � - , � _. ,�. ; ��� . �
�. _ � � � , _ 7< _ _ __ �
COUNCIL ACTION: Approved on 6/4/2013
�. , �. ,.�.� . ___� .,. .,. �r,,_ f... ... � _ . . � .s � u ��
DATE:
CODE:
6/4/2013 REFERENCE
NO..
C TYPE:
**G26278 LOG NAME:
CONSENT PUBLIC
HEARING:
04MOTOROLA SYSTEM
PURCHASE AGREEMENT
DSR
NO
SUBJECT: Authorize System Purchase Agreement with Motorola Solutions, Inc., in the Amount Up to
$982,254.00 and Upon Approval to Use Grant Funds by the State of Texas, Department of
Public Safety to Add Dynamic System Resiliency to the City of Fort Worth Public Safety
Radio Communications System Using a Cooperative Contract for the Information
Technology Solutions Department (ALL COUNCIL DISTRICTS)
� � .� . . � -.�� t. . _ _r t � .� .. �_ _ �. �� �w ... �. � ��._� . ti s: . �w_ . � __ . . ��
RECOMMENDATION:
It is recommended that the City Council authorize a System Purchase Agreement with Motorola
Solutions, Inc., in the amount up to $982,254.00 and upon approval to use grant funds by the State of
Texas, Department of Public Safety to add Dynamic System Resiliency to the City of Fort Worth
Public Safety Radio Communications System using Houston-Galveston Area Council Contract No.
RA05-12 for the Information Technology Solutions Department.
DISCUSSION:
The City of Fort Worth's Public Safety Radio Communications System provides primary radio
communications for the City's Police Department, Fire Department, and City Marshal. The system
also supports other City departments (Water, Transportation and Public Works, etc). Additionally, the
system provides primary communications for 14 surrounding jurisdictions and interoperable
communications to over 30 additional public safety organizations in the region.
The Dynamic System Resiliency (DSR) feature will enable the system to automatically maintain
critical radio system communications in the event of catastrophic component failure.
On June 14, 2011, the City Council approved M&C G-17303 authorizing execution of a System
Purchase Agreement with Motorola Solutions, Inc., for the upgrade of the City's public safety radio
communications system. The DSR feature is an additional feature for this system that is funded by
the Urban Area Security Initiative (UASI) grant program.
On November 11, 2012, the City Council approved M&C C-25968 accepting UASI grant funds to pay
for programs to maintain and enhance local capabilities to prepare for, prevent, respond to and
recover from acts of terrorism and natural disasters. Upon approval from Department of Public
Safety (DPS), these grant funds will be used to pay for services under this Agreement. In order to
meet deadlines for completion of the project, Staff recommends execution of this Agreement as soon
as possible. Staff anticipates project approval by DPS in June 2013.
COOPERATIVE PURCHASE - State law provides that a local government purchasing an item under
a Cooperative Purchasing Agreement satisfies any state law requiring that the local government seek
competitive bids for purchase of the item. Houston-Galveston Area Council (HGAC) contracts were
competitively bid to increase and simplify the purchasing power of government entities.
M/WBE OFFICE - A waiver of the goal for MBE/SBE subcontracting requirements was requested by
http://apps.cfwnet.org/council�acket/mc_review.asp?ID=18460&councildate=6/4/2013 1 / 16/2014
�IVI&C Review
Page 2 of 2
the Department and approved by the M/WBE Office, in accordance with the BDE Ordinance, because
tne purchase of goods or services is from source(s) where subcontracting or supplier opportunities
' are negligible.
ADMINISTRATIVE CHANGE ORDER - An Administrative Change Order or increase may be made
by the City Manager for this System Purchase Agreement in the amount up to $50,000.00 and does
not require specific City Council approval as long as sufficient funds have been appropriated.
FISCAL INFORMATION/CERTIFICATION:
The Financial Management Services Director certifies that funds are available in the current capital
budgets, as appropriated, of the Grants Fund and the Information Systems Capital Project Fund.
TO Fund/AccountlCenters
FROM Fund/Account/Centers
GR76 539120 004442581050 $795,587.00
P251 539120 041030173520 $186,667.00
Submitted for Citv Manager's Office by:
Originating Department Head:
Additional Information Contact:
ATTACHMENTS
Susan Alanis (8180)
Peter Anderson (8781)
Steve Streiffert (2221)
Alan Girton (8484)
http://apps. cfwnet. org/council�acicet/mc_review. asp?ID=18460&councildate=6/4/2013 1/ 16/2014