Loading...
The URL can be used to link to this page
Your browser does not support the video tag.
Home
My WebLink
About
Contract 41910-A7
CITY SECRETARY CONTRACT No. lj/q /0 ,. ~Cl AMENDMENT NO. 7 TO CITY SECRETARY CONTRACT NO. 41910 SYSTEM PURCHASE AGREEMENT BETWEEN CITY OF FORT WORTH AND MOTOROLA SOLUTIONS INC. This Amendment No . 7 ("Amendment") to City Secretary Contract No. 4191 O System Purchase Agreement ("Agreement"), is made and entered into by and between the C ity 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 Alan is, its duly authorized Ass istant City Manager, and Motorola Solutions , Inc., ("Consultan t"), acting by and through Dan Delaney its duly authorized MSSI Vice President , collectively referred to as the "Parties." RECITALS The follow ing provisions are true and correct and form the basis of this Amendment: WHEREAS , on or about June 14 , 2011 , the parties entered into a System Purchase Agreement ("Agreement") to purchase a P25 Radio Communication Syst em . The Agreement is a public document on file in the City 's Secretary Office and referenced as City Secretary Contract No. ("CSC ") 41910 ; and WHEREAS, on or about May 23 , 2012 , the parties subsequently amended the Agreement via CSC No . 41910-A 1, to incorporate changes agreed to during the Des ign Review and in accordance with the Agreement , to modify pricing structure , system description , scope of services , acceptance testing, equ ipment , L TE services , and other items as deemed necessary and agreed to by the Parties ; and further amended the agreement on or about May , 23 , 2012 , via CSC No . 4191 O-A2 , to extend the pric ing provision and modify provis ions for equipment storage; and further amended the Agreement on or about August 1, 20 12, via CSC No . 41910- A-3 to incorporate changes in the Ast ra Repeater (ARS) site location from Texas Motor Speedway ("TMS ") to American Tower Corporation Roanoke Site ("Roanoke ATC "); and further amended the Agreement on or about January 25 , 2013, via CSC No. 41910 -A -4 to incorporate changes for subscriber hardware and installations , training , and wo rk at radio sites deemed necessary and agreed to by the Parties ; and further amended the Agreement on or abou t Apr il 26, 2013 , via CSC No . 4191 O-A-5 to incorporate changes in design , equipment, and installation for work at Burnett Plaza Site , Roanoke Site , Bergh 2 site , and Eagle Mountain Site ; and further amended the Agreement on or about August 20 , 2013 , via CSC No . 41910-A6 to incorporate changes in des ign , equipment, installation and work at Burnett Plaza Site , Eagle Mountain Site , Rolling Hills Site , North Beach Site , Roanoke Site , Bergh Site , Bolt Street Site , and Westland 6 Site. CSC Nos . 41910 , 41910-A1 , 41910-A2 , 41910-A3 , 41910-A4 , 41910-A5 and 41910-A6 are hereby collectively referred to as the ("Agreement"); and WHEREAS , the Parties now wish to amend the agreement to incorporate changes in des ign , equipment , installation and implementation of Public Safety Long Term Evolution (PS L TE) CFW / MOTOROLA Amendment No . 7 to CSC No. 41910 Page 1 RECEIVED SEP 1 5 2014 OFFICIAL RECORD CITY SECRETARY FT, WORTH, TX Radio Access Network (RAN) and Remote Agency Co re/Gateway connected to and su pported by the Harris County, TX Evolved Packet Core (EPC); including Aeroflex Service Monitor and DiagnostX Tool. NOW, THEREFORE , for good and valuable consideration , the receipt and adequacy of wh ich are hereby acknowledged, the City and Consultant agree as follows : 1 . The agreement shall be modified to incorporate changes in design , equipment, installation and implementation as agreed to by the Parties set forth herein and in Exhibit "A ," Change Order No . 7 and the attached documents , including the Section 4. Acceptance Test Plan December 20 , 2013 ; Section 1A. Acceptance Test Plan (Failure Modes) December 20, 2013 ; Addendum 1 Public Safety PS L TE System December 20 , 2013 ; the Change Order 7 Pricing Summary, and Exhibit E-4 Maintenance Statement of Work for Support, all of which are attached hereto or incorporated by reference and hereby made part of this Agreement. 2 . All other provisions of the Agreement that are not expressly amended herein shall remain in full force and eff'Jf1· Executed on this the ~ay of ~ , 2014 . CITY OF FORT WORTH: Sus n Alanis 1stant City Manager Date 1ll 2\ ~14 ATTEST: CFW / MOTORO LA Amendment No . 7 t o CSC No. 4 1910 Page 2 MOTOROLA SOLUTIONS, INC .: OFFICIAL RECORD CITY SECRETARY FT. WORTH, TX APPROVED AS TO FORM AND LEGALITY: By~ Maiesti; armer Senior Assistant City Attorney Contract Authorization: M&C G-17303 Date Approved : June 14 , 2011 CFW / MOTOROLA Amendment No . 7 to CSC No . 41910 Pag e 3 ' ' , M &C R ev iew Page 1 of 3 Official site of the City of Fort Worth, Texas CITY COUNCIL AGENDA DATE: CODE: COUNCIL ACTION: Approved on 6/14/2011 -19735-06-2011 6/14/2011 G REFERENCE NO.: G-17303 LOG NAME: TYPE: PUBLIC NON-CONSENT HEARING: FORT \Vi)RTI I ~ 13TAX NOTES 11 NO SUBJECT: Approve One-Time Exception to the Financial Management Policy Statements to Allow the Use of Debt Structures Involving Balloon Payments for the Sole Purpose of Financing the Upgrade to the City's Public Safety and Public Works Radio Communications System Via Tax Notes , Adopt Ordinance Authorizing Issuance of Tax Notes in the Principal Amount of $43,050 ,000.00, Approving the Sale of the Notes to JP Morgan Chase , Providing for the Levy , Assessment and Collection of a Tax Sufficient to Pay the Interest on Said Notes , Create a Sinking Fund for the Payment of the Principal Thereof and Ordaining Other Matters Related Thereto , Authorize Execution of a System Purchase Agreement in the Amount Not to Exceed $39,345 ,641 .55 with Motorola Solutions , Inc ., for Equipment and Professional Services Using a Houston-Galveston Area Contract, and Authorize Execution of Amendment No. 2 to City Secretary Contract No. 40264 with Buford Goff & Associates to Provide Engineering and Quality Assurance Services in the Amount Not to Exceed $2 ,900 ,000 .00 RECOMMENDATION: It is recommended that the City Council : 1. Approve a one-time exception to the Financial Management Policy Statements to allow the use of debt structures involving balloon payments for the sole purpose of financing the upgrade to the City's Public Safety and Public Works radio communications system via Tax Notes ; 2 . Adopt the attached ordinance authorizing the issuance of Tax Notes in the principal amount of $43 ,050,000 .00 , approving the sale of the notes to JP Morgan Chase; providing for the levy , assessment and collection of a tax sufficient to pay the interest on said notes and to create a sinking fund for the payment of the principal thereof and ordaining other matters related thereto ; 3 . Authorize execution of a system purchase agreement in the amount not to exceed $39 ,345 ,641 .55 with Motorola Solutions , Inc ., for equipment and professional services using Houston-Galveston Area Contract number RA01-08; and 4 . Authorize execution of Amendment No . 2 to City Secretary Contract No . 40264 with Buford Goff & Associates to provide engineering and quality assurance services in the amount not to exceed $2 ,900 ,000.00. DISCUSSION: If approved , this M&C will approve a one-time exception to the Financial Management Policy Statements (FMPS) regarding debt structures with balloon payments , authorize the issuance and sale of Tax Notes to JP Morgan Chase in order to fund the project to upgrade the City 's public safety and public works radio communications system instead of using the lease-purchase agreement previously approved , and authorize the execution of the related purchase and services agreements . The FMPS , adopted by the City Council on December 14, 2010 , prohibits balloon debt repayment schedules which consist of low annual payments and one large payment of the balance due at the end of the term . However, due to a unique combination of circumstances , including rare market conditions , financing restrictions , and the urgency of the project to ensure continued maximum public safety , staff is seeking a one -time exception to the policy for the sole purpose of funding this long -term project v ia Tax Notes which have a maximum life of seven years. The principal pay-down schedule would mirror a http://apps.cfwnet.org/council_packet/mc _review.asp ?ID = 15442&councildate=6/1 4/2011 9/10 /2014 ... M&C R ev iew Page 2 of 3 standard 10-year issue for the first six years , thus avoiding the spirit of typical balloon-payment financing . It is anticipated that the Tax Notes will be refunded pr ior to final maturity to accomplish proper amortization periods . On May 17 , 2011 , (M&C P-11234 revised) the City Council approved the acquisition of hardware , software and services to upgrade the City's public safety and public works radio communications system . On this same M&C , the staff recommendation was to fund this project via a lease-purchase agreement w ith Motorola . On today 's Agenda is M&C G-17302 for separate consideration as staffs recommendation to rescind that authorization and repeal the related ordinances . Because of current market conditions , the City can finance this project quickly via Tax Notes , resulting in a projected savings of approximately $500 ,000 .00 annually over the lease-purchase cost. Although the method of financing is transferring from lease-purchase to financed purchase , the General Fund will continue to be the source of repayment. The upgrade to a current generation digital system will more effectively meet the requirements of first responders , and fulfills state and federal objectives for interoperability amongst the region's similar agencies . This system will replace the City's current system acquired in 1992 , which is no longer supported by the manufacturer. On September 16 , 2008 , M&C C-23055 was approved , autho rizing Buford Goff and Associates , Inc ., (BGA) to perform an assessment of the public safety radio system . In March 2009 , BGA presented a report that key components of the system had reached end of their life expectancy , were no longer supported by the manufacturer and could suffer failures when taxed by emergencies and increased traffic . In light of these factors , the City was encouraged to act as soon as possible . On May 18 , 2010 , City Council approved M&C C-24221 authorizing BGA to develop a master plan for the City to upgrade its radio systems , and negotiate a competitively-priced agreement with the C ity's communications provider , Motorola Solutions , Inc . The master plan reinforced the urgency of the 2009 study . Given the current fragile state of the system , increasing serv ice outages , the unavailability of replacement parts , and the financial challenges the C ity is facing , the Master Plan attempted to balance these factors and ensure a stable , reliable and secure communicat ions infrastructure for Police , Fire , Water, Transportation and Public Works , Parks and Community Service and other City departments . On June 15 , 2010 , M&C C-24272 was approved to authorize the acqu isition of the Project 25 (P25) standard master switch , or the core , of a current generation radio system along with one small site to operate as a potential backup to the existing system . The plan proposed by BGA and Motorola Solutions , Inc ., builds upon the installation of this master switch and the initial site . Because of the magnitude of this project , the full build-out and m igration is expected to require almost 48 months to complete . Assuming contract execution in July 2011 , the project would be scheduled for completion in the first quarter of 2015 . The total cost of the project is estimated not to exceed $53 ,000 ,000 .00 . This total includes $39 ,345 ,641 .55 for hardware , software and services acquired through the System Purchase Agreement with Motorola Solutions , Inc .; $2 ,900 ,000 .00 for engineering , consulting , and other professional se rvices from BGA through March 2015 ; and additional costs for project management and site construction . Additional M&Cs will be submitted to the City Council for approval of these other project costs as necessary . Staff recommends execution of the System Purchase Agreement with Motorola Solutions . Under this agreement , the system implemented will include expanded coverage areas , specifically in west Fort Worth and at Texas Motor Speedway , and it will provide additional security features which will help prevent unauthorized monitoring of public safety communications transmissions. Public works personnel will also utlize a segment of th is system , and if a significant event occurs , public safety personnel will have access to the public works portion as well. Ongo ing support capabilities wil l be enhanced through 7x24 monitoring and dispatch by Motorola's network operations center. Staff also recommends execution of Amendment No . 2 to City Secretary Contract No . 40264 with Buford Goff & Associates for the provision of engineering , consulting and other professional se rvices through March 2015. These services will include detailed work regard ing system design reviews , frequency licensing , acceptance testing and other critical program functions . Staff is continuing to explore cooperative measures with other agencies for potential cost sharing and joint participation . This project is structured in such a way to enable such measures if they are realized in the future . It is anticipated that the Crime Control and Prevention District (CCPD ) will transfer funds , at a future http ://apps .cfwnet.org/council_packet/mc _review.asp?ID = 15442&councildate=6/14 /2011 9/10 /2014 ~ · ,-N&C R eview P age 3 of 3 date via M&C , to offset a portion of the total cost and provide a funding source for the Fiscal Year 2012 debt service payment. Additionally, it is anticipated that the City Manger's Proposed Budget will include General Fund debt service transfers beginning in Fiscal Year 2013 . PRICE ANALYSIS -The HGAC contract offers fixed discounts ranging from five percent to 25 percent, which remain unchanged from the previous purchase Agreement approved by City Council on March 18 , 2008 , M&C P-10750. Staff reviewed the pricing and determined it to be fair and reasonable . 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 . The Houston-Galveston Area Council contract was competitively bid to increase and simplify the purchasing power of government entities . M/WBE -Buford Goff and Associates , Inc., agrees to maintain its initial M/WBE commitment of five percent that it made on the original agreement and extend and maintain that same M/WBE commitment of five percent to this Amendment No. 2 . Therefore Buford Goff and Associates , Inc ., remains in compliance with the City's M/WBE Ordinance and attests to its commitment by its signature on the Acceptance of Previous M/WBE Commitment form executed by an authorized representative of its company . A waiver of the goal for M/WBE subcontracting requirements for Motorola Solutions , Inc ., was approved by the M/WBE Office because the purchase of goods or services is from sources where subcontracting or supplier opportunities are negligible . FISCAL INFORMATION/CERTIFICATION: The Financial Management Services Director certifies that funds will be available upon completion of the sale , closing and delivery of approximately $43 ,050 ,000 .00 City of Fort Worth , Texas , Tax Notes , Series 2011 . The Financial Management Services Director also certifies that funds will be available to make the debt service payments on these obligations , and funds will be available in the General Fund , as appropriated , to satisfy the City 's obligations . TO Fund/Account/Centers Submitted for City Manager's Office by: Originating Department Head: Additional Information Contact: ATTACHMENTS note ord draft 060611 .doc FROM Fund/Account/Centers Karen Montgomery (6222) Lena Ellis (8517 ) James Mauldin (2438) h ttp:// a p ps. cfwnet. org/ counc i 1 _packet/me _review .asp ?ID= 1544 2&councildate=6/ 14/20 1 1 9/10/2 01 4 I .• MOTOROLA SOLUTIONS EX HI BIT "A" Ch a nge Order No. 7 CHANGE ORDER ---------------------- 0 ate: Feb ru arv 12, 20 14 Project Name: Fort Worth P25 Upgrade Project -TX-10l192A Customer Name: City of Fort Worth Cu sto mer Proj ect Mgr: Alan Girton ---------------------- The purpose of this Change Order is to: 1. Update the L TE Addendum 1 to cla r ify software ve rsions to be implemented 2 . Update the Functional Acceptance Test Plan w ith agreed changes in test execution steps 3. Provide 1 Diagnost ix tool 4. Provide 1 Aeroflex Service Monitor 5 . Provide 180 NNTN8092A Li Ion Batteries 6. Prov ide 42 NN T N7 0658 Mu ltichargers Contract# City of Fort Worth : Contract 41910 Motorola Solutions Contract: 11-11006/DL Contract Date: 6/23/11 In accordance with the te rms and conditions of the contract identified above between the City of Fort Worth and Motorola Solutions , Inc., the follo w ing changes are approved : Contract Pri ce Adjustments Original Contract Value: $39 ,345 ,641 .55 Previous Change Order amoun ts for Change Orde r numbers [o----1 through [i. j No Price Adjustments This Change Order: New Contract Value : Completion Date Adjustments Original Completion Date: Current Completion Date prio r to this Change Order: New Completion Date : Change~ to System Purchase Agreement (SPA) Provisions: Decrease project credit from $2 ,472,343 .28 to $2 ,318 ,602 .19 . Total credit used with this change order is $153,741.09 $39,345,641 .55 12/31/2014 2/28/2015 NIA T here are no changes to the Sys tem Pu rchase Agreement (SPA) Pro v isio ns wi th this change orde r . Changes in Equipment: The equipment changes are identified in the following att achmen t, which is inco rp orated into th is Change Order by this reference 1. Change Ordef'7 Pricing Summ ary -dated Februa ry 12 , 2 01 4 Fort W orth P25 Upg rad e Project Page 1 of 2 . 0 MOTOROLA SOLUTIONS CHANGE ORDER Changes in Services: The changes in services are identified in the following updated sections. These sections replace in their entirety the current corresponding sections of the Agreement: 1. Change Order 7 L TE Addendum 1 -dated December 20, 2013 2. Change Order. 7 -Acceptance Test Plan -dated December 20, 2013 3 . Change Order 7 -Acceptance Test Plan RVTM -dated December 20, 2013 Schedule Chan es: There are no schedule changes with this Change Order. Pricing Changes: I The Price of the contract is not altered with this Change Order. As a result of this change order, the outstanding project purchasing credit remaining available for the City of Fort Worth is reduced from , $2,472,343.28 to $2 ,318,602.19. Tota! credit used with this change order is $153,741.09 . I Warranty Chan es: There are no warranty changes with this Change Order. I Customer Res onsibilities: There are no changes to customer responsibilities with this Change Order. Payment Schedule Changes: There are no Payment Schedule changes with this Change Order. 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: t-'7-f'-( Mo ala olutlsPojectanager Fort Worth P25 Upgrade Project Page 2 of 2 4. 1 Introduction The functional acceptance plan for the City of Fort Worth System will take place in several steps. This process assumes that the Master Site having been purchased will be installed and operation in the field before Phases 2 and 3 will anive at Motorola's CCSi. The City is responsible to lease Tls to CCSi to connect between the Master Site Motorola will perform all the tests listed under sections 4.2 (Phase 2) and 4.3 (phase 3) at CCSi. The Tls required for this test will be: 1. 2 Tls from the Master Site to CCSi for the Eagle Mountain Prime Site which will be at CCSi. 2. 2 Tls from the Master Site to CCSi for the Prime Site at Rolling Hills Prime Site which will be at CCSi. 3. 2 Tls from the Master Site to CCSi for the Bolt Street Dispatch Center located at CCSi. 4. 2 Tl s from the Master Site to CC Si for the Alternate Dispatch Center located at CCSi. 5. 1 Tl from the CEN LAN at CCSi for the KMF/Network equipment at the two dispatch centers and the radio shop that will be at CCSi. 6. Note the Tl from number 5 above will also be used for demonstration of OTAP and Moscad terminal testing. Additional Master site equipment for Phases 2 & 3 and software upgrades for these two Phases will be sent to the field, and implemented by the field team before the CCSi tests may be performed. CCSi will further rack and stack all equipment for the RF sites , and prime site subsystems. Therefore the tests under Sections 4.2 (Phase 2) and Section 4.3 (phase 3) would performed in CCSi and then as a final functional test in the field. Motorola Confidential Restricted Use or disclosure of this proposal is subject to the restrictions on the title page City of Fort Worth, Texas ASTRO 25 Migration , Citywide Trunked Radio System December 20 , 2013 Acceptan ce Test Plan 4-1 Once the equipment for Phase 2 has been installed and optimized in the field, the Phase 2 tests will be performed. Once the equipment for Phase 3 has been installed and optimized, the entire Phase 3 test script in Section 4 .3 will be performed. This may be based on a limited number of channel resources being available at this final test due to channel implementation issues at the time of this final test. Those channels not available for the FA TP at the time of the final test, will be tested at some point during the final FA TP on dummy loads and then shut off until they may be implemented. Addendum: Note: The following paragraphs include updates provided on December 20, 2013 as part of Change Order 7. On November 22, 2013 the FATP was reviewed by the City and Motorola Solutions. Since the initial design of the system, and the creation of the F ATP before the initial set of tests were done in CC Si, several changes have been made to the system design. The effect of these design changes, and the fact that several tests were originally created with system features which eventually did not become part of the final system design, necessitated certain changes to the F ATP. Further, it was noted that one test required four system sites to be active, and that certain tests remaining were redundant. Three tests in the original document were found to be duplicates of other tests in the document. These were earlier versions of the same three tests and needed to be removed from the Phase 3 test procedure. Also , to prevent critical system outages on a live radio system, it was determined before the Phase 2 testing that some Phase 3 tests needed to be performed during Phase 2 testing. Therefore, the F ATP includes the following changes from previous versions, and have been reviewed and agreed by both the City of Fort W01ih (under the review of BGA) and Motorola: 1. Tests that were performed during Phase 2 on 10/9/2012 have a grey background added and have a note above the Pass/Fall line that states: "This test was performed and passed during Phase 2 testing on 10/09/2013" 2. Tests related to the Smart X system implementation have been removed from the FA TP since Smart X was removed from the system design by an earlier change order. 3. Tests related to "Text Messaging" features which were not in the final system design were removed. City of Fort Worth, Texas ASTRO 25 Migration , Citywide Trunked Radio System December 20 , 2013 4-2 Acceptance Test Plan Motorola Confidential Restricted Use or disclosure of this proposal is subject to the restrictions on the title page 4. The test requiring 4 system sites has been changed to show the need for 2 system sites. Note, this change does not impact validity of the test. 5. Three tests that were duplicates in the original Phase 3 section were removed, including: a. Key Management Facility (KMF) -Store & Forward to MCC 7500 b. Key Management Facility (KMF) -Create MCC 7500 c. KMF MCC7500 Conso le Summary Report Motorola Confidential Restricted Us e or disclosure of this proposal is subject to the restrictions on the title page City of Fort Worth, Texas ASTRO 25 Migration, Cit ywide Trunked Radio System December 20 ,.2013 Acceptance Test Plan 4-3 4.2 Phase 2 ~. DESCRIP'rlO SEflJ,A .__ _____ _ RADIO-~ -TALKGROUP 1 RADIO-~ -SITE -Sl 'fE 1 RAiDI0-2 -TALKGR@UP 1 RADll0-2 -SITE -SITE ~ RADI0 -3 -TALKGRGlJP 2 RADI0-3 -SITE -SITc ~ RADI0-4 -TAL:KGROUP ~ RADI0-4 -SITE -SITE ~ VeRSION #1.~40 Motorola Confidential Re stricted Use or disclosure of this proposal is subject t o the restrictions on the tit le page 2. lESili ,L._,-~-,.._,·-~-~~..,....,..--~--. §teR 1. Initiate a wicie area call with RADI 0-1 in TALKGROUP 1. =----! ... ....,,...,~..,.,....---~--Observe that only RAQI0-2 will be able ta monitor and respond to the call. , __ _ Initiate a wide area call with RADI0-3 in .....,. ........ ,......,,..if ALKGROUP 2 . .,._,....,___,._,_ ...... ___ ..,.., his test was performed and passed durin,g [E_hase ~ testing 9].l_LQ /09/2012. Pass ___ Fail __ City of Fort Worth , Texas ASTRO 25 Migration , Citywide Tru nked Radio Syste m De cemb er 20,.2013 Acceptance Test Plan 4-5 Wide Area Trunking -FDMA Onl~ Sites 1. DESCRIPTION ----~--This trunking feature allows an equipped radio user to transmit an announcement to severa different talkgroups simultaneously. Th multigroup (MG) call can be flagged for ... ln-te-r-ru-p~ Mode in the User Configuration Manager (UCMJ database , this means that the trunked syste does not wait for attached talkgroups to finis h calls in progress . Upon dekeying , the interrupte radios will join the multigroup call in progress. As with other types of calls , multigroup calls ca o take place from an ~here in the ~Y~!~D1., NOTE : A receiver interference failure ma~ appear if RADI0-1 is not immediately dekeyed rJ"his test is not recommended for single sit§ §ystems as RF cont~ntion will occur. SETU R RADI0-1 -TALKGROUP 1 RADI0-1 -SITE -SITE 1 RADI0-2 -TALKGROUP 2 RADI0-2 -SlliE -SITE 1 RADI0-3 -RANDOM (No .... t.~-- RADI0-3 -SITE -SITE 2, RADI0-4 -ATG 1 RADI0-4 -SITE -SITE 2 * RANDOM is any talkgm up not a member of ATG 1. * Multigroups are set up through both the UCM and the Subscriber Prog camming software . City of Fort Worth , Tex as ASTRO 25 Migration, Citywide Trunked Rad io System December 20, 2013 4-6 Accepta nce Test Plan 2.TESli Step 1. Verify ATG 1 is set for the in the UCM database. Ste 2. Using RADI0-1 , initiate a call o TALKGROUP 1 . .._,,__ __ This test was performed and p ass_e d during Ph ase 2 testing on 10/09/2 01 2.1 Pass Fail __ Motorol a Confid e nti al Res t ric ted Use or disclosure of this proposal is subject to the restrictions on the tit le page Call in Wait Mede (Sing!g * T ALKGROUP 1 TALKGROUP 2 are members of ATG 1. * ~NDOM is any ta lkgrou i:2 not a member o1i ~ifG 1 . "'Multigroups are set up through both the UCM eD.9 the Subscri ber Programming software. WERSION #1.040 Motorol a Confid e nti al Restric ted Use or disclosu re of th is proposal is subject to the restrictions on the title page ~-TEST! fil§R 1 . VL.e-r-ify_A_T_G"""'""1 .,..is-s-e"""t..,,fo_r_t~h-e "'w77"'ai:-:-t -m~o~d:-e"7'.in' --~~~t_He UCM database . .._~--... §..,§R 2. Using RAgl0-1 , initiate a call o n irALKGROLlP 1 . .__ ____ .., S -te_P._3 __ ,,-W .... hile RADI0-1 is keyed , attempt to initiate a multigroup call using RAGI0-4 p n A ifG 1. Verify RAl2ll0-4 receiYes. a busy tone because Gne of the._ __ _ r a !kgroups attached to ATG 1 is invelved j n a T alkgroup Cal l....._ __ ,---__,,......,, ~-e[)-_ -4-. -K'""'e'y RADIG-2 and ve r ify that a busy ten is received because the ATG 1 call is in IT'hi s test was performed and passed during Ph ase 2 testing on 10/09/20 12. f!!ss __ F-ail __ City of Fo rt Worth , Texas ASTRO 25 Migration , C itywide Trunked Radio Syste m December 20,.2013 Acce ptance Test Plan 4 -7 Wide Area Trunking -FDMA Only Sites Recent User Priority 1. DESCRIPTION This test verifies that a recent user of the channel has priority over other users of equal priority of being assigned a channel when a busy queue exi sts . The maximum number of consecutive times that a user may be elevated to recent user priority is two. SETUP RADI0-1 -TALKGROUP 1 RADI0-1 -SITE -SITE 1 RADI0-2 -TALKGROUP 2 RADI0-2 -SITE -SITE 1 RADI0-3 -TALKGROUP 3 RADI0-3 -SITE -SITE 1 VERSION #1.220 City of Fort Worth , Texas ASTRO 25 Mig rati on, Ci tyw ide Trun ked Radio System December 20, 2013 4-8 Acceptance Test Plan 2. TEST Step 1. Ensure that the priority level for all talkgroups is the same. Simulate a busy system by disabling all channels at SITE 1 with the ex ception of the control channel and one voice channel. Step 2. Press and hold the PTT switch of RADI0- 1. Step 3. Press and hold the PTT switch on RADI0- 2 and then press and hold the PTT switch on RADI0-3 . Verify that both radios receive a busy tone. Step 4 . Release the PTT switches on RADI0-2 and RADI0-3. Step 5. Release the PTT switch on RADI0-1. Step 6 . As soon as RADI0-2 receives its callback tone , press and hold its PTT switch. Step 7. Within 2 seconds of callback , re-key RADI0-1. Verify that RADI0-1 receives a busy tone . Release the PTT switch on RADI0-1. Step 8. Release the PTT switch on RADI0-2. Verify that RADI0-1 receives a callback tone before RADI0-3 . Step 9. Repeat Steps 2-8 . Verify that the priority of RADI0-1 is once more elevated in the busy queue . Step 10 . Repeat Steps 2-8 once more. Verify that in Step 9 that RADI0-3 receives the callback tone since RADI0- 1 cannot be elevated in the busy queue more than two consecutive times . Pass __ Fail Motorola Confidential Restricted Use or disclosu re of thi s proposal is s ubject t o the restrictions on the titl e page Wide Are~ TrL.:Jnking -FDMA Qnl~ 1Sites MERS.ION #1.06 Motorola Confidential Restricted Use or disclosure of thi s proposa l is subject to the restrictions on the title page fl>a ss ___ ""F_,.;;a=i'-'I '-----' City of Fort Worth , Texas ASTRO 25 Mi gration , Citywide Trun ked Radio System December 20,.2013 Acceptance Test Plan 4-9 Wide Area Trunking -FDMA Ont ~ Sites Call Alert Single Site} 1. DESCRIPTIO N ..... -~-,c-----~ Call Alert is a tone page that allows a user to selectively alert another radio unit. The initiatin g radio will receive notification from the trunke system as to whether or not the page was received by the target radio . Units receiving a Call Alert will sound an alert tone . As with othe r, types of calls , Call Alerts can take Qlace from anywhere in the system . SETUP. -~~-....,....--...-, RADI0-1 -TALKGROUP 1 RADI0-1 -SITE -SITE 1 RADI0-2 -TALKGROUP 2 RADI0-2 -SITE -SITE 1 RADI0-3 -TALKGROUP 2 RADI0 -3 -SITE -SITE 1 VERSION #1.05 0 Ci t y of Fort Worth , Texas ASTRO 25 Mi g rat ion, Citywi de Trunked Ra di o System Decem ber 20, 20 13 4-10 A cce ptance T es t Plan 2.TES~L--~~~-,--~~~~-:--:~ Step 1. Using RADI0-1 , press the page button. Ste p 2. Ente r the unit ID of RADI0-2 with the keypad , or scroll to the location where this ID is store 1 Step 3. Press the PTT to initiate the call ale rt (Page). Verify that the RADI0-1 use n receives audible indication that the Cal · lert (Page) was sent ..__ ___ _ __ .,.. Ste 4. Ver ify that RADI0-2 user receives an audible ind ication of an incoming Cal ~lert (Page was sent but RADI0-3 aoes no t. i........------,--.--,--:-:--. ..... Step 5. Verify RADI0-1 gets an audible indication that the Call Alert (Page) was..__ __ _ successfully received at the target radio . §tep 6. Turn off RADI0-2 . Send a Call Alen (Page) from RADI0-1 to RADI0-2 Ste R 7. Verify that the RADI0-1 user receives audible ind ication tha t e Call Ale , (Page) was sent...._ ______ .,....., Step 8. Verify RADI0-1 receives an ind icafo tha the Call Alert (Page) was no t.__ __ _ successfull y received at t e ta get adio This test was performed and passed during Phase 2 testing on 10/09 /20 12 . Pass __ Fail __ Mo to rol a Co nfi denti al Restricted Use or di sc losure of t hi s propo s al is su bj ect t o t he res tri cti o ns o n th e titl e page Wide Area Trunking -FDMA Gnl~ Site Private Call (Single Site} ~. Dl:SCRIPTION "----------.....,......, P~ivate Call is a selective calling feature that allows a dispatcner or radio user to carry on one-to-one conversation that is only heard b)I tne 2 parties involved. Sub$criber units receiving a private call will sound an alert tone. As with other types of calls, Private Calls can take P.lac e, from an Y.}!Y here i t e s ste smliUF! --~-~---. RADI0-1 -TALKGFZOUP 1 RADIO-~ -S1T6 -SITE 1 RADI0-2 -TALK.GROU~ RADI Q)-2 -Sl-rE -SI T !i 1 RADI0-3 -ifAlKGF-{OU!e' 2 RADIQ -3 -Sl "Jj E -SPrE i VERSIQN #1.08Q Motorol a Confide nt ial Res t ric ted Use or disclosu re of this proposa l is subject to the restr ictio ns on the title page 2. "JilsS li --~......,... ........ ~~-----=~~= ~12 1. Using RAQI0-1 g ress the PJ ivate Call (Call) buttori .. "" -...,,....-.,.---.-~--.. p--te_,p_ _ _?_-'--_-E..,.,nter the unit ID of RADI0-2 with the keypad, Gr sGroll to the location where t his ID is storec!. -=-e---s:::-"----~~--<"""":'l ~12 3. _p ress the PTT to init iate the Private Call ___ __,.(Call)."-'--------~~ ~f.'l 4 . Verify that RADI0-2 hears tones and the cli splay indicates that a Priva te Cal (Call) has been received but RADI0-3 receives no indications ----,-..,_,,_.....,.~~~ ~l::l 5. Answer the Private Gall (Call) at RADIQ-~ by pressing tbe Private Call (Call buttGn . If RADI0-2 has a display, verifM it shows the ID numt;ier or alias ofi RAIJI0-1. -~,---=· ......... -~------...., Ste [il 6. Press the PTT switch on RADI0-2 an respond to the Private Call (Call). N0te fhat if you do not press the Private Cal (Call) l::iutton before pressing PTT, you audio will be heard by all members of the talkgroup, and not Just by the rad·q initiating the f'rivate Call (Call) ----~te 7 . Verify that RADI0-2 cafl communicate with RADI0-1 . ....,,,,,_,...,__ ,;-._,-.-,-.---.-~"7!"""~'""1 ~12 8. Verify that RADI0-3 aoes not monitor tne Private Call (Call) . ....,..___...------,-~ -~l,,_e _P. -9.-E"'""nd the Private Call (Call) by pressing th Rrivate Call (Call) button or the flome · button to return to norma tal grou g ,g_g eration- hi s test was p erformed and passed during iPhase 2 testing on 10/09 /2 01 2 . ~ass __ Fal l __ City of Fort Wo rt h, Tex as ASTRO 25 Migrat ion , Cityw ide Trunked Rad io System Decemb er 20 ,.2 0 13 Acceptan ce Test Plan 4-11 Wide Area Trunking -FDMA Onl ~ Sites Emergency Alarm and Call wit TalkgrouQ Revert (Single Site , 1. DESCRIPTION Users in life threatening situations can use the Emergency button on the radio to immediatel YI send a signal to the dispatcher and be ass igne d the next available voice channel. An Emergency Call can be set to either Top of Queue o n ---..... Ruthless Preemption operation . This test verifies the Emergency ID will appear on the dis lay of the subscribers. To accomplish this , a ........ _ ___, Emergency Alarm and Call will be initiated from a portable wh ich will be received by a portable affiliated at an site of an y zone in the system . A portable has the ability to revert to a specific talkgroup when an emergency is initiated . Th is is useful when the users have a designate ' talkgrou Q for handling emergencies The revert talkgrou P. must be set in the ortah!§ via software. NOTE : If the subscriber does not have the PTTI Display OP.tion the Emergency ID will not be dis Qlayed . SETUR -~ RADI0-1 -TALKGROUP 1 RADI0 -1 -SITE -SITE 1 RADI0-2 -TALKGROUP 1 RAD I0 -2 -SITE -SITE 1 RADI0-3 -EMERGENCY TG' RADI0-3 -SITE -SITE 1 * EMERGENCY TG is the talkgrou A programmed for emerge ncy revert . VERSION #1.049 Ci t y of Fort W orth , Texas ASTRO 25 Mig rati on, Ci tywide Trun ked Rad io System December 20, 2013 4-1 2 Accept ance T est Pl an 2.TESi1 ·~-~~-----~-::-:--=:::-:-1 ?teP. 1. Make a Talkgroup Call from RADI0-1 and verify only RADI0-2 can hear the aud io. Step 2 . Dekey RADI0-1 .__ _____ .....,~, Ste P. 3. Using RADI0-1 send an Emergency Cal by depressing the emergenc switc and then the PTT switch ·~---' "-~~---Ste12 4. **For radios with displays only ** Observe the display on RADI0-3 denotes a emergency and the unit ID or alias of the unit sending the emergency and thaf RADI0-3 can hear RADI0-1's aud io. s·~t-e_P._5-. -1-n addition observe that RADI0-2 can no t hear RADI0-1's audio SteP. 6. Release the PTT switch 011 RADI0-1 an cancel thee ergency . This test was performed and passed dru,:ing Ph ase 2 testing on 10/09/20 12. Pass __ F~_i! __ Mot oro la Confid e nti al Rest ri cted Use or di sclo sure of th is prop osa l is sub j ect t o t he res t rict io ns on the t itl e page Emergency Alarm and Call with iToQ oJ Clueue (Single Site} SliTUR ...__ _____ ..,. RADI0-1 -TALKGROUP 1 RAD>I0>-1 -SITE -SITE ~ RADIG-2 -TALKGRQUP 1 RADI0-2 -SITE -SITE 1 RADIQ-3 -TALKGROUP 2 RACH0-3 -Sl"fiE -SIT:E ~ RAl'.dl0-4 -TALKGROLJP 3 RADIG-4 -SlifE -Slif"E 1 WERSIGN #1.150 Motorola Confidential Restricted Us e or disclosu re of this proposal is subject to the restrictions on the titl e page ,-bis test was performed and passed during Phase 2 testing_,9 n 10/09 /2012. City of Fort W orth , Texas A STRO 25 Migration , Ci tywide Trun ked Radio System December 20,.2013 Acceptan ce Test Plan 4-13 ~. DESCRIPTIO This test verifies that a subscriber can be set ug for receive o eration onlY, Setting a portable for "dispatch enabled" egua to no in the Radio User Capabilities record allows the radio to receive but not initiate grou g calls . Setting a portable for "Voice enabled" equal to no in the Radio User profile allows the user tg receive dispatch calls , but not originate o receive Unit-to-Unit or call alerts . SETUP. ...._ _____ ..., RADI0-1 -TALKGROUP 1 RADI0-1 -SITE -SITE 1 RADI0-2 -TALKGROUP 1 RADI0-2 -SITE -SITE '---- CONSOLE-1 -TALKGROUP VERSION #1.11 9 City of Fort Worth , Texas ASTRO 25 Migrati on, Citywide Trunked Radio System De cember 20, 20 13 4-14 A cceptance Test Pl an 2. TES li .__ _____ ..,.,..--~~ Step 1. Set RAD10-1's template for "dispatch enabled" equal to no in the Radio Usen Capabilities Profile. This allows the rad ·o to receive , but not initiate group calls. Step 2. Set RADI0-1 for "Voice enabled" equal to no in the Radio User. This allows the user to receive dispatch calls , but no t originate or receive U ·t-to-Unit or cal ____ alerts .... ------------. Ste g 3 . Verify that the Site Access denial flag is set to either "Both" or "TG Onl Y,''. 4 . Make a call from CONSOLE-1 on ---;TALKGROUP 1. Verift both Radios can hear the audio ----l..------.,,-~ SteP-5 . Make a call from RADI0-2 and verify t a both RADI0-1 and the CONSOLE-1 hear the cal l. ~-.......... -,--~----Ste 6. Verify that RADI0-1 is not granted ____ channel when it is keyed up ._. __ _ Ste 12 7. Verify that CONSOLE-1 can not make a Private Call to RADI0-1 but can Private Call RADI0-2 . ...__ ____ __, Step 8. Verify that RADI0-2 cannot make Private Call to RADI0-1 but can Private Call CONSOLE-1. This test was performed and passed during Phase 2 testing on 10/09/2 01 2 . Pass __ Fail __ Mo t orol a Confidential Res t ricted Use or disclosure of th is proposa l is subject to the restrict io ns on the title page Slgn0ff Certificate wrrNE~ss · Please Print Title: WlifNESS: Please Print Name: PJease.P.rin U f.itle : ~l"JiNE£~: ~!'ease P ri nt Name: Motorola Confidential Restricted Use or disclosu re of thi s proposal is subject to the restrictions on the t it le page Initials: Initials City of Fort Worth, Texas ASTRO 25 Migration , Citywide Trunked Radio System December 20 ,.2013 Acceptance Test Plan 4-15 4.3 Phase 3 MCC 7500 Features Multigroup Call 1. DESCRIPTION This trun k ing featu re allows an equipped console operator posit ion to transm it an announcement to several different talkgroups simu ltaneously . As with Tal kgroup Calls , multigroup calls opera te across sites as well as w ith in the same s ite. SETUP RADI0-1 -TALKGROUP 1 RADI0-1 -SITE -SITE 1 RADI0-2 -TALKGROUP 2 RADI0-2 -SITE -SITE 2 RADI0-3 -TALKGROUP 3 RADI0-3 -SITE -SITE 3 (SITE 1 if only 2 Sites) RADI0-4 -RANDOM RADI0-4 -SITE -SITE 4 (SITE 2 if only 2 Sites ) CONSOLE-1 -ATG * TALKGROUP 1, TALKGROUP 2 , & TALKGROUP 3 are members of ATG 1. * RANDOM is any talkgroup not a membe r of ATG 1. * Multigroups are set up through both the UCM and the Subsc riber Programm ing software . VERSION #1.120 City of Fort Worth , Texas A STRO 25 Mi gration , Citywide T runked Radio System December 20, 2013 4-14 A ccep t ance Test Plan 2. TEST Step 1. Using CONSOLE -1, select the ATG 1 resource , wh ich corresponds to TALKGROUP 1, TALKGROUP 2, and TALKGROUP 3. Step 2. Initiate the Multigroup Cal l from CONSOLE -1. Step 3. Observe that RADI0-1 , RADI0-2 and RADI0-3 receive the Multigroup Call. Step 4 . Verify that RADI0-4 does not receive the Multigroup Call because it is not a member of ATG 1. Step 5. Answer the Multigroup Call using RADI0- 1 and observe CONSOLE-1 rece ives the response . Step 6. Verify that if the call is answered within the repeater hang time , the console will receive the call on the ATG 1 resource tile , otherwise the console will receive the call on the TALKGROUP 1 tile . Step 7. Verify that if the call is answered within the repeate r hang time , RADI0-2 and RADI0 -3 will monitor that cal l. Pass Fail Motorola Confidential Restricted Use or disc losu re of th is pro posa l is s ubj ect to t he rest ri ct ions o n the t itle page MCC 7500 Features Call Alert Page 1. DESCRIPTION Call Alert Page allows a subscriber/dispatcher to sel~ct ive ly alert another radio uni t. The initiating radio/console will receive notification as to whethe r or not the ca ll alert was received . Units receiving a Call Alert will sound an alert tone a~d show a visual alert indication. The display will also show the individual ID of the initiating radio/console unit. After receiving the Call Alert, the radio can respond with either a Private Call or norma l talkgroup call. This feature is fully supported on all display portables and mobiles. SETUP RADI0-1 -TALKGROUP 1 RADI0-1 -SITE -SITE 1 CONSOLE-1 -TALKGROUP 1 VERSION #1.070 Motorola Confidential Restricted Use or disclosure of t his proposal is subject to the restrictions on the title page 2. TEST Step 1. Using CONSOLE-1, select the call alert button in the "Private Call" resource window . Step 2. Enter the ID of RADI0-1 . Step 3. Send the call alert to RADI0-1 by depressing the send button . Step 4 . Verify that RADI0-1 receives the alert and that the ID of the console is shown . Step 5. Turn off RADI0-1 . Step 6. Send the call alert to RADI0-1 again . Step 7. Verify that after trying to page RADI0-1 , the console displays "Can not send call alert -target not found " in the summary list. Pass Fail City of Fort Worth , Texas ASTRO 25 Migration , Citywide Tru nked Radio System Dece mbe r 20,.2013 Acceptance Test Plan 4-15 MCC 7500 Features Talkgroup Selection and Call 1. DESCRIPTION The Talkgroup Call is the prim ary level of organization for communications on a trun ke d rad io system . Dispatchers with Talkgroup Call capability will be ab le to communicate with other members of the same talkgroup. This provides the effect of an assigned channel down to the talkgroup level. When a Talkgroup Call is in itiated from a subscriber unit , the call is indicated on each dispatch operator position that has a channel control resource associated with the un it's channel/talkgroup. SETUP RADI0-1 -TALKGROUP 1 RADI0-1 -SITE -SITE 1 RADI0-2 -TALKGROUP 2 RADI0-2 -SITE -SITE 1 RADI0-3 -TALKGROUP 1 RADI0-3 -SITE -SITE 2 RADI0-4 -TALKGROUP 2 RADI0-4 -SITE -SITE 2 CONSOLE-1 -TALKGROUP 1 CONSOLE-2 -TALKGROUP 2 VERSION #1.100 City of Fort Worth , Texas ASTRO 25 Migration , Citywide Trunked Radio System Decem ber 20, 2013 4-16 Acceptance Test Plan 2. TEST Step 1. Initiate a wide area call from CONSOLE-1 on TALKGROUP 1. Step 2. Observe that RADI0-1 and RADI0 -3 will be able to monitor the call. Dekey the console and have either radio respond to the call. Step 3. Observe that all Consoles with TALKGROUP 1 can monitor both sides of the conversation . Step 4 . Ini tiate a wide area call from CONSOLE-2 on TALKGROUP 2. Step 5 . Observe that RADI0-2 and RADI0-4 w ill be able to monitor the call . Dekey the console and have either radio respond to the call . Step 6. Observe that all Consoles with TALKGROUP 2 can monitor both sides of the conve rsation . Pass Fail Motorola Confidential Restricted Use o r disclosure of t his proposa l is subject to the restrict ions on the t itl e page • MCC 7500 Features Secure Talkgroup Selection and Call 1. DESCRIPTION The talkgroup call is the primary level of organization for communicat ions on a trunked radio system. Dispa tchers with talkgroup call capability will be able to communicate with other members of the same talkgroup . This provides the effect of an assigned channel down to the talkgroup level. When a talkgroup call is initiated from a subscriber unit , the call is indicated on each dispatch operator position that has a channel control resource associated with the unit's channel/talkgroup . Note : Radios used in this test must be secure capable . SETUP RADI0-1 -TALKGROUP 1 RADI0-1 -SITE -SITE 1 RADI0-2 -TALKGROUP 2 RADI0-2 -SITE -SITE 1 RADI0-3 -TALKGROUP 1 RADI0-3 -SITE -SITE 2 RADI0-4 -TALKGROUP 2 RADI0-4 -SITE -SITE 2 TALKGROUP 1 uses "CKR1" and TALKGROUP 2 uses "CKR2". All radios are set for secure transmit. All Consoles (MCC 7500 and Gold Elite) are configured with TALKGROUP 1 and TALKGROUP 2 with CKR1 and CKR2 assigned , respect ively . Encryption Keys for "CKR 1" and "CKR2 " are properly loaded in all Radios and Consoles. VERSION #1.020 Motorola Confidential Restricted Use or di sclosure of this proposal is subject to the restrictions on t he t itl e page 2. TEST Step 1. Initiate a secure wide area call from any Gold Elite operator position on TALKGROUP 1. Step 2. Observe that RADI0-1 and RADI0-3 will be able to mon itor the secure call. Also observe that any MCC 7500 Console on TALKGROUP 1 is able to monitor the secure call . Step 3. Dekey the Gold Elite console and have either radio respond in secure to the call . Step 4. Observe that all Consoles (both Gold Elite and MCC 7500) with TALKGROUP 1 can monitor both sides of the conversation . Step 5. Dekey the radio . Step 6. Initiate a secure w ide area call from any MCC 7500 operator position on TALKGROUP 2. Step 7. Observe that RADI0-2 and RADI0-4 will be able to monitor the secure call . Also observe that any Gold El ite Console on TALKGROUP 2 is able to monitor the secure call. Step 8. Dekey the MCC 7500 console and have either radio respond in secure to the call. Step 9. Observe that all Consoles (bot h Gold Elite and MCC 7500) with TALKGROUP 2 can monitor both sides of the conversation. Step 10. Dekey the radio . Pass __ Fail __ City of Fort Worth , Texas ASTRO 25 Migration , C itywide Trunked Radio System December 20 ,.2013 Acceptance Te st Plan 4-17 MCC 7500 Features Talkgroup Patch 1. DESCRIPTION Talkgroup Patch allows a dispatche r to merge several ta lkgroups together on one voice channel to participate in a single conversation. This can be used for situations involving two or more channels or talkgroups that need to communicate with each other. Using the Patch featu re, the console operator can talk and listen to all of the selected talkgroups grouped ; in addition , the members of the indiv idual tal kgroups can also talk or listen to members of other ta lkgroups . Patched talkgroups can communicate with the console dispatcher and other members of different talkgroups because of the "supergroup" nature of the Patch feature. NOTE : If "secure" and "clear" resources are patched together, one repeater for each mode may be assigned per site . SETUP RADI0-1 -TALKGROUP 1 RADI0-1 -SITE -SITE 1 RADI0-2 -TALKGROUP 2 RADI0-2 -SITE -SITE 1 RADI0-3 -TALKGROUP 1 RADI0-3 -SITE -SITE 2 RADI0-4 -TALKGROUP 2 RADI0-4 -SITE -SITE 2 * All 4 Radios must have the same home zone . All 4 Radios should be in the clear mode. VERSION #1.090 City of Fort Worth , Texas A STR O 25 Mig rat ion , C ityw ide Trun ked Rad io Syste m December 20 , 20 13 4-1 8 Acce ptance T est Plan 2. TEST Ste p 1. Se le ct an operator position for testing wh ich contains TALKGROUP 1 and TALKGROUP 2. Step 2. At the desired operator position select one of the Patch tabs in the Patch/Multi - Se lect window. Step 3. Click the button on the patch that allows an operator to setup and edit a patch (note that the patch window turns blue). Step 4 . Add TALKGROUP 1 and TALKGROUP 2 to the patch by selecting each resource tile . Step 5. Once the talkgroups are added , click the patch setup button again to complete the patch setup. Step 6. Initiate seve ral Talkgroup Calls between Step 7 . Step 8. Step 9. radios. Observe that all radios are able to communicate with one another. Also via ZoneWatch (if available) observe that only one station is assigned at each of the two sites. Initiate a call from the operator position using the Patch Transmit and observe that all radios are able to receive the call and only one station is assigned at each of the two sites. Remove TALKGROUP 1 and TALKGROUP 2 from the patch . Pass __ Fail __ Motorola Confidential Restricted Use or disclos ure of t his proposa l is s ubj ect to th e res t rict ion s on th e titl e page MCC 7500 Features Multi-Select/APB 1. DESCRIPTION Multi-Select (MSEL) allows a dispatcher to merge several talkgroups together on one voice channel to participate in a single conversation. This can be used for announcements to two or more channels or talkgroups for general broadcast purposes . Using the Mu lti-Select feature , the console operator can talk and listen to all of the selected talkgroups grouped ; however, the members of the individual talkgroups cannot talk or listen to members of other talkgroups . Multi-selected talkgroups sti ll only communicate with the console dispatcher and other members in the same talkgroup. A predefined multi-select configuration can be saved by the console operator as an All Points Bulletin (APB) for qu ick broadcast-type transmissions by the dispatcher. NOTE : If "secure" and "clear" resources are multi-selected , one repeater for each mode may be assigned per site. SETUP RADI0-1 -TALKGROUP 1 RADI0-1 -SITE -SITE 1 RADI0-2 -TALKGROUP 2 RADI0-2 -SITE -SITE 2 RADI0-3 -TALKGROUP 3 RADI0-3 -SITE -SITE 1 RADI0-4 -TALKGROUP 4 RADI0-4 -SITE -SITE 2 CONSOLE-1 -TALKGROUP 1, TALKGROUP 2 , TALKGROUP 3 and TALKGROUP 4 VERSION #1.090 Motorola Confidential Restricted Use or d isclos ure of this proposal is subject to the restrictions on t he titl e page 2. TEST Step 1. At CONSOLE-1 select one of the Multi- Select tabs in the Patch/Multi -Select window . Step 2. Click the button on the Multi-Select that allows an operator to setup and edit a multiselect (note: MSEL window turns green ). Step 3. Add TALKGROUP 1, TALKGROUP 2 , TALKGROUP 3 and TALKGROUP 4 to the Multi -Select by selecting each resource tile. Step 4. Once the talkgroups are added click the Multi-Select Setup button again to complete the Multi-Select setup . Step 5. Initiate a call from CONSOLE-1 using the APB Transmit and observe that all radios are able to receive the call. Also via ZoneWatch (i f available) verify that only one RF resource is ass igned at any s ite where multiple radios are affiliated. (See note) Step 6. Remove all talkgroups from the Multi- Select. Pass Fail City of Fort Worth , Texas ASTRO 25 Mig rat ion, C it ywide Trunked Radio System Decembe r 20 ,.2013 Acceptan ce Te st Plan 4-19 MCC 7500 Features MCC 7500 Console Initiated Private Call to a MCC 7500 Console 1. DESCRIPTION Private Conversation is a select ive call ing feature that allows a dispatcher or radio user to carry on one-to-one conversat ion that is hea rd only by the two parties involved . Subscr iber uni ts receiving a private call wil l sound an alert tone . As with other call types , Private Calls operate across sites as well as within the same site . MCC 7500 Console can use the feature to communicate with another MCC 7500 Console in the same or another Console Site. Pr ivate call between the two Consoles is supported for MCC 7500 Consoles only . SETUP RADI0-1 -TALKGROUP 1 RADI0-1 -SITE -SITE 1 CONSOLE-1 -CSITE -CSITE 1 CONSOLE-1 -CSITE -CSITE 1 CONSOLE-1 -CSITE -CSITE 1 VERSION #1.060 City of Fort Worth , Texas A S T RO 25 Mig ration , Citywide Trunked Rad io System Decembe r 20 , 20 13 4-20 A cce pta nce Test Plan 2. TEST Step 1. Se lect the "PRIVATE -CALL" tile at CONSOLE-1 . Step 2 . Click the button on the tile that prov ides the Private Call function . Step 3. Select the numeric keypad . Step 4 . Using the displayed keypad enter the unit ID to be Private Called (CONSOLE-2) or select CONSOLE-2 from the drop down list (i f listed ). Step 5. Click the Send button. Step 6 . At CONSOLE-2 , answer the Pr ivate Call from CONSOLE-1 and verify that CONSOLE-2 is able to hear the CONSOLE-1 audio . Also verify that the CONSOLE-1 can hear the CONSOLE-2 audio . Step 7 . Verify that RADI0-1 and CONSOLE-3 do not hear the audio for the Private Call. Step 8. Verify us ing ZoneWatch (if applicable) that no site resources are used as th is is an IP-based call from Console user to Console user. Step 9. After completing the Private Call , return to the normal talkgroup mode . Pass __ Fail __ Motorola Confidential Restricted Use or di sclos ure of thi s pro posa l is s ubj ect to t he restr ictio ns o n th e t itl e page MCC 7500 Features Emergency Alarm (Ack'd by MCC 7500 Console) and Call Display Description 1. DESCRIPTION Use rs in life threaten ing situat ions can use the eme rgency button on t he radio to send an audible ala rm and a v isual alarm signal to a conso le operator in o rder to request immed iate system access to a voice channel fo r an emergency call . An emergency alarm begins after the radio user presses the radio's emergency button . Pressing the emergency button places the rad io in "emergency mode". To begin an emergency call , the rad io use r must press the rad io's PTT button while in "emergency mode." The assigned voi c e channe l will be dedicated to the emergency ca ller's talkgroup for an extended period of time , equa l to the Message Hang Time plus the Emergency Hang T ime . As with other call types , emergency calls can operate across sites as well as within the same site . SETUP RADI0-1 -TALKGROUP 1 RADI0-1 -SITE -SITE 1 VERSION #1.050 Motorola Confid e ntial Restri cted Use or disclos ur e of t his pro posa l is subject to t he rest ri ct io ns on the title page 2. TEST St ep 1. Select an MCC 7 500 operato r position in the zone where RADI0-1 is affiliated for the test. Step 2. Initiate an Emergency Alarm from RADI0- 1. Step 3. Observe the Emergency from RADI0-1 is received at the MCC 7 500 operator posit ion for T ALKGROU P 1. St ep 4 . Ac k nowledge the Em ergency at t he MCC 7500 opera tor position. Verify that another ope rator pos it ion affil iated to TALKGROUP 1 receives not ificat ion that the call has been acknowledged. Step 5. Key RADI0-1 to in itiate an Emergency call to th e MCC 7 500 operator position and reply to the rad io from the operator position . Observe that the call ta kes place . Step 6. Clear the Emergency from the MCC 7500 console on TALKGROUP 1. Step 7 . Reset RADI0-1 by holding the Emergency button on the rad io. Pass __ Fail __ City of Fort Worth , Texas A ST RO 25 M igration , C itywide T run ked Radio System Decembe r 20 ,.2013 Accept ance T est Plan 4-21 MCC 7500 Features Channel Marker -Trunked Channels (MCC 7500 Consoles Only) 1. DESCRIPTION A Channel Marker is a distinct , short duration , audible tone over radio and Console speakers . The tone is initiated and cancelled by a console operator. The tone can be initiated only for the talkgroups or analog conventional channels. On initiation , it is generated periodically when there is no voice activity. The tone can be used for various purposes. The primary purpose of t he tone is to inform radio users that the conventional channel or the trunked talkgroup is currently involved in a high priority situation and they should stay off the channel unless they are involved in the high priority situation. The tone also informs the users that a console operator is actively monitoring the talkgroup . Note that the Channel Marker tone will only start when there is no vo ice activity for the selected Talkgroup/Analog conventional channel. The channel Marker tone is sent in a current transmission mode of the Console user. SETUP RADI0-1 TALKGROUP 1 RADI0-2 TALKGROUP 1 CONSOLE-1 -TALKGROUP 1 CONSOLE-2 -TALKGROUP 1 Note : Verify that TALKGROUP 1 has Channel Marker capability VERSION #1.030 City of Fort Worth, Texas ASTRO 25 Migrati on, Cityw ide Trunked Rad io System De cem be r 20 , 20 13 4-22 Accept ance Te st Plan 2. TEST Step 1. Verify communications between the Consoles and the Radios on TALKGROUP 1 Step 2. Initiate a Channel Marker tone on TALKGROUP 1 from CONSOLE-1 . Step 3. Verify that RADI0-1 and RADI0-2 can monitor the Channel Marker tone at TALKGROUP 1 preset period . Step 4. Verify that CONSOLE-1 and CONSOLE-2 can also monitor the Channel Marker tone at TALKGROUP 1 preset period . Step 5. Initiate a call from RAD I0-1 and continue to key longer than the preset Channel Marker tone period for TALKGROUP 1 Step 6. Verify that while RADI0-1 is keyed , the Channel Marker tone is suppressed. Step 7. Verify that after RADI0-1 de-keys , the periodic Channel Marker tone continues to be transmitted on TALKGROUP 1 Step 8. Cancel the Channel Marker on T ALKGROUP 1 from CONSOLE-1 . Step 9. Verify the Channel Marker is no longer monitored on TALKGROUP 1 Pass __ Fail __ Motorola Confidential Restricted Use or di sclosure of this proposal is subject t o th e restri cti o ns on the t itl e pag e MCC 7500 Features Console Priority 1. DESCRIPTION Console Operator Positions have ult imate control of transmitted audio on an assigned vo ice channel resource . The Console Position has the capability to take control of an assigned vo ice channel for a talkgroup call so that the operator's audio overrides any subsc riber audio. Console priority is a feature that enables dispatchers to gain immed iate access to an assigned vo ice channel so that a central point of aud io contro l ex ists . SETUP RADI0-1 -TALKGROUP 1 RADI0-1 -SITE -SITE 1 RADI0-2 -TALKGROUP 1 RADI0-2 -SITE -SITE 1 CONSOLE-1 -TALKGROUP 1 VERSION #1.110 Motorola Confidential Restricted Use or di sclos ure of thi s proposa l is subject to the rest rictions on the title page 2. TEST Step 1. In itiate a Talkgroup call from RADI0-1 on TALKGROUP 1. Keep this ca ll in progress until the test has completed . Step 2. Observe that RAD I0-2 receives the call. Step 3. Wh ile the ca ll is in progress , key up CONSOLE-1 on TALKGROUP 1. Step 4. Observe that RAD I0-2 is now receiving audio from CONSOLE -1 on TALKGROUP 1. Step 5. De -key CONSOLE-1. Step 6. Verify RADI0-2 now receives RADI0-1 audio . Step 7. End the TALKGROUP 1 call from RADI0- 1. Pass Fail City of Fort Worth , Texas AS T RO 25 Migrat ion , Citywide Tr unked Rad io System December 20 ,.2013 Acce ptance Test Pl an 4-23 MCC 7500 Features Link Failure between MCC 7500 site and Zone Controller 1. DESCRIPTION This test verifies that the two co mm unication paths between the MCC 7500 Consol e Site and Zone Controller are redundant and the syste m w ill continue uninte rrupted if the ma in path fails . To accomplish this test one of the two NIC connect ions is removed at the ZC . SETUP RADI0-1 -TALKGROUP 1 RADI0-1 -SITE -SITE 1 RADI0-2 -TALKGROUP 1 RADI0-2 -SITE -SITE 1 RADI0-3 -TALKGROUP 2 RADI0-3 -SITE -SITE 1 RADI0-4 -TALKGROUP 2 RADI0-4 -SITE -SITE 2 CONSOLE-1 and CONSOLE-2 at the MCC 7500 Console site are affiliated to the TALKGROUP 1 and TALKGROUP 2 talkgroups . VERSION #1.040 City of Fort Worth , Texas A ST RO 25 Migration , C ityw ide T ru nked Radio System December 20 , 2013 4-24 A cceptance Test Plan 2. TEST Step 1. In it iate a Talkgroup Call w ith RADI0-1 in TALKGROUP 1. Step 2. Observe that only RADI0-2, CONSOLE -1 and CONSOLE-2 are able to monitor and respond to the call Step 3. Initiate a Tal kgroup call with RADI0-3 in TALKGROUP 2. Step 4. Observe that only RADI0-4 , CONSOLE-1 and CONSOLE-2 are able to monitor and respond to the call. Step 5. Remove the ENET cable to Link 1 from the NIC on the ZC , th is will simulate a Zone Controlle r to Console Site Link failure. Step 6. Observe that the calls on TALKGROUP 1 and TALKGROUP 2 can continue . Step 8. Connect the ENET cables to normalize the system . Pass __ Fail __ Motorola Confidential Restricted Use o r disc los ure of t his proposa l is subject to th e restr ictions on the t itl e page MCC 7500 Features Redundant Console Site Link Failure (MCC 7500 Console Site only) 1. DESCRIPTION Communication between the Master Site and a Remote Console Site ca n take place over dedicated redundant links . The two links between the Master Site and the Remote Console Site operate in a redundant mode. The system will switch to the backup link if the main LAN or WAN link fails . Note : The Pr imary Site Router, if functional , will always be the active router . The Secondary Site Router will only take over when the Primary Site Router is malfunctioning. SETUP RADI0-1 -TALKGROUP 1 RADI0-1 -SITE -SITE 1 CONSOLE-1 -TALKGROUP 1 A radio and a Console are required to perform this test (RA DI0-1 and CONSOLE-1 ). Select a Consol e site with redundant links to the Master Site. VERSION #1.010 Motorola Confidential Restricted Us e or discl osure of th is proposal is sub j ect to the re st ri ct ions on the title page 2. TEST Step 1. CONSOLE-1 initiates a Tal kgroup call on TALKGROUP 1. Step 2. Observe that RADI0-1 is able to receive and respond to the call. Step 3. Remove the WAN link from the active router (Primary Site Router) at the Remote Console Site. Step 4 . In itiate a Talkgroup Call with RADI0-1 in TALKGROUP 1. Step 5. Observe that CONSOLE-1 is able to rece ive and respond to the call. Step 6. Replace the WAN link connection that was removed in step 4 . Pass __ Fail __ City of Fort Worth , Texas ASTRO 25 Mi g rati o n, Citywide Trun ked Radio Sys tem December 20 ,.2013 Acceptance Test Plan 4-25 MCC 7500 Features 1. DESCRIPTION This test will demonstrate the Archiving lnterfac~ Server (AIS) can be used to log trunking talkgroup call audio for call in a secure transmi mode on a given talkgroup . The audio i archived in a vocoded decrypted format (I B , for Trunking Talkgroup Call) only when the logging system user reguested coded audio t be logged . The AIS at MCC7500 Console site is affiliated to TALKGROUP 1 and has the appro12riate secure keys loaded . ..__ __ RADI0-1 -TALKGROUP 1 RADI0-1 -SITE -SITE 1 CONSOLE-1 -TALKGROUP 1 City of Fort Worth , Texas ASTRO 25 Mig ration, Citywide Trunked Radio System December 20 , 2013 4-26 Acceptance Test Plan 2. TES 11 Step 1 I itiate PTT from RADI0-1 on TALKGROUP 1 in a secure transmi t mode . Step 2. Observe that the call audio is being sent to the logging system by the laybacl< application . Step 3. lfTALKGROUP 1 is marked to receiv coded audio verify the coded audio can be played back via the application . Ste(::! 4 . Observe that the-events for the TALKGROUP 1 call is logged even if the TALKGROUP 1 is not marked to receive coded audio . This test was performed and passed during Phase 2 testing on 10 /09 /2 01 2. Pass Fail Motorola Confidential Restricted Use or disclosure of th is proposal is subject to the res t rictions on the t itl e page ' PC 7500 Features . DESCRIPTIG>N i...:,:---,,,......,...-------~-ifnis test will demonstrate that upon receiving notification from the Zone Controller of an Emergency Acknowlecige/Rec0gflize issued fo n a resource that tne AIS is monitoring, the AIS will re ort the event to the Log_gii g Syste m S~TUR ---~---RAGIQ-~ 1ALKGRGlJIP 1 CONSOLE:-1 TALKGROUP 1 AIS , NICE play back station a ... n""'0_r_e-co_r_d_s-ta-t-io,_ connected to AIS via the site LAN switcn . Configure an alias for RADI0-1 and RADI0-2 alild allow ... adeguate time for data i;,roQagati0n . ERSION #1.06 Motorola Confidential Restricted Use o r d isclosu re of t his proposa l is subject to the restrictions on the t itle page 2. TEST! ~...,.......,.,,, .. _,, __ .,..,.._ Step 1. Start an emergency alarm from RABIO ] .§~ 2. Verify tnat a RADI0-1 displays a ----· emergency indication and CONSQLE-1. •-c-·-·-·-·gets the Emergency indication . Step2:_ Key up RADI0-1 on TALKGROUP j_ Verify that CONSOL6-1 receives audio .....----on TAlKGRQUP 1 ........ ___ _ ~R 4. Playback rece t TALKGROUP 1 cal activitie . ___ ____, . .,.,... ___ ,,__ __ ~ §te 5. Verify that the logging system has recorded the emergency alarm ..._.. __ Fall/events with correct Resource Alias , ,lndivig_ual Alias Site ID and the zone ID . Thi s t es t was p erformed and ·p asse d durjn g Ph2 s~ 2 _t ~sting on 10/09/2 01 2. City of Fort Worth, Tex as ASTRO 25 Mig ration , Ci tyw ide T runked Radio System December 20 ,.2013 Acceptance T est Pla n 4-27 Logging Subsystem -Logging User Can Search Recorded Calls b~ Various Fields 1. DESCRIPTIO Th is test will demonstrate that the Logging System will allow an authorized user to searc recorded conversat ions and to play back th des ired conversation . The supported searc includes time and date search, resource search based on ID or alias (trunked talkgroup), type oj ca ll search site search zone search and use n search ~.-------------------- Note : If using the Inform Appl ication the search fields may be lim ited to 3, Unit ID , Resou rce Alias and Ind ividual ID SETU The NICE play back sta tion connected to AI S via the site LAN switch. AIS with prerecorded audio/events in TALKGROUP 1 an TALKGROUP 2 is required . Assign aliases for TALKGROUP 1 (TALKGROUP 1_ALIAS) and TALKGROUP 2 (TALKGROUP 2_ALIAS}. Playback station is configured wi th Use r Account UA. VERSION #1.070 City of Fo rt Wo rth, Texas ASTRO 25 Migration , Citywide Trun ked Radio System December 20 , 2013 4-28 A cceptan ce Test Pl an 2. TES lj §tep 1. Verify that TALKGROUP 1 and TALKGROUP 2 recorded audio/events can be replayed by logging in with U/>J user account. S!e p 2. Search for a recorded call by 'time an d date' field and play back the recorde call from the search results . ._---- Ste Q 3. Verify that accurate search results ar produced and the recorded call is played bac ~.._1 ----~~- S1eR 4 . Search for a recorded call by 'lndividua Al ias' field and play back the recorde call from the search results.__ __ _ St§!? 5. Verify that accurate search results are produced and the recorded call is played bac 1-...,----------. Ste Q 6. Search for a recorded call by 'Resourc aliases' and play back the ecorded cal from the search results . ___ _ SteR 7. Verify that accurate search results ar produced and the recorded call i played bacl~ ~te R 8. Search for a recorded call by 'Site ID ' fiel and play back the recorded call from the search results . Step 9. Verify that accurate search results ar§ produced and the recorded call is pl ayed back . This test was performed and passed during Phase 2 testing on 10 /09 /2012. Pass __ Fail __ Mot orola Confidentia l Res tri ct ed Use or disclosure of this proposa l is subject to the restri ctio ns on the tit le page ilec 7500 Features ~ Log_ging Trunking if"alkgreu ~ Call :1. D ESCRIP"f lON iT his test w·ill aemon ... s""'t r-a-te,-h,-o-w=~th_e_A~re·~h~iv.~i-n~·g·, Interface Server (AIS ) can be used to le g" t runk ing talkgroup call audio/events on a g ive n t alkgrou p. The aud io is a rchived in a v0coded fo rmat (IMB ~ for T run k ing Talt grou p Calls). VERSION #1 .040 Motorola Confidenti a l Re stricte d Use or d isclosure of th is proposal is subject to the restr ictions on the title page 2. TES 1!,~--·- SteR...1.Jr!ltiate a talkgroup call from RADI0-1 on ifALKGROUP ~-_, ·-~-·----' ?t~p_J . Observe that the call e ven ts/audio are being sent tQ.J.h~Qgg _Lr:igy ys tem byy,_g ,_.,..,... ___ Al£. §tel?.2 !)sing the playback station and logging recorder, verify the logged au d io/events --~ ....... correspond to steps 1 and 2. · SteQ 4. Initiate a tal kgroup call from CONSOLE-1 on TALKGROUP 1 -~--""" SteQ 5._ob·serve that the call events/audio are being~<U.tl§Jogging_Jh'.Stem by the ____ _.AIS . §te P.._§.,_ LI.sing t he playback station an'i:J logging recorder , verify the audie/events log ~c:j fg rr§§P-Ond_ to ste ps 4 and 5. This t es t was performed and passe d during Phase 2 t~sting on 10/0~/2012. Pass __ f a)I __ City of Fort Worth , Texas ASTRO 25 Migration , Cityw ide Trunked Radio System Decem be r 20 ,.2013 Acceptance Test Plan 4-29 MCC 7500 Features Instant Recall Recorder (IRR) Operation on the MCC 7500 1. DESCRIPTION The Instant Recall Recorder (IRR) a llows for audio from a phone call or a radio call to be played back at the MCC 7500 Console position . Thirty minutes of audio is saved for radio and an additional thirty mi nutes for telephone . The audio is saved on the positions hard disk in the form of a .wav file . SETUP CONSOLE-1 -TALKGROUP 1 running IRR application . VERSION #1.010 City of Fort Worth , Texas ASTRO 25 Migration , Citywide T runked Radio System Decembe r 20 , 2013 4-30 Acceptance Test Plan 2. TEST Step 1. Select a radio channel on the CONSOLE- 1 application window. Step 2. Select IRR from the CONSOLE-1 toolbar. Step 3. Initiate radio communication between two portables . Step 4 . Verify a new entry appears in the IRR log window. Step 5. Select the new entry from the list. Step 6. Press play and verify conversation replay . Pass Fail Motorola Confidential Restricted Use or disclosure of thi s proposal is subject t o the re strict ions on the title page MCC 7500 Features System Page -Sequential Mode (MCC 7500 Consoles Only) 1. DESCRIPTION A pag e is an attempt to send an alert to a destination receiver. Pages are use d to convey alarm to users , or contro l messages to specialized hardware . A System Page is a Ca ll alert (signaling alert) typically sen t to the user to indicate the originator's desire to be contacted . System pages are associated w ith the trunked resources for the purpose of identify ing the system , but are sent over the control channel where the target user is affiliated . The user interface allows for issu ing an individual system page and a group system pages. The sequential mode refers to the configured pag ing mechanism where console sends pages one-at-a-t ime and in order of the pag ing q ueue . A pre-configured group page representing a set of ind ividual pages is invoked via the console use r interface . SETUP RADI0-1 -TG -1 RADI0-2 -TG -2 RAD/0-3 -CCH 1 RADI0-4 -CCH 2 VERSION #1.000 Motorola Confidential Restri cted Use or disclosure of t his proposal is subject t o the rest rictions on t he title page 2. TEST St ep 1. Ve rify comm unication s on TA LKGROUP 1, 2 and 3 by sett ing up voice calls betwe en the Rad io an d Console on each TG separately . Step 2 . Set RADI0-2 to TALKGROUP 3 Step 3. Create a list of system pages through the standa rd pagin g interface o n CONSOLE-3 El ite interface . Keep the order of the pages to be Radio1 SysPage1 , Radio 2SysPage1 and Radio 3 SysPage1 respe ctively Step 4 . Press "Send" and Verify the page to RADI0-1 is sent and received by CONSOLE-1 and RADI0-1 Step 5. Verify the page to RADI0-2 is sent and rece ived by CONSOLE-2 and RADI0-2 once the first page in the list is acknowledged Step 6. Verify the page to RADI0-3 is sent and received by RADI0-3 once the second page in the list is ac k nowledged . Pass __ Fail __ City of Fort Worth , Texas AS T RO 25 Mi gration , Citywide Trunked Radio System December 20 ,.2013 Accep tance T est Plan 4-31 MCC 7500 Features Alarm Input/Outputs (Aux 1/0 Option) 1. DESCRIPTION The alarm inputs of the Aux 1/0 can be connected to almost any dev ice that requires or can detect a relay closure . These s ignals can be simulated and monitored in the factory . SETUP Connect a multi-meter capable of monitoring closures to the proper pins of the punch block cabled to the Aux 1/0. One momentatry input and one momentary output should be configured on at least one MCC 7500 console . CONSOLE-1 -TALKGROUP 1 CONSOLE-1 -SITE -CONSITE 1 Aux 1/0 punch block pinout: Au x 1/0 1 -pins 26 , 1 Aux 1/0 2 -pins 27 ,2 Aux 1/0 3 -pins 28 ,3 Aux 1/0 4 -pins 29,4 VERSION #1.010 City of Fort Worth , Texas ASTRO 25 Migrat ion , Citywide Trunked Radio Sys tem December 20 , 2013 4-32 Acceptance Test Plan 2. TEST Step 1. Using a shorting w ire , simulate a relay closure on an input via the punch block . Step 2 . Verify that CONSOLE-1 momentary input displays the icon designated for an ON STATE . Step 3. Remo~e the shorting wire and verify that CONSOLE-1 displays the icon designated for an OFF _STATE . Step 4 . Connect the meter to the pi ns to monitor a relay output. Step 5. Verify that the meter reads an open circuit. Step 6 . Depress the momentary input button on the console to initiate a relay closure . Step 7. Verify that the meter displays a closed circuit. Pass __ Fail Motorola Confidential Restricted Us e or disc los ure of th is proposal is subject to the rest ri ct ions on the t itle pa ge Integrated Voice and Data (IV & D) Over the Air Programming (PoP25) 1. DESCRIPTION The feature Programming Over P25 (POP25) allows a user to configure a radio remotely from the enterprise network by sending a sequence of commands over-the-air via the ASTRO 25 ® IV&D system . It is ex pected that the POP25 will s ignificantly reduce the operational costs of IV&D radios by configuring personalities , talkgroups , channels , sites , etc in a radio without physically touching the radio . This test will demonstrate the ability to perform a subscriber update using Customer Programming Software (CPS ) over the air. NOTE : There are subscriber programm ing options that will affect the test. The subscriber can be programmed to Approve the update , implement the update on ne xt power cycle or disregard the update. SETUP RADI0-1 -TALKGROUP 1 RADI0-1 -SITE -SITE 1 RADI0-2 -TALKGROUP 1 RADI0-2 -SITE -SITE 1 PC loaded with Customer Programming Software (CPS) and the System Key Dongle. The PC must be connected to the ASTRO 25 ® network via the CEN . RADI0-1 must be data capable and context activated for data service . VERSION #1.060 Motorola Confidential Restricted Use or discl osure of thi s proposa l is su bj ect to t he res tri ct io ns on the ti t le page 2. TEST Step 1. Locate IP address for RADI0-1 Step 2 . From the CPS computer on the Customer Enterprise Network (CEN), connect to RADI0-1 over the network and read the subscriber . Step 3. Make a change to the arch ived program file and write to RADI0-1. Step 4. Once the new archive is received at RADI0-1 the radio user will have to approve the new configuration. Step 5. Once the new configuration has been received and the load is complete , verify the configuration change has been implemented . Step 6. On the CPS PC return the archive feature to the original state . Step 7. Send the program update to RADI0-1. Verify the progress bar is shown in the CPS status bar. Step 8. Begin a talkgroup call by keying RADI0-2 . Ver ify RADI0-1 hears the audio . Step 9. While the call is in progress dekey and key RADI0-2 several times with various pauses to interrupt the data transfer to RADI0-1 . Step 1 O. Dekey RADI0-2 and verify the data transfer completes . Once the programming update has completed accept the configurat ion change on RADI0-1 . Verify RADI0-1 configuration has returned to its original state . Pass __ Fail __ City of Fort Worth , Texas A STRO 25 Migrat ion , C itywi de Trunked Rad io Sys tem Dece mbe r 20 ,.20 13 A ccep t ance T est Pl an 4-33 Key Management Facility (KMF) Adding Keys to the Key Kettle 1. DESCRIPTION A Key Kett le is a reposi tory fo r keys. Keys can be ente red into and extracted from the Key Kettle as needs determine . The KMF allows encryption keys to be sto red two different ways in the KMF system : with or without Key ID (KID ) numbers . Encryption keys stored in the KMF without KIDs show up in a Key Kettle -one kettle per algorithm . Keys are then added to the KMF database from the Kettle , at which point , the key disappears from the Kettle , a KID is assigned to it , and it shows up inside the Keys list. In th is test , 5 Keys will be added to the Key Kettle . SETUP No setup is requ ired . VERSION #1.040 City of Fort Worth , Texas AS T RO 25 Mig rat ion, Citywide T runked Radio Sys tem December 20 , 2013 4-34 Acceptance Test Plan 2. TEST Step 1. From the KMF Client window , select the Sec urity menu and then the Kettle Keys menu item . Step 2. Select the des ired Algorithm for which keys will be ad ded . (Type AES for exam ple ). Step 3. Click the button that corresponds to the inp ut method , in this case 'Keyboard.' Step 4 . Enter the Key Data in the Key Kett le dialog bo x . Step 5. Click on the 'Save and New .' - Step 6. Add fou r additional Keys by repeating Steps 4 and 5. Step 7. Clic k the 'Close ' button . Pass Fail Motorola Confidential Restricted Use o r disclos ure of th is prop osa l is subject t o the restrict ions on the t it le page Key Management Facility (KMF) Creating Unique Key Encryption Keys (UKEKs) 1. DESCRIPTION The KMF client operator must create Unique Key Enc ryption Keys (UKEKs) for all valid OTAR system subscribers. The Unique Key Encryption Key (UKEK) is a unique key used to perform inner-layer encryption. It is assigned to a radio for encrypting keys within Key Management Messages (KMMs). SETUP There should be at least one key available in the Key Kettle correspond ing to the Algorithm being used. VERSION #1.040 Motorola Confidential Restricted Use or disclos ure of t his proposal is subject t o t he res trict ions on t he t itle page 2. TEST Step 1. From the KMF Client window, select the Security menu and then the Keys menu item . Step 2 . Click the 'New' button. Step 3. Create the Key Name. Step 4 . Choose the Key Source as 'Keyboard.' Step 5 . Select the Key Algorithm from the drop down menu or type in the correct algorithm. (type -DES-OFB , AES ). Step 6. Select the Key Type of UKEK. Step 7. Type in the Key Data. Step 8. Click on the 'Save and Close' button. Step 9. Repeat Steps 2-8 with a Key Source of 'Key Kettle .' Pass __ Fail __ City of Fort Worth , Texas ASTRO 25 Mig rati on , C it ywide T runked Rad io Sys tem December 20 ,.2013 Accept ance T es t Pl an 4-35 Key Management Facility (KMF) Creating Common Key Encryption Keys (CKEKs) 1. DESCRIPTION The KMF client operator must create Common Key Encryption Keys (CKEKs) for all valid OTAR system subscribers. The Common Key Encryption Key (CKEK) is a shared KEK that is manually assigned to Radio Groups and used for encrypting keys within group Over-the-Air Rekeying (OT AR) messages . In this test , two CKEKs will be created . SETUP There should be at least one key available in the Key Kettle corresponding to the Algorithm being used. VERSION #1.050 City of Fort Wo rth, Texas ASTRO 25 Migration , Citywide Trunked Radio System December 20 , 2013 4-36 Acceptance Test Plan 2. TEST Step 1. From the KMF Client window, select the Security menu and then the Keys menu item. Step 2. Click the 'New' button. Step 3. Create the Key Name. Step 4. Select the Key Algorithm . (type -DES- OFB , AES) Step 5. Select the Key Type of CKEK. Step 6. Choose the Key Source as 'Keyboard .' Step 7. Type in the Key Data. Step 8. Click on the 'Save and Close' button. Step 9. Repeat Steps 2-8 with a Key Source of 'Key Kettle.' Pass Fail Motorola Confidential Restricted Use or disclosure of th is proposal is subject to th e restrictions on the title page Key Management Facility (KMF) Creating CKRs -Common Key References 1. DESCRIPTION In an ASTRO 25 Trunking system , radios communicate using clear talk groups that are managed using CPS (a t the radio). Centralized key management imposes a layer of encryption over these clear talk groups . This encryption layer is created by distributing certain keys to certain users , forming secured groups by virtue of the fact that only users with keys in common are able to communicate in secured mode . These groups of users share encryption keys, called Common Key References (CK Rs ), which are created and managed us ing the KMF . The CKRs are used by all devices in the system to select a key to use for initiating outgoing secure communications . In the radios CKR addresses are actually assigned using CPS programming . CKRs must be determined in coordination with the overall communications plan . In a KMF- managed system , all devices assigned to the same CKR are provisioned with the same key data for securely communicating with one another. In th is test , three CKRs will be created . SETUP No setup required . Note : If each CKR is to have two unique TEKs , a minimum of six TEKs must already be added into the KMF database . VERSION #1.040 Motorola Confidential Restricted Use or disclosure of this proposal is subject to the restrictions on the title page 2. TEST Step 1. From the KMF C lient window, select the Sec ur ity menu and then the CKRs menu item . Step 2. Click the 'New' button . Step 3. Create CKR Name . Step 4. Enter a unique CKR ID. Step 5 . Select the Algorithm Name . (type -DES - OFB , AES). Step 6. Select KEYSET 1 and click the Select button . Choose a TEK for KEYSET 1 and click the OK button . Step 7. Select KEYSET 2 and click the Select button. Choose a TEK for KEYSET 2 and click the OK button. Step 8. Click on the 'Save and New' button . Step 9. Repeat Steps 3-8 for two additional CKRs . Step 1 O. Click on the 'Save and Close' button on the last CKR. Pass __ Fail __ City of Fort Worth , Texas ASTRO 25 Migration , Citywide Tru nked Rad io System December 20 ,.2013 Acceptance Te st Plan 4 -37 Key Management Facility (KMF) Creating Radio Groups 1. DESCRIPTION A Radio gro up is a lis t of rad ios that use th e same CKR. The Radio group ma intains th e subscribe r to CKR mapping . In this test, a Radio Group will be created . SETUP No setup required. VERSION #1.050 City of Fort Worth , Te xas AS T RO 25 Migration , Citywide T runked Radio System December 20, 2013 4-38 Acceptance Test Plan 2. TEST Step 1. From th e KMF Cl ient window , select the Securi ty menu and then the Radio Groups menu item . Step 2. Clic k the 'New' button . Step 3. Crea te a Rad io Group name . Step 4 . Enter a unique Radio Group RSI. Step 5 . Cli c k the Select button under the Select A lgorithm section. Step 6 . Select the Algor ithm Name in the 'Select Algorithm ' dialog box and click the OK button . Step 7. Clic k the Add button under the CKR sect ion . Select the CKRs in the 'Select CKR' dialog box and click the OK button . Note : pick CKR (s) that is for the sa m e algorithm that was selected earl ier . Step 8. Click on the 'Save and Close' button to end the process. Pass Fail Motorola Confidential Restricted Use or disc los ure of th is pro posa l is subject to t he rest ri ctio ns on the t itle page Key Management Facility (KMF) Creating Key Variable Loaders (KVLs) 1. DESCRIPTION A Key Variable Loader (KVL ) is a device for manually loading keys into secure devices by physically connecting to the device and downloading the key material to the attached device. The KVL4000 series serves three main functions within the ASTRO 25 KMF system : Key Fill Device -The KVL 's primary function is to serve as a key fill device for all of Motorola 's secure communications equipment - Subscribers , Console crypto -cards , and KMF crypto-cards . Configuration Tool -The KVL serves as a configuration tool that can be used to set and view various parameters w ithin Motorola's secure communications equipment. This role of the KVL is used during the initialization of a secure system , programming sessions of secure modules (Console Crypto -Cards and Subscriber UCMs ), and maintenance activities done at a service shop. Store and Forward Tool -When used with a KMF , the KVL4000 can be used to store Key Management Messages (KMMs ) from a KMF and forward those messages to other key managed devices . SETUP Ini tialize a KVL4000 for OTAR Use Note : In step si x of the tes t , the user will be asked to select a UKEK to associate with the KVL. This UKEK needs to be entered via the keyboard so the user kn ow s what the key variable actually is . This same key needs to be entered manuall y into the KVL. VERSION #1.050 Motorola Confidential Restricted Use o r d isc losure of thi s pro posal is su bject to t he restrictio ns on th e ti tle page 2. TEST Step 1. From the KMF Client window , select the Security menu and the KVLs (Key Variable Loaders ) menu item . Click the 'New' button . Step 2. C reate a KVL Name . Then enter a KVL RSI that matc hes the entered RSI of the KVL hardware. Step 3. Click the Select button under the Select Algor ithm section . Then select the Algorithm Name in the 'Select Algorithm ' dialog bo x and click the OK button. Step 4. Select the Algorithm under the UKEK section , and then click the Add button. Step 5. Select the UKEK in the 'Select UKEK' dialog bo x and click the OK button . Note: pick a UKEK that is for the same algorithm that was selected earlier. Step 6. Enter KVL Serial Number. Then click the Key Loading Tab. Step 7. Click the Add button under the CKR section . Step 8. Select all the CKRs for the KVL in the 'Select CKR' dia log bo x and cl ick the OK button . Note : pick CKR(s ) that are the same algorithm of the earlier selection Step 9. Click on the 'Save and Close' button to end the process. Pass Fail City of Fort Worth, Texas AS TR O 25 Migration , C itywide Trunked Radio System Dece mber 20 ,.20 13 Acceptance Test Plan 4-39 Key Management Facility (KMF) Creating Subscriber Units 1. DESCRIPTION In ord e r to configure radios for OTAR th e user must c reate new radio records in the KMF database . Th ese reco rds in cl ude the Radi o ID , th e UKEK , and th e Radio RSI. A radio set for Enhanced KMM Security must be provisioned with TEK as well as a UKEK. If a radio is set for enhanced security level , it must include a TEK that matches with a TEK in the KMF. Otherwise , th e registration message will not be sent by the radio or cannot be decrypted by the KMF . Th e radio must be provisioned w ith a UKEK , KMF RSI , and Message Number Period from a KVL . Thi s can be done either through the KVL manual mode , or through RED Store and Forward. The Message number period must be within the acceptable window range that is established to prevent against replay attack . With the above parameters configured , the radio is enabled for OTAR . However, until the radio has reg istered for OTAR the KMF will only accept the registration if the radio has an existing record associated to the Radio ID. SETUP Subscriber unit must be provisioned for OTAR in CPS. Typical Subscriber Unit provisioning may include : -Loading subscribers with the appropr iate encryption algorithm or algorithms . -Configuring the "Radio-wide secure " options in the CPS . -Configuring the "Radio-wide secure HW multikey" options. -Configuring the "Trunking systems multikey options ." -Configuring the "Trunking: personality" screen in the CPS . -Configuring the "Trunking : personality" Emergency Options screen in the CPS . -Configuring the "Trunking :personality :talkgroup" screen in the subscriber CPS . VERSION #1.040 City of Fort Worth, Texas AS TR O 25 Mi grat ion , Cityw ide T ru nked Rad io System De ce mber 20 , 2013 4-40 A ccepta nce T est Pl an 2. TEST Step 1. From the KMF Client window , select the Security menu and then the Radios menu item . Click the 'New' button . Step 2. Select the Radio Group in the 'Select Radio Group ' dialog bo x and click the OK button . Step 3. Create a Subscriber Name and enter the Subscriber Serial Number. Step 4. Enter a unique Radio RSI ID . Step 5. Click the Select button under the Transport Systems section . Step 6. Select the Transport Services in the 'Select Transport Services' dialog box and click the OK button . Step 7. Select an Algorithm and click on the Add button under the UKEKs (Unique Key Encryption Keys ) section. Step 8. Select the UKEK in the 'Select UKEK' dialog bo x and click the OK button. Note : pick a UKEK that is the same algorithm of the Subscriber Group Step 9. Select some or all of the Subscriber Unit Capab ilities in the Radio Details section : -Locked Out, -KLK Enabled , - Enhanced Security Mode , - lnhibiUEnable Capable . Step 10 . Click on the 'Save and Close' button to end the process . Pass Fail Motorola Confidential Restricted Us e o r disclos ure of th is pro po sa l is subj ect t o th e res t ri cti ons o n th e t itl e page Key Management Facility (KMF) Store and Forward Operation - Subscriber 1. DESCRIPTION Hav ing configured the OT AR system , every fiel d unit must be loaded with the in itialization information . Th is is referred to as "S tore and Forward " operation . This method is the same as standard OTAR pro c edures exc ept the KMMs are de livered physically and directly . SETUP Subscriber codeplug must already be configured fo r OTAR operat ion us ing CPS . RADI0-1 must be provisioned with a UKEK, KMF RSI , and Message Number Period from a KVL. Th is can be done th rough eithe r the KVL 's manua l mode , or through RED Store and Forward (S&F ). The Message Number Period must be within the acceptable w indow range that is establ ished to prevent against replay attack. With the above pa rameters configured , the radio is enabled for OTAR. However, until the rad io has registered for OTAR the KMF will on ly accept the reg istration if the radio has an ex isting record associated to the Radio ID . Two radios are re quired for this test. RADI0-1 will be the test rad io that w ill be used for Sto re and Forward ope ration . RADI0-2 will be a reference radio . It is assumed that both radios in itia lly do not have any traffic keys. Using a KVL , manua ll y load a TEK into RADI0-2. Note t hat the manually loaded TEK must be the same TEK that will be delivere d to RADI0-1 . Ensure that RADI0-1 and RADI0-2 are on the sam e talkgroup . Note : If the KVL has been set for Red Store and Forward , the ra d io does not have to be manual ly provisioned with a UKEK. Before performing th e S&F function , the KMF manager must have ass oci ated all Radio s with their CKRs , KVLs , KEKs , TEKs , etc. VERSION #1.040 Motorola Confidential Restricted Use or disclosu re of this p roposa l is subject to t he restrict ions on the t itle page 2. TEST Step 1. Conn ect th e KVL directly to the KMF Serv e r via the com port and a serial cable to download the KM Ms for the Rad ios associated with it in the KMF . Powe r up the KVL. Note that the KMF to KVL connection can be dire ct or via modem. Step 2. Using the KVL menu , arrow to the KMF option and select it. Arrow to 'Direct/RS232' and select it. Step 3. The OT AR system k nows what KVL manages what Radios. The KMF constructs the setup messages , encrypts them , and downloads them to t he KVL. The KVL displays: "Download ing from the KMF /KVL ." The download is complete when the KVL displays "Download Successful" Step 4. Power down the KVL and disconnect it from the KMF . Step 5. Powe r up both , the KVL and RADI0-1 , connect them together v ia a KVL/Rad io cable and , sele ct through the KVL menu select the Update function . Step 6. The KVL automatical ly identifies the target and updates it. Upon comp letion of the download , the KVL collects the Radio's acknowledgement and updates its memory status . The download is complete when the KVL displays "Down load Suc cessfu l" and gives an audi Step 7. Reconnect the KVL to the KMF Server to return the acknowledgements . Us ing the KVL menu , arrow up to 'KMF ' and select it. A rr ow to 'Dire ct/RS2 32' and select it. Step 8. The KMF Server updates t he Un it's currency and h isto ry. Step 9. Verify secure communications between RADI0-1 and RADI0-2. Pass __ Fail City of Fort Worth , Texas AS TRO 25 M igrati on, C itywide T runked Rad io System December 20,.2013 Acceptance T est Plan 4-41 Key Management Facility (KMF) KMF Summary Report 1. DESCRIPTION The KMF gives t he capab ility to ge nerate two typ es of reports of subscribe r reco rds ; the Detailed View Report and the Summarized Report. A Summary Report is also ava il able that contains a summary of multiple devices such as MCC 7 500 consoles including their current status . SETUP MCC 7500 console must be ente red in the KMF database . VERSION #1.020 City of Fort Worth , Texas ASTRO 25 Mi g ration , Cityw ide Tru nked Radio System December 20 , 2013 4-42 Acceptance Test Plan 2. TEST Step 1. Fro m the KMF Client window , select the Se cu rity menu followed by the Infrastructure sub-menu and then select the Consoles/CDEMs/TMGs Groups menu item . Step 2. Se lect a MCC 7500 console from the list. Step 3. Right-cl ick and choose 'View Detailed Report.' This will display a detailed report of the selected radio. Step 4. Review the Detailed Report. Step 5. Close the Detailed Report. Step 6. Select a MCC 7500 console from the list. Step 7. Right-click and choose 'View Summarized Report.' This will display a summary of the MCC 7500 information including its current or non-current state . Ste p 8. Review the Summarized Report . Step 9. Close the Summarized Report. Motorola Confidential Restricted Use or di sclosure of this proposa l is sub j ect to the restr ictions o n t he t itl e page Pass __ Fail Motorola Confidential Restricted Use or disclosu re of t his proposal is subject to the restrictions on the t itle page City of Fort Worth , Texas AS T RO 25 Mig rat io n, Cityw id e Trun ked Radio Syste m December 20 ,.2013 Acceptance T est Plan 4-43 Key Management Facility (KMF) Store and Forward Operation -MCC 7500 Consoles 1. DESCRIPTION Having con figured the OTEK system , every field un it must be loaded wit h the initialization information . This is referred to as "Store and Forward " operation . Th is method is the same as standard OTEK procedures except the KM Ms are delivered physically and directl y. Note : Console must already be configured for OTEK operation us ing NM . It is also advisable to zeroize the console by depressing t he zeroize button . This wi ll insure t hat the store and forward is performed in the console with a clea n de fault status . T ypica l Console NM secure provisioning may include: -Co nfiguring the console "secure" options in the NM for secure voice (VPM /secure card , TG-CKR mappings , secure/clear strapping , etc.) -Configu ring the console OTEK options in the NM (O TEK enabled , KMF FQDN , security levels, etc.). CONSOLE-1 must also be prov isioned with a console RSI , UKEK, KMF RSI , and Messag e Number Pe riod from a KVL . Th is can be done through either the KVL's manual mode , o r through RED Sto re and Forwa rd (S&F). Th e Message Number Pe riod must be within th e acceptable window ra nge that is established to prevent against rep lay attack. W ith the above parameters configu red , the console is enabled for OTEK. Ho wever , unti l the console has reg istered for OTEK the KMF will not be able to centrally ma nage it using OTEK. The KMF will only accept the registrat ion if th e console has an existing re cord associated to the Cons ole ID . Note: If t he KVL has been set for Red Store and Forward , th e console does not ha ve t o be manually provisioned with a UKEK. Th e KVL must also be provisioned and coordinated with the KMF configuration . SETUP RADI0-1 -TALKGROUP 1 (Secure mode , keys must be loaded ) CONSOLE-1 -TALKGROUP 1 (Secure capable , no Encryption keys loaded .) CONSOLE-2 -TALKGROUP 1 (Secure Capable , Encryption Keys loaded) VERSION #1.030 City of Fort Worth , Texas ASTRO 25 Migration , Citywide Trunked Radio System December 20 , 201 3 4-44 Acceptan ce Test Plan 2. TEST Step 1. Connect the KVL directly to the KMF Server via the com port and a serial cable to download the KM Ms for the consoles associated with it in the KMF . Power up the KVL . Note that the KMF to KVL connection can be direct or via modem . Step 2. Using the KVL menu , arrow to the KMF option and select it. Arrow to 'Direct/RS232' and select it. Step 3. The KMF is configured with what KVL manages what consoles . The KMF constructs the setup messages , encrypts them , and downloads them to the KVL. The KVL displays: "Downloading from the KMF/KVL." The download is complete when the KVL displays "Download Successful" and gives an audible alert. Step 4. Power down the KVL and disconnect it from the KMF . Step 5. Power up both , the KVL and CONSOLE-1 , connect them together via a KVL/console cable and , select through the KVL menu select the Update function . Step 6. The KVL automatically identifies the target and updates it. Upon completion of the download , the KVL collects the Console's acknowledgement and updates its memory status . The download is complete when the KVL displays "Download Successful " and gives an audible alert. Step 7. Reconnect the KVL to the KMF Server to return the acknowledgements . Using the KVL menu , arrow up to 'KMF' and select it. Arrow to 'Direct/RS232' and select it. Step 8. The KMF Server updates the Unit's currency and history. Step 9. The console will now have the current keys . Double -click on CONSOLE-1 in the list and verify that its status is marked current. Step 10 . Ver ify secure communications between CONSOLE-1, CONSOLE-2 and RADI0-1 on TALKGROUP 1. Pass Fail Motorola Confidential Restricted Use or disc los ur e of this proposal is subject to the restrictions on the title page Key Management Facility (KMF) Creating Console Unit (MCC 7500) Records in the KMF 1. DESCRIPTION In order to configure consoles for OTEK th e use r m ust create new console records in the KMF database . These records include the Console ID the UKEK and the Console RSI. U~til the cons,ole has re gistered for OTEK th e KMF will not be able to key manage the console using OTEK. The KMF will only accept the registration if the console has an ex isting record associated to the Console ID . SETUP A conso le must already be configured for OTEK ope ration us ing NM . It is also advisab le to zeroize the console by depressing the zeroize button. This will insure tha t th e store and forward is performed in the console w ith a clean default status . A console must also be provisioned with a console RSI , UKEK, KMF RSI , and Message Number Period from a KVL . This can be done through either the KVL 's manual mode or through RED Sto re and Forward (S&F ). VERSION #1.030 Motorola Confidential Restri cted Use or d isclos ur e of t hi s proposal is subject to t he rest ri ctions on th e t it le page 2. TEST Step 1. From the KMF Client window , select the Security menu and then the Infrastructure sub -menu and then se lect the Consoles menu item . Click the 'New' button. Step 2. Select the Consol es Group in the 'Se le ct Group' dialog bo x and clic k the OK button . Step 3. Crea te a Console Name and en ter a uniq ue Console RSI ID Step 4. Click the Select button under the Transport Systems section. Step 5. Select the desired Transport Services in the 'Select Transport Services' dialog bo x and click the OK button . Step 6. Select an A lgorithm and cl ick on the Se lect button under the UKEKs (Unique Key Encryption Keys ) secti on . Step 7. Select the UKEK in the 'Select UKEK' dialog bo x and cl ick the OK button . Note : pick a UKEK that is the same algo rithm of the Console Group Step 8. Select some or all of the Console Unit Capabilities in the Console Details sect ion. Step 9. Click on the 'Save and C lose ' button to end the process . Pass __ Fail __ City of Fort Worth, Texas ASTRO 25 M ig ration , Citywide T runked Rad io Syste m Decembe r 20 ,.2 013 Accept ance T est Plan 4-45 Over The Air Rekeying (OTAR) Full Update to Subscriber 1. DESCRIPTION The entire set of encryption keys (i n addition to other state parameters) are sent to a radio using the Full Unit Update command . Note : If the subscriber has just been powered up , make sure to let it stabilize for about 20 seconds . Observe the screen display and make sure the radio is conte xt activated . Another method to verify KMF registration is to observe the KMF event viewer to see that the test radio has registered. SETUP Two radios are required for this test. RADI0-1 will be the test radio that will be used for OT AR operation . RADI0-2 will be a reference radio. It is assumed that RADI0-1 initially does not have any traffic keys . Note : It is assumed that this test will occur after the Store and Forward tests . VERSION #1.060 City of Fort Worth , Texas ASTRO 25 Migrati on, Citywide Trunked Radi o System December 20, 2013 4-46 Acceptance Test Pl an 2. TEST Step 1. From the KMF Client window, select the Security menu and then the Radios menu item. Step 2. Select RADI0-1 from the list. Step 3. Click the 'Full Update' button , or right-click and choose 'Full Update.' Step 4 . From the Event Viewer in the KMF Client w indow, verify that RADI0-1 is shown under Operation Type. The operation is complete when the Operation Status is Complete and the Operation Progress is 100 %. Step 5 . The radio will now have the current keys . Double -click on RADI0-1 in the list and verify that its status is marked current. Step 6. Now that RADI0-1 is current , verify secure communications between RADI0-1 and RADI0-2 . Pass Fail Motorola Confidential Restricted Use or disclosure of this proposal is subject to th e restrictions on the t itl e pag e .. Over The Air Rekeying (OTAR) Clear Hello 1. DESCRIPTION The KMF operator can send a message to any rad io to confirm that radio is on the system . Note : If the subscriber has just been powered up , make sure to let it stabil ize for about 20 seconds . Observe the screen d isplay and make sure the radio is context activated . Another method to verify KMF registrat ion is to observe the KMF event viewer to se e that the test radio has registered. SETUP RADI0-1 T ALKGROUP 1 RADI0-1 -SITE -SITE 1 VERSION #1.030 Motorola Confidenti al Restricted Use or di sclosure of thi s proposa l is su bje ct t o th e res t rict ions on t he t itle page 2. TEST Step 1. From t he KMF Cli e nt window , select the Security menu and then the Radios menu item. Step 2 . Select RADI0-1 from the list. Step 3. Click the 'C lear Hello ' button , or right-click and choose 'Clea r Hello .' Step 4 . From the Event V iewer in the KMF Client win dow, verify that RADI0-1 is shown under Operat io n Type. The operation is complete when t he Operation Status is Comp lete and the Operation Progress is 100 %. Pass Fail City of Fort Worth , Texas AS T RO 25 Migrat ion, Ci tywide Tru nked Radio Sys tem December 20,.2013 Acceptance T est Plan 4-47 Over The Air Rekeying (OTAR) Encrypted Hello 1. DESCRIPTION The KMF operator can send an encrypted message to any radio to confirm that rad io is on the system and that its encryption services are funct ion ing . Note: If the subscriber has just been powered up , make sure to let it stabil ize for about 20 seconds . Observe the sc reen d isplay and ma ke sure the radio is conte xt activated . Another method to verify KMF registration is to observe the KMF event viewer to see that the test radio has regis tered . SETUP This test will require one radio (RADI0-1) on any talkgroup (T ALKGROU P 1 ). Note : The radio must be current in the KMF VERSION #1.060 City of Fort Worth , Texa s A ST RO 25 Migration , Cityw ide Trunked Radio System December 20 , 2013 4-48 Acceptance Test Plan 2. TEST Ste p 1. From the KMF Clien t w indow , se lect the Secu rity menu an d then the Radios menu item . Step 2. Select RADI0-1 from the list. ., Step 3. Click the 'Enc rypted Hello' button , or right- clic k and choose 'Encryp ted Hello.' Step 4. From the Event Viewer in the KMF Client window , verify that RADI0-1 is shown under Operation Type . The operation is complete when the Operation Status is Complete and the Operation Progress is 100%. Pass Fail Motorola Confidential Restricted Use or disc losure of t his pro posa l is s ubj ect to th e restrictio ns on t he t itle page ; Over The Air Rekeying (OTAR) Radio Inhibit 1. DESCRIPTION The KMF client can select any radio and completely disable the voice communications and user ergonomics using the Inhibit command . A KMF operator can send an encrypted command to inhibit a radio, making the radio unable to process any non-OT AR traffic . The enable command reverses these states . Note : If the subscriber has just been powered up , make sure to let it stabilize for about 20 seconds . Observe the screen display and make sure the radio is context activated. Another method to verify KMF registration is to observe the KMF event viewer to see that the test rad io has registered. SETUP This test w ill require two radios (RADI0-1 and RADI0-2 ) on any talkgroup (TALKGROUP 1 ). Note: The radio must be current in the KMF VERSION #1.040 Motorola Confidential Restricted Use or dis closu re of this proposal is subject to the restrictions on the title page 2. TEST Step 1. Verify communications between RADI0-1 and RADI0-2 . Step 2. From the KMF Client window, select the Security menu and then the Radios menu item . Step 3. Select RADI0-1 from the list. Step 4 . Click the 'Inhibit' button , or right-click and choose 'Inh ibit.' Step 5 . From the Event Viewer in the KMF Client window , verify that RADI0-1 is shown under Operation Type . The operation is comp le te when the Operation Status is Complete and the Operation Progress is 100 %. Step 6. Verify that RADI0-1 is turned off and cannot communicate with RADI0-2 . Pass __ Fail City of Fort Worth , Texas AS TRO 25 M igrati on , C ityw ide Trunked Radio System December 20 ,.2013 A cceptance Test Plan 4-49 Over The Air Rekeying (OTAR) Radio Enable 1. DESCRIPTION The KMF cl ient can select the prev iously inh ibited radio and complet ely enable the vo ice communications a nd user ergonomics us ing the enable command. A KMF operator can send an encrypted command to enable a radio , making the rad io able to process any non-OT AR traffic. Note : If the subscriber has just been powered up , make sure to let it stabilize for about 20 seconds. Observe the screen display and make sure the radio is context activated. Another method to verify KMF registration is to observe the KMF event v iewer to see that the test rad io has registered . SETUP This test w ill require two radios (RADI0-1 and RADI0-2 ) on any ta l kgroup (TALKGROUP 1). Note : The radio must be current in the KMF Note : RCM inhibits and OTAR inhibts work interchangeably. If t he radio , that is properly programmed , has been inhibited with OTAR , it can be re-enabled with RCM . VERSION #1.020 City of Fort Worth , Texas A ST RO 25 Mi g ration, C ityw ide Trun ked Radi o System December 20 , 2013 4-50 Acceptance Test Plan 2. TEST Ste p 1. Fro m th e KMF C l ient w indow, select the Security menu and then the Radios menu item . Step 2 . Select RADI0-1 from the list. .. Step 3. Cl ick the 'Enable' button , or right-click and choose 'Enable .' Step 4 . From the Event V iewer i n the KMF Client window , verify that RADI0-1 is shown under Operation Type . The operation is complete when the Operation Status is Complete and the Operation Progress is 100%. Step 5. Verify that RADI0-1 can now communicate with RADI0-2. Pass __ Fail __ Motorola Confidential Restricted Use or disclos ure of thi s pro posa l is subject t o t he res t rict io ns on th e t itle page Over The Air Rekeying (OTAR) Keyset Manipulation 1. DESCRIPTION The KMF application provides an operator with two keysets to perform rekeying operations . Only one keyset can be active in a device at a t ime , and an operator is ab le to rename and activate either keyset as necessary. Th is feature enables an operator to perform rekeying operations w ithout interrupting communications. Note : If the subscriber has just been powered up , make su re to let it stabil ize for about 20 seconds . Observe the screen display and make sure the radio is context activated . Another method to verify KMF registrat ion is to obse rve the KMF event viewer to see that the test rad io has reg istered . SETUP This test w ill require one radio (RADI0-1) on any talkgroup (TALKGROUP 1). RADI0-1 must have a display. VERSION #1.010 Motorola Confidential Restricted Use or disclos ure of thi s pro posal is su bj ect to th e res t rict io ns o n th e ti tle page 2. TEST Step 1. From t he KMF Client window , select the Security menu and then the Keysets menu item . Step 2. Double-click on Keyset 1. Step 3. In the dialog bo x , change the Keyset Name and press the 'Save and Close' button . Step 4 . Double-click on Keyset 2. Step 5. In the d ialog bo x , change the Keyset Name and press the 'Save and Close ' button. Step 6. From the KMF Client window , select the Security menu and then the CKRs menu item . Select the CKR and click Open . Veri fy that the Keyset names have changed . Step 7. Perform a Full Update on RADI0-1 . Step 8. On RADI0-1 's screen , use the arrow keys on the menu to se lect 'Keysets'. Use the arrow keys to scroll up /down through the list of ava ilable Keysets. Ve rify the new name ex ists in the Keyset list. Pass __ Fail __ City of Fort Worth , Texas ASTRO 25 Mig rat ion, C ityw ide T runked Rad io System December 20 ,.2013 A cceptance T est Pl an 4-51 Over The Air Rekeying (OTAR) KeysetChangeover 1. DESCRIPTION The Changeover procedure is initiated by the KMF and is used to direct a radio or a group of radios to perform a keyset changeover. This procedure is used to direct the intended radios to changeover from using one keyset to another keyset. SETUP Three radios are required for this test. RADI0-1, RADI0-2 and RADI0-3. Verify that Keyset 001 is the active keyset. VERSION #1.030 City of Fort Worth , Texas A STRO 25 Migra t ion , C itywide T ru nke d Rad io System Dece mber 20 , 20 13 4-52 A cceptance Tes t Plan 2. TEST Step 1. From the KMF Client window , select the Security menu and then the Keysets menu item. Step 2. Select Keyset 2 from the list and click the 'Set Active Keyset' button . Step 3. A window will pop up "Would you like to perform a keyset changeover at this time?" Select checkbo x to confirm you would like a Keyset Changeover to occur Step 4 . Select the checkbo x to perform a system wide keyset changeover. Note: Not selecting a checkbo x will require individual radios to be updated. Step 5. Depending on the size of the KMF database , the keyset changeover may take some time to complete . After the keyset changeover is complete , using RADI0-1 'son screen menu , verify that Keyset 002 is now the active keyset. Pass Fail Motorola Confidential Restricted Use or disc los ure of th is pro po sa l is subject to th e res t ricti ons o n t he t itl e page Over The Air Rekeying (OTAR) Rekey Request 1. DESCRIPTION A subscriber unit has the capability to request a rekey from the KMF . If the subscriber has lost or manually removed their TE Ks , or has possibly missed an update or keyset changeover, they may need to manually initiate a rekey . If all of the radio's keys are manually zerioized from the menu screen , the UKEKs will be lost , however the Key Loss Key (KLK ) wil l st ill decrypt inbound OTAR messages. The radios need to have this Key Loss Key feature turned on in the radio and in their KMF record. The rekey request wi ll not work if the radio is zeroized from the OT AR or if it zeroized by depressing its purple and orange buttons . In this situation , the radio would need to be store and forwarded . SETUP One radio (RADI0-1 ) and one site (SITE 1) are required to perform th is test. RADI0-1 must be affiliated to the system and registered with the KMF . SITE 1 must be operating in w ide area trunking , capable of supporting data service. Either use a KVL to delete the TEKs out of RADI0-1, or manually remove them through the radio 's menu. A UKEK shou ld stil l be in RADI0- 1. VERSION #1.030 Motorola Confidential Restricted Use or di sc losu re of th is pro po sal is su bject to t he rest rict ions on t he t itle page 2. TEST Step 1. Choose REKY from Radio 1 's display menu . Step 2. When the subscriber's display shows 'REQUEST REKEY , ' press the PTT to send the request. Step 3. Verify the subscriber shows 'PLEASE WAIT'. Step 4. Verify the subscriber displays 'RE KEYED'. Step 5. From the Event Viewer in the KMF Client window , verify that RADI0-1 is shown under Operation Type . The operation is complete when the Operation Status is Complete and the Operation Progress is 100 %. Pass Fail City of Fort Worth , Texas A STR O 25 Mi grat io n, Ci t ywi de Trun ke d Rad io Syste m December 20 ,.2013 A ccepta nce T es t Plan 4-53 Over The Air Rekeying (OTAR) Locked Out 1. DESCRIPTION The KMF operator can designate a radio as "Locked Out." When a radio has been locked out at the KMF , any rekey request from the radio user is denied and results in a "No Service" message from the KMF . Note: If the subscriber has just been powered up , make sure to let it stabilize for about 20 seconds. Observe the screen display and make sure the radio is context activated. Another method to verify KMF registration is to observe the KMF event viewer to see that the test radio has registered . SETUP RADI0-1 TALKGROUP 1 RADI0-1 -SITE -SITE 1 VERSION #1.040 City of Fort Worth, Texas ASTRO 2 5 Migration , Cityw id e Trun ked Rad io Sys t em De ce mber 20 , 20 13 4-5 4 A cce pta nce T es t Plan 2. TEST Step 1. From the KMF Cl ient window , select the Security menu and then the Radios menu item. Step 2. Select RADI0-1 from the list. Step 3. Click the 'Open ' button , or right-click and choose 'Open .' Step 4 . Under the Radio Details section , check the 'Locked-Out' option . Step 5. Click on the 'Save and Close' button to Step 6 . Step 7. end the process . From the RADI0-1 's menu , initiate a Rekey Request. From the Event Viewer in the KMF Client window ; verify that RADI0-1 is shown under Operation Type. Step 8. Verify that the Rekey Request from the radio user is denied and "unauthori z ed Un i t Detected . ID: XXX Rekey Reques t " will be d isplayed on KMF Event Viewer . Note that this will not impact normal voice operations , unless the radio does not have the correct TEKs. 'Locked out' denies the radio OTAR Motorola Confidential Restricted Us e or disclosure of th is proposal is subj ect t o the restr icti o ns on th e t itle pa ge Pass Fail Motorola Confidential Restricted Use or disclosu re of this proposal is subje ct to th e restri ctions on the title pag e City of Fort Worth , Texas AS TR O 25 Migration, Citywide Trun ked Radio Syste m December 20,.2013 A cceptance Test Pl an 4-55 Wide Area Trunking -FDMA Only Sites Talkgroup Call (Single Site) 1. DESCRIPTION The Talkgroup is the primary level of organization for communications on a trunked radio system . Radios with Talkgroup Call capability will be able to communicate with other members of the same Talkgroup . This provides the effect of a private channel down to the Talkgroup level. This test will demonstrate that a Talkgroup transmiss ion in itiated by a radio user will only be heard by system users who have the same Talkgroup selected . As with other types of ca lls , Talkgroup Calls can take place from anywhere in the system . SETUP RADI0-1 -TALKGROUP 1 RADI0-1 -SITE -SITE 1 RADI0-2 -TALKGROUP 1 RADI0-2 -SITE -SITE 1 RADI0-3 -TALKGROUP 2 RADI0-3 -SITE -SITE 1 RADI0-4 -TALKGROUP 2 RADI0-4 -SITE -SITE 1 VERSION #1.140 City of Fort Worth , Texas A STRO 25 Migra tio n , C itywide Trun ked Radio System Dece mbe r 20, 2013 4-56 Accepta nce Test Plan 2.TEST Step 1. Initiate a wide area call with RADI0-1 in TALKGROUP 1. Step 2. Observe that only RADI0-2 will be able to monitor and respond to the call. Step 3. Initiate a w ide area call with RADI0-3 in TALKGROUP 2 . Step 4 . Observe that only RADI0-4 will be able to monito r and respond to the call. Pass Fail Motorola Confidential Restricted Use o r di sclosu re of thi s pro pos al is subject to th e res t rict ions on th e ti tle page Wide Area Trunking -FDMA Only Sites Secure Operation (Single Site) 1. DESCRIPTION Digital encryption is used to scramble a transmission so only properly equipped radios can mon itor the conversation . A "Key" is used to encrypt the transmit audio. Only radios with the same "Key" can decrypt the audio and listen to it. SETUP RADI0-1 -TALKGROUP 1 (Secure TX Mode ) RADI0-1 -SITE -SITE 1 RADI0-2 -TALKGROUP 1 (Secure TX Mode) RADI0-2 -SITE -SITE 1 RADI0-3 -TALKGROUP 1 (Secure TX Mode & no , or incorrect Key ) RADI0-3 -SITE -SITE 1 RADI0-4 -TALKGROUP 1 (Clear TX Mode ) RADI0-4 -SITE -SITE 1 Note : The identical secure mode must be programmed into RADI0-1 , RADI0-2 , RADI0-4 and that RADI0-3 has no secure code loaded or has a un ique secure code from the other test ing radios . VERSION #1.060 Motorola Confidential Restricted Us e or disclosure of this proposal is subject to the restrictions on the ti tle page 2. TEST Step 1. Initiate a secure wide area call with RADI0 -1 on TALKGROUP 1. Keep this call in progress until instructed to end the call. Step 2. Observe that RADI0-2 will be able to monitor the call. Step 3. Observe that RADI0-3 does not receive the cal l. Step 4. Observ e that RADI0-4 w ill also receive the call even with the secure switch set to the non-secure mode of operation. Step 5. End the call from RADI0-1. Step 6. Respond to the RADI0-1 call with RADI0- 2. Ve rify that RADI0-1 and RADI0-4 hear the reponse but that RADI0-3 does not hear the response . Pass Fail City of Fort Worth , Texas ASTRO 25 Migrat ion, Citywide Trunked Radio System Decembe r 20,.2013 Accepta nce Test Plan 4-57 Wide Area Trunking -FDMA Only Sites Multigroup Call in Interrupt Mode 1. DESCRIPTION This trunking feature al lows an equ ipped radio user to t ransmit an announcement to severa l different ta lk groups simultaneously . The multigroup (MG) call can be flagged for Interrupt Mode in the User Con fi guration Manager (UCM ) database , this means that the trunked system does not wait for attached talkgroups to finish calls in progress . Upon dekeying , the interrupted radios will join the mu ltigroup call in progress . As with othe r types of calls , multigroup calls can take place from anywhere in the system . NOTE : A receiver interference fa ilure may appea r if RADI0-1 is no t immediately de keyed . This test is not recommended fo r single site systems as RF co ntention will occur. SETUP RADI0-1 -TALKGROUP 1 RADI0-1 -SITE -SITE 1 RADI0-2 -TALKGROUP 2 RADI0-2 -SITE -SITE 1 RADI0-3 -RANDOM (Not part of MG ) RADI0-3 -SITE -SITE 2 RADI0-4 -ATG 1 RADI0-4 -SITE -SITE 2 * TALKGROUP 1, TALKGROUP 2 are members of ATG 1. * RANDOM is any tal kgroup not a member of ATG 1. * Multigroups are set up through both the UCM and the Subscriber Prog ramming software . VERSION #1.150 City of Fort Worth , Texas AS T RO 25 Migration , Citywide T runked Rad io System December 20 , 2013 4-58 A cceptance Test P lan 2.TEST Step 1. Verify ATG 1 is set for the Interrupt mode in t he UCM database . Step 2. Using RADI0-1, initiate a call on TALKGROUP 1. Step 3. While RADI0-1 is keyed , init iate a multigroup call using RADI0-4 on ATG 1. Verify RADI0-2 receives the call but RADI0-3 does not unmute . Step 4. Dekey RADI0-1 and verify RADI0-1 unmutes and joins the multigroup call in progress . Pass Fail Motorola Confidential Restricted Use or disclosure of t his prop os al is s ubject t o t he res t rictio ns on the t it le page Wide Area Trunking -FDMA Only Sites Multigroup Call in Wait Mode (Single Site) 1. DESCRIPTION This trunking feature allows an equipped radio user to transm it an announcement to several different talkgroups simultaneously . The multigroup (ATG) call can be flagged for Wait Mode in the User Configu ra tion Manager (UCM ) database forcing all attached talkgroups to finish calls in progress before the trunked system will process the multigroup call. The system does not permit inactive , attached talkgroups to initiate Ta lk group Calls during the "wait" timeframe . As with other types of calls , multigroup calls can take place from anywhere in the system . SETUP RADI0-1 -TALKGROUP 1 RADI0-1 -SITE -SITE 1 RADI0-2 -TALKGROUP 2 RADI0-2 -SITE -SITE 1 RADI0-3 -RANDOM RADI0-3 -SITE -SITE 1 RADI0-4 -ATG 1 RADI0-4 -SITE -SITE 1 * TALKGROUP 1, TALKGROUP 2 are members of ATG 1. * RANDOM is any talkgroup not a member of ATG 1. * Multigroups are set up through both the UCM and the Subscriber Prog ramming software . VERSION #1.040 Motorola Confidential Restricted Use or disclos ure of this proposal is subject to the restrictions on th e t itl e page 2. TEST Step 1. Verify ATG 1 is set for the Wa it mode in the UCM database . Step 2. Us ing RADI0-1 , initiate a call on TALKGROUP 1. Step 3. While RADI0-1 is keyed , attempt to initiate a multigroup call using RADI0-4 on ATG 1. Verify RADI0-4 receives a busy tone because one of the talkgroups attached to ATG 1 is involved in a Talkgroup Call. Step 4. Key RADI0-2 and verify that a busy tone is received because the ATG 1 call is in queue . Step 5. Dekey RADI0-1 and verify RADI0-4 receives a callback. Step 6. Key RADI0-4 and verify both RADI0-1 and RADI0-2 hear the mu ltigroup call while RAD I0-3 does not unmute . Pass __ Fail __ City of Fort Worth , Texas ASTRO 25 Migration , C it ywi d e T run ked Radio System December 20 ,.2013 Acceptan ce T est Plan 4-59 Wide Area Trunking -FDMA Only Sites Continuous Assignment Updating 1. DESCRIPTION When a talkgroup is assigned a vo ice channel , the site controller cont inu es to trans m it th e channel assignment on the control channel for the duration of the talkgroup call . Rad ios coming into use on the system are automatically sent to voice channels with conversations in progress involving their selected ta lk groups . SETUP RADI0-1 -TALKGROUP 1 RADI0-1 -SITE -SITE 1 RAD I0 -2 -TALKGROUP 1 RADI0-2 -SITE -SITE 1 RADI0-3 -TALKGROUP 1 RADI0-3 -SITE -SITE 1 VERSION #1.060 City of Fort Worth , Tex as ASTRO 25 Migration, Citywide T runked Radio Sys tem Decembe r 20 , 2013 4-60 A cceptance Test Plan 2. TEST Step 1. Turn OFF RADI0 -1. Step 2. In it iate a Tal kg roup Call using RADI0-2 and verify RADI0 -3 hears the audio . Step 3. While the Tal kgroup Call is in progress , turn ON RADI0-1. Step 4. Observe that the rad io, which was just brought bac k into service , joins the Tal kgroup Call already in progress . Step 5. End the talkgroup call . Step 6. Switch RADI0-1 to anothe r tal kgroup. Step 7. Initiate a Tal kgroup Call from RADI0-2 to RADI0-3 . Step 8 . While the Talkgroup Call is in progress , set RADI0-1 back to the original tal kgroup . Step 9. Observe that RADI0-1 joins the Talkgroup Call already in progress. Pass __ Fail __ Motorola Confidential Restricted Use or disc los ure of t his proposa l is subject to the restrict ions on the t itle page Wide Area Trunking -FDMA Only Sites Call Alert (Single Site) 1. DESCRIPTION Call Alert is a tone page that allows a use r to selectively a lert another radio unit. The initiating radio will receive notification from the trunked system as to whether or not the page was recei ved by the target radio . Units rece iving a Call Alert will sound an alert tone. As with other types of calls , Call Alerts can take place from anywhere in the system . SETUP RADI0-1 -TALKGROUP 1 RADI0-1 -SITE -SITE 1 RADI0-2 -TALKGROUP 2 RADI0-2 -SITE -SITE 1 RADI0-3 -TALKGROUP 2 RADI0-3 -SITE -SITE 1 VERSION #1.050 Motorola Confidential Restricted Us e or disclosure of th is prop osa l is subject to th e restrictions on the t itl e page 2.TEST Step 1. Us ing RADI0-1 , press the page button . Step 2 . Enter the unit ID of RADI0-2 with the keypad , or scroll to the location where this ID is stored Step 3. Press the PTT to initiate the call alert (Page ). Verify that the RADI0-1 user receives audible indication that the Call Alert (Page ) was sent. Step 4 . Verify that RADI0-2 user receives an audible indication of an incoming Call Alert (Page) was sent but RADI0-3 does not. Step 5. Verify RADI0-1 gets an audible indication that the Call Alert (Page ) was successfully received at the target radio . Step 6. Turn off RADI0-2. Send a Call Alert (Page) from RADI0-1 to RADI0-2 . Step 7. Verify that the RADI0-1 user receives audible indication that the Call Alert (Page) was sent. Step 8. Verify RADI0-1 receives an indication that the Call Alert (Page ) was not successfully rece ived at the target radio. Pass __ Fail __ City of Fort Worth, Texas ASTRO 25 Migration , C it ywide Trunked Radio System December 20,.2013 Acceptance Test Plan 4-61 Wide Area Trunking -FDMA Only Sites Private Call (Single Site) 1. DESCRIPTION Private Call is a selective calling feature that allows a dispatcher or radio user to carry on one-to -one conversation that is only heard by the 2 parties involved . Subscriber units receiving a private call will sound an alert tone . As with other types of calls , Private Calls can take place from anywhere in the system. SETUP RADI0-1 -TALKGROUP 1 RADI0-1 -SITE -SITE 1 RADI0-2 -TALKGROUP 2 RADI0-2 -SITE -SITE 1 RADI0-3 -TALKGROUP 2 RADI0-3 -SITE -SITE 1 VERSION #1.080 City of Fort Worth , Texas ASTRO 25 Migration , Citywide Trunked Radio System December 20 , 2013 4-62 Acceptance Test Plan 2. TEST Step 1. Using RADI0-1 , press the Private Call (Call) button . Step 2 . Enter the unit ID of RADI0-2 with the keypad , or scroll to the location where this ID is stored. Step 3 . Press the PTT to initiate the Private Call (Call). Step 4 . Verify that RADI0-2 hears tones and the display indicates that a Private Call (Cal l) has been received , but RADI0-3 receives no indications. Step 5. Answer the Private Call (Call) at RADI0-2 by pressing the Private Call (Call) button. If RADI0-2 has a display , verify it shows the ID number or alias of RADI0-1. Step 6. Press the PTT switch on RADI0-2 and respond to the Private Call (Call). Note that if you do not press the Private Call (Call) button before pressing PTT, your aud io will be heard by all members of the talkgroup , and not just by the radio initiating the Private Call (Call). Step 7. Verify that RADI0-2 can communicate with RADI0-1. Step 8. Verify that RADI0-3 does not monitor the Private Call (Call). Step 9. End the Private Call (Call) by pressing the Private Call (Call) button or the Home button to return to normal talkgroup operation. Pass Fail __ Motorola Confidential Restricted Use or disclosure of this proposal is subject to the restrictions on the t itl e page Wide Area Trunking -FDMA Only Sites Emergency Alarm and Call with Talkgroup Revert (Single Site) 1. DESCRIPTION Users in life threatening situations can use the Emergency button on the radio to immediately send a signal to the dispatcher and be assigned the next available voice channel. An Emergency Call can be set to either Top of Queue or Ruthless Preemption operation. This test verifies the Emergency ID will appear on the display of the subscribers . To accomplish this , an Emergency Alarm and Call will be initiated from a portable which will be rece ived by a portable affi liated at any site of any zone in the system . A portable has the ability to revert to a specific talkgroup when an emergency is initiated . This is useful when the users have a designated talkgroup for handling emergencies . The revert ta lkgroup must be set in the portable via software . NOTE : If the subscriber does not have the PTT Display option , the Emergency ID will not be displayed . SETUP RADI0-1 -TALKGROUP 1 RADI0-1 -SITE -SITE 1 RADI0-2 -TALKGROUP 1 RADI0-2 -SITE -SITE 1 RADI0-3 -EMERGENCY TG RADI0-3 -SITE -SITE 1 * EMERGENCY TG is the ta lkg roup programmed for emergency revert . VERSION #1.040 Motorola Confidential Restricted Use or disclosure of th is p rop osal is subject t o t he rest rictio ns on the t itle page 2. TEST Step 1. Make a Tal kgroup Call from RADI0-1 and verify only RADI0-2 can hear the audio . Step 2. De key RADI0-1. Step 3. Using RADI0-1 se nd an Emergency Call by de pressing the emergen c y switch and then the PTT sw itch . .Step 4. **For rad ios with displays only ** Observe the display on RADI0-3 denotes an emergency and the unit ID or alias of the unit sending t he emergency and that RADI0-3 can hear RADI0-1's audio . Step 5. In addition observe that RADI0-2 can not hear RAD10-1 's audio . Step 6. Release the PTT switch on RADI0-1 and cancel the emergency. Pass __ Fail __ City of Fort Worth, Texas AS T RO 25 Mi g rati on , Citywide T ru n ked Radio Syst em Dece m be r 20,.20 13 Accept ance T es t Pl an 4-63 City of Fort Worth , Texas ASTRO 25 Migration, Citywide Trunked Radio System December 20 , 2013 4-64 Acceptan ce Test Plan Motorola Confidential Restricted Use or disc losure of this prop osa l is subject to the restrictions on the title page Wide Area Trunking -FDMA Only Sites Receive Only Radio 1. DESCRIPTION This test verifies that a s ubscriber can be set up for receive operation only. Setting a portable for "dispatch enabled" equal to no in the Radio User Capab ilities reco rd allows the rad io to receive , but not initiate group calls. Setting a portable for "Vo ice enabled " equal to no in the Radio User profile allows the user to receive dispatch ca ll s , but not originate or receive Unit-to-Unit or call alerts . SETUP RADI0-1 -TALKGROUP 1 RADI0-1 -SITE -SITE 1 RADI0-2 -TALKGROUP 1 RADI0-2 -SITE -SITE 2 CONSOLE-1 -TALKGROUP 1 VERSION #1.110 Motorola Confidential Restricted Use or di sc los ure of thi s proposa l is subj ect to th e rest rictions on the title page . 2. TEST Step 1. Set RADI0-1 's template for "dispatch enab led " equa l to no in the Radio User Capabilities Profile . This allows the rad io to receive , but not initiate group calls. Step 2 . Set RADI0-1 for "Vo ic e enabled " equal to no in the Rad io Use r. This all ows the user to rece ive dispatch calls , but not originate or receive Unit-to-Unit or call alerts . Step 3. Verify that the Site Access denial flag is set to either "Both " or "TG Only " or "E ither". Step 4. Make a call from CONSOLE-1 on TALKGROUP 1. Verify both Radios can hear the aud io. Step 5. Make a call from RADI0-2 and verify that both RADI0-1 and the CONSOLE-1 hear the call. Step 6. Verify that RADI0-1 is not granted a channel when it is keyed up . Step 7. Verify that CONSOLE-1 can not make a Private Call to RADI0-1 but can Private Call RADI0-2 . Step 8. Verify that RADI0-2 cannot make a Private Call to RADI0-1 but can Private Call CONSOLE-1 . City of Fort Worth , Texas AS TR O 25 Mi grati on, Ci t yw ide T runk ed Rad io Syst em Decembe r 20,.20 13 Accep tance T est Pl an 4-65 Pass __ Fail __ City of Fort Worth , Texas ASTRO 25 Migration , Cit ywide Trunked Radio System December 20 , 2013 4-66 Acceptance Test Plan Motorola Confidential Restricted Us e or disclosure of th is proposal is subject to the restrictions on the title page Site Trunking -FDMA Only Sites Site Trunking Talkg.;;..ro,;;..u ...... _ _. ?ite , 1. DESCRIPTIO When a Site goes into Site Trunking, radios with Talkgroup Call capability will be able to ____ ..,. communicate with other members of the same talkgroup at that same site . (Members of the same talkgroup at other sites will not be c!!?-1? 19 .Q1 0nitor those conversations ., S ETU ~ . RADI0-1 -TALKGROUP 1 RA[)I0-1 -SITE -SITE 1 RADI0-2 -';J"ALKGROUP 1 RA[S)I0-2 -SITE -SITE 1 RADI0-3 -'TALKGROUP 2, RAQIQ-3 -SITE -SITE 1 RADIQ-4 -TALKGROUP 2. BAQI0-4 -SITE -SITE ;J, Motorola Confidential Restricted Us e or disclosure of this proposa l is subject to the restrictions on the tit le page 2. TES f. ~t~p .1-Pl ace SITE ·1 into the Site Trunking mod_E?, via the Unified Event Manager (UJEM). Step _1 . Initiate a Talkgroup Call with B.fl.010-1 on TALKGROUP 1 at Sl"fE 1.,___-c___, ~t~p--9. Observe that only RADI0-2 will be able to monitor ahd respond to the call . Note that RADI0-3 AND RADIQ-4 are nof able to monitor the call since they_ are QI! k nother Talkgroup..:·, ----,,,,..,..,=~~ ~-,Q--4·_-l-nitiate a Talkgroup Call with RAE>IG-3 on TALKGROUP 2 at SITE 1..._~~--. §_tgQ 5. Observe that only RADI0-4 will be ~ble tq monitor .and respond to the c:_all . This· test was perfo~ed and p assefl during Phase 2 testing on 10/09 /2 012. . ------.. -- P ass ·Fail ~ . ---· -- City of Fort Worth , Texas ASTRO 25 Migration , Ci tywide Trun ked Radio System December 20 ,.2013 Acceptance Test Plan 4-67 Site Trunking -FDMA Only Site s Site Trunking Call Alert 1. DESCRIPTIO N Call Alert is a tone page that all ows a user to selectively alert another rad io unit. When a si te is in Site Trunking , Radios at the site wi ll only be able to Call Alert other radios at the same s ite . The initiating rad io w ill receive notification from the trunked system as to whether or not th ~ P.age was received by the ta rget radio . SETU P. RADI0-1 -TALKGROUP 1 RAD I0 -1 -SITE -SITE 1 RADI0-2 -TALKGROUP 2 RADI0-2 -SITE -SITE 1 * All Radios should b~ "Site Locked " VERSIO~ #1.94Q City of Fort W o rth , Texas ASTRO 25 Mig ration , Citywide Trunked Rad io System December 20 , 2013 4-68 Acce pt ance Test Plan 2. TEST Step 1. Place SITE 1 into the Site Trunking mode via the Unified Event Manager (UEM). ' Step 2. Using RADI0-1, press the page button . Step 3 . Enter the Unit ID of RADI0-2 with the keypad , or scrol l to the location wh §I§ this ID is stored . Step 4. Press the PTT to in itiate the Call Alert. Step 5. Verify that RADI0-2 received the Call Alert . Step 6. Exit the Call Alert mode and return to norma l talkgro l!J2 mode . This test was performed and passed du:r_.ing Phase_ 2 testing on 10/09/2012. Pass Fail Mot orol a Co nfiden tia l Rest ricted Use or disclosure of t his proposal is subject to the restr ictions on the title page Site Trunking Private Call . D6SCRIPTIO Private Calls is a selective calling feature thc!,f allows a dispatcher or radio user to carry on one-to-one conversation that is only heard by the 2 parties involved . When a site is in Site ~runking , Radios at the site will only be able to 8.r ivate Call other radios at the same site . SETU .1--..._~~"'"'"=""""'.'1 RADIG -1 -TALKGRGUP 1 RADI0-1 -SITE -SITE ~ RADIG-2 -TALKGROUP' 1 RADI0-2 -SITE -SITE 1 RADI0-3 -TALKGROUf:> 1 RADIG -3 -SITE -SITE 1 Moto rola Confid ential Restricted Use or disclosure of this proposal is subject to the restrictions on the title page 2 T~Sli ~i_ep 1. Place SITE-1 into the Site Tru nking ·mode via the Unified Event Manager (UEM). §te!22..: Using RADl 9 -1, pr§.~§. t.b_e P_r iyate Call button . ~p ~ !;nter the Unit ID of RADI0-2 with the keypad, or scroll to the location where this ID is stored . ........,. _ _,__"""'""'.":"l Step 4 . Press the PTT to initiate the ca ll. Ste p 5 . Verify that at RADI0-2 only tones are heard and the display indicates that a call has been received . ._ -----,-"""I! ~f.,...e12_6 __ -A--~swer the call at RADI0-2 ~y ~res~iflg the Private Call button . Verify its d1s12lay bhows the ID number or alias of the calling uni t......_ ______ ~~o;:---i (t=~-p·-7=_-P::-ress tl'ie PTT switch on RADI0-2 and respond to the call. Note that if you do not press the Private Call button befor pressing PTT, your au·dfo will be heard by all members of the talkgroup , ar:id not .by the radio initiating the Private Call §t.gp 8 ~.Verify only R.ADI0-1 hears the audio from RADI0-2 . --------..----, Step J. find the Private Call and re t urn to normal t alkgrou12 operation . Thls test was performed and pas§e d during p h ase 2 testing on 10/0J[2012. Pass · Fai l · . -~ --- City of Fort Worth , Texas ASTRO 25 Migration , Citywide Trunked Radio System December 20,.2013 Acceptance Test Plan 4-69 Site tr!Jnking -FQ.MA Only Sites Site Trunking Busy Queuing an Callbac~ 1. DESCRIPTIO 1 If no voice channel resources are available , radios requesting channels for ne conversations are placed in the busy queue . Users of the same priority will move through the queue in a FIFO (first in, first out) sequence; . however, users of higher priority will be inserted ahead of lower priority users in the queue. When a voice channel becomes available, the radio at the top of the busy queue gets a channel assignment and generates a callback tone . Th ~ callback alerts the user that a channe l assignment was made and transmitting is nQw 12ossible on the selected talkgrou ill SETUP. RADI0-._1 -_ T-A-LKGROUP 1 RADI0-1 -SITE -SITE 1 RADI0-2 -TALKGROUP 2 RADI0-2 -SITE -SITE 1 RADI0-3 -TALKGROUP 3 RADI0-3 -SITE -SITE 1 RADI0-4 -TALKGROUP 1 RADI0-4 -SITE -SITE 1 All radios are "Site Locked ." VERSION #1.090 City of Fort Worth , Texas ASTRO 25 Migration , Citywide Trun ked Radio System Decemb er 20 , 2013 4-70 Acceptance Te st Plan 2. TEST Step 1. Simulate a busy system by disabling al • channels at SITE 1 with the exceP.tion of the control chan0el and one voice. channel. Step 2. Initiate a Talkgroup Call with RADI0-1 an d observe that RADI0-4 receives the cal l. Keep this call in 12rogress until instructe~ to end the cal l. Ste.P. 3. Key RADI0-2 and observe that the radio receives a busy. Step 4 . K_ey RADI0-3 and gbserve t~at the radi g receives a busy. Step 5. End the Talkgroup Call established in Step 2. Step 6. Observe that RADI0-2 receives a callback prior to RADL0-3 receiving a callback. This test was performed and passed during Phase 2 testing on 10/09/2012. Pass __ Fail __ Motorola Confidential Restricted Us e or disc losure of this proposal is subject to the restrictions on the title page 1. DESCRIPTIO When a tal kg roup is assigned a vo ice chann e l) the site controller co r,i finues to transmit the channel assignment on the control channel fo f] the duration of the Talkgroup Gall. Rad ios _ coming into use on the system are automatically: sent to voice channel~ with conversations in progress invo lving their selected talkgroups. T tiis is demonstrated for a site in Site T ru r::i_k in_g_, S6Tlrn RADI0-.... 1 --..... T_A,,....,lK,..,.G~R~O~U~P...,.,1 RADIO-~ -SITE -Sl ifE 1 RADI0-2 -TALKGROUP 1 RADI0-2 -SITE -SIT~ 1 RADI0-3 -TAlKGROIJP tl RADI0-3 -S ITE -SITE * A:11 Ra ei os should be "Site Locked " Moto rola Confidenti a l Restricte d Use or d isclosure of this proposal is subject to the restrictions on th e t itle page 2.TESli Step_ 1. Place .SITE 1 into the Site Trunk ing mode via the Unified Event Man qg~r (U!;JJ}. --:,--,~ Step 2 . Turn OFF RADI0-1 . _ Step 3. lnitiat~ a Talkgroup Call 1:1_si~g RA. DIO -~ §tep 4. While the TalkgmuQ Call is in rogress ! t urn on RADI0-1 . 1-, ______ _,..,. 7 ---i SJ§p_§. Observe that RADI0-1 , which was just brought back into service , Joins the Talkgroup Call already in progress. ~p-6 . Release the PTT of RADI0-2. Step 7 . Switch RADI0-1 to TALKGROUP 2 . Step 8. Initiate a Talkgroup Call using RADI0-2 SteQ 9. Wh ile the Talkgroup Call is in progress , turn RADI0-1 back to TAL:KGROUP 1. Ste Q 10. Observe that RADI0-1 , which was just set back to TAlKGROUP i , joins th §_T alkgr.Qld R Qg]l_alr§_ad y: in Qmgress. . . . . . . . -, This test was performed and P<!Sse d during P_h a~e .'J testing_9n 1~0/09/2012 . i ~_ss __ f ~J I __ Ci ty of Fort W orth, Texas ASTRO 25 Migration , Citywide Trunked Radio System December 20 ,.20 13 Acce ptance Test Plan 4-71 ?ite Tru11king -FDMA Only Sites Site Trunking Emergency Call and Alarm 1. DESCRIPTIO "------~ This test verifies that Emergency Alarms and Calls can be in itiated by subscribers when th e registered site is in Site Trunking . With al ( portables registered on a Site Trunking site , a portable will initiate an Emergency Alarm bY, pressing the Emergency button . By pressing th PTT , an Emergency Call will be issued and the ID of the initiator will be displayed with a Emergency indication by the other subscrib_en~ on the same talkgroup . Note that for site trunking , Erner ency: Call OP.eration is always TO P-of Queue . SETU A . RADI0-1 -TALKGROUP 1 RADI0-1 -SITE -SITE 1 RADI0-2 -TALKGROUP 1 RADI0-2 -SITE -SITE 1 RADI0-3 -TALKGROUP 2 RADI0-3 -SITE -SITE 1 RADI0-4 -TALKGROUP 3i RADI0-4 :-SITE -SIT E 1 * All Rad ios should be "Site Loc ked" VERSION #1.040 Ci t y of Fort Wo rth, Texas A STRO 25 Migrat ion, Ci tywide Trunked Radio System Decem be r 20 , 2013 4-72 A cceptance Test Pl an 2. TEST. Step 1. Place SITE 1 into the Si te Trunking mod ~ via the Unified Event Manager (UEM). Step 2 . Simu late a busy system by disabling al • channels at SITE 1 with the exception of the control channel and one voice channel. Step 3. Press the PTT on RADI0-3 and hold th PTT switch until instructed to release . Step 4 Key RADI0-4 and obse e that the radi 1 receives a busy Step 5. Us ing RADI0-1 , initiate an emergencY, alarm followed by an emergency cal l. Ste Q 6. Observe that RADI0-1 cannot transmit due to the voice channel being busy..o Step 7. Release the PTT switch on RADI0-3 Step 8. Observe that RADI0-1 can now procee w ith the call and RADI0-2 receives the call. Also observe that the display on RADI0-2 denotes an emerge l}9'. an the ID of the u it sending the emergency. Step 9. End the emergency call and ve ri fy tha l RADI0-4 gets a callback . Step 1 O. Restore all chan els to service . This test was performed and passed during Phase 2 te sting on 10 /09 /2012 . Pass __ Fail __ Motorola Confi de ntia l Restricte d Us e o r di sc los ure of thi s proposal is su bj ect to t he rest ricti o ns on the t itle page Site -Trunking --FDMA o ·n( Site s S ite Trunking Wide Area Resevery 1. DESCRIPTION ...._ __ ,.., __ . __ " 'A site in Site Trunki ng will transition to W id e t rea Trunking when all failures have been f leared and when the Unified Event Manager UEM has set the site~ status to W ide ~rga, {\II subscribers shou ld transition from Site Trunking to Wide Area Trunki g a!71d continue to pJ:.ocess calls. · 1 s11::ruP. I ....._=------RADI0-1 -TALKGROUP 1 RADI0-1 -SITE -Sl ifE 1 RADI0-2 -TALKGROL!JP 1 RADI0-2 -SITE -SITE 1 Site needs to be laced in Site Trunking-via the UE -1c All Radios shGuld be "Site Locked' Y iRSIQN #1.030 Motorola Confid enti al Rest ricted Use or disclosure of this proposal is subject to the restrictions on the title page 2. f EST StE.)p __ 1._From the UEM set the status of SITE 1 to W ide Area and clear any system errors t hat may have Qlaced SITE 1 i nto Si t e T runking . ' ~tep 2 . Verify that the status of SITE 1 i .__ __ t oneWat~~ and ~EM reflect that SITE 1 r as trans 1t1oned into Wide Area il"rlinking . !te r.i 3 . Verify that RA~_.,...D,---10---1 -a~nd_R_A~D-I0---2-n-o _.,..._... __ longer display Site Trunking . ~ Ste12 4 . Verify communications between RADI0-1 --.....:;:md RADI0-2. $...!§Q....5. Verify that Zone ... w-·a-tc-h-ca-n-n_o_w_m_o_n-ito-n t he status of S TE 1 l'fhis test was perforri:J.e d· and passed during Pha§.e 2 te~ting_oI! l Q/09/2012. Pass City of Fort W o rth, Texas ASTRO 25 Migration , Citywide Trunked Radio System December 20 ,.2013 Acceptance Test Plan 4-73 System Reli ~bility Features Redundant Zone Controller Switching/Automatic Switchover: In a non-DSR configuration the Zone Controller subsystem uses two Zone Controllers in a redundant configuration . The backup Zone Controller is made active either upon the loss of the active ZC or upon a user command from the Unified Network Configurator (UNC). In a DSR configuration there are 4 Zone Controllers in a redun~ant configuration . Any one of the 4 coul ~ be active to keep the Zone Sites in Wide Area Trunking. If using the Dynamic Resilience Zone configuration the Unified Event Manager will report the Zone Controller switchover in both Unifieq Event Managers (UEM ). SETUP RADIO 1 -TG 1 RADIO 1 -SITE ~ SITE 1 RADIO 2 -TG 1 RADIO 2 -SITE -SITE 1 RADIO 3 -TG 1 RADIO 3 -SITE -Site 1 VERSION #1.020 City of Fort W o rth , Texas ASTRO 25 Migration , Citywide Trunked Ra dio System December 20, 2013 4-74 Accepta nce Te st Plan 2. TEST Ste p 1, Verify the state of the current Zone Controllers is Active or Standby in th Unified Network Configurator (UNC). (There will be 2 Zone Controllers in sing le Zone or 4 in the case of DSR zones .) Step 2. Verify in the Unified Event Manage r. (UEM) that the Standby Zone Controller is _in "Synchronization ComR ete" stat~ pnor to switching . Step 3. Reset the active Zone Controller via the Unified Event Manager (UEM) diagnost ic. Step 4 . Verify using UNC , UEM and ZoneWatch (if applicab le) that the standby Zone Controller becomes active and brings al ( sites back wide. Wait for the Rad ios ta • settle out the site affiliations . Step 5. Key RADIO 1 and verify that RADIO 2 and RADIO 3 hear the audio Step 6. End the call from RADIO 1. Step 7. Verify that Zone Controller that was rese comes back up to an "Enabled " and "Standby " state . This test was performed and p asse d during Phase 2 testing on 10/0 9/2 01 2 . Pass Fail Mot orola Confi de nti al Rest ri cted Use or disclosure of this proposal is subject to the restrictions on the title page S stem R.eliamili!i' Features ~ DliSCRIPTION --~-Communication between the Master Site and . the Remote Site can take place over dedicated redundant links. The two links between th~ Master Site and the Simulcast Prime Site oper:ate in a hot/standby mode. The system .wil l switch to the backu[;! link if the main LAN qr WAN link fails Note that tlie Primary Site Router, if functional ,i will always be tl:ie active router. The Secondary Site Router will only take over when the Primary Site Routerj§_ malfunctioni o.g_. SETsUP. RADI0-1 -TALKGROUP 1 RADIG-1 -SITE -SITE 1 RADI0-2 -TALKGROld.lP 1 RADIP-2 -SITE -SITE 1 * SITE 1 should have red\.mda Q!JiD ks to the Mast~r ~ite ., Motorola Confidential Restricted Use or di sclos ure of t h is p roposa l is subject to t he restrict ions on the title page ~te·p 1. Initiate a TalkgrOU[;! Call with RADI0-1 on TALK~R()Up 1, ~te p ~-Observe that RA DI0-2 is able to monitm p nd re ~Rond to the cal l. Step 3. Remove the WAN link from the active _r:_outer at the Simulcast Prime Site . fil~P. 4-,_ Initiate a Talkgroup Call .with RADIP-1 OIJ 16.1,,.!S§RQU~.t St~p_§.,_ Q bserve that RADl'c:f-2 is abl e to monito n ,e nd respond_ to the cal l. I!!! -·· -~ .. g ~p..&:_ Replace-the WAN link connection that was removed in Step 3 . This tes t was performed and paS§~d during phase i t ~~ting_Q..I_! 10/Q9 /_I 012. Pass Fail §ystem _Re_liability Features, - City of Fort Worth , Texas AS TRO 25 Mig rat ion , Ci tyw ide T r unked Radio Syst em December 20 ,.20 13 Accept ance T est Pl an 4-75 Redundant Site Controlle t Switching/User Initiated Switchover 1. DESCRIPTIO N .. __ _ The Simulcast subsystem uses two Site Controllers in a redundant configuration . The backup Site Controller is made active eithe r upon the loss of the active Site Controller or upon a user-initiated command from the Configuration Service Software . · SETUR RADI0-1 -TAl..::KGROUP 1 RADI0-1 -SITE -SITE 1 RADI0-2 -TALKGROUP 1 RADI0-2 -SITE .-SITE 1 VERSION #1.050 City of Fort Wo rth , Texas AST RO 25 Migration , Citywide Trunked Radio System December 20 , 2013 4-76 Acceptance Test Plan 2. TEST Step 1. Us ing CSS , connect to the ACTIVE sit controller , and read the configuration data .1 Step 2. Select the "Status Panel Screen" from the Service Pull-Down Menu . Step 3. Initiate a Ta lkgroup Call with RADI0-1 an d observe that it is received by RADI0-2 . Keep this call in 12 rogress until instructed to end the call · Step 4. Disab le the ACTIVE site controller b placing it into the "USER DISABLED" state. This will force the INACTIVE site controller to become ACTIVE and tak over control of the s stem Step 5. Notice that the call set-up in Step 3 i~ unaffected b_y the site controlle r sw itchove r. Step 6. Step 7. Notice that the call is granted , and that RADI0-1 receives the new · transmission . This test was performed and p assed during Phase 2 testing on 10/09/20 12_. Pass Fail Motorola Confid e nti al Restricted Use or disc losure of this proposal is subject to the rest ri ctions on t he t itle page Sys_!e~J~.eliabili!Y Features --~ ----......... -[' DESCRIPiTIQ>N This test shows that i n the eve nt of a com.plete failure of the Master Site, the Simulcast Sites will revert to Site Trunking . To simulate the failure of the entire Master site, the WAN links from the Master Site to the Simulcast Site -- Routers will be aisconnected. ~his will isolate the Simulcast cells (Layer 1 §..IJ.d L2 yer 2)_ fro m_ t!J e Master Sit~ RADIQ-1 -TALKGR.OUP 1 RADI0-1 -Sll'c -SITE 1 RADI0-2 -TALKGROUP 1 RADI0-2 -SITE -SITE 1 RADI0-3 -TALKGROUP 2 RADI0-3 -SIT~ -SITE RADI0-4 -TALKGROUP 2 RADI0-4 -SITE -&ITE 2 TAL GROUP 1 -SITE .ACCl::SS SITE 1 ONLY. TALK~_ROUP 2 -SITE ACCESS _SITE 1_ GNL Yi V ERSION #1.Q90 Motorola Confidential Restricted Us e or disclosure of this proposal is subject to the restrictions on th e title pag e file i J :·!.r:i_i tiate a TALKGROUP 1 c a ll from RADI0-1. Verify that RADI0-2 recei v es the audio . Initiate a TALKGROUP 2 cal i from RADI0-3. Verify .J.b at RA.Ql0-4 - receives the audio . $t_ep_2 . _ R_emove the WAN lin,ks "Hom th e Master Site to the Simulcast Sites . Note this can be done either at the Master Site o r _ ;:it both Simulcast Prime Sites . - §i§P. 3. Verify that the Sim_ulcast Site enters Site 'T runking . ~l~P.-4 . initiate a TALK<:3ROUP 1 call fro m RADI0-1. Verify that RADI0-2 r ... ec-e-iv-e=s the audio. Initiate a TALKGROUP 2 call ,·-from RADI0-3. Verjfy_ that RADI0-1 receives the audio . Reconnect the WAN site links. Verify th si t both Simulcast Sites return to Wide _ Area ifr,unking --- §!eP. 7. Initiate a TALKGROLJP 1 call fro RADI0-1 . Verify tnat RAD! 0-2 receive ~ the audio. Initiate a TALKGROU!=> 2 call 1fr0m RAIJI0-3. Verify_j h9t RAD10-4j . ~ceives th~ audio . This test was performed and pass~d durll!g Phas~. 2_ !~sting_ op. 1O(Q9J).0 12. F'·ass Fail ~------ City of Fort Worth , Texas ASTRO 25 Migration , Citywide Trunked Radio System December 20,.2 013 Acceptan ce Test Plan 4-77 Signoff Certificate By the ir signatu res below, the follow ing w itnesses certify they have observed the In-Field System Acceptance Test Procedures . Signatures WITNESS : Date : ------------------ Please Print Name :------------------- Please Print T itle :------------------ W ITNESS : Initials : D ate : ------------------ Please Print Name : In itials : ------------------- Please Print Title :------------------ WITNESS : -----------------'D ate: __ _ Please Print Name : ------------------- Please Print Title : ------------------- City of Fort Worth , Texas A STRO 25 M ig rati on , Cityw ide T ru nked Rad io System December 20 , 2013 4-78 A ccepta nce T est Pla n Initials : Motorola Confidential Restricted Use or disclos ure of th is proposal is subj ect to t he re st rict io ns on t he ti tl e page ... 1A .1 Introduction This document is an addendum to Section 04 in the Contract ATP document. Buford Goff and Associates created a Requirement Verification Traceability Matrix -Infrastructure document which out-lined several Failure Modes spoken about in Section 2.4 of the System Description which did not have test procedure verification test scripts. The tests in this document were created to verify the Failure Modes as described in the System Description that were not covered by other test procedures. Most of the Requirement Verification Traceability Matrix tests created in May of 2011 were performed as part of Phase 2 Testing. Two of these tests were not performed at that time because they required taking down half the channels on the only layer active with the Phase 2 cut-over. It was determined to perform these tests at Phase 3 cut-over on layer 02. Since the creation of this set of tests in 2011, and the Phase 2 cut-over in 2012. The implementation of the Phase 3 system has changed. These tests if performed must be performed during the week of December 02 of 2013 before Layer 02 users are activated, and before the performance of the Coverage Acceptance Plan beginning on December 09, of 2013. This document has been edited to include only the two remaining tests: 1. Prime Simulcast Site LANSW Failure 2. Simulcast Remote Site LANSW O 1 failure These tests have been modified to be performed on Layer 02 This document originally covered the testing of the Alcatel polling engine. The implementation of the Alcatel polling engine has been postponed until post -Phase 3 implementation. To test the Alcatel polling engine it will require the installation and implementation of the polling engine. Since the polling engine provides interpretation of Alcatel alarms to the resident Moscad system, the functionality of Motorola Confidentia l Restricted Use or City of Fort Worth , Texas disclosure of this proposal is subject to the ASTRO 25 Migration, Citywide Trunked Radio System restrictions on the title page December 20 , 2013 Addendum Acceptance Test Plan 1A-1 this polling engine will not be a formal test procedure, but will be a demonstration that the alarms provided by the Alcatel microwave system will b e di spl ayed on the Moscad Graphics Work Stations that are part of the Project 25 system infrastructure . The two remaining t ests in this document are modified to reflect that th e tests will be performed on the Layer 02 prime site and on (a) Layer 02 remote site. City of Fort Worth , Te xas A STRO 25 Migration, Citywide Trunked Radio System Dece mber 20 , 2013 1A-2 Addendum Acceptance Test Moto rola Confidential Restricted Use or d isc losu re of this proposa l is subject to the restrict ions on the t it le page ·"' 1.2 RVTM Additional Test Scripts Prime Simulcast Site LANSW failure 1. DESCRIPTION The Simulcast Prime Site employs S imulcast Prime Site Ethernet Switches. Failure of one Ethernet Switch at the Prime site will result in a loss of channels based on the comparators connected to the failed switch. The City of Fort Worth system has two Simulcast Prime Sites . For Phase 3 the system has two of these Prime Sites , since Layer 01 will have active users at the time of the performance of this test, these tests will be performed on Layer 02t. This site is co-located with the remote site at Rolling Hills , therefore these tests will be performed at the Rolling Hills site . Note this test will require a person to observe the UEM terminal which is not located at this site . The City of Fort Worth Prime Site for Layer 02 divides the channels between the to LANSWs , odd channels for LANSW 01 and even channels for LANSW 02. The site GPS and NFM SDM3000 unit are also plugged into LANSW 01 . The failure of LANSW 01 w ill cause the NFM site environmental alarming from the prime site to fail , it will also cause the GPS at the site to lose NTP , however the GPS will free-run and supply clock to the comparators . The system channels available to the subsystem will be cut- in -half. The system will st ill communicate with the Master Site , and calls will be processed normally on the remaining channels. SETUP RADI0-1 -TALKGROUP 1 RADI0-1 -SITE -1 RADI0-2 -TALKGROUP 1 RADI0 -2 -SITE -1 RADI0-3 -TALKGROUP 2 RADI0-3 -SITE -1 RADI0-4 -TALKGROUP 2 RADI0-4 -SITE -2 VERSION #1.140 Motorola Confidential Restricted Use or disclosure of this proposal is subject to the restrictions on the title page 2. TEST Step 1. Turn off LANSW 01 on the Layer 02 prime site Step 2. Observe that the LANSW 01 shows failure on UEM Step 3. Observe that the odd channels on the Prime Site are no longer available on System Watch but the Layer will still be in wide area trunking. Step 4. Note that if the active control channel on the system was an odd channel when the LANSW was turned off the system w ill roll the contro l channel to an even channel. Step 5. Initiate a Talkgroup Call with RADI0-1 Step 6. Observe that RADI0-2 is able to monitor and respond to the call . Step 7. Initiate a Talkgroup Call with RADI0-3 Step 9. Observe that RADI0-4 is able to monitor and respond to the call . Step 10. Observe that the talkgroup calls take place on an even numbered c hannel. Step 11. Turn LANSW 01 on -Observe the alarms clear on UEM , and that on System Watch all channels now become active in wide-area trunking mode . Pass __ Fail __ Simulcast Remote Site LANSW 01 failure City of Fort Worth , Texas ASTRO 25 Migration , Ci tywide Trunked Radio System December 20 , 2013 Addendum A ccepta nce Test Plan 1A-3 1. DESCRIPTION The Simulcast Remote Site employs Simulcast Remote Site Ethernet Sw itc hes. Failure of one Ethernet Switch at the Remote site will result in a loss of channels based on the number of channels connecte d to the failed switch . The City of Fort Worth system has two Simulcast Prime Sites . For Phase 3 the system has two of these Prime Sites , since Layer 01 will have active users at the time of the performance of this test , these tests wi ll be performed on Layer 02t. This site is co -located with the remote site at Rolling Hills , therefore these tests will be performed at the Rolling Hills site. Note this test will require a person to observe the UEM terminal which is not located at this site. The City of Fort Worth Rolling Hills Remote Site for Layer 02 divides the channels between the two LANSWs, odd channels for LANSW 01 and even channels for LANSW 02 . The site GPS is also plugged into LANSW 01 . The failure of LANSW 01 will cause the GPS at the site to lose NTP , however the GPS will free- run and supply clock to the channels. The system channels available to the subsystem will be cut-in-half. The system will still communicate with the Prime Site , and calls will be processed normally on the remaining channels . SETUP RADI0-1 -TALKGROUP 1 RADI0-1 -SITE -1 RADI0-2 -TALKGROUP 1 RADI0-2 -SITE -1 RADI0-3 -TALKGROUP 2 RADI0-3 -SITE -1 RADI0-4 -TALKGROUP 2 RADI0-4 -SITE -2 City of Fort Worth, Texas ASTRO 25 Migration , Citywide Trunked Radio System Decemb er 20 , 2013 1A-4 Addendum Acceptan ce Test VERSION #1.140 2. TEST Step 1. Turn off LANSW 01 on the Layer 01 remote site Step 2. Observe that the LAN SW 01 shows failure on UEM -this should also display that there is no communications with the GPS Step 3. Observe that the odd channels on the Layer 01 are no longer available on System Watch but the Layer will still be in wide area trunking. Step 4 . Note that if the active control channel on the system was an odd channel when the LANSW , was turned off the system will roll the control channel to an even channel. Step 5. Initiate a Talkgroup Call with RADI0-1 Step 6. Observe that RADI0-2 is able to monitor and respond to the call. Step 7. Initiate a Talkgroup Call with RADI0-3 Step 9. Observe that RADI0-4 is able to monitor and respond to the call. Step 10. Observe that the talkgroup calls take place on an even numbered channel. Step 11. Turn LANSW 01 on -Observe the alarms clear on UEM , and that on System Watch all channels now become active in wide-area trunking mode. Pass __ Fail Motorola Confidential Restricted Use or disclosure of this proposal is sub j ect to the restrictions on the title page Signoff Certificate By their signatures below, the following witnesses certify they have observed the In-Field System Acceptance Test Procedures . Signatures WITNESS : -----------------:Date: __ _ Please Print Name : __________________ _ Initials: Please Print Title : __________________ _ WITNESS: ----------------.:Date: __ _ Please Print Name : ___________________ _ Initials : Please Print Title : __________________ _ WITNESS : D ate: ------------------ Please Print Name: __________________ _ Initials : Please Print Title : _________________ _ Motorola Confidential Restricted Use or disclosure of thi s proposal is subject to th e restrictions on the title page City of Fort Worth, Texas AS TR O 25 Migration, Cityw ide Trunked Radio System December 20, 2013 Addendum Acceptan ce Test Plan 1-A 5 4-14 City of Fort Worth , Texas ASTRO 25 Migration , Citywide Trunked Radio System December 20 , 2013 Acceptance Test Plan Motorola Confidential Restricted Use or disclosure of this proposal is subject to the restrictions on the title page Addendum 1 Fort Worth, TX Public Safety PS L TE System December 20, 2013 A./ {/ Data Restrictions _/ _,, ,- / This proposal is considered Motorola confidential and restricted. The proposal is submitted with the r estr]E!!gri ttl;t it is to be used f or eva luation purposes only, and is not to be disclosed publicly or in any manner to anyone other than those employed by the Fort Worth, TX req ui red to evaluate this proposa l without the express perm ission of Motorola Solutions, Inc. / ,-,,. MOTOROLA and t he Stylized M Logo are registered in the U.S. Patent & Trademark Office. All other product or service names are the property of their respective owners.© Motoro la Solutions, Inc. 20 11 1507 LBJ Freeway, Ste 700, Farmers Branch, TX 75234 Section 1 . System Des cri ptio n ........................................................................................ 1-1 1.1 Fort Worth Public Safety PS LTE System ............................................................. 1-1 1.1 .1 Network and Backhaul Design .......................................................................... 1-2 1.2 System Design ........................................................................................................ 1-4 1.2.1 City of Fort Worth -Equipment Responsibilities .............................................. 1-5 1.3 Remote Agency Core /Gateway Architectural Considerations ................................ 1-6 1.3.1 Optional Prioritization Service Manager (PSM) -Not Included ........................ 1-6 1.4 PS L TE Solut ion Architecture ................................................................................. 1-7 1.4.1 User Equipment (UE) ........................................................................................ 1-7 1.4.2 E-UTRAN .......................................................................................................... 1-8 1.4 .3 Evolved Packet Core (EPC) -Harris County ................................................... 1-8 Section 2. Statement of Work .......................................................................................... 2-1 2 .1 Statement of Work for Imp lementation ................................................................... 2-1 2 .1.1 General Information .......................................................................................... 2-1 2 .1.2 System Implementation Overview .................................................................... 2-1 2. 1. 3 Detailed Description of Work ............................................................................ 2-2 2.1.4 Fort Worth Responsibilities and Assumptions for Hosted Harris County PS LTE EPC 2-2 2. 1. 5 General Project Responsibilities ....................................................................... 2-3 2. 1. 6 Project Initiation and Kickoff. ............................................................................. 2-6 2. 1. 7 Design Revie w .................................................................................................. 2-7 2. 1. 8 Order Processing ....................................................................................... 2-102-9 2. 1. 9 Civil Work and Site Development ............................................................ 2-11 -2-4() 2.1.10 Implementation ...................................................................................... 2-1~ 2.1. 11 Functional Acceptance Test Plan (FA TP) .............................................. 2-17-2-4-e 2.1 .12 Training .................................................................................................. 2-18~ 2. 1. 13 System Documentation .......................................................................... 2-18~ 2.1.14 Project Finalization ................................................................................. 2-19~ 2.1.15 Warranty. ................................................................................................ 2-19~ Section 3. Acceptance Test Plan ..................................................................................... 3-1 3.1 Introduction ............................................................................................................. 3-1 3 .1.1 Network Attachment Test .................................................................................. 3-1 3.1.2 PS LTE Link Verifi ca tion Test ........................................................................... 3-2 3.1.3 eNodeB Handoff ............................................................................................... 3-2 3. 1. 4 Respon sibility Matrix ......................................................................................... 3-3 Section 4 . Statement of Work for Support ...................................................................... 4 -1 4~1 Warranty and Maintenance Support for the LTE Subsystem ................................. 4-1 Fort Worth , TX Publi c Safety PS L TE System December 20, 2013 T able of Contents -1 - 4.1.1 Warranty and Support ...................................................................................... 4-1 Fort Worth, TX Public Safety PS L TE System May 10 , 2011 -2 -Table of Contents .. 1.1 Fort Worth Public Safety PS L TE System This document describes the Public Safety PS LTE System ("System") or Fort Worth. The following sections define the system design and so luti on, based upon Motorola's understanding of Fort Worth's requirements. The PS LTE solution for the City of Fort Worth includes: + Radio Access Network (RAN) components: • Two eNodeB transceiver sites, AC powered indoor eNodeB cabinets • Backhaul Termination Equipment at each eNodeB site • 100' to 300' three-sector Antenna Systems with Transmission Lines at each eNodeB site • Two eNodeB Software Licenses + Remote Agency Core/Gateway components Remote Agency Core/Gateway: • Converged Packet Gateway (CPG) • Aggregation Switch, Firewall and Security Gateway + User Equipment: • (10) Vehicular Subscriber Modem (VSM Model 1) ;Model 1 • (5) USB Modem + Professional services: • Project Management • System Engineering • Network Engineering • System Technologist • Installation • Deployment and Configuration • Functional Acceptance Tests • One Year Warranty + Fort Worth provided components: • Firewall and Network Equipment needed to connect the CPG to the Fort Worth enterprise network . • Any additional equipment needed to facilitate the required transport connection to the Harris County PS LTE EPC. • Any additional equipment needed to facilitate the required site backhaul connection from the Motorola provided aggregation switch to the eNodeB sites. Motorola Confidential Restricted Use or disclosure of this proposal is · subject to th e restrictions on the titl e page Fort Worth , TX Public Sa fety PS L TE System December 20 , 2013 System Description 1-1 1.1.1 1.1.1.1 Network and Backhaul Design Required, but not included in this proposal, are the services provided by the PS L TE Evolved Packet Core (EPC) in Harris County. The City of Fort Worth is responsible for all necessary negotiations , coordination and inter-agency agreements with Harris County for use of their PS L TE Core. The inter-agency agreements m u st define the system features and functions that Harris County will provide with the use of the Harris County EPC. The agreement should include eNodeB and CPG provisioning, operations and management, as well subscriber and SIM provisioning. Additionally, our proposal does not include any additional subscriber software licensing to support the (15) total proposed Fort Worth PS LTE subscribers on the Harris County PS L TE EPC. Should Harris County's subscriber licensing be unable to accommodate these two additional subscribers, the additional costs will be a responsibility of Fort Worth. The City of Fort Worth 's eNodeB's and Remote Agency Core/Gateway, and the Harris County EPC will function as one system and network deployment. All Fort Worth PS LTE user data will be routed through the CPG at Fort Worth and will stay within the Fort Worth RAN and enterprise network . In most use cases only the system control data will traverse the transport link back to Harris County EPC. There is the possibility that user data will traverse the transport link between Fort Worth and Harris County when a Harris County PS LTE user roams onto the Fort Worth RAN or a Fort Worth user roams onto the Harris County RAN. To accommodate user roaming between the two RAN s, Motorola recommends a 3 Mbps link be provisioned to connect the CPG to the Harris County EPC. As the system grows with additional eNodeBs, and users are added to the system, additional bandwidth on the transport link will be required. Backhaul Requirements We assume that the City of Fort Worth will provide a Layer 3 switch with MPLS capability and available 1 Gbps Ethernet port with a 1 OOMbps Committed Information Rate (CIR), with the connection being 1 OOOBaseTX to connect to their backhaul network at each eNodeB site location. Motorola's demarcation point will be the backhaul termination switch provided at each eNodeB. Motorola will connect the cables from the Backhaul Termination E quipment (BTE) to the Fort Worth demarcation switch within 25 'of each PS LTE eNodeB equipment rack within the same equipment room. Should our assumptions change, the network design, system design and equipment must be revised, and these cost differentials will be a responsibility of the City of Fort Worth and will not be provided as part of the proposed incentive . Fort Wo rt h, TX P ub lic Safety PS L TE System December 20 , 2013 Mo torol a Co nfidenti al Restricted Use or disc losure of this proposal is subject to the restri ctions on the t itle page 1-2 System Description 1.1 .1.2 All site data will be backhauled to a Fort Worth aggregation point. At this location, the site and user control data will be forwarded to the Harris County core for processing. Motorola recommends that the capacity of the link between Fort Worth and Harris County shoul d be, at a minimum, 3Mbps, in both directions. Additional bandwidth will be required when Fort Worth adds users or sites to the proposed PS LTE system. The specifications for these links are as follows: + Symmetric link capacity + Packet loss rate and packet error rate <l OE-5 + Transport packet delay variation (aka PDV or jitter)< 1 ms + eN odeB link delay < Sms + CPG to EPC transport link delay <Sms Network Requirements The diagram below outlines the network design for Fort Worth . Motorola is providing the specific Remote Agency Core/Gateway components depicted in the block diagram only, Aggregation Switch, Firewall/Security Gateway, and RAN components. The City of Fort Worth is responsible for providing all other network components, switches, routers, firewalls, security gateways necessary to interconnect to their enterprise network and to the Harris County EPC . All network integration is also a responsibility of the City of Fort Worth. The use of an MVPN middleware solution, such as Radio IP, is highly recommended to provide FIPS140-2 security and IP optimization from the end user mobile computer to the MVPN server within the trusted customer enterprise network. These components or network integration services are not included in our proposal. Figure 1-1 shows the overall system layout at the block level. Motorol a Con fi denti al Rest ricte d Use or d isclosure of this proposal is subject to the restrictions on the title page Fo rt W orth , TX Public Safety PS L TE System December 20 , 2013 System Description 1-3 Harris County Evolved Packet :•. -, HSSIPCRF • DNS/DHCP/ NTP oss tl!!!Z..---~ · ' ' Device Mgr • MME • Fort Worth Enterprise Network Motorola provided equipment Remote Agency Core/Gateway Aggregation Switch, Firewall, Security Gateway Radio Access Network IP Data Plane Control Plane Figure 1-1: PS L TE Architecture -2 Site Design and Remote Agen c y Core/Gateway 1.2 System Design The System design includes two eNodeB's, one CPG, one redundant Aggregation Switch and one redundant Firewall/Security Gateway as well as (5) USB Modems and (10) VSM Model 1 Model 1 (200 mW) Subscribers. As no specific sites have been chosen for the eNodeB locations, we are not including a coverage design, guarantee, or a coverage acceptance test plan with this proposal. When the sites have been chosen Motorola can provide informational coverage maps. However, we assume that the proposed equipment will be installed at the same sites as the proposed ASTRO radio system and Master site. Should this assumption change, additional costs will be presented to the City of Fort Worth for system integration as a change order to the project. In order to accurately model coverage for a public safety PS L TE system, the expected performance of the proposed system must first be clearly defined and understood. The performance of a PS LTE system is gauged by three factors: coverage, through put, and capacity. These performance factors are heavily interrelated, so that changes in one factor inevitably impacts the others. Capacity and throughput are inversely related to coverage ; hence an increase in capacity and throughput performance requirements results in a reduction of the predicted coverage footprint. A performance acceptance test is not included with this proposal. Fo rt Wo rt h, T X Public Safety PS L TE System December 20 , 2013 1-4 System Des cript ion Motorol a Confidential Restricted Use or disc losure of t his proposa l is subject to the restr ictions on the title page As users are added throughout the system and the capacity requirements for the system grow, the probability of interference in the system increases. This is an expected behavior in technologies such as PS L TE that re-use the same spectrum at all sites, referred to as an N =l architecture. Therefore, as more users become active throughout an area, more eNodeBs and UEs will transmit on the same frequency, increasing the overall noise on the channel and creating potential interference within the system. The role of the system design, including network planning, site separation, and the use of antenna down-tilt, in mitigating the effects of interference, and the proposed PS L TE system includes many advanced features specifically intended for this purpose. Advanced features in the PS L TE system include automatic transmit power control, inter-cell interference coordination, and interference rejection combining . It is important to highlight how the subscriber type impacts coverage. Although the VSM Model 1 and USB Modem emit the same transmit power, the USB Modem experiences more loss because its antenna is located inside the vehicle. This additional loss is what causes reduced coverage performance for the in-car USB Modem . 1.2.1 City of Fort Worth -Equipment Responsibilities 1.2 .1 .1 Backup Power 1.2.1.2 Per the FCC Waiver for operating on the PSST frequencies, the City must provide sufficient Battery Backup , as well as Generator power for the proposed PS LTE eNodeB sites and Remote Agency Core/Gateway. It may be possible to reuse the backup power systems proposed for the ASTRO sites, however additional analysis is required to verify if this will be possible. Each eNodeB , as proposed, will require at least ninety six amp hours of -48VCD battery backup to provide 4 hours of uninterrupted operation should the power fai l at the eNodeB site. Installation, testing and integration of City provided backup power with the proposed eNodeB sites is not included in our proposal and are a responsibility of the City o f Fort Worth. Equ ipment Spares Our proposal pricing does not include eNodeB or Remote Agency Core/Gateway equipment spares. Motorola recommends that the City consider procurement of spares. Motorola Confidential Restricted Use or disclosure of this proposal is subje ct to the restrictions on th e title pag e Fort Worth , TX Public Safety PS L TE System December 20 , 201 3 System Description 1-5 1.3 Remo te Agency Core/Gateway Architectural Considerations 1.3. 1 The City of Fort Worth's proposed Remote Agency Core/Gateway Architecture will be supported in Motorola's PS LTE Software Release 5.0 which is estimated to be avai lable in 2013. Therefore , our proposal is based on the assumption of equipment being implemented in this timeframe. The advantage of the proposed configuration is that the Harris County EPC and the Fort Worth Remote Agency Core/Gateway function as a single network from network operation perspective. User traffic is kept local in most application transactions, without the need to traverse back and forth to the Harris County EPC. The exception would be items like roaming and possibly other scenarios. This design significantly reduces the required backhaul link bandwidth needed, to only PS LTE control traffic , which is usually 5% of user traffic volume. Additionally, the traffic delay element needs to be considered for real time interactive applications like VoIP and PTT . If one of these real time applications is intended to be used over PS L TE, Remote Agency Core/Gateway is the recommend configuration. Optional Prioritization Service Manager (PSM) -Not Included The PSM is an agency network element that can be l ocated between a MVPN and the rest of application networks. The key function it provides is dynamic QoS control over a secure (MVPN) connection. Without a PSM , an agency will not able to allocate and adjust dynamically the QoS level based on public safety day-to-day incident and work flow changes. Real time applications are sensitive to packet delay and jitter. QoS is the mechanism to provide guaranteed bandwidth. Motorola's optional PSM network element is the brains of QoS management. If application services deployed over PS LTE require QoS management, such as VoIP and PTT, then a PSM should be added to the solution in order to provide optional subscriber performance. The PSM also allows management of dynamic QoS policy changes. A customer can implement a PSM even without a Remote Agency Core/Gateway to connect to a Hosted PS L TE EPC , with or without a PSM within its own operation domain. The PSM deployment has no dependency on Remote Agency Core/Gateway model. Fort Worth , TX Public Safety PS L TE System December 20 , 201 3 Motorola Confidential Restricted Use or disclosure of th is proposal is subject to the restrictions on the title page 1-6 System Descript ion However, the PSM does need to follow the MVPN deployment. Our PS L TE architecture supports one MVPN domain per PSM. Therefore, if an agency has an existing MVPN deployment and would like to use that over PS LTE, then a PSM needs to fo ll ow the MVPN deployment domain and be able to support all applications that run over it. 1.4 PS L TE Solution Architecture 1.4.1 1.4.1 .1 1.4.1.2 This section describes Motorola's PS L TE Architecture and all available equipment and features . The specific solution for Fort Worth is described in section 1.1 and 1.2 of this document. Motoro l a's current PS LTE Network offering is based on 3GPP Re l ease 8 Standards. The PS L TE so lution architecture is comprised of two critical segments , the Evolved Packet Core (EPC), and the Evolved Universal Terrestrial Radio Access Network (EUTRAN or RAN). The EPC is an all IP, packet switched core network and the EUTRAN is by PS LTE definition, th e Radio Access Network (RAN). The end user terminals in a PS L TE system are referred to as User Equipment (UE). The following paragraphs describe various components of the PS L TE solution architecture, as shown in Figure 1-1. User Equipment (UE) User equipment in a PS LTE system is any subscriber device which is used to access the network. Vehicular Subscriber Modem (VSM Mode l 1) The VSM Model 1 will support the 3GPP Release 8 standard interface to the PS LTE RAN. The VSM Model 1, equipped with a set of external high gain omni-directional MIMO antennas in a 1 Tx-2 Rx configuration, offers improved link budget and throughput performance. The VSM supports rugged trunk vehicle mounting and both USB and Ethernet-based wired computers and peripherals, as well as internal GPS and WiFi capability. The VSM is able to be managed remotely, and is upgradable over the air. Two external antennas are required. These two antennas support PS L TE, GPS and WiFi. All antennas and cabling are provided with the VSM Model 1. USB Modem The USB Modem device is suitable for external modem-to -PC installations for a range of existing Public Safety applications, and also multimedia capabilitie s such as live motion video to and from the attached PC . Moto rola Confide nt ia l Res tri cte d Use or disclosure of this proposal is subject to the restrictions on the title page Fort W o rt h, TX Public Safety PS L TE System December 20 , 2013 System Descript io n 1-7 1.4.2 1.4.2.1 1.4.3 1 .4 .3 .1 E-UTRAN Motorola's PS LTE air interface utilizes Orthogonal Frequency Division Multiple Access (OFDMA) in the downlink and Single Carrier Frequency Division Multi p le A~cess (SCFDMA) in the uplink. PS LTE uses Multiple Input Multiple Output, or MIMO, antenna systems. MIMO uses multiple antennas for both transmit and receive functions. eNodeB (eNB) In PS LTE systems, th e Base Transceiver System, Base Site Controller, and Radio Network Controll er , are all merged into a single element called the eNodeB (eNB). Motoro la's eNB is a PS LTE standards -b ased macro eNodeB. The eNodeB utilizes OFDMA and advanced antenna technology to provide a spectrally efficient and modular design that supports a large variety of site deployment scenarios. The eNodeB is located in the access network and provides air interface support to UEs, while al so terminating signaling and bearer packets , as well as communicating with oth er eNodeB peers in the network. The eNodeB performs the fo ll owing functions: • Provides the PS LTE air interface • Performs radio resource management functions • Measurement gathering for use in scheduling and mobility decisions • Radio Protocol Support Evolved Packet Core (EPC) -Ha rris County The EPC , which wi ll be hosted by Harri s County, TX, consists of the Mobility Management Entity (MME), Home Subscriber Server (HSS), Converged Packet Gateway (CPG), Operation Support System (OSS), and the Policy and Charging Rules Function (PCRF) server. Mobil ity Management Entity (MME) -Harris County The Mobility Management Entity (MME) provides control plane functions for the Motorola PS LTE network that is responsib le for mobility management and network access . Major functions of th e MME include: • Assisting with the authentication of UEs onto the network. • Tracking active and idle UEs . • Paging UEs when triggered by the arrival of new data. 1.4.3.2 Home Subscr ib er Server (H SS ) -Ha rris County The HSS contains the master database ofUE profiles and authentication data used by the MME for authenticating and authorizing UEs. It al so stores the location information of the UE, which is us ed for u ser mobility and intertechno lo gy handovers. Fort Worth , TX Public Safety PS L TE System De ce mber 20 , 20 13 1-8 System Description Motorola Confidential Restricted Use or disclosure of thi s proposal is It\ subj ect to th e restrictio ns on the title page W 1.4.3.3 Policy and Charging Rules Function (PCRF) -Harris County The PCRF creates rules for setting both policy and charging for the UE. These rules could be a combination of parameters such as types of applications. 1.4.3.4 Serving and Packet Gateways -Harris County and Fort Worth + Converged Packet Gateway (CPG) -Motorola offers a Converged Packet Gateway (CPG). Motorola's CPG solution provides the SGW and PGW functions using a single scalable, multimedia core platform. The Remote Agency Core/Gateway architecture for Fort Worth includes a local CPG in addition to the Harris County PS L TE EPC equipment. + Serving-Gateway (SGW) -The SGW is the mobility anchor, supports transport level QoS, and manages accounting for roaming users. The SGW routes and forwards user data packets, terminates downlink data for idle UEs, and is also the local mobility anchor for inter-eNodeB handovers. The SGW also maintains a buffer for each idle UE and holds the packets until the UE is paged and an RF channel is reestablished. For each UE associated with the EPC, at a given point of time, there is a single SGW. + Packet Data Network-Gateway (PGW) -The PGW is the point of interconnection to external networks and is responsible for the UE IP address assignment. It is the logical point of interconnection to each agency network in the proposed system. The PGW also acts as the Mobile IP/Proxy Mobile IP (MIP /PMIP) anchor point across EUTRAN and non 3GPP technologies (i.e. WiMAX, 3GPP2, WiFi, etc.), as well as providing Dynamic Host Configuration Protocol (DHCP) server and client functions. 1.4.3.5 PS L TE Operation Support System (OSS) -Harris County 1.4.3.6 To manage the EPC and the E-UTRAN, Motorola uses the PS LTE OSS. The PS L TE OSS is an Element Management System (EMS) designed to provide network managers a single location to manage, monitor, and upgrade the network. The OSS does not manage the HSS /PCRF. Prioritization Service Manager (PSM) -Not Included The optional PSM provides Public Safety enhanced QoS management and allows agencies to manage traffic prioritization in a shared network environment. The PSM is a server-client application that distributes control to agencies and meets the stringent Quality of Service (QoS) requirements for public safety applications. The PSM extends beyond the standard 3GPP PS LTE capabilities to allow agencies the ability to statically and dynamically manage the priorities of enterprise-wide resources based on the individual user, their agency, the incident, and their role. The PSM Client is Motorola device middleware compatible with Motorola PS L TE devices and certified third party PS LTE devices. The device middleware Motoro la Confi de nt ial Rest ricted Use or d isclosure of this proposal is subject to the restrictions on the title page Fort W o rt h, TX Pub lic Safety PS L TE System December 20 , 2013 System Description 1-9 1.4.3. 7 1.4.3.7.1 communicates with the PSM to facilitate customized QoS for the UE on the PS-PS LTE system. Motorola's PSM solution provides the controls necessary to successfully manage data flows and ensure the most important information at a particular point in time is prioritized. The solution provides more functionality over a standard carrier-grade PS L TE solution including a management service that meets public safety QoS and prioritization requirements. Motorola can provide further details on the PSM solution if desired by the City of Fort Worth. PS L TE Push-To-Talk (PTT) -Not Included Motorola's optional IP-based PS LTE Push-To-Talk solution is deployed as an overlay of the Motorola Public Safety PS LTE network on the existing PS LTE Radio Access Network (RAN), core network, and packet data network. Motorola's PS LTE PTT Server appears as an application server to the Public Safety PS LTE network. Motorola 's solution is based on a fully integrated, redundant PTT server platform to meet the operational and reliability needs of a Push-To-Talk over PS LTE network deployment. It also requires a PS PS LTE PTT client to be installed on the User Equipment. It will be available in PS LTE Software release 2.0. PS L TE PTT Ca ll Features The PS L TE PTT application can support the call features required by Public Safety agencies . The following is a list of the call types supported by PS LTE PTT: Instant Personal Talk (Individual one-to -one PTT Call) An individual Push-to-Talk call can be made between two PS L TE PTT users. The initiating PS L TE PTT user selects an individual from the PTT contact list and presses the PTT button. + Instant Personal Alert (Alert Call) Alert Call is used when the originator wants to inform the target user that one -to-one PTT communications is desired and allow the target user to respond to the Alert when available to communicate. The receiving PS LTE PTT user must initiate a PTT response to establish audio. + Instant Group Talk This represents a PTT group call to a group of PS L TE PTT users associated and previously defined as part of the group established in the Enterprise Management System. The group name is selected from the PTT contact list and the group call is initiated by pressing PTT button. + Temporary Group Talk A PS LTE PTT user can create a temporary group by selecting members from the PTT contact list. This type of group created by the user is referred to as a Temporary Group as it is not saved on the device or server. Fort Worth , TX Pub lic Safety PS L TE System December 20 , 2013 Motorol a Confid e ntial Restri cted Use or disclosu re of this proposal is It\ subject to th e restrictions on the tit le page W 1-1 O System Description 1.4.3.8 1.4.3.9 PS L TE PTT to ASTRO 25 Interoperabi lity -Not Included The PS L TE PTT group voice service can be connected to an ASTRO 25 network via an IP wireline gateway that bridges talkgroup calls. The PTT gateway enables direct talkgro up communi cations between users with PS LTE PTT handsets and Public Safety radio users with ASTRO 25 radios. This interoperability is enabled through the programming of the PTT gateway which links talkgroups on the ASTRO 25 system with corresponding pre-defined gro ups on the PS LTE PTT network. The PTT Gateway enhances Public Safety interoperability and seaml ess communications among l ocal, state and federal agencies using different networks and different devices . Network Management -Not Included The Network Management so lution will provide management functionalities including: + Configuration Management + Provisioning Service + Fault Management + Security Management + Software Load and Upgrade Management Motorol a Confid e ntia l Res t ri cted Use or d isclosure of this proposal is subject to the restrict ions on the title page Fo rt Worth , TX Public Safety PS L TE System December 20 , 2013 System Description 1-1 1 2.1 2.1.1 2.1.2 Statement of Work for Implementation General Information This Statement of Work (SOW) defines the principal activities and responsibilities of the parties for the implementation of the City of Fort Worth PS LTE System. Deviations and changes to this SOW are subject to mutual agreement between Motorola and Fort Worth and will be addressed in accordance with the Change provisions of the agreement. Our proposal for Fort Worth 's PS LTE system is based on implementation concurrent with the proposed ASTRO system. As such, we have applied system integration efficiencies in resources, specific tasks and mobilization. Should the timeline for the ASTRO system change, or if the PS L TE system is separated from that proposal, Motorola will revise the implementation plan and costs, if necessary, and present them to Fort Worth. System Implementation Overview This SOW specifically addresses the implementation of the City of Fort Worth 's PS LTE System that consists of a PS LTE Radio Access Network (RAN) and Remote Agency Core/Gateway connected to and supported by the Harris County, TX EPC. Motorola 's implementation plan includes the following phases, which require participation by the City of Fort Worth: + Project Initiation and Kickoff + Design Review encompassing proposed systems and responsibilities + Coordination with Harris County for key tasks such as network and backhaul design, testing and operational use -City of Fort Worth Responsibility + Order Processing and Validation + Manufacturing + Site Preparation and Readiness -City of Fort Worth Responsibility + Installation and Configuration + Functional Acceptance Tests + System Documentation + Project Finalization Motorola Confidential Restricted Use or disclosure of th is proposal is sub ject to the restrictions on the ti t le page Fort Worth, TX Pub lic Safety PS L TE System December 20 , 2013 Statement of Work 2-1 2.1 .3 2.1.4 + 1 Year Warranty As part of the System Description, Motorola has provided an engineering design, which served as the foundation for the Design Review. During the Design Review, details were finalized to allow some equipment ordering. During the Design Review stage, the City has decided to implement the two eNodeB's and Remote Agency Core/Gateway in two phases. Phase 1 will include the eNodeB implementation at the Texas Motor Speedway, and is expected to interface directly with the Harris County LTE system, without use of the Remote Agency Core/Gateway. Phase 2 will include implementation of the Remote Agency Core/Gateway, and the 2nd eNodeB site, co- located with the P25 system at the North Beach radio site. Motorola's implementation team will install and optimize the RAN at each of the two identified radio sites. We will then perform Acceptance Tests in accordance with the Acceptance Test Plan (ATP). The ATP includes tests to verify Network Attachment, Link Verification, and eNodeB handoff for the proposed VSM Model 1 devices. Following the Acceptance Testing, Motorola and Fort Worth will begin the transition to the new System. The project team and the post-acceptance service team will work with the Fort Worth project team during this phase to transition to the System Support Period. The final steps to full System implementation are delivery of System documentation, punch list resolution, and final project acceptance. Detailed Description of Work The work required by this SOW is divided into the following tasks: Title, Description, Motorola and Fort Worth Responsibilities and Completion Criteria, including project Deliverable(s). The estimated scheduled dates of tasks will be depicted in the Project Schedule. Fort Worth Responsibilities and Assumptions for Hosted Harris County PS L TE EPC The following list of considerations captures responsibilities and assumptions for this architecture, which is the basis for our proposal. Please note that the list below is not all inclusive and subject to change. Also, it is dependent on the defined capabilities, features, functions and operational model established in the final Interlocal Agreement between Harris County and the City of Fort Worth. 1. Software and Hardware versions between the Harris County PS L TE core and Fort Worth eNodeBs and Remote Agency Core/Gateway will need to remain consistent. Therefore, any decisions made at the core to update and/or upgrade the software and hardware will necessitate the remote sites following suit. Budgeting and timing of the costs should be understood and anticipated. Fort Worth, TX Publi c Safety PS L TE System December 20 , 2013 Motorola Confidential Restricted Us e or disclosure of th is proposal is If\ subject to the restri ctio ns on the title page W 2-2 Statement of Work 2.1.5 2.1.5.1 2. Hardware must be maintained consistent with the system, to support software updates and hardware obsolescence as well as allowing performance for all components of the system and both agencies. 3. The operations described below will occur at the Harris County EPC and Network Operations Center. These activities require coordination through Harris County. • Network Fault Management • Performance Monitoring • System Configuration • Security Monitoring and Response • Administrative Account Management • Access Authorization • Provisioning of User Equipment • Performance Statistics • Billing to Users • System Reporting • Roaming Capabilities • System Feature Activation • Application Interfaces • Backhaul and Network Planning • QoS Configuration • IP Planning and System Expansion 4 . The City of Fort Worth will have the same Public Land Mobile Network ID (PLMN) as Harris County. 5. Network and backhaul design, ongoing maintenance and support as well as software and hardware upgrades to integrate both agencies are a responsibility of the City of Fort Worth and must be coordinated with Harris County. General Project Responsibilities The following general project responsibilities, not defined by specific tasks, include: Motorola Project Manager Responsibilities Motorola will designate a Project Manager who will direct Motorola's efforts and serve as Motorola's primary point of contact. The Motorola Project Manager will have significant authority to make certain decisions relative to the project, on behalf of Motorola, and w ill have direct access to Motorola's management for resolving problems beyond the Project Manager's immediate authority. The responsibilities of the Motorola Project Manager include: + Participate with the City of Fort Worth in monthly progress review meetings and submit status updates that identify the act ivities of the previous review period, as well as activities planned for the upcoming review period, including an updated Project Schedule. Motorola Confidential Restricted Use or disclosure of this proposal is subject to the restrictions on the title page Fort W orth, TX Public Safety PS L TE System December 20 , 2013 Statement of Work 2-3 • Maintain project communications with the City of Fort Worth 's Project Manager, and project team members. Motoro la will provide a record of correspondence as part of the progress updates provided prior to each progress meeting. • Maintain a documentation schedule that identifies and shows the status of documents to be transmitted for review during the next two reporting periods. • Participate in biweekly conference calls and issue a mutually agreed upon agenda for each call or meeting. • Manage the efforts of Motorola staff and coordinate Motorola activities with Fort Worth project team members. • Measure, evaluate and report progress against the Project Schedule. • Address deviations from the Project Schedule. • Monitor the project to arrange availability of support resources as scheduled and as identified in the contract. • Assume accountability for all Motorola contractor and subcontractor supplied tasks within the Project Schedule. • Review and administer change control procedures through Fort Worth Project Manager, commonly referenced as a "Project Change Request" (PCR), issued by the Motorola Project Manager. • Provide timely responses to issues related to project progress. • Work wi th Fort Worth 's Project Manager in designing and approving the format of an action item log to be used in conjunction with the Project Schedule. The purpose of the lo g is to identify outstanding i ssues, provide continual status updates on specific tasks , and to identify responsibilities of the parties. + Prepare and submit a monthly status report that identifies the activities and milestones completed in the previous month and activities planned for the current month, and the next month, including progress and payment milestones, and an updated Project Schedule. + In the event that Motorola replaces or substitutes any critical project team members, such as the lead Project Manager or lead Project Engineer, Motorola will promptly notify the City of Fort Worth Project Manager of such a change and w ill identify the person Motorola intends to assign as a replacement or substitute. 2.1.5.2 Fort Worth Project Manager Responsibilities The City of Fort Worth will designate a Project Manager who will direct the City of Fort Worth efforts and serve as the primary point of contact for the project. The City of Fort Worth Project Manager will have significant authority to make certain decisions relative to the project, and will have direct access to the City of Fort Worth's management for resolving problems be yo nd the Project Manager's immediate authority. The responsib iliti es of the City of Fort Worth's Project Manager include: + Maintain project communications with Motorola's Project Manager. + Accountable for the Harris County PS L TE EPC Coordination, Planning and Execution. Fort Worth , TX Pu blic Safety PS L TE System December 20 , 2013 2-4 Statement of Work Motorola Confidential Restricted Use o r disclo sure of thi s proposal is subject to the restri ctions on the title page • Identify the efforts required of the City of Fort Worth's staff to meet the City of Fort Worth's task requirements and milestones in the Statement of Work and Project Schedule . • Review the preliminary Project Schedule with Motorola's Project Manager, and assist Motorola in developing a detailed Project Schedule defining the detailed tasks and schedule of Motorola and the City of Fort Worth's responsibilities. • Measure and evaluate progress against the Project Schedule. • Monitor the project to arrange availability of support resources as scheduled and as identified in the contract. • Participate in weekly conference calls. • Participate in Monthly Progress Review Meetings. • Provide timely responses to issues related to project progress raised by Motorola's Project Manager. • Review and administer change control procedures, hardware and software certification, and all related project tasks required to maintain the project schedule. • Approve and release payments in a timely manner. • Ensure that all appropriate Fort Worth personnel attend and actively participate in Progress Reviews , conference calls, and other project meetings. • Assign personnel who will work with Motorola and Motorola's subcontractors as needed for the duration of the project. • Ensure acceptable Standard Change Request and Approval Letter(s) are approved by authorized signature(s). • Work with Motorola personnel in designing and approving the format of an action item log to be used in conjunction with the project schedule. The purpose of the log is to identify outstanding issues, provide continual status updates on specific tasks, and to identify responsibilities of the parties. • Inform Motorola of all relevant rules , regulations, and requirements for installation. Should these conditions impact the project schedule and hinder installation, the City of Fort Worth may incur additional cost. • Provide building access to Motorola personnel to all facilities where the System is to be installed during the project. Temporary identification cards should be issued to Motorola personnel if required for access to the City of Fort Worth facilities. Access must be available after business hours where required by Motorola, or as necessary to meet the project schedule. • Provide any required parking permits to Motorola personnel for restricted access entry and /or parking. • Review and approve or revise delivered design documents within five days of submission. • Provide all required liaison support with the agencies and vendors required to support the solution. • Ensure all Fort Worth subcontractors perform in accordance with this SOW and the project schedule. Motorola Confidential Restricted Use or disclosure of this proposal is subject to the restrictions on the title page Fort Worth, TX Public Safety PS L TE System Decem ber 20 , 2013 Statement of Work 2-5 2.1.5.3 2.1.6 Hosted Core Management (Harris County PS L TE EPC) -Fort Worth Project Manager Respons ibi liti es These responsibilities for coordination with Harris County include tasks that will be required to successfully design, install , integrate and test the proposed system for Fort Worth. The list below outlines the anticipated tasks however is not all inclusive. + Establish a single point of contact at Harris County to participate in project review and status update meetings, engage throughout the implementation phase of the project and resolve issues. + Coordinate meetings and discussions with the appropriate Harris County personnel and resources throughout the implementation phase of the project and at specific checkpoints identified by the Motorola Project Manager. + Establish an Interlocal agreement with Harris County in the Kickoff phase of the project to govern technical design, features, functions and operational modeling . + Coordinate resources within the City of Fort Worth and Harris county to engage in discussions during Design Review related to the following items: • Backhaul and Aggregation Design per design specifications and bandwidth requirements. • Network Design, IP Addressing, including physical and logical interfaces. • FCC Frequency lic ensing considerations . • Spec ific features and functions including Performance Management, Network Fault Management and Performance and Network Monitoring, Roaming capability, Provisioning subscribers. • Operational and ongoing considerations such as software and hardware upgrades , ongoing maintenance and subscriber operational usage. + Coordinate resources and provide information required to install and integrate Fort Worth RAN and Remote Agency Core/Gateway equipment with Harris County PS L TE EPC. + Coordinate and provide resources at the PS L TE EPC in Harris County for operational and functional testing as quoted for Fort Worth. + Provide resources, timeframe and coordinate software upgrades with Harris County to release 3 .0 . Project Initiation and Kickoff The project will be initiated with a Project Kickoff meeting, including key Fort Worth and Motorola project participants. The objectives of the Kickoff meeting include: + Review high level System design and project purpose. + Introduce and exchange contact information of all project participants. + Review roles of key participants and project review procedures . + Establish a clear chain of communication and authority. + Review overall project scope and objectives. + Review resource requirements. Fort Worth , TX Public Safety PS L TE System Decembe r 20 , 2013 Motorola Confidential Restricted Use or disclosure of this proposal is 19\ subject to the restrictions on the title page V 2-6 Statement of Work 2.1.6.1 2 .1.6.2 2.1.7 During the Project Initiation phase, Motorola will r eview and work w ith the City of Fort Worth to finalize the following project processes and procedures: + Change Contro l Plan + Iss u es Do c ument and Action Item Log Re sponsibility Matrix -------I -Resp~~sibillty---r ·-------Deliv~rible Task Initiate the project with a Kickoff Motorola and Fort Documented project Meeting . Worth personnel names , responsibilities , contacts , and project review procedures . Define format of the Issues and Motorola and Fort Initial Issues and Action Item Action Item Log . Worth Log Review change control procedures Motorola Initial Change Control Plan with the City of Fort Worth Project Manager. Work with Motorola personnel in Fort Worth Approved Initial Change finalizing and approving the Control Plan Change Control Plan . Provide current system and site Fort Worth Fort Worth Existing System documentation. Documentation Coordination with Harris County Fort Worth Single Point of Contact at regarding System Design and Harris County Resource Implementation , Responsibilities assigned for implementation and Project Schedule. phase Complet ion Criter ia This ac tivity i s considered complete when the Project Kickoff Session has been held and project scope, procedures, roles and responsibilities are documente d . Des ign Review - Fort Worth and Motorola will review the System de si gn through analysis of th e System functionality, interface requirements, and end-user requirements, as mutually agreed between Motorola and the City of Fort Worth. The project schedule will al so be reviewed and finali ze d , based on the agreed-upon design. Motorola wi ll draft and deli ver final versions of the design documents and project sc h edul e to the City of Fort Wmih for review and ap pro val. Deviations from the PS LTE so lution described in the System Description may require mutual exec ution of a change order, depending on the scope of the change(s). Motoro la and the City of Fort Worth deliverables and responsibilities are describ ed in greater detail in the following sections. Motorola Confidential Restricted Use or disclosure of t his proposal is subject to the re stricti ons on th e title page Fort Worth, TX Public Safety PS L TE System December 20 , 20 13 Statement of Work 2-7 2.1 .7 .1 Re sp on sibility Matri x Task Identify all RAN site locations , and location for installation of the Remote Agency Core/Gateway equipment. Motorola 's design is based upon the assumption that equipment will be located at ex isting radio s ites . Assure site access to inspect equipment installation sites , and determine if any course of action is necessary to handle installation constraints . The City of Fort Worth will provide ex isting site and system drawings as ava ilable . Site Readiness Audits : . R56 Aud its will be conducted as part of the proposed ASTRO system . . Prepare a report that includes requirements and recommendations detailing site preparation to provide a suitab le environment for installation of the PS L TE equ ipment. . Obtain any frequency licenses needed . . Obtain all FCC (700 MHz waiver approval ), zoning , site access , and othe r permits (including , but not limited to , easements , impact studies , planning commiss ion approva l, variances , obstruction permits , etc ) necessary fo r th is project and any ot he r agreements requ ired to gain use of s ites . Coordinate w ith other agencies on its use . . Investigate and mit igate any sources of interference including enginee ri ng studies if necessary. . De lays in obtaining licenses/waiver may result in Motorola incurring additional cos t s , which may require mutual ex ecution of a chanqe order. Identify electrical requ irements at each mounting location for use w it h the iden t ified sites associated w ith the pro j ect. Condu ct a de sign me et ing to rev iew and final ize the RAN design . Condu ct a design review presentation w it h Fort Worth to review the proposed solut ion . Revi ew Sys tem Des ign and interconn ection to Harris County including but not limited to network design , backh aul and agg regation points , phys ical and log ica l demarca tion points , features an d function s , o peration a l m odeling and us age . Fort Worth , TX Publ ic Safety PS L TE System December 20 , 2013 2-8 Statement of Work I Responsibility I Deliverable Fort Worth Radio Access Network Design Input: All site locations defined Fort Worth Site Access Ex isting Site and System Documentation Motorola Site Audit Reports Fort Worth A ll Sites : Frequency Licenses and Site Permits Motorola All Sites : Design Input: All electrical requ irements defined Moto rola Radio Access Network Design Motorol a Design Review Meeting and Presentation Fort Worth Final ize Design Document w it h input from Harris County Motorola Confidential Restricted Use or d isclos ure of t his pro posa l is subject to the rest rictions on the t itle page Task I Responsibility I Delivera!;>le , -- Participate in design review meeting . Coordination with Fort Worth Attendance at Harris County and establishment of an lnterlocal design review Agreement. meeting and ILA established. . Deliver the Design Document that reflects changes in Motoro la Design Documents design and scope , as well as definition of details determined during the Design Review. . Update the equipm e nt list as necessary to accommodate the spe ci fics of the Design Review. . Update the System De sc ription to reflect changes in the System design . . Update the System drawings and documentation to reflect changes in the System design . . Update the SOW to reflect changes in the implementation scope . . Motorola and the City of Fort Worth will final ize the implementation schedu le. . Subm it the final Design Document to Fort Worth through t he change orde r process . Any changes in System pr ice driven by the design review will be included in the change order. Review and approve the Design Document within five Fort Worth Design Document business days of receipt. Approval Finalize Project Schedule within five days of the Design Motorola Final Project Review meeting through the Change Order Process. Schedule Approve Fina l Proje ct Schedule within two days of Fort Worth Approved Final rece ipt. Pro j ect Schedule 2 .1 .7 .2 Com pl et ion C ri teria Thi s activ ity is considere d co mplete wh en the D es i gn R evi ew i s co mpl et e and the City of P ort W orth h as appro ve d the D esign R evi ew, fina l proj ect schedul e, and any ch ange or der res ulting from the Des ign R eview. Addendum: Th is document update i s provide d in D ecember, 2013 . Locations of the eNodeB 's have b een determin ed . T h e City h as el ect ed t o p roceed wi th a Phase d appro ac h. Phase 1 wi ll include ins tall ati on and integration of th e CPG at Fort W orth 's Eagl e Mountain master site, an d the Texas M oto r Sp ee dway eNodeB site, di rectl y interfa ced with the Harri s County system . Thi s sit e w ill be u se d t o conduct pil ot t es t s at the T exas Motor Sp ee dway. The fo ll owing Phase wi ll incl ud e fu ll integration of the eNo deB at the City's North B each radi o site. Motorola Confidential Restricted Use or discl osu re of thi s proposa l is s ubject t o th e rest ric tions o n the t it le page Fort Worth, TX P ublic Sa f ety PS L T E Sys tem December 20 , 2013 Statemen t of Work 2-9 2.1.8 Updated Design documents are placed on the project website with the following URL: LTE (general folder): https://compass.motorolasolutions .com/cgi/go /385923466 TMS (eNodeB site): https://compass.motorolasolutions.com/cgi/go /386287067 North Beach (eNodeB site): https://compass.motorolasolutions.com/cgi/go /3 86269910 Order Processing Motorola will place orders for the System hardware that is being purchased for the City of Fort Worth System. Motorola will also place orders for required third-party equipment and execute subcontracts with our subcontractors. Fort Worth , TX Public Safety PS L TE System December 20 , 2013 Motorola Confidential Restricted Use or disclosure of this proposal is subject to the restrictions on the title page 2-10 Statement of Work 2.1.8.1 Responsibility Matrix --- --------------------------i------------I ---------------------- Task Responsibility Deliverable ·- Pl ace factory orde rs for all Motoro la manufactured Motorola Orders for Motorola equipment. manufactured equipment P lace order for all third-party equipment. Motorola Third-Party Equipment Orders Execute agreements with subcontractors . Motorola Subcontracts in place Manufacture equipment and track third-party Motorola Fort Worth System equipment orders . Hardware Ship equipment to the Motorola-leased Fort Worth Motorola Equ ipment Shipping project warehouse, or the antenna system vendor's warehouse , prior to final delivery to Fort Worth sites . Provide clear and stable access to the sites for Fort Worth Site Access transporting electronics and other materials. Sufficient site access must be available for trucks to deliver materials under their own power and for personnel to move materials to the facility without assistance from special equipment. Provide appropriate site access and mechan isms Fort Worth S ite Access (elevator) to deliver heavy equipment (servers, etc .) to be ins tal led in sites , as required . 2.1.8.2 Completion Criteria This activity is considered complete when all equipment orders have been placed, procured, and shippe d to the City of Fort Worth. 2.1.9 Civil Work and Site Development A very comprehensive level of civil and site services was included with the proposed ASTRO system submitted to the City of Fort Worth. Our assumption for this proposal is that the PS L TE system will be implemented concurrently with the proposed ASTRO system. As such civil and site preparation efficiencies and costs will be shared between both types of technologies at two existing radio sites. Should this assumption, the timeline of either of the se projects change, or become separate projects, we will provide a revised proposal and costs to the City of Fort Worth. We have outlined the civil responsibilities at each site below based on the information gathered. Site Readiness including site preparation, electrica l and grounding above and beyond wh at i s outlined below, or in the ASTRO system Statement of Work, are a responsibility of the Ci ty of Fort Worth. Motorola Confidential Restricted Use or disclosure of this proposal is subject to the restrictions on the title page Fort Worth, TX Public Sa f ety PS L TE System December 20 , 20 13 Statement of Work 2-11 Motorola wi ll begin install ation and implementation tasks at a site only after mutual agreement by the City of Fort Worth and Motorola that the site is deemed ready. For the proj ect , we assume the tasks belo w would be done concurrently and incorporate both the ASTRO and PS LTE equipment at the two eNodeB sites and the Remote Agency Core/Gateway loc ation. Note that the below responsibilities are also d etail ed and amended in the ASTRO system Statement of Work, based up on completion of the initi a l Design Review: + Tower Structural Analyses for the existing radio sites included in our ASTRO system proposal. + Specific Architectural, En gineerin g and Site Preparation Services for the two radio si tes including permitting, zo ning, and environmental studi es quoted in our ASTRO proposal. + Specific Facility Enhancements quoted in our ASTRO propo sal at two radio sites incorporating electrical, grounding and backup power enhancements per Motorola R56 Standards and Guidelines for Communication Sites. 2.1.9.1 Responsibility Matrix Task Site Readiness completed within the established project schedule timeframe . Site Specific Civil Work and Site Development as outlined in Section 3.7.2 of the ASTRO Statement of Work including: . Specific Architectural and Engineering Services . . Tower Structural Analysis for rad io sites . . Backup UPS and Generator Power for radio sites . Site Specific Civil Work and Site Development as outlined in Section 3.7.2 of the ASTRO Statement of Work including : . Final Zoning and Permitting , EME p lans . . Provide adequate utility power at each site . . Pay for utility connection , pole or line extensions , and any easement or usage fees . . Pay for usage costs of power, leased lines and generator fueling . . Any necessary tower modifications , antenna support structures , cable boots . Additional PS L TE Antenna and Transmission Line Installation at one of two radio/eNodeB sites : . . . . Install three panel antennas with side arms . Install si x transmission lines and attachment hardware . Perform sweep tests on transmission lines . Ground and Bond new antenna systems to existing single point tower and site qround system. Fort Worth, TX Publi c Safety PS L TE System December 20 , 2013 2-12 Statement of Work I Responsibility I Deliverables Fort Worth Sites Meet Site Readiness Conditions Motorola and Fort Complete Site Worth Work -Motorola and Fort Worth Fort Worth Complete Site Work -Fort Worth Motorola and Fort Antenna Systems Worth Installed Motorola Confidential Restricted Us e o r disclosure of this propo sal is It\ subject t o the restri ctions on th e title page W I Task ~· _ j _ Respons_ibility -·--• -~J. Additional Facility Improvement Work: . At one of two eNodeB sites, provide and install two 20 -Amp breakers in the distribution panel and wire to two outlets instal led at the equipment cabinet. . At the Remote Agency Core/Gateway site/Master site , install two 20-Amp breakers into existing breaker panels and wire to two outlets installed at the equipment cabinet. Backup Battery Power for eNodeB sites : . Provide sufficient Battery Backup for each of two eNodeB sites . . Backup Generator Power for TMS eNodeB Backup Generator Power for North Beach eNodeB Remove or relocate existing equipment. Provide roof and wall penetrations , conduit, cab le trays and other supporting equipment necessary for the routing of power , grounding and networking cables. Confirm that existing sites meet requirements for site readiness based on the mutually agreed to requirements in the Site Planning , Preparat ion Checklists , and R56 Audit Results . Investigate and mitigate existing or future sources of internal and external interference at the existing sites . Provide the appropriate fire inspection and building inspection certificates . Inspect and approve the equipment installation locations , power, backhau l and network demarcations in accordance to the mutually agreed upon site improvements. Motorola Confidential Restricted Use o r di sclosure of thi s prop os al is s ubj ect to the restri ct io ns on th e titl e pa ge Motorola and Fort Worth Motorola Fort Worth Motorola Fort Worth Fort Worth and Motorola Fort Worth Fort Worth Fort Worth Motorola I Deliverables Outlets for eNodeB and Remote Agency Core/Gateway sites Backup Power operational Backup generator power Backup generator power Removal or relocation of existing equipment as necessary . Power, grounding and network cable routes Fort Worth Sites Meeting Site Readiness Conditions Remediation of any interference Inspection Certificates Site Approval Fort Worth, TX Public S afety PS L TE Sy stem Dece m ber 20, 201 3 Stateme nt of Work 2-13 2.1.9.2 Site Design Assumptions The items below were assumptions made by Motorola in developing the civil and site design tasks , responsibilities and assumptions for this proposal. + No prevailing wage, certified payroll , mandatory union workers or mandatory minority workers are required for this work. + All work is assumed to be done during normal business hours as dictated by time zone (Monday thru Friday, 7:30 a.m. to 5 :00 p.m.), or as mutually agreed + Site has adequate electrical service for the new shelter and tower. Utility transformer, transformer upgrades , line , or pole extensions have not been included. + Pricing has been based on National codes such IBC or BOCA. Local codes or jurisdictional requirements have not been cons idered in this proposal. + If extremely harsh or difficult weather conditions delay the site work for more than a week, Motorola will seek excusable delays rather than risk job site safety. + The existing antenna support structure is structurally capable of supporting the new antenna, cables , and ancillary equipment proposed and will not need to be removed or rebuilt at the existing site. The tower or supporting structure meets all applicable EIA/TIA-222 G structural, foundation, ice, wind, and twist and sway requirements. Motorola has not included any cost for structural or foundation upgrades to the antenna support structure . + Structural analyses for towers or other structures that have not been performed by Motorola will relinquish Motorola from any responsibility for the analysis report contents and/or recommendation therein. + Complete upgrades of each eNodeB site at the City of Fort Worth to R56 is not included in our proposal. + The floor can support the proposed new loading. Physical or structural improvements to the existing room will not be required . 2.1.9.3 Completion Criteria This activity is considered complete when site readiness has been achieved. 2.1.10 Implementation Implementation includes the installation, integration and optimization of the PS L TE RAN and Remote Agency Core/Gateway equipment located at the identified sites. Our proposal assumes implementation of equipment to Fort Worth concurrently with Motorola's PS LTE Software release 5.0. Fort Worth, TX Public Safe ty PS L TE System December 20, 20 13 2-14 Statement of Work Motorola Confidential Restricted Use or disclosure of this proposal is It\ subject to the restrictions on the title page W 2 .1.10 .1 Respo nsibility Ma trix ----------- - ---------i---------------i--------------- ---- Task Responsibility Deliverable ---- Inventory proposed equipment (Motorola with Fort Worth oversight). Provide all site links between the RAN/eNodeB sites , Remote Agency Core /Gateway and the City of Fort Worth backhaul aggregation point , as well as any necessary network equipment required . Site links must conform to the performance specifications provided by Motorola in the Design Review. Motorola and Fort Worth Fort Worth Provide sufficient backhaul and associated network Fort Worth equ ipment between the City of Fort Worth network aggregation point and the Harris County PS L TE Core . Site links must confirm to the performance specifica tions provided by Motorola in the Design Review. Provide and instal l if necessary any required Fort Worth network equipment, MVPN , cabling and switches required to facilitate the physical and logical connection of Fort Worth eNodeB sites and Remote Agency Core/Gateway location to the Harris County PS L TE Core based on the final network design. We assume Harris County will provide the DCHP server for PS L TE at their EPC . Test and certify backhaul links meet minimum Motorola required perfo rmance specifications for proposed equipment. Installat io n of eNodeB sites and Remote Agency Motorola Core/Gateway will include the following tasks : • Phys ic al installation , ground ing and bonding of eNodeB equipment rack . • Connect eNodeB to antenna systems and power systems . • Connect eNodeB BTE switch to Fort Worth provided backhaul equipment. • Configure ," optimize and integ rate with Harris County PS L TE EPC . • Verify operational testing and functionality. Motorola Confidential Restricted Use or disclosure of this proposal is subject to the restrictions on the title page Equipment Inventory Document Approved site links Carrier agreement for backhaul Backhaul Complete Backhaul links certified eNodeB Installation Complete Fort Worth , TX P ublic Safety PS L TE System December 20, 2013 Statemen t of Work 2-15 Task Responsibility I Deliverable Provid e and install th e foll owing equi pment at each Fort Worth All Sites: specified location : Network . Netwo rk demarcation within 6 feet of switch. Demarcation , . Proper network interfa ce to connect bac k haul Power , Appropriate equipment to ex isting point of presence Cabling , Floor locations at each of the s ites . Space , Tower Space . 24x7 surge protected powe r at ea c h equipment rack . . Wall penetrations , conduit , cable t rays and other supporting equipment necessary for the routin g of power, grounding and networki ng cables . . Floor space fo r all equipment racks . . Tower Space for PS L TE antennas . We have assumed two mobilizations of our Fort Worth Mob ilization Efforts installation and engineering teams fo r eNodeB Co m plete sites , so site read iness at a ll sites must be complete at the same time . Shou ld th is assumption not be valid , remobilization costs will be presented to the City of Fort Worth via change order. Provide Vehicles with ade q uate mounting space Fort Worth Subscribers for (10) VSM Model 1 and antennas per Available for spec ifications , as well as available USB slots for Installation the (5 ) proposed dongles . Vehicular mounts will be prov ided by Fort Worth. Provide Mobile Data Computers (MDC ) w ith Fort Worth MDC that meets minimum required hardware , software and specifications operating system specifications to operate with the available for proposal use r devices installation Our proposal does not include any additional Fort Worth Subscriber Licensing subscriber software licensing to support the (15 ) proposed Fort Worth subscribers on the Harris County PS L TE EPC . Should Harris County 's ex isting subs c riber licensing be unable to accommodate these two additional subscribers , the additional costs will be a responsibility of Fort Worth . Install proposed VSM Model 1 and USB into Motoro la PS L TE Devices existing Fort Worth vehicle and MDC 's . Installed Create "As Built" documentation for inclusion in the Motoro la "As Built" final project documentation. Documentation 2 .1.10 .2 Comp letion Cr iteria This activ ity is con si dere d compl et e when Motoro l a h as compl eted th e inst all ation s of the PS LTE RAN equipm ent. Fort Worth , TX Publ ic Safety PS L T E System December 20, 20 13 2-16 St atemen t of Work Motorola Confidential Restricted Use or disclos ur e of thi s prop osal is It\ subject to th e res tri ctio ns o n the ti tl e page W 2.1.11 Functional Acceptance Test Plan (FATP) Motorola will be responsible for functional performance of proposed equipment as provided by Motorola under this contract. The City of Fort Worth will assume responsibility for the proper functional performance of all other equipment necessary including the Harris County PS LTE EPC for completion ofthis project. Our proposed PS L TE solution for Fort Worth will connect to the existing Harris County PS LTE Core. As such, Harris County and the City of Fort Worth are responsible for the required backhaul and integration between their networks to ensure adequate functional performance. The project implementation requires the integration of existing Fort Worth equipment with equipment provided under this contract. Fort Worth equipment includes, but is not limited to facilities, network equipment, fiber connectivity, and backhaul. Backhaul network performance and latency are the responsibility of Fort Worth. Motorola is responsible for the proper functional performance of all Motorola- provided PS LTE RAN and Remote Agency Core/Gateway hardware as described in the System Description, when operating within environmental specifications. Fort Worth is responsible for the proper functional performance of all existing and Fort Worth provided hardware, software, network/transport layer, that will be interfaced with or integrated into the various subsystem implementations for this project. Motorola will not be responsible for the performance of these items. Acceptance tests will be performed in accordance with the Acceptance Test Plan (ATP) in Section 3 of this document. During acceptance testing, the System will be tested and the results documented. Upon successful completion of acceptance testing, the City of Fort Worth and Motorola will sign a System Acceptance Certificate. 2 .1.11.1 Responsibility Matrix Task - Complete equipment preparations and test set-up activities required to conduct each test. Coordinate FATP with Harris County including resources to participate in the test. Perform tests in accordance with the procedures in the ATP. Assign authorized representative(s) to monitor the test. Provide operational Mobile Data Computer(s ) (M DC ) PS L TE Devices , Drivers Fuel and Vehicle(s) for the duration of the test. Present results of test. Part icipate in the Acceptance Tests. Motorola Confidential Restricted Use or disclosure of this proposa l is subject to the restrictions on the title page I Responsibility J Motorola Fort Worth Motorola Fort Worth Fort Worth Motorola Fort Worth Deliverable Set-up complete PS L TE EPC and resources available Performance of test Resource Assignment Provide require d equipment and resources Test Results Written acceptance of System Fort Worth , TX Public Safety PS L TE System December 20 , 2013 Statement of Work 2-17 2 .1.11.2 Completion Criteria This activity is considered complete upon completion of acceptance testing. The City of Fort Worth and Motorola will acknowledge completion of acceptance testing by signing a System Acceptance Certificate, at which time the System will be available for use by the City of Fort Worth. 2.1.12 Training There is no training included in our PS LTE proposal for Fort Worth. 2.1.13 System Documentation Motorola will provide documentation of the system configuration, physical installation, and system testing. Documentation will be created and updated during the project. All documentation will be provided in soft copy format. 2.1 .13.1 Design Documentation Motorola will create or update the following standard documents during the design phase: + Documentati on Index + System Description + Deliverables List + Block Diagrams for RAN Sites and Remote Agency Core /Gateway location + RAN and Remote Agency Core/Gateway Installation Plan Drawings + Final Project Schedule + Acceptance Test Plan The compilation of the above documentation constitutes the "Fort Worth RAN and Remote Agency Core/Gateway Design Documents" deliverable. 2.1.13.2 System Manual-"As-Built" Documentation Motorola will supply three soft copies of "as-built" documentation for the System. The documentation will consist of: + Standard Equipment Manuals + (2) eNodeB Site RAN Deployment Site Drawings + Remote Agency Core/Gateway Design Drawings + Acceptance Test Results + Warranty Information Fo rt W orth, TX Public Safety PS L TE System December 20 , 2013 2-18 Statement of Work Moto ro la Confid e nti al Rest ricted Use or disclosure of this proposal is It\ subject to the restrictions on the tit le page W • 2.1.13.3 Equipment Manu als Motorola will provide the equipment and software vendor s' manuals and product documentation covering both standard and optional features. The content of these m anual s is standardized and may not b e specific to the City of Fort Worth. The documentation will be provided as soft copies. 2 .1.1 4 Project Finalization The finalization phase of the proj ect consists of confirming that the below criteria for Final Project Acceptance have been met. 2 .1.14.1 Responsibility Matrix Task I Responsibility I Deliverable - Resolve punch list items documented at Motorola Approved Punch list System Acceptance . Resolut ion Confirm that the information required to Motorola Service Transition transition the project to the Motorola Certificate and Service Organization is obtained , which Customer Support Plan includes the development of a Warranty Customer Support Plan with Fort Worth . All documents listed in System Manual-Motorola System Manual-"As "As Built" Documentation Section will be Built" Documents submitted , as they become ready . Final approval of System Manual-"As Fort Worth Written Approval Built" Document Package within five days . Statement( s) Acknowledge Final Project Acceptance. Fort Worth Signed Final Acceptance Documents 2.1.14.2 Comp letion Criteria This activ ity is considered complet e wh en the City of Fort Worth and Motoro la have signed the Final Project Acceptance certificate, representing the completion of the System impl ementation work and acknowl edgement of System acceptance . 2 .1.15 Warranty The services provided during the Warranty Period will be delivered in this phase of the project. Specific information can be fo und in Section 6 -Statement of Work for Supp ort . Please note that our equipment Warranty is one Year and does not track with the long-term Warranty and ongoing Support and Maintenance Plan included with the ASTRO proposal. Motorola Confidential Restricted Use or disclosure of this proposal is subject to the restrictions on the title pag e Fort Worth , TX Pu blic Safety PS L TE System Decem ber 2 0 , 2013 Statem ent of Work 2-19 2 .1.15.1 Responsibi li ty Matrix Task Perform Services du ri ng the PS L TE 1 Year Warranty Period . 2.1.15 .2 Comp let ion Criter ia "' Responsibility Deliverable Mo torola Warranty Services This activity is considere d com p l ete w h en th e Warranty P erio d ends . Fort Worth , TX Pu blic Saf ety PS L T E System December 20 , 2013 2-20 Statemen t of W o rk Motorola Confidential Restricted Use or disc los ure of th is proposa l is It\ subject to t he res t rict ions on t he t it le page W 3.1 Introduction 3.1.1 This document describes the Acceptance Test Plan (ATP) for the Fort Worth PS LTE System. Under the direction of the Motorola Project Manager, teams consisting of representatives from Fort Worth and Motorola will execute agreed-upon test procedures. These tests will require Fort Worth to coordinate time and resources at the PS LTE EPC with Harris County. The following sections contain a brief outline of th e tests to be performed: 1. Network Attachment Test 2. Link Verification Test 3. eNodeB HandoffTest These tests wi ll be condu cted once the eN odeBs are functional and optimized at each site . This includes an active link back to the Evolved Packet Core (EPC) hosted by the Harris County, TX. Motorola will , for each test performed, provide documentation detailing the test data collected and the results achieve d. This will include traffic capture , trace, and lo g files collected when relevant. Network Attachment Test The obj ective of the Network Attachment Test is to validate the authenticati on and authorization of a User Entity (UE) during the network attachment process . The UE is provisioned in the Home Subscriber Server (HSS) prior to the test. For the test, the UE i s attached to the Mobile D ata Computer (MDC) at power up and attachment to the PS LTE network is verified. The Network Attachment Test will confirm the following System functions: • Link Management + UE Attach • UE Release • Service Requests • UE Detach • UE Authentication • Dedicated Bearer Activation • Dedicated Bearer Deactivation Motorol a Confid e nti al Restricted Use or disclosure of th is proposal is subject to the restri ctions on the title page Fort Worth , TX Public Safety PS L TE System December 20, 2013 A cce ptance Test Plan 3-1 3.1 .1.1 3.1.2 Test Preparation The network elements under test must have passed quality assurance testing and there must be no known blocking issues that impact the testing activity. A common set of too l s to analyze protocols for the interface under test will be used. Interface logs for each test will be collected and provided from the monitoring/observations points. PS L TE Link Verification Test The objective of the PS LTE Link Verification Test is to verify logical interface operation and end-to-end connectivity between the PS LTE UE and a test computer connected to the EPC. The PS LTE Link Verification Test will confirm the operation of the following logical interfaces: + S 1--eN odeB to MME + Slu-eNodeB to Packet Gateway • S5 -Serving Gateway to Packet Gateway + S6-MME to HSS + S 11 MME to Serving Gateway + Uu -Ue to eNodeB + SGi -PDN Gateway to IP Service etwork .. 3 .1.2.1 Test Preparation 3.1.3 The test wi ll use LAN analyzer software to log the link verification test activity . The software will be install ed on the test computer used to provide ICMP echo responses to ping requests from the mobile computer. The test message sequ ences will be manually initiated and logged by the operator of the mobile computer. Since the test is focused on verifying connectivity rather than coverage, the MDC will be situated close enough to the eNodeB site to ensure that the quality of the RF communication path is sufficient to reduce propagation errors that could be introduced into the test results. Since the link verification test i s valid only if the MDC is operating in so lid RF coverage areas , Motorola personnel will select a suitable test location prior to the start of link verification testing. e NodeB Handoff The objective of the eNodeB Handoff is to confirm the successful handoff from one eNodeB to another eNodeB as the UE VSM Model 1 roams within the coverage area of the PS LTE System. The eNodeB Handoff will confirm the following System functions: + Inter eNodeB Handoff + Session persistence during Handoff + X2 -eNodeB to eNodeB Fort Wo rth , TX Public Safety PS L TE System December 20 , 2013 Motorola Confi de ntial Res tricted Use or disclosure of this proposa l is It\ subject to the restrictions on t he title page W 3-2 Acceptance Test Pl an 3.1.3.1 A st arting and endi ng location will be id enti fie d prior to commencing Handover. The st artin g p oin t w ill b e located in th e coverage area of the i dentified prim ary eN odeB t o be tes te d and the ending p oint w ill b e l ocat ed in th e coverage area of th e se condary eNo deB to b e tes t ed . The dri ve team wi ll ve ri fy the t es t too l setup and function a lity prior t o b eg innin g the te st. Test Prep arat io n Th e test u ses b oth cl ie nt and server m essaging software based on industry standard UDP fo rmat. Th e server software wi ll be in st all ed on a test computer located w ith the EP C. Th e cl ient software w ill b e in stall ed on an M D C in th e test ve hicl e . Th e M D C will co nnec t to a Vehicl e M o dem with ext ernal ant enna. 3 .1.4 Respo nsibil ity Matri x Task I Responsibility I Deliverable Complete pre -test set-up using the Motoro la Test Preparation insta lled PS L TE network Complete infrastructure and the UE Have a minimum of one person Motorola Resource Assignment available onsite to perform the test. Provide and ensure that there are Fort Worth Test Environment no other subscribers active on the ne twork and no user data on the bac k hau l to Harris County , TX . Confirm that the eNodeB lin ks are Motorola Test Environment funct iona l before the test beg ins. Record all test results . Motorola Test Results Assign authorize d representative (s) Fort Worth Resource Assignment to monitor the test. Provide operational Mobile Data Fort Worth Test MDC (s ) and Computer(s) (MDC ) and vehicle (s) vehicle (s) for the duration of the test. Ensure that the configu red Fort Worth Test Environment bandwidth is ava ilable on the site li nks . Present results of test. Moto rola Test Results 3 .1.4.1 Comp let ion Criter ia Acceptance Testin g is co ns idere d compl et e upo n Fort Worth and M oto rola app rovals an d sign-offs of th e A cceptan ce Tests . Approval of th e Acceptance Tests co n stitutes System Acceptance, at wh ich time th e System wi ll b e avai l abl e for use by the City of Fort Worth. Motorola Confidential Restricted Use o r di sclos ure of thi s proposa l is subject to t he restrictions on the tit le page Fort Worth , TX Pub lic Safety PS L TE Sys tem December 20 , 20 13 Acceptance Test Plan 3-3 CITY OF FORT WORTH P25 UPGRADE -CHANGE ORDER 7 PRICING SUMMARY 2-12-14 CFW Price with # Track Site or Dept Description Incentives HGAC Price List Price 1 Subscriber 180 NNTN8092A Li Ion Battery $19,468.80 $25,200.00 2 Subscriber 42 NNTN7065B Multichargers $24,067 .26 $33,096.00 3 Operations Aeroflex Service Monitor $60,135.03 $69,641.00 4 Operations Diagnostix $50,070.00 TOTAL CHANGE ORDER $153,741.09 • 1.0 Definitions EXHIBIT E-4 City of Fort Worth L TE Subsystem Maintenance Statement of Work for Support These defined terms might not apply to every section of this Statement of Work . Cap italized terms used in this Statement of Work and not otherwise defined within the Statement of Work , or in the System Purchase Agreement or other applicable agreement (collectively , "Agreement") have the following meanings: 1.1 Case: Electronic tracking document for requests for service through the Motorola System Support Center. 1.2 Case Status : Identifier of the status of a Case from beginning to end . 1.3 Component(s): New or refurbished parts of equal quality. 1.4 Configuration Change Support: configuration task within the network allowing provisioning within network elements. 1.5 Connectivity: Remote access to the System via dial up or dedicated links 1.6 Continuously/Continuous : Seven (7) days per week , twenty four (24 ) hours a day, including holidays. 1.7 Customer: The end-user Customer as identified in the Agreement. 1.8 Customer Support Plan : A document mutually developed by Motorola and the Customer that provides information about the Customer and the System and describes the specific processes by which Motorola will deliver and the Customer will receive the services described in this Statement of Work. 1.9 Elements : Those device types present on the Customer's System whose status may be communicated to the SSC . 1.1 O Equ ipment: The equipment specified in the Equipment List as set forth in the Agreement , including any additions to the Equipment List during the Warranty Period . 1.11 L TE Warranty Support Period: The 12 month period commencing at the start of the Warranty Period for Equipment and Software as defined by the Agreement , such Warranty Support Period ex piring 12 months after System Acceptance . 1.12 Event: An alarm or informational notification received by Motorola through the Network Management tools . 1.13 Feature : A Software functionality. 1.14 Firmware : Software in object code form that is implanted or embedded in hardware . 1.15 FRU: Field Replaceable Unit, typically a board or module , contained within the Infrastructure. 1.16 Infrastructure : The fi x ed Equipment excluding mob iles , portables , and accessories . 1.17 Infrastructure Depot Operations or IDO : A Motorola facility which serves as Mo torola 's centralized location for infrastructure repair . 1.18 Loaner : Infrastructure that is owned by Motorola and serves as a temporary replacement wh ile the Customer's Infrastructure is being repaired . 1.19 Maintenance : The process for determining the cause of Equipment failure , removing , repairing , or replacing Components necessary to conform the Equipment with the manufacturer's specifications along with system-specific specifications , delivering and reinsta ll ing the Components and placing the Equipment back into operation. 1.20 MCNS: Mission Critical Network Services 1.21 Motorola Software: Software whose copyright is owned by Motorola or its affil iated company . 1.22 Non-Motorola Software : Software whose copyright is owned by a party other than Motorola or its affiliated company. 1.2 3 Notification: The point in time when the Custome r contacts Motoro la and requests service . 1.24 Optional Feature: A n additional Feature issued with a L TE EPC Release that is available to Customer at additional cost. PS LTE St ate m ent of Work-PS LTE Rl.O December 20, 2013 Page 1 1.25 Response : The event when a technician , a remote systems technologist or a remote network specialist beg ins to actively work on the techn ical issue , remotely or on-site , as determined by Motorola. 1.26 Restore/Restoration : The effort requ ired to bring Equipment to the level for which it was designed , engineered a nd adj u sted for performance in accordance with the manufacturer's published specifications , although such Equipment may not necessarily be malfunctioning . · 1.27 Servicer: a Motorola Autho r ized Service Station or Motorola Field Service personnel. 1.28 Severity Level: The degree of adverse impact of an issue or Event. 1.29 Software: The Software furnished with the System including any Motorola Software and Non-Motorola Software. 1.30 Software License Agreement: The agreement or portion of an agreement pursuant to which Motorola licenses Software to Customer, including System Releases . 1.31 Special Product Feature : A Feature that is specially developed for Customer and which contains a functionality that is unique to Customer. 1.32 Standard Business Day: Monday through Friday , 8:30 a .m . to 4 :30 p.m., local time , excluding Motorola holidays. 1.33 Standard Feature : A software functionality for components of Customer's System that is available to Customer in the standard software release . 1.34 Start Date : Effective start date as listed on the Agreement. 1.35 System : The communications system as defined in the Communications System Agreement or other applicable Agreement. 1.36 Subsystem : The RAN and/or lower L TE EPC elements as requ ired by a client connecting to a hosted L TE EPC . 1.37 System Acceptance : Unless otherwise defined in the Communications System Agreement , the date upon which Motorola has successfully completed all of the System tests as described in the acceptance test plan . 1.38 System Release: One software version release on a part icular platform . PS L TE R1 .0 example is where 1 is the platform indicator and .0 is software version release indicator. 1.39 System Support Center or SSC : a Motorola facility which serves as Motorola 's centralized system support facility to compliment the field support resources . 1.40 Systemic : A recurring Software or hardware defect that significantly affects the operation of the System . 1.41 Technical Support Operations or TSO : A centralized telephone support help desk that provides technical support for Motorola customers who have purchased products from Motoro la (Network & Enterprise) or who have a contract for technical support . 1.42 Vendor: Any manufacturer (other than Motorola) or third party that services or repairs Infrastructure or subscriber equipment. 1.43 Verification : Contacting the appropriate designated person to verify the System is operational (original problem resolved ) and closing the Case . 1.44 Work-around : A change in the followed procedures or data supplied by Vendor to avoid error without substantially impairing use of the Equ ipment. 1.45 Work Flow : A step-by-step process including instruction or direction for routing , handling , and processing information at a given agency. 2.0 L TE System Support Statement of Work 2.1 Description of Services Since the City of Fort Worth wil l be participating in a hosted environment with the Harris County L TE EPC infrastructure , the warranty support provided by Motorola will cover the City of Fort Worth subsystem of eNBs and partial L TE EPC network components. The following assumptions outline conditions re quired for Motorola to provide warranty support. If these assumptions or syste m design chang e, Motorola will work with the City of Fort Worth to provide an updated warranty s up port prog ram. PS LTE St atement of Work -PS LTE Rl.O December 20, 2013 Page 1 Assumptions : 1. Fort Worth will act as a subsystem , connecting into the Harris County Hosted L TE EPC System. 2. Fort Worth intends to enter into a hosting agreement with Harris County providing for system monitoring and operation. 3. Fort Worth intends to enter into an agreement with Harris County providing Motorola access to the hosted L TE EPC for purposes of technical support of Fort Worth eNBs and partial L TE EPC network components . 4 . Fort Worth , Harris County and Motorola will coordinate all system wide maintenance needs and upgrades. 5. Overall network performance and operation will be the responsibility of Harris County , who will keep Fort Worth and Motorola apprised of network status . The Motorola L TE System Support service is a support package designed to support the Equipment and Motorola Software components of a new L TE System during Warranty Period. During the Warranty Period , Motorola understands that there will be a relationship between the City of Fort Worth L TE subsystem and the Harris County L TE EPC system. The Motorola Warranty services described here are included in the price of the System. After the Warranty Period expires , these services are available for purchase under a separate agreement. Warranty services will be provided in accordance with the terms and conditions set forth herein . If any conflict exists between the Statement of Work provisions and the terms and conditions , the terms and cond itions shall prevai l. All services described in this Statement of Work will be provided in accordance with the terms of the Agreement and will cover only the L TE Equipment and related Motorola Software. Motorola System Support is comprised of the following services that are described in greater detail in this Statement of Work and are intended for the L TE Subsystem : 2.1.1 Network Monitoring -Section 3.0 Network Monitoring bundles the following services: Network Monitoring , On-Site Infrastructure Response , Dispatch Service . 2.1 .2 Technical Support -Section 4.0 2.1 .3 Software Maintenance Plan -Section 5.0 2 .1.4 Infrastructure Software Installation -Section 6.0 2 .2 Ex pansion, Replacement. or Phased Implementation Equipment After System Acceptance, if new Equipment is being integrated with an ex isting System to expand the System (either as a subsequent phase of a multi phase proj ect or ex pansion due to another entity joining the System ) , or to replace a major part of the System , then such new Equipment will be covered as follows : If the existing System is covered under its original Warranty program , the new Equipment will be covered as if it were part of the original System for the remainder of the Warranty Period . If the existing System is not covered under its or iginal Warranty program but is covered under a service agreement with Motorola to provide services, then the new Eq uipment will be covered at the same level of service for the rema inder of the term of that service PS LT E Statement of Work-PS LTE Rl .0 Dece mber 20, 2013 Page 2 2.4 agreement and t he price for the service agreement will be increased to cover the additional Equipment. If the existing System is not covered under either its original Warranty program or a service agreement with Motorola, the new Equipment is covered only by the Equipment warranty. General Description of Statement of Work for Support 2.4 .1 Motorola has the following responsibilities : 2.4.1.1 Prepare a Customer Support Plan in conjunction with the Customer, preferably before System Acceptance . 2.4.1 .2 Respond in accordance to pre-defined Response times upon receipt from Customer of Customer managed passwords required for proper access to the Customer's System . 2.4.1.3 Apply additional support charges above and beyond the contracted service agreements that may apply if it is determined that System faults were caused by the Customer making changes to critical System parameters . 2.4 .2 Customer has the following responsibilities : 2.4.2 .2 Prepare a Customer Support Plan in conjunction with Motorola , preferably before System Acceptance. The Customer must provide all information necessary to complete the Customer Support Plan . 2.4 .2 .3 Cooperate with Motorola and perform all acts that are reasonable or necessary to enable Motorola to provide the Warranty services to Customer. 2.4.2.4 Provide all Customer managed passwords required to access the Customer's System to Motorola upon request or when opening a Case to request service support or enable Response to a technical issue . 3.0 Network Monitoring Statement of Work Providing services in this section is contingent upon satisfaction of the assumptions stated in Section 2.1 3.1 Description of Services Overview: Network Monitoring is a bundled service offering that provides Network Monitoring, Dispatch Service and On-Site Infrastructure Response services to the Customer . This service is applicable only for the L TE subsystem Infrastructure . Network Monitoring includes the monitoring where possible of the L TE subsystem infrastructure. Motorola will monitor Elements of the L TE System for Events . The L TE Fault Monitoring service provides integration of fault notifications from the entire Motorola system offering , and presentation of alarms via a unified alarm manager. Once an event or activity is detected at the NOC , the SSC system technologist will forward the incident to the SSC Dispatch Center Operat ion s, and place the incident in 'h igh priority' status . The Sub System is continuously monito red in 'high priority' status throughout the troubleshooting and repair process . Event records are cleared and returned to 'normal ' status when the field technician notifies the NOC that a resolution is in place . PS LTE Statement of Work-PS LTE Rl .O December 20, 2013 Page 3 -· Dispatch and Case Management Service provides a central point of contact (via a toll free telephone number) to receive technical service requests and/or to dispatch technical support resources to your locations per specified service level agreement(s) following a documented process for prioritizing and assigning service calls and requests . Our systems support center dispatch operations team is available 24 hours per day, 7 days per week , and 365 days per year, and is staffed with qualified personnel who understand Motorola 's service delivery process . Case notes are updated continuously throughout the repair process to ensure that all parties understand the steps taken by field and SSC personnel involved restoration process. All cases are managed to completion , and case notes are available to Motorola customers via Motorola-On-Line (MOL) web access . The On-Site Infrastructure Response service provides local , t rained and qua lified technicians who arrive at your location to diagnose and restore the communications network. This includes running diagnostics on the Infrastructure or FRU (Field Replacement Unit) and replacing defective infrastructure or FRU . Following proven response and restoration processes , Motorola 's System Support Center (SSC) will contact local service personnel and dispatch a qual ified technician to your site . An automated escalation and case management process ensures that technician site arrival and system restoration comply with contracted response times (as described in the attached table). The system technician will respond to the Fort Worth location based on pre-defined severity levels . Through MoJorola Online , the customer has the ability to view case management details , add notes to the case or track case progress . The SSC will maintain contact with the on-site technician until System Restoral and case is closed . 3.2 Motorola Responsibilities 3 .2 .1 Provide dedicated Connectivity through a private network connection necessary for monitoring the Fort Worth L TE Sub System . 3.2 .2 If determined necessary by Motorola , provide Motorola owned equipment for monitoring L TE Sub System elements . 3.2 .3 Verify Connectivity and Event monitoring prior to System Acceptance or Start Date. 3.2.4 Continuously receive data from Fort Worth monitored Subsystem and Fort Worth initiated service requests . 3.2 .5 Remotely access the Fort Worth 's Subsystem to perform remote diagnos is as permitted by Customer 3 .2.6 Create a Case , as necessary. Gather information to perform the following : 3.2 .6 .1 Characterize the issue 3.2.6 .2 Determine a plan of action 3.2 .6 .3 Assign and track the Case to resolution . 3 .2.7 Dispatch a Servicer, as required , by Motorola standard procedures and provide ne cessary Case information 3.2 .8 Ensure the required personnel have access to Customer information as needed . 3 .2 .9 Disable and enable L TE Subsystem devices , as necessary , for Servicers . PS LT E St atement of Wo r k-PS LTE Rl.O Dece m be r 20, 2013 Page 4 3.2.10 Verify with Customer that Restoration is complete or System is functional , if required by Customer's repair Verificat ion preference described in the Customer Support Plan required by section 3.5. If V erification by Customer cannot be completed with in 20 minutes of Restoration , the Case will be closed and the Servicer will be released. 3.2.11 Escalate the Case to the appropriate party upon ex piration of a Response time . 3.2.12 Close the Case upon receiving notificat ion from Customer or Servicer, indicating the Case is resolved . 3 .2 .13 Notify Customer of Case Status , as described in the Customer Support Plan 3 .2 .14 Respond in accordance to pre-defined Response t imes upon receipt from Customer of Customer managed passwords required for proper access to the Customer's System 3.1 Customer Responsibilities 3 .1.1 Allow Motorola Continuous remote access to obtain System availability and performance data 3 .1.2 Provide Motorola with pre-defined Customer information and preferences prior to Start Date necessary to complete Customer Support Plan ., including , but not limited to : 3.1.2 .1 Case notification preferences and procedure 3.1.2.2 Repair Verification Preference and procedure 3.1.2.3 Database and escalation procedure forms 3.1.2.4 Submit changes in any information supplied in the Customer Support Plan to the Customer Support Manager 3 .1.3 Provide the following information when initiating a service request: 3.1.3 .1 Assigned System ID number 3 .1.3.2 Problem description and site location 3.1.3.3 Other pertinent information requested by Motorola to open a Case 3 .1.4 Notify the SSC when Customer performs any activity that impacts the Subsystem . (Activity that impacts the Subsystem may include , but is not lim ited to , installing software or hardware upgrades , performing upgrades to the network , or taking down part of the system to perform maintenance .) 3 .1.5 Provide all Customer managed passwords required to access the Customer's Subsystem to Motorola upon request or when opening a Case to request service support or enable Response to a technical issue. 3.1.6 Pay additional support charges above and beyond the contracted service agreements that may apply if it is determined that Subsystem faults were caused by the Custome r making changes to critical System parameters PS LT E Statement of Work-PS LTE Rl.O Dece m ber 20, 2013 Page 5 '• • 3.1. 7 Cooperate with Motorola and perform all acts that are reasonable or necessary to enable Motorola to provide the services described in th is SOW 4.0 Technical Support Statement of Work Providing services in this section is contingent upon satisfaction of the assumptions stated in Section 2.1 4.1 Description of Services Technical Support service provides ce ntralized remote telephone support for technical issues that require a high level of communications systems expertise or troubleshooting on Equipment. The SSC 's Technical Support Operation is staffed with technologists who specialize in the diagnosis and resolution of L TE system performance issues. Technical Support Service (i) does not include software upgrades that may be required for issue resolution ; (ii) does not include Customer training ; and (iii) is only available for those system types that are supported and approved by Technical Support Operations. 4.2 Motorola responsibilities: 4.2.1 Respond to requests for Technical Support for the Restoration of failed Systems and diagnosis of operation problems in accordance with the response times set forth. 4 .2 .2 Advise caller of procedure for determining any additional requirements for issue characterization and Restoration, including providing a known fix for issue resolution when available. 4.2 .3 Attempt remote access to the L TE System where available for remote diagnostics , when possible . 4.2.4 Maintain communication with the Servicer or Customer in the field until close of the Case , as needed. 4.2.5 Coordinate technical resolutions with Vendor(s), as needed . 4.2.6 Escalate and manage support issues , including Systemic issues , to Motorola engineering and product groups, as applicable . 4.2 .7 Escalate the Case to the appropriate party upon expiration of a Response time. 4 .2.8 Provide Configuration Change Support and Work Flow changes to a System that has remote access capability. 4 .2.9 Determine , in its sole discretion, when a Case requires more than the Technical Support services described in this SOW and notify Customer of an alternative course of action . 4.3 Customer responsibilities: 4.3.1 Provide Motorola with pre-defined information prior to Start Date necessary to comple te the Customer Support Plan . 4.3.1.1 Submit changes in any information supplied in the Customer Support Plan to the Customer Support Manager . 4.3 .2 Contact the SSC in order to access the Technical Support Operation , provide name of ca ll er, name of Customer , System ID number, Service Agreement number, site (s) in questions , and brief description of the problem . 4.3 .3 Supply on -site presence when requested by SSC . 4.3.4 Validate issue resolution prior to close of the Case . PS LT E St at em ent of Wo r k-PS LTE Rl.0 Decem ber 20, 2013 Page 6 4.3 .5 Allow Motorola remote access to the L TE System by equipping the System with the necessary Connectivity . 4.3 .6 Acknowledge that Cases will be handled in accordance with the times and priorities as defined . 5.0 Software Services Statement of Work 5 .1 Description of Service Motorola will provide to City of Fort Worth Software services in accordance w ith this Statement of Work. Motorola will provide Software Updates for L TE Release R2 .0 and R3.0. Software Services cons ists of design services for System Updates and review of System audit data . Motorola will review System audit data along with an Equipment list to avoid potential Software incompatibilities between Eq uipment that is being upgraded versus Equipment, which is not upgraded. Motorola will identify additional Equipment and engineering, (if applicable) for the System that is required as a result of the upgrade and will recommend a plan for installation of this additional Equipment. Implementation of this installation plan is not included with these Software Services . 5.2 Motorola responsibilities : 5.2.1 Provide to Customer the software updates for L TE Releases R2 .0 and R3.0 5 .2 .2 Provide to Customer (in response to a Customer order) those Features included in an System Update that apply to the Motorola and certified third party software in Customer's ex isti ng L TE System components . 5.2.3 Perform the following Software upgrade design: 5.2 .3 .1 Review Infrastructure System audit data as needed. 5.2.3.2 Identify additional System equ ipment needed to implement a System Update , if applicab le. 5 .2 .3 .3 Complete a proposal defining the System Update , Equipment requirements , installation plan , and impact to System users. 5.2 .3.4 Advise Customer of probable impact to System users during the_ actual field upgrade implementation . 5.3 Customer responsibilities: 5.3 .1 Customer must provide coordination and timeline for updates with Harris County L TE EPC updates 5 .3 .2 Customer must coordinate with Mo torola to provide updates for L TE Releases R2.0 and R3.0 5.3 .3 Cooperate with Motorola and perform all acts that are reasonable or ne cessary to enable Motorola to provide these services to Customer 6.1 Infrastructure Software Installation Statement of Work 6 .1 Des c ription Of Service PS LT E St atement of Work-PS LTE Rl .0 Dece mber 20, 2013 Page 7 .. _., .. , # Infrastructure Software Installation provides the technical resources to install and activate two (2 ) L TE System Releases (R2 .0 and R3.0) during the Warranty Period . Exclusion This service excludes the Software installation for any Subscriber software installation. 6.2 Motorola responsibilities : 6.2.1 Install L TE System Updates , provided pursuant to the Software Service Statement of Work , on infrastructure equipment. 6.3 Customer responsibilities : 6 .3.1 Purchase additional Equipment needed to implement System Updates if required. 6 .3.2 If applicable, purchase a Software upgrade for the L TE system. 6.3.3 Inform System users of update plans and scheduled System downtime. Perform appropriate system backups and make them readily available during the installation of the System Update . 6.3.4 Properly store and make available purchased software and hardware needed for installation of the System Update . 6.3 .5 Customer must provide coordination and timeline for updates with Harris County L TE EPC updates. Terms and Conditions for Warranty SECTION 1 SERVICE DESCRIBED A. Motorola will provide Warranty services for the Equipment in accordance with the following standards : (i) Motorola / Ericsson parts or parts of equal quality will be used; (ii) the Equipment will be serviced at levels set forth in Motorola's and Ericsson's product manuals ; and (iii) routine service procedures that are prescribed by Motorola and Ericsson will be followed . B. At Customer's request , Motorola may provide additional services at Motorola 's then applicable rates for such services. C . Customer must maintain , and upon reasonable request by Motorola, provide a complete equipment list indicating serial numbers , model numbers , and location of Infrastructure Equipment. D . Customer must immediately notify Motorola in writing when any Equipment is added , lost , damaged , or stolen, or taken in or out of service. E. Customer must notify Motorola immediately of any Equipment failure. SECTION 2 EXCLUDED SERVICES A. Warranty Services exclude the repair or replacement of Equipment that has become defective or damaged from use in other than the normal , customary , intended , and authorized manner; use not in compliance with applicable industry standards ; excessive wear and tear ; or accidents , liquids, power surges , neglect, acts of God , or other fo rce majeure events . B. Motorola has no obligation for any transmission medium , such as telephone line s , computer networks , or the worldwide web , or for Equipment malfunction caused by such transmiss ion medium. C . Unless specifically included in a writing executed by Motorola , Service of Equipment excludes items that are consumed in the normal operation of t he Equipment , such as batteries , magnetic tapes , and computer supplies ; upgrading or reprogramming of Equipment (unless part of an System Update or replacement); accesso ries , belt clips , battery chargers, custom or special products , or modified units ; or repair or maintenance of any transmission line, antenna , PS LTE Sta t em en t of Work-PS LT E Rl.O Decem ber 20, 2013 Page 8 microwave equ ipm ent , towe r or tower light ing , duplex er , co m biner , dong les , or multicoupler. SECTION 3 RIGHT TO SUBCONTRACT/ASSIGNMENT Motorola may assign its rights and obligations and may subcontract any portion of Motorola 's performance under the Warranty program. SECTION 4 TIME AND PLACE OF SERVICE Warranty Servic es wi ll be provided at the location specified in the Warranty Statement of Work . When Motorola performs service at the Customer's location , Customer w ill prov ide Motorola , at no charge , a non-hazardous and secure work environment with adequate shelter, heat, air condition ing , light , and power , and with full and free access to the Equipment. Customer will provide all information pertaining to the hardware and software elements of any system with which the Equipment is interfacing so that Motorola may perform its services . Unless otherwise specified in the Warranty Statement of Work , the hours of service will be 8 :30 a.m . to 4 :30 p .m ., loca l time , excluding weekends and hol idays . Customer will pay any cha rges associated w ith helicopter or other unusual access requirements or ex penses . SECTION 5 WARRANTY Motoro la warran ts that its services under th is Warranty program will be free of defects in materials and workmanship for a period of ninety (90) days from the date of performance of the services . MOTOROLA DISCLAIMS ALL OTHER WARRANTIES , EX PRESS OR IMPLIED , INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE . PS L TE St at e m ent of W o r k -PS LT E Rl .0 December 20, 2013 Page 9 .. -•