Loading...
HomeMy WebLinkAboutContract 37208 MOTONOLA intelligence everywhere CITY 8-C TARY31-1Qa CONTr��r;qj�-No. COMMUNICATIONS SYSTEM AGREEMENT CITY OF FORT WORTH, TX LOCAL GOVERNMENT REFRESH REVISION HISTORY: 08-14-07 Draft jp Draft 10-18-07 REV JP Revised pricig_g added Cornet switch City of Fort Worth,Texas City of Fort Worth, Texas COMMUNICATION SYSTEM AGREEMENT City of Fora Worthi Texas, Motorola, Inc., a Delaware corporation ("Motorola"), and the City of Fort Worth, Texas, a municipal corporation organized under the laws of the state of Texas and situated in Tarrant, Denton, and Wise counties, Texas ("Customer or the City") enter into this Communications System Agreement (the "Agreement" or "Communications System Agreement"), effective as of the last date signed below (the "Effective Date"), pursuant to which Customer will purchase and Motorola will provide Customer with a refresh of the Local Government analog simulcast communications system. Section 1 EXHIBITS The Exhibits below are hereby incorporated into and made a part of this Agreement. In interpreting this Agreement and resolving any ambiguities, the main body of this Agreement will take precedence over the Exhibits and any inconsistency between the Exhibits will be resolved in the order in which the Exhibits appear below. Exhibit A Motorola Software License Agreement Exhibit B Payment Terms Exhibit C Technical Documents C-1 Equipment List and Pricing Exhibit D System Acceptance Certificate Section 2 DEFINITIONS Capitalized terms used in this Agreement and not otherwise defined within the Agreement have the following meanings: "Communications System" or "System" is the communications system described in Exhibit C, including, but not limited to, the Equipment, Software and all services described in the, Statement of Work, Acceptance Test Plan and Equipment List. "Equipment" is the equipment specified in the Equipment Lists "Motorola Software" is software whose copyright is owned by Motorola. 15t Page 2 Motorola January 9,2008 City of Fort Worth, Texas "Non-Motorola Software" is software whose copyright is owned by a party other than Motorola. "Software" includes Motorola and any Non-Motorola Software that may be furnished with the Communications System. Section 3 SCOPE OF AGREEMENT A. SCOPE OF WORK. Motorola will assemble and integrate the Equipment and Software, and deliver, install and test the Communications System at designated sites, as specified in Exhibit C and in accordance with this Agreement and, specifically, with the Project Timeline and Implementation Schedule, as specified in C-2, and the Payment Terms, as specified in Exhibit B. Customer will perform its responsibilities as specified in Exhibit C and in accordance with this Agreement. Motorola shall perform all work described in and pursuant to this Agreement in a professional manner and in conformance to professional standards. B. CHANGE ORDERS. Either party may request changes within the general scope of this Agreement. If a requested change causes an increase or decrease in the cost of or time required for the performance of this Agreement, Motorola and Customer will agree to an equitable adjustment in the Agreement price or performance schedule, or both; provided, however, that if Motorola requests the change and Customer consents, such change shall not result in or create any delay in any milestone set forth in the Project Schedule set forth in C-2 unless otherwise specifically agreed to in writing by Customer. Motorola is not obligated to comply with requested changes unless and until both parties execute a written change order. Changes that increase Customer's costs under this Agreement by more than $25,000,00 must be approved by Customer's City Council prior to execution of a written change order. C. ADDITIONAL_ PRODUCTS. For one (1) year after the date of Final System Acceptance, Customer may purchase additional Equipment as add-ons to the Communications System ("Add-on Equipment"). If Customer and Motorola have agreed to a convention for processing electronic data interchange ("EDI") transactions, purchase orders may be transmitted electronically. Each purchase order must specifically refer to this Agreement and will be an offer by Customer subject to Motorola's acceptance. Except for pricing and delivery terms, which must be stated on the purchase order, Customer and Motorola agree that the applicable terms of this Agreement will be the only terms and conditions that govern the purchase and sale of products identified on such purchase orders. Customer and Motorola agree that the procedure for payment of all additional products so purchased will be in accordance with the procedure set forth in Section 5 this Agreement. D. MAINTENANCE SERVICE. After the first year following expiration of the Warranty Period, Customer may purchase maintenance services and software support for the MOTOROLA Page 3 Motorola ��7 January 9,2008 City of Fort Worth, Texas Communications System pursuant to a separately executed service agreement and software subscription agreement between Motorola and Customer. E. MOTOROLA SOFTWARE. Any Motorola Software furnished will be licensed to Customer solely according to the terms and restrictions of the Software License Agreement attached as Exhibit A. Customer hereby accepts all of the terms and restrictions of the Software License Agreements as negotiated between Motorola and the City of Fort Worth. F. NON-MOTOROLA SOFTWARE. Non-Motorola Software furnished by Motorola will be subject to the terms and restrictions of its copyright owner unless such copyright owner has granted to Motorola the right to sublicense such Non-Motorola Software, in which case the Software License Agreement (including any addendum to satisfy such copyright owner's requirements) shall apply; provided, however, that nothing in this Section 31, the Software License Agreement or any restrictions or requirements of copyright owners of Non-Motorola Software, shall be deemed or construed to limit or restrict in any way the System Functionality Warranty provided by Motorola in accordance with Section 8.13 of this Agreement. G. PROJECT MANAGEMENT. Motorola shall assign a project manager acceptable to Customer, who is authorized to exercise technical direction of all duties and obligations of Motorola and Motorola's subcontractors under this Agreement. Motorola agrees to meet and consult with Customer before designating a new or alternate project manager and allow Customer reasonable right of refusal. Motorola's project manager shall have authority to negotiate changes in or amendments to this Agreement on behalf of Motorola. In addition, any and all of Motorola's officers, agents, employees, and subcontractors may, at the option of Customer, be subject to a security check at any time. Customer shall have the right to require the removal from Customer's premises any of Motorola's officers, agents, employees or subcontractors if Customer reasonably determines, such individual's presence is inappropriate under the circumstances, and Motorola agrees that it will immediately comply with and assist Customer in such removal. At Customer's request, Motorola shall promptly provide Customer with the names, dates of birth, drivers' license numbers and other identification documents required by Customer of Motorola's officers, agents, employees or subcontractors that will be present on Customer's premises in order for Motorola to fulfill its obligations under this Agreement for the purpose of standard background/criminal checks. H. PROJECT STATUS MEETINGS. From the Effective Date of this Agreement until Final System Acceptance, Motorola agrees to conduct periodic project status meetings at locations specified by Customer. These meetings shall be conducted on not less than a monthly basis and may be conducted more frequently if the parties agree. MOTOROLA Page 4 Motorola January 9,2008 City of Fort Worth, Texas Section 4 PERFORMANCE SCHEDULE A. Motorola and Customer agree to perform their responsibilities in accordance with the Statement of Work and the Project Timeline and Implementation Schedule. Payments are to be activity based 1 related, not cumulative time based / related. If payments are tied to deliverables, if the deliverable moves so does the payment. B. By executing this Agreement, Customer authorizes Motorola to proceed with the manufacture, assembly, integration, delivery, installation, and testing of the Communications System. No further notice to proceed, purchase order, authorization, resolution, or any other action will be required unless required by applicable laws or ordinances. Section 5 PAYMENT SCHEDULE A. The total contract price for all equipment, software and services provided under this Agreement is not to exceed $ 343,975 for which Customer agrees to make payments in accordance with the Payment Terms in Exhibit B. B. Freight charges for all Equipment, software and any and all other products and supplies provided hereunder are included in the Contract Price. All material to be shipped FOB Destination. C. Notwithstanding anything to the contrary in this Agreement, Motorola understands that Customer has appropriated no more than $343,975 _for purposes of the manufacture, assembly, integration, delivery, installation and testing of the Communications System and all other work or services provided by Motorola or its subcontractors under this Agreement. Motorola understands and agrees that Customer shall not be liable to Motorola or any of its subcontractors for any sums in excess of such amount unless Customer's City Council first approves and appropriates sums in excess of such amount, in which case such additional sums shall also be included as part of the Contract Price as defined and interpreted in this Agreement. D. All invoices from Motorola shall be submitted to Customer's Project Manager or, in his or her absence, the Director of Customer's IT Solutions Department. Customer shall pay invoices for services and deliverables received and approved by Customer within thirty (30) days of receipt. If Customer has any questions or disputes regarding such invoices, Motorola shall make Motorola personnel available as needed to answer or resolve such, and Customer shall be allowed additional time to pay the questioned or disputed portion of those invoices. MOVX OLA Page 5 Motorola January 9,2008 City of Fort Worth, Texas Section 6 TRAINING Any training to be provided by Motorola to Customer will be described in the Statement of Work. Customer will notify Motorola immediately if a date change for a scheduled training program is required. If Motorola incurs additional costs because Customer reschedules a training program less than thirty (30) days before its scheduled start date, Motorola may recover these additional costs. Section 7 SITES A. In addition to its responsibilities described in the Statement of Work, Customer agrees to provide a designated project director, also known as the Project Manager, procure any necessary construction permits, building permits, zoning variances and the like, provide access to the sites identified in the Exhibits as requested by Motorola, and have such sites available for installation of the Equipment by Motorola in accordance with the performance schedule and Statement of Work. B. If either Motorola or Customer determines during the course of performance of this Agreement that the sites identified in the Exhibits are no longer available or desired, or, if subsurface, structural, adverse environmental or latent conditions at any site differ from those indicated on the specifications in the Exhibits, Motorola and Customer will promptly investigate the conditions and in good faith negotiate an equitable solution and, based on such solution, execute any written amendments to this Agreement or the Exhibits attached hereto that may be deemed necessary by both parties. C. If Customer and Motorola determine that any change requested by Customer in site availability, installation plans, or specifications may require an adjustment in the Contract Price or in the time required for the performance of this Agreement, the parties will in good faith negotiate an equitable solution and, based on such solution, execute any written amendments to this Agreement or the Exhibits attached hereto that may be deemed necessary by both parties. Amendments will be via the Change Order process described in "Section 3 Scope of Agreement, Paragraph B. Change Orders." SECTION 8 FINAL SYSTEM ACCEPTANCE A. Motorola will perform tests of various components of the Communications System and a final test of the fully integrated Communications System in accordance with the Statement of Work/Acceptance Test Plan. Acceptance of the Communications System will occur upon the successful completion of such final testing of the System as a fully integrated Communications System, as outlined in and in accordance with the Statement of Work/Acceptance Test Plan ("System Acceptance"), at which time both parties shall promptly document any deficiencies, failures, or problems, in the form of a Punch List. Final System Acceptance Certificates will not be issued by the City of Fort Worth until all issues on the Punch List have been resolved to the MO7"t>RO4'A Page 6 Motorola January 9,2008 City of Fort Worth, Texas sole satisfaction of the City of Fort Worth ("Final System Acceptance"). Customer shall not unreasonably delay Final System Acceptance. In addition, both parties shall promptly execute certificates of subsystem acceptance upon the successful completion of testing of such subsystems, as outlined in and in accordance with the Acceptance Test Plan attached hereto. Customer and Motorola will jointly prepare a list of such omissions and variances which Motorola will correct according to an agreed upon schedule with clearly defined and agreed to due dates. Reference to `System Acceptance' SHALL NOT equate to `Final System Acceptance'. B. BENEFICIAL USE. Customer acknowledges that Motorola's ability to perform its implementation and testing responsibilities may be impeded if Customer begins using the System before System Acceptance. Therefore, Customer will not commence Beneficial Use before System Acceptance without Motorola's prior written authorization, which will not be unreasonably withheld. Motorola is not responsible for System performance deficiencies that occur during unauthorized Beneficial Use. Upon commencement of Beneficial Use, Customer assumes responsibility for the use and operation of the System. Section 9 WARRANTY A. WARRANTY PERIOD. Upon System Acceptance or Beneficial Use, whichever first occurs, the System Functionality representation described below is fulfilled. The Equipment and Motorola Software is warranted for a period of one (1) year after System Acceptance in accordance with the applicable limited warranties shown below. Customer must notify Motorola in writing if Equipment or software does not conform to these warranties no later than one month after the expiration of the Warranty Period. B. SYSTEM FUNCTIONALITY WARRANTY. Motorola represents that the Communications System will satisfy the functional requirements in Exhibit C. Upon System Acceptance, this System Functionality representation is fulfilled. After System Acceptance, the Equipment Warranty set forth below and the Software Warranty set forth in the Software License Agreement will apply in accordance with their terms and conditions. Motorola will not be responsible for performance deficiencies of the System caused by ancillary equipment not furnished or specified for use by Motorola or another party in accordance with the provisions of this Agreement that is attached to or used in connection with the System provided hereunder. Additionally, Motorola will not be responsible for System performance where the functionality is reduced for reasons beyond Motorola's control including but not limited to i) an earthquake, adverse atmospheric conditions or other natural causes; ii) the construction of a building that adversely affects the microwave path reliability or Radio Frequency (RF) coverage; iii) the addition of additional frequencies at System sites that cause RF interference or intermodulation; iv) Customer changes to load usage and/or configuration outside the parameters specified in Exhibit C; v) any Mi?MAOLR Page 7 Motorola January 9,2008 City of Fort Worth, Texas other act outside the scope of the ordinary use of the Communications System by parties who are beyond Motorola's control, including Customer or its employees, contractors, consultants or agents. C. EQUIPMENT WARRANTY. Motorola warrants the Equipment against material defects in material and workmanship under normal use and service during the Warranty Period. The Warranty Period for non-Motorola manufactured Equipment will be stated in this section. At no additional charge and at its option, Motorola will either repair the defective Equipment, replace the defective Equipment with the same or equivalent Equipment acceptable to Customer or refund the purchase price of the defective Equipment, and such action on the part of Motorola will be the full extent of Motorola's liability hereunder. Repaired or replaced Equipment is warranted for the balance of the Warranty Period. All defective parts of the Equipment replaced under warranty shall become the property of Motorola. THIS WARRANTY DOES NOT APPLY TO a) Defects or damage resulting from use of the Equipment in other than its normal and customary manner. b) Defects or damage occurring from misuse, accident, water, or neglect. c) Defects or damage occurring from testing, operation, maintenance (except first line/front line echelon maintenance provided by Customer), installation, alteration, modification, or adjustment not (i) provided by Motorola pursuant to this Communications System Agreement or (ii) otherwise authorized in writing by Motorola. d) Breakage or damage to antennas unless caused directly by defects in material or workmanship. e) Equipment that has been subjected to unauthorized Equipment modifications, disassembly or repairs (including the addition to the Equipment of non-Motorola supplied equipment if not authorized by Motorola) which adversely affect performance of the Equipment or interfere with Motorola's normal warranty inspection and testing of the Equipment to verify any warranty claim. f) Equipment that has had the serial number removed or made illegible. g) Batteries that carry a separate limited warranty. h) Equipment which, due to illegal or unauthorized alteration of the software/firmware in the Equipment, does not function in accordance with Motorola's published specifications or with the FCC type acceptance labeling in MOTOROLA Page 8 Motorola January 9,2008 City of Fort Worth, Texas effect for the Equipment at the time the Equipment was initially distributed from Motorola. i) Scratches or other cosmetic damage to Equipment surfaces that does not affect the operation of the Equipment. j) Software (which is covered by the Software License Agreement). k) Normal and customary wear and tear. 1) On site response, except where it pertains to specific new equipment, that is purchased as part of this Agreement. m) After hours warranty support. n) Systems diagnostics or response is not included as part of this Agreement. o) Any services requested that do not pertain to specific equipment that is part of this Agreement, will be billed at prevailing time and material rates. D. MOTOROLA SOFTWARE WARRANTY. Motorola Software is warranted in accordance with the terms of the Software License Agreement attached as Exhibit A. E. These express limited warranties as set forth in this Section are extended by Motorola to the original end user purchasing or leasing the System for commercial, industrial, or governmental use only, and is not assignable or transferable. These are the complete warranties for the Equipment and Software provided pursuant to this Agreement. F. THESE WARRANTIES ARE GIVEN IN LIEU OF ALL OTHER WARRANTIES. MOTOROLA DISCLAIMS ALL OTHER WARRANTIES OR CONDITIONS, EXPRESS OR IMPLIED, INCLUDING THE IMPLIED WARRANTIES OR CONDITIONS OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Section 10 DELAYS A. Successful project implementation will require cooperation and fairness between the parties. Because it is impractical to provide for every contingency that may arise during the course of performance of this Agreement, the parties agree to notify the other in writing if they become aware that any condition will significantly delay performance. The parties will agree to reasonable extensions of the project schedule by executing a written change order that may, or may not, have a financial impact. M,O' ROLA Page 9 Motorola January 9,2008 City of Fort Worth,Texas B. Under no circumstances will either party be responsible for delays or lack of performance resulting from events beyond the reasonable control of that party ("Excusable Delays"). Such events include, but are not limited to, acts of God, weather conditions, compliance with laws and regulations (excluding Customer's failure to properly and timely apply for all required FCC licenses), governmental action, bid protests, fire, strikes, lock-outs, and other labor disruptions, material shortages, riots, acts of war, and an Excusable Delay of a Motorola subcontractor. C. Customer will make available to Motorola the sites when scheduled and Customer will not otherwise unreasonably delay or prevent Motorola's performance of its responsibilities. In the event of a Customer delay during the time of shipment, Motorola may ship the equipment as scheduled to a location as designated by the Customer or if no such location is designated, a Motorola designated storage facility. Motorola shall not ship equipment until advised by the City that the site is ready. If either party materially delays performance under this Agreement, Motorola and Customer shall discuss the reasons for the particular delay and negotiate in good faith a solution to address such delay and will execute a written change order that may, or may not, have a financial impact, if appropriate. Section I I DEFAULT A. If Motorola fails to complete delivery, installation or acceptance testing in accordance with this Agreement, Customer may consider Motorola to be in default, unless an Excusable Delay has caused such failure. Customer agrees to give Motorola written notice of such default. Motorola will have thirty (30) calendar days from the receipt of such notice to provide a written plan of action that is acceptable to Customer to cure the default. Such written plan of action shall include milestones necessary to cure the default and timetables for achieving those milestones and shall be signed by Motorola and Customer. B. If Motorola fails to cure the default within the timetables and in accordance with the plan of action that Customer has accepted, Customer may (i) terminate any unfulfilled portion of this Agreement and, at Customer's sole option, complete the Communications System at a quality and to a capability equaling, that specified in this Agreement through a third party or (ii) if the Communications System or any component thereof cannot be completed through a third party as provided in subsection (i) above, demand and receive specific performance by Motorola. If Customer completes the Communications System through a third party, Customer may recover all reasonable costs and expenses incurred in the course of completing the Communications System to a capability not exceeding that specified in the Agreement, less the unpaid portion of the Contract Price. Customer agrees to use its best efforts to mitigate such costs. Motorola's liability under this Section is subject to the limitations of the Section entitled Limitation of Liability of this Agreement. WI07+C ROL 4 Page 10 Motorola January 9,2008 City of Fort Worth, Texas Section 12 LIABILITY AND INDEMNIFICATION A. GENERAL LIABILITY AND INDEMNITY. MOTOROLA SHALL BE RESPONSIBLE FOR ANY AND ALL TANGIBLE PROPERTY LOSS OR DAMAGE AND/OR PERSONAL INJURY, INCLUDING DEATH, TO ANY AND ALL PERSONS, OF ANY KIND OR CHARACTER, WHETHER DEAL OR ASSERTED, TO THE EXTENT CAUSED BY THE NEGLIGENT ACT(S) OR OMISSION(S) OR INTENTIONAL MISCONDUCT OF MOTOROLA, ITS OFFICERS, AGENTS, SERVANTS, EMPLOYEES, AND/OR SUBCONTRACTORS, IN THE PERFORMANCE OF OR RELATED TO THE PERFORMANCE OF THIS AGREEMENT. IN ADDITION, MOTOROLA SHALL DEFEND, INDEMNIFY AND HOLD CUSTOMER HARMLESS FROM AND AGAINST ANY AND ALL LAWSUITS, CLAIMS, ACTIONS, DEMAND, LIABILITIES OR OTHER COSTS AND EXPENSES WHICH MAY ACCRUE AGAINST CUSTOMER TO THE EXTENT THAT THE SAME ARE CAUSED BY THE NEGLIGENT ACT(S) OR OMISSION(S) OR INTENTIONAL MISCONDUCT OF MOTOROLA, ITS OFFICERS, AGENTS, SERVANTS, EMPLOYEES, AND/OR SUBCONTRACTORS. THE TERMS, CONDITIONS AND PROVISIONS OF THIS PARAGRAPH SHALL, SURVIVE THE EXPIRATION OR TERMINATION OF THIS AGREEMENT. B. PATENT AND COPYRIGHT INFRINGEMENT. Motorola will defend at its expense any suit brought against Customer to the extent it is based on a claim that the Equipment or Motorola Software infringes a U.S. patent or copyright, and Motorola will indemnify for those costs and damages finally awarded against Customer which are attributable to any such claim. Motorola's duties to defend and indemnify are conditioned upon: Customer promptly notifying Motorola in writing of the infringement claim; Motorola having sole control of the defense of the suit and all negotiations for its settlement or compromise; and Customer providing to Motorola cooperation and, if requested by Motorola, reasonable assistance in the defense of the infringement claim. If a claim occurs, or in Motorola's opinion is likely to occur, Motorola may at its option and expense procure for Customer the right to continue using the Equipment or Motorola Software, replace or modify it so that it becomes non-infringing while providing functionally equivalent performance, or grant Customer a credit for the Equipment or Motorola Software as depreciated and accept its return. The depreciation amount will be calculated based upon generally accepted accounting standards for such Equipment and Motorola Software. Motorola will have no duty to defend or indemnify for any claim that is based upon the combination of the Equipment or Motorola Software with any software, apparatus or device not furnished by Motorola; the use of ancillary equipment or software not furnished by Motorola and that is attached to or used in connection with the Equipment or Motorola Software; any Equipment that is not Motorola's design or formula; a modification of the Motorola Software by a party other than Motorola; or MCi,PONOLA Page 11 Motorola January 9,2008 City of Fort Worth, Texas the failure by Customer to install an enhancement release to the Motorola Software that is intended to correct the claimed infringement. The foregoing states the entire liability of Motorola with respect to infringement of patents and copyrights by the Equipment, Motorola Software, or any of their parts. Section 13 DISPUTES A. Motorola and Customer will attempt to settle any claim or controversy arising from this Agreement through consultation and negotiation in good faith and a spirit of mutual cooperation. If those attempts fail, the dispute may be mediated by a mediator chosen jointly by Motorola and Customer within thirty (30) business days after notice by one of the parties requesting non-binding mediation. If both parties consent to mediation, Motorola and Customer will share the cost of the mediation equally. The parties may postpone mediation until they have completed some specified but limited discovery about the dispute. The parties may also replace mediation with some other form of non-binding alternate dispute resolution ("ADR") procedure. Any mediation, ADR procedure or other negotiations or meetings pertaining to a claim, controversy or problem arising under this Agreement shall be held at a location in Fort Worth, Tarrant County, Texas. B. Any dispute that cannot be resolved between the parties through negotiation or mediation within two (2) months after the date of the initial request for non-binding mediation may then be submitted by either party to a court of competent jurisdiction in accordance with Section 16.J of this Agreement. Each party consents to jurisdiction over it by such a court. The use of any ADR procedures will not be considered under the doctrine of laches, waiver, or estoppel to affect adversely the rights of either party. Either party may resort to the judicial proceedings described in this paragraph prior to the expiration of the two-month ADR period if (a) good faith efforts to attempt resolution of the dispute under these procedures have been unsuccessful or (b) interim relief from the court is necessary to prevent serious and irreparable injury to such party or any of its affiliates, agents, employees, customers, suppliers, or subcontractors. Section 14 LIMITATION OF LIABILITY Except for personal injury or death, Motorola's total liability to Customer for claims or damages asserted by Customer, whether for breach of contract, warranty, negligence, strict liability in tort, indemnification, or otherwise, will be limited to the total Contract Price. IN NO EVENT WILL MOTOROLA BE LIABLE FOR ANY LOSS OF USE, LOSS OF TIME, INCONVENIENCE, COMMERCIAL LOSS, LOST PROFITS OR SAVINGS, OR OTHER SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES IN ANY MAY RELATED TO OR ARISING FROM THIS AGREEMENT, THE SALE OR USE OF THE EQUIPMENT, OR THE PERFORMANCE OF SERVICES BY MOTOROLA PURSUANT TO THIS AGREEMENT. This Limitation of Liability will survive the expiration or termination of this Agreement. MCVr% 0L,A Page Motorola January 9,2008 City of Fort Worth, Texas Section 15 INSURANCE From the Effective Date of this Agreement until Final System Acceptance, Motorola shall maintain, in full force and effect, a policy or policies of insurance as specified in this Section 14 to cover risks related to Motorola's scope of work under this Agreement. At a minimum, Motorola shall provide coverage of the types and at the limits specified herein: • Commercial General Liability: $1,000,000.00 per occurrence; $2,000,000 annual aggregate; • Business Automobile Liability: $1,000,000 combined single limit • Worker's Compensation: Applicable Statutory Limits The insurers for all policies must be approved to do business in the State of Texas. Certificates of Insurance provided by Motorola under this Agreement shall (i) list Customer as an additional insured on the commercial general liability policy, and (ii) provide that the respective policy shall not be canceled, limited in scope or coverage, or non-renewed until after thirty (30) days prior written notice has been give to the Risk Manager, City of Fort Worth, 1000 Throckmorton Street, Fort Worth, Texas 76102. Motorola shall provide Customer with a copy of its Certificate(s) of Insurance prior to the effective date of this Agreement. Section 16 Termination Customer may terminate this Agreement, in whole or in part, at any time and for any reason following at least thirty (30) calendar days' advance written notice to Motorola. Customer shall pay Motorola for (i) all Equipment provided and services and other work performed by Motorola through the effective date of termination; (ii) actual and reasonable expenses incurred by Motorola in the removal of installation and test equipment from Customer's premises; and (iii) any actual and reasonable costs which may be borne by Motorola in the early and abrupt termination for convenience of subcontracts, provided that Customer has approved in writing the provisions of such subcontracts that relate to termination by Motorola or liquidated damages or other financial obligations of Motorola due to termination by Motorola, which approval shall not unreasonably be withheld. Section 17 FCC Licenses Customer will obtain and comply with all Federal Communications Commission ("FCC") licenses and authorizations required for the installation, operation and use of the System before the scheduled installation of the Equipment. Although Motorola might assist Customer in the preparation of its FCC license applications, neither Motorola nor any of its employees is an agent or representative of Customer in FCC or other matters. MOTO OLA Page 13 Motorola January 9,2008 City of Fort Worth, Texas Section 18 GENERAL A. TITLE AND RISK OF LOSS. Title to respective Equipment will pass to Customer upon delivery to Customer's facilities. Full risk of loss, however, shall not pass to Customer until completion of the Installation of Equipment Milestone set forth in Exhibit B provided, however, that after delivery of Equipment to Customer's facilities but before payment by Customer to Motorola for that Equipment, Customer shall be responsible for any losses or damages to Equipment to the extent that such are directly caused by the negligent act(s) or omission(s) or intentional misconduct of Customer, its officers, agents, servants and/or employees. Title to Software will not pass to Customer at any time. B. TAXES. The purchase price does not include any amount for federal, state, or local excise, sales, lease, service, rental, use, property, occupation, or other taxes, all of which (other than federal, state, and local taxes based on Motorola's income or net worth) will be paid by Customer except as exempt by law. C. CONFIDENTIAL INFORMATION. Customer and Motorola will not disclose to third parties any material or information that is identified by either party to the other as proprietary and confidential ("Confidential Information") without the other party's prior written permission unless required by law; provided, however, that Customer may disclose Confidential Information of Motorola to Customer's employees, agents, consultants and other contractors, in which case Customer shall identify to such parties the nature and obligations of Customer with respect to that Confidential Information. Notwithstanding the foregoing, Motorola understands and acknowledges that the Customer is a public entity under the laws of the State of Texas, and as such, all information held by Customer or that customer has a right of access to is subject to public disclosure under Chapter 552 of the Texas Government Code. Customer may be required to disclose information that may reveal Motorola proprietary information to third parties under the Texas Government Code or by any other legal process, law, rule or judicial order by a court of competent jurisdiction. If either Customer or Motorola is required by law to disclose such material or information, the disclosing party will notify the other party prior to such disclosure. D. DISCLAIMER OF LICENSE. Except as explicitly provided in the Motorola Software License Agreement included in Exhibit A, nothing in this Agreement will be deemed to grant, either directly or by implication, estoppel, or otherwise, any license or right under any patents, patent applications, copyrights, trade marks, trade secrets or other intellectual property of Motorola. E. ASSIGNABILITY. This Agreement may not be assigned by either party without the prior written consent of the other party except that Motorola may assign this Page 14 Motorola January 9,2008 City of Fort Worth, Texas Agreement to any of its affiliates or its right to receive payment following at least thirty (30) days' advance written notice to Customer. F WAIVER. Failure or delay by either party to exercise any right or power under this Agreement will not operate as a waiver of such right or power. G. SEVERABILITY. If any portion of this Agreement is held to be invalid or unenforceable, that provision will be considered severable and the remainder of this Agreement will remain in full force and effect as if the invalid provision were not part of this Agreement. H. HEADINGS AND SECTION REFERENCES. The headings given to the sections of this Agreement are inserted only for convenience and are not to be construed as part of this Agreement or as a limitation of the scope of the particular Section to which the heading refers. I. ENTIRE AGREEMENT. This Agreement (including the Exhibits) constitutes the entire agreement of the parties regarding the subject matter of this Agreement and supersedes all previous agreements and understandings, whether written or oral, relating to such subject matter. This Agreement may be altered, amended, or modified only by a written instrument signed by the duly authorized representatives of both parties. J. GOVERNING LAW AND VENUE. This Agreement will be governed by and construed in accordance with the laws of the State of Texas. Venue for any action arising under or related to the terms and conditions of this Agreement shall lie in state courts located in Tarrant County, Texas or in the United States District Court for the Northern District of Texas, Fort Worth Division. K. NOTICES AND CORRESPONDENCE. Notices authorized or required under this Agreement must be in writing and, along with all written correspondence, mailed via United States Mail, certified, return receipt requested, to the below addresses: City of Fort Worth Motorola, Inc. Attn: Project Manager Attn: Law Department IT Radio & Infrastructure Services 6450 Sequence Drive 1000 Throckmorton San Diego, CA 92121 Fort Worth, TX 76102 As to written correspondence from one party to the other that concerns or is related to the clarification, proposed solution or any other situation requiring a written response from the other party, both Motorola and Customer shall have a maximum of ten (10) business days from receipt to respond in writing to such correspondence. If the receiving party believes that the contents of such correspondence does not A1'OTCHOLA Page Motorola January ry 9,2008 City of Fort Worth, Texas conform to the requirements of this Agreement, or otherwise disagrees with such correspondence, it shall notify the sending party in writing within the above-stated ten (10) business days, defining in detail such non-acceptance. In the event that the receiving party finds the content of the correspondence in conformance to the requirements of this Agreement, it shall, within the above stated ten (10) business days, notify sending party in writing of this fact, and such notification shall constitute acceptance of the content of the correspondence delivered. Because certain Agreement deliverable documents requiring Customer's approval may require more than ten (10) business days for Customer to complete its review process, Customer may have up to thirty (30) business days to review and approve documents and manuals relating to the functional specification and administration of the System or any portion thereof. L. COPIES. Customer shall have the right to make as many copies of Motorola's written application system documentation as necessary for Customer's own internal use (including, but not limited to, any consultants or other contractors retained by Customer for assistance related to this Agreement or the Communications System) except as prohibited by copyright restriction. Customer agrees that authorized copies will contain any trade secret notice found in Motorola's original document. In addition, Customer shall have the right to make as many copies of any user manuals, technical manuals, maintenance manuals or other similar types of documents provided by Motorola under this Agreement as necessary for Customer's own internal use. Customer shall also have the right to make copies of Motorola's software programs and documentation except as may be specifically prohibited under the Software License Agreement. M. MOTOROLA SUBCONTRACTORS AND SUPPLIERS. Motorola may not subcontract with a third party for the provision of any services or materials whose value or cost exceeds $1,000.00 without the advance written consent of Customer which consent will not be unreasonably withheld. Motorola will enter into written contracts with all subcontractors that are approved by Customer, which contracts shall incorporate this Agreement for all purposes. In no event shall Customer's approval of any subcontractor of Motorola relieve Motorola of its responsibilities and obligations under this Agreement. Throughout this Agreement and all Exhibits attached hereto, references to the duties and obligations of a specific subcontractor of Motorola shall also be fully binding on and enforceable against Motorola as if Motorola itself were providing the services or supplies provided by the subcontractor. N. DISASTER RECOVERY. In the event a disaster or accident beyond Customer's control impairs the operation of the System, Motorola shall use its best efforts to help Customer restore operations as quickly as possible at rates not to exceed those set forth in or calculated in accordance with those in the Service Agreement or those last paid by Customer for similar services. M070HOLA Page 16 Motorola January 9,2008 City of Fort Worth, Texas O. SECTIONS SURVIVING TERMINATION OR FINAL SYSTEM ACCEPTANCE. The terms and conditions of Sections S, 10, 11, 12, 13, 16.J shall survive the termination date of and/or date of Final System Acceptance under this Agreement. P. RIGHT TO AUDIT. Motorola agrees that Customer shall, until the expiration of three (3) years after final payment under this contract, have access to and the right to examine and photocopy any directly pertinent books, documents, papers and records of Motorola involving transactions relating to this contract. Customer may send a representative to a Motorola facility during normal business hours to conduct such limited review, or at Customer's request Motorola will provide copies of the specific documents to Customer's location for its review. Motorola books and records provided to Customer pursuant to this provision shall not be used, duplicated or disclosed to any other third party without the express written permission of Motorola, unless required by law. In no circumstances will Motorola be required to create or maintain documents not kept in the ordinary course of Motorola's business operations, nor will Motorola be required to disclose any information, including but not limited to product cost data, which it considers confidential or proprietary to Motorola. Motorola agrees that Customer shall have access during normal working hours to all necessary Motorola facilities and shall be provided adequate and appropriate workspace in order to conduct audits in compliance with the provisions of this section. Customer shall give Motorola reasonable advance notice of intended audits. (a) Motorola further agrees to include in all its subcontractor agreements hereunder a provision to the effect that the subcontractor agrees that Customer shall, until the expiration of three (3) years after final payment under the subcontract, have access to and the right to examine and photocopy any directly pertinent books, documents, papers and records of such subcontractor, subject to the provisions of Paragraph P above, involving transactions to the subcontract, and further, that Customer shall have access during normal working hours to all subcontractor facilities, and shall be provided adequate and appropriate workspace, in order to conduct audits in compliance with the provisions of this article together with subsection (3) hereof. Customer shall give subcontractor reasonable advance notice of intended audits. (b) Motorola and subcontractor agree to photocopy such documents as may be requested by the City. The City agrees to reimburse Motorola and or subcontractor for the cost of copies at the rate published in the Texas Administrative Code in effect as of the time copying is performed. A 07-off " Page Motorola January ry 9,2008 City of Fort Worth, Texas In witness whereof, the parties have caused duly authorized reIfivecute this Agreement in multiples on the dates set forth below. IN WITNESS WHEREOF.City ofFort Worth Motorola, Inc By: '�A� 1��� �'/, � y: L Name: Karen L, Montgomery Name: �ul��-�� /`GC JS Title: Assistant,City Manager/CFO Title: ASS / .� 4e,5 Date: P/ & Dater Approved as o Form and Legality; r By: Assistant City Attorney M&C: I I X;a Date Approved: a• Atte*yySecretary By: Lve EXHIBIT A SOFTWARE LICENSE AGREEMENT F OYOT RO" Page 18 Motorola January 9,2008 EXHIBIT A MOTOROLA COMMUNICATIONS SYSTEM AGREEMENT CITY OF FORT WORTH,TX LOCAL GOVERNMENT REFRESH Software License Agreement In this Exhibit A, the term "Licensor" means Motorola, Inc., ("Motorola"); "Licensee," means the Customer; "Primary Agreement" means the agreement to which this exhibit is attached; and "Agreement" means this Exhibit and the applicable terms and conditions contained in the Primary Agreement. The Parties agree as follows: Section 1 SCOPE Licensor will provide to Licensee proprietary software; or radio communications, computer, or other electronic products ("Products") containing embedded or pre-loaded proprietary software; or both. "Software" means proprietary software in object code format, and adaptations, translations, de- compilations, disassemblies, emulations, or derivative works of the software, and may contain one or more items of software owned by a third party supplier ("Third Party Software"). Product and Software documentation that specifies technical and performance features and capabilities, and the user, operation and training manuals for the Software (including all physical or electronic media upon which this information is provided) are collectively referred to as "Documentation." This Agreement contains the terms and conditions pursuant to which Licensor will license to Licensee, and Licensee may use, the Software and Documentation. Section 2 GRANT OF LICENSE Subject to Section 1, Licensor hereby grants to Licensee a personal, non-transferable (except as permitted in Section 8 below), limited, and non-exclusive license under Licensor's applicable proprietary rights to use the Software and related Documentation for the purposes for which they were designed and in accordance with the terms and conditions of this Agreement. The license does not grant any rights to source code. Section 3 LIMITATIONS ON USE 3.1. Licensee may use the Software only for Licensee's internal business purposes and only in accordance with the Documentation. Any other use of the Software is strictly prohibited. Licensee may not for any reason modify, disassemble, peel components, decompile, otherwise reverse engineer or attempt to reverse engineer, derive source code, create derivative works from, adapt, translate, merge with other software, copy, reproduce, distribute, or export any Software or permit or encourage any third party to do so, except that Licensee may make one copy of Software provided by Licensor to be used solely for archival, back-up, or disaster recovery purposes. Licensee must reproduce all copyright and trademark notices on all copies of the Software and Documentation. 3.2. Licensee may not copy onto or transfer Software installed in one Product device onto another device. Notwithstanding the preceding sentence, Licensee may temporarily transfer Software installed on one device onto another if the original device is inoperable or malfunctioning, if Licensee provides written notice to Licensor of the temporary transfer and the temporary transfer is discontinued when the original device is returned to operation. Upon Licensor's written request, Licensee must provide to Licensor a written list of all Product devices in which the Software is installed and being used by Licensee. 3.3. Concerning Motorola's Radio Service Software ("RSS"), if applicable, Licensee must purchase a copy for each location at which Licensee uses RSS. Licensee's use of RSS at an authorized location does not entitle Licensee to use or access the RSS remotely. Licensee may make one additional copy CFW SLA.Exhibit A.1.09.08.revision.doc for each computer owned or controlled by Licensee at each authorized location. Upon Licensor's written request, Licensee must provide to Licensor a written list of all locations where Licensee uses or intends to use RSS. Section 4 OWNERSHIP AND TITLE Title to all copies of Software will not pass to Licensee at any time and remains vested exclusively in the copyright owner. The copyright owner owns and retains all of its proprietary rights in any form concerning the Software and Documentation, including all rights in patents, patent applications, inventions, copyrights, trade secrets, trademarks, trade names, and other intellectual properties (including any corrections, bug fixes, enhancements, updates, or modifications to or derivative works from the Software whether made by Licensor or another party, or any improvements that result from Licensor's processes or, if applicable, providing information services). Nothing in this Agreement is intended to restrict the proprietary rights of Licensor or to grant by implication or estoppel any proprietary rights. All intellectual property developed, originated, or prepared by Licensor in connection with providing to Licensee Software, Products, Documentation, or related services remain vested exclusively in Licensor, and this Agreement does not grant to Licensee any shared development rights of intellectual property. Section 5 CONFIDENTIALITY Licensee acknowledges that the Software and Documentation contain Licensor's valuable proprietary and Confidential Information and are Licensor's trade secrets, and that the provisions in the Agreement concerning Confidential Information apply. Section 6 LIMITED WARRANTY 6.1. The commencement date and the term of the Software warranty will be as stated in the Primary Agreement, except that the Warranty Period for LiveScan software will be 90 days; and for application Software that is provided on a per unit basis, the Warranty Period for subsequent units licensed is the remainder(if any) of the initial Warranty Period or, if the initial Warranty Period has expired, the remainder (if any)of the term of the applicable Software Maintenance and Support Agreement. 6.2. During the applicable Warranty Period, Licensor warrants that the unmodified Software, when used properly and in accordance with the Documentation and this Agreement, will be free from a reproducible defect that eliminates the functionality or successful operation of a feature critical to the primary functionality or successful operation of the Software. Whether a defect occurs will be determined solely with reference to the Documentation. Licensor does not warrant that Licensee's use of the Software or Products will be uninterrupted or error-free or that the Software or the Products will meet Licensee's particular requirements. Warranty claims are described in the Primary Agreement. 6.3. LICENSOR DISCLAIMS ALL OTHER WARRANTIES, EXPRESS OR IMPLIED, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE TRANSACTION COVERED BY THIS AGREEMENT IS A LICENSE AND NOT A SALE OF GOODS. Section 7 LIMITATION OF LIABILITY The Limitation of Liability provision is described in the Primary Agreement. Section 8 TRANSFERS CFW SLA.Exhibit A.1.09.08.revision.doc Licensee will not transfer Software or the related Documentation to any third party without Licensor's prior written consent, which consent may be withheld in Licensor's reasonable discretion and which may be conditioned upon the transferee paying all applicable license fees and agreeing to be bound by this Agreement. Notwithstanding the preceding sentence, if Licensee transfers ownership of radio Products to a third party, Licensee may assign its rights to use the Software (other than Radio Service Software and Motorola's FLASHport® Software) embedded in or furnished for use with those radio Products if Licensee transfers all copies of the Software and the related Documentation to the transferee, and the transferee executes a transfer form to be provided by Licensor upon request (which form obligates the transferee to be bound by this Agreement). Section 9 TERM AND TERMINATION Licensee's right to use the Software and Documentation will begin when this Agreement is mutually executed by both parties and will continue during the life of the Products in which the Software is used, unless Licensee breaches this Agreement in which case it will be terminated immediately upon notice by Licensor. Licensee acknowledges that Licensor has made a considerable investment of resources in the development, marketing, and distribution of its proprietary Software and Documentation and that reasonable and appropriate limitations on Licensee's use of the Software and Documentation are necessary for Licensor to protect its investment, trade secrets, and valuable intellectual property rights concerning the Software and Documentation, Licensee also acknowledges that its breach of this Agreement will result in irreparable harm to Licensor for which monetary damages would be inadequate. In the event of a breach of this Agreement and in addition to termination of this Agreement, Licensor will be entitled to all available remedies at law or in equity (including immediate injunctive relief and repossession of all non-embedded Software and associated Documentation unless Licensee is a Federal agency of the United States Government). Within thirty (30) days after termination of this Agreement, Licensee must certify in writing to Licensor that all copies of the Software and Documentation have been returned to Licensor or destroyed and are no longer in use by Licensee. Section 10 NOTICES Notices are governed by Section 18 of the Primary Agreement. Section 11 UNITED STATES GOVERNMENT LICENSING PROVISIONS If Licensee is the United States Government or a United States Government agency, then this section also applies. Licensee's use, duplication or disclosure of the Software and Documentation under Licensor's copyrights or trade secret rights is subject to the restrictions set forth in subparagraphs (c)(1) and (2) of the Commercial Computer Software-Restricted Rights clause at FAR 52.227-19 (JUNE 1987), if applicable, unless they are being provided to the Department of Defense. If the Software and Documentation are being provided to the Department of Defense, Licensee's use, duplication, or disclosure of the Software and Documentation is subject to the restricted rights set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 (OCT 1988), if applicable. The Software and Documentation may or may not include a Restricted Rights notice, or other notice referring to this Agreement. The provisions of this Agreement will continue to apply, but only to the extent that they are consistent with the rights provided to the Licensee under the provisions of the FAR or DFARS mentioned above, as applicable to the particular procuring agency and procurement transaction. Section 12 GENERAL 12.1. COPYRIGHT NOTICES. The existence of a copyright notice on the Software will not be construed as an admission or presumption that public disclosure of the Software or any trade secrets associated with the Software has occurred. 12.2. COMPLIANCE WITH LAWS. Licensee will comply with all applicable laws and regulations, including export laws and regulations of the United States. Licensee will not, without the prior cr'w S LA.Exhibit A.t.09.08.revision.doc authorization of Licensor and the appropriate governmental authority of the United States, in any form export or re-export, sell or resell, ship or reship, or divert, through direct or indirect means, any item or technical data or direct or indirect products sold or otherwise furnished to any person within any territory for which the United States Government or any of its agencies, at the time of the action, requires an export license or other governmental approval. Violation of this provision will be a material breach of this Agreement, permitting immediate termination by Licensor. 12.3. ASSIGNMENTS. Assignment rights are governed by Section 18 of the Primary Agreement. 12.4. GOVERNING LAW 1 VENUE. This Agreement will be governed by the laws of the state of Texas and the laws of the United States to the extent that they apply. Venue for any action arising under or related to the terms and conditions of this Agreement shall lie in the state courts located in Tarrant County, Texas or in the United States District Court for the Northern District of Texas, Fort Worth Division. CFW SLA.Exhibit A.1.09.08.revision.doc City of Fort Worth, Texas EXHIBIT IS PAYMENT TERMS 50% UPON CONTRACT EXECUTION ($171,987.50) 25% UPON EQUIPMENT SHIPMENT AND INSTALLATION ($85,993.75) 25% UPON PROJECT ACCEPTANCE ($85,993.75) aft M 77'OROL A Page 21 Motorola Confidential Proprietary November14 2006 'o vZ rn m �o o in as rn o 0 0 0 o Rn W5 tnY o Cr � � m m N a, n � aov� M17NNvotnONooltNON n o 4D o Cal u a m t ar ,� ,-+ ,--, N o+ t ,-- Cr „ JCL 'n �N o0 M1 cr ,-� �""" N a;,--� M tn CV n N N M M 'A C C kn an � to . H3 b9 CPI 59 69 s9 5e 69 69 6R iff 6R 454 bS 6A 4r4 6R 59 56 &9 69 &4 &4 rR b9 69 59 b9 5r3 ti0 xn CT m %o o in 'Ir ON in o ON o �o in in 4) d� n do 00 PLI � o sHs*3vSctssyssa61IJbsbssFrsFrfAssbscA F» En w 2 U O U A m v W O W O � � x o o oP.' o ° ' 0 (A � 0 a p�, •� U WW , > U , A pWP-1Poz U o � H O � U W W o A U A U U , ao H 4raUx a w ❑❑❑ U � rn ,A� � u, AV U A A A A Q Q A o a o E" rmo It—no p .-- C7 t+gjv�s 00 N d W+ ON1 M M n 0 a M M ef' (*1 �--� CY A r-I 0 CO) AaAAA A*Crr MOLA intelligence everywhere' CITY OF FORT WORTHS TEXAS LOCAL GOVERNMENT RADIO SYSTEM EQUIPMENT REFRESH TECHNICAL DOCUMENTATION Motorola Western Division Systems Integration REVISION HISTORY: 08-13-07 1 gvs Initial Release. 08-14-07 2 ma Minor chap es to task overview.Remove Iink verification testing. 09-20-07 3 9yS Correct grammatical errors. 10-19-07 4 9vS Revisions to add Cornet Switch for cutover. 10-21-07 5 fna/gvs Corrections File:CFW LG Refresh Engineering Document Rev 5 102107 City of Fort Worth Page Left Blank Intentionally City of Fort Worth CITY OF FORT WORTH, TEXAS LOCAL GOVERNMENT RADIO SYSTEM EQUIPMENT REFRESH Table of Contents SystemDescription............................................................................................................ I ProjectOverview............................................................................................................. 1 ProposedEquipment....................................................................................................... 1 EquipmentRemoval........................................................................................................ 1 Grounding ...................................................................................................................... 1 RoofPenetrations............................................................................................................ 1 Antenna Network RepIacement...................................................................................... 1 Antenna Mounting Locations.......................................................................................... 1 ACPower Requirements................................................................................................. 2 CornetSwitch..................................................................................................................2 SpaceRequirements........................................................................................................ 2 FunctionalTesting. ......................................................................................................... 2 CoverageTesting ........................................................................................................... 3 TaskOverview................................................................................................................ 3 Step 1: Replace Antenna Network.............................................................................. 3 Step 2: Install and cutover FNE equipment ................................................................3 Local Government System Block Diagram - Revised .................................................... 5 Local Government System Proposed Rack Layout - Revised......................................... 5 Local Government System Proposed Rack Layout - Revised......................................... 6 Local Government System Proposed Rack Face Diagram - Revised ............................. 7 Burnett Plaza Site Existing Fort Worth Antenna Locations - Revised........................... S Local Government System Transmit Antenna Network................................................. 9 Local Government System Receive Antenna Network................................................. 10 EquipmentList................................................................................................................ 11 Statementof Work....................................................................:..................................... 13 Contract......................................................................................................................... 13 Contract Award (Milestone) ..................................................................................... 13 ContractAdministration............................................................................................ 13 ProjectKickoff.......................................................................................................... 13 Contract Design Review(CDR). .................................................................................. 14 ReviewContract Design ........................................................................................... 14 Design Approval (Milestone).................................................................................... 15 Page i City of Fort Worth OrderProcessing.............................:............................................................................. 15 ProcessEquipment list.............................................................................................. 15 Manufacturing and Staging........................................................................................... 15 Manufacture Motorola Fixed Network Equipment................................................... 16 Manufacture Non-Motorola Equipment.................................................................... 16 ShipEquipment to Field ........................................................................................... 16 Ship Acceptance (Milestone).................................................................................... 16 Civil Work for The Customer Provided Facilities........................................................ 16 SystemInstallation........................................................................................................ 18 Install Fixed Network Equipment............................................................................. 18 Fixed Network Equipment Installation Complete..................................................... 18 System Installation Acceptance (Milestone)............................................................. 18 SystemOptimization..................................................................................................... 19 OptimizeSystem FNE............................................................................................... 19 Optimization Complete............................................................................................. 19 Training......................................................................................................................... 19 PerformTraining. ..................................................................................................... 19 TrainingComplete .................................................................................................... 19 Audit and Acceptance Testing...................................................................................... 20 PerformR-56 Audit................................................................................................... 20 PerformEquipment Testing...................................................................................... 20 PerformFunctional Testing. ..................................................................................... 20 PerformCoverage Testing .......................................................................................21 System Acceptance Test Procedures (Milestone)..................................................... 21 Finalize.......................................................................................................................... 21 SystemCutover......................................................................................................... 21 ResolvePunchlist...................................................................................................... 22 Transition to Service/Project Transition Certificate ................................................. 22 FinalizeDocumentation............................................................................................ 22 Final Acceptance (Milestone) .................................................................................. 23 ProjectAdministration.................................................................................................. 23 ProjectStatus Meetings............................................................................................. 23 Progress Milestone Submittal ................................................................................... 23 ChangeOrder Process............................................................................................... 24 FunctionalAcceptance Test Plan...................................................................................25 Overview...................................................................................................................25 Acceptance Test Procedures...................................................................................... 25 TestObjective ........................................................................................................... 25 Methodology............................................................................................................. 25 QuantarHardware Testing........................................................................................ 25 Sample Quantar Datasheet........................................................................................ 26 TalkgroupCall .......................................................................................................... 28 BusyQueuing and Call Back.................................................................................... 29 Emergency Alarm and Call -Tactical...................................................................... 30 Page H City of Fort Worth Continuous Assignment Updating ........................................................................... 31 Transmitter Power Shutdown.................................................................................... 33 Receiver Interference Shutdown............................................................................... 34 Console to MTC 3600 Link Failure.......................................................................... 35 Base Station Identification........................................................................................ 36 StationFailure........................................................................................................... 37 StationPower Failure................................................................................................ 38 FailsoftOperation......................................................................................................39 ConsoleTalkgroup Call............................................................................................41 ConsolePriority ........................................................................................................ 42 EmergencyAlarm and Call....................................................................................... 43 PTTID/Alias Display.............................................................................................. 44 Functional Test Signoff Certificate............................................................................... 45 Coverageacceptance test plan....................................................................................... 46 Overview.......................................................................................................................46 CATPDefinitions .........................................................................................................46 CoverageArea:.......................................................................................................... 46 Channel Performance Criterion(CPC): .................................................................... 46 Reliability:................................................................................................................. 47 Equipment Configurations: ....................................................................................... 47 In-Building Coverage:...............................................................................................47 CATPMethod...............................................................................................................47 Determine the required number of test tiles in the coverage area:............................48 Constraints on test tile sizes...................................................................................... 48 Accessibility to test tiles............................................................................................ 48 Randomly Select A Test Location Within Each Tile:............................................... 48 Perform Measurements In Each Tile:........................................................................ 48 Determine If Each Tile Passes Or Fails The CPC Requirement............................... 48 Determine The Coverage Area Reliability For Acceptance:..................................... 48 Responsibilities and Preparation...................................................................................49 CATPProcedures.......................................................................................................... 49 CATP Documentation and Coverage Acceptance........................................................ 50 SystemAcceptance Certificate....................................................................................... 52 Page iii City of Fort Worth Local Government Equipment Refresh System Description Project Overview • Two(2)Receive multicoupler input filters. The purpose of this project is to implement an • One(1)set controller spares consisting of each equipment refresh of the Local Government Single module and power supply. Site Trunked System.This will consist of replacing all fixed network equipment and antenna systems with the exception of the transmit combiners. IT Electronics Shop • Two(2)Spare Quantar repeaters. Proposed Equipment Equipment Removal The equipment supplied and installed for this project will consist of the following: The decommissioned equipment will be removed from the site and transported to a location specified Burnett Plaza by the City. • Twenty(20)Quantar trunked repeaters to be Grounding installed as replacements for the existing MSF5000 stations. All equipment and racks supplied for this project will be connected to the existing ground network at • One(1)Cornet Switch to facilitate cutover from Burnett Plaza. the old controller to the new MTC controller_ • One(1)Tone control panel for future remote Roof Penetrations switching capability.Panel will be installed but not operational.The City will be responsible for In order to facilitate installation and cutover of the implementing this feature if desired. antenna network,2 additional roof penetrations with conduit and weatherhead will be required.New main • One(1)MTC3600 single site controller with feed lines will have to be pulled into place before the redundant power supply to be installed as a existing lines can be removed.The City will be replacement for the existing 6809 controller. responsible for contracting with the building owners • One(1) 10 dB omni antenna,feed line, and to get the penetrations installed.These should be of associated parts to replace the receive antenna on equal size and in the same location as the existing the Local Government system. penetrations. • One(1)tower top preamp and receive Antenna Network Replacement multicoupler to replace the existing equipment on the Local Government system. As part of this project,the existing Local Government • One(1) 10 dB omni antenna,feed line,and antenna network is being replaced.This includes associated parts to add a second receive antenna antennas,main lines,jumpers,connectors,and on the Local Government system.Receivers will multicoupler.The transmit combiners are not being be distributed between the 2 antennas. replaced at this time. In addition,the receive network will be split among 2 antennas and multicouplers.The • One(1)tower top preamp and receive odd channels will be on one and the even channels on multicoupler for the corresponding additional the other. receive antenna on the Local Government system. Receivers will be distributed between the Antenna Mounting Locations 2 multicouplers. • Five(5) 10 dB omni antennas,feed lines, and The existing masts are Celwave dual units with 2 associated parts to replace the existing transmit antennas. Since these are no Ionger manufactured, antennas on the Local Government system. twice as many antenna mounts will be required.The existing 3 masts will be removed and those spots re- • Five(5)Transmit combiner input filters. used.However without taking the system down,4 Page 1 City of Fort Worth Local Government System Equipment Refresh additional spots will be required for new antennas so Note: The Cornet Switch consists of 2 chassis in a painless cutover can be accomplished.A total of 7 order to accommodate the required number of switch antenna locations will be required for this equipment cards.Each chassis contains a main and redundant refresh.The City will be responsible for obtaining power supply.It is recommended that each power these additional mounting locations. supply be on a separate circuit.In order to accommodate the additional circuits in rack.1, two AC surge panels will be installed, one on each side of AC Power Requirements the header bar. In order to facilitate the cutover of this equipment refresh, a total of 29 new 20 amp AC circuits will be Cornet Switch required.The existing circuits are not in the correct physical locations where the new equipment will be A dual chassis Cornet Switch will be installed to installed.The new circuits must be terminated in the facilitate the cutover from the old 6809 based rack mounted surge panel provided as part of this controller to the new MTC controller.This will project.The City will be responsible for contracting reduce the switchover time to just a few seconds. with the building owners to provide the necessary AC Initially the system would have been reduced in circuits. Refer to the following table and the rack capacity by 10 channels.The switch will enable the face diagram for circuit Iocations. cutover to occur within a few seconds with no reduction in capacity.On-going calls will be dropped Rack No.of 20 and the consoles will lose connection for a few No. I Equipment Amp Ckts seconds until the TIMI links re-synchronize. In addition,a tone control panel will be physically Repeater 1 1 installed but not made operational.This will allow for Repeater 2 1 remote switching between controllers.The City will Repeater 3 1 be responsible for implementing this capability in the future.Base interface modules will be required at 3 Repeater 4 1 each dispatch center to generate the control tones Repeater 5 1 ' along with audio circuits to Burnett Plaza.Alternately Repeater 6 1 a control tone generator could be placed at the IT Repeater 7 1 Electronics Shop for remote control of the switch. Re eater 8 1 Repeater 9 1 Space Requirements Repeater 10 1 Three rack spaces will be required at Burnett Plaza Repeater 11 1 for the proposed equipment. 2 Repeater 12 1 In order to facilitate installation and cutover of the Repeater 13 1 proposed equipment, the existing MSF stations will Repeater 14 1 be moved to temporary locations.The new equipment Repeater 15 1 racks wiII be installed in the space vacated by the Re. eater 16 1 MSF stations.The MSF stations will be removed and transported to a Iocation specified by the City.Refer Repeater 17 1 to the floor plan and rack face diagrams for details. Repeater 18 1 Repeater 19 1 Functional Testing Repeater 20 1 A functional test plan is included later in this 1 Cornet Switch 4(See Note) document. Some of the tests will be performed on the Tone Panel 1 MTC controller while operating with a limited set of Controller* 2 channels on dummy loads.Tests such as failsoft MuIticoupler A 1 operation will interfere with normal operations and Multicou ler B 1 will not be performed on a Iive system unless the City deems it permissible.The final test plan and procedures will be mutually agreed to during design Total 29 review meetings. * -Redundant power supply should be on separate circuit Page 2 City of Fort Worth Local Government System Equipment Refresh k) Install and test new antenna and line in final spot Coverage Testing vacated. At the completion of the installation and cutover,a 1) Remove old multicoupler. coverage test will be performed.This will be an m) Install new multicoupler(B)and connect to new automated signal strength measurement drive test antenna. only. Since this is a single site system and simulcast n) Move 10 channels(odd or even)one at a time interference will not be present,a subjective audio from multicoupler A to multicoupler B. One test has not been included.The purpose of the test is channel at a time out of service while cable is to verify the accuracy of the coverage prediction map moved. and not check every location within the service area. Step 2:Install and cutover FNE equipment For this proposal,the test area will consist of no more than 1700 tiles no smaller than 1/z mile square.The a} City to contract with building owners to provide pass/fail signal strength criterion will be-103 dBm 29 additional 20 amp AC circuits as indicated on adjusted for mobile antenna performance. If the City rack layout drawing. Circuits to be ready to desires a more stringent coverage test, then additional terminate in rack mounted surge panel as soon as costs may be incurred through a change order racks are installed. process. b) Install temporary RF,audio,and control cables to specified location. Task Overview c) Move MSF stations for channels 3,4,5,and 6 to temporary location one at a time. System This provides a very high level view of the capacity down by 1 channel at a time during this implementation and cutover of this equipment.A process. detailed implementation and cutover plan will be d) Install rack#3 containing Quantar channels 1—8 developed and reviewed during technical design and a rack mounted 8 circuit surge panel in space meetings. vacated by MSF stations. e) Electrician to terminate 8 AC circuits in rack Step 1:Replace Antenna Network. mount surge panel. a) City to install 2 new roof penetrations with f) Power up Quantar stations I—8,program for conduit and weatherhead. appropriate frequency and system parameters, b} City to obtain and specify 4 additional antenna and perform station diagnostics, testing,and optimization.mounting locations. g) Install RF,audio,and control cabling to Quantar c} Install and test 4 new antennas and lines using rack#3 for channels 1—8. the 4 new mounting locations and 2 new roof h) Disable MSF channel 1 and disconnect from penetrations. system. d) Move 4 of the existing TX combiners to new i) Connect and power up Quantar channel 1 and antennas.Temporary loss of 4 channels while enable on system. combiner is disconnected and reconnected to j) Repeat steps h and j for channels 2—8. new line.e) Remove the 2 old antenna masts and associated k) Remove MSF stations 1—8 from equipment R)~coax lines that have just been taken out of room 1) Move MSF stations for channels 9 and 10 to service. temporary location one at a time.System f) Install and test 2 new antennas and lines in the capacity down by 1 channel at a time during this spots vacated by the old antenna masts.Use process. space in old roof penetration vacated by line m) Install rack#2 containing Quantar channels 9— removal. 16 and a rack mounted 8 circuit surge panel in g) Move the remaining TX combiner to one of the space vacated by MSF stations. new antennas.Temporary loss of 4 channels n) Electrician to terminate 8 AC circuits in rack while combiner is disconnected and reconnected mount surge panel. to new line. o) Power up Quantar stations 9—16,program for h) Install one of the new multicouplers(A)and appropriate frequency and system parameters, connect to one of the new antennas. and perform station diagnostics, testing and i) Move all channels from old multicoupler one at a optimization. time to the new multicoupler A, (Multicoupler p) Install RF,audio,and control cabling to Quantar has 24 ports) One channel at a time out of rack#2 for channels 9—16. service while cable is moved. q) Disable MSF channel 9 and disconnect from j) Remove last old antenna mast and associated RF system. lines. Page 3 City of Fort Worth Local Government System Equipment Refresh r) Connect and power up Quantar channel 9 and cc) Remove Quantar channels from MTC.controller enable on system. and place controller in idle mode. s) Repeat steps q and r for channels 10—16. dd) Reprogram temporary Channel 1 Quantar back to t) Remove MSF stations 9—16 from equipment Channel 17-perform diagnostics,testing and room optimization. u) Install rack#1 containing Quantar channels 17— ee) Install RF,audio,and control cabling to Quantar 20,the system controller,a dual chassis Cornet rack#2 for channels 17—20. Switch, a tone panel, and 2 rack mounted 8 ff) Disable MSF channel 17 and disconnect from circuit surge panels in space vacated by MSF system. stations. gg) Connect and power up Quantar channel 17 and v) Electrician to terminate 13 AC circuits in rack enable on system_ mount surge panel. hh) Repeat steps ee and ff for channels 18 20. w) Power up MTC controller and perform ii) Remove MSF stations 17—20 from equipment diagnostics as required. room x) Power up Cornet Switch and perform diagnostics J) InstalI control cabling from Quantar repeaters and functional testing as required. and MTC controller to Cornet Switch. y) Power up Quantar stations 18—20,program for kk) Install control cables from 6809 controller to appropriate frequency and system parameters, Cornet Switch. and perform station diagnostics,testing,and 11) Install cabling for TIMI links to pass through optimization. Cornet Switch. z) Power up Quantar station 17 and program mm) Place Cornet Switch in"6809"position. temporarily to Channel 1 control channel nn) Disconnect each repeater and reconnect one frequency. at a time to 6809 controller through Cornet aa) Connect Quantar repeaters for temporary Switch. Channel 1 and channels 18 20 to MTC oo) Activate MTC 3600 controller and manually controller and install dummy loads on antenna switch repeaters via the Cornet Switch.All ports. subscribers should automatically switch to the bb) Perform basic trunking functionality tests on new controller immediately. MTC controller to confirm proper operation. Page 4 — 'k:7 ,! g | - 2 ^ ! - & § _ / � E! - / Q voSf " & | LL a % R ` / \ § & § Co j ) } / (9 2 ° ( b 7 \ _tea � § w w / - /> � 2 > )f r _a k o d ■ \ & I YJ 3 2 k �� 2 � k k 7 % a � Fin m £ r � $ kk k � t � _ E § � \ § � o 4 . . . - / - 7 q £ # A � a E W ) � k � \ k \_ ■ u � m A | 5EC § \ k�§ / ID 0 W �2 � ; § § 7q - k![ �2§; �#if , � co . i I w }k( ® I ira © )!« f 2 | % P-4 LOLO k§« ® \k ® c 2 | ' ) J Co / 2 ) ƒ f k ~ / 2 \� ƒ �)w ¢ � FM- £ § . 2 ƒ . § � k k � o C � $ : m U) Q m W E i O LL CD E E LL O E p .� � rno ra c� CD T U m r J rn ts C? O O — T-E �a 4^ (1) Ln a M NE n Z Z Z Z a Z Z ` Z a 8 m' a ay a aY a � a a IDa m ay aY 0i � F- a�+ F- d) � w � w � (D C_ m dCL do du Qa C3a- t'JCL C'JQ da tO Er tot Ix It a w + a, co O — — — a) � w {O N N m C'7 0) N N r aIts S? d J Q r E r ` r E r E r E r E E mu Z Z = Z 3 Z Z = Z Z = Q ° L O1 0 N m a ° a `° a°° a m a m a°° a `° =m t 42 and o Y � 1 =m' = coC3 = urC7 � d'U' m "o ScmC7 Ua U �� U —J U ccrn a S .- cc S .. S . S S .. ora DC !' m Ev= 3 Qo am aami ad aa) a � do�G i m O � pm Qa�i � m � m � m (�+f a�i ~dC. m m Y U CC CC It CC Cc Cc - Cc a rnm o a _v QE OD m w E m mtJ c�iwQ tl N m C N AN C C C T C to v a mw �m N w ° Qm ¢°`�° Qm Qm O UU a _- � Zug w� C to r m Z = oC7 ZmC7 zmC7 Snc� i to my !!aa o� U U U �VJ U�J U u J U `J (IS Q m rN m Qo 3 ° (3@ Fa CD O¢ d¢ d ac d rr � O w+ v x a y - r. tv Im ?� 64 ca ro 4-1 U - ' t L � f �4 � l7 N Q o �. 44 m ro _ ro C E3 C C 9 Ir =� O F � m c ,p3 ro � ©:¢ a O 1p E 0o `-' v t� 0 to z O kR)z N La X a WII M U LOoQ �omA J�> a t405ram+ CIN R��� coIM z r MI-1 �c N NIQ', Nf4 NNI NIQ NIQ 1.. -. ..: am ATI I AT7fil IL IN AT Si � dQ:L'] 2 TI + .7 rl C �3 Q it R �P � p¢ 3a aWaa a �� LalnhlrtNl Golal�l_IR-2 �onGlner] � Ca-al.iclR i:olr-rll�k��� 12 ry - I � W � (OP) TT nuxa u F,. iva Rt n CChannels 1,6,11,1B chalinels 2,7,12,17 Chan nels-3.8,13,18 Channels 4,9,14,19 BhanneISL5,16,15,2a ® I� � O a.a C� o� W 9 L E. N LL d ❑ ry W a LL^ E Z a d ® U0< dos 08 ai � � f+t. 1 FBL7 0 UPL c�Z Q n 20 C O OI N US`il ID a ti u a W1 �. 0°°u � a � •141 � o 0 ON ova wo .Lu CD N U 9 ro QA A _ A i Af C7 d R�kL04 R s. Q��'{ mg ...pppI s=` fy6��`+� R a O ua J J ?• [[[TTT p���c. C Z 0. pp a o U N yF 100 40 N, co vLUC LL all �Q F0. wctc PLw CReceiver Mkilticbupler 7 Receiver Multicaupler 2 PLLG PIIw P A!IG TT:TTITT IL �. F M TA4 . I LUG nU UG PLC vwU UG PLC viUU UG 7TTT- PLu vLUG •� �f''i � ti �! � ,eF!• r1R* r � N � W G7 C> c> v aL m ai ax m d a m m to 0 m m m IG m IV U U U- s e t r m rd m m m 0 r s S o C? U U V U .V ,U U� U Cl C� � . 0 slauuego pajagwnN ppp slauue40 paaagmnN uan3 d O m � O .y Ca City of Fort Worth Local Government System Equipment Refresh Equipment List QTV N mrNc_L4TuRI+ _ 1)G C:lt1 l-ION 4 TRN7343 SEVEN AND A HALF FOOT RACK 22 TTN5028A HDW RACKMNT QUANTAR STDALONE 4 DSOP820B POWER DIST.UNIT SURGE PROTECT 1 SQMOISUM0070 MTC 3600 STANDALONE SINGLE SITE CONTROLLER 1 D392AQ ADD: 14 CHANNELS 21 CH CTY 1 D389AK ADD:REDUNT CNTLR INTERFACE 1 D431AJ ADD: CONSOLE INTERFACE I D313AG ADD:CONSOLE INTERFACE SPARES 1 D179CF ADD:MTC 3600 SINGLE SITE SPARES 1 D275AK ADD:REDUNDANT 110/220 VAC POWER SUPPLY 1 D396AH ADD:OPERATIONS/SERVICE MANUAL 1 L3174 3810 PLUS MODEM S/A V.34 PROTOCOL 2 TRN7663A ENTERPRIZE AC LINE CORD 1 DSZlZI118567 RM001 WITH SPECIAL FACEPLATE 2 L3174 3810 PLUS MODEM S/A V.34 PROTOCOL 20 T5365 QUANTAR/QUANTRO FAMILY MODEL 20 X750 ADD:800 MHZ BAND RX 806-825 MHZ/TX 851-870 MHZ, 100-20 WATTS 20 X997 A ENH:QUANTAR 6809 TRUNKING OPERATION 20 X87 DEL: CABINET 20 X432 ADD.MANUAL,SERVICE 20 U752 ADD:POWER CORD, 12 FT AC, QTAR 20 C115 ADD:CONSOLE PRIORITY INTERFACE 20 X337 ADD: CABLE TRUNKING 50' 2 T5365 QUANTAR/QUANTRO FAMILY MODEL 2 X750 ADD:800 MHZ BAND RX 806-825 MHZ/TX 851-870 MHZ, 100-20 WATTS 2 X997 A ENH: QUANTAR 6809 TRUNKING OPERATION 2 X87 DEL: CABINET 2 X432 ADD: MANUAL,SERVICE 2 U752 ADD:POWER CORD, 12 FT AC, QTAR 2 C115 ADD:CONSOLE PRIORITY INTERFACE 1 DSTTAS80028224 TTA W/RMC COMBINATION 1 DSRMC80OPF05 OPTIONAL 5 MHZ FILTER KIT FOR RMC TRAY 2 DSISDCSOLNZ30MA DC INJECTOR 30V Surge Suppressor 1 DSPD100171 ANTENNA BASE OMNI DIRECTIONAL 800-836 MHZ 1 DSTTAS80028224 TTA W/RMC COMBINATION 1 DSRMC80OPF05 OPTIONAL 5 MHZ FILTER KIT FOR RMC TRAY 2 DSISDC50LNZ30MA DC INJECTOR 30V Surge Suppressor 1 DSPD100171 OMNI ANTENNA, 10DBD,800-836 MHZ,BW=35MHZ,N-F,50OW 1 DSPD504482 FILTER BAND PASS 806-88OMHZ CWA,5 MHZ 1 DSPD100171 OMNI ANTENNA, 10DBD,800-836 MHZ,BW=35MHZ,N-F,50OW Page 11 City of Fort Worth Local Government System Equipment Refresh TY EwI=Oc.LAT[ E Dp;� RllrI'ON 1 DSDSXLDMA LIGHTNING ARRESTOR,7-16DIN MALE/FEMALE,50OW 1 DSPD504482 FILTER BAND PASS 806-88OMHZ CWA,5 MHZ 1 DSPD100171 OMNI ANTENNA, 1ODBD,800-836 MHZ,BW=35MHZ,N-F,50OW 1 DSDSXLDMA LIGHTNING ARRESTOR,7-16DIN MALE/FEMALE,50OW 1 DSPD504482 FILTER BAND PASS 806-88OMHZ CWA,5 MHZ 1 DSPD100171 OMNI ANTENNA, IODBD,800-836 MHZ,BW=35MHZ,N-F,50OW 1 DSDSXLDMA LIGHTNING ARRESTOR,7-16DIN MALE/FEMALE,500W 1 DSPD504482 FILTER BAND PASS 806-88OMHZ CWA,5 MHZ 1 DSPD100171 OMNI ANTENNA, 10DBD,800-836 MHZ,BW=35MHZ,N-F,50OW 1 DSDSXLDMA LIGHTNING ARRESTOR,7-16DIN MALE/FEMALE,50OW 1 DSPDS04482 FILTER BAND PASS 806-88OMHZ CWA,5 MHZ 1 DSPD100171 OMNI ANTENNA, lODBD,800-836 MHZ,BW=35MHZ,N-F,50OW I DSDSXLDMA LIGHTNING ARRESTOR,7-16DIN MALE/FEMALE,50OW Cornet Switch _ 4TY HOMENCC ATURE J)ESCRIPTION 'U i -- — 2 DSIPS32CC IPS 32 SWITCH CHASSIS 1 DUAL POWER SUPPLY/CONTROLLER 10 DSIPS32BP1 BLANK PANEL- COVERS 1 OPEN SLOT-CAN BE USED WITH 16/32 2 DSDUALRJ45 IPS A/B DUAL RJ 45 CARD - NO BUS 20 DS24CIRCDB25 IPS A/B CARD - DB25 24 LEAD SWITCHING - NO BUS 1 CLN1195 SWITCH FOR REDUNDANT TRNK CONTROL Page 12 City of Fort Worth Local Government System Equipment Refresh Statement of Work Contract Contract Award(Milestone) ♦ The Customer and Motorola execute the contract and both parties receive all the necessary documentation. Contract Administration Motorola Responsibilities: ♦ Assign a Project Manager,as the single point of contact with authority to make project decisions. ♦ Assign-resources necessary for project implementation. ♦ Set up the project in the Motorola information system. ® Schedule the project kick-off meeting with the Customer. Customer Responsibilities: ♦ Assign a Project Manager,as the single point of contact responsible for Customer signed approvals. ♦ Assign other resources necessary to ensure completion of project tasks for which the Customer is responsible. Completion Criteria: o Motorola internal processes are set up for project management. o Both Motorola and the Customer assign all required resources. ♦ Project kickoff meeting is scheduled. Project Kickoff Motorola Responsibilities: ♦ Conduct a project kickoff meeting during the Contract Design Review(CDR)phase of the project. ♦ Ensure key project team participants attend the meeting. ♦ Introduce all project participants attending the meeting. ♦ Review the roles of the project participants to identify communication flows and decision- making authority between project participants. ♦ Review the overall project scope and objectives with the Customer. ♦ Review the resource and scheduling requirements with the Customer. ♦ Review the Project Schedule with the Customer to address upcoming milestones and/or events. ♦ Review the teams' interactions(Motorola and the Customer),meetings,reports,milestone acceptance,and the Customer's participation in particular phases. Page 13 City of Fort Worth Local Government System Equipment Refresh Customer Responsibilities: ♦ The Customer's key project team participants attend the meeting. ♦ Review Motorola and Customer responsibilities. Completion Criteria: o Project kick-off meeting completed. 0 Meeting notes identify the next action items. Contract Design Review(CDR) Review Contract Design Motorola Responsibilities: ♦ Meet with the Customer project team. ♦ Review the operational requirements and the impact of those requirements on various equipment configurations. ♦ Establish a defined baseline for the system design and identify any special product requirements and their impact on system implementation. ♦ Review the System Design,Statement of Work,Project Schedule, and Acceptance Test Plans, and update the contract documents accordingly. ♦ Discuss the proposed Cutover Plan and methods to document a detailed procedure. ♦ Submit design documents to tho Customer for approval.These documents form the basis of the system,which Motorola will manufacture,assemble,stage,and install. ♦ Establish demarcation point(SUPPLIED BY THE MOTOROLA SYSTEM ENGINEER)to define the connection point between the Motorola-supplied equipment and the Customer- supplied link(s)and external interfaces. ♦ Work with the Customer to identify radio interference between the new communication system and other existing radio systems. Restrictions: • Motorola assumes no liability or responsibility for inadequate frequency availability or frequency licensing issues. • Motorola is not responsible for issues outside.of its immiat ede control. Such issues include,but are not restricted to,improper'frequency coordination by others and non- compliant operation of other radios. • Motorola is not responsible for co-channel interference due to errors in frequency coordination by APCO or any other unlisted frequencies,or the improper design,installation,or'operation of systems installed or operated by others. • If,for any reason, any of the proposed sites cannot be utilized.due to reasons beyond Motorola's control,the costs associated with site changes delays including,but not limited to,re-engineering,frequency re-licensing,site zonor ing,site permitting,schedule delays,site abnormalities,re-mobilization,etc.,will be paid for by the Customer and documented'through the change order process. Customer Responsibilities: ♦ The Customer's key project team participants attend the meeting. ♦ Make timely decisions,according to the Project Schedule. ♦ Frequency Licensing and Interference: Page 14 City of Fort Worth Local Government System Equipment Refresh • As mandated by FCC,the Customer,as the licensee,has the ultimate responsibility for providing all required radio licensing or licensing modifications for the system prior to system staging. This responsibility includes paying for FCC licensing and frequency coordination fees. Completion Criteria: ♦ Complete Design Documentation,which may include updated System Description,Equipment List,system drawings,or other documents applicable to the project. ♦ Incorporate any deviations from the proposed system into the contract documents accordingly. ♦ The system design is"frozen,"in preparation for subsequent project phases such as Order Processing and Manufacturing. ♦ A Change Order is executed in accordance with all material changes resulting from the Design Review to the contract. Design Approval(Milestone) ♦ The Customer executes a Design Approval milestone document. Order Processing Process Equipment list Motorola Responsibilities. ® Validate Equipment List by checking for valid model numbers,versions,compatible options to main equipment,and delivery data. ♦ Enter order into Motorola's Customer Order Fulfillment(COF)system. ♦ Create Ship Views,to confirm with the Customer the secure storage location(s)to which the equipment will ship. Ship Views are the mailing labels that carry complete equipment shipping information,which direct the timing,method of shipment,and ship path for ultimate destination receipt. ♦ Create equipment orders. ♦ Reconcile the equipment list(s)to the Contract. ♦ Procure third-party equipment if applicable. Customer Responsibilities: ♦ Approve shipping location(s). ♦ Complete and provide Tax Certificate information verifying tax status of shipping location. Completion Criteria: ♦ Verify that the Equipment List contains the correct model numbers,version,options,and delivery data. ♦ Trial validation completed. ♦ Bridge the equipment order to the manufacturing facility. Manufacturing and Staging Manufacture Motorola Fixed Network Equipment Motorola Responsibilities: Page 1S City of Fort Worth Local Government System Equipment Refresh o Manufacture the Fixed Network Equipment(FNE)necessary for the system based on equipment order. Customer Responsibilities: o None. Completion Criteria: ® FNE shipped to the field. Manufacture Non Motorola Equipment Motorola Responsibilities: o Manufacture(third party equipment suppliers)non-Motorola equipment necessary for the system based on equipment order. Customer Responsibilities: o None. Completion Criteria: ♦ Ship non-Motorola manufactured equipment to the field and/or the staging facility. Ship Equipment to Field Motorola Responsibilities: o Pack system for shipment to final destination. o Arrange for shipment to the field. Customer Responsibilities: ♦ None. Completion Criteria: o Equipment ready for shipment to the field. Ship Acceptance(Milestone) o All equipment shipped to the field. Civil Work for The Customer Provided Facilities Motorola Responsibilities. o Provide electrical requirements for each equipment rack to be installed in the Customer- provided facilities. Provide heat load for each equipment rack to be installed in the Customer provided facilities. Page 16 City of Fort Worth Local Government System Equipment Refresh Customer Responsibilities: ® Secure site lease/ownership,zoning,permits,regulatory approvals, easements,power,and Telco connections. ♦ Provide clear and stable access to the sites for 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. ♦ Supply adequately sized electrical service,backup power(UPS,generator,batteries,etc.) including the installation of conduit,circuit breakers,outlets,etc., at each equipment location. Provide AC power(dedicated 20 Amp AC circuits)for each major piece of equipment terminated in the rack mounted surge panels as specified in the System Description,including the associated electrical service and wiring(conduit,circuit breakers,etc.). Motorola is requesting 29 new AC circuits at locations specified in the System Description to facilitate installation and cutover. ♦ Provide adequate HVAC,grounding,lighting,cable routing,and surge protection(also, among existing and Motorola-provided equipment)based upon Motorola's R-56 Standards and Guidelines for Communication Sites. Ceiling(minimum 9 feet)and cable tray heights (minimum 8 feet)in the equipment rooms in order to accommodate 7-foot, 6-inch equipment racks. ♦ Provide floor space and desk space for the System equipment at the Customer-provided facilities. Each rack shall be provided a minimum of 24-inch x 24-inch footprint with 36 inches clearance in the front and back. ♦ Relocate existing equipment,if needed,to provide required space for the installation of Motorola-supplied equipment. ♦ Bring grounding system up to Motorola's R-S6 Standards and Guidelines for Communication Sites and supply a single point system ground,of 5 ohms or less, to be used on all FNE supplied under the Contract. Supply grounding tic point within 10 feet from the Motorola- supplied equipment. ♦ Provide all necessary wall or roof penetrations on existing buildings for antenna coax and microwave waveguide(if applicable)for main transmitter antennas,microwave radios,and control station Yagi antennas.Motorola is requesting 2 additional roof penetrations to facilitate installation and cutover of the antenna network. ♦ Provide obstruction-free area for the cable run between the demarcation point and the communications equipment. ♦ Resolve any environmental issues including,but not limited to, asbestos,structural integrity (rooftop,water tank,tower,etc.)of the site,and any other building risks. (Resolve environmental or hazardous material issues). ♦ Arrange for space on the building for installation of new antennas at the proposed heights. Motorola is requesting 4 additional antenna locations. ♦ Perform structural analysis of existing rooftop as required to confirm that the structure is capable of supporting proposed and future antenna loads. ♦ Supply all permits as contractually required. ♦ Supply interior building cable trays,raceways,conduits,and wire supports. ♦ Supply engineering and drafting as required for modifications to existing building drawings for site construction. ♦ Complete all customer deliverables in accordance within the approved project schedule Completion Criteria: ♦ All sites are ready for equipment installations in compliance with Motorola's R56 Standards and Guidelines for Communication Sites. Page 17 City of Fort Worth Local Government System Equipment Refresh System Installation Install Fixed Network Equipment Motorola Responsibilities: ♦ Will provide a short term storage Iocation for the Motorola-provided equipment. ♦ Receive and inventory all equipment. ♦ Install system equipment as specified by the Equipment List,System Description, and system drawings Interference Motorola is not responsible for interference caused or received by the Motorola provided equipment except for interference that is directly caused by the Motorola provided transmitters)to the Motorola provided receiver(s).Should the City of fort Worth system experience interference,Motorola can be contracted to investigate the source and recommend solutions to mitigate the issue. ♦ Bond the supplied equipment to the site ground system in accordance with the Motorola R56 Standards and Guidelines for Communication Sites. o Will interface with the following network connections:Microwave or T1 ® Will remove existing equipment that is part of the system replacement. ♦ Will transport removed equipment to a location designated by the Customer within the City of Fort Worth. ♦ Will not dispose of existing equipment. Customer Responsibilities: ♦ Provide access to the sites,as necessary. Completion Criteria: ♦ Fixed Network Equipment installation completed and ready for optimization. Fixed Network Equipment Installation Complete ♦ All fixed network equipment installed and accepted by the Customer. System Installation Acceptance(Milestone) ♦ All equipment installations are completed and accepted by the Customer. System Optimization Optimize System FIVE Motorola Responsibilities: Page 18 City of Fort Worth Local Government System Equipment Refresh ♦ Verify that all equipment is operating properly and that all electrical and signal levels are set accurately. ♦ Verify that all audio and data levels are at factory settings. ♦ Check forward and reflected power for all radio equipment, after connection to the antenna systems,to verify that power is within tolerances. ♦ Motorola and its subcontractors optimize each subsystem. ♦ Check audio and data levels to verify factory settings. ♦ Verify communication interfaces between devices for proper operation. ♦ Test features and functionality are in accordance with manufacturers' specifications and that they comply with the final configuration established during the CDR/system staging. Customer Responsibilities: ♦ Provide access/escort to the sites. Completion Criteria: ♦ System IiNE optimization is complete. Optimization Complete ♦ System optimization is completed. Motorola and the Customer agree that the equipment is ready for acceptance testing. Training Perform Training Motorola Responsibilities: o MTC3600 technician training is included for up to six students ♦ Finalize training schedules purchased as part of this project with the Customer Project Manager. o Conduct the training classes outlined in the Training Plan. (attached) Customer Responsibilities: ♦ Attend training classes. ♦ Comply with the pre-requisites in the Training Plan. Completion Criteria: ♦ All training classes completed. Training Complete ♦ All training classes completed. Audit and Acceptance Testing Perform R-56 Audit Motorola Responsibilities: Page 19 City of Fort Worth Local Government System Equipment Refresh ♦ Perform R-56 site-installation quality-audits,verifying proper physical installation and operational configurations. ♦ Create site evaluation report to verify site meets or exceeds requirements,as defined in Motorola's R 56 Standards and Guidelines for Communication Sites. Customer Responsibilities.- Provide access/escort to the sites. ♦ Witness tests. (if desired) Completion Criteria: ♦ All R-56 Standards and Guidelines for Communication Sites audits completed successfully. Perform Equipment Testing Motorola Responsibilities: ♦ Test individual components of the system to verify compliance to the equipment specifications. ♦ Repeat any failed test(s)once Motorola(or the Customer)has completed the corrective action(s). ♦ Prepare documentation of component tests to be delivered as part of the final documentation package. Customer Responsibilities: ♦ Witness tests if desired. Completion Criteria: ♦ SuccessfuI completion of equipment testing. Perform Functional Testing Motorola Responsibilities: ♦ Verify the operational functionality and features of the individual subsystems and the system supplied by Motorola,as contracted. ♦ If any major task as contractually described fails,repeat that particular task after Motorola determines that corrective action has been taken. ♦ Document all issues that arise during the acceptance tests. ♦ Document the results of the acceptance tests and present to the Customer for review. ♦ Resolve any minor task failures before Final System Acceptance. Customer Responsibilities: ♦ Witness the functional testing. Completion Criteria: ♦ Successful completion of the functional testing. ♦ Customer approval of the functional testing. Page 20 City of Fort Worth Local Government System Equipment Refresh Perform Coverage Testing Motorola Responsibilities: ♦ Motorola and the Customer determine the required number of test vehicles for simultaneous testing of multiple service areas. ♦ Perform coverage testing according to the Contract Coverage Acceptance Test Plan(CATP) that's part of this document. ♦ Submit test reports within the agreed period. ♦ If any area fails,re-test that particular area when Motorola determines that corrective action has been taken. o Document all issues that arise during the coverage testing. o Submit final test reports,according to the agreed period. Customer Responsibilities: ♦ Provide the required number of test vehicles,drivers,and resources to witness the coverage testing. ♦ Review the test results in a timely manner. ♦ Timely approval of the test results,if the reports indicate compliance with the agreed requirements. Completion Criteria: ♦ Successful completion of the coverage testing and approval by the Customer. System Acceptance Test Procedures(Milestone) ♦ Customer approves the completion of all the required tests. Finalize System Cutover Motorola Responsibilities: ♦ Motorola and the Customer approve a mutually agreed upon cutover plan based upon discussions held during the CDR. ♦ During cutover,follow the written plan and implement the defined contingencies,as required. ♦ Conduct cutover meeting(s)with user group representatives to address both how to mitigate technical and communication problem impact to the users during cutover and during the general operation of the system. Customer Responsibilities: ♦ Attend cutover meetings and approve the cutover plan. ♦ Notify the user group(s)affected by the cutover(date and time). ♦ Conduct a roll call of all users working during the cutover,in an organized and methodical manner. . ♦ Provide Motorola with the subscriber information for input into the system database,for activation. Completion Criteria: ♦ Successful migration from the old system to the new system. Page 21 City of Fort Worth Local Government System Equipment Refresh Resolve Punchlist Motorola Responsibilities: ♦ Work with the Customer to resolve punchlist items,documented during the Acceptance Testing phase, in order to meet all the criteria for final system acceptance. Customer Responsibilities: ♦ Assist Motorola with resolution of identified punchlist items by providing support, such as access to the sites,equipment and system,and approval of the resolved punchlist item(s)- Completion Criteria: ♦ All punchlist items resolved and approved by the Customer. Transition to Service/Project Transition Certificate Motorola Responsibilities: ♦ Review the items necessary for transitioning the project to warranty support and service ♦ Provide a Customer Support Plan detailing the warranty and post warranty support, if applicable,associated with the Contract equipment. Customer Responsibilities: ♦ Participate in the Transition Service/Project Transition Certificate(PTC)process. Completion Criteria: ♦ All service information has been delivered and approved by the Customer. Finalize Documentation Motorola Responsibilities: ♦ Provide as-built site drawings and revise necessary existing drawings to reflect system changes. (Approximately 20 drawings) ♦ The documentation will be limited to the following: • Maintenance manuals for all site equipment • Functional Acceptance Test Plan test sheets and results • Equipment Inventory List(paper or disk) • ATP Test Checklists • System Block Diagram • RF Site Floor Plan • RF Site Rack Face Diagrams • Antenna Network Drawings for RF Sites • Site Block Diagrams • Technical Service Manuals Customer Responsibilities: ♦ Receive and approve all documentation provided by Motorola. Page 22 City of Fort Worth Local Government System Equipment Refresh Completion Criteria: ♦ All required documentation is provided and approved by the Customer. Final Acceptance(Milestone) ♦ All deliverables completed,as contractually required. ♦ Final System Acceptance received from the Customer. Project A dm in istration Project Status Meetings Motorola Responsibilities: ♦ Once a month or as mutually agreed,the Motorola Project Manager,or designee,will attend all project status meetings with the Customer,as determined during the CDR. ♦ Record the meeting minutes and supply the report. ♦ The agenda will include the following: • Overall project status compared to the Project Schedule. • Product or service related issues that may affect the Project Schedule. • Status of the action items and the responsibilities associated with them,in accordance with the Project Schedule. • Any miscellaneous concerns of either the Customer or Motorola. Customer Responsibilities: ♦ Attend meetings. ♦ Respond to issues in a timely manner. Completion Criteria: ♦ Completion of the meetings and submission of meeting minutes. Progress Milestone Submittal Motorola Responsibilities: ♦ Submit progress(non-payment)milestone completion certificate/documentation. Customer Responsibilities: ♦ Approve milestone,which will signify confirmation of completion of the worm associated with the scheduled task, Completion Criteria: ♦ The Customer approval of the Milestone Completion document(s). Page 23 City of Fort Worth Local Government System Equipment Refresh Change Order Process Either Party may request changes within the general scope of this Agreement. If a requested change causes an increase or decrease in the cost or time required to perform this Agreement, the Parties will agree to an equitable adjustment of the Contract Price,Performance Schedule,or both,and will reflect the adjustment in a change order_ Neither Party is obligated to perform requested changes unless both Parties execute a written change order. Page 24 City of Fort Worth Local Government,System Equipment Refresh Functional Acceptance Test Plan Overview Methodology The Local Government System Functional Each test identified in this document shall be Acceptance Test Plan(FATP)will be executed at the conducted by a Motorola representative and completion of equipment installation.The purpose of witnessed by an authorized City of Fort Worth this test is to verify correct system functionality with representative.The results of each test will be regard to the equipment refresh. compared with the test goals and recorded as Representatives of both the City of Fort Worth and Pass/Fail on the record sheets.If deficiencies are Motorola will witness the test and provide sign off found during the tests,both the deficiencies and the upon completion of each individual test and the resolutions will be agreed on and documented.Any summary results of the entire test. deviations detected during this testing will be The failure of one test in the testing process will be corrected by Motorola,retested, and witnessed by the considered a failure of that portion of the test only, City. and not the entire test.The individual test or group of As each test is completed, the Motorola and Fort the tests affected by the failure will be repeated after Worth representatives will record the date of the test, corrections have been completed.An acceptance the test results,and their initials.The City of Fort punch list of items to be improved or corrected will Worth and Motorola will sign a statement of be created and tracked to completion. conditional acceptance upon successful completion of Acceptance Test Procedures this ATP. Any system testing that the City of Fort Worth wants Quantar Hardware Testing performed that is not specified in the ATP listing section may reviewed by Motorola for feasibility and acceptability. Any additional tests may represent a Each Quantar repeater supplied as part of this project change in the project's scope. will be tested and measured during the installation phase.All pertinent station data will be documented Each test will be conducted independently using as part of the final documentation package.In detailed check sheets to be provided by Motorola,as addition,a full complement of station diagnostics will appropriate, and approved by the City of Fort Worth be performed and critical parameters will be prior to commencement of acceptance testing. If measured and recorded.The sample chart shown on deficiencies are found during the testing,both the the following page will be completed for each of the deficiencies and resolutions to the deficiencies shall Quantars supplied for this project. be agreed upon and documented.Where the defined deficiencies do not prevent productive operational use of the system,the test will be deemed to have been completed. Motorola will,however,remain responsible for the resolution of the remaining deficiencies as agreed. Test Objective These tests are being performed to verify the basic functionality and operating parameters of the Local Government system. Page 25 City of Fort Worth Local Government System Equipment Refresh Sample QuantarDatasheet System ID Customer Name Site name Site number Channel Number/Name Date of Test Model Number Serial Number Performed by Title Versions BoardlKit# Typical Value l*Note Firmware Version Station Control Board R020.10.513 Station Wireline Board R020.10.001 Station Exciter Board R020.09.005 Station Boot2 Firmware R020.10.001 Station IP address 145.1. Site ID . Chan# Back lane ID *Exam le 000001B3BF7B Code plug Version Date Dependant Transmitter Tests Note Measured Transmitter Frequency Programmed TX Frequency in MHz Reference Oscillator Frequency Error,Measured in Hertz TX Deviation Adjustment Refer to Service Manual/RSS Help Frequency 1 Fre uenc 2 Frequency3 Frequency 4 Modulation Compensation Observe Modulation Scope Pass or Fail Frequency 1 Frequency 2 Power Out ut During Calibration Full PA Output Power 100 Reflected Power at Station Measured in Watts 0 VSWR at Station Auto-Calculated 1.00 Receiver Tests Note Typical Value Measured Receiver Frequency in MHz Refer to Site Doc. NIA 12dB,SINAD at Receiver Refer to Service Manual Refer to Service Manual 12dB SINAD at Multicou Ier Refer to MOP Same as 12dB SINAD b7gwIch Setting Refer to Service Manual I Site De endant Wireline Ad justments RSS Pro rammed Test Set Rx Wireline Test Tone Level 1kHz Status/Activity Tone Level TX Wireline Input Power Source Note Measured input Supply Voltage AC or DC input supply voltage Page 26 City of Fort Worth Local Government System Equipment Refresh Smartnet Trunling Features The purpose of the following tests are to verify some of the Srnartnet Trunking features of the system with the new controller. Page 27 City of Fort Worth Local Government System Equipment Refresh 2.TEST SmartNet Trunking Features Step 1. Initiate a talkgroup call with RADIO-1. Talkgroup Call Step 2. Verify the ISW is decoded by the MTC 3600. 1.DESCRIPTION Step 3. Verify communication with RADI0-2. The Talkgroup Call is the primary level of organization for communications on a trunked radio Pass Fail system. Radios with talkgroup call capability will be able to communicate with other members of the same talkgroup. Radio users can select between the different talkgroups that are programmed in the radio using a manual switch or keypad. SETUP RADI0-1 -TALKGROUP 1 RADI0-2-TALKGROUP 1 VERSION#1.03 Page 28 City of Fort Worth Local Government System Equipment Refresh SmartNet Trunking Features 2.TEST Step 1. Disable all but one voice channel via the Busy Queuing and Call Back SMT. I.DESCRIPTION Step 2. Verify priority levels of talkgroups via the SAC command in the SMT. Once the system channel capacity is full,all radio Step 3. Press the PTT of RADI0-1 and hold.This users trying to enter the system will receive a Busy wiII capture the last voice channel. signal and be put in queue by priority. Once a voice channel is available,the system will call back the Step 4. Key RADIO-2 and then key RADIO-3. highest queued user with a callback tone. Both RADIO-2 and RADIO-3 will receive SETUP busy tones. Step S. Release the PIT of RADIO-1. RADIO-1 -TALKGROUP 1 -PRL--8 RADIO-2-TALKGROUP 2-PRLr8 Step 6. RADIO-2 will receive the first callback. RADI0-3 -TALKGROUP 3-PRL=8 Step 7. RADI0-3 will receive the second callback. VERSION##1 Pass Fail Page 29 City of Fort Worth Local Government System Equipment Refresh SmartNet Trunking Features 2.TEST Step 1. Set Top of Queue method using the EMRG Emergency Alarm and Call -Tactical command via the SMT. 1.DESCRIPTION Step 2. Disable all but one voice channel via the SMT. An Emergency Alarm is initiated from a portable or Step 3. Depress and hold the PTT of RADIO-1. mobile by depressing the preprogrammed emergency button. Once initiated,the radio unit sends a burst of Step 4. Key RADIO-3(RADIO-3 will receive a data over the control channel(no voice channel busy tone). assigned). The dispatcher is immediately notified of the emergency status by an audible alert and visual Step 5. Press the emergency button RADIO-2 to display of the emergency caller`s ID at the Centracom initiate the emergency alarm.An audible Series Gold Console,System Watch or SIMS. acknowledgment tone will be received and the display will indicate emergency. After the emergency unit depress PTT,if a voice channel is available,it will be assigned immediately Step b. Verify the display of the emergency alarm and the Emergency Call will proceed. The on the management terminals on Emergency Call will take place on either the TALKGROUP 1. talkgroup that the user is currently on(Tactical)or will revert to a predetermined talkgroup. Step 7. Key RADIO-2(RADIO-2 will receive a busy tone). In the event of a busy system, two alternatives are offered to handle emergency traffic:Top of Queue, Step 8. Release the PTT of RADI0-1 and observe and Ruthless Preemption. that RADIO-2 receives the callback first as the emergency user. In Top of Queue,the emergency user is put first in the queue,and all current calls are turned to Step 9. Verify extended repeater hangtime(defaults transmission trunked. As soon as the first radio user to 30 seconds)for the emergency call. dekeys,the channel is assigned to the emergency user. Step 10. RADIO-2 clears emergency and RADIO-3 receives a callback.Enable all channels. SETUP Pass Fail RADI0-1 -TALKGROUP 1 PRL=B RADIO-2-TALKGROUP 2 PRL--B RADIO-3 -TALKGROUP 3 PRL--8 VERSION#1.08 Page 30 City of Fort Worth Local Government System Equipment Refresh SmartNet Trunking Features 2.TEST Step 1. Turn RADI0-1 off. Continuous Assignment Updating Step 2. Initiate talkgroup call with RADIO-2 1.DESCRIPTION communicating with RADIO-3. Step 3. While the talkgroup call is in progress,turn When a talkgroup is assigned a voice channel,the RADIO-1 on. controller continues to transmit the channel assignment data for the duration of the call. This Step 4. Observe that RADIO-1 will join the assures that late joining radios will be sent to the talkgroup call in progress. correct channel to join the call in progress. SETUP Pass Fail RADIO-1 -TALKGROUP 1 RADIO-2-TALKGROUP 1 RADIO-3-TALKGROUP 1 VERSION#1.04 Page 31 City o,f Fort Worth Local Government System Equipment Refresh System Reliability Features The purpose of the following tests are to verify some of the reliability features of the system with the new controller. Page 32 City of Fort Worth Local Government System Equipment Refresh System Reliability Features 2.TEST Step 1. Disconnect the transmit antenna connection Transmitter Power Shutdown to trunked repeater 1. This will cause a high VSWR condition. 1.DESCRIPTION Step 2. Key RADIO-1 so that channel 1 is assigned, The MTC 3600 can detect a loss or decrease in and verify that the MTC 3600 will fail this channel. The interface for channel 1 on the transmitter output power of all trunked repeaters ACE card will show the orange disabled connected to it. Each trunked repeater contains an LED driven. internal wattmeter element. Once the forward power has decreased past the threshold set,the repeater Step 3. Restore the transmit antenna connection to instructs the central to take the channel out of service. trunked repeater 1. Verify that the channel is If reflected power increases past the threshold set,the put back into service by the WC 3600 repeater will also instruct the MTC 3600 to take the within five minutes. channel out of service. This information is conveyed via the RS232 cable connection between the MTC 3600 and the trunked repeater. Pass Fail VERSION#1.09 Page 33 City of Fort Worth Local Government System Equipment Refresh System Reliability Features 2.TEST Step 1. Using a service monitor,generate a 1 kHz Receiver Interference Shutdown tone on the receive frequency of trunked repeater 7,modulate the signal at 3.0 kHz, 1.DESCRIPTION with no connect tone. An unauthorized signal is received by a trunked Step 2. Access the PARM command via the SMT terminal. repeater. The interference does not contain the sub- audible connect tone that the central controller is Step 3. Set the Carrier Malfunction Time Out looking for. This can be caused when a mobile from Parameter to 10 seconds with MA command. another system with similar frequencies strays into trunking system range. In order to prevent a Step 4. Verify that within 10 seconds the MTC 3600 disruption of communications,the MTC 3600 will will fail the trunked channel. The shutdown remove this channel from trunked system selection or can be monitored on the front panel of the assignment process when it detects an illegal carrier MTC 3600. The interface for channel 1 on for longer than the specified time out period. Once the ACE card will show the orange disabled the interfering carrier ceases, the channel is returned LED driven. The Channel Status routine of to service. the SMT will also confirm that the channel is disabled. The SMT will also generate an The time-out period(Carrier Malfunction)which is error message indicating this failure. set by the PARM command in the MTC 3600 via the System Manager Terminal,may be set to 1 to 253. Step 5. Remove the interfering signal, and verify Setting the value to 254 will disable the Receiver that the controller will put this channel back Interference Shutdown feature. into service within five minutes. Pass Fail VERSION#1.06 Page 34 City of Fort Worth Local Government System Equipment Refresh System Reliability Features 2.TEST Step 1. Disable one of the Console links. Console to MTC 3600 Link Failure Step 2. Verify the console can continue to monitor 1.DESCRIPTION and dispatch trunked calls. Step 3. Enable the link and wait 30 seconds before The data links between the Central Electronics Bank disabling the other Console link. (CEB)Trunking Interface Module(TIMI)and the trunking central controller are fully redundant. These Step 4. Verify that console continues to monitor and links are tested every 300 milliseconds and a hot- dispatch trunked calls. standby TIMI is updated with the current call status in the event that it must take over. If the data link between the main TIMI and the Controllers or the Pass Fail active TIMI card should fail,the redundant TIMI is activated within 1.5 seconds and normal trunked console operation resumes with no loss of status. VERSION#1.03 Page 3S City of Fort Worth Local Government System Equipment Refresh System Reliability Features 2.TEST Step 1. Set up a service monitor to monitor the Base Station Identification lowest available transmit frequency in the system. 1.DESCRIPTION Step 2. Within 30 minutes,a series of 900 Hz tones are heard. The system call sign is automatically transmitted via International Morse Code once every 30 minutes in compliance with FCC regulations.This message is Pass Fail sent in Morse Code at 17 words per minute using 900 Hz tone modulation. VERSION#1.01 Page 36 City of Fort Worth Local Government System Equipment Refresh System Reliability Features 2.TEST Step 1. Access disable the base station/repeater for Station Failure one channel. 1.DESCRIPTION Step 2. The MTC3600 should mark the base station as failed within 60 seconds. When a Base/Repeater Station fails due to hardware problems,the system will not assign that repeater. Pass Fail VERSION#1.04 Page 37 City of Fort Worth Local Government System Equipment Refresh System Reliability Features 2.TEST Step 1. Power down one base station. Station Power Failure Step 2. Press PTT on RA.D10-1 several times until 1.DESCRIPTION failed station is assigned. When a Base Station fails due to hardware problems, Step 3. Notice the MTC 3600 marks the channel asfailed. the system will not assign that repeater. Step 4. Verify that the MTC 3600 no longer assigns the failed channel. VERSION#1.05 Step 5. Power up base station. Pass Fail Page 38 City of Fort Worth Local Government System Equipment Refresh System Reliability Features 2.TEST Step 1. Disable all possible control channels via the Failsoft Operation SMT, 1.DESCRIPTION Step 2. Verify system enters failsoft and all trunked repeaters immediately key up. To ensure continued communications,the trunked Step 3. Verify that RADI0-1 and RADIO-2 enter system will enter "failsoft anode"in the event that the failsoft mode, and hear periodic failsoft tone. MTC 3600 can no longer control the trunking system. Failsoft operation will occur if any of the following Step 4. Verify communication per the entire conditions are present: fleetmapping plan to ensure proper - No Control Channels available operation. - No Voice Channels available Step 5. Enable the control channels. - Loss of any MTC 3600 site - Loss of any main MTC 3600 boards Step 6. Verify that the system resumes trunking - Loss of power to MTC 3600 within 5 minutes When in this mode, trunked radios operate as they would an a conventional repeater system. In failsoft, Pass Fail talkgroups are distributed across the different trunked repeater channels. These assignments are part of the customer fleetmap plan and are preprogrammed into each trunked radio,as well as consoles operators. Since there are a limited number of trunked channel resources,different talkgroups will share the same failsoft channel. These talkgroups will be merged together for the duration of failsoft. It is important to ensure that the groups that normally communicate together while the system is trunking should fail to the same trunked repeater in failsoft. Trunked radio users are alerted to the failsoft condition by visual display of failsoft,and a periodic audible tone. Note: This test will be performed on the new controller with a subset of channels on dummy loads. This will avoid service interruption on a live system. VERSION#1.03 Page 39 City of Fort Worth Local Government System Equipment Refresh Elite Console Features The purpose of the following tests are to verify the functionality of the controller console interface. Page 40 City of Fart Worth Local Government System Equipment Refresh Elite Console Features 2.TEST Step 1. The console operator selects the Console Talkgroup Call TALKGROUP 1 resource window and changes his mode to clear by depressing the 1.DESCRIPTION padlock button so that it displays an open padlock. Resource Windows are used to communicate with Step 2. Transmit on RADIO-1 in the clear mode. talkgroups. Each talkgroup in the system will have its own resource window. Step 3. Verify that the console hears audio through the select speaker. A call from a subscriber unit to a console is indicated on each dispatch operator position that has a resource Step 4. Verify the display of RADIO-Ps ID on the window associated with the channel the subscriber TALKGROUP 1 resource window,and that unit is transmitting on. no padlock is displayed because the transmit and receive modes match. When a subscriber keys on a talkgroup that the console has selected,the subscriber's audio comes out Step 5. Transmit on console in the clear mode, of the select speaker of the console.Audio on verify communication with RADIO-1. talkgroups that the console has not selected is heard on the unselected speaker. Pass Fail If the resource has secure capability,a padlock button appears in the resource window. If an incoming call is uncoded and is received on a channel where the transmit mode is set to coded,an unlocked padlock appears in the call indicator area on the resource. If an incoming call is coded and the transmit mode is set to clear,a locked padlock appears in the call indicator area. NOTE:If the system is clear only,the default transmission mode is clear. There will be no mode indication on the console. SETUP RADIO-1 -TALKGROUP 1 CONSOLE-TALKGROUP 1 Resource Window VERSION#1.03 Page 41 City of Fort Worth Local Government System Equipment Refresh Elite Console Features 2.TEST Step 1. The operator selects the TALKGROUP 1 Console Priority Resource Window. 1. DESCRIPTION Step 2. RADIO-1 transmits on TALKGROUP 1. Console operator positions have ultimate control of Step 3. Verify that RADIO-2 can hear RADIO 1. transmitted audio on an assigned voice channel Step 4. While RADI0-1 is transmitting,key resource.The console position possesses the TALKGROUP 1's Resource Window on the capability to take control of an assigned voice operator. channel for a talkgroup call so that the operator's audio overrides any subscriber audio. Console Step 5. Verify that RADIO-2 hears the console but priority is a feature that enables dispatchers to gain not RADIO-1.This shows that the console immediate access to an assigned voice channel so that has priority over the subscriber. a central point of audio control exists. Step 6. Dekey the Console. SETUP Step 7. Verify that RADIO-2 now hears RADIO-1. RADI0-1 -TALKGROUP 1 Pass Fail RADIO-2-TALKGROUP 1 VERSION#1.41 Page 42 City of Fort Worth Local Government System Equipment Refresh Elite Console Features 2.TEST Step 1. Press the emergency alarm button and key- Emergency Alarm and Cali up on RADIO-1. Verify that an audible alarm is present at the console. 1.DESCRIPTION Step 2. Verify that TALKGROUP 1's resource When an operator position receives an emergency window border is blinking red and that alarm, the following indications occur. RADIO-Is ID or alias is shown in the resource window. The alarm will also be -The emergency alarm tone sounds through the displayed in the activity log. console select speaker. Step 3. Press the tone off icon to turn off the audible -A red border flashes around the resource window alarm. and the ID or alias is displayed in the resource Step 4. Acknowledges the emergency and verify window. communication between RADIO-1 and the -A flashing message is displayed on the monitor console. activity log identifying which channel the emergency Step 5. Verify the extended repeater hang-time alarm occurred on. This assists the user to find the granted to the emergency call. talkgroup resource window quickly,even if the resource window is covered by another resource. Step 6. Reset the emergency from the console by window. pressing the cross icon,followed by the At the end of an emergency call,a channel drop out acknowledgment and knockdown icons. time begins,this time is adjustable 25:24). The Step 7. Reset the emergency from RADIO-1. emergency call remains in the system until the time out expires. SETUP Pass Fail RADIO-1 -TALKGROUP 1 VERSION#1.01 Page 43 City of Fort Worth Local Government System Equipment Refresh Elite Console Features 2.TEST Step 1. Initiate a TALKGROUP 1 call from PTT ID/Alias Display RADIO-1. 1.DESCRIPTION Step 2. Verify that RADIO-1's unit ID or alias displays at the TALKGROUP 1 resource on the console position. Console operator positions contain various resources such as talkgroup,multigroup,Private Call which enable the operator to communicate with the Pass Fail subscriber units. If activity occurs on one of these operator position resources, the unit ID or associated alias of the initiating radio appears at the console resource. Default operation for the system is to display unit IDs at the console operator resource,but pre-defined aliases can be substituted for each unit ID. Depending upon system configuration,the unit ID or the unit ID alias can be displayed at the console operator resource. If an alias display is preferred, then unit ID aliases must be programmed to appear at the console dispatch position. SETUP RADIO-1 -TALKGROUP 1 VERSION#1.01 Page 44 City of Fort Worth Functional Test Signoff Certificate By their signatures below,the following witnesses certify they have observed the In-Plant System Acceptance Test Procedures. Signatures WITNESS: Mild: Please Print Name: Initials WITNESS: d PIease Print Name: � Initials WITNESS: late PIease Print Name: I Initials Page 45 City of Fort Worth Coverage acceptance test plan Overview This Coverage Acceptance Test Plan(CATP)is designed to verify that the Local Government radio system equipment refresh will meet or exceed the required coverage reliability within the City of Fort Worth's service area as indicated on Motorola's coverage maps.The CATP defines the coverage testing method and procedure,the coverage acceptance criterion,the test documentation,and the responsibilities of both Motorola and the City of Fort Worth. Coverage Acceptance Testing is based upon a coverage prediction that accurately represents the implemented infrastructure and parameters that are consistent with the contract agreements. If the implemented system varies from the design parameters,then a revised coverage map will be prepared.New test maps will reflect the measured losses and gains associated with the implemented infrastructure and subscribers.These will be used to define the test configuration and potential areas from which test locations may be included in the evaluation process. Since this is a single site,analog system,Motorola is proposing an automated drive test to collect signal strength data.The pass/fail criterion will be-103 dBm plus any adjustments needed for the performance of the antenna used. To verify that the radio coverage reliability is met,the indicated coverage area within the City of Fort Worth's operating area will be divided into approximately 1700 equally sized test tiles which are approximately.5 mile square.The intent is not to test every point within the service area but rather to verify the accuracy of the coverage prediction map. If the City desires additional and/or smaller test tiles,this may represent a change in scope and possibly additional costs. CATP Definitions Several definitions are needed to accurately describe the coverage test method. Where cited,these terms or methods are defined in TSB-88A-11. Coverage Area: The coverage area is the geographical region in which communications will be provided which meets or exceeds the specified Channel Performance Criterion at the specified reliability for the specified equipment configuration(s). Radio systems are typically designed to maximize the coverage area within the customer's service area (users' operational area,jurisdictional boundaries, etc-) {TSB-88A,clause 4.11 The predicted 35 watt mobile coverage area for this system is indicated on Motorola's coverage map(s)supplied with this proposal. Channel Performance Criterion(CPC): The CPC is the specified minimum design performance level in a faded channel. {TSB-88A,clause 4.21 For this system, the CPC is a Delivered Audio Quality of DAQ-3.0. The DAQ definitions are provided in Table 1. {TSB-88A, §4-5.1,Table 11. Given the static reference sensitivity of a receiver,the faded performance threshold for the specified CPC is determined by using the projected CPC requirements for different DAQs listed in TSB-88A,Annex A,Table A-1. The CATP pass/fail criterion for each test location is the faded performance threshold,plus any adjustments for antenna performance and in-building or in-vehicle losses. (TSB-88A,subelause 4.5.1,Figure 2) 1 Wireless Communications Systems---Performance in Noise-and Interference-Limited Situations--- Recommended Methods for Technology-Independent Modeling,Simulation, and Verification,Technical Service Bulletin TSB-88A-1,Telecommunications Industry Association(TIA),Arlington VA, 1999 &2002. Page 46 City of Fort Worth Table I—Delivered Audio QualityDefanitions DAQ (Delivered Audio Quality) Subjective Performance Description 1 Unusable,speech present but unreadable. 2 Understandable with considerable effort. Frequent repetition due to noise / distortion. 3 Speech understandable with slight effort. Occasional repetition required due to noise/distortion. 3.4 Speech understandable with repetition only rarely required. Some noise / distortion. 4 Speech easily understood. Occasional noise/distortion. 4.5 Speech easily understood.Infrequent noise/distortion. 5 Speech easily understood. Reliability. The reliability is the percentage of locations within the coverage area that meet or exceed the specified CPC. Motorola's coverage map(s)indicate the area within which this system is predicted to provide at least 97%reliability of meeting or exceeding the CPC of DAQ-3.0. {TSB-88A,subclause 4.4.2;not regulatory contour reliability} Equipment Configurations: These are the types and configurations of radio network and field unit equipment upon which coverage acceptance is based. Motorola's coverage map(s)for this system indicate(s)the coverage area for the following equipment configuration: • Single site coverage to and from analog 35-watt mobile radios: The mobile radio will be installed in a standard configuration in a typical vehicle. In Building Coverage: In-building coverage will not be tested. CATP Method The method used to test coverage is statistical sampling of the predicted coverage area to verify that the CPC is met or exceeded at the required reliability for each of the defined equipment configurations. It is impossible to verify every point within a coverage area,because there are infinite points;therefore,coverage reliability will be verified by sampling a statistically significant number of randomly selected locations,quasi-uniformly distributed throughout the predicted coverage area. This CATP provides an objective,quantitative method of measurement using Motorola's Voyagers" hardware and software. The method follows TIA TSB-88A section 7.0,"Performance Confirmation",and has direct correlation with Motorola's coverage prediction methodology. Page 47 City of Fort Worth Determine the required number of test tiles in the coverage area: The predicted coverage area shown on Motorola's coverage map will be divided into a tile pattern to produce at least the number of uniformly sized test locations required by the Estimate of Proportions formula. {TSB-88A,subclause 7.2.1,equation 521 The minimum number of test tiles required varies for different systems,from a hundred to many thousands,depending on the size of the coverage area,desired confidence in results,type of coverage test,and the predicted versus required reliability. Constraints on test tile sizes The minimum test tile size is 100 by 100 wavelengths;however,the minimum practical test tile size is typically about 400 by 400 meters(about 0.25 by 0.25 miles). The minimum practical size for any system is determined by the distance traveled at the speed of the test vehicle while sampling,GPS error margin,and availability of road access within very small tiles. A related consideration is the time,resources,and cost involved in testing very large numbers of very small test tiles. The maximum test file size is 2 by 2 km (1.25 by 1.25 miles). {TSB-88A,subclause 7.4.31. In some wide-area systems,this constraint on maximum size may dictate a greater number of test locations than the minimum number required by the Estimate of Proportions formula. Accessibility l to test tiles Prior to testing(if possible)or during the test,Motorola and the City of Fort Worth will determine whether any test tiles are inaccessible for the coverage test(due to lack of roads,restricted land, etc.) Inaccessible tiles will be eliminated from the acceptance test calculation. {TSB-88A,subclause 7.4.41 Randomly SelectA Test Location Within Each File: Using Voyagers',the actual test location within each tile will be quasi-randomly selected by the test vehicle crossing into the the at an arbitrary point,with an arbitrary speed and direction. Perform Measurements In Each Tile: , In each test tile,a series of sequential measurements(subsamples)will be made. This test location measurement,containing a number of subsamples,constitutes the test sample for this location. The test sample will establish the local median signal level within the test tile. The distance over which the subsamples are measured will be 40 wavelengths. A median of multiple signal strength subsarples is used rather than a single measurement to ensure that the measurement is not biased by taking a single sample that might be at a peak or null point on the radio wave. Determine If Each Tile Passes Or Fails The CPC Requirement. For each tile, the pass / fail criterion is the faded performance threshold for the specified CPC, plus any adjustments for antenna performance. Coverage acceptance testing will be performed in the talk-out direction to a test receiver in a vehicle. Determine The Coverage Area Reliability For Acceptance: After all accessible tiles in the coverage area have been tested;the coverage area reliability(%)will be determined by dividing the number of tiles that pass by the total number of tiles tested. JTSB-88A,clause 7.1,equation 51}The coverage test acceptance criterion is that the tested coverage area reliability must be equal to or greater than the required reliability of 97%. Responsibilities and Preparation This information will help set the expectations of the City of Fort Worth and Motorola regarding requirements for equipment,personnel,and time during the coverage test. Page 48 City of Fort Worth The City of Fort Worth will provide the following for the duration of the coverage test: • At least one test vehicle that is representative of the vehicles to be installed with mobile radios,including antenna location • At least one City representative, to drive each test vehicle and/or to be the customer representative(s)for the test team(s) Motorola will provide the following for the duration of the coverage test: • At least one Motorola representative,to navigate and to operate[Voyagers"' • At least one calibrated Motorola Voyagers" coverage testing package • At least one laptop computer equipped with Voyagers" software Coverage acceptance testing will be performed in the portion(s)of the City of Forth's operating area predicted by Motorola to provide the required reliability. Motorola will determine the minimum number of test tiles required, as described in the Method section of this CATP. Motorola and the City of Fort Worth will plan the route for the test vehicle(s)through the coverage test area, to ensure that at least the minimum required number of tiles are tested. If possible,any tiles not accessible to the test vehicle(s)will be identified while planning the route. No acceptance testing will be performed in locations on Motorola's coverage map(s)predicted to be below the required reliability. Motorola and the City may agree to perform"information only"tests in such locations; however,these"information only"test results will not be used for coverage acceptance. Any"information only"test locations must be defined before starting the test. If the added locations require significant additional time and resources to test, a change order will be required and Motorola may charge the City on a time-and-materials basis. Motorola will calibrate the test receiver(s)used with the Voyagers" coverage testing package. Depending on the system,the test receiver(s)may be provided by either Motorola or the City. Motorola will conduct this test only once. If any portion of the test is determined to be unreliable because of proven equipment malfunctions or failures,Motorola will repeat the portion of the test affected by the equipment malfunction or failure_The City of Fort Worth will have the option to accept the coverage at any time prior to completion of the coverage test. Before starting the test, the City and Motorola will agree upon the time frame for Motorola's submission of a report containing the coverage test results. CATP Procedures A quantitative coverage acceptance test will be performed using Motorola's Voyager$"' package,to provide objective verification that the system provides the faded performance threshold for the specified CPC. Voyagers"' consists of the following: • A calibrated test receiver,connected to an antenna installed in a representative location on the test vehicle. The test receiver will monitor transmissions from the fixed network radio site. • A Global Positioning System(GPS)receiver,which will provide the computer with the location and speed of the test vehicle. • A laptop computer with Voyagers"'software and a mapping database,which includes highways and local streets,political boundaries,rivers,railroads, etc. Page 49 City of Fort worth The procedure for the objective signal strength coverage test will be as follows: • The Voyagers"' package will be installed in a test vehicle. City personnel will drive the test vehicle over a route planned to cover the accessible tiles within the coverage test area.Motorola personnel will operate the Voyager Impackage. • During the coverage test,the laptop computer will display the vehicle's location on a map of the coverage test area overlaid with the test tiles. Voyagers"' will automatically initiate signal level measurements when the GPS receiver indicates that a the has been entered. The computer will provide a visual indication that a measurement has been completed in a tile.Voyagerlmwill manage the coverage test data collection,and will store for later analysis the mobile outbound reference signal level measured in each tested tile. • Coverage acceptance will be based on demonstrating that at least 97%of the tiles in the coverage test area are measured to provide a median signal Ievel of 103 dBm or greater at the mobile test receiver input. • Any tile that fails the objective Voyagers"signal level test described above will be re-tested using a subjective Delivered Audio Quality(DAQ)test. The pass/fail criterion for the subjective test will be a DAQ level of 3.0.Any tile that fails the objective test,but passes the subjective re-test will be declared passed. CATP Documentation and Coverage Acceptance During the coverage acceptance test,Voyagers"' generates computer files that include the Reference Tile Levels for each test tile. A copy of this raw data will be provided to the City at the conclusion of the coverage test. Motorola will process this data to determine whether the coverage test was passed for each equipment configuration,and to produce a map detailing the coverage test results. Motorola will submit to the City a report detailing the coverage test results_ This report will include a document, which is to be signed by both the City and Motorola,indicating the test was performed in accordance with this CATP and the results of the test indicate the acceptance or non-acceptance of the coverage portion of the system. The City will have the option to accept the coverage at any time prior to completion of the coverage test or documentation process. Page 50 City of Fort Worth Page 51 City of Fort Worth Local Government System Equipment Refresh System Acceptance Certificate Customer Name. Project Naive: This System Acceptance Certificate memorializes the occurrence of System Acceptance. Motorola and Customer acknowledge that: 1. The Acceptance Tests set forth in the Acceptance Test Plan have been successfully completed. 2. The System is accepted. Customer Representative: Motorola Representative: Signature: Signature: Print Name: Print Name: Title: Title: Date: Date: FINAL PROJECT ACCEPTANCE: Motorola has provided and Customer has received all deliverables, and Motorola has performed all other work required for Final Project Acceptance. Customer Representative: Motorola Representative: Signature: Signature: Print Name: Print Name: Title: Title: Date: Date: Page 52 CRY ©f York Worth, Texas !mayor and Council Communication COUNCIL ACTION: Approved on 2/24/2004 DATE: Tuesday, February 24, 2004 LOG NAME: 13PO4-0032 REFERENCE NO.: **P-9920 SUBJECT: Purchase Agreement with Motorola Communications, Inc. for Radios, Radio Parts and Equipment, and Radio Repair Services for the Information Technology Solutions Department RECOMMENDATION: It is recommended that the City Council: 1. Authorize a purchase agreement with Motorola Communications, Inc. (Motorola) for the purchase of radios, radio parts and equipment, and radio repair services using the Houston-Galveston Area Council Contract (HGAC) RA00-70 agreement; and 2. Authorize this agreement to begin February 24, 2004, and expire December 31, 2004, with options to renew for three one-year periods subject to HGAC renewing or issuing a new contract to Motorola for similar equipment and services. DISCUSSION: The City of Fort Worth uses Motorola's SmartNet II Trunked Radio Platform for its voice radio communications. The City also uses Motorola's RD-LAP Radio Platform for its mobile data communications. Due to the proprietary nature of the City's two existing systems, radios, parts and equipment must be compatible with the infrastructure components. The Information Technology Solutions Department's Communication Services Group coordinates the purchase of radios, parts, equipment, and repair services for all City departments. The City will utilize the HGAC contract to purchase radios, radio equipment, radio parts and radio repair services for Motorola equipment. HGAC has as a part of its mission to provide cooperative purchasing agreements for qualifying agencies. Under Section 791.025C of the Texas Government Code, a local government that purchases goods and services under this section satisfies the requirement that the local government seek competitive bids for the purchase of goods and services. The Information Technology Solutions Department will procure goods and services through this cooperative purchasing agreement on an as-needed basis. The following table shows the approximate dollar expenditures by four major categories of goods and services that the City of Fort Worth has spent in the last year: Category- Approximate Annual Expenditure Radio Parts $125,000 Voice Radios (Mobile and Handheld) $325,000 Infrastructure Equipment $ 45,400 Repair Services (Radio and Other) $148,600 Logname: 13PO4-0032 Page 1 of 2 About 85% of the repair services component is for the repair of voice mobile and voice portable handheld radios. The remaining portion of the repair component is for infrastructure repair, keyboards and screens associated with mobile data computers (MDCs) and other minor items. It is anticipated that the Police and Fire Departments will be the two departments requesting the majority of the radios that the Information Technology Solutions Department is asked to procure through this purchase agreement. The above totals represent approximate expenditures in the previous one-year period. Future expenditures for equipment, parts and services are dependant on City departments needs and budgets for the year. MIWBE - A waiver of the goal for MIWBE subcontracting requirements was requested by the Purchasing Division and approved by the M/WBE Office because the purchase of goods or services is from sources where subcontracting or supplier opportunities are negligible. RENEWAL OPTIONS - This agreement may be renewed for up to three successive one-year terms at the City's option, if the HGAC renews the contract, or signs a new contract, with Motorola. This action does not require specific City Council approval provided that the City Council has appropriated sufficient funds to satisfy the City's obligations during the renewal term. FISCAL INFORMATIONICERTIFICATION: The Finance Director certifies that funds are available in the current operating budgets, as appropriated, of the participating departments. BQN104-00321LGS TO Fund/AccountlCenters FROM Fund/AccountlCenters Submitted for City Manager's Office by: Richard Zavala (6183) Ori inating Department Head: Jim Keyes (8517) Additional Information Contact: Robert Combs (8357) Kate Yarhouse (8465) Logname: 13PO4-0032 Page 2 of 2 Page 1 of 3 Farmer, Maleshia From: DeHoyos, Beatrice Sent: Monday, June 02, 2008 1:12 PM To: Farmer, Maleshia Subject: RE: Motorola Local Government Refresh We purchased hardware for the radio infrastructure back in September 2008 under MdrCP--9920. We have received the hardware. Now we need the hardware to be installed and supported. (The reason for the agreement.) The hardware has already been paid for. The agreement should already have been executed back in November- December time frame, but somehow i t go t dropped from someone's radar. We now need the hardware to be installed by Motorola. Please let me know if you have any questions Tha4lk4! Sea tv i ce'Del ayo�- Sr. IT Services Specialist/Contract Administrator City of Fort Worth Tel: 817.392.6640 Fax: 817.392.8654 ��vrt�w��;Yvkndwled�e,c riwy��c�y�th�baptc�nreYes& From: Farmer, Maleshia Sent: Monday, June 02, 2008 11:54 AM To: DeHoyos, Beatrice Subject: RE: Motorola Local Government Refresh Bea, based on this M&C, I'm not connecting approval for signature of this contract. Am I missing something? Please explain. Thanks, Maleshia B. Farmer Assistant City Attorney City of Fort Worth (817) 392-7647 From: DeHoyos, Beatrice Sent: Monday, June 02, 2008 10:26 AM To: Farmer, Maleshia Subject: RE: Motorola Local Government Refresh M&C P--9920 6/3/2008 Page 2 of 3 Please let me know if you have any questions Beatr%c&17e,Yoyo-k Sr. IT Services Specialist/Contract Administrator City of Fort Worth Tel: 817.392.6640 Fax: 817.392.8654 4 n1 r vweStOW-,ntisvkpow aLwwyTpayj-Me,beor,4�"t From: Farmer, Maleshia Sent: Monday, June 02, 2008 8:55 AM To: DeHoyos, Beatrice Subject: RE: Motorola Local Government Refresh What's the M&C#? Thanks. Maleshia B. Farmer Assistant City Attorney City of Fort worth (817) 392-7647 From: DeHoyos, Beatrice Sent: Sunday, June 01, 2008 7:17 PM To: Farmer, Maleshia Cc: Smith, Kathryn W. Subject: RE: Motorola Local Government Refresh This was purchase last fiscal year under the old HGACMotorola M&C. The items and services are already paid for. This is the agreement for the services and maintenance. Please let me know if you have any questions Oww". Beau c,elDelRoyo-- Sr. IT Services Specialist/Contract Administrator City of Fort Worth Tel: 817.392.6640 Fax: 817.392.8654 4m i.vweutow t,,rvknz w&dg -a wgya-pavj-theme befit r r�est. From: Farmer, Maleshia Sent: Friday, May 30, 2008 4:25 PM To: DeHoyos, Beatrice Cc: Smith, Kathryn W. 6/3/2008 Page 3 of 3 Subject: Motorola Local Government Refresh Bea, Is there an M&C approving this contract? Maleshia B. Farmer Assistant City Attorney City of Fort Worth 1000 Throckmorton Street Fort Worth, Texas 76102 (817) 392-7647 (direct dial) (817) 392-8359 (fax) maleshia.farmer@fortworthgov.org This message and all attachments are confidential and are intended solely for the use by the individual or entity to which they are addressed. This communication may contain material protected by the attorney-client privilege. Any review, use, distribution, forwarding, printing or copying by persons other than the intended recipients is strictly prohibited. If you believe this email was sent to you in error, please notify the sender by replying to this transmission or by calling Maleshia Farmer at 817-392-7647 and delete this message or any copy. Unless expressly stated in this email, nothing in the message should be construed as a digital or electronic signature. 6/3/2008